Yesterday, during my system update,
I have got the following warning:
WARNING: One or more updates have been skipped due to a dependency conflict:
media-libs/openjpeg:2
(media-libs/openjpeg-2.1.0::gentoo, ebuild scheduled for merge) conflicts
with
media-libs/openjpeg-2.1:2
On Wednesday 05 November 2014 23:21:46 Volker Armin Hemmann wrote:
have you tried restarting plasma? Or switched screens?
I don't know how to restart plasma, other than logging out and in again. I
have six virtual desktops most of the time, and they're all equally blank.
i have occasionally
On 11/08/2014 04:43 PM, Gevisz wrote:
Yesterday, during my system update,
I have got the following warning:
WARNING: One or more updates have been skipped due to a dependency conflict:
media-libs/openjpeg:2
(media-libs/openjpeg-2.1.0::gentoo, ebuild scheduled for merge) conflicts
Op zaterdag 8 november 2014 09:52:32 schreef Peter Humphrey:
On Wednesday 05 November 2014 23:21:46 Volker Armin Hemmann wrote:
have you tried restarting plasma? Or switched screens?
I don't know how to restart plasma, other than logging out and in again. I
have six virtual desktops most
is located at
'/var/log/portage/media-gfx:sam2p-0.49.2:20141108-123213.log'.
* For convenience, a symlink to the build log is located at
'/var/tmp/portage/media-gfx/sam2p-0.49.2/temp/build.log'.
* The ebuild environment file is located
'=media-gfx/sam2p-0.49.2::gentoo'`.
* The complete build log is located at
'/var/log/portage/media-gfx:sam2p-0.49.2:20141108-123213.log'.
* For convenience, a symlink to the build log is located at
'/var/tmp/portage
::gentoo'`,
* the complete build log and the output of `emerge -pqv
'=media-gfx/sam2p-0.49.2::gentoo'`.
* The complete build log is located at
'/var/log/portage/media-gfx:sam2p-0.49.2:20141108-123213.log
/log/portage/media-gfx:sam2p-0.49.2:20141108-123213.log'.
* For convenience, a symlink to the build log is located
at
'/var/tmp/portage/media-gfx/sam2p-0.49.2/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp
::gentoo'`.
* The complete build log is located at
'/var/log/portage/media-gfx:sam2p-0.49.2:20141108-123213.log'.
* For convenience, a symlink to the build log is
located at
'/var/tmp/portage/media-gfx/sam2p-0.49.2/temp/build.log
meino.cramer at gmx.de writes:
Gentoo, I need a little help in choosing the correct stage3
image/archive (currently the board is on the way to me...).
The processor of the board is a AT91SAM9G25 (softloater, no FPU or
similiar) and the available stage3 images/archives are (as of my
::gentoo'`,
* the complete build log and the output of `emerge -pqv
'=media-gfx/sam2p-0.49.2::gentoo'`.
* The complete build log is located at
'/var/log/portage/media-gfx:sam2p-0.49.2:20141108-123213.log
-gfx:sam2p-0.49.2:20141108-123213.log'.
* For convenience, a symlink to the build log is
located at
'/var/tmp/portage/media-gfx/sam2p-0.49.2/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/media
at
'/var/log/portage/media-gfx:sam2p-0.49.2:20141108-123213.log'.
* For convenience, a symlink to the build log is
located at
'/var/tmp/portage/media-gfx/sam2p-0.49.2/temp/build.log'.
* The ebuild environment file is located
-0.49.2::gentoo'`.
* The complete build log is located at
'/var/log/portage/media-gfx:sam2p-0.49.2:20141108-123213.log'.
* For convenience, a symlink to the build log is
located at
'/var/tmp/portage/media-gfx/sam2p-0.49.2/temp
and the output of `emerge
-pqv
'=media-gfx/sam2p-0.49.2::gentoo'`.
* The complete build log is located at
'/var/log/portage/media-gfx:sam2p-0.49.2:20141108-123213.log'.
* For convenience, a symlink to the build log
'`,
* the complete build log and the output of `emerge
-pqv
'=media-gfx/sam2p-0.49.2::gentoo'`.
* The complete build log is located at
'/var/log/portage/media-gfx:sam2p-0.49.2:20141108-123213.log'.
* For convenience, a symlink
'`.
* The complete build log is located at
'/var/log/portage/media-gfx:sam2p-0.49.2:20141108-123213.log'.
* For convenience, a symlink to the build log is
located at
'/var/tmp/portage/media-gfx/sam2p-0.49.2/temp/build.log
On 07/11/14 19:46, James wrote:
Ok
so I'm still on 4.7.3; but if I set 4.8.3
as the default, should I rebuild @system ?
# gcc-config -l
[1] x86_64-pc-linux-gnu-4.7.3 *
[2] x86_64-pc-linux-gnu-4.8.3
I saw the news item about 4.8.3-SSP, which I think is a good idea, but
how deeply, if at
On Sat, 08 Nov 2014 18:36:59 +0800 Lin Xiao xiaolini...@gmail.com wrote:
On 11/08/2014 04:43 PM, Gevisz wrote:
Yesterday, during my system update,
I have got the following warning:
WARNING: One or more updates have been skipped due to a dependency
conflict:
Am 07.11.2014 um 19:19 schrieb Mark Pariente:
Going to 4.9 though is another thing. Apparently they broke the ABI for
the standard C++ library, so once you start compiling C++ stuff with 4.9
you better go all in (I did @system @world with 4.9 and had very few
things that failed to compile[1],
Nikos Chantziaras realnc at gmail.com writes:
I saw the news item about 4.8.3-SSP, which I think is a good idea, but
how deeply, if at all, do I need to rebuild packages ?
You don't need to rebuild, although there are known problems with having
both 4.7 and 4.8 installed, and having 4.7
snip from stefan
I give that a try ... as I set up a fresh new btrfs-subvolume to do a
fresh new build based on my at world only yesterday I will see if I can do
it with gcc 4.9 while I am at it.
Let's see if things work out and if it gets any better.
end/snip
Hello Stefan,
Well. OK. I'm
Am 08.11.2014 um 21:27 schrieb James:
If you would be so cool as to post your subvolume setup;
I'd be very grateful:
[..]
I guess what really has me confused is to set up a traditional
fstab, uuid, efi, with grub2. I'm just dense I guess
because the aforementioned doc, I think derived
Am 08.11.2014 um 22:07 schrieb Stefan G. Weichinger:
Number Start (sector)End (sector) Size Code Name
12048 194559 94.0 MiBEF00 ESI
2 194560 480585727 229.1 GiB 8300 Linux filesystem
3 480585728 488396799 3.7
Stefan G. Weichinger lists at xunil.at writes:
Does this help in any way?
Yes very much so. I use gmane to read and post,
So I have to write more than I quote and trim
the replied verbiage down.
Did you create your pool already?
No. Following the gentoo wiki:
Am 07.11.2014 um 19:19 schrieb Mark Pariente:
Going to 4.9 though is another thing. Apparently they broke the ABI
for the standard C++ library, so once you start compiling C++ stuff
with 4.9 you better go all in (I did @system @world with 4.9 and had
very few things that failed to
On 8 November 2014 22:17:44 GMT+00:00, James wirel...@tampabay.rr.com wrote:
Yes very much so. I use gmane to read and post,
So I have to write more than I quote and trim
the replied verbiage down.
node
That's not just a gmane rule, it's good netiquette.
--
Sent from my Android
Neil Bothwick neil at digimed.co.uk writes:
Yes very much so. I use gmane to read and post,
So I have to write more than I quote and trim
the replied verbiage down.
That's not just a gmane rule, it's good netiquette.
Usually yes. But in this case, I would like to eventually
respond
Has anyone else seen this or is able to offer advice ?
This has happened 4 times during 2014 when Xscreensaver was running.
I return to my desk find a blank X-ish screen when I hit Enter,
I get a raw terminal announcing the crash ; 'startx' gets things going again.
The screensaver running at
29 matches
Mail list logo
