> On Mar 11, 2023, at 11:14 AM, Tommy Trussell <tommy.truss...@gmail.com> wrote:
>
> I like to watch for updates and be aware when they happen.
>
> This system is running Ubuntu 22.04.02, so today I kicked off the update
> manager (looking for updated .deb packages and their associated changelog
> descriptions, if any) then from a terminal I checked for updated snaps, and
> then flatpaks.
>
> I was surprised the flatpak "stable" repository was showing an update to
> GnuCash 4.13. I was even more surprised it was showing the update would be
> to a commit from December. As you can imagine, I've run flatpak update
> numerous times since December. Both commits SAY they're GnuCash "4.13+" and
> from the same date and time in December.
>
> What happened? Is it something weird with flatpak? From my (naive)
> perspective, GnuCash looks exactly the same. The diffs are
> tiny, it seems, though I didn't see any way to know that before allowing
> the update.
>
[SNIP]
> Commit:
> eb1be08966b94073a6f219dcf8f61f42c88228d1d1f2aba15da990591bccf3c7
> Parent:
> 7e2d8364088a32d0f6849893a43b41a5623886c2d5c7da3505c023ba0c86fa5f
> Subject: Fix GnuCash tarball sha256 (bd9f8e1e)
> Date: 2022-12-18 22:30:44 +0000
The commits are weird. The one in parentheses is the current HEAD on
https://github.com/flathub/org.gnucash.GnuCash/commits/master and as will be
apparent if you visit that page the commit was needed because the first build
failed.
Does the subject for the parent commit say "Package GnuCash 4.13 (c825100b)"?
That's the build that failed so it's seems odd to me that it would have made an
installable flatpak.
Regards,
John Ralls
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
