hich supports the MX400. The choice of which
version(s) of the Debian nvidia-kernel-* packages to include in
any Debian release is a Debian decision, not an nvidia marketing
decision or plan.
I would suggest that Chris might try contacting [EMAIL PROTECTED]
and/or [EMAIL PROTECTED] for information.
re's
the DM route but DMs can't vote. I help a bit by filing bug
reports (usually upstream) and answering questions on the
debian-users mailing list but while I appreciate the Debian
product, the Debian process is unappealing.
--Mike Bird
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
On Sat May 10 2008 11:03:40 Julien Cristau wrote:
> On Sat, May 10, 2008 at 10:59:44 -0700, Mike Bird wrote:
> > How should a package depend on a package built by module-assistant?
>
> It shouldn't.
Are you saying the dependent package should install successfully
and then fail
On Sat May 10 2008 10:44:48 Philipp Kern wrote:
> On Sat, May 10, 2008 at 10:32:35AM -0700, Mike Bird wrote:
> > nvidia-graphics-drivers was removed from testing ten months ago.[0]
> > New versions cannot transition to testing because of dependencies
> > on modules which are
to testing?[3]
Will nvidia-graphics-drivers be included in EtchAndAHalf?[4]
TIA,
--Mike Bird
[0]
http://packages.qa.debian.org/n/nvidia-graphics-drivers/news/20070710T223919Z.html
[1] e.g.
Package: nvidia-kernel-2.6.24-1-686
Status: install ok installed
Priority: optional
Section: non-free/x11
#x27;t.
Having this information, whether in the package or from some
other source, helps to figure out what changes are needed to
the live conf files, and may even permit a VCS-type automated
merge in some cases.
We very much depend on your freeradius package. Thank you!
--Mike Bird
--
To UNSUBS
m scripts that everyone has for
backups or nagios extensions or adding users or emptying cameras etc etc.
Not everyone writes scripts to the same high standards as Debian but it
would still be very unfortunate if a Debian update broke them.
--Mike Bird
--
To UNSUBSCRIBE, email to [EMAIL PRO
x compliant. Within the Debian world, this is a dash
bug. Possible solutions include Debian-specific patches to either
make dash's test compatible or to disable dash's incompatible test.
--Mike Bird
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe
fference between a working .deb and an "official" .deb is that an
"official" Debian maintainer has endured Debian's tedious hazing ritual.
--Mike Bird
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
use if you wish, but never
never never enable IPv6 by default.
--Mike Bird
[ [EMAIL PROTECTED] cc per request ]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
mage packages:
2006-12-12 14:07:09 upgrade initramfs-tools 0.85b 0.85c
2006-12-28 06:32:25 upgrade initramfs-tools 0.85e 0.85e
2006-12-30 11:31:37 upgrade mdadm 2.5.6-6 2.5.6-7
--Mike Bird
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
he Debian release protocol, not a package.
Tetex/Texlive situation is similar. There may be others.
--Mike Bird
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
that Tetex remains the default and Tetex dependencies are unaffected.
Frank's plan provides a good starting point when that time comes for
each Tetex user when the switch to Texlive becomes inescapable.
Please reconsider,
--Mike Bird
[0] http://www.tug.org/tetex/
13 matches
Mail list logo