Ticket #976 (closed task: wontfix)

Opened 3 years ago

Last modified 3 years ago

Util-linux 2.25.2

Reported by: chris@… Owned by: clfs-commits@…
Priority: major Milestone: CLFS Standard 3.1.0
Component: BOOK Version: CLFS Standard GIT
Keywords: Cc: berzerkula@…, jonathan@…, chris@…

Description

New minor version. The addition of GPT support to fdisk/cfdisk is nice, but that's probably not enough to warrant a version upgrade before the book release, and I'm not seeing any major bugfixes either.

I'd say wait on updating this, unless there's some important fix that I missed in the release notes.

Change History

comment:1 Changed 3 years ago by blackadder

Looks like we will either have to build it twice as there is now a circular dependency with systemd libraries, or consider a scheme like the one in LFS, where they link e2fsprogs and systemd to the tools version(s) of util-linux libraries. I much prefer the former.

New switch(s) --with-systemd, which controls the building against systemd, suggest adding this to the 2nd build along with --with-systemdsystemunitdir=/lib/systemd/system

--disable-bash-completion, seems this package has also gained this facility.

comment:2 Changed 3 years ago by chris@…

Util-linux using systemd isn't new - note that there's already a note in the Util-linux page in the current book about this.

comment:3 Changed 3 years ago by blackadder

Yes but i didn't think you had to use --with-systemd, to get any of the unit files.

comment:4 Changed 3 years ago by chris@…

I just tried building 2.25, and it does install systemd service files, in the correct location, without specifying any additional configure options, at least if systemd is found.

comment:5 follow-up: ↓ 8 Changed 3 years ago by blackadder

Apologies if I wasn't clear, we either have to build it twice, once before systemd to satisfy e2fs and systemd dependencies and then again after systemd to get any unit files. Or fiddle with pkgconfig and library locations.

You are probably right about the additional configure option use uses it as default.

comment:6 follow-up: ↓ 7 Changed 3 years ago by blackadder

Use to just use --enable-socket-activation to get the appropriate uuid support for socket activation, can't do that now,

comment:7 in reply to: ↑ 6 Changed 3 years ago by chris@…

Replying to blackadder:

Use to just use --enable-socket-activation to get the appropriate uuid support for socket activation, can't do that now,

The configure option is gone, but it looks like it's enabled by default.

comment:8 in reply to: ↑ 5 Changed 3 years ago by chris@…

Replying to blackadder:

Apologies if I wasn't clear, we either have to build it twice, once before systemd to satisfy e2fs and systemd dependencies and then again after systemd to get any unit files. Or fiddle with pkgconfig and library locations.

You are probably right about the additional configure option use uses it as default.

I know what you mean, but I believe we do cover this by suggesting that the user can rebuild it with the same commands. If you want to discuss changing this, perhaps that could be done in a new ticket, since it doesn't really have any relation to the version update.

comment:9 Changed 3 years ago by chris@…

Looks like this version will need the addition of --without-python in the temp-system.

comment:10 Changed 3 years ago by kb0iic

  • Version set to CLFS Standard GIT
  • Summary changed from Util-linux 2.25 to Util-linux 2.25.2
  • Milestone set to CLFS Standard 3.1.0

comment:11 Changed 3 years ago by kb0iic

  • Status changed from new to closed
  • Resolution set to wontfix
Note: See TracTickets for help on using tickets.