netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: Petter Reinholdtsen <pere@debian.org>,
	netdev@vger.kernel.org, Robert Scheck <fedora@robert-scheck.de>,
	AsciiWolf <mail@asciiwolf.com>
Subject: Re: [mail@asciiwolf.com: Re: ethtool: Incorrect component type in AppStream metainfo causes issues and possible breakages]
Date: Thu, 24 Apr 2025 15:29:15 +0200	[thread overview]
Message-ID: <aAo8q1X882NYUHmk@eldamar.lan> (raw)
In-Reply-To: <CAB-mu-QE0v=eUdvu_23gq4ncUpXu20NErH3wkAz9=hAL+rh0zQ@mail.gmail.com>

Hi Michal,

On Fri, Apr 11, 2025 at 10:48:44PM +0200, AsciiWolf wrote:
> Please note that as pointed out in my previous emails, the binary
> provides seems to be required for console-application component type.
> 
> Daniel
> 
> pá 11. 4. 2025 v 22:18 odesílatel AsciiWolf <mail@asciiwolf.com> napsal:
> 
> >
> > Here is the proposed fix. It is validated using appstreamcli validate
> > and should work without issues.
> >
> > --- org.kernel.software.network.ethtool.metainfo.xml_orig
> > 2025-03-31 00:46:03.000000000 +0200
> > +++ org.kernel.software.network.ethtool.metainfo.xml    2025-04-11
> > 22:14:11.634355310 +0200
> > @@ -1,5 +1,5 @@
> >  <?xml version="1.0" encoding="UTF-8"?>
> > -<component type="desktop">
> > +<component type="console-application">
> >    <id>org.kernel.software.network.ethtool</id>
> >    <metadata_license>MIT</metadata_license>
> >    <name>ethtool</name>
> > @@ -11,6 +11,7 @@
> >    </description>
> >    <url type="homepage">https://www.kernel.org/pub/software/network/ethtool/</url>
> >    <provides>
> > +    <binary>ethtool</binary>
> >      <modalias>pci:v*d*sv*sd*bc02sc80i*</modalias>
> >    </provides>
> >  </component>
> >
> > Regards,
> > Daniel Rusek

Is there anything else you need from us here? Or are you waiting for
us for a git am'able patch? If Daniel Rusek prefers to not submit one,
I can re-iterate with the required changes my proposal 
https://lore.kernel.org/netdev/20250411141023.14356-2-carnil@debian.org/
with the needed changes.

We would like to apply the change in downstream Debian fwiw, but only
with the variant accepted by upstream.

Regards,
Salvatore

  reply	other threads:[~2025-04-24 13:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 13:47 [mail@asciiwolf.com: Re: ethtool: Incorrect component type in AppStream metainfo causes issues and possible breakages] Michal Kubecek
     [not found] ` <CAB-mu-QjxGvBHGzaVmwBpq-0UXALzdSpzcvVQPvyXjFAnxZkqA@mail.gmail.com>
2025-04-11 14:07   ` ethtool: Incorrect component type in AppStream metainfo causes issues and possible breakages Petter Reinholdtsen
2025-04-11 20:18   ` [mail@asciiwolf.com: Re: ethtool: Incorrect component type in AppStream metainfo causes issues and possible breakages] AsciiWolf
2025-04-11 20:48     ` AsciiWolf
2025-04-24 13:29       ` Salvatore Bonaccorso [this message]
2025-04-25 16:46         ` Michal Kubecek
2025-04-25 19:38           ` Salvatore Bonaccorso
2025-04-29 20:37             ` Michal Kubecek
2025-04-30 14:43               ` Salvatore Bonaccorso
     [not found]                 ` <CAB-mu-QfzzZX8x-rPsras9r7jA2vMSpNqimV0h-OBOaa-z2tuQ@mail.gmail.com>
2025-04-30 15:02                   ` Salvatore Bonaccorso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aAo8q1X882NYUHmk@eldamar.lan \
    --to=carnil@debian.org \
    --cc=fedora@robert-scheck.de \
    --cc=mail@asciiwolf.com \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=pere@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).