Add scripts to generate repos

[mwt]

What is the purpose of this change?

This adds two scripts. One builds the apt repo and the other builds the yum repo. The scripts can be run using make repo_apt and make repo_yum.

Was the change discussed in an issue or in the forum before?

Once done, this should close #136.

Checklist

• I have read the contribution guidelines.
• I have added tests for all changes in this PR if appropriate.
• I have added documentation for the changes if appropriate.
• All commit messages are in house style.
• I'm done, this Pull Request is ready for review :-)

[ncw]

This is looking very nice :-)

I think I'd like to install the dependencies separately rather than download them into the mount.

What is the best way to install https://github.com/ionos-cloud/reprepro ? I built a deb from its source because I couldn't find a repo, but I'm guessing there is one somewhere?

I used

apt install createrepo-c rpm

To get the yum deps.

The apt repo worked fine, but the yum repo has thrown up a bug in rclone mount - using --vfs-cache-mode writes I get this, whereas it works find with --vfs-cache-mode full.

gpg: can't open '/mnt/yum.rclone.org/i386/repodata/repomd.xml': Input/output error
gpg: signing failed: Input/output error

Which was caused by

2022/05/23 12:18:07 DEBUG : i386/.repodata/repomd.xml: >Open: fd=<nil *ReadFileHandle>, err=can't open file - writer failed
2022/05/23 12:18:07 DEBUG : i386/.repodata/repomd.xml: >Open: fh=<nil>, err=can't open file - writer failed

Which in turn was caused by the file being in the cache and not uploaded yet, which is something rclone should deal with.

Anyway, that's not relevant to this issue!

I've got the two repos hosted now

• https://apt.rclone.org/
• https://yum.rclone.org/

How do they look to you?

I've got lots of older versions I can pump in - do you think that is a good idea?

[mwt]

That's how I installed reprepro as well. I just installed the deb after building it.

There are two junk files in the rpm repo from a failed run. You can remove ./repodata and ./.rpm from the root folder.

You should be able to add back versions. I found that the last 10 versions were safe. Going further caused some issues because of inconsistent architecture names. Even then, I don't think there were inconsistencies with the popular architectures.

Right now, reprepro is configured to retain 20 versions. This can be easily changed.

[mwt]

@ncw The repo is mostly generating fine. However, your key is only dsa1024 which isn't accepted by current versions of Debian/Ubuntu or the RHEL version I tried.

It might be a good idea to use a new key for this repo without changing your default key in gpg. You can use dsa4096 which will probably be accepted for a while.

GPG is also using SHA1 to sign both repos which I think is also not allowed. Do you have something like personal-digest-preferences SHA1 in your config (~/.gnupg/gpg.conf)? You could probably fix this by changing it to personal-digest-preferences SHA256.

[mwt]

Hi, I'm still available to help with this if you have an additional dsa4096 key that I can set the script to use. Additionally,
https://mirror.mwt.me/rclone/
is still up with 17 versions.