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

It would have been a good idea to actually ask me why I retired the package in the first place ...

I doubt that any packager in Fedora can maintain this package at all (and I'm saying this as the maintainer of 1000-2000 Rust packages, depending on how you count), unless we first significantly invest time into improving Rust packaging tools for "workspace" packages like zola.

Additionally, because the currently packaged version of zola was very old, it had very outdated dependencies - most of which I have already retired, as well. So the package that was unretired here is now hopelessly broken.

As such, I request that the unretirement is reverted, at least for the F37 branch. I intentionally retired this package before the final freeze to ensure a broken, outdated, and unmaintained package does not leak into F37 repositories.

If not rebuilt, it won't be tagged back automatically.

Hi @decathorpe, asking the previous maintainer about the reasons is not really part of the process. Even if it was I am not sure how should I do that if there are 10-20 unretirement requests per week...

It is part of the process.

https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming

You should not do it @humaton, the one who requests the unretirement should do it.

Ok, I was writing from releng side of things.

The package was retired on 2022-09-30. I have 8 weeks, i.e., until 2022-11-25, to get it re-packaged before I have to undergo the new review process[1]. The project is under active development upstream, the last release was in August, just a couple of months ago, and it included some real changes. I don't know what a "workspace" package is, so I don't understand that objection. I'm totally happy that the package is still reverted in f37 and am happy to wait until the release of f37 is accomplished to make an attempt to try to package it anew, with a newer upstream release, and hopefully fewer obsolete dependencies.

[1] https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming

The problem is that for newer versions of the package, the hacky workarounds that were used to build the current version no longer work. Believe me, I tried. The only way to work around the problem is now to not use dynamic BuildRequires at all but specify all dependencies manually (plus package all the missing dependencies for new versions, which are numerous).

Ok. I'll go ahead and re-orphan the package and my project will take the compile-from-source route.

I now realize that what was meant by "workspace" package is a Rust project that uses Rust "workspaces". I guess those are essentially impossible to package in Fedora, which is good to know.

One point about procedure, though. If checking with the prior maintainer is really part of the process it makes sense for that to be part of the issue process, not part of a side-channel email process described in a Fedora document some where.

I don't know how to make that happen, but it really makes sense to me that that should be public and publicly recorded.

I can not orphan the package, I get the following error: "Unable to orphan the package: An error occurred at the database level and prevent the action from reaching completion."

Since the package was not actually built after being unretired, could it please be blocked in koji's f37 and f38 tags again?

It is blocked now, and the package is orphaned.