tdb

2015-01-16 Thread R. Scott Evans

Admittedly I've only got a math minor, but isn't 1.3.4  1.2.13?   ;-)

# pkg version -IvL=
tdb-1.2.13,1  succeeds index (index has 1.3.4)

-scott
___
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: tdb

2015-01-16 Thread Larry Rosenman

On 2015-01-16 08:33, R. Scott Evans wrote:

Admittedly I've only got a math minor, but isn't 1.3.4  1.2.13?   ;-)

# pkg version -IvL=
tdb-1.2.13,1  succeeds index (index has 1.3.4)

-scott
the ,1 is the PORTEPOCH which apparently was changed because of a 
version number regression.

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 108 Turvey Cove, Hutto, TX 78634-5688

___
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: tdb

2015-01-16 Thread R. Scott Evans

On 01/16/15 09:39, Larry Rosenman wrote:

On 2015-01-16 08:33, R. Scott Evans wrote:

Admittedly I've only got a math minor, but isn't 1.3.4  1.2.13?   ;-)

# pkg version -IvL=
tdb-1.2.13,1  succeeds index (index has 1.3.4)

-scott

the ,1 is the PORTEPOCH which apparently was changed because of a
version number regression.


Well, I mention it because while I use pkg version -IvL=, I know the 
FreeBSD Handbook section on updating ports instructs one to use 'pkg 
version -l ' which will cause this ports change to go unseen. 
Likewise, portmaster -a on my box didn't catch this and I had to 
specifically update/downgrade the port.


-scott
___
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: tdb

2015-01-16 Thread Vitaly Magerya
On 2015-01-16 16:47, R. Scott Evans wrote:
 On 01/16/15 09:39, Larry Rosenman wrote:
 On 2015-01-16 08:33, R. Scott Evans wrote:
 Admittedly I've only got a math minor, but isn't 1.3.4  1.2.13?   ;-)

 # pkg version -IvL=
 tdb-1.2.13,1  succeeds index (index has 1.3.4)

 -scott
 the ,1 is the PORTEPOCH which apparently was changed because of a
 version number regression.
 
 Well, I mention it because while I use pkg version -IvL=, I know the 
 FreeBSD Handbook section on updating ports instructs one to use 'pkg 
 version -l ' which will cause this ports change to go unseen. 
 Likewise, portmaster -a on my box didn't catch this and I had to 
 specifically update/downgrade the port.

Folks, the relevant diff here is [1]; it reverted PORTEPOCH
from 1 to 0. And you're right, it's a bug, since PORTEPOCH
should never ever decrease.

[1] 
http://svnweb.freebsd.org/ports/head/databases/tdb/Makefile?r1=377150r2=377149
___
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


Samba / TDB Port update

2013-06-06 Thread Jos Chrispijn

Dear port maintainer,
When updating Samba, I get this error:

===  tdb-1.2.11,1 conflicts with installed package(s):
  samba34-3.4.17

  They will not build together.
  Please remove them first with pkg_delete(1).
*** [check-build-conflicts] Error code 1

I don't want to delete Samba as I use it very frequently. Can you advise?

Thanks,
Jos Chrispijn
___
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: Samba / TDB Port update

2013-06-06 Thread William Grzybowski
On Thu, Jun 6, 2013 at 8:03 AM, Jos Chrispijn po...@webrz.net wrote:
 Dear port maintainer,
 When updating Samba, I get this error:

 ===  tdb-1.2.11,1 conflicts with installed package(s):
   samba34-3.4.17

   They will not build together.
   Please remove them first with pkg_delete(1).
 *** [check-build-conflicts] Error code 1

 I don't want to delete Samba as I use it very frequently. Can you advise?

You have to update samba to 3.5 or 3.6. Or keep with your current tdb version.



--
William Grzybowski
--
Curitiba/PR - Brasil
___
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: Samba / TDB Port update

2013-06-06 Thread Jos Chrispijn
   Hi William,

   William Grzybowski:

 You have to update samba to 3.5 or 3.6. Or keep with your current
 tdb version.

   Just upgraded, problem solved.
   Thanks for your reminder, must have had a temporary melt down D-)
   Cheers,
   Jos Chrispijn
___
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


databases/tdb fails to compile

2011-05-05 Thread Carsten Jensen
I'm trying to install samba35, during the compile phase it installs
python27 if it isn't already installed (I've previously installed it
with pth enabled) and it compiles/installs the tdb (or tries to).

I've linked /usr/local/includes/pth/pth.h and pthread.h to
/usr/local/includes/pth/python2.7 (this is required for py-imaging which
I'm also using bunt wondering if this is the right way?).

Now I get this compile error

snip
cc -I./include -Iinclude  -O2 -pipe -fno-strict-aliasing -I./libreplace
 -o bin/tdbtool tools/tdbtool.o -L. -ltdb
cc -I./include -Iinclude  -O2 -pipe -fno-strict-aliasing -I./libreplace
 -o bin/tdbdump tools/tdbdump.o -L. -ltdb
cc -I./include -Iinclude  -O2 -pipe -fno-strict-aliasing -I./libreplace
 -o bin/tdbbackup tools/tdbbackup.o -L. -ltdb
ln -fs libtdb.so.1 libtdb.so
cc -shared  -o tdb.so pytdb.o -L. -ltdb `/usr/local/bin/python-config
--ldflags`
/usr/bin/ld: cannot find -lpth
gmake: *** [tdb.so] Error 1
*** Error code 1

Stop in /usr/ports/databases/tdb.
*** Error code 1
/snip

Googling the error I noticed this PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=152111
Which didn't work for me


I've tried some different things, and basically ended out in installing
python26, adding tdb from the packages repo, uninstalling python26 and
reinstalling python27 to continue.

are there any hints to if this should be reported as a bug, though it's
there already, or how to take it from here ??

cheers
Carsten
___
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