From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1N7UNJ-0007gL-Og for garchives@archives.gentoo.org; Mon, 09 Nov 2009 13:33:43 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B4E3EE0B18; Mon, 9 Nov 2009 13:33:40 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 91D08E0B18 for ; Mon, 9 Nov 2009 13:33:40 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 6E6F367E9C for ; Mon, 9 Nov 2009 13:33:39 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -1.763 X-Spam-Level: X-Spam-Status: No, score=-1.763 required=5.5 tests=[AWL=0.836, BAYES_00=-2.599] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UvJAyKyyLj6h for ; Mon, 9 Nov 2009 13:33:32 +0000 (UTC) Received: from mail-fx0-f211.google.com (mail-fx0-f211.google.com [209.85.220.211]) by smtp.gentoo.org (Postfix) with ESMTP id 755E367D3F for ; Mon, 9 Nov 2009 13:33:32 +0000 (UTC) Received: by fxm3 with SMTP id 3so1001809fxm.24 for ; Mon, 09 Nov 2009 05:33:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Ksed7tXMOrqnRbEdhX3OJ0LjqDz7mje8z9N+5SIiTOc=; b=lggS5hm+favVIR8EvTGLHXtWBfkF672CwLjPoFZW4erakueRMb+FWZnpAeDjEAp7iA P+93839eci0z3P54eJRZ5+5FnZh+K2Z7yhYH1j9XYDIA4rt3+iaC4byiKIBzM13owHqB FJ19q6Km1j5+4Bw4M5OFasvS6Bg95PulNcUgc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=Ws7TZzPDvmJ6mwSOl9sVOxg9eAymqxVO0xdNuGBdGm8J/rLF86qkzJ8olNh5PUD5wZ lCuqQT/k1LpPBSUykIkrpDI8V4HuDcqPjSiemZOAwYbYCktItiZRh9bOAnq5VND2gPkY 7ibncmb937ErSc8k+Pw4XHMw2aaewGmxbJ9l4= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Sender: yngwin.gentoo@gmail.com Received: by 10.239.139.207 with SMTP id u15mr736256hbu.95.1257773611088; Mon, 09 Nov 2009 05:33:31 -0800 (PST) Date: Mon, 9 Nov 2009 14:33:30 +0100 X-Google-Sender-Auth: 676b5311736581ea Message-ID: Subject: [gentoo-dev] URGENT: exotic arches need Qt 4.5.3 stabilization From: Ben de Groot To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 9766f451-e750-4e34-a67f-bb3f42b067a8 X-Archives-Hash: dd63d00c5ed5219d8ee67419532aadfa I am of the opinion it is irresponsible to leave vulnerable versions of Qt with known security bugs any longer in the tree. The Qt team therefore requests that arches that have not done so already move quickly on stabilizing Qt 4.5.3, see bug 290922 and 283810. We plan on REMOVING or at the very least HARDMASKING pending removal all <=4.5.2 ebuilds by the end of this week. This means that arches that have not stabilized 4.5.3 would loose their stable Qt4 version. Please let us know if there is any way in which we can assist arches. We are aware that some arches are down to one active person. But if there is no other way, maybe the status of such arches should be reconsidered. We especially request ppc64 to be marked as an experimental arch, as it is the worst one lagging in stabilization. See bug 281821 for a poignant example, a 3 months open security bug. Regards, -- Ben de Groot Gentoo Linux developer (qt, media, lxde, desktop-misc) ______________________________________________________