FreeBSD ports you maintain which are out of date

2014-08-18 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
+-+
emulators/gxemul| 0.6.0   | 0.6.0.1
+-+
graphics/gphoto2| 2.5.4   | 2.5.5
+-+
graphics/libgphoto2 | 2.5.4   | 2.5.5
+-+
lang/nwcc   | 0.7.5   | 0.8.3
+-+
net-mgmt/pandorafms_agent   | 4.0.1   | 5.1-140818
+-+
net-mgmt/pandorafms_console | 4.0.1   | 5.1-140818
+-+
net-mgmt/pandorafms_server  | 4.0.1   | 5.1-140818
+-+


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

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

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


Squid 33

2014-08-18 Thread Andrea Venturoli

Hello.

Beware anyone updating www/squid33: latest update to this ports 
overwrote my squid.conf.


This might get annoying.

 bye
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: net-im/skype-[devel] won't connect

2014-08-18 Thread Artyom Mirgorodskiy
So I try again to run pulse audio and got the following error in syslog:
linux: pid 95238 (pacat): syscall ppoll not implemented

Anybody can help how to implement this syscall on linuxulator?

On Wednesday 13 August 2014 22:09:22 Vassilis Laganakos wrote:
 Hi,
 
 On Wed, Aug 13, 2014 at 10:47:25AM -0500, Scot Hetzel wrote:
  On Wed, Aug 13, 2014 at 10:38 AM, Kenta S. ken...@hush.com wrote:
   Hello. This afternoon when I try to sign onto Skype, I get:
  
   Periodic UIC Update Failed
  
   I haven't updated ports recently. Does anyone have an idea?
   I heard Skype was closing down old versions.
  
  
  I had received the following e-mail from Skype a few days ago:
  
  On Fri, Aug 8, 2014 at 7:53 PM, Skype norep...@emails.skype.com wrote:
  
   Your Skype for Linux version is being retired.
   Update today. »
   Can't see this email properly? Forgotten your password?
   Your Skype for Linux version is being retired. Update today.
   Dear swhetzel,
  
   We are now retiring older versions of Skype and it appears that at some
   point you signed into Skype with one of these. To continue signing into
   Skype on Linux you'll need to download the latest version. The new
   version comes with improved performance, the latest features and
   security updates, so you'll get the best possible Skype experience.
  
   If you're on the latest version of Skype, the above will not apply.
  
   Update now at http://www.skype.com/download.
  
  Someone will need to update the Skype port to the latest Linux version
  and see if it works on our current version of Linux emulation.
  
 
 I've read in various places (and tested myself with a couple of version on
 Linux) that any version before skype 4.3.0.37 will not connect.
 
 The skype port at: 
 https://github.com/vassilisl/freebsd-ports/tree/master/net-im/skype4
 will connect (if you use the f20 ports 
 https://github.com/vassilisl/freebsd-linux_base-f20 ;) )
 but it doesn't have sound working. Both xmj and I are working on getting
 that version of Skype on c6 and f20 linux emulation bases respectivelly,
 which basically means get it to talk to pulseaudio.
 
 If anyone has experience with that, please shout! :)
 
 Regards,
 Vassilis
 
 
 
-- 
Artyom Mirgorodskiy
___
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: net-im/skype-[devel] won't connect

2014-08-18 Thread Vassilis Laganakos
Hi Artyom,

On Mon, Aug 18, 2014 at 06:16:02PM +0300, Artyom Mirgorodskiy wrote:
 So I try again to run pulse audio and got the following error in syslog:
 linux: pid 95238 (pacat): syscall ppoll not implemented
 
 Anybody can help how to implement this syscall on linuxulator?
 
Didn't get the chance to update the thread on the work on this (albeit for
-f20). I have an implementation for that syscall, as well for fstatfs64, and
seems to be working. Just need to test it a bit more and I'll push it for
formal review and more testing :)

I did push the linux-f20-pulseaudio-libs and related packages in the git
repo for the -f20 libs the weekend.

Cheers,
Vassilis

 On Wednesday 13 August 2014 22:09:22 Vassilis Laganakos wrote:
  Hi,
  
  On Wed, Aug 13, 2014 at 10:47:25AM -0500, Scot Hetzel wrote:
   On Wed, Aug 13, 2014 at 10:38 AM, Kenta S. ken...@hush.com wrote:
Hello. This afternoon when I try to sign onto Skype, I get:
   
Periodic UIC Update Failed
   
I haven't updated ports recently. Does anyone have an idea?
I heard Skype was closing down old versions.
   
   
   I had received the following e-mail from Skype a few days ago:
   
   On Fri, Aug 8, 2014 at 7:53 PM, Skype norep...@emails.skype.com wrote:
   
Your Skype for Linux version is being retired.
Update today. »
Can't see this email properly? Forgotten your password?
Your Skype for Linux version is being retired. Update today.
Dear swhetzel,
   
We are now retiring older versions of Skype and it appears that at some
point you signed into Skype with one of these. To continue signing into
Skype on Linux you'll need to download the latest version. The new
version comes with improved performance, the latest features and
security updates, so you'll get the best possible Skype experience.
   
If you're on the latest version of Skype, the above will not apply.
   
Update now at http://www.skype.com/download.
   
   Someone will need to update the Skype port to the latest Linux version
   and see if it works on our current version of Linux emulation.
   
  
  I've read in various places (and tested myself with a couple of version on
  Linux) that any version before skype 4.3.0.37 will not connect.
  
  The skype port at: 
  https://github.com/vassilisl/freebsd-ports/tree/master/net-im/skype4
  will connect (if you use the f20 ports 
  https://github.com/vassilisl/freebsd-linux_base-f20 ;) )
  but it doesn't have sound working. Both xmj and I are working on getting
  that version of Skype on c6 and f20 linux emulation bases respectivelly,
  which basically means get it to talk to pulseaudio.
  
  If anyone has experience with that, please shout! :)
  
  Regards,
  Vassilis
  
  
  
 -- 
 Artyom Mirgorodskiy


signature.asc
Description: Digital signature


Re: Squid 33

2014-08-18 Thread Dr. Peter Voigt
Am Mon, 18 Aug 2014 16:43:38 +0200
schrieb Andrea Venturoli m...@netfence.it:

 Hello.
 
 Beware anyone updating www/squid33: latest update to this ports 
 overwrote my squid.conf.
 
 This might get annoying.
 
   bye
   av.

Yeah, thanks. I have just been wondering why Squid suddenly didn't
require authentication anymore. Your mail saved me a lot of time.

Regards,
Peter


signature.asc
Description: PGP signature


Re: [Patch] Using MACHINE_ARCH identifiers in pkg

2014-08-18 Thread Nathan Whitehorn


On 08/14/14 13:40, olli hauer wrote:

On 2014-08-14 21:42, Bryan Drewery wrote:

On 8/14/2014 2:38 PM, olli hauer wrote:

On 2014-08-14 17:35, Nathan Whitehorn wrote:

...


Something I've mentioned to Bapt a few times is that pkg needs a way to
have a list of accepted ABI strings. Then we could add both the old and
the new style as accepted (internally) so that old and new repositories
will continue to work.


Ups, rollback is not possible after the client database was updated.

Even by rollback and rebuild the package metadata the following error pops up.

~/pkg-static.old_ABI update -f
Updating repository catalogue
pkg-static: Repository str has a wrong packagesite, need to re-create database
Fetching meta.txz: 100% of 584 B
Fetching digests.txz: 100% of 43 kB
Fetching packagesite.txz: 100% of 138 kB

Adding new entries: 34%
pkg-static: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64

pkg-static: repository str contains packages with wrong ABI: FreeBSD:8:amd64
Adding new entries: 100%
pkg-static: Unable to update repository str



Hm. I'm not sure how to handle this. There are two places that emit hard 
errors in such cases: pkg-add, which is fine since we have a workaround 
there, and here. The check is at line 446 of libpkg/repo/binary/update.c 
(you can comment it out for testing). For this one, there does not seem 
to be any good solution and we need to find one since this is the same 
issue you ran into the upgrade path.


Here are the two options I see. They are similar to each other, and we 
could do both for some time.
1. Make an intermediate pkg that is otherwise unaltered but doesn't have 
this check during updates and keep it in the tree for some substantial 
length of time so most people have it by the time we want upgrades to 
the new ABI strings.
2. Set PKGNG_ALTABI globally on the ports tree for i386 and amd64 for 
some period of time so that all built packages get the current ABI 
identifiers rather than the new ones.


Any preference here? Or other options?



Roll back on the client
# ~/bin/pkg-static backup -r /var/backups/pkgng.db


Roll back on the build host:
- remove all packages that where created meanwhile with the patched pkg
   including pkg.
- reinstall unpatched pkg on the build host
- start a new build

By doing a manual cleanup I also found that packages containing the old ABI are 
not removed.

# ls -ltr
-rw-r--r--  2 root  wheel   2592992 Aug 14 21:10 openssl-1.0.1_15.txz
-rw-r--r--  2 root  wheel   1963944 Aug 14 21:11 subversion-1.8.10_1.txz

# ls -l openssl*
-rw-r--r--  3 root  wheel  2593488 Aug 11 17:31 openssl-1.0.1_14.txz
-rw-r--r--  2 root  wheel  2592992 Aug 14 21:10 openssl-1.0.1_15.txz


Is this on the build host or the client? In other words, is this a 
poudriere issue or a pkg one?



So the patch has more side affects ...

Anyway I'm happy to test new patches to get rid of the old ABI string ;)



Thanks for your testing so far!
-Nathan
___
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: Cacti staged and migration issue (was Re: FreeBSD unmaintained ports which are currently scheduled for deletion)

2014-08-18 Thread Adam McDougall
On 08/15/2014 14:16, Kurt Jaeger wrote:
 Hi!
 
 Consequently, I have no idea how to set the owner/group on those
 directories in stagedir.
 
 As can be seen, with some help I was able to find a solution.
 I also changed the patches to shebangfixes 8-}
 
 But: There's a real issue coming up in
 
 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192618#c13
 
 Can you have a look and probably provide a write-up on how to
 migrate a running cacti install to the new hier(7) setup ?
 

I've been using the updated port since last night on a new server
install, working well so far.  On my old server I would have had to
update the configs but I've been meaning to replace it anyway.  Thanks.

I think it would be a good idea copy or move the pkg-message updated
path tips to /usr/ports/UPDATING to increase chances of it being read.
___
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


Cant get gimp to use xsane with FreeBSD 10.-RELRASE

2014-08-18 Thread Mike Clarke

I've just upgraded from 9,1-RELEASE to 10.0-RELEASE

After deleting and reinstalling all packages I can't get gimp to use 
the xsane dialog. The option to use xsane doesn;t appear in the File - 
Create menu

The output from gimp --verbose shows the following problem:

Parsing '/home/mike/.gimp-2.8/pluginrc'
Querying plug-in: '/home/mike/.gimp-2.8/plug-ins/xsane'
/home/mike/.gimp-2.8/plug-ins/xsane: GIMP support missing
Terminating plug-in: '/home/mike/.gimp-2.8/plug-ins/xsane'
Writing '/home/mike/.gimp-2.8/pluginrc'

But xsane was built with gimp support

curlew:/home/mike% pkg query %n %Ok %Ov xsane gimp-app
xsane DOCS on
xsane GIMP on
xsane NLS on
gimp-app AA on
gimp-app DBUS on
gimp-app GHOSTSCRIPT off
gimp-app GVFS off
gimp-app HELPBROWSER on
gimp-app JASPER off
gimp-app LIBEXIF on
gimp-app LIBMNG on
gimp-app LIBRSVG2 on
gimp-app POPPLER on
gimp-app SIMD on
gimp-app WMF on

curlew:/home/mike% pkg info gimp-app xsane
gimp-app-2.8.10_3,1
Xsane-0.999_1

And I have the symbolic link in my plug-ins subdirectory.

curlew:/home/mike% ls -l ~/.gimp-2.8/plug-ins/
total 1
lrwxr-xr-x  1 mike  mike  20 18 Aug 15:17 xsane@ - 
/usr/local/bin/xsane

And the target exists

curlew:/home/mike% ls -l /usr/local/bin/xsane
-r-xr-xr-x  1 root  wheel  602240 18 Aug 20:06 /usr/local/bin/xsane*

I've tried this using packages and then by building gimp-app and xsane 
from ports with the same result each time.

I had no problems on 9.0RELEASE with the same package versions and 
build options so I'm wondering if we have an issue specific to 
10.RELEASE here.

curlew:/home/mike% uname -a
FreeBSD curlew.lan 10.0-RELEASE-p7 FreeBSD 10.0-RELEASE-p7 #0: Tue Jul  
8 06:37:44 UTC 2014 root@amd64-
builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64


-- 
Mike Clarke
___
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: [Patch] Using MACHINE_ARCH identifiers in pkg

2014-08-18 Thread olli hauer
On 2014-08-18 18:15, Nathan Whitehorn wrote:
 
 On 08/14/14 13:40, olli hauer wrote:
 On 2014-08-14 21:42, Bryan Drewery wrote:
 On 8/14/2014 2:38 PM, olli hauer wrote:
 On 2014-08-14 17:35, Nathan Whitehorn wrote:
 ...

 Something I've mentioned to Bapt a few times is that pkg needs a way to
 have a list of accepted ABI strings. Then we could add both the old and
 the new style as accepted (internally) so that old and new repositories
 will continue to work.

 Ups, rollback is not possible after the client database was updated.

 Even by rollback and rebuild the package metadata the following error pops 
 up.

 ~/pkg-static.old_ABI update -f
 Updating repository catalogue
 pkg-static: Repository str has a wrong packagesite, need to re-create 
 database
 Fetching meta.txz: 100% of 584 B
 Fetching digests.txz: 100% of 43 kB
 Fetching packagesite.txz: 100% of 138 kB

 Adding new entries: 34%
 pkg-static: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64

 pkg-static: repository str contains packages with wrong ABI: FreeBSD:8:amd64
 Adding new entries: 100%
 pkg-static: Unable to update repository str
 
 
 Hm. I'm not sure how to handle this. There are two places that emit hard 
 errors in such cases: pkg-add, which is fine since we have a workaround 
 there, and here. The check is at line 446 of libpkg/repo/binary/update.c (you 
 can comment it out for testing). For this one, there does not seem to be any 
 good solution and we need to find one since this is the same issue you ran 
 into the upgrade path.
 
 Here are the two options I see. They are similar to each other, and we could 
 do both for some time.
 1. Make an intermediate pkg that is otherwise unaltered but doesn't have this 
 check during updates and keep it in the tree for some substantial length of 
 time so most people have it by the time we want upgrades to the new ABI 
 strings.
 2. Set PKGNG_ALTABI globally on the ports tree for i386 and amd64 for some 
 period of time so that all built packages get the current ABI identifiers 
 rather than the new ones.
 
 Any preference here? Or other options?


Hi Nathan,

Your suggestion 2) could do the trick, at last for current ports.

I will see if I can do some additional tests the next days, specially with 
mixed ABI strings in the packages.

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


tinderbox seems broken after recent commits (python-related?)

2014-08-18 Thread Alexey Dokuchaev
hi there,

tinderbox is unable to build more-or-less complex ports for couple of days
now; both for 8.4/pkg_tools and 9.3/pkgng: it quietly exits with no package
produced and no logs generated, except build/build-name/make.0 that looks
always like this (modulo list of dependent packages, can be longer):

`python27-2.7.8_3.txz' is up to date.
`gettext-0.18.3.1_1.txz' is up to date.
`libiconv-1.14_3.txz' is up to date.
`indexinfo-0.2.txz' is up to date.
make: Graph cycles through `py27-pylib-1.4.20.txz'
make: Graph cycles through `py27-setuptools27-5.5.1.txz'
`pkgconf-0.9.6_1.txz' is up to date.
`pkg-1.3.6.txz' is up to date.

On stable/8, make(1) falls into endless loop, repeating these lines all
over again untill it dies via sig11.

Can it be related to the recent Python framework overhaul?  Any ideas how
to remedy the situation?  Thanks,

./danfe
___
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: tinderbox seems broken after recent commits (python-related?)

2014-08-18 Thread Shane Ambler
On 19/08/2014 13:26, Alexey Dokuchaev wrote: hi there,

 tinderbox is unable to build more-or-less complex ports for couple of days
 now; both for 8.4/pkg_tools and 9.3/pkgng: it quietly exits with no
package
 produced and no logs generated, except build/build-name/make.0 that
looks
 always like this (modulo list of dependent packages, can be longer):

 `python27-2.7.8_3.txz' is up to date.
 `gettext-0.18.3.1_1.txz' is up to date.
 `libiconv-1.14_3.txz' is up to date.
 `indexinfo-0.2.txz' is up to date.
 make: Graph cycles through `py27-pylib-1.4.20.txz'
 make: Graph cycles through `py27-setuptools27-5.5.1.txz'
 `pkgconf-0.9.6_1.txz' is up to date.
 `pkg-1.3.6.txz' is up to date.

 On stable/8, make(1) falls into endless loop, repeating these lines all
 over again untill it dies via sig11.

 Can it be related to the recent Python framework overhaul?  Any ideas how
 to remedy the situation?  Thanks,

 ./danfe

This was mentioned earlier on the tinderbox list ---


 Original Message 
Subject: Re: Graph cycles through in devel/p5-CPAN-Meta-Requirements
Date: Wed, 13 Aug 2014 20:47:26 +0930
From: Shane Ambler free...@shaneware.biz
To: Tomoyuki Sakurai tomoyu...@reallyenglish.com,
tinderbox-l...@marcuscom.com tinderbox-l...@marcuscom.com

On 13/08/2014 16:41, Tomoyuki Sakurai wrote:
 hi,
 
 just fyi, tinderbox users. devel/p5-CPAN-Meta-Requirements has a
 circular dependency on p5-CPAN-Meta. any port depending on
 p5-CPAN-Meta, munin-node in my case, cannot be built on tinderbox. the
 build silently fails as if there was no error.
 
 this will hit you hard if you build your packages and assume no error
 means no problem.
 
 a work around is commenting out TEST_DEPENDS line in
 devel/p5-CPAN-Meta-Requirements/Makefile.
 

I'm getting circular dependencies with python ports too.

Comment out the TEST_DEPENDS in devel/py-setuptools/Makefile to stop it
for now.

I think this started with changing USE_PYTHON to USES=python possibly
same for perl. Maybe mixing the two is the issue.



___
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