Reading from the previous messages in this group, it seems that there is
a lot of work to do on bringing Mono up-to-date for FreeBSD? I'm
guessing those problems will have to be addressed first before even
considering updating Mono dependant ports?
So asking if there is an update coming/planned for the F-Spot port in
the near future (within 1-2 months) is probably just wishful thinking?
Or not?
FYI: The current port version is 0.4.0, while the latest F-Spot version
is 0.5.0.2.
PS: please put me in CC when replying to the list, since I am not a
member of the list.
Kind regards,
Michiel Detailleur
On Wed, Oct 08, 2008 at 09:18:58PM +0200, Michiel Detailleur wrote:
> Reading from the previous messages in this group, it seems that there
> is a lot of work to do on bringing Mono up-to-date for FreeBSD? I'm
> guessing those problems will have to be addressed first before even
> considering updating Mono dependant ports?
Getting everything working at the same time can be tricky. That's
however what we are trying to do :-)
> So asking if there is an update coming/planned for the F-Spot port in
> the near future (within 1-2 months) is probably just wishful thinking?
> Or not?
>
> FYI: The current port version is 0.4.0, while the latest F-Spot
> version is 0.5.0.2.
We have F-Spot 0.5.0.2 in the BSD# ports tree since a few minutes
(updated from 0.5.0.1) but while it compiles and installs smoothly, I am
not able to use it on my computer. It hangs at startup, truss(1) output
this:
| 80947: gettimeofday({1223634959.765469 },0x0) = 0 (0x0)
| 80947: clock_gettime(0,{1223634959.765658935 }) = 0 (0x0)
| 80947: _umtx_op(0x8af0b20,0x8,0x1,0x8af0b00,0xbf8ecc44,0x286a3c2c) ERR#60 'Operation timed out'
| 80947: gettimeofday({1223634959.866180 },0x0) = 0 (0x0)
| 80947: clock_gettime(0,{1223634959.866382197 }) = 0 (0x0)
| 80947: _umtx_op(0x8af0b20,0x8,0x1,0x8af0b00,0xbf8ecc44,0x286a3c2c) ERR#60 'Operation timed out'
| 80947: gettimeofday({1223634959.970375 },0x0) = 0 (0x0)
| 80947: clock_gettime(0,{1223634959.981228098 }) = 0 (0x0)
I started to hack a shell script to compile SVN revisions of F-Spot
between a known broken version and one starting properly but compilation
dependencies are not the same and build fail with a recent environment
and an old F-Spot release. I think the next move will therefore to add
a lot of debug info to track what's happening (``mono --trace'' aborts).
Any better idea is welcomed!
Regards,
Romain
--
Romain Tartière <rom...@blogreen.org> http://romain.blogreen.org/
pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)