#579 prunerepo doesn't clean projects where automatic createrepo is disabled
Closed: MIGRATED a year ago by nikromen. Opened 5 years ago by praiskup.

Per code:

    def prune_project(self, project_path, username, projectdir):
        [...]
        try:
            if not get_auto_createrepo_status(self.opts.frontend_base_url, username, projectname):
                loginfo("Skipped {}/{} since auto createrepo option is disabled"
                          .format(username, projectdir))
                return

Metadata Update from @msuchy:
- Issue tagged with: meeting

5 years ago

Metadata Update from @msuchy:
- Issue untagged with: meeting

5 years ago

The problem of "auto createrepo disable" is it's original purpose -- KDE/Gnome developers use it (original requestors) for "batch updates" of packages, so they build into /devel repo, and once everything is ready - they do the createrepo manually. The question is who of them enable the automatic prunerepo later, and who not .. and how much priority we should give here (how much storage we would save, research needed...).

I for one would disable createrepo for repositories for pull-requests; so I don't propose the repository to anyone for use. In my case, such builds would never been removed...

IMO, we should run the prunerepo even in this case (one day) -- and do the cleanup using the "production" repodata (not devel).

Metadata Update from @praiskup:
- Issue tagged with: RFE

5 years ago

Metadata Update from @nikromen:
- Issue close_status updated to: MIGRATED
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata