Re: State of APK package manger integration - switched!
Works good for me, reinstalled my router with yesterdays nightly and only got apk Den mån 11 nov. 2024 kl 12:56 skrev Paul Spooren : > > Hi Robert, > > No it should not be there, based on the code it shouldn’t be there but maybe > it’s pulled in by some other package depending on it. I’ll have a look, > thanks for notifying me. > > Best, > Paul > > > On 11. Nov 2024, at 10:55, Robert Marko wrote: > > > > On Mon, 11 Nov 2024 at 10:15, Paul Spooren wrote: > >> > >> Hi again, > >> > >> We switched last night and I see the first targets being build with APK as > >> package manager[1]. Since phase2 (aka package feeds builds) picks up on > >> SDKs from phase1 (firmware/SDK/etc), it will take a few more hours until > >> package feeds are fully available. > >> > >> Unfortunately something wiped the backups of `targets.opkg` and > >> `packages.opkg`. I’ll try to investigate what caused this, I assume a > >> cleanup script deployed long ago... Please be patient. > >> > >> There will be more things coming up and being bumpy, this is nightly > >> snapshots after all. Please report bugs but don’t upgrade this to your > >> production systems. > > > > Hi Paul, was keeping the OPKG included as well intended? > > Because now both APK and OPKG are included by default. > > > > Regards, > > Robert > >> > >> Best, > >> Paul > >> > >> [1]: https://buildbot.openwrt.org/images/#/changes/52 > >> > >>> On 9. Nov 2024, at 16:50, Paul Spooren wrote: > >>> > >>> Hi all, > >>> > >>> I merged the remaining ImageBuilder fixes and have my fingers crossed > >>> those are the last. > >>> > >>> We plan to do the switch on Monday! > >>> > >>> My self hosted infrastructure is obsolete and we moved instead to the > >>> official staging environment[1]. > >>> > >>> I’ll create a copy of both targets and packages folders on the download > >>> servers ending with `.opkg`. So you can still download OPKG based > >>> snapshots from that day and by modifying the feeds on device, download > >>> whatever packages. > >>> > >>> Please enjoy the weekend! > >>> > >>> Best, > >>> Paul > >>> > >>> [1]: https://buildbot.staging.openwrt.org/images/#/ > >>> > >>> > On 30. Oct 2024, at 14:07, Paul Spooren wrote: > > Hi all, > > Thanks to some extra shifts from fellow developers and temporary > building capacity sponsored by some awesome communities, we made good > progress! > > Starting with f72879d[1] and following commits we fixed up most the > remaining (known) issues and got a ton of images to test[2], if you have > some spare time, please give it a spin. > > There is a standing pull request on GitHub[3] which contains all > “staging” fixes which are then picked up by our testing build > infrastructure [4][5]. Please feel free to report issues there! > > > FYI seems like ImageBuilder still needs some love, I've tested both: > > Should be fixed via the latest commit[6]. Please be patient with the > phase1 builds. > > There were multiple concerns about the size increase[7]! Yes, right now > APK is not as tiny as OPKG. We’re on it! APK is “applet” based so we can > make certain features optional later on, i.e. the index creation. > Secondly we’re using the highly optimized v3 index structure of APK > while Alpine Linux sticks with v2 (for now). Upstream APK supports both > versions and we’ll eventually cleanup the v2 code or make it optional. > > We plan to branch 24.10 soonish [sic] and then make APK the default in > the main branch. If APK flies as expected, we may enable it for 24.10, > too. > > Best, > Paul > > [1]: > https://github.com/openwrt/openwrt/commit/f72879dd60b908fcca2ab016e30fe22c347a279d > [2]: https://buildbot.aparcar.org/targets/ > [3]: https://github.com/openwrt/openwrt/pull/16767 > [4]: https://buildbot.aparcar.org/phase1/#/ > [5]: https://buildbot.aparcar.org/phase2/#/ > [6]: > https://github.com/openwrt/openwrt/pull/16767/commits/85c376c67625370ef754825b86d868535b26995a > [7]: > https://github.com/openwrt/openwrt/pull/16767#issuecomment-2434823810 > > >>> > >> > >> ___ > >> openwrt-devel mailing list > >> openwrt-devel@lists.openwrt.org > >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: State of APK package manger integration - switched!
On 11.11.24 12:57, Robert Marko wrote: On Mon, 11 Nov 2024 at 12:56, Paul Spooren wrote: Hi Robert, No it should not be there, based on the code it shouldn’t be there but maybe it’s pulled in by some other package depending on it. I’ll have a look, thanks for notifying me. Hi Paul, I have started poking around and somehow this is getting evaluated weirdly: ifneq ($(CONFIG_USE_APK),) DEFAULT_PACKAGES+=apk-mbedtls else DEFAULT_PACKAGES+=opkg endif Because removing the else condition drops OPKG from default package selection. This is definitely broken. Anything that is used for generating (menu)config related files cannot rely on any symbols in .config Looks like there are other similarly broken checks in the same file below this part. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: State of APK package manger integration - switched!
On Mon, 11 Nov 2024 at 12:56, Paul Spooren wrote: > > Hi Robert, > > No it should not be there, based on the code it shouldn’t be there but maybe > it’s pulled in by some other package depending on it. I’ll have a look, > thanks for notifying me. Hi Paul, I have started poking around and somehow this is getting evaluated weirdly: ifneq ($(CONFIG_USE_APK),) DEFAULT_PACKAGES+=apk-mbedtls else DEFAULT_PACKAGES+=opkg endif Because removing the else condition drops OPKG from default package selection. Regards, Robert > > Best, > Paul > > > On 11. Nov 2024, at 10:55, Robert Marko wrote: > > > > On Mon, 11 Nov 2024 at 10:15, Paul Spooren wrote: > >> > >> Hi again, > >> > >> We switched last night and I see the first targets being build with APK as > >> package manager[1]. Since phase2 (aka package feeds builds) picks up on > >> SDKs from phase1 (firmware/SDK/etc), it will take a few more hours until > >> package feeds are fully available. > >> > >> Unfortunately something wiped the backups of `targets.opkg` and > >> `packages.opkg`. I’ll try to investigate what caused this, I assume a > >> cleanup script deployed long ago... Please be patient. > >> > >> There will be more things coming up and being bumpy, this is nightly > >> snapshots after all. Please report bugs but don’t upgrade this to your > >> production systems. > > > > Hi Paul, was keeping the OPKG included as well intended? > > Because now both APK and OPKG are included by default. > > > > Regards, > > Robert > >> > >> Best, > >> Paul > >> > >> [1]: https://buildbot.openwrt.org/images/#/changes/52 > >> > >>> On 9. Nov 2024, at 16:50, Paul Spooren wrote: > >>> > >>> Hi all, > >>> > >>> I merged the remaining ImageBuilder fixes and have my fingers crossed > >>> those are the last. > >>> > >>> We plan to do the switch on Monday! > >>> > >>> My self hosted infrastructure is obsolete and we moved instead to the > >>> official staging environment[1]. > >>> > >>> I’ll create a copy of both targets and packages folders on the download > >>> servers ending with `.opkg`. So you can still download OPKG based > >>> snapshots from that day and by modifying the feeds on device, download > >>> whatever packages. > >>> > >>> Please enjoy the weekend! > >>> > >>> Best, > >>> Paul > >>> > >>> [1]: https://buildbot.staging.openwrt.org/images/#/ > >>> > >>> > On 30. Oct 2024, at 14:07, Paul Spooren wrote: > > Hi all, > > Thanks to some extra shifts from fellow developers and temporary > building capacity sponsored by some awesome communities, we made good > progress! > > Starting with f72879d[1] and following commits we fixed up most the > remaining (known) issues and got a ton of images to test[2], if you have > some spare time, please give it a spin. > > There is a standing pull request on GitHub[3] which contains all > “staging” fixes which are then picked up by our testing build > infrastructure [4][5]. Please feel free to report issues there! > > > FYI seems like ImageBuilder still needs some love, I've tested both: > > Should be fixed via the latest commit[6]. Please be patient with the > phase1 builds. > > There were multiple concerns about the size increase[7]! Yes, right now > APK is not as tiny as OPKG. We’re on it! APK is “applet” based so we can > make certain features optional later on, i.e. the index creation. > Secondly we’re using the highly optimized v3 index structure of APK > while Alpine Linux sticks with v2 (for now). Upstream APK supports both > versions and we’ll eventually cleanup the v2 code or make it optional. > > We plan to branch 24.10 soonish [sic] and then make APK the default in > the main branch. If APK flies as expected, we may enable it for 24.10, > too. > > Best, > Paul > > [1]: > https://github.com/openwrt/openwrt/commit/f72879dd60b908fcca2ab016e30fe22c347a279d > [2]: https://buildbot.aparcar.org/targets/ > [3]: https://github.com/openwrt/openwrt/pull/16767 > [4]: https://buildbot.aparcar.org/phase1/#/ > [5]: https://buildbot.aparcar.org/phase2/#/ > [6]: > https://github.com/openwrt/openwrt/pull/16767/commits/85c376c67625370ef754825b86d868535b26995a > [7]: > https://github.com/openwrt/openwrt/pull/16767#issuecomment-2434823810 > > >>> > >> > >> ___ > >> openwrt-devel mailing list > >> openwrt-devel@lists.openwrt.org > >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: State of APK package manger integration - switched!
Hi Robert, No it should not be there, based on the code it shouldn’t be there but maybe it’s pulled in by some other package depending on it. I’ll have a look, thanks for notifying me. Best, Paul > On 11. Nov 2024, at 10:55, Robert Marko wrote: > > On Mon, 11 Nov 2024 at 10:15, Paul Spooren wrote: >> >> Hi again, >> >> We switched last night and I see the first targets being build with APK as >> package manager[1]. Since phase2 (aka package feeds builds) picks up on SDKs >> from phase1 (firmware/SDK/etc), it will take a few more hours until package >> feeds are fully available. >> >> Unfortunately something wiped the backups of `targets.opkg` and >> `packages.opkg`. I’ll try to investigate what caused this, I assume a >> cleanup script deployed long ago... Please be patient. >> >> There will be more things coming up and being bumpy, this is nightly >> snapshots after all. Please report bugs but don’t upgrade this to your >> production systems. > > Hi Paul, was keeping the OPKG included as well intended? > Because now both APK and OPKG are included by default. > > Regards, > Robert >> >> Best, >> Paul >> >> [1]: https://buildbot.openwrt.org/images/#/changes/52 >> >>> On 9. Nov 2024, at 16:50, Paul Spooren wrote: >>> >>> Hi all, >>> >>> I merged the remaining ImageBuilder fixes and have my fingers crossed those >>> are the last. >>> >>> We plan to do the switch on Monday! >>> >>> My self hosted infrastructure is obsolete and we moved instead to the >>> official staging environment[1]. >>> >>> I’ll create a copy of both targets and packages folders on the download >>> servers ending with `.opkg`. So you can still download OPKG based snapshots >>> from that day and by modifying the feeds on device, download whatever >>> packages. >>> >>> Please enjoy the weekend! >>> >>> Best, >>> Paul >>> >>> [1]: https://buildbot.staging.openwrt.org/images/#/ >>> >>> On 30. Oct 2024, at 14:07, Paul Spooren wrote: Hi all, Thanks to some extra shifts from fellow developers and temporary building capacity sponsored by some awesome communities, we made good progress! Starting with f72879d[1] and following commits we fixed up most the remaining (known) issues and got a ton of images to test[2], if you have some spare time, please give it a spin. There is a standing pull request on GitHub[3] which contains all “staging” fixes which are then picked up by our testing build infrastructure [4][5]. Please feel free to report issues there! > FYI seems like ImageBuilder still needs some love, I've tested both: Should be fixed via the latest commit[6]. Please be patient with the phase1 builds. There were multiple concerns about the size increase[7]! Yes, right now APK is not as tiny as OPKG. We’re on it! APK is “applet” based so we can make certain features optional later on, i.e. the index creation. Secondly we’re using the highly optimized v3 index structure of APK while Alpine Linux sticks with v2 (for now). Upstream APK supports both versions and we’ll eventually cleanup the v2 code or make it optional. We plan to branch 24.10 soonish [sic] and then make APK the default in the main branch. If APK flies as expected, we may enable it for 24.10, too. Best, Paul [1]: https://github.com/openwrt/openwrt/commit/f72879dd60b908fcca2ab016e30fe22c347a279d [2]: https://buildbot.aparcar.org/targets/ [3]: https://github.com/openwrt/openwrt/pull/16767 [4]: https://buildbot.aparcar.org/phase1/#/ [5]: https://buildbot.aparcar.org/phase2/#/ [6]: https://github.com/openwrt/openwrt/pull/16767/commits/85c376c67625370ef754825b86d868535b26995a [7]: https://github.com/openwrt/openwrt/pull/16767#issuecomment-2434823810 >>> >> >> ___ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel signature.asc Description: Message signed with OpenPGP ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: State of APK package manger integration - switched!
On Mon, 11 Nov 2024 at 10:15, Paul Spooren wrote: > > Hi again, > > We switched last night and I see the first targets being build with APK as > package manager[1]. Since phase2 (aka package feeds builds) picks up on SDKs > from phase1 (firmware/SDK/etc), it will take a few more hours until package > feeds are fully available. > > Unfortunately something wiped the backups of `targets.opkg` and > `packages.opkg`. I’ll try to investigate what caused this, I assume a cleanup > script deployed long ago... Please be patient. > > There will be more things coming up and being bumpy, this is nightly > snapshots after all. Please report bugs but don’t upgrade this to your > production systems. Hi Paul, was keeping the OPKG included as well intended? Because now both APK and OPKG are included by default. Regards, Robert > > Best, > Paul > > [1]: https://buildbot.openwrt.org/images/#/changes/52 > > > On 9. Nov 2024, at 16:50, Paul Spooren wrote: > > > > Hi all, > > > > I merged the remaining ImageBuilder fixes and have my fingers crossed those > > are the last. > > > > We plan to do the switch on Monday! > > > > My self hosted infrastructure is obsolete and we moved instead to the > > official staging environment[1]. > > > > I’ll create a copy of both targets and packages folders on the download > > servers ending with `.opkg`. So you can still download OPKG based snapshots > > from that day and by modifying the feeds on device, download whatever > > packages. > > > > Please enjoy the weekend! > > > > Best, > > Paul > > > > [1]: https://buildbot.staging.openwrt.org/images/#/ > > > > > >> On 30. Oct 2024, at 14:07, Paul Spooren wrote: > >> > >> Hi all, > >> > >> Thanks to some extra shifts from fellow developers and temporary building > >> capacity sponsored by some awesome communities, we made good progress! > >> > >> Starting with f72879d[1] and following commits we fixed up most the > >> remaining (known) issues and got a ton of images to test[2], if you have > >> some spare time, please give it a spin. > >> > >> There is a standing pull request on GitHub[3] which contains all “staging” > >> fixes which are then picked up by our testing build infrastructure [4][5]. > >> Please feel free to report issues there! > >> > >>> FYI seems like ImageBuilder still needs some love, I've tested both: > >> > >> Should be fixed via the latest commit[6]. Please be patient with the > >> phase1 builds. > >> > >> There were multiple concerns about the size increase[7]! Yes, right now > >> APK is not as tiny as OPKG. We’re on it! APK is “applet” based so we can > >> make certain features optional later on, i.e. the index creation. Secondly > >> we’re using the highly optimized v3 index structure of APK while Alpine > >> Linux sticks with v2 (for now). Upstream APK supports both versions and > >> we’ll eventually cleanup the v2 code or make it optional. > >> > >> We plan to branch 24.10 soonish [sic] and then make APK the default in the > >> main branch. If APK flies as expected, we may enable it for 24.10, too. > >> > >> Best, > >> Paul > >> > >> [1]: > >> https://github.com/openwrt/openwrt/commit/f72879dd60b908fcca2ab016e30fe22c347a279d > >> [2]: https://buildbot.aparcar.org/targets/ > >> [3]: https://github.com/openwrt/openwrt/pull/16767 > >> [4]: https://buildbot.aparcar.org/phase1/#/ > >> [5]: https://buildbot.aparcar.org/phase2/#/ > >> [6]: > >> https://github.com/openwrt/openwrt/pull/16767/commits/85c376c67625370ef754825b86d868535b26995a > >> [7]: https://github.com/openwrt/openwrt/pull/16767#issuecomment-2434823810 > >> > > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: State of APK package manger integration - switched!
Hi again, We switched last night and I see the first targets being build with APK as package manager[1]. Since phase2 (aka package feeds builds) picks up on SDKs from phase1 (firmware/SDK/etc), it will take a few more hours until package feeds are fully available. Unfortunately something wiped the backups of `targets.opkg` and `packages.opkg`. I’ll try to investigate what caused this, I assume a cleanup script deployed long ago... Please be patient. There will be more things coming up and being bumpy, this is nightly snapshots after all. Please report bugs but don’t upgrade this to your production systems. Best, Paul [1]: https://buildbot.openwrt.org/images/#/changes/52 > On 9. Nov 2024, at 16:50, Paul Spooren wrote: > > Hi all, > > I merged the remaining ImageBuilder fixes and have my fingers crossed those > are the last. > > We plan to do the switch on Monday! > > My self hosted infrastructure is obsolete and we moved instead to the > official staging environment[1]. > > I’ll create a copy of both targets and packages folders on the download > servers ending with `.opkg`. So you can still download OPKG based snapshots > from that day and by modifying the feeds on device, download whatever > packages. > > Please enjoy the weekend! > > Best, > Paul > > [1]: https://buildbot.staging.openwrt.org/images/#/ > > >> On 30. Oct 2024, at 14:07, Paul Spooren wrote: >> >> Hi all, >> >> Thanks to some extra shifts from fellow developers and temporary building >> capacity sponsored by some awesome communities, we made good progress! >> >> Starting with f72879d[1] and following commits we fixed up most the >> remaining (known) issues and got a ton of images to test[2], if you have >> some spare time, please give it a spin. >> >> There is a standing pull request on GitHub[3] which contains all “staging” >> fixes which are then picked up by our testing build infrastructure [4][5]. >> Please feel free to report issues there! >> >>> FYI seems like ImageBuilder still needs some love, I've tested both: >> >> Should be fixed via the latest commit[6]. Please be patient with the phase1 >> builds. >> >> There were multiple concerns about the size increase[7]! Yes, right now APK >> is not as tiny as OPKG. We’re on it! APK is “applet” based so we can make >> certain features optional later on, i.e. the index creation. Secondly we’re >> using the highly optimized v3 index structure of APK while Alpine Linux >> sticks with v2 (for now). Upstream APK supports both versions and we’ll >> eventually cleanup the v2 code or make it optional. >> >> We plan to branch 24.10 soonish [sic] and then make APK the default in the >> main branch. If APK flies as expected, we may enable it for 24.10, too. >> >> Best, >> Paul >> >> [1]: >> https://github.com/openwrt/openwrt/commit/f72879dd60b908fcca2ab016e30fe22c347a279d >> [2]: https://buildbot.aparcar.org/targets/ >> [3]: https://github.com/openwrt/openwrt/pull/16767 >> [4]: https://buildbot.aparcar.org/phase1/#/ >> [5]: https://buildbot.aparcar.org/phase2/#/ >> [6]: >> https://github.com/openwrt/openwrt/pull/16767/commits/85c376c67625370ef754825b86d868535b26995a >> [7]: https://github.com/openwrt/openwrt/pull/16767#issuecomment-2434823810 >> > signature.asc Description: Message signed with OpenPGP ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
