From: jean-christophe manciot <actionmystique@gmail.com>
To: Christian Hesse <list@eworm.de>
Cc: cgit@lists.zx2c4.com
Subject: Re: Incompatibilities with python3-pygments 2.6.1?
Date: Wed, 1 Jul 2020 17:26:58 +0200 [thread overview]
Message-ID: <CAKcFC3YXS=KYbmB3KzLqky32zDJK91FEb0sMPzoB-gRAr1khdw@mail.gmail.com> (raw)
In-Reply-To: <20200701161254.4d3d2eb1@leda>
Nothing related to this issue appears in uwsgi/nginx logs nor any
other log below /var/log.
Is there a way to log cgit trace?
On Wed, Jul 1, 2020 at 4:12 PM Christian Hesse <list@eworm.de> wrote:
>
> jean-christophe manciot <actionmystique@gmail.com> on Wed, 2020/07/01 15:51:
> > 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.
> >
> > Cheers.
>
> I use cgit with python-pygments 2.6.1-2 on Arch Linux. Everything works as
> expected, so looks like this is not a general issue with python-pygments.
>
> Any error messages in the logs?
> --
> main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
> "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
> putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
--
Jean-Christophe
next prev parent reply other threads:[~2020-07-01 15:27 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 [this message]
2020-07-01 15:35 ` Roy Marples
2020-07-01 15:41 ` jean-christophe manciot
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='CAKcFC3YXS=KYbmB3KzLqky32zDJK91FEb0sMPzoB-gRAr1khdw@mail.gmail.com' \
--to=actionmystique@gmail.com \
--cc=cgit@lists.zx2c4.com \
--cc=list@eworm.de \
/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).