7:52 a.m.
I saw the announcement a week or so ago but it didn't appear to answer my
questions...
I noticed that EPEL 7 branches were created for several of my packages that
have el6 branches, but not all of them. I didn't request them (yet) so I'm
wondering, are some packages automatically added or did someone else
request them as a dependency to one of their packages? I need to dig
through my packages but I intend to maintain el7 branches of all of my
packages that have el6 branches.
Thanks,
Richard
8:38 a.m.
Hi Richard,
On Thu, Jan 16, 2014 at 6:52 AM, Richard Shaw <hobbes1069(a)gmail.com> wrote:
I noticed that EPEL 7 branches were created for several of my
packages that
have el6 branches, but not all of them. I didn't request them (yet) so I'm
wondering, are some packages automatically added or did someone else request
them as a dependency to one of their packages? I need to dig through my
packages but I intend to maintain el7 branches of all of my packages that
have el6 branches.
It's possible that these were some of the packages that you and I
share as dependencies of MythTV. I requested branches for a lot of my
packages on January 11th using Dennis' procedure with the wiki [1],
but I haven't gotten around to doing the builds in Koji yet. I'm
planning to do the builds by next week.
- Ken
[1] https://lists.fedoraproject.org/pipermail/epel-devel/2014-January/009027....
1:23 p.m.
On Thu, 2014-01-16 at 07:38 -0700, Ken Dreyer wrote:
Hi Richard,
On Thu, Jan 16, 2014 at 6:52 AM, Richard Shaw <hobbes1069(a)gmail.com> wrote:
> I noticed that EPEL 7 branches were created for several of my packages that
> have el6 branches, but not all of them. I didn't request them (yet) so I'm
> wondering, are some packages automatically added or did someone else request
> them as a dependency to one of their packages? I need to dig through my
> packages but I intend to maintain el7 branches of all of my packages that
> have el6 branches.
It's possible that these were some of the packages that you and I
share as dependencies of MythTV. I requested branches for a lot of my
packages on January 11th using Dennis' procedure with the wiki [1],
but I haven't gotten around to doing the builds in Koji yet. I'm
planning to do the builds by next week.
I would've expected anything that exists in epel6 and doesn't exist in
rhel7 to get an epel7 branch. It seems a bit ludicrous doing it manually
- do I have to go through all the deps of any package I want to build
for epel7 and figure this out manually and file branch requests for each
package that isn't in rhel7? yeesh.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
2:10 p.m.
On Thu, Jan 16, 2014 at 1:23 PM, Adam Williamson <awilliam(a)redhat.com>wrote:
On Thu, 2014-01-16 at 07:38 -0700, Ken Dreyer wrote:
> Hi Richard,
>
> On Thu, Jan 16, 2014 at 6:52 AM, Richard Shaw <hobbes1069(a)gmail.com>
wrote:
> > I noticed that EPEL 7 branches were created for several of my packages
that
> > have el6 branches, but not all of them. I didn't request them (yet) so
I'm
> > wondering, are some packages automatically added or did someone else
request
> > them as a dependency to one of their packages? I need to dig through my
> > packages but I intend to maintain el7 branches of all of my packages
that
> > have el6 branches.
>
> It's possible that these were some of the packages that you and I
> share as dependencies of MythTV. I requested branches for a lot of my
> packages on January 11th using Dennis' procedure with the wiki [1],
> but I haven't gotten around to doing the builds in Koji yet. I'm
> planning to do the builds by next week.
I would've expected anything that exists in epel6 and doesn't exist in
rhel7 to get an epel7 branch. It seems a bit ludicrous doing it manually
- do I have to go through all the deps of any package I want to build
for epel7 and figure this out manually and file branch requests for each
package that isn't in rhel7? yeesh.
Agreed... The only argument I can think of against it is that we don't
want
stuff that's not being maintained from automatically making it's way
into el7, but at the same time I don't have my list of packages memorized.
I guess I'll have to come up with some shell-fu to walk through my git
directories looking for instances of el6?
Richard
2:14 p.m.
On Thu, 2014-01-16 at 14:10 -0600, Richard Shaw wrote:
On Thu, Jan 16, 2014 at 1:23 PM, Adam Williamson
<awilliam(a)redhat.com>
wrote:
On Thu, 2014-01-16 at 07:38 -0700, Ken Dreyer wrote:
> Hi Richard,
>
> On Thu, Jan 16, 2014 at 6:52 AM, Richard Shaw
<hobbes1069(a)gmail.com> wrote:
> > I noticed that EPEL 7 branches were created for several of
my packages that
> > have el6 branches, but not all of them. I didn't request
them (yet) so I'm
> > wondering, are some packages automatically added or did
someone else request
> > them as a dependency to one of their packages? I need to
dig through my
> > packages but I intend to maintain el7 branches of all of
my packages that
> > have el6 branches.
>
> It's possible that these were some of the packages that you
and I
> share as dependencies of MythTV. I requested branches for a
lot of my
> packages on January 11th using Dennis' procedure with the
wiki [1],
> but I haven't gotten around to doing the builds in Koji yet.
I'm
> planning to do the builds by next week.
I would've expected anything that exists in epel6 and doesn't
exist in
rhel7 to get an epel7 branch. It seems a bit ludicrous doing
it manually
- do I have to go through all the deps of any package I want
to build
for epel7 and figure this out manually and file branch
requests for each
package that isn't in rhel7? yeesh.
Agreed... The only argument I can think of against it is that we don't
want stuff that's not being maintained from automatically making it's
way into el7
Well, things don't get *built* just because they have a git branch. I
don't think we usually do mass builds in epel, do we?
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
2:14 p.m.
> > > I noticed that EPEL 7 branches were created for several
of my packages
> > > that
> > > have el6 branches, but not all of them. I didn't request them (yet) so
> > > I'm
> > > wondering, are some packages automatically added or did someone else
> > > request
> > > them as a dependency to one of their packages? I need to dig through
> > > my
> > > packages but I intend to maintain el7 branches of all of my packages
> > > that
> > > have el6 branches.
> >
> > It's possible that these were some of the packages that you and I
> > share as dependencies of MythTV. I requested branches for a lot of my
> > packages on January 11th using Dennis' procedure with the wiki [1],
> > but I haven't gotten around to doing the builds in Koji yet. I'm
> > planning to do the builds by next week.
>
> I would've expected anything that exists in epel6 and doesn't exist in
> rhel7 to get an epel7 branch. It seems a bit ludicrous doing it manually
> - do I have to go through all the deps of any package I want to build
> for epel7 and figure this out manually and file branch requests for each
> package that isn't in rhel7? yeesh.
>
Agreed... The only argument I can think of against it is that we don't want
stuff that's not being maintained from automatically making it's way into
el7, but at the same time I don't have my list of packages memorized. I
guess I'll have to come up with some shell-fu to walk through my git
directories looking for instances of el6?
Ultimately it'll be automatically branched but it'll still be up to
the maintainer to build and push the builds so while there might end
up being a branch there it'll be ultimately stagnant and won't have
builds until the maintainer actively does so.
Peter
2:18 p.m.
On Thu, 16 Jan 2014 14:10:31 -0600
Richard Shaw <hobbes1069(a)gmail.com> wrote:
> I would've expected anything that exists in epel6 and
doesn't exist
> in rhel7 to get an epel7 branch. It seems a bit ludicrous doing it
> manually
It's not. There's a bunch of things that are in epel6 that are
pointless to have in epel7.
When we did epel6 we did that from epel5, and I think it worked pretty
poorly. There were packages where maintainers had no interest so
nothing ever got built, there were packages that made no sense anymore,
etc.
> - do I have to go through all the deps of any package I want to
> build for epel7 and figure this out manually and file branch
> requests for each package that isn't in rhel7? yeesh.
Yes, although by 'branch request' it's 'edit wiki page' or 'file
bug
asking maintainer if they want to maintain it in epel7.
> Agreed... The only argument I can think of against it is that
we
> don't
want stuff that's not being maintained from automatically making it's
way into el7, but at the same time I don't have my list of packages
memorized. I guess I'll have to come up with some shell-fu to walk
through my git directories looking for instances of el6?
Right. We want things where someone is actually maintaining them.
We also don't want things like:
renamed packages since epel6.
packages that were dropped since epel6.
packages where maintainers want to maintain a newer version thats named
differently, etc.
Additionally: this sort of thing is suited for the epel-devel
list...where it was discussed before we started...
kevin
3774
days inactive
3774
days old
6 comments
5 participants
participants (5)
-
Adam Williamson -
Ken Dreyer -
Kevin Fenzi -
Peter Robinson -
Richard Shaw