Hi,

I have packaged stellarium for mga8 from spec

The new packages versions is here: https://mega.nz/folder/Ph9gHBYS#UpekWJJqcjSKKZsU346D3w

If some packager can check and update in mga8.

Greetings!

Thank you for the notification.
We do already have version: 0.21.0 in Cauldron, but you say 0.21.3 is available, so why not?

Assigning to DavidG who has done most of the recent updates; CC'ing akien the official packager for stellarium who might want to do this.

Assignee: bugsquad => geiger.david68210
CC: (none) => rverschelde
Source RPM: Stellarium => stellarium-0.20.4-1.mga8.src.rpm

I didn't manage to download the SRPM from Mega (it's stuck on "Decrypting folder data" still after 15 min, at least in Firefox Nightly).

But I could update stellarium locally (on Cauldron) by just bumping the version number, I suppose that's what you did too? In such case you can directly attach a .spec file for review (or a diff) instead a SRPM, especially for a package with a voluminous source tarball (372M).
A SRPM is mostly useful for more complex packages where you have to write patches, or use custom-made tarballs for some reason (e.g. to remove nonfree content).

Here's the change I pushed: http://svnweb.mageia.org/packages/cauldron/stellarium/current/SPECS/stellarium.spec?r1=1767136&r2=1767135&pathrev=1767136

stellarium-0.21.3-1.mga9 is now building in Cauldron,
and stellarium-0.21.3-1.mga8 in Mageia 8 core/updates_testing.

---

As you're a packager apprentice, there are two parts of the packaging and QA workflow which you can practice here if you're interested:

- Write an update advisory for the update candidate to Mageia 8 (for the SRPM stellarium-0.21.3-1.mga8 which I built). See https://wiki.mageia.org/en/Update_Advisory_Announcement_Example for details and an example.

- Participate in the QA testing effort to help validate the update. See https://wiki.mageia.org/en/QA_process_for_validating_updates for details.

This is just a suggestion of course, I can do it myself if you're not available.

Assignee: geiger.david68210 => joselpddj
CC: (none) => mageia
QA Contact: (none) => rverschelde

I think what comment 3 says, is actually what I tried to do.

- I've opened this report to indicate the update request for the package in question and added a link to the updated packages (I've also attached the spec requested above).

- I forgot to point out, that it works fine for me so far, both in Mageia Vbox, and in Mageia on real installation.

Assigned also to the quality team to validate!!!

Translated with www.DeepL.com/Translator (free version)

Created attachment 13075 [details]
Stellarium 0.21.3 spec

This is the updated spec.

Thanks!

What I meant to say is that we have a specific workflow for both packagers and QA testers that I suggest you could follow.

Opening the bug report, providing a spec, and testing the update are all very good steps, but there's some more involved in the update workflow:

- Writing an update advisory. That's what will be published on http://advisories.mageia.org/ to let users know about what changes in the update.
It's also what lets the QA team know what they should test (lists the SRPM(s) and RPM(s) that they're supposed to validate). See https://wiki.mageia.org/en/Update_Advisory_Announcement_Example for details and an example.

Here's another real-life example: https://bugs.mageia.org/show_bug.cgi?id=29130#c5

- To actually validate the update, you should test the one that results from what was submitted to the buildsystem. So while the testing that you made with your self-built package is valuable, the real QA testing should be done with stellarium-0.21.3-1.mga8 which I pushed to the buildsystem earlier.

So you should uninstall the version you have currently, install stellarium-0.20.4-1.mga8 from Core Release, and then install stellarium-0.21.3-1.mga8 from Core Updates Testing (this is the "Update Candidate" as described in https://wiki.mageia.org/en/QA_process_for_validating_updates). Once tested (it should update fine, and run fine), you can comment about this as described in the wiki.

Ok,about comment 6:

- I don't have permissions to put the update in the testing repositories, and communication with my mentor is pending next week. I understand that the notices are given when the package is uploaded to the testing repositories, if this is not the case please correct me.

- I have uninstalled my package, I have installed stellarium 0.20.4 from core repositories and update from testing repositories to stellarium 0.21.3. All ok for the moment, update, config, location search, sky options, etc. The new version works fine.

If anyone else can validate this, we can up it to update repositories.

Thanks for your help, I will continue reading the wiki!!

The package is already uploaded to the testing repository as I did it :)
My suggestion was that you do the next step which is to write an update *advisory*, i.e. the document described in the wiki page I linked. But I'll do it to give an example.

Advisory:
=========

Updated stellarium package provides latest release

  This update provides stellarium 0.21.3, which is the latest upstream release.
  It adds a number of new features and fixes some bugs, see the referenced
  release notes for details on the changes since Mageia 8's original 0.20.4.

References:

- https://stellarium.org/release/2021/03/28/stellarium-0.21.0.html
- https://stellarium.org/release/2021/06/24/stellarium-0.21.1.html
- https://stellarium.org/release/2021/09/27/stellarium-0.21.2.html
- https://stellarium.org/release/2021/12/25/stellarium-0.21.3.html

RPM in core/updates_testing:
============================

stellarium-0.21.3-1.mga8

SRPM in core/updates_testing:
=============================

stellarium-0.21.3-1.mga8

Testing procedure:
==================

It's a graphical planetarium application, usage should be fairly intuitive (set location, look at the stars, toggle some buttons).

Adding MGA8-64-OK (assuming it was on x86_64) to the whiteboard for comment 7 - for future tests, remember to do it yourself when you test an update candidate.

Whiteboard: (none) => MGA8-64-OK

Ok, Ok, I understand that you say, for the netx I willl so do

I have others bug reports where I can make it

Thanks!

Technically, QA is supposed to test on the 32-bit arch, as well as on 64. While it's rare for an update to work on one arch and not the other, it does happen.

Because it's rare, and because QA manpower is limited, with certain exceptions we have become less strict about requiring tests on both arches for most updates, especially if there are a large number of updates waiting for QA's attention. 

Personally, I would hope that before submitting an update to QA the packager at least checks for a clean install of the other arch, but realistically I know it doesn't always happen.

So, I have tested this update with a 32-bit install on 64-bit hardware, a Plasma install that uses the server kernel and with a Radeon HD 8490 GPU. There were no installation issues, and no issues noted with using the app, once I made the effort to learn the interface.

Validating. Advisory in Comment 8.

CC: (none) => andrewsfarm, sysadmin-bugs
Whiteboard: MGA8-64-OK => MGA8-64-OK MGA8-32-OK
Keywords: (none) => validated_update

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2022-0004.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED