Re: Perl version change and ports/UPDATING

[David Wolfskill]

On Sat, Mar 31, 2018 at 04:23:54PM -0700, Kevin Oberman wrote:
> On Sat, Mar 31, 2018 at 7:25 AM, David Wolfskill 
> wrote:
> ... 
> > But "pkg updating -i" fails to display the 20180330 entry for me;
> > it does show entries for some(?) other ports I have installed:
> ...
> > Is the above a demostration of a problem with "pkg updating"?
> > Something else?
> ...
> I suspect thre issue is the handing of the wildcard (lang/perl5*). Either
> it's a bug or wildcards should not be allowed in UPDATING. There are LOTS
> of entries with asterisks, though, ome rather more complex such as:
> 20180308:
>   AFFECTS: */php* */pecl* */pear*
> BTW, that one should show up in "pkg updating -i" and does not, either.
> 

I finally(!) got around to unpacking the distribution files for
pkg-1.10.5; looking at src/updating.c, "pkg updating" uses either
strcasestr() or strstr() (depending on whether or not -i is specified)
for matching the origins of installed ports against the "AFFECTS" lines
in ports/UPDATING.

I see no code that would support anything other than literal string
matches -- no attempts to specify/use meta-characters; no globs;
no regular expressions.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
An investigator who doesn't make a perp nervous isn't doing his job.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: Perl version change and ports/UPDATING

[Kevin Oberman]

On Sat, Mar 31, 2018 at 7:25 AM, David Wolfskill 
wrote:

> While the actual change to the Perl version works fine for me, I
> find that invoking "pkg updating" fails to display the 20180330
> ports/UPDATING entry.  I got lucky, because I found out about the
> change a different way.
>
> I maintain /usr/ports as an SVN working copy, using a local private
> mirror (updated nightly):
>
> g1-215(11.1-S)[1] svn info /usr/ports/
> Path: /usr/ports
> Working Copy Root Path: /usr/ports
> URL: file:///svn/freebsd/ports/head
> Relative URL: ^/head
> Repository Root: file:///svn/freebsd/ports
> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
> Revision: 466037
> Node Kind: directory
> Schedule: normal
> Last Changed Author: mandree
> Last Changed Rev: 466037
> Last Changed Date: 2018-03-31 03:08:17 -0700 (Sat, 31 Mar 2018)
>
> g1-215(11.1-S)[2]
>
>
> The 20180330 entry does exist in /usr/ports/UPDATIMG:
>
> g1-215(11.1-S)[2] grep -i -B 2 -A 2 perl /usr/ports/UPDATING | head
>
> 20180330:
>   AFFECTS: users of lang/perl5*
>   AUTHOR: m...@freebsd.org
>
>   The default Perl version has been switched to Perl 5.26.  If you are
> using
>   binary packages to upgrade your system, you do not have anything to do,
> pkg
>   upgrade will do the right thing.  For the other people, follow the
> --
>
> g1-215(11.1-S)[3]
>
>
> I have Perl installed:
>
> g1-215(11.1-S)[3] pkg info -o perl5\*
> perl5-5.26.1   lang/perl5.26
> g1-215(11.1-S)[4]
>
>
> But "pkg updating -i" fails to display the 20180330 entry for me;
> it does show entries for some(?) other ports I have installed:
>
> g1-215(11.1-S)[4] pkg updating -i | head
> 20180319:
>   AFFECTS: users of dns/dnsmasq
>   AUTHOR: mand...@freebsd.org
>
>   Note that with dnsmasq 2.79, some parts of the interface have changed in
> an
>   incompatible way versus previous versions. This comprises changed
> recursion
>   behaviour, signature support, a change for SIGINT (vs. SIGHUP) behaviour.
>
>   Note especially that dnsmasq will no longer answer non-recursive queries
>   unless it is marked authoritative!  Be sure to see the manual page for
> the
> g1-215(11.1-S)[5]
>
>
> Is the above a demostration of a problem with "pkg updating"?
> Something else?
>
> Thanks!
>
> Peace,
> david
> --
> David H. Wolfskill  da...@catwhisker.org
> An investigator who doesn't make a perp nervous isn't doing his job.
>
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.
>

I also don't see the perl message. The newest entry I see is:
20180214:
  AFFECTS: users of lang/ruby23
I have no installed ports with newer update messages installed.

I suspect thre issue is the handing of the wildcard (lang/perl5*). Either
it's a bug or wildcards should not be allowed in UPDATING. There are LOTS
of entries with asterisks, though, ome rather more complex such as:
20180308:
  AFFECTS: */php* */pecl* */pear*
BTW, that one should show up in "pkg updating -i" and does not, either.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Perl help needed

[Kevin Oberman]

On Sat, Mar 31, 2018 at 1:22 PM, Robert Huff  wrote:

>
> Christoph Moench-Tegeder writes:
>
> >  ## Robert Huff (roberth...@rcn.com):
> >
> >  >On a system with over 850 ports, 32 starting with "p5-", the
> >  > list of dependent ports portmaster created from
> >  > "pkg shlib -qR libperl.so.5.24" was over 200, including things like
> >  > FireFox and llvm50 (llvm is required for mesa-dri).
> >
> >  That sound like "too much". I've 1408 ports installed, of which 90
> >  are named p5-*, and "pkg shlib -qR libperl.so.5.26" shows only 32 ports.
> >
> >  Did you rebuild everything along the build-dependencies, or does your
> >  build tool use the run-depdendencies?
> >  There had been a time when ports had way too many dependencies
> registered,
> >  if my memory serves right that was because many build-dependencies were
> >  recorded as run-dependencies (or there was no distinction at all). Is
> >  that a leftover effect from those times?
>
> "Insufficient data, Captain."
> I followed the instructions for portmaster from
> UPDATING/20171103, only changing the version numbers.
> Running "pkg shlib -qR libperl.so.5.26" now produces 13 items;
> this makes your explanation plausible, if not authoritative.
>
> Again, thanks.
>
>
> Robert Huff


While the method in the instructions is  right, it is serious overkill. It
not only lists direct dependencies, but ports that depend on libs or other
executables that link to libperl.

You can save a LOT of time and CPU cycles by updating the obvious
candidates (portmaster p5-) to get almost everything and then using "pkg
check -B" to find all ports that REALLY link to libperl.so.5.24. All I
found was not-snmp (which really IS a perl5 port, but is not prefixed by
p5-) and ImageMagick.

In retrospect, I probably didn't need to re-install most of the p5- ports
as most just call perl5, but have no direct linkages to it. I doubt that
more then a handful of ports actually needed to be touched.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Perl help needed

[Robert Huff]

Christoph Moench-Tegeder writes:

>  ## Robert Huff (roberth...@rcn.com):
>  
>  >On a system with over 850 ports, 32 starting with "p5-", the
>  > list of dependent ports portmaster created from
>  > "pkg shlib -qR libperl.so.5.24" was over 200, including things like
>  > FireFox and llvm50 (llvm is required for mesa-dri).
>  
>  That sound like "too much". I've 1408 ports installed, of which 90
>  are named p5-*, and "pkg shlib -qR libperl.so.5.26" shows only 32 ports.
>  
>  Did you rebuild everything along the build-dependencies, or does your
>  build tool use the run-depdendencies?
>  There had been a time when ports had way too many dependencies registered,
>  if my memory serves right that was because many build-dependencies were
>  recorded as run-dependencies (or there was no distinction at all). Is
>  that a leftover effect from those times?

"Insufficient data, Captain."
I followed the instructions for portmaster from
UPDATING/20171103, only changing the version numbers.
Running "pkg shlib -qR libperl.so.5.26" now produces 13 items;
this makes your explanation plausible, if not authoritative.

Again, thanks.


Robert Huff




___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Perl help needed

[Christoph Moench-Tegeder]

## Robert Huff (roberth...@rcn.com):

>   On a system with over 850 ports, 32 starting with "p5-", the
> list of dependent ports portmaster created from
> "pkg shlib -qR libperl.so.5.24" was over 200, including things like
> FireFox and llvm50 (llvm is required for mesa-dri).

That sound like "too much". I've 1408 ports installed, of which 90
are named p5-*, and "pkg shlib -qR libperl.so.5.26" shows only 32 ports.

Did you rebuild everything along the build-dependencies, or does your
build tool use the run-depdendencies?
There had been a time when ports had way too many dependencies registered,
if my memory serves right that was because many build-dependencies were
recorded as run-dependencies (or there was no distinction at all). Is
that a leftover effect from those times?

Regards,
Christoph

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

node v9.9.0 bad dependency on libuv

[Mahmoud Al-Qudsi]

Hello all,

The binary node package on FreeBSD 11.1-RELEASE has a bad dependency on libuv. 
I had libuv 1.17.0 installed and installed node with `pkg install node`, which 
installed node v9.9.0.

Running `node` at this point would return the following error message:

> /usr/local/bin/node: Undefined symbol "uv_os_getpid"

Updating libuv to the latest (1.19.2) resolved that error.

I’m not sure if that symbol was introduced in 1.18 or 1.19, but the libuv 
dependency for node needs to be bumped.

Thanks,

Mahmoud Al-Qudsi
NeoSmart Technologies 
___
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 RSS feed

[Kevin Oberman]

On Fri, Mar 30, 2018 at 9:45 AM, Andrea Venturoli  wrote:

> Hello.
>
> I used to read ports' UPDATING via RSS, but now the feed I was using (from
> versia) seems to be gone.
>
> Anyone knows of another one?
>
> I looked into FreshPorts, but didn't find a way to get this specific feed.
>
>  bye & Thanks
> av.
>

I moved to:
http://updating.kojevnikov.com/
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Perl help needed

[Robert Huff]

Christoph Moench-Tegeder writes:

>  > Socket.c: loadable library and perl binaries are mismatched
>  > (got handshake key 0xd200080, needed 0xdf00080) 
>  
>  The perl default version changed - are you sure your perl and modules
>  still match? See UPDATING 20180330.
>  The error message is just what I'd expect for a mismatch.

Following this path seems to have fixed things.
Warning to anyone who does this:
On a system with over 850 ports, 32 starting with "p5-", the
list of dependent ports portmaster created from
"pkg shlib -qR libperl.so.5.24" was over 200, including things like
FireFox and llvm50 (llvm is required for mesa-dri).  Total rebuild
time was many hours on a lightly loaded 4 core*3 ghz machine.

My profuse thinks to all who offered advice.


Respectfully,


Robert Huff



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

UPDATING RSS feed

[Andrea Venturoli]

Hello.

I used to read ports' UPDATING via RSS, but now the feed I was using 
(from versia) seems to be gone.


Anyone knows of another one?

I looked into FreshPorts, but didn't find a way to get this specific feed.

 bye & Thanks
av.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Perl version change and ports/UPDATING

[David Wolfskill]

While the actual change to the Perl version works fine for me, I
find that invoking "pkg updating" fails to display the 20180330
ports/UPDATING entry.  I got lucky, because I found out about the
change a different way.

I maintain /usr/ports as an SVN working copy, using a local private
mirror (updated nightly):

g1-215(11.1-S)[1] svn info /usr/ports/
Path: /usr/ports
Working Copy Root Path: /usr/ports
URL: file:///svn/freebsd/ports/head
Relative URL: ^/head
Repository Root: file:///svn/freebsd/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 466037
Node Kind: directory
Schedule: normal
Last Changed Author: mandree
Last Changed Rev: 466037
Last Changed Date: 2018-03-31 03:08:17 -0700 (Sat, 31 Mar 2018)

g1-215(11.1-S)[2] 


The 20180330 entry does exist in /usr/ports/UPDATIMG:

g1-215(11.1-S)[2] grep -i -B 2 -A 2 perl /usr/ports/UPDATING | head

20180330:
  AFFECTS: users of lang/perl5*
  AUTHOR: m...@freebsd.org

  The default Perl version has been switched to Perl 5.26.  If you are using
  binary packages to upgrade your system, you do not have anything to do, pkg
  upgrade will do the right thing.  For the other people, follow the
--

g1-215(11.1-S)[3] 


I have Perl installed:

g1-215(11.1-S)[3] pkg info -o perl5\*
perl5-5.26.1   lang/perl5.26
g1-215(11.1-S)[4] 


But "pkg updating -i" fails to display the 20180330 entry for me;
it does show entries for some(?) other ports I have installed:

g1-215(11.1-S)[4] pkg updating -i | head
20180319:
  AFFECTS: users of dns/dnsmasq
  AUTHOR: mand...@freebsd.org

  Note that with dnsmasq 2.79, some parts of the interface have changed in an
  incompatible way versus previous versions. This comprises changed recursion
  behaviour, signature support, a change for SIGINT (vs. SIGHUP) behaviour.

  Note especially that dnsmasq will no longer answer non-recursive queries
  unless it is marked authoritative!  Be sure to see the manual page for the
g1-215(11.1-S)[5] 


Is the above a demostration of a problem with "pkg updating"?
Something else?

Thanks!

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
An investigator who doesn't make a perp nervous isn't doing his job.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: FreeBSD textproc/elasticsearch6 does not honour /etc/profile

[Mark Felder]

On Sat, Mar 31, 2018, at 02:25, Leander Schäfer wrote:
> Hello Mark,
> 
> Thanks for your reply. I didn't know about the elasticsearch_env="" - so
> thanksfor that. So my follow-up questions are:
> 
>   * How would I have to set up elasticsearch_env="", cause according to
> the man of env elasticsearch_env="-S -P
> /usr/local/bin:/usr/local/sbin" wouldn't do the job.
>   * What needs to be changed, so elasticsearch's auto detect script
> would work with regular values of PATH? Cause currently the default
> PATH is like: PATH=/sbin:/bin:/usr/sbin:/usr/bin and this won't work
> with an openjdk compiled from ports. Cause this would be my prefered
> way.
> 

I guess I am confused about what you are trying to accomplish. When you install 
ElasticSearch from ports/packages on FreeBSD it automatically installs Java 
(OpenJDK) from ports/packages and will use it by default. You do not have to 
specify a which Java to use; simply modifying the configuration file(s) and 
starting the service should be sufficient.

Are you in a situation where you have multiple versions of Java on the system 
and you are trying to tell ElasticSearch to use a different one?

> Can I post your replies in the FreeBSD forum? Might be useful for others
> as well ;)
> 
> Thanks a lot
> 

Certainly


-- 
  Mark Felder
  ports-secteam & portmgr member
  f...@freebsd.org
___
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 textproc/elasticsearch6 does not honour /etc/profile

[Leander Schäfer]

Hello Mark,

Thanks for your reply. I didn't know about the elasticsearch_env="" - so
thanksfor that. So my follow-up questions are:

  * How would I have to set up elasticsearch_env="", cause according to
the man of env elasticsearch_env="-S -P
/usr/local/bin:/usr/local/sbin" wouldn't do the job.
  * What needs to be changed, so elasticsearch's auto detect script
would work with regular values of PATH? Cause currently the default
PATH is like: PATH=/sbin:/bin:/usr/sbin:/usr/bin and this won't work
with an openjdk compiled from ports. Cause this would be my prefered
way.

Can I post your replies in the FreeBSD forum? Might be useful for others
as well ;)

Thanks a lot

Best regards,
Leander


Am 30.03.18 um 21:34 schrieb Mark Felder:
>
> On Thu, Mar 29, 2018, at 05:43, Leander Schäfer wrote:
>> Hello,
>>
>> it looks like textproc/elasticsearch6 does not honour /etc/profile?
>> Please have a look for detailed description and reproduction of the
>> issue:
>> https://forums.freebsd.org/threads/textproc-elasticsearch6-does-not-honour-etc-profile.65338/
>>
>> Best regards,
>>
>> Leander S.
> I'm pretty sure this is not supposed to work. /etc/profile is used by sh(1) 
> and would only be read during a login shell. The FreeBSD rc subsystem uses 
> "su -m" when running processes as a specific user, not "su -l". The "su -l" 
> would fail because ElasticSearch's user has a default shell of /sbin/nologin. 
> As far as I can tell this is normal behavior.
>
> If you need to change env for Elastic you can use the elasticsearch_env="" in 
> /etc/rc.conf. Any further questions about overcoming issues in your 
> environment are welcome. We also have a list for elastic now called 
> "freebsd-elas...@freebsd.org". 
>
>
> Hope that helps,
>
>

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