Bug#802354: Help needed: Bug#802354: python-matplotlib-venn: FTBFS: AttributeError: can't set attribute

[Andreas Tille]

Hi Konstantin,

the full story of the problem with tests can be read here:

   https://bugs.debian.org/802354

I'll keep you updated if we find a solution but may be you might have
one yourself and can help solving the issue.

On Tue, Oct 20, 2015 at 07:37:57AM +0200, Olivier Sallou wrote:
> > The package fails to build:
> >
> > == 49 passed in 1.17 seconds 
> > ===
> > pybuild --test --test-pytest -i python{version} -p 3.4 --test 
> > --system=custom "--test-args=cp -a README.rst {home_dir}/build && cd 
> > {home_dir}/build && {interpreter} /python-matplotlib-venn-0.11/setup.py 
> > test && rm README.rst" --dir .
> > I: pybuild base:170: cp -a README.rst 
> > /python-matplotlib-venn-0.11/.pybuild/pythonX.Y_3.4/build && cd 
> > /python-matplotlib-venn-0.11/.pybuild/pythonX.Y_3.4/build && python3.4 
> > /python-matplotlib-venn-0.11/setup.py test && rm README.rst
> > running test
> > Traceback (most recent call last):
> >   File "/python-matplotlib-venn-0.11/setup.py", line 56, in 
> > entry_points=''
> I am not an expert, but it seems that entry_points is expected to be a
> dict ( = {} ) . As it is empty, I think it could just be removed.

The problematic chunk is probably not entry_points but rather

   self.test_args = []
 
> Olivier
> >   File "/usr/lib/python3.4/distutils/core.py", line 148, in setup
> > dist.run_commands()
> >   File "/usr/lib/python3.4/distutils/dist.py", line 955, in run_commands
> > self.run_command(cmd)
> >   File "/usr/lib/python3.4/distutils/dist.py", line 973, in run_command
> > cmd_obj.ensure_finalized()
> >   File "/usr/lib/python3.4/distutils/cmd.py", line 107, in ensure_finalized
> > self.finalize_options()
> >   File "/python-matplotlib-venn-0.11/setup.py", line 21, in finalize_options
> > self.test_args = []
> > AttributeError: can't set attribute

I tried a web search for this kind of error and found

   https://github.com/marshmallow-code/marshmallow/issues/300

which was solved in this patch

   
https://github.com/marshmallow-code/marshmallow/commit/1dbcae9c439d1a268717feb089351fc3c5180ac3#diff-2eeaed663bd0d25b7e608891384b7298

I tried to implement this idea in python-matplotlib-venn but the change
relies on the existence of a dir tests/ which is not part of the download
tarball (but of the upstream Git repository[1]).

If I apply the attached patch *and* copy the tests/ dir from upstream
Git repository I get


$ python3.4 setup.py test
running test
Searching for pytest
Best match: pytest 2.8.2
Processing pytest-2.8.2-py3.4.egg

Using 
/home/andreas/debian-maintain/repack/python-matplotlib-venn/python-matplotlib-venn-0.11/.eggs/pytest-2.8.2-py3.4.egg
Searching for py>=1.4.29
Best match: py 1.4.30
Processing py-1.4.30-py3.4.egg

Using 
/home/andreas/debian-maintain/repack/python-matplotlib-venn/python-matplotlib-venn-0.11/.eggs/py-1.4.30-py3.4.egg
running egg_info
writing dependency_links to matplotlib_venn.egg-info/dependency_links.txt
writing top-level names to matplotlib_venn.egg-info/top_level.txt
writing requirements to matplotlib_venn.egg-info/requires.txt
writing matplotlib_venn.egg-info/PKG-INFO
reading manifest file 'matplotlib_venn.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'matplotlib_venn.egg-info/SOURCES.txt'
running build_ext

--
Ran 0 tests in 0.000s

OK


Hmmm, doing all the things without any test run does not seem sensible.

I'm out of ideas now and any help would be welcome.

Kind regards

   Andreas.

[1] https://github.com/konstantint/matplotlib-venn

-- 
http://fam-tille.de
Description: https://github.com/marshmallow-code/marshmallow/commit/1dbcae9c439d1a268717feb089351fc3c5180ac3#diff-2eeaed663bd0d25b7e608891384b7298
Ends-Up-in:
running build_ext
Traceback (most recent call last):
  File "/build/python-matplotlib-venn-0.11/setup.py", line 41, in 
test_suite='tests'
  File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
  File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 146, in run
self.with_project_on_sys_path(self.run_tests)
  File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 127, in with_project_on_sys_path
func()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 167, in run_tests
testRunner=self._resolve_as_ep(self.test_runner),
  File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
self.parseArgs(argv)
  File "/usr/lib/python2.7/unittest/main.py", line 149, in parseArgs
self.createTests()
  File "/usr/lib/python2.7/unittest/main.py", line 158, in createTests
self.module)
  File "/usr/lib/python2.7/unittest/loader.py", line 130, 

Bug#802154: [Pkg-emacsen-addons] Bug#802154: sml-mode: fails to upgrade lenny -> squeeze -> wheezy -> jessie -> stretch

[Barak A. Pearlmutter]

> There's really no reasonable way to support versions of emacs older than
> 24 with the elpa based infrastructure. Indeed most emacs addon packages
> just won't work, never mind packaging issues. I guess a versioned depend
> on emacs would do the trick to pull in emacs24. If that seems like the
> right solution, I can have dh-elpa do it automatically.

That does indeed seem to me like the right solution.

However, I'd think it should be *possible* to install elpa- packages
without having emacs installed at all.  They might not be very useful,
but so be it.  This would argue for a "Recommends:" dependency.  And
also an "Enhances:".  And it would give dpkg a bit more freedom.

The current bug is somewhat deeper.  If the elpa infrastructure can't
handle emacs (< 24), then it probably shouldn't try to use it.  This
situation could come up if both emacs23 and emacs24 are installed, say,
with update-alternatives set to point to emacs23.  So even an explicit
dependency on emacs24 won't completely address the issue.  I think these
considerations argue for explicit version testing, or careful feature
testing, in the installation scripts.  Although maybe dh-elpa (>= 0.13)
is already doing this?

(I suppose this discussion should really be moved to debian-emacsen.)

--Barak.

Processed: Re: Bug#802321: gdal-bin: NetCDF-4 / HDF5 support broken in recent gdal

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible
Bug #802321 [gdal-bin] gdal-bin: NetCDF-4 / HDF5 support broken in recent gdal
Added tag(s) unreproducible.
> severity -1 important
Bug #802321 [gdal-bin] gdal-bin: NetCDF-4 / HDF5 support broken in recent gdal
Severity set to 'important' from 'grave'

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

Processed: Re: Bug#802413: xserver-xorg-video-qxl: FTBFS: Package 'libcacard', required by 'spice-server', not found

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed pending
Bug #802413 [libspice-server-dev] xserver-xorg-video-qxl: FTBFS: Package 
'libcacard', required by 'spice-server', not found
Added tag(s) pending and confirmed.

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

Bug#802321: gdal-bin: NetCDF-4 / HDF5 support broken in recent gdal

[Sebastiaan Couwenberg]

Control: tags -1 unreproducible
Control: severity -1 important

Hi Otakar,

Thanks for the nc file, can you also send the files used by gmt?

With JEJK_topoC9k_ZABA10mHbpv.nc I can now confirm that the issue is not
present in gdal (1.11.2+dfsg-3+b2) on unstable:

$ ncdump -h JEJK_topoC9k_ZABA10mHbpv.nc
netcdf JEJK_topoC9k_ZABA10mHbpv {
dimensions:
x = 501 ;
y = 601 ;
variables:
double x(x) ;
x:long_name = "x" ;
x:actual_range = -546000., -541000. ;
double y(y) ;
y:long_name = "y" ;
y:actual_range = -1073000., -1067000. ;
float z(y, x) ;
z:long_name = "z" ;
z:_FillValue = NaNf ;
z:actual_range = 2.38614749908447, 11.5756139755249 ;

// global attributes:
:Conventions = "COARDS, CF-1.5" ;
:title = "Produced by grdreformat" ;
:history = "grdreformat CRJK_topoC9c_ZABAGED10m.grd
Jesenik_topoC9_ZABAGED10mBpv.nc -R-546000/-541000/-1073000/-1067000" ;
:GMT_version = "5.1.2 (r14256) [64-bit]" ;
}

$ ncdump -k JEJK_topoC9k_ZABA10mHbpv.nc
netCDF-4

$ h5dump -n JEJK_topoC9k_ZABA10mHbpv.nc
HDF5 "JEJK_topoC9k_ZABA10mHbpv.nc" {
FILE_CONTENTS {
 group  /
 dataset/x
 dataset/y
 dataset/z
 }
}

$ gdalinfo JEJK_topoC9k_ZABA10mHbpv.nc
Driver: netCDF/Network Common Data Format
Files: JEJK_topoC9k_ZABA10mHbpv.nc
Size is 501, 601
Coordinate System is `'
Origin = (-546005.000,-1066995.000)
Pixel Size = (10.000,-10.000)
Metadata:
  NC_GLOBAL#Conventions=COARDS, CF-1.5
  NC_GLOBAL#GMT_version=5.1.2 (r14256) [64-bit]
  NC_GLOBAL#history=grdreformat CRJK_topoC9c_ZABAGED10m.grd
Jesenik_topoC9_ZABAGED10mBpv.nc -R-546000/-541000/-1073000/-1067000
  NC_GLOBAL#title=Produced by grdreformat
  x#actual_range={-546000,-541000}
  x#long_name=x
  y#actual_range={-1073000,-1067000}
  y#long_name=y
  z#_FillValue=nan
  z#actual_range={2.386147499084473,11.5756139755249}
  z#long_name=z
Corner Coordinates:
Upper Left  ( -546005.000,-1066995.000)
Lower Left  ( -546005.000,-1073005.000)
Upper Right ( -540995.000,-1066995.000)
Lower Right ( -540995.000,-1073005.000)
Center  ( -543500.000,-107.000)
Band 1 Block=167x151 Type=Float32, ColorInterp=Undefined
  NoData Value=nan
  Metadata:
_FillValue=nan
actual_range={2.386147499084473,11.5756139755249}
long_name=z
NETCDF_VARNAME=z

$ gmt grdreformat JEJK_topoC9k_ZABA10mHbpv.grd
JEJK_topoC9k_ZABA10mHbpv.xnc=nf
grdreformat: Error for input file: No such file
(JEJK_topoC9k_ZABA10mHbpv.grd)
grdreformat: Syntax error: Specify only one input and one output file

$ gmt grdinfo JEJK_topoC9k_ZABA10mHbpv.nc
JEJK_topoC9k_ZABA10mHbpv.nc: Title: Produced by grdreformat
JEJK_topoC9k_ZABA10mHbpv.nc: Command: grdreformat
CRJK_topoC9c_ZABAGED10m.grd Jesenik_topoC9_ZABAGED10mBpv.nc
-R-546000/-541000/-1073000/-1067000
JEJK_topoC9k_ZABA10mHbpv.nc: Remark:
JEJK_topoC9k_ZABA10mHbpv.nc: Gridline node registration used [Cartesian
grid]
JEJK_topoC9k_ZABA10mHbpv.nc: Grid file format: nf = GMT netCDF format
(32-bit float), COARDS, CF-1.5
JEJK_topoC9k_ZABA10mHbpv.nc: x_min: -546000 x_max: -541000 x_inc: 10
name: x nx: 501
JEJK_topoC9k_ZABA10mHbpv.nc: y_min: -1073000 y_max: -1067000 y_inc: 10
name: y ny: 601
JEJK_topoC9k_ZABA10mHbpv.nc: z_min: 2.38614749908 z_max: 11.5756139755
name: z
JEJK_topoC9k_ZABA10mHbpv.nc: scale_factor: 1 add_offset: 0
JEJK_topoC9k_ZABA10mHbpv.nc: format: netCDF-4 chunk_size: 167,151
shuffle: on deflation_level: 3

$ gmt grdinfo JEJK_topoC9k_ZABA10mHbpv.nc=gd
ERROR 1: nBlockYSize = 151, only 1 supported when reading bottom-up dataset
ERROR 1: JEJK_topoC9k_ZABA10mHbpv.nc, band 1: IReadBlock failed at X
offset 0, Y offset 0
ERROR 1: nBlockYSize = 151, only 1 supported when reading bottom-up dataset
ERROR 1: JEJK_topoC9k_ZABA10mHbpv.nc, band 1: IReadBlock failed at X
offset 1, Y offset 0
ERROR 1: nBlockYSize = 151, only 1 supported when reading bottom-up dataset
ERROR 1: JEJK_topoC9k_ZABA10mHbpv.nc, band 1: IReadBlock failed at X
offset 2, Y offset 0
ERROR 1: nBlockYSize = 151, only 1 supported when reading bottom-up dataset
ERROR 1: JEJK_topoC9k_ZABA10mHbpv.nc, band 1: IReadBlock failed at X
offset 0, Y offset 1
ERROR 1: nBlockYSize = 151, only 1 supported when reading bottom-up dataset
ERROR 1: JEJK_topoC9k_ZABA10mHbpv.nc, band 1: IReadBlock failed at X
offset 1, Y offset 1
ERROR 1: nBlockYSize = 151, only 1 supported when reading bottom-up dataset
ERROR 1: JEJK_topoC9k_ZABA10mHbpv.nc, band 1: IReadBlock failed at X
offset 2, Y offset 1
ERROR 1: nBlockYSize = 151, only 1 supported when reading bottom-up dataset
ERROR 1: JEJK_topoC9k_ZABA10mHbpv.nc, band 1: IReadBlock failed at X
offset 0, Y offset 2
ERROR 1: nBlockYSize = 151, only 1 supported when reading bottom-up dataset
ERROR 1: JEJK_topoC9k_ZABA10mHbpv.nc, band 1: IReadBlock failed at X
offset 1, Y offset 2
ERROR 1: nBlockYSize = 151, only 1 supported 

Bug#802413: xserver-xorg-video-qxl: FTBFS: Package 'libcacard', required by 'spice-server', not found

[Michael Tokarev]

Control: tag -1 + confirmed pending

20.10.2015 09:31, Julien Cristau wrote:
> Control: reassign -1 libspice-server-dev 0.12.6-2
> 
> Not our bug, as the error message says this is an issue with the package
> providing spice-server.pc.

>> configure: error: Package requirements (spice-server >= 0.6.3) were not met:
>>
>> Package 'libcacard', required by 'spice-server', not found

Oh.  This is the dependencies.  libspice-server-dev should depend
on libcacard-dev.  Will upload a new version asap.

Thanks,

/mjt

Bug#800095: marked as done (vdr-plugin-vnsiserver: FTBFS: sh: 0: Can't open /usr/share/vdr-dev/dependencies.sh)

[Debian Bug Tracking System]

Your message dated Tue, 20 Oct 2015 09:18:25 +0200
with message-id <5625eac1.6050...@e-tobi.net>
and subject line Re: Bug#800095: vdr-plugin-vnsiserver: FTBFS: sh: 0: Can't 
open /usr/share/vdr-dev/dependencies.sh
has caused the Debian Bug report #800095,
regarding vdr-plugin-vnsiserver: FTBFS: sh: 0: Can't open 
/usr/share/vdr-dev/dependencies.sh
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.)


-- 
800095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-vnsiserver
Version: 1.2.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

vdr-plugin-vnsiserver fails to build from source in unstable/amd64.
Looks like vdr-dev has a nicer interface for this now, eg.
/usr/bin/dh_vdrplugin_depends?

  [..]

 dh_auto_test -O--parallel
   fakeroot debian/rules binary
  dh binary --parallel
 dh_testroot -O--parallel
 dh_prep -O--parallel
 dh_auto_install -O--parallel
make -j14 install

DESTDIR=/tmp/buildd/vdr-plugin-vnsiserver-1.2.0/debian/vdr-plugin-vnsiserver
AM_UPDATE_INFO_DIR=no
  make[1]: Entering directory '/tmp/buildd/vdr-plugin-vnsiserver-1.2.0'
  install -D libvdr-vnsiserver.so
  
/tmp/buildd/vdr-plugin-vnsiserver-1.2.0/debian/vdr-plugin-vnsiserver/usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.2.0
  make[1]: Leaving directory '/tmp/buildd/vdr-plugin-vnsiserver-1.2.0'
 dh_install -O--parallel
 dh_installdocs -O--parallel
 dh_installchangelogs -O--parallel
 dh_perl -O--parallel
 dh_link -O--parallel
 dh_strip_nondeterminism -O--parallel
 dh_compress -O--parallel
 dh_fixperms -O--parallel
 dh_strip -O--parallel
 dh_makeshlibs -O--parallel
 dh_shlibdeps -O--parallel
 dh_installdeb -O--parallel
 debian/rules override_dh_gencontrol
  make[1]: Entering directory '/tmp/buildd/vdr-plugin-vnsiserver-1.2.0'
  sh /usr/share/vdr-dev/dependencies.sh
  sh: 0: Can't open /usr/share/vdr-dev/dependencies.sh
  debian/rules:13: recipe for target 'override_dh_gencontrol' failed
  make[1]: *** [override_dh_gencontrol] Error 127
  make[1]: Leaving directory '/tmp/buildd/vdr-plugin-vnsiserver-1.2.0'
  debian/rules:10: recipe for target 'binary' failed
  make: *** [binary] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/vdr-plugin-vnsiserver_1.2.0-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sat Sep 26 00:53:33 GMT+12 2015
I: pbuilder-time-stamp: 1443272013
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 9), pkg-config, vdr-dev (>= 1.7.17)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20290 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on pkg-config; however:
  Package pkg-config is not installed.
 pbuilder-satisfydepends-dummy depends on vdr-dev (>= 1.7.17); however:
  Package vdr-dev is not installed.

Setting up pbuilder-satisfydepends-dummy 

Bug#785893: marked as done (pidgin-sipe: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Tue, 20 Oct 2015 07:19:04 +
with message-id 
and subject line Bug#785893: fixed in pidgin-sipe 1.20.0-2
has caused the Debian Bug report #785893,
regarding pidgin-sipe: Please update to GStreamer 1.x
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.)


-- 
785893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pidgin-sipe
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package pidgin-sipe currently still depends on GStreamer 0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
Source: pidgin-sipe
Source-Version: 1.20.0-2

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

Debian distribution maintenance software
pp.
Jakub Adam  (supplier of updated pidgin-sipe package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Oct 2015 20:00:28 +0200
Source: pidgin-sipe
Binary: pidgin-sipe pidgin-sipe-dbg
Architecture: source
Version: 1.20.0-2
Distribution: unstable
Urgency: medium
Maintainer: Jakub Adam 
Changed-By: Jakub Adam 
Description:
 pidgin-sipe - Pidgin plugin for MS Office Communicator and MS Lync
 pidgin-sipe-dbg - Pidgin plugin for MS Office Communicator and MS Lync (debug 
symbo
Closes: 785893
Changes:
 pidgin-sipe (1.20.0-2) unstable; urgency=medium
 .
   * Fix lintian maintainer-script-without-set-e pedantic warning.
   * Switch to GStreamer 1.0 (Closes: #785893).
Checksums-Sha1:
 a484b15147d820c3b358946b1e4437568ed7347b 2135 pidgin-sipe_1.20.0-2.dsc
 4bf4d25ee271080c07634b78734d6063298664fb 11616 
pidgin-sipe_1.20.0-2.debian.tar.xz
Checksums-Sha256:
 6896bc3438ac80baa62a3c3fb505d79efab66f298d360cd87bdf08a8e2064661 2135 
pidgin-sipe_1.20.0-2.dsc
 415df38be0f25c0d9ac6830317a20bef27d47939ac8098b8c744069caece45bc 11616 
pidgin-sipe_1.20.0-2.debian.tar.xz
Files:
 eed642ccd074110fce91451812a6ba8f 2135 misc optional pidgin-sipe_1.20.0-2.dsc
 f908a94b4612eec7f41a70ffa768e62d 11616 misc optional 
pidgin-sipe_1.20.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWJea6AAoJEPNPCXROn13ZZzoP/j8ZyD7Hz1Ns3w0iiu9fR1Qp
S7VFN+nunyh8nuYt+E9hDIao/bMSDsOo3KCRGWop5VLzaAg5M81D578G/mRqrPmm
wP9oziQPds1IzCYj/sMpGU43u+2ZzTwBCyZY6qM9odspO7r+DIYtzwpuFv3jV+T5
DwwOxO6QVMUbb5NJ43+S4i/5dYqMK9r5nQuQ+nrOgLYtWNBtkQrJMkUsjSb6rZ6+
Lo2DMy2/n3eAqJF/mDrEc37NSHk96a5hNzjlUB/WesZDxStYmAPr+xIDNscPkLqE
UeBaXi2X9StFngexUneRcsDvw5GDspFbMs0TRDbAeufCq54YLApNjACER4bQVFvD
Ln0fg8nlwV69a0BROdCWs1f8sPsGfiACP0fPKjYHnaLX4j2CrjkiE4sbHNRvAUbA
dp2Ne/D8zLn1pOJbp4/snpmpce7WNiha660iWJxPinSTo6CZaw7ZU69J2LpRYUoC
UxKTH1QnfRm+qIcI39ZfkRO+4gqKhghjecmQTsKF7u0f0oWC0VwzFNXlOffvQ1sK
H27s9xsa7Z+Ep6Nn+ed9oGLVvydMulwd4PH7ZCUIYkU6+LYCdezJK6ZazZFwfXan
q6fih8ZzipOtYHdzkQqxFwzzUHOUPHJ0y/z/gTEMMjC5oF4QJPuA4E3EDCOycWmN
6FQ7QI7w1PWTEjEd/7gW
=WWnX
-END PGP SIGNATURE End Message ---

Bug#802413: marked as done (xserver-xorg-video-qxl: FTBFS: Package 'libcacard', required by 'spice-server', not found)

[Debian Bug Tracking System]

Your message dated Tue, 20 Oct 2015 07:19:22 +
with message-id 
and subject line Bug#802413: fixed in spice 0.12.6-3
has caused the Debian Bug report #802413,
regarding xserver-xorg-video-qxl: FTBFS: Package 'libcacard', required by 
'spice-server', not found
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.)


-- 
802413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xserver-xorg-video-qxl
Version: 0.1.4-3
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

checking for inotify_init1... yes
checking for SPICE... no
configure: error: Package requirements (spice-server >= 0.6.3) were not met:

Package 'libcacard', required by 'spice-server', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/xserver-xorg-video-qxl.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: spice
Source-Version: 0.12.6-3

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated spice package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Oct 2015 10:08:46 +0300
Source: spice
Binary: libspice-server1 libspice-server1-dbg libspice-server-dev
Architecture: source
Version: 0.12.6-3
Distribution: unstable
Urgency: medium
Maintainer: Liang Guo 
Changed-By: Michael Tokarev 
Description:
 libspice-server-dev - Header files and development documentation for 
spice-server
 libspice-server1 - Implements the server side of the SPICE protocol
 libspice-server1-dbg - Debugging symbols for libspice-server1
Closes: 802413
Changes:
 spice (0.12.6-3) unstable; urgency=medium
 .
   * update Standards-Version to 3.9.6 (no changes)
   * add libcacard-dev to libspice-server-dev dependencies
 (Closes: #802413)
Checksums-Sha1:
 8960c588c19fae02cc4da062a6389e08b236b36d 1938 spice_0.12.6-3.dsc
 00576f21488f619972bd240c59d825b8ba65ef17 8768 spice_0.12.6-3.debian.tar.xz
Checksums-Sha256:
 76dc2691bc7b42eb737999b30cb04b99ab0b67c9946525a72e35ff979898e2b0 1938 
spice_0.12.6-3.dsc
 2aec9afc95c24c44453a98260aabf3cee716f6942e63868ba924a4b1591f54d3 8768 
spice_0.12.6-3.debian.tar.xz
Files:
 589ae6d344a1f8f0fcda07bb8ac9d89c 1938 misc optional spice_0.12.6-3.dsc
 569c154e65849b78435ae24d184fc7cc 8768 misc optional 
spice_0.12.6-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWJejMAAoJEL7lnXSkw9fbH74IALF2NVqJd0xFQrvb6R0AQWQV
L7qu3CMgDhCShMQh+q7P1u4Au7/RpuUj7QM3UyoaTqkxd0Yybt31JtGv8J18DOxj
v0v+PiWGzTKekJO6Oj/HqkMGIJ//Lt7X130CeySS5c5TrFq6fnEfRnSUTpE0Ugok
XGlGHFIPq6XH6vRofkkSt+vMfl0Z3qSCly/zintEjtofBLNksnHsinSbzu17o1y+
lUevKamdCXUH/mpkAIa2qj4TXS9rDeXAdsaqEkiWrqR2Ewq/cJbwwaa2o1dwS3cW
9WngdA/YMU7g7EE+1RNPEi657mwevgiBpHK96jY6kAKKO50LdMkcaHUPKXazYyo=
=h1cQ
-END PGP SIGNATURE End Message ---

Bug#802452: nvidia-legacy-304xx-driver: X fails to start

[Luis Carvalheiro]

Package: nvidia-legacy-304xx-driver
Version: 304.125-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

since my last dist-upgrade, X fails to start when installing this package. When
system boots, the screen starts to flicker, and X doesn't come up.

The error lines in Xorg.0.log are:

EE) [mi] EQ overflowing.  Additional events will be discarded until existing
events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/Xorg (xorg_backtrace+0x4e) [0x55ad24a5685e]
(EE) 1: /usr/bin/Xorg (mieqEnqueue+0x253) [0x55ad24a38893]
(EE) 2: /usr/bin/Xorg (QueuePointerEvents+0x52) [0x55ad24912fd2]
(EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fbb45779000+0x60a7)
[0x7fbb4577f0a7]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fbb45779000+0x687d)
[0x7fbb4577f87d]
(EE) 5: /usr/bin/Xorg (0x55ad248a3000+0x96848) [0x55ad24939848]
(EE) 6: /usr/bin/Xorg (0x55ad248a3000+0xbf6f8) [0x55ad249626f8]
(EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7fbb4ca9e000+0x35180)
[0x7fbb4cad3180]
(EE) 8: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbb47071000+0x9ef42)
[0x7fbb4710ff42]
(EE) 9: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbb47071000+0xa0c43)
[0x7fbb47111c43]
(EE) 10: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbb47071000+0x11fb71)
[0x7fbb47190b71]
(EE) 11: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbb47071000+0x701bbd)
[0x7fbb47772bbd]
(EE) 12: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbb47071000+0x701daf)
[0x7fbb47772daf]
(EE) 13: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbb47071000+0x6f19b0)
[0x7fbb477629b0]
(EE) 14: /usr/bin/Xorg (0x55ad248a3000+0x13c351) [0x55ad249df351]
(EE) 15: /usr/bin/Xorg (0x55ad248a3000+0x131f87) [0x55ad249d4f87]
(EE) 16: /usr/bin/Xorg (0x55ad248a3000+0x5807f) [0x55ad248fb07f]
(EE) 17: /usr/bin/Xorg (0x55ad248a3000+0x5c1cb) [0x55ad248ff1cb]
(EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5)
[0x7fbb4cabfb45]
(EE) 19: /usr/bin/Xorg (0x55ad248a3000+0x465be) [0x55ad248e95be]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up
the stack.
(EE) [mi] mieq is *NOT* the cause.  It is a victim.
[  4371.719] [mi] Increasing EQ size to 1024 to prevent dropped events.
[  4371.720] [mi] EQ processing has resumed after 75 dropped events.
[  4371.720] [mi] This may be caused my a misbehaving driver monopolizing the
server's resources.


Relevant information from /var/log/messages:

Oct 19 10:16:14 munch gdm3: Unable to kill session worker process
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: X.Org X Server 1.17.2
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Release Date:
2015-06-16
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: X Protocol Version 11,
Revision 0
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Build Operating
System: Linux 4.2.0-1-amd64 x86_64 Debian
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Current Operating
System: Linux munch 4.2.0-1-amd64 #1 SMP Debian 4.2.1-2 (2015-09-27) x86_64
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-amd64 root=UUID=5018e4ce-ecb4-43eb-
95e0-81251baa6b4a ro quiet
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Build Date: 06 October
2015  07:27:47AM
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: xorg-server 2:1.17.2-3
(http://www.debian.org/support)
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Current version of
pixman: 0.33.2
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Before reporting
problems, check http://wiki.x.org
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: to make sure that you
have the latest version.
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Markers: (--) probed,
(**) from config file, (==) default setting,
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (++) from command
line, (!!) notice, (II) informational,
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (WW) warning, (EE)
error, (NI) not implemented, (??) unknown.
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (==) Log file:
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log", Time: Mon Oct 19 10:16:15 2015
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (==) Using config
file: "/etc/X11/xorg.conf"
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (==) Using system
config directory "/usr/share/X11/xorg.conf.d"
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (==) ServerLayout
"Layout0"
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (**) |-->Screen
"Screen0" (0)
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (**) |   |-->Monitor
"Monitor0"
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (**) |   |-->Device
"Device0"
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (**) |-->Input Device
"Keyboard0"
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (**) |-->Input Device
"Mouse0"
Oct 19 10:16:15 munch 

Bug#790252: libpgf: FTBFS with glibc 2.21 and gcc-5

[YunQiang Su]

On Tue, 7 Jul 2015 18:22:19 -0400 Martin Michlmayr  wrote:
> retitle 790252 libpgf: FTBFS with gcc-5 (symbols)
> thanks
>
> * Daniel Schepler  [2015-06-27 11:17]:
> > Source: libpgf
> > Version: 6.14.12-3
> > Severity: normal
> >
> > >From my pbuilder build log, using a setup preferring glibc and gcc-defaults
> > from experimental:
>
> I see the same with GCC 5 and the glibc from unstable.

I NMUed this package with the attached patch to 5-days delay.

>
> --
> Martin Michlmayr
> Linux for HP Helion, Hewlett-Packard
>
>


libpgf.debdiff
Description: Binary data

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Mon, Oct 19, 2015 at 10:11:45PM +0100, Luca Boccassi wrote:

> Maybe there's some context I'm missing. Forgive me for asking, but are
> you sure this is due to the Nvidia driver packages or glx-alternatives?

Absolutely. This is Nvidia driver problem. Few days ago I conducted
specific experiment. After upgrading to latest version of all nvidia
and glx packages, I've downgraded only kernel module and after
reloading module the glx got working. But after rebooting system the
problem returned again. So not only kernel module is problem, but it
is main.

> Andreas, you use KDE if I'm not mistaken. Are you seeing any issues? Do

How many times again: this is not problem of KDE, plasma, kodi or any
other software using glx. This is problem of glx in nvidia driver. 

I am using xlock from very old package xlockmore-gl not included in
any of today's debian distributions. But it has two options
"-modelist allgl" and "-modelist all-allgl". First is for include glx
modes, second - to exclude ones. This is very good for testing glx,
because it explicitly points to glx as the source of problem when it
works with second option and doesn't work with the first one.

So it is certainly clear, that the source of our problems is glx
feature of nvdia driver. But the fact that You can't reproduce the
problem (if You can't, because You never mentioned this) may mean,
that problem is somehow hardware specific. In this case there are no
way to debug it as to ask us to do for You some experiments of Your
choice.

Here is my hardware:

lspci | grep -i nvidia
01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 635] 
(rev a1)
01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)

If this guess is not true and the problem is not hardware specific, then You
should try number of different software using glx to reproduce the
problem.

And finally it is possible, that at some point of investigation You
will understand necessity to escalate the problem to upstream.

###  Vladimir Stavrinov  ###

Bug#802321: gdal-bin: NetCDF-4 / HDF5 support broken in recent gdal

[otas]

Hi Bas,

On Mon, 19 Oct 2015 20:00:06 +0200, Sebastiaan Couwenberg wrote:
Do you have another testing machine perhaps that hasn't been updated 
yet?



Unfortunately not.

The issue is related to GMT 5.1.2 I'm using "in production" on my 
system (Debian Stretch). I have a MS Windows computer too with GMT 5.1, 
where the issue with NetCDF-4 format is not present.


Under wheezy, there is GMT 4.5.7 which is not so far dependent on gdal.
So I can issue under wheezy (on the same sample grid)

$ GMT grdinfo JEJK_topoC9k_ZABA10mHbpv.nc
JEJK_topoC9k_ZABA10mHbpv.nc: Title: Produced by grdreformat
JEJK_topoC9k_ZABA10mHbpv.nc: Command: grdreformat 
CRJK_topoC9c_ZABAGED10m.grd Jesenik_topoC9_ZABAGED10mBpv.nc 
-R-546000/-541000/-1073000/-1067000

JEJK_topoC9k_ZABA10mHbpv.nc: Remark:
JEJK_topoC9k_ZABA10mHbpv.nc: Gridline node registration used
JEJK_topoC9k_ZABA10mHbpv.nc: Grid file format: nf (# 18) GMT netCDF 
format (float)  (COARDS-compliant) [DEFAULT]
JEJK_topoC9k_ZABA10mHbpv.nc: x_min: -546000 x_max: -541000 x_inc: 10 
name: x nx: 501
JEJK_topoC9k_ZABA10mHbpv.nc: y_min: -1073000 y_max: -1067000 y_inc: 10 
name: y ny: 601
JEJK_topoC9k_ZABA10mHbpv.nc: z_min: 2.38614749908 z_max: 11.5756139755 
name: z

JEJK_topoC9k_ZABA10mHbpv.nc: scale_factor: 1 add_offset: 0

without any problem, because GMT4 applies directly own internal 
routines (or netcdf library functions) to recognize and import NetCDF-4 
raster data. However, the forced use of gdal input routines in GMT4 
brings a problem again (under wheezy):


$ GMT grdinfo JEJK_topoC9k_ZABA10mHbpv.nc=gd

terminates with SIGSEGV.

Take a closer look at gdal:

$ gdalinfo JEJK_topoC9k_ZABA10mHbpv.nc
HDF5-DIAG: Error detected in HDF5 (1.8.8) thread 140136550176640:
  #000: ../../../src/H5Ddeprec.c line 231 in H5Dopen1(): not found
major: Dataset
minor: Object not found
  #001: ../../../src/H5Gloc.c line 430 in H5G_loc_find(): can't find 
object

major: Symbol table
minor: Object not found
  #002: ../../../src/H5Gtraverse.c line 861 in H5G_traverse(): internal 
path traversal failed

major: Symbol table
minor: Object not found
  #003: ../../../src/H5Gtraverse.c line 641 in H5G_traverse_real(): 
traversal operator failed

major: Symbol table
minor: Callback failed
  #004: ../../../src/H5Gloc.c line 385 in H5G_loc_find_cb(): object 
'xx' doesn't exist

major: Symbol table
minor: Object not found
HDF5-DIAG: Error detected in HDF5 (1.8.8) thread 140136550176640:
  #000: ../../../src/H5D.c line 391 in H5Dclose(): not a dataset
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.8) thread 140136550176640:
  #000: ../../../src/H5Ddeprec.c line 231 in H5Dopen1(): not found
major: Dataset
minor: Object not found
  #001: ../../../src/H5Gloc.c line 430 in H5G_loc_find(): can't find 
object

major: Symbol table
minor: Object not found
  #002: ../../../src/H5Gtraverse.c line 861 in H5G_traverse(): internal 
path traversal failed

major: Symbol table
minor: Object not found
  #003: ../../../src/H5Gtraverse.c line 641 in H5G_traverse_real(): 
traversal operator failed

major: Symbol table
minor: Callback failed
  #004: ../../../src/H5Gloc.c line 385 in H5G_loc_find_cb(): object 
'yy' doesn't exist

major: Symbol table
minor: Object not found
HDF5-DIAG: Error detected in HDF5 (1.8.8) thread 140136550176640:
  #000: ../../../src/H5D.c line 391 in H5Dclose(): not a dataset
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.8) thread 140136550176640:
  #000: ../../../src/H5Ddeprec.c line 231 in H5Dopen1(): not found
major: Dataset
minor: Object not found
  #001: ../../../src/H5Gloc.c line 430 in H5G_loc_find(): can't find 
object

major: Symbol table
minor: Object not found
  #002: ../../../src/H5Gtraverse.c line 861 in H5G_traverse(): internal 
path traversal failed

major: Symbol table
minor: Object not found
  #003: ../../../src/H5Gtraverse.c line 641 in H5G_traverse_real(): 
traversal operator failed

major: Symbol table
minor: Callback failed
  #004: ../../../src/H5Gloc.c line 385 in H5G_loc_find_cb(): object 
'zz' doesn't exist

major: Symbol table
minor: Object not found
HDF5-DIAG: Error detected in HDF5 (1.8.8) thread 140136550176640:
  #000: ../../../src/H5D.c line 391 in H5Dclose(): not a dataset
major: Invalid arguments to routine
minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.8.8) thread 140136550176640:
  #000: ../../../src/H5Ddeprec.c line 231 in H5Dopen1(): not found
major: Dataset
minor: Object not found
  #001: ../../../src/H5Gloc.c line 430 in H5G_loc_find(): can't find 
object

major: Symbol table
minor: Object not found
  #002: ../../../src/H5Gtraverse.c line 861 in H5G_traverse(): internal 
path traversal failed

major: Symbol table
minor: Object not found
  #003: ../../../src/H5Gtraverse.c 

Bug#800660: Bug is still present with 3.18.1-1

[Raphael Hertzog]

Control: reopen -1 3.18.1-1

Hi,

I upgraded to 3.18.1-1 and I still can't use the session-started
GNOME Keyring to login into websites.

Passwords are correctly pre-filled but as soon as click on the
submit form, Iceweasel gets stuck.

Unfortunately, this time I don't have any error message in the
journal except this one:
oct. 20 11:22:53 x230-buxy gnome-session[1806]: ** (gnome-shell:1925):
CRITICAL **: remove_mnemonics: assertion 'label != NULL' failed

So the upstream fixes fixed the error messages but not my
real problem.

I am up-to-date with sid on all packages:
$ dpkg-query -W gnome-shell xul-ext-gnome-keyring gnome-keyring
gnome-keyring   3.18.1-1
gnome-shell 3.18.0-1
xul-ext-gnome-keyring   0.10-1

FTR someone reported the problem on the extension side too:
https://github.com/swick/mozilla-gnome-keyring/issues/31

What can be done to further debug the problem?

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#802458: gnome-software: fails to upgrade from 'jessie' - trying to overwrite /usr/share/dbus-1/services/org.freedesktop.PackageKit.service

[Andreas Beckmann]

Package: gnome-software
Version: 3.18.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', 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/ch-relationships.html#s-replaces

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

  Selecting previously unselected package gnome-software.
  Preparing to unpack .../gnome-software_3.18.2-1_amd64.deb ...
  Unpacking gnome-software (3.18.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gnome-software_3.18.2-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/share/dbus-1/services/org.freedesktop.PackageKit.service', which is also 
in package gnome-packagekit-session 3.14.0-1
  Processing triggers for fontconfig (2.11.0-6.3) ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...
  Processing triggers for libc-bin (2.19-18+deb8u1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/gnome-software_3.18.2-1_amd64.deb


cheers,

andreas


gnome-packagekit-session=3.14.0-1_gnome-software=3.18.2-1.log.gz
Description: application/gzip

Processed: Re: Bug#802347: mlpost: FTBFS: mlpost.mli: lexing: empty token

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ocaml
Bug #802347 [src:mlpost] mlpost: FTBFS: mlpost.mli: lexing: empty token
Bug reassigned from package 'src:mlpost' to 'ocaml'.
No longer marked as found in versions mlpost/0.8.1-6.
Ignoring request to alter fixed versions of bug #802347 to the same values 
previously set
> affects -1 mlpost
Bug #802347 [ocaml] mlpost: FTBFS: mlpost.mli: lexing: empty token
Added indication that 802347 affects mlpost

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

Bug#802347: mlpost: FTBFS: mlpost.mli: lexing: empty token

[Stéphane Glondu]

Control: reassign -1 ocaml
Control: affects -1 mlpost

Le 19/10/2015 19:48, Chris West (Faux) a écrit :
> [...]
> File "/mlpost-0.8.1/_build/mlpost.mli", line 4186:
> lexing: empty token
> 16 error(s) encountered
> Command exited with code 1.
> ocamlbuild.Makefile:198: recipe for target 'doc' failed
> make[2]: *** [doc] Error 10
> make[2]: Leaving directory '/mlpost-0.8.1'
> debian/rules:23: recipe for target 'override_dh_auto_install' failed

This is due to the reproducibility patch in ocaml adding .file
directives. It breaks ocamldoc -pp. The patch will have to be
reengineered. Meanwhile, I will amend it so that ocamldoc -pp works, but
it means that ocamlopt -pp will no longer be deterministic :-(

Cheers,

-- 
Stéphane

Processed: found 802347 in 4.02.3-2

[Debian Bug Tracking System]

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

> found 802347 4.02.3-2
Bug #802347 [ocaml] mlpost: FTBFS: mlpost.mli: lexing: empty token
Marked as found in versions ocaml/4.02.3-2.
> thanks
Stopping processing here.

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

Processed: tagging 802461

[Debian Bug Tracking System]

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

> tags 802461 + pending
Bug #802461 [dolphin4] dolphin4: fails to upgrade from 'jessie' - trying to 
overwrite /usr/lib/kde4/dolphinpart.so
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#802456: clang-tidy-3.6: fails to upgrade from 'testing' - trying to overwrite /usr/lib/llvm-3.6/bin/clang-tidy

[Sylvestre Ledru]

Le 20/10/2015 11:42, Andreas Beckmann a écrit :
> Package: clang-tidy-3.6
> Version: 1:3.6.2-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
> 
>>From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package clang-tidy-3.6.
>   Preparing to unpack .../clang-tidy-3.6_1%3a3.6.2-2_amd64.deb ...
>   Unpacking clang-tidy-3.6 (1:3.6.2-2) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/clang-tidy-3.6_1%3a3.6.2-2_amd64.deb (--unpack):
>trying to overwrite '/usr/lib/llvm-3.6/bin/clang-tidy', which is also in 
> package clang-3.6 1:3.6.2-1
>   dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>   Errors were encountered while processing:
>/var/cache/apt/archives/clang-tidy-3.6_1%3a3.6.2-2_amd64.deb
This is fixed in the svn.
(just like for 3.7)

Sylvestre

Bug#802465: qemu: Failure to build the qemu package from source, libnuma dependencies, spice dependencies etc.

[Thomas Dullien]

Package: qemu
Version: 1:2.4+dfsg-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

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

   * What led up to the situation?

I am trying to build the debian qemu package from source - I want to
investigate the problems described in the
qemu mailing list here: http://lists.gnu.org/archive/html/qemu-
devel/2014-08/msg02161.html

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

I issued the following commands:
apt-source qemu
apt-get build-dep qemu
debuild -b -uc -us

The configure step here fails with the error message:

ERROR: User requested feature spice
   configure was not able to find it.
   Install spice-server(>=0.12.0) and spice-protocol(>=0.12.3) devel

The subsequent compilation steps throw up problems at different steps:
cc -DHAS_LIBSSH2_SFTP_FSYNC -fPIE -DPIE -m64 -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-
decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing
-fno-common -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-D_FORTIFY_SOURCE=2
-DCONFIG_QEMU_DATAPATH='"/usr/share/qemu:/usr/share/seabios:/usr/lib/ipxe/qemu"'
-DVENDOR_DEBIAN -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-
externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-
style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-strong
-I/usr/include/p11-kit-1 -I/usr/include/p11-kit-1 -I/usr/include/libpng12 -o
config-temp/qemu-conf.exe config-temp/qemu-conf.c -Wl,-z,relro -Wl,-z,now -pie
-m64 -g -Wl,-z,relro -Wl,--as-needed
config-temp/qemu-conf.c:1:24: fatal error: sys/endian.h: No such file or
directory
(...)
cc -DHAS_LIBSSH2_SFTP_FSYNC -fPIE -DPIE -m64 -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-
decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing
-fno-common -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-D_FORTIFY_SOURCE=2
-DCONFIG_QEMU_DATAPATH='"/usr/share/qemu:/usr/share/seabios:/usr/lib/ipxe/qemu"'
-DVENDOR_DEBIAN -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-
externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-
style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-strong
-I/usr/include/p11-kit-1 -I/usr/include/p11-kit-1 -I/usr/include/libpng12 -o
config-temp/qemu-conf.exe config-temp/qemu-conf.c -Wl,-z,relro -Wl,-z,now -pie
-m64 -g -Wl,-z,relro -Wl,--as-needed
/tmp/cc4crmnD.o: In function `main':
/home/thomas/Desktop/sources/qemu-2.4+dfsg/qemu-build/config-temp/qemu-
conf.c:4: undefined reference to `timer_create'

   * What was the outcome of this action?

I failed to build the package from source.

   * What outcome did you expect instead?

I would like for the package to be built :-)

PS: Thanks a ton for the work you're doing!



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

Kernel: Linux 4.1.0-2-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 qemu depends on:
ii  qemu-system  1:2.4+dfsg-4
ii  qemu-user1:2.4+dfsg-4
ii  qemu-utils   1:2.4+dfsg-4

qemu recommends no packages.

Versions of packages qemu suggests:
pn  qemu-user-static  

-- no debconf information

Bug#802467: bijiben: Crash on startup

[Denis Rodrigues Ferreira]

Package: bijiben
Version: 3.18.1-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

Bijiben don't start. When call in a terminal it show:

$ bijiben

** (bijiben:30342): WARNING **: Unable to connect to EDS: Error calling
StartServiceByName for org.gnome.evolution.dataserver.Sources5:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute
program org.gnome.evolution.dataserver.Sources5: No such file or directory

** (bijiben:30342): WARNING **: Cannot initialize BijiManager: Error calling
StartServiceByName for org.gnome.evolution.dataserver.Sources5:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute
program org.gnome.evolution.dataserver.Sources5: No such file or directory

Debian Stretch
bijiben version: 3.18.1-1

Kernel version: 4.2.0-1-686-pae

Locale: en_US.UTF-8




-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.2.0-1-686-pae (SMP w/2 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 bijiben depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  libc62.19-22
ii  libcairo-gobject21.14.2-2
ii  libcairo21.14.2-2
ii  libecal-1.2-19   3.18.0-3
ii  libedataserver-1.2-213.18.0-3
ii  libgdk-pixbuf2.0-0   2.32.1-1
ii  libglib2.0-0 2.46.0-2
ii  libgoa-1.0-0b3.18.0-1
ii  libgtk-3-0   3.18.2-1
ii  libical1a1.0.1-0.1
ii  libpango-1.0-0   1.38.0-3
ii  libpangocairo-1.0-0  1.38.0-3
ii  libtracker-sparql-1.0-0  1.6.0-1
ii  libuuid1 2.27-3
ii  libwebkitgtk-3.0-0   2.4.9-2+b1
ii  libxml2  2.9.2+zdfsg1-4
ii  libzeitgeist-2.0-0   0.9.14-2.2+b1
ii  tracker  1.6.0-1

bijiben recommends no packages.

bijiben suggests no packages.

-- no debconf information

Bug#802154: marked as done (sml-mode: fails to upgrade lenny -> squeeze -> wheezy -> jessie -> stretch)

[Debian Bug Tracking System]

Your message dated Tue, 20 Oct 2015 10:21:30 +
with message-id 
and subject line Bug#802154: fixed in sml-mode 6.7-2
has caused the Debian Bug report #802154,
regarding sml-mode: fails to upgrade lenny -> squeeze -> wheezy -> jessie -> 
stretch
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.)


-- 
802154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sml-mode
Version: 6.7-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'lenny' to 'squeeze' to 'wheezy' to 'jessie' to 'stretch'.
It installed fine in 'lenny', and upgraded to 'squeeze', 'wheezy' and
'jessie' successfully, but then the upgrade to 'stretch' failed.

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

  Setting up elpa-sml-mode (6.7-1) ...
  Install emacsen-common for emacs22
  emacsen-common: Handling install of emacsen flavor emacs22
  Wrote /etc/emacs22/site-start.d/00debian-vars.elc
  Wrote /usr/share/emacs22/site-lisp/debian-startup.elc
  Install elpa-sml-mode for emacs22
  install/sml-mode-6.7: Handling install of emacsen flavor emacs22
  install/sml-mode-6.7: byte-compiling for emacs22
  Warning: Could not find simple.el nor simple.elc
  Loading 00debian-vars...
  Loading /etc/emacs/site-start.d/50sml-mode.el (source)...
  Package sml-mode removed but not purged.  Skipping setup.
  Cannot open load file: package
  ERROR: install script from elpa-sml-mode package failed
  dpkg: error processing package elpa-sml-mode (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


sml-mode_6.7-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sml-mode
Source-Version: 6.7-2

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

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated sml-mode 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: SHA1

Format: 1.8
Date: Tue, 20 Oct 2015 10:40:52 +0100
Source: sml-mode
Binary: elpa-sml-mode sml-mode
Architecture: source all
Version: 6.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacs addons team 

Changed-By: Barak A. Pearlmutter 
Description:
 elpa-sml-mode - Emacs major mode for editing Standard ML programs
 sml-mode   - Transition package, sml-mode to elpa-sml-mode
Closes: 802154
Changes:
 sml-mode (6.7-2) unstable; urgency=medium
 .
   * rebuild with newer dh-elpa, this should (closes: #802154)
Checksums-Sha1:
 55d3a3b8ff7ad89d7792bf6e62591b0ba44f8317 2000 sml-mode_6.7-2.dsc
 8e4409694a1ea505ef13092fc9d2905ca6a5ed40 5116 sml-mode_6.7-2.debian.tar.xz
 f971171c829d4ebc6983d259285caa3f448b2a94 37686 elpa-sml-mode_6.7-2_all.deb
 5bc13e7edf0bfb0e4f7fbe6eaed142e2b0d61057 4516 sml-mode_6.7-2_all.deb
Checksums-Sha256:
 a0bb5443fc2ce96018004d528c2b9bfc0001ed8e6a3a2b00c819aebfc31b49b8 2000 
sml-mode_6.7-2.dsc
 05aeb95359bda7a21a728c505721ae19b0194fa439420923bc890fe6fbc9c137 5116 
sml-mode_6.7-2.debian.tar.xz
 9c42ef20454c1c870e6d75ac04abdee4c9830ac280c3b4a02f2f9796573b0226 37686 
elpa-sml-mode_6.7-2_all.deb
 3f7dbc9054ce722e2f6fd17a825c539a19b319412845390a35d3d4db3b0752a7 4516 
sml-mode_6.7-2_all.deb
Files:
 19015a775d6a5fe0ab9e99470405adee 2000 editors optional sml-mode_6.7-2.dsc
 c3f663d4d1fb770639fc2286d86ee98b 5116 editors optional 
sml-mode_6.7-2.debian.tar.xz
 11bb5e9f34acd5c9275db58fc02304db 37686 editors optional 
elpa-sml-mode_6.7-2_all.deb
 957e39848182a8f12be5b4790c243a61 4516 editors optional sml-mode_6.7-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWJg3CAAoJEBJbV0deGQ0YQGIQAJy79bV29GBEOeafbWa/WACy
roY9lVEdCbU2kdTxh9v2tmDjwT7AGStPspVV4lu3xmQ+F1iCzhD9iQL6xqunuURn
vhWt0L3LqVRjQrA/sEM2cuvaTlLou4xb30xD3pje69Dj5+Q9vCYYoY9zUvOAw+k2

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Miguel Angel Rojas]

>
>
> I must first say that I am absolutely not familiar with KDE, the QT
> environment and how it works. But the thread that raises the abort
> doesn't look like it's in the GL libraries code:
>
> Maybe there's some context I'm missing. Forgive me for asking, but are
> you sure this is due to the Nvidia driver packages or glx-alternatives?
>
>
Hi Luca,

But indeed, it is! I conducted the same experiments as Vladimir did with
the same result. Something is wrong with the glx beyond 0.6.x (bad
packaging, new API, new behavior? I don't know). I would recommend to
reproduce as it is very easy to do it and you will see what we are talking
about.

Talking about Bug #799948, is there a reason why sddm user should be
included in video? (because it seems to be the workaround) If so, someone
should notify sddm guys that is somehow required due to new upstream
requirement in nvidia glx packages. We don't have a clear explanation about
it.

Regards

Bug#802456: clang-tidy-3.6: fails to upgrade from 'testing' - trying to overwrite /usr/lib/llvm-3.6/bin/clang-tidy

[Andreas Beckmann]

Package: clang-tidy-3.6
Version: 1:3.6.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package clang-tidy-3.6.
  Preparing to unpack .../clang-tidy-3.6_1%3a3.6.2-2_amd64.deb ...
  Unpacking clang-tidy-3.6 (1:3.6.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/clang-tidy-3.6_1%3a3.6.2-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/llvm-3.6/bin/clang-tidy', which is also in 
package clang-3.6 1:3.6.2-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/clang-tidy-3.6_1%3a3.6.2-2_amd64.deb


cheers,

Andreas


clang-3.6=1%3.6.2-1_clang-tidy-3.6=1%3.6.2-2.log.gz
Description: application/gzip

Bug#802461: dolphin4: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/kde4/dolphinpart.so

[Andreas Beckmann]

Package: dolphin4
Version: 4:15.08.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' 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/ch-relationships.html#s-replaces

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

  Selecting previously unselected package dolphin4.
  Preparing to unpack .../dolphin4_4%3a15.08.2-1_amd64.deb ...
  Unpacking dolphin4 (4:15.08.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/dolphin4_4%3a15.08.2-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/kde4/dolphinpart.so', which is also in package 
dolphin 4:4.14.2-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

andreas


dolphin=4%4.14.2-1_dolphin4=4%15.08.2-1.log.gz
Description: application/gzip

Processed: bug 801659 is forwarded to m...@overmeer.net

[Debian Bug Tracking System]

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

> forwarded 801659 m...@overmeer.net
Bug #801659 [libxml-compile-dumper-perl] libxml-compile-dumper-perl: depends on 
libdata-dump-streamer-perl, broken by perl 5.22
Set Bug forwarded-to-address to 'm...@overmeer.net'.
> thanks
Stopping processing here.

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

Bug#802452: nvidia-legacy-304xx-driver: X fails to start

[Andreas Beckmann]

On 2015-10-20 11:10, Luis Carvalheiro wrote:
> Package: nvidia-legacy-304xx-driver
> Version: 304.125-2

This is not a recent (legacy) driver version. Or you didn't report the
bug on the system where it happened.

Please run
  reportbug -N 802452
in the failing system to collect system information.


Andreas

Bug#802487: aide crash (SIGSEGV) at beginning

[jpp]

Package: aide
Version: 0.16~a2.git20130520-3~bpo70+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

My version af "aide" crash at beginning with a SIGSEGV, even if I try "aide
--help'.
I launch "aide --help" with strace and the trace is very short :
-
execve("/usr/bin/aide", ["aide"], [/* 21 vars */]) = 0
uname({sys="Linux", node="filtre.jpp.fr", ...}) = 0
brk(0)  = 0x108b000
brk(0x108c1c0)  = 0x108c1c0
arch_prctl(ARCH_SET_FS, 0x108b8a0)  = 0
brk(0x10ad1c0)  = 0x10ad1c0
brk(0x10ae000)  = 0x10ae000
statfs("/sys/fs/selinux", 0x7ffdb40382e0) = -1 ENOENT (No such file or
directory)
statfs("/selinux", 0x7ffdb40382e0)  = -1 ENOENT (No such file or directory)
open("/proc/filesystems", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7effe0207000
read(3, "nodev\tsysfs\nnodev\trootfs\nnodev\tr"..., 1024) = 366
read(3, "", 1024)   = 0
close(3)= 0
munmap(0x7effe0207000, 4096)= 0
umask(0177) = 022
rt_sigaction(SIGBUS, {0x4120f0, [BUS], SA_RESTORER|SA_RESTART, 0x449fa0},
{SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGTERM, {0x4120f0, [TERM], SA_RESTORER|SA_RESTART, 0x449fa0},
{SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGUSR1, {0x4120f0, [USR1], SA_RESTORER|SA_RESTART, 0x449fa0},
{SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGUSR2, {0x4120f0, [USR2], SA_RESTORER|SA_RESTART, 0x449fa0},
{SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGHUP, {0x4120f0, [HUP], SA_RESTORER|SA_RESTART, 0x449fa0},
{SIG_DFL, [], 0}, 8) = 0
uname({sys="Linux", node="filtre.jpp.fr", ...}) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

System information :
CPU : corei3 4140
Mem: 16GB
System disk SSD Vertex
Raid 1 2 x 2GB seagate

Regards

JPPO



-- System Information:
Debian Release: 7.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.3 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

aide depends on no packages.

Versions of packages aide recommends:
ii  aide-common  0.16~a2.git20130520-3~bpo70+1

aide suggests no packages.

-- no debconf information

Processed: bumblebee: should support nvidia-legacy-{304,340}xx drivers, too

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 801598
Bug #802479 [bumblebee] bumblebee: should support nvidia-legacy-{304,340}xx 
drivers, too
802479 was not blocked by any bugs.
802479 was not blocking any bugs.
Added blocking bug(s) of 802479: 801598

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

Bug#799018: marked as done (xiphos: gtkhtml4.0 removed from Debian so FTBFS due to missing build-deps)

[Debian Bug Tracking System]

Your message dated Tue, 20 Oct 2015 12:51:34 +
with message-id 
and subject line Bug#799018: fixed in xiphos 4.0.4+dfsg1-1
has caused the Debian Bug report #799018,
regarding xiphos: gtkhtml4.0 removed from Debian so FTBFS due to missing 
build-deps
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.)


-- 
799018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xiphos
Version: 3.2.2+dfsg1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

I closed the removal bug for xiphos, #797564, based on the understanding that
it would be updated and ported away from gtkhtml4.0 soon.  Based on that, I've
gone ahead and removed gtkhtml4.0 since xiphos was the last blocker.

Scott K
--- End Message ---
--- Begin Message ---
Source: xiphos
Source-Version: 4.0.4+dfsg1-1

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

Debian distribution maintenance software
pp.
Daniel Glassey  (supplier of updated xiphos package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Oct 2015 21:31:23 +0100
Source: xiphos
Binary: xiphos xiphos-dbg xiphos-data
Architecture: source all amd64
Version: 4.0.4+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: CrossWire Packages 
Changed-By: Daniel Glassey 
Description:
 xiphos - environment for Bible reading, study, and research
 xiphos-data - data files for Xiphos Bible study software
 xiphos-dbg - debug symbols for Xiphos Bible study software
Closes: 769940 770713 783556 799018 801891
Changes:
 xiphos (4.0.4+dfsg1-1) unstable; urgency=medium
 .
   [ Unit 193 ]
   * New upstream release. (Closes: #783556)
 - Fixes many GTK3 incompatibilities. (Closes: #770713, #769940)
   * Bump Standards-Version to 3.9.6.
   * wrap-and-sort.
   * d/control:
 - Drop gsettings-desktop-schemas-dev | gconf2-common, and libgtkhtml*
   Closes: #799018
 - Add docbook-utils, libbiblesync-dev, and libgtk-3-dev.
 - Bump libsword-dev min dep to 1.7.3.
 - Add myself to uploaders.
   * d/rules:
 - During repack, also remove build-win32/ and debian/
 - Remove the builddeb override, not needed.
 - Install upstream changelog.
 - Enable --verbose build.
 - Pass --enable-webkit-editor, --gtk=3 and --debug-level=release.
 - Set DEB_LDFLAGS_MAINT_APPEND to only link as needed.
 - Don't remove src/examples/ipc-interface.xml in the cleaning stage.
   * d/Debian, d/clean, d/README.*: Drop.
   * d/source.lintian-overrides: Remove debian-watch-file-should-mangle-version.
   * d/watch: Update to find new releases, and filter out testing releases.
   * d/xiphos.install: Install usr/bin/xiphos-nav
   * d/xiphos-data.install: Install xiphos.appdata.xml.
 .
   [ Daniel Glassey ]
   * d/control: Vcs now pkg-crosswire git
add myself as uploader
remove xnox and Jonathan from uploaders
type in xiphos-dbg description
   * New release for sword transition. (Closes: #801891)
Checksums-Sha1:
 8feb1215a69b54fd5a81fb31c36e6aacd464cff8 2275 xiphos_4.0.4+dfsg1-1.dsc
 63ad3e3a7f87f1e3f5eae0b4f3beb0c9e19de5f2 8050881 xiphos_4.0.4+dfsg1.orig.tar.gz
 90fb9853ba0ae18e25e5d4fdd45d3be32219be02 10092 
xiphos_4.0.4+dfsg1-1.debian.tar.xz
 c12e67884023b76c1ba6f5c101b7ef392987339a 4950872 
xiphos-data_4.0.4+dfsg1-1_all.deb
 545f585a5817969cdeafe0c5fb8a2ddfbe6ccdc0 1461128 
xiphos-dbg_4.0.4+dfsg1-1_amd64.deb
 d083f46ad51f996753b6ee779909e5025b124e55 347472 xiphos_4.0.4+dfsg1-1_amd64.deb
Checksums-Sha256:
 8344c2f09258431fa924201795404ac063f3392a151a69a5651c68498a416a80 2275 
xiphos_4.0.4+dfsg1-1.dsc
 3a7191bd763060fde7aab4b27ee4fa1084f9ab8391e75d0809f2a48a170c44e9 8050881 
xiphos_4.0.4+dfsg1.orig.tar.gz
 e24612d5e75f400f9e1e37a4dae95efdc6ec27a875dae2829c09415dc990792a 10092 
xiphos_4.0.4+dfsg1-1.debian.tar.xz
 

Bug#802347: marked as done (mlpost: FTBFS: mlpost.mli: lexing: empty token)

[Debian Bug Tracking System]

Your message dated Tue, 20 Oct 2015 11:34:48 +
with message-id 
and subject line Bug#802347: fixed in ocaml 4.02.3-5
has caused the Debian Bug report #802347,
regarding mlpost: FTBFS: mlpost.mli: lexing: empty token
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.)


-- 
802347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mlpost
Version: 0.8.1-6
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

+ /usr/bin/ocamldoc -dump mlpost.odoc -hide Mlpost -g customdoc/img.cmo -I 
/usr/lib/ocaml/lablgtk2 -I /usr/lib/ocaml/cairo -I /usr/lib/ocaml/cairo -pp 
'./myocamlmacroparser.byte  -D CAIRO -D CONCRETE' -I dvi -I backend -I concrete 
-I gui mlpost.mli
File "/mlpost-0.8.1/_build/mlpost.mli", line 4101:
lexing: empty token
File "/mlpost-0.8.1/_build/mlpost.mli", line 4107:
lexing: empty token
File "/mlpost-0.8.1/_build/mlpost.mli", line 4126:
lexing: empty token

...

lexing: empty token
File "/mlpost-0.8.1/_build/mlpost.mli", line 4186:
lexing: empty token
16 error(s) encountered
Command exited with code 1.
ocamlbuild.Makefile:198: recipe for target 'doc' failed
make[2]: *** [doc] Error 10
make[2]: Leaving directory '/mlpost-0.8.1'
debian/rules:23: recipe for target 'override_dh_auto_install' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/mlpost.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: ocaml
Source-Version: 4.02.3-5

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated ocaml package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Oct 2015 11:41:11 +0200
Source: ocaml
Binary: ocaml-nox ocaml ocaml-base-nox ocaml-base ocaml-native-compilers 
ocaml-source ocaml-interp ocaml-compiler-libs ocaml-mode
Architecture: source amd64 all
Version: 4.02.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Description:
 ocaml  - ML language implementation with a class-based object system
 ocaml-base - Runtime system for OCaml bytecode executables
 ocaml-base-nox - Runtime system for OCaml bytecode executables (no X)
 ocaml-compiler-libs - OCaml interpreter and standard libraries
 ocaml-interp - OCaml interactive interpreter and standard libraries
 ocaml-mode - major mode for editing Objective Caml in Emacs
 ocaml-native-compilers - Native code compilers of the OCaml suite (the .opt 
ones)
 ocaml-nox  - ML implementation with a class-based object system (no X)
 ocaml-source - Sources for Objective Caml
Closes: 802347
Changes:
 ocaml (4.02.3-5) unstable; urgency=medium
 .
   * Fix ocamldoc with -pp (Closes: #802347)
Checksums-Sha1:
 aab410b60e94b7aea32c45f200816e17bb7b25ad 2686 ocaml_4.02.3-5.dsc
 2f15d4dd812ee5ed4740b6ae7a267bb7b80e4970 45316 ocaml_4.02.3-5.debian.tar.xz
 54906b4b3dd67acc544adc60464db1f359df882e 538376 
ocaml-base-nox_4.02.3-5_amd64.deb
 c79b25f14cbd29956fed492d08fa420630f8ef7c 132650 ocaml-base_4.02.3-5_amd64.deb
 87229e77e1b95307be6008c35781ecf231e91d84 9626358 
ocaml-compiler-libs_4.02.3-5_amd64.deb
 53656d7574ac7b1ff762ff0b4114a6032effd4df 360246 ocaml-interp_4.02.3-5_amd64.deb
 e51b57c476c9548ea5c9b3a965013161bd55af42 136446 ocaml-mode_4.02.3-5_all.deb
 c03b43a241b1a620bf6b2568e959a1ee59809873 2533284 
ocaml-native-compilers_4.02.3-5_amd64.deb
 58b0f2800fbb266fdd9f3ee4d49408a6dc5d7fdd 5992890 ocaml-nox_4.02.3-5_amd64.deb
 a01a1e0819a1bb03c7eff6ea93d45871238ff5ea 2160286 ocaml-source_4.02.3-5_all.deb
 

Bug#802452: nvidia-legacy-304xx-driver: X fails to start

[Andreas Beckmann]

On 2015-10-20 13:32, Luis Carvalheiro wrote:
> Dear Maintainer,
> 
> I had to apt-get remove --purge nvidia* to get a working graphical
> environment. I used reportbug in a GUI to report it after that. When i run
> reportbug -N 802452 i can't add nothing more. I reported the bug in the
> failing system.

Well, that's not the failing system any more.

> Do you want me to install nvidia-legacy-304xx-driver, switch to a
> text-based reportbug and fill a new bug report?

That would be great. Just reportbug -N 802452 should collect the info.


Andreas

Bug#802465: marked as done (qemu: Failure to build the qemu package from source, libnuma dependencies, spice dependencies etc.)

[Debian Bug Tracking System]

Your message dated Tue, 20 Oct 2015 15:41:27 +0300
with message-id <56263677.5000...@msgid.tls.msk.ru>
and subject line Re: Bug#802465: qemu: Failure to build the qemu package from 
source, libnuma dependencies, spice dependencies etc.
has caused the Debian Bug report #802465,
regarding qemu: Failure to build the qemu package from source, libnuma 
dependencies, spice dependencies etc.
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.)


-- 
802465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu
Version: 1:2.4+dfsg-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

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

   * What led up to the situation?

I am trying to build the debian qemu package from source - I want to
investigate the problems described in the
qemu mailing list here: http://lists.gnu.org/archive/html/qemu-
devel/2014-08/msg02161.html

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

I issued the following commands:
apt-source qemu
apt-get build-dep qemu
debuild -b -uc -us

The configure step here fails with the error message:

ERROR: User requested feature spice
   configure was not able to find it.
   Install spice-server(>=0.12.0) and spice-protocol(>=0.12.3) devel

The subsequent compilation steps throw up problems at different steps:
cc -DHAS_LIBSSH2_SFTP_FSYNC -fPIE -DPIE -m64 -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-
decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing
-fno-common -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-D_FORTIFY_SOURCE=2
-DCONFIG_QEMU_DATAPATH='"/usr/share/qemu:/usr/share/seabios:/usr/lib/ipxe/qemu"'
-DVENDOR_DEBIAN -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-
externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-
style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-strong
-I/usr/include/p11-kit-1 -I/usr/include/p11-kit-1 -I/usr/include/libpng12 -o
config-temp/qemu-conf.exe config-temp/qemu-conf.c -Wl,-z,relro -Wl,-z,now -pie
-m64 -g -Wl,-z,relro -Wl,--as-needed
config-temp/qemu-conf.c:1:24: fatal error: sys/endian.h: No such file or
directory
(...)
cc -DHAS_LIBSSH2_SFTP_FSYNC -fPIE -DPIE -m64 -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-
decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing
-fno-common -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-D_FORTIFY_SOURCE=2
-DCONFIG_QEMU_DATAPATH='"/usr/share/qemu:/usr/share/seabios:/usr/lib/ipxe/qemu"'
-DVENDOR_DEBIAN -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-
externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-
style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-strong
-I/usr/include/p11-kit-1 -I/usr/include/p11-kit-1 -I/usr/include/libpng12 -o
config-temp/qemu-conf.exe config-temp/qemu-conf.c -Wl,-z,relro -Wl,-z,now -pie
-m64 -g -Wl,-z,relro -Wl,--as-needed
/tmp/cc4crmnD.o: In function `main':
/home/thomas/Desktop/sources/qemu-2.4+dfsg/qemu-build/config-temp/qemu-
conf.c:4: undefined reference to `timer_create'

   * What was the outcome of this action?

I failed to build the package from source.

   * What outcome did you expect instead?

I would like for the package to be built :-)

PS: Thanks a ton for the work you're doing!



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

Kernel: Linux 4.1.0-2-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 qemu depends on:
ii  qemu-system  1:2.4+dfsg-4
ii  qemu-user1:2.4+dfsg-4
ii  qemu-utils   1:2.4+dfsg-4

qemu recommends no packages.

Versions of packages qemu suggests:
pn  qemu-user-static  

-- no debconf information
--- End Message ---
--- Begin Message ---
20.10.2015 11:54, Thomas Dullien wrote:
> Package: qemu
> Version: 1:2.4+dfsg-4
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> 
> I am 

Bug#802310: nvidia configuration changed w.r.t. bumblebee ...

[Andreas Beckmann]

I pushed a few commits for bumblebee that add the Debian specific
versioned dependency on glx-alternative-nvidia. Regarding the legacy
drivers: for now I only added them to the blacklist, let's do more on
this topic later. (BTW, why does bumblebe insist on loading
nvidia-current? That should be plain nvidia...)
Please give it some testing.


Andreas

Bug#802471: libopenraw1v5: Try to overwrite file in libopenraw1

[Christian Marillat]

Package: libopenraw1v5
Version: 0.0.9-3.6
Severity: serious

Dear Maintainer,

libopenraw1v5 must Conflicts/Replaces libopenraw1 :

Unpacking libopenraw1v5:i386 (0.0.9-3.6) ...
dpkg: error processing archive 
/var/cache/apt/archives/libopenraw1v5_0.0.9-3.6_i386.deb (--unpack):
 trying to overwrite '/usr/lib/i386-linux-gnu/libopenraw.so.1.6.0', which is 
also in package libopenraw1:i386 0.0.9-3.5+b2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for libc-bin (2.19-22) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libopenraw1v5_0.0.9-3.6_i386.deb

Christian

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

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

Bug#790271: Note: Fixed upstream

[Bjarni Runar Einarsson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello! Note that this bug has been fixed upstream and new
releases made to fix this and other bugs. :-)

Cheers,
 - Bjarni

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJWJi7dAAoJEI4ANxYAz5SRdzwH/i3rME/acFIlwWoxHUhY+eUp
u0myigd4dS00Mcidrxz3VOBrNkHprhFi+mCJ+7Hn1luIHeI9w6ASNUHNkRFtjwYK
4tvDGRujYjr3n3qwRCuWAA+rHUXPvPg3arUBMAdJ7BvRnaioO7PyQhD5h6zvXxYY
g/beJ/upAdKRs/+0rx/LBOnn3tdPUC0WhxpiutMcOkvPwLv6eZ0c6Du4k86s7nNA
5L45u9gabPNs+22pb8JVHK3YHlaqxvYNvs5lUka24zp82gU5ErrUgXWtIthmbjhA
HiPrIZQdH3PSP3vAU+sWRZWh9j71vqo1agmnR4J/bkzpTESqs1+zFxSUPS2JmTU=
=n9Wg
-END PGP SIGNATURE-

Bug#801781: kate: Error in `kate': free(): invalid pointer

[Luca Ghio]

Could this be related to https://bugs.kde.org/show_bug.cgi?id=352627 ? I run 
into this bug with kate 4:15.08.1-1, and upgrading kate5-data to 4:15.08.2-1 
didn't solve the issue. Disabling "Autoload repositories" in Kate settings 
helped to stop Kate crashing when opening a file, inside a git repository, from 
Dolphin or from Kate itself, but it didn't help when opening a file (even 
outside a git repository) from a shell while the current directory of the shell 
is a git repository.

Bug#802474: Error in dist squeeze armel content list

[Andreas Hänel]

Package: release.debian.org
Severity: grave

When trying to install python on following release:

uname -a
Linux GeSyNAS 2.6.31.8.nv+v2 #1 Thu Apr 18 17:40:54 HKT 2013 armv5tel 
GNU/Linux


/etc/debian_version = 6.0.3

/etc/apt/sources.list =
deb http://ftp.us.debian.org/debian/ squeeze main
deb-src http://ftp.us.debian.org/debian/ squeeze main
deb http://security.debian.org/ squeeze/updates main
deb-src http://security.debian.org/ squeeze/updates main
deb http://ftp.us.debian.org/debian/ squeeze-updates main
deb-src http://ftp.us.debian.org/debian/ squeeze-updates main


One will get the error message:
root# apt-get install python
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer 
required:

  libpcap0.8 cracklib-runtime libcrack2 libcap-ng0 libavahi-client3 libnet1
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  python-minimal python2.6 python2.6-minimal
Suggested packages:
  python-doc python-tk python-profiler python2.6-doc python2.6-profiler
  binutils binfmt-support
The following NEW packages will be installed:
  python python-minimal python2.6 python2.6-minimal
0 upgraded, 4 newly installed, 0 to remove and 41 not upgraded.
2 not fully installed or removed.
Need to get 3,837 kB/4,040 kB of archives.
After this operation, 15.3 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Err http://ftp.us.debian.org/debian/ squeeze/main python2.6-minimal 
armel 2.6.6-8+b1

  404  Not Found [IP: 128.61.240.89 80]
Err http://ftp.us.debian.org/debian/ squeeze/main python2.6 armel 2.6.6-8+b1
  404  Not Found [IP: 128.61.240.89 80]
Failed to fetch 
http://ftp.us.debian.org/debian/pool/main/p/python2.6/python2.6-minimal_2.6.6-8+b1_armel.deb 
404  Not Found [IP: 128.61.240.89 80]
Failed to fetch 
http://ftp.us.debian.org/debian/pool/main/p/python2.6/python2.6_2.6.6-8+b1_armel.deb 
404  Not Found [IP: 128.61.240.89 80]
E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?



Reason for this ist that on the distribution server ftp.us.debian.org 
the list of packages

/debian/dists/squeeze/main/binary-armel/Packages.gz
contains e.g. python2.6-minimal_2.6.6-8+b1_armel.deb
but under
/debian/pool/main/p/python2.6/
only python2.6_2.6.6-8+b1_amd64.deb, python2.6_2.6.6-8+b1_i386.deb or 
python2.6_2.6.8-1.1_armel.deb are available.


Seems that the package list wasn't updated correctly.
Please correct this or provide a lazy to perform a workaround.

Thanks and cheers
Andy Hänel




---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Processed: Re: Bug#802474: Error in dist squeeze armel content list

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #802474 [release.debian.org] Error in dist squeeze armel content list
Bug reassigned from package 'release.debian.org' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #802474 to the same values 
previously set
Ignoring request to alter fixed versions of bug #802474 to the same values 
previously set
> forcemerge 801200 -1
Bug #801200 [ftp.debian.org] ftp.debian.org: 
/debian/dists/squeeze/main/binary-armel/Packages still exists
Bug #802474 [ftp.debian.org] Error in dist squeeze armel content list
Severity set to 'normal' from 'grave'
Merged 801200 802474

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

Bug#802474: Error in dist squeeze armel content list

[Adam D. Barratt]

Control: reassign -1 ftp.debian.org
Control: forcemerge 801200 -1

On 2015-10-20 13:25, Andreas Hänel wrote:

Package: release.debian.org
Severity: grave


The Release Team don't run the archive. Reassigning to ftp.debian.org.


When trying to install python on following release:

uname -a
Linux GeSyNAS 2.6.31.8.nv+v2 #1 Thu Apr 18 17:40:54 HKT 2013 armv5tel 
GNU/Linux


/etc/debian_version = 6.0.3

[...]

Err http://ftp.us.debian.org/debian/ squeeze/main python2.6-minimal
armel 2.6.6-8+b1
  404  Not Found [IP: 128.61.240.89 80]
Err http://ftp.us.debian.org/debian/ squeeze/main python2.6 armel 
2.6.6-8+b1

  404  Not Found [IP: 128.61.240.89 80]
Failed to fetch
http://ftp.us.debian.org/debian/pool/main/p/python2.6/python2.6-minimal_2.6.6-8+b1_armel.deb
404  Not Found [IP: 128.61.240.89 80]
Failed to fetch
http://ftp.us.debian.org/debian/pool/main/p/python2.6/python2.6_2.6.6-8+b1_armel.deb
404  Not Found [IP: 128.61.240.89 80]
E: Unable to fetch some archives, maybe run apt-get update or try with
--fix-missing?


Regards,

Adam

Bug#775257: marked as done (libiomp5: missing SONAME link /usr/lib/libiomp5.so -> libiomp5.so.5)

[Debian Bug Tracking System]

Your message dated Tue, 20 Oct 2015 12:31:48 +
with message-id 
and subject line Bug#775257: fixed in openmprtl 3.7.0-2
has caused the Debian Bug report #775257,
regarding libiomp5: missing SONAME link /usr/lib/libiomp5.so -> libiomp5.so.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.)


-- 
775257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libiomp5
Version: 0.20141212-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi Sylvestre,

libiomp5 in experimental misses the SONAME link, this must be shipped.
There are also no preinst/prerm scripts that would trigger ldconfig,
sounds like a missing debhelper call ...

Andreas
--- End Message ---
--- Begin Message ---
Source: openmprtl
Source-Version: 3.7.0-2

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated openmprtl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Oct 2015 13:57:07 +0200
Source: openmprtl
Binary: libiomp-dev libomp-dev libiomp5 libomp5 libiomp5-dbg libomp5-dbg 
libiomp-doc libomp-doc
Architecture: source amd64 all
Version: 3.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 libiomp-dev - Intel OpenMP runtime - dev package - transition package
 libiomp-doc - Intel OpenMP runtime - Documentation -  Transition package
 libiomp5   - Intel OpenMP runtime - transition package
 libiomp5-dbg - Intel OpenMP runtime - Debug transition package
 libomp-dev - LLVM OpenMP runtime - dev package
 libomp-doc - LLVM OpenMP runtime - Documentation
 libomp5- LLVM OpenMP runtime
 libomp5-dbg - LLVM OpenMP runtime - Debug package
Closes: 775257
Changes:
 openmprtl (3.7.0-2) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * Set SONAME to libiomp.so.5 properly (Closes: #775257)
   * Ship a libiomp5.so compat symlink.
   * Convert to multiarch.
Checksums-Sha1:
 ff35849a18608c8b324523ddc9b1daf43d89a8ed 2334 openmprtl_3.7.0-2.dsc
 57451d1a146b3a23b64c161448f85d697ebfa797 14516 openmprtl_3.7.0-2.debian.tar.xz
 fc079e41b1f3e130410539a0ddb31b1a7180ddc3 4384 libiomp-dev_3.7.0-2_amd64.deb
 620b28dceff91f376a2f52fae6a0e2e82a1e9023 4294 libiomp-doc_3.7.0-2_all.deb
 6981d7092a71483c28687941148cd1a6f05f53fb 4310 libiomp5-dbg_3.7.0-2_amd64.deb
 acb1d7966f404652fae2a9d298dcf70dd2995893 4280 libiomp5_3.7.0-2_amd64.deb
 eb0970c777e14ee21f16223b9c3f1eac0093fe20 5724 libomp-dev_3.7.0-2_amd64.deb
 abbd90060a62ce7c0cb8251db866efc25ae8f659 727146 libomp-doc_3.7.0-2_all.deb
 fc758dacf90521f21f3ce4861cd5c7d2acfc9ce8 39030 libomp5-dbg_3.7.0-2_amd64.deb
 5459526744860888cd9f242e41bb39011aa40619 191084 libomp5_3.7.0-2_amd64.deb
Checksums-Sha256:
 a742271dd12bee6e0f61f59763cc0e8c0e03ab842fb4aceba7e86b817cc0529f 2334 
openmprtl_3.7.0-2.dsc
 1af21c2564d41afafd401ae97262a466b7cb6869677d9293f80f77d0f9e5f582 14516 
openmprtl_3.7.0-2.debian.tar.xz
 814b7d5fbad8d876bed1d905d357bd57d37970abc8fdcda834bd17d815c969a7 4384 
libiomp-dev_3.7.0-2_amd64.deb
 3c0c122f0582f5d9588259f2c8a790f5d597ac6a371a05233ebf2c57d084d422 4294 
libiomp-doc_3.7.0-2_all.deb
 c24be318df981f0ba01eecaa4ec15e589bb220792a75048f708724ba28f26c14 4310 
libiomp5-dbg_3.7.0-2_amd64.deb
 08eac6c9d406c14fe865ad1ebe5c9a73e55c6a4f4b332048ef8592530e7fa220 4280 
libiomp5_3.7.0-2_amd64.deb
 fb601c205e2f28e01747a10fe321a97718bfc11c4f581f1c8c7872aff38216a9 5724 
libomp-dev_3.7.0-2_amd64.deb
 8f33dc6603d4fad4f8afbbf5f780e9e153af18239d71e9cf81fc5c348bb0294e 727146 
libomp-doc_3.7.0-2_all.deb
 7da12aaca4ae97a7c633c6c369345f4b240055fe5c4b6c6dc510c35d8cecedb6 39030 
libomp5-dbg_3.7.0-2_amd64.deb
 6100fd378b9021bc28dfb40e6c5998be444c4f4cb1c04937ea08afcaf1b03321 191084 
libomp5_3.7.0-2_amd64.deb
Files:
 362a5639d93b5e9485bbf568bc5aa425 2334 libs extra 

Bug#802452: nvidia-legacy-304xx-driver: updated with system info

[Andreas Beckmann]

On 2015-10-20 14:35, Luis Carvalheiro wrote:
> /proc/version:
> Linux version 4.2.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
> 4.9.3 (Debian 4.9.3-4) ) #1 SMP Debian 4.2.3-2 (2015-10-14)
> 
> /proc/driver/nvidia/version:
> NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.125  Mon Dec  1 19:58:28 
> PST 2014
> GCC version:  gcc version 4.9.3 (Debian 4.9.3-4) 

OK, you are really using 304.125 on Linux 4.2, so this is probably a
duplicate of #801193.
Please try 304.128-6 from unstable instead.


Andreas

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Mon, Oct 19, 2015 at 10:05:12PM +0100, Luca Boccassi wrote:

> In your case it looks like it certainly is. Your glx alternative is

No, it is not. I never touched setup. As I wrote before more then
once, the problem arises after upgrade, not as result of setup changing.


> configured to Mesa instead of Nvidia:
> 
> diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
> glx-diversions
> diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
> glx-diversions
> diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
> glx-diversions
> diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
> by glx-diversions

You are wrong: it is about divert and not about alternative.
 
> Please run:
>
> sudo update-alternatives --set glx /usr/lib/nvidia
> sudo dpkg-reconfigure glx-alternative-nvidia

This does not helps and can't help, because again and again: it is
not setup problem, it is upgrade result. Downgrade helps. That is
what I am doing to get it working:

dpkg -P nvidia-kernel-support
dpkg -i glx-alternative-mesa_0.5.1_amd64.deb 
glx-alternative-nvidia_0.5.1_amd64.deb glx-diversions_0.5.1_amd64.deb 
libegl1-nvidia_340.93-1_amd64.deb libgl1-nvidia-glx-i386_340.93-1_i386.deb 
libgl1-nvidia-glx_340.93-1_amd64.deb libgl1-nvidia-glx_340.93-1_i386.deb 
libgles1-nvidia_340.93-1_amd64.deb libgles2-nvidia_340.93-1_amd64.deb 
libnvidia-eglcore_340.93-1_amd64.deb libnvidia-ml1_340.93-1_amd64.deb 
nvidia-alternative_340.93-1_amd64.deb nvidia-driver-bin_340.93-1_amd64.deb 
nvidia-driver_340.93-1_amd64.deb nvidia-kernel-dkms_340.93-1_amd64.deb 
nvidia-vdpau-driver_340.93-1_amd64.deb 
xserver-xorg-video-nvidia_340.93-1_amd64.deb

And nothing else.

###  Vladimir Stavrinov  ###

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Vladimir Stavrinov]

On Tue, Oct 20, 2015 at 09:25:16AM +0300, Vladimir Stavrinov wrote:

> what I am doing to get it working:
> 
> dpkg -P nvidia-kernel-support
> dpkg -i glx-alternative-mesa_0.5.1_amd64.deb 
> glx-alternative-nvidia_0.5.1_amd64.deb glx-diversions_0.5.1_amd64.deb 
> libegl1-nvidia_340.93-1_amd64.deb libgl1-nvidia-glx-i386_340.93-1_i386.deb 
> libgl1-nvidia-glx_340.93-1_amd64.deb libgl1-nvidia-glx_340.93-1_i386.deb 
> libgles1-nvidia_340.93-1_amd64.deb libgles2-nvidia_340.93-1_amd64.deb 
> libnvidia-eglcore_340.93-1_amd64.deb libnvidia-ml1_340.93-1_amd64.deb 
> nvidia-alternative_340.93-1_amd64.deb nvidia-driver-bin_340.93-1_amd64.deb 
> nvidia-driver_340.93-1_amd64.deb nvidia-kernel-dkms_340.93-1_amd64.deb 
> nvidia-vdpau-driver_340.93-1_amd64.deb 
> xserver-xorg-video-nvidia_340.93-1_amd64.deb
> 

In reverse order or do it twice to resolve dependency issue.

> And nothing else.

Then reboot.

P.S. 0.6.92 doesn't help again.

###  Vladimir Stavrinov  ###

Bug#802402: jabref: FTBFS: build.xml:209: /usr/lib/ure/share/java does not exist.

[gregor herrmann]

On Tue, 20 Oct 2015 07:18:26 +0200, Rene Engelhard wrote:

> On Mon, Oct 19, 2015 at 08:39:15PM -0700, tony mancill wrote:
> > > Rene, do yo know which version of ure changed the direcories (so that
> > > we can add a versioned dependency)? I guess you're quicker than me to
> > > find this out :)
> > Looking like somewhere around >= 5.0~ for une.

Thanks! That's excellent news for the morning email check :)

> Yeah, I am sorry for the mess, completely forgot that change and even needed
> FTBFS bugs to fix my own packages... :/

No worries.


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#791730: marked as done (FTBFS with GCC 5: new symbols appeared in the symbols file)

[Debian Bug Tracking System]

Your message dated Tue, 20 Oct 2015 07:00:17 +
with message-id 
and subject line Bug#791730: fixed in libopenraw 0.0.9-3.6
has caused the Debian Bug report #791730,
regarding FTBFS with GCC 5: new symbols appeared in the symbols file
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.)


-- 
791730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenraw
Version: 0.0.9-3.5
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

This package fails to build with GCC 5:

> sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on bl460gen8-30.hlinux.usa.hp.com
...
> dh_strip --dbg-package=libopenraw1-dbg --dbg-package=libopenrawgnome1-dbg
> make[1]: Leaving directory '/«PKGBUILDDIR»'
>dh_makeshlibs
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libopenraw1/DEBIAN/symbols doesn't match 
> completely debian/libopenraw1.symbols
> --- debian/libopenraw1.symbols (libopenraw1_0.0.9-3.5_amd64)
> +++ dpkg-gensymbolsXZ0BGY 2015-07-07 21:32:51.103863069 +
> @@ -7,16 +7,18 @@
>   _ZN5Debug5Trace5printEi@Base 0.0.9
>   _ZN5Debug5TracelsEPKc@Base 0.0.9
>   _ZN5Debug5TracelsEPv@Base 0.0.9
> - _ZN5Debug5TracelsERKSs@Base 0.0.9
> + 
> _ZN5Debug5TracelsERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
> 0.0.9-3.5
> +#MISSING: 0.0.9-3.5# _ZN5Debug5TracelsERKSs@Base 0.0.9
>   _ZN5Debug5TracelsEi@Base 0.0.9
> - 
> (optional=templinst)_ZN5boost10shared_ptrIN7OpenRaw9Internals4CIFF4HeapEED1Ev@Base
>  0.0.9
> - 
> (optional=templinst)_ZN5boost10shared_ptrIN7OpenRaw9Internals4CIFF4HeapEED2Ev@Base
>  0.0.9
> - 
> (optional=templinst|arch=!armel)_ZN5boost10shared_ptrIN7OpenRaw9Internals6IFDDirEED1Ev@Base
>  0.0.9
> - 
> (optional=templinst|arch=!armel)_ZN5boost10shared_ptrIN7OpenRaw9Internals6IFDDirEED2Ev@Base
>  0.0.9
> +#MISSING: 0.0.9-3.5# 
> (optional=templinst)_ZN5boost10shared_ptrIN7OpenRaw9Internals4CIFF4HeapEED1Ev@Base
>  0.0.9
> +#MISSING: 0.0.9-3.5# 
> (optional=templinst)_ZN5boost10shared_ptrIN7OpenRaw9Internals4CIFF4HeapEED2Ev@Base
>  0.0.9
> +#MISSING: 0.0.9-3.5# 
> (optional=templinst|arch=!armel)_ZN5boost10shared_ptrIN7OpenRaw9Internals6IFDDirEED1Ev@Base
>  0.0.9
> +#MISSING: 0.0.9-3.5# 
> (optional=templinst|arch=!armel)_ZN5boost10shared_ptrIN7OpenRaw9Internals6IFDDirEED2Ev@Base
>  0.0.9
>   (optional=templinst|arch=armel 
> armhf)_ZN5boost10shared_ptrIN7OpenRaw9Internals6IFDDirEEaSERKS4_@Base 0.0.9
>   
> (optional=templinst)_ZN5boost12basic_formatIcSt11char_traitsIcESaIcEE18make_or_reuse_dataEm@Base
>  0.0.9
>   
> (optional=templinst)_ZN5boost12basic_formatIcSt11char_traitsIcESaIcEE5clearEv@Base
>  0.0.9
> - 
> (optional=templinst)_ZN5boost12basic_formatIcSt11char_traitsIcESaIcEE5parseERKSs@Base
>  0.0.9
> + 
> _ZN5boost12basic_formatIcSt11char_traitsIcESaIcEE5parseERKNSt7__cxx1112basic_stringIcS2_S3_EE@Base
>  0.0.9-3.5
> +#MISSING: 0.0.9-3.5# 
> (optional=templinst)_ZN5boost12basic_formatIcSt11char_traitsIcESaIcEE5parseERKSs@Base
>  0.0.9
>   
> (optional=templinst)_ZN5boost12basic_formatIcSt11char_traitsIcESaIcEEC1EPKc@Base
>  0.0.9
>   
> (optional=templinst)_ZN5boost12basic_formatIcSt11char_traitsIcESaIcEEC2EPKc@Base
>  0.0.9
>   
> (optional=templinst)_ZN5boost12basic_formatIcSt11char_traitsIcESaIcEED1Ev@Base
>  0.0.9
> @@ -26,51 +28,51 @@
>   
> (optional=templinst)_ZN5boost15throw_exceptionINS_2io12too_few_argsEEEvRKT_@Base
>  0.0.9
>   
> (optional=templinst)_ZN5boost15throw_exceptionINS_2io13too_many_argsEEEvRKT_@Base
>  0.0.9
>   
> (optional=templinst)_ZN5boost15throw_exceptionINS_2io17bad_format_stringEEEvRKT_@Base
>  0.0.9
> - (optional=templinst)_ZN5boost16exception_detail10clone_baseD0Ev@Base 0.0.9
> - (optional=templinst)_ZN5boost16exception_detail10clone_baseD1Ev@Base 0.0.9
> - (optional=templinst)_ZN5boost16exception_detail10clone_baseD2Ev@Base 0.0.9
> +#MISSING: 0.0.9-3.5# 
> (optional=templinst)_ZN5boost16exception_detail10clone_baseD0Ev@Base 0.0.9
> +#MISSING: 0.0.9-3.5# 
> (optional=templinst)_ZN5boost16exception_detail10clone_baseD1Ev@Base 0.0.9
> +#MISSING: 0.0.9-3.5# 
> (optional=templinst)_ZN5boost16exception_detail10clone_baseD2Ev@Base 0.0.9
>   
> (optional=templinst)_ZN5boost16exception_detail10clone_implINS0_19error_info_injectorINS_17bad_function_callD0Ev@Base
>  0.0.9
>   
> 

Bug#802414: python-requirements-detector: FTBFS: AttributeError: 'Call' object has no attribute 'starargs'

[Daniel Stender]

The problem here is #800788 (python3-astroid: not fit for Python 3.5), which is 
upstream.

If there isn't going to be fix in the short term a solution would be to build
requirements-detector temporarily against python3 instead of python3-all.

DS

-- 
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
LPI certified Linux admin (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/blog/

Bug#802413: xserver-xorg-video-qxl: FTBFS: Package 'libcacard', required by 'spice-server', not found

[Julien Cristau]

Control: reassign -1 libspice-server-dev 0.12.6-2

Not our bug, as the error message says this is an issue with the package
providing spice-server.pc.

On Mon, Oct 19, 2015 at 23:18:15 +0100, Chris West (Faux) wrote:

> Source: xserver-xorg-video-qxl
> Version: 0.1.4-3
> Severity: serious
> Justification: fails to build from source
> Tags: sid stretch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> The package fails to build:
> 
> checking for inotify_init1... yes
> checking for SPICE... no
> configure: error: Package requirements (spice-server >= 0.6.3) were not met:
> 
> Package 'libcacard', required by 'spice-server', not found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/xserver-xorg-video-qxl.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 


signature.asc
Description: PGP signature

Processed: Re: Bug#802413: xserver-xorg-video-qxl: FTBFS: Package 'libcacard', required by 'spice-server', not found

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libspice-server-dev 0.12.6-2
Bug #802413 [src:xserver-xorg-video-qxl] xserver-xorg-video-qxl: FTBFS: Package 
'libcacard', required by 'spice-server', not found
Bug reassigned from package 'src:xserver-xorg-video-qxl' to 
'libspice-server-dev'.
No longer marked as found in versions xserver-xorg-video-qxl/0.1.4-3.
Ignoring request to alter fixed versions of bug #802413 to the same values 
previously set
Bug #802413 [libspice-server-dev] xserver-xorg-video-qxl: FTBFS: Package 
'libcacard', required by 'spice-server', not found
Marked as found in versions spice/0.12.6-2.

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

Bug#802413: xserver-xorg-video-qxl: FTBFS: Package 'libcacard', required by 'spice-server', not found

[Michael Tokarev]

20.10.2015 10:07, Michael Tokarev wrote:
> Control: tag -1 + confirmed pending
> 
> 20.10.2015 09:31, Julien Cristau wrote:
>> Control: reassign -1 libspice-server-dev 0.12.6-2
>>
>> Not our bug, as the error message says this is an issue with the package
>> providing spice-server.pc.
> 
>>> configure: error: Package requirements (spice-server >= 0.6.3) were not met:
>>>
>>> Package 'libcacard', required by 'spice-server', not found
> 
> Oh.  This is the dependencies.  libspice-server-dev should depend
> on libcacard-dev.  Will upload a new version asap.

Uploaded, but I really wonder.  I remember thinking about this a bit
when adding cacard support to spice debian package, but haven't
realized the prob with .pc files (which might be artifical actually).

The thing is: libspice-server1 iself depends on libcacard0, but none
of the users of libspice-server1 should be aware of that, unless
they use libcacard internally too.  libspice-server-dev .h files
don't include any of libcacard header files.  The only place where
libcacard is mentioned in libspice-server-dev is this .pc file,
so pkgconfig checks for the corresponding libcacard.pc file which
is in -dev package.  While no other tools do that, eg, linker will
happily find libcacard0.so.0 when linking with libspice-server.so.

Should we really add this dependency?  It sounds better to remove
this requiriment from the libspice-server's .pc file than to add
a dep.

(In this particular case it is not important at all, one tiny extra
dependency for these large packages is nothing.  But I'm thinking
about general rule here)

Thanks,

/mjt

Bug#802390: mumble-server: No init script or systemd unit

[Sunil Mohan]

Daniel, thank you for the bug report.

> Verified. It seems this was missed in the switch from individual
> debhelper calls to dh in debian/rules.
> 
> Thanks very much for reporting this. Will fix ASAP.

Thank you for the quick response and fix. It would you really nice to
have the fixed package uploaded soon as we are planning to show Mumble
during FreedomBox Demo on Oct 30.  FreedomBox is currently running on
sid :(

> 
> I have a systemd unit file written for mumble-server, BTW, but I'm
> unclear how to include it alongside the init script. If anyone has a
> hint about that, please send it to this bug report. Thanks.

The init script and systemd unit should both be shipped.  systemd will
simply ignore the init script when a unit with the same name is
present[1].  (If you want a different name to the systemd unit that is
possible too with 'Alias=' option).

After you are done with basic stuff in the unit file, consider adding
security features to the unit file[2].  This will bring many of the
security advantages of containers without containers.  This will be
pretty sweet thing for FreedomBox :)

Links:

1)
https://wiki.debian.org/Teams/pkg-systemd/Packaging#systemd_unit_files_naming_and_installation

2)
https://wiki.debian.org/Teams/pkg-systemd/Packaging#Creating_service_files

Thank again,

-- 
Sunil



signature.asc
Description: OpenPGP digital signature

Processed: Fix 802260

[Debian Bug Tracking System]

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

> severity 802260  normal
Bug #802260 [gnome-gmail] gnome-gmail: Some dependencies missing
Severity set to 'normal' from 'grave'
> retitle 802260  Installation Experience on KDE
Bug #802260 [gnome-gmail] gnome-gmail: Some dependencies missing
Changed Bug title to 'Installation Experience on KDE' from 'gnome-gmail: Some 
dependencies missing'
> thanks
Stopping processing here.

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

Bug#802508: Not compatible with gnome-shell 3.18

[Michael Biebl]

Package: gnome-shell-mailnag
Version: 3.14.1-1
Severity: serious

Hi,

gnome-shell 3.18 was uploaded to unstable a while ago.
gnome-shell-mailnag is not compatible with that gnome-shell version.

See
/usr/share/gnome-shell/extensions/mail...@pulb.github.com/metadata.json

"shell-version": ["3.10", "3.12", "3.14"],

Please update your package so it supports this latest version of
gnome-shell and specify the supported versions in your package.

Instead of Depends: gnome-shell, please use something like
Depends: gnome-shell (>= 3.10), gnome-shell (<< 3.15)

This will ensure, that users which have that extension installed will be
notified before upgrading gnome-shell.


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

Kernel: Linux 4.2.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 gnome-shell-mailnag depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  gnome-shell  3.18.1-1
ii  libc62.19-22
ii  libfolks25   0.11.1-2+b1
ii  libgee-0.8-2 0.18.0-1
ii  libglib2.0-0 2.46.1-1
ii  mailnag  1.1.0-1

gnome-shell-mailnag recommends no packages.

gnome-shell-mailnag suggests no packages.

-- no debconf information

Bug#801413: polarssl: CVE-2015-5291: Remote attack on clients using session tickets or SNI

[James Cowgill]

Hi,

So I asked upstream about the specific commits which fixed this bug
here:
https://tls.mbed.org/discussions/bug-report-issues/question-about-cve-2015-5291

They seemed pretty resistive to the idea of just adding specific
patches on top of 1.3.9, and if you look at the changelog there are a
number of other security bugs which seem important but don't have CVEs
because they couldn't be triggered remotely.
https://github.com/ARMmbed/mbedtls/blob/mbedtls-1.3.14/ChangeLog

One thing which was suggested was to use 1.3.14 and then disable at
compile time all the new features which may affect the ABI and then
revert the SONAME change, but is doing that actually allowed for the
security archive or will the update be too big?

(I haven't actually done any of this yet, I'm just checking it'll be
OK before I spend my time on it)

Thanks,
James

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

Bug#801413: polarssl: CVE-2015-5291: Remote attack on clients using session tickets or SNI

[Florian Weimer]

* James Cowgill:

> They seemed pretty resistive to the idea of just adding specific
> patches on top of 1.3.9, and if you look at the changelog there are a
> number of other security bugs which seem important but don't have CVEs
> because they couldn't be triggered remotely.
> https://github.com/ARMmbed/mbedtls/blob/mbedtls-1.3.14/ChangeLog

I can sympathesize with that.  For example, I strongly recommend the
RSA-CRT hardening introduced in 1.3.13.

> One thing which was suggested was to use 1.3.14 and then disable at
> compile time all the new features which may affect the ABI and then
> revert the SONAME change, but is doing that actually allowed for the
> security archive or will the update be too big?

We can do that, but I don't know if it is a good idea to patch
cryptographic software in such extensive ways.

We can live with the addition of new symbols, but removal of symbols,
changes in struct sizes or offsets, and so on, would be hugely
problematic.  For are start, you could just build both the old and new
versions and run libabigail on them, to get an idea what actually did
change.

Florian

Processed: Re: GNOME shell extension not compatible with recent GNOME versions

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #799441 [hijra-applet] GNOME shell extension not compatible with recent 
GNOME versions
Severity set to 'serious' from 'important'

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

Bug#802509: libboost-coroutine-dev: The boost-coroutine library is only compiled as a static library

[Tiago de Paula Peixoto]

Package: libboost-coroutine-dev
Version: 1.58.0.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The boost-coroutine library is currently only compiled as a static
library, while all other boost libraries are compiled also as shared
objects.

Static librares cannot be linked against shared objects, and hence
this renders this library useless by other libraries and plugins.

AFAIK, there is no reason to compile it as a shared object, since that
is what most other distros do.

Best,
Tiago

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

Kernel: Linux 4.1.6-rh1-xenU (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages libboost-coroutine-dev depends on:
ii  g++ 4:5.2.1-4
ii  g++-5   5.2.1-22
ii  libboost-coroutine1.58-dev  1.58.0+dfsg-3.1
ii  libstdc++-5-dev 5.2.1-22

libboost-coroutine-dev recommends no packages.

libboost-coroutine-dev suggests no packages.

-- no debconf information

Processed: fixed 796542 in 1.8.0-3, notfixed 527861 in mount/2.27~rc2-1, fixed 527861 in 2.27~rc2-1 ...

[Debian Bug Tracking System]

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

> fixed 796542 1.8.0-3
Bug #796542 {Done: Thomas Goirand } [src:python-testtools] 
python-testtools: FTBFS: TypeError: 'NoneType' object is not callable
Marked as fixed in versions python-testtools/1.8.0-3.
> notfixed 527861 mount/2.27~rc2-1
Bug #527861 {Done: Andreas Henriksson } [mount] mention 
explicitly if noatime also means nodiratime
The source mount and version 2.27~rc2-1 do not appear to match any binary 
packages
No longer marked as fixed in versions mount/2.27~rc2-1.
> fixed 527861 2.27~rc2-1
Bug #527861 {Done: Andreas Henriksson } [mount] mention 
explicitly if noatime also means nodiratime
There is no source info for the package 'mount' at version '2.27~rc2-1' with 
architecture ''
Unable to make a source version for version '2.27~rc2-1'
Marked as fixed in versions 2.27~rc2-1.
> tags 708038 - jessie
Bug #708038 {Done: Christopher James Halse Rogers } [gnome-do] 
gnome-do: depends on libgnomedesktop2 which is going away
Removed tag(s) jessie.
> thanks
Stopping processing here.

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

Bug#799441: GNOME shell extension not compatible with recent GNOME versions

[Michael Biebl]

Am 20.10.2015 um 19:34 schrieb Michael Biebl:

> To ensure the latter, it would be a good idea, if the gnome-shell
> extension was split into a separate binary package which has the
> appropriate depends. Atm this would mean
> Depends: gnome-shell (>= 3.2), gnome-shell (<< 3.3)

I've turned this into a separate bug report, asking for the gnome-shell
extension to be split off. See #802512


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



signature.asc
Description: OpenPGP digital signature

Processed: re: gimp-dimage-color: FTBFS: Makefile:206: *** missing separator (did you mean TAB instead of 8 spaces?). Stop.

[Debian Bug Tracking System]

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

> tags 753206 +patch
Bug #753206 [src:gimp-dimage-color] gimp-dimage-color: FTBFS: Makefile:206: *** 
missing separator (did you mean TAB instead of 8 spaces?).  Stop.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#802522: mediawiki-extensions-ldapauth: Ldap auth is broken when used with php5 > 5.6.11

[Alejandro Lorenzo Gallego]

Package: mediawiki-extensions-ldapauth
Version: 3.7
Severity: grave
Tags: newcomer
Justification: renders package unusable

Dear Maintainer,

It appears that due to a change in how ldap_connect works in php5-ldap >=
5.6.11 this extension for mediawiki fails to authenticate against ldap servers.

Discussion on the bug and possible solution is on the mediawiki wiki
https://www.mediawiki.org/wiki/Topic:Sl9i17el9a1g9tv1

For the record, the proposed fix in the discussion of changing rtrim to trim in
the file extensions/LdapAuthentication/LdapAuthentication.php worked for me,
but i cannot be 100% sure it is secure and "the proper thing to do"

This renders this package unusable in stable, testing and unstable, as the sole
purpouse of the package is to provide ldap auth.






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

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

Versions of packages mediawiki-extensions-ldapauth depends on:
ii  mediawiki-extensions-base  3.7
ii  php5-ldap  5.6.13+dfsg-0+deb8u1

mediawiki-extensions-ldapauth recommends no packages.

mediawiki-extensions-ldapauth suggests no packages.

-- no debconf information

Bug#802347: mlpost: FTBFS: mlpost.mli: lexing: empty token

[Ralf Treinen]

On Tue, Oct 20, 2015 at 12:02:35PM +0200, Stéphane Glondu wrote:
> Control: reassign -1 ocaml
> Control: affects -1 mlpost
> 
> Le 19/10/2015 19:48, Chris West (Faux) a écrit :
> > [...]
> > File "/mlpost-0.8.1/_build/mlpost.mli", line 4186:
> > lexing: empty token
> > 16 error(s) encountered
> > Command exited with code 1.
> > ocamlbuild.Makefile:198: recipe for target 'doc' failed
> > make[2]: *** [doc] Error 10
> > make[2]: Leaving directory '/mlpost-0.8.1'
> > debian/rules:23: recipe for target 'override_dh_auto_install' failed
> 
> This is due to the reproducibility patch in ocaml adding .file
> directives. It breaks ocamldoc -pp. The patch will have to be
> reengineered. Meanwhile, I will amend it so that ocamldoc -pp works, but
> it means that ocamlopt -pp will no longer be deterministic :-(

This also looks like the same bug that hit dose3 [1]. -Ralf.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801773

Processed: fixed 799140 in 4.1+dfsg-1+deb8u5

[Debian Bug Tracking System]

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

> fixed 799140 4.1+dfsg-1+deb8u5
Bug #799140 {Done: Mike Gabriel } [src:wordpress] 
wordpress: CVE-2015-5714 CVE-2015-5715
Marked as fixed in versions wordpress/4.1+dfsg-1+deb8u5.
> thanks
Stopping processing here.

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

Bug#801430: aptitude: segfault maybe casued by package dependency loop aptitudeDepCache::internal_mark_delete loop here

[Manuel A. Fernandez Montecelo]

2015-10-20 18:44 GMT+01:00 Nick Black :
> I can confirm that 0.7.4 fixes the issue I reported. Good work.

Good, thanks for the confirmation!


-- 
Manuel A. Fernandez Montecelo 

Bug#801695: clang segfaults on hello world on arm64

[Riku Voipio]

Hi,

Seems this has been fixed with the latest 3.6.2-2 upload.

 clang -v
 Debian clang version 3.6.2-2 (tags/RELEASE_362/final) (based on LLVM 3.6.2)
 clang hello.c -o hello
 ./hello
 Hello World

Riku

Bug#802510: GNOME shell extension not compatible with recent GNOME versions

[Michael Biebl]

Package: workrave-data
Version: 1.10.6-3
Severity: serious

The gnome-shell extension shipped by workrave is not compatible with
recent GNOME versions.

According to
/usr/share/gnome-shell/extensions/workr...@workrave.org/metadata.json
the latest supported version is 3.14, while the current gnome-shell
version in unstable is 3.18.

Please update the extension, or drop it from the package.




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

Kernel: Linux 4.2.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 workrave-data depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2

workrave-data recommends no packages.

workrave-data suggests no packages.

-- no debconf information

Bug#801430: aptitude: segfault maybe casued by package dependency loop aptitudeDepCache::internal_mark_delete loop here

[Nick Black]

I can confirm that 0.7.4 fixes the issue I reported. Good work.

-- 
nick black -=- http://www.nick-black.com
to make an apple pie from scratch, you need first invent a universe.

Bug#802506: Not compatible with gnome-shell 3.18

[Michael Biebl]

Package: gnome-shell-extension-autohidetopbar
Version: 20150911-1
Severity: serious

Hi,

gnome-shell 3.18 was uploaded to unstable a while ago.

gnome-shell-extension-autohidetopbar is not compatible with that version
according to the dependencies that are specified:
Depends: gnome-shell (<< 3.17)

Please update your package so it works with gnome-shell 3.18.


Thanks,
Michael



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

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

Processed: patch fixing gnome-do ftbfs

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #801889 [src:gnome-do] Build-Depends on no longer existing packages
Added tag(s) patch.

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

Bug#801889: patch fixing gnome-do ftbfs

[Andreas Henriksson]

Control: tags -1 + patch

Hello!

Attaching a patch that makes gnome-do build again (otherwise
completely untested).

HTH.

Regards,
Andreas Henriksson
diff --git a/debian/changelog b/debian/changelog
index 4bf3a1b..c9b5924 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+gnome-do (0.95.3-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Drop librsvg and wnck cil build-deps
+- looks unused/unneeded and are no longer available in the archive.
+  * debian/patches/05_drop_gnome_desktop_2.diff:
+- bump to use gnome-desktop soname .12
+  * debian/control: Bump libgnome-desktop-3-dev build-dep to >= 3.18
+- to match the previous change.
+
+ -- Andreas Henriksson   Tue, 20 Oct 2015 16:19:57 +0200
+
 gnome-do (0.95.3-3) unstable; urgency=medium
 
   * [fec7a68] Drop libgnome-desktop2 dependency.
diff --git a/debian/control b/debian/control
index 4d1ce90..10c40f5 100644
--- a/debian/control
+++ b/debian/control
@@ -32,9 +32,7 @@ Build-Depends: debhelper (>= 7.0.50),
libnotify-cil-dev,
libglib2.0-dev,
libgtk2.0-dev,
-   librsvg2-2.0-cil-dev,
-   libwnck1.0-cil-dev,
-   libgnome-desktop-3-dev,
+   libgnome-desktop-3-dev (>= 3.18),
 Standards-Version: 3.9.5
 Homepage: http://do.cooperteam.net
 Vcs-Git: git://git.debian.org/git/pkg-cli-apps/packages/gnome-do.git
diff --git a/debian/patches/05_drop_gnome_desktop_2.diff b/debian/patches/05_drop_gnome_desktop_2.diff
index 97f6b86..68c84f5 100644
--- a/debian/patches/05_drop_gnome_desktop_2.diff
+++ b/debian/patches/05_drop_gnome_desktop_2.diff
@@ -79,5 +79,5 @@ Forwarded: not-needed
  
  	
 -	
-+	
++	
  

Processed: user debian...@lists.debian.org, usertagging 761568, tagging 761568, affects 761568 ...

[Debian Bug Tracking System]

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

> # all packages are uninstallable in sid
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 761568 piuparts
Usertags were: qa-ftbfs qa-ftbfs-20140913.
Usertags are now: piuparts qa-ftbfs qa-ftbfs-20140913.
> tags 761568 - jessie
Bug #761568 [src:diet] diet: FTBFS: convert: unable to open file 
`/tmp/magick-229129QKrUoVzzgMw': No such file or directory @ 
error/constitute.c/ReadImage/540.
Removed tag(s) jessie.
> affects 761568 + libdiet-sed2.8
Bug #761568 [src:diet] diet: FTBFS: convert: unable to open file 
`/tmp/magick-229129QKrUoVzzgMw': No such file or directory @ 
error/constitute.c/ReadImage/540.
Added indication that 761568 affects libdiet-sed2.8
> usertags 790624 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 790624 + libopenms1.11
Bug #790624 [openms] FTBFS: undefined reference to symbol 
'_ZNK4QDir6mkpathERK7QString'
Added indication that 790624 affects libopenms1.11
> usertags 799322 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 799322 + libpocl1
Bug #799322 [src:pocl] pocl: FTBFS: (gcc5 related?) symbols mismatches + test 
failures
Added indication that 799322 affects libpocl1
> usertags 70 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> affects 70 + elki
Bug #70 [src:elki] elki: FTBFS: error: cannot find symbol 
org.apache.batik.dom.svg.SVGDOMImplementation
Added indication that 70 affects elki
> usertags 801835 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 775362 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 775362 + ergo
Bug #775362 [src:ergo] ergo: FTBFS when higly parallelized: test suite 
fails+hangs
Added indication that 775362 affects ergo
> usertags 795237 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 797279 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 797279 + libswiften2
Bug #797279 [src:swift-im] swift-im ftbfs in unstable
Added indication that 797279 affects libswiften2
> usertags 798703 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 798703 + libwreport2
Bug #798703 [src:wreport] wreport: ABI transition needed for libstdc++ v5
Added indication that 798703 affects libwreport2
> usertags 792176 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> affects 792176 + mysql-testsuite-5.5
Bug #792176 [mysql-server-5.5] mysql-server-5.5: uninstallable in sid
Ignoring request to set affects of bug 792176 to the same value previously set
> reassign 801541 python-tg.devtools 2.0.2-5
Bug #801541 [tg.devtools] tg.devtools: unsatisfiable Depends: python-sqlalchemy 
(<< 0.10)
Bug reassigned from package 'tg.devtools' to 'python-tg.devtools'.
No longer marked as found in versions 2.0.2-5.
Ignoring request to alter fixed versions of bug #801541 to the same values 
previously set
Bug #801541 [python-tg.devtools] tg.devtools: unsatisfiable Depends: 
python-sqlalchemy (<< 0.10)
Marked as found in versions tg.devtools/2.0.2-5.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
761568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761568
775362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775362
790624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790624
792176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792176
797279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797279
798703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798703
799322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799322
70: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=70
801541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#794723: Policykit crashes systemd

[Simon McVittie]

On 20/10/15 04:56, Martin Pitt wrote:
> Martin Pitt [2015-10-20  5:27 +0200]:
>> For now I propose that the preinst temporarily masks polkitd.service
>> (ln -s /dev/null /run/systemd/system/polkitd.service), and the
>> postinst removes that symlink again, as then the conffiles are all in
>> place. I just tested this in a scenario that previously hung, and it
>> works smoothly.

It works in my test-case too (installing task-xfce-desktop).

> Committed this:
> 
>   http://anonscm.debian.org/cgit/pkg-utopia/policykit.git/commit/?id=5f7dd5

Looks good, please go ahead (unless Michael has some objection).

S

Bug#790951: restarts gmond at bad time during dist-upgrade (was: Re: Bug#802499: testing plugin packages during upgrades)

[Andreas Beckmann]

[ moving discussion to #790951 ]

On 2015-10-20 20:36, Daniel Pocock wrote:
> During an upgrade from wheezy to jessie, I saw it happen with
> ganglia-monitor and ganglia-modules-linux

> The details are explained in
> https://bugs.debian.org/791403

Do you have an upgrade log? I cannot reproduce this in piuparts,
always g-m is configured first, and g-m-l afterwards:

That's from piuparts test wheezy2jessie, amd64, --install-recommends.
The test got rerun yesterday :-), but the March logfile without
--install-recommends shows the same. I can provide the full logfiles if
needed.

The first command output is from
  apt-get install ganglia-modules-linux
in wheezy, the second from
  apt-get distupgrade
to jessie.
No services get started due to policy-rc.d, but you see what was attempted:

$ grep -C3 'Setting up ganglia'
wheezy2jessie-rcmd/main/pass/ganglia-modules-linux_1.3.6-1.log
  Setting up libapr1 (1.4.6-3+deb7u1) ...
  Setting up libpython2.7 (2.7.3-6+deb7u2) ...
  Setting up libganglia1 (3.3.8-1+nmu1) ...
  Setting up ganglia-monitor (3.3.8-1+nmu1) ...
  Adding system user: ganglia.
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up ganglia-modules-linux (1.3.4-6) ...
  invoke-rc.d: policy-rc.d denied execution of restart.
0m43.6s DEBUG: Command ok: ['chroot', '/tmp/piupartss/tmpfbZyHc',
'apt-get', '-y', 'install', 'ganglia-modules-linux']
0m43.6s INFO: Running scripts post_install
--
  Setting up ucf (3.0030) ...
  Setting up xz-utils (5.1.1alpha+20120614-2+b3) ...
  Setting up libganglia1 (3.6.0-6) ...
  Setting up ganglia-monitor (3.6.0-6) ...
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libpam-cap:amd64 (1:2.24-8) ...
  Setting up psmisc (22.21-2) ...
  Setting up ganglia-modules-linux (1.3.6-1) ...
  invoke-rc.d: policy-rc.d denied execution of restart.
  Processing triggers for libc-bin (2.19-18+deb8u1) ...
  Processing triggers for systemd (215-17+deb8u2) ...

So maybe another failure happened during your upgrade?
Or maybe I need a bigger system (more packages) to upgrade ...


Andreas

Bug#802533: hitch: creates /nonexistent/

[Andreas Beckmann]

Package: hitch
Version: 1.0.0~beta5-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left an unowned directory on
the system after purge, which is a violation of policy (did not check).

Filing this as serious since that directory is frequently used for system
users that should have their HOME *nonexistent*.

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

0m45.6s ERROR: FAIL: Package purging left files on system:
  /nonexistent/  not owned

Don't forget to clean this up (in preinst) on upgrades from the buggy version.


cheers,

Andreas


hitch_1.0.0~beta5-2.log.gz
Description: application/gzip

Processed: block 789133 with 801862

[Debian Bug Tracking System]

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

> block 789133 with 801862
Bug #789133 [release.debian.org] transition: ocaml 4.02.3
789133 was blocked by: 801458 789614 789619 801459 789402 789354 789403 790062
789133 was not blocking any bugs.
Added blocking bug(s) of 789133: 801862
> thanks
Stopping processing here.

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

Processed: block 789403 with 801862

[Debian Bug Tracking System]

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

> block 789403 with 801862
Bug #789403 [src:llvm-toolchain-3.4] FTBFS with OCaml 4.02.2: Some fatal 
warnings were triggered
789403 was not blocked by any bugs.
789403 was blocking: 789133
Added blocking bug(s) of 789403: 801862
> thanks
Stopping processing here.

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

Bug#799340: marked as done (libgetdata-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man3/gd_frameoffset.3.gz)

[Debian Bug Tracking System]

Your message dated Tue, 20 Oct 2015 21:21:48 +
with message-id 
and subject line Bug#799340: fixed in libgetdata 0.8.9-3
has caused the Debian Bug report #799340,
regarding libgetdata-doc: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/man/man3/gd_frameoffset.3.gz
to be marked as done.

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

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


-- 
799340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgetdata-doc
Version: 0.8.9-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libgetdata-doc.
  Preparing to unpack .../libgetdata-doc_0.8.9-2_all.deb ...
  Unpacking libgetdata-doc (0.8.9-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgetdata-doc_0.8.9-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/gd_frameoffset.3.gz', which is also 
in package libgetdata-dev 0.7.3-6+b2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libgetdata-doc_0.8.9-2_all.deb

and

  Selecting previously unselected package libgetdata-doc.
  Preparing to unpack .../libgetdata-doc_0.8.9-2_all.deb ...
  Unpacking libgetdata-doc (0.8.9-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgetdata-doc_0.8.9-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man5/dirfile.5.gz', which is also in 
package libgetdata-tools 0.7.3-6+b2
  Errors were encountered while processing:
   /var/cache/apt/archives/libgetdata-doc_0.8.9-2_all.deb
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


libgetdata-dev=0.7.3-6+b2_libgetdata-doc=0.8.9-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libgetdata
Source-Version: 0.8.9-3

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated libgetdata 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Oct 2015 19:29:39 +0100
Source: libgetdata
Binary: libgetdata-doc libgetdata-dev libgetdata5 libgetdata++3 libfgetdata2 
libf95getdata2 libgetdata-tools python-pygetdata libgetdata-perl
Architecture: source amd64 all
Version: 0.8.9-3
Distribution: sid
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Description:
 libf95getdata2 - library to read/write dirfile data - Fortran 95 bindings
 libfgetdata2 - library to read/write dirfile data - Fortran 77 bindings
 libgetdata++3 - library to read/write dirfile data - C++ bindings
 libgetdata-dev - library to read/write dirfile data - devel files (C, C++, 
F77, F9
 libgetdata-doc - library to read/write dirfile data - API and standards 
documents
 libgetdata-perl - library to read/write dirfile data - perl bindings
 libgetdata-tools - library to read/write dirfile data - extra tools
 libgetdata5 - library to read/write dirfile data
 python-pygetdata - library to read/write dirfile data - python bindings
Closes: 799340
Changes:
 libgetdata (0.8.9-3) unstable; urgency=medium
 .
   * Add Breaks to -dev, -doc packages to resolve upgrade issue.
 Closes: #799340.
Checksums-Sha1:
 37a776f77ed3665698e2ede3218290df25706433 2661 libgetdata_0.8.9-3.dsc
 1ee214dbcc622bc5b79e36a28af54690a12ee42c 4436 libgetdata_0.8.9-3.debian.tar.xz
 ff2b85be4084facdcc96742f291f4683fb8e00a6 96150 

Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)

[Scott Mcdermott]

Package: xserver-xorg-legacy
Version: 2:1.17.2-3
Severity: grave

I recently did an upgrade of X, which broke it on my machine.
Here are old (working) and new (broken) versions that apt-get
installed, as shown in /var/log/apt/history.log:

xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3)

This upgrade has broken X startup for me.  Here is how
I start X (as ordinary user):

exec setsid env -i \
LOGNAME=$LOGNAME \
USER=$USER \
HOME=$HOME \
PATH=$PATH \
EDITOR=$EDITOR \
DISPLAY=$DISPLAY \
SHELL=$SHELL \
TERM=$TERM \
LANG=$LANG \
X :0 vt63 \
-dpi 106 \
-nolisten tcp \
-noreset \
-keeptty \
-novtswitch

Then I run my window manager.  This has worked for me
at least 10 years.  I am using KMS (Intel i965GM):

 $ fbset
mode "1024x768"
geometry 1024 768 1024 768 32
timings 0 0 0 0 0 0 0
accel true
rgba 8/16,8/8,8/0,0/0
endmode

 $ dmesg | grep fbcon:
fbcon: inteldrmfb (fb0) is primary device

I have been able to run the X server (as an ordinary user)
using /usr/bin/X since modesetting was originally
implemented in the kernel.

Looking at the ChangeLog, I saw that /usr/bin/X was actually a
wrapper, which was moved to xserver-xorg-legacy.  Ok then:

Install: xserver-xorg-legacy:amd64 (1.17.2-3)

Problem 1: after upgrade, permissions bad on device

/usr/lib/xorg/Xorg.wrap: (EE) xf86OpenConsole:
  Cannot open virtual console 63 (Permission denied)

That didn't happen before.  It's mode 0620 root:tty, and
I'm not in the tty group, so the wrapper must have opened
the terminal with escalated privs before the upgrade, but
not after.  Note that I routinely "pkill X" to kill my
server -- as the ordinary user that started it -- so it
was definitely running without privs after initialization.
It must have done something while setuid, and then dropped
the privs.

My /etc/X11/Xwrapper.config contains the single line:

allowed_users=anybody

I changed /dev/tty63 to mode 0666 to move past this, but
then got a new problem.

Problem 2: after upgrade, IO ports operation not permitted:

X: xf86EnableIOPorts: failed to set IOPL for I/O
  (Operation not permitted)

I tried invoking Xorg.wrap directly (to eliminate the new
shell script at /usr/bin/X) and also copying it into place as
/usr/bin/X, but neither works, same errors.  I traced it to be
sure it was running the wrapper.  Not clear to me why this is
broken, since the ChangeLog implies only that it moved to a
different package.  But clearly the behavior is different now
and it actually works differently.

Note, X *does* start fine as root with the new package, but, I
don't want to run my X server as root, and didn't have to
before this upgrade.

Note, I used same kernel before and after: 4.1.0-2-amd64

Downgrade fixes it:

Commandline: apt-get install xserver-xorg-core=2:1.17.2-1.1
Downgrade: xserver-xorg-core:amd64 (1.17.2-3, 1.17.2-1.1)
Remove: xserver-xorg-legacy:amd64 (1.17.2-3),
xserver-xspice:amd64 (0.1.4-3),
xserver-xorg:amd64 (7.7+12)

Commandline: apt-get install xserver-xorg=1:7.7+9
Install: xserver-xorg:amd64 (7.7+9)

Note that I *do not* use systemd.  Please don't tell me I have
to either use systemd, or run my X server as root.  I didn't
have to do either before this upgrade.

Please advise; thanks.

Bug#802526: pymvpa2: FTBFS: ImportError: cannot import name fprob

[Yaroslav Halchenko]

yeap -- known... will upload a quick fix release soonish. thanks

On Mon, 19 Oct 2015, Chris West (Faux) wrote:

> Source: pymvpa2
> Version: 2.4.0-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid stretch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

> Dear Maintainer,

> The package fails to build:

> Failure: SkipTest (External statsmodels is not present thus tests battery 
> skipped) ... SKIP: External statsmodels is not present thus tests battery 
> skipped
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#802523: psocksxx: FTBFS: You made dpkg-gensymbols sad

[Chris West (Faux)]

Source: psocksxx
Version: 0.0.6-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

   dh_makeshlibs
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libpsocksxx0/DEBIAN/symbols doesn't match 
completely debian/libpsocksxx0.symbols.amd64
--- debian/libpsocksxx0.symbols.amd64 (libpsocksxx0_0.0.6-2_amd64)
+++ dpkg-gensymbolsdY4BHc   2015-10-19 20:08:47.938645878 +
@@ -100,7 +100,7 @@
  _ZNK8psocksxx9lsockaddr9psockaddrEv@Base 0.0.5
  _ZNK8psocksxx9nsockaddr4sizeEv@Base 0.0.5
  _ZNK8psocksxx9nsockaddr9psockaddrEv@Base 0.0.5
- _ZNSs12_S_constructIPcEES0_T_S1_RKSaIcESt20forward_iterator_tag@Base 0.0.5
+#MISSING: 0.0.6-2# 
_ZNSs12_S_constructIPcEES0_T_S1_RKSaIcESt20forward_iterator_tag@Base 0.0.5
  _ZTI11sockaddr_in@Base 0.0.5
  _ZTI11sockaddr_un@Base 0.0.5
  _ZTIN8psocksxx11isockstreamE@Base 0.0.5
@@ -148,7 +148,7 @@
  _ZTVN8psocksxx14tcpnsockstreamE@Base 0.0.5
  _ZTVN8psocksxx14udpnsockstreamE@Base 0.0.5
  _ZTVN8psocksxx20socktimeoutexceptionE@Base 0.0.5
- _ZTVN8psocksxx8sockaddrE@Base 0.0.5
+#MISSING: 0.0.6-2# _ZTVN8psocksxx8sockaddrE@Base 0.0.5
  _ZTVN8psocksxx9lsockaddrE@Base 0.0.5
  _ZTVN8psocksxx9nsockaddrE@Base 0.0.5
  _ZThn16_N8psocksxx11lsockstreamD0Ev@Base 0.0.5
dh_makeshlibs: failing due to earlier errors
debian/rules:19: recipe for target 'binary' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/psocksxx.html

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

Bug#802526: pymvpa2: FTBFS: ImportError: cannot import name fprob

[Chris West (Faux)]

Source: pymvpa2
Version: 2.4.0-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

Failure: SkipTest (External statsmodels is not present thus tests battery 
skipped) ... SKIP: External statsmodels is not present thus tests battery 
skipped

==
ERROR: Test all classifiers for conformant behavior
--
Traceback (most recent call last):
  File 
"/pymvpa2-2.4.0/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/tests/test_clf.py",
 line 916, in test_generic_tests
clf.train(traindata)
  File 
"/pymvpa2-2.4.0/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/base/learner.py",
 line 132, in train
result = self._train(ds)
  File 
"/pymvpa2-2.4.0/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/clfs/meta.py", 
line 1371, in _train
self.__mapper.train(dataset)
  File 
"/pymvpa2-2.4.0/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/base/learner.py",
 line 132, in train
result = self._train(ds)
  File 
"/pymvpa2-2.4.0/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/featsel/base.py",
 line 320, in _train
selected_ids = self._get_selected_ids(dataset)
  File 
"/pymvpa2-2.4.0/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/featsel/base.py",
 line 296, in _get_selected_ids
sensitivity = self.__sensitivity_analyzer(dataset)
  File 
"/pymvpa2-2.4.0/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/base/learner.py",
 line 259, in __call__
return super(Learner, self).__call__(ds)
  File 
"/pymvpa2-2.4.0/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/base/node.py", 
line 121, in __call__
result = self._call(ds)
  File 
"/pymvpa2-2.4.0/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/measures/anova.py",
 line 122, in _call
from scipy.stats import fprob
ImportError: cannot import name fprob

...

--
Ran 494 tests in 263.900s

FAILED (SKIP=19, errors=14)
debian/rules:42: recipe for target 'override_dh_auto_install' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/pymvpa2.html

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

Bug#802524: nitime: FTBFS: ImportError: cannot import name mpl

[Chris West (Faux)]

Source: nitime
Version: 0.5-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

make[2]: Entering directory '/nitime-0.5/doc'
../tools/make_examples.py
Traceback (most recent call last):
  File "../tools/make_examples.py", line 96, in 
execfile(script)
  File "ar_est_1var.py", line 31, in 
from nitime.viz import plot_tseries
  File "/nitime-0.5/debian/tmp/usr/lib/python2.7/dist-packages/nitime/viz.py", 
line 19, in 
from matplotlib import mpl
ImportError: cannot import name mpl
Makefile:79: recipe for target 'rstexamples' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/nitime.html

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

Bug#802527: twitter-bootstrap3: FTBFS: less: SyntaxError: Cannot find module 'source-map'

[Chris West (Faux)]

Source: twitter-bootstrap3
Version: 3.3.5+dfsg-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

# Mimic less from Gruntfile
lessc --strict-math=on \
--source-map-url=bootstrap.css.map \
--source-map=dist/css/bootstrap.css.map \
less/bootstrap.less dist/css/bootstrap.css
SyntaxError: Cannot find module 'source-map' in 
/twitter-bootstrap3-3.3.5+dfsg/less/bootstrap.less on line null, 
column 0:
1  * Bootstrap v3.3.5 (http://getbootstrap.com)

debian/rules:9: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/twitter-bootstrap3.html

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

Bug#802525: pyx3: FTBFS: AttributeError: 'module' object has no attribute 'safe_repr'

[Chris West (Faux)]

Source: pyx3
Version: 0.14-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

sphinx-build -b html -d _build/doctrees   . _build/html
Running Sphinx v1.3.1
making output directory...

Exception occurred:
  File "conf.py", line 291, in 
old_safe_repr = sphinx.util.inspect.safe_repr
AttributeError: 'module' object has no attribute 'safe_repr'
The full traceback has been saved in /tmp/sphinx-err-_79sz6gp.log, if you want 
to report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
Makefile:27: recipe for target 'html' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/pyx3.html

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

Bug#802310: nvidia configuration changed w.r.t. bumblebee ...

[Luca Boccassi]

On Tue, 2015-10-20 at 14:43 +0200, Andreas Beckmann wrote:
> I pushed a few commits for bumblebee that add the Debian specific
> versioned dependency on glx-alternative-nvidia. Regarding the legacy
> drivers: for now I only added them to the blacklist, let's do more on
> this topic later. (BTW, why does bumblebe insist on loading
> nvidia-current? That should be plain nvidia...)
> Please give it some testing.

Tested with 340.93-5 and also with 358.09 since it has the new extra
module that could make things more complicated. Removed bumblebee and
reinstalled, the glx-alternative was configured as expected. Modules are
unloaded and card is turned off on exit. Tested with Cuda too. Looks
good to me.

Would be good to test on Ubuntu too, even though the packaging looks
pretty safe and sound. I don't have access to a laptop with Ubuntu at
the moment and I cannot install it on my Debian one unfortunately.

I'm not sure why it picks nvidia-current. There is an override
in /etc/bumblebee/bumblebee.conf though.

kind regards,
Luca Boccassi


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

Processed: systemd: postinst may not have run correctly on upgrades from jessie

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 801156
Bug #802545 [systemd] systemd: postinst may not have run correctly on upgrades 
from jessie
802545 was not blocked by any bugs.
802545 was not blocking any bugs.
Added blocking bug(s) of 802545: 801156

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

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Luca Boccassi]

On Tue, 2015-10-20 at 12:16 +0300, Vladimir Stavrinov wrote:
> On Mon, Oct 19, 2015 at 10:11:45PM +0100, Luca Boccassi wrote:
> 
> > Maybe there's some context I'm missing. Forgive me for asking, but are
> > you sure this is due to the Nvidia driver packages or glx-alternatives?
> 
> Absolutely. This is Nvidia driver problem. Few days ago I conducted
> specific experiment. After upgrading to latest version of all nvidia
> and glx packages, I've downgraded only kernel module and after
> reloading module the glx got working. But after rebooting system the
> problem returned again. So not only kernel module is problem, but it
> is main.

That is most likely because the permissions on the device nodes are
different when you load the module manually vs when udev does it at
boot.

> > Andreas, you use KDE if I'm not mistaken. Are you seeing any issues? Do
> 
> How many times again: this is not problem of KDE, plasma, kodi or any
> other software using glx. This is problem of glx in nvidia driver. 
> 
> I am using xlock from very old package xlockmore-gl not included in
> any of today's debian distributions. But it has two options
> "-modelist allgl" and "-modelist all-allgl". First is for include glx
> modes, second - to exclude ones. This is very good for testing glx,
> because it explicitly points to glx as the source of problem when it
> works with second option and doesn't work with the first one.
> 
> So it is certainly clear, that the source of our problems is glx
> feature of nvdia driver. But the fact that You can't reproduce the
> problem (if You can't, because You never mentioned this) may mean,
> that problem is somehow hardware specific. In this case there are no
> way to debug it as to ask us to do for You some experiments of Your
> choice.
> 
> Here is my hardware:
> 
> lspci | grep -i nvidia
> 01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 635] 
> (rev a1)
> 01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev 
> a1)
> 
> If this guess is not true and the problem is not hardware specific, then You
> should try number of different software using glx to reproduce the
> problem.
> 
> And finally it is possible, that at some point of investigation You
> will understand necessity to escalate the problem to upstream.

The reason I'm asking about which DM this is happening on is because,
after applying the video group workaround I am not experiencing any
issues with any software that uses GLX or any other library provided by
the nvidia drivers. So, I was just trying to narrow it down and get the
full picture of the environment.

As I wrote earlier, yesterday I noticed that it is not enough for the
desktop-manager user (sddm or Debian-gdm) to be in the video group, the
user also MUST be part of it, otherwise GDM breaks due to the device
nodes permissions problem.

Could you please make sure that both your user and your DM user (sddm I
believe?) are in the video group and try again and report the result?

Kind regards,
Luca Boccassi


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

Bug#801582: marked as done (grub-pc: default entry becomes Halt once (for setting alarm) => no boot)

[Debian Bug Tracking System]

Your message dated Tue, 20 Oct 2015 22:34:10 +
with message-id 
and subject line Bug#801582: fixed in nvram-wakeup 1.1-4
has caused the Debian Bug report #801582,
regarding grub-pc: default entry becomes Halt once (for setting alarm) => no 
boot
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.)


-- 
801582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-pc
Version: 2.02~beta2-28
Severity: critical
Justification: breaks the whole system


Today my system did not boot because the default entry was set
to  Halt once (for setting alarm). This emans that if I upgrade
machines where I have only ssh access, no console, I'm dead.
And I have many both at work and home.

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/root / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda6 /var ext4 rw,relatime,data=ordered 0 0
/dev/sda2 /usr ext4 rw,relatime,data=ordered 0 0
/dev/sda8 /home ext4 rw,relatime,data=ordered 0 0
/dev/sda7 /usr/local ext4 rw,relatime,data=ordered 0 0
/dev/sda5 /tmp ext2 rw,relatime,errors=continue 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/disk/by-id/ata-WDC_WD2500BEKT-75PVMT0_WD-WXP1AC0K6712
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  
e305023c-baf2-4e52-9847-d35118d65706
else
  search --no-floppy --fs-uuid --set=root e305023c-baf2-4e52-9847-d35118d65706
fi
font="/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=fr_FR
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  
e305023c-baf2-4e52-9847-d35118d65706
else
  search --no-floppy --fs-uuid --set=root e305023c-baf2-4e52-9847-d35118d65706
fi
insmod png
if background_image /share/images/desktop-base/lines-grub.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-a65a0c35-cdf7-40f5-b630-a7835e6ac24b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod 

Bug#802550: x264: FTBFS on mipsel: Error: opcode not supported on this processor: mips2 (mips2) `addvi.b $w0, $w1, 1'

[Sebastian Ramacher]

Package: x264
Version: 2:0.148.2601+gita0cd7d3-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

x264 failed to build on mipsel:
| # Build static lib
| LDFLAGS="-Wl,-z,relro" ./configure --prefix=/usr 
--libdir=/usr/lib/mipsel-linux-gnu 
--extra-cflags=-fno-aggressive-loop-optimizations --enable-static --disable-cli 
\
||| ( tail -v -n +0 config.log config.log ; exit 1 )
| You specified a pre-MSA CPU in your CFLAGS.
| If you really want to run on such a CPU, configure with --disable-asm.
| ==> config.log <==
| x264 configure script
| Command line options: "--prefix=/usr" "--libdir=/usr/lib/mipsel-linux-gnu" 
"--extra-cflags=-fno-aggressive-loop-optimizations" "--enable-static" 
"--disable-cli"
|
| checking whether gcc works... yes
| checking whether gcc supports for( int i = 0; i < 9; i++ ); with 
-std=gnu99... yes
| checking for -mmsa -mfp64 -mhard-float... no
| Failed commandline was:
| --
| gcc conftest.c   -fstack-protector-strong -Wformat -Werror=format-security 
-Wall -I. -I$(SRCPATH) -fno-aggressive-loop-optimizations -std=gnu99  -mmsa 
-mfp64 -mhard-float  -Wl,-z,relro -lm -o conftest
| gcc: error: unrecognized command line option '-mmsa'
| --
| Failed program was:
| --
| int main (void) {  return 0; }
| --
| checking whether gcc supports __asm__("addvi.b $w0, $w1, 1");... no
| Failed commandline was:
| --
| gcc conftest.c   -fstack-protector-strong -Wformat -Werror=format-security 
-Wall -I. -I$(SRCPATH) -fno-aggressive-loop-optimizations -std=gnu99
-Wl,-z,relro -lm -o conftest
| /tmp/ccT8Idl1.s: Assembler messages:
| /tmp/ccT8Idl1.s:24: Error: opcode not supported on this processor: mips2 
(mips2) `addvi.b $w0,$w1,1'
| --
| Failed program was:
| --
| int main (void) { __asm__("addvi.b $w0, $w1, 1"); return 0; }
| --
|
| ==> config.log <==
| x264 configure script
| Command line options: "--prefix=/usr" "--libdir=/usr/lib/mipsel-linux-gnu" 
"--extra-cflags=-fno-aggressive-loop-optimizations" "--enable-static" 
"--disable-cli"
|
| checking whether gcc works... yes
| checking whether gcc supports for( int i = 0; i < 9; i++ ); with 
-std=gnu99... yes
| checking for -mmsa -mfp64 -mhard-float... no
| Failed commandline was:
| --
| gcc conftest.c   -fstack-protector-strong -Wformat -Werror=format-security 
-Wall -I. -I$(SRCPATH) -fno-aggressive-loop-optimizations -std=gnu99  -mmsa 
-mfp64 -mhard-float  -Wl,-z,relro -lm -o conftest
| gcc: error: unrecognized command line option '-mmsa'
| --
| Failed program was:
| --
| int main (void) {  return 0; }
| --
| checking whether gcc supports __asm__("addvi.b $w0, $w1, 1");... no
| Failed commandline was:
| --
| gcc conftest.c   -fstack-protector-strong -Wformat -Werror=format-security 
-Wall -I. -I$(SRCPATH) -fno-aggressive-loop-optimizations -std=gnu99
-Wl,-z,relro -lm -o conftest
| /tmp/ccT8Idl1.s: Assembler messages:
| /tmp/ccT8Idl1.s:24: Error: opcode not supported on this processor: mips2 
(mips2) `addvi.b $w0,$w1,1'
| --
| Failed program was:
| --
| int main (void) { __asm__("addvi.b $w0, $w1, 1"); return 0; }
| --
| debian/rules:26: recipe for target 'override_dh_auto_build' failed
| make[1]: *** [override_dh_auto_build] Error 1
| make[1]: Leaving directory '/«BUILDDIR»/x264-0.148.2601+gita0cd7d3'
| debian/rules:16: recipe for target 'build-arch' failed
| make: *** [build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
| 

| Build finished at 20151016-0152

Full build log is available at
https://buildd.debian.org/status/fetch.php?pkg=x264=mipsel=2:0.148.2601+gita0cd7d3-1=1444960382

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#793012: gmp-ecm: FTBFS on mipsel: bad assembly?

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello:

Finally I could access to  the mips and mipsel porter boxes and check
the patched version of the package: everything is fine.
Thanks to Jurica Stanojkovic.

The patch has been brought to Alioth as is (modulo some comments).

I will submit the new version for sponsorship soon.

Thanks,
Jerome
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJWJr+uAAoJEIC/w4IMSybj4BEIALr2myT9YP/2t/Z1J0Khzsjt
T4fdKIbbKJ/f+Z0EvjGYRy4wREK+PyctyP0IeSxv809eohywkrfHhvaRVJvhwILP
GOuNi9uWWcfheoXP1GVse8DjcZaFZAniqIji7yqeixSOyDuwL1iqWNajbFIXQDLV
j6k3aWS8EQV3v4fn72l+dkg64ebFnkd91mFCo2EwatGSN6V5+WBG/tPuXrTA4GIz
eFdKuMKlQg8YWYB73U657mIjwFu5nCddJnWpPldK08o95XvMSRJf1WPuxjDj2Fdl
STE9/PVI5rpupDQOuBFyklKHAfIdPanuVGBaaUeIM16g8ADbHeV5yI5ErxQqjgs=
=oubH
-END PGP SIGNATURE-

Bug#802471: libopenraw1v5: Try to overwrite file in libopenraw1

[Michael Biebl]

On Tue, 20 Oct 2015 13:38:24 +0200 Christian Marillat
 wrote:
> Package: libopenraw1v5
> Version: 0.0.9-3.6
> Severity: serious
> 
> Dear Maintainer,
> 
> libopenraw1v5 must Conflicts/Replaces libopenraw1 :
> 
> Unpacking libopenraw1v5:i386 (0.0.9-3.6) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/libopenraw1v5_0.0.9-3.6_i386.deb (--unpack):
>  trying to overwrite '/usr/lib/i386-linux-gnu/libopenraw.so.1.6.0', which is 
> also in package libopenraw1:i386 0.0.9-3.5+b2
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Processing triggers for libc-bin (2.19-22) ...
> Errors were encountered while processing:
>  /var/cache/apt/archives/libopenraw1v5_0.0.9-3.6_i386.deb
> 

Just in case it's not immediately obvious:

You added a
Conflicts/Replaces: libopenraw1v5, while you want a
Conflicts/Replaces: libowpnraw1 obviously.

Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#799948: Plasma desktop is unable to start (black screen - panic)

[Luca Boccassi]

On Tue, 2015-10-20 at 11:56 +0200, Miguel Angel Rojas wrote:
> 
> I must first say that I am absolutely not familiar with KDE,
> the QT
> environment and how it works. But the thread that raises the
> abort
> doesn't look like it's in the GL libraries code:
> 
> Maybe there's some context I'm missing. Forgive me for asking,
> but are
> you sure this is due to the Nvidia driver packages or
> glx-alternatives?
> 
> 
> 
> Hi Luca,
> 
> 
> But indeed, it is! I conducted the same experiments as Vladimir did
> with the same result. Something is wrong with the glx beyond 0.6.x
> (bad packaging, new API, new behavior? I don't know). I would
> recommend to reproduce as it is very easy to do it and you will see
> what we are talking about.

Hi Miguel,

The reason I'm asking is because I can't reproduce any problems on GDM,
with any software that uses GLX or other libraries, after adding the
workaround.

But I noticed something looking again at the system info you forwarded,
the only user in the "video" group is sddm:

video:x:44:sddm

I verified yesterday that even on GDM both the DM-manager user (in my
case Debian-gdm) AND my user MUST be in the video group, otherwise the
problem occurs.

Could you please try to add your user to the video group and see if that
helps?

> Talking about Bug #799948, is there a reason why sddm user should be
> included in video? (because it seems to be the workaround) If so,
> someone should notify sddm guys that is somehow required due to new
> upstream requirement in nvidia glx packages. We don't have a clear
> explanation about it.

We are still discussing and investigating that. It is not a new upstream
requirement but a fix to the device nodes permissions that we are trying
out, but it seems to be causing way too much grief. Please see this
message by Andreas [1] for more details about the background.

Kind regards,
Luca Boccassi


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

Bug#794723: [Pkg-utopia-maintainers] Bug#794723: Policykit crashes systemd

[Michael Biebl]

Hi,

Am 20.10.2015 um 05:56 schrieb Martin Pitt:
> Control: tag -1 pending
> 
> Martin Pitt [2015-10-20  5:27 +0200]:
>> For now I propose that the preinst temporarily masks polkitd.service
>> (ln -s /dev/null /run/systemd/system/polkitd.service), and the
>> postinst removes that symlink again, as then the conffiles are all in
>> place. I just tested this in a scenario that previously hung, and it
>> works smoothly.
> 
> Committed this:
> 
>   http://anonscm.debian.org/cgit/pkg-utopia/policykit.git/commit/?id=5f7dd5
> 
> I don't upload it yet as I'd like to give Simon and Michael a chance
> to weigh in. If you are okay with this, I'll upload this and also
> apply it to the experimental branch.

any particular reason why you didn't just use
systemctl (un)mask --runtime
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#802549: transition: x264

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 802550
Bug #802549 [release.debian.org] transition: x264
802549 was not blocked by any bugs.
802549 was not blocking any bugs.
Added blocking bug(s) of 802549: 802550

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

Bug#802390: mumble-server: No init script or systemd unit

[Chris Knadle]

Sunil Mohan:
> Daniel, thank you for the bug report.
> 
>> Verified. It seems this was missed in the switch from individual
>> debhelper calls to dh in debian/rules.
>>
>> Thanks very much for reporting this. Will fix ASAP.
> 
> Thank you for the quick response and fix. It would you really nice to
> have the fixed package uploaded soon as we are planning to show Mumble
> during FreedomBox Demo on Oct 30.  FreedomBox is currently running on
> sid :(

I'll do my best.  I'm trying to track down an issue with dpkg-buildflags
concerning one file being shipped that may partially be missing the FORTIFY
flag.  At least some functions are fortified but there doesn't seem to be a
good verification tool to know if lintian is reporting a false-positive or
if there's a QMAKE file missing dpkg-buildflags.

>> I have a systemd unit file written for mumble-server, BTW, but I'm
>> unclear how to include it alongside the init script. If anyone has a
>> hint about that, please send it to this bug report. Thanks.
> 
> The init script and systemd unit should both be shipped.  systemd will
> simply ignore the init script when a unit with the same name is
> present[1].  (If you want a different name to the systemd unit that is
> possible too with 'Alias=' option).
> 
> After you are done with basic stuff in the unit file, consider adding
> security features to the unit file[2].  This will bring many of the
> security advantages of containers without containers.  This will be
> pretty sweet thing for FreedomBox :)

There are a few wrinkles with shipping a systemd unit file.

 - There's a bug with mumble-server startup under systemd and
   upstart (#780300).  You can see the service file I created
   in testing the bug here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;msg=49;filename=mumble-server.service;bug=780300
   Using a setting of "host=::" is a workaround, but I don't
   consider that a true solution to the bug.

 - mumble-server ships an /etc/default/mumble-server file to
   disable the daemon by default, and there's no clean way
   under systemd to disable a unit based on the contents of an
   environment variable in a file.

https://wiki.ubuntu.com/SystemdForUpstartUsers#A.2BAC8-etc.2BAC8-default_files_which_enable.2BAC8-disable_jobs

 - As discussed on [debian-devel] in the "init script, installed but
   not activated" thread, it's tricky to ship a systemd service file
   that isn't active by default.

  -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us



signature.asc
Description: OpenPGP digital signature

Bug#802550: x264: FTBFS on mipsel: Error: opcode not supported on this processor: mips2 (mips2) `addvi.b $w0, $w1, 1'

[James Cowgill]

Hi,

On Wed, 2015-10-21 at 00:56 +0200, Sebastian Ramacher wrote:
> Package: x264
> Version: 2:0.148.2601+gita0cd7d3-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> x264 failed to build on mipsel:
> > # Build static lib
> > LDFLAGS="-Wl,-z,relro" ./configure --prefix=/usr 
> > --libdir=/usr/lib/mipsel-linux-gnu 
> > --extra-cflags=-fno-aggressive-loop-optimizations --enable-static 
> > --disable-cli \
> >    || ( tail -v -n +0 config.log config.log ; exit 1 )
> > You specified a pre-MSA CPU in your CFLAGS.
> > If you really want to run on such a CPU, configure with --disable-asm.

So (with my mips porting hat on) you will need to pass --disable-asm
here for mips, mipsel and mips64el.

But why on earth is this the upstream default? MSA isn't exactly common
on MIPS processors at the moment (eg binutils support was only added
last year).

James

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

Bug#794763: marked as done (mplayer2: MPlayer interrupted by signal 11 in module: demux_open)

[Debian Bug Tracking System]

Your message dated Tue, 20 Oct 2015 23:46:06 +
with message-id 
and subject line Bug#794817: Removed package(s) from unstable
has caused the Debian Bug report #794763,
regarding mplayer2: MPlayer interrupted by signal 11 in module: demux_open
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.)


-- 
794763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mplayer2
Version: 2.0-728-g2c378c7-4+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Mplayer2 seems to be broken. For all videos in different formats I tried to
watch I get:

$ mplayer video.avi
MPlayer2 2.0-728-g2c378c7-4+b1 (C) 2000-2012 MPlayer Team
Cannot open file '/home/aleksandr/.mplayer/input.conf': No such file or
directory
Failed to open /home/aleksandr/.mplayer/input.conf.
Cannot open file '/etc/mplayer/input.conf': No such file or directory
Failed to open /etc/mplayer/input.conf.

Playing video.avi.


MPlayer interrupted by signal 11 in module: demux_open
- MPlayer crashed by bad usage of CPU/FPU/RAM.
  Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
  disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
  It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
  gcc version. If you think it's MPlayer's fault, please read
  DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  won't help unless you provide this information when reporting a possible bug.

Backtrace:
(gdb) run video.avi
Starting program: /usr/bin/mplayer video.avi
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
MPlayer2 2.0-728-g2c378c7-4+b1 (C) 2000-2012 MPlayer Team
Cannot open file '/home/aleksandr/.mplayer/input.conf': No such file or
directory
Failed to open /home/aleksandr/.mplayer/input.conf.
Cannot open file '/etc/mplayer/input.conf': No such file or directory
Failed to open /etc/mplayer/input.conf.

Playing video.avi.

Program received signal SIGSEGV, Segmentation fault.
strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: No such file or directory.


Maybe information from valgrind will be useful (see attachment)

The same bug can be found at https://trac.mplayerhq.hu/ticket/2237

Some similar bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760669
https://trac.videolan.org/vlc/ticket/11851

Best regards,
Alexandr



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

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

Versions of packages mplayer2 depends on:
ii  liba52-0.7.4  0.7.4-17
ii  libasound21.0.28-1
ii  libass5   0.10.2-3
ii  libavcodec56  6:11.4-1~deb8u1
ii  libavformat56 6:11.4-1~deb8u1
ii  libavresample26:11.4-1~deb8u1
ii  libavutil54   6:11.4-1~deb8u1
ii  libbluray11:0.6.2-1
ii  libbs2b0  3.1.0+dfsg-2.1
ii  libc6 2.19-18
ii  libcaca0  0.99.beta19-2
ii  libcdio-cdda1 0.83-4.2
ii  libcdio-paranoia1 0.83-4.2
ii  libcdio13 0.83-4.2
ii  libdca0   0.0.5-7
ii  libdirectfb-1.2-9 1.2.10.0-5.1
ii  libdv41.0.0-6
ii  libdvdread4   5.0.0-1
ii  libenca0  1.16-1
ii  libfaad2  2.7-8
ii  libgif4   4.1.6-11
ii  libgl1-mesa-glx [libgl1]  10.3.2-1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20140719git3eb0ae6a~dfsg-2
ii  libjpeg62-turbo   1:1.3.1-12
ii  liblcms2-22.6-3+b3
ii  liblircclient00.9.0~pre1-1.2
ii  libmad0   0.15.1b-8
ii  libmpg123-0   1.20.1-2
ii  libogg0   1.3.2-1
ii  libpng12-01.2.50-2+b2
ii  libpostproc52 6:0.git20120821-4
ii  libpulse0 5.0-13
ii  libquvi7   

Bug#802310: nvidia configuration changed w.r.t. bumblebee ...

[Andreas Beckmann]

On 2015-10-21 00:09, Luca Boccassi wrote:
> Tested with 340.93-5 and also with 358.09 since it has the new extra
> module that could make things more complicated. Removed bumblebee and
> reinstalled, the glx-alternative was configured as expected. Modules are
> unloaded and card is turned off on exit. Tested with Cuda too. Looks
> good to me.

Thanks. Uploading ...

> Would be good to test on Ubuntu too, even though the packaging looks
> pretty safe and sound. I don't have access to a laptop with Ubuntu at
> the moment and I cannot install it on my Debian one unfortunately.

I don't have an Ubuntu chroot ready for test-building, maybe I should
create one :-)


Andreas

Bug#800941: marked as done (regression in 2.46: can't restore a just-trashed file)

[Debian Bug Tracking System]

Your message dated Wed, 21 Oct 2015 02:26:11 +0200
with message-id <5626dba3.4090...@debian.org>
and subject line Re: regression in 2.46: can't restore a just-trashed file
has caused the Debian Bug report #800941,
regarding regression in 2.46: can't restore a just-trashed file
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.)


-- 
800941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib2.0
Version: 2.46.0-2
Severity: critical
Justification: breaks functionality of many file managers

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=749314
Control: tags -1 stretch sid upstream
Control: affects -1 caja nemo nautilus thunar


Steps to reproduce:
1. Move some file to trash using a file manager or gvfs-trash tool.
   Tested with the following file managers: Caja, Nemo, Nautilus, Thunar.
2. Browse trash and try to restore the file.

The file manager complains that it can't determine the original location
of the file, and so doesn't restore it. This is a regression in 2.46 since
restoring worked fine in 2.44.

The problem is that "trash::orig-path" and "trash::deletion-date" attributes
are not added to the trashed file. Without that the file manager can't
determine the original location of the file, and hence can't restore it.

You can check the file attributes by printing the moved file's info:
gvfs-info trash:///file_name

Check the upstream report [1] for more details.


[1] https://bugzilla.gnome.org/show_bug.cgi?id=749314--- End Message ---
--- Begin Message ---
Version: 2.46.1-1
On Mon, 05 Oct 2015 11:53:38 +0300 =?UTF-8?B?VmxhZCBPcmxvdg==?=
 wrote:
> Source: glib2.0
> Version: 2.46.0-2
> Severity: critical
> Justification: breaks functionality of many file managers
> 
> Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=749314
> Control: tags -1 stretch sid upstream
> Control: affects -1 caja nemo nautilus thunar
> 
> 
> Steps to reproduce:
> 1. Move some file to trash using a file manager or gvfs-trash tool.
>Tested with the following file managers: Caja, Nemo, Nautilus, Thunar.
> 2. Browse trash and try to restore the file.
> 
> The file manager complains that it can't determine the original location
> of the file, and so doesn't restore it. This is a regression in 2.46 since
> restoring worked fine in 2.44.
> 
> The problem is that "trash::orig-path" and "trash::deletion-date" attributes
> are not added to the trashed file. Without that the file manager can't
> determine the original location of the file, and hence can't restore it.
> 
> You can check the file attributes by printing the moved file's info:
> gvfs-info trash:///file_name
> 
> Check the upstream report [1] for more details.
> 
> 
> [1] https://bugzilla.gnome.org/show_bug.cgi?id=749314

This was fixed in 2.46.1 by commit

0aae1bf g_local_file_trash: write info file first


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



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