it's good to announce stuff thru eselect news
i like that
i don't need to look up thru slow ff while i m in prompt console
;-p



Tryyabbadabbadont wrote:The only problem that I have with it is that it doesn't support bash completion like some of the other eselect modules do. It is a pain to type in the entire article ID, especially when there is only one. Now if I could only figure out how the others support bashcomp, I would see about adding it to the news module...
Code: Select all
eselect news read newCode: Select all
eselect news read 1Code: Select all
eselect news read all

hehe... I HAD to because yeah, not having bash completion is a bit of a pain, huh? You should definitely figure that out and submit a patchyabbadabbadont wrote:Pshaw! No one worth their salt actually reads the help docs...
Code: Select all
$ eselect news read
!!! Error: You didn't tell me what you want to read
Killed
Good Lord! You mean you actually expect it to gracefully handle errors?!? They've only been working on it for four years. Give it a reasonable amount of time to mature and I'm sure they'll iron out all the bugs. (say, another four years or sodjanderson wrote:hehe... I HAD to because yeah, not having bash completion is a bit of a pain, huh? You should definitely figure that out and submit a patchyabbadabbadont wrote:Pshaw! No one worth their salt actually reads the help docs...
Oh, andseems a bit excessive to me... just playing around with this module makes me feel like every other step is "!!! ERROR !!! KILLED!!! arrrrg".Code: Select all
$ eselect news read !!! Error: You didn't tell me what you want to read Killed
Code: Select all
# eselect news list
Unread news items:
(none found)
Read news items:
(none found)
I have had the same problem.slack---line wrote:I guess I'm being dumb, but...
I'd be grateful if someone could tell me where I actually grab the news from?Code: Select all
# eselect news list Unread news items: (none found) Read news items: (none found)
Cheers
slack

Not likely. No doubt you ran emerge --sync when you (re-)merged those packages.Qanii wrote:I have had the same problem.slack---line wrote:I'd be grateful if someone could tell me where I actually grab the news from?
re-emerging eselect and eselect-news fixed it.


Well, the Gentoo Way is to provide choices: You have the option to break your system first, then read the news after you try to solve the problem on your own.castor_fou wrote:The only con with this approach is that I won't have to search for hours why I broke my system. And that was good occasions to learn how linux works too.


Ahh ha, this may explain why I get nothing since I use the following command to sync nightly on an NSLU2 NAS device that I then mount over NFS for my desktop and laptop...timeBandit wrote:Not likely. No doubt you ran emerge --sync when you (re-)merged those packages.Qanii wrote:I have had the same problem.slack---line wrote:I'd be grateful if someone could tell me where I actually grab the news from?
re-emerging eselect and eselect-news fixed it.
News items are part of the Portage tree. They are downloaded when you sync your tree.
Code: Select all
rsync --recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages rsync://rsync.gentoo.org/gentoo-portage /usr/portage/
Whilst I'm still unable to suss out where the news items are stored, I don't think its /var/log/news/ since when you sync your portage tree its all within /usr/portage/ (if my understanding is correct).sera wrote:There exists /var/log/news/ on my system but it's always empty. I wonder if there is a minimum portage version needed to get this feature to work.Are the news items located in /distfiles, /local or /packages and I'm inadvertently excluding the news items with the above?
Good detective work, I too have stuff in there and it appears to be up-to-date, but eselect news still doesn't report anything...sera wrote:Ok, found the non empty directory /usr/portage/metadata/news/
Code: Select all
$ ls /usr/portage/metadata/news/
2007-05-04-paludis-0.24 2009-04-06-tetex timestamp.chk
2009-01-04-sparc-multilib 2009-04-06-x_server-1_5
$ eselect news list
Unread news items:
(none found)
Read news items:
(none found)

Code: Select all
# rm /var/lib/gentoo/news/news-gentoo.*
# find /usr/portage/metadata/news -mindepth 1 -type d -printf "%P\n" >/var/lib/gentoo/news/news-gentoo.unreadtimeBandit wrote:This resets the read/unread markers for the main Portage tree:eselect news list will then list all news items. Note that news items are tracked per overlay, by repository name (gentoo is the main tree).Code: Select all
# rm /var/lib/gentoo/news/news-gentoo.* # find /usr/portage/metadata/news -mindepth 1 -type d -printf "%P\n" >/var/lib/gentoo/news/news-gentoo.unread