net-im/tdlib-purple: Resurrect, now at 0.9.6
Changelog:
https://github.com/UnitedMarsupials/tdlib-purple/blob/v0.9.6/CHANGELOG.md
The port was removed on 2025-11-01 as broken: it no longer compiled
against a current net-im/tdlib, having been written for TDLib 1.7.9,
and upstream has not committed since December 2021.
This is a fork that tracks the modern API. 0.9.6 builds against TDLib
1.8.44 or newer, tested against 1.8.68, and gathers the good pull
requests left unanswered upstream: the 1.8 port itself, the option to
display self-destructing messages, and no longer adding group chats one
is not a member of. Beyond those it shows the thumbnail Telegram sends
with a video, describes the contents of message types it does not
support rather than only naming them, escapes text chosen by the remote
party before it reaches the conversation window, and its translations
display correctly in locales that are not UTF-8, with a Ukrainian one
added.
In Pidgin, a message's reactions are listed under it, with who gave
each in its tooltip, and a message's own menu adds or takes back a
reaction, edits, deletes or reports it, and copies its file; files can
also be dragged out of a conversation. Edits and deletions are applied
in place, replies and notices link to their message, a conversation
opened is filled from Telegram starting at the first unread message,
and blocking someone in Pidgin blocks them on Telegram.
A message's menu also forwards it, natively within Telegram, without
uploading its files again, or to a buddy or chat of any other account,
chosen in a dialog that searches the list as one types. A group's own
news, such as members joining or leaving, is told in words, and a
message can be addressed to a phone number or an @username.
Those Pidgin features need Pidgin's headers at build time, though
nothing of Pidgin is linked, and the plugin checks at run time that its
host is Pidgin, so it still serves Finch or BitlBee. The new PIDGIN
option, on by default, build-depends on net-im/pidgin; off, the plugin
is built for libpurple alone, as before, without those features.
Stickers are decoded by the front-end's GdkPixbuf rather than by the
plugin, so libwebp and libpng are not linked; WebP stickers need
graphics/webp-pixbuf-loader at run time instead.
TDLib's C++ libraries carry no version in their sonames, so a plugin
built against one TDLib release used to load with another and crash on
the first changed class. The plugin now compares the running TDLib's
version with the one it was built against and declines to load on a
mismatch: every update of net-im/tdlib therefore needs a PORTREVISION
bump here.
The bundled copies of fmt and rlottie are gone from the distribution,
so the port no longer excludes them when extracting, and voice call
support compiles out by itself where tgvoip is absent instead of
failing the build.
The test suite works again -- it had not compiled since TDLib 1.7.9 --
so `make test` now runs it, and the TEST option that warned it was
broken is gone.
While here, declare the glib20 dependency the plugin has always linked
against directly, by way of libpurple's own pkg-config.
PR: 278263
Co-authored-by: Claude Opus 5.5 (effort medium)
dns/encrypted-dns-server: Update 0.9.21 => 0.9.22
Changelog:
https://github.com/DNSCrypt/encrypted-dns-server/compare/0.9.21...0.9.22
While here:
- Remove patch that fixes build without METRICS as it upstreamed.
- Set ETCDIR to ${PREFIX}/etc/encrypted-dns so it matches the
chroot() path in the shipped sample configuration.
- Create pkg-message.
PR: 300945
MFH: 2026Q4
(cherry picked from commit bd53704f439a4e83c3d4a2d9540a5c0c4006cdb2)
dns/encrypted-dns-server: Update 0.9.21 => 0.9.22
Changelog:
https://github.com/DNSCrypt/encrypted-dns-server/compare/0.9.21...0.9.22
While here:
- Remove patch that fixes build without METRICS as it upstreamed.
- Set ETCDIR to ${PREFIX}/etc/encrypted-dns so it matches the
chroot() path in the shipped sample configuration.
- Create pkg-message.
PR: 300945
MFH: 2026Q4
security/clamav-lts: Update to 1.4.7
Fixes the same vulnerabilities as clamav 1.5.5.
Changes: https://github.com/Cisco-Talos/clamav/releases/tag/clamav-1.4.7
Sponsored by: Netzkommune GmbH
(cherry picked from commit 767a119ac8b806b5764a03f49cd843d24c5e8ffc)
sysutils/rpi-firmware 1.20260521.g20260521_2
Firmware for RaspberryPi Single Board Computer
sysutils/rpi-firmware: Set framebuffer_swap=0, no mmc overlay on RPi 4
With framebuffer_swap enabled, which is the default, the recent
firmware puts the red component of a 32 bpp pixel in the low byte when
U-Boot requests RGB. U-Boot always requests RGB and announces red in
bits 16-23 in the EFI GOP, so everything that draws with that layout
has red and blue swapped. Set framebuffer_swap=0 in the config files
of the single models that boot U-Boot. The EDK2 one and the generic
config_arm64.txt are left alone.
On the Raspberry Pi 4 the SD card slot is on the emmc2 controller, so
dtoverlay=mmc only repurposes the controller of the on-board WiFi chip.
It was copied from the Raspberry Pi 3 file, where it moved the SD card
to the controller supported at the time. Remove it from
config_rpi4.txt. The other files are unchanged, there is no way to
test them here.
Bump PORTREVISION as the installed files change.
PR: 300542
Tested on: Raspberry Pi 4 Model B Rev 1.4 (U-Boot 2026.10, firmware
1.20260521): the vt(4) console and raw pixels written in
the GOP layout have the right colors with
framebuffer_swap=0, and the SD card and boot work without
the overlay. The settings were applied by hand to
config.txt, no package was built from this change.
(cherry picked from commit 821cc4b7470f1e834f117e401d720d513c3e1636)
sysutils/rpi-firmware 1.20260521.g20260521_1
Firmware for RaspberryPi Single Board Computer
sysutils/rpi-firmware: Use firmware DTB placement on Raspberry Pi 5
Set device_tree_address to an empty value for Pi 5, overriding the
inherited 0x4000 address and allowing firmware to place the DTB.
Keep DTB selection automatic for the D0 overlay. Preserve other models'
settings and bump PORTREVISION.
Companion src driver and release changes are required for Pi 5 support.
(cherry picked from commit b06f05c6953f35150ab8eaacac273510ea485a2a)
lang/rust 1.99.1_3
Language with a focus on memory safety and concurrency
lang/rust: Remove .github directories from the installed files
The .github directories in the vendored sources end up in the final
package but serve no purpose there. Remove them in post-extract so
they are not installed.
The same thing is done in lang/rust-nightly.
sysutils/rpi-firmware 1.20260521.g20260521_2
Firmware for RaspberryPi Single Board Computer
sysutils/rpi-firmware: Set framebuffer_swap=0, no mmc overlay on RPi 4
With framebuffer_swap enabled, which is the default, the recent
firmware puts the red component of a 32 bpp pixel in the low byte when
U-Boot requests RGB. U-Boot always requests RGB and announces red in
bits 16-23 in the EFI GOP, so everything that draws with that layout
has red and blue swapped. Set framebuffer_swap=0 in the config files
of the single models that boot U-Boot. The EDK2 one and the generic
config_arm64.txt are left alone.
On the Raspberry Pi 4 the SD card slot is on the emmc2 controller, so
dtoverlay=mmc only repurposes the controller of the on-board WiFi chip.
It was copied from the Raspberry Pi 3 file, where it moved the SD card
to the controller supported at the time. Remove it from
config_rpi4.txt. The other files are unchanged, there is no way to
test them here.
Bump PORTREVISION as the installed files change.
PR: 300542
Tested on: Raspberry Pi 4 Model B Rev 1.4 (U-Boot 2026.10, firmware
1.20260521): the vt(4) console and raw pixels written in
the GOP layout have the right colors with
framebuffer_swap=0, and the SD card and boot work without
the overlay. The settings were applied by hand to
config.txt, no package was built from this change.
sysutils/u-boot-rpi*: Remove the BGR pixel order patch
Remove the patch that made U-Boot request the BGR pixel order from the
Raspberry Pi firmware, added in 5ef311bb4326. The red and blue swap
is fixed by setting framebuffer_swap=0 in the config.txt files of
rpi-firmware, with U-Boot requesting RGB as upstream does.
The two do not work together. The firmware puts the red component in
bits 16-23, the layout that U-Boot announces in the EFI GOP, only when
the requested pixel order differs from framebuffer_swap. With the
patch and framebuffer_swap=0 both are 0 and the colors are swapped
again.
Do not drop PORTREVISION, bump it so the package version goes up.
PR: 300542