On Wed, Oct 25, 2023 at 3:23 PM Daniel Alley wrote:
>
> >There are arguments
> > about whether it's appstream-builder specific (given that Debian's
> > archive is bigger, their package format is more complex to "pluck"
> > from, etc and appstream-generator does fine there), but the point is
> >
>There are arguments
> about whether it's appstream-builder specific (given that Debian's
> archive is bigger, their package format is more complex to "pluck"
> from, etc and appstream-generator does fine there), but the point is
> that for Fedora with appstream-builder, it's too slow. Note that
Seconding that, the did, at least in the past, and they do interpret the severity of
deviations differently than the written standard.
On 24.10.23 14:26, Michael Catanzaro wrote:
On Tue, Oct 24 2023 at 08:06:12 AM -0400, Neal Gompa wrote:
The two tools don't have incompatible ideas of valid
On Tue, Oct 24 2023 at 08:06:12 AM -0400, Neal Gompa
wrote:
The two tools don't have incompatible ideas of valid metadata, we
intentionally don't do strict validation.
Well for one example incompatibility, you can review that issue:
https://github.com/ximion/appstream/issues/476
Michael
On Fri, Sep 29, 2023 at 12:39 PM Kevin Fenzi wrote:
>
> On Thu, Sep 28, 2023 at 01:03:08PM +0100, Richard Hughes wrote:
> > On Wed, 27 Sept 2023 at 22:41, Kevin Fenzi wrote:
> > > I'm not sure at all that it would be possible to do at compose-time...
> > > composes are taking around 3.5-4hours
On Tue, Oct 24, 2023 at 7:54 AM Michael Catanzaro wrote:
>
> On Mon, Sep 25 2023 at 09:15:37 PM -0400, Neal Gompa
> wrote:
> > There was no switching. Both appstream-util and appstreamcli are
> > considered conformant.
> >
> > Ultimately, the only way we can stop relying on appstream-glib is if
On Mon, Sep 25 2023 at 09:15:37 PM -0400, Neal Gompa
wrote:
There was no switching. Both appstream-util and appstreamcli are
considered conformant.
Ultimately, the only way we can stop relying on appstream-glib is if
appstream-builder[1] was reimplemented on top of libappstream-compose.
Long
Hi list,
just a heads up: because we're talking about how to validate appstream metadata: When
validating metadata, one of the "default" warnings you get is:
> In the past, mailto: URL schemas to link to email addresses were also supported for
this URL type. It is recommended to not use them
On Thu, Sep 28, 2023 at 01:03:08PM +0100, Richard Hughes wrote:
> On Wed, 27 Sept 2023 at 22:41, Kevin Fenzi wrote:
> > I'm not sure at all that it would be possible to do at compose-time...
> > composes are taking around 3.5-4hours and thats after I have done
> > a lot to speed them up, but
On Thu, 28 Sept 2023 at 08:03, Richard Hughes wrote:
> On Wed, 27 Sept 2023 at 22:41, Kevin Fenzi wrote:
> > I'm not sure at all that it would be possible to do at compose-time...
> > composes are taking around 3.5-4hours and thats after I have done
> > a lot to speed them up, but might be
On Wed, 27 Sept 2023 at 22:41, Kevin Fenzi wrote:
> I'm not sure at all that it would be possible to do at compose-time...
> composes are taking around 3.5-4hours and thats after I have done
> a lot to speed them up, but might be worth some benchmarking
> to see how much slower it would be. If we
I must say that I found appstreamcli to be to unstable in CI of projects that I used to
maintain, and file format documentation and validator source code reality diverge, and
behaviour is understandably changed between appstreamcli revisions. We had to disable and
later re-enable the metainfo
Il 27/09/23 23:49, Neal Gompa ha scritto:
> On Wed, Sep 27, 2023 at 5:41 PM Kevin Fenzi wrote:
>> On Wed, Sep 27, 2023 at 10:05:38AM -0400, Neal Gompa wrote:
>>> On Wed, Sep 27, 2023 at 9:48 AM Richard Hughes wrote:
On Wed, 27 Sept 2023 at 13:23, Mattia Verga via devel
wrote:
>
On Wed, Sep 27, 2023 at 5:41 PM Kevin Fenzi wrote:
>
> On Wed, Sep 27, 2023 at 10:05:38AM -0400, Neal Gompa wrote:
> > On Wed, Sep 27, 2023 at 9:48 AM Richard Hughes wrote:
> > >
> > > On Wed, 27 Sept 2023 at 13:23, Mattia Verga via devel
> > > wrote:
> > > > Can't this script be moved to run
On Wed, Sep 27, 2023 at 10:05:38AM -0400, Neal Gompa wrote:
> On Wed, Sep 27, 2023 at 9:48 AM Richard Hughes wrote:
> >
> > On Wed, 27 Sept 2023 at 13:23, Mattia Verga via devel
> > wrote:
> > > Can't this script be moved to run in Openshift as cron-based?
> >
> > Yes! In fact, that's what I
On Wed, Sep 27, 2023 at 9:48 AM Richard Hughes wrote:
>
> On Wed, 27 Sept 2023 at 13:23, Mattia Verga via devel
> wrote:
> > Can't this script be moved to run in Openshift as cron-based?
>
> Yes! In fact, that's what I proposed about a decade ago when I wanted
> to include the data in the
On Wed, 27 Sept 2023 at 13:23, Mattia Verga via devel
wrote:
> Can't this script be moved to run in Openshift as cron-based?
Yes! In fact, that's what I proposed about a decade ago when I wanted
to include the data in the metadata like Debian does. I do think it
should be managed by someone in
Il 27/09/23 13:24, Richard Hughes ha scritto:
> On Tue, 26 Sept 2023 at 03:16, Neal Gompa wrote:
>> So a stopgap solution was implemented: appstream-data. Richard Hughes
>> maintains a local mirror of the full Fedora repositories and generates
>> the appstream data from that using scripts[1] and
On Tue, 26 Sept 2023 at 03:16, Neal Gompa wrote:
> So a stopgap solution was implemented: appstream-data. Richard Hughes
> maintains a local mirror of the full Fedora repositories and generates
> the appstream data from that using scripts[1] and extra data[2] to
> produce the appstream-data
On Mon, Sep 25, 2023 at 1:45 PM Alexander Ploumistos
wrote:
>
> On Mon, Sep 25, 2023 at 7:33 PM Artur Frenszek-Iwicki
> wrote:
> >
> > Without docs, the whole process is a black box.
>
> +1
>
> That was actually one of the two reasons I started this thread.
>
> For instance, is this the package
On Sun, Sep 24, 2023 at 2:46 AM Mattia Verga via devel
wrote:
>
> Il 24/09/23 01:18, Neal Gompa ha scritto:
> > On Sat, Sep 23, 2023 at 6:05 PM Michael Catanzaro
> > wrote:
> >> On Sat, Sep 23 2023 at 10:26:48 PM +0200, Alexander Ploumistos
> >> wrote:
> >>> Could someone involved
> >>> with
On Mon, Sep 25, 2023 at 7:33 PM Artur Frenszek-Iwicki
wrote:
>
> Without docs, the whole process is a black box.
+1
That was actually one of the two reasons I started this thread.
For instance, is this the package that must be rebuilt in order to see
an AppStream metadata file appear/refreshed
> Ultimately, appstream-util's output is what matters since we use
> appstream-builder (from appstream-glib) to generate our AppStream
> metadata index. If it doesn't pass that tool, it doesn't show up.
Bit of a tangent, but: is this documented anywhere?
Because if if is, then I can't find it.
Il 24/09/23 01:18, Neal Gompa ha scritto:
> On Sat, Sep 23, 2023 at 6:05 PM Michael Catanzaro
> wrote:
>> On Sat, Sep 23 2023 at 10:26:48 PM +0200, Alexander Ploumistos
>> wrote:
>>> Could someone involved
>>> with AppStream please provide some information? Shouldn't our
>>> documentation be
24. syyskuuta 2023 2.18.14 GMT+03:00 Neal Gompa kirjoitti:
>> On Sat, Sep 23 2023 at 10:26:48 PM +0200, Alexander Ploumistos
>> wrote:
>> > Could someone involved
>> > with AppStream please provide some information? Shouldn't our
>> > documentation be changed to reflect these changes? Does
On Sat, Sep 23, 2023 at 6:05 PM Michael Catanzaro wrote:
>
> On Sat, Sep 23 2023 at 10:26:48 PM +0200, Alexander Ploumistos
> wrote:
> > Could someone involved
> > with AppStream please provide some information? Shouldn't our
> > documentation be changed to reflect these changes? Does the FPC
On Sat, Sep 23 2023 at 10:26:48 PM +0200, Alexander Ploumistos
wrote:
Could someone involved
with AppStream please provide some information? Shouldn't our
documentation be changed to reflect these changes? Does the FPC need
to decide on this?
From upstream perspective: appstream-util is
The current state of things, Fedora-wise, is summarized in FPC ticket #1053:
https://pagure.io/packaging-committee/issue/1053
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Hello,
According to our packaging guidelines[1], "you MUST run appstream-util
validate-relax (in %check or %install) and have BuildRequires:
libappstream-glib, to help ensure the validity and safety of the
appdata files you’re installing".
For quite some time now, I've been seeing references to
29 matches
Mail list logo
