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 5093B138350 for ; Wed, 22 Apr 2020 13:51:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C18AFE0D82; Wed, 22 Apr 2020 13:51:47 +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 5337FE0D68 for ; Wed, 22 Apr 2020 13:51:47 +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 03MDpoQr007450 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Wed, 22 Apr 2020 09:51:51 -0400 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.15.2/8.15.2) with ESMTPS id 03MDpgQX647870 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Wed, 22 Apr 2020 09:51:42 -0400 Received: (from covici@localhost) by ccs.covici.com (8.15.2/8.15.2/Submit) id 03MDpgGq647869; Wed, 22 Apr 2020 09:51:42 -0400 Date: Wed, 22 Apr 2020 09:51:42 -0400 Message-ID: From: John Covici To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Is Gentoo dead? In-Reply-To: <0510a8e0-a427-7b6a-e795-dcfab6dcb372@gmail.com> 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: 826008fd-44b7-4088-9228-638d41d2e125 X-Archives-Hash: dd73ea56f0c786a8292d171e3a6871c9 On Wed, 22 Apr 2020 08:53:24 -0400, Dale wrote: >=20 > [1 ] > John Covici wrote: > > On Wed, 22 Apr 2020 04:15:18 -0400, > > Dale wrote: > >> [1 ] > >> John Covici wrote: > >>> I am seeing a lot more unmaintained packages -- at least in the ones I > >>> have -- than there used to be and bugs going unanswered probably > >>> because of that. Not sure what to do about it, I don't have time to > >>> get into doing this much, just keeping up with world updates is quite > >>> time consuming all by itself. > >>> > >> > >> That may be but the packages that are most used are likely maintained > >> and well maintained at that.=A0 There are some old packages that haven= 't > >> been updated in years, upstream is dead or no one uses them much anymo= re > >> that are slowly being removed.=A0 If one can't install them, no real p= oint > >> in them being in the tree.=A0 I might add, the switch from the much ol= der > >> pythons are really forcing a house cleaning.=A0 But, some packages are > >> just out of date and something new has taken their place.=A0 Nothing n= ew > >> there.=A0 I'm sure this happens with every distro out there, even the = paid > >> ones. > >> > >> I follow -dev and have recently had to uninstall a package and install > >> something else that is newer and more up to date.=A0 I saw a message a= bout > >> that old package that seemed to stop working for me a good while ago.= =A0 > >> What I had still lurking about would sometimes crash and I didn't trust > >> it.=A0 I used to use that as a GUI to manage LVM.=A0 I use LVM a lot h= ere.=A0 > >> In that message was them removing the old package and recommending a > >> replacement I never heard of.=A0 I installed it and it may actually be > >> better than the old software I used to use.=A0 While the old package m= ay > >> be gone, the new one seems to be more up to date, stable and appears to > >> have a better design.=A0 Different for sure, I'll have to learn how the > >> GUI does its thing but could be better in the end. Since LVM has been > >> updated a good bit in the past year or so, that old software either > >> needed a lot of work or just use the newer software. > >> > >> There are a lot of packages that are just not used by enough people to > >> maintain them anymore.=A0 Some are being replaced with more up to date > >> packages.=A0 There are lots of reasons for that.=A0 If a package you u= se is > >> being removed, search -dev and look to see if there is a replacement > >> mentioned in the last rites message.=A0 If it was removed, they almost > >> always include a replacement if there is one.=A0 Sometimes another pac= kage > >> absorbs what the old package used to do. While at times -dev can get > >> quite busy, I'd be lost without it.=A0 Things are mentioned there about > >> upcoming changes that I don't see mentioned anywhere else.=A0 That > >> includes this list as well.=A0 It's a great way to keep somewhat up to > >> date on what's going on.=A0 One doesn't have to read every post either= .=A0 > >> After a while, you can tell by the subject line if that thread will be > >> anything you would be interested in.=A0 Last rites, things about upgra= des > >> and such get my attention.=A0 I generally know when something big is g= oing > >> to happen weeks or even months before it hits the tree. > >> > >> If you want to share what packages you are missing out on, I'd be glad > >> to search my -dev archives and see if I can find something that may he= lp.=A0 > > Well, teamviewer is the worst -- teamviewer 15 won't emerge because it > > will overwrite files belonging to the previous version (!da). Someone > > even slotted the thing, but still no joy. I filed a bug, but no > > response. Also, although I don't think there is a new version, but > > sendmail seens to be unmaintained. > > Also, ant-core -- there is a bug against that, but no fix as yet. > > >=20 >=20 > I did a search on the forums for teamview but didn't find that problem.=A0 > Did you perhaps install it without using portage at some point?=A0 If not, > can you try to emerge it and post the failure here, a new thread might > 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 emerge > 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 not sure > who to contact to see if it can be nudged into action tho. You may can > talk to a dev, Rich is active on here, and see if he knows or is willing > to post on -dev about it needing attention.=A0 Given its widespread use, > surely someone who uses it can step up and maintain it.=A0 >=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.=A0 > 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 time. >=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 owns 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.service * /usr/share/dbus-1/services/com.teamviewer.TeamViewer.Desktop.se= rvice * /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.Desktop.s= ervice * * /usr/share/dbus-1/services/com.teamviewer.TeamViewer.service * /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.policy * * Package 'net-misc/teamviewer-15.4.4445' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. How do ebuilds normally handle such a thing -- don't all new versions have this situation? --=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