Your message dated Mon, 12 Nov 2007 07:32:16 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450631: fixed in koffice 1:1.6.3-4
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 message dated Mon, 12 Nov 2007 07:32:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450433: fixed in gfpoken 0.30-5
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 you
Your message dated Mon, 12 Nov 2007 07:32:17 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449197: fixed in nuapplet 2.0-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 you
hi again,
On Mon, Nov 12, 2007 at 08:15:26AM +0100, Michael Ablassmeier wrote:
> both par and libpar-perl do ship `/usr/share/man/man1/parldyn.1p.gz' but
s/par/libpar-packer-perl/ of course, sorry.
bye,
- michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscrib
Your message dated Mon, 12 Nov 2007 06:47:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#447543: fixed in gammu 1.14.0-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 now you
Your message dated Mon, 12 Nov 2007 06:47:06 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449119: fixed in gmobilemedia 0.4+dfsg-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 i
Package: libpar-packer-perl, libpar-perl
Severity: serious
Justification: policy violation
hi,
both par and libpar-perl do ship `/usr/share/man/man1/parldyn.1p.gz' but
neither conflict or add a diversion, thus fail to be installed in the same
environment:
> Unpacking libpar-packer-perl (from li
Package: par, libpar-packer-perl
Severity: serious
Justification: policy violation
hi,
both par and libpar-packer-perl do ship `/usr/bin/par' but neither conflict or
add a diversion, thus fail to be installed in the same environment:
> Unpacking libpar-packer-perl (from libpar-packer-perl_0.976
Your message dated Mon, 12 Nov 2007 05:22:21 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450477: fixed in ko.tex 0.1.0+20071012-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 i
Your message dated Mon, 12 Nov 2007 05:25:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450456: fixed in perl 5.8.8-12
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
Your message dated Mon, 12 Nov 2007 05:18:39 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#434671: fixed in gclcvs 2.7.0-79
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 Mon, 12 Nov 2007 05:24:23 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449539: fixed in mr 0.13
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 Mon, 12 Nov 2007 05:18:39 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#432003: fixed in gclcvs 2.7.0-79
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 Mon, 12 Nov 2007 05:18:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#440844: fixed in galculator 1.3.1-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 now
Your message dated Mon, 12 Nov 2007 05:25:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450456: fixed in perl 5.8.8-12
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
Your message dated Mon, 12 Nov 2007 05:24:37 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#446893: fixed in nifticlib 0.6-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 Mon, 12 Nov 2007 05:26:45 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380964: fixed in straw 0.27-0.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 now you
Your message dated Mon, 12 Nov 2007 05:18:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#440844: fixed in galculator 1.3.1-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 now
Your message dated Mon, 12 Nov 2007 05:21:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#443035: fixed in jruby1.0 1.0.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 now y
Your message dated Mon, 12 Nov 2007 05:24:23 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449539: fixed in mr 0.13
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 Mon, 12 Nov 2007 05:18:39 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449352: fixed in gclcvs 2.7.0-79
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 Mon, 12 Nov 2007 05:18:39 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#432341: fixed in gclcvs 2.7.0-79
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 Mon, 12 Nov 2007 05:18:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#440844: fixed in galculator 1.3.1-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 now
Your message dated Mon, 12 Nov 2007 05:27:46 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449165: fixed in zangband 1:2.7.5pre1-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
Your message dated Mon, 12 Nov 2007 05:26:33 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450466: fixed in sgf2dg 4.026-8
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 you
Your message dated Mon, 12 Nov 2007 05:26:51 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#448259: fixed in tcpreplay 3.2.3-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 now
Your message dated Mon, 12 Nov 2007 05:27:31 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450449: fixed in xmonad 0.4-5
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
Your message dated Mon, 12 Nov 2007 05:27:34 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450629: fixed in xpdf 3.02-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 your
Your message dated Mon, 12 Nov 2007 05:23:59 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450458: fixed in manderlbot 0.9.2-11
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 no
Your message dated Mon, 12 Nov 2007 05:17:17 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#447315: fixed in ax25-apps 0.0.6-15
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 message dated Mon, 12 Nov 2007 05:22:12 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450630: fixed in kdegraphics 4:3.5.8-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
Your message dated Mon, 12 Nov 2007 05:18:43 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449168: fixed in gdc-4.1 0.25-4.1.2-17d1
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 i
Your message dated Mon, 12 Nov 2007 05:26:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#448717: fixed in rt2500 1:1.1.0-b4+cvs20070924-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 c
Your message dated Mon, 12 Nov 2007 05:25:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449200: fixed in openssl 0.9.8g-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 y
Your message dated Mon, 12 Nov 2007 05:26:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#448715: fixed in rt2400 1.2.2+cvs20070911-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 i
Your message dated Mon, 12 Nov 2007 05:27:19 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449059: fixed in whereami 0.3.34
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 Mon, 12 Nov 2007 05:18:43 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449167: fixed in gdc-4.1 0.25-4.1.2-17d1
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 i
Your message dated Mon, 12 Nov 2007 05:23:20 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#448488: fixed in linux-2.6 2.6.22-6
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 message dated Mon, 12 Nov 2007 05:26:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#432533: fixed in rt2570 1.1.0+cvs20070927-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 i
Your message dated Mon, 12 Nov 2007 05:25:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449200: fixed in openssl 0.9.8g-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 y
Your message dated Mon, 12 Nov 2007 05:25:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#449200: fixed in openssl 0.9.8g-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 y
Your message dated Mon, 12 Nov 2007 05:26:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#432533: fixed in rt2570 1.1.0+cvs20070927-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 i
Your message dated Mon, 12 Nov 2007 05:25:56 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450659: fixed in python-django 0.97~svn6668-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
Your message dated Mon, 12 Nov 2007 05:26:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#448719: fixed in rt2570 1.1.0+cvs20070927-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#409767: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396574: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:19:24 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431986: fixed in hlatex-fonts 1.0-6
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 message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396574: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#409767: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#409767: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#429187: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#429979: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#429979: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#429979: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#409767: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427506: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396574: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#429979: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396574: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#429187: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#429187: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:22:53 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#429187: fixed in libnss-pgsql 1.4.0debian-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 i
Your message dated Mon, 12 Nov 2007 05:25:28 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#424817: fixed in php-html-template-it 1:1.2.1-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 ca
Your message dated Mon, 12 Nov 2007 05:25:55 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450659: fixed in python-django 0.96.1-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
Package: xscreensaver
Version: 5.03-3
Severity: serious
Tags: security
Justification: Security Hole - Unintended information disclosure
When xcompmgr is running, the fireworxx hack will display over the live screen
(including any changes post screen-lock). This does not occur when
xcompmgr is not
Package: libocamlnet-ssl-ocaml
Version: 2.2.8.1-1
Severity: grave
Tags: patch
Justification: renders package unusable
Hi !
While playing with the ssl_client.ml example, I ended up correcting two
issues:
* ssl_client.ml must use:
let cl_ctx = Ssl.create_context Ssl.TLSv1 Ssl.Client_con
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.9
> tags 448644 pending
Bug#448644: CVE-2007-5708 remote denial of service
Tags were: patch security
Tags added: pending
>
End of message, stopping processing here.
Please contact me if
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.10
> package rt2570-source
Ignoring bugs not assigned to: rt2570-source
> forcemerge 448720 432533
Bug#448720: rt2570-source: FTBFS with 2.6.22
Bug#432533: rt2570-source: fails to compil
Aurelien Jarno wrote:
Justin Pryzby a écrit :
On Sun, Nov 11, 2007 at 08:21:53PM +1100, Shaddy Baddah wrote:
Package: qemu
Version: 0.9.0+20070816-1
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
qemu is exiting with a Segmentation fault
Package: libgdal-ruby1.8
Version: 1.4.2-3
Severity: grave
Justification: renders package unusable
The libgdal-ruby1.8 package is empty on alpha and amd64. The problem
seems to be linking PIC and non-PIC code together. From the amd64
build log:
/usr/bin/ld: gdal_wrap.o: relocation R_X86_64_32 aga
Eddy wrote:
> For me this happens in a totally reproducible way. When is started it works,
> but
> after the first hide, the display is either black or gray.
>
> This makes imho the bug serious since the package is unusable.
Yes, you're right.
A CVS snapshot will be uploaded with urgency=high a
Thiemo Seufer wrote:
> Christian Holm Christensen wrote:
> [snip]
> > Just one question: Is it possible for you to try to build the packages
> > on mipsel?
>
> I can try, but right now the best mipsel machine I have set up is a
> puny 250 MHz machine. :-)
This fails due to a missing -lcurl, you
Justin Pryzby a écrit :
> On Sun, Nov 11, 2007 at 08:21:53PM +1100, Shaddy Baddah wrote:
>> Package: qemu
>> Version: 0.9.0+20070816-1
>> Severity: grave
>> Justification: renders package unusable
>>
>> *** Please type your report below this line ***
>> qemu is exiting with a Segmentation fault err
This just tells me that it's dual-licensed. Shouldn't this be asked at
debian-legal?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I too can confirm that libssl0.9.8_0.9.8g-3_i386.deb fixed the bug.
I noticed that I could use libssl0.9.8_0.9.8g-2_i386.deb, but only when I
compiled wpa_supplicant with -O0 and opened
http://hostap.epitest.fi/bugz/show_bug.cgi?id=245 (which I've closed now
with an actual fix in place).
Tha
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.10
> # does not FTBFS anymore
> close 441086 5.1.22rc-1
Bug#441086: mysql-dfsg-5.1_5.1.21beta-1(hppa/experimental): FTBFS: error: 'max'
was not declared in this scope
'close' is deprecat
# Automatically generated email from bts, devscripts version 2.10.10
# does not FTBFS anymore
close 441086 5.1.22rc-1
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message dated Sun, 11 Nov 2007 16:15:36 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#450838: initrd images for sparc64 f do not allow booting
machines
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for [EMAIL PROTECTED]:
> fixed 354005 0.7.15-1
Bug#354005: init.d script error
Bug marked as fixed in version 0.7.15-1.
> found 354005 0.7.14-2
Bug#354005: init.d script error
Bug marked as found in version 0.7.14-2.
> notfound 354005 0.7.14-1.2
Bug#354005: init.d script e
adobe illustrator cs3 - 69
alias studiotools 11.02 - 49
creative suite premium 2 - 149
roxio digitalmedia studio deluxe suite 7.0 - 49
ulead videostudio 11.0 plus - 39
macrovision installshield premier edition 2008 - 199
steinberg cubase sx 2.2.0.33 - 39
virtual pc 7.0 for mac - 49
type cheapxpso
Package: initramfs-tools
Version: 0.91b
Severity: critical
--- Please enter the report below this line. ---
When booting, many segmentation faults are encountered and then
an ash shell prompt is given. The log complains from not being able
to mount /dev/hda2 on /root, but within the shell executi
On Sun, Nov 11, 2007 at 08:21:53PM +1100, Shaddy Baddah wrote:
> Package: qemu
> Version: 0.9.0+20070816-1
> Severity: grave
> Justification: renders package unusable
>
> *** Please type your report below this line ***
> qemu is exiting with a Segmentation fault error immediately after
> passing it
Processing commands for [EMAIL PROTECTED]:
> severity 441126 minor
Bug#441126: gfpoken - FTBFS: montage: unable to open image
`/tmp/tmp.pFPMh17125/blender//0064.png': No such file or directory.
Severity set to `minor' from `serious'
> tags 450433 +pending
Bug#450433: gfpoken: FTBFS: libgnomevfs-
Lucas Nussbaum <[EMAIL PROTECTED]> wrote:
Hi,
> Built against audacious 1.3, so we are in the same case as #450438.
I think I have it ported to audacious 1.4, need to wait until
audacious is installable again to test that out.
JB.
--
Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PRO
Package: swfdec-mozilla
Version: uninstallable because depends on unavailable libswfdec0.5-2
Severity: grave
Justification: renders package unusable
Hi,
basically the subject says it all: on my system, for a loong time
swfdec-mozilla is uninstallable because it depends on libswfdec0.5-2
which is
On Sun, Nov 11, 2007 at 10:35:50 +0100, Alex Bihlmaier wrote:
> Hi there,
>
> David announced the upcoming upload of 1:7.3+4 to the Debian Archive 1
> week ago, unfortunately I am not able to find the package for download.
>
> My Sid is unusable for 1 week, that's sad. :(
>
See this mail:
http:
Hi there,
David announced the upcoming upload of 1:7.3+4 to the Debian Archive 1
week ago, unfortunately I am not able to find the package for download.
My Sid is unusable for 1 week, that's sad. :(
Please comment for download instructions, I tried with aptitude +
http://packages.debian.org
ty,
Package: qemu
Version: 0.9.0+20070816-1
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
qemu is exiting with a Segmentation fault error immediately after
passing it valid invokation arguments. Please find a cut and paste of
the problem below
88 matches
Mail list logo
