Re: slowing down the development schedule for a release.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/21/2013 04:39 PM, Frantisek Kluknavsky wrote:
On 08/21/2013 04:16 PM, Ralf Corsepius wrote:
On 08/21/2013 04:01 PM, Frantisek Kluknavsky wrote:
On 08/21/2013 03:35 PM, Ralf Corsepius wrote:
there are no f20 mock configurations on released Fedora releases in
place

Is fedpkg mock-config problematic?
No. fedpkg mockbuild for f20 and mock -r fedora-20-XXX are the problem.


Ralf


Maybe I misunderstand the purpose of "fedpkg mock-config". I mean
workflow like:

1. fedpkg switch-branch f20
2. fedpkg mock-config > fedora-20-x86_64.cfg
3. (maybe edit fedora-20-x86_64.cfg ?)
4. sudo mv fedora-20-x86_64.cfg /etc/mock
5. fedpkg mockbuild

where steps 2-4 are needed only once after branching.
Ahh! I wasn't aware about this possibility.


Is fedpkg
mockbuild for f20 still problematic after that?
Slightly, because you'd have to install such a *.cfg globally, which then will conflict with mock, once it will be updated.

Ralf

--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux