Luis Lepe
Markh Hi, I've just been able to install the mongo packages (on Centos) without any issues. Can you paste (to gist/pastebin/pastie) the contents of your /etc/yum. Dec 14, 2018 - I can get Edge and apigee-setup installed, but when I get to edge components, I keep getting the 'Package does not match intended download. My daily deployment validation deploys two Openlogic Centos 7.2 Azure VMs. Usually either one or both gets the yum error 'Package does not match intended download.
Not The Intended Use
Offline
ClearOS 6.2 on Hyper-V stuck on Upgrading packages
0votes
I'm writing a tutorial on How to install ClearOS 6.2 on Hyper-V.
The steps I'm doing are:
* Create Virtual Machine with 1 legacy adapter
* Install ClearOS
* Connect with ssh and run 'yum install kernel-2.6.32-220.13.1.v6.x86_64' (otherwise Linux Integration Componentes 3.2 will not install)
* reboot
* Mount LIC 3.2 ISO file
* reconnect with ssh and run
>mount –t iso9660 /dev/scd0 /mnt
>cd /mnt
>./install.sh
* shutdown virtual machine
* Remove legacy adapter and add two network adapters (one to the internet, one to the LAN)
* Start virtual machine
* From the Hyper-V console configure network (remove old adapter from configuration and add the two new ones)
This is where I'm stuck because as part of the configuration you need to upgrade the packages and the GUI doesn't help much...
By hand I tried to upgrade it with ssh and running:
> yum install app-base-1.1.2-1.v6.noarch
but it says:
Downloading Packages:
(1/19): app-base-1.1.2-1.v6.noarch.rpm | 187 kB 00:03
http://mirror3-toronto.clearsdn.com/clearos/community/6/updates/x86_64/RPMS/app-
base-1.1.2-1.v6.noarch.rpm: [Errno -1] Package does not match intended download.
Suggestion: run yum --enablerepo=clearos-updates clean metadata
Trying other mirror.
(1/19): app-base-1.1.2-1.v6.noarch.rpm | 187 kB --:--
http://mirror2-dallas.clearsdn.com/clearos/community/6/updates/x86_64/RPMS/app-b
ase-1.1.2-1.v6.noarch.rpm: [Errno -1] Package does not match intended download.
Suggestion: run yum --enablerepo=clearos-updates clean metadata
Trying other mirror.
(1/19): app-base-1.1.2-1.v6.noarch.rpm | 187 kB 00:01
http://mirror2-houston.clearsdn.com/clearos/community/6/updates/x86_64/RPMS/app-
base-1.1.2-1.v6.noarch.rpm: [Errno -1] Package does not match intended download.
Suggestion: run yum --enablerepo=clearos-updates clean metadata
Trying other mirror.
(1/19): app-base-1.1.2-1.v6.noarch.rpm | 187 kB 00:00
http://mirror2-dc.clearsdn.com/clearos/community/6/updates/x86_64/RPMS/app-base-
1.1.2-1.v6.noarch.rpm: [Errno -1] Package does not match intended download. Sugg
estion: run yum --enablerepo=clearos-updates clean metadata
Trying other mirror.
(1/19): app-base-1.1.2-1.v6.noarch.rpm | 187 kB 00:03
http://mirror1.timburgess.net/clearos/community/6/updates/x86_64/RPMS/app-base-1
.1.2-1.v6.noarch.rpm: [Errno -1] Package does not match intended download. Sugge
stion: run yum --enablerepo=clearos-updates clean metadata
Trying other mirror.
[errors cut]
Error Downloading Packages:
1:app-base-1.1.2-1.v6.noarch: failure: RPMS/app-base-1.1.2-1.v6.noarch.rpm fro
m clearos-updates: [Errno 256] No more mirrors to try.
1:app-base-core-1.1.2-1.v6.noarch: failure: RPMS/app-base-core-1.1.2-1.v6.noar
ch.rpm from clearos-updates: [Errno 256] No more mirrors to try.
Any ideas will be greatly appreciated.
The steps I'm doing are:
* Create Virtual Machine with 1 legacy adapter
* Install ClearOS
* Connect with ssh and run 'yum install kernel-2.6.32-220.13.1.v6.x86_64' (otherwise Linux Integration Componentes 3.2 will not install)
* reboot
* Mount LIC 3.2 ISO file
* reconnect with ssh and run
>mount –t iso9660 /dev/scd0 /mnt
>cd /mnt
>./install.sh
* shutdown virtual machine
* Remove legacy adapter and add two network adapters (one to the internet, one to the LAN)
* Start virtual machine
* From the Hyper-V console configure network (remove old adapter from configuration and add the two new ones)
This is where I'm stuck because as part of the configuration you need to upgrade the packages and the GUI doesn't help much...
By hand I tried to upgrade it with ssh and running:
> yum install app-base-1.1.2-1.v6.noarch
but it says:
Downloading Packages:
(1/19): app-base-1.1.2-1.v6.noarch.rpm | 187 kB 00:03
http://mirror3-toronto.clearsdn.com/clearos/community/6/updates/x86_64/RPMS/app-
base-1.1.2-1.v6.noarch.rpm: [Errno -1] Package does not match intended download.
Suggestion: run yum --enablerepo=clearos-updates clean metadata
Trying other mirror.
(1/19): app-base-1.1.2-1.v6.noarch.rpm | 187 kB --:--
http://mirror2-dallas.clearsdn.com/clearos/community/6/updates/x86_64/RPMS/app-b
ase-1.1.2-1.v6.noarch.rpm: [Errno -1] Package does not match intended download.
Suggestion: run yum --enablerepo=clearos-updates clean metadata
Trying other mirror.
(1/19): app-base-1.1.2-1.v6.noarch.rpm | 187 kB 00:01
http://mirror2-houston.clearsdn.com/clearos/community/6/updates/x86_64/RPMS/app-
base-1.1.2-1.v6.noarch.rpm: [Errno -1] Package does not match intended download.
Suggestion: run yum --enablerepo=clearos-updates clean metadata
Trying other mirror.
(1/19): app-base-1.1.2-1.v6.noarch.rpm | 187 kB 00:00
http://mirror2-dc.clearsdn.com/clearos/community/6/updates/x86_64/RPMS/app-base-
1.1.2-1.v6.noarch.rpm: [Errno -1] Package does not match intended download. Sugg
estion: run yum --enablerepo=clearos-updates clean metadata
Trying other mirror.
(1/19): app-base-1.1.2-1.v6.noarch.rpm | 187 kB 00:03
http://mirror1.timburgess.net/clearos/community/6/updates/x86_64/RPMS/app-base-1
.1.2-1.v6.noarch.rpm: [Errno -1] Package does not match intended download. Sugge
stion: run yum --enablerepo=clearos-updates clean metadata
Trying other mirror.
[errors cut]
Error Downloading Packages:
1:app-base-1.1.2-1.v6.noarch: failure: RPMS/app-base-1.1.2-1.v6.noarch.rpm fro
m clearos-updates: [Errno 256] No more mirrors to try.
1:app-base-core-1.1.2-1.v6.noarch: failure: RPMS/app-base-core-1.1.2-1.v6.noar
ch.rpm from clearos-updates: [Errno 256] No more mirrors to try.
Any ideas will be greatly appreciated.
Match Does It Work
- TheokratOffline0votesLuis,
I'm not sure if this will be any help to you or not, but with some additional help I was able to get ClearOS 6.2 Community running on Hyper-V. See this thread for details:
http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,37/func,view/id,40416/
I'm not quite sure what
yum install app-base-1.1.2-1.v6.noarch
does. Is that to install the ClearOS apps? If so, are you not able to use the web logon page and install the ClearOS apps from there?
One other thought ... are you sure that
2.6.32-220.13.1.v6.x86_64
is the kernel you're running with? I was unable to get the Microsoft Linux Integration components to work with this kernel. When I entered:
yum install kmod-igb
(see above thread for details) I ended up with this kernel:
2.6.32-220.17.1.el6.x86_64
And with that kernel I was able to use the Synthetic NICs in Hyper-V.
I'm wondering if something you did caused the kernel to be changed from 2.6.32-220.13.1.v6.x86_64 to something else? And if so perhaps that is why you're getting the error messages when you try to execute 'yum install app-base-1.1.2-1.v6.noarch'?
If none of this is helpful to you I hope that someone else can find a solution for you. - Luis LepeOffline0votesI installed community.
No idea whatsoever on why you're getting different results than mine.
At first I tried to install LIC 3.2 whithout doing anything else but it errored out until I installed that specific version of the kernel.
I'm guessing you got another kernel version possibly because your processor is different than mine.
Frankly I gave up didn't had much time to spend on this. - TheokratOffline0votesLuis,
I do not know why ClearOS doesn't behave the same way for me as it did for you.
AMD FX-8150
Microsoft Hyper-V 2008 R2 SP1
clearos-community-6.2-x86_64.iso
I didn't understand your comment, 'Connect with ssh and run 'yum install kernel-2.6.32-220.13.1.v6.x86_64' (otherwise Linux Integration Componentes 3.2 will not install)' as that is the version of the Linux kernel I see installed.
login as: root
root@clearos62dev's password:
[root@clearos62dev ~]# uname -r
2.6.32-220.13.1.v6.x86_64
Just in case the install command you mentioned did something I did not expect I tried it anyway, but didn't get any results.
[root@clearos62dev ~]# yum install kernel-2.6.32-220.13.v6.x86_64
Loaded plugins: clearcenter-marketplace, fastestmirror
ClearCenter Marketplace: fetching repositories...
Loading mirror speeds from cached hostfile
* clearos: mirror3-toronto.clearsdn.com
* clearos-addons: mirror3-toronto.clearsdn.com
* clearos-core: mirror3-toronto.clearsdn.com
* clearos-extras: mirror3-toronto.clearsdn.com
* clearos-updates: mirror3-toronto.clearsdn.com
* private-clearcenter-dyndns: download1.clearsdn.com:80
private-clearcenter-dyndns 2/2
Setting up Install Process
No package kernel-2.6.32-220.13.v6.x86_64 available.
Error: Nothing to do
I tried enabling all the repositories and searching to see if a kernel with that name was available, but didn't see anything.
[root@clearos62dev ~]# yum search kernel-
Loaded plugins: clearcenter-marketplace, fastestmirror
ClearCenter Marketplace: fetching repositories...
Loading mirror speeds from cached hostfile
* clearos: mirror3-toronto.clearsdn.com
* clearos-addons: mirror3-toronto.clearsdn.com
* clearos-contribs: mirror3-toronto.clearsdn.com
* clearos-core: mirror3-toronto.clearsdn.com
* clearos-dev: mirror3-toronto.clearsdn.com
* clearos-developer: download4.clearsdn.com
* clearos-epel: mirrors.xmission.com
* clearos-extras: mirror3-toronto.clearsdn.com
* clearos-test: mirror3-toronto.clearsdn.com
* clearos-updates: mirror3-toronto.clearsdn.com
* clearos-updates-testing: mirror3-toronto.clearsdn.com
* private-clearcenter-dyndns: download2.clearsdn.com:80
private-clearcenter-dyndns 2/2
N/S Matched: kernel-
kernel-debug.x86_64 : The Linux kernel compiled with extra debugging enabled
kernel-debug.i686 : The Linux kernel compiled with extra debugging enabled
kernel-debug-devel.x86_64 : Development package for building kernel modules to
: match the debug kernel
kernel-debug-devel.i686 : Development package for building kernel modules to
: match the debug kernel
kernel-devel.x86_64 : Development package for building kernel modules to match
: the kernel
kernel-devel.i686 : Development package for building kernel modules to match the
: kernel
kernel-doc.noarch : Various documentation bits found in the kernel source
kernel-firmware.noarch : Firmware files used by the Linux kernel
kernel-headers.x86_64 : Header files for the Linux kernel for use by glibc
kernel-headers.i686 : Header files for the Linux kernel for use by glibc
Name and summary matches only, use 'search all' for everything.
You didn't mention whether you installed ClearOS Community or Professional? I had been using the Community install, but tried the Professional and ran into a new problem during the next step (after selecting Professional).
Exception: Cannot find a valid baseurl for repo: clearos
Any ideas on why your results are different than mine? - TheokratOffline0votesLuis,
I just stumbled across your post and realized it is similar to another post (ClearOS 6.2 Hyper-v) and problem I've been working on.
http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,37/func,view/id,40416/#42485
One thing that puzzles me about your post is that you mentioned:
Connect with ssh and run 'yum install kernel-2.6.32-220.13.1.v6.x86_64' (otherwise Linux Integration Componentes 3.2 will not install)
It appeared to me that kernel-2.6.32-220.13.1.v6.x86_64 was the default that shipped with ClearOS 6.2? At least in my experience (detailed in above link) I was on 2.6.32-220 and after performing all yum upgrades then I got the 2.6.32-220.17.1.v6.x86_64 kernel.
The other thing that puzzles me is you seem to have been able to get the Microsoft Linux v3.2 components installed on 2.6.32-220.13.1.v6.x86_64 kernel? I got errors (see other post) on both 2.6.32-220.13.1.v6.x86_64 and 2.6.32-220.17.1.v6.x86_64.
One thing that is different is I had ClearOS 6.2 community configured in gateway mode whereas you mentioned performing the initial upgrades and installing Microsoft v3.2 components with a single interface in standalone mode? It seems odd that should make a difference, but I'll have to try that and see if it works for me.
If I can get that far then I'll see if I run into the same problems you did. If I do I'm also not sure how to resolve those issues, but at least you seem to have gotten further than I did in getting ClearOS to run properly on Hyper-V.
Package Does Not Match Intended Download 2017
Please login to post a reply
Package Does Not Match Intended Download For Pc
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »