Le 04/05/2011 07:43, Jonathan Nieder a écrit :
> clone 625521 -1
> severity 625521 grave
> severity -1 important
> reassign -1 libc6 2.13-0exp1
> retitle -1 glibc: memcpy copies down on amd64
> tags -1 upstream patch fixed-upstream
> # sorry for the noise
> quit
>
> Jonathan Nieder wrote:
>
>> So
Source: jsonbot
Version: 0.6.1.2-1
Severity: serious
Justification: missing source
Hi,
no source for ./jsb/upload/assets/{jquery.js,jquery-1.2.6.min.js} is
included in the package.
Note that jquery is already provided by libjs-jquery.
Regards,
Ansgar
--
To UNSUBSCRIBE, email to debian-bugs-
Your message dated Wed, 04 May 2011 06:20:30 +
with message-id
and subject line Bug#577057: fixed in libnss-db 2.2.3pre1-3.2
has caused the Debian Bug report #577057,
regarding CVE-2010-0826: allows local users to obtain sensitive information via
a symlink attack involving a setgid or setuid
Your message dated Wed, 04 May 2011 06:20:30 +
with message-id
and subject line Bug#548484: fixed in libnss-db 2.2.3pre1-3.2
has caused the Debian Bug report #548484,
regarding libnss-db: please use newer bdb
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Wed, 04 May 2011 06:20:30 +
with message-id
and subject line Bug#548484: fixed in libnss-db 2.2.3pre1-3.2
has caused the Debian Bug report #548484,
regarding Still uses db4.6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Your message dated Wed, 04 May 2011 06:05:07 +
with message-id
and subject line Bug#625472: fixed in expeyes 1.0.3-2
has caused the Debian Bug report #625472,
regarding expeyes-doc-en and expeyes-doc: error when trying to install together
to be marked as done.
This means that you claim that t
On Tue, 03 May 2011, Julien Lavergne wrote:
> Btw, I understood that I need to keep the Replaces: libimobiledevice2 in
> libimobiledevice2, right ? Because without it, there will be a error
> when the upgrade will happen ?
Hum, typo I guess. You need "Replaces: libimobiledevice1" in
libimobiledevi
Hello Ralf,
thank you for your quick feedback!
I just uploaded a new revision to fix this bug.
The hardware implementing expEYES can be assembled anywhere as per the
free license of the design. It is currently made by Indian companies,
and will be available through Hackable Devices soon.
Please
Processing commands for cont...@bugs.debian.org:
> clone 625521 -1
Bug#625521: causes segfault in Xorg
Bug 625521 cloned as bug 625522.
> severity 625521 grave
Bug #625521 [xserver-xorg-core] causes segfault in Xorg
Severity set to 'grave' from 'critical'
> severity -1 important
Bug #625522 [xse
clone 625521 -1
severity 625521 grave
severity -1 important
reassign -1 libc6 2.13-0exp1
retitle -1 glibc: memcpy copies down on amd64
tags -1 upstream patch fixed-upstream
# sorry for the noise
quit
Jonathan Nieder wrote:
> Sounds like http://sourceware.org/bugzilla/show_bug.cgi?id=12518
> which
On Wed, May 04, 2011 at 12:10:48AM -0500, Jonathan Nieder wrote:
> Sounds like http://sourceware.org/bugzilla/show_bug.cgi?id=12518
> which is fixed (sort of) by commit 0354e355 (2011-04-01).
Oh my word. So glibc 2.13 breaks random binaries that happened to
incorrectly use memcpy() instead of me
Processing commands for cont...@bugs.debian.org:
> reassign 625521 xserver-xorg-core 2:1.10.1-2
Bug #625521 [libc6] causes segfault in Xorg
Bug reassigned from package 'libc6' to 'xserver-xorg-core'.
Bug No longer marked as found in versions eglibc/2.13-2.
Bug #625521 [xserver-xorg-core] causes se
reassign 625521 xserver-xorg-core 2:1.10.1-2
quit
Hi,
Steve M. Robbins wrote:
> Xorg now segfaults, with the following in the Xorg.0.log:
>
> Program received signal SIGSEGV, Segmentation fault.
> __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:153
> 153 ../sysdeps/x86_64/mul
Processing commands for cont...@bugs.debian.org:
> block 622279 with 553930 553961 621932 605839 577321 614498
Bug #622279 [release.debian.org] transition: python-defaults
Was blocked by: 624810 616364 624824 623165 624901 624740 621993 614619 622966
618094 622978 623578 606681 624889 622976 6229
On Wed, May 04, 2011 at 06:43:54AM +0200, Aurelien Jarno wrote:
> Which versions of xorg* packages are you using? Which hardware is that?
> Can you attach your full Xorg.0.log?
The installed packages are below.
It's a radeon card (full details in attached log).
Log attached.
Thanks,
-Steve
ii
On Tue, May 03, 2011 at 11:27:08PM -0500, Steve M. Robbins wrote:
> Package: libc6
> Version: 2.13-2
> Severity: critical
>
> Xorg now segfaults, with the following in the Xorg.0.log:
>
> Program received signal SIGSEGV, Segmentation fault.
> __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcp
Your message dated Wed, 04 May 2011 04:32:31 +
with message-id
and subject line Bug#625183: fixed in bochs 2.4.6-2
has caused the Debian Bug report #625183,
regarding bochs: FTBFS: ./libtool: 1: finalize_command+= : not found
to be marked as done.
This means that you claim that the problem ha
Package: libc6
Version: 2.13-2
Severity: critical
Xorg now segfaults, with the following in the Xorg.0.log:
Program received signal SIGSEGV, Segmentation fault.
__memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:153
153 ../sysdeps/x86_64/multiarch/memcpy-ssse3.S: No such file or
Your message dated Wed, 04 May 2011 04:18:23 +
with message-id
and subject line Bug#624974: fixed in xserver-xorg-input-aiptek 1:1.4.0-1
has caused the Debian Bug report #624974,
regarding xserver-xorg-input-aiptek: FTBFS: ../../src/xf86Aiptek.h:362:5:
error: unknown type name 'LocalDevicePtr
Andreas Rottmann writes:
> AFAICS, guile-1.6 received no .la removal bug, but, unless there are
> really packages build-depending on guile-1.6 which install .la files
> referencing libguile.la, this bug should have been filed on guile-1.6
> instead. The current scan result show this line regardi
Your message dated Wed, 04 May 2011 00:47:04 +
with message-id
and subject line Bug#624920: fixed in xserver-xorg-input-void 1:1.3.1-3
has caused the Debian Bug report #624920,
regarding xserver-xorg-input-void: FTBFS: ../../src/void.c:244:6: error: too
few arguments to function 'InitValuator
user debian-...@lists.debian.org
usertags 616296 = ftbfs-gcc-4.6 ftbfs-werror
severity 616296 important
# a bug is a bug
tags 625312 - wheezy sid
tags 625312 + upstream
merge 616296 625312
tags 616296 + patch
quit
Matthias Klose wrote:
> This package builds with -Werror, and GCC 4.6 triggers new
Processing commands for cont...@bugs.debian.org:
> user debian-...@lists.debian.org
Setting user to debian-...@lists.debian.org (was jrnie...@gmail.com).
> usertags 616296 = ftbfs-gcc-4.6 ftbfs-werror
Bug#616296: btrfs-tools: will FTBFS with gcc-4.6
Usertags were: ftbfs-gcc-4.6.
Usertags are now:
Your message dated Tue, 03 May 2011 23:05:08 +
with message-id
and subject line Bug#622980: fixed in swig2.0 2.0.3-2
has caused the Debian Bug report #622980,
regarding swig: wrapper does not compile with python 3.2
to be marked as done.
This means that you claim that the problem has been dea
Hi all,
the bug is already fixed and the patch have been merged upstream. I'm just
waiting for my sponsor to upload the package which shouldn't take long.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.deb
Your message dated Tue, 03 May 2011 22:09:32 +
with message-id
and subject line Bug#625484: fixed in db4.8 4.8.30-8
has caused the Debian Bug report #625484,
regarding libdb4.8: 'Build signature doesn't match environment' in 4.8.30-6
to be marked as done.
This means that you claim that the pr
I think this one got fixed somewhere along the way. At least building 2.0.0
with a build-dep on binutils-gold works.
Beside that I'm of course happy that we've seen so many mails to d-d-a and
elsewhere telling us that using gold is now a release goal. (I spare it out
to CC doko because I doubt he'
Your message dated Tue, 03 May 2011 21:42:31 +
with message-id
and subject line Bug#625489: fixed in s3d 0.2.2-2
has caused the Debian Bug report #625489,
regarding s3d-doc: error when trying to install together with other s3d packages
to be marked as done.
This means that you claim that the
Your message dated Tue, 03 May 2011 21:44:16 +
with message-id
and subject line Bug#625097: fixed in spring 0.82.7.1+dfsg1-3
has caused the Debian Bug report #625097,
regarding spring: FTBFS: AAStar.h:70:43: error: 'NULL' was not declared in this
scope
to be marked as done.
This means that y
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding libqwt: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding albumshaper: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not
name a type
to be marked as done.
This means tha
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding kseg: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you c
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding ike: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you cl
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding extcalc: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name
a type
to be marked as done.
This means that yo
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding ttfm: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you c
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding unixodbc: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name
a type
to be marked as done.
This means that y
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding qt-x11-free: FTBFS: ../include/qvaluelist.h:91:13: error: 'ptrdiff_t'
does not name a type
to be marked as done.
Thi
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding ihu: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you cl
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding turqstat: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name
a type
to be marked as done.
This means that y
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding qgfe: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you c
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding polymer: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name
a type
to be marked as done.
This means that yo
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding k3dsurf: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name
a type
to be marked as done.
This means that yo
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding poppler: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name
a type
to be marked as done.
This means that yo
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding linamc: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding pfstools: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name
a type
to be marked as done.
This means that y
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding muse: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you c
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding webxml: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding libqglviewer: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not
name a type
to be marked as done.
This means th
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding unixcw: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding qwt: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you cl
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding callgit: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name
a type
to be marked as done.
This means that yo
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding freecycle: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not
name a type
to be marked as done.
This means that
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding biblememorizer: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does
not name a type
to be marked as done.
This means
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding qtdmm: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding sqlitebrowser: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not
name a type
to be marked as done.
This means t
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding qtodo: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding zsafe: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding dvbcut: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding qtstalker: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not
name a type
to be marked as done.
This means that
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding engauge-digitizer: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does
not name a type
to be marked as done.
This mea
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding qps: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you cl
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding icomlib: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name
a type
to be marked as done.
This means that yo
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding xxdiff: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding qimhangul: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not
name a type
to be marked as done.
This means that
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding alsa-tools: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not
name a type
to be marked as done.
This means that
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding xdrawchem: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not
name a type
to be marked as done.
This means that
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding qcad: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you c
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding bouml: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding dares: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding esvn: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a
type
to be marked as done.
This means that you c
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding mypasswordsafe: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does
not name a type
to be marked as done.
This means
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding qscintilla: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not
name a type
to be marked as done.
This means that
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding scim-bridge: FTBFS: qvaluelist.h:91:13: error: 'ptrdiff_t' does not
name a type
to be marked as done.
This means tha
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding libqt3-headers: use of ptrdiff_t without qualification/include
to be marked as done.
This means that you claim that t
Your message dated Tue, 03 May 2011 21:42:04 +
with message-id
and subject line Bug#611255: fixed in qt-x11-free 3:3.3.8b-8
has caused the Debian Bug report #611255,
regarding GCC 4.6 fix for Qt 3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Tue, 03 May 2011 21:39:54 +
with message-id
and subject line Bug#596310: fixed in libtuxcap 1.4.0.dfsg2-1.2
has caused the Debian Bug report #596310,
regarding libtuxcap: python2.5-dev used as build-dependency, not python-dev or
python2.6-dev
to be marked as done.
This mea
On Sun, 2011-04-17 at 21:08 +0200, Patrick Matthäi wrote:
>
> > Now that squeeze is released I should really start that transition...
> >
> > Unfortunately, the diff of r12620 does not apply to swig 2.0.3 as it
> > depends on a bunch of other changes.
>
> Packaging a VCS snapshot of swig2.0? :)
Aurelien Jarno wrote:
> Given I am out of idea, I probably ask stupid questions... Could you
> please dump your /proc/cpuinfo ?
No problem; thanks for working on this. In the meantime I am installing
sid (slowly) in a vm.
$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
c
On Tue, May 03, 2011 at 02:55:47PM -0500, Jonathan Nieder wrote:
> Aurelien Jarno wrote:
> > On Tue, May 03, 2011 at 02:49:04PM -0500, Jonathan Nieder wrote:
> >> Aurelien Jarno wrote:
>
> >>> Have you installed any icedove extension, as a Debian package or
> >>> manually?
> >>
> >> Yes. Order of
Package: s3d-doc
Version: s3d-doc/0.2.2-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Date: 2011-05-03
Architecture: amd64
Distribution: sid
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependenc
There's something seriously broken in the Berkeley DB build system,
because it got broken by --enable-test vs --disable-test. I'm going to
report that upstream.
So even it's seems as a waste of CPU time, I have to build the
packages with --enable-tcl (because that's the dependency of
--enable-test
Your message dated Tue, 03 May 2011 19:58:49 +
with message-id
and subject line Bug#605296: fixed in olsrd 0.6.1-1
has caused the Debian Bug report #605296,
regarding olsrd 0.5.6.r7 doesn't work with kernels >= 2.6.31
to be marked as done.
This means that you claim that the problem has been d
Processing commands for cont...@bugs.debian.org:
> tags 553930 + pending
Bug #553930 [src:aubio] FTBFS with binutils-gold
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
553930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553930
Debian B
Aurelien Jarno wrote:
> On Tue, May 03, 2011 at 02:49:04PM -0500, Jonathan Nieder wrote:
>> Aurelien Jarno wrote:
>>> Have you installed any icedove extension, as a Debian package or
>>> manually?
>>
>> Yes. Order of events:
>>
>> 1. Installed icedove to try it out. Failed as described in this
On Tue, May 03, 2011 at 02:49:04PM -0500, Jonathan Nieder wrote:
> Aurelien Jarno wrote:
>
> > Have you installed any icedove extension, as a Debian package or
> > manually?
>
> Yes. Order of events:
>
> 1. Installed icedove to try it out. Failed as described in this bug.
> 2. Downgraded lib
Aurelien Jarno wrote:
> Have you installed any icedove extension, as a Debian package or
> manually?
Yes. Order of events:
1. Installed icedove to try it out. Failed as described in this bug.
2. Downgraded libc6 to 2.11.x. icedove worked!
3. Upgraded libc6 to 2.13.x again. icedove still w
On Tue, May 03, 2011 at 02:16:36PM -0500, Jonathan Nieder wrote:
> Aurelien Jarno wrote:
>
> >>> zlib1g1:1.2.5.dfsg-1
> >
> > Can you try do downgrade this one? There have been plenty of issue with
> > versions from experimental, though they don't match the error message.
>
> Gladly. Dow
Your message dated Tue, 03 May 2011 21:49:33 +0300
with message-id <877ha7liv6@whisper.part.iki.fi>
and subject line FTBFS with binutils-gold
has caused the Debian Bug report #554797,
regarding FTBFS with binutils-gold
to be marked as done.
This means that you claim that the problem has been d
Your message dated Tue, 03 May 2011 16:19:23 -0300
with message-id <87y62nlhhg@convex-new.cs.unb.ca>
and subject line Fixed in 5.1.1+dfsg1-1
has caused the Debian Bug report #599960,
regarding plt-scheme: FTBFS on mipsel: [install-cgc] Error 1
to be marked as done.
This means that you claim th
Your message dated Tue, 03 May 2011 16:19:23 -0300
with message-id <87y62nlhhg@convex-new.cs.unb.ca>
and subject line Fixed in 5.1.1+dfsg1-1
has caused the Debian Bug report #599960,
regarding plt-scheme: FTBFS on mips: setup-plt: bootstrapping from source...
to be marked as done.
This means t
Aurelien Jarno wrote:
>>> zlib1g1:1.2.5.dfsg-1
>
> Can you try do downgrade this one? There have been plenty of issue with
> versions from experimental, though they don't match the error message.
Gladly. Downgraded to 1:1.2.3.4.dfsg-3. No change, alas.
> Also that might sound stupid, b
Package: libdb4.8
Version: 4.8.30-4
Severity: critical
Justification: breaks the whole system
When upgrading libdb4.8 from version 4.8.30-4 to 4.8.30-6 slapd fails to start.
Executing
e.g. slapcat returns the following error:
--- BEGIN ---
# slapcat
bdb(dc=blankersfamily,dc=com): Build signatur
Hello, the same problem happens in conjuntion with expeyes-doc-fr:
dpkg: error processing /var/cache/apt/archives/expeyes-doc-fr_1.0.3-1_all.deb
(--unpack):
trying to overwrite '/usr/share/expeyes/doc/fr-eyes.pdf', which is also in
package expeyes-doc 1.0.1-1
configured to not write apport repo
Your message dated Tue, 03 May 2011 19:06:08 +
with message-id
and subject line Bug#625165: fixed in m-tx 0.60d-2
has caused the Debian Bug report #625165,
regarding m-tx: FTBFS: cp: cannot stat `doc/mtxdoc.pdf': No such file or
directory
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> tags 624952 + pending fixed-upstream patch
Bug #624952 [src:gnome-chemistry-utils] gnome-chemistry-utils: FTBFS:
fragment-residue.cc:73:95: error: passing 'const gcp::Document' as 'this'
argument of 'void gcp::Document::SaveResidue(const gcp::Re
Processing commands for cont...@bugs.debian.org:
> # Incorrect maintainer adddress is a "must" violation of Policy 3.3
> severity 584568 serious
Bug #584568 [src:pydirector] pydirector: typo in the maintainer e-mail
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Pl
On Tue, May 03, 2011 at 09:02:19AM +0200, Sebastian Bremicker wrote:
> Hi,
>
> I don't see my previous mail in the sent folder and also forgot to cc
> the bugtracker, so here I go again:
>
> > > A far fetched thought maybe, but me using mozilla.debian.net's
> > > experimental iceweasel (v5 as of
On Mon, May 02, 2011 at 04:13:47PM -0500, Jonathan Nieder wrote:
> Sebastian Bremicker wrote:
> > Hi Jonathan,
>
> >> Could you uninstall and reinstall icedove and check?
> >
> > yes, I'm sorry, but it is running flawlessy here. I also
> > purged .icedove from my homedirectory prior to reinstall (
Your message dated Tue, 03 May 2011 18:51:21 +
with message-id
and subject line Bug#556482: fixed in sysprof 1.0.12-5
has caused the Debian Bug report #556482,
regarding FTBFS with binutils-gold
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Processing commands for cont...@bugs.debian.org:
> tags 625061 pending
Bug #625061 [src:enblend-enfuse] enblend-enfuse: FTBFS against boost 1.46.1
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
625061: http://bugs.debian.org/cgi-bin/bugrepor
1 - 100 of 191 matches
Mail list logo
