Qubes packages updates, what has changed?

[Holger Levsen]

Hi,

I just did a dom0 upgrade and was offered to update qubes-gui-dom0 to version
3.2.9-1.fc23, however when I clicked on "package changelog" in yum-extender
the changelog was empty.

This has happened before…

So I'm wondering: how can I find out, what has changed and why does Qubes 3.2
receive an update?

I'm thinking more of a general solution, like an announce mailinglist, but
for now I would also be happy about a pointer to the git repo and branch,
where I can see those changes leading to qubes-gui-dom0 3.2.9-1.fc23…


--
cheers,
Holger

[Holger Levsen]

On Mon, Mar 06, 2017 at 11:06:25PM +0000, Holger Levsen wrote:
> I just did a dom0 upgrade and was offered to update qubes-gui-dom0 to version
> 3.2.9-1.fc23, however when I clicked on "package changelog" in yum-extender
> the changelog was empty.
>
> This has happened before…
>
> So I'm wondering: how can I find out, what has changed and why does Qubes 3.2
> receive an update?
>
> I'm thinking more of a general solution, like an announce mailinglist, but

(or making sure yum-extender has a changelog to display…)

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, Mar 06, 2017 at 11:06:25PM +0000, Holger Levsen wrote:

> Hi,
>
> I just did a dom0 upgrade and was offered to update qubes-gui-dom0 to version
> 3.2.9-1.fc23, however when I clicked on "package changelog" in yum-extender
> the changelog was empty.
>
> This has happened before…

Yes, we currently do not fill %changelog section in rpm packages. We
have this on our todo list...
https://github.com/QubesOS/qubes-issues/issues/1508

> So I'm wondering: how can I find out, what has changed and why does Qubes 3.2
> receive an update?
>
> I'm thinking more of a general solution, like an announce mailinglist, but
> for now I would also be happy about a pointer to the git repo and branch,
> where I can see those changes leading to qubes-gui-dom0 3.2.9-1.fc23…

https://github.com/QubesOS/qubes-issues/issues?utf8=%E2%9C%93&q=qubes-gui-dom0%203.2.9-1.fc23

;)

Each comment added by builder-github plugin have a link to appropriate
git log. In this case:
https://github.com/QubesOS/qubes-gui-daemon/compare/044040b0dff32f2fbc2af3d53daa72ccf6e7b397...52bd56cee67d5b92a1d5d789136e286954c62c84

Such comments are added to issues referenced from commits. We try to
always include issue reference if that makes sense (sometimes by
creating an issue just to have something to put in that commit). But
there may be cases, when no issue was referenced, then it will be harder
to find that (you'll need to know what repository to look at).

There is more: right now we're enabling another way to track updates -
have an issue created for every updated package, as a way to track what
is in testing repository. See here:
https://github.com/QubesOS/qubes-issues/issues/2573
https://github.com/QubesOS/updates-status/issues


This isn't fully integrated yet, but you can get an idea how it will
look like.

All the above is implemented here:
https://github.com/qubesos/qubes-builder-github

Feel free to open pull requests there.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJYvfJxAAoJENuP0xzK19csRWgH/195uEgVvjEQhi4jGFUzU0Ca
9r+I/8EFO7daECpyHtXfPrwjUfl5QrOVXwEeWNBMbVQq0yGxU+YxAtat6REMMHeL
C4wLTEJoF3Jd7gwfeFMjOQQo2ARs7ePIqJVUptHFvSWyZWkMXnorUIBAqLdyXgU8
Pc47wJ2FrezPWiNjPZZHN2eM5KKT02KLgsSCM9LtY2qfLhu/TTKCmk1GG+7AV6EG
xaoArhHuo84XjuM2NuDECznsPb6btLXonLN8xOSTp3qq+b2aqMZNL+r8JRG8NixK
zJmi1XYxrcTq4s22ZZGcnVPNTRxveVK1UZs/38flmKAKP1qFQJnk1v/hn5/5DY0=
=dc5T
-----END PGP SIGNATURE-----

[Holger Levsen]

Hi Marek,

sorry for the late reply, your replies often include lots of data to process…
that's awesome just sometimes hard to find the time to :)

Thanks a lot for all this information!

On Tue, Mar 07, 2017 at 12:36:17AM +0100, Marek Marczykowski-Górecki wrote:
> Yes, we currently do not fill %changelog section in rpm packages. We
> have this on our todo list...
> https://github.com/QubesOS/qubes-issues/issues/1508

ah. I've subscribed to this issue now, as I think it's quite important to
solve.

> There is more: right now we're enabling another way to track updates -
> have an issue created for every updated package, as a way to track what
> is in testing repository. See here:
> https://github.com/QubesOS/qubes-issues/issues/2573
> https://github.com/QubesOS/updates-status/issues

nice. I've subscribed to the later URL too :)


--
cheers,
Holger