Oh that is brilliant – i am seriously impressed. Of course i revere 42 & to my probable embarrassment have incorporated it in many small ways into my everyday life for many years]. However, in the decades since my university days i have grown progressively sadder to find fewer & fewer places where / people who “got” my myriad casual insertions of key phrases & concepts into otherwise vanilla conversations. Much more recently, since i first heard of openSUSE, & then learned the bifurcation of Leap & Tumbleweed, i was frequently puzzled by Leap’s 42… but never dared to believe it might have an origin as you’ve now advised. Such happy news! I mean, really - a nice OS and an associated community that understands The Total Perspective Vortex, Vogon poetry & The Infinite Improbability Drive, not to mention why you should be really scared if you ever find yourself materialising inside a super-chic spaceship that’s all black, including black buttons & black screens with black writing on a black background…
Maybe i’m home [if only i can come to grips with repo management & package installations sans mass destruction].**
Thanks Malcolm. I have a Leap VM, as well as a couple of TW VMs, which i created on my Maui Tower a month or two ago to play with & start my learning about openSUSE & out of that experience i pretty much fell in love with TW, to the extent i later opted to replace Maui with it on my Laptop… the machine to which this current thread pertains].
Why not Leap for me? This question is still being debated in my own head, but so far i’ve still not surmounted these self-arguments against it:
My Maui 17.03 uses Plasma 5.9.3, i have already played with 5.10.2 in KDE Neon, & simply love 5.10.2 which is now 5.10.3 in TW. Maui imminently will release 17.06, which will have Plasma 5.10.x i believe. I’m just unwilling to go back to any distro with a pre-5.10.x version, as some of its newer features & functions definitely enhance my workflow & general user-experience enjoyment. I used to be a “devout” Mint KDE user for three years, but left them & went looking for better last year when they chose [in the change from KDE4 to 5] to stay with really old Plasma5 versions. Even the freshly released Mint 18.2 KDE still only has Plasma 5.8.7. Hence Leap’s 5.8.6 is a very
unappealing prospect to me. 1. I do like having later rather than older package versions. Eg, LibreOffice
in Maui currently is 5.3.3.2, in TW is 5.4.0.1, but in Leap is only 5.2.5.1 – LO 5.3 was a major release with many important fixes & new features, including MUFFIN [aka Ribbon UI]. Prior to 5.3 i hated LO, avoided it like the plague, not only for its UI but for the very poor way it handled my multitude of legacy MS Office 2010 files. Come 5.3, i utterly reversed my previous dislike of it, to the extent that it became & remains my default Office suite, & i think it’s quite wonderful. It [5.3 & onward] performs vastly better for me than any older version ever did. Going back “down” to Leap’s 5.2.x is just unthinkable. 1. Having read in various forum posts here that some people “option up” their Leaps by adding various repos like KDE, Applications & Qt, in order to also get newer Plasma stuff, i have given this much thought. Eventually i declined, on the basis that (a) i’d probably be setting myself up for a whole new dimension of repo/package/version debacles that i’d struggle to manage, & (b) what’s really the point of that? If i want the latest stuff, why not just use TW?
My choices will doubtless seem silly to some, but i hope at least the logic is to some extent defensible.
Hi
Well there is a LibreOffice 5.3 repo for 42.2 and 42.3. Again your choice, just have to understand the possible issues with either, chances are potentially higher with Tumbleweed…
I’m sure the Forum KDE gurus will advise on the desktop side (that’s not me…I use GNOME).
IME running TW is the better option compared to Leap+LO+KDE repos. The days where TW was exiting because you knew things would break, just not when, have long gone. If you consider it from a QA perspective: TW is tested and accepted before release, Leap likewise, Leap+repo+repo+repo is not. Re. stability I can’t say Leap is better than TW or vice versa.
I’ve finished licking my wounds & am now trying again to make progress. As a result of the Snapper Roll-back i did several nights ago, a couple of non-standard packages i had already installed psensor & recoll], are no longer present *. For now i’m focusing on psensor.
I now downloaded your RPM [not retrying the One Click, as per your advice] for it from openSUSE Software, then attempted to install it via CLI, but failed due to the error per below [commonplace result i have already received many times before for other packages, & i still don’t understand how i can possibly get the keys except by directly asking each person]:
linux-763v:~/Downloads> sudo zypper in psensor-1.1.5-1.26.x86_64.rpm
[sudo] password for root:
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 6 NEW packages are going to be installed:
hddtemp libappindicator3-1 libdbusmenu-gtk3-4 libindicator3-7 libjson-c2 psensor
The following recommended package was automatically selected:
hddtemp
6 new packages to install.
Overall download size: 263.2 KiB. Already cached: 214.0 KiB. After the operation, additional 1.7 MiB
will be used.
**Continue? [y/n/...? shows all options] (y): **
In cache hddtemp-0.3_beta15_e16aed6-3.2.x86_64.rpm (1/6), 51.9 KiB (119.5 KiB unpacked)
In cache libdbusmenu-gtk3-4-16.04.0-1.3.x86_64.rpm (2/6), 53.0 KiB (152.4 KiB unpacked)
In cache libindicator3-7-12.10.2+bzr20151208-1.6.x86_64.rpm (3/6), 42.9 KiB (106.8 KiB unpacked)
In cache libjson-c2-0.12.1-2.2.x86_64.rpm (4/6), 29.9 KiB ( 44.5 KiB unpacked)
In cache libappindicator3-1-12.10.1+bzr20170215-1.2.x86_64.rpm (5/6), 36.2 KiB ( 88.6 KiB unpacked)
Retrieving package psensor-1.1.5-1.26.x86_64 (6/6), 263.2 KiB ( 1.2 MiB unpacked)
psensor-1.1.5-1.26.x86_64.rpm:
Header V3 RSA/SHA256 Signature, key ID 97090d5e: NOKEY
V3 RSA/SHA256 Signature, key ID 97090d5e: NOKEY
psensor-1.1.5-1.26.x86_64 (Plain RPM files cache): Signature verification failed [4-Signatures public key is not available]
**Abort, retry, ignore? [a/r/i] (a): **
You had earlier told me:
Download the rpm’s and create a local rpm repo, or use zypper in <url_to_rpm> likewise add verbosity with -vvv so you can see what the system is going to do.
…but i’m afraid i don’t really understand how to comply with this.
As per recent advice in this thread from Knurpht, https://forums.opensuse.org/showthread.php/525748-Apparent-Catastrophe?p=2828624#post2828624, i shall now try this request out on you as my first test-case… would you be willing pls to submit your psensor package to Tumbleweed, so that in future amateurs like me can simply get it from the standard TW repos & not have this current error / challenge?*
As to psensor, probably not, as I would have to also look at maintaining things like libXNVCtrl (aside from getting through the legal folks) which would also need pushing…
There is nothing stopping someone grabbing it to look after and submit…
don’t add (packages from) home: and devel: repos. Things in there are breaking all the time because it’s the place where they should break
Because i have had so much hassle & confusion with my incompetent mismanagement of repos initially, i have tried to pay careful attention to all the various bits of advice i’ve subsequently received from everyone here in these fora, since i started asking for help.
Without in any way wishing to offend you, considering that quotation above, & considering your:
…am i silly in supposing that this is possibly one or both of “home: and devel: repos”, or are they something completely different, & hence i should stop worrying? :shame:
Well, anyway, i’ve done it now, via personal repo creation & manual key download as you earlier suggested, & Karl kindly explained [re the repo]. What a great idea creating my own local repo is – very cool
As well as using your psensor repo, after getting a memory jogger from another, older, thread in the fora, i also installed sensors via zypper, then ran
sudo sensors-detect
.
Now, psensor is working a treat on Lappy, just as nicely as it used to when Lappy still ran Maui. Excellent.
Oh wow, that’s nice. Now that i’ve seen the explanation, retrospectively the concept of my own local repo is embarrassingly simple, but i couldn’t grasp it earlier. I found this slightly comical / alarming:
Warning: Requested more delta workers than workers. This is insane. Limiting.
Anyway, i was going to also do it via Konsole, but had the idea to see if the YaST GUI also would let me, & i saw it would, so that’s how i did it. Furthermore, unlike you, i chose to fetch Malcolm’s repo’s key & manually import it into YaST, prior to doing [in YaST2] the actual installation of psensor. This time it all went like clockwork.
I’m really pleased with this local repo idea, & so i plan to substitute it for all the individual non-standard repos i currently have [albeit disabled] in YaST - one by one i’ll determine which individual non-std pgm i downloaded & installed from each of these non-std repos, download [if available] the rpm file, store it in my local repo “for future usage” in case i need to do any fresh installation for any reason, & then fully remove each non-std repo from YaST. I am hoping - fingers crossed - that this methodology will/might prevent me creating any more future ugly repo/dependency/version conflicts that’s been the only Big Downer for me so far since i recently began my adventures in openSUSE-land.
Recoll is an important pgm for me on my Maui Tower, & if my TW “real life” testing still underway on my Lappy is to lead me eventually to decide that i also wish to migrate Tower to TW, then i need to one way or another get Recoll installed, without wrecking my system again.
From openSUSE Software for Tumbleweed there’s actually three repos shown from which i could get recoll, although realistically the third looks unattractive due to being a quite old version. I assume that the first “KDE:Extra”] is an official or semi-official oS repo… would it be thus safe for me to use for the rpm download? The second repo “home:Lazy_Kent”] sounds entirely unofficial; how can a newbie like me ascertain its safety [the name though amusing is not exactly confidence-inspiring]? Furthermore, is that one of the “home:”-type repos that Knurpht warned me away from?
You’re getting there. The KDE:Extra repo could be called semi-official, I use it for a couple of KDE apps ( f.e. luckybackup ). To enable it and install recoll:
zypper ar -f -n KDEextra http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Tumbleweed/ KDEextra
zypper ref
zypper in recoll
, you will be asked to trust the key, I set it to Always.
Ha, thanks so much! I don’t want to actually say out loud that i am slowly beginning to feel less out of control now with my repo management, because such arrogance would likely instantly cause my TW to implode… but it really is feeling somewhat less terrifying than before… rotfl!
You use KDE:Extra for LB - how ironic; when i installed LB a week or two ago, for reasons i can’t now recall or explain, i chose not to use that repo, but instead your one: home:Knurpht:Extras.
FYI: I used to use LB as my default backup tool [in Maui], but changed from it to BackInTime a couple of months ago once i discovered it & decided i like it even more. Have you tried that one? It’s now also installed in my Lappy’s TW.
PS: Would i be correct in assuming that whilst you use KDE:Extra to install those pgms, once installed you Disable this repo?
Following the advances made in rationalising my repos per the recent posts in this thread, i’ve now removed all but 2 of the non-standard repos from YaST2. The 2 remaining & Disabled] non-std ones are:
openSUSE:Tumbleweed
openSUSE:Factory
I briefly re-enabled them one at a time, so as to try to see what specific non-std pgms i had installed over the past ~month from them. However, there’s many dozens, if not hundreds, of pgms / packages listed for each of these two. Looking at many of them at random, it seems to be that lots of packages are actually from the Main Repository [OSS], but also from one or other of these two… what a mess i created!
Is there an efficient way i can “return” all relevant packages to the standard repos [without me once again blowing up my TW], which would then leave truly ONLY the one or two * pgms i did install from these two non-std repos clearly visible… eg, so that when i look in YaST2 at the package list under #1 above, i see one or two pgms not dozens/hundreds? Then i can easily decide what i want to do with those pgms, thereafter deleting both these non-std repos. As it is now, i can’t see these pgms amongst all the “noise” created by all the others also listed.*
Use home repos to get things that may not be in the regular ones but don’t leave them active since you generally don’t know what else is in there that may conflict
Factory is not enabled, but as i said, i’d like to actually remove it, & the other non-std one too, once i can ascertain what 1, 2 or 3 pgms i had installed from both these repos.
