releng

#10913 untag nextcloud modules from epel8-modular-updates
Closed: Fixed by humaton. Opened by carlwgeorge.

Closed: Fixed
Reopen Issue

Describe the issue

The Fedora nextcloud module has repeatedly been built for epel8 via stream expansion, despite the packages not being installable. This has been reported to the maintainer with no action for six months.

https://bugzilla.redhat.com/show_bug.cgi?id=2042653

Separately someone has started the non-responsive maintainer process for that maintainer.

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/FQAEZ5SZLU26LLG6DQEFJAKWOQG5PCBK/

Via my provenpackager permissions I have added the -epel8 string to the platform dependencies in the modulemd to prevent future module builds from expanding to include an epel8 build. Next I would like to untag the existing modules so that they are removed from the repos, but I do not have koji admin permissions. I believe the command needed for this is:

koji untag-build --all --verbose epel8-modular-updates nextcloud

When do you need this? (YYYY/MM/DD)

No deadline, the packages are uninstallable and that doesn't change if this takes days, weeks, or months to get to.

When is this no longer needed or useful? (YYYY/MM/DD)

EPEL8 retirement in 2029.

If we cannot complete your request, what is the impact?

Uninstallable packages from EPEL make Fedora and EPEL look bad.

@carlwgeorge 

$ koji untag-build --all --verbose epel8-modular-updates nextcloud
untagging nextcloud-nextcloud_22-820210712193613.9edba152
untagging nextcloud-nextcloud_stable-820210712183013.9edba152
untagging nextcloud-nextcloud_20-820210712182853.9edba152
untagging nextcloud-nextcloud_19-820210712182738.9edba152
untagging nextcloud-nextcloud_21-820210712182939.9edba152
untagging nextcloud-nextcloud_19-820210630133545.9edba152
untagging nextcloud-nextcloud_20-820210630133442.9edba152
untagging nextcloud-nextcloud_stable-820210630133028.9edba152
untagging nextcloud-nextcloud_21-820210630133336.9edba152
untagging nextcloud-nextcloud_stable-820201210100155.9edba152
untagging nextcloud-nextcloud_20-820201210100223.9edba152
untagging nextcloud-nextcloud_19-820201210100256.9edba152
untagging nextcloud-nextcloud_18-820201210100326.9edba152
untagging nextcloud-nextcloud_stable-820210116140253.9edba152
untagging nextcloud-nextcloud_20-820210116140218.9edba152
untagging nextcloud-nextcloud_19-820210116140330.9edba152
untagging nextcloud-nextcloud_18-820210116140359.9edba152
untagging nextcloud-nextcloud_19-820201228205310.9edba152
untagging nextcloud-nextcloud_18-820201228205342.9edba152
untagging nextcloud-nextcloud_20-820201228205117.9edba152
untagging nextcloud-nextcloud_stable-820201228205225.9edba152

Done.

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

It looks like this was fixed but then another build happened.

https://koji.fedoraproject.org/koji/buildinfo?buildID=2040056

I'm not sure how this build happened since epel8 is excluded from the stream expansion.

https://src.fedoraproject.org/modules/nextcloud/c/9a6c3a7a1707fdade05861e08951988183b8091b?branch=nextcloud-21

That build is showing up in the epel8-modular repo, please untag it as well. Could we somehow block this module from being built in epel8-modular-updates?

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

Metadata Update from @phsmoura:
- Issue tagged with: low-gain, medium-trouble, ops

Current status:

Extra Packages for Enterprise Linux Modular 8 - x86_64
Name            Stream             Profiles              Summary                                                   
nextcloud       nextcloud-22       default, testing      A private file sync and share server - version 22.0.x     
nextcloud       23                 default, testing      A private file sync and share server - version 23.x.x     
nextcloud       24                 default, testing      A private file sync and share server - version 24.x.x

Just like the earlier streams, none of these are installable due to missing php-pecl-imagick, php-pecl-memcached, php-pecl-redis5, and php-smbclient.
  • https://src.fedoraproject.org/modules/nextcloud/c/3711ee74b3e5ffdf75b648b3640f8c0a811603ca?branch=nextcloud-22
  • https://src.fedoraproject.org/modules/nextcloud/c/831c407618d954c07f7a0bcf8475016e0cd6cfd4?branch=23
  • https://src.fedoraproject.org/modules/nextcloud/c/f8ac542493820922fc1830afb4840165ce0be486?branch=24

I think these changes will prevent the module from being built for epel8 again. Please run the koji untag-build --all --verbose epel8-modular-updates nextcloud command again to untag the existing module builds.

https://pagure.io/fesco/issue/2838#comment-814876

 
$ koji untag-build --all --verbose epel8-modular-updates nextcloud 
untagging nextcloud-23-820220801190052.nx4
untagging nextcloud-24-820220801192024.nx4
untagging nextcloud-nextcloud_22-820220801190557.9edba152

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

low-gain medium-trouble ops

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.