You are not logged in.
similar problem here :
[kaveiros@arch ~]$ sudo pacman -Suy
Password:
:: Synchronizing package databases...
core 35.7K 127.3K/s 00:00:00 [######################] 100%
extra 468.0K 202.1K/s 00:00:02 [######################] 100%
community 385.1K 200.1K/s 00:00:02 [######################] 100%
multilib 20.3K 100.6K/s 00:00:00 [######################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
:: gobject-introspection and gir-repository are in conflict. Remove gir-repository? [y/N]
What shall I do? Is it a bug?
Offline
do it. is not a bug
Give what you have. To someone, it may be better than you dare to think.
Offline
Edit: nwm, wonder beat me to it.
Last edited by karol (2010-10-04 13:14:48)
Offline
Ok did it everything works fine.thanks
Offline
gobject-introspection says, it replaces gir-repository. Will it therefore provide gir-repository? Or will you have to modify the packages that depend on gir-repository (there are none in the repos anymore I think)?
Last edited by Cdh (2010-10-04 14:54:00)
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
gir-repository is not required anymore and nothing in our repos depend on it. therefor a provides is useless.
we wanted to get rid of it somehow because it was conflicting with our packages that have gir files now.
Give what you have. To someone, it may be better than you dare to think.
Offline
Excuse me.
I've the same "problem" of Kaveiros. If I confirm the removal of "gir-repository", pacman shows me about 142 mb of updates to be downloaded. Is this normal?
Thank you for your help
Offline
yes is normal.
Give what you have. To someone, it may be better than you dare to think.
Offline
gir-repository is not required anymore and nothing in our repos depend on it. therefor a provides is useless.
we wanted to get rid of it somehow because it was conflicting with our packages that have gir files now.
Ok, then just editing the depends in AUR packages with gir-repository dependency should work. Thanks.
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
Dudes, how can you consider this not being a bug. What does an average experienced user know about package dependencies of those packages in particular? Nothing! He will try guessing, go look for it on-line and generally just waste time. How many broken installations will this not-bug generate? Not to mention future cases.
pacman -Syu is supposed to upgrade the system and the last thing the user need to do in this situation is to make decisions that can potentially harm his system when the package manager should have known the correct action in the first place.
Is it because pacman cannot handle superseded packages or because the packages in question are not properly marked in the database?
Last edited by misiu_mp (2010-10-05 06:24:52)
Offline