Bug#1030694: Rename init variable to fix conflict with entry point
Hi David, Em seg., 6 de fev. de 2023 às 12:27, David Prévot escreveu: > > Package: inotify-tools > Version: 3.22.6.0-3 > Severity: important > Tags: upstream patch > > Hi! > > We’ve noticed that fsnotifywait didn’t work as expected: even if the > kernel is notified, fsnotifywait was not. The following upstream commit > actually fixes the issue, I’ve tested it also on a bullseye server (with > the package rebuilt as a backport). > > https://github.com/inotify-tools/inotify-tools/commit/be8426ce01fbe91cab62bc1131649cc80c60 > > Unfortunately, it also required the following change in the symbols > file. > > - init@Base 3.21.9.5 > + initialized@Base 3.22.6.0 > > Can you please consider applying this small targeted fix in time for the > Bookworm release? Sure! Thanks a lot for your help. Regards, Eriberto
Bug#1030694: Rename init variable to fix conflict with entry point
Package: inotify-tools Version: 3.22.6.0-3 Severity: important Tags: upstream patch Hi! We’ve noticed that fsnotifywait didn’t work as expected: even if the kernel is notified, fsnotifywait was not. The following upstream commit actually fixes the issue, I’ve tested it also on a bullseye server (with the package rebuilt as a backport). https://github.com/inotify-tools/inotify-tools/commit/be8426ce01fbe91cab62bc1131649cc80c60 Unfortunately, it also required the following change in the symbols file. - init@Base 3.21.9.5 + initialized@Base 3.22.6.0 Can you please consider applying this small targeted fix in time for the Bookworm release? Thanks in advance. Regards taffit signature.asc Description: PGP signature
