Luci packages out of date?

Installing and Using OpenWrt
1

I'm a bit confused about the versions of the Luci packages in 24.10.0.

If I do an 'opkg update' and 'opkg list-upgradable' on a virgin 24.10.0 install, there are 13 luci packages that are already out of date. One of them, luci-mod-admin-full, is version 19.253.48496~3f93650 from 2019. If I go look at https://github.com/openwrt/luci/tree/master/modules/luci-mod-admin-full I see that the last commit there is indeed from 6 years ago. And yet 'opkg list-upgradable' says there's a new, much more recent version, 25.035.62793~4f7a183. I can install it with opkg with no apparent problems.

I tried compiling locally and the same outdated versions are included in the image. Is there something I'm missing?

2

https://openwrt.org/meta/infobox/upgrade_packages_warning

3

I don't think that answers why the luci packages start out listed as out of date immediately? I read the page twice and don't see it mentioned there.

1 Like
4

no it doesn't, but it tells you not to update them.

the packages for a certain release are static, while new ones are constantly get built.

1 Like
5

So you didn't actually answer the question then.

I think it is quite an interesting question:

  • Why are luci packages released quite often without any apparent changes?
  • Why not just only release the ones that have changes?
  • Why is 24.10 using such old versions to begin with?
  • If we aren't supposed to update to them, why publish them to the stable releases to begin with? Probably for owut I imagine?
1 Like
6

Actually, that warning isn't even on that page any more. I would kindly suggest you check your links before blindly posting them.

1 Like
7

You are mistaken. That warning was there mostly for routers with limited disk space, where installing many updates on the squashfs would fill up all available space. It literally warns against 'blindly upgrading packages.' These days it's fine to upgrade most packages, except for some core packages.

Besides that, like @Vorpal said, it wouldn't answer my question. Why is opkg showing newer versions than there are in a freshly compiled image? One of them is six years out of date.

8

it is, wrong link though, updated .... sorry.
for some reason google have issues finding this specific page when searched for.

9

If you compile from the 24.10.0 release tag, the feeds are locked to that release tag moment and you get old version of packages, including LuCI.

If you compile from the 24.10 branch head, you get the current version of packages in the branch.

2 Likes
10

Use Grok. Search engines are so yesterday.

11

Actually, regarding that, the explanation is likely a bit more complicated, and depends on the style of the feeds repo cloning. If buildbot clones a shallow copy with no history, the automatic versioning in LuCI will pick up a too new version.

If your own feed clone has a more full history, the versioning for that module is calculated from the correct old commit of that module.

4 Likes
12

Right, that makes sense. I'll play around a bit here with my local feed, to see if I can get a better understanding of how the versioning works exactly. Thanks!

13

Is this tongue in cheek?

14

There is only one way to find out.....

1 Like
15

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.