Drew Parsons <[EMAIL PROTECTED]> writes:
[with an unattributed quote from Chris:)]
> > That's no excuse for off-topic posts! I mean, by that logic,
> > *everyone* should move all their questions to deb-laptops.
> Everyone who has a laptop.
No -- general questions about Debian that aren't spec
On Wed, Feb 09, 2000 at 11:04:27AM -0800, Chris Waters wrote:
>
> Actually, it's not really about "newer", it's about having a
> version number that sorts later, so, one possibility is to use a
> special version number that will always sort later. This is the trick
> suggested for custom kernels.
Please format your emails to 76 characters or less.
On Wed, Feb 09, 2000 at 03:33:09PM -0500, [EMAIL PROTECTED] wrote:
> > After doing a apt-get upgrade apt downloaded and installed the debian
>
> Speaking of it, how would one put a package on hold
echo 'package_name hold' | dpkg --set-selection
> After doing a apt-get upgrade apt downloaded and installed the debian
Speaking of it, how would one put a package on hold, apt-get manual doesn't
state how to do it. I always have this problem of getting the same version
package, as I just compiled and installed via 'apt-get upgrade' overinsta
On Wed, Feb 09, 2000 at 11:04:27AM -0800, Chris Waters wrote:
> Drew Parsons <[EMAIL PROTECTED]> writes:
>
> > Running on the theory that it might help speed up my Pentium II system
> > (debatable, but that's beside the point), I've tried
> > recompiling a selection of packages with pentium optimi
Drew Parsons <[EMAIL PROTECTED]> writes:
> Running on the theory that it might help speed up my Pentium II system
> (debatable, but that's beside the point), I've tried
> recompiling a selection of packages with pentium optimisation, downloading
> the debian source and running `./debian/rules bina
Hi,
This was a bug in kernel-package which has now been corrected.
manoj
>>"Daniel" == Daniel J Mashao <[EMAIL PROTECTED]> writes:
Daniel> It looks like you new kernel was made after all. I would copy
Daniel> it to the right place /boot/vmlinuz and use it. I think your
Daniel> p
Hiya,
Thanks for your note. I guess I was a bit misleading about "patching". The
patch I used was a buslogic flashpoint patch for my scsi controller. Not
a kernel patch. I got the new 2.0.29 complete sources before I tried to
compile. Sorry 'bout that...
J. Goldman
--
TO UNSUBSCRIBE FROM THIS M
On Sun, 16 Feb 1997, Jesse Goldman wrote:
> I've run into a snag making a kernel package for version 2.0.29. I got
> new sources, patched them, did a "make-kpkg clean" and then a "make-kpkg
Why patch the new sources? I thought you only needed to patch if you had
2.0.28 sources and wanted to upgra
On 17 Feb 1997 [EMAIL PROTECTED] wrote:
> Hi,
>
> Thank you for the report, this is a real bug in kernel-package
> version 3.16: vi has, for some obscure reason, started to expand info
> to information and so on spontaneously. I generally catch it at it,
Hi,
Thank you for the report, this is a real bug in kernel-package
version 3.16: vi has, for some obscure reason, started to expand info
to information and so on spontaneously. I generally catch it at it,
but this time it snuck up and changed Feb to February in the
changelog, causing d
Hi,
Could you please mail me the debian/changelog file? Also,
could you run dpkg-gencontrol manually and see if it sheds any more
light? Also, Could you give the version of kernel-package installed?
manoj
--
"IT'S THE TWO GODDAMNED CULTURES AGAIN !*! Bit-brained nerdery on on
12 matches
Mail list logo
