Forked debian-junior and debian-games now released.

Indeed license is considered "too vague" by FSF.
Since Debian evidently tolerates it, our only option is to block it.

I guess what Parabola and Trisquel consider an issue is this comment:

Fixed since Debian release 2.4-3 in 2010.

Parabola build routines declares individual docx source files as additional sources in its rpms metadata.

This bug is bogus: Parabola patch do not avoid any promotion of non-free stuff, only refences to Free stuff by (arguably non-free trademark-protected) labels.

another update: Newer USB fixed the order with two drives: m.2 250gb sata and 2.5" 250gb sata drive

So i decided to install using another new USB, with the newest OEM (9/4/2017) installed

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.

i usually type y on the heuristics.

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?

"no root filesystem is defined" on an a BIWIN 128 gb SSD sata 2.5"

i made a mistake.

Patches have been cleaned up and pushed to gerrit.

"no root filesystem is defined" on an Order with two drives: Nvme m.2 1 tb SSD and Samsung 850 evo 1 tb sata.

Done by @MrChromebox

Fixed by @MrChromebox via FSP2 SATA speed limit option.

Done by @MrChromebox and to be merged upstream soon.

Done, and tested.

While true that smtube _can_ use tonvid.com, Debian distribution of smtube does not.

bogusly forked fromT61: It is tonvid.com (not smtube itslef) that tracks users.

its the usb(s) that are having the issues loading purism OEM install. Problem Resolved with new USBs.

@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 tried installing using the same OEM installation. i get this error. I will send through my whatsapp account. It might be the download may be corrupted?

upload failure

press back or escape button and you should have an option to access the shell/logs

how would i check the access logs

@mak @kakaroto can we test this somehow? Also @ah_purism can you attach images as well and check if you have access to logs?

Should i wait for a new coreboot/oem install or should i use the older version that i know would work?

On the 15 inch Purism Laptops. Have not tried 13 inch.

Current status:

I dput'ed last night a fork of Debian kodi, stripped of the kodi-repository-kodi binary package.

for the record: