Re: ports with lib_depends: prefering one lib over another

[Baptiste Daroussin]

On Mon, Jul 28, 2014 at 07:32:15AM +0200, Kurt Jaeger wrote:
> Hi!
> 
> In 
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192123
> 
> the suggestion is to use graphics/libjpeg-turbo, if possible
> and use graphics/jpeg, if not.
> 
> Question: How can this be expressed in the ports Makefile ?
> 
It is just not possible so far by design of the ports tree by design,
It needs a more general purpose framework and needs to be carefully thought
about.

In general something allowing a global choosing of libjpeg-turbo vs libjpeg on
amd64 and i386 would be great (there is also the new mozilla fork of
libjpeg-turbo btw :))

a USES sounds a good idea, should it be general to all graphic libraries or only
jpeg?

regards,
Bapt


pgp2hBv8goARb.pgp
Description: PGP signature

FreeBSD ports you maintain which are out of date

[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
+-+
net-mgmt/pandorafms_agent   | 4.0.1   | 5.1-140728
+-+
net-mgmt/pandorafms_console | 4.0.1   | 5.1-140728
+-+
net-mgmt/pandorafms_server  | 4.0.1   | 5.1-140728
+-+
science/gramps  | 3.4.8   | 4.1.0
+-+


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: Tor web browser

[Kurt Jaeger]

Hi!

> https://trillian.chruetertee.ch/svn/freebsd-gecko/trunk/www/linux-tor-browser

Thanks -- is this official ? Is this supposed to be added to the
ports ?

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

Re: Tor web browser

[Jerry]

On Mon, 28 Jul 2014 12:25:25 +0200, Kurt Jaeger stated:

>Hi!
>
>> https://trillian.chruetertee.ch/svn/freebsd-gecko/trunk/www/linux-tor-browser
>
>Thanks -- is this official ? Is this supposed to be added to the
>ports ?
>


It would be great to have the latest version in the ports system.

-- 
Jerry


signature.asc
Description: PGP signature

net/openldap24-server: lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0): No such file or directory

[O. Hartmann]

The port net/openldap24-server fails to register/install with this error:

pkg-static:
lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0):
No such file or directory

The port/installation is corrupted after that - which makes me very happy.

Please CC me.

oh


signature.asc
Description: PGP signature

Re: net/openldap24-server: lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0): No such file or directory

[olli hauer]

On 2014-07-28 15:54, O. Hartmann wrote:
> The port net/openldap24-server fails to register/install with this error:
> 
> pkg-static:
> lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0):
> No such file or directory
> 
> The port/installation is corrupted after that - which makes me very happy.
> 
> Please CC me.
> 
> oh
> 

The following patch should work, seems this is a leftover from libtool -> 
libtool:keepla


Index: openldap24-server/pkg-plist
===
--- net/openldap24-server/pkg-plist  (revision 363124)
+++ net/openldap24-server/pkg-plist  (working copy)
@@ -84,11 +84,9 @@
 %%SHA2%%libexec/openldap/pw-sha2.la
 %%SHA2%%libexec/openldap/pw-sha2.so
 %%SHA2%%libexec/openldap/pw-sha2.so.0
-%%SHA2%%libexec/openldap/pw-sha2.so.0.0.0
 %%SMBPWD%%libexec/openldap/smbk5pwd.la
 %%SMBPWD%%libexec/openldap/smbk5pwd.so
 %%SMBPWD%%libexec/openldap/smbk5pwd.so.0
-%%SMBPWD%%libexec/openldap/smbk5pwd.so.0.0.0
 libexec/slapd
 %%MODULES%%@dirrmtry libexec/openldap
 sbin/slapacl

-- 
br. olli
___
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/openldap24-server: lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0):

[O. Hartmann]

Updating of port net/openldap24-server fails grandios with the following error:

===>  Installing for openldap-sasl-server-2.4.39_2
===>   Registering installation for openldap-sasl-server-2.4.39_2
pkg-static:
lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/pw-sha2.so.0.0.0):
No such file or directory pkg-static:
lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0):
No such file or directory *** Error code 74

Great.

The OS is 




FreeBSD 11.0-CURRENT #0 r269157: Sun Jul 27 22:57:48 CEST 2014 


signature.asc
Description: PGP signature

Re: net/openldap24-server: lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0): No such file or directory

[O. Hartmann]

Am Mon, 28 Jul 2014 17:01:23 +0200
olli hauer  schrieb:

> On 2014-07-28 15:54, O. Hartmann wrote:
> > The port net/openldap24-server fails to register/install with this error:
> > 
> > pkg-static:
> > lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0):
> > No such file or directory
> > 
> > The port/installation is corrupted after that - which makes me very happy.
> > 
> > Please CC me.
> > 
> > oh
> > 
> 
> The following patch should work, seems this is a leftover from libtool -> 
> libtool:keepla
> 
> 
> Index: openldap24-server/pkg-plist
> ===
> --- net/openldap24-server/pkg-plist  (revision 363124)
> +++ net/openldap24-server/pkg-plist  (working copy)
> @@ -84,11 +84,9 @@
>  %%SHA2%%libexec/openldap/pw-sha2.la
>  %%SHA2%%libexec/openldap/pw-sha2.so
>  %%SHA2%%libexec/openldap/pw-sha2.so.0
> -%%SHA2%%libexec/openldap/pw-sha2.so.0.0.0
>  %%SMBPWD%%libexec/openldap/smbk5pwd.la
>  %%SMBPWD%%libexec/openldap/smbk5pwd.so
>  %%SMBPWD%%libexec/openldap/smbk5pwd.so.0
> -%%SMBPWD%%libexec/openldap/smbk5pwd.so.0.0.0
>  libexec/slapd
>  %%MODULES%%@dirrmtry libexec/openldap
>  sbin/slapacl
> 

This works for me.

I'm uncapable of connecting to the bugreport server from my provider's network! 
Can not
issue a PR.


signature.asc
Description: PGP signature

Re: net/openldap24-server: lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0): No such file or directory

[olli hauer]

On 2014-07-28 17:18, O. Hartmann wrote:
> Am Mon, 28 Jul 2014 17:01:23 +0200
> olli hauer  schrieb:
> 
>> On 2014-07-28 15:54, O. Hartmann wrote:
>>> The port net/openldap24-server fails to register/install with this error:
>>>
>>> pkg-static:
>>> lstat(/usr/ports/net/openldap24-server/work/stage/usr/local/libexec/openldap/smbk5pwd.so.0.0.0):
>>> No such file or directory
>>>
>>> The port/installation is corrupted after that - which makes me very happy.
>>>
>>> Please CC me.
>>>
>>> oh
>>>
>>
>> The following patch should work, seems this is a leftover from libtool -> 
>> libtool:keepla
>>
>>
>> Index: openldap24-server/pkg-plist
>> ===
>> --- net/openldap24-server/pkg-plist  (revision 363124)
>> +++ net/openldap24-server/pkg-plist  (working copy)
>> @@ -84,11 +84,9 @@
>>  %%SHA2%%libexec/openldap/pw-sha2.la
>>  %%SHA2%%libexec/openldap/pw-sha2.so
>>  %%SHA2%%libexec/openldap/pw-sha2.so.0
>> -%%SHA2%%libexec/openldap/pw-sha2.so.0.0.0
>>  %%SMBPWD%%libexec/openldap/smbk5pwd.la
>>  %%SMBPWD%%libexec/openldap/smbk5pwd.so
>>  %%SMBPWD%%libexec/openldap/smbk5pwd.so.0
>> -%%SMBPWD%%libexec/openldap/smbk5pwd.so.0.0.0
>>  libexec/slapd
>>  %%MODULES%%@dirrmtry libexec/openldap
>>  sbin/slapacl
>>
> 
> This works for me.
> 
> I'm uncapable of connecting to the bugreport server from my provider's 
> network! Can not
> issue a PR.
> 


Not required, I've taken the liberty to commit the fix

-- 
br. olli
___
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: Cannot get a read lock on a database, it is locked by another process

[Kris Moore]

On 07/27/2014 10:51, Stefan Esser wrote:
> The locking of the pkg database leads to soft failures, but I'm afraid,
> if these soft failures happen to coincide with certain administrative
> tasks, they can lead to unexpected results.
>
> One example is that portmaster fails to detect PKGNG (and then assumes
> to be working in a pre-PKGNG environment), if some pkg subcommand locks
> the database. To repeat:
>
> # pkg version -Bs &
> # pkg info
>
> As long as pkg version runs, pkg info fails to get the read lock (at
> least in the large majority of my tests). You can also prevent any pkg
> command from running, if you STOP (kill -STOP / ^Z) pkg version. Any
> other pkg command will fail, until "pkg version" has been "unstopped"
> and run to completion. This might even be a local DoS, if any command
> that read-locks the package DB for extended time can be executed by
> an unprivileged user.
>
> Similar error messages are reported by pkg_libcheck, which issues
> lots of pkg commands in parallel. (I have observed some 5 lock
> failures per 1000 installed packages on my system).
>
>
> I did not try to test all combinations of simultanous pkg commands
> and did not verify, whether e.g. "pkg upgrade" might be stopped
> half way through because of an error accessing the pkg database,
> but I have seen SQLITE error messages that indicated failed write
> operations (INSERT/UPDATE).
>
> Either the timeouts are too low, or the duration during which the
> database is locked by a single operation is too large (or there is
> no fairness and some processes never get access to the database?).
>
>
> I think this should be fixed, since pkg commands that lock the
> database can be run from CRON or by other means in the background
> and the operator who issues pkg commands in the foreground (or runs
> portmaster) receives spurious error messages (which might still be
> better than the batch jobs doing silly things, after they failed to
> obtain information from the pkg database ...)
>
> Regards, STefan
> ___
> 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"

+1 to this whole thing.

I would prefer that pkg commands simply wait for the DB to become
unlocked again, instead of just failing outright.

We have many scripts which monitor the system, check for updates,
display our GUI store-front, and its really annoying to have random bits
of it fail simply because of bad timing with another pkg process.

-- 
Kris Moore
PC-BSD Software
iXsystems

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

Strange pkg_deinstall behaviour with pkgng

[Andrea Venturoli]

Hello.

I was forced to switch to pkgng on a 9.2 box and I'm now noticing a 
strange behaviour.


Before, "pkg_deinstall -R foo" would deinstall foo and all ports on 
which foo depended, except those who were needed by other ports.


Now, "pkg_deinstall -R foo" will deinstall foo, all ports on which foo 
depends and all ports depending on the ports on which foo depends.


E.g.
Port A depends on B
Port B depends on C
Port D depends on C

With the old behaviour, "pkg_deinstall -R A" would deinstall A and B 
(but not C).

Now it will deinstall A, B, C and D.

Is this normal or expected?
How can I restore the old behaviour?



 Thanks
av.
___
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: Tor web browser

[Darren Pilgrim]

On 7/27/2014 12:30 PM, Jerry wrote:

Sun, 27 Jul 2014 15:24:21 -0400

Is there a port of the "Tor web browser" 
available? The site lists one for BSD, but I would prefer to get it via the
port's system


I think the reason it isn't in ports is because it's literally just a 
portable Firefox with a premade profile.  You can replicate it using 
parts already in ports and a few minutes work creating a Firefox profile.

___
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: pkg create deadlocks and hangs ZFS host

[Michael Gmelin]

I had pkg crash[1] our build host a couple of times today. I could
reproduce the issue on a local machine and opened a detailed bug
report on github[2] which links to a gist containing the patch that's
also attached to this email.

- Michael

[1] Crash like in "power cycle required".
[2] https://github.com/freebsd/pkg/issues/897

-- 
Michael Gmelin
>From d21a99520dc573a566910b37c6b1549cc1b9305f Mon Sep 17 00:00:00 2001
From: Michael Gmelin 
Date: Mon, 28 Jul 2014 21:02:06 +0200
Subject: [PATCH] Disabled implicitly activated "pass mode", which is
 unintuitive and causes deadlocks. (I frankly have no idea what its intended
 use is)

---
 libpkg/packing.c | 4 
 1 file changed, 4 insertions(+)

diff --git a/libpkg/packing.c b/libpkg/packing.c
index 40e806d..461444f 100644
--- a/libpkg/packing.c
+++ b/libpkg/packing.c
@@ -69,7 +69,9 @@ packing_init(struct packing **pack, const char *path, pkg_formats format)
 	archive_read_disk_set_standard_lookup((*pack)->aread);
 	archive_read_disk_set_symlink_physical((*pack)->aread);
 
+#if 0 // disabled, pass mode hangs
 	if (!is_dir(path)) {
+#endif
 		(*pack)->pass = false;
 		(*pack)->awrite = archive_write_new();
 		archive_write_set_format_pax_restricted((*pack)->awrite);
@@ -97,6 +99,7 @@ packing_init(struct packing **pack, const char *path, pkg_formats format)
 			*pack = NULL;
 			return EPKG_FATAL;
 		}
+#if 0 // disabled, pass mode hangs
 	} else { /* pass mode directly write to the disk */
 		pkg_debug(1, "Packing to directory '%s' (pass mode)", path);
 		(*pack)->pass = true;
@@ -104,6 +107,7 @@ packing_init(struct packing **pack, const char *path, pkg_formats format)
 		archive_write_disk_set_options((*pack)->awrite,
 		EXTRACT_ARCHIVE_FLAGS);
 	}
+#endif
 
 	(*pack)->resolver = archive_entry_linkresolver_new();
 	archive_entry_linkresolver_set_strategy((*pack)->resolver,
-- 
2.0.0

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

[QAT] 363158: 4x leftovers, 4x fetch, 12x success

[Ports-QAT]

Rename benchmark/ patch-xy patches to reflect the files they modify.
-

  Build ID:  20140728141800-19922
  Job owner: ad...@freebsd.org
  Buildtime: 6 hours
  Enddate:   Mon, 28 Jul 2014 20:23:04 GMT

  Revision:  363158
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=363158

-

Port:benchmarks/bonnie 2.0.6_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385738/bonnie-2.0.6_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385739/bonnie-2.0.6_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385740/bonnie-2.0.6_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385741/bonnie-2.0.6_1.log

-

Port:benchmarks/dbs 1.1.5_6

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385742/dbs-1.1.5_6.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385743/dbs-1.1.5_6.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385744/dbs-1.1.5_6.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385745/dbs-1.1.5_6.log

-

Port:benchmarks/iozone21 2.01

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385746/iozone21-2.01.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385747/iozone21-2.01.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385748/iozone21-2.01.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385749/iozone21-2.01.log

-

Port:benchmarks/nbench 2.2.3

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385750/nbench-2.2.3.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385751/nbench-2.2.3.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385752/nbench-2.2.3.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385753/nbench-2.2.3.log

-

Port:benchmarks/ttcp 1.12_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   FETCH
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385754/ttcp-1.12_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   FETCH
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385755/ttcp-1.12_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   FETCH
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385756/ttcp-1.12_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   FETCH
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140728141800-19922-385757/ttcp-1.12_1.log


--
Buildarchive URL: 
redports 
___
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: pkg create deadlocks and hangs ZFS host

[Baptiste Daroussin]

On Mon, Jul 28, 2014 at 09:19:57PM +0200, Michael Gmelin wrote:
> I had pkg crash[1] our build host a couple of times today. I could
> reproduce the issue on a local machine and opened a detailed bug
> report on github[2] which links to a gist containing the patch that's
> also attached to this email.
> 
> - Michael
> 
> [1] Crash like in "power cycle required".
> [2] https://github.com/freebsd/pkg/issues/897
> 

This patch will break pkg register which is used by the ports tree, I'll work on
a better patch

regards,
Bapt


pgpvJI0nS0asO.pgp
Description: PGP signature

Re: pkg: Cannot get a read lock on a database, it is locked by another process

[Kevin Oberman]

On Mon, Jul 28, 2014 at 8:34 AM, Kris Moore  wrote:

> On 07/27/2014 10:51, Stefan Esser wrote:
> > The locking of the pkg database leads to soft failures, but I'm afraid,
> > if these soft failures happen to coincide with certain administrative
> > tasks, they can lead to unexpected results.
> >
> > One example is that portmaster fails to detect PKGNG (and then assumes
> > to be working in a pre-PKGNG environment), if some pkg subcommand locks
> > the database. To repeat:
> >
> > # pkg version -Bs &
> > # pkg info
> >
> > As long as pkg version runs, pkg info fails to get the read lock (at
> > least in the large majority of my tests). You can also prevent any pkg
> > command from running, if you STOP (kill -STOP / ^Z) pkg version. Any
> > other pkg command will fail, until "pkg version" has been "unstopped"
> > and run to completion. This might even be a local DoS, if any command
> > that read-locks the package DB for extended time can be executed by
> > an unprivileged user.
> >
> > Similar error messages are reported by pkg_libcheck, which issues
> > lots of pkg commands in parallel. (I have observed some 5 lock
> > failures per 1000 installed packages on my system).
> >
> >
> > I did not try to test all combinations of simultanous pkg commands
> > and did not verify, whether e.g. "pkg upgrade" might be stopped
> > half way through because of an error accessing the pkg database,
> > but I have seen SQLITE error messages that indicated failed write
> > operations (INSERT/UPDATE).
> >
> > Either the timeouts are too low, or the duration during which the
> > database is locked by a single operation is too large (or there is
> > no fairness and some processes never get access to the database?).
> >
> >
> > I think this should be fixed, since pkg commands that lock the
> > database can be run from CRON or by other means in the background
> > and the operator who issues pkg commands in the foreground (or runs
> > portmaster) receives spurious error messages (which might still be
> > better than the batch jobs doing silly things, after they failed to
> > obtain information from the pkg database ...)
> >
> > Regards, STefan
> > ___
> > 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"
>
> +1 to this whole thing.
>
> I would prefer that pkg commands simply wait for the DB to become
> unlocked again, instead of just failing outright.
>
> We have many scripts which monitor the system, check for updates,
> display our GUI store-front, and its really annoying to have random bits
> of it fail simply because of bad timing with another pkg process.
>
> --
> Kris Moore
> PC-BSD Software
> iXsystems


This is a real pain, but I only see it on one of my systems. That system is
my only i386 system and also my only system running 9.2. Whether that has
anything to do with it, I can't say, but it makes me very nervous. I just
would like to know why only the one system has the problem.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.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"

Scilab 5.5.0

[Max Brazhnikov]

Hi folks,

I've finally got a chance update math/scilab to the latest release.
The patch can be found at
http://people.freebsd.org/~makc/patches/scilab550-20140729.diff.xz

If you prefer a packed port directory:
http://people.freebsd.org/~makc/ports/scilab550-20140729.txz

I've reduced the number of options mainly for simplicity, PVM is not supported 
anymore.

I have tested it on 9-amd64/10-amd64, so I'm interested in other combinations.
Please report back to me in case of success or failure.

Scilab may crash at start up if graphics/libglesv2 is installed, deinstall it 
and try again before reporting a problem.

Max
___
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: pkg create deadlocks and hangs ZFS host

[Michael Gmelin]

> On 28 Jul 2014, at 23:30, Baptiste Daroussin  wrote:
> 
>> On Mon, Jul 28, 2014 at 09:19:57PM +0200, Michael Gmelin wrote:
>> I had pkg crash[1] our build host a couple of times today. I could
>> reproduce the issue on a local machine and opened a detailed bug
>> report on github[2] which links to a gist containing the patch that's
>> also attached to this email.
>> 
>> - Michael
>> 
>> [1] Crash like in "power cycle required".
>> [2] https://github.com/freebsd/pkg/issues/897
> 
> This patch will break pkg register which is used by the ports tree, I'll work 
> on
> a better patch
> 
> regards,
> Bapt

For completeness sake: bapt fixed this properly in
https://github.com/freebsd/pkg/commit/bf4a9a6ec13824036c035ceba01076e5e30841b4

___
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: Scilab 5.5.0

[Kevin Oberman]

On Mon, Jul 28, 2014 at 3:10 PM, Max Brazhnikov  wrote:

> Hi folks,
>
> I've finally got a chance update math/scilab to the latest release.
> The patch can be found at
> http://people.freebsd.org/~makc/patches/scilab550-20140729.diff.xz
>
> If you prefer a packed port directory:
> http://people.freebsd.org/~makc/ports/scilab550-20140729.txz
>
> I've reduced the number of options mainly for simplicity, PVM is not
> supported
> anymore.
>
> I have tested it on 9-amd64/10-amd64, so I'm interested in other
> combinations.
> Please report back to me in case of success or failure.
>
> Scilab may crash at start up if graphics/libglesv2 is installed, deinstall
> it
> and try again before reporting a problem.
>
> Max
> ___
> 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"
>

Max,

Great! But please submit this to buzilla (https://bugs.freebsd.org/bugzilla/)
so it will not get lost. (By the way, if it won't work with libglesv2, add
a CONFLICTS statement to the Makefile.)
--
R. Kevin Oberman, Network Engineer, Retired
___
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"