Package Details: waterfox-git 55.2.2+1034b9e9972e-1

Git Clone URL: https://aur.archlinux.org/waterfox-git.git (read-only)
Package Base: waterfox-git
Description: 64-Bit optimized Firefox fork, no data collection, allows unsigned extensions
Upstream URL: https://www.waterfoxproject.org/
Licenses: MPL
Conflicts: waterfox waterfox-bin
Provides: waterfox=55.2.2+1034b9e9972e
Submitter: ilikenwf
Maintainer: ilikenwf
Last Packager: ilikenwf
Votes: 6
Popularity: 1.152891
First Submitted: 2017-02-05 09:35
Last Updated: 2017-10-24 03:38

Dependencies (34)

Required by (0)

Sources (12)

Latest Comments

bhrgunatha commented on 2017-11-20 13:19

Build is failing for me:

I built about a month ago and due to the upgrade of icu (59 -> 60) my built version no longer works - xul requires older libicui18n.so (wants 59)

Relevant error reports from the log file are:

stack backtrace:
0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
1: std::sys_common::backtrace::print
2: std::panicking::default_hook::{{closure}}
3: std::panicking::default_hook
4: std::panicking::rust_panic_with_hook
5: std::panicking::begin_panic_new
6: std::panicking::begin_panic_fmt
7: build_script_build::build_gecko::bindings::write_binding_file
8: build_script_build::build_gecko::bindings::generate_structs
9: __rust_maybe_catch_panic
10: <F as alloc::boxed::FnBox<A>>::call_box
11: std::sys::imp::thread::Thread::new::thread_start
12: start_thread
13: __clone
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Any', src/libcore/result.rs:860:4
stack backtrace:
0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
1: std::sys_common::backtrace::print
2: std::panicking::default_hook::{{closure}}
3: std::panicking::default_hook
4: std::panicking::rust_panic_with_hook
5: std::panicking::begin_panic_new
6: std::panicking::begin_panic_fmt
7: rust_begin_unwind
8: core::panicking::panic_fmt
9: core::result::unwrap_failed
10: build_script_build::main
11: __rust_maybe_catch_panic
12: std::panicking::try
13: std::rt::lang_start
14: __libc_start_main
15: _start

make[5]: *** [/home/bhrgunatha/waterfox-git/src/Waterfox/config/rules.mk:987: force-cargo-library-build] Error 101
make[5]: Leaving directory '/home/bhrgunatha/waterfox-git/src/Waterfox/obj-x86_64-pc-linux-gnu/toolkit/library/rust'
...
...
make[4]: *** [/home/bhrgunatha/waterfox-git/src/Waterfox/config/recurse.mk:73: toolkit/library/rust/target] Error 2
make[4]: *** Waiting for unfinished jobs....
...
...
make[5]: Leaving directory '/home/bhrgunatha/waterfox-git/src/Waterfox/obj-x86_64-pc-linux-gnu/widget/gtk'
make[4]: Leaving directory '/home/bhrgunatha/waterfox-git/src/Waterfox/obj-x86_64-pc-linux-gnu'
make[3]: *** [/home/bhrgunatha/waterfox-git/src/Waterfox/config/recurse.mk:33: compile] Error 2
make[3]: Leaving directory '/home/bhrgunatha/waterfox-git/src/Waterfox/obj-x86_64-pc-linux-gnu'
make[2]: *** [/home/bhrgunatha/waterfox-git/src/Waterfox/config/rules.mk:453: default] Error 2
make[2]: Leaving directory '/home/bhrgunatha/waterfox-git/src/Waterfox/obj-x86_64-pc-linux-gnu'
make[1]: *** [/home/bhrgunatha/waterfox-git/src/Waterfox/client.mk:419: realbuild] Error 2
make[1]: Leaving directory '/home/bhrgunatha/waterfox-git/src/Waterfox'
make: *** [client.mk:170: build] Error 2
ERROR: A failure occurred in build().
Aborting...

Rest of my system is up-to-date,

Any ideas how to get it built.


meatatt commented on 2017-08-17 03:58

By the following commit, version number has dropped to 55.0.1, making yaourt try to upgrade this package while the latest version 55.0.1+e57df0da9107 has already been installed.

commit d7a847706ede179e856955c7532d0cfe9797e6ae
Author: Alex Kontos <alex@waterfoxproject.org>
Date: Tue Aug 15 00:52:48 2017 +0100

Downgrade version number.

ilikenwf commented on 2017-07-15 20:03

-git implies that it is building the tip of the primary development branch in most cases unless that branch doesn't usually build, so master is proper.

Likewise -git implies git, not a tarball.

ilikenwf commented on 2017-06-07 02:43

Because this is a git package it is always up to date unless it doesn't build.

meatatt commented on 2017-04-02 10:31

Won't build without cargo, please add it to make dependencies.

Dante_Igashu commented on 2017-02-17 05:22

**UPDATE** 10/02/2017

Let me try to be as specific and kind as you were (that must be the reason why I "love" Linux Techies).
/*That's all I get for errors, the text displayed before that is about the compiling process and marks no errors. Your "solution" or "request" tells me nothing.*/

Well I guess I was even much more specific about the subject than that poor answer.

It would be motivating (at least) to see a message like:
"Thanks dear user for reporting issues, I am sorry to inform you that the information you provided at the moment is not sufficient to get an idea on what could be the cause of that error, but if you do X and post X here we may get a better idea

Have a nice day!"

but that kind of attitude may be the reason a million things never get fixed on some linux distributions...

In this case let me try to help each other as it seems you don't care.

Yes, I know compiling time is dependent on my machine hardware capabilities, I should have been more specific and say "perhaps it may give you an idea where the error could be".
I guess I should try my best to read your minds to know exactly what you could need so you can work on a fix, But as hard as I could try I know that will be impossible to me. So, may I give some suggestions:

1. I could give you as much of the text displayed from the compiling process AS I can get (which means I will have to wait until the error is present again).

2. I could get another file for you, if that's the case, just tell me which one and if I need to do something on the terminal, it would be very kind from you if you told me what command I would need in order to get that information.

I am willing to help (even if there's little I may know about what's going on) so I would appreciate at least a little guidance on what I can do to help even a little and, maybe, collaborate on a better solution system on arch linux.

THANKS for taking a little time to read this unnecessary comments, and have a great day!

ilikenwf commented on 2017-02-10 19:51

Compile time will vary based on your machine specs.

Your error output is incomplete and doesn't really tell us anything.

Dante_Igashu commented on 2017-02-08 03:39

Hello!
Thanks for creating this package ilikenwf, I would like to know if I am the only one with an issue installing waterfox-git. It took about 90 minutes compiling when it stopped due to an error with installation. I hope it gets a solution, I love waterfox because my laptop is not a powerful one, and when using firefox I can't play 60fps videos, but that's no problem when using waterfox, besides other benefits.
THANKS IN ADVANCE for any kind of help I can get (Even if it just a helpful and kind tip).

PS: I had Waterfox-bin installed but uninstalled it before trying to install the git version, so I guess that may not be the problem.

PS: I tried to install it again and this is what I get at the end:

make[5]: Leaving directory '/tmp/yaourt-tmp-dante/aur-waterfox-git/src/Waterfox/obj-x86_64-pc-linux-gnu/dom/xbl'
make[4]: Leaving directory '/tmp/yaourt-tmp-dante/aur-waterfox-git/src/Waterfox/obj-x86_64-pc-linux-gnu'
make[3]: *** [/tmp/yaourt-tmp-dante/aur-waterfox-git/src/Waterfox/config/recurse.mk:33: compile] Error 2
make[3]: Leaving directory '/tmp/yaourt-tmp-dante/aur-waterfox-git/src/Waterfox/obj-x86_64-pc-linux-gnu'
make[2]: *** [/tmp/yaourt-tmp-dante/aur-waterfox-git/src/Waterfox/config/rules.mk:523: default] Error 2
make[2]: Leaving directory '/tmp/yaourt-tmp-dante/aur-waterfox-git/src/Waterfox/obj-x86_64-pc-linux-gnu'
make[1]: *** [/tmp/yaourt-tmp-dante/aur-waterfox-git/src/Waterfox/client.mk:413: realbuild] Error 2
make[1]: Leaving directory '/tmp/yaourt-tmp-dante/aur-waterfox-git/src/Waterfox'
make: *** [client.mk:168: build] Error 2
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build waterfox-git.
==> Restart building waterfox-git ? [y/N]

Is it an error in the PKGBUILD?

**UPDATE** 10/02/2017

Let me try to be as specific and kind as you were (that must be the reason why I "love" Linux Techies).
/*That's all I get for errors, the text displayed before that is about the compiling process and marks no errors. Your "solution" or "request" tells me nothing.*/

Well I guess I was even much more specific about the subject than that poor answer.

It would be motivating (at least) to see a message like:
"Thanks dear user for reporting issues, I am sorry to inform you that the information you provided at the moment is not sufficient to get an idea on what could be the cause of that error, but if you do X and post X here we may get a better idea

Have a nice day!"

but that kind of attitude may be the reason a million things never get fixed on some linux distributions...

In this case let me try to help each other as it seems you don't care.

Yes, I know compiling time is dependent on my machine hardware capabilities, I should have been more specific and say "perhaps it may give you an idea where the error could be".
I guess I should try my best to read your minds to know exactly what you could need so you can work on a fix, But as hard as I could try I know that will be impossible to me. So, may I give some suggestions:

1. I could give you as much of the text displayed from the compiling process AS I can get (which means I will have to wait until the error is present again).

2. I could get another file for you, if that's the case, just tell me which one and if I need to do something on the terminal, it would be very kind from you if you told me what command I would need in order to get that information.

I am willing to help (even if there's little I may know about what's going on) so I would appreciate at least a little guidance on what I can do to help even a little and, maybe, collaborate on a better solution system on arch linux.

THANKS for taking a little time to read this unnecesary comments, and have a great day!