Re: FreeBSD ports you maintain which are out of date

2014-10-03 Thread Bartek Rutkowski
On Thu, Oct 2, 2014 at 4:27 PM, Bartek Rutkowski wrote: >> >> Port| Current version | New >> version >> +-+ >> graphics/geoserver | 2.1.1

Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread Baptiste Daroussin
Hi, As you may know, the ports tree currently provides two versions of the X.Org server and related pieces of software: 1. xserver 1.7, Mesa 7.6 and libdrm 2.4.17 2. xserver 1.12, Mesa 9.1 and libdrm 2.4.52 We are about to remove the older set. The primary reason is the maintenance cost. Th

Re: Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread Jean-Sébastien Pédron
On 03.10.2014 10:30, Baptiste Daroussin wrote: > Hi, > > As you may know, the ports tree currently provides two versions of the > X.Org server and related pieces of software: >1. xserver 1.7, Mesa 7.6 and libdrm 2.4.17 >2. xserver 1.12, Mesa 9.1 and libdrm 2.4.52 > > We are about to remov

py-imaging vs. py-pillow

2014-10-03 Thread Stefan Ehmann
According to freshports there are about 10 ports that depend on py-pilllow and 50 that depend on py-imaging. py-imaging conflicts with py-pilllow. E.g., calibre and xmbc cannot be installed at the same time. I noticed the problem because calibre switched to py-pilllow recently. There really

Re: Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread Claude Buisson
On 10/03/2014 10:30, Baptiste Daroussin wrote: Hi, As you may know, the ports tree currently provides two versions of the X.Org server and related pieces of software: 1. xserver 1.7, Mesa 7.6 and libdrm 2.4.17 2. xserver 1.12, Mesa 9.1 and libdrm 2.4.52 We are about to remove the older

Re: Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread René Ladan
2014-10-03 11:01 GMT+02:00 Claude Buisson : > On 10/03/2014 10:30, Baptiste Daroussin wrote: > >> Hi, >> >> As you may know, the ports tree currently provides two versions of the >> X.Org server and related pieces of software: >> 1. xserver 1.7, Mesa 7.6 and libdrm 2.4.17 >> 2. xserver 1.1

Re: Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread Jean-Sébastien Pédron
On 03.10.2014 11:01, Claude Buisson wrote: > NVIDIA does not exist in your world ? Hi! You're right, we forgot to mention NVIDIA. The NVIDIA port installs its own bits from the kernel module to the specific libGL.so. The notion of "UMS/KMS" doesn't exist and the port is made to work with all ver

Re: py-imaging vs. py-pillow

2014-10-03 Thread William Grzybowski
Coexist how? They are essentially the same package. I don't see how thats possible. py-imaging is deprecated, they should be switched to py-pillow and thats it. On Fri, Oct 3, 2014 at 6:08 AM, Stefan Ehmann wrote: > According to freshports there are about 10 ports that depend on py-pilllow > and

misc/getopt MFH r369764 to 2014Q4

2014-10-03 Thread Richard Frewin
Hi All, Sorry if this is in hand, but could someone please MFH r369764 (misc/getopt: "Cleanup *.o from tarball" from ports/194074) to the new 2014Q4 branch, as I can't build getopt for i386 at the moment. Cheers - Richard. ___ freebsd-ports@freebs

Re: py-imaging vs. py-pillow

2014-10-03 Thread Stefan Ehmann
On 03.10.2014 13:37, William Grzybowski wrote: Coexist how? They are essentially the same package. I don't see how thats possible. I meant that you should be able to install ports that depend on py-imaging and ports that depend on py-imaging at the same time. py-imaging is deprecated, they

INDEX build failed for 8.x

2014-10-03 Thread Ports Index build
INDEX build failed with errors: Generating INDEX-8 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- --- describe.biology --- --- describe.cad --- --- describe.chinese --- --- de

Re: py-imaging vs. py-pillow

2014-10-03 Thread Diane Bruce
On Fri, Oct 03, 2014 at 02:01:32PM +0200, Stefan Ehmann wrote: > On 03.10.2014 13:37, William Grzybowski wrote: > > Coexist how? They are essentially the same package. I don't see how > > thats possible. > > I meant that you should be able to install ports that depend on > py-imaging and ports th

Re: update to 37.0.2062.124 fails due to conflict (jpeg/jpeg-turbo)

2014-10-03 Thread René Ladan
(redirecting to freebsd-ports@ ) 2014-09-30 22:34 GMT+02:00 hugo : [..] > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > Checking integrity... done (1 conflicting) > Checking integrity... done (0 conflicting) > The following 5 pack

Re: Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread Lena
> From: Baptiste Daroussin > there's a know regression with syscons and kernel video > drivers: you can't switch back to a console once an X.Org session is > started. A new console driver called vt(4) fixes this issue Does 10.1 with vt in text mode support _all_ the following in rc.conf? scrnma

Re: Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread Ed Maste
On 3 October 2014 10:00, wrote: > > Does 10.1 with vt in text mode support _all_ the following in rc.conf? > > scrnmap="koi8-u2cp866u" > font8x16="cp866u-8x16" > allscreens_flags="80x30" > keymap="ru.koi8-r" No, in text mode vt currently has support for cp437 only. vt(4) uses UTF-8 only right n

Re: Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread Chris H
> Hi, > > As you may know, the ports tree currently provides two versions of the > X.Org server and related pieces of software: >1. xserver 1.7, Mesa 7.6 and libdrm 2.4.17 >2. xserver 1.12, Mesa 9.1 and libdrm 2.4.52 > > We are about to remove the older set. The primary reason is the > main

INDEX now builds successfully on 8.x

2014-10-03 Thread Ports Index build
___ 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: Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread Baptiste Daroussin
On Fri, Oct 03, 2014 at 07:47:23AM -0700, Chris H wrote: > > Hi, > > > > As you may know, the ports tree currently provides two versions of the > > X.Org server and related pieces of software: > >1. xserver 1.7, Mesa 7.6 and libdrm 2.4.17 > >2. xserver 1.12, Mesa 9.1 and libdrm 2.4.52 > > >

Re: Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread Marat N.Afanasyev
Jean-Sébastien Pédron wrote: On 03.10.2014 11:01, Claude Buisson wrote: NVIDIA does not exist in your world ? Hi! You're right, we forgot to mention NVIDIA. The NVIDIA port installs its own bits from the kernel module to the specific libGL.so. The notion of "UMS/KMS" doesn't exist and the po

Re: Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread Chris H
> On Fri, Oct 03, 2014 at 07:47:23AM -0700, Chris H wrote: >> > Hi, >> > >> > As you may know, the ports tree currently provides two versions of the >> > X.Org server and related pieces of software: >> >1. xserver 1.7, Mesa 7.6 and libdrm 2.4.17 >> >2. xserver 1.12, Mesa 9.1 and libdrm 2.4.

Re: Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread Lena
> From: Jean-S?bastien P?dron > NVIDIA users are not impacted by this change at all. x11/nvidia-driver-304 (for older videochips) too? > the NVIDIA driver (like > old Intel/AMD UMS drivers) takes care of restoring the GPU in a state > that syscons can use (eg. VGA text mode on a PC). What abou

RE: Removal of legacy X.Org (aka non-WITH_NEW_XORG)

2014-10-03 Thread Michael Jung
I hope this may be an additional data point. I also had grave issues with NEW_XORG. When I did experience a problem 99% of the time the computer locked up. My uptime was never more than a 24 hour period. No crash dumps, black screen, no keyboard light activity in toggling caps lock. Howeve

Re: Xtide Broken on X86 X64 current

2014-10-03 Thread Lowell Gilbert
Manfred Antar writes: > I've done more research on this. Mac OSX has a patch so this will compile > with clang without errors. > This is probably the best for current as clang is default compiler. > This patch from OSX works on 11.0 current Interesting. The patch is basically setting a compiler

Re: py-imaging vs. py-pillow

2014-10-03 Thread Marcus von Appen
On, Fri Oct 03, 2014, Stefan Ehmann wrote: > According to freshports there are about 10 ports that depend on > py-pilllow and 50 that depend on py-imaging. > > py-imaging conflicts with py-pilllow. E.g., calibre and xmbc cannot be > installed at the same time. > > > I noticed the problem because c

[no subject]

2014-10-03 Thread 2602398231
Hey == This mobile text message is brought to you by AT&T ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

[no subject]

2014-10-03 Thread 2602398231
Just seeing who this is my contacts. Were jumbled and only coded in contact list == This mobile text message is brought to you by AT&T ___ freebsd-ports@freebsd.org mailing list http://lists

Re: Question about ports config dialog

2014-10-03 Thread Matt Reimer
Ah, thanks. Matt On Wed, Oct 1, 2014 at 8:17 AM, Matthew Seaman wrote: > On 10/01/14 16:01, Matt Reimer wrote: > > What does the "+" mean in the config dialogs that appear while building > > ports? Does it indicate a setting that's checked by default, or a > > recommendation, or ...? > > It mea