Re: [RFC] patch's default backup behavior
In message , Kyle Evans writes: > On Fri, Apr 8, 2022 at 10:41 PM Warner Losh wrote: > > > > > > > > On Fri, Apr 8, 2022, 9:26 PM Kyle Evans wrote: > >> > >> Hello! > >> > >> FreeBSD's patch follows historical patch(1) behavior w.r.t. backups, > >> where a backup is created for every file patched. > >> > >> I'd like to test the waters on switching this to the GNU behavior, > >> which feels a whole lot more reasonable. Notably, they'll only create > >> backup files if a mismatch was detected (presumably this means either > >> a hunk needed fuzz or a hunk outright failed). This yields far fewer > >> backup files in the ideal scenario (context entirely matches), while > >> still leaving backup files when it's sensible (base file changed and > >> we might want to regenerate the patch). > >> > >> Thoughts / comments / concerns? Cross-posted this to a couple of > >> different lists to try and hit the largest number of stakeholders in > >> patch(1) behavior. > > > > > > Could one select the old behavior? Or would it just be a change? A new -V v > alue? > > > > Yeah, the current behavior is actually represented by the `-b` flag. > With the new behavior, we'd specifically implement > `--backup-if-mismatch` (a nop from the beginning), > `--no-backup-if-mismatch` (turn off backups, equivalent to `-V none` > but "lighter" in that it won't override -b/-V) and we'd leave existing > flags otherwise alone. Looks good to me. > > > I like the Idea. > > > > Warner > > > >> Thanks, > >> > >> Kyle Evans > >> > -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few.
Re: Recent quarterly GNOME upgrade broke my desktop
On Fri, Apr 8, 2022, 22:32 Neel Chauhan wrote: > 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 sorry if it broke for you. > > > I don't mention drm-fbsd13-kmod breakage due ABI changes (?) as I was > > able to recompile it against 13.1-RC1 locally and make it work (with > > some visual artefacts for some reason) > > I have no issues with GNOME 42, on both 14-CURRENT and 13.1-RC2, but > then I'm using the latest branch. > > > But I can't make that new GNOME work and switched to XFCE for now. > > GDM starts fine, but once I login I get "oops, something went wrong" > > message from gnome-shell. > > I disabled GDM autostart and got this in my .xinitrc: > > exec gnome-session --debug > .xsession-errors 2>&1 > > Then I started X with startx. The error file is attached. > > The errors I noticed: > > (gnome-shell:15744): Gjs-CRITICAL **: 09:23:03.928: JS ERROR: TypeError: > method GLib.TimeZone.get_offset: At least 1 argument required, but only > 0 passed > _clocksChanged/<@resource:///org/gnome/shell/ui/dateMenu.js:343:46 > _clocksChanged@resource:///org/gnome/shell/ui/dateMenu.js:342:25 > _init@resource:///org/gnome/shell/ui/dateMenu.js:309:14 > ... > > were something I fixed a while back. > > A few questions: > > 1. Are you using x11/gnome-shell 41.4_2 (note the `_2` in the version)? > This version fixes the GNOME shell. > > > Found something similar on debian mail list, where they suggested > > upgrading to gnome-shell 42. > > > https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1849602.html > > The reporter says it helped. > > Not sure if I get the same error. > > > > Am I the only one who experiences this issue with GNOME? > > You could try updating packages again, or switching to "latest". It's > only very recently that GNOME packages unbroke. > > I am using 13.1-RC2 on my laptop with GNOME 42 (really a 41/42 hybrid as > of now). > > -Neel (nc@) > Yes, I have gnome-shell-41.4_2 installed on my system. Switching to latest doesn't show any gnome-related pkg to upgrade. >
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ games/exult | 1.7.0.20211128 | snapshot-v1.7.0.20220409 +-+ math/wxmaxima | 22.03.0 | version-22.04.0 +-+ net/mpich | 3.4.3 | 4.0.2 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout!
