Skip to content

Conversation

@jimklimov
Copy link
Member

Follow-up for #2800 and #3291.

Perhaps the NIT suite should use the tool instead of directly starting the driver programs; then this would have been caught. Maybe some other day though...

…ED_PRIVATE_LIBS [networkupstools#2800]

Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
…older vs. ENABLE_SHARED_PRIVATE_LIBS [networkupstools#2800]

Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
@jimklimov jimklimov added this to the 2.8.5 milestone Jan 31, 2026
@jimklimov jimklimov added CI Entries related to continuous integration infrastructure (here CI = tools + scripts + recipes) portability We want NUT to build and run everywhere possible bug service/daemon start/stop General subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug labels Jan 31, 2026
@AppVeyorBot
Copy link

…l too [networkupstools#2800]"

This reverts commit deb3c6c:
currently problematic on Appveyor builds:
Can't start /c/projects/nut/drivers/dummy-ups.exe: No such file or directory [The system cannot find the path specified. ]

Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
@jimklimov
Copy link
Member Author

jimklimov commented Feb 1, 2026

Adding upsdrvctl to NIT was not as trivial as hoped: something not found on Appveyor at least... Possibly DLLs not in the right path?..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug CI Entries related to continuous integration infrastructure (here CI = tools + scripts + recipes) portability We want NUT to build and run everywhere possible service/daemon start/stop General subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants