Building Pale Moon on Devuan fails

The place to report Pale Moon specific bugs on Linux and other operating systems.

Moderator: satrow

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Building Pale Moon on Devuan fails

Unread postby miroR » Sat, 20 May 2017, 16:38

title: Building Pale Moon on Devuan fails
---
To install Pale Moon in my Devuan Linux, I've been following this guide:
A linux build framework for Pale Moon
viewtopic.php?f=37&t=13898&start=20

Here is why (and there's also the issue which is still left to solve for me):
Palemoon installation from source
https://dev1galaxy.org/viewtopic.php?id=616

Might it to do with:
xpcshell should be built with "-march=native"
viewtopic.php?f=57&t=14370
I can not tell...

The error is, pasting just a little shorter excerpt from that topic:

Code: Select all

 0:06.39 Executing /home/mr/pmmain/native/pmbuild/dist/bin/xpcshell -g /home/mr/pmmain/native/pmbuild/dist/bin/ -a /home/mr/pmmain/native/pmbuild/dist/bin/ -f /home/mr/pmmain/pmsrc/toolkit/mozapps/installer/precompile_cache.js -e precompile_startupcache("resource://gre/");
 0:06.44 out of memory
 0:06.44 Assertion failure: [unhandlable oom] OOM in createJitRuntime, at /home/mr/pmmain/pmsrc/js/src/jscntxt.cpp:1183
 0:06.45 Traceback (most recent call last):
 0:06.45   File "/home/mr/pmmain/pmsrc/toolkit/mozapps/installer/packager.py", line 405, in <module>
 0:06.45     main()
 0:06.45   File "/home/mr/pmmain/pmsrc/toolkit/mozapps/installer/packager.py", line 399, in main
 0:06.45     args.source, gre_path, base)
 0:06.45   File "/home/mr/pmmain/pmsrc/toolkit/mozapps/installer/packager.py", line 157, in precompile_cache
 0:06.45     errors.fatal('Error while running startup cache precompilation')
 0:06.45   File "/home/mr/pmmain/native/pmsrc/python/mozbuild/mozpack/errors.py", line 101, in fatal
 0:06.45     self._handle(self.FATAL, msg)
 0:06.45   File "/home/mr/pmmain/native/pmsrc/python/mozbuild/mozpack/errors.py", line 96, in _handle
 0:06.45     raise ErrorMessage(msg)
 0:06.45 mozpack.errors.ErrorMessage: Error: Error while running startup cache precompilation
 0:06.47 /home/mr/pmmain/pmsrc/toolkit/mozapps/installer/packager.mk:36: recipe for target 'stage-package' failed
 0:06.47 make[3]: *** [stage-package] Error 1
 0:06.47 make[3]: Leaving directory '/home/mr/pmmain/native/pmbuild/browser/installer'
 0:06.47 /home/mr/pmmain/pmsrc/toolkit/mozapps/installer/packager.mk:81: recipe for target 'make-package' failed
 0:06.48 make[2]: *** [make-package] Error 2
 

Any help is warmly welcome!

User avatar
filip
Hobby Astronomer
Hobby Astronomer
Posts: 15
Joined: Wed, 08 Feb 2017, 15:52
Location: Serbia

Re: Building Pale Moon on Devuan fails

Unread postby filip » Sat, 20 May 2017, 17:29

I don't know which CPU/march are you building for, but I had the same issue with the startupcache precompilation for as long as I can remember when building for AMD Ahtlon II (-march=amdfam10) on an Intel machine.
Solved by compiling on the target PC with "-mach=native" ( for some reason compiling with "core2", "athlon-xp" and "k8-sse3" march on any machine doesn't exibit this issue for me, "amdfam10" is the only one failing ).

Also, since you're building for Devuan/Debian, you can use "palemoon_27.X.Y.*.debian.tar.xz " source from Steve's repository:
http://download.opensuse.org/repositori ... ebian_8.0/
... to build .deb package.
I'm asuming you know how to do that ( "mozconfig" is inside /debian, source format is "3.0 Quilt" so you'll need an *orig.tar.gz etc... ), but if you need help, I can write a how-to. :)

EDIT:

It's also possible that you're running out of memory during build ( how much RAM do you have on the build PC? ), however I've been seeing the same error while being certain that it's actually not happening ( monitoring the RAM live during build which never exceeded ~6GB usage on an machine with 8GB RAM + 6GB swap )

Code: Select all

...
0:06.44 out of memory
0:06.44 Assertion failure: [unhandlable oom] OOM...

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon on Devuan fails

Unread postby miroR » Sat, 20 May 2017, 18:52

Thanks for caring!
filip wrote:I don't know which CPU/march are you building for, but I had the same issue with the startupcache precompilation for as long as I can remember when building for AMD Ahtlon II (-march=amdfam10) on an Intel machine.
Solved by compiling on the target PC with "-mach=native" ( for some reason compiling with "core2", "athlon-xp" and "k8-sse3" march on any machine doesn't exibit this issue for me, "amdfam10" is the only one failing ).

I see.
Also, since you're building for Devuan/Debian, you can use "palemoon_27.X.Y.*.debian.tar.xz " source from Steve's repository:
http://download.opensuse.org/repositori ... ebian_8.0/
... to build .deb package.
I'm asuming you know how to do that ( "mozconfig" is inside /debian, source format is "3.0 Quilt" so you'll need an *orig.tar.gz etc... ), but if you need help, I can write a how-to. :)

I thought I had that... But no, only now I do... Or I lost it... Never mind.
I might go the way with that source:

Code: Select all

$ ls -ABRgo
-rw-r--r-- 1      1264 Apr 30 03:19 palemoon_27.3.0~repack-1.dsc
-rw-r--r-- 1 125987516 Apr 30 03:19 palemoon_27.3.0~repack.orig.tar.xz
-rw-r--r-- 1     30322 May 20 18:48 palemoon_27.3.0~repack.orig.tar.xz.meta4
$

, if... [continuation further below]

EDIT:

It's also possible that you're running out of memory during build ( how much RAM do you have on the build PC? ), however I've been seeing the same error while being certain that it's actually not happening ( monitoring the RAM live during build which never exceeded ~6GB usage on an machine with 8GB RAM + 6GB swap )

Code: Select all

...
0:06.44 out of memory
0:06.44 Assertion failure: [unhandlable oom] OOM...

I have 16G of memory, it's not that, I don't think. But I don't know either...
[the promised continuation now]
First I'll be, actually I am, looking into where to try and stick:

Code: Select all

--disable-precompiled-startupcache

as the author of writes in
xpcshell should be built with "-march=native"
and maybe I managed to compile it...

But pls. stick around (just casually, don't let it interfere with your other work), if I need a piece of advice...
And about the guide, maybe other folks would need it too even if I wouldn't... But it's true, I haven't used quilt, and am not familiar with it... I'm much more used to building on Gentoo than on Devuan/Debian...

I think I first need to try and see where to stick that --disable-precompiled-startupcache, because Pale Moon has been built in my Devuan, just I can't package it... Because that should not be too much work, figuring it out...

And if that should fail, I go that Steve Pusser's source way.

User avatar
filip
Hobby Astronomer
Hobby Astronomer
Posts: 15
Joined: Wed, 08 Feb 2017, 15:52
Location: Serbia

Re: Building Pale Moon on Devuan fails

Unread postby filip » Sat, 20 May 2017, 19:36

You're welcome! :)

I have 16G of memory, it's not that, I don't think. But I don't know either...


Yeah, RAM is not the issue then...

First I'll be, actually I am, looking into where to try and stick:

--disable-precompiled-startupcache



When building debian package, that should go into "mozconfig", found in ./palemoon*/debian1. Just add this line to it:

Code: Select all

ac_add_options --disable-precompiled-startupcache


1 The easiest way to unpack the complete source is to run:

Code: Select all

dpkg-source -x palemoon_27.3.0~repack-1.dsc


Otherwise it also goes into "mozconfig", with the only difference being that "mozconfig" is now located inside Pale Moon toplevel source directory.

But pls. stick around (just casually, don't let it interfere with your other work), if I need a piece of advice...


Well, I'm pretty busy latelly, so at times it might take a while for me to reply, but I'll certanly be around. :)

And about the guide, maybe other folks would need it too even if I wouldn't...


I'll get to it... In the meantime, here's a quick & dirty rundown:

Code: Select all

# First make sure you have the Debian tools needed:
sudo apt install dpkg-dev devscripts build-essential


Code: Select all

# Get the source ( changing the version number in file names accordingly ):
dget http://download.opensuse.org/repositories/home:/stevenpusser/Debian_8.0/palemoon_27.3.0~repack-1.dsc

# Extract:
dpkg-source -x palemoon_27.3.0~repack-1.dsc

# Enter src dir:
cd palemoon-27.3.0~repack

# Edit "debian/mozconfig" as needed/desired
your_prefered_editor ./debian/mozconfig

# If building for the first time, install Pale Moon build dependencies
mk-build-deps --install ./debian/control

# Let it build/go make some coffee:
dpkg-buildpackage -j$(nproc)

# Install the package using you preffered method
# Or in case you're upgrading, simply use:
sudo debi --upgrade


Cheers! :)

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon on Devuan fails

Unread postby miroR » Sat, 20 May 2017, 20:42

The:

Code: Select all

ac_add_options --disable-precompiled-startupcache

in the mozconfig.txt that I created by Walter Dnes's instructions, that option did it!

I have a shiny brand new:

Code: Select all

mr@localhost:~$ ls -ABRgo palemoon-27.3.0.linux-x86_64.tar.bz2
-rw-r--r-- 1 32622705 May 20 19:37 palemoon-27.3.0.linux-x86_64.tar.bz2
mr@localhost:~$ sha256sum palemoon-27.3.0.linux-x86_64.tar.bz2
26a90e72b8dba8748f6559f0a57ae7dca911b0c698e804e43e16b0824de2f1e3  palemoon-27.3.0.linux-x86_64.tar.bz2
mr@localhost:~$

source package now.

First I need to test if it really can log SSL-keys for me... That's, for other interested parties :) in: https://wiki.wireshark.org/SSL.

Configuration goes probably like in my Gentoo... I stick:

Code: Select all

export SSLKEYLOGFILE=/home/mr/.sslkey.log

or maybe I stowed it somewhere else, I can't tell you (if anybody is following here and want to try and log SSL-keys, pls. know that it is a security hazard if you don't control really well you system; it hasn't been removed --it was available in regular builds-- for nothing).

Now I log out completely, and log back in.
And after the instructions in Walter Dnes' package pmmain.tgz (the page where it's available at the top has already been linked previously; actually not directly, so:
A linux build framework for Pale Moon
viewtopic.php?f=37&t=13898&start=20
), in the readme.txt of that package:

Code: Select all

mr@localhost:~/pmmain/native$  pmbuild/dist/palemoon/palemoon -no-remote -p

But (probably grsecurity-related and innocuous...

Code: Select all

mr@localhost:~/pmmain/native$  pmbuild/dist/palemoon/palemoon -no-remote -p
out of memory
Assertion failure: [unhandlable oom] OOM in createJitRuntime, at /home/mr/pmmain/pmsrc/js/src/jscntxt.cpp:1183
Segmentation fault
mr@localhost:~/pmmain/native$

because I have:

Code: Select all

mr@localhost:~/pmmain/native$ uname -r
4.9.27-unofficial+grsec170512-22
mr@localhost:~/pmmain/native$

installed.

But no, the problem is more complex actually...

Code: Select all

mr@localhost:~/pmmain/native$ ls -l pmbuild/dist/palemoon
total 82772
-rw-r--r-- 1 mr mr      509 May 20 19:12 application.ini
drwxr-xr-x 7 mr mr     4096 May 20 19:36 browser
-rw-r--r-- 1 mr mr       40 May 20 19:36 chrome.manifest
drwxr-xr-x 2 mr mr     4096 May 20 19:36 components
drwxr-xr-x 3 mr mr     4096 May 20 19:36 defaults
-rw-r--r-- 1 mr mr      188 May 20 19:36 dependentlibs.list
drwxr-xr-x 2 mr mr     4096 May 20 19:36 dictionaries
-rw-r--r-- 1 mr mr      899 May 20 19:36 libfreeblpriv3.chk
-rwxr-xr-x 1 mr mr   512368 May 20 19:36 libfreeblpriv3.so
-rwxr-xr-x 1 mr mr 10965904 May 20 19:36 libicudata.so.58
-rwxr-xr-x 1 mr mr  1837824 May 20 19:36 libicui18n.so.58
-rwxr-xr-x 1 mr mr  1309504 May 20 19:36 libicuuc.so.58
-rwxr-xr-x 1 mr mr    10544 May 20 19:36 libmozalloc.so
-rwxr-xr-x 1 mr mr  6889944 May 20 19:36 libmozjs.so
-rwxr-xr-x 1 mr mr   727872 May 20 19:36 libmozsqlite3.so
-rwxr-xr-x 1 mr mr   216336 May 20 19:36 libnspr4.so
-rwxr-xr-x 1 mr mr   990488 May 20 19:36 libnss3.so
-rwxr-xr-x 1 mr mr   651456 May 20 19:36 libnssckbi.so
-rw-r--r-- 1 mr mr      899 May 20 19:36 libnssdbm3.chk
-rwxr-xr-x 1 mr mr   116280 May 20 19:36 libnssdbm3.so
-rwxr-xr-x 1 mr mr   167336 May 20 19:36 libnssutil3.so
-rwxr-xr-x 1 mr mr    18704 May 20 19:36 libplc4.so
-rwxr-xr-x 1 mr mr    14480 May 20 19:36 libplds4.so
-rwxr-xr-x 1 mr mr   140704 May 20 19:36 libsmime3.so
-rw-r--r-- 1 mr mr      899 May 20 19:36 libsoftokn3.chk
-rwxr-xr-x 1 mr mr   217192 May 20 19:36 libsoftokn3.so
-rwxr-xr-x 1 mr mr   259168 May 20 19:36 libssl3.so
-rwxr-xr-x 1 mr mr 52508696 May 20 19:36 libxul.so
-rw-r--r-- 1 mr mr  5992065 May 20 19:36 omni.ja
-rwxr-xr-x 1 mr mr   372176 May 20 19:36 palemoon
-rwxr-xr-x 1 mr mr   372176 May 20 19:36 palemoon-bin
-rw-r--r-- 1 mr mr       47 May 20 19:36 platform.ini
-rwxr-xr-x 1 mr mr   359832 May 20 19:36 plugin-container
-rw-r--r-- 1 mr mr     2046 May 20 19:36 precomplete
-rw-r--r-- 1 mr mr      711 May 20 19:36 removed-files
-rwxr-xr-x 1 mr mr     8915 May 20 15:26 run-mozilla.sh
mr@localhost:~/pmmain/native$


That's the build. But trying to sort it with paxrat:

Code: Select all

mr@localhost:~/pmmain/native/pmbuild/dist/palemoon$ su -c "paxrat -s pm -b palemoon"
Password:
exit status 2
2017/05/20 20:19:42 Unable to get real path for palemoon
mr@localhost:~/pmmain/native/pmbuild/dist/palemoon$

Hmmmh...

Code: Select all

mr@localhost:~/pmmain/native/pmbuild/dist/palemoon$ su -c "paxrat -s pm -b /home/mr/pmmain/native/pmbuild/dist/palemoon/palemoon"
Password:
2017/05/20 20:21:10 Cannot set PaX flags on /home/mr/pmmain/native/pmbuild/dist/palemoon/palemoon. Owner of symlink did not match owner of symlink target

mr@localhost:~/pmmain/native/pmbuild/dist/palemoon$

Wait a minute... Maybe... because... No! All these are regular directories, are they?

Code: Select all

mr@localhost:~/pmmain/native/pmbuild/dist/palemoon$ ls -ld /home
drwxr-xr-x 3 root root 4096 May  9 22:51 /home
mr@localhost:~/pmmain/native/pmbuild/dist/palemoon$ ls -ld /home/mr
drwxr-xr-x 39 mr mr 12288 May 20 20:14 /home/mr
mr@localhost:~/pmmain/native/pmbuild/dist/palemoon$ ls -ld /home/mr/pmmain
drwxr-xr-x 7 mr mr 4096 May 20 17:03 /home/mr/pmmain
mr@localhost:~/pmmain/native/pmbuild/dist/palemoon$ ls -ld /home/mr/pmmain/native
drwxr-xr-x 3 mr mr 4096 May 20 20:12 /home/mr/pmmain/native
mr@localhost:~/pmmain/native/pmbuild/dist/palemoon$ ls -ld /home/mr/pmmain/native/pmbuild
drwxr-xr-x 52 mr mr 4096 May 20 19:36 /home/mr/pmmain/native/pmbuild
mr@localhost:~/pmmain/native/pmbuild/dist/palemoon$ ls -ld /home/mr/pmmain/native/pmbuild/dist
drwxr-xr-x 17 mr mr 4096 May 20 19:37 /home/mr/pmmain/native/pmbuild/dist
mr@localhost:~/pmmain/native/pmbuild/dist/palemoon$ ls -ld /home/mr/pmmain/native/pmbuild/dist/palemoon
drwxr-xr-x 6 mr mr 4096 May 20 19:36 /home/mr/pmmain/native/pmbuild/dist/palemoon
mr@localhost:~/pmmain/native/pmbuild/dist/palemoon$

They're not soft links, for sure... But if any is hard symlink, how do I get to know that...

I very probably could boot into the stock kernel vmlinuz-3.16.0-4-amd64, but I feel lost without the protection of grsecurity...

The last "Owner of symlink did not match owner of symlink target"-error produced this line in /va/log/messages:

Code: Select all

May 20 20:10:41 localhost kernel: [ 7842.919086] palemoon[11069]: segfault at 0 ip 0000035b1b7eb2d3 sp 000003c684d872e0 error 6 in libmozjs.so[35b1b723000+640000]


So the issue is partly resolved, but new issue has arisen... Sorry for the messy report... But I hope also that, being detailed, there is a good side to it.

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon on Devuan fails

Unread postby miroR » Sat, 20 May 2017, 20:52

filip wrote:...
First I'll be, actually I am, looking into where to try and stick:

--disable-precompiled-startupcache

When building debian package, that should go into "mozconfig", found in ./palemoon*/debian1. Just add this line to it:

Code: Select all

ac_add_options --disable-precompiled-startupcache

Yeah, I did figure that out.

1 The easiest way to unpack the complete source is to run:

Code: Select all

dpkg-source -x palemoon_27.3.0~repack-1.dsc


Otherwise it also goes into "mozconfig", with the only difference being that "mozconfig" is now located inside Pale Moon toplevel source directory.

But pls. stick around (just casually, don't let it interfere with your other work), if I need a piece of advice...


Well, I'm pretty busy latelly, so at times it might take a while for me to reply, but I'll certanly be around. :)

And about the guide, maybe other folks would need it too even if I wouldn't...


I'll get to it... In the meantime, here's a quick & dirty rundown:

Code: Select all

# First make sure you have the Debian tools needed:
sudo apt install dpkg-dev devscripts build-essential


Code: Select all

# Get the source ( changing the version number in file names accordingly ):
dget http://download.opensuse.org/repositories/home:/stevenpusser/Debian_8.0/palemoon_27.3.0~repack-1.dsc

# Extract:
dpkg-source -x palemoon_27.3.0~repack-1.dsc

# Enter src dir:
cd palemoon-27.3.0~repack

# Edit "debian/mozconfig" as needed/desired
your_prefered_editor ./debian/mozconfig

# If building for the first time, install Pale Moon build dependencies
mk-build-deps --install ./debian/control

# Let it build/go make some coffee:
dpkg-buildpackage -j$(nproc)

# Install the package using you preffered method
# Or in case you're upgrading, simply use:
sudo debi --upgrade


Cheers! :)

Hey, thanks! That was great. It does sound very similar to what I read in packaging-tutorial.en.pdf and such, only so much quicker and, since I read those for hours :) these days, easier!

However, as you can see from the previous post of mine that I posted kind of in the meantime, I have a bad-looking paxrat issue to deal with... Aargh!

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon on Devuan fails

Unread postby miroR » Sat, 20 May 2017, 23:05

I followed these instructions:
filip wrote:When building debian package, that should go into "mozconfig", found in ./palemoon*/debian1. Just add this line to it:

Code: Select all

ac_add_options --disable-precompiled-startupcache


1 The easiest way to unpack the complete source is to run:

Code: Select all

dpkg-source -x palemoon_27.3.0~repack-1.dsc

Here I applied this patch:

Code: Select all

From: Miroslav Rovis <miro.rovis@croatiafidelis.hr>
Date: Sat, 20 May 2017 10:43:20 +0000
Subject: [PATCH] patch to allow SSL-key logging

---
--- security/nss/lib/ssl/Makefile
+++ security/nss/lib/ssl/Makefile
@@ -39,12 +39,11 @@ CSRCS       += unix_err.c
 endif
 endif
 
-# Enable key logging by default in debug builds, but not opt builds.
-# Logging still needs to be enabled at runtime through env vars.
-NSS_ALLOW_SSLKEYLOGFILE ?= $(if $(BUILD_OPT),0,1)
-ifeq (1,$(NSS_ALLOW_SSLKEYLOGFILE))
+# Enable key logging by default in all builds
+#NSS_ALLOW_SSLKEYLOGFILE ?= $(if $(BUILD_OPT),0,1)
+#ifeq (1,$(NSS_ALLOW_SSLKEYLOGFILE))
 DEFINES += -DNSS_ALLOW_SSLKEYLOGFILE=1
-endif
+#endif
 
 #######################################################################
 # (5) Execute "global" rules. (OPTIONAL)                              #
--
2.1.4

Otherwise it also goes into "mozconfig", with the only difference being that "mozconfig" is now located inside Pale Moon toplevel source directory.

Which one of these are you referring to:

Code: Select all

mr@localhost:~/Test/palemoon-27.3.0~repack$ ls -ltr $(find ./ -name mozconfig)
-rw-r--r-- 1 mr mr 639 Feb  9 22:57 ./debian/mozconfig
-rw-r--r-- 1 mr mr 407 Apr 22 21:34 ./xulrunner/config/mozconfig
-rw-r--r-- 1 mr mr 446 Apr 22 21:34 ./build/macosx/universal/mozconfig
-rw-r--r-- 1 mr mr 401 Apr 22 21:34 ./browser/config/mozconfig
mr@localhost:~/Test/palemoon-27.3.0~repack$

?
But I didn't touch any of them so far.

Code: Select all

# First make sure you have the Debian tools needed:
sudo apt install dpkg-dev devscripts build-essential

All these (I only had build-essential, because I built that 4.9.27-unofficial+grsec170512-22 kernel previously).

Code: Select all

# Get the source ( changing the version number in file names accordingly ):
dget http://download.opensuse.org/repositories/home:/stevenpusser/Debian_8.0/palemoon_27.3.0~repack-1.dsc

# Extract:
dpkg-source -x palemoon_27.3.0~repack-1.dsc

# Enter src dir:
cd palemoon-27.3.0~repack

Ah, I see now which one mozconfig you meant:
# Edit "debian/mozconfig" as needed/desired
your_prefered_editor ./debian/mozconfig

# If building for the first time, install Pale Moon build dependencies
mk-build-deps --install ./debian/control

But I made a mistake here. I have a no-dbus system ( purged it as per:
https://git.devuan.org/dev1fanboy/Upgra ... thout-dbus )...

...And I edited that ./debian/control and removed (the /home/mr/debian_control_170520_2206_localhost is the backed up original):

Code: Select all

mr@localhost:~/Test/palemoon-27.3.0~repack$ diff -u /home/mr/debian_control_170520_2206_localhost debian/control
--- /home/mr/debian_control_170520_2206_localhost       2017-02-22 22:20:09.000000000 +0000
+++ debian/control      2017-05-20 22:06:45.446929046 +0000
@@ -18,11 +18,8 @@
         zip,
         pkg-config,
         libgtk2.0-dev (>= 2.14),
-        libdbus-1-dev (>=0.60),
-        libdbus-glib-1-dev (>= 0.60),
         yasm (>= 1.1),
         libasound2-dev,
-        libpulse-dev,
         libxt-dev,
         mesa-common-dev
 Standards-Version: 3.9.6
mr@localhost:~/Test/palemoon-27.3.0~repack$


And I got bad errors when I ran:

# Let it build/go make some coffee:
dpkg-buildpackage -j$(nproc)


These errors:

Code: Select all

dpkg-buildpackage: source package palemoon
dpkg-buildpackage: source version 27.3.0~repack-1
dpkg-buildpackage: source distribution obs
dpkg-buildpackage: source changed by Steven Pusser <stevep@mxlinux.org>
 dpkg-source --before-build palemoon-27.3.0~repack
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean --parallel
   dh_testdir -O--parallel
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/home/mr/Test/palemoon-27.3.0~repack'
rm -f mozconfig
dh_auto_clean
make[1]: Leaving directory '/home/mr/Test/palemoon-27.3.0~repack'
   dh_clean -O--parallel
 dpkg-source -b palemoon-27.3.0~repack
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building palemoon using existing ./palemoon_27.3.0~repack.orig.tar.xz
dpkg-source: error: cannot represent change to palemoon-build-deps_27.3.0~repack-1_all.deb: binary file contents changed
dpkg-source: error: add palemoon-build-deps_27.3.0~repack-1_all.deb in debian/source/include-binaries if you want to store the modified binary in the debian tarball
dpkg-source: error: unrepresentable changes to source
dpkg-buildpackage: error: dpkg-source -b palemoon-27.3.0~repack gave error exit status 2


Instead, I should have edited the debian/mozconfig, should have added:

Code: Select all

ac_add_options --disable-dbus

and things into it.

So of course, I couldn't reach here:

Code: Select all

# Install the package using you preffered method
# Or in case you're upgrading, simply use:
sudo debi --upgrade


Cheers! :)

Will make another try next, or better tomorrow. Good night!

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon on Devuan fails

Unread postby miroR » Sun, 21 May 2017, 04:52

Repeating the procedure:

Code: Select all

dpkg-source -x palemoon_27.3.0~repack-1.dsc
cd palemoon-27.3.0~repack
patch -p0 < ~/allow-sslkeylogfile.patch
vi debian/mozconfig
dpkg-buildpackage -d -j4 |& tee ~/dpkg-buildpackage-d-j4_$(date +%y%m%d_%H%M)_$(hostname)

More kindly it failed this time:

Code: Select all

dpkg-buildpackage: source package palemoon
dpkg-buildpackage: source version 27.3.0~repack-1
dpkg-buildpackage: source distribution obs
dpkg-buildpackage: source changed by Steven Pusser <stevep@mxlinux.org>
 dpkg-source --before-build palemoon-27.3.0~repack
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean --parallel
   dh_testdir -O--parallel
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/home/mr/palemoon-27.3.0~repack'
rm -f mozconfig
dh_auto_clean
make[1]: Leaving directory '/home/mr/palemoon-27.3.0~repack'
   dh_clean -O--parallel
 dpkg-source -b palemoon-27.3.0~repack
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building palemoon using existing ./palemoon_27.3.0~repack.orig.tar.xz
dpkg-source: info: local changes detected, the modified files are:
 palemoon-27.3.0~repack/security/nss/lib/ssl/Makefile
dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/palemoon_27.3.0~repack-1.diff.GTB1VL
dpkg-source: info: you can integrate the local changes with dpkg-source --commit
dpkg-buildpackage: error: dpkg-source -b palemoon-27.3.0~repack gave error exit status 2

where /tmp/palemoon_27.3.0~repack-1.diff.GTB1VL:

Code: Select all

Description: <short summary of the patch>
 TODO: Put a short summary on the line above and replace this paragraph
 with a longer explanation of this change. Complete the meta-information
 with other relevant fields (see below for details). To make it easier, the
 information below has been extracted from the changelog. Adjust it or drop
 it.
 .
 palemoon (27.3.0~repack-1) obs; urgency=medium
 .
   * New major upstream release.
Author: Steven Pusser <stevep@mxlinux.org>

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: <vendor|upstream|other>, <url of original patch>
Bug: <url in upstream bugtracker>
Bug-Debian: https://bugs.debian.org/<bugnumber>
 Bug-Ubuntu: https://launchpad.net/bugs/<bugnumber>
Forwarded: <no|not-needed|url proving that it has been forwarded>
Reviewed-By: <name and email of someone who approved the patch>
Last-Update: <YYYY-MM-DD>

--- palemoon-27.3.0~repack.orig/security/nss/lib/ssl/Makefile
+++ palemoon-27.3.0~repack/security/nss/lib/ssl/Makefile
@@ -39,12 +39,11 @@ CSRCS       += unix_err.c
 endif
 endif

-# Enable key logging by default in debug builds, but not opt builds.
-# Logging still needs to be enabled at runtime through env vars.
-NSS_ALLOW_SSLKEYLOGFILE ?= $(if $(BUILD_OPT),0,1)
-ifeq (1,$(NSS_ALLOW_SSLKEYLOGFILE))
+# Enable key logging by default in all builds
+#NSS_ALLOW_SSLKEYLOGFILE ?= $(if $(BUILD_OPT),0,1)
+#ifeq (1,$(NSS_ALLOW_SSLKEYLOGFILE))
 DEFINES += -DNSS_ALLOW_SSLKEYLOGFILE=1
-endif
+#endif

 #######################################################################
 # (5) Execute "global" rules. (OPTIONAL)                              #

which is only administrative changes to learn to do for me, I hope.

Modifying my patch to read:

Code: Select all

Description: patch to allow SSL-key logging

Forwarded: not-needed
Bug: https://forum.palemoon.org/viewforum.php?f=57
Bug-Devuan: https://bugs.devuan.org
Author: Miroslav Rovis <miro.rovis@croatiafidelis.hr>

---
--- security/nss/lib/ssl/Makefile
+++ security/nss/lib/ssl/Makefile
@@ -39,12 +39,11 @@ CSRCS       += unix_err.c
 endif
 endif

-# Enable key logging by default in debug builds, but not opt builds.
-# Logging still needs to be enabled at runtime through env vars.
-NSS_ALLOW_SSLKEYLOGFILE ?= $(if $(BUILD_OPT),0,1)
-ifeq (1,$(NSS_ALLOW_SSLKEYLOGFILE))
+# Enable key logging by default in all builds
+#NSS_ALLOW_SSLKEYLOGFILE ?= $(if $(BUILD_OPT),0,1)
+#ifeq (1,$(NSS_ALLOW_SSLKEYLOGFILE))
 DEFINES += -DNSS_ALLOW_SSLKEYLOGFILE=1
-endif
+#endif

    #######################################################################
 # (5) Execute "global" rules. (OPTIONAL)                              #


But I see that my problem consists in that I can not apply my patch by myself, I have to let Devuan/Debian tools know about the patch, and let probably dpkg-buildpackage apply my patch...

Hmmm... How do I do that? Maybe I find out on my own before people start waking up (it's Sun 21 May 04:47:37 UTC 2017).

Or wait, haven't read carefully. It said to me in the error:

Code: Select all

dpkg-source: info: you can integrate the local changes with dpkg-source --commit

but neither do I (yet) understand exactly how to do that...

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon on Devuan fails

Unread postby miroR » Sun, 21 May 2017, 05:08

That was much simpler than I feared:

Code: Select all

mr@localhost:~/palemoon-27.3.0~repack$ dpkg-source --commit
dpkg-source: info: local changes detected, the modified files are:
 palemoon-27.3.0~repack/security/nss/lib/ssl/Makefile
Enter the desired patch name: allow-sslkeylogfile.patch

Select an editor.  To change later, run 'select-editor'.
  1. /bin/nano        <---- easiest
  2. /usr/bin/vim.basic
  3. /usr/bin/vim.tiny

Choose 1-3 [1]: 2
dpkg-source: info: local changes have been recorded in a new patch: palemoon-27.3.0~repack/debian/patches/allow-sslkeylogfile.patch
mr@localhost:~/palemoon-27.3.0~repack$

And I'll try building now:

Code: Select all

$ dpkg-buildpackage -d -j4 |& tee ~/dpkg-buildpackage-d-j4_$(date +%y%m%d_%H%M)_localhost

where the |& tee ... is producing ~/dump_170521_0347_localhost currently (I have UTC in my machine).

But:

Code: Select all

./dom/html/test/allowMedia.sjs
./dom/media/test/allowed.sjs
./security/manager/ssl/tests/mochitest/mixedcontent/alloworigin.sjs
./.pc/allow-sslkeylogfile.patch
mr@localhost:~/palemoon-27.3.0~repack$ find ./ -name 'allow-ss*'
./debian/patches/allow-sslkeylogfile.patch
./.pc/allow-sslkeylogfile.patch
mr@localhost:~/palemoon-27.3.0~repack$ dpkg-buildpackage -d -j4 |& tee ~/dpkg-buildpackage-d-j4_$(date +%y%m%d_%H%M)_localhost
dpkg-buildpackage: source package palemoon
dpkg-buildpackage: source version 27.3.0~repack-1
dpkg-buildpackage: source distribution obs
dpkg-buildpackage: source changed by Steven Pusser <stevep@mxlinux.org>
 dpkg-source --before-build palemoon-27.3.0~repack
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean --parallel
   dh_testdir -O--parallel
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/home/mr/palemoon-27.3.0~repack'
rm -f mozconfig
dh_auto_clean
make[1]: Leaving directory '/home/mr/palemoon-27.3.0~repack'
   dh_clean -O--parallel
 dpkg-source -b palemoon-27.3.0~repack
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building palemoon using existing ./palemoon_27.3.0~repack.orig.tar.xz
can't find file to patch at input line 11
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Description: patch to allow SSL-key logging
|
|Forwarded: not-needed
|Bug: https://forum.palemoon.org/viewforum.php?f=57
|Bug-Devuan: https://bugs.devuan.org
|Author: Miroslav Rovis <miro.rovis@croatiafidelis.hr>
|
|---
|--- security/nss/lib/ssl/Makefile
|+++ security/nss/lib/ssl/Makefile
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
dpkg-source: info: if patch 'allow-sslkeylogfile.patch' is correctly applied by quilt, use 'quilt refresh' to update it
dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/allow-sslkeylogfile.patch/ --reject-file=- < palemoon-27.3.0~repack.orig.FOvCQM/debian/patches/allow-sslkeylogfile.patch gave error exit status 1
dpkg-buildpackage: error: dpkg-source -b palemoon-27.3.0~repack gave error exit status 2
mr@localhost:~/palemoon-27.3.0~repack$

So it's

Code: Select all

$ quilt refresh

to try next...

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon on Devuan fails

Unread postby miroR » Sun, 21 May 2017, 05:27

Code: Select all

mr@localhost:~/palemoon-27.3.0~repack$ quilt refresh |& tee ~/quilt_refresh_$(date +%y%m%d_%H%M)_$(hostname)
Nothing in patch debian/patches/allow-sslkeylogfile.patch
mr@localhost:~/palemoon-27.3.0~repack$ cp -iav ~/allow-sslkeylogfile.patch debian/patches/
cp: overwrite ‘debian/patches/allow-sslkeylogfile.patch’? y
‘/home/mr/allow-sslkeylogfile.patch’ -> ‘debian/patches/allow-sslkeylogfile.patch’
mr@localhost:~/palemoon-27.3.0~repack$


Code: Select all

mr@localhost:~/palemoon-27.3.0~repack$ quilt refresh |& tee ~/quilt_refresh_$(date +%y%m%d_%H%M)_$(hostname)
Patch debian/patches/allow-sslkeylogfile.patch is unchanged
mr@localhost:~/palemoon-27.3.0~repack$ cat debian/patches/allow-sslkeylogfile.patch
Description: patch to allow SSL-key logging

Forwarded: not-needed
Bug: https://forum.palemoon.org/viewforum.php?f=57
Bug-Devuan: https://bugs.devuan.org
Author: Miroslav Rovis <miro.rovis@croatiafidelis.hr>

---
mr@localhost:~/palemoon-27.3.0~repack$

which is an empty patch.

It isnt' taking my patch... Or...

I checked it. The security/nss/lib/ssl/Makefile is untouched. No, it's not applying it... How is this done?

User avatar
filip
Hobby Astronomer
Hobby Astronomer
Posts: 15
Joined: Wed, 08 Feb 2017, 15:52
Location: Serbia

Re: Building Pale Moon on Devuan fails

Unread postby filip » Sun, 21 May 2017, 13:18

I'm afraid I cannot be of much help when it comes to grsecurity kernel, however it would certanly be a good idea to boot into default 3.16 just to verify that the issue is actually with the kernel, and not with the PM build itself! ;) :)

@quilt:

Well, that thing does tend to be mind boggling at times ( read: annoying as hell, especially with emptying the patch file(s) on refresh ).
Anyway, in the nutshell, whenever it starts acting like that, just start from scratch. It's much easier then dealing with it.

- Backup the "mozconfig" from /debian
- Delete the entire source & unpack again
- Put the "mozconfig" back in place
- Manually patch the file(s) you want ( and verify that it's actually patched/changed )
- Run "dpkg-source --commit" ( verify that the patch file created in /debian/patches is valid/non-empty )
- Build. :)

Instead, I should have edited the debian/mozconfig, should have added:

Code: Select all
ac_add_options --disable-dbus

and things into it.


:thumbup:

Hey, thanks! That was great. It does sound very similar to what I read in packaging-tutorial.en.pdf and such, only so much quicker and, since I read those for hours :) these days, easier!


:thumbup:

I know those pains... :D I'd say that debian packaging is perfectly comparable to git. Very powerfull and actually easy to use once you learn it. The bad part: that learning it is a major PITA... :D

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon on Devuan fails

Unread postby miroR » Sun, 21 May 2017, 15:00

On too short notice editing is disallowed... I only now noticed that the title should read:
Building Pale Moon in Devuan fails...
But, not even the post that I posted some five or more hours ago can be edited anymore...
---
I am now browsing with Pale Moon that I built, and it is logging SSL-keys!

I'll try and tell a story about it, but it's a lot...

But in short, 'man quilt' is (somewhat) unfriendly, not stressing the important deals of the method that is uses clearly enough. Only after reading further where 'man quilt' links and suggests, and esp. the plain and good old README of theinstalled package, did I figure out...

Will try and be back to explain.
Dear filip, are you aware that without your help I would still be plodding through manuals and things, and at least a day or two away from having compiled this Pale Moon that I now proudly use in my Devuan?
A big thanks to you! And, your icon is one of the best I have seen recently, and in longer time...

Regards!

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon in Devuan fails

Unread postby miroR » Sun, 21 May 2017, 16:17

I repeated the procedure, but successfully, like this (starting from scratch; actually you'll be able to trust my word on the procedure below only after I have updated my Air-Gapped1 by basically following what I now write below):

Code: Select all

dpkg-source -x palemoon_27.3.0~repack-1.dsc
cd palemoon-27.3.0~repack

vi debian/mozconfig

It's very useful to note that I based my mozconfig on Walter Dnes's one from his unofficial package that I used, and which would have also worked, but for the paxrat non-familiarity of mine...2

My mistake was to go straight for (don't do this yet!):

Code: Select all

patch -p0 < ~/allow-sslkeylogfile.patch

Nope! The important detail about quilt, is it works only on files that it knows of. IOW, ths file that my patch modifies:

Code: Select all

security/nss/lib/ssl/Makefile

needs to be added to quilt. And more. But adding files to quilt is not clearly stressed in the "man quilt" for first time readers...

The best instructions I found in /usr/share/doc/quilt/README.gz:

Code: Select all

Typical Usages: New patches; Importing patches; Patch management
======================================================================

Add new patches:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. create a new patch: quilt new {patchname, e.g., sysctl_fix.patch}

2. add/edit file(s): quilt edit filepath
or:
2a. add file(s) to patch: quilt add {filepath}
2b. manual edit file(s) use your $editor

3. update the patch: quilt refresh
3b. list the patch description: quilt header [patch]
3c. update the patch description: quilt header -e [patch]


( And /usr/share/doc/quilt/quilt.pdf is a very good read, and necessary: it's hands on and simple. )

So, from my ~/.bash_history, here's how I dealt with this source patching issue. I'm giving the history lines that I will likely try and follow exactly when I install all these in Air-Gapped, as only then will I be able to verify this procedure, as I noted at the top of this post.

Code: Select all

ls -lRa debian/patches/
ls -lRa .pc
cat debian/patches/series

Notice what you see. What exists and what not yet... And...

Code: Select all

quilt new allow-sslkeylogfile.patch

...[And]...

Code: Select all

ls -lRa debian/patches/
ls -lRa .pc
cat debian/patches/series

...[And] ...how it changes.
( And you can repeat it later as well. )

This was the crucial move (or it was crucial for me to understand that I needed to do it):

Code: Select all

quilt add security/nss/lib/ssl/Makefile

Before we patch the file, pls. note the first 6 lines of that Makefile that needs to be fixed so Palemoon can log SSL-keys:

Code: Select all

tail -24 security/nss/lib/ssl/Makefile
tail -24 security/nss/lib/ssl/Makefile | head -6

The if condition there is intact. And it needs to be commented out for our purpose!

Now that the file is added, i.e. now that quilt knows about it, it doesn't matter how you edit it. IOW, simply:

Code: Select all

patch -p0 < ~/allow-sslkeylogfile.patch

did if for me.

Code: Select all

tail -24 security/nss/lib/ssl/Makefile
tail -24 security/nss/lib/ssl/Makefile | head -6

The if condition there has been commented out (or the reader didn't do it right). The compiled-to-be Palemoon will serve our purpose!

Code: Select all

quilt refresh
quilt header
quilt header allow-sslkeylogfile.patch
quilt header -e allow-sslkeylogfile.patch
quilt files
quilt diff
quilt push

I actually don't recall why I did all the above, but in essence...
In essence, I haven't later changed the patch below, not since the post of mine which is some fourth previous from here, and which I am using now by quoting it.

In essence, the above commands should get your patch again just like that, basically by manually editing after you, if I remember correctly, issue:

Code: Select all

quilt header -e allow-sslkeylogfile.patch
.
Modifying my patch to read:

Code: Select all

Description: patch to allow SSL-key logging

Forwarded: not-needed
Bug: https://forum.palemoon.org/viewforum.php?f=57
Bug-Devuan: https://bugs.devuan.org
Author: Miroslav Rovis <miro.rovis@croatiafidelis.hr>

---
--- security/nss/lib/ssl/Makefile
+++ security/nss/lib/ssl/Makefile
@@ -39,12 +39,11 @@ CSRCS       += unix_err.c
 endif
 endif

-# Enable key logging by default in debug builds, but not opt builds.
-# Logging still needs to be enabled at runtime through env vars.
-NSS_ALLOW_SSLKEYLOGFILE ?= $(if $(BUILD_OPT),0,1)
-ifeq (1,$(NSS_ALLOW_SSLKEYLOGFILE))
+# Enable key logging by default in all builds
+#NSS_ALLOW_SSLKEYLOGFILE ?= $(if $(BUILD_OPT),0,1)
+#ifeq (1,$(NSS_ALLOW_SSLKEYLOGFILE))
 DEFINES += -DNSS_ALLOW_SSLKEYLOGFILE=1
-endif
+#endif

    #######################################################################
 # (5) Execute "global" rules. (OPTIONAL)                              #



And then:

Code: Select all

dpkg-buildpackage -d -j4

compiles the SSL-key logging Pale Moon (it did for me :) ).

---


1 LINKS Air-Gapped, cloning. If I'm late to post these links, pls. find them in a later post of mine.

2 Similarly I don't want dbus, and I don't want pulseaudio in my system, and of course we belong to the init-freedom users who strongly dislike systemd... I left Debian because of it.
Can't test that other install because I only need one Palemoon, and posting this procedure took precedence over testing if that $HOME installed Palemoon would work if I boot with vmlinuz-3.16.0-4-amd64.

User avatar
filip
Hobby Astronomer
Hobby Astronomer
Posts: 15
Joined: Wed, 08 Feb 2017, 15:52
Location: Serbia

Unread postby filip » Sun, 21 May 2017, 22:09

I am now browsing with Pale Moon that I built, and it is logging SSL-keys!

Glad to hear, congratulations!!! :clap: :thumbup:

Dear filip, are you aware that without your help I would still be plodding through manuals and things, and at least a day or two away from having compiled this Pale Moon that I now proudly use in my Devuan?
A big thanks to you! And, your icon is one of the best I have seen recently, and in longer time...


You're most welcome! :)

@logo/avatar:

Thanks!
Yeah, it is cool really. However I'm not the author.
I've dug it out of some FTP site a long time ago but couldn't find out who made it.
Anyway, whoever it is, kudos to him/her! :)

...
needs to be added to quilt. And more. But adding files to quilt is not clearly stressed in the "man quilt" for first time readers...


Well, quilt.... :crazy: :D

Anyhow, are you sure that the:

Code: Select all

patch -p0 < ~/allow-sslkeylogfile.patch

... actually does the job right?

I'm not saying that you're wrong here, it's just that I never had to resort to the whole "quilt add" way ( and I have patched and built a sh*t load of packages )... Quilt would always detect and properly record any changes to the src.

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re:

Unread postby miroR » Thu, 06 Jul 2017, 10:57

I'm browsing with Lynx text browser, not so used to, sorry for errors, My Pale Moon currently broken, and with the same error...
filip wrote:
I am now browsing with Pale Moon that I built, and it is logging SSL-keys!

Glad to hear, congratulations!!! :clap: :thumbup:

Dear filip, are you aware that without your help I would still be plodding through manuals and things, and at least a day or two away from having compiled this Pale Moon that I now proudly use in my Devuan?
A big thanks to you! And, your icon is one of the best I have seen recently, and in longer time...


You're most welcome! :)

@logo/avatar:

Thanks!
Yeah, it is cool really. However I'm not the author.
I've dug it out of some FTP site a long time ago but couldn't find out who made it.
Anyway, whoever it is, kudos to him/her! :)

...
needs to be added to quilt. And more. But adding files to quilt is not clearly stressed in the "man quilt" for first time readers...


Well, quilt.... :crazy: :D
I gave links, and they should tell you all. Thought to show you, but my migration from Gentoo to Devuan has not completed for my Apache/PHP to post for you that it worked, on https://www.CroatiaFidelis.hr/foss/cap/ ... About your question below, I mean:
Anyhow, are you sure that the:

Code: Select all

patch -p0 < ~/allow-sslkeylogfile.patch

... actually does the job right?

I'm not saying that you're wrong here, it's just that I never had to resort to the whole "quilt add" way ( and I have patched and built a sh*t load of packages )... Quilt would always detect and properly record any changes to the src.
... And I need to go through and remember how I compiled Pale Moon almost two months ago... Next... (I really miss it, and no other browser do I trust for use online really, on top of, I think Firafox would ask me to install dbus, which I don't want to do.)

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon on Devuan fails

Unread postby miroR » Thu, 06 Jul 2017, 11:00

Because since some updated/salvaging in my Devuan:
Broken packages in Ascii, how to fix? (Beware of Debian Stretch)
https://dev1galaxy.org/viewtopic.php?id=1115
I get this error when I try to start Pale Moon:

Code: Select all

$ palemoon
out of memory
Assertion failure: [unhandlable oom] OOM in createJitRuntime, at /home/mr/palemoon-27.3.0~repack/js/src/jscntxt.cpp:1183
Segmentation fault

De ja vu.

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon on Devuan fails

Unread postby miroR » Thu, 06 Jul 2017, 12:09

That repo of Steve Pusser is not signed, right? And so this is (only probably) still fine:

Code: Select all

$ dget http://download.opensuse.org/repositories/home:/stevenpusser/Debian_8.0/palemoon_27.3.0~repack-1.dsc
dget: retrieving http://download.opensuse.org/repositories/home:/stevenpusser/Debian_8.0/palemoon_27.3.0~repack-1.dsc
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   382  100   382    0     0   4915      0 --:--:-- --:--:-- --:--:--  4961
100  1264  100  1264    0     0    766      0  0:00:01  0:00:01 --:--:-- 21423
dget: using existing palemoon_27.3.0~repack.orig.tar.xz
dget: using existing palemoon_27.3.0~repack-1.debian.tar.xz
palemoon_27.3.0~repack-1.dsc:
dscverify: palemoon_27.3.0~repack-1.dsc failed signature check:
gpg: no valid OpenPGP data found.
gpg: processing message failed: Unknown system error
Validation FAILED!!
Well, was (probably) so the last time too... Same sources...

User avatar
filip
Hobby Astronomer
Hobby Astronomer
Posts: 15
Joined: Wed, 08 Feb 2017, 15:52
Location: Serbia

Unread postby filip » Fri, 07 Jul 2017, 14:51

miroR wrote:
Anyhow, are you sure that the:

Code: Select all

patch -p0 < ~/allow-sslkeylogfile.patch

... actually does the job right?

I'm not saying that you're wrong here, it's just that I never had to resort to the whole "quilt add" way ( and I have patched and built a sh*t load of packages )... Quilt would always detect and properly record any changes to the src.
... And I need to go through and remember how I compiled Pale Moon almost two months ago... Next... (I really miss it, and no other browser do I trust for use online really, on top of, I think Firafox would ask me to install dbus, which I don't want to do.)


If you kept the source directory, you can just rebuild the package again. ;)

Btw, you can also "add" patches to /debian simply by importing them directly like:

Code: Select all

quilt import /path/to/patch

Works fine atleast for regular diffs.

However, I'd suggest you to first fix the packages issue*:
miroR wrote:Because since some updated/salvaging in my Devuan:
Broken packages in Ascii, how to fix? (Beware of Debian Stretch)
https://dev1galaxy.org/viewtopic.php?id=1115
I get this error when I try to start Pale Moon:

Code: Select all

$ palemoon
out of memory
Assertion failure: [unhandlable oom] OOM in createJitRuntime, at /home/mr/palemoon-27.3.0~repack/js/src/jscntxt.cpp:1183
Segmentation fault

De ja vu.

... since just rebuilding Palemoon might not be enough ( and it's probably not needed, if you fix the apt breakage first ).

miroR wrote:That repo of Steve Pusser is not signed, right? And so this is (only probably) still fine:


Packages (.debs) are signed, source is not ( unless I'm missing the obvious ).

*
Off-topic:
Issue is that "/lib/init/vars.sh" was moved from "initscripts" to "sysvinit-utils" package, however dependencies were not sorted unitil v2.88dsf-59.6 causing the "initscripts" to be upgraded first which is wrong as you have seen.
Anyway, try installing "sysvinit-utils" first:

Code: Select all

sudo apt install sysvinit-utils

if neccessary followed by:

Code: Select all

sudo dpkg --configure -a

and finally:

Code: Select all

sudo apt dist-upgrade

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon on Devuan fails

Unread postby miroR » Fri, 07 Jul 2017, 18:36

Lost one reply already.

Linkname: Re: [DNG] error processing package initscripts, because /lib/init/vars.sh missing
URL: https://lists.dyne.org/lurker/message/2 ... b7.en.html

The issue seems to be related with grsec:

$ uname -r
4.9.27-unofficial+grsec170512-22
$

Will be back.

Thanks for caring.

miroR
Fanatic
Fanatic
Posts: 102
Joined: Tue, 31 May 2016, 19:22

Re: Building Pale Moon on Devuan fails

Unread postby miroR » Fri, 07 Jul 2017, 18:48

And lost another bit of text. Lynx is a torture until you learn it, that is.
It's that I could go online with Pale Moon, in safe mode, but only in "normal" Mr Linux's kernel, stinking Mr Linux's kernel, of his and of his lieutenants, where there is hardly any security...

Like with:

4.9.0-3-amd64

except, I don't like being unsafe online...

See you later when I sort the grsecurity/Palemoon issues.

Might take time...


Return to “Bug reports (Linux & other)”

Who is online

Users browsing this forum: No registered users and 1 guest