#13033 Deletion of outdated copr chroots
Closed: Fixed by phsmoura. Opened by bochecha.

Describe what you would like us to do:

About 6 years ago, I had created a Whatchghost Copr, to build watchghost in Fedora and EL as that was a project my employer was working on.

Fast forward today, and this thing has been spamming me about "upcoming deletion of outdated chroots in your projects", beacause I have abandonned this thing and my employer isn't working on it anymore. :shrug:

(in the meantime, I caught a seasonal flu as we all do every year, it attacked my brain and spinal chord, leaving me paraplegic and with cognitive troubles, leading to huge memory problems :cry:)

I would like to delete the chroots so that new releases of Fedora and EL don't keep building those packages, taxing our planet some more with all those bits being shifted needlessly, both with the builds and the emails sent.

But it seems I can't do it myself because contrarily to what the emails say I am not an admin, as the @watchghost group has 0 members...

When do you need this to be done by? (YYYY/MM/DD)

ASAP, but whenever the team has time of course. :wink:

Copr_upcoming_deletion_of_outdated_chroots_in_your_projects.mbox


Metadata Update from @kevin:
- Issue assigned to kevin

Hi! Long time no see!

I've added you to the group. You will need to logout and back on to copr and then you should be able to delete things. :)

Let me know if there's anything further we can do for you!

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

Indeed, it has been a very long time... 🫣

So unfortunately, I still can't delete the project and its chroots :point_down:

1000001952.png

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

Hi @kevin, as I said above, I still can't delete the chroots myself. :disappointed:

Ah, surprisingly, today it worked. :confused:

So you can close it again, then. :shrug:

Metadata Update from @zlopez:
- Issue tagged with: copr

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

Metadata