Hi, thanks for your answers. There is not really such big of a problem with going back to -current. There just seems to be a bug with the current version of rspamd's milter. Where it bounces alot of messages "warning: milter unix:public/rspamd_proxy.sock: can't read SMFIC_BODYEOB reply packet header: Undefined error: 0". This problem seems to only exist with the package in current and not in release. Therefore my wish to return.
But well okay. I'll try to recover from the pile of **** I created. Thank you so much for your help. I appreciate it! Have a nice day. // Niav > Gesendet: Sonntag, 29. Dezember 2019 um 18:38 Uhr > Von: "Ingo Schwarze" <schwa...@usta.de> > An: n...@web.de > Cc: misc@openbsd.org > Betreff: Re: Going back to release from current installation p > > Hi, > > n...@web.de wrote on Sun, Dec 29, 2019 at 10:41:47AM +0100: > > > I have done the mistake to go back to release from current. > > I thought I'd just reinstall installed packages. > > But it doesn't work that way. > > I do receive error messages like the following for rspamd: > > > > pkg_add: Unknown element: @so lib/rspamd/librspamd-actrie.so > > in /var/db/pkg/rspamd-2.2/+CONTENTS, > > > > This error message is the response to me doing: "pkg_add -r". > > > > The same happens on deletion. Is there a way to fix this ? > > None of this is supported, but if you simply upgrade to the newest > -current snapshot using the normal process, then run "pkg_add -u" > after that, your machine will likely be back in working order. > That may not always work, but i see no particular reason why it > should break at the current point in time. > > If it is a mission-critical machine where errors might have dire > consequences, if there is a risk that you damaged more than you > said here, or if you simply want to make really sure all is fine, > simply follow the supported and recommended process and reinstall > from scratch. > > Yours, > Ingo >
