Bug#810018: Bug #810018: Consider shipping pidof with procps

2023-11-13 Thread Luca Boccassi
On Mon, 13 Nov 2023 at 21:07, Craig Small wrote: > > On Tue, 14 Nov 2023 at 06:09, Mark Hindley wrote: >> >> IIUC, the proposal[1] was to create a new Essential procps-base just >> containing >> pidof. Otherwise bin:procps would have to become Essential itself. Its >> installed >> size is

Bug#810018: Bug #810018: Consider shipping pidof with procps

2023-11-13 Thread Craig Small
On Tue, 14 Nov 2023 at 06:09, Mark Hindley wrote: > IIUC, the proposal[1] was to create a new Essential procps-base just > containing > pidof. Otherwise bin:procps would have to become Essential itself. Its > installed > size is about 20 times larger than sysvinit-util and that wouldn't >

Bug#810018: Bug #810018: Consider shipping pidof with procps

2023-11-13 Thread Luca Boccassi
On Mon, 13 Nov 2023 at 19:14, Mark Hindley wrote: > > Craig, > > Thanks for this. > > On Mon, Nov 13, 2023 at 08:08:37PM +1100, Craig Small wrote: > > I'll need the assistance of the sysvinit-utils maintainers (CC'ed) as > >well, as pidof will be moving from that package. > > IIUC, the

Bug#810018: Bug #810018: Consider shipping pidof with procps

2023-11-13 Thread Mark Hindley
Craig, Thanks for this. On Mon, Nov 13, 2023 at 08:08:37PM +1100, Craig Small wrote: > I'll need the assistance of the sysvinit-utils maintainers (CC'ed) as >well, as pidof will be moving from that package. IIUC, the proposal[1] was to create a new Essential procps-base just containing

Bug#810018: Bug #810018: Consider shipping pidof with procps

2023-11-13 Thread Luca Boccassi
On Mon, 13 Nov 2023 at 09:17, Craig Small wrote: > > > On Sat, 11 Nov 2023 at 23:45, Luca Boccassi wrote: >> >> Now that Bookworm has shipped, what about finally finishing this and >> getting rid of this debianism? There is really no reason to delay it >> any longer at this point. Thank you! > >

Bug#810018: Bug #810018: Consider shipping pidof with procps

2023-11-13 Thread Craig Small
On Sat, 11 Nov 2023 at 23:45, Luca Boccassi wrote: > Now that Bookworm has shipped, what about finally finishing this and > getting rid of this debianism? There is really no reason to delay it > any longer at this point. Thank you! > Hi Luca, I'll need the assistance of the sysvinit-utils

Bug#810018: Bug #810018: Consider shipping pidof with procps

2023-11-11 Thread Luca Boccassi
On Mon, 21 Mar 2022 15:07:21 -0700 Josh Triplett wrote: > On Mon, Mar 21, 2022 at 02:01:14PM +0100, Andreas Henriksson wrote: > > On Mon, Mar 21, 2022 at 10:34:58AM +, Mark Hindley wrote: > > > Craig, > > > > > > Thanks for this. > > > > > > This dates from before my detailed involvement

Bug#810018: Bug #810018: Consider shipping pidof with procps

2022-03-21 Thread Josh Triplett
On Mon, Mar 21, 2022 at 02:01:14PM +0100, Andreas Henriksson wrote: > On Mon, Mar 21, 2022 at 10:34:58AM +, Mark Hindley wrote: > > Craig, > > > > Thanks for this. > > > > This dates from before my detailed involvement with this area of Debian. I > > have > > read through the bug report,

Bug#810018: Bug #810018: Consider shipping pidof with procps

2022-03-21 Thread Andreas Henriksson
Hello Mark, Craig, On Mon, Mar 21, 2022 at 10:34:58AM +, Mark Hindley wrote: > Craig, > > Thanks for this. > > This dates from before my detailed involvement with this area of Debian. I > have > read through the bug report, but apologies if I have missed pertinent detail. [] > 3) A

Bug#810018: Bug #810018: Consider shipping pidof with procps

2022-03-21 Thread Mark Hindley
Craig, Thanks for this. This dates from before my detailed involvement with this area of Debian. I have read through the bug report, but apologies if I have missed pertinent detail. I am happy to work with you to achieve this if it is really worthwhile and time well spent. However, I am yet to

Bug#810018: Bug #810018: Consider shipping pidof with procps

2022-03-21 Thread Craig Small
Hello, You may recall quite some time ago there was this bug #810018 where it was asked can procps ship pidof so that sysvinit-utils could have its Essential flag removed. That was.. back in 2016. Is this still something that would be useful to be done? Michael put some good work in looking