Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
On Wednesday 29 October 2008 19:59:11 Alan McKinnon wrote: A last note on emerge's output, especially with blockers: the time spent to read all the portage pages (several times) is time very well spent. I recommend when next you get blockers, is to rerun emerge with -t and take note of what packages cause a blocker to be pulled in or up|downgraded. make a list of everything involved and read the ebuilds. Plot it all out with pen and pencil, do this repetitively till you have a lightbulb moment where it all suddenly makes sense. Sound advice, but it didn't help me last week. I had to take a more devious approach involving a new test system and repeated attempts to install the same packages on it as were on the live system until I found the one that was causing the trouble. It was then a simple matter to remove it from the world file, where it shouldn't have been in the first place, and I can now dispense with the test system. So I could have saved myself several days of head-banging if I'd just looked in the world file - I'd have noticed the offender straight away. 20-20 hindsight. Wonderful. Most folks around here have done this at some point and there doesn't seem to be a shortcut :-) Indeed. -- Rgds Peter
Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
On Wed, Oct 29, 2008 at 10:23 PM, Andrey Vul [EMAIL PROTECTED] wrote: But I usually use emerge -p file in order to see the difference in dependencies from testing USE flags. I would always choose -pN over -aN. Where's the portage to-do list? If you can find it, add these two items: fix the uname add pager support for -p, -a, -t Well, I didn't find it with the miserably little effort I put into looking... so instead, I wrote up a quick hack to emerge to implement use of a pager any time the internal display() function is called. I made the mistake of writing it against the 'stable' version of portage, though... so I'll be (hopefully) porting it over to Portage 2.2_rc12 (the newest my current state of laziness allows on my amd64 machine). Any chance anyone here's a bit more skilled with python than I am and would want to remind me of all the error checking I left out? After I get a patch handy, at least... As for the 'fix the uname' bit... I haven't had a chance to dig through the changelogs to see the who/when/why of the change that made it what it is now, and whether (as was clarified as likely in the related thread here) the current output is what's intended. -- Poison [BLX] Joshua M. Murphy
Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
On Wed, Oct 29, 2008 at 12:33 PM, Rafael Barrera Oro [EMAIL PROTECTED] wrote: Hello people, i tried to install kde-meta-4.1.2 and i ran across a few problems. The thing is that some packages are blocking packages required for the installation The following is output of portage when displaying the blocking packages [uninstall] app-crypt/qca-1.0-r2 [?] [blocks b ] app-crypt/qca-1.0-r3 (app-crypt/qca-1.0-r3 is blocking app-crypt/qca-2.0.1-r1) [blocks B ] =x11-libs/qt-4.4.0_alpha:4 (=x11-libs/qt-4.4.0_alpha:4 is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-sql-4.4.2, x11-libs/qt-gui-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2, x11-libs/qt-webkit-4.4.2, x11-libs/qt-opengl-4.4.2) [blocks B ] sys-fs/udev-114 (sys-fs/udev-114 is blocking media-gfx/sane-backends-1.0.19-r2, media-libs/libgphoto2-2.4.2) My usual solution for problems of this kind is to mercilessly unmerge any packages that stand in my way, but, considering we are talking about packages like qt and udev, i must admit i do not dare to follow my usual strategy. AFAIK, only KDE4 uses Qt 4. Unmerge x11-libs/qt:4 and emerge the split qt. Unless you don't have qt installed, then something's weird. Can you post the output of eix x11-libs/qt -c ? As long as you don't use USB or any hotplug devices, you can unmerge and remerge udev at will. I guess the paths i can follow are masking some packages or unmerging some packages, being confronted by such a decision and unsure of what i should do, i decided to seek your advice. Make backups, then do what you usually do. -- Andrey Vul A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
On Wednesday 29 October 2008 18:41:47 Andrey Vul wrote: [blocks B ] sys-fs/udev-114 (sys-fs/udev-114 is blocking media-gfx/sane-backends-1.0.19-r2, media-libs/libgphoto2-2.4.2) My usual solution for problems of this kind is to mercilessly unmerge any packages that stand in my way, but, considering we are talking about packages like qt and udev, i must admit i do not dare to follow my usual strategy. Instead of unmerging stuff without mercy, taking a sledgehammer to the problem and generally acting like a Windows user, I recommend you read the output and understand what is going on. It clearly says that your *current* version of udev which is less than 114 is blocking sane-backends and libgphoto. So, merge udev separately: emerge -av1 udev there's no need for udev to go in world, it's already in system. Then emerge world and it will probably work (after you deal with qt that is, but another poster told you how to do that) -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
Thank you both for your responses, i will try dealing with QT first and then emerge udev separately, without any mercilless barbaric running-around-barely-dressed-waving-an-axe-around unmerging. I'm gonna miss the sledgehammer though... Seroiusly, thanks very much for your help PD: As soon as i get it done i will tell how the outcome was 2008/10/29 Alan McKinnon [EMAIL PROTECTED] On Wednesday 29 October 2008 18:41:47 Andrey Vul wrote: [blocks B ] sys-fs/udev-114 (sys-fs/udev-114 is blocking media-gfx/sane-backends-1.0.19-r2, media-libs/libgphoto2-2.4.2) My usual solution for problems of this kind is to mercilessly unmerge any packages that stand in my way, but, considering we are talking about packages like qt and udev, i must admit i do not dare to follow my usual strategy. Instead of unmerging stuff without mercy, taking a sledgehammer to the problem and generally acting like a Windows user, I recommend you read the output and understand what is going on. It clearly says that your *current* version of udev which is less than 114 is blocking sane-backends and libgphoto. So, merge udev separately: emerge -av1 udev there's no need for udev to go in world, it's already in system. Then emerge world and it will probably work (after you deal with qt that is, but another poster told you how to do that) -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
On Wed, Oct 29, 2008 at 1:03 PM, Rafael Barrera Oro [EMAIL PROTECTED] wrote: Thank you both for your responses, i will try dealing with QT first and then emerge udev separately, without any mercilless barbaric running-around-barely-dressed-waving-an-axe-around unmerging. It'll be faster do do udev first. Get it done and over with. Qt will take 2+ hours to compile. I'm gonna miss the sledgehammer though... I sledgehammer my way through blocks and no problems here :D Seroiusly, thanks very much for your help PD: As soon as i get it done i will tell how the outcome was 2008/10/29 Alan McKinnon [EMAIL PROTECTED] On Wednesday 29 October 2008 18:41:47 Andrey Vul wrote: [blocks B ] sys-fs/udev-114 (sys-fs/udev-114 is blocking media-gfx/sane-backends-1.0.19-r2, media-libs/libgphoto2-2.4.2) My usual solution for problems of this kind is to mercilessly unmerge any packages that stand in my way, but, considering we are talking about packages like qt and udev, i must admit i do not dare to follow my usual strategy. Instead of unmerging stuff without mercy, taking a sledgehammer to the problem and generally acting like a Windows user, I recommend you read the output and understand what is going on. It clearly says that your *current* version of udev which is less than 114 is blocking sane-backends and libgphoto. So, merge udev separately: emerge -av1 udev I prefer emerge -1pv udev look at output emerge -1 udev there's no need for udev to go in world, it's already in system. Then emerge world and it will probably work (after you deal with qt that is, but another poster told you how to do that) -- Andrey Vul A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
On Wednesday 29 October 2008 19:03:51 Rafael Barrera Oro wrote: Thank you both for your responses, i will try dealing with QT first and then emerge udev separately, without any mercilless barbaric running-around-barely-dressed-waving-an-axe-around unmerging. There you go, that's a good lad :-) I'm gonna miss the sledgehammer though... Don't dismiss it entirely thoguh. It comes in handy when dealing with recalcitrant incorigible users. Very very handy indeed. A last note on emerge's output, especially with blockers: the time spent to read all the portage pages (several times) is time very well spent. I recommend when next you get blockers, is to rerun emerge with -t and take note of what packages cause a blocker to be pulled in or up|downgraded. make a list of everything involved and read the ebuilds. Plot it all out with pen and pencil, do this repetitively till you have a lightbulb moment where it all suddenly makes sense. Most folks around here have done this at some point and there doesn't seem to be a shortcut :-) -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
On Wed, 29 Oct 2008 13:14:34 -0400, Andrey Vul wrote: emerge -av1 udev I prefer emerge -1pv udev look at output emerge -1 udev Which means you have to wait for the dependency resolver to run twice. Which is why it's better to use emerge -1av udev look at output press enter -- Neil Bothwick If it ain't broke, wait a day or two!! signature.asc Description: PGP signature
Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
On Wednesday 29 October 2008 22:46:34 Neil Bothwick wrote: On Wed, 29 Oct 2008 13:14:34 -0400, Andrey Vul wrote: emerge -av1 udev I prefer emerge -1pv udev look at output emerge -1 udev Which means you have to wait for the dependency resolver to run twice. Which is why it's better to use emerge -1av udev look at output press enter you have it wrong: emerge -1av udev do not press enter look at output press enter :-) -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
On Wed, 29 Oct 2008 23:52:25 +0200, Alan McKinnon wrote: emerge -1av udev look at output press enter you have it wrong: emerge -1av udev do not press enter look at output press enter Looking at the output only confuses me, I prefer to skip that step :) -- Neil Bothwick The box said 'needs Win95 or better' so I bought an Amiga. signature.asc Description: PGP signature
Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
On Wed, Oct 29, 2008 at 4:46 PM, Neil Bothwick [EMAIL PROTECTED] wrote: On Wed, 29 Oct 2008 13:14:34 -0400, Andrey Vul wrote: emerge -av1 udev I prefer emerge -1pv udev look at output emerge -1 udev Which means you have to wait for the dependency resolver to run twice. Which is why it's better to use emerge -1av udev look at output press enter I don't like package managers which require interactivity. emerge -uvDp world | less is easier to parse then emerge -upDa world. Why? Because I don't have to find a way of transferring return if less handles all of the keyboard input. So I prefer two stages: 1) pretend merge - single verbosity - and look at output 2) actual merge - normal / quiet - and pipe to tee -- Neil Bothwick If it ain't broke, wait a day or two!! -- Andrey Vul A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
On Wed, Oct 29, 2008 at 7:26 PM, Andrey Vul [EMAIL PROTECTED] wrote: I don't like package managers which require interactivity. emerge -uvDp world | less is easier to parse then emerge -upDa world. Why? Because I don't have to find a way of transferring return if less handles all of the keyboard input. So I prefer two stages: 1) pretend merge - single verbosity - and look at output 2) actual merge - normal / quiet - and pipe to tee So what you're saying... is that emerge should have a switch to turn on, when using -p, -a, and/or -t, a pager? Particularly one that, until you're content with -a in particular, doesn't accidentally have a means of handing output back off to the emerge for the yes/no? This would spare the double run of the dependency checker while giving users who want it a pager to use and giving the rest the same functionality a simple -a gives now... something like etc-update's use of a pager comes to mind. Let's see... -P is taken for --prune ... --less/-L or... --more/-m ... --more/-M ? Of course, --pager/-M would work too, but it's less intuitive (we already have --unmerge/-C ... so why not, I suppose). Not *quite* sure I'm up to the task at the moment, though. -- Poison [BLX] Joshua M. Murphy
Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
On Wed, Oct 29, 2008 at 9:44 PM, Joshua Murphy [EMAIL PROTECTED] wrote: On Wed, Oct 29, 2008 at 7:26 PM, Andrey Vul [EMAIL PROTECTED] wrote: I don't like package managers which require interactivity. emerge -uvDp world | less is easier to parse then emerge -upDa world. Why? Because I don't have to find a way of transferring return if less handles all of the keyboard input. So I prefer two stages: 1) pretend merge - single verbosity - and look at output 2) actual merge - normal / quiet - and pipe to tee So what you're saying... is that emerge should have a switch to turn on, when using -p, -a, and/or -t, a pager? Particularly one that, until you're content with -a in particular, doesn't accidentally have a means of handing output back off to the emerge for the yes/no? This Yes. would spare the double run of the dependency checker while giving users who want it a pager to use and giving the rest the same functionality a simple -a gives now... something like etc-update's use of a pager comes to mind. Let's see... -P is taken for --prune ... --less/-L or... --more/-m ... --more/-M ? Of course, --pager/-M would work too, but it's less intuitive (we already have --unmerge/-C ... so why not, I suppose). Not *quite* sure I'm up to the task at the moment, though. But I usually use emerge -p file in order to see the difference in dependencies from testing USE flags. I would always choose -pN over -aN. Where's the portage to-do list? If you can find it, add these two items: fix the uname add pager support for -p, -a, -t -- Andrey Vul A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
