Package: vim
Version: 1:7.0-035+1
Severity: serious
Vim has undeclared file conflict with vim-doc 1:6.3-071+1sarge1 on
/usr/share/doc/vim which breaks upgrades from sarge.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message dated Fri, 04 Aug 2006 22:47:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#208134: fixed in gnome-tasksel 0.9.7.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
On Sun, Jul 30, 2006 at 02:41:23PM -0500, Alex Midgley wrote:
> I dug a little deeper, and it turns out that the form of the time
> command that Knights is using is correct by the xboard specification,
> and Crafty handles it correctly when it is in xboard mode.
>
> The problem appears to be the s
In addition to 381397 ("Upgrade of lprng fails in a 32-bit chroot
environment within Debian x86-64") I can confirm lprng 3.8.28-5 fails to
print at all. I'm printing via TCP/IP over Ethernet.
I have also reverted to lprng 3.8.28-4 to resolve this.
Regards,
Adam
--
To UNSUBSCRIBE, email to [EM
The following message is a courtesy copy of an article
that has been posted to gmane.linux.debian.devel.kernel as well.
On Fri, 4 Aug 2006 16:18:14 +0200, maximilian attems <[EMAIL PROTECTED]> said:
> hello Manoj and vorlon! rechecking the issues that were reported on
> #358397 and #362064
> 1
Processing commands for [EMAIL PROTECTED]:
> Tags 366565 + pending
Bug#366565: libalgorithm-diff-ruby: Please stop building ruby1.6 packages
Tags were: patch
Tags added: pending
> Thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Tags 366565 + pending
Thanks
I have prepared the package that fixes this bug, and I'm going to upload it
to the delayed queue (5 day delayed), since the severity of this bug was
raised currently.
The interdiff output is attached to this mail. As you can see, it's
basically the patch submitted by
On that subject, I tried to use aoss wrapper as a work around (still
OpenAL / ALUT should use ALSA when possible not OSS)
It worked with chromium - sound was playing (despite error/warning
messages) but it didn't worked with my simpe test program though.
Chromium:
-OpenAL
Package: libopenal0a
Version: 0.0.8-1
Severity: grave
ii libopenal0a 0.0.8-1
open /dev/[sound/]dsp: Device or resource busy
It seems that OpenAL try to open OSS driver even when ALSA works fine
(my other alsa apps work fine).
In example chromium game (it uses OpenAL) repo
Package: lprng
Version: 3.8.28-5
Severity: serious
Justification: fails to work at all
one of my patches botched usb printing (at least)
must roll back patches, this is a placemarker to stop it migrating
lprng 3.8.28-4 does nothave this problem
also check the prerm scripts
-- System Information
Your message dated Fri, 04 Aug 2006 15:47:22 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#375053: fixed in gnupg2 1.9.20-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 Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381448: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381404: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381448: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381404: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381399: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381399: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381404: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381399: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381399: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381394: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381408: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381394: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381448: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381404: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381404: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381408: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381394: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381448: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381408: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381408: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381448: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381399: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381394: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381408: fixed in shadow 1:4.0.18.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 no
Your message dated Fri, 04 Aug 2006 15:17:15 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381394: fixed in shadow 1:4.0.18.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 no
hello
the problem is that start-stop-daemon can't start the server if the old
(shutting down) process is still running since it just allows one
instance
a simple solution is to copy the "start" section in the initscript and
rename it to "force-start", change the --pidfile $PIDFILE to --pidfile
/d
Package: avarice
Version: 2.4-2
Severity: grave
Tags: patch
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
avarice is linked with the shared version of libbfd, but the
binutils-dev says :
"Note that building Debian packages which depend on the shared libbfd
Your message dated Fri, 04 Aug 2006 13:47:24 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364262: fixed in debian-edu 0.805
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
Processing commands for [EMAIL PROTECTED]:
> tag 258174 + fixed
Bug#258174: db3(GNU/k*BSD): FTBFS: out of date libtool scripts
Tags were: patch
Tags added: fixed
> tag 357526 + fixed
Bug#357526: db3-doc: doc package is not DFSG-free
There were no tags set.
Tags added: fixed
> quit
Stopping proce
Processing commands for [EMAIL PROTECTED]:
> tag 379265 + fixed
Bug#379265: FTBFS: needs an update for new ghc6
Tags were: patch
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs data
Processing commands for [EMAIL PROTECTED]:
> severity 381483 wishlist
Bug#381483: adolc: FTBFS: gawkism/bashism
Severity set to `wishlist' from `serious'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator
I'm sorry, is this *not* a "fails to build in standard Debian build
environment" problem. This is a "fails to build in non-standard
environment in which awk is mawk instead of gawk" issue.
If it were the former, I the severity of "serious" would be
reasonable, and I would upload a fix immediately
Processing commands for [EMAIL PROTECTED]:
> retitle 381483 adolc: FTBFS: gawkism/bashism
Bug#381483: adolc: FTBFS: awk: not an option: --file=debian/move-READMEs.awk
Changed Bug title.
> tag 381483 patch
Bug#381483: adolc: FTBFS: gawkism/bashism
There were no tags set.
Tags added: patch
> thank
retitle 381483 adolc: FTBFS: gawkism/bashism
tag 381483 patch
thanks
--- adolc-1.10.1.orig/debian/rules
+++ adolc-1.10.1/debian/rules
@@ -65,8 +65,8 @@
DESTDIR=`pwd`/debian/tmp bindir=/usr/bin/adolc/additional
mkdir --parents
debian/libadolc-examples/usr/share/doc/libadolc-exampl
Package: ivmanVersion: 0.6.12-3Severity: graveJustification: renders package unusableThe package ivman don't install, ocurring the error "invoke-rc.d:initscript ivman, action "start" failed."Try to run command line ivman after that, but the command "ps aux | grepivman" don't return any ivman job ru
On Thu, Aug 03, 2006 at 10:40:09PM -0300, Margarita Manterola wrote:
> Hi!
>
> I've been working with a couple of friends (Damián Viano and Martín
> Ferrari), in trying to fix this bug. We've built perl in an hppa machine
> and use that build to test the following things.
>
> This line:
>
Package: adolc
Version: 1.10.1-1
Severity: serious
Hello,
There was a problem while autobuilding your package:
> Automatic build of adolc_1.10.1-1 on avidan by sbuild/i386 0.49
> Build started at 2006080
Processing commands for [EMAIL PROTECTED]:
> tag 381390 + fixed
Bug#381390: pyrite-publisher: can't open file '/usr/lib/python/compileall.py'
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administr
Package: aptitude
Version: 0.4.2-1
Severity: serious
Hello,
There was a problem while autobuilding your package:
> Automatic build of aptitude_0.4.2-1 on avidan by sbuild/i386 0.49
> Build started at 2006080
On Wed, 2 Aug 2006 21:37, Brian M. Carlson said:
> I am inclined to say that this is grave, but since gnupg tends to do
> memory allocation before it drops privileges, you might find that this
The allocation problem, which is overflow like
malloc(numbercontrolledbyuser+20), can only happen after
Package: initramfs-tools
Version: 0.73
Severity: grave
Justification: makes the package unsuitable for release in maintainer's opinion
After upgrading from testing (0.69b) to unstable (0.73), resuming from
hibernation no longer works -- it just boots as normal. Downgrading
fixes the issue.
-- Pac
Package: acl2
Version: 3.0.1-1
Severity: serious
Hi,
Your package is failing to build on amd64 with the following
error:
HARD ACL2 ERROR in RECORD-ERROR: An attempt was made to treat NIL
as a record of type REWRITE-RULE.
ACL2 Error in CERTIFY-BOOK: Evaluation aborted. See :DOC wet for
how y
Your message dated Fri, 04 Aug 2006 09:17:25 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#373926: fixed in nagios-plugins 1.4.3.0cvs.20060707-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
Processing commands for [EMAIL PROTECTED]:
> reassign 381448 passwd
Bug#381448: postgresql-common postinst error blocks postgresql-8.1 installation
Bug reassigned from package `postgresql-common' to `passwd'.
> severity 381448 serious
Bug#381448: postgresql-common postinst error blocks postgresql
Your message dated Fri, 04 Aug 2006 09:02:09 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381348: fixed in cpio 2.6-17
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 r
reassign 381448 passwd
severity 381448 serious
tags 381448 confirmed patch
merge 381448 381394
thanks
Hi Fidel,
Fidel Ramos [2006-08-04 16:12 +0200]:
> adduser: `/usr/sbin/useradd -d /var/lib/postgresql -g postgres -s /bin/bash
> -u 106 postgres'
Already known as #381394 and a handful of duplic
Processing commands for [EMAIL PROTECTED]:
> severity 369448 important
Bug#369448: [powerpc] failure in pre-inst script, package fails to install
Severity set to `important' from `grave'
> stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system admini
Processing commands for [EMAIL PROTECTED]:
> reassign 381406 libgdome2-cpp-smart-dev
Bug#381406: gdome2-xslt: FTBFS: ld: cannot find -lz
Bug reassigned from package `gdome2-xslt' to `libgdome2-cpp-smart-dev'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bu
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> severity 330214 important
Bug#330214: kernel-image-2.6.8-2-686: kernel panic when using QUEUE target with
iptables
Severity set to `important' from `critical'
>
End of message, stop
Processing commands for [EMAIL PROTECTED]:
> Tags 381122 + patch
Bug#381122: Bashism in /etc/cron.daily/apticron
There were no tags set.
Tags added: patch
> Thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian
Tags 381122 + patch
Thanks
The attached patch replace the $RANDOM and let bash internal functions
using external commands in coreutils.
--- debian/cron.daily 2006-06-16 11:05:37.0 -0300
+++ debian/rata.daily 2006-08-04 11:17:18.0 -0300
@@ -1,9 +1,9 @@
#!/bin/sh
RANGE=3600
-nu
severity 369448 important
stop
can you still reproduce your bug with newest 2.6.17 image from unstable?
if yes please post your /etc/kernel-img.conf
also did you read the following follow up to your bug report:
On Wed, 07 Jun 2006, Manoj Srivastava wrote:
> Hi,
>
> Looking at the logs,
Package: adonthell
Version: 0.3.4.cvs.20050813-2.1+b1
Severity: grave
Justification: renders package unusable
Hello,
$ /usr/games/adonthell wastesedge
Segmentation fault
Segfault a the end of the sound during the splash screen.
$ strace /usr/games/adonthell wastesedge
munmap(0xa760a000,
reassign 381406 libgdome2-cpp-smart-dev
thanks
On Fri, Aug 04, 2006 at 08:45:02AM +0200, Julien Danjou wrote:
> package: gdome2-xslt
> version: 0.0.7-4
> severity: serious
>
> hello,
>
> There was a problem while autobuilding your package:
> > g++ -g -Wall -O2 -o .libs/test main.o -lz -lm
> >
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> package libpam-smbpass libsmbclient libsmbclient-dev python-samba samba
> samba-common samba-dbg samba-doc samba-doc-pdf smbclient smbfs swat winbind
Ignoring bugs not assigned to: s
Hello,
On Mon, Jul 31, 2006 at 09:30:35AM +0530, Kapil Hari Paranjape wrote:
> tags 349674 upstream
> thanks
>
> Hello,
>
> As reported in Debian bug #349674 which can be seen at
>
> http://bugs.debian.org/349674
>
> Unison has problems when the file system is removed from under it.
>
>
Package: postgresql-common
Version: 58
Severity: grave
Justification: renders package unusable
I'm unable to install postgresql-8.1. The whole system is a fresh
install, the base system from etch netinstall beta 2 and then a complete
upgrade to sid. This isn't an update of installed postgresql pa
hello Manoj and vorlon!
rechecking the issues that were reported on #358397 and #362064
1) fails to install on read-only /boot
this is correct and not yet checked, boot is assumed rw.
we currently fail to check that, but non standard setup.
2) overwriting yaird generated image
only happened in s
Your message dated Fri, 4 Aug 2006 15:47:06 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Close #295736
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 reo
Processing commands for [EMAIL PROTECTED]:
> severity 381428 important
Bug#381428: cupsys: Device dialog does not how any entry
Severity set to `important' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(adminis
severity 381428 important
thanks
At Fri, 04 Aug 2006 13:25:37 +0200,
root wrote:
> Package: cupsys
> Version: 1.2.2-1
> Severity: grave
> Justification: renders package unusable
>
> While trying to add a printer, the dialog never presents a device
> selection, it stays empty. This way, I am not a
Processing commands for [EMAIL PROTECTED]:
> severity 381348 serious
Bug#381348: cpio build glitch breaks Unicode char handling
Severity set to `serious' from `important'
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(adminis
Your message dated Fri, 4 Aug 2006 14:54:10 +0200
with message-id <[EMAIL PROTECTED]>
and subject line duplicate bug
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 reo
Hi,
finally, there was the things answered by the release-team about the
future of oot-modules in etch I wanted to know.
So, I can prepare new ipw* oot-module packages next week.
Regards,
Daniel
--
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email: [EMAIL PROT
Kapil Hari Paranjape <[EMAIL PROTECTED]> wrote:
> I think I understand what you are saying:
>
> The problem is that changes in the Linux interface force you to ask
> Linux users to install the program setuid in order to be sure to test
> all the possible difficulties that may arise when writing a
Your message dated Fri, 04 Aug 2006 05:02:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380686: fixed in initramfs-tools 0.73b
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 Fri, 04 Aug 2006 05:02:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379359: fixed in kiwi 1.9.8-7
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 Fri, 04 Aug 2006 04:32:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381248: fixed in libsdl1.2 1.2.11-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
Processing commands for [EMAIL PROTECTED]:
> reopen 381404
Bug#381404: proftpd: fails to install (useradd bug?)
Bug reopened, originator not changed.
> reassign 381404 passwd
Bug#381404: proftpd: fails to install (useradd bug?)
Bug reassigned from package `proftpd' to `passwd'.
> severity 381404
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/06, Josselin Mouette <[EMAIL PROTECTED]> wrote:
Le vendredi 04 août 2006 à 15:03 +0700, Theppitak Karoonboonyanan a
écrit :
> > However, I don't quite understand about the circular
> > dependency problem. Could you give more info?
Currently,
Package: cupsys
Version: 1.2.2-1
Severity: grave
Justification: renders package unusable
While trying to add a printer, the dialog never presents a device
selection, it stays empty. This way, I am not able to add any printer.
The folder backend was missing first and I copied it in from
/usr/lib/cu
Em Thu, 3 Aug 2006 17:31:26 +0200
David Weinehall <[EMAIL PROTECTED]> escreveu:
> On Wed, Aug 02, 2006 at 11:18:41PM -0300, Gustavo Noronha Silva wrote:
> So it seems that this version works =)
Great =D, let me upload then!
--
Gustavo Noronha Silva <[EMAIL PROTECTED]>
http://people.debian.org/~
Your message dated Fri, 04 Aug 2006 03:02:54 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381098: fixed in ocp 0.1.10rc6-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 yo
Processing commands for [EMAIL PROTECTED]:
> severity 368967 serious
Bug#368967: RM: gcj-4.0 -- RoM; old gcj packages, replaced by gcj-4.1
Severity set to `serious' from `normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrato
Le vendredi 04 août 2006 à 15:03 +0700, Theppitak Karoonboonyanan a
écrit :
> > However, I don't quite understand about the circular
> > dependency problem. Could you give more info?
Currently, there is a circular dependency between libpango1.0-0 and
libpango1.0-common. This is why by chance your
Hi,
this was tagged pending already some time ago, and fixed since, but only
in experimental.
Is a fix for testing expected soon?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
> severity 381405 serious
Bug#381405: gcj-4.0: FTBFS: gnat-4.0 has no installation candidate
Severity set to `serious' from `wishlist'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Processing commands for [EMAIL PROTECTED]:
> reopen 381405
Bug#381405: gcj-4.0: FTBFS: gnat-4.0 has no installation candidate
Bug reopened, originator not changed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrato
reopen 381405
thanks
On Fri, Aug 04, 2006 at 09:44:47AM +0200, Matthias Klose wrote:
> this package is scheduled for removal.
Please, close bugs when the package is actually removed, not before.
--
Julien Danjou
.''`. Debian Developer
: :' : http://julien.danjou.info
`. `' http://people.debia
Processing commands for [EMAIL PROTECTED]:
> tags 381405 + wontfix
Bug#381405: gcj-4.0: FTBFS: gnat-4.0 has no installation candidate
There were no tags set.
Tags added: wontfix
> tags 381405 + pending
Bug#381405: gcj-4.0: FTBFS: gnat-4.0 has no installation candidate
Tags were: wontfix
Tags adde
On Fri, Aug 04, 2006 at 12:01:35AM +0200, Arjan Oosting wrote:
> tag 380132 patch
> thanks
>
> I have prepared a patch which solves the FTBFS. The patch is attached.
>
> Greetings Arjan
Thanks Arjan, but I already uploaded a fix for this bug (Looks
like its in unstable as I write).
cheers,
--
Your message dated Fri, 4 Aug 2006 10:25:16 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381264: Error: this program needs to be installed suid root
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
Hi there
This problem is consistently causing issues for me and numerous other people..
I don't really have much to add to this bug request, other than to consider
this a vote for "please look at this if you have some time - it'd be much
appreciated".
I know you guys have hundreds of other thing
Processing commands for [EMAIL PROTECTED]:
> tag 381394 patch
Bug#381394: postgresql-common fails to install at useradd command
Tags were: confirmed
Bug#381399: Subject: postgresql: postgresql can't be installed
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need a
tag 381394 patch
thanks
The attached patch should fix this problem by adding support for
passing group names to useradd's -g option.
--
Matt
--- src/useradd.c.orig 2006-08-04 00:55:19.0 -0700
+++ src/useradd.c 2006-08-04 00:58:07.0 -0700
@@ -206,11 +206,9 @@
char *
Processing commands for [EMAIL PROTECTED]:
> merge 381394 381408
Bug#381394: postgresql-common fails to install at useradd command
Bug#381408: useradd's -g option doesn't handle group names
Bug#381399: Subject: postgresql: postgresql can't be installed
Merged 381394 381399 381408.
> --
Stopping p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/06, Theppitak Karoonboonyanan <[EMAIL PROTECTED]> wrote:
However, I don't quite understand about the circular
dependency problem. Could you give more info?
Umm.. I have also replaced the hard-coded dependencies
with ${shlibs:Depends}, ${mis
On Fri, Aug 04, 2006 at 08:19:24AM +0200, Jan Wagner wrote:
> I recognised the problem first with 1.4.3. Dont know if earlier packages are
> effected. 1.4.3.0cvs.20060707-2 has the check_ldaps symlink in basic and
> standard, so sarge and etch are definetly effected.
assuming you mean sid and et
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/3/06, Josselin Mouette <[EMAIL PROTECTED]> wrote:
The pango-libthai package relies on pango-querymodules, but it doesn't
depend on libpango1.0-common. Currently, this package is pulled by
chance because of a circular dependency with libpango1.0
1 - 100 of 106 matches
Mail list logo
