On Thu, 2013-08-08 at 10:08 +1000, Aníbal Monsalve Salazar wrote:
I couldn't reproduce your test. See below what I get with your key
fingerprint.
You appear to have misunderstood my test. Your test involves a
hex-encoded version of my GPG fingerprint. My test involves the raw,
non-encoded
Package: mnemosyne
Version: 2.2.1-1
Justification: renders package unusable
Severity: grave
Dear Maintainer,
Mnemosyne fails at startup (it worked just fine yesterday).
I suppose that this problem is caused by python-matplotlib but as I lack
experience with python I can't really help.
Here is
logol.pl fails to compile with new version with error:
osallou@debiansid:~/Desktop/DEBIAN-MED/logol/logol-1.6.2.orig$ swipl -f
prolog/logol.pl
ERROR: Prolog initialisation failed:
ERROR: source_sink `library(dialect/assertions)' does not exist
I am investigating the root cause.
--
gpg key
On Thu, Aug 08, 2013 at 10:07:48AM +0200, Marco Nenciarini wrote:
I've almost done with repackaging it with modern debhelper and integrating
the two patch from bts. The only thing left is testing. I'll push the brand
new git repository on collab-maint later today, so if anyone wants to help
Package: filezilla
Severity: grave
Tags: security upstream patch
Hi,
the following vulnerabilities were published for filezilla.
CVE-2013-4206[0]:
buffer underrun in modmul can corrupt the heap
CVE-2013-4207[1]:
non-coprime values in DSA signatures can cause buffer overflow in modular
inverse
Your message dated Thu, 08 Aug 2013 09:03:56 +
with message-id e1v7m8s-0001hj...@franck.debian.org
and subject line Bug#718545: fixed in freecad 0.13.1830-dfsg-3
has caused the Debian Bug report #718545,
regarding freecad: Unavailable dependencies in testing and unstable.
to be marked as done.
Your message dated Thu, 08 Aug 2013 09:03:56 +
with message-id e1v7m8s-0001hd...@franck.debian.org
and subject line Bug#717034: fixed in freecad 0.13.1830-dfsg-3
has caused the Debian Bug report #717034,
regarding freecad: FTBFS against oce 0.12
to be marked as done.
This means that you claim
BTW, libsnack2 and libsnack2-alsa have been renamed to tcl-snack and
tcl-snack-alsa without any provides. So you need tcl-snack |
tcl-snack-alsa in the dependencies now.
--
bye,
pabs
http://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Re: Ansgar Burchardt 2013-08-07 5202018d.2030...@debian.org
Package: ftp.debian.org
X-Debbugs-Cc: Christoph Berg m...@debian.org
Please remove oftc-hybrid from the archive. It is licensed under the
GPL, but links OpenSSL (#485610). The package as already been removed
from testing in 2008
reassign 719025 gedit-plugins
severity 719025 important
found 719025 3.8.3-1
thanks
Am 08.08.2013 00:54, schrieb Christoph Anton Mitterer:
Hi Michael.
On Wed, 2013-08-07 at 23:54 +0200, Michael Biebl wrote:
I suspect this is a plugin specific issue.
Yep, you're right and it's multiedit :)
Processing commands for cont...@bugs.debian.org:
reassign 719025 gedit-plugins
Bug #719025 [gedit] gedit crashes when closing a tab/file
Bug reassigned from package 'gedit' to 'gedit-plugins'.
No longer marked as found in versions gedit/3.8.3-3.
Ignoring request to alter fixed versions of bug
Il 08/08/2013 12:08, Paul Wise ha scritto:
BTW, libsnack2 and libsnack2-alsa have been renamed to tcl-snack and
tcl-snack-alsa without any provides. So you need tcl-snack |
tcl-snack-alsa in the dependencies now.
Thank you very much for pointing at this. I did not yet notice it.
I just
Hello there
what about the timeline for fixing this bug?
we are running Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-48squeeze3)
and we have same problems on a productive server!
where i've to install the patch? on dom0 or/and on domU's?
which patch i should use?
Il 05/08/2013 13:27, Paul Wise ha scritto:
On Mon, 2013-08-05 at 12:20 +0200, Giulio Paci wrote:
If you want to sponsor it and you have time to do it, feel free to
upload it.
Please upload a source package based on the latest git to mentors. I've
no idea how to construct a source package
On Thu, 2013-08-08 at 13:46 +0200, rooter wrote:
Hello there
what about the timeline for fixing this bug?
we are running Linux version 2.6.32-5-xen-amd64 (Debian
2.6.32-48squeeze3) and we have same problems on a productive server!
where i've to install the patch? on dom0
Your message dated Thu, 08 Aug 2013 12:18:45 +
with message-id e1v7paz-0004si...@franck.debian.org
and subject line Bug#719030: fixed in logol 1.6.2-3
has caused the Debian Bug report #719030,
regarding logol: fails to build with new version of swi-prolog
to be marked as done.
This means that
On Thu, 2013-08-08 at 13:46 +0200, rooter wrote:
Hello there
what about the timeline for fixing this bug?
we are running Linux version 2.6.32-5-xen-amd64 (Debian
2.6.32-48squeeze3) and we have same problems on a productive server!
where i've to install the patch? on dom0
Your message dated Thu, 8 Aug 2013 14:35:32 +0200
with message-id 20130808123532.GB24942@loar
and subject line Fixed in 1.4.3-1
has caused the Debian Bug report #713154,
regarding ruby-sinatra: FTBFS: tests failed
to be marked as done.
This means that you claim that the problem has been dealt
Hi,
On Tue, Jul 30, 2013 at 12:27 AM, Oxan van Leeuwen
o...@oxanvanleeuwen.nl wrote:
This package is an old version of the python-irc package.
Indeed, this seems to be the case. However, I don't think it was
intentional. Upstream was renamed from irclib to irc, and I think
it's likely that it
Processing control commands:
block 718309 by -1
Bug #718309 [python-irclib] python-irclib: duplicate of python-irc
718309 was not blocked by any bugs.
718309 was not blocking any bugs.
Added blocking bug(s) of 718309: 719114
--
718309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718309
Processing control commands:
block 718309 by -1
Bug #718309 [python-irclib] python-irclib: duplicate of python-irc
718309 was blocked by: 719114
718309 was not blocking any bugs.
Added blocking bug(s) of 718309: 719115
--
718309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718309
719115:
Processing commands for cont...@bugs.debian.org:
block 718309 by 719113
Bug #718309 [python-irclib] python-irclib: duplicate of python-irc
718309 was blocked by: 719115 719114
718309 was not blocking any bugs.
Added blocking bug(s) of 718309: 719113
thanks
Stopping processing here.
Please
Thanks for the NMU, I just got around to seeing it.
Upstream was in the middle of a transition between lead developers and
there has been significant changes to the code base. I'm going to
upload a new version that will include some of your changes.
Some, however, have been dropped (e.g.,
Processing commands for cont...@bugs.debian.org:
# preparing to set usertags
unarchive 617931
Bug #617931 {Done: Anton Gladky gladky.an...@gmail.com} [gmsh] gmsh: multiple
licensing issues
Unarchived Bug 617931
unarchive 618696
Bug #618696 {Done: hazel...@debian.org (Adam C. Powell, IV)}
Your message dated Thu, 08 Aug 2013 15:18:07 +
with message-id e1v7ryz-00084d...@franck.debian.org
and subject line Bug#718454: fixed in arduino-mk 0.12.0-1
has caused the Debian Bug report #718454,
regarding arduino-mk: Doesn't work at all
to be marked as done.
This means that you claim that
Control: reopen -1
Control: notfixed -1 2.3.0~rc1-1
Control: found -1 2.3.0~rc1-1
Still fails:
Building initial module for 3.10-2-amd64
Error! Build of lttng-probe-lttng.ko failed for: 3.10-2-amd64 (x86_64)
Consult the make.log in the build directory
All modules were built successfully, so
] Error 2
| dpkg-buildpackage: error: debian/rules build gave error exit status 2
The full build log is available at
http://people.debian.org/~sramacher/logs/qutecsound_0.6.1-2_amd64-20130808-1735.log
Regards
--
Sebastian Ramacher
signature.asc
Description: Digital signature
Package: nvidia-legacy-96xx-kernel-dkms
Version: 96.43.23-5
Severity: grave
Building against linux-headers-3.10-2-amd64 version 3.10.5-1:
/var/lib/dkms/nvidia-legacy-96xx/96.43.23/build/nv.c:512:5: error: implicit
declaration of function 'create_proc_entry'
Processing control commands:
reopen -1
Bug #717165 {Done: Jon Bernard jbern...@debian.org} [lttng-modules-dkms]
lttng-modules-dkms: Fails to build against Linux 3.10-1
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need
Processing commands for cont...@bugs.debian.org:
tags 719125 + jessie sid
Bug #719125 [src:qutecsound] qutecsound: FTBFS: src/csoundengine.h:69:3: error:
'CsoundChannelListEntry' does not name a type
Added tag(s) sid and jessie.
thanks
Stopping processing here.
Please contact me if you need
Your message dated Thu, 08 Aug 2013 15:50:00 +
with message-id e1v7stq-0004qb...@franck.debian.org
and subject line Bug#712383: fixed in svnmailer 1.0.8-13
has caused the Debian Bug report #712383,
regarding svnmailer: crashes with python-subversion
to be marked as done.
This means that you
Note that this failure also occurs when trying to build the new upstream
version.
signature.asc
Description: signature
Processing commands for cont...@bugs.debian.org:
# usertags set, the following bugs may be archived back
archive 617931
Bug #617931 {Done: Anton Gladky gladky.an...@gmail.com} [gmsh] gmsh: multiple
licensing issues
archived 617931 to archive/31 (from 617931)
archive 618696
Bug #618696 {Done:
Processing control commands:
severity -1 grave
Bug #710125 [openvswitch] openvswitch: unable to compile kernel module with
linux-3.8
Severity set to 'grave' from 'important'
tag -1 jessie sid
Bug #710125 [openvswitch] openvswitch: unable to compile kernel module with
linux-3.8
Added tag(s)
Processing commands for cont...@bugs.debian.org:
severity 696751 grave
Bug #696751 [oss4-dkms] oss4-dkms: fails to build
Severity set to 'grave' from 'normal'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
696751:
On Thu, Aug 8, 2013 at 9:03 AM, Ben Hutchings b...@decadent.org.uk wrote:
Control: severity -1 grave
Control: tag -1 jessie sid
This is obviously grave, but not for stable.
Ben - I know that you were working on packaging 1.9. That should fix
this issue and then I think we probably can switch
Package: cloop-src
Version: 2.6.39.2-1
Severity: grave
Tags: jessie sid
This module needs to be updated for, at least, this API change:
https://git.kernel.org/linus/3dadecce20603aa380023c65e6f55f108fd5e952
It fails to build against 3.10.5 with these errors:
/usr/src/modules/cloop/cloop.c: In
On Wednesday 07 August 2013 22:13:49 you wrote:
For example, one fix that comes to mind is to change the line in the
first patch:
char* soundfont_paths =
/usr/share/sounds/sf2/TimGM6mb.sf2:/usr/share/sounds/sf2/FluidR3_GM.sf2;
to this:
char* soundfont_paths =
Package: device3dfx-source
Version: 2011.07.03-1
Severity: grave
Tags: jessie sid
This module failed to build using linux-headers-3.10-2-amd64 version
3.10.5-1:
make[2]: Entering directory `/usr/src/modules/device3dfx'
Missing /lib/modules/3.10-2-amd64/build/include/linux/version.h
Configure
Package: mga-vid-source
Version: 2.6.32-1
Severity: grave
This module failed to build using linux-headers-3.10-2-amd64 version
3.10.5-1, with the following error message:
/usr/src/modules/mga-vid/mga_vid.c:73:24: fatal error: asm/system.h: No such
file or directory
I don't believe this
Package: vpb-driver-source
Version: 4.2.55-1
Severity: grave
This module failed to build with linux-headers-3.10-2-amd64 version
3.10.5-1. The error messages include:
/usr/src/modules/vpb-driver/src/vtcore/vtcore_main.c: In function
'vtcore_init':
Package: nova-common
Version: 2013.1.2-3
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
2013/8/8 Dominique Dumont d...@debian.org:
On Wednesday 07 August 2013 22:13:49 you wrote:
For example, one fix that comes to mind is to change the line in the
first patch:
char* soundfont_paths =
/usr/share/sounds/sf2/TimGM6mb.sf2:/usr/share/sounds/sf2/FluidR3_GM.sf2;
to this:
char*
Am Mittwoch, den 07.08.2013, 13:40 +0100 schrieb Gianfranco Costamagna:
Package: docbook2x
Version: 0.8.8-8
Severity: serious
Dear Maintainer,
please consider upload of my package available on mentors [1], because
now docbook2x cannot be installed on sid anymore. I cannot
build/rebuild
This patch fixes this bug:
https://bugzilla.mozilla.org/attachment.cgi?id=685492action=diff
I confirmed this by patching (patch applies cleanly to the mozilla
subdir) and rebuilding icedove_17.0.7-1~deb7u1_amd64. Works fine now in
sawfish.
--
Steaphan [STEF-in] Greene
Software Engineer:
On Thu, Aug 08, 2013 at 09:29:18AM -0700, Jesse Gross wrote:
On Thu, Aug 8, 2013 at 9:03 AM, Ben Hutchings b...@decadent.org.uk wrote:
Control: severity -1 grave
Control: tag -1 jessie sid
This is obviously grave, but not for stable.
Ben - I know that you were working on packaging 1.9.
Your message dated Thu, 08 Aug 2013 19:48:11 +
with message-id e1v7wbv-0005e4...@franck.debian.org
and subject line Bug#713117: fixed in lua-penlight 1.2.1-1
has caused the Debian Bug report #713117,
regarding lua-penlight: FTBFS: build-dependency not installable: lua-ldoc
to be marked as
As the one who introduced that bug: please go ahead, your solution looks right
to me. ;-)
Von Samsung Mobile gesendet
Ursprüngliche Nachricht
Von: Manuel A. Fernandez Montecelo manuel.montez...@gmail.com
Datum:
An: Dominique Dumont d...@debian.org
Cc: Fabian Greffrath
On Aug 8, 2013 11:42 AM, Sebastian Ramacher sramac...@debian.org wrote:
Source: qutecsound
Version: 0.6.1-2
Severity: serious
Justification: FTBFS (but built successfully in the past)
qutecsound fails to build from source since csound 6.00 is available in
unstable
Yes, I am in the process
Your message dated Thu, 08 Aug 2013 21:03:55 +
with message-id e1v7xnd-aa...@franck.debian.org
and subject line Bug#719133: fixed in device3dfx 2013.08.08-1
has caused the Debian Bug report #719133,
regarding Fails to build against Linux 3.10
to be marked as done.
This means that you
Hi Daniel thanks for the fast and prompt answer.
Unfortunately I deleted the package because I wanted to upload a NMU version,
and for some reason the package didn't get published anymore on mentors.
I also tried to dcut the old package but also dcut file is still there.
Tomorrow morning I'll
Package: gxine
Version: 0.5.907-2
Severity: grave
Justification: renders package unusable
Hi,
please update gxine
Not installable, depends on libmozjs10d
FTBFS:
make[3]: Entering directory `/tmp/buildd/gxine-0.5.907/src'
CC console_output.o
In file included from console_output.h:24:0,
Control: tags -1 + pending
On 2013-08-09 08:25:15, Norbert Preining wrote:
Not installable, depends on libmozjs10d
FTBFS:
make[3]: Entering directory `/tmp/buildd/gxine-0.5.907/src'
CC console_output.o
In file included from console_output.h:24:0,
from
Processing control commands:
tags -1 + pending
Bug #719168 [gxine] gxine: ftbfs, not installable
Added tag(s) pending.
--
719168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to
Your message dated Fri, 09 Aug 2013 00:48:13 +
with message-id e1v7ash-0001nf...@franck.debian.org
and subject line Bug#714452: fixed in automake1.13 1:1.13.3-1.1
has caused the Debian Bug report #714452,
regarding automake1.13: FTBFS: There seems to be no Makefile in this directory.
to be
Source: opencolorio
Version: 1.0.8~dfsg0-1
Severity: serious
Justification: fails to build from source
Builds of opencolorio on kFreeBSD have been failing, because
ocioconvert is hitting undefined reference errors:
CMakeFiles/ocioconvert.dir/main.cpp.o:(.gcc_except_table+0x1ec): undefined
Source: opencolorio
Version: 1.0.8~dfsg0-1
Severity: serious
Justification: fails to build from source
Builds of opencolorio on non-x86 architectures have been failing
because it specifies the non-portable -msse2 flag:
cc1plus: error: unrecognized command line option '-msse2'
Please leave
Source: opencolorio
Version: 1.0.8~dfsg0-1
Severity: serious
Justification: fails to build from source
Builds of opencolorio nearly succeed on i386, but still fail because
the precise set of (mangled) symbol names differs somewhat from the
package's (amd64-based) expectations. Please account for
Source: owncloud-client
Version: 1.2.5+dfsg-1
Severity: serious
Justification: fails to build from source
Builds of owncloud-client in minimal environments geared for building
only its architecture-dependent binary packages (as on most
autobuilders) have been failing:
dh_sphinxdoc -a
Source: owncloud-client
Version: 1.2.5+dfsg-1
Severity: serious
Justification: fails to build from source
Builds of owncloud-client on autobuilders with python-sphinx already
installed (as on i386 and mips, for whatever reason) have been failing
too; per the backtrace, it looks like they somehow
60 matches
Mail list logo
