M. M. wrote:
> 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?
Fix the themes to work with the current version? If upstream doesn't do it
(in time), it's your
Le Mar 28 août 2012 03:12, Adam Williamson a écrit :
> On 2012-08-25 22:52, M.M. wrote:
>
>> Or is it better to add an explicit "Requires" (for e.g. GNOME Shell
>> 3.4.x) to the Spec files? In such case, is something like "Requires:
>> gnome-shell=3.4.*" allowed to specify all sub-releases belongi
On Mon, Aug 27, 2012 at 06:12:55PM -0700, Adam Williamson wrote:
> On 2012-08-25 22:52, M.M. wrote:
>
> >Or is it better to add an explicit "Requires" (for e.g. GNOME Shell
> >3.4.x) to the Spec files? In such case, is something like "Requires:
> >gnome-shell=3.4.*" allowed to specify all sub-rele
On 2012-08-25 22:52, M.M. wrote:
Or is it better to add an explicit "Requires" (for e.g. GNOME Shell
3.4.x) to the Spec files? In such case, is something like "Requires:
gnome-shell=3.4.*" allowed to specify all sub-releases belonging to
the 3.4 branch?
You can't use wildcards like this, but I
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
I think you should also consider the gnome version in different version of
Fedora.
--
*Yours sincerely,*
*Christopher Meng*
Ambassador/Contributor of Fedora Project and many others.
http://cicku.me
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/lis
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
Dear M.M.,
Unblocking a blocked branch is just as easy as blocking: just creating a
releng work ticket.
Regards,
Patrick
On Aug 26, 2012 10:37 AM, "M.M." wrote:
> OK, I've untagged the packages "zukini", "zukitwo" and "zukiwi" from
> "f18-updates-candidate" and "f19" through "koji-untag-pkg -v
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
Dear M.M.,
1. You can untag them (koji untag-pkg) if the builds where made this
day. If not, you'll need to get it blocked. For the f16/f18 branches,
you can also just make sure not to add it to Bodhi, but I would
suggest untagging them anyway.
2. Yes, they can block package for specific branches,
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
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.
With kind regards,
Patrick
--
deve
12 matches
Mail list logo
