On Wed, Apr 5, 2017, at 11:28 AM, Kamil Dudka wrote:
> Anyway, do not overestimate the power of HTTP/2. It will not transparently
> bring you better transfers for free. You can speak HTTP/2 even while using
> the curl tool but it is mainly useful for testing. If you want to take the
> advantage
> Our first attempt to make sudo pip safe on Fedora [0] was
This seems to be using "Fedora" to mean a *host* system, and
I'd agree there. I'll note as an aside that the other host system
management tool we use in Fedora is rpm-ostree, part of
Atomic Host: https://github.com/projectatomic/rpm-os
On Wed, May 24, 2017, at 11:22 AM, Jan Pokorný wrote:
> Nope, the point is that nothing has changed in the codebase or, for
> that matter, tags. It must have been GitHub that changed how its
> equivalent of "git archive" behaves.
Yep, that's happened in the past, obviously just happened again,
On Tue, Jun 13, 2017, at 10:43 AM, Matthew Miller wrote:
> I know we're already at new-deliverable explosion, but this seems like
> a place where it'd be nice to have Rawhide and Bikeshed (or whatever we
> want to call "tested and believed-to-be basically functional Rawhide").
> That doesn't see
On Thu, Jul 6, 2017, at 09:15 PM, Matthew Miller wrote:
> Hopefully, by the time we are at F28, Modularity will provide a way for
> us to offer faster streams for people who want them -- but let's also
> focus on stable releases.
But with Modularity, how much does it even make sense to talk abou
On Tue, Jul 11, 2017, at 03:49 PM, Jean-Baptiste Holcroft wrote:
> Le 11/07/2017 à 19:30, Colin Walters a écrit :
> > specific ones. And we get into a lot of interesting questions around
> > the intersection
> > of the languages and Workstation, depending on what gets inst
On Wed, Jul 12, 2017, at 07:53 AM, Kevin Kofler wrote:
>
> When I see the plans that are floated around, the other stuff might also end
> up being containerized in a similar way, just using other technologies
> (e.g., Docker).
There are definitely apps today that are designed to run in standal
Hi,
On Fri, Jul 14, 2017, at 05:52 PM, Andrew Lutomirski wrote:
> I don't see the problem. The runtime could be all of /use and the app
> could be a symlink living in /app that points at /usr. The latter
> could be created on the fly in a tmpfs.
You're right; however, there are two other aspec
On Tue, Jul 18, 2017, at 02:58 PM, Chris Murphy wrote:
> > But if I've understood correctly, any changes to the base will be discarded
> > when you update the base image. right?
No; `rpm-ostree install` is persistent, and so are other changes like
`rpm-ostree initramfs --enable` and so is the rec
On Mon, 2013-11-04 at 14:48 +, Richard Hughes wrote:
> I like what ChromeOS
> does where it has a rescue-ish partition, to do the upgrade, but
> without something like btrfs that can switch roots on a running
> filesystem that's basically impossible on Linux.
This is precisely what https://wik
On Tue, 2013-11-05 at 13:23 -0800, Adam Williamson wrote:
> If
> distros move away from the gospel of centralized distribution
Some people working on technologies in this area may have that as a
goal, but I think it's absolutely crucial to continue to support the
"package" model of application d
On Tue, 2013-12-17 at 23:24 +0100, Miloslav Trmač wrote:
> b) Which WG will take on the task of solving this? We shouldn't end
> up with everybody agreeing that this needs to be solved, but no PRD
> proposing to solve this. Is it the Base WG or the Env and Stacks WG?
> Or is it up to Server and
Hi Andrew,
On Tue, 2013-12-17 at 15:05 -0800, Andrew Lutomirski wrote:
> There will be a similar problem in the docker images, unless you're
> suggesting that everyone use Ubuntu-in-docker-on-Fedora/RHEL.
True, but it becomes the responsibility of the container creator, not
"Fedora".
Anyways, I
On Tue, 2013-12-17 at 15:27 -0800, Andrew Lutomirski wrote:
> there are
> lots of libraries where, for example, .so.6 would be a perfectly fine
> replacement for .so.7, but the system doesn't know that.
I think the authors of these libraries screwed up. Namely, libudev and
libffi were both mista
On Thu, 2013-12-12 at 18:50 +0100, Phil Knirsch wrote:
> Hi everyone.
>
> During last weeks Base WG discussion about package set and self hosting
> of Base we came to a point where especially the self hosting of Base
> would currently look absurd as we'd require more than 2000 components to
> d
Hi,
On Fri, 2013-12-20 at 16:28 -0600, Jon wrote:
> To reduce size, complexity, save time.
That's quite vague.
> What do you mean by "*enforcing*", or how would you imagine that happening?
My original email contained a total of 3 sentences, and you didn't reply
to the second sentence, which an
On Mon, 2014-01-13 at 08:39 -0500, Matthew Miller wrote:
> On Sun, Jan 12, 2014 at 04:39:12PM -0800, Adam Williamson wrote:
> > You're preaching to the choir. But if in practice people really don't
> > deploy things via the distribution packages, it doesn't matter how
> > awesomely secure the distr
On Tue, 2014-01-14 at 11:00 +0100, Nicolas Mailhot wrote:
> So instead of the perenial "let's drop rpm and use upstream incomplete
> systems"
You might note I didn't say that.
> I'd like to see the people working in those language communities
> work at adding the missing bits to those upstream
Hello devel@,
I'm excited to announce the first public release (v2014.3) of the
fedostree/rpm-ostree project.
The web page is here:
http://rpm-ostree.cloud.fedoraproject.org/#/
rpm-ostree is a quite new, raw, and also quite unofficial project (the instance
above is in the Fedora private scratch
Hi Dennis,
On Tue, 2014-01-21 at 07:40 +0100, Dennis Jacobfeuerborn wrote:
> Interesting. I've downloaded the VM Image and tried to understand the
> setup.
Some bits are documented here
https://people.gnome.org/~walters/ostree/doc/layout.html
> Apparently there exist sort of two root trees /
On Fri, 2014-01-24 at 00:55 +0100, Kevin Kofler wrote:
> Last time an issue like that happened (the D-Bus regression that broke
> updates),
That was my fault. Something which left an impact on me, you can be
sure. Like SELinux, DBus impacts everything nearly everything in early
userspace.
In
On Fri, 2014-01-24 at 00:12 +0100, Lars Seipel wrote:
> On Thu, Jan 23, 2014 at 05:07:16PM -0500, Josh Boyer wrote:
> > Also possibly correct. However, that doesn't preclude the repos as we
> > know them today from still existing, with still the same quality.
>
> Server, desktop or embedded board
On Fri, 2014-01-24 at 18:52 +0100, drago01 wrote:
> From the website:
>
> "Although yum is installed, it will operate in read-only mode. Do not
> attempt to use it at the moment. See "
>
> Seems like the part talking about it is somehow missing i.e see what? ;)
I updated the text a bit on http:/
On Sat, 2014-01-25 at 10:37 -0800, Josh Stone wrote:
> Ok, sure, you can mount -o nosuid,noexec,nodev ... but this isn't the
> default for btrfs subvolume paths AFAIK. It needs to be a conscious
> decision in whatever snapshot design we choose.
This is definitely an issue with the OSTree design,
Hi Simo,
On Sat, 2014-01-25 at 14:55 -0500, Simo Sorce wrote:
> The reason is simple: lot's of software *changes* data as part of its
> normal functioning, including and often in rollback-incompatible ways.
I wrote and maintain a system that has been doing continuous deployment
of GNOME. It's b
On Fri, Jan 31, 2014 at 9:02 AM, Matthias Clasen
wrote:
I would be happy if Fedora moves towards being an OS,
Red Hat Enterprise Linux comes in both Server and Workstation variants,
among others. To continue to serve a useful role as upstream, I
believe Fedora should be able to do *both* of
The OpenEmbedded project has been doing this for quite a while:
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-devtools/python/python-2.7-manifest.inc
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
On Fri, Feb 19, 2016, at 02:37 PM, Kevin Fenzi wrote:
> * Setup tags for all the various groups that have kickstarts. ie,
> 'xfce' 'docker' 'cloud' 'atomic' 'workstation' etc. And get someone
> from each of those groups to actually watch the tags or someone to CC
> on who will actually loo
On Tue, Mar 22, 2016, at 08:27 AM, Stephen Gallagher wrote:
> I'd also point out that the supported mechanism for upgrading from F23 to F24
> is:
That's one of them - there are two. I have extended:
https://fedoraproject.org/wiki/Upgrading
to also cover rpm-ostree managed systems such as the Fe
On Fri, Apr 8, 2016, at 05:23 AM, Petr Pisar wrote:
> I'm curious how you would predict hash of initramfs because it is
> generated on the host and depends on dracut configuration and presence
> of various optionally installed packages.
That's true for a system managed by yum/dnf, but rpm-ostre
On Fri, Apr 8, 2016, at 05:36 AM, Florian Weimer wrote:
> Remote attestation only works with a trusted counterpart who rejects
> access once a breach is detected. Who do you expect to be the
> counterpart for Fedora users? Is there anyone who offers such a service
> without also requiring to u
On Thu, Apr 14, 2016, at 12:35 PM, Petr Šabata wrote:
> Good news, everyone,
>
> the first draft of the module metadata format is now available
> for you to comment on. We've decided to go with YAML so it
> should be fairly readable. You can view the latest version here:
>
> https://pagure.io/f
On Thu, Apr 28, 2016, at 06:52 PM, Adam Miller wrote:
> Docker Layered Image "packaging" Guidelines [1]
This current design means Dockerfiles are always secondary shims.
I think the most interesting case is for new services which are
Docker/container only at least upstream.
Do we e.g. requ
On Wed, May 18, 2016, at 03:06 PM, Subhendu Ghosh wrote:
> Is ostree remotes in scope?
ostree has /etc/ostree/remotes.d today...the only thing I can think of
here is that there are certainly use cases for having some common
configuration between yum repos and ostree remotes - things like TLS
cli
On Wed, Nov 16, 2016, at 02:49 PM, Stephen Gallagher wrote:
> Today, Fedora Server relies on whatever is the default for
> docker-storage-setup.
> We just tell Anaconda to reserve up to 15GiB by default for the / partition
> and
> then it puts all remaining free space (on drives selected to be u
On Wed, Nov 23, 2016, at 08:49 AM, Miroslav Suchý wrote:
> I just wanted to download F25 Cloud image for OpenStack and was surprised
> that there is none. There is just Atomic image.
> But Atomic use rpm-ostree for installing packages. There is no DNF.
On the host, yes. But the intent is to mov
On Tue, Dec 6, 2016, at 08:26 PM, Zbigniew Jędrzejewski-Szmek wrote:
> An alternative proposal: add a opt-out/opt-in flag (similar to
> _hardened_build)
> %global _strict_c_flags 0/1
What I've been doing for years now is to carry a baseline set of
"warnings that must be errors" in my projects, l
On Thu, Dec 8, 2016, at 01:26 PM, Dennis Gilmore wrote:
>
> I would like to see us stop pushing non security updates to updates from
> updates-testing entirely and do it in monthly batches instead. we would push
> daily security fixes and updates-testing. However this would make atomic
> host
On Thu, Dec 8, 2016, at 09:26 PM, Colin Walters wrote:
> Anyways, in the big picture, while I don't speak for everyone on the Project
> Atomic side,
> I personally point users at CentOS first, unless I have some reason to think
> they want Fedora.
> Something like 80% of
On Wed, Dec 21, 2016, at 07:19 AM, Björn Persson wrote:
> > The fontconfig cache files are placed onto /var/cache/fontconfig now.
> > this seems incompatible with the ostree model. so this is a proposal
> > to move it to /usr/lib/fontconfig/cache.
>
> Is OStree calling for the entire /var/cache
Hi,
rpm-ostree is the underlying hybrid image/package system for the Fedora Atomic
Host edition.
The layering functionality however requires some potential changes
in your packages.
https://bugzilla.redhat.com/show_bug.cgi?id=1415451
is a recent bug that shows one example. You can find more in
On Mon, Jan 23, 2017, at 02:03 PM, Tom Hughes wrote:
> How about you just explain here what it is you want rather than making
> everybody go and read some bug?
OK, here's a copy of the text:
rpm-ostree is a new model for rpm packages on using ostree[0]. In order to
implement atomic upgrades w
On Thu, Mar 26, 2020, at 8:35 AM, Zbigniew Jędrzejewski-Szmek wrote:
>
> Relying on the target distro management stack sound nice, but is
> actually problematic: how do you run the next version before you
> install the next version? Sure, you can install stuff to some temporary
> location and ru
On Mon, Apr 27, 2020, at 7:19 AM, Petr Šabata wrote:
> Details in the gist:
> https://gist.github.com/contyk/0f0585c57976ca18a293b3566408
How about s/use/globalbuildopt/ ?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send
On Mon, May 4, 2020, at 11:05 AM, Tomas Tomecek wrote:
> In the packit project, we work in source-git repositories
There's really 3 options:
- dist-git as it exists today (what we thought made sense in the days of CVS
converted into git without much re-engineering)
- source-git (used in Debia
On Wed, Oct 2, 2019, at 1:40 PM, Fabio Valentini wrote:
> As others in the thread have pointed out, mandatory pull requests just
> make no sense for most single-maintainer projects, which most packages
> probably are.
Well, a lot of this relates to what the *merge policy* is. If a PR submitter
On Wed, Oct 2, 2019, at 3:18 PM, Neal Gompa wrote:
> On Wed, Oct 2, 2019 at 2:45 PM Colin Walters wrote:
> >
> >
> >
> > On Wed, Oct 2, 2019, at 1:40 PM, Fabio Valentini wrote:
> >
> > > As others in the thread have pointed out, mandatory pull request
As part of creating Fedora CoreOS (and derivatives like Red Hat Enterprise
Linux CoreOS), we are making some fairly fundamental changes to how the
operating system works - while OSTree isn't new to Fedora, Ignition is - and
more broadly than that, using Ignition implies something much more simil
On Tue, Jul 30, 2019, at 4:13 PM, Zbigniew Jędrzejewski-Szmek wrote:
> Please note that the cgroup hierarchy default remains as "hybrid".
> Upstream has switched the default to "unified", but I reverted this
> switch in Fedora. If there are no major issues reported with this
> pre-release, the n
On Tue, Jul 30, 2019, at 3:52 PM, Daniel Walsh wrote:
> If you want small images, just use buildah.
Dockerfile-based multi-stage builds are significantly more popular than this
and should really be mentioned first.
I'm not saying `buildah` is bad, but...what you're talking about here also
enc
On Wed, Aug 7, 2019, at 11:25 AM, Colin Walters wrote:
>
>
> On Tue, Jul 30, 2019, at 3:52 PM, Daniel Walsh wrote:
> > If you want small images, just use buildah.
>
> Dockerfile-based multi-stage builds are significantly more popular than
> this and should really be m
On Wed, Aug 21, 2019, at 7:34 AM, Daniel Walsh wrote:
> I agree. Entering a container and doing a yum update is an
> Anti-pattern.
This is a complex discussion - I think we need both. Personally I
live inside a "pet" container using https://github.com/cgwalters/coretoolbox
and I definitely `y
FWIW,
For Fedora CoreOS we don't enable a firewall by default; see
https://github.com/coreos/fedora-coreos-tracker/issues/26
(Neither for that matter does Fedora Cloud:
https://pagure.io/fedora-kickstarts/blob/master/f/fedora-cloud-base.ks#_36 )
___
de
On Mon, Sep 16, 2019, at 12:45 PM, Troy Dawson wrote:
> systemd-sysusers seeks to unify user creation[1]. It also has the
> benefit of being able to create users on bootup. But, it pulls in the
> entire systemd infrastructure with all it's dependencies.
>
> containers do not need systemd to run.
On Wed, Sep 18, 2019, at 8:00 AM, Nico Kadel-Garcia wrote:
>
> You also have to pre-build your filesystems to have a place to copy
> the files into at installation time. If you're going to go to that
> much work, why are you bothering with yum? Why not just pre-build and
> install a base operati
On Thu, Sep 26, 2019, at 10:24 AM, Pierre-Yves Chibon wrote:
> I like this.
> It means that the build-system would have to generate the tarball of the
> source
> and put it into dist-git at srpm-build time (I believe we still want to store
> a
> copy of the sources used for a build).
https://gi
On Tue, Jan 7, 2020, at 6:41 AM, Tom Hughes wrote:
>
> I'd love to find a way to directly integrate the likes of gem, npm
> etc directly into our packaging rather than us having to repackage
> everything by hand but I just don't see any way of doing it without
> compromising what we do to the ext
On Sun, Jan 5, 2020, at 12:08 PM, Chris Murphy wrote:
> I've pretty much concluded Fedora is best off dropping the nested ext4
> in favor of plain squashfs, and using zstd.
Fedora CoreOS already uses zstd for squashfs:
https://github.com/coreos/coreos-assembler/blob/master/src/cmd-buildextend-
Hi,
On Mon, Jan 6, 2020, at 6:11 PM, Anthony Green wrote:
>
> I released a new version of libffi a month or so ago, the first one in 5
> years. There's an ABI change that was unavoidable in order to
> accommodate the aarch64 port, and the sonumber was bumped.
Anthony, I think all of the work yo
On Mon, Jan 20, 2020, at 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.
rpm-ostree[1] (used for Fedora CoreOS and Silverblue and IoT among o
On Mon, Mar 2, 2020, at 9:14 AM, Kalev Lember wrote:
> For extra libraries that app flatpaks need that are not part of the
> runtime, those we rebuild for the /app prefix for each app, using the MBS.
I think whenever discussing this, it needs to be stated clearly that the
*reason* for using th
On Wed, Jan 16, 2019, at 2:01 AM, Adam Williamson wrote:
> It seems the Atomic installer images from the nightly 'updates' and
> 'updates-testing' composes for F29 started failing as of 20190115.n.0
> and still failed in 20190116.n.0. Failure looks like:
>
> https://openqa.fedoraproject.org/tes
On Thu, Feb 14, 2019, at 6:05 AM, Javier Martinez Canillas wrote:
> So our plan is to have a library + command
> line tool for configuring everything related to the bootloader.
FWIW, "rpm-ostree kargs" is already a CLI and DBus API to change the kernel
arguments that we expect people to use on
On Thu, Mar 7, 2019, at 10:53 AM, Florian Weimer wrote:
>
> > The %transfiletriggerpostun would've probably fixed it if it used -p
> > instead of shell.
>
> We switched to the shell for the benefit of rpm-ostree.
Short answer:
https://github.com/projectatomic/rpm-ostree/issues/749#issuecomm
On Mon, Mar 11, 2019, at 2:46 PM, Fabio Valentini wrote:
>
> I'm having a similar problem, but with Silverblue / rawhide.
>
> I installed the system when rawhide was still f30, but now I can't run
> "rpm-ostree upgrade" anymore, due to this error:
>
> Enabled rpm-md repositories: rawhide
>
On Tue, Mar 12, 2019, at 2:50 PM, Kevin Fenzi wrote:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/5UVGSBRLX352A4S2CBZ2CGBXPAGQTYKB/
>
> How does this plan work with silverblue? Not sure... could use some
> input from them.
It's the same model for Fedora
On Tue, Apr 9, 2019, at 12:07 PM, Lennart Poettering wrote:
> Heya,
>
> today I installed the current Fedora 30 Workstation beta on my new
> laptop. It was a bumpy ride, I must say (the partitioner (blivet?)
> crashed five times or so on me, always kicking me out of anaconda
> again, just becaus
On Fri, Apr 12, 2019, at 7:13 AM, Lennart Poettering wrote:
> On Fr, 12.04.19 11:35, Dominik 'Rathann' Mierzejewski
> (domi...@greysector.net) wrote:
>
> > > Interestingly I think Google Chrome needs this when it installs,
> > > though it seems nonsensical to me. (Chrome is installed by about 5
On Thu, Apr 11, 2019, at 7:41 AM, Ty Young wrote:
> Hi,
>
> I'm thinking of switching to Fedora 30 Silverblue(once it comes out of
> beta anyway) from Arch linux. One of the requirements is to be able to
> install, compile from source and easily switch between JDK builds.
Bigger picture, as
Here's a related discussion for CoreOS-style systems:
https://github.com/coreos/fedora-coreos-config/pull/77
It's quite different from traditional since Ignition implies using
ConditionFirstBoot which means systemd does a preset-all on firstboot; the PR
is about the tension between what RPM is d
On Mon, Jun 17, 2019, at 4:47 AM, Michael Schroeder wrote:
> On Fri, Jun 14, 2019 at 12:12:01PM -0400, Neal Gompa wrote:
> > I would actually really like to see rpm's multiversioning capabilities
> > extended to support this.
>
> I'd actually prefer to drop the multiversion mode for the kernel a
On Mon, Jun 17, 2019, at 2:51 PM, Neal Gompa wrote:
> RPM-OSTree is functionally irrelevant in this discussion,
Changing how we handle the kernel is certainly relevant.
> since it has
> its own behavior patterns and eschews compatibility with the greater
> ecosystem anyway.
I don't think th
FWIW, rpm-ostree fixes all of this today - the entire update is really
transactional,
and fully handles hitting ENOSPC at any point.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.o
On Fri, Sep 28, 2018, at 2:42 PM, Andrew Lutomirski wrote:
> There's a request for the nvme-cli package to generate a unique name
> to use when connecting to NVMe-over-fabrics targets:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1633814
>
> I'm wondering what the right approach is. For the v
On Thu, Oct 11, 2018, at 8:37 PM, Marek Marczykowski-Górecki wrote:
> Hi all!
>
> I'm new on this list. I work on Qubes OS, where Fedora is used as a base
> distribution.
Tangentially: Qubes is very cool and I'm glad you find Fedora useful
as a base system. I work on Fedora CoreOS and have patch
This is one of a semi-regular rollup/highlights post of what's happening in the
rpm-ostree project, used by [Fedora Atomic Host](https://getfedora.org/atomic/)
as well as [Fedora Silverblue](https://silverblue.fedoraproject.org/), and
planned to be used by the converged [Fedora
CoreOS](https://
On Thu, Nov 15, 2018, at 10:57 AM, Matthew Miller wrote:
> On Thu, Nov 15, 2018 at 07:57:54AM -0700, Ken Dreyer wrote:
> > One of the problems I've encountered with this approach is that the
> > upstream Git repo links to (a lot of) submodules. If you're lucky
> > those submodules point at Git r
On Thu, Nov 15, 2018, at 12:38 PM, Ken Dreyer wrote:
> I am sorry to be such a noob, but I read the words on that page, they
> sound exciting, but I am lost. What does "mirror git repositories like
> rpmdistro-gitoverlay does" mean? I could use a really clear
> step-by-step walkthrough of how I
On Sat, Nov 17, 2018, at 12:24 PM, Jonathan Dieter wrote:
> Agreed, that this would be a massive format change and should therefore
> be a major version bump for RPM. New versions of RPM should still be
> able to read and install old-format rpms, but, as you point out, old
> versions of RPM won
On Wed, Mar 29, 2023, at 6:08 PM, Fabio Valentini wrote:
>
> I don't really want to throw money out the window just because DNF
> eats up all the memory it can :(
Everyone needs to internalize: This has nothing to do with DNF, really.
It's about the *size of the repository metadata*.
Every s
On Tue, Mar 21, 2023, at 8:16 AM, Karel Zak wrote:
> Hey all,
>
>
> util-linux v2.39-rc1 coming to rawhide, Release Notes:
> https://kernel.org/pub/linux/utils/util-linux/v2.39/v2.39-ReleaseNotes
>
> I usually don't report util-linux Fedora updates, but this one is
> special. This new version
On Thu, Jun 29, 2023, at 3:55 AM, Panu Matilainen wrote:
>> last time I looked auditd is started later than
>> systemd-sysusers. Hence not sure if sysusers would actually generate
>> audit messages that auditd could pick them up.
>
> For the rpm integration, "started later" is irrelevant as the us
On Fri, Dec 9, 2022, at 10:59 AM, Timothée Ravier wrote:
> Using layering will also conflict / not interact well with the move to
> container based ostree image in F38:
> https://fedoraproject.org/wiki/Changes/OstreeNativeContainerStable
(I'm only kind of following this thread and I agree we
On Thu, Dec 22, 2022, at 12:35 PM, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Shorter_Shutdown_Timer
>
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in order to receive
> community feedback. This proposal will only
;s job would be to scan if iscsi volumes are configured. If it
>> finds configured ones, it would then issue "systemctl start --no-block
>> iscsi.service" to enqueue a start job for the real thing.
>
>
> Something like that was suggested last year, and Colin Walters object
On Thu, Dec 8, 2022, at 9:51 AM, Daniel P. Berrangé wrote:
> I think the "Upgrade/compatibility impact" section ought to call out the
> possible risk with config mgmt tools like puppet/ansible, that might be
> managing SSH host keys and their permissions/ownership
So that was done with:
> The
On Fri, Aug 25, 2023, at 7:42 AM, Richard Hughes wrote:
> Hi all,
>
> I was thinking of adding Passim as a default-installed and
> default-enabled dep of fwupd in the Fedora 40 release. Before I create
> lots of unnecessary drama, is there any early feedback on what's
> described in https://githu
On Wed, Sep 13, 2023, at 1:44 PM, Matthew Miller wrote:
> On Mon, Sep 11, 2023 at 09:20:09AM -0700, Adam Williamson wrote:
>> IIRC it was a condition of that proposal that we wind up on a hosted
>> version of the *open source* release of gitlab, which is something we
>> managed to talk gitlab int
One thing I find amusing about this list (which like some others is kind of a
long-running soap opera that happens to sometimes produce software as a side
effect) is that many times, I can see just two bits of information:
- The subject of the email
- The name of the person responding
And I bas
On Fri, Sep 15, 2023, at 4:12 PM, Neal Gompa wrote:
> On Fri, Sep 15, 2023 at 1:28 PM Colin Walters wrote:
>>
>>
>> My point is only partly about the HTML, but about the ecosystem surrounding
>> it (CI is a really big one) but really the total user experience
On Mon, Sep 18, 2023, at 3:57 AM, Petr Pisar wrote:
> V Fri, Sep 15, 2023 at 01:27:23PM -0400, Colin Walters napsal(a):
>> To state the blindingly obvious thing, RHEL made a decision to centralize on
>> Gitlab. Having Fedora be on pagure creates IMO unnecessary friction for me
On Mon, Dec 11, 2023, at 12:31 PM, Neal Gompa wrote:
>
> We're currently not allowed to use /usr/etc (not that I like that path
> anyway) because it breaks RPM-OSTree. My understanding is that this
> directory is reserved by RPM-OSTree for storing pristine copies of
> /etc content for each OSTre
On Mon, Jan 15, 2024, at 8:57 AM, Fabio Valentini wrote:
> Hi all,
>
> I've been made aware that there has been a cascade of packages that
> dropped i686 support in Rawhide, most of them referencing my
> EncourageI686LeafRemoval Change Proposal, but none of which *actually
> are* leaf packages:
>
On Mon, Jan 15, 2024, at 8:57 AM, Fabio Valentini wrote:
> Hi all,
>
> I've been made aware that there has been a cascade of packages that
> dropped i686 support in Rawhide, most of them referencing my
> EncourageI686LeafRemoval Change Proposal, but none of which *actually
> are* leaf packages:
>
On Mon, Aug 29, 2022, at 3:52 AM, Brian (bex) Exelbierd wrote:
> I use Fedora IoT on GCPs free tier offering and it is fine. I a,
> assuming `rpm-ostree install` doesn’t have this issue.
It does have the issue.
rpm-ostree links to libdnf which is doing all the same things.
As I commented in
On Wed, Sep 7, 2022, at 5:35 AM, Richard W.M. Jones wrote:
> It was pointed out on the bug that librsvg2 is in a similar situation.
> The answer there was to bundle ("vendor") all the Rust dependencies
> into the tarball. The command "cargo vendor" does this.
>
> For librsvg2 that's 278MB of de
We shipped https://fedoraproject.org/wiki/Changes/OstreeNativeContainer in
Fedora 36 and a lot has happened since then.
One of the biggest things is that rpm-ostree now knows how to intelligently
generate reproducible "chunked" container images.
I'll describe this by also highlighting another
On Wed, Sep 28, 2022, at 9:47 AM, Rahul Sundaram wrote:
> FYI, the command in that page doesn't appear to be working because
> "latest" is the default tag if you don't specify one for docker and it
> doesn't exist, so you have to append ":stable" or something like that.
https://github.com/cor
On Tue, Sep 27, 2022, at 6:08 PM, Colin Walters wrote:
> We shipped https://fedoraproject.org/wiki/Changes/OstreeNativeContainer
> in Fedora 36 and a lot has happened since then.
Also, I should mention that we're planning to use this in OpenShift, see
https://github.com/openshift/e
On Mon, Oct 10, 2022, at 7:41 AM, Antonio Murdaca wrote:
> Hi folks, in rpm-ostree based systems like fedora iot I would love to
> handle the migration process similar to what happens today in
> silverblue et all wrt sysroot.readonly
> https://pagure.io/workstation-ostree-config/blob/main/f/po
301 - 400 of 563 matches
Mail list logo
