Skip site navigation (1)Skip section navigation (2) 
Date:      Mon, 18 Sep 2023 19:33:10 +0100
From:      Graham Perrin <grahamperrin@gmail.com>
To:        pkgbase@FreeBSD.org
Subject:   PkgBase: documenting package-related issues
Message-ID:  <f76d0dc4-0924-632d-7475-287ba7f9ffb5@gmail.com>
next in thread | raw e-mail | index | archive | help 
This is a multi-part message in MIME format.
--------------TgdKftNWF9WsYgRAZW6QHoUH
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273859#c5>:

 > how can we document all these breakages and workarounds, so that 
people can just do the equivalent of `do-release-upgrade`?

I guess, for some types of issue there can be a package message.

--------------TgdKftNWF9WsYgRAZW6QHoUH
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html data-lt-installed="true">
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body style="padding-bottom: 1px;">
    <p><a class="moz-txt-link-rfc2396E" href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273859#c5">&lt;https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273859#c5&gt;</a>:
      <br>
    </p>
    <p>&gt; how can we document all these breakages and workarounds, so
      that people can just do the equivalent of `do-release-upgrade`?</p>
    <p>I guess, for some types of issue there can be a package message.
      <br>
    </p>
  </body>
  <lt-container></lt-container>
</html>

--------------TgdKftNWF9WsYgRAZW6QHoUH--

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f76d0dc4-0924-632d-7475-287ba7f9ffb5>