[Was: Re: Firmware Selector Setup]

[Baptiste Jonglez]

On 14-09-20, Paul Spooren wrote:
> > - is it possible to add 18.06?
> 
> From my understanding, no. JSON support was only added to 19.07. We
> could manually backport the patches oot and build once all targets just
> to receive the profile.json files. Then we would have to update all
> containing checksum inside the profiles, as many images are not yet
> reproducible. Maybe a bit to much work?

Ah, right, this JSON thing is not in 18.06.

Is this JSON support difficult to backport?  If not, it could be included
in the next 18.06 release, so that the buildbots would generate the needed
JSON files.

> > Regarding 18.06, here is a use-case: I would like to search for a model,
> > and then it would give me the latest stable version for it (18.06 or
> > 19.07). A bit like https://openwrt.org/toh/start
> >
> > Currently, when I search "WR841", it only gives me TL-WR841N v13 because
> > the earlier models are no longer built for 19.07. It would be nice to
> > show the other models; that is, propose 18.06 as a fallback when 19.07
> > is
> > not supported.
> >
> > If this is not straightforward to implement, this could be added to a
> > later version of YAFS: the current version is already good!
> >
> > Thanks,
> > Baptiste
> >
> > On 14-09-20, Moritz Warning wrote:
> > > Hi Petr and everybody else,
> > > 
> > > thank you very much in making this possible!
> > > I think this will be a significant step forwards in end user usability.
> > > 
> > > On 9/14/20 12:36 PM, Petr Štetiar wrote:
> > > > Moritz Warning <moritzwarning at web.de> [2020-08-01 02:13:05]:
> > > >
> > > > Hi,
> > > >
> > > >> we have reached the point that we can finally set up the firmware selector [0]. Yay!
> > > >> But somebody need to finally put it on the website...
> > > >
> > > > so https://firmware-selector.staging.openwrt.org is alive, deployed
> > > > automatically from CI pipeline[1]. Any push into master branch deploys site at
> > > > firmware-selector.staging.o.o (once all CI tests pass). Then after additional
> > > > QA steps done usually by humans it's possible to manually trigger another CI
> > > > pipeline which is going to deploy the site at production URL
> > > > firmware-selector.openwrt.org.
> > > >
> > > > Next steps:
> > > >
> > > >  - fix the `web` group/repo name clash on GitLab.com/openwrt and setup mirroring and
> > > >    CI/CD deployment from GitLab.com/openwrt/web/firmware-selector-openwrt-org.git
> > > >  - fix remaining issues (if any) on staging and make the site officialy alive
> > > >    on firmware-selector.openwrt.org
> > > >
> > > > I plan to tackle these in the upcoming days.
> > > >
> > > > 1. https://gitlab.com/ynezz/openwrt-firmware-selector/-/pipelines/189588455
> > > Let me know if I can help.
> > > 
> > > >
> > > > Cheers,
> > > >
> > > > Petr
> > > >
> > > 
> > > 
> > > _______________________________________________
> > > openwrt-adm mailing list
> > > openwrt-adm at lists.openwrt.org
> > > https://lists.openwrt.org/mailman/listinfo/openwrt-adm
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.openwrt.org/pipermail/openwrt-adm/attachments/20200914/4af5b2c9/attachment.sig>