NuxRo commented on PR #10057:
URL: https://github.com/apache/cloudstack/pull/10057#issuecomment-2527999726

   > cc @NuxRo still doesn't work:
   > 
   > ```
   > root@devcloud:~# dnf install cloudstack-common-4.20.1.0-1.noarch.rpm
   > Updating and loading repositories:
   >  Fedora 41 - aarch64 - Updates                                             
                                                                      100% |  
14.8 KiB/s |   6.7 KiB |  00m00s
   >  Fedora 41 - aarch64 - Updates                                             
                                                                      100% |  
71.9 KiB/s | 292.5 KiB |  00m04s
   > Repositories loaded.
   > Failed to resolve the transaction:
   > Problem: conflicting requests
   >   - nothing provides libc.so.6 needed by 
cloudstack-common-4.20.1.0-1.noarch from @commandline
   >   - nothing provides libc.so.6(GLIBC_2.0) needed by 
cloudstack-common-4.20.1.0-1.noarch from @commandline
   >   - nothing provides libc.so.6(GLIBC_2.1) needed by 
cloudstack-common-4.20.1.0-1.noarch from @commandline
   >   - nothing provides libc.so.6(GLIBC_2.2) needed by 
cloudstack-common-4.20.1.0-1.noarch from @commandline
   >   - nothing provides libc.so.6(GLIBC_2.2.3) needed by 
cloudstack-common-4.20.1.0-1.noarch from @commandline
   >   - nothing provides libc.so.6(GLIBC_2.3) needed by 
cloudstack-common-4.20.1.0-1.noarch from @commandline
   > You can try to add to command line:
   >   --skip-broken to skip uninstallable packages
   > ```
   > 
   > But the workaround was to `rpm -ivh 
cloudstack-common-4.20.1.0-1.noarch.rpm --nodeps`.
   
   I'll try to find some time and test for a solution.
   In theory if we specify all our deps correctly in the spec file then we can 
use "AutoReqProv: no" which should sort this problem out.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to