I tried installing the firmware-realtek package and it worked. So it would seem that
my hardware is incompatible with free software. I believe that the game changer was the firmware binary rtl8188eufw.bin and not the driver alone.

Fratal no longer depend indirectly on gnulib.

Thank you for clarifying the nature of this issue. Title and priority adjusted accordingly.

I used the nextcloud repository because the application was not present in those of pureos.

PureOS avoid code which Debian or the GNU project considers nonfree - despite others (inlcuding kernel developers) having different opinions regarding licensing and the need for sources of code/data/blobs.

PureOS does not contain the web pages of duckduckgo.com but do indeed currently link to that website.

Added: according to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912720 there is a new maintainer who should help to restore the package at Debian

OK, looks like its not maintained anymore (from the issue comments at Debian site). I'll try to bump it as well, thanks for finding the issue. I am not familiar with Debian and wasn't aware of this check.

If you change your system to be a mixture of PureOS and other sources, then your system is no longer a PureOS system.

Please mention which versions of the packages pulseaudio and libasound2-plugins is installed on your system.

Please mention which versions of the packages pulseaudio and libasound2-plugins is installed on your system.

Thanks for reporting this issue!

Originally these choices were made because we were asked to remove the references on the FSF mailinglist to get PureOS endorsed. They also asked us to remove the "non-free" component reference from the APT manual pages.
However, nobody seems to insist on that anymore, and your reasoning makes sense to me, so I will gladly resynchronize this package with Debian.

Revert to track only freedom issue (not the related issue of it not being a freedom issue after all).

Revert to track only freedom issue (not the related issue of it not being a freedom issue after all).

Sad news:

It's on my todo list and will likely be added after the current refactoring is over. The tricky thing here is that Laniakea delegates most archive actions to dak, and I would need to hook into dak to make this feature work properly (which means without email parsing) and integrate it with the generic Laniakea messaging.
This feature will also require our sysadmins to allow bots in some way on our Matrix instance (at the moment, I have no way to actually register a Matrix bot).

Inside it, click on the yellow or orange box to see older changes...

Hi, any update for this? It's been many months and I would still dearly love this feature.

From Matrix discussions, this might affect Bluetooth as well (mentioning also to improve serch terms)

s/removed/reset/

@mak Do I understand correctly that clamav can now be removed without the need for a dummy package?

It appears these new pointers disappear after several minutes.

What's the status on this? The issue of LibreJS is coming up again in general, and I will also be requesting some other addons are either default or opt-in (perhaps with a slide in the first-boot setup wizard for PureOS).

I guess I can confirm this bug.

In T486#11164, @mladen.pejakovic wrote:

Run:
sudo systemd-hwdb update
sudo udevadm trigger
Make sure you don't have any other hack or workaround applied.

I've removed the Purism lines as above from the /lib/udev/hwdb.d/60-keyboard.hwdb and restarted but still getting hash\tilde for the backslash\pipe key.

Is it possible that you are talking about /etc/udev/hwdb.d/? If your /lib/udev/hwdb.d/ is empty: which OS are you using?

indeed there is no file in that directory at all

I received my Librem 13 v2 with UK keyboard today and the pipe key is also mapped to hash\tilde.

@kyle.rankin @mladen.pejakovic

so far we don't have anyone in-house who is able to re-create this specific problem but clearly you are getting some kind of support request that motivated you to file this ticket.

Oh, neat!
Package synced with unstable.
2018-10-25 14:36:49 - INFO: Imported 'xscreensaver_5.40-1.dsc' to 'landing/main'.

more info at https://bugs.debian.org/876087 and T235.

I want TB to be packaged by PureOS and installed by default on PureOS unless there is some Free Software licensing issue that would prevent this (I don't believe there is).

@sean.obrien While that "Flatkill" (what a dumb name...) makes excellently valid points, there's nothing that is a fundamental flaw in Flatpak's design that won't be resolved with better maintenance and more development time. However, that's something that still needs to happen, and when creating something new, you need to start somewhere ;-)
But anyway, it's better to have this discussion at a different place, to not make the discussion on this (syncing) issue overly hard to follow.

@guido

For our CI we can (and will auto upload to purple/laboratory for some stuff but I'm really talking about things we want from other Debian suites not necessarily maintained by us.

This was fixed on 2018-10-15 with Thunar update 1.8.2-1. Debian testing package changelog ( http://metadata.ftp-master.debian.org/changelogs//main/t/thunar/thunar_1.8.2-1_changelog ) reads in part:

In T594#11055, @guido wrote:

@sean.obrien (this might become a bit off topic): the flatpak side needs more work for the 3rd party apps.

@sean.obrien (this might become a bit off topic): the flatpak side needs more work for the 3rd party apps.

@guido got it, thanks! The further we can think down the road the better, so if I can be of any help let me know. I'm not yet sure what else might be necessary / desired by devs for mobile app development.

We have purple and laboratory in PureOS and the CI repos for phone development.

Anything we can do to make developing apps for the Librem phone smoother is really important. Does it make sense at this point to author a strategy / procedures for packages like this? Maybe a separate repo for unstable packages that we want to make available on PureOS as quickly as possible to encourage Librem phone development? I'm still getting my feet wet, so perhaps some of this is worked out already.

Sure let's discuss more (edit: in another medium). I intend to solve the root problem identified by @thegoat above:

Please see the GNOME case above, this is really not tied to our CI.