Package Details: flightradar24 1.0.48-1

Git Clone URL: https://aur.archlinux.org/flightradar24.git (read-only, click to copy)
Package Base: flightradar24
Description: Feeder software for Flightradar24.com (fr24feed)
Upstream URL: https://www.flightradar24.com/share-your-data
Licenses: custom
Submitter: yuvadm
Maintainer: jimmyxu
Last Packager: jimmyxu
Votes: 9
Popularity: 0.65
First Submitted: 2014-03-13 15:31 (UTC)
Last Updated: 2024-05-21 02:09 (UTC)

Latest Comments

1 2 3 4 Next › Last »

jimmyxu commented on 2024-02-15 02:22 (UTC)

I've added a service file and listed dump978 in optdepends.

skooj commented on 2024-02-14 16:35 (UTC) (edited on 2024-02-14 17:24 (UTC) by skooj)

With 1.0.46, FR24 added a feeder for UAT (978) planes. By my understanding, this is only used in the US. This PKGBUILD does not install the binaries or service for this, though they are included in the .deb files sourced by FR24 themselves.

I am not very familiar with making or modifying PKGBUILD files, but since I was already feeding UAT (through dump978-fa, which is required) to other services, I was able to modify the PKGBUILD with the following package() section:

package() {
  install -Dm755 -t "$pkgdir/usr/bin" usr/bin/fr24feed usr/bin/fr24feed-status usr/bin/fr24feed-signup-uat usr/bin/fr24uat-feed-status
  install -Dm644 usr/share/fr24/licences/LICENSE.fr24feed.txt "$pkgdir/usr/share/licenses/$pkgname/LICENSE"
  install -Dm644 -t "$pkgdir/etc" etc/fr24feed.ini

  install -Dm644 -t "$pkgdir/usr/lib/systemd/system" fr24feed.service etc/systemd/system/fr24uat-feed.service
  install -Dm644 flightradar24.sysusers "$pkgdir/usr/lib/sysusers.d/$pkgname.conf"

  # hostname: invalid option -- 'I'
  # Try 'hostname --help' or 'hostname --usage' for more information.
  install -Dm755 -t "$pkgdir/usr/lib/$pkgname" hostname
}

l3rc10 commented on 2023-10-10 09:44 (UTC) (edited on 2023-10-10 09:44 (UTC) by l3rc10)

works on pi4 too

diff --git a/PKGBUILD b/PKGBUILD
index 51c79cf..546828f 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -9,7 +9,7 @@ pkgrel=1
 _pkgver=1.0.34-0
 _pkgverarm=1.0.37-0
 pkgdesc='Feeder software for Flightradar24.com (fr24feed)'
-arch=('x86_64' 'i686' 'armv6h' 'armv7h')
+arch=('x86_64' 'i686' 'armv6h' 'armv7h' 'aarch64')
 url='https://www.flightradar24.com/share-your-data'
 license=('custom')
 depends=('bash' 'dump1090')
@@ -23,6 +23,7 @@ source_x86_64=("https://repo-feed.flightradar24.com/linux_x86_64_binaries/${_pkg
 source_i686=("https://repo-feed.flightradar24.com/linux_x86_binaries/${_pkgname}_${_pkgver}_i386.deb")
 source_armv6h=("https://repo-feed.flightradar24.com/rpi_binaries/${_pkgname}_${_pkgverarm}_armhf.deb")
 source_armv7h=("https://repo-feed.flightradar24.com/rpi_binaries/${_pkgname}_${_pkgverarm}_armhf.deb")
+source_aarch64=("https://repo-feed.flightradar24.com/rpi_binaries/${_pkgname}_${_pkgverarm}_armhf.deb")

 sha256sums=('857383cd88daac429f25579d40cc5c4f3c4468f2af406cba70d3d7e9fe825cd3'
             'a018c751e431fcde72e709917fdfe663a5c74040af80b56d1a4658ba962c95e5'
@@ -32,6 +33,7 @@ sha256sums_x86_64=('d6d9bae103946729d2c58a04a77686f01c29b9f3d6bcfe74e750c80d6be7
 sha256sums_i686=('2ac8166d910b7ca9d102733defb49b65012236610b9c2e974c815175a578395c')
 sha256sums_armv6h=('ef28bb6df6e2eb68b866f69c1f04bffa9243b4dc9f662064de7d01817eaa2f46')
 sha256sums_armv7h=('ef28bb6df6e2eb68b866f69c1f04bffa9243b4dc9f662064de7d01817eaa2f46')
+sha256sums_aarch64=('ef28bb6df6e2eb68b866f69c1f04bffa9243b4dc9f662064de7d01817eaa2f46')

 prepare() {
   tar -xf data.tar.gz

hotaru commented on 2020-08-22 05:33 (UTC)

looks like 1.0.25-4 fixed the segmentation fault on x86_64.

a36233 commented on 2019-12-26 11:54 (UTC) (edited on 2019-12-26 12:28 (UTC) by a36233)

systemd-coredump[875]: Process 865 (fr24feed) of user 991 dumped core.

                                            Stack trace of thread 865:
                                            #0  0x00007fd054badf43 n/a (/usr/lib/libnss_resolve.so.2 + 0x6f43)
                                            #1  0x00007fd054bba47e n/a (/usr/lib/libnss_resolve.so.2 + 0x1347e)
                                            #2  0x00007fd054bd9109 n/a (/usr/lib/libnss_resolve.so.2 + 0x32109)
                                            #3  0x00007fd054bd9395 n/a (/usr/lib/libnss_resolve.so.2 + 0x32395)
                                            #4  0x00007fd054bd9966 n/a (/usr/lib/libnss_resolve.so.2 + 0x32966)
                                            #5  0x00007fd054bdcf61 _nss_resolve_gethostbyname3_r (/usr/lib/libnss_resolve.so.2 + 0x35f61)
                                            #6  0x00007fd054bdd66a _nss_resolve_gethostbyname_r (/usr/lib/libnss_resolve.so.2 + 0x3666a)
                                            #7  0x00000000009633af n/a (/usr/bin/fr24feed + 0x5633af)
                                            #8  0x0000000000962b4f n/a (/usr/bin/fr24feed + 0x562b4f)
                                            #9  0x000000000049781c n/a (/usr/bin/fr24feed + 0x9781c)
                                            #10 0x000000000041c097 n/a (/usr/bin/fr24feed + 0x1c097)
                                            #11 0x00000000008cb350 n/a (/usr/bin/fr24feed + 0x4cb350)
                                            #12 0x00000000004185ea n/a (/usr/bin/fr24feed + 0x185ea)

                                            Stack trace of thread 867:
                                            #0  0x00000000007d4f94 n/a (/usr/bin/fr24feed + 0x3d4f94)
                                            #1  0x00000000008f7518 n/a (/usr/bin/fr24feed + 0x4f7518)
                                            #2  0x00000000008fac22 n/a (/usr/bin/fr24feed + 0x4fac22)
                                            #3  0x00000000008f1e6a n/a (/usr/bin/fr24feed + 0x4f1e6a)
                                            #4  0x00000000008f154b n/a (/usr/bin/fr24feed + 0x4f154b)
                                            #5  0x000000000049ce89 n/a (/usr/bin/fr24feed + 0x9ce89)
                                            #6  0x00000000007cfb72 n/a (/usr/bin/fr24feed + 0x3cfb72)
                                            #7  0x0000000000960bdf n/a (/usr/bin/fr24feed + 0x560bdf)

                                            Stack trace of thread 866:
                                            #0  0x00000000007d3ba5 n/a (/usr/bin/fr24feed + 0x3d3ba5)
                                            #1  0x00000000004a510a n/a (/usr/bin/fr24feed + 0xa510a)
                                            #2  0x00000000004a5530 n/a (/usr/bin/fr24feed + 0xa5530)
                                            #3  0x00000000008098df n/a (/usr/bin/fr24feed + 0x4098df)
                                            #4  0x00000000007cfb72 n/a (/usr/bin/fr24feed + 0x3cfb72)
                                            #5  0x0000000000960bdf n/a (/usr/bin/fr24feed + 0x560bdf)

jimmyxu commented on 2019-11-24 07:58 (UTC)

@test0 I'm drawing a blank on the scheme as there were days where even the pkgver of amd64 and armhf differed. I initially thought about 1.0.24_5_7-1 but considered it a tad messy. So if you have any ideas.

test0 commented on 2019-11-23 07:11 (UTC)

Will be possible to add a sub-revision number in order not to mess up with the official release number and differentiate between architectures?

jimmyxu commented on 2019-11-22 17:27 (UTC) (edited on 2019-11-22 18:26 (UTC) by jimmyxu)

Just added a hostname script to hopefully get rid of the "invalid option -- 'I'" warning. Please let me know if I borked anything.

From my testing, the only latest thing working on x86_64 right now is their i386 version (fr24feed_1.0.24-5_i386). Disabling mlat does not help.

So if you want to run that, just change source_x86_64 and sha256sums_x86_64 to read the same as _i686.

hotaru commented on 2019-11-19 08:32 (UTC)

update: just got a response to the message I sent via the contact form. apparently they think clearing cookies and cache in my browser is going to somehow fix fr24feed segfaulting on a completely different machine.

hotaru commented on 2019-11-18 21:40 (UTC)

looks like posting on their forum just resulted a flood of off-topic spam and trolls defending the spam.

I did manage to find a contact form on the flightradar24 site, and reported the bug that way as well. I don't have high hopes for it being fixed, though.