• Policy proposal: maintainer release for BROKEN ports

    From Robert Clausecker@fuz@fuz.ooo to muc.lists.freebsd.ports on Mon Oct 26 23:03:31 2026
    From Newsgroup: muc.lists.freebsd.ports

    Dear portmgr,

    In light of today's ports removal I feel like we need to improve the
    process around broken ports a bit. Diizzy's actions reflect a common
    failure mode we see in the tree:

    - maintainer falls absent
    - port falls into disrepair and breaks
    - nobody is alerted of the breakage and those who notice believe that
    there is a maintainer and do not take action
    - eventually someone notices that the port has been broken for *very
    long* and removes it outright (permitted within policy)

    I propose the following policy changes to improve the situation:

    - Committers are encouraged to mark ports that do not build anywhere
    as BROKEN if they believe the breakage reason to be of a kind that
    will not resolve itself shortly (e.g. temporary mirror outage). If
    the port is only broken in some configurations (some OSVERSION, some
    ARCH), the appropriate BROKEN_${ARCH} etc. should be used. When in
    doubt, committers can check the pkg repos or freshports for binary
    package presence to ascertain whether the port builds in any
    configuration

    - A new variable BROKEN_SINCE= YYYY-mm-dd is added, which should be
    set to when the breakge was first noticed when the port is marked as
    BROKEN. It should not be set for BROKEN_*, only for complete breakage.
    This is when *you* the committer noticed that the port was broken.

    - Before marking the port as BROKEN, check if there are any patches around
    that could fix it. Prefer applying such patches under build fix blanket
    approval over marking the port as BROKEN. This is not a mandatory step,
    but you are strongly encouraged to follow it.

    - Make sure to commit BROKEN and BROKEN_SINCE without delay once you
    notice the breakage.

    - Three months from BROKEN_SINCE, maintainership reverts to
    ports@FreeBSD.org except in the case of group maintainerships.
    At the same time, an EXPIRATION_DATE is added three months from
    that date. This process should be automated by means of a cron job.

    - Broken ports may only be removed without going through this process
    or without maintainer approval (this may be through maintainer timeout)
    if they are clearly beyond rescue. This includes cases like

    * The port is only available for an architecture that is no longer
    supported.

    * The port requires an OS feature that is no longer present and that
    cannot be supplied as a third-party dependency.

    * The port is not legally redistributable.

    * Upstream has requested we do not ship the port.

    * A mandatory dependency of the port has been removed and the port
    cannot be patched to no longer require it.

    * The port is unfetchable and it will not be possible to make it fetchable.
    Please follow the BROKEN process for unfetchable ports unless you
    are absolutely sure that no new upstream / hoster will ever be found.

    - Committers and third-party contributors are encouraged to step up and
    fix BROKEN ports under the established build fix policy without explicit
    maintainer approval. If they find the maintainer to be absent, they are
    encouraged to claim maintainership or revert it to ports@FreeBSD.org under
    the standard policies for maintainer timeout and absentee maintainers.

    - A port that is deleted and re-added must follow the same rules as any
    other new port. In particular, there must be a maintainer who has
    explicitly agreed to maintain the port. This can be a group
    maintainership. In case of an absentee maintainer, this can only be
    the old maintainer if he was successfully contacted or reached out on
    his own, agrees to be maintainer and is able to convince the committer
    to re-add the port that he will follow through with maintaining. It is
    at the committers discretion to ascertain this commitment. When in
    doubt, a different maintainer must be found

    Please discuss. If this proposal is well received, I would like to submit these ideas for voting in about two weeks.

    Yours,
    Robert Clausecker
    --
    () ascii ribbon campaign - for an encoding-agnostic world
    /\ - against html email - against proprietary attachments


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Gleb Popov@arrowd@freebsd.org to muc.lists.freebsd.ports on Tue Oct 27 11:22:41 2026
    From Newsgroup: muc.lists.freebsd.ports

    On Tue, Oct 27, 2026 at 2:04rC>AM Robert Clausecker <fuz@fuz.ooo> wrote:

    Dear portmgr,

    In light of today's ports removal I feel like we need to improve the
    process around broken ports a bit. Diizzy's actions reflect a common
    failure mode we see in the tree:

    - maintainer falls absent
    - port falls into disrepair and breaks
    - nobody is alerted of the breakage and those who notice believe that
    there is a maintainer and do not take action
    - eventually someone notices that the port has been broken for *very
    long* and removes it outright (permitted within policy)

    I propose the following policy changes to improve the situation:

    - Committers are encouraged to mark ports that do not build anywhere
    as BROKEN if they believe the breakage reason to be of a kind that
    will not resolve itself shortly (e.g. temporary mirror outage). If
    the port is only broken in some configurations (some OSVERSION, some
    ARCH), the appropriate BROKEN_${ARCH} etc. should be used. When in
    doubt, committers can check the pkg repos or freshports for binary
    package presence to ascertain whether the port builds in any
    configuration

    - A new variable BROKEN_SINCE= YYYY-mm-dd is added, which should be
    set to when the breakge was first noticed when the port is marked as
    BROKEN. It should not be set for BROKEN_*, only for complete breakage.
    This is when *you* the committer noticed that the port was broken.
    FWIW, I do not like the new knob. BROKEN_SINCE can be inferred from the
    "git blame" output, locating the commit that added BROKEN.
    - Before marking the port as BROKEN, check if there are any patches around
    that could fix it. Prefer applying such patches under build fix blanket
    approval over marking the port as BROKEN. This is not a mandatory step,
    but you are strongly encouraged to follow it.

    - Make sure to commit BROKEN and BROKEN_SINCE without delay once you
    notice the breakage.

    - Three months from BROKEN_SINCE, maintainership reverts to
    ports@FreeBSD.org except in the case of group maintainerships.
    At the same time, an EXPIRATION_DATE is added three months from
    that date. This process should be automated by means of a cron job.
    What about active maintainers that deliberately marked their ports BROKEN?
    For example, waiting for a new release upstream that will fix the issue?

    - Broken ports may only be removed without going through this process
    or without maintainer approval (this may be through maintainer timeout)
    if they are clearly beyond rescue. This includes cases like

    * The port is only available for an architecture that is no longer
    supported.

    * The port requires an OS feature that is no longer present and that
    cannot be supplied as a third-party dependency.

    * The port is not legally redistributable.

    * Upstream has requested we do not ship the port.

    * A mandatory dependency of the port has been removed and the port
    cannot be patched to no longer require it.

    * The port is unfetchable and it will not be possible to make it fetchable.
    Please follow the BROKEN process for unfetchable ports unless you
    are absolutely sure that no new upstream / hoster will ever be found.

    - Committers and third-party contributors are encouraged to step up and
    fix BROKEN ports under the established build fix policy without explicit
    maintainer approval. If they find the maintainer to be absent, they are
    encouraged to claim maintainership or revert it to ports@FreeBSD.org under
    the standard policies for maintainer timeout and absentee maintainers.

    - A port that is deleted and re-added must follow the same rules as any
    other new port. In particular, there must be a maintainer who has
    explicitly agreed to maintain the port. This can be a group
    maintainership.
    Fully agree.
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kevin Oberman@rkoberman@gmail.com to muc.lists.freebsd.ports on Tue Oct 27 17:17:35 2026
    From Newsgroup: muc.lists.freebsd.ports

    --000000000000737564065edb7e7a
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable

    On Tue, Oct 27, 2026 at 7:12=E2=80=AFAM Daniel Engberg <diizzy@freebsd.org>=
    wrote:

    On 2026-10-27 09:50, Jochen Neumeister wrote:
    Hi all,

    Robert's proposal touches a real problem: ports that stay BROKEN for
    months while nobody feels responsible. Releasing such ports to ports@
    can help, because it makes clear that anyone may step in and fix them.
    To Gleb's point, it should not hit active maintainers who set BROKEN
    on purpose while waiting for an upstream release.

    What I miss in this thread is the order of steps. Most of the
    discussion is about when a port may be removed. Shouldn't the first
    goal be to fix it?

    If a project is dead, for example the repository has seen no activity
    for years and the code no longer builds, there is nothing wrong with removing the port. If the project is alive, the port should get the
    chance to be fixed first. For Budgie, the fix had been available
    upstream since November 2025 (10.9.4). For filesystems/darling-dmg, a
    patch had been waiting in Bugzilla since September 27 (PR 298920),
    and the maintainer timeout had already expired. Both ports were
    removed anyway. Restoring, fixing and testing both took one evening,
    which is less time than all of us have spent on this discussion.

    These are not isolated cases. On October 4, 19 and 26 alone, 27 ports
    were removed from the tree in 21 commits because they were marked
    BROKEN. None of them had been deprecated with DEPRECATED and EXPIRATION_DATE first. Two of them were not even broken themselves,
    they only depended on a broken port. Users of these ports had no
    chance to speak up.
    BROKEN stops generating packages, adding PORTREVISION, DEPRECATED etc
    wont do anything as that isn't propagated to pkg "top" metadata.

    Running "pkg update" and "pkg upgrade" doesn't notify of anything, even
    if the package is gone from upstream repo.

    So adding DEPRECATED etc will do nothing in practice because that
    information will never be propagated because the port (package) isn't
    built in the first place.

    If you're using ports you'll already see BROKEN.

    It's applicable as long as the port actually builds however.

    I see that Daniel is possibly unaware that DEPRECATED does do something if
    you have the port in question installed. The periodic output, by default, prints a list of all packages that have security issues in the CVE and all ports that are deprecated. It also shows the date when the port may be
    deleted. Assuming you run periodic/security, the log takes care of making
    it evident to those using the port that it is deprecated every day. E.
    g. "xmlto-0.0.28_3:
    Tag: deprecated Value: Depends on vulnerable libxslt" and "xmlto-0.0.28_3:
    Tag: expiration_date Value: 2025-12-31".
    --=20
    Kevin Oberman, Part time kid herder and retired Network Engineer
    E-mail: rkoberman@gmail.com

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

    <div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon= t-family:tahoma,sans-serif;font-size:small">On Tue, Oct 27, 2026 at 7:12=E2= =80=AFAM Daniel Engberg &lt;<a href=3D"mailto:diizzy@freebsd.org">diizzy@fr= eebsd.org</a>&gt; wrote:</div></div><div class=3D"gmail_quote gmail_quote_c= ontainer"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8= ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2026-10-27 0= 9:50, Jochen Neumeister wrote:<br>
    &gt; Hi all,<br>
    &gt;<br>
    &gt; Robert&#39;s proposal touches a real problem: ports that stay BROKEN f= or<br>
    &gt; months while nobody feels responsible. Releasing such ports to ports@<=

    &gt; can help, because it makes clear that anyone may step in and fix them.=

    &gt; To Gleb&#39;s point, it should not hit active maintainers who set BROK= EN<br>
    &gt; on purpose while waiting for an upstream release.<br>
    &gt;<br>
    &gt; What I miss in this thread is the order of steps. Most of the<br>
    &gt; discussion is about when a port may be removed. Shouldn&#39;t the firs= t<br>
    &gt; goal be to fix it?<br>
    &gt;<br>
    &gt; If a project is dead, for example the repository has seen no activity<=

    &gt; for years and the code no longer builds, there is nothing wrong with<b=

    &gt; removing the port. If the project is alive, the port should get the<br=

    &gt; chance to be fixed first. For Budgie, the fix had been available<br>
    &gt; upstream since November 2025 (10.9.4). For filesystems/darling-dmg, a<=

    &gt; patch had been waiting in Bugzilla since September 27 (PR 298920),<br> &gt; and the maintainer timeout had already expired. Both ports were<br>
    &gt; removed anyway. Restoring, fixing and testing both took one evening,<b=

    &gt; which is less time than all of us have spent on this discussion.<br> &gt;<br>
    &gt; These are not isolated cases. On October 4, 19 and 26 alone, 27 ports<=

    &gt; were removed from the tree in 21 commits because they were marked<br>
    &gt; BROKEN. None of them had been deprecated with DEPRECATED and<br>
    &gt; EXPIRATION_DATE first. Two of them were not even broken themselves,<br=

    &gt; they only depended on a broken port. Users of these ports had no<br>
    &gt; chance to speak up. <br>
    BROKEN stops generating packages, adding PORTREVISION, DEPRECATED etc <br>
    wont do anything as that isn&#39;t propagated to pkg &quot;top&quot; metada= ta.<br>

    Running &quot;pkg update&quot; and &quot;pkg upgrade&quot; doesn&#39;t noti=
    fy of anything, even <br>
    if the package is gone from upstream repo.<br>

    So adding DEPRECATED etc will do nothing in practice because that <br> information will never be propagated because the port (package) isn&#39;t <=

    built in the first place.<br>

    If you&#39;re using ports you&#39;ll already see BROKEN.<br>

    It&#39;s applicable as long as the port actually builds however.</blockquot= e><div><span class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif= ;font-size:small"></span></div><div><span class=3D"gmail_default" style=3D"= font-family:tahoma,sans-serif;font-size:small">I see that Daniel is possibl=
    y unaware that DEPRECATED does do something if you have the port in questio=
    n installed. The periodic output, by default, prints a list of all packages=
    that have security issues in the CVE=C2=A0and all ports that are deprecate=
    d. It also shows the date when the port may be deleted. Assuming you run pe= riodic/security, the log takes care of making it evident to those using the=
    port that it is deprecated every day. E. g. &quot;</span>xmlto-0.0.28_3: T= ag: deprecated Value: Depends on vulnerable libxslt<span class=3D"gmail_def= ault" style=3D"font-family:tahoma,sans-serif;font-size:small">&quot; and &q= uot;</span>xmlto-0.0.28_3: Tag: expiration_date Value: 2025-12-31<span clas= s=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-size:small"= >&quot;.=C2=A0</span></div><div><span class=3D"gmail_signature_prefix"><spa=
    n class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-size:= small"></span>-- </span></div></div><div dir=3D"ltr" class=3D"gmail_signatu= re"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div = dir=3D"ltr">Kevin Oberman, Part time kid herder and retired Network Enginee= r<br>E-mail: <a href=3D"mailto:rkoberman@gmail.com" target=3D"_blank">rkobe= rman@gmail.com</a><br></div><div><br></div></div></div></div></div></div></= div></div></div>

    --000000000000737564065edb7e7a--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Dan Langille@dan@langille.org to muc.lists.freebsd.ports on Thu Oct 29 08:57:56 2026
    From Newsgroup: muc.lists.freebsd.ports

    On Wed, Oct 28, 2026, at 01:21, Daniel Engberg wrote:
    On 2026-10-28 01:17, Kevin Oberman wrote:
    On Tue, Oct 27, 2026 at 7:12rC>AM Daniel Engberg <diizzy@freebsd.org
    <mailto:diizzy@freebsd.org>> wrote:

    On 2026-10-27 09:50, Jochen Neumeister wrote:
    > Hi all,
    >
    > Robert's proposal touches a real problem: ports that stay BROKEN for >> > months while nobody feels responsible. Releasing such ports to ports@ >> > can help, because it makes clear that anyone may step in and fix
    them.
    > To Gleb's point, it should not hit active maintainers who set BROKEN >> > on purpose while waiting for an upstream release.
    >
    > What I miss in this thread is the order of steps. Most of the
    > discussion is about when a port may be removed. Shouldn't the first >> > goal be to fix it?
    >
    > If a project is dead, for example the repository has seen no activity >> > for years and the code no longer builds, there is nothing wrong with >> > removing the port. If the project is alive, the port should get the >> > chance to be fixed first. For Budgie, the fix had been available
    > upstream since November 2025 (10.9.4). For filesystems/darling-dmg, a >> > patch had been waiting in Bugzilla since September 27 (PR 298920),
    > and the maintainer timeout had already expired. Both ports were
    > removed anyway. Restoring, fixing and testing both took one evening, >> > which is less time than all of us have spent on this discussion.
    >
    > These are not isolated cases. On October 4, 19 and 26 alone, 27 ports >> > were removed from the tree in 21 commits because they were marked
    > BROKEN. None of them had been deprecated with DEPRECATED and
    > EXPIRATION_DATE first. Two of them were not even broken themselves, >> > they only depended on a broken port. Users of these ports had no
    > chance to speak up.
    BROKEN stops generating packages, adding PORTREVISION, DEPRECATED etc
    wont do anything as that isn't propagated to pkg "top" metadata.

    Running "pkg update" and "pkg upgrade" doesn't notify of anything, even >> if the package is gone from upstream repo.

    So adding DEPRECATED etc will do nothing in practice because that
    information will never be propagated because the port (package) isn't
    built in the first place.

    If you're using ports you'll already see BROKEN.

    It's applicable as long as the port actually builds however.

    I see that Daniel is possibly unaware that DEPRECATED does do something
    if you have the port in question installed. The periodic output, by
    default, prints a list of all packages that have security issues in the
    CVE-aand all ports that are deprecated. It also shows the date when the
    port may be deleted. Assuming you run periodic/security, the log takes
    care of making it evident to those using the port that it is deprecated
    every day. E. g. "xmlto-0.0.28_3: Tag: deprecated Value: Depends on
    vulnerable libxslt" and "xmlto-0.0.28_3: Tag: expiration_date Value:
    2025-12-31".
    --
    Kevin Oberman, Part time kid herder and retired Network Engineer
    E-mail: rkoberman@gmail.com <mailto:rkoberman@gmail.com>


    Hi Kevin,

    You're are correct in the sense that it does something but IF the port actually builds (and is installed). It doesn't work on ports that fails
    to build and generate packages.
    Case in point, this is an extract from the system emails I receive.
    Checking for packages with security vulnerabilities:
    Host system:
    Database fetched: 2026-10-27T08:15+00:00
    oniguruma-6.9.10: Tag: expiration_date Value: 2026-12-01
    oniguruma-6.9.10: Tag: deprecated Value: Project archived upstream
    Are you saying that if oniguruma is failing to build, these messages do not appear?
    --
    Dan Langille
    dan@langille.org
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2