I just went to install Digikam.
YaST suggested the install size was about 16MB.
Then to satisfy dependencies (most of which seemed to be slight version differences of existing packages) it downloaded about 350MB.
Is this a function of rpms?
I never used to have this sort of issue when I was running debian based systems.
On 2010-12-07 00:06, opticyclic wrote:
>
> I just went to install Digikam.
> YaST suggested the install size was about 16MB.
> Then to satisfy dependencies (most of which seemed to be slight version
> differences of existing packages) it downloaded about 350MB.
>
> Is this a function of rpms?
> I never used to have this sort of issue when I was running debian based
> systems.
Hypothesis: that you had not updated the system before, and those were
delayed updates. Or your repo configuration and the digikam version you
chose triggered those packages.
It is possible to know that by analyzing the proposed install.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
# | Alias | Name | Enabled | Refresh
---+----------------------+-----------------------+---------+--------
1 | KDE:Distro:Factory | KDE:Distro:Factory | Yes | No
2 | Libdvdcss repository | Libdvdcss repository | Yes | No
3 | NVIDIA Repository | NVIDIA Repository | Yes | No
4 | Packman Repository | Packman Repository | Yes | No
5 | WineDev | WineDev | Yes | No
6 | packman | packman | Yes | No
7 | repo-debug | openSUSE-11.3-Debug | No | No
8 | repo-non-oss | openSUSE-11.3-Non-Oss | Yes | No
9 | repo-oss | openSUSE-11.3-Oss | Yes | No
10 | repo-source | openSUSE-11.3-Source | No | No
11 | repo-update | openSUSE-11.3-Update | Yes | No
I have set YaST to manually update so that it starts quicker, but that was only done on Nov 21st and I have done updates since then.
Its a bit of a mute point at the moment anyway, because on restarting after installing DigiKam, KDE is segfaulting and the only way to log in is via IceWM.
I couldn’t work out how to access the network from IceWM (the KDE network settings kept crashing) so I just reinstalled 11.3
I have a separation of system and data so it was a relatively clean process.
However, these are the enabled repositories after a fresh install
If factory is such a beta area likely to cause problems, why is it enabled by default?
Surely packman is what we want enabled in the default installation, right?
> If factory is such a beta area likely to cause problems, why is it
> enabled by default?
That can not be so. You must have done something to enable it. The only
default repos are oss, non-oss, dvd, updates, and source and debug (both
disabled).
If you are sure you didn’t enable them, it could be a feature of the
installation reading settings. I know a new install on top of another read
the fstab and the user list, and recreates those settings in the new
install. I’m not aware that it reads the list of repos, but perhaps it is a
new feature in 11.3. Anybody knows if this guess is correct?
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Well, Factory was enabled previously but surely reformatting as part of the install would have wiped out any previous settings.
Otherwise there is a serious problem with the installer.
opticyclic wrote:
> Well, Factory was enabled previously but surely reformatting as part of
> the install would have wiped out any previous settings.
> Otherwise there is a serious problem with the installer.
if you did all of those things and during install you accepted the default application suites and didn’t fiddle with the repos selected for the install and had no errors during install and and after install
added zero software via a “1-Click”
did not change any repo settings via YaST or zypper
but you still got that list of repos, then you machine is filled
with evil spirits…you probably should hire a professional exorcist
before beginning again…
On 2010-12-11 06:36, caf4926 wrote:
>
> opticyclic;2264657 Wrote:
>> Well, Factory was enabled previously but surely reformatting as part of
>> the install would have wiped out any previous settings.
>> Otherwise there is a serious problem with the installer.
The partition is reformatted, but some settings, like the list of users and
passwords, are saved to memory then rewritten to the new system. This is a
known feature.
> If you were performing a New install and formatted /
> No way you get factory
That’s my belief, but perhaps there is a new feature we don’t know about?
Is that possible?
Else, it is Merlin’s doings. :-p
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
I couldn’t afford a professional exorcist but I managed to get hold of OpenExorcism which seems to have done the trick.
It cleared all assumptions enabling me to look at the system info on the LiveCD.
I noticed that it was KDE4.5, which prompted me to check what isos I still had.
openSUSE-11.3-KDE4-LiveCD-i686.iso
AND
KDE-Four-Live.i686-4.5.0-Build7.16.iso
The CD probably has the latter on it, which probably has factory as part of the install in order to get 4.5.
Just booted from 11.3 x86_64 LiveCD (downloaded in july/2010) and the preconfigured repos are Oss, Non-Oss and update. Perhaps there is a later release (like 11.1 LiveCD had a “reloaded KDE” version)?
opticyclic wrote:
> The CD probably has the latter on it, which probably has factory as
> part of the install in order to get 4.5.
yep…
that makes sense…
and when you work outside of the regular distro release, you always
take a chance that you will shoot yourself in the foot…lots and
lots of ways to do that…
if you use factory, you need to know what you do, why and when…