11, 2020 at 2:49 PM Owen Taylor wrote:
>
> From: "Owen W. Taylor"
>
> This is an initial attempt to create a configuration for flatpak-indexer to
> replace
> regindexer and add an image delta capability. The config here is derived from
> a working openshift
From: "Owen W. Taylor"
flatpak-indexer replaces regindexer for creating an index of Fedora
Flatpaks. It adds an additional capability
Add a new openshift namespace: flatpak-indexer, with three deploymentconfigs
in it:
- flatpak-indexer: generates the index
- flatpak-indexer-differ: worker(s)
From: "Owen W. Taylor"
This is an initial attempt to create a configuration for flatpak-indexer to
replace
regindexer and add an image delta capability. The config here is derived from
a working openshift configuration, but is untested in this form.
See:
Introduction
=
The original way that Flatpaks were updated was via ostree
repositories. More recently, the ability was added to distribute them
as container images, and that is what we do for the Fedora build
Flatpaks via registry.fedoraproject.org.
The one big gap we have between the two
From: "Owen W. Taylor"
Flatpak-1.6 expects metadata to be stored in Docker-compatible labels
rather than OCI annotations. We build Flatpaks for Fedora with both
labels and annotations for compatibility with older and newer Flatpaks,
but we also need to have two sets of indexes:
- One that is
One of the main goals for Fedora 31 Silverblue was to have core
applications that were removed a few releases ao from the Silverblue
fixed image because they could be installed as Flatpaks actually
pre-installed when you install Silverblue. The anaconda feature landed
this cycle, and we have all
[ Summary: if you are going to rebuild the OSBS buildroot image in the
near future, talk to me to make sure things don't break ]
I just submitted a new version of flatpak-module-tools to Bodhi. This
updates flatpak-module-tools to use the libmodulemd v2 API - this was
forced because
On Thu, Jan 31, 2019 at 3:06 PM Kevin Fenzi wrote:
> This looks fine to me.
Thanks for taking a look, Kevin!
> I guess we should coordinate a time to apply this and any other changes
> at the same time?
https://pagure.io/fedora-infrastructure/issue/7496 has the details of
what needs to be
From: "Owen W. Taylor"
Configure pagure to allow a flatpaks/ namespace, and koji and MBS
to allow building from it.
When we sync package ownership to Koji, the f29-flatpaks tag (which has
the Flatpak containers) tag gets everything in the flatpaks/ namespace,
while the f29-modular tag gets
On Tue, Jan 8, 2019 at 12:28 PM Owen Taylor wrote:
> * In fedscm_admin: Map flatpaks namespace to the ‘module’ PDC branch
> type when storing the SLA into the PDC, to avoid PDC changes, and
> because the SLA really is a module SLA.
Digging into this, I don't think this is right - it wo
Currently, the content for a Flatpak in Fedora can be found in
modules/. E.g.:
https://src.fedoraproject.org/modules/quadrapassel/tree/master - I’d
like to propose creating a separate namespace in src.fedoraproject.org
- flatpaks/
Benefits:
* Allow automation to easily distinguish Flatpaks from
expansion to build a container locally
rpkg
Load the modulemd module we are building into a flatpak to find what
runtime it is using, and hence the right build target
Thanks!
Owen
On Mon, May 21, 2018 at 1:29 PM, Owen Taylor wrote:
> My understanding is that with the planned retirem
My understanding is that with the planned retirement of the PDC:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/JHKHWYU5XK7H2P2QZZCCQR4ZRCTY3OSB/
Querying for module information should be done using the MBS and/or Koji
APIs.
Various code that I
The Docker registry protocol has very limited search and index
functionality - you can (if enabled on the server) list all repositories,
list tags for each repository, and then download the manifest for each tag.
This obviously is very inefficient if you want to ask questions like:
* "What
14 matches
Mail list logo
