Qubes 3.2RC2 not verifying Checksum but passing Siganture?

40 views
Skip to first unread message

kernel[consulting] Sebastian Hültenschmidt

unread,
Aug 19, 2016, 8:53:56 AM8/19/16
to qubes...@googlegroups.com
Hi all,
I just recently downloaded the 3.2RC2 and verified the signature ok.
When i tried to use it, it fails the checksum test after ~4.8%
It rechecked the signature and tried another USB Stick without sucess.
I used it anyway to install, but it had only XFCE window manager, no KDE.

To verify i dowloaded the 3.2RC1 and it works as expected. Signature ok, checksum test ok, KDE available. I just assume you are not switching packages when transitioning from one RC to another, so i guess there is something broke on the way. RC1 is 4.5 GB, RC2 only 4.0 GB.

Did i make a mistake? Anyone else with this behaviour?

Best regards,

Sebastian

Am 18.08.2016 13:35 schrieb qubes...@googlegroups.com:
>
> qubes...@googlegroups.com
> Google Groups
> Topic digest
> View all topics
> Packaging Awesome with Qubes patches - 1 Update
> Implications of switching to Hardware Memory Virtualization for all AppVMs - 1 Update
> [PATCH] 3.2rc2 - fix missing trailing backslash in qvm-backup-restore - 2 Updates
> Packaging Awesome with Qubes patches
> Andrew David Wong <a...@qubes-os.org>: Aug 17 11:11AM -0700
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>  
> On 2016-08-16 20:34, Nicklaus McClendon wrote:
> > why Awesome can't be packaged as well. The build process runs find
> > locally, and seems to have failed on TravisCI due to a lack of
> > memory. I'd be more than happy to aid in the process if needed.
>  
> Thank you! We currently have an issue open for this:
>  
> https://github.com/QubesOS/qubes-issues/issues/1756
>  
> It's currently assigned to woju (CCed). Perhaps you might be willing
> to coordinate with him (either on GitHub or in this thread)?
>  
> - --
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -----BEGIN PGP SIGNATURE-----
>  
> iQIcBAEBCgAGBQJXtKjqAAoJENtN07w5UDAwRNIP/jgEgBD3UfjzJbxHU69Kj7PG
> HXQsGG7aGnvNKsW8oxLAM+9OLkk21QMSZXmr6YE2PDesUL2PdqobSidPTaLBaGpC
> KdR1vkEyQfeRFOfTLqxR6e09vaq6ks+ASKQTrx4X/NGAv5eQhSFJFhKu2pZzeVgk
> dM8X1wFMYC06KkrkE3Lpj12im29bqV21eMR7ZS7TmJloLw522wLPH/Whs4pHGxTE
> TV8kFzg1Fm7uKrmCwmdJ8AhbVLXBWOUtVsaXkA0nMP9guVyf+sqBk6LnxL43g2gS
> 354zxuGFyNUxpKjxivuQ9bgH2Wx4xoC4b07Zoqok99ETAUhIEkWj7SYrZzwOl3Su
> 3l3s0r+3YTVO6jlgcxvnQYUQWkpntiFG27qFfLYKo7VRkXD3OBUQ1i5Ib2ID+u7F
> zwy49HwNiezXz5CRtVhjgNQDCnLvonJM/nvkdN80zZ5FbIBK2euCABehAmO/zkBp
> S2gUO+k6PwawcYHdFlet7Qe3SSBqdaJ74jJTJwvkZh6SW777XNrJeIz1S0Q1UfnW
> AL6eMDCZhrVXD7HD9CtME3LMCz/BNEyAAGb02ZYE9bqkSh9sypUDRJ/GnrxgmdeM
> tXQbkOqcpqmc4ef4eWZDg/RDOehv1VlsRASCX6qLbiHjPYrwUAkCAWRjQS+kj+35
> 02/R8CPf/W+jZObekyY6
> =ZfE3
> -----END PGP SIGNATURE-----
> Back to top
> Implications of switching to Hardware Memory Virtualization for all AppVMs
> pixel fairy <pixel...@gmail.com>: Aug 17 10:55AM -0700
>
> Just confirmed 3.2rc2 does not work in vmware-fusion.
>  
> theres something ironic about a compartmentalization platform built on
> virtualization being so hard to run in virtualization.
> Back to top
> [PATCH] 3.2rc2 - fix missing trailing backslash in qvm-backup-restore
> Ivan <iv...@c3i.bg>: Aug 17 02:39PM +0300
>
> qvm-backup-restore in 3.2rc2 fails with:
>  
>  
> File "/usr/bin/qvm-backup-restore", line 288
> "a new directory named "\
> ^
> IndentationError: unexpected indent
>  
>  
> Cause: missing backslash on line 287. Trivial patch attached.
>  
> Side question: what is the preferred way to report such things: send a
> patch/email to qubes-devel like now, create an issue on github, or clone
> the repo/fix the file and send a pull request ?
>  
> ivan
> Marek Marczykowski-Górecki <marm...@invisiblethingslab.com>: Aug 17 01:51PM +0200
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>  
> On Wed, Aug 17, 2016 at 02:39:50PM +0300, Ivan wrote:
> > ^
> > IndentationError: unexpected indent
>  
> > Cause: missing backslash on line 287. Trivial patch attached.
>  
> Applied, thanks!
>  
> > Side question: what is the preferred way to report such things: send a
> > patch/email to qubes-devel like now, create an issue on github, or clone the
> > repo/fix the file and send a pull request ?
>  
> Whichever method you prefer. Pull requests are slightly easier to handle
> (especially because you see a list of them and its harder to miss it).
> Patches are always better than just reports ;)
>  
> - --
> 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
>  
> iQEcBAEBCAAGBQJXtE/AAAoJENuP0xzK19csOb8H/RtwB4cR7qYgx/sITxmnQvl0
> 9Hh7yeOiWtIX7/Pzf3S9C7CedVwNII+an4L54FdfknHWEcfgVXr3+mA0fqxuhq1B
> joASZKRSEUXhSUURtpOq1t1qrpArHoA7I3rnpb2soWJ4+h8mHITxbNP2cVOuImnQ
> heNdfFWNC84QGaHb4OMJC86FOnYA7t9SRo5v0f5JQn3SG3FHdzwtV2yi1jECD7ne
> rvezHaXcOy3rxKKC7j79A4rZ7/Y80YJEMZZ3Eu2BfKPYVwhMwN8AP4we23JDgu+g
> /OmSpylhcGtHrNXpDDsgyoIoK1d0G2N5qq310d1rFltqCquC456Ofr6lfsz/RNg=
> =GKes
> -----END PGP SIGNATURE-----
> Back to top
> You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
> To unsubscribe from this group and stop receiving emails from it send an email to qubes-devel...@googlegroups.com.

Reply all
Reply to author
Forward
0 new messages