On 2015-01-29, 01:29 GMT, Peter Hutterer wrote:
I don't have numbers on how many packages have this need but I predict that
the efforts to get this to work, test it, deploy it, etc. are vastly greater
than the time saved not having to retire a package :)
Certainly, but
a) we are geeks, so we
On Thu, 29 Jan 2015 09:09:04 +0100
Matěj Cepl mc...@cepl.eu wrote:
On 2015-01-29, 01:29 GMT, Peter Hutterer wrote:
I don't have numbers on how many packages have this need but I
predict that the efforts to get this to work, test it, deploy it,
etc. are vastly greater than the time saved
On Wed, 28 Jan 2015 20:48:02 +0100
Matěj Cepl mc...@cepl.eu wrote:
Hi,
this is a question which I have encountered couple of times, but
I have always forgot to ask about it: is it possible to have
a package without Rawhide (devel) branch?
Nope.
I have just created (and got approved)
On 2015-01-28, 21:10 GMT, Kevin Fenzi wrote:
I have just created (and got approved) python-mako1.0 as
a compatibility package for EPEL-6. When I asked for the new
repo for it, I expect to get also devel/Rawhide branch for it.
However, I don't see any purpose of it. Should I just orphan the
On Thu, Jan 29, 2015 at 01:04:34AM +0100, Matěj Cepl wrote:
On 2015-01-28, 21:10 GMT, Kevin Fenzi wrote:
I have just created (and got approved) python-mako1.0 as
a compatibility package for EPEL-6. When I asked for the new
repo for it, I expect to get also devel/Rawhide branch for it.
On Thu, Jan 29, 2015 at 01:04:34AM +0100, Matěj Cepl wrote:
And couldn't we make the script which builds the repos
understand some syntax extension to do it? E.g., what about
Perhaps it would do just the retirement of devel branch.
What about that?
The process is going to change soon:
Hi,
this is a question which I have encountered couple of times, but
I have always forgot to ask about it: is it possible to have
a package without Rawhide (devel) branch?
I have just created (and got approved) python-mako1.0 as
a compatibility package for EPEL-6. When I asked for the new
