public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29643] Release upload process improvements
Date: Thu, 06 Oct 2022 17:50:27 +0000	[thread overview]
Message-ID: <bug-29643-14326-LFHVzN2WzQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29643-14326@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29643

--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
(In reply to iank from comment #1)
> This is a great idea, and I suggest using the GNU FTP software. It is
> unpublished currently, I think only because of momentum that it started
> as a tiny script 16 years ago but we (FSF) could publish and/or share it
> right away (just say the word). We recently had a volunteer audit the
> code for security issues and have been working toward publish a release
> that had all the documentation for other people to easily use it, but
> that doesn't need to be perfect, we can just do it.

If you do publish the scripts please add a pointer in this bug.

> For example, (and I would just open a separate bug for this, but I want
> to get this off my chest): I notice that the sort order on
> https://sourceware.org/pub/ is alphabetical instead of version ordering,
> which is confusing. On the GNU FTP, we apparently get the right sort
> ordering through debian's config,

It looks like we already are using VersionSort so this should be correct.
Do you have an directory where the sort oder is wrong?

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

  parent reply	other threads:[~2022-10-06 17:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-02 21:17 [Bug Infrastructure/29643] New: " mark at klomp dot org
2022-10-03  3:10 ` Ian Kelling
2022-10-03 17:10   ` Frank Ch. Eigler
2022-10-07 15:38     ` Ian Kelling
2022-10-03  4:08 ` [Bug Infrastructure/29643] " iank at fsf dot org
2022-10-06 17:50 ` mark at klomp dot org [this message]
2022-10-12  4:07 ` iank at fsf dot org
2022-12-31 16:14 ` mark at klomp dot org
2023-01-04 11:14   ` Ian Kelling
2023-01-04 11:14 ` iank at fsf dot org
2023-01-10  9:51 ` iank at fsf dot org
2023-01-10 10:04 ` iank at fsf dot org

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=bug-29643-14326-LFHVzN2WzQ@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=overseers@sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).