hnyman
September 25, 2023, 9:06am
15
I wonder if it is just a temporary buildbot upload error or similar, (trying to do just when buildbot is uploading a new build ?)
There have also been similar LuCI bug reports in the last few days, (but the issue is not related to LuCI)
So, this might be a bit wider?
This might be fallout from
committed 05:33PM - 24 Sep 23 UTC
Currently, the same information is stored at the Packages.manifest in
the 'Packa… ge:' variable and also additionally in the 'SourceName:' variable.
So we have for Packages.manifest for strongswan-charon-cmd:
```
Package: strongswan-charon-cmd
Version: 5.9.11-1
SourceName: strongswan-charon-cmd
License: GPL-2.0-or-later
Section: net
```
This is not correct. Several installable packages are built from the same
strongswan source. Therefore it makes more sense that the source name is
really the source name. In this case the it is 'strongswan'.
After this change the Packages.manifest for strongswan-charon-cmd:
```
Package: strongswan-charon-cmd
Version: 5.9.11-1
SourceName: strongswan
License: GPL-2.0-or-later
Section: net
```
In summary. The 'Package' name is the name of the package to be installed
on the target system. The 'SourceName' is the compile unit from which the
package was build from. This must be the same for all installable
packages built from the same compile unit. This commit fixes that.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
as the failing packages gpio-button-hotplug, kernel, mac80211 are built from kernel sources, and do not have a proper package files. (well, mac80211 has Makefile, but is done from kernel backports)
cc @feckert @hauke @aparcar
1 Like