List for cgit developers and users
 help / color / mirror / Atom feed
From: jean-christophe manciot <actionmystique@gmail.com>
To: Roy Marples <roy@marples.name>
Cc: cgit@lists.zx2c4.com
Subject: Re: Incompatibilities with python3-pygments 2.6.1?
Date: Wed, 1 Jul 2020 17:41:31 +0200	[thread overview]
Message-ID: <CAKcFC3bprWuYU8OMY899+6wrJVnxt+5ZQLzMYdifTTazkSub_A@mail.gmail.com> (raw)
In-Reply-To: <d6f9eaa1-4620-842f-bbc4-fbf4cba8e950@marples.name>

I tried to restart uwsgi then nginx systemd services after
python3-pygments upgrade, but the symptom persists.

On Wed, Jul 1, 2020 at 5:35 PM Roy Marples <roy@marples.name> wrote:
>
> On 01/07/2020 14:51, jean-christophe manciot wrote:
> > Hello everyone,
> >
> > I've built python3-pygments from sources
> > (https://github.com/pygments/pygments) using the latest stable 2.6.1
> > tag.
> > Using it with cgit v1.2.3 and git 2.25.1 leads to blank 'about' pages
> > whereas everything works fine with 2.3.1+dfsg-1ubuntu2 on Ubuntu
> > focal.
> >
> > Any suggestions?
> >
> > The deb package is available on Ubuntu focal at
> > https://git.sdxlive.com/PPA/tree/Ubuntu/pool/stable/p/python3-pygments.
>
> I use the highlight package instead, running cgit under uwsgi fronted by nginx.
> When I restart the web server, the highlighted code is blank until I restart the
> uwsgi service. I don't know why this is as there is no reported error, but the
> symtom appears to mirror your own so I thought it was worth mentioning.
>
> Roy



-- 
Jean-Christophe

  reply	other threads:[~2020-07-01 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01 13:51 jean-christophe manciot
2020-07-01 14:12 ` Christian Hesse
2020-07-01 15:26   ` jean-christophe manciot
2020-07-01 15:35 ` Roy Marples
2020-07-01 15:41   ` jean-christophe manciot [this message]
2020-07-03 15:36     ` jean-christophe manciot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKcFC3bprWuYU8OMY899+6wrJVnxt+5ZQLzMYdifTTazkSub_A@mail.gmail.com \
    --to=actionmystique@gmail.com \
    --cc=cgit@lists.zx2c4.com \
    --cc=roy@marples.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).