public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] udev: Update to version 3.2.11
Date: Thu, 25 Aug 2022 14:02:24 +0100	[thread overview]
Message-ID: <1E14957D-D438-4BF7-B888-7BB6A66D7E8E@ipfire.org> (raw)
In-Reply-To: <df792c7f-c1e2-3ee1-32ac-ee5cacb63c92@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 5892 bytes --]

Hello,

A VM is good enough for most testing, since they emulate hardware well enough so that udev would be necessary - and most stuff is independent of the hardware anyways.

I was just considering whether there would be some changes that didn’t make the NEWS in udev because I am not so deep into the kernel development.

I would say, that this is good enough for me and the patch can continue its journey.

Acked-by: Michael Tremer <michael.tremer(a)ipfire.org>

-Michael

> On 22 Aug 2022, at 14:25, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi Michael,
> 
> On 22/08/2022 13:47, Adolf Belka wrote:
>> Hi Michael,
>> 
>> On 22/08/2022 10:42, Michael Tremer wrote:
>>> Hello Adolf,
>>> 
>>> The patch looks good and there do not seem to be too many changes here.
>>> 
>>> However, did you boot a system with this and did you see anything change there?
>> No I did not.
>> 
>> I can give that a go but only on a vm system. Is that good enough. Is a successful boot-up just classified as getting to the login prompt without any errors or do I need to compare the boot logs of the old and new udev boots to look for differences?
>> 
> Tested it out on a vm. It booted without any difference that I could see to normal. Looking in the logs, I don't know what to look for.
> 
> 
> I then restored my backup and everything is running as it should do.
> 
> Looking at many of the menu items nothing was showing a problem.
> 
> 
> Regards,
> 
> If I need to do some more specific checking just let me know what and where to look and I will do so.
> 
> Regards,
> 
> Adolf.
> 
>> Regards,
>> Adolf.
>>> 
>>> -Michael
>>> 
>>>> On 21 Aug 2022, at 21:01, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>> 
>>>> - Update from version 3.2.6 to 3.2.11
>>>> - Update of rootfile
>>>> - Changelog
>>>>   Release 3.2.11 Latest
>>>>       add actions workflows to check compilation on glibc and musl (devuan, alpine) by @ArsenArsen in #206
>>>>       Add build instructions by @slicer69 in #207
>>>>       src/libudev/conf-files.c: fix bug of using basename by @xfan1024 in #198
>>>>       Permit eudev to work with rules which include escaped double-quotes by @slicer69 in #208
>>>>       sync src/ata_id/ata_id.c by @bbonev in #201
>>>>       sync src/v4l_id/v4l_id.c by @bbonev in #202
>>>>       sync src/scsi_id/scsi_id.c by @bbonev in #203
>>>>       sync src/mtd_probe/*.[ch] by @bbonev in #204
>>>>       sparse: avoid clash with __bitwise and __force from 4.10 linux/types.… by @bbonev in #209
>>>>       Silence deprecation warnings by @bbonev in #210
>>>>       update CONTRIBUTING to reflect updated governance, clarify systemd commit hash requirements by @kaniini in #211
>>>>       hashmap: don't initialize devt_hash_ops in the header by @kaniini in #212
>>>>       Update to latest Devuan stable by @wwuck in #213
>>>>       hwdb: sync with systemd/main by @bbonev in #215
>>>>       Add getrandom(2) system call number for PowerPC by @Low-power in #216
>>>>    No changelog for versions prior to 3.2.11 found. Looks like they are in nthe systemd
>>>>     releases and not easily extracted.
>>>> 
>>>> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
>>>> ---
>>>> config/rootfiles/common/udev | 9 +++++++++
>>>> lfs/udev                     | 4 ++--
>>>> 2 files changed, 11 insertions(+), 2 deletions(-)
>>>> 
>>>> diff --git a/config/rootfiles/common/udev b/config/rootfiles/common/udev
>>>> index 5c1267abe..a34ee46c3 100644
>>>> --- a/config/rootfiles/common/udev
>>>> +++ b/config/rootfiles/common/udev
>>>> @@ -6,6 +6,7 @@ etc/udev/hwdb.d
>>>> etc/udev/hwdb.d/20-OUI.hwdb
>>>> etc/udev/hwdb.d/20-acpi-vendor.hwdb
>>>> etc/udev/hwdb.d/20-bluetooth-vendor-product.hwdb
>>>> +etc/udev/hwdb.d/20-dmi-id.hwdb
>>>> etc/udev/hwdb.d/20-net-ifname.hwdb
>>>> etc/udev/hwdb.d/20-pci-classes.hwdb
>>>> etc/udev/hwdb.d/20-pci-vendor-model.hwdb
>>>> @@ -14,12 +15,20 @@ etc/udev/hwdb.d/20-sdio-vendor-model.hwdb
>>>> etc/udev/hwdb.d/20-usb-classes.hwdb
>>>> etc/udev/hwdb.d/20-usb-vendor-model.hwdb
>>>> etc/udev/hwdb.d/20-vmbus-class.hwdb
>>>> +etc/udev/hwdb.d/60-autosuspend-fingerprint-reader.hwdb
>>>> +etc/udev/hwdb.d/60-autosuspend.hwdb
>>>> etc/udev/hwdb.d/60-evdev.hwdb
>>>> +etc/udev/hwdb.d/60-input-id.hwdb
>>>> etc/udev/hwdb.d/60-keyboard.hwdb
>>>> +etc/udev/hwdb.d/60-seat.hwdb
>>>> etc/udev/hwdb.d/60-sensor.hwdb
>>>> +etc/udev/hwdb.d/70-analyzers.hwdb
>>>> +etc/udev/hwdb.d/70-cameras.hwdb
>>>> +etc/udev/hwdb.d/70-joystick.hwdb
>>>> etc/udev/hwdb.d/70-mouse.hwdb
>>>> etc/udev/hwdb.d/70-pointingstick.hwdb
>>>> etc/udev/hwdb.d/70-touchpad.hwdb
>>>> +etc/udev/hwdb.d/80-ieee1394-unit-function.hwdb
>>>> #etc/udev/rules.d
>>>> etc/udev/rules.d/55-lfs.rules
>>>> etc/udev/rules.d/81-cdrom.rules
>>>> diff --git a/lfs/udev b/lfs/udev
>>>> index f148eb0aa..e712ef6ea 100644
>>>> --- a/lfs/udev
>>>> +++ b/lfs/udev
>>>> @@ -24,7 +24,7 @@
>>>> 
>>>> include Config
>>>> 
>>>> -VER        = 3.2.6
>>>> +VER        = 3.2.11
>>>> RULES_VER  = 20171102
>>>> 
>>>> THISAPP    = eudev-$(VER)
>>>> @@ -42,7 +42,7 @@ objects = $(DL_FILE) udev-lfs-$(RULES_VER).tar.bz2
>>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>>> udev-lfs-$(RULES_VER).tar.bz2 = $(DL_FROM)/udev-lfs-$(RULES_VER).tar.bz2
>>>> 
>>>> -$(DL_FILE)_BLAKE2 = 7705c1526b043cbef1efcf29c1728639e063845a5ee91b0ad22d43335dce34bf2ebbe4257ca024680759020d4120a8293f62cf8e112fb1191c35f0ec2f96b681
>>>> +$(DL_FILE)_BLAKE2 = e1985a4fd0d497b739543d027b5b40033932819e3e5402a51f73fab666144f97f768dff325b5f0e0beb43420efa9afdefb76a9da6b88fa065ad25c76fe1fbc6a
>>>> udev-lfs-$(RULES_VER).tar.bz2_BLAKE2 = b5fb8177a87719e28adc976b83953024dbcfb8739b0c2e61da186cbc4df5e75e62c888da987d15c64db164002bb0a1e66ce0ff206b143dc953d7571b66d5d5c0
>>>> 
>>>> install : $(TARGET)
>>>> -- 
>>>> 2.37.2
>>>> 
>>> 


      parent reply	other threads:[~2022-08-25 13:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-21 20:01 Adolf Belka
2022-08-22  8:42 ` Michael Tremer
2022-08-22 11:47   ` Adolf Belka
2022-08-22 13:25     ` Adolf Belka
2022-08-25 12:53       ` Michael Tremer
2022-08-25 13:02       ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1E14957D-D438-4BF7-B888-7BB6A66D7E8E@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox