Bug#892956: libinput-dev: Requires.private without package dependencies breaks pkg-config users

[Timo Aaltonen]

On 14.03.2018 22:25, Adrian Bunk wrote:
> Package: libinput-dev
> Version: 1.10.3-1
> Severity: grave
> Control: affects -1 src:efl src:gnome-twitch src:muffin src:mutter 
> src:gnome-shell
> 
> https://buildd.debian.org/status/package.php?p=efl=sid
> 
> ...
> configure: error: pkg-config missing libinput >= 0.6.0 xkbcommon >= 0.3.0 
> libudev
> 
> 
> Root cause are the new dependencies in Requires.private
> without package dependencies:
> 
> $ pkg-config --cflags  libinput
> Package libwacom was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libwacom.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libwacom', required by 'libinput', not found

1.10.2-1 didn't have them, and nothing changed in 1.10.3 that would
result in this, so the culprit is elsewhere. Where did that
"Requires.private" come from?


-- 
t

Bug#892981: cenon.app: Incomplete debian/copyright?

[Chris Lamb]

Source: cenon.app
Version: 4.0.6+ds1-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Yavor Doganov 

Hi,

I just ACCEPTed cenon.app from NEW but noticed it was missing 
attribution in debian/copyright for at least Adobe Systems,
NeXT, vhf interservice GmbH, GraphiCode, etc.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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

Processed: bug 888198 is forwarded to https://github.com/lsegal/yard/issues/1161

[Debian Bug Tracking System]

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

> forwarded 888198 https://github.com/lsegal/yard/issues/1161
Bug #888198 [src:yard] yard: FTBFS on ruby2.5: got: ("gem.deps.rb")
Set Bug forwarded-to-address to 'https://github.com/lsegal/yard/issues/1161'.
> thanks
Stopping processing here.

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

Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Chris Lamb]

Source: gnome-themes-extra
Version: 3.27.92-1
Severity: serious
Justication: Policy 12.5

Hi,

I just ACCEPTed gnome-themes-extra from NEW but noticed it was 
missing attribution in debian/copyright for at least adwaita_engine.c
under themes/Adwaita/gtk-2.0.


(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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

Bug#892933: marked as done (isl-0.18: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 05:19:36 +
with message-id 
and subject line Bug#892933: fixed in isl-0.18 0.18-4
has caused the Debian Bug report #892933,
regarding isl-0.18: Incomplete debian/copyright?
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.)


-- 
892933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: isl-0.18
Version: 0.18-2
Severity: serious
Justication: Policy 12.5

Hi,

I just ACCEPTed isl-0.18 from NEW but noticed it was missing 
attribution in debian/copyright for at least a code copy (?) of
imath.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: isl-0.18
Source-Version: 0.18-4

We believe that the bug you reported is fixed in the latest version of
isl-0.18, 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.
Matthias Klose  (supplier of updated isl-0.18 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Mar 2018 05:53:30 +0100
Source: isl-0.18
Binary: libisl-0.18-dev libisl15
Architecture: source
Version: 0.18-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Description:
 libisl-0.18-dev - manipulating sets and relations of integer points bounded by 
line
 libisl15   - manipulating sets and relations of integer points bounded by line
Closes: 892933
Changes:
 isl-0.18 (0.18-4) unstable; urgency=medium
 .
   * Update debian/copyright (copied from isl). Closes: #892933.
Checksums-Sha1:
 775676ff764599e3e1547272a51c349c8be55e9e 1878 isl-0.18_0.18-4.dsc
 5c7d9217afa12a626fb0b9226913f9e8d4522514 0 isl-0.18_0.18-4.debian.tar.xz
 61fcc82100bf0d76fd704a756ecad43787b198b9 5608 isl-0.18_0.18-4_source.buildinfo
Checksums-Sha256:
 b93886eeda25761ecbfb4b33514b3eab9ac6a58e8be03693154f0873ae4d322b 1878 
isl-0.18_0.18-4.dsc
 d24372925cf8baa49d8f1d012087049bdd1394a2c525a6ce0d0f853977ae9560 0 
isl-0.18_0.18-4.debian.tar.xz
 212df3726e6b1b5bcacb409925b6e6bf2c7fc7e51324f4f98b17939240d013e0 5608 
isl-0.18_0.18-4_source.buildinfo
Files:
 daadc0dff2aa738515e1b9d772089895 1878 libs optional isl-0.18_0.18-4.dsc
 d816a8f4e2ee9fe55809f8683d2f78e7 0 libs optional 
isl-0.18_0.18-4.debian.tar.xz
 9c3d53ea6bc64d45e92b04e3a4fd39b7 5608 libs optional 
isl-0.18_0.18-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlqp/JsQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9buPEACTvnD3aLPO1fR/vV5NU3hstR9/FK+21dLd
dUItkZhTV5sJ2mbCcO1yVkLPEyXUN/aM/le/I1a1kY0N9sYM75QCotwZU4RzVcvP
KtnYCMqT10QXbT1cactyvQ+28ECWtJQrtesPsiNvVxsF0A6xxeE1nxJzjWc5I7h2
Ksiqu9lxCBQK7gHXRamrYaU6ZYw9XE9TiQe/UP242Yas17DXtPkwgwa5oNqRJkLp
nW2RhITnO9EpvcCjnGbnGVBx3fXK7qLFowConnDPxNhLcPz6RiSVWiXTDZUSME22
o6ljSTxDcH+2zcSPXPnpS4cAsGIO9XwXoD8bLOghuBQS7kc+9KoRt0Lvtu14vysc
HzaFsyF79CIGAH7wpw3NsD3vbdGb5sej/9Tyokl5S8tzvAC9FG3IATry+oL9m9BJ
FJOuRsxapradrt6+nN3/gP/3DBbti4CfOf4Yu3RzpKmJLvYY5kLya/QHP5jU0mHX
ZMPD4nAryhs5cX1uIXBju7ImgbXQAjcKB06UhMRI8JawYgrlQ+sam/Pjh+n/1iEw
Uw15O7z7amQODG0SjOcKTOzNSfQ1BB6yMX6kvgjjggJxJkb22luKh/oP2qsn/lCZ
mgoenUHSOxKWMl/EyaYo1KHAuVb9I0V3LgDiGDkwrZmIpKCrQDl7LWMWVd6DGVrx
XOSuzVP58g==
=fJd9
-END PGP SIGNATURE End Message ---

Bug#883636: stretch update for showq

[Jaromír Mikeš]

On Wed, Mar 14, 2018, 6:47 PM Adrian Bunk  wrote:

> On Tue, Jan 02, 2018 at 05:36:06PM +, Debian Bug Tracking System wrote:
> >...
> >  showq (0.4.1+git20161215~dfsg0-3) unstable; urgency=medium
> >...
> >* Hack prefix to get app started. (Closes: #883636)
> >  Thanks to James Cowgill 
> >...
>
> Thanks a lot for fixing this bug for unstable.
>
> It is still present in stretch, could you also fix it there?
> Alternatively, I can fix it for stretch if you don't object.
>

Please go ahead. I don't object.

best

mira

>

Bug#884542: marked as done (prometheus-mysqld-exporter FTBFS: FAIL: TestScrapeInnodbMetrics)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 04:04:14 +
with message-id 
and subject line Bug#884542: fixed in prometheus-mysqld-exporter 
0.10.0+git20180201.a71f4bb+ds-1
has caused the Debian Bug report #884542,
regarding prometheus-mysqld-exporter FTBFS: FAIL: TestScrapeInnodbMetrics
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.)


-- 
884542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prometheus-mysqld-exporter
Version: 0.9.0+ds-3
Severity: serious
Tags: buster sid

Some recent change in unstable makes prometheus-mysqld-exporter FTBFS:

https://tests.reproducible-builds.org/debian/history/prometheus-mysqld-exporter.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus-mysqld-exporter.html

...
=== RUN   TestScrapeInnodbMetrics
--- FAIL: TestScrapeInnodbMetrics (0.00s)
info_schema_innodb_metrics_test.go:17: no such flag -log.level
--- End Message ---
--- Begin Message ---
Source: prometheus-mysqld-exporter
Source-Version: 0.10.0+git20180201.a71f4bb+ds-1

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated 
prometheus-mysqld-exporter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Mar 2018 03:07:26 +
Source: prometheus-mysqld-exporter
Binary: prometheus-mysqld-exporter
Architecture: source
Version: 0.10.0+git20180201.a71f4bb+ds-1
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packaging Team 

Changed-By: Martín Ferrari 
Description:
 prometheus-mysqld-exporter - Prometheus exporter for MySQL server.
Closes: 848481 884542
Changes:
 prometheus-mysqld-exporter (0.10.0+git20180201.a71f4bb+ds-1) unstable; 
urgency=high
 .
   * Team upload.
 .
   [ Filippo Giunchedi ]
   * Suggest default-mysql-server | virtual-mysql-server (Closes: #848481)
 .
   [ Martín Ferrari ]
   * debian/control: Update package name for client-golang.
   * debian/control: Update Standards-Version (no changes).
   * debian/control: Fix Vcs-* fields.
   * debian/control: Replace golang-go with golang-any in Build-Depends.
   * debian/control: Mark package as autopkgtest-able.
   * debian/rules: Replace DH_GOPKG with XS-Go-Import-Path.
   * debian/rules: Replace dpkg-parsechangelog with /usr/share/dpkg/pkg-info.mk
 and simplify.
   * New upstream release/git snapshot. Closes: #884542.
   * debian/control: Require latest go-sqlmock, as tests fail otherwise.
   * debian/rules: Fix dh_auto_install parameters.
   * debian/control: Automated cme fixes.
   * debian/control: Update debhelper compat.
   * debian/copyright: Add Files-Excluded to match repackaging.
   * Remove unneeded lintian override.
   * debian/doc: Refresh.
Checksums-Sha1:
 06d28a408934cf0e9be182c7183a08d09e2b4411 2850 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1.dsc
 7b3573bf9f893f8e7f121112de8777bce705e79b 48085 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds.orig.tar.gz
 83a41b33ef8371fe0d65a0e0f62e4a2a77a74123 5460 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1.debian.tar.xz
 8ec83d474815ac2de875b6c18be34ce1b2b87ffa 8640 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1_amd64.buildinfo
Checksums-Sha256:
 c599d99fc720ea3e7936d43716400b01ece97e2d078f144d6b129306a42b79a7 2850 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1.dsc
 6b648efbc580fe0b3232d6e8e0cb9f96a9157737e574344b6ef6c0614794500b 48085 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds.orig.tar.gz
 8adf24d774594d72041a1ed33af85d4831d9dc00823d02aec8372f6ea3b839a8 5460 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1.debian.tar.xz
 d63b8f58eef89b40899374160b13b3996205c86c8b183144f07b265581957249 8640 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1_amd64.buildinfo
Files:
 

Bug#884542: Pending fixes for bugs in the prometheus-mysqld-exporter package

[pkg-go-maintainers]

tag 884542 + pending
thanks

Some bugs in the prometheus-mysqld-exporter package are closed in
revision d5f1611c81992321eb63d2f3eba13fd10d49886e in branch
'debian/sid' by Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/prometheus-mysqld-exporter.git/commit/?id=d5f1611

Commit message:

New upstream release/git snapshot. Closes: #884542.

Processed: Pending fixes for bugs in the prometheus-mysqld-exporter package

[Debian Bug Tracking System]

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

> tag 884542 + pending
Bug #884542 [src:prometheus-mysqld-exporter] prometheus-mysqld-exporter FTBFS: 
FAIL: TestScrapeInnodbMetrics
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#890893: marked as done (appstream-glib FTBFS: error: redefinition of ‘glib_autoptr_cleanup_GCabCabinet’)

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 02:50:04 +
with message-id 
and subject line Bug#890893: fixed in appstream-glib 0.7.7-1
has caused the Debian Bug report #890893,
regarding appstream-glib FTBFS: error: redefinition of 
‘glib_autoptr_cleanup_GCabCabinet’
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.)


-- 
890893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: appstream-glib
Version: 0.7.4-1
Severity: serious

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

...
FAILED: libappstream-glib/appstream-glib@sha/as-store-cab.c.o 
cc  -Ilibappstream-glib/appstream-glib@sha -Ilibappstream-glib 
-I../libappstream-glib -Ilibappstream-glib/.. -I../libappstream-glib/.. 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/libgcab-1.0 -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 
-I/usr/include/uuid -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 
-std=c99 -D_XOPEN_SOURCE=500 -DAS_COMPILATION -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
'-DG_LOG_DOMAIN="As"' -MMD -MQ 
'libappstream-glib/appstream-glib@sha/as-store-cab.c.o' -MF 
'libappstream-glib/appstream-glib@sha/as-store-cab.c.o.d' -o 
'libappstream-glib/appstream-glib@sha/as-store-cab.c.o' -c 
../libappstream-glib/as-store-cab.c
In file included from 
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9:0,
 from /usr/include/glib-2.0/glib/gtypes.h:32,
 from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/libgcab-1.0/libgcab/gcab-cabinet.h:24,
 from /usr/include/libgcab-1.0/libgcab.h:23,
 from ../libappstream-glib/as-store-cab.c:24:
/usr/include/glib-2.0/glib/gmacros.h:430:43: error: redefinition of 
‘glib_autoptr_cleanup_GCabCabinet’
 #define _GLIB_AUTOPTR_FUNC_NAME(TypeName) glib_autoptr_cleanup_##TypeName
   ^
/usr/include/glib-2.0/glib/gmacros.h:444:22: note: in expansion of macro 
‘_GLIB_AUTOPTR_FUNC_NAME’
   static inline void _GLIB_AUTOPTR_FUNC_NAME(TypeName) (TypeName **_ptr) { if 
(*_ptr) (func) (*_ptr); } \
  ^~~
../libappstream-glib/as-store-cab.c:32:1: note: in expansion of macro 
‘G_DEFINE_AUTOPTR_CLEANUP_FUNC’
 G_DEFINE_AUTOPTR_CLEANUP_FUNC(GCabCabinet, g_object_unref)
 ^
/usr/include/glib-2.0/glib/gmacros.h:430:43: note: previous definition of 
‘glib_autoptr_cleanup_GCabCabinet’ was here
 #define _GLIB_AUTOPTR_FUNC_NAME(TypeName) glib_autoptr_cleanup_##TypeName
   ^
/usr/include/glib-2.0/glib/gmacros.h:436:22: note: in expansion of macro 
‘_GLIB_AUTOPTR_FUNC_NAME’
   static inline void _GLIB_AUTOPTR_FUNC_NAME(ModuleObjName) (ModuleObjName 
**_ptr) { \
  ^~~
/usr/include/glib-2.0/gobject/gtype.h:1401:3: note: in expansion of macro 
‘_GLIB_DEFINE_AUTOPTR_CHAINUP’
   _GLIB_DEFINE_AUTOPTR_CHAINUP (ModuleObjName, ParentName) 
  \
   ^~~~
/usr/include/libgcab-1.0/libgcab/gcab-cabinet.h:38:1: note: in expansion of 
macro ‘G_DECLARE_FINAL_TYPE’
 G_DECLARE_FINAL_TYPE(GCabCabinet, gcab_cabinet, GCAB, CABINET, GObject)
 ^~~~
--- End Message ---
--- Begin Message ---
Source: appstream-glib
Source-Version: 0.7.7-1

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated appstream-glib package)

Bug#892891: marked as done (chromium: FTBFS: error: invalid application of 'sizeof' to incomplete type 'policy::ConfigurationPolicyProvider')

[Debian Bug Tracking System]

Your message dated Thu, 15 Mar 2018 01:37:24 +
with message-id 
and subject line Bug#892891: fixed in chromium-browser 65.0.3325.146-4
has caused the Debian Bug report #892891,
regarding chromium: FTBFS: error: invalid application of 'sizeof' to incomplete 
type 'policy::ConfigurationPolicyProvider'
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.)


-- 
892891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 65.0.3325.146-3

65.0.3325.146-3 was never uploaded.
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 65.0.3325.146-4

We believe that the bug you reported is fixed in the latest version of
chromium-browser, 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.
Michael Gilbert  (supplier of updated chromium-browser 
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: Thu, 15 Mar 2018 01:22:51 +
Source: chromium-browser
Binary: chromium chromium-l10n chromium-shell chromium-widevine chromium-driver 
chromium-common
Architecture: source
Version: 65.0.3325.146-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Maintainers 

Changed-By: Michael Gilbert 
Description:
 chromium   - web browser
 chromium-common - web browser - common resources used by the chromium packages
 chromium-driver - web browser - WebDriver support
 chromium-l10n - web browser - language packs
 chromium-shell - web browser - minimal shell
 chromium-widevine - web browser - widevine content decryption support
Closes: 892891
Changes:
 chromium-browser (65.0.3325.146-4) unstable; urgency=medium
 .
   * Fix another incomplete type build error (closes: #892891).
Checksums-Sha1:
 ba4b98418625dc736deec181069c2309ab8fcb89 4319 
chromium-browser_65.0.3325.146-4.dsc
 6aabb251eccb0731c524513f10b28977692093cd 142836 
chromium-browser_65.0.3325.146-4.debian.tar.xz
 84f8bc5738cdf7e554355dda446663010ecd5361 18997 
chromium-browser_65.0.3325.146-4_source.buildinfo
Checksums-Sha256:
 4a440666fab6642882092c2b933eb202795be841f45e5b8589dce4682f75006c 4319 
chromium-browser_65.0.3325.146-4.dsc
 5ad5ccf83b1fde491721712322e37454745ba386d06cf4af50633be865999846 142836 
chromium-browser_65.0.3325.146-4.debian.tar.xz
 1d9fa7f4ebb4b1bc54d0b7adba602afeb870e3c603d48b86d2a26398696413f3 18997 
chromium-browser_65.0.3325.146-4_source.buildinfo
Files:
 7790a6b9be11c2073878f43ab8ed9fdf 4319 web optional 
chromium-browser_65.0.3325.146-4.dsc
 484f846f49a7a1e759dc8132e8782620 142836 web optional 
chromium-browser_65.0.3325.146-4.debian.tar.xz
 c75e3e49a858f024c9b71331a06d98ac 18997 web optional 
chromium-browser_65.0.3325.146-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEluhy7ASCBulP9FUWuNayzQLW9HMFAlqpy7YACgkQuNayzQLW
9HN/XiAAqUr2IY0RfaIX4id3tZ1jlzy685VzNKP8/PICoiIhy9PXNmgnLRKmqNn7
q1l3VhVmfmI86JaDzkW+phbnqTCipzTFf44xhMg9endVI3nKGhXpltzwIaXl0gRY
SL6xkHJxpO97WDnfPNssQ5e0Zp0wdfrYHpLkMWik76RP28N2/gqxx7iAaUpgU/9A
25JPD6LGnoTs1Dh5oaEQqzfJtJYwTFPr2g8F36b6RSrVHa2qhZ4B/nVCkPSSLPft
xJCcQlj1JvMmJ0gkB16dzWsg1lxX21O8rAJCKmNh1i9M8Lt582oB3JQZkh/0lWOH
Ri3pAI86kFFd5cd0HRX0G+y9qAX6pBOKTb7JsIf5/sklngOeq/dpOcQzLzCuRslS
WJwG0mJ6M3f42VVFmwhI8aNW2uXyj+HAY4tmFYg+PJokXfQlW3M2L2DItptx+eUw
R6jO2rLHPSziux9UvB/ZK3v/j6tZOQpU3teb9pbSHXLzrGq0ws6yluCRo5sX3NwA
/ytBNELtlcxzy8xI9YCdLDzyZdy28NnMjY2b1tlg2bYKCD2fZQ2cR4rZAnkjY+go
IIG8j9qGJnFLxITRVs1e+je4rwlnbGNsa5mphAnVVbfMfpg7dbxTKWM6MX8F/P0F
wBROAK84kUnEEt2EUy6uymzeAgfBZNb4aD5X9BSB7lPmOhrsEPWCAfOleiUfBiBe
K6LLEYmuECBvI6g2Yw926Nw/KVhVC9ZxIEF7OkDBNCLnTOXybFqK+aJpvCGwd827
gKS3GZ5Daob2uTq1BS+vnw0bfFwqOT+9qQ47700NtFRFX8Zm+doYrf2H+6XDuenT
f6zrTKQsQoE84DKLllmlrNtgzbhjRXtV7vv26UUTb0AdDT91Wntcuk3OxZFuTHN/
Evpdz5eKjFxAN2VMBNYTgPJ7bJK68OguSpgeiH/S5JEmIvF2E0RzR2+tu+eow+7b
v1TctU9UPvqOZ3z4yZy5v+Oen6D/4Qz5XrEU/mFpwqDg9zCKKGDmTGSzgbjycT3B
sH9l9F6zN6wMghulueU5cuoQEW/8Jt5hizDJ47PUdeZsCGPZSz2n4sruAhFpgsm6

Bug#890430: make: warning: -jN forced in submake: disabling jobserver mode.

[Andreas Beckmann]

On Fri, 16 Feb 2018 14:34:40 +0100 Aurelien Jarno 
wrote:
> This problem also affects the build daemons, the build of the linux
> package is much longer now on the architectures where make-dfsg does not
> FTBFS. The linux package indeed builds in parallel by using the
> MAKEFLAGS variable. I guess other packages are also affected. I am
> therefore raising the severity of this bug, we do not want such
> regression in testing.

This also affects openjdk-10 (and probably the other openjdk-* as well):
https://bugs.debian.org/891573
There the result was a unlimited-parallel build (something like
make -j), I noticed because the machine became unresponsive for
interactive use because the load suddenly went above 400 and it started
to swap ...


Andreas

Bug#892971: libignition-fuel-tools1-{1,dev}: both ship /usr/lib/ruby/ignition/cmdfuel1.rb

[Andreas Beckmann]

Package: libignition-fuel-tools1-dev,libignition-fuel-tools1-1
Version: 1.0.0+dfsg4-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

  Selecting previously unselected package libignition-fuel-tools1-dev:amd64.
  Preparing to unpack 
.../35-libignition-fuel-tools1-dev_1.0.0+dfsg4-3_amd64.deb ...
  Unpacking libignition-fuel-tools1-dev:amd64 (1.0.0+dfsg4-3) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ADbRwA/35-libignition-fuel-tools1-dev_1.0.0+dfsg4-3_amd64.deb
 (--unpack):
   trying to overwrite '/usr/lib/ruby/ignition/cmdfuel1.rb', which is also in 
package libignition-fuel-tools1-1:amd64 1.0.0+dfsg4-3
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-ADbRwA/35-libignition-fuel-tools1-dev_1.0.0+dfsg4-3_amd64.deb


cheers,

Andreas

Bug#890997: marked as done (boxbackup FTBFS on i386: test failures)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 23:34:36 +
with message-id 
and subject line Bug#890997: fixed in boxbackup 0.13~~git20180313.g16a11e86-1
has caused the Debian Bug report #890997,
regarding boxbackup FTBFS on i386: test failures
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.)


-- 
890997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boxbackup
Version: 0.13~~git20180102.g6d7e9562-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=boxbackup=i386=0.13~~git20180102.g6d7e9562-1=1519188957=0

...
common: PASSED
crypto: PASSED
compress: PASSED
raidfile: FAILED: Exception caught: OSError
basicserver: PASSED
backupstore: PASSED
backupstorefix: PASSED
backupstorepatch: PASSED
backupdiff: PASSED
bbackupd: FAILED: 2 tests failed (first at :0)
s3store: PASSED
httpserver: PASSED

One or more tests have failed. Please check the following common causes:

* Check that no instances of bbstored or bbackupd are already running
  on this machine.
* Make sure there isn't a firewall blocking incoming or outgoing connections
  on port 2201.
* Check that there is sufficient space in the filesystem that the tests
  are being run from (at least 1 GB free).
* The backupdiff test fails if it takes too long, so it's sensitive to
  the speed of the host and your connection to it.

After checking all the above, if you still have problems please contact
us on the mailing list, boxbac...@boxbackup.org. Thanks!
debian/rules:32: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: boxbackup
Source-Version: 0.13~~git20180313.g16a11e86-1

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated boxbackup package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Mar 2018 08:19:09 -0400
Source: boxbackup
Binary: boxbackup-server boxbackup-client
Architecture: i386 source
Version: 0.13~~git20180313.g16a11e86-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Reinhard Tartler 
Closes: 890997
Description: 
 boxbackup-client - client for the BoxBackup remote backup system
 boxbackup-server - server for the BoxBackup remote backup system
Changes:
 boxbackup (0.13~~git20180313.g16a11e86-1) unstable; urgency=medium
 .
   * New upstream pre-release (requested by upstream)
   * Fixes test failures on i386 (closes: #890997)
Checksums-Sha1: 
 831ffee0ac08622d90dd7a30ff56b681364b1605 2402 
boxbackup_0.13~~git20180313.g16a11e86-1.dsc
 ff98f18fc90af033749b303b79c123f165d3bb3f 2131640 
boxbackup_0.13~~git20180313.g16a11e86.orig.tar.gz
 24368bca2eebb3a6535a44af525b86df9d0f128b 63568 
boxbackup_0.13~~git20180313.g16a11e86-1.debian.tar.xz
 770f4b66e685dbf5c87edce890f6ef1ccdf35613 17168060 
boxbackup-client-dbgsym_0.13~~git20180313.g16a11e86-1_i386.deb
 74d08dfb857cdb6a7b1f311266e6bc3e705918d2 1503328 
boxbackup-client_0.13~~git20180313.g16a11e86-1_i386.deb
 8858ec65c1dcc812ca92144d18f46265ebac44bd 13955328 
boxbackup-server-dbgsym_0.13~~git20180313.g16a11e86-1_i386.deb
 0fad068cb2135c12666f4f98e6424aea0dcd3a68 1282272 
boxbackup-server_0.13~~git20180313.g16a11e86-1_i386.deb
 edb29fb4d55f4234e99922565c29032561169f99 11545 
boxbackup_0.13~~git20180313.g16a11e86-1_i386.buildinfo
Checksums-Sha256: 
 3016fe4ffb423eecca4c4b03e534dd17d2efe8b53cd86c7a07cd7b81cf07b150 2402 
boxbackup_0.13~~git20180313.g16a11e86-1.dsc
 9ac1e9119cd7ec515e931e59db45f4edff28b3edb259a50045c24eb161e86a70 2131640 
boxbackup_0.13~~git20180313.g16a11e86.orig.tar.gz
 ad18750630e60a279c11863139a3cd24e9259aff4fbab24918d5c99f2f96a0d3 63568 
boxbackup_0.13~~git20180313.g16a11e86-1.debian.tar.xz
 4a2b01bc3e36dc2529e870d0f527e518c379fd6e795e5800ce3d90b61fbbfe6d 17168060 
boxbackup-client-dbgsym_0.13~~git20180313.g16a11e86-1_i386.deb
 

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

[Francisco J. Blanco]

Package: netbeans
Version: 8.2+dfsg1-1
Followup-For: Bug #891957

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Versions of packages netbeans depends on:
ii  default-jdk [java8-sdk]2:1.8-59
ii  libnb-apisupport3-java 8.2+dfsg1-1
ii  libnb-ide14-java   8.2+dfsg1-1
ii  libnb-java5-java   8.2+dfsg1-1
ii  libnb-platform18-java  8.2+dfsg1-1
ii  openjdk-8-jdk [java8-sdk]  8u151-b12-1

netbeans recommends no packages.

netbeans suggests no packages.

-- no debconf information


Hi,

As Patrick suggests, downgrading libequinox-osgi-java to stable version 
(3.8.1-10) fixed the problem.

Now Netbeans is starting normally.

Regards.

Bug#892723: marked as done (dehydrated: Dehydrated broken in stable due to unhandled redirect)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 22:17:08 +
with message-id 
and subject line Bug#892723: fixed in dehydrated 0.3.1-3+deb9u2
has caused the Debian Bug report #892723,
regarding dehydrated: Dehydrated broken in stable due to unhandled redirect
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.)


-- 
892723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dehydrated
Version: 0.3.1-3+deb9u1
Severity: normal

Since recently, updating a cert no longer works. The challenge works, and the 
new cert is created, but creating the cert chain fails:

...
 + Creating fullchain.pem...
   + ERROR: An error occurred while sending get-request to 
http://cert.int-x3.letsencrypt.org/ (Status 301)
...

The new cert is consequently not "actived" by symlinks, and the deploy scripts 
are not run.
The reason is a new redirect at Let's Encrypt, and curl does not follow 
redirects unless the "-L" switch is given.

This was fixed upstrem by 


Arne

-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-6-686-pae (SMP w/1 CPU core)
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), 
LANGUAGE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages dehydrated depends on:
ii  ca-certificates  20161130+nmu1
ii  curl 7.52.1-5+deb9u4
ii  openssl  1.1.0f-3+deb9u1

dehydrated recommends no packages.

dehydrated suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dehydrated
Source-Version: 0.3.1-3+deb9u2

We believe that the bug you reported is fixed in the latest version of
dehydrated, 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.
Mattia Rizzolo  (supplier of updated dehydrated 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, 12 Mar 2018 11:48:10 +0100
Source: dehydrated
Binary: dehydrated dehydrated-apache2 letsencrypt.sh letsencrypt.sh-apache2
Architecture: source
Version: 0.3.1-3+deb9u2
Distribution: stretch
Urgency: medium
Maintainer: Debian Let's Encrypt 
Changed-By: Mattia Rizzolo 
Description:
 dehydrated - ACME client implemented in Bash
 dehydrated-apache2 - dehydrated challenge response support for Apache2
 letsencrypt.sh - ACME client - transitional dummy package to dehydrated
 letsencrypt.sh-apache2 - letsencrypt.sh support for Apache2 - transitional 
dummy package
Closes: 892723
Changes:
 dehydrated (0.3.1-3+deb9u2) stretch; urgency=medium
 .
   * Add patch from upstream to follow redirects on HTTP GET.
 This fixes an error when creating the fullchain.pem after the LE API
 introduced a new redirect.  Closes: #892723
Checksums-Sha1:
 d5082e750002453857637a9c1c971b5c59c74c91 2495 dehydrated_0.3.1-3+deb9u2.dsc
 3f1ac4ef433daabe6867acfb08e2f3318d08bae5 17264 
dehydrated_0.3.1-3+deb9u2.debian.tar.xz
Checksums-Sha256:
 b37a4c775e48876e72de7823a16a38efd4b233c96e33faf2eaa567b8bf4dba4d 2495 
dehydrated_0.3.1-3+deb9u2.dsc
 152fe28fba8c80c74fbd76547300886faaf2c02f868d17515766ae315e908af3 17264 
dehydrated_0.3.1-3+deb9u2.debian.tar.xz
Files:
 28a3ad777ffc090bc892cc6318f80caf 2495 misc optional 
dehydrated_0.3.1-3+deb9u2.dsc
 c35947c8ad5764fb68843df962a10dff 17264 misc optional 
dehydrated_0.3.1-3+deb9u2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlqoBoIACgkQCBa54Yx2
K61VFg//cjKs0RrJCXVgMohkjRBT9pyk68i5VoZuqt736TUr8YWpWkxokEkYosK1
SLd4j5Nu0pz416kThGHnDPtRu1KpffmIIwCW6a0M2n7+0F68pWlyr6adEvh/H+aA
apm1w88/Ai1BRKmoemCYccGTAI0Z1mX9gTwv5SAnPXdR/NppPMgCgKlwLm15YJrf
ccOpJSaXzWIROFcD8/dtU49TUbuZfA3KO8woxgeJMFTnw6MupPnx8zyKpkGSqHhe

Bug#886120: doxygen = scapegoat ?

[Adam Borowski]

On Wed, Mar 14, 2018 at 09:34:36PM +0100, Paolo Greppi wrote:
> @kilobyte, let me see if I can understand your purpose with this bug report.
> 
> What happened is:
> 1) you find a serious bug in ctpp2 (popcon: 14)
> 2) you decide it's RC
> 3) it's doxygen fault so you reassign it to doxygen (popcon: 8381), and it 
> stays RC
> 
> Now let's look at the effect of all this:
> 1) doxygen is currently orphaned (https://bugs.debian.org/888580)
> 2) therefore nobody will take care of this unless someone adopts it
> 3) the average Johanna trying to decide whether she should adopt it will
>be repelled by this RC bug and the perspective that anybody anytime can
>file RC bugs because any obscure package fails to build and it's
>doxygen fault
> 4) consequently doxygen will not make it to buster
> 4) ctpp2-doc is also dropped from stable, and all other packages that
>depend on doxygen for building, which if I am not mistaken are 443:
> 
> grep-dctrl -FBuild-Depends doxygen -sPackage /var/lib/apt/lists/*Sources | wc
> 443 8868612
> 
> Is that your wish ?

Your reasoning is: https://en.wikipedia.org/wiki/Appeal_to_consequences
which is not a reason for dismissing a bug.  It _may_ be a valid reason
for the Release Team to mark the bug as buster-ignore, or to temporarily
reduce its severity, but this won't make it disappear.

The problem is not that random packages sometimes fail to build (not just
ctpp2, but obscure races are pretty hard to reproduce and/or debug).  The
problem is that packages _succeed_ where they shouldn't.

Doxygen turns bugs that usually would be obvious, easy to fix breakage into
random rare failures that appear to build the vast majority of the time. 

And, packages that have enough impact (such as doxygen) are already immune
to autoremoval, which addresses your 4) and 4).

Because of ignoring the failures, we don't know how widespread problems like
misgenerated output that's then (correctly) rejected by graphviz, are.

Only then we'd be able to correctly assess reasonable severities to
individual bugs.  Here, doxygen causes at least one package to FTBFS which
might or might not be RC (we'd know more only once it's no longer leakily
papered over).


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.

Bug#892960: libdrm FTBFS on arm*: symbol differences

[Sven Joachim]

Control: tags -1 + pending

On 2018-03-14 22:44 +0200, Adrian Bunk wrote:

> Source: libdrm
> Version: 2.4.91-1
> Severity: serious
>
> https://buildd.debian.org/status/package.php?p=libdrm=sid
>
> ...
>debian/rules override_dh_makeshlibs
> make[1]: Entering directory '/<>'
> dh_makeshlibs -plibdrm2 -V'libdrm2 (>= 2.4.89)' --add-udeb=libdrm2-udeb -- -c4
> dh_makeshlibs -plibdrm-nouveau2 -V'libdrm-nouveau2 (>= 2.4.66)' -- -c4
> dh_makeshlibs -plibdrm-radeon1 -V'libdrm-radeon1 (>= 2.4.39)' -- -c4
> dh_makeshlibs -plibdrm-amdgpu1 -V'libdrm-amdgpu1 (>= 2.4.90)' -- -c4
> dh_makeshlibs -plibdrm-tegra0 -V'libdrm-tegra0' -- -c4
> dh_makeshlibs -plibdrm-freedreno1 -V'libdrm-freedreno1 (>= 2.4.89)' -- -c4
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: warning: debian/libdrm-freedreno1/DEBIAN/symbols doesn't 
> match completely debian/libdrm-freedreno1.symbols
> --- debian/libdrm-freedreno1.symbols (libdrm-freedreno1_2.4.91-1_arm64)
> +++ dpkg-gensymbolsaJO5I2 2018-03-14 07:53:26.403570801 +
> @@ -7,10 +7,12 @@
>   fd_bo_from_fbdev@Base 0
>   fd_bo_from_handle@Base 0
>   fd_bo_from_name@Base 0
> + fd_bo_get_iova@Base 2.4.91-1
>   fd_bo_get_name@Base 0
>   fd_bo_handle@Base 0
>   fd_bo_map@Base 0
>   fd_bo_new@Base 0
> + fd_bo_put_iova@Base 2.4.91-1
>   fd_bo_ref@Base 0
>   fd_bo_size@Base 0
>   fd_device_del@Base 0
> dh_makeshlibs: failing due to earlier errors
> debian/rules:103: recipe for target 'override_dh_makeshlibs' failed
> make[1]: *** [override_dh_makeshlibs] Error 2

I have added the missing symbols in git, not tested though.

Cheers,
   Sven

Processed: Re: Bug#892960: libdrm FTBFS on arm*: symbol differences

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #892960 [src:libdrm] libdrm FTBFS on arm*: symbol differences
Added tag(s) pending.

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

Bug#892964: mercurial: CVE-2018-1000132

[Salvatore Bonaccorso]

Source: mercurial
Version: 3.1.2-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for mercurial.

CVE-2018-1000132[0]:
| Mercurial version 4.5 and earlier contains a Incorrect Access Control
| (CWE-285) vulnerability in Protocol server that can result in
| Unauthorized data access. This attack appear to be exploitable via
| network connectivity. This vulnerability appears to have been fixed in
| 4.5.1.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-1000132
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000132
[1] 
https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.5.1_.2F_4.5.2_.282018-03-06.29

Regards,
Salvatore

Bug#892849: [3dprinter-general] Bug#892849: Bug#892849: cura: Exception while launching cura

[Gregor Riepl]

> ii  libarcus3  3.1.0-1  amd64    message queue for Cura based on p
> ii  python3-arcus  3.1.0-1  amd64    message queue for Cura based on p
> ii  python3-sip    4.19.8+dfsg- amd64    Python 3/C++ bindings generator r

Thank you.

Unfortunately, I cannot reproduce the problem on my machine, even with these
exact versions from sid installed.
But I'm using a sid/stretch mix, not pure sid, so it may be related to that.

On the other hand, I will submit Cura 3.2.1 soon, so perhaps a new build will
help. I'll keep the bug open until then.
If it still happens with 3.2.1, we'll need to debug this further.

Bug#892960: libdrm FTBFS on arm*: symbol differences

[Adrian Bunk]

Source: libdrm
Version: 2.4.91-1
Severity: serious

https://buildd.debian.org/status/package.php?p=libdrm=sid

...
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/<>'
dh_makeshlibs -plibdrm2 -V'libdrm2 (>= 2.4.89)' --add-udeb=libdrm2-udeb -- -c4
dh_makeshlibs -plibdrm-nouveau2 -V'libdrm-nouveau2 (>= 2.4.66)' -- -c4
dh_makeshlibs -plibdrm-radeon1 -V'libdrm-radeon1 (>= 2.4.39)' -- -c4
dh_makeshlibs -plibdrm-amdgpu1 -V'libdrm-amdgpu1 (>= 2.4.90)' -- -c4
dh_makeshlibs -plibdrm-tegra0 -V'libdrm-tegra0' -- -c4
dh_makeshlibs -plibdrm-freedreno1 -V'libdrm-freedreno1 (>= 2.4.89)' -- -c4
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: debian/libdrm-freedreno1/DEBIAN/symbols doesn't match 
completely debian/libdrm-freedreno1.symbols
--- debian/libdrm-freedreno1.symbols (libdrm-freedreno1_2.4.91-1_arm64)
+++ dpkg-gensymbolsaJO5I2   2018-03-14 07:53:26.403570801 +
@@ -7,10 +7,12 @@
  fd_bo_from_fbdev@Base 0
  fd_bo_from_handle@Base 0
  fd_bo_from_name@Base 0
+ fd_bo_get_iova@Base 2.4.91-1
  fd_bo_get_name@Base 0
  fd_bo_handle@Base 0
  fd_bo_map@Base 0
  fd_bo_new@Base 0
+ fd_bo_put_iova@Base 2.4.91-1
  fd_bo_ref@Base 0
  fd_bo_size@Base 0
  fd_device_del@Base 0
dh_makeshlibs: failing due to earlier errors
debian/rules:103: recipe for target 'override_dh_makeshlibs' failed
make[1]: *** [override_dh_makeshlibs] Error 2

Bug#886120: doxygen = scapegoat ?

[Paolo Greppi]

@kilobyte, let me see if I can understand your purpose with this bug report.

What happened is:
1) you find a serious bug in ctpp2 (popcon: 14)
2) you decide it's RC
3) it's doxygen fault so you reassign it to doxygen (popcon: 8381), and it 
stays RC

Now let's look at the effect of all this:
1) doxygen is currently orphaned (https://bugs.debian.org/888580)
2) therefore nobody will take care of this unless someone adopts it
3) the average Johanna trying to decide whether she should adopt it will be 
repelled by this RC bug and the perspective that anybody anytime can file RC 
bugs because any obscure package fails to build and it's doxygen fault
4) consequently doxygen will not make it to buster
4) ctpp2-doc is also dropped from stable, and all other packages that depend on 
doxygen for building, which if I am not mistaken are 443:

grep-dctrl -FBuild-Depends doxygen -sPackage /var/lib/apt/lists/*Sources | wc
443 8868612

Is that your wish ?

Paolo

Bug#892959: slic3r-prusa FTBFS on 32bit: error: format not a string literal and no format arguments

[Adrian Bunk]

Source: slic3r-prusa
Version: 1.39.1+dfsg-1
Severity: serious

https://buildd.debian.org/status/package.php?p=slic3r-prusa=sid

...
/usr/bin/perl -MExtUtils::XSpp::Cmd -e xspp -- -t 
"/<>/slic3r-prusa-1.39.1+dfsg/xs/xsp/typemap.xspt" 
"/<>/slic3r-prusa-1.39.1+dfsg/xs/xsp/Print.xsp": In function 'void 
XS_Slic3r__Print_output_filepath(PerlInterpreter*, CV*)':
/usr/bin/perl -MExtUtils::XSpp::Cmd -e xspp -- -t 
"/<>/slic3r-prusa-1.39.1+dfsg/xs/xsp/typemap.xspt" 
"/<>/slic3r-prusa-1.39.1+dfsg/xs/xsp/Print.xsp":847:31: error: format 
not a string literal and no format arguments [-Werror=format-security]

Bug#892956: libinput-dev: Requires.private without package dependencies breaks pkg-config users

[Adrian Bunk]

Package: libinput-dev
Version: 1.10.3-1
Severity: grave
Control: affects -1 src:efl src:gnome-twitch src:muffin src:mutter 
src:gnome-shell

https://buildd.debian.org/status/package.php?p=efl=sid

...
configure: error: pkg-config missing libinput >= 0.6.0 xkbcommon >= 0.3.0 
libudev


Root cause are the new dependencies in Requires.private
without package dependencies:

$ pkg-config --cflags  libinput
Package libwacom was not found in the pkg-config search path.
Perhaps you should add the directory containing `libwacom.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libwacom', required by 'libinput', not found
 
$ 

Processed: libinput-dev: Requires.private without package dependencies breaks pkg-config users

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:efl src:gnome-twitch src:muffin src:mutter src:gnome-shell
Bug #892956 [libinput-dev] libinput-dev: Requires.private without package 
dependencies breaks pkg-config users
Added indication that 892956 affects src:efl, src:gnome-twitch, src:muffin, 
src:mutter, and src:gnome-shell

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

Bug#892950: apcupsd FTBFS: python-imaging removed from pillow/5.0.0-1

[Helmut Grohne]

Source: apcupsd
Version: 3.14.14-1
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

apcupsd fails to build from source in unstable. Its Build-Depends are no
longer satisfiable, because python-imaging was removed from
pillow/5.0.0-1.

Helmut

Processed: severity of 892945 is normal

[Debian Bug Tracking System]

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

> severity 892945 normal
Bug #892945 [libvirt-daemon] Cannot start domain using user session
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#890465: marked as done (pioneers: Depends on libgnome)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 19:20:21 +
with message-id 
and subject line Bug#890465: fixed in pioneers 15.5-1
has caused the Debian Bug report #890465,
regarding pioneers: Depends on libgnome
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.)


-- 
890465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pioneers
Version: 15.4-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnome
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.

pioneers Build-Depends on libgnome2-dev (which adds a libgnome2-0
Depends). That seems wrong because libgnome is a gtk2 library but
pioneers is built with gtk3.

Without that build dependency, pioneers doesn't offer user help which
seems really wrong.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: pioneers
Source-Version: 15.5-1

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

Debian distribution maintenance software
pp.
Roland Clobus  (supplier of updated pioneers package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Mar 2018 17:44:00 +0100
Source: pioneers
Binary: pioneers pioneers-console pioneers-metaserver pioneers-data 
pioneers-console-data
Architecture: source all amd64
Version: 15.5-1
Distribution: unstable
Urgency: medium
Maintainer: Roland Clobus 
Changed-By: Roland Clobus 
Description:
 pioneers   - Settlers of Catan board game
 pioneers-console - Settlers of Catan board game - console parts
 pioneers-console-data - Settlers of Catan board game - data files for console 
parts
 pioneers-data - Settlers of Catan board game - data files
 pioneers-metaserver - Settlers of Catan board game - metaserver
Closes: 885613 890465
Changes:
 pioneers (15.5-1) unstable; urgency=medium
 .
   * New upstream release.
   * pioneers-builddep updated.
   * Removed dependency on libgnome (closes: #890465)
   * Removed dependency on scrollkeeper (closes: #885613)
   * Added dependency on autoconf-archive.
   * Added dependency on yelp-tools.
   * Applied 'wrap-and-sort' to all debian/* files.
   * Removed dependency on netpbm.
   * Removed menu file, FreeDesktop desktop entries are provided.
   * Changed compat level to 11.
   * Use secure URL for the source code and copyright file.
   * Upgrade standards version to 4.1.3.
   * Removed package transitions since 15.1-1.
Checksums-Sha1:
 ef7500c3115c6c320122a5f32478fa722519bb05 2369 pioneers_15.5-1.dsc
 6738c308d3a9f31e7c3ac047c83249ebe3650c65 4975627 pioneers_15.5.orig.tar.gz
 c39039a30ee2eadc8e4e5a46d69e896e32aabd92 29932 pioneers_15.5-1.debian.tar.xz
 a1ff7a92dc2a629ff3821433a76edcf9411efcfb 230956 
pioneers-console-data_15.5-1_all.deb
 bd088d883b31a5b90514a9342a6a55442051ee55 703700 
pioneers-console-dbgsym_15.5-1_amd64.deb
 998810aa9158203d98a7372c6bbf0c081f7396c1 195100 
pioneers-console_15.5-1_amd64.deb
 6a4b835cc617316dddb284e981851e49aeb1333e 2868000 pioneers-data_15.5-1_all.deb
 b500d843f2da18bdfd7bb0abefa47745a39a2de0 2082836 
pioneers-dbgsym_15.5-1_amd64.deb
 744fb82a401781b2a46f0a2fbf1f4b84a701707a 196028 
pioneers-metaserver-dbgsym_15.5-1_amd64.deb
 30f6d8efb88a90e86701c2d4e3cfb05e4ad57340 121156 
pioneers-metaserver_15.5-1_amd64.deb
 bacce2e4de2f53df1d61571298df14df730cfb04 17201 pioneers_15.5-1_amd64.buildinfo
 b7c617a867b53a0923aeb4c237d7851bf2d5d7a1 300136 pioneers_15.5-1_amd64.deb
Checksums-Sha256:
 972683e388cae56a5d4b0d32ccb8676ca6fbacc81ccfb18c496652002a892ad3 2369 
pioneers_15.5-1.dsc
 3ee1415e7c48dc144fbdb99105a6ef8a818e67ed34e9d0f8e01224c3636cef0c 4975627 
pioneers_15.5.orig.tar.gz
 

Bug#886044: syncmaildir: raising severity of gconf dependency bug

[gregor herrmann]

On Wed, 14 Mar 2018 09:55:36 +0100, Enrico Tassi wrote:

> > Looking at the ChangeLog and the git history, it seems that gconf has
> > been replaced by gsettings already in 1.2.6.
> > Grepping through the code shows two leftovers, the build dependency in
> > debian/control, and a mentioning in PKGS_VALA in Makefile.
> > 
> > If I remove those two pieces, the package builds and the Depends line
> > of the syncmaildir-applet binary package loses gconf-service and
> > libgconf-2-4.
> > 
> > Patch (git diff against master) attached.
> > 
> > Enrico, do you have time to work on this? Otherwise I'm happy to
> > make an upload based on this diff.
> 
> Many thanks for the work!

You're welcome.
 
> I was planning to do a new release (I'm also the upstream, and I have a
> couple of pending fixes) and the do the upload fixing the gconf issue.

That's good news!
 
> I'm very busy so can't guarantee I'll manage to do it promptly, so if
> it helps please do an NMU (and I'll wait the migration to testing before
> doing my upload, in case I manage to release quickly).

I'm not sure about the timeline for the gconf removal (cc'ing jbicha)
but I guess it can wait a bit, and would save some work.

In case Jeremy indicates a high urgency I'm happy to to this minimal
NMU in between.


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: Bruce Springsteen: Bobby Jean


signature.asc
Description: Digital Signature

Bug#892375: marked as done (isl: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 18:51:28 +
with message-id 
and subject line Bug#892375: fixed in isl 0.19-1
has caused the Debian Bug report #892375,
regarding isl: Incomplete debian/copyright?
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.)


-- 
892375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: isl
Version: 0.19-1~exp2
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Matthias Klose 

Hi,

I just ACCEPTed isl from NEW but noticed it was missing attribution 
in debian/copyright for at least imath/imath.c, interface/isl_test_python.py
etc.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: isl
Source-Version: 0.19-1

We believe that the bug you reported is fixed in the latest version of
isl, 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.
Matthias Klose  (supplier of updated isl 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: Fri, 09 Mar 2018 09:44:38 +0700
Source: isl
Binary: libisl-dev libisl19
Architecture: source
Version: 0.19-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Description:
 libisl-dev - manipulating sets and relations of integer points bounded by line
 libisl19   - manipulating sets and relations of integer points bounded by line
Closes: 892375
Changes:
 isl (0.19-1) unstable; urgency=medium
 .
   * New upstream release.
   * Update debian/copyright. Closes: #892375.
   * Stop building the debug package, move the pretty printers to the library
 package.
   * Bump the libisl soname.
Checksums-Sha1:
 6e3d57d5559c9847dc12da67fec127ff15e05066 1833 isl_0.19-1.dsc
 88048de4db814bcc31103b8d5bc9c02b75c8f7e1 22388 isl_0.19-1.debian.tar.xz
 8ef370c9e59ad87d05737afd42744986d9aedc09 5583 isl_0.19-1_source.buildinfo
Checksums-Sha256:
 f9786677430e2ea7295c6ad9480e7e710582f84b5b850a5ddfe1f21b3d726b0f 1833 
isl_0.19-1.dsc
 aa034a5700c63867aae836a1f985fccc50ccacd1abe57a2a016e076fa745feb0 22388 
isl_0.19-1.debian.tar.xz
 0f5176e91f77a3969c985ce83cfd2a37f6cdea15f1a6409ad218365e340899ae 5583 
isl_0.19-1_source.buildinfo
Files:
 13984450b8bf9f80e17dd8ad1701c991 1833 libs optional isl_0.19-1.dsc
 14e4086edb06ea6f7e23973d0801e80f 22388 libs optional isl_0.19-1.debian.tar.xz
 14f1075f22fcea78f3cfde3cc8498717 5583 libs optional isl_0.19-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlqpa24QHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9XqpD/4jmTQ1hnV4HAwBiZ1PXseCYci3zwNrrJPF
g5Z7ytCQZE428fXJtt/GSCb18N7aJbq9gxwHSWujhNLB+f9aohSw3KSMGi25ZXNZ
QvMM0PzW6a7ZYAiOZ/8vRLnZlg/N1G/vXyiMr7ouzAUt6ILDhFrFmDSCGYBMJEQg
0vgzAOZtnWPv0QZTuNYY++oK5X/MmYKhTzfqgS1UKixkrjHNJrbLB8aQRNpZ4Ogx
UTHi9AvL9XOq1o/KHDrmer4SUWaD5QXn5lTic+Hgj1s77OXRf9Q2PRvq85w9UucW
gMnoi3+5gs7B6kvfFDnkkbTFYUxhXtYQnvmIqZ6WS+OwrNMF79VWdaXvOuNyCTho
5EFgxMA/s/l+Ec3fRnz/wQAw/2cdjU8Ws5Y13/E9Yt7R8uKxoohagy4VeUxWADhX
1XBA+fbqwgpTDV59AkMpLQx+cTCOR5dcxvPyw06Zo9j7WBer9g1hsUUsXM3TCAup
lahRSzZlZJdjC3N8ubVqUMgibsW1EtwBLbyqInW9lhdWG69GZAYJEbvqZnAsJVc2
H5TOBP7VvDnkT6CTce1eMrbNN0sf/g2sEoKmoTSZXoY1ewqTHXDKZuPL2W0PUAqj
6KCLt3I5NWY0GkWeb/NUQFLJSfHsV7hFTNN/mRiXSUDzkSGYP7GUykM4bGs+Dt7L
dFU+Gnonjg==
=eFZf
-END PGP SIGNATURE End Message ---

Bug#886532: Coming updates for meltdown/spectre

[Laurent Bigonville]

On Sun, 7 Jan 2018 12:11:17 + Nigel Kukard  wrote:
>
> Is it going to be possible to include this patch in qemu please?
>
> https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg00811.html
>
>
> ref: https://www.qemu.org/2018/01/04/spectre/
>

FTR this seems to be part of 2.11.1, would be nice to be fixed in 
unstable at least


I don't know if there are backports for this patch for the 2.8 branch 
used in stable

Bug#892799: Bug #892799 in libtgvoip marked as pending

[guriev-ns]

Control: tag -1 pending

Hello,

Bug #892799 in libtgvoip 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/debian/libtgvoip/commit/85ad7e8a3ba4887d696913b93f41e36bf667098f


Clarify copyright notices about WebRTC code

Closes: #892799



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892799

Processed: Bug #892799 in libtgvoip marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892799 [src:libtgvoip] libtgvoip: Incomplete debian/copyright?
Added tag(s) pending.

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

Bug#892945: Cannot start domain using user session

[Laurent Bigonville]

Package: libvirt-daemon
Version: 4.0.0-2
Severity: serious

Hi,

I cannot start a domain using a libvirt user session. I'm getting the following 
message:

Impossible de terminer l’installation : « internal error: process exited while 
connecting to monitor: Could not access KVM kernel module: Permission denied
2018-03-14T18:32:12.683550Z qemu-system-x86_64: failed to initialize KVM: 
Permission denied »

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/create.py", line 2545, in 
_do_async_install
guest.start_install(meter=meter)
  File "/usr/share/virt-manager/virtinst/guest.py", line 498, in start_install
doboot, transient)
  File "/usr/share/virt-manager/virtinst/guest.py", line 434, in _create_guest
domain = self.conn.createXML(install_xml or final_xml, 0)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3659, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirtError: internal error: process exited while connecting to monitor: Could 
not access KVM kernel module: Permission denied
2018-03-14T18:32:12.683550Z qemu-system-x86_64: failed to initialize KVM: 
Permission denied

My user is part of the libvirt group. Is polkit somehow broken or something?

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages libvirt-daemon depends on:
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.12-3
ii  libaudit1   1:2.8.2-1
ii  libavahi-client30.7-3.1
ii  libavahi-common30.7-3.1
ii  libblkid1   2.31.1-0.5
ii  libc6   2.27-2
ii  libcap-ng0  0.7.7-3.1+b1
ii  libcurl3-gnutls 7.58.0-2
ii  libdbus-1-3 1.13.2-1bigon1
ii  libdevmapper1.02.1  2:1.02.145-4.1
ii  libfuse22.9.7-1
ii  libgnutls30 3.5.18-1
ii  libnetcf1   1:0.2.8-1+b2
ii  libnl-3-200 3.2.27-2
ii  libnl-route-3-200   3.2.27-2
ii  libnuma12.0.11-2.1
ii  libparted2  3.2-20
ii  libpcap0.8  1.8.1-6
ii  libpciaccess0   0.13.4-1+b2
ii  libsasl2-2  2.1.27~101-g0780600+dfsg-3
ii  libselinux1 2.7-2+b1
ii  libssh2-1   1.8.0-1
ii  libudev1238-2
ii  libvirt04.0.0-2
ii  libxen-4.8  4.8.3+comet2+shim4.10.0+comet3-1+deb9u5
ii  libxenstore3.0  4.8.3+comet2+shim4.10.0+comet3-1+deb9u5
ii  libxml2 2.9.4+dfsg1-6.1
ii  libyajl22.1.0-2+b3

Versions of packages libvirt-daemon recommends:
ii  libxml2-utils   2.9.4+dfsg1-6.1
ii  netcat-openbsd  1.187-1
ii  qemu-kvm1:2.11+dfsg-1

Versions of packages libvirt-daemon suggests:
pn  libvirt-daemon-driver-storage-gluster   
pn  libvirt-daemon-driver-storage-rbd   
pn  libvirt-daemon-driver-storage-sheepdog  
pn  libvirt-daemon-driver-storage-zfs   
ii  libvirt-daemon-system   4.0.0-2
pn  numad   

-- no debconf information

Bug#888153: marked as done (prometheus: Performance problems in 2.1.0)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 18:34:48 +
with message-id 
and subject line Bug#888153: fixed in prometheus 2.2.0+ds-1
has caused the Debian Bug report #888153,
regarding prometheus: Performance problems in 2.1.0
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.)


-- 
888153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prometheus
Version: 2.1.0+ds-1
Severity: grave
Tags: upstream
Justification: renders package unusable

The upstream developers of Prometheus have advised me to block transition of
prometheus 2.1.0+ds-1 due to some serious performance issues introduced with
this release. I expect a fix for this will be released soon, but meanwhile this
bug should stop prometheus from migrating to testing.

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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages prometheus depends on:
ii  adduser  3.116
ii  daemon   0.6.4-1+b2
ii  debconf [debconf-2.0]1.5.65
ii  libc62.26-1
pn  libjs-bootstrap  
pn  libjs-eonasdan-bootstrap-datetimepicker  
ii  libjs-jquery 3.2.1-1
pn  libjs-jquery-hotkeys 
pn  libjs-moment 
pn  libjs-mustache   
pn  libjs-rickshaw   

Versions of packages prometheus recommends:
pn  prometheus-node-exporter  

prometheus suggests no packages.
--- End Message ---
--- Begin Message ---
Source: prometheus
Source-Version: 2.2.0+ds-1

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated prometheus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Mar 2018 18:18:37 +
Source: prometheus
Binary: prometheus
Architecture: source
Version: 2.2.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Martín Ferrari 
Description:
 prometheus - Monitoring system and time series database
Closes: 888153
Changes:
 prometheus (2.2.0+ds-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #888153.
   * Add notice about DB changes.
   * Update TSDB version.
   * Refresh patches.
   * Update Azure patch for new breakage.
   * Inline unreleased method from the golang client lib.
Checksums-Sha1:
 3b5cfc1337c75ed664c126b34a60ca03b1bd169a 3319 prometheus_2.2.0+ds-1.dsc
 d6ccaa7bd6ef4cf8fc51c7f941d7fc4188eb341b 1028048 
prometheus_2.2.0+ds.orig.tar.gz
 68a0c75380659b9ca0d4af12367be5309f607036 26376 
prometheus_2.2.0+ds-1.debian.tar.xz
 736527fb6b5dfff61220f3e3e6a7390077d9d9f3 11519 
prometheus_2.2.0+ds-1_amd64.buildinfo
Checksums-Sha256:
 c94de16918725034e0f7e0fac281488917a11de9034aa7e199e7f646390045c4 3319 
prometheus_2.2.0+ds-1.dsc
 ef9a88451fb28f0696844fd26f83ce07fcf54dcf94fb8bae37044045b40276ca 1028048 
prometheus_2.2.0+ds.orig.tar.gz
 d450ea7f3f46e36074021aa99fe361493a57f419a1fcf1445dbac101368efa2f 26376 
prometheus_2.2.0+ds-1.debian.tar.xz
 382dcee2dd5072fb8a6dcf1b96eb30b216fabef6dedcef255a283b2e8e18fc5b 11519 
prometheus_2.2.0+ds-1_amd64.buildinfo
Files:
 db21a645236d03023b168e4c44d2dba7 3319 net optional prometheus_2.2.0+ds-1.dsc
 639fc5f3dd3faf6d9178437fbda61be5 1028048 net optional 
prometheus_2.2.0+ds.orig.tar.gz
 da6d01bcc5aa186ef794145af9ed0ac9 26376 net optional 
prometheus_2.2.0+ds-1.debian.tar.xz
 

Bug#888153: Pending fixes for bugs in the prometheus package

[pkg-go-maintainers]

tag 888153 + pending
thanks

Some bugs in the prometheus package are closed in revision
15211deb72e4a23726c1fd5467e20d4cfd3eb231 in branch 'debian/sid' by
Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/prometheus.git/commit/?id=15211de

Commit message:

New upstream release. Closes: #888153.

Processed: Pending fixes for bugs in the prometheus package

[Debian Bug Tracking System]

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

> tag 888153 + pending
Bug #888153 [prometheus] prometheus: Performance problems in 2.1.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#881342: stretch update for rtkit

[Felipe Sateler]

On Wed, Mar 14, 2018 at 2:35 PM, Adrian Bunk  wrote:

> On Wed, Feb 21, 2018 at 03:24:08PM +, Debian Bug Tracking System wrote:
> >...
> >  rtkit (0.11-6) unstable; urgency=medium
> >  .
> >* Move dbus and polkit from Recommends to Depends
> >  rtkit can't do much really without either of them so bump them to
> Depends.
> >  (Closes: #881342)
> >...
>
> Thanks a lot for fixing this bug for unstable.
>
> It is still present in stretch, could you also fix it there?
> Alternatively, I can fix it for stretch if you don't object.
>

I'd be happy if you do. I'm currently suffering from ENOTIME so I'm not
likely to get around to doing that soon.

-- 

Saludos,
Felipe Sateler

Bug#877457: stretch update for trafficserver

[Adrian Bunk]

On Wed, Jan 17, 2018 at 09:42:09AM +, Debian Bug Tracking System wrote:
>...
>  trafficserver (7.1.1-1) unstable; urgency=medium
>  .
>* Fix trafficserver-dev dependencies. (Closes: #877457)
>...

Thanks a lot for fixing this bug for unstable.

It is still present in stretch, could you also fix it there?
Alternatively, I can fix it for stretch if you don't object.

Thanks
Adrian

-- 

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

Bug#883636: stretch update for showq

[Adrian Bunk]

On Tue, Jan 02, 2018 at 05:36:06PM +, Debian Bug Tracking System wrote:
>...
>  showq (0.4.1+git20161215~dfsg0-3) unstable; urgency=medium
>...
>* Hack prefix to get app started. (Closes: #883636)
>  Thanks to James Cowgill 
>...

Thanks a lot for fixing this bug for unstable.

It is still present in stretch, could you also fix it there?
Alternatively, I can fix it for stretch if you don't object.

Thanks
Adrian

-- 

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

Bug#876251: stretch update for ola

[Adrian Bunk]

On Thu, Sep 28, 2017 at 12:21:11PM +, Debian Bug Tracking System wrote:
>...
>  ola (0.10.5.nojsmin-3) unstable; urgency=medium
>...
>* debian/ola-rdm-tests.rdm_test_server.init: fix typo. Closes: #876251
>...

Thanks a lot for fixing this bug for unstable.

It is still present in stretch, could you also fix it there?
Alternatively, I can fix it for stretch if you don't object.

Thanks
Adrian

-- 

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

Bug#881342: stretch update for rtkit

[Adrian Bunk]

On Wed, Feb 21, 2018 at 03:24:08PM +, Debian Bug Tracking System wrote:
>...
>  rtkit (0.11-6) unstable; urgency=medium
>  .
>* Move dbus and polkit from Recommends to Depends
>  rtkit can't do much really without either of them so bump them to 
> Depends.
>  (Closes: #881342)
>...

Thanks a lot for fixing this bug for unstable.

It is still present in stretch, could you also fix it there?
Alternatively, I can fix it for stretch if you don't object.

Thanks
Adrian

-- 

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

Processed: Re: [Openjdk] Bug#891573: openjdk-10: builds with unlimited 'make -j'

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #891573 [src:openjdk-10] openjdk-10: builds with unlimited 'make -j'
Severity set to 'important' from 'serious'

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

Bug#891573: [Openjdk] Bug#891573: openjdk-10: builds with unlimited 'make -j'

[Matthias Klose]

Control: severity -1 important

On 26.02.2018 19:56, Andreas Beckmann wrote:
> Source: openjdk-10
> Version: 10~32-1
> Severity: serious
> Justification: make build machine unusable while building
> 
> Hi,
> 
> I just stumbled upon load 425 while rebuilding openjdk-10 in
> experimental ... the build runs with DEB_BUILD_OPTIONS=parallel=4
> 
> There seem to be some unlimited 'make -j' calls ...
> 
> Unfortunately no such commands were logged in the build logfile, the
> only evidence I have left is a screen full of

I can't reproduce this. Let's see how the builds on the buildds work out.  You
should see a configure option --with-num-cores=

Bug#867414: stretch update for pymongo

[Adrian Bunk]

On Tue, Aug 29, 2017 at 11:30:06PM +, Debian Bug Tracking System wrote:
>...
>  pymongo (3.5.1+dfsg1-1) unstable; urgency=medium
>...
>* Fix python3-pymongo-ext dependency (Closes: #867414)
>...

Thanks a lot for fixing this bug for unstable.

It is still present in stretch, could you also fix it there?
Alternatively, I can fix it for stretch if you don't object.

Thanks
Adrian

-- 

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

Bug#867464: stretch update for radicale

[Adrian Bunk]

On Wed, Aug 23, 2017 at 10:54:05PM +, Debian Bug Tracking System wrote:
>...
>  radicale (2.1.4-2) experimental; urgency=medium
>  .
>* Fix resolve python-related dependencies and provisions, and drop
>  deprecated (and bogus, for python3 package) XB-Python-Version field.
>  Closes: Bug#867464. Thanks to Adrian Bunk.
>...

Thanks a lot for fixing this bug for unstable.

It is still present in stretch, could you also fix it there?
Alternatively, I can fix it for stretch if you don't object.

Thanks
Adrian

-- 

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

Bug#892933: isl-0.18: Incomplete debian/copyright?

[Chris Lamb]

Source: isl-0.18
Version: 0.18-2
Severity: serious
Justication: Policy 12.5

Hi,

I just ACCEPTed isl-0.18 from NEW but noticed it was missing 
attribution in debian/copyright for at least a code copy (?) of
imath.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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

Bug#880047: stretch update for postgrey

[Adrian Bunk]

On Tue, Mar 13, 2018 at 11:25:21AM +0100, Julien Cristau wrote:
> On 03/12/2018 07:03 PM, Adrian Bunk wrote:
> > On Sat, Nov 25, 2017 at 10:36:10AM +, Debian Bug Tracking System wrote:
> >> ...
> >>  postgrey (1.36-5) unstable; urgency=medium
> >>  .
> >>* debian/postgrey.init: create /var/run/postgrey if it
> >>  does not exist, patch provided by Laurent Bigonville 
> >> .
> >>  (Closes: 756813, 880047)
> >> ...
> > 
> > Thanks a lot for fixing this bug for unstable.
> > 
> > It is still present in stretch, could you also fix it there?
> > Alternatively, I can fix it for stretch if you don't object.
> > 
> > An open question would be whether #867201 should then also be fixed
> > in stretch, I've added Julien to the Cc.
> > 
> I thought I've already said in that bug I don't think it warrants a
> stable update?

It wasn't clear to me whether you meant "doesn't warrant an own stable 
update" or "should not be backported to stable at all".

Now I understand it is the latter.

> Cheers,
> Julien

cu
Adrian

-- 

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

Bug#892926: marked as done (gcc-7-cross-ports stopped building packages that some of its binaries depend upon)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 17:40:16 +0100
with message-id 
and subject line Re: Bug#892926: gcc-7-cross-ports stopped building packages 
that some of its binaries depend upon
has caused the Debian Bug report #892926,
regarding gcc-7-cross-ports stopped building packages that some of its binaries 
depend upon
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.)


-- 
892926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-7-cross-ports
Version: 11
Severity: serious

Since February 2018, some of the binary packages are not built anymore.
Per the changelog:

gcc-7-cross-ports (10) unstable; urgency=medium

  * Build using 7.3.0-4.
  *
  * Stop building packages now built from gcc-8-cross.
  *

 -- Matthias Klose   Tue, 20 Feb 2018 04:21:26 +0700

For example, gcc-7-powerpc-linux-gnu depends on
libgcc-7-dev-powerpc-cross, which is not built anymore. So, it's
uninstallable.

Thanks.
Cascardo.


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

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

Processed: notfound 886806 in intel-microcode/3.20140913.1

[Debian Bug Tracking System]

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

> notfound 886806 intel-microcode/3.20140913.1
Bug #886806 {Done: Henrique de Moraes Holschuh } 
[intel-microcode] intel-microcode: New version 20180108 published
No longer marked as found in versions intel-microcode/3.20140913.1.
> thanks
Stopping processing here.

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

Processed: retitle 886367 to intel-microcode: spectre microcode updates for unstable/testing

[Debian Bug Tracking System]

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

> retitle 886367 intel-microcode: spectre microcode updates for unstable/testing
Bug #886367 [intel-microcode] intel-microcode: coming updates for 
meltdown/spectre
Changed Bug title to 'intel-microcode: spectre microcode updates for 
unstable/testing' from 'intel-microcode: coming updates for meltdown/spectre'.
> thanks
Stopping processing here.

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

Processed: closing 886806

[Debian Bug Tracking System]

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

> close 886806
Bug #886806 [intel-microcode] intel-microcode: New version 20180108 published
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: retitle 887856 to intel-microcode: spectre microcode updates for stable

[Debian Bug Tracking System]

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

> retitle 887856 intel-microcode: spectre microcode updates for stable
Bug #887856 [intel-microcode] intel-microcode: Spectre / Meltdown : bring 
intel-microcode 20180104 to stretch
Changed Bug title to 'intel-microcode: spectre microcode updates for stable' 
from 'intel-microcode: Spectre / Meltdown : bring intel-microcode 20180104 to 
stretch'.
> thanks
Stopping processing here.

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

Bug#888121: marked as done (ruby-delayed-job-active-record: FTBFS on ruby2.5: `method_missing': undefined method `yaml_as')

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 16:11:30 +
with message-id 
and subject line Bug#888121: fixed in ruby-delayed-job 4.1.4-1
has caused the Debian Bug report #888121,
regarding ruby-delayed-job-active-record: FTBFS on ruby2.5: `method_missing': 
undefined method `yaml_as'
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.)


-- 
888121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-delayed-job-active-record
Version: 4.0.3-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

...

Finished in 1.56 seconds (files took 2.53 seconds to load)
88 examples, 0 failures

/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5   │
└──┘

GEM_PATH=debian/ruby-delayed-job-active-record/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -e gem\ \"delayed_job_active_record\"

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/ruby-delayed-job-active-record-4.0.3/debian/ruby-delayed-job-active-record/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-delayed-job-active-record/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation
/usr/lib/ruby/vendor_ruby/thread_safe/cache.rb:155: warning: constant ::Fixnum 
is deprecated
/usr/lib/ruby/vendor_ruby/thread_safe/cache.rb:155: warning: constant ::Fixnum 
is deprecated
/usr/lib/ruby/vendor_ruby/active_record/dynamic_matchers.rb:26:in 
`method_missing': undefined method `yaml_as' for ActiveRecord::Base:Class 
(NoMethodError)
Did you mean?  yaml_tag
from 
/usr/lib/ruby/vendor_ruby/delayed/serialization/active_record.rb:4:in 
`'
from 
/usr/lib/ruby/vendor_ruby/delayed/serialization/active_record.rb:3:in 
`'
from 
/usr/lib/ruby/vendor_ruby/delayed/serialization/active_record.rb:2:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:274:in 
`block in require'
from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:240:in 
`load_dependency'
from /usr/lib/ruby/vendor_ruby/active_support/dependencies.rb:274:in 
`require'
from /usr/lib/ruby/vendor_ruby/delayed/worker.rb:64:in `backend='
from 
/build/ruby-delayed-job-active-record-4.0.3/lib/delayed_job_active_record.rb:5:in
 `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/ruby-delayed-job-active-record-4.0.3/spec/helper.rb:8:in 
`'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from 
/build/ruby-delayed-job-active-record-4.0.3/spec/delayed/backend/active_record_spec.rb:1:in
 `'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:100:in `setup'
from 

Processed: notfixed 886367 in intel-microcode/3.20180108.1

[Debian Bug Tracking System]

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

> notfixed 886367 intel-microcode/3.20180108.1
Bug #886367 [intel-microcode] intel-microcode: coming updates for 
meltdown/spectre
No longer marked as fixed in versions intel-microcode/3.20180108.1.
> thanks
Stopping processing here.

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

Bug#887856: intel-microcode: Spectre / Meltdown : bring intel-microcode 20180104 to stretch

[Moritz Mühlenhoff]

On Wed, Mar 14, 2018 at 12:39:22PM -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 14 Mar 2018, Moritz Muehlenhoff wrote:
> > On Sun, Jan 21, 2018 at 07:47:35AM -0200, Henrique de Moraes Holschuh wrote:
> > > severity 887856 grave
> > > block 887856 by 886998
> > > thanks
> > > 
> > > On Sat, 20 Jan 2018, Julien Aubin wrote:
> > > > As of now intel-microcode of stretch is still set to 20170707 (20171117
> > > > through
> > > > bpo) which lets users vulnerable to Spectre attack CVE-2017-5715. Could 
> > > > you
> > > > please bring quickly the microcode update to stretch, at least on bpo ?
> > > 
> > > Please refer to bug #886998
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886998
> > > 
> > > We will wait for a new, official Intel microcode release before we
> > > consider updating the intel-microcode package in stable and backports.
> > 
> > https://downloadcenter.intel.com/download/27591/Linux-Processor-Microcode-Data-File
> > 
> > These should be good now? 
> 
> Yes, uploaded to unstable a few hours ago (might be waiting on dinstall,
> though).
> 
> > Let's keep this cooking in unstable for a while before considering an 
> > upgrade in stable, though.
> 
> Sure, uploaded with medium priority to get 10 days worth of unstable,
> then let's get it to wait around on testing for at least 1 month *after*
> the next kernel update in testing (which should re-enable IBRS+IBPB on
> Skylake).
> 
> Unless we get lots of indirect coverage from other distros that would
> allow us to speed this up, I'd say we'll wait about 2 months before
> proposing it for -stable.

Ack, that was about the time frame I had in my mind.

Cheers,
Moritz

Processed: notfixed 886367 in intel-microcode/3.20171215.1

[Debian Bug Tracking System]

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

> notfixed 886367 intel-microcode/3.20171215.1
Bug #886367 [intel-microcode] intel-microcode: coming updates for 
meltdown/spectre
No longer marked as fixed in versions intel-microcode/3.20171215.1.
> thanks
Stopping processing here.

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

Bug#892074: marked as done (uwsgi: FTBFS with ruby2.5 as default)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 16:00:37 +
with message-id 
and subject line Bug#892074: fixed in uwsgi 2.0.15-10.3
has caused the Debian Bug report #892074,
regarding uwsgi: FTBFS with ruby2.5 as default
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.)


-- 
892074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uwsgi
Version: 2.0.15-10.2
Severity: serious
Justification: fails to build from source

I am about to upload ruby-defaults to unstable, switching the default
Ruby to ruby2.5. With that in place, uwsgi fails to build from source
like this:

[...]
 CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro" python uwsgiconfig.py -v --plugin plugins/rack_ruby23 
debian/buildconf/uwsgi-plugin.ini rack_ruby23
using profile: debian/buildconf/uwsgi-plugin.ini
detected include path: ['/usr/lib/gcc/x86_64-linux-gnu/7/include', 
'/usr/local/include', '/usr/lib/gcc/x86_64-linux-gnu/7/include-fixed', 
'/usr/include/x86_64-linux-gnu', '/usr/include']
*** uWSGI building and linking plugin plugins/rack_ruby23 ***
Error: unable to find directory 'plugins/rack_ruby23'
make: *** [debian/rules:450: debian/stamp-uwsgi-plugin-rack-ruby2.3] Error 1
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
[...]

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

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: uwsgi
Source-Version: 2.0.15-10.3

We believe that the bug you reported is fixed in the latest version of
uwsgi, 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.
Antonio Terceiro  (supplier of updated uwsgi 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: Sat, 10 Mar 2018 19:16:35 -0300
Source: uwsgi
Binary: uwsgi uwsgi-dbg uwsgi-src uwsgi-dev uwsgi-core uwsgi-emperor 
uwsgi-plugins-all uwsgi-infrastructure-plugins uwsgi-app-integration-plugins 
uwsgi-plugin-alarm-curl uwsgi-plugin-alarm-xmpp uwsgi-plugin-curl-cron 
uwsgi-plugin-emperor-pg uwsgi-plugin-glusterfs uwsgi-plugin-rados 
uwsgi-plugin-rbthreads uwsgi-plugin-fiber uwsgi-plugin-geoip 
uwsgi-plugin-graylog2 uwsgi-plugin-gevent-python uwsgi-plugin-greenlet-python 
uwsgi-plugin-asyncio-python uwsgi-plugin-asyncio-python3 
uwsgi-plugin-tornado-python uwsgi-plugin-gccgo uwsgi-plugin-jvm-openjdk-8 
uwsgi-plugin-jwsgi-openjdk-8 uwsgi-plugin-ring-openjdk-8 
uwsgi-plugin-servlet-openjdk-8 uwsgi-plugin-ldap uwsgi-plugin-lua5.1 
uwsgi-plugin-lua5.2 uwsgi-plugin-mono uwsgi-plugin-psgi uwsgi-plugin-python 
uwsgi-plugin-python3 uwsgi-plugin-rack-ruby2.5 uwsgi-plugin-router-access 
uwsgi-plugin-sqlite3 uwsgi-plugin-xslt libapache2-mod-proxy-uwsgi 
libapache2-mod-proxy-uwsgi-dbg libapache2-mod-uwsgi libapache2-mod-uwsgi-dbg
 libapache2-mod-ruwsgi libapache2-mod-ruwsgi-dbg python-uwsgidecorators 
python3-uwsgidecorators
 uwsgi-extra
Architecture: source amd64 all
Version: 2.0.15-10.3
Distribution: unstable
Urgency: medium
Maintainer: uWSGI packaging team 
Changed-By: Antonio Terceiro 
Description:
 libapache2-mod-proxy-uwsgi - uwsgi proxy module for Apache2 (mod_uwsgi)
 libapache2-mod-proxy-uwsgi-dbg - debugging symbols for Apache2 mod_proxy_uwsgi
 libapache2-mod-ruwsgi - uwsgi module for Apache2 (mod_Ruwsgi)
 libapache2-mod-ruwsgi-dbg - debugging symbols for Apache2 mod_Ruwsgi
 libapache2-mod-uwsgi - 

Bug#892735: marked as done (beets tests pull in resources from the network, and fail as well)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 16:00:10 +
with message-id 
and subject line Bug#892735: fixed in beets 1.4.6-2
has caused the Debian Bug report #892735,
regarding beets tests pull in resources from the network, and fail as well
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.)


-- 
892735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:beets
Version: 1.4.6-1.1
Severity: serious
Tags: sid buster

the beets tests pull in resources from the network, and then fail as well.

[...]
running test
Searching for discogs-client
Reading https://pypi.python.org/simple/discogs-client/
Downloading
https://pypi.python.org/packages/1f/1f/62a8cee111ff72c5ad379039adef8c872813602ffd516ba35368726f14c2/discogs-client-2.2.1.tar.gz#md5=c82be8006e1c02fcfc2bb42a2e312151
Best match: discogs-client 2.2.1
Processing discogs-client-2.2.1.tar.gz
Writing /tmp/easy_install-zu0tmzvm/discogs-client-2.2.1/setup.cfg
Running discogs-client-2.2.1/setup.py -q bdist_egg --dist-dir
/tmp/easy_install-zu0tmzvm/discogs-client-2.2.1/egg-dist-tmp-38vd56jf
warning: no previously-included files matching 'make_symlinks.py' found under
directory 'discogs_client/tests'
zip_safe flag not set; analyzing archive contents...
Moving discogs_client-2.2.1-py3.6.egg to /home/packages/tmp/beets-1.4.6/.eggs

Installed /home/packages/tmp/beets-1.4.6/.eggs/discogs_client-2.2.1-py3.6.egg
Searching for pathlib
Reading https://pypi.python.org/simple/pathlib/
Downloading
https://pypi.python.org/packages/ac/aa/9b065a76b9af472437a0059f77e8f962fe350438b927cb80184c32f075eb/pathlib-1.0.1.tar.gz#md5=5099ed48be9b1ee29b31c82819240537
Best match: pathlib 1.0.1
Processing pathlib-1.0.1.tar.gz
Writing /tmp/easy_install-94hca6pr/pathlib-1.0.1/setup.cfg
Running pathlib-1.0.1/setup.py -q bdist_egg --dist-dir
/tmp/easy_install-94hca6pr/pathlib-1.0.1/egg-dist-tmp-5ghf0vkb
zip_safe flag not set; analyzing archive contents...
Moving pathlib-1.0.1-py3.6.egg to /home/packages/tmp/beets-1.4.6/.eggs

Installed /home/packages/tmp/beets-1.4.6/.eggs/pathlib-1.0.1-py3.6.egg
Searching for oauthlib
Reading https://pypi.python.org/simple/oauthlib/
Downloading
https://pypi.python.org/packages/a5/8a/212e9b47fb54be109f3ff0684165bb38c51117f34e175c379fce5c7df754/oauthlib-2.0.6.tar.gz#md5=277a9a966cc8c72e492b4eeb41332445
Best match: oauthlib 2.0.6
Processing oauthlib-2.0.6.tar.gz
Writing /tmp/easy_install-kz2hycyj/oauthlib-2.0.6/setup.cfg
Running oauthlib-2.0.6/setup.py -q bdist_egg --dist-dir
/tmp/easy_install-kz2hycyj/oauthlib-2.0.6/egg-dist-tmp-nrkifwe0
zip_safe flag not set; analyzing archive contents...
Moving oauthlib-2.0.6-py3.6.egg to /home/packages/tmp/beets-1.4.6/.eggs

Installed /home/packages/tmp/beets-1.4.6/.eggs/oauthlib-2.0.6-py3.6.egg


that's a lot of missing test dependencies ...


[...]
==
FAIL: test_asciify_variable (test_library.DestinationFunctionTest)
--
Traceback (most recent call last):
  File "/home/packages/tmp/beets-1.4.6/test/test_library.py", line 594, in
test_asciify_variable
self._assert_dest(b'/base/abC_1_2d')
  File "/home/packages/tmp/beets-1.4.6/test/test_library.py", line 565, in
_assert_dest
self.assertEqual(actual, dest)
AssertionError: b'/base/abC_ 1_2 d' != b'/base/abC_1_2d'

==
FAIL: test_asciify_character_expanding_to_slash (test_library.DestinationTest)
--
Traceback (most recent call last):
  File "/home/packages/tmp/beets-1.4.6/test/test_library.py", line 430, in
test_asciify_character_expanding_to_slash
self.assertEqual(self.i.destination(), np('lib/abC_1_2d'))
AssertionError: b'/home/packages/tmp/beets-1.4.6/test/lib/abC_ 1_2 d' !=
b'/home/packages/tmp/beets-1.4.6/test/lib/abC_1_2d'

--
Ran 1788 tests in 45.117s

FAILED (failures=2, skipped=31)
Test failed: 
error: Test failed: 
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: beets
Source-Version: 1.4.6-2

We believe that the bug you reported is fixed in the latest version of
beets, 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 

Processed: fixed 886367 in intel-microcode/3.20180312.1

[Debian Bug Tracking System]

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

> fixed 886367 intel-microcode/3.20180312.1
Bug #886367 [intel-microcode] intel-microcode: coming updates for 
meltdown/spectre
Marked as fixed in versions intel-microcode/3.20180312.1.
> thanks
Stopping processing here.

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

Processed: notfixed 886367 in intel-microcode/3.20180108.1+really20171117.1

[Debian Bug Tracking System]

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

> notfixed 886367 intel-microcode/3.20180108.1+really20171117.1
Bug #886367 [intel-microcode] intel-microcode: coming updates for 
meltdown/spectre
Ignoring request to alter fixed versions of bug #886367 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#892911: marked as done (intel-microcode: New version 20180312 published)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 12:40:58 -0300
with message-id <20180314154058.z3zakxy2xpr6p...@khazad-dum.debian.net>
and subject line Re: Bug#892911: intel-microcode: New version 20180312 published
has caused the Debian Bug report #892911,
regarding intel-microcode: New version 20180312 published
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.)


-- 
892911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: intel-microcode
Version: 3.20180108.1+really20171117.1
Severity: grave
Tags: security

Hello!

It looks like there has been a new release.  The data file version is
20180312.

The microcode download page is
https://downloadcenter.intel.com/download/27591/Linux-Processor-Microcode-Data-File?v=t
--- End Message ---
--- Begin Message ---
On Wed, 14 Mar 2018, Emre Uyguroglu wrote:
> Package: intel-microcode
> Version: 3.20180108.1+really20171117.1
> Severity: grave
> Tags: security
> 
> Hello!
> 
> It looks like there has been a new release.  The data file version is
> 20180312.

Uploaded a few hours ago to unstable, missed this bug report by a hair.

Closing the bug manually...

-- 
  Henrique Holschuh--- End Message ---

Processed: found 886367 in intel-microcode/3.20180108.1+really20171117.1

[Debian Bug Tracking System]

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

> found 886367 intel-microcode/3.20180108.1+really20171117.1
Bug #886367 {Done: Henrique de Moraes Holschuh } 
[intel-microcode] intel-microcode: coming updates for meltdown/spectre
Marked as found in versions intel-microcode/3.20180108.1+really20171117.1 and 
reopened.
> thanks
Stopping processing here.

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

Bug#892926: gcc-7-cross-ports stopped building packages that some of its binaries depend upon

[Thadeu Lima de Souza Cascardo]

Source: gcc-7-cross-ports
Version: 11
Severity: serious

Since February 2018, some of the binary packages are not built anymore.
Per the changelog:

gcc-7-cross-ports (10) unstable; urgency=medium

  * Build using 7.3.0-4.
  *
  * Stop building packages now built from gcc-8-cross.
  *

 -- Matthias Klose   Tue, 20 Feb 2018 04:21:26 +0700

For example, gcc-7-powerpc-linux-gnu depends on
libgcc-7-dev-powerpc-cross, which is not built anymore. So, it's
uninstallable.

Thanks.
Cascardo.


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

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

Processed: unarchiving 886367

[Debian Bug Tracking System]

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

> unarchive 886367
Bug #886367 {Done: Henrique de Moraes Holschuh } 
[intel-microcode] intel-microcode: coming updates for meltdown/spectre
Unarchived Bug 886367
> thanks
Stopping processing here.

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

Bug#887856: intel-microcode: Spectre / Meltdown : bring intel-microcode 20180104 to stretch

[Henrique de Moraes Holschuh]

On Wed, 14 Mar 2018, Moritz Muehlenhoff wrote:
> On Sun, Jan 21, 2018 at 07:47:35AM -0200, Henrique de Moraes Holschuh wrote:
> > severity 887856 grave
> > block 887856 by 886998
> > thanks
> > 
> > On Sat, 20 Jan 2018, Julien Aubin wrote:
> > > As of now intel-microcode of stretch is still set to 20170707 (20171117
> > > through
> > > bpo) which lets users vulnerable to Spectre attack CVE-2017-5715. Could 
> > > you
> > > please bring quickly the microcode update to stretch, at least on bpo ?
> > 
> > Please refer to bug #886998
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886998
> > 
> > We will wait for a new, official Intel microcode release before we
> > consider updating the intel-microcode package in stable and backports.
> 
> https://downloadcenter.intel.com/download/27591/Linux-Processor-Microcode-Data-File
> 
> These should be good now? 

Yes, uploaded to unstable a few hours ago (might be waiting on dinstall,
though).

> Let's keep this cooking in unstable for a while before considering an upgrade 
> in stable, though.

Sure, uploaded with medium priority to get 10 days worth of unstable,
then let's get it to wait around on testing for at least 1 month *after*
the next kernel update in testing (which should re-enable IBRS+IBPB on
Skylake).

Unless we get lots of indirect coverage from other distros that would
allow us to speed this up, I'd say we'll wait about 2 months before
proposing it for -stable.

I will upload the usual backports after it propagates to testing,
though.

-- 
  Henrique Holschuh

Bug#892458: Fwd: [Debian-astro-maintainers] ftools update

[Ole Streicher]

FYI


 Forwarded Message 
Subject: [Debian-astro-maintainers] ftools update
Date: Wed, 14 Mar 2018 10:42:25 -0400
From: Michael Arida 
To: debian-astro-maintain...@lists.alioth.debian.org


Dear Debian Astro Maintainers,

As you may have noticed CFITSIO was updated Friday (March 2) for a
major bug fix.  Since you have a software bundle that uses what we
assume is CFITSIO somewhere under the hood, we wanted to let you know
that you should update that code.  We are also expecting another
update in April.

If you have any questions or concerns, feel free to contact me.

Regards,
 Mike Arida

Michael Arida (ADNET) ASD/HEASARC
301.286.2291/1215 (voice/fax)  Code 660, NASA/GSFC
michael.ar...@nasa.gov Greenbelt, MD 20771

___
Debian-astro-maintainers mailing list
debian-astro-maintain...@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/debian-astro-maintainers

Bug#880842: marked as done (gnome-twitch FTBFS with meson 0.43.0: Invalid kwargs for option "use-deprecated-webkit": "descritpion")

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 15:19:28 +
with message-id 
and subject line Bug#880842: fixed in gnome-twitch 0.4.1-1.1
has caused the Debian Bug report #880842,
regarding gnome-twitch FTBFS with meson 0.43.0: Invalid kwargs for option 
"use-deprecated-webkit": "descritpion"
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.)


-- 
880842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-twitch
Version: 0.3.1-1
Severity: serious
Tags: buster sid

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

...
Meson encountered an error in file meson_options.txt, line 2, column 0:
Invalid kwargs for option "use-deprecated-webkit": "descritpion"

A full log can be found at 
/build/1st/gnome-twitch-0.3.1/build/meson-logs/meson-log.txt
debian/rules:13: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1
--- End Message ---
--- Begin Message ---
Source: gnome-twitch
Source-Version: 0.4.1-1.1

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
gnome-twitch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Mar 2018 16:04:12 +0100
Source: gnome-twitch
Binary: gnome-twitch gnome-twitch-player-backend-gstreamer-cairo 
gnome-twitch-player-backend-gstreamer-opengl 
gnome-twitch-player-backend-gstreamer-clutter 
gnome-twitch-player-backend-mpv-opengl
Architecture: source
Version: 0.4.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Tim Dengel 
Changed-By: Gianfranco Costamagna 
Description:
 gnome-twitch - GNOME Twitch app for watching Twitch.tv streams without a 
browser
 gnome-twitch-player-backend-gstreamer-cairo - Player backend for GNOME Twitch 
based on gstreamer+cairo
 gnome-twitch-player-backend-gstreamer-clutter - Player backend for GNOME 
Twitch based on gstreamer+clutter
 gnome-twitch-player-backend-gstreamer-opengl - Player backend for GNOME Twitch 
based on gstreamer+opengl
 gnome-twitch-player-backend-mpv-opengl - Player backend for GNOME Twitch based 
on mpv
Closes: 880842
Changes:
 gnome-twitch (0.4.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Upload to unstable
 .
   [ Jeremy Bicha ]
   * debian/patches/6bee8bc0.patch: Cherry-pick upstream build fix
 (Closes: #880842)
Checksums-Sha1:
 966d086b51b27bfe531b2ec1c8a68c457cafa44e 2518 gnome-twitch_0.4.1-1.1.dsc
 6fb0e82075481cee78edaa5ab69df9ea9f63922a 4728 
gnome-twitch_0.4.1-1.1.debian.tar.xz
 25df2aa5fd43f59385fb6da2cabd4db23793b6be 6588 
gnome-twitch_0.4.1-1.1_source.buildinfo
Checksums-Sha256:
 03ad2cee72a299c44962db17f87d7f7b336178b96b84a8a2d71efcf87e7d5111 2518 
gnome-twitch_0.4.1-1.1.dsc
 e015831ff00e912a151b9563eb72df7bc891df07146e6bf61912241b787123e3 4728 
gnome-twitch_0.4.1-1.1.debian.tar.xz
 862fcd501bf53591cb48af4f8fb6f1c87d64bfedcaaa67d1cf01b6826bed27ac 6588 
gnome-twitch_0.4.1-1.1_source.buildinfo
Files:
 4f6296cec3239bf33255aacdc401a693 2518 video extra gnome-twitch_0.4.1-1.1.dsc
 6771fa3af312377c29c9a170b46f263a 4728 video extra 
gnome-twitch_0.4.1-1.1.debian.tar.xz
 965988e3d8ec3423886e7f9a451bfc3c 6588 video extra 
gnome-twitch_0.4.1-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJaqTp1AAoJEPNPCXROn13ZndcP/1VsYV/rcjei4T75gu8B39jq
c6yRVlM+IiqSRXvyFye6G/YQH/oFl3J4aG3GaH0MaAIhHMent+a/FKIk/0Il5Ybm
69K77TF1N+kuz30IjFgzTVnZ8XGFOY4KpH98r7/iJB8NK+Ui/8tRj2TTrY0Du9do
wKzca+qbELwU2r9Anw4cEuX8SraQTNPVzvmiOTIseN8fopIDtB6ZMFqvmP4SY3/7
I1x84Lfd+V9gipc2f5q7OUGmVMbswwT6vuQO22pbQqwTJMBoQsEj2Xi6NHCdPBxD
x1IkYWqph/DnKboRtfVrLzCxUjGVC5JZItTvQ8vDfSNNsGpvHNy/23t6y9Im+wkY
7SSZrE/WcUSuhggsiX434F8DUC2uIegqGkeDzq4okRj2Xs1+s4AS5y52BGhjWiK/
qw930v7dBTvvBqmBM9igwlFAox9N8OEjn9fy+dJEApQm0K3wZo6B8dB3rhMSGmZU

Bug#865798: marked as done (golang-github-shopify-sarama FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 15:19:36 +
with message-id 
and subject line Bug#865798: fixed in golang-github-shopify-sarama 1.16.0-1
has caused the Debian Bug report #865798,
regarding golang-github-shopify-sarama FTBFS: test failures
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.)


-- 
865798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-shopify-sarama
Version: 1.9.0-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-shopify-sarama FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-shopify-sarama.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-shopify-sarama.html

...
--- FAIL: TestMessageEncoding (0.00s)
request_test.go:32: Encoding empty gzip failed
got  [132 99 80 148 0 1 255 255 255 255 0 0 0 23 31 139 8 0 0 0 
0 0 0 255 1 0 0 255 255 0 0 0 0 0 0 0 0] 
want [97 79 149 90 0 1 255 255 255 255 0 0 0 23 31 139 8 0 0 9 
110 136 0 255 1 0 0 255 255 0 0 0 0 0 0 0 0]
...
FAIL
exit status 1
FAILgithub.com/Shopify/sarama   4.201s
...
--- End Message ---
--- Begin Message ---
Source: golang-github-shopify-sarama
Source-Version: 1.16.0-1

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

Debian distribution maintenance software
pp.
Christos Trochalakis  (supplier of updated 
golang-github-shopify-sarama 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, 13 Mar 2018 14:34:01 +0200
Source: golang-github-shopify-sarama
Binary: golang-github-shopify-sarama-dev
Architecture: source
Version: 1.16.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Christos Trochalakis 
Description:
 golang-github-shopify-sarama-dev - Go library for Apache Kafka
Closes: 840627 865798
Changes:
 golang-github-shopify-sarama (1.16.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #840627)
   * Switch to debhelper 11
   * Standards-Version: 4.1.3
   * Enable Go autopkgtests
   * Add myself to Uploaders
   * Drop alignment patch, merged upstream
   * Add missing dependencies
   * Introduce 3 patches fixing broken and flaky tests (Closes: 865798)
Checksums-Sha1:
 1712ed91c3b7512d20d15c16b064653a2eb695c2 2795 
golang-github-shopify-sarama_1.16.0-1.dsc
 90b9401d223b4d0a98b07ffe1fbd980a61cb79b5 156199 
golang-github-shopify-sarama_1.16.0.orig.tar.gz
 ce94cf27e00cfb5adf36819608ce3d73018e5df2 4356 
golang-github-shopify-sarama_1.16.0-1.debian.tar.xz
 3c15283ca9b91025e704b62839c04ff796cf3377 7539 
golang-github-shopify-sarama_1.16.0-1_amd64.buildinfo
Checksums-Sha256:
 76ee425b691202fd5df36e8f7762fa944299e782084dc07e5162f4358d6b28d8 2795 
golang-github-shopify-sarama_1.16.0-1.dsc
 0727859f5ad3900662e637cd9d26198e78b07b80c646600df917a8cf621f2d13 156199 
golang-github-shopify-sarama_1.16.0.orig.tar.gz
 07a9027ad39cddc1bf9b83125999d8687ee4253b7c58d9143010328738d29ce0 4356 
golang-github-shopify-sarama_1.16.0-1.debian.tar.xz
 b01bec6c83ccec76f8ccbfd5d847c17c09707a45de24a82008b696f6a102af60 7539 
golang-github-shopify-sarama_1.16.0-1_amd64.buildinfo
Files:
 3a4cdd0ed08a8d05b38313d4ceee4539 2795 devel optional 
golang-github-shopify-sarama_1.16.0-1.dsc
 90b23dd59774887c5596273762b067c6 156199 devel optional 
golang-github-shopify-sarama_1.16.0.orig.tar.gz
 886b37eea181b85b4655784b75cb4b2b 4356 devel optional 
golang-github-shopify-sarama_1.16.0-1.debian.tar.xz
 fba8aefcf01844877f4e450984e8a38d 7539 devel optional 
golang-github-shopify-sarama_1.16.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEf2SPbCEjyY+zKcgrETYmAKdH7NkFAlqpOHsACgkQETYmAKdH
7NmxLxAAqPsnRgYyRjOqPaMl8U2A0wHeCKtKTonaSQgAHx3RULoadw26KcSqOCX/
gV1jStB+YFrMUZuoI/Rxt2iIiGCtcjd35qou+ANnXfNLQ76l5s5jC7E6Z11/AmJe

Processed: gnome-twitch: diff for NMU version 0.4.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 880842 + pending
Bug #880842 [src:gnome-twitch] gnome-twitch FTBFS with meson 0.43.0: Invalid 
kwargs for option "use-deprecated-webkit": "descritpion"
Added tag(s) pending.

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

Bug#880842: gnome-twitch: diff for NMU version 0.4.1-1.1

[Gianfranco Costamagna]

Control: tags 880842 + pending
On Sun, 11 Mar 2018 20:58:24 -0400 Jeremy Bicha  wrote:
> Control: forwarded -1 https://github.com/vinszent/gnome-twitch/commit/6bee8bc0
> Control: tags -1 fixed-upstream patch
> 
> 

Dear maintainer,

I've prepared an NMU for gnome-twitch (versioned as 0.4.1-1.1) and
uploaded it to DELAYED/0.

Regards.


G.



signature.asc
Description: OpenPGP digital signature

Bug#892645: [gnome-twitch] Segfault on json node

[Gianfranco Costamagna]

control: severity -1 important

Hello,

On Sun, 11 Mar 2018 20:46:04 -0400 Jeremy Bicha  wrote:
> Is this reproducible with gnome-twitch 0.4.1-1 from experimental?
> 

please try to reproduce with the one I'm uploading in unstable, and raise 
severity again if you get the same crash again

G.

> Thanks,
> Jeremy Bicha
> 
> 



signature.asc
Description: OpenPGP digital signature

Processed: Re: [gnome-twitch] Segfault on json node

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #892645 [gnome-twitch] [gnome-twitch] Segfault on json node
Severity set to 'important' from 'grave'

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

Processed: add chromium prefix

[Debian Bug Tracking System]

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

> retitle 892891 chromium: FTBFS: error: invalid application of 'sizeof' to 
> incomplete type 'policy::ConfigurationPolicyProvider'
Bug #892891 [chromium] FTBFS: error: invalid application of 'sizeof' to 
incomplete type 'policy::ConfigurationPolicyProvider'
Changed Bug title to 'chromium: FTBFS: error: invalid application of 'sizeof' 
to incomplete type 'policy::ConfigurationPolicyProvider'' from 'FTBFS: error: 
invalid application of 'sizeof' to incomplete type 
'policy::ConfigurationPolicyProvider''.
> thanks
Stopping processing here.

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

Processed: Bug#892891: 65.0.3325.146-3 never uploaded

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #892891 [chromium] 65.0.3325.146-3 never uploaded
Severity set to 'serious' from 'normal'
> retitle -1 FTBFS: error: invalid application of 'sizeof' to incomplete type 
> 'policy::ConfigurationPolicyProvider'
Bug #892891 [chromium] 65.0.3325.146-3 never uploaded
Changed Bug title to 'FTBFS: error: invalid application of 'sizeof' to 
incomplete type 'policy::ConfigurationPolicyProvider'' from '65.0.3325.146-3 
never uploaded'.

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

Bug#888124: marked as done (ruby-fakeweb: FTBFS on ruby2.5: undefined method `close' for #)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 13:50:46 +
with message-id 
and subject line Bug#888124: fixed in ruby-fakeweb 1.3.0+git20170806+dfsg1-1
has caused the Debian Bug report #888124,
regarding ruby-fakeweb: FTBFS on ruby2.5: undefined method `close' for 
#
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.)


-- 
888124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-fakeweb
Version: 1.3.0+git20131202.48208f9+dfsg-3
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


188 runs, 359 assertions, 0 failures, 0 errors, 0 skips
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5   │
└──┘

GEM_PATH=debian/ruby-fakeweb/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -e gem\ \"fakeweb\"

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/build/ruby-fakeweb-1.3.0+git20131202.48208f9+dfsg/debian/ruby-fakeweb/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-fakeweb/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 debian/ruby-tests.rb
Run options: --seed 13512

# Running:

..E.EE...EEEFFEEF.E.EE...EEE..F..EE..E.E..E...EE.EE...EF...FE...E.EFE.EF..EF....

Finished in 0.103453s, 1817.2499 runs/s, 2590.5477 assertions/s.

  1) Error:
TestFakeWebTrailingSlashes#test_registering_root_with_slash_and_request:
NoMethodError: undefined method `close' for 
#
Did you mean?  closed?
   clone
/usr/lib/ruby/2.5.0/net/http.rb:1014:in `do_finish'
/usr/lib/ruby/2.5.0/net/http.rb:912:in `start'
/usr/lib/ruby/2.5.0/net/http.rb:609:in `start'

/build/ruby-fakeweb-1.3.0+git20131202.48208f9+dfsg/test/test_trailing_slashes.rb:23:in
 `test_registering_root_with_slash_and_request'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:839:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:311:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `each'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest.rb:337:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest.rb:309:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `block in __run'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `map'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `__run'
/usr/lib/ruby/vendor_ruby/minitest.rb:136:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:63:in `block in autorun'

  2) Error:
TestFakeWebTrailingSlashes#test_registering_root_without_slash_and_request:
NoMethodError: undefined method `close' for 
#
Did you mean?  closed?
   clone
/usr/lib/ruby/2.5.0/net/http.rb:1014:in `do_finish'
/usr/lib/ruby/2.5.0/net/http.rb:912:in `start'

Bug#868839: marked as done (ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 13:50:53 +
with message-id 
and subject line Bug#868851: fixed in ruby-mustermann 1.0.0-4
has caused the Debian Bug report #868851,
regarding ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19
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.)


-- 
868851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-mustermann,ruby-mustermann19
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1.0.0-2
Control: found -1 0.4.3+git20160621-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package ruby-mustermann19.
  Preparing to unpack .../ruby-mustermann19_0.4.3+git20160621-1_all.deb ...
  Unpacking ruby-mustermann19 (0.4.3+git20160621-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-mustermann19_0.4.3+git20160621-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/ruby/vendor_ruby/mustermann/ast/boundaries.rb', which is also in 
package ruby-mustermann 1.0.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-mustermann19_0.4.3+git20160621-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

usr/lib/ruby/vendor_ruby/mustermann.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/boundaries.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/compiler.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/expander.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/node.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/param_scanner.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/parser.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/pattern.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/template_generator.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/transformer.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/translator.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/validation.rb
usr/lib/ruby/vendor_ruby/mustermann/caster.rb
usr/lib/ruby/vendor_ruby/mustermann/composite.rb
usr/lib/ruby/vendor_ruby/mustermann/equality_map.rb
usr/lib/ruby/vendor_ruby/mustermann/error.rb
usr/lib/ruby/vendor_ruby/mustermann/expander.rb
usr/lib/ruby/vendor_ruby/mustermann/extension.rb
usr/lib/ruby/vendor_ruby/mustermann/identity.rb
usr/lib/ruby/vendor_ruby/mustermann/mapper.rb
usr/lib/ruby/vendor_ruby/mustermann/pattern.rb
usr/lib/ruby/vendor_ruby/mustermann/pattern_cache.rb
usr/lib/ruby/vendor_ruby/mustermann/regexp.rb
usr/lib/ruby/vendor_ruby/mustermann/regexp_based.rb
usr/lib/ruby/vendor_ruby/mustermann/regular.rb
usr/lib/ruby/vendor_ruby/mustermann/simple_match.rb
usr/lib/ruby/vendor_ruby/mustermann/sinatra.rb
usr/lib/ruby/vendor_ruby/mustermann/to_pattern.rb
usr/lib/ruby/vendor_ruby/mustermann/version.rb


This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


ruby-mustermann=1.0.0-2_ruby-mustermann19=0.4.3+git20160621-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ruby-mustermann
Source-Version: 1.0.0-4

We believe that the bug you reported is fixed in the latest version of
ruby-mustermann, 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 

Bug#868851: marked as done (ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 13:50:53 +
with message-id 
and subject line Bug#868851: fixed in ruby-mustermann 1.0.0-4
has caused the Debian Bug report #868851,
regarding ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19
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.)


-- 
868851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-mustermann-grape,ruby-mustermann19
Version: ruby-mustermann-grape/1.0.0-1
Version: ruby-mustermann19/0.4.3+git20160621-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2017-07-19
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Preconfiguring packages ...
Selecting previously unselected package libreadline7:amd64.
(Reading database ... 11004 files and directories currently installed.)
Preparing to unpack .../libreadline7_7.0-3_amd64.deb ...
Unpacking libreadline7:amd64 (7.0-3) ...
Selecting previously unselected package libssl1.0.2:amd64.
Preparing to unpack .../libssl1.0.2_1.0.2l-2_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2l-2) ...
Selecting previously unselected package libssl1.1:amd64.
Preparing to unpack .../libssl1.1_1.1.0f-3_amd64.deb ...
Unpacking libssl1.1:amd64 (1.1.0f-3) ...
Selecting previously unselected package openssl.
Preparing to unpack .../openssl_1.1.0f-3_amd64.deb ...
Unpacking openssl (1.1.0f-3) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../ca-certificates_20161130+nmu1_all.deb ...
Unpacking ca-certificates (20161130+nmu1) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-6_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-6) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.1.2+dfsg-1_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.2+dfsg-1) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../rubygems-integration_1.11_all.deb ...
Unpacking rubygems-integration (1.11) ...
Selecting previously unselected package ruby2.3.
Preparing to unpack .../ruby2.3_2.3.3-1_amd64.deb ...
Unpacking ruby2.3 (2.3.3-1) ...
Selecting previously unselected package ruby.
Preparing to unpack .../ruby_1%3a2.3.3_amd64.deb ...
Unpacking ruby (1:2.3.3) ...
Selecting previously unselected package rake.
Preparing to unpack .../archives/rake_12.0.0-1_all.deb ...
Unpacking rake (12.0.0-1) ...
Selecting previously unselected package ruby-did-you-mean.
Preparing to unpack .../ruby-did-you-mean_1.0.0-2_all.deb ...
Unpacking ruby-did-you-mean (1.0.0-2) ...
Selecting previously unselected package ruby-minitest.
Preparing to unpack .../ruby-minitest_5.10.2-1_all.deb ...
Unpacking ruby-minitest (5.10.2-1) ...
Selecting previously unselected package ruby-net-telnet.
Preparing to unpack .../ruby-net-telnet_0.1.1-2_all.deb ...
Unpacking ruby-net-telnet (0.1.1-2) ...
Selecting previously unselected package ruby-power-assert.
Preparing to unpack .../ruby-power-assert_0.3.0-1_all.deb ...
Unpacking ruby-power-assert (0.3.0-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../ruby-test-unit_3.2.5-1_all.deb ...
Unpacking ruby-test-unit (3.2.5-1) ...
Selecting previously unselected package libyaml-0-2:amd64.
Preparing to unpack .../libyaml-0-2_0.1.7-2_amd64.deb ...
Unpacking libyaml-0-2:amd64 (0.1.7-2) ...
Selecting previously unselected package libruby2.3:amd64.
Preparing to unpack .../libruby2.3_2.3.3-1_amd64.deb ...
Unpacking libruby2.3:amd64 (2.3.3-1) ...
Selecting previously unselected package ruby-mustermann.
Preparing to unpack .../ruby-mustermann_1.0.0-2_all.deb ...
Unpacking ruby-mustermann (1.0.0-2) ...
Selecting previously unselected package ruby-mustermann-grape.
Preparing to unpack .../ruby-mustermann-grape_1.0.0-1_all.deb ...
Unpacking ruby-mustermann-grape (1.0.0-1) ...
Selecting previously unselected package ruby-mustermann19.
Preparing to unpack .../ruby-mustermann19_0.4.3+git20160621-1_all.deb ...
Unpacking ruby-mustermann19 (0.4.3+git20160621-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/ruby-mustermann19_0.4.3+git20160621-1_all.deb 
(--unpack):
 trying to overwrite '/usr/lib/ruby/vendor_ruby/mustermann/ast/boundaries.rb', 
which is also in package ruby-mustermann 1.0.0-2
Processing triggers for libc-bin (2.24-12) ...
Processing 

Bug#891901: arduino: Doesn't open.

[Geert Stappers]

On Fri, Mar 02, 2018 at 11:21:41AM +0100, Nicola wrote:
> Package: arduino
> Version: 2:1.5.6.2+sdfsg2-3
> Severity: grave
> Tags: a11y
> Justification: renders package unusable
> 

Yes, it is sad to see there is no recent Arduino in Debian.

Recent Arduino versions are reported
in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816908
and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780706

The later, #780706, shows progress and/or request for help.

Processed: Bug #868851 in ruby-mustermann marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #868851 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Bug #868839 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Added tag(s) pending.
Added tag(s) pending.

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

Bug#868851: Bug #868851 in ruby-mustermann marked as pending

[boutil]

Control: tag -1 pending

Hello,

Bug #868851 in ruby-mustermann 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/ruby-team/ruby-mustermann/commit/b45cbfad95f564bfbbf1dfa4edb01c33a89917ef


Fix version in Breaks/Replaces ruby-mustermann19 to cover version in stretch 
(Closes: #868851)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/868851

Bug#891245: marked as done (CVE-2018-6544 / CVE-2018-1000051)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 12:49:48 +
with message-id 
and subject line Bug#891245: fixed in mupdf 1.12.0+ds1-1
has caused the Debian Bug report #891245,
regarding CVE-2018-6544 / CVE-2018-151
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.)


-- 
891245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mupdf
Version: 1.11+ds1-2
Severity: grave
Tags: security

Please see
https://security-tracker.debian.org/tracker/CVE-2018-151
https://security-tracker.debian.org/tracker/CVE-2018-6544

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: mupdf
Source-Version: 1.12.0+ds1-1

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

Debian distribution maintenance software
pp.
Kan-Ru Chen (陳侃如)  (supplier of updated mupdf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 14 Mar 2018 21:26:44 +0900
Source: mupdf
Binary: libmupdf-dev mupdf mupdf-tools
Architecture: source amd64
Version: 1.12.0+ds1-1
Distribution: unstable
Urgency: high
Maintainer: Kan-Ru Chen (陳侃如) 
Changed-By: Kan-Ru Chen (陳侃如) 
Description:
 libmupdf-dev - development files for the MuPDF viewer
 mupdf  - lightweight PDF viewer
 mupdf-tools - command line tools for the MuPDF viewer
Closes: 891245
Changes:
 mupdf (1.12.0+ds1-1) unstable; urgency=high
 .
   * New upstream version 1.12.0+ds1
   * Exclude thirdparty/{freeglut,lcms2} from upstream source
   * Refresh patches
   * Add freeglut3-dev build-dep
   * d/mupdf.docs: Include droid fonts NOTICE file
   * d/patches: Fix CVE-2018-6544 / CVE-2018-151 (Closes: #891245)
Checksums-Sha1:
 83448e582264b3fd47fbd7369be8588e494e1d59 2182 mupdf_1.12.0+ds1-1.dsc
 cad833e1f0927ca9750229350627d9680cc2e376 21967664 mupdf_1.12.0+ds1.orig.tar.xz
 a7de6500392729ab7df26cc151474ca58c9d442b 26800 mupdf_1.12.0+ds1-1.debian.tar.xz
 206f3e1693bc77ac03851db375bcdca943302282 21526180 
libmupdf-dev_1.12.0+ds1-1_amd64.deb
 c036f6e0bd39dc03933fd7f473e5bc4477fb8cbc 19213204 
mupdf-tools_1.12.0+ds1-1_amd64.deb
 b5d0038739579bcb1c6289125183a662d569bcdc 10091 
mupdf_1.12.0+ds1-1_amd64.buildinfo
 2cb3d78fe0bb34d2c8c9a27d457b1ac90643a14e 18989284 mupdf_1.12.0+ds1-1_amd64.deb
Checksums-Sha256:
 8084100bece3ad9e2523004c4fde51ea8e58a449ad53d5cb4708517090031a4d 2182 
mupdf_1.12.0+ds1-1.dsc
 c3fc2e424a240c12ae79ec12dccd6273d1265487b668e28c7ccf75f6b58d9d5d 21967664 
mupdf_1.12.0+ds1.orig.tar.xz
 40d8634f7046aa8bfe0515fd77fa5c9b29252612fd1b44095c375a9977b4fa6a 26800 
mupdf_1.12.0+ds1-1.debian.tar.xz
 0342471c06f7c5ea66c91948f649a2e4638efc1376e83a57318068dedf92c216 21526180 
libmupdf-dev_1.12.0+ds1-1_amd64.deb
 b1c061df6d12ba0c0941bdf78a0015f2ccf7b889f2a903097459b720ba2a8810 19213204 
mupdf-tools_1.12.0+ds1-1_amd64.deb
 9230c1721201c258bc09ab201ab2d88e5db44bca71d2b20e8cfa364606f0b7ea 10091 
mupdf_1.12.0+ds1-1_amd64.buildinfo
 dc7b6fe9db48d2558c4d448cf5785b280c527e1b61629acd5cdea939e670c0f8 18989284 
mupdf_1.12.0+ds1-1_amd64.deb
Files:
 f0fc4549ff43814ad39c32fb9e1e3937 2182 text optional mupdf_1.12.0+ds1-1.dsc
 3881cbbc1d7af2308563cf6c0c6ff8f2 21967664 text optional 
mupdf_1.12.0+ds1.orig.tar.xz
 2499b2bf6dfc6eb6abf2eeb8895c0fc5 26800 text optional 
mupdf_1.12.0+ds1-1.debian.tar.xz
 61ef2bcfaf2bcc39a830db17192257c2 21526180 libdevel optional 
libmupdf-dev_1.12.0+ds1-1_amd64.deb
 152372dd8ac1bbb0a2a083d72deeba26 19213204 text optional 
mupdf-tools_1.12.0+ds1-1_amd64.deb
 1bd7ca0377e413c7ce74242c702f1062 10091 text optional 
mupdf_1.12.0+ds1-1_amd64.buildinfo
 63f609a55e50b27d12d702be0f37ea20 18989284 text optional 
mupdf_1.12.0+ds1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE2JDTPWFH4vUeM4aHCjk1SrblfeEFAlqpFbMACgkQCjk1Srbl
feG2AQ/+MPGKk7vH4c8eT+hOnli8lzNJNVFN87mvkse+/Z0gE1ZIH8kN5bbT0HPn
6M/8zWgbxCI+SIl62RUEkNcaRyxg8JKb/NXGBv2y6sTqpSHZPRyq3bU2kxSz1fcO
BUiWBhJZI0Jbrkvw4ABIwq2VqugzlfSSERHAWVs7WSC90Ft5zeKKeUkQX6HT+vqN

Bug#892912: pytrainer: startup fails because gtk2 features were dropped from matplotlib

[Riccardo Stagni]

Source: pytrainer
Version: 1.11.0-1
Severity: grave
Tags: sid buster upstream
Forwarded: https://github.com/pytrainer/pytrainer/issues/114


Since matplotlib 2.1.1-1 was uploaded to unstable dropping gtk2 features (last
january) pytrainer fails at startup throwing an ImportError.

Please see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885511
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889137
https://github.com/pytrainer/pytrainer/issues/114

Severity set to grave as pytrainer is unusable (both in sid and testing).


Thanks for your work,
Riccardo

Bug#892911: intel-microcode: New version 20180312 published

[Emre Uyguroglu]

Package: intel-microcode
Version: 3.20180108.1+really20171117.1
Severity: grave
Tags: security

Hello!

It looks like there has been a new release.  The data file version is
20180312.

The microcode download page is
https://downloadcenter.intel.com/download/27591/Linux-Processor-Microcode-Data-File?v=t

Bug#878216: Info received (More informations about HyperV version impacted)

[vincent.ta...@amen.fr]

Hi,
Just to add, look like only gen2 of vm are affected (But I have only few 
cases: 8)

Best regards
Vince

Bug#871153: marked as done (libqb: FTBFS: dh_auto_test: make -j16 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 12:04:18 +
with message-id 
and subject line Bug#871153: fixed in libqb 1.0.3-1
has caused the Debian Bug report #871153,
regarding libqb: FTBFS: dh_auto_test: make -j16 check VERBOSE=1 returned exit 
code 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.)


-- 
871153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libqb
Version: 1.0.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[5]: Entering directory '/<>/tests'
> PASS: array.test
> PASS: map.test
> PASS: rb.test
> PASS: blackbox-segfault.sh
> FAIL: log.test
> PASS: loop.test
> PASS: ipc.test
> PASS: resources.test
> ===
>libqb 1.0.1: tests/test-suite.log
> ===
> 
> # TOTAL: 8
> # PASS:  7
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: log
> =
> 
> Running suite(s): logging
> thr_send_logs_1
> thr_send_logs_1
> thr_send_logs_2
> thr_send_logs_2
> ERROR: qb_rb_chunk_read failed: Connection timed out
> Ringbuffer: 
>  ->OVERWRITE
>  ->write_pt [0]
>  ->read_pt [0]
>  ->size [1024 words]
>  =>free [4096 bytes]
>  =>used [0 bytes]
> Ringbuffer: 
>  ->NORMAL
>  ->write_pt [0]
>  ->read_pt [0]
>  ->size [1024 words]
>  =>free [4096 bytes]
>  =>used [0 bytes]
> 50%: Checks: 12, Failures: 6, Errors: 0
> check_log.c:129:P:va_serialize:test_va_serialize:0: Passed
> check_log.c:187:P:log_stupid_inputs:test_log_stupid_inputs:0: Passed
> check_log.c:312:F:log_basic:test_log_basic:0: Assertion 'test_priority == 3' 
> failed: test_priority == 0, 3 == 3
> check_log.c:478:F:log_format:test_log_format:0: Assertion 'test_buf == "debug 
> check_log.c Angus"' failed: test_buf == "", "debug check_log.c Angus" == 
> "debug check_log.c Angus"
> check_log.c:554:F:log_enable:test_log_enable:0: Assertion 'test_buf == 
> "Hello"' failed: test_buf == "", "Hello" == "Hello"
> check_log.c:630:P:log_threads:test_log_threads:0: Passed
> check_log.c:671:P:log_long_msg:test_log_long_msg:0: Passed
> check_log.c:279:F:log_filter_fn:test_log_filter_fn:0: Assertion 'num_msgs == 
> 3' failed: num_msgs == 2, 3 == 3
> check_log.c:725:F:threaded_logging:test_threaded_logging:0: Assertion 
> 'num_msgs == 10' failed: num_msgs == 0, 10 == 10
> check_log.c:759:P:threaded_logging_bad_sched_params:test_threaded_logging_bad_sched_params:0:
>  Passed
> check_log.c:799:F:extended_information:test_extended_information:0: Assertion 
> 'test_buf == "message with no extended information"' failed: test_buf == "", 
> "message with no extended information" == "message with no extended 
> information"
> check_log.c:854:P:zero_tags:test_zero_tags:0: Passed
> FAIL log.test (exit status: 1)
> 
> 
> Testsuite summary for libqb 1.0.1
> 
> # TOTAL: 8
> # PASS:  7
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See tests/test-suite.log
> Please report to develop...@clusterlabs.org
> 
> Makefile:1204: recipe for target 'test-suite.log' failed
> make[5]: *** [test-suite.log] Error 1
> make[5]: Leaving directory '/<>/tests'
> Makefile:1310: recipe for target 'check-TESTS' failed
> make[4]: *** [check-TESTS] Error 2
> make[4]: Leaving directory '/<>/tests'
> Makefile:1383: recipe for target 'check-am' failed
> make[3]: *** [check-am] Error 2
> rm auto_check_header_qbmap.c auto_check_header_qblist.c 
> auto_check_header_qbhdb.c auto_check_header_qbconfig.c 
> auto_check_header_qbipc_common.c auto_check_header_qbipcc.c 
> auto_check_header_qbrb.c auto_check_header_qblog.c auto_check_header_qbutil.c 
> auto_check_header_qbarray.c auto_check_header_qbatomic.c 
> auto_check_header_qbipcs.c auto_check_header_qbloop.c 
> auto_check_header_qbdefs.c
> make[3]: Leaving directory '/<>/tests'
> Makefile:511: recipe for target 'check-recursive' failed
> make[2]: *** [check-recursive] Error 1
> make[2]: Leaving directory '/<>'
> Makefile:802: recipe for target 'check' failed
> make[1]: *** [check] Error 2
> 

Bug#892373: marked as done (proftpd-mod-fsync FTBFS with proftpd 1.3.6-1)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 11:53:13 +
with message-id 
and subject line Bug#892373: fixed in proftpd-mod-fsync 0.3-1
has caused the Debian Bug report #892373,
regarding proftpd-mod-fsync FTBFS with proftpd 1.3.6-1
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.)


-- 
892373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-fsync
Version: 0.2-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proftpd-mod-fsync.html

...
mod_fsync.c:184:10: error: implicit declaration of function 'HANDLED'; did you 
mean 'PR_HANDLED'? [-Werror=implicit-function-declaration]
   return HANDLED(cmd);
  ^~~
...
mod_fsync.c: In function 'fsync_postparse_ev':
mod_fsync.c:269:12: error: 'LOG_SYMLINK' undeclared (first use in this 
function); did you mean 'PR_LOG_SYMLINK'?
   case LOG_SYMLINK:
^~~
PR_LOG_SYMLINK
mod_fsync.c:269:12: note: each undeclared identifier is reported only once for 
each function it appears in
mod_fsync.c:274:12: error: 'LOG_WRITEABLE_DIR' undeclared (first use in this 
function); did you mean 'PR_LOG_WRITABLE_DIR'?
   case LOG_WRITEABLE_DIR:
^
--- End Message ---
--- Begin Message ---
Source: proftpd-mod-fsync
Source-Version: 0.3-1

We believe that the bug you reported is fixed in the latest version of
proftpd-mod-fsync, 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.
Francesco Paolo Lovergine  (supplier of updated 
proftpd-mod-fsync package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Mar 2018 12:31:36 +0100
Source: proftpd-mod-fsync
Binary: proftpd-mod-fsync
Architecture: source amd64
Version: 0.3-1
Distribution: unstable
Urgency: medium
Maintainer: ProFTPD Maintainance Team 

Changed-By: Francesco Paolo Lovergine 
Description:
 proftpd-mod-fsync - ProFTPD module mod_fsync
Closes: 892373
Changes:
 proftpd-mod-fsync (0.3-1) unstable; urgency=medium
 .
   [ Fabrizio Regalli ]
 .
   * Removing libacl1-dev as BD
 .
   [ Hilmar Preuße ]
 .
   * New upstream release: can be built with ProFTP 1.3.6 (Closes: #892373)
 * Bump BD version of proftp-dev to >= 1.3.6.
   * Overhaul clean target in debian/rules to make it work
   * Remove "DM-Upload-Allowed" field.
   * Standards Version 4.1.3, no changes needed.
   * debhelper compat 9, BD Version of debhelper adapted.
   * Remove Fabrizio Regalli from Uploaders field.
Checksums-Sha1:
 00abfedddb75813ede491bda27a0544a69ea60a4 2087 proftpd-mod-fsync_0.3-1.dsc
 30919d5d5337519508eb4a21f8d9fb3663e1bbef 5315 proftpd-mod-fsync_0.3.orig.tar.gz
 80f73c08e8fb3986272b110d30b6b0514c710696 2928 
proftpd-mod-fsync_0.3-1.debian.tar.xz
 ce26623db36bb74b7df0a7534db9a69a023e5951 13872 
proftpd-mod-fsync-dbgsym_0.3-1_amd64.deb
 6a5df4a1f9883c3116d1ce49fbd1e447d3165a2f 6894 
proftpd-mod-fsync_0.3-1_amd64.buildinfo
 ed706fe86befea8096ec388ab799e1d97ead067e 21552 
proftpd-mod-fsync_0.3-1_amd64.deb
Checksums-Sha256:
 915c9773b232e6c162c2b1749027d9003b86ea9c101a667a3ca87621a3b88133 2087 
proftpd-mod-fsync_0.3-1.dsc
 207ea8a3af32e5afac0a24226043fedfb767b7947befe1eeba2672519b44b374 5315 
proftpd-mod-fsync_0.3.orig.tar.gz
 d73699328f2f8707ba35350304dc7b07a0e3596108b03f3735f23bf62d6aa380 2928 
proftpd-mod-fsync_0.3-1.debian.tar.xz
 9ffee68b7d13bf56ebfea0c75a0b846ba982f297b36716583776bb8181852ddd 13872 
proftpd-mod-fsync-dbgsym_0.3-1_amd64.deb
 a9e712b6a927be410cf615eb9905145070ab3d309552fa75da26ef4deb50aead 6894 
proftpd-mod-fsync_0.3-1_amd64.buildinfo
 5f9942d67480bb4266a9a832c55d158577d9b3298a66dcb4c9dc01c65933d91f 21552 
proftpd-mod-fsync_0.3-1_amd64.deb
Files:
 4f72efcfbaeb019a5dcd09cfa039177d 2087 net optional proftpd-mod-fsync_0.3-1.dsc
 a3a25699a7e69a40e7f6892f576efcd8 5315 net optional 
proftpd-mod-fsync_0.3.orig.tar.gz
 abd569d1045b51524d0430dc921dc15e 2928 net optional 

Bug#892371: marked as done (proftpd-mod-vroot FTBFS with proftpd 1.3.6-1)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 11:53:22 +
with message-id 
and subject line Bug#892371: fixed in proftpd-mod-vroot 0.9.4-2
has caused the Debian Bug report #892371,
regarding proftpd-mod-vroot FTBFS with proftpd 1.3.6-1
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.)


-- 
892371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-mod-vroot
Version: 0.9.4-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proftpd-mod-vroot.html

...
mod_vroot.c:1518:19: error: void value not ignored as it ought to be
   if (cmd->argv[1][pathlen - 1] != '/') {
   ^
...
mod_vroot.c: In function 'vroot_pre_pass':
mod_vroot.c:1651:7: error: 'pr_fs_t {aka struct fs_rec}' has no member named 
'creat'; did you mean 'read'?
   fs->creat = vroot_creat;
   ^
--- End Message ---
--- Begin Message ---
Source: proftpd-mod-vroot
Source-Version: 0.9.4-2

We believe that the bug you reported is fixed in the latest version of
proftpd-mod-vroot, 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.
Francesco Paolo Lovergine  (supplier of updated 
proftpd-mod-vroot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Mar 2018 11:41:13 +0100
Source: proftpd-mod-vroot
Binary: proftpd-mod-vroot
Architecture: source amd64
Version: 0.9.4-2
Distribution: unstable
Urgency: medium
Maintainer: ProFTPD Maintainance Team 

Changed-By: Francesco Paolo Lovergine 
Description:
 proftpd-mod-vroot - ProFTPD module mod_vroot
Closes: 892371
Changes:
 proftpd-mod-vroot (0.9.4-2) unstable; urgency=medium
 .
   [Hilmar Preuße]
 .
   * 2 patches from upstream to make package compatible to proftp 1.3.6.
 (Closes: #892371)
Checksums-Sha1:
 a75e73bcc54006b00b39d44e20ffd847eadc0f83 2157 proftpd-mod-vroot_0.9.4-2.dsc
 07a1de3b2537a98320d655f47d1a2ef7972cede1 5936 
proftpd-mod-vroot_0.9.4-2.debian.tar.xz
 e3015173d283d44e3ea2a873d26102da44ee970c 28108 
proftpd-mod-vroot-dbgsym_0.9.4-2_amd64.deb
 4bdec9093e166fc9817a0484062c3afe56c8d772 6916 
proftpd-mod-vroot_0.9.4-2_amd64.buildinfo
 ca819b082d6ac6b73d86a58b2390d9a63d9a12fb 16244 
proftpd-mod-vroot_0.9.4-2_amd64.deb
Checksums-Sha256:
 bce3022b481d65f324ffeda6c235bbf4965e957615e039877b99b9bcfc4eb13b 2157 
proftpd-mod-vroot_0.9.4-2.dsc
 9334ef9769824a859cfe43493064a616480ce538ed353468c39d69ca49f43177 5936 
proftpd-mod-vroot_0.9.4-2.debian.tar.xz
 3bd71862b1eedb007f10f40318546295022119be85e6e4fb154e685fa001f59a 28108 
proftpd-mod-vroot-dbgsym_0.9.4-2_amd64.deb
 c9cdc76a5035355cc736b78debdd9f379a5e0824442397f4d7628c34c4410a62 6916 
proftpd-mod-vroot_0.9.4-2_amd64.buildinfo
 7acec006f37be2d4cfd944d49982e979f94ff1ebf2a24be73f97d724260f0c46 16244 
proftpd-mod-vroot_0.9.4-2_amd64.deb
Files:
 9ecbf4eddfbe791d58b6f30c22a6357c 2157 net optional 
proftpd-mod-vroot_0.9.4-2.dsc
 ea4c239aa585c27c16cb41f4f0e016af 5936 net optional 
proftpd-mod-vroot_0.9.4-2.debian.tar.xz
 97dac15cd0c79cd55f3319ccae0614f2 28108 debug optional 
proftpd-mod-vroot-dbgsym_0.9.4-2_amd64.deb
 e119f58ec2d8ca1dec902996aaa9ae51 6916 net optional 
proftpd-mod-vroot_0.9.4-2_amd64.buildinfo
 47bcd5cae4d1ba08c5ca30c84200cca0 16244 net optional 
proftpd-mod-vroot_0.9.4-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEBXmpeiI46/m+Ye0CDwKl4RY2hqQFAlqo/ioTHGZyYW5raWVA
ZGViaWFuLm9yZwAKCRAPAqXhFjaGpJQBEACZeuFXe3E5Nq9bhirvhtbCIEyzwl0H
RXmnZ6EEdvc4hxevxkHskSqzT53Drbu/8mLAyjxSq5rWcJKDmhMBFZJK5qtHrE5W
9spX6IzeslFy9dlDYGpcjPNyWOgPy6AliRpHEiJ3yvgx8q2Qatw/NAgzmSAMZVlH
h0ryViWx/Yk0igJyvgMCyVoPU8hM++VGmpdidnYCDNTy3Mhh1KH2r+VIfnsEzHmA
z6IGmKH0zqoDfTzLTceEG51i/ixySEPTbG9qKsMBJD/UkObizq3kMJphVkobg/4i
xr39nhkVZ82JwO+FViNBooq4rq2GkMBTXbKW9/WKOaoUVRSaRKR+w3kActtDdom6
Oys5BTyfzmzN2+Ebfb/mi7CNC7nR70VLuVJ/pjFvvzWSxnAqEVoLm4/dgQEdnYSZ
VFYQAReqZFFUUCzXpgkZ8kfThEG7ABhXUUV6pI4iiQMxBLHNY85KcrtF+NCbT+mQ

Processed: bug 888508 is forwarded to https://gitlab.com/gitlab-org/gitlab-ce/issues/44244

[Debian Bug Tracking System]

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

> forwarded 888508 https://gitlab.com/gitlab-org/gitlab-ce/issues/44244
Bug #888508 [src:gitlab] gitlab: multiple CVEs from GitLab Security Release: 
10.3.4, 10.2.6, and 10.1.6 advisory
Set Bug forwarded-to-address to 
'https://gitlab.com/gitlab-org/gitlab-ce/issues/44244'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#892738: consolekit: consolekit removal causes a regression

[Debian Bug Tracking System]

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

> notfound 892738 0.4.6-6
Bug #892738 [consolekit] consolekit: consolekit removal causes a regression
No longer marked as found in versions consolekit/0.4.6-6.
> found 892738 0.4.6-6.1
Bug #892738 [consolekit] consolekit: consolekit removal causes a regression
Marked as found in versions consolekit/0.4.6-6.1.
> thanks
Stopping processing here.

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

Bug#892738: consolekit: consolekit removal causes a regression

[Benedikt Spranger]

notfound 892738 0.4.6-6
found 892738 0.4.6-6.1

thanks

Dear Maintainer,

correct the complained version from 0.4.6-6 to 0.4.6-6.1, since 0.4.6-6
is OK, and due to https://tracker.debian.org/news/928882 add the NMU
uploader to CC.

Sincerly yours
Bene

Bug#887856: intel-microcode: Spectre / Meltdown : bring intel-microcode 20180104 to stretch

[Moritz Muehlenhoff]

On Sun, Jan 21, 2018 at 07:47:35AM -0200, Henrique de Moraes Holschuh wrote:
> severity 887856 grave
> block 887856 by 886998
> thanks
> 
> On Sat, 20 Jan 2018, Julien Aubin wrote:
> > As of now intel-microcode of stretch is still set to 20170707 (20171117
> > through
> > bpo) which lets users vulnerable to Spectre attack CVE-2017-5715. Could you
> > please bring quickly the microcode update to stretch, at least on bpo ?
> 
> Please refer to bug #886998
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886998
> 
> We will wait for a new, official Intel microcode release before we
> consider updating the intel-microcode package in stable and backports.

https://downloadcenter.intel.com/download/27591/Linux-Processor-Microcode-Data-File

These should be good now? 

Let's keep this cooking in unstable for a while before considering an upgrade 
in stable, though.

Cheers,
Moritz

Bug#892096: gcc-snapshot: AddressSanitizer uses glibc internal functions

[Vincent Lefevre]

Control: reopen -1

On 2018-03-14 10:27:35 +0100, Vincent Lefevre wrote:
> On 2018-03-14 09:20:17 +0100, Matthias Klose wrote:
> > now built using glibc-2.27.
> 
> Which version? FYI, I still obtain a crash with 201803012-1.

Reopening since 201803012-1 depends on libc6 (>= 2.27), thus has
presumely been built with glibc-2.27:

cventin:~> dpkg -s gcc-snapshot | grep Depends:
Depends: binutils (>= 2.30), libc6-dev-i386 (>= 2.11), libc6-dev-x32 (>= 2.11), 
libc6-dev (>= 2.13-5), lib32z1 (>= 1:1.1.4), libc6 (>= 2.27), libc6-i386 (>= 
2.27), libc6-x32 (>= 2.27), libgc1c2 (>= 1:7.2d), libgmp10 (>= 2:5.0.1~), 
libisl15 (>= 0.15), libmpc3, libmpfr6 (>= 3.1.3), zlib1g (>= 1:1.1.4), python

And I still get the same error:

cventin:~> gcc-snapshot -m32 -fsanitize=address tst.c -o tst
cventin:~> ./tst
AddressSanitizer:DEADLYSIGNAL
=
==8875==ERROR: AddressSanitizer: SEGV on unknown address 0xf7f29e70 (pc 
0xf7f29e84 bp 0xff97c77c sp 0xff97c73c T16777215)
==8875==The signal is caused by a WRITE memory access.
#0 0xf7f29e83 in _dl_get_tls_static_info (/lib/ld-linux.so.2+0x11e83)
#1 0xf7a43b19  (/usr/lib/gcc-snapshot/lib32/libasan.so.5+0x10cb19)
#2 0xf7a32787  (/usr/lib/gcc-snapshot/lib32/libasan.so.5+0xfb787)
#3 0xf7f2791a  (/lib/ld-linux.so.2+0xf91a)
#4 0xf7f18cb9  (/lib/ld-linux.so.2+0xcb9)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/lib/ld-linux.so.2+0x11e83) in 
_dl_get_tls_static_info
==8875==ABORTING

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

Processed: Re: gcc-snapshot: AddressSanitizer uses glibc internal functions

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #892096 {Done: Matthias Klose } [gcc-snapshot] 
gcc-snapshot: AddressSanitizer uses glibc internal functions
Bug reopened
Ignoring request to alter fixed versions of bug #892096 to the same values 
previously set

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

Processed (with 1 error): forcibly merging 888123 892798 888194

[Debian Bug Tracking System]

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

> forcemerge 888123 892798 888194
Bug #888123 {Done: Cédric Boutillier } [src:ruby-safe-yaml] 
ruby-crack: FTBFS on ruby2.5: uninitialized constant 
SafeYAML::Parse::Date::DateTime
Bug #888194 {Done: Cédric Boutillier } [src:ruby-safe-yaml] 
ruby-safe-yaml: FTBFS on ruby2.5: uninitialized constant 
SafeYAML::Parse::Date::DateTime
Unable to merge bugs because:
package of #892798 is 'ruby-safe-yaml' not 'src:ruby-safe-yaml'
Failed to forcibly merge 888123: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: reassign 892798 to ruby-safe-yaml

[Debian Bug Tracking System]

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

> reassign 892798 ruby-safe-yaml
Bug #892798 [ruby-crack] ruby-crack FTBFS uninitialized constant 
SafeYAML::Parse::Date::DateTime (NameError)
Bug reassigned from package 'ruby-crack' to 'ruby-safe-yaml'.
No longer marked as found in versions ruby-crack/0.4.3-2.
Ignoring request to alter fixed versions of bug #892798 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#892874: marked as done (libmatio-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/libmatio-dev/NEWS.gz)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 09:49:20 +
with message-id 
and subject line Bug#892874: fixed in libmatio 1.5.12-2
has caused the Debian Bug report #892874,
regarding libmatio-doc: fails to upgrade from 'stable' to 'sid' - trying to 
overwrite /usr/share/doc/libmatio-dev/NEWS.gz
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.)


-- 
892874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmatio-doc
Version: 1.5.12-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Selecting previously unselected package libmatio-doc.
  Preparing to unpack .../libmatio-doc_1.5.12-1_all.deb ...
  Unpacking libmatio-doc (1.5.12-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmatio-doc_1.5.12-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libmatio-dev/NEWS.gz', which is also in 
package libmatio-dev:amd64 1.5.9-1+b1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libmatio-doc_1.5.12-1_all.deb


cheers,

Andreas


libmatio-dev=1.5.9-1+b1_libmatio-doc=1.5.12-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libmatio
Source-Version: 1.5.12-2

We believe that the bug you reported is fixed in the latest version of
libmatio, 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.
Sébastien Villemot  (supplier of updated libmatio package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Mar 2018 10:11:31 +0100
Source: libmatio
Binary: libmatio-dev libmatio4 libmatio-doc
Architecture: source
Version: 1.5.12-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Sébastien Villemot 
Description:
 libmatio-dev - MAT File I/O Library - development files
 libmatio-doc - MAT File I/O Library - documentation files
 libmatio4  - Library to read and write Matlab MAT files
Closes: 892874
Changes:
 libmatio (1.5.12-2) unstable; urgency=medium
 .
   * libmatio-doc now Breaks+Replaces libmatio-dev (<< 1.5.10-1~).
 The NEWS and README were moved from libmatio-dev to libmatio-doc in
 release 1.5.10-1. Then, in release 1.5.12-1, the bump to debhelper 11,
 while keeping them inside the libmatio-doc package, moved them back to
 /u/s/d/libmatio-dev/ on the filesystem. (Closes: #892874)
Checksums-Sha1:
 4b10062d379079b27b3479a4488c0b5dc969e2c8 2098 libmatio_1.5.12-2.dsc
 c5f1f06672f4509d7e0919eaf7ef9111af211843 6208 libmatio_1.5.12-2.debian.tar.xz
 76fc059ce27b8458d991fc3a233d85d2e679deba 9155 libmatio_1.5.12-2_amd64.buildinfo
Checksums-Sha256:
 732dc43fe871e7e9bc20dd27d44f6159f51371d318e056e4f32248ce6e14f87b 2098 
libmatio_1.5.12-2.dsc
 896d9b8cd157808df144dace9b736db1d2e084c5b72fb3f013578463fad594ec 6208 
libmatio_1.5.12-2.debian.tar.xz
 707a816d4eef6dd49103b27a31527a7f2a5698e29cad11b6488e65a0e1e6b879 9155 
libmatio_1.5.12-2_amd64.buildinfo
Files:
 aa86d6aef0cef118366cdb4db137a2a4 2098 libs optional libmatio_1.5.12-2.dsc
 3136439dadcf71a0a6bb91a1c47749e4 6208 libs optional 
libmatio_1.5.12-2.debian.tar.xz
 5a1af9c5151bfb58794228ad00dca08b 9155 libs optional 
libmatio_1.5.12-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlqo6T0ACgkQLOzpNQ7O

Bug#892900: marked as done (console-setup: The last update console-setup 1.179 fails in its postinstallation scripts)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 09:34:06 +
with message-id 
and subject line Bug#892900: fixed in console-setup 1.180
has caused the Debian Bug report #892900,
regarding console-setup: The last update console-setup 1.179 fails in its 
postinstallation scripts
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.)


-- 
892900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: console-setup
Version: 1.179
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

Today's upgrade to console-setup 1.179 broke postinstallation scripts.

There's another problem that the scripts attempt to modify the file
/etc/default/console-setup, inserting the line CODESET="Arabic" into it
(though I haven't found a way to reproduce it)

   * What led up to the situation?

I upgraded Debian SID.

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

Run "apt-get update" and "apt-get upgrade"

   * What was the outcome of this action?

dpkg: error processing package console-setup (--configure):
 installed console-setup package post-installation script subprocess returned 
error exit status 20
Errors were encountered while processing:
 console-setup
E: Sub-process /usr/bin/dpkg returned an error code (1)

   * What outcome did you expect instead?

The upgrade should succeed.

*** End of the template - remove these lines ***

my /etc/default/console-setup is
# CONFIGURATION FILE FOR SETUPCON
# Consult the console-setup(5) manual page.
ACTIVE_CONSOLES="/dev/tty[1-6]"
CHARMAP="UTF-8"
#CODESET="Lat2"
#FONTFACE="Fixed"
#FONTSIZE="8x16"
#VIDEOMODE=
CODESET="Lat2"
FONTFACE="TerminusBold"
FONTSIZE="10x20"
#VIDEOMODE="1024x768-60"
# The following is an example how to use a braille font
# FONT='lat9w-08.psf.gz brl-8x8.psf'


If I run the installation script manually, I get this result:
/usr/share/debconf/frontend /var/lib/dpkg/info/console-setup.config configure 
1.178 2>&1|tee console-setup.log

+ set -e
+ . /usr/share/debconf/confmodule
+ [ ! 1 ]
+ [ -z  ]
+ exec
+ [  ]
+ exec
+ DEBCONF_REDIR=1
+ export DEBCONF_REDIR
+ CONFIGFILE=/etc/default/console-setup
+ default_codeset=
+ default_fontface=
+ CHARMAP=
+ CODESET=
+ FONTFACE=
+ FONTSIZE=
+ fontsets=Arabic-Fixed15
Arabic-Fixed16
Arabic-VGA14
Arabic-VGA16
Arabic-VGA28x16
Arabic-VGA32x16
Arabic-VGA8
Armenian-Fixed13
Armenian-Fixed14
Armenian-Fixed15
Armenian-Fixed16
Armenian-Fixed18
CyrAsia-Fixed13
CyrAsia-Fixed14
CyrAsia-Fixed15
CyrAsia-Fixed16
CyrAsia-Fixed18
CyrAsia-Terminus12x6
CyrAsia-Terminus14
CyrAsia-Terminus16
CyrAsia-Terminus20x10
CyrAsia-Terminus22x11
CyrAsia-Terminus24x12
CyrAsia-Terminus28x14
CyrAsia-Terminus32x16
CyrAsia-TerminusBold14
CyrAsia-TerminusBold16
CyrAsia-TerminusBold20x10
CyrAsia-TerminusBold22x11
CyrAsia-TerminusBold24x12
CyrAsia-TerminusBold28x14
CyrAsia-TerminusBold32x16
CyrAsia-TerminusBoldVGA14
CyrAsia-TerminusBoldVGA16
CyrKoi-Fixed13
CyrKoi-Fixed14
CyrKoi-Fixed15
CyrKoi-Fixed16
CyrKoi-Fixed18
CyrKoi-Terminus12x6
CyrKoi-Terminus14
CyrKoi-Terminus16
CyrKoi-Terminus20x10
CyrKoi-Terminus22x11
CyrKoi-Terminus24x12
CyrKoi-Terminus28x14
CyrKoi-Terminus32x16
CyrKoi-TerminusBold14
CyrKoi-TerminusBold16
CyrKoi-TerminusBold20x10
CyrKoi-TerminusBold22x11
CyrKoi-TerminusBold24x12
CyrKoi-TerminusBold28x14
CyrKoi-TerminusBold32x16
CyrKoi-TerminusBoldVGA14
CyrKoi-TerminusBoldVGA16
CyrKoi-VGA14
CyrKoi-VGA16
CyrKoi-VGA28x16
CyrKoi-VGA32x16
CyrKoi-VGA8
CyrSlav-Fixed13
CyrSlav-Fixed14
CyrSlav-Fixed15
CyrSlav-Fixed16
CyrSlav-Fixed18
CyrSlav-Terminus12x6
CyrSlav-Terminus14
CyrSlav-Terminus16
CyrSlav-Terminus20x10
CyrSlav-Terminus22x11
CyrSlav-Terminus24x12
CyrSlav-Terminus28x14
CyrSlav-Terminus32x16
CyrSlav-TerminusBold14
CyrSlav-TerminusBold16
CyrSlav-TerminusBold20x10
CyrSlav-TerminusBold22x11
CyrSlav-TerminusBold24x12
CyrSlav-TerminusBold28x14
CyrSlav-TerminusBold32x16
CyrSlav-TerminusBoldVGA14
CyrSlav-TerminusBoldVGA16
CyrSlav-VGA14
CyrSlav-VGA16
CyrSlav-VGA28x16
CyrSlav-VGA32x16
CyrSlav-VGA8
Ethiopian-Fixed15
Ethiopian-Fixed18
Ethiopian-Goha12
Ethiopian-Goha14
Ethiopian-Goha16
Ethiopian-GohaClassic12
Ethiopian-GohaClassic14
Ethiopian-GohaClassic16
FullCyrAsia-Fixed13
FullCyrAsia-Fixed14
FullCyrAsia-Fixed15
FullCyrAsia-Fixed16
FullCyrAsia-Fixed18
FullCyrAsia-Terminus12x6
FullCyrAsia-Terminus14
FullCyrAsia-Terminus16
FullCyrAsia-Terminus20x10
FullCyrAsia-Terminus22x11
FullCyrAsia-Terminus24x12
FullCyrAsia-Terminus28x14
FullCyrAsia-Terminus32x16
FullCyrAsia-TerminusBold14

Bug#891029: marked as done (dxf2gcode: overly generic python module name: /usr/lib/python3/dist-packages/core/__init__.py)

[Debian Bug Tracking System]

Your message dated Wed, 14 Mar 2018 09:34:12 +
with message-id 
and subject line Bug#891029: fixed in dxf2gcode 20170925-2
has caused the Debian Bug report #891029,
regarding dxf2gcode: overly generic python module name: 
/usr/lib/python3/dist-packages/core/__init__.py
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.)


-- 
891029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dxf2gcode
Version: 20170925-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package uses a very generic
python module name that now clashes with other packages:

/usr/lib/python3/dist-packages/core/__init__.py


Andreas
--- End Message ---
--- Begin Message ---
Source: dxf2gcode
Source-Version: 20170925-2

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

Debian distribution maintenance software
pp.
Sebastian Kuzminsky  (supplier of updated dxf2gcode package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Mar 2018 10:00:02 +0100
Source: dxf2gcode
Binary: dxf2gcode
Architecture: source
Version: 20170925-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Sebastian Kuzminsky 
Description:
 dxf2gcode  - prepares drawings of parts for automatic machine tools
Closes: 891029
Changes:
 dxf2gcode (20170925-2) unstable; urgency=medium
 .
   * Forwarded patches upstream.
   * Moved python modules to a new top-level module (Closes: #891029)
   * Relicensed debian/* to GPL-3+ to match upstream.
   * Added debian/upstream/metadata for UMEGAYA.
Checksums-Sha1:
 0315ed9e4a77a0396523f6ae4cb6c7ef09f2bdc9 2053 dxf2gcode_20170925-2.dsc
 bc6b43393bf7a4a63e1465cc0948a65d63b5b0ae 12248 
dxf2gcode_20170925-2.debian.tar.xz
 67b28e8a912e7146565fcd369e3b4d40ac877dc4 9737 
dxf2gcode_20170925-2_amd64.buildinfo
Checksums-Sha256:
 10e9761381aeb2aad6536a63e1c7491b135bbef8b34ba8a139b444991da352bb 2053 
dxf2gcode_20170925-2.dsc
 0938fd5012150b7462a51b10c4b8833b04b22933845e53eb84539ccb95bb08ea 12248 
dxf2gcode_20170925-2.debian.tar.xz
 bba515f5820b7a01cfa882925ade9e4d169a9d4e7e4d9f179fba8db63e685934 9737 
dxf2gcode_20170925-2_amd64.buildinfo
Files:
 860e5eeaf0d4d7a15e656b325f9e8d6f 2053 science optional dxf2gcode_20170925-2.dsc
 3b2cf04985b3c1e624047c571992fc07 12248 science optional 
dxf2gcode_20170925-2.debian.tar.xz
 c0d3dabed10813eb1330e596a40a7f14 9737 science optional 
dxf2gcode_20170925-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlqo5acACgkQLOzpNQ7O
vkqmNg/+L5nL+Akd2265Q+q+pTZeRfmOt6SDrV+qqmL1r3HxRx0rBgC7HAgZ6HAs
L0wdtqdG+j+ojcDwQYopprjiaHlxe+JFqrK3wZzcE9vI+QLpEosYlmnNqTq8ycCt
rJ+fO7qiFX6PG8q71yZ+qEUVm545JvzUHdBXeRTnmPZSY4ObYLa+q72os0XeE3KN
U26jNX8ksMOyf+So0snma698Z8MFxPaZ9fvEPbK5MOIdwlrZuS1EApZjlmNg1N3i
RsD043+Fb6ML9VdPChEwt7v2WdnDg5ENsZFm4A27WZAiZ9HkGYXSt3jJ6W+yeuAY
odjsRbjo2xVmOrS4L/jBEX1rH4lz4tP6fDA9iorUrOSA6ySNuWYAg3WCUNk0j7NC
uzjDnL+XDcTvhXS92p+w688SqRj47TEF8neoSD/j4xwMiCy9VBTRoAZgo6YAkcr2
waX+eOaPuuq20sOfFlLDq+wamTBGNBELTyeF06ImHUXVw1f2va74o8zDXEYJZS8i
ZaJb1xMM1ndDijFGafzS962qcX86prQxVEexw1HHwcpeU3xgEaPHaVTF1MgOFRh1
X0Ep/tlF2/ZMqEHIcW1URn3UwZjXWITA8muWpnZTbIedZvwm+lB14PYGSFRqihM9
rlaJ3ak5mIw/H2pQT9jl6Sgyqyq12t/JY7R6aBHUFnK6fA11dJk=
=P/ZS
-END PGP SIGNATURE End Message ---