Bug#997851: Update on doas package status

2022-05-08 Thread Jesse Smith
Thanks for the update. Having a Debian package (even an unofficial one) would be nice. I can still post install instructions for it in our README file. Is it possible to rename the existing package or add  warning to it to let people know the "doas" package in Debian is actually OpenDoas and not

Bug#997851: Update on doas package status

2022-05-06 Thread Scupake
Hello, A little update on this issue. I found out that I am not be able to upload both packages into the Debian repositories since the two programs are too similar to each other. However I can provide packages for slicer69/doas on a git repo since the packaging for it is pretty much done. I am

Bug#997851: Update on doas package status

2022-04-17 Thread Jesse Smith
On 2022-04-17 11:49 a.m., Scupake wrote: > Hello, > > I'm very very sorry for taking an unreasonable time to reply and resolve > this issue. I will try to be more active from now on. > > I'm also currently packaging slicer69/doas, though I still haven't > decided on a name, I would like to use

Bug#997851: Update on doas package status

2022-04-17 Thread Scupake
Hello, I'm very very sorry for taking an unreasonable time to reply and resolve this issue. I will try to be more active from now on. I'm also currently packaging slicer69/doas, though I still haven't decided on a name, I would like to use "doas-portable" if it is at least mentioned in

Bug#997851: Update on doas package status

2022-03-02 Thread Jesse Smith
This issue has been open for several months now without an update and I'd like to encourage its resolution. The upstream doas project is still getting issue reports [1] which are resulting from confusion in the naming between "doas" versus "OpenDoas". Ideally this package should have its name