We could add the NVME support via cherrypick in active development release (hirsute) as proposed by my colleague Victor, but I would rather prefer to see lshw to bump version from B.02.18 to B.02.19 so that hirsute will be updated (take the opportunity that Hirsute is in development release to do the necessary to save us time later when Hirsute will become stable)
To do so Debian has to accept the bump, and I'll then do a sync or merge from debian/unstable to ubuntu/Hirsute.
Let's see if Debian is reactive to my request, and I'll adjust accordingly.
In order of preference:
1) If Debian is reactive in a timely fashion to my request, I'll wait for them to bump the package and then merge/sync into Ubuntu.
2) If Debian takes time to answer to my request, I'll sponsor Victor's patchset as is.
But I do think it's worth putting this on hold a couple of days and wait for a possible outcome for scenario #1.
[sts-sponsors] [hirsute]
I have reported a bug against debian/lshw: /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 977774
https:/
We could add the NVME support via cherrypick in active development release (hirsute) as proposed by my colleague Victor, but I would rather prefer to see lshw to bump version from B.02.18 to B.02.19 so that hirsute will be updated (take the opportunity that Hirsute is in development release to do the necessary to save us time later when Hirsute will become stable)
https:/ /ezix.org/ project/ wiki/HardwareLi Ster#Changes
To do so Debian has to accept the bump, and I'll then do a sync or merge from debian/unstable to ubuntu/Hirsute.
Let's see if Debian is reactive to my request, and I'll adjust accordingly.
In order of preference:
1) If Debian is reactive in a timely fashion to my request, I'll wait for them to bump the package and then merge/sync into Ubuntu.
2) If Debian takes time to answer to my request, I'll sponsor Victor's patchset as is.
But I do think it's worth putting this on hold a couple of days and wait for a possible outcome for scenario #1.
- Eric