Re: HEADS UP: 5.6 ports lock approaching

2014-07-22 Thread Christian Weisgerber
On 2014-07-22, Stuart Henderson  wrote:

> The main release-critical thing I know about is dovecot.

Yes.

Other known breakage of varying importance:
* boehm-gc doesn't build on sparc64.
* Some mono ports have been left broken since the mono update.
* openimageio picks up an installed opencv during the build, causing
  breakage in dependent ports.
* Every build I see a few new KDE errors.  I guess I should do a run
  with dpb -r to flush out more dependency issues.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de



Re: HEADS UP: 5.6 ports lock approaching

2014-07-22 Thread Stuart Henderson
On 2014/07/21 22:03, Christian Weisgerber wrote:
> We are quickly approaching ports lock for the 5.6 release.
> 
> No new ports.
> 
> No updates for the sake of updating.
> 
> If you have fixes, or fixes tied to updates, that are important and
> that you think should still go in, you'll need to convince espie@ /
> jasper@ / naddy@ / sthen@ first.
> 
> This is also the last chance to TEST packages and report problems.
> Anything that won't get fixed real soon will remain broken for the
> release.
> 
> -- 
> Christian "naddy" Weisgerber  na...@mips.inka.de
> 

The main release-critical thing I know about is dovecot.



Re: HEADS UP: 5.6 ports lock approaching

2014-07-21 Thread Edd Barrett
On Mon, Jul 21, 2014 at 10:03:59PM +0200, Christian Weisgerber wrote:
> This is also the last chance to TEST packages and report problems.
> Anything that won't get fixed real soon will remain broken for the
> release.

wxMaxima is currently broken with what looks like a wxWidgets bug, but
someone who knows some C++ should take a second look.

Details in my recent post on ports@

-- 
Best Regards
Edd Barrett

http://www.theunixzoo.co.uk



Re: HEADS UP: 5.6 ports lock approaching

2014-07-21 Thread Ian McWilliam

On 22/07/2014 6:03 AM, Christian Weisgerber wrote:

We are quickly approaching ports lock for the 5.6 release.

No new ports.

No updates for the sake of updating.

If you have fixes, or fixes tied to updates, that are important and
that you think should still go in, you'll need to convince espie@ /
jasper@ / naddy@ / sthen@ first.

This is also the last chance to TEST packages and report problems.
Anything that won't get fixed real soon will remain broken for the
release.


"No one expects the Spanish Inquisition!"

Not sure how to get past that panel of  Inquisitors...but nobody 
cared to address this.


http://marc.info/?l=openbsd-ports&m=140296359324997&w=2

Sorry if I have to move you from... "the Comfy Chair"

Ian McWilliam



HEADS UP: 5.6 ports lock approaching

2014-07-21 Thread Christian Weisgerber
We are quickly approaching ports lock for the 5.6 release.

No new ports.

No updates for the sake of updating.

If you have fixes, or fixes tied to updates, that are important and
that you think should still go in, you'll need to convince espie@ /
jasper@ / naddy@ / sthen@ first.

This is also the last chance to TEST packages and report problems.
Anything that won't get fixed real soon will remain broken for the
release.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de



Re: ports lock approaching

2012-01-27 Thread Marc Peters

On 01/27/12 02:04, Stuart Henderson wrote:

Lock for 5.1 is approaching, all ports commits should be ok'd by naddy,
ajacoutot, landry, robert, espie or myself - emphasis is now on fixing
problems that will affect many users, without introducing any big
changes or instability.

Now would be a very good time to upgrade to the latest base snapshot,
run pkg_add -ui, test packages and report problems with any you rely on.
Testing update scenarios from 5.0 would be particularly appreciated
(refer to http://www.openbsd.org/faq/current.html for details of
updates requiring special attention).

There may still be time to get important fixes in before 5.1 but we
will need to know about any problems in the next couple of days.

Snapshot packages for amd64 and i386 should be in sync with base
snapshots following recent library updates; for other architectures
look for a package directory with plenty of files dated 21 January
onwards (sparc64 are on the way to mirrors now; powerpc should be
next). Please focus on packages rather than ports.


Here is again my diff to update print/lyx to the latest version. Maybe 
someone of the above mentioned can review it and commit this before the 
lock and it will ship with 5.1.


Tested on amd64 and i386.
Index: Makefile
===
RCS file: /cvs/ports/print/lyx/Makefile,v
retrieving revision 1.62
diff -u -r1.62 Makefile
--- Makefile16 Sep 2011 11:13:41 -  1.62
+++ Makefile11 Jan 2012 23:11:27 -
@@ -2,14 +2,14 @@
 
 COMMENT=   graphical frontend for LaTeX (nearly WYSIWYG)
 
-DISTNAME=  lyx-1.6.6.1
-REVISION=  3
+DISTNAME=  lyx-2.0.2
+REVISION=  0
 CATEGORIES=print editors
 
 HOMEPAGE=  http://www.lyx.org/
 
-MASTER_SITES=  ftp://ftp.lyx.org/pub/lyx/stable/1.6.x/ \
-   ftp://ftp.lip6.fr/pub/lyx/stable/1.6.x/
+MASTER_SITES=  ftp://ftp.lyx.org/pub/lyx/stable/2.0.x/ \
+   ftp://ftp.lip6.fr/pub/lyx/stable/2.0.x/
 
 # GPLv2
 PERMIT_PACKAGE_CDROM=  Yes
@@ -29,6 +29,7 @@
 WANTLIB += QtGui>=8 X11 aspell c m pthread stdc++ z
 WANTLIB += boost_filesystem-mt>=1 boost_iostreams-mt>=1
 WANTLIB += boost_regex-mt>=1 boost_signals-mt>=1
+WANTLIB += glib-2.0 gmodule-2.0
 
 SEPARATE_BUILD=concurrent
 USE_LIBTOOL=   Yes
Index: distinfo
===
RCS file: /cvs/ports/print/lyx/distinfo,v
retrieving revision 1.10
diff -u -r1.10 distinfo
--- distinfo4 Jun 2010 22:43:33 -   1.10
+++ distinfo11 Jan 2012 23:11:27 -
@@ -1,5 +1,4 @@
-MD5 (lyx-1.6.6.1.tar.gz) = XEPDFhy+wIx48kbMpXYWNg==
-RMD160 (lyx-1.6.6.1.tar.gz) = jsgq2uaMQPwBIrEqY2n/NP/ikz8=
-SHA1 (lyx-1.6.6.1.tar.gz) = VFb+boLhr6YBYb3xpTtXViEY9lE=
-SHA256 (lyx-1.6.6.1.tar.gz) = 5WasuoL4htwCdhmMKkqWTkSEXuxOg9b94b0UcTARDW8=
-SIZE (lyx-1.6.6.1.tar.gz) = 15698964
+MD5 (lyx-2.0.2.tar.gz) = ff26f28d3b9ed9f3c45162b17e675842
+RMD160 (lyx-2.0.2.tar.gz) = 3a9ace8032e26dadbf1bde38da230d4726e06444
+SHA256 (lyx-2.0.2.tar.gz) = 
94fd01f36b58494c3d14fd95f42dd70fbdfd4da3248d22dc78e05ca811301a52
+SIZE (lyx-2.0.2.tar.gz) = 18742720
Index: pkg/PLIST
===
RCS file: /cvs/ports/print/lyx/pkg/PLIST,v
retrieving revision 1.18
diff -u -r1.18 PLIST
--- pkg/PLIST   4 Jun 2010 22:43:33 -   1.18
+++ pkg/PLIST   11 Jan 2012 23:11:27 -
@@ -10,6 +10,7 @@
 share/locale/ar/LC_MESSAGES/lyx.mo
 share/locale/ca/LC_MESSAGES/lyx.mo
 share/locale/cs/LC_MESSAGES/lyx.mo
+share/locale/da/LC_MESSAGES/lyx.mo
 share/locale/de/LC_MESSAGES/lyx.mo
 share/locale/el/LC_MESSAGES/lyx.mo
 share/locale/en/LC_MESSAGES/lyx.mo
@@ -20,6 +21,7 @@
 share/locale/gl/LC_MESSAGES/lyx.mo
 share/locale/he/LC_MESSAGES/lyx.mo
 share/locale/hu/LC_MESSAGES/lyx.mo
+share/locale/ia/LC_MESSAGES/lyx.mo
 share/locale/id/LC_MESSAGES/lyx.mo
 share/locale/it/LC_MESSAGES/lyx.mo
 share/locale/ja/LC_MESSAGES/lyx.mo
@@ -30,12 +32,15 @@
 share/locale/ro/LC_MESSAGES/lyx.mo
 share/locale/ru/LC_MESSAGES/lyx.mo
 share/locale/sk/LC_MESSAGES/lyx.mo
+share/locale/sr/LC_MESSAGES/lyx.mo
+share/locale/sv/LC_MESSAGES/lyx.mo
 share/locale/tr/LC_MESSAGES/lyx.mo
 share/locale/uk/LC_MESSAGES/lyx.mo
 share/locale/zh_CN/LC_MESSAGES/lyx.mo
 share/locale/zh_TW/LC_MESSAGES/lyx.mo
 share/lyx/
 share/lyx/CREDITS
+share/lyx/autocorrect
 share/lyx/bind/
 share/lyx/bind/aqua.bind
 share/lyx/bind/broadway.bind
@@ -44,20 +49,14 @@
 share/lyx/bind/de/
 share/lyx/bind/de/menus.bind
 share/lyx/bind/emacs.bind
-share/lyx/bind/fi/
-share/lyx/bind/fi/menus.bind
 share/lyx/bind/greekkeys.bind
 share/lyx/bind/hollywood.bind
 share/lyx/bind/latinkeys.bind
 share/lyx/bind/mac.bind
 share/lyx/bind/math.bind
 share/lyx/bind/menus.bind
-share/lyx/bind/pt/
-share/lyx/bind/pt/menus.bind
 share/lyx/bind/sciword.bind
 share/lyx/bind/site.bind
-share/lyx/bind/sv/
-share/lyx/bind/sv/menus.bind
 share/lyx/bind/xemacs.bind
 share/lyx/chkconfig.ltx
 share/lyx/commands/
@@ -66,12 +65,12 @@
 share/lyx/

ports lock approaching

2012-01-26 Thread Stuart Henderson
Lock for 5.1 is approaching, all ports commits should be ok'd by naddy,
ajacoutot, landry, robert, espie or myself - emphasis is now on fixing
problems that will affect many users, without introducing any big
changes or instability.

Now would be a very good time to upgrade to the latest base snapshot,
run pkg_add -ui, test packages and report problems with any you rely on.
Testing update scenarios from 5.0 would be particularly appreciated
(refer to http://www.openbsd.org/faq/current.html for details of
updates requiring special attention).

There may still be time to get important fixes in before 5.1 but we
will need to know about any problems in the next couple of days.

Snapshot packages for amd64 and i386 should be in sync with base
snapshots following recent library updates; for other architectures
look for a package directory with plenty of files dated 21 January
onwards (sparc64 are on the way to mirrors now; powerpc should be
next). Please focus on packages rather than ports.