[new] net/i2pd 2.25.0
Hi, This would be my first port, but I've actually read the documentation and think I got it right. Not totally sure about the PLIST but hopefully someone can point out my mistakes. I plan to update the i2pd source for OpenBSD so this port can lose it's current patch, but since the release was made before the port was written it's needed for now. This can be considered as a official port from the project. I don't have CVS access so I would need someone here to actually submit it. Best regards, Mikal Villa / Meeh net-i2pd.tar.bz2 Description: BZip2 compressed data
Re: [new] net/i2pd 2.25.0
Hi, Since my first request the 2.26.0 release was done so I've also updated the port. Can't seem to have gotten any replies on it, is there nobody that has time to help me verify & import to cvs? I've attached the updated port. Best regards, Mikal Villa On 06/06/2019 12:00, Mikal Villa wrote: > Hi, > > This would be my first port, but I've actually read the documentation > and think I got it right. Not totally sure about the PLIST but hopefully > someone can point out my mistakes. > > I plan to update the i2pd source for OpenBSD so this port can lose it's > current patch, but since the release was made before the port was > written it's needed for now. This can be considered as a official port > from the project. > > I don't have CVS access so I would need someone here to actually submit it. > > > Best regards, > Mikal Villa / Meeh > net-i2pd-2.26.tar.bz2 Description: BZip2 compressed data
Re: [new] net/i2pd 2.25.0
Hi,
Thanks a lot for your reply and corrections of the port. And yea, you're
probably right about
giving it a small description, I was way to focused about just trying to
get the port as correct
as possible that it didn't even occur to me.
So, what is it and why should you care?
I2P is short for Invisible Internet Project and it's a mix-network with
many similarities with the Tor network.
However some main differences is that instead of using centralized
directory servers which Tor does, I2P
has it's own DHT network, and routers have to learn themself which are
good relays and not. So Tor has a
faster bootup, but I2P is fully decentralizd. Both project where started
up ~16-17 years ago, however I2P
is much less known than Tor, and while Tor has had much focus on
out-proxying back to the internet, I2P
has had focus on hidden services and applications inside the network
which never leaves back to the internet.
I2P also has a very simple naming system, so you can have addresses like
planet.i2p and stats.i2p instead of
something similar to ouad893ou4fj09fe0f.onion. (Yes, that was just me
baning on the keyboard)
Again, thanks a lot for your tip and corrections of the port Stuart!
Best regards,
Mikal Villa
On 11/06/2019 13:42, Stuart Henderson wrote:
> On 2019/06/11 10:27, Mikal Villa wrote:
>> Hi,
>>
>> Since my first request the 2.26.0 release was done so I've also updated
>> the port.
>>
>> Can't seem to have gotten any replies on it, is there nobody that has
>> time to help me verify & import to cvs?
>>
>> I've attached the updated port.
>>
>>
>>
>> Best regards,
>> Mikal Villa
>>
>> On 06/06/2019 12:00, Mikal Villa wrote:
>>> Hi,
>>>
>>> This would be my first port, but I've actually read the documentation
>>> and think I got it right. Not totally sure about the PLIST but hopefully
>>> someone can point out my mistakes.
>>>
>>> I plan to update the i2pd source for OpenBSD so this port can lose it's
>>> current patch, but since the release was made before the port was
>>> written it's needed for now. This can be considered as a official port
>>> from the project.
>>>
>>> I don't have CVS access so I would need someone here to actually submit it.
>>>
>>>
>>> Best regards,
>>> Mikal Villa / Meeh
>>>
> It often helps a bit to describe the port in the email so readers can
> see if they might be interested in it.
>
> Updated tar attached with some cleanup, which I'll explain inline with the
> diff below. It is in better shape like this but I don't particularly want
> to run it for further tests so will leave it to someone else to pick up
> if they're interested.
>
>
> : diff --git a/Makefile b/Makefile
> : index 4ac5ff7..984070d 100755
> : --- a/Makefile
> : +++ b/Makefile
> : @@ -1,48 +1,42 @@
> : # $OpenBSD$
> :
> : -GH_ACCOUNT =PurpleI2P
> : -GH_PROJECT =i2pd
> : -GH_TAGNAME =2.26.0
> : -DISTNAME = i2pd-${GH_TAGNAME}
> : +COMMENT = client for the I2P anonymous network
> : +
> : +GH_ACCOUNT = PurpleI2P
> : +GH_PROJECT = i2pd
> : +GH_TAGNAME = 2.26.0
>
> spaces->tabs
> DISTNAME is set to $GH_PROJECT-$GH_TAGNAME by default, no need to set it
> separately
>
> : +
> : CATEGORIES = net
> : HOMEPAGE = https://i2pd.website
> : -COMMENT = full-featured C++ inplementation of a I2P router
>
> move up to standard position (see Makefile.template), reword a bit
> (keeping COMMENT simple, describing in DESCR)
>
> :
> : MAINTAINER = Mikal Villa
> :
> : -# BSD 3-clause
> : +# BSD
>
> standard in ports tree
>
> : -PERMIT_PACKAGE_CDROM = Yes
> : +PERMIT_PACKAGE = Yes
>
> this is gradually being replaced in the ports tree
>
> : +WANTLIB += ${COMPILER_LIBCXX} boost_date_time-mt boost_filesystem-mt
> : +WANTLIB += boost_program_options-mt boost_system-mt c crypto m
> : +WANTLIB += ssl z
> :
> : -WANTLIB = ${COMPILER_LIBCXX} boost_date_time boost_filesystem \
> : - boost_program_options boost_system c crypto m ssl z
> : +COMPILER = base-clang ports-gcc
> : +MODULES = devel/cmake
>
> you already patch the cmake file, and it has an install target, and
> installs the headers for the library, so might as well use it.
>
> : LIB_DEPENDS = devel/boost
> :
> : -COMPILER =base-clang ports-gcc base-gcc
>
> boost needs a c++11 compiler already so no point having base-gcc in this list
>
> : -USE_GMAKE =Yes
> : -SUBST_VARS += VARBASE
>
> should use LOCALSTATEDIR which is already
Re: update www/tor-browser on stable
Hi,
Just wanna mention that i2p has started a browser project as well, and
*if* my i2pd port gets accepted into your ports repo, I would continue
with a
port for the i2p browser (currently beta3) which downstreams tor-browser
with it's own i2p patches so it works on both networks but also contain all
privacy patches that tbb does. It's fair to mention I'm the lead
dev/maintainer
on that sub-project for i2p. And since I wanted to test openbsd on a laptop
and not just servers/routers, I suddenly got a self interest in a
openbsd build.
/Mikal
On 15/06/2019 00:52, George Rosamond wrote:
>
> Solene Rapenne:
>> I propose applying the following www/tor-browser update on 6.5-stable
>> (it's the exact same patch than on current)
>>
>> tor-browser on 6.5 has the same bug that hit firefox last month,
>> extensions are disabled.
> Yes, but Tor Browser 8.0.9 is now deprecated, and 8.5.1 is the current one.
>
> https://blog.torproject.org/new-release-tor-browser-851
>
> g
>
>> Tested, works well.
>>
>>
>> Index: ports/www/tor-browser/Makefile.inc
>> diff -u ports/www/tor-browser/Makefile.inc:1.15
>> ports/www/tor-browser/Makefile.inc:1.17
>> --- ports/www/tor-browser/Makefile.inc:1.15 Sat Oct 6 00:02:12 2018
>> +++ ports/www/tor-browser/Makefile.inc Thu May 9 08:31:17 2019
>> @@ -1,4 +1,4 @@
>> -# $OpenBSD: Makefile.inc,v 1.15 2018/10/05 22:02:12 sthen Exp $
>> +# $OpenBSD: Makefile.inc,v 1.17 2019/05/09 06:31:17 landry Exp $
>>
>> MAINTAINER ?= Sean Levy
>> HOMEPAGE ?= https://www.torproject.org
>> @@ -6,7 +6,7 @@
>> PERMIT_PACKAGE_CDROM ?= Yes
>> CATEGORIES =www
>> BROWSER_NAME = tor-browser
>> -TB_VERSION =8.0.2
>> +TB_VERSION =8.0.9
>> TB_PREFIX = tb
>>
>> SUBST_VARS += BROWSER_NAME TB_VERSION
>> Index: ports/www/tor-browser/browser/Makefile
>> diff -u ports/www/tor-browser/browser/Makefile:1.31
>> ports/www/tor-browser/browser/Makefile:1.32
>> --- ports/www/tor-browser/browser/Makefile:1.31 Mon Mar 11 20:04:38 2019
>> +++ ports/www/tor-browser/browser/Makefile Wed May 1 19:36:30 2019
>> @@ -1,4 +1,4 @@
>> -# $OpenBSD: Makefile,v 1.31 2019/03/11 19:04:38 semarie Exp $
>> +# $OpenBSD: Makefile,v 1.32 2019/05/01 17:36:30 landry Exp $
>> # Some of this comes from www/firefox-esr as apropos, since Tor
>> # browser is a fork of ESR. It is a good idea to look at that
>> # Makefile when editing this one (ESR versions not always the same).
>> @@ -9,7 +9,6 @@
>> MOZILLA_VERSION = ${TB_VERSION}
>> MOZILLA_PROJECT = ${BROWSER_NAME}
>> MOZILLA_CODENAME = browser
>> -REVISION = 0
>>
>> EXTRACT_SUFX = .tar.gz
>> PATCHORIG = .pat.orig
>> @@ -17,7 +16,7 @@
>> PKGNAME = ${TB_PREFIX}-browser-${TB_VERSION}
>> DISTNAME = ${BROWSER_NAME}-${TB_VERSION}
>>
>> -SO_VERSION =3.0
>> +SO_VERSION =4.0
>> MOZILLA_LIBS = xul clearkey lgpllibs mozavcodec mozavutil
>> mozgtk
>> MOZILLA_LIBS += freebl3 nss3 nssckbi nssdbm3
>> MOZILLA_LIBS += nssutil3 smime3 softokn3 ssl3
>> Index: ports/www/tor-browser/browser/distinfo
>> diff -u ports/www/tor-browser/browser/distinfo:1.14
>> ports/www/tor-browser/browser/distinfo:1.16
>> --- ports/www/tor-browser/browser/distinfo:1.14 Sat Oct 6 00:02:12 2018
>> +++ ports/www/tor-browser/browser/distinfo Thu May 9 08:31:17 2019
>> @@ -1,2 +1,2 @@
>> -SHA256 (mozilla/tor-browser-8.0.2.tar.gz) =
>> 0jsZDX8VhqhTF4ZHPaCXgqnZWzDS1QHIY0LncLuuYks=
>> -SIZE (mozilla/tor-browser-8.0.2.tar.gz) = 385480115
>> +SHA256 (mozilla/tor-browser-8.0.9.tar.gz) =
>> B2YOSrwnXSihuHRczush6oYeo9LPFSJGNqoTlE3cmAI=
>> +SIZE (mozilla/tor-browser-8.0.9.tar.gz) = 387604509
>> Index:
>> ports/www/tor-browser/browser/patches/patch-build_moz_configure_init_configure
>> diff -u
>> ports/www/tor-browser/browser/patches/patch-build_moz_configure_init_configure:1.2
>>
>> ports/www/tor-browser/browser/patches/patch-build_moz_configure_init_configure:removed
>> ---
>> ports/www/tor-browser/browser/patches/patch-build_moz_configure_init_configure:1.2
>>Wed Oct 3 16:55:36 2018
>> +++
>> ports/www/tor-browser/browser/patches/patch-build_moz_configure_init_configure
>>Fri Jun 14 22:56:32 2019
>> @@ -1,24 +0,0 @@
>> -$OpenBSD: patch-build_moz_configure_init_configure,v 1.2 2018/10/03
>> 14:55:36 sthen Exp $
>> -
>> -Fix build with rust 1.29.
>> -https://hg.mozilla.org/mozilla-central/rev/36f4ba2fb6f5
>> -https://hg.mozilla.org/releases/mozilla-esr60/rev/381ae910e9b2712699fdc6a9bb9702c04bccb8f5
>> -
>> -Index: build/moz.configure/init.configure
>> build/moz.configure/init.configure.orig
>> -+++ build/moz.configure/init.configure
>> -@@ -577,7 +577,13 @@ def split_triplet(triplet, allow_unknown=False):
>> - # There is also a quartet form:
>> - # CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM
>> - # But we can consider the "KERNEL-OPERATING_SY
Re: [new] net/i2pd 2.25.0
Hi,
Thanks for your reply and OK Rafael! I've updated with sthen@'s changes,
however I have also updated the port to don't have the need for cmake,
and it now install client application headers and the static libraries
needed from i2pd to build a client app. Thus, I also removed the test he
added but I think this flavor is better (less dependencies versus test).
i2pd has a few unit tests but I can ensure you that Orignal the main dev
will not put of time for some tests at least not this year.
Regarding the cmake and why it was there, the reason for this was that I
took the "less broken" attempt to port i2pd to OpenBSD and changed it
just to get started into the ports system.
However, gotten far much better known with the ports system now I decided
to try without it, since I recalled we had a Makefile.bsd and which was
still working great.
Also I noticed I didn't get my thunderbird to work with the text and line
breaks in the mailing list, so this would be my first neomutt/mutt email
ever. So I'll resend and fixup my mistakes like, if I for example
messes up with the attachment.
Hopefully I don't bug you all with the horrible line breaks anymore :)
/Mikal
On 15/06/2019, 12:04, Rafael Sadowski wrote:
Please find attached a new tarball based on sthen@ work which fix the
test build.
Since there have been a lot of requests for this port and this one looks
fine for me. OK rsadowski@
On Thu Jun 13, 2019 at 06:19:33AM +0200, Mikal Villa wrote:
Hi,
Thanks a lot for your reply and corrections of the port. And yea, you're
probably right about
giving it a small description, I was way to focused about just trying to
get the port as correct
as possible that it didn't even occur to me.
So, what is it and why should you care?
I2P is short for Invisible Internet Project and it's a mix-network with
many similarities with the Tor network.
However some main differences is that instead of using centralized
directory servers which Tor does, I2P
has it's own DHT network, and routers have to learn themself which are
good relays and not. So Tor has a
faster bootup, but I2P is fully decentralizd. Both project where started
up ~16-17 years ago, however I2P
is much less known than Tor, and while Tor has had much focus on
out-proxying back to the internet, I2P
has had focus on hidden services and applications inside the network
which never leaves back to the internet.
I2P also has a very simple naming system, so you can have addresses like
planet.i2p and stats.i2p instead of
something similar to ouad893ou4fj09fe0f.onion. (Yes, that was just me
baning on the keyboard)
Again, thanks a lot for your tip and corrections of the port Stuart!
Best regards,
Mikal Villa
On 11/06/2019 13:42, Stuart Henderson wrote:
> On 2019/06/11 10:27, Mikal Villa wrote:
>> Hi,
>>
>> Since my first request the 2.26.0 release was done so I've also updated
>> the port.
>>
>> Can't seem to have gotten any replies on it, is there nobody that has
>> time to help me verify & import to cvs?
>>
>> I've attached the updated port.
>>
>>
>>
>> Best regards,
>> Mikal Villa
>>
>> On 06/06/2019 12:00, Mikal Villa wrote:
>>> Hi,
>>>
>>> This would be my first port, but I've actually read the documentation
>>> and think I got it right. Not totally sure about the PLIST but hopefully
>>> someone can point out my mistakes.
>>>
>>> I plan to update the i2pd source for OpenBSD so this port can lose it's
>>> current patch, but since the release was made before the port was
>>> written it's needed for now. This can be considered as a official port
>>> from the project.
>>>
>>> I don't have CVS access so I would need someone here to actually submit it.
>>>
>>>
>>> Best regards,
>>> Mikal Villa / Meeh
>>>
> It often helps a bit to describe the port in the email so readers can
> see if they might be interested in it.
>
> Updated tar attached with some cleanup, which I'll explain inline with the
> diff below. It is in better shape like this but I don't particularly want
> to run it for further tests so will leave it to someone else to pick up
> if they're interested.
>
>
> : diff --git a/Makefile b/Makefile
> : index 4ac5ff7..984070d 100755
> : --- a/Makefile
> : +++ b/Makefile
> : @@ -1,48 +1,42 @@
> : # $OpenBSD$
> :
> : -GH_ACCOUNT =PurpleI2P
> : -GH_PROJECT =i2pd
> : -GH_TAGNAME =2.26.0
> : -DISTNAME = i2pd-${GH_TAGNAME}
> : +COMMENT = client for the I2P anonymous network
> : +
> : +GH_ACCOUNT =PurpleI2P
> : +GH_PROJECT =i2pd
> : +GH_TAGNAME =2.26.0
>
> spaces->tabs
&g
[update] net/i2pd 2.28.0
Hi, I've updated i2pd to 2.28.0. Sorry I missed out on 2.27.0, was on a "forced vacation" by my gf :) Attached the ports diff which I hopefully made correct from the cvs util. As usual I have to bug one of you with cvs support to commit it for me until I maybe one day gets it as well :) -- Best regards, Mikal Villa cvs server: Diffing . Index: Makefile === RCS file: /cvs/ports/net/i2pd/Makefile,v retrieving revision 1.1.1.1 diff -u -p -r1.1.1.1 Makefile --- Makefile16 Jun 2019 22:13:55 - 1.1.1.1 +++ Makefile29 Aug 2019 12:48:55 - @@ -4,7 +4,7 @@ COMMENT = client for the I2P anonymous n GH_ACCOUNT = PurpleI2P GH_PROJECT = i2pd -GH_TAGNAME = 2.26.0 +GH_TAGNAME = 2.28.0 CATEGORIES = net HOMEPAGE = https://i2pd.website Index: distinfo === RCS file: /cvs/ports/net/i2pd/distinfo,v retrieving revision 1.1.1.1 diff -u -p -r1.1.1.1 distinfo --- distinfo16 Jun 2019 22:13:55 - 1.1.1.1 +++ distinfo29 Aug 2019 12:48:55 - @@ -1,2 +1,2 @@ -SHA256 (i2pd-2.26.0.tar.gz) = KuGJeMh5a7a0W8jP5OHyU3fgz8n8+fRgVLCdwzhO72M= -SIZE (i2pd-2.26.0.tar.gz) = 1073024 +SHA256 (i2pd-2.28.0.tar.gz) = GBMn7cfPWzwl7lHsxRik2pD6nkIeyiEHmWeRA4pRSiE= +SIZE (i2pd-2.28.0.tar.gz) = 1079208 cvs server: Diffing patches cvs server: Diffing pkg
