You are not logged in.

#1 2019-05-31 15:53:56

ApB
Member
Registered: 2019-05-24
Posts: 6

Adapting firefox-nightly PKGBUILD from AUR to pentium4.

With the whole pentium4 migration the AUR PKGBUILD for firefox-nightly stoped working.

https://aur.archlinux.org/cgit/aur.git/ … ox-nightly

mozilla doesn't offer -pentium4 packages and i686 doesn't work.

Any help/tips on how to make this work?

Offline

#2 2019-05-31 19:51:38

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 393

Re: Adapting firefox-nightly PKGBUILD from AUR to pentium4.

Why do you say i686 doesn't work?

This might be a good test case for adapting prebuilt binary pkgbuilds to pentium4.  You need at the very least to add 'pentum4' to the arch array, and rename (or copy and rename if you want something that also works on older i686 envs) src_i686 and sha512sums_i686 to end with pentium4.  Does it work for you if you do those three steps, or is there anything I've missed?


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#3 2019-05-31 20:14:06

ApB
Member
Registered: 2019-05-24
Posts: 6

Re: Adapting firefox-nightly PKGBUILD from AUR to pentium4.

Tried adding pentiun4 on the arch array > no go. Was the first thing i tried. Then tried changing pacman.conf from auto to i686 but that didn't work also. I might need to mess with makepkg.conf but didn't try this yet and i am quite sure that if i do it will fuck up other things.

Its outside my skill level. hmm

Last edited by ApB (2019-05-31 20:15:54)

Offline

#4 2019-05-31 21:23:27

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 393

Re: Adapting firefox-nightly PKGBUILD from AUR to pentium4.

It seems to be working for me.  I've downloaded that pkgbuild and modified it, and have been able to build a package.  Here's my diffs against the PKGBUILD:

diff --git a/PKGBUILD b/PKGBUILD
index 97e5767..f31db4b 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -8,9 +8,9 @@ pkgname=${_name}-${_channel}
 pkgdesc="Standalone Web Browser from Mozilla — Nightly build (${_lang})"
 url="https://www.mozilla.org/${_lang}/${_name}/${_channel}"
 _version=69.0a1
-pkgver=69.0a1.20190521
+pkgver=69.0a1.
 pkgrel=1
-arch=('i686' 'x86_64')
+arch=('i686' 'x86_64' 'pentium4')
 license=('MPL' 'GPL' 'LGPL')
 depends=('dbus-glib' 'gtk3' 'libxt' 'nss' 'mime-types')
 optdepends=('pulseaudio: audio support'
@@ -25,7 +25,7 @@ _url="https://download-installer.cdn.mozilla.net/pub/${_name}/nightly/latest-moz
 _src="${_name}-${_version}.${_lang}.linux"
 _filename="$(date +%Y%m%d)-${_src}"
 source=("${pkgname}.desktop" 'policies.json')
-source_i686=("${_filename}-i686.tar.bz2"::"${_url}/${_src}-i686.tar.bz2"
+source_pentium4=("${_filename}-i686.tar.bz2"::"${_url}/${_src}-i686.tar.bz2"
              "${_filename}-i686.tar.bz2.asc"::"${_url}/${_src}-i686.tar.bz2.asc"

              "${_filename}-i686.tar.bz2.asc"::"${_url}/${_src}-i686.tar.bz2.asc"
              "${_filename}-i686.txt"::"${_url}/${_src}-i686.txt")
 source_x86_64=("${_filename}-x86_64.tar.bz2"::"${_url}/${_src}-x86_64.tar.bz2"
@@ -33,7 +33,7 @@ source_x86_64=("${_filename}-x86_64.tar.bz2"::"${_url}/${_src}-x86_64.tar.bz2"
                "${_filename}-x86_64.txt"::"${_url}/${_src}-x86_64.txt")
 sha512sums=('42426e7b510bd88cbf7b246bf66d7768afa5d71389bf15f7a4231dc24f99fd73284dd9a0a8eb4342b42337c2c7dd843e570a93afa7d3b44c97ecbf5e38e433ac'
'5ed67bde39175d4d10d50ba5b12063961e725e94948eadb354c0588b30d3f97d2178b66c1af466a6e7bd208ab694227a1391c4141f88d3da1a1178454eba5308')
-sha512sums_i686=('SKIP' 'SKIP' 'SKIP')
+sha512sums_pentium4=('SKIP' 'SKIP' 'SKIP')
 sha512sums_x86_64=('SKIP' 'SKIP' 'SKIP')
 validpgpkeys=('14F26682D0916CDD81E37B6D61B7B526D98F0353') # Mozilla’s GnuPG release key

I'm not sure that that pkgver update is.  Perhaps it's something makepkg does while it's running.

I did need to import a gpg key to validate the binary:

gpg --recv-keys BBBEBDBB24C6F355

And I did get an error while building the package:

==> Starting pkgver()...
head: cannot open '20190531-firefox-69.0a1.en-US.linux-pentium4.txt' for reading: No such file or directory

But I think that's just an informational message. 'pkgver()' is defined in the PKGBUILD too, and you'd just need to hardcode the ${CARCH} if you needed this message to proceed.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

Board footer

Powered by FluxBB