My recent attempts to upgrade ImageMagick (to the currently offered
MacPorts-version @6.8.0-7) keep failing.
*# port installed imagemagick*
The following ports are currently installed:
ImageMagick
@6.8.0-2_0+graphviz+hdri+jbig+jpeg2+lqr+mpeg+pango+perl+q16+rsvg+wmf
(active)
*# sudo port -p
Oh, *blush*
Thanks, Ryan. (I had searched in bugzilla before posting, but I didn't find
it. Now will search double-as-hard before I file my building problems for
argyll...)
On Tue, Feb 12, 2013 at 12:59 AM, Ryan Schmidt ryandes...@macports.orgwrote:
On Feb 11, 2013, at 16:53, Kurt
Hi, all.
I'm trying to install the highlight port. But the build stage does not
complete:
[]
/usr/bin/clang++ -Wall -O2 -DNDEBUG -c -I ./include/ -I/usr/include/lua5.1
-fno-strict-aliasing ./core/Diluculum/LuaValue.cpp
/usr/bin/clang++ -Wall -O2 -DNDEBUG -c -I ./include/
Schmidt ryandes...@macports.orgwrote:
On Aug 13, 2013, at 14:34, Kurt Pfeifle wrote:
I'm trying to install the highlight port. But the build stage does not
complete:
I believe this bug was already reported:
https://trac.macports.org/ticket/39932
I assume this old version of highlight
Sometimes I'm interested in finding out the differences between the old and
the new-to-be installed version of a port.
Is there a canonical way to get access to a changelog?
I'm interested in the upstream changelog within the sources (should there
be one) as well as in the changes the port
On Thu, May 28, 2015 at 7:28 PM, Jeremy Lavergne jer...@lavergne.gotdns.org
wrote:
End users probably don't read the man pages to even know these flags
exist.
That's what I already hinted at in my last mail.
We're left wondering how and why you're even using them.
-p Despite
On Wed, May 27, 2015 at 11:54 PM, Lawrence Velázquez lar...@macports.org
wrote:
On May 27, 2015, at 4:37 PM, Kurt Pfeifle kurt.pfei...@googlemail.com
wrote:
[]
girara was updated an hour ago. Please run a selfupdate and try upgrading
again.
Thanks, it works now.
P.S. Unrelated: Stop
Sorry, I had a typo in my previous message.
I provided the output of `port log zathura` (not `port log girara` as it
stated).
On Wed, May 27, 2015 at 10:37 PM, Kurt Pfeifle kurt.pfei...@googlemail.com
wrote:
$ sudo port -pf upgrade zathura
--- Computing dependencies for zathura
$ sudo port -pf upgrade zathura
--- Computing dependencies for zathura
--- Building zathura
Error: org.macports.build for port zathura returned: command execution failed
Please see the log file for port zathura for details:
I do not fully understand how MacPorts is working, so please bear with me.
I currently have a problem to upgrade a number of ports, including
ghostscript, gd2, gimp-gap, gdk-pixbuf2, MyPaint and tiff.
My suspicion is that it all tracks back to a problem with upgrading tiff:
$ port outdated tiff
wrote:
On 08.08.2015 11:43 AM, Kurt Pfeifle wrote:
But I have every package installed which has /jpeg/ in its name:
|$ port installed *jpeg* jpeg @9a_1+universal (active) jpeg2ps @1.9_0
(active)
jpegoptim @1.2.4_1 (active) libjpeg-turbo @1.3.1_0 libjpeg-turbo @1.4.0_0
libjpeg-turbo
If I’m not mistaken, the two ports for argyll and num-utils both install a
file /opt/local/bin/average an are therefore conflicting. Both average
commands do very different things, BTW.
Should I open a ticket?
___
macports-users mailing list
When trying to install some ports on a newly upgraded Yosemite system, I
get these lines:
Warning: All compilers are either blacklisted or unavailable;
defaulting to first fallback option
For example, it happens for the sam2p port. Here this line is repeated
about two dozen times even:
---
On Fri, Aug 14, 2015 at 5:37 AM, Ryan Schmidt ryandes...@macports.org
wrote:
On Aug 12, 2015, at 4:07 PM, Kurt Pfeifle wrote:
If I’m not mistaken, the two ports for argyll and num-utils both install
a file /opt/local/bin/average an are therefore conflicting. Both average
commands do very
On Fri, Aug 14, 2015 at 5:34 AM, Ryan Schmidt ryandes...@macports.org
wrote:
On Aug 12, 2015, at 8:09 PM, Kurt Pfeifle wrote:
When trying to install some ports on a newly upgraded Yosemite system, I
get these lines:
Warning: All compilers are either blacklisted or unavailable
I am interested to learn about newly added ports.
Is there a "port list" command that can sort ports according to their
release date?
Most likely, at the present time, there's none.
Is there another method (web interface or trac ticket query or ...?) which
I could employ to find *quickly* out
On Fri, Dec 18, 2015 at 9:00 PM, <
macports-users-requ...@lists.macosforge.org> wrote:
> At the moment, you can only filter the Subversion commit log and look
> for added Portfiles. With a little bit of quick hacking I came up with
> this command, which prints the port directories added in the
On Fri, Dec 18, 2015 at 10:01 PM, Kurt Pfeifle <kurt.pfei...@googlemail.com>
wrote:
>
> On Fri, Dec 18, 2015 at 9:00 PM, <
> macports-users-requ...@lists.macosforge.org> wrote:
>>
>> svn log -v -r"{$(date -v-2w +'%Y-%m-%d')}":HEAD
>> https://
On Sun, Apr 3, 2016 at 3:17 AM, Clemens Lang <c...@macports.org> wrote:
>
> On Sat, Apr 02, 2016 at 10:59:11PM +0200, Kurt Pfeifle wrote:
> > Maybe I can convince MacPorts developers to change where they fetch
> > their own sources?
> > I'm not sure if it indeed
>
> > Last night, sourceforge was returning an html file saying that SF was
> > in "disaster recovery mode". The checksum check baled out at this
> > point.
> >
> > This morning, something a bit different is happening, but there's
> > still a checksum issue.
>
> That's
20 matches
Mail list logo
