Re: [gentoo-user] emerge output: [ebuild UD ]
On 17/09/14 03:01, Michael Orlitzky wrote: On 09/16/2014 03:14 PM, Alan McKinnon wrote: For some reason xfce-power-manager-1.3.1 does not satisfy what the local install needs but 1.3.0 does. So portage wants to make it so. Version 1.3.1 was removed from the tree, leaving only 1.3.0 to satisfy XFCE_PLUGINS=battery/brightness. That's not it. Portage doesn't work like that. It's because he specifically keyworded 1.3.1 in package.keywords, instead using something smart like: xfce-extra/xfce4-power-manager- To get latest non-live version.
Re: [gentoo-user] emerge output: [ebuild UD ]
On Wed, Sep 17, 2014 at 9:27 AM, Samuli Suominen ssuomi...@gentoo.org wrote: On 17/09/14 03:01, Michael Orlitzky wrote: On 09/16/2014 03:14 PM, Alan McKinnon wrote: For some reason xfce-power-manager-1.3.1 does not satisfy what the local install needs but 1.3.0 does. So portage wants to make it so. Version 1.3.1 was removed from the tree, leaving only 1.3.0 to satisfy XFCE_PLUGINS=battery/brightness. That's not it. Portage doesn't work like that. It's because he specifically keyworded 1.3.1 in package.keywords, instead using something smart like: xfce-extra/xfce4-power-manager- To get latest non-live version. I'm not necessarily after the most recent non-live version of the package. I just didn't want lvm2 pulled in as my current setup has no use for it. What would you recommend doing, leave things as they are, or keyword the stanza you suggested? Thanks.
Re: [gentoo-user] emerge output: [ebuild UD ]
On 17/09/14 16:16, Alexander Kapshuk wrote: On Wed, Sep 17, 2014 at 9:27 AM, Samuli Suominen ssuomi...@gentoo.org wrote: On 17/09/14 03:01, Michael Orlitzky wrote: On 09/16/2014 03:14 PM, Alan McKinnon wrote: For some reason xfce-power-manager-1.3.1 does not satisfy what the local install needs but 1.3.0 does. So portage wants to make it so. Version 1.3.1 was removed from the tree, leaving only 1.3.0 to satisfy XFCE_PLUGINS=battery/brightness. That's not it. Portage doesn't work like that. It's because he specifically keyworded 1.3.1 in package.keywords, instead using something smart like: xfce-extra/xfce4-power-manager- To get latest non-live version. I'm not necessarily after the most recent non-live version of the package. I just didn't want lvm2 pulled in as my current setup has no use for it. What would you recommend doing, leave things as they are, or keyword the stanza you suggested? Thanks. Notice that I said _non_-live and the char in the line. I would use the stanza (as you said) because if 1.4.0 is not stabilized before something like 1.4.1 is added to tree, and 1.4.0 gets deleted, you are facing the same problem all over again. As in, xfce-extra/xfce4-power-manager- with the means I want latest non-live version.
Re: [gentoo-user] emerge output: [ebuild UD ]
On Wed, Sep 17, 2014 at 5:07 PM, Samuli Suominen ssuomi...@gentoo.org wrote: On 17/09/14 16:16, Alexander Kapshuk wrote: On Wed, Sep 17, 2014 at 9:27 AM, Samuli Suominen ssuomi...@gentoo.org wrote: On 17/09/14 03:01, Michael Orlitzky wrote: On 09/16/2014 03:14 PM, Alan McKinnon wrote: For some reason xfce-power-manager-1.3.1 does not satisfy what the local install needs but 1.3.0 does. So portage wants to make it so. Version 1.3.1 was removed from the tree, leaving only 1.3.0 to satisfy XFCE_PLUGINS=battery/brightness. That's not it. Portage doesn't work like that. It's because he specifically keyworded 1.3.1 in package.keywords, instead using something smart like: xfce-extra/xfce4-power-manager- To get latest non-live version. I'm not necessarily after the most recent non-live version of the package. I just didn't want lvm2 pulled in as my current setup has no use for it. What would you recommend doing, leave things as they are, or keyword the stanza you suggested? Thanks. Notice that I said _non_-live and the char in the line. I would use the stanza (as you said) because if 1.4.0 is not stabilized before something like 1.4.1 is added to tree, and 1.4.0 gets deleted, you are facing the same problem all over again. As in, xfce-extra/xfce4-power-manager- with the means I want latest non-live version. Understood. Thanks.
[gentoo-user] emerge output: [ebuild UD ]
Recently, I updated xfce-extra/xfce4-power-manager to version 1.3.1,
which is unstable, in order to prevent lvm2 from being pulled in as a
dependency.
grep xfce-extra/xfce4-power-manager /etc/portage/package.*
/etc/portage/package.accept_keywords:=xfce-extra/xfce4-power-manager-1.3.1 ~x86
As I ran 'emerge -avuND @world' today, I got this output:
These are the packages that would be merged, in order:
Calculating dependencies . . .. . done!
[ebuild N ] sys-apps/sg3_utils-1.37 USE=-static-libs 0 kB
[ebuild N ] sys-apps/rescan-scsi-bus-1.29 0 kB
[ebuild N ] sys-block/thin-provisioning-tools-0.3.2-r1 USE={-test} 0 kB
[ebuild N ] sys-fs/lvm2-2.02.109 USE=readline thin udev (-clvm)
(-cman) -device-mapper-only -lvm1 -lvm2create_initrd (-selinux)
-static -static-libs -systemd 0 kB
[ebuild NS] sys-fs/udisks-1.0.5-r1:0 [2.1.3:2] USE=nls -debug
-remote-access (-selinux) 0 kB
[ebuild UD ] xfce-extra/xfce4-power-manager-1.3.0 [1.3.1]
USE=policykit udisks%* -debug -networkmanager -systemd (-lxpanel%)
XFCE_PLUGINS=brightness -battery 0 kB
Total: 6 packages (1 downgrade, 4 new, 1 in new slot), Size of downloads: 0 kB
emerge trying to downgrade a package, Is that a bug or feature? This
is the first time I've encountered it. I googled it as well, but so
far found nothing relevant.
The list's input would be appreciated.
Re: [gentoo-user] emerge output: [ebuild UD ]
On 09/16/2014 11:51 AM, Alexander Kapshuk wrote: Recently, I updated xfce-extra/xfce4-power-manager to version 1.3.1, which is unstable, in order to prevent lvm2 from being pulled in as a dependency. [ebuild UD ] xfce-extra/xfce4-power-manager-1.3.0 [1.3.1] USE=policykit udisks%* -debug -networkmanager -systemd (-lxpanel%) XFCE_PLUGINS=brightness -battery 0 kB Total: 6 packages (1 downgrade, 4 new, 1 in new slot), Size of downloads: 0 kB emerge trying to downgrade a package, Is that a bug or feature? This is the first time I've encountered it. I googled it as well, but so far found nothing relevant. Version 1.3.1 (which you had installed) used two XFCE_PLUGINS: battery and brightness. The newer 1.4.0 only uses power. Since you still have brightness in your XFCE_PLUGINS, it's pulling in the only version that supports that, the previous 1.3.0. Try replacing brightness with power in your XFCE_PLUGINS.
Re: [gentoo-user] emerge output: [ebuild UD ]
On Tue, Sep 16, 2014 at 7:07 PM, Michael Orlitzky m...@gentoo.org wrote: On 09/16/2014 11:51 AM, Alexander Kapshuk wrote: Recently, I updated xfce-extra/xfce4-power-manager to version 1.3.1, which is unstable, in order to prevent lvm2 from being pulled in as a dependency. [ebuild UD ] xfce-extra/xfce4-power-manager-1.3.0 [1.3.1] USE=policykit udisks%* -debug -networkmanager -systemd (-lxpanel%) XFCE_PLUGINS=brightness -battery 0 kB Total: 6 packages (1 downgrade, 4 new, 1 in new slot), Size of downloads: 0 kB emerge trying to downgrade a package, Is that a bug or feature? This is the first time I've encountered it. I googled it as well, but so far found nothing relevant. Version 1.3.1 (which you had installed) used two XFCE_PLUGINS: battery and brightness. The newer 1.4.0 only uses power. Since you still have brightness in your XFCE_PLUGINS, it's pulling in the only version that supports that, the previous 1.3.0. Try replacing brightness with power in your XFCE_PLUGINS. Replacing brightness with power in XFCE_PLUGINS, followed by running 'emerge -avuND @world', still tried to downgrade the package in question. I then ran 'emerge -avuND 'xfce-extra/xfce4-power-manager-1.3.1' which suggested adding '=xfce-extra/xfce4-power-manager-1.4.0 ~x86' to /etc/portage/package.accept_keywords. I did that, followed by running 'emerge -avuND @world', which pulled in xfce-extra/xfce4-power-manager-1.4.0. Thanks.
Re: [gentoo-user] emerge output: [ebuild UD ]
On 16/09/2014 17:51, Alexander Kapshuk wrote:
Recently, I updated xfce-extra/xfce4-power-manager to version 1.3.1,
which is unstable, in order to prevent lvm2 from being pulled in as a
dependency.
grep xfce-extra/xfce4-power-manager /etc/portage/package.*
/etc/portage/package.accept_keywords:=xfce-extra/xfce4-power-manager-1.3.1
~x86
As I ran 'emerge -avuND @world' today, I got this output:
These are the packages that would be merged, in order:
Calculating dependencies . . .. . done!
[ebuild N ] sys-apps/sg3_utils-1.37 USE=-static-libs 0 kB
[ebuild N ] sys-apps/rescan-scsi-bus-1.29 0 kB
[ebuild N ] sys-block/thin-provisioning-tools-0.3.2-r1 USE={-test} 0
kB
[ebuild N ] sys-fs/lvm2-2.02.109 USE=readline thin udev (-clvm)
(-cman) -device-mapper-only -lvm1 -lvm2create_initrd (-selinux)
-static -static-libs -systemd 0 kB
[ebuild NS] sys-fs/udisks-1.0.5-r1:0 [2.1.3:2] USE=nls -debug
-remote-access (-selinux) 0 kB
[ebuild UD ] xfce-extra/xfce4-power-manager-1.3.0 [1.3.1]
USE=policykit udisks%* -debug -networkmanager -systemd (-lxpanel%)
XFCE_PLUGINS=brightness -battery 0 kB
Total: 6 packages (1 downgrade, 4 new, 1 in new slot), Size of downloads: 0 kB
emerge trying to downgrade a package, Is that a bug or feature? This
is the first time I've encountered it. I googled it as well, but so
far found nothing relevant.
portage is doing what the ebuilds and make.conf tell it to do.
For some reason xfce-power-manager-1.3.1 does not satisfy what the local
install needs but 1.3.0 does. So portage wants to make it so.
Downgrades are not common, but neither are they unusual. It's not a
feature either, it's a necessaity that portage be able to do this.
The list's input would be appreciated.
--
Alan McKinnon
alan.mckin...@gmail.com
Re: [gentoo-user] emerge output: [ebuild UD ]
On Tue, Sep 16, 2014 at 10:14 PM, Alan McKinnon alan.mckin...@gmail.com wrote:
On 16/09/2014 17:51, Alexander Kapshuk wrote:
Recently, I updated xfce-extra/xfce4-power-manager to version 1.3.1,
which is unstable, in order to prevent lvm2 from being pulled in as a
dependency.
grep xfce-extra/xfce4-power-manager /etc/portage/package.*
/etc/portage/package.accept_keywords:=xfce-extra/xfce4-power-manager-1.3.1
~x86
As I ran 'emerge -avuND @world' today, I got this output:
These are the packages that would be merged, in order:
Calculating dependencies . . .. . done!
[ebuild N ] sys-apps/sg3_utils-1.37 USE=-static-libs 0 kB
[ebuild N ] sys-apps/rescan-scsi-bus-1.29 0 kB
[ebuild N ] sys-block/thin-provisioning-tools-0.3.2-r1 USE={-test} 0
kB
[ebuild N ] sys-fs/lvm2-2.02.109 USE=readline thin udev (-clvm)
(-cman) -device-mapper-only -lvm1 -lvm2create_initrd (-selinux)
-static -static-libs -systemd 0 kB
[ebuild NS] sys-fs/udisks-1.0.5-r1:0 [2.1.3:2] USE=nls -debug
-remote-access (-selinux) 0 kB
[ebuild UD ] xfce-extra/xfce4-power-manager-1.3.0 [1.3.1]
USE=policykit udisks%* -debug -networkmanager -systemd (-lxpanel%)
XFCE_PLUGINS=brightness -battery 0 kB
Total: 6 packages (1 downgrade, 4 new, 1 in new slot), Size of downloads: 0
kB
emerge trying to downgrade a package, Is that a bug or feature? This
is the first time I've encountered it. I googled it as well, but so
far found nothing relevant.
portage is doing what the ebuilds and make.conf tell it to do.
For some reason xfce-power-manager-1.3.1 does not satisfy what the local
install needs but 1.3.0 does. So portage wants to make it so.
Downgrades are not common, but neither are they unusual. It's not a
feature either, it's a necessaity that portage be able to do this.
The list's input would be appreciated.
--
Alan McKinnon
alan.mckin...@gmail.com
Thanks for the explanation. I overlooked the fact that XFCE_PLUGINS is
a user-defined variable and didn't think to look for answers in the
xfce-extra/xfce4-power-manager ebuild at the time.
The responses I got are certainly appreciated.
Re: [gentoo-user] emerge output: [ebuild UD ]
On 09/16/2014 03:14 PM, Alan McKinnon wrote: For some reason xfce-power-manager-1.3.1 does not satisfy what the local install needs but 1.3.0 does. So portage wants to make it so. Version 1.3.1 was removed from the tree, leaving only 1.3.0 to satisfy XFCE_PLUGINS=battery/brightness.
Re: [gentoo-user] emerge output: [ebuild UD ]
On 09/16/2014 12:39 PM, Alexander Kapshuk wrote: Replacing brightness with power in XFCE_PLUGINS, followed by running 'emerge -avuND @world', still tried to downgrade the package in question. I then ran 'emerge -avuND 'xfce-extra/xfce4-power-manager-1.3.1' which suggested adding '=xfce-extra/xfce4-power-manager-1.4.0 ~x86' to /etc/portage/package.accept_keywords. I did that, followed by running 'emerge -avuND @world', which pulled in xfce-extra/xfce4-power-manager-1.4.0. Did you have 1.3.1 keyworded? Because it was ~x86 also when it was removed.
Re: [gentoo-user] emerge output: [ebuild UD ]
On Wed, Sep 17, 2014 at 3:02 AM, Michael Orlitzky m...@gentoo.org wrote: On 09/16/2014 12:39 PM, Alexander Kapshuk wrote: Replacing brightness with power in XFCE_PLUGINS, followed by running 'emerge -avuND @world', still tried to downgrade the package in question. I then ran 'emerge -avuND 'xfce-extra/xfce4-power-manager-1.3.1' which suggested adding '=xfce-extra/xfce4-power-manager-1.4.0 ~x86' to /etc/portage/package.accept_keywords. I did that, followed by running 'emerge -avuND @world', which pulled in xfce-extra/xfce4-power-manager-1.4.0. Did you have 1.3.1 keyworded? Because it was ~x86 also when it was removed. Yes, I did have this stanza, '=xfce-extra/xfce4-power-manager-1.3.1 ~x86', in my /etc/portage/package.accept_keywords.
[gentoo-user] emerge output, screenshots and the list Was: fcitx crash, libpng cairo?
On 13 April 2013, at 06:14, Jackie wrote: ... Tried to downgrade libpng cairo today but no luck… I've here got the snapshot of the infomation got after masking libpng-1.6.1 cairo-1.12.14.Hell No!snapshot7_libpng_slot.png I'm looking at your problem now to try and help you with it, but you have attached an image screenshot of your emerge output (in this case the output of `emerge libpng cairo -pv`). In future please submit emerge output as plain text, not as an image. To complete my first paragraph just now, for example, I had to retype `emerge libpng cairo -pv`. As I did so I had to check between windows, looking left and right, to make sure I spelled it right. And I still cannot be certain of that! It would have been much easier for me if I could have just copied and pasted the text `emerge libpng cairo -pv`, instead of retyping it. In investigating your problem I will want to make lookups on the Gentoo packages database, and this is most easily done by googling (which may turn up other relevant results, also). When you supply your output as an image it makes this more difficult, too, because once again it prevents me from copying and pasting. You should be able to select and copy and paste from your terminal program - kTerm or iTerm or gnome-terminal or whatever. Otherwise you can use the tmux program and capture the buffer into a text file [1], which you can then copy and paste into your email using a GUI text editor. If you need help with this, please just tell us. Putting text in an image makes it harder to help you. Stroller. [1] http://unix.stackexchange.com/a/26568
Re: [gentoo-user] emerge output confusion regarding upgradeable packages
On Monday 12 May 2008, PaulNM wrote: The fetch restriction is realplayer, and expected. The three upgrades are a complete surprise. I can't figure out why they're there. [ebuild U ] dev-python/dnspython-1.6.0 [1.5.0] USE=-examples 98 kB [ebuild U ] x11-apps/xcursorgen-1.0.2 [1.0.1] 88 kB [ebuild U ] dev-lang/yasm-0.6.2 [0.6.0] USE=-nls 1,230 kB emerge -pv --update --deep --newuse world doesn't want to do anything. emerge -p --depclean doesn't want to remove anything. Adding t (emerge -pvet world) to the first command yields this (related) info: [nomerge ] net-p2p/bittorrent-5.0.9-r1 USE=-gtk [ebuild U ] dev-python/dnspython-1.6.0 [1.5.0] USE=-examples 98 kB [nomerge ] x11-themes/xcursor-themes-1.0.1 [ebuild U ] x11-apps/xcursorgen-1.0.2 [1.0.1] 88 kB [ebuild R ] x11-libs/libXcursor-1.1.9 USE=-debug 230 kB [ebuild R ] x11-libs/libXfixes-4.0.3 USE=-debug 210 kB [ebuild R ] x11-proto/fixesproto-4.0 38 kB [nomerge ] media-video/mplayer-1.0_rc2_p25993 USE=X a52 aac alsa cdparanoia directfb dts dvd encode fbcon ftp ggi gif gtk iconv ipv6 jpeg lzo mmx mmxext mp3 opengl oss png pulseaudio quicktime rar real sdl sse svga truetype unicode v4l v4l2 vorbis win32codecs xanim xv xvid xvmc -3dnow -3dnowext -aalib (-altivec) -amrnb -amrwb -arts -bidi -bindist -bl -cddb -cdio -cpudetection -custom-cflags -debug -dga -doc -dv -dvb -enca -esd -jack -joystick -ladspa -libcaca -lirc -live -livecd -mad -md5sum -mp2 -musepack -nas -nemesi -openal -pnm -radio -rtc -samba -speex -srt -sse2 -ssse3 -teletext -tga -theora -tivo -vidix -x264 -xinerama -xscreensaver -zoran VIDEO_CARDS=vesa -mga -s3virge -tdfx [nomerge ] media-libs/xvid-1.1.3 USE=(-altivec) -examples [ebuild U ] dev-lang/yasm-0.6.2 [0.6.0] USE=-nls 1,230 kB This is expected behaviour. The three packages you mention are not in world and thus don't form part of the initial search. Even though you are using -uN, nothing in world *requires* specifically those updated/latest versions, so they never make it into the dependency tree as a suitable version is already installed. When you add -t though, you clear out the dependency tree, fooling portage into thinking the packages are not installed. dnspython, xcursorgen and yasm are needed and not installed so portage does the normal thing of selecting the latest versions that match your rules in /etc/portage -- Alan McKinnon alan dot mckinnon at gmail dot com -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] emerge output confusion regarding upgradeable packages
Alan McKinnon wrote: This is expected behaviour. The three packages you mention are not in world and thus don't form part of the initial search. Even though you are using -uN, nothing in world *requires* specifically those updated/latest versions, so they never make it into the dependency tree as a suitable version is already installed. I think the end of my message was a little confusing, if you look earlier, you'll see I'm using --deep. (emerge -pv --update --deep --newuse world) When you add -t though, you clear out the dependency tree, fooling portage into thinking the packages are not installed. dnspython, xcursorgen and yasm are needed and not installed so portage does the normal thing of selecting the latest versions that match your rules in /etc/portage I think you mean -e (--emptytree) here. Using -t (--tree) just adds a whole bunch of stuff to help you see what is pulling in particular packages. I seem to recall at one time using -e actually showed all packages as N (new), but now it seems to indicate their current status (R for replace). According to the emerge man page, -u (--update) will update the specified set and its direct dependencies. -d (--deep) will update the specified set and its entire dependency tree (dependencies of its dependencies, and so on). My final comment was simply noting that two of the three were direct dependencies and should show up with just -u. In any case, they should all show up with -d. PaulNM -- gentoo-user@lists.gentoo.org mailing list
[gentoo-user] emerge output confusion regarding upgradeable packages
Hey Folks, this one has me confused I use http-replicator, but that's not directly related to my problem, it's just how I discovered it. I occasionally prune the http-replicator cache by emptying every system's distfiles directory, then run emerge -fe world to download only the current distfiles from my http-replicator system. Afterwards I delete the files from the replicator cache and copy the distfiles over from the systems to the replicator cache directory. I usually do a pretend run first (add pv to the emerge command) to see how many packages I'm dealing with. On this one system, I see odd results. Robotech paul # emerge -pve world These are the packages ... (Huge snip here!) Total: 1017 packages (3 upgrades, 1014 reinstalls), Size of downloads: 1,780,810 kB Fetch Restriction: 1 package (1 unsatisfied) Portage tree and overlays: [0] /usr/portage [1] /usr/local/portage [2] /usr/portage/local/layman/sectools [3] /usr/portage/local/layman/berkano The fetch restriction is realplayer, and expected. The three upgrades are a complete surprise. I can't figure out why they're there. [ebuild U ] dev-python/dnspython-1.6.0 [1.5.0] USE=-examples 98 kB [ebuild U ] x11-apps/xcursorgen-1.0.2 [1.0.1] 88 kB [ebuild U ] dev-lang/yasm-0.6.2 [0.6.0] USE=-nls 1,230 kB emerge -pv --update --deep --newuse world doesn't want to do anything. emerge -p --depclean doesn't want to remove anything. Adding t (emerge -pvet world) to the first command yields this (related) info: [nomerge ] net-p2p/bittorrent-5.0.9-r1 USE=-gtk [ebuild U ] dev-python/dnspython-1.6.0 [1.5.0] USE=-examples 98 kB [nomerge ] x11-themes/xcursor-themes-1.0.1 [ebuild U ] x11-apps/xcursorgen-1.0.2 [1.0.1] 88 kB [ebuild R ] x11-libs/libXcursor-1.1.9 USE=-debug 230 kB [ebuild R ]x11-libs/libXfixes-4.0.3 USE=-debug 210 kB [ebuild R ] x11-proto/fixesproto-4.0 38 kB [nomerge ] media-video/mplayer-1.0_rc2_p25993 USE=X a52 aac alsa cdparanoia directfb dts dvd encode fbcon ftp ggi gif gtk iconv ipv6 jpeg lzo mmx mmxext mp3 opengl oss png pulseaudio quicktime rar real sdl sse svga truetype unicode v4l v4l2 vorbis win32codecs xanim xv xvid xvmc -3dnow -3dnowext -aalib (-altivec) -amrnb -amrwb -arts -bidi -bindist -bl -cddb -cdio -cpudetection -custom-cflags -debug -dga -doc -dv -dvb -enca -esd -jack -joystick -ladspa -libcaca -lirc -live -livecd -mad -md5sum -mp2 -musepack -nas -nemesi -openal -pnm -radio -rtc -samba -speex -srt -sse2 -ssse3 -teletext -tga -theora -tivo -vidix -x264 -xinerama -xscreensaver -zoran VIDEO_CARDS=vesa -mga -s3virge -tdfx [nomerge ] media-libs/xvid-1.1.3 USE=(-altivec) -examples [ebuild U ] dev-lang/yasm-0.6.2 [0.6.0] USE=-nls 1,230 kB The above shows the only instances of dnspython/xcursorgen/yasm in the entire output (checked with grep). The upgraders (dnspython, xcursorgen, yasm) are not in world, nor is xvid. The three packages (bittorrent, xcursor-themes, mplayer) at the top of the trees are in world. Two of the three are direct dependencies of packages in world, so they should show as upgradeable even without --deep. What am I missing/doing wrong? PaulNM -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] emerge output
On Fri, 26 Aug 2005 01:27:11 +0100, Tony Davison wrote: There is a little gadget called 'enotice that I use but I';m b*d if I can remember where I got it from, perhaps the above URL. It's in the Gentoo Script Repository at http://gentooexperimental.org/script/repo/list An alternative is to set PORT_LOGDIR in /etc/make.conf, and create whatever directory you set it to. You'll find two log files in here for each emerge, one contains all the compiler output, the other has the info and warning messages. There was a script to mail these to you, but I can't find it now. -- Neil Bothwick Barnum was wrongit's more like every 30 seconds! pgpEtCPVWah6E.pgp Description: PGP signature
Re: [gentoo-user] emerge output
On 2005-08-26 01:48:36 +0200 (Fri, Aug), Holly Bostick wrote: Idea #3: there is a way (and possibly more than one) to tail out the einfo messages, either to a file, or to the console, but unfortunately I don't remember what they are atm Oh, wait, they're listed on the Wiki: http://gentoo-wiki.com/TIP_Portage_utilities_not_in_portage I think what you might want is portlog-info, which is in the Informational Utilities section. ...or something dumber^H^H^H^H^Hsimpler: # --- #!/bin/bash COUNT=60 cd /var/log/portage || exit -1 for file in $( ls -1rt | tail -n $COUNT) do if grep $'\e' $file | grep -q -v -e Applying [^ ]*.patch -e $'\e'\[32;01mok$'\e'\[34;01m then tput bold echo ' ' ls -l $file echo ' ' tput sgr0 grep $'\e' $file | grep -v Applying [^ ]*.patch fi done # --- The log files are created when you set the PORT_LOGDIR in /etc/make.conf (yeah, you replace then that cd /var/log/portage with your - possibly different - location, or do something like eval $(grep ^PORT_LOGDIR= /etc/make.conf)) . HTH -- No virus found in this outgoing message. Checked by 'grep -i virus $MESSAGE' Trust me. pgp1eTIxDSzsw.pgp Description: PGP signature
RESOLVED: [gentoo-user] emerge output
Neil, Mariusz~ Thanks for the input. Just setting up PORT_LOGDIR has gone a long way to providing exactly what I'm looking for. It's a shame that this isn't setup by default, but I can think of a few reasons why it isn't. John D -Original Message- From: Mariusz Pêkala [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 4:33 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] emerge output On 2005-08-26 01:48:36 +0200 (Fri, Aug), Holly Bostick wrote: Idea #3: there is a way (and possibly more than one) to tail out the einfo messages, either to a file, or to the console, but unfortunately I don't remember what they are atm Oh, wait, they're listed on the Wiki: http://gentoo-wiki.com/TIP_Portage_utilities_not_in_portage I think what you might want is portlog-info, which is in the Informational Utilities section. ...or something dumber^H^H^H^H^Hsimpler: # --- #!/bin/bash COUNT=60 cd /var/log/portage || exit -1 for file in $( ls -1rt | tail -n $COUNT) do if grep $'\e' $file | grep -q -v -e Applying [^ ]*.patch -e $'\e'\[32;01mok$'\e'\[34;01m then tput bold echo ' ' ls -l $file echo ' ' tput sgr0 grep $'\e' $file | grep -v Applying [^ ]*.patch fi done # --- The log files are created when you set the PORT_LOGDIR in /etc/make.conf (yeah, you replace then that cd /var/log/portage with your - possibly different - location, or do something like eval $(grep ^PORT_LOGDIR= /etc/make.conf)) . HTH -- No virus found in this outgoing message. Checked by 'grep -i virus $MESSAGE' Trust me. -- gentoo-user@gentoo.org mailing list
[gentoo-user] emerge output
I just did an emerge uDv world during the course of the 22 packages (a lot considering I just loaded this last night), I got some messages saying please make sure you run (I couldnt read it all since it went by so fast) I got a couple of these before it was over. Is there a way to view that output after the fact? I didnt see it in either dmesg or any of the /var/log files Thanks for the input. Regards, John Dangler GenoFit 800-505-4078 (Corporate) 386-767-3730 (Direct) 866-273-0408 (Fax) www.genofit.com [EMAIL PROTECTED]
Re: [gentoo-user] emerge output
John Dangler schreef: I just did an emerge –uDv world… during the course of the 22 packages (a lot considering I just loaded this last night), I got some messages saying “please make sure you run … (I couldn’t read it all since it went by so fast)… I got a couple of these before it was over. Is there a way to view that output after the fact? I didn’t see it in either dmesg or any of the /var/log files… Thanks for the input. Idea #1: if you know the name of the file or files that had an einfo message (if you don't know the names, try looking at the end /var/log/emerge.log to see the packages most recently emerged), just open the ebuild in a text editor and read it at your leisure. Idea #2: In whatever console you use, change the size of the scrollback buffer to something that seems ridiculously high (my buffer is 3 lines). For most emerges -- even in groups of 20 or more-- this should be enough to allow you to scroll back and read any einfo messages that you may have noticed. This won't so much work for emerges that are themselves more than 3 lines (for instance, if I emerge gcc and then glibc, I won't be able to scroll back and see any messages I missed in the gcc emerge once the glibc emerge is an hour or so in, but usually it's good enough). Idea #3: there is a way (and possibly more than one) to tail out the einfo messages, either to a file, or to the console, but unfortunately I don't remember what they are atm Oh, wait, they're listed on the Wiki: http://gentoo-wiki.com/TIP_Portage_utilities_not_in_portage I think what you might want is portlog-info, which is in the Informational Utilities section. HTH, Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge output
On Friday 26 August 2005 00:48, Holly Bostick wrote: John Dangler schreef: I just did an emerge –uDv world… during the course of the 22 packages (a lot considering I just loaded this last night), I got some messages saying “please make sure you run … (I couldn’t read it all since it went by so fast)… I got a couple of these before it was over. Is there a way to view that output after the fact? I didn’t see it in either dmesg or any of the /var/log files… Thanks for the input. Idea #1: if you know the name of the file or files that had an einfo message (if you don't know the names, try looking at the end /var/log/emerge.log to see the packages most recently emerged), just open the ebuild in a text editor and read it at your leisure. Idea #2: In whatever console you use, change the size of the scrollback buffer to something that seems ridiculously high (my buffer is 3 lines). For most emerges -- even in groups of 20 or more-- this should be enough to allow you to scroll back and read any einfo messages that you may have noticed. This won't so much work for emerges that are themselves more than 3 lines (for instance, if I emerge gcc and then glibc, I won't be able to scroll back and see any messages I missed in the gcc emerge once the glibc emerge is an hour or so in, but usually it's good enough). Idea #3: there is a way (and possibly more than one) to tail out the einfo messages, either to a file, or to the console, but unfortunately I don't remember what they are atm Oh, wait, they're listed on the Wiki: http://gentoo-wiki.com/TIP_Portage_utilities_not_in_portage I think what you might want is portlog-info, which is in the Informational Utilities section. There is a little gadget called 'enotice that I use but I';m b*d if I can remember where I got it from, perhaps the above URL. Just had a look in /usr/sbin/enotice its python script by a guy called Eldad Zack [EMAIL PROTECTED] HTH -- Tony Davison [EMAIL PROTECTED] Its late, I'm tired and out of ciggies, bed time. -- gentoo-user@gentoo.org mailing list
