[FFe][Sync request] Please sync mono-tools 1.9-2 (main) from Debian unstable (main)

[James Westby]

Binary package hint: monodoc-browser

mono-tools is obsolete in Ubuntu, out of step with the rest of the Mono stack in Intrepid. As part of progress towards this bug, a MIR was granted for webkit-sharp (https://bugs.launchpad.net/ubuntu/+source/webkit-sharp/+bug/262719) which allows the package to be synced instead of merged.

Upstream will likely be unable to support problems with a partially-obsolete software stack, and this merge is required to avoid it.

This has been tested in an Intrepid pbuilder and chroot - see attached files.

[James Westby (james-w)]

Hi,

Here is the debdiff against the current Debian version. Please
sponsor it in to the archive.

Thanks,

James

[Jo Shields (directhex)]

Please be aware that the Debian Mono team is removing, wherever possible, dependencies on xulrunner - in this specific instance, mono-tools 1.9-1 has been superceded by 1.9-2 which relies on webkit-sharp instead. As a result, this package can now be switched to Syncing rather than Merging, since webkit-sharp has been synced successfully. However, webkit-sharp is NOT in main.

One desirable aspect of webkit from an Ubuntu perspective is that it requires no Ubuntu-specific hacking on MOZILLA_FIVE_HOME, meaning more syncs and less merges as more packages in Debian are ported.

Please consider promoting webkit-sharp to main, and syncing 1.9-2

[James Westby (james-w)]

On Thu, 2008-08-14 at 07:53 +0000, directhex wrote:
> Please be aware that the Debian Mono team is removing, wherever
> possible, dependencies on xulrunner - in this specific instance, mono-
> tools 1.9-1 has been superceded by 1.9-2 which relies on webkit-sharp
> instead. As a result, this package can now be switched to Syncing rather
> than Merging, since webkit-sharp has been synced successfully. However,
> webkit-sharp is NOT in main.

Hi,

Thanks for the information.

> One desirable aspect of webkit from an Ubuntu perspective is that it
> requires no Ubuntu-specific hacking on MOZILLA_FIVE_HOME, meaning more
> syncs and less merges as more packages in Debian are ported.

Yes, but webkit-sharp in main may be less desirable that this.

> Please consider promoting webkit-sharp to main, and syncing 1.9-2

I have no real idea if this is better. I was asked to merge
mono-tools as it handn't been touched at the point I was asked.
I don't mind my work being thrown away, but it means that I need
at least some guidance.

Is using webkit-sharp instead a good idea?

Thanks,

James

[Jo Shields (directhex)]

Sorry for the delay, forgot to subscribe to this bug.

mono-tools upstream supports several HTML engines, so using gecko-sharp (as with current Ubuntu packages) remains possible. However, the Debian Mono team will no longer be linking mono-tools (or any other Mono package) against gecko-sharp. The question therefore is a question of preference - if Ubuntu developers such as yourself don't mind needing to put in work on a merge whenever mono-tools is updated, then by all means, keep webkit-sharp out of main. If syncing is preferred due to lower admin overhead, then webkit-sharp will be required.

You may also want to look at the other non-webkit changes in 1.9-2 (http://packages.debian.org/changelogs/pool/main/m/mono-tools/mono-tools_1.9-2/changelog), but none of them are exactly vital.

In either case, I'd feel much happier with 1.9-anything in Intrepid compared to the obsolete 1.2.6 currently in there. If you want to go ahead with the existing diff.gz, then feel free, it'll still produce perfectly usable packages.

[James Westby (james-w)]

On Wed, 2008-08-20 at 19:10 +0000, directhex wrote:
> Sorry for the delay, forgot to subscribe to this bug.

Hi,

Thanks for the information.

> mono-tools upstream supports several HTML engines, so using gecko-sharp
> (as with current Ubuntu packages) remains possible. However, the Debian
> Mono team will no longer be linking mono-tools (or any other Mono
> package) against gecko-sharp. The question therefore is a question of
> preference - if Ubuntu developers such as yourself don't mind needing to
> put in work on a merge whenever mono-tools is updated, then by all
> means, keep webkit-sharp out of main. If syncing is preferred due to
> lower admin overhead, then webkit-sharp will be required.

I'd love to get rid of the diff, and it sounds like a good idea.

Webkit is in main, but webkit-sharp isn't yet. I don't know
what the policy is on language bindings. I'll try and see if it's
possible to promote webkit-sharp early enough that we can sync
without problems.

> You may also want to look at the other non-webkit changes in 1.9-2
> (http://packages.debian.org/changelogs/pool/main/m/mono-tools/mono-
> tools_1.9-2/changelog), but none of them are exactly vital.
>
> In either case, I'd feel much happier with 1.9-anything in Intrepid
> compared to the obsolete 1.2.6 currently in there. If you want to go
> ahead with the existing diff.gz, then feel free, it'll still produce
> perfectly usable packages.

That would be the second option, if we can't get the promotion in time.

Thanks,

James

[Steve Langasek (vorlon)]

FFe granted, will sync shortly.

[Steve Langasek (vorlon)]

[Updating] mono-tools (1.2.6-4ubuntu5 [Ubuntu] < 1.9-2 [Debian])
 * Trying to add mono-tools...
  - <mono-tools_1.9-2.dsc: downloading from http://ftp.debian.org/debian/>
  - <mono-tools_1.9.orig.tar.gz: downloading from http://ftp.debian.org/debian/>
  - <mono-tools_1.9-2.diff.gz: downloading from http://ftp.debian.org/debian/>
I: mono-tools [main] -> monodoc-browser_1.2.6-4ubuntu5 [main].
I: mono-tools [main] -> gnunit_1.2.6-4ubuntu5 [universe].
I: mono-tools [main] -> gnunit2_1.2.6-4ubuntu5 [universe].
I: mono-tools [main] -> mono-tools-gui_1.2.6-4ubuntu5 [universe].
I: mono-tools [main] -> mono-tools-devel_1.2.6-4ubuntu5 [universe].