Re: Ports recompile for 13.0-RELEASE

[@lbutlr]

On 04 May 2021, at 09:00, Ronald Klop  wrote:
> On 5/4/21 4:10 PM, @lbutlr wrote:
>> With the move to FreeBSD 13.0 is there a simple (single step) way to 
>> reinstall all the current ports other than saving off a list of the ports 
>> and then stepping through that list to reinstall them? It was very 
>> inefficient when moving to 12.0 as many ports in the list, of course, were 
>> dependent on other ports, but then got recompiled, sometimes multiple times. 
>> I know I ended up in a make loop where came was compiled over and over again 
>> until I aborted, listed the current ports, differ on the previous ports, and 
>> picked a port I though would have a lot of reps to restart the compile. I 
>> then did this several more times to get back to where I had been on 11.x
> 
> I used "portmaster -fa" in the past.

Yeah, that's what I tried wen moving to 12.0 from 11.4 and it left a lot of 
cleaning up.

>> (And yes, I've tried moving to poudrerie several times and we do not get on. 
>> At all.)
> 
> Might help to do another attempt. Especially if you are using custom port 
> settings instead of pkgs.

It just doesn't work the way my brain works, and I don't have a bunch of 
servers I need to keep updated, and the two servers I am running are different 
architecture. Something as simple as "hey, I want to install this one port" 
seemed overly complicated. I can see it's great when you have a cluster of 
servers and want to manage the updates on a dedicated server, but I don't need 
that.

That said:

 # pkg-static upgrade -f
 # portmaster install postfix dovecot 

So far, so good (I thought I would have to also redo MariaDB but it all seems 
to be working now, mail did not work until I recompiled Dovecot and Postfix, 
but I was expecting that.

So far the only thing that is new is an error about pam_opie, but that's for a 
new thread.

-- 
Incredible! One of the worst performances of my career and they never
doubted it for a second.

___
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"

Ports recompile for 13.0-RELEASE

[@lbutlr]

With the move to FreeBSD 13.0 is there a simple (single step) way to reinstall 
all the current ports other than saving off a list of the ports and then 
stepping through that list to reinstall them? It was very inefficient when 
moving to 12.0 as many ports in the list, of course, were dependent on other 
ports, but then got recompiled, sometimes multiple times. I know I ended up in 
a make loop where came was compiled over and over again until I aborted, listed 
the current ports, differ on the previous ports, and picked a port I though 
would have a lot of reps to restart the compile. I then did this several more 
times to get back to where I had been on 11.x

And there's still no way to tell if a port was installed from pkg or from 
ports, correct? Since I use MariaDB instead of MySQLI have to be sure I don't 
try to use package for anything that will try to install MySQL instead.

And finally, the release of 13.0 ends the 12.x versions, right? There will not 
be a 12.3.

(And yes, I've tried moving to poudrerie several times and we do not get on. At 
all.)

-- 
I don't need no stinking taglines.

___
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 update 3.7->3.8

[@lbutlr]

On 26 Apr 2021, at 20:43, Rozhuk Ivan  wrote:
> This long command hanle files that requires shebang:
> portmaster -BvD -y --no-confirm --delete-build-only `grep -rsp "\/python3\.7" 
> /usr/local/ | grep -v '/usr/local/man/' | grep -v '/usr/local/lib/python3' | 
> sed -e 's|:.*||' -e 's|Binary file ||' -e 's| matches||' | xargs pkg which 
> -oq | sort -u`

What grep are you using?

/usr/bin/grep -rsp "python3\.7" /usr/local/ => grep: invalid option -- p

(FreeBSD 12.2, grep (GNU grep) 2.5.1-FreeBSD)

-- 
Margo: Although Dark King is a little generic as far as villain names go,
   wouldn’t you say?
Eliot: I have notes.

___
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: Mariabackup core dump

[@lbutlr]

On 20 Apr 2021, at 11:34, Kurt Jaeger  wrote:
> 
>> 
>> 
>> This was posted 3 years ago, and I am having the identical issue. From what 
>> I can see on that page, no activity has taken place. Anyone have any ideas?
>> 
>> (It does seem to work fine if you give the full path, but needless to say, 
>> I'm slightly concerned about that error)
> 
> Which version of FreeBSD and which version of mariadb can reproduce this ?

FreeBSD 12.2 and MariDB 10.3.28 for me, though not for the original bug report, 
I think that was mariaBD 10.2 and not sure what version of FreeBSD.


-- 
I have NOT lost my mind!  I've got a backup around here somewhere.

___
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"

Mariabackup core dump

[@lbutlr]

This was posted 3 years ago, and I am having the identical issue. From what I 
can see on that page, no activity has taken place. Anyone have any ideas?

(It does seem to work fine if you give the full path, but needless to say, I'm 
slightly concerned about that error)

-- 
Windle shook his head sadly. Five exclamation marks, the sure sign of
an insane mind. --Reaper Man

___
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: gitup issues [was Re: No update for a day on ports?]

[@lbutlr]

On 10 Apr 2021, at 19:34, Peter Jeremy via freebsd-ports 
 wrote:
> On 2021-Apr-01 22:36:02 +1100, Trev  wrote:
> 
> One consequence is that gitup is unusable
> on small memory environments - in my case, I saw peak memory usage hit
> 5GB (though the largest file I have is 1.8GB, so I'm not sure why it's
> eating so much memory).

As a data point my servers only have 4GB or RAM and gitup runs fine.

(One is a Celeron J1800 and the other an i5-3470, the Celeron is dog slow 
running gitup, but it runs).

(~1 minutes for the i5, 25 min for the Celery)

This makes me wish even more there was a simple way to exclude categories for 
the ports tree like all the foreign languages and x11 games and audio (for me, 
of course)

Actually, all my installed ports only come from these trees:

archivers benchmarks converters databases devel dns editors
ftp lang mail math misc net ports-mgmt print security shells
sysutils textproc and www

I'd love to be able to only sync, download, and check those categories, granted 
that include the six largest categories and 8 of the top ten, so not sure how 
much it would help, but it would help some.

-- 
My little brother got his arm stuck in the microwave. So my mom had
to take him to the hospital. My grandma dropped acid this
morning, and she freaked out. She hijacked a busload of penguins.
So it's sort of a family crisis. Bye!

___
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"

gitup on two machines

[@lbutlr]

I have tow machines, both on 12.2-RELEASE

Running `gitup ports` on one server updates the ports tree. Running the the 
same command with the same configuration (pointing at the GitHub mirror in both 
cases) just sits there with no feedback and does nothing, even if I run it with 
a -v 2 flag.

   "ports" : {
"host"   : "github.com",
"repository" : "/freebsd/freebsd-ports.git",
"branch" : "main",
"target" : "/usr/ports",
"ignores": [
"distfiles",
"packages",
],
},

Server1 is x86 and Server2 is amd64


-- 
"Are you pondering what I'm pondering?"
"Whuh... I think so, Brain, but... but if Charlton Heston doesn't eat
Soylent Green, what will he eat?"

___
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: gitip usage.

[@lbutlr]

On 04 Apr 2021, at 10:46, Jeffrey Bouquet via freebsd-ports 
 wrote:
> running 12.2 STABLE,

Curious, why are you not running the RELEASE version of 12.2?

-- 
"Are you pondering what I'm pondering?"
"I think so, Brain. But Trojans won’t arrive on the scene for another
300 years."

___
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: No update for a day on ports?

[@lbutlr]

On 01 Apr 2021, at 01:54, Milan Obuch  wrote:
> This is unpleasant move for me. This means git or equivalent (and
> dependencies) must be installed on any box where tracking ports tree is
> planned/needed... and no tool like svnlite could be expected in base
> system for some time.

You only need to install git if you are going to keep git commit hostly and 
branches of the ports, which  you would already be doing if that was something 
you needed, I'd think. Simply updating the ports tree does not require 
installing git.

> So I need some work on my local infrastructure to adjust to this move.

I don't think so, I am pulling the ports tree from the git repo without git 
installed.

 # portmaster -l | grep git
===>>> gitup-0.90_1
 #


-- 
I do believe Marsellus Wallace, my husband, your boss, told you to
take *me* out and do *whatever I wanted*. Now I wanna dance, I
wanna win. I want that trophy, so dance good.

___
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: Deprecation of portsnap (was: Proposed ports git transition schedule)

[@lbutlr]

On 01 Apr 2021, at 04:19, Felix Palmen  wrote:
> * Christoph Moench-Tegeder  [20210326 19:45]:
>> ## Felix Palmen (fe...@palmen-it.de):
>>> I'd assume (someone may correct me) that portsnap will still be
>>> supported,

>> https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119098.html

> Is this finally decided, and is there a timeline?

That post I read as the official decision that port snap was going to die. But  
WITHOUT_PORTSANP added to the default base would be the single, I'd think. Most 
of the ground work has already been done.

> portsnap is still built by default on releng/13.0.

We'll see if it makes it to RELEASE or not.

gitup is working well right now, but it looks more fiddly and I wish the 'fake 
JSON' configuration file was actual valid JSON, OTOH, it seems o run a lot 
faster than portsnap.


-- 
I WILL NOT TRADE PANTS WITH OTHERS Bart chalkboard Ep. 7F05

___
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: Lessons from the PHP git repo "hack"

[@lbutlr]

On 31 Mar 2021, at 12:02, Jose Quinteiro  wrote:
> I've found passwords checked into public Github repos more than once. I
> don't equate Github with security.

Have you also found the code necessary to replicate a 2FA token checked in to a 
GitHub repo?

-- 
I WILL NOT DO THE DIRTY BIRD Bart chalkboard Ep. AABF08

___
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: Lessons from the PHP git repo "hack"

[@lbutlr]

On 31 Mar 2021, at 07:58, Felix Palmen  wrote:
> * @lbutlr  [20210331 07:47]:
>> Which brings me to the reason for this post, as it seems that the
>> ports collection of FreeBSD 13.x will be in the same position, running
>> a private git server network and using GitHub as a mirror and I wonder
>> if some lessons from php's experience with this should be considered
>> for this setup before it's implemented.
> 
> Apart from the fact there's only one ports tree…

How does that make any difference? If someone gains access to the repo and 
makes changes everyone gets this changes.

> I'd say the lesson is keep your systems updated and pay attention to
> keep your credentials safe/secret. I don't see how Github would prevent
> such an incident any better.

That is making an assumption that the people running the php git server were 
incompetent, which is not something I am willing to do at this point.

-- 
But I been sane a long while now, and change is good.

___
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"

Lessons from the PHP git repo "hack"

[@lbutlr]

As you may know, PHP has decided to move their repo to GitHub after an 
unauthorized "hack" was committed to PHP.

I say "hack" because it appears the code was intentionally obvious and went to 
some lengths to draw attention to itself, so it appears someone did this to 
highlight issues with the private git repo rather than a real attempt to hack. 
These changes were made under authorized accounts despite a 2FA system and it's 
unclear at this point how access was gained.

The current Gihub, which was a mirror only, will be the primary repo going 
forward and the php git server will be retired.

Which brings me to the reason for this post, as it seems that the ports 
collection of FreeBSD 13.x will be in the same position, running a private git 
server network and using GitHub as a mirror and I wonder if some lessons from 
php's experience with this should be considered for this setup before it's 
implemented.

I'm not linking to stories about this because all the ones I can find are 
clickbait frothing panic-inducing nonsense rather than looking at what actually 
happened.

Maybe Krebs will post something soon.

-- 
Turning and turning in the widening gyre
The falcon cannot hear the falconer;

___
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: Proposed ports git transition schedule

[@lbutlr]

On 27 Mar 2021, at 08:20, Felix Palmen  wrote:
> I'm talking about net/gitup, which is a little C program with
> *no* dependencies and definitely no python involved. If you don't have
> it in your ports tree, upgrade your ports tree.

Just for clarity sakes, running gitup ports wight now would replace running 
portsnap?

But we should update it to point to a different server at some point in the 
future?

Would I be safe in removing the stable and current blocks from the gitup.conf 
file since I will never use those?

Might I suggest that -v should mean -v 1 and -vv should mean -v 2? As it is, -v 
means -v 0 and that seems odd?

There's no cron flag, so does this mean we do not need to be concerned with 
when the process runs? Is it safe to run it more than once a day? I mean, I 
doubt GitHub cares at this point, but looking forward…

-- 
A bad day using a Mac is better than a good day using Windows

___
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: Port: astro/sunclock: Malaysia is in the wrong time zone

[@lbutlr]

On 20 Mar 2021, at 21:31, Erich Dollansky  
wrote:
> I just noticed that Malaysia is in the same time zone as Jawa
> (Indonesia) and Thailand.  Wikipedia says for Malaysia UTC+8 and for
> Jawa and Thailand UTC + 7. 

The time zone amp around Malaysia is very odd, but it appears to NOT share the 
same time zone as Thailand at all, but shares a time with China dn the 
Philippines.

Thailand is +7, Malaysia, Perth, and China are +8, Japan and the Koreas are +9


 (3MB, slow connection)

The only thing unaccounted on that map is the cluster fun that is Antarctica, 
but otoh, it's Antarctica.



-- 
"He had delusions of adequacy." - Walter Kerr

___
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 with some gnustep ports after upgrade from 12.1 to 12.2

[@lbutlr]

On 12 Mar 2021, at 21:32, Edwin Ancaer  wrote:
> $ sudo pkg install gnumail
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up to date.
> All repositories are up to date.
> pkg: No packages available to install matching 'gnumail' have been found in
> the repositories
> 
> Out of curiosity, I tried to reinstal anotrher package, gorm, which worked
> fine.
> 
> Now I wonder, is there a problem with those packages (I did pkg update -f
> several times), or is the problem local, at my computer.

I think you will have to build gnumail out of /usr/ports/mail/gnumail as it 
does not appear to be in pkg in 12.2.


-- 
Latet anguis in herba.

___
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: editors/libreoffice fails to build after misc/box2d update

[@lbutlr]

On 08 Mar 2021, at 01:49, Serpent7776  wrote:
> On Mon, 8 Mar 2021 14:44:29 +1300
> Jonathan Chen  wrote:
> 
>> ===>   libreoffice-7.1.0.3_2 depends on shared library: libBox2D.so - not
>> found ===>   Installing existing package /packages/All/Box2D-2.4.1.txz  
>> Installing Box2D-2.4.1...
>> Extracting Box2D-2.4.1: .. done
>> ===>   libreoffice-7.1.0.3_2 depends on shared library: libBox2D.so - not
>> found *** Error code 1
> 
> Maybe that's a stupid question, but why does libreoffice depend on a game
> physics engine?

Purely a WAG, but HTML rendering? Also, probably animation effects in documents?


-- 
"Are you pondering what I'm pondering?"
"Methinks so, Brain, verily, but dost thou think Pete Rose by any
other name would still smell as sweaty?"

___
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: When did pkg(8) drop support for 12-STABLE?

[@lbutlr]

On 23 Feb 2021, at 16:31, Chris  wrote:
> It was from a 12-STABLE usb stick (probably 12.1). Is there no way forward, 
> save
> building up to 12.2?

It sounds like the version you want is -RELEASE, not -STABLE.

Think of -STABLE as "We are still working on this, but we THINK it's stable" as 
opposed to RELEASE "this is ready for general release."

Matthius included the steps needed to get to the current supported version.

-- 
I gotta straighten my face This mellow-thighed chick just put my
spine out of place

___
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: When did pkg(8) drop support for 12-STABLE?

[@lbutlr]

On 23 Feb 2021, at 13:26, Chris  wrote:
> OK On a virgin 12 stable install.

The current release is 12.2-RELEASE. 12.0-RELEASE was EOLed last February. I am 
not sure what build you mean by "12-STABLE"

Are you on the http://lists.freebsd.org/mailman/listinfo/freebsd-stable mailing 
list?


-- 
'Why?' he [Rincewind] said. The world is going to end. 'What, again?'

___
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: My dumper failure

[@lbutlr]

On 27 Jan 2021, at 08:08, @lbutlr  wrote:
> # uname -rs
> FreeBSD 12.2-RELEASE-p1

I finally had some down time, so I did a postmaster -rR databases/mydumper

This resintalled 86 ports and then still failed to complete mydumper. Here is 
more of the error

FAILED: CMakeFiles/myloader.dir/connection.c.o
/usr/bin/cc  -I/usr/local/include/mysql -I/usr/local/include/glib-2.0 
-I/usr/local/lib/glib-2.0/include -I/usr/local/include -Wall 
-Wno-deprecated-declarations -Wunused -Wwrite-strings -Wno-strict-aliasing 
-Wextra -Wshadow  -O3 -g -I/usr/local/include/mysql 
-I/usr/local/include/mysql/mysql -O2 -pipe  -fstack-protector-strong 
-fno-strict-aliasing -MD -MT CMakeFiles/myloader.dir/connection.c.o -MF 
CMakeFiles/myloader.dir/connection.c.o.d -o 
CMakeFiles/myloader.dir/connection.c.o -c connection.c
connection.c:47:9: error: use of undeclared identifier 'SSL_MODE_REQUIRED'
i = SSL_MODE_REQUIRED;
^
connection.c:49:9: error: use of undeclared identifier 'SSL_MODE_DISABLED'
i = SSL_MODE_DISABLED;
^
connection.c:53:23: error: use of undeclared identifier 'MYSQL_OPT_SSL_MODE'
  mysql_options(conn, MYSQL_OPT_SSL_MODE, );
  ^
3 errors generated.
[3/10] /usr/bin/cc  -I/usr/local/include/mysql -I/usr/local/include/glib-2.0 
-I/usr/local/lib/glib-2.0/include -I/usr/local/include -Wall 
-Wno-deprecated-declarations -Wunused -Wwrite-strings -Wno-strict-aliasing 
-Wextra -Wshadow  -O3 -g -I/usr/local/include/mysql 
-I/usr/local/include/mysql/mysql -O2 -pipe  -fstack-protector-strong 
-fno-strict-aliasing -MD -MT CMakeFiles/mydumper.dir/server_detect.c.o -MF 
CMakeFiles/mydumper.dir/server_detect.c.o.d -o 
CMakeFiles/mydumper.dir/server_detect.c.o -c server_detect.c
[4/10] /usr/bin/cc  -I/usr/local/include/mysql -I/usr/local/include/glib-2.0 
-I/usr/local/lib/glib-2.0/include -I/usr/local/include -Wall 
-Wno-deprecated-declarations -Wunused -Wwrite-strings -Wno-strict-aliasing 
-Wextra -Wshadow  -O3 -g -I/usr/local/include/mysql 
-I/usr/local/include/mysql/mysql -O2 -pipe  -fstack-protector-strong 
-fno-strict-aliasing -MD -MT CMakeFiles/myloader.dir/myloader.c.o -MF 
CMakeFiles/myloader.dir/myloader.c.o.d -o CMakeFiles/myloader.dir/myloader.c.o 
-c myloader.c
[5/10] /usr/bin/cc  -I/usr/local/include/mysql -I/usr/local/include/glib-2.0 
-I/usr/local/lib/glib-2.0/include -I/usr/local/include -Wall 
-Wno-deprecated-declarations -Wunused -Wwrite-strings -Wno-strict-aliasing 
-Wextra -Wshadow  -O3 -g -I/usr/local/include/mysql 
-I/usr/local/include/mysql/mysql -O2 -pipe  -fstack-protector-strong 
-fno-strict-aliasing -MD -MT CMakeFiles/mydumper.dir/mydumper.c.o -MF 
CMakeFiles/mydumper.dir/mydumper.c.o.d -o CMakeFiles/mydumper.dir/mydumper.c.o 
-c mydumper.c
ninja: build stopped: subcommand failed.
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make: stopped in /usr/ports/databases/mydumper

-- 
Bishops move diagonally. That's why they often turn up where the
kings don't expect them to be.

___
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"

My dumper failure

[@lbutlr]

# uname -rs
FreeBSD 12.2-RELEASE-p1

Portmaster build of my dumper fails:

[6/10] /usr/bin/cc  -I/usr/local/include/mysql -I/usr/local/include/glib-2.0 
-I/usr/local/lib/glib-2.0/include -I/usr/local/include -Wall 
-Wno-deprecated-declarations -Wunused -Wwrite-strings -Wno-strict-aliasing 
-Wextra -Wshadow  -O3 -g -I/usr/local/include/mysql 
-I/usr/local/include/mysql/mysql -O2 -pipe  -fstack-protector-strong 
-fno-strict-aliasing -MD -MT CMakeFiles/mydumper.dir/mydumper.c.o -MF 
CMakeFiles/mydumper.dir/mydumper.c.o.d -o CMakeFiles/mydumper.dir/mydumper.c.o 
-c mydumper.c
ninja: build stopped: subcommand failed.
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make: stopped in /usr/ports/databases/mydumper

Ports tree updated a few hours ago. This is the only port that shows an update:

# portmaster -L | grep -B1 " New 
===>>> mydumper-0.9.5
===>>> New version available: mydumper-0.10.1

This is not critical, but it is one of the ways I backup MySQL databases.

-- 
Vi Veri Veniversum Vivus Vici

___
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"

Pinentry

[@lbutlr]

I ma trying to figure out why pin entry and pinetnry-tty are installed. If I 
try to remove it, I get a list of post that are to be deleted.

Installed packages to be REMOVED:
gnupg: 2.2.27
gpgme: 1.15.1
mimedefang: 2.83_3
mutt: 2.0.4
pinentry: 1.1.0_7
pinentry-tty: 1.1.0
spamass-milter: 0.4.0_4
spamassassin: 3.4.4
subversion: 1.14.0

I've looked through he config for all of these and not seen anything about PIN 
entry, and am wondering why it would be required to run any of these packages.

I cannot imagine any circumstances in which I would need to enter a PIN on a 
TTY and no one else could possibly do so.

I suspect mutt since it is relatively newly installed, nut I see nothing in the 
config that seems like it wold disable this. (Mutt is used as a convenient way 
to send html formatted mail of some system events), it is not used to access 
mail off the server and is only used by me to access mail on the server.

-- 
"Are you pondering what I'm pondering?"
"Well, I think so, Brain, but first you'd have to take that whole
bridge apart, wouldn't you?"

___
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"

iperf checksums?

[@lbutlr]

When trying to install iperf:

===>>> Waiting on fetch & checksum for benchmarks/iperf <<<===
fetch: https://freefr.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: 
size mismatch: expected 370518, actual 373268
=> Attempting to fetch 
https://jaist.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz
fetch: https://jaist.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: 
size mismatch: expected 370518, actual 373268
=> Attempting to fetch 
https://nchc.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz
fetch: https://nchc.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: 
size mismatch: expected 370518, actual 373268
=> Attempting to fetch 
https://netcologne.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz
fetch: 
https://netcologne.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: size 
mismatch: expected 370518, actual 373268
=> Attempting to fetch 
https://netix.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz
fetch: https://netix.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz: 
size mismatch: expected 370518, actual 373268
=> Attempting to fetch 
https://superb-dca2.dl.sourceforge.net/project/iperf2/iperf-2.0.14a.tar.gz

Over and over with identical numbers on slightly differ source forge servers.

-- 
"Woof bloody woof."

___
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: Bind master error on empty.db

[@lbutlr]

On 30 Oct 2020, at 11:52, Chris  wrote:
> As an aside; why the enormous SPAM header?

My milter was misconfigured (again) to not acknowledge that outbound messages 
were submitted via authenticated submission, so it tagged my mail as being from 
a dynamic address (correct) before passing it along.

I've fix the config (again) and hopefully this time will not accidentally 
revert it.

爛

Removing the entire .../master/ directory has no affect on bind, but the 
package will complain on update.

-- 
"Are you pondering what I'm pondering?"
"Well, I think so, Brain, but it's a miracle that this one grew
back."

___
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: Bind master error on empty.db

[@lbutlr]

On 29 Oct 2020, at 15:37, Tatsuki Makino  wrote:
> Do you use named_chrootdir?

No.

-- 
Ghosts prefer empty bottles that we've all drunk.

___
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"

Bind master error on empty.db

[@lbutlr]

Spam detection software, running on the system "mail.covisp.net",
has identified this incoming email as possible spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
ad...@covisp.net for details.

Content preview:  When updating bind 9.16 I get: pkg-static: file 
'/usr/local/etc/namedb/master/empty.db'
   is missing pkg-static: package creation failed ===>>> Ignore this error [i]
   ===>>> Abort update [a] ===>>> Retry [r]

Content analysis details:   (6.1 points, 5.0 required)

 pts rule name  description
 -- --
-1.9 BAYES_00   BODY: Bayes spam probability is 0 to 1%
[score: 0.]
 1.5 BODY_8BITS BODY: Body includes 8 consecutive 8-bit characters
 3.3 RCVD_IN_PBLRBL: Received via a relay in Spamhaus PBL
[73.14.161.160 listed in zen.spamhaus.org]
 0.0 RCVD_IN_SORBS_DUL  RBL: SORBS: sent directly from dynamic IP
address
[73.14.161.160 listed in dnsbl.sorbs.net]
 1.0 RDNS_DYNAMIC   Delivered to internal network by host with
dynamic-looking rDNS
 0.3 KHOP_HELO_FCRDNS   Relay HELO differs from its IP's reverse DNS
 0.0 HELO_MISC_IP   Looking for more Dynamic IP Relays
 1.9 NO_FM_NAME_IP_HOSTNNo From name + hostname using IP address

BAYES_HT0.000-+--H*Ad:U*freebsd-ports, 0.000-+--grep, 0.000-4--bytes, 
0.001-+--H*Ad:D*freebsd.org, 0.002-1--retry, 0.002-+--usr, 0.002-1--sooner, 
0.002-1--UD:db, 0.003-+--HTo:D*freebsd.org, 0.003-1--abort, 0.004-+--config, 
0.006-+--HTo:U*freebsd-ports, 0.009-+--HTo:D*org, 0.010-+--bind, 
0.015-+--H*x:Apple, 0.016-+--H*UA:Apple, 0.037-+--H*Ad:D*org, 
0.041-+--H*ct:plain, 0.048-+--install, 0.049-3--H*m:kreme, 
0.049-3--H*F:U*kremels, 0.061-+--file, 0.063-2--H*x:2.3654.0.3.2.82, 
0.063-2--H*UA:2.3654.0.3.2.82, 0.089-1--sample, 0.093-4--ignoring, 
0.093-2--H*F:D*kreme.com, 0.116-+--error, 0.124-1--rushed, 0.126-+--etc
BAYES_ST0.987-1--HX-Envelope-From:sk:kremels


--- Begin Message ---
When updating bind 9.16 I get:

pkg-static: file '/usr/local/etc/namedb/master/empty.db' is missing
pkg-static: package creation failed

===>>> Ignore this error  [i]
===>>> Abort update   [a]
===>>> Retry  [r]

===>>> How would you like to proceed? [I]

Ignoring the error caused bind to install but why the error? I have no 
reference to /usr/local/etc/namedb/master/ anywhere in my config.

 # grep -ir master /usr/local/etc/namedb | grep -v sample
 #

Ignoring the error caused a master/empty.db to be created, along with a couple 
of other files.

 # tree master
master
├── empty.db
├── localhost-forward.db
└── localhost-reverse.db

The files are each about 250-300 bytes.

--
'But look,' said Ponder, 'the graveyards are full of people who
rushed in bravely but unwisely.' 'Ook.' 'What did he say?' said
the Bursar. 'I think he said, "Sooner or later the graveyards are
full of everybody".'

--- End Message ---
___
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

[@lbutlr]

On 05 Aug 2020, at 04:59, Hans Petter Selasky  wrote:
> 2) Should portsnap be a wrapper for GIT/SVN whatever is used?

Yes, this seems like a very obvious thing to do as it will minimize disruption 
for the most users.

Not everyone has any use for git our any need to learn git syntax. A "portsnap" 
wrapper that duplicates existing functionality should be part of this change.



-- 
99 percent of lawyers give the rest a bad name.

___
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 and less

[@lbutlr]

On 31 Jul 2020, at 14:24, @lbutlr  wrote:
> Is there anyway to change this behavior so that less is called with -E / 
> --QUIT-AT_EOF? 

Never mind, I dididn’t think of it as a user-level issue.

export MANPAGER='less -s -X -F'
export PAGER='less -s -X -F'



-- 
Against stupidity the gods themselves contend in vain.

___
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 and less

[@lbutlr]

When postmaster displays the package messages after installing, it calls less, 
which forces you to hit 'q' to exit, and when you quit less, it clear the 
buffer on the screen and returns you to the display of the compile process.

Is there anyway to change this behavior so that less is called with -E / 
--QUIT-AT_EOF? Or can I just tell postmaster to cat this files so they appear 
in my terminals scroll back no matter what?

(I think the discarding that text that is paged by less is a terminal emulator 
or tmux setting, but haven’t looked into that.)




-- 
'Never say die, master. That's our motto, eh?' I CAN'T SAY IT'S EVER
REALLY BEEN MINE. --Hogfather

___
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: Changing what version Poudriere builds

[@lbutlr]

On 07 Jul 2020, at 17:37, @lbutlr  wrote:
> Poudriere is trying to built/update bind9.14 instead of bind9.16, which is 
> current. How do I tell it to get bind 9.16 instead?

Never mind, the wrong ports tree was updated.

Or at least no the one I expected.





-- 
and I swear it happened just like this: / a sigh, a cry, a hungry
kiss, the Gates of Love they budged an inch / I can't say much
has happened since / but CLOSING TIME

___
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"

Changing what version Poudriere builds

[@lbutlr]

Poudriere is trying to built/update bind9.14 instead of bind9.16, which is 
current. How do I tell it to get bind 9.16 instead?

(Yes, the ports tree is updated).



-- 
"He is not only dull himself; he is the cause of dullness in others."
Samuel Johnson

___
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: Updating py27-* ports

[@lbutlr]

On 04 Jul 2020, at 08:30, Carmel  wrote:
> I see that you are putting it all on one line. That is probably easier.
> I like the separate entries technique simply because I find it easier
> to read myself or quickly comment out an entry.

I agree that separate lines have advantages. When making changes I tend to go 
to multiple lines, then collapse back to a single line when I have a stable set.

> What I have never been able to get a definitive answer to is exactly
> what the "+" does or if it is even needed, I have seen
> 'default_versions" both with and without it.

+= adds the option, = set it.

DEFAULT_VERSIONS=foo bar sing
$DEFAULT_VERSIONS foo bar sing

DEFAULT_VERSIONS+=max
$DEFAULT_VERSIONS foo bar sing max

DEFAULT_VERSIONS=sam
$DEFAULT_VERSIONS sam



-- 
Please to meet you, Rose. Now run for your life!

___
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: Reminder: freedb.org (CDDB) has shut down

[@lbutlr]

On 01 Jul 2020, at 09:14, Christian Weisgerber  wrote:
> (On OpenBSD I extracted all ports and grepped over the sources, which
> revealed some 35 affected ports.
> https://marc.info/?l=openbsd-ports=159346807907595=2
> I don't have the resources to do this on FreeBSD.)

I did a quick and dirty check on FreeBSD 12.1 x86

grep -ir CDDB /usr/ports/INDEX-12 | wc -l
 154 

(133 of them are libcddb)

HTH?


-- 
"Are you pondering what I'm pondering?"
"Sure, Brain, but how are we going to find chapsour size?"

___
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 port can't build (again)

[@lbutlr]

On 16 Jun 2020, at 14:55, Larry Rosenman  wrote:
> sysutils/lsof ABSOLUTELY REQUIRES /usr/src to be able to build.

Is there a list of the files in src that it requires?

Can I delete the rest?

(Tranferring 1.5GB is far less of an issue than keeping 1.5GB around).

-- 
Get in there you big furry oaf! I don't care what you smell!
___
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 port can't build (again)

[@lbutlr]

> On 17 Jun 2020, at 07:35, Matthew Seaman  wrote:
> 
> On 17/06/2020 04:23, @lbutlr wrote:
>> Thank you, cleared /usr/src and running the svn checkout with that
>> URL now. It's still well over a gig so it will be a few minutes
>> before trying to build lsof again.
> Alas, it is a bit late now, but next time you need to switch branches
> like this, use `svn switch ^/releng/12.1` which will save you many
> gigabytes of unnecessary network traffic.

Well, it was about 1.5GB, and on a gigabit connection it only took time because 
it downloaded each file instead of a package/archive.

But I am unlikely to switch branches (and confused as to why the non-RELEASE 
13.0 was the default) without updating the entire OS.

-- 
Think of how stupid the average person is, and realize half of them are 
stupider than that.

___
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 port can't build (again)

[@lbutlr]

On 16 Jun 2020, at 21:14, George Mitchell  wrote:
> On 2020-06-16 23:12, George Mitchell wrote:
>> On 2020-06-16 23:10, @lbutlr wrote:
>>> [...]
>>> Needless to say, I was expecting that checkout would give me 12.1, but I 
>>> don't see how to get that.


> Pardon the typo:
> 
> https://svn.freebsd.org/base/releng/12.1/

Thank you, cleared /usr/src and running the svn checkout with that URL now. 
It's still well over a gig so it will be a few minutes before trying to build 
lsof again.

Yep. That solved the problem, and lsof built.

Thanks again!



-- 
Beware of the Leopard!


___
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 port can't build (again)

[@lbutlr]

On 16 Jun 2020, at 06:40, Mike Bristow  wrote:
> What is the output of "egrep '^(TYPE|REVISION|BRANCH)' 
> /usr/src/sys/conf/newvers.sh" ?

Well, this seems like it might be bad:

# egrep '^(TYPE|REVISION|BRANCH)' /usr/src/sys/conf/newvers.sh
TYPE="FreeBSD"
REVISION="13.0"
BRANCH=${BRANCH_OVERRIDE:-CURRENT}

> How do you maintain the src tree on your machine?

svn checkout https://svn.FreeBSD.org/base/head /usr/src  

And

cd /usr/src
make update SVN_UPDATE=yes

Needless to say, I was expecting that checkout would give me 12.1, but I don't 
see how to get that.




-- 
'You make us want what we can't have and what you give us is worth
nothing and what you take is everything and all there is left for
us is the cold hillside, and emptiness, and the laughter of the
elves.'


___
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"

Lsof port can't build (again)

[@lbutlr]

When trying to update lsof on FreeBSD 12.1-RELEASE-p5 GENERIC i386 I get the 
following fatal error:

/usr/src/sys/sys/pcpu.h:224:10: fatal error: 'machine/pcpu_aux.h' file not found
#include 
 ^~~~

After doing some searching $(find / -type d -name machine), I found a similarly 
named file:

# ll /usr/include/machine/pcpu.h
16 -r--r--r--  1 root  wheel   8.0K Oct 31  2019 /usr/include/machine/pcpu.h


-- 
Let him who desires peace, prepare for war.


___
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"

Json-c, bind, and updating

[@lbutlr]

This has happened in the past, but it happened again this weekend when an 
update to ;ibjson-c did not update bind, rendering bind unable to load 
libjson-c.so.4 because it had been replaced with libjson-c.so.5.

In a rush I simply linked libjson-c.so.4 -> libjson-c.so.5 and all is happy 
AFAICT. Well, at least functional.

There is no update listed for bind because, evidently, "The dns/bind914 port 
moved to dns/bind916 Reason: Has expired: End of life, please migrate to a 
newer version of BIND9" is not an "update". I mean, yes, this is correct, but 
it seems less than helpful. And yet, if I try to install bund914, it will 
install 916, so there is an update.

Especially when Bind-tools is happily updated to 9.16

The following actions were performed:
Re-installation of bind-tools-9.16.3_1
Upgrade of bind914-9.14.11 to bind916-9.16.3_2

Sure would have been nice if this had shown up as an available update.


-- 
he'd moved like music, like someone dancing to a rhythm inside his
head. And his face for a moment in the moonlight was the skull of
an angel…


___
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: mail/mailman v3?

[@lbutlr]

>> AIUI you can move your entire archive to the new system.
> 
> There are many thousand links to the freebsd pipermail archives,
> and invalidating all those links sounds like a serious loss of institutional
> memory.

As I said in the pat of my message you snipped, you do not have to remove your 
pipermail archives.

Here is is again:

You can even keep pipermail for your old archive. You just can’t use pipermail 
with the new system.



-- 
Looking into Granny's eyes was like looking into a mirror. What you
saw looking back at you was yourself, and there was no hiding
place.


___
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: mail/mailman v3?

[@lbutlr]

On 28 Apr 2020, at 14:00, Chris  wrote:
> as at *least* it completely abandons the previous archive system.

Pipermail was… lacking. It looked 20 years old (because it was).

> Making your previous archive, an archive of an archive.

AIUI you can move your entire archive to the new system. You can even keep 
pipermail for your old archive. You just can’t use pipermail with the new 
system.




-- 
"Master, what is the difference between a humanistic, monastic system
of belief in which wisdom is sought by means of an apparently
nonsensical system of questions and answers, and a lot of mystic
gibberish made up on the spur of the moment?" Wen considered this
for some time, and a last said: "A fish!”


___
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: mail/mailman v3?

[@lbutlr]

On 28 Apr 2020, at 09:33, Matthias Andree  wrote:
> Leaving Python 3.x compatibility aside,

But that is the main issue. Python 2.7 is dead. Well, fine, it’s not quite dead 
yet, but it is also not feeling any better.

(I ran mailman lists for many years, but never made the move to mailman 3 and 
the lists petered out several years back, so I have no horse in this hunt (or 
is it dog in this race? :)).



-- 
HILLBILLIES ARE PEOPLE TOO Bart chalkboard Ep. AABF11


___
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

[@lbutlr]

On 27 Apr 2020, at 17:32, ajtiM via freebsd-ports  
wrote:
>  qt5-webengine

There is py-qt5-webengine which seems to want py37





-- 
"Remember -- that which does not kill us can only make us stronger."
"And that which *does* kill us leaves us *dead*!”


___
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: Linux-foldingathome

[@lbutlr]

On 07 Apr 2020, at 06:36, Yuri Pankov  wrote:
> @lbutlr wrote:

>> # service fahclient start
>> Starting fahclient.
>> 13:33:52:WARNING:Exception: Failed to open '/proc/bus/pci/devices': Failed 
>> to open '/proc/bus/pci/devices': No such file or directory: No such file or 
>> directory
>> 13:33:52:ERROR:Exception: Could not read link /proc/self/exe

> It is looking for /compat/linux/proc -- if it isn't mounted and you aren't on 
> recentish -current

12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC  amd64

Isn’t recent enough, I guess?

> where all required mounts are done by rc script, you should follow the 
> pkg-message for linux_base-c7 port.

Thank you, that solved the issue and the client is running now.



-- 
Support bacteria - they're the only culture some people have.


___
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"

Linux-foldingathome

[@lbutlr]

Has anyone had any experience with installing the port 
biology/linux-foldingathome?

After installing it and editing the configuration file I try to start it and 
get the following:

# service fahclient start
Starting fahclient.
13:33:52:WARNING:Exception: Failed to open '/proc/bus/pci/devices': Failed to 
open '/proc/bus/pci/devices': No such file or directory: No such file or 
directory
13:33:52:ERROR:Exception: Could not read link /proc/self/exe
/usr/local/etc/rc.d/fahclient: WARNING: failed to start fahclient

/proc/ is empty.

There were no errors when installing the port.

# kldstat
Id Refs AddressSize Name
 1   57 0x8020  2448d90 kernel
 21 0x82649000   3a99a8 zfs.ko
 32 0x829f3000 a5b8 opensolaris.ko
 41 0x82f11000 4260 ng_ubt.ko
 56 0x82f16000 9e30 netgraph.ko
 62 0x82f2 91b8 ng_hci.ko
 73 0x82f2a000  9c0 ng_bluetooth.ko
 81 0x82f2b000 cad0 ng_l2cap.ko
 91 0x82f380001ba00 ng_btsocket.ko
101 0x82f54000 21c0 ng_socket.ko
111 0x82f57000  acf mac_ntpd.ko
121 0x82f58000 18a0 uhid.ko
131 0x82f5a000 1aa0 wmt.ko
141 0x82f5c000 2928 ums.ko
151 0x82f5f00035b20 linux64.ko
163 0x82f95000 3178 linux_common.ko
171 0x82f99000 494c linprocfs.ko
181 0x82f9e000 1eae linsysfs.ko


-- 
Traveling through hyperspace ain't like dusting crops, boy.


___
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

[@lbutlr]

On 20 Mar 2020, at 15:30, @lbutlr  wrote:
> PORTS+MODULE=sysutils/lsof

Oops.



-- 
Say, give it up, give it up, television's taking its toll That's
enough, that's enough, gimme the remote control I've been nice,
I've been good, please don't do this to me Turn it off, turn it
off, I don't want to have to see


___
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

[@lbutlr]

On 20 Mar 2020, at 14:10, Robert Huff  wrote:
> 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.

Why was this changed (I did not install the source and my /usr/src/ directory 
is empty and has been since I moved to 12.1)

>   My solution has been to add "sysutils/lsof" to PORTS_MODULES in
> /etc/make.conf.

How does this help?

# cat /etc/make.conf
DEFAULT_VERSIONS+=ssl=openssl apache=2.4 php=7.2 perl5=5.30 mysql=10.3m 
PORTS+MODULE=sysutils/lsof

Building lsof still fails

pkg install works.



-- 
Sarah, age 18, says "man, once you go Crayola you can't go back.”


___
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"

lsof marked ignored

[@lbutlr]

Got this when trying tu update lsof:

===>>> lsof-4.93.2_9,8
===>>> New version available: lsof-4.93.2_10,8

===>>> Currently installed version: lsof-4.93.2_9,8
===>>> Port directory: /usr/ports/sysutils/lsof

===>>> This port is marked IGNORE
===>>> requires kernel sources

Don’t see anything in MOVED or UPDATIN about changes to lsof?

Since I built the previous version should I just comment the IGNORE line in the 
makefile and not worry about why I 
 got this error (didn’t get it before).



-- 
'Things either exist or they don't,' said Jeremy. 'I am very clear
about that. I have medicine.' --The Thief of Time


___
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: Aria2 and magnets

[@lbutlr]

On 05 Mar 2020, at 06:54, @lbutlr  wrote:
> I’ve tried the magnet (and other magnets) several times. The first time I 
> tried a magnet link there was an error, but that is sort of documented for 
> araia2 and subsequent attempts do not generate an error about DHT, but they 
> do not download.

Tried it just before posting and it failed again (left it for 5 minutes with 
zero progress).. Did it again just now and it worked fine. 15th time’s the 
charm?

 *** Download Progress Summary as of Thu Mar  5 06:51:28 2020 ***   
  
[#af2955 123MiB/0.9GiB(13%) CN:12 SD:7 DL:7.2MiB ETA:1m54s]
FILE: /root/FreeBSD-12.1-RELEASE-amd64-memstick.img


___
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: Aria2 and magnets

[@lbutlr]

> On 05 Mar 2020, at 06:08, RW via freebsd-ports  
> wrote:
> 
> On Wed, 4 Mar 2020 17:19:06 -0700
> @lbutlr wrote:
> 
>> Brand new install of aria2 and I tried to grab the FreBSD 12.1 amd64
>> image via a magnet link:
> ...
>> After about 30 minutes the only thing I get is updates showing 0
>> Bytes downloaded.
> ...
>> 
>> Downloading a torrent file, in this case Ubuntu server, works fine:
> 
> Perhaps DHT is blocked in your firewall.

Nope, though I guess it could be on that specific machine, but I don’t think so.

> It's also worth rechecking the
> magnet link in case the Ubuntu download bootstrapped DHT.

I’ve tried the magnet (and other magnets) several times. The first time I tried 
a magnet link there was an error, but that is sort of documented for araia2 and 
subsequent attempts do not generate an error about DHT, but they do not 
download.
> 

___
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"

Aria2 and magnets

[@lbutlr]

Brand new install of aria2 and I tried to grab the FreBSD 12.1 amd64 image via 
a magnet link:

# aria2c 
'magnet:?xt=urn:btih:da22f9b3339bf44c0a2e33626658873253b67f8d=FreeBSD-12.1-RELEASE-amd64-memstick.img’

After about 30 minutes the only thing I get is updates showing 0 Bytes 
downloaded.

 *** Download Progress Summary as of Wed Mar  4 17:06:48 2020 ***   
  
==
[#4209c2 0B/0B CN:0 SD:0 DL:0B]
FILE: [MEMORY][METADATA]FreeBSD-12.1-RELEASE-amd64-memstick.img
--

[#4209c2 0B/0B CN:0 SD:0 DL:0B]  

Downloading a torrent file, in this case Ubuntu server, works fine:

aria2c 
"http://releases.ubuntu.com/18.04/ubuntu-18.04.4-live-server-amd64.iso.torrent?_ga=2.195131947.685826887.1583367284-2079251896.1583367284”

Download Results:
gid   |stat|avg speed  |path/URI
==++===+===
5c5de9|OK  |   309KiB/s|/root/ubuntu-18.04.4-live-server-amd64.iso.torrent
5b7f37|OK  |36MiB/s|/root/ubuntu-18.04.4-live-server-amd64.iso

With a successful download in a few seconds.

I mean, I can use torrent files, but I prefer dealing with magnets and some 
files (like the FreeBSD images) don’t have .torrents.

___
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: Good CLI BitTorrent client?

[@lbutlr]

On 04 Mar 2020, at 08:44, nonamel...@ukr.net wrote:
> There is also rtorrent, but I recommend aria2.

That has a shockingly small number of deps, definitely giving that a try.

Thanks everyone!

___
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 CLI BitTorrent client?

[@lbutlr]

Sice people are talking about GUI botttorrent clients, are there decent ones 
that are CLI?

___
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: Starting with poudriere

[@lbutlr]

On 16 Feb 2020, at 02:02, Kurt Jaeger  wrote:
> /usr/local/etc/poudriere.d/121-default-make.conf

And this conf file applies when you use the jail named exactly “121-default”? 
So for my jail named 121x64 the conf file would be 

"121x64-make.conf"

And for 113x86

"113x86-make.conf"

Ok, this is starting to make some sense. Now I just need to get a list of the 
ports pon the 11.3 system currently in the form / so I can 
at least set that up with the current ports.

Not sure I quite get how the Webserver lets your other machines get the 
packages in such a way that they can be dropped in place, but I don’t need to 
do that right now anyway (that will be a task for when I have migrated that 
machine to 12.1 amd64 anyway), hopefully in the next month.


-- 
"He has no enemies, but is intensely disliked by his friends.." Oscar
Wilde

___
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: Starting with poudriere

[@lbutlr]

On 15 Feb 2020, at 21:43, Dan McGrath  wrote:
> You would run "poudriere bulk", then sit back sipping coffee while it
> churns through all of the packages.

Hang on a second, so the intended use for poudriere is to build ALL packages?

Right now I have two jails setup, one for 12.1 amd64 and one for 11.3 i386. 
That seems like a *LOT* of compiling/building.

And once I’ve build, say, ImageMagick or postfix/doveco/.=mariadb/apache/etc 
how do I then deploy them to the 11.3 server (as in, a different machine)?


-- 
Cause love's such an old fashioned word
And love dares you to care for the people on the
Edge of the night, and love dares you to change
Our way of caring about ourselves, 
This is our last dance This is ourselves.
Under Pressure.
___
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: Starting with poudriere

[@lbutlr]

On 15 Feb 2020, at 16:32, @lbutlr  wrote:
> Sorry for the rather basic questions.

Thanks everyone for your comments. One more dumb question I can’t find the 
answer to.

Let’s say I want to build and install a single port via poudrier. For the same 
of argument some port that has configuration options I want to change.

I have the ports tree setup, have my jail setup, and I want to build it.

And then I want to deploy it to the target machine once it’s built.

Or I want to deploy to to the local machine.

Let’s say, for fun, it’s something like ImageMafick that has a lot that goes 
with it.

Am I writing a config file for this every port I want to build?


-- 
The fact is that camels are far more intelligent than dolphins.
Footnote: Never trust a species that grins all the time. It's up
to something. —Pyramids


___
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"

Starting with poudriere

[@lbutlr]

I’ve setup a new FreeBSD 12.1 system and am going to give poudriere a whirl on 
it.

The machine is currently setup as a two drive zfs mirror and I have used pkg to 
install a few basic things (sudo, zsh, poudriere itself, etc).

I am reading through 

 and I have some questions.

First, the example of says that if we don’t change any options, the defaults 
will be used. OK, but it makes no mention on how we might change or set 
options? Is this simply talking about the build options panels that sometimes 
come up (Build examples, support ssl, use sqlite or MySQL, etc), and when I 
first go to build a “persistent list” those option screens will come up and I 
can make changes and they will be saved? Or is there something else that I need 
to do?

Second, let's say that I want to setup the machine to build postfix, dovecot, 
apache, pigeonhole, marisadb, postfixadmin, rpoundcube, and horde all in on 
“persistent list” since all of these pacajkges are need to do mail and webmail, 
do I simply list the packages in a single file the way the page lists 
www/firefox?

Once I have poudriere setup and running and I’m comfortable with it, do I need 
to do anything to have it “take over” sudo and anything else that I installed 
via pkg?

Sorry for the rather basic questions.


-- 
"Are you pondering what I'm pondering?"
"I think so, Brain, but why would anyone want to see Snow White and
the Seven Samurai?”


___
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: OpenSSL multiple names?

[@lbutlr]

On 07 Feb 2020, at 11:06, @lbutlr  wrote:
>  I updated openssl in January, and as I said it has been recompiled several 
> times 

To be clear, I did everything that UPDATING 20200101 mentions, including 
reinstalling all ports, changing make.conf, etc.

But all along, the system has reported that the version is openssl111-1.1.1, 
until 05 Feb. BTW, there is no new version of openssl listed in Postmaster and 
the distill in security/openssl says the date is Wed Sep 11 02:04:23 MDT 2019.

 root # cat security/openssl/distinfo  
   
[11:14] [/usr/ports] 
TIMESTAMP = 1568189063
SHA256 (openssl-1.1.1d.tar.gz) = 
1e3a91bc1f9dfce01af26026f856e064eab4c8ee0a8f457b5ae30b40b8b711f2
SIZE (openssl-1.1.1d.tar.gz) = 8845861



-- 
When this kiss is over it will start again But not be any different
could be exactly the same It's hard to imagine that nothing at
all Could be so exciting, could be this much fun


___
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: OpenSSL multiple names?

[@lbutlr]

On 06 Feb 2020, at 17:55, Koichiro Iwao  wrote:
> I think UPDATING 20200101 should help you.

Nope, that doesn’t help me. I updated openssl in January, and as I said it has 
been recompiled several times (well, at least six) since then as I have updated 
ports. This behavior of confusing the two forms “openssl-1.1.1d,1” and 
“openssl111-1.1.1f” is new.

> On Wed, Feb 05, 2020 at 06:41:19PM -0700, @lbutlr wrote:
>> When trying to port upgrade mariadb it reinstalled openssl (just about 
>> everything for the last month has reinstalled openssl)
>> 
>> I get this after a successful build
>> 
>> ===>   Registering installation for openssl-1.1.1d,1
>> Installing openssl-1.1.1d,1...
>> pkg-static: openssl-1.1.1d,1 conflicts with openssl111-1.1.1d
>> 
>> There is /usr/ports/security/openssl
>> 
>> So why are there two different formats on the port name and how do I fix 
>> this.


-- 
It was intended that when Newspeak had been adopted once and for all
and Oldspeak forgotten, a heretical thought...should be literally
unthinkable, at least so far as thought is dependent on words.


___
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"

OpenSSL multiple names?

[@lbutlr]

When trying to port upgrade mariadb it reinstalled openssl (just about 
everything for the last month has reinstalled openssl)

I get this after a successful build

===>   Registering installation for openssl-1.1.1d,1
Installing openssl-1.1.1d,1...
pkg-static: openssl-1.1.1d,1 conflicts with openssl111-1.1.1d

There is /usr/ports/security/openssl

So why are there two different formats on the port name and how do I fix this?


___
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 failing

[@lbutlr]

On 01 Jan 2020, at 16:57, Adam Weinberger  wrote:
> Ok, let’s stop there. Nobody is going to get fired, and insulting

What?

No, seriously, what?


___
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 failing

[@lbutlr]

On 01 Jan 2020, at 15:28, Kurt Jaeger  wrote:
>> If FreeBSD is going to REQUIRE poudriere, then go ahead and do
>> so. If not, then the other packages managers and the ports tree
>> itself have to work without screwing the admin, failing to build
>> for inexplicable reasons, inputting a dependency that breaks other
>> packages, or my favorite, failing to update dependencies.
> 
> If we'd remove portmaster, we'd loose a relevant part of our
> user-base, that's why is has not been removed. This caused
> other issues, as you are well aware.

If you are concerned about losing users without postmaster then fix postmaster. 
Leaving a port manage that is “broken” is not going to do anything but hurt 
everyone.


> The open source community (and FreeBSD) really has problems with
> the velocity of the software involved -- and can barely keep up.
> 
> So it's not that easy.

Bit they are perfectly happy to drop support when the replacement packages are 
still not up to snuff.

>>> You are right that there wasn't a warning, and that was a major
>>> mistake that should not have happened. security/openssl and
>>> security/openssl111 should have contained messages about this switch.
>> 
>> Since openssl updated about a week ago, this oversight falls into the class 
>> that I would call ???inexcusable???. If I did this on a job I would 
>> (rightly) be immediately fired.
>> 
>> I would fire me if I did something like this.

> If we fired every volunteer when some mishap has happened, we
> would run of of volunteers very fast.

This was the responsibility of a single volunteer? Removing openssl without 
warning wasn’t something that was discussed over the last six months?




-- 
Lead me not into temptation, I can find the way.

___
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 failing

[@lbutlr]

On 01 Jan 2020, at 14:18, Adam Weinberger  wrote
> This is why we practically beg people to use poudriere. 

If FreeBSD is going to REQUIRE poudriere, then go ahead and do so. If not, then 
the other packages managers and the ports tree itself have to work without 
screwing the admin, failing to build for inexplicable reasons, inputting a 
dependency that breaks other packages, or my favorite, failing to update 
dependencies.

> I've mentioned this to you before, lbutlr, because you post about
> encountering these snags quite regularly, and your (quite warranted)
> frustration is apparent. I really do think that your FreeBSD life will
> be simpler if you switch from portmaster to poudriere.

It is not that simple, of course. This will take quite a lot of work, and a lot 
of time, for something that I deal with a handful of times a year. This means 
that for the foreseeable future, I would be starting over basically every time 
there is some issue.

> They are simply an inevitable consequence of using a very old and broken tool

If the tool is broken, remove it.

> You are right that there wasn't a warning, and that was a major
> mistake that should not have happened. security/openssl and
> security/openssl111 should have contained messages about this switch.

Since openssl updated about a week ago, this oversight falls into the class 
that I would call “inexcusable”. If I did this on a job I would (rightly) be 
immediately fired.

I would fire me if I did something like this.



-- 
In the 60's, people took acid to make the world appear weird. Now the
world is weird and people take Prozac to make it appear normal.

___
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 failing

[@lbutlr]

On 01 Jan 2020, at 13:46, Franco Fichtner  wrote:
> 
> 
> 
>> On 1. Jan 2020, at 9:42 PM, @lbutlr  wrote:
>> 
>> On 01 Jan 2020, at 13:40, Franco Fichtner  wrote:
>>> security/openssl was removed before, now security/openssl111 has become 
>>> security/openssl.
>> 
>> Ugh.
>> 
>>> A bit too eager for my taste, but that's why we all have private trees, 
>>> don't we.  ;)
>> 
>> This is going to go poorly, if previous attempts to update to 1.1 are any 
>> indication.
> 
> With PHP 5.6 axed prematurely a while back I am interested to see OpenSSL 
> 1.0.2
> phased out now with a number of ports still not supporting 1.1.1 and seeing 
> them
> marked as broken sooner or later.

Well, at this point I cannot install openssl111 without deinstalling openssl, 
which I cannot deinstall since it is gone from ports.

Looks like I have to remove openssl, which … I mean, seriously, this seems 
pretty hostile.

Name   : openssl
Version: 1.0.2u,1
Installed on   : Sun Dec 22 08:13:27 2019 MST

There was nothing at all on the 22nd about “WARNING THIS WILL BREAK EVERYTHING 
IN A WEEK” which to mean seems like it should have been made super obvious.



-- 
There are 10 types of people in the world: Those who understand
binary and those who don’t.

___
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 failing

[@lbutlr]

On 01 Jan 2020, at 13:40, Franco Fichtner  wrote:
> security/openssl111 has become security/openssl.

I have /usr/ports/security/openssl111 and no /usr/ports/security/openssl which 
doesn’t sound like what you said.



-- 
'Pcharn'kov!' Footnote: 'Your feet shall be cut off and be buried
several yards from your body so your ghost won't walk.'
--Interesting Times

___
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 failing

[@lbutlr]

On 01 Jan 2020, at 13:40, Franco Fichtner  wrote:
> security/openssl was removed before, now security/openssl111 has become 
> security/openssl.

Ugh.

> A bit too eager for my taste, but that's why we all have private trees, don't 
> we.  ;)

This is going to go poorly, if previous attempts to update to 1.1 are any 
indication.



-- 
people didn't seem to be able to remember what it was like with the
elves around. Life was certainly more interesting then, but
usually because it was shorter. And it was more colourful, if you
liked the colour of blood. --Lords and Ladies

___
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 failing

[@lbutlr]

Portmaser -L errors out with

make: "/usr/ports/Mk/Uses/ssl.mk" line 97: You are using an unsupported SSL 
provider openssl

Make.conf:
DEFAULT_VERSIONS+=ssl=openssl apache=2.4 php=7.2 perl5=5.28 mysql=10.1m

Worked fine on Saturday, maybe Friday.



-- 
i wasn't born a programmer. i became one because i was impatient. -
Dave Winer

___
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"

Cannot update gnupg

[@lbutlr]

checking whether "make check" shall run all tests... no
configure:
***
*** The system does not provide a working iconv function.  Please
*** install a suitable library; for example GNU Libiconv which is
*** available at:
***   https://ftp.gnu.org/gnu/libiconv/
***
configure: error: 
***
*** Required libraries not found. Please consult the above messages
*** and install them before running configure again.
***
===>  Script "configure" failed unexpectedly.
Please report the problem to ad...@freebsd.org [maintainer] and attach the
"/usr/ports/security/gnupg/work/gnupg-2.2.18/config.log" including the output
of the failure of your make command. Also, it might be a good idea to provide
an overview of all packages installed on your system (e.g. a
/usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1

 # portmaster -l | grep libiconv
===>>> libiconv-1.14_11
 # freebsd-version -u
11.3-RELEASE-p4

gnupg-2.2.17_3 ua currently installed

Log file is here with package list appended

 



-- 
Today the road all runners come/Shoulder high we bring you home. And
set you at your threshold down/Townsman of a stiller town.

___
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: Checking you the maintainer of a port?

[@lbutlr]

On 27 Nov 2019, at 14:05, Janky Jay, III  wrote:
> Please see the "MAINTAINER=" line in the port's "Makefile”.

Aw hell, I should have gripped all the files. I was sure it would’t be in the 
make file!



-- 
"Are you pondering what I'm pondering?"
"I think so, but where is a fish?”

___
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"

Checking you the maintainer of a port?

[@lbutlr]

I thought that the maintainer of a port was listed somewhere in the files at 
user/ports//portbase/ but evidently not. What is the easiest way to find 
out, sitting in console on a server without a GUI, to find out who the 
maintainer is? (On my desktop I can just google and launch a browser, but that 
is not possible on most of the servers which do not have web clients installed.

(Right now I am looking for the maintainer of roundcube, but this is a general 
question.)


-- 
Yeah, and I never wanted to kick Albert Einstein in the nuts.

___
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: MariaDB 10.1.42?

[@lbutlr]

On 10 Nov 2019, at 15:26, j...@mailman-hosting.com wrote:
> On Nov 10, 2019, 4:24 PM -0500, @lbutlr , wrote:
>> Any idea when we might see MariaDB 10.1.42 to counter 
>> <https://vuxml.freebsd.org/freebsd/fc91f2ef-fd7b-11e9-a1c7-b499baebfeaf.html>?

> According to https://mariadb.com/kb/en/library/mariadb-10142-release-notes/ 
> 10.1.42, which was released *five* days ago, has a serious bug. This is fixed 
> in 10.1.43, which was released *two* days ago. See 
> https://mariadb.com/kb/en/library/mariadb-10143-release-notes/

I only checked the ports site, not knowing about maridb.com

> Perhaps you can provide a patch.

No, that’s not something I would be able to do.


-- 
SOURCERERS MAKE THEIR OWN DESTINY. THEY TOUCH THE EARTH LIGHTLY.

___
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"

MariaDB 10.1.42?

[@lbutlr]

Any idea when we might see MariaDB 10.1.42 to counter 
?

(It’s been a week).



-- 
A man without religion is like a fish without a bicycle.

___
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: Omg upgrade wants to install MySQL

[@lbutlr]

On 02 Nov 2019, at 20:29, Eugene Grosbein  wrote:
> 03.11.2019 9:20, @lbutlr wrote:
> 
>> On 02 Nov 2019, at 19:35, Eugene Grosbein  wrote:
>>> I prefer third option. Sometimes it is handy to "pkg lock" packages you 
>>> installed from ports buiklt with non-default options, too.
>> 
>> If I could tell which pkg install is going to install MySQL and libX stuff I 
>> would lock those, but I Dion’t see anyway to check that.
> 
> You need to lock MariaDB.

MariaDB *is* locked. Both client and server. Pkg update was still going to 
install MySQL.

>> And it does seem odd that pkg is still assuming MySQL and desktop FreeBSD.
>> I know of many 120 FreeBSD servers and not one has a GUI desktop.
>> I mean, I am sure they exist, but they must be a pretty tiny sliver.
> 
> First, it is NOT pkg assuming anything. Package repository has packages built 
> from ports with their *default* options
> and pkg merely uses them.

Fine. Ports assuming MySQL.

> Second, support of X headers/formats/libraries does not assume "desktop" 
> FreeBSD
> and does not install any graphical environment but generally only some small 
> headers or libs,
> not even libX11 not to mention heavy window managers or desktop environment.

A whole lot of X11 cruft gets installed if you do not go through and disable 
X11. A LOT. So there is some assumption in the defaults that there will be a 
desktop environment, yes.

___
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"

Omg upgrade wants to install MySQL

[@lbutlr]

I have mariadb101 (client and server) installed, but when looking at what pkg 
update will do, one of the things it will do is install MySQL. Is there 
something I need to do to tell it to use MariaDB instead?

Since I am here, it also wants to install a bunch of X11 packages, but I 
neither want nor have any desktop environment installed, so similar question, 
how can I tell pkg to run in “don’t enable GUIs” mode?



-- 
'That's blasphemy,' said the vampire. He gasped as Vimes shot him a
glance like sunlight. 'That's what people say when the voiceless speak.’

___
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: Rebuild between dot versions?

[@lbutlr]

On 8 Sep 2019, at 14:56, Adam Weinberger  wrote:
> You meant when
> updating FreeBSD to new minors. No, it's not strictly necessary,
> though you absolutely should rebuild anything that installs a KLD.
> Compiler improvements usually happen in minor releases, so you
> certainly won't get that benefit until you rebuild them all.

Seems to be working so far. I will recommend[pi;e the main things relatively 
soon. But all seems good so far.

Thanks!



-- 
Trying to engage you in any meaningful discussion is like trying to play
chess with a pigeon.  You shit all over the board and then strut around
acting like you won.

___
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: Rebuild between dot versions?

[@lbutlr]

On 8 Sep 2019, at 15:12, Pau Amma  wrote:
> On Sun, September 8, 2019 8:24 pm, @lbutlr wrote:
>> Also, is there a way to use freebsd-update to see what the current patch
>> level is of a release?
> 
> Assuming you mean "the highest patch level available for that version",
> not "the one I'm currently running": I believe this was discussed recently
> in IRC and the conclusion was "no, but there should be”.


Definitely should be, yes.



-- 
Everything that was magical was just a way of describing the world in
words it couldn't ignore.

___
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"

Rebuild between dot versions?

[@lbutlr]

Is it necessary to rebuild ports when moving from dot versions (like 11.2 tp 
11.3)?

Also, is there a way to use freebsd-update to see what the current patch level 
is of a release?



-- 
Why would I ever want to go outside the Beltway?

___
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: ruby25 from ports will not compile

[@lbutlr]

On 6 Sep 2019, at 19:16, Yasuhiro KIMURA  wrote:
> From: "@lbutlr" 
> Subject: ruby25 from ports will not compile
> Date: Fri, 6 Sep 2019 12:44:29 -0600
> 
>> Trying to update ruby on 11.2-RELEASE-p11 (I have also tried to switch to 
>> ruby26 with basically the same results)
>> 
>> # cd /usr/ports/lang/ruby25 
>> # make MAKE_JOBS_UNSAFE=yes install   
>> vm.c:(.text+0x1e0bb): undefined reference to 
>> `__dtraceenabled_ruby___method__entry'
>> vm.c:(.text+0x1e0ef): undefined reference to 
>> `__dtraceenabled_ruby___method__return'
>> vm.c:(.text+0x1e15d): undefined reference to `__dtrace_ruby___method__entry'
>> vm.c:(.text+0x1e274): undefined reference to `__dtrace_ruby___method__return'
>> vm.o: In function `hook_before_rewind':
>> vm.c:(.text+0x1ed7b): undefined reference to 
>> `__dtraceenabled_ruby___method__return'
>> vm.c:(.text+0x1eefe): undefined reference to `__dtrace_ruby___method__return'
>> cc: error: linker command failed with exit code 1 (use -v to see invocation)
>> *** Error code 1
>> 
>> Stop.
>> make[2]: stopped in /usr/ports/lang/ruby25/work/ruby-2.5.6
>> *** Error code 1
> 
> What is your architecture? I made clean install of 11.2-RELEASE-p14
> amd64, checked out latest ports tree (r511379) and tried
> 
> # cd /usr/ports/lang/ruby25
> # make BATCH=yes install
> # cd /usr/ports/lang/ruby26
> # make BATCH=yes install
> 
> Then everything completed successfully.

FreeBSD 11.2-RELEASE-p11 #0: Tue Jul  2 21:05:37 UTC 2019 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386

I’ve just removed ruby for now, I couldn’t find anything that was using it.



-- 
You think you can catch Keyser Soze?

___
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: ruby25 from ports will not compile

[@lbutlr]

On 6 Sep 2019, at 13:30, Walter Schwarzenfeld  wrote:
> CONFIGURE_ARGS+=--disable-dtrace

Shouldn’t

 [ ] DSIABLE DEBUG 

do that?

I added the suggested line to make.conf and did make clean && make and same 
results.



-- 
Turning and turning in the widening gyre
The falcon cannot hear the falconer;

___
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"

ruby25 from ports will not compile

[@lbutlr]

Trying to update ruby on 11.2-RELEASE-p11 (I have also tried to switch to 
ruby26 with basically the same results)

 # cd /usr/ports/lang/ruby25 
 # make MAKE_JOBS_UNSAFE=yes install   
vm.c:(.text+0x1e0bb): undefined reference to 
`__dtraceenabled_ruby___method__entry'
vm.c:(.text+0x1e0ef): undefined reference to 
`__dtraceenabled_ruby___method__return'
vm.c:(.text+0x1e15d): undefined reference to `__dtrace_ruby___method__entry'
vm.c:(.text+0x1e274): undefined reference to `__dtrace_ruby___method__return'
vm.o: In function `hook_before_rewind':
vm.c:(.text+0x1ed7b): undefined reference to 
`__dtraceenabled_ruby___method__return'
vm.c:(.text+0x1eefe): undefined reference to `__dtrace_ruby___method__return'
cc: error: linker command failed with exit code 1 (use -v to see invocation)
*** Error code 1

Stop.
make[2]: stopped in /usr/ports/lang/ruby25/work/ruby-2.5.6
*** Error code 1

 # pkg info -dr ruby   
  [12:38] [/usr/ports/lang/ruby25] 
ruby-2.5.5_3,1
Depends on :
libyaml-0.2.2
libunwind-20170615
libffi-3.2.1_3
libedit-3.1.20190324,1

Since it has no dependencies, I am considering just deleting it as it may well 
be left over from something that is no longer being used.


-- 
Can I tell you the truth? I mean this isn't like TV news, is it?

___
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"

A port like pi-hole?

[@lbutlr]

I’ve been running pi-hole on my home LAN and would like to run something like 
it on my FreeBSD machines as well. There isn’t a pi-hole port, but is there 
something like it that lets you easily setup blacklists to block DNS queries 
for adware/malware servers?



-- 
There is no Humpty Dumpty, and there is no God. None, not one, no God,
never was.

___
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: freebsd-ports Digest, Vol 846, Issue 7

[@lbutlr]

On 18 Aug 19, at 06:23 , Adriaan de Groot  wrote:
> On Sunday, 18 August 2019 14:00:01 CEST freebsd-ports-requ...@freebsd.org 
> wrote:
>>> So I hoped to collect experiences on this.
>> 
>> I was favorably impressed by Otter Browser, but have not been able to update
>> because my FreeBSD installation, 11.1-STABLE, is too far behind for
>> updating ports.
> 
> You "otter" be able to build current Qt 5.12.2 and all the bits underneath 
> otter, although that's not something that the kde@ team does or supports.

I looked at Otter Browser briefly, but it was unable to load many pages 
correctly, so I removed it. It seemed find for more basic stuff, but anything 
that was heavy CSS/resposive/Complicated just didn’t ;layout correctly.



-- 
There is a road, no simple highway, between the dawn and the dark of
night

___
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: PHP version retirement

[@lbutlr]

On 12 Aug 19, at 01:04 , Martin Waschbüsch  wrote:
> So, I find it wrong to say, as I understood you, to remove a package from the 
> ports tree because otherwise others people, for instance users of FreeBSD, 
> would have the *expectation* of receiving support for those packages.

There is not expectation that any code is being maintained, but there *IS* an 
expectation that the software in ports is being maintained, supported, and is 
functional.


-- 
Im finding's you'r mis'use of apostrophe's disturbing.

___
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: firefox

[@lbutlr]

On 11 Aug 2019, at 20:29, bruce  wrote:
> I have tried firefox.  It crashes regularly 

That doesn’t sound right. If Firefox is crashing a lot there is something not 
quite right with your system or install.

Seamonkey was last update a bit over a year ago.

That’s about a decade in Browser time.



-- 
'That's blasphemy,' said the vampire. He gasped as Vimes shot him a
glance like sunlight. 'That's what people say when the voiceless speak.’

___
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: need help with python

[@lbutlr]

On 4 Jul 2019, at 20:39, AN  wrote:
> 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?

Rebuild all the ports that depend on python (and any python depends on).

You might also look at what you have that requires python. For example, I 
recently;y eliminated almost all the python packages by simply removing scons. 
It may come back if something needs scons to build in the future, but for now I 
have only three python 3.6 packages installed:

===>>> py36-ply-3.11
===>>> py36-setuptools-41.0.0
===>>> python36-3.6.8_2

These are required for bindutils, but I eliminated the one part of blind tools 
that needs put-on I wouldn’t have it at all.

Of course, your setup is different, but it is definitely worth looking at your 
depends.

pkg -rd python27



-- 
Thanks to great leaders such as Ghengis Khan, Joan of Arc, and Socratic
Method, the world is full of history.


___
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: portsnap broken?

[@lbutlr]

On 2 Jul 2019, at 18:33, Ashish SHUKLA  wrote:
> I noticed portsnap mirror is outdated for few hours now:

Out of date based on what? How often are you pulling portsnap?

(I run portsnap cron update once a day)



-- 
THEY ARE LAUGHING AT ME, NOT WITH ME Bart chalkboard Ep. 7G12


___
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: Cleaning up pkg-message

[@lbutlr]

On 9 Jun2019, at 09:33, Grzegorz Junka  wrote:
> Because pkg doesn't know if it's a first install or reinstall.

This is a solvable issue, however. There are may things that could be checked 
to see if this is a new install or not,  though some go them will require some 
additional tracking pf [ports as they are added and removed.


-- 
These go to 11


___
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: net/xrdp: Issue(s) with Channels/Clipboard.

[@lbutlr]

On Jun 6, 2019, at 8:15 AM, Janky Jay, III  wrote:
> I had to do a "portsnap fetch extract" and install audio/lame via ports
> to get this to work. Now I have a full ports environment for just one
> dependency. It's a small VM that is only used for certain things so I
> try to use space sparingly. This makes it somewhat of an issue.

You do not have to install the entire ports tree to install a package from 
ports.

# svnlite checkout https://svn.freebsd.org/ports/head/audio/lame

> The real issue, though, is that this was installed using "pkg" and does
> not work correctly due to audio/lame being a dependency that does not
> have a package. Hence the reason the maintainer will be removing
> audio/lame as a dependency.

Yep, that does seem like an issue.




-- 
showing snuffy is when Sesame Street jumped the shark


___
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: net/xrdp: Issue(s) with Channels/Clipboard.

[@lbutlr]

On Jun 5, 2019, at 7:56 AM, Janky Jay, III  wrote:
> So, this needed to be built from ports. I
> would imagine that these are important to people using sound (I am not)
> so some audio dependencies should remain. However, I'm not sure it
> should be "audio/lame" if there is not a package available for it.

Why is it an issue that lame must be built from ports?

LOTS of things must be built from ports.



-- 
"It was a dark and stormy night; the rain fell in torrents -- except at
occasional intervals, when it was checked by a violent gust of wind
which swept up the streets (for it is in London that our scene lies)
rattling along the housetops, and fiercely agitating the scanty flame of
the lamps that struggled against the darkness.”


___
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"

Vim 8.1 failing to update

[lbutlr]

Vim 8.1 is failing to update from vim-8.1.1248 after trying to install 
/usr/ports/editors/vim/files/vietnamese_viscii.vim

Why is it trying to install this? I have no need for vitnekmese and don’t see 
anything in make config that mentions Vietnamese or any "alternate alphabet" 
language.

That actual error is

msgfmt --desktop -d . --template gvim.desktop.in -o gvim.desktop
msgfmt: Cannot convert from "ISO-8859-1" to "UTF-8". msgfmt relies on iconv(). 
This version was built without iconv().
*** Error code 1

libiconv doesn’t have a build option for UTF-8 and neither does gettext-tools 
(which installs msgfmt).



-- 
<[TN]FBMachine> I got kicked out of Barnes and Noble once for moving all
the bibles into the fiction section


___
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: Dovecot packages

[@lbutlr]

On 22 May 2019, at 16:41, Doug Hardie  wrote:
> It appears that the dovecot package is now the one that is maintained and 
> dovecot2 package has remained stagnant.  

You didn't replace your port tree when you upgraded to 12.0-RELEASE.

I think that portsnap fetch extract ensures your ports tree matches the current 
ports.

Ah, yes, from the man -8 portsnap:

 extract  Extract a ports tree, replacing existing files and
  directories.  NOTE: This will remove anything occupying the
  location where files or directories are being extracted; in
  particular, any changes made locally to the ports tree (for
  example, adding new patches) will be silently obliterated.

===>
  Only run this command to initialize your portsnap-maintained
  ports tree for the first time, if you wish to start over
  with a clean, completely unmodified tree, or if you wish to
  extract a specific part of the tree (using the path option).
===>

-- 
Whoever had created humanity had left in a major design flaw. It was its
tendency to bend at the knees. --Feet of Clay


___
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: ImageMacgick6 seems to conflict with itself

[@lbutlr]

On 29 Apr 2019, at 17:34, bob prohaska  wrote:
> By the time I fell into the trap, the old ImageMagick directory
> had been renamed to ImageMagick6,

I've run into this many times of the years with many packages. It is always 
extreme annoying and I can't see any reason for this behavior.

However, postmaster -o seems to handle things correctly.


-- 
These go to 11


___
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: ltmain.sh not found

[@lbutlr]

On 25 Apr 2019, at 07:14, Willem Offermans  wrote:
> When I have time, I will dig into poudriere. I assume there is 
> documentation/tutorial around that will get me going.
> The man pages will also be helpful.

Loos like



and 



might be the places to start.

(I am also on postmaster and am at least partially, if not mostly, posting this 
to the list so I have an archive of the links :)


-- 
I AM ZOMBOR! (kelly) ZOMBOR!


___
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: Suggestion to split games category into games-console, games-engine and games

[@lbutlr]

On 20 Apr 2019, at 14:30, Sid  wrote:
> 
> /usr/ports/games is already very large.
> What about splitting up games in the ports tree into games, games-console and 
> games-engine?

What about a configure file or option to exclude certain branches of the ports 
tree os I don't have to keep downloading updates to packages I will never run?

For example, I have no need of any of the languages, X11-*, irc, games, cad, or 
finance on my mail server.


-- 
Not all who wander are lost



___
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"

postfix and postfix-current

[@lbutlr]

I see today that

===>>> postfix-current-3.4.20190106,5
  ===>>> New version available: postfix-current-3.5.20190330,5

What is the proper way to move from postfix-current-3.4.20190106,5 to 
postfix-3.4.5 (mail/postfix)?

I was on postfix current because the root postfix had not updated to the 3.4 
branch, I am not ready to move to 3.5 at this point.

is it enough to simply pkg delete -f postfix-current-3.4.20190106,5 and then 
postmaster mail/postfix or is there any other steps to take?


-- 
'Everything will be all right. From History's point of view, that is.
There really isn't any other.'


___
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"

port configuration diff with defaults

[@lbutlr]

Is there a way to check if a port is using the default config (make config) and 
if not, to see the differences between the default config and the ports current 
config?


-- 
Humans are always slightly lost. It's a basic characteristic. It
explains a lot about them.


___
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"

missing dependency

[@lbutlr]

pkg: dovecot has a missing dependency: mariadb100-client
pkg: postfix-current has a missing dependency: mariadb100-client
pkg: net-snmp has a missing dependency: mariadb100-client
pkg: rsyslog has a missing dependency: mariadb100-client
pkg: p5-DBD-mysql has a missing dependency: mariadb100-client

This is correct, as I had to move to mariadb102-cloent, but why aren't the 
other packages up=dated with the new version.

I have recently (yesterday) updated all packages.


-- 
"I've had a perfectly wonderful evening. But this wasn't it." - Groucho
Marx


___
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: Updating Postfix

[@lbutlr]

On 21 Mar 2019, at 06:25, Carmel NY  wrote:
> I am just inquiring to find out if there is any specific reason for
> these ports not being updated. In the past, the releases and the
> FreeBSD ports system were kept virtually in sync.

There was some talk when 3.4.0 came out about withdrawing it, and then the 
.1-.4 updates came quite quickly.

I don't know, but I guess, this delayed the port maintainer from moving forward.


-- 
in the long run there's still time to change the road you're on


___
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?

[@lbutlr]

On 17 Jan 2019, at 05:53, Robert Huff  wrote:
> Samy Mahmoudi writes:
>> Why do you need a replacement for xmms ?
> Because it's no longer in the ports tree?

/usr/ports/audio/xmms2
/usr/ports/audio/gxmms2

Is there an issue with xmms2?

-- 
I loved you when our love was blessed I love you now there's nothing
left But sorrow and a sense of overtime


___
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"

Port Spamass-rules?

[@lbutlr]

When updating Spam Assassin today I noticed that the notes at the end of the 
port install still recommend installing mail/spamass-rules.

This should not be done, right?

-- 
Get in there you big furry oaf! I don't care what you smell!

___
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"