Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Thu, Apr 29, 2010 at 11:17:59PM +0200, Moritz Muehlenhoff wrote: On Mon, Apr 26, 2010 at 01:02:09PM +0200, Alexander Sack wrote: Yeah, in any case we might want to get this in experimental/unstable so we get a feeling how this can be maintained. Also having this beast NEWed is probably a good start ;). It's in Debian unstable since half a year: http://packages.qa.debian.org/libv/libv8.html and yes, for now chromium-browser will use its libv8 and i dont have plans for uploading the standalone package until that has stabilized. Is the Chrome version of libv8 forked from the version of v8 in the archive? no, but libv8 is getting bumped too quickly to use the system lib. - Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Mon, Apr 26, 2010 at 01:02:09PM +0200, Alexander Sack wrote: Yeah, in any case we might want to get this in experimental/unstable so we get a feeling how this can be maintained. Also having this beast NEWed is probably a good start ;). It's in Debian unstable since half a year: http://packages.qa.debian.org/libv/libv8.html and yes, for now chromium-browser will use its libv8 and i dont have plans for uploading the standalone package until that has stabilized. Is the Chrome version of libv8 forked from the version of v8 in the archive? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Sun, Apr 25, 2010 at 10:41:50PM +0200, Moritz Muehlenhoff wrote: On Thu, Apr 22, 2010 at 07:07:01PM +0200, Giuseppe Iuculano wrote: Il 22/04/2010 12:25, Stefano Zacchiroli ha scritto: Regarding security issues, I duly notice that Giuseppe is a full member of the Debian security team, so I believe we should trust his judgement on that. webkit related security issues are real and I'm well placed to know about it. I would like to hear Giuseppe about his concerns wrt this point. Sure, I just meant to highlight that he's probably more qualified than other people (surely more than me for instance) to judge on this. I do hope he has already thought about it :), but it would indeed be nice if he can share his opinions here. We are already tracking[1] chromium security issues, this is another webkit fork and it is a real pain; but given the fact that now we have three members in the webkit security groups (Fathi is one of them), from the Security team's (CCed) point of view there is no objections. Alexander Sack wrote: One example: If you look at the release channels, you will notice that there are two releases a week in average or something. Not real releases,tags or anything like that. The problem here is that chromium uses a continuous rollout and backout approach, which is fine on its own, but when it comes to reflecting this in a distro you easily become trapped to either keep up with their update frequency through the security channel :-P (e.g. going through security twice a week ;)) ... or somehow figuring how to bake stable releases from a continuous head in a way that you can release regression free security updates as those are announced. I am not saying there is no way to do that, just that its tough and we have to learn a lot before we can consider putting chromium in a stable release for debian. After a quick look to their release blog, I noted a lot of announcement for the dev tree, but not for the stable tree. Anyway could you explain your plans for chromium in Debian please? When do you intend to upload it in unstable or experimental? BTW, yesterday I uploaded gyp. FWIW, I concur with Alexander Sack. We should not yet include Chromium in Squeeze. Let's give it some time to settle down and observe if it's actually maintainable. The issues raised by both Alexander and Tom Callaway of Fedora seem very credible to me. If Chromium in Squeeze+1 can be build with the system copy of webkit, that's an added bonus. Likewise, we shouldn't include libv8 yet (or exclude it from security support). Yeah, in any case we might want to get this in experimental/unstable so we get a feeling how this can be maintained. Also having this beast NEWed is probably a good start ;). and yes, for now chromium-browser will use its libv8 and i dont have plans for uploading the standalone package until that has stabilized. - Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
Hi, Il 23/04/2010 22:55, Stefano Zacchiroli ha scritto: That's great news guys, I'm really looking forward for chromium browser in unstable ... and if you need a beta tester, ping me :-) Preliminary i386/amd64 Debian packages can be found here: http://people.debian.org/~iuculano/chromium/ Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Mon, Apr 26, 2010 at 03:14:43PM +0200, Giuseppe Iuculano wrote:
Preliminary i386/amd64 Debian packages can be found here:
http://people.debian.org/~iuculano/chromium/
Wonderful!, thanks.
I'll given them a try and report any problem.
(You might want to sign the .dsc though, so that people can have a trust
path to the .deb-s.)
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
Il 26/04/2010 15:58, Stefano Zacchiroli ha scritto: (You might want to sign the .dsc though, so that people can have a trust path to the .deb-s.) Signed, thanks! Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Thu, Apr 22, 2010 at 07:07:01PM +0200, Giuseppe Iuculano wrote: Il 22/04/2010 12:25, Stefano Zacchiroli ha scritto: Regarding security issues, I duly notice that Giuseppe is a full member of the Debian security team, so I believe we should trust his judgement on that. webkit related security issues are real and I'm well placed to know about it. I would like to hear Giuseppe about his concerns wrt this point. Sure, I just meant to highlight that he's probably more qualified than other people (surely more than me for instance) to judge on this. I do hope he has already thought about it :), but it would indeed be nice if he can share his opinions here. We are already tracking[1] chromium security issues, this is another webkit fork and it is a real pain; but given the fact that now we have three members in the webkit security groups (Fathi is one of them), from the Security team's (CCed) point of view there is no objections. Alexander Sack wrote: One example: If you look at the release channels, you will notice that there are two releases a week in average or something. Not real releases,tags or anything like that. The problem here is that chromium uses a continuous rollout and backout approach, which is fine on its own, but when it comes to reflecting this in a distro you easily become trapped to either keep up with their update frequency through the security channel :-P (e.g. going through security twice a week ;)) ... or somehow figuring how to bake stable releases from a continuous head in a way that you can release regression free security updates as those are announced. I am not saying there is no way to do that, just that its tough and we have to learn a lot before we can consider putting chromium in a stable release for debian. After a quick look to their release blog, I noted a lot of announcement for the dev tree, but not for the stable tree. Anyway could you explain your plans for chromium in Debian please? When do you intend to upload it in unstable or experimental? BTW, yesterday I uploaded gyp. FWIW, I concur with Alexander Sack. We should not yet include Chromium in Squeeze. Let's give it some time to settle down and observe if it's actually maintainable. The issues raised by both Alexander and Tom Callaway of Fedora seem very credible to me. If Chromium in Squeeze+1 can be build with the system copy of webkit, that's an added bonus. Likewise, we shouldn't include libv8 yet (or exclude it from security support). Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
Hello Thanks for adding gyp into sid so far. Many Debian users prefers to use Google Chrome repository. I'm not sure many Debian users prefer to use non-debian repositories. For me and our users it's definitely not the case, we prefer to use Debian repositories exclusively, and our own where we add other packages that are not available in Debian ourselves. Simply because we rely and need Debian security updates in some managed (monitored with hobbit, and manually checked if all went fine) for our well over a hundred workstations. Having this in Debian, and stable would be a big benefit for any administrator that runs Debian for more than his own workstation. Even if a security fix is not easily to be done, it's easier to just remove a package than adding one and watching the extra repository work as it should, temporarily (until a proper fix can be done). Yours, Gurkan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Thu, Apr 22, 2010 at 11:03:47PM +0300, Fathi Boudra wrote: We are already tracking[1] chromium security issues, this is another webkit fork and it is a real pain; but given the fact that now we have three members in the webkit security groups (Fathi is one of them), from the Security team's (CCed) point of view there is no objections. good to know. BTW, yesterday I uploaded gyp. Thanks and already accepted (interesting to see some packages can go fast ;) I guess nothing prevent to upload a package to experimental now. OK, I will make this happen over weekend. Will add Guiseppe as an Uploader ... please contribute directly to our branches in launchpad from here on. - Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Fri, Apr 23, 2010 at 12:49:29PM +0200, Gürkan Sengün wrote: Hello Thanks for adding gyp into sid so far. Many Debian users prefers to use Google Chrome repository. I'm not sure many Debian users prefer to use non-debian repositories. For me and our users it's definitely not the case, we prefer to use Debian repositories exclusively, and our own where we add other packages that are not available in Debian ourselves. Simply because we rely and need Debian security updates in some managed (monitored with hobbit, and manually checked if all went fine) for our well over a hundred workstations. I agree, that we want chromium in archive ... having external solutions only is not in the spirit of debian imo. - Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Fri, Apr 23, 2010 at 01:42:35PM +0200, Alexander Sack wrote:
BTW, yesterday I uploaded gyp.
Thanks and already accepted (interesting to see some packages can go fast ;)
I guess nothing prevent to upload a package to experimental now.
OK, I will make this happen over weekend. Will add Guiseppe as an Uploader ...
please contribute directly to our branches in launchpad from here on.
That's great news guys, I'm really looking forward for chromium browser
in unstable ... and if you need a beta tester, ping me :-)
Thanks a lot and keep up the good work.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
Hi, On Thu, Apr 22, 2010 at 4:28 AM, Alexander Sack wrote: The problem is that chromium browser cannot be maintained in a debian stable relase as it is. If you think different talk to me on IRC. Let's wait how bad it blows up once ubuntu lucid enters stable release mode. Just for the record, I don't want to stand in anyones way; however, the package is as ready as it can be; the problem is really on upstream release process. Note: I don't want to take over this ITP. As a user, I'm expecting to be able to install chromium on my favorite distribution. I don't understand why we don't have this package available on experimental or unstable (hint: you can block migration by opening an RC bug). The upstream release process and how you want to deal with it is a completely different point. If you think the current state prevent to ship chromium with squeeze, it's fine. Cheers, Fathi an advanced user ;) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Thu, Apr 22, 2010 at 03:12:56AM +0200, Alexander Sack wrote:
Is there a specific reason why you (Chromium team) uploaded
chromium-browser in Ubuntu two months ago and not yet in Debian?
I don't received any answer, so I'm going to take over this ITP in order
to get chromium-browser in time for squeeze.
Hi Giuseppe, many thanks for your offer, personally I'd like you to go
ahead with your packaging work on chromium-browser to at least have the
*possibility* of getting the package in squeeze. That means having it in
unstable first, then we'll use the usual rules for transition to testing
of all other packages.
I requested an alioth group, feel free to join it when it will be
accepted.
The problem is that chromium browser cannot be maintained in a debian
stable relase as it is. If you think different talk to me on IRC.
It's a bit of a pity that this argument of yours was not in the bug log
of the ITPs of chromium, or else I've missed it blatantly (in that case
I apologize in advance). The only counter argument I've found thus far
to upload was a licensing problem, which seems to be solved now.
Regarding security issues, I duly notice that Giuseppe is a full member
of the Debian security team, so I believe we should trust his judgement
on that.
All in all, it would be an incredible pity not to have chromium-browser
in Debian and probably a good argument for a lot of desktop users to use
another Debian-based distribution (say, Ubuntu). I don't think we should
block the packaging of chromium lightly; if there are clear reasons to
do so they should be clearly stated, and well communicated.
No matter what, we've clear processes for this kind of issues and I
think we should use them rather then simply not uploading the package
and stopping other developers motivated in doing that, by fiddling with
the owner of this ITP.
If you ask me, I'd like Giuseppe to take back ownership of this bug
report and go ahead with the packaging work.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Thu, Apr 22, 2010 at 12:51 PM, Stefano Zacchiroli wrote: Hi Giuseppe, many thanks for your offer, personally I'd like you to go ahead with your packaging work on chromium-browser to at least have the *possibility* of getting the package in squeeze. That means having it in unstable first, then we'll use the usual rules for transition to testing of all other packages. or experimental. Regarding security issues, I duly notice that Giuseppe is a full member of the Debian security team, so I believe we should trust his judgement on that. webkit related security issues are real and I'm well placed to know about it. I would like to hear Giuseppe about his concerns wrt this point. All in all, it would be an incredible pity not to have chromium-browser in Debian and probably a good argument for a lot of desktop users to use another Debian-based distribution (say, Ubuntu). Many Debian users prefers to use Google Chrome repository. No matter what, we've clear processes for this kind of issues and I think we should use them rather then simply not uploading the package and stopping other developers motivated in doing that, by fiddling with the owner of this ITP. If you ask me, I'd like Giuseppe to take back ownership of this bug report and go ahead with the packaging work. IMHO, common sense is preferred here. I don't see the problem for Giuseppe to team up with Alexander (and Fabien Tassin) and finally push a package in experimental. 1st step: upload gyp to Debian ! Cheers, Fathi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
webkit related security issues are real and I'm well placed to know about it. oups, I mean chromium here :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Thu, Apr 22, 2010 at 01:10:12PM +0300, Fathi Boudra wrote:
*possibility* of getting the package in squeeze. That means having it in
unstable first, then we'll use the usual rules for transition to testing
of all other packages.
or experimental.
Yup, exactly, with the added benefit that in the mean time we'll get NEW
review.
Regarding security issues, I duly notice that Giuseppe is a full member
of the Debian security team, so I believe we should trust his judgement
on that.
webkit related security issues are real and I'm well placed to know about it.
I would like to hear Giuseppe about his concerns wrt this point.
Sure, I just meant to highlight that he's probably more qualified than
other people (surely more than me for instance) to judge on this. I do
hope he has already thought about it :), but it would indeed be nice if
he can share his opinions here.
IMHO, common sense is preferred here.
I don't see the problem for Giuseppe to team up with Alexander (and
Fabien Tassin) and finally push a package in experimental.
Sure, and thanks for the hook to highlight what I forgot to mention: the
offer Giuseppe has already advanced of collaborating on the packaging on
alioth is surely the best possible outcome of all this.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
Il 22/04/2010 12:25, Stefano Zacchiroli ha scritto: Regarding security issues, I duly notice that Giuseppe is a full member of the Debian security team, so I believe we should trust his judgement on that. webkit related security issues are real and I'm well placed to know about it. I would like to hear Giuseppe about his concerns wrt this point. Sure, I just meant to highlight that he's probably more qualified than other people (surely more than me for instance) to judge on this. I do hope he has already thought about it :), but it would indeed be nice if he can share his opinions here. We are already tracking[1] chromium security issues, this is another webkit fork and it is a real pain; but given the fact that now we have three members in the webkit security groups (Fathi is one of them), from the Security team's (CCed) point of view there is no objections. Alexander Sack wrote: One example: If you look at the release channels, you will notice that there are two releases a week in average or something. Not real releases,tags or anything like that. The problem here is that chromium uses a continuous rollout and backout approach, which is fine on its own, but when it comes to reflecting this in a distro you easily become trapped to either keep up with their update frequency through the security channel :-P (e.g. going through security twice a week ;)) ... or somehow figuring how to bake stable releases from a continuous head in a way that you can release regression free security updates as those are announced. I am not saying there is no way to do that, just that its tough and we have to learn a lot before we can consider putting chromium in a stable release for debian. After a quick look to their release blog, I noted a lot of announcement for the dev tree, but not for the stable tree. Anyway could you explain your plans for chromium in Debian please? When do you intend to upload it in unstable or experimental? BTW, yesterday I uploaded gyp. [1]http://security-tracker.debian.org/tracker/status/itp Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
We are already tracking[1] chromium security issues, this is another webkit fork and it is a real pain; but given the fact that now we have three members in the webkit security groups (Fathi is one of them), from the Security team's (CCed) point of view there is no objections. good to know. BTW, yesterday I uploaded gyp. Thanks and already accepted (interesting to see some packages can go fast ;) I guess nothing prevent to upload a package to experimental now. Cheers, Fathi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
owner 520324 ! thanks Il 27/03/2010 17:14, Giuseppe Iuculano ha scritto: Hi Alexander, Il 26/03/2010 12:24, Alexander Sack ha scritto: Just pull and build the ubuntu package. Is there a specific reason why you (Chromium team) uploaded chromium-browser in Ubuntu two months ago and not yet in Debian? Cheers, Giuseppe. I don't received any answer, so I'm going to take over this ITP in order to get chromium-browser in time for squeeze. I requested an alioth group, feel free to join it when it will be accepted. Cheers, Giuseppe signature.asc Description: OpenPGP digital signature
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
owner 520324 a...@debian.org thanks On Wed, Apr 21, 2010 at 10:14:59PM +0200, Giuseppe Iuculano wrote: owner 520324 ! thanks Il 27/03/2010 17:14, Giuseppe Iuculano ha scritto: Hi Alexander, Il 26/03/2010 12:24, Alexander Sack ha scritto: Just pull and build the ubuntu package. Is there a specific reason why you (Chromium team) uploaded chromium-browser in Ubuntu two months ago and not yet in Debian? Cheers, Giuseppe. I don't received any answer, so I'm going to take over this ITP in order to get chromium-browser in time for squeeze. I requested an alioth group, feel free to join it when it will be accepted. Dude, The problem is that chromium browser cannot be maintained in a debian stable relase as it is. If you think different talk to me on IRC. Let's wait how bad it blows up once ubuntu lucid enters stable release mode. - Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Thu, Apr 22, 2010 at 03:12:56AM +0200, Alexander Sack wrote: On Wed, Apr 21, 2010 at 10:14:59PM +0200, Giuseppe Iuculano wrote: I don't received any answer, so I'm going to take over this ITP in order to get chromium-browser in time for squeeze. I requested an alioth group, feel free to join it when it will be accepted. Dude, The problem is that chromium browser cannot be maintained in a debian stable relase as it is. If you think different talk to me on IRC. Let's wait how bad it blows up once ubuntu lucid enters stable release mode. Just for the record, I don't want to stand in anyones way; however, the package is as ready as it can be; the problem is really on upstream release process. It's completely unclear when to release and what to release and that is what we are trying out in ubuntu lucid. Most likely we will get out of this that we need to work with upstream on something better. One example: If you look at the release channels, you will notice that there are two releases a week in average or something. Not real releases,tags or anything like that. The problem here is that chromium uses a continuous rollout and backout approach, which is fine on its own, but when it comes to reflecting this in a distro you easily become trapped to either keep up with their update frequency through the security channel :-P (e.g. going through security twice a week ;)) ... or somehow figuring how to bake stable releases from a continuous head in a way that you can release regression free security updates as those are announced. I am not saying there is no way to do that, just that its tough and we have to learn a lot before we can consider putting chromium in a stable release for debian. - Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Sat, Mar 27, 2010 at 05:38:52PM +0100, Fathi Boudra wrote: Just pull and build the ubuntu package. Thanks. It seems Ubuntu package doesn't build as is. gyp doesn't exist in Debian. timeout is provided by coreutils package. right ... gyp needs to get in too!! FTA probably could help getting that in. - Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
Hi Alexander, Il 26/03/2010 12:24, Alexander Sack ha scritto: Just pull and build the ubuntu package. Is there a specific reason why you (Chromium team) uploaded chromium-browser in Ubuntu two months ago and not yet in Debian? Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
Just pull and build the ubuntu package. Thanks. It seems Ubuntu package doesn't build as is. gyp doesn't exist in Debian. timeout is provided by coreutils package. Cheers, Fathi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Sat, Mar 27, 2010 at 5:14 PM, Giuseppe Iuculano iucul...@debian.org wrote: Is there a specific reason why you (Chromium team) uploaded chromium-browser in Ubuntu two months ago and not yet in Debian? just a guess: missing b-d in Debian. i.e. gyp -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
On Wed, Mar 24, 2010 at 10:15:56AM +0100, Fathi Boudra wrote: Hi, Could you give us en ETA of the ITP ? Can we have unofficial packages while waiting for the official upload ? seconded. Otherwise, you could give us some quick steps to build our own packages :) Just pull and build the ubuntu package. - Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
Hi, Could you give us en ETA of the ITP ? Can we have unofficial packages while waiting for the official upload ? seconded. Otherwise, you could give us some quick steps to build our own packages :) Cheers, Fathi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
i hope it comes into squeeze, looking forward for this.
/me too
is there anything we can do to help ?
Cheers,
--
Emmanuel Bouthenot
mail: kol...@{openics,debian}.orggpg: 1024D/0x414EC36E
xmpp: kol...@im.openics.org irc: kol...@{freenode,oftc}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
thanks for the status updates and working on this, i hope it comes into squeeze, looking forward for this. guerkan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520324: ITP: chromium-browser -- A web browser developed by Google based on the WebKit engine
Hi Alexander, I've already packaged libv8-0 (latest 1.3.11 from upstream committed some days ago to trunk), the package is building fine, lintian clean and it is waiting for a sponsor (ITP 497701). Most of the packaging comes from ubuntu but I had to adapt it for Debian; it is in collab-maint so if you want to partecipate it would be great. Chromium (chromium-browser) needs libv8-0 to work so if we can have a single team to manage this it could be great; if we could have people from ubuntu and Debian to commit to a single repository it would be even better. What do you think? Cheers Antonio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
