@mak does this mean that the most correct solution for many people will be to simply uninstall fwupd because it is useless for them? i don't remember installing it. it is "Recommends:" by pureos-gnome and gnome-software, but i don't have things configured to automatically install packages simply because they are mentioned in "Recommends:" fields. i think it came preinstalled on my librem 14.

This is an annoying issue, as it is extremely hard (if not impossible currently) to fix properly. A proper fix would be to re-sign the fwupd-amd64-signed binary package, but we can not do that as we do not have any EFI signing facilities for PureOS...
This package has been removed from PureOS (as we don't support UEFI with secure boot signing enabled properly anyways), but users who have installed the package manually before will of course run into this issue now until they run an apt purge fwupd-amd64-signed. We could force the removal of this package via conflicts, but that may also not be an ideal solution here :-/

I have see this message, "failed to update metadata for lvfs" a couple times now when checking for a software update. It doesn't happen often but running the following command seems to help.

Thanks for the suggestions.
Please in future file one suggestion per issue report, to ease further tracking and discussion.

Everything that gets uploaded to the archive gets built for arm64 (librem5) automatically.

Will this automagically get built for the Librem 5 or do we have to put it into the build process for the Librem 5?

Pushed my minor changes to the repo. (pureos/packages/gpodder-adaptive.git)
Uploaded to the repo.

Thank you both for the replies - I'll try and fix up and build.

W: gpodder source: inconsistent-appstream-metadata-license share/metainfo/org.gpodder.gpodder.appdata.xml (cc0-1.0 != gpl-3+)

Are we changing the defaults?

Are we changing the defaults?

I'll try and fix the E: error but the one I worry about is this;

W: gpodder source: inconsistent-appstream-metadata-license share/metainfo/org.gpodder.gpodder.appdata.xml (cc0-1.0 != gpl-3+)

If you didn't touch the licensing then this is not an issue, if you did something with AppStream we should try to figure out this inconsistency.

So I ran the build with;

gbp buildpackage --git-debian-branch="pureos/master"

Lintian says;

E: gpodder source: invalid-version-number-for-derivative 3.10.21-1-1 (must end with pureosX)
W: gpodder source: inconsistent-appstream-metadata-license share/metainfo/org.gpodder.gpodder.appdata.xml (cc0-1.0 != gpl-3+)
W: gpodder: unusual-interpreter usr/share/gpodder/extensions/rm_ogg_cover.py #!/usr/bin/python
W: gpodder: unusual-interpreter usr/share/gpodder/extensions/rockbox_convert2mp4.py #!/usr/bin/python
W: gpodder: unusual-interpreter usr/share/gpodder/extensions/tagging.py #!/usr/bin/python
W: gpodder: wrong-bug-number-in-closes #T1096 in the installed changelog (line 3)
`

Thanks for including the pristine-tar branch. Would be cool if you were to mention how you're building this. For example, just pasting the commands you did to build the deb?

Are you using gbp? What's your conf look like?

@guido any feedback here? ^^^ yay, nay, something else? :D

ok packaged the adaptive version of gpodder at: https://source.puri.sm/pureos/packages/gpodder-adaptive

Packaging an adaptive Gpodder for Byzantium is most welcome - thank you @joao.azevedo

Also AFIK there is no deb version of gpodder adaptive in debian experimental, unlike with other packages like dino-im.

A couple of more reports about this issue in our forums:

In T1091#20414, @ctowne wrote:

Distribution upgrade worked for me.

sudo apt dist-upgrade

Distribution upgrade worked for me.

Another report from a user:

another report:

The patch has been merged and a new release made: https://source.puri.sm/librem5-apps/Stream/-/merge_requests/3

@joao.azevedo Sorry for the spurious ping. :-)

@jeremiah.foster you pinged the wrong João ;)

From what I can see the instructions for telegram-desktop 3.1.1+ds-1~bpo11+1 are the same as for other versions. That is to say, the build instructions appear to require you have API credentials;

Thanks for the clarification!

The patch adds no new features, it just makes the app work again

@jonas.smedegaard yes, this targets Byzantium.

@joao.azevedo did the outside World change, so that this is a regression, or is this a functionality which *never* worked on Stream and the patch is effectively a feature addition?

I assume this issue is targeted byzantium - tagging accordingly.

@jeremiah.foster pinging you here because you packaged Stream for PureOS.

thanks, this is working for now!

i now have 2.6.1+ds-1+deb11u1 and i cannot even log in.

I have updated 6/12 and again 17/12,
i now have 2.6.1+ds-1+deb11u1 and i cannot even log in.

Systemd v248 reverted the software workaround: https://github.com/systemd/systemd/commit/ba2b8f9

gnome-authenticatior already is packaged in Debian, but it is an old version; 3.32

Awesome, thanks for the feedback.
I used the GNOME Disks and reset the passphrase with no issues, worked pretty smoothly, no issues since.
My L15 is still hummin along just fine.

@Wildfire yes, this is fixed in Debian Bullseye

@mak
If time permits please have a look into updating base-files.

To add to this: if initramfs-tools is replaced by dracut the resulting initrd will not include functionality to decrypt a LUKS root filesystem using a LibremKey.

I guess this is done now...

@joao.azevedo please note that bundling multiple issues makes them all harder to track - e.g. I would be uncomfortable assigning the issue report to myself if knowledgable about only a subset of involved issues, would only flag it as done when all parts were done, and would have a hard time noticing when all parts were done.

Assigning to you, @jeremiah.foster as you seem to be involved already and know at least some bits of it...

Sorry for the late reponse.
Unfortunately, PureOS does not support non-free environments like VMware. You are of course welcome to try use it in such environments, but we cannot help with issues you may encounter related to that.

Closing due to lack of info.