action sometimes throw error.
waqar-islam opened this issue · 2 comments
The action sometimes run successfully but then throws this error
Reading package lists... Reading package lists... Building dependency tree... Reading state information... You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: msodbcsql17 : Depends: odbcinst but it is not going to be installed unixodbc : Depends: odbcinst1debian2 (>= 2.3.11-1) but it is not going to be installed Depends: libodbc1 (>= 2.3.11-1) but it is not going to be installed unixodbc-dev : Depends: odbcinst1debian2 (= 2.3.11-1) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). Reading package lists... Building dependency tree... Reading state information... You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: mssql-tools : Depends: msodbcsql17 (>= 17.3.0.0) but it is not going to be installed unixodbc : Depends: odbcinst1debian2 (>= 2.3.11-1) but it is not going to be installed Depends: libodbc1 (>= 2.3.11-1) but it is not going to be installed unixodbc-dev : Depends: odbcinst1debian2 (= 2.3.11-1) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). Reading package lists... Building dependency tree... Reading state information... unixodbc-dev is already the newest version (2.3.11-1). You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: unixodbc : Depends: odbcinst1debian2 (>= 2.3.11-1) but it is not going to be installed Depends: libodbc1 (>= 2.3.11-1) but it is not going to be installed unixodbc-dev : Depends: odbcinst1debian2 (= 2.3.11-1) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
hm... interesting, you using self hosted runners? are there ones with different distros? I assume the varient would be because some runners have this dependency issue and some don't. Either way I assume I can run this apt --fix-broken install on fail and that would solve the issue
though on a second thought that would be a distro specific solution and the cool thing here is that I don't have any distro specific logic. hm.