Re: [Tails-dev] i2p-0.9.25~Tails-2.3
anonym: > pr0ng: >> I believe I've repackaged the 0.9.25 to 'conform' to the Tails layout >> correctly and will be rebuilding the Tails dev branch with 0.9.25 >> over the next couple of days when I get another block of time, likely >> mid-week ~ 20, 21st? >> >> [...] >> >> Although I am able to explode the .deb from i2p (.25) and repack as >> required I am not yet fully up-to-speed with how I 'release' this after >> testing, so I will refer to zzz for some advice on that matter and if >> you have any pointers on this, please do shout! :) > > [...] > > However, now it seems we'll have a non-official package for Tails. I > wonder, why can we not use the Debian Jessie ones? That makes me think > that Tails, rather, should adapted so the normal deb8 packages can be > installed. Could you please elaborate? So, I have built a Tails image with the 0.9.25-1~deb8u+1 packages from deb.i2p2.no and it seems to work just fine. So what is the purpose of repackaging them into 0.9.25~Tails-2.3 to "conform" to Tails? It doesn't seem necessary on first glance. Cheers! ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] i2p-0.9.25~Tails-2.3
pr0ng:
>
> Hi Tails!
>
>>> We have named pr0ng the new maintainer for I2P in Tails.
>>> Pr0ng has I2P, Tails, and some Debian packaging knowledge,
>
> pr0ng here. I was last contacted via zzz(@i2p) who forwarded me the
> mail from anonym. Nice to be aboard, looking forwards to maintaining
> the i2p system as part of the Tails distribution. :)
I can only repeat (now in public) the following:
>>> Woo! \o/ Welcome aboard, pr0ng!
:)
and has already gotten far enough to be testing I2P 0.9.25
on Tails.
>
>>> Does this mean,
>
>>> 1. install the i2p .deb in a running Tails session, or
>
>>> 2. build a Tails image that have i2p 0.9.25 installed from scratch
>>> [0]?
>
> 1) I was originally testing the .deb running in a Tails session from
> the Ubuntu release I had knocking around, to (a) look at the
> differences between an 'ordinary' installation and one from within
> Tails itself and (b) make sure functionality was as expected.
>
> Since then I have moved onto building Tails from the [0]
> https://tails.boum.org/contribute/build/
>
> Had a few issues with manual build of Tails initially, mostly due to my
> immediate ignorance, but this gave me the opportunity to understand the
> process for a live-build from scratch and correct some of the issues as
> I went along which was a good learning process.
>
> Now I'm happily building Tails 2.2.1 using the Puppet/Vagrant setup you
> documented. I needed to go through these steps initially to feel
> comfortable with the tools, requirements etc.
Cool! Do not be afraid to ask before spending too much time trying to
figure these things out. The current state of the vagrant build setup is
a bit crap, but we're in the process of migrating it from VirtualBox to
libvirt/KVM and will from them on maintain it better so things will
likely get easier.
> I believe I've repackaged the 0.9.25 to 'conform' to the Tails layout
> correctly and will be rebuilding the Tails dev branch with 0.9.25 over
> the next couple of days when I get another block of time, likely
> mid-week ~ 20, 21st?
>
> I've (just today) subscribed to the tails-dev@boum.org mailing list and
> expect I'll be able to continue updates via this going forward.
You might also want to register an account on our bug tracker:
https://labs.riseup.net/code/projects/tails
> Although I am able to explode the .deb from i2p (.25) and repack as
> required I am not yet fully up-to-speed with how I 'release' this after
> testing, so I will refer to zzz for some advice on that matter and if
> you have any pointers on this, please do shout! :)
Previously this is how it worked: the I2P package maintainer uploads the
official i2p Debian packages to deb.i2p2.no. S/he builds a Tails with
the package for the Debian version Tails is based on (so Jessie at the
moment). If all is ok, s/he creates a ticket ("Import I2P x.y.z") on our
bug tracker, and assigns the ticket to the Release Manager (me,
generally, see our calendar [0]) with "QA Status = Ready for QA". Then I
take over. Makes sense?
[0] https://tails.boum.org/contribute/calendar/ -- essentially, unless
otherwise specified, I'm the RM.
However, now it seems we'll have a non-official package for Tails. I
wonder, why can we not use the Debian Jessie ones? That makes me think
that Tails, rather, should adapted so the normal deb8 packages can be
installed. Could you please elaborate?
>>> Since the 0.9.25 packages are up on deb.i2p2.no already I think we'll
>>> get it into Tails 2.3 (note that it has been delayed until 2016-04-26
>>> due to Mozilla delaying the next Firefox ESR until then). pr0ng, if
>>> you please send an email with your current progress to tails-dev@ and
>>> I'll detail what remains to make that happen -- if you hit a
>>> stumbling block (e.g. building Tails is not so easy at the moment)
>>> I'm sure I can help or even take over parts.
>
> Basically, I just need to read a little more methinx. I will do the
> repack and rebuild mid-week and then come back to you with a request
> for assistance at that point - should this also be directed to the
> mailing list? Happy to do things out in the open, just not sure of
> protocol etc! Will check my mail on i2p now to see if my
> subscription is 'active' and such.
Like I said above, the preferred way to notify us that we should import
some packages are via a new ticket in our bug tracker.
> Pleased to be involved - I'm a big Tails evangelist (as well of course
> of i2p :)) ~ speak shortly
Yay, we'll happy to have you! :)
Cheers!
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] i2p-0.9.25~Tails-2.3
Hi, pr0ng: Yay for Tails and i2p! Wordlife, Spencer ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] i2p-0.9.25~Tails-2.3
Hi Tails! >> We have named pr0ng the new maintainer for I2P in Tails. >> Pr0ng has I2P, Tails, and some Debian packaging knowledge, pr0ng here. I was last contacted via zzz(@i2p) who forwarded me the mail from anonym. Nice to be aboard, looking forwards to maintaining the i2p system as part of the Tails distribution. :) >> Woo! \o/ Welcome aboard, pr0ng! >>> and has already gotten far enough to be testing I2P 0.9.25 >>> on Tails. >> Does this mean, >> 1. install the i2p .deb in a running Tails session, or >> 2. build a Tails image that have i2p 0.9.25 installed from scratch >> [0]? 1) I was originally testing the .deb running in a Tails session from the Ubuntu release I had knocking around, to (a) look at the differences between an 'ordinary' installation and one from within Tails itself and (b) make sure functionality was as expected. Since then I have moved onto building Tails from the [0] https://tails.boum.org/contribute/build/ Had a few issues with manual build of Tails initially, mostly due to my immediate ignorance, but this gave me the opportunity to understand the process for a live-build from scratch and correct some of the issues as I went along which was a good learning process. Now I'm happily building Tails 2.2.1 using the Puppet/Vagrant setup you documented. I needed to go through these steps initially to feel comfortable with the tools, requirements etc. I believe I've repackaged the 0.9.25 to 'conform' to the Tails layout correctly and will be rebuilding the Tails dev branch with 0.9.25 over the next couple of days when I get another block of time, likely mid-week ~ 20, 21st? I've (just today) subscribed to the tails-dev@boum.org mailing list and expect I'll be able to continue updates via this going forward. Although I am able to explode the .deb from i2p (.25) and repack as required I am not yet fully up-to-speed with how I 'release' this after testing, so I will refer to zzz for some advice on that matter and if you have any pointers on this, please do shout! :) >> Since the 0.9.25 packages are up on deb.i2p2.no already I think we'll >> get it into Tails 2.3 (note that it has been delayed until 2016-04-26 >> due to Mozilla delaying the next Firefox ESR until then). pr0ng, if >> you please send an email with your current progress to tails-dev@ and >> I'll detail what remains to make that happen -- if you hit a >> stumbling block (e.g. building Tails is not so easy at the moment) >> I'm sure I can help or even take over parts. Basically, I just need to read a little more methinx. I will do the repack and rebuild mid-week and then come back to you with a request for assistance at that point - should this also be directed to the mailing list? Happy to do things out in the open, just not sure of protocol etc! Will check my mail on i2p now to see if my subscription is 'active' and such. Pleased to be involved - I'm a big Tails evangelist (as well of course of i2p :)) ~ speak shortly Cheers, pr0ng ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] i2p-0.9.25~Tails-2.3
Hi Tails! >> We have named pr0ng the new maintainer for I2P in Tails. >> Pr0ng has I2P, Tails, and some Debian packaging knowledge, pr0ng here. I was last contacted via zzz(@i2p) who forwarded me the mail from anonym. Nice to be aboard, looking forwards to maintaining the i2p system as part of the Tails distribution. :) >> Woo! \o/ Welcome aboard, pr0ng! >>> and has already gotten far enough to be testing I2P 0.9.25 >>> on Tails. >> Does this mean, >> 1. install the i2p .deb in a running Tails session, or >> 2. build a Tails image that have i2p 0.9.25 installed from scratch >> [0]? 1) I was originally testing the .deb running in a Tails session from the Ubuntu release I had knocking around, to (a) look at the differences between an 'ordinary' installation and one from within Tails itself and (b) make sure functionality was as expected. Since then I have moved onto building Tails from the [0] https://tails.boum.org/contribute/build/ Had a few issues with manual build of Tails initially, mostly due to my immediate ignorance, but this gave me the opportunity to understand the process for a live-build from scratch and correct some of the issues as I went along which was a good learning process. Now I'm happily building Tails 2.2.1 using the Puppet/Vagrant setup you documented. I needed to go through these steps initially to feel comfortable with the tools, requirements etc. I believe I've repackaged the 0.9.25 to 'conform' to the Tails layout correctly and will be rebuilding the Tails dev branch with 0.9.25 over the next couple of days when I get another block of time, likely mid-week ~ 20, 21st? I've (just today) subscribed to the tails-dev@boum.org mailing list and expect I'll be able to continue updates via this going forward. Although I am able to explode the .deb from i2p (.25) and repack as required I am not yet fully up-to-speed with how I 'release' this after testing, so I will refer to zzz for some advice on that matter and if you have any pointers on this, please do shout! :) >> Since the 0.9.25 packages are up on deb.i2p2.no already I think we'll >> get it into Tails 2.3 (note that it has been delayed until 2016-04-26 >> due to Mozilla delaying the next Firefox ESR until then). pr0ng, if >> you please send an email with your current progress to tails-dev@ and >> I'll detail what remains to make that happen -- if you hit a >> stumbling block (e.g. building Tails is not so easy at the moment) >> I'm sure I can help or even take over parts. Basically, I just need to read a little more methinx. I will do the repack and rebuild mid-week and then come back to you with a request for assistance at that point - should this also be directed to the mailing list? Happy to do things out in the open, just not sure of protocol etc! Will check my mail on i2p now to see if my subscription is 'active' and such. Pleased to be involved - I'm a big Tails evangelist (as well of course of i2p :)) ~ speak shortly Cheers, pr0ng ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
