Done, the suites are now always ordered alphabetically.

I understand, my comment was meant to be, er, self-answering or something.

(I think I'm misparsing, we can get both with the above!)

User-friendly or paranoid? Why not both? Sounds great :D

Assigning to @mak , at least to start off :)

Thanks for your input :)

Is it possible to just make the name friendlier? Perhaps name it on installation ($SYSTEMNAME-disk) or display it like a credit card: "disk ending -1234".

I could have sworn I fixed that already...
Should be rather trivial to address, in any case :-)

Thanks for addressing this problem so quickly!

In T422#7589, @Wayne wrote:

There are now two threads in the Purism forum regarding these issues. In this post:
https://forums.puri.sm/t/new-librem-13v3-won-t-boot-to-disk-login/3064/10?u=wayne

https://gist.github.com/lamby/e45c7a221defe75db026ee529d00c789/raw

I have Librem13v2 with *UK* keyboard.

@chris.lamb Jup, in fact, the arm64 package was already there when I looked at it. See http://software.pureos.net/builds/package/eb2f2109-0755-5fc0-b32f-ad5c5274a56c/1/ for its build logs.

Thanks @mak !

@mak Ah, so we would have (eventually) got an arm64 package (and then it would have migrated) - we would have just have had to wait?

As a side note, I am now a happy user of "GNOME Packages", which does work in Wayland.

@chris.lamb Be patient ;-) Migrating a completely new package taes at least two dinstall runs, so a few hours was just not enough time ^^
@d3vid The website takes a few minutes to update after a new package has been published, so you might have caight the new package immediately after it was migrated, but before it was actually registered in the database as being in green as well.

Just got these changes from an apt updated and rebooted. Works like a charm, thanks!

This package has arrived in green (got it via apt even though http://software.pureos.net/package/source/green/fontconfig still lists -4).

@d3vid That is a blocker, but I adjusted the code again to ignore the arm64 architecture - we don't have enough build power at time to ensure that we can build every single package on arm64 (although in this case, plymouth built without problems).

http://software.pureos.net/package/source/landing/plymouth migration excuses currently list:

Thanks for reporting - this is an (older) duplicate of T433; see there for the current status.

It's in landing now at least. Curious why it hasn't actually migrated given that the excuses mention that the priority was elevated?

Unfortunately a few hours on http://software.pureos.net/package/source/landing/fontconfig is not showing -5 as being in landing or green. There is no reason why it shouldn't migrate if -4 is already there (no change of dependencies AFAICT). Can you help?

Done, if the package can migrate, it should migrate instantly.
Its status can be monitored at http://software.pureos.net/package/source/landing/fontconfig

Would that be because it is not yet in buster?

In T434#7672, @mak wrote:

The system doesn't seem to know that revision yet, I'll bump the packages urgency in advance.

The system doesn't seem to know that revision yet, I'll bump the packages urgency in advance.

This is fixed if you have plymouth-themes 0.9.3-3pureos1 (just uploaded) and fontconfig 2.13.0-5 (see T434 - needs fast-migrating into green).

re-closing this issue for now

Not related to T429a after all I think. I think I have a fix, just need to get back to my Librem machine to test.

Ah, wait, it *is* an unrelated issue: https://bugs.debian.org/897572

Or is this an entirely unrelated issue? Could do with some guidance here :)

Unfortunately, neither the udev rule nor the "setkeycodes 56 43" works for me. Any ideas?

I think it doesn't matter what keys you hit (as long as you press something) it will eventually timeout to some degree.

Re-opening. I just installed plymouth from green and it still has this behaviour.

https://github.com/systemd/systemd/pull/7826 is in our systemd

So, I can reproduce this. ctrl-alt-f2 actually seems to work for me (in the sense that it restores the gui prompt)

@chris.lamb Thanks for the suggestion. I tried only Alt-F2 and it works no better (or worse) than button mashing without it.

@d3vid Can you try Alt-F2?

1. Rough starting point (comments welcome)

I downloaded the iso normally and pressed live (first option) and gave it.

How did you get to the Debian installer in that version? Because that is no longer a supported option to installing PureOS.

but, it was this version (2018-04-26) that I used and gave error.

You are using an old installer image, please use an up-to-date one like https://downloads.pureos.net/live/gnome/2018-04-26/ for installing PureOS.

There are now two threads in the Purism forum regarding these issues. In this post:

Going back, I did notice something that might be interesting. On the first reboot after the update, vt.handoff=7 is missing.

This was not fixed in the above due to https://bugs.debian.org/898511 ("git repository missing latest 0.9.3-2 upload")

Fixed in https://code.puri.sm/pureos/plymouth/commit/c6c31458c6e485c559c1757efbd6187a132f4a60 (uploaded as plymouth_0.9.3-1pureos1_amd64.changes)

wellton reminded me....The 5/9 update was the upgrade to linux-image-4.16.0-1 pkg. I failed to explicitly mention that.

Same problem here. My kernel is 4.16.8-gnu