Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 8 Oct 2022 13:18:28 -0700
From:      paul beard <paulbeard@gmail.com>
To:        Graham Perrin <grahamperrin@freebsd.org>
Cc:        questions@freebsd.org
Subject:   Re: pkg upgrade vs building from source
Message-ID:  <CAMtcK2rp2JLHpWJbQHv1DQBB8MS3=ro9hbJF0orUEK3rqJ5xLw@mail.gmail.com>
In-Reply-To: <e4544587-50bb-55e8-3284-58a76b3a69f7@freebsd.org>
References:  <CAMtcK2rPSxd0DignXvzw%2BnNc1U1iYpBjGpN%2BtqA4zevUO4qkQA@mail.gmail.com> <e4544587-50bb-55e8-3284-58a76b3a69f7@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000cd8a0405ea8ba10b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>
> Which version of FreeBSD, exactly?
>

FreeBSD www.paulbeard.org 12.3-RELEASE FreeBSD 12.3-RELEASE r371126 GENERIC
 i386


> Packages from latest, or quarterly?
>

Hm=E2=80=A6whatever pkg update pulls

freebsd-version -kru ; uname -aKU
>
See above.

pkg -vv | grep -e url -e enabled -e priority


pkg -vv | grep -e url -e enabled -e priority

    url             : "pkg+http://pkg.FreeBSD.org/FreeBSD:12:i386/quarterly
",
    enabled         : yes,
    priority        : 0,


On Sat, Oct 8, 2022 at 11:12 AM Graham Perrin <grahamperrin@freebsd.org>
wrote:

> On 08/10/2022 16:35, paul beard wrote:
>
> 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 pri=
me
> 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 pi=
le
> 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 mor=
e
> 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/
>
>
> Which version of FreeBSD, exactly?
>
> Packages from latest, or quarterly?
>
> freebsd-version -kru ; uname -aKU
>
> pkg -vv | grep -e url -e enabled -e priority
>


--=20
Paul Beard / www.paulbeard.org/

--000000000000cd8a0405ea8ba10b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex">Which version of FreeBSD, exactly?<span c=
lass=3D"gmail-Apple-converted-space">=C2=A0<br></span></blockquote><div>=C2=
=A0</div>FreeBSD <a href=3D"http://www.paulbeard.org">www.paulbeard.org</a>=
 12.3-RELEASE FreeBSD 12.3-RELEASE r371126 GENERIC =C2=A0i386<br><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,2=
04,204);padding-left:1ex"><span class=3D"gmail-Apple-converted-space"></spa=
n>Packages from latest, or quarterly?<span class=3D"gmail-Apple-converted-s=
pace">=C2=A0<br></span></blockquote><div><br></div><div>Hm=E2=80=A6whatever=
 pkg update pulls =C2=A0</div><div><br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-sty=
le:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span class=
=3D"gmail-Apple-converted-space"></span>freebsd-version -kru ; uname -aKU<b=
r></blockquote><div>See above. =C2=A0</div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">=
pkg -vv | grep -e url -e enabled -e priority</blockquote><div><br></div>pkg=
 -vv | grep -e url -e enabled -e priority<div><br>=C2=A0 =C2=A0 url =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : &quot;pkg+<a href=3D"http://pkg.FreeBS=
D.org/FreeBSD:12:i386/quarterly">http://pkg.FreeBSD.org/FreeBSD:12:i386/qua=
rterly</a>&quot;,<br>=C2=A0 =C2=A0 enabled =C2=A0 =C2=A0 =C2=A0 =C2=A0 : ye=
s,<br>=C2=A0 =C2=A0 priority =C2=A0 =C2=A0 =C2=A0 =C2=A0: 0,<br><div>=C2=A0=
</div></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"=
gmail_attr">On Sat, Oct 8, 2022 at 11:12 AM Graham Perrin &lt;<a href=3D"ma=
ilto:grahamperrin@freebsd.org">grahamperrin@freebsd.org</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,2=
04);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <div>On 08/10/2022 16:35, paul beard wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">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&#39;s mature enough t=
o
        handle it. <br>
        <br>
        Reader, it is not.=C2=A0
        <div><br>
        </div>
        <div>I allowed it to upgrade postfix the other day and
          discovered that it no longer worked; <br>
          Oct =C2=A08 03:15:16 &lt;mail.warn&gt; www postfix/smtp[65148]:
          warning: unsupported SASL client implementation: cyrus<br>
          Oct =C2=A08 03:15:16 &lt;mail.crit&gt; www postfix/smtp[65148]:
          fatal: SASL library initialization<br>
          Oct =C2=A08 03:15:17 &lt;mail.warn&gt; www postfix/master[1157]:
          warning: process /usr/local/libexec/postfix/smtp pid 65148
          exit status 1<br>
          Oct =C2=A08 03:15:17 &lt;mail.warn&gt; www postfix/master[1157]:
          warning: /usr/local/libexec/postfix/smtp: bad command startup
          -- 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 configuration files, it just
            worked properly after a proper install.=C2=A0</div>
          <div><br>
          </div>
          <div>I can obviously=C2=A0issue pkg lock against=C2=A0postfix to =
ensure
            it&#39;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.=C2=A0</div=
>
          <div><br>
          </div>
          <div>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&#39;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 how 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/" target=3D"_b=
lank">www.paulbeard.org/</a></div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>Which version of FreeBSD, exactly? <br>
    </p>
    <p>Packages from latest, or quarterly? <br>
    </p>
    <p>freebsd-version -kru ; uname -aKU</p>
    <p>pkg -vv | grep -e url -e enabled -e priority<br>
    </p>
  </div>
  <u></u><u></u>

</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature">Paul Beard / <a href=3D"http://www.paulbeard.org=
/" target=3D"_blank">www.paulbeard.org/</a><br></div>

--000000000000cd8a0405ea8ba10b--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMtcK2rp2JLHpWJbQHv1DQBB8MS3=ro9hbJF0orUEK3rqJ5xLw>