[Bug 281427] devel/mm, devel/ossp-al, devel/ossp-cfg, devel/ossp-ex, devel/ossp-l2, devel/ossp-val, devel/ossp-var, devel/ossp-xds, devel/shtool, devel/str, lang/p5-ePerl, mail/lmtp2nntp, misc/iselect, misc/ossp-uuid, net/ossp-sa: new upstream, new mirror site

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281427

--- Comment #2 from наб <nabijaczleweli@nabijaczleweli.xyz> ---
> Do any of the current maintainers have access to the new web sites? 
I suppose they can use sr.ht like anyone else. They can't log into my computer
though. I feel like this is fair, and mirrors what we can do with their sites.

> Or are they even aware of this takeover?
It has been noted in http://cvs.ossp.org/tktview?tn=209,4

> Did you contact Ralf S. Engelschall?
See above. idk what else I'd post to him.

> Usually a new contributor gains the trust of existent maintainer(s)
There were none. The OSSP project had finished and there were no upstream
maintainers.

Now there's me. Do with this what you wish.
I'm just notifying you of this (and of whatever legal issues I found with your
distribution in the process) because I believe ossp-uuid 1.6.3 &c. will better
serve your users, and the mirrors will better ensure long-term correctness.

Also, "usually" is doing a lot of heavy lifting here.
I'd say that "usually" you assemble the upstream history from other archival
sites (https://sr.ht/~nabijaczleweli/urlview-ng) because it doesn't exist and
"usually" you post an obituary to the old bug tracker
(https://sr.ht/~nabijaczleweli/archivemount-ng) —
https://github.com/cybernoid/archivemount/issues/29 — and salvage a mirror of
the old upstream site before it decays even more and you can't anymore. Then
you apply downstream patches and maybe unbreak whatever else.
Those last three points sound awfully familiar. Let's hope for as long as
possible it's not the last four.

> before he
I agree, this doesn't apply to me.

> is given access to the existent infrastructure (source code repository, web page, ftp, etc),
Everyone has access to the existent infrastructure. I have archived it so you
can continue to have access to the contents, and for my and your convenience I
have also adapted it to modern formats.

> instead of replacing it.
Of note here is that you've /already/ replaced it:
  .if !defined(IGNORE_MASTER_SITE_OSSP)
  MASTER_SITE_OSSP+= \
        http://ftp.ntua.gr/pub/utils/ossp/%SUBDIR%/ \
        ftp://ftp.ntua.gr/pub/utils/ossp/%SUBDIR%/
  .endif

Most likely because ftp://ftp.ossp.org has been dying, dead, or broken for an
indeterminate length of time
(but at least since 2023, when you replaced ftp.ossp.org as "Remove dead main
site"
https://github.com/freebsd/freebsd-ports/commit/8449100fd9ecabb4339b1a4ef857c8e53ff6dedb)
and trying to complete a mirror over FTP took hours in a special network
configuration over one specific client; others at the hetzner colo didn't seem
to have these issues; ymmv. I have validated it's the same as what's exposed
over rsync.

I haven't replaced it, and {www,ftp,cvs}.OSSP.org will probably remain in its
current form until rse kicks it. It /should/ do this.

You are welcome to use my mirror site as well, which I hope to maintain until
/I/ kick it. Maybe some-one else will salvage my site and decide to fix
whatever blunders I made last week and update the code for 2080 then. I'm
simply pre-empting this, just as I hope others will pre-empt me.

> Maybe you can ask Ralf for access to ossp.org?
I'm not interested in *.ossp.org except for its archival qualities (and the
shadow bug reports); this seems like a lot of meddling in rse's infra. Unclear
why I'd want this. It's not like you use that anyway.

Well, I guess users do once they see the ossp.org link. And they keep posting
to the CVSTrac bug tracker. And getting no response since 2009 (because the
project had finished by then).

> We don't want to end up in another xz situation (https://tukaani.org/xz-backdoor/).
Then you're naturally free to pull in any patches piece-meal, under the terms
of any applicable licences of course, and I remain interested in any bugs that
you do find.

-- 
You are receiving this mail because:
You are the assignee for the bug.