Bugzilla Bug 122079

Pleas move conky 1.3.5 to stable (another version is acceptable) I have been
running it since it went ~x86 with no problems. A search for conky show's no
bugs. With torsmo having been removed from portage and conky it's successor we
could use a non ~arch release of it.

Brenden - last I spoke you I think you mentioned that 1.3.4 was your preferred
package to go stable (I could be wrong). Is this still the case?

Caleb - I agree with your reasoning. Just checking with the guru conky devs for
a version.

I posted on the fluxbox doc bug that it should replace torsmo. but since it was
~arch that I would request it moved to stable. So we don't have a ~arch package
in the doc.

Conky 1.3.5 has a couple significant bugs.  Please wait a few more days so I
can find some time to do a 1.4.0 release.

I can wait - not a problem.

I can wait too.

bug 122643 is the conky 1.4.0 bug.

According to bug 122637 conky should be okay on alpha too.

I'm Testing the 1.4.0 Build so far so good. It compiled it runs. I'll post
there if I have problems. 

Torsmo-0.17 had KEYWORDS="x86 ppc amd64 sparc"
I propose we do the same for conky-1.4.0 in 2 weeks if no objections. (btw
please remind me or just cc the arch teams then)

(In reply to comment #9)
> Torsmo-0.17 had KEYWORDS="x86 ppc amd64 sparc"
> I propose we do the same for conky-1.4.0 in 2 weeks if no objections. (btw
> please remind me or just cc the arch teams then)
> 

sounds good

As per comment 9, Torsmo, the abandoned codebase of Conky, had stable keywords
on your arch. Now that Torsmo has been removed from Gentoo it is only fair that
Conky receives the same stabilizations status.

Thanks for your consideration.

I had it already running on ppc, so stable.

sparc stable.

My network stats look kinda weird, and I'm getting a lot of:

Conky: unknown variable tcp_portmon

Nor do I see where to define that off hand.  The graphs for ath0 appear to
work, but the text doesn't.

xmms_player seems to be defined, but nothing as far as the actual visible
output (or an example) is shown.

I'll attach the config I have for it.

Created an attachment (id=81133) [edit]
conkyrc

Here's the config for it.  Some of the stuff I assume has docs on how to work
with it, but just in case.

(In reply to comment #14)
> My network stats look kinda weird, and I'm getting a lot of:
> 
> Conky: unknown variable tcp_portmon
> 
> Nor do I see where to define that off hand.  The graphs for ath0 appear to
> work, but the text doesn't.
> 
> xmms_player seems to be defined, but nothing as far as the actual visible
> output (or an example) is shown.
> 
> I'll attach the config I have for it.
> 

echo "app-admin/conky -ipv6 xmms" >> /etc/portage/package.use

regarding tcp_portmon, this functionality is for ip4 only and, as such, it only
read entries in /proc/net/tcp.   if you are only running ip6, the port monitors
wont work.   if you are running a mixed ip4/ip6 box, you must config conky with
-ipv6, as brenden mentioned.

as for xmms, you must config it with use flag xmms if you are using that
player, set xmms_player, as you did -- but that is not enough.   you must then
add your text variables, of which there are many:

${xmms_title}
${xmms_status}
${xmms_bar}

are three popular ones.   cheers.

x86 stable \(^.^)/ Yay!

I have -ipv6 yet I'm still getting tcp_portmon weirdness.  I do have a
/proc/net/tcp file as well.  XMMS functionality seems to have a minor bug where
it doesn't know how to handle the status bar if you run conky while in the
middle of playing a file.

I would like to know exactly what problems you're having with the portmon
stuff.   

amd64 stable

all stable - closing.