On 01/14/2014 03:04 PM, Malte Forkel wrote:
Am 14.01.2014 10:44, schrieb Alex Mestiashvili:
I am also interested in possible solutions, but I would use git with 2
branches - one for debian package, and one for the modified version.
This way by switching between branches you can build packages y
Am 14.01.2014 10:47, schrieb Jonathan Dowland:
> Is the package in question maintained in a version control repository
> (apt-cache showsrc pkgname | grep ^Vcs might help to determine this).
> If so, you could record the debian-specific changes in a commit and
> either mail the commit to a bug numb
Am 14.01.2014 10:44, schrieb Alex Mestiashvili:
> I am also interested in possible solutions, but I would use git with 2
> branches - one for debian package, and one for the modified version.
>
> This way by switching between branches you can build packages you need.
>
Using git is probably a goo
On 01/13/2014 03:49 PM, Malte Forkel wrote:
Hello,
I'm testing some changes to an existing package which is using format
3.0 (quilt). I have split my changes into two patches: One modifies the
original source, one adapts files in the debian directory.
This approach fails when I build the packag
Is the package in question maintained in a version control repository
(apt-cache showsrc pkgname | grep ^Vcs might help to determine this).
If so, you could record the debian-specific changes in a commit and
either mail the commit to a bug number or push a copy of your modified
checkout somewhere (
Am 14.01.2014 00:32, schrieb Gregory Nowak:
> There may be a better way, but I've used apt-build in the past to do
> something similar. I ran
>
> apt-build source pkg-name
>
> to download the sources. Then I modified them how I wanted, and then
> ran
>
> apt-build install pkg-name
>
> This is f
On Mon, Jan 13, 2014 at 03:49:46PM +0100, Malte Forkel wrote:
> Hello,
>
> I'm testing some changes to an existing package which is using format
> 3.0 (quilt). I have split my changes into two patches: One modifies the
> original source, one adapts files in the debian directory.
>
> This approach
On Sat, Nov 12, 2005 at 12:25:50PM +0100, Markus Grunwald wrote:
> Hello,
Hi
> How do I patch my 2.6 kernel with the new (four numbers) kernel version
> scheme ? Cound't find that in the archives ( or was too dumb to use the cor=
> rect
> search terms...).
>
> To be concrete: which patch do I ne
Eric,
you give a big amount of informations and a clear view to me about lots
of thinks i did not know.
Now I'm sure I have to study...a lot... :)
Also the link are very good!
..now I go to open a new topic on the list .. :)
Thanks again
Lorenzo
* Eric Gaumer <[EMAIL PROTECTED]> [031004, 09:25]
On Sun, 2004-10-03 at 01:04, [EMAIL PROTECTED] wrote:
> Hi Eric and all boys on the list...
>
> > >
> > > To patch the 2.6.8.1 to 2.6.8.1-mm4 should I patch to
> > > 2.6.8.1-mm1, 2.6.8.1-mm2, 2.6.8.1-mm3, and at the end the 2.6.8.1-mm4?
> > > Or can I patch the 2.6.8.1 only with the 2.6.8.1-mm4?
Hi Eric and all boys on the list...
> >
> > To patch the 2.6.8.1 to 2.6.8.1-mm4 should I patch to
> > 2.6.8.1-mm1, 2.6.8.1-mm2, 2.6.8.1-mm3, and at the end the 2.6.8.1-mm4?
> > Or can I patch the 2.6.8.1 only with the 2.6.8.1-mm4?
> >
>
> The mm4 patch is against 2.6.8-1. You should not apply m
On Sat, 2004-10-02 at 12:05, [EMAIL PROTECTED] wrote:
> Hi,
>
> I have just installed the debian kernel source package:
>
> kernel-source-2.6.8
This is not upstream source. That means the patches you speak of will
probably fail (especially the mm patches). If you want to run from the
mm tree, yo
12 matches
Mail list logo
