-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
palemoon: 27.9.4 -> 28.2.1 #51161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
palemoon: 27.9.4 -> 28.2.1 #51161
Conversation
@develCuy thank you for your contribution!
@GrahamcOfBorg build palemoon |
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: palemoon Partial log (click to expand)
|
Failure on x86_64-linux (full log) Attempted: palemoon Partial log (click to expand)
|
@develCuy you're missing gconf. I believe the build has worked for you but not for borg because you do not have sandbox enabled, and the build has picked up a dependency already on your system.
|
Failure on aarch64-linux (full log) Attempted: palemoon Partial log (click to expand)
|
Just added a note about my troubles with gconf to the description of this PR. |
@develCuy try |
Thanks @kalbasit! I'll retry the build now. @GrahamcOfBorg build palemoon |
@develCuy You need to request access to ofborg to be able to invoke it. Please see https://github.com/NixOS/ofborg @GrahamcOfBorg build palemoon |
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: palemoon Partial log (click to expand)
|
Failure on aarch64-linux (full log) Attempted: palemoon Partial log (click to expand)
|
@develCuy I get the following error:
This looks to be coming from here |
Timed out, unknown build status on x86_64-linux (full log) Attempted: palemoon Partial log (click to expand)
|
@kalbasit, just pushed an update, can you invoke @GrahamcOfBorg? |
sure, @GrahamcOfBorg build palemoon |
@kalbasit the build doesn't run :( |
I'll try again. @GrahamcOfBorg build palemoon |
seems to timeout now. Note that ofborg now logs into the checkbox below instead of writing comments. |
ok np, I’ll build it manually and based on that I’ll change the meta timeout. |
@develCuy the build is still failing.
Can you please attempt to build it yourself and let me know when it's ready and is building correctly? Thanks! |
I tried to build but I've been unable to. That's probably just unchanged by this PR, but it could be improved if you care about the package. It eats very much RAM per thread and it doesn't respect |
I was able to build palemoon 28.4.1 just fine on a machine with 8 threads and it was never using more than 8GB of RAM. |
(triage) @develCuy Are you still interested in moving this PR forward? |
@develCuy Hopefully if you turn on |
If that is still an issue, adding
to the .mozconfig appears to solve that.
EDIT 2: 28.4.1 and 28.2.1 give same build error. 😕
Those files do exist on Arch at least, wonder what's different… Someone should review if the official branding option should be kept though. My understanding of this statement is "yes, as long as we don't replace the bundled libraries"? |
@@ -10,14 +10,14 @@ | |||
|
|||
stdenv.mkDerivation rec { | |||
name = "palemoon-${version}"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
name
gets auto-constructed if you supply pname
now, best to change that while we're already here.
name = "palemoon-${version}"; | |
pname = "palemoon"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that a lot of other packages use this formula instead:
pname = "myname";
name = "${pname}-${version}";
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For convenience, you can also use pname and version attributes and mkDerivation will automatically set name to "${pname}-${version}" by default. Since RFC 0035, this is preferred for packages in Nixpkgs, as it allows us to reuse the version easily
902952d
Not required, but the link in homepage = "https://www.palemoon.org/"; Besides that, does this build on NixOS? I tried a very similar expression, changing: Deleting those files from the manifest lets the packaging finish, but that is most definitely not gonna be desired by upstream if we include the official branding. |
I am having this devtools issue in the install phase OPNA2608 was describing when building on NixOS. |
obsoleted by #64499 |
Motivation for this change
Update palemoon to latest releases, which includes security updates. I reported this as an issue as well (#51160).
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)I changed the compile settings according to: http://developer.palemoon.org/Developer_Guide:Build_Instructions/Pale_Moon/Linux. I don't know what to do with this:
mk_add_options MOZ_OBJDIR=/home/$USER/pmbuild/
, so I removed it, also, I guess that the following options should be reviewed carefully:Also, I don't know what is the right way to add gconf-2.0 as dependency, in my local I add this:
pkgs.gnome.Gconf
but inside buildInputs, otherwise nix-build can't find it.Finally, compilation never finished because it was too much for my old laptop.
closes #51160