Works :)

I will look into this.

Everything works now :-)

purebrowser might need to provide firefox-esr and iceweasel as virtual packages...

That request to add another repository is something I have also seen every once in a while a few months ago - I think it's an upstream bug.
Let's see if that happens again when this issue is resolved.

This should be fixed automatically in a few hours when the archive files have been regenerated.

@todd Hmm, that's not much information... But it's pretty safe to say that grsec prevents some action executed by the polkit daemon or frontend service which leads to a successful grant of permissions.

Why is the source "none" - that does not make sense.
I guess some label is set incorrectly in appstream-generator or dak.

From my tests, it is grsec related. We will need to dig deeper into this before we put grsec as default.

Please run sudo journalctl -f in a separate terminal while trying to perform the privileged action, and paste the output here. That might give us a hint on what is going on.

I can't reproduce this issue here, might be related to running a grsec kernel.
I'll try with that in an hour (and I also have a couple of other ideas, but grsec being the problem seems likely).

Hmm... Is policykit-1-gnome and policykit-1 installed? I'll have to look into that...

I tried both of these:

This should be resolved with the last GS upload.
Will come back every time GS is updated in Debian until we rebuild packages for PureOS (but I'll keep an eye on it).

This should be resolved with the last GS upload.
Will come back every time GS is updated in Debian until we rebuild packages for PureOS (but I'll keep an eye on it).

Adding /usr/bin/epiphany-browser to paxctld doesn't solve this?

This needs to be solved within PureBrowser package (which @hema.prathaban will take care) as Iceweasel shouldn't be part of our archive (I already explained this to Hema day or two ago).

I could install it from command prompt:

All steps completed successfully while running LibreJS (on Firefox 51.0.1 / Ubuntu 16.10). This indicates it should be successful on (for example) IceCat / GuixSD or PureBrowser / PureOS.

Adding a comment. (And resolving.)

Currently there is no free driver for Atheros bluetooth. We consider this work-in-progress.

Also, the package python-dev cannot be installed from green :

To solve this we will need to get rid of any dependency on the desktop-base package of the PureOS default packages - as I recall from Tanglu, this required touching quite a few packages.
Btw, the bootloader should not be shown at all on bootup, and only if the previous boot was interrupted or shift is pressed while booting up or another non-PureOS OS is installed.

Thanks mak!

This is done now, but appstream.po.n isn't yet reachable via HTTP(S), so screenshots will not show up until the server is serving them.
But at least all software centers should contain stuff now :-)

For the final release the current plan is to actually go with Calamares of default installer instead of Debina Installer.

This is because we need appstream metadata and we are preparing that machine so it will be done for final release (probably for next image which will be tagged as beta) :)

@mak proxmox has the nasty habit of messing up all the keys excpet the first one. Can you try now?

@theodotos.andreou Looks like by SSH public key isn't registered with the root account (I can't log in at master.po.n)

@theodotos.andreou Excellent! I will need to think a bit about how to send data there properly while we do not yet have a database server storing it (will likely be just a data-upload from the dak machine).
I hope I can do that on Sunday, if not then hopefully next week.

@mak It seems I was overreacting about Dreamhost :)

@mak 1 CPU, 4096MB RAM, 16GB storage. Let me know if we need more.

I am trying to switch the nameserver and glue records of pureos.net to ns1 and ns2.puri.sm. It's not very clear how to do that. I opened a ticket. Todd can you please forward to me any reply from their support?

For now, I will have it serve just static data - when I go forward with the QA web app, it will likely be based on Vibe.d or Flask, and at least the former is pretty low on CPU (it uses almost zero system resources if not in use, but can grow quite RAM-heavy if you cache stuff there).

@mak. I will create an LXC container for this. Any idea on specs (CPU, RAM, Storage)?