Re: CFT: Update to xf86-video-ati 7.5.0

2014-10-31 Thread Jean-Sébastien Pédron
On 30.10.2014 21:12, Christian Weisgerber wrote:
 What do you mean?  Upgrading from xf86-video-ati 7.2.0 to 7.5.0 was
 a one-time event.

Yes, but I was wondering if your problem was still there from time to
time (ie. not related to the update).

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature


Re: CFT: Update to xf86-video-ati 7.5.0

2014-10-31 Thread Jean-Sébastien Pédron
On 30.10.2014 23:21, Miguel Clara wrote:
 What I don't understand is how could this could work before. Are you
 sure you had xf86-video-ati 7.2.0 installed?
 
 However I don't understand why you say it worked before cause what I've
 reported before and now is that It didn't work (with ATI)
 
 I still have the old xorg log, from back when I reported this in the list,
 if I'm not mistaken this is the one:
 http://filebin.net/zs1iia21yv/Xorg.radeonkmserror.log
 
 So It was not working with ATI even before 7.2,a and with 7.2 I also can't
 get xorg to start, although I was getting a black screen at some point, but
 the log states Xorg crashed!
 
 maybe in this new report I've somehow gave the impression that It worked,
 but I only works with the Intel card!

That's my fault, I understood that it was working, then you upgraded to
7.5.0 and X broke. But no, as you say, your older log shows that the
same problem existed before the upgrade. Sorry :)

Could you please download the following file:
https://raw.githubusercontent.com/freebsd/freebsd-ports-graphics/xserver-1.14/x11-servers/xorg-server/files/patch-hw_xfree86_modes_xf86Crtc.c

Put it here:
/usr/ports/x11-servers/xorg-server/files/patch-hw_xfree86_modes_xf86Crtc.c

And rebuild xorg-server 1.12 with WITH_DEBUG=1 and test again (with
xf86-video-ati 7.5.0 installed)?

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature


Fwd: Re: pkg 1.4 freeze please test test test!

2014-10-31 Thread Juan Ramón Molina Menor

The problem I have now is that when trying to install new packages,

pkg insists on being downgraded. Locking it has not helped.

# pkg install vim-lite
Updating FreeBSD repository catalogue...
pkg: Repository FreeBSD has a wrong packagesite, need to re-create database
Fetching meta.txz: 100%   944 B   0.9k/s00:01
Fetching packagesite.txz: 100%5 MB 296.7k/s00:18
Processing entries: 100%
FreeBSD repository update completed. 23724 packages processed
Updating FreeBSD_new_xorg repository catalogue...
pkg: Repository FreeBSD_new_xorg has a wrong packagesite, need to re-create data
base
Fetching meta.txz: 100%   944 B   0.9k/s00:01
Fetching packagesite.txz: 100%  192 KB 196.3k/s00:01
Processing entries: 100%
FreeBSD_new_xorg repository update completed. 799 packages processed
New version of pkg detected; it needs to be installed first.
Checking integrity... done (0 conflicting)
The following 1 packages will be affected (of 0 checked):

Installed packages to be DOWNGRADED:
 pkg: 1.4.0.a3 - 1.3.8_3 [FreeBSD]

The operation will free 8 MB.



There is also that wrong packagesite message.

What am I doing wrong?

# cat /etc/make.conf
WITH_NEW_XORG=YES
WITH_GALLIUM=YES
WITH_PKGNG=YES
WITH_PKG=devel


What version of freebsd are you on I would bet 9.1 where the bootstrap was dumb
and may have created for you a bad /usr/local/etc/pkg.conf


No, I’m on 10.0-RELEASE:

# uname -a
FreeBSD Marianne.Juan.home 10.0-RELEASE-p10 FreeBSD 10.0-RELEASE-p10 #0:
Mon Oct 20 12:38:37 UTC 2014
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386


for the fact that pkg wants to be downgraded I ll track the bug.

Do you have net-snmp installed?


No.

# pkg info net-snmp
pkg: No package(s) matching net-snmp


# pkg -vv
Version : 1.4.0.alpha3
PKG_DBDIR = /var/db/pkg;
PKG_CACHEDIR = /var/cache/pkg;
PORTSDIR = /usr/ports;
INDEXDIR = ;
INDEXFILE = INDEX-10;
HANDLE_RC_SCRIPTS = false;
ASSUME_ALWAYS_YES = false;
REPOS_DIR [
/etc/pkg/,
/usr/local/etc/pkg/repos/,
]
PLIST_KEYWORDS_DIR = ;
SYSLOG = true;
ABI = FreeBSD:10:i386;
ALTABI = freebsd:10:x86:32;
DEVELOPER_MODE = false;
VULNXML_SITE = http://vuxml.freebsd.org/freebsd/vuln.xml.bz2;;
FETCH_RETRY = 3;
PKG_PLUGINS_DIR = /usr/local/lib/pkg/;
PKG_ENABLE_PLUGINS = true;
PLUGINS [
]
DEBUG_SCRIPTS = false;
PLUGINS_CONF_DIR = /usr/local/etc/pkg/;
PERMISSIVE = false;
REPO_AUTOUPDATE = true;
NAMESERVER = ;
EVENT_PIPE = ;
FETCH_TIMEOUT = 30;
UNSET_TIMESTAMP = false;
SSH_RESTRICT_DIR = ;
PKG_ENV {
}
PKG_SSH_ARGS = ;
DEBUG_LEVEL = 0;
ALIAS {
all-depends = query %dn-%dv;
annotations = info -A;
build-depends = info -qd;
download = fetch;
iinfo = info -i -g -x;
isearch = search -i -g -x;
leaf = query -e \%a == 0\ \%n-%v\;
leaf = query -e \%a == 0\ \%n-%v\;
list = info -ql;
origin = info -qo;
provided-depends = info -qb;
raw = info -R;
required-depends = info -qr;
shared-depends = info -qB;
show = info -f -k;
size = info -sq;
}
CUDF_SOLVER = ;
SAT_SOLVER = ;
RUN_SCRIPTS = true;
CASE_SENSITIVE_MATCH = false;
LOCK_WAIT = 1;
LOCK_RETRIES = 5;
SQLITE_PROFILE = false;
WORKERS_COUNT = 0;
READ_LOCK = false;
PLIST_ACCEPT_DIRECTORIES = false;
IP_VERSION = 0;
AUTOMERGE = true;


Repositories:
  FreeBSD: {
url : pkg+http://pkg.FreeBSD.org/FreeBSD:10:i386/latest;,
enabled : yes,
mirror_type : SRV,
signature_type  : FINGERPRINTS,
fingerprints: /usr/share/keys/pkg
  }
  FreeBSD_new_xorg: {
url :
pkg+http://pkg.FreeBSD.org/FreeBSD:10:i386/new_xorg;,
enabled : yes,
mirror_type : SRV,
signature_type  : FINGERPRINTS,
fingerprints: /usr/share/keys/pkg
  }


Hope it helps,
Juan


I have upgraded to 1.4.0.a4 and the problem persists: it insist on 
downgrading to pkg 1.3.8_3 when I try 'pkg upgrade' or 'pkg install 
somepackage'.


Best regards,
Juan
___
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

Bug 193424 has no been committed - why?

2014-10-31 Thread Robert Backhaus
As the maintainer, I gave the go-ahead for this PR to be committed well
over a month ago. I sent a message to koobs@ to see why it wasn't
committed, and have not received a reply.

Can a committer please take this and commit it, or tell me what I need to
do to get it committed?

Thanks,
Robert.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193424
___
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

2014-10-31 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
+-+
sysutils/am-utils   | 6.1.5   | 6.2
+-+


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


Re: CFT: Update to xf86-video-ati 7.5.0

2014-10-31 Thread Miguel Clara
On Fri, Oct 31, 2014 at 9:08 AM, Jean-Sébastien Pédron dumbb...@freebsd.org
 wrote:

 On 30.10.2014 23:21, Miguel Clara wrote:
  What I don't understand is how could this could work before. Are you
  sure you had xf86-video-ati 7.2.0 installed?
 
  However I don't understand why you say it worked before cause what I've
  reported before and now is that It didn't work (with ATI)
 
  I still have the old xorg log, from back when I reported this in the
 list,
  if I'm not mistaken this is the one:
  http://filebin.net/zs1iia21yv/Xorg.radeonkmserror.log
 
  So It was not working with ATI even before 7.2,a and with 7.2 I also
 can't
  get xorg to start, although I was getting a black screen at some point,
 but
  the log states Xorg crashed!
 
  maybe in this new report I've somehow gave the impression that It worked,
  but I only works with the Intel card!

 That's my fault, I understood that it was working, then you upgraded to
 7.5.0 and X broke. But no, as you say, your older log shows that the
 same problem existed before the upgrade. Sorry :)

 Could you please download the following file:

 https://raw.githubusercontent.com/freebsd/freebsd-ports-graphics/xserver-1.14/x11-servers/xorg-server/files/patch-hw_xfree86_modes_xf86Crtc.c

 Put it here:
 /usr/ports/x11-servers/xorg-server/files/patch-hw_xfree86_modes_xf86Crtc.c

 And rebuild xorg-server 1.12 with WITH_DEBUG=1 and test again (with
 xf86-video-ati 7.5.0 installed)?


Ok using xorg-1.12, and xf86-video-ati-7.5 (both WITH_DEBUG)

Still fails, sudo gdb Xorg Xorg.core shows:

[]
#0  0x00080205ccaa in thr_kill () from /lib/libc.so.7
#1  0x000802133f09 in abort () from /lib/libc.so.7
#2  0x0062e4be in OsAbort () at utils.c:1198
#3  0x004a6880 in ddxGiveUp (error=EXIT_ERR_ABORT) at
xf86Init.c:1009
#4  0x004a6998 in AbortDDX (error=EXIT_ERR_ABORT) at xf86Init.c:1053
#5  0x00637ae6 in AbortServer () at log.c:476
#6  0x006367fd in FatalError (f=0x659396 Caught signal %d (%s).
Server aborting\n) at log.c:611
#7  0x0062b9d8 in OsSigHandler (signo=11, sip=0x7fffe570,
unused=0x7fffe200) at osinit.c:146
#8  0x0008010b84f6 in swapcontext () from /lib/libthr.so.3
#9  0x0008010b80ec in sigaction () from /lib/libthr.so.3
#10 signal handler called
#11 0x004eb710 in SetCompatOutput (config=0x8034e32c0) at
xf86Crtc.c:1829
#12 0x004eb1ea in xf86SetScrnInfoModes (scrn=0x803512400) at
xf86Crtc.c:1843
#13 0x004ebf13 in xf86InitialConfiguration (scrn=0x803512400,
canGrow=1) at xf86Crtc.c:2503
#14 0x00080474153e in drmmode_pre_init (pScrn=0x803512400,
drmmode=0x8034c7258, cpp=4) at drmmode_display.c:1757
#15 0x00080473c89a in RADEONPreInit_KMS (pScrn=0x803512400, flags=0) at
radeon_kms.c:946
#16 0x004a4e19 in InitOutput (pScreenInfo=0x8acdb0, argc=1,
argv=0x7fffec18) at xf86Init.c:586
#17 0x00424c66 in main (argc=1, argv=0x7fffec18,
envp=0x7fffec28) at main.c:20


last lines of Xorg.0.log

 tail -20 /var/log/Xorg.0.log

[ 77453.777]ABI class: X.Org Video Driver, version 12.1
[ 77453.777] (II) RADEON(0): KMS Color Tiling: enabled
[ 77453.777] (II) RADEON(0): KMS Color Tiling 2D: enabled
[ 77453.777] (II) RADEON(0): KMS Pageflipping: enabled
[ 77453.777] (II) RADEON(0): SwapBuffers wait for vsync: enabled
[ 77453.778] (WW) RADEON(0): No outputs definitely connected, trying
again...
[ 77453.778] (WW) RADEON(0): Unable to find connected outputs - setting
1024x768 initial framebuffer
[ 77453.778] (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless
otherwise stated.
[ 77453.778] Segmentation fault at address 0x0
[ 77453.778]
Fatal server error:
[ 77453.778] Caught signal 11 (Segmentation fault). Server aborting
[ 77453.778]
[ 77453.778]
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.


--
 Jean-Sébastien Pédron


___
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: CFT: Update to xf86-video-ati 7.5.0

2014-10-31 Thread Jean-Sébastien Pédron
On 31.10.2014 11:34, Miguel Clara wrote:
 #11 0x004eb710 in SetCompatOutput (config=0x8034e32c0) at
 xf86Crtc.c:1829

A crash on line 1829 means that the patch was not applied. With the
patch, the same line is at 1832.

Double-check how you named the new file in the
/usr/ports/x11-servers/xorg-server/files directory. It must start with
the patch- prefix.

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature


[CFT] Simgear and Flightgear updates to 3.2.0

2014-10-31 Thread Ganael LAPLANCHE
Hi everyone,

If you are a Flightgear user, I would be pleased to get feedback on the
upcoming update to version 3.2.0.

Patches are available here :

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

Thanks :)

--
Ganael LAPLANCHE ganael.laplan...@martymac.org
http://www.martymac.org | http://contribs.martymac.org
FreeBSD: martymac marty...@freebsd.org, http://www.FreeBSD.org
___
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


Welcome to Twitter, Brackett VanSchaick!

2014-10-31 Thread Twitter via freebsd-ports
Brackett VanSchaick,
Welcome to Twitter.

Take 2 minutes to make Twitter work better for you.

We have one suggestion: follow more people. Yes, more. Following is how you 
build your home timeline. Building a great timeline is at the heart of making 
Twitter work. By building a timeline that reflects you and your interests, 
you'll see how quickly Twitter becomes an invaluable part of your life.


Suggestions for you:


Thomas Abthorpe @tabthorpe
N-Space dimensional nerd, with many likes and interests
https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2Ftabthorpe%3Ft%3D1%26cn%3Db2xkX3dlbGNvbWVfZW1haWxfcG9ydGVk%26sig%3Dfaa0869292ab3fd50f42fa704c8cf7acc140e790%26al%3D1%26iid%3Da4477ff2adb545a39d1281b222a816ef%26autoactions%3D1414762598%26uid%3D2851874679%26nid%3D244%2B316%2B20141030amp;t=1amp;cn=b2xkX3dlbGNvbWVfZW1haWxfcG9ydGVkamp;sig=22651e74a18bc35a77fc1b6c998e455c21bf95d1amp;iid=a4477ff2adb545a39d1281b222a816efamp;uid=2851874679amp;nid=244+316+20141030

Nico Mommaerts @mr_dfuse
Dad, coder, biker, gamer
https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2Fmr_dfuse%3Ft%3D1%26cn%3Db2xkX3dlbGNvbWVfZW1haWxfcG9ydGVk%26sig%3D926757865abc0abd4bcf60598aa6105ec14d5b4e%26al%3D1%26iid%3Da4477ff2adb545a39d1281b222a816ef%26autoactions%3D1414762598%26uid%3D2851874679%26nid%3D244%2B320%2B20141030amp;t=1amp;cn=b2xkX3dlbGNvbWVfZW1haWxfcG9ydGVkamp;sig=04cc59e069e8fb0dc90d846b946bb29c9d7f3c2camp;iid=a4477ff2adb545a39d1281b222a816efamp;uid=2851874679amp;nid=244+320+20141030

Marco Dola @DolaMarco

https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2FDolaMarco%3Ft%3D1%26cn%3Db2xkX3dlbGNvbWVfZW1haWxfcG9ydGVk%26sig%3D6452c1ad76ef5422b9af2cec2e30d88b82eb272e%26al%3D1%26iid%3Da4477ff2adb545a39d1281b222a816ef%26autoactions%3D1414762598%26uid%3D2851874679%26nid%3D244%2B324%2B20141030amp;t=1amp;cn=b2xkX3dlbGNvbWVfZW1haWxfcG9ydGVkamp;sig=b8e2fa17407abc485883f05013d2203a28fa7ad1amp;iid=a4477ff2adb545a39d1281b222a816efamp;uid=2851874679amp;nid=244+324+20141030


We have more great suggestions for you. Check out more people to follow:
https://twitter.com/who_to_follow
___
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: zabbix

2014-10-31 Thread Paul Pathiakis via freebsd-ports
That's excellent.  I'm a little confused as to how to apply the patch.  
At what level should I apply this in the current ports tree?  At this 
point there is nothing about zabbix24 in the tree. Should I apply at 
/usr/ports/net-mgmt?


Also, it may be beneficial to start a cleanup process in ports about 
zabbix at this point:


zabbix (1.8??!!)
zabbix2
zabbix22

And name the current working release (2.4) to be simply 'zabbix'.

Also, remove zabbix 2.0, leaving only 2.2 and 2.4.  (Of course announce 
it in UPDATES so that people can upgrade properly)


Does this sound useful?  (I've recently come across people putting out 
instructions of how to install zabbix and zabbix2 on FreeBSD 10 - It 
looks like they are doing initial installs.  They are missing out on a 
lot of features of the newer revisions/version.)


Thank you for reading,

P


On 10/30/2014 19:23, Pakhom Golynga wrote:

Hi,
Please find https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194104

30.10.2014 23:32, Paul Pathiakis пишет:

Hi!

Is there a change that there will be an upgrade to Zabbix to the 2.4 
version or later?


I see that ports/pkgs has 2.0 and 2.2.

Thank you, it's most appreciated.

P.




___
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: CFT: Update to xf86-video-ati 7.5.0

2014-10-31 Thread Miguel Clara
On Fri, Oct 31, 2014 at 11:00 AM, Jean-Sébastien Pédron 
dumbb...@freebsd.org wrote:

 On 31.10.2014 11:34, Miguel Clara wrote:
  #11 0x004eb710 in SetCompatOutput (config=0x8034e32c0) at
  xf86Crtc.c:1829

 A crash on line 1829 means that the patch was not applied. With the
 patch, the same line is at 1832.

 Double-check how you named the new file in the
 /usr/ports/x11-servers/xorg-server/files directory. It must start with
 the patch- prefix.


Xorg.0.log:
% tail -40 /var/log/Xorg.0.log
[   207.575]compiled for 1.12.4, module version = 2.5.0
[   207.575]ABI class: X.Org Video Driver, version 12.1
[   207.575] (II) RADEON(0): KMS Color Tiling: enabled
[   207.575] (II) RADEON(0): KMS Color Tiling 2D: enabled
[   207.575] (II) RADEON(0): KMS Pageflipping: enabled
[   207.575] (II) RADEON(0): SwapBuffers wait for vsync: enabled
[   207.576] (WW) RADEON(0): No outputs definitely connected, trying
again...
[   207.576] (WW) RADEON(0): Unable to find connected outputs - setting
1024x768 initial framebuffer
[   207.576] (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless
otherwise stated.
[   207.576] (II) RADEON(0): mem size init: gart size :1fdef000 vram size:
s:4000 visible:3fcc
[   207.576] (II) RADEON(0): EXA: Driver will allow EXA pixmaps in VRAM
[   207.576] (==) RADEON(0): DPI set to (96, 96)
[   207.576] (II) Loading sub module fb
[   207.576] (II) LoadModule: fb
[   207.576] (II) Loading /usr/local/lib/xorg/modules/libfb.so
[   207.576] (II) Module fb: vendor=X.Org Foundation
[   207.576]compiled for 1.12.4, module version = 1.0.0
[   207.576]ABI class: X.Org ANSI C Emulation, version 0.4
[   207.576] (II) Loading sub module ramdac
[   207.577] (II) LoadModule: ramdac
[   207.577] (II) Module ramdac already built-in
[   207.577] (EE) RADEON(0): No modes.
[   207.577] (II) UnloadModule: radeon
[   207.577] (II) UnloadSubModule: fb
[   207.577] (II) Unloading fb
[   207.577] (II) UnloadSubModule: exa
[   207.577] (II) Unloading exa
[   207.577] (II) UnloadSubModule: dri2
[   207.577] (II) Unloading dri2
[   207.577] (EE) Screen(s) found, but none have a usable configuration.
[   207.577]
Fatal server error:
[   207.577] no screens found
[   207.577]
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
[   207.577] Please also check the log file at /var/log/Xorg.0.log for
additional information.
[   207.577]
[   207.580] Server terminated with error (1). Closing log file.



dmesg:

iic7: I2C generic I/O on iicbus7
info: [drm] Radeon Display Connectors
info: [drm] Internal thermal controller with fan control
info: [drm] radeon: power management initialized
No connectors reported connected with modes
info: [drm] Cannot find any crtc or sizes - going 1024x768
info: [drm] fb mappable at 0xA0142000
info: [drm] vram apper at 0xA000
info: [drm] size 3145728
info: [drm] fb depth is 24
info: [drm]pitch is 4096
fbd0 on drmn0
VT: Replacing driver vga with new fb.
info: [drm] Initialized radeon 2.29.0 2008052


 --
 Jean-Sébastien Pédron


___
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: CFT: Update to xf86-video-ati 7.5.0

2014-10-31 Thread Jean-Sébastien Pédron
On 31.10.2014 15:35, Miguel Clara wrote:
 [   207.577] (EE) RADEON(0): No modes.
 [   207.577] (II) UnloadModule: radeon
 [   207.577] (II) UnloadSubModule: fb
 [   207.577] (II) Unloading fb
 [   207.577] (II) UnloadSubModule: exa
 [   207.577] (II) Unloading exa
 [   207.577] (II) UnloadSubModule: dri2
 [   207.577] (II) Unloading dri2
 [   207.577] (EE) Screen(s) found, but none have a usable configuration.

Cool, the crash is fixed.

Could you please post the whole Xorg.log?

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature


Re: CFT: Update to xf86-video-ati 7.5.0

2014-10-31 Thread Miguel Clara
On Fri, Oct 31, 2014 at 2:41 PM, Jean-Sébastien Pédron dumbb...@freebsd.org
 wrote:

 On 31.10.2014 15:35, Miguel Clara wrote:
  [   207.577] (EE) RADEON(0): No modes.
  [   207.577] (II) UnloadModule: radeon
  [   207.577] (II) UnloadSubModule: fb
  [   207.577] (II) Unloading fb
  [   207.577] (II) UnloadSubModule: exa
  [   207.577] (II) Unloading exa
  [   207.577] (II) UnloadSubModule: dri2
  [   207.577] (II) Unloading dri2
  [   207.577] (EE) Screen(s) found, but none have a usable configuration.

 Cool, the crash is fixed.

 Could you please post the whole Xorg.log?

 http://filebin.ca/1fdab69tzLua/Xorg.0.log

About the  but none have a usable configuration does this  mean I can
have a xorg.conf that would work with the ati card, or does it simple mean
we are one step closer?

--
 Jean-Sébastien Pédron


___
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: CFT: Update to xf86-video-ati 7.5.0

2014-10-31 Thread Jean-Sébastien Pédron
On 31.10.2014 15:56, Miguel Clara wrote:
 About the  but none have a usable configuration does this  mean I can
 have a xorg.conf that would work with the ati card, or does it simple mean
 we are one step closer?

Currently, no update to xorg-server or xf86-video-ati will make your
card work, because we lack the support in the kernel.

However, now you can keep both xf86-video-ati and xf86-video-intel
installed and the server won't crash :) And one day in the future, the
Radeon card will come to life, though definitely not for today's
Halloween :)

With power consumption in mind, I would probably don't install
xf86-video-ati at all for now, so radeonkms isn't loaded.

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature


Re: CFT: Update to xf86-video-ati 7.5.0

2014-10-31 Thread Miguel Clara
On Fri, Oct 31, 2014 at 3:25 PM, Jean-Sébastien Pédron dumbb...@freebsd.org
 wrote:

 On 31.10.2014 15:56, Miguel Clara wrote:
  About the  but none have a usable configuration does this  mean I can
  have a xorg.conf that would work with the ati card, or does it simple
 mean
  we are one step closer?

 Currently, no update to xorg-server or xf86-video-ati will make your
 card work, because we lack the support in the kernel.

 However, now you can keep both xf86-video-ati and xf86-video-intel
 installed and the server won't crash :) And one day in the future, the
 Radeon card will come to life, though definitely not for today's
 Halloween :)

 With power consumption in mind, I would probably don't install
 xf86-video-ati at all for now, so radeonkms isn't loaded.


Agreed, but ideally one could change as needed... ofc it will always mean
restart Xorg... IFAIK  you can do it in Linux.

In any case this laptop has the battery dead already so its AC always.

On another note, as I've refereed in the other report, my perfect scenario
for this laptop would be using the intel on host and pass-trough the ati to
virtualized guest... vbox is not and option and AFAIK bhyve is far from
that too, but maybe Xen will be a solution soon :)

But for now I'll just keep testing with this one ;)

thanks for you're time on this btw, please continue the good work

--
 Jean-Sébastien Pédron


___
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.4 freeze please test test test!

2014-10-31 Thread René Ladan

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 29-10-2014 00:19, Baptiste Daroussin wrote:
 Hi all,

 We are starting the release process of pkg 1.4, we want to have a
better release
 process than with every single previous version of pkg. For that we
will need
 you help!

 pkg-devel has been updated to the latest version of pkg as of alpha2.

 Changes you can expect in pkg 1.4 are the following:
 - Loads of bug fixes
 - Stricter checking of the path passed via the plist
 - Removal of the bundled libyaml
 - new --raw-format to chose the output format for info -R and search -R
 - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become
FreeBSD:10:amd64)
   the old ABI is available as a fallback in ALTABI
 - pkg check now support a quiet mode
 - new 3 way merge code (stolen from the fossil-scm) to allow automerging
   configuration files
 - new @config keyword to mark a file as a config file (during
   upgrade/reinstallation it will try to merge the configuration with
the one the
   user may have modified) an option AUTOMERGE is available to prevent
   automerging if automerge fails a .pkgnew file will be created along
with the
   untouched user version of the configuration
 - The update procedure has been improved and speed up a lot (in
particular for
   machine with low resources)
 - The unique identifier has been modified to be pkgname meaning now
ports can be
   moved in new categories without having to be considered a different
package
 - Only libraries starting by lib* are added to the provided libraries
 - General speed up of all operations

 We need help in testing, but we also need help in writing regression
tests !
 The more we have tests the more stable the releases will be.
Here is an upgrade failure from pkg 1.3.8_3 to pkg 1.4.0.a4 (I probably
didn't follow the book), while chrooting into a 10.0-RELEASE ezjail:

# pkg install -f pkg-1.4.0.a4.txz
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Updating database digests format: 100%
Checking integrity... done (1 conflicting)
New version of pkg detected; it needs to be installed first.
Checking integrity... done (0 conflicting)
The following 2 packages will be affected (of 0 checked):

New packages to be INSTALLED:
pkg: 1.4.0.a4

Installed packages to be REINSTALLED:
pkg-1.3.8_3 (direct conflict changed)

The process will require 17 MB more space.
2 MB to be downloaded.

Proceed with this action? [y/N]: y
Fetching pkg-1.3.8_3.txz: 100%2 MB   2.3M/s00:01 
[1/2] Deleting pkg-1.3.8_3: 100%
pkg: unlinkat(usr/local/etc/bash_completion.d/_pkg.bash): No such file
or directory
pkg: unlinkat(usr/local/etc/periodic/daily/411.pkg-backup): No such file
or directory
pkg: unlinkat(usr/local/etc/periodic/daily/490.status-pkg-changes): No
such file or directory
pkg: unlinkat(usr/local/etc/periodic/security/410.pkg-audit): No such
file or directory
pkg: unlinkat(usr/local/etc/periodic/security/460.pkg-checksum): No such
file or directory
pkg: unlinkat(usr/local/etc/periodic/weekly/400.status-pkg): No such
file or directory
pkg: unlinkat(usr/local/etc/pkg.conf.sample): No such file or directory
pkg: unlinkat(usr/local/include/pkg.h): No such file or directory
pkg: unlinkat(usr/local/lib/libpkg.a): No such file or directory
pkg: unlinkat(usr/local/lib/libpkg.so): No such file or directory
pkg: unlinkat(usr/local/lib/libpkg.so.3): No such file or directory
pkg: unlinkat(usr/local/lib/libpkg.so.3.0.0): No such file or directory
pkg: unlinkat(usr/local/libdata/pkgconfig/pkg.pc): No such file or directory
pkg: unlinkat(usr/local/man/man3/pkg_printf.3.gz): No such file or directory
pkg: unlinkat(usr/local/man/man3/pkg_repos.3.gz): No such file or directory
pkg: unlinkat(usr/local/man/man5/pkg-repository.5.gz): No such file or
directory
pkg: unlinkat(usr/local/man/man5/pkg.conf.5.gz): No such file or directory
pkg: unlinkat(usr/local/man/man8/pkg-add.8.gz): No such file or directory
pkg: unlinkat(usr/local/man/man8/pkg-annotate.8.gz): No such file or
directory
pkg: unlinkat(usr/local/man/man8/pkg-audit.8.gz): No such file or directory
pkg: unlinkat(usr/local/man/man8/pkg-autoremove.8.gz): No such file or
directory
pkg: unlinkat(usr/local/man/man8/pkg-backup.8.gz): No such file or directory
pkg: unlinkat(usr/local/man/man8/pkg-check.8.gz): No such file or directory
pkg: unlinkat(usr/local/man/man8/pkg-clean.8.gz): No such file or directory
pkg: unlinkat(usr/local/man/man8/pkg-config.8.gz): No such file or directory
pkg: unlinkat(usr/local/man/man8/pkg-convert.8.gz): No such file or
directory
pkg: unlinkat(usr/local/man/man8/pkg-create.8.gz): No such file or directory
pkg: unlinkat(usr/local/man/man8/pkg-delete.8.gz): No such file or directory
pkg: unlinkat(usr/local/man/man8/pkg-fetch.8.gz): No such file or directory
pkg: unlinkat(usr/local/man/man8/pkg-info.8.gz): No such file or directory
pkg: unlinkat(usr/local/man/man8/pkg-install.8.gz): No such file or
directory
pkg: 

Re: CFT: Update to xf86-video-ati 7.5.0

2014-10-31 Thread Jean-Sébastien Pédron
On 31.10.2014 16:53, Miguel Clara wrote:
 Agreed, but ideally one could change as needed... ofc it will always mean
 restart Xorg... IFAIK  you can do it in Linux.

Yes, when we grow support for video cards only used to render things,
you won't have to restart anything.

 On another note, as I've refereed in the other report, my perfect scenario
 for this laptop would be using the intel on host and pass-trough the ati to
 virtualized guest... vbox is not and option and AFAIK bhyve is far from
 that too, but maybe Xen will be a solution soon :)

I don't know for Xen, but even on Linux, GPU virtualization in KVM isn't
for tomorrow. Red Hat is working on the subject through the Virgil
project[1].

 thanks for you're time on this btw, please continue the good work

You're welcome :) You helped a lot to diagnose the problem and test the
patch! An update to xserver 1.14 is almost ready for a CFT. This will
include the patch you tested.

[1] https://virgil3d.github.io/

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature


Re: CFT: Update to xf86-video-ati 7.5.0

2014-10-31 Thread Miguel Clara
On Fri, Oct 31, 2014 at 4:24 PM, Jean-Sébastien Pédron dumbb...@freebsd.org
 wrote:

 On 31.10.2014 16:53, Miguel Clara wrote:
  Agreed, but ideally one could change as needed... ofc it will always mean
  restart Xorg... IFAIK  you can do it in Linux.

 Yes, when we grow support for video cards only used to render things,
 you won't have to restart anything.

  On another note, as I've refereed in the other report, my perfect
 scenario
  for this laptop would be using the intel on host and pass-trough the ati
 to
  virtualized guest... vbox is not and option and AFAIK bhyve is far from
  that too, but maybe Xen will be a solution soon :)

 I don't know for Xen, but even on Linux, GPU virtualization in KVM isn't
 for tomorrow. Red Hat is working on the subject through the Virgil
 project[1].

Just to add some info on this about xen:
http://wiki.xen.org/wiki/Xen_VGA_Passthrough_Tested_Adapters



  thanks for you're time on this btw, please continue the good work

 You're welcome :) You helped a lot to diagnose the problem and test the
 patch! An update to xserver 1.14 is almost ready for a CFT. This will
 include the patch you tested.

 [1] https://virgil3d.github.io/

 --
 Jean-Sébastien Pédron


___
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.4 freeze please test test test!

2014-10-31 Thread René Ladan
On 31-10-2014 16:57, René Ladan wrote:
 
 On 29-10-2014 00:19, Baptiste Daroussin wrote:
 Hi all,
 
 We are starting the release process of pkg 1.4, we want to have a
 better release
 process than with every single previous version of pkg. For that we
 will need
 you help!
 
 pkg-devel has been updated to the latest version of pkg as of alpha2.
 
 Changes you can expect in pkg 1.4 are the following:
 - Loads of bug fixes
 - Stricter checking of the path passed via the plist
 - Removal of the bundled libyaml
 - new --raw-format to chose the output format for info -R and search -R
 - ABI is now follwing MACHINE_ARCH (freebsd:10:x86:64 become
 FreeBSD:10:amd64)
   the old ABI is available as a fallback in ALTABI
 - pkg check now support a quiet mode
 - new 3 way merge code (stolen from the fossil-scm) to allow automerging
   configuration files
 - new @config keyword to mark a file as a config file (during
   upgrade/reinstallation it will try to merge the configuration with
 the one the
   user may have modified) an option AUTOMERGE is available to prevent
   automerging if automerge fails a .pkgnew file will be created along
 with the
   untouched user version of the configuration
 - The update procedure has been improved and speed up a lot (in
 particular for
   machine with low resources)
 - The unique identifier has been modified to be pkgname meaning now
 ports can be
   moved in new categories without having to be considered a different
 package
 - Only libraries starting by lib* are added to the provided libraries
 - General speed up of all operations
 
 We need help in testing, but we also need help in writing regression
 tests !
 The more we have tests the more stable the releases will be.
 Here is an upgrade failure from pkg 1.3.8_3 to pkg 1.4.0.a4 (I probably
 didn't follow the book), while chrooting into a 10.0-RELEASE ezjail:
 
 # pkg install -f pkg-1.4.0.a4.txz
 Updating FreeBSD repository catalogue...
 FreeBSD repository is up-to-date.
 All repositories are up-to-date.
 Updating database digests format: 100%
 Checking integrity... done (1 conflicting)
 New version of pkg detected; it needs to be installed first.
 Checking integrity... done (0 conflicting)
 The following 2 packages will be affected (of 0 checked):
 
 New packages to be INSTALLED:
 pkg: 1.4.0.a4
 
 Installed packages to be REINSTALLED:
 pkg-1.3.8_3 (direct conflict changed)
 
 The process will require 17 MB more space.
 2 MB to be downloaded.
 
 Proceed with this action? [y/N]: y
 Fetching pkg-1.3.8_3.txz: 100%2 MB   2.3M/s00:01 
 [1/2] Deleting pkg-1.3.8_3: 100%
 pkg: unlinkat(usr/local/etc/bash_completion.d/_pkg.bash): No such file
 or directory
 pkg: unlinkat(usr/local/etc/periodic/daily/411.pkg-backup): No such file
 or directory
 pkg: unlinkat(usr/local/etc/periodic/daily/490.status-pkg-changes): No
 such file or directory
 pkg: unlinkat(usr/local/etc/periodic/security/410.pkg-audit): No such
 file or directory
 pkg: unlinkat(usr/local/etc/periodic/security/460.pkg-checksum): No such
 file or directory
 pkg: unlinkat(usr/local/etc/periodic/weekly/400.status-pkg): No such
 file or directory
 pkg: unlinkat(usr/local/etc/pkg.conf.sample): No such file or directory
 pkg: unlinkat(usr/local/include/pkg.h): No such file or directory
 pkg: unlinkat(usr/local/lib/libpkg.a): No such file or directory
 pkg: unlinkat(usr/local/lib/libpkg.so): No such file or directory
 pkg: unlinkat(usr/local/lib/libpkg.so.3): No such file or directory
 pkg: unlinkat(usr/local/lib/libpkg.so.3.0.0): No such file or directory
 pkg: unlinkat(usr/local/libdata/pkgconfig/pkg.pc): No such file or directory
 pkg: unlinkat(usr/local/man/man3/pkg_printf.3.gz): No such file or directory
 pkg: unlinkat(usr/local/man/man3/pkg_repos.3.gz): No such file or directory
 pkg: unlinkat(usr/local/man/man5/pkg-repository.5.gz): No such file or
 directory
 pkg: unlinkat(usr/local/man/man5/pkg.conf.5.gz): No such file or directory
 pkg: unlinkat(usr/local/man/man8/pkg-add.8.gz): No such file or directory
 pkg: unlinkat(usr/local/man/man8/pkg-annotate.8.gz): No such file or
 directory
 pkg: unlinkat(usr/local/man/man8/pkg-audit.8.gz): No such file or directory
 pkg: unlinkat(usr/local/man/man8/pkg-autoremove.8.gz): No such file or
 directory
 pkg: unlinkat(usr/local/man/man8/pkg-backup.8.gz): No such file or directory
 pkg: unlinkat(usr/local/man/man8/pkg-check.8.gz): No such file or directory
 pkg: unlinkat(usr/local/man/man8/pkg-clean.8.gz): No such file or directory
 pkg: unlinkat(usr/local/man/man8/pkg-config.8.gz): No such file or directory
 pkg: unlinkat(usr/local/man/man8/pkg-convert.8.gz): No such file or
 directory
 pkg: unlinkat(usr/local/man/man8/pkg-create.8.gz): No such file or directory
 pkg: unlinkat(usr/local/man/man8/pkg-delete.8.gz): No such file or directory
 pkg: unlinkat(usr/local/man/man8/pkg-fetch.8.gz): No such file or directory
 pkg: unlinkat(usr/local/man/man8/pkg-info.8.gz): No such file or directory
 pkg: 

Re: Bug 193424 has no been committed - why?

2014-10-31 Thread Kurt Jaeger
Hi!

 As the maintainer, I gave the go-ahead for this PR to be committed well
 over a month ago. I sent a message to koobs@ to see why it wasn't
 committed, and have not received a reply.
 
 Can a committer please take this and commit it, or tell me what I need to
 do to get it committed?

I dont speak for koobs@, but I assume from the PRs I'm trying to work
on that it's mostly overload on the side of the committers, in general.

-- 
p...@opsec.eu+49 171 3101372 6 years to go !
___
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


net-mgmt/icinga2: Icinga Web is not working: Error: Could not read object configuration data!

2014-10-31 Thread O. Hartmann

On CURRENT (most recent), I run net-mgmt/icinga2. Setup ran smooth, I also set 
up the IDO
for PostgreSQL. Checking whether icinga2 logs data to the PostgreSQL database 
resulted
positive.

I try to install/configure a Web Interface a sdescribed in the Icinga2 docs. 
IDO is a
prerequiste for Icinga Web (I'm not using Icinga Web 2!).

For that purpose, I installed net/mgmt/icinga (which contains the web 
interface). I made
the proper changes to /usr/local/etc/icinga/cgi.cfg as reported in this HowTo:
http://lists.freebsd.org/pipermail/freebsd-ports/2014-June/093372.html. Please 
see also
https://forums.freebsd.org/threads/icinga2-network-monitoring.47106/. Via
icinga2-enable-feature I also enabled all requested modules as described in the 
Icinga2
docs.

So far. Having doen EXACTLY as suggested, I do not get any kind of 
Webinterface. The web
browser (Mozilla Firefox) reports always: Error: Could not read object 
configuration data!

There is something missing.

Is someone using Icinga2 with the classical Web and has followed these 
instructions and
gets a different result?

Please CC me.

Kind regards,
Oliver


pgpgiET08OzNe.pgp
Description: OpenPGP digital signature


Reducing the size of the ports tree (brainstorm v2)

2014-10-31 Thread Baptiste Daroussin
Hi all,

tijl@ spotted an interesting point, distinfo and pkg-descr files files
convenient are taking a lot of space for free, we can reduce the size of the
while ports tree by a factor 2 by simply merging them into one of the other
files (Makefile and/or pkg-plist) from my testing it really devides
significantly the size of the tree.

Problem is how to merge them if we want to.

What we do not want to loose:
- Easyness of parsing distinfo
- Easyness to get informations about the description

so far I have not been able to figure out a user friendly way

Ideas I got so far only concerns pkg-descr:
Adding an entry in the Makefile for the WWW:
WWW= bla
or an entry in the plist: @www http...

for the description the Makefile is not suitable as multi line entry in
Makefiles are painful
Maybe a new keyword:
@descr EOD
mydesc
in 
multiline
EOD

which could easily be added to the plist parser in pkg. But I'm do not find that
very friendly in particular for make(1) to extract the data.

Concerning the distinfo I have no idea.

so this mail is a call of ideas :), if nothing nice ideas is found we will just
do nothing here :)

regards,
Bapt


pgpHpdw6bUZ2g.pgp
Description: PGP signature


pkg install trouble again

2014-10-31 Thread Jeffrey Bouquet via freebsd-ports
Continuing with the latest pkg2ng failure to actually convert  import another
local.sqlite  pipe to a pkg install [   ] -f -y ...

I deleted a few ports to save space.  Then,
Continuing with the reinstall of not converted but installed reinstalls ...

The following bug persists after a reboot:



pkg install -f nettle(securty/nettle)

New packages to be INSTALLED (i HAD JUST removed these)

gcc49
gutenprint-base
openjdk
mysql55-client
csound
libgda4

Installed packages to be REINSTALLED

nettle...

A few others down the list in n* did not demand reinstalls... so the sql code 
or some file
somewhere is buggy and can be fixed I hope...   

[
Along with the pkg2ng code which started it all as per the previous emails (v9) 
which maybe
only needs a prerequisite file in the environment, an environment variable, or 
is incomplete
and/or buggy... in the v9 upgrades...  I have no idea.  
]
___
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 install trouble again

2014-10-31 Thread Baptiste Daroussin
On Fri, Oct 31, 2014 at 11:56:34AM -0700, Jeffrey Bouquet via freebsd-ports 
wrote:
 Continuing with the latest pkg2ng failure to actually convert  import 
 another
 local.sqlite  pipe to a pkg install [   ] -f -y ...
 
 I deleted a few ports to save space.  Then,
 Continuing with the reinstall of not converted but installed reinstalls ...
 
 The following bug persists after a reboot:
 
 
 
 pkg install -f nettle(securty/nettle)
 
 New packages to be INSTALLED (i HAD JUST removed these)
 
 gcc49
 gutenprint-base
 openjdk
 mysql55-client
 csound
 libgda4

The above means something in your installation requires those ports, it is just
trying to make the dependency chain sain again.
 
 Installed packages to be REINSTALLED
 
 nettle...
 
 A few others down the list in n* did not demand reinstalls... so the sql code 
 or some file
 somewhere is buggy and can be fixed I hope...   

Can you host somewhere your /var/db/pkg/local.sqlite so I can study your
specific case?

Bapt


pgpeK1P7BpYER.pgp
Description: PGP signature


graphics/png fail

2014-10-31 Thread Beeblebrox
graphics/png has been failing like this for some time, and I would go around
the problem by fetching the newer binary then re-starting poudriere. That
trick did not work this time, so now I'm stuck.

Same error when building on host (non-poudriere). Port used to compile on
host, but no longer. Host  poudriere make.conf are identical.

Running tests...
/usr/local/bin/ctest --force-new-ctest-process 
Test project /wrkdirs/usr/ports/graphics/png/work/libpng-1.5.19
Start 1: pngtest
1/2 Test #1: pngtest ..   Passed0.01 sec
Start 2: pngvalid
2/2 Test #2: pngvalid .***Failed5.88 sec

50% tests passed, 1 tests failed out of 2

Total Test time (real) =   5.89 sec

The following tests FAILED:
  2 - pngvalid (Failed)
Errors while running CTest



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/graphics-png-fail-tp5961223.html
Sent from the freebsd-ports mailing list archive at Nabble.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


graphics/libEGL graphics/libglapi fail: Localization?

2014-10-31 Thread Beeblebrox
On my system (poudriere jail and host) , both ports fail with same error
(ca/LC_MESSAGES/options.mo).  Host  poudriere make.conf are identical.
Disabling below setting in make.conf made no difference.
###  OPTIONS_UNSET=  DOCS EXAMPLES NLS IPV6

ERROR:
===  Building for libEGL-10.3.2
gmake[1]: Entering directory
'/wrkdirs/usr/ports/graphics/libEGL/work/Mesa-10.3.2/src/mesa/drivers/dri/common/xmlpool'
cd ../../../../../..  gmake  am--refresh
cd ../../../../../..  gmake  am--refresh
Updating (ca) ca/LC_MESSAGES/options.mo from ca.po.
msgfmt: not found
Makefile:638: recipe for target 'ca/LC_MESSAGES/options.mo' failed
gmake[1]: *** [ca/LC_MESSAGES/options.mo] Error 127
gmake[1]: Leaving directory
'/wrkdirs/usr/ports/graphics/libEGL/work/Mesa-10.3.2/src/mesa/drivers/dri/common/xmlpool'
*** Error code 2

The poudriere error logs for both also have some strange entres for config
stage:

OpenGL:  yes (ES1: no ES2: no)
OpenVG:  no
OSMesa:  no
DRI platform:drm
DRI drivers: no
llvm:no
Gallium: no

While make.conf has these enabled:
  WITH_NEW_XORG=yes
  WITH_GALLIUM=yes
  WITHOUT_NOUVEAU=yes




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/graphics-libEGL-graphics-libglapi-fail-Localization-tp5961228.html
Sent from the freebsd-ports mailing list archive at Nabble.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: graphics/png fail

2014-10-31 Thread Michael Jung

On 2014-10-31 15:33, Beeblebrox wrote:
graphics/png has been failing like this for some time, and I would go 
around
the problem by fetching the newer binary then re-starting poudriere. 
That

trick did not work this time, so now I'm stuck.

Same error when building on host (non-poudriere). Port used to compile 
on

host, but no longer. Host  poudriere make.conf are identical.

Running tests...
/usr/local/bin/ctest --force-new-ctest-process
Test project /wrkdirs/usr/ports/graphics/png/work/libpng-1.5.19
Start 1: pngtest
1/2 Test #1: pngtest ..   Passed0.01 sec
Start 2: pngvalid
2/2 Test #2: pngvalid .***Failed5.88 sec

50% tests passed, 1 tests failed out of 2

Total Test time (real) =   5.89 sec

The following tests FAILED:
  2 - pngvalid (Failed)
Errors while running CTest



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/graphics-png-fail-tp5961223.html
Sent from the freebsd-ports mailing list archive at Nabble.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


While this does not directly help you, it passes the test for me on 
11.0-CURRENT #4 r273857:


PORTNAME=   png
PORTVERSION=1.5.19


snip
Running tests...
Test project /usr/ports/graphics/png/work/libpng-1.5.19
Start 1: pngtest
1/2 Test #1: pngtest ..   Passed0.03 sec
Start 2: pngvalid
2/2 Test #2: pngvalid .   Passed   31.60 sec

100% tests passed, 0 tests failed out of 2

Total Test time (real) =  31.74 sec
===  Staging for png-1.5.19
/bin/mkdir -p 
/usr/ports/graphics/png/work/stage/usr/local/include/libpng
/bin/mkdir -p 
/usr/ports/graphics/png/work/stage/usr/local/libdata/pkgconfig

===   Generating temporary packing list





___
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: graphics/libEGL graphics/libglapi fail: Localization?

2014-10-31 Thread Koop Mast

On 31-10-2014 20:39, Beeblebrox wrote:

On my system (poudriere jail and host) , both ports fail with same error
(ca/LC_MESSAGES/options.mo).  Host  poudriere make.conf are identical.
Disabling below setting in make.conf made no difference.
###  OPTIONS_UNSET=  DOCS EXAMPLES NLS IPV6

ERROR:
===  Building for libEGL-10.3.2
gmake[1]: Entering directory
'/wrkdirs/usr/ports/graphics/libEGL/work/Mesa-10.3.2/src/mesa/drivers/dri/common/xmlpool'
cd ../../../../../..  gmake  am--refresh
cd ../../../../../..  gmake  am--refresh
Updating (ca) ca/LC_MESSAGES/options.mo from ca.po.
msgfmt: not found
Makefile:638: recipe for target 'ca/LC_MESSAGES/options.mo' failed
gmake[1]: *** [ca/LC_MESSAGES/options.mo] Error 127
gmake[1]: Leaving directory
'/wrkdirs/usr/ports/graphics/libEGL/work/Mesa-10.3.2/src/mesa/drivers/dri/common/xmlpool'
*** Error code 2

The poudriere error logs for both also have some strange entres for config
stage:

OpenGL:  yes (ES1: no ES2: no)
OpenVG:  no
OSMesa:  no
DRI platform:drm
DRI drivers: no
llvm:no
Gallium: no

While make.conf has these enabled:
   WITH_NEW_XORG=yes
   WITH_GALLIUM=yes
   WITHOUT_NOUVEAU=yes



This should have been fixed by 
https://svnweb.freebsd.org/changeset/ports/371048 .

___
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: graphics/libEGL graphics/libglapi fail: Localization?

2014-10-31 Thread Beeblebrox
Koop:
 This should have been fixed by 
 https://svnweb.freebsd.org/changeset/ports/371048 .
As usual, at latest revision of ports.

But I did make a mistake when posting:
Compiles on host, NOT in poudriere (without disabling OPTIONS_UNSET= NLS).

I decided to try on a un-merged tree (update and skip gnome3 merge)
# poudriere bulk -j 11amd graphics/png
gets built.

Re-trying with gnome3 merged tree = fails.

-- 
FreeBSD_amd64_11-Current_RadeonKMS




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/graphics-libEGL-graphics-libglapi-fail-Localization-tp5961228p5961250.html
Sent from the freebsd-ports mailing list archive at Nabble.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: CFT: Update to xf86-video-ati 7.5.0

2014-10-31 Thread Christian Weisgerber
Jean-Sébastien Pédron:

  What do you mean?  Upgrading from xf86-video-ati 7.2.0 to 7.5.0 was
  a one-time event.
 
 Yes, but I was wondering if your problem was still there from time to
 time (ie. not related to the update).

I don't know, I haven't restarted the X server since.

I guess I shouldn't have brought it up in the first place.  It's
not important, possibly a fluke, and has just caused confusion.

Maybe it wasn't clear in the Xorg.0.log snippet I sent, but from
comparing log files, the actual error was this:

[351790.259] drmOpenByBusid: Interface 1.4 failed, trying 1.1
...
[351790.259] (EE) RADEON(0): [drm] failed to set drm interface version.
[351790.259] (EE) RADEON(0): Kernel modesetting setup failed

To me this means nothing, but I thought it might be something obvious
for the people working on X11.

-- 
Christian naddy Weisgerber  na...@mips.inka.de
___
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: graphics/libEGL graphics/libglapi fail: Localization?

2014-10-31 Thread Beeblebrox
Another Correction :((

* The un-merged tree (with gnome3) trial was with graphics/png, not with these 
ports, my mistake.
* These ports compile on host, but not in poudriere.
* No modification to make.conf needed for host side compile.

-- 
FreeBSD_amd64_11-Current_RadeonKMS




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/graphics-libEGL-graphics-libglapi-fail-Localization-tp5961228p5961269.html
Sent from the freebsd-ports mailing list archive at Nabble.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: graphics/libEGL graphics/libglapi fail: Localization?

2014-10-31 Thread Beeblebrox
On a completely clean ports tree,

# poudriere bulk -j s11a graphics/libEGL graphics/libglapi

fails for both ports.

-- 
FreeBSD_amd64_11-Current_RadeonKMS




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/graphics-libEGL-graphics-libglapi-fail-Localization-tp5961228p5961278.html
Sent from the freebsd-ports mailing list archive at Nabble.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: Reducing the size of the ports tree (brainstorm v2)

2014-10-31 Thread Tijl Coosemans
On Fri, 31 Oct 2014 19:56:21 +0100 Baptiste Daroussin b...@freebsd.org wrote:
 Hi all,
 
 tijl@ spotted an interesting point, distinfo and pkg-descr files files
 convenient are taking a lot of space for free, we can reduce the size of the
 while ports tree by a factor 2 by simply merging them into one of the other
 files (Makefile and/or pkg-plist) from my testing it really devides
 significantly the size of the tree.
 
 Problem is how to merge them if we want to.
 
 What we do not want to loose:
 - Easyness of parsing distinfo
 - Easyness to get informations about the description
 
 so far I have not been able to figure out a user friendly way
 
 Ideas I got so far only concerns pkg-descr:
 Adding an entry in the Makefile for the WWW:
 WWW= bla
 or an entry in the plist: @www http...
 
 for the description the Makefile is not suitable as multi line entry in
 Makefiles are painful
 Maybe a new keyword:
 @descr EOD
 mydesc
 in 
 multiline
 EOD
 
 which could easily be added to the plist parser in pkg. But I'm do not find 
 that
 very friendly in particular for make(1) to extract the data.
 
 Concerning the distinfo I have no idea.
 
 so this mail is a call of ideas :), if nothing nice ideas is found we will 
 just
 do nothing here :)

For distinfo I was thinking about something like this in the Makefile:

DIST_FILES= FOO BAR

FOO_FILE=   foo-1.0
FOO_SITES=  http://www.example.com/foo/
FOO_SIZE=   12345
FOO_SHA256= 0123456789abcdef.

BAR_FILE=   bar-2.0
BAR_SITES=  http://www.example.com/bar/
BAR_SIZE=   54321
BAR_SHA256= .fedcba9876543210

If bsd.port.mk then contained this:
DIST_FILES?=DIST
DIST_FILE?= 
${PORTNAME}-${DISTVERSIONPREFIX}${DISTVERSION}${DISTVERSIONSUFFIX}

Then for ports with a single distfile named after PORTNAME (the large
majority), the above would reduce to:

DIST_SITES= http://www.example.com/foo/
DIST_SIZE=  12345
DIST_SHA256=0123456789abcdef.

Also, if BAR_SITES is the same as FOO_SITES you can use somthing like
BAR_SITES=${FOO_SITES} of course.


pkg-descr and pkg-plist will be around for a while I think but maybe pkg
could support an alternative syntax that is similar to the manifest file
included in the package.  This file (named Manifest maybe?) would include
a comment, description, install/deinstall scripts and a list of files and 
directories like this (copied from https://github.com/freebsd/pkg):

comment: Short package description
desc: |-
  Long package description
  goes here
www: http:///www.example.com/
files: |-
  bin/foo
  lib/bar
dirs: |-
  some/dir
scripts:
  post-install: |-
#!/bin/sh
echo post-install
  pre-install: |-
#!/bin/sh
echo pre-install
___
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 local repo path bug after multiple solver iterations

2014-10-31 Thread Nick Rogers
Hello,

I opened this issue on pkg github the other day. Hoping someone on this
list may have some input.

https://github.com/freebsd/pkg/issues/1070

Thanks,

-Nick
___
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/dansguardian revival?

2014-10-31 Thread Nick Rogers
On Tue, Oct 21, 2014 at 6:29 PM, Chris H bsd-li...@bsdforge.com wrote:

 On Tue, 21 Oct 2014 09:39:30 +0200 Marko Cupać marko.cu...@mimar.rs
 wrote

  On Mon, 20 Oct 2014 17:47:19 -0700
  Chris H bsd-li...@bsdforge.com wrote:
 
   Unless theirs any objection. I'll take it. I'll open a pr(1)
   with a shar(1) ready, in about an hour.
  
   --Chris
 
  Nice to hear that dansguardian will be back in ports. I also used it
  for years in combination with www/squid33 without problem. I was
  compiling it from ports, and the trick was to compile squid33 first,
  and dansguardian only after, as dansguardian would only check existence
  of /use/local/bin/squid, and if it was already there, no matter which
  version, it would happily compile, install and work.

 Right. But there's ${STAGE} to deal with, as well. I may
 make sqid34 the DEPENDS (I'm still testing).
 I'm also working with the -devel version, and will likely
 convert it to the (un)devel version, as there is less user
 overhead involved -- RESTRICTED/COPYRIGHT/LICENSE/{...}

 Should be able to post a complete version, sometime
 tomorrow.


Hey Chris. Any luck getting your new dansguardian port to work? I can't
find a PR for it. Just wondering if theres anything I can do to help test
or if it would be worth my while to just submit a PR with the last-known
www/dansguardian for the time being. Thanks.

-Nick


 --Chris


  --
  Marko Cupać
  https://www.mimar.rs
  ___
  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@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@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Reducing the size of the ports tree (brainstorm v2)

2014-10-31 Thread Erich Dollansky
Hi,

On Fri, 31 Oct 2014 19:56:21 +0100
Baptiste Daroussin b...@freebsd.org wrote:

 tijl@ spotted an interesting point, distinfo and pkg-descr files files
 convenient are taking a lot of space for free, we can reduce the
 size of the while ports tree by a factor 2 by simply merging them
 into one of the other files (Makefile and/or pkg-plist) from my
 testing it really devides significantly the size of the tree.
 
it is some 50 000 small files.

 Problem is how to merge them if we want to.
 
 What we do not want to loose:
 - Easyness of parsing distinfo
 - Easyness to get informations about the description
 
Could they be put into a single file with a format like:

[/usr/ports/www/firefox]
descr=some text which can span
line
distinfo=SHA256 (firefox-33.0.source.tar.bz2) =
1018c2fae8c54c8a45f5a3ce348a2617a3f8039a789b09b7cfa5a27be069b229
SIZE = (firefox-33.0.source.tar.bz2) = 155177527

It is a bit old fashioned but will fulfil the requirements but will add
just one new layer.

Erich
___
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: py27-pytz-2014.7,1

2014-10-31 Thread LuKreme
On 30 Oct 2014, at 00:18 , LuKreme krem...@kreme.com wrote:
 Got this error running postmaster -a -x postfix
 
 ===  Installing for py27-pytz-2014.7,1
 ===  Checking if py27-pytz already installed
 ===   Registering installation for py27-pytz-2014.7,1 as automatic
 pkg-static: Plist error, directory listed as a file: 
 lib/python2.7/site-packages/pytz-2014.7-py2.7.egg-info
 *** [fake-pkg] Error code 74

Anything I can do about this?


-- 
In England 100 miles is a long distance. In the US 100 years is a long
time

___
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: Postfix file ownership problem

2014-10-31 Thread Sahil Tandon
On Tue, 2014-10-21 at 09:20:24 +0200, Jakob Breivik Grimstveit wrote:

 Why do I get this error about files with wrong ownership? Tried
 reinstalling, but it did not help...

I am not sure; I have not seen this before and no one else has reported
it.

Can you reproduce the problem with only one Postfix port installed?

 $ pkg info|grep -i postfix
 postfix-2.11.1_4,1 Secure alternative to widely-used Sendmail
 postfix-base-2.12.20140709_2,4 Secure alternative to widely-used Sendmail

-- 
Sahil Tandon
___
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: Reducing the size of the ports tree (brainstorm v2)

2014-10-31 Thread Darren Pilgrim

On 10/31/2014 11:56 AM, Baptiste Daroussin wrote:

tijl@ spotted an interesting point, distinfo and pkg-descr files files
convenient are taking a lot of space for free, we can reduce the size of the
while ports tree by a factor 2 by simply merging them into one of the other
files (Makefile and/or pkg-plist) from my testing it really devides
significantly the size of the tree.



Ideas I got so far only concerns pkg-descr:
Adding an entry in the Makefile for the WWW:
WWW= bla
or an entry in the plist: @www http...


I really do like

DESCR=Some relatively short amount of text that describes the port \
  in more detail than COMMENT can do. This could be multiple \
  sentences and broken across lines.

We have multi-line entries all over the place with things like long 
commands in pre- and post-install targets.  Since pkg-descr tends to be 
a write-once file, I think it's a pretty tiny amount of pain for shaving 
off that many files.  If you're really are worried about making 
maintainers do non-natural line breaks for readability, add a make 
reflowdescr target or add something to porttools that does it for us.


The reason I like having this stuff in the Makefile is that you can do 
something like this:


# make -C /usr/ports/foo/bar -V DESCR


Concerning the distinfo I have no idea.


Could we do something similar to dependency lists?  For example:

DISTINFO= example1.tbz:size:{SHA256}hash \
  example2.tar.gz:size:{SHA256}hash

In the simple case where DISTFILES is one generated filename:

DISTINFO= ${DISTFILES}:size:{SHA256}hash

___
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: Reducing the size of the ports tree (brainstorm v2)

2014-10-31 Thread Alfred Perlstein

On 10/31/14, 11:56 AM, Baptiste Daroussin wrote:

Hi all,

tijl@ spotted an interesting point, distinfo and pkg-descr files files
convenient are taking a lot of space for free, we can reduce the size of the
while ports tree by a factor 2 by simply merging them into one of the other
files (Makefile and/or pkg-plist) from my testing it really devides
significantly the size of the tree.

Problem is how to merge them if we want to.

What we do not want to loose:
- Easyness of parsing distinfo
- Easyness to get informations about the description

so far I have not been able to figure out a user friendly way

Ideas I got so far only concerns pkg-descr:
Adding an entry in the Makefile for the WWW:
WWW= bla
or an entry in the plist: @www http...

for the description the Makefile is not suitable as multi line entry in
Makefiles are painful
Maybe a new keyword:
@descr EOD
mydesc
in
multiline
EOD

which could easily be added to the plist parser in pkg. But I'm do not find that
very friendly in particular for make(1) to extract the data.

Concerning the distinfo I have no idea.

so this mail is a call of ideas :), if nothing nice ideas is found we will just
do nothing here :)

regards,
Bapt


Have you asked sjg about enhancing our make(1) to make HEREDOCs inside 
makefiles cleaner/nicer?


That would be best idea imo.  Then you could get rid of multiple files 
and merge into makefiles.  Maybe even eventually the patchfiles as well.


I had some basic thoughts on this, one trick would be to do like 
perl(1)'s DATA section of scripts.

http://stackoverflow.com/questions/13463509/the-data-syntax-in-perl

Other option is to make a separate shar(1)-like file to contain all meta 
data and add targets to deterministically create/delete this file, this 
file could include patches, description, plist and everything.  In fact 
it could contain the makefile itself...


Just some random thoughts that may/may-not find useful.

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