Bug#720441: Got a fix, how to submit patch.

2013-10-28 Thread ольга крыжановская
I think I am done with the Debian testing, and fixes, to *properly* integrate ast-ksh.2013-10-10 into Debian, with functionality and scope similar to Opensolaris PSARC/2006/550 - the shell is much more stable now, and properly has all its builtins working. Olga On Thu, Oct 10, 2013 at 2:44 AM, Ol

Bug#720441: Got a fix, how to submit patch.

2013-10-09 Thread Phi Debian
I did produce a patch, and posted it. The patch implement the exact same code as the one later given by the code owner, i.e init a local with 0. So now if wheezy is frozen, it can still be patched, the current source version you got with wheezy actually contain already 5 patch, plus mine it goes t

Bug#720441: Got a fix, how to submit patch.

2013-10-09 Thread Oliver Kiddle
ольга крыжановская wrote: > What is the way to replace the patched up 2012-02-29? Find sponsor, > declare him how bad it is? I think so. One thought is that you could try to pester Jonathan Wiltshire : he did 93u+-1.2. It is probably wise to prepare the replacement first. Oliver -- To UNSUBSC

Bug#720441: Got a fix, how to submit patch.

2013-10-09 Thread ольга крыжановская
What is the way to replace the patched up 2012-02-29? Find sponsor, declare him how bad it is? Olga On Thu, Oct 10, 2013 at 1:21 AM, Oliver Kiddle wrote: > Phi Debian wrote: >> On Wed, Oct 9, 2013 at 4:11 PM, Oliver Kiddle wrote: >> >> > >> > Debian does have ksh93u. >> >> Ambiguous > > Clearly

Bug#720441: Got a fix, how to submit patch.

2013-10-09 Thread Oliver Kiddle
Phi Debian wrote: > On Wed, Oct 9, 2013 at 4:11 PM, Oliver Kiddle wrote: > > > > > Debian does have ksh93u. > > Ambiguous Clearly we've got ambiguity in Debian versions of ksh too: wheezy does have 2012-02-29, testing/unstable have 2012-08-01. 2012-08-01 will never go into wheezy, the best we

Bug#720441: Got a fix, how to submit patch.

2013-10-09 Thread Phi Debian
On Wed, Oct 9, 2013 at 4:11 PM, Oliver Kiddle wrote: > > Debian does have ksh93u. Ambiguous > Latest version at the following URL is what > Debian has: > http://www2.research.att.com/~gsf/download/ This link shows 3 ksh93u versions > > I think there is a more recent version that is declared

Bug#720441: Got a fix, how to submit patch.

2013-10-09 Thread ольга крыжановская
ksh93u+ is the last stable version, ksh93v- is the alpha currently in development. I am working on integrating ksh93v-, with major changes, regarding to making it much more stable on Debian, and to enable the POSIX builtins, which are mostly missing in Debian (compared to, like Suse). Olga On Wed

Bug#720441: Got a fix, how to submit patch.

2013-10-09 Thread Oliver Kiddle
Phi Debian wrote: > It appears after some back and forth mail with attresearch (code > owner) that the source code used by debian (and ubuntu) are both out > of date, they both have this code dump or corruptin bug that was fixed > at ksh93u (dixit David Korn). Debian does have ksh93u. Latest versi

Bug#720441: Got a fix, how to submit patch.

2013-10-08 Thread Phi Debian
Hi All, It appears after some back and forth mail with attresearch (code owner) that the source code used by debian (and ubuntu) are both out of date, they both have this code dump or corruptin bug that was fixed at ksh93u (dixit David Korn). I dunno what ksh93u debian grabed but for sure it is b

Bug#720441: Got a fix, how to submit patch.

2013-10-07 Thread Cedric Blancher
On 7 October 2013 09:38, Phi Debian wrote: > Hi All, > > This patch fix the ksh core dump or random memory corruption seen when > typing ## (or more generally #) > > The original code was missing a var initialisation, later teh code > firex a nullderef still missing the var initialisation. > > Thi

Bug#720441: Got a fix, how to submit patch.

2013-10-07 Thread Phi Debian
Hi All, This patch fix the ksh core dump or random memory corruption seen when typing ## (or more generally #) The original code was missing a var initialisation, later teh code firex a nullderef still missing the var initialisation. This fix do both the var init, and the null deref avoidance.

Bug#720441: Got a fix, how to submit patch.

2013-10-06 Thread Oliver Kiddle
On 4 Oct, you wrote: > How should I proceed for a patch submit, I did provide it to att > owner, so I guess future release will have the fix, but for debian > should I do something, does debian has its own set of 'fixes' (I am > ignorant here) You an include a small patch in an e-mail to this bug

Bug#720441: Got a fix, how to submit patch.

2013-10-03 Thread Phi Debian
Hi All, Please ignore my prev mail with my professional email, my spam killer reject external mail. How should I proceed for a patch submit, I did provide it to att owner, so I guess future release will have the fix, but for debian should I do something, does debian has its own set of 'fixes' (I

Bug#720441: Got a fix

2013-10-03 Thread phi
Hi All, Hi find a fix for this, How should I proceed to submit it ? Cheers, Phi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org