#7079 reset 27 atomic host ostree repo
Closed: It's all good 5 years ago by mohanboddu. Opened 6 years ago by dustymabe.

We are currently using smart versioning for our ostree repo in Fedora 27 (i.e. using "version": '!OSTREE_VERSION_FROM_LABEL_DATE_TYPE_RESPIN' feature of pungi). Since we have not yet completed the work to move bodhi to pungi from mash we need to go back to not smart versioning like we were doing in previous releases for now. I'll open a PR against pungi-fedora for this.

In order to do this we need the repo to be reset. This can be as simple as removing just the refs fedora/27/${basearch}/atomic-host. Extra credit would be to also prune the repo so that we drop content we no longer care about.


Yup, deleting the ref and pruning should be good. :thumbsup:

FYI: opened PR to pungi-fedora to change this once we have the refs cleaned up: https://pagure.io/pungi-fedora/pull-request/386

I just moved the old repository to
/mnt/koji/compose/atomic/27-old-ticket7079/ and created a new /mnt/koji/compose/atomic/27/, just to prevent loss of data if this was not wanted.
We can remove the old repo in a week I'd say.

I just moved the old repository to
/mnt/koji/compose/atomic/27-old-ticket7079/ and created a new /mnt/koji/compose/atomic/27/, just to prevent loss of data if this was not wanted.
We can remove the old repo in a week I'd say.

+1 let's leave this ticket open until we remove the old repo

can we remove the old repo and close this ticket?

Metadata Update from @syeghiay:
- Issue assigned to mohanboddu

5 years ago

@mohanboddu will remove the /compose/atomic/27-old-ticket7079 repo.

@mohanboddu did you remove the /compose/atomic/27-old-ticket7079 repo yet?

From our grooming discussion on #fedora-releng channel on Apr 12 2019

proposal: close 7079. That dir tree no longer exists. ;)

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

5 years ago

Metadata Update from @mohanboddu:
- Issue status updated to: Open (was: Closed)

5 years ago

Metadata Update from @mohanboddu:
- Issue close_status updated to: It's all good
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata