Martin Costabel wrote:
> Alexander Hansen wrote:
>> Martin Costabel wrote:
>>> Chupacerveza wrote:
>>>
I have a best practices question: if all I'm doing is updating the
name of the maintainer and some usage notes, should I bump the
revision number?
thanks,
>>> Ye
Alexander Hansen wrote:
> Martin Costabel wrote:
>> Chupacerveza wrote:
>>
>>> I have a best practices question: if all I'm doing is updating the name
>>> of the maintainer and some usage notes, should I bump the revision number?
>>> thanks,
>>>
>> Yes. Anything that changes the contents
Martin Costabel wrote:
> Chupacerveza wrote:
>
>> I have a best practices question: if all I'm doing is updating the name
>> of the maintainer and some usage notes, should I bump the revision number?
>> thanks,
>>
>
> Yes. Anything that changes the contents of the *.deb file needs a new r
If I'm making no change to the .patch file at this time, must I submit
it anyway with the new .info? I'm inclined to just submit the .info
file, but if this causes problems with the review process then I'll
post both.
Thanks,
Robert
Daniel Macks wrote:
> On Fri, Jul 17, 2009 at 12:00:51PM -0500, Chupacerveza wrote:
>> hmmm, when building in maintainer mode:
>>
>> ... has a preferred Depends on python25-socket, but python25-socket is
>> an obsolete package.
>>
>> Now, another user has asked that I upgrade this to use 2.6, but I
On Fri, Jul 17, 2009 at 12:00:51PM -0500, Chupacerveza wrote:
> hmmm, when building in maintainer mode:
>
> ... has a preferred Depends on python25-socket, but python25-socket is
> an obsolete package.
>
> Now, another user has asked that I upgrade this to use 2.6, but I
> wanted to get the quick
hmmm, when building in maintainer mode:
... has a preferred Depends on python25-socket, but python25-socket is
an obsolete package.
Now, another user has asked that I upgrade this to use 2.6, but I
wanted to get the quick maintainer change in first and then come back
and make those changes.
I'm
This is good to know! Thanks!
monipol wrote:
> On 17/07/2009, at 09:37, Martin Costabel wrote:
>> Chupacerveza wrote:
>>> I have a best practices question: if all I'm doing is updating the name
>>> of the maintainer and some usage notes, should I bump the revision
>>> number?
>>> thanks,
>>
>> Ye
On 17/07/2009, at 09:37, Martin Costabel wrote:
> Chupacerveza wrote:
>> I have a best practices question: if all I'm doing is updating the
>> name
>> of the maintainer and some usage notes, should I bump the revision
>> number?
>> thanks,
>
> Yes. Anything that changes the contents of the *.d
Okay, thanks Martin! --robert
Martin Costabel wrote:
> Chupacerveza wrote:
>> I have a best practices question: if all I'm doing is updating the
>> name of the maintainer and some usage notes, should I bump the
>> revision number?
>> thanks,
>
> Yes. Anything that changes the contents of the *
Chupacerveza wrote:
> I have a best practices question: if all I'm doing is updating the name
> of the maintainer and some usage notes, should I bump the revision number?
> thanks,
Yes. Anything that changes the contents of the *.deb file needs a new rev.
--
Martin
I have a best practices question: if all I'm doing is updating the name
of the maintainer and some usage notes, should I bump the revision number?
thanks,
Robert
--
Enter the BlackBerry Developer Challenge
This is your
I'm in Europe for a couple more days so I've been awake for hours. :-)
It's possible that packages may build differently against your X11 beta
than against the released macosxforge X11 or Apple's official setup.
You don't have to downgrade, but be prepared for that possibility.
Chupacerveza wrot
Wow, everyone is awake and on the ball this morning! I just started my
first cup of coffee!
Last question for now, I have X11-2.4.0_beta2 installed, it doesn't seem
to me that this should make any difference for package maintenance, but
I figured it would be better to ask.
Oh, I'm still watchi
Robert T Wyatt wrote:
> Howdy fink developers,
>
> Murali is busy with other projects and so I'm interested in taking over
> maintainership of denyhosts-py25. Should I simply submit a package on
> the tracker with the new maintainer info?
>
>
Sure. If you're just going to take over maintainer
On 12/07/2009, at 12:15, Robert T Wyatt wrote:
> Murali is busy with other projects and so I'm interested in taking
> over
> maintainership of denyhosts-py25. Should I simply submit a package on
> the tracker with the new maintainer info?
Yep, and please add a comment stating that the previous m
Charles Lepple wrote:
> On Sun, Jul 12, 2009 at 11:15 AM, Robert T
> Wyatt wrote:
>
>> Oh, I also need to subscribe to this list from a different address as
>> this one will be retired one day. Here would be my preferred:
>> chupacerv...@gmail.com
>>
>
> Robert:
>
> You can manage your subs
On Sun, Jul 12, 2009 at 11:15 AM, Robert T
Wyatt wrote:
> Oh, I also need to subscribe to this list from a different address as
> this one will be retired one day. Here would be my preferred:
> chupacerv...@gmail.com
Robert:
You can manage your subscription info here:
https://lists.sourceforge.n
Howdy fink developers,
Murali is busy with other projects and so I'm interested in taking over
maintainership of denyhosts-py25. Should I simply submit a package on
the tracker with the new maintainer info?
Oh, I also need to subscribe to this list from a different address as
this one will be
19 matches
Mail list logo
