search

sailfishos-chum / main

Documentation and issue tracker for the SailfishOS:Chum community repository
https://build.merproject.org/project/show/sailfishos:chum
MIT License
26 stars 4 forks source link

How to update package info at SailfishOS:Chum OBS repository? #107

Open Olf0 opened 1 year ago

Olf0 commented 1 year ago

QUESTION

Which process is envisioned to update a package description at the SailfishOS:Chum OBS repository?

STEPS TO REPRODUCE

  1. Be maintainer of a package in SailfishOS:Chum:Testing or in some other repo hosted at the SailfishOS-OBS.
  2. Submit it to SailfishOS:Chum and have it accepted.
  3. Alter the package's description at SailfishOS:Chum:Testing etc.
  4. Submit it to SailfishOS:Chum and have it accepted, again.

The old description of this package at SailfishOS:Chum stays.

ADDITIONAL INFORMATION

I have not found any technical means to update a package description at a OBS-repository after it was initially submitted and accepted, if one is not maintainer of the the package at the target repo or administrator of the target repo. Side note: The description field of the package submission form only creates a description for the specific submission.

I have tried asking to update various package descriptions at SailfishOS:Chum with the one from SailfishOS:Chum:Testing via the description of the request or as a comment to it couple of times, and even succeeded once or twice, but see that this is a fully manual process, which requires an admin of SailfishOS:Chum to go to the package at SailfishOS:Chum:Testing, copy its current description and paste it as package description at SailfishOS:Chum. Hence this is not a feasible process for the permanently growing number of packages at SailfishOS:Chum.

What seems to work well, is to submit a request to delete a package at SailfishOS:Chum and to pose another request which submits the package again. For OBS this submission is an initial one, hence the package description is automatically copied, AFAIU. Up to now this happened rather as a side effect of renamed packages and I always waited until the deletion request was accepted before submitting the package anew.

Suggestion

Define the scheme of sending a request to delete a package at SailfishOS:Chum, immediately followed by a submission request for this package as the regular process to update the description of a package at SailfishOS:Chum.

Hence this issue is rather to document this process and make the maintainers (currently principally @piggz and @rinigus) aware that a combination of a deletion request followed by a submission request of the same package shall both be accepted in their original order to achieve an updated package description without any significant period of time this package is not available at / from SailfishOS:Chum.

Olf0 commented 3 months ago

As a workaround this scheme can be used:

  1. Update package information in the SailfishOS:Chum:testing repository.
  2. Pose a request to delete the package in the SailfishOS:Chum repository and clearly denote in the request description, that this request must be carried out before accepting the subsequent re-submission of the same package, explicitly naming updating the package information as the reason.
  3. Re-submit the package with updated package information from the SailfishOS:Chum:testing repository to the SailfishOS:Chum repository and clearly denote in the request description, that this request must be carried out after accepting the prior deletion request for the same package, explicitly naming updating the package information as the reason.