Dear all,
You are kindly invited to the meeting:
ELN SIG on 2023-05-05 from 12:00:00 to 13:00:00 US/Eastern
At fedora-meeting(a)irc.libera.chat
The meeting will be about:
Source: https://calendar.fedoraproject.org//meeting/10449/
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2023-05-03/fedora_coreos…
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2023-05-03/fedora_coreos…
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2023-05-03/fedora_coreos…
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:30:23 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2023-05-03/fedora_coreos…
.
Meeting summary
---------------
* roll call (dustymabe, 16:30:29)
* Action items from last meeting (dustymabe, 16:35:01)
* status post went out:
https://lists.fedoraproject.org/archives/list/coreos-status@lists.fedorapro…
(dustymabe, 16:35:17)
* New Package Request: nmstate (dustymabe, 16:37:12)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1175
(dustymabe, 16:37:18)
* LINK:
https://github.com/coreos/fedora-coreos-docs/pull/531#issuecomment-15135417…
(dustymabe, 16:37:50)
* AGREED: we will document a single or a few examples with nmstate
(perhaps putting them on a secondary page and linking from the main
page) and leave keyfiles as the primary documented network
configuration for now. (dustymabe, 16:48:07)
* Ship moby-engine 23.0.x in Fedora CoreOS (dustymabe, 16:48:41)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1476
(dustymabe, 16:48:46)
* AGREED: once this makes it into bodhi stable we will add it to our
`next` stream for at least a month to gather feedback before
promoting it. (dustymabe, 16:59:30)
* Regular updates for the UEFI revoked signatures database (dbx)
(dustymabe, 17:01:39)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1478
(dustymabe, 17:01:42)
* ACTION: dustymabe to invite grub and kernel folks to discuss this
topic further (dustymabe, 17:05:10)
* GCP: add aarch64 image (dustymabe, 17:10:42)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1377
(dustymabe, 17:10:48)
* AGREED: we will leave the existing image families in place (for
x86_64) and create new `-arm64` image families for the aarch64
images. (dustymabe, 17:17:50)
* open floor (dustymabe, 17:18:40)
* The Fedora 38 rebase is landing in stable over the next few days!
(dustymabe, 17:20:02)
* thanks to the work by gursewak we should have kubevirt images (and
docs) in the next round of FCOS releases (dustymabe, 17:22:37)
Meeting ended at 17:26:10 UTC.
Action Items
------------
* dustymabe to invite grub and kernel folks to discuss this topic
further
Action Items, by person
-----------------------
* dustymabe
* dustymabe to invite grub and kernel folks to discuss this topic
further
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dustymabe (112)
* bgilbert (36)
* zodbot (22)
* jlebon (20)
* apiaseck[m] (9)
* pjones (9)
* fifofonix (6)
* mnguyen (5)
* ravanelli (3)
* walters (2)
* gursewak (1)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
Greetings everyone.
Fedora Release engineering was made aware recently that some real builds
seemed to have been done from commits not in any branch in the main
repository for the package. All cases we are currently aware of were
maintainers mistakenly building from a forked repo with a valid pull
request.
On investigation, this was found to be due to some changes in how koji
does the buildSRPMFromSCM task and us being unaware of the implications
of that change.
In short, when a pull request is created, pagure keeps track of those
commits in refs/pulls. Previously koji did a 'git reset' to the exact
commit, which would only work for commits on a branch. The new method
with 'git fetch' will follow refs and find the pull request commit.
Upstream koji developers have created a plugin for us to check policy
after the checkout and require official builds to be from a commit that
is in a branch. This plugin has been deployed and is active.
Sorry for any confusion this issue may have caused.
kevin
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr…
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
We're trying to rebuild the Fedora 38 ghc packages on riscv64, and
some fail with:
$ ./Setup build -j4
Preprocessing library for pandoc-types-1.22.2.1..
Building library for pandoc-types-1.22.2.1..
ghc-9.2.6: setNumCapabilities: not supported on this platform
[3 of 7] Compiling Text.Pandoc.Definition
<no location info>: error:
ghc-9.2.6: Couldn't find a target code interpreter. Try with -fexternal-interpreter
It comes from here:
https://ghc.gitlab.haskell.org/ghc/doc/libraries/ghc-9.7/src/GHC.Driver.Env…
I haven't the first clue what "target code interpreter" or "external
interpreter" is referring to here. Isn't Haskell compiled to native
code?
Do we know what could cause this and how to correct it?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
Following is the list of topics that will be discussed in the
FESCo meeting Tuesday at 17:00UTC in #fedora-meeting on
irc.libera.chat.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2023-05-02 17:00 UTC'
Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda
= Discussed and Voted in the Ticket =
N/A
= Followups =
N/A
= New business =
#2983 Create an email list policy
https://pagure.io/fesco/issue/2982
#2984 Change: Remove webkit2gtk-4.0 API Version
https://pagure.io/fesco/issue/2984
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda
If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
👋
--
Major Hayden