Bug#720441: Got a fix
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
Bug#302033: UP 500% in 2 days
http://i14.tinypic.com/48vvjib.png Same as for i -= n. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#92571: HUGE report
http://imagecloset.com/uimages/cqs1176820583j.png Il ne faut pas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#720441: reported on ubuntu as well.
Hi As I bumped into this on ubuntu as well, and as bod suggested, I did try to report to lauchped.net too. There I discover it is already 'known' since december 2012, meaning this have little chance to be fixed one day. See https://bugs.launchpad.net/ubuntu/+source/ksh/+bug/1086873 So for your information, I worked around this by simply downloading the source package and rebuild, with no fix, the simple rebuild is enough to cure, then indeed you place you new ksh into the install dir. Cheers, Phi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720441: Got a fix, how to submit patch.
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 am ignorant here) Cheers, Phi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720441: Got a fix, how to submit patch.
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. ksh-debdiff Description: Binary data
Bug#720441: Got a fix, how to submit patch.
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 buged. So what is the process to get a more recent source code on debian (at least wheezy) and then an updated binary package. Where should we wave ? Thanx in advance, Cheers, Phi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720441: Got a fix, how to submit patch.
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 a beta or alpha. > > This said, I wouldn't be surprised if the download link is out-of-date > given that the maintainers are leaving AT&T. > > Oliver No the link are accurate, and as Olga said, what is beta is ksh98v The story goes like this Version JM 93u+ 2012-02-29 Is bugged (core dump on ##) Version AJM 93u+ 2012-06-28 Is correct (regarding ##) Version AJM 93u+ 2012-08-01 is correct *regarding ##) Debian binary ksh package for wheezy gets Version JM 93u+ 2012-02-29 and match the source code we got with apt-get source ksh Bottom line, you rigth, debian has the ksh93u+ but the only wrong one. Suse got a ksh93+ as well but a good one. I think wheezy deserve a clean ksh93, and should be patched, without waitng for next ksh93v Hope this helps Cheers, Phi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720441: Got a fix, how to submit patch.
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 to 6 (mine called fix-coredump-memcorrupt-pond-1st-char.patch ) CY51$ pwd /home/phi/ksh-93u+/debian/patches CY51$ ls cleanup-man-title.patch no-rpath.patch fix-cd-builtin.patch series fix-coredump-memcorrupt-pond-1st-char.patch shell-options.patch handle-removed-working-dir.patch So wheezy as proven it could handle patches, let's add one more. This is in the case it is easier to patch vs enter a band new version. Cheers, Phi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#76671: Lindsay sucking vids
Enlarge your member for maximum satisfaction http://www.Crovinci.com/ Make her unbelievably wet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
