Arch Linux User Repository

Everyone can now participate in the general package update process! The process is almost entirely automated, these are the necessary steps:

1. Create an MR with your changes to the source repo (the firedragon folder contains the files of this repo)
2. Wait for a maintainer to review and merge it
3. Done! When merging, the PKGBUILD will automatically be deployed to AUR via the CI pipeline.

We are finally there! After being frozen on version 119 and investing quite some time improving the app, Firedragon now has an entirely new base!

Please see the Announcement post:

https://forum.garudalinux.org/t/new-firedragon-major-version-is-out/34585

The build fails when patching in the Librewolf patches section:

---- Librewolf patches - UI
patching file browser/locales/en-US/browser/preferences/preferences.ftl
Hunk #2 succeeded at 420 (offset 9 lines).
Hunk #3 succeeded at 583 (offset 13 lines).
Hunk #4 succeeded at 612 (offset 13 lines).
Hunk #5 succeeded at 656 (offset 4 lines).
patching file browser/components/preferences/privacy.inc.xhtml
Hunk #4 succeeded at 1031 (offset 15 lines).
patching file browser/locales/en-US/browser/preferences/preferences.ftl
Hunk #1 succeeded at 1113 (offset 6 lines).
patching file browser/locales/en-US/browser/browser.ftl
Hunk #1 succeeded at 543 with fuzz 1.
patching file browser/components/preferences/main.inc.xhtml
Hunk #1 succeeded at 679 (offset 14 lines).
patching file browser/components/preferences/preferences.js
Hunk #1 succeeded at 234 with fuzz 1 (offset 73 lines).
patching file browser/components/newtab/lib/AboutPreferences.jsm
patching file browser/locales/en-US/browser/sanitize.ftl
patching file browser/components/preferences/main.inc.xhtml
patching file browser/components/preferences/main.js
patching file browser/components/preferences/privacy.js
patching file toolkit/mozapps/extensions/content/aboutaddons.js
patch unexpectedly ends in middle of line
Hunk #1 succeeded at 1997 with fuzz 1.
patching file .gitlab-ci.yml
patching file browser/components/preferences/jar.mn
patching file browser/components/preferences/librewolf.inc.xhtml
patching file browser/components/preferences/librewolf.js
patching file browser/components/preferences/preferences.js
Hunk #1 succeeded at 8 with fuzz 1.
Hunk #2 succeeded at 192 (offset 74 lines).
patching file browser/components/preferences/preferences.xhtml
Hunk #1 succeeded at 13 (offset 1 line).
Hunk #2 succeeded at 130 (offset 1 line).
Hunk #3 succeeded at 223 (offset 10 lines).
patching file browser/locales/en-US/browser/preferences/preferences.ftl
Hunk #1 succeeded at 1370 (offset 23 lines).
patching file browser/themes/shared/jar.inc.mn
Hunk #1 succeeded at 79 with fuzz 1 (offset -26 lines).
Hunk #2 succeeded at 98 with fuzz 1 (offset -22 lines).
patching file browser/themes/shared/preferences/category-librewolf.svg
patching file browser/themes/shared/preferences/librewolf.css
patching file browser/themes/shared/preferences/preferences.inc.css
Hunk #1 succeeded at 206 (offset 5 lines).
The next patch would create the file browser/themes/shared/preferences/category-librewolf.svg,
which already exists!  Skipping patch.
1 out of 1 hunk ignored
==> ERROR: A failure occurred in prepare().
    Aborting...

The PKGBUILD itself didn't change because the actual change happened in the common repo :)

just pointing out that the PKGBUILD did not change

Sorry for the late answer @prg! The reason is quite simple, in this case a patch (located in the common repo) changed. Likely this corresponding commit.

What's the deal with c8cb6a5a5d63 ? It bumps the pkgrel, but changes nothing. The commit log comment mentions something about changing the svg, but nothing changed...?

As of 96.0.3, the builds reference the $srcdir:

==> Checking for packaging issues...
==> WARNING: Package contains reference to $srcdir
usr/lib/firedragon/libmozavcodec.so
usr/lib/firedragon/omni.ja
usr/lib/firedragon/firedragon
usr/lib/firedragon/plugin-container
usr/lib/firedragon/libxul.so
usr/lib/firedragon/libmozsandbox.so
usr/lib/firedragon/libmozavutil.so

The application works just fine on X. I'm using it myself in fact :)

Is there a way to build this without wayland? I'm pretty sure I'm still dependent on X for a lot of apps I regularly use

Thanks for keeping us updated, I also pushed a patch which simply disables the pip check (taken from Gentoo forum) :)

UPDATE3 (TLDR): firedragon 95.0.2-2 PKGBUILD works for me after removing python-pip from the build system. Thanks for the updates!

Current PKGBUILD doesn't build Looks like line 56 needs to be updated from "firefox-kde.patch" to "mozilla-kde.patch"

sed: can't read /home/user/.cache/yay/firedragon/src/common/patches/kde/firefox-kde.patch: No such file or directory
==> ERROR: A failure occurred in prepare().
    Aborting...

UPDATE: After fixing that, the build fails with pip errors:

Found link https://files.pythonhosted.org/packages/da/f6/c83229dcc3635cdeb51874184241a9508ada15d8baa337a41093fab58011/pip-21.3.1.tar.gz#sha256=fd11ba3d0fdb4c07fbc5ecbba0b1b719809420f25038f8ee3cd913d3faa3033a (from https://pypi.org/simple/pip/) (requires-python:>=3.6), version: 21.3.1
Given no hashes to check 181 links for project 'pip': discarding no candidates
Traceback (most recent call last):
  File "/home/user/.cache/yay/firedragon/src/firefox-95.0.2/./mach", line 167, in <module>
    main(sys.argv[1:])
  File "/home/user/.cache/yay/firedragon/src/firefox-95.0.2/./mach", line 159, in main
    mach = check_and_get_mach(os.path.dirname(os.path.realpath(__file__)))
  File "/home/user/.cache/yay/firedragon/src/firefox-95.0.2/./mach", line 146, in check_and_get_mach
    return load_mach(dir_path, mach_path)
  File "/home/user/.cache/yay/firedragon/src/firefox-95.0.2/./mach", line 134, in load_mach
    return mach_initialize.initialize(dir_path)
  File "/home/user/.cache/yay/firedragon/src/firefox-95.0.2/build/mach_initialize.py", line 291, in initialize
    _activate_python_environment(topsrcdir)
  File "/home/user/.cache/yay/firedragon/src/firefox-95.0.2/build/mach_initialize.py", line 233, in _activate_python_environment
    raise Exception(
Exception: According to "pip check", the current Python environment has package-compatibility issues.
==> ERROR: A failure occurred in build().
    Aborting...

Looks like the python-pip stuff still needs to get ironed out

UPDATE2: As of 95.0.2-2, I'm able to start compiling after uninstalling the python-pip package from my build VM