[Pkg-privacy-maintainers] Bug#824460: Bug#824460: testing using alpha versions?

[Holger Levsen]

On Mon, May 23, 2016 at 12:02:20PM +0200, georg at riseup.net wrote:
> Notes: 
> 
> - I proposed this way to test apparmor profiles etc, which doesn't
>   necessarily check for a smooth upgrade path between different
>   versions. If we would like to do this as well, we would indeed have
>   to keep copies of ~/.local/share/torbrowser/ (and
>   ~/.config/torbrowser/ ?) like intrigeri described.

while it certainly would be great to test the apparmor profiles without
testing upgrades, I'd like to emphasize/repeat that the apparmor
profiles currently are working fine except for the upgrade usecase. Thus
"just" adding tests for the stuff which is non-broken ain't too helpful.

> - Even if one would test using alpha versions, there would have to be a
>   way to do this multiple times in a row, which would mean, as far as I
>   understand the things currently, having some sort of deleting /
>   restoring the directories and running the update(s) again.

yes :)

btw, it looks like Phil is making nice progress extending the cucumber
tests from TAILS to Debian, see eg
https://jenkins.debian.net/view/lvc/job/lvc_debian-8.4.0/52/ (look at
the videos rather than the pngs…)

Once these tests work nicely it should be rather straightforward to
enable apparmor in a VM, install torbrowser-launcher and run it.
And: this framework has snapshotting too…

It would be a long shot, but maybe worth it?


-- 
cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 811 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-privacy-maintainers/attachments/20160523/a7c56067/attachment.sig>