You'll need a recent kernel which is why Amber won't run - I'm using 5.10.0-4-amd64 #1 SMP Debian 5.10.19-1 (2021-03-02) x86_64 GNU/Linux but I'm surprised the one from the OEM ISO didn't work for you. Did you use this to install: http://downloads.pureos.net/byzantium/gnome-oem/2020-11-20/?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 31 2021
Mar 30 2021
I tested this in a Byzantium image in Boxes. It worked, I was able o change the disk encryption passphrase twice on the same VM.
Mar 29 2021
Mar 28 2021
Upstream bug fixed.
@jeremiah.foster I am running Plymouth version 0.9.5-2pureos1. This is on a Librem 13 v3 running Byzantium.
Mar 27 2021
The (supported) way to install Kodi on PureOS is to use the package which is part of PureOS, *not* use external packages from Ubuntu or elsewhere.
This issue should be fixed since release 2:19.0+dfsg1-1pureos1 of kodi, which should appear in Debian Byzantium within a week.
Mar 26 2021
Which hardware? Which version of plymouth? Amber or Byzantium?
Added to debian/control file, patch merged.
Mar 25 2021
Mar 22 2021
Mar 20 2021
BTW. This also happens on amber-phone.
@jonas.smedegaard I don't think we're using rred in PureOS though?
Mar 18 2021
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
Mar 17 2021
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.
Mar 16 2021
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
Mar 15 2021
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.
Mar 12 2021
Mar 11 2021
Mar 9 2021
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.
Good points.
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?
Mar 8 2021
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.
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;