Your message dated Sun, 9 Apr 2017 01:57:56 +0200 with message-id <20170408235756.rfvifcughvrk6qg6@angband.pl> and subject line Re: Bug#859776: sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free Vim-like text editor has caused the Debian Bug report #859776, regarding sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free Vim-like text editor to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 859776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859776 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free Vim-like text editor
- From: Paride Legovini <pl@ninthfloor.org>
- Date: Fri, 07 Apr 2017 12:54:22 +0200
- Message-id: <[🔎] 149156246286.23082.17911198887991446346.reportbug@mandragola>
Package: sponsorship-requests Severity: wishlist Dear mentors, I'm looking for a sponsor for "vis": * Package name : vis Version : 0.3 Upstream Author : Marc André Tanner <mat@brain-dump.org> * URL : https://github.com/martanne/vis * License : ISC Section : editors It's my main editor, so I'm willing to keep the package well maintained and up to date. To access further information about this package please visit: https://mentors.debian.net/package/vis Thank you, Paride Legovini
--- End Message ---
--- Begin Message ---
- To: 859776-done@bugs.debian.org
- Subject: Re: Bug#859776: sponsorship-requests: vis/0.3 [ITP] -- A a modern and legacy free Vim-like text editor
- From: Adam Borowski <kilobyte@angband.pl>
- Date: Sun, 9 Apr 2017 01:57:56 +0200
- Message-id: <20170408235756.rfvifcughvrk6qg6@angband.pl>
- In-reply-to: <[🔎] a0999718-efaa-e1e5-b480-c570ec76b24d@ninthfloor.org>
- References: <[🔎] 149156246286.23082.17911198887991446346.reportbug@mandragola> <[🔎] 20170407133938.yisirklqlokqtrmg@angband.pl> <[🔎] 036e75a8-9d1f-df73-22d7-d6d452731cb0@ninthfloor.org> <[🔎] 20170407175404.zbrqob7hnft24ku2@angband.pl> <[🔎] a0999718-efaa-e1e5-b480-c570ec76b24d@ninthfloor.org>
On Sat, Apr 08, 2017 at 12:56:40PM +0200, Paride Legovini wrote: > On 2017-04-07 19:54, Adam Borowski wrote: > > On Fri, Apr 07, 2017 at 05:52:21PM +0200, Paride Legovini wrote: > >> On 2017-04-07 15:39, Adam Borowski wrote: > >>> On Fri, Apr 07, 2017 at 12:54:22PM +0200, Paride Legovini wrote: > >>>> * Package name : vis > >>>> Version : 0.3 > > > > Seems to be fine, except for two error messages I get: > > > > /usr/share/vis/themes/default-256.lua:23: attempt to index a nil value (local 'lexers') > > WARNING: could not find lpeg module > > The package now Recommends: lua-lpeg, that is the dependency you are > missing. The upstream README.md lists it as an "optional runtime > dependency", so I think Recommends: is appropriate. I'd still prefer a nicer message, or no error at all -- but that's not a blocker for the initial version. Let's get a working version in, there'll be plenty of time to improve it later. > I also changed the priorities for the alternatives for 'editor' and 'vi' > (see debian/postinst). The rationale is that it's OK to prefer vis to > very basic flavors of vim, lettings the ones with more features win. I > also didn't want to override nano, as it is the editor suggested to less > experienced users. Seems reasonable to me, but I'd like to have some > feedback. I'm not a vi user, but from the gist of things I see that vis tries to be a good _editor_ but not necessarily a good _vi_. That sounds like you'd want a pretty low priority for "vi" but a decent one for "editor". But I haven't researched the priorities either, someone else might have better feedback here. Uploaded; I've done most testing on armhf as I suppose you did amd64 yourself; armhf is also the architecture I used for the binary upload so it will have no build log. ᛗᛖᛟᚹ! -- ⢀⣴⠾⠻⢶⣦⠀ Meow! ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second ⠈⠳⣄⠀⠀⠀⠀ preimage for double rot13!
--- End Message ---