https://software.opensuse.org/download. … e=palemoon

James
Indiana/USA

Legal on Pale Moon potential packaging and distribution
https://dev1galaxy.org/viewtopic.php?id=1974

Regards!

https://www.croatiafidelis.hr/foss/dev1miro/

I have (with manual adjusting in /var/lib/apt/lists managed to apt-get install my:

$ palemoon --version
Moonchild Productions Pale Moon 27.8.3
$

from it.
Here the log how it went:

$ apt-get install palemoon
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be upgraded:
  palemoon
[...]

Oh, that doesn't belong here... Pls. go to:
A repo serving Pale Moon
https://dev1galaxy.org/viewtopic.php?id=1972

Regards!

Note that the output of apt-cache policy does not show the package as coming from a repository. It just lists /var/lib/dpkg/status instead. It know the package is there, but it can't tell where it came from. Packages installed with dpkg and packages installed from a repo that is no longer in the sources will show up that way.

Sorry to say that palemoon is not in the devuan repo. You're getting a false positive.

But why is apt not saying it does not have it in the repo?

A pretty old version (too old, I'd think), where and when did you get it?

Apt has to see  that palemoon is installed, because it's installed, in my case, and probably in your case too, with /dpkg -i <the-deb-pacakege>.

And surely, I scoured all the /var/lib/apt/lists and marginally in some lz4 compressed files (such as, this is the concrete decompression line:

lz4cat pkgmaster.devuan.org_merged_dists_ascii_main_Contents-amd64.lz4 > pkgmaster.devuan.org_merged_dists_ascii_main_Contents-amd64

), I was able to find string palemoon (and such), but it's not about the package palemoon...

Yeah, it's not in the Devuan repo. And I don't think it's in the Debian repo either, only in OBS, the Suse repo, where Steven Pusser maintains it (and he does a good job, for that).

Right, regards!

Your system:

palemoon is already the newest version (27.7.2~repack-1).

My system:

palemoon is already the newest version.
$ apt-cache policy palemoon
palemoon:
  Installed: 27.3.0~repack-1
  Candidate: 27.3.0~repack-1
  Version table:
 *** 27.3.0~repack-1 0
        100 /var/lib/dpkg/status

Different versions, but in each case it's the newest version that apt can see.

# apt-cache search palemoon
palemoon - Firefox-based, efficient and easy to use web browser
# apt-get -s install palemoon
Reading package lists... Done
Building dependency tree       
Reading state information... Done
palemoon is already the newest version (27.7.2~repack-1).
The following package was automatically installed and is no longer required:
  libpoppler68
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 80 not upgraded.
#

But that can only be since very recently that it is in Devuan.
Previously, Pale Moon just wasn't available in Devuan.
But great that it is now!
I've learned a lot here, and my experience sure might be useful for others with similar issues, anyway.
Also, is it not actually originally the Debian package, or is it originally Devuan maintained as Jaromil had suggested it would be great to have, anybody?
(Not that originally Debian maintained means anything bad.)
(Also I won't be installing it to be able to find out easily, even though binary Pale Moon, just as Firefox, usually have SSL-key logging enabled, and not disabled. I won't because I'm happy with what I conf'ed and compiled.)

Regards!

Or you could just install the .deb package, seems much simpler.

What to say about a comment like that!
Readers without (own-created) prejudice, have a look at:
Firefox-ESR, Palemoon, Apulse on Jessie
https://lists.dyne.org/lurker/message/2 … fd.en.html
where our leader explicitly asks:

and decide for yourself whether my efforts are maybe (be it only) minally useful in that direction?
I didn't reply to that question my Jaromil because I know that maintaing a package of that importance and value takes much more yet than I am currently able to achieve, but I took good notice.
But I'd really prefer no byke-shedding remarks, pls.
I don't want any flames, and if anybody does, you'll be left without a reply from me. I simply try to use my time for what is useful.

Regards!

# diff -u BAK/sources.list_180203_1908 /etc/apt/sources.list
--- BAK/sources.list_180203_1908        2017-12-01 15:56:21.000000000 +0000
+++ /etc/apt/sources.list       2018-02-23 09:08:16.861440857 +0000
[...]
@@ -32,3 +32,11 @@
 # Devuan repositories
 deb tor+https://packages.devuan.org/merged ceres main contrib non-free
 deb-src tor+https://packages.devuan.org/merged ceres main contrib non-free
+deb tor+https://pkgmaster.devuan.org/merged/ jessie main contrib non-free
+deb tor+https://pkgmaster.devuan.org/merged/ jessie-backports main contrib non-free
+deb tor+https://pkgmaster.devuan.org/devuan/ jessie-proposed main contrib non-free
+deb tor+https://pkgmaster.devuan.org/devuan/ jessie-proposed-backports main contrib non-free
+deb tor+https://pkgmaster.devuan.org/devuan/ jessie-proposed-security main contrib non-free
+deb tor+https://pkgmaster.devuan.org/merged/ jessie-proposed-updates main contrib non-free
+deb tor+https://pkgmaster.devuan.org/merged/ jessie-security main contrib non-free
+deb tor+https://pkgmaster.devuan.org/merged/ jessie-updates main contrib non-free

IOW, I needed to add back in the Jessie sources, and then after the usual apt-get update was able to do:

apt-get install gcc-4.9 g++-4.9 --install-recommends |& tee ~mr/LOG_/apt-get_install_gcc-4.9_g++-4.9--install-recommends_$(date +%y%m%d_%H%M%S)_O

( that was the real command, I simply hit Ctrl-R in my xterm terminal to search in the history, and then typed "apt-g" and there it popped up for me to show it to you, gentle reader )
And then I got:

# ls -l ~mr/LOG_/apt-get_install_gcc-4.9_g++-4.9--install-recommends_180223_093129_O
-rw-r--r-- 1 root root 4075 2018-02-23 09:32 /home/mr/LOG_/apt-get_install_gcc-4.9_g++-4.9--install-recommends_180223_093129_O
#

And it looks:
# cat ~mr/LOG_/apt-get_install_gcc-4.9_g++-4.9--install-recommends_180223_093129_O  >> This-file-that-I-prepare-for-posting-but-cut-short-a-lot

[...]
The following additional packages will be installed:
  cpp-4.9 gcc-4.9-base libasan1 libcloog-isl4 libgcc-4.9-dev libisl10
  libstdc++-4.9-dev
Suggested packages:
[...]
The following NEW packages will be installed:
  cpp-4.9 g++-4.9 gcc-4.9 libasan1 libcloog-isl4 libgcc-4.9-dev libisl10
  libstdc++-4.9-dev
The following packages will be upgraded:
  gcc-4.9-base
1 upgraded, 8 newly installed, 0 to remove and 174 not upgraded.
[...]
Running external script: '/usr/bin/test -x /sbin/paxrat && /sbin/paxrat 1>/dev/null || true'
Running external script: 'if [ -x /usr/bin/rkhunter ] && grep -qiE '^APT_AUTOGEN=.?(true|yes)' /etc/default/rkhunter; then /usr/share/rkhunter/scripts/rkhupd.sh; fi'

I thought I'd post this just so if some other Devuaner/Debianers comese across a similar issue.

Regards!

It's safe and normal to have multiple versions of gcc.

Yes, but you will lose the gcc's that do not belong to your release, such as I lost gcc-4 and g++-4 that do not belong to testing/unstable, i.e. Ascii/Ceres.

Interesting to here that.

Yep! That's what I noted in:
Pale Moon and uBlock0 on a grsec-hardened kernel 3
https://www.croatiafidelis.hr/foss/cap/ … ock0-3.php
at the top.
I also write there that you devs of Devuan/(and Debian) need to be commended for good maintenace at:
[ same title, just sequence number 1 ]
https://www.croatiafidelis.hr/foss/cap/ … ock0-1.php

Looks like there's a newer version of 4.9 in jessie-security:

~$ apt-cache policy gcc-4.8
gcc-4.8:
  Installed: 4.8.4-1
  Candidate: 4.8.4-1
  Version table:
 *** 4.8.4-1 0
        500 http://pkgmaster.devuan.org/merged/ jessie/main amd64 Packages
        500 http://auto.mirror.devuan.org/merged/ jessie/main amd64 Packages
        500 http://debian.csail.mit.edu/debian/ jessie/main amd64 Packages
        100 /var/lib/dpkg/status

~$ apt-cache policy gcc-4.9
gcc-4.9:
  Installed: 4.9.2-10
  Candidate: 4.9.2-10+deb8u1
  Version table:
     4.9.2-10+deb8u1 0
        500 http://pkgmaster.devuan.org/merged/ jessie-security/main amd64 Packages
        500 http://auto.mirror.devuan.org/merged/ jessie-security/main amd64 Packages
 *** 4.9.2-10 0
        500 http://pkgmaster.devuan.org/merged/ jessie/main amd64 Packages
        500 http://auto.mirror.devuan.org/merged/ jessie/main amd64 Packages
        500 http://debian.csail.mit.edu/debian/ jessie/main amd64 Packages
        100 /var/lib/dpkg/status

Installing uBlock Origin breaks Pale Moon on grsec-hardened kernel
https://forum.palemoon.org/viewtopic.php?f=46&t=18389

which recently I think I feel it might be because of compiler...

And that what I thought was, eventually, a successfuly compilation, is not so, but causes those issues, because it's with gcc-6:

Building Pale Moon on Devuan fails
https://forum.palemoon.org/viewtopic.ph … 20#p135249

(see also previous to that post by Steve, who is a Debian dev, and also he let me know that he did install later with gcc-4.9)

Somewhere in Palemoon talks by their devs, they mention it needs to be compiled with gcc-4.

Question: since there are no gcc-4 available in my Ceres (and I also have Ascii in my sources), I guess I need to add Jessie to my sources to, hopefully, be able to install gcc-4 (likely gcc-4.9).

Is that acceptable? Having all those gcc compilers? Would that mean instability for my system?

Regards!

Asking for help on Pale Moon forum as well:
Building Pale Moon on Devuan fails
https://forum.palemoon.org/viewtopic.php?f=57&t=15751

And receiving, and also providing some tips at the newest post:
( same title as above, actually it's the same topic )
https://forum.palemoon.org/viewtopic.ph … 51#p114421

But, I think I talked my Palemoon to log SSL-keys... Taken before I posted that, but it's this one, I think:

4523354827de15973a92035031d6ea6a480dc5311650f2c7f6fcec51279535a0  dump_170521_1448_loc.pcap

However, I got to rush now... There're also some not-so-good realizations... But, gotta go.