Re: [Tails-dev] Package Tor Monitor
Hi, Alan wrote (17 Aug 2015 23:42:12 GMT) : > Would someone knowledgeable please package: > https://git-tails.immerda.ch/alan/tor-monitor/tag/?id=0.1 Some more bits of info that might help people raise their hand: * Packaging is probably super easy. What we need is *also* someone committed to maintaining the package on the long run. * IMO this should be maintained under the umbrella of the pkg-anonymity-tools team (which is currently understaffed, as one can see by looking at the state of torbrowser-launcher and onionshare). * I've privately asked nodens (who's almost done with packaging our OpenPGP Applet) if he's interested. In any case, I would feel more comfortable if at least 2 people committed to do this. * I'm happy to review and sponsor uploads, but I won't commit to mentor *myself* anyone who would need lots of hand-holding e.g. while learning Debian packaging. But perhaps other Tails people or pkg-anonymity-tools members would be happy to do it :) Cheers, -- intrigeri ___ 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] Package Tor Monitor
Alan: > Would someone knowledgeable please package: > https://git-tails.immerda.ch/alan/tor-monitor/tag/?id=0.1 I don't have the skills to package this but I would be happy to test it in Tails or elsewhere. How can I do that? ___ 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] Package Tor Monitor
Hi, sajolida wrote: > Alan: > > Would someone knowledgeable please package: > > https://git-tails.immerda.ch/alan/tor-monitor/tag/?id=0.1 > > I don't have the skills to package this but I would be happy to test it > in Tails or elsewhere. How can I do that? Clone the git, then follow the instructions in README. Don't hesitate to ask if something is unclear. 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] Package Tor Monitor
Hi, intrigeri wrote: > Alan wrote (17 Aug 2015 23:42:12 GMT) : > > Would someone knowledgeable please package: > > https://git-tails.immerda.ch/alan/tor-monitor/tag/?id=0.1 > > Some more bits of info that might help people raise their hand: > [...] > Please note that I was looking for somebody to prepare a package for Tails, not for Debian, but why not? 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] Package Tor Monitor
Alan wrote (18 Aug 2015 17:33:03 GMT) : > Please note that I was looking for somebody to prepare a package > for Tails, not for Debian, but why not? OK, got it. I would rather avoid a regression here (replacing a tool that's in Debian with one that isn't). Note that Vidalia is not in Jessie, and it's going to be removed from sid soon. Anyway: someone needs to do the initial packaging :) Cheers, -- intrigeri ___ 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] Package Tor Monitor
intrigeri: > Hi, > > Alan wrote (17 Aug 2015 23:42:12 GMT) : >> Would someone knowledgeable please package: >> https://git-tails.immerda.ch/alan/tor-monitor/tag/?id=0.1 > > Some more bits of info that might help people raise their hand: > > * Packaging is probably super easy. What we need is *also* someone >committed to maintaining the package on the long run. > * I've privately asked nodens (who's almost done with packaging our >OpenPGP Applet) if he's interested. In any case, I would feel more >comfortable if at least 2 people committed to do this. I would co-maintain this with nodens and if anyone on the list is interested.. i can do some handholding. Cheers! u. ___ 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] Package Tor Monitor
Hi everyone, > I would co-maintain this with nodens and if anyone on the list is > interested.. i can do some handholding. I have been lurking on this ML for a while so I might just break my silence right now. I have done some Debian packaging in the Debian Med team, for now mainly working on bioinformatics software [1] but I would like to broaden my focus a bit. As I've always been interested in privacy enhancing technologies as well, I would like to help out with some additional packaging work if I have the time and given some priority advice (haven't looked at the bugs in pkg-anonymity-tools in detail yet). I'm a DM so you hopefully won't need to sponsor every single update after awhile ;) Long story short, there’s a first version of a tor-monitor package in: https://github.com/satta/tor-monitor It’s quite Debian-style (just build with git-buildpackage) — I am not sure whether you do things much differently in Tails. I can file an ITP if you want it in Debian as well. Looking forward to hear what you think. Cheers Sascha signature.asc Description: Message signed with OpenPGP using GPGMail ___ 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] Package Tor Monitor
Hi Sascha, Sascha Steinbiss: > Hi everyone, > >> > I would co-maintain this with nodens and if anyone on the list is >> > interested.. i can do some handholding. > I have been lurking on this ML for a while so I might just break my > silence right now. > I have done some Debian packaging in the Debian Med team, for now mainly > working on bioinformatics software [1] but I would like to broaden my focus > a bit. As I've always been interested in privacy enhancing technologies > as well, I would like to help out with some additional packaging work if I > have the time and given some priority advice (haven't looked at the bugs in > pkg-anonymity-tools in detail yet). Welcome! > I'm a DM so you hopefully won't need to sponsor every single update after > awhile ;) > Long story short, there’s a first version of a tor-monitor package in: > https://github.com/satta/tor-monitor Awesome! > It’s quite Debian-style (just build with git-buildpackage) — I am not sure > whether you do things much differently in Tails. I can file an ITP if you > want it in Debian as well. Looking forward to hear what you think. In general, we tend to want to use Debian packages and maintain them in Debian, rather than having them only in Tails. So, yes, please file an ITP bug :) What about hosting the packaging in collab-maint? Cheers! u. ___ 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] Package Tor Monitor
Hi, Sascha Steinbiss wrote (19 Aug 2015 21:42:42 GMT) : > [...] I would like to help out with some additional packaging work if I > have the time and given some priority advice (haven't looked at the bugs in > pkg-anonymity-tools in detail yet). Excellent! Please subscribe to pkg-anonymity-tools and let's continue this discussion there. > Long story short, there’s a first version of a tor-monitor package in: > https://github.com/satta/tor-monitor \o/ > It’s quite Debian-style (just build with git-buildpackage) — I am not sure > whether you do things much differently in Tails. I've not looked at it, but generally we (both in Tails and in pkg-anonymity-tools) use the standard gbp workflow, preferably using --upstream-vcs-tag at `gbp import-orig' time. > I can file an ITP if you want it in Debian as well. Yes, please :) Cheers, -- intrigeri ___ 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] Package Tor Monitor
u wrote (20 Aug 2015 09:26:44 GMT) : > What about hosting the packaging in collab-maint? Yes, please (that's what we do for all packages maintained by the pkg-anonymity-tools team). ___ 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] Package Tor Monitor
Le 19/08/2015 23:42, Sascha Steinbiss a écrit : > Hi everyone, > Hi Sascha, welcome ! > Long story short, there’s a first version of a tor-monitor package in: > https://github.com/satta/tor-monitor > > It’s quite Debian-style (just build with git-buildpackage) — I am not sure > whether you do things much differently in Tails. I can file an ITP if you > want it in Debian as well. Looking forward to hear what you think. > Great ! I just I a look at it, and I was wondering : the pot file gets generated at build time, so it would'nt be reproducible without some patches to the build system (change date of potfile generation for the last changelog entry's, or maybe change the upstream work to generate it along with the tarball, and bypass this at debian build time). Maybe we should do something like OpenPGP Applet : create a full upstream project on alioth to hosts tarball, upstream changelog etc, and then use this as a basis for debian package (with a separate repository for debian packaging like suggested before) ? Cheers, -- Clément (nodens) signature.asc Description: OpenPGP digital signature ___ 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] Package Tor Monitor
Hi all, >> It’s quite Debian-style (just build with git-buildpackage) — I am not sure >> whether you do things much differently in Tails. I can file an ITP if you >> want it in Debian as well. Looking forward to hear what you think. > > In general, we tend to want to use Debian packages and maintain them in > Debian, rather than having them only in Tails. > > So, yes, please file an ITP bug :) OK, will do. > What about hosting the packaging in collab-maint? I would be in favour of that as well. However, I only have an Alioth guest account and someone needs to manually add me to the collab-maint project (Debian Med have their own Alioth project). I have requested to join a few weeks ago but received no reply. I can repeat my request directly to one of the admins — could you probably recommend someone? Cheers, Sascha ___ 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] Package Tor Monitor
Hi intrigeri, […] > Excellent! Please subscribe to pkg-anonymity-tools and let's continue > this discussion there. [x] Done. I have subscribed this morning. […] >> It’s quite Debian-style (just build with git-buildpackage) — I am not sure >> whether you do things much differently in Tails. > > I've not looked at it, but generally we (both in Tails and in > pkg-anonymity-tools) use the standard gbp workflow, preferably > using --upstream-vcs-tag at `gbp import-orig' time. Ok. While I have been using Git for a long time, I have done most of my packaging work using Svn up to now. The gbp workflow looks quite polished though, and easy to adopt. Cheers Sascha ___ 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] Package Tor Monitor
Hi Clement, […] > I just I a look at it, and I was wondering : the pot file gets generated > at build time, so it would'nt be reproducible without some patches to > the build system (change date of potfile generation for the last > changelog entry's, or maybe change the upstream work to generate it > along with the tarball, and bypass this at debian build time). Indeed. If it’s just the 'POT-Creation-Date’ entry, wouldn’t it suffice to use faketime? That’s how I made some of my packages with autogenerated PDF manuals build reproducibly, which show a similar timestamp problem. Having upstream generate these separate from the build process would of course be cleaner and preferable. For the time being, I have faketimed the build to the last changelog date and time. See my github repo. > Maybe we should do something like OpenPGP Applet : create a full > upstream project on alioth to hosts tarball, upstream changelog etc, and > then use this as a basis for debian package (with a separate repository > for debian packaging like suggested before) ? Hmm, this would make it possible to create a proper watchfile — the cgit installation on git.tails.boum.org seems to have snapshot tarball creation for tags deactivated. Cheers Sascha signature.asc Description: Message signed with OpenPGP using GPGMail ___ 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] Package Tor Monitor
Sascha Steinbiss wrote (20 Aug 2015 19:37:17 GMT) : > However, I only have an Alioth guest account > and someone needs to manually add me to the collab-maint project Please send me your Alioth handle privately, and I'll see what I can do. Also, let's move this discussion to pkg-anonymity-tools :) Cheers, -- intrigeri ___ 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] Package Tor Monitor
Hi, Clement Hermann wrote: > Le 19/08/2015 23:42, Sascha Steinbiss a écrit : > Hi Sascha, welcome ! > > Long story short, there’s a first version of a tor-monitor package in: > > https://github.com/satta/tor-monitor > > First, thanks a lot! > I just I a look at it, and I was wondering : the pot file gets generated > at build time, so it would'nt be reproducible without some patches to > the build system (change date of potfile generation for the last > changelog entry's, or maybe change the upstream work to generate it > along with the tarball, and bypass this at debian build time). > I'm upstream, so I can do anything you want to ease packaging. Do you want the POT file to be included in 'sdist' tarball? 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] Package Tor Monitor
Hi Alan, […] >> I just I a look at it, and I was wondering : the pot file gets generated >> at build time, so it would'nt be reproducible without some patches to >> the build system (change date of potfile generation for the last >> changelog entry's, or maybe change the upstream work to generate it >> along with the tarball, and bypass this at debian build time). >> > I'm upstream, so I can do anything you want to ease packaging. Do you > want the POT file to be included in 'sdist' tarball? You are definitely more familiar with the internals of the Python distutils steps. I am happy with any solution you propose as long as ‘setup.py build’ does not generate a new POT file on each build (hence updating the timestamp) but reuses a version that is pregenerated by you and committed in your upstream repo. Cheers Sascha ___ 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] Package Tor Monitor
Hi, Sascha Steinbiss wrote: > You are definitely more familiar with the internals of the Python distutils > steps. > I am happy with any solution you propose as long as ‘setup.py build’ does not > generate a new POT file on each build (hence updating the timestamp) > but reuses a version that is pregenerated by you and committed in your > upstream repo. > After reading the documentation and the code of the build system extensions I use to support python desktop applications (python-distutils-extra), I came to the conclusion that your request is not supported. I looked for other similar build systems and fails to find one with similar functionalities. Not as easy as I though... I can whishlist this feature upstream, but that won't solve your short term problem. 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] Package Tor Monitor
Hi, On Mon, Aug 24, 2015 at 10:53:43AM +, Alan wrote: > > After reading the documentation and the code of the build system > extensions I use to support python desktop applications > (python-distutils-extra), I came to the conclusion that your request is > not supported. I looked for other similar build systems and fails to > find one with similar functionalities. Not as easy as I though... > > I can whishlist this feature upstream, but that won't solve your short > term problem. I'm certainly not as knowledgeable as you regarding python and this distutils-extra packaging thing, but I kinda remembered there are ways to deactivate or customize some targets with a setup.cfg file. Some use the [aliases] part of it to have the said used target do what they want. That's a bit hackish though. You may want to look at tahoe-lafs sources for that. Reading http://www.glatzor.de/projects/python-distutils-extra/, it seems you can configure distutils-extra to disable the build_l18n target with such a setup.cfg. Not sure that it's the one responsible of your problem though. bert. ___ 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] Package Tor Monitor
Hi, bertagaz wrote: > Reading http://www.glatzor.de/projects/python-distutils-extra/, it seems > you can configure distutils-extra to disable the build_l18n target with > such a setup.cfg. Not sure that it's the one responsible of your problem > though. > No, because it will not build the .mo files anymore. Look at the code: https://bazaar.launchpad.net/~python-distutils-extra-hackers/python-distutils-extra/debian/view/head:/DistUtilsExtra/command/build_i18n.py#L89 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] Package Tor Monitor
Hi Alan, >> You are definitely more familiar with the internals of the Python distutils >> steps. >> I am happy with any solution you propose as long as ‘setup.py build’ does not >> generate a new POT file on each build (hence updating the timestamp) >> but reuses a version that is pregenerated by you and committed in your >> upstream repo. >> > After reading the documentation and the code of the build system > extensions I use to support python desktop applications > (python-distutils-extra), I came to the conclusion that your request is > not supported. I looked for other similar build systems and fails to > find one with similar functionalities. Not as easy as I though... I see. Thanks for your research! > I can whishlist this feature upstream, but that won't solve your short > term problem. For now I have implemented a simple workaround by just wrapping the python build with faketime, which I feel is sufficient here as this package is not overly complex. So I would say as a short-term solution, the reproducibility issue raised by nodens is addressed. Cheers Sascha ___ 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.
