Bug#764401: Bug#783978: Bug#764401: Are you planning to take over mksh in Debian?
On Fri, May 1, 2015 at 6:18 PM, Thorsten Glaser wrote: > Kenneth Pronovici dixit: >>I'm not trying to be snarky here, but I'm a little lost. This package >>is orphaned. If you're no longer the package maintainer, why should >>it even matter to you whether upstream issues are tracked as Debian >>bugs? > > Because > > ① I’m upstream, > > ② I’m maintaining this package in Debian, and, most importantly, > > ③ feature requests aren’t bugs, period. > >>Besides that, this is arguably a functional regression vs. older >>versions of pdksh in Debian, which mksh now provides. I think it's >>useful to have the change in behavior noted, even if it is only a >>wishlist. > > That’s arguably a good point. > > One of mksh’s biggest strengths is that it behaves consistently > across all platforms, though. DO NOT break that. Ok, this is clearly becoming way more of a big deal than I expected it to be. If you're maintaining the package in Debian (even though it's orphaned, which makes no sense to me) then feel free to just close #783978, the wishlist request. I'd prefer to have that bug stay open, but now we've moved into the realm of differing philosophies regarding bug reports, and you and I clearly disagree on this subject. Do whatever works best for you. As far as the mksh behavior is concerned, I never suggested (even in the original stackexchange discussion), that I wanted to make mksh behave differently in Debian than on other platforms. I was simply offering to help get the changes into Debian, based on the fact that the package appeared to be without a maintainer. If the package is being maintained, then you don't need my help with that. End of story. I hereby withdraw my interest in #764401, the ITA bug report. If you can make the requested improvement upstream, that's great, and I would really welcome the change. If not, I'll just find some other shell to use. Thanks, KEN -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAL5KwF9yymN2X+NSV=g6aB3f2_B56kV3+Ocg=5nyt0pygoz...@mail.gmail.com
Bug#764401: Are you planning to take over mksh in Debian?
Kenneth Pronovici dixit: >I filed the bug so nothing would get lost while the package is >orphaned, which seems like a reasonable thing to do. The next That may seem reasonable… >maintainer might very well have a different policy for Debian bugs >than you did. I would if it were my package. … and even if this were reasonable… it’s still not a reasonable thing as I indicated interest upstream for this already. I know you’re well-meaning and all, but you’re interfering with things that currently work. (That, written out in the English language, sounds harsher than I mean it, please take it in that spirit.) bye, //mirabilos -- “ah that reminds me, thanks for the stellar entertainment that you and certain other people provide on the Debian mailing lists │ sole reason I subscribed to them (I'm not using Debian anywhere) is the entertainment factor │ Debian does not strike me as a place for good humour, much less German admin-style humour” -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pine.bsm.4.64l.1505012320500.6...@herc.mirbsd.org
Bug#764401: Bug#783978: Bug#764401: Are you planning to take over mksh in Debian?
Kenneth Pronovici dixit: >I'm not trying to be snarky here, but I'm a little lost. This package >is orphaned. If you're no longer the package maintainer, why should >it even matter to you whether upstream issues are tracked as Debian >bugs? Because ① I’m upstream, ② I’m maintaining this package in Debian, and, most importantly, ③ feature requests aren’t bugs, period. >Besides that, this is arguably a functional regression vs. older >versions of pdksh in Debian, which mksh now provides. I think it's >useful to have the change in behavior noted, even if it is only a >wishlist. That’s arguably a good point. One of mksh’s biggest strengths is that it behaves consistently across all platforms, though. DO NOT break that. Goodnight, //mirabilos -- exceptions: a truly awful implementation of quite a nice idea. just about the worst way you could do something like that, afaic. it's like anti-design. that too… may I quote you on that? sure, tho i doubt anyone will listen ;) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pine.bsm.4.64l.1505012316540.6...@herc.mirbsd.org
Bug#764401: Are you planning to take over mksh in Debian?
On Fri, May 1, 2015 at 5:36 PM, Thorsten Glaser wrote: > Kenneth Pronovici dixit: >>I'll file a Debian bug to document the improvements I asked for, just > Please DO NOT file Debian bugs for upstream issues in mksh, > only for packaging issues. > > This has been at the top of README.Debian for ages. Thorsten, I'm not trying to be snarky here, but I'm a little lost. This package is orphaned. If you're no longer the package maintainer, why should it even matter to you whether upstream issues are tracked as Debian bugs? I filed the bug so nothing would get lost while the package is orphaned, which seems like a reasonable thing to do. The next maintainer might very well have a different policy for Debian bugs than you did. I would if it were my package. Besides that, this is arguably a functional regression vs. older versions of pdksh in Debian, which mksh now provides. I think it's useful to have the change in behavior noted, even if it is only a wishlist. KEN -- Kenneth J. Pronovici -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAL5KwF-5JP4CC=ar3_yys8t2omqkv04fzawkflyjhdxoeyq...@mail.gmail.com
Bug#764401: Are you planning to take over mksh in Debian?
Kenneth Pronovici dixit: >I'll file a Debian bug to document the improvements I asked for, just Please DO NOT file Debian bugs for upstream issues in mksh, only for packaging issues. This has been at the top of README.Debian for ages. Debian bugs requesting functionality changes are likely to get closed quicky, as they are no bugs. Feature requests upstream (via #!/bin/mksh on Freenode IRC, via miros-mksh@, or, if it must be, via Launchpad) are OK. Thanks. bye, //mirabilos -- "Using Lynx is like wearing a really good pair of shades: cuts out the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL." -- Henry Nelson, March 1999 -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pine.bsm.4.64l.1505012234500.6...@herc.mirbsd.org
Bug#764401: Are you planning to take over mksh in Debian?
On Fri, May 1, 2015 at 1:03 PM, Dominik George wrote: >> Are you still planning to take over mksh in Debian? If not, I would >> like to take ownership of #76401 and maintain the package myself. I >> actively use ksh on Debian, and I don't want to see the packages go >> unmaintained. Also, I have been talking with upstream about some >> improvements, and I want to be in a position where I can apply patches. > > I am still going to take over mksh in Debian, yes. > > Currently, the package is still maintained by Thorsten Glaser, who is a > next door neighbour at my dayjob and keeps mksh updated on behalf of > Debian QA. > > Please send your improvements to me, nonetheless. Ok. My main goal is to make sure the mksh package is being maintained. If it is, then there's no need for me to take it over. I'll file a Debian bug to document the improvements I asked for, just so something is being tracked. Whenever the new code is available, I'll assume you can integrate it into Debian. If you need my help integrating or testing changes, or if you eventually change your mind about taking over the package, please let me know. Thanks, KEN -- Kenneth J. Pronovici -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cal5kwf_c-bcrbufprexv-0c2txhohscc6imlv974fjpbq3l...@mail.gmail.com
Bug#764401: Are you planning to take over mksh in Debian?
Hi, > Are you still planning to take over mksh in Debian? If not, I would > like to take ownership of #76401 and maintain the package myself. I > actively use ksh on Debian, and I don't want to see the packages go > unmaintained. Also, I have been talking with upstream about some > improvements, and I want to be in a position where I can apply patches. I am still going to take over mksh in Debian, yes. Currently, the package is still maintained by Thorsten Glaser, who is a next door neighbour at my dayjob and keeps mksh updated on behalf of Debian QA. Please send your improvements to me, nonetheless. Cheers, Nik signature.asc Description: OpenPGP digital signature
Bug#764401: Are you planning to take over mksh in Debian?
Hi Dominik, Are you still planning to take over mksh in Debian? If not, I would like to take ownership of #76401 and maintain the package myself. I actively use ksh on Debian, and I don't want to see the packages go unmaintained. Also, I have been talking with upstream about some improvements, and I want to be in a position where I can apply patches. Thanks! KEN -- Kenneth J. Pronovici