upstream collectd package overrides the compiled one #55
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Sysdeploy/openwrt#55
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For reason which is not fully clear to me, during package installation inside the image, the collectd package that's online on downloads.openwrt.org takes precedence over the locally built one. This means it can't use encrypted network communication. I'm trying to debug the cause, but I only have a couple of days to test it.
Could you try this: https://artifacts.bitmessage.at/openwrt/16440/? It's possible that collectd depends on some package from feed "base". In #54 I added copying packages built from the "base".
Well it used to work before (around February), I haven't tested it since. If you look at the buildlog of 16440, it still says, at line 5527:
Downloading https://downloads.openwrt.org/releases/22.03.2/packages/aarch64_cortex-a72/packages/collectd_5.12.0-34_aarch64_cortex-a72.ipk
So I don't think it works. If you look at an earlier build that had it correctly, for example
90e53ad77b
which has a build log at https://buildbot.bitmessage.org/#/builders/33/builds/15785/steps/3/logs/stdio, you can see at line 5030:Downloading file:packages/collectd_5.12.0-33_aarch64_cortex-a72.ipk
Oh wait it's a newer version. Maybe that's the problem. Maybe the feed references an older version.
This is strange, all the feeds have fixed git revision in
feeds.conf.default
so the release shouldn't be increased. I also found this, not sure if it's relevant.Maybe they have a new SDK tarball. You can download it by invalidating docker cache.
I cleared all the docker caches about a week ago.
I think these packages are downloaded based on config in
repositories.conf
, notfeeds.conf.default
.No, 22.03.2 is still dated by Oct 16, 2022. So maybe 22.03.4?
feeds.conf defines the versions, you build with SDK.
I think packages are released separately from the image. And the latest image release, 22.03.5 is older than the collectd-5.12.0-34 package. So even if we bump to 22.03.5, it will still build the old package.
Hmm, it seems unfair to update this.
Hmm, I thought the last digit is a quarter. So we need to drop the revision in the feeds.conf.
The trunk release is 46 ):
Fixed in #56