I don't try to curse all of the open-source people just because of my small problems. If it looks so, I apologize.
No problem, no need to apologize. It was meant as a small info or reminder that the use of FreeBSD is based on free,voluntary hard work of others and in case of the package mirror hosting, the generosity of commercial firms (and a university).
And my level isn't yet enough to maintain a port or to make a patch, unfortunately.
Don't say that.
Here is someone at a very beginner level (even in using computers) making an effort in port maintenance.
So, do you think it's better to use quarterly and not bother, or just to be little more patient with the latest? By the way, in the quarterly, there is only firefox-esr package, not the latest one (?).
The quarterly branch is in general more "stable" as the latest, but there is no guarantee it will not or less affected, as you can see in the absents of the firefox package. I have also
www/firefox installed (version 78.0_2,1), latest repository, but I don't experience the library problems you have.
And if I'm on the latest, and if I need immediately the package which is absent, what should I do?
In case of
www/firefox,
multimedia/vlc, and
net-im/telegram-desktop be patient, the package will be available in a few day. If you need a deleted program urgent you can install from
/var/cache/pkg with
pkg add
.
Official latest (and quarterly) repository packages are build after the head (quarterly) ports tree. More or less the same ports tree you might have on your system. If a port doesn't build on the freebsd.org package build servers, chances are high it won't build on your system either.
But the opposite could be the case (even though only in exceptional cases). Ports trees, especially head changes, literally, by the minute, even seconds. The build servers use a snapshot of the tree from a specific time. If a port doesn't build on the servers, but in the mean time a port is updated, it could build on your system.
There are other methods to obtain a working environment, e.g. if you are using ZFS you can rollback, or with
sysutils/beadm boot a copy of an environment with working copies of the programs, or have a parallel installed second installation, etc.
If the filesystem is ZFS
sysutils/beadm is best suited and easy to use to obtain a working environment. Have a look
here, and don't be intimidated by the amount of information. If you don't understand something, just ask. It's not complicated to configure, even easier to use, like e.g.: From a woking system create an image with the current packages before a pkg upgrade:
beadm create pkgsgood
, upgrade packages, see if all is good, when not:
beadm activate pkgsgood
, reboot into it:
shutdown -r now
.
just to worry the community less.
I don't know about others , but I'm not worried.
. Ask as much as you like. As you can see there is no lack of users willing to respond to your postings.
scary to imagine if the same is happened with a production server's packages, not user's laptop...
See my suggestion regarding
sysutils/beadm. Also production servers have a testing server before upgrading to production.
I
see the Firefox package was built at Jul 4... Who has stolen it??
The batch of build packages haven't been uploaded to the repository yet:
http://pkg.freebsd.org/FreeBSD:12:amd64/latest
If somebody is waiting for
www/chromium from the latest pkg repository, it failed to build, there will be no package in the following pkg upgrade.
In case someone want's to take a look at the log, be warned, it has ~150 Mb.