On 08/08/2024 8:40 PM, Bastien Roucariès wrote:
Le mercredi 7 août 2024, 17:05:01 UTC Nicolas Peugnet a écrit :
Hi all,
Pierre-Elliott Bécue <p...@debian.org> on Wed, 27 Sep 2023 14:19:20:
Otto Kekäläinen <o...@debian.org> wrote on 27/09/2023 at 06:35:07+0200:
Hi!
Thanks for the context - so there is no need technical incompatibility
at play, but mostly a matter of having resources and time to do it.
..
Regarding the 301 redirection I'll see with the interested parties (DSA
and Lintian maintainers) if this option is fine with everyone.
I could easily write Ansible code to maintain a simple Nginx server,
with 302 redirects https://lintian.debian.org/tags/(.*)/?$ ->
https://udd.debian.org/lintian-tag.cgi?tag=$1, use same Ansible style
as salsa.debian.org is maintained on
(https://salsa.debian.org/salsa/salsa-ansible), and also donate a tiny
virtual machine for Debian project if needed. Is there some special
bureaucracy on top of that work to do to be able to contribute with
this?
Don't worry, the server still exists, it's just down, and reputting the
DNS takes little to no time.
Regarding apache config, I'm fine with doing it. It's a matter of
checking with everyone that we want to do that as the plan was nuking
the server from orbit.
Providing debian.org infrastructure requires to be a member of the
Debian System Administrators (DSA) team, which in turn requires to be a
Debian Developer, so, sadly, you can't really help on that part.
That being said, thank you for offering your time.
I sent the following email in reply to Bug#1042428 but I didn't see it
was archived, so I repost it here:
As I just recently started making Debian packages, I clicked multiple times on links
to <https://lintian.debian.org> that led me to a dead end, for instance from
mentors.debian.org, or on the hyperlinks that lintian itself produce in the terminal
output. It was not a very pleasant experience, especially for a newbie.
In my opinion, redirecting lintian.debian.org to the UDD links posted above is
not a good option, because as I understand it, they only were intended to show
the extended explanation for each tag. Having the list of all the affected
packages in this page it not helpful, and it makes the pages very slow to load
(and to produce).
So instead I thought that it would be quite easy to generate a static website
that would be very fast to generate once, and then to serve and load. So I made
my own implementation that generates a website that could be directly uploaded
to lintian.debian.org, as it follows strictly the previous URL structure (I
also added the manual of lintian as I also stumbled on links to it).
For now I hosted it on my server so you can see the result there:
<https://static.club1.fr/nicolas/lintian/>
For instance the link above translates to:
<https://static.club1.fr/nicolas/lintian/tags/superfluous-file-pattern.html>
And here are the sources:
<https://github.com/n-peugnet/lintian-ssg>
It is not meant to replace the corresponding UDD link, in fact I added a link
to it in the page of each tag, to see all the affected packages. But I think it
is better to first arrive on a very fast to load page that simply explains the
tag, and then be able to follow a link to see the list of affected packages.
What will be wonderfull is to retrieve number of package affected and do a svg
graph along time... Using a static script
nicolas did you contact the the infrasture team ?
Not yet, I wanted to request feedback on my proposal beforehand.
I just added debian-ad...@lists.debian.org in CC, I hope it was the
right thing to do.
Please telle me what you think about it and if you think it can be uploaded to
lintian.debian.org?
In the meantime I added some features and hosted it on its own domain to
make the custom 404 page work correctly: <https://lintian.club1.fr/>.
So, do you think it could be used to make the lintian.debian.org website
back up?
P.S. I'm not subscribed to this list, so please CC me.
Regards
--
Nicolas Peugnet
