Tails

#3 Updated by intrigeri 2019-03-16 16:47:03

segfault wrote:
> I fixed a typo, beside that the code review passes

@segfault, is there anything else you plan to do here? It looks like this fix has been waiting for a while on your plate after that successful review.

#8 Updated by segfault 2019-04-12 10:08:22

I fixed the duplicate StartupNotify=true entry, released a new version, built a new Debian package and tested it. Now in order to use this new Debian packgage, we would have to install onioncircuits from our own repo, which we currently don’t do. Should I prepare a branch for that?

#9 Updated by intrigeri 2019-04-12 10:10:38

> Now in order to use this new Debian packgage, we would have to install onioncircuits from our own repo, which we currently don’t do. Should I prepare a branch for that?

Yes. In that branch you can run ./bin/add-APT-overlay then upload your package to the corresponding APT (overlay) suite.

#10 Updated by segfault 2019-04-12 10:32:50

intrigeri wrote:
> > Now in order to use this new Debian packgage, we would have to install onioncircuits from our own repo, which we currently don’t do. Should I prepare a branch for that?
>
> Yes. In that branch you can run ./bin/add-APT-overlay then upload your package to the corresponding APT (overlay) suite.

Oh that I already did, in order to test the package. What I meant is a branch to merge into devel/stable in order to have the new Debian package in the next Tails release. For that we would have to add a pin to origin deb.tails.boum.org in config/chroot_apt/preferences, right?

#12 Updated by intrigeri 2019-04-12 11:49:57

>> Yes. In that branch you can run ./bin/add-APT-overlay then upload your package to the corresponding APT (overlay) suite.

> Oh that I already did, in order to test the package.

Hmmm, something went wrong. This tells me the APT suite is empty:

ssh reprepro@incoming.deb.tails.boum.org reprepro list feature-16350-onioncircuits-opening-feedback

And I see no version newer than 0.3-0tails2 when I run:

ssh reprepro@incoming.deb.tails.boum.org reprepro ls onioncircuits

This may invalidate the tests you did already on an image built from this branch.

On the server, /var/log/incoming-tails.log says No distribution found for 'onioncircuits_0.6-0.0tails1_amd64.changes'! and incoming/onioncircuits_0.6-0.0tails1_amd64.changes has Distribution: feature-16350-onioncircuits-opening-feedback, which is correct. So I think you uploaded before the cronjob created that APT suite. I’ve touch’ed the .changes file to force inotify+reprepro to process it again and now your package been imported :)

Then I’ve triggered a new build on https://jenkins.tails.boum.org/view/Tails_ISO/job/build_Tails_ISO_feature-16350-onioncircuits-opening-feedback/9/

> What I meant is a branch to merge into devel/stable in order to have the new Debian package in the next Tails release. For that we would have to add a pin to origin deb.tails.boum.org in config/chroot_apt/preferences, right?

I believe our existing catch-all APT pinning is sufficient, as long as the package’s version is greater than the one from Debian. The .packages file for the aforementioned Jenkins build will tell.

#13 Updated by segfault 2019-04-12 12:40:53

intrigeri wrote:
> >> Yes. In that branch you can run ./bin/add-APT-overlay then upload your package to the corresponding APT (overlay) suite.
>
> > Oh that I already did, in order to test the package.
>
> Hmmm, something went wrong. This tells me the APT suite is empty:
>
> […]
>
> And I see no version newer than 0.3-0tails2 when I run:
>
> […]
>
> This may invalidate the tests you did already on an image built from this branch.

It might be that the image I tested this with did not have the correct onioncircuits version installed, because I just noticed that I also get visual feedback when I open the old onioncircuits version (cursor spins, icon and name appear in top bar). This seems to be because the line StartupNotify=true was already present in the .desktop file, and a StartupWMClass line was also already there. Now I wonder how all the work it took to build and use this package compares to the benefit we get from it (fixing a typo in the StartupWMClass).

#16 Updated by intrigeri 2019-04-13 05:15:33

@segfault, I’ve thus merged stable into devel and in turn, devel into feature/buster.

Thanks!