upstream collectd package overrides the compiled one #55

Closed
opened 2023-08-06 17:47:51 +02:00 by PeterSurda · 13 comments
Owner

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.

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.
lee.miller was assigned by PeterSurda 2023-08-06 17:47:51 +02:00
Collaborator

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".

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".
Author
Owner

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

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 https://git.bitmessage.org/Sysdeploy/openwrt/commit/90e53ad77bb0ff4fd05e306ff509483493914a27 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`
Author
Owner

Oh wait it's a newer version. Maybe that's the problem. Maybe the feed references an older version.

Oh wait it's a newer version. Maybe that's the problem. Maybe the feed references an older version.
Collaborator

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.

> 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](https://lists.openwrt.org/pipermail/openwrt-devel/2022-November/039750.html), not sure if it's relevant. Maybe they have a new SDK tarball. You can download it by invalidating docker cache.
Author
Owner

I cleared all the docker caches about a week ago.

I cleared all the docker caches about a week ago.
Author
Owner

I think these packages are downloaded based on config in repositories.conf, not feeds.conf.default.

I think these packages are downloaded based on config in `repositories.conf`, not `feeds.conf.default`.
Collaborator

Maybe they have a new SDK tarball. You can download it by invalidating docker cache.

No, 22.03.2 is still dated by Oct 16, 2022. So maybe 22.03.4?

> Maybe they have a new SDK tarball. You can download it by invalidating docker cache. No, 22.03.2 is still dated by Oct 16, 2022. So maybe [22.03.4](https://buildbot.bitmessage.org/#/builders/33/builds/16521)?
Collaborator

I think these packages are downloaded based on config in repositories.conf, not feeds.conf.default.

feeds.conf defines the versions, you build with SDK.

> I think these packages are downloaded based on config in `repositories.conf`, not `feeds.conf.default`. feeds.conf defines the versions, you build with SDK.
Author
Owner

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.

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.
Collaborator

Hmm, it seems unfair to update this.

Hmm, it seems unfair to update [this](https://downloads.openwrt.org/releases/22.03.2/packages/aarch64_cortex-a72/packages).
Collaborator

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, I thought the last digit is a quarter. So we need to drop the revision in the feeds.conf.

> 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, I thought the last digit is a quarter. So we need to drop the revision in the feeds.conf.
Collaborator

The trunk release is 46 ):

The trunk release is [46](https://git.openwrt.org/?p=feed/packages.git;a=blob;f=utils/collectd/Makefile;h=6890694a502aef227aeed720bbf8ea65a5165086;hb=HEAD) ):
Author
Owner

Fixed in #56

Fixed in #56
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Sysdeploy/openwrt#55
No description provided.