From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 6F2AB1381FA for ; Tue, 3 Jun 2014 15:17:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 829CDE0AAD; Tue, 3 Jun 2014 15:17:20 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7D3DFE08D3 for ; Tue, 3 Jun 2014 15:17:19 +0000 (UTC) Received: from [10.173.147.84] (85-76-37-17-nat.elisa-mobile.fi [85.76.37.17]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: ssuominen) by smtp.gentoo.org (Postfix) with ESMTPSA id 1D0B533FB3E for ; Tue, 3 Jun 2014 15:17:17 +0000 (UTC) Message-ID: <538DE670.1070906@gentoo.org> Date: Tue, 03 Jun 2014 18:14:56 +0300 From: Samuli Suominen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Systemd upower References: <20140603161406.0400709b5f38540475ac4c1f@web.de> <6653474.aQqAYpAeto@wstn> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 80e54510-d915-4c5b-97a2-155a736492e7 X-Archives-Hash: 397a8d6bfc5bb797d4204da0374b63af On 03/06/14 18:10, Canek Peláez Valdés wrote: >> Maybe a news item explaining the switch of upower would help those who haven't >> blundered into this yet. > Maybe. The thing is, this is going to keep happening, as more and more > infrastructure migrates towards systemd. Perhaps a news item everytime > it happens is unrealistic? > > I would expect Gentoo users to search for viable solutions by > themselves, or asking for ways to solve it in the proper channels > (like Silvio did). Yes, thank you. That's exactly how I've seen the situation, but am I expecting too much from our users? (I think I'll be forced to write up some minimal news item just to shut up the loud minority who can't be bothered to do anything themselfs, like even read package ChangeLogs if they stumble upon something manual.)