Skip to content

Sanetize packages version

Thomas Petazzoni buildroot 1 version New

Get series with b4
b4 am 20190623183308.3bfbc24d@windsurf

Versions newest first

  1. v1 Latest0 of 4 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 4 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Buildroot] [PATCH 0/4] Sanetize packages version

Hello,

Quoted 7 lines · On Thu, 20 Jun 2019 22:32:29 +0200 Arnout Vandecappelle <[email protected]> wrote:
Quoted 4 lines

- android-tools: 4.2.2+git20130218
The downloaded version is fetch from launchpad, the RM version corresponds to the android version because sources for this tool are not distributed alone.

I wonder why we're using this launchpad version instead of the upstream
version. Maybe the original contributor (a certain Thomas P) remembers that?

The upstream android-tools from Google doesn't have any reasonable build system: it only has a bunch of Android.mk, which requires the entire Android stuff to be pulled in to be used. The Debian/Ubuntu version has an alternate build system with a few makefiles that get the job done.

Quoted 11 lines
Quoted 3 lines

- bandwidthd: 2.0.1-auto-r11
The downloaded version is not the original bandwithd but a fork that uses automake, this fork appends -auto-rXX to the actual version.

We should keep the suffix then.

Actually, there's another fork under NethServer that seems a little more
active. It's also used by OpenWrt.

But the sourceforge repo that hasn't seen activity in 15 years that
release-monitoring refers to is definitely not OK :-)

Perhaps we should register a separate bandwidthd-auto project in release-monitoring.org that tracks the bandwidthd fork we're using, and create a bandwidthd -> bandwidthd-auto mapping in RM.

Quoted 9 lines
Quoted 4 lines

- imx-alsa-plugins: rel_imx_4.9.x_1.0.0_ga
- imx-mkimage: rel_imx_4.14.78_1.0.0_ga
I The 4.9.x seems to be related to freescale but I'm not sure about the *_ga suffix.

The 4.9.x / 4.14.78 is the kernel version; the 1.0.0 is the freescale release
on top of that. Obviously these packages really have nothing to do with the kernel version, but they distribute everything as a single SDK and the kernel version is the anchor.

Most of these vendor-specific packages often have very weird version numbering, I'm not sure it will be easy for RM to track these. To me, such packages are not really the priority of things we want to check/monitor with RM.

Quoted 8 lines
Quoted 7 lines

- luarocks fetched packages: luasql-0.2.2.1-1
A large amount of lua packages have a -1 suffix. This suffix is not present on release-monitoring, so I think we should remove it. The thing is: the luarocks-package function seems to use the <pkg>_VERSION variable.
Remove suffix for those packages will probably require to modify a bit the way luarocks packages are handle.

Quoted 4 lines

Hm, good point... The -1 is the packaging version. Sometimes it needs to be
repackaged and you get a -2. And for some reason, sometimes it's -0.

I don't see a convenient way to work around this...

The only solution that I can see is changing the luarocks infra to use something else than <pkg>_VERSION, like <pkg>_LUAROCKS_VERSION, and have packages provide this variable.

Quoted 4 lines
Quoted 2 lines

If we achieve to modify these packages, the only packages left would be those with a commit id as version.

Commit ID is no problem.

Agreed.

Best regards,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com