Pureos rolling release

antonis · April 16, 2020, 7:39am

What I found strange recently was that there was no riot to install on byzantium. I had to install it from the debian package manually. Isn’t that strange?

vmedea · April 18, 2020, 5:49pm

I followed the steps in Pureos rolling release to upgrade to byzantium, but get the following errors during apt full-upgrade:

Err:1 https://repo.puri.sm/pureos byzantium/main amd64 libpango-1.0-0 amd64 1.42.4-8
  404  Not Found [IP: 138.201.228.45 443]
Err:2 https://repo.puri.sm/pureos byzantium/main amd64 libpangoft2-1.0-0 amd64 1.42.4-8
  404  Not Found [IP: 138.201.228.45 443]
Err:3 https://repo.puri.sm/pureos byzantium/main amd64 libpangocairo-1.0-0 amd64 1.42.4-8
  404  Not Found [IP: 138.201.228.45 443]
Err:4 https://repo.puri.sm/pureos byzantium/main amd64 libpangoxft-1.0-0 amd64 1.42.4-8
  404  Not Found [IP: 138.201.228.45 443]
Err:5 https://repo.puri.sm/pureos byzantium/main amd64 gir1.2-pango-1.0 amd64 1.42.4-8
  404  Not Found [IP: 138.201.228.45 443]
Err:6 https://repo.puri.sm/pureos byzantium/main amd64 nautilus amd64 3.36.1-1
  404  Not Found [IP: 138.201.228.45 443]
Err:7 https://repo.puri.sm/pureos byzantium/main amd64 libnautilus-extension1a amd64 3.36.1-1
  404  Not Found [IP: 138.201.228.45 443]
Err:8 https://repo.puri.sm/pureos byzantium/main amd64 nautilus-data all 3.36.1-1
  404  Not Found [IP: 138.201.228.45 443]
Err:9 https://repo.puri.sm/pureos byzantium/main amd64 libsrtp2-1 amd64 2.3.0-3
  404  Not Found [IP: 138.201.228.45 443]
E: Failed to fetch https://repo.puri.sm/pureos/pool/main/p/pango1.0/libpango-1.0-0_1.42.4-8_amd64.deb  404  Not Found [IP: 138.201.228.45 443]
E: Failed to fetch https://repo.puri.sm/pureos/pool/main/p/pango1.0/libpangoft2-1.0-0_1.42.4-8_amd64.deb  404  Not Found [IP: 138.201.228.45 443]
E: Failed to fetch https://repo.puri.sm/pureos/pool/main/p/pango1.0/libpangocairo-1.0-0_1.42.4-8_amd64.deb  404  Not Found [IP: 138.201.228.45 443]
E: Failed to fetch https://repo.puri.sm/pureos/pool/main/p/pango1.0/libpangoxft-1.0-0_1.42.4-8_amd64.deb  404  Not Found [IP: 138.201.228.45 443]
E: Failed to fetch https://repo.puri.sm/pureos/pool/main/p/pango1.0/gir1.2-pango-1.0_1.42.4-8_amd64.deb  404  Not Found [IP: 138.201.228.45 443]
E: Failed to fetch https://repo.puri.sm/pureos/pool/main/n/nautilus/nautilus_3.36.1-1_amd64.deb  404  Not Found [IP: 138.201.228.45 443]
E: Failed to fetch https://repo.puri.sm/pureos/pool/main/n/nautilus/libnautilus-extension1a_3.36.1-1_amd64.deb  404  Not Found [IP: 138.201.228.45 443]
E: Failed to fetch https://repo.puri.sm/pureos/pool/main/n/nautilus/nautilus-data_3.36.1-1_all.deb  404  Not Found [IP: 138.201.228.45 443]
E: Failed to fetch https://repo.puri.sm/pureos/pool/main/libs/libsrtp2/libsrtp2-1_2.3.0-3_amd64.deb  404  Not Found [IP: 138.201.228.45 443]

It can’t continue after that.
~~Anyone have an idea?~~
Edit: solved

uzanto · April 18, 2020, 10:30pm

Looks like if the server was down, try again now or do ping -c1 138.201.228.45 to see if you can reach it.

vmedea · April 19, 2020, 3:52pm

Ping works fine! FWIW it downloaded about 1500 other packages successfully Just not the ones in the error message. It looks like the package versions actually on the server mismatch the ones in the apt metadata.

vmedea · April 23, 2020, 6:04pm

FWIW it looks like this problem was solved, or solved itself. I just re-tried and was successful in upgrading amber to byzantium on my Librem15v4. First experience is that rendering and screen updates feel faster, probably due to the new Mesa graphics drivers.

Linuxnoob · April 25, 2020, 8:17am

Operating system: pureos Byzantium
Problem:
Did an update today and after I turn on my system instead of the login screen I get
Oh no! Something has gone wrong.
A problem has occured and the system can’t recover. Please contact a system administrator.
What I do after that:
•Ctrl+Alt+F2
•login
•sudo startx
• display shows
Oh no! Something has gone wrong.
A problem has occured and the system can’t recover. Please contact a system administrator.
With an option to logout below.
• I click logout.
•The XKEYBOARD keymap compiler (xkbcomp) reports:
Internal error: Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server
xinit: connection to the xserver lost

gusnan · April 25, 2020, 12:42pm

I have the same on a Byzantium machine in Virtualbox. Are you also running your machine in Virtualbox, or is it non-virtual? (I have no solution, sorry).

gusnan · April 25, 2020, 12:53pm

@Linuxnoob I have it even worse in Virtualbox - if I switch to another VT I only get the message

A start job is running for Hold until boot process finishes up (2min 30s / no limit)

So, I cannot even get a login prompt.

Linuxnoob · April 25, 2020, 3:04pm

I am not using a virtual box. I am using it on a desktop.

niceguy · April 25, 2020, 5:54pm

I have the same problem. I hope someone can share a solution soon

uzanto · April 25, 2020, 5:55pm

Gnome 3.36 had broken Debian (testing) a week ago but it was solved in an update next day.
Try to update from the comand line again.

niceguy · April 25, 2020, 6:01pm

I tried updating, but it didn’t help. However, I have 8 packages being kept back:
gir
libnautilus-extension
libpango
libpangocairo
libpangoft
libpangoxft
nautilus
nautilus-data

uzanto · April 25, 2020, 6:05pm

Try sudo apt full-upgrade but don’t do it just take a picture of the output and show it here or write it down.

The problem is that Debian people update some packages to gnome 3.36 but they left some dependencies without updating but I don’t remember wich ones, maybe gir…

niceguy · April 25, 2020, 6:16pm

I get this:

Thanks for your help!

uzanto · April 25, 2020, 6:24pm

If you upgrade like tht you will remove etcher from the system that’s why is not doing it, you can give it a try and hope for the best by I think purism team didn’t fix the broken packages yet.

Anyway it can be fixed using Debian testing repos on your own risk just let me know if you want to and I’ll write down how to do it.

niceguy · April 25, 2020, 6:39pm

I full-upgraded, but unfortunately the problem is still there.
Is it risky to switch to Debian repos? Can (and actually should) I just switch back at a later point? I think I’ll try it, since it’s my only hope at this moment.

uzanto · April 25, 2020, 6:47pm

It’s just upgrade gnome-shell and dependencies from Debian unstable and then remove this repo you will be using pureos byzantium repos after this, I did it from Debian testing to unstable.

Do you know how to add repositories from terminal? I’m on the phone right know and takes a while to type this down.

PS. I just though that Debian testing is fixed now maybe it’s better install that gnome-shell or speak with PureOs team because they should update this packages

niceguy · April 25, 2020, 7:07pm

I don’t know, but I can look for explanations myself later and let you know if I have problems.

Edit:
So I changed the repository to deb http://ftp.debian.org/debian testing main contrib non-free.
Now I can boot and login, but the shell won’t open any software. Nothing will show up. Do I have to update gnome-shell still? Or did I miss something else? Already tried updating and upgrading through Ctrl + Alt + F3, but that didn’t help.

pfm · April 26, 2020, 12:28am

Same problem here. After update i cant get x to start.
Also: i cant log in on the non X side. Have my authentication configured such that it requires a yubikey. The yubikey never lights up.
Typing my password in plain text into the login field to check if the keyboard setup is correct shows me the characters ‘A turn into ~A and an invert exclamation mark. Apologies for the strange typing, but im on my tablet.
Any help would be most appreciated.
By the way: my drive is encrypted with gpg and a librem key, on the recovery shell it asks me for a password and not for the pin, woudl this be my gpg password?

Linuxnoob · April 26, 2020, 12:59am

I think I found the problem
Gnome shell is unable to update in the Byzantium repo
https://software.pureos.net/package/excuses/8390d15e-bf5a-4b6e-8843-be2a876591d5