Signal-ftp-sync removed on master.gnome.org

Hello, I always used signal-ftp-sync to update master.gnome.org when added a mac or windows binary, as explained on Uploading binaries:

https://wiki.gnome.org/MaintainersCorner/Binaries

Now the command does not exists. Any help?

I’ve removed that line from the wiki page. There’s no replacement for it: just got to wait for mirrors to sync.

But 5h passed and is not updated.

I’m sure there’s something missing.

Xavier,

There’s no replacement for signal-ftp-sync, that script was used ages ago to sync ftp.acc.umu.se, formerly known as ftp.gnome.org, whenever a new tarball/binary was uploaded to master.gnome.org. These days (and since we moved to have multiple mirrors thanks to mirrorbrain/mirrorbits) each individual mirror has its own sync schedule, there’s no other way around than waiting for a specific mirror to synchronize.

Sorry that discourse does not let me put more than 2 links on the post - “new users max two links” :frowning:

Here:
http://ftp.acc.umu.se/mirror/gnome.org/binaries/mac/chronojump/
and (changing “mac” for “win32”)

You can find Chronojump-2.3.0.dmg and Chronojump-2.3.0.exe

BUT on
https://download.gnome.org/binaries/mac/chronojump/
and (changing “mac” for “win32”)

you cannot find them, BUT watching their parent directories chronojump folders got updated yesterday:

So download DOT gnome DOT org SLASH binaries is updating weirdly.

Should be fixed by now, please let me know if it’s re-happening, thanks!

Hello Andrea, I uploaded two files:

/ftp/pub/gnome/binaries/win32/chronojump/Chronojump-2.3.0-1-g84d5217.exe
/ftp/pub/gnome/binaries/mac/chronojump/Chronojump-2.3.0-1-gcf1ff.dmg

3,5 hours ago and they do not appear on download DOT gnome DOT org SLASH binaries

For some reason all the files you mv from your home directory to the relevant /ftp path get the wrong SELinux label, that doesn’t happen for my non-privileged user and I’m figuring out why, how do you upload these files? direct scp to the relevant path or scp to home then cp/mv?

I scp to home path and then I mv

Missatge de Andrea Veri via GNOME Discourse <noreply@gnome.org> del dia dt., 17 de gen. 2023 a les 17:14:

So the culprit actually is mv always maintains the SELinux context of a specific file whereas cp does not, please also see [1] in this regard. ftpadmin handles this correctly but when you manually copy files over you need to remember you should use cp rather than mv. I fixed the existing files for you for now.

[1] SELinux/mvcpinstall - Fedora Project Wiki

Ok, thank you very much and sorry for the inconvenience, I take note for future uploads.