Saverio, it looks I'm using tinc on OpenWRT packaged by you) Thank you for it Is something there in that task, what is harder than https://wiki.openwrt.org/doc/devel/packages ? Anyway, I want to try On Thu, Nov 3, 2016 at 5:57 PM, Guus Sliepen <guus at tinc-vpn.org> wrote:> On Thu, Nov 03, 2016 at 03:43:42PM +0100, Saverio Proto wrote: > > > I am not using OpenWrt a lot anymore, and it is becoming difficult to > > me to test quickly the tinc package and update OpenWrt when a new tinc > > release is out. > > > > does anyone wants to step in as the new package Maintainer ? > > Thank you very much for maintaining the OpenWrt package up to now! > > -- > Met vriendelijke groet / with kind regards, > Guus Sliepen <guus at tinc-vpn.org> > > _______________________________________________ > tinc mailing list > tinc at tinc-vpn.org > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > >-- brgds Maxim Vorontsov -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20161104/c3ebe48d/attachment.html>
Hello Maxim, thanks for stepping in ! so, I am not even sure how it works for commit rights, because the people I was in touch with now forked the project to LEDE. Also, I always committed to OpenWrt packages but I see my commits are there also for LEDE. If you are on the mailing list of the OpenWrt/LEDE community you should understand how this is going to work in the future. I have no idea. Lets make it started like this. Fork in github the package repository: https://github.com/openwrt/packages Make a version bump to tinc 1.0.30 Commit message is like packagename: version bump xxx So in our example: tinc: version bump 1.0.30 also change MAINTAINER:=Saverio Proto <zioproto at gmail.com> to something else. It is important if you make changes and you dont change PKG_VERSION to increase PKG_RELEASE. Also it is important to reset to 1 PKG_RELEASE when upgrading PKG_VERSION. Also it is important to make sure the package compiles before pushing. If you just version bump compile check is enough. If you change init script or other stuff you have to do more testing. After pushing there should still be build bots that compile packages for all ARCH. You can have a look if packages are built for all ARCHs. So for now to get started push your change to github and make a merge request. thank you. Saverio 2016-11-04 19:13 GMT+01:00 Maxim Vorontsov <6012030 at gmail.com>:> Saverio, it looks I'm using tinc on OpenWRT packaged by you) > Thank you for it > > Is something there in that task, what is harder than > https://wiki.openwrt.org/doc/devel/packages ? > > Anyway, I want to try > > > > On Thu, Nov 3, 2016 at 5:57 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: >> >> On Thu, Nov 03, 2016 at 03:43:42PM +0100, Saverio Proto wrote: >> >> > I am not using OpenWrt a lot anymore, and it is becoming difficult to >> > me to test quickly the tinc package and update OpenWrt when a new tinc >> > release is out. >> > >> > does anyone wants to step in as the new package Maintainer ? >> >> Thank you very much for maintaining the OpenWrt package up to now! >> >> -- >> Met vriendelijke groet / with kind regards, >> Guus Sliepen <guus at tinc-vpn.org> >> >> _______________________________________________ >> tinc mailing list >> tinc at tinc-vpn.org >> https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc >> > > > > -- > brgds > Maxim Vorontsov > > _______________________________________________ > tinc mailing list > tinc at tinc-vpn.org > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc >
Hello Maxim, did you send the pull request ? Please send an email to the list when you do thank you Saverio 2016-11-05 10:09 GMT+01:00 Saverio Proto <zioproto at gmail.com>:> Hello Maxim, > thanks for stepping in ! > > so, I am not even sure how it works for commit rights, because the > people I was in touch with now forked the project to LEDE. > > Also, I always committed to OpenWrt packages but I see my commits are > there also for LEDE. > > If you are on the mailing list of the OpenWrt/LEDE community you > should understand how this is going to work in the future. I have no > idea. > > Lets make it started like this. > Fork in github the package repository: > https://github.com/openwrt/packages > > Make a version bump to tinc 1.0.30 > > Commit message is like > packagename: version bump xxx > > So in our example: > tinc: version bump 1.0.30 > > also change MAINTAINER:=Saverio Proto <zioproto at gmail.com> to something else. > > It is important if you make changes and you dont change PKG_VERSION to > increase PKG_RELEASE. Also it is important to reset to 1 PKG_RELEASE > when upgrading PKG_VERSION. > > Also it is important to make sure the package compiles before pushing. > If you just version bump compile check is enough. If you change init > script or other stuff you have to do more testing. > After pushing there should still be build bots that compile packages > for all ARCH. You can have a look if packages are built for all ARCHs. > > So for now to get started push your change to github and make a merge request. > > thank you. > > Saverio > > 2016-11-04 19:13 GMT+01:00 Maxim Vorontsov <6012030 at gmail.com>: >> Saverio, it looks I'm using tinc on OpenWRT packaged by you) >> Thank you for it >> >> Is something there in that task, what is harder than >> https://wiki.openwrt.org/doc/devel/packages ? >> >> Anyway, I want to try >> >> >> >> On Thu, Nov 3, 2016 at 5:57 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: >>> >>> On Thu, Nov 03, 2016 at 03:43:42PM +0100, Saverio Proto wrote: >>> >>> > I am not using OpenWrt a lot anymore, and it is becoming difficult to >>> > me to test quickly the tinc package and update OpenWrt when a new tinc >>> > release is out. >>> > >>> > does anyone wants to step in as the new package Maintainer ? >>> >>> Thank you very much for maintaining the OpenWrt package up to now! >>> >>> -- >>> Met vriendelijke groet / with kind regards, >>> Guus Sliepen <guus at tinc-vpn.org> >>> >>> _______________________________________________ >>> tinc mailing list >>> tinc at tinc-vpn.org >>> https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc >>> >> >> >> >> -- >> brgds >> Maxim Vorontsov >> >> _______________________________________________ >> tinc mailing list >> tinc at tinc-vpn.org >> https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc >>