Hi
As a result of a revert of v2020 of ksh last year, the current version
on sid for ksh is as follows:
2020.0.0+really93u+20120801-10
With the next upgrade, we're looking to move to the 93u+m community
maintained distribution that has a different versioning scheme (starting
with 1.0.0-beta.1).
On Fri, Sep 10, 2021 at 02:25:32PM +0100, Phil Morrell wrote:
> On Fri, Sep 10, 2021 at 05:18:13PM +0530, Anuradha Weeraman wrote:
> Then there appears to be this 93u+m project publishing essentially v2020
> as 1.0.0 beta, tagged as 'v1.0.0-beta.1'. It's release notes
On Fri, Sep 10, 2021 at 07:37:55PM +0530, Anuradha Weeraman wrote:
> > 2) If you do go ahead with switching to the community distribution, then
> > "93u+m" is part of the name, not the version number, so I'd suggest:
> >
> > 1:1.0.0~beta.1-1
>
> It do
On Sat, Sep 11, 2021 at 10:16:00AM -0400, Michael Stone wrote:
> Hmm. If the project refers to itself as 93u+m does it make sense to package
> it as ksh instead of something like ksh93u+m? This reminds me of when debian
> first packaged openssh as "ssh" because that's what the predecessor package
>
On Sat, Sep 11, 2021 at 07:50:52PM +0200, Timo Röhling wrote:
> * Anuradha Weeraman [2021-09-11 21:37]:
> https://wiki.debian.org/RenamingPackages has a few good suggestions.
> Maybe the transition package method would be appropriate here?
> You could probably put the transitional
On Fri, Oct 11, 2019 at 06:49:37PM -0400, Scott Kitterman wrote:
> I have been told by docker users (I'm not one) that systemd as provided on
> Debian can't be used in docker. I have no idea if that's true or not. I try
> really hard to know as little about init systems as possible and trust ou
6 matches
Mail list logo
