Re: Could a committer please take a look at this?

[Lacey Powers]

On 08/11/2017 02:27 AM, Kurt Jaeger wrote:
> 9 171 3101372 3 years to go !

Noted. Sorry about that. I'll be sure to do that in the future, even if
I'm sending late-night emails. =)

And thank you for your help with this. Very much appreciated.

Best,

Lacey

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

[Bug 1898] [packages-current]jp-ghostscript300-2.6 is not in packages-current

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=1898

richkinds  changed:

   What|Removed |Added

 CC||nim...@duck2.club

--- Comment #2 from richkinds  ---
I just built it and put it on the ftp site.

check:

https://allowlive.com/floyd-mayweather-vs-conor-mcgregor-live-stream/

-- 
You are receiving this mail because:
You are the assignee for the 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: pkg issue after FreeBSD 11 upgrade

[Cassiano Peixoto]

Hi Matthew,

Thanks for your answer. Slapd is just an example, it happens with any
application like apache, mysql, dovecot and others.

I can see the process is running and up, and it dies after pkg process has
finished. Looks like pkg is killing any application related to its thread.

I know it's not the best approach, but used to work on FreeBSD 10.

Anyway, I'll change my script to restart services out of pkg process.

Thanks.

On Fri, Aug 11, 2017 at 5:09 AM, Matthew Seaman  wrote:

> On 10/08/2017 22:05, Cassiano Peixoto wrote:
> > I ran into an issue after FreeBSD 11 upgrade. I have some meta ports that
> > starts services like slapd.
> >
> > Its has been working fine on 10-STABLE. But after FreeBSD
> > 11-STABLE r321625M upgrade it stopped working.
> >
> > Here is a simple example of my pkg-install.in script:
> >
> > #!/bin/sh
> > /usr/local/etc/rc.d/slapd stop
> > /usr/local/etc/rc.d/slapd start
> >
> > I can see its executing while upgrading a package:
> >
> > Stopping slapd.
> > Waiting for PIDS: 13875.
> > Starting slapd.
> >
> > But looking if the process is running, it's not:
> >
> > # ps ax | grep slapd
> > 14164  0  S+ 0:00.00 grep slapd
> >
> > Then I manually run the rc.d script and the service starts:
> >
> > # /usr/local/etc/rc.d/slapd restart
> > slapd not running? (check /var/run/openldap/slapd.pid).
> > Starting slapd.
> >
> > So my question is: something has changed on FreeBSD 11 not allowing this
> > kind of execution?
> >
> > BTW, I'm using pkg 1.10.1 and my ports collection is as same as I was
> using
> > on FreeBSD 10.
>
> Restarting daemons after upgrading is something the project has been
> quite resistant to implementing.  Mostly because as soon as you start
> looking into it in any depth the true complexity of doing that sort of
> thing reliably for any conceivable system becomes apparent and you end
> up muttering darkly about systemd and losing the will to live.
>
> However, yes, restarting slapd -- it's clear that your script does get
> called, but slapd fails to start at that point during the upgrade
> process.  slapd is well known (at least to me) for failing to start
> /silently/ -- you need to check the process is actually there after
> trying to start it, and look at the logfiles and so forth.  It also
> seems to quit at the slightest provocation, presumably to avoid any
> potential for data corruption.
>
> So check you logs to see why slapd didn't start.  It's quite possible
> that it was simply that something else that slapd needed wasn't
> available at that exact point during the upgrade process, and just
> waiting until the upgrade had finished would sort things out.
>
> Cheers,
>
> Matthew
>
>
___
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 the net/ceph-devel port

[Kurt Jaeger]

Hi!

> >> Would somebody please take a look at the the update at:
> >>https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218974
> > 
> > That PR is already committed and closed.
> 
> Ah, sorry, That was the original commit, I picked the wrong one from my
> archived mails. It should have read:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221063

Ah, oh!

> >> It also went by phabricator:
> >>https://reviews.freebsd.org/D11770
> > 
> > That's a new patch, I assume ?
> 
> Yup, it should be equal to waht is in Bugzilla under 221063.

So, all that is now sorted out 8-) Thanks!

-- 
p...@opsec.eu+49 171 3101372 3 years 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: Updating the net/ceph-devel port

[Willem Jan Withagen]

On 11-8-2017 15:30, Kurt Jaeger wrote:
> Hi!
> 
>> Would somebody please take a look at the the update at:
>>https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218974
> 
> That PR is already committed and closed.

Ah, sorry, That was the original commit, I picked the wrong one from my
archived mails.
It should have read:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221063

>> It also went by phabricator:
>>https://reviews.freebsd.org/D11770
> 
> That's a new patch, I assume ?

Yup, it should be equal to waht is in Bugzilla under 221063.

--WjW




___
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 the net/ceph-devel port

[Kurt Jaeger]

Hi!

> > > It also went by phabricator:
> > >https://reviews.freebsd.org/D11770

> > That's a new patch, I assume ?

> It is, I just had a look. So, the best way would be
> to open a new PR, point to the review and ask for someone
> to commit it.

So, that hit the tree a few seconds ago.

Thanks!

-- 
p...@opsec.eu+49 171 3101372 3 years 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: Updating the net/ceph-devel port

[Kurt Jaeger]

Hi!

> > Would somebody please take a look at the the update at:
> >https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218974
> 
> That PR is already committed and closed.
> 
> > It also went by phabricator:
> >https://reviews.freebsd.org/D11770
> 
> That's a new patch, I assume ?

It is, I just had a look. So, the best way would be
to open a new PR, point to the review and ask for someone
to commit it.

I'm testbuilding it right now, even without a PR...

-- 
p...@opsec.eu+49 171 3101372 3 years 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: Updating the net/ceph-devel port

[Kurt Jaeger]

Hi!

> Would somebody please take a look at the the update at:
>https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218974

That PR is already committed and closed.

> It also went by phabricator:
>https://reviews.freebsd.org/D11770

That's a new patch, I assume ?

-- 
p...@opsec.eu+49 171 3101372 3 years 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"

Updating the net/ceph-devel port

[Willem Jan Withagen]

Hi,

Would somebody please take a look at the the update at:
   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218974

It also went by phabricator:
   https://reviews.freebsd.org/D11770

--WjW
___
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: oniguruma5-5.9.6_1 is vulnerable

[Kurt Jaeger]

Hi!

> For some weeks I noticed
> 
> oniguruma5-5.9.6_1 is vulnerable:
> oniguruma -- multiple vulnerabilities
> CVE: CVE-2017-9228
> CVE: CVE-2017-9228
> CVE: CVE-2017-9227
> CVE: CVE-2017-9226
> CVE: CVE-2017-9224
> WWW:https://vuxml.FreeBSD.org/freebsd/b396cf6c-62e6-11e7-9def-b499baebfeaf.html
> 
> Can you please provide a port update? Thanks.

Basically, the suggestion is to update dependent ports to oniguruma6,
and then remove oniguruma5. See

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220438

for more details. That's a little bit of work and we're short
on folks doing it 8-}

-- 
p...@opsec.eu+49 171 3101372 3 years 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"

oniguruma5-5.9.6_1 is vulnerable

[Jos Chrispijn]

Dear port maintainer,

For some weeks I noticed

oniguruma5-5.9.6_1 is vulnerable:
oniguruma -- multiple vulnerabilities
CVE: CVE-2017-9228
CVE: CVE-2017-9228
CVE: CVE-2017-9227
CVE: CVE-2017-9226
CVE: CVE-2017-9224
WWW:https://vuxml.FreeBSD.org/freebsd/b396cf6c-62e6-11e7-9def-b499baebfeaf.html

Can you please provide a port update? Thanks.

Keep up the good work,
Jos Chrispijn

___
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: Could a committer please take a look at this?

[Kurt Jaeger]

Hi!

> As said in the subject, could someone please take a look at this?
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214417
> 
> I would really appreciate it. =)

Done. Please note: Adding the title of the PR in postings
on -ports@ helps to understand the context.

-- 
p...@opsec.eu+49 171 3101372 3 years 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"

Could a committer please take a look at this?

[Lacey Powers]

Hello,

As said in the subject, could someone please take a look at this?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214417

I would really appreciate it. =)

Best,

Lacey

___
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
+-+
devel/py-jep| 3.6.4   | 3.7.0
+-+
multimedia/obs-studio   | 19.0.3  | 20.0.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"

Re: pkg issue after FreeBSD 11 upgrade

[Matthew Seaman]

On 10/08/2017 22:05, Cassiano Peixoto wrote:
> I ran into an issue after FreeBSD 11 upgrade. I have some meta ports that
> starts services like slapd.
> 
> Its has been working fine on 10-STABLE. But after FreeBSD
> 11-STABLE r321625M upgrade it stopped working.
> 
> Here is a simple example of my pkg-install.in script:
> 
> #!/bin/sh
> /usr/local/etc/rc.d/slapd stop
> /usr/local/etc/rc.d/slapd start
> 
> I can see its executing while upgrading a package:
> 
> Stopping slapd.
> Waiting for PIDS: 13875.
> Starting slapd.
> 
> But looking if the process is running, it's not:
> 
> # ps ax | grep slapd
> 14164  0  S+ 0:00.00 grep slapd
> 
> Then I manually run the rc.d script and the service starts:
> 
> # /usr/local/etc/rc.d/slapd restart
> slapd not running? (check /var/run/openldap/slapd.pid).
> Starting slapd.
> 
> So my question is: something has changed on FreeBSD 11 not allowing this
> kind of execution?
> 
> BTW, I'm using pkg 1.10.1 and my ports collection is as same as I was using
> on FreeBSD 10.

Restarting daemons after upgrading is something the project has been
quite resistant to implementing.  Mostly because as soon as you start
looking into it in any depth the true complexity of doing that sort of
thing reliably for any conceivable system becomes apparent and you end
up muttering darkly about systemd and losing the will to live.

However, yes, restarting slapd -- it's clear that your script does get
called, but slapd fails to start at that point during the upgrade
process.  slapd is well known (at least to me) for failing to start
/silently/ -- you need to check the process is actually there after
trying to start it, and look at the logfiles and so forth.  It also
seems to quit at the slightest provocation, presumably to avoid any
potential for data corruption.

So check you logs to see why slapd didn't start.  It's quite possible
that it was simply that something else that slapd needed wasn't
available at that exact point during the upgrade process, and just
waiting until the upgrade had finished would sort things out.

Cheers,

Matthew



signature.asc
Description: OpenPGP digital signature

Re: Official opinion about new py3- port

[Yasuhiro KIMURA]

Hi Adam.

Thank you for your quick response, and sorry for my late reply.

From: Adam Weinberger 
Subject: Re: Official opinion about new py3- port
Date: Wed, 9 Aug 2017 15:33:42 -0600

> An exception does exist for when a py3 port is a required
> dependency, which it sounds like is the case here. Can you confirm
> that the current ports postfix-policyd-spf-python (1.3.2) fails on
> python 3.6?

Do you mean the issue reported by following PR?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220470

If so, I couldn't reproduce it with my mail server.

I submitted PR to update mail/postfix-policyd-spf-python simply
because I found newer version is released.

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

devel/git fails to install due to pkg-plist disparity

[Thomas Mueller]

Trying to install devel/git on FreeBSD 11.1-STABLE amd64 failed due to two 
files in pkg-plist not being found.

I checked the distfiles (tar tvf) and still didn't find the two files.

I was able to edit pkg-plist to remove the two offending lines, saving the 
official version as pkg-plist.orig.

Then I was successful installing devel/git 2.14.1.

What made me anxious was trying to cross-compile Haiku (haiku-os.org) from 
FreeBSD, and compilation apparently requires git to verify the tags.

This is a rather new installation (FreeBSD 11.1-STABLE), hance I had no 
previous installation of git. 

===>  Installing for git-2.14.1 


===>  Checking if git already installed 


===>   Registering installation for git-2.14.1  


pkg-static: Unable to access file 
/BETA1/usr/ports/devel/git/work11/stage/usr/local/share/doc/git/technical/api-hashmap.html:No
 such file or directory 
 
pkg-static: Unable to access file 
/BETA1/usr/ports/devel/git/work11/stage/usr/local/share/doc/git/technical/api-hashmap.txt:No
 such file or directory 
  
*** Error code 74  

Distfiles in question were

-rw-r--r--   1 root  wheel4791876 Aug 10 17:57 git-2.14.1.tar.xz


-rw-r--r--   1 root  wheel1115176 Aug 10 17:57 git-htmldocs-2.14.1.tar.xz   


-rw-r--r--   1 root  wheel 410400 Aug 10 17:58 git-manpages-2.14.1.tar.xz   
 

Tom

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