Re: audio/alsa-plugins compiles OK, install fails
Gleb Popov responds: > > On Wed, May 12, 2021 at 3:01 PM Robert Huff wrote: > > > > > Stop. > > > make[1]: stopped in /usr/ports/audio/alsa-plugins > > *** Error code 1 > > Hello. This is being worked on in https://reviews.freebsd.org/D30223 Awesome. I thank those involved. Respectfully, Robert "Thank god it wasn't me." Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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"
audio/alsa-plugins compiles OK, install fails
Hello:
On a system running:
14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-d6327ae8c1: Sun Jan 24 14:16:54 EST
2021 amd64
with any required ports updated. audio/alsa-plugins builds
sucessfully.
Installation, however, fails with:
===> Installing for alsa-plugins-1.2.2
===> Checking if alsa-plugins is already installed
===> Registering installation for alsa-plugins-1.2.2
pkg-static: Unable to access file
/data/port-work/usr/ports/audio/alsa-plugins/work/stage/usr/local/lib/alsa-lib/libasound_module_rate_lavcrate.la:No
such file or directory
pkg-static: Unable to access file
/data/port-work/usr/ports/audio/alsa-plugins/work/stage/usr/local/lib/alsa-lib/libasound_module_rate_lavcrate.so:No
such file or directory
pkg-static: Unable to access file
/data/port-work/usr/ports/audio/alsa-plugins/work/stage/usr/local/lib/alsa-lib/libasound_module_rate_lavcrate_fast.so:No
such file or directory
pkg-static: Unable to access file
/data/port-work/usr/ports/audio/alsa-plugins/work/stage/usr/local/lib/alsa-lib/libasound_module_rate_lavcrate_faster.so:No
such file or directory
pkg-static: Unable to access file
/data/port-work/usr/ports/audio/alsa-plugins/work/stage/usr/local/lib/alsa-lib/libasound_module_rate_lavcrate_high.so:No
such file or directory
pkg-static: Unable to access file
/data/port-work/usr/ports/audio/alsa-plugins/work/stage/usr/local/lib/alsa-lib/libasound_module_rate_lavcrate_higher.so:No
such file or directory
*** Error code 1
Stop.
make[1]: stopped in /usr/ports/audio/alsa-plugins
*** Error code 1
I have no clue what's happening. Help, please?
Respectfully,
Robert Huff
--
Hello ... my name is SARS-CoV-2.
You are not wearing a mask?
Prepare to die!
___
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"
looking for port origin for executable
Hello:
Would some kind soul please tell me which port installs the
executable "g-ir-scanner"? I was purging unused ports and seem to
have done this one by mistake.
Apologetically,
Robert Huff
___
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"
Proposed ports git transition schedule
The transition has happened. Where do I find the authoritative guide for non-committers? Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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: broken vuln.xml?
Baptiste Daroussin writes:
> Does pkg audit -F fixes your problem ?
Seems to.
Off for more testing ...
Thanks.
Respectfully,
Robert Huff
--
Hello ... my name is SARS-CoV-2.
You are not wearing a mask?
Prepare to die!
___
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: broken vuln.xml?
Baptiste Daroussin writes: > On Tue, Feb 02, 2021 at 01:01:14PM +, Bob Eager wrote: > > > > This appears to have broken (Sunday?) on one of my systems. > > > What is the correct way to download/regenerate this file? > >=20 > > portaudit is being replaced by pkg audit. > >=20 > > This may already have happened - I am not sure. > > portaudit has been replaced by pkg audit 7 years ago! (removed > from the ports tree in 2014. So here's my problem: Starting yesterday all attempts to rebuild ports - any port - end like this: portmaster: java-zoneinfo-2020.d ===>>> Currently installed version: java-zoneinfo-2020.d ===>>> Port directory: /usr/ports/java/java-zoneinfo ===>>> Gathering distinfo list for installed ports ===>>> Launching 'make checksum' for java/java-zoneinfo in background ===>>> Gathering dependency list for java/java-zoneinfo from ports ===>>> Initial dependency check complete for java/java-zoneinfo portmaster: java-zoneinfo-2020.d ===>>> Starting build for java/java-zoneinfo <<<=== ===>>> All dependencies are up to date ===> Cleaning for java-zoneinfo-2021.a pkg-static: Invalid end of XML pkg-static: cannot process vulnxml ===> java-zoneinfo-2021.a has known vulnerabilities: => Please update your ports tree and try again. => Note: Vulnerable ports are marked as such even if there is no update available. => If you wish to ignore this vulnerability rebuild with 'make DISABLE_VULNERABILITIES=yes' *** Error code 1 Stop. make: stopped in /usr/ports/java/java-zoneinfo Am I even asking about the right file? What broke, why (if possible), and how do I fix it? Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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: broken vuln.xml?
Hell:
> Robert Huff wrote:
>
> > Hello:
> > This appears to have broken (Sunday?) on one of my systems.
> > What is the correct way to download/regenerate this file?
>
> portaudit is being replaced by pkg audit.
>
> This may already have happened - I am not sure.
Uh ... ok. With no warning? No entry in
UPDATING?
Respectfully,
Robert Huff
--
Hello ... my name is SARS-CoV-2.
You are not wearing a mask?
Prepare to die!
___
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"
broken vuln.xml?
Hello: This appears to have broken (Sunday?) on one of my systems. What is the correct way to download/regenerate this file? Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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"
problem with pear-File_Archive
Hello: Generating INDEX-13 - please wait..--- describe.accessibility --- --- describe.arabic --- [deletia] --- describe.x11-toolkits --- --- describe.x11-wm --- make_index: /usr/ports/archivers/pear-File_Archive: no entry for /usr/ports/lang/php72 lang/php72 no longer exists. What's up? Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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: Skype?
Pau Amma writes:
> ports/MOVED
>
> net-im/skype4||2019-04-30|Has expired: Unsupported upstream
Dang - I looked in MOVED, but somehow managed to miss this.
Profuse apologies for the user error.
Respectfully,
Robert Huff
--
Hello ... my name is SARS-CoV-2.
You are not wearing a mask?
Prepare to die!
___
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"
Skype?
Hello: There used to be net-im/skype (and fellow travellers). Don't find it now; can't figure out what happened to it. What am I missing? Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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: replacing ffserver?
Let me restate the issue.
My goal is to be able to have someone visit (e.g.)
"https://webcam.example.com:; and have the feed from the webcam
appear in their browser.
What I have at the moment:
a) a system running:
FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020 amd64
b) a working webcam
c) the latest version of webcamd, which finds the webcam and
creates video0 and video1.
So: I need to make the contents of video0 available on port .
I have been unable to find a concise current method for how to do
that. (Including anything with Apache, which seems like an obvious
step.)
Respectfully,
Robert Huff
--
Hello ... my name is SARS-CoV-2.
You are not wearing a mask?
Prepare to die!
___
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: replacing ffserver?
Jonathan Chen writes:
> Possibly multimedia/motion?
On examination ... interesting program, but not what I'm looking
for. (Today. :-)
Respectfully,
Robert Huff
--
Hello ... my name is SARS-CoV-2.
You are not wearing a mask?
Prepare to die!
___
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"
replacing ffserver?
Hello: I now have a working webcam and want to make its output available (via https?) on my local net. It is my understanding a common way to do this used to be ffserver, a utility provided by ffmpeg. However: no such object appears in the plist, nor has it become a separate port. Is there well-liked replacement? Or perhaps even a how-to? Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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: problem building INDEX
Christoph Moench-Tegeder writes:
> That would suggest that you have set your Samba version via
> DEFAULT_VERSIONS in make.conf or similar, which forces the
> dependency on the non- existing Samba port.
That was it.
("Minion - bring me a wall, that I may beat my head against it in
humiliation!")
Sheepishly,
Robert Huff
--
Hello ... my name is SARS-Cov-19.
You are not wearing a mask?
Prepare to die!
___
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"
problem building INDEX
Hello:
Since about the beginning of the week, doing this:
huff@ > cd /usr/ports && make index
ends like this:
--- describe.x11-fonts ---
--- describe.x11-servers ---
--- describe.x11-themes ---
--- describe.x11-toolkits ---
--- describe.x11-wm ---
make_index: /usr/ports/devel/gvfs: no entry for /usr/ports/net/samba410
Done.
I'm reasonably sure this is not my fault; don't actually care
what happened as long as it can be fixed.
Respectfully,
Robert Huff
--
Hello ... my name is SARS-Cov-19.
You are not wearing a mask?
Prepare to die!
___
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"
streaming from FreeBSD to Roku?
Is anyone out there successfully using FreeBSD as a media server for a Roku device? If so, please contact me off-list. Respectfully, Robert Huff ___ 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"
looking for Dima Panov
Would he please contact me off-list? Respectfully, Robert Huff ___ 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: [HEADS UP] Planned deprecation of portsnap
Michael Gmelin writes:
> There are many users who never create any patches, but simply use
> the ports tree to install software.
Add my name to that list.
(Used to use cvsup ... now subversion ... soon git ... where will
the insanity end? :-) )
Respectfully,
Robert Huff
--
Get it right: _physical_ distancing; _social_ cohesion
___
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: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available
George Mitchell writes: > >> But basically, expect all python 2.x using ports to go away, unless > >> they get fixed to use python 3.x, or no python at all. > > > >Is there a method whereby - given a list of installed ports using > > python 2 - one might determine which can and which cannot be upgraded > > to pythin 3? > > [...] > > There's a heuristic method: run the python program "2to3" on the > file you want to asses. It will try to replace 2.x usages with > their 3.x equivalents. Success is not guaranteed. (2to3 is part > of python27.)-- George Let me be more precise. I have a list of 110 installed ports flavored "py27-". For each port I want to know: a) according to the Makefile, is it possible to build this with python-37? (Or even -36?) b) will doing so break any port for which this port is a dependency? I understand the only way to answer (b) may be by trial-and-error; fair enough. But if I can identify all those with no dependants ... that would be a start. Respectfully, Robert Huff ___ 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: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available
Dimitry Andric writes: > But basically, expect all python 2.x using ports to go away, unless > they get fixed to use python 3.x, or no python at all. Is there a method whereby - given a list of installed ports using python 2 - one might determine which can and which cannot be upgraded to pythin 3? Respectfully, Robert "110 candidates" Huff ___ 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: qt5-webengine
Jonathan Chen writes:
>Frankly speaking, if you're compiling your own ports, you
> have to use either synth or poudriere; anything else will cost you
> time hunting down broken dependencies.
Speaking as someone who's been compiling from ports for at least
a decade, and maintains 1200+ ports on at least one box:
Yes ... but not much. I use portmaster and stuff mostly Just
Works(tm). [Thanks, guys!] Ports get updated regularly, and the last
major problem I can remember had to do with defauly version bumps in
perl and python (2->3).
I understand there are folks for whom poudriere or synth are The
Right Tool(tm). But I am one of a number of folks for whom it is like
carpet-bombing the neighborhood to get rid of one miscreant squirrel.
Respectfully,
Robert Huff
___
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: lsof marked ignored
Larry Rosenman writes:
> I'd love to see the kernel folks make better interfaces.
>
> I've been saying that for 2 years.
Can you be one step more specific on what interface it needs?
Respectfully,
Robert Huff
___
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: lsof marked ignored
Adam Weinberger writes: > > ===>>> Currently installed version: lsof-4.93.2_9,8 > > ===>>> Port directory: /usr/ports/sysutils/lsof > > > > ===>>> This port is marked IGNORE > > ===>>> requires kernel sources > > That error should only occur if system sources are missing from > /usr/src. Check that they're still there, and if not then check them > out from svn. (Last time I checked ) Not only does it require kernel sources, but those sources need to match the running kernel. My solution has been to add "sysutils/lsof" to PORTS_MODULES in /etc/make.conf. Respectfully, Robert Huff ___ 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"
good gui bit-torrent client?
I used to use azureus/vuze, but it hasn't been maintained is quite a while. So I changed to deluge ... which now has a dependency semi-permanently BROKEN. What can people recommend as a replacement? Hopefully, Robert Huff ___ 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: xterm-353
Thomas Mueller writes:
> > Seamonkey - which was my default browser until it was no longer
> > updated - came with this ability built in. The only problem was the
> > list of alternate identities was vintage, like, 2000 with no way (that
> > I knew of) to change it.
>
> I went to seamonkey-project.org website a few months ago, saw it
> was still being developed, not dead, not lame-duck.
Fair enough.
However: there is no port.
Hasn't been for months.
Since I have neither the skill or the time to create and maintain
one ... far as I'm concerned seamonkey is dead.
Do you know something I don't know?
Respectfully,
Robert Huff
___
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: xterm-353
Kevin Oberman writes: > > Where would I find User Agent Switcher by Linder? Would it be on a > > Mozilla site, and would it work with SeaMonkey? > > > > Would the several Firefox or SeaMonkey extensions have similar > > functionality? > > It's available through Firefox from about:addons. It is the one by Linder, > one of at eat three extensions of the same name. I don't know about > SeaMonkey. Does it support the extension interface like Firefox? If so, it > will probably work. You might also check the website at > http://mybrowseraddon.com/useragent-switcher.html Seamonkey - which was my default browser until it was no longer updated - came with this ability built in. The only problem was the list of alternate identities was vintage, like, 2000 with no way (that I knew of) to change it. Respectfully, Robert Huff ___ 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: breakage in "make index"
Mathieu Arnold writes:
> >with the ports tree updated every night, for about the last week
> > "make index" has failed because:
> >
>
> I fear nobody can make the adjustment but you, the default linux
> switched to c7 a last summer, and the linux-c6-* ports were a eek ago.
> You probably have DEFAULT_VERSIONS=linux=c6 somewhere.
In make.conf - now fixed.
Apologetically,
Robert Huff
___
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"
breakage in "make index"
[I'm posting this here because "ports@" is the listed
maintainer.]
On a system running:
FreeBSD 13.0-CURRENT #0 r354131: Mon Oct 28 17:27:33 EDT 2019 amd64
with the ports tree updated every night, for about the last week
"make index" has failed because:
--- describe.x11-wm ---
make_index: /usr/ports/astro/google-earth: no entry for
/usr/ports/graphics/linux-c6-dri
Done.
and therefore "pkg version" also fails.
This is beyond my skill set; would someone who knows how please
make the appropriate adjustment?
Respectfully,
Robert Huff
___
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: [HEADSUP] Re: Is IPV6 option still necessary?
Andrea Venturoli writes:
> I'm building without IPv6, just because it's one (currently
> useless) less thing to worry about (settings, security, etc...).
Phrased differently: one less possible failure mode.
Respectfully,
Robert Huff
___
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: Can't update qt5-gui on 11.2-RELEASE-p13
Adriaan de Groot writes:
> Basically, Qt is using internal headers that it shouldn't .. but
> that means we need to make Qt depend on evdev-proto. There is a fix
> in the works.
_Please_ announce this in UPDATING.
Respectfully,
Robert Huff
___
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: Status of samba ports
Andrea Venturoli writes:
> Sorry for being pedantic, but I believe a lot of us would benefit from
> some guidance:
> _ should we upgrade promptly to 4.10? Will it work or will it be a waste
> of time?
> _ should we stay on 4.8, because it will be the default on FreeBSD for a
> long time still? And will it be fixed?
> _ should we just wait for a (working) 4.11 to come our way? When will
> this happen?
I'd prefer to wait for 4.11, assuming it appears in a reasonable
time-frame.
What would encourage that would be a "migrating for dummies"
document from 4.8, as I understand this is not a trivial process.
Respectfully,
Robert Huff
___
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"
libreoffice 6.3 fails to compile on -current
Data point: After upgrading gperf to gperf31, LibreOffice 6.3 builds and installs on: FreeBSD 13.0-CURRENT r344507 amd64 Respectfully, Robert Huff ___ 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"
firefox
bruce writes:
> I used seamonkey for years without problems. Now with seamonkey no
> longer available I have tried firefox. It crashes regularly and
> isn't nearly as good as seamonkey. When are you bringing seamonkey
> back?
Short answer: probably never.
Longer answer:
1) it is (I believe) no longer developed/maintained upstream.
2) the port does not have a local maintainer.
3) it has a long list of security issues, which persisted for
months if not years.
I, too, will miss it. But in the larger scheme of things this
probably the path of wisdom.
(Now ... if you are volunteering to revive it, assume
maintainership, and contribute patches - thankyouthankyouthankyou)
Respectfully,
Robert Huff
___
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: Massive PORTS_REVISION bump after making gcc-9.1 default
Stefan Esser writes:
> Am 28.07.19 um 01:26 schrieb Kevin Oberman:
> > Today I was hit with 226 ports needing update. With one
> > exception, all were the result of the bump or the default gcc
> > version to 9.1. The problem is that 9.1 was not installed first,
> > so over 43 of these ports were rebuilt with the exact same
> > compiler it was built with before the rebuild, eating up 2:45 of
> > time on my build system. I'm sure if was less for many as my
> > build system is over 8 years old. It was non-trivial in any case.
>
> Which port management tool did you use to rebuild the updated ports?
>
> I just checked what portmaster does, and it appears to build gcc-9.1
> before starting to update ports that depend on it.
This matches my experience - ports tree updated starting 00:00:01
Saturday, build started eight hours later.
Respectfully,
Robert Huff
___
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: "make index" fails
Jan Beich writes: > Robert Huff writes: > > >> --- describe.x11-wm --- > >> make_index: /usr/ports/x11/nvidia-driver: no entry for > /usr/ports/graphics/linux-c6-libglvnd > > Could be related to recent DEFAULT_VERSIONS+=linux=c6_64 > removal. See UPDATING. That fixed it. Thanks. Respectfully, Robert "looking for a convenient brick wall" Huff ___ 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"
"make index" fails
For the last 2-3 days, "cd /usr/ports && make index" has failed
with:
> --- describe.x11-themes ---
> --- describe.x11-toolkits ---
> --- describe.x11-wm ---
> make_index: /usr/ports/x11/nvidia-driver: no entry for
> /usr/ports/graphics/linux-c6-libglvnd
> Done.
Is this a fault on my end, or is there a hiccup in the ports
tree?
And if the former, how do I fix it?
Respectfully,
Robert Huff
___
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"
need help with python
AN writes:
> I do not use python directly, only as dependencies. It seems python36 is
> default now. What is the correct procedure to set ports to use python36
> so I can safely delete python27?
Depending on the ports you need, it may not be possible to
completely move from 2.7 to 3.6. I tried to do this within the last
few months and was blocked by (among other things) one port which
_absolutely insisted_ on python 2.7. (Don't remember which one off
the top of my head.)
(It would be really useful if someone (not me!) wrote a script
that identified any ports which run on non-default versions which can
be safely upgraded.)
Respectfully,
Robert Huff
___
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: Debug version of firefox
Anders Jensen-Waud writes:
> On 5/5/19 8:56 am, George Mitchell wrote:
> > I tried compiling a debugging version of firefox:
> >
> > cd /usr/ports/www/firefox; make clean; make WITH_DEBUG=yes install
> >
> > The resulting binary had no debug symbols. What did I do wrong?
> > -- George
> >
> WITH_DEBUG may not modify Firefox's actual makefile to do what you want.
> I would see if you need to monkey patch './configure' with a flag or two.
Has anyone asked the maintainer, which I believe is
"ge...@freebsd.org"?
Respectfully,
Robert Huff
___
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"
Problem with portupgrade and py27-tkinter
Montgomery-Smith, Stephen writes:
> I have both py27-tkinter and py36-tkinter installed. When I do
> portupgrade, it tries to upgrade py27-tkinter to py36-tkinter:
Am I correct in remembering portupgrade dosen't handle flavors?
Respectfully,
Robert Huff
(portmaster user)
___
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: lang/go14 doesn't build without COMPAT11 in FREEBSD 12
=?utf-8?Q?Lucas_Nali_de_Magalh=C3=A3es?= writes:
> The issue is better explained in the other thread, sorry. CPUTYPE
> native means the system detects its own processor and I was informed
> that this detection isn't working well
If true, this sounds like an excellent project for Summer of Code.
Perhaps someone who knows how could add it to the porjects list?
Suggestively,
Robert Huff
___
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"
Firefox problem printing big fonts
Andrea Venturoli writes:
> Sorry if my question is vague, but I'm lost at where to start looking.
May I suggest "gecko@", which I believe to be the list for
Mozilla-based ports?
Referentially,
Robert Huff
___
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: [HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT
Charlie Li writes:
> The LLVM ports are still needed for those consumers that need their
> components, such as llvm-config and the like. Please refer to the aptly
> named wiki page again:
> https://wiki.freebsd.org/WhyDoIHaveToBuildLLVMWhenIAlreadyHaveClangInstalled
This was the thing I thinking about.
> Think of it this way: the base system toolchain is *based on* some
> released version of LLVM (or GCC) as of a particular revision of
> base/. "Based on" means that components that are not critical to
> the actual functioning of the toolchain or otherwise useful to
> FreeBSD itself are bound to be stripped away when included and
> integrated in the base system.
That may be the path of wisdom; and I understand keeping things
working is a non-trivial job, for which I thank those who do it.
Please understand my ... frustration ... in having to deal with
the conseqences, particularly with regard to the ongoing drm changes.
To return to my original point, this is why I suggested an entry in
ports/UPDATING - to let others in my position know of possible
impact.
Respectfully,
Robert Huff
___
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: [HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT
Jan Beich writes:
> Robert Huff writes:
>
> > If this manages to truly replace previous versions a lot of people
> > will want to know.
>
> What does "truly replace" mean?
I was recently told the reason we need devel/llvm70 is the llvm
in base has - for reasons above my pay grade, but probably not above
yours - certain components disabled which are required by various
ports.
If 8.0 (in base) has those components enabled, then the odds are
good I can remove devel/llvm[67]0 - recovering almost 700 mb of disk
space and simplifying debugging efforts.
Major win for me; probably for others.
Respectfully,
Robert Huff
___
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"
[HEADS UP] Clang 8.0.0 upgrade on 13.0-CURRENT
Jan Beich writes:
> Recently /projects/clang800-import branch was merged[1] into /head.
> 13.0-CURRENT now comes with Clang/libc++/LLD 8.0.0 (RC3 atm) in
> base. Many ports have been fixed in advance but many also
> remain[2] broken. If you receive mail from pkg-fallout@ one of
> your port no longer builds on head-*-default jails or the package
> you're using is no longer available this maybe the cause.
_Please_ make sure to announce this in src/UPDATING and
ports/UPDATING. If this manages to truly replace previous versions a
lot of people will want to know.
Respectfully,
Robert Huff
___
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: replacement for xmms?
Jack L. writes:
> I'd love to keep xmms but it seems gtk1 was removed from ports in
> the latest FreeBSD ports release so running xmms became
> problematic. I guess after 20 years of using xmms, it was time to
> move onto something of this decade
Twenty four hours into using Audacious ... it looks like a good
replacement. Mind you, my requirements are pretty minimal.
Respectfully,
Robert Huff
___
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: replacement for xmms?
Samy Mahmoudi writes:
> Why do you need a replacement for xmms ?
Because it's no longer in the ports tree?
Respectfully,
Robert Huff
___
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"
replacement for xmms?
I'm looking for something not too complicated, that runs in a GUI. Suggestions? Respectfully, Robert Huff ___ 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"
llvm60 required by ???
Is there anything other than mesa-dri that requires this port? Respectfully, Robert Huff ___ 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"
how to do pkg_info -W without pkg_info?
@lbutlr writes:
> I would like to find out what port installed a specific file, and
> in searching I found the suggestion, from 2010, to use
>
> pkg_info -W
>
> But on FreeBSD 11.1-p4-RELEASE with postmaster, there is no
> pkg_info and `pkg info` doesn't have a -W flag nor, apparently, a
> way to check for where a file came from.
Try: "pkg which".
Respectfully,
Robert Huff
___
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: how to enforce one version of python
tech-lists writes:
> > _This_ is really annoying. I try to keep my systems with exactly
> > what they need installed, to reduce both bloat and possibly security
> > issues.
>
> YES. This for me is *exactly* why it is so infuriating. And
> doubleplus regarding security. Followed closely by something
> installing the py-27 version when I wanted the 36-version.
>
> I'd like to have the latest stable python for everything that
> requires it. Like I have with perl. I think that means py-36. I
> don't want py-27. I'd like to enforce that, but seemingly I can't,
> because the invocation in make.conf for default version does not
> enforce it in all situations.
>
> If something wants another version of python, I want it to fail,
> ideally spitting out a usable reason why. Is my position
> unreasonable? I hope it isn't. Maybe it is? I dunno.
Let's see if the folks on python@ have better information.
Respectfully,
Robert Huff
___
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: how to enforce one version of python
Daniel Nebdal writes:
>
> The fun
> part is the combination of 2-only holdouts and new 3-only code,
> which is why it's easy to end up with both installed.
_This_ is really annoying. I try to keep my systems with exactly
what they need installed, to reduce both bloat and possibly security
issues. There's one Perl installation; having two Python versions -
and trying to keep track between them - makes me use a lot of bad
language.
Peevishly,
Robert Huff
___
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: how to enforce one version of python
tech-lists writes:
> > The only question I have there - why we still don't switched to
> > python3 by default?)
>
> yeah!!! :D
How many ports _require_ python 3?
How many ports _require_ python 2?
Curiously,
Robert Huff
___
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: Breakage of editors/tamago (Re: build errors after upgrading editors/emacs to version 26.1)
Yasuhiro KIMURA wrote: Hello all, From: Joseph Mingrone Subject: build errors after upgrading editors/emacs to version 26.1 Date: Tue, 29 May 2018 22:17:00 -0300 Poudriere tests of all 'USES=emacs' ports with the latest editors/emacs (version 26.1) resulted in the following errors in either 10i386 or 11amd64 jails: editors/tamago (hrs@) I'm investigating breakage of this port and submitted report of current status as following bug report. Bug 228812 - editors/tamago: This port is broken only with restrected conditions https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228812 Summary of report is * This port is not broken with real environment (i.e. not poudriere). it applies to all flavors. * With poudriere full, canna and nox are broken. devel_full and devel_nox are not. * Accoding to the error message of poudriere build log, source of build failure may be bug of Emacs 26.1. I'll continue to investigating this problem. But to be honest I'm far from emacs lisp expert, and I know almost nothing about inside of Emacs either. So please give me hint, idea, suggestion, etc if something hits upon you about this problem. Additional data points: 1) Under Emacs, vm (mail reader viewmail) compiled for Emacs 25.3 does not work for 26.1. 2) Attempts to compile vm-8.2.0b under Emacs 26.1 fail due to changes in how Emacs processes Lisp. This is a registered bug, at "https://bugs.launchpad.net/vm/+bug/1763377;. There is a patch, which at least in my case fixes one problem but reveals another. (Build log available on request.) Respectfully, Robert Huff ___ 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: Perl help needed
Christoph Moench-Tegeder writes: > ## Robert Huff (roberth...@rcn.com): > > >On a system with over 850 ports, 32 starting with "p5-", the > > list of dependent ports portmaster created from > > "pkg shlib -qR libperl.so.5.24" was over 200, including things like > > FireFox and llvm50 (llvm is required for mesa-dri). > > That sound like "too much". I've 1408 ports installed, of which 90 > are named p5-*, and "pkg shlib -qR libperl.so.5.26" shows only 32 ports. > > Did you rebuild everything along the build-dependencies, or does your > build tool use the run-depdendencies? > There had been a time when ports had way too many dependencies registered, > if my memory serves right that was because many build-dependencies were > recorded as run-dependencies (or there was no distinction at all). Is > that a leftover effect from those times? "Insufficient data, Captain." I followed the instructions for portmaster from UPDATING/20171103, only changing the version numbers. Running "pkg shlib -qR libperl.so.5.26" now produces 13 items; this makes your explanation plausible, if not authoritative. Again, thanks. Robert Huff ___ 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: Perl help needed
Christoph Moench-Tegeder writes: > > Socket.c: loadable library and perl binaries are mismatched > > (got handshake key 0xd200080, needed 0xdf00080) > > The perl default version changed - are you sure your perl and modules > still match? See UPDATING 20180330. > The error message is just what I'd expect for a mismatch. Following this path seems to have fixed things. Warning to anyone who does this: On a system with over 850 ports, 32 starting with "p5-", the list of dependent ports portmaster created from "pkg shlib -qR libperl.so.5.24" was over 200, including things like FireFox and llvm50 (llvm is required for mesa-dri). Total rebuild time was many hours on a lightly loaded 4 core*3 ghz machine. My profuse thinks to all who offered advice. Respectfully, Robert Huff ___ 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"
Perl help needed
On a system running:
FreeBSD 12.0-CURRENT #0 r331659: Thu Mar 29 12:31:36 EDT 2018 amd64
with perl5-5.24.3 rebuilt yesterday, attemptping to build/run a
small number of modules gives something like this:
===> Cleaning for p5-Net-DNS-1.15,1
===> License MIT accepted by the user
===> p5-Net-DNS-1.15,1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by p5-Net-DNS-1.15,1 for building
===> Extracting for p5-Net-DNS-1.15,1
=> SHA256 Checksum OK for Net-DNS-1.15.tar.gz.
===> Patching for p5-Net-DNS-1.15,1
===> p5-Net-DNS-1.15,1 depends on package: p5-Net-LibIDN2>=1 - found
===> p5-Net-DNS-1.15,1 depends on package: p5-Digest-HMAC>=1.03 - found
===> p5-Net-DNS-1.15,1 depends on package: p5-IO-Socket-IP>=0.38 - found
===> p5-Net-DNS-1.15,1 depends on package: perl5>=5.24<5.25 - found
===> Configuring for p5-Net-DNS-1.15,1
Socket.c: loadable library and perl binaries are mismatched (got handshake key
0xd200080, needed 0xdf00080)
I'm not a perl expert, plus perl on FreeBSD mostly just works,
so I have no idea how to diagnose much less fix this. I googled the
error message, and found various solutions that worked for them, but
not for me.
Anyone willing to help me with this off-list?
Respectfully,
Robert Huff
___
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"
FreeBSD Port: firefox-58.0.2,1 core dump on restart WM
Alex V. Petrov writes:
> Why if you do not explicitly exit FF, then when you reload the
> window manager (for me it awesome wm) or reboot machine, FF does
> a core dump?
This does not happen for me when using:
fvwm-2.6.7_3
firefox-58.0.2,1
(Just tested.)
Perhaps one or both need rebuilding?
Respectfully,
Robert Huff
___
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: problem installing ports
On 8/26/2016 7:42 AM, Robert Huff wrote: Let me guess, you have (NFSv4) ACLs enabled somewhere. The HEAD was supposedly fixed in r304075, but the change still was not merged to stable/11. Yes, on the filesystem that holds WRKDIRPREFIX. Is it as simple as that? (And is there a PR number?) Apparently, it is. Thanks for the helo. Madly compiling away, Robert Huff ___ 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: problem installing ports
On 8/26/2016 7:33 AM, Konstantin Belousov wrote:
===> Registering installation for dialog4ports-0.1.6
Installing dialog4ports-0.1.6...
Child process pid=6648 terminated abnormally: Bus error
*** Error code 138
Stop.
... and pkg-static drops a core file.
I get this (with different pids) for _every_ port on "make install".
Never seen this before. Google offered no possible causes.
"Bus error" means a memory violation - and I have no idea how to
proceed. The core file has no debugging symbols, making a backtrace
useless.
Let me guess, you have (NFSv4) ACLs enabled somewhere. The HEAD was
supposedly fixed in r304075, but the change still was not merged to
stable/11.
Yes, on the filesystem that holds WRKDIRPREFIX.
Is it as simple as that? (And is there a PR number?)
Boggled at the simplicity,
Robert Huff
___
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"
problem installing ports
So ... I replaced my 10.3/i386 system with: FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 and kernel+world are working. Installing ports is a different matter. 1) I created /usr/ports and /usr/doc. 2) I "self-installed" pkg; this brought with it apr-1.5.2.1.5.4_1 db5-5.3.28_4 expat-2.1.1_2 gdbm-1.12 gettext-runtime-0.19.8.1 indexinfo-0.2.4 readline-6.3.8 serf-1.3.8_1 sqlite3-3.13.0 3) Next: root@>> pkg install subversion which I used to populate the ports tree. 4) Now, to install portmaster. That requires dialog4ports: root@>> make clean ===> Cleaning for dialog4ports-0.1.6 root@>> make ===> License BSD2CLAUSE accepted by the user ===> dialog4ports-0.1.6 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by dialog4ports-0.1.6 for building ===> Extracting for dialog4ports-0.1.6 => SHA256 Checksum OK for dialog4ports-0.1.6.tar.gz. ===> Patching for dialog4ports-0.1.6 ===> Configuring for dialog4ports-0.1.6 ===> Building for dialog4ports-0.1.6 --- dialog4ports.o --- --- mixedlist.o --- --- dialog4ports.1.gz --- --- dialog4ports.o --- cc -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -pedantic -c dialog4ports.c -o dialog4ports.o --- mixedlist.o --- cc -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -pedantic -c mixedlist.c -o mixedlist.o --- dialog4ports.1.gz --- gzip -cn dialog4ports.1 > dialog4ports.1.gz --- dialog4ports --- cc -O2 -pipe -fstack-protector -fno-strict-aliasing -Wall -pedantic dialog4ports.o mixedlist.o -o dialog4ports -lncursesw -lm -ldialog ===> Staging for dialog4ports-0.1.6 ===> Generating temporary packing list install -m 555 dialog4ports /data/port-work/usr/ports/ports-mgmt/dialog4ports/work/stage/usr/local/bin install -m 0644 dialog4ports.1.gz /data/port-work/usr/ports/ports-mgmt/dialog4ports/work/stage/usr/local/man/man1 > Compressing man pages (compress-man) root@>> make install ===> Installing for dialog4ports-0.1.6 ===> Checking if dialog4ports already installed ===> Registering installation for dialog4ports-0.1.6 Installing dialog4ports-0.1.6... Child process pid=6648 terminated abnormally: Bus error *** Error code 138 Stop. ... and pkg-static drops a core file. I get this (with different pids) for _every_ port on "make install". Never seen this before. Google offered no possible causes. "Bus error" means a memory violation - and I have no idea how to proceed. The core file has no debugging symbols, making a backtrace useless. Exasperatedly, Robert Huff ___ 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: OpenCASCADE 6.9.1
Andrea Venturoli writes:
> On 10/30/15 13:25, Kurt Jaeger wrote:
>
> > There's no public distfile, only available if one registers ?
>
> Exactly.
During the time before the advent of OpewnJDK, one had to do something
similar to get the sources to Sun's Java. No re-hosting allowed.
` Respectfully,
Robert Huff
___
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"
building broken after today's update
(This (as far as I know) is something I've screwed up, not a problem with the ports build process; I just need some help setting things right.) After a morning of updating various ports, the build process is broken; specifically, it _appears_ to involve make. Test case: huff@ cd /usr/ports/misc/pciids huff@ make clean ... and nothing happens. After waiting a few seconds start hitting 'ctl-t' and get this: load: 0.20 cmd: sh 41244 [running] 0.00r 0.00u 0.00s 1% 1388k make[2]: Working in: /usr/ports/lang/python33 make[11]: Working in: /usr/ports/lang/python33 make[1]: Working in: /usr/ports/lang/python33 make[3]: Working in: /usr/ports/lang/python33 make[9]: Working in: /usr/ports/lang/python33 make[7]: Working in: /usr/ports/lang/python33 make[12]: Working in: /usr/ports/lang/python33 make[14]: Working in: /usr/ports/lang/python33 make[6]: Working in: /usr/ports/lang/python33 make[5]: Working in: /usr/ports/lang/python33 make[4]: Working in: /usr/ports/lang/python33 make[10]: Working in: /usr/ports/lang/python33 make[15]: Working in: /usr/ports/lang/python33 make[13]: Working in: /usr/ports/lang/python33 make: Working in: /usr/ports/misc/pciids make[8]: Working in: /usr/ports/lang/python33 load: 0.20 cmd: sh 41403 [running] 0.00r 0.00u 0.00s 2% 332k make[23]: Working in: /usr/ports/lang/python33 make[18]: Working in: /usr/ports/lang/python33 make[14]: Working in: /usr/ports/lang/python33 make: Working in: /usr/ports/misc/pciids make[3]: Working in: /usr/ports/lang/python33 make[17]: Working in: /usr/ports/lang/python33 make[16]: Working in: /usr/ports/lang/python33 make[9]: Working in: /usr/ports/lang/python33 until I ctl-c out. I have no idea what happened; as far as I know there's no reason for make to involve python. Help, please? Bewildered, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
package availability
I'm looking for a package of fftw3-3.3.3_2, built for amd64 with default options. pkg search fftw3 reports 3.3.3_1. When is 3.3.3_1 likely to become available? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: package availability
Baptiste Daroussin b...@freebsd.org writes: Right now packages are built weekly (build start every wednesday 1am UTC) once built they are automatically published and available to users within the next days. Understood. I will keep trying. If it hasn't shown up by Monday ... I will probably be back. :-) Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: problem with devel/glib20
From: Marcus von Appen m...@freebsd.org To: Robert Huff roberth...@rcn.com Cc: po...@freebsd.org Subject: Date: Thu, 4 Sep 2014 08:03:36 +0200 --w7PDEPdKQumQfZlR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On, Thu Sep 04, 2014, Robert Huff wrote: [glib20 + python files installation issue] https://svnweb.freebsd.org/ports?view=revisionrevision=367216 A fix was committed yesterday (see above), most likely after you tried to build glib20. Can you update to your ports tree and try again? I can, and I did, and it worked. Winner! Thanks, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
reinstalling from portmaster backup package
Through a series of steps I won't get into. I deinstalled port X.1 in anticiparion of installing X,2. However, X.2 (built fine but) failed to install. (I'm working on that.) Fortunately, I have a portmaster backup of X.1 which I need to reinstall in the meantime. Unfortunately, I find the portmaster documentation ... obscure ... on how to do this. (OK, so I'm used to ports not packages.) Can someone tell me the command to reinstall (and reregister) X.1? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
problem with devel/glib20
[I have sent mail to the maintainer, but not heard back. The matter is somewhat pressing, so here I am ] I'm trying to move from glib-2.36.3_3 to _4. The build appears to go correctly. However, make install produces this: === Installing for glib-2.36.3_4 === glib-2.36.3_4 depends on file: /usr/local/bin/python3.3 - found === glib-2.36.3_4 depends on file: /usr/local/bin/perl5.16.3 - found === glib-2.36.3_4 depends on shared library: libpcre.so - found (/usr/local/lib/libpcre.so.3) === glib-2.36.3_4 depends on shared library: libffi.so - found (/usr/local/lib/libffi.so.6.0.1) - found (/usr/local/lib/gcc47/libffi.so.4) === glib-2.36.3_4 depends on shared library: libintl.so - found (/usr/local/lib/libintl.so.9) === glib-2.36.3_4 depends on shared library: libiconv.so.3 - found (/usr/local/lib/libiconv.so.3) === Checking if glib already installed === Registering installation for glib-2.36.3_4 pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/__init__.pyc): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/__init__.pyo): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/codegen.pyc): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/codegen.pyo): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/codegen_docbook.pyc): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/codegen_docbook.pyo): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/codegen_main.pyc): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/codegen_main.pyo): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/config.pyc): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/config.pyo): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/dbustypes.pyc): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/dbustypes.pyo): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/parser.pyc): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/parser.pyo): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/utils.pyc): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/devel/glib20/work/stage/usr/local/share/glib-2.0/codegen/utils.pyo): No such file or directory *** Error code 74 Google has no record of anything like this. So: 1) Is this a problem with the port, or is there something I need to reinstall or reconfigure? (I'll take a pointer to the right answer.) 2) Given the system is running: FreeBSD 11.0-CURRENT #1 r264673: Sat Apr 19 09:43:10 EDT 2014 amd64 is there a sanctioned package out there? pkg install devel/glib20 only gets me _3. Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
question about pkg install
Scenario: I have a program (several, actually) I need to install from the generic package repository. These programs depend on openldap-client; however I have openldap-sasl-client installed. In my experience the two have been interchangeable when compiling from ports. Is there a way to tell 'pkg install' Yeah, I know it says openldap-client, but the same version of openldap-sasl-client satisfies the dependency? Or do I just use 'pkg install -M' and hope everything works? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: PKG 3.1.0 update - Segmentation fault: 11
Jos Chrispijn writes: Baptiste Daroussin: This is a known one I'm very sorry about but tricky to fix, to solve it, open your /usr/local/etc/pkg.conf you might have a duplicated entry in alias (probable leaf), remove the second one, that will solve your problem. regards, Bapt thanks, will try and let you know once being successfully. It worked for me. Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
updating db6?
I have ~10 programs that use db6, and I'd like to use the released version. However ... the update procedure discussed in ports/UPDATING is way beyond my pay-grade. Is it really that complicated? If so, has anyone put the essentials into a script they'd be willing to share? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: libxul.so rebuilt, still a version error.
J Bouqet writes: /usr/local/lib/firefox/libxul.so /usr/local/lib/libxul//libxul.so /usr/local/lib/libxul/sdk/lib/libxul.so /usr/local/lib/seamonkey/libxul.so /usr/local/lib/thunderbird/libxul.so Rebuilt libxul. IIRC that persists even after copying the new libxul to the seamonkey location. Sometime back I was told while doing this is unlikely to damage anything, it is in fact The Wrong Answer(tm). There are specific reasons why (most) Mozilla products build their own versions of libxul, even when the supposedly suitable standalone lib is available. For more information, talk to the folks on gecko@. Which brings up the obvious question: you rebuilt standalone libxul. Did you also rebuild Firefox/Seamonkey/Thunderbird/etc.? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: libxul.so rebuilt, still a version error.
I have learned to treat any bump in the version of {libxul, SeaMonkey,
FireFox, ThunderBird, etc.} as heads-up for a bump of the rest; if that
doesn't happen in a few days I start to ask why?.
And if you don't have a tool for cleaning out obsolete libraries, get
one now. I use the -L option of portupgrade as I have not been able
to figure out how to get portmaster (of pkg) to do the same
Respectfully,
Robert Huff
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: print/cups-base won't build due to dwarf error in /usr/bin/ld
Thomas Mueller mueller6...@bellsouth.net writes: I do no better with avahi or mdnsresponder, and I tried both. Just a different error: On a system running FreeBSD 11.0-CURRENT #1 r264673: Sat Apr 19 09:43:10 EDT 2014 amd64 and all relevant ports current, adding the AVAHI option allowed me to build and install. One data point, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
second call: dns/libidn staging broken
This port builds fine, or seems to. However, when I try to install I get this: === Installing for libidn-1.28_1 === libidn-1.28_1 depends on shared library: libintl.so - found (/usr/local/lib/libintl.so.9) === Checking if dns/libidn already installed === Registering installation for libidn-1.28_1 pkg-static: lstat(/data/port-work/usr/ports/dns/libidn/work/stage/usr/local/share/emacs/site-lisp/idna.el): No such file or directory pkg-static: lstat(/data/port-work/usr/ports/dns/libidn/work/stage/usr/local/share/emacs/site-lisp/punycode.el): No such file or directory *** Error code 74 Stop. make[1]: stopped in /usr/ports/dns/libidn *** Error code 1 I'm not seeing this type of error with other ports so I think it's local breakage. I've written to the maintainer (a week ago) and had no response. (This is blocking the curl update; I could turn off IDN support there, but would much rather not.) Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
second call: dns/libidn staging broken
Kevin Oberman writes:
This port builds fine, or seems to. However, when I try to
install I get this:
Looks like it might be an issue with your build environment. Looks
like you have customized your build directories (/data/port-work). I
suspect something might be wrong there. I have seen several reports
of issues when symlinks are used in these types of customizations.
It's not a sym-link, it's an evnironment variable:
WRKDIRPREFIX=/data/port-work
This was done because certain large ports (e.g. libreoffice) were
eating up all the free space on /usr. So I pointed the work directory
to /data, which has 200+ gbytes free. This works fine except is rare
cases like this one.
So ... how do I go about further diagnosing the breakage and getting
that to {maintainer, pkg-ng team} who can Do the Right Thing?
Respectfully,
Robert Huff
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
second call: dns/libidn staging broken
Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org writes:
It's not a sym-link, it's an evnironment variable:
WRKDIRPREFIX=/data/port-work
This was done because certain large ports (e.g. libreoffice)
were eating up all the free space on /usr. So I pointed the work
directory to /data, which has 200+ gbytes free. This works fine
except is rare cases like this one.
I've seen some funny things with WRKDIRPREFIX too, but I can't reproduce
them. I've mostly seen it on my chroot tinderbox, which always runs with
WRKDIRPREFIX set because the ports tree is mounted read-only. The
tinderbox is currently broken for other reasons.
I tried unsetting the environment variable, and it died in exactly the
same way. Which brings me back to:
So ... how do I go about further diagnosing the breakage and
getting that to {maintainer, pkg-ng team} who can Do the Right Thing?
Respectfully,
Robert Huff
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
second call: dns/libidn staging broken
[resent with corrected attribution]
Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org writes:
It's not a sym-link, it's an evnironment variable:
WRKDIRPREFIX=/data/port-work
This was done because certain large ports (e.g. libreoffice)
were eating up all the free space on /usr. So I pointed the work
directory to /data, which has 200+ gbytes free. This works fine
except is rare cases like this one.
I've seen some funny things with WRKDIRPREFIX too, but I can't
reproduce them. I've mostly seen it on my chroot tinderbox, which
always runs with WRKDIRPREFIX set because the ports tree is mounted
read-only. The tinderbox is currently broken for other reasons.
I tried unsetting the environment variable, and it died in exactly the
same way. Which brings me back to:
So ... how do I go about further diagnosing the breakage and
getting that to {maintainer, pkg-ng team} who can Do the Right Thing?
Respectfully,
Robert Huff
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
second call: dns/libidn staging broken
Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org writes: Looking at the configure output for libidn, I'll guess that you don't have emacs installed when you try to install libidn, so the configure script decides not to install the elisp (.el) files, and staging chokes because it depends more heavily on the plist than the old port system did. You can look at the generated config.log to see if it backs me up on this. That explains the symptoms, and (if true) exposes the breakage: I don't have emacs installed ... but I do have xemacs. And yes, they install their libraries to different paths. I know less than nothing about configure scripts: is there a place where a simple fudge would make it work? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
libidn issue?
Anyone else have a problem with the staging step of libidn? (Or is this a known problem Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: libfreetype.so.9 errors
With respect to the missing libxcb.so.2: try re-building open-motif. This updated libXm, which made a large number of these vanish. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: libfreetype.so.9 errors
On 4/20/2014 1:18 PM, Beeblebrox wrote: Latest compiled ports result in below message for several binaries: Shared object libfreetype.so.9 not found, required by chrome So far the ports I have seen this are www/midori, www/chromium, editors/libreoffice; but I have not tested all ports installed on the system. Add www/opera to the list. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
replacing gcc with clang
Is there a authoritative list of those ports know to not build with clang 3.2/3.4? Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
pkgng abilities (was: pkgng vs. portupgrade reporting ports outdated)
Matthew Seaman matt...@freebsd.org writes: pkg(8) does a damn sight more than the old pkg_tools. Granted, though much of it I currently have little use for. :-) pkgng can do almost everything the old system can, and does it better. s/almost// OK, Obi-wan - what's the replacement for: a) portsclean with the C, D (single and double), and L options? (Use no more than two commands.) b) pkg_sort ? With these, I will cheerfully delete portupgrade. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng vs. portupgrade reporting ports outdated
sindrome sindr...@gmail.com With pkgng I issue a 'pkg update' followed by a 'pkg upgrade' and it shows me x number of ports that need to be updated. So it updates and completes just fine and of course it's much faster than building from source. So I still keep my source, ports and docs in sync via svn update. Here's where the issue comes in. After I have done the pkg upgrade and it tells me all is up-to-date, the 'pkg_version -v |grep needs' command shows me dozens of ports that are not up-to-date and further the versions it's saying I have installed are not consistent with the versions that were installed through pkgng. It is my understanding it is generally a bad idea to mix the old and new package systems. (It can be done, but it's beyond my pay grade and if you're asking this I'd guess it is - at the moment - beyond yours.) pkgng can do almost everything the old system can, and does it better. (Now if it only had a replacement for pkg_sort ) Each records its status quo in distinct and incompatible ways. When I want to know what needs updating I use: huff pkg version -v -l \ which I can send either to a file, or to e-mail, or to a script wrapped around portmaster. Does this help? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Libiconv confusion on 10.0-RELEASE
Johan Hendriks joh.hendr...@gmail.com writes: As far as I know, there is some libiconv functionality missing in the base libiconv implementation. That is the reason some ports installed converters/libiconv from ports. From reading the mailing lists and skimming the PRs, it appears subversion may be such a port. Is there a current list of ports know to need the ports version of iconv? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
problem with vulnxml.xml after system update
After updating a system to: FreeBSD 11.0-CURRENT #0 r263263: Mon Mar 17 15:09:18 EDT 2014 amd64 all attempts to build ports hit this: pkg-static: unable to open vulnxml file /var/db/pkg/vuln.xml: Invalid argument I've never seen this before; it isn't mentioned in src/UPDATING or ports/UPDATING; and googling produces nothing useful. The file exists, has size zero, is owned by root:wheel. What have I missed? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: problem with vulnxml.xml after system update
olli hauer writes: # cp /usr/ports/security/vuxml/vuln.xml /var/db/pkg/ This fixed it. Thanks. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: changes to base system DNS
Warren Block writes: From dim memory of a couple of weeks ago... Making sure I understand: doing this (or the corrected version) will bring up named at the same point in the boot process as using system named in previous versions? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Replacement for sysutils/wait_on
Andrea Venturoli writes: I have a script which monitors a directory and wakes up as soon as a new file appears. I'm using sysutils/wait_on for this, but this port expired a few days ago. Is there a drop in replacement? Any other suggestion? Isn't there a component of the GNOME suite which does this? Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
script to identify required compiler?
Is there a script - either in base or as part of a port - that will identify which ports require a compiler other than the system-default compiler (and which compiler that is)? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [graphics/libcdr] Boost issue breaks build?
A.J. 'Fonz' van Werven writes: I'm trying to build editors/libreoffice, which fails at the dependency graphics/libcdr. I've got exactly the same issue. I have sent e-mail to various maintianers, but had no reply. Respectfully Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
can't build gimp-help-en due to missing Sourceforge file
[I sent mail to the maintainer (cc'ed: here) but had no respeonse. And there's nothing about it in UPDATING. So ...] While attempting to update to the latest version I get: Copying images (en) ... 1605 *** Making html for en ... I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl warning: failed to load external entity http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl; compilation error: file stylesheets/plainhtml.xsl line 10 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl gmake[1]: *** [html/en/index.html] Error 5 Is there something I've failed to update, or even install? What's up, and how does it get fixed? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
radeonhd driver DEPRECATED?
Or so the Makefile says. What's the canonical replacement? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: radeonhd driver DEPRECATED?
Niclas Zeising writes: Or so the Makefile says. What's the canonical replacement? xf86-video-ati. The xf86-video-radeonhd hasn't seen any upstream development since 2010. Thanks. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
about the Berkeley DB 4 cleanup
[Ref: ports/UPDATING 20131214] I am an indirect user of BDB (currently ver 4.3); pkg version -r reports redland-1.0.16 ruby19-bdb43-0.6.6_1 webalizer-geoip-2.23.8 php5-5.4.21 xmms-1.2.11_20 libreoffice-4.0.6_1 gramps-3.3.0_2 docproj-2.0_1 librcc-0.2.12 apr-1.4.8.1.5.3 apache24-2.4.6_1 subversion-1.8.5 py27-bsddb-2.7.6_3 portupgrade-2.4.11.3,2 as being dependant, and I suspect the list will be longer with each passing day. While I appreciate the work done to move the universe along, the upgrade instructions included (by reference) are partially past my understanding and _way_ beyond my comfort zone. (And I suspect I'm not alone.) So: what explodes if I simply set WITH_BDB_VER=5, shutdown my services, and rebuild? Alternately: does someone whose comfort zone this is well within) have a script that will take care of things? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
no db after crash; portmaster unhappy
One of my machines crashed this morning, and lost /usr/ports/db - the directory and everything in it. Portmaster refuses to run. How do I re-create that information? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
arts 1.5.10 deprecated
An attempt to rebuild this brought a message saying the port is deprecated due to dependency on qt3. Considering I have at least a dozen ports listed as dependencies - including gimp, sdl_*, and mplayer - what is the recommended replacement? Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: arts 1.5.10 deprecated
Matthias Apitz writes: An attempt to rebuild this brought a message saying the port is deprecated due to dependency on qt3. Considering I have at least a dozen ports listed as dependencies - including gimp, sdl_*, and mplayer - what is the Btw: I do not see that mplayer depends on qt3 stuff: $ pkg_info -r mplayer-1.1.r20130308 | fgrep qt3 recommended replacement? In general, the answer will be: use qt4-* ports :-( As soon as a) I know what the equivalent is and b) it compiles and runs. I am happy to know arts is an indirect dependency (probably thought the sdl_*) and mplayer /et al./ will hopefully continue to function. Not happy I do not have the skill to disentangle this and know for sure. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
qt3 - qt4 question
1) I have x11-toolkits/qt-copy (part of qt33) installed, and at least a dozen ports that depend on it. 2) Attempts to upgrade devel/qt4-corelibs fail on complaints the two conflict. 3) I cannot find a qt4-copy, and there is no mention of this in UPDATING going back three years. 4) What is the correct successor for qt-copy? Is that functionality been included elsewhere in qt4? 5) Is there a way to determine which (if any) of the dependent ports will have issues with the conversion? Right now the choice seems to be between a) inspecting the Makefiles (my make-fu is at the slapstick comedy level) and b) just doing and hoping nothing breaks. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
