I tried many things and couldn't reproduce this issue - please file a new one in case the problem persists.

Logo changed to the simple text version - it looks weird though:

You can maybe resolve this by running sudo apt install base-files=10.1pureos1, but if this one package was upgraded for some reason, chances are that there are multiple other ones that also have wrong versions, making any bug happening on that system not a PureOS issue - so maybe a reinstallation is a safer bet.

Yeah, this PureOS has been messed with... How did you manage to install a base-files package from Trisquel?

This is impossible, something has severely messed up your system. What is the output of apt-cache policy base-files as well as cat /etc/apt/sources.list ; cat /etc/apt/sources.list.d/*?

.tar.bz2 files are not installable packages, they are just compressed archives like .zip/.tar.gz/.tar.xz files. They are to be uncompressed with an Archive Manager, and can't be installed with a tool like GNOME Software.

The pure-text logo will look really bad as window and toolbar icon, but I can use it anyway.
Thanks for updating the link!

This is fixed in calamares >= 3.2~rc3-0pureos2 now, but will also require a rebuild of the live images to be in full effect.
For some reason, Calamares doesn't create a swap partition right now, I am currently investigating that behavior (and playing with the idea of using swapfiles instead of swap partitions).
Once that issue is dealt with, I will build new live ISO images.

Does the update really fail (as in apt showing an error), or does it not boot, or what exactly happens here?
Packages being held back in landing is normal for that suite.

A logo - any logo - would be nice by this point, since Calamares will be our default installer soon (the link above is no longer working).

I made this work now, but there is a bunch of other changes I would like to do first, still.
(Like installing on an unencrypted /boot by default)

Checking reverse dependencies...
# Broken Build-Depends:
pinto: cpanminus (>= 1.6916)

Dropping pinto as well.

You surely want a way to open compressed zip/tar.gz/tar.xz etc. archives in the default install.

The package went through NEW after I synchronized it with Debian, which leads to this situation now:
INFO: Can not sync povray: Target version '1:3.7.0.4-2pureos1' is newer/equal than source version '1:3.7.0.4-2'.
So, we can only properly sync this with Debian when the Debian version is newer (the archive will not allow downgrades).

Done

This is fixed in the 2018-01-18 live ISO images from today :-)

Oh? GNOME Software should register for the deb package mimetype... So, I wonder what went wrong there...

The package is in green now, please watch out for any issues.

Apparently it breaks a bunch of stuff (garmin-plugin etc.), but that looks like a false-positive to me. The real issues are the -dbg packages being seemingly broken due to the Firefox package taking over binaries from the existing PureBrowser package.
I'll enforce that migration manually.
http://master.pureos.net/migration/landing/green/excuses/firefox-esr/52.5.0esr-1pureos2

If users install PureBrowser after uninstalling it or on flavors where it was not installed by default, they will not get the privacy addons that come with it. Also, these addons are logically tied to PureBrowser, and not to the flavor metapackage, because it's PureBrowser that includes them, not the OS. Furthermore, having them in the flavor package means that they might get installed with PureBrowser or might not get removed when someone uninstalls the purebrowser package.

Relevant metadata package link: https://anonscm.debian.org/git/collab-maint/webapps-metainfo.git

This is pretty much all done already, we are just blocking on some bug fixes needed in GNOME Software.
I thought I would quickly do that when the ftp-masters enabled AppStream on the Debian repo again so I could test the whole pipeline, but they seem to be ignoring me[1] :P

This is resolved now - thanks for the hint!

GRUB is in fastboot mode, so you should only see it when the install fails. And if you see it, it should have no branding at all :-)

It will pull in Qt though, and GNOME doesn't support applets/system tray icons natively anymore.
So, can we add it? Yes, of course, but it will look very alien, and we will have to modify our GNOME Shell session to display status icons.

Could you please try this again with a recent PureOS image? The live installer has been updated several times.
Did you do a custom installation of the OS, or did you use one of the default options?

Yes, but this is a "default in PureBrowser" task, so it actually belongs to the person maintaining purebrowser in PureOS (which is the package that should depend on the appropriate extensions, or recommend them).

Resolved, all future images will include a timestamp of the date when they were built.

@chris.lamb Hmm... There is no "precendence" system, both apps should show up in the software center with a .desktop file like this (although we potentially should do something about OnlyShowIn apps that only list one DE).
On PureOS, we don't export the AppStream generator hints anywhere unfortunatey, a fact that I should change. Debian, however, does export hints, and there you can see https://appstream.debian.org/sid/main/issues/gdebi.html - the icon "gnome-mime-application-x-deb" isn't found. This is maybe related to that icon being a mimetype icon (it's technically legal by the XDG icon spec to load mime icons for apps, and the AppStream generator honors that, but from an UI standpoint I think it's a terrible idea to make an app assume the icon of a filetype - maybe our generator should actually stop that practice).

Resolved in the 2018-01-06 images.

Hmm, the November image should work (from 2017-11-11) and only the December images should have this issue... But maybe I overlooked something there.
This issue should be resolved soon.

I actually warned about this issue, so people would not link to the December image from our download page, as I haven't had the time to fix the problem during that month...
Oh well...

This one was uploaded *after* I reverted the previous changes. Now I can't do that anymore without a fake upload, since the PureOS version is newer than in Debian.

@jonas.smedegaard I would actually prefer that PureBrowser recommends the extensions we want to ship with it - it would make logical sense for the browser package to pull in the extensions we recommend, instead of the system's seed depending on those directly.
By having PureBrowser just recommend the package, users can still easily uninstall it later.

Whoops, I forgot to close this...
The package has been force-synced with Debian and is now tracking Debian Testing again.

@jonas.smedegaard Those are the issues I resolve with pleasure.
The last thing we need is bullshit divergences.

Done

https://appstream.debian.org/sid/main/issues/linphone.html (same issue on PureOS for sure).

Package systemd resynchronized with Debian.

INFO: Imported 'systemd_235-2.dsc' to 'landing/main'.
INFO: Imported 'libudev-dev_235-2_amd64.deb libnss-myhostname_235-2_amd64.deb libpam-systemd_235-2_amd64.deb libnss-resolve_235-2_amd64.deb libnss-mymachines_235-2_amd64.deb libsystemd-dev_235-2_amd64.deb libsystemd0_235-2_amd64.deb libnss-systemd_235-2_amd64.deb libudev1_235-2_amd64.deb libudev1-udeb_235-2_amd64.udeb systemd-sysv_235-2_amd64.deb systemd-coredump_235-2_amd64.deb systemd_235-2_amd64.deb udev_235-2_amd64.deb systemd-container_235-2_amd64.deb systemd-journal-remote_235-2_amd64.deb udev-udeb_235-2_amd64.udeb systemd-tests_235-2_amd64.deb' to 'landing/main'.

@francois Hey, just for clarity: Is this the final PureOS logo for a while? Or will you make a new logo in time, because in that case I would like to wait for that to become ready.
I heard you were planning for some "eight-like shape", will that happen?
If not, I'll just use the PureOS text logo.

Hmm, not sure what went wrong there - please ping me again if the error happens again, in that case I need to run the webservice in verbose mode to catch a bit more output on errors.

So... What did you try? Is there still an issue at all?
Not root filesystem could mean the OEM installation didn't happen. When the OEM installer asks you whether it should automatically determine the fastest disk, what did you answer?

@ah_purism From the logs Zlatan sent me it looks like this is indeed the case. The SquashFS filesystem on the source disk is damaged. This can happen because of a defective download, or because your USB stick is at the end of its life.
Can you download the ISO image again, verify its checksum and then try it maybe with one other USB stick, to rule out defective hardware?

I know about this, fixing it is already on my todo list.

I don't understand BOINC well enough to say how exactly the distributed code gets fed into the system, only (believe that I) understand that it does happen and that we cannot ensure that code fed into the system is freely licensed.

@jonas.smedegaard I can not block binary packages, it's either all or nothing. You will need to edit the package in PureOS, removing the problematic pieces.
Only syncing a few binary packages leads to an inconsistent archive with big headaches for QA, and if we later rebuild all packages from scratch becomes completely impossible.
So, adding a PureOS delta is the way to go here.

Closing this one, in case you experience a similar issue again, please file a new bug.

This has been blacklisted for ages now :-)

This has been resolved in https://github.com/lkorigin/laniakea/commit/5b5745da84fdf55e80f1829626daf01543380d38
The list of blacklisted packages is now visible at http://master.pureos.net/synchrotron/blacklist

This will require changes in Laniakea, which is currently stuck in a PostgreSQL transition. It has been on my todo list already though to revise the synchronization process.
The likeliest chance is that these issues are from an older, broken sync (the more annoying option would be that this is an issue that still exists).
In any case, it's quite high up on the task list (I was aware of the general issue so far, but didn't know that it affected so many packages).

I knew about this, it just didn't have a very hight priority yet due to the focus being on the OEM install (it's on my todo list now though).

This actually looks like the decryption worked okay and LVM is good.
Did you get this message *after* you entered your password to decrypt the device?

Since you apparently are using a fully encrypted disk, it would mean that any data would be lost when you reinstall.

Do not use Bleachbit - ever. See https://blog.martin-graesslin.com/blog/2012/07/do-not-use-bleachbit/
I can look into this later this week, to maybe figure out what's wrong, but if you can, reinstalling the OS is probably the best idea.

How did you install PureOS?

Nothing has changed though - everything is exactly like it was on this front.

Jup ;-)
We are 3 kernel versions in the future now.