jrb wrote:
After updating the certificate, the --no-check-certificate option isn't required.
Excellent work s243a! I ran through your procedure and it worked perfectly and I started to make a .pet using Debian Sid's ca-certificates figuring they would be the most up to date. Then I found this
ca-certificates-2019-03-08.pet lurking in my Downloads. Can't remember downloading it and searches haven't found it. It's more up to date than Sid and it downloaded your test package with no argument.
I would like to give credit to the creator, maybe they will see this and step forward.
Will install this .pet in the next update.
Thankyou, I'm glad it's working for you. I was surprised that you were able to get such new certificates to work
jrb wrote:
I'll write a script to move the offending files out of my save folder.
Precise-light comes with glibc-2.20. I know it says 2.10 in woof-installed-packages, sloppy work on my part. I suspect firefox-16 is too old to accomodate that.
I'm not sure, whether firefox-16 can use this version of glibc or not. I created an adrv yesterday, by using my
remaster sandbox script. The link is as follows:
adrv_precise_light-5.7.2.sfs
This "a drive" (aka adrv) has updated certificates, but not as new as the ones that you are using. It also has
Sc0ttman's package manager (pkg) installed on it [1]. I went a little crazy with the repos, and added all of the precise repos.
Here is my ~/.pkg/pkgrc file:
Code: Select all
WORKDIR=/root/pkg
REPONAME=precise-main
EX=deb
REPOFILE=Packages-ubuntu-precise-main
REPOURL1=http://archive.ubuntu.com/ubuntu/
REPOURL2=http://ftp.filearena.net/pub/ubuntu/
REPOURL3=
REPOURL4=
PKGSEARCH="list_pkg_names"
PKGSEARCHEXACT="pkg -ne"
DEPSEARCH="list_all_pkg_names"
DEPSEARCHEXACT="pkg -nea"
REPOFALLBACKS="noarch jessie-tor-main precise-multiverse precise-universe precise-restricted precise-security-main precise-security-multiverse precise-security-universe precise-security-restricted precise-updates-main precise-updates-universe precise-updates-multiverse precise-updates-restricted precise-backports-main precise-backports-universe precise-backports-multiverse precise-proposed-universe "
PKGSCOPE="one"
DEPSCOPE="all"
BLEDGE="no"
RDCHECK="yes"
AUTOCLEAN="no"
BUILDTOOL=petbuild
Notice the long list of fallback repos. I'm not sure what issues using so many repos might present. Something interesting though is the following:
Code: Select all
sandbox# /usr/sbin/pkg --names-all firefox_
firefox_11.0+build1-0ubuntu4
firefox_52.0.2+build1-0ubuntu0.12.04.1
also
Code: Select all
cd /var/packages
grep -rn . -e 'firefox_52' | cut -d '|' -f1
./Packages-ubuntu-precise-security-main:245:firefox_52.0.2+build1-0ubuntu0.12.04.1
./Packages-ubuntu-precise-updates-main:386:firefox_52.0.2+build1-0ubuntu0.12.04.1
So it looks like version 52 of firefox is available in the repos precise-security-main and also in precise-updates-main. I might give installing this a try. Note that I did the above commands in a sandbox. I tested booting with my adrv yesterday. pkg wasn't working even though it was on the adrv. Tonight I realized the problem is that the following files from my adrv:
Code: Select all
/root/.pkg/sources
/root/.pkg/sources-all
/root/.pkg/pkgrc
appear to be different than what is on my adrv after the first run of pkg. I'm guessing pkg thinks that I'm doing a new install and overwrites these files. The solution is to replace these files with those found on my adrv. Note that the last file can be generated from the previous two by doing the command:
I have "precise-main" set as the default repo because I suspect that it will likely have the greatest compatibility. PKG has an environmental variable called "
BLEDGE" (for
bleeding-edge) that will install the newest version of the pkg from all installed repos (verify?). I haven't tested this feature.
Anyway, I'll test pkg more on precise light and also see if I can figure out why these config files are overwritten on first run.
Another oddity, with my adrv is when I boot it the prompt says "sandbox"
Notes
-----------------------
1 - the version of pkg I installed on the adrv is
a fork that is part of
Merge Request #72.
Edit: I created a new version of my adrv
adrv_precise_light-5.7.2.sfs(not tested yet). I was installing the portable browser in a sandbox and it complained about the architecture being 64bits. This is because the sandbox was being run in a 64bit system. I think the solution to this is to create a wrapper function for uname.
, with libc6 blacklisted and possibly the portable browser installer included.
Edit 2: I figured out why the prompt says sandbox.
See post.