Bug#1024221: Bug#1022573: transition: procps
On Thu, 22 Dec 2022 at 19:50, Paul Gevers wrote: > That's (in general) sub-optimal for the release team. We try hard to > avoid entangling transitions and therefor we try to finish transitions > sooner rather than later. My preference would be that you NMU (minimal > changes) now; the maintainer can always update the pending changes after > the migration happened. > Sure thing Paul; I have uploaded an NMU which is only the patch that gets it to link to libproc2. I know upstream made some slight changes, with the patch I sent them but it was for things like using exit instead of return for some functions when there was a failure, but most of them used both anyway so it seemed pretty arbitrary. If /proc is unmounted or malloc fails, you're in a world of hurt anyway. Timo, if you need help getting the next version linked to libproc2 I've done both versions so I can help. - Craig
Bug#1024221: Bug#1022573: transition: procps
Hi Craig, On 22-12-2022 00:28, Craig Small wrote: BUT, procps is in transition and this linking needs to happen before the first freeze milestone so I will upload 20220525 linked to libproc2 if we get near to running out of time. That's (in general) sub-optimal for the release team. We try hard to avoid entangling transitions and therefor we try to finish transitions sooner rather than later. My preference would be that you NMU (minimal changes) now; the maintainer can always update the pending changes after the migration happened. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1024221: Bug#1022573: transition: procps
(added the bug report for igt) On Thu, 22 Dec 2022 at 08:29, Craig Small wrote: > On Thu, 22 Dec 2022 at 07:46, Paul Gevers wrote: > >> An actual upload. If the maintainer isn't doing it, I think an NMU is >> appropriate if you're sure of the fix. >> > Ah, I thought you were the igt maintainer :) > > I'll have a go recreating it and uploading it tonight. I'm pretty > confident about the patches but don't use the package myself. > So the issue is that the changelog has updated the version to 1.26+git20221011-1 but this isn't uploaded or tagged. I can either: Attach my patch for 1024221 to bug #1024221 and wait Update to 20221011 and add the patch, this both links to libproc2 and updates the version Roll-back to 20220524 and add the patch, keeps the binary the same linked to libproc2 but moves the changelog back Ideally, I'd like 20221011 linked to libproc2 but I don't want to release a new version of intel-gpu-tools as I'm not the maintainer and there might be a reason its not being updated. BUT, procps is in transition and this linking needs to happen before the first freeze milestone so I will upload 20220525 linked to libproc2 if we get near to running out of time. - Craig > - Craig > >
