This issue should be fixed since release 2:19.0+dfsg1-1pureos1 of kodi, which should appear in Debian Byzantium within a week.

Which hardware? Which version of plymouth? Amber or Byzantium?

Added to debian/control file, patch merged.

BTW. This also happens on amber-phone.

@jonas.smedegaard I don't think we're using rred in PureOS though?

Merge request holding Vcs fields here: https://source.puri.sm/Librem5/debs/squeekboard/-/merge_requests/3

I'll inquire with MLS to see how we get a key.

I think that's what we should do, see above

The Ubuntu issue referenced in that changelog section is this: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918112

apt 2.2.2 arrived in Debian testing now (so should soon enter PureOS landing) might fix this - judging from its changelog: https://tracker.debian.org/media/packages/a/apt/changelog-2.2.2

{F723349}This happened to me too. This is a copy of /var/lib/apt before it was cleared out.
I then moved these files and run updates without issue. I tested reverting back to the broken apt files and running updates, that came back with 0 to upgrade.
We would likely have to revert to the old packages that we don't host anymore to reproduce the error. One idea is to boot a live USB and try to copy over the broken apt files.

Are we trying to get an API key from Mozilla Location Services?

What are we trying to achieve?

@jeremiah.foster location services are off by default, this is for the case where the user enables it. Would you drive that process since it affects all devices running PureOS the same way??

I don't know if we have a formal policy around the Mozilla location services though I don't think we should be using Debian's. I think we need to create a policy or at least have a process to do so.

@jeremiah.foster any plans here? Should that go via the sys-team to manage all api keys?

wrong issue tracker - moved to https://source.puri.sm/Purism/docs.puri.sm/-/issues/38

pipx is a technical tool, not intended for regular users. It was packaged for Debian as it was requested for the _administration_ of Librem One services but explicitly *not* for general use.

Arch Linux discussion: https://bbs.archlinux.org/viewtopic.php?id=260567

as previously noted, this is a non-issue: no non-free package is suggested because the suggested package is not registered in apt so it is neither free nor non-free, it is instead nonexistent.

as previously noted, this is a non-issue: no non-free package is suggested because the suggested package is not registered in apt so it is neither free nor non-free, it is instead nonexistent.

as previously noted, this is a non-issue since the package cannot really suggest something that does not exist as a package registered with apt.

I have tested and can confirm that the use of suffix purge works to drop local fork:
https://lists.puri.sm/pipermail/pureos-changes/2021-March/001152.html shows the packages I uploaded, and https://software.pureos.net/search_pkg?term=zpb shows (at the time of writing this) that landing now contains the package from Debian.

Looks good.

https://tracker.pureos.net/w/development/packaging_overview/#mandatory-debian-control-file Please review.

Good points.

https://source.puri.sm/Librem5/debs/webkit/-/merge_requests/13

The same for me with UEFI, I tried several software including the recommended Etcher without ever succeeding in obtaining a bootable USB key, and with several USB keys, before resigning myself. It's a shame, the other distributions are not a problem. What is missing from the ISO image?

Sorry to reopen, but I think the Guidelines are currently in a confusingly odd state:

Thanks for a swift resolution.

Excellent!

I made the changes to the debian/control file (maintainer email address, VCS-*) mandatory.

Done: https://tracker.pureos.net/w/development/packaging_overview/

unp does not suggest a non-free package, only a non-existent one.

What exactly was tested 1000 times? some apt tool using an up-to-date libapt, or something more low-level?

I can confirm this;

I did two runs of 1000 calls to the server and did not see any anomalies.