FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Packaging

 
 
LinkBack Thread Tools
 
Old 05-07-2011, 04:11 PM
Kevin Fenzi
 
Default input on a conflicts case

Greetings.

I'm looking at the supybot-gribble package (under review).
https://bugzilla.redhat.com/show_bug.cgi?id=693664

Currently it Conflicts: supybot.
It's not really falling under any of the current cases on
http://fedoraproject.org/wiki/Packaging:Conflicts
but I think it might be another case to add next to compat packages.

Background:

supybot is a irc bot written in python. It's already in Fedora.
Development is very slow. Currently many of the database functions in
it don't work because they still haven't switched from sqlite1 for
example. We also have several plugins that use it.

supybot-gribble is a blessed rapid development fork. Changes here are
fast paced and much more current. Once patches here look good and
stable they are submitted back to the main supybot branch. It's much
like a 'supybot-rawhide' or devel.

The two packages share the name and python tree files. Upstream has no
desire to rename things in supybot-gribble as this will make it harder
to fold changes back into supybot. There is no great need to run both
at the same time on the same machine.

In the review I suggested we just let them conflict and setup the
plugins so they would work with either (require /usr/bin/supybot). To
me this seems like an acceptable Conflicts case related to the 'compat
packages' case, except in this case it's 'newer/rawhide/ng version'.

Thoughts? Flames?

kevin
--
packaging mailing list
packaging@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/packaging
 
Old 05-07-2011, 04:51 PM
Manuel Wolfshant
 
Default input on a conflicts case

On 05/07/2011 07:11 PM, Kevin Fenzi wrote:
> Greetings.
>
> I'm looking at the supybot-gribble package (under review).
> https://bugzilla.redhat.com/show_bug.cgi?id=693664
>
> Currently it Conflicts: supybot.
> It's not really falling under any of the current cases on
> http://fedoraproject.org/wiki/Packaging:Conflicts
> but I think it might be another case to add next to compat packages.
>
> Background:
>
> supybot is a irc bot written in python. It's already in Fedora.
> Development is very slow. Currently many of the database functions in
> it don't work because they still haven't switched from sqlite1 for
> example. We also have several plugins that use it.
>
> supybot-gribble is a blessed rapid development fork. Changes here are
> fast paced and much more current. Once patches here look good and
> stable they are submitted back to the main supybot branch. It's much
> like a 'supybot-rawhide' or devel.
>
> The two packages share the name and python tree files. Upstream has no
> desire to rename things in supybot-gribble as this will make it harder
> to fold changes back into supybot. There is no great need to run both
> at the same time on the same machine.
>
> In the review I suggested we just let them conflict and setup the
> plugins so they would work with either (require /usr/bin/supybot). To
> me this seems like an acceptable Conflicts case related to the 'compat
> packages' case, except in this case it's 'newer/rawhide/ng version'.
>
> Thoughts? Flames?

Seems sane so I am with you on this one.
--
packaging mailing list
packaging@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/packaging
 
Old 05-09-2011, 12:30 PM
Jon Ciesla
 
Default input on a conflicts case

Manuel Wolfshant wrote:
> On 05/07/2011 07:11 PM, Kevin Fenzi wrote:
>
>> Greetings.
>>
>> I'm looking at the supybot-gribble package (under review).
>> https://bugzilla.redhat.com/show_bug.cgi?id=693664
>>
>> Currently it Conflicts: supybot.
>> It's not really falling under any of the current cases on
>> http://fedoraproject.org/wiki/Packaging:Conflicts
>> but I think it might be another case to add next to compat packages.
>>
>> Background:
>>
>> supybot is a irc bot written in python. It's already in Fedora.
>> Development is very slow. Currently many of the database functions in
>> it don't work because they still haven't switched from sqlite1 for
>> example. We also have several plugins that use it.
>>
>> supybot-gribble is a blessed rapid development fork. Changes here are
>> fast paced and much more current. Once patches here look good and
>> stable they are submitted back to the main supybot branch. It's much
>> like a 'supybot-rawhide' or devel.
>>
>> The two packages share the name and python tree files. Upstream has no
>> desire to rename things in supybot-gribble as this will make it harder
>> to fold changes back into supybot. There is no great need to run both
>> at the same time on the same machine.
>>
>> In the review I suggested we just let them conflict and setup the
>> plugins so they would work with either (require /usr/bin/supybot). To
>> me this seems like an acceptable Conflicts case related to the 'compat
>> packages' case, except in this case it's 'newer/rawhide/ng version'.
>>
>> Thoughts? Flames?
>>
>
> Seems sane so I am with you on this one.
> --
> packaging mailing list
> packaging@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/packaging
>
I am as well, tentatively. My yum-math is weak, if we file-require
/usr/bin/supybot, which will get pulled in by default, and is it the one
we want, for some value of "we"?

-J

--
in your fear, seek only peace
in your fear, seek only love

-d. bowie

--
packaging mailing list
packaging@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/packaging
 
Old 05-09-2011, 11:44 PM
Toshio Kuratomi
 
Default input on a conflicts case

On Sat, May 07, 2011 at 10:11:38AM -0600, Kevin Fenzi wrote:
> Greetings.
>
> I'm looking at the supybot-gribble package (under review).
> https://bugzilla.redhat.com/show_bug.cgi?id=693664
>
> Currently it Conflicts: supybot.
> It's not really falling under any of the current cases on
> http://fedoraproject.org/wiki/Packaging:Conflicts
> but I think it might be another case to add next to compat packages.
>
> Background:
>
> supybot is a irc bot written in python. It's already in Fedora.
> Development is very slow. Currently many of the database functions in
> it don't work because they still haven't switched from sqlite1 for
> example. We also have several plugins that use it.
>
> supybot-gribble is a blessed rapid development fork. Changes here are
> fast paced and much more current. Once patches here look good and
> stable they are submitted back to the main supybot branch. It's much
> like a 'supybot-rawhide' or devel.
>
> The two packages share the name and python tree files. Upstream has no
> desire to rename things in supybot-gribble as this will make it harder
> to fold changes back into supybot. There is no great need to run both
> at the same time on the same machine.
>
> In the review I suggested we just let them conflict and setup the
> plugins so they would work with either (require /usr/bin/supybot). To
> me this seems like an acceptable Conflicts case related to the 'compat
> packages' case, except in this case it's 'newer/rawhide/ng version'.
>
> Thoughts? Flames?
>

Alternative: Let's upgrade the supybot package in Fedora to use
supybot-gribble instead.

Thoughts on the pros and cons of that vs a conflicting package?

-Toshio
--
packaging mailing list
packaging@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/packaging
 
Old 05-09-2011, 11:51 PM
Kevin Fenzi
 
Default input on a conflicts case

On Mon, 9 May 2011 16:44:53 -0700
Toshio Kuratomi <a.badger@gmail.com> wrote:

>
> Alternative: Let's upgrade the supybot package in Fedora to use
> supybot-gribble instead.
>
> Thoughts on the pros and cons of that vs a conflicting package?

Yeah, we thought about that...

Pros:

- No conflict.
- More things work (like the plugins that need sqlite)

Cons:

- Doesn't work on epel5.
- Might have breakage from time to time since it's a devel version.

I'd be ok with this approach if we kept supybot in epel5 and if the
supybot maintainer is on board.

kevin

--
packaging mailing list
packaging@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/packaging
 
Old 05-10-2011, 01:58 PM
Tom Callaway
 
Default input on a conflicts case

On 05/09/2011 07:51 PM, Kevin Fenzi wrote:

> I'd be ok with this approach if we kept supybot in epel5 and if the
> supybot maintainer is on board.

I see no reason that an older version of supybot couldn't live on in epel5.

~tom

==
Fedora Project
--
packaging mailing list
packaging@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/packaging
 

Thread Tools




All times are GMT. The time now is 10:08 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org