• pkg is suddenly case sensitive?

    From Dan Mahoney \(ports\)@freebsd@gushi.org to muc.lists.freebsd.ports on Thu Dec 4 01:23:55 2025
    From Newsgroup: muc.lists.freebsd.ports

    All,
    We've been using puppet on many of our systems to manage installed ports, and we've always defaulted to telling pkg to install the lowercase name of a package.
    Recenty, we're noticing that pkg fails to install p5-ipc-run3, and that a pkg search won't find it anymore because it's in the tree as p5-IPC-Run3.
    Did pkg recently change to be case-sensitive?
    -Dan--
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Baptiste Daroussin@bapt@FreeBSD.org to muc.lists.freebsd.ports on Thu Dec 4 11:03:17 2025
    From Newsgroup: muc.lists.freebsd.ports

    On Thu 04 Dec 01:23, Dan Mahoney (ports) wrote:
    All,

    We've been using puppet on many of our systems to manage installed ports, and we've always defaulted to telling pkg to install the lowercase name of a package.

    Recenty, we're noticing that pkg fails to install p5-ipc-run3, and that a pkg search won't find it anymore because it's in the tree as p5-IPC-Run3.

    Did pkg recently change to be case-sensitive?


    The fact that pkg was case sensitive was a bug, which has been harmless for a while, until people started playing with packages named "FreeBSD-" vs packages named "freebsd-" with the same suffix.

    Note I just figured a bug which makes the pkg.conf setting which determines this
    behaviour bugging and not working consistently everywhere (well actually working
    in most cases). I am fixing this part right now.

    Best regards,
    Bapt


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Dan Mahoney \(ports\)@freebsd@gushi.org to muc.lists.freebsd.ports on Thu Dec 4 02:18:15 2025
    From Newsgroup: muc.lists.freebsd.ports


    On Dec 4, 2025, at 2:03rC>AM, Baptiste Daroussin <bapt@FreeBSD.org> wrote:

    On Thu 04 Dec 01:23, Dan Mahoney (ports) wrote:
    All,

    We've been using puppet on many of our systems to manage installed ports, and we've always defaulted to telling pkg to install the lowercase name of a package.

    Recenty, we're noticing that pkg fails to install p5-ipc-run3, and that a pkg search won't find it anymore because it's in the tree as p5-IPC-Run3.

    Did pkg recently change to be case-sensitive?


    The fact that pkg was case sensitive was a bug, which has been harmless for a while, until people started playing with packages named "FreeBSD-" vs packages
    named "freebsd-" with the same suffix.
    Do you mean that it was a harmless bug that it *ignored* case by default? Like the above case where 'pkg install p5-ipc-run3' would work just fine?
    Note I just figured a bug which makes the pkg.conf setting which determines this
    behaviour bugging and not working consistently everywhere (well actually working
    in most cases). I am fixing this part right now.
    The shipped pkg.conf doesn't have a setting for this.
    The manpage still states that case sensitive defaults to No. If this was changed, it would really be worth a mention in UPDATING.
    -Dan--
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Baptiste Daroussin@bapt@FreeBSD.org to muc.lists.freebsd.ports on Thu Dec 4 11:50:55 2025
    From Newsgroup: muc.lists.freebsd.ports

    On Thu 04 Dec 11:03, Baptiste Daroussin wrote:
    On Thu 04 Dec 01:23, Dan Mahoney (ports) wrote:
    All,

    We've been using puppet on many of our systems to manage installed ports, and we've always defaulted to telling pkg to install the lowercase name of a package.

    Recenty, we're noticing that pkg fails to install p5-ipc-run3, and that a pkg search won't find it anymore because it's in the tree as p5-IPC-Run3.

    Did pkg recently change to be case-sensitive?


    The fact that pkg was case sensitive was a bug, which has been harmless for a while, until people started playing with packages named "FreeBSD-" vs packages
    named "freebsd-" with the same suffix.

    Note I just figured a bug which makes the pkg.conf setting which determines this
    behaviour bugging and not working consistently everywhere (well actually working
    in most cases). I am fixing this part right now.

    Best regards,
    Bapt

    Side note: if you want a consistent and predictible behaviour the -C/-i options are still working the same for all versions of pkg.

    Best regards,
    Bapt


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Dan Mahoney \(ports\)@freebsd@gushi.org to muc.lists.freebsd.ports on Thu Dec 4 04:34:27 2025
    From Newsgroup: muc.lists.freebsd.ports


    On Dec 4, 2025, at 2:50rC>AM, Baptiste Daroussin <bapt@FreeBSD.org> wrote:

    On Thu 04 Dec 11:03, Baptiste Daroussin wrote:
    On Thu 04 Dec 01:23, Dan Mahoney (ports) wrote:
    All,

    We've been using puppet on many of our systems to manage installed ports, and we've always defaulted to telling pkg to install the lowercase name of a package.

    Recenty, we're noticing that pkg fails to install p5-ipc-run3, and that a pkg search won't find it anymore because it's in the tree as p5-IPC-Run3.

    Did pkg recently change to be case-sensitive?


    The fact that pkg was case sensitive was a bug, which has been harmless for a
    while, until people started playing with packages named "FreeBSD-" vs packages
    named "freebsd-" with the same suffix.

    Note I just figured a bug which makes the pkg.conf setting which determines this
    behaviour bugging and not working consistently everywhere (well actually working
    in most cases). I am fixing this part right now.

    Best regards,
    Bapt

    Side note: if you want a consistent and predictible behaviour the -C/-i options
    are still working the same for all versions of pkg.
    That would require rewriting puppet's package provider. It's easier to update our manifests now that we know this is a thing, and I'm sure there will be Gotchas, especially with the CamelCase perl ports.
    Thanks for the quick answer.
    -Dan--
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2