Bug#918111: marked as done (ITP: luakit -- A webkit2-based web browser extensible by Lua)
Your message dated Fri, 18 Jan 2019 17:57:57 +0100
with message-id <20190118165757.54uxss4hnr274m73@victor>
and subject line Re: ITP: luakit -- A webkit2-based web browser extensible by Lua
has caused the Debian Bug report #918111,
regarding ITP: luakit -- A webkit2-based web browser extensible by Lua
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.)
--
918111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918111
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Markus Demleitner <msdemlei@fsfe.org>
* Package name : luakit
Version : 2017-08-10
Upstream Author : Aidan Holm <aidanholm@gmail.com
* URL : https://luakit.github.io
* License : GPLv3
Programming Lang: C, Lua
Description : A webkit2-based web browser extensible by Lua
Luakit has been part of Debian up to and including stretch. It was removed
from sid recently because the version in Debian depended on Webkit1.
Upstream, however, had ported the software to Webkit2 by then.
I would like to bring back the modernised luakit to Debian.
The description of the old package by and large still pertains (although
I give you it would be spiced up a bit): Luakit is a highly configurable
browser framework based on WebKit2GTK. It is very fast and extensible
by Lua. It is primarily targeted at power users, developers and any
people with too much time on their hands who want to have fine-grained
control over their web browser's behaviour and interface.
--- End Message ---
--- Begin Message ---
A luakit package has accepted into unstable on 2019-01-17.
--- End Message ---
Reply to: