I've also hit a bug related to python3 probably:
https://bugzilla.redhat.com/show_bug.cgi?id=1267808
But even when I did a quick fix, there is a problem I got:
Status code: 404 for
https://copr.fedoraproject.org/api/coprs/sochotni/fedwatch/detail/fedora-...
I expect it is caused by the fact f23 buildroot doesn't exist in
sochotni/fedwatch. Funny thing is that it works when running
`dnf copr enable sochotni/fedwatch`
but the f23 repo doesn't exist, so installation of copr package doesn't
work (well, it works but the package is grabbed from fedora proper repo).
The bottom line is that either the plugin must be more fault tolerant
when a copr doesn't exist for specified chroot or playground
specification should be generated for every chroot separately.
Some other issues, not blockers though:
usability issues of dnf plugin for playground:
* `dnf playground <action> -h|--help` doesn't print any nice message
* dnf playground list
* dnf playground list-enabled
* bash completion doesn't work
Honza
On 10/01/2015 10:59 AM, Honza Horak wrote:
As promised, these are the meeting logs that are related to
Playground:
https://meetbot.fedoraproject.org/fedora-meeting-2/2015-03-12/env-and-sta...
https://meetbot.fedoraproject.org/fedora-meeting-2/2015-03-26/env-and-sta...
https://meetbot.fedoraproject.org/fedora-meeting-2/2015-04-23/env-and-sta...
https://meetbot.fedoraproject.org/fedora-meeting-2/2015-05-28/env-and-sta...
https://meetbot.fedoraproject.org/teams/env-and-stacks/env-and-stacks.201...
Some quick brainstorming about how the process could look like:
* submit a request (
https://fedorahosted.org/env-and-stacks/)
* somebody does checking (small review that focuses on license,
influencing the base system, general quality, but only license is really
a blocker; plus conflicts with base system -- yes, playground doesn't
allow to pick some of the coprs -- use `dnf copr enable` for enabling
some conflicting packages) --
https://meetbot.fedoraproject.org/fedora-meeting-2/2015-04-23/env-and-sta...
* after checking, something like bodhi karma happens -- either package
stays without enough votes some reasonable period or if E&S people
provide enough voting, the package is pushed into playground sooner
(something from the above was taken from the logs above with a little
own imagination; some workflow plus some nice diagram would be handy
about what is happening in playground and how it works with approving a
copr to be in playground after this is ready)
Honza