Pkg: warning: database version 32 is newer than libpkg(3) version 31, but still compatible
-
login as: admin
Using keyboard-interactive authentication.
Password for admin@dmfirewall.datamais.local:
*** Welcome to pfSense 2.3-RELEASE-pfSense (i386) on dmfirewall ***ADSL (wan) -> rl0 -> v4: 192.168.2.3/24
LAN (lan) -> re0 -> v4: 192.168.0.254/24
TPA (opt1) -> rl1 -> v4: 177.200.195.6/24- Logout (SSH only) 9) pfTop
- Assign Interfaces 10) Filter Logs
- Set interface(s) IP address 11) Restart webConfigurator
- Reset webConfigurator password 12) pfSense Developer Shell
- Reset to factory defaults 13) Update from console
- Reboot system 14) Disable Secure Shell (sshd)
- Halt system 15) Restore recent configuration
- Ping host 16) Restart PHP-FPM
- Shell
Enter an option: 13
pkg: warning: database version 32 is newer than libpkg(3) version 31, but still compatible
pkg: warning: database version 32 is newer than libpkg(3) version 31, but still compatible
pkg: warning: database version 32 is newer than libpkg(3) version 31, but still compatibleUpdating repositories metadata…
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
Updating samba36 repository catalogue...
samba36 repository is up-to-date.
All repositories are up-to-date.
pkg: warning: database version 32 is newer than libpkg(3) version 31, but still compatible
pkg: warning: database version 32 is newer than libpkg(3) version 31, but still compatible
pkg: warning: database version 32 is newer than libpkg(3) version 31, but still compatible
Upgrading pkg...Some hint?
-
I split this off the other thread because it's not related to the other issue.
You appear to have manually edited/changed your repositories. You're on your own with that.
Updating samba36 repository catalogue…
samba36 repository is up-to-date. -
Thanks for your reply.
I did not, deliberately, edited/changed anything.
You refer to this repo?
FreeBSD: { enabled: no }
pfSense-core: {
url: "pkg+http://pkg.pfsense.org/pfSense_v2_3_0_i386-core",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/local/share/pfSense/keys/pkg"
enabled: yes
}pfSense: {
url: "pkg+http://pkg.pfsense.org/pfSense_v2_3_0_i386-pfSense_v2_3_0",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/local/share/pfSense/keys/pkg"
enabled: yes
} -
First thing to do if you spot anything funny with pkg is to run:
pkg update -f
This will forcefully re-download the repository catalogues and in many cases will sort out the funny dependencies as well.
-
Some error messages and this message is looping forever (or until I stop it):
Updating samba36 repository catalogue…
samba36 repository is up-to-date.Upgrading pkg...
The messages as I see when upgranding:
Processing entries....
pkg: Skipping unknown key 'messages'
pkg: Skipping unknown key 'messages'
pkg: Skipping unknown key 'messages'
pkg: Skipping unknown key 'messages'
Processing entries...
pkg: Skipping unknown key 'messages'
pkg: Skipping unknown key 'messages'
pkg: Skipping unknown key 'messages'
pkg: Skipping unknown key 'messages'
Processing entries.... done
pfSense repository update completed. 404 packages processed.
Updating samba36 repository catalogue...
samba36 repository is up-to-date.Upgrading pkg...
-
Whatever was manually done to add the samba36 package repository is likely to blame. That did not come from our servers and must have been manually added, and is unsupported.
-
In a previous version of pfsense, I installed the Sarg Report and I think that 'samba' was installed together.
I removed Sarg. Could you give some hint about how to remove samba and its tries for actualization?
-
I did it removing samba36.conf from /usr/local/etc/pkg/repos