Ok, so not having full context as some of the discussion was happening on IRC (and no mention of it was left on the bug here + the package was not rejected from the queue), I have possibly prematurely accepted the libnet-ssleay-perl SRU. After getting logs from Rik I see there's still no consensus on whether the read()/write() behavioral change is wanted/acceptable or not. When reviewing the package I got the impression that it was an approved change (per regression potential).
To my defense: with bionic-proposed being in a broken state causing build failures for both packages and images, the only two sane options were either accepting the package as-is or removing the two previous SRUs from -proposed.
Since I was obviously missing context and did barge in uninvited: Steve, if you think that the SRU is not really acceptable as is, please request a follow up upload with further changes. Thanks.
Ok, so not having full context as some of the discussion was happening on IRC (and no mention of it was left on the bug here + the package was not rejected from the queue), I have possibly prematurely accepted the libnet-ssleay-perl SRU. After getting logs from Rik I see there's still no consensus on whether the read()/write() behavioral change is wanted/acceptable or not. When reviewing the package I got the impression that it was an approved change (per regression potential).
To my defense: with bionic-proposed being in a broken state causing build failures for both packages and images, the only two sane options were either accepting the package as-is or removing the two previous SRUs from -proposed.
Since I was obviously missing context and did barge in uninvited: Steve, if you think that the SRU is not really acceptable as is, please request a follow up upload with further changes. Thanks.