Re: Packaging software compatible with only one Fedora release
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 job as the package maintainer to do it. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging software compatible with only one Fedora release
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 belonging to the 3.4 branch? You can't use wildcards like this, but I wonder if you could do this: Requires: gnome-shell = 3.3 Requires: gnome-shell 3.5 I've never actually tried that, but it might work. If it doesn't, someone tell me, cos I'd like to know =) This only works as long as there is a single package providing gnome-shell in the repo, as soon as someone releases a compat package this will fail big time. The reqs are evaluated separately, so rpm thinks a system with something providing gnome-shell 3.2 + something else providing gnome-shell 3.6 will work with your package. In rpm, to restrict a version range on both ends, you need to combine requires with conflicts (requires A = x, conflicts A = y). There is no way to specify a range not open to infinity on one end as an atomic requirement (it's an annoying limitation, but the positive side-effect is that it forced people to give up on strict version locking and packages upgrade by default). -- Nicolas Mailhot -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging software compatible with only one Fedora release
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 everyone else? By the way, in the table tags here: http://koji.fedoraproject.org/koji/packageinfo?packageID=13861 a tag dist-f15 is shown. Should I request also that to be blocked? Thank you. M.M. 2012/8/26 Patrick Uiterwijk puiterw...@gmail.com 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, and thus can block it for any branch except one. But if you do this, I would suggest to explain this in the ticket so they won't accidentally remove the branch you do want. Adding the specific version can be useful to prevent someone from installing it over a koji- or local build of gnome-shell indeed. Regards, Patrick -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging software compatible with only one Fedora release
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 wonder if you could do this: Requires: gnome-shell = 3.3 Requires: gnome-shell 3.5 I've never actually tried that, but it might work. If it doesn't, someone tell me, cos I'd like to know =) (note I tried to keep in mind GNOME naming convention, there: betas of GNOME 3.4 would have been versioned 3.3.x and would presumably have worked with this theme.) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging software compatible with only one Fedora release
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-releases belonging to
the 3.4 branch?
You can't use wildcards like this, but I wonder if you could do this:
Requires: gnome-shell = 3.3
Requires: gnome-shell 3.5
Yes. For instance, from the bzrtools spec file (meant to work with
a specific version of bzr):
%global bzrver 2.3
%%global bzrnextver 2.4
[...]
Requires: bzr = %{bzrver}, bzr %{bzrnextver}.0
-Toshio
pgp0gxLHzXIfg.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging software compatible with only one Fedora release
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 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging software compatible with only one Fedora release
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. With kind regards, Patrick Thank you. 1. Can I delete builds for undesired branches, if they have been created already? 2. Can I request rel-eng to block the package for every undesired branch (i.e. also F18)? Moreover, if possible, wouldn't it be better to add also an explicit, stricter constraint on the version of Gnome Shell to the Requires: field of the Spec file, as I suggested in my previous message? Regards, M.M. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging software compatible with only one Fedora release
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, and thus can block it for any branch except one. But if you do this, I would suggest to explain this in the ticket so they won't accidentally remove the branch you do want. Adding the specific version can be useful to prevent someone from installing it over a koji- or local build of gnome-shell indeed. Regards, Patrick -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging software compatible with only one Fedora release
OK, I've untagged the packages zukini, zukitwo and zukiwi from f18-updates-candidate and f19 through koji-untag-pkg -v --all f18-updates-candidate/19 zukini/zukitwo/zukiwi (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 published by the developers, will I be allowed to I ask rel-eng to un-block the package for the related branch? Thank you again. 2012/8/26 Patrick Uiterwijk puiterw...@gmail.com: 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, and thus can block it for any branch except one. But if you do this, I would suggest to explain this in the ticket so they won't accidentally remove the branch you do want. Adding the specific version can be useful to prevent someone from installing it over a koji- or local build of gnome-shell indeed. Regards, Patrick -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging software compatible with only one Fedora release
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. hal8...@hotmail.it wrote: OK, I've untagged the packages zukini, zukitwo and zukiwi from f18-updates-candidate and f19 through koji-untag-pkg -v --all f18-updates-candidate/19 zukini/zukitwo/zukiwi (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 published by the developers, will I be allowed to I ask rel-eng to un-block the package for the related branch? Thank you again. 2012/8/26 Patrick Uiterwijk puiterw...@gmail.com: 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, and thus can block it for any branch except one. But if you do this, I would suggest to explain this in the ticket so they won't accidentally remove the branch you do want. Adding the specific version can be useful to prevent someone from installing it over a koji- or local build of gnome-shell indeed. Regards, Patrick -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging software compatible with only one Fedora release
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 puiterw...@gmail.com: 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. hal8...@hotmail.it wrote: OK, I've untagged the packages zukini, zukitwo and zukiwi from f18-updates-candidate and f19 through koji-untag-pkg -v --all f18-updates-candidate/19 zukini/zukitwo/zukiwi (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 published by the developers, will I be allowed to I ask rel-eng to un-block the package for the related branch? Thank you again. 2012/8/26 Patrick Uiterwijk puiterw...@gmail.com: 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, and thus can block it for any branch except one. But if you do this, I would suggest to explain this in the ticket so they won't accidentally remove the branch you do want. Adding the specific version can be useful to prevent someone from installing it over a koji- or local build of gnome-shell indeed. Regards, Patrick -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Packaging software compatible with only one Fedora release
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/listinfo/devel
Packaging software compatible with only one Fedora release
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 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? Thanks in advance for your help. Regards, M.M. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
