From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 5DF23138350 for ; Wed, 22 Apr 2020 15:58:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 01B6FE0E71; Wed, 22 Apr 2020 15:58:53 +0000 (UTC) Received: from covici.com (debian-2.covici.com [166.84.7.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A376DE0E2A for ; Wed, 22 Apr 2020 15:58:52 +0000 (UTC) Received: from ccs.covici.com (ccs.covici.com [70.109.53.110]) (authenticated bits=0) by covici.com (8.15.2/8.15.2/Debian-14~deb10u1) with ESMTPSA id 03MFwt26008653 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Wed, 22 Apr 2020 11:58:57 -0400 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.15.2/8.15.2) with ESMTPS id 03MFwmBC770243 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Wed, 22 Apr 2020 11:58:48 -0400 Received: (from covici@localhost) by ccs.covici.com (8.15.2/8.15.2/Submit) id 03MFwmB7770242; Wed, 22 Apr 2020 11:58:48 -0400 Date: Wed, 22 Apr 2020 11:58:48 -0400 Message-ID: From: John Covici To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Is Gentoo dead? In-Reply-To: References: <20200421165803.GB187193@redacted> <20200421183317.GC187193@redacted> <877dy8isdu.fsf@wedjat.horus-it.com> <20200421190035.GE187193@redacted> <8ca01aef-6df7-f4cb-7e37-5459a1009fbd@gmail.com> <0510a8e0-a427-7b6a-e795-dcfab6dcb372@gmail.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/26 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) Organization: Covici Computer Systems 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 72054000-8e63-4c14-92ee-8165f3c899cb X-Archives-Hash: 3fbb768cf39ee3c63976491e1959d1f6 On Wed, 22 Apr 2020 11:26:20 -0400, Jack wrote: >=20 >=20 > On 4/22/20 11:20 AM, John Covici wrote: > > On Wed, 22 Apr 2020 11:04:24 -0400, > > Dale wrote: > >> [1 ] > >> John Covici wrote: > >>> On Wed, 22 Apr 2020 08:53:24 -0400, > >>> Dale wrote: > >>>=20 > >>>> I did a search on the forums for teamview but didn't find that probl= em. > >>>> Did you perhaps install it without using portage at some point?=A0 I= f not, > >>>> can you try to emerge it and post the failure here, a new thread mig= ht > >>>> be best.=A0 I bet there is someone here who can fix it even if they = don't > >>>> use that package.=A0 Generally, a file collision for one package is > >>>> handled much like any other package.=A0 It's been a long time and em= erge > >>>> has changed a LOT but the last time I ran into this, I unmerged the > >>>> package and then re-emerged it. > >>>>=20 > >>>> Sendmail.=A0 I found this: > >>>>=20 > >>>>=20 > >>>> root@fireball / # cat > >>>> /var/cache/portage/tree/mail-mta/sendmail/metadata.xml > >>>> > >>>> > >>>> > >>>> =A0=A0=A0=A0=A0=A0=A0 > >>>> > >>>> root@fireball / # > >>>>=20 > >>>>=20 > >>>> It seems to be maintainer needed at the moment.=A0 Most likely a dev > >>>> retired or was otherwise unable to maintain it any longer.=A0 I'm no= t sure > >>>> who to contact to see if it can be nudged into action tho. You may c= an > >>>> talk to a dev, Rich is active on here, and see if he knows or is wil= ling > >>>> to post on -dev about it needing attention.=A0 Given its widespread = use, > >>>> surely someone who uses it can step up and maintain it. > >>>>=20 > >>>> Ant-core is maintained by the java team.=A0 I'm not sure what their = status > >>>> is at the moment but since it still exists, I'm sure they are active. > >>>> I've seen posts in the past that the java team is a bit slow, lots of > >>>> work and not enough time in the day.=A0 Might just take a little tim= e. > >>>>=20 > >>> Here is the relevant section from teamviewer build: > >>> * checking 102 files for package collisions > >>> * This package will overwrite one or more files that may belong to > >>> other > >>> * packages (see list below). You can use a command such as > >>> `portageq > >>> * owners / ` to identify the installed package that ow= ns > >>> a > >>> * file. If portageq reports that only one package owns a file > >>> then do > >>> * NOT file a bug report. A bug report is only useful if it > >>> identifies at > >>> * least two or more packages that are known to install the same > >>> file(s). > >>> * If a collision occurs and you can not explain where the file > >>> came from > >>> * then you should simply ignore the collision since there is > >>> not enough > >>> * information to determine if a real problem exists. Please > >>> do NOT file > >>> * a bug report at https://bugs.gentoo.org/ unless you > >>> report exactly > >>> * which two packages install the same file(s). See > >>> * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers > >>> for tips on how > >>> * to solve the problem. And once again, please do NOT > >>> file a bug report > >>> * unless you have completely understood the above > >>> message. > >>> * > >>> * Detected file collision(s): > >>> * > >>> * /usr/share/dbus-1/services/com.teamviewer.TeamViewer.servi= ce > >>> * /usr/share/dbus-1/services/com.teamviewer.TeamViewer.Desk= top.service > >>> * /usr/share/polkit-1/actions/com.teamviewer.TeamViewer.policy > >>> * /usr/share/icons/hicolor/24x24/apps/TeamViewer.png > >>> * /usr/share/icons/hicolor/48x48/apps/TeamViewer.png > >>> * > >>> * /usr/share/icons/hicolor/32x32/apps/TeamViewer.png > >>> * /usr/share/icons/hicolor/16x16/apps/TeamViewer.png > >>> * /usr/share/icons/hicolor/256x256/apps/TeamViewer.png > >>> * /lib/systemd/system/teamviewerd.service > >>> * /opt/bin/teamviewer > >>> * /opt/bin/teamviewerd > >>> * > >>> * Searching all installed packages for file > >>> collisions... > >>> * > >>> * Press Ctrl-C to Stop > >>> * > >>> * net-misc/teamviewer-14.7.1965:14::gentoo > >>> * /lib/systemd/system/teamviewerd.service > >>> * /opt/bin/teamviewer > >>> * /opt/bin/teamviewerd > >>> * /usr/share/dbus-1/services/com.teamviewer.TeamViewer.Des= ktop.service > >>> * > >>> * /usr/share/dbus-1/services/com.teamviewer.TeamViewer.se= rvice > >>> * /usr/share/icons/hicolor/16x16/apps/TeamViewer.png > >>> * /usr/share/icons/hicolor/24x24/apps/TeamViewer.png > >>> * /usr/share/icons/hicolor/256x256/apps/TeamViewer.png > >>> * /usr/share/icons/hicolor/32x32/apps/TeamViewer.png > >>> * > >>> * /usr/share/icons/hicolor/48x48/apps/TeamViewer.png > >>> * /usr/share/polkit-1/actions/com.teamviewer.TeamViewer.pol= icy > >>> * > >>> * Package > >>> 'net-misc/teamviewer-15.4.44= 45' > >>> NOT merged due to file > >>> * collisions. If necessary, > >>> refer to your elog messages > >>> for the whole > >>> * content of the above > >>> message. > >>>=20 > >>> How do ebuilds normally handle such a thing -- don't all new versions > >>> have this situation? > >>>=20 > >> It does but it seems portage thinks the files belong to another > >> package.=A0 I'm not sure why that is tho.=A0 You may can use the porta= geq > >> command it mentions to see what that is.=A0 I suspect it will be a > >> interesting result.=A0 I think I've only ran into this once.=A0 There = is a > >> way to override it but I can't recall how it's done. > >>=20 > >> If it were me, I'd manually remove the files and emerge the package IF > >> they do not belong to another package.=A0 Once they are gone, it won't= be > >> a problem.=A0 Maybe this is just a quirk or something that is a one ti= me > >> deal. > >>=20 > >> I think this is how to disable this but I'd be sure it is safe before > >> doing this. > >>=20 > >> FEATURES=3D"-collision-protect" emerge -a teamviewer > >>=20 > >> Make sure the spelling is correct there.=A0 Again, make sure those don= 't > >> belong to another package that will be broken.=A0 In theory, this > >> shouldn't happen to begin with. > >>=20 > >> Hope that gives you some options. > > The reason I did not try any of those is because the package which > > owns the files is a previous version of the same package!! This > > disturbs me that portage does not igure this out all by itself. >=20 > How did you determine that?=A0 Does portage agree with that > statement?=A0 Is it the same category and package?=A0 Was the > previous version installed by portage? >=20 > One possible approach would be to quickpg the installed version, > then unmerge it and try the new emerge again. Yes, portage agrees with that statement, maybe I didn't give you the whole log, I thought it said that in there -- I did see that, I am sure. My question is how does this work normally, when you merge a package and update is this not always the case that there are files owned by the previous version on the system? --=20 Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici@ccs.covici.com