#2753 Can we have at least one previous update for each updated package?
Closed: Rejected by name. Opened by name.

Consider this bug: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2113

Now, as a user, I have two equally bad options:

  • Downgrade all the way down to the first package available in Fedora 35 which is terrible considering how many fixes PipeWire has seen
  • Compile your own PipeWire which is near impossible for absolute most users out there.

You may argue that keepcache=True addresses this issue only it's disabled by default nowadays and once you get an issue like this it's already too late to enable it and all Fedora mirrors have already purged the previous update.

I really really really really want Fedora to consider keeping at least one previous update for each package available on its mirrors.

This is doubly important for Fedora releases which have stopped being supported because in this case you either have access to the original packages or their last versions in updates.


This is something I'd personally like too, but this is a request for Release Engineering, not us. Last I heard, there were technical limitations in our systems that prevented us from doing it, but you could ask them and find out.

Also note, all versions ever shipped are in our buildsystem, but I'm not sure if there's a straightforward way to access those builds for this scenario.

This is something I'd personally like too, but this is a request for Release Engineering, not us.

I'd be grateful if you helped me out and did everything properly. I'm completely new to pagure.io (only used bugzillas previously) and I don't want to be a source of spam here.

Is it possible to just move this issue over there?

Generally, if you have a proposal to do something differently, it's best to start here: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ -- when a consensus is reached, you can ask around where to file tickets.

This here is a fesco issue tracker. We use it to vote about several processing issues, such as:

  • https://docs.fedoraproject.org/en-US/program_management/changes_policy/
  • https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
  • https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Sponsor_a_New_Contributor/#becoming_a_fedora_package_collection_sponsor
  • resolving arguments when other means have clearly failed

When we vote about stuff, we sometimes discuss it here. However, this is not the Fedora's development discussion forum. This is a place for voting. The majority of Fedora contributors do not follow this issue tracker and as such, cannot participate in the discussion unless they are told about it.


Is it possible to just move this issue over there?

Not that I know of.


See https://pagure.io/fesco/issue/2678 for a previous ticket that asked for a more or less same thing.

@churchyard

Generally, if you have a proposal to do something differently, it's best to start here: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ -- when a consensus is reached, you can ask around where to file tickets.

Considering the issue has been raised twice already, it's quite serious, mustn't be too difficult to implement and you know all the ins and outs, could you start a discussion over there by yourself please? Thank you!

Considering the issue has been raised twice already, it's quite serious

Being proposed twice does not make this serious.

mustn't be too difficult to implement

The short discussion in https://pagure.io/fesco/issue/2678 suggests it is quite difficult to implement.

and you know all the ins and outs

I don't.

could you start a discussion over there by yourself please? Thank you!

No. This is not how community involvement works.

OK, fine,

We don't have enough resources to have proper QA/QC and we are not interested in alleviating the issue of broken updates either some of which prevent the user from being able to use Fedora at all.

Good. Sorry for bothering you. Time and again everyone responsible for the Linux ecosystem proves how little they care about Linux becoming an OS usable by mere mortals. Have a good day.

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

This is the second time you've come here, made a request, and then insulted everybody when it didn't happen. This behavior is not welcome here.

Metadata