Higher-than-Debian version shadows a Debian package if both are available. That is suitable for packages deliberately deviating from its Debian counterpart.
Example: debian-games (we fix an FSF-specific freedom-issue)

superceded by T938

The problem tracked in this issue is that you can install non-free packages or add non-free repos - including skype and others.
Which packages can most easily be installed due to the default configuration of the tool is a subset of this general issue.

seems I was mistaken: Matthias explained today that "whatever works, as long as the string "pureos" with a version number suffix appears in there".

Thanks!

https://software.pureos.net/package/bin/byzantium/libglib2.0-0 currently says "This package is currently not installable!"

Please note that this issue is about whether or not a package in PureOS is violating policies defined by Debian and/or FSF.

@jeremiah.foster I am not sure but I don't think Yamane-san is hanging out on irc

core part of OpenQA is already in Debian: https://tracker.debian.org/pkg/os-autoinst

Upstream bugreport: https://bugs.debian.org/908947

There are many, many, MANY ways you can break your system, by changing how its configuration to behave differently from what it did when initially installed.

Yes, unrar-free recommends unar.

Thanks for reporting this issue.

@mak Please block pipx from entering PureOS.

The package telegram-desktop is Free software, and its ties to commercial rtworked services does not affect PureOS compliance as a GNU Free Software Distribution.

I see no reason for blocking MAME from PureOS.

If this issue still persist, then it is too complex to solve. Sorry for the annoyance.

Assuming this was a glitch in the matrix.

The cause of this issue is likely either that your PureBrowser profile is corrupted or that it contains data only readable by Firefox 68.x not 60.x which PureBrowser is no reverted to.

ah right - using the command-line option --ProfileManager provides for a more user-friendly interaction than directly renaming the profile dir. Thanks for mentioning that, @marcus, I'll keep than in mind for future guidance.

I don't know what happened concretely in your case. Perhaps the versions you read was simply _available_ versions instead of _installed_ ones?

Those are all _newer_ releases of the addons than provided by PureOS.

Is this perhaps a duplicate (and revisit) of T148 and/or T711? - symptoms seem similar.

Thanks for that additional info, @mladen

Hi @marcus - thank for reporting this issue.

Thanks for elaborating.

PureOS has reverted to PureBrowser based on Firefox 60.x so this bug is fixed (for now...).

PureOS has reverted to PureBrowser based on Firefox 60.x so this bug is fixed (for now...).

@emmes your attached notes seem to indicate that this has been an issue for quite a while - when did you first experience this issue?

@emmes why did you attach a text file, not post directly the text?!?

@joao.azevedo Please file a separate issue about loss of profile (because that is clearly a different issue from being told here as a debugging aid to rename a profile folder).

@Squid Thanks for the added details.

I sure hope that it was our messing directly with the configfiles (as per my instructions) that caused that - and that package downgrade does *not* cause any such surprises!

PureBrowser downgraded to 60.x, again fixing this issue.

Thanks, that's quite helpful @richard.kolla !

PureBrowser is now downgraded to 60.x in PureOS amber.

@joao.azevedo Can I ask you to please confirm that PureBrowser as of today fixes tis issue, specifically?

Hi @tbernard - sorry I didn't ask back when this was reported which versions of PureBrowser and Ublock Origin you were using.

Thanks a ot for confirming!

...actually: @joao.azevedo please try update your system and tell me if this is still an issue on PureOS amber as of today?

Thanks for reporting this.

Which version of PureBrowser is this? See also T823

As for user notification, I suggest borrowing from how needrestart does it: Provide a purpose-specific GUI as a separate binary package, and have core package suggest either that or libnotify-bin, where the latter spews simpler notifications.

It might be documented, but since I am lousy at reading documentation here's how I'd figure it out:

please describe in *words* what is the issue reported.

To test, try install debian-security-support and afterwards binutils.

@d3vid Interesting idea. We might use a similar approach as Debian package debian-security-support.

This issue is not about feature updates or enhancements.

Fixing this awaits Debian package maintainers for firefox-esr to release their git sources for the newest bugfix release firefox-esr 60.9.0esr-1~deb10u1

Either this is a needless duplicate of T814 or it is a call to leadership about special-treating T814. In either case my participation is irrelevant.

@joao.azevedo Could you please test if installing uBlock Origin package from Debian testing on top of an up-to-date (and clean, no Mozilla or other non-PureOS-origin code added) PureOS amber install fixes this issue?

Thanks for your details about PureOS.

@emmes Which version did you install from PureOS Amber? Info should be available in /var/log/dpkg.log even if you since removed it again.

Thanks for your additional info, @emmes

@joao.azevedo Yes, that could quite likely be same issue as this one!

@EchedeyLR I agree that this issue is an issue for PureOS. It is not a freedom issue however: That tag has a specific definition tied to https://www.gnu.org/distros/free-system-distribution-guidelines.html (if you think the definition should be changed then please discuss that with the GNU project).

@Badger Thanks for the suggestions. Please, however, file those as separate issues (i.e. wishlist requests).

I don't recognize this as a freedom issue - care to elaborate, @EchedeyLR ?

Ok, then I am closing this. If someone comes up with a reason current behaviour here is basd, we can reopen.

I agree that Firefox Sync is enabled. I believe it has been enabled for quite some time.

Please do open separate issue reports for each of those other issues.

no no, as I tried to communicate, the provided info is appreciated.

It is helpful if you can try distinguish stories that involve wandering off of PureOS and (re)installing things from elsewhere, from stories about solely using software provided as part of PureOS.

Thanks for the details.

@richard.kolla I made a typo in the first test - please try this:

@richard.kolla Thanks for testing!

but already, getting fixed by only (?) removing and reinstalling the addon indicates that this is a bug in the addon rather than Firefox trying to suppress it (e.g. due to that new Mozilla content blocker perhaps conflicting with it).

@joao.azevedo thanks - what is probably more interesting is what you did in-between: Did you start PureBrowser while the addon was removed? Or did you have PureBrowser running while removing and reinstalling the addon?

This might be related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931640

Arguably, PureBrowser no longer blocks advertisements, as tracked specifically in T814.

Thanks for the clarification.