On Fri, Jul 11, 2003 at 12:27:38PM +0200, GCS wrote:
> On Fri, Jul 11, 2003 at 09:47:57AM +0100, Colin Watson <[EMAIL PROTECTED]>
> wrote:
> > The simplest way is just to apply the patch directly and rebuild! DBS,
> > dpatch, and the like are usually massive overkill for small packages or
> > smal
On Fri, Jul 11, 2003 at 04:51:32AM -0400, Morgon Kanter <[EMAIL PROTECTED]>
wrote:
> Why not just use dpatch? It does all this and more for you.
I did not know this before. It was new to me, and I still have a
problem with this: /usr/share/dpatch/dpatch.make, line 30 is:
if $$patch -patch >$$sta
On Fri, Jul 11, 2003 at 11:14:56AM +0200, Luk Claes wrote:
> What does the folowing 'problem' mean:
>
> The package has not yet entered testing even though the 10-day delay is
> over.
It means that there's another problem. If you tell us the package name
we'll be able to look into it in more deta
On Friday, July 11, 2003, at 02:14 AM, Luk Claes wrote:
What does the folowing 'problem' mean:
The package has not yet entered testing even though the 10-day delay is
over.
The urgency=low upload has not entered testing for one of the other
reasons listed at:
http://www.debian.org/doc/man
Hi
What does the folowing 'problem' mean:
The package has not yet entered testing even though the 10-day delay is
over.
Kind regards
Luk
---
GPG Fingerprint : C061 8F2E EA93 43DE 08D5 71EA 02DF 840B 1B57 0E7C
On Friday, July 11, 2003, at 01:33 AM, GCS wrote:
I would like to ask how can I add a patch to an existing package? I
have created debian/patches, placed my patch there. Adding a 'patch
-p1 <
..' seems to be ok for the first time. But second time, it fails, as
the
source is already patched.
On Fri, Jul 11, 2003 at 10:33:53AM +0200, GCS wrote:
> I would like to ask how can I add a patch to an existing package?
The simplest way is just to apply the patch directly and rebuild! DBS,
dpatch, and the like are usually massive overkill for small packages or
small patch sets.
--
Colin Wats
On Fri, Jul 11, 2003 at 12:27:38PM +0200, GCS wrote:
> On Fri, Jul 11, 2003 at 09:47:57AM +0100, Colin Watson <[EMAIL PROTECTED]> wrote:
> > The simplest way is just to apply the patch directly and rebuild! DBS,
> > dpatch, and the like are usually massive overkill for small packages or
> > small p
> I would like to ask how can I add a patch to an existing package? I
> have created debian/patches, placed my patch there. Adding a 'patch -p1 <
> ..' seems to be ok for the first time. But second time, it fails, as the
> source is already patched. How can I use a stamp file maybe showing it
> is
Hi all,
I would like to ask how can I add a patch to an existing package? I
have created debian/patches, placed my patch there. Adding a 'patch -p1 <
..' seems to be ok for the first time. But second time, it fails, as the
source is already patched. How can I use a stamp file maybe showing it
is
On Fri, Jul 11, 2003 at 04:51:32AM -0400, Morgon Kanter <[EMAIL PROTECTED]> wrote:
> Why not just use dpatch? It does all this and more for you.
I did not know this before. It was new to me, and I still have a
problem with this: /usr/share/dpatch/dpatch.make, line 30 is:
if $$patch -patch >$$stam
On Fri, Jul 11, 2003 at 11:14:56AM +0200, Luk Claes wrote:
> What does the folowing 'problem' mean:
>
> The package has not yet entered testing even though the 10-day delay is
> over.
It means that there's another problem. If you tell us the package name
we'll be able to look into it in more deta
I found the instructions you were talking about.
If you are going to adopt a package, retitle its bug to replace `O' with >`ITA', in order for other people to know the package is being adopted and to >prevent its automatic removal from the archive.
This is done.
To actually adopt the package,
[EMAIL PROTECTED] wrote*:
>
>> Include the following line in fda's changelog file:
>>
>> * New maintainer. (closes: #192657)
>>
[... same for judy ...]
>I'm not sure about this. These 'bugs' are just the report that the package
>is orphan aren't they? The only thing I have to do is send a mail
Include the following line in fda's changelog file:
* New maintainer. (closes: #192657)
And the following line judy's changelog file:
* New maintainer. (closes: #172772)
I'm not sure about this. These 'bugs' are just the report that the package
is orphan aren't they? The only thing
On Friday, July 11, 2003, at 02:14 AM, Luk Claes wrote:
What does the folowing 'problem' mean:
The package has not yet entered testing even though the 10-day delay is
over.
The urgency=low upload has not entered testing for one of the other
reasons listed at:
http://www.debian.org/doc/manuals/
Hi
What does the folowing 'problem' mean:
The package has not yet entered testing even though the 10-day delay is
over.
Kind regards
Luk
---
GPG Fingerprint : C061 8F2E EA93 43DE 08D5 71EA 02DF 840B 1B57 0E7C
--
To UNSUBSCRIBE,
On Friday, July 11, 2003, at 01:33 AM, GCS wrote:
I would like to ask how can I add a patch to an existing package? I
have created debian/patches, placed my patch there. Adding a 'patch
-p1 <
..' seems to be ok for the first time. But second time, it fails, as
the
source is already patched.
You
On Fri, Jul 11, 2003 at 10:33:53AM +0200, GCS wrote:
> I would like to ask how can I add a patch to an existing package?
The simplest way is just to apply the patch directly and rebuild! DBS,
dpatch, and the like are usually massive overkill for small packages or
small patch sets.
--
Colin Wats
> I would like to ask how can I add a patch to an existing package? I
> have created debian/patches, placed my patch there. Adding a 'patch -p1 <
> ..' seems to be ok for the first time. But second time, it fails, as the
> source is already patched. How can I use a stamp file maybe showing it
> is
Hi all,
I would like to ask how can I add a patch to an existing package? I
have created debian/patches, placed my patch there. Adding a 'patch -p1 <
..' seems to be ok for the first time. But second time, it fails, as the
source is already patched. How can I use a stamp file maybe showing it
is
I found the instructions you were talking about.
If you are going to adopt a package, retitle its bug to replace `O' with >`ITA', in order for other people to know the package is being adopted and to >prevent its automatic removal from the archive.
This is done.
To actually adopt the package,
[EMAIL PROTECTED] wrote*:
>
>> Include the following line in fda's changelog file:
>>
>> * New maintainer. (closes: #192657)
>>
[... same for judy ...]
>I'm not sure about this. These 'bugs' are just the report that the package
>is orphan aren't they? The only thing I have to do is send a mail
Include the following line in fda's changelog file:
* New maintainer. (closes: #192657)
And the following line judy's changelog file:
* New maintainer. (closes: #172772)
I'm not sure about this. These 'bugs' are just the report that the package
is orphan aren't they? The only thing I
24 matches
Mail list logo
