On 5/14/2014 12:54 AM, John Marino wrote:
On 5/14/2014 09:42, Pavel Timofeev wrote:
Hi!
After this commit to regular ports tree both zabbix (2.0 and 2.2)
ports was messed.
For example:
> Options available for the single DB: you have to select exactly
one of them
MYSQL=on: MySQL databa
.5.0
1 gem installed
Installing RDoc documentation for nokogiri-1.5.0...
===> Registering installation for rubygem-nokogiri-1.5.0
I also want to note (in case anyone else searches for this) that
rubygem-net-ldap port also had the same issue for me and this fixed that
po
r code 1
Stop in /usr/ports/www/redmine.
*** [install] Error code 1
Stop in /usr/ports/www/redmine.
--
Adam Strohl
http://www.ateamsystems.com/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
if I don't intervene. Is there any
way to see what it's trying to do at this stage? Or is this something
anybody else has run into?
Try using truss (ie; "truss make install")
--
Adam Strohl
http://www.ateamsystems.com/
__
d do the same, as it
could take *hours* to build and you would be left without the port in
the meantime.
Good call.
--
Adam Strohl
http://www.ateamsystems.com/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
On 6/11/2012 4:30, Bryan Drewery wrote:
On 6/10/2012 4:27 PM, Adam Strohl wrote:
Where/when would this trigger?
This could block the upgrade as soon as they try to build it if they
already have the ini and do not have a sample file.
The issue is that most things (ie; people or portupgrade
a typo but just in case: Its the local.ini file
that is the issue (and contains the overrides against default.ini as
well as the admin account usernames and password hashes).
I've grabbed your PR and will investigate tomorrow.
Cool, thanks!
--
Ad
ck up the file before upgrading?
Or is /usr/ports/UPDATING it? (and do I need to do anything special to
have this listed there?)
P.S.
Any other feedback on the PR/diff is welcome.
--
Adam Strohl
http://www.ateamsystems.com/
___
freebsd-ports@freeb
On 6/4/2012 21:59, Erich wrote:
Hi,
On 04 June 2012 21:10:31 Adam Strohl wrote:
On 6/4/2012 18:36, Adam Strohl wrote:
On 6/4/2012 18:07, Erich wrote:
yes, you installed bash and screen first.
Can you try it without?
From a 100% clean install:
- portsnap fetch extract update
- compiled
On 6/4/2012 18:36, Adam Strohl wrote:
On 6/4/2012 18:07, Erich wrote:
yes, you installed bash and screen first.
Can you try it without?
From a 100% clean install:
- portsnap fetch extract update
- compiled x-org + VMware driver
No issues, works fine.
On 6/4/2012 18:07, Erich wrote:
yes, you installed bash and screen first.
Can you try it without?
Doesn't tinderbox do this every night?
I really try to install X as the first thing after I finished installation.
>
I wonder why you need bash from the ports at that stage?
Because that is
On 6/4/2012 4:23, Erich Dollansky wrote:
Hi,
On 03 June 2012 PM 11:41:12 Adam Strohl wrote:
On 6/3/2012 19:19, Erich Dollansky wrote:
do a simple thing. Install a naked 8.3, 9.0 or 10.0 on a fresh hard disk. Get
then the ports tree and start compiling X.
I did not get a running system since
On 6/3/2012 19:19, Erich Dollansky wrote:
do a simple thing. Install a naked 8.3, 9.0 or 10.0 on a fresh hard disk. Get
then the ports tree and start compiling X.
I did not get a running system since at least 2007 when I did this. There was
always at least one manual intervention needed.
I di
On 6/3/2012 17:24, Etienne Robillard wrote:
Technical debt perhaps counts when upstream vendor "new versions" breaks
things unexpectingly ?
For this to happen though that means one of two things:
1. The port maintainer has updated the port to grab this new version,
and tested it (and it worke
14 matches
Mail list logo
