Bug#702013: unblock: chromium-browser/25.0.1364.97-1
On Mon, Mar 04, 2013 at 07:49:46PM +0100, Julien Cristau wrote: On Mon, Mar 4, 2013 at 19:11:43 +0100, Giuseppe Iuculano wrote: On 02/03/2013 22:57, Michael Gilbert wrote: The arm builds have been nothing but trouble so far, and without upstream interest they are likely to continue to break with most upstream releases. My vote is removal, but its really Guiseppe's call. I totally agree, we should drop arm support. Do I need to upload another revision without the arm arch in debian/control ? Yes please. Any moves on this? Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits signature.asc Description: Digital signature
Bug#702013: unblock: chromium-browser/25.0.1364.97-1
On Sun, 2013-03-17 at 14:22 +, Jonathan Wiltshire wrote: On Mon, Mar 04, 2013 at 07:49:46PM +0100, Julien Cristau wrote: On Mon, Mar 4, 2013 at 19:11:43 +0100, Giuseppe Iuculano wrote: I totally agree, we should drop arm support. Do I need to upload another revision without the arm arch in debian/control ? Yes please. Any moves on this? chromium-browser (25.0.1364.152-1) unstable; urgency=high . * [8761d73] Remove armel and armhf. We cannot support them in wheezy That version already migrated. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702013: unblock: chromium-browser/25.0.1364.97-1
On 02/03/2013 22:57, Michael Gilbert wrote: The arm builds have been nothing but trouble so far, and without upstream interest they are likely to continue to break with most upstream releases. My vote is removal, but its really Guiseppe's call. I totally agree, we should drop arm support. Do I need to upload another revision without the arm arch in debian/control ? Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Bug#702013: unblock: chromium-browser/25.0.1364.97-1
On Mon, Mar 4, 2013 at 19:11:43 +0100, Giuseppe Iuculano wrote: On 02/03/2013 22:57, Michael Gilbert wrote: The arm builds have been nothing but trouble so far, and without upstream interest they are likely to continue to break with most upstream releases. My vote is removal, but its really Guiseppe's call. I totally agree, we should drop arm support. Do I need to upload another revision without the arm arch in debian/control ? Yes please. Cheers, Julien signature.asc Description: Digital signature
Bug#702013: unblock: chromium-browser/25.0.1364.97-1
On Fri, Mar 1, 2013 at 17:56:10 +0100, Moritz Muehlenhoff wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock chromium-browser 25.0.1364.97-1. It fixes many security issues
and will be updated to the current upstream release during Wheezy release
cycle
as well.
That means somebody needs to get it to build on arm{el,hf}, or get the
binaries removed, though.
https://buildd.debian.org/status/package.php?p=chromium-browser
Cheers,
Julien
signature.asc
Description: Digital signature
Bug#702013: unblock: chromium-browser/25.0.1364.97-1
On Sat, Mar 02, 2013 at 01:12:51PM +0100, Julien Cristau wrote:
On Fri, Mar 1, 2013 at 17:56:10 +0100, Moritz Muehlenhoff wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock chromium-browser 25.0.1364.97-1. It fixes many security
issues
and will be updated to the current upstream release during Wheezy release
cycle
as well.
That means somebody needs to get it to build on arm{el,hf}, or get the
binaries removed, though.
https://buildd.debian.org/status/package.php?p=chromium-browser
Guiseppe, Michael?
IMO, if there's no official upstream support for arm by upstream, we should
drop arm support to prevent unpleasant surprises and delays when updating to
current upstream releases in wheezy-security.
Cheers,
Moritz
Cheers,
Julien
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702013: unblock: chromium-browser/25.0.1364.97-1
That means somebody needs to get it to build on arm{el,hf}, or get the
binaries removed, though.
https://buildd.debian.org/status/package.php?p=chromium-browser
Guiseppe, Michael?
IMO, if there's no official upstream support for arm by upstream, we should
drop arm support to prevent unpleasant surprises and delays when updating to
current upstream releases in wheezy-security.
The arm builds have been nothing but trouble so far, and without
upstream interest they are likely to continue to break with most
upstream releases.
My vote is removal, but its really Guiseppe's call.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702013: unblock: chromium-browser/25.0.1364.97-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock chromium-browser 25.0.1364.97-1. It fixes many security issues and will be updated to the current upstream release during Wheezy release cycle as well. Cheers, Moritz unblock chromium-browser/25.0.1364.97-1 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
