Re: www/aria2 dependencies & lang/llvm33 build error

2013-11-26 Thread Matthias Andree
Am 22.11.2013 15:20, schrieb andrew clarke:
> On Sun 2013-11-17 14:15:02 UTC+0100, Michael Gmelin (free...@grem.de) wrote:
> 
 www/aria2 1.18.1 requires lang/clang33. Is this really necessary?
 Previous aria2 versions didn't require clang.
>>>
>>> I've now had a chance to check the aria2 sources and evidently it now
>>> requires C++11 support, which I find surprising, but that's progress I
>>> suppose...
>>
>> From a developer's standpoint this makes a lot of sense, since C++11 is
>> more productive and a lot more fun to use.
> 
> Sounds good. I just wonder about the logic behind doing that for a
> minor 1.17 -> 1.18 release though.

Without asking the aria2 developers, I would argue that once you've got
it built, it's likely compatible with the previous 1.X versions with
respect to its public interfaces (shell, possibly library API,
configuration files) so the developers did not move to a major 2.X release.

Also you could argue that C++11 has caught on relatively quickly so it
might appear to the aria2 developers to be a minor move.

> Out of curiosity I tried building devel/libc++ under 9.2 but it failed with:
> 
> Shared object "libz.so.5" not found, required by "libLLVM-3.3.so"
> 
> Evidently the fix is to add "libz.so.5 libz.so" to /etc/libmap.conf.

No, the fix is to rebuild libLLVM-3.3.so after the system upgrade.

https://wiki.freebsd.org/NewC%2B%2BStack

>> - Try building aria with a recent gcc instead
> 
> I've had no success with that either!

Was the configure complaining, or the build after you'd hacked the
configure script?  I presume you'd have to use gcc48.
___
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: www/aria2 dependencies & lang/llvm33 build error

2013-11-26 Thread Matthias Andree
Am 22.11.2013 15:56, schrieb andrew clarke:
> On Fri 2013-11-22 15:51:14 UTC+0100, Michael Gmelin (free...@grem.de) wrote:
> 
>>> Then the obvious question is... How did you get aria2 to build in 9.1
>>> when I can't get it to build in 9.2? ;-)
>>
>> I built 9.1 from source using:
>>
>> WITH_LIBCPLUSPLUS=YES
>> (and later WITH_CLANG_EXTRAS=1)
>>
>> (make buildworld installworld kernel)
>>
>> So I've got libc++.
>>
>> All ports are built using:
>> CC=clang
>> CXX=clang++
>> CXXFLAGS+= -std=c++11 -stdlib=libc++
>> CPP=clang-cpp
> 
> I see! I'll give that a try if I get some free time, although the
> effort required seems excessive just to build the latest aria2 . :)

Have you got it working?  If you get it working, feeding back what
you've got to the port's maintainer would be good so it can be marked
broken on 8.X and made to work on 9.X with proper instructions if libc++
is missing.

___
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_libchk (was Re: gvfs on FreeBSD 10 fails to build)

2013-11-26 Thread Kevin Oberman
On Tue, Nov 26, 2013 at 11:32 AM, Matthew Seaman wrote:

> On 26/11/2013 18:15, Warren Block wrote:
> > On Tue, 26 Nov 2013, Kevin Oberman wrote:
> >
> >> Possibly hijacking the thread, but isn't it time that pkg_libchk was
> >> made a
> >> part of the base system? It comes up over and over as a tool to simplify
> >> dealing with dealing with shareable library version bumps and even more
> >> important for dealing with the problem seen here. It's a fairly simple,
> >> well written, maintainable shell script, so will run with no
> >> dependencies.
> >> I can't think of any reason not to include it in the base system.
> >>
> >> Checking for issues with shareable libraries is an obvious requirement
> >> for
> >> maintaining a system and doing so without a tool like pkg_libchk is
> >> unnecessarily tedious and painful.
> >
> > Maybe integrating it with pkg rather than the base system.  At least for
> > me, it's not a problem with the base.
>
> pkg(8) already has a lot of shlib analysis built in.  So, for instance
> to find all the pkg with binaries that link against libiconv:
>
>% pkg shlib -P libiconv.so.3
>
> Hmmm... although it seems the -P and -R flags have gotten swapped over
> somehow.
>
> Matthew
>

Yes, this is a start, but it would be quite difficult to confirm that every
package installed has no missing libraries. This is a somewhat different
problem. If pkg can be modified to do this, great, but pkg_libchk works
with both old and new packaging systems today.

I do feel that if similar capability can be added to pkg, that would be
better as removing something from base is a real pain.

-- 
R. Kevin Oberman, Network Engineer
E-mail: rkober...@gmail.com
___
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"


portmaster glitch with /usr/ports/MOVED

2013-11-26 Thread andrew clarke
I made the mistake of telling portmaster-3.17.3 to build
mail/mutt-devel instead of mail/mutt. Evidently portmaster sees the
port has moved based on /usr/ports/MOVED, which is good, but it 
erroneously calls pkg, apparently without arguments, and the remaining
output looks a bit broken.

Regards
Andrew

# portmaster mail/mutt-devel

===>>> The mail/mutt-devel port moved to mail/mutt
===>>> Reason: mail/mutt-devel is ready for primetime

===>>> Exiting
Usage: pkg info 
   pkg info -a
   pkg info [-AbBDdefgiIklOqRrsx] 
   pkg info [-AbBDdfIlqRrs] -F 

For more information see 'pkg help info'.

===>>> The second argument to -o can be a package name,
   or a port directory from /usr/ports

does not seem to be installed,
   or listed as a dependency

===>>> No valid installed port, or port directory given
===>>> Try portmaster --help

===>>> Killing background jobs
Terminated
===>>> Exiting
___
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: Fwd: [thunderbird-24.1.0] FreeBSD 10-i386 jail at 11-amd64 host: Error while running startup cache precompilation

2013-11-26 Thread Cy Schubert
In message <5272af33.7030...@smeets.im>, Florian Smeets writes:
> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> --LjCOVwNOW3aPxiaJSC0KaksgOOBQirtv3
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> 
> On 31/10/13 16:13, Boris Samorodov wrote:
> >=20
> > Hi All,
> >=20
> > I get the following error using 10-i386 jail at 11-amd64 host:
> > -
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D hase: install>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > =3D=3D=3D>  Installing for thunderbird-24.1.0
> > ...
> > Executing
> > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/obj-i386-portbld-fr=
> eebsd10.0/mozilla/dist/bin/xpcshell
> > -g
> > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/obj-i386-portbld-fr=
> eebsd10.0/mozilla/dist/bin/
> > -a
> > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/obj-i386-portbld-fr=
> eebsd10.0/mozilla/dist/bin/
> > -f
> > /wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/moz=
> apps/installer/precompile_cache.js
> > -e precompile_startupcache("resource://gre/");
> > Traceback (most recent call last):
> >   File
> > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/mo=
> zapps/installer/packager.py",
> > line 375, in 
> > main()
> >   File
> > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/mo=
> zapps/installer/packager.py",
> > line 367, in main
> > args.source, gre_path, base)
> >   File
> > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/toolkit/mo=
> zapps/installer/packager.py",
> > line 148, in precompile_cache
> > errors.fatal('Error while running startup cache precompilation')
> >   File
> > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/python/moz=
> build/mozpack/errors.py",
> > line 101, in fatal
> > self._handle(self.FATAL, msg)
> >   File
> > "/wrkdirs/usr/ports/mail/thunderbird/work/comm-esr24/mozilla/python/moz=
> build/mozpack/errors.py",
> > line 96, in _handle
> > raise ErrorMessage(msg)
> > mozpack.errors.ErrorMessage: Error: Error while running startup cache
> > precompilation
> > gmake[3]: *** [stage-package] Error 1
> > -
> >=20
> > And there is a line at /var/log/messages:
> > -
> > Oct 31 17:54:33 bb052 kernel: pid 20298 (xpcshell), uid 0: exited on
> > signal 11 (core dumped)
> > -
> >=20
> > Full log is here:
> > http://gw.wart.ru/bulk/10-i386-default/2013-10-31_13h42m43s/logs/errors=
> /thunderbird-24.1.0.log
> >=20
> 
> Yeah, I'm also seeing this, I missed that 2 builds failed, seamonkey is
> also affected on 10.0/i386. No Idea what it is, yet. I hope to have some
> time during the weekend to look at it.

I'm seeing the same problem on my i386 systems (except for one). It 
installs nicely on amd64.

On my one i386 system that thunderbird and seamonkey install, the system is 
a FreeBSD-11 system using ports built on a 9.X system a year ago and 
upgraded piecemeal (not recommended for the faint of heart). I'm betting 
there's an upgraded port somewhere that may contribute to this. (This 
particular
-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  http://www.FreeBSD.org
i386 system will be upgraded to amd64 using a $LOCALBASE and friends 
rsynced from a system downstairs -- been doing this for years.)



___
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: Question on updating pkg

2013-11-26 Thread Baptiste Daroussin
On Tue, Nov 26, 2013 at 11:05:07PM +0100, Michael Gmelin wrote:
> Maybe this has been answered before, but I stumbled over it numerous
> times:
> 
> When pkg needs an update, it's performed first and pkg exits just ok,
> but the original action wouldn't be done. This is a little bit
> confusing when running it manually and potentially harmfully in a
> scripted context.
> 
> Thanks,
> Michael
> 
> 
> Example:
> $ sudo pkg install git
> Updating repository catalogue
> digests.txz
>  100%  996KB 996.1KB/s 996.1KB/s   00:01
>  packagesite.txz
>  100% KB   5.4MB/s   3.8MB/s   00:01 Incremental update completed,
>  0 packages processed: 11200 packages updated, 709 removed and 135
>  added. New version of pkg detected; it needs to be installed first.
>  After this upgrade it is recommended that you do a full upgrade using:
>  'pkg upgrade'
> 
> The following 1 packages will be installed:
> 
> Upgrading pkg: 1.1.4_8 -> 1.1.4_10
> 
> The installation will require 2 kB more space
> 
> 1 MB to be downloaded
> 
> Proceed with installing packages [y/N]: y
> pkg-1.1.4_10.txz
> 100% 1649KB   1.6MB/s   1.6MB/s   00:01 Checking integrity... done
> [1/1] Upgrading pkg from 1.1.4_8 to 1.1.4_10... done
> 
> $ git
> bash: git: command not found
> 
> -- 
> Michael Gmelin
> ___
> 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"

This has been addressed by pkg 1.2, now the process initially asked for is
automatically restarted,

regards,
Bapt


pgptl0iu8xADG.pgp
Description: PGP signature


Question on updating pkg

2013-11-26 Thread Michael Gmelin
Maybe this has been answered before, but I stumbled over it numerous
times:

When pkg needs an update, it's performed first and pkg exits just ok,
but the original action wouldn't be done. This is a little bit
confusing when running it manually and potentially harmfully in a
scripted context.

Thanks,
Michael


Example:
$ sudo pkg install git
Updating repository catalogue
digests.txz
 100%  996KB 996.1KB/s 996.1KB/s   00:01
 packagesite.txz
 100% KB   5.4MB/s   3.8MB/s   00:01 Incremental update completed,
 0 packages processed: 11200 packages updated, 709 removed and 135
 added. New version of pkg detected; it needs to be installed first.
 After this upgrade it is recommended that you do a full upgrade using:
 'pkg upgrade'

The following 1 packages will be installed:

Upgrading pkg: 1.1.4_8 -> 1.1.4_10

The installation will require 2 kB more space

1 MB to be downloaded

Proceed with installing packages [y/N]: y
pkg-1.1.4_10.txz
100% 1649KB   1.6MB/s   1.6MB/s   00:01 Checking integrity... done
[1/1] Upgrading pkg from 1.1.4_8 to 1.1.4_10... done

$ git
bash: git: command not found

-- 
Michael Gmelin
___
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: portmaster refuses to use pkgng with local packages

2013-11-26 Thread olli hauer
On 2013-11-26 22:27, Axel Rau wrote:
> 
> Am 26.11.2013 um 20:58 schrieb Matthew Seaman :
> 
>> On 26/11/2013 18:07, Axel Rau wrote:
>>> I need a configuration, where pkg uses *ONLY* *my* repo.
>>
>> Delete the package site line from pkg.conf
> 
>>
> Unfortunately, this does not help:
> ---
> # pkg update
> Updating repository catalogue
> pkg: 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest//digests.txz:
>  File unavailable (e.g., file not found, no access)
> pkg: No digest falling back on legacy catalog format
> pkg: 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest//repo.txz:
>  File unavailable (e.g., file not found, no access)
> ---
> pkg did not contact my web server.
> 

After winning the fight with a couple of machines.

on the package build machine
- cd $package && rm repo.txz
- upgrade pkg on your Pd box to 1.2_1
- pkg repo (with the 1.2 version)

on the client:
- rm /var/db/repo* (and only this files!)

test a simple fetch from the client, in your case:
fetch http://db1.in.chaos1.de/92amd64-default/packagesite.txz
tail your webserver log if the file is found, else adjust the webserver config
or the packagesite.

For a quick jumpstart copy pkg-static (version 1.2) to the client and use this
binary so the pkg wrapper from the OS is not used.

I've wrote a small summary on githup maybe it helps others.
https://github.com/freebsd/pkg/issues/650

PS:
In case you see error messages like:
pkg: /usr/local/etc/pkg/repos//local.conf file is using a deprecated format. 
Please replace it with the following:
==...
and then your identical repo.conf ignore it for now only trust your web logs (I 
think the pkg team will fix this soon)

-- 
Regards,
olli
___
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: lang/gcc not build

2013-11-26 Thread Dimitry Andric
On 26 Nov 2013, at 22:43, Alexander Panyushkin  wrote:
...
> configure:4209: checking for C compiler default output file name
> configure:4231: gcc46 -Oz -march=athlon64-sse3 -mtune=athlon64-sse3 -pipe 
> -Qunused-arguments -Qunused-parameter -Wformat -Wformat-security -O2 
> -march=athlon64-sse3 -mtune=athlon64-sse3 -pipe -Wformat -I/usr/local/include 
> -Wl,-rpath=/usr/local/lib/gcc46 -fno-strict-aliasing -D_FORTIFY_SOURCE=2 
> -D_FORTIFY_SOURCE=2 -Wl,-rpath=/usr/local/lib/gcc46 conftest.c  >&5
> gcc46: error: unrecognized option '-Qunused-arguments'
> gcc46: error: unrecognized option '-Qunused-parameter'
> configure:4235: $? = 1

Apparently the COMPILER_TYPE logic in bsd.compiler.mk does not detect
you are using gcc, most likely because you are using USE_GCC= in
make.conf.  (This setting should normally be used in port Makefiles, not
in make.conf, AFAIK.)

Try one of the following:
* Add COMPILER_TYPE=gcc in make.conf (in the part where you put USE_GCC)
* Alternatively, remove USE_GCC and just set CC=gcc46, CXX=g++46 and
  CPP=cpp46.

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: portmaster refuses to use pkgng with local packages

2013-11-26 Thread Axel Rau

Am 26.11.2013 um 20:58 schrieb Matthew Seaman :

> On 26/11/2013 18:07, Axel Rau wrote:
>> I need a configuration, where pkg uses *ONLY* *my* repo.
> 
> Delete the package site line from pkg.conf

> 
Unfortunately, this does not help:
---
# pkg update
Updating repository catalogue
pkg: 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest//digests.txz:
 File unavailable (e.g., file not found, no access)
pkg: No digest falling back on legacy catalog format
pkg: 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest//repo.txz:
 File unavailable (e.g., file not found, no access)
---
pkg did not contact my web server.

Thanks, Axel
---
PGP-Key:29E99DD6  ☀ +49 151 2300 9283  ☀ computing @ chaos claudius

___
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: lang/gcc not build

2013-11-26 Thread Dimitry Andric
On 26 Nov 2013, at 21:26, Alexander Panyushkin  wrote:
> 26.11.2013 21:42, Dimitry Andric пишет:
>> * Don't set CFLAGS with '=', always use '+='.
>> * Try moving your make.conf out of the way, and build the port again.  Does 
>> it now work?
>> * If all that still fails, post the config.log file, like the message says.
> I change CFLAGS with '='  to CFLAGS with '+='
> 
> Same error

Post the config.log file, please.

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: portmaster refuses to use pkgng with local packages

2013-11-26 Thread Matthew Seaman
On 26/11/2013 18:07, Axel Rau wrote:
> I need a configuration, where pkg uses *ONLY* *my* repo.

Delete the packagesite line from pkg.conf

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature


Re: lang/gcc not build

2013-11-26 Thread Dimitry Andric
[Redirecting to the appropriate mailing list...]

On 26 Nov 2013, at 18:47, Alexander Panyushkin  wrote:
> #portmaster lang/gcc
> [...]
> cd /usr/ports/lang/gcc/work/gcc-4.6.4 ; contrib/gcc_update --touch
> configure: loading site script /usr/ports/Templates/config.site
> checking build system type... x86_64-portbld-freebsd10.0
> checking host system type... x86_64-portbld-freebsd10.0
> checking target system type... x86_64-portbld-freebsd10.0
> checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel
> checking whether ln works... yes
> checking whether ln -s works... yes
> checking for a sed that does not truncate output... (cached) /usr/bin/sed
> checking for gawk... (cached) /usr/bin/awk
> checking for gcc... gcc46
> checking for C compiler default output file name...
> configure: error: in `/usr/ports/lang/gcc/work/build':
> configure: error: C compiler cannot create executables
> See `config.log' for more details.
> ===>  Script "../gcc-4.6.4/configure" failed unexpectedly.
> Please report the problem to ger...@freebsd.org [maintainer] and attach the
> "/usr/ports/lang/gcc/work/build/config.log" including the output of the 
> failure
> of your make command. Also, it might be a good idea to provide an overview
> of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static
> info -g -Ea).
> *** Error code 1
> 
> #
> /etc/make.conf
> 
> .if ${.CURDIR:N*/ports/lang/gcc*} == ""
> CFLAGS= -O2 -march=athlon64-sse3 -mtune=athlon64-sse3 -pipe -Wformat
> CPPFLAGS+= -D_FORTIFY_SOURCE=2
> USE_GCC=4.6
> .endif
> 
> #pkg info -ix gcc
> gcc-4.6.3
> gcc-ecj-4.5
> gccmakedep-1.0.2_1

* Don't set CFLAGS with '=', always use '+='.
* Try moving your make.conf out of the way, and build the port again.  Does it 
now work?
* If all that still fails, post the config.log file, like the message says.

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: pkg_libchk (was Re: gvfs on FreeBSD 10 fails to build)

2013-11-26 Thread Matthew Seaman
On 26/11/2013 18:15, Warren Block wrote:
> On Tue, 26 Nov 2013, Kevin Oberman wrote:
> 
>> Possibly hijacking the thread, but isn't it time that pkg_libchk was
>> made a
>> part of the base system? It comes up over and over as a tool to simplify
>> dealing with dealing with shareable library version bumps and even more
>> important for dealing with the problem seen here. It's a fairly simple,
>> well written, maintainable shell script, so will run with no
>> dependencies.
>> I can't think of any reason not to include it in the base system.
>>
>> Checking for issues with shareable libraries is an obvious requirement
>> for
>> maintaining a system and doing so without a tool like pkg_libchk is
>> unnecessarily tedious and painful.
> 
> Maybe integrating it with pkg rather than the base system.  At least for
> me, it's not a problem with the base.

pkg(8) already has a lot of shlib analysis built in.  So, for instance
to find all the pkg with binaries that link against libiconv:

   % pkg shlib -P libiconv.so.3

Hmmm... although it seems the -P and -R flags have gotten swapped over
somehow.

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature


Re: pkg 1.2 lots of messages about enabled key.

2013-11-26 Thread Johan Hendriks
Op dinsdag 26 november 2013 schreef Baptiste Daroussin (b...@freebsd.org):

> On Tue, Nov 26, 2013 at 05:15:38PM +0100, Johan Hendriks wrote:
> > I just updated pkg to pkg 1.2
> >
> > But when i usr pkg it gives me a lot of messages like below:
> >
> > pkg: Warning: expecting a boolean for the 'enabled' key of the 'FreeBSD'
> > repo,  the value has been correctly converted, please consider fixing
> >
> > If i run pkg_libchk the whole screen fills up with these messages.
> > I did copy the new /usr/local/etc/pkg.conf.sample file to
> > /usr/local/etc/pkg.conf
> > Also i checked /etc/pkg/FreeBSD.conf , and it looks good to me as far as
> > i understand it.
> >
> > vi /etc/pkg/FreeBSD.conf
> > # $FreeBSD: stable/10/etc/pkg/FreeBSD.conf 257797 2013-11-07 15:43:41Z
> > bdrewery $
> > FreeBSD: {
> >url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest";,
> >mirror_type: "srv",
> >signature_type: "fingerprints",
> >fingerprints: "/usr/share/keys/pkg",
> >enabled: "YES"
> > }
> >
> > something i missed?
> >
> > regards
> > Johan
> > ___
> > 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
> "
>
> the MFC to stable/10 is coming in 2 days next beta will have it
>
> regards,
> Bapt
>

I will try tomorrow without the "  "
Thanks.

Regards,
Johan
___
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"


pkg_libchk (was Re: gvfs on FreeBSD 10 fails to build)

2013-11-26 Thread Warren Block

On Tue, 26 Nov 2013, Kevin Oberman wrote:


Possibly hijacking the thread, but isn't it time that pkg_libchk was made a
part of the base system? It comes up over and over as a tool to simplify
dealing with dealing with shareable library version bumps and even more
important for dealing with the problem seen here. It's a fairly simple,
well written, maintainable shell script, so will run with no dependencies.
I can't think of any reason not to include it in the base system.

Checking for issues with shareable libraries is an obvious requirement for
maintaining a system and doing so without a tool like pkg_libchk is
unnecessarily tedious and painful.


Maybe integrating it with pkg rather than the base system.  At least for 
me, it's not a problem with the base.

___
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: portmaster refuses to use pkgng with local packages

2013-11-26 Thread Axel Rau

Am 24.11.2013 um 12:43 schrieb Axel Rau :

> 
> Am 27.10.2013 um 21:11 schrieb Matthew Seaman :
> 
>> On 27/10/2013 18:53, Axel Rau wrote:
>>> I looked at poudriere earlier, but did not recognize that it plays with pkg 
>>> nicely and also did not like to set up a web server to just serve local 
>>> jails.
>>> I will give it a try.
>> 
>> You don't need to set up a webserver, necessarily.  If you're using
>> poudriere to build packages on the same machine where you want to
>> install them, then you can just use a file:// URL in your pkg.conf and
>> pkg will dtrt.  If you want to maintain a bunch of machines on a
>> network, then using a webserver to distribute the packages is probably
>> easiest overall, but you could NFS mount the repo and use a file:// URL
>> again, or you could use ssh:// to pull the packages down.
> While trying ports-mgmt/poudriere in my ezjail/portmaster environment, I 
> learned:
> poudriere can't run at secure level 1, because it loads linux.ko and uses 
> chflags.


Because of the chflags issue, I moved my repo to another server, installed a 
web server, configured firewalls and now trying to let pkg use my own repo, 
which does not work.
With the help of Olli, I checked the index provided by my web server and I 
added a config file in /usr/local/etc/pkg/repos/ .

I need a configuration, where pkg uses *ONLY* *my* repo.

This is the current situation:

# pkg info pkg
pkg-1.1.4_8

# pkg update
Updating repository catalogue
pkg: 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest//digests.txz:
 File unavailable (e.g., file not found, no access)
pkg: No digest falling back on legacy catalog format
pkg: 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest//repo.txz:
 File unavailable (e.g., file not found, no access)

# pkg -vv update
 Version: 1.1.4
 PACKAGESITE: 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest/
   PKG_DBDIR: /var/db/pkg
PKG_CACHEDIR: /tmp
PORTSDIR: /usr/ports
  PUBKEY: 
   HANDLE_RC_SCRIPTS: no
   ASSUME_ALWAYS_YES: no
   REPOS_DIR: /usr/local/etc/pkg/repos/
  PLIST_KEYWORDS_DIR: 
  SYSLOG: yes
AUTODEPS: no
 ABI: freebsd:9:x86:64
  DEVELOPER_MODE: no
  PORTAUDIT_SITE: http://portaudit.FreeBSD.org/auditfile.tbz
VULNXML_SITE: http://www.vuxml.org/freebsd/vuln.xml.bz2
 MIRROR_TYPE: SRV
 FETCH_RETRY: 3
 PKG_PLUGINS_DIR: /usr/local/lib/pkg/
  PKG_ENABLE_PLUGINS: yes
 PLUGINS:
   DEBUG_SCRIPTS: no
PLUGINS_CONF_DIR: /usr/local/etc/pkg/
  PERMISSIVE: no
 REPO_AUTOUPDATE: yes
  NAMESERVER: 
  EVENT_PIPE: 
   FETCH_TIMEOUT: 30
 UNSET_TIMESTAMP: no
SSH_RESTRICT_DIR: 
 PKG_ENV:
   DISABLE_MTREE: no

Repositories:
  packagesite:
 url: 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest/
 key: 
 enabled: yes
 mirror_type: SRV
  lrau-repo:
 url: http://db1.in.chaos1.de/92amd64-default
 key: 
 enabled: yes
 mirror_type: HTTP

---
# cat /usr/local/etc/pkg.conf 
packagesite: http://db1.in.chaos1.de/92amd64-default
PKG_CACHEDIR: /tmp

# cat /usr/local/etc/pkg/repos/lrau-repo.conf 
lrau-repo: {
url: "http://db1.in.chaos1.de/92amd64-default"; ,
mirror_type: "HTTP",
enabled: yes,
key: /usr/local/etc/ssl/certs/pkg.cert
}

Any help appreciated,
Axel
---
PGP-Key:29E99DD6  ☀ +49 151 2300 9283  ☀ computing @ chaos claudius

___
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: portmaster refuses to use pkgng with local packages

2013-11-26 Thread Axel Rau

Am 25.11.2013 um 10:40 schrieb Stefan Esser :

> Am 24.11.2013 12:43, schrieb Axel Rau:
>> While trying ports-mgmt/poudriere in my ezjail/portmaster environment, I 
>> learned:
>> poudriere can't run at secure level 1, because it loads linux.ko and uses 
>> chflags.
>> 
>> Regarding moving to pkgng, what are the replacements to portaudit / 
>> jailaudit?
> 
> # pkg audit -F
> Thanks Stefan, I will try this once my repo works.

Axel
---
PGP-Key:29E99DD6  ☀ +49 151 2300 9283  ☀ computing @ chaos claudius

___
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: gvfs on FreeBSD 10 fails to build

2013-11-26 Thread Kevin Oberman
On Tue, Nov 26, 2013 at 2:18 AM, Boris Samorodov  wrote:

> 26.11.2013 13:41, Johan Hendriks пишет:
> > Boris Samorodov schreef:
> >> 26.11.2013 11:55, Johan Hendriks пишет:
> >>
> >>> Hello all, I just updated my FreeBSD 9 Stable machine to FreeBSD 10
> >>> Stable.
> >>>
> >>> I am now in the proces of rebuilding all ports.
> >>> First I  noticed that libiconv was not needed anymore from ports so I
> >>> deleted that port.
> >>>
> >>> But on devel/gvfs I get an error.
> >> It's not enough just to remove converters/libiconv. For more information
> >> please take a look at /usr/ports/UPDATING.
> >>
> > I did go through /usr/ports/UPDATING, but not far enough :D
> >
> > Well the problem now is that i can not create a list of ports to
> > reinstall anymore because i already did remove libiconv.
>
> You may want to use pkg_libchk from sysutils/bsdadminscropts
> to detect those files/libraries which depends upon libiconv.
>

Possibly hijacking the thread, but isn't it time that pkg_libchk was made a
part of the base system? It comes up over and over as a tool to simplify
dealing with dealing with shareable library version bumps and even more
important for dealing with the problem seen here. It's a fairly simple,
well written, maintainable shell script, so will run with no dependencies.
I can't think of any reason not to include it in the base system.

Checking for issues with shareable libraries is an obvious requirement for
maintaining a system and doing so without a tool like pkg_libchk is
unnecessarily tedious and painful.
-- 
R. Kevin Oberman, Network Engineer
E-mail: rkober...@gmail.com
___
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.2 lots of messages about enabled key.

2013-11-26 Thread Baptiste Daroussin
On Tue, Nov 26, 2013 at 05:15:38PM +0100, Johan Hendriks wrote:
> I just updated pkg to pkg 1.2
> 
> But when i usr pkg it gives me a lot of messages like below:
> 
> pkg: Warning: expecting a boolean for the 'enabled' key of the 'FreeBSD' 
> repo,  the value has been correctly converted, please consider fixing
> 
> If i run pkg_libchk the whole screen fills up with these messages.
> I did copy the new /usr/local/etc/pkg.conf.sample file to 
> /usr/local/etc/pkg.conf
> Also i checked /etc/pkg/FreeBSD.conf , and it looks good to me as far as 
> i understand it.
> 
> vi /etc/pkg/FreeBSD.conf
> # $FreeBSD: stable/10/etc/pkg/FreeBSD.conf 257797 2013-11-07 15:43:41Z 
> bdrewery $
> FreeBSD: {
>url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest";,
>mirror_type: "srv",
>signature_type: "fingerprints",
>fingerprints: "/usr/share/keys/pkg",
>enabled: "YES"
> }
> 
> something i missed?
> 
> regards
> Johan
> ___
> 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"

the MFC to stable/10 is coming in 2 days next beta will have it

regards,
Bapt


pgpMBPD8xUy00.pgp
Description: PGP signature


Re: pkg 1.2 lots of messages about enabled key.

2013-11-26 Thread Łukasz Wąsikowski
W dniu 2013-11-26 17:15, Johan Hendriks pisze:

> I just updated pkg to pkg 1.2
> 
> But when i usr pkg it gives me a lot of messages like below:
> 
> pkg: Warning: expecting a boolean for the 'enabled' key of the 'FreeBSD'
> repo,  the value has been correctly converted, please consider fixing

[...]

>   enabled: "YES"
> }
> 
> something i missed?

Get rid of " signs. It should be:

enabled: yes

-- 
best regards,
Lukasz Wasikowski
___
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"


[patch] graphics/libGL/bsd.mesalib.mk

2013-11-26 Thread David Shane Holden
The latest graphics/libGL/bsd.mesalib.mk commit breaks graphics/dri when 
WITH_NEW_XORG is defined since it's trying to patch a nonexistent file.
diff --git a/graphics/libGL/bsd.mesalib.mk b/graphics/libGL/bsd.mesalib.mk
index 8e5e481..bf46cbb 100644
--- a/graphics/libGL/bsd.mesalib.mk
+++ b/graphics/libGL/bsd.mesalib.mk
@@ -120,8 +120,10 @@ post-patch:
 		${WRKSRC}/configure
 	@${REINPLACE_CMD} -e 's|/etc/|${PREFIX}/etc/|g' \
 		${WRKSRC}/src/mesa/drivers/dri/common/xmlconfig.c
+.if !defined(WITH_NEW_XORG)
 	@${REINPLACE_CMD} -e 's|python|${PYTHON_CMD}|' \
 		${WRKSRC}/src/gallium/auxiliary/util/Makefile
+.endif
 .if !defined(WITH_NEW_XORG)
 	@${REINPLACE_CMD} -e 's|[$$](INSTALL_LIB_DIR)/pkgconfig|${PREFIX}/libdata/pkgconfig|' \
 		${WRKSRC}/src/glu/Makefile \
___
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"

pkg 1.2 lots of messages about enabled key.

2013-11-26 Thread Johan Hendriks

I just updated pkg to pkg 1.2

But when i usr pkg it gives me a lot of messages like below:

pkg: Warning: expecting a boolean for the 'enabled' key of the 'FreeBSD' 
repo,  the value has been correctly converted, please consider fixing


If i run pkg_libchk the whole screen fills up with these messages.
I did copy the new /usr/local/etc/pkg.conf.sample file to 
/usr/local/etc/pkg.conf
Also i checked /etc/pkg/FreeBSD.conf , and it looks good to me as far as 
i understand it.


vi /etc/pkg/FreeBSD.conf
# $FreeBSD: stable/10/etc/pkg/FreeBSD.conf 257797 2013-11-07 15:43:41Z 
bdrewery $

FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest";,
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: "YES"
}

something i missed?

regards
Johan
___
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: sysutils/parallel maintainer: looking for guidance

2013-11-26 Thread Chris Howey
On 25 November 2013 18:54, Chris Howey  wrote:

> The latest version of parallel (20131122) has added a "Please use the
> below reference to cite parallel" notice that prints a few lines of output
> to stderr when it runs.
>
> User action is required to stop this notice from appearing upon every
> invocation (by running "parallel --bibtex" once).
>
> My concern is that anyone currently running automated scripts using
> parallel may be caught off guard by this, should I keep it anyway, or
> comment it out in a patch?
>
> Maybe a pkg-message, or a note in UPDATING, or is it even worth worrying
> about?
>

I received a reply from the upstream author echoing what Matthias said (
http://lists.freebsd.org/pipermail/freebsd-ports/2013-November/088067.html),
mentioning he made efforts to have the notice only appear when run from a
terminal.

If anyone's curious I'm not going to make any modifications regarding the
notice.
___
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 you maintain which are out of date

2013-11-26 Thread 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
+-+
audio/fdk-aac   | 0.1.2   | 0.1.3
+-+
devel/ocaml-extlib  | 1.5.4   | 1.6.1
+-+
www/xist| 3.25| 5.4
+-+


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

If wish to stop receiving portscout reminders, please contact
portsc...@freebsd.org

Thanks.
___
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 Port: lighttpd-1.4.33

2013-11-26 Thread Oliver Schonrock
Having issue compiling/running www/lighttpd with openssl_from_ports

details are here:

http://redmine.lighttpd.net/issues/2534

Not sure which end needs to change: Freebsd lighty port, openssl port or
lighty?

-- 
Oliver Schonrock

___
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: gvfs on FreeBSD 10 fails to build

2013-11-26 Thread Boris Samorodov
26.11.2013 13:41, Johan Hendriks пишет:
> Boris Samorodov schreef:
>> 26.11.2013 11:55, Johan Hendriks пишет:
>>
>>> Hello all, I just updated my FreeBSD 9 Stable machine to FreeBSD 10
>>> Stable.
>>>
>>> I am now in the proces of rebuilding all ports.
>>> First I  noticed that libiconv was not needed anymore from ports so I
>>> deleted that port.
>>>
>>> But on devel/gvfs I get an error.
>> It's not enough just to remove converters/libiconv. For more information
>> please take a look at /usr/ports/UPDATING.
>>
> I did go through /usr/ports/UPDATING, but not far enough :D
> 
> Well the problem now is that i can not create a list of ports to
> reinstall anymore because i already did remove libiconv.

You may want to use pkg_libchk from sysutils/bsdadminscropts
to detect those files/libraries which depends upon libiconv.

> I will try to use some binary packages on the ports that fail.

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: gvfs on FreeBSD 10 fails to build

2013-11-26 Thread Johan Hendriks

Boris Samorodov schreef:

26.11.2013 11:55, Johan Hendriks пишет:


Hello all, I just updated my FreeBSD 9 Stable machine to FreeBSD 10 Stable.

I am now in the proces of rebuilding all ports.
First I  noticed that libiconv was not needed anymore from ports so I
deleted that port.

But on devel/gvfs I get an error.

It's not enough just to remove converters/libiconv. For more information
please take a look at /usr/ports/UPDATING.


I did go through /usr/ports/UPDATING, but not far enough :D

Well the problem now is that i can not create a list of ports to 
reinstall anymore because i already did remove libiconv.

I will try to use some binary packages on the ports that fail.

Thanks for your time..

regards
Johan



___
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: gvfs on FreeBSD 10 fails to build

2013-11-26 Thread Boris Samorodov
26.11.2013 11:55, Johan Hendriks пишет:

> Hello all, I just updated my FreeBSD 9 Stable machine to FreeBSD 10 Stable.
> 
> I am now in the proces of rebuilding all ports.
> First I  noticed that libiconv was not needed anymore from ports so I
> deleted that port.
> 
> But on devel/gvfs I get an error.

It's not enough just to remove converters/libiconv. For more information
please take a look at /usr/ports/UPDATING.

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: poudirere behave-alike for

2013-11-26 Thread Baptiste Daroussin
On Mon, Nov 25, 2013 at 02:15:59AM +0100, Christopher J. Ruwe wrote:
> I think my question is slightly off-topic, but I think freebsd-ports@
> may be the best of many not so good fits:
> 
> I need to build packages for Solaris and SmartOS. My first choice
> would be ports, which unfortunately are not very well suited to
> cross-building. Instead I use, as many people, pkgsrc.
> 
> I would like to leverage pkgsrc with something like poudriere,
> especially as I have ZFS and zones in Solaris/SmartOS. I found in a
> message on the DragonFlyBSD list
> http://leaf.dragonflybsd.org/mailarchive/users/2013-01/msg8.html
> a mention of poudriere being used on DragonFly/pkgsrc.
> 
> Does anybody know of the state of this piece of software? The git
> repos I can find on google are stale links. As etoilebsd is
> referenced in the mail from DragonFly, I chose to ask here first.
> 
> To all of you, have a nice week, cheers,

As the creator of poudriere I would be more that happy to see poudriere ported
to Solaris-based os, on the paper it shouldn't be that hard: you have zfs
already zones that can probably be used the way we use the jails right now or
you can fallback on chroot like dragonfly does, you have tmpfs etc. That's on
the paper.

porting on pkgsrc would also be nice, I have been contacted by a couple of
pkgsrc developper but so far nothing came out.

Just keep in mind, that the main target will always remain FreeBSD but I can
offer a dedicated branch and tell you that there will be convergence. That is
how we do now with dragonfly.

regards,
Bapt


pgpIfvw9jZC8v.pgp
Description: PGP signature


Re: sysutils/parallel maintainer: looking for guidance

2013-11-26 Thread Matthias Andree
Am 26.11.2013 01:54, schrieb Chris Howey:
> The latest version of parallel (20131122) has added a "Please use the below
> reference to cite parallel" notice that prints a few lines of output to
> stderr when it runs.
> 
> User action is required to stop this notice from appearing upon every
> invocation (by running "parallel --bibtex" once).
> 
> My concern is that anyone currently running automated scripts using
> parallel may be caught off guard by this, should I keep it anyway, or
> comment it out in a patch?
> 
> Maybe a pkg-message, or a note in UPDATING, or is it even worth worrying
> about?

Parallel appears to make efforts to not dump the notice if stderr is
redirected, so if that works, no need to worry.

Note the online citation clause lacks the volume no. (36) and number (1)
in many styles (they are available in the BibTeX snippet though);
personally, I would also double-quote the journal's name due to the
strange ;login: in its name.


If you are worried, you can patch this notice/bib-tex requirement away,
pretending that --no-notice had been given, and have the output of
"parallel --bibtex" and the complete version of "When using GNU parallel
for a publication please cite: O. Tange (2011): GNU Parallel..."
displayed through pkg-message.
  You will then need to document that you have changed the program, with
date and your name -- see clauses 5 and 6 in the GPLv3, either in
/usr/ports/Templates/Licenses/GPLv3, or online at
.

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