I have had this for a while and do not use an initrd. I can rmmod genrtc and
modprobe rtc afterwards. However, certain thing have already loaded which
depend upon the rtc.ko and produce errors with genrtc.ko loaded.
I had a blacklist entry which had been successful in surpressing genrtc. I
On Tuesday 15 May 2007, Stephen Gran wrote:
This one time, at band camp, David Baron said:
I tried renicing. Indeed, now top shows clamd running with the specified
nice value and could probably be started from init.d script with a nice
value. However, the kde system monitor applet does
On Tuesday 15 May 2007, Stephen Gran wrote:
This one time, at band camp, David Baron said:
On Tuesday 15 May 2007, Stephen Gran wrote:
I'm sorry, maybe I'm not reading this clearly. Is the bug report about
clamd not being niceable (preferabl in some automated way, via an init
script
On Tuesday 15 May 2007, Stephen Gran wrote:
This one time, at band camp, David Baron said:
On Tuesday 15 May 2007, Stephen Gran wrote:
[EMAIL PROTECTED]:~$ ps -elF | egrep '(ADDR|clam)'
F S UIDPID PPID C PRI NI ADDR SZ WCHANRSS PSR STIME TTY
TIME CMD 1 S clamav
Package: clamav-daemon
Version: 0.90.2-1+b1
Severity: wishlist
File: /usr/sbin/clamd
I tried renicing. Indeed, now top shows clamd running with the specified
nice value and could probably be started from init.d script with a nice
value. However, the kde system monitor applet does not show clamd
On Thursday 03 May 2007, Marc Haber wrote:
On Thu, May 03, 2007 at 06:10:03PM +0300, David Baron wrote:
On Thursday 03 May 2007, you wrote:
On Thu, May 03, 2007 at 04:09:00PM +0300, David Baron wrote:
In outlook express, one would check authentification required and
enter simply 'v
On Wednesday 02 May 2007, Marc Haber wrote:
On Wed, May 02, 2007 at 10:04:36PM +0300, [EMAIL PROTECTED] wrote:
Did not change it. I am sending this as I had to do the original
submission from the provider's online mail site.
What do your logs say? I bet that your host is failing to
On Thursday 03 May 2007, Marc Haber wrote:
On Thu, May 03, 2007 at 03:08:32PM +0300, David Baron wrote:
The logs show the message being sent smarthost, completed.
Unfortunately, exim logs do not show whether exim did authenticate.
Then show the return with the error message which does cite
If it is OK bypassing the smarthost, then either:
Exim4 is doing something different now that the provider is not
pleased with,
I suspect that it is not authenticating.
or
the provider has made some little changes and has not documented them to
the subscribers (would not be the
On Thursday 03 May 2007, you wrote:
On Thu, May 03, 2007 at 04:09:00PM +0300, David Baron wrote:
In outlook express, one would check authentification required and enter
simply 'v'. (Usually there will be fields for username and password)
What would v mean?
Good question. How much more
Package: enigma
Version: 1.00-2
Severity: grave
Justification: renders package unusable
After latest Sid upgrades (including libc6), enigma will fail after
completing one board with an undefined libzipios symbol. Leaves screen at
wrong setting if played full screen and mouse is eaten whether full
Any news about that? Could we close the bug?
My Debian box is working 100% OK. Can upgrade other stuff as well.
However:
After a recent post about libc6 upgrade trashing someone's sarge, I recommend
the following:
1. Pre-configure:
Check running kernel. If not new enough, STOP NOW.
Check
On Wednesday 25 April 2007, you wrote:
David Baron a écrit :
On Wednesday 25 April 2007, you wrote:
Aurelien Jarno a écrit :
d_bron a écrit :
Package: libc6
Version: 2.5-4
Severity: critical
Justification: breaks unrelated software
Once again, with feeling.
1. Attempt to fix
On Wednesday 25 April 2007, you wrote:
Aurelien Jarno a écrit :
d_bron a écrit :
Package: libc6
Version: 2.5-4
Severity: critical
Justification: breaks unrelated software
Once again, with feeling.
1. Attempt to fix up dependencies and upgrade using apt -4 install. As
soon as it
Some more odities that may or may not be relevant:
With the downgraded (allbeit dependency-problematic) to 2.3*:
sh run from kpackage fails looking for an .so.# library.
sh run from anywhere else works fine
bash (sh is simply a symlink to bash) runs fine.
Opera run from a command line works fine.
On Wednesday 25 April 2007, Aurelien Jarno wrote:
David Baron a écrit :
Some more odities that may or may not be relevant:
With the downgraded (allbeit dependency-problematic) to 2.3*:
sh run from kpackage fails looking for an .so.# library.
Which one?
Can't get back there but might
LD_ASSUME_KERNEL=2.6.1 /lib/ld-2.5.so /lib/libc.so.6
I have a LD_ASSUME_KERNEL=2.4.19 in /etc/profile which was put there for
jackd. Maybe I should get rid of that! Tried that with the upgrade and
actually got into a bash login from the console but kdm would not restart to
test it there. Had
LD_ASSUME_KERNEL=2.6.1 /lib/ld-2.5.so /lib/libc.so.6
I have a LD_ASSUME_KERNEL=2.4.19 in /etc/profile which was put there for
jackd. Maybe I should get rid of that! Tried that with the upgrade and
actually got into a bash login from the console but kdm would not restart to
test it there. Had
On Tuesday 24 April 2007, Aurelien Jarno wrote:
David Baron a écrit :
Package: libc6
Version: 2.5-2
Severity: critical
Justification: breaks unrelated software
1. Upgrade -- balks at symlinks in /usr/lib, asks user to remove them.
BAD BAD BAD!
What do you mean exactly? Could you
Package: libc6
Version: 2.5-2
Severity: critical
Justification: breaks unrelated software
1. Upgrade -- balks at symlinks in /usr/lib, asks user to remove them. BAD
BAD BAD!
2. Once these removed, installs. Bash is now unusable--problem is in calls
from bashrc, bash.bashrc, et al. bash -norc, sh
Package: sudo
Version: 1.6.8p12-5
Severity: important
Most recent upgrade of sudo no longer can execute something on the path, for
example, $KDEDIR/bin/some-kde-app. If I explicitely give it this path
string, it works just fine. May be related to #383389
(Bug or feature? If feature, one might
On Sunday 15 April 2007, Bdale Garbee wrote:
tags 419394 +moreinfo
severity 419394 normal
thanks
On Sun, 2007-04-15 at 17:38 +0300, David Baron wrote:
Most recent upgrade of sudo no longer can execute something on the path,
for example, $KDEDIR/bin/some-kde-app. If I explicitely give
Package: gsambad
Version: 0.1.5-2
Severity: important
Get the following on startup:
[EMAIL PROTECTED]:~$
** (gsambad:11320): WARNING **: Couldn't find pixmap file: gsambad.png
(gsambad:11320): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
The program does
The installation of kqemu does still place option major=0
in /etc/modprobe.d/kqemu.
Should be major=250
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: kqemu-source
Version: 1.3.0~pre11-3
Severity: grave
Justification: renders package unusable
The following from dmesg | grep kqemu:
kqemu: Unknown symbol kqemu_init
kqemu: Unknown symbol kqemu_exec
kqemu: Unknown symbol kqemu_delete
kqemu: Unknown symbol kqemu_global_init
kqemu: Unknown
Package: kqemu-common
Version: 1.3.0~pre11-2
Severity: important
The kqemu node is major=250
The package places /etc/modprobe.d/kqemu with major=0
Since this apparently overrides specified options, qemu reports cannot open
/dev/kqemu.
Changing the contents of modprobe.d/kqemu to major=250 fixes
Package: qemu
Version: 0.8.2-5
Severity: normal
Always get Could not open '/dev/kqemu' - QEMU acceleration layer not
activated.
This message may or may not be true. I have experimented with the
permissions of /dev/kqemu and sudoing the qemu run to no avail. Set up a kqemu
group for such
This file had an option of major=0. This apparently overrode any attempt to do
it explicitely modprobe kqemu major=250. This may be the cause of the
problem.
If so, the bug may be switched the kqemu-source if this install placed this
file.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
Package: jackd
Version: 0.101.1-2
Severity: important
I have seen this one in several application, most recently aldrin.
The app detects the jackd server and tries to connect to an audio output
device. Something returns this error.
Code using floating point for the sample rate must be rounded
On Tuesday 06 February 2007, you wrote:
severity 409645 important
thanks
On Sun, Feb 04, 2007 at 04:46:04PM +0200, David Baron wrote:
Fuse got installed, probably as a dependency from something else. All of
a sudden, I get on my bootup a failure started fuse module. I never
elected
Package: fuse-utils
Version: 2.6.2-1
Severity: grave
Justification: renders package unusable
Fuse got installed, probably as a dependency from something else. All of a
sudden, I get on my bootup a failure started fuse module. I never elected to
start this. Maybe initscripts activated it. However:
On Saturday 27 January 2007 23:32, Daniel Baumann wrote:
severity 408711 normal
tags 408711 +moreinfo
thanks
David Baron wrote:
I can install it by using --force-all or appropriate
--ignore-dependencies but this will cripple further apt upgrading.
no clue what you are talking about. can
On Sunday 28 January 2007 15:18, Daniel Baumann wrote:
reopen 408711
reassign 408711 kernel-package
thanks
David Baron wrote:
Run sudo m-a install kqemu-source which I assume simply is doing dpkg -i
kqemu-module-..deb
This fails with an unment dependency on a missing linux-modules
On Sunday 28 January 2007 21:32, Daniel Baumann wrote:
David Baron wrote:
kqemu is contributed, non-free and while nice to have a package in Sid,
this is outside the overall Debian realm. Having unneeded dependencies is
such a package is not really so nice.
you did not understand, please
Package: kqemu-source
Version: 1.3.0~pre9-11
Severity: grave
Justification: renders package unusable
I can install it by using --force-all or appropriate --ignore-dependencies
but this will cripple further apt upgrading.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT
Package: module-assistant
Version: 0.10.8
Severity: normal
kqemu-source does not appear on the modules list, even after update. I can,
of course, specify in the command line.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (990, 'unstable'), (650, 'testing')
Package: module-assistant
Version: 0.10.8
Severity: normal
The following scenarios render further builds quite problematic, usually
necessistating reuntar of kernel source (note that building against source,
not installed headers):
1. build for current running kernel, linux-another kernel source
On Sunday 07 January 2007 19:11, Eduard Bloch wrote:
#include hallo.h
* David Baron [Sun, Jan 07 2007, 05:49:00PM]:
Package: module-assistant
Version: 0.10.8
Severity: normal
The following scenarios render further builds quite problematic, usually
necessistating reuntar of kernel
Package: kqemu-source
Version: 1.3.0~pre9-4
Severity: grave
Justification: renders package unusable
Attempted to install the latest and greatest kqemu using m-a. This failed
trying to write to a /etc/udev.d subdirectory. I am not using udev so obviously
do not have this.
There is no dependency
Package: kernel-patch-openvz
Version: 028test007.1
Severity: normal
Near end of shutdown sequence, get a series of messages of form:
Uncharging ... too many ...
They are apparently harmless.
Not preserved in logcheck items.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT
Get the following harmless quip on boot:
Dec 23 18:26:18 d_baron kernel: Testing NMI watchdog ... CPU#0: NMI
appears to be stuck (0-0)!
This means that on your motherboard/CPUs kernel was unable
to setup NMI watchdog. nothing bad, except for kernel won't be
able to detect it's hard
Compiled and booted!! I apparently will work with voluntary preemption as
well as no premption. No oopses, flags. Next week I will start to play with
it!
Caveat:
Unionfs will not compile against the patched sources (not using it yet so it
can wait).
Get the following harmless quip on boot:
Compiled and booted!! I apparently will work with voluntary preemption as
well as no premption. No oopses, flags. Next week I will start to play with
it!
Caveat:
Unionfs will not compile against the patched sources (not using it yet so it
can wait).
--
To UNSUBSCRIBE, email to [EMAIL
On Thursday 21 December 2006 08:16, Ola Lundqvist wrote:
Hi David
When I compiled the kernel yesterday using the same version of the kernel
and the openvz patch I did not need to do anything with symlinking.
My compile line look something like this:
export PATCH_THE_KERNEL=true
untar
Got it to build and even attempt to boot--no undefineds!
The thing listed a lot of oops codes, many involving the journaling, so I
panicked and stopped it.
Additionally, there were items like:
BUG: Using SMP with preemptive
(or something like that.)
(I do not have multiple processors but
as of that date would not patch. The current
version patched but produced the errors on compile.
Regards,
// Ola
On Tue, Dec 19, 2006 at 10:58:40AM +0200, David Baron wrote:
Package: kernel-patch-openvz
Version: 028test007.1
Severity: important
Justification: fails to build from source
Here
Hi
I have built it now and I have no problem building. Not at least
with make-kpkg.
I use this.
According to upstream you did not run make oldconfig for some reason?
It does this anyway. I compied to .config from the non-patched kernel and was
asked to fill in various new items inserted
Hi
I have built it now and I have no problem building. Not at least
with make-kpkg.
I use this.
According to upstream you did not run make oldconfig for some reason?
It does this anyway. I compied to .config from the non-patched kernel and was
asked to fill in various new items inserted
Hi
I have built it now and I have no problem building. Not at least
with make-kpkg.
I use this.
According to upstream you did not run make oldconfig for some reason?
It does this anyway. I compied to .config from the non-patched kernel and
was
asked to fill in various new items inserted
Package: kernel-patch-openvz
Version: 028test007.1
Severity: important
Justification: fails to build from source
Here they are: (May be others as well.)
kernel/built-in.o: In function `do_env_create':
vecalls.c:(.text+0x349a7): undefined reference to `ve_snmp_proc_init'
On Tuesday 05 December 2006 17:21, Roland Marcus Rutschmann wrote:
On Tuesday 05 December 2006 14:33, David Baron wrote:
On Tuesday 05 December 2006 12:24, Roland Marcus Rutschmann wrote:
Hi,
just checked with all available DICOM files available to me. Could you
please send me
Package: medicon
Severity: grave
Justification: renders package unusable
Medicon and Xmedicon both segfault on recent DICOM files. I would assume the
problem is in the common library rather than either of these individually.
DICOM is an ongoing, developing standard and apparently new codes are
On Monday 04 December 2006 15:18, Martin Michlmayr wrote:
* David Baron [EMAIL PROTECTED] [2006-12-04 11:34]:
Package: medicon
I don't see this package in Debian. What does
dpkg -p medicon | grep Maintainer
say?
OK it's medcon and xmedcon. Maintainer is Roland Marchus Rutschmann. He
Package: dansguardian
Version: 2.8.0.6-antivirus-6.4.4-1
Severity: important
All of a sudden, my main partition was full up. Since the complaining
program was trying to write /tmp, I listed /tmp contents and found several
hundred megabytes of stuff in /tmp/dgvirus. I removed two of the largest
On Thursday 16 November 2006 17:45, Daniel Baumann wrote:
Hi,
please note that this was for both, unionfs and squashfs, requested by
waldi. Hence, this bug is a non-issue, actually.
Regards,
Daniel
Since current kernel is 2.6.18 and these compile just fine, certainly close it
already :-)
Yesterday, my 1.5M ADSL ran at full 195kbs. Not one single failure getting
SOAP information download
Today, I was running at 60-80kbs and got repeated failures.
This thing needs fixing at the provider 012.net.il due to the sporadic
slowness download from the US. The reason that a slower
On Sunday 15 October 2006 03:00, Junichi Uekawa wrote:
retitle 391180 ISP in Israel uses NetApp NetCache, and it's unable to serve
Proxy requests reliably. What can I do? thanks
I'm retitling the bug report accordingly so that others don't get confused
about what the problem is.
Hi,
I
On Saturday 14 October 2006 08:46, Junichi Uekawa wrote:
Retrieving bug reports... 0% W: unsupported proxy `false'
Your apt.conf is wrong, and broken due to broken and now fixed
apt-setup.
Your proxy is called 'false' which shouldn't be.
Another posting instructed this poster to take out
On Friday 13 October 2006 07:57, Michael Ott wrote:
Hi!
I got the following error during upgrade:
Fetched 7301kB in 54s (134kB/s)
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... 0% W: unsupported proxy `false'
Error retrieving bug reports
Retry
On Friday 13 October 2006 04:53, Steve Langasek wrote:
severity 392597 important
thanks
On Thu, Oct 12, 2006 at 02:38:49PM +0200, David Baron wrote:
The Debian nvidia packages do not work as well as nvidia's own (even
though the code would be mostly the same). Planet Penguin Racer reports
I spoke with the provider who is indeed running NetCache which is a default
transfer proxy for most Israeli ADSL. He informed me that the proxy is only
active on port 80 and that any other port bypasses it.
This might be another settable option?
It is now, tried -p 81. Did not change anything.
Package: nvidia-glx
Severity: serious
Justification: 4
The Debian nvidia packages do not work as well as nvidia's own (even though
the code would be mostly the same). Planet Penguin Racer reports half the
frame rate. FlightGear will not run.
Kernel Module was built using m-a.
-- System
I do not believe this is still a problem. Probably can close unless someone
had this happen again!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
0.62 installed. Network problematic today so get frequent empty soap ... do
you want to retry Can keep saying yes, will work after a few retries.
An idea would be to silently retry within the timeout (30 seconds, not 999
seconds or something I can set somewhere), then ask. This would rarely
Sorry to bother you again but it might be useful:
Not one failure today. None. What is different--network was functioning at
full rated transferspeed rather than the fluctuation and such of the past few
days. So maybe the timing is relevant or some problem on the provider's
server?
--
To
Since top reveals that this is being run when trying to run OO, I did so
manually. Once the program has crashed and any further run attempts yield
this error:
pure virtual method called
terminate called without an active exception
This may be of interest.
--
To UNSUBSCRIBE, email to [EMAIL
Package: openoffice.org
Version: 2.0.4~rc3-1
Severity: important
RTF import is broken. May touch upon the following and other previous bugs:
#250005, #326091, #302073.
RTF produced by OO MAY (or may not) in fact come in OK.
RTF produced by other programs will not. After the crash,
further
Package: apt-listbugs
Version: 0.0.58
Severity: important
Usually works just fine. Every few runs, get:
E: Sub-process if dpkg -s apt-listbugs | grep -q '^Status: .* ok installed';
then /usr/sbin/apt-listbugs apt || ( test $? -ne 10 || exit 10; echo
'Warning: apt-listbugs exited abnormally, hit
1. May be related to a very short timeout trying to get the information!
2. This is the exact same error message I get if I answer no to whether to
procede with the upgrade, it seems. Kpackage seems to need to generate and
error to abort the upgrade process (and afterwards does not handle the
Version 0.57 still has the problem.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: squashfs-module
Version: squashfs
Severity: normal
Will not compile against 2.6.17 sources. Same problem with unionfs so this
was also prematurely posted. Dependencies on 2.6.18 not flagged.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy:
Package: unionfs-source
Version: 1.3.20060918.2217+debian-1
Severity: grave
Justification: renders package unusable
Compilation error on main.c, get_sb_nodev() too many arguments.
I cannot find a prototype for this function in the unionfs sources to try to
fix it so must be part of the kernel.
Package: fontconfig
Version: 2.4.1-1
Severity: grave
Justification: renders package unusable
Recent Sid versions cannot write font caches.
Will report scanning of # directories, # fonts in log or using -v option,
but will not write caches. This renders X very slow (such a bug reported)
and KDE
Subject: exim4: Spurious? paniclog error
Package: exim4
Version: 4.63-3
Severity: normal
At each system start, I get a system email with:
exim paniclog /var/log/exim4/paniclog on d_baron has non-zero size, mail
system might be broken
It's not :-)
The paniclog will contain a few entries like:
Package: prelink
Version: 0.0.20060712-2
Severity: grave
Justification: renders package unusable
Prelink does indeed prelink, missing many binaries due to problems outside
its scope. However, it eventually fails with:
*** glibc detected *** free(): invalid pointer: 0xb7f9ac08 ***
Prelink failed
Package: sgt-puzzles
Version: 6739-1
Severity: important
Game has various levels such as intermediate, extreme, etc.
Many of these (extreme, unreasonable, others) but NOT all of them crash the
program.
The usual backtrace box does NOT come up so I have no trace data.
-- System Information:
Simply recompiling the Nvidia (closed--from their site) driver fixed it!
Recommend others who have such problems: Try recompiling the driver/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: foomatic-db
Version: 20060530-1
Severity: normal
Since the foomatic package changelog suggested reinstalling the printer
PPDs, I set out to do so. Building the driver database produced a lot of
errors. In the KDE shell, got several unable to create databse error boxes
and the console
Package: freeglut3
Version: 2.4.0-5
Severity: grave
Justification: renders package unusable
Latest upgrade from Sid caused the following error--console output from
flightgeear but planet-penguine and others also inoperative:
freeglut (fgfs): Unable to create direct context rendering for window
Package: libasound2
Version: 1.0.11-5,6
Severity: critical
Justification: breaks unrelated software
Alsa is unable to find any of its hw:# devices.
Disables all sound
Hangs up artsd
Error messages on bootup, however not recorded in any logs.
Easy enough to reproduce.
I downgraded to 1.0.11-3
On Wednesday 05 April 2006 12:44, you wrote:
reassign 359264 libgconf2-4
thanks
On Wed, Mar 29, 2006 at 05:17:32PM +0200, David Baron wrote:
Python2.4 upgrades today on Sid apparently corrected the problem.
I had to install python2.4_2.4.2+2.4.3c1-1_i386.deb with a dpkg
--force-all
I had somehow lost the main database file. Once regenerated, program could
once again test and update. Program should protect itself against missing or
invalid data rather than proceed and segfault out.
I now get the following which I never got before:
### Warning: File system error.
###
Package: tripwire
Version: 2.3.1.2.0-7
Severity: important
Tripwire now requires its policy text files on line and will segfault
and crash with it/them.
For security reasons, it was recommended to keep these off line in safe
storage. Requiring them on line is not secure behavior and it always
I saw this in an error message somewhere but did not repeat. I reconfigured,
regenerated the binary files. Still get the segfault, however.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Python2.4 upgrades today on Sid apparently corrected the problem.
I had to install python2.4_2.4.2+2.4.3c1-1_i386.deb with a dpkg --force-all
because of duplicated files. Running apt-get -f install afterwards to
complete the aborted upgrades completed all the gnome/pango incompletes as
well! I
On Tuesday 28 March 2006 05:40, you wrote:
On Mon, Mar 27, 2006 at 04:44:00PM +0200, David Baron wrote:
Package: upgrades-reports
Version: gnome libraries 2.14.0-1, libpango1.0-common 1.12.0-2
Severity: grave
Justification: renders package unusable
An undefined symbol in the gnome
Package: upgrades-reports
Version: gnome libraries 2.14.0-1, libpango1.0-common 1.12.0-2
Severity: grave
Justification: renders package unusable
An undefined symbol in the gnome, pango libraries renders the upgrades
uninstallable and disables programs now dependent on them:
undefined symbol:
Package: libgtk-x11-2.0
Version: 2.0
Severity: critical
Justification: breaks unrelated software
The following error message was produced after recent upgrade (solo is a
sudoku game):
solo: symbol lookup error: /usr/lib/libgtk-x11-2.0.so.0: undefined
symbol: g_object_compat_control
-- System
Package: dri-trunk
Version: 2005.01.26-2
Severity: critical
Justification: breaks the whole system
When system is hung with blank screen, impossible to escape to shell
and the only way out is to reboot. File systems (ext3) seem uneffected
and journals were not restored.
Commenting out the line in
On Wednesday 02 February 2005 15:00, you wrote:
* David Baron [EMAIL PROTECTED] [2005-02-02 10:14]:
Package: dri-trunk
Version: 2005.01.26-2
I cannot find such a package in the Debian archive. Do you know where
you obtained in? If not, what does
dpkg -p dri-trunk | grep Maintainer
On Wednesday 02 February 2005 15:00, you wrote:
* David Baron [EMAIL PROTECTED] [2005-02-02 10:14]:
Package: dri-trunk
Version: 2005.01.26-2
I cannot find such a package in the Debian archive. Do you know where
you obtained in? If not, what does
dpkg -p dri-trunk | grep Maintainer
401 - 491 of 491 matches
Mail list logo