FreeBSD unmaintained ports which are currently marked broken

[linimon]

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles.  In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments.  One common problem is that recent versions of
FreeBSD use clang instead of gcc by default.  Another common problem
is that the compiles succeed on the i386 and amd64 architecture
(e.g. the common Intel PC), but fail on one or more of the other
architectures due to assumptions about things such as size of various
types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 8.x/9.x/10.x/-current with target architecture'.)



portname:   archivers/pecl-lzf
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=pecl-lzf


portname:   astro/gpstk
broken because: Distfile size mismatch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=gpstk


portname:   astro/sky2000
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=sky2000


portname:   audio/amb-plugins
broken because: Distfile size mismatch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=amb-plugins


portname:   audio/amrcoder
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=amrcoder


portname:   audio/btc
broken because: Ftp time out
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=btc


portname:   audio/cplay
broken because: Fails to fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=cplay


portname:   audio/linux-genpuid
broken because: Unfetchable
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-genpuid


portname:   audio/musica
broken because: Unfetchable
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=musica


portname:   audio/optimfrog
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=optimfrog


portname:   audio/pecl-id3
broken because: Unfetchable
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=pecl-id3


portname:   audio/pure-audio
broken because: Unfetchable
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=pure-audio


portname:   audio/rsynth
broken because: Unfetchable
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=rsynth


portname:   audio/sonice
broken because: Unfetchable
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=sonice


portname:   audio/sphinx
broken because: Unfetchable
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=sphinx


portname:   benchmarks/fhourstones
broken because: Unfetchable
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=fhourstones


portname:   benchmarks/flops
broken because: Unfetchable
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=flops


portname:   benchmarks/geekbench
broken because: Unfetchable
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=geekbench


portname:   benchmarks/pathload
broken because:

FreeBSD ports which are currently marked broken

[linimon]

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles.  In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments.  One common problem is that recent versions of
FreeBSD use clang instead of gcc by default.  Another common problem
is that the compiles succeed on the i386 and amd64 architecture
(e.g. the common Intel PC), but fail on one or more of the other
architectures due to assumptions about things such as size of various
types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 8.x/9.x/10.x/-current with target architecture'.)



portname:   archivers/hlextract
broken because: Checksum and size mismatch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=hlextract


portname:   archivers/pecl-lzf
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=pecl-lzf


portname:   archivers/ruby-zip
broken because: Does not build with Ruby 2.1
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=ruby-zip


portname:   archivers/wzip
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=wzip


portname:   astro/aa
broken because: Checksum mismatch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=aa


portname:   astro/dgpsip
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=dgpsip


portname:   astro/ephem
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=ephem


portname:   astro/gpstk
broken because: Distfile size mismatch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=gpstk


portname:   astro/sky2000
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=sky2000


portname:   astro/wmglobe
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=wmglobe


portname:   audio/aacgain
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=aacgain


portname:   audio/amb-plugins
broken because: Distfile size mismatch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=amb-plugins


portname:   audio/ampache
broken because: Unfetchable
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ampache


portname:   audio/amrcoder
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=amrcoder


portname:   audio/aureal-kmod
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=aureal-kmod


portname:   audio/btc
broken because: Ftp time out
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=btc


portname:   audio/cd2mp3
broken because: Fails to fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=cd2mp3


portname:   audio/cmus-post.fm
broken because: No public distfiles
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=cmus-post.fm


port

FreeBSD ports which are currently marked forbidden

[linimon]

As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles.  Often,
these ports are so marked due to security concerns, such as known
exploits.

An overview of each port, including errors seen on the build farm,
is included below.

portname:   x11/nvidia-driver-173
forbidden because:  vulnerable to denial of service or arbitrary code
execution (CVE-2014-8298)
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=nvidia-driver-173
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD unmaintained ports which are currently scheduled for deletion

[linimon]

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness.  Often,
this is due to a better alternative having become available and/or
the cessation of development on the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:   chinese/joe
description:Joe's Own Editor
maintainer: po...@freebsd.org
deprecated because: The difference with editors/joe is too trivial to
warrant a separate port
expiration date:2015-09-27
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=joe


portname:   games/wmfortune
description:Dockapp that outputs fortune messages
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: Broken for more than 6 months
expiration date:2015-04-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=wmfortune
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports which are currently scheduled for deletion

[linimon]

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness.  Often,
this is due to a better alternative having become available and/or
the cessation of development on the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:   archivers/lz4
description:Fast compressor using LZ4 algorithm
maintainer: ale...@renatasystems.org
deprecated because: Superseded by archivers/liblz4; use that instead
expiration date:2015-05-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=lz4


portname:   chinese/joe
description:Joe's Own Editor
maintainer: po...@freebsd.org
deprecated because: The difference with editors/joe is too trivial to
warrant a separate port
expiration date:2015-09-27
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=joe


portname:   databases/db48
description:The Berkeley DB package, revision 4.8
maintainer: mand...@freebsd.org
deprecated because: Please migrate to db5 or db6
expiration date:2015-05-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=db48


portname:   databases/postgresql84-client
description:PostgreSQL database (client)
maintainer: pg...@freebsd.org
deprecated because: EOL was reached in July 2014
expiration date:2015-05-10
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql84-client


portname:   databases/postgresql84-contrib
description:The contrib utilities from the PostgreSQL distribution
maintainer: pg...@freebsd.org
deprecated because: EOL was reached in July 2014
expiration date:2015-05-10
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql84-contrib


portname:   databases/postgresql84-docs
description:The PostgreSQL documentation set
maintainer: pg...@freebsd.org
deprecated because: EOL was reached in July 2014
expiration date:2015-05-10
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql84-docs


portname:   databases/postgresql84-plperl
description:Write SQL functions for PostgreSQL using Perl5
maintainer: pg...@freebsd.org
deprecated because: EOL was reached in July 2014
expiration date:2015-05-10
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql84-plperl


portname:   databases/postgresql84-plpython
description:Module for using Python to write SQL functions
maintainer: pg...@freebsd.org
deprecated because: EOL was reached in July 2014
expiration date:2015-05-10
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql84-plpython


portname:   databases/postgresql84-pltcl
description:Module for using Tcl to write SQL functions
maintainer: pg...@freebsd.org
deprecated because: EOL was reached in July 2014
expiration date:2015-05-10
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql84-pltcl


portname:   databases/postgresql84-server
description:The most advanced open-source database available
anywhere
maintainer: pg...@freebsd.org
deprecated because: EOL was reached in July 2014
expiration date:2015-05-10
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql84-server


portname:   deskutils/libopensync-plugin-python
description:Python plugin for the OpenSync framework
maintainer: webmas...@kibab.com
status: BROKEN
deprecated because: Unfetchable, devices are not produced anymore
expiration date:2015-05-07
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=libopensync-plugin-python


portname:   deskutils/msynctool
description:Command line client for the OpenSync framework
maintainer: webmas...@kibab.com
status: 

Re: devel/p4web -- Fix broken port

[Kubilay Kocak]

On 21/04/2015 11:41 AM, Devin Teske wrote:
> Hi Antoine,
> 
> Please find attached a patch to unbreak the devel/p4web build.
> I got the distinfo directly from perforce.com support. This is the
> new location of p4web which has been open-sourced.
> 
> The binaries did not change checksum.
> 
> Hey, while we’re here, let’s just axe the distinfo for old versions
> which the Makefile doesn’t even support installing.
> 
> Looking forward to having a working devel/p4web port again.
> 
> Patch contains a couple hunks for devel/p4web/Makefile
> as well as doing an “svn delete” for the old distinfo files that
> we no longer support (we do not support installing the 6.0
> versions of the binaries regardless of your build environment).
> — 
> Cheers,
> Devin
> 
> P.S. Please put on the commit message…
> 
> Submitted by: dteske
> Sponsored by: Panzura, Inc.
> 

Hey Devin, thanks for this. Can you pop it in an issue on Bugzilla?

Handy from a breadcrumbs and information for our-future-selves point of view

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

Re: pkg 1.5.0 is out

[Slawa Olhovchenkov]

On Tue, Apr 14, 2015 at 10:05:00PM +0200, Baptiste Daroussin wrote:

> Hi all,
> 
> Final pkg 1.5.0 has been released.

pkg 1.5.1 at 'pkg upgrade' propose
===
New packages to be INSTALLED:
nvidia-driver: 346.47
linux-c6-libGLU: 10.1
===

I am use nvidia-driver-340:

# pkg info nvidia-driver-340-340.76
nvidia-driver-340-340.76
Name   : nvidia-driver-340
Version: 340.76
Installed on   : Tue Mar 10 16:15:59 MSK 2015
Origin : x11/nvidia-driver-340
Architecture   : freebsd:10:x86:64
Prefix : /usr/local
Categories : x11 kld
Licenses   : NVIDIA
Maintainer : da...@freebsd.org
WWW: http://www.nvidia.com/object/unix.html
Comment: NVidia graphics card binary drivers for hardware
OpenGL rendering
Options:
ACPI_PM: on
DOCS   : on
LINUX  : on
WBINVD : off
Shared Libs required:
libXext.so.6
libX11.so.6
Shared Libs provided:
libvdpau_nvidia.so.1
libnvidia-glsi.so.1
libnvidia-glcore.so.1
libnvidia-eglcore.so.1
libnvidia-cfg.so.1
libglx.so.1
libGLESv2.so.2
libGLESv1_CM.so.1
libGL.so.1
libEGL.so.1
Annotations:
repo_type  : binary
repository : ivs
Flat size  : 209MiB
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Bacula without IPv6

[Andrea Venturoli]

On 04/12/15 18:41, Dan Langille wrote:


That is a good idea.  Please submit a PR so we do not lose track of this.  I 
ask because it may be some time before I work on this.

We'll have the default with IPV6 on.


Done: it's #199535.

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

Re: Bacula without IPv6

[Baptiste Daroussin]

On Sun, Apr 12, 2015 at 01:41:03PM -0300, Dan Langille wrote:
> 
> > On Apr 12, 2015, at 12:38 PM, Andrea Venturoli  wrote:
> > 
> > Hello.
> > 
> > Running Bacula on a system where IPv6 was disabled in the kernel yields lot 
> > of errors:
> > 
> >> # bconsole
> >> Connecting to Director localhost:9101
> >> bconsole: bsock.c:227-0 Socket open error. proto=28 port=9101. 
> >> ERR=Protocol not supported
> >> ...
> >> *autodisplay on
> >> *status client
> > > ...
> >> 12-Apr 17:34 martin-xxx JobId 0: Error: bsock.c:225 Socket open error. 
> >> proto=28 port=9102. ERR=Protocol not supported
> > 
> > While these are harmless, any succesful job will report:
> > 
> >>  Termination:Backup OK -- with warnings
> > 
> > This can lead to overlooking more serious problems.
> > 
> > 
> > 
> > Solving it all is as easy as adding "--disable-ipv6" to CONFIGURE_ARGS.
> > 
> > 
> > 
> > I'm reporting this hoping it will help others, but I also ask: can we have 
> > an option to disable IPv6, like many other ports have?
> 
> That is a good idea.  Please submit a PR so we do not lose track of this.  I 
> ask because it may be some time before I work on this.
> 
> We'll have the default with IPV6 on.
> 
IPV6 is always on by default per OPTIONS framework design :)

Best regards,
Bapt


pgp6VbNZqDEgk.pgp
Description: PGP signature

Re: pkg-static: Insufficient privileges to add packages

[Dan Langille]

This reply has been rearranged..

On Tue, Apr 21, 2015 at 6:56 AM Ben Woods mailto:woods...@gmail.com>> wrote:

> On Apr 20, 2015, at 7:18 PM, Ben Woods  wrote:

> On Tue, Apr 21, 2015 at 4:02 AM Dan Langille  > wrote:
> I am running a testport on www/py-django-tastypie
> 
> My goal it to add an option for using www/django16 as well as www/django 
> (1.7).
> 
> The error I get is:
> 
> $ sudo poudriere testport -v -j 101amd64 -p testing -z testing -i -o 
> www/py-django-tastypie
> ...
> ===>Verifying install for py27-django>=1.5 in /usr/ports/www/py-django16
> ===>   Installing existing package /packages/All/py27-django16-1.6.11.txz
> pkg-static: Insufficient privileges to add packages
> 
> But because I'm running testport interactively, I see I can install the port 
> it mentions:
> 
> root@101amd64-testing-testing:~ # pkg install 
> /packages/All/py27-django16-1.6.11.txz
> Updating local repository catalogue...
> [101amd64-testing-testing] Fetching meta.txz: 100%816 B   0.8kB/s00:01
> [101amd64-testing-testing] Fetching packagesite.txz: 100%   50 KiB  51.4kB/s  
>   00:01
> Processing entries: 100%
> local repository update completed. 205 packages processed.
> Updating database digests format: 100%
> Checking integrity... done (0 conflicting)
> The following 1 package(s) will be affected (of 0 checked):
> 
> New packages to be INSTALLED:
> py27-django16: 1.6.11
> 
> The process will require 27 MiB more space.
> 
> Proceed with this action? [y/N]: y
> [101amd64-testing-testing] [1/1] Installing py27-django16-1.6.11...
> [101amd64-testing-testing] [1/1] Extracting py27-django16-1.6.11: 100%
> root@101amd64-testing-testing:~ #
> 
> 
> Why does the testport fail?
> 
> Full build log here: 
> http://services.unixathome.org/poudriere/data/101amd64-testing-testing/2015-04-20_19h53m23s/logs/errors/py27-django-tastypie-0.12.1.log
>  
> 




> That error is generated in the pkg exec_add function in src/add.c here:
> https://github.com/freebsd/pkg/blob/master/src/add.c 
> 
> 
> It occurs because it checks the package database for read, write, create 
> access using the pkgdb_access and pkgdb_check_access functions in 
> libpkg/pkgdb.c here:
> https://github.com/freebsd/pkg/blob/master/libpkg/pkgdb.c 
> 
> 
> I believe this is inside the jail created by poudriere testport. It would be 
> interesting to add the -i interactive flag to the testport run and check the 
> permissions on/in the pkg database. Mine are here for reference:
> % ls -lah /var/db/pkg/
> total 37484
> drwxr-xr-x   2 root  wheel 8B 21 Apr 06:00 .
> drwxr-xr-x  13 root  wheel19B 21 Apr 06:13 ..
> -rw-r--r--   1 root  wheel   246B  4 Dec 06:22 FreeBSD.meta
> -rw-r--r--   1 root  wheel11M 21 Apr 06:00 local.sqlite
> -rw-r--r--   1 root  wheel   246B 21 Apr 03:05 poudriere.meta
> -rw-r--r--   1 root  wheel49M  4 Dec 06:22 repo-FreeBSD.sqlite
> -rw-r--r--   1 root  wheel   1.6M 21 Apr 03:05 repo-poudriere.sqlite
> -r--r--r--   1 root  wheel   3.3M 21 Apr 03:17 vuln.xml
> 
> Regards,
> Ben


> 
> 
> Hand on a minute now my poudriere system is doing the same thing - looks 
> like we have a bug somewhere.
> 
> I am running pkg 1.5.1 and poudriere 3.1.4. According to freshports, pkg was 
> updated on 16th April, and poudriere on 10th April.
> 
> Inside my poudriere testport jail (using the -i interactive mode flag), I 
> have:
> # ls -lah /var/db/pkg/
> total 7953
> drwxr-xr-x   2 root  wheel 3B Apr 20 23:17 .
> drwxr-xr-x  12 root  wheel14B Apr 20 23:17 ..
> -rw-r--r--   1 root  wheel   7.7M Apr 20 23:17 local.sqlite
> 
> Thoughts?
> 



Here's what I have:

Edit /etc/motd to change this login announcement.
root@101amd64-testing-testing:~ # ls -lah /var/db/pkg/
total 2991
drwxr-xr-x   2 root  wheel 3B Apr 21 13:28 .
drwxr-xr-x  10 root  wheel12B Mar 14 19:18 ..
-rw-r--r--   1 root  wheel   2.8M Apr 21 13:28 local.sqlite
root@101amd64-testing-testing:~ #

—
Dan Langille
http://langille .org/







signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: devel/p4web -- Fix broken port

[Devin Teske]

On Apr 21, 2015, at 1:37 AM, Kubilay Kocak  wrote:

> On 21/04/2015 11:41 AM, Devin Teske wrote:
>> Hi Antoine,
>> 
>> Please find attached a patch to unbreak the devel/p4web build.
>> I got the distinfo directly from perforce.com support. This is the
>> new location of p4web which has been open-sourced.
>> 
>> The binaries did not change checksum.
>> 
>> Hey, while we’re here, let’s just axe the distinfo for old versions
>> which the Makefile doesn’t even support installing.
>> 
>> Looking forward to having a working devel/p4web port again.
>> 
>> Patch contains a couple hunks for devel/p4web/Makefile
>> as well as doing an “svn delete” for the old distinfo files that
>> we no longer support (we do not support installing the 6.0
>> versions of the binaries regardless of your build environment).
>> — 
>> Cheers,
>> Devin
>> 
>> P.S. Please put on the commit message…
>> 
>> Submitted by:dteske
>> Sponsored by:Panzura, Inc.
>> 
> 
> Hey Devin, thanks for this. Can you pop it in an issue on Bugzilla?
> 
> Handy from a breadcrumbs and information for our-future-selves point of view
> 

Yeah, no problem. Thanks!
-- 
Devin
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg-static: Insufficient privileges to add packages

[Ben Woods]

>> On Tue, Apr 21, 2015 at 4:02 AM Dan Langille  wrote:
>>>
>>> I am running a testport on www/py-django-tastypie
>>>
>>> My goal it to add an option for using www/django16 as well as www/django
>>> (1.7).
>>>
>>> The error I get is:
>>>
>>> $ sudo poudriere testport -v -j 101amd64 -p testing -z testing -i -o
>>> www/py-django-tastypie
>>> ...
>>> ===>Verifying install for py27-django>=1.5 in
>>> /usr/ports/www/py-django16
>>> ===>   Installing existing package /packages/All/py27-django16-1.6.11.txz
>>> pkg-static: Insufficient privileges to add packages
>>>
>>> But because I'm running testport interactively, I see I can install the
>>> port it mentions:
>>>
>>> root@101amd64-testing-testing:~ # pkg install
>>> /packages/All/py27-django16-1.6.11.txz
>>> Updating local repository catalogue...
>>> [101amd64-testing-testing] Fetching meta.txz: 100%816 B   0.8kB/s
>>> 00:01
>>> [101amd64-testing-testing] Fetching packagesite.txz: 100%   50 KiB
>>> 51.4kB/s00:01
>>> Processing entries: 100%
>>> local repository update completed. 205 packages processed.
>>> Updating database digests format: 100%
>>> Checking integrity... done (0 conflicting)
>>> The following 1 package(s) will be affected (of 0 checked):
>>>
>>> New packages to be INSTALLED:
>>> py27-django16: 1.6.11
>>>
>>> The process will require 27 MiB more space.
>>>
>>> Proceed with this action? [y/N]: y
>>> [101amd64-testing-testing] [1/1] Installing py27-django16-1.6.11...
>>> [101amd64-testing-testing] [1/1] Extracting py27-django16-1.6.11: 100%
>>> root@101amd64-testing-testing:~ #
>>>
>>>
>>> Why does the testport fail?
>>>
>>> Full build log here:
>>> http://services.unixathome.org/poudriere/data/101amd64-testing-testing/2015-04-20_19h53m23s/logs/errors/py27-django-tastypie-0.12.1.log
>>
>>
>> That error is generated in the pkg exec_add function in src/add.c here:
>> https://github.com/freebsd/pkg/blob/master/src/add.c
>>
>> It occurs because it checks the package database for read, write, create
>> access using the pkgdb_access and pkgdb_check_access functions in
>> libpkg/pkgdb.c here:
>> https://github.com/freebsd/pkg/blob/master/libpkg/pkgdb.c
>>
>> I believe this is inside the jail created by poudriere testport. It would
>> be interesting to add the -i interactive flag to the testport run and check
>> the permissions on/in the pkg database. Mine are here for reference:
>> % ls -lah /var/db/pkg/
>> total 37484
>> drwxr-xr-x   2 root  wheel 8B 21 Apr 06:00 .
>> drwxr-xr-x  13 root  wheel19B 21 Apr 06:13 ..
>> -rw-r--r--   1 root  wheel   246B  4 Dec 06:22 FreeBSD.meta
>> -rw-r--r--   1 root  wheel11M 21 Apr 06:00 local.sqlite
>> -rw-r--r--   1 root  wheel   246B 21 Apr 03:05 poudriere.meta
>> -rw-r--r--   1 root  wheel49M  4 Dec 06:22 repo-FreeBSD.sqlite
>> -rw-r--r--   1 root  wheel   1.6M 21 Apr 03:05 repo-poudriere.sqlite
>> -r--r--r--   1 root  wheel   3.3M 21 Apr 03:17 vuln.xml
>>
>> Regards,
>> Ben
>>
>>
>>
>>
>> Hand on a minute now my poudriere system is doing the same thing -
>> looks like we have a bug somewhere.
>>
>> I am running pkg 1.5.1 and poudriere 3.1.4. According to freshports, pkg
>> was updated on 16th April, and poudriere on 10th April.
>>
>> Inside my poudriere testport jail (using the -i interactive mode flag), I
>> have:
>> # ls -lah /var/db/pkg/
>> total 7953
>> drwxr-xr-x   2 root  wheel 3B Apr 20 23:17 .
>> drwxr-xr-x  12 root  wheel14B Apr 20 23:17 ..
>> -rw-r--r--   1 root  wheel   7.7M Apr 20 23:17 local.sqlite
>>
>> Thoughts?
>
> Here's what I have:
>
> Edit /etc/motd to change this login announcement.
> root@101amd64-testing-testing:~ # ls -lah /var/db/pkg/
> total 2991
> drwxr-xr-x   2 root  wheel 3B Apr 21 13:28 .
> drwxr-xr-x  10 root  wheel12B Mar 14 19:18 ..
> -rw-r--r--   1 root  wheel   2.8M Apr 21 13:28 local.sqlite
> root@101amd64-testing-testing:~ #
>
> —
> Dan Langille
> http://langille.org/

For the record, downgrading pkg to 1.4.12 and poudriere to 3.1.2 did
not fix this issue for me.

The port that I am trying to testport on FreeBSD 10.1 is
math/plplot-ada. The testport permission issues do not occur with the
port as it is currently - only after making the changes I have
proposed to math/plplot here:
https://bugs.freebsd.org/bugzilla/attachment.cgi?id=155771&action=diff
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: MooseFS Ports for versions 2.0 and 3.0

[Piotr Robert Konopelko]

Hello,

I've submitted the upgraded ports and obsoleted prior attachments.
Please review them.

https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=moosefs[1] 

In the meantime MooseFS has been upgraded, so I posted ports to the 2.0.63-1 
version.

Thanks in advance :)

-- 
Best regards,
Piotr Robert Konopelko
*MooseFS Technical Support Engineer* | moosefs.com[2]


(...)




3. It's nice for ports for share parts of their configuration, but I don't 
think it should be 
called "bsd.port.moosefs.mk[3]" (this implies it is part of the port build 
scripts). A good 
example of what you could do is devel/libtool. It has a Makefile which includes 
Makefile.common. The devel/libltdl port also 
includes "${.CURDIR}/../libtool/Makefile.common".


The name was used by original port creator. I've change it to Makefile.common. 




4. @dirrm is now deprecated in pkg-plist. Suggest it is probably easier to 
build this with 
"make install && make makeplist > pkg-plist". Note that you should check the 
plist looks 
correct, and also delete the top warning line from the generated file.


Yes. I've changed @dirrm[try] to @dir or removed them. I've also added '@owner 
mfs' and 
'@group mfs' and compared each list with the result of "make makeplist".




5. The pkg-descr file should be updated to include a better description of the 
package, 
and link to the website.


Yes. I've made much better descriptions.




6. Before submitting a port, check that it passes the normal checks by 
installing the ports-
mgmt/portlint program, and running "portlint -AC" in the port directory.


portlint -AC gives something like this:


[root@fbsdmule /usr/ports/sysutils/moosefs-master]# portlint -AC
WARN: Makefile: PORTVERSION/DISTVERSION is set externally to this port's 
Makefile, 
but this port is not configured as a slave port.
WARN: Makefile: MAINTAINER is set externally to this port's Makefile, but this 
port is 
not configured as a slave port.
0 fatal errors and 2 warnings found.


I hope that I can leave it - I've checked other random ports and such warning 
are very 
usual.




7. If you have access to a poudriere installation, you should submit the 
"poudriere 
testport" logs showing that this port will build successfully.


Yes we have. We use poudriere to make packages, so all our ports are always 
checked by 
poudriere.


Myself or other ports contributors/committers can help with this if you do not 
have access 
to a poudriere installation, but please make sure you have at least tested the 
build on 
FreeBSD with a "make install".




Much of this is covered in the porter's handbook. It's a good read if you 
haven't already 
seen it. You can find it here:
https://www.freebsd.org/doc/en/books/porters-handbook/book.html[4]



Note that if you re-submit patches to each bug report, be sure to tick the 
option that it 
obsolete's the previous patch.


Ok. We'll send those ports again.




Good luck! :)


Thanks again for your comments. It was very helpful.




-- Regards,Jakub Kruszona-Zawadzki- - - - - - - - - - - - - - - -Segmentation 
fault 
(core dumped)Phone: +48 602 212 039






[1] https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=moosefs
[2] http://moosefs.com
[3] http://bsd.port.moosefs.mk/
[4] https://www.freebsd.org/doc/en/books/porters-handbook/book.html
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg-static: Insufficient privileges to add packages

[Dan Langille]

> On Apr 21, 2015, at 11:44 AM, Ben Woods  wrote:
> 
>>> On Tue, Apr 21, 2015 at 4:02 AM Dan Langille  wrote:
 
 I am running a testport on www/py-django-tastypie
 
 My goal it to add an option for using www/django16 as well as www/django
 (1.7).
 
 The error I get is:
 
 $ sudo poudriere testport -v -j 101amd64 -p testing -z testing -i -o
 www/py-django-tastypie
 ...
 ===>Verifying install for py27-django>=1.5 in
 /usr/ports/www/py-django16
 ===>   Installing existing package /packages/All/py27-django16-1.6.11.txz
 pkg-static: Insufficient privileges to add packages
 
 But because I'm running testport interactively, I see I can install the
 port it mentions:
 
 root@101amd64-testing-testing:~ # pkg install
 /packages/All/py27-django16-1.6.11.txz
 Updating local repository catalogue...
 [101amd64-testing-testing] Fetching meta.txz: 100%816 B   0.8kB/s
 00:01
 [101amd64-testing-testing] Fetching packagesite.txz: 100%   50 KiB
 51.4kB/s00:01
 Processing entries: 100%
 local repository update completed. 205 packages processed.
 Updating database digests format: 100%
 Checking integrity... done (0 conflicting)
 The following 1 package(s) will be affected (of 0 checked):
 
 New packages to be INSTALLED:
py27-django16: 1.6.11
 
 The process will require 27 MiB more space.
 
 Proceed with this action? [y/N]: y
 [101amd64-testing-testing] [1/1] Installing py27-django16-1.6.11...
 [101amd64-testing-testing] [1/1] Extracting py27-django16-1.6.11: 100%
 root@101amd64-testing-testing:~ #
 
 
 Why does the testport fail?
 
 Full build log here:
 http://services.unixathome.org/poudriere/data/101amd64-testing-testing/2015-04-20_19h53m23s/logs/errors/py27-django-tastypie-0.12.1.log
>>> 
>>> 
>>> That error is generated in the pkg exec_add function in src/add.c here:
>>> https://github.com/freebsd/pkg/blob/master/src/add.c
>>> 
>>> It occurs because it checks the package database for read, write, create
>>> access using the pkgdb_access and pkgdb_check_access functions in
>>> libpkg/pkgdb.c here:
>>> https://github.com/freebsd/pkg/blob/master/libpkg/pkgdb.c
>>> 
>>> I believe this is inside the jail created by poudriere testport. It would
>>> be interesting to add the -i interactive flag to the testport run and check
>>> the permissions on/in the pkg database. Mine are here for reference:
>>> % ls -lah /var/db/pkg/
>>> total 37484
>>> drwxr-xr-x   2 root  wheel 8B 21 Apr 06:00 .
>>> drwxr-xr-x  13 root  wheel19B 21 Apr 06:13 ..
>>> -rw-r--r--   1 root  wheel   246B  4 Dec 06:22 FreeBSD.meta
>>> -rw-r--r--   1 root  wheel11M 21 Apr 06:00 local.sqlite
>>> -rw-r--r--   1 root  wheel   246B 21 Apr 03:05 poudriere.meta
>>> -rw-r--r--   1 root  wheel49M  4 Dec 06:22 repo-FreeBSD.sqlite
>>> -rw-r--r--   1 root  wheel   1.6M 21 Apr 03:05 repo-poudriere.sqlite
>>> -r--r--r--   1 root  wheel   3.3M 21 Apr 03:17 vuln.xml
>>> 
>>> Regards,
>>> Ben
>>> 
>>> 
>>> 
>>> 
>>> Hand on a minute now my poudriere system is doing the same thing -
>>> looks like we have a bug somewhere.
>>> 
>>> I am running pkg 1.5.1 and poudriere 3.1.4. According to freshports, pkg
>>> was updated on 16th April, and poudriere on 10th April.
>>> 
>>> Inside my poudriere testport jail (using the -i interactive mode flag), I
>>> have:
>>> # ls -lah /var/db/pkg/
>>> total 7953
>>> drwxr-xr-x   2 root  wheel 3B Apr 20 23:17 .
>>> drwxr-xr-x  12 root  wheel14B Apr 20 23:17 ..
>>> -rw-r--r--   1 root  wheel   7.7M Apr 20 23:17 local.sqlite
>>> 
>>> Thoughts?
>> 
>> Here's what I have:
>> 
>> Edit /etc/motd to change this login announcement.
>> root@101amd64-testing-testing:~ # ls -lah /var/db/pkg/
>> total 2991
>> drwxr-xr-x   2 root  wheel 3B Apr 21 13:28 .
>> drwxr-xr-x  10 root  wheel12B Mar 14 19:18 ..
>> -rw-r--r--   1 root  wheel   2.8M Apr 21 13:28 local.sqlite
>> root@101amd64-testing-testing:~ #
>> 
>> —
>> Dan Langille
>> http://langille.org/
> 
> For the record, downgrading pkg to 1.4.12 and poudriere to 3.1.2 did
> not fix this issue for me.
> 
> The port that I am trying to testport on FreeBSD 10.1 is
> math/plplot-ada. The testport permission issues do not occur with the
> port as it is currently - only after making the changes I have
> proposed to math/plplot here:
> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=155771&action=diff

I am also testing local changes to a port.

The problem occurs on a 10.1 but NOT on a 9.3 jail (both amd64).

Here is the good 9.3 run: 
http://services.unixathome.org/poudriere/build.html?mastername=93amd64-testing-testing&build=2015-04-21_16h17m45s

Compare that to the failed 10.1 run: Full build log here: 
http://services.unixathome.org/poudriere/data/101amd64-testing-testing/2015-04-20_19h53m23s/logs/errors/py27-django-tastypie-0.12.1.log

I am using pkg-1.5.1 and poudriere-

Re: pkg-static: Insufficient privileges to add packages

[Baptiste Daroussin]

On Tue, Apr 21, 2015 at 11:44:01PM +0800, Ben Woods wrote:
> >> On Tue, Apr 21, 2015 at 4:02 AM Dan Langille  wrote:
> >>>
> >>> I am running a testport on www/py-django-tastypie
> >>>
> >>> My goal it to add an option for using www/django16 as well as www/django
> >>> (1.7).
> >>>
> >>> The error I get is:
> >>>
> >>> $ sudo poudriere testport -v -j 101amd64 -p testing -z testing -i -o
> >>> www/py-django-tastypie
> >>> ...
> >>> ===>Verifying install for py27-django>=1.5 in
> >>> /usr/ports/www/py-django16
> >>> ===>   Installing existing package /packages/All/py27-django16-1.6.11.txz
> >>> pkg-static: Insufficient privileges to add packages
> >>>
> >>> But because I'm running testport interactively, I see I can install the
> >>> port it mentions:
> >>>
> >>> root@101amd64-testing-testing:~ # pkg install
> >>> /packages/All/py27-django16-1.6.11.txz
> >>> Updating local repository catalogue...
> >>> [101amd64-testing-testing] Fetching meta.txz: 100%816 B   0.8kB/s
> >>> 00:01
> >>> [101amd64-testing-testing] Fetching packagesite.txz: 100%   50 KiB
> >>> 51.4kB/s00:01
> >>> Processing entries: 100%
> >>> local repository update completed. 205 packages processed.
> >>> Updating database digests format: 100%
> >>> Checking integrity... done (0 conflicting)
> >>> The following 1 package(s) will be affected (of 0 checked):
> >>>
> >>> New packages to be INSTALLED:
> >>> py27-django16: 1.6.11
> >>>
> >>> The process will require 27 MiB more space.
> >>>
> >>> Proceed with this action? [y/N]: y
> >>> [101amd64-testing-testing] [1/1] Installing py27-django16-1.6.11...
> >>> [101amd64-testing-testing] [1/1] Extracting py27-django16-1.6.11: 100%
> >>> root@101amd64-testing-testing:~ #
> >>>
> >>>
> >>> Why does the testport fail?
> >>>
> >>> Full build log here:
> >>> http://services.unixathome.org/poudriere/data/101amd64-testing-testing/2015-04-20_19h53m23s/logs/errors/py27-django-tastypie-0.12.1.log
> >>
> >>
> >> That error is generated in the pkg exec_add function in src/add.c here:
> >> https://github.com/freebsd/pkg/blob/master/src/add.c
> >>
> >> It occurs because it checks the package database for read, write, create
> >> access using the pkgdb_access and pkgdb_check_access functions in
> >> libpkg/pkgdb.c here:
> >> https://github.com/freebsd/pkg/blob/master/libpkg/pkgdb.c
> >>
> >> I believe this is inside the jail created by poudriere testport. It would
> >> be interesting to add the -i interactive flag to the testport run and check
> >> the permissions on/in the pkg database. Mine are here for reference:
> >> % ls -lah /var/db/pkg/
> >> total 37484
> >> drwxr-xr-x   2 root  wheel 8B 21 Apr 06:00 .
> >> drwxr-xr-x  13 root  wheel19B 21 Apr 06:13 ..
> >> -rw-r--r--   1 root  wheel   246B  4 Dec 06:22 FreeBSD.meta
> >> -rw-r--r--   1 root  wheel11M 21 Apr 06:00 local.sqlite
> >> -rw-r--r--   1 root  wheel   246B 21 Apr 03:05 poudriere.meta
> >> -rw-r--r--   1 root  wheel49M  4 Dec 06:22 repo-FreeBSD.sqlite
> >> -rw-r--r--   1 root  wheel   1.6M 21 Apr 03:05 repo-poudriere.sqlite
> >> -r--r--r--   1 root  wheel   3.3M 21 Apr 03:17 vuln.xml
> >>
> >> Regards,
> >> Ben
> >>
> >>
> >>
> >>
> >> Hand on a minute now my poudriere system is doing the same thing -
> >> looks like we have a bug somewhere.
> >>
> >> I am running pkg 1.5.1 and poudriere 3.1.4. According to freshports, pkg
> >> was updated on 16th April, and poudriere on 10th April.
> >>
> >> Inside my poudriere testport jail (using the -i interactive mode flag), I
> >> have:
> >> # ls -lah /var/db/pkg/
> >> total 7953
> >> drwxr-xr-x   2 root  wheel 3B Apr 20 23:17 .
> >> drwxr-xr-x  12 root  wheel14B Apr 20 23:17 ..
> >> -rw-r--r--   1 root  wheel   7.7M Apr 20 23:17 local.sqlite
> >>
> >> Thoughts?
> >
> > Here's what I have:
> >
> > Edit /etc/motd to change this login announcement.
> > root@101amd64-testing-testing:~ # ls -lah /var/db/pkg/
> > total 2991
> > drwxr-xr-x   2 root  wheel 3B Apr 21 13:28 .
> > drwxr-xr-x  10 root  wheel12B Mar 14 19:18 ..
> > -rw-r--r--   1 root  wheel   2.8M Apr 21 13:28 local.sqlite
> > root@101amd64-testing-testing:~ #
> >
> > —
> > Dan Langille
> > http://langille.org/
> 
> For the record, downgrading pkg to 1.4.12 and poudriere to 3.1.2 did
> not fix this issue for me.
> 
> The port that I am trying to testport on FreeBSD 10.1 is
> math/plplot-ada. The testport permission issues do not occur with the
> port as it is currently - only after making the changes I have
> proposed to math/plplot here:
> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=155771&action=diff

I found the reason for Dan by checking the logs,  If I could see your own logs
then I will tell you where you mistake is.

actually you are having poudriere building as a user (internally to the jail)
which is a very good thing as it allows to catch things like this :D)

I mean it is dropping roots priviledges to build, stage and make package.

but still try to install a dependency there, proba

Re: pkg-static: Insufficient privileges to add packages

[Dan Langille]

> On Apr 21, 2015, at 12:34 PM, Baptiste Daroussin  wrote:
> 
> On Tue, Apr 21, 2015 at 11:44:01PM +0800, Ben Woods wrote:
 On Tue, Apr 21, 2015 at 4:02 AM Dan Langille  wrote:
> 
> I am running a testport on www/py-django-tastypie
> 
> My goal it to add an option for using www/django16 as well as www/django
> (1.7).
> 
> The error I get is:
> 
> $ sudo poudriere testport -v -j 101amd64 -p testing -z testing -i -o
> www/py-django-tastypie
> ...
> ===>Verifying install for py27-django>=1.5 in
> /usr/ports/www/py-django16
> ===>   Installing existing package /packages/All/py27-django16-1.6.11.txz
> pkg-static: Insufficient privileges to add packages
> 
> But because I'm running testport interactively, I see I can install the
> port it mentions:
> 
> root@101amd64-testing-testing:~ # pkg install
> /packages/All/py27-django16-1.6.11.txz
> Updating local repository catalogue...
> [101amd64-testing-testing] Fetching meta.txz: 100%816 B   0.8kB/s
> 00:01
> [101amd64-testing-testing] Fetching packagesite.txz: 100%   50 KiB
> 51.4kB/s00:01
> Processing entries: 100%
> local repository update completed. 205 packages processed.
> Updating database digests format: 100%
> Checking integrity... done (0 conflicting)
> The following 1 package(s) will be affected (of 0 checked):
> 
> New packages to be INSTALLED:
>py27-django16: 1.6.11
> 
> The process will require 27 MiB more space.
> 
> Proceed with this action? [y/N]: y
> [101amd64-testing-testing] [1/1] Installing py27-django16-1.6.11...
> [101amd64-testing-testing] [1/1] Extracting py27-django16-1.6.11: 100%
> root@101amd64-testing-testing:~ #
> 
> 
> Why does the testport fail?
> 
> Full build log here:
> http://services.unixathome.org/poudriere/data/101amd64-testing-testing/2015-04-20_19h53m23s/logs/errors/py27-django-tastypie-0.12.1.log
 
 
 That error is generated in the pkg exec_add function in src/add.c here:
 https://github.com/freebsd/pkg/blob/master/src/add.c
 
 It occurs because it checks the package database for read, write, create
 access using the pkgdb_access and pkgdb_check_access functions in
 libpkg/pkgdb.c here:
 https://github.com/freebsd/pkg/blob/master/libpkg/pkgdb.c
 
 I believe this is inside the jail created by poudriere testport. It would
 be interesting to add the -i interactive flag to the testport run and check
 the permissions on/in the pkg database. Mine are here for reference:
 % ls -lah /var/db/pkg/
 total 37484
 drwxr-xr-x   2 root  wheel 8B 21 Apr 06:00 .
 drwxr-xr-x  13 root  wheel19B 21 Apr 06:13 ..
 -rw-r--r--   1 root  wheel   246B  4 Dec 06:22 FreeBSD.meta
 -rw-r--r--   1 root  wheel11M 21 Apr 06:00 local.sqlite
 -rw-r--r--   1 root  wheel   246B 21 Apr 03:05 poudriere.meta
 -rw-r--r--   1 root  wheel49M  4 Dec 06:22 repo-FreeBSD.sqlite
 -rw-r--r--   1 root  wheel   1.6M 21 Apr 03:05 repo-poudriere.sqlite
 -r--r--r--   1 root  wheel   3.3M 21 Apr 03:17 vuln.xml
 
 Regards,
 Ben
 
 
 
 
 Hand on a minute now my poudriere system is doing the same thing -
 looks like we have a bug somewhere.
 
 I am running pkg 1.5.1 and poudriere 3.1.4. According to freshports, pkg
 was updated on 16th April, and poudriere on 10th April.
 
 Inside my poudriere testport jail (using the -i interactive mode flag), I
 have:
 # ls -lah /var/db/pkg/
 total 7953
 drwxr-xr-x   2 root  wheel 3B Apr 20 23:17 .
 drwxr-xr-x  12 root  wheel14B Apr 20 23:17 ..
 -rw-r--r--   1 root  wheel   7.7M Apr 20 23:17 local.sqlite
 
 Thoughts?
>>> 
>>> Here's what I have:
>>> 
>>> Edit /etc/motd to change this login announcement.
>>> root@101amd64-testing-testing:~ # ls -lah /var/db/pkg/
>>> total 2991
>>> drwxr-xr-x   2 root  wheel 3B Apr 21 13:28 .
>>> drwxr-xr-x  10 root  wheel12B Mar 14 19:18 ..
>>> -rw-r--r--   1 root  wheel   2.8M Apr 21 13:28 local.sqlite
>>> root@101amd64-testing-testing:~ #
>>> 
>>> —
>>> Dan Langille
>>> http://langille.org/
>> 
>> For the record, downgrading pkg to 1.4.12 and poudriere to 3.1.2 did
>> not fix this issue for me.
>> 
>> The port that I am trying to testport on FreeBSD 10.1 is
>> math/plplot-ada. The testport permission issues do not occur with the
>> port as it is currently - only after making the changes I have
>> proposed to math/plplot here:
>> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=155771&action=diff
> 
> I found the reason for Dan by checking the logs,  If I could see your own logs
> then I will tell you where you mistake is.
> 
> actually you are having poudriere building as a user (internally to the jail)
> which is a very good thing as it allows to catch things like this :D)
> 
> I mean it

Re: devel/p4web -- Fix broken port

[Devin Teske]

> On Apr 21, 2015, at 1:37 AM, Kubilay Kocak  wrote:
> 
> On 21/04/2015 11:41 AM, Devin Teske wrote:
>> Hi Antoine,
>> 
>> Please find attached a patch to unbreak the devel/p4web build.
>> I got the distinfo directly from perforce.com support. This is the
>> new location of p4web which has been open-sourced.
>> 
>> The binaries did not change checksum.
>> 
>> Hey, while we’re here, let’s just axe the distinfo for old versions
>> which the Makefile doesn’t even support installing.
>> 
>> Looking forward to having a working devel/p4web port again.
>> 
>> Patch contains a couple hunks for devel/p4web/Makefile
>> as well as doing an “svn delete” for the old distinfo files that
>> we no longer support (we do not support installing the 6.0
>> versions of the binaries regardless of your build environment).
>> — 
>> Cheers,
>> Devin
>> 
>> P.S. Please put on the commit message…
>> 
>> Submitted by:dteske
>> Sponsored by:Panzura, Inc.
>> 
> 
> Hey Devin, thanks for this. Can you pop it in an issue on Bugzilla?
> 
> Handy from a breadcrumbs and information for our-future-selves point of view


Filed. Thanks! ;D

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199589
— 
Devin
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: minidlna: file descriptor 3794 too big for select

[Michael Lappe]

Hello Stefan,

 

thanks for your nice post "minidlna: file descriptor 3794 too big for
select". 

 

I'm using minidlna 1.1.0 in a NAS4free Jail (TheBrig). And after adding my
big music collection to the media folder I got exactly the problem you got
before.

 

Would you send me your patch please? A little instruction would be nice,
too. Cause I guess I'm a kind of newbie.

 

Thanks again!

 

Regards,

Michael

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

Re: pkg-static: Insufficient privileges to add packages

[Ben Woods]

On Wednesday, April 22, 2015, Baptiste Daroussin  wrote:

> On Tue, Apr 21, 2015 at 11:44:01PM +0800, Ben Woods wrote:
> > >> On Tue, Apr 21, 2015 at 4:02 AM Dan Langille  > wrote:
> > >>>
> > >>> I am running a testport on www/py-django-tastypie
> > >>>
> > >>> My goal it to add an option for using www/django16 as well as
> www/django
> > >>> (1.7).
> > >>>
> > >>> The error I get is:
> > >>>
> > >>> $ sudo poudriere testport -v -j 101amd64 -p testing -z testing -i -o
> > >>> www/py-django-tastypie
> > >>> ...
> > >>> ===>Verifying install for py27-django>=1.5 in
> > >>> /usr/ports/www/py-django16
> > >>> ===>   Installing existing package
> /packages/All/py27-django16-1.6.11.txz
> > >>> pkg-static: Insufficient privileges to add packages
> > >>>
> > >>> But because I'm running testport interactively, I see I can install
> the
> > >>> port it mentions:
> > >>>
> > >>> root@101amd64-testing-testing:~ # pkg install
> > >>> /packages/All/py27-django16-1.6.11.txz
> > >>> Updating local repository catalogue...
> > >>> [101amd64-testing-testing] Fetching meta.txz: 100%816 B   0.8kB/s
> > >>> 00:01
> > >>> [101amd64-testing-testing] Fetching packagesite.txz: 100%   50 KiB
> > >>> 51.4kB/s00:01
> > >>> Processing entries: 100%
> > >>> local repository update completed. 205 packages processed.
> > >>> Updating database digests format: 100%
> > >>> Checking integrity... done (0 conflicting)
> > >>> The following 1 package(s) will be affected (of 0 checked):
> > >>>
> > >>> New packages to be INSTALLED:
> > >>> py27-django16: 1.6.11
> > >>>
> > >>> The process will require 27 MiB more space.
> > >>>
> > >>> Proceed with this action? [y/N]: y
> > >>> [101amd64-testing-testing] [1/1] Installing py27-django16-1.6.11...
> > >>> [101amd64-testing-testing] [1/1] Extracting py27-django16-1.6.11:
> 100%
> > >>> root@101amd64-testing-testing:~ #
> > >>>
> > >>>
> > >>> Why does the testport fail?
> > >>>
> > >>> Full build log here:
> > >>>
> http://services.unixathome.org/poudriere/data/101amd64-testing-testing/2015-04-20_19h53m23s/logs/errors/py27-django-tastypie-0.12.1.log
> > >>
> > >>
> > >> That error is generated in the pkg exec_add function in src/add.c
> here:
> > >> https://github.com/freebsd/pkg/blob/master/src/add.c
> > >>
> > >> It occurs because it checks the package database for read, write,
> create
> > >> access using the pkgdb_access and pkgdb_check_access functions in
> > >> libpkg/pkgdb.c here:
> > >> https://github.com/freebsd/pkg/blob/master/libpkg/pkgdb.c
> > >>
> > >> I believe this is inside the jail created by poudriere testport. It
> would
> > >> be interesting to add the -i interactive flag to the testport run and
> check
> > >> the permissions on/in the pkg database. Mine are here for reference:
> > >> % ls -lah /var/db/pkg/
> > >> total 37484
> > >> drwxr-xr-x   2 root  wheel 8B 21 Apr 06:00 .
> > >> drwxr-xr-x  13 root  wheel19B 21 Apr 06:13 ..
> > >> -rw-r--r--   1 root  wheel   246B  4 Dec 06:22 FreeBSD.meta
> > >> -rw-r--r--   1 root  wheel11M 21 Apr 06:00 local.sqlite
> > >> -rw-r--r--   1 root  wheel   246B 21 Apr 03:05 poudriere.meta
> > >> -rw-r--r--   1 root  wheel49M  4 Dec 06:22 repo-FreeBSD.sqlite
> > >> -rw-r--r--   1 root  wheel   1.6M 21 Apr 03:05 repo-poudriere.sqlite
> > >> -r--r--r--   1 root  wheel   3.3M 21 Apr 03:17 vuln.xml
> > >>
> > >> Regards,
> > >> Ben
> > >>
> > >>
> > >>
> > >>
> > >> Hand on a minute now my poudriere system is doing the same thing -
> > >> looks like we have a bug somewhere.
> > >>
> > >> I am running pkg 1.5.1 and poudriere 3.1.4. According to freshports,
> pkg
> > >> was updated on 16th April, and poudriere on 10th April.
> > >>
> > >> Inside my poudriere testport jail (using the -i interactive mode
> flag), I
> > >> have:
> > >> # ls -lah /var/db/pkg/
> > >> total 7953
> > >> drwxr-xr-x   2 root  wheel 3B Apr 20 23:17 .
> > >> drwxr-xr-x  12 root  wheel14B Apr 20 23:17 ..
> > >> -rw-r--r--   1 root  wheel   7.7M Apr 20 23:17 local.sqlite
> > >>
> > >> Thoughts?
> > >
> > > Here's what I have:
> > >
> > > Edit /etc/motd to change this login announcement.
> > > root@101amd64-testing-testing:~ # ls -lah /var/db/pkg/
> > > total 2991
> > > drwxr-xr-x   2 root  wheel 3B Apr 21 13:28 .
> > > drwxr-xr-x  10 root  wheel12B Mar 14 19:18 ..
> > > -rw-r--r--   1 root  wheel   2.8M Apr 21 13:28 local.sqlite
> > > root@101amd64-testing-testing:~ #
> > >
> > > —
> > > Dan Langille
> > > http://langille.org/
> >
> > For the record, downgrading pkg to 1.4.12 and poudriere to 3.1.2 did
> > not fix this issue for me.
> >
> > The port that I am trying to testport on FreeBSD 10.1 is
> > math/plplot-ada. The testport permission issues do not occur with the
> > port as it is currently - only after making the changes I have
> > proposed to math/plplot here:
> > https://bugs.freebsd.org/bugzilla/attachment.cgi?id=155771&action=diff
>
> I found the reason for Dan by checking the logs,  If I could see your own
> logs

Re: pkg-static: Insufficient privileges to add packages

[Baptiste Daroussin]

On Wed, Apr 22, 2015 at 07:46:06AM +0800, Ben Woods wrote:
> On Wednesday, April 22, 2015, Baptiste Daroussin  wrote:
> 
> > On Tue, Apr 21, 2015 at 11:44:01PM +0800, Ben Woods wrote:
> > > >> On Tue, Apr 21, 2015 at 4:02 AM Dan Langille  > > wrote:
> > > >>>
> > > >>> I am running a testport on www/py-django-tastypie
> > > >>>
> > > >>> My goal it to add an option for using www/django16 as well as
> > www/django
> > > >>> (1.7).
> > > >>>
> > > >>> The error I get is:
> > > >>>
> > > >>> $ sudo poudriere testport -v -j 101amd64 -p testing -z testing -i -o
> > > >>> www/py-django-tastypie
> > > >>> ...
> > > >>> ===>Verifying install for py27-django>=1.5 in
> > > >>> /usr/ports/www/py-django16
> > > >>> ===>   Installing existing package
> > /packages/All/py27-django16-1.6.11.txz
> > > >>> pkg-static: Insufficient privileges to add packages
> > > >>>
> > > >>> But because I'm running testport interactively, I see I can install
> > the
> > > >>> port it mentions:
> > > >>>
> > > >>> root@101amd64-testing-testing:~ # pkg install
> > > >>> /packages/All/py27-django16-1.6.11.txz
> > > >>> Updating local repository catalogue...
> > > >>> [101amd64-testing-testing] Fetching meta.txz: 100%816 B   0.8kB/s
> > > >>> 00:01
> > > >>> [101amd64-testing-testing] Fetching packagesite.txz: 100%   50 KiB
> > > >>> 51.4kB/s00:01
> > > >>> Processing entries: 100%
> > > >>> local repository update completed. 205 packages processed.
> > > >>> Updating database digests format: 100%
> > > >>> Checking integrity... done (0 conflicting)
> > > >>> The following 1 package(s) will be affected (of 0 checked):
> > > >>>
> > > >>> New packages to be INSTALLED:
> > > >>> py27-django16: 1.6.11
> > > >>>
> > > >>> The process will require 27 MiB more space.
> > > >>>
> > > >>> Proceed with this action? [y/N]: y
> > > >>> [101amd64-testing-testing] [1/1] Installing py27-django16-1.6.11...
> > > >>> [101amd64-testing-testing] [1/1] Extracting py27-django16-1.6.11:
> > 100%
> > > >>> root@101amd64-testing-testing:~ #
> > > >>>
> > > >>>
> > > >>> Why does the testport fail?
> > > >>>
> > > >>> Full build log here:
> > > >>>
> > http://services.unixathome.org/poudriere/data/101amd64-testing-testing/2015-04-20_19h53m23s/logs/errors/py27-django-tastypie-0.12.1.log
> > > >>
> > > >>
> > > >> That error is generated in the pkg exec_add function in src/add.c
> > here:
> > > >> https://github.com/freebsd/pkg/blob/master/src/add.c
> > > >>
> > > >> It occurs because it checks the package database for read, write,
> > create
> > > >> access using the pkgdb_access and pkgdb_check_access functions in
> > > >> libpkg/pkgdb.c here:
> > > >> https://github.com/freebsd/pkg/blob/master/libpkg/pkgdb.c
> > > >>
> > > >> I believe this is inside the jail created by poudriere testport. It
> > would
> > > >> be interesting to add the -i interactive flag to the testport run and
> > check
> > > >> the permissions on/in the pkg database. Mine are here for reference:
> > > >> % ls -lah /var/db/pkg/
> > > >> total 37484
> > > >> drwxr-xr-x   2 root  wheel 8B 21 Apr 06:00 .
> > > >> drwxr-xr-x  13 root  wheel19B 21 Apr 06:13 ..
> > > >> -rw-r--r--   1 root  wheel   246B  4 Dec 06:22 FreeBSD.meta
> > > >> -rw-r--r--   1 root  wheel11M 21 Apr 06:00 local.sqlite
> > > >> -rw-r--r--   1 root  wheel   246B 21 Apr 03:05 poudriere.meta
> > > >> -rw-r--r--   1 root  wheel49M  4 Dec 06:22 repo-FreeBSD.sqlite
> > > >> -rw-r--r--   1 root  wheel   1.6M 21 Apr 03:05 repo-poudriere.sqlite
> > > >> -r--r--r--   1 root  wheel   3.3M 21 Apr 03:17 vuln.xml
> > > >>
> > > >> Regards,
> > > >> Ben
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> Hand on a minute now my poudriere system is doing the same thing -
> > > >> looks like we have a bug somewhere.
> > > >>
> > > >> I am running pkg 1.5.1 and poudriere 3.1.4. According to freshports,
> > pkg
> > > >> was updated on 16th April, and poudriere on 10th April.
> > > >>
> > > >> Inside my poudriere testport jail (using the -i interactive mode
> > flag), I
> > > >> have:
> > > >> # ls -lah /var/db/pkg/
> > > >> total 7953
> > > >> drwxr-xr-x   2 root  wheel 3B Apr 20 23:17 .
> > > >> drwxr-xr-x  12 root  wheel14B Apr 20 23:17 ..
> > > >> -rw-r--r--   1 root  wheel   7.7M Apr 20 23:17 local.sqlite
> > > >>
> > > >> Thoughts?
> > > >
> > > > Here's what I have:
> > > >
> > > > Edit /etc/motd to change this login announcement.
> > > > root@101amd64-testing-testing:~ # ls -lah /var/db/pkg/
> > > > total 2991
> > > > drwxr-xr-x   2 root  wheel 3B Apr 21 13:28 .
> > > > drwxr-xr-x  10 root  wheel12B Mar 14 19:18 ..
> > > > -rw-r--r--   1 root  wheel   2.8M Apr 21 13:28 local.sqlite
> > > > root@101amd64-testing-testing:~ #
> > > >
> > > > —
> > > > Dan Langille
> > > > http://langille.org/
> > >
> > > For the record, downgrading pkg to 1.4.12 and poudriere to 3.1.2 did
> > > not fix this issue for me.
> > >
> > > The port that I am trying to testport on FreeBSD 10.1 is
> > > math/plplot-ada

Re: pkg-static: Insufficient privileges to add packages

[Ben Woods]

On 22 April 2015 at 07:51, Baptiste Daroussin  wrote:
>> >
>> > I found the reason for Dan by checking the logs,  If I could see your own
>> > logs
>> > then I will tell you where you mistake is.
>> >
>> > actually you are having poudriere building as a user (internally to the
>> > jail)
>> > which is a very good thing as it allows to catch things like this :D)
>> >
>> > I mean it is dropping roots priviledges to build, stage and make package.
>> >
>> > but still try to install a dependency there, probably because the
>> > dependency
>> > line you have in your port is buggy. In dan case he was testing if
>> > py27-django>=1.5 but was refering to the www/py-django16 port which result
>> > in a
>> > package named py27-django16 which is not py27-django aka the test will
>> > always
>> > fail and the ports tree will try to reinstall again and again even in
>> > phases
>> > when it cannot due to lack of priviledges
>> >
>> > As a conclusion the bug is in the port you are testing not in pkg, neither
>> > in
>> > poudriere.
>> >
>> > If you show me the logs of your own build I will tell you what is your
>> > mistake.
>> >
>> > Best regards,
>> > Bapt
>> >
>>
>> Thanks for your help Bapt. You are right, it was an issue with the port
>> dependency list. In my case the library had changed from plplotd.so to
>> plplot.so (now without the 'd'). I have fixed that in the LIB_DEPENDS line
>> and the problem is fixed.
>>
>> Trying to debug this issue took some time, because the error message was
>> about permissions and I didn't make the connection was with unsatisfied
>> dependencies.
>>
>> Could we perhaps add an additional check somewhere in the process that
>> informs you the dependencies have not been correctly satisfied? Do you
>> think this extra check belongs in poudriere or the ports infrastructure?
>
> Improvement for that has been added into the ports tree and taken in account 
> by
> poudriere in latest poudriere-devel 3.1.99.20150421_1 by Bryan
>
> Best regards,
> Bapt

Thanks Bapt and Bryan - looks like a helpful change!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: phalcon-1.3.4

[Daniel Lin]

Hello, Ruud,

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

I'd approved the phalcon 2.0 patch pr, hope the committers could commit
and update soon.

Please just wait.

Have a nice day.


2015-04-19 3:47 GMT+08:00 Ruud Boon :

> Hi Daniel,
>
> Thank you for maintaining the Phalcon port.
> I’m wondering do you have any plans to upgrade the port to 2.0?
>
> All the best.
> Ruud
>
>


-- 
Daniel Lin (pct)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"