Hello,
I don't manage to play the 64/Scaar.aac either, while 32/Scaar.aac works
fine (tested with faad: totem and vlc). How was this file generated from
the real audio ?
Regards,
--
Clément
Processing commands for [EMAIL PROTECTED]:
> tags 360479 + help
Bug#360479: steghide: FTBFS: error: 'VERSION' was not declared in this scope
There were no tags set.
Tags added: help
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administr
tags 360479 + help
thanks
Hi
So how can you explain that it has been built on
alpha amd64 arm hppa hurd-i386 i386 ia64 kfreebsd-i386 mips mipsel powerpc s390
sparc
with a previous version of g++ then?
Okay now I'll explain why I think this is a fault in g++:
The file is built with:
g++ -DHAVE_
Hi,
Jarno Elonen wrote:
> > 2) the default *is* 4.0. since months.
>
> Yes, however, OOo doesn't seems to be compiled with it yet.
wrong. It is. We use g++ 4.0. Since it became default.
> > > How about CPPUHELPERLIB? Will libuno_cppuhelpergcc4 appear automatically
> > > once OOo is rebuilt with
Package: argouml
Version: 0.19.6-2
Severity: serious
Tags: patch
When building 'argouml' on unstable, I get the following error:
Building argouml unstable main amd64...
Reading package lists...
Building dependency tree...
E: Package mime-codecs has no installation candidate
E: Failed to satisfy
Package: xorg-x11
Version: 6.9.0.dfsg.1-5
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of xorg-x11_6.9.0.dfsg.1-5 on ball by sbuild/mips 85
> Build started at 20060403-0041
[...]
> ** Using build dependencies supplied by package:
> Build-Depends
Package: ivtv-source
Version: 0.6.1-1
Severity: serious
The ivtv drivers require non-free (and non-distributable) firmware in
order to run. See http://ivtvdriver.org/index.php/Firmware . Thus, the
ivtv drivers and utilities need to go in contrib, not main.
- Josh Triplett
signature.asc
Descr
Processing commands for [EMAIL PROTECTED]:
> severity 360420 serious
Bug#360420: nfs-kernel-server: fail to upgrade
Severity set to `serious'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs databa
Your message dated Sun, 02 Apr 2006 17:02:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#357222: fixed in libgtk2-ex-podviewer-perl 0.14-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Mon, 3 Apr 2006 02:08:36 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Your message dated Mon, 3 Apr 2006 02:08:36 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
severity 358061 important
tag 358061 - security
tag 358061 + upstream
forwarded 358061 http://bugs.mutt.org/2173
thanks
* Vincent Lefevre [Tue, 21 Mar 2006 02:19:20 +0100]:
> Mutt doesn't filter control characters, in particular the ^J and ^M,
> from headers, which can lead to unwanted behavior;
Your message dated Mon, 3 Apr 2006 02:08:36 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Processing commands for [EMAIL PROTECTED]:
> severity 358061 important
Bug#358061: mutt: Mutt should filter control characters from headers
Severity set to `important'.
> tag 358061 - security
Bug#358061: mutt: Mutt should filter control characters from headers
Tags were: security
Tags removed: s
> 2) the default *is* 4.0. since months.
Yes, however, OOo doesn't seems to be compiled with it yet.
Will the next uploaded version be? I.e. can I upload a fix now and say
"Depends: OpenOffice.org-common (>= 2.0.2-3)"?
> > How about CPPUHELPERLIB? Will libuno_cppuhelpergcc4 appear automatically
>
On Sun, 2006-04-02 at 19:03 +0200, Kurt Roeckx wrote:
> Note that _X_SENTINEL is defined in , and that
> Xlib.h does include that, the problem however seems to be that
> it's using ../../exports/include/X11/Xfuncproto.h, which doesn't
> have that.
>
Ah yes, that must explain it - it must be a di
reassign 360448 iptables
severity 360448 normal
merge 360448 355285
quit
On Sun, Apr 02, 2006 at 01:46:29PM +0200, Hansgeorg Schwibbe wrote:
> When the server is up, the mac rules are correct like this:
> debian:~# iptables
> -L
Processing commands for [EMAIL PROTECTED]:
> severity 360421 serious
Bug#360421: couple of file conflicts
Severity set to `serious'.
> tag 360421 pending
Bug#360421: couple of file conflicts
There were no tags set.
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you
Processing commands for [EMAIL PROTECTED]:
> reassign 360448 iptables
Bug#360448: iptables damages mac rules with kernel-image-2.4.27-3-k7
Bug reassigned from package `kernel-image-2.4.27-3-k7' to `iptables'.
> severity 360448 normal
Bug#360448: iptables damages mac rules with kernel-image-2.4.27
On Sun, Apr 02, 2006 at 01:52:10PM -0700, Steve Langasek wrote:
> reassign 360499 liballegro4.2-dev
> close 360499 2:4.2.0-4
> merge 360499 356861
> thanks
[...]
> Well, liquidwar build-depends on liballegro4.2-dev, so this would be bug
> #356861.
It build now, thanks Steve.
Kurt
--
To UNSUB
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349196: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349729: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#315115: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#315115: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349196: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349196: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349587: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#315718: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#315718: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349587: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349729: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349729: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349729: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349587: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349549: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349549: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349549: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349549: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349587: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 02 Apr 2006 15:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349196: fixed in sudo 1.6.8p12-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.16
> reassign 319666 ispell-tl
Bug#319666: aspell-tl: Needs repackaging for latest aspell
Bug reassigned from package `aspell-tl' to `ispell-tl'.
> merge 319666 360450
Bug#319666: aspell-
Package: mkvtoolnix
Version: 1.6.5-4
Severity: grave
Justification: causes non-serious data loss
Under amd64 gebnerated files are corrupted, here there are some samples:
http://chicca.ath.cx/mkvtoolnix/
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (9
Package: brutalchess
Version: 0.0.20060314cvs-1
Severity: grave
The first time I run brutal chess, the window is drawn but then it
segfaults:
Fatal signal: Segmentation Fault (SDL Parachute Deployed)
zsh: exit 245 /usr/games/brutalchess
-- System Information:
Debian Release: testing/unstable
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.16
> severity 360450 grave
Bug#360450: ispell-tl: FTBFS: Build depends on aspell-bin.
Severity set to `grave'.
> merge 319666 360450
Bug#319666: aspell-tl: Needs repackaging for latest as
Your message dated Sun, 2 Apr 2006 14:30:21 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#360449: iptables damages mac rules with
kernel-image-2.4.27-3-k7
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Sun, 02 Apr 2006 14:19:51 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#358184: fixed in latex-sanskrit 2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is n
On 31/03/2006 at 08:09 Bastian Blank wrote...
> Package: torcs
> Version: 1.2.4-1+b1
> Severity: serious
>
> There was an error while trying to autobuild your package:
>
Yes, this is due the split of openal libs, I'm preparing an upload for
this.
thanks,
Rudy
--
Rudy Godoy | 0x3433BD21 | ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[ please keep me in the loop. Hint: [EMAIL PROTECTED] does *not* go
to the submitter but only to the maintainer and the buglog ]
Hi.
Jarno Elonen wrote:
> > 4) You build with g++-3.3, you *sure* that it will work with the g++-4.0
> > built OOo and li
On Sun, 2006-04-02 at 16:56 +0530, Ganesan Rajagopal wrote:
> Joe Wreschnig wrote:
> > Package: python-ctypes
> > Version: 0.9.9.3-2
> > Severity: grave
> >
> > 0.9.9.3 uses a different API to load shared object files, which is the
> > primary purpose of the ctypes library. This version of the pac
> 4) You build with g++-3.3, you *sure* that it will work with the g++-4.0
> built OOo and libstlport4.6? I doubt that.
Mm.. Since OOo's debian/rules says GCC_VERSION='', I assume it uses default
GCC for autobuild, no? OO2-soikko's setup.mk currently contains stuff like
this:
SDK_GXX_INCLUDE_
reassign 360500 ftp.debian.org
severity 360500 normal
retitle 360500 RM: tcltk8.0-ja -- ROQA; uninstallable, obsolete version of
tcl/tk
thanks
On Sun, Apr 02, 2006 at 08:35:03PM +0200, Kurt Roeckx wrote:
> Package: tcltk8.0-ja
> Version: 8.0.4jp1.3-15
> Severity: serious
> Your package is curren
Processing commands for [EMAIL PROTECTED]:
> reassign 360500 ftp.debian.org
Bug#360500: tcltk8.0-ja: Build depends on removed libreadline4-dev.
Bug reassigned from package `tcltk8.0-ja' to `ftp.debian.org'.
> severity 360500 normal
Bug#360500: tcltk8.0-ja: Build depends on removed libreadline4-de
Processing commands for [EMAIL PROTECTED]:
> reassign 360499 liballegro4.2-dev
Bug#360499: liquidwar: FTBFS: ld: cannot find -lXcursor
Bug reassigned from package `liquidwar' to `liballegro4.2-dev'.
> close 360499 2:4.2.0-4
Bug#360499: liquidwar: FTBFS: ld: cannot find -lXcursor
'close' is deprec
reassign 360499 liballegro4.2-dev
close 360499 2:4.2.0-4
merge 360499 356861
thanks
On Sun, Apr 02, 2006 at 08:31:52PM +0200, Kurt Roeckx wrote:
> Package: liquidwar
> Version: 5.6.3-2
> Severity: serious
> Your pacakge is failing to build wiht the following error:
> Linking liquidwar (target=def
reassign 360479 steghide
thanks
Ola Lundqvist <[EMAIL PROTECTED]> writes:
> reassign 360479 g++
> thanks
>
> I have now looked over the code and can not possibly find out that
> this is a fault in the code.
Uhm, reassining bugs to gcc if you don't understand the issue is not
the way to go. Pleas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[ it would be nice if you could send mail also to me when you ask
something to me. thanks. hint: [EMAIL PROTECTED] only goes to the
*maintainer* and the buglog ]
Hi,
Jarno Elonen wrote:
> > you install the component via a uno package system-wide usin
Processing commands for [EMAIL PROTECTED]:
> reassign 360479 steghide
Bug#360479: steghide: FTBFS: error: 'VERSION' was not declared in this scope
Bug reassigned from package `g++' to `steghide'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking sy
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.16
> # no other applications have this problem; this looks like an application bug
> severity 360513 normal
Bug#360513: libgtk2.0-0: gtk application crashes eventually after upgrade on
t
Your message dated Sun, 2 Apr 2006 22:07:26 +0200
with message-id <[EMAIL PROTECTED]>
and subject line kerberos4 removed from Debian
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your respo
Your message dated Sun, 2 Apr 2006 22:06:35 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 22:07:26 +0200
with message-id <[EMAIL PROTECTED]>
and subject line kerberos4 removed from Debian
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your respo
Package: libgtk2.0-0
Version: 2.8.13-1
Severity: grave
Justification: renders package unusable
After a while, I upgraded the distro. Now my application crashes eventually
when idle. The only thing running is a timer which replaces a gtk tree model
associated with an gtktreeview; It used to work "
Your message dated Sun, 2 Apr 2006 22:06:35 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 22:07:26 +0200
with message-id <[EMAIL PROTECTED]>
and subject line kerberos4 removed from Debian
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your respo
Your message dated Sun, 2 Apr 2006 22:06:35 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 22:07:26 +0200
with message-id <[EMAIL PROTECTED]>
and subject line kerberos4 removed from Debian
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your respo
Your message dated Sun, 2 Apr 2006 21:44:16 +0200
with message-id <[EMAIL PROTECTED]>
and subject line thy removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reope
Your message dated Sun, 2 Apr 2006 21:48:49 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:44:16 +0200
with message-id <[EMAIL PROTECTED]>
and subject line thy removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reope
Your message dated Sun, 2 Apr 2006 21:38:29 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:47:53 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Renamed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:45:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
> you install the component via a uno package system-wide using unopkg.
> While this is the normal way this is to be done it doesn't reliably work
> on OOo upgrades. At least with the Wikipedia plugin for OOo I somethimes
> had to remove and register it again, otherwise I get errors.
Sometimes, bu
Your message dated Sun, 2 Apr 2006 21:49:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:45:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:47:51 +0200
with message-id <[EMAIL PROTECTED]>
and subject line renamed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:49:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
reassign 360479 g++
thanks
I have now looked over the code and can not possibly find out that this is
a fault in the code. If someone can tell me what the problem is then I can
accept it but this have worked before and VERSION tag is found in config.h
which is included. I have even tried to explic
Your message dated Sun, 2 Apr 2006 21:36:35 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:47:51 +0200
with message-id <[EMAIL PROTECTED]>
and subject line renamed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:49:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Processing commands for [EMAIL PROTECTED]:
> reassign 360479 g++
Bug#360479: steghide: FTBFS: error: 'VERSION' was not declared in this scope
Bug reassigned from package `steghide' to `g++'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Your message dated Sun, 2 Apr 2006 21:45:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:45:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:48:49 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:49:16 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:34:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:35:30 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:44:16 +0200
with message-id <[EMAIL PROTECTED]>
and subject line thy removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reope
Your message dated Sun, 2 Apr 2006 21:35:30 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:47:53 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Renamed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:47:53 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Renamed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
Your message dated Sun, 2 Apr 2006 21:31:35 +0200
with message-id <[EMAIL PROTECTED]>
and subject line db2 removed from the archive
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your respon
Your message dated Sun, 2 Apr 2006 21:31:35 +0200
with message-id <[EMAIL PROTECTED]>
and subject line db2 removed from the archive
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your respon
On Sun, Apr 02, 2006 at 08:35:05PM +0200, Ola Lundqvist wrote:
> Hi
>
> Please provide more information on the environment where it fail to build.
> * What compiler version?
> * What architecture?
This is current sid, and it breaks on atleast i386 and amd64.
This is with gcc-4.0 4.0.3-1.
For a f
Package: liquidwar
Version: 5.6.3-2
Severity: serious
Hi,
Your pacakge is failing to build wiht the following error:
Linking liquidwar (target=default, debug=no, static=no, asm=yes)
/usr/bin/ld: cannot find -lXcursor
PS: Could you please make it show the command lines when building
something. I
Package: tcltk8.0-ja
Version: 8.0.4jp1.3-15
Severity: serious
Hi,
Your package is currently using libreadline4 which has been
removed. Please change your build dependency to
libreadline5-dev.
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Conta
Hi
Please provide more information on the environment where it fail to build.
* What compiler version?
* What architecture?
Regards,
// Ola
On Sun, Apr 02, 2006 at 05:25:08PM +0200, Kurt Roeckx wrote:
> Package: steghide
> Version: 0.5.1-7
> Severity: serious
>
> Hi,
>
> Your package is faili
On Sun, Apr 02, 2006 at 03:15:00PM -0300, Gustavo R. Montesino wrote:
> On Sun, Apr 02, 2006 at 03:37:50PM +0200, Kurt Roeckx wrote:
> > Hi,
> >
> > I've just NMU'd it. Patch is attached.
> >
>
> Yay... thanks for NMUing a pending tagged bug with almost no warning...
> quite Debian style. Maybe
Your message dated Sun, 02 Apr 2006 11:17:17 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#360483: fixed in zeroc-ice 3.0.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
1 - 100 of 158 matches
Mail list logo
