Opened 15 years ago

Closed 15 years ago

#2473 closed task (fixed)

Udev-146

Reported by: Matthew Burgess Owned by: lfs-book@…
Priority: normal Milestone: 7.0
Component: Book Version: SVN
Severity: normal Keywords:
Cc:

Description

New version. Release announcement at http://marc.info/?l=linux-hotplug&m=125025456907405&w=2.

Change History (5)

comment:1 by Bryan Kadzban, 15 years ago

Note that this will require a change to the bootscripts (udev_retry). According to the release announcement, "udevadm trigger --retry-failed" is gone; you're supposed to use "udevadm trigger --type=failed" now.

The latter does exist in current udev versions, so we could make this change now. But I don't know if that will cause grief for the 6.5 release process; if so, and assuming we won't push this udev into a frozen book, we can hold off until after 6.5 is done.

(I actually have the change done; I threw it together this morning. But there's no particular reason to submit if it might cause problems when we branch for -rc3 or -final.)

comment:2 by bdubbs@…, 15 years ago

Type: enhancementtask

When I looked at the changelog, there didn't seem to be anything critical for 6.5. I recommend that we not try to put this in before the release.

in reply to:  2 ; comment:3 by Matthew Burgess, 15 years ago

Replying to bdubbs@…:

I recommend that we not try to put this in before the release.

Agreed, that's why I set the version to 7.0 :-) Bryan, feel free to commit your changes to trunk, but the 6.5 branch is most certainly frozen.

Thanks,

Matt.

in reply to:  3 comment:4 by Bryan Kadzban, 15 years ago

Replying to matthew@…:

Bryan, feel free to commit your changes to trunk, but the 6.5 branch is most certainly frozen.

Oh, of course. (And you don't branch/tag 6.5-final from trunk; you just tag it from the current 6.5 branch. Duh.)

Committed to trunk in r9049. Udev can be upgraded whenever, unless they changed something else too. :-)

comment:5 by Matthew Burgess, 15 years ago

Resolution: fixed
Status: newclosed

Fixed in r9061.

Note: See TracTickets for help on using tickets.