qupzilla-qt5 pkg: bad dependency (was: otter-browser...)
same problem with qupzilla-qt5: full log of install, attempted use: udo pkg install qupzilla-qt5 < Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. pkg: scummvm-tools has a missing dependency: lame pkg: vice has a missing dependency: lame The following 3 package(s) will be affected (of 0 checked): New packages to be INSTALLED: qupzilla-qt5: 1.8.9_2 qt5-xml: 5.7.1 qt5-imageformats: 5.7.1 Number of packages to be installed: 3 The process will require 13 MiB more space. 3 MiB to be downloaded. Proceed with this action? [y/N]: y [1/3] Fetching qupzilla-qt5-1.8.9_2.txz: 100%2 MiB 2.6MB/s00:01 [2/3] Fetching qt5-xml-5.7.1.txz: 100% 89 KiB 90.7kB/s00:01 [3/3] Fetching qt5-imageformats-5.7.1.txz: 100% 64 KiB 66.0kB/s00:01 Checking integrity... done (0 conflicting) [1/3] Installing qt5-xml-5.7.1... [1/3] Extracting qt5-xml-5.7.1: 100% [2/3] Installing qt5-imageformats-5.7.1... [2/3] Extracting qt5-imageformats-5.7.1: 100% [3/3] Installing qupzilla-qt5-1.8.9_2... Extracting qupzilla-qt5-1.8.9_2: 100% qupzilla /usr/local/lib/libQt5Core.so.5: version Qt_5.7 required by /usr/local/bin/qupzilla not found ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
otter-browser pkg: bad dependency
i just installed binary pkg: otter-browser. it won't run because libQt5Core (also installed from binary pkg) lacks the version it was build with. pkg is all up to date. full log of install, attempted use, attempted update: sudo pkg install otter-browser Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. pkg: scummvm-tools has a missing dependency: lame pkg: vice has a missing dependency: lame The following 15 package(s) will be affected (of 0 checked): New packages to be INSTALLED: otter-browser: 0.9.12_2 qt5-webkit: 5.7.1 qt5-quick: 5.7.1 qt5-xmlpatterns: 5.7.1 qt5-qml: 5.7.1 qt5-testlib: 5.7.1 qt5-sql: 5.7.1 qt5-printsupport: 5.7.1 qt5-opengl: 5.7.1 leveldb: 1.20_1 snappy: 1.1.4 qt5-multimedia: 5.7.1 qt5-script: 5.7.1 qt5-concurrent: 5.7.1 qt5-sqldrivers-sqlite3: 5.7.1 Number of packages to be installed: 15 The process will require 73 MiB more space. 15 MiB to be downloaded. Proceed with this action? [y/N]: y [1/15] Fetching otter-browser-0.9.12_2.txz: 100%2 MiB 1.0MB/s00:02 [2/15] Fetching qt5-webkit-5.7.1.txz: 100%7 MiB 1.5MB/s00:05 [3/15] Fetching qt5-quick-5.7.1.txz: 100%2 MiB 1.7MB/s00:01 [4/15] Fetching qt5-xmlpatterns-5.7.1.txz: 100%1 MiB 1.1MB/s00:01 [5/15] Fetching qt5-qml-5.7.1.txz: 100%1 MiB 1.3MB/s00:01 [6/15] Fetching qt5-testlib-5.7.1.txz: 100% 117 KiB 119.8kB/s00:01 [7/15] Fetching qt5-sql-5.7.1.txz: 100% 95 KiB 97.5kB/s00:01 [8/15] Fetching qt5-printsupport-5.7.1.txz: 100% 163 KiB 166.7kB/s00:01 [9/15] Fetching qt5-opengl-5.7.1.txz: 100% 140 KiB 143.7kB/s00:01 [10/15] Fetching leveldb-1.20_1.txz: 100% 196 KiB 201.2kB/s00:01 [11/15] Fetching snappy-1.1.4.txz: 100% 62 KiB 63.2kB/s00:01 [12/15] Fetching qt5-multimedia-5.7.1.txz: 100% 540 KiB 553.4kB/s00:01 [13/15] Fetching qt5-script-5.7.1.txz: 100% 509 KiB 520.7kB/s00:01 [14/15] Fetching qt5-concurrent-5.7.1.txz: 100% 35 KiB 36.3kB/s00:01 [15/15] Fetching qt5-sqldrivers-sqlite3-5.7.1.txz: 100% 26 KiB 26.6kB/s 00:01 Checking integrity... done (0 conflicting) [1/15] Installing qt5-xmlpatterns-5.7.1... [1/15] Extracting qt5-xmlpatterns-5.7.1: 100% [2/15] Installing qt5-qml-5.7.1... [2/15] Extracting qt5-qml-5.7.1: 100% [3/15] Installing qt5-testlib-5.7.1... [3/15] Extracting qt5-testlib-5.7.1: 100% [4/15] Installing qt5-sql-5.7.1... [4/15] Extracting qt5-sql-5.7.1: 100% [5/15] Installing snappy-1.1.4... [5/15] Extracting snappy-1.1.4: 100% [6/15] Installing qt5-quick-5.7.1... [6/15] Extracting qt5-quick-5.7.1: 100% [7/15] Installing qt5-printsupport-5.7.1... [7/15] Extracting qt5-printsupport-5.7.1: 100% [8/15] Installing qt5-opengl-5.7.1... [8/15] Extracting qt5-opengl-5.7.1: 100% [9/15] Installing leveldb-1.20_1... [9/15] Extracting leveldb-1.20_1: 100% [10/15] Installing qt5-webkit-5.7.1... [10/15] Extracting qt5-webkit-5.7.1: 100% [11/15] Installing qt5-multimedia-5.7.1... [11/15] Extracting qt5-multimedia-5.7.1: 100% [12/15] Installing qt5-script-5.7.1... [12/15] Extracting qt5-script-5.7.1: 100% [13/15] Installing qt5-concurrent-5.7.1... [13/15] Extracting qt5-concurrent-5.7.1: 100% [14/15] Installing qt5-sqldrivers-sqlite3-5.7.1... [14/15] Extracting qt5-sqldrivers-sqlite3-5.7.1: 100% [15/15] Installing otter-browser-0.9.12_2... Extracting otter-browser-0.9.12_2: 100% Message from qt5-sql-5.7.1: == To enable Qt database support, install the database plugin ports. The following plugin ports are available: - databases/qt5-sqldrivers-ibase InterBase/Firebird - databases/qt5-sqldrivers-mysql MySQL - databases/qt5-sqldrivers-odbcOpen Database Connectivity - databases/qt5-sqldrivers-pgsql PostgreSQL - databases/qt5-sqldrivers-sqlite2 SQLite 2 - databases/qt5-sqldrivers-sqlite3 SQLite 3 - databases/qt5-sqldrivers-tds FreeTDS == ged install_msgs otter-browser /usr/local/lib/libQt5Core.so.5: version Qt_5.7 required by /usr/local/bin/otter-browser not found sudo pkg update Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Is pkg quarterly really needed?
On Thu, Apr 20, 2017, at 06:22 AM, Mark Linimon wrote: > On Wed, Apr 19, 2017 at 04:37:05PM -0400, scratch65...@att.net wrote: > > (Right now, it's quite hard to resist the paranoid suspicion that > > maybe this crazy, anti-real-user behavior is a subtle way to kill > > freebsd altogether by driving away the non-hobbyists.) > > That's one explanation. > > The other, possible, explanation, is that the efforts of a group of > volunteers isn't adequate enough for every use case -- including your own. This!!! I used to help out a little with a Linux distro, many years ago when it was feasible for a handful of hobyists to do so in their spare time. The experience was sobering. In about 5 years I went from building my own LFS system without any help (I wasn't on the net) to seeing a bunch of people just barely keep up as Xorg and Gtk+ grew circular dependency chains, some users demanded stability while others wanted updates, and of course compile times were rapidly increasing. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Is pkg quarterly really needed?
On Tue, Apr 18, 2017, at 02:54 PM, qjail1 wrote:
> I maintain a port and I have users complaining that the pkg system takes
> many months before the updated version of my port shows up in the pkg
> system.
>
> My response is I tell them to change a line in their
> /etc/pkg/FreeBSD.conf file
> from url: "pkg+http://pkg.Freebsd.org/${ABI}/quarterly;,
> to url: "pkg+http://pkg.Freebsd.org/${ABI}/latest;,
>
> The old pkg system never had this quarterly update cycle and I see no
> reason to have it now when its so easy to over ride the default.
>
> Why not just change the default to "latest" and save on all the overhead
> of the quarterly cycle?
I have to say that if pkg abandoned the cautious update cycle, I'd abandon
FreeBSD. I've really had enough of constant upgrades. The one thing I have
which needs constant upgrades is a Flash video downloader. I keep that in ~/bin
and use its built-in upgrade mechanism when required, which is simple. I don't
need to get it via some root-only mechanism. It doesn't have a man page of
course, but --help|less is easy enough.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports expiring soon due to Google Code site removal
On Fri, Mar 24, 2017, at 04:12 PM, Mark Linimon wrote: > As of 20170324 there are still 175 ports that are marked deprecated and > broken due to the Google Code site having gone away. These are due to > expire on 20170430. Please consider this a "last call" to find a current > mastersite for these ports before then. Thanks. ... > devel/plan9port po...@freebsd.org ... this should be the right place to get it now: https://github.com/9fans/plan9port i considered taking ownership of the port, but decided i'd rather work with upstream to ensure it compiles out of the box on freebsd because it's one of those projects which "has lots of config files, they're the ones which end in '.c'!" :) it's not really so bad as that, but i will be modifying my copy and don't want to maintain another unmodified copy which i don't use. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portmaster installation trampling on my binary packages???
On Sun, Mar 19, 2017, at 07:54 PM, Kevin Oberman wrote: > I think you need to understand the relationship between packages and > ports. First and foremost, they are the same thing. When you build a > port you are actually creating a package by processing the source > files. This usually, but not always means compiling, linking, creating > libraries, often both shareable (.so) and static (.a), installing > documents, etc. This is done in a process called staging. The staged > port is then packed into a package and the package is installed. This > package is the exact same package that is installed by using pkg > install, except that it is created locally from the sources instead of > being downloaded from a repository. That explains almost everything! Thanks. > When you run 'portmaster -a', you are telling the system to go > through every installed port and confirm that it is the same version > as that installed. If it is not, regardless of whether it was > installed by building the port or by downloading and installing the > binary package, portmaster will build and install the new port, > replacing the old port. > If you have installed from the packages included in a FreeBSD > distribution, they are the packages existing at the time of the > release. In many cases, this is a LOT of packages as they are > continually updated as needed. (Some not very often and others as > often as every week or two.) So hte first time you run 'portmaster - > a', you will build and re-install a LOT of things and, since the pre- > built packages are all built using the default build option, you may > get a lot of configuration screens where you can choose non-default > options. These options will be saved and future updates will not ask > again until the options are changed, a far less frequent thing. Again, > the initial run of portmaster is at least "tedious". That makes complete sense after the first paragraph. > My question must start with "Do you have a reason to build from > sources? You do if you need non-default options, but otherwise that is > likely not needed and extremely time consuming. Instead you can jsut > use packages and install the pre-built binaries. Y0ou don't even need > to have ports on you system. Indeed. I had planned to install most everything with pkg, only installing from ports things which weren't available as binary packages. The big thing which pushed me to the ports tree was not plan9port (which I could easily install from source), but this: $ pkg query -e '%c ~ *game* || %e ~ *game*' %n pysolfc $ Am I misunderstanding pkg query -e, too? :) > Here is what I do for most systems: > If any ports require non-default options, and few will, use "pkg lock > PACKAGE-NAME" so pkg will not attempt to update the port from > binaries. Then I run 'pkg upgrade' regularly. This will update any > ports that have been modified since you installed your system. Because > it installed binary packages, it is quite speedy. Then, I run 'make -C > /usr/ports fetchindex' to get the latest index of ports and then 'pkg > version -vL=' to check on whether any locked ports need to be touched. > (As I have no more than 2 such ports 0n any system, this is pretty > infrequent.) If you don't have any ports that need to be built from > scratch, you can skip this and not even worry about the ports. That all looks useful, I'll keep a copy to refer to. > the other issue is whether you want to keep all ports right up to the > latest update. There are two sets of packages built for every release. > One is "latest" and the other is "quarterly". 'quarterly' is only > updated four times a year or for security fixes. 'latest' is > continually updated. Most people probably are fine running with > quarterly. It results in a lot less churn and fewer cases of being > bitten by buggy updates. (Yes, they do happen.) I'm not sure I understand. Are "latest" and "quarterly" ports trees? > I strongly urge that you read the sections of the FreeBSD Handbook[1] > , especially the section on ports and packages, Section 4. It should > clarify a lot and make things simpler. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 Oh, reading section 4 of the handbook got me into this mess. :) Perhaps I'm too tired to read it properly, because I don't see anything to suggest I avoid mixing packages & ports freely. -- I'm too old to use vi. Links: 1. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
portmaster installation trampling on my binary packages???
Hi. I'm quite new to FreeBSD. I'm getting a system up & running slowly, working around my chronic fatigue. Today I'm updating for the first time. Base system and pkg update appeared to go well. I haven't rebooted, wanting to get everything done before reboot. https://www.freebsd.org/doc/handbook/ports-using.html This handook page says "ports-mgmt/portmaster is a very small utility for upgrading installed ports. It is designed to use the tools installed with the FreeBSD base system without depending on other ports or databases." That sounds just fine to me, so I did the usual to install portmaster, cd to its directory, and make install clean. So far, so good. Then I ran portmaster -a, and it all went pear-shaped. I found myself looking at an endless stream of dialogs; compile-time options for things I don't remember installing as ports. Assuming they're dependencies of some port I installed I accept this, but I'm puzzled because I only remember installing one port (devel/plan9port), and I thought it only built itself and maybe one dependency. Then it got disturbing: I get a dialog for *xorg* compile-time options. I installed xorg with pkg, a binary package, not a compiled port. I was briefly uncertain, my memory isn't very good, so I checked this: # date -jr `pkg query %t xorg` Sat Mar 11 21:32:41 GMT 2017 What's going on? Is it going to build xorg and all these dozens of other ports too? If so, what about the binary packages I installed? Will they be overwritten? When I installed that one port, it didn't see the need to compile xorg from ports then, so why is it asking me about xorg compile time options now? Why is it asking me to configure literally dozens of other ports I don't care about? That question goes double if it's NOT going to install any of these ports. Most of all, why is this massive drain on my energy happening when all I did was ask for the installation of something described in FreeBSD's official handbook as "very small"? It's now sitting waiting for me to select bash compile time options, a shell I do not care about AT ALL. If it's installed, it's a binary package as a dependency of some other binary package. Can I safely ^C this? Is portmaster normally this insane? If so, why does the handbook recommend it?! There have been a couple of strange incidents with the ports tree prior to this. I installed from dvd, selecting to install the ports tree at that time. This took long enough that it looked like the biggest part of the installation. When I tried to install that one port, it told me it needed to fetch the port tree. I thought this bizzarre, but ran the suggested command anyway, and after that the port installed just fine. Today I refer to the handbook, and it recommends upgrading the tree using portsnap. Fine, I accept this recommendation... and portsnap then proceeds to whine that it can't work with the default ports tree, it needs *it's* version. (Why is it part of the base system if it can't use the default tree?) After a couple of aeons waiting for portsnap to do its thing and then mk clean just in case I'd installed something else and forgotten about it, I then installed portmaster and tried to use it with the results described above. -- I'm too old to use vi. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
