doc: add two upper bounds for libical
First one is based on a commit, second one on a report that it was
already fixed six years ago, so I took the oldest distfile I had that
was newer than that as an upper bound.
netsurf: mark as not make-jobs-safe
Due to
gmake[1]: *** No rule to make target 'build-x86_64--netbsd-x86_64--netbsd-release-lib-static/filter-lexer.inc', needed by 'build-x86_64--netbsd-x86_64--netbsd-release-lib-static/filter-lexer.c'. Stop.
and
src/filter-parser.y:15:10: fatal error: filter-lexer.h: No such file or directory
sysutils/qemu-guest-agent: New package for just the qemu-ga program.
This is an agent designed to be used inside a guest -- so it's not
really useful for cases where you want the rest of the emulators/qemu
package, and at a few megabytes it's much smaller than emulators/qemu
which weighs in at a few gigabytes.
If we had subpackages -- multiple binary packages built from a single
source -- then it would be reasonable to use that for the qemu guest
agent rather than maintaining a separate makefile. But we don't.
Derived from wip/qemu-guest-agent.
graphics/darktable: Link against libexecinfo if needed.
Fixes:
[ 56%] Building C object bin/CMakeFiles/darktable.dir/main.c.o
[ 56%] Linking C executable darktable
/usr/bin/ld: libdarktable.so: undefined reference to `backtrace_symbols'
/usr/bin/ld: libdarktable.so: undefined reference to `backtrace'
collect2: error: ld returned 1 exit status
*** [bin/darktable] Error code 1
devel/ruby-activestorage80: update to 8.0.2
8.0.2 (2025/03/12)
* A Blob will no longer autosave associated Attachment.
This fixes an issue where a record with an attachment would have its dirty
attributes reset, preventing your after commit callbacks on that record to
behave as expected.
Note that this change doesn't require any changes on your application and
is supposed to be internal. Active Storage Attachment will continue to be
autosaved (through a different relation).
Edouard-chin
