Hi
I’ve someone asking this in the forum, but I can’t find in the search.
This was happening in 13.2 too.
Every time, I have a external hdd plug, yast warns me ( upon some package installation), about running out of space in that hdd.
Not sure why, Yast wants to install it on that hdd.
This doesn’t happen with zypper. Just Yast or the ( software installer ? )
Not sure if there is a fix to this, and not sure what happens, if I would click to proceed.
Thanks for the reply
Curiously enough, I’ve reinstall opensuse, and I made some installations through Yast with my external hdd plugged, and it did not happen…
But it was happening, in 13.2, and when I posted .
If it happens again, I’ll try to paste a screenshot, and that info.
Does not make sense unless you booted from that external/ RPM installs all go to root partition unless you have added additional partition in an odd way
That does seem to be an odd message, but based on the file name it might have something to do with mounting the external USB3 device and not actually trying to install a file at that location (but I can’t know for sure since I’m not sure what libsass is doing with the external device). Also, You might notice that the that the filename itself contains a backslash not followed by a character to be escaped, which I’m not sure what would be the consequence.
What might happen if you try to delete possibly corrupt file (or reboot since /run in mounted as tempfs)
For example, in a root console
rm -r /run/media/daniel/*
Reading up a bit on what libsass is, it appears that originally it was written in Ruby, but people thought so much of it that it was ported to C/C++ as “libsass” so that it could be wrapped for use in other languages.
This suggests that although you’d probably still need to compile on your own for latest features and functionality (as of today, latest git contrib was 2 mths ago), you’d likely be able to get a “wrapped” libsass ready to go for the specific language you are developing in. If openSUSE isn’t providing latest, there is a pretty good likelihood it’s already available in the official repos for whatever language you are using (ie python = pip, ruby = gem, node = npm, etc). If you want to explore the official repos for your language, I’ve done some writeups how to setup for Ruby and Nodejs at the following wiki pages. A similar approach should be implemented for python using virtualenv.
Thanks
I don’t think this is related to the libsass. It already happen in 13.2
I’ll be changing the name for something with no spaces, but no sure if the mlabel formats or not the drive, and I have a lot of stuff that I can’t loose, so I’ll be cautious, hum…maybe doing it in windows ?rotfl!
But , what’s strange, it’s that only happens sometimes.
I’ll be changing the name, and then post the results.
only to confirm, in my
PC=Dell latitude E6510, RAM=8Gb, GPU=GT218 NVS 3100M, CPU=i7 Q 720 @ 1.60GHz, OS=opensuse 13.2 KDE= 4.14.9
happen the same error, if I answer yes it continue without (it seems) problems
my disk is without spaces in
/run/media/user/backup4/
and it is ext3 filesystem
manythanks ciao pier