Your message dated Wed, 09 Nov 2016 09:37:12 +0800 with message-id <1478655432.9579.25.camel@debian.org> and subject line Re: Bug#843215: fwupd: Please announce supported hardware using appstream has caused the Debian Bug report #843215, regarding fwupd: Please announce supported hardware using appstream to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 843215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843215 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: bts <submit@bugs.debian.org>
- Subject: fwupd: Please announce supported hardware using appstream
- From: Paul Wise <pabs@debian.org>
- Date: Sat, 05 Nov 2016 13:00:54 +0800
- Message-id: <[🔎] 1478322054.1979.20.camel@debian.org>
Package: fwupd Severity: wishlist User: pere@hungry.com Usertags: appstream-modalias X-Debbugs-CC: pere@debian.org Please announce the supported hardware via AppStream. That will allow users that are using isenkram to know that they might want to install fwupd when they plugin a device that can get firmware updates. More info about how to do this is available on the wiki page: https://wiki.debian.org/AppStream/Guidelines#Announcing_supported_hardware -- bye, pabs https://wiki.debian.org/PaulWiseAttachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
- To: Mario Limonciello <Mario.Limonciello@dell.com>, 843215-done@bugs.debian.org
- Subject: Re: Bug#843215: fwupd: Please announce supported hardware using appstream
- From: Paul Wise <pabs@debian.org>
- Date: Wed, 09 Nov 2016 09:37:12 +0800
- Message-id: <1478655432.9579.25.camel@debian.org>
- In-reply-to: <[🔎] 42a8176a939c42139a08b255143309e3@ausx13mpc120.AMER.DELL.COM>
- References: <[🔎] 1478322054.1979.20.camel@debian.org> <[🔎] fb9951c0e2fc4185a6e2cab833eb23ee@ausx13mpc120.AMER.DELL.COM> <[🔎] 1478581149.9579.13.camel@debian.org> <[🔎] 42a8176a939c42139a08b255143309e3@ausx13mpc120.AMER.DELL.COM>
On Tue, 2016-11-08 at 22:51 +0000, Mario Limonciello wrote: > On the contrary, I would disagree here. Those devices just show > information about the current firmware on the device from udev. > Prompting the user to install fwupd just to see this information > seems like a giant waste of time. The really valuable ones are > the ones that you can actually perform an update for. I see, thanks for explaining the situation to me, closing bug then. > Actually ARM platforms I think make a lot of sense too. I suppose for UEFI based ones where the firmware is proprietary, sure. > Fwupd can perform updates for USB type devices (DFU & Colorhug) that > can both be used with ARM platforms. IIRC the ColourHug firmware is open source, so it is exactly the kind of device where Debian should package the firmware properly. > It also has specific support for Raspberry Pi FW: > https://github.com/hughsie/fwupd/blob/master/src/fu-provider-rpi.c I would rather Debian properly package the open RPi firmware instead: https://github.com/christinaa/rpi-open-firmware > Actually in looking closer at this, this doesn't really make sense given > what isenkram does. It duplicates effort from what gnome-software > already does with fwupd. Not everyone uses GNOME, so I still think it would be useful. -- bye, pabs https://wiki.debian.org/PaulWiseAttachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---