On Wed, Oct 9, 2024 at 2:19 PM Kilian Hanich via devel <
devel@lists.fedoraproject.org> wrote:
> Am 09.10.24 um 17:12 schrieb Simo Sorce:
> >> Hence I am very curious where you think the security issues are?
> > Sorry, I did not mean in any way to imply there are open security issue
> > with syste
On Fri, Aug 2, 2024 at 8:31 AM Cristian Le via devel <
devel@lists.fedoraproject.org> wrote:
> On 2024/08/01 17:27, Owen Taylor wrote:
>
> On Thu, Aug 1, 2024 at 9:24 AM Neal Gompa wrote:
>
>>
>> Well, if you have a general package that's shipped in every build
On Thu, Aug 1, 2024 at 9:24 AM Neal Gompa wrote:
> On Thu, Aug 1, 2024 at 9:13 AM Owen Taylor wrote:
> >
> > Hi Neal -
> >
> > Daniel's original suggestion here (make pkg-config always look in /app
> too) actually seems fine to me and simple, and I don&#
Hi Neal -
Daniel's original suggestion here (make pkg-config always look in /app too)
actually seems fine to me and simple, and I don't see any downsides. But
certainly flatpak-rpm-macros doesn't *just* modify RPM macros, it currently
also:
- Changes the installation prefix for Python by droppin
On Tue, May 14, 2024 at 6:50 AM Panu Matilainen wrote:
>
> Patch and source numbers start from zero, that goes for automatically
> numbered patches too. So there's an off by one in the application, and
> the latter %autopatch which is supposed to apply patches >= 2 simply has
> nothing to do, and
One practical example - the process of creating an OCI container image of
the Fedora Flatpak runtime does a *lot* of zlib compression and
decompression. (https://pagure.io/flatpak-module-tools/issue/22). A lot of
that is temporary to save disk space and IO bandwidth and could be switched
to zstd or
On Sun, Jul 2, 2023 at 5:01 PM Demi Marie Obenour
wrote:
> On 6/3/23 08:42, Michael Catanzaro wrote:
> > On Sat, Jun 3 2023 at 10:26:07 AM -, John Iliopoulos <
> jxftw2...@gmail.com> wrote:
> >> Hello,
> >>
> >> While i completely understand why you do this i do think that it is
> >> importan
On Tue, Jun 6, 2023 at 7:50 AM Leon Fauster via devel <
devel@lists.fedoraproject.org> wrote:
> Is the Fedora OCI flatpak approach not about the trust into the chain of
> flatpak creation? src -> signed rpm -> flatpak? So, even in an ideal world
> where RHEL is immutable and the best workstation e
On Mon, Jun 5, 2023 at 8:35 AM Josh Boyer wrote:
> On Mon, Jun 5, 2023 at 6:28 AM Debarshi Ray via devel
> wrote:
>
> I wanted to wrap up this sub-thread on-list, after Owen and I chatted
> > about it off-list.
> >
> > I am fine with having the fedora-toolbox OCI images being defined as
> > kick
On Tue, May 30, 2023 at 9:47 AM Debarshi Ray wrote:
> Hey Owen,
>
> On Mon, 2023-05-29 at 12:39 -0400, Owen Taylor wrote:
> > On Mon, May 29, 2023 at 8:16 AM Debarshi Ray via devel
> > wrote:
> > >
> > > My main concern, which I had brought up in the R
On Mon, May 29, 2023 at 8:16 AM Debarshi Ray via devel <
devel@lists.fedoraproject.org> wrote:
> Hey Owen,
>
> On Wed, 2023-05-24 at 13:50 -0400, Owen Taylor wrote:
> >
> > What if we made the Toolbox container image just one more base image
> &g
On Thu, May 25, 2023 at 6:57 AM Petr Pisar wrote:
> V Thu, May 25, 2023 at 06:04:51AM -0400, Owen Taylor napsal(a):
> > * We need to rebuild files that can contain data from both parts
> > (/etc/ld.so.conf, /usr/lib/fontconfig/cache, etc.)
>
> How does splitting files fr
On Thu, May 25, 2023 at 4:02 AM Florian Weimer wrote:
> * Owen Taylor:
>
> > On Fri, May 12, 2023 at 1:34 PM Florian Weimer
> wrote:
>
> > Do you have a pointer where I can read up on the current approach?
> >
> > Some references that I found quickly:
>
On Tue, May 9, 2023 at 11:52 AM Kevin Fenzi wrote:
> Just a general answer/info here at the bottom of the thread...
>
> I realize our container build pipeline is not great, but it's currently
> working and I will keep it working until we replace it.
>
> I agree we should replace it, and there's l
On Wed, May 17, 2023 at 4:42 AM Petr Pisar wrote:
> [...]
> > Any Fedora packager can rebuild a package into f39-app using 'fepdkg
> > build --target=f39-app'.
> >
> [...]
> > Once a package exists in f39-app or f38-app, then
> > [[
> https://gitlab.com/redhat/centos-stream/ci-cd/distrosync/distr
On Mon, May 15, 2023 at 1:51 AM Milan Crha wrote:
> On Wed, 2023-05-10 at 09:30 -0400, Owen Taylor wrote:
> > Does that sound workable? Are there better ways we could do it?
>
> Hi,
> if I recall correctly, using the custom D-Bus prefix is there to match
> appli
On Sat, May 13, 2023, 4:24 AM Mattia Verga via devel <
devel@lists.fedoraproject.org> wrote:
> Il 13/05/23 03:04, Owen Tay rt I look
>
> On Fri, May 12, 2023, 1:03 PM Mattia Verga via devel <
> devel@lists.fedoraproject.org> wrote:
>
>> Il 10/05/23 12:54, Aoife Moloney ha scritto:
>> M kk kk kk kk
On Fri, May 12, 2023 at 1:34 PM Florian Weimer wrote:
> * Owen Taylor:
>
> > On Wed, May 10, 2023 at 9:48 AM Florian Weimer
> wrote:
> >
> > * Aoife Moloney:
> >
> > > There are two types of Flatpak containers -
> > > runtimes - w
On Fri, May 12, 2023, 1:03 PM Mattia Verga via devel <
devel@lists.fedoraproject.org> wrote:
> Il 10/05/23 12:54, Aoife Moloney ha scritto:
> > https://fedoraproject.org/wiki/Changes/FlatpaksWithoutModules
> >
> >
> I've never tried to make a flatpak because I was scared by the need of
> firstly b
On Thu, May 11, 2023 at 2:31 PM Dan Čermák
wrote:
> Hi,
>
> Aoife Moloney writes:
>
> > https://fedoraproject.org/wiki/Changes/FlatpaksWithoutModules
> >
> snip
> >
> > There is considerable implementation complexity within OSBS to implement
> this,
> > because the N/V/R need to be written into
> I'm just wondering whether the name suffix is the right place to put
"flatpak" as if it were a subpackage - can we use the dist tag instead, say
`fi39` for "fedora immutable based on fedora 39" or something like that? Or
`fp39` for `fedora flatpak ...`?
The main difference is what happens when y
On Wed, May 10, 2023 at 5:34 PM Chris Murphy
wrote:
>
>
> On Wed, May 10, 2023, at 2:24 PM, Owen Taylor wrote:
>
>
>
> On Wed, May 10, 2023 at 12:02 PM Neal Gompa wrote:
>
>
> Now, there's a second problem with reading everything from the ESP - it's
>
On Wed, May 10, 2023 at 12:02 PM Neal Gompa wrote:
>
> This proposal isn't better. Neither Windows nor macOS put critical
> operating system code in the ESP, and we shouldn't either. But you
> want to put kernels in the ESP? That's the wrong approach too.
>
> As soon as you throw UKIs in the mix,
On Wed, May 10, 2023 at 9:48 AM Florian Weimer wrote:
> * Aoife Moloney:
>
> > There are two types of Flatpak containers -
> > runtimes - which contain unmodified Fedora packages,
> > and applications - which contain Fedora packages rebuilt to relocate
> > them from /usr to /app.
>
> Is this relo
On Wed, May 10, 2023 at 8:06 AM Milan Crha wrote:
> On Wed, 2023-05-10 at 11:54 +0100, Aoife Moloney wrote:
> > Additionally a couple of packages (evolution-data-services and
> > tracker-miners) are set up so they can be
> > built with an application-specific D-Bus prefix. Evolution has:
> >
> >
On Tue, May 9, 2023 at 2:31 PM Chris Adams wrote:
> Once upon a time, Chris Murphy said:
> > What about the increasing growth in linux-firmware and in particular the
> NVIDIA firmware requirements? My reading suggests it's significant and the
> future growth also significant.
>
> Could we use a
On Tue, May 9, 2023 at 12:39 PM Neal Gompa wrote:
> On Tue, May 9, 2023 at 12:31 PM Lennart Poettering
> wrote:
> >
> > On Di, 09.05.23 08:22, Neal Gompa (ngomp...@gmail.com) wrote:
> >
> > > I've been asked to consider converting /boot to a Btrfs subvolume so
> > > that it no longer has a fixed
On Fri, Apr 7, 2023 at 5:12 AM Simo Sorce wrote:
> On Thu, 2023-04-06 at 12:56 -0400, Owen Taylor wrote:
> > On Thu, Apr 6, 2023 at 12:32 PM Simo Sorce wrote:
> >
> > > On Mon, 2023-04-03 at 16:18 -0500, Michael Catanzaro wrote:
> > > > On Mon, Apr 3 2023
On Thu, Apr 6, 2023 at 12:32 PM Simo Sorce wrote:
> On Mon, 2023-04-03 at 16:18 -0500, Michael Catanzaro wrote:
> > On Mon, Apr 3 2023 at 01:41:48 PM -0700, Brian C. Lane
> > wrote:
> > > This seems like exactly the kind of discussion that belongs on the
> > > devel
> > > list, not on a website
I just posted a thread on discussion.fedoraproject.org:
https://discussion.fedoraproject.org/t/future-of-encryption-in-fedora/80397
to invite discussion of a requirements document and draft plan about what
we might do for encrypting Fedora Workstation systems in the future. Please
follow up ther
For years, Red Hat Linux / Fedora systems have had a umask of 0002 for
regular users as part of the "user private group" scheme [*]. Basically the
idea is that you can set a directory group-sticky and use it as a common
work area for a group of users.
A change a couple of years ago seems to have p
On Wed, Feb 16, 2022 at 12:14 PM Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/polkit_recommends_pkla_pkexec
> [..]
> `pkexec` and `pkla-compat`
> ([https://src.fedoraproject.org/rpms/polkit-pkla-compat package]) are
> legacy tools that are no longer needed on a desktop and increase
On Thu, Feb 17, 2022 at 2:28 PM Adam Williamson
wrote:
> On Wed, 2022-02-16 at 13:55 -0500, Neal Gompa wrote:
> > On Wed, Feb 16, 2022 at 12:38 PM Lennart Poettering
> > wrote:
> > >
> > > On Mi, 16.02.22 12:12, Ben Cotton (bcot...@redhat.com) wrote:
> > >
> > > > `pkexec` and `pkla-compat`
> >
On Sat, Jul 3, 2021 at 4:39 PM Mark Otaris wrote:
>
> I don’t agree with this change, as it seems obvious that many users who do
> not want proprietary software installed do not want repositories with
> proprietary software in them installed either (whether or not these
> repositories are enabl
On Sat, Jul 3, 2021 at 6:14 PM Fabio Valentini wrote:
>
> On Tue, Jun 29, 2021 at 10:26 PM Ben Cotton wrote:
> >
> > https://fedoraproject.org/wiki/Changes/Filtered_Flathub_Applications
> >
> > == Summary ==
> > Enabling third-party repositories will now create a Flathub remote
> > that is a filt
On Wed, Jun 30, 2021 at 9:26 AM Vitaly Zaitsev via devel
wrote:
>
> On 30/06/2021 14:44, Owen Taylor wrote:
> > Setting up an independent non-profit, and maintaining it's non-profit
> > status is a quite involved activity. (details depend on the country,
> > of cours
On Wed, Jun 30, 2021 at 7:53 AM Zbigniew Jędrzejewski-Szmek
wrote:
> > * There is a fedora-third-party package with a
> > fedora-third-party script with
> > enable/disable/refresh/query subcommands. The status is
> > stored in /etc/fedora-third-party.conf
> > * Packages like fedora-workstation-re
On Wed, Jun 30, 2021 at 7:44 AM Ian McInerney wrote:
>> Roughly speaking, the criteria for including software is a) will not
>> cause legal or other problems for Fedora to point to b) does not
>> overlap Fedora Flatpaks or software in Fedora that could easily be
>> made into a Flatpak c) works re
On Wed, Jun 30, 2021 at 6:42 AM Vitaly Zaitsev via devel
wrote:
>
> On 29/06/2021 22:25, Ben Cotton wrote:
> > Enabling third-party repositories will now create a Flathub remote
> > that is a filtered view of Flathub.
>
> I don't trust Flathub at all, because they don't want to register a
> non-pr
On Wed, Jun 30, 2021 at 6:50 AM Lars Seipel wrote:
> >[Find out
> >more...](https://fedoraproject.org/wiki/Workstation/Third_Party_Software_Repositories)
> >* If the user leaves the box checked, GNOME Initial setup runs
> >`fedora-third-party enable`.
>
> Leaves the box checked? Either I'm misund
On Fri, May 7, 2021 at 12:17 PM Jerry James wrote:
>
> On Fri, May 7, 2021 at 9:45 AM Michael Catanzaro wrote:
> > Um... not that I know of.
> >
> > Honestly, I don't know anything about GLib 1 other than that it's very
> > old. I think if I were trying to port Sagemath, I would just upgrade
> >
On Sun, May 2, 2021 at 9:46 PM Ian McInerney wrote:
[...]
> This is how to reproduce it:
> 1) Use the Cinnamon live CD
> 2) Install a random flatpak (note, since this is on live you have to deal
> with the space issue first)
> sudo ostree --repo=/var/lib/flatpak/repo/ config set
> core.min-f
On Sat, May 1, 2021 at 10:09 AM Neal Gompa wrote:
>
> On Sat, May 1, 2021 at 9:48 AM Owen Taylor wrote:
> >
> > On Sat, May 1, 2021, 7:51 AM Neal Gompa wrote:
> >>
> >> In general, I'd like to see if we can figure out *why* Mutter isn't
> >
On Sat, May 1, 2021, 7:51 AM Neal Gompa wrote:
>
> Note it only looks fine as long as you're not using fractional
> scaling. Once framebuffer/fractional scaling is enabled in Mutter, it
> looks absolutely terrible, because X11 applications are not scaled
> properly. There are also other glitches
On Wed, Apr 21, 2021 at 4:09 PM Frank Ch. Eigler wrote:
> A direct way would be for someone to koji-download the given rpm, and
> hand-extract/compare the files. (It's obviously not economical.)
>
> > Thus, the debuginfod server becomes a juicy target.
>
> Yes. The Changes FAQ section discusses
On Sun, Apr 11, 2021 at 1:52 PM Owen Taylor wrote:
>
>
> On Sat, Apr 10, 2021 at 9:55 AM Michael Catanzaro
> wrote:
>
>> On Sat, Apr 10 2021 at 08:03:09 AM -0400, Owen Taylor
>> wrote:
>> > Did you notice that it also works for the Fedora Flatpaks (thanks,
&
On Sat, Apr 10, 2021 at 9:55 AM Michael Catanzaro
wrote:
> On Sat, Apr 10 2021 at 08:03:09 AM -0400, Owen Taylor
> wrote:
> > Did you notice that it also works for the Fedora Flatpaks (thanks,
> > Frank!) - basic proof of concept:
> >
> > $ flatpak run --comman
On Fri, Apr 9, 2021 at 11:01 AM Michael Catanzaro wrote:
>
> On Fri, Apr 9 2021 at 04:19:31 PM +0200, Lars Seipel
> wrote:
> > Really cool. Thanks for making it happen.
>
> I started testing the staging server yesterday. It seems a little slow
> -- I worry for anyone debugging anything that links
On Tue, Dec 22, 2020 at 5:31 AM Michael Schwendt wrote:
>
> On Mon, 21 Dec 2020 08:09:50 -0500, Owen Taylor wrote:
>
> > Most likely the GPU driver. This is a symptom of a corrupted Xft glyph
> > cache inside the Xwayland X server.
> >
> > (It's not impossib
On Mon, Dec 21, 2020 at 4:37 AM Michael Schwendt wrote:
>
> In the attached screenshot excerpt it's the bold "a" character that is
> missing everywhere within the entire main window of Claws Mail. In other
> cases, it's a different character. Sometimes it is not missing but
> visually corrupted, l
So, this was discussed quite a bit in
https://pagure.io/fedora-workstation/issue/71 and the conclusion that
the Workstatopn Working Group came to 3 months ago was that we didn't
want to do this. We basically understood that main way of using
thermald was to use the proprietary dptfxtract tool to ex
On Thu, Aug 8, 2019 at 2:34 PM Antonio M
wrote:
> I am the reporter of bug
> https://bugzilla.redhat.com/show_bug.cgi?id=1738614
> I have never such an issue before kernels 5..2.x and it is not always true
> that clicking on notation bar solves the issue
>
Do you think you could try downgrading
Recently filed bugs about similar issues:
https://bugzilla.redhat.com/show_bug.cgi?id=1738614
https://bugzilla.redhat.com/show_bug.cgi?id=1739169
Not sure if they are the *same* problem or different problems. They
look like the same issue (cursor only visible over application
windows) - but one r
On Fri, Mar 22, 2019 at 1:04 PM Japheth Cleaver wrote:
>
> On 3/21/2019 3:23 PM, Richard W.M. Jones wrote:
>
> So what? On Fedora /bin/sh is bash, and bash is a fine shell.
>
> All this nonsense of using dash for /bin/sh on Debian is IMO a
> pointless bunch of make-work.
>
> Fedora has certainly
On Thu, Feb 21, 2019 at 3:04 AM Peng Wu wrote:
> When the langpack packages Requires font(:lang=xx), it will pull in
> one random font package choose from several fonts packages which
> Provides font(:lang=xx).
>
> To fix random fonts dependencies problem, I think maybe we can
> manually add "
On Thu, Jan 31, 2019 at 12:23 PM Pete Walter wrote:
> I've noticed that someone created a flatpak build for one of my packages
> (feedreader), but it's horribly out of date: flatpak has 2.5.1 vs rpm has
> 2.7.0. I've been trying to update the flatpak build, but not much luck here.
> The documen
Jens-Ulrik Petersen wrote:
>
> On Mon, Jan 28, 2019 at 8:04 AM Owen Taylor wrote:
>>
>> I see that I have ibus-typing-booster installed, but I don't see any
>> sign of it in the GNOME "Region & Language" panel input source
>> selection. Does ibus-typin
> Currently, ibus-m17n is the default input method for Indian languages
> in Fedora. ibus-typing-booster uses the same libm17n used by
> ibus-m17n to support input for Indian languages and thus it can do
> everything ibus-m17n can do. But on top of that, ibus-typing-booster
> supports predictive i
If I understand the proposal, I'm slightly concerned that the proposed
use of Supplements: means that there will be no longer any single
place where we declare "this is our recommended font for LangX, this
is our recommended input method for LangX" - the history of this will
be collectively over al
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 -
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 o
On Tue, Jan 8, 2019 at 7:17 AM Benjamin Berg wrote:
>
> On Tue, 2019-01-08 at 12:33 +0100, Miroslav Suchý wrote:
> > Dne 08. 01. 19 v 11:35 Nicolas Mailhot napsal(a):
> > > *which* *do* *not* *permit* *or* *no* *longer* *permit* *the*
> > > *identification* *of* *data* *subjects*
> >
> > How do yo
On Mon, Dec 10, 2018, 4:24 AM Samuel Rakitničan <
srakitni...@fedoraproject.org wrote:
> Hi,
>
> Got an e-mail from Koschei [1] with a notice that camotics package is
> starting to fail to build. The reason for this seems to be that something
> that used to pull mesa-libEGL-devel doesn't do so any
On Wed, Nov 28, 2018 at 12:40 PM Stephen John Smoogen wrote:
> On Wed, 28 Nov 2018 at 11:37, Owen Taylor wrote:
> > Fedora needs to be an operating system provider, not just an operating
> > system toolbox provider.
>
> I feel like we have been saying this for 15+ yea
On Wed, Nov 28, 2018 at 3:07 AM Brian (bex) Exelbierd
wrote:
> I think that Fedora's role as an innovater in the OS space means we
> should be aggressively exploring this. Rolling Releases, Tech-Driven
> Releases and Time-Based Releases all have well known positives and
> negatives. All of the
ote:
>
> On 11/27/18 10:13 AM, Josh Boyer wrote:
> > On Tue, Nov 27, 2018 at 11:21 AM Owen Taylor wrote:
> >>
> >> On Tue, Nov 27, 2018 at 11:05 AM Josh Boyer
> >> wrote:
> >>> On Tue, Nov 27, 2018 at 10:13 AM Owen Taylor wrote:
> >>>&
On Tue, Nov 27, 2018 at 10:51 AM Stephen Gallagher wrote:
> As came up in another part of the earlier thread, I think this is an
> opportunity for Modularity. For those things like GNOME that want to
> rev mid-release, if they shipped the 3.34 release as new stream, those
> that want to move to it
On Tue, Nov 27, 2018 at 11:05 AM Josh Boyer wrote:
> On Tue, Nov 27, 2018 at 10:13 AM Owen Taylor wrote:
> > But for the next thousand or so Fedora developers, the release cycle
> > is actually not a big deal - not something that takes much of their
> > time - and it gives
One of the key parts of making a decision to delay/skip F31 is
figuring out, ahead of the decision, what the expected experience is
for users and packagers. Does F30 have normal stability, or do we try
to keep users happy by moving things forward with ad-hoc updates and
cross-our-fingers and hope n
On Tue, Nov 27, 2018 at 10:12 AM Stephen John Smoogen wrote:
> Define what a compose is? Currently it is a word which covers a
> multitude of different processes and reasons for those processes. We
> can't 'fix' or even 'replace' or parallel them without actually
> knowing why someone duct taped t
On Mon, Nov 26, 2018 at 9:26 PM Brendan Conoboy wrote:>
> On 11/16/18 7:50 AM, Paul Frields wrote:
> [snip]
> > We should skip the F31 release cycle and leave F30 in place longer in
> > order to focus on improving the tooling and testing changes. These
> > tooling changes will improve the overall
A lot of discussion about improving the compose process seem to end up
with a "reality check" - that ideas have already been tried but don't
work because of requirements a) b) c) d). You can't have the pony, but
maybe if a lot of effort is put into it, you can have a faster rocking
horse.
If want
On Mon, Nov 26, 2018 at 9:59 AM Tomasz Kłoczko wrote:
> 1) if dbus service crashes/is not availaible temporary IMO it wold be
> good to prepare whole desktop apps code to not crash but handle dbus
> disconnection and maybe display centered message that it is not
> possible to connect to dbus. Cras
Thanks for starting this discussion, Matthew!
A few notes:
* My personal long-term dream is that all Fedora users are running
Silverblue, we do great automated QA testing, and upgrading from one
Fedora to the next is a non-event, and opt-out rather than opt-in, and
long term support would not be
On Mon, Sep 24, 2018 at 10:15 AM Miro Hrončok wrote:
> On 21.9.2018 12:19, Miro Hrončok wrote:
> > We updated python-matplotlib to 3.0.0. It only supports Python 3. This
> > was done in Rawhide only.
> >
> > The python2-matplotlib* subpackages were moved to a new SRPM,
> > python2-matplotlib (rem
On Mon, Sep 24, 2018 at 7:04 AM Adam Samalik wrote:
> I thought about this for a while, and I can see some conceptual
> similarities between upgrading a major Fedora release and changing a module
> stream. I tried to think about major Fedora releases (I mean f28, f29, etc)
> as "streams" of Fedor
Using modules for this purpose will take some care for parallel
installability - unless you are happy with sagemath only being runnable
from within a container.
Unless I'm missing something, to restore a python2 subpackage that has been
removed in the main Fedora, you'd need to:
- Create a strea
Hi Bastien,
Here are some of the benefits I see of this effort as compared to simply
telling users to consume Flatpaks from Flathub or independent repositories:
* Benefit to Flaptak users on all distributions: more applications are
available more quickly. Some applications will be much easier to
On Fri, Sep 7, 2018 at 5:29 AM, Martin Kolman wrote:
> On Fri, 2018-09-07 at 05:06 -0400, Owen Taylor wrote:
>
[...]
> That's *very* nice & something I have been calling for basically from day
> one with flatpacks.
>
> Not everyone wants to become a relea
On Fri, Sep 7, 2018 at 3:36 AM, Vít Ondruch wrote:
> Dne 7.9.2018 v 03:45 Owen Taylor napsal(a):
>
> [...]
>
> If you maintain a graphical application, please try creating a Flatpak of
> it. Your experience will vary - some applications are quite easy, but if
> your app
On Fri, Sep 7, 2018 at 4:03 AM, Michal Konečný wrote:
> I thought there will be some automatic building script for flatpaks, so
> the maintainers doesn't need to do it by themselves.
> Is this automatization now dropped?
>
One level of automation is 'fedmod rpm2flatpak' which automatically figur
On Fri, Sep 7, 2018 at 2:52 AM, Robin Lee
wrote:
> What does it mean for 'Fedora' Flatpaks?
> - Flatpaks that run on a Fedora runtime? Then, what's the benifit to
> use Fedora runtime instead of freedesktop ones?
> - Flatpaks that maintained by Fedora community? Then, why not
> encourage people t
I'd like to invite Fedora contributors to start creating Flatpaks of
graphical applications in Fedora. We're still working on putting the final
pieces into place to have a complete story from end to end, but it's
definitely close enough to get started.
If you maintain a graphical application, plea
On Tue, Sep 4, 2018, 11:54 PM Ray Strode wrote:
> Hi,
>
> On Tue, Sep 4, 2018 at 4:00 PM Owen Taylor wrote:
> I haven't dealt with modularity yet, really, so tell me if i wrong (i'm
> kind of guessing a little bit from briefly snooping around). module
> building is
The current idea
=
A Flatpak is a module. The way that the module is deployed is by creating a
Flatpak container from the module. (Other modules might be deployed by
installing by RPMs directly or creating a server container.)
Because Flatpaks are a module, they share the modules/ nam
What are the possibilities for how a stream is maintained? The cases I can
think of:
* Indefinite - rolling forward with upstream - "master" "stable" etc.
* Tied to an upstream version and it's EOL - a "2.1" stream of django
* [less common] tied to a particular version of Fedora - the "29" str
Hi Rex,
As part of my Flaptak efforts, I've been looking what libraries and other
packages are used by our most popular applications and I noticed that all
applications using KDE libraries are pulling in a pile of perl packages. As
far as I can tell, this is only because of the two scripts:
/usr
The Fedora today, there was a presentation about a vision for how
applications should have a different life cycle than the operating system:
https://flock2018.sched.com/event/Fjdk/at-long-last-rings-split-lifecycles
For Flatpaks, the future is now - as soon as we start building them, I'd
like to
I'm interested in participating with a special interest in Flatpaks - the
other type of Fedora container ;-) - I want to keep things aligned as much
as possible. And also from the perspective of using containers for
development within Fedora Workstation.
I can contribute a certain familiarity with
On Fri, Jul 27, 2018 at 9:44 AM, Florian Weimer wrote:
> On 07/27/2018 03:33 PM, John Reiser wrote:The key principle is that
> sizeof(foo) must be the stride of an array of foo,
>
> and the array must guarantee alignment of each element in the array.
>>
>
> Why do you think that? If some documen
I'm not sure it needs to be mentioned in the change proposal - but there
are some caveats to this as it applies to the workstation:
* There are no plans to add any user interface to enable/disable modules
in the GNOME Software user interface.
* If we even want graphical applications from enabled
dency 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 retiremen
It sounds like what we are doing is shipping the "regional subset" fonts
for all 4 CJK scripts. I wonder if we would do better to ship one unified
font - I believe that at least with the GNOME stack, the rendered results
will be equivalent, since Pango+Harfbuzz should set appropriate 'locl' tags
(h
On Fri, Mar 16, 2018 at 4:04 PM, Dennis Gregorovic
wrote:
> The challenge here is that those module builds are squeezed into a N-V-R
> format when imported into Koji. The N-V-R format is used for all build
> types in Koji and it works well for its purpose, but it's also not
> realistic to expect
;
>
> ----- Mail original -
> De: "Owen Taylor"
>
> Hi Owen,
>
> > Is there a guide for Fedora packagers about how to handle unbundling for
> > golang packages? The draft guidelines don't seem to go into any details.
>
> I don't think there is,
Hi Nicolas,
Is there a guide for Fedora packagers about how to handle unbundling for
golang packages? The draft guidelines don't seem to go into any details.
I've looked at packaging a few golang packages unbundled, and have
immediately run into:
A) lots of unpackaged dependencies
B) dependenci
On Thu, Jan 11, 2018 at 1:08 PM, Adam Williamson wrote:
> On Thu, 2018-01-11 at 10:19 -0700, Chris Murphy wrote:
> > On Thu, Jan 11, 2018 at 3:26 AM, James Hogarth
> wrote:
> >
> > > Having upgraded and freshly installed systems so different is going to
> > > be messy with supporting users and i
On Wed, 2017-08-23 at 17:25 +0100, Richard Hughes wrote:
> On 23 August 2017 at 13:57, Marius Vollmer wrote:
> > In a modular repository, I think the same thing should happen so that
> > GNOME Software can present interesting modules to the user in a nice
> > way.
>
> What kind of modules would b
Hi Langdon,
Thanks for all the work that went into the process and guidelines!
My particular interest is in what I consider the simplest use case - taking an
existing leaf-node application (desktop or otherwise), creating a module that
only includes that application and is not meant for buildi
On Tue, 2017-08-08 at 13:39 -0400, Ralph Bean wrote:
> ## Solution: "Input" Modulemd Syntax Changes
>
> We’re going to extend the modulemd syntax to allow specifying multiple
> dependencies in an "input" modulemd (the one that packagers modify). When
> submitted to the build system, the module-bu
1 - 100 of 148 matches
Mail list logo
