date:20140821

Am 21.08.2014 08:19, schrieb Chris Tillman:
 - If you move the journal directory away and create a new one, is the
 problem gone?

 After moving it out of the way, it returns No journal files found. Same
 after re-creating /var/log/journal. After moving the directory back, the
 assertion returns.
 

So that looks like a corrupted journal then, causing the abort.

It's probably best if you file this issue upstream and share the
problematic journal file (if you don't have any privacy concerns), so
the upstream developers have a chance reproducing the issue.

Once you filed the bug report upstream, please report back so we can
link the bug reports.


-- 
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#702882: Status of igraph packaging for Debian

Hi Tamás,

I realised that there remains an open bug to version 0.6.5.  Could you
please check whether this exists or not.  Mathieu, what do you think?

Kind regards

Andreas.

On Mon, Aug 18, 2014 at 12:09:51PM +0200, Tamás Nepusz wrote:
 Hi Andreas,
 
  OK, I have updated debian/watch file (please checkout svn[1]). I'd
  suggest to always use this for packaging issues and keep us (= the
  Debian Med team) informed about needed changes. The new version was
  just uploaded to unstable.
 Thanks, looks great!
 
 Also, I'm happy to maintain the offician debian/ dir of igraph at 
 svn.debian.org in the future. I'll send a request to join the Debian-med team 
 on Alioth soon. Also, I was wondering whether I should also maintain the 
 debian/ dir of python-igraph, but it looks like that belongs to a different 
 team so maybe it's better if I ask there.
 
  What I would be really wondering is the Role of R igraph. I realised
  that it contains a code copy of (c-)igraph which is somehow against
  Debian policy.
 I'm not that familiar with R packaging (on our side it is Gabor who is 
 responsible for developing and maintaining the R interface of igraph) but I 
 have a vague recollection that he once said that R packages that depend on an 
 external C library usually also contain a copy of the source code of that 
 library and compile the whole thing (i.e. the dependent library and the 
 actual glue code between R and the library) in one batch when someone runs 
 install.packages(...) from R. This is probably the reason why the R 
 interface of igraph also contains a copy of the C library. But again, I never 
 created R packages so I might be wrong here and the best is probably ask 
 someone who is more familiar with R packages to see how it is done in 
 practice (as I'm pretty sure that igraph is not the only R package that 
 depends on an external C library).
 
 Best regards,
 Tamas
 

-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758772: CVE-2014-3589

2014-08-21 Thread Moritz Muehlenhoff

Source: pillow
Severity: important
Tags: security

https://github.com/python-pillow/Pillow/commit/205e056f8f9b06ed7b925cf8aa0874bc4aaf8a7d
has been assigned CVE-2014-3589

Cheers,
Moritz


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#747259: [Help] gfortran problem: Cannot assign to a named constant

Hi,

any idea how to resolve this gfortran problem:

Automatic builds of abinit with gfortran 4.8.2 (as unstable uses these
days) have been failing:

  gfortran -DHAVE_CONFIG_H -I. -I../.. -I../../src/incs -I../../src/incs 
-I/«BUILDDIR»/abinit-7.6.3+dfsg/fallbacks/exports/include   -ffree-form 
-J/«BUILDDIR»/abinit-7.6.3+dfsg/src/mods   -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -c -o m_ListCdagC.o m_ListCdagC.F90
  m_ListCdagC.F90:129.29:
  
IF(ALLOCATED(list_1%list)) THEN \newline deallocate(list_1%list, 
stat=ABI_ALL
   1
  Error: Cannot assign to a named constant at (1)
  m_ListCdagC.F90:242.29:
  
  IF(ALLOCATED(list_temp)) THEN \newline deallocate(list_temp, 
stat=ABI_ALLOC
   1
  Error: Cannot assign to a named constant at (1)
  m_ListCdagC.F90:954.29:
  
IF(ALLOCATED(list_1%list)) THEN \newline deallocate(list_1%list, 
stat=ABI_ALL
   1
  Error: Cannot assign to a named constant at (1)
  make[4]: *** [m_ListCdagC.o] Error 1
  make[4]: Leaving directory `/«BUILDDIR»/abinit-7.6.3+dfsg/src/62_ctqmc'



Thanks for any hint

  Andreas.

-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#696981: munin: Cron job warn about not a reference at /usr/share/perl5/Munin/Master/Utils.pm line 908

2014-08-21 Thread Petter Reinholdtsen

[Steve Schnepp]
 This bug has popped up also seemingly randomly on fresh install of other
 distrib.
 
 It was always caused by no node being configured, or more exactly the
 single node being incorrectly configured.
 
 There was a mismatch between the naming config of the node in the master
 and in the node (which usually are both on the same host when this triggers)
 
 Could you check if that's the case in your install ?

In my case, there is no node configured at all.  The attached file is
the generated configuration, showing no node, and there is nothing in
the .d directory.

Are you able to reproduce it too?

-- 
Happy hacking
Petter Reinholdtsen
# Munin server configuration generated from cron using sitesummary
# data by /usr/sbin/sitesummary-update-munin
# Do not edit, it will be overwritten. 
# Edit /etc/munin/munin.conf.pre and
# /etc/munin/munin.conf.post instead.

dbdir   /var/lib/munin
htmldir /var/cache/munin/www
logdir  /var/log/munin
rundir  /var/run/munin
tmpldir /etc/munin/templates

# (Exactly one) directory to include all files from.
#
includedir /etc/munin/munin-conf.d

Bug#758764: [Aptitude-devel] Bug#758764: E: Internal error: couldn't generate list of packages to download

2014-08-21 Thread Axel Beckert

Control: tag -1 + moreinfo

Hi Dan,

積丹尼 Dan Jacobson wrote:
 Package: aptitude
 Version: 0.6.11-1
 
 # set libglib2.0-data
 # aptitude install $@
 The following packages will be upgraded: 
   libglib2.0-data  
 1 packages upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
 Need to get 0 B of archives. After unpacking 11.3 kB will be used.
 Do you want to continue? [Y/n/?] 
 E: Can't find a source to download version '8:6.8.8.9-3' of 
 'imagemagick-doc:i386'
 E: Can't find a source to download version '8:6.8.8.9-3' of 
 'imagemagick-doc:i386'
 E: Internal error: couldn't generate list of packages to download

Interesting. The error messages seem totally unrelated. Did you have
any other actions scheduled, e.g. via aptitude $action
--schedule-only $package or the TUI?

Why should be there a version 8:6.8.8.9-3 of imagemagick? The newest
version of imagemagick in the archive is only 8:6.8.8.9-2 according to
https://packages.qa.debian.org/i/imagemagick.html (which includes
what's on incoming.debian.org btw.)

My guess is that there is the installation of imagemagick-doc:i386
version 8:6.8.8.9-3 scheduled, but it's nowhere available anymore. It
must have been installed (or scheduled to be installed from a local
APT repo) in the past, maybe self-compiled and then removed or
downgraded with non-aptitude, e.g. dpkg -i.

Please tell us about the history of imagemagick-doc:i386 on your
system. (/var/log/dpkg.log and /var/log/aptitude may help there.)

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758764: [Aptitude-devel] Bug#758764: E: Internal error: couldn't generate list of packages to download

2014-08-21 Thread 積丹尼 Dan Jacobson

All I know is that I am a victim of bug 758760 .

All I know is I just to aptitude safe-upgrade and must have swallowed
something weird yesterday and can't get it out of my system today.

grep -h imagemagick-doc /var/log/dpkg.log /var/log/aptitude |uniq

2014-08-13 11:44:15 upgrade imagemagick-doc:all 8:6.8.8.9-3 8:6.8.9.6-1
2014-08-13 11:44:15 status half-configured imagemagick-doc:all 8:6.8.8.9-3
2014-08-13 11:44:15 status unpacked imagemagick-doc:all 8:6.8.8.9-3
2014-08-13 11:44:16 status half-installed imagemagick-doc:all 8:6.8.8.9-3
2014-08-13 11:44:35 status half-installed imagemagick-doc:all 8:6.8.8.9-3
2014-08-13 11:44:36 status unpacked imagemagick-doc:all 8:6.8.9.6-1
2014-08-13 11:44:37 status unpacked imagemagick-doc:all 8:6.8.9.6-1
2014-08-13 11:45:32 configure imagemagick-doc:all 8:6.8.9.6-1 none
2014-08-13 11:45:32 status unpacked imagemagick-doc:all 8:6.8.9.6-1
2014-08-13 11:45:32 status half-configured imagemagick-doc:all 8:6.8.9.6-1
2014-08-13 11:45:32 status installed imagemagick-doc:all 8:6.8.9.6-1
2014-08-21 12:07:45 upgrade imagemagick-doc:all 8:6.8.9.6-1 8:6.8.9.6-2
2014-08-21 12:07:45 status half-configured imagemagick-doc:all 8:6.8.9.6-1
2014-08-21 12:07:45 status unpacked imagemagick-doc:all 8:6.8.9.6-1
2014-08-21 12:07:45 status half-installed imagemagick-doc:all 8:6.8.9.6-1
2014-08-21 12:29:20 upgrade imagemagick-doc:all 8:6.8.9.6-1 8:6.8.9.6-2
2014-08-21 12:29:20 status half-installed imagemagick-doc:all 8:6.8.9.6-1
2014-08-21 12:33:54 upgrade imagemagick-doc:all 8:6.8.9.6-1 8:6.8.9.6-2
2014-08-21 12:33:54 status half-installed imagemagick-doc:all 8:6.8.9.6-1
2014-08-21 12:35:28 upgrade imagemagick-doc:all 8:6.8.9.6-1 8:6.8.9.6-2
2014-08-21 12:35:28 status half-installed imagemagick-doc:all 8:6.8.9.6-1
2014-08-21 12:38:37 upgrade imagemagick-doc:all 8:6.8.9.6-1 8:6.8.9.6-2
2014-08-21 12:38:37 status half-installed imagemagick-doc:all 8:6.8.9.6-1
2014-08-21 13:10:45 upgrade imagemagick-doc:all 8:6.8.9.6-1 8:6.8.9.6-2
2014-08-21 13:10:45 status half-installed imagemagick-doc:all 8:6.8.9.6-1
[HOLD] imagemagick-doc:i386
[UPGRADE] imagemagick-doc:i386 8:6.8.8.9-3 - 8:6.8.9.6-1
[HOLD] imagemagick-doc:i386
[UPGRADE] imagemagick-doc:i386 8:6.8.9.6-1 - 8:6.8.9.6-2


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758690: kde-telepathy: cant connect to my accounts (xmpp, icq, gmail)

2014-08-21 Thread Stefan Krueger

Hello,
 
thanks for you reply.
I think its a problem between Kwallet and telepathy.
If i close telepathy and kick it from kwallet (Access Control) and start 
telepathy again he ask me to have access to it, i said Always Allow and it 
works.. after a reboot i must do the same again.



PS: do you run telepathy-idle with IRC? i've installed telepathy-idle but if i 
add an account i dont see IRC

best regards 
Stefan


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#745766: libtesseract-dev: please install pkg-config file

2014-08-21 Thread Christian Marillat

On Thu, 24 Apr 2014 22:54:07 +0200 Alessandro Ghedini gh...@debian.org wrote:
 Package: libtesseract-dev
 Version: 3.03.03-1
 Severity: normal
 Tags: patch
 
 Hi,
 
 tesseract provides a pkg-config file (tesseract.pc) and it'd be nice if the
 Debian package installed it so that software depending on tesseract can easily
 detect its presence.

Would be nice to see this bug fixed before the Jessie release.

Christian


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758392: systemd: Assertion caused by journalctl --listboots

2014-08-21 Thread Chris Tillman

Filed upstream bug 82894.


On Thu, Aug 21, 2014 at 6:27 PM, Michael Biebl bi...@debian.org wrote:

 Am 21.08.2014 08:19, schrieb Chris Tillman:
  - If you move the journal directory away and create a new one, is the
  problem gone?
 
  After moving it out of the way, it returns No journal files found. Same
  after re-creating /var/log/journal. After moving the directory back, the
  assertion returns.
 

 So that looks like a corrupted journal then, causing the abort.

 It's probably best if you file this issue upstream and share the
 problematic journal file (if you don't have any privacy concerns), so
 the upstream developers have a chance reproducing the issue.

 Once you filed the bug report upstream, please report back so we can
 link the bug reports.


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




-- 
Chris Tillman
Developer

Bug#758773: deja-dup: Does not start scheduled back-up

2014-08-21 Thread Albin Stjerna

Package: deja-dup
Version: 30.0-1
Severity: important

Dear Maintainer,

On my system, deja-dup does not run scheduled back-ups, despite my telling it 
to via the preferences. However, it does run fine when I click the back up 
now button. Altering the back-up preferences and re-setting them does not 
affect the outcome.

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

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

Versions of packages deja-dup depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.20.0-2
ii  duplicity0.6.24-1
ii  libatk1.0-0  2.12.0-1
ii  libc62.19-9
ii  libcairo-gobject21.12.16-2
ii  libcairo21.12.16-2
ii  libgdk-pixbuf2.0-0   2.30.7-1
ii  libgirepository-1.0-11.40.0-2
ii  libglib2.0-0 2.40.0-4
ii  libgtk-3-0   3.12.2-2
ii  libnautilus-extension1a  3.12.2-1
ii  libnotify4   0.7.6-2
ii  libpango-1.0-0   1.36.3-1
ii  libpangocairo-1.0-0  1.36.3-1
ii  libpeas-1.0-01.10.0-2+b1
ii  libsecret-1-00.18-1

Versions of packages deja-dup recommends:
ii  gvfs-backends1.20.2-1
ii  openssh-client [ssh-client]  1:6.6p1-7
ii  python-boto  2.29.1-1
pn  python-cloudfilesnone

deja-dup suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758764: [Aptitude-devel] Bug#758764: E: Internal error: couldn't generate list of packages to download

2014-08-21 Thread Axel Beckert

Control: tag -1 - moreinfo

Hi Dan,

thanks for the additional information!

積丹尼 Dan Jacobson wrote:
 All I know is that I am a victim of bug 758760 .
 
 All I know is I just to aptitude safe-upgrade and must have swallowed
 something weird yesterday and can't get it out of my system today.
 
 grep -h imagemagick-doc /var/log/dpkg.log /var/log/aptitude |uniq
 
 2014-08-13 11:44:15 upgrade imagemagick-doc:all 8:6.8.8.9-3 8:6.8.9.6-1

Hrm, I may have misread 8:6.8.8.9-3 as 8:6.8.9.6-3. So scrap that idea
of a locally installed version of the version in experimental + 1.

 2014-08-13 11:44:15 status half-configured imagemagick-doc:all 8:6.8.8.9-3
 2014-08-13 11:44:15 status unpacked imagemagick-doc:all 8:6.8.8.9-3
 2014-08-13 11:44:16 status half-installed imagemagick-doc:all 8:6.8.8.9-3
 2014-08-13 11:44:35 status half-installed imagemagick-doc:all 8:6.8.8.9-3
 2014-08-13 11:44:36 status unpacked imagemagick-doc:all 8:6.8.9.6-1
 2014-08-13 11:44:37 status unpacked imagemagick-doc:all 8:6.8.9.6-1
 2014-08-13 11:45:32 configure imagemagick-doc:all 8:6.8.9.6-1 none
 2014-08-13 11:45:32 status unpacked imagemagick-doc:all 8:6.8.9.6-1
 2014-08-13 11:45:32 status half-configured imagemagick-doc:all 8:6.8.9.6-1
 2014-08-13 11:45:32 status installed imagemagick-doc:all 8:6.8.9.6-1
 2014-08-21 12:07:45 upgrade imagemagick-doc:all 8:6.8.9.6-1 8:6.8.9.6-2
 2014-08-21 12:07:45 status half-configured imagemagick-doc:all 8:6.8.9.6-1
 2014-08-21 12:07:45 status unpacked imagemagick-doc:all 8:6.8.9.6-1
 2014-08-21 12:07:45 status half-installed imagemagick-doc:all 8:6.8.9.6-1
 2014-08-21 12:29:20 upgrade imagemagick-doc:all 8:6.8.9.6-1 8:6.8.9.6-2
 2014-08-21 12:29:20 status half-installed imagemagick-doc:all 8:6.8.9.6-1
 2014-08-21 12:33:54 upgrade imagemagick-doc:all 8:6.8.9.6-1 8:6.8.9.6-2
 2014-08-21 12:33:54 status half-installed imagemagick-doc:all 8:6.8.9.6-1
 2014-08-21 12:35:28 upgrade imagemagick-doc:all 8:6.8.9.6-1 8:6.8.9.6-2
 2014-08-21 12:35:28 status half-installed imagemagick-doc:all 8:6.8.9.6-1
 2014-08-21 12:38:37 upgrade imagemagick-doc:all 8:6.8.9.6-1 8:6.8.9.6-2
 2014-08-21 12:38:37 status half-installed imagemagick-doc:all 8:6.8.9.6-1
 2014-08-21 13:10:45 upgrade imagemagick-doc:all 8:6.8.9.6-1 8:6.8.9.6-2
 2014-08-21 13:10:45 status half-installed imagemagick-doc:all 8:6.8.9.6-1
 [HOLD] imagemagick-doc:i386
 [UPGRADE] imagemagick-doc:i386 8:6.8.8.9-3 - 8:6.8.9.6-1
 [HOLD] imagemagick-doc:i386
 [UPGRADE] imagemagick-doc:i386 8:6.8.9.6-1 - 8:6.8.9.6-2

The interesting thing here is as far as I can see that sometimes,
imagemagick-doc seems an arch:all (dpkg.log) and sometimes an
arch:i386 (aptitude's log) package. According to apt-cache show it's
arch:all in both, Sid and Experimental.

So thanks for the additional information! Looks like an multiarch
issues in aptitude to me.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758699: mercurial-git: AttributeError: 'gitrepo' object has no attribute 'changegroup'

2014-08-21 Thread Qijiang Fan

Hello,

It should be fixed in the svn repository.

Could you please help sponsor the upload ?


Thanks



On Wed, Aug 20, 2014 at 5:40 PM, Jakub Wilk jw...@debian.org wrote:

 Package: mercurial-git
 Version: 0.4.0-2
 Severity: grave

 I can't clone any git repository:

 $ hg clone git://anonscm.debian.org/collab-maint/pdf2djvu.git
 destination directory: pdf2djvu
 requesting all changes
 ** Unknown exception encountered with possibly-broken third-party
 extension git
 ** which supports versions 2.3.1 of Mercurial.
 ** Please disable git and try your action again.
 ** If that fixes the bug please report it to
 https://bitbucket.org/durin42/hg-git/issues
 ** Python 2.7.8 (default, Aug 18 2014, 10:01:58) [GCC 4.9.1]
 ** Mercurial Distributed SCM (version 3.1)
 ** Extensions loaded: git
 Traceback (most recent call last):
  File /usr/bin/hg, line 43, in module
mercurial.dispatch.run()
  File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 28,
 in run
sys.exit((dispatch(request(sys.argv[1:])) or 0)  255)
  File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 69,
 in dispatch
ret = _runcatch(req)
  File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 138,
 in _runcatch
return _dispatch(req)
  File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 820,
 in _dispatch
cmdpats, cmdoptions)
  File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 600,
 in runcommand
ret = _runcommand(ui, options, cmd, d)
  File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 911,
 in _runcommand
return checkargs()
  File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 882,
 in checkargs
return cmdfunc()
  File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 817,
 in lambda
d = lambda: util.checksignature(func)(ui, *args, **cmdoptions)
  File /usr/lib/python2.7/dist-packages/mercurial/util.py, line 550, in
 check
return func(*args, **kwargs)
  File /usr/lib/python2.7/dist-packages/mercurial/commands.py, line
 1331, in clone
branch=opts.get('branch'))
  File /usr/lib/python2.7/dist-packages/mercurial/hg.py, line 402, in
 clone
destpeer.local().clone(srcpeer, heads=revs, stream=stream)
  File /usr/lib/python2.7/dist-packages/mercurial/localrepo.py, line
 1731, in clone
return self.pull(remote, heads)
  File /usr/lib/python2.7/dist-packages/mercurial/localrepo.py, line
 1579, in pull
return exchange.pull (self, remote, heads, force)
  File /usr/lib/python2.7/dist-packages/mercurial/exchange.py, line 566,
 in pull
_pullchangeset(pullop)
  File /usr/lib/python2.7/dist-packages/mercurial/exchange.py, line 652,
 in _pullchangeset
cg = pullop.remote.changegroup(pullop.fetch, 'pull')
 AttributeError: 'gitrepo' object has no attribute 'changegroup'

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

 Kernel: Linux 3.14-2-amd64 (SMP w/1 CPU core)
 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
 Shell: /bin/sh linked to /bin/dash

 Versions of packages mercurial-git depends on:
 ii  mercurial   3.1-1
 ii  python  2.7.8-1
 ii  python-dulwich  0.9.7-2

 --
 Jakub Wilk




-- 
Qijiang Fan
GPG KEY ID (LONG): 3983 9DD3 50E4 6156
If you need a GPG encrypted and/or signed email, please tell in advance.
If you're not intended to receive this email, please don't forward it to
anyone else, please delete it and its copies, including all attachments,
and please let the sender know it went to the wrong person. Thanks.

Bug#746858: Status of igstk (should we remove the package?)

Hi,

as you might have noticed igstk is RC buggy and also lagging behind
upstream (5.2).  If nobody has any interest in keeping the package alive
we might consider droping it from the archive.

What do you think?

Kind regards

  Andreas.

-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758774: /etc/cron.d/php5: sessionclean script missing from package

2014-08-21 Thread Daniel Néri

Package: php5-common
Version: 5.4.4-14+deb7u13
Severity: normal
File: /etc/cron.d/php5

  Hello,

This version of php5-common changed /etc/cron.d/php5 to use a script
sessionclean but this script is not included in the package.


Regards,
Daniel


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

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

Versions of packages php5-common depends on:
ii  dpkg1.16.15
ii  libc6   2.13-38+deb7u3
ii  lsof4.86+dfsg-1
ii  psmisc  22.19-1+deb7u1
ii  sed 4.2.1-10
ii  ucf 3.0025+nmu3

php5-common recommends no packages.

php5-common suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758755: [pkg-cryptsetup-devel] Bug#758755: libcryptsetup4-udeb: depends on libgcrypt20-udeb, which doesn't exist

2014-08-21 Thread Jonas Meurer


Hi Cyril,

Am 2014-08-21 01:10, schrieb Cyril Brulebois:

Package: libcryptsetup4-udeb
Version: 2:1.6.6-1
Severity: grave
Justification: renders package unusable

Hi,

your package is no longer installable, because it now depends on
libgcrypt20-udeb, which is nowhere to be found.


now that you report the bugs I realize that I should have checked 
myself.


@GnuTLS-Maint: what's the reason for not shipping a libgcrypt20-udev 
yet?

Do you intend to fix #758756 soon?

Likely a bug in libgcrypt20 (which builds no udeb but leads you to get 
a
dependency on it) which I'm about to file. I don't see it in the 
archive

or in NEW at least.

The switch to libgcrypt20 seems premature to me.


I see. Reason for the switch to gcrypt 1.6 was the recent Whirlpool 
cipher

bug in gcrypt 1.5.3:

http://lists.gnupg.org/pipermail/gcrypt-devel/2014-January/002889.html
http://www.saout.de/pipermail/dm-crypt/2014-January/003799.html
http://www.saout.de/pipermail/dm-crypt/2014-February/003956.html

Also see section '8.3 Gcrypt after 1.5.3 breaks Whirlpool' in cryptsetup 
FAQ:

https://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#8._Issues_with_Specific_Versions_of_cryptsetup

Kind regards,
 jonas


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758775: /usr/bin/qemu-system-i386: No RBD support in wheezy-backports

2014-08-21 Thread Alexis Lahouze

Package: qemu-system-x86
Version: 2.1+dfsg-2~bpo70+2
Severity: important
File: /usr/bin/qemu-system-i386

Dear Maintainer,

I am planning to use KVM with VM virtual disks stored in a Ceph
cluster, using wheezy-backports package.

Ceph packages are present in wheezy-backports repository, so I don't
understand why RBD support is systematicaly disabled as in changelog
for version 2.1+dfsg-2~bpo70+2.

Could you keep RBD support on future releases in wheezy-backports?

Best regards,
Alexis Lahouze.


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

Kernel: Linux 3.2.0-4-amd64 (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

Versions of packages qemu-system-x86 depends on:
ii  ipxe-qemu   1.0.0+git-20120202.f6840ba-3
ii  libaio1 0.3.109-3
ii  libasound2  1.0.25-4
ii  libbluetooth3   4.99-2
ii  libbrlapi0.54.4-10+deb7u1
ii  libc6   2.13-38+deb7u3
ii  libcurl3-gnutls 7.26.0-1+wheezy9
ii  libfdt1 1.3.0-4
ii  libgcc1 1:4.7.2-5
ii  libglib2.0-02.33.12+really2.32.4-5
ii  libgnutls26 2.12.20-8+deb7u2
ii  libiscsi2   1.12.0-2~bpo70+1
ii  libjpeg88d-1+deb7u1
ii  libncurses5 5.9-10
ii  libpixman-1-0   0.26.0-4+deb7u1
ii  libpng12-0  1.2.49-1
ii  libpulse0   4.0-6~bpo7+1
ii  libsasl2-2  2.1.25.dfsg1-6+deb7u1
ii  libsdl1.2debian 1.2.15-5
ii  libspice-server10.12.4-0nocelt2~bpo70+1
ii  libssh2-1   1.4.2-1.1
ii  libtinfo5   5.9-10
ii  libusb-1.0-02:1.0.19-1~bpo70+1
ii  libusbredirparser1  0.6-2~bpo70+1
ii  libuuid12.20.1-5.3
ii  libvdeplug2 2.3.2-4
ii  libx11-62:1.5.0-1+deb7u1
ii  libxen-4.1  4.1.4-3+deb7u2
ii  libxenstore3.0  4.1.4-3+deb7u2
ii  qemu-system-common  2.1+dfsg-2~bpo70+2
ii  seabios 1.7.5-1~bpo70+1
ii  zlib1g  1:1.2.7.dfsg-13

Versions of packages qemu-system-x86 recommends:
ii  qemu-utils  2.1+dfsg-2~bpo70+2

Versions of packages qemu-system-x86 suggests:
ii  kmod 9-3
pn  ovmf none
pn  sambanone
pn  sgabios  none
ii  vde2 2.3.2-4

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758608: collectd-core: It seems that collectd-core does not depends on libmnl

2014-08-21 Thread Andrei POPESCU

Control: reassign -1 collectd-core 5.4.1-3+b1

On Ma, 19 aug 14, 10:18:39, Benoit C. wrote:
 Source: collectd-core
 Version: 5.4.1-3+b1
 Severity: normal
 
 Dear Maintainer,
 
 restarting collectd-core leads to this warning:
 ERROR: lt_dlopen (/usr/lib/collectd/netlink.so) failed: file not
 found. The most common cause for this problem are missing dependencies.
 Use ldd(1) to check the dependencies of the plugin / shared object.
 
 So I checked:
 
 # ldd /usr/lib/collectd/netlink.so
 linux-gate.so.1 (0xb774b000)
 libmnl.so.0 = not found
 libdl.so.2 = /lib/i386-linux-gnu/i686/cmov/libdl.so.2 (0xb7737000)
 libc.so.6 = /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb758b000)
 /lib/ld-linux.so.2 (0xb774c000)
 
 Installing libmnl solves the problem.
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers unstable
   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
 Architecture: amd64 (x86_64)
 
 Kernel: Linux 3.2.57 (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

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Bug#758775: /usr/bin/qemu-system-i386: No RBD support in wheezy-backports

2014-08-21 Thread Alexis Lahouze

Anyway, I think librados2 and librbd1 could be in recommends and not
in direct dependency.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758531:

2014-08-21 Thread Daniele Scasciafratte

The command for downgrade without problem:

apt-get download libpulse0:i386=5.0-6
apt-get download libpulse0:amd64=5.0-6
dpkg -i ./libpulse0_5.0-6_i386.deb
dpkg -i ./libpulse0_5.0-6_amd64.deb

KDE now works without problem :-)

Bug#758776: please build a python3-clang package

2014-08-21 Thread Matthias Klose

Package: src:llvm-toolchain-3.5

please build a python3-clang package.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758777: please build a python3-clang package

2014-08-21 Thread Matthias Klose

Package: src:llvm-toolchain-snapshot

please build a python3-clang package.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758619: more complete backtrace

2014-08-21 Thread Simon McVittie

forwarded 758619 https://bugzilla.gnome.org/show_bug.cgi?id=735141
found 758619 glib2.0/2.41.2-1
notfound 758619 glib2.0/2.40.0-4
thanks

On 20/08/14 22:50, Eric Valette wrote:
 Because I use the glib/gtk from experimental I guess.

Thanks, yes, it's that. Specifically, this change:

https://bugzilla.gnome.org/show_bug.cgi?id=731986

In particular, the abort on incorrect locking is new; the original plan
seems to have been for it to be runtime-optional.

I've sent this upstream to ask whether runtime-optional is feasible.

S


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#747259: Aw: [Debichem-devel] Bug#747259: [Help] gfortran problem: Cannot assign to a named constant

2014-08-21 Thread Daniel Leidert



Hi,



Remove the new line (in your code newline, see below)between the IF and THEN statements.

Or else add the missing END IF statement. That should do the trick.



HTH and regards, Daniel




Gesendet:Donnerstag, 21. August 2014 um 08:47 Uhr
Von:Andreas Tille andr...@an3as.eu
An:Debian Mentors List debian-ment...@lists.debian.org, 747...@bugs.debian.org
Betreff:[Debichem-devel] Bug#747259: [Help] gfortran problem: Cannot assign to a named constant

Hi,

any idea how to resolve this gfortran problem:

Automatic builds of abinit with gfortran 4.8.2 (as unstable uses these
days) have been failing:

gfortran -DHAVE_CONFIG_H -I. -I../.. -I../../src/incs -I../../src/incs -I/BUILDDIR/abinit-7.6.3+dfsg/fallbacks/exports/include -ffree-form -J/BUILDDIR/abinit-7.6.3+dfsg/src/mods -g -O2 -fstack-protector --param=ssp-buffer-size=4 -c -o m_ListCdagC.o m_ListCdagC.F90
m_ListCdagC.F90:129.29:

IF(ALLOCATED(list_1%list)) THEN newline deallocate(list_1%list, stat=ABI_ALL
1
Error: Cannot assign to a named constant at (1)
m_ListCdagC.F90:242.29:

IF(ALLOCATED(list_temp)) THEN newline deallocate(list_temp, stat=ABI_ALLOC
1
Error: Cannot assign to a named constant at (1)
m_ListCdagC.F90:954.29:

IF(ALLOCATED(list_1%list)) THEN newline deallocate(list_1%list, stat=ABI_ALL
1
Error: Cannot assign to a named constant at (1)
make[4]: *** [m_ListCdagC.o] Error 1
make[4]: Leaving directory /BUILDDIR/abinit-7.6.3+dfsg/src/62_ctqmc



Thanks for any hint

Andreas.

--
http://fam-tille.de

___
Debichem-devel mailing list
debichem-de...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debichem-devel





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#696981: munin: Cron job warn about not a reference at /usr/share/perl5/Munin/Master/Utils.pm line 908

2014-08-21 Thread Steve Schnepp

Oh.

Looking at your config file, it seems the munin package fails to
automatically setup the local node.
Then, since there is no node that is successfully polled, it emits
this log message.

Is the Debian Edu configuration phase different from a vanilla
Debian install ?

Btw, I admit that the message could be much more user-friendly.

--
Steve Schnepp
http://blog.pwkf.org/tag/munin


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#696981: munin: Cron job warn about not a reference at /usr/share/perl5/Munin/Master/Utils.pm line 908

2014-08-21 Thread Petter Reinholdtsen

[Steve Schnepp]
 Oh.
 
 Looking at your config file, it seems the munin package fails to
 automatically setup the local node.

It probably do not fail to do so.  The config is overwritten by
sitesummary.

 Then, since there is no node that is successfully polled, it emits
 this log message.

It is not a log message.  It is a message picked up by cron and
emailed.  If it was a log message, there would not be a problem, as
the logs are rotated. :)

 Is the Debian Edu configuration phase different from a vanilla
 Debian install ?

The Debian Edu (aka sitesummary) configuration for munin is generated
using information submitted by the clients using the
sitesummary-client package.  In this case, no client have been able to
submit information yet, and thus the generated munin configuration
contain no nodes.

 Btw, I admit that the message could be much more user-friendly.

The problem is not its message content, it is the fact that it is
emailed every 5 minutes to the root user, thus filling up /var/ with
emails.

I would expect munin to not complain in cron when asked to not do
anything (which would be the request to it with a configuration file
without any nodes :).  Can you change it to not complain when no node
is listed?

-- 
Happy hacking
Petter Reinholdtsen


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758619: more complete backtrace

On 08/21/2014 10:26 AM, Simon McVittie wrote:

 In particular, the abort on incorrect locking is new; the original plan
 seems to have been for it to be runtime-optional.
 
 I've sent this upstream to ask whether runtime-optional is feasible.


Well instead of correcting the symptom, I would prefer to correct the
bug itself. If locking mecahnism is hazardous, then it eman beahavior is
hazardous and that could lead to other bugs later.

Searching for the bug, I saw that, in the past, the very same undefined
behavior caused crash instead of and assert.

But I have no time (and probably not the gtk/glib basic knowledge) to
search for a solution.

-- eric


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758619: more complete backtrace

On 08/21/2014 10:37 AM, Eric Valette wrote:

 Searching for the bug, I saw that, in the past, the very same undefined
 behavior caused crash instead of and assert.

http://debian.2.n7.nabble.com/Bug-671785-segfaults-when-running-reportbug-td548240.html


meaning the bug is not new and was triggered before evn with the pthread
lock mechanism.


-- eric


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758766: openttd: New Upstream

2014-08-21 Thread Matthijs Kooijman

Hey Matthias,

 1.4.2 is available. Most online games use it, so 1.4.1 is no longer very
 useful in multiplayer mode, hence the elevated priority.
Thanks for the reminder, I've just uploaded the new version.

Gr.

Matthijs


signature.asc
Description: Digital signature

Bug#758775: /usr/bin/qemu-system-i386: No RBD support in wheezy-backports

2014-08-21 Thread Michael Tokarev

On Thu, 21 Aug 2014 12:51:31 +0400 Michael Tokarev m...@tls.msk.ru wrote:

  Ceph packages are present in wheezy-backports repository, so I don't
  understand why RBD support is systematicaly disabled as in changelog
  for version 2.1+dfsg-2~bpo70+2.

Just a small clarification.  This is the current situation with ceph in
wheezy-backports:

 https://buildd.debian.org/status/package.php?p=cephsuite=wheezy-backports

For 28 days it can't be built on several architectures, and maintainer
does not care, -- as I said, they work in upload and forget mode, never
looking at bugs (including Fails To Build From Source (FTBFS) bugs like
this one), their package stayed with RC (release-critical) bugs for months
during wheezy release, and the situation hasn't changed since that time.
This is the actual reason I had to _disable_ ceph support in my last
bpo upload.

  Could you keep RBD support on future releases in wheezy-backports?

Did you read the bpo changelog entry in qemu package?

Thanks,

/mjt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758778: dpkg-maintscript-helper: error: original symlink target is not an absolute path

2014-08-21 Thread Andreas Cadhalpun


Package: dpkg
Version: 1.17.13
Severity: serious
Justification: makes packages uninstallable/unremovable
Affects: autoconf-archive

Dear Maintainer,

the changelog for 1.17.13 contains:
 * Fix dpkg-maintscript-helper symlink_to_dir to assure absolute
   pathnames arguments.

The problem is that now the following happens, if one tries to install 
autoconf-archive:


# dpkg -i autoconf-archive_20140228-1_all.deb
Selecting previously unselected package autoconf-archive.
(Reading database ... 11973 files and directories currently installed.)
Preparing to unpack autoconf-archive_20140228-1_all.deb ...
dpkg-maintscript-helper: error: original symlink target is not an 
absolute path
dpkg: error processing archive autoconf-archive_20140228-1_all.deb 
(--install):

 subprocess new pre-installation script returned error exit status 1
dpkg-maintscript-helper: error: original symlink target is not an 
absolute path

dpkg: error while cleaning up:
 subprocess new post-removal script returned error exit status 1
Errors were encountered while processing:
 autoconf-archive_20140228-1_all.deb

It can't even be removed with normal means:

# dpkg --purge autoconf-archive
dpkg: error processing package autoconf-archive (--purge):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting a removal
Errors were encountered while processing:
 autoconf-archive

One has to force the removal:

# dpkg --purge --force-remove-reinstreq autoconf-archive
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: package is in a very bad inconsistent state; you should
 reinstall it before attempting a removal
(Reading database ... 11973 files and directories currently installed.)
Removing autoconf-archive (20140228-1) ...

I'm not sure why dpkg-maintscript-helper was changed to fail when a 
non-absolute symlink was used, but this change should not make it into 
testing, unless all packages doing so have been fixed.


Best regards,
Andreas


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

Kernel: Linux 3.16-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set 
to C)

Shell: /bin/sh linked to /bin/dash

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.6-7
ii  libc62.19-9
ii  liblzma5 5.1.1alpha+20120614-2
ii  libselinux1  2.3-1
ii  tar  1.27.1-2
ii  zlib1g   1:1.2.8.dfsg-2

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt  1.0.6

-- no debconf information


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#756374: nouveau: Re: linux-image-3.14-1-amd64: Nouveau driver can't working good wirh all engines

2014-08-21 Thread Corcodel Marian

Package: src:linux
Version: 3.14.15-2
Followup-For: Bug #756374

Hi
Follow patch not solve this bug but is add exceptions on create objects and
driver will continue to working wo acceleration on different applications.



-- Package-specific info:
** Version:
Linux version 3.14-2-rt-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.3 (Debian 4.8.3-7) ) #1 SMP PREEMPT RT Debian 3.14.15-2 (2014-08-09)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.14-2-rt-amd64 root=/dev/mapper/debian-root ro

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

** Kernel log:
[5.776186] systemd-udevd[249]: renamed network interface eth1 to eth0
[5.796284] systemd-udevd[246]: renamed network interface rename2 to eth1
[5.993318] ACPI Warning: SystemIO range 
0x0400-0x041f conflicts with OpRegion 
0x0400-0x040f (\SMRG) (20131218/utaddress-258)
[5.993461] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[5.995479] snd-ca0106: Model 100a Rev  Serial 100a1102
[6.060076] snd_hda_intel :00:1b.0: irq 44 for MSI/MSI-X
[6.183703] [drm] Initialized drm 1.1.0 20060810
[6.254327] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input7
[6.263582] input: HDA Intel Front Headphone as 
/devices/pci:00/:00:1b.0/sound/card1/input15
[6.263791] input: HDA Intel Line Out Side as 
/devices/pci:00/:00:1b.0/sound/card1/input14
[6.265443] input: HDA Intel Line Out CLFE as 
/devices/pci:00/:00:1b.0/sound/card1/input13
[6.265617] input: HDA Intel Line Out Surround as 
/devices/pci:00/:00:1b.0/sound/card1/input12
[6.265786] input: HDA Intel Line Out Front as 
/devices/pci:00/:00:1b.0/sound/card1/input11
[6.265953] input: HDA Intel Line as 
/devices/pci:00/:00:1b.0/sound/card1/input10
[6.266121] input: HDA Intel Rear Mic as 
/devices/pci:00/:00:1b.0/sound/card1/input9
[6.266299] input: HDA Intel Front Mic as 
/devices/pci:00/:00:1b.0/sound/card1/input8
[6.336619] wmi: Mapper loaded
[6.492654] iTCO_vendor_support: vendor-support=0
[6.511378] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[6.511511] iTCO_wdt: Found a ICH9 TCO device (Version=2, TCOBASE=0x0860)
[6.511962] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[6.569368] coretemp coretemp.0: Using relative temperature scale!
[6.569868] coretemp coretemp.0: Using relative temperature scale!
[7.235265] Adding 1949692k swap on /dev/mapper/debian-swap.  Priority:-1 
extents:1 across:1949692k 
[8.305944] [drm] hdmi device  not found 1 0 1
[8.306032] nouveau  [  DEVICE][:01:00.0] BOOT0  : 0x046f00a3
[8.306081] nouveau  [  DEVICE][:01:00.0] Chipset: G72 (NV46)
[8.306128] nouveau  [  DEVICE][:01:00.0] Family : NV40
[8.306201] nouveau  [   VBIOS][:01:00.0] checking PRAMIN for image...
[8.386237] nouveau  [   VBIOS][:01:00.0] ... appears to be valid
[8.386291] nouveau  [   VBIOS][:01:00.0] using image from PRAMIN
[8.386470] nouveau  [   VBIOS][:01:00.0] BIT signature found
[8.386518] nouveau  [   VBIOS][:01:00.0] version 05.72.22.43.00
[8.386791] nouveau :01:00.0: irq 45 for MSI/MSI-X
[8.386803] nouveau  [ PMC][:01:00.0] MSI interrupts enabled
[8.386934] nouveau  [ PFB][:01:00.0] RAM type: DDR2
[8.386982] nouveau  [ PFB][:01:00.0] RAM size: 256 MiB
[8.387029] nouveau  [ PFB][:01:00.0]ZCOMP: 0 tags
[9.374176] nouveau  [  PTHERM][:01:00.0] FAN control: none / external
[9.374247] nouveau  [  PTHERM][:01:00.0] fan management: automatic
[9.374302] nouveau  [  PTHERM][:01:00.0] internal sensor: yes
[9.394220] nouveau  [ CLK][:01:00.0] 20: core 550 MHz shader 550 
MHz memory 540 MHz
[9.394296] nouveau  [ CLK][:01:00.0] --: core 199 MHz memory 391 
MHz 
[9.394505] [TTM] Zone  kernel: Available graphics memory: 2025236 kiB
[9.394559] [TTM] Initializing pool allocator
[9.394620] [TTM] Initializing DMA pool allocator
[9.394695] nouveau  [ DRM] VRAM: 252 MiB
[9.394747] nouveau  [ DRM] GART: 512 MiB
[9.394802] nouveau  [ DRM] TMDS table version 1.1
[9.394855] nouveau W[ DRM] TMDS table script pointers not stubbed
[9.394909] nouveau  [ DRM] DCB version 3.0
[9.394963] nouveau  [ DRM] DCB outp 00: 01000300 0028
[9.395017] nouveau  [ DRM] DCB outp 01: 02011310 0028
[9.395070] nouveau  [ DRM] DCB outp 02: 01011312 
[9.395124] nouveau  [ DRM] DCB outp 03: 020223f1 00c0c080
[9.395178] nouveau  [ DRM] DCB conn 00: 
[9.395265] nouveau  [ DRM] DCB conn 01: 1130
[9.395349] nouveau  [ DRM] DCB conn 02: 0210
[9.395429] nouveau  [ DRM] DCB conn 03: 0211
[9.395508] nouveau  [ DRM] DCB conn 04: 0213
[9.395790]

Bug#758619: Much simpler code to trigger the problem (extract from bug #671785)

On 08/21/2014 10:52 AM, Eric Valette wrote:

cat  test.py
#!/usr/bin/python
import gtk
gtk.gdk.threads_init()
raw_input(If this didn't crash, hit enter.)

2 r-x-ceva6380:~-python test.py
If this didn't crash, hit enter.Attempt to unlock mutex that was not locked
Aborted


#!/usr/bin/python
import gtk

gtk.gdk.threads_init()
gtk.gdk.threads_enter()  = fixes the problem
raw_input(If this didn't crash, hit enter.)

python test.py
If this didn't crash, hit enter.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#754830: bluez: Unit bluetooth.service entered failed state

2014-08-21 Thread Roman Dushko

Package: bluez
Version: 5.21-3
Followup-For: Bug #754830

Dear Maintainer,

after upgrade + dist-upgrade on Tuesday, 19 August 2014,
I noticed strange behavior of bluetooth manager (in KDE tray) - appeared
and disappeared from time to time. Next day, possibly after another set
of patches, I noticed that bluetooth service does not work anymore.

I updated bluez to the latest 5.21-3 version, compiled and installed
bluez 5.22, which installed hcitool of verions = 5.22, but still same
problem:
When I run `/etc/init.d/bluetooth status`, I receive info that Active: failed,
and some text information like:
| Failed to access management interface
| Adapter handling initialization failed
| bluetooth.service main process exited, code=exited, status=1/FAILURE
| Unit bluetooth.service entered failed state.

And nothing...

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

Kernel: Linux 3.0.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bluez depends on:
ii  dbus 1.8.6-1
ii  init-system-helpers  1.20
ii  kmod 18-1
ii  libc62.19-9
ii  libdbus-1-3  1.8.6-1
ii  libglib2.0-0 2.40.0-4
ii  libreadline6 6.3-8
ii  libudev1 208-6
ii  lsb-base 4.1+Debian13
ii  udev 208-6

bluez recommends no packages.

bluez suggests no packages.

-- Configuration Files:
/etc/dbus-1/system.d/bluetooth.conf changed:
!-- This configuration file specifies the required security policies
 for Bluetooth core daemon to work. --
!DOCTYPE busconfig PUBLIC -//freedesktop//DTD D-BUS Bus Configuration 1.0//EN
 http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd;
busconfig
  !-- ../system.conf have denied everything, so we just punch some holes --
  policy user=root
allow own=org.bluez/
allow send_destination=org.bluez/
allow send_interface=org.bluez.Agent1/
allow send_interface=org.bluez.MediaEndpoint1/
allow send_interface=org.bluez.MediaPlayer1/
allow send_interface=org.bluez.ThermometerWatcher1/
allow send_interface=org.bluez.AlertAgent1/
allow send_interface=org.bluez.Profile1/
allow send_interface=org.bluez.HeartRateWatcher1/
allow send_interface=org.bluez.CyclingSpeedWatcher1/
allow send_interface=org.freedesktop.DBus.ObjectManager/
  /policy
  policy at_console=true
allow send_destination=org.bluez/
  /policy
  !-- allow users of lp group (printing subsystem) to 
   communicate with bluetoothd --
  policy group=lp
allow send_destination=org.bluez/
  /policy
  policy context=default
deny send_destination=org.bluez/
  /policy
/busconfig


-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758780: tuxtype: Can't open lessons when using German locale

2014-08-21 Thread Ronny Standtke

Package: tuxtype
Version: 1.8.3-1~bpo70+1
Severity: normal

When running tuxtype on a system with a German locale, lessons can't be
opened.
When trying to open a lesson, tuxtype just returns to the main menu and
outputs the following error messages to the console:

error loading script
/usr/share/tuxtype/themes/deutsch/scripts/basic_lesson_01.xml
load_script() failed to load
'/usr/share/tuxtype/themes/deutsch/scripts/basic_lesson_01.xml'

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

Kernel: Linux 3.14-0.bpo.2-686-pae (SMP w/3 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tuxtype depends on:
ii  fonts-sil-andika1.002-2
ii  libc6   2.13-38+deb7u3
ii  libcairo2   1.12.2-3
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.33.12+really2.32.4-5
ii  libpango1.0-0   1.30.0-1
ii  librsvg2-2  2.36.1-2
ii  libsdl-image1.2 1.2.12-2
ii  libsdl-mixer1.2 1.2.12-3
ii  libsdl-net1.2   1.2.8-2
ii  libsdl-pango1   0.1.2-6
ii  libsdl1.2debian 1.2.15-5
ii  libt4k-common0  0.1.1-1~bpo70+1
ii  libxml2 2.8.0+dfsg1-7+wheezy1
ii  tuxtype-data1.8.3-1~bpo70+1

Versions of packages tuxtype recommends:
pn  fonts-bengnone
pn  fonts-devanone
pn  fonts-gujrnone
pn  fonts-gurunone
pn  fonts-kndanone
pn  fonts-oryanone
pn  fonts-sil-doulos  none
pn  fonts-tamlnone
pn  fonts-telunone

tuxtype suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758779: RFA: KLone -- embedded web application development framework

2014-08-21 Thread Torben Försterling

Package: wnpp
Severity: normal

I request to adopt the KLone package.

The package description is:
 This package contains KLone's source code, to be used to build custom
 kloned servers.
 .
 KLone is a fully-featured, multiplatform, web application development
 framework, targeted especially for embedded systems and appliances.
 .
 It is a self-contained solution which includes a web server and an SDK
 for creating WWW sites with both static and dynamic content. When
 using KLone, there's absolutely no need for any additional component:
 neither the HTTP/S server (e.g. Apache, Netscape, Roxen), nor the
 typical active pages engine (PHP, Perl, ASP, Python).
 .
 KLone does everything, and does it fast and small.
 .
 KLone blends the HTTP/S server application together with its content
 and configuration into a single executable file. The site developer
 writes his/her dynamic pages in C/C++ (in usual scripting style: % /*
 code */ %) and uses KLone to transform them into embeddable,
 compressed native code with the native C/C++ compiler. The result is
 then linked to the HTTP/S server skeleton to obtain one single,
 ROM-able, binary file. This means that he/she can get:
  - easy, complete and unfiltered interaction with the host operating
  system
  - dynamic pages in native compiled code, which in turn implies
  - fast execution and
  - small overall application footprint
  - all of this without giving up the common functionality of web
  application frameworks such as sessions, parsing of form
  variables, cookies, etc


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758619: more complete backtrace

2014-08-21 Thread Simon McVittie

# the real bug is #671785 but it's easy to avoid it in reportbug
reassign 758619 reportbug
tags 758619 + patch
thanks

On 21/08/14 09:37, Eric Valette wrote:
 Well instead of correcting the symptom, I would prefer to correct the
 bug itself. If locking mecahnism is hazardous, then it eman beahavior is
 hazardous and that could lead to other bugs later.

Indeed. I think it's pygtk that is getting this wrong, and as you
pointed out in another mail, we have already had a bug to track that,
#671785, since 2012. The upstream bug has had no activity since 2012
either, until today.

However, reportbug can easily work around it, whereas a solution in
pygtk is rather more involved (and might never happen, since pygtk is
deprecated upstream); so I think it would be best if the reportbug
maintainers apply the one-line workaround, which is to turn off the
broken feature with the patch that can be found at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671785#53 (the
functional part is reproduced at the end of this mail). Let's use bug
number 758619 to track that.

I now realise that the steps to reproduce the bug are:

* you have either GLib from experimental on Linux, or kFreeBSD,
  so the locking error is fatal;
* you have python-gtk2 and $DISPLAY is set, so reportbug's gtk2 UI
  module can load; as a side-effect, python-gtk2 registers the faulty
  PyOS_InputHook implementation;
* but you *do not* use the gtk2 UI module, so reportbug calls
  raw_input(), which results in the PyOS_InputHook being called

and with that information, I can reproduce it in an experimental chroot
with xvfb-run reportbug reportbug. The patch below fixes it.

As much as I'd like to say this is release-critical for python-gtk2,
which is also dead upstream, so let's remove it from Debian and tell
everyone to use Gtk 3 via pygi, I don't think the maintainers of its
300 reverse dependencies would be very impressed.

S

--- gtk2_ui.py.orig 2014-08-21 09:28:45.375375786 +
+++ gtk2_ui.py  2014-08-21 09:29:02.843495121 +
@@ -35,6 +35,7 @@
 except:
 has_spell = False

+gtk.set_interactive (0)
 gtk.gdk.threads_init ()

 import sys


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758781: preprocess: Incorrect recursive #include detection

2014-08-21 Thread Anton Nikolaevsky

Package: preprocess
Version: 1.1.0+ds-1
Severity: normal
Tags: patch

1. Have the following files:
common.sh:
first.sh:
# #include common.sh
second.sh:
# #include common.sh
result.sh:
# #include first.sh
# #include second.sh

2. Run the command 'preprocess result.sh'
Expected: no errors, just empty lines in output
Actual: preprocess: error: detected recursive #include of 'common.sh'



-- System Information:
Debian Release: 7.6
  APT prefers stable
  APT policy: (990, 'stable'), (700, 'unstable'), (500, 'experimental'), (500, 
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf
armel
i386

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

Versions of packages preprocess depends on:
ii  python 2.7.3-4+deb7u1
ii  python2.6  2.6.8-1.1
ii  python2.7  2.7.3-6+deb7u2

preprocess recommends no packages.

preprocess suggests no packages.

-- no debconf information
--- /usr/lib/python2.7/dist-packages/preprocess.py	2014-08-21 09:29:02.760427203 +0400
+++ preprocess.py	2014-08-21 09:28:45.516730105 +0400
@@ -453,7 +453,7 @@
 defines = preprocess(fname, fout, defines, force,
  keepLines, includePath, substitute,
  contentTypesRegistry=contentTypesRegistry, 
- __preprocessedFiles=__preprocessedFiles)
+ __preprocessedFiles=__preprocessedFiles[:])
 elif op in (if, ifdef, ifndef):
 if op == if:
 expr = match.group(expr)

Bug#758774: /etc/cron.d/php5: sessionclean script missing from package

2014-08-21 Thread Salvatore Bonaccorso

Hello Daniel,

On Thu, Aug 21, 2014 at 09:54:19AM +0200, Daniel Néri wrote:
 Package: php5-common
 Version: 5.4.4-14+deb7u13
 Severity: normal
 File: /etc/cron.d/php5
 
   Hello,
 
 This version of php5-common changed /etc/cron.d/php5 to use a script
 sessionclean but this script is not included in the package.

Thanks for noticing this, this falled through the cracks. 

A fixed package is ready, but we need to wait for the builds to
complete.

Regards,
Salvatore


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#671785: python-gtk2: crashes reportbug on Linux with GLib = 2.41, or kFreeBSD

2014-08-21 Thread Simon McVittie

retitle 671785 python-gtk2: crashes reportbug on Linux with GLib = 2.41, or 
kFreeBSD
thanks

On Sun, 30 Dec 2012 at 20:21:30 -0600, Jeff Epler wrote:
 But whether that
 is the case or not, pygtk really can't impose the additional requirement
 on users of raw_input() that they have to manipulate a gdk lock before
 the call; whatever it's doing had better be transparent to users of
 raw_input.

Indeed. Having just done basically the same analysis for #758619
(which is the same locking error manifesting on Linux due to GLib 2.41
having better checks similar to those in kFreeBSD, and is currently RC),
I think pygtk's PyOS_InputHook is fundamentally flawed.

I can't think of a solution to this in pygtk, other than to disable the
PyOS_InputHook by default or entirely (which would be a feature regression
for users of the interactive Python prompt; but then again, its locking
is broken anyway).

pygobject does not appear to have that feature.

I have reassigned #758619 back to reportbug and suggested that the
reportbug maintainers should explicitly turn off the PyOS_InputHook,
which would work around this bug for reportbug.

S


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758601: ruby-pg: Ships old gemspec files

2014-08-21 Thread Cédric Boutillier

Package: ruby-pg
Version: 0.17.1-1
Followup-For: Bug #758601
Control: tag -1 - moreinfo + pending

Hi Kris,

I now understood the problem. The debian/ directory of the ruby-pg
source package contains an copy of the gemspec instead that was used as
the current one.

I am preparing a new upload which will regenerate a new one from the
source.

Thanks!

Cédric



signature.asc
Description: Digital signature

Bug#758778: dpkg-maintscript-helper: error: original symlink target is not an absolute path

Hi!

On Thu, 2014-08-21 at 11:18:46 +0200, Andreas Cadhalpun wrote:
 Package: dpkg
 Version: 1.17.13
 Severity: serious
 Justification: makes packages uninstallable/unremovable
 Affects: autoconf-archive

 the changelog for 1.17.13 contains:
  * Fix dpkg-maintscript-helper symlink_to_dir to assure absolute
pathnames arguments.
 
 The problem is that now the following happens, if one tries to install
 autoconf-archive:
 
 # dpkg -i autoconf-archive_20140228-1_all.deb
 Selecting previously unselected package autoconf-archive.
 (Reading database ... 11973 files and directories currently installed.)
 Preparing to unpack autoconf-archive_20140228-1_all.deb ...
 dpkg-maintscript-helper: error: original symlink target is not an absolute
 path
 dpkg: error processing archive autoconf-archive_20140228-1_all.deb
 (--install):
  subprocess new pre-installation script returned error exit status 1
 dpkg-maintscript-helper: error: original symlink target is not an absolute
 path
 dpkg: error while cleaning up:
  subprocess new post-removal script returned error exit status 1
 Errors were encountered while processing:
  autoconf-archive_20140228-1_all.deb
 
 It can't even be removed with normal means:
 
 # dpkg --purge autoconf-archive
 dpkg: error processing package autoconf-archive (--purge):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting a removal
 Errors were encountered while processing:
  autoconf-archive

When a package contains a broken maintainer script, the way to allow
again its removal is to reinstall a fixed version, as hinted in the
error message, which in this case would need to be created and
uploaded, but all the same.

 One has to force the removal:
 
 # dpkg --purge --force-remove-reinstreq autoconf-archive
 dpkg: warning: overriding problem because --force enabled:
 dpkg: warning: package is in a very bad inconsistent state; you should
  reinstall it before attempting a removal
 (Reading database ... 11973 files and directories currently installed.)
 Removing autoconf-archive (20140228-1) ...
 
 I'm not sure why dpkg-maintscript-helper was changed to fail when a
 non-absolute symlink was used, but this change should not make it into
 testing, unless all packages doing so have been fixed.

This and any other such package (although we did a quick check over
codesearch.d.o, but I guess missed this one due to the line breaks)
were broken already, and not performing the symlink to dir switch
anyway because the code is checking if the parameter matches the
canonicalized form («readlink -f»), which it will not.

This can make dpkg lose track, remove or overwrite unintended file,
as they might end up installed in a (real) path that does not match
with the one listed in the package metadata.

I think that for this reason dpkg needs to make those break explicitly,
and that having such version in testing is more valuable than trying to
avoid those packages to explicitly break, instead of allowing the
possibly silent breakage.

I'm thus probably just going to either close or reassign this bug
report to the affected package(s).

Thanks,
Guillem


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758619: more complete backtrace


 --- gtk2_ui.py.orig   2014-08-21 09:28:45.375375786 +
 +++ gtk2_ui.py2014-08-21 09:29:02.843495121 +
 @@ -35,6 +35,7 @@
  except:
  has_spell = False
 
 +gtk.set_interactive (0)
  gtk.gdk.threads_init ()
 
  import sys
 


I confirm this also fixes the bug for me. Thanks for the support.

-- eric


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758224: Confused about libpulse0 libsystemd-journal0 dependency

2014-08-21 Thread Godefridus Daalmans


Control: tags -1 moreinfo unreproducible
Hi,

On Fri, Aug 15, 2014 at 10:50 AM, Frits Daalmans 
fr...@daalmansdata.eu

wrote:

Package: pulseaudio
Version: 5.0-6
Severity: normal

Problem: can't install libpulse0:i386 5.0-6 on system with
libpulse0:amd64 5.0-6

I have a mixed amd64 / i386 architecture system, have libpulse0:amd64
upgraded to 5.0-6, and wished to upgrade libpulse0:i386 from 4.0-6+b1 
to

5.0-6
for skype.

libpulse0 version 5.0-6 has a new Depends: libsystemd-journal0 (= 
183)


libsystemd-journal0 version 204-7 for amd64 architecture is installed.

I don't know much about libsystemd-journal0, but its description
mentions it
provides an interface for the systemd journal service.

My question / bug report is this: is the dependency of libpulse0 on
libsystemd-journal0 architecture-independent, or must I have a 
specific

32-bit
libsystemd-journal0:i386 installed in order to get libpulse0:i386
working
(that is what apt-get is telling me)


Yes, you need that. The systemd libs are multiarch-enabled, so it 
should

work.



(The latter is not an option because on my, admittedly experimental,
system it wants to remove pulseaudio and systemd(!!), as well as 260
other packages.


This is the part that is broken, then. What does 'apt install
libpulse0:i386=5.0-6' say?

--

Saludos,
Felipe Sateler


Hi Felipe,

I have run a little experiment: first of all, baseline experiment,
apt-get install -f doesn't install anything.

apt-get install libpulse0:i386=5.0-6

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libpulse0:i386 : Depends: libsystemd-journal0:i386 (= 183) but it is 
not going to be installed

E: Unable to correct problems, you have held broken packages.

libsystemd-journal0 version 208-6 depends on libc6, libgcrypt11, 
liblzma5, libselinux1


apt-get install libsystemd-journal0:i386
... (details omitted)
114 upgraded, 64 newly installed, 262 to remove and 700 not upgraded.

it seems to want to remove eclipse, KDE, gnome, pulseaudio, and systemd.

Then I dug a bit deeper into the depends of libsystemd-journal0:i386
I don't want to have a complete i386 installation: I normally work with 
amd64, with the minimal number of i386 libraries for skype and a few 
games.


apt-cache show libsystemd-journal0:i386=208-6

I think the relevant info is:

Package: libsystemd-journal0
Source: systemd
Version: 208-6
Architecture: i386
Depends: libc6 (= 2.9), libgcrypt11 (= 1.5.1), liblzma5 (= 
5.1.1alpha+20120614), libselinux1 (= 1.32)

Pre-Depends: multiarch-support
Priority: optional


If I do a dpkg -l | egrep ' (libc6|libgcrypt11|liblzma5|libselinux1)'
I get:

ii  libc6:amd642.19-7
   amd64GNU C Library: Shared libraries
ii  libc6:i386 2.19-7
   i386 GNU C Library: Shared libraries
ii  libgcrypt11:amd64  1.5.3-3   
   amd64LGPL Crypto library - runtime library
ii  libgcrypt11:i386   1.5.3-3   
   i386 LGPL Crypto library - runtime library
ii  liblzma5:amd64 5.1.1alpha+20120614-2 
   amd64XZ-format compression library
ii  liblzma5:i386  5.1.1alpha+20120614-2 
   i386 XZ-format compression library
ii  libselinux1:amd64  2.3-1 
   amd64SELinux runtime shared libraries
ii  libselinux1:i386   2.3-1 
   i386 SELinux runtime shared libraries


hmm.. so all of the dependencies should already be satisfied, for both 
architectures,
in fact the installed versions are identical for both (seems the 
sanest).


Also multiarch-support is in place


Anyway, for each of the dependencies I did an apt-get -s install, 
results:


apt-get -s install libc6:i386

broken on my computer:

The following packages have unmet dependencies:
 tar : PreDepends: libacl1 (= 2.2.51-8) but it is not going to be 
installed

   PreDepends: libc6 (= 2.17) but it is not going to be installed
   PreDepends: libselinux1 (= 1.32) but it is not going to be 
installed


apt-get -s install libgcrypt11:i386

apt-get wants to do an unacceptable solution:
(...)
156 upgraded, 62 newly installed, 660 to remove and 648 not upgraded.


apt-get -s install liblzma5:i386

liblzma5:i386 is already the newest version.

apt-get -s install libselinux1:i386

libselinux1:i386 is already the newest version.



I hope that this information is helpful.

Bug#758778: dpkg-maintscript-helper: error: original symlink target is not an absolute path

On Thu, 2014-08-21 at 11:18:46 +0200, Andreas Cadhalpun wrote:
 Package: dpkg
 Version: 1.17.13
 Severity: serious
 Justification: makes packages uninstallable/unremovable
 Affects: autoconf-archive

 the changelog for 1.17.13 contains:
  * Fix dpkg-maintscript-helper symlink_to_dir to assure absolute
pathnames arguments.
 
 The problem is that now the following happens, if one tries to install
 autoconf-archive:

The only other affected package is lilypond. I'll check the actual
effect from dir_to_symlink too, cook a list and send to debian-devel@.
And file some RC bugs at the same time.

Thanks,
Guillem


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758780: tuxtype: Can't open lessons when using German locale

2014-08-21 Thread Holger Levsen

control: tags -1 + confirmed upstream

Hi Ronny,

thanks for your bug report!

On Donnerstag, 21. August 2014, Ronny Standtke wrote:
 Version: 1.8.3-1~bpo70+1

this version doenst exist, am I right to assume you are using a local 
backport?

 When running tuxtype on a system with a German locale, lessons can't be
 opened.

I can confirm this, but I think this might be an upstream problem:

$ find /usr/share/tuxtype/themes/ -name *lesson* 
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_37.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_15.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_04.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_16.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_20.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_23.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_21.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_39.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_12.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_42.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_30.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_18.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_35.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_17.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_24.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_13.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_27.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_08.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_09.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_40.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_41.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_22.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_36.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_29.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_05.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_06.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_03.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_19.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_14.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_02.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_32.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_11.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_01.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_34.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_38.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_28.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_07.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_25.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_43.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_10.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_26.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_33.xml
/usr/share/tuxtype/themes/greek/scripts/basic_lesson_31.xml


cheers,
Holger


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

Bug#758782: tiger: TigerCron should randomize start time

2014-08-21 Thread Ludovic Pouzenc

Package: tiger
Version: 1:3.2.3-10
Severity: wishlist

Dear Maintainer,

In virtualized environnements, tiger could cause I/O storms. An example of bad
situation :

tiger with default conf on 15 VM in a same KVM host.
The first August at 2:00 AM , all VM + the host starts find_files check.
IO load gets very high at 02:01 and other services are impacted.

I think we could imitate apt cron behavior to randomize start time, adjusting
the minute part only. Basicaly they use a sleep $(random 1800).

I this could be done only by altering the tigercron script and adding a
function like the apt one :

From wheezy default /etc/cron.daily/apt :
# sleep for a random interval of time (default 30min)
# (some code taken from cron-apt, thanks)
random_sleep()
{
RandomSleep=1800
eval $(apt-config shell RandomSleep APT::Periodic::RandomSleep)
if [ $RandomSleep -eq 0 ]; then
return
fi
if [ -z $RANDOM ] ; then
# A fix for shells that do not have this bash feature.
RANDOM=$(dd if=/dev/urandom count=1 2 /dev/null | cksum | cut -c1-5)
fi
TIME=$(($RANDOM % $RandomSleep))
debug_echo sleeping for $TIME seconds
sleep $TIME
}

Maybe this introduce some dependancies like coreutils (but seems a common
case).

Regards,
Ludovic



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

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

Versions of packages tiger depends on:
ii  binutils   2.22-8
ii  bsdmainutils   9.0.3
ii  debconf [debconf-2.0]  1.5.49
ii  libc6  2.13-38+deb7u3
ii  net-tools  1.60-24.2
ii  ucf3.0025+nmu3

Versions of packages tiger recommends:
ii  chkrootkit 0.49-4.1+deb7u2
ii  exim4-daemon-light [mail-transport-agent]  4.80-7
ii  john   1.7.8-1
ii  tripwire   2.4.2.2-2

Versions of packages tiger suggests:
ii  lsof  4.86+dfsg-1

-- debconf information:
  tiger/mail_rcpt: root
  tiger/policy_adapt:


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735832: (no subject)

2014-08-21 Thread Erwan Prioul


Hi,

I've collected and tested the patch applied by Ubuntu.
It could be useful in the meantime the package will be updated with the 
upstream version.


Erwan.
diff -Naur a/debian/patches/01_editor.dpatch b/debian/patches/01_editor.dpatch
--- a/debian/patches/01_editor.dpatch	2014-08-21 11:18:05.109832955 +0200
+++ b/debian/patches/01_editor.dpatch	2014-08-21 11:29:41.145795962 +0200
@@ -10,7 +10,7 @@
 +++ wyrd-1.4.1/wyrdrc	2006-11-27 11:42:35.0 +0100
 @@ -5,11 +5,11 @@
  # the default reminder file to display
- set reminders_file=~/.reminders
+ set reminders_file=$HOME/.reminders
  # command for editing an old appointment, given a line number %line% and filename %file%
 -set edit_old_command=$EDITOR +%line% %file%
 +set edit_old_command=${VISUAL:-$EDITOR} +%line% %file%
diff -Naur a/debian/patches/02_fix-ftbfs-ocaml-4.patch b/debian/patches/02_fix-ftbfs-ocaml-4.patch
--- a/debian/patches/02_fix-ftbfs-ocaml-4.patch	1970-01-01 01:00:00.0 +0100
+++ b/debian/patches/02_fix-ftbfs-ocaml-4.patch	2014-08-21 11:39:19.529765221 +0200
@@ -0,0 +1,36 @@
+From: Paul Pelzl
+Subject: fix 'configure' test which incorrectly rejected OCaml 4 
+ .
+ Patch not needed for wyrd = 1.4.6
+ .
+Origin: upstream, http://bazaar.launchpad.net/~pelzlpj/wyrd/wyrd-dev/revision/304
+Bug-Ubuntu: https://launchpad.net/bugs/1281275
+Bug-Debian: http://bugs.debian.org/735832
+
+---
+ configure|2 +-
+ configure.in |2 +-
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+--- a/configure.in
 b/configure.in
+@@ -63,7 +63,7 @@
+ OCAMLMINORVERSION=`echo $OCAMLVERSION | cut -d '.' -f 2`
+ if test $OCAMLMAJORVERSION -lt 3 ; then
+AC_MSG_ERROR(Wyrd requires OCaml version 3.08 or greater.)
+-else
++elif test $OCAMLMAJORVERSION -eq 3; then
+if test $OCAMLMINORVERSION -lt 8 ; then
+   AC_MSG_ERROR(Wyrd requires OCaml version 3.08 or greater.)
+fi
+--- a/configure
 b/configure
+@@ -1724,7 +1724,7 @@
+{ { echo $as_me:$LINENO: error: Wyrd requires OCaml version 3.08 or greater. 5
+ echo $as_me: error: Wyrd requires OCaml version 3.08 or greater. 2;}
+{ (exit 1); exit 1; }; }
+-else
++elif test $OCAMLMAJORVERSION -eq 3; then
+if test $OCAMLMINORVERSION -lt 8 ; then
+   { { echo $as_me:$LINENO: error: Wyrd requires OCaml version 3.08 or greater. 5
+ echo $as_me: error: Wyrd requires OCaml version 3.08 or greater. 2;}
diff -Naur a/debian/patches/series b/debian/patches/series
--- a/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ b/debian/patches/series	2014-08-21 11:20:54.249823966 +0200
@@ -0,0 +1,2 @@
+01_editor.dpatch
+02_fix-ftbfs-ocaml-4.patch
diff -Naur a/debian/rules b/debian/rules
--- a/debian/rules	2014-08-21 11:18:05.105832956 +0200
+++ b/debian/rules	2014-08-21 11:19:09.873829513 +0200
@@ -2,7 +2,6 @@
 
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/autotools.mk
-include /usr/share/cdbs/1/rules/dpatch.mk
 
 DEB_CONFIGURE_EXTRA_FLAGS = --enable-utf8
 
diff -Naur a/debian/source/format b/debian/source/format
--- a/debian/source/format	1970-01-01 01:00:00.0 +0100
+++ b/debian/source/format	2014-08-21 11:21:50.185820993 +0200
@@ -0,0 +1 @@
+3.0 (quilt)

Bug#758778: dpkg-maintscript-helper: error: original symlink target is not an absolute path

2014-08-21 Thread Andreas Cadhalpun


Control: affects -1 lilypond

Hi,

On 21.08.2014 11:50, Guillem Jover wrote:

This and any other such package (although we did a quick check over
codesearch.d.o, but I guess missed this one due to the line breaks)
were broken already, and not performing the symlink to dir switch
anyway because the code is checking if the parameter matches the
canonicalized form («readlink -f»), which it will not.

This can make dpkg lose track, remove or overwrite unintended file,
as they might end up installed in a (real) path that does not match
with the one listed in the package metadata.

I think that for this reason dpkg needs to make those break explicitly,
and that having such version in testing is more valuable than trying to
avoid those packages to explicitly break, instead of allowing the
possibly silent breakage.


Thanks for the detailed explanation. :)


I'm thus probably just going to either close or reassign this bug
report to the affected package(s).


On 21.08.2014 12:01, Guillem Jover wrote:
 The only other affected package is lilypond. I'll check the actual
 effect from dir_to_symlink too, cook a list and send to debian-devel@.
 And file some RC bugs at the same time.

I also couldn't find more affected packages. It should be possible to 
fix these two before dpkg migrates to testing in 9 days.


Best regards,
Andreas


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758783: julia: does not start with -p option specified

2014-08-21 Thread Frederik Beaujean

Package: julia
Version: 0.2.1+dfsg-3
Severity: normal

Dear Maintainer,

I wanted to try the parallel capabilities of julia. Following the manual, I 
tried to start it up as
$ julia -p 2
Master process (id 1) could not connect within 60.0 seconds.
exiting.
Master process (id 1) could not connect within 60.0 seconds.
exiting.

Master process (id 1) could not connect within 60.0 seconds.
exiting.
Master process (id 1) could not connect within 60.0 seconds.
exiting.
^C

The same happens even with one process
$ julia -p 1
Master process (id 1) could not connect within 60.0 seconds.
exiting.
Master process (id 1) could not connect within 60.0 seconds.
exiting.
Master process (id 1) could not connect within 60.0 seconds.
exiting.
^C

and I never get to do anything.

To start julia at all, I had to use julia -f due to this outstanding bug #755576

bye

Fred

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

Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages julia depends on:
ii  libamd2.3.11:4.2.1-3
ii  libarpack2 3.1.5-3
ii  libblas3 [libblas.so.3]1.2.20110419-7
ii  libc6  2.19-7
ii  libcamd2.3.1   1:4.2.1-3
ii  libcholmod2.1.21:4.2.1-3
ii  libcolamd2.8.0 1:4.2.1-3
ii  libdouble-conversion1  2.0.1-1
ii  libffi63.1-2
ii  libfftw3-double3   3.3.4-1
ii  libfftw3-single3   3.3.4-1
ii  libgcc11:4.9.1-4
ii  libgfortran3   4.9.1-4
ii  libgmp10   2:6.0.0+dfsg-4
ii  liblapack3 [liblapack.so.3]3.5.0-3
ii  libllvm3.3 1:3.3-16
ii  libmpfr4   3.1.2-1
ii  libncurses55.9+20140712-2
ii  libopenblas-base [liblapack.so.3]  0.2.10-2
ii  libpcre3   1:8.35-3
ii  libquadmath0   4.9.1-4
ii  libreadline6   6.3-8
ii  libspqr1.3.1   1:4.2.1-3
ii  libstdc++6 4.9.1-4
ii  libtinfo5  5.9+20140712-2
ii  libumfpack5.6.21:4.2.1-3
ii  libunwind8 1.1-3
ii  multiarch-support  2.19-7

Versions of packages julia recommends:
ii  git  1:2.1.0~rc1-1

Versions of packages julia suggests:
pn  essnone
ii  julia-doc  0.2.1+dfsg-3

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758392: systemd: Assertion caused by journalctl --listboots

forwarded 758392 https://bugs.freedesktop.org/show_bug.cgi?id=82894
thanks

Am 21.08.2014 09:35, schrieb Chris Tillman:
 Filed upstream bug 82894.
 

Thanks, Chris,


-- 
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#758778: dpkg-maintscript-helper: error: original symlink target is not an absolute path

2014-08-21 Thread Andreas Cadhalpun


Control: affects -1 imagemagick

Hi,

On 21.08.2014 12:01, Guillem Jover wrote:

The only other affected package is lilypond. I'll check the actual
effect from dir_to_symlink too, cook a list and send to debian-devel@.
And file some RC bugs at the same time.


There is also imagemagick-doc 8:6.8.9.6-2 in experimental, which fails 
to install [1][2].


Best regards,
Andreas


1: 
https://anonscm.debian.org/cgit/collab-maint/imagemagick.git/tree/debian/imagemagick-doc.postinst?h=debian/6.8.9.6-2

2: https://bugs.debian.org/758760


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758784: base: kernel BUG in vmwgfx_drv.c:903!

2014-08-21 Thread Oleg Buklanov

Package: base
Severity: important
Tags:



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

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

System crashes when any program is trying to access multiple files in
/dev/char folder.
It may happen during parallel backup or anti-virus scan of entire file system
Here is the script which can be used to reproduce the problem on ESXi
4.1.0 platform:
--- cut here 
#!/bin/sh
cd /dev/char
for i in `ls`
do
   wc $i 
done
 end 
or
wc /dev/226:0 
wc /dev/226:64 

NOTE: files must be opened simultaniously. In certain cases system
freezes, in other - remains live. Syslog contains the following
information:
NOTE2: This bug was reproduced on freshly installed system without any
third party software (vmware-tools wasn't installed either)

Aug 20 17:37:11 debian7p5-32 kernel: [  732.170152] [drm] width 640
Aug 20 17:37:11 debian7p5-32 kernel: [  732.170156] [drm] height 480
Aug 20 17:37:11 debian7p5-32 kernel: [  732.170158] [drm] bpp 32
Aug 20 17:37:11 debian7p5-32 kernel: [  732.172975] [drm] Fifo max
0x0004 min 0x1000 cap 0x007f
Aug 20 17:37:11 debian7p5-32 kernel: [  732.183717] PM: Marking nosave
pages: 0009f000 - 0010
Aug 20 17:37:11 debian7p5-32 kernel: [  732.183720] PM: Basic memory
bitmaps created
Aug 20 17:37:11 debian7p5-32 kernel: [  737.986119] PM: Basic memory
bitmaps freed
Aug 20 17:37:11 debian7p5-32 kernel: [  738.045046] [ cut
here ]
Aug 20 17:37:11 debian7p5-32 kernel: [  738.045230] kernel BUG at
/build/linux-xMFgY8/linux-3.2.57/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:903!
Aug 20 17:37:11 debian7p5-32 kernel: [  738.045423] invalid opcode:
 [#1] SMP
Aug 20 17:37:11 debian7p5-32 kernel: [  738.045569] Modules linked in:
nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop snd_pcm vmwgfx
snd_page_alloc ttm snd_timer snd soundcore parport_pc parport coretemp
vmw_balloon drm processor crc32c_intel thermal_sys psmouse ac evdev
pcspkr serio_raw i2c_piix4 power_supply i2c_core shpchp container
button ext4 crc16 jbd2 mbcache sr_mod cdrom sg ata_generic sd_mod
crc_t10dif floppy pcnet32 mii ata_piix mptspi scsi_transport_spi
mptscsih mptbase libata scsi_mod [last unloaded: scsi_wait_scan]
Aug 20 17:37:11 debian7p5-32 kernel: [  738.047473]
Aug 20 17:37:11 debian7p5-32 kernel: [  738.047557] Pid: 2617, comm:
wc Not tainted 3.2.0-4-686-pae #1 Debian 3.2.57-3+deb7u2 VMware, Inc.
VMware Virtual Platform/440BX Desktop Reference Platform
Aug 20 17:37:11 debian7p5-32 kernel: [  738.047944] EIP:
0060:[f849603b] EFLAGS: 00010287 CPU: 0
Aug 20 17:37:11 debian7p5-32 kernel: [  738.048116] EIP is at
vmw_master_set+0x81/0x150 [vmwgfx]
Aug 20 17:37:11 debian7p5-32 kernel: [  738.048252] EAX: f75526c0 EBX:
f754 ECX: 10d1 EDX: 10d1
Aug 20 17:37:11 debian7p5-32 kernel: [  738.048397] ESI: f70c36c0 EDI:
f7540420 EBP: f77b4a40 ESP: f73f5de8
Aug 20 17:37:11 debian7p5-32 kernel: [  738.048542]  DS: 007b ES: 007b
FS: 00d8 GS: 00e0 SS: 0068
Aug 20 17:37:11 debian7p5-32 kernel: [  738.048679] Process wc (pid:
2617, ti=f73f4000 task=f73a49e0 task.ti=f73f4000)
Aug 20 17:37:11 debian7p5-32 kernel: [  738.048893] Stack:
Aug 20 17:37:11 debian7p5-32 kernel: [  738.048997]  f7071f80 f77b4940
0102a33d f7253c00 f77b4a40 f7253c14 f8495fba f842e5cf
Aug 20 17:37:11 debian7p5-32 kernel: [  738.049419]  f77b4a54 f72054f8
f71ce800 f72eac00 f843db84 f71ce800 f72054f8 ffed
Aug 20 17:37:11 debian7p5-32 kernel: [  738.049845]  f842eda8 f7253c00
f72054f8 f750dd40 f71ce800  c10d03e3 
Aug 20 17:37:11 debian7p5-32 kernel: [  738.050267] Call Trace:
Aug 20 17:37:11 debian7p5-32 kernel: [  738.050380]  [f8495fba] ?
vmw_master_drop+0xec/0xec [vmwgfx]
Aug 20 17:37:11 debian7p5-32 kernel: [  738.050652]  [f842e5cf] ?
drm_open+0x22d/0x483 [drm]
Aug 20 17:37:11 debian7p5-32 kernel: [  738.050791]  [f842eda8] ?
drm_stub_open+0xbf/0x107 [drm]
Aug 20 17:37:11 debian7p5-32 kernel: [  738.050935]  [c10d03e3] ?
chrdev_open+0xf3/0x111
Aug 20 17:37:11 debian7p5-32 kernel: [  738.051067]  [c10cc0b7] ?
__dentry_open+0x186/0x25f
Aug 20 17:37:11 debian7p5-32 kernel: [  738.051201]  [c10cce05] ?
nameidata_to_filp+0x3a/0x45
Aug 20 17:37:11 debian7p5-32 kernel: [  738.051336]  [c10d02f0] ?
cdev_put+0x17/0x17
Aug 20 17:37:11 debian7p5-32 kernel: [  738.051467]  [c10d6ec5] ?
do_last+0x4f8/0x513
Aug 20 17:37:11 debian7p5-32 kernel: [  738.051596]  [c10d731c] ?
path_openat+0x236/0x28b
Aug 20 17:37:11 debian7p5-32 kernel: [  738.051729]  [c10d741a] ?
do_filp_open+0x23/0x5c
Aug 20 17:37:11 debian7p5-32 kernel: [  738.051862]  [c102a33d] ?
should_resched+0x5/0x1e
Aug 20 17:37:11 debian7p5-32 kernel: [  738.051995]  [c12c360a] ?
_cond_resched+0x5/0x18
Aug 20 17:37:11 debian7p5-32 kernel: [  738.052127]  [c10cce64] ?

Bug#758785: python-babel: Broken dir_to_symlink handling

Source: python-babel
Source-Version: 1.3+dfsg.1-4
Severity: important

Hi!

This package has an old and broken embedded copy of the
dpkg-maintscript-helper dir_to_symlink implementation which had
several issues, among others not handling correctly relative symlink
targets passed as arguments, which the code here is doing.

Please do not embed such code, as the purpose of that tools is
precisely to have centralized code fixes, which is the problem it's
trying to solve and embedding defies that as exemplified here.

If you'd insist on still embedded its code, I'd request that you keep
track of any further changes to the program, and that you always try
to use the native command and only if not available fallback to
whatever local implementation you want to ship.

Thanks,
Guillem


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758760: dpkg-maintscript-helper: error: original symlink target is not an absolute path

Control: severity -1 serious
Control: found -1 8:6.8.8.2-1

On Thu, 2014-08-21 at 07:59:40 +0800, 積丹尼 Dan Jacobson wrote:
 Package: imagemagick-doc
 
 Preparing to unpack .../imagemagick-doc_8%3a6.8.9.6-2_all.deb ...
 dpkg-maintscript-helper: error: original symlink target is not an absolute 
 path
 dpkg: error processing archive 
 /var/cache/apt/archives/imagemagick-doc_8%3a6.8.9.6-2_all.deb (--unpack):
  subprocess new pre-installation script returned error exit status 1
 dpkg-maintscript-helper: error: original symlink target is not an absolute 
 path
 dpkg: error while cleaning up:
  subprocess new post-removal script returned error exit status 1

This makes the package uninstallable/removable, bumping severity.

Thanks,
Guillem


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758786: Dissy has been replaced by a complete re-implementation called EmilPRO

2014-08-21 Thread Henri Salo

Package: dissy
Version: 9-3.1
Severity: normal

After discussion with upstream he added this text to page
https://code.google.com/p/dissy/

Note! Dissy has been replaced by a complete re-implementation called EmilPRO,
which has many improvements over Dissy. More information about EmilPRO can be
found at emilpro.com and source code is at github.com/SimonKagstrom/emilpro.
I've therefore deprecated Dissy, so you should really take a look at EmilPRO
instead!

Debian package name should be changed according to policy, which is currently
unkown to me. In case you need more information how do change it you can contact
me and I'll find out more details.

---
Henri Salo


signature.asc
Description: Digital signature

Bug#745904: rsyslogd-2068: could not load module '/usr/lib/rsyslog/lmnsd_gtls.so', rsyslog error -2078

Am 21.08.2014 10:28, schrieb Edy Corak:
 I have now found the problem. Sorry, that was my mistake.
 
 The certificate has been updated and because the server was not rebooted long 
 time, I got the error not noticed.
 After a reboot, just this error message appears in the log files.
 Perhaps it is possible to specify the error message, so that the error is 
 easier to see ?

Have you also tried to run it in debug mode (-d)?
If you also didn't get a proper error message this way, please file a
bug upstream [1] and report back with the bug number.


Michael


[1] http://bugzilla.adiscon.com/
-- 
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#758787: lilypond-doc: Broken usage of dpkg-maintscript-helper

Package: lilypond-doc
Version: 2.18.0-1
Severity: serious

Hi!

The dpkg-maintscript-helper usage in this package is broken, because
it's using a relative symlink target. The dpkg-maintscript-helper has
been doing sanity checks to see if the canonicalized symlink targe
(from «readlink -f») matches the passed symlink target argument, which
will just not match, and not perform the switch.

Starting with dpkg 1.17.13 the program will error out on such
parameters (the documentation has been updated too now), so the package
becomes uninstallable/unremovable. Please switch to use an absolute
path for the symlink target.

Thanks,
Guillem


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758780: tuxtype: Can't open lessons when using German locale

2014-08-21 Thread Ronny Standtke

Hi Holger

 this version doenst exist, am I right to assume you are using a local
 backport? 

Yes, that's true, I created a local backport.

Cheers

Ronny


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758788: cryptsetup: Passphrase caching broken in decrypt_keyctl

2014-08-21 Thread Marek Królikowski

Package: cryptsetup
Version: 2:1.6.6-1
Severity: normal

Dear Maintainer,
after upgrade to 2:1.6.6-1 I have to enter passphrase for each of crypttab 
entries. 
Desired behavior is for cryptsetup to try cached passphrase for crypptab 
entries with
the same identifier (pw1 in this case).

Working configurations:
- cryptsetup 2:1.6.4-4
- cryptsetup 2:1.6.6-1 with decrypt_keyctl copied from 2:1.6.4-4


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.16-trunk-amd64 root=/dev/mapper/debian-system ro quiet

-- /etc/crypttab
sdaX_crypt UUID=redacted pw1 luks,keyscript=decrypt_keyctl
sdbX_crypt UUID=redacted pw1 luks,discard,keyscript=decrypt_keyctl

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (995, 'unstable'), (991, 'experimental'), (101, 'testing'), (100, 
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-trunk-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

Versions of packages cryptsetup depends on:
ii  cryptsetup-bin 2:1.6.6-1
ii  debconf [debconf-2.0]  1.5.53
ii  dmsetup2:1.02.88-1
ii  libc6  2.19-9

Versions of packages cryptsetup recommends:
ii  busybox 1:1.22.0-8
ii  console-setup   1.111
ii  initramfs-tools [linux-initramfs-tool]  0.115
ii  kbd 1.15.5-1

Versions of packages cryptsetup suggests:
ii  dosfstools  3.0.26-3
ii  keyutils1.5.9-5
ii  liblocale-gettext-perl  1.05-8+b1

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758789: bareftp: Fix FTBFS on ppc64el

2014-08-21 Thread Frederic Bonnard

Package: src:bareftp
Version: 0.3.9-1
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el

Dear Maintainer,
here is a patch from Ubuntu to fix FTBFS on ppc64el,
thank you,

Fred


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

Kernel: Linux 3.2.0-4-686-pae (SMP w/8 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/dash
--- a/debian/patches/ppc64el.fix	1969-12-31 21:00:00.0 -0300
+++ b/debian/patches/ppc64el.fix	2014-08-21 08:30:22.0 -0300
@@ -0,0 +1,55 @@
+Patch libtool.m4 and configure to build on ppc64el.
+Matthias Klose d...@ubuntu.com Sat, 18 Jan 2014 14:24:49 +0100
+
+--- bareftp-0.3.9.orig/configure
 bareftp-0.3.9/configure
+@@ -8539,7 +8539,10 @@ s390*-*linux*|s390*-*tpf*|sparc*-*linux*
+ 	  x86_64-*linux*)
+ 	LD=${LD-ld} -m elf_i386
+ 	;;
+-	  ppc64-*linux*|powerpc64-*linux*)
++	  powerpc64le-*)
++	LD=${LD-ld} -m elf32lppclinux
++	;;
++	  powerpc64-*)
+ 	LD=${LD-ld} -m elf32ppclinux
+ 	;;
+ 	  s390x-*linux*)
+@@ -8558,7 +8561,10 @@ s390*-*linux*|s390*-*tpf*|sparc*-*linux*
+ 	  x86_64-*linux*)
+ 	LD=${LD-ld} -m elf_x86_64
+ 	;;
+-	  ppc*-*linux*|powerpc*-*linux*)
++	  powerpcle-*)
++	LD=${LD-ld} -m elf64lppc
++	;;
++	  powerpc-*)
+ 	LD=${LD-ld} -m elf64ppc
+ 	;;
+ 	  s390*-*linux*|s390*-*tpf*)
+--- bareftp-0.3.9.orig/m4/shamrock/libtool.m4
 bareftp-0.3.9/m4/shamrock/libtool.m4
+@@ -1282,7 +1282,10 @@ s390*-*linux*|s390*-*tpf*|sparc*-*linux*
+ 	  x86_64-*linux*)
+ 	LD=${LD-ld} -m elf_i386
+ 	;;
+-	  ppc64-*linux*|powerpc64-*linux*)
++	  powerpc64le-*)
++	LD=${LD-ld} -m elf32lppclinux
++	;;
++	  powerpc64-*)
+ 	LD=${LD-ld} -m elf32ppclinux
+ 	;;
+ 	  s390x-*linux*)
+@@ -1301,7 +1304,10 @@ s390*-*linux*|s390*-*tpf*|sparc*-*linux*
+ 	  x86_64-*linux*)
+ 	LD=${LD-ld} -m elf_x86_64
+ 	;;
+-	  ppc*-*linux*|powerpc*-*linux*)
++	  powerpcle-*)
++	LD=${LD-ld} -m elf64lppc
++	;;
++	  powerpc-*)
+ 	LD=${LD-ld} -m elf64ppc
+ 	;;
+ 	  s390*-*linux*|s390*-*tpf*)
--- a/debian/patches/series	1969-12-31 21:00:00.0 -0300
+++ b/debian/patches/series	2014-08-21 06:18:04.0 -0300
@@ -0,0 +1 @@
+ppc64el.fix

Bug#758715: RFS: bgfinancas/2.0-1 [ITP]‏

2014-08-21 Thread José Robson Mariano Alves


 I think it would be best to just use the user's locale to decide which
 language to display.

Hi Paul, the user decide is better, because some users have systems in English 
and prefer the Portuguese language, or otherwise.
I have friends who think this way.
Example: people learning new languages.

Bug#758790: icinga2: [INTL:ru] Russian debconf templates translation

2014-08-21 Thread Yuri Kozlov

Package: icinga2
Version: 2.0.1-2
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

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

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

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

Russian debconf templates translation is attached.

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

Kernel: Linux 3.14-1-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


ru.po.gz
Description: application/gzip

Bug#758791: italc: [INTL:ru] Russian debconf templates translation update

2014-08-21 Thread Yuri Kozlov

Package: italc
Version: 1:2.0.2+dfsg1-1
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

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

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

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

Russian debconf templates translation update is attached.

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

Kernel: Linux 3.14-1-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


ru.po.gz
Description: application/gzip

Bug#758760: [Pkg-gmagick-im-team] Bug#758760: dpkg-maintscript-helper: error: original symlink target is not an absolute path

2014-08-21 Thread roucaries bastien

control: tags -1 + pending
control: clone -1 -2
control: reassign -2 dpkg
control: severity -2 wishlist
control: retitle dpkg-maint-helper should document that
dpkg-maintscript-helper symlink_to_dir pathname are canonical path

Hi,

Pending for imagemagick. However could we document that
dpkg-maintscript-helper symlink_to_dir pathname are canonical path ?

Thanks

On Thu, Aug 21, 2014 at 12:58 PM, Guillem Jover guil...@debian.org wrote:
 Control: severity -1 serious
 Control: found -1 8:6.8.8.2-1

 On Thu, 2014-08-21 at 07:59:40 +0800, 積丹尼 Dan Jacobson wrote:
 Package: imagemagick-doc

 Preparing to unpack .../imagemagick-doc_8%3a6.8.9.6-2_all.deb ...
 dpkg-maintscript-helper: error: original symlink target is not an absolute 
 path
 dpkg: error processing archive 
 /var/cache/apt/archives/imagemagick-doc_8%3a6.8.9.6-2_all.deb (--unpack):
  subprocess new pre-installation script returned error exit status 1
 dpkg-maintscript-helper: error: original symlink target is not an absolute 
 path
 dpkg: error while cleaning up:
  subprocess new post-removal script returned error exit status 1

 This makes the package uninstallable/removable, bumping severity.

 Thanks,
 Guillem

 ___
 Pkg-gmagick-im-team mailing list
 pkg-gmagick-im-t...@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gmagick-im-team


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#752717: hardening-wrapper: disable standard hardening flags for test suite

2014-08-21 Thread Aurelien Jarno

On Mon, Aug 11, 2014 at 11:01:32AM +0200, Romain Francoise wrote:
 severity serious
 quit
 
 dpkg 1.17.11 now emits -fstack-protector-strong by default, which makes
 the package FTBFS because of this bug. Raising severity.

I have just done an NMU to fix this RC bug. Please find the patch
attached.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru hardening-wrapper-2.5/debian/changelog hardening-wrapper-2.5+nmu1/debian/changelog
--- hardening-wrapper-2.5/debian/changelog	2013-12-17 19:14:59.0 +0100
+++ hardening-wrapper-2.5+nmu1/debian/changelog	2014-08-21 13:54:44.0 +0200
@@ -1,3 +1,12 @@
+hardening-wrapper (2.5+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable standard hardening flags for test suite, to avoid conflicting
+with hardening-wrapper's own flags which are being tested. Thanks to
+Romain Francoise for the patch (Closes: 752717).
+
+ -- Aurelien Jarno aure...@debian.org  Thu, 21 Aug 2014 13:50:24 +0200
+
 hardening-wrapper (2.5) unstable; urgency=low
 
   * hardened-ld: detect symlink loops, like done for hardened-cc already
diff -Nru hardening-wrapper-2.5/debian/rules hardening-wrapper-2.5+nmu1/debian/rules
--- hardening-wrapper-2.5/debian/rules	2012-03-31 22:46:15.0 +0200
+++ hardening-wrapper-2.5+nmu1/debian/rules	2014-08-21 13:48:21.0 +0200
@@ -1,3 +1,6 @@
 #!/usr/bin/make -f
+
+export DEB_BUILD_MAINT_OPTIONS=hardening=-all
+
 %:
 	dh $@

Bug#758770: ERROR: x-face-el is broken - called emacs-package-remove as a new-style add-on, but has no compat file.

2014-08-21 Thread Tatsuya Kinoshita

Control: severity -1 minor
Control: found -1 1.3.6.24-13
Control: notfound -1 1.3.6.24-14
Control: close -1 1.3.6.24-14

On August 21, 2014 at 12:50PM +0800, jidanni (at jidanni.org) wrote:
 Preparing to unpack .../x-face-el_1.3.6.24-14_all.deb ...
 ERROR: x-face-el is broken - called emacs-package-remove as a new-style 
 add-on, but has no compat file.

This ERROR is caused when removing x-face-el 1.3.6.24-13, and
fixed in 1.3.6.24-14.

BTW, this ERROR is just warning and you can ignore this, because
the install/remove scripts of x-face-el are compatible with both
old-style and new-style.

Thanks,
-- 
Tatsuya Kinoshita


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758580: luabind: diff for patch to version 0.9.1+dfsg-9.1

2014-08-21 Thread Andreas Grob

tags 758580 + patch

Dear maintainer,

I have prepared a patch for luabind (versioned as 0.9.1+dfsg-9.1).
I created this patch hoping it might be helpful, should you decide
to implement the contained changes.

Kind Regards,
Andreas Grob
diff -Nru luabind-0.9.1+dfsg/debian/changelog luabind-0.9.1+dfsg/debian/changelog
--- luabind-0.9.1+dfsg/debian/changelog	2014-08-10 01:03:42.0 +0200
+++ luabind-0.9.1+dfsg/debian/changelog	2014-08-20 09:08:22.0 +0200
@@ -1,3 +1,10 @@
+luabind (0.9.1+dfsg-9.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * Fix dereference of null pointer in adopt_policy.hpp (Closes: #758580)
+
+ -- Andreas Grob vilar...@illarion.org  Wed, 20 Aug 2014 09:05:11 +0200
+
 luabind (0.9.1+dfsg-9) unstable; urgency=low
 
   * Change Build-Depends from libboost1.54-all-dev | libboost1.55-all-dev |
diff -Nru luabind-0.9.1+dfsg/debian/patches/11_fix_null_pointer_dereference.patch luabind-0.9.1+dfsg/debian/patches/11_fix_null_pointer_dereference.patch
--- luabind-0.9.1+dfsg/debian/patches/11_fix_null_pointer_dereference.patch	1970-01-01 01:00:00.0 +0100
+++ luabind-0.9.1+dfsg/debian/patches/11_fix_null_pointer_dereference.patch	2014-08-20 08:49:42.0 +0200
@@ -0,0 +1,18 @@
+Description: Fix null pointer dereference in adopt_policy.hpp
+Author: Andreas Grob vilar...@illarion.org
+Bug-Debian: http://bugs.debian.org/758580
+--- a/luabind/adopt_policy.hpp
 b/luabind/adopt_policy.hpp
+@@ -65,7 +65,11 @@
+ 
+ object_rep* obj = static_castobject_rep*(
+ lua_touserdata(L, index));
+-obj-release();
++
++if (obj)
++{
++obj-release();
++}
+ 
+ adjust_backref_ownership(ptr, boost::is_polymorphicT());
+ 
diff -Nru luabind-0.9.1+dfsg/debian/patches/series luabind-0.9.1+dfsg/debian/patches/series
--- luabind-0.9.1+dfsg/debian/patches/series	2014-08-10 01:03:42.0 +0200
+++ luabind-0.9.1+dfsg/debian/patches/series	2014-08-20 08:39:19.0 +0200
@@ -8,3 +8,4 @@
 08_support_for_Lua_5.2.patch
 09_build_system_support_for_Lua_5.2.patch
 10_remove_refs_to_remote_images.patch
+11_fix_null_pointer_dereference.patch

Bug#750212: Bug#757818: partman-lvm: Refuses to reinstall if it find old lvm volume

2014-08-21 Thread Gabriele Giacone

On Mon, Aug 11, 2014 at 05:39:43PM +0200, Petter Reinholdtsen wrote:
 Package: partman-lvm
 Version: 91
 
 After the parted API change and fixes, I ran into a new problem when
 testing Debian Edu based on Jessie.  The installation hang and the log
 report that something is waiting on a prompt.  I normally test in a
 virtual machine, and reuse the hard drive every time.  After
 URL: https://bugs.debian.org/757417  and related bugs were fixed in
 partman, reinstallation hang.  These are the last few messages in the
 syslog before the hang:
[...]
 Aug 11 15:01:10 partman-lvm: WARNING: swap signature detected on 
 /dev/vg_system/swap_1. Wipe it? [y/n]
 
 Checking ps show that lvcreate is hanging, with a call looklike like
 this: lvcreate -l 255 -n swap_1 vg_system from partman-lvm.
 
 Looking in the partman-lvm source, I find the code in
 URL:http://sources.debian.net/src/partman-lvm/91/lib/lvm-base.sh/?hl=480#L480,
 which I suspect is the cause of this hang:
[...] 
   log-output -t partman-lvm lvcreate -l $extents -n $lv $vg
[...]
 
 Could the old behaviour where reinstallation work be reintroduced?

Same problem with xen-tools and fai-setup-storage (CC'ing bugs).

lvm2 2.02.105 introduces --wipesignatures option, so another option
along with --yes missing in wheezy.
  https://git.fedorahosted.org/cgit/lvm2.git/tree/WHATS_NEW?id=v2_02_109#n262

man lvcreate says that if not specified, signature wiping is done each
time zeroing is done, and given zeroing is enabled by default, shouldn't
it wipe signatures by default? I didn't test it.

 -W, --wipesignatures {y|n}
   Controls  wiping of detected signatures on newly created Logical Volume.
   If this option is not specified, then by default signature wiping is
   done each time the zeroing (-Z/--zero) is done. This default behaviour
   can be  controlled  by  allocation/wipe_signatures_when_zeroing_new_lvs
   setting found in lvm.conf(5).
   If  blkid  wiping is used (allocation/use_blkid_wiping setting in
   lvm.conf(5)) and LVM2 is compiled with blkid wiping support, then
   blkid(8) library is used to detect the signatures (use blkid -k command
   to list the signatures that are  recognized).   Otherwise, native LVM2
   code is used to detect signatures (MD RAID, swap and LUKS signatures are
   detected only in this case).  Logical Volume is not wiped if the read
   only flag is set.

 -Z, --zero {y|n}
Controls zeroing of the first 4KiB of data in the new logical volume.
Default is yes.
Volume will not be zeroed if the read only flag is set.
Snapshot volumes are zeroed always.

-- 
G..e


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758140: LedgerSMB 1.3.40-1 for Ubuntu

2014-08-21 Thread RJ Clay


Vladimir,


On 08/15/2014 06:02 AM, Robert J. Clay wrote:


On Thu, Aug 14, 2014 at 1:03 PM, Vladimir Botka vl...@netng.org wrote:

On Thu, 14 Aug 2014 08:55:18 -0400
RJ Clay j...@rocasa.us wrote:


On 08/06/2014 08:48 AM, RJ Clay wrote:

It also has already been sync'ed over to Ubuntu, and I'll be
working on backports there as well.

Back ported versions of 1.3.40 for Ubuntu v12.04 ('precise') and
v14.04 ('trusty') are now available from the LedgerSMB Launchpad PPA:
https://launchpad.net/~ledgersmb/+archive/ubuntu/main/+packages


thank you for the backport and for the heads-up. I've installed
LedgerSMB on 'trusty' and during the configuration steps (below) I've
landed with the error message:
database: ERROR: syntax error at or near # LINE 1: # Configure
ledgersmb user permissions


   Note that a bug has been raised in Debian regarding this issue, #758140.  There is also a 
related but more general bug in Debian (#698298)  and the corresponding bug for that in Ubuntu 
(#1078817, where it was originally raised).  All of these have to do with using dbconfig-common 
in the configuration step as part of the package installation;  that package has a lot of 
problems (which is why it experimently and is disabled by default)  and as we really only need 
to set up the LedgerSMB database administrative user, I will be working on an updated LSMB 
package that does not use dbconfig-common at all.




There are 4 options how to proceed: abort, retry, retry (skip
questions), ignore.

Would it be possible to help me to figure out how to proceed?


   As noted before;  abort out of that and redo that with the configuation step disabled. (If 
necessary, run 'dpkg-reconfigure ledgersmb'.)  Then set the password manually on the 'ledgersmb' 
admin user as necessary, as noted in the README.Debian file.






Robert James Clay
j...@rocasa.us


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#757265: Bug#758715: RFS: bgfinancas/2.0-1 [ITP]‏

2014-08-21 Thread José Robson Mariano Alves


 Your package and program are in Brazilian Portuguese.

Hi, i change my package to english.
The program is in English and Brazilian Portuguese.
I will add more languages in the future.

Regards,
José Robson Mariano Alves

Bug#756551: systemd-nspawn: Host and machine ids are equal - refusing to link journals

2014-08-21 Thread Major Hayden

No problems on an up to date jessie build.  Thanks Michael.

--
Major Hayden

On Aug 20, 2014, at 23:52, Michael Biebl bi...@debian.org wrote:

 I just tested this, and it worked perfectly for me:
 
 - Install jessie in a KVM based virtual machine using systemd 208-6 as init
 - mkdir /var/lib/container/  debootstrap jessie /var/lib/container/jessie
 - systemctl start systemd-nspawn@jessie.service
 
 = on the host system, the container journal ist properly linked into
 the host journal.
 
 Unless I hear back from you, I'm going to close this bug in a couple of
 days.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#749942: taskcoach: segfault on quit

2014-08-21 Thread Nicolas Boulenguez

Package: taskcoach
Version: 1.4.0-1
Followup-For: Bug #749942

The bug bites almost systematically on my machine, but neither in GDB
nor on upstream Debian test virtual machine.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735488: qt4-x11: Add arm64 support

2014-08-21 Thread Lisandro Damián Nicanor Pérez Meyer

On Wednesday 20 August 2014 22:57:31 Wookey wrote:
 +++ Lisandro Damián Nicanor Pérez Meyer [2014-08-16 12:02 -0300]:
[snip]
 The kernel calls it 'arm64' and so does Apple in their webkit patches,
 so we are not the only ones, but aarch64 is often used internally, as
 despite being a silly name is at least easily identiifed as unique.

That's excelent data, specially because I decided to go with all the patch 
(using both aarch64/arm64).

Thanks!


-- 
No es el crecimiento de la tecnología lo que excluye, sino la
protección sistemática de los derechos de uso de la misma,
lo cual se puede aplicar al arte.
  David Cuartielles

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#758793: base: Random lockups. Can only ALT+SYSRQ+REISUB to reboot

2014-08-21 Thread Demetris Demetriou

Package: base
Severity: important

Hello,

I've started getting random lockups while using XFCE, iceweasel, icedove. The
screen will freeze but the mouse cursor can be moved around,with no ability to
click anywhere.

Sometimes if I'm lucky I might be able to CTRL+ALT+F1 into a console and
manually restart lightdm. Everything is ok for a bit, then back to a random
lockup.

I can't find any error log entries, except these: (which are way too early in
the boot process)

Aug 21 15:15:17 kernel: [0.323186] Unpacking initramfs...
Aug 21 15:15:17 kernel: [1.201565] irq 9: nobody cared (try booting with
the irqpoll option)
Aug 21 15:15:17 kernel: [1.201628] CPU: 1 PID: 1 Comm: swapper/0 Not
tainted 3.14-2-amd64 #1 Debian 3.14.15-2
Aug 21 15:15:17 kernel: [1.201630] Hardware name: TOSHIBA Satellite
P300D/Satellite P300D, BIOS V3.30   09/23/2009
Aug 21 15:15:17 kernel: [1.201634]  8801310076c4 814c5732
880131007600 810b37f8
Aug 21 15:15:17 kernel: [1.201639]  880131007600 0009
 810b3d11
Aug 21 15:15:17 kernel: [1.201642]   
0009 
Aug 21 15:15:17 kernel: [1.201647] Call Trace:
Aug 21 15:15:17 kernel: [1.201649]  IRQ  [814c5732] ?
dump_stack+0x41/0x51
Aug 21 15:15:17 kernel: [1.201662]  [810b37f8] ?
__report_bad_irq+0x28/0xc0
Aug 21 15:15:17 kernel: [1.201666]  [810b3d11] ?
note_interrupt+0x241/0x290
Aug 21 15:15:17 kernel: [1.201670]  [810b1781] ?
handle_irq_event_percpu+0xc1/0x1b0
Aug 21 15:15:17 kernel: [1.201673]  [810b18a3] ?
handle_irq_event+0x33/0x50
Aug 21 15:15:17 kernel: [1.201677]  [810b4728] ?
handle_fasteoi_irq+0x58/0x100
Aug 21 15:15:17 kernel: [1.201684]  [81015a58] ?
handle_irq+0x18/0x30
Aug 21 15:15:17 kernel: [1.201688]  [81015374] ? do_IRQ+0x44/0xe0
Aug 21 15:15:17 kernel: [1.201692]  [814cb3ad] ?
common_interrupt+0x6d/0x6d
Aug 21 15:15:17 kernel: [1.201694]  EOI  [81297e16] ?
inflate_fast+0x106/0x610
Aug 21 15:15:17 kernel: [1.201702]  [81299709] ?
zlib_inflate+0x11e9/0x19c0
Aug 21 15:15:17 kernel: [1.201708]  [818d36fd] ?
write_buffer+0x1d/0x2b
Aug 21 15:15:17 kernel: [1.201712]  [818d370b] ?
write_buffer+0x2b/0x2b
Aug 21 15:15:17 kernel: [1.201717]  [8190632e] ?
bunzip2+0x3ff/0x3ff
Aug 21 15:15:17 kernel: [1.201720]  [8190657b] ?
gunzip+0x249/0x30e
Aug 21 15:15:17 kernel: [1.201724]  [818d39f9] ?
unpack_to_rootfs+0x149/0x26a
Aug 21 15:15:17 kernel: [1.201727]  [818d3676] ?
initrd_load+0x3a/0x3a
Aug 21 15:15:17 kernel: [1.201731]  [818d3e1f] ?
maybe_link.part.2+0xff/0xff
Aug 21 15:15:17 kernel: [1.201735]  [818d3e78] ?
populate_rootfs+0x59/0x10c
Aug 21 15:15:17 kernel: [1.201740]  [8100212a] ?
do_one_initcall+0xca/0x170
Aug 21 15:15:17 kernel: [1.201744]  [8107ede8] ?
parse_args+0x228/0x400
Aug 21 15:15:17 kernel: [1.201749]  [818d3066] ?
kernel_init_freeable+0x15f/0x1e1
Aug 21 15:15:17 kernel: [1.201753]  [818d28ac] ?
do_early_param+0x81/0x81
Aug 21 15:15:17 kernel: [1.201757]  [814b7e20] ?
rest_init+0x70/0x70
Aug 21 15:15:17 kernel: [1.201760]  [814b7e25] ?
kernel_init+0x5/0xf0
Aug 21 15:15:17 kernel: [1.201763]  [814d308c] ?
ret_from_fork+0x7c/0xb0
Aug 21 15:15:17 kernel: [1.201767]  [814b7e20] ?
rest_init+0x70/0x70
Aug 21 15:15:17 kernel: [1.201769] handlers:
Aug 21 15:15:17 kernel: [1.201822] [812ed2a8] acpi_irq
Aug 21 15:15:17 kernel: [1.201912] Disabling IRQ #9
Aug 21 15:15:17 kernel: [1.521932] Freeing initrd memory: 15860K
(8800360f6000 - 880037073000)


Running with irqpoll leads to a different error (IMHO unrelated). Running
acpi=off leads to no error during boot up but random lockups again.

Didn't know which package I should file this bug against, since I honestly
don't know what's causing it. The system doesn't give any other indication
through logs that something is wrong when it locks up.

It can happen right after logging in, while idling on desktop, or while under
load. Again, no indication as to what is causing it, since what causes one
lockup doesn't cause the next one.

Running Jessie, but the problem started appearing a few months back in wheezy.

Suspected HDD, SMART data says it's fine. Suspected RAM, memtest86+ says its
fine after multiple rounds. It could be a faulty motherboard (the laptop is 5
years old) but I've seen mentions of ubuntu also having the same random lockups
on newer laptops. https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1184451

Thank you,
Demetris Demetriou
deZillium LTD



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

Bug#754618: [Pkg-sssd-devel] Bug#754618: sssd: FTBFS on many archs due to testsuite failures

2014-08-21 Thread Timo Aaltonen

On 17.08.2014 09:56, Petter Reinholdtsen wrote:
 [Timo Aaltonen]
 Sigh #748671, another forgotten bug.. the CVE is of low importance
 though, and is not blocking.
 
 Ah, glad to have reminted you, as
 URL: https://packages.qa.debian.org/s/sssd.html  show that #748671
 block sssd version 1.11.5.1-2 from entering testing, blocking the
 Debian Edu roaming workstation setup to work out of the box (in
 addition to another bug we are working on. :).
 
 Apart from the libsasl2-modules-ldap demotion everything else should be
 in 1.11.5.1-1/2 already. The new upstream version was released because
 of the samba issue Stephane reported.
 
 Ah, good to know. :) Then I guess the diff will go away when Ubuntu
 update their package.
 
 btw, the FTBFS's seem to be caused by timeouts, one build can
 succeed fine and the next fails with 1-3 failures..
 
 Ah, races.  Always fun to debug. :/

Well, I've just disabled tests on slow archs, and the new sbus tests
fail because of the chroot, reason yet to be discovered..



-- 
t


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#746858: Status of igstk (should we remove the package?)

2014-08-21 Thread Dominique Belhachemi

Hi Andreas,

I think you are right, this is a good time to go forward with the removal
request.

-Dominique
On Aug 21, 2014 3:54 AM, Andreas Tille ti...@debian.org wrote:

 Hi,

 as you might have noticed igstk is RC buggy and also lagging behind
 upstream (5.2).  If nobody has any interest in keeping the package alive
 we might consider droping it from the archive.

 What do you think?

 Kind regards

   Andreas.

 --
 http://fam-tille.de

Bug#745904: rsyslogd-2068: could not load module '/usr/lib/rsyslog/lmnsd_gtls.so', rsyslog error -2078

2014-08-21 Thread Edy Corak

On Do, Aug 21, 2014 13:04:48, Michael Biebl wrote:

 Am 21.08.2014 10:28, schrieb Edy Corak:
  I have now found the problem. Sorry, that was my mistake.
  
  The certificate has been updated and because the server was not rebooted 
  long time, I got the error not noticed.
  After a reboot, just this error message appears in the log files.
  Perhaps it is possible to specify the error message, so that the error is 
  easier to see ?
 
 Have you also tried to run it in debug mode (-d)?
 If you also didn't get a proper error message this way, please file a
 bug upstream [1] and report back with the bug number.
 
 
 Michael
 
 
 [1] http://bugzilla.adiscon.com/
 -- 
 Why is it that all of the instruments seeking intelligent life in the
 universe are pointed away from Earth?
 
Hi,

I have try the debug mode (-d). The path was changed to non existing, to see 
what error message will be shown.
Only at the start in debug mode (-d) there is following message:

unexpected GnuTLS error -64 in nsd_gtls.c:583: Error while reading file.
Called LogError, msg: could not load module '/usr/lib/rsyslog/lmnsd_gtls.so', 
rsyslog error -2078

And later there is only the last one about could not load module

Called LogError, msg: could not load module '/usr/lib/rsyslog/lmnsd_gtls.so', 
rsyslog error -2078

When I start rsyslogd with (-c5 -d) there is only one message

rsyslogd-2068: could not load module '/usr/lib/rsyslog/lmnsd_gtls.so', rsyslog 
error -2078 [try http://www.rsyslog.com/e/2068 ]

Maybe this can be changed to show always the complete error message.

I missed the error message at the beginning in debug mode (-d).

But now it's ok, everything works like it should.

Thanks for your help

Best regards

Edy Corak


signature.asc
Description: Digital signature

Bug#758794: taskcoach: app freezes when I try to edit any task

2014-08-21 Thread clayton

Package: taskcoach
Version: 1.4.0-1
Severity: important

This is what I see everytime in the terminal at the moment of the freeze:

$ taskcoach
QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.

This happens for both double-clicking the task in the list, or right clicking 
the task
and then selecting edit. Every time.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-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

Versions of packages taskcoach depends on:
ii  fonts-dejavu  2.34-1
ii  libxss1   1:1.2.2-1
ii  python2.7.8-1
ii  python-chardet2.2.1-2
ii  python-dateutil   1.5+dfsg-1
ii  python-keyring4.0-1
ii  python-lockfile   1:0.8-2
ii  python-pyparsing  2.0.2+dfsg1-1
ii  python-squaremap  1:1.0.4-1
ii  python-twisted14.0.0-2
ii  python-wxgtk2.8   2.8.12.1+dfsg2-1
ii  python-wxversion  2.8.12.1+dfsg2-1
ii  python-xdg0.25-4
ii  x11-utils 7.7+2

Versions of packages taskcoach recommends:
ii  libavahi-compat-libdnssd1  0.6.31-4
ii  libgnome-2-0   2.32.1-5
ii  python-notify  0.1.1-3

Versions of packages taskcoach suggests:
pn  espeak   none
ii  python-kde4  4:4.13.3-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#684010: [blueman] Turning off bluetooth also disables WiFi in NetworkManager

2014-08-21 Thread Christopher Schramm

Is this still valid for recent versions?


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#757961: Does not work with GCC 4.9, default GCC in Jessie

2014-08-21 Thread Graham Inggs

Just for reference, nvidia-cuda-toolkit 6.0.37 also prevents the use of 
gcc  4.8 in /usr/include/host_config.h and therefore needs the same patch.
In fact, the only difference between /usr/include/host_config.h in 
5.5.22 and 6.0.37 is that the version in 6.0.37 now allows ICC 13.1 
instead of ICC 12.1.


Tomasz: do you need this uploaded before you can upload pycuda 2014.1?


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758795: RFP: libdate-range-perl -- Work with a range of dates in Perl

2014-08-21 Thread Mark Raymond

Package: wnpp
Severity: wishlist

* Package name: libdate-range-perl
  Version : 1.41
  Upstream Author : Tony Bowden t...@tmtm.com
* URL : https://metacpan.org/pod/Date::Range
* License : GPLv2
  Programming Lang: Perl
  Description : Work with a range of dates in Perl


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737441: [src:nagios3] Sourceless file (minified) (jquery)

2014-08-21 Thread Petter Reinholdtsen

Hi.  I noticed from
URL: https://packages.qa.debian.org/n/nagios3.html  that Nagios is
no longer available in Debian testing, thanks to this bug.

The bug #737441 about jquery javascript files without source in the
Nagios tarball has caused Nagios to be removed from testing.  This is
unfortunate for Debian Edu, which currently hope to use it in Jessie.

What is the plan for addressing the issue?  Will the proposal from
Daniel Pocock work?  Should we work on providing a patch, or are there
other plans for Nagios in Debian?

-- 
Happy hacking
Petter Reinholdtsen


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758796: src:parole: use dh-autoreconf to fix FTBFS on ppc64el

2014-08-21 Thread Erwan Prioul


Package: src:parole
Version: 0.5.4-1
Severity: normal
Tags: patch

Dear Maintainer,

While trying to build the package on ppc64el, it failed, due to libtool 
and configuration files not being updated.

Please consider this patch, which uses dh-autoreconf to fulfill that need.

Thanks in advance,
Erwan.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ppc64el (ppc64le)

Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

diff -Naur a/debian/control b/debian/control
--- a/debian/control	2014-08-21 14:13:01.465275083 +0200
+++ b/debian/control	2014-08-21 14:56:17.273137119 +0200
@@ -8,7 +8,8 @@
  libgtk2.0-dev (= 2.20), libgstreamer0.10-dev, 
  libgstreamer-plugins-base0.10-dev, libdbus-1-dev, libdbus-glib-1-dev,
  libxfce4ui-1-dev, libxfconf-0-dev (= 4.10),
- libnotify-dev, libtagc0-dev
+ libnotify-dev, libtagc0-dev,
+ dh-autoreconf, xfce4-dev-tools, gtk-doc-tools
 Standards-Version: 3.9.4
 Homepage: http://goodies.xfce.org/projects/applications/parole
 Vcs-Svn: svn://anonscm.debian.org/pkg-xfce/goodies/trunk/parole/
diff -Naur a/debian/rules b/debian/rules
--- a/debian/rules	2014-08-21 14:13:01.565275078 +0200
+++ b/debian/rules	2014-08-21 14:16:32.993263841 +0200
@@ -5,7 +5,7 @@
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 
 %:
-	dh $@ --parallell
+	dh $@ --parallell --with autoreconf
 
 override_dh_makeshlibs:
 	dh_makeshlibs -X usr/lib/$(DEB_HOST_MULTIARCH)/parole-0
@@ -15,4 +15,5 @@
 	dh_install --fail-missing
 
 override_dh_auto_configure:
+	xdt-autogen
 	dh_auto_configure -- --disable-silent-rules

Bug#749743: qt4-x11: use ppc64el in no_pch_architectures to fix FTBFS on ppc64el

2014-08-21 Thread Lisandro Damián Nicanor Pérez Meyer

Copying ppc64el porters to see if we can speed up this and be able to push qt4
with ppc64el on saturday (hopefully).

On Sunday 15 June 2014 23:14:37 Lisandro Damián Nicanor Pérez Meyer wrote:
On Thursday 29 May 2014 20:26:53 Brahadambal Srinivasan wrote:
[snip]

Dear Maintainer,

While trying to build qt4-x11 on ppc64el, it failed, as it
required 'ppc64el' to be added to the no_pch_architectures
list

No problem with this one, I have already added it to the list.

And it has been there since a couple of uploads.

and also needed changes in the configure script.
Please consider the patches here, to correct the build issues.

Now I do have some concerns here. That seems to be changing more things that
just ppc64el stuff.

I guess you need to change *86_64 to *64* because ppc is definitely no x86
:) But I really doubt this is the correct way to do it.

And this is why I'm CCing porters. I currently do not have much spare time to
get into a porterbox myself, and I will do my best to push a qt4-x11 upload on
saturday to add (at least) arm64 support. If someone can get to test this
before that I might be able to add ppc64el as well.

We have three issues here:

- In the patch [0] *86_64 has been changed to *64 in two lines (in the
middle). I'm really skeptic that this is a good change (if needed at all). And
I need to convince upstream too. Is this really necessary? In case it is, is
there a more precise approach? Like, for example, leaving *86_64 and adding a
new rule for whatever fits ppc64el.

- The second issue is: who did this patch? It is not mentioned in the bug and
I need that info to properly add a patch for whatever reason.

- The first change in the mentioned patch uses ppc64le and not ppc64el, is
that right?

Now, about upstreaming the patch: Qt has a CLA in which you *don't* loose your
copyright but just give permission to Digia to use it in it's commercial
product (the code remains FLOSS!). I have two ways of pushing this upstream:

- Find the original coder and beg him to push it to upstream's gerrit instance
(preferred)

- Find the original coder and beg him to publicly state (on a mailing list,
for example) that this patch is licensed under a BSD license, which is less
restrictive.

We don't want to have deltas, so I *really* need your help here.

Note: in this *particular* case I might solve this issue by the fact that this
change really doesn't seems copyrighteable because it's just using already
defined stuff, but if we have either of the above situations things get much
much easier.

[0]
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=add_ppc64le_support.patch;att=2;bug=749743

Kinds regards, Lisandro.

--
El futuro es WIN95 A no ser que hagamos algo a tiempo.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

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

Bug#758797: migemo-el: breaks compatibility with emacs23

2014-08-21 Thread Tatsuya Kinoshita

Package: migemo-el
Version: 1:1.2+gh0.20140306-2
Severity: important

New migemo.el uses cl-lib which breaks compatibility with Emacs
older than 24.3.

To prevent an installation failure with Emacs 24.3, skip
byte-compilation when FLAVOR is
`emacs|emacs23|emacs22|emacs21|emacs20|emacs19|mule2|xemacs*`
(allow emacs24 and future flavors).

Thanks,
--
Tatsuya Kinoshita


pgpFLUXH0NzhD.pgp
Description: PGP signature

Bug#758798: ifupdown-extra: check-network-cable fails because of leading spaces

2014-08-21 Thread ael

Package: ifupdown-extra
Version: 0.25
Severity: normal
Tags: patch

The line in check_status_ethtool():
 local LINK=$($ETHTOOL $IFACE 21 | grep Link detected || :)
fails because ethtool has leading spaces.
A simple fix is to quote:
  local LINK=$($ETHTOOL $IFACE 21 | grep Link detected || :)
-

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

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ifupdown-extra depends on:
ii  bind9-host [host]1:9.9.5.dfsg-4
ii  curl 7.37.1-1
ii  dpkg 1.17.10
ii  host 1:9.9.5.dfsg-4
ii  iproute2 3.16.0-1
ii  iputils-arping   3:20121221-5+b1
ii  iputils-ping [ping]  3:20121221-5+b1
ii  net-tools1.60-26
ii  netcat-traditional [netcat]  1.10-40

Versions of packages ifupdown-extra recommends:
ii  ethtool  1:3.13-1

ifupdown-extra suggests no packages.

-- no debconf information
--- 00check-network-cable_old	2014-04-10 00:38:10.0 +0100
+++ 00check-network-cable_new	2014-08-21 14:48:47.998575266 +0100
@@ -69,7 +69,7 @@
 
 check_status_ethtool() {
 	local status=0
-	local LINK=$($ETHTOOL $IFACE 21 | grep Link detected || :)
+	local LINK=$($ETHTOOL $IFACE 21 | grep Link detected || :)
 
 	# If ethtool fails to print out the link line we break off
 	# notice that ethtool cannot get the link status out of all
--- 00check-network-cable_old	2014-04-10 00:38:10.0 +0100
+++ 00check-network-cable_new	2014-08-21 14:48:47.998575266 +0100
@@ -69,7 +69,7 @@
 
 check_status_ethtool() {
 	local status=0
-	local LINK=$($ETHTOOL $IFACE 21 | grep Link detected || :)
+	local LINK=$($ETHTOOL $IFACE 21 | grep Link detected || :)
 
 	# If ethtool fails to print out the link line we break off
 	# notice that ethtool cannot get the link status out of all

Bug#758726: git-buildpackage: git-pbuilder removes necessary *.source.changes

2014-08-21 Thread Guido Günther

Hi,
On Wed, Aug 20, 2014 at 06:36:45PM +0200, Markus Koschany wrote:
 Package: git-buildpackage
 Version: 0.6.15
 Severity: normal
 
 Hi,
 
 This bug was already reported on launchpad.net.
 
 https://bugs.launchpad.net/ubuntu/+source/git-buildpackage/+bug/1349103
 
 In short when I run git-buildpackage -S the source.changes file gets
 deleted afterwards and I would expect that this won't happen.
 
 I'm quoting the bug reporter from launchpad because I experience the
 exact same issue here on Debian unstable.
 
 When using `git-buildpackage -S` to produce a source package, it can
 manage to successfully build everything, but then gets to this part in
 /usr/bin/pbuilder:

s/pbuilder/git-pbuilder/

 
 if [ -n `ls ../*_source.changes` ] ; then
  rm ../*_source.changes
 fi

Yeah, for the -S case this hould probably be skipped. Russ?

Cheers,
 -- Guido


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#755581: systemd: emergency mode infinite loop after systemd upgrade

2014-08-21 Thread Johannes Schauer

Hi Michael,

sorry that it took me two days to come back to you but I was attending the
Debian Bootstrap sprint and could not afford to reboot my laptop and end up
with a possibly broken system these days.

Quoting Michael Biebl (2014-08-19 16:15:31)
 Johannes, it seems that we tracked this issue down. Sorry it took so long.
 
 The problem is an active syslog.socket when emergency mode is entered.
 Each log message then tries to start rsyslog.service which conflicts
 with the emerge service (due to the dependencies rsyslog.service has).
 
 We need to make sure that syslog.socket is stopped when the emergency
 mode is entered.
 
 Adding Conflicts=syslog.socket to emergency.service [1] seems to be an
 acceptable workaround.
 
 It would be great if you can confirm that this also fixes the problem of
 the failing emergency mode for you.

I added Conflicts=syslog.socket to the [Unit] section of
/lib/systemd/system/emergency.service and can confirm that after the boot
failed, I now get correctly dropped into emergency mode.

Thanks a lot for fixing this!

I see that you closed this bugreport. Is the issue of my filesystems not being
mounted tracked under another bug?

cheers, josch


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#746858: Status of igstk (should we remove the package?)

Hi Dominique,

On Thu, Aug 21, 2014 at 08:56:42AM -0400, Dominique Belhachemi wrote:
 Hi Andreas,
 
 I think you are right, this is a good time to go forward with the removal
 request.

Could you please also give some reasons for Debian Med mailing list
readers why we are stopping to support some software that is actively
maintained upstream?  There might be interested people who could keep on
working with this but simply have not realised that there is a problem.
So please try to be verbose in public about the reasons.

Kind regards

  Andreas.

-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#753943: RFS: gcstar/1.7.0-1 [ITA]

2014-08-21 Thread Jörg Frings-Fürst

Hola Eriberto,

first thank you for reviewing gcstar.

Am Mittwoch, den 20.08.2014, 13:42 -0300 schrieb Eriberto Mota:
 tags 753943 moreinfo
 thanks
 
 Hi again Jörg. :-)
 
 Please,
 
 1. d/control: change from 'internet' to 'Internet' in long description.
ok.
 2. d/copyright:
  - 2006-2011 to Alexander Wirt.
  - I found several names and years. Please, use 'grep -sri
 copyright * | grep -v debian' and review d/copyright carefully.
 
done

 3. d/gcstar.lintian-overrides: make the script executable via d/rules
 or add a comment line explaining the motive of the override. I prefer
 the first.
 
I have add a chmod in d/rules and delete the override file.

 4. Remove the useless file README.source.
 
done.

 5. d/rules: remove the second line.
 
ok

 6. d/watch: remove the first line and aditional final break lines. To
 see all blank final lines use 'tail -n1 *' in debian/.
 
ok.

 7. Solve this Lintian message: I: gcstar:
 desktop-entry-lacks-keywords-entry
 usr/share/applications/gcstar.desktop
 
done.

 8. d/dirs: I think that it is useless.
 
ok.

 9. I got these errors when testing in cowbuilder:
 
 Net::FreeDBOK
 Ogg::Vorbis::Header::PurePerl  OK
 Time::PieceOK
 
 I/O error : Permission denied
 I/O error : Permission denied
 Failed to write XML file; For permission problems, try rerunning as root
 I/O error : Permission denied
 I/O error : Permission denied
 Failed to write XML file; For permission problems, try rerunning as root
 Installing in /tmp/buildd/gcstar-1.7.0/debian/gcstar/usr/
 
 End of the installation
 No error
 
I have found two issues for this:

- The upstream install script removes previous installation files and
- it runs update-desktop-database  update-mime-database.

Both disabled via patch and in d/rules.

 Thanks for your work. Have a nice day!
 
 Cheers,
 
 Eriberto
 
[...]

Package is uploaded to mentors[1]. I make the git push this evening.

 
CU
Jörg


[1] http://mentors.debian.net/debian/pool/main/g/gcstar/gcstar_1.7.0-1.dsc

-- 
pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8  EBCB 422B 44B0 BE58 1B6E
pgp Key: BE581B6E
CAcert Key S/N: 0E:D4:56

Jörg Frings-Fürst
D-54526 Niederkail

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net







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

Bug#758799: RFP: libtemplate-plugin-digest-md5-perl -- Template::Toolkit interface to the MD5 algorithm

2014-08-21 Thread Mark Raymond

Package: wnpp
Severity: wishlist

* Package name: libtemplate-plugin-digest-md5-perl
  Version : 0.04
  Upstream Author : Barbie bar...@missbarbell.co.uk
* URL : https://metacpan.org/pod/Template::Plugin::Digest::MD5
* License : Artistic Licence v2
  Programming Lang: Perl
  Description : Perl Template::Toolkit interface to the MD5 algorithm


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#756794: vsftpd: FTBFS on kfreebsd-*

2014-08-21 Thread Steven Chamberlain

tags + patch
user debian-...@lists.debian.org
usertags + kfreebsd
thanks

Hi,

On 20/08/14 16:38, Jörg Frings-Fürst wrote:
 There are no changes at sysdeputil.c between vsftpd/3.0.2-14 and
 vsftpd/3.0.2-15.

I see what happened:  kfreebsd-kernel-headers introduced a new
sys/capability.h which we did not have before.  vsftpd will use it in
preference to a dummyinc/sys/capability.h

You can see in dummyinc/sys/capability.h that it would otherwise #undef
VSF_SYSDEP_HAVE_LIBCAP.

vsftpd expects sys/capability.h will define cap_t, but only libcap has
that, our header does not.  I'm not sure what's right/wrong here.
libcap is a linux-any package currently but would conflict with this
FreeBSD kernel header otherwise.  (Why does libpcap put it in sys/?)

Either way, we don't seem to have libcap on GNU/kFreeBSD, and quoting
Ben Kaduk:
 It seems [libpcap] is the provider of the cap_t; there is no such concept in
 the base freebsd system.

I think it is appropriate to add the attached, along with the other
platform-specific configuration atop sysdeputil.c

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org
Description:
  Neither FreeBSD nor GNU/kFreeBSD have libpcap.  Avoid confusing
  sys/capability.h kernel header with libpcap's
Author: Steven Chamberlain ste...@pyro.eu.org
Bug-Debian: http://bugs.debian.org/756794
Forwarded: no

--- a/sysdeputil.c
+++ b/sysdeputil.c
@@ -113,6 +113,10 @@
   #define VSF_SYSDEP_HAVE_SETPROCTITLE
 #endif
 
+#if defined(__FreeBSD_kernel__)
+  #undef VSF_SYSDEP_HAVE_LIBCAP
+#endif
+
 #if defined(__NetBSD__)
   #include stdlib.h
   #define VSF_SYSDEP_HAVE_SETPROCTITLE


signature.asc
Description: OpenPGP digital signature

Bug#746858: Status of igstk (should we remove the package?)

2014-08-21 Thread Steve M. Robbins

On August 21, 2014 09:50:56 AM Andreas Tille wrote:
 Hi,
 
 as you might have noticed igstk is RC buggy and also lagging behind
 upstream (5.2).  If nobody has any interest in keeping the package alive

I don't use the package and have no intention of maintaining it, I'm afraid.

-Steve


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#755581: systemd: emergency mode infinite loop after systemd upgrade