Re: Dovecot packages

[Doug Hardie]

> On 22 May 2019, at 16:23, Miroslav Lachman <000.f...@quip.cz> wrote:
> 
> Doug Hardie wrote on 2019/05/23 00:41:
> 
> [...]
> 
>> Unless you notice this interesting anomaly, you can get easily burned like I 
>> did.  I would recommend that either the dovecot2 package be deleted, or at 
>> least kept current with the dovecot package.
> 
> There is no dovecot2 package in the official FreeBSD repository / ports tree: 
> https://www.freshports.org/search.php?query=dovecot
> 
> You have very stale packages on your machines and you didn't read 
> instructions in UPDATING file of "pkg updating" command:

Thats quite interesting.  When I run pkg updating command, the first entry is 
dated 20160616.

pkg-1.10.5_5   Package manager

# freebsd-version -ku
12.0-RELEASE-p3
12.0-RELEASE-p3

brain# pkg update
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
brain# pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking for upgrades (0 candidates): 100%
Processing candidates (0 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.



Same results on all my machines.


> 
> 
> 20170807:
>  AFFECTS: users of mail/dovecot2 and mail/dovecot2-pigeonhole
>  AUTHOR: ad...@freebsd.org
> 
>  Now that dovecot1 has been removed from the ports tree, dovecot2
>  and dovecot2-pigeonhole have been renamed to simply dovecot and
>  dovecot-pigeonhole.
> 
>  pkg should handle the rename automatically, but if you run into
>  trouble, you can point pkg at the new origin via:
> 
>  # pkg set -o mail/dovecot2:mail/dovecot
>  # pkg set -o mail/dovecot2-pigeonhole:mail/dovecot-pigeonhole
> 
>  Similarly, you can point portmaster at the new location via:
> 
>  # portmaster -o mail/dovecot mail/dovecot2
> 
>  If all else fails, just remove and reinstall the package:
> 
>  # pkg delete dovecot2
>  # pkg install dovecot

That was the approach I used.  Worked fine.  Dovecot now works properly again.

> 
> Miroslav Lachman

___
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

[Miroslav Lachman]

Doug Hardie wrote on 2019/05/23 00:41:

[...]


Unless you notice this interesting anomaly, you can get easily burned like I 
did.  I would recommend that either the dovecot2 package be deleted, or at 
least kept current with the dovecot package.


There is no dovecot2 package in the official FreeBSD repository / ports 
tree: https://www.freshports.org/search.php?query=dovecot


You have very stale packages on your machines and you didn't read 
instructions in UPDATING file of "pkg updating" command:



20170807:
  AFFECTS: users of mail/dovecot2 and mail/dovecot2-pigeonhole
  AUTHOR: ad...@freebsd.org

  Now that dovecot1 has been removed from the ports tree, dovecot2
  and dovecot2-pigeonhole have been renamed to simply dovecot and
  dovecot-pigeonhole.

  pkg should handle the rename automatically, but if you run into
  trouble, you can point pkg at the new origin via:

  # pkg set -o mail/dovecot2:mail/dovecot
  # pkg set -o mail/dovecot2-pigeonhole:mail/dovecot-pigeonhole

  Similarly, you can point portmaster at the new location via:

  # portmaster -o mail/dovecot mail/dovecot2

  If all else fails, just remove and reinstall the package:

  # pkg delete dovecot2
  # pkg install dovecot

Miroslav Lachman
___
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: pkg query hackaton

[Tatsuki Makino]

Excuse me.
It doesn't matter, but I would also like the following command:

e.g. foodaemon-X.X ->depends to-> libbar-X.X ->depends to-> libfoo-X.0

If libfoo-X.0 is updated to libfoo-X.1, perhaps, foodaemon-X.X should be
restarted. But pkg info -r libfoo is listed as below, foodaemon could
not be found.

libfoo-X.1:
libbar-X.X

So for example, If we write -r twice to show all packages.

% pkg info -r -r libfoo
libfoo-X.1:
libbar-X.X
foodaemon-X.X

Could someone do such a modify? :)
___
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"

Dovecot packages

[Doug Hardie]

Some years ago I setup a server with dovecot2 package.  At that time there were 
2 dovecot packages: dovecot which had a version of 1.x and dovecot2 which had a 
version of 2.x.  That made sense since dovecot v2 is quite different from v1.

As time went on I was upgrading that server to FreeBSD 12-RELEASE and just did 
a pkg upgrade during the upgrade process.  Dovecot upgraded to a more recent 
v2.x.  However, it no longer worked.  There were numerous error messages 
logged.  I thought that was strange since I had another system with dovecot v2 
running just fine.  Eventually I discovered that the two dovecot packages have 
changed.  The working system was a dovecot package which is now v2.y where y is 
significantly greater than dovecot2 v2.x.  It appears that the dovecot package 
is now the one that is maintained and dovecot2 package has remained stagnant.  

Unless you notice this interesting anomaly, you can get easily burned like I 
did.  I would recommend that either the dovecot2 package be deleted, or at 
least kept current with the dovecot package.

-- Doug

___
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 lang/phantomjs [deprecated]

[Douglas Thrift]

On 5/22/2019 3:25 AM, Miroslav Lachman wrote:
> The port lang/phantomjs is marked as deprecated / expired 2019-05-15. Is
> there any alternative in the ports tree? I searched the net and found
> https://slimerjs.org but it is not in the ports tree. (I don't have a
> skill to port it and maintain it myself)
> 
> One of my clients is using phantomjs thru some webapplication so I need
> to find some replacement.
> 
> Kind regards
> Miroslav Lachman
> ___
> 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"

I have been looking at using https://github.com/GoogleChrome/puppeteer
as something to move to from phantomjs for the use case that I had.

-- 
Douglas William Thrift

___
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 bind911 or 914

[Kevin Oberman]

On Wed, May 22, 2019 at 8:54 AM Wojciech Puchar  wrote:

> i've reinstalled bind914 (and then tried 911 too) after updating to latest
> FreeBSD-11
>
> and the problem is that bind cannot perform any TCP transfers
>
> in logs i'm getting like this
>
> May 22 20:50:55 <3.6> puchar named[67338]: transfer of
> 'icetransport.pl/IN' from 84.10.41.58#53: connected using
> 194.1.144.90#44228
> May 22 20:50:55 <3.3> puchar named[67338]: transfer of
> 'icetransport.pl/IN' from 84.10.41.58#53: failed while receiving
> responses: host
> May 22 20:50:55 <3.6> puchar named[67338]: transfer of
> 'icetransport.pl/IN' from 84.10.41.58#53: Transfer status: host
> unreachable
> May 22 20:50:55 <3.6> puchar named[67338]: transfer of
> 'icetransport.pl/IN' from 84.10.41.58#53: Transfer completed: 0 messages,
> 0 recor
>
>
> while on 84.10.41.58 i see
>
> May 22 20:50:51 icetransport named[4479]: client @0x3bc271400
> 194.1.144.90#44228 (icetransport.pl): transfer of 'icetransport.pl/IN':
> AXFR started (serial 3873)
> May 22 20:50:51 icetransport named[4479]: client @0x3bc271400
> 194.1.144.90#44228 (icetransport.pl): transfer of 'icetransport.pl/IN':
> AXFR ended
> May 22 20:50:51 icetransport named[4479]: client @0x3c0129400
> 194.1.144.90#44231 (icetransport.pl): transfer of 'icetransport.pl/IN':
> AXFR started (serial 3873)
> May 22 20:50:51 icetransport named[4479]: client @0x3c0129400
> 194.1.144.90#44231 (icetransport.pl): transfer of 'icetransport.pl/IN':
> AXFR ended
>
>
> using FreeBSD base system host program i can transfer this domain without
> problem too.
>
>
> this way named now cannot update any of domains from master server.
>
> furthermore i see LOTS of things like this in log:
>
> May 22 20:51:10 <3.3> puchar named[67338]: dispatch 0x804544e00: shutting
> down due to TCP receive error: 193.108.91.73#53: host unreachable
>
>
>
> seems like named connect properly over tcp and then reports error.
>
> Any idea what's this and how to fix it?
>

Looks to me like either a firewall or policy issue, not BIND.

Back a decade ago, many firewalls defaulted to blocking tcp/53. This was
based on the unfortunate decision to list the use of tcp/53 as "SHOULD" in
the RFC instead of "MUST", but this should produce a timeout,not a host
unreachable. "host unreachable" is should be the result of an ICMP message
coming back from a router.

Take a look at the traffic with tcpdump or wireshark and see if you are
getting no response (firewall) or an ICMP Host Unreachable. If the latter,
it is coming from a router between you and Akamai and is the result of
policy; most likely of your ISP. In neither case is you local BIND at
fault. Historically ISPs have loved to play rude games with DNS, either
deliberately or due to software flaws in things like load balancers.
--
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"

FIXED Re: problem with bind911 or 914

[Wojciech Puchar]

net.inet.tcp.soreceive_stream=1 was the problem. turning it off fixed 
things



On Wed, 22 May 2019, Wojciech Puchar wrote:

i've reinstalled bind914 (and then tried 911 too) after updating to latest 
FreeBSD-11


and the problem is that bind cannot perform any TCP transfers

in logs i'm getting like this

May 22 20:50:55 <3.6> puchar named[67338]: transfer of 'icetransport.pl/IN' 
from 84.10.41.58#53: connected using 194.1.144.90#44228
May 22 20:50:55 <3.3> puchar named[67338]: transfer of 'icetransport.pl/IN' 
from 84.10.41.58#53: failed while receiving responses: host
May 22 20:50:55 <3.6> puchar named[67338]: transfer of 'icetransport.pl/IN' 
from 84.10.41.58#53: Transfer status: host unreachable
May 22 20:50:55 <3.6> puchar named[67338]: transfer of 'icetransport.pl/IN' 
from 84.10.41.58#53: Transfer completed: 0 messages, 0 recor



while on 84.10.41.58 i see

May 22 20:50:51 icetransport named[4479]: client @0x3bc271400 
194.1.144.90#44228 (icetransport.pl): transfer of 'icetransport.pl/IN': AXFR 
started (serial 3873)
May 22 20:50:51 icetransport named[4479]: client @0x3bc271400 
194.1.144.90#44228 (icetransport.pl): transfer of 'icetransport.pl/IN': AXFR 
ended
May 22 20:50:51 icetransport named[4479]: client @0x3c0129400 
194.1.144.90#44231 (icetransport.pl): transfer of 'icetransport.pl/IN': AXFR 
started (serial 3873)
May 22 20:50:51 icetransport named[4479]: client @0x3c0129400 
194.1.144.90#44231 (icetransport.pl): transfer of 'icetransport.pl/IN': AXFR 
ended



using FreeBSD base system host program i can transfer this domain without 
problem too.



this way named now cannot update any of domains from master server.

furthermore i see LOTS of things like this in log:

May 22 20:51:10 <3.3> puchar named[67338]: dispatch 0x804544e00: shutting 
down due to TCP receive error: 193.108.91.73#53: host unreachable




seems like named connect properly over tcp and then reports error.

Any idea what's this and how to fix 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"



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

problem with bind911 or 914

[Wojciech Puchar]

i've reinstalled bind914 (and then tried 911 too) after updating to latest 
FreeBSD-11


and the problem is that bind cannot perform any TCP transfers

in logs i'm getting like this

May 22 20:50:55 <3.6> puchar named[67338]: transfer of 
'icetransport.pl/IN' from 84.10.41.58#53: connected using 
194.1.144.90#44228
May 22 20:50:55 <3.3> puchar named[67338]: transfer of 
'icetransport.pl/IN' from 84.10.41.58#53: failed while receiving 
responses: host
May 22 20:50:55 <3.6> puchar named[67338]: transfer of 
'icetransport.pl/IN' from 84.10.41.58#53: Transfer status: host 
unreachable
May 22 20:50:55 <3.6> puchar named[67338]: transfer of 
'icetransport.pl/IN' from 84.10.41.58#53: Transfer completed: 0 messages, 
0 recor



while on 84.10.41.58 i see

May 22 20:50:51 icetransport named[4479]: client @0x3bc271400 
194.1.144.90#44228 (icetransport.pl): transfer of 'icetransport.pl/IN': 
AXFR started (serial 3873)
May 22 20:50:51 icetransport named[4479]: client @0x3bc271400 
194.1.144.90#44228 (icetransport.pl): transfer of 'icetransport.pl/IN': 
AXFR ended
May 22 20:50:51 icetransport named[4479]: client @0x3c0129400 
194.1.144.90#44231 (icetransport.pl): transfer of 'icetransport.pl/IN': 
AXFR started (serial 3873)
May 22 20:50:51 icetransport named[4479]: client @0x3c0129400 
194.1.144.90#44231 (icetransport.pl): transfer of 'icetransport.pl/IN': 
AXFR ended



using FreeBSD base system host program i can transfer this domain without 
problem too.



this way named now cannot update any of domains from master server.

furthermore i see LOTS of things like this in log:

May 22 20:51:10 <3.3> puchar named[67338]: dispatch 0x804544e00: shutting down 
due to TCP receive error: 193.108.91.73#53: host unreachable



seems like named connect properly over tcp and then reports error.

Any idea what's this and how to fix 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"

pkg query hackaton

[Grzegorz Junka]

Hi,

I am interested in two pkg query solutions and I thought I will ask here 
first, maybe someone already spend time or knows a better approach.


1. List of packages sorted by the amount of packages that depend on them

2. List of all recursive dependencies of a particular package


Ad1. Basically, it would be a list of all packages installed in the 
system where for each package the query would retrieve the amount of 
dependent packages. Then sort that list.


Bonus. Can 1. be also recursively, e.g. sum amounts of all dependent 
packages, then for each dependent package add that package's dependent 
packages, etc. This will likely cause loops so probably a state with 
packages already added would need to be maintained.


Ad2. Given package A list all its direct dependencies, then for each 
dependency list its dependencies, and so on. Add them to a big list then 
sort and unique. Can that be done in pkg query alone?



Out of interest, is "pkg install -R" truly recursive, i.e. would it 
reinstall any packages that require the given package indirectly 
(through another package, not through a direct dependency)?


GrzegorzJ


___
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: Reinstalling with dependencies

[Grzegorz Junka]

On 22/05/2019 13:48, Grzegorz Junka wrote:


On 22/05/2019 13:42, Miroslav Lachman wrote:

Grzegorz Junka wrote on 2019/05/22 14:11:

[...]

Are you saying that even if elinks was reinstalled with dependencies 
that wouldn't help?


We have two issues here:

1. How to reinstall a package with dependencies (as stated in the 
subject)


You can try something like this

pkg install -f `pkg info -d elinks | tr -d :`


pkg info -d will list direct dependencies of the port and then this 
list is given to command pkg install -f.




That's a good idea. Thank you. I may probably want to strip versions 
too, to allow upgrading to more recent versions. But I can take it 
from there.




However, I just realized that it may not be enough, i.e. pkg info -d 
lists only direct dependencies, so this would allow me to reinstall all 
direct dependencies but not recursively.


Adding a loop in bash or something is another solution but it starts to 
become clunky.



___
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: Reinstalling with dependencies

[Grzegorz Junka]

On 22/05/2019 13:42, Miroslav Lachman wrote:

Grzegorz Junka wrote on 2019/05/22 14:11:

[...]

Are you saying that even if elinks was reinstalled with dependencies 
that wouldn't help?


We have two issues here:

1. How to reinstall a package with dependencies (as stated in the 
subject)


You can try something like this

pkg install -f `pkg info -d elinks | tr -d :`


pkg info -d will list direct dependencies of the port and then this 
list is given to command pkg install -f.




That's a good idea. Thank you. I may probably want to strip versions 
too, to allow upgrading to more recent versions. But I can take it from 
there.


GrzegorzJ

___
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: Reinstalling with dependencies

[Miroslav Lachman]

Grzegorz Junka wrote on 2019/05/22 14:11:

[...]

Are you saying that even if elinks was reinstalled with dependencies 
that wouldn't help?


We have two issues here:

1. How to reinstall a package with dependencies (as stated in the subject)


You can try something like this

pkg install -f `pkg info -d elinks | tr -d :`


pkg info -d will list direct dependencies of the port and then this list 
is given to command pkg install -f.


Miroslav Lachman
___
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: pkg upgrade -f dying on me

[Grzegorz Junka]

On 22/05/2019 13:30, Mark Martinec wrote:

2019-05-22 13:46, je Grzegorz Junka wrote:

root@someserv:~ # pkg --version
1.10.5
root@someserv:~ # /usr/local/sbin/pkg-static upgrade -f
Updating desktop_nvidia repository catalogue...
desktop_nvidia repository is up to date.
All repositories are up to date.
Checking for upgrades (1637 candidates):  46%
libwps03 has no direct installation candidates, change it to libwps? 
[Y/n]:

Checking for upgrades (1637 candidates):  81%
gmime26 has no direct installation candidates, change it to gmime30? 
[Y/n]:

Checking for upgrades (1637 candidates):  82%
glib12 has no direct installation candidates, change it to glib? [Y/n]:
Checking for upgrades (1637 candidates): 100%
Processing candidates (1637 candidates): 100%
Child process pid=4192 terminated abnormally: Segmentation fault


This has been my experience (mostly) ever since pkg-ng was introduced.
When answering Y to such questions, it is very likely it will crash.

My 'solution' is not to accept any of the offered changes, but
just to delete the defunct packages, do the pkg upgrade, then
install whatever is still needed.



Great, thank you Mark. That worked!

GrzegorzJ

___
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 lang/phantomjs [deprecated]

[Andrea Venturoli]

On 2019-05-22 14:29, Miroslav Lachman wrote:

Steven Hartland wrote on 2019/05/22 13:56:

Pretty sure chrome has a headless mode now, perhaps you could use that.


The last time I tried chrome headless it was so big beast (for headless 
servers) that I abandoned it.

True, but I'm using it nonetheless.




Build time in my poudriere was about 33 hours


8 hours here, but only if I use a single core for it...



> and so many dependencies I don't want to install in headless

I agree again... love it or leave it, however.




So I hope there is still some chance to find something lighter 
than headless chrome.


Firefox should work (although it's only a little lighter then Chromium), 
but I was not able to make it work at first try, so I gave up.




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

Re: pkg upgrade -f dying on me

[Mark Martinec]

2019-05-22 13:46, je Grzegorz Junka wrote:

root@someserv:~ # pkg --version
1.10.5
root@someserv:~ # /usr/local/sbin/pkg-static upgrade -f
Updating desktop_nvidia repository catalogue...
desktop_nvidia repository is up to date.
All repositories are up to date.
Checking for upgrades (1637 candidates):  46%
libwps03 has no direct installation candidates, change it to libwps? 
[Y/n]:

Checking for upgrades (1637 candidates):  81%
gmime26 has no direct installation candidates, change it to gmime30? 
[Y/n]:

Checking for upgrades (1637 candidates):  82%
glib12 has no direct installation candidates, change it to glib? [Y/n]:
Checking for upgrades (1637 candidates): 100%
Processing candidates (1637 candidates): 100%
Child process pid=4192 terminated abnormally: Segmentation fault


This has been my experience (mostly) ever since pkg-ng was introduced.
When answering Y to such questions, it is very likely it will crash.

My 'solution' is not to accept any of the offered changes, but
just to delete the defunct packages, do the pkg upgrade, then
install whatever is still needed.

  Mark
___
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 lang/phantomjs [deprecated]

[Miroslav Lachman]

Steven Hartland wrote on 2019/05/22 13:56:

Pretty sure chrome has a headless mode now, perhaps you could use that.


The last time I tried chrome headless it was so big beast (for headless 
servers) that I abandoned it. Build time in my poudriere was about 33 
hours and so many dependencies I don't want to install in headless 
machines. So I hope there is still some chance to find something lighter 
than headless chrome.


Miroslav Lachman

___
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: Reinstalling with dependencies

[Grzegorz Junka]

On 22/05/2019 13:17, Baptiste Daroussin wrote:

On Wed, May 22, 2019 at 01:11:05PM +0100, Grzegorz Junka wrote:

On 22/05/2019 12:51, Baptiste Daroussin wrote:

On Wed, May 22, 2019 at 12:43:33PM +0100, Grzegorz Junka wrote:

Is there any way to reinstall a package with all its dependencies?


I am getting the following error:

root@someserv:~ # pkg check -d
Checking all packages: 100%
elinks is missing a required shared library: libjs.so



2 reasons may happen for that to happen:
1/ spidermonkey17 does not have a proper SONAME for the libjs.so file it
provides (bug 1)
2/ somehow the linked port seems to not register properly spidermonkey17 as a
direct dependency of elinks when the option is checked (bug 2)

I have checked the case 1 and yes libjs.so is buggy I haven't yet checked the
case 2, but I quite sure there is a bug there as well, resulting in a package
that does not have the proper dependencies registered at the creation

Best regards,
Bapt


Are you saying that even if elinks was reinstalled with dependencies that
wouldn't help?

We have two issues here:

1. How to reinstall a package with dependencies (as stated in the subject)

2. Would reinstalling elinks with all dependencies fix the issue mentioned
in the email

I have a couple more packages broken like elinks. I didn't include them
because I only wanted to post an example and assumed they would be fixed if
I reinstalled them properly. But here we go:

No I do mean the elinks packages is probably broken when build with the option
that brings in spidermonkey as a dependency

root@someserv:~ # pkg check -d
Checking all packages: 100%
elinks is missing a required shared library: libjs.so
fireflies is missing a required shared library: libgfx.so
py27-exiv2 is missing a required shared library: libexiv2.so.26

There was also virtuoso but I deinstalled it assuming it's an old version
(the new version doesn't build due to openssl 1.1.0 issue).

So now I have two questions: Is it possible to reinstall a package with it's
dependencies? And what to do with those broken packages above, should I
report a bug?


I don't know for the specific case of the broken packages above, pkg check will
try to reinstall the missing dependency if any is found. If not, it just report
the broken packages and one has to figure out why those packages are broken.

I could easily guess for the elinks case. there might be similar reasons for
other packages.

For example reading at the MOVED file I can easily figure out that py27-exiv2 is
a package that no longer exists.

For fireflies I don't know, one has to check.



Thanks Bapt.  From what you wrote I infer that an option to reinstall a 
package with all dependencies doesn't exist, e.g.


pkg install -D pkg-name (Force reinstallation of package dependencies if 
already installed)


I will raise a bug for elinks when I am done with upgrading packages.


___
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: Reinstalling with dependencies

[Baptiste Daroussin]

On Wed, May 22, 2019 at 01:11:05PM +0100, Grzegorz Junka wrote:
> 
> On 22/05/2019 12:51, Baptiste Daroussin wrote:
> > On Wed, May 22, 2019 at 12:43:33PM +0100, Grzegorz Junka wrote:
> > > Is there any way to reinstall a package with all its dependencies?
> > > 
> > > 
> > > I am getting the following error:
> > > 
> > > root@someserv:~ # pkg check -d
> > > Checking all packages: 100%
> > > elinks is missing a required shared library: libjs.so
> > > 
> > > 
> > 2 reasons may happen for that to happen:
> > 1/ spidermonkey17 does not have a proper SONAME for the libjs.so file it
> > provides (bug 1)
> > 2/ somehow the linked port seems to not register properly spidermonkey17 as 
> > a
> > direct dependency of elinks when the option is checked (bug 2)
> > 
> > I have checked the case 1 and yes libjs.so is buggy I haven't yet checked 
> > the
> > case 2, but I quite sure there is a bug there as well, resulting in a 
> > package
> > that does not have the proper dependencies registered at the creation
> > 
> > Best regards,
> > Bapt
> 
> 
> Are you saying that even if elinks was reinstalled with dependencies that
> wouldn't help?
> 
> We have two issues here:
> 
> 1. How to reinstall a package with dependencies (as stated in the subject)
> 
> 2. Would reinstalling elinks with all dependencies fix the issue mentioned
> in the email
> 
> I have a couple more packages broken like elinks. I didn't include them
> because I only wanted to post an example and assumed they would be fixed if
> I reinstalled them properly. But here we go:

No I do mean the elinks packages is probably broken when build with the option
that brings in spidermonkey as a dependency
> 
> root@someserv:~ # pkg check -d
> Checking all packages: 100%
> elinks is missing a required shared library: libjs.so
> fireflies is missing a required shared library: libgfx.so
> py27-exiv2 is missing a required shared library: libexiv2.so.26
> 
> There was also virtuoso but I deinstalled it assuming it's an old version
> (the new version doesn't build due to openssl 1.1.0 issue).
> 
> So now I have two questions: Is it possible to reinstall a package with it's
> dependencies? And what to do with those broken packages above, should I
> report a bug?


I don't know for the specific case of the broken packages above, pkg check will
try to reinstall the missing dependency if any is found. If not, it just report
the broken packages and one has to figure out why those packages are broken.

I could easily guess for the elinks case. there might be similar reasons for
other packages.

For example reading at the MOVED file I can easily figure out that py27-exiv2 is
a package that no longer exists.

For fireflies I don't know, one has to check.

Best regards,
Bapt


signature.asc
Description: PGP signature

Re: Reinstalling with dependencies

[Grzegorz Junka]

On 22/05/2019 12:51, Baptiste Daroussin wrote:

On Wed, May 22, 2019 at 12:43:33PM +0100, Grzegorz Junka wrote:

Is there any way to reinstall a package with all its dependencies?


I am getting the following error:

root@someserv:~ # pkg check -d
Checking all packages: 100%
elinks is missing a required shared library: libjs.so



2 reasons may happen for that to happen:
1/ spidermonkey17 does not have a proper SONAME for the libjs.so file it
provides (bug 1)
2/ somehow the linked port seems to not register properly spidermonkey17 as a
direct dependency of elinks when the option is checked (bug 2)

I have checked the case 1 and yes libjs.so is buggy I haven't yet checked the
case 2, but I quite sure there is a bug there as well, resulting in a package
that does not have the proper dependencies registered at the creation

Best regards,
Bapt



Are you saying that even if elinks was reinstalled with dependencies 
that wouldn't help?


We have two issues here:

1. How to reinstall a package with dependencies (as stated in the subject)

2. Would reinstalling elinks with all dependencies fix the issue 
mentioned in the email


I have a couple more packages broken like elinks. I didn't include them 
because I only wanted to post an example and assumed they would be fixed 
if I reinstalled them properly. But here we go:


root@someserv:~ # pkg check -d
Checking all packages: 100%
elinks is missing a required shared library: libjs.so
fireflies is missing a required shared library: libgfx.so
py27-exiv2 is missing a required shared library: libexiv2.so.26

There was also virtuoso but I deinstalled it assuming it's an old 
version (the new version doesn't build due to openssl 1.1.0 issue).


So now I have two questions: Is it possible to reinstall a package with 
it's dependencies? And what to do with those broken packages above, 
should I report a bug?


___
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 lang/phantomjs [deprecated]

[Steven Hartland]

Pretty sure chrome has a headless mode now, perhaps you could use that.

On 22/05/2019 12:39, dangerwillrobinsondan...@gmail.com wrote:





On May 22, 2019, at 19:33, Kurt Jaeger  wrote:

Hi!


The port lang/phantomjs is marked as deprecated / expired 2019-05-15. Is
there any alternative in the ports tree? I searched the net and found
https://slimerjs.org but it is not in the ports tree. (I don't have a
skill to port it and maintain it myself)

One of my clients is using phantomjs thru some webapplication so I need
to find some replacement.

I have a vague guess that selenium does something similar.

https://docs.seleniumhq.org/

Not really.
phantomjs is like a headless browser client.
Selenium is web automation API and now a W3C standard implemented by browsers 
to support it. Version 3+
Earlier versions worked with older browsers via plugins or extensions but no 
more, in part due to security issues and in part because W3C.

PhantomJS was often like a generic browser space you could test inside of and 
it did have Selenium bindings.


--
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

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


___
freebsd-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: Reinstalling with dependencies

[Baptiste Daroussin]

On Wed, May 22, 2019 at 12:43:33PM +0100, Grzegorz Junka wrote:
> Is there any way to reinstall a package with all its dependencies?
> 
> 
> I am getting the following error:
> 
> root@someserv:~ # pkg check -d
> Checking all packages: 100%
> elinks is missing a required shared library: libjs.so
> 
> 

2 reasons may happen for that to happen:
1/ spidermonkey17 does not have a proper SONAME for the libjs.so file it
provides (bug 1)
2/ somehow the linked port seems to not register properly spidermonkey17 as a
direct dependency of elinks when the option is checked (bug 2)

I have checked the case 1 and yes libjs.so is buggy I haven't yet checked the
case 2, but I quite sure there is a bug there as well, resulting in a package
that does not have the proper dependencies registered at the creation

Best regards,
Bapt


signature.asc
Description: PGP signature

Re: pkg upgrade -f dying on me

[Grzegorz Junka]

On 22/05/2019 12:03, Kurt Jaeger wrote:

Hi!


How to debug this?:

root@someserv:~ # pkg upgrade -f

Which version of pkg ?

pkg --version

Try:

/usr/local/sbin/pkg-static upgrade -f



root@someserv:~ # pkg --version
1.10.5
root@someserv:~ # /usr/local/sbin/pkg-static upgrade -f
Updating desktop_nvidia repository catalogue...
desktop_nvidia repository is up to date.
All repositories are up to date.
Checking for upgrades (1637 candidates):  46%
libwps03 has no direct installation candidates, change it to libwps? [Y/n]:
Checking for upgrades (1637 candidates):  81%
gmime26 has no direct installation candidates, change it to gmime30? [Y/n]:
Checking for upgrades (1637 candidates):  82%
glib12 has no direct installation candidates, change it to glib? [Y/n]:
Checking for upgrades (1637 candidates): 100%
Processing candidates (1637 candidates): 100%
Child process pid=4192 terminated abnormally: Segmentation fault

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

Reinstalling with dependencies

[Grzegorz Junka]

Is there any way to reinstall a package with all its dependencies?


I am getting the following error:

root@someserv:~ # pkg check -d
Checking all packages: 100%
elinks is missing a required shared library: libjs.so


But reinstalling elinks doesn't help:


root@someserv:~ # pkg install -fR elinks
Updating desktop_nvidia repository catalogue...
desktop_nvidia repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
    elinks-0.11.7_11

Number of packages to be reinstalled: 1

Proceed with this action? [y/N]: y
[1/1] Reinstalling elinks-0.11.7_11...
[1/1] Extracting elinks-0.11.7_11: 100%


After that same error is shown.

___
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 lang/phantomjs [deprecated]

[dangerwillrobinsondanger]

> On May 22, 2019, at 19:33, Kurt Jaeger  wrote:
> 
> Hi!
> 
>> The port lang/phantomjs is marked as deprecated / expired 2019-05-15. Is
>> there any alternative in the ports tree? I searched the net and found
>> https://slimerjs.org but it is not in the ports tree. (I don't have a
>> skill to port it and maintain it myself)
>> 
>> One of my clients is using phantomjs thru some webapplication so I need
>> to find some replacement.
> 
> I have a vague guess that selenium does something similar.
> 
> https://docs.seleniumhq.org/

Not really. 
phantomjs is like a headless browser client. 
Selenium is web automation API and now a W3C standard implemented by browsers 
to support it. Version 3+
Earlier versions worked with older browsers via plugins or extensions but no 
more, in part due to security issues and in part because W3C. 

PhantomJS was often like a generic browser space you could test inside of and 
it did have Selenium bindings. 

> 
> -- 
> p...@opsec.eu+49 171 3101372One year to go !
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-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: pkg upgrade -f dying on me

[Kurt Jaeger]

Hi!

> How to debug this?:
> 
> root@someserv:~ # pkg upgrade -f

Which version of pkg ?

pkg --version

Try:

/usr/local/sbin/pkg-static upgrade -f

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
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"

pkg upgrade -f dying on me

[Grzegorz Junka]

Hi,

How to debug this?:

root@someserv:~ # pkg upgrade -f
Updating desktop_nvidia repository catalogue...
desktop_nvidia repository is up to date.
All repositories are up to date.
Checking for upgrades (1638 candidates):  46%
libwps03 has no direct installation candidates, change it to libwps? [Y/n]:
Checking for upgrades (1638 candidates):  81%
gmime26 has no direct installation candidates, change it to gmime30? [Y/n]:
Checking for upgrades (1638 candidates):  82%
glib12 has no direct installation candidates, change it to glib? [Y/n]:
Checking for upgrades (1638 candidates): 100%
Processing candidates (1638 candidates): 100%
Child process pid=3850 terminated abnormally: Segmentation fault


___
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 lang/phantomjs [deprecated]

[Kurt Jaeger]

Hi!

> The port lang/phantomjs is marked as deprecated / expired 2019-05-15. Is
> there any alternative in the ports tree? I searched the net and found
> https://slimerjs.org but it is not in the ports tree. (I don't have a
> skill to port it and maintain it myself)
> 
> One of my clients is using phantomjs thru some webapplication so I need
> to find some replacement.

I have a vague guess that selenium does something similar.

https://docs.seleniumhq.org/

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
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: graphics/php*-gd requires X11 by default

[Miroslav Lachman]

Greg Kennedy wrote on 2019/05/22 05:07:

Never mind!  I just saw that this was fixed in October for php73-gd.  Need
to update my PHP version.


I think all supported versions of PHP should have the same options 
enabled. And I support X11=off by default.




On Thu, May 16, 2019 at 8:54 PM Greg Kennedy  wrote:


I'm raising this again as the last time I tried to check with the port
maintainer, he had not made the change, and wasn't available to do so.

Can someone change the default config for graphics/php72-gd from X11=on to
X11=off?

It will save a large number of dependencies on X11, at the cost of not
supporting this (very rarely used) image format.

On Sat, Sep 15, 2018 at 12:14 PM Greg Kennedy 
wrote:


I sent an email to the maintainer of these ports (t...@freebsd.org) a few
days ago, but didn't hear back - so I thought I'd raise the same question
to the mailing list instead.

---

Hey there!  I was wondering something about the php-gd ports
(specifically 7.2 but earlier as well).  Looking at the config options
I see this:

  X11=on: Enable XPM support

With this option enabled php-gd can read XPixMap images, but in turn
this pulls in a host of additional X11 dependencies.  That's an awful
lot for (usually) headless servers, especially for an image format
that is (relatively) unused.  I don't mind the option being there but
because it is defaulted to "on", that means official FreeBSD packages
are built with this support and all the dependencies.  On my system I
have to manually build this one port just to turn off the option.

Would it be possible to modify the defaults for this port so that
X11=off by default?  Or, why is the default to "on"?  (I have a guess,
that this respects WITHOUT_X11 in /etc/make.conf, but that's useless
for pre-built binary packages)

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

replacement for lang/phantomjs [deprecated]

[Miroslav Lachman]

The port lang/phantomjs is marked as deprecated / expired 2019-05-15. Is 
there any alternative in the ports tree? I searched the net and found 
https://slimerjs.org but it is not in the ports tree. (I don't have a 
skill to port it and maintain it myself)


One of my clients is using phantomjs thru some webapplication so I need 
to find some replacement.


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

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
databases/ip4r  | 2.2 | 2.4.1
+-+
devel/grpc  | 1.15.1  | v1.21.0
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

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