Dear all,
You are kindly invited to the meeting:
Docs Writing Hour on 2019-10-16 from 10:00:00 to 11:00:00 US/Eastern
The meeting will be about:
Join members of the docs team in #fedora-docs for writing time. This is a great time to focus on writing and talk about challenges and blockers related to producing content.
There is no formal schedule for this meeting. Attendees should show up and use this as a way to block writing time into their week.
Source: https://apps.fedoraproject.org/calendar/meeting/9360/
Dear all,
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 31
Final Release Readiness meeting. This meeting will be held on
Thursday, 2019-10-17 at 19:00 UTC.
We will meet to make sure we are coordinated and ready for the release
of Fedora 31 Final. Please note that this meeting will be held even if
the release is delayed at the Go/No-Go meeting on the same day two
hours earlier.
You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
For more information, see
https://fedoraproject.org/wiki/Release_Readiness_Meetings.
View the meeting on Fedocal:
https://apps.fedoraproject.org/calendar/Fedora%20release/2019/10/17/#m9630
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Dear all,
You are kindly invited to the meeting:
Docs Writing Hour on 2019-10-09 from 10:00:00 to 11:00:00 US/Eastern
The meeting will be about:
Join members of the docs team in #fedora-docs for writing time. This is a great time to focus on writing and talk about challenges and blockers related to producing content.
There is no formal schedule for this meeting. Attendees should show up and use this as a way to block writing time into their week.
Source: https://apps.fedoraproject.org/calendar/meeting/9360/
Hello,
I'm running into errors while running ./build.sh in the council-docs
repository for this PR:
https://pagure.io/Fedora-Council/council-docs/pull-request/63
Initially, I got:
> $ ./build.sh
>
> This build script is using Podman to run the build in an isolated environment.
>
> WARN[0000] Error initializing configured OCI runtime runc: no valid executable found for OCI runtime runc: invalid argument
> Error: could not get runtime: default OCI runtime "runc" not found: invalid argument
@hhlp pointed out that it's listed in F31 common bugs here:
https://fedoraproject.org/wiki/Common_F31_bugs#Podman_fails_to_run_containe…
The fix, unfortunately, doesn't seem to work fully:
> (ins)[asinha@ankur-pc fedora-council-docs(fedora-join=)]$ rm ~/.config/containers/libpod.conf -f
>
> (ins)[asinha@ankur-pc fedora-council-docs(fedora-join=)]$ ./build.sh
>
> This build script is using Podman to run the build in an isolated environment.
>
> 2019-09-25T10:28:24.000811303Z: cannot rm state directory '/run/user/1000/crun/42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195': Directory not empty
> ERRO[0002] Error removing container 42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195: error cleaning up container 42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195: error removing container 42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195 from runtime: `/usr/bin/crun delete --force 42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195` failed: exit status 1
> (ins)[asinha@ankur-pc fedora-council-docs(fedora-join=)]$
>
Would anyone have a workaround/fix please?
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London