Re: dnf history - change in how rpmdb checksum is computed

On 07/18/2018 09:24 AM, Daniel Mach wrote: > Hi everyone, > The DNF team is currently reviewing DNF compatibility with YUM 3 and we'd > like to get feedback on this one: > https://bugzilla.redhat.com/show_bug.cgi?id=1120253 > > rpmdb checksum is a checksum of all installed RPMs > It has no

Re: [atomic-devel] Starting a Container SIG

On 07/25/2018 01:09 PM, Clement Verna wrote: > > Please Reply if you're interested with helping out making the > Container story great in Fedora. If there is a good response, I will > create a Container SIG wiki page, and I guess we can ask for > container-devel mailing list for SIG

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

On 06/29/2018 08:42 AM, Stephen Gallagher wrote: > > > On Fri, Jun 29, 2018 at 8:32 AM Daniel Walsh > wrote: > > Users of OpenSHift Origin require CRI-O 1.10 right now.  But Kubernetes > users want to try out the latest packages for kubernetes 1.11 which >

make yum repo when we build things in koji

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I often build an rpm in koji to make sure it builds but in order to consume that rpm using our tools most of the time it needs to be in a yum repo somewhere. I could create a repo locally and serve it locally or even push it to somehwere to

Re: make yum repo when we build things in koji

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/19/2018 10:39 PM, Reindl Harald wrote: > > > [harry@srv-rhsoft:~]$ cat /etc/yum.repos.d/koji.repo > [koji] > name=Koji Repo > baseurl=https://koji.fedoraproject.org/repos/f$releasever-build/latest/$basearch/ > enabled=0 >

Re: Unannounced soname bump (Rawhide): qpdf (libqpdf.so.18 -> libqpdf.so.21)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/28/2018 01:38 PM, Daniel P. Berrangé wrote: > On Wed, Feb 28, 2018 at 01:12:03PM -0500, Matthew Miller wrote: >> On Wed, Feb 28, 2018 at 05:57:53PM +, Daniel P. Berrangé wrote: >>> mistake that caused files to go missing, and was never

Atomic Working Group VFAD 03/09

Hi everyone, This is a reminder that tomorrow we have a VFAD (Virtual Fedora Activity Day) for everyone who  can and wants to join in on the discussions:  https://pagure.io/atomic-wg/issue/429 -- Location: https://bluejeans.com/dmabe -- Topics: [upstream technology] * rpm-ostree

Re: Fedora Rawhide-20180308.n.2 compose check report

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 03/09/2018 09:33 PM, Dusty Mabe wrote: > > I honestly think we should > > - #1 - make Cloud an empty variant (It's useless, and we build repos for no > reason) > - #2 - Cloud base images get built from Everythin

Re: Fedora Rawhide-20180308.n.2 compose check report

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 03/08/2018 11:18 PM, Adam Williamson wrote: > On Thu, 2018-03-08 at 22:25 -0500, Dusty Mabe wrote: >> >> On 03/08/2018 08:17 PM, Fedora compose checker wrote: >>> Missing expected images: >>> >>> Ato

Re: Fedora Rawhide-20180308.n.2 compose check report

On 03/09/2018 09:49 PM, Adam Williamson wrote: > On Fri, 2018-03-09 at 21:42 -0500, Dusty Mabe wrote: >> >> On 03/09/2018 09:33 PM, Dusty Mabe wrote: >>> >> >> >>> I honestly think we should >>> >>> - #1 - make Cloud an emp

Re: Fedora Rawhide-20180308.n.2 compose check report

On 03/08/2018 08:17 PM, Fedora compose checker wrote: > Missing expected images: > > Atomichost qcow2 x86_64 > Atomichost raw-xz x86_64 This is kind of interesting.. I see these images in the compose:

Re: Fedora-Atomic 27-20180407.0 compose check report

On 04/07/2018 03:54 AM, Fedora compose checker wrote: > No missing expected images. > > Passed openQA tests: 2/2 (x86_64) > Can we get these emails to go to ato...@lists.fedoraproject.org? Dusty ___ devel mailing list --

Re: Fedora Atomic Host Two Week Release Announcement: 27.122

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/19/2018 05:55 PM, nore...@fedoraproject.org wrote: > > A new Fedora Atomic Host update is available via an OSTree update: > > Version: 27.122 > Commit(x86_64): > 931ebb3941fc49af706ac5a90ad3b5a493be4ae35e85721dabbfd966b1ecbf99 >

Re: runroot changing during the course of a rawhide pungi run

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/26/2018 07:51 PM, Kevin Fenzi wrote: > On 02/22/2018 07:34 PM, Dusty Mabe wrote: >> >> If I understand correctly there was a new lorax build [1] that completed >> at 01:11 UTC (02/23) that then made it into the

Re: Fedora Atomic Host Two Week Release Announcement: 27.93

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/27/2018 10:47 AM, nore...@fedoraproject.org wrote: > > A new Fedora Atomic Host update is available via an OSTree update: > > Version: 27.93 > Commit(x86_64): > da0bd968610aa1e29c5bb37065649407fbbfffa53e63831afdadbd34a3b05327 >

march VFAD for the atomic working group

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 https://pagure.io/atomic-wg/issue/429 In the Atomic working group in Fedora we have occasionally used virtual Fedora Activity Days (VFADs) to get the community together to discuss in a high bandwidth setting (video conference) some techical issues

Re: Frequently broken Rawhide/Branched composes

On 03/01/2018 11:52 AM, Kevin Kofler wrote: > Vít Ondruch wrote: >> Speaking of that, it seems that the Rawhide compose failed yesterday due >> to some KDE/QT soname bump: > [actually a typo in a Requires, as was already pointed out] >> >>

Re: Fedora 28 Atoimic Host RC 1.1 available for testing

On 04/25/2018 04:58 PM, Colin Walters wrote: > > > On Wed, Apr 25, 2018, at 4:35 PM, Dusty Mabe wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> The Atomic Host compose based on RC 1.1 is available for testing now. >>

Fedora 28 Atoimic Host RC 1.1 available for testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The Atomic Host compose based on RC 1.1 is available for testing now. The toplevel directory is: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-20180425.0 The cloud images are under the compose/AtomicHost/$arch/images/

Re: [atomic-devel] Fedora 28 Atoimic Host RC 1.1 available for testing

On 04/26/2018 08:54 AM, Sinny Kumari wrote: > > > On Thu, Apr 26, 2018 at 2:05 AM, Dusty Mabe <du...@dustymabe.com > <mailto:du...@dustymabe.com>> wrote: > > The Atomic Host compose based on RC 1.1 is available for testing now. > >

resume= kernel cmdline arg by default on servers

For BZ1206936 [1] we started adding resume= kernel command line by default [2] in fedora installs. This is causing issues for ostree based systems, which I haven't fully investigated yet, but figured I would ask the question: Is resume=/path/to/swap something we really want on server installs

Re: resume= kernel cmdline arg by default on servers

On 10/18/2018 07:58 AM, Stephen Gallagher wrote: > On Wed, Oct 17, 2018 at 11:27 PM Dusty Mabe wrote: >> >> >> For BZ1206936 [1] we started adding resume= kernel command line by >> default [2] in fedora installs. This is causing issues for ostree >> bas

Re: Fedora 29 Final Go/No-Go meeting

On 10/12/2018 10:08 PM, Trever L. Adams wrote: > On 10/12/18 9:27 AM, Ben Cotton wrote: >> Dear all, >> >> The Go/No-Go meeting for the Fedora 29 Final release will be held on >> Thursday, 2018-10-18 at 17:00 UTC in #fedora-meeting-1. For more >> information, see:

Re: Bodhi update pushes are now automated

On 11/7/18 1:35 PM, Michael Cronenworth wrote: > On 11/7/18 10:44 AM, Mohan Boddu wrote: >> For a long time now updates are pushed manually everyday. It was troublesome >> and >> someone has to own it for a week and look after it. >> >> Now, the pushes are automated and are pushed everyday at

where to put udev rules for to support cloud providers

context: https://github.com/coreos/fedora-coreos-tracker/issues/104 There are some udev rules that support various hardware on different cloud providers that we'd like to provide as part of Fedora CoreOS so it can operate on those platforms as expected. In the past these udev rules could be

Re: Self Introduction - Robert Fairley

On 1/17/19 12:31 PM, Robert Fairley wrote: > Hi all, > > I'm an intern at Red Hat in Toronto, Canada. I'm working on Fedora CoreOS, > and helping bring aspects of Container Linux to Fedora. I'll be maintaining a > package upstream, console-login-helper-messages. I also help out with >

Re: Atomic 29: ostree upgrade failed because of libdnf

On 12/5/18 5:14 AM, arnaud gaboury wrote: > > > On Tue, Dec 4, 2018 at 6:57 PM Dusty Mabe <mailto:du...@dustymabe.com>> wrote: > > > > On 12/4/18 11:40 AM, Dusty Mabe wrote: > > > > > I will look at the configs and see if I c

Re: Atomic 29: ostree upgrade failed because of libdnf

On 12/4/18 11:40 AM, Dusty Mabe wrote: > > I will look at the configs and see if I can figure out where things are going > wrong. > I think this a a regression is some of the new yaml parsing in pungi. I opened a bug to see https://pagure.io/pungi/issue/1092 The updates-

Re: Atomic 29: ostree upgrade failed because of libdnf

On 12/4/18 5:11 AM, arnaud gaboury wrote: > - > $ cat /etc/os-release > NAME=Fedora > VERSION="29.20181129.0 (Workstation Edition)" > ID=fedora > VERSION_ID=29 > PLATFORM_ID="platform:f29" > PRETTY_NAME="Fedora 29.20181129.0 (Workstation Edition)" >

Re: Any plans to support .heic files in Fedora?

On 12/3/18 6:53 PM, Leigh Scott wrote: >> On 11/30/18 5:20 AM, Leigh Scott wrote: >> >> Thanks Leigh. I see those have already made progress in code review. +1000 >> >> Is there a definitive reason why those are necessary to go in RPM fusion? >> Was >> Tom Hughes right? >> >> Dusty > > This

Re: Any plans to support .heic files in Fedora?

On 11/30/18 5:20 AM, Leigh Scott wrote: > Reviewers welcome. > > https://bugzilla.rpmfusion.org/show_bug.cgi?id=5089 > https://bugzilla.rpmfusion.org/show_bug.cgi?id=5090 Thanks Leigh. I see those have already made progress in code review. +1000 Is there a definitive reason why those are

Re: Atomic 29: ostree upgrade failed because of libdnf

On 12/6/18 6:20 AM, arnaud gaboury wrote: > > > On Wed, Dec 5, 2018 at 4:13 PM Dusty Mabe <mailto:du...@dustymabe.com>> wrote: > > > > On 12/5/18 5:14 AM, arnaud gaboury wrote: > > > > > > On Tue, Dec 4, 2018 at 6:57 PM Dus

prevent accidentally creating branches in dist-git

I've certainly made the mistake of accidentally creating branches in dist-git and now being stuck with them because we can't delete them. Now that src.fedoraproject.org (dist-git) is backed by a newer version of pagure you can prevent creating new branches by `git push`. For your project in the

Any plans to support .heic files in Fedora?

Seems like Apple converted their phones over to using a new file format to store pictures. I was copying some pictures from a phone and noticed my linux box couldn't read them and they had an interesting extension .heic. Looks like there is a new image format in town and we need the libheif and

Re: Fedora Atomic Host Two Week Release Announcement: 28.20180917.0

On 09/17/2018 03:19 PM, nore...@fedoraproject.org wrote: > > A new Fedora Atomic Host update is available via an OSTree update: > > Version: 28.20180917.0 > Commit(x86_64): > 17b11d74047ded1264a57555a64ae6fc5d02a332c556679bfcf32864fc91f11e > Commit(aarch64): >

Re: Packit is released: Packaging as a Service

On 3/21/19 9:40 AM, Tomas Tomecek wrote: > We are pleased to announce the initial version of Packit. > > Packit makes it easy to bring and integrate your upstream projects > into Fedora, right now we are focused to bring upstream > releases into Fedora rawhide. You can use packit now as a

Removing Atomic Host from Fedora Rawhide

Hello Fedora Atomic Host users, With the switched focus to Fedora CoreOS for the future of our immmutable, container oriented operating systems the last major release of Fedora Atomic Host was Fedora 29. Considering this we are removing the builds for Fedora Atomic Host from rawhide and will

Re: Fedora Atomic Host Two Week Release Announcement: 29.20190513.0

On 5/15/19 8:25 AM, Sven Kieske wrote: > Hi, > > is there a reason why _all_ links below: > > https://getfedora.org/en/atomic/* > > are dead? > > I always get, e.g.: > > Not Found > > The requested URL /en/atomic/download/ was not found on this server. > Apache Server at getfedora.org Port

Re: Fedora Atomic Host Two Week Release Announcement: 29.20190516.0

On 5/16/19 6:27 PM, nore...@fedoraproject.org wrote: > > A new Fedora Atomic Host update is available via an OSTree update: > > Version: 29.20190516.0 > Commit(x86_64): > 7f719bf60b865ca96aacd0e8ae3e6074c7eb5783d8ceb9003dbba5dfd5a29ba3 > Commit(aarch64): >

Re: How to consume fedora-messaging?

On 6/10/19 12:06 PM, Adam Williamson wrote: > On Mon, 2019-06-10 at 09:24 +0900, Tristan Cacqueray wrote: >> On Mon, Jun 10, 2019 at 01:24 Igor Gnatenko wrote: >>> Hello, >>> >>> I have been trying to write some script which would listen on >>> generation of new repository / successful build is

Re: Fedora Atomic Host Two Week Release Announcement: 29.20190625.0

On 6/25/19 1:38 PM, nore...@fedoraproject.org wrote: > > A new Fedora Atomic Host update is available via an OSTree update: > > Version: 29.20190625.0 > Commit(x86_64): > c50cc86ad7972f85853f1deafda3899eb86a0e5220c613744eed64320298716e > Commit(aarch64): >

Re: Fedora Rawhide-20190625.n.0 compose check report

On 6/25/19 6:32 PM, Adam Williamson wrote: > On Tue, 2019-06-25 at 17:45 +, Fedora compose checker wrote: >> Missing expected images: >> >> Atomichost raw-xz x86_64 >> Atomichost qcow2 x86_64 >> >> Compose FAILS proposed Rawhide gating check! >> 3 of 47 required tests failed, 4 results

Re: Orphaning cloud-init, python-boto

On 8/10/19 9:06 PM, Garrett Holmstrom wrote: > Hi, > > My time to work on Fedora cloud-related things has diminished in > recent months, so I have not been able to give the cloud-init and > python-boto packages the care they deserve. They are free to a good > home. > Maybe larks (cc) would

Re: Xen / EC2 release criteria proposal

On 8/9/19 8:56 PM, Adam Williamson wrote: > Hey folks! I'm starting a new thread for this to trim the recipient > list a bit and include devel@ and coreos@. Hey Adam! > > The Story So Far: there is a Fedora release criterion which requires > Fedora to boot on Xen: > > "The release must boot

Re: Orphaning cloud-init, python-boto

On 8/10/19 9:06 PM, Garrett Holmstrom wrote: > Hi, > > My time to work on Fedora cloud-related things has diminished in > recent months, so I have not been able to give the cloud-init and > python-boto packages the care they deserve. They are free to a good > home. > Can you give cloud-init

Re: Fedora-29-updates-testing-20190819.0 compose check report

On 8/19/19 1:18 AM, Sinny Kumari wrote: > From the build logs [1] [2] , it looks like disk got full which could be > builder specific. We can dig in more if it happens again. > > [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=37134473 > [2] >

Re: Fedora Atomic Host Two Week Release Announcement: 29.20190820.0

On 8/21/19 5:46 AM, Normand wrote: > > > On 8/20/19 7:56 PM, nore...@fedoraproject.org wrote: >> We are releasing images from multiple architectures but please note >> that x86_64 architecture is the only one that undergoes automated >> testing at this time. > > Is there wiki pages that

Re: fedora-gpg-keys not updated yet again

On 8/23/19 12:21 PM, Kevin Fenzi wrote: > On 8/23/19 4:12 AM, Dusty Mabe wrote: >> >> >> On 8/22/19 12:58 PM, Kevin Fenzi wrote: >>> On 8/21/19 9:27 AM, Dusty Mabe wrote: >>>> >>>> >>>> On 8/19/19 6:59 AM, Pavel Raiskup

Re: [atomic-announce] Fedora Atomic 29 EOL date?

On 8/24/19 6:27 AM, Feilong Wang wrote: > Hi team, > Hi Feilong! I'm adding in Spyros who has worked with us in the past on Atomic Host and Magnum. > Could you please help me understand when will be the EOL date for Fedora > Atomic 29? I understand generally it takes 13 months. But given

Re: fedora-gpg-keys not updated yet again

On 8/19/19 6:59 AM, Pavel Raiskup wrote: > On Monday, August 19, 2019 10:50:52 AM CEST Zbigniew Jędrzejewski-Szmek wrote: >> Can we *please* send out the FN+1 and FN+2 keys a month before branching, >> to *all* releases of Fedora, so we can avoid this pointless scramble? > > What about to have

Re: fedora-gpg-keys not updated yet again

On 8/22/19 12:58 PM, Kevin Fenzi wrote: > On 8/21/19 9:27 AM, Dusty Mabe wrote: >> >> >> On 8/19/19 6:59 AM, Pavel Raiskup wrote: >>> On Monday, August 19, 2019 10:50:52 AM CEST Zbigniew Jędrzejewski-Szmek >>> wrote: >>>> Can we *please* send

Re: 'showme' RPM dependency visualizer (was: Minimization Objective report)

On 8/23/19 6:35 AM, Dominik 'Rathann' Mierzejewski wrote: > Hi, Adam. > > On Wednesday, 21 August 2019 at 15:41, Adam Samalik wrote: > [...] >> == Toolbox == >> >> The 'showme' tool [3] for visualising and inspecting RPM dependencies >> now supports weak dependencies and a package list output.

Re: Help update Hugo

On 8/22/19 12:46 AM, Robert-André Mauchin wrote: > Hello, > > Feel free to help review these packages needed to update Hugo: > Thanks for the effort here Robert-André. I might be able to help with a few of these since I use Hugo. Will let you know next week. Dusty

Re: [atomic-announce] Fedora Atomic 29 EOL date?

On 9/10/19 10:18 PM, Feilong Wang wrote: > Hi Dusty, > > Now Spyros and I are trying to ask for support in Ignition for multi part > MIME, see https://github.com/coreos/ignition/issues/849 It would be nice if > we can get your review and support. Thanks. Any chance you could drop by

Re: CPE Team Weekly Update

On 9/27/19 9:18 AM, Aoife Moloney wrote: > Hi everyone, > > > I’d like to introduce myself first, my name is Aoife Moloney and I recently > started with the Community Platform Engineering (CPE) team. My role within > this team is going to be a hybrid role of a Product Owner / Project

Re: Fedora Atomic Host Two Week Release Announcement: 29.20191001.0

On 10/2/19 5:25 PM, nore...@fedoraproject.org wrote: > > A new Fedora Atomic Host update is available via an OSTree update: > > Version: 29.20191001.0 > Commit(x86_64): > 15b8a10f8b587c2a037a592806dc04e9cdf6ab1c73c6e49fdaacab1b1174b9ab > Commit(aarch64): >

Fedora Atomic Host Nearing End Of Life

This content also exists at: https://www.projectatomic.io/blog/2019/11/fedora-atomic-host-nearing-eol/ Last year we [introduced the plans for Fedora CoreOS] [1] including that Fedora CoreOS would be the successor to Fedora Atomic Host and Container Linux (from CoreOS Inc.). As part of that

Re: Fedora Atomic Host Nearing End Of Life

On 11/25/19 11:41 AM, Normand wrote: > > > On 11/21/19 11:33 PM, Dusty Mabe wrote: >> This content also exists at: >> https://www.projectatomic.io/blog/2019/11/fedora-atomic-host-nearing-eol/ >> >> Last year we [introduced the plans for Fedora CoreOS] [1] incl

new maintainer for tmuxinator

It was orphaned recently. Anybody care to pick it up? :) https://src.fedoraproject.org/rpms/tmuxinator Dusty ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of

Re: What to do with simple-koji-ci?

On 2/7/20 9:30 AM, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > I while back I wrote a small service named simple-koji-ci, which reacts to > every pull-request opened on dist-git and fires a (scratch) build of the > package > with the proposed changes merged, and report the outcome

Re: Vague proposal: ship prebuilt initramfs images

On 1/20/20 7:57 PM, Matthew Garrett wrote: > > I've been thinking about ways to solve this for a while, and I'm coming > to the conclusion that the best plan is probably to just ship pre-built > initramfs images. I can think of three main reasons to want to use > system-specific images:

co-maintainer wanted for fuse-sshfs in EPEL8

The current maintainer of fuse-sshfs is looking for a co-maintainer for it in epel8. It's currently not in EPEL 8 so if you go from RHEL or CentOS 7->8 you'll lose it. I have users of vagrant-sshfs who would like to have it there. https://bugzilla.redhat.com/show_bug.cgi?id=1758884#c4 Anybody

Re: co-maintainer wanted for fuse-sshfs in EPEL8

-maintainer we'll then need to add a epel8 branch and build against it. Thanks so much! Dusty On 3/8/20 12:33 PM, Vascom wrote: > You can add me as comaintainer. > FAS name: vascom > > вс, 8 мар. 2020 г., 19:32 Dusty Mabe <mailto:du...@dustymabe.com>>: > > The curre

Re: Should logrotate timer be enabled by default on all installations?

On 3/18/20 8:04 AM, Kamil Dudka wrote: > logrotate is a utility designed to simplify the administration of log files > on > a system which generates a lot of log files. It used to be triggered by > cron. > The cron hook was unconditionally installed with logrotate but it took effect >

Re: Emerging editions, Fedora 32 Beta, and bureaucracy

On 3/17/20 2:01 PM, Adam Williamson wrote: Hey Adam, > > 3) CoreOS - CoreOS is just a *whole* other thing. It is not built like > the rest of Fedora at all. It's not built as Pungi composes, whatever > compose process it does have doesn't run alongside our other compose > processes or

September Fedora CoreOS update for the Fedora Council

The Fedora CoreOS working group periodically gives status updates to the Fedora Council. Since we compiled this list I figured it would be nice to share more widely: - Rebased the `next` stream to Fedora 33 - https://github.com/coreos/fedora-coreos-tracker/issues/611 - Added better afterburn

Re: F33 beta: where are my Rust packages?

On 10/12/20 9:24 AM, Fabio Valentini wrote: > On Mon, Oct 12, 2020 at 9:15 AM Artur Frenszek-Iwicki > wrote: >> >> I wrote to Igor a week ago, but it seems he's away currently, as I didn't >> get an answer yet. >> >> Do you know of some document that describes how to "go through Igor's whole

Re: splitting out systemd-networkd, systemd-standalone-{sysusers,tmpfiles} subpackages in F33+

On 10/1/20 8:20 AM, Peter Robinson wrote: >> Moreover, *all* Fedora variants use NetworkManager. *ALL* OSTree > (rpm)ostree variants are Fedora variants - please don't using phrasing > implying otherwise. > IOW you just say: *all* Fedora variants use NetworkManager. They

Re: splitting out systemd-networkd, systemd-standalone-{sysusers,tmpfiles} subpackages in F33+

On 10/1/20 12:00 AM, Joe Doss wrote: > On 9/30/20 7:14 PM, Colin Walters wrote: >> That's not true, you can `rpm-ostree override remove`. It'd still be >> there in the ostree repository on disk, but you don't see it in the >> "deployment" (what you actually boot into). Few people care about >>

Testing out container runtimes in F33

If you're already on Fedora 33 would you please help us test out the pending updates to our container runtimes and give a +1 or -1 in the bodhi update? podman and friends: - https://bodhi.fedoraproject.org/updates/FEDORA-2020-7b6058fec9 - sudo dnf upgrade --advisory

New CoreOS Assembler release v0.8.1

nt RHCOS LUKS rootfs Dusty Mabe (20): 6df34a21 mantle: bump google.golang.org/api library to latest a11197f2 mantle/ore: glcoud: add --create-image option to upload.go 02653cad cosalib/gcp: remove unused argument 91297ff2 mantle/ore: gcloud: fix error detection, add

Fedora CoreOS rebasing to Fedora 32: known issues; upcoming test day

test day. Join us in #fedora-coreos on Freenode to test Fedora CoreOS based on Fedora 32! For more information, see the mailing list post. Thanks for helping us make Fedora CoreOS awesome! Dusty Mabe, for the Fedora CoreOS team

rust-ipnetwork license change

The license for rust-ipnetwork changed to "MIT or Apache-2.0" upstream [1]. This is reflected in the PR to distgit [2] to update to the latest version. Dusty [1] https://github.com/achanda/ipnetwork/commit/fa128680b51fbcf9c37db99f011c91204c4a3b0d [2]

Re: Fedora 33 in GCP

On 11/19/20 11:10 PM, Matthew Miller wrote: > On Thu, Nov 19, 2020 at 07:41:02PM -0500, Dusty Mabe wrote: >> We have published an image into GCP for Fedora 33 (see [1]). >> The details are: >> image project: fedora-cloud >> image name:fedora-cloud-base-gcp-33

Re: Fedora 34 Change: Make Fedora CoreOS a Fedora Edition (System-Wide Change)

On 12/2/20 12:33 PM, Adam Williamson wrote: > > Note that if you go to getfedora.org and click on CoreOS *right now*, > it offers you a Fedora 32-based CoreOS. This is the kind of thing that > is kinda fine so long as it's an Emerging Edition. It would *not*, > IMHO, be fine for an Edition.

Re: Fedora 34 Change: Make Fedora CoreOS a Fedora Edition (System-Wide Change)

On 12/2/20 12:57 PM, Ben Cotton wrote: > On Wed, Dec 2, 2020 at 12:22 PM Adam Williamson > wrote: >> >> So to boil this down into a representative question: when we are doing >> the Fedora 34 Go/No-Go meeting in ~four months' time, how do we decide >> whether to release "Fedora CoreOS 34"? >> >

November Fedora CoreOS update for the Fedora Council

The Fedora CoreOS working group periodically gives status updates to the Fedora Council. Here's the update for this past month: * Enablement work on getting the new LUKS path used in OKD * Informational fedora messages are now sent by the FCOS pipeline for integration with other services

Fedora 33 in GCP

We have published an image into GCP for Fedora 33 (see [1]). The details are: image project: fedora-cloud image name:fedora-cloud-base-gcp-33-1-2-x86-64 We're hoping to get this information added to the website at some point. Dusty [1] https://pagure.io/cloud-sig/issue/318

October Fedora CoreOS update for the Fedora Council

The Fedora CoreOS working group periodically gives status updates to the Fedora Council. Since we compiled this list I figured it would be nice to share more widely: - Shipped Fedora CoreOS based on Fedora 33 in the `next` stream - [migrated existing systems to

Fedora CoreOS stable stream now rebased to Fedora 34

by default [5]. - DNF Count Me support for Fedora CoreOS [6]. Thanks to everyone who participated in the test day [7] and to everyone that run the `testing` and `next` streams to help us identify and fix issues before they get to `stable`. Dusty Mabe, for the Fedora CoreOS team [0] https

Fedora 34 GCP image

FYI - I published the Fedora 34 GCP image to the `fedora-cloud` project in GCP. See https://pagure.io/cloud-sig/issue/328 for more details. Currently you do have to provide cloud-init userdata to the instance (via the user-data key). This hopefully won't be the case once we include the newly

Re:  Advice on packaging azure-cli

On 5/25/21 8:29 AM, Major Hayden wrote: >  Hello there, > > I'm eager to package Azure's CLI tools for Fedora that would allow users > to manage their Microsoft Azure cloud infrastructure. This would help > with CI/CD, information security, monitoring, and of course, deployments. I don't

Re:  Advice on packaging azure-cli

On 5/25/21 9:01 AM, Miro Hrončok wrote: > On 25. 05. 21 14:29, Major Hayden wrote: > > The culprit of trying to maintain them in one component is that they are > released independently. Maintaining various subpackages with different > versions > and release cycles from the same spec file is

Re: Fedora CoreOS stable stream now rebased to Fedora 34

On 5/20/21 12:13 PM, Ron Olson wrote: > If I may, I think the issue is right there in the name: Fedora CoreOS. The > Fedora name brings some expectations and it seems CoreOS, by its nature, > can’t be at parity with the other Fedora flavors and that leads to confusion. > I can attest that I

Re: F35 Change: Make btrfs the default file system for Fedora Cloud (System-Wide Change proposal)

On 6/2/21 5:28 AM, Peter Boy wrote: > > > > very nicely put. According to Matthew and others cloud wg did virtually not > exist for more than a year, no meetings, silence on mailing list beyond > bi-weekly announcement of a „standing“ meeting nobody attended to, there was > discussion to

Re: Package downgrades from Fedora 33 -> Fedora 34 (including ostree + rpm-ostree)

On 4/6/21 10:58 AM, Fabio Valentini wrote: > On Tue, Apr 6, 2021 at 4:43 PM Colin Walters wrote: >> >> Hi, >> >> On Tue, Apr 6, 2021, at 6:42 AM, Fabio Valentini wrote: >>> Hi everybody, >>> >>> It's that time of the year again, and this time there's not that many >>> downgrades to complain

Thanks to everyone who participated in the FCOS 35 test day/week

day results page can be viewed at: https://testdays.fedoraproject.org/events/122 We do still have some platforms that weren't tested so feel free to execute those test cases! Dusty Mabe ___ devel mailing list -- devel@lists.fedoraproject.org

Fedora CoreOS next stream rebased to Fedora Linux 35

Hi all, Fedora Linux 35 Beta was released today [1]. Our Fedora CoreOS `next` stream has been migrated to Fedora Linux 35 content. Existing nodes on the `next` stream will update as normal over the following days. Please test it out and report any issues in our issue tracker [2]. Thank you to

Fedora CoreOS 64 bit ARM artifacts

Hi all, A few weeks ago we started shipping 64 bit ARM (aarch64) artifacts for our Fedora CoreOS streams. The download page [1] has been updated to show the new artifact downloads and you should be able to retrieve aarch64 information from all relevant stream and release metadata. Please report

Re: [CoreOS] Fedora CoreOS Community Video Meeting 2021-10-06

On 10/5/21 5:53 PM, Dusty Mabe wrote: > Hi All, > > Tomorrow we will be holding a video meeting for the Fedora CoreOS community. > > Harshal Patil will be joining us to give a brief overview of how Fedora > CoreOS is used > for the e2e node tests in upstream Kubernetes.

Re: Self Introduction: Saqib Ali

On 9/20/21 9:02 AM, Saqib Ali wrote: > Hey everyone, > > First post on this list :) I'm Saqib Ali and I'm a student at the University > of Toronto. I'm currently an intern at Red Hat on the CoreOS team. > I've been working with Fedora CoreOS and attended the last Flock to Fedora > (nice to

Fedora CoreOS Community Video Meeting 2021-10-06

Hi All, Tomorrow we will be holding a video meeting for the Fedora CoreOS community. Harshal Patil will be joining us to give a brief overview of how Fedora CoreOS is used for the e2e node tests in upstream Kubernetes. https://github.com/coreos/fedora-coreos-tracker/issues/984 We'll also be

Fedora CoreOS Meeting Minutes 2021-11-17

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2021-11-17/fedora_coreos_meeting.2021-11-17-16.31.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2021-11-17/fedora_coreos_meeting.2021-11-17-16.31.txt Log:

Fedora CoreOS streams rebasing to Fedora Linux 35

[11] - Support for a minimal ISO image [12] - Support for Nutanix [13] - Switching to iptables-nft by default [14] Thanks to everyone who participated in the test day [15] and to everyone that follows the `testing` and `next` streams to help us identify and fix issues before they get to `stable`. Dusty

Fedora CoreOS Meeting Minutes 2021-11-24

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2021-11-24/fedora_coreos_meeting.2021-11-24-16.28.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2021-11-24/fedora_coreos_meeting.2021-11-24-16.28.txt Log:

Re: Fedora CoreOS Community Video Meeting 2021-11-02

Correction in the subject: 2021-11-03 And in the Body: Time: 16:30 UTC (same as normal) on Wednesday November 3rd On 11/2/21 10:19 PM, Dusty Mabe wrote: > Hi All, > > Tomorrow we will be holding a video meeting for the Fedora CoreOS community. > > Colin Walters will be pres

Fedora CoreOS Community Video Meeting 2021-11-02

Hi All, Tomorrow we will be holding a video meeting for the Fedora CoreOS community. Colin Walters will be presenting on a new proposal for "CoreOS Layering". https://github.com/coreos/enhancements/pull/7 We'll also be discussing any meeting tickets and possibly revisit our list of high level

Fedora CoreOS Meeting Minutes 2021-10-27

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2021-10-27/fedora_coreos_meeting.2021-10-27-16.27.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2021-10-27/fedora_coreos_meeting.2021-10-27-16.27.txt Log:

Re: [CoreOS] Fedora CoreOS Community Video Meeting 2021-11-02

On 11/2/21 10:19 PM, Dusty Mabe wrote: > Hi All, > > Tomorrow we will be holding a video meeting for the Fedora CoreOS community. > > Colin Walters will be presenting on a new proposal for "CoreOS Layering". > https://github.com/coreos/enhancements/pull/7 >

Re: [CoreOS] Fedora CoreOS Community Video Meeting 2021-11-02

On 11/3/21 5:45 PM, Eduard Lucena wrote: > Would you like to have this meeting uploaded to Fedora Project's YouTube > channel? > > Not really sure on that one. Maybe grab me and we'll discuss it. Dusty ___ devel mailing list --

<    1   2   3   4   >