Fix with texlive
-
Build ID: 20140722063200-22014
Job owner: b...@freebsd.org
Buildtime: 33 minutes
Enddate: Tue, 22 Jul 2014 07:04:44 GMT
Revision: 362519
Repository:
Hello, Baptiste.
You wrote 22 июля 2014 г., 1:46:00:
>> There is good news, and there is bad news. The bad news is that
>> print/pdftk actually relies on the Java functionality in the GCC ports
>> to build. The good news is that it seems to be the only such port.
>>
>> Mathieu, is there a way
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
This comes up from time to time. I think most people solve it by
rebuilding docbook.
-- WXS
On Fri, Jul 18, 2014 at 02:06:40AM +0200, David wrote:
> Path: .
> Working Copy Root Path: /usr/ports
> URL: https://svn0.eu.freebsd.org/ports/head
> Relative URL: ^/head
> Repository Root: https://svn0.eu
I get this error all the time, could you expand on reinstalling docbook
as I did this and still get the same error.
Many thanks,
Gary
On 22/07/2014 14:01, Wesley Shields wrote:
This comes up from time to time. I think most people solve it by
rebuilding docbook.
-- WXS
On Fri, Jul 18, 2014 at
Baptiste Daroussin wrote:
Hi all,
I need some testers to have one unique libdrm what ever version xorg is used, we
know the newer version works properly with newer xorg, I have been testing so
far with old xorg and everything seems to work ootb.
Can anyone test and tell me if that works?
basica
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187652
--- Comment #10 from commit-h...@freebsd.org ---
A commit references this bug:
Author: ume
Date: Tue Jul 22 15:02:20 UTC 2014
New revision: 362546
URL: http://svnweb.freebsd.org/changeset/ports/362546
Log:
Make it buildable with Ruby 2.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187652
Hajimu UMEMOTO changed:
What|Removed |Added
Status|In Discussion |Issue Resolved
Resolution
sysutils/py-salt has been broken for the last couple of weeks. The
resulting package didn't include the python egg info directory and as a
result, py-salt crashed on startup. There a PR in bugzilla for this:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191986
>From what I can tell, this pr
>>>On 2014-07-22 17:34, Nick Hilliard wrote:> sysutils/py-salt has been broken
>>>for the last couple of weeks. The
resulting package didn't include the python egg info directory and as a
result, py-salt crashed on startup. There a PR in bugzilla for this:
https://bugs.freeb
On Tue, Jul 22, 2014 at 7:09 PM, olli hauer wrote:
On 2014-07-22 17:34, Nick Hilliard wrote:> sysutils/py-salt has been broken
for the last couple of weeks. The
> resulting package didn't include the python egg info directory and as a
> result, py-salt crashed on startup. There
On 22/07/2014 18:43, Antoine Brodin wrote:
> But I can still bump PORTREVISION on py-salt as for this specific port
> the missing egginfo is harmful? (for most other ports it's harmless)
that would be great, thanks.
Nick
___
freebsd-ports@freebsd.org
I've seen the following crash 2 times (separated by 3 months and
a lot of system update/churn).
Can someone look at it?
borg.lerctr.org dumped core - see /var/crash/vmcore.4
Thu Apr 24 10:39:06 CDT 2014
FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #29 r264823M: Wed Apr
23 09:35:
On Mon, Jul 21, 2014 at 11:32:11PM +0200, Gerald Pfeifer wrote:
> On Thu, 17 Jul 2014, Lev Serebryakov wrote:
> > Maybe, we should encourage ports, which is needed gcc, to use only one
> > version? If many ports needs 4.8, maybe, we should bump "any" version to
> > 4.8 for gcc-less systems? And
It worked! Thanks. But now I get this instead.
===> Checking if devel/git already installed
===> Registering installation for git-2.0.2
pkg-static:
lstat(/usr/ports/devel/git/work/stage/usr/local/libexec/git-core/git-http-fetch):
No such file or directory
pkg-static:
lstat(/usr/ports/devel/
Ugh, I thought I thoroughly tested this update. I don't think the
problem is related to OpenSSL from ports at all. I botched the plist
somewhere. I'll take a look at this tomorrow and hopefully get a fix in.
Sorry for the noise, my testing systems have recently undergone some major
changes.
-- WX
16 matches
Mail list logo
