checking dependency tree ia portmaster

2016-11-05 Thread @lbutlr
given a port that is listed in postmaster -l as a Branch port, how do I see its dependancies and what it depends on? For example, I have libX11 listed as a Branch port and would like to see all the “upsteream: and “downstream” ports. ___

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread Andrey Chernov
The instruction posted to UPDATING is a bit incomplete. Additionlly portupgrade -f "p5-*" should run to move all ports still sitting in 5.20 directory, even if they are not depending on perl lib. ___ freebsd-ports@freebsd.org mailing list

Re: devel/llvm38 install seems to be missing files (e.g., FileCheck)

2016-11-05 Thread David Wolfskill
On Sat, Nov 05, 2016 at 05:08:46PM +0100, Dimitry Andric wrote: > On 05 Nov 2016, at 16:58, Rainer Hurling wrote: > ... > >> Am I incorrect in thinking that devel/llvm38 has a problem, though, in > >> that "%%LIT%%llvm38/bin/FileCheck" is in that port's pkg-plist, and > >>

Re: devel/llvm38 install seems to be missing files (e.g., FileCheck)

2016-11-05 Thread Dimitry Andric
On 05 Nov 2016, at 16:58, Rainer Hurling wrote: > > Am 05.11.2016 um 14:54 schrieb David Wolfskill: >> On Sat, Nov 05, 2016 at 05:26:33AM -0700, David Wolfskill wrote: >>> ... >>> I circumvented the problem: ... >>> >>> g1-252(11.0-S)[20] sudo cp -p !$ /usr/local/llvm38/bin/

Re: devel/llvm38 install seems to be missing files (e.g., FileCheck)

2016-11-05 Thread Rainer Hurling
Hi David, Am 05.11.2016 um 14:54 schrieb David Wolfskill: > On Sat, Nov 05, 2016 at 05:26:33AM -0700, David Wolfskill wrote: >> ... >> I circumvented the problem: ... >> >> g1-252(11.0-S)[20] sudo cp -p !$ /usr/local/llvm38/bin/ >> sudo cp -p work/stage/usr/local/llvm38/bin/FileCheck

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread Piotr Szafarczyk
On 2016-11-05 15:33, tech-lists wrote: On 05/11/2016 14:18, Tijl Coosemans wrote: It's probably caused by pkg not copying hardlinks: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213255 What version of pkg are we using? Mine is 1.9.3 My problems were because of 1.8.7. With 1.9.3 (and

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread tech-lists
On 05/11/2016 14:48, tech-lists wrote: On second thoughts, I don't think it was this because the portupgrade tool builds a package, removes the old one then installs the new one. The bug you posted says the problem doesn't happen when one makes the package. edit: i think my issue was slightly

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread tech-lists
On 05/11/2016 14:18, Tijl Coosemans wrote: It's probably caused by pkg not copying hardlinks: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213255 On second thoughts, I don't think it was this because the portupgrade tool builds a package, removes the old one then installs the new one.

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread Piotr Szafarczyk
On 2016-11-05 15:18, Tijl Coosemans wrote: It's probably caused by pkg not copying hardlinks: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213255 Hi, Wonderful! This is exactly my problem. Using pkg add installs all the files. Thanks a lot. Regards, Piotr

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread tech-lists
On 05/11/2016 14:18, Tijl Coosemans wrote: It's probably caused by pkg not copying hardlinks: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213255 What version of pkg are we using? Mine is 1.9.3 -- J. ___ freebsd-ports@freebsd.org mailing list

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread Tijl Coosemans
On Fri, 4 Nov 2016 23:00:56 + tech-lists wrote: > On 04/11/2016 22:58, tech-lists wrote: >> On 03/11/2016 15:00, Mathieu Arnold wrote: >>> Instructions on how to switch are in UPDATING. >>> >>> If you do not want to switch, you do not have to do anything. >> >> I

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread Piotr Szafarczyk
On 2016-11-05 14:51, tech-lists wrote: Everything? Could you try any other port that creates links? Are links created? By "links" do you mean "installed usable links into /usr/local/bin" then yes. A little earlier today I built and installed libreoffice from ports, without issue. $ ls -lah

Re: FreeBSD Port: fusefs-wdfs-1.4.2_6

2016-11-05 Thread Matthieu Volat
On Fri, 4 Nov 2016 11:19:11 +0100 Ruud Boon wrote: > Hi, > > I’m wondering if this port is still maintained. > Under FreeBSD 10.3 it looks like it’s failing (trying to mount a webdav > result is disappearing mount directory) > Hi, I also ran into various issues with wdfs,

Re: devel/llvm38 install seems to be missing files (e.g., FileCheck)

2016-11-05 Thread David Wolfskill
On Sat, Nov 05, 2016 at 05:26:33AM -0700, David Wolfskill wrote: > ... > I circumvented the problem: ... > > g1-252(11.0-S)[20] sudo cp -p !$ /usr/local/llvm38/bin/ > sudo cp -p work/stage/usr/local/llvm38/bin/FileCheck /usr/local/llvm38/bin/ > g1-252(11.0-S)[21] > > That done, lang/rust built.

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread tech-lists
On 05/11/2016 11:46, Piotr Szafarczyk wrote: Everything? Could you try any other port that creates links? Are links created? By "links" do you mean "installed usable links into /usr/local/bin" then yes. A little earlier today I built and installed libreoffice from ports, without issue. $

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread tech-lists
On 05/11/2016 11:46, Piotr Szafarczyk wrote: Everything? Could you try any other port that creates links? Are links created? Seems so. What port(s) would you like me to try? -- J. ___ freebsd-ports@freebsd.org mailing list

Re: devel/llvm38 install seems to be missing files (e.g., FileCheck)

2016-11-05 Thread David Wolfskill
On Thu, Nov 03, 2016 at 05:50:07AM -0700, David Wolfskill wrote: > After seeing that lang/rust failed to build again today (it had also > failed yesterday), I decided to actually check the typescript file (from > the portmaster run) to see if I could figure out what was wrong. > I

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread Piotr Szafarczyk
On 2016-11-05 10:58, tech-lists wrote: It looks like the same problem I encountered with 5.20 under 10.3 (just one box). Links are not created during port building (with other than perl too). With perl, two links are missing under /usr/local/bin. Creating them manually allows for a successful

Re: mail/{neo,}mutt: why not packaged with gpgme?

2016-11-05 Thread Baptiste Daroussin
On Wed, Nov 02, 2016 at 09:45:51PM +0100, Niklaas Baudet von Gersdorff wrote: > Hello, > > While talking about an issue I have with mail/{neo,}mutt and > security/gnupg on #gnupg on freenode I was advised to use > security/gpgme with mutt. I haven't been using gpgme for a while, > mainly because

Re: mail/{neo,}mutt: why not packaged with gpgme?

2016-11-05 Thread Baptiste Daroussin
On Wed, Nov 02, 2016 at 09:45:51PM +0100, Niklaas Baudet von Gersdorff wrote: > Hello, > > While talking about an issue I have with mail/{neo,}mutt and > security/gnupg on #gnupg on freenode I was advised to use > security/gpgme with mutt. I haven't been using gpgme for a while, > mainly because

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread tech-lists
On 05/11/2016 07:12, Piotr Szafarczyk wrote: Hi, It looks like the same problem I encountered with 5.20 under 10.3 (just one box). Links are not created during port building (with other than perl too). With perl, two links are missing under /usr/local/bin. Creating them manually allows for a

FreeBSD ports you maintain which are out of date

2016-11-05 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated,

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-05 Thread Piotr Szafarczyk
On 2016-11-05 00:00, tech-lists wrote: On 04/11/2016 22:58, tech-lists wrote: On 03/11/2016 15:00, Mathieu Arnold wrote: I followed the instructions in /usr/ports/UPDATING for portupgrade. I have found that numerous ports will not build: edit: the error I get now when I try to rebuild an