Re: www/uchiwa port

[Kurt Jaeger]

Hi!

The port is now in the tree. Thanks for the quick turnaround and fix!

-- 
p...@opsec.eu+49 171 3101372 4 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: www/uchiwa port

[Kurt Jaeger]

Hi!

> I created a new port a few week back;
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210071
> 
> I was wondering if someone with commit access could please take a look and
> see if it's okay to get this into the ports tree.

I had a quick look.

> If any changes needs to be done to have this commit please let me know and
> I will update the port accordingly.

Have you tested it in poudriere ?

The pkg-plist seems to be inconsistent, see those build logs:

http://people.freebsd.org/~pi/logs/www__uchiwa-cur-1467305994.txt
http://people.freebsd.org/~pi/logs/www__uchiwa-93a-1467305994.txt
http://people.freebsd.org/~pi/logs/www__uchiwa-103-1467305994.txt

-- 
p...@opsec.eu+49 171 3101372 4 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: wordpress CLI

[Kubilay Kocak]

On 1/07/2016 1:13 AM, Vick Khera wrote:
> Can I get a commit on 209583
> ? It is a port
> for the wordpress CLI tool.  It has been sitting there for a month and a
> half now with no action whatsoever.
> 
> 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"
> 

Hi Vick

I've triaged the issue and provided some review homework^W feedback as well.

Give me a holler off list if you have any questions or need further
pointers :)

./koobs
___
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"

is USES=ncurses useless?

[Vick Khera]

I've observed (and filed PR 206471
) that the
USES=ncurses flag in a port does not result in the port actually linking
with the ncurses library provided by the port.

Does anyone else notice this? Specifically two ports I've encountered that
have this issue are tmux and tty-clock. They both specify the ncurses from
ports, yet link to base system ncurses library. They register dependencies
against the ncurses port, too, which seems to be the only accomplishment of
this setting.

Full gory details are in the PR linked above. I'd appreciate any comments.
___
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 3.4.5 update

[Kubilay Kocak]

On 1/07/2016 12:07 AM, Rainer Hurling wrote:
> 
> Please keep in mind, that your failed update already deinstalled the old
> python 3.4.4 port, but failed to install the new version. So, at the
> moment, python 3 is probably not installed on your system. You can get
> back the old version by

Would be cool if this was detected, and the deinstall was reverted
___
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"

wordpress CLI

[Vick Khera]

Can I get a commit on 209583
? It is a port
for the wordpress CLI tool.  It has been sitting there for a month and a
half now with no action whatsoever.

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: python 3.4.5 update

[Rainer Hurling]

Am 30.06.16 um 11:02 schrieb Otacílio de Araújo Ramos Neto:

Em qua, 29 de jun de 2016 20:16, Stari Karp  escreveu:




Hi!

I tried to update Python on my
10.3-RELEASE-p5 (akd64) and I got:




ports/lang/python34/work/Python-3.4.5 ./python -E -m
ensurepip  $ensurepip --root=/usr/ports/lang/python34/work/stage/ ;  fi
/bin/rm -f
/usr/ports/lang/python34/work/stage/usr/local/lib/libpython3.so
# Upstream Issue: http://bugs.python.org/issue17975
for i in
/usr/ports/lang/python34/work/stage/usr/local/lib/python3.4/lib-
dynload/*.so; do  /usr/bin/strip $i; done
# Strip shared extensions
> Compressing man pages (compress-man)

===>>> Creating a backup package for old version python34-3.4.4_3
Creating package for python34-3.4.4_3
process with pid 2056 still holds the lock
process with pid 2056 still holds the lock
process with pid 2056 still holds the lock
process with pid 2056 still holds the lock
process with pid 2056 still holds the lock
process with pid 2056 still holds the lock
pkg: Cannot get an advisory lock on a database, it is locked by another
process

===>>> Starting check for runtime dependencies
===>>> Gathering dependency list for lang/python34 from ports
===>>> Dependency check complete for lang/python34

===>>> All >> python34-3.4.4_3 (1/1)

===>  Installing for python34-3.4.5
===>  Checking if python34 already installed
===>   An older version of python34 is already installed (python34-
3.4.4_3)
  You may wish to ``make deinstall'' and install this port again
  by ``make reinstall'' to upgrade it properly.
  If you really wish to overwrite the old port of python34
  without deleting it first, set the variable "FORCE_PKG_REGISTER"
  in your environment or the "make install" command line.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/lang/python34
*** Error code 1

Stop.
make: stopped in /usr/ports/lang/python34

===>>> A backup package for python34-3.4.4_3 should
   be located in /usr/ports/packages/portmaster-backup

===>>> Installation of python34-3.4.5 (lang/python34) failed
===>>> Aborting update

===>>> Update for lang/python34 failed
===>>> Aborting update

Thank you very much.

SK



Are you shure that no other process is handling The ports at the same time?
Like doing a query.

[]'S
-Otacilio

As far as I know, portmaster itself has some not yet solved problems 
with ports, escpecially in a mixed system of ports, installed as a 
package by pkg and build from sources.


For me, there are some possible opportunities, to circumstance this 
behaviour:


1) portmaster -m "FORCE_PKG_REGISTER" lang/python34
   [this also does not work in all situations :( ]

2) portmaster lang/perl5 lang/python34
   [(re)installing something like lang/perl5 before should help always ]

3) cd /usr/ports/lang/python34
   make clean && make install

Please keep in mind, that your failed update already deinstalled the old 
python 3.4.4 port, but failed to install the new version. So, at the 
moment, python 3 is probably not installed on your system. You can get 
back the old version by


   pkg add /usr/ports/packages/portmaster-backup/python34-3.4.4_3

as stated by portmasters message.

HTH,
Rainer Hurling


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

www/uchiwa port

[Alexander Holte-Davidsen]

Hi,

I created a new port a few week back;
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210071

I was wondering if someone with commit access could please take a look and
see if it's okay to get this into the ports tree.

If any changes needs to be done to have this commit please let me know and
I will update the port accordingly.

Best regards,
Alexander
___
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/m6811-binutils| 2.15| 2.26.1
+-+
emulators/mame  | 0.166   | mame0175
+-+
emulators/mess  | 0.166   | mame0175
+-+
java/netty  | 3.9.2   | 3.10.6
+-+


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: python 3.4.5 update

[Otacílio de Araújo Ramos Neto]

Em qua, 29 de jun de 2016 20:16, Stari Karp  escreveu:

>
>
> Hi!
>
> I tried to update Python on my
> 10.3-RELEASE-p5 (akd64) and I got:
>
>
> 
> 
> ports/lang/python34/work/Python-3.4.5 ./python -E -m
> ensurepip  $ensurepip --root=/usr/ports/lang/python34/work/stage/ ;  fi
> /bin/rm -f
> /usr/ports/lang/python34/work/stage/usr/local/lib/libpython3.so
> # Upstream Issue: http://bugs.python.org/issue17975
> for i in
> /usr/ports/lang/python34/work/stage/usr/local/lib/python3.4/lib-
> dynload/*.so; do  /usr/bin/strip $i; done
> # Strip shared extensions
> > Compressing man pages (compress-man)
>
> ===>>> Creating a backup package for old version python34-3.4.4_3
> Creating package for python34-3.4.4_3
> process with pid 2056 still holds the lock
> process with pid 2056 still holds the lock
> process with pid 2056 still holds the lock
> process with pid 2056 still holds the lock
> process with pid 2056 still holds the lock
> process with pid 2056 still holds the lock
> pkg: Cannot get an advisory lock on a database, it is locked by another
> process
>
> ===>>> Starting check for runtime dependencies
> ===>>> Gathering dependency list for lang/python34 from ports
> ===>>> Dependency check complete for lang/python34
>
> ===>>> All >> python34-3.4.4_3 (1/1)
>
> ===>  Installing for python34-3.4.5
> ===>  Checking if python34 already installed
> ===>   An older version of python34 is already installed (python34-
> 3.4.4_3)
>   You may wish to ``make deinstall'' and install this port again
>   by ``make reinstall'' to upgrade it properly.
>   If you really wish to overwrite the old port of python34
>   without deleting it first, set the variable "FORCE_PKG_REGISTER"
>   in your environment or the "make install" command line.
> *** Error code 1
>
> Stop.
> make[1]: stopped in /usr/ports/lang/python34
> *** Error code 1
>
> Stop.
> make: stopped in /usr/ports/lang/python34
>
> ===>>> A backup package for python34-3.4.4_3 should
>be located in /usr/ports/packages/portmaster-backup
>
> ===>>> Installation of python34-3.4.5 (lang/python34) failed
> ===>>> Aborting update
>
> ===>>> Update for lang/python34 failed
> ===>>> Aborting update
>
> Thank you very much.
>
> SK
>

Are you shure that no other process is handling The ports at the same time?
Like doing a query.

[]'S
-Otacilio

>
___
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: Is there still broken lang/ruby23 ?

[Kurt Jaeger]

Hi!

> Kazuhiko> Is there still broken lang/ruby23[1]. Or can build in latest
> Kazuhiko> 11.0-* ? 
> 
> Kazuhiko> [1] 
> http://permalink.gmane.org/gmane.os.freebsd.devel.pkg-fallout/294364
> 
> swills> Yes, I haven't looked at it yet, but if you want to take a look, I'd
> swills> welcome patches.
> 
> Could you put the attached two patches into lang/ruby23/files and give
> it a try?

Testbuild on 11a (r302198M) on a loaded host was OK, but make check-plist found

bin/erb

missing. I'll now test poudriere.

-- 
p...@opsec.eu+49 171 3101372 4 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: PRs ready for commit for www/node*

[Bradley T. Hughes]

> On 30 Jun 2016, at 08:28, Kurt Jaeger  wrote:
> 
> Hi!
> 
>> I've got several patches pending for the www/node* ports [...]
> 
>> I'd appreciate help from a willing and able committer to get these
>> in the tree, ideally before the next quarterly branch is cut.
> 
> Done.

Thanks, Kurt. I appreciate it :)

--
Bradley T. Hughes
bradleythug...@fastmail.fm

___
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: PRs ready for commit for www/node*

[Kurt Jaeger]

Hi!

> I've got several patches pending for the www/node* ports [...]

> I'd appreciate help from a willing and able committer to get these
> in the tree, ideally before the next quarterly branch is cut.

Done.

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