On Thu, Mar 06, 2025 at 12:41:49PM +0100, Chris Hofstaedtler wrote: > On Thu, Mar 06, 2025 at 12:23:31PM +0100, Petter Reinholdtsen wrote: > > Is the esptool package still being maintained? I notice no upload for > > many years and a new upstream available, > > There was an upload by Faidon in 2024, adding to CC:.
Yeah I made three major uploads in 2023-2024, but I very explicitly made them as -0.1 NMUs: I wanted to see a few things happen, but I did not want to commit on maintaining this in the longer-term. So while I've been subscribed to the PTS and had seen this bug when it was first posted, I refrained from commenting on it since I am not nor want to be the maintainer. Sorry :) I do have the bandwidth for maybe another upload if necessary, but I agree that this package needs a bit more "permanent" love, perhaps under the auspices of a team like the Electronics team. (To be clear, I had an ongoing off-list thread with Milan when I made these uploads who was gracious enough to both welcome these uploads and to invite me to be a comaintainer.) With that out of the day, my 2ยข with regards to this bug: I know very little about AppStream, but this proposal doesn't make sense to me. cdc_acm is just a driver for modems and serial devices and the likes. Some ESP32 devices support this interface; for these devices, cdc_acm creates /dev/ttyACM nodes, that esptool then uses as a transport for communicating/flashing these devices using a bespoke protocol. esptool targets only a set of very specific devices, which represent a tiny fraction of all the possible cdc_acm devices out there. If this AppStream inclusion means that esptool will be recommended to every CDC ACM device, then I think that would be very confusing to users and generally not the right thing to do. Regards, Faidon
