Bug #24
closedCan't build bms2orp-binding since Gitlab file architecture changed
0%
Description
Initially, all the bindings / services directories were located at the root of the Datahub repository.
The %prep section of the bms2orp-binding spec file was:
%prep
%autosetup -p 1
mv %{_builddirsrc}/%{name}-%{version}/%{name} %{_builddirsrc}/%{name}
rm -rf %{_builddirsrc}/%{name}-%{version}
mv %{_builddirsrc}/%{name} %{_builddirsrc}/%{name}-%{version}
A couple of weeks ago, a new file architecture was implemented. In this new file architecture, the bms2orp-binding directory is now located in a directory named Common.
The spec file was modified to take this new architecture into account and became:
%prep
%autosetup -p 1
mv %{_builddirsrc}/%{name}-%{version}/Common/%{name} %{_builddirsrc}/%{name}
rm -rf %{_builddirsrc}/%{name}-%{version}
mv %{_builddirsrc}/%{name} %{_builddirsrc}/%{name}-%{version}
In the factory, this new spec file has been imported correctly. The problem is that, when building, the factory can't find the bms2orp-binding directory.
A ls
command was inserted in the %prep section of the new spec file and the result below shows the old architecture instead of the new one (extract from build.log file):
+ cd bms2orp-binding-2.0.0
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ ls
BOSCH_CISS_BLE_module
Makefile
ORP_server
README.md
automate-wifi-binding
bms2orp-binding
bms2redis-binding
canbus-plugins-bms
configs-datahub
platform-info-binding
poc-service
redisTS2influxDB
saft-delivery
specifications
tests
It looks as if the factory didn't refresh the files since the architecture change. Thus, all build attempts fail.
Factory version:¶
Server ID1bc74b96-1c72-11ec-ac7c-00163e6eea73
Server Version0.15.0
Server API Version1
Source Tag2022-03-21_134355
Updated by Vincent Rubiolo over 2 years ago
- Assignee changed from Vincent Rubiolo to Marc-Antoine Riou
Updated by Sebastien Douheret [IoT.bzh] about 2 years ago
- Affects Version/s armel-RC 0.15.0 added
- Affects Version/s deleted (
armel-1.0)
Updated by Sebastien Douheret [IoT.bzh] about 2 years ago
- Target version set to armel-1.0
Updated by Sebastien Douheret [IoT.bzh] about 2 years ago
- Fix Version/s armel-1.0 added
Updated by Marc-Antoine Riou about 2 years ago
The file manager had a bug in v0.15.0 regarding its cache which
was not refreshed between two versions of application archive.
This bug is now fixed in armel-1.0
Updated by José Bollo about 2 years ago
- Status changed from New to In Progress
- Assignee changed from Marc-Antoine Riou to Emmanuel Jubera [SAFT]
seem resolved since Armel 1.0.
Updated by Emmanuel Jubera [SAFT] about 2 years ago
- Status changed from In Progress to Resolved
Fix tested with Armel 1.0.5.
Updated by Emmanuel Jubera [SAFT] almost 2 years ago
- Status changed from Resolved to Closed