Cannot find any valid SRPM URL for this ticket. Common causes are:

- You didn't specify `SRPM URL: ...` in the ticket description
  or any of your comments
- The URL schema isn't HTTP or HTTPS
- The SRPM package linked in your URL doesn't match the package name specified
  in the ticket summary


---
This comment was created by the fedora-review-service
https://github.com/FrostyX/fedora-review-service

If you want to trigger a new Copr build, add a comment containing new
Spec and SRPM URLs or [fedora-review-service-build] string.

SRPM URL: https://download.copr.fedorainfracloud.org/results/quentium/Stacer/srpm-builds/10488396/stacer-1.7.0-1.src.rpm

Spec URL: https://github.com/QuentiumYT/Stacer/blob/main/rpm/SPECS/copr.spec
SRPM URL: https://download.copr.fedorainfracloud.org/results/quentium/Stacer/srpm-builds/10488396/stacer-1.7.0-1.src.rpm
Description: Monitor your system (CPU, memory, disk) in a graphical application (Qt). Change and monitor your services. Summarizes basic system information and can show network download/upload speeds/totals.
Fedora Account System Username: quentium
Repo URL: https://github.com/QuentiumYT/Stacer
Debian package: https://packages.debian.org/sid/stacer
COPR repo: http://copr.fedorainfracloud.org/coprs/quentium/Stacer/

Copr build:
https://copr.fedorainfracloud.org/coprs/build/10515650
(succeeded)

Review template:
https://download.copr.fedorainfracloud.org/results/@fedora-review/fedora-review-2481780-stacer/fedora-rawhide-x86_64/10515650-stacer/fedora-review/review.txt

Please take a look if any issues were found.


---
This comment was created by the fedora-review-service
https://github.com/FrostyX/fedora-review-service

If you want to trigger a new Copr build, add a comment containing new
Spec and SRPM URLs or [fedora-review-service-build] string.

Copr build:
https://copr.fedorainfracloud.org/coprs/build/10515654
(succeeded)

Review template:
https://download.copr.fedorainfracloud.org/results/@fedora-review/fedora-review-2481780-stacer/fedora-rawhide-x86_64/10515654-stacer/fedora-review/review.txt

Please take a look if any issues were found.


---
This comment was created by the fedora-review-service
https://github.com/FrostyX/fedora-review-service

If you want to trigger a new Copr build, add a comment containing new
Spec and SRPM URLs or [fedora-review-service-build] string.

> Linux system optimizer and monitoring

There's something wrong with this sentence (phrase?). "optimization and monitoring", "optimizer and monitor", something else?

The ticket title doesn't match the package name. Please retitle.

IIUC, you also need to go through the sponsorship process.

Yes maybe, I am just maintaining a fork of this original project, and I haven't changed its catch line ^^

I don't get it, "Review Request: Stacer - add back to main Fedora repos" it has Stacer in it already. Should I remove everything after the dash?

Also, it was already in Fedora 42 and before, I'm not sure about the process but I'd like adding it back to the repos, it's not first time submission I guess.

I learned that I can sponsor it myself, I can do the publishing and making it available for Fedora users, no clue how I go into that :)

(In reply to Quentin Lienhardt from comment #7)
> Yes maybe, I am just maintaining a fork of this original project, and I
> haven't changed its catch line ^^

As a packager, the job is sometimes to improve things even if upstream
disagrees. In this particular case, the issue is very minor, so if you 
think it doesn't make sense to diverge from upstream, that is acceptable. But
in general, sometimes it is necessary to diverge.

> I don't get it, "Review Request: Stacer - add back to main Fedora repos" it
> has Stacer in it already. Should I remove everything after the dash?

"stacer" is not the same as "Stacer". The Packaging Guidelines say that lowercase
names should be used, to the correct package name is "stacer".
(I see my comment was very cryptic. This wasn't intentional, I was just going
through a number of bugs and trying to deal with each one quickly.)

> Also, it was already in Fedora 42 and before, I'm not sure about the process
> but I'd like adding it back to the repos, it's not first time submission I
> guess.

The process in this case is almost the same as when a new package is submitted.
The package was retired for approx. a year, so a new review is required, and
when that happens, the review is done pretty much as for a new package. 

> I learned that I can sponsor it myself, I can do the publishing and making
> it available for Fedora users, no clue how I go into that :)

https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/
has a general description. In your case, you already have software that you
want to maintain, so the second part is mostly done. But the rest of the
process would need to be followed.

I understand, do I need to help with lots of packaging or can packagers stick to the packages they want? I don't have the time to maintain lots of packages tho

Alright, my bad. No problem, I was just wondering ^^

I see, will go through the process again, thanks for the info.

Also will be reading how to join the maintainers but yeah, not sure how I'll manage that with other packages. I don't even have a Fedora distro ATM ^^'

Thanks for the info