Re: Going back to release from current installation p
Hi, n...@web.de wrote on Sun, Dec 29, 2019 at 08:40:40PM +0100: > thanks for your answers. There is not really such big of a problem > with going back to -current. Usually, downgrading an OpenBSD installation simply doesn't work at all. As you saw, it typically breaks in one way or another, so don't do it. > There just seems to be a bug with the current version of rspamd's > milter. When you see a bug in -current, going back to -stable is never a good idea. Instead, help to identify the bug and get it fixed. That's the whole point of running -current, after all. > 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. The maintainer of the mail/rspamd port is likely to overlook this report in this thread (given that it is on misc@ and given the Subject:). Besides, this report is extremely brief, i'm not convinced it contains sufficient information to understand the problem. But since i don't use spamd, i'm not sure. The latest commit to the mail/rspamd port was on 2019/12/29 21:35:02. Make sure you have a package built with that commit, and if the problem persists, post a report to ports@ with as much detail as you can. You may also Cc: the maintainer in case of regressions, in this case sthen@. Yours, Ingo
Re: Going back to release from current installation p
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" > 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 >
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
Re: Going back to release from current installation p
> 29. des. 2019 kl. 10:41 skrev n...@web.de: > > Hi, > 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 ? > The recommended approach would be to reinstall, restore your non-system things and any customizations from backup, pkg_add whatever it is you need. In the meantime, pkg_info(1), specifically the -z option might help, do read the man page. All the best, Peter — Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. signature.asc Description: Message signed with OpenPGP
Going back to release from current installation p
Hi, 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 ? I'd be so happy for any help. Best regards, niav
