Question regarding MONO port for FreeBSD

[J. Buck Caldwell]

This address is listed as the Maintainer for the MONO port in the
FreeBSD Ports tree. The version in that tree is getting quite old - are
there plans to update it?

[Phillip N.]

Hi Buck,

Sure there is, in the bsd# ports repo (not the official freebsd ones)
there is version 2.0 avaible.
There are some problems with it, ones they go the official ports will be
updated.

Any help about this (testing, feedback, etc) would be helpful!

good luck.

--
Phillip N. <pneu...@gmail.com>

[Romain Tartière]

Yup! I'm working on it right now!

You can track the BSD# subversion repository for updates on
http://bsd-sharp.googlecode.com/

My tinderbox build the whole thing: http://tinderbox.sigabrt.org/

With kind 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)

[Paul Hoffman]

At 9:30 AM -0400 9/1/08, Phillip N. wrote:
>Any help about this (testing, feedback, etc) would be helpful!

What about on reporting bugs? I sent a message to the list on 5/11/08
with a crash bug that never was responded to. The a2c project (which
is based on .NET/Mono) is now catching grief for not working witht
the current Mono on BSD, but we can't seem to get anyone's attention
on fixing it.

[Phillip N.]

Hi Paul,

We switched the mailing list after May.
Please report issues to http://code.google.com/p/bsd-sharp/issues/list

Thanks!


>

[Romain Tartière]

Hi Paul!

I can't find any reference to your message in the list archives [1] nor
to port named 'a2c' in the FreeBSD ports tree [2] (or even a new port
request in the FreeBSD PR system [3])...

Am-I missing something?

May you give more details about the problem and fill-in a bug report in
the issue tracking system [4]?

Thank you,
Romain

References:
1. http://groups.google.com/group/bsd-sharp/topics
2. http://www.freshports.org/search.php?query=a2c
3. http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports&text=a2c
4. http://code.google.com/p/bsd-sharp/issues/list

[Paul Hoffman]

At 8:20 PM +0200 9/1/08, Romain Tartière wrote:
>Hi Paul!
>
>On Mon, Sep 01, 2008 at 08:57:35AM -0700, Paul Hoffman wrote:
>> At 9:30 AM -0400 9/1/08, Phillip N. wrote:
>> >Any help about this (testing, feedback, etc) would be helpful!
>>
>> What about on reporting bugs? I sent a message to the list on 5/11/08
>> with a crash bug that never was responded to. The a2c project (which
>> is based on .NET/Mono) is now catching grief for not working witht the
>> current Mono on BSD, but we can't seem to get anyone's attention on
>> fixing it.
>
>I can't find any reference to your message in the list archives [1]

As I said, I sent this in May. See
<http://forge.novell.com/pipermail/bsd-sharp-list/2008-May/001218.html>

> nor
>to port named 'a2c' in the FreeBSD ports tree [2] (or even a new port
>request in the FreeBSD PR system [3])...

We are not trying to put this in the FreeBSD ports system until we
can be sure it will work reliably with Mono.

>Am-I missing something?

You may have missed the previous message. To reiterate:

==========
There seems to be a crash bug that doesn't exist in 1.2. In trying to
build a2c (see <http://code.google.com/p/a2c/>), lots and lots of
stuff makes, but then:

# make
gmcs -out:a2c.exe -debug+ -warn:0 AsnFile.cs C_Emitter.cs
C_Sharp_Emitter.cs CodeEmitter.cs Constraints.cs Error.cs lex.l.cs
LogError.cs parser.y.cs Program.cs Rule.cs SymbolTable.cs Token.cs
Type.cs Value.cs
Running a sanity test to see if the new a2c.exe works
mono a2c.exe -out=sanitytest ../test/rfc3280.asn ../test/pkix-common.asn
Fatal error 'thr_resume_wrapper: thread has returned from
_thread_switch' at line 1125 in file
/usr/src/lib/libpthread/thread/thr_kern.c (errno = 22)
Stacktrace:

Abort trap (core dumped)
*** Error code 134

Stop in /usr/home/phoffman/a2c/trunk/a2c.
#

1.9 is the first version past 1.2 that I have tried this with.

How can I help you debug this?
==========

>May you give more details about the problem and fill-in a bug report in
>the issue tracking system [4]?

Now done.

[Paul Hoffman]

So, um, any progress on this? I submitted the bug as you asked
(<http://code.google.com/p/bsd-sharp/issues/detail?id=2>), but
haven't seen any action. I'm still happy to help debug any way I can.

--Paul Hoffman

[Paul Hoffman]

Greetings again. I'm trying to make the current Mono on FreeBSD 7.0.
I do a clean install of FreeBSD 7.0, then get /usr/ports up-to-date
with cvsup. I then download mono-merge and install it and run it. I
then go to /usr/ports/lang/mono and 'make'. It doesn't work:

===> Vulnerability check disabled, database not found
=> mono-2.0.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch from
http://mono.ximian.com/monobuild/preview/sources/mono/.
fetch:
http://mono.ximian.com/monobuild/preview/sources/mono/mono-2.0.tar.bz2:
size mismatch: expected 19362592, actual 19320767
=> Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/.
fetch:
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mono-2.0.tar.bz2:
File unavailable (e.g., file not found, no access)
=> Couldn't fetch it - please try to retrieve this
=> port manually into /usr/ports/distfiles/ and try again.
*** Error code 1

Stop in /usr/ports/lang/mono.

Can someone help here?

--Paul Hoffman

[Romain Tartière]

Hi Paul,

The Mono team release preview tarballs whose filename does not change:
the files are updated in-place. As a consequence, each time a new
preview release is made available, the BSD# ports distinfos have to be
updated.

I have committed such an update a few minutes ago and am re-building
mono-related stuff in my tinderbox in order to be synced with this new
release).

FYI, you can disable checksum verification setting NO_CHECKSUM in your
environment, or update the distinfo file using `make makesum'. Refer to
ports(7) for more details. Be careful however to check that you do not
have a deprecated file fetched in your distfiles directory. In doubt,
delete the tarball and `make fetch' one more time.

With kind regards,
Romain

[Paul Hoffman]

>The Mono team release preview tarballs whose filename does not change:
>the files are updated in-place. As a consequence, each time a new
>preview release is made available, the BSD# ports distinfos have to be
>updated.

Yes, I figured that.

>I have committed such an update a few minutes ago and am re-building
>mono-related stuff in my tinderbox in order to be synced with this new
>release).

And that seems to work now. That is, 'mono-merge; make' at least got
past the checksum failure.

>FYI, you can disable checksum verification setting NO_CHECKSUM in your
>environment, or update the distinfo file using `make makesum'. Refer to
>ports(7) for more details. Be careful however to check that you do not
>have a deprecated file fetched in your distfiles directory. In doubt,
>delete the tarball and `make fetch' one more time.

I'm not sure about this. Are you saying that, as new pre-release
tarballs come out, I will have the problem again? I'm *really*
hesitant to tell my system to ignore checksum errors.

[Phillip N.]

El lun, 22-09-2008 a las 09:48 -0700, Paul Hoffman escribió:
> I'm not sure about this. Are you saying that, as new pre-release
> tarballs come out, I will have the problem again? I'm *really*
> hesitant to tell my system to ignore checksum errors.

Yes, if the original tarball changes, the port will notice that.
This happends when a new version if comming out, not all the time.
I guess you have two options:

1.- ignore the checksum
2.- make makesum, test if the new version works ok and tell us!

btw, thanks romain for the updates!

good luck!

--
Phillip N. <pneu...@gmail.com>

[Romain Tartière]

On Mon, Sep 22, 2008 at 09:48:27AM -0700, Paul Hoffman wrote:
> I'm not sure about this. Are you saying that, as new pre-release
> tarballs come out, I will have the problem again? I'm *really*
> hesitant to tell my system to ignore checksum errors.

There are two good reason not to ignore checksums:
- If a distfile is invalid it will not trigger an error anymore (and
it has been designed for this purpose...)
- If a port is updated (i.e. distinfo is changed for a mono port), and
you already have an old version of the tarball, the port system will
not figure it out and you will use the new version's Makefile and
pkg-plist with the old sources, and it might not work as expected.
If you don't turn of checksum check, the port system will detect
that the tarball is invalid and will try to continue to fetch it (it
will think the transfer was aborted)... It will fail but seeing the
error message will help you diagnose the problem, remove your local
tarball and retry the update.

Basically, do not turn off checksum check. If you have a failure at the
fetch step, remove the tarball from the distfiles directory and try
again. If the problem is still present, rebuild checksums (or delete the
distinfo file).

Kind regards,