View previous topic :: View next topic |
Author |
Message |
padoor Advocate
Joined: 30 Dec 2005 Posts: 4185 Location: india
|
Posted: Sat Nov 12, 2011 4:33 am Post subject: emerge messages have stopped? |
|
|
Code: | ramaswamy@localtux ~ $ su
Password:
localtux ramaswamy # emerge wmmemfree
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) x11-plugins/wmmemfree-0.7-r2
>>> Installing (1 of 1) x11-plugins/wmmemfree-0.7-r2
>>> Recording x11-plugins/wmmemfree in "world" favorites file...
>>> Jobs: 1 of 1 complete Load avg: 1.45, 1.04, 1.21
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date.
localtux ramaswamy # |
new style of merge screen.
what will happen if a merge fails?
where to look for error messages?
today's update of 7 files did the same way.
no scrolling messages while merge of any of them _________________ reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name) |
|
Back to top |
|
|
desultory Bodhisattva
Joined: 04 Nov 2005 Posts: 9410
|
Posted: Sat Nov 12, 2011 5:43 am Post subject: |
|
|
padoor wrote: | new style of merge screen. | Which is now the default in the 2.1 and 2.2 series.
padoor wrote: | what will happen if a merge fails? | Messages will indicate failure.
padoor wrote: | where to look for error messages? | As before, they will be in "${PORTAGE_TMPDIR}/portage/${PVR}/temp/build.log".
padoor wrote: | today's update of 7 files did the same way.
no scrolling messages while merge of any of them | That was the intent, which can be overridden by including --quiet-build=n in EMERGE_DEFAULT_OPTS in /etc/make.conf. |
|
Back to top |
|
|
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Sat Nov 12, 2011 8:52 am Post subject: |
|
|
Quote: | That was the intent, which can be overridden by including --quiet-build=n in EMERGE_DEFAULT_OPTS in /etc/make.conf. |
Thank goodness for that. I'd lose a chief source of entertainment. Why watch TV when you can watch your computer compile it's software?
Cheers,
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
padoor Advocate
Joined: 30 Dec 2005 Posts: 4185 Location: india
|
Posted: Sat Nov 12, 2011 9:34 am Post subject: |
|
|
enjoy pappy_mcfae
probably it may reduce cpu and mem loads for no video out _________________ reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name) |
|
Back to top |
|
|
i92guboj Bodhisattva
Joined: 30 Nov 2004 Posts: 10315 Location: Córdoba (Spain)
|
Posted: Sat Nov 12, 2011 4:51 pm Post subject: |
|
|
padoor wrote: | enjoy pappy_mcfae
probably it may reduce cpu and mem loads for no video out |
This depends on your video driver, your terminal emulator en a few other things. However you can achieve the same thing just minimizing your window or going to another workspace.
However, even if I feel a bit disoriented right now, I am glad that this was implemented, overall taking into account that this new default can easily be reversed if you really want to get the old behaviour. |
|
Back to top |
|
|
DaggyStyle Watchman
Joined: 22 Mar 2006 Posts: 5909
|
Posted: Sat Nov 12, 2011 5:00 pm Post subject: |
|
|
pappy_mcfae wrote: | Quote: | That was the intent, which can be overridden by including --quiet-build=n in EMERGE_DEFAULT_OPTS in /etc/make.conf. |
Thank goodness for that. I'd lose a chief source of entertainment. Why watch TV when you can watch your computer compile it's software?
Cheers,
Pappy |
I've actually liked it... _________________ Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
Back to top |
|
|
firephoto Veteran
Joined: 29 Oct 2003 Posts: 1612 Location: +48° 5' 23.40", -119° 48' 30.00"
|
Posted: Sat Nov 12, 2011 5:09 pm Post subject: |
|
|
Seems like a punishment to those build systems that have clean output and progress indication like cmake. After reading the discussion that triggered this, it went from those ebuilds that can't display necessary errors needing changes to ... well I guess it just went to killing the build output completely.
What exactly was the issue that was corrected with this change to the defaults? _________________ #gentoo-kde on freenode |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21624
|
Posted: Sat Nov 12, 2011 5:52 pm Post subject: |
|
|
In my opinion, an upstream build system should not run quietly, unless it also has the ability to go back and give you a full explanation when things break. I dislike getting a build log where you have a compilation error, the name of the file, and nothing else. You do not know what compiler options the build system used and may not even know which features it decided to turn on/off. I much prefer the idea that the upstream build system be noisy and that Portage hide the output until needed, then go back and display the log when an error occurs. |
|
Back to top |
|
|
mv Watchman
Joined: 20 Apr 2005 Posts: 6747
|
Posted: Sat Nov 12, 2011 6:28 pm Post subject: |
|
|
Hu wrote: | In my opinion, an upstream build system should not run quietly [...] You do not know what compiler options the build system used and may not even know which features it decided to turn on/off |
You are mixing two things here: One is to display useful information which might help debugging (like the compiler/linker flags, utilities and features which are used - this should be output at the end of the configure phase, but can for autotools pakckages usually found in much more detail in the configure.log), and the other is useless output during compilation like repeating all compiler/linker flags for every command and even showing "if"-statements and other completely useless crap.
The point is that making the latter output more verbose does not give the desired information either but just makes looking at logs (and even more communicating and storing them) much more cumbersome and resource intensive. So the right[TM] way to go (at least with autotools based packages) would be to encourage --enable-silent-rules and to post the configure.log in case the upstream configure output is not very verbose in what is going on.
Unfortunately, gentoo takes currently the opposite road: It seems that --disable-silent-rules will be default in gentoo, soon. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21624
|
Posted: Sat Nov 12, 2011 7:14 pm Post subject: |
|
|
I have encountered enough build systems that have "special" flags for particular subdirectories that I consider the entire build log potentially useful. I recognize that some build systems are repetitive enough that your statement is correct, but some of them are not. I would much rather receive the full and noisy build log, then reprocess it with sed/grep to discard uninteresting sections. The storage cost is unfortunate, but necessary. |
|
Back to top |
|
|
mv Watchman
Joined: 20 Apr 2005 Posts: 6747
|
Posted: Sat Nov 12, 2011 9:51 pm Post subject: |
|
|
Hu wrote: | I have encountered enough build systems that have "special" flags for particular subdirectories that I consider the entire build log potentially useful. |
In the best case, this will show the compiler/linker flags. Concerning the important information that you ask for - which packages are (auto)detected, which features are activated, and in case of complex packages like texlive, which environment variables are possibly set (for the non-compiling part) - all this information will still only be available in the config.log (or might be visible during configure output). In particular, from the information which you are missing you gain at most one relatively unimportant - the compiler/linker flags - and these are in almost all cases already shown in the corresponding (subdirectory) configure output, since autotools does explicitly not support setting them locally per file/subdirectory but only per (sub)project. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21624
|
Posted: Sun Nov 13, 2011 12:40 am Post subject: |
|
|
Again, you assume that upstream uses a build system that provides some sort of sanity. There are packages that either skip autotools/cmake entirely or abuse them so badly that they should have skipped them. I never said that the config.log should not be included in a problem report. I only said that the build.log should be verbose and should be available. I do not care whether the build system is verbose on the console that runs it. I care only that the build system be sufficiently verbose in its logging that I can either identify why it broke or that I can provide a concise set of questions to the reporter. |
|
Back to top |
|
|
mv Watchman
Joined: 20 Apr 2005 Posts: 6747
|
Posted: Sun Nov 13, 2011 7:54 am Post subject: |
|
|
Hu wrote: | There are packages that either skip autotools/cmake entirely or abuse them so badly that they should have skipped them. |
Yep. But in such a case, if upstream does not provide sufficient logging/output anyway, there is not much you can do to get a better one (e.g. --disable-silent-rules won't work in such a case anyway). |
|
Back to top |
|
|
wrc1944 Advocate
Joined: 15 Aug 2002 Posts: 3435 Location: Gainesville, Florida
|
Posted: Sun Nov 13, 2011 2:41 pm Post subject: |
|
|
After today's portage update, suddenly no emerge output? WTF!
Luckily, I quickly found this thread after trying emerge -uDv, which didn't work.
Why would the Gentoo devs think making no detailed emerge output the default is a good idea? It's beyond me.
To us old-time Gentoo users (ten years now), that's one of the main reasons we like Gentoo. _________________ Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
Back to top |
|
|
Fitzcarraldo Advocate
Joined: 30 Aug 2008 Posts: 2034 Location: United Kingdom
|
Posted: Sun Nov 13, 2011 4:32 pm Post subject: |
|
|
I'm in two minds about this change, really. On the one hand I like to see precisely what's happening, but on the other hand it does make the output very compact and easy to assimilate when one is doing an emerge world:
Code: | meshedgedx fitzcarraldo # emerge -uvDN world
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] sys-devel/gcc-config-1.5-r2 [1.5-r1] 0 kB
[ebuild R ] dev-libs/apr-1.4.5 USE="urandom uuid -doc -older-kernels-compatibility -static-libs%" 0 kB
[ebuild R ] dev-libs/apr-util-1.3.12 USE="berkdb gdbm ldap -doc -freetds -mysql -odbc -postgres -sqlite -static-libs%" 0 kB
[ebuild U ] dev-python/sip-4.13 [4.12.4] USE="-debug -doc" 698 kB
[ebuild U ] dev-libs/glib-2.30.1-r2 [2.30.1-r1] USE="fam static-libs -debug -doc (-selinux) -systemtap -test -utils -xattr" 0 kB
[ebuild U ] dev-cpp/clucene-2.3.3.4 [0.9.21b-r1] USE="-debug -doc -static-libs (-threads%)" 2,189 kB
[ebuild U ] net-libs/libmsn-4.2 [4.1] USE="-debug" 310 kB
[ebuild U ] dev-python/PyQt4-4.8.6 [4.8.5] USE="X assistant dbus declarative kde opengl sql svg webkit -debug -doc -examples -multimedia -phonon -xmlpatterns" 9,436 kB
[ebuild U ] kde-base/plasma-workspace-4.7.3-r2 [4.7.3] USE="handbook rss semantic-desktop xinerama (-aqua) -debug -google-gadgets -gps (-kdeenablefinal) -python -qalculate" 0 kB
Total: 9 packages (7 upgrades, 2 reinstalls), Size of downloads: 12,631 kB
>>> Verifying ebuild manifests
>>> Starting parallel fetch
>>> Emerging (1 of 9) sys-devel/gcc-config-1.5-r2
>>> Installing (1 of 9) sys-devel/gcc-config-1.5-r2
>>> Emerging (2 of 9) dev-libs/apr-1.4.5
>>> Installing (2 of 9) dev-libs/apr-1.4.5
>>> Emerging (3 of 9) dev-libs/apr-util-1.3.12
>>> Installing (3 of 9) dev-libs/apr-util-1.3.12
>>> Emerging (4 of 9) dev-python/sip-4.13
>>> Installing (4 of 9) dev-python/sip-4.13
>>> Emerging (5 of 9) dev-libs/glib-2.30.1-r2
>>> Installing (5 of 9) dev-libs/glib-2.30.1-r2
>>> Emerging (6 of 9) dev-cpp/clucene-2.3.3.4
>>> Installing (6 of 9) dev-cpp/clucene-2.3.3.4
>>> Emerging (7 of 9) net-libs/libmsn-4.2
>>> Installing (7 of 9) net-libs/libmsn-4.2
>>> Emerging (8 of 9) dev-python/PyQt4-4.8.6
>>> Installing (8 of 9) dev-python/PyQt4-4.8.6
>>> Emerging (9 of 9) kde-base/plasma-workspace-4.7.3-r2
>>> Installing (9 of 9) kde-base/plasma-workspace-4.7.3-r2
>>> Jobs: 9 of 9 complete Load avg: 3.01, 3.29, 2.40
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date.
* After world updates, it is important to remove obsolete packages with
* emerge --depclean. Refer to `man emerge` for more information.
meshedgedx fitzcarraldo # |
I'll have to defer my final decision on whether or not to assign EMERGE_DEFAULT_OPTS="--quiet-build=n" in /etc/make.conf until I see what the output looks like when there is a problem with an emerge world. _________________ Clevo W230SS: amd64, VIDEO_CARDS="intel modesetting nvidia".
Compal NBLB2: ~amd64, xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC udev elogind & KDE on both.
Fitzcarraldo's blog |
|
Back to top |
|
|
DaggyStyle Watchman
Joined: 22 Mar 2006 Posts: 5909
|
Posted: Sun Nov 13, 2011 5:51 pm Post subject: |
|
|
is there any way to revert this? _________________ Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21624
|
Posted: Sun Nov 13, 2011 6:17 pm Post subject: |
|
|
DaggyStyle wrote: | is there any way to revert this? | Do you mean that --quiet-build=n does not do what you want? |
|
Back to top |
|
|
DaggyStyle Watchman
Joined: 22 Mar 2006 Posts: 5909
|
Posted: Sun Nov 13, 2011 7:08 pm Post subject: |
|
|
Hu wrote: | DaggyStyle wrote: | is there any way to revert this? | Do you mean that --quiet-build=n does not do what you want? |
I'll try, thanks. _________________ Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
Back to top |
|
|
mv Watchman
Joined: 20 Apr 2005 Posts: 6747
|
Posted: Sun Nov 13, 2011 8:42 pm Post subject: |
|
|
Fitzcarraldo wrote: | but on the other hand it does make the output very compact |
Unfortunately, this is not the case for the net traffic if you use screen or tmux: Displaying the current load average regularly in the title bar needs (slightly) more net resources then the previous way of updating the bar only once per emerge phase. That is the main reason why I will not be using it on remote systems. |
|
Back to top |
|
|
mkyral Apprentice
Joined: 06 May 2007 Posts: 185 Location: Czech Republic
|
Posted: Mon Nov 14, 2011 9:40 am Post subject: |
|
|
I was also surprised. It is not so bad, but would be great to have more information on output - add emerge/installation result and time.
E.g.:
Code: |
>>> Emerging (1 of 9) sys-devel/gcc-config-1.5-r2 <OK> Time 00:03:25
>>> Installing (1 of 9) sys-devel/gcc-config-1.5-r2 <OK> Time 00:00:05
>>> Emerging (2 of 9) dev-libs/apr-1.4.5 <FAIL> Time 00:10:46
...
|
That would be nice. |
|
Back to top |
|
|
padoor Advocate
Joined: 30 Dec 2005 Posts: 4185 Location: india
|
Posted: Mon Nov 14, 2011 12:45 pm Post subject: |
|
|
hows that i dont get times as you?
see the snapshot below
http://ompldr.org/vYjlxZg/snapshot2.png
very unwisely i decided to merge libreoffice which runs for last 7 hours.
the previous packages merged times not shown as the post shown above
what changes you have made?
edit
after reading your post again i find it is in your wish list
well i too hope these features can be added and ETA of the running merge _________________ reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name) |
|
Back to top |
|
|
firephoto Veteran
Joined: 29 Oct 2003 Posts: 1612 Location: +48° 5' 23.40", -119° 48' 30.00"
|
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10589 Location: Somewhere over Atlanta, Georgia
|
Posted: Mon Nov 14, 2011 8:17 pm Post subject: |
|
|
padoor wrote: | well i too hope these features can be added and ETA of the running merge | padoor, do you know about genlop (app-portage/genlop)? It can provide running status and remaining time estimates.
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
mkyral Apprentice
Joined: 06 May 2007 Posts: 185 Location: Czech Republic
|
Posted: Mon Nov 14, 2011 9:04 pm Post subject: |
|
|
John R. Graham wrote: | padoor wrote: | well i too hope these features can be added and ETA of the running merge | padoor, do you know about genlop (app-portage/genlop)? It can provide running status and remaining time estimates.
- John |
I know it, but I don't know why, almost always I tried it, genlop told me, there is no running emerge. But it was not true. |
|
Back to top |
|
|
firephoto Veteran
Joined: 29 Oct 2003 Posts: 1612 Location: +48° 5' 23.40", -119° 48' 30.00"
|
Posted: Mon Nov 14, 2011 9:07 pm Post subject: |
|
|
mkyral wrote: | John R. Graham wrote: | padoor wrote: | well i too hope these features can be added and ETA of the running merge | padoor, do you know about genlop (app-portage/genlop)? It can provide running status and remaining time estimates.
- John |
I know it, but I don't know why, almost always I tried it, genlop told me, there is no running emerge. But it was not true. |
It being a separate command also reduces it's usefulness and like you said the fact that it has to be ran when the emerge is going and it just doesn't wait for something to output is a pita too... and actually as I just check it out now I see it just runs, checks the running emerge and outputs some time then it's done. Not an ongoing progress without some other foo obviously. _________________ #gentoo-kde on freenode |
|
Back to top |
|
|
|