Re: [Tails-dev] Tor Monitor build fails
Alan: Hi Alan, > Sascha Steinbiss wrote: >> I can build everything perfectly directly after cloning: >> >> [vagrant@debian-8:~] $ git clone https://github.com/satta/tor-monitor.git >> Cloning into 'tor-monitor'... >> remote: Counting objects: 153, done. >> remote: Compressing objects: 100% (74/74), done. >> remote: Total 153 (delta 78), reused 145 (delta 70), pack-reused 0 >> Receiving objects: 100% (153/153), 32.71 KiB | 0 bytes/s, done. >> Resolving deltas: 100% (78/78), done. >> Checking connectivity... done. >> [vagrant@debian-8:~] $ cd tor-monitor >> [vagrant@debian-8:~/tor-monitor] $ gbp buildpackage --git-pbuilder -uc -us >> gbp:info: tor-monitor_0.1.orig.tar.gz does not exist, creating from >> 'upstream/0.1' >> Building with cowbuilder for distribution sid >> I: using cowbuilder as pbuilder >> […] >> >> As you can see, the tarball is created if it does not exist. Does this work >> for you? >> > No, it doesn't work under Tails (based on wheezy), but I tried under > jessie and the build starts... but then I hit: > > $ gbp buildpackage --git-dist=jessie --git-arch=i386 --git-pbuilder -uc -us > gbp:info: Building with pbuilder for jessie > Building with pbuilder for distribution jessie, architecture i386 > I: using pbuilder as pbuilder > dpkg-buildpackage: source package tor-monitor > dpkg-buildpackage: source version 0.1-1 > dpkg-buildpackage: source distribution unstable > dpkg-buildpackage: source changed by Sascha Steinbiss > dpkg-source --before-build tor-monitor-packaging > fakeroot debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_testdir -O--buildsystem=pybuild >debian/rules override_dh_auto_clean > make[1]: Entering directory 'XXX/tor-monitor-packaging' > rm -f po/tormonitor.pot > rm -rf build > make[1]: Leaving directory 'XXX/tor-monitor-packaging' >dh_clean -O--buildsystem=pybuild > dpkg-source -b tor-monitor-packaging > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building tor-monitor using existing > ./tor-monitor_0.1.orig.tar.gz > dpkg-source: warning: file tor-monitor-packaging/tormonitor.desktop has no > final newline (either original or modified version) > dpkg-source: info: local changes detected, the modified files are: > tor-monitor-packaging/tormonitor.desktop > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/tor-monitor_0.1-1.diff.3aQP6Q > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b tor-monitor-packaging gave error > exit status 2 > gbp:error: 'git-pbuilder -uc -us' failed: it exited with 2 > What's in the diff /tmp/tor-monitor_0.1-1.diff.3aQP6Q? Only this? > dpkg-source: warning: file tor-monitor-packaging/tormonitor.desktop has no final newline (either original or modified version) > dpkg-source: info: local changes detected, the modified files are: > tor-monitor-packaging/tormonitor.desktop ? Is this something which could have happened due to some editor configuration on your machine? 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.
tails-dev@boum.org
Dear Product Manager, Greetings from Nikita in Yeastar. Good to know you are in telecommunication field. We happen to specialize in design in production of IP PBX and VoIP gateways for SMB since 2006. Sincerely hope to establish business relationship with you. Call me and let's talk more. Nikita Wei Business Development Manager Tel: 865925503309ext6250 Fax:865925503307 Skype ID: yeastar.nikita ___ 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] An idea
emmapeel: > gil.guil...@free.fr: >> Hello, >> >> I had another idea : and what about Tails for smartphones ? because >> smartphones are small computers and can also be compromised by bad software. >> > See https://labs.riseup.net/code/issues/6064 > > Please have a look at the documentation/bug tracker before sending > suggestions, as many things have been already discussed... I'm not sure the current status of things is well documented on the website. At least searching for "smartphone" on the website doesn't return anything useful. Before being technically possible to run Tails on smartphone, we want to work on having Tails working on tablets and we have some testing results here: https://tails.boum.org/blueprint/handheld/ ___ 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] Bogons/Iptables - add 224.0.0.0/4 and (some) others, please!
Hi Jason, Jason Nesmith wrote (14 Sep 2015 12:48:15 GMT) : > Please add to iptables the list of Bogons: > https://www.team-cymru.org/Services/Bogons/bogon-bn-nonagg.txt > 2 or 3 of them are already there, but missing are some important ones which > need blocking like 224.0.0.0/4 ! Could you please clarify what specific problem this solution would address? 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] Testing with openqa?
Alan wrote (23 Aug 2015 13:28:41 GMT) :
> but I encourage the people working on the test suite to have a look
> at OpenQA and consider wether it would make sense to use it. It has
> a nice web interface to update screenshots, and we would share
> maintenance with other distros.
I've had a look during DebConf, and indeed the web interface for
developers is much better than what Jenkins will give us as-is.
Perhaps at some point we'll need $something that extracts data from
Jenkins and presents it to developers, and at that point it may be
worth looking into OpenQA.
Note that tests are written directly in Perl, with no overlay language
like Gherkin. Not as if we were taking much benefit from Gherkin for
{intra,inter}-team communication yet, but I like it that we're able to;
and I intend to try to use Gherkin more in the future when discussing
changes with UX folks.
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] [PATCH] config/amnesia: use --show-field over sed filtering.
Hi, On Tue, Sep 15, 2015 at 10:29:02AM +0200, intrigeri wrote: > > I think you (anonym) have fixed the Vagrant bits on #9262 already, and > the only blocker left now is #7642, that bertagaz committed to work on > (not sure he realized that it was actually blocking #9262 though). Absolutely not. :) I think we had a problem during our summit then, when we added this task to the list of work to do in 2016. So I haven't look that closely to this ticket yet. I'll put that higher in todo, and will try to get something out ASAP. 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] Automated tests specification
bertagaz wrote (03 Sep 2015 08:44:01 GMT) : > On Wed, Sep 02, 2015 at 01:12:39PM +0200, intrigeri wrote: >> I think that's not a blocker for the first iteration, though: if videos >> are added between Oct. 15 and Jan. 15, I'm happy :) >> >> bertagaz, time to create tickets that sum this up, or do we need >> more discussion? > Done, in #10153 and subtickets. Dunno if this parent ticket makes sense, > but I think we'll need one of that kind at some point, and as this > tickets are not blocking for #5288, I preferred this solution. OK. > Shall I add the right deliverable fiels too? Yes, please encode into Redmine the "by January 15" information. 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] Tor Monitor: don't show duplicate streams with the same destination in the same circuit
Alan wrote (14 Sep 2015 11:06:58 GMT) : > After checking how this could be done, I'm really unsure. Replied on the ticket (where you've posted basically the same text). 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] jenkins.t.b.o and nightly.t.b.o downtime
bertagaz wrote (14 Sep 2015 14:45:26 GMT) : >> I'd appreciate it there were HTTP redirect rules added to keep >> compatibility with already published URLs. > Where can I get such a list of published URLs? There is no such list, and I'd rather not hardcode an exact list. The ones I'd like to keep working are: http://nightly.tails.boum.org/build_Tails_ISO_*/latest.iso So I suggest using a wildcard, regexp, or whatever the web server config supports to this aim. 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] [PATCH] Change syslinux menu entries from "Live" to "Boot"
Hi, [not sure why Chris and -ux@ are not Cc'ed anymore, but well] sajolida wrote (12 Sep 2015 14:04:16 GMT) : > We're talking about the "future" Greeter here. Where we already agree on > saying "Start Tails". We wanted to avoid having the same label on two > different screen (and feelings like "What! Didn't I started Tails > already in the previous screen?"). For the curious (and to avoid having the same discussion again): This wording decided there: https://mailman.boum.org/pipermail/tails-ux/2015-January/000204.html And then I expressed some concerns with how this terminology integrates with the bigger picture on https://labs.riseup.net/code/issues/8776, where apparently I was painful enough to piss off sajolida, who still was wise enough to turn the problem into something that needs to be user-tested: https://labs.riseup.net/code/issues/8238 (which will need to have the doc updated accordingly, by the way). 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] Tails contributors meeting: Saturday October 03
Hi, On Tue, Sep 15, 2015 at 12:00:01AM -0700, sajolida wrote: > The next Tails contributors meeting is scheduled for: > > Saturday 03 October > #tails-dev on irc.oftc.net >9 pm in Paris >8 pm in London >3 pm in New-York > 12 pm in San Francisco I won't be able to attend, sorry. 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] Newer version of Tor in Tails
bertagaz wrote (09 Sep 2015 22:48:42 GMT) : > Great! We don't have that kind of integration branch right now. Indeed, and we should fix that. Filed #10197 and friends to track it. anonym, do you want to give it a first try with your RM hat on, after 1.6 is out? > May you keep us informed if you find any issue? Note that the package found in Tor's APT repo differs a bit from the one we ship: https://tails.boum.org/contribute/release_process/tor/ 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] [PATCH] config/amnesia: use --show-field over sed filtering.
Hi, anonym wrote (09 Sep 2015 00:33:25 GMT) : >> config/amnesia: use --show-field over sed filtering. > Unfortunately -S/--show-field isn't available in the dpkg-parsechangelog > available in Debian Wheezy, and we still want to support building Tails > on that target (notably since our Vagrant-based build system still is stuck > on that > version). I think you (anonym) have fixed the Vagrant bits on #9262 already, and the only blocker left now is #7642, that bertagaz committed to work on (not sure he realized that it was actually blocking #9262 though). > We should naturally do this move once we stop > supporting that target. Right ⇒ I've applied Chris' patch on the branch that ports our build system to Jessie (feature/9262-build-on-jessie). Yay, thanks! By the way, it seems that we have a similar construct (dpkg-parsechangelog | awk '/^Version: /) in other files: * auto/scripts/tails-custom-apt-sources (used at build time, so it could go on the same branch) * features/step_definitions/build.rb (used when running the test suite, which requires Jessie already) 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.
[Tails-dev] Tails contributors meeting: Saturday October 03
The next Tails contributors meeting is scheduled for: Saturday 03 October #tails-dev on irc.oftc.net 9 pm in Paris 8 pm in London 3 pm in New-York 12 pm in San Francisco Everyone interested in contributing to Tails is welcome! Feel free to propose and prepare discussion topics. Either: - Raise them in this thread so that others can ask details and prepare the discussion too. - Update the blueprint of the agenda: https://tails.boum.org/blueprint/monthly_meeting/ - Make sure that the discussion tickets that you want to treat during the meeting are well detailed on Redmine. If you want to get involved but don't know yet how, please introduce yourself during the meeting, and be sure to tell us what you are interested in. The meeting might not be the most adequate time and place to properly introduce newcomers to the development process, but at least it should be a fine place to know each others, and schedule a better suited event. ___ 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.
