Francois Gouget | 3 May 10:46 2016
Picon

Bug#823307: libgstreamer1.0-dev is not Multi-Arch compatible

Package: libgstreamer1.0-dev
Version: 1.8.0-2
Severity: normal

Dear Maintainer,

The libgstreamer1.0-dev package is not multi-arch aware so that the amd64 version
conflicts with the i386 one which makes it impossible to install both. As a result
several libigstxxx.so symbolic links are missing making development impossible without
manually hacking the filesystem.

This particularly hurts Wine development as it is important to be able to compile both
the 32 and 64 bit versions.

Note that this bug is still present in 1.8.1-1.

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

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

Versions of packages libgstreamer1.0-dev depends on:
ii  gir1.2-gstreamer-1.0  1.8.0-2
(Continue reading)

Daniel Stender | 3 May 10:43 2016
Picon

Bug#823306: pyomo: Pyomo crashes with glp solver

Package: pyomo
Version: 4.3.11327-1
Severity: normal

Pyomo crashes using the glp solver:

<cut>
$ pyomo solve --solver=glp diet1.py diet.dat --summary
Traceback (most recent call last):
  File "/usr/bin/pyomo", line 9, in <module>
    load_entry_point('Pyomo==4.3.11327', 'console_scripts', 'pyomo')()
  File "/usr/lib/python3/dist-packages/pyomo/scripting/pyomo_main.py", line 83, in main
    retval = _options.func(_options, _unparsed)
  File "/usr/lib/python3/dist-packages/pyomo/scripting/plugins/solve.py", line 181, in solve_exec
    config = opt.config_block()
  File "/usr/lib/python3/dist-packages/pyomo/opt/base/solvers.py", line 139, in __getattr__
    self._solver_error(attr)
  File "/usr/lib/python3/dist-packages/pyomo/opt/base/solvers.py", line 153, in _solver_error
    + "\n\toptions: %s" % ( self.options, ) )
RuntimeError: Attempting to use an unavailable solver.

The SolverFactory was unable to create the solver "glp"
and returned an UnknownSolver object.  This error is raised at the point
where the UnknownSolver object was used as if it were valid (by calling
method "config_block").

The original solver was created with the following parameters:
	type: glp
	_args: ()
	options: {}
(Continue reading)

Daniel Stender | 3 May 10:39 2016
Picon

Bug#823305: RFP: python-jsontest -- Python metaclass for autogenerating tests from JSON files

Package: wnpp
Severity: wishlist
Control: block 823304 by -1

* Package name    : python-jsontest
  Version         : 1.2
  Upstream Author : Nick Barrett <pointlessrambler <at> gmail.com>
* URL             : https://github.com/Fizzadar/JsonTest
* License         : Expat
  Programming Lang: Python
  Description     : Python metaclass for autogenerating tests from JSON files

JsonTest is a tiny metaclass designed for automatically generating tests based off
JSON files. Originally built for testing ElasticQuery.

DS

Daniel Stender | 3 May 10:35 2016
Picon

Bug#823304: pyinfra: build-time tests should be running

Package: pyinfra
Version: 0.1~dev19-1
Severity: wishlist

The build time tests of pyinfra are currently disabled due to missing
jsontest. If that becomes available, testing should be activated.

DS

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

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

Versions of packages pyinfra depends on:
ii  libjs-sphinxdoc          1.3.6-2
ii  python3-colorama         0.3.7-1
ii  python3-dateutil         2.4.2-1
ii  python3-docopt           0.6.2-1
ii  python3-gevent           1.1.0-2
ii  python3-jinja2           2.8-1
ii  python3-paramiko         1.16.0-1
ii  python3-six              1.10.0-3
ii  python3-termcolor        1.1.0-1
(Continue reading)

Michele Orru` | 3 May 10:18 2016
Picon

Bug#823303: docker.io: Group `docker` already existing makes installation fail

Package: docker.io
Version: 1.8.3~ds1-2
Severity: normal

Dear Maintainer,

When trying to install docker, if the group "docker" already exists, apt fails
with the following error:

$ sudo apt install docker.io
Reading package lists... Done
Building dependency tree
Reading state information... Done
docker.io is already the newest version (1.8.3~ds1-2).
0 upgraded, 0 newly installed, 0 to remove and 84 not upgraded.
1 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 docker.io (1.8.3~ds1-2) ...
addgroup: The group `docker' already exists as a system group. Exiting.
Job for docker.service failed because the control process exited with error
code. See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
dpkg: error processing package docker.io (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 docker.io
E: Sub-process /usr/bin/dpkg returned an error code (1)

Instead, I would have expected instead apt to ignore the return code of addgroup
(Continue reading)

Tobias Frost | 3 May 10:13 2016
Picon

Bug#822322: openmeeg: please switch to vtk6

Package: src:openmeeg
Followup-For: Bug #822322
Control: retitle -1 openmeeg: please drop B-D alternative on vtk5

Hi Yaroslav,

Thanks for the upload of openmeeg to experimental, and hoping the best that it
"feels well" there as you wrote in #809671 ;-)

However let me reopen this bug and downgrade its severity because of this
changelog entry:

 bdepend on vtk6 (allowing vtk5 as alternative) (Closes: #822322)

vtk5 will be removed very soon and vtk6 is even available in jessie,
so this alternative can really go away. It is also bpo safe.

So please just depend on vtk6 and drop the vtk5 entierly.

Many thanks,

Adam Borowski | 3 May 09:51 2016
Picon
Gravatar

Bug#823301: clementine: can't specify non-default sound sink anymore

Package: clementine
Version: 1.3~rc1-1+b1
Severity: normal

Hi!
I have multiple sound cards in my box, and I put Clementine on a different
one than everything else.  Ie, non-default.  I guess this is not an obscure
scenario, as it's natural to put music to the room while keeping all random
sounds to headphones.

However, when I go to the setting menu, I see only "Default device on Output
to a sound card via ALSA", "... JACK", "... OSS" and so on.  There's
apparently no way to specify the device beyond the plugin type.

This worked right in jessie, and, despite changes to Clementine, the old
config worked for me until I had to change the settings.  Digging through
backups, I see the proper stanza was:

.config/Clementine/Clementine.conf
[GstEngine]
sink=alsasink
device=hw:0

Too bad, this is not documented anywhere.  And even if it was, Clementine
is a 100% GUI program without any intentional backdoor interfaces.  Even all
other settings in the conf file are, as far as I tell, settable through the
GUI so this one seems to be an omission.  And a regression from jessie.

-- System Information:
Debian Release: stretch/sid
(Continue reading)

Paul Wise | 3 May 09:38 2016
Picon
Gravatar

Bug#823299: cpants_lint: ability to check the the current directory

Package: cpants-lint
Severity: wishlist
File: /usr/bin/cpants_lint
Control: affects -1 check-all-the-things
User: check-all-the-things <at> packages.debian.org
Usertags: new-check

It would be nice to be able to run cpants_lint on a directory (and
default to the current directory) instead of requiring an existing
tarball. This way it could be run during development too. It would need
to detect if the relevant files are present and exit if they are not.

--

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Gert Wollny | 3 May 09:25 2016
Picon
Gravatar

Bug#822785: dcmjpls: Big Endian Transfer Syntax not handlled correctly

Hi Andreas, 

I'll look into this shortly. Was AFK for a few days. 

Best, 
Gert 

Paul Wise | 3 May 09:35 2016
Picon
Gravatar

Bug#823298: cpants-lint: uninitialized value when checking uncompressed tarball

Package: cpants-lint
Version: 0.05-4
Severity: minor
File: /usr/bin/cpants_lint

When I run cpants_lint on an uncompressed tarball, it gives perl warnings:

$ apt-get source libwww-topica-perl
$ gunzip libwww-topica-perl_0.6.orig.tar.gz
$ cpants_lint libwww-topica-perl_0.6.orig.tar
Use of uninitialized value $vname in substitution (s///) at
/usr/share/perl5/Module/CPANTS/Analyse.pm line 123.
Use of uninitialized value $vname in string eq at /usr/share/perl5/Module/CPANTS/Analyse.pm line 125.
...

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (860, 'testing-proposed-updates'), 800, 'unstable-debug'), (800,
'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libapp-cpants-lint-perl depends on:
ii  libapp-cpants-lint-perl        0.05-4
ii  libmodule-cpants-analyse-perl  0.96-1
(Continue reading)

Tim Weippert | 3 May 09:32 2016

Bug#823297: libbotan: security update breaks monotone

Package: libbotan-1.10-0
Version: 1.10.8-2+deb8u1
Severity: grave
File: libbotan
Justification: renders package unusable

Dear Maintainer,

it seems that the recent security update breaks monotone:

mtn: Symbol `_ZTVN5Botan17DataSource_MemoryE' has different size in shared object, consider re-linking
mtn: updating along branch 'net.dn42.registry'
mtn: fatal signal: Segmentation fault
this is almost certainly a bug in monotone.
please send this error message, the output of 'mtn version --full',
and a description of what you were doing to <https://code.monotone.ca/p/monotone/issues/>
do not send a core dump, but if you have one, 
please preserve it in case we ask you for information from it.
Segmentation fault

Maybe the bug should also be sent to monotone for rebuilding?

cheers, 
tim

-- System Information:
Debian Release: 8.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
(Continue reading)


Gmane