Hi,
On 2022-04-07 16:28, Pavel Timofeev wrote:
Hello, dear community
I've got non-working gnome-shell with the recent GNOME upgrade in the
new 2022Q2 quarterly port branch.
My laptop:
[pavel.timofeev@carbon ~]$ freebsd-version -ku
13.1-RC1
13.1-RC1
I help maintain GNOME on FreeBSD. I'm sorr
Hi,
I'm thinking about adopting the port sysutils/froxlor, as the current
maintainer seems to have long-abandoned the port.
However, I don't know if it's okay or not. Is it?
I have committed an update to the port, the open for 2.5 years Bugzilla
PR 241495, although I bumped it to its latest
Hi ports@,
I was looking at the port security/sssd (mainly to connect FreeBSD to a
Windows Server 2022 AD), and noticed the maintainer is inactive.
sssd has multiple maintainer timeouts:
https://www.freshports.org/security/sssd
I don't know if we should reset the maintainership of this port
Hi freebsd-ports@,
I have this Bugzilla PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256200
This attempts to update devel/glib20 to 2.68.3, which is needed for the
GNOME 40 import.
I did request an exp-run, but the initial patch did not apply. I did
update the patch which should a
It's your thoughts and care that count Neel, don't feel guilty.
Thanks!
The responses you received could have been a bit more 'matter of fact'.
What was *actually* important about the replies was 'we should be
QA'ing everything and getting more than one persons eyes on things'.
True, especi
need portmgr
approval, but I won't commit it without approval.
Happy hacking!
-Neel Chauhan (nc@)
Footnotes:
[1] - For reference, I work at Microsoft and use Windows at work, but
used FreeBSD almost exclusively at home since 2012, back when I was only
15 (I'm 24 now), and more-or-less
