handbrake & poudriere

2013-08-05 Thread Wolfgang Riegler
Hello,

I have problems with the port multimedia/handbrake. I'm using FreeBSD 9.1-r5 
amd64 and try to package the port with poudriere but it fails, because of 
"Package gtk+-2.0 was not found in the pkg-config search path". Here is the 
complete build log from poudriere: 
http://riegler.homeip.net/handbrake-0.9.8_2.log

Maybe someone can help me. Thanks in advance

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

2013-08-05 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
+-+
www/xpi-pentadactyl | 20130407| 20130805
+-+


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

If wish to stop receiving portscout reminders, please contact
portsc...@freebsd.org

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"


libpkg, sqlite and database problems prevent building any packages

2013-08-05 Thread Thomas Mueller
I have smaller FreeBSD 9.1-STABLE and 9.2-BETA2 installations that I update 
less frequently than the main hard-drive installation.

On the USB-stick installations, I find I can't upgrade or build any ports 
because of a database mess.  I get error messages mentioning sqlite even for 
packages that don't depend on sqlite3.

I tried to build or upgrade devel/subversion, ports-mgmt/pkg, databases/sqlite3 
and ports-mgmt/portmaster, and get error messages every time like

===>>> Starting check for runtime dependencies
===>>> Gathering dependency list for ports-mgmt/pkg from ports
pkg-static: warning: database version 19 is newer than libpkg(3) version 12, 
but still compatible
pkg-static: sqlite: no such column: infos (pkgdb.c:1086)
===>>> No dependencies for ports-mgmt/pkg

pkg-static: warning: database version 19 is newer than libpkg(3) version 12, 
but still compatible
pkg-static: sqlite: no such column: infos (pkgdb.c:1086)
pkg-static: warning: database version 19 is newer than libpkg(3) version 12, 
but still compatible
pkg-static: sqlite: no such column: infos (pkgdb.c:1086)
===>  Installing for pkg-1.1.4_1
===>   Generating temporary packing list
===>  Checking if ports-mgmt/pkg already installed
pkg-static: warning: database version 19 is newer than libpkg(3) version 12, 
but still compatible
pkg-static: sqlite: no such column: infos (pkgdb.c:1086)
*** [check-already-installed] Error code 74

Stop in /BETA1/usr/ports/ports-mgmt/pkg.
*** [/BETA1/usr/ports/ports-mgmt/pkg/worki386/.install_done.pkg._usr_local] 
Error code 1

Stop in /BETA1/usr/ports/ports-mgmt/pkg.

===>>> Installation of pkg-1.1.4_1 (ports-mgmt/pkg) failed
===>>> Aborting update

===>>> Update for ports-mgmt/pkg failed
===>>> Aborting update

===>>> Update for converters/libiconv failed
===>>> Aborting update

===>>> Update for devel/gettext failed
===>>> Aborting update

===>>> Update for devel/gmake failed
===>>> Aborting update

===>>> Update for devel/icu failed
===>>> Aborting update

===>>> Killing background jobs
Terminated

===>>> You can restart from the point of failure with this command line:
   portmaster  databases/sqlite3 devel/icu devel/gmake devel/gettext 
converters/libiconv ports-mgmt/pkg 

===>>> Exiting


I also get messages even when running pkg, this is the new pkgng.

You might want to see my /etc/make.conf .

Main hard drive installation:


PORTSDIR=/BETA1/usr/ports
PACKAGES=/usr/packages
WRKDIR=${.CURDIR}/work9amd64
# WITH_NEW_XORG=yes
# WITH_KMS=yes
WITH_PKGNG=yes
OPTIONS_SET=DOCS NLS
mpop_SET=GNUTLS NLS
# added by use.perl 2013-06-16 03:51:03
PERL_VERSION=5.16.3


for USB-stick installation with 9.2-BETA2 amd64:


PORTSDIR=/BETA1/usr/ports
PACKAGES=/usr/packages
WRKDIR=${.CURDIR}/workusb64
WITH_PKGNG=yes
OPTIONS_SET.mpop=GNUTLS NLS
# added by use.perl 2012-09-23 09:49:32
PERL_VERSION=5.14.2


for USB-stick installation with 9.1-STABLE i386:


PORTSDIR=/BETA1/usr/ports
PACKAGES=/usr/packages
WRKDIR=${.CURDIR}/worki386
# WITH_NEW_XORG=yes
# WITH_KMS=yes
WITH_PKGNG=yes
OPTIONS_SET=DOCS NLS
# WITHOUT_MODULES= usb/ulpt # This does not work
SRC_BASE=/STABLE1/usr/src
# added by use.perl 2013-06-17 12:56:10
PERL_VERSION=5.16.3


I know there was a major change in database format when subversion was updated 
in ports from 1.7 to 1.8, but would this cause the problems that are driving me 
crazy?  There ought to be a way to resolve this, but I can't see what to do, 
everything I try leads to the same error messages.

Tom

___
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: libpkg, sqlite and database problems prevent building any packages

2013-08-05 Thread Kimmo Paasiala
On Mon, Aug 5, 2013 at 1:42 PM, Thomas Mueller
 wrote:
> I have smaller FreeBSD 9.1-STABLE and 9.2-BETA2 installations that I update 
> less frequently than the main hard-drive installation.
>
> On the USB-stick installations, I find I can't upgrade or build any ports 
> because of a database mess.  I get error messages mentioning sqlite even for 
> packages that don't depend on sqlite3.
>
> I tried to build or upgrade devel/subversion, ports-mgmt/pkg, 
> databases/sqlite3 and ports-mgmt/portmaster, and get error messages every 
> time like
>
> ===>>> Starting check for runtime dependencies
> ===>>> Gathering dependency list for ports-mgmt/pkg from ports
> pkg-static: warning: database version 19 is newer than libpkg(3) version 12, 
> but still compatible
> pkg-static: sqlite: no such column: infos (pkgdb.c:1086)
> ===>>> No dependencies for ports-mgmt/pkg
>
> pkg-static: warning: database version 19 is newer than libpkg(3) version 12, 
> but still compatible
> pkg-static: sqlite: no such column: infos (pkgdb.c:1086)
> pkg-static: warning: database version 19 is newer than libpkg(3) version 12, 
> but still compatible
> pkg-static: sqlite: no such column: infos (pkgdb.c:1086)
> ===>  Installing for pkg-1.1.4_1
> ===>   Generating temporary packing list
> ===>  Checking if ports-mgmt/pkg already installed
> pkg-static: warning: database version 19 is newer than libpkg(3) version 12, 
> but still compatible
> pkg-static: sqlite: no such column: infos (pkgdb.c:1086)
> *** [check-already-installed] Error code 74
>
> Stop in /BETA1/usr/ports/ports-mgmt/pkg.
> *** [/BETA1/usr/ports/ports-mgmt/pkg/worki386/.install_done.pkg._usr_local] 
> Error code 1
>
> Stop in /BETA1/usr/ports/ports-mgmt/pkg.
>
> ===>>> Installation of pkg-1.1.4_1 (ports-mgmt/pkg) failed
> ===>>> Aborting update
>
> ===>>> Update for ports-mgmt/pkg failed
> ===>>> Aborting update
>
> ===>>> Update for converters/libiconv failed
> ===>>> Aborting update
>
> ===>>> Update for devel/gettext failed
> ===>>> Aborting update
>
> ===>>> Update for devel/gmake failed
> ===>>> Aborting update
>
> ===>>> Update for devel/icu failed
> ===>>> Aborting update
>
> ===>>> Killing background jobs
> Terminated
>
> ===>>> You can restart from the point of failure with this command line:
>portmaster  databases/sqlite3 devel/icu devel/gmake 
> devel/gettext converters/libiconv ports-mgmt/pkg
>
> ===>>> Exiting
>
>
> I also get messages even when running pkg, this is the new pkgng.
>
> You might want to see my /etc/make.conf .
>
> Main hard drive installation:
>
>
> PORTSDIR=/BETA1/usr/ports
> PACKAGES=/usr/packages
> WRKDIR=${.CURDIR}/work9amd64
> # WITH_NEW_XORG=yes
> # WITH_KMS=yes
> WITH_PKGNG=yes
> OPTIONS_SET=DOCS NLS
> mpop_SET=GNUTLS NLS
> # added by use.perl 2013-06-16 03:51:03
> PERL_VERSION=5.16.3
>
>
> for USB-stick installation with 9.2-BETA2 amd64:
>
>
> PORTSDIR=/BETA1/usr/ports
> PACKAGES=/usr/packages
> WRKDIR=${.CURDIR}/workusb64
> WITH_PKGNG=yes
> OPTIONS_SET.mpop=GNUTLS NLS
> # added by use.perl 2012-09-23 09:49:32
> PERL_VERSION=5.14.2
>
>
> for USB-stick installation with 9.1-STABLE i386:
>
>
> PORTSDIR=/BETA1/usr/ports
> PACKAGES=/usr/packages
> WRKDIR=${.CURDIR}/worki386
> # WITH_NEW_XORG=yes
> # WITH_KMS=yes
> WITH_PKGNG=yes
> OPTIONS_SET=DOCS NLS
> # WITHOUT_MODULES= usb/ulpt # This does not work
> SRC_BASE=/STABLE1/usr/src
> # added by use.perl 2013-06-17 12:56:10
> PERL_VERSION=5.16.3
>
>
> I know there was a major change in database format when subversion was 
> updated in ports from 1.7 to 1.8, but would this cause the problems that are 
> driving me crazy?  There ought to be a way to resolve this, but I can't see 
> what to do, everything I try leads to the same error messages.
>
> Tom
>


This has nothing to do with subversion. Your pkg(8) client  is out of
date compared to the /var/db/pkg/local.sqlite database.

-Kimmo
___
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"


Current unassigned ports problem reports

2013-08-05 Thread FreeBSD bugmaster
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker  Resp.  Description

f ports/181040[patch] sysutils/conky "diskio" memory leak fix
o ports/181038print/acrobatviewer dies with null pointer exception w
o ports/181037update math/coinmp to version 1.7.0
f ports/181021x11-toolkits/open-motif fails to build because YY_MAIN
o ports/181019[NEW PORT] graphics/luxrays: LuxRender library dedicat
f ports/181018graphics/ufraw fails to build due to missing mkinstall
f ports/181017games/iourbanterror: iourbanterror-4.1.1.s2318,1 needs
o ports/181015upgrade russian/wordpress to 3.6
f ports/181013[PATCH] graphics/ufraw build failure after glib update
f ports/181010net-mgmt/smokeping 2.6.9 build problem
o ports/180987[NEW PORTs] audio/ardour3 and multimedia/harvid
f ports/180984math/openblas:  Patch patch-exports+gensymbol failed t
o ports/180981[new port] math/gkmap a Karnaugh Map
o ports/180967Update port games/opensonic to 0.1.4
o ports/180963[Maintainer patch] Upgrade mail/dbmail from 3.1.0 to 3
f ports/180959[PATCH] x11/x3270: update to 3.3.12
o ports/180953[MAINTAINER] www/typo347: update to 4.7.14
o ports/180952[MAINTAINER] www/typo345: update to 4.5.29
o ports/180951[MAINTAINER] www/typo3: update to 6.1.3
o ports/180925Can't compile sysutils/fusefs-smbnetfs on -current
o ports/180914broken: packages-8-stable
o ports/180909[MAINTAINER] devel/allegro: Remove conflict with alleg
o ports/180908[MAINTAINER] devel/allegro-devel: Update to 5.0.9, rem
f ports/180898update dns/dnscrypt-proxy to 1.3.2
o ports/180887New Port: databases/php5-mongodb
f ports/180845package creation fails for sysutils/bacula-bat
o ports/180841[MAINTAINER] databases/jrrd: update to 1.0.6_1
f ports/180832New version of news/nzbget (11.0)
o ports/180828[MAINTAINER] russian/MT: update to 5.2.7,1
f ports/180799[PATCH] mail/dovecot2 without-ssl make package error
f ports/180786lang/lua52 lacks a pkgconfig file
f ports/180773[Maintainer update] sysutils/qjail   Bug fix.
o ports/180757[MAINTAINER] cad/repsnapper: update to 2.2.0b1
f ports/180753[PATCH] devel/ocaml-opam: fix build error of util.ml
f ports/180739ports/sysutils/ezjail patch
f ports/180736net/torsocks: aclocal-1.14: error: couldn't open direc
f ports/180734games/iourbanterror: broken
o ports/180668japanese/mutt-devel update to 1.5.21-ja.2
o ports/180665[new port] secturiy/rngtest: TRNG/PRNG test tool
o ports/180664checksum mismatch in biology/tinker
o ports/180654[NEW PORT] devel/linux-f10-hal-libs: HAL libs (Linux F
f ports/180651net/scribe won't build with automake update to 1.14
f ports/180647www/cherokee: build fails
f ports/180642[PATCH] astro/gpsman: update to 6.4.4.1
f ports/180634security/ipsec-tools: ipsec-tools doesnt create contro
o ports/180611[patch] update cad/feappv
f ports/180607sysutils/zfsnap: grammar error(s) in pkg-descr
o ports/180602[NEW PORT] multimedia/xjadeo: A synced video player fo
o ports/180595unable to build net-p2p/mldonkey-core on i386 using cl
f ports/180584[patch] net-mgmt/wmi-client: Point to one working MAST
f ports/180564multimedia/mplayer compilation error with Clang (runni
o ports/180524games/crack-attack crashes
o ports/180492problem with /usr/ports/Mk/bsd.ldap.mk
o ports/180475audio/freeswitch-sounds: volume reduced to 20% of orig
o ports/180452New Port: devel/libbson: library providing useful rout
o ports/180446New port: print/p910nd A small printer daemon
o ports/180409ports/math/scilab trying to use F77
o ports/180408ports/math/scilab missing a file to be installed
o ports/180407x11-fm/dolphin in kde-4.10.5 will cause reboot
f ports/180389[PATCH] net/rabbitmq: update to 3.1.3
o ports/180387[MAINTAINER-UPDATE] www/mawstats: set EXPIRATION_DATE 
o ports/180351new port: ftp/u1ftp
f ports/180350textproc/sigil build problems when libzip installed
f ports/180345[patch] sysutils/gdisk: update to version 0.8.6 and so
o ports/180338dev

glib fallout

2013-08-05 Thread Lowell Gilbert
What's the general status of cleaning up the ports that broke as a
result of the glib/getline changes? I noticed that someone opened up a
bunch of PRs on the subject and then closed them, so I'm sure there's an
effort going on, but I haven't heard about it.

In particular, I'm currently living with ufraw...

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: libpkg, sqlite and database problems prevent building any packages

2013-08-05 Thread Thomas Mueller
> > I know there was a major change in database format when subversion was 
> > updated in ports from 1.7 to 1.8, but would this cause the problems that are
> > driving me crazy?  There ought to be a way to resolve this, but I can't see 
> > what to do, everything I try leads to the same error messages.
 
> > Tom
   

 
> This has nothing to do with subversion. Your pkg(8) client  is out of
> date compared to the /var/db/pkg/local.sqlite database.
  
> -Kimmo

I could see my pkg client is out of date, but how do I update it?

Attempts to update all gave me those error messages.  Installation fails.   
 

Tom
___
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: libpkg, sqlite and database problems prevent building any packages

2013-08-05 Thread Matthew Seaman
On 05/08/2013 14:30, Thomas Mueller wrote:
> I could see my pkg client is out of date, but how do I update it?
> 
> Attempts to update all gave me those error messages.  Installation fails. 
>

Your package database has got into an inconsistent state.  pkg(8) is
attempting to auto-update the schema to the latest version, but failing
because it's trying to remove an 'infos' column from a table where that
column has apparently already been removed.  (Likely this situation has
come about because pkg got killed in the middle of doing this update
previously.)

How happy are you to get down'n'dirty with the source code and running
SQL from the command line?  If you look at the updates pkg is attempting
to run shown here:

   https://github.com/freebsd/pkg/blob/master/libpkg/private/db_upgrades.h

would you be capable of looking at the DB schema, working out which of
those updates had been applied, aplying any outstanding ones by hand and
then setting the user version to 19 by:

   sql> PRAGMA user_version = 19 ;

?

If not, check in /var/backups for a good copy of your local.sqlite
database and try and restore from there.  Unfortunately, there's no
guarantee that any backup copy doesn't have the same inconsistencies as
your live copy.

We need to make pkg(8) databases more resilient to the effects of SIGHUP
or similar while they are elbows-deep in the bowels of the DB schema...

Cheers,

Matthew





___
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: libpkg, sqlite and database problems prevent building any packages

2013-08-05 Thread Kimmo Paasiala
On Mon, Aug 5, 2013 at 5:03 PM, Matthew Seaman  wrote:
> On 05/08/2013 14:30, Thomas Mueller wrote:
>> I could see my pkg client is out of date, but how do I update it?
>>
>> Attempts to update all gave me those error messages.  Installation fails.
>
> Your package database has got into an inconsistent state.  pkg(8) is
> attempting to auto-update the schema to the latest version, but failing
> because it's trying to remove an 'infos' column from a table where that
> column has apparently already been removed.  (Likely this situation has
> come about because pkg got killed in the middle of doing this update
> previously.)
>
> How happy are you to get down'n'dirty with the source code and running
> SQL from the command line?  If you look at the updates pkg is attempting
> to run shown here:
>
>https://github.com/freebsd/pkg/blob/master/libpkg/private/db_upgrades.h
>
> would you be capable of looking at the DB schema, working out which of
> those updates had been applied, aplying any outstanding ones by hand and
> then setting the user version to 19 by:
>
>sql> PRAGMA user_version = 19 ;
>
> ?
>
> If not, check in /var/backups for a good copy of your local.sqlite
> database and try and restore from there.  Unfortunately, there's no
> guarantee that any backup copy doesn't have the same inconsistencies as
> your live copy.
>
> We need to make pkg(8) databases more resilient to the effects of SIGHUP
> or similar while they are elbows-deep in the bowels of the DB schema...
>
> Cheers,
>
> Matthew
>
>
>
>
>

Ok this is then different problem than what I saw when I reverted back
from pkg-devel to pkg, the error message was the same though.

-Kimmo
___
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: libpkg, sqlite and database problems prevent building any packages

2013-08-05 Thread Matthew Seaman
On 05/08/2013 15:24, Kimmo Paasiala wrote:
> Ok this is then different problem than what I saw when I reverted back
> from pkg-devel to pkg, the error message was the same though.

Yeah -- we don't really have any support for down-reving the schema in
local.sqlite at the moment, so going from pkg-devel to pkg can be
traumatic.  It should be OK right now as there's no difference in the DB
schemas for what's currently in ports.

repo.sqlite should have significantly more forwards and backwards
compatibility, although with the latest versions of pkg, you aren't
downloading a pre-built sqlite DB, but a collection of YAML documents
containing selected package metadata.  So all that up- and down- DB
schema version changing code is pretty much redundant.  C'est la vie.

Cheers,

Matthew



___
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: libpkg, sqlite and database problems prevent building any packages

2013-08-05 Thread Thomas Mueller
On 05/08/2013 14:30, Thomas Mueller wrote:
> I could see my pkg client is out of date, but how do I update it?
>
> Attempts to update all gave me those error messages.  Installation fails.

Matthew Seaman responded:

> Your package database has got into an inconsistent state.  pkg(8) is
> attempting to auto-update the schema to the latest version, but failing
> because it's trying to remove an 'infos' column from a table where that
> column has apparently already been removed.  (Likely this situation has
> come about because pkg got killed in the middle of doing this update
> previously.)

> How happy are you to get down'n'dirty with the source code and running
> SQL from the command line?  If you look at the updates pkg is attempting
> to run shown here:

>https://github.com/freebsd/pkg/blob/master/libpkg/private/db_upgrades.h

> would you be capable of looking at the DB schema, working out which of
> those updates had been applied, aplying any outstanding ones by hand and
> then setting the user version to 19 by:

>sql> PRAGMA user_version = 19 ;

?

> If not, check in /var/backups for a good copy of your local.sqlite
> database and try and restore from there.  Unfortunately, there's no
> guarantee that any backup copy doesn't have the same inconsistencies as
> your live copy.

> We need to make pkg(8) databases more resilient to the effects of SIGHUP
> or similar while they are elbows-deep in the bowels of the DB schema...

Trying to do what you suggest would in all likelihood be an exercise in 
futility, especially when I am very tired from being unable to sleep.

I didn't realize pkgng was so non-sturdy.

I wonder what would happen if I delete /var/db/pkg/local.sqlite, or perhaps 
better, move it to another location and name so as not to burn my bridges.

But anything so I can upgrade pkg.

Does pkgng have no means of recovery?  Can pkg regenerate a database, and from 
what?

My /var/backups on the USB-stick 9.2-BETA2 amd64 installation shows


total 280
-rw-r--r--  1 root  wheel1674 Apr  2  2012 aliases.bak
-rw-r--r--  1 root  wheel 436 Apr  2  2012 group.bak
-rw---  1 root  wheel1500 Apr  2  2012 master.passwd.bak
-rw-r--r--  1 root  wheel  269144 Dec 13  2012 pkgdb.bak.tbz
-rw-r--r--  1 root  wheel 129 Jul 16  2012 pkgdb.bak.tbz.2


pkg.bak.tbz looks like the database from the old format.

My /var/backups on the USB-stick 9.1-STABLE i386 installation shows


total 140
-rw-r--r--  1 root  wheel1688 Jan 20  2013 aliases.bak
-rw-r--r--  1 root  wheel1674 Jun  6  2012 aliases.bak2
-rw-r--r--  1 root  wheel 481 Jan 17  2013 group.bak
-rw-r--r--  1 root  wheel 449 Jul 13  2012 group.bak2
-rw---  1 root  wheel1761 Jan 17  2013 master.passwd.bak
-rw---  1 root  wheel1500 Jun  6  2012 master.passwd.bak2
-rw-r--r--  1 root  wheel8524 May 28 03:01 pkgdb.bak.tbz
-rw-r--r--  1 root  wheel 130 Jan 19  2013 pkgdb.bak.tbz.2
-rw-r--r--  1 root  wheel  100352 May 28 04:29 pkgng.db


pkgng.db looks like the new format, but that was before I built wine and 
dependencies.

Tom
___
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"


[patch]Uses/iconv.mk, devel/getext has no libiconv linkage.

2013-08-05 Thread Yamaya Takashi
Hi.

Some ports, e.g. devel/glib20, cannot build because devel/gettext has no
libiconv linkage.
msgfmt cannot handle utf-8 and say "invalid multibyte sequence".

Patch attached file and rebuild devel/gettext, msgfmt works correctly.


Index: Mk/Uses/iconv.mk
===
--- Mk/Uses/iconv.mk	(revision 324274)
+++ Mk/Uses/iconv.mk	(working copy)
@@ -17,5 +17,6 @@
 .endif
 
 LIB_DEPENDS+=	libiconv.so.3:${PORTSDIR}/converters/libiconv
+LDFLAGS+= -L${LOCALBASE}/lib -liconv
 
 .endif
___
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_info -W equivalent in pkgng?

2013-08-05 Thread Xin Li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Is there an equivalent of pkg_info -W with pkgng?  (Or let's say,
given a file /usr/local/bin/X, how do I find the corresponding package
that installs it?)

Cheers,
- -- 
Xin LI https://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJR//adAAoJEG80Jeu8UPuzsTUIALkvHHkxlpCcuBp4PRtCiC/U
AATOufv7E2uGUUbQCCWwx7JoQ2c7QpnxgIhMIVbcveFfoJ27Pik5Qfnmaip5ozCD
m6WKjk1OhJcDosshfpSU3nSJet5AeB501oFg9y31/3s+TDqZr+Cu9LFx85Ktyzhu
M7IObwY76XKUC/s1xU1SkEz4NO74afhoejnCQxMkCteYFZNEZGvToZH+ckLoqljZ
IyLpBSYZybooV9Ei29+qGIRnbmdR7uEcdzTiRjLKHPqDaotnbhxRYjiVcLHrHxZ2
U/hwmEO7RYbJa9fIfykZGKcrHTEigzeiR6VDqwGExR847XFZ70o/XsBbpl7PjZQ=
=2KHr
-END PGP SIGNATURE-
___
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_info -W equivalent in pkgng?

2013-08-05 Thread Julien Laffaye

pkg which

On 8/5/2013 9:01 PM, Xin Li wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Is there an equivalent of pkg_info -W with pkgng?  (Or let's say,
given a file /usr/local/bin/X, how do I find the corresponding package
that installs it?)

Cheers,
- -- 
Xin LI https://www.delphij.net/

FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJR//adAAoJEG80Jeu8UPuzsTUIALkvHHkxlpCcuBp4PRtCiC/U
AATOufv7E2uGUUbQCCWwx7JoQ2c7QpnxgIhMIVbcveFfoJ27Pik5Qfnmaip5ozCD
m6WKjk1OhJcDosshfpSU3nSJet5AeB501oFg9y31/3s+TDqZr+Cu9LFx85Ktyzhu
M7IObwY76XKUC/s1xU1SkEz4NO74afhoejnCQxMkCteYFZNEZGvToZH+ckLoqljZ
IyLpBSYZybooV9Ei29+qGIRnbmdR7uEcdzTiRjLKHPqDaotnbhxRYjiVcLHrHxZ2
U/hwmEO7RYbJa9fIfykZGKcrHTEigzeiR6VDqwGExR847XFZ70o/XsBbpl7PjZQ=
=2KHr
-END PGP SIGNATURE-
___
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: pkg_info -W equivalent in pkgng?

2013-08-05 Thread Boris Samorodov
05.08.2013 23:02, Julien Laffaye пишет:
> On 8/5/2013 9:01 PM, Xin Li wrote:
> 
> Is there an equivalent of pkg_info -W with pkgng?  (Or let's say,
> given a file /usr/local/bin/X, how do I find the corresponding package
> that installs it?)
>
> pkg which

And there is a very useful table of corresponding commands here:
https://wiki.freebsd.org/PkgPrimer

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: mail/mail-notification 5.4 fails to compile

2013-08-05 Thread Torfinn Ingolfsen
On Sun, Aug 4, 2013 at 9:17 PM, Marcin Wisnicki
 wrote:
> BTW there are no build errors on build cluster. Is there anything
> non-standard about your build environment ?


No, not that I'm aware of at least.
This is a standard install of FreeBSD 8.4-release, upgraded to
8.4-stable via source and make world, ports tree fetched via portsnap.
No options set in /etc/make.conf.
The only thing I can think of, is that I did choose non-default
options for the mail-notification port (disabling things I don't need)
as shown in the build output in my first message.

-- 
Regards,
Torfinn Ingolfsen
___
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: mail/mail-notification 5.4 fails to compile

2013-08-05 Thread Torfinn Ingolfsen
On Sun, Aug 4, 2013 at 8:42 PM, Marcin Wisnicki
 wrote:
> I guess bsd.gnome.mk should be smart enough to `killall -HUP gconfd-2`
> at package post-install when port uses gconf (has GCONF_SCHEMAS).
> Please file a PR against gnome ports.

Are you sure that this way (killall -HUP ...) is the correct fix?
It seems like a workaround (instead of a real fix) to me, based on the
discussion in the two bugs I listed in my previous message.
Also, pkill -HUP gconfd-2 didn't work for me, I had to kill the
gconfd-2 process totally.
HTH
-- 
Regards,
Torfinn Ingolfsen
___
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: libpkg, sqlite and database problems prevent building any packages

2013-08-05 Thread Jeffrey Bouquet
Bottom posting below; will reply in better format when/if I get another webmail 
client maybe... the

text is below the next occurance of "bottom posting"




 From: Thomas Mueller 
To: freebsd-ports@freebsd.org 
Sent: Monday, August 5, 2013 8:36 AM
Subject: Re: libpkg, sqlite and database problems prevent building any packages
 

On 05/08/2013 14:30, Thomas Mueller wrote:
> I could see my pkg client is out of date, but how do I update it?
>
> Attempts to update all gave me those error messages.  Installation fails.

Matthew Seaman responded:

> Your package database has got into an inconsistent state.  pkg(8) is
> attempting to auto-update the schema to the latest version, but failing
> because it's trying to remove an 'infos' column from a table where that
> column has apparently already been removed.  (Likely this situation has
> come about because pkg got killed in the middle of doing this update
> previously.)

> How happy are you to get down'n'dirty with the source code and running
> SQL from the command line?  If you look at the updates pkg is attempting
> to run shown here:

>    https://github.com/freebsd/pkg/blob/master/libpkg/private/db_upgrades.h

> would you be capable of looking at the DB schema, working out which of
> those updates had been applied, aplying any outstanding ones by hand and
> then setting the user version to 19 by:

>    sql> PRAGMA user_version = 19 ;

?

> If not, check in /var/backups for a good copy of your local.sqlite
> database and try and restore from there.  Unfortunately, there's no
> guarantee that any backup copy doesn't have the same inconsistencies as
> your live copy.

> We need to make pkg(8) databases more resilient to the effects of SIGHUP
> or similar while they are elbows-deep in the bowels of the DB schema...

Trying to do what you suggest would in all likelihood be an exercise in 
futility, especially when I am very tired from being unable to sleep.

I didn't realize pkgng was so non-sturdy.

I wonder what would happen if I delete /var/db/pkg/local.sqlite, or perhaps 
better, move it to another location and name so as not to burn my bridges.

But anything so I can upgrade pkg.

Does pkgng have no means of recovery?  Can pkg regenerate a database, and from 
what?

My /var/backups on the USB-stick 9.2-BETA2 amd64 installation shows


total 280
-rw-r--r--  1 root  wheel    1674 Apr  2  2012 aliases.bak
-rw-r--r--  1 root  wheel     436 Apr  2  2012 group.bak
-rw---  1 root  wheel    1500 Apr  2  2012 master.passwd.bak
-rw-r--r--  1 root  wheel  269144 Dec 13  2012 pkgdb.bak.tbz
-rw-r--r--  1 root  wheel     129 Jul 16  2012 pkgdb.bak.tbz.2


pkg.bak.tbz looks like the database from the old format.

My /var/backups on the USB-stick 9.1-STABLE i386 installation shows


total 140
-rw-r--r--  1 root  wheel    1688 Jan 20  2013 aliases.bak
-rw-r--r--  1 root  wheel    1674 Jun  6  2012 aliases.bak2
-rw-r--r--  1 root  wheel     481 Jan 17  2013 group.bak
-rw-r--r--  1 root  wheel     449 Jul 13  2012 group.bak2
-rw---  1 root  wheel    1761 Jan 17  2013 master.passwd.bak
-rw---  1 root  wheel    1500 Jun  6  2012 master.passwd.bak2
>-rw-r--r--  1 root  wheel    8524 May 28 03:01 pkgdb.bak.tbz
>-rw-r--r--  1 root  wheel     130 Jan 19  2013 pkgdb.bak.tbz.2
>-rw-r--r--  1 root  wheel  100352 May 28 04:29 pkgng.db


>pkgng.db looks like the new format, but that was before I built wine and 
>dependencies.

..
..
Bottom posting... 

Non-sturdy? , but this sort of showstopper is what IMHO 
should necessite a huge problem-resolving flowchart, 
before pkg(ng)  fully obsoletes its legacy
alternative... not to mention the possibility of 
pkg(ng) not having enough memory, 
on some installs where before /var/db/pkg would have enough.
Just a 2c.    As in, if I *have to* migrate to pkg/, I need something from 
which to
copy the succint parts to a few post-its on the monitor...  (think 
HUGE...FLOWCHART...) 

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"
___
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: [REVIEW] Completing i386-wine

2013-08-05 Thread David Naylor
On Monday, 5 August 2013 02:31:54 Sam Fourman Jr. wrote:
> Would there also be the possibility to have i386-wine as a source-code
> 
> > port, and build from i386 installation?  That avoids cross-compiling.
> > 
> > One could build an i386 installation either from amd64 or previous i386
> > installation, then build i386-wine and other desired ports when booted
> > into
> > the i386 installation.
> > 
> > This i386 installation would be on another partition or another disk (USB
> > 3.0 stick or USB 3.0 hard-drive partition?), and from the amd64
> > installation, the i386 installation could be mounted on /compat/i386.
> > 
> > With a USB hard drive, if not directly bootable, the loader and kernel
> > could be copied to another boot disk/partition, and root could be set for
> > the USB hard-drive partition.  My USB 3.0 hard drive, Western Digital My
> > Book Essential, is not recognized by the BIOS/UEFI or GRUB2, but is
> > accessible from Linux or FreeBSD.
> > 
> > Tom--
> 
> Can't we just have the port build wine in a i386 jail? eg it would require
> the FreeBSD sources, build the jail... etc.. it seems like a LOT, but
> honestly whats wrong with it... ill do the testing

Hi Sam / Thomas

Well, when compiling on i386 the port is "source based".  I am reluctant to 
bring in the i386 environment bootstrapping logic within the port (especially 
given there are so many different ways - and personal preferences - on how to 
do it).  

I also think it is not appropriate, in my opinion, for a port to do so much.  

Given that nothing stops an individual from setting up such an environment 
manually (such as how I do it to create the packages) I think the port offers 
enough functionality as is.  

I hope this clarifies my position on this, and thank you for your feedback :-)

signature.asc
Description: This is a digitally signed message part.


Re: mail/mail-notification 5.4 fails to compile

2013-08-05 Thread Marcin Wisnicki
It's not a workaround - it is a real fix as suggested by gconf
documentation and it's used by linux distros (see debian[1] and
gentoo[2]).

[1] 
http://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gconf/debian/gconf2.postinst?revision=31302&view=markup
[2] 
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/gnome2-utils.eclass?diff_format=s&revision=1.31&view=markup

On Mon, Aug 5, 2013 at 9:40 PM, Torfinn Ingolfsen  wrote:
> On Sun, Aug 4, 2013 at 8:42 PM, Marcin Wisnicki
>  wrote:
>> I guess bsd.gnome.mk should be smart enough to `killall -HUP gconfd-2`
>> at package post-install when port uses gconf (has GCONF_SCHEMAS).
>> Please file a PR against gnome ports.
>
> Are you sure that this way (killall -HUP ...) is the correct fix?
> It seems like a workaround (instead of a real fix) to me, based on the
> discussion in the two bugs I listed in my previous message.
> Also, pkill -HUP gconfd-2 didn't work for me, I had to kill the
> gconfd-2 process totally.
> HTH
> --
> Regards,
> Torfinn Ingolfsen
___
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"


KDE4 woes

2013-08-05 Thread Stan Gammons
I finally got KDE4 to build.  In order to stop the error I was getting, I did a 
portmaster --force-config x11/kde and deselected kdenetwork. The build finished 
without errors. I need to add virtuoso, but KDE appears to be working Ok from 
what little checking I've done.  Any ideas why kdenetwork failing to update 
caused the build to abort?


Stan
___
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]Uses/iconv.mk, devel/getext has no libiconv linkage.

2013-08-05 Thread Boris Samorodov
(CC to the maintainer: gn...@freebsd.org)

05.08.2013 20:13, Yamaya Takashi пишет:
> 
> Some ports, e.g. devel/glib20, cannot build because devel/gettext has no
> libiconv linkage.
> msgfmt cannot handle utf-8 and say "invalid multibyte sequence".
> 
> Patch attached file and rebuild devel/gettext, msgfmt works correctly.

Confirmed. The fix works. Thanks!

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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"

kdenetwork4

2013-08-05 Thread Stan Gammons
Here the output I get when I try to build kdenetwork4 from ports.  Looks
like libmsn is the problem.  Where is the makefile located that has
libmsn as a dependency?


Stan



]0;portmaster: net/kdenetwork4
===>>> Port directory: /usr/ports/net/kdenetwork4

===>>> Gathering distinfo list for installed ports

===>>> Launching 'make checksum' for net/kdenetwork4 in background
===>>> Gathering dependency list for net/kdenetwork4 from ports
===>>> Launching child to install net-im/kopete-kde4

===>>> net/kdenetwork4 >> net-im/kopete-kde4 (1/1)
]0;portmaster: net/kdenetwork4 >> net-im/kopete-kde4 (1/1)
===>>> Port directory: /usr/ports/net-im/kopete-kde4

===>>> Launching 'make checksum' for net-im/kopete-kde4 in background
===>>> Gathering dependency list for net-im/kopete-kde4 from ports
===>>> Launching child to install audio/msilbc

===>>> net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc (2/2)
]0;portmaster: net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc
(2/2)
===>>> Port directory: /usr/ports/audio/msilbc

===>>> Launching 'make checksum' for audio/msilbc in background
===>>> Gathering dependency list for audio/msilbc from ports
===>>> Launching child to install net/ilbc

===>>> net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc >> net/ilbc
(3/3)
]0;portmaster: net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc >>
net/ilbc (3/3)
===>>> Port directory: /usr/ports/net/ilbc

===>>> Launching 'make checksum' for net/ilbc in background
===>>> Gathering dependency list for net/ilbc from ports
===>>> Initial dependency check complete for net/ilbc

===>>> Continuing initial dependency check for audio/msilbc
===>>> Launching child to install net/linphone-base

===>>> net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc >>
net/linphone-base (4/4)
]0;portmaster: net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc >>
net/linphone-base (4/4)
===>>> Port directory: /usr/ports/net/linphone-base

===>>> Launching 'make checksum' for net/linphone-base in background
===>>> Gathering dependency list for net/linphone-base from ports
===>>> Launching child to install audio/gsm

===>>> net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc >>
net/linphone-base >> audio/gsm (5/5)
]0;portmaster: net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc >>
net/linphone-base >> audio/gsm (5/5)
===>>> Port directory: /usr/ports/audio/gsm

===>>> Launching 'make checksum' for audio/gsm in background
===>>> Gathering dependency list for audio/gsm from ports
===>>> Initial dependency check complete for audio/gsm

===>>> Continuing initial dependency check for net/linphone-base
===>>> Launching child to install audio/speex

===>>> net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc >>
net/linphone-base >> audio/speex (6/6)
]0;portmaster: net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc >>
net/linphone-base >> audio/speex (6/6)
===>>> Port directory: /usr/ports/audio/speex

===>>> Launching 'make checksum' for audio/speex in background
===>>> Gathering dependency list for audio/speex from ports
===>>> Initial dependency check complete for audio/speex

===>>> Continuing initial dependency check for net/linphone-base
===>>> Launching child to install net/libexosip2

===>>> net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc >>
net/linphone-base >> net/libexosip2 (7/7)
]0;portmaster: net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc >>
net/linphone-base >> net/libexosip2 (7/7)
===>>> Port directory: /usr/ports/net/libexosip2

===>>> Launching 'make checksum' for net/libexosip2 in background
===>>> Gathering dependency list for net/libexosip2 from ports
===>>> Launching child to install net/libosip

===>>> net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc >>
net/linphone-base >> net/libexosip2 >> net/libosip (8/8)
]0;portmaster: net/kdenetwork4 >> net-im/kopete-kde4 >> audio/msilbc >>
net/linphone-base >> net/libexosip2 >> net/libosip (8/8)
===>>> Port directory: /usr/ports/net/libosip

===>>> Launching 'make checksum' for net/libosip in background
===>>> Gathering dependency list for net/libosip from ports
===>>> Initial dependency check complete for net/libosip

===>>> Continuing initial dependency check for net/libexosip2
===>>> Initial dependency check complete for net/libexosip2

===>>> Continuing initial dependency check for net/linphone-base
===>>> Initial dependency check complete for net/linphone-base

===>>> Continuing initial dependency check for audio/msilbc
===>>> Initial dependency check complete for audio/msilbc

===>>> Continuing initial dependency check for net-im/kopete-kde4
===>>> Launching child to install multimedia/libv4l

===>>> net/kdenetwork4 >> net-im/kopete-kde4 >> multimedia/libv4l (9/9)
]0;portmaster: net/kdenetwork4 >> net-im/kopete-kde4 >>
multimedia/libv4l (9/9)
===>>> Port directory: /usr/ports/multimedia/libv4l

===>>> Launching 'make checksum' for multimedia/libv4l in background
===>>> Gathering dependency list for multimedia/libv4l from ports
===>>> Initi

hmmm, "build --from sd" on openoffice-3 ?

2013-08-05 Thread Gary Aitken
While trying to build openoffice-3, 
I get an error as follows:
...
sw deliver
deliver -- version: 275594
COPY: build.lst -> 
/usr/ports/editors/openoffice-3/work/aoo-3.4.1/main/solver/341/unxfbsdx.pro/inc/sw/build.lst
LOG: writing 
/usr/ports/editors/openoffice-3/work/aoo-3.4.1/main/solver/341/unxfbsdx.pro/inc/sw/deliver.log
Module 'sw' delivered successfully. 1 files copied, 0 files unchanged

1 module(s): 
sd
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making 
/usr/ports/editors/openoffice-3/work/aoo-3.4.1/main/sd/source/ui/toolpanel

When you have fixed the errors in that module you can resume the build by 
running:

build --from sd



But there is no "build",
and no "make build"

If I do a simple "make" the port build completes, and a "make install" installs,
but I'm concerned about the "sd" module being messed up and would like to 
rebuild only so I can find what went wrong without rebuilding the whole dang
thing.  Unfortunately, I didn't pipe the output to a file...

Can anyone tell me how to do the equivalent of "build --from sd"?

Thanks,

Gary

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