TAUDIO_H=1 -DHAS_SAMPLERATE_H=1
> -c -o ptt_unix.o ptt_unix.c
> ptt_unix.c:66:20: error: sys/io.h: No such file or directory
> make[1]: *** [ptt_unix.o] Error 1
> make[1]: Leaving directory `/build/buildd/wsjt-5.9.6.r309'
> make: *** [build-stamp] Error 2
> **
> Build finished at 20060926-0038
> FAILED [dpkg-buildpackage died]
Your message dated Mon, 25 Sep 2006 23:32:09 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#389291: fixed in libselinux 1.30.28-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 n
Package: dcc
Version: 1.3.42-1
Severity: serious
Justification: violating DFSG §5 and DFSG §6
* This agreement is not applicable to any entity which sells anti-spam
* solutions to others or provides an anti-spam solution as part of a
* security solution sold to other entities, or to
severity 389494 important
thanks
Quoting Rodrigo Iván Zayas Reyes ([EMAIL PROTECTED]):
> Package: samba
> Version: 3.0.23c-1
> Severity: grave
Please do not overflate bug reports. The correct severity here is
"important".
/usr/share/doc/debian/bug-maint-info.txt gives good hints abou tbug
severi
On Tue, September 26, 2006 3:44, Frans Pop said:
> Although the log does not show which udebs were actually installed,
> after the failure /var/lib/dpkg shows the following packages installed
> (probably newly installed as they are at the bottom of the file):
> - cdebconf-newt-entropy
> - crypto-mo
On Tuesday 26 September 2006 09:37, David Härdeman wrote:
> Perhaps "depmod -ae" needs to be executed after the
> crypto-modules-$kvers module has been downloaded and unpacked?
Yes, depmod definitely needs to be called after new modules are loaded.
(AFAIK depmod -a should be enough.)
Grep on depm
On Tue, Sep 26, 2006 at 12:57:50AM -0500, Manoj Srivastava wrote:
> > On Mon, Sep 25, 2006 at 01:20:16AM -0700, Steve Langasek wrote:
> >> Could you check if changing "-lpthread" to "-pthread" works?
> > Yes, it works. Thanks.
> > It also works with e2fsprogs, which was the original reason for t
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> merge 388568 389506
Bug#388568: xserver-xorg: postinst can hang
Bug#389506: fails to configure with debconf
Merged 388568 389506.
>
End of message, stopping processing here.
Please
The bug still happens with 0.30. I was browsing the monotone-devel
archives and something went *tick* in my head:
Shaun Jackman wrote:
> The monotone-0.30.tar.gz tarball shipped with package_revision.txt set
> to `unknown'. Should this be fixed?
Thomas Moschny wrote:
> [it is likely to affect 0.
On Mon, Sep 25, 2006 at 01:50:04PM +0200, Marc Haber wrote:
> On Mon, Sep 25, 2006 at 10:26:45AM +0200, Bill Allombert wrote:
> > There is an error when attempting to purge console-log:
> >
> > Removing console-log ...
> > Purging configuration files for console-log ...
> > Removing system u
Hi Bill,
2006/9/25, Bill Allombert <[EMAIL PROTECTED]>:
Package: nut
Version: 2.0.4-2
Severity: serious
Hello Arnaud,
There is an error when attempting to purge nut:
Removing nut ...
Purging configuration files for nut ...
/var/lib/dpkg/info/nut.postrm: line 5: deluser: command not foun
Processing commands for [EMAIL PROTECTED]:
> tags 389315 + patch pending
Bug#389315: strigi_0.3.8-1(hppa/unstable): FTBFS: broken inotify include file
There were no tags set.
Tags added: patch, pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug track
On Fri, Jul 21, 2006 at 04:47:12AM -0700, Anthony Fok wrote:
> stardict (2.4.7-2) unstable; urgency=low
> .
>* FTBFS: Forgot to add bzip2 build-dependency. Thanks to Aarom Ucko
> for the reminder! (Closes: Bug#378807)
>* Also: Build-Depends: libpcre3-dev, needed by dsl2dict in star
Dear Buildd admins,
there seems to be a problem with packages that build-depend on tetex,
which only manifests on the alpha, mips and mipsel buildds. We need
your help to investigate this, please see below.
Ralf Stubner <[EMAIL PROTECTED]> wrote:
> The strange thing is that mktexmf, which is c
On Mon, 25 Sep 2006, Matthew Wilcox wrote:
On Mon, Sep 25, 2006 at 07:36:11PM +0200, Andreas Tille wrote:
is any kind soul out there that is able to send me a patch
for this problem. I have no real idea what to do.
Get:1 http://http.us.debian.org unstable/main wordnet 1:2.0g-14 (tar) [5464kB
Package: libgcj-common
Version: 1:4.1.1-13
Severity: grave
Preparing to replace libgcj-common 1:4.1.1-13 (using
.../libgcj-common_1%3a4.1.1-14_all.deb) ...
Unpacking replacement libgcj-common ...
dpkg: error processing
/var/cache/apt/archives/libgcj-common_1%3a4.1.1-14_all.deb (--unpack):
tryin
Your message dated Tue, 26 Sep 2006 03:41:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line gstreamer0.10-plugins-good: Depends on non-existant
libraw1394-5, should depend on libraw1394-8?
has caused the attached Bug report to be marked as done.
This means that you claim that the prob
Processing commands for [EMAIL PROTECTED]:
> tags 389315 + patch pending
Bug#389315: strigi_0.3.8-1(hppa/unstable): FTBFS: broken inotify include file
Tags were: pending patch
Tags added: patch, pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug trac
Your message dated Tue, 26 Sep 2006 13:31:03 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in NMU of acidbase 1.2.5-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
Hi,
Just wanted to confirm that changing /etc/libnss-ldap.conf's
permissions to 0644 fixes the problem.
To do this properly, I had to re-configure the package
(dpkg-reconfigure libnss-ldap), since hand-fixed perms get reset on
upgrade.
Does libnss-ldap.conf need to be 0600 at all? As far as I se
Your message dated Tue, 26 Sep 2006 13:31:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in NMU of phpgacl 3.3.7-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
Your message dated Tue, 26 Sep 2006 12:04:26 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Doesn't crash with the latest libmodplug0c2 package
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
On Tuesday 26 September 2006 09:51, Frans Pop wrote:
> On Tuesday 26 September 2006 09:37, David Härdeman wrote:
> > Perhaps "depmod -ae" needs to be executed after the
> > crypto-modules-$kvers module has been downloaded and unpacked?
>
> Yes, depmod definitely needs to be called after new modules
concerning my previous email, I solved the problem: I kept xorg 7.1 and
installed the new version of the NVIDIA driver:
NVIDIA-Linux-x86-1.0-8774-pkg1.run
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message dated Tue, 26 Sep 2006 12:44:24 +0200
with message-id <[EMAIL PROTECTED]>
and subject line [Pkg-jed-sl-modules] Bug#383779: FTBFS on amd64: not creating
PIC code?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
Is anyone working on this release critical bug?
Might I suggest that dropping the isdnvboxserver package for now might be a
better option than having all of isdnutils (and reverse-dependencies)
dropped from etch?
Cheers,
--
Steve Langasek Give me a lever long enough and a Free
On Tue, Sep 26, 2006 at 10:54:26AM +0200, Bill Allombert wrote:
> > 2006/9/25, Bill Allombert <[EMAIL PROTECTED]>:
> > >Package: nut
> > >Version: 2.0.4-2
> > >Severity: serious
> > >There is an error when attempting to purge nut:
> > > Removing nut ...
> > > Purging configuration files for nut
tags 389315 + patch pending
thanks
hi,
i have committed on Debian pkg-kde svn, a patch to fix this issue.
basically, it fixes inotify support configure option and disables it.
A proper fix will be in next upstream release, removing inotify private files.
cheers,
Fathi
clone 388115 -1
reassign -1 jadetex
retitle -1 40jadetex.cnf is missing magic header
tags -1 -pending
stop
Frank Küster <[EMAIL PROTECTED]> wrote:
> And some more questions.
No more answers needed. The bug was actually twofold; my patch is going
to fix the part on tetex-base's side, but for i
Processing commands for [EMAIL PROTECTED]:
> tag 388235 + fixed
Bug#388235: config/postrm depends on non-essential packages (dbconfig-common,
probably ucf)
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking s
Processing commands for [EMAIL PROTECTED]:
> tag 388232 + fixed
Bug#388232: config/postrm depends on non-essential packages (dbconfig-common,
probably ucf)
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking s
Processing commands for [EMAIL PROTECTED]:
> clone 388115 -1
Bug#388115: tetex-base: postinst fails, can not upgrade
Bug 388115 cloned as bug 389550.
> reassign -1 jadetex
Bug#389550: tetex-base: postinst fails, can not upgrade
Bug reassigned from package `tetex-base' to `jadetex'.
> retitle -1
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> severity 386695 important
Bug#386695: Group commentary is a personal commentary in a group location
Severity set to `important' from `grave'
>
End of message, stopping processing her
tags 389315 + patch pending
thanks
hi,
i have committed on Debian pkg-kde svn, a patch to fix this issue.
basically, it fixes inotify support configure option and disables it.
A proper fix will be in next upstream release, removing inotify private files.
cheers,
Fathi
Processing commands for [EMAIL PROTECTED]:
> tag 388233 + fixed
Bug#388233: config/postrm depends on non-essential packages (dbconfig-common,
probably ucf)
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking s
Processing commands for [EMAIL PROTECTED]:
> found 388222 1.38.9-2
Bug#388222: config/postrm depends on non-essential packages (dbconfig-common,
probably ucf)
Bug marked as found in version 1.38.9-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracki
On Tue, Sep 26, 2006 at 11:22:38AM +0200, Andreas Tille wrote:
> Probably it did not hit the mirrors, but now it should be there.
> (Debian verison number -2 is missleading because -1 was in experimental
> and than was overriden by another upload of a previous upstream
> version with colon versioni
Your message dated Tue, 26 Sep 2006 12:29:33 +0200
with message-id <[EMAIL PROTECTED]>
and subject line ripit poiicy violation
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 responsibil
Your message dated Tue, 26 Sep 2006 05:25:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#389546: Conflict between fglrx-driver and xserver-xorg-core
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 i
On Tue, Sep 26, 2006 at 03:05:17AM -0700, Steve Langasek wrote:
> Eric,
>
> On Tue, Sep 26, 2006 at 02:32:38AM +0200, Eric Van Buggenhaut wrote:
>
> > I hope you're fine, it's been a long time since we met in Barcelona,
> > years ago... Are you still there ?
>
> > I'm dealing with bug #385665 a
Processing commands for [EMAIL PROTECTED]:
> tag 388225 + fixed
Bug#388225: config/postrm depends on non-essential packages (dbconfig-common,
probably ucf)
There were no tags set.
Tags added: fixed
> tag 388226 + fixed
Bug#388226: config/postrm depends on non-essential packages (dbconfig-common,
Processing commands for [EMAIL PROTECTED]:
> tag 388219 + fixed
Bug#388219: config/postrm depends on non-essential packages (dbconfig-common,
probably ucf)
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking s
Your message dated Tue, 26 Sep 2006 13:31:13 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in NMU of webcalendar 1.0.4-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 y
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> found 386781 0.7.1+cvs20060924.1330-1
Bug#386781: Crashes browser
Bug marked as found in version 0.7.1+cvs20060924.1330-1.
>
End of message, stopping processing here.
Please contact
Package: classpath-gtkpeer
Version: 2:0.92-3
Severity: grave
I'm still seeing upgrade problems:
Selecting previously deselected package classpath-gtkpeer.
Unpacking classpath-gtkpeer (from
.../classpath-gtkpeer_2%3a0.92-3_powerpc.deb) ...
dpkg: error processing
/var/cache/apt/archives/classp
Processing commands for [EMAIL PROTECTED]:
> tag 388239 + fixed
Bug#388239: config/postrm depends on non-essential packages (dbconfig-common,
probably ucf)
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking s
Subject: Conflict between fglrx-driver and xserver-xorg-core
Package: fglrx-driver
Version: 8.28.8-1
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
There's a conflict between fglrx-driver and xserver-xorg-core. When I try to
install the fg
Processing commands for [EMAIL PROTECTED]:
> tag 388231 + fixed
Bug#388231: config/postrm depends on non-essential packages (dbconfig-common,
probably ucf)
Tags were: patch
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system a
Your message dated Tue, 26 Sep 2006 14:40:31 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in NMU of postfix-policyd 1.80-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 no
On Sun, Sep 24, 2006 at 02:15:57AM -0300, Margarita Manterola wrote:
> I have tested the patches provided by Michael Ablassmeier and Christian
> Aichinger, and I have confirmed that applying both these patches together
> fixes the problem.
>
> I'm attaching the full interdiff output of the upload
Your message dated Tue, 26 Sep 2006 06:17:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#389382: fixed in djvulibre 3.5.17-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
On Tue, 26 Sep 2006, Matthew Wilcox wrote:
which is just garbage. static const char Id[] = "..." would make sense.
Well, this sounds very reasonable in dead.
How does that build on any architecture?
As expected fine on i386 and probably better than before on any other.
So if you commit tha
Hi Robert
On Monday 25 September 2006 10:17, Robert Millan wrote:
> On Mon, Sep 11, 2006 at 06:26:37PM +0200, Mats Erik Andersson wrote:
> > Venerable Maintainers of Grub,
> >
> > I offer you a patch that should close bug report
> > #345931.
> >
> > The patch has been built on top of grub-0.9
Processing commands for [EMAIL PROTECTED]:
> #> Bug 388115 cloned as bug 389550.
> #> Bug reassigned from package `tetex-base' to `jadetex'.
> #
> # Helm-a-lee
> reassign 389550 tex-common
Bug#389550: 40jadetex.cnf is missing magic header
Bug reassigned from package `jadetex' to `tex-common'.
> r
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> found 374996 0.7.1+cvs20060924.1330-1
Bug#374996: kills all your processes (including browser) on open a web page
with flash
Bug marked as found in version 0.7.1+cvs20060924.1330-1.
On Tue, Sep 26, 2006 at 02:51:14PM +0200, Andreas Tille wrote:
> On Tue, 26 Sep 2006, Matthew Wilcox wrote:
>
> >which is just garbage. static const char Id[] = "..." would make sense.
> Well, this sounds very reasonable in dead.
>
> >How does that build on any architecture?
>
> As expected fin
Your message dated Tue, 26 Sep 2006 07:32:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#382038: fixed in fglrx-driver 8.28.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
Philip Craig a écrit :
it seemed to be the apache.pem key cert. Not the config files.
Andreas Barth wrote:
Hi,
* Philip Craig ([EMAIL PROTECTED]) [060830 10:43]:
I have more info. I did a stack trace with apache-ssl.dbg built from
source, and it was crashing in libssl.
i test 'apache-ss
On Tue, 26 Sep 2006, Steve Langasek wrote:
> Eric,
>
> On Tue, Sep 26, 2006 at 02:32:38AM +0200, Eric Van Buggenhaut wrote:
>
> > I hope you're fine, it's been a long time since we met in Barcelona,
> > years ago... Are you still there ?
>
> > I'm dealing with bug #385665 and your help would be gr
Your message dated Tue, 26 Sep 2006 07:32:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#388840: fixed in fglrx-driver 8.28.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
On Tue, Sep 26, 2006 at 03:23:45PM +0200, Steinar H. Gunderson wrote:
> On Sun, Sep 24, 2006 at 02:15:57AM -0300, Margarita Manterola wrote:
> > I have tested the patches provided by Michael Ablassmeier and Christian
> > Aichinger, and I have confirmed that applying both these patches together
> >
Package: tex-common
Version: 0.28
Severity: serious
Justification: file (directory) conflict, breaks upgrade
Sorry for german, but with today's upgrade run I got:
Entpacke Ersatz für tex-common ...
dpkg: Fehler beim Bearbeiten von
/var/cache/apt/archives/tex-common_0.29_all.deb (--unpack):
versu
Package: fluxbox
Version: 0.9.14-1.2
Severity: grave
Justification: renders package unusable
Hi
i've happy used fluxbox for long time, but 2 days ago it won't
start. But the strange thing is that if i create a new users, with no
groups at all, it starts fine. So i removed .fluxbox on my
Okay, just dput a fix.
Sorry for all the libs trouble w/ this package. It is a strange
situation: the ABI is (at least in principle) utterly unstable across
releases for the bits of the library that upstream uses, but the calls
into the library that are blessed for external use should be stable.
Processing commands for [EMAIL PROTECTED]:
> tag 386491 + fixed
Bug#386491: FTBFS on sparc
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To
Your message dated Tue, 26 Sep 2006 03:47:21 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#388235: fixed in simba 0.8.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
Eric,
On Tue, Sep 26, 2006 at 02:32:38AM +0200, Eric Van Buggenhaut wrote:
> I hope you're fine, it's been a long time since we met in Barcelona,
> years ago... Are you still there ?
> I'm dealing with bug #385665 and your help would be greatly
> appreciated.
> Someon is requesting to move fl
Hello,
I use asterisk-classic 1.2.10 (testing) and get the same error message
with asterisk-chan-capi.
Asterisk Dynamic Loader Starting:
[chan_capi.so]Sep 26 12:10:37 WARNING[1257]: loader.c:325
__load_resource: /usr/lib/asterisk/modules/chan_capi.so: undefined
symbol: ast_pickup_call
/etc/ast
Processing commands for [EMAIL PROTECTED]:
> severity 389494 important
Bug#389494: samba 3.0.23c-1 shares cause segfault
Severity set to `important' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
On Tue, Sep 26, 2006 at 10:43:39AM +0200, Arnaud Quette wrote:
> Hi Bill,
>
> 2006/9/25, Bill Allombert <[EMAIL PROTECTED]>:
> >Package: nut
> >Version: 2.0.4-2
> >Severity: serious
> >
> >Hello Arnaud,
> >
> >There is an error when attempting to purge nut:
> >
> > Removing nut ...
> > Purging c
Ross Boylan <[EMAIL PROTECTED]> wrote:
> I modified tetex-base.postinst as indicated in the patch above to
> postinst.in. The problem remains.
Hm, can you please add a "set -x" at the beginning of
tetex-base.postinst, try again like this
dpkg --configure -a 2>&1 | tee configure.log
(or similar
Frank Küster <[EMAIL PROTECTED]> wrote:
> Ross Boylan <[EMAIL PROTECTED]> wrote:
>
>> I modified tetex-base.postinst as indicated in the patch above to
>> postinst.in. The problem remains.
>
> Hm, can you please add a "set -x" at the beginning of
> tetex-base.postinst, try again like this
>
> dpk
With the workaround provided by Jerome the python back-end still doesn't works:
omniidl: Could not import back-end 'python'
omniidl: Maybe you need to use the -p option?
omniidl: (The error was 'No module named python')
I've fixed it by adding
'/usr/share/pycentral/omniidl4-python/site-packages
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> severity 378214 important
Bug#378214: Opening file fails, kino stops with segmentation fault
Severity set to `important' from `grave'
> tags 378214 moreinfo unreproducible
Bug#378214
Your message dated Tue, 26 Sep 2006 10:05:25 -0400
with message-id <[EMAIL PROTECTED]>
and subject line build-dep on automake1.9
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 responsib
On 26/09/06, Matthew Wilcox <[EMAIL PROTECTED]
> wrote:
On Tue, Sep 26, 2006 at 02:51:14PM +0200, Andreas Tille wrote:> On Tue, 26 Sep 2006, Matthew Wilcox wrote:>> >which is just garbage. static const char Id[] = "..." would make sense.
> Well, this sounds very reasonable in dead.
>> >How does th
Your message dated Tue, 26 Sep 2006 08:47:42 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#388067: fixed in tetex-base 3.0-22
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
On Tue, Sep 26, 2006 at 01:37:31PM +0200, Frank Küster wrote:
> clone 388115 -1
> reassign -1 jadetex
> retitle -1 40jadetex.cnf is missing magic header
> tags -1 -pending
> stop
>
> Frank Küster <[EMAIL PROTECTED]> wrote:
>
> > And some more questions.
>
> No more answers needed. The bug was
On Tue, Sep 26, 2006 at 01:02:02PM +0200, Frans Pop wrote:
On Tuesday 26 September 2006 09:51, Frans Pop wrote:
Also, if loading modules can result in new devices, update-dev (from
di-utils) needs to be called.
Again, grep in hwdetect for examples.
Adding a 'depmod -a' does fix the problem.
Michel Dänzer wrote:
>
> > * xserver-xorg/config/device/driver: vesa
>
> Does this also happen with the 'ati' driver?
No, it works, but this driver is almost unusable with my card: it
supports max 8bit colour, so GNUstep apps won't run, and it totally
messes the console colours making it garbled
On Tue, Sep 26, 2006 at 09:52:28AM -0400, Leandro Dorileo wrote:
> Hi Robert
>
> On Monday 25 September 2006 10:17, Robert Millan wrote:
> > On Mon, Sep 11, 2006 at 06:26:37PM +0200, Mats Erik Andersson wrote:
> > > Venerable Maintainers of Grub,
> > >
> > > I offer you a patch that should clos
Ross Boylan <[EMAIL PROTECTED]> wrote:
> Thanks for looking into this. Is there some work-around that will get
> past the jadetex problem (as I guess you found, it was precisely the
> same error message).
Sorry for forgetting to mention the workaround.
mv /etc/texmf/fmt.d/40jadetex.cnf /etc/t
Willi Mann wrote:
> Package: tex-common
> Version: 0.28
> Severity: serious
> Justification: file (directory) conflict, breaks upgrade
>
> Sorry for german, but with today's upgrade run I got:
>
> Entpacke Ersatz für tex-common ...
> dpkg: Fehler beim Bearbeiten von
> /var/cache/apt/archives/tex
Package: gnutls-bin
Version: 1.4.4-1
Severity: grave
I recently upgraded the gnutls-bin package, and I can no longer
use gnutls to connect over TLS to the SMTP server I use. starttls
works fine with the same server. Below is the output from gnutls-cli.
gnutls-cli -d 2 smtp.mail.gatech.edu -p 25
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> # was not in a stable release, so replaces are not RC
> severity 389539 important
Bug#389539: file conflict with java-gcj-compat-dev
Severity set to `important' from `grave'
>
End of
Please keep [EMAIL PROTECTED] in the cc; this information should be
recorded in the bug report.
Brent S. Elmer wrote:
> I downloaded qt-x11-free-dbg and ran your debug version of
> fireglcontrol. I didn't download the source to debug but here is the
> gdb info anyway:
As far as I can tell, it's
reassign 389584 latex-ucs-doc
merge 389584 388376
stop
Willi Mann <[EMAIL PROTECTED]> wrote:
> /usr/share/texmf/doc is a directory in package latex-ucs-doc, but a
> symlink in tex-common 0.29.
>
> So IMHO tex-common should conflict (replace?) with latex-ucs-doc and
> latex-ucs-doc should change
Processing commands for [EMAIL PROTECTED]:
> reassign 389584 latex-ucs-doc
Bug#389584: tex-common: file confict with latex-ucs
Bug reassigned from package `tex-common' to `latex-ucs-doc'.
> merge 389584 388376
Bug#388376: latex-ucs-doc: installs files into /usr/share/texmf/doc against
Debian TeX
> No, latex-ucs-doc should not start shipping directories that were
> symlinks all the time. What's your version of latex-ucs-doc? If it is
> 20041017-5 or older, then this is a duplicate of #388376. Please
> upgrade to 20041017-6 in unstable where the bug is fixed. If it still
Yes, that fixe
I moved qtrc out of the way. I don't think there is any difference.
(gdb) r
Starting program: /home/brente/firegl/fireglcontrol
[Thread debugging using libthread_db enabled]
[New Thread -176896 (LWP 25293)]
Qt: gdb: -nograb added to command-line options.
Use the -dograb option to
Hey again,
On Tue, Sep 26, 2006 at 06:37:59PM +0200, David Härdeman wrote:
> This leaves libpopt0 and cdebconf-newt-entropy
>
> I've committed a preliminary test for the presence of those two libs to
> crypto_check_required_tools.
case $1 in
dm-crypt)
- tools="/bin
Processing commands for [EMAIL PROTECTED]:
> #>> merge 389584 388376
> #> Mismatch - only Bugs in same state can be merged:
> close 389584 20041017-6
Bug#389584: tex-common: file confict with latex-ucs
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> severity 389274 grave
Bug#389274: nvidia-kernel-2.6.17-1-686: not built against the latest kernel
Severity set to `grave' from `important'
> merge 389274 384261
Bug#384261: nvidia-ke
Hey David,
Thanks for adding the checks.
On Tue, Sep 26, 2006 at 06:37:59PM +0200, David Härdeman wrote:
> This leaves libpopt0 and cdebconf-newt-entropy
cdebconf-newt-entropy is already taken care of through db_capb;
blockdev-keygen will return an error dialog if it needs but cannot
find the p
Your message dated Tue, 26 Sep 2006 10:49:22 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#389315: fixed in strigi 0.3.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 now you
Your message dated Tue, 26 Sep 2006 10:48:42 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#389299: fixed in linuxlogo 4.14-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 y
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> reassign 389456 partman-crypto
Bug#389456: p-a-c: Fails to configure encrypted volumes
Bug reassigned from package `partman-auto-crypto' to `partman-crypto'.
> found 389456 13
Bug#38
Ralf Stubner <[EMAIL PROTECTED]> wrote:
> This is actually a bug in latex-ucs-doc not in tex-common which has been
> reported (#388376 and #388407) before. It is fixed in latex-ucs
> 20041017-6. If I interpret latex-ucs's changelog correctly, this problem
> was introduced in version 20041017-4 upl
Ross Boylan <[EMAIL PROTECTED]> wrote:
> On Tue, 2006-09-26 at 18:37 +0200, Frank Küster wrote:
>> Ross Boylan <[EMAIL PROTECTED]> wrote:
>>
>> > Thanks for looking into this. Is there some work-around that will get
>> > past the jadetex problem (as I guess you found, it was precisely the
>> > s
Hi, I have the same problem.
After the upgrade (one or two days ago) my fonts started to show those
symptons.
This is my aptitude log (sorry, but it is in spanish):
===
Registro completado.
Aptitude 0.4.3: informe de
1 - 100 of 148 matches
Mail list logo