Bug#351430: Bug#350740: Bug#351430: seamonkey for etch ?
On Fri, Sep 22, 2006 at 08:23:26AM +0200, Jeroen van Wolffelaar <[EMAIL PROTECTED]> wrote: > On Fri, Sep 22, 2006 at 07:27:40AM +0200, Mike Hommey wrote: > > Now, some comments on Hendrik-Jan messages: > > > - transition/dummy package (how do I do this?) > > > > The only solution is to make these transition packages from the mozilla > > source package, because they have an epoch. > > You can generate the transition packages from seamonkey just fine -- > you can override the version used in the binary package from > debian/rules -- they do not need to match the source version (though > it's the default and deviating should be done with care). See > gcc-defaults for a well known example. Well, yeah, you can do painful things. I tend to like the KISS principles. ;) Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350740: Bug#351430: seamonkey for etch ?
On Fri, Sep 22, 2006 at 07:27:40AM +0200, Mike Hommey wrote: > Now, some comments on Hendrik-Jan messages: > > - transition/dummy package (how do I do this?) > > The only solution is to make these transition packages from the mozilla > source package, because they have an epoch. You can generate the transition packages from seamonkey just fine -- you can override the version used in the binary package from debian/rules -- they do not need to match the source version (though it's the default and deviating should be done with care). See gcc-defaults for a well known example. But having a seperate source package for the dummy packages is possible too, it's mostly a matter of taste. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350740: Bug#351430: seamonkey for etch ?
On Thu, Sep 21, 2006 at 10:24:16PM -0400, Jaldhar H. Vyas <[EMAIL PROTECTED]> wrote: > On Fri, 22 Sep 2006, James Westby wrote: > > >Hi all, > > > >Sorry to but in, but have you seen the log of > > > >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=350740 > > > >This guy seems pretty interested and active. It seems your work and his > >are uncoordinated at the moment though. > > > > I agree. Hendrik-Jan if you have an account on alioth.debian.org can you > tell me the name. Or if you don't have an account, can you set one up? > Then I will arange for you to get access to the seamonkey SVN repository. > > 1.1 sounds like it should go to experimental. For etch we should > concentrate on 1.0.5 or whatever is the most recent stable version IMO. I think we should try to talk with the release managers. All new major versions of mozilla products are going to be released just after the hypothetical date of the freeze, but since upstream will drop support for the current branches within six months after etch hypothetical release date, that means we'll be on our own for security support quite quickly. On the other hand, the soon to be released branches will be supported at least 6 more months, which means we'll be on our own much later. It is a better long term support plan... > I've already mentioned this to Alexander but I'll say it again, IMO > seamonkey should be one package rather than split up. It is supposed to > be an Internet suite after all and people who want a more fine-grained set > of packages can use firefox et al. I think we should not impose to users who currently use mozilla-browser and al. packages to have everything installed. A meta seamonkey package installing all the fine grained packages would be a good thing though. I know quite a lot of people, including me in the past, using mozilla-browser only, and not caring about the composer or the mail client. Some other do only use the composer and might want to install only it (though these ones would be better using nvu, but composer is going to be somehow resurrected) > btw, I might get some time to work on seamonkey again soon. I have > already uploaded 1.0.5 for Linspire but their standards and ours are > different so I can't simply copy my existing package. I still insists on all the things I said before my vacation, about the patches and all. Please do consider all that, and/or comment http://people.debian.org/~glandium/seamonkey-patches/README Now, some comments on Hendrik-Jan messages: > Unfortunately, building Seamonkey on its own libs (and shipping > them), is also a no-go as the libnspr4-dev and libnss3-dev packages of > xulrunner then conflict with it. > > If anyone knows of a way around this, feel free to comment on this. Don't ship the libraries in /usr/lib. Ship them in /usr/lib/seamonkey like firefox does. You can put them in a common package on which all the seamonkey packages will depend, if you will. > The system myspell dictionaries are now correctly linked (were in > components, are now in dictionaries). Please consider using the system myspell libraries. I have a patch for that, that is already applied to firefox 2.0b2 in experimental. > - transition/dummy package (how do I do this?) The only solution is to make these transition packages from the mozilla source package, because they have an epoch. Cheers Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Fri, 22 Sep 2006, James Westby wrote: Hi all, Sorry to but in, but have you seen the log of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=350740 This guy seems pretty interested and active. It seems your work and his are uncoordinated at the moment though. I agree. Hendrik-Jan if you have an account on alioth.debian.org can you tell me the name. Or if you don't have an account, can you set one up? Then I will arange for you to get access to the seamonkey SVN repository. 1.1 sounds like it should go to experimental. For etch we should concentrate on 1.0.5 or whatever is the most recent stable version IMO. I've already mentioned this to Alexander but I'll say it again, IMO seamonkey should be one package rather than split up. It is supposed to be an Internet suite after all and people who want a more fine-grained set of packages can use firefox et al. btw, I might get some time to work on seamonkey again soon. I have already uploaded 1.0.5 for Linspire but their standards and ours are different so I can't simply copy my existing package. -- Jaldhar H. Vyas <[EMAIL PROTECTED]> La Salle Debain - http://www.braincells.com/debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On (21/09/06 22:06), Mike Hommey wrote: > On Thu, Sep 21, 2006 at 08:56:38PM +0200, Alexander Sack <[EMAIL PROTECTED]> > wrote: > > Sorry, still working on the final security patches. Its because my > > work-capacity has been significantly reduced during the last few weeks by > > severe private-life hazards. > > > > Please understand that I have to fix some real life issues first. > > > > I regret all this, but I did not choose this doom either. I would > > understand if you would not go ahead lifting this package as I have to > > admit that I will not be able to put much time into this any-time soon > > (at least not till nov). > > No problem, I'll try to do something with my own spare time. > > Good luck with your RL issues, whatever they are. > > Mike > Hi all, Sorry to but in, but have you seen the log of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=350740 This guy seems pretty interested and active. It seems your work and his are uncoordinated at the moment though. Thanks, James -- James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/ seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp256r1/nistp256 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Thu, Sep 21, 2006 at 08:56:38PM +0200, Alexander Sack <[EMAIL PROTECTED]>
wrote:
> On Thu, Sep 21, 2006 at 07:43:23PM +0200, Mike Hommey wrote:
> > Hi Alex,
> >
> > On Thu, Aug 31, 2006 at 07:47:01AM +0200, Mike Hommey <[EMAIL PROTECTED]>
> > wrote:
> > > On Wed, Aug 30, 2006 at 10:04:17PM +0200, Alexander Sack <[EMAIL
> > > PROTECTED]> wrote:
> > > > Can you please upload them somewhere for now? When do you leave on
> > > > vacation?
> > >
> > > I'll upload to gluck in ${HOME}/public_html, which means it will be on
> > > people.debian.org/~glandium/. Expect it to be done some time tonight
> > > (local time: GMT+2)
> > >
> > > I'm leaving on sunday, but will more than probably put me away from
> > > saturday.
> >
> > Did you have time to work on seamonkey during the past two weeks ?
> >
>
> Sorry, still working on the final security patches. Its because my
> work-capacity has been significantly reduced during the last few weeks by
> severe private-life hazards.
>
> Please understand that I have to fix some real life issues first.
>
> I regret all this, but I did not choose this doom either. I would
> understand if you would not go ahead lifting this package as I have to
> admit that I will not be able to put much time into this any-time soon
> (at least not till nov).
No problem, I'll try to do something with my own spare time.
Good luck with your RL issues, whatever they are.
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Thu, Sep 21, 2006 at 07:43:23PM +0200, Mike Hommey wrote:
> Hi Alex,
>
> On Thu, Aug 31, 2006 at 07:47:01AM +0200, Mike Hommey <[EMAIL PROTECTED]>
> wrote:
> > On Wed, Aug 30, 2006 at 10:04:17PM +0200, Alexander Sack <[EMAIL
> > PROTECTED]> wrote:
> > > Can you please upload them somewhere for now? When do you leave on
> > > vacation?
> >
> > I'll upload to gluck in ${HOME}/public_html, which means it will be on
> > people.debian.org/~glandium/. Expect it to be done some time tonight
> > (local time: GMT+2)
> >
> > I'm leaving on sunday, but will more than probably put me away from
> > saturday.
>
> Did you have time to work on seamonkey during the past two weeks ?
>
Sorry, still working on the final security patches. Its because my
work-capacity has been significantly reduced during the last few weeks by
severe private-life hazards.
Please understand that I have to fix some real life issues first.
I regret all this, but I did not choose this doom either. I would
understand if you would not go ahead lifting this package as I have to
admit that I will not be able to put much time into this any-time soon
(at least not till nov).
- Alexander
--
GPG messages preferred. | .''`. ** Debian GNU/Linux **
Alexander Sack| : :' : The universal
[EMAIL PROTECTED] | `. `' Operating System
http://www.asoftsite.org | `-http://www.debian.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
Hi Alex,
On Thu, Aug 31, 2006 at 07:47:01AM +0200, Mike Hommey <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 30, 2006 at 10:04:17PM +0200, Alexander Sack <[EMAIL PROTECTED]>
> wrote:
> > Can you please upload them somewhere for now? When do you leave on
> > vacation?
>
> I'll upload to gluck in ${HOME}/public_html, which means it will be on
> people.debian.org/~glandium/. Expect it to be done some time tonight
> (local time: GMT+2)
>
> I'm leaving on sunday, but will more than probably put me away from
> saturday.
Did you have time to work on seamonkey during the past two weeks ?
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Thu, Aug 31, 2006 at 07:47:01AM +0200, Mike Hommey <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 30, 2006 at 10:04:17PM +0200, Alexander Sack <[EMAIL PROTECTED]>
> wrote:
> > Can you please upload them somewhere for now? When do you leave on
> > vacation?
>
> I'll upload to gluck in ${HOME}/public_html, which means it will be on
> people.debian.org/~glandium/. Expect it to be done some time tonight
> (local time: GMT+2)
http://people.debian.org/~glandium/seamonkey-patches/
There is a README with comments on some patches, some issues with what
is currently in svn, and some thoughts for the packaging based on my
knowledge from firefox and xulrunner.
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Wed, Aug 30, 2006 at 10:04:17PM +0200, Alexander Sack <[EMAIL PROTECTED]>
wrote:
> Can you please upload them somewhere for now? When do you leave on
> vacation?
I'll upload to gluck in ${HOME}/public_html, which means it will be on
people.debian.org/~glandium/. Expect it to be done some time tonight
(local time: GMT+2)
I'm leaving on sunday, but will more than probably put me away from
saturday.
Cheers
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Wed, Aug 30, 2006 at 08:36:21PM +0200, Mike Hommey wrote: > On Wed, Aug 30, 2006 at 07:24:11AM +0200, Mike Hommey <[EMAIL PROTECTED]> > wrote: > > On Wed, Aug 30, 2006 at 12:46:36AM +0200, Alexander Sack <[EMAIL > > PROTECTED]> wrote: > > > On Sat, Aug 26, 2006 at 10:04:42PM +0200, Alexander Sack wrote: > > > > > > > > + maintenance place: > > > >+ svn used by jaldhar? > > > >+ complete checkin ... deflated > > > > > > > > > > As Jaldhar apparently has not much time, can we just "highjack" the > > > svn archive for now? Or should we move to a new place? > > > > As you wish. I'm almost done with the patches triage, I'll soon be able > > to upload a set of patch for seamonkey. > > I have a set of patches for seamonkey, and a set of changes I want to do > to the files that are currently in the collab-maint svn, according to > the patches. I also have 4 or 5 patches that need porting to seamonkey, > i.e. take the idea and do the same with the seamonkey specific build > system/code. (For example, there is a patch to correctly install > default.xpm which only applies to the xulrunner/ subdirectory of > xulrunner, but for which the issue is also in all others mozilla > products, but at a different place, with a possibly different fix) > > Please tell me where I should put all these before leaving, so that you > can do your homework when I'm not here ;) Can you please upload them somewhere for now? When do you leave on vacation? - Alexander -- GPG messages preferred. | .''`. ** Debian GNU/Linux ** Alexander Sack| : :' : The universal [EMAIL PROTECTED] | `. `' Operating System http://www.asoftsite.org | `-http://www.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Wed, Aug 30, 2006 at 12:09:25PM -0700, Alex Vincent <[EMAIL PROTECTED]> wrote: > Allow me to stick my two cents in, as the person currently > representing the SeaMonkey community unofficially. > > Wherever you post patches that alter the SeaMonkey code, I'd like to > at least read them and offer feedback. I'm obviously not in a > position to reject a patch, but if changes are being made, we should > see which ones can be ported back to mozilla.org as a matter of course > for forward-development of mozilla.org products. Firefox 2.0 (and > consequently SeaMonkey 1.1) are due to be released within a few > months, so now's a pretty good time to keep an eye out for last-minute > changes the Etch and Debian communities need. Don't worry, most of these patch are patches that are either taken from upstream bugzilla, been sent upstream, or soon to be sent. Most of them have been applied and thus tested for quite a long time on firefox, xulrunner and thunderbird in Debian. Some have been applied in mozilla.org trunk or even 1.8.1 in the best case, and some are still discussed. Don't worry ;) Cheers, Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
Allow me to stick my two cents in, as the person currently representing the SeaMonkey community unofficially. Wherever you post patches that alter the SeaMonkey code, I'd like to at least read them and offer feedback. I'm obviously not in a position to reject a patch, but if changes are being made, we should see which ones can be ported back to mozilla.org as a matter of course for forward-development of mozilla.org products. Firefox 2.0 (and consequently SeaMonkey 1.1) are due to be released within a few months, so now's a pretty good time to keep an eye out for last-minute changes the Etch and Debian communities need. -- "The first step in confirming there is a bug in someone else's work is confirming there are no bugs in your own." -- Alexander J. Vincent, June 30, 2001 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Wed, Aug 30, 2006 at 07:24:11AM +0200, Mike Hommey <[EMAIL PROTECTED]> wrote: > On Wed, Aug 30, 2006 at 12:46:36AM +0200, Alexander Sack <[EMAIL PROTECTED]> > wrote: > > On Sat, Aug 26, 2006 at 10:04:42PM +0200, Alexander Sack wrote: > > > > > > + maintenance place: > > >+ svn used by jaldhar? > > >+ complete checkin ... deflated > > > > > > > As Jaldhar apparently has not much time, can we just "highjack" the > > svn archive for now? Or should we move to a new place? > > As you wish. I'm almost done with the patches triage, I'll soon be able > to upload a set of patch for seamonkey. I have a set of patches for seamonkey, and a set of changes I want to do to the files that are currently in the collab-maint svn, according to the patches. I also have 4 or 5 patches that need porting to seamonkey, i.e. take the idea and do the same with the seamonkey specific build system/code. (For example, there is a patch to correctly install default.xpm which only applies to the xulrunner/ subdirectory of xulrunner, but for which the issue is also in all others mozilla products, but at a different place, with a possibly different fix) Please tell me where I should put all these before leaving, so that you can do your homework when I'm not here ;) Cheers Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Wed, Aug 30, 2006 at 12:46:36AM +0200, Alexander Sack <[EMAIL PROTECTED]> wrote: > On Sat, Aug 26, 2006 at 10:04:42PM +0200, Alexander Sack wrote: > > > > + maintenance place: > >+ svn used by jaldhar? > >+ complete checkin ... deflated > > > > As Jaldhar apparently has not much time, can we just "highjack" the > svn archive for now? Or should we move to a new place? As you wish. I'm almost done with the patches triage, I'll soon be able to upload a set of patch for seamonkey. Note that I'll be on vacation from saturday until sep 20th, so I won't be able to work a lot on seamonkey from then. Cheers, Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Sat, Aug 26, 2006 at 10:04:42PM +0200, Alexander Sack wrote: > > + maintenance place: >+ svn used by jaldhar? >+ complete checkin ... deflated > As Jaldhar apparently has not much time, can we just "highjack" the svn archive for now? Or should we move to a new place? - Alexander -- GPG messages preferred. | .''`. ** Debian GNU/Linux ** Alexander Sack| : :' : The universal [EMAIL PROTECTED] | `. `' Operating System http://www.asoftsite.org | `-http://www.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
Dropping bugs from CC ... On Sat, Aug 26, 2006 at 08:49:48PM +0200, Mike Hommey wrote: > On Sat, Aug 26, 2006 at 07:04:00PM +0200, Alexander Sack <[EMAIL PROTECTED]> > wrote: > > > So maybe we want to use seamonkey to see how good team maintainence > > for mozillas can work? Jaldhar would you agree to set > > [EMAIL PROTECTED] as the maintainer and > > list all that contribute explicitly as co-maintainer? > > > > Mike, what do you think about it? > > I think this is a great idea. It would be a preliminary step for me to > turn the xulrunner maintainance into a team one, which i'd like to see > happen, but not before I've clearly documented the whys and the hows of > the xulrunner packaging, which a team maintainance of seamonkey will > help me doing. I hope to be able to switch xulrunner to a team > maintainance soon after the etch release, then we'll be able to > experiment building the other mozilla applications on top of it, which, > by then, should almost be officially supported upstream. > OK, so lets discuss some basics like preferred package layout etc. Please comment and object: + package layout: upstream orig.tar.gz (no embedded tarball) ... but separate patches included (dpatch or something) + packages needed: + all current mozilla application equivalents + the -dev, but without libxxx packages. + a dbg package ... I want to see a dbg for all mozilla packages we have in etch. I will reupload a thunderbird build which I cancelled previously because I wanted security fixes to go into etch first. + maintenance place: + svn used by jaldhar? + complete checkin ... deflated + initial work-load: + mike reviews his patches clears up which ones are needed for archs, build system etc. + I move package to layout (orig.tar.gz + patches) as mentioned above (or whatever we decide to use) + anyone who has time does the work to tweak configure options and debhelper files to produce the packages mentioned above. We can either split this up in front or just first comes first serves? Anything important I missed? - Alexander -- GPG messages preferred. | .''`. ** Debian GNU/Linux ** Alexander Sack| : :' : The universal [EMAIL PROTECTED] | `. `' Operating System http://www.asoftsite.org | `-http://www.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Sat, Aug 26, 2006 at 10:04:42PM +0200, Alexander Sack <[EMAIL PROTECTED]> wrote: > OK, so lets discuss some basics like preferred package layout > etc. Please comment and object: > > + package layout: upstream orig.tar.gz (no embedded tarball) ... but > separate patches included (dpatch or something) dpatch is what I use for xulrunner. Tarball in tarball is something I hate, I'm happy to see you don't want that :) > + packages needed: >+ all current mozilla application equivalents + the -dev, but >without libxxx packages. Why would we need mozilla-dev packages at all ? >+ a dbg package ... I want to see a dbg for all mozilla packages we >have in etch. I will reupload a thunderbird build which I cancelled >previously because I wanted security fixes to go into etch >first. Agreed > + maintenance place: >+ svn used by jaldhar? Why not ? Though if we go for the complete checkin, we'd probably rather use a separate svn tree. Creating one for the team, if there isn't any yet, could be a good idea. >+ complete checkin ... deflated For both firefox and xulrunner, we are using a complete checkin, and it doesn't waste so much space, the repository is actually smaller than the checked out tree. Firefox has patches applied, but xulrunner uses dpatch, having the complete tree in svn helps me to generate the patches efficiently. > + initial work-load: >+ mike reviews his patches clears up which ones are needed for >archs, build system etc. I'll do that in the next few days. >+ I move package to layout (orig.tar.gz + patches) as mentioned >above (or whatever we decide to use) >+ anyone who has time does the work to tweak configure options and >debhelper files to produce the packages mentioned above. We can >either split this up in front or just first comes first serves? > > Anything important I missed? Sounds good :) Cheers Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Sat, Aug 26, 2006 at 07:04:00PM +0200, Alexander Sack <[EMAIL PROTECTED]> wrote: > On Sat, Aug 26, 2006 at 03:00:22PM +0200, Mike Hommey wrote: > > > > Well, in the current state, it still requires a lot of work to split the > > package in smaller parts like mozilla, and add transition packages. It > > would also be necessary to port most of the patches from xulrunner to > > make it work on all debian architectures. > > Hmm... so should we take this over to make things happen faster? What > do you mean by "port most of the patches from xulrunner" ... won't > they apply cleanly? Most should apply with no problem. But IIRC some kinda depend on the soname patch (the one to add sonames to the xulrunner libs), which is not a thing I want to see applied on seamonkey, firefox and others because they don't need to. But that work is not a very difficult one. Plus, I really need to do some triage in my patch-set, between build-system patches, code patches, debian-specific patches, etc. > So maybe we want to use seamonkey to see how good team maintainence > for mozillas can work? Jaldhar would you agree to set > [EMAIL PROTECTED] as the maintainer and > list all that contribute explicitly as co-maintainer? > > Mike, what do you think about it? I think this is a great idea. It would be a preliminary step for me to turn the xulrunner maintainance into a team one, which i'd like to see happen, but not before I've clearly documented the whys and the hows of the xulrunner packaging, which a team maintainance of seamonkey will help me doing. I hope to be able to switch xulrunner to a team maintainance soon after the etch release, then we'll be able to experiment building the other mozilla applications on top of it, which, by then, should almost be officially supported upstream. Cheers, Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Sat, Aug 26, 2006 at 02:08:05PM +0200, Alexander Sack <[EMAIL PROTECTED]> wrote: > > Here the svn url I just looked up in my inbox ... > > svn://svn.debian.org/svn/collab-maint/deb-maint/seamonkey > > Jaldhar ... whats the current state ... we are starting to run out of > time if we want to be safe to see this in etch? Well, in the current state, it still requires a lot of work to split the package in smaller parts like mozilla, and add transition packages. It would also be necessary to port most of the patches from xulrunner to make it work on all debian architectures. BTW, I need to do some sorting on my patches in xulrunner, that would be the occasion to prepare a list of patches to port to seamonkey. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351430: seamonkey for etch ?
On Sat, Aug 26, 2006 at 01:41:31PM +0200, Mike Hommey wrote: > Hi everyone, > > (Sorry for the duplicates people may receive) > > I'd like to know what the status is for these ITP on seamonkey. Is > actually someone working on it ? Are there any preliminary packages ? > > Being myself maintainer of xulrunner and co-maintainer of firefox, I can > give a hand if necessary. I think Alexander Sack, who has worked on mozilla > security updates wouldn't mind giving some advices too. > > If it appears that noone is working on that, I'll take over the ITPs and > upload a seamonkey package by the end of september (I think), but I first > need to know if someone is doing something or not, to avoid duplication of > efforts. > > Thanks for your attention. I already offered to take over ITP ... but Jaldhar is working on this ... he uploaded a seamonkey package a few weeks ago, which was rejected because of too many lintian errors. Jaldhar, can you please repost the svn url? I have lost it and cannot look up. - Alexander -- GPG messages preferred. | .''`. ** Debian GNU/Linux ** Alexander Sack| : :' : The universal [EMAIL PROTECTED] | `. `' Operating System http://www.asoftsite.org | `-http://www.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
