On 3/28/12, Stephen Powell wrote:
> (I.e. is this a bug or a feature?)
Haha, indeed! It seems M$ is haunting us, haha...
Regards,
Panayiotis
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
On Tue, 27 Mar 2012 13:28:51 -0400 (EDT), Panayiotis Karabassis wrote:
>
> Thanks! This seems to cover me.
>
> Not much of a terminology, haha, I just had to put the numbers in there
> because there are three version substrings in the .deb file of a kernel
> package! To the confusion adds the fac
Thanks! This seems to cover me.
Not much of a terminology, haha, I just had to put the numbers in there
because there are three version substrings in the .deb file of a kernel
package! To the confusion adds the fact that the version of the source
package (now starts with 2.6 even for 3.0+ kernels)
On Tue, 27 Mar 2012 06:49:58 -0400 (EDT), Panayiotis Karabassis wrote:
>
> I am trying to understand how make-kpkg chooses the versions for the
> packages it creates. Each package has a name(a), which contains a
> version part(a1), as well as a version(b), which is further split in
> upstream vers
Hi,
I am trying to understand how make-kpkg chooses the versions for the
packages it creates. Each package has a name(a), which contains a
version part(a1), as well as a version(b), which is further split in
upstream version(b1) and Debian revision(b2), right? Assuming this, I'll
ask my question i
I know that what I want to do is not really "the Debian Way", but I do not
have an option, so I want to make the best of a bad deal.
I am trying to install Debian onto a Compulab 586BASE which has some
Flash memory built into it. This flash memory is supported by a compulab
supplied driver, part
6 matches
Mail list logo
