Re: [gentoo-user] eix-test-obsolete
the...@sys-concept.com wrote: > On 03/26/2017 05:16 PM, Alan McKinnon wrote: > > On 26/03/2017 23:14, the...@sys-concept.com wrote: > >> I'm in a process of clean-up my packages. > >> Running: eix-test-obsolete > >> > >> Shows a lot of valuable information, but I can not decode entries > >> in: > >> > >> Installed packages with a version not in the database (or masked): > >> ... > >> example > >> [?] app-editors/nano (2.6.3@03/25/2017 -> 2.3.1-r2): GNU GPL'd Pico > >> clone with more functionality > >> > >> I've nano-2.6.3 installed. What does the "-> 2.3.1-r2" indicates? > >> > > > > > > > > Oh come on Thelma, really? > > > > > > Did you even bother to read the eix man page? This is getting > > tiresome. Please just stop it, gentoo-user is not your personal > > Google clone or a quasi-brain you can tap for any answer without > > doing some thinking of your own > > > > A simple eix nano would have told you everything: > > > > It's in section "installed packages not in database" > > Latest stable nano is 2.6.3. You have 2.3.1-r2 > > Apology Alan, but this still isn't very clear to me. > Yes, I did check with "eix nano" and it showed that I had latest > version installed. > > Even "emerge -Ca nano" showed I had no prior version installed. > So am still confused why is it has "-> 2.3.1-r2" > > I figured it must be a pointer to an older version but since I had a > newest version installed why pointer to an older version? > > man eix only shows "eix-test-obsolete" is equivalent to eix -tTc Maybe an eix-update will help. -- Regards wabe
Re: [gentoo-user] eix-test-obsolete
On 03/26/2017 05:16 PM, Alan McKinnon wrote: > On 26/03/2017 23:14, the...@sys-concept.com wrote: >> I'm in a process of clean-up my packages. >> Running: eix-test-obsolete >> >> Shows a lot of valuable information, but I can not decode entries in: >> >> Installed packages with a version not in the database (or masked): >> ... >> example >> [?] app-editors/nano (2.6.3@03/25/2017 -> 2.3.1-r2): GNU GPL'd Pico >> clone with more functionality >> >> I've nano-2.6.3 installed. What does the "-> 2.3.1-r2" indicates? >> > > > > Oh come on Thelma, really? > > > Did you even bother to read the eix man page? This is getting tiresome. > Please just stop it, gentoo-user is not your personal Google clone or a > quasi-brain you can tap for any answer without doing some thinking of > your own > > A simple eix nano would have told you everything: > > It's in section "installed packages not in database" > Latest stable nano is 2.6.3. You have 2.3.1-r2 Apology Alan, but this still isn't very clear to me. Yes, I did check with "eix nano" and it showed that I had latest version installed. Even "emerge -Ca nano" showed I had no prior version installed. So am still confused why is it has "-> 2.3.1-r2" I figured it must be a pointer to an older version but since I had a newest version installed why pointer to an older version? man eix only shows "eix-test-obsolete" is equivalent to eix -tTc -- Thelma --
Re: [gentoo-user] eix-test-obsolete
On 26/03/2017 23:14, the...@sys-concept.com wrote: I'm in a process of clean-up my packages. Running: eix-test-obsolete Shows a lot of valuable information, but I can not decode entries in: Installed packages with a version not in the database (or masked): ... example [?] app-editors/nano (2.6.3@03/25/2017 -> 2.3.1-r2): GNU GPL'd Pico clone with more functionality I've nano-2.6.3 installed. What does the "-> 2.3.1-r2" indicates? Oh come on Thelma, really? Did you even bother to read the eix man page? This is getting tiresome. Please just stop it, gentoo-user is not your personal Google clone or a quasi-brain you can tap for any answer without doing some thinking of your own A simple eix nano would have told you everything: It's in section "installed packages not in database" Latest stable nano is 2.6.3. You have 2.3.1-r2 -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] eix-test-obsolete
I'm in a process of clean-up my packages. Running: eix-test-obsolete Shows a lot of valuable information, but I can not decode entries in: Installed packages with a version not in the database (or masked): ... example [?] app-editors/nano (2.6.3@03/25/2017 -> 2.3.1-r2): GNU GPL'd Pico clone with more functionality I've nano-2.6.3 installed. What does the "-> 2.3.1-r2" indicates? -- Thelma
Re: [gentoo-user] eix-test-obsolete problem
Thanks very much. It works. BTW, there is a trivial error in you reply as following On Fri, Mar 07, 2008 at 06:06:02PM +0100, Vaeth wrote: your name in a new file profile/repo_name) and then to reemerge ^^ It should be profiles/repo_name -- Shaochun Wang [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] eix-test-obsolete problem
On Fri, 7 Mar 2008 10:50:57 +0800, Shaochun Wang wrote:
It seems that there is no cache in the portage overlays, so update-eix
can't get the package information in these overlay.
That's normal. eix still gets the information, by reading the filesystem.
The cache is simply a way of speeding u this process for large trees.
What can I do to get the local overlay picked by eix?
It should already, if you search for a package that has an ebuild in the
overlay, it should display it, along with the name of the overlay.
% eix openchrome
* x11-drivers/xf86-video-openchrome [1]
Available versions: 0.2.901 {dri}
Description: VIA unichrome graphics driver
[1] digimed /mnt/portage/local
--
Neil Bothwick
Modesty Becomes You. Try It More Often.
signature.asc
Description: PGP signature
Re: [gentoo-user] eix-test-obsolete problem
Installed packages with a version not in the database (or masked): [I] app-misc/beagle ([EMAIL PROTECTED]/27/08) ^ This is your problem: eix is not able to detect from which repository this version was installed. The reason is that you have not given your overlay a name. Some time ago, eix was able to guess the repository by means of the information in /var/db/*/*/environment.bz2, but new portage versions do not store that information in this file anymore. The clean solution of your problem is to give your overlay a name (i.e. to create a profile subdirectory in your overlay and store your name in a new file profile/repo_name) and then to reemerge all packages from the overlay so that the name is also stored in the /var/db database. (Instead of reemerging you can also hack the database manually and create the files /var/db/*/*/repository with the corresponding overlay name in it; however, I give no guarantee that this will not have unexpected side effects...). If you want that eix-test-obsolete just ignores the repository (i.e. that 0.3.3[?] is found in the database even if the version in the database is from a possibly different overlay), set NONEXISTENT_IF_OTHER_OVERLAY='false' in /etc/eixrc. However, I would not recommend this. The output of update-eix is as expected: [3] /usr/local/portage (cache: none) ^^ This is empty, because you have not named your overlay yet This means that the cache method none is used (man eix for details) which is the default for overlays unless you set something special.[*] [*] With eix-0.12.0 the default has changed to a new cache method which appears superior (but has some security risks). The previous cache method none was renamed. -- gentoo-user@lists.gentoo.org mailing list
[gentoo-user] eix-test-obsolete problem
I have an local overlay, which contains some ebuild written by myself or copied from bugzilla. When I execute eix-test-obsolete, it display the following wierd thing: Installed packages with a version not in the database (or masked): [I] app-misc/beagle ([EMAIL PROTECTED]/27/08): Search tool that ransacks your personal information space to find whatever you're looking for [I] net-ftp/proftpd ([EMAIL PROTECTED]/20/08): An advanced and very configurable FTP server. [I] x11-misc/qterm ([EMAIL PROTECTED]/07/08): QTerm is a BBS client in Linux. [1] /usr/local/portage And I also notice that when I execute command update-eix, the following is printed: Reading Portage settings .. Building database (/var/cache/eix) .. [0] gentoo /usr/portage/ (cache: metadata) Reading 100% [1] /usr/portage/local/layman/sajinet (cache: none) Reading 100% [2] berkano /usr/portage/local/layman/berkano (cache: none) Reading 100% [3] /usr/local/portage (cache: none) Reading 100% Applying masks .. Database contains 12454 packages in 152 categories. It seems that there is no cache in the portage overlays, so update-eix can't get the package information in these overlay. What can I do to get the local overlay picked by eix? -- Shaochun Wang [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] -- gentoo-user@lists.gentoo.org mailing list
