also sprach Turbo Fredriksson <[EMAIL PROTECTED]> [2005.08.11.1026 +0200]:
> I need to make some local kernel patch packages. Anyone know how
> to do this (reference to doc ok :).
Unfortunately, such a doc does not exist. Nevertheless, the process
is quite simple. I would suggest tha
I need to make some local kernel patch packages. Anyone
know how to do this (reference to doc ok :).
--
Clinton smuggle NSA Kennedy genetic spy supercomputer jihad congress
killed Iran cracking Delta Force Waco, Texas SDI
[See http://www.aclu.org/echelonwatch/index.html for more about this
On Mon, 18 Mar 2002 20:49, Ian Duggan wrote:
> > If you want an orig.tar.gz then you have to have one there before running
> > dpkg-buildpackage.
> >
> > As for kernel-patch packages, if your package is like the ones I manage
> > then you'll have a new patch to
> If you want an orig.tar.gz then you have to have one there before running
> dpkg-buildpackage.
>
> As for kernel-patch packages, if your package is like the ones I manage then
> you'll have a new patch to add to the package every few weeks and no other
> updates. So th
On Mon, 18 Mar 2002 20:49, Ian Duggan wrote:
> > If you want an orig.tar.gz then you have to have one there before running
> > dpkg-buildpackage.
> >
> > As for kernel-patch packages, if your package is like the ones I manage
> > then you'll have a new patch to
> If you want an orig.tar.gz then you have to have one there before running
> dpkg-buildpackage.
>
> As for kernel-patch packages, if your package is like the ones I manage then
> you'll have a new patch to add to the package every few weeks and no other
> updates. So th
On Mon, 18 Mar 2002 17:35, Ian Duggan wrote:
> Are kernel-patch packages considered native or non-native? I am trying
> to understand what the final set of files should be when I am done
> packaging a kernel-patch. Right now, I have the following files:
>
> kernel-patch-preem
Are kernel-patch packages considered native or non-native? I am trying
to understand what the final set of files should be when I am done
packaging a kernel-patch. Right now, I have the following files:
kernel-patch-preempt_20020315.dsc
kernel-patch-preempt_20020315.tar.gz
On Mon, 18 Mar 2002 17:35, Ian Duggan wrote:
> Are kernel-patch packages considered native or non-native? I am trying
> to understand what the final set of files should be when I am done
> packaging a kernel-patch. Right now, I have the following files:
>
> kernel-patch-preem
Are kernel-patch packages considered native or non-native? I am trying
to understand what the final set of files should be when I am done
packaging a kernel-patch. Right now, I have the following files:
kernel-patch-preempt_20020315.dsc
kernel-patch-preempt_20020315.tar.gz
On Thu, Mar 14, 2002 at 11:59:42AM +0100, Russell Coker wrote:
> My kernel-patch packages were all built against the source tree from
> ftp.kernel.org. All except two of them came from the upstream that way.
>
> If someone reports a bug against these packages about problems applyi
ve patches for 2.4.13-ac. I have patches for most of
> the kernels between 2.4.4 and 2.4.18, as well as 2.5.1 through 2.5.6 in
> there.
In my kernel patch packages I dumped support for <=2.4.9 when it was
discovered to have security holes.
Then 2.4.10 had Ext2/Lilo issues so I dumped supp
On Thu, Mar 14, 2002 at 11:59:42AM +0100, Russell Coker wrote:
> My kernel-patch packages were all built against the source tree from
> ftp.kernel.org. All except two of them came from the upstream that way.
>
> If someone reports a bug against these packages about problems applyi
> Why does the patch require 2.4.13-ac7?
>
> Why would you want to support an ancient pre-release of the kernel anyway?
>
> Why doesn't it apply against 2.4.13?
It doesn't just have patches for 2.4.13-ac. I have patches for most of
the kernels between 2.4.4 and 2.4.18, as well as 2.5.1 through
ve patches for 2.4.13-ac. I have patches for most of
> the kernels between 2.4.4 and 2.4.18, as well as 2.5.1 through 2.5.6 in
> there.
In my kernel patch packages I dumped support for <=2.4.9 when it was
discovered to have security holes.
Then 2.4.10 had Ext2/Lilo issues so I dumped supp
> Why does the patch require 2.4.13-ac7?
>
> Why would you want to support an ancient pre-release of the kernel anyway?
>
> Why doesn't it apply against 2.4.13?
It doesn't just have patches for 2.4.13-ac. I have patches for most of
the kernels between 2.4.4 and 2.4.18, as well as 2.5.1 through
On Thu, 14 Mar 2002 03:43, Ian Duggan wrote:
> I'm packaging some kernel patches that apply against some of the -ac
> kernel trees, however it looks like dh_installkpatches isn't designed to
> handle this. Here is the relevant line:
>
> $kv[0] =~ m/^(\d+\.\d+)\.(\d+)$/ or die "Malformed kernel vers
ebian kernels and modify the patches for them.
>
> How should this be handled?
My kernel-patch packages were all built against the source tree from
ftp.kernel.org. All except two of them came from the upstream that way.
If someone reports a bug against these packages about problems applyin
On Thu, 14 Mar 2002 03:43, Ian Duggan wrote:
> I'm packaging some kernel patches that apply against some of the -ac
> kernel trees, however it looks like dh_installkpatches isn't designed to
> handle this. Here is the relevant line:
>
> $kv[0] =~ m/^(\d+\.\d+)\.(\d+)$/ or die "Malformed kernel ver
#include
Ian Duggan wrote on Wed Mar 13, 2002 um 04:07:46PM:
> When packaging kernel patches, should the patches be against the debian
> kernel sources or the stock kernels? I have several patches I'm
Idealy against the Debian kernel sources.
> packaging for the stock kernels. It would be a lot
ebian kernels and modify the patches for them.
>
> How should this be handled?
My kernel-patch packages were all built against the source tree from
ftp.kernel.org. All except two of them came from the upstream that way.
If someone reports a bug against these packages about problems applyin
#include
Ian Duggan wrote on Wed Mar 13, 2002 um 04:07:46PM:
> When packaging kernel patches, should the patches be against the debian
> kernel sources or the stock kernels? I have several patches I'm
Idealy against the Debian kernel sources.
> packaging for the stock kernels. It would be a lo
I'm packaging some kernel patches that apply against some of the -ac
kernel trees, however it looks like dh_installkpatches isn't designed to
handle this. Here is the relevant line:
$kv[0] =~ m/^(\d+\.\d+)\.(\d+)$/ or die "Malformed kernel version:
`$kv[0]'";
and the error:
dh_installkpatches
M
When packaging kernel patches, should the patches be against the debian
kernel sources or the stock kernels? I have several patches I'm
packaging for the stock kernels. It would be a lot of work to pull down
all the various debian kernels and modify the patches for them.
How should this be handle
I'm packaging some kernel patches that apply against some of the -ac
kernel trees, however it looks like dh_installkpatches isn't designed to
handle this. Here is the relevant line:
$kv[0] =~ m/^(\d+\.\d+)\.(\d+)$/ or die "Malformed kernel version:
`$kv[0]'";
and the error:
dh_installkpatches
When packaging kernel patches, should the patches be against the debian
kernel sources or the stock kernels? I have several patches I'm
packaging for the stock kernels. It would be a lot of work to pull down
all the various debian kernels and modify the patches for them.
How should this be handl
26 matches
Mail list logo
