Your message dated Sat, 14 Dec 2013 06:18:42 +
with message-id
and subject line Bug#732023: fixed in libtk-img 1:1.4.2-1
has caused the Debian Bug report #732023,
regarding libtk-img: undefined symbol TIFFReassignTagToIgnore in
libtifftcl3.8.2.so
to be marked as done.
This means that you cla
I agree with Scott's assessment, although I would note that Debian *does* have
a suite that addresses the needs of Bitcoin: stable-updates. Mandatory
protocol rule changes would seem to fall within the "broken by the flow of
time" category. Thoughts?
--
To UNSUBSCRIBE, email to debian-bugs-rc
Package: tor
Version: 0.2.3.25-1
Severity: grave
Justification: renders package unusable
Hi,
When trying to start Tor with this command, so starting it with the
Debian default torrc:
$ tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc
... then I'm getting the following error messag
Processing commands for cont...@bugs.debian.org:
> severity 707641 normal
Bug #707641 [cryptsetup] overriding root device on TS-419 non-working
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
707641: http://bugs.debian.org/c
On Fri, Dec 13, 2013 at 01:58:31AM +0100, Andreas Beckmann wrote:
> On 2013-12-03 22:30, Yann Dirson wrote:
> > I'm wondering if that could not be caused by a bug in the mime
> > trigger, that would have been fixed already.
>
> That would be easier to test - what package is it?
I was thinking abo
Package: webkitgtk
Severity: serious
User: paul...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks
Howdy maintainers,
http://sources.debian.net/src/webkitgtk/2.3.2-1/Source/WebCore/inspector/Scripts/jsmin.py
I believe this file to be a derived work, and subject to C
Your message dated Fri, 13 Dec 2013 21:20:48 +
with message-id
and subject line Bug#729629: fixed in mediawiki 1:1.19.8+dfsg-2.2
has caused the Debian Bug report #729629,
regarding mediawiki: CVE-2013-4567, CVE-2013-4568 and CVE-2013-4572
to be marked as done.
This means that you claim that t
Your message dated Fri, 13 Dec 2013 19:03:46 +
with message-id
and subject line Bug#731606: fixed in git-annex 5.20131213
has caused the Debian Bug report #731606,
regarding git-annex: git annex lock ignores modifications and replaces from
latest annexed version
to be marked as done.
This me
Processing commands for cont...@bugs.debian.org:
> unarchive 726009
Bug #726009 {Done: Anton Gladky } [src:yade] Yade requires
too much RAM for building
Unarchived Bug 726009
> forcemerge 726009 731878
Bug #726009 {Done: Anton Gladky } [src:yade] Yade requires
too much RAM for building
Bug #7318
forcemerge 726009 731878
thanks
This is the same bug like #731878. I have implemented all
possible procedures, which were advised to reduce RAM
consumption including splitting some large .cpp-files.
I do not see any other possibilities to reduce it more, sorry.
Thus we can just blacklist yade on
Your message dated Fri, 13 Dec 2013 18:58:06 +0100
with message-id
and subject line
has caused the Debian Bug report #725631,
regarding getfem++: FTBFS due to: /usr/bin/install: cannot stat 'jar/*.jar': No
such file or directory
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> fixed 725631 4.2.1~beta1~svn4482~dfsg-2
Bug #725631 [src:getfem++] getfem++: FTBFS due to: /usr/bin/install: cannot
stat 'jar/*.jar': No such file or directory
Marked as fixed in versions getfem++/4.2.1~beta1~svn4482~dfsg-2.
> thanks
Stopping pro
fixed 725631 4.2.1~beta1~svn4482~dfsg-2
thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Your message dated Fri, 13 Dec 2013 17:48:48 +
with message-id
and subject line Bug#732070: fixed in openvswitch 1.9.3+git20131029-1.1
has caused the Debian Bug report #732070,
regarding openvswitch-switch: installation fails
to be marked as done.
This means that you claim that the problem ha
Below is my opinion, and is open for debate:
Although there are mechanisms for supporting security updates in
stable debian releases, and luke-jr's work of porting fixes is great
and exactly what is needed, updates to network protocols would not
classify as a security update and would only be avai
Hi Ben,
it's always a pleasure to see that you are ok with help. I will NMU shortly.
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Sat, Dec 14, 2013 at 12:22:46AM +0800, Thomas Goirand wrote:
> Since this completely blocks the apt-get install process, and makes it
> impossible to install openvswitch-switch without manual intervention, I
> have set this bug severity to "grave", because it fits this definition:
>
> "makes th
Hi,
Since this completely blocks the apt-get install process, and makes it
impossible to install openvswitch-switch without manual intervention, I
have set this bug severity to "grave", because it fits this definition:
"makes the package in question unusable by most or all users."
By the way, it
Processing commands for cont...@bugs.debian.org:
> severity 732070 grave
Bug #732070 [openvswitch-switch] openvswitch-switch: installation fails
Severity set to 'grave' from 'important'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
732070: http://bugs.d
Your message dated Fri, 13 Dec 2013 16:00:13 +
with message-id
and subject line Bug#727750: fixed in boost1.54 1.54.0-4
has caused the Debian Bug report #727750,
regarding boost1.54: macro for int128 detection
to be marked as done.
This means that you claim that the problem has been dealt wit
Hi,
On Thu, Dec 12, 2013 at 10:45:30PM -0500, Aaron M. Ucko wrote:
> Source: psi4
> Version: 4.0~beta5+dfsg-1
> Severity: serious
> Justification: fails to build from source
>
> Builds of psi4 covering only its architecture-dependent psi4 binary
> package (as on the autobuilders, or with debuild
Bad news is now compiling fails with:
/home/wollny/Debian/ball/build/source/PYTHON/EXTENSIONS/VIEWmodule/sipVIEWpart0.cpp:
In member function 'virtual void sipDatasetControl::destroy()':
/home/wollny/Debian/ball/build/source/PYTHON/EXTENSIONS/VIEWmodule/sipVIEWpart0.cpp:2981:9:
error: reference
Hello,
it seems the attached patch solves the problem (Building at 95% way
beyond where it failed before).
Actually, it is commit 1e76c9 in the ball git repro
https://bitbucket.org/ball/ball
Cheers,
Gert
>From 1e76c9cb1920e9176b725269985c7eb43126d188 Mon Sep 17 00:00:00 2001
From: Luis de
Your message dated Fri, 13 Dec 2013 15:20:58 +
with message-id
and subject line Bug#728094: fixed in stimfit 0.13.6-1
has caused the Debian Bug report #728094,
regarding stimfit: FTBFS on kfreebsd but built there in the past
to be marked as done.
This means that you claim that the problem has
Hi,
On Fri, Dec 13, 2013 at 01:11:10PM +0100, Gert Wollny wrote:
> The build system is quite complex, which makes it difficult to fix it
> without digging too much into it. As far as I can see there is some
> mixup between creating the files in VIEW/DIALOG and VIEW/UIC and then
> things go wrong,
If you're doing an NMU anyway, want to apply the patches for the recent
CVEs? I was waiting for a new release, but not sure when one will be out.
Thanks,
Ari
On Dec 12, 2013 12:39 PM, "Cyril Brulebois" wrote:
> Control: tag -1 upstream patch
>
> Julien Cristau (2013-12-12):
> > Source: gimp
> >
Ari Pollak (2013-12-13):
> If you're doing an NMU anyway, want to apply the patches for the recent
> CVEs? I was waiting for a new release, but not sure when one will be out.
Julien doesn't seem to be in a hurry for this transition, so I'll
probably skip NMUing. Was just trying to send patches fo
Hi there,
I've updated the copy of corosync I was working with.
The patch is now here:
https://github.com/aborrero/pkg-corosync
Commit: 3343dd2 [Fix Debian bug #705023]
Please let me know any issue.
Regards.
--
Arturo Borrero González
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@list
Hi,
Thanks, Kay, for the very fast response and the detailed reasoning.
Your arguments convinced me, that it is technically a very good idea to
keep userspace out of the firmware loading. This should definitely not
be reintroduced upstream or in the Debian version of udev. (Originally
I thou
On Fri, Dec 13, 2013 at 12:48 PM, Mathieu Malaterre wrote:
> Control: forwarded -1 https://github.com/jcupitt/libvips/issues/88
>
> On Fri, Dec 13, 2013 at 11:20 AM, Jay Berkenbilt wrote:
>> Mathieu Malaterre wrote:
>>
>>> This bug is hard to debug, since libjpeg / libtiff / imagemagick are
>>>
Your message dated Fri, 13 Dec 2013 13:26:21 +0100
with message-id <1423124.pZfXh09XV4@gyllingar>
and subject line Re: Bug #727758: cups segfaults in libdbus - Fixed in 1.6.4-2 ?
has caused the Debian Bug report #727758,
regarding cups segfaults in libdbus
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> retitle 732059 VTK_USE_SYSTEM_FREETYPE is ON, but FREETYPE_LIBRARY is
> NOTFOUND.
Bug #732059 [vtk] https://github.com/jcupitt/libvips/issues/88
Changed Bug title to 'VTK_USE_SYSTEM_FREETYPE is ON, but FREETYPE_LIBRARY is
NOTFOUND.' from 'https:
Package: vtk
Severity: serious
Looks like vtk cannot be build using latest freetype (2.5.1-1), it
keeps failing with:
-- Found EXPAT: expat (found version "2.1.0")
CMake Error at CMake/vtkThirdParty.cmake:19 (MESSAGE):
VTK_USE_SYSTEM_FREETYPE is ON, but FREETYPE_LIBRARY is NOTFOUND.
Call Stack
Control: forwarded -1 https://github.com/jcupitt/libvips/issues/88
On Fri, Dec 13, 2013 at 11:20 AM, Jay Berkenbilt wrote:
> Mathieu Malaterre wrote:
>
>> This bug is hard to debug, since libjpeg / libtiff / imagemagick are
>> all linked together so this is not just a matter of recompiling vips
Processing control commands:
> forwarded -1 https://github.com/jcupitt/libvips/issues/88
Bug #714984 [libvips-tools] libvips-tools: Segmentation Fault: vips 7.28.5-1
with jpeg compression
Set Bug forwarded-to-address to 'https://github.com/jcupitt/libvips/issues/88'.
--
714984: http://bugs.debi
Processing commands for cont...@bugs.debian.org:
> fixed 714984 7.36.3-2
Bug #714984 [libvips-tools] libvips-tools: Segmentation Fault: vips 7.28.5-1
with jpeg compression
Marked as fixed in versions vips/7.36.3-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> forwarded 721622 https://issues.asterisk.org/jira/browse/ASTERISK-22980
Bug #721622 {Done: Jeremy Lainé } [asterisk-modules]
dependency change s/libradiusclient-ng2/libfreeradius-client2
Set Bug forwarded-to-address to
'https://issues.asterisk.o
Mathieu Malaterre wrote:
> This bug is hard to debug, since libjpeg / libtiff / imagemagick are
> all linked together so this is not just a matter of recompiling vips
> with libjpeg62-dev unfortunately.
The vips in wheezy does seem to have gotten caught up in libjpeg
transition issues. The case
Processing commands for cont...@bugs.debian.org:
> notfound 714984 7.36.3-1
Bug #714984 [libvips-tools] libvips-tools: Segmentation Fault: vips 7.28.5-1
with jpeg compression
Ignoring request to alter found versions of bug #714984 to the same values
previously set
>
End of message, stopping proc
Your message dated Fri, 13 Dec 2013 10:04:23 +
with message-id
and subject line Bug#730978: fixed in blender 2.69-3
has caused the Debian Bug report #730978,
regarding blender: FTBFS on armel: error: implicit declaration of function
'atomic_add_uint32'
to be marked as done.
This means that y
Your message dated Fri, 13 Dec 2013 09:19:19 +
with message-id
and subject line Bug#706155: fixed in evemu 1.2.0-1
has caused the Debian Bug report #706155,
regarding python3-evemu: fails to install: SyntaxError: invalid syntax in
evemu/base.py, line 22
to be marked as done.
This means that
It seems just linking against libfreeradius-client2 is not sufficient, we also
need to
change the default RADIUS configuration path in the asterisk code. If
libfreeradius-client2 tries to load the old configuration file
(/etc/radiusclient-ng/radiusclient.conf) it bombs with a segfault:
#0 0x
On Thu, Dec 12, 2013 at 10:42 AM, Sven Joachim wrote:
> It seems there is a problem with parallel builds, I could reproduce it
> with "dpkg-buildpackage -j2", but not in a non-parallel build.
The race condition seems to be triggered by the inability to extract
program examples from the info file
Your message dated Fri, 13 Dec 2013 09:18:18 +0100
with message-id
and subject line
has caused the Debian Bug report #732015,
regarding has_binary_operator.hp:50: Parse error at "BOOST_JOIN"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Package: inn2
Severity: critical
As subject. Having done the following, over a period of time:
install inn2
discover it doesn't work at all (bug 655748)
remove inn2
install inn2
purge inn2
The result is that the active, history and newsgroups files are deleted
without warning.
Your message dated Fri, 13 Dec 2013 09:13:28 +0100
with message-id <52aac1a8.3060...@debian.org>
and subject line Re: Bug#724215: eliom: FTBFS: make[1]: *** No rule to make
target `Makefile.config'. Stop.
has caused the Debian Bug report #724215,
regarding eliom: FTBFS: make[1]: *** No rule to ma
Processing control commands:
> severity -1 grave
Bug #729515 {Done: Mathieu Malaterre } [gdcm] java
compilation should target 1.5
Severity set to 'grave' from 'normal'
--
729515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729515
Debian Bug Tracking System
Contact ow...@bugs.debian.org wit
Processing control commands:
> severity -1 serious
Bug #729748 {Done: Mathieu Malaterre } [gdcm] Fwd: Comments
regarding gdcm_2.4.0-1_amd64.changes
Severity set to 'serious' from 'important'
--
729748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729748
Debian Bug Tracking System
Contact ow
On 12 December 2013 21:29, Arturo Borrero Gonzalez
wrote:
>
> I am triying to fix #705023. I forked the main corosync packaging git
> repo and pushed a commit to mine.
>
I'm sorry,
I miss that the source package version you had in the git repo was
1.4.2-3, instead of the latest 2.3.0-1.
My patch
49 matches
Mail list logo
