Date: Sat, 8 Oct 2022 08:35:39 -0700 From: paul beard <paulbeard@gmail.com> To: FreeBSD-questions <freebsd-questions@freebsd.org> Subject: pkg upgrade vs building from source Message-ID: <CAMtcK2rPSxd0DignXvzw%2BnNc1U1iYpBjGpN%2BtqA4zevUO4qkQA@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
--0000000000005ff55f05ea87ae0e Content-Type: text/plain; charset="UTF-8" My skepticism over pkg doing what I expect grows after recent events. I decided after I rebuilt this freebsd instance that I would say goodbye to installing from source and allow pkg to manage it all. Surely by now, it's mature enough to handle it. Reader, it is not. I allowed it to upgrade postfix the other day and discovered that it no longer worked; Oct 8 03:15:16 <mail.warn> www postfix/smtp[65148]: warning: unsupported SASL client implementation: cyrus Oct 8 03:15:16 <mail.crit> www postfix/smtp[65148]: fatal: SASL library initialization Oct 8 03:15:17 <mail.warn> www postfix/master[1157]: warning: process /usr/local/libexec/postfix/smtp pid 65148 exit status 1 Oct 8 03:15:17 <mail.warn> www postfix/master[1157]: warning: /usr/local/libexec/postfix/smtp: bad command startup -- throttling I went to the port directory and did a deinstall/reinstall and all is well. Postfix flush cleared out the test emails I had queued up and no errors in maillog. No changes to teh configuration files, it just worked properly after a proper install. I can obviously issue pkg lock against postfix to ensure it's left alone but I have to wonder how many other ports are similarly not ready for prime time after pkg gets involved? One of the reasons I tried freebsd, all the way back to release 4.11, is that rpm in the linux world was a massive pile of inconsistency. The ports system was so coherent and well managed: I preferred the cathedral to the bazaar, as a book of the period described that time. I suppose not trusting pkg with ports you rely on seems reasonable but with dependencies and whatnot, how to decide? Should pkg include some more robust testing to ensure services are actually running after upgrade? I don't know if it could but I suppose the maintainer could devise some tests, looking at logfiles or whatnot. All in all, not how I expected to spend a half hour on Saturday morning. How do other people manage this? -- Paul Beard / www.paulbeard.org/ --0000000000005ff55f05ea87ae0e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">My skepticism over pkg doing what I expect grows after rec= ent events. I decided after I rebuilt this freebsd instance that I would sa= y goodbye to installing from source and allow pkg to manage it all. Surely = by now, it's mature enough to handle it. <br><br>Reader, it is not.=C2= =A0<div><br></div><div>I allowed it to upgrade postfix the other day and di= scovered that it no longer worked; <br>Oct =C2=A08 03:15:16 <mail.warn&g= t; www postfix/smtp[65148]: warning: unsupported SASL client implementation= : cyrus<br>Oct =C2=A08 03:15:16 <mail.crit> www postfix/smtp[65148]: = fatal: SASL library initialization<br>Oct =C2=A08 03:15:17 <mail.warn>= ; www postfix/master[1157]: warning: process /usr/local/libexec/postfix/smt= p pid 65148 exit status 1<br>Oct =C2=A08 03:15:17 <mail.warn> www pos= tfix/master[1157]: warning: /usr/local/libexec/postfix/smtp: bad command st= artup -- throttling<div><br></div><div>I went to the port directory and did= a deinstall/reinstall and all is well. Postfix flush cleared out the test = emails I had queued up and no errors in maillog. No changes to teh configur= ation files, it just worked properly after a proper install.=C2=A0</div><di= v><br></div><div>I can obviously=C2=A0issue pkg lock against=C2=A0postfix t= o ensure it's left alone but I have to wonder how many other ports are = similarly not ready for prime time after pkg gets involved? One of the reas= ons I tried freebsd, all the way back to release 4.11, is that rpm in the l= inux world was a massive pile of inconsistency. The ports system was so coh= erent and well managed: I preferred the cathedral to the bazaar, as a book = of the period described that time.=C2=A0</div><div><br></div><div>I suppose= not trusting pkg with ports you rely on seems reasonable but with dependen= cies and whatnot, how to decide? Should pkg include some more robust testin= g to ensure services are actually running after upgrade? I don't know i= f it could but I suppose the maintainer could devise some tests, looking at= logfiles=C2=A0or whatnot.=C2=A0</div><div><br></div><div>All in all, not h= ow I expected to spend a half hour on Saturday morning. How do other people= manage this?=C2=A0</div><div><br></div><div><br></div><div><br>--<br>Paul = Beard / <a href=3D"http://www.paulbeard.org/">www.paulbeard.org/</a></div><= /div></div> --0000000000005ff55f05ea87ae0e--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMtcK2rPSxd0DignXvzw%2BnNc1U1iYpBjGpN%2BtqA4zevUO4qkQA>