Posting this mainly for info as I don’t know yet if this is gonna cause me any major problems
Just ran zypper dup --from Tumbleweed on a freshly installed (from dvd) 11.4 64-bit and got quite a lot of package missing from Tumbleweed Standard messages
They were all LibreOffice packages and gstreamer related packages
I decided to ignore them all and verify with zypper after it had finished running, figuring they would get pulled in later (eventually?) with zypper dup anyway (if I’m lucky that is)
zypper verify returned: Dependencies of all installed packages are satisfied, so it doesn’t look if anything’s broken
Am going to reboot the machine now, then cross my fingers and run zypper dup
Even seems to have fixed whatever was causing akonadi to take forever loading up, which means the desktop is usable on login about 5 times faster now. I hate akonadi sometimes!
Only thing I can see that needs looking at now is when logging out of kde I see a screen full of FIBMAP: INVALID ARGUMENT messages, I’ve no idea what that means and whether it’s any cause for concern as I’ve never seen it before
This isn't new. The FIBMAP ioctl tries to determine the actual block on disk
that a file is using. Most likely it's coming from preload, the tool that
tries to check what things are in use and load them into memory so they will
start quicker on future boots, and it is probably trying to map something that
doesn't support mapping, such as a tmpfs or similar
This message has been around forever. At some point someone should probably
fix the preload code to check to see if the filesystem in question supports
mapping before trying to do it, and just hide the error message
As it’s been around forever I’m surprised I’ve not seen it before, started using opensuse regularly since version 10.2 … maybe I’ve not been paying proper attention lol
From the above looks like it’s more of an annoyance than a problem, could it be that in this particular I have a few ntfs partitions or that it uses nfs for the /home perhaps?
Anyone know if there’s some kind of fix/workaround that might stop them getting displayed?
Bit of a nervy experience there – glad you figured out that the share was blocking the process.
The “zypper dup --from Tumbleweed” policy has concerned me for some time now because the package maintainer has stated that he crafts the Tumbleweed repo contents to work from a simple “zypper dup”. The usage of “–from Tumbleweed” seems to me to be illogical in light of the maintainer’s policy of testing his changes against a plain “zypper dup”. I think I’ll be recommending against the “–from Tumbleweed” qualifier in future.
I think mine would have went a bit sweeter if I’d just used zypper dup in the first place given the files it couldn’t install when adding the from Tumbleweed switch
Installed from the exact same dvd on the exact same machine in exactly the same way, ran updates then proceeded to implement Tumbleweed
The only real difference in the system was that I decided to leaving configuring nis and nfs until later, but those being enabled did only affect one package first time round
This time, using just zypper dup, it didn’t ask me to resolve anything at all, just went straight to the report on how many packages it was going to upgrade etc and asking whether I wanted to continue
Let it run and it went flawlessly, no missing packages or any other errors, so in this instance at least using --from Tumbleweed actually caused problems that don’t appear without it, so with a freshly installed system a plain zypper dup does seem to be cleaner and less problematic
The portal Tumbleewed page does actually say that --from Tumbleweed isn’t supported but is given as a possibly safer method for people with repositories other than oss, non-oss, updates, tumbleweed and tumbleweed packman enabled
It strikes me though that if people follow the instructions they won’t have any other repos enabled when they run zypper dup so that ‘should’ be a moot point
Personally since first trying Tumbleweed I’ve always when needing a package from any other repo installed the package then disabled the repo, temporarily re-enabling anytime I need anything else from it
That way I know that when I run zypper dup only the necessary repos are enabled
Noticed while I was doing this that you took the original how-to sticky down and redid it, nice job, I was gonna post the result of doing it with just zypper dup on there … but it looks so nice and clean I didn’t wanna spoil it
Not sure why you have been so concerned with “zypper dup --from Tumbleweed”. I thought it was only appropriate for the first upgrade to Tumbleweed from the initial 11.4 installation. Thereafter only a plain “zypper dup” is needed, governed by priorities set for enabled repos as required. That’s worked for me ever since our testing/discussion in that other long thread on the subject.
Since your id isn’t “swerdna”, I’m not sure what you are going on about, especially the sarcasm.
BTW, I personally wouldn’t draw any conclusions from your OP, except as stated i.e. you ignored some messages and hoped for the best. Normally, zypper dup tells you what it’s going to do before you agree/not. I didn’t have your problem when I switched to Tumbleweed.
Forgot to add (being honest I accidentally clicked the Submit button without realising when I got up from the desk)
With regards to ignoring the warnings, hoping for the best wasn’t the case, zypper reported it was going to install all those packages but when I told it to carry on and do so it couldn’t find them on the repository, so the choice was to abort it or let it run
I figured aborting it was liable to do as much damage as letting it run, so I let it run, that’s what I meant when I said ignoring it, temporarily ignoring the fact they weren’t found on the repository, a bad choice of words on my part perhaps but then I am welsh and hardly anyone understands us half the time anyway
No hoping for the best was involved and I did in fact have the system running fine and the only reason I reinstalled was that I’d come across a statement about zypper dup --from Tumbleweed being ‘not really supported’ on the Tumbleweed portal page so this being a machine I use for playing around on, I wanted to give it a go without --from Tumbleweed just to see what would happen
Incidentally my noticing that statement and deciding to try it virtually coincided with swerdna’s comment on the very same thing and deciding to change his sticky on the subject
“so concerned”? No, just mildly concerned that I might have been mislead by the OP of the wiki article. Originally they recommended “–from TW”, now they recommend the plain dup. If they’d put the plain dup there from the get go, we would have been better off IMO. Prioritisation of the Tumbleweed repos and the use of “–from TW” is a fine thing for the advanced users, but it’s mostly unnecessary for the rank and file (like me) who just need a working desktop in a straightforward fashion with straightforward maintenance. I haven’t skipped a beat since I put all at priority 99 and only ever run the plain dup. Whereas I have had some interesting rides from using “–from TW”. After saying all of that, I think both approaches are valid. As they say in the books “there are many ways to cook a boot”.
I read that as a one-time only (the first time) exercise.
lol! If counting up to 99 is an “advanced” level ability, I would have to agree with you. I haven’t used “–from TW”, once Tumbleweed was installed, just plain “zypper dup” or sometimes YaST. Packman (for multimedia) at the highest priority repo (e.g. 80) is an obvious one even for standard 11.4, since openSUSE/Tumbleweed has on occasion introduced a higher-level package(s). I then have Tumbleweed at 90, the rest at 99, and haven’t ever needed to change those three priorities since. I haven’t had any problems updating/running Tumbleweed so far, but have enjoyed the improvements included in the latest stable applications.
Whereas I have had some interesting rides from using “–from TW”.
I avoided that complication, and now it seems to be somewhat discredited.
