Re: [LEDE-DEV] Branching LEDE 17.01 / problems with ath9k
* Thomas Endt[13.01.2017 09:19]: > > the page https://lede-project.org changed again and 'reporting bugs' > > is hidden under 'Developer Guide' which is just...wrong Please make > > this more "friendly". > > https://lede-project.org/contact contains a link to > https://bugs.lede-project.org/ since 11/11/2016. > IMHO the perfect place. thank you - that makes sense. maybe move it more ontop? it's nearly the last entry after, even after "Server Status Changes Announcements on Twitter" 8-) bye, bastian ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Branching LEDE 17.01 / problems with ath9k
> -Ursprüngliche Nachricht- > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von Bastian Bittorf > Gesendet: Donnerstag, 12. Januar 2017 10:39 > An: Jo-Philipp Wich > Cc: l...@kitschensync.net; LEDE Development List > Betreff: Re: [LEDE-DEV] Branching LEDE 17.01 / problems with ath9k > > Thanks for these strong steps toward a release, the last weeks where > full of commits and everybody seems to work very hard. > > What i want to mention is, that older ath9k chips (ar91xx?) are not > useable with LEDE anymore, e.g. TP-Link 1043nd v1 > > This needs more testing and reporting. Maybe someone has time to jump > in. I have opened a ticket for that: > https://bugs.lede-project.org/index.php?do=details_id=373 > > bye, bastian > > BTW: > the page https://lede-project.org changed again and 'reporting bugs' > is hidden under 'Developer Guide' which is just...wrong Please make > this more "friendly". https://lede-project.org/contact contains a link to https://bugs.lede-project.org/ since 11/11/2016. IMHO the perfect place. regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Branching LEDE 17.01 / problems with ath9k
Thanks for these strong steps toward a release, the last weeks where full of commits and everybody seems to work very hard. What i want to mention is, that older ath9k chips (ar91xx?) are not useable with LEDE anymore, e.g. TP-Link 1043nd v1 This needs more testing and reporting. Maybe someone has time to jump in. I have opened a ticket for that: https://bugs.lede-project.org/index.php?do=details_id=373 bye, bastian BTW: the page https://lede-project.org changed again and 'reporting bugs' is hidden under 'Developer Guide' which is just...wrong Please make this more "friendly". ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Branching LEDE 17.01
Hi Ted, so no one else objected and you want to hold of until after the weekend; therefor I propose to branch on Monday, the 16th. ~ Jo signature.asc Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Branching LEDE 17.01
On Tue, 2017-01-10 at 16:19 +0100, Jo-Philipp Wich wrote: > Hi guys, > > I'd like to branch off lede-17.01 on Friday, the 13th and would > appreciate if you could merge your outstanding, release critical work > until then. > > If you think we should delay branching, then raise your objections now. > > If no objections are brought up within the next 24 hours, I'll go > forward asking the feed maintainers to create "lede-17.01" branches. > > > Regards, > Jo > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev Hi Jo - Could you possibly hold off on this until after the weekend. I'm still working on a few PolarSSL issues (and some other more minor) in the Packages repo. I should have them done by then. After that, I'll just cherry-pick other fixes until we freeze a release. /ted ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Branching LEDE 17.01
Hi! I'd really like to see a rather trivial issue addressed: dnsmasq fails to get notifications on /tmp/resolv.conf.auto changes when running inside ujail. This is because the bind mount obviously won't survive this file being *replaced*, eg. if the DHCP client supplies the DNS server to be used only after dnsmasq has already been started. The easiest solution would be to introduce a directory /tmp/resolv.conf.d/, move all /tmp/resolv.conf* in there and bind mount that into the jail instead. The current /tmp/resolv.conf.auto seems to hardcoded in netifd and appears in dnsmasq's and mwan's default config. Anywhere else? Given the overall code quality of dnsmasq, it would really be nice to at least have it run in a jail by default for the next release... Mentioning the problem to John, he said that the current bind mounting approach will be replaced by a future jailfs he is working on. However, I'm afraid this won't be ready by Friday ;) If there are no objections, I'll suggest a PR introducing /tmp/resolv.conf.d/ and moving the location of /tmp/resolv.conf* into that directory. Cheers Daniel On Tue, Jan 10, 2017 at 04:19:05PM +0100, Jo-Philipp Wich wrote: > Hi guys, > > I'd like to branch off lede-17.01 on Friday, the 13th and would > appreciate if you could merge your outstanding, release critical work > until then. > > If you think we should delay branching, then raise your objections now. > > If no objections are brought up within the next 24 hours, I'll go > forward asking the feed maintainers to create "lede-17.01" branches. > > > Regards, > Jo > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] Branching LEDE 17.01
Hi guys, I'd like to branch off lede-17.01 on Friday, the 13th and would appreciate if you could merge your outstanding, release critical work until then. If you think we should delay branching, then raise your objections now. If no objections are brought up within the next 24 hours, I'll go forward asking the feed maintainers to create "lede-17.01" branches. Regards, Jo ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev