Created attachment 938414 [details] debug_log Description of problem: I am using Fedora-Live-Workstation-x86_64-21_Alpha-1.iso Version-Release number of selected component (if applicable): DevAssistance version is 0.9.1-1.fc21 How reproducible: 1: Select Project type as expree.js project 2: Give project name as node (not sure significance of that) 3: Click on Run Actual results: I have got an error that failed dependencies though dependencies were resolved automatically. I have attached debug.log
Thanks for the bug. This bug is related to openssl-libs which causes multilib problems. See your debug.log. Reassigning to openssl-libs. For fast orientation output from debug.log: ---> Package openssl.x86_64 1:1.0.1i-3.fc21 will be reinstalled ---> Package openssl.x86_64 1:1.0.1i-4.fc21 will be an update ---> Package openssl-devel.x86_64 1:1.0.1i-4.fc21 will be installed ---> Package openssl-libs.x86_64 1:1.0.1i-3.fc21 will be reinstalled ---> Package openssl-libs.x86_64 1:1.0.1i-4.fc21 will be an update ---> Package pcre-devel.x86_64 0:8.35-6.fc21.1 will be installed ---> Package perl-srpm-macros.noarch 0:1-12.fc21 will be installed ---> Package redhat-rpm-config.noarch 0:24-2.fc21 will be installed ---> Package v8.x86_64 1:3.14.5.10-12.fc21 will be installed ---> Package v8-devel.x86_64 1:3.14.5.10-12.fc21 will be installed ---> Package zlib-devel.x86_64 0:1.2.8-7.fc21 will be installed --> Finished Dependency Resolution Error: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem. Eg.: 1. You have an upgrade for openssl-libs which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of openssl-libs of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude openssl-libs.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of openssl-libs installed, but yum can only see an upgrade for one of those architectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work. 3. You have duplicate versions of openssl-libs installed already. You can use "yum check" to get yum show these errors. ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). Protected multilib versions: 1:openssl-libs-1.0.1i-4.fc21.x86_64 != 1:openssl-libs-1.0.1i-3.fc21.x86_64 Error: Protected multilib versions: krb5-libs-1.12.2-8.fc21.x86_64 != krb5-libs-1.12.2-3.fc21.x86_64 Error: Protected multilib versions: 1:openssl-1.0.1i-4.fc21.x86_64 != 1:openssl-1.0.1i-3.fc21.x86_64 Error: Protected multilib versions: libgomp-4.9.1-9.fc21.x86_64 != libgomp-4.9.1-7.fc21.x86_64 Error: Protected multilib versions: libstdc++-4.9.1-9.fc21.x86_64 != libstdc++-4.9.1-7.fc21.x86_64
I think this is some problem with your installation, the repositories or yum. There was no change in openssl in regards to its multilib status in Fedora 21 development cycle. So I suppose it is either case 3. from above (then it is an installation problem), or 2. (then it is a bug in repository change). I do not see what could be fixed within openssl here.
Hi Tomas, I did not installed anything extra, I just installed whatever comes deafult with Fedora-Live-Workstation-x86_64-21_Alpha-1.iso Please let me if you want any more information.
Created attachment 941731 [details] Failed yum install launched by devassistant trying to create an Express.js project I have the same symptom - can't create an Express.js project - but what looks like a different mechanism. When I try to create an Express project, it does a dependency check. The install is failing - the 'nodejs-glob' package appears to be broken.
Filed bug 1147108 against nodejs-glob. It's probably irrelevant given that nodejs-glog-4.0.6 is available (bug 1030898).
Created attachment 941732 [details] screenshot of attempted install of 'glob' from NPM Bah! I cleaned up my Node directory structure (https://bugzilla.redhat.com/show_bug.cgi?id=1147108#c3) and reinstalled nodejs and npm via yum. This successfully brought in nodejs-glob. Then I did an Express project create in devassistant with just the dependency installation step checked. It installed a few more packages with yum and then tried to install "glob" via NPM! Could it be that Express needs the newer version of nodejs-glob and so it's going out to NPM? I don't know the Node.js stack at all - I'm just exploring this stuff.
Anish/Petr: This error occurs because the yum transaction devassistant creates forces a particular version of openssl.x86_64 to be updated without updating openssl.i686. A normal `yum install nodejs` would not hit this issue, since it wouldn't bother updating openssl to the latest version. You need to either not include every dependency under the sun in your yum transaction and let yum handle it on it's own, or ensure all multilib packages are included when you build your transactions. Ed: This issue seems to have a completely different cause.
Ugh, mid-air collision with that. Ed, let's work on your issue in the bug you created for nodejs-glob. If it turns out that devassistant is the culprit we can reassign that one after I've worked out what exactly is the problem there. The originally reported issue is different and is the result of a dependency of the main "nodejs" package, not "nodejs-glob".
(In reply to T.C. Hollingsworth from comment #8) > Ugh, mid-air collision with that. Ed, let's work on your issue in the bug > you created for nodejs-glob. If it turns out that devassistant is the > culprit we can reassign that one after I've worked out what exactly is the > problem there. > > The originally reported issue is different and is the result of a dependency > of the main "nodejs" package, not "nodejs-glob". Sounds good.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.