I'll inquire with MLS to see how we get a key.

Are we trying to get an API key from Mozilla Location Services?

What are we trying to achieve?

I don't know if we have a formal policy around the Mozilla location services though I don't think we should be using Debian's. I think we need to create a policy or at least have a process to do so.

https://tracker.pureos.net/w/development/packaging_overview/#mandatory-debian-control-file Please review.

Good points.

I made the changes to the debian/control file (maintainer email address, VCS-*) mandatory.

Done: https://tracker.pureos.net/w/development/packaging_overview/

I can confirm this;

I did two runs of 1000 calls to the server and did not see any anomalies.

This is a good idea @guido, thanks for logging this. Package reproducibility is easy to test with reprotest, I'll check with @mak to see where we can include this.

https://tracker.pureos.net/w/development/synchrotron/

Phabricator's API is called conduit. I can pull data from conduit and it looks like this;

I think "blobs" is tricky terminology which might confuse - it confuses me. I prefer talking about 'firmware'. Firmware is stored in Read Only Memory (ROM) as a binary. It usually cannot be changed and it just meant to make the hardware work at all. The FSF says "Firmware that is installed during use is software; firmware that is delivered inside the device and can't be changed is software by nature, but we can treat it as if it were a circuit." This makes firmware closer, or even the same as, hardware. And while all hardware should have free designs, like Purism's, we don't have to reject non-free hardware the way we have to reject non-free software according to the FSF.

Do we need or want a channel from Gitlab to Matrix too?

Is this a Tracker <--> Matrix channel? We already have #dev/pureos-changes so you don't mean that channel I assume.

I've been informed that it is at least *theoretically* possible to point snapd to a only free "store" https://forum.snapcraft.io/t/external-repositories/1760/7
This might help us not have to remove snapd and then patch and maintain all the software that depends on snap and snapd.

Might be cool to put that documentation here: https://tracker.pureos.net/w/development/

nginx error log on Artemis is saying:

Get:289 https://repo.pureos.net/pureos byzantium/main arm64 xdg-user-dirs arm64 0.17-2 [53.2 kB]
E: Failed to fetch https://repo.pureos.net/pureos/pool/main/c/chardet/python3-chardet_4.0.0-1_all.deb Error reading from server - read (5: Input/output error) [IP: 138.201.228.45 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Fetched 94.6 MB in 9s (10.1 MB/s)

@guido - have you seen this issue?

This should be fixed in later versions.

Similar issue:

The idea of "shadowing" upstream or downstream as the case may be seems pretty useful though my brain is more accustomed to having the PureOS version of a package be higher.

AppStream is more for app meta-data while apt-file basically searches a directory of ASCII text to find specific files inside packages. I'm not sure if you could use AppStream as an apt-file replacement.

If this is an issue with Thunderbird, it should be filed upstream

Thanks Sebastian! Let's find another package @alvesadrian

In T978#17857, @mak wrote:

the issue is the "Software & Updates > Updates > Automatically check for updates: Never" configuration is not preventing the system from automatically checking for updates every day.

they have to do that *and* disable updates in GNOME: "GNOME Software" > "Burger Menu" > "Update Preferences" > Toggle Automatic Updates
(as shown in the image I posted above)

The Original Poster is stating that their use case is customers at sea who have expensive connection charges which require they disable unnecessary network communication.

The user writes back saying that they disabled GNOME Software and was unable to stop automatic upgrades. There is no effect of the GNOME Software settings observed. I think the next step on my side is to run strace on GNOME Software and settings to see what is happening (or not happening).

It appears that one *cannot* shut off updates with GNOME Software despite the settings that would imply that this is possible. What needs to be address is apt-daily-upgrade.timer. systemctl status apt-daily-upgrade.timer says;

● apt-daily-upgrade.timer - Daily apt upgrade and clean activities
     Loaded: loaded (/lib/systemd/system/apt-daily-upgrade.timer; enabled; vendor preset: enabled)
     Active: active (waiting) since Fri 2020-12-11 10:07:48 EST; 2 weeks 5 days ago
    Trigger: Thu 2020-12-31 06:28:21 EST; 10h left
   Triggers: ● apt-daily-upgrade.service

This can be disabled which ought to turn off automatic updates. Stop the timer and disable this way;

sudo systemctl stop apt-daily-upgrade.timer
sudo systemctl disable apt-daily-upgrade.timer

The plan that was devised consists of two steps;

@jonas.smedegaard Did a user report this? Or is this bug from your own sleuthing? :-) I ask because sometimes the FSF rewards users who report freedom issues with GNU Bucks and there may be some at stake for reporting.

Glad you tracked down the issue! Nice sleuthing!