On Wednesday 08 Jan 2014 14:37:00 Stefan G. Weichinger wrote:
> Am 08.01.2014 14:36, schrieb Mick:
> >> I don't know if I am stating the obvious but just in case: Have
> >> a look here and set up your --python2 to reflect what you have
> >> installed. You may need to go at it in steps between ver
On Thu, 09 Jan 2014 03:06:05 +0100
Tamer Higazi wrote:
> tried to merge libreoffice-bin, and the dependency failed to compile.
> Any ideas what might be the problem or how to solve that?!
>
> http://pastebin.com/raw.php?i=dwMcutSq
Can you attach that to https://bugs.gentoo.org/show_bug.cgi?id=4
tried to merge libreoffice-bin, and the dependency failed to compile.
Any ideas what might be the problem or how to solve that?!
http://pastebin.com/raw.php?i=dwMcutSq
Tamer
Hello,
i has found the problem. That was the kernel with gresecurity patch. I has
read that can give trouble and now i change kernel and dbus is installed.
Thanks for help & Nice Day
Silvio
Am 08.01.2014 19:47, schrieb Grant Edwards:
> On 2014-01-08, Stefan G. Weichinger wrote:
>
>> Looking forward to some clever suggestions ;-)
>
> Well, I'd start by running memtest86 overnight just to eliminate the
> possibility of marginal memory. But, if memory serves, this is a
> remote serve
> http://mywiki.wooledge.org/BashFAQ/088
The advice here to use awk to "compress" log files seems a bit dated.
Bash now allows you to set in .bashrc:
export HISTCONTROL=erasedups
I don't know that there's an "ultimate answer" to history management.
Personally, for years I have had my prompt
Bruce Hill wrote:
> On Wed, Jan 08, 2014 at 07:10:10AM -0500, Tanstaafl wrote:
> > Hi all,
> >
> > I routinely am logged into a server with multiple consoles (I log in
> > with one (the same) regular user, then su - to root).
> >
> > This morning I tried to grep roots .bash_history for a comma
On 01/05/2014 01:41 PM, Alan McKinnon wrote:
> I have Gentoo on a first gen Acer Aspire One. The teeny keyboard doesn't
> have a numpad, it's simulated by using the right-hand bunch of keys and
> you engage it with Fn-F11
>
> It's recently started booting up with the numpad on which is annoying at
On 2014-01-08, Stefan G. Weichinger wrote:
> Looking forward to some clever suggestions ;-)
Well, I'd start by running memtest86 overnight just to eliminate the
possibility of marginal memory. But, if memory serves, this is a
remote server at a customer site -- so that may not be a viable
optio
On Sun, 29 Dec 2013 19:23:41 +0800 Oli wrote:
> Had a similar issue not too long ago. It was down to a block error
> on the hard drive. After a full check and repair, it worked well.
On host system could install dbus without problem.
siefke ~ $ su -c "emerge -pqv =sys-apps/dbus-1.6.12::gen
On 2014-01-08 11:54 AM, Tanstaafl wrote:
I just updated glibc to 2.1.17, and got the following error at the very
end of the emerge:
/usr/bin/python2.7: relocation error: /lib64/libresolv.so.2: symbol
__sendmmsg, version GLIBC_PRIVATE not defined in file libc.so.6 with
lin
On 2014-01-08 12:35 AM, J. Roeleveld wrote:
Tanstaafl wrote:
Current permissions are:
Virtual domain dirs:
/var/vmail/example1.com 777
/var/vmail/example2.com 777
Do yourself a favour and reconsider the above 777 really carefully.
I have never needed to set anything wide open like that.
Am 08.01.2014 17:41, schrieb Stefan G. Weichinger:
> trying "emerge -B glibc" for now ... step by step.
emerge -B : success
emerge -K: same failure
The unpacking of glibc seems to somehow break python while emerge still
runs ... at least that is my impression.
Manually unpacking the 2.17-tarba
I just updated glibc to 2.1.17, and got the following error at the very
end of the emerge:
/usr/bin/python2.7: relocation error: /lib64/libresolv.so.2: symbol __sendmmsg,
version GLIBC_PRIVATE not defined in file libc.so.6 with lin
k time
Am 08.01.2014 17:20, schrieb Neil Bothwick:
> On Wed, 08 Jan 2014 12:54:09 +0100, Stefan G. Weichinger wrote:
>
>> # python-updater /usr/sbin/python-updater: Zeile 146: 28887
>> Speicherzugriffsfehler /usr/bin/portageq has_version / "${1}"
>> /usr/sbin/python-updater: Zeile 146: 2
>> Speicher
On Wed, 08 Jan 2014 12:54:09 +0100, Stefan G. Weichinger wrote:
> # python-updater
> /usr/sbin/python-updater: Zeile 146: 28887 Speicherzugriffsfehler
> /usr/bin/portageq has_version / "${1}"
> /usr/sbin/python-updater: Zeile 146: 2 Speicherzugriffsfehler
> /usr/bin/portageq has_version / "${1
On 08/01/2014 14:10, Tanstaafl wrote:
> Hi all,
>
> I routinely am logged into a server with multiple consoles (I log in
> with one (the same) regular user, then su - to root).
>
> This morning I tried to grep roots .bash_history for a command I ran
> some time ago, and it wasn't there. I know I
Am 08.01.2014 14:36, schrieb Mick:
>> I don't know if I am stating the obvious but just in case: Have
>> a look here and set up your --python2 to reflect what you have
>> installed. You may need to go at it in steps between versions.
>
> Oops! Pulled the trigger too fast - sorry:
>
> http://w
On Wed, Jan 08, 2014 at 07:10:10AM -0500, Tanstaafl wrote:
> Hi all,
>
> I routinely am logged into a server with multiple consoles (I log in
> with one (the same) regular user, then su - to root).
>
> This morning I tried to grep roots .bash_history for a command I ran
> some time ago, and it
On Wednesday 08 Jan 2014 13:33:20 Mick wrote:
> On Wednesday 08 Jan 2014 12:10:41 Stefan G. Weichinger wrote:
> > Am 08.01.2014 13:06, schrieb Mick:
> > > On Wednesday 08 Jan 2014 11:58:01 Stefan G. Weichinger wrote:
> > >> Thanks for the pointer.
> > >>
> > >> Unpacked /usr/portage/distfiles/port
On Wednesday 08 Jan 2014 12:10:41 Stefan G. Weichinger wrote:
> Am 08.01.2014 13:06, schrieb Mick:
> > On Wednesday 08 Jan 2014 11:58:01 Stefan G. Weichinger wrote:
> >> Thanks for the pointer.
> >>
> >> Unpacked /usr/portage/distfiles/portage-2.2.7.tar.bz2 right now
> >> etc
> >>
> >> Still gett
On Monday 06 Jan 2014 21:35:41 Alan McKinnon wrote:
> On 06/01/2014 19:58, »Q« wrote:
> > I had exactly the same weirdness after 1.6.8 was stabilized. I waited
> > a few hours, re-synced the tree, and then updated without any warnings
> > about blocks; the old libpng was unmerged and 1.6.8 was m
Am 08.01.2014 13:06, schrieb Mick:
> On Wednesday 08 Jan 2014 11:58:01 Stefan G. Weichinger wrote:
>
>> Thanks for the pointer.
>>
>> Unpacked /usr/portage/distfiles/portage-2.2.7.tar.bz2 right now
>> etc
>>
>> Still getting segfaults with the replaced emerge-command :-(
>
> This does not look
Hi all,
I routinely am logged into a server with multiple consoles (I log in
with one (the same) regular user, then su - to root).
This morning I tried to grep roots .bash_history for a command I ran
some time ago, and it wasn't there. I know I ran it, so I'd like to
configure my bash histor
On Wednesday 08 Jan 2014 12:06:47 Mick wrote:
> On Wednesday 08 Jan 2014 11:58:01 Stefan G. Weichinger wrote:
> > Thanks for the pointer.
> >
> > Unpacked /usr/portage/distfiles/portage-2.2.7.tar.bz2 right now etc
> >
> > Still getting segfaults with the replaced emerge-command :-(
>
> This does
On Wednesday 08 Jan 2014 11:58:01 Stefan G. Weichinger wrote:
> Thanks for the pointer.
>
> Unpacked /usr/portage/distfiles/portage-2.2.7.tar.bz2 right now etc
>
> Still getting segfaults with the replaced emerge-command :-(
This does not look good.
Can you get someone to reboot the machine wi
On Sunday 05 Jan 2014 21:41:46 Alan McKinnon wrote:
> I have Gentoo on a first gen Acer Aspire One. The teeny keyboard doesn't
> have a numpad, it's simulated by using the right-hand bunch of keys and
> you engage it with Fn-F11
>
> It's recently started booting up with the numpad on which is anno
Am 08.01.2014 12:53, schrieb Mick:
> In case things are really badly borked:
>
> http://www.gentoo.org/proj/en/portage/doc/manually-fixing-portage.xml
>
> Then you can use emerge --buildpkg to create a binary package
> locally, and scp it to the remote machine where you can use
> --usepkg or --u
Am 08.01.2014 12:45, schrieb Mick:
> The segfaults look scary and could point to hardware fault. I'd
> run a backup of any useful data to start with.
sure, backups ran late night ... and non-python-stuff seems to work ok
so far
> Then run 'python-updater' to rebuild any packages that had their
On Wednesday 08 Jan 2014 11:39:03 Stefan G. Weichinger wrote:
> Am 08.01.2014 12:28, schrieb Stefan G. Weichinger:
> > What can I do? quickpkg some python-version and copy over?
> > (sidenote: 32bit box ...)
>
> I assume it should be glibc repaired, right?
> Activated some 32bit-chroot here and bu
On Wednesday 08 Jan 2014 11:28:36 Stefan G. Weichinger wrote:
> Greetings,
>
> yesterday I started to upgrade an older gentoo server at a customer. It
> has only been updated now and then as they tend to save money and rarely
> contact me ...
>
> I recommended to at least apply the stuff mentione
Am 08.01.2014 12:28, schrieb Stefan G. Weichinger:
> What can I do? quickpkg some python-version and copy over?
> (sidenote: 32bit box ...)
I assume it should be glibc repaired, right?
Activated some 32bit-chroot here and building glibc-2.17-package now.
How to apply that without emerge? googlin
Greetings,
yesterday I started to upgrade an older gentoo server at a customer. It
has only been updated now and then as they tend to save money and rarely
contact me ...
I recommended to at least apply the stuff mentioned in the GLSAs ... and
applied some updates today (remote, via ssh).
Today
On Sunday 05 Jan 2014 16:15:31 Alan McKinnon wrote:
> Golden rule:
>
> When updating perl or python and a version change occurs, take note and
> always run perl-cleaner or python-updater afterwards.
Sage advice indeed. And if you're really paranoid, run python-updater before
perl-cleaner in cas
34 matches
Mail list logo
