The latest upstream version has been package and placed at: https://mentors.debian.net/package/vizigrep
This version fixes the dependency error. I'm working on updating to Python-3 separately and will provide that update sometime in the future. For now, let's see if we can get v1.4 into Debian to avoid Vizigrep getting dropped. I need a sponsor. I've e-mailed the original sponsor (Gianfranco Costamagna). Hopefully he is able to take a look today or tomorrow. On Wed, Aug 1, 2018 at 1:03 PM Raúl Benencia <r...@kalgan.cc> wrote: > Dear Jason, > > On Wed, Aug 01, 2018 at 12:07:45PM -0400, Jason J. Herne wrote: > > I'm the author of Vizigrep. It needs to be converted to Python-3. I'll > work > > on the conversion but I need a little info on Debian's process. > > Thanks for taking care of the package! > > > 1. Is there some sort of deadline to ensure Vizigrep does not get > dropped? > > The package will get dropped from testing in two weeks, that's Aug 14th. > You can get more information here: > > https://tracker.debian.org/pkg/vizigrep > > > 2. What is the process for submitting my changes once I am done? I used > to > > know this at one time... Is there a wiki page I should follow? > > So, there are many ways in which you can package your software. > Personally, I like to use git for keeping track of all the packaging > code. Check the wiki[0] page for getting started if you want to give > this method a try. I also encourage you to take a look to the New > Maintainer's guide[1]. > > [0] https://wiki.debian.org/PackagingWithGit > [1] https://www.debian.org/doc/manuals/maint-guide/ > > Once you have your package ready, you have to find a sponsor for it. > For this, I encourage you to contact the person that sponsored the package > for the first time. > > Cheers, > Rul > -- - Jason J. Herne (hern...@gmail.com)
