00:16 <cruxbridge> <jloc0> Libsoup3 port on 3.8 has malformed git mess

04:49 <cruxbridge> <tim> fixed, thanks

04:52 <cruxbot> [contrib/3.7]: calf: 0.90.5.2 -> 0.90.6

04:52 <cruxbot> [contrib/3.7]: fdupes: 2.3.2 -> 2.4.0

10:11 <cruxbot> [contrib/3.7]: firefox: updated to version 136.0.4

10:37 <farkuhar> Sorry about the git mess in libsoup3. At first when Tim asked for the new gtk4 dependencies to be moved to opt, I thought he meant the 3.8 branch, so that's where my initial commits went. Later I realized he was bumping gtk4 in opt/3.7 too, and a followup commit in that branch caused problems for the merge.

10:49 <r0ni> i only noticed the issue cuz 'ports -d' gave me a - for libsoup3 and i started looking deeper as to what that meant lol but twas easily sorted

11:29 <farkuhar> In retrospect, it would have been safer to revert the commits in 3.8, and then push them in 3.7 instead. That way the merge would have a clean directory to overwrite. As it is, I end up keeping track of divergent histories, with some of my ports frozen at their current version in 3.7 so as not to clobber their 3.8 counterparts (which have received updates).

14:22 <cruxbot> [opt/3.7]: nfs-utils: updated to version 2.8.3

14:22 <cruxbot> [opt/3.7]: imagemagick: updated to version 7.1.1-47

14:22 <cruxbot> [core/3.7]: libarchive: updated to version 3.7.9

20:00 <cruxbot> [contrib/3.7]: p5-image-exiftool: 13.25 -> 13.26

20:00 <cruxbot> [contrib/3.7]: python3-termcolor: 2.5.0 -> 3.0.0

20:00 <cruxbot> [contrib/3.7]: sbc: 2.0 -> 2.1

20:00 <cruxbot> [contrib/3.7]: sof-bin: 2025.01 -> 2025.01.1

20:00 <cruxbot> [opt/3.7]: upower: 1.90.7 -> 1.90.8