#6 [RFE] Drop this upstream package and use src.fedoraproject.org Pagure instead
Opened by sgallagh. Modified

Is there any valid reason to maintain this as a separate upstream anymore, or can we do what we did for fedora-release and fedora-repos and instead move this to using the dist-git project as the canonical upstream for this?


I think it's helpful for @duffy and the design team to have source tracking for the individual image files. So either they'd end up all listed as Sources in dist git and stored in dist git, or else in a source tarball which comes from... who knows where.

Yes, very much so. Having this pagure set up makes it infinitely easier for us to update the images. Please let's keep it?

I may have been unclear; I'm talking about doing something like https://src.fedoraproject.org/rpms/nodejs-packaging/c/8de3f914f4c8e2e0ed07563d68b6bfacd96f2aa3?branch=rawhide where we moved all of the contents of the upstream repo into the dist-git repo.

However, I do understand the concern about having to include all of the image files as Sources; that could be tedious to set up initially.

Once it was set up, the idea would be that your existing workflow would be largely unchanged, but that releases wouldn't require generating a tarball in one repo, uploading it to the lookaside cache and then updating the spec in the dist-git repo to consume it. You'd just perform the release from the same repository.

I am not opposed to doing what sgallagh suggests, even if it does involve an initial amount of work to adjust from using one tarball to NN Source files.

I would ask that maybe we time this change so that I don't have to break workflow right before a release.

This ticket has been open for two and a half years; I'm fine holding it off until after F34 ships.

Maybe the source git approach here is would be an option? That keeps this as the working repo for all the various files and reduces the workflow steps.

Eh. Not a fan. I'd rather just move it over.

Please note that this either needs to move to Forge or dist-git, as pagure.io is shutting down. There is plenty of precedent for logos being its own source repo though, and that makes sense given that dist-git is cloned with every package build, it seems cleaner to keep the sources as a tarball in lookaside cache rather than in git history. Also, logos are several MB of binary data, compared to release/repos which are just a few text files.

Ping? pagure is due to be decommissioned in the next few weeks, this needs to move to forge before then.

Sorry, I thought I replied here.

I think it should move under design team.

I'll try and ping them next week again...

I was asked to file a ticket on it: https://forge.fedoraproject.org/design/tickets/issues/70

Metadata