- Remove BROKEN mark; the plist doesn't seem to be broken, and port and package install and deinstall properly (tested on 5-CURRENT). - Satisfy portlint (use a tab after a variable name, not spaces) Port maintainer (tim@n2it.net) is cc'd. Generated with FreeBSD Port Tools 0.50
State Changed From-To: open->feedback Can I ask what version of ImageMagick have you tested with? Because it does not compile against ImageMagick 6.0.6 here. My guess is that it can't link against new 6.x API
Responsible Changed From-To: freebsd-ports-bugs->pav Watch
Pav Lucistnik, 27.09.04, 00:21h CEST: > Can I ask what version of ImageMagick have you tested with? > Because it does not compile against ImageMagick 6.0.6 here. > > My guess is that it can't link against new 6.x API You're right, I have ImageMagick 5.x installed. I wasn't aware that there was a major version upgrade of ImageMagick, or I would have updated that before trying py-magick. There isn't any newer version of the Python bindings, as it seems, so the port remains broken. But the BROKEN string seems to be misleading, then; as the PR mentions, I couldn't find any problems with the plist, and when I asked on ports@, there was no reply. Could you change the message to something more appropriate, maybe? Stefan
V po, 27. 09. 2004 v 11:58, Stefan Walter pí¹e: > > Can I ask what version of ImageMagick have you tested with? > > Because it does not compile against ImageMagick 6.0.6 here. > > > > My guess is that it can't link against new 6.x API > > You're right, I have ImageMagick 5.x installed. I wasn't aware that > there was a major version upgrade of ImageMagick, or I would have > updated that before trying py-magick. There isn't any newer version of > the Python bindings, as it seems, so the port remains broken. > > But the BROKEN string seems to be misleading, then; as the PR mentions, > I couldn't find any problems with the plist, and when I asked on ports@, > there was no reply. Could you change the message to something more > appropriate, maybe? Yes, I will change the BROKEN string to something like 'Does not work with ImageMagick 6.x' after the freeze. Do you think there's any chance that this project will produce a new release in future? Otherwise we can just delete the port, I suppose. -- Pav Lucistnik <pav@oook.cz> <pav@FreeBSD.org> Somebody ought to cross ball point pens with coat hangers so that the pens will multiply instead of disappear.
Pav Lucistnik, 27.09.04, 12:59h CEST: > > But the BROKEN string seems to be misleading, then; as the PR mentions, > > I couldn't find any problems with the plist, and when I asked on ports@, > > there was no reply. Could you change the message to something more > > appropriate, maybe? > > Yes, I will change the BROKEN string to something like 'Does not work > with ImageMagick 6.x' after the freeze. Do you think there's any chance > that this project will produce a new release in future? Otherwise we can > just delete the port, I suppose. I wouldn't object to that; I don't use it, I just saw it was broken and tried to fix it. According to sourceforge.net, the current version was released in April 2003, and it looks like there hasn't been any sign of life of it for a while. Furthermore, the ImageMagick home page lists http://pythonmagick.procoders.net/ for Python bindings, so I guess you're right and we don't need to keep this port around any more. Stefan
State Changed From-To: feedback->closed Broken port removed.