Page 1 of 2

GhostBSD 10.3 new pkgs repository

Posted: Fri Jun 02, 2017 8:01 pm
by ASX
Intro
GhostBSD typically made use of FreeBSD repositories for pkgs update.
FreeBSD offer two set of repositories: "quarterly" and "latest".
"Quarterly" is the default repo since FreeBSD 10.2/GhostBSD 10.3, supposedly it is more stable and reliable than the "latest" repo, and receive only minimal updates, for three months, and the end of the quarter a new "quarterly" repos is branched from "latest".

Unfortunately, the quarterly repo was not as stable and reliable as expected, and of course, you can see yourself that there is a flaw in the current workflow: when a new "quarterly" repo is branched it is exactly in pair with the "latest" repository, can't be more stable or reliable than "latest" itself.

We have discussed a lot (internally, between devs), about basing our repos on ports/head branch or on ports/quarterly branch, we were ready to tradeoff the latest and greatest for some more stability, but the latest quarterly switch and the related issues, solved our doubts instantly: we will make use of the "ports/head" (which correspond tpo "latest" pkg repo), for our own repositories.

Fallback
Producing a repository require some work, and some testing, for these reasons we will have three repos for each Release and for each arch:
- test (used from devs, and from users willing to help testing)
- current (the "normal" / default repository
- previous (this is what was the "current" before latest round of updates, it is meant to be a quick fallback in case something wrong went unnoticed in the "current" repository.


How to
The "test" repository is the only one available right now, to make use of it:

# create a /usr/local/etc/pkg/repos/GhostBSD.conf file:

# amd64

Code: Select all

GhostBSD: {
  url: "http://pkg.GhostBSD.org/GhostBSD-10/amd64/test",
  enabled: yes
}
# i386

Code: Select all

GhostBSD: {
  url: "http://pkg.GhostBSD.org/GhostBSD-10/i386/test",
  enabled: yes
}
to verify which repositories are configured use:

Code: Select all

pkg -vv
The first time, you should reinstall all packages, using:

Code: Select all

pkg upgrade -f -r GhostBSD
to disable the FreeBSD repository permanently, create a /usr/local/etc/pkg/repos/FreeBSD.conf file:

Code: Select all

FreeBSD: {
  enabled: no
}
After disabling the FreeBSD repository, you can use the usual pkg syntax, whitout the need to specify the "-r GhostBSD" repository.

Re: GhostBSD 10.3 new pkgs repository

Posted: Sat Aug 05, 2017 9:13 am
by NevilleGoddard
I did a clean install of GhostBSD 10.3 and I immediately disabled the FreeBSD repository and enabled the GhostBSD test repository.
It was on my intel graphics laptop. I installed the amd64 xfce iso with UFS and FreeBSD bootloader.
I then ran pkg upgrade -f
The update went fine (although there were some messages about package conflicts) and it booted straight into the desktop.
The only problems I could see right away were that I had lost my applications menu on the panel and the wireless icon was different. I could easily get the applications menu back.
Fixing the network manager icon took a bit more work.
I ran the command :

networkmgr

and I got doas: operation not permitted so I thought it was a doas config problem.

I went to /usr/local/etc/doas.conf in my GhostBSD10.3 machine and compared it to the same file in my GhostBSD11 machine remembering I didn't have this problem with GhostBSD11.
The two files were quite different with the 10.3 file having much less text.
I then edited this file to include the missing sections on netcardmgr, detect-nics, detect-wifi, ifconfig, service and wpa_supplicant.
Now all is well. 8-)
I can't find anything else wrong.
My only "complaint" was that the original wallpapers are gone. :cry:
That and it was too easy. :D
Thanks a lot!

Re: GhostBSD 10.3 new pkgs repository

Posted: Sat Aug 05, 2017 9:38 am
by ASX
NevilleGoddard wrote:I went to /usr/local/etc/doas.conf in my GhostBSD10.3 machine and compared it to the same file in my GhostBSD11 machine remembering I didn't have this problem with GhostBSD11.
The two files were quite different with the 10.3 file having much less text.
I then edited this file to include the missing sections on netcardmgr, detect-nics, detect-wifi, ifconfig, service and wpa_supplicant.
Now all is well. 8-)
The repos for 10.3 and 11.x are not updated at the same time, with 11.1 being usually more up to date, and in this specific case doas has remained behind in 10.x.

A next 10.3 build is planned shortly (I was about to start it yesterday, but ericbsd was about to add other changes, and we have decided to wait until his latest changes will flow in. Just for your info. ;)

Re: GhostBSD 10.3 new pkgs repository

Posted: Sat Aug 05, 2017 10:18 am
by NevilleGoddard
Can we create our own GhostBSD-10.3 ISOs?
Can this be done by editing the ghostbsd.defaults.conf file in ghostbsd-build?

Re: GhostBSD 10.3 new pkgs repository

Posted: Sat Aug 05, 2017 11:11 am
by ASX
NevilleGoddard wrote:Can we create our own GhostBSD-10.3 ISOs?
Can this be done by editing the ghostbsd.defaults.conf file in ghostbsd-build?
Yes and yes! Have fun! :D

Re: GhostBSD 10.3 new pkgs repository

Posted: Sat Aug 05, 2017 11:21 am
by ASX
Note that on github is stored also the previous "branch", 10.3 of ghostbsd-build

https://github.com/GhostBSD/ghostbsd-bu ... .3-Release

Re: GhostBSD 10.3 new pkgs repository

Posted: Tue Aug 08, 2017 8:49 am
by ASX
A new round of updates is available for 10.3 amd64 and 10.3 i386, built from ports as of 2017-08-05.

Re: GhostBSD 10.3 new pkgs repository

Posted: Tue Aug 08, 2017 8:52 am
by NevilleGoddard
My laptop with 10.3 is running extremely well.
Will update now.

Thanks a bunch. ;)

Re: GhostBSD 10.3 new pkgs repository

Posted: Tue Aug 08, 2017 11:47 pm
by NevilleGoddard
I tried to update my GhostBSD 10.3 with the new updates but I got this:

Number of packages to be installed: 7
Number of packages to be upgraded: 119
Number of packages to be reinstalled: 231

The process will require 355 MiB more space.

Proceed with this action? [y/N]: y
[1/361] Reinstalling libxml2-2.9.4...
[1/361] Extracting libxml2-2.9.4: 100%
[2/361] Reinstalling libXdmcp-1.1.2...
[2/361] Extracting libXdmcp-1.1.2: 100%
[3/361] Reinstalling libXau-1.0.8_3...
[3/361] Extracting libXau-1.0.8_3: 100%
[4/361] Reinstalling libxcb-1.12_2...
[4/361] Extracting libxcb-1.12_2: 100%
[5/361] Upgrading pciids from 20170525 to 20170701...
[5/361] Extracting pciids-20170701: 100%
[6/361] Reinstalling libX11-1.6.5,1...
[6/361] Extracting libX11-1.6.5,1: 100%
[7/361] Reinstalling libpciaccess-0.13.5...
[7/361] Extracting libpciaccess-0.13.5: 100%
[8/361] Reinstalling libfontenc-1.1.3_1...
[8/361] Extracting libfontenc-1.1.3_1: 100%
[9/361] Reinstalling libffi-3.2.1...
[9/361] Extracting libffi-3.2.1: 100%
[10/361] Reinstalling libXfixes-5.0.3...
[10/361] Extracting libXfixes-5.0.3: 100%
[11/361] Reinstalling libXext-1.3.3_1,1...
[11/361] Extracting libXext-1.3.3_1,1: 100%
[12/361] Reinstalling gettext-runtime-0.19.8.1_1...
[12/361] Extracting gettext-runtime-0.19.8.1_1: 100%
[13/361] Reinstalling freetype2-2.8...
[13/361] Extracting freetype2-2.8: 100%
[14/361] Installing readline-7.0.3...
[14/361] Extracting readline-7.0.3: 100%
[15/361] Reinstalling xcb-util-0.4.0_2,1...
[15/361] Extracting xcb-util-0.4.0_2,1: 100%
pkg: sqlite error while executing COMMIT TRANSACTION in file pkgdb.c:1255: database is locked
[16/361] Upgrading python27 from 2.7.13_3 to 2.7.13_7...
pkg: sqlite error while executing BEGIN IMMEDIATE TRANSACTION in file pkgdb.c:1255: cannot start a transaction within a transaction


Any ideas?

Re: GhostBSD 10.3 new pkgs repository

Posted: Wed Aug 09, 2017 4:43 am
by ASX
NevilleGoddard wrote:I tried to update my GhostBSD 10.3 with the new updates but I got this:
...
[15/361] Reinstalling xcb-util-0.4.0_2,1...
[15/361] Extracting xcb-util-0.4.0_2,1: 100%
pkg: sqlite error while executing COMMIT TRANSACTION in file pkgdb.c:1255: database is locked
[16/361] Upgrading python27 from 2.7.13_3 to 2.7.13_7...
pkg: sqlite error while executing BEGIN IMMEDIATE TRANSACTION in file pkgdb.c:1255: cannot start a transaction within a transaction


Any ideas?
Not much really ... it could be a corrupted pkg database ...

try to get a list o finstalled packages: and save it.

Code: Select all

pkg leaf
That should allow you to remove alll packages, delete the pkg database, and reinstall all packages.