The package update is not a perfect solution but it is better to have
it as is than to remove it.
Updated packages are also used by imagebuilder and attended
sysupgrade. I normally generate a new image to apply updates because
some devices cannot afford the extra installation. If we need updated
p
Am Sun, Dec 12, 2021 at 08:42:52PM +0100 schrieb Jo-Philipp Wich:
>
> In my opinion, there is a fundamental decision to be made on whether we would
> like to pursue the goal of (also) being a binary distribution for
> routers/embedded appliances or if we simply concentrate on the build-from-
> sour
On 12/12/21 20:42, Jo-Philipp Wich wrote:
- The wiki actively discourages users from upgrading packages [1]
- The overall sentiment in the forum is to instruct users to not/never
upgrade packages [2] but to always upgrade to the next release, build from
source [3] or use snapshots
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
On 2021-12-12 20:42, Jo-Philipp W
On Sun, Dec 12, 2021 at 08:42:52PM +0100, Jo-Philipp Wich wrote:
> - Stop providing binary package updates; build release images and associated
>repositories once only, archive the artifacts and redelegate build
>resources back to master snapshots
This!
If people are interested in providi
Hi,
since the release of LEDE 17.01.0, OpenWrt started offering updated binary
packages for released versions, means the HEAD of a released stable branch is
continuously getting rebuilt and the resulting binaries are uploaded to the
release repositories. Users will see those updated packages as "u
