conky v1.9.0-6 vs conky v1.10+

Sector11 · 2017-01-19 14:42:48

OK On Topic:

Long live Conky v1.9

Conky v1.10 is like a vacuum, it ....... ]:D

stevep · 2017-01-19 20:22:00

If you forwardport 1.9.1 (which means rebuild from source), the way to have it be seen as a higher version than 1.10 without the pinning hassle is to add or increment the epoch, which is a number added to the start of the version. So in debian/changelog:

conky (1:1.9.1-1)

will be handled as a higher version than

conky (1.10.0-1)

Last edited by stevep (2017-01-19 20:22:58)

Head_on_a_Stick · 2017-01-19 20:35:21

^ Thanks for the tip Steve, I was wondering about that

Sector11 · 2017-01-19 20:51:19

19 Jan 17 @ 17:43:25 ~
  $ list conky-all
Alias for: apt list -a filename
Listing... Done
conky-all/jessie-backports 1.10.6-1~bpo8+1 amd64
conky-all/stable,now 1.9.0-6 amd64 [installed]

Ahhhhh so we go for 1:1.9.0-6

Question: was there ever a conky v1.9.1 ??

cpoakes · 2017-01-19 21:44:02

stevep wrote:

If you forwardport 1.9.1 (which means rebuild from source), the way to have it be seen as a higher version than 1.10 without the pinning hassle is to add or increment the epoch, which is a number added to the start of the version. So in debian/changelog:
conky (1:1.9.1-1)
will be handled as a higher version than
conky (1.10.0-1)

Thanks! I have seen but never understood this numbering scheme. Like HOAS, will put it to good use with other forward-ported packages.

stevep · 2017-01-26 20:27:13

Head_on_a_Stick wrote:

I say we fork it.
As soon as I can figure out how to set up stretch packages in my OBS repository I will "forward-port" version 1.9 to stretch/Helium.

I've been trying to do that too; according to this mailing list announcement, you have to be an "advanced developer", whatever that means: http://lists.opensuse.org/opensuse-buil … 00050.html

Head_on_a_Stick · 2017-01-26 20:56:38

^ Interesting, thanks.

stevep wrote:

you have to be an "advanced developer"

Ah well, I suppose that rules me out then... 8o

Sector11 · 2017-01-26 22:11:48

Why do we need to forward port it?

Just keep the v1.9.0-6 deb files somewhere we can get them, install them with gdepi if necessary and place the installed conky-cli, conky-std or conky-all on hold.

That will work at least until the dependencies fail.

Hmmmmmmmmmm I have them back to v1.6 something I think ... I should test them all.

Head_on_a_Stick · 2017-01-27 07:33:11

The advantage of a forward-ported 1.9 version would be that no pinning would be needed to keep it installed and the code base could be maintained in the future.

unklar · 2017-01-27 08:53:23

^ Hm HoaS,

interesting and very good.
If that succeeds ... I would be with you forever.

iMBeCil · 2017-01-27 08:58:01

Head_on_a_Stick wrote:

The advantage of a forward-ported 1.9 version would be that no pinning would be needed to keep it installed and the code base could be maintained in the future.

Did you consider:
MANPOWER(Conky 1.9 maintenance) >> MANPOWER(Keep Conky 1.9 pinned)

imp2021 · 2017-01-30 09:45:54

Hmm, sounds like Übersicht needs to be rewritten to have it run on linux

DeepDayze · 2017-06-10 22:43:59

And what about any adventurous souls who track Sid or even Testing (currently Stretch) branch? In Sid there's Conky 1.10. Wonder if it will be possible to install the 1.9 conky and then pin it so it won't get updated ever.

Last edited by DeepDayze (2017-06-10 22:44:34)

Sector11 · 2017-06-10 23:52:58

someone running SID needs to try it.

Someone running "Stretch" also needs to try it - if interested.

Stable packages now:

conky (1.9.0-6) highly configurable system monitor (transitional package)
conky-all (1.9.0-6) highly configurable system monitor (all features enabled)
conky-all-dbg (1.9.0-6) highly configurable system monitor (all features enabled - debug)
conky-cli (1.9.0-6) highly configurable system monitor (basic version)
conky-cli-dbg (1.9.0-6) highly configurable system monitor (basic version - debug)
conky-std (1.9.0-6) highly configurable system monitor (default version)
conky-std-dbg (1.9.0-6) highly configurable system monitor (default version - debug)

Grab them while they last.

unklar · 2017-06-11 08:41:14

I have run here on three machines 5 siduction versions.
Of it is installed in 4 conky1.9 and in Plasma5 runs conky1.10

inxi -SM
System:    Host: x40 Kernel: 4.9.11-towo.2-siduction-686 i686 (32 bit)
           Desktop: Fluxbox 1.3.5
           Distro: siduction 15.1.0 Paint It Black - xorg - (201601171617)
Machine:   Device: laptop System: IBM product: 2371H8G v: ThinkPad X40
           Mobo: IBM model: 2371H8G
           BIOS: IBM v: 1UETD3WW (2.08 ) date: 12/21/2006
Battery    BAT0: charge: 0.9 Wh 97.8% condition: 0.9/27.4 Wh (3%)

apt-cache policy conky-all
conky-all:
  Installiert:           1.9.0-6
  Installationskandidat: 1.10.6-1
  Versionstabelle:
     1.10.6-1 500
        500 http://httpredir.debian.org/debian unstable/main i386 Packages
 *** 1.9.0-6 100
        100 /var/lib/dpkg/status

Where is the problem?

apt-cache policy conky-all
conky-all:
  Installiert:           1.10.6-1
  Installationskandidat: 1.10.6-1
  Versionstabelle:
 *** 1.10.6-1 500
        500 http://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

inxi -SM
System:    Host: sidukde Kernel: 4.11.4-towo.1-siduction-amd64 x86_64 (64 bit)
           Desktop: KDE Plasma 5.8.6 Distro: siduction 16.1.0 Patience - kde - (201702251051)
Machine:   Device: desktop Mobo: ASUSTeK model: P5Q-PRO v: Rev 1.xx
           BIOS: American Megatrends v: 2102 date: 02/23/2009

At least 1 time a week

apt update && apt dist-upgrade

made.

Last edited by unklar (2017-06-11 08:59:44)

DeepDayze · 2017-06-11 14:18:35

stevep wrote:

If you forwardport 1.9.1 (which means rebuild from source), the way to have it be seen as a higher version than 1.10 without the pinning hassle is to add or increment the epoch, which is a number added to the start of the version. So in debian/changelog:
conky (1:1.9.1-1)
will be handled as a higher version than
conky (1.10.0-1)

So that's a good plan, and if user already has 1.10 installed should be able to "downgrade" it with that hypothetical 1:1.9.1-1 package easily with just apt-get install?

Head_on_a_Stick · 2017-06-11 14:43:21

DeepDayze wrote:

if user already has 1.10 installed should be able to "downgrade" it with that hypothetical 1:1.9.1-1 package easily with just apt-get install?

Actually, APT will see the version with the epoch as "newer" so an upgrade command should do the trick:

sudo apt edit-sources # add repository and save file
sudo apt update
sudo apt upgrade

DeepDayze · 2017-06-11 15:46:55

Sounds good will try it. I have some old-style conky configs lying around as well.

Last edited by Head_on_a_Stick (2017-06-11 16:21:22)

Sector11 · 2017-06-11 17:28:13

unklar wrote:

I have run here on three machines 5 siduction versions.
Of it is installed in 4 conky1.9 and in Plasma5 runs conky1.10
{snip}
At least 1 time a week
apt update && apt dist-upgrade
made.

In the machines with v1.9.0 conky try this:

apt-mark showhold

does conky show as being held?
if Yes ...

sudo apt-mark unhold conky-all

and:

apt update && apt dist-upgrade

unklar · 2017-06-12 08:25:51

^ I have, my dear.
Otherwise I would not have written it.

#21 2017-01-19 14:42:48

Re: conky v1.9.0-6 vs conky v1.10+

#22 2017-01-19 20:22:00

Re: conky v1.9.0-6 vs conky v1.10+

#23 2017-01-19 20:35:21

Re: conky v1.9.0-6 vs conky v1.10+

#24 2017-01-19 20:51:19

Re: conky v1.9.0-6 vs conky v1.10+

#25 2017-01-19 21:44:02

Re: conky v1.9.0-6 vs conky v1.10+

#26 2017-01-26 20:27:13

Re: conky v1.9.0-6 vs conky v1.10+

#27 2017-01-26 20:56:38

Re: conky v1.9.0-6 vs conky v1.10+

#28 2017-01-26 22:11:48

Re: conky v1.9.0-6 vs conky v1.10+

#29 2017-01-27 07:33:11

Re: conky v1.9.0-6 vs conky v1.10+

#30 2017-01-27 08:53:23

Re: conky v1.9.0-6 vs conky v1.10+

#31 2017-01-27 08:58:01

Re: conky v1.9.0-6 vs conky v1.10+

#32 2017-01-30 09:45:54

Re: conky v1.9.0-6 vs conky v1.10+

#33 2017-06-10 22:43:59

Re: conky v1.9.0-6 vs conky v1.10+

#34 2017-06-10 23:52:58

Re: conky v1.9.0-6 vs conky v1.10+

#35 2017-06-11 08:41:14

Re: conky v1.9.0-6 vs conky v1.10+

#36 2017-06-11 14:18:35

Re: conky v1.9.0-6 vs conky v1.10+

#37 2017-06-11 14:43:21

Re: conky v1.9.0-6 vs conky v1.10+

#38 2017-06-11 15:46:55

Re: conky v1.9.0-6 vs conky v1.10+

#39 2017-06-11 17:28:13

Re: conky v1.9.0-6 vs conky v1.10+

#40 2017-06-12 08:25:51

Re: conky v1.9.0-6 vs conky v1.10+

Board footer