Summary: | x11-libs/qt-core-4.8.2 - depgraph calculation problems running `emerge -vp qt-core' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Igor Franchuk <lanthruster> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Igor Franchuk
2012-10-23 09:48:29 UTC
(In reply to comment #0) > emerge -pv qt-core Try `emerge -uDN world'. > * IMPORTANT: config file '/etc/portage/package.keywords' needs updating. > * See the CONFIGURATION FILES section of the emerge > * man page to learn how to update config files. Fix that first. [...] > * IMPORTANT: 1 news items need reading for repository 'gentoo-zh'. > * IMPORTANT: 11 news items need reading for repository 'gentoo'. > * Use eselect news to read news items. Maybe you want to read those too. (In reply to comment #1) > (In reply to comment #0) > > emerge -pv qt-core > > Try `emerge -uDN world'. > > > * IMPORTANT: config file '/etc/portage/package.keywords' needs updating. > > * See the CONFIGURATION FILES section of the emerge > > * man page to learn how to update config files. > > Fix that first. > > [...] > > > * IMPORTANT: 1 news items need reading for repository 'gentoo-zh'. > > * IMPORTANT: 11 news items need reading for repository 'gentoo'. > > * Use eselect news to read news items. > > Maybe you want to read those too. Thank you for the reply. I'm living with Gentoo for a long time I use many applications and I'm sure that about 5% of them will be broken after -uDN world and I'd have to spend days fixing them, only discovering problems when I start an application. package.keywords error is irrelevant to this problem. There are merge cfg files in the portage folder with irrelevant to qt-core packages. If there is any other than -uDN world way of fixing this problem - please let me know. Thanks again! Well, first of all this is not a support channel - it's a bug tracker. Finding a solution for your situation is not the same as fixing bugs - you wouldn't see these problems you are seeing if you had kept your system up to date on a somewhat regular basis, say, updating once a month. There is no bug here. Which brings me to my second point, that back-porting bug fixes on systems that have not been upgraded simply isn't something Gentoo developers can support if it extends to beyond the basic system packages - you should properly maintain your system or it will break sooner or later. Thirdly, had you updated regularly, you wouldn't be seeing this problem. The /etc updates should have been merged, a viable upgrade path would be available from the old Qt packages to the new ones, and so forth. Maintaining that not updating helps you keep a stable system is a rather backward viewpoint, and many Gentoo developers and other Gentoo users uphold quite the reverse viewpoint. Try our Gentoo support chat channel irc://chat.freenode.net/#gentoo or http://forums.gentoo.org if you want to resolve this issue - it has no place on http://bugs.gentoo.org/ . Thank you for your viewpoint. To contradict to that I would mention that if you update system on regular basis or if you update Gentoo automatically it will become disfunctional pretty soon. And all your time will be spent on resolving issues which you're really not interested and which do not worth spending time on. If you're not a maintainer fixing a problem requires understanding of the algorithms and this understanding is reading the sources and tracing the code. But since you're not familiar with every package - it takes days to understand the problem and find the cure. And after the fix is applied you forget about the software layout and then the situation repeats itself. It's better to have authors to fix the problems or to become an author yourself. But I posted this message not because I was against spending time on this but rather because Emerge brings a meaningless output. I consider this as a bug or at least malfunction. There is no useful information about how to fix the problem and what packages exactly are responsible for the conflict. And usually when this kind of output is produced it indicates a problem in the program which produced this output. If this was a security program I would go to it's sources with 80% chance this output being a result of a bug either in some qt-package or emerge itself. (In reply to comment #3) > Well, first of all this is not a support channel - it's a bug tracker. > Finding a solution for your situation is not the same as fixing bugs - you > wouldn't see these problems you are seeing if you had kept your system up to > date on a somewhat regular basis, say, updating once a month. There is no > bug here. > > Which brings me to my second point, that back-porting bug fixes on systems > that have not been upgraded simply isn't something Gentoo developers can > support if it extends to beyond the basic system packages - you should > properly maintain your system or it will break sooner or later. > > Thirdly, had you updated regularly, you wouldn't be seeing this problem. The > /etc updates should have been merged, a viable upgrade path would be > available from the old Qt packages to the new ones, and so forth. > Maintaining that not updating helps you keep a stable system is a rather > backward viewpoint, and many Gentoo developers and other Gentoo users uphold > quite the reverse viewpoint. > > Try our Gentoo support chat channel irc://chat.freenode.net/#gentoo or > http://forums.gentoo.org if you want to resolve this issue - it has no > place on http://bugs.gentoo.org/ . |