www/py-django42: Extend EXPIRATION_DATE after 74ee429290da
* Updating www/seahub and, above all, net-mgmt/seafile-server is more
difficult than originally anticipated. Since the current version of
www/seahub still relies on Django 4.2, extend the EXPIRATION_DATE by
three months.
PR: 291707
With hat: python
net-mgmt/seafile-server,www/seahub: Deprecate
Updating www/seahub, and especially net-mgmt/seafile-server, is more
difficult than originally anticipated. The current version of www/seahub
also only runs with Django 4.2, which has been end-of-life since April.
Before www/seahub and net-mgmt/seafile-server are marked as BROKEN after
the migration of the affected ports to Django 5.2 [1], and then vanish
from the ports tree at the end of 2026Q2 - which would also break POLA
due the short time period - do the following to buy some time for a
possible update:
* Create required py-dj42-* ports and switch www/seahub to them. These
py-dj42-* ports were copied from their original counterparts, are
bound to Django 4.2, and have also been adapted for the PEP517 build
framework to make them future-proof. Also adjust related entries in
MOVED.
* Add CONFLICTS_INSTALL entries to the original counterparts as well
[11 lines not shown]
[GlobalsModRef] Don't erase while iterating
The loop erases from AllocsForIndirectGlobals while walking it, which
now hits the iterator invalidation assert in DenseMap::erase. Use
remove_if instead.
deskutils/mate-notification-daemon: switch to GitHub source
Switch from MATE mirror to GitHub tarball using USE_GITHUB and
GH_ACCOUNT=mate-desktop, add autoreconf, remove tar:xz, and bump
PORTREVISION.
[ORC] Avoid iterator invalidation when erasing image info symbols
processObjCImageInfo iterated the section's DenseSet of symbols while
calling removeDefinedSymbol, which erases from that same set. Re-fetch
begin() each iteration so the iterator is always fresh.
deskutils/mate-indicator-applet: switch to GitHub source
Switch from MATE mirror to GitHub tarball using USE_GITHUB and
GH_ACCOUNT=mate-desktop, add autoreconf, remove tar:xz, and bump
PORTREVISION.
snd_hda: Reassign duplicate HDMI/DP pin sequences instead of disabling
Some firmware (e.g. Apple EFI on Sandy Bridge Mac hardware) programs all
HDMI/DP output pins in an association with identical sequence numbers.
The existing code disables the entire association on the first
duplicate, leaving HDMI/DP audio non-functional.
For digital output pins (HDMI/DP) with seq=0 duplicates, search for the
next free sequence slot and reassign the duplicate rather than
disabling.
The seq=0 restriction targets the known Apple firmware pattern; any
other duplicate sequence is more likely a genuine firmware error and the
association is still disabled.
Update first after reassignment so that hpredir is not left pointing at
a stale sequence. Non-digital and input associations retain the existing
disable behaviour.
[6 lines not shown]
devel/librashader: Update 0.10.1 => 0.11.0
Port changes:
* Improve readability by putting USE_GITHUB and its related variables
into its own block. Also put the CARGO_FEATURES on separate lines.
* Remove "stable" from CARGO_FEATURES. This has become the default
upstream and is a no-op to ensure backwards-compatibility.
* Remove obsolete patch for big-endian architectures. This fix is
included in the updated spirv-cross2 crate.
Changelog:
https://github.com/SnowflakePowered/librashader/releases/tag/librashader-v0.11.0
PR: 295606
Reported by: Stefan Schlosser <bsdcode at disroot.org> (maintainer)
Approved by: osa, vvd (Mentors, implicit)
[Clang][test] check-clang-format not created with LLVM_ENABLE_IDE (#199638)
add_lit_testsuites skips creating targets for each subdirectory when
LLVM_ENABLE_IDE. Only create the dependency (introduced in #199169) when
the check-clang-format target actually exists.
Fixes the LLVM build when using an IDE.
[Coroutines] Allow rematerialization of unary operators and selected intrinsics (#197698)
All of those can be cheaply recomputed when the coroutine has resumed.
Before this change, results of unary operators and intrinsics were
spilled into the coroutine frame and reloaded on resume:
```
%neg = fneg float %n
store float %neg, ptr %neg.spill.addr
; In resume:
%neg.reload = load float, ptr %neg.reload.addr
; ... use %neg.reload
```
After this change, only the operand is spilled and the operation is
rematerialized on each resume, avoiding the frame store:
[9 lines not shown]
[mlir][mem2reg] fix assert for indirect blocking uses inside regions (#199193)
When adding new blocking uses created by the interface of a previous
blocking uses (typically forwarding the blocking uses to the op result
users), the mem2reg framework was assuming that the new blocking uses
are in the same region as the original blocking use, which is not true
in general and lead to the assert:
`Transforms/Mem2Reg.cpp:743: void
{anonymous}::MemorySlotPromoter::removeBlockingUses(mlir::Region*):
Assertion `op->getParentRegion() == region && "all operations must still
be in the same region"' failed.`
This patch fixes this by adding the new uses into the userToBlockingUses
for the region of the new blocking uses.
