Mdthbs

Why does the cable resistance jump from a low value to high value at a particular frequency?

Word for an event that will likely never happen again

Escape Velocity - Won't the orbital path just become larger with higher initial velocity?

What are the odds of rolling specific ability score totals in D&D?

When was "Fredo" an insult to Italian-Americans?

Units of measurement, especially length, when body parts vary in size among races

Does fossil fuels use since 1990 account for half of all the fossil fuels used in history?

How do I call a 6-digit Australian phone number with a US-based mobile phone?

Is this bar slide trick shown on Cheers real or a visual effect?

Good textbook for queueing theory and performance modeling

What are the advantages of this gold finger shape?

What is a "soap"?

Is there any official ruling on how characters go from 0th to 1st level in a class?

What is the most difficult concept to grasp in Calculus 1?

Sword-and-sorcery flick from the 80s with a magic scarf that saves the hero's life

Is there a word for returning to unpreparedness?

Would the USA be eligible to join the European Union?

To show that a recursively defined sequence is Cauchy - How?

Unconventional examples of mathematical modelling

Is there a name for the technique in songs/poems, where the rhyming pattern primes the listener for a certain line, which never comes?

Is it possible to know the exact chord from the roman numerals

Do I have to cite common CS algorithms?

What should I do if actually I found a serious flaw in someone's PhD thesis and an article derived from that PhD thesis?

Is there a fallacy about "appeal to 'big words'"?

Yum doesn't update package dependency

How do I create an RPM package that would fail a YUM transaction if certain creteria are metWhat is the correct way to resolve this rpm conflict? (Error: p11-kit-trust conflicts with nss-3.13.3-6.el6.x86_64)How do I install an .rpm that fails with an error about an .so file not being found from Python 2.6?Without using the Yum cache, can I retrieve or reconstruct an RPM after it has been installed?How to update a disconnected CentOS system from a list of installed RPMs?cannot offline install vnc server on CentOS 7

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

0

I have a package, for just simplicity, named as 'main1', which depends on 'dependant-package' - in the rpm, there is no version number requirement specified, so in my system, yum installed 'dependant-package 1.0'.

When I got a new package, named as 'main2', which depends on 'dependant-package = 2.0', yum strictly refuse to upgrade this dependant package:

--> Finished Dependency Resolution

Error: Package: main2.noarch (new-repo)

           Requires: dependant-package = 2.0

           Installed: dependant-package-1.0-1.noarch (old-repo)

               dependant-package = 1.0-1

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest

The new packages, and repo looks correct, so not clear what's going on.
If I force yum to pick the new repo, interestingly it works:

yum install --disablerepo=* --enablerepo=new-repo  main2

What's going on? Why yum doesn't even try to upgrade?

yum rpm

share|improve this question

asked yesterday

RenszarvRenszarv

1

New contributor

Renszarv is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

0

I have a package, for just simplicity, named as 'main1', which depends on 'dependant-package' - in the rpm, there is no version number requirement specified, so in my system, yum installed 'dependant-package 1.0'.

When I got a new package, named as 'main2', which depends on 'dependant-package = 2.0', yum strictly refuse to upgrade this dependant package:

--> Finished Dependency Resolution

Error: Package: main2.noarch (new-repo)

           Requires: dependant-package = 2.0

           Installed: dependant-package-1.0-1.noarch (old-repo)

               dependant-package = 1.0-1

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest

The new packages, and repo looks correct, so not clear what's going on.
If I force yum to pick the new repo, interestingly it works:

yum install --disablerepo=* --enablerepo=new-repo  main2

What's going on? Why yum doesn't even try to upgrade?

yum rpm

share|improve this question

asked yesterday

RenszarvRenszarv

1

New contributor

Renszarv is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

I have a package, for just simplicity, named as 'main1', which depends on 'dependant-package' - in the rpm, there is no version number requirement specified, so in my system, yum installed 'dependant-package 1.0'.

When I got a new package, named as 'main2', which depends on 'dependant-package = 2.0', yum strictly refuse to upgrade this dependant package:

--> Finished Dependency Resolution

Error: Package: main2.noarch (new-repo)

           Requires: dependant-package = 2.0

           Installed: dependant-package-1.0-1.noarch (old-repo)

               dependant-package = 1.0-1

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest

The new packages, and repo looks correct, so not clear what's going on.
If I force yum to pick the new repo, interestingly it works:

yum install --disablerepo=* --enablerepo=new-repo  main2

What's going on? Why yum doesn't even try to upgrade?

yum rpm

share|improve this question

asked yesterday

RenszarvRenszarv

1

New contributor

Renszarv is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

--> Finished Dependency Resolution

Error: Package: main2.noarch (new-repo)

           Requires: dependant-package = 2.0

           Installed: dependant-package-1.0-1.noarch (old-repo)

               dependant-package = 1.0-1

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest

yum install --disablerepo=* --enablerepo=new-repo  main2

share|improve this question

asked yesterday

RenszarvRenszarv

1

New contributor

Renszarv is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

asked yesterday

RenszarvRenszarv

1

New contributor

Renszarv is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked yesterday

RenszarvRenszarv

1

New contributor

Renszarv is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked yesterday

RenszarvRenszarv

1