Ilya A. Volynets-Evenbakh wrote:
Good good! Laugh is good for your health, and you'll
need lot of support in that area next time I see you...
Ok, seriously, WHAT THE FUCK is wrong with this? Anyone? The gentoo
flaming guide [1] is a JOKE. Lets not get violent here, mkay?
-smithj
[1]: http:
Alin Nastac wrote:
Please correct me if I'm wrong, but isn't amd64 and ia64 architectures
nearly the same? Beside 3dnow/sse instruction sets of course.
If so, shouldn't we have the same kewords ("amd64 ia64", "~amd64 ~ia64"
or none) on every package that don't use 3dnow/sse instructions?
no, th
I will be going to the Ohio Linux Fest with my company this weekend. If
anyone from Gentoo will be going, let me know and we can hang out. I'll
be arriving Friday and leaving Saturday.
-smithj
--
gentoo-dev@gentoo.org mailing list
media-gfx/xzgv is masked pending removal due to a dead upstream. There
are plenty of other image viewers out there which are maintained.
-smithj
--
gentoo-dev@gentoo.org mailing list
Thomas Cort wrote:
On Sat, 06 May 2006 21:22:56 -0700
Joshua Jackson <[EMAIL PROTECTED]> wrote:
I've noticed a disturbing trend with the website redesign. Larry is
disappearing from the site.
That is utterly disturbing! I too enjoy Larry the cow, and would like to keep
him around and improve
Chris White wrote:
That would be suka, but just to somewhat summarize, there are a lot of issues
in getting it ported to amd64, and upstream itself is using lots of manpower
to try and resolve this issue. At this point it's pretty much going with what
upstream is doing. I tried it personally an
Ciaran McCreesh wrote:
I for one welcome our new infra overlords. Perhaps you should add in a
clause saying that infra will randomly (maybe with the help of a
keyword filter) inspect emails sent to all @gentoo.org addresses for
any signs of subversive activity. You could also add a clause saying
Carsten Lohrke wrote:
As soon as KDE 3.5 goes stable - no date yet - I'd like to bury
x11-misc/karamba (if desktop-misc herd agrees)
x11-misc/superkaramba
as well as
x11-plugins/karamba-* - unmaintained for years
Reasoning is that the Superkaramba that comes with KDE 3.5 is a rewrite,
ena
Stefan Cornelius wrote:
Hi devs,
app-arch/zoo is prone to a buffer overflow that needs to be patched but
the package has no maintainer, see http://bugs.gentoo.org/123782 for
details. Since I don't have commit rights, I would appreciate help to
get this sorted out, the patch is really simple and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick Rout wrote:
> am i right in saying this package has disappeared quite recently?
http://www.gentoo.org/cgi-bin/viewcvs.cgi/sys-kernel/win4lin-sources/
"Removing win4lin-sources; in need of maintainer due to security issues..."
- --
smithj
Gen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georgi Georgiev wrote:
> When should make be used? I thought that ebuilds should always use
> emake, and if necessary -- emake -j1. But never make.
make DESTDIR=${D} install || die "make install failed"
- --
smithj
Gentoo Developer
[ desktop stuff
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Sun, 21 Aug 2005 23:10:58 -0400 "Nathan L. Adams" <[EMAIL PROTECTED]>
> wrote:
> | What are the most common ebuild mistakes?
> Existing tools will already get some of these. However, most
> user-submitted ebuilds have quite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> Isn't this one of those things that's best done on a per-dev basis?
> It's so trivial there's no point shipping an app that does it --
> reading the associated documentation would take longer than writing
> your own. Plus that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott Shawcroft wrote:
> The bugday database would hold additional bug information. Not the
> data found in bugzilla. We get the available info from the bugzilla
> DB. The bugday DB is a supplement.
your origional email said "User logins using user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott Shawcroft wrote:
> - Have pre-bugday and post-bugday podcasts designed to present
> information in an alternate form.
i like it, but also make it available as an .mp3 or a more common format (i
know nothing about podcasting or if mplayer could p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Casey Allen Shobe wrote:
> I'm sure there will be more - there are a number of ebuilds I have
> small issues with that I just workaround. I'm much more inclined
> to just fix the problem instead of complaining about it because of
> past experiences
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alin Dobre wrote:
> Am I the only one receiving this message? I have received another one
> last days. If so, there is someone infected that is subscribed to this
> list. Could be smithj himself, but usually the sender is forged. The two
> emails come
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Diego 'Flameeyes' Pettenò wrote:
> On Thursday 07 July 2005 02:04, Sven Wegener wrote:
>
>>We would like to split up src_compile. The
>>new src_configure should just do the econf part and src_compile should
>>do the emake part.
>
> That will be very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas de Grenier de Latour wrote:
> Btw, what's wrong with the `DEPEND="$(your_function)" || die`
> i've proposed? Using a return code seems to be the simplest way
> to signal a failure, no?
>
calling a function in a global scope is a bad idea. it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Doty wrote:
> All-
>
> Everyone welcome Jan(grahl04) as the newest GDP German translator. In
> his own words, "Most of my time is currently spent attending the
> University of Florida, apart from that I like to engage in a number of
> volunteer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan Smith wrote:
> Upstream is dead, package doesn't work, and it has a suitable
> replacement which seems to be actively developed that would be put into
> portage as its replacement. No reverse dependency issues.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As some of you may know, there were some problems with xlockmore-5.18,
namely that once the screen was locked, it refused to unlock. Obviously
this was not desired behaviour, so that version was masked.
vanquirius came up with two possible solutions.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan wrote:
> I was just reading a GLSA on the announce list, and noticed the
> Creative-Commons Attribution/Share-alike license at the bottom. Why I
> clicked the link this time in particular I don't know, but I did...
>
> It seems the 2.0 version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
st3vie wrote:
> hi all, and thanks for the kind words. :)
(use your gentoo email address... thats why its there ;-)
- --
smithj
Gentoo Developer
[ desktop-misc && documentation ]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan Kundrát wrote:
> Christian Hartmann wrote:
>
>>Feedback is highly appreciated.
>
>
> IMHO if you don't require moderators of Local Forums to accept and
> follow same guidelines as the global moderators, you're actually against
> the point of "Mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Upstream is dead, package doesn't work, and it has a suitable
replacement which seems to be actively developed that would be put into
portage as its replacement. No reverse dependency issues.
The package has been masked for a week to ensure that noone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Beber [Gentoo] wrote:
> Hi guys,
>
> thanks for you to look of my reply on this bug :)
>
> It don't think that a virtual need to be use here. 3 softwares for a
> virtual is quite less.
>
> Why are you placing a REDEPEND instead of a PDEPEND ?
> xaut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The desktop-misc herd (which was sadly neglected until recently) could
benefit from a new virtual. x11-misc/xautolock is a wrapper which locks
the screen via any appropriate program such as xlockmore or xtrlock.
This program needs to depend on an xlock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
M. Edward (Ed) Borasky wrote:
> I'm not a developer ... and I'm not in California ... but I am a Gentoo
> bigot and I'm certainly willing to help out ... as are most Gentoo
> users/developers.
> [snip]
I know that I can't speak for all the developers,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark S Petrovic wrote:
> Is there a principal Gentoo developer in Northern or Southern California
> (preferred) to whom I can pay a visit to gain a deeper understanding of
> who the Gentoo team is, what they are trying to accomplish, and how?
If you h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris White wrote:
> [snip]
> if you feel that I have handled the situation properly regarding your
> voicing, please send an email to dev-relations and I'll be happy to work
> things out.
> [snip]
just to clarify: you mean improperly, right? why wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron Walker wrote:
> Greetings,
>
> Please give a nice Gentoo-ized welcome to Senno During (st3vie). Senno will
> be
> leading the Dutch GWN Translation team (actually he has been for several
> weeks).
>
> Ripped from his quiz:
>
> i'm 28 years
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Nigbur wrote:
> On Tuesday 14 June 2005 02:59, Mike Doty wrote:
>
>>Hey all-
>>
>>Introducing our newest victim^H^H^H^H^H^Hdev, Johnathan Smith.
>>smithj(as he's known to his friends) hails from North Carolina, here in
>>the US. He's going to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Introducing our newest victim^H^H^H^H^H^Hdev, Johnathan Smith. smithj
> (as he's known to his friends) hails from North Carolina, here in
> the US. He's going to be helping out with desktop-misc items as well
> as hopefully
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i asked this in #gentoo-dev, but didn't get much of an answer (partly
due to being kicked off irc by a crappy wireless connection)
in any case, i have an x86, and want to create depgraphs for
other archs
my first attempt was running this command (xzg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey Forman wrote:
> I've looked at the actual DB behind bugzilla, and that seems to be the
> only bug having that such situation, with a resolved-like status, but no
> resolution, all the other bugs look fine. *shrug*
>
> -Jeffrey
bug 89521 [1]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey Forman wrote:
> [snip]
> Anything else I've forgotten, I will happily take full credit for.
> [snip]
one more thing: comment #15 of bug 92622 [1] shows the bug which was a
dup as marked through. perhaps this is intentional (resolved bugs show
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georgi Georgiev wrote:
> maillog: 17/05/2005-16:04:20(+0300): Alin Dobre types
>>>
>>>*** This bug has been marked as a duplicate of 12745 ***
>>
>>Here it is, the last row.
>
>
> But in the headers it says:
>
> Status: RESOLVED
> Resolution:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey Forman wrote:
> Hey All,
>
> The upgrade for bugs.gentoo.org went exactly as I had planned for.
> Completed in under 20 minutes, which included this email. I've upgraded
> our Bugzilla from the old 2.18rc2 to 2.18.1. This fixes more security
>
39 matches
Mail list logo
