It might not matter for your problem, but I do not se how you can use zypper dup to make a distro up to date. You use zypper dup to change products to another vendor repo which has newer versions of packages. You do that e.g. when you go from one level of openSUSE to the next. But to have the newest versions of the repos on your system of the packages you installed, you use zypper up. zypper dup can bork what you have (e.g switch back part of your multi media setup to OSS away from Packman).
I was instructed to prefere zypper dup against zypper up, but I have to say I have difficulties to sort the various zypper update processes (du, up, patch…). I have read many things but still not very clear for me.
I do not have filtering on the server (not that I know of :-(), and I don’t see why this should only impact my account and not other people account. May it be some local account setup ? local quota? postfix limit?
in main.cf, message_size_limit = 10000000
to not lose messages, I just added (after I posted the first message here) an dalias to an external mail account I have also and there the messages come complete.
my personal account is only 5Gb and /home have 30Gb available.
I forgot to add an important thing. Since I updated locally (not the server) with 12.2, I get error messages in thunderbird. Stranges messages.
to be complete, before having fully empty messages, I had duplicated messages (one normal, the other empty safe the visible header part).
First error message said “not found”, then from time to time “what is the good one, left or right” and shows two messages. No idea what, but that it may be the duplicate.
So, may be any application part of the process may have taken strong mesure to stop this :-(. imap is dovecot. I don’t see where this could have been stored
Am 08.09.2012 13:36, schrieb jdd:
> I was instructed to prefere zypper dup against zypper up,
Can you give us a link where you have instructed to use dup? So that we
can see and understand the context of this advise.
As Henk told you in general this has a high risk of borking your system
if you have not only the standard repositories (and almost nobody has
only oss, non-oss and update, at least packman is enabled by most people
and often more in addition).
–
PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
On 09/08/12 08:22, Martin Helm pecked at the keyboard and wrote:
> Am 08.09.2012 13:36, schrieb jdd:
>> I was instructed to prefere zypper dup against zypper up,
> Can you give us a link where you have instructed to use dup? So that we
> can see and understand the context of this advise.
> As Henk told you in general this has a high risk of borking your system
> if you have not only the standard repositories (and almost nobody has
> only oss, non-oss and update, at least packman is enabled by most people
> and often more in addition).
>
Oh please! If one has the priorities set properly for their repos that
won’t happen. I always use zypper dup and never have problems with my
systems being “borked”.
SDB:Zypper usage 11.3 - openSUSE
if you ever add a new repo, zypper up wont update with this one, zypper dup do. It’s what I understand. By the way my server have a limited number of repositories (including packman, sure :-(). and change are unfrequent in this part.
by the way, I moved all my INBOX content to archive and this seemed to fix the problem. I have contents again. probably some qirk with the mailbox content.
Am 08.09.2012 14:40, schrieb Ken Schneider:
> Oh please! If one has the priorities set properly for their repos that
> won’t happen. I always use zypper dup and never have problems with my
> systems being “borked”.
That will not work in general, it may work for you and your special needs.
Working with repository priorities is a very coarse way of dealing with
packages. My mileage varies in that I need the packages which I decided
to be from a specific vendor stay with that vendor and that is what
“zypper up” is designed for and works.
“zypper dup” is simply designed for a completely different use case,
while you might be able to trick it into what you like (to disallow
vendor change for example) I see no point in doing so when the right
option is available separately.
–
PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
Am 08.09.2012 15:06, schrieb jdd:
> Hey… I just have a new error message:
You should not just tell us which message you get but also which command
exactly you used to get that message.
It will also help if you post the content of
zypper lr -d
to see what repositories you have and also tell from which repositories
dovecot, postfix, thunderbird are installed respectively.
–
PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
Am 08.09.2012 17:36, schrieb jdd:
> yes I did exactly this and it seem to work this repo:
> Code:
> --------------------
> URL : http://download.opensuse.org/repositories/KDE:/Release:/49/openSUSE_12.2/
> --------------------
> the bug seems to involve any filter on the client thanks
>
>
Thanks for the feedback and confirmation, so after all it was a KDE
issue and there is at least a way to solve it by updating it. Good to know.
–
PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
this repo:
this repo: