Skip to content

[bot-automerge] util-linux v2.42.3 - #62

Merged
conda-forge-admin merged 3 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:2.42.3_h026579
Sep 6, 2026
Merged

conda-forge-admin merged 3 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:2.42.3_h026579

Conversation

@regro-cf-autotick-bot

Copy link
Copy Markdown
Contributor

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

  • Dependencies have been updated if changed: see upstream
  • Tests have passed
  • Updated license if changed and license_file is packaged

Information about this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version.
  3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
  4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
  5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name Upstream Version Current Version
ncurses 6_6_20260425 Anaconda-Server Badge

This PR was created by the conda-forge-bot. The conda-forge-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/conda-forge/conda-forge-bot/actions/runs/33622011101 - please use this URL for debugging.

@conda-forge-admin

Copy link
Copy Markdown
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@conda-forge-admin

conda-forge-admin commented Sep 2, 2026 •

Copy link
Copy Markdown
Contributor

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

  • linter: passed
  • azure: passed
  • github-actions: passed

Thus the PR was passing and merged! Have a great day!

@hmaarrfk hmaarrfk closed this Sep 2, 2026
@hmaarrfk hmaarrfk reopened this Sep 2, 2026
@hmaarrfk hmaarrfk closed this Sep 2, 2026
@hmaarrfk hmaarrfk reopened this Sep 2, 2026
@hmaarrfk hmaarrfk closed this Sep 2, 2026
@hmaarrfk hmaarrfk reopened this Sep 2, 2026
@hmaarrfk hmaarrfk closed this Sep 2, 2026
@hmaarrfk hmaarrfk reopened this Sep 2, 2026
@hmaarrfk hmaarrfk closed this Sep 4, 2026
@hmaarrfk hmaarrfk reopened this Sep 4, 2026
<details><summary>Claude's draft</summary>

`recipe/4554-kill-decode-strip-RT0.patch` backported the one-line fix from
util-linux/util-linux#4554 (upstream commit
12d905457fcac7145ff6eacf389895ed65657593), which adds
`sed_cmd+=" -e s/' RT0'//"` to `tests/ts/kill/decode`.

That fix is present in the 2.42.3 tarball at `tests/ts/kill/decode:119`, so
the backport no longer applies and would fail source preparation on every
platform:

    patch -p1 --dry-run  ->  Reversed (or previously applied) patch detected!
    git apply --check    ->  patch does not apply

Removed the patch file and the `source.patches` block.

Verified locally in docker with
`python build-locally.py linux_64_python3.15.____cp315`:
`kill: decode functions ... OK` on upstream's own fix, `All 368 tests
PASSED`, and the package builds and passes the conda-build test phase. The
built package carries no patch in `info/recipe/`.

The source sha256 in the bot's bump was independently verified against the
downloaded tarball.

Resume this Claude session:
```
cd /home/mark/git/feedstock
claude --resume 1a1da11f-8b2a-42db-a714-637acafc1f0c
```
</details>

Claude-Session: https://claude.ai/code/session_01EfjECQNBRAvthx6SMS52Mx
@conda-forge-admin

Copy link
Copy Markdown
Contributor

Hi! This is the friendly conda-forge automerge bot!

It appears that not all commits to this PR were made by the bot. Thus this PR is not being automatically merged. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

@hmaarrfk hmaarrfk added the automerge Merge the PR when CI passes label Sep 5, 2026
<details><summary>Claude's draft</summary>

util-linux 2.42.3 fails to build on linux-riscv64 only:

  libmount/src/hook_idmap.c:335:33: error: 'RESOLVE_NO_SYMLINKS' undeclared

The symbol was introduced in hook_idmap.c by the CVE-2026-78410 fix
(fb8e26535), which replaced a raw open_tree() call with mnt_open_tree()
but did not add the include that provides the fallback #define. Upstream
masked this on Fedora because glibc 2.40+ pulls <linux/openat2.h> in
transitively via <fcntl.h>.

riscv64 is the only conda-forge linux target that trips over it. Its
sysroot is glibc 2.39 with kernel-headers 6.12, so configure detects the
new mount API and compiles the guarded block; every other linux subdir
still builds against glibc 2.28 with kernel-headers 4.18 and drops it:

  linux-64      checking for fsopen/open_tree/mount_setattr... no
  linux-riscv64 checking for fsopen/open_tree/mount_setattr... yes

Backport upstream 7e2e010874b1, which adds the missing
#include "fileutils.h". Applies unmodified to the 2.42.3 tarball.

Verified locally: build-locally.py linux_riscv64_python3.14.____cp314
now builds and packages successfully.

Note for later: upstream util-linux#4606 (still open) points out that
fileutils.h's fallback defines RESOLVE_NO_SYMLINKS as 0x02, which is
really RESOLVE_NO_MAGICLINKS; the kernel value is 0x04. That affects
symlink hardening for restricted mounts and is not made worse here --
this is exactly what upstream ships.

Resume this Claude session:
```
cd /home/mark/git/feedstock/util-linux-feedstock
claude --resume b8dc57de-d20a-47e5-b0e8-25d84ce3c1cd
```
</details>

Claude-Session: https://claude.ai/code/session_01R5SVs1MgZwsBie81wWSbok
@conda-forge-admin

Copy link
Copy Markdown
Contributor

Hi! This is the friendly conda-forge automerge bot!

Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

@conda-forge-curator conda-forge-curator Bot removed the automerge Merge the PR when CI passes label Sep 6, 2026
@hmaarrfk hmaarrfk added the automerge Merge the PR when CI passes label Sep 6, 2026
@conda-forge-admin
conda-forge-admin merged commit 6f2cc90 into conda-forge:main Sep 6, 2026
30 checks passed
@regro-cf-autotick-bot
regro-cf-autotick-bot deleted the 2.42.3_h026579 branch September 6, 2026 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge Merge the PR when CI passes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants