pkg upgrade (992 candidates)

[fernandel]

Hi!

Long time I didn't have a problem with pkg upgrade but today surprisse. When I ran I got:

 pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating FreeBSD-kmods repository catalogue...
FreeBSD-kmods repository is up to date.
All repositories are up to date.
Checking for upgrades (922 candidates): 100%
Processing candidates (922 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.

I didn't change anything and settings in
/usr/local/etc/pkg/reps/FreeBSD.conf I have

FreeBSD: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}
FreeBSD-kmods: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/kmods_latest_${VERSION_MINOR}",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}

which I have from FreeBSD 14.2 and now I am using FreeBSD -RELEASE-14.3-p5 and long time was okay.
pkg version is 2.4.2_1.

Thank you.[/cmd]

 

[SirDice]

Your packages are up to date.

That's all that's important.

/usr/local/etc/pkg/reps/FreeBSD.conf

Only put the url entry in there. All others will come from the default /etc/pkg/FreeBSD.conf. There's no need to copy those too.

 

[Erichans]

Only put the url entry in there. All others will come from the default /etc/pkg/FreeBSD.conf. There's no need to copy those too.

This is technically accurate and sufficient; however, I find it helpful* to have it in clear and plain view that the repositories are enabled when inspecting a user created config setting, so carefully weigh adding:

  enabled: yes,

to each repository section.

___
* this also eases enabling/disabling a repository by the use of sed(1) scripting.

 

[fernandel]

Thank you .
It was again update and I had less candidates now - less for pkg's updated. I had a problem with Inkscape and I did remove it and also remove related pkg's, install again and for now looks like Inkscape doesn't has a problem.
Now I have 866 candidate.
Are pkg's are built for 14.3 now. Is it possible that candidates shows because are majority built for 14.2, please?

 

[fmc000]

FWIW, I run 14.3-STABLE and I have:

All repositories are up to date.
Checking for upgrades (870 candidates): 100%
Processing candidates (870 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.

 

[balanga]

Erm.... maybe check the title of your thread....

 

[balanga]

When running pkg upgrade is there an option to create a logfile or should I do it manually.

It would be nice to have a copy of all the adviseries.

Maybe I should just pipe the output through tee().

 

[SirDice]

When running pkg upgrade is there an option to create a logfile or should I do it manually.

Any pkg(8) actions (delete, install, etc) are logged in /var/log/messages.