From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-66335-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 38E1213877A
	for <garchives@archives.gentoo.org>; Mon, 23 Jun 2014 23:15:25 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id E0F5CE0880;
	Mon, 23 Jun 2014 23:15:19 +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 F2207E085A
	for <gentoo-dev@lists.gentoo.org>; Mon, 23 Jun 2014 23:15:18 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by smtp.gentoo.org (Postfix) with ESMTP id 38AFA33F5FA
	for <gentoo-dev@lists.gentoo.org>; Mon, 23 Jun 2014 23:15:18 +0000 (UTC)
X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org
X-Spam-Flag: NO
X-Spam-Score: -1.17
X-Spam-Level:
X-Spam-Status: No, score=-1.17 tagged_above=-999 required=5.5
	tests=[AWL=-1.158, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001,
	SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from smtp.gentoo.org ([IPv6:::ffff:127.0.0.1])
	by localhost (smtp.gentoo.org [IPv6:::ffff:127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PDdEEqX7pVri for <gentoo-dev@lists.gentoo.org>;
	Mon, 23 Jun 2014 23:15:12 +0000 (UTC)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.gentoo.org (Postfix) with ESMTPS id 3DA4C33FD61
	for <gentoo-dev@gentoo.org>; Mon, 23 Jun 2014 23:15:12 +0000 (UTC)
Received: from list by plane.gmane.org with local (Exim 4.69)
	(envelope-from <lnx-gentoo-dev@m.gmane.org>)
	id 1WzDS3-0004c4-NM
	for gentoo-dev@gentoo.org; Tue, 24 Jun 2014 01:15:03 +0200
Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <gentoo-dev@gentoo.org>; Tue, 24 Jun 2014 01:15:03 +0200
Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <gentoo-dev@gentoo.org>; Tue, 24 Jun 2014 01:15:03 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: gentoo-dev@lists.gentoo.org
From: Duncan <1i5t5.duncan@cox.net>
Subject: [gentoo-dev] Re: Changes in installed ebuilds
Date: Mon, 23 Jun 2014 23:14:52 +0000 (UTC)
Message-ID: <pan$e60c0$3e4f188b$d1a21e65$22911b7f@cox.net>
References: <loa1tb$mkn$1@ger.gmane.org>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net
User-Agent: Pan/0.140 (Chocolate Salty Balls; GIT d447f7c
 /m/p/portage/src/egit-src/pan2)
X-Archives-Salt: 3a497872-88c4-4e42-9341-e6b7e253704c
X-Archives-Hash: 35be388827d1dd7f1b765fb72004e6d9

Jörg Schaible posted on Mon, 23 Jun 2014 22:15:39 +0200 as excerpted:

> can somebody tell my, since when existing (and installed) ebuilds
> suddenly change without at least increasing the version number?


That has always been the case.  Existing ebuilds aren't always bumped for 
changes, only if the changes are seen to be installation significant.  In 
particular, dependencies generated in eclasses can change, thus changing 
dependencies for the potentially many installed packages inheriting those 
eclasses. It's thus possible to correct minor problems without forcing a 
reinstall.

Tho that also means it's possible to screw things up, and occasionally 
that does happen.  I personally run --update --deep with all my updates 
here, and run ~arch (with gentoo/kde overlay live-kde) as well, and 
believe that spares me some big forced-upgrade jumps since I tend to be 
well ahead of the minimum version numbers and older, less current testing 
ebuilds, but I do think it makes a difference.  Additionally, mostly 
stable systems with a few ~arch keyworded packages is a known low-testing 
and not always anticipated corner-case.  All-stable and all-~arch systems 
are better tested and supported.

Without knowing/checking specifics and assuming it wasn't a stable/~arch 
mixed-system issue, the problem here was likely a screwup.  Someone 
didn't anticipate the effect of their update on your specific case, 
triggering an unintended result.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman