Package: gitit / 0.15.1.0+dfsg-2

Metadata

Package Version Patches format
gitit 0.15.1.0+dfsg-2 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
clean cabal file.patch | (download)

gitit.cabal | 11 2 + 9 - 0 !
1 file changed, 2 insertions(+), 9 deletions(-)

 remove from .cabal data files, missing in tarball
jquery.patch | (download)

data/templates/expire.st | 2 1 + 1 - 0 !
data/templates/page.st | 1 1 + 0 - 0 !
src/Network/Gitit/Layout.hs | 2 1 + 1 - 0 !
3 files changed, 3 insertions(+), 2 deletions(-)

 use libjs-jquery instead of embedded code
 Patch gitit to use the javascript linked from the libjs-jquery package,
 instead of the embedded one.
newer hoauth2 | (download)

gitit.cabal | 2 1 + 1 - 0 !
src/Network/Gitit/Authentication/Github.hs | 22 11 + 11 - 0 !
src/Network/Gitit/Config.hs | 16 6 + 10 - 0 !
3 files changed, 18 insertions(+), 22 deletions(-)

 [patch] adjust for hoauth2 >= 2.3.0

hoauth2 is used by Stackage Nightly 2.3.0 and will thus be included in
Stackage LTS 19 when it comes out. Another motivation for this being
able to build with aeson 2.0 which is possible since hoauth2 2.1.

I've elected not to try to support a wider range (say >= 2.0 && < 2.4 or
even >= 1.3.0 && < 2.4) because *every version* released between 2.0 and
2.3 contains a breaking change that affects gitit, the CPP would turn
out to be quite the mess. Since there haven't been any functional
changes since the last release on master, people that can't upgrade yet
can safely skip a (hypothetical) immediate release.

If wanted, support for hoauth2 >= 2.1 && < 2.4 could possibly be
interesting, only supporting aeson >= 2.0 is probably a safe bet for
future releases.

newer pandoc | (download)

gitit.cabal | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 [patch] allow building with pandoc 2.17