30.11.2020 23:27, Paul Gevers wrote:
Hi all, Christian,
On Tue, 8 Sep 2020 15:40:11 +0200 Christian Ehrhardt
<[email protected]> wrote:
Signed-off-by: Christian Ehrhardt <[email protected]>
---
...raseReserved-override-driver-queue_p.patch | 74 ++++++++
...BlockEraseReserved-skip-unless-iSCSI.patch | 39 ++++
...e-Write-override-driver-queue_pdu-ca.patch | 71 ++++++++
...e-Write-skip-InvalidDataOutSize-unle.patch | 39 ++++
...EraseReserved-override-driver-queue_.patch | 74 ++++++++
...ryptoEraseReserved-skip-unless-iSCSI.patch | 39 ++++
...iteReserved-override-driver-queue_pd.patch | 68 +++++++
...-test-tool-Use-extern-int-in-headers.patch | 58 ++++++
...mdSnTooHigh-override-driver-queue_pd.patch | 68 +++++++
...mdSnTooLow-override-driver-queue_pdu.patch | 69 ++++++++
...ataSnInvalid-override-driver-queue_p.patch | 166 ++++++++++++++++++
...-unused-iscsi_queue_pdu-symbol-overl.patch | 104 +++++++++++
debian/patches/series | 12 ++
13 files changed, 881 insertions(+)
Uh-oh...
[]
If your comfortable, can this please be uploaded? libiscsi is a key
package (so won't be autoremoved) and the freeze is getting near. Let's
not wait with fixing this until the latest moment.
So, is it another case of poorly maintained upstream software
which become a key package?
Speaking of the upload, - I hoped upstream will finally catch up
and release a new version (with another soversion bump as Ronni
does each time wrongly, despite numerous attempts to teach him
to do it properly), - but it seems it's a dead hope, so yes,
we should upload the fixed version, - if new upstream release
will come before freeze we can consider using it too.
Lemme handle it if there's no objections.
Thanks,
/mjt
