|
View:
New views
18 Messages
—
Rating Filter:
Alert me
|
|
|
Upcoming xulrunner transitionHi,
I'm taking advantage of the fact I have temporary ADSL synchronization to send this message. Unfortunately, I don't know how long it will last, nor when the service will be properly repaired. Anyways, As gcj-4.x have now transitioned, it's time for xulrunner transition. Unfortunately, without network access, I've not been able to do due work on the last 14 bugs on http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=xulrunner-transition;users=glandium@... Anyways, if we don't move fast enough and wait more, it's not going to happen at all, and that would probably be worse than waiting for every bit to be ready. So here is what I suggest: - I upload both iceweasel and xulrunner rc2 releases to unstable, after I'm ready to upload them, and after you tell me I can go on, if my network connection permits. - Rdeps currently in experimental shall be uploaded to unstable too (which is why I'm Bcc'ing their maintainers) - Packages with patches in the bug list above shall be NMUed (and here, I'm counting on my fellow DDs, since I probably won't be able to do this myself... uploading iceweasel and xulrunner is already going to take a long time, considering how much badwidth i'm left with) - The rest of the packages will have to be fixed (note that greasemonkey will need a new upstream to work with iceweasel 3, on top of needing some changes to rules and dependencies) What do you think? Cheers Mike -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transitionHi,
Mike Hommey wrote: > So here is what I suggest: > - I upload both iceweasel and xulrunner rc2 releases to unstable, after > I'm ready to upload them, and after you tell me I can go on, if my > network connection permits. > - Rdeps currently in experimental shall be uploaded to unstable too > (which is why I'm Bcc'ing their maintainers) Will do that hopefully next Tuesday for openoffice.org (2.4.1 release). > What do you think? So far OK. Regards, Rene -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transitionHi,
* Mike Hommey (mh@...) [080607 09:08]: > - I upload both iceweasel and xulrunner rc2 releases to unstable, after > I'm ready to upload them, and after you tell me I can go on, if my > network connection permits. There is this comment from Matthias (doko) about xulrunner which will help us with (not only) this transition: | - either make the -dev and the -common packages architecture | dependant. ftp space is not the only thing to consider when | making a decision about arch/indep packages. | | - or loosen the dependencies; I hardly doubt that the dependencies | need to be as strict as they currently are. To loosen those the | package maintainer needs to monitor the upstream changes. This | is more effort, but can be done, e.g. GCC packaging is done in | a way to reduce dependencies and to ease transitions. It's more | effort in package maintainance, but helps overall. I'd appreciate if you could do these changes - the first one shouldn't be too complicated. Provided this is done, uploading xulrunner to unstable is ok with the release team. (And I hope that your network issues are fixed fast, or you're in spite of them available in case any issues pop up - quite an unfortunate timing.) Thanks for waiting till now. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transitionOn Sat, Jun 07, 2008 at 10:15:50PM +0200, Andreas Barth wrote:
> Hi, > > * Mike Hommey (mh@...) [080607 09:08]: > > - I upload both iceweasel and xulrunner rc2 releases to unstable, after > > I'm ready to upload them, and after you tell me I can go on, if my > > network connection permits. > > There is this comment from Matthias (doko) about xulrunner which will > help us with (not only) this transition: > > | - either make the -dev and the -common packages architecture > | dependant. ftp space is not the only thing to consider when > | making a decision about arch/indep packages. > | > | - or loosen the dependencies; I hardly doubt that the dependencies > | need to be as strict as they currently are. To loosen those the > | package maintainer needs to monitor the upstream changes. This > | is more effort, but can be done, e.g. GCC packaging is done in > | a way to reduce dependencies and to ease transitions. It's more > | effort in package maintainance, but helps overall. > > I'd appreciate if you could do these changes - the first one shouldn't > be too complicated. Only 4 years ago, Steve McIntyre filed bugs on arch-dependent packages containing a large amount of arch-independent data. Have things changed in the last 4 years ? OTOH, the -dbg packages are already huge and one of them represents as much waste as all the binary-indep packages together. Anyways, the second option is out of question, I already spend too much time on xulrunner, and don't want to spend more. Now, if only I (or anyone else, actually) had time to fix #246992, which is the real problem... > Provided this is done, uploading xulrunner to unstable is ok with the > release team. (And I hope that your network issues are fixed fast, or > you're in spite of them available in case any issues pop up - quite an > unfortunate timing.) While I was fortunate to have a few hours of stable (though slow) network connectivity yesterday, it is now back to the broken state, with only sporadic access, a few seconds at a time. I can successfully send some mail through (with a while true; do exim -qff; done loop, but sometimes the SMTP session is cut right before the end, but after the message was actually sent, so the message is sent but still in my queue. Sorry to anyone receiving several messages from me), download small files (wget -t 0 is my friend), or, obviously, POP my mail ; but all that takes time. The timing could have been slightly better... I had time to prepare iceweasel 3.0~rc2-1 and upload it on gluck (you can find it on http://people.debian.org/~glandium/, signed and ready to upload, but it requires xulrunner 1.9 in unstable first...), but by the time I had xulrunner 1.9 ready, network was already down... It will be hard to upload any xulrunner release in the current state :-/ If my network stays in this state for the next few days and I can't upload, maybe I can send an interdiff between the last .diff.gz in experimental and the new .diff.gz so that someone could upload for me. Volunteers? I do hope things will get better before the freeze... Mike -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transitionOn Sun, Jun 08, 2008 at 08:44:07AM +0200, Mike Hommey wrote:
> The timing could have been slightly better... I had time to prepare > iceweasel 3.0~rc2-1 and upload it on gluck (you can find it on > http://people.debian.org/~glandium/, signed and ready to upload, but it > requires xulrunner 1.9 in unstable first...), but by the time I had > xulrunner 1.9 ready, network was already down... It will be hard to > upload any xulrunner release in the current state :-/ Okay, I just got lucky, and my network connection has been up for a few minutes now, which is much better than a few seconds. I'm currently uploading xulrunner 1.9~rc2-1 to my gluck space. The .dsc (signed), .diff.gz and .orig.tar.gz are already out there, so if I lose network now, there's already everything needed for someone else to do the upload. This doesn't implement the removal of arch-indep packages yet because I haven't had time to do that yet, and I'm already relieved to be able to upload the current state of affairs. If my network stays up long enough, I will upload a new version, though. Mike -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transitionOn Sun, Jun 08, 2008 at 09:42:53AM +0200, Mike Hommey wrote:
> On Sun, Jun 08, 2008 at 08:44:07AM +0200, Mike Hommey wrote: > > The timing could have been slightly better... I had time to prepare > > iceweasel 3.0~rc2-1 and upload it on gluck (you can find it on > > http://people.debian.org/~glandium/, signed and ready to upload, but it > > requires xulrunner 1.9 in unstable first...), but by the time I had > > xulrunner 1.9 ready, network was already down... It will be hard to > > upload any xulrunner release in the current state :-/ > > Okay, I just got lucky, and my network connection has been up for a few > minutes now, which is much better than a few seconds. I'm currently > uploading xulrunner 1.9~rc2-1 to my gluck space. The .dsc (signed), > .diff.gz and .orig.tar.gz are already out there, so if I lose network > now, there's already everything needed for someone else to do the upload. > This doesn't implement the removal of arch-indep packages yet because I > haven't had time to do that yet, and I'm already relieved to be able to > upload the current state of affairs. If my network stays up long enough, > I will upload a new version, though. Damn, and now I realize what I'm uploading is targetted at experimental... Mike -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transition* Mike Hommey (mh@...) [080608 08:55]:
> On Sat, Jun 07, 2008 at 10:15:50PM +0200, Andreas Barth wrote: > > * Mike Hommey (mh@...) [080607 09:08]: > > > - I upload both iceweasel and xulrunner rc2 releases to unstable, after > > > I'm ready to upload them, and after you tell me I can go on, if my > > > network connection permits. > > > > There is this comment from Matthias (doko) about xulrunner which will > > help us with (not only) this transition: > > > > | - either make the -dev and the -common packages architecture > > | dependant. ftp space is not the only thing to consider when > > | making a decision about arch/indep packages. > > | > > | - or loosen the dependencies; I hardly doubt that the dependencies > > | need to be as strict as they currently are. To loosen those the > > | package maintainer needs to monitor the upstream changes. This > > | is more effort, but can be done, e.g. GCC packaging is done in > > | a way to reduce dependencies and to ease transitions. It's more > > | effort in package maintainance, but helps overall. > > > > I'd appreciate if you could do these changes - the first one shouldn't > > be too complicated. > > Only 4 years ago, Steve McIntyre filed bugs on arch-dependent packages > containing a large amount of arch-independent data. Have things changed > in the last 4 years ? I would consider the xulrunner-packages to be the exception to the rule. Normally, using arch=all-packages is the right thing to do. However, in case of xulrunner, which is a build-dependency of many central packages (which means if they fail to build they can block quite many other packages), I think that archive space (we speak about 11*4 MB = 44 MB) counts less than saving time of the involved teams. > Anyways, the second option is out of question, I already spend too much > time on xulrunner, and don't want to spend more. I can understand that. > Now, if only I (or anyone else, actually) had time to fix #246992, which > is the real problem... That isn't so trivial - otherwise, it would've been done already. But yes, that should be done some day. Until that happens however, we should try to reduce impact in cases it hurts us bad. > If my network stays in this state for the next few days and I can't > upload, maybe I can send an interdiff between the last .diff.gz in > experimental and the new .diff.gz so that someone could upload for me. > Volunteers? That'd work. But please tell me what all needs to be uploaded, and in which order (and sign the interdiff of course :) ). As alternative, you can send me a signed dsc + diff, and I can do the builds and uploads (so basically you have a source-only "upload"). Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transitionOn Sun, Jun 08, 2008 at 10:09:05AM +0200, Andreas Barth wrote:
> > If my network stays in this state for the next few days and I can't > > upload, maybe I can send an interdiff between the last .diff.gz in > > experimental and the new .diff.gz so that someone could upload for me. > > Volunteers? > > That'd work. But please tell me what all needs to be uploaded, and in > which order (and sign the interdiff of course :) ). As alternative, you > can send me a signed dsc + diff, and I can do the builds and uploads (so > basically you have a source-only "upload"). Actually, I've been fortunate enough to have some networking back, and I'm currently uploading a whole new package (without arch indep packages except the java interfaces) to gluck (http://people.debian.org/~glandium/). Well I was fortunate until a few minutes ago, when it broke again, but I had enough networking to upload almost everything, except the -dbg and python-xpcom packages. Anyways, the .dsc, .orig.tar.gz and .diff.gz are out there, ready to be built and uploaded. Please feel free to do so when you feel is the right time (I guess waiting for openoffice wouldn't be a bad idea, for instance). I'll drop a note if I get lucky again and am able to finish transferring the remaining debs. I also have, thanks to Lucas Nussbaum, a way out of my misery, involving some tunnelling and access to a wireless network with a very bad link quality, so I should be able to do some followup. Mike -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transition* Mike Hommey (mh@...) [080608 15:46]:
> On Sun, Jun 08, 2008 at 10:09:05AM +0200, Andreas Barth wrote: > > > If my network stays in this state for the next few days and I can't > > > upload, maybe I can send an interdiff between the last .diff.gz in > > > experimental and the new .diff.gz so that someone could upload for me. > > > Volunteers? > > > > That'd work. But please tell me what all needs to be uploaded, and in > > which order (and sign the interdiff of course :) ). As alternative, you > > can send me a signed dsc + diff, and I can do the builds and uploads (so > > basically you have a source-only "upload"). > > Actually, I've been fortunate enough to have some networking back, > and I'm currently uploading a whole new package (without arch indep > packages except the java interfaces) to gluck > (http://people.debian.org/~glandium/). Well I was fortunate until a few > minutes ago, when it broke again, but I had enough networking to upload > almost everything, except the -dbg and python-xpcom packages. That's enough, thank you. One question (just to be sure): We speak about /home/glandium/public_html/xulrunner_1.9~rc2-1_amd64.changes ? Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transitionOn Sun, Jun 08, 2008 at 04:07:37PM +0200, Andreas Barth wrote:
> * Mike Hommey (mh@...) [080608 15:46]: > > On Sun, Jun 08, 2008 at 10:09:05AM +0200, Andreas Barth wrote: > > > > If my network stays in this state for the next few days and I can't > > > > upload, maybe I can send an interdiff between the last .diff.gz in > > > > experimental and the new .diff.gz so that someone could upload for me. > > > > Volunteers? > > > > > > That'd work. But please tell me what all needs to be uploaded, and in > > > which order (and sign the interdiff of course :) ). As alternative, you > > > can send me a signed dsc + diff, and I can do the builds and uploads (so > > > basically you have a source-only "upload"). > > > > Actually, I've been fortunate enough to have some networking back, > > and I'm currently uploading a whole new package (without arch indep > > packages except the java interfaces) to gluck > > (http://people.debian.org/~glandium/). Well I was fortunate until a few > > minutes ago, when it broke again, but I had enough networking to upload > > almost everything, except the -dbg and python-xpcom packages. > > That's enough, thank you. > > One question (just to be sure): We speak about > /home/glandium/public_html/xulrunner_1.9~rc2-1_amd64.changes ? Yes, and actually, in the meanwhile, network is back again, and I could finish the upload. Which means the built packages there are all there and ok (I rsync'ed again, just to be sure) Cheers Mike -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transition* Mike Hommey (mh@...) [080608 15:46]:
> Anyways, the .dsc, .orig.tar.gz and .diff.gz are out there, ready to be > built and uploaded. Please feel free to do so when you feel is the right > time (I guess waiting for openoffice wouldn't be a bad idea, for > instance). Actually, we don't think that we should wait, so it is uploaded now. Thanks for your help so far despite the bad network connectivity. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transition* Mike Hommey (mh@...) [080608 16:18]:
> On Sun, Jun 08, 2008 at 04:07:37PM +0200, Andreas Barth wrote: > > * Mike Hommey (mh@...) [080608 15:46]: > > > On Sun, Jun 08, 2008 at 10:09:05AM +0200, Andreas Barth wrote: > > > > > If my network stays in this state for the next few days and I can't > > > > > upload, maybe I can send an interdiff between the last .diff.gz in > > > > > experimental and the new .diff.gz so that someone could upload for me. > > > > > Volunteers? > > > > > > > > That'd work. But please tell me what all needs to be uploaded, and in > > > > which order (and sign the interdiff of course :) ). As alternative, you > > > > can send me a signed dsc + diff, and I can do the builds and uploads (so > > > > basically you have a source-only "upload"). > > > > > > Actually, I've been fortunate enough to have some networking back, > > > and I'm currently uploading a whole new package (without arch indep > > > packages except the java interfaces) to gluck > > > (http://people.debian.org/~glandium/). Well I was fortunate until a few > > > minutes ago, when it broke again, but I had enough networking to upload > > > almost everything, except the -dbg and python-xpcom packages. > > > > That's enough, thank you. > > > > One question (just to be sure): We speak about > > /home/glandium/public_html/xulrunner_1.9~rc2-1_amd64.changes ? > > Yes, and actually, in the meanwhile, network is back again, and I could > finish the upload. Which means the built packages there are all there > and ok (I rsync'ed again, just to be sure) Ok. Unfortunatly xulrunner seems to FTBFS on all arches due to missing javaxpcom.jar (some difference between -B and -b I assume), see http://bugs.debian.org/485284 If we need another upload anyways, can we do an libxul-dev for the moment that just points to xulrunner-dev, so that we can get away with a couple of binNMUs in some cases? Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transitionOn Sun, Jun 08, 2008 at 10:36:40PM +0200, Andreas Barth wrote:
> Ok. Unfortunatly xulrunner seems to FTBFS on all arches due to missing > javaxpcom.jar (some difference between -B and -b I assume), see > http://bugs.debian.org/485284 Sorry :-/ > If we need another upload anyways, can we do an libxul-dev for the > moment that just points to xulrunner-dev, so that we can get away with a > couple of binNMUs in some cases? Unfortunately, except for libmozdev, binNMU are far from being enough. See http://lists.debian.org/debian-release/2008/05/msg00009.html BTW, once I upload 1.9~rc2-2, can you trigger binNMUs on bfilter, freej, edbrowse, gxine, libjavascript-perl, and mediatomb ? Thanks Mike -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transition* Mike Hommey (mh@...) [080609 07:41]:
> BTW, once I upload 1.9~rc2-2, can you trigger binNMUs on bfilter, freej, > edbrowse, gxine, libjavascript-perl, and mediatomb ? Yes. And everbody: Please feel ready to upload any dependend packages already now - but of course you need to build them on amd64 until we have the new version in the archive. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transitionOn Mon, Jun 09, 2008 at 10:26:33AM +0200, Andreas Barth <aba@...> wrote:
> * Mike Hommey (mh@...) [080609 07:41]: > > BTW, once I upload 1.9~rc2-2, can you trigger binNMUs on bfilter, freej, > > edbrowse, gxine, libjavascript-perl, and mediatomb ? > > Yes. And everbody: Please feel ready to upload any dependend packages > already now - but of course you need to build them on amd64 until we > have the new version in the archive. Which I just uploaded to ftp-master. Mike -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transitionOn Sun, Jun 08, 2008 at 08:44:07AM +0200, Mike Hommey wrote:
> > If my network stays in this state for the next few days and I can't > upload, maybe I can send an interdiff between the last .diff.gz in > experimental and the new .diff.gz so that someone could upload for me. > Volunteers? > In future, feel free to ping me if you have network issues. I had similar problems in the past and know how it feels to regularly get stuck uploads. At best I could get those bits from git (prod!), but if you have diff.gz and so on i can do that too. - Alexander -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transition* Mike Hommey (mh@...) [080607 09:08]:
> I'm taking advantage of the fact I have temporary ADSL synchronization > to send this message. Unfortunately, I don't know how long it will last, > nor when the service will be properly repaired. > > Anyways, As gcj-4.x have now transitioned, it's time for xulrunner > transition. Unfortunately, without network access, I've not been able to > do due work on the last 14 bugs on > http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=xulrunner-transition;users=glandium@... Can you continue NMUing these packages? It would be great to have all the packages at least on i386/amd64 soon, so that we can work on fixing the missing architectures. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to debian-release-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: Upcoming xulrunner transition* Andreas Barth (aba@...) [080620 08:39]:
> [...] Status update: The transition is now mostly ready to be done, except the RC bugs on xulrunner, iceweasel and epiphany-browser. Also, a few RC bugs on some leaf packages haven't been filed yet (e.g. zekr), but now all packages that need bugs have them filed. So, please: Don't upload packages that interfere with xulrunner except for RC bug fixes now, as we want to have all of them transitioned rather soon. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to |