solfire:/root>emerge kde-meta
Calculating dependencies -!!! Digest verification failed:
!!! /usr/portage/kde-base/kdebase-startkde/kdebase-startkde-4.1.2-r1.ebuild
!!! Reason: Filesize does not match recorded size
!!! Got: 4061
!!! Expected: 4064
... done!
>>> Verifying ebuild Manifests...
!!! Dig
ok, now it works...dont know what caused the last hickup...
mcc
[EMAIL PROTECTED] <[EMAIL PROTECTED]> [08-10-05 10:12]:
> solfire:/root>emerge kde-meta
> Calculating dependencies -!!! Digest verification failed:
> !!! /usr/portage/kde-base/kdebase-startkde/kdebase-startkde-4.1.2-r1.ebuild
> !!! R
Am Sonntag, 5. Oktober 2008 10:10:33 schrieb [EMAIL PROTECTED]:
> solfire:/root>emerge kde-meta
> Calculating dependencies -!!! Digest verification failed:
> !!! /usr/portage/kde-base/kdebase-startkde/kdebase-startkde-4.1.2-r1.ebuild
> !!! Reason: Filesize does not match recorded size
> !!! Got: 40
I'm using start-stop-daemon for making sure rc.wmii runs only once (If
you don't know wmii's way of handling configs: it doesn't matter).
Although I run it as user, it sets USER=root and HOME=/root. Is this
behaviour expected or should I file a bug?
-Erik
--
hackerkey://v4sw5hw2ln3pr5ck0m
On Sat, 2008-10-04 at 20:25 -0400, David Relson wrote:
> On Sun, 5 Oct 2008 01:05:35 +0200
> Alan McKinnon wrote:
>
> > On Sunday 05 October 2008 00:03:47 Andreas Simbuerger wrote:
> > > > Installs to /usr/local/lib sounds like b0rked ebuilds. I'd try
> > > > using equery to find the ebuilds that
On Sun, 05 Oct 2008 00:40:56 -0400
Albert Hopkins wrote:
> On Sat, 2008-10-04 at 23:29 -0400, David Relson wrote:
> [...]
> > Can somebody please explain how the gnome main menu is built, where
> > it resides, and how to force a rebuild?
>
> http://standards.freedesktop.org/menu-spec/latest/
The
Well, I took notice that kde 4.1.2 is in portage... I quickly removed kde-svn
and layman and began the unmasking and keywording of 4.1.2. I let it all
install over night and... This morning, with a little trepidation, I booted
into KDE-4.1.2... no problems!
This is the first of the recent kd
On Sunday 05 October 2008 07:19:37 [EMAIL PROTECTED] wrote:
> It getting more confused:
>
> This morning I did a
>
> emerge -pvuNDt world
>
> again and it shows me nothing suspicious.
>
> But doing a
>
> emerge -pv kde
>
> still reports:
>
> Calculating dependencies... done!
> [ebuild N] kde-b
On Sunday 05 October 2008 07:28:27 [EMAIL PROTECTED] wrote:
> Sorry, I mistyped some tings:
OK, that explains the last post then :-)
> I meant (hrrrmm): :)
> The /blocking/ items are only shown with
> emerge -pv kde.
The blocks do not exist until you try to emerge something that will block with
On Sunday 05 October 2008 10:10:33 [EMAIL PROTECTED] wrote:
> solfire:/root>emerge kde-meta
> Calculating dependencies -!!! Digest verification failed:
> !!! /usr/portage/kde-base/kdebase-startkde/kdebase-startkde-4.1.2-r1.ebuild
> !!! Reason: Filesize does not match recorded size
> !!! Got: 4061
>
Am Sonntag, 5. Oktober 2008 19:06:04 schrieb Alan McKinnon:
> When you run 'emerge -pvuND world' you are asking portage to update your
> entire system, do a deep resolve looking into DEPENDS as well, and to take
> changed/added/removed USE flags into account as well.
Correct so far.
> This will
Jerry McBride ha scritto:
Well, I took notice that kde 4.1.2 is in portage... I quickly removed kde-svn
and layman and began the unmasking and keywording of 4.1.2. I let it all
install over night and... This morning, with a little trepidation, I booted
into KDE-4.1.2... no problems!
This is
On Sunday 05 October 2008 20:08:23 b.n. wrote:
> Jerry McBride ha scritto:
> > Well, I took notice that kde 4.1.2 is in portage... I quickly removed
> > kde-svn and layman and began the unmasking and keywording of 4.1.2. I let
> > it all install over night and... This morning, with a little trepida
On Sun, 05 Oct 2008 20:08:23 +0200, b.n. wrote:
> Could you share your relevant package.mask and package.keywords, for
> the laziest of us? :)
emerge autounmask
autounmask kde-meta
:-)
--
Neil Bothwick
The trouble with the world is that everybody in it is three drinks behind.
signature.asc
Hi,
You may wish to specify the --user parameter. As this tool is for system
daemons (therefore located in /sbin), it seems obvious it starts daemons
as root by default. I checked on my system and I don't have a setuid bit
on this program, no more it starts any program when my wheel user
executes
Alle domenica 05 ottobre 2008, Neil Bothwick ha scritto:
> On Sun, 05 Oct 2008 20:08:23 +0200, b.n. wrote:
> > Could you share your relevant package.mask and package.keywords,
> > for the laziest of us? :)
>
> emerge autounmask
> autounmask kde-meta
>
> :-)
I continue to have a blocking package (ac
Hello,
Currently I'm using hotswap of the UltraBay devices (hdd and cd/dvd) on my IBM
T43, kernel 2.6.23-gentoo-r3, the hdd is Ultra ATA 160GB. Hotswap of these works
well.
And now my problem: I've bought new UltraBay box with new hdd - SATA II 320GB.
After hotswaping the new hdd (320), it i
On Sun, 5 Oct 2008 20:59:25 +0200, Luigi Pinna wrote:
> I continue to have a blocking package (actually not installed):
>
> [blocks B ] <=x11-libs/qt-4.4.0_alpha:4 (is blocking x11-libs/qt-
> dbus-4.4.1, x11-libs/qt-script-4.4.1, x11-libs/qt-qt3support-4.4.1, x11-
> libs/qt-assistant-4.4.1, x
On Sun, Oct 05, 2008 at 08:54:25PM +0200, Jil Larner wrote:
> You may wish to specify the --user parameter. As this tool is for system
> daemons (therefore located in /sbin), it seems obvious it starts daemons
> as root by default. I checked on my system and I don't have a setuid bit
> on this prog
On Sunday 05 October 2008 20:16:55 Neil Bothwick wrote:
> On Sun, 05 Oct 2008 20:08:23 +0200, b.n. wrote:
> > Could you share your relevant package.mask and package.keywords, for
> > the laziest of us? :)
>
> emerge autounmask
> autounmask kde-meta
For the super-lazy amongst us, what does that pac
Alan McKinnon wrote:
> On Sunday 05 October 2008 20:16:55 Neil Bothwick wrote:
>
>> On Sun, 05 Oct 2008 20:08:23 +0200, b.n. wrote:
>>
>>> Could you share your relevant package.mask and package.keywords, for
>>> the laziest of us? :)
>>>
>> emerge autounmask
>> autounmask kde-meta
>>
On Sun, 5 Oct 2008 22:47:42 +0200, Alan McKinnon wrote:
> > emerge autounmask
> > autounmask kde-meta
>
> For the super-lazy amongst us, what does that package do?
>
> OK, I can figure out what it does, so my real question should be "what
> other stuff does it do that I might not expect? Any g
Neil Bothwick wrote:
>
> It basically adds a bunch of packages to /etc/portage/packages.unmask
> and /etc/portage/packages.keywords, bracketed by start/end comments so
> you can remove them. It's a quick and easy way of emerging something
> with a lot of masked dependencies, like kde-meta:4.
>
> I
It turns out that /etc/portage/package.keywords
and /etc/portage/package.unmask can be directories, which is convenient
for organizational purposes. If this is the case, autounmask does the
smart thing and creates the file autounmask-pkgname (in this case,
autounmask-kde-meta) in those folders. I
On Sun, 05 Oct 2008 17:30:40 -0500, Dale wrote:
> > I used it the last time I tried KDE4 and it did just as was expected,
> > except is added =cat/pkg-vers, which I changed to ~cat/pkg/vers so I
> > could pick up and fixes.
> You can tell it not to put versions tho.
Yes, but that can be dodgy. I
I thought it was solved, but I was wrong.
Last time I reported this I was advised to start it from the command
line. So here's what I get for "oowriter":
/usr/bin/soffice: line 254: 28590 Segmentation fault
"$sd_prog/$sd_binary" "$@"
And I cannot use OO at all.
My root directory (where all bi
Greetings!
I've recently updated from kernel 2.6.20 to 2.6.24 a little used
machine. The new kernel is working quite well. However hdparm isn't
happy.
Running either "hdparm -d0 /dev/hda" or "hdparm -d1 /dev/hda" gives a
"HDIO_SET_DMA failed: Operation not permitted" error. Using the same
co
Hi,
Erik Hahn a écrit :
> It doesn't run the command as root but as normal user (it isn't setuid
> either. All it does is setting the *variables* $USER and $HOME to the
> wrong values.
>
Oh, I read too quickly :x And by the way didn't give the right command
switch that are --chuid --user and --e
Hi,
David Relson a écrit :
> CONFIG_SCSI_DMA=y
Isn't that an option which considers all disks to be SATA ?
Not sure, but you might check that.
Sincerely,
Jil
David Relson schrieb:
> Greetings!
>
> I've recently updated from kernel 2.6.20 to 2.6.24 a little used
> machine. The new kernel is working quite well. However hdparm isn't
> happy.
>
> Running either "hdparm -d0 /dev/hda" or "hdparm -d1 /dev/hda" gives a
> "HDIO_SET_DMA failed: Operation no
30 matches
Mail list logo
