The upgrade of TracSVN is completed
We're now running Trac-1.6
Tests welcome:
https://trac.osgeo.org
https://git.osgeo.org
https://svn.osgeo.org
--strk;
On Wed, Sep 4, 2024 at 1:58 PM Sandro Santilli <strk@kbt.io> wrote:
The upgrade of TracSVN is completed
We're now running Trac-1.6Tests welcome:
Apparently "always" I get
502 Bad Gateway
________________________________
nginx/1.18.0 (Ubuntu)
when opening a new ticket while saving it.
It now happened ~2 min before:
date -u
Sun Sep 8 11:08:49 AM UTC 2024
Maybe the log file shows what's wrong?
Markus
On Sun, Sep 08, 2024 at 01:09:33PM +0200, Markus Neteler wrote:
On Wed, Sep 4, 2024 at 1:58 PM Sandro Santilli <strk@kbt.io> wrote:
> The upgrade of TracSVN is completed
> We're now running Trac-1.6
>
> Tests welcome:
>
> https://trac.osgeo.orgApparently "always" I get
502 Bad Gateway
________________________________
nginx/1.18.0 (Ubuntu)when opening a new ticket while saving it.
It now happened ~2 min before:
date -u
Sun Sep 8 11:08:49 AM UTC 2024Maybe the log file shows what's wrong?
I've filed a ticket:
https://trac.osgeo.org/osgeo/ticket/3271
If you are able to reproduce again could you give exact URL ?
In the nginx logs the only grass-related error lines
are at 2024/09/08 10:10:15 and 2024/09/08 11:47:02
--strk;
On Sun, Sep 8, 2024 at 4:45 PM Sandro Santilli <strk@kbt.io> wrote:
On Sun, Sep 08, 2024 at 01:09:33PM +0200, Markus Neteler wrote:
> On Wed, Sep 4, 2024 at 1:58 PM Sandro Santilli <strk@kbt.io> wrote:
> > The upgrade of TracSVN is completed
> > We're now running Trac-1.6
> >
> > Tests welcome:
> >
> > https://trac.osgeo.org
>
> Apparently "always" I get
>
> 502 Bad GatewayIf you are able to reproduce again could you give exact URL ?
In the nginx logs the only grass-related error lines
are at 2024/09/08 10:10:15 and 2024/09/08 11:47:02
I was actually opening a SAC ticket.
I think I saw "https://trac.osgeo.org/osgeo/newticket" as URL when the
502 error occurred.
Markus
Hi,
Since the update I no longer receive emails on my Trac tickets. Like this
following the answers is close to impossible.
Would you mind to check this?
Thanks
Markus
Sandro Santilli <strk@kbt.io> schrieb am Mi., 4. Sep. 2024, 13:58:
The upgrade of TracSVN is completed
We're now running Trac-1.6Tests welcome:
https://trac.osgeo.org
https://git.osgeo.org
https://svn.osgeo.org--strk;
Hi,
Isn't maintaining a OSGeo Trac/svn/gitea/whatever infrastructure a lost battle, waste of energy and volunteer time, strategically dubious / sending a inaudible message nowadays? And when I say nowadays, I really mean since 10 years at least...
There's no way cool kids will want to contribute to projects using that. Plus the fact you need to go over the mantra barrier to create your account. It looks really like if we actively wanted to discourage contributions, do we?
Which (still active) OSGeo projects are still using that as their canonical infa: geos (gitea for git repo & tickets ?), PostGIS (Trac for tickets?), ... ? Maybe consider a migration plan to be able to completely shut down services at some later point?
At least if OSGeo really wanted to host a software forge, it could host a gitlab instance, so the 5% of people who don't use github have at least some familiarity with it, but I would even question that (with Trac/SVN/gitea, we are targeting the 0.1% outliers). Everybody have sold their soul to github and are happily providing food to LLMs. Let's just accept it, bend to the powers governing the world, and move on.
Even
~~~~
PS1: interestingly, gitea canonical repository is ... hosted on github (GitHub - go-gitea/gitea: Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD). That tells a lot, doesn't it?
PS2: Little tour of other organizations:
- Eclipse Foundation: both github and gitlab (Explore projects · GitLab): Moving Eclipse projects to GitHub and GitLab | Eclipse Foundation Staff Blogs (this post actually makes the same point as me about what the new gen expects)
- Apache Foundation: github apparently, at least Apache Arrow uses it both for tickets & code
- Freedesktop.org: gitlab
- Gnome: gitlab
- KDE; gitlab
Sure you may find counter-examples to that trend, but it is definitely there.
--
http://www.spatialys.com
My software is free, but my time generally not.
I think this is related to the issue we are having with trac webhooks giving some sort of trac db upgrade error which we are still investigating.
We are having similar issue with trac tickets getting auto commented on source code pushes.
From: Projects <projects-bounces@lists.osgeo.org> On Behalf Of Markus Neteler via Projects
Sent: Sunday, September 22, 2024 4:48 PM
To: OSGeo-projects <projects@lists.osgeo.org>; OSGeo-SAC <sac@lists.osgeo.org>
Subject: Re: [Projects] Trac/SVN/Gitea upgrade completed, tests welcome
Hi,
Since the update I no longer receive emails on my Trac tickets. Like this following the answers is close to impossible.
Would you mind to check this?
Thanks
Markus
Sandro Santilli <strk@kbt.io <mailto:strk@kbt.io> > schrieb am Mi., 4. Sep. 2024, 13:58:
The upgrade of TracSVN is completed
We're now running Trac-1.6
Tests welcome:
https://trac.osgeo.org
https://git.osgeo.org
https://svn.osgeo.org
--strk;
Isn't maintaining a OSGeo Trac/svn/gitea/whatever infrastructure a lost battle,
waste of energy and volunteer time, strategically dubious / sending a inaudible
message nowadays? And when I say nowadays, I really mean since 10 years at
least...
We don't just manage osgeo projects here, but also all our servers and some other things.
So no I wouldn't say it's a lost cause, cause a lot of the stuff we manage in gitea and trac, I wouldn't want on github.
Sure we have private repos on github for now.
There's no way cool kids will want to contribute to projects using that.
Plus the fact you need to go over the mantra barrier to create your account. It
looks really like if we actively wanted to discourage contributions, do we?
PostGIS has mirrors on github and gitlab so I don't think we are missing much on cool kid traffic.
Which (still active) OSGeo projects are still using that as their canonical infa:
geos (gitea for git repo & tickets ?), PostGIS (Trac for tickets?), ... ? Maybe
consider a migration plan to be able to completely shut down services at some
later point?
Hello - GEOS is completely on github now, you guys won that battle, or have you forgotten?
I still don't care to entertain tickets on github. Even despite the mantra thing, I still feel we have way too many tickets on PostGIS 
I do wonder though if we should move out of trac as that does seem to cause us the most headache when we upgrade.
At least if OSGeo really wanted to host a software forge, it could host a gitlab
instance, so the 5% of people who don't use github have at least some
familiarity with it, but I would even question that (with Trac/SVN/gitea, we are
targeting the 0.1% outliers).
Gitlab takes way more effort to maintain than gitea. Gitea is a simple executable and a PostgreSQL backend db. Nothing simpler than that
and it does the job fine and well github (an open source utopia that isn't open source, sounds like an oxymoron to me).
Github is really just free CI horsepower and perhaps a place to get random patches, and that's great we use it for those things.
Everybody have sold their soul to github and are
happily providing food to LLMs. Let's just accept it, bend to the powers
governing the world, and move on.
If I was interested in being an EVERYBODY, I would have stuck with SQL Server, gone the ESRI Arc whatever route like everyone else around me
and never stepped on OSGeo sand.
You may thing this is a lost cause, but I'd rather battle a lost cause, than sell my soul like everybody.
Thanks,
Regina
Even Rouault <even.rouault@spatialys.com> writes:
Everybody
have sold their soul to github and are happily providing food to
LLMs. Let's just accept it, bend to the powers governing the world,
and move on.
Not everybody, and we're not happy. github has been part of what's
wrong with the world for a long time and they are getting worse.
Delivering them content and people is not IMHO in the public interest.
I do agree about trac; I used to run it 2007-2015ish.
As for the real cool kids, github isn't cool and they are using forgejo,
either self-hosted or at codeberg. So I see reasonable options:
self-host gitlab (I think this is going to fade as reaosnable over
time, so I don't think it's a good idea)
self-host forgejo (forgejo is where the part of the community that
cares about the problematic behavior of github is headed, as I see it)
put official repos on codeberg, and donate some fraction of the
previous costs of maintenance
On Sun, Sep 22, 2024 at 10:48:06PM +0200, Markus Neteler wrote:
Since the update I no longer receive emails on my Trac tickets. Like this
following the answers is close to impossible.
Would you mind to check this?
It was postfix being unable to resolve hostnames.
It's now fixed and mail held in queue was delivered.
Thanks for reporting the issue.
--strk;