tag 282147 patch
thanks
Hi,
attached you will find a patch that modifies update-inetd to use debconf
for interaction (and therefore non-interaction if non-interactive, with
reasonable defaults).
Submitters of the respective bugs, and maintainers, please review. I can
upload the fix if necessary.
reassign 392863 ftp.debian.org
retitle 392863 Please remove obsolete preview-latex package
thanks
Frank Küster <[EMAIL PROTECTED]> wrote:
> Hi Makoto, hi Davide,
>
> Bill Allombert <[EMAIL PROTECTED]> wrote:
>
>> Package: preview-latex
>> Version: 0.9.1-4
>> Severity: serious
>>
>> Hello Makoto,
Processing commands for [EMAIL PROTECTED]:
> reassign 392863 ftp.debian.org
Bug#392863: preview-latex: fails to install
Bug reassigned from package `preview-latex' to `ftp.debian.org'.
> retitle 392863 Please remove obsolete preview-latex package
Bug#392863: preview-latex: fails to install
Change
Processing commands for [EMAIL PROTECTED]:
> severity 396393 normal
Bug#396393: inkscape: No tight-fitting bounding box in EPS output
Severity set to `normal' from `grave'
> tags 396393 patch
Bug#396393: inkscape: No tight-fitting bounding box in EPS output
There were no tags set.
Tags added: pat
severity 396393 normal
tags 396393 patch
thanks
Emilio Jose Padron Gonzalez <[EMAIL PROTECTED]> wrote:
> Package: inkscape
> Version: 0.44.1-1
> Severity: grave
> Justification: renders package unusable
>
>
> EPS output seems to be broken.
Indeed. However, eps output is only one of a couple of
Package: ire-the-flat
Version: 0.91-1
Severity: grave
Justification: renders package unusable
While it loads, the program crashes. This is the console output.
$ ire-flat
IRE game runtime, Copyright (C) 2004 IT-HE Software
IRE Kernel version: 0.92
Build date: Mar 30 2006 at 04:38:00
IT-HE lib vers
Package: ire-rotj
Version: 1.02-5
Severity: grave
Justification: renders package unusable
After using the keyboard to choose one menu option, the program crashes.
The console output is below.
$ ire-rotj
IRE game runtime, Copyright (C) 2004 IT-HE Software
IRE Kernel version: 0.92
Build date: Mar 3
Your message dated Wed, 01 Nov 2006 05:50:53 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393619: fixed in varmon 1.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
Your message dated Wed, 01 Nov 2006 05:47:26 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396532: fixed in mlterm 2.9.3-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
Package: totem
Version: 2.16.2-2
Severity: serious
Justification: Policy 2.3
Totem copyright holders have allowed an exception to the GPL so Totem
may be distributed with GStreamer non-GPL plugins. However, this is not
stated in the debian/copyright file.
-- System Information:
Debian Release: 4
Your message dated Wed, 01 Nov 2006 04:47:17 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393021: fixed in mod-vhost-ldap 1.2.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
Processing commands for [EMAIL PROTECTED]:
> severity 396528 important
Bug#396528: hunspell: FTBFS on arm: 3 tests failed
Severity set to `important' from `serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrat
severity 396528 important
thanks
Frank Küster wrote:
> Strange that this has never been reported, but it seems hunspell never
> was built successfully on arm. I checked the last three build logs from
> http://buildd.debian.org/build.php?arch=arm&pkg=hunspell, and the
> failure always seems to be
Qzk9RDQgPUNDPUM1PUQ3Oj89?=
Date: Wed, 1 Nov 2006 12:20:01 -0060
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="koi8-r";
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4
OCA9QzM9QzE9RDI9QzU9Q0EhISE/PQA=?=
Date: Wed, 1 Nov 2006 12:22:26 -0060
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="koi8-r";
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Expres
PUQ0PUQxPUNEPUM5ID1EMz1EMj1DMT1DQyw/PQA=?=
Date: Wed, 1 Nov 2006 12:14:26 -0060
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="koi8-r";
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outloo
QT1DND1DNT1EQj1EOCw/PQA=?=
Date: Wed, 1 Nov 2006 12:17:47 -0330
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="koi8-r";
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2
Mj1DQz1EMT1DND1EOCw/PQA=?=
Date: Wed, 1 Nov 2006 12:19:49 -0060
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="koi8-r";
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4
OCA9QzM9QzE9RDI9QzU9Q0EhISE/PQA=?=
Date: Wed, 1 Nov 2006 12:21:47 -0060
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="koi8-r";
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Expres
QSA9Q0I9Q0Y9Q0U9Qzk9Q0U9RDksPz0=?=
Date: Wed, 1 Nov 2006 12:22:12 -0060
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="koi8-r";
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Expres
QT1DND1DNT1EQj1EOCw/PQA=?=
Date: Wed, 1 Nov 2006 12:14:09 +0300
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="koi8-r";
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3
Your message dated Wed, 01 Nov 2006 04:18:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#395416: fixed in evolution-data-server 1.8.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 cas
RDc9QzE9Q0M9Qzk9Q0M9QzEgPz0=?=
Date: Wed, 1 Nov 2006 12:35:05 -0480
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="koi8-r";
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.
On 11/1/06, Matthias Klose <[EMAIL PROTECTED]> wrote:
* Added suggest gdb-doc (closes: #392961)
This surely didn't remove the GFDL'ed texi files from the source as
done in the gdb source package.
Nope, I'll rectify that...
--
Håkan Ardö
OCA9QzM9QzE9RDI9QzU9Q0EhISE/PQA=?=
Date: Wed, 1 Nov 2006 12:19:49 -0060
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="koi8-r";
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Expres
QzU9Q0MgPUM1PUMyPUQxPUQ0PUQ4Pz8/LD89?=
Date: Wed, 1 Nov 2006 12:21:43 -0060
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="koi8-r";
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Ex
Processing commands for [EMAIL PROTECTED]:
> severity 368330 grave
Bug#368330: distmp3host does not start up (mknod: invalid mode)
Severity set to `grave' from `normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(adminis
QzU9Q0MgPUM1PUMyPUQxPUQ0PUQ4Pz8/LD89?=
Date: Wed, 1 Nov 2006 12:13:21 -0060
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="koi8-r";
reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Ex
Your message dated Wed, 01 Nov 2006 04:02:24 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#395416: fixed in evolution-data-server 1.6.3-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 cas
Processing commands for [EMAIL PROTECTED]:
> reopen 392961
Bug#392961: [NONFREE-DOC:GFDL] package contains non-free documentation
'reopen' is deprecated when a bug has been closed with a version;
use 'found' or 'submitter' as appropriate instead.
Bug reopened, originator not changed.
> thanks
Sto
Your message dated Wed, 01 Nov 2006 20:51:53 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393889: libapache2-mod-fastcgi uninstallable in sid due to
apache2 conflict
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been deal
reopen 392961
thanks
* Added suggest gdb-doc (closes: #392961)
This surely didn't remove the GFDL'ed texi files from the source as
done in the gdb source package.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: coco-doc
Version: 20060919-1
Severity: serious
This package includes two PDF files, UserManual.pdf and
DataStructures.pdf, without corresponding sources. According to
pdfinfo, the sources are Microsoft Word documents; this is not nice, but
it is definitely preferred to directly editing a
Processing commands for [EMAIL PROTECTED]:
> found 396323 1.36.2
Bug#396323: rpncalc - FTBFS: strip: Unable to recognise the format of the input
file
Bug marked as found in version 1.36.2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system a
Your message dated Wed, 1 Nov 2006 12:31:41 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixing version-tracking for already fixed-in-NMU 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 ca
p/usr/bin/rpncalc
> strip: Unable to recognise the format of the input file
> `/build/buildd/rpncalc-1.36.2/debian/tmp/usr/bin/rpncalc'
> make: *** [binary-arch] Error 1
> **
> Build finished at 20061101-015
Your message dated Wed, 1 Nov 2006 12:23:03 +0100
with message-id <[EMAIL PROTECTED]>
and subject line not RC anymore after sarge
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 responsi
Package: hunspell
Version: 1.1.4-3
Severity: serious
Strange that this has never been reported, but it seems hunspell never
was built successfully on arm. I checked the last three build logs from
http://buildd.debian.org/build.php?arch=arm&pkg=hunspell, and the
failure always seems to be the same
Package: mlterm
Version: 2.9.3-4
Severity: serious
Hi,
Your package is failing to build on amd64 with the following error:
gcc -Wall -g -O2 -I. -c kik_utmp_sysv.c -fPIC -DPIC -o .libs/kik_utmp_sysv.lo
kik_utmp_sysv.c: In function 'kik_utmp_new':
kik_utmp_sysv.c:123: error: incompatible types in
Your message dated Wed, 1 Nov 2006 12:28:35 +0100
with message-id <[EMAIL PROTECTED]>
and subject line marking done in the right version
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
Your message dated Wed, 1 Nov 2006 12:12:55 +0100
with message-id <[EMAIL PROTECTED]>
and subject line marked as done with right version
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
Your message dated Wed, 1 Nov 2006 12:14:12 +0100
with message-id <[EMAIL PROTECTED]>
and subject line marking as done
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 r
Your message dated Wed, 1 Nov 2006 12:03:09 +0100
with message-id <[EMAIL PROTECTED]>
and subject line marking fixed with right version
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 re
Your message dated Wed, 1 Nov 2006 11:58:55 +0100
with message-id <[EMAIL PROTECTED]>
and subject line marking done with right version
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 res
Processing commands for [EMAIL PROTECTED]:
> tags 392947 + etch-ignore
Bug#392947: jmpost: purging the package fails (mktexlsr unavailable)
There were no tags set.
Tags added: etch-ignore
> --
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system adminis
Your message dated Wed, 01 Nov 2006 02:47:14 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#394666: fixed in meta-gnustep 5.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 y
Processing commands for [EMAIL PROTECTED]:
> severity 396372 grave
Bug#396372: FTBFS: src/autoprofile.h:30:20: error: config.h: No such file or
directory
Severity set to `grave' from `serious'
> merge 394773 396372
Bug#394773: minor change needed for compatibility with gaim2.0.0beta4
Bug#396372:
On Oct 31, Francesco Poli <[EMAIL PROTECTED]> wrote:
> IMHO, DFSG#2 refers to source code, as is usually defined, that is to
> say, as in the GNU GPL v2.
No, it does not. As usual, you are just inventing new requirements which
are not specified by the DFSG.
> Deliberately obfuscated code is absol
Your message dated Wed, 01 Nov 2006 02:32:12 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390001: fixed in bigloo 2.8c-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 your
Processing commands for [EMAIL PROTECTED]:
> found 387089 20061027
Bug#387089: Certificate links must not be removed
Bug marked as found in version 20061027.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Deb
Your message dated Wed, 01 Nov 2006 02:32:12 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390001: fixed in bigloo 2.8c-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 your
Your message dated Wed, 1 Nov 2006 11:43:42 +0100
with message-id <[EMAIL PROTECTED]>
and subject line marking done with correct version
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
Your message dated Wed, 1 Nov 2006 11:32:15 +0100
with message-id <[EMAIL PROTECTED]>
and subject line marking correctly as versioned-done
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 Wed, 1 Nov 2006 11:32:15 +0100
with message-id <[EMAIL PROTECTED]>
and subject line marking correctly as versioned-done
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 Wed, 1 Nov 2006 11:32:15 +0100
with message-id <[EMAIL PROTECTED]>
and subject line marking correctly as versioned-done
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 Wed, 1 Nov 2006 11:39:34 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Closing with correct versions
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 Wed, 01 Nov 2006 02:32:22 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396258: fixed in wireshark 0.99.4-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
reopen 387089
thanks
I'm sorry to tell you, but this problem is not yet fixed.
Installed version of ca-certificates:
ii ca-certificates 20061027Common CA
Certificates PEM files
There should be a link, but isn't:
finlandia!joey(tty1):/etc/ssl/certs> l |grep luo
> Hi,
> I have the same problem: cups does not work any longer with my Epson C82
> USB printer. Here is what I see in /var/log/cups/error_log:
Er, how can you claim you have the same problem when your logs are totally
different?
> E [01/Nov/2006:09:11:54 +0100] PID 5051 (/usr/lib/cups/filter/ps
Processing commands for [EMAIL PROTECTED]:
> reopen 387089
Bug#387089: Certificate links must not be removed
'reopen' is deprecated when a bug has been closed with a version;
use 'found' or 'submitter' as appropriate instead.
Bug reopened, originator not changed.
> thanks
Stopping processing here
Package: meta-gnustep
Version: 5.1
Severity: normal
Tags: patch
Hi,
Attached is the diff for my meta-gnustep 5.2 NMU.
--
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint: D5AF 25FB 316B 53BB 08E7 F999 E544 DE07 9B7C 328D
diff -Nru /tmp/Vpa8dE27dM/meta-gnustep-5
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> reopen 389287
Bug#389287: Package built against libraries from experimental
'reopen' is deprecated when a bug has been closed with a version;
use 'found' or 'submitter' as appropriate
Hi,
My opinion on this matter was requested, so I'm documenting it here.
gst-ffmpeg suffers from a very similar problem, since it has an
embedded fork of ffmpeg. My understanding is that upstream needs more
than ffmpeg's offer in the first place, and also rewrote the build
completely
Your message dated Wed, 01 Nov 2006 02:02:12 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396459: fixed in libsdl1.2 1.2.11-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
severity 396418 normal
merge 396418 394838
quit
On Tue, Oct 31, 2006 at 05:57:29PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in etch, I discovered that your package
> failed to build on i386.
>
> I tried to build it several times to make sure the issue was not transient.
>
On Wed, Nov 01, 2006, Steve Langasek wrote:
> > * [2] SDL_syswm.h needs the X headers. I'm not sure whether this should be
> > fixed in libsdl1.2-dev or not; if it is, that could take care of about 1/3
> > to
> > 1/2 of the failures.
>
> Seems like a clear case of a bug in libsdl1.2-dev to me
Processing commands for [EMAIL PROTECTED]:
> severity 396418 normal
Bug#396418: cogito: FTBFS: failed tests
Severity set to `normal' from `serious'
> merge 396418 394838
Bug#394838: cogito: must depend on git-core (>> 1:1.4.2-0)
Bug#396418: cogito: FTBFS: failed tests
Merged 394838 396418.
> qui
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> # per the maintainer
> tags 394214 - patch
Bug#394214: eciadsl: FTBFS, uses PAGE_SIZE
Tags were: patch
Tags removed: patch
>
End of message, stopping processing here.
Please contact
Hi Masayuki,
Is there any progress on this bug? This build failure on arm makes it
impossible to update enchant for the two RC bugs that the library has in
testing, and there is no sign that libhunspell-dev will be available on arm
any time soon. Is there some way that enchant can be built witho
Can you also supply the contents of your /etc/ivman/IvmConfigBase.xml ?
thanks,
stew
signature.asc
Description: Digital signature
Processing commands for [EMAIL PROTECTED]:
> severity 393880 normal
Bug#393880: ivman: won't start
Severity set to `normal' from `grave'
> tags 393880 moreinfo
Bug#393880: ivman: won't start
There were no tags set.
Tags added: moreinfo
> tags 393880 unreproducible
Bug#393880: ivman: won't start
Hi
On Sunday 29 October 2006 19:54, Bastian Blank wrote:
> Package: gpsim-lcd
> Version: 0.2.7-1
> Severity: serious
>
> There was an error while trying to autobuild your package:
> > Automatic build of gpsim-lcd_0.2.7-1 on lxdebian.bfinv.de by sbuild/s390
> > 85
I do not have access to any of the
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> notfound 390664 1.39-1.1
Bug#390664: [NONFREE-DOC] Package contains IETF RFC/I-Ds
Bug marked as not found in version 1.39-1.1.
> found 390664 1.2-1.39-1.1
Bug#390664: [NONFREE-DOC] P
Can you run ivman like this, as root:
ivman --debug --nofork
and send the results?
thanks,
stew
signature.asc
Description: Digital signature
On Wed, Nov 01, 2006 at 05:49:41AM +0100, Daniel Schepler wrote:
> On Wednesday 01 November 2006 00:17 am, Steve Langasek wrote:
> > On Tue, Oct 31, 2006 at 10:12:17PM +0100, Daniel Schepler wrote:
> > > After the recent upload of libsdl1.2-dev downgrading the *-dev
> > > dependencies to recommends
.6-svn20061012.debian-1 on avidan by sbuild/i386 98
> Build started at 20061101-0450
> **
...
> fi
> i486-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../.. -DSYS_LINUX
> -I../../include -D_FILE_
On Tue, Oct 31, 2006 at 01:14:32PM +0100, Goswin von Brederlow wrote:
> It probably means that libaa-dev dropped its libaa.la file to earlz
> while dependend packages still have them and you can do nothing about this.
> But just in case I wanted to let you know.
>
> If libaa-dev is to blamen then
Processing commands for [EMAIL PROTECTED]:
> severity 387201 grave
Bug#387201: can't print on Brother HL01435 with any version of cupsys newer
than 1.2.1-2
Severity set to `grave' from `important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> severity 387498 serious
Bug#387498: mipsel: system() hangs when compiled with -pg (gprof profiling)
Severity set to `serious' from `grave'
>
End of message, stopping processing here.
Processing commands for [EMAIL PROTECTED]:
> severity 387201 important
Bug#387201: can't print on Brother HL01435 with any version of cupsys newer
than 1.2.1-2
Severity set to `important' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug track
Processing commands for [EMAIL PROTECTED]:
> severity 394934 grave
Bug#394934: cupsys: 1.2.3 and later => Printer not connected; will retry in 30
seconds...
Severity set to `grave' from `important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
severity 393880 normal
tags 393880 moreinfo
tags 393880 unreproducible
thanks
I can't reproduce this. It doesn't seem to happen to other users, so I'm
lowering the severity. Any more info you could give, such as the info I
previously requested would be welcome.
Thanks
signature.asc
Descrip
0
> Build started at 20061101-0233
> **
...
> (cd .libs && rm -f lib.gb.net.so.0 && ln -s lib.gb.net.so.0.0.0
> lib.gb.net.so.0)
> (cd .libs && rm -f lib.gb.net.so && ln -s lib
Hi,
As subject says, 2.6.18 is the etch target kernel, so it would be nice to have
information about the presence of this bug in 2.6.18.
In any case, this is probably not going to stop the migration of the 2.6.18
kernel to etch, since the bug is present in etch.
Furthermore, it only affects xen
Hi, ...
Please install the sid 2.6.18-3 kernel, and confirm the issue is still present
in it.
Friendly,
Sven Luther
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
sorry.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
> severity 396471 grave
Bug#396471: linux-image-2.6.18-1-parisc64-smp: fails to install
Bug#395110: linux-2.6: cannot configure linux-image-2.6.18-1-k7 package:
Missing Required parameter 'Old' at
/var/lib/dpkg/info/linux-image-2.6.18-1-k7.postinst
Seve
Quoting Ola Lundqvist ([EMAIL PROTECTED]):
> Hi
>
> Can you add debug lines to /var/lib/dpkg/info/bootsplash.postinst
> to pinpoint on what line you get this problem?
I am not the person who has the problem.
Nick Dickerson is
signature.asc
Description: Digital signature
Hi
Ohh sorry. I must have misunderstood the thread then.
Nick can you add the debug lines I'm referring to?
Regards,
// Ola
On Wed, Nov 01, 2006 at 08:52:58AM +0100, Christian Perrier wrote:
> Quoting Ola Lundqvist ([EMAIL PROTECTED]):
> > Hi
> >
> > Can you add debug lines to /var/lib/dpkg/i
101 - 189 of 189 matches
Mail list logo
