Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Shreyas Minocha
@shreyasminocha
which is actually pretty interesting, but apparently "Since version 1.5 of the protocol, a Firefox Account is required in order to use the synchronization service."?
if it's possible to run a sync server without getting in bed with FF, we could definitely relax some of the sync settings (maybe change them from lockPref to defaultPref)
yeah and apparently the sync server tech is open source
Shreyas Minocha
@shreyasminocha
also apparently sync data is encrypted in the browser, which is a good sign. depending on your threat model you may choose to use the ff sync server itself
in any case i think a loosening of sync-related settings is in order
Shreyas Minocha
@shreyasminocha
we'll have to check if those introduce other issues though
Shreyas Minocha
@shreyasminocha
in other news, we've been getting some attention on the fediverse
so that's cool.
Carlos Santos Armendariz
@csarmendariz_gitlab
Hi there, thanks a lot for working on this, it looks really useful :)
I downloaded the appimage, but after changing the permissions, if I try to execute it, it just do nothing
I thought of asking here in case someone has a quick explanation of why this could happen
I'm using a pretty old ubuntu Mate 16.04
I guess I could try the flatpak but I thought of asking first, I prefer the appimage if possible
Christian Hofmann
@ohfp_gitlab

Hm, no quick explanation at least.

Do you get any kind of output or error message when you launch the appimage from the terminal?

We intentionally build the AppImage and the Flatpak releases on Ubuntu 16.04/Xenial, to ensure it runs on (even relatively ancient but) still supported Ubuntu versions, so at least that shouldn't be the cause.

FlailAway
@FlailAway
[80] DRM and Save password are grayed out. How can I change those?
Christian Hofmann
@ohfp_gitlab
those are locked in the librewolf.cfg – if you want to use / change those settings, you need to edit /usr/lib/librewolf/librewolf.cfg directly (more complex if using appimage or flatpak, I think); the settings to look for should be browser.safebrowsing.passwords.enabled and media.eme.enabled; changing lockPref to defaultPref for them.
(I might be wrong about the password setting, will look it up and get back to you)
Christian Hofmann
@ohfp_gitlab
yep, it's probably signon.rememberSignons and/or signon.storeSignons.
periish
@periish
Hi! I was wanting to package LibreWolf for my distribution
However, I’ve noticed there aren’t really many options to do so :<
The build system is quite a mess(I can’t figure it out!), and it’s not exactly viable to use Flatpaks nor AppImages.
periish
@periish
(It’s a musl distribution, so AppImages are out of the question)
Christian Hofmann
@ohfp_gitlab

Hm, I've been wanting to to clean up the build scripts (and build documentation) for a while now; I might just do that then ^^

Which distro is it? At least with alpine, things should be relatively simple to adapt, as APKBUILDs are quite similar to PKGBUILDs.

Besides that, there's probably not much to use for musl-based systems directly; the build scripts are mainly there to build a debian/ubuntu-based tarball to allow backwards-compatibility to ancient-ish debian/ubuntu distributions and libraries, as that's what is needed to build the appimage and flatpak releases. Then there's the PKGBUILD to build a release for Arch-based systems.
I'd assume neither of those would output binaries that could be properly used with musl, so one would probably have to get this done with a new, separate build process.
periish
@periish
My distributuon is KISS Linux! It’s quite a rare one, so I wouldn’t want to weigh you down with the build system.
I do wonder if you could create a build that can output source tarballs akin to plain firefox’s, as that’s what our build system requires.
Internet access isn’t allowed during the build process for base system packages, for reproducibility reasons.
periish
@periish
(My wording above is confusing. Dylanaraps maintains KISS, I simply package things)
(Here’s the website, https://k1ss.org; and a page on the build system, https://k1ss.org/package-system)
We shouldn’t have to worry about patches for musl, ALSA, or dbus removal support. Firefox has this all upstream.
Christian Hofmann
@ohfp_gitlab

Interesting distro ^^

Is internet access available when pulling the required sources, or would those have to be available locally beforehand?
Looking at the package system, it seems like it should be easiest to start from the PKGBUILD, as the KISS build system also seems to pretty much "just a script" – so we could either pull in all the sources directly as well, or provide them offline with just a few changes.

periish
@periish
Internet access is allowed for pulling the sources, yes. The sources are iterated through and downloaded into the cache, and are then extracted into the build dir. Nothing is actually done to enforce this; it’s a nicety, akin to how all dependencies are alphabetically ordered.
All go software in the community repo accesses the internet, as an example.
periish
@periish
I’m curious as to what the remove_addons patch does.
Christian Hofmann
@ohfp_gitlab
In that case: If you want to give it a spin, you could just pick up the https://gitlab.com/librewolf-community/browser/linux/-/blob/master/PKGBUILD; get the few patches/files that are part of the repo separately (megabar.patch, remove_addons.patch and the librewolf.desktop, for x86_64 at least) directly and follow allong. prepare, build and package are just functions executed in that order, and the only other specialty is that some variables (
periish
@periish
I’m a bit rusty on my bashisms.
Does the += on _cert_sed create an array?
I’ll report back on the results in a few days. Currently away from my computer; and I want to hold off on compiling rust until I make progress in other projects.
Christian Hofmann
@ohfp_gitlab

$CARCH (architecture: aarch64, x86_64 etc), $pkgdir and $srcdir (pkgdir is the "output directory" that gets packaged; srcdir is the working directory, where the sources are).

nope, just extends the string in the variable, instead of other ways to avoid having one looooong line ^^

the remove_addons.patchremoves some addons which might be undesired / be used to collect data, by not having them built and removing some code referencing them.
No rush – hope things work, and I'd be happy to help if you get stuck somewhere ^^
periish
@periish
Ah! Thanks for the help
matrixbot
@matrixbot
@anonymous_zero:matrix.org was kicked by Telegram Bridge ("This chat does not have a bot relaying messages for unauthenticated users.").
matrixbot
@matrixbot
@nunbit:converser.eu was kicked by Telegram Bridge ("This chat does not have a bot relaying messages for unauthenticated users.").
onny
@onny_gitlab
Hey, in case you're interested, I packaged the AppImage version of LibreWolf for NixOS https://git.project-insanity.org/onny/nur-packages/-/blob/master/pkgs/librewolf-bin/default.nix Feel free to ask if you need some instructions
matrixbot
@matrixbot
@fbiiskgb:matrix.org was kicked by Telegram Bridge ("This chat does not have a bot relaying messages for unauthenticated users.").
matrixbot
@matrixbot
@freenode_Hund:matrix.org was kicked by Telegram Bridge ("This chat does not have a bot relaying messages for unauthenticated users.").
Hund on Freenode Hi!
@freenode_Hund:matrix.org was kicked by Telegram Bridge ("This chat does not have a bot relaying messages for unauthenticated users.").
Christian Hofmann
@ohfp_gitlab
Just a quick note: I'll get 81.0 ready asap and will then get to work on the newly opened issues and the whole config-thing. I know I've "promised" that several times now, it's just that time is at a premium at the moment more than I would've thought, so most of the times just getting a new release done is all that I can get done – I hope it won't stay that way! :)