Skip to content

papyrus: fix build with GNOME 50, GCC 15#180

Merged
jackpot51 merged 3 commits into
pop-os:masterfrom
PSGtatitos:master
May 26, 2026
Merged

papyrus: fix build with GNOME 50, GCC 15#180
jackpot51 merged 3 commits into
pop-os:masterfrom
PSGtatitos:master

Conversation

@PSGtatitos
Copy link
Copy Markdown
Contributor

@PSGtatitos PSGtatitos commented May 26, 2026

  • I have disclosed use of any AI generated code in my commit messages.
    • If you are using an LLM, and do not fully understand the changes it is making to the code base, do not create a PR.
    • In our experience, AI generated code often results in overly complex code that lacks enough context for a proper fix or feature inclusion. This results in considerably longer code reviews. Due to this, AI authored or partially authored PRs may be closed without comment.
  • I understand these changes in full and will be able to respond to review comments.
  • My change is accurately described in the commit message.
  • My contribution is tested and working as described.
  • I have read the Developer Certificate of Origin and certify my contribution under its conditions.

@jackpot51 jackpot51 merged commit 77c9381 into pop-os:master May 26, 2026
1 check passed
@PSGtatitos
Copy link
Copy Markdown
Contributor Author

Hi @jackpot51, it's been ~14 hours since the merge but Papyrus still doesn't show up in the COSMIC Store.
The direct Flatpak install works fine (flatpak install --user io.github.PSGtatitos.papyrus).
Is there a rebuild/indexing step needed on your side?
Thanks!

@PSGtatitos
Copy link
Copy Markdown
Contributor Author

Hi @jackpot51 (and team),
Just following up — it's been over 24 hours since the PR was merged, but Papyrus still doesn't appear in the COSMIC Store.
The app installs and runs correctly using the direct command:

flatpak install --user io.github.PSGtatitos.papyrus

Is there a manual rebuild or indexing step needed on the backend for new apps to show up in the store? Any guidance would be appreciated.
Thank you for your help!

@jackpot51
Copy link
Copy Markdown
Member

@PSGtatitos let me know if this makes it show up:

flatpak update --appstream

Then close and open COSMIC Store.

@PSGtatitos
Copy link
Copy Markdown
Contributor Author

This is the output:
~ ❯ flatpak update --appstream
Updating appstream data for user remote cosmic
Updating appstream data for user remote flathub
Updating appstream data for user remote papyrus-origin
Error updating: Error updating appstream2: No such ref 'appstream2/x86_64' in remote papyrus-origin; Error updating appstream: No such ref 'appstream/x86_64' in remote papyrus-origin

@PSGtatitos
Copy link
Copy Markdown
Contributor Author

Hey @jackpot51,
I just changed my .metainfo.xml file in my repository to hopefully not interfere with the index rebuild. I just think you need to trigger a CI rerun so everything is rebuilt with the new .metainfo.xml file. Thank you for taking the time to review this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants