Disabling Fedora 30 chroots in Copr

[Jakub Kadlcik]

Hello,

we have just disabled Fedora 30 chroots in Copr.

According to the Fedora wiki [1], Fedora 30 reached the end of its life
on 2020-05-26 and therefore we are disabling it in Copr.

That effectively means that from this moment, it is no longer possible
to submit builds for the following chroots:

- fedora-30-x86_64
- fedora-30-i386
- fedora-30-ppc64le
- fedora-30-aarch64
- fedora-30-armhfp

[1] https://fedoraproject.org/wiki/End_of_life


Jakub

EnablingFedora33chrootsinFedoraCopr

[Pavel Raiskup]

On Tuesday, August 18, 2020 3:12:06 PM CEST Jakub Kadlcik wrote:
>  we have just disabled Fedora 30 chroots in Copr. 
And at the same time, we enabled fedora-33-* chroots.  It required us to do
a small bug-fix release of copr-frontend today, but I believe it went out
smoothly without interrupts.

Happy building,
Pavel

>  According to the Fedora wiki [1], Fedora 30 reached the end of its
> life
>  on 2020-05-26 and therefore we are disabling it in Copr.
>  
>  That effectively means that from this moment, it is no longer possible
>  to submit builds for the following chroots: 
>  - fedora-30-x86_64
>  - fedora-30-i386
>  - fedora-30-ppc64le
>  - fedora-30-aarch64
>  - fedora-30-armhfp
>  
>  [1] https://fedoraproject.org/wiki/End_of_life
>  
>  
>  Jakub
>  _______________________________________________
>  copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
>  To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedorahosted.org/archives/list/[e-mail]...
>

EnablingFedora33chrootsinFedoraCopr

[Cole Robinson]

On 8/18/20 10:48 AM, Pavel Raiskup wrote:
>  On Tuesday, August 18, 2020 3:12:06 PM CEST Jakub Kadlcik wrote:
> > we have just disabled Fedora 30 chroots in Copr.
>  
>  And at the same time, we enabled fedora-33-* chroots.  It required us to do
>  a small bug-fix release of copr-frontend today, but I believe it went out
>  smoothly without interrupts.
>   
Was enabling fedora-33-ppc64le intentional? All the other ppc64le
chroots are still disabled, due to the data center move AFAIK

Thanks,
Cole

EnablingFedora33chrootsinFedoraCopr

[Pavel Raiskup]

On Tuesday, August 18, 2020 5:09:32 PM CEST Cole Robinson wrote:
>  On 8/18/20 10:48 AM, Pavel Raiskup wrote:
>  > On Tuesday, August 18, 2020 3:12:06 PM CEST Jakub Kadlcik wrote:
>  >> we have just disabled Fedora 30 chroots in Copr.
>  > 
>  > And at the same time, we enabled fedora-33-* chroots.  It required us to do
>  > a small bug-fix release of copr-frontend today, but I believe it went out
>  > smoothly without interrupts.
>  > 
>  
>  Was enabling fedora-33-ppc64le intentional? All the other ppc64le
>  chroots are still disabled, due to the data center move AFAIK 
Yes, I'm sorry.  I did a cut-and-paste mistake, I re-disabled it now.

Pavel

[Jakub Kadlcik]

Hello again,

the Fedora 30 chroots are disabled for around three months now but so far we
haven't marked the built results as outdated. I did it just now, so
according to Outdated chroots removal policy [1], Copr is
going to preserve existing build results in those chroots for another
180 days and then automatically remove them unless you take an action
and prolong the chroots life span in your projects. Read more about this
feature in the  Copr - Removing outdated chroots blog post [2].

The email notifications for upcoming deletion proved to be unreliable
for some users in the past, therefore we tried to improve this
situation within the latest Copr release [3]. We added some on-page
notifications [4] to let you know if some of your chroots are about to
be deleted soon. We also added a page that shows outdated chroots from
all projects that you are an admin of. This should give you a much
better overview than having to go through all projects and looking
into their settings. It also gives you an option to be proactive, and
add a task to your calendar to prolong the chroots that you care
about, and repeat it once in a few months. It shouldn't take more than
a couple of minutes to complete. Please log-in and see
https://copr.fedorainfracloud.org/user/repositories/


[1] https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html
[2] http://frostyx.cz/posts/copr-removing-outdated-chroots
[3] https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
[4]
https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html#eol-chroo...

Jakub

On Tue, Aug 18, 2020 at 3:12 PM Jakub Kadlcik <jkadlcik(a)redhat.com&gt; wrote:
>  Hello,
>
>  we have just disabled Fedora 30 chroots in Copr.
>
>  According to the Fedora wiki [1], Fedora 30 reached the end of its life
>  on 2020-05-26 and therefore we are disabling it in Copr.
>
>  That effectively means that from this moment, it is no longer possible
>  to submit builds for the following chroots:
>
>  - fedora-30-x86_64
>  - fedora-30-i386
>  - fedora-30-ppc64le
>  - fedora-30-aarch64
>  - fedora-30-armhfp
>
>  [1] https://fedoraproject.org/wiki/End_of_life
>
>
>  Jakub

EPEL6andFedora31EOLinCoprfollow(Was:Re:DisablingFedora30chrootsinCopr)

[Pavel Raiskup]

On Monday, November 23, 2020 12:52:43 AM CET Jakub Kadlcik wrote:
>  The email notifications for upcoming deletion proved to be
> unreliable
>  for some users in the past, therefore we tried to improve this
>  situation within the latest Copr release [3]. 
Because of what Jakub said ^^, we made Fedora 30 EOL in Copr unusually
late.

So I just want to warn that the Fedora 31 is going to be EOLed much sooner
in Copr, in the next few days (see upstream schedule [1]).  And since
EPEL-6 approaches EOL by the end of the this November, we'll make it EOL
soon as well.

[1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html
>  [3] https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html
Pavel

[Alexander Ploumistos]

Hello Jakub,

I noticed that some of my projects still have chroots for even older
releases, e.g. F28, F29 without the option to remove them. In another
instance, only a specific F30 arch shows up among the chroots to be
removed or extended, while the others architectures are not picked up.
Is there something I can do to remove them, other than deleting the
entire build along with every other chroot?

Best regards,
A.

[Jakub Kadlcik]

Hello Alexander,
what do those chroots say in their "Remaining time" column, please?


Jakub

On Mon, Nov 23, 2020 at 8:34 AM Alexander Ploumistos
<alex.ploumistos(a)gmail.com&gt; wrote:
>  Hello Jakub,
>
>  I noticed that some of my projects still have chroots for even older
>  releases, e.g. F28, F29 without the option to remove them. In another
>  instance, only a specific F30 arch shows up among the chroots to be
>  removed or extended, while the others architectures are not picked up.
>  Is there something I can do to remove them, other than deleting the
>  entire build along with every other chroot?
>
>  Best regards,
>  A.
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]