Hi Danni,
On Tue, May 10, 2016 at 07:13:28PM +0200, Andreas Tille wrote:
> >
> > I then rebuilt the package on a fresh sid cowbuilder, but now there's a
> > new problem (see attachment for the exact error message) near the end of
> > the build, involving a static_cast.
I can confirm that the cur
Hi,
libbson-doc also ships
/usr/share/man/man3/clock.3.gz
which also exists in manpages-dev. -Ralf.
Package: golang-github-rcrowley-go-metrics-dev,golang-metrics-dev
Version: golang-github-rcrowley-go-metrics-dev/0.0~git20160226.0.eeba7bd-1
Version: golang-metrics-dev/0.0~git20150823-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Date: 2016-05-18
Architecture: amd64
D
Processing commands for cont...@bugs.debian.org:
> reassign 824623 cdbs
Bug #824623 {Done: Simon McVittie } [src:glib2.0] glib2.0
FTBFS: dh_install: libglib2.0-tests missing files:
usr/lib/glib2.0/installed-tests
Bug reassigned from package 'src:glib2.0' to 'cdbs'.
No longer marked as found in v
Your message dated Wed, 18 May 2016 07:20:22 +0100
with message-id <20160518062022.ga12...@perpetual.pseudorandom.co.uk>
and subject line Re: Bug#824623: glib2.0 FTBFS: dh_install: libglib2.0-tests
missing files: usr/lib/glib2.0/installed-tests
has caused the Debian Bug report #824623,
regarding g
Source: glib2.0
Version: 2.48.1-1
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap
Hi,
glib2.0 FTBFS again. A few days ago, cdbs was responsible (#824083) for
that. Now I cannot tell, but I wouldn't rule that out either and
therefore put Jonas into Cc. Either way, glib2.0 didn't c
Processing commands for cont...@bugs.debian.org:
> reassign 823962 boxer-data 8
Bug #823962 [parl-desktop-strict] parl-desktop-strict: not installable in sid
Bug reassigned from package 'parl-desktop-strict' to 'boxer-data'.
No longer marked as found in versions debian-parl/1.9.2.
Ignoring request
the problem its that versions in wheeze stable are not fixed!
what about it?
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Your message dated Wed, 18 May 2016 00:19:59 +
with message-id
and subject line Bug#824605: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u4
has caused the Debian Bug report #824605,
regarding kfreebsd-10: CVE-2016-1887: Incorrect argument handling in sendmsg(2)
to be marked as done.
This means
Your message dated Wed, 18 May 2016 00:20:28 +
with message-id
and subject line Bug#821898: fixed in opendkim 2.11.0~alpha-2
has caused the Debian Bug report #821898,
regarding opendkim: incompatible SSL versions
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 18 May 2016 00:19:59 +
with message-id
and subject line Bug#824604: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u4
has caused the Debian Bug report #824604,
regarding kfreebsd-10: CVE-2016-1886: Buffer overflow in keyboard driver
to be marked as done.
This means that yo
Your message dated Tue, 17 May 2016 23:49:25 +
with message-id
and subject line Bug#824585: fixed in cdbs 0.4.134
has caused the Debian Bug report #824585,
regarding libgnomekbd: FTBFS: find: 'doc': No such file or directory
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> reassign 823101 ftp.debian.org
Bug #823101 [src:python-geoclue] python-geoclue: geoclue is scheduled for
removal - switch to geoclue2
Bug reassigned from package 'src:python-geoclue' to 'ftp.debian.org'.
No longer marked as found in versions pyth
Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u3
Severity: grave
Tags: security
https://security.FreeBSD.org/advisories/FreeBSD-SA-16:19.sendmsg.asc
Incorrect argument handling in the socket code allows malicious local
user to overwrite large portion of the kernel memory.
This affects
Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u3
Severity: grave
Tags: security
https://security.FreeBSD.org/advisories/FreeBSD-SA-16:18.atkbd.asc
Incorrect signedness comparison in the ioctl(2) handler allows a
malicious local user to overwrite a portion of the kernel memory.
This aff
Your message dated Tue, 17 May 2016 22:32:59 +
with message-id
and subject line Bug#824587: fixed in objenesis 2.3-2
has caused the Debian Bug report #824587,
regarding objenesis: Missing parent pom
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 17 May 2016 22:21:12 +
with message-id
and subject line Bug#824550: fixed in gr-air-modes 0.0.2.65e5bd1-1
has caused the Debian Bug report #824550,
regarding gr-air-modes build-depends on zeromq which is going to be removed
to be marked as done.
This means that you cla
Your message dated Tue, 17 May 2016 22:22:12 +
with message-id
and subject line Bug#824584: fixed in libetonyek 0.1.6-2
has caused the Debian Bug report #824584,
regarding libetonyek: FTBFS: configure: error: Package requirements (mdds) were
not met
to be marked as done.
This means that you
raise KeyError(key)
| KeyError: 'LANG'
| dh_auto_build: python setup.py build --force returned exit code 1
For a full build log see
https://people.debian.org/~sramacher/logs/wicd_1.7.4+tb2-1_amd64-20160517-2208.log
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
7;: u'rigel',
'replication_driver_data': None, 'replication_status': u'disabled',
'snapshot_id': None, 'replication_extended_status': None, 'user_id':
'c853ca26-e8ea-4797-8a52-ee124a013d0e', 'metadata': [], 'launched_at':
'2016-05-17T20:58:41.257605
--
| _StringException: Empty attachments:
| pythonlogging:''
| stderr
| stdout
|
| Traceback (most recent call last):
| File "reno/tests/test_scanner.py", line 186, in setUp
| self._git_setup()
| File "reno/tests/test_scan
I don't know how to use targetcli. I tried the simple command you gave in
your bug report, but that failed for other reasons (some kind of input file is
missing).
In any case, I just uploaded pyparsing 2.1.4+dfsg1-1 which has a number of bug
fixes. Please try that. If it works for you, great!
Le 17/05/2016 à 21:52, Markus Koschany a écrit :
> Hmm, they don't ship a parent pom in 2.3 anymore. I will see if I can
> simply reuse the old one.
The project still has a parent pom though:
https://github.com/easymock/objenesis/blob/2.3/pom.xml
I suggest using the GitHub tag archive as th
Am 17.05.2016 um 21:38 schrieb Emmanuel Bourg:
> Control: retitle -1 objenesis: Missing parent pom
> Control: reassign -1 objenesis 2.3-1
> Control: affects -1 stapler wagon2
>
> Thank you for the report Chris. This error is caused by objenesis/2.3-1,
> the parent pom is missing in the update. It
Processing control commands:
> retitle -1 objenesis: Missing parent pom
Bug #824587 [src:stapler] stapler: FTBFS: Could not resolve dependencies for
project org.kohsuke.stapler:stapler:jar
Changed Bug title to 'objenesis: Missing parent pom' from 'stapler: FTBFS:
Could not resolve dependencies f
Control: retitle -1 objenesis: Missing parent pom
Control: reassign -1 objenesis 2.3-1
Control: affects -1 stapler wagon2
Thank you for the report Chris. This error is caused by objenesis/2.3-1,
the parent pom is missing in the update. It affects all reverse
dependencies using Maven.
Processing commands for cont...@bugs.debian.org:
> affects 824585 src:libgnomekbd
Bug #824585 [cdbs] libgnomekbd: FTBFS: find: 'doc': No such file or directory
Added indication that 824585 affects src:libgnomekbd
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
824
Control: reassign -1 cdbs 0.4.132
Hi Chris,
thanks for your bug report. This is a regression in cdbs, thus reassigning.
Am 17.05.2016 um 21:04 schrieb Chris Lamb:
> dpkg-buildpackage: info: source package libgnomekbd
> dpkg-buildpackage: info: source version 3.6.0-1
> dpkg-buildpackage: in
Processing control commands:
> reassign -1 cdbs 0.4.132
Bug #824585 [src:libgnomekbd] libgnomekbd: FTBFS: find: 'doc': No such file or
directory
Bug reassigned from package 'src:libgnomekbd' to 'cdbs'.
No longer marked as found in versions libgnomekbd/3.6.0-1.
Ignoring request to alter fixed vers
Not a concern after previous patches
Source: networkmanager-qt
Version: 5.16.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
networkmanager-qt fails to build from source in unst
Source: libgnomekbd
Version: 3.6.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
libgnomekbd fails to build from source in unstable/amd64:
Source: stapler
Version: 1.242-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
stapler fails to build from source in unstable/amd64:
[..]
Source: libetonyek
Version: 0.1.6-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
libetonyek fails to build from source in unstable/amd64:
Source: supercollider
Version: 1:3.7.0~repack-1
Severity: serious
Hi,
supercollider FTBFS on every arch except for amd64, i386, armhf and
mipsel.
The build fails during the compile of oscpack_build.cpp with one of
these errors. The first error appears on 64-bit arches only.
===
[ 30%] Buil
Fix a SIGABRT in pdb file handling
bug: https://github.com/ImageMagick/ImageMagick/issues/148
bug-ubuntu:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1556273
origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/53c1dcd34bed85181b901bfce1a2322f85a59472
bug: https://github.com/ImageMagick/ImageMagick/issues/143
origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/424d40ebfcde48bb872eba75179d3d73704fdf1f
bug-ubuntu:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1553366
bug-debian: https://bugs.debian.org
Ben Hutching uploaded linux 4.5.4-1 that fixes this issue this morning.
See https://bugs.debian.org/822396
Build is under way...
https://buildd.debian.org/status/package.php?p=linux&suite=unstable
collected no longer FTBFS here.
Your message dated Tue, 17 May 2016 17:51:45 +
with message-id
and subject line Bug#823916: fixed in pypy 5.1.2+dfsg-1
has caused the Debian Bug report #823916,
regarding pypy: FTBFS on s390x
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1553366
Origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/1bc1fd0ff8c555841c78829217ac81fa0598255d
bug-ubuntu:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1545183
bug-debian: https://bugs.debian.org/823750
Bug:https://github.com/ImageMagick/ImageMagick/issue
Control: tags -1 moreinfo
On Fri, 6 May 2016 16:52:33 +0200 Laurent Bigonville
wrote:
> Do you think it's a regression from 3.18? TBH, I think I already saw
> this behavior in the past.
Tobias, can you please answer this question, i.e. try 3.18 from testing
and see if that shows the same behavi
Processing control commands:
> tags -1 moreinfo
Bug #822529 [gdm3] gdm3: retries to often / to fast on errors
Added tag(s) moreinfo.
--
822529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: severity -1 important
Hi Ben
On Fri, 25 Mar 2016 08:50:04 + Simon McVittie wrote:
> On Wed, 23 Mar 2016 at 15:48:33 +, Ben Hutchings wrote:
> > If I change the network configuration through the right hand menu in
> > GNOME Shell it may hang for 10 seconds or (apparently) indefin
Processing control commands:
> severity -1 important
Bug #819096 [gnome-shell] Frequent hangs/crashes when changing network
configuration
Severity set to 'important' from 'serious'
--
819096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819096
Debian Bug Tracking System
Contact ow...@bugs.d
Your message dated Tue, 17 May 2016 16:21:21 +
with message-id
and subject line Bug#824455: fixed in irstlm 6.00.05-2
has caused the Debian Bug report #824455,
regarding missing license in debian/copyright
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Tue, 17 May 2016 16:20:19 +
with message-id
and subject line Bug#823318: fixed in giada 0.12.1~dfsg1-1
has caused the Debian Bug report #823318,
regarding giada: contains non-free Steinberg ASIO library
to be marked as done.
This means that you claim that the problem has be
Processing commands for cont...@bugs.debian.org:
> tags 815409 + confirmed
Bug #815409 [qemu] qemu-img create -f qcow2 ... segfaults on mips
Added tag(s) confirmed.
> found 815409 2.6+dfsg-1
Bug #815409 [qemu] qemu-img create -f qcow2 ... segfaults on mips
There is no source info for the package '
Package: python-pyparsing
Version: 2.1.1+dfsg1-1
Severity: serious
Dear Maintainer,
'saveconfig' command of targetcli (in targetcli package) does not work with
python-pyparsing_2.1.1+dfsg1-1_all.deb package.
downgrade to python-pyparsing_2.0.3+dfsg1-1_all.deb fixes problem.
# targetcli / savecon
Hi Emilio (2016.05.17_17:22:58_+0200)
> On Thu, 12 May 2016 22:34:17 + Stefano Rivera wrote:
> > pypy (5.1.1+dfsg-2) unstable; urgency=medium
> > .
> >* Cherry-pick upstream s390x patches, that should (amongst other things)
> > get
> > us building on s390x, again. (Closes: #823916)
Processing control commands:
> reopen -1
Bug #823916 {Done: Stefano Rivera } [src:pypy] pypy: FTBFS
on s390x
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in vers
Control: reopen -1
On Thu, 12 May 2016 22:34:17 + Stefano Rivera wrote:
> pypy (5.1.1+dfsg-2) unstable; urgency=medium
> .
>* Cherry-pick upstream s390x patches, that should (amongst other things)
> get
> us building on s390x, again. (Closes: #823916)
You might have noticed it, b
On 17/05/16 14:21, Vlad Orlov wrote:
> Hi,
>
> This doesn't happen even in VirtualBox working on a host with an old Core 2
> Duo
> (both host and guest Debian installations are 64-bit). The upgrade went fine.
This is because your CPU architecture is not 32 bit, and not i586 or lower.
I'm sure if
Processing commands for cont...@bugs.debian.org:
> tags 822369 - pending
Bug #822369 [xfsprogs] xfsprogs: FTBFS: error: redefinition of 'struct fsxattr'
Bug #822470 [xfsprogs] qemu: FTBFS: error: redefinition of 'struct fsxattr'
Removed tag(s) pending.
Removed tag(s) pending.
> thanks
Stopping pro
Package: flashplugin-nonfree
Version: 1:3.6.1+b1
Followup-For: Bug #814316
Dear Maintainer,
Flash Player version installed on this system : 11.2.202.616
Flash Player version available on upstream site: 11.2.202.621
flash-mozilla.so - auto mode
link best version is /usr/lib/flashplugin-nonfree/
Processing commands for cont...@bugs.debian.org:
> tags 822369 + pending
Bug #822369 [xfsprogs] xfsprogs: FTBFS: error: redefinition of 'struct fsxattr'
Bug #822470 [xfsprogs] qemu: FTBFS: error: redefinition of 'struct fsxattr'
Added tag(s) pending.
Added tag(s) pending.
> tags 823588 + pending
B
Package: flashplugin-nonfree
Version: 1:3.6.1+b1
Followup-For: Bug #814316
Dear Maintainer,
please update to new upstream version, which fixes CVE-2016-4117 [1].
Thank you.
[1] https://helpx.adobe.com/security/products/flash-player/apsa16-02.html
-- Package-specific info:
Debian version: st
Package: elpa-ebib
Version: 2.5.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the a
Your message dated Tue, 17 May 2016 16:22:48 +0300
with message-id <573b1b28.5040...@msgid.tls.msk.ru>
and subject line Re: Bug#824553: qemu-nbd: devices for partitions are not
created
has caused the Debian Bug report #824553,
regarding qemu-nbd: devices for partitions are not created
to be marked
Hi,
This doesn't happen even in VirtualBox working on a host with an old Core 2 Duo
(both host and guest Debian installations are 64-bit). The upgrade went fine.
Package: qemu-utils
Version: 1:2.5+dfsg-5+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
In debian testing weekly build from 2016-04-18 qemu-nbd worked fine, and in
build from 2016-04-25 it stopped working.
Steps to reproduce:
qemu-img create -f qcow2 myimg.qcow2
source: gr-air-modes
version: 0.0.1.514414f-5
severity: serious
control: block 818998 by -1
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818998
Please work towards removing the build-dependency on zeromq.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52
Processing control commands:
> block 818998 by -1
Bug #818998 [ftp.debian.org] RM: zeromq -- RoQA; old, superseeded by zeromq3
818998 was blocked by: 818222
818998 was not blocking any bugs.
Added blocking bug(s) of 818998: 824550
--
818998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81899
On Sat, May 23, 2015 at 04:37:44PM -0500, John Goerzen wrote:
> I am super busy right now (taking flying lessons) and will not likely
> have the chance to look at this soon, unfortunately. I would happily
> accept patches if anybody else has the time to do so.
I wonder, anything happened in the l
Source: node-css-parse
Version: 1.7.0+dfsg-1
Severity: serious
node-css-parse removal has been requested in
https://bugs.debian.org/764944 but can't be processed yet due to rdeps.
Filing this bug so that node-css-parse get out of stretch in the
meantime.
--
regards,
Matt
Your message dated Tue, 17 May 2016 11:34:01 +
with message-id
and subject line Bug#821576: fixed in geshi 1.0.8.11-2.1
has caused the Debian Bug report #821576,
regarding php-geshi: PHP 7.0 Transition
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Tue, 17 May 2016 11:20:51 +
with message-id
and subject line Bug#822755: fixed in kcalc 4:16.04.1-1
has caused the Debian Bug report #822755,
regarding kcalc: When launching it nothing happens
to be marked as done.
This means that you claim that the problem has been dealt w
I will try to fix this with an NMU.
--
,--.
: /` ) Tanguy Ortolo
| `-'Debian Developer
\_
signature.asc
Description: Digital signature
Processing control commands:
> forwarded -1 https://symlink.me/issues/945
Bug #817186 [weboob] Boobank reveals hidden password
Set Bug forwarded-to-address to 'https://symlink.me/issues/945'.
> tag -1 patch fixed-upstream
Bug #817186 [weboob] Boobank reveals hidden password
Added tag(s) fixed-upst
Control: forwarded -1 https://symlink.me/issues/945
Control: tag -1 patch fixed-upstream
Control: severity -1 important
Hi Bertrand,
Just passing by, wondering about weboob's state and why it isn't in
testing, I've just noticed this RC bug.
Bertrand Marc (2016-03-08):
> Package: weboob
> versio
Processing commands for cont...@bugs.debian.org:
> archive 803550
Bug #803550 [rsem] rsem: uninstallable on architectures without bowtie
Bug 803550 cannot be archived
> fixed 803550 1.2.30+dfsg-1
Bug #803550 [rsem] rsem: uninstallable on architectures without bowtie
Marked as fixed in versions rse
Your message dated Tue, 17 May 2016 11:41:15 +0200
with message-id
and subject line
has caused the Debian Bug report #803550,
regarding rsem: uninstallable on architectures without bowtie
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the ca
Processing commands for cont...@bugs.debian.org:
> forwarded 805678 https://github.com/pchanial/pyoperators/issues/23
Bug #805678 [src:pyoperators] pyoperators: FTBFS: NameError: global name
'FFTW_DEFAULT_NUM_THREADS' is not defined
Set Bug forwarded-to-address to
'https://github.com/pchanial/py
On Tue, May 17, 2016 at 09:14:39 +0200, Tino Keitel wrote:
> absolutely. Actually, I have 1.6.1 packages ready for upload.
Sorry, 1.5.1 packages of cause [1].
It's not pushed to the git repository[2] yet, just send me a notice if
someone wants to look into it.
Regards,
Tino
[1] http://tikei.de
Processing commands for cont...@bugs.debian.org:
> forwarded 820701 https://github.com/Shark-ML/Shark/issues/63
Bug #820701 [src:shark] shark: FTBFS on various architectures - testsuite
failures
Set Bug forwarded-to-address to 'https://github.com/Shark-ML/Shark/issues/63'.
>
End of message, stopp
On Tue, May 17, 2016 at 09:08:17 +0200, Patrick Ohly wrote:
[...]
> OTOH, Debian itself is still on an old, pre-release version. Tino, do
> you still have plans for getting SyncEvolution updated in Debian?
Hi,
absolutely. Actually, I have 1.6.1 packages ready for upload. I just
wanted to do som
On Mon, 2016-05-16 at 10:59 +0200, Andreas Henriksson wrote:
> Hello!
>
> Some information below which might be useful
>
> On Sun, May 15, 2016 at 09:37:24PM +0200, Michael Biebl wrote:
> > Source: syncevolution
> > Version: 1.4.99.4-5
> > Severity: serious
> >
> > Hi,
> >
> > during the li
thx
On Tue, May 17, 2016 at 3:40 AM, Geert Stappers
wrote:
> On Mon, May 16, 2016 at 05:04:29PM -0300, Cristian Aires wrote:
> > On Mon, 09 May 2016 14:22:37 +0200 Salvatore Bonaccorso wrote:
> > >
> > > For further information see:
> > >
> > > [0] https://security-tracker.debian.org/tracker/CVE
78 matches
Mail list logo
