#11720 Unretire rpms/aespipe
Closed: Fixed by humaton. Opened by jhladky.

  • Describe the issue

User has an old disk encrypted with aespipe and he wants to read in Fedora-38. I have tried to build the package on f38 and there was no issue.

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

2023/10/16

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

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

Old drives cannot be read on current Fedora.


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

Hello,

I will re-take the ownership of the package. I just need need it to be moved back to the production or link to instructions how to do that.

Thanks a lot
Jirka

I have found a procedure described here:

https://docs.pagure.org/releng/sop_unretire.html

I have followed the process and opened a BZ here to document the request to unretire the package:
https://bugzilla.redhat.com/show_bug.cgi?id=2243029

Thanks
Jirka

Hi @jhladky,

thanks for contacting releng. What you found is a releng SOP and an old one. It's not related to your part in this process. For future please reference packaging docs at https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming

The package is retired for more than 8 Weeks as per https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming
We require a re-review to unretire this package.

Once you have BZ with fedora_review+ please reopen this ticket.

Hi Tomas

there is a BZ with fedora_review+
https://bugzilla.redhat.com/show_bug.cgi?id=2244729

Thanks!
Jirka

The package is now unretired. For missing branches please use $fedpkg request-branch

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

Metadata