Thank you.
2012/12/27 Thorsten Leemhuis
> On 27.12.2012 10:34, M.M. wrote:
> > Is kernel 3.7 expected to be available for Fedora 18?
> > If so, can you estimate how long it will take?
> > Thank you.
>
> See http://jwboyer.livejournal.com/46002.html
> Quoting one part:
>
> """
> > Fedora 18: […]
Is kernel 3.7 expected to be available for Fedora 18?
If so, can you estimate how long it will take?
Thank you.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
OK, thanks for your answers.
I've submitted a new request for each package:
https://bugzilla.redhat.com/show_bug.cgi?id=874718
https://bugzilla.redhat.com/show_bug.cgi?id=874719
https://bugzilla.redhat.com/show_bug.cgi?id=874721
Regards,
M.M.
--
devel mailing list
devel@lists.fedoraproject.org
ht
I have requested Release Engineering to unblock some packages,
which previously had been blocked on some branches:
https://fedorahosted.org/rel-eng/ticket/5387
I have been told that those packages must be reviewed again in order to be
unblocked.
I'm not 100% sure of what to do. Do I have to open a
OK, here is the ticket I filed to rel-eng:
https://fedorahosted.org/rel-eng/ticket/5307
Now, I'm unsure on how to deal with the branch "master": should I keep
it up-to-date even if it's related to Fedora 19? Or, instead, when
updating the package, should I update only the branch "f17", excluding
e
OK, thank you.
Just another question.
When I'll be updating those packages, what should I do?
Should I push the changes only to the f17 branch on Git? Or should I
push them to all branches anyway and only avoid requesting builds on
Koji for the f18/f19 branches?
2012/8/26 Patrick Uiterwijk :
> Dea
OK, I've untagged the packages "zukini", "zukitwo" and "zukiwi" from
"f18-updates-candidate" and "f19" through "koji-untag-pkg -v --all
f<18-updates-candidate/19> " (I couldn't untag
them from "f18" since admin privileges are needed for that).
When a version compatible with i.e. Fedora 18 or 19 is
Patrick Uiterwijk wrote:
> Hello M.M.,
>
> As soon as you request the git repo, you will automatically get the
> devel (F19) branch.
> You could do two things:
> 1. Just make no builds for any other branches, then it won't get in there.
> 2. Request rel-eng to block the package for the devel branch
Hi everyone.
I'm packaging some themes for GNOME Shell, which are compatible with only
GNOME 3.4 (i.e. can be installed with success only on Fedora 17).
What do you think is the best way to act?
Can I submit the package to the F17 branch only, excluding everyone else
(also master, i.e. F19)?
Or is
