On Fri, 23 Sep 2016 16:06:16 +0200, Ryan Schmidt
wrote:
On Sep 23, 2016, at 08:51, j. van den hoff wrote:
installation and upgrading of the pdftk package fails (and does so for
some time) issuing:
"pdftk currently does not build on OS X 10.11 or greater"
any chance to
installation and upgrading of the pdftk package fails (and does so for
some time) issuing:
"pdftk currently does not build on OS X 10.11 or greater"
any chance to see pdftk working again any time soon? or is it an upstream
problem?
thanks
joerg
--
Using Opera's revolutionary email client
if it helps, I'll type in everything you want (expect `/bin/rm -r' I mean
;-)) to get more info and solve the issue. just let me know (possibly
off-list as well).
On Wed, 16 Mar 2016 21:31:54 +0100, Sean Farley wrote:
j. van den hoff writes:
On Wed, 16 Mar 2016 19:41:39 +
thanks. will try (if it is feasible for a "non-pythonist"). will keep you
informed.
On Wed, 16 Mar 2016 21:47:38 +0100, Sean Farley wrote:
j. van den hoff writes:
if it helps, I'll type in everything you want (expect `/bin/rm -r' I
mean
;-)) to get more info
On Wed, 16 Mar 2016 19:41:39 +0100, Sean Farley wrote:
j. van den hoff writes:
on one of two machines (both running 10.10.5 and current `port')
installation of py-hgsubversion fails with (end of logfile
on one of two machines (both running 10.10.5 and current `port')
installation of py-hgsubversion fails with (end of logfile):
8<--
...
CC='/usr/bin/clang'
CC_PRINT_OPTIONS='YES'
CC_PRINT_OPTIONS_FILE='/o
I encountered this today (current `port' and osx 10.10.5), when upgrading
`sc'. the tail of the log file read:
8<--
:debug:destroot destroot phase started at Thu Jan 28 12:57:17 CET 2016
:notice:destroot ---> Staging sc into destroot
:info:de
On Fri, 20 Nov 2015 22:03:23 +0100, Ian Wadham wrote:
On 21/11/2015, at 7:15 AM, Bradley Giesbrecht wrote:
Bam, confidence restored!
Congratulations, Ryan! It is great to know that you will be
the person handling this important job.
I hope you will still find some time to answer queries on
On Wed, 18 Nov 2015 22:19:58 +0100, Brandon Allbery
wrote:
On Wed, Nov 18, 2015 at 4:17 PM, j. van den hoff
wrote:
well, groff_char is a manpage from the groff project itself and I would
be
surprised if it has changed much (and in a backward incompatible way!)
in
recent years (but did
On Wed, 18 Nov 2015 22:08:58 +0100, Brandon Allbery
wrote:
On Wed, Nov 18, 2015 at 4:07 PM, j. van den hoff
wrote:
ah yes, never occured to me tht there might be a man port as well. thank
you for this solution. regarding "satisfactory": for my personal use,
yes
it is. gene
On Wed, 18 Nov 2015 22:01:32 +0100, Ryan Schmidt
wrote:
On Nov 18, 2015, at 1:43 PM, j. van den hoff wrote:
I see the following output from `man groff_char' with version 1.22.3 of
`groff' under macos 10.10.5:
/usr/bin/tbl::294: unrecognised format `O'
/usr/bin/tbl::294: gi
I see the following output from `man groff_char' with version 1.22.3 of
`groff' under macos 10.10.5:
/usr/bin/tbl::294: unrecognised format `O'
/usr/bin/tbl::294: giving up on this table
(many more similar lines following)
and the finally appearing manpage indeed does not contain the tables
lis
me _how_ this inconsistency can occur in the first place. any ideas how to
proceed (apart from opening a ticket, I mean ;-))
joerg
On Sat, 26 Sep 2015 00:29:54 +0200, Mojca Miklavec
wrote:
On Fri, Sep 25, 2015 at 5:52 PM, j. van den hoff wrote:
not sure whether this qualifies for a ticke
On Sat, 26 Sep 2015 00:29:54 +0200, Mojca Miklavec
wrote:
On Fri, Sep 25, 2015 at 5:52 PM, j. van den hoff wrote:
not sure whether this qualifies for a ticket: after recent (~ 2 days
ago)
`port upgrade outdated' postscript generation via `ghostscript' fails
for me
with an er
not sure whether this qualifies for a ticket: after recent (~ 2 days ago)
`port upgrade outdated' postscript generation via `ghostscript' fails for
me with an error
Error: /invalidfont in /findfont
Operand stack:
Times-Roman@0 --nostringval-- Times-Roman
Execution stack:
%interp_exi
I see reproducible crashes of midori on a macpro under 10.10.3 with the
error message "illegal instruction". I suspect this error is due to some
problem with the webkit-gtk @2.4.8_1+video package since I get the same
error message from a different browser (external to macports) which I
comp
I just did a `port selfupdate; port upgrade outdated' run under macos
10.10.3 on a mac pro. `octave' fails like this during the configure phase
(final section of main.log):
8<--
:info:configure checking whether we are using the GNU Fortran 77
compiler... no
:info
On Mon, 13 Apr 2015 12:34:00 +0200, Ryan Schmidt
wrote:
On Apr 13, 2015, at 4:27 AM, j. van den hoff wrote:
one marginal observation I made: after `port deactivate installed'
when executing `port installed active' I receive the message "None of
the specified ports are in
On Mon, 13 Apr 2015 11:34:29 +0200, Chris Jones
wrote:
On 13/04/15 10:27, j. van den hoff wrote:
thanks to both of you for your answers and clarifications.
On Mon, 13 Apr 2015 04:04:14 +0200, Ryan Schmidt
wrote:
On Apr 12, 2015, at 5:54 AM, j. van den hoff wrote:
I just have upgraded
thanks to both of you for your answers and clarifications.
On Mon, 13 Apr 2015 04:04:14 +0200, Ryan Schmidt
wrote:
On Apr 12, 2015, at 5:54 AM, j. van den hoff wrote:
I just have upgraded two x86_64 machines from 10.9. to 10.10.3 and
upgraded one of them according to the migration
I just have upgraded two x86_64 machines from 10.9. to 10.10.3 and
upgraded one of them according to the migration guide (i.e.
uninstalled/reinstalled all ~ 800 macports packages). this took an
astonishing long time (over night, basically) partly due to a multi-hour
recompilation of the `at
On Sat, 11 Apr 2015 13:38:39 +0200, Ryan Schmidt
wrote:
On Apr 11, 2015, at 6:36 AM, j. van den hoff wrote:
very good -- thanks a lot! and I hope that you are right regarding it
being easy ...
Fixed. Wait 30 minutes, run "sudo port selfupdate", and then try again.
gee, tha
very good -- thanks a lot! and I hope that you are right regarding it
being easy ...
On Sat, 11 Apr 2015 13:28:27 +0200, Ryan Schmidt
wrote:
On Apr 11, 2015, at 5:46 AM, j. van den hoff wrote:
I ran into this problem today after upgrading from 10.9 to 10.10.3. the
install fails
hi list,
I ran into this problem today after upgrading from 10.9 to 10.10.3. the
install fails with exactly the same error messages reported 4 months ago
in the ticket https://trac.macports.org/ticket/46059. seemingly nothing
could be done about the problem since then. is there any hope tha
I found only one (seemingly unanswered post in the archive: does somebody
now where this warning comes from in the
`ports clean all' process (observed under 10.9.2)? more importantly: are
they relevant?
e.g., one instance happens here:
...
---> Cleaning jump
Warning: No value for java JAVA_
On Apr 16, 2014, at 9:59, j. van den hoff
wrote:
work/ksh93-2012-08-01/arch/darwin.i386-64/bin/ksh
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
___
macports-users mailing list
macports-users@lists.macosforge.or
I'm currently in the process of setting up macports from scratch after
upgrade ot 10.9(.2). so far the migration procedure found on the macports
page mostly has worked (some glitches, of course), but now I see some real
problems:
sudo port install ksh93
runs just fine (silently), seemingl
On Wed, 14 Aug 2013 16:07:11 +0200, Brandon Allbery
wrote:
On Wed, Aug 14, 2013 at 7:13 AM, j. van den hoff
wrote:
---> Cleaning apr-util
Error: arpack: Variant openmpi conflicts with gcc43
Error: Unable to open port: Error evaluating variants
To report a bug, follow the instructions
not sure whether this should be reported via the ticket system:
I just tried to `upgrade outdated' after a `selfupdate' and this failed
with:
sudo port upgrade outdated
---> Fetching archive for apr
---> Attempting to fetch apr-1.4.8_0.darwin_12.x86_64.tbz2 from
http://lil.fr.packages.mac
On Wed, 19 Jun 2013 13:09:15 +0200, Brandon Allbery
wrote:
On Wed, Jun 19, 2013 at 6:33 AM, j. van den hoff
wrote:
1.
the duplicate listings do not hint at any relevant corruption of my
macports setup, right?
Correct.
2.
what is the reason for the occurrence of the duplicate listings
I have seen this already with 10.6 and currently with 10.8:
`port list installed' frequently reports several of the installed ports
repeatedly (I see 2-4 times) on consecutive lines (including the
`@num.num' version designation, i.e. seemingly exact duplicates). which
ports are affected loo
has someone experience with the `uzbl' web browser (under macos 10.6.8
with uzbl @2011.11.28) using Apple's X11?
I installed uzbl yesterday on two machines both running 10.6.8 but one
using Apple's X11, the other one using Xquartz. on the latter everything
is fine, on the former I get rep
after upgrading `unison -doc all' and `unison -doc topics' both show an
empty string instead of the complete manual or list of topics,
respectively, as these commands should (and did, at least with version
2.32).
I'm guessing: the manual is in a different text file (and not linked into
th
hi,
this seems either a problem of the `hg' or the `hgsubversion' package
(probably the latter):
after upgrading to hg 2.0, `hg' does no longer find the `hgsubversion'
extension in its search path, i.e. the entry
`hgsubversion=' (without explicit path) does no longer work in `.hgrc'.
the
On Tue, 22 Nov 2011 13:53:46 +0100, Ryan Schmidt
wrote:
On Nov 22, 2011, at 05:49, j. van den hoff wrote:
not so much a macports question, but probably a ksh93 bug (or so I do
believe), which I don't know where to report:
I would appreciate any feedback whether this behaviour is
hi,
not so much a macports question, but probably a ksh93 bug (or so I do
believe), which I don't know where to report:
short version:
==
the `read' built-in is supposed to read a single input line (up to a
linefeed). it does'nt work correctly with very long input lines but rath
hi,
I'm using dblatex as backend to asciidoc for pdf production. I noticed
massive latency
(e.g. for a one-page document real time 17 sec, system+user) 3 sec.) when
doing
this. I don't know anything about docbook/xml stuff but after quite some
searching found out that
the problem is relate
hi,
FYI: after doing a `port selfupdate; port upgrade outdated' this bug
surfaced again, i.e. it is still not patched
in the macports `gv' package.
if I knew how to do it I would help out, but I presume it's easy for
someone from the macports core group (one-line
patch to /opt/local/share/
38 matches
Mail list logo
