1.8.1 has been stable for quite some time so let's get rid of 1.7.x
+# Vlastimil Babka cas...@gentoo.org (15 Feb 2011)
+# Masked for removal of all versions older than 1.8.1 in few weeks.
+dev-java/ant-core-1.8.1
+dev-java/ant-antlr-1.8.1
+dev-java/ant-apache-bcel-1.8.1
+dev-java/ant-apache-bsf
,
Petteri
Title: Pending Removal of Java support on ia64
Author: Petteri Räty betelge...@gentoo.org
Author: IA64 Arch Team i...@gentoo.org
Author: Vlastimil Babka cas...@gentoo.org
Content-Type: text/plain
Posted: 2011-02-18
Revision: 1
News-Item-Format: 1.0
Display-If-Keyword: ia64
Display
Hi,
when trying to bump sci-geosciences/googleearth to a 6 beta version [1],
there's a problem with missing /lib/ld-lsb.so.3 file, which the binary
somehow requires, and otherwise fails with a rather cryptic error
message (saying that the binary itself is missing).
Apparently this is mandated
On 01/31/2011 04:23 PM, Nathan Phillip Brink wrote:
Have you checked if patchelf can fix the googleearth binary? I think
that it is intended for this sort of problem:
http://nixos.org/patchelf.html .
Thank you, this really helped! And since patchelf is in the tree, I
could workaround
On 02/25/2010 02:41 PM, Markos Chandras wrote:
On Thursday 25 February 2010 08:22:17 Ulrich Mueller wrote:
On Wed, 24 Feb 2010, Robin H Johnson wrote:
Metadata.xml should allow use of achangepolicies element. Within
the element, package maintainers should be able to describe how
Duncan wrote:
In theory that's what those stupid version string thingys are for, but
it's s much easier just to forget one! =:^[
Maybe something about this should go in the handbook -- a suggestion that
if one is going to use a package.unmask entry, that they copy the
package.mask entry
Ben de Groot wrote:
2009/11/8 Mark Loeser halc...@gentoo.org:
Also, please learn how to communicate in a manner that is constructive
instead of acting like a dick at every opportunity.
Looks to me this should be applied to some others in this thread first.
Really, aren't there more
Zac Medico wrote:
Vlastimil Babka wrote:
The question is what to do now, rename it? Users will then see it again,
and I don't know if there are even worse consequences.
AFAIK, seeing it again is the worst that will happen. The cvs -
rsync script will ensure that the incorrectly named new
Hi,
it was brought up by ulm that the news item
'2009-04-18-java-config-wrapper-0.16' has an illegal name because it
contains a dot. As it was me who named and commited it, I am sorry for
this mistake. The file name in -dev review mail was called
'generation1-deprecation' and I probably
Peter Faraday Weller wrote:
On a more serious note, the problem seems to be the complete lack of
management in the required places, Gentoo is fast becoming (or more
likely, already is) an anarchic organisation, where it's becoming
nigh-on impossible to keep track of things.
I see a number of
dev-java/ant-tasks was a meta ebuild that is no longer used in 1.7.1 so
it's going away completely
# Vlastimil Babka cas...@gentoo.org (30 Apr 2009)
# masked for removal, bug #261563
=dev-java/ant-core-1.7.0*
=dev-java/ant-antlr-1.7.0*
=dev-java/ant-apache-bcel-1.7.0*
=dev-java/ant-apache-bsf
Richard Freeman wrote:
Tobias Scherbaum wrote:
Wouldn't it make much more sense to package move ksudoku then?
I was thinking the same thing - this is a stable package, so ideally it
shouldn't be replaced with an unstable one. Why not keep -0.4 in the
tree for stable users?
+1
Also the
Thomas Sachau wrote:
I see many ebuild that still use econf || die, also econf should die by
itself. Are there any
specific reasons for this? Some cases where econf does not die also it fails?
Or some other reason
for this?
My guess is that due to the general lack of consistency in what
David Leverton wrote:
On Saturday 20 September 2008 18:15:27 Alexis Ballier wrote:
I can think of checks like:
- foo is a dep/rdep of bar
- foo has a plugin like architecture
- bar will work with minimal foo
- most people will expect some features in bar that come with foo's
plugins
- we
Apparently, setting USE=x86 in make.conf on amd64 arch can have funny
consequences such as [1]. And I can imagine even more subtle and hard to
detect errors due to this.
I think it's better to prevent this rather than waste time with bug
reports like that. I asked Zac on IRC whether portage could
Fernando J. Pereda wrote:
On 10 Jun 2008, at 15:33, Joe Peterson wrote:
Luca Barbato wrote:
Check if exists a line EAPI=*$, if does and the rest of the string
matches an understood eapi, go on sourcing, otherwise ignore/mask it...
And placing it out-of-band (like # EAPI=...) avoids any
.
The question is how to name the switch :) -n could be confusing as
echo -n has the opposite effect. Maybe -b for blank?
--
Vlastimil Babka (Caster)
Gentoo/Java
signature.asc
Description: OpenPGP digital signature
domain
is not the best thing durability-wise :)
--
Vlastimil Babka (Caster)
Gentoo/Java
signature.asc
Description: OpenPGP digital signature
++ I suppose you want people to read the package-specific information
and not e.g. fill bug reports caused by wrong assumptions about the
flag's meaning.
--
Vlastimil Babka (Caster)
Gentoo/Java
signature.asc
Description: OpenPGP digital signature
that non-elog output is not tied too
closely to ends of elog blocks.
--
Vlastimil Babka (Caster)
Gentoo/Java
signature.asc
Description: OpenPGP digital signature
Enrico Weigelt wrote:
* Ciaran McCreesh [EMAIL PROTECTED] schrieb:
Hi,
Hi Enrico, long time no see!
b) Marking that two related implementations are mutually incompatible at
runtime because they both provide the same binary.
Classical example: MTA's:
Traditionally they tend to provide an
Samuli Suominen wrote:
Wed, 16 Apr 2008 12:09:24 -0700
Chris Gianelloni [EMAIL PROTECTED] kirjoitti:
On Wed, 2008-04-16 at 11:49 +0200, Vlastimil Babka wrote:
thirty days is the norm for the minimal period between an ebuilds
last
It is the norm. It is not a requirement. In fact
Enrico Weigelt wrote:
* Ciaran McCreesh [EMAIL PROTECTED] schrieb:
Hi,
Hi Enrico, long time no see!
b) Marking that two related implementations are mutually incompatible at
runtime because they both provide the same binary.
Classical example: MTA's:
Traditionally they tend to provide an
should be completely separate,
never conflicting each other. So some package kfoo either depends
on kdelibfoo-3.x OR kdelibfoo-4.x.
Of course I don't know whether the problems comes from ebuilds
or upstream ;-o
If you don't know why the blocks nned to be there then why comment on that?
--
Vlastimil
Jeroen Roovers wrote:
Dear ebuild maintainers,
thirty days is the norm for the minimal period between an ebuilds last
non-keywording change while in the tree and the usual call for
stabilisation. If you cannot find a pressing reason to push
stabilisation forward, then don't ask. In the
Petteri Räty wrote:
Vlastimil Babka kirjoitti:
*portage-2.1.5_rc1 (04 Apr 2008)
04 Apr 2008; Zac Medico [EMAIL PROTECTED] +portage-2.1.5_rc1.ebuild:
2.1.5_rc1 release. In the event that a previously installed package has
since been masked, emerge will no longer perform an automatic
Mark Loeser wrote:
Mike Frysinger [EMAIL PROTECTED] said:
On Sunday 30 March 2008, Mark Loeser wrote:
Actually, I'd say this should just be removed. If a user wants to apply
a patch, they can put their own ebuild into an overlay and do it
themselves (presumably if they want to patch
Petteri Räty wrote:
Attached is a patch that fixes this.
Arrays? How non-POSIX1
Anyway, why don't we instead discuss what phases to add to next EAPI, so
we can avoid these hacks :)
--
Vlastimil Babka (Caster)
Gentoo/Java
signature.asc
Description: OpenPGP digital signature
Hi,
reading comments on bug 209538, I've seen this dangerous thing from Zac:
Once these issues are solved it will be nice if we can rely exclusively
on the dependencies from /var/db/pkg.
Well, the idea that devs will have to revbump packages just for RDEPEND
version restrictions so that
would implement it, and portage need not
care), or we would want to use the general metadata query also for other
purposes.
Anyway, restricting ebuilds from vdb access sounds like a good idea to me.
--
Vlastimil Babka (Caster)
Gentoo/Java
signature.asc
Description: OpenPGP digital signature
(YMMV)
Mon Nov 19 22:26:38 2007 dev-lang/perl-5.8.8-r4
merge time: 6 minutes and 10 seconds.
Wed Nov 7 12:46:01 2007 sys-apps/paludis-0.24.6
merge time: 16 minutes and 25 seconds.
--
Vlastimil Babka (Caster)
Gentoo/Java
signature.asc
Description: OpenPGP digital
), yuck :)
--
Vlastimil Babka (Caster)
Gentoo/Java
signature.asc
Description: OpenPGP digital signature
Daniel Barkalow wrote:
It shouldn't remove the Java VM that
java-config is set to.
This would be a bit trickier I guess, as every user can have it set
differently :)
Caster
--
gentoo-portage-dev@lists.gentoo.org mailing list
Mike Frysinger wrote:
On Monday 28 January 2008, Ryan Hill wrote:
In your package.mask entry, it would help to have the following info:
it would help too if you add a comment like this to the top of the mask file
-mike
I've did it instead:
Index: package.mask
Chris Gianelloni wrote:
Do we really need a front-page news item for this? I don't think the
impact would be terribly great, as I suspect this affects a very small
number of people whom are likely to be more advanced users. I think
adding the info to GMN/gentoo-dev-announce/gentoo-user should
Duncan wrote:
A GWN or similar announcement before it moves beyond the dev profiles
would be nice, but if the affected devs (incl. bugwranglers) are willing
to deal with the complaints and they seem to be, the leaner system and
image is IMO a good thing, and announcement or not, people really
Chris Gianelloni wrote:
I think throwing up an announcement today/tomorrow for Thursday/Friday
should be sufficient for this sort of a change, as it won't affect any
user who has a version of portage released in the past ~1.5 years.
So, since it seems nobody objected it, time for the
Chris Gianelloni wrote:
On Sun, 2008-01-27 at 17:11 -0800, Zac Medico wrote:
If there are no objections then I don't so any reason not to go ahead and add
the manifest1_obsolete sometime in the near future. Thoughts?
Let's do it. I look forward to a lot less inodes on my disks.
Let's schedule
Duncan wrote:
At minimum, I'd say make the usual BIG WARNING NOISES in the usual
places, and probably still expect complaints. It may still be worth
doing to cut down on system size... or not, depending on where the system
size vs. inevitable complaints comes down. (FWIW, it's precisely this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Hill wrote:
| I think Jakub should get the Octane2. Then he can help with all those
mips bugs. :)
I thought removing keywords was easy even without the actual hardware :P
Caster
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)
Santiago M. Mola wrote:
But stuff like aac needs encode and cdio conflicts with
cdparanoia should be something separate from USE flag documentation.
Well, at least until it's handled at ebuild level, local USE flag
documentation can be used to explain the implications to the user
beforehand
Ryan Hill wrote:
What do people think of this?
a) Keep use.desc as it is: a list of common flags and a short general
description of their meaning.
Good.
b) Keep use.local.desc as it is: a list of per-package flags that are
specific to one to a few ebuilds (i think 5 is the number though i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wulf C. Krueger wrote:
| We would welcome any comments, especially if accompanied by patches ;)
| and, of course, your kind approval to commit it. :-)
Hi,
Checked only briefly, it's late :) but I miss a comment in the header
that you need EAPI=1 in
Ciaran McCreesh wrote:
a) Drop all keywords but those of mips. Leaves mips and, more
importantly, its users with a vulnerable and unmaintained set of
packages.
...and break the tree spectacularly, causing huge amounts of pain for
your fellow developers when they encounter horrible repoman
and
fixed, work in progres in java-overlay, bug #164129.
Vlastimil Babka
--
gentoo-dev@lists.gentoo.org mailing list
Markus Ullmann wrote:
-junit - Adds junit awareness -- useful for developers.
+junit - Adds junit testframework awareness -- useful for developers
junit - Adds junit test framework awareness -- useful for developers
Actually, this flag should probably go away with gen-1 java ebuilds
(gen-2
Ciaran McCreesh wrote:
On Wed, 12 Dec 2007 23:14:24 +0100
Carsten Lohrke [EMAIL PROTECTED] wrote:
I disagree here. It would be annoying and possibly even hindering in
future not being able to use higher EAPI features in eclasses. Point
is the eclass has to check, if the author of an ebuild
William L. Thomson Jr. wrote:
On Fri, 2007-12-14 at 18:00 +0200, Petteri Räty wrote:
He doesn't have a
family yet but perhaps that's why he's into photographing.
What's that implying he is some photo perv or something. Taking pictures
of others families? Taking photo's makes up for a lack
administrative thing so people don't add many new global flags
without consultation, but still can quickly add local flags just for
their package.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Warner wrote:
perhaps it'd be useful to introduce an anal_die. developers run anal
tests,
users get sane tests.
-mike
Anal ftw
-Alec
Also known as FEATURES=stricter.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP
whether the file has simply been moved, by either correcting the
path or removing the filename from the dodoc call.
dodoc calls should have || die and USE=doc should be tested before
commiting a bump, IMHO
--
Vlastimil Babka (Caster)
Gentoo/Java
--
[EMAIL PROTECTED] mailing list
this for such cases.
If this is what you call RDEPEND conceptually broken, then sorry for
useles try to explain it :) Maybe package manager could be smart enough
and relax the RDEPEND in such cases itself, maybe it's better to say
that via PDEPEND explicitly...
--
Vlastimil Babka (Caster)
Gentoo/Java
=186156
Thanks
As you wish! [1] :)
[1] http://bugs.gentoo.org/show_activity.cgi?id=186156
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGooZEtbrAj05h3oQRApS1AKCU0vyw
-mtune?
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGndsrtbrAj05h3oQRAp5hAJ4in2JnV637D7GyDMvG6hc8A8/n4QCeK9Eo
IFUTZxAFqfSVx3Za64GQM0c=
=6wSA
-END PGP SIGNATURE
?). OTOH, while this
might be useful for more than few packages (I can also think of some),
it's not too many to clutter the tree significantly.
Or am I missing something?
Cheers,
-jkt
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux
at large. We are volunteers, and if we want to treat Gentoo as
our own personal toy (which we currently aren't), then so be it.
Are you people serious? Let's ban nondevs from bugzilla then? Close
#gentoo, disband PR, etc? Not sure if we can keep any sponsors then...
- --
Vlastimil Babka (Caster
in the middle of
linear scale between freezing water and average healthy human body
temperature. And not higher than the latter, as nowadays!
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Long wrote:
And no, I don't like being lumped in with Mr McCreesh.
Why would anyone do that? His trolling is sophisticated, but you're just
an annoying spammer.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raúl Porcel wrote:
good, now my nick is armin79 :D
Lies! No way your karma would go up! Cheater!
armin79--
armin78--
armin77--
You're good now.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU
since some point. And if not, it should :)
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGiaA2tbrAj05h3oQRAuyAAJ4nu6QcexxRQkQEpg98pXGn09Ry+gCfVDtk
H3ENhWchaop/RzVBH8kNQoI
?
Or do we need a GLEP and/or council approval?
(just kidding)
((hopefully))
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGfmeVtbrAj05h3oQRAuQLAKCT7ePtnoD3mUW+y1H
':
* dev-java/ibm-jdk-bin-1.5.0.5: 50.9M
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGehf7tbrAj05h3oQRAi3BAJ9CIIQ4We8aY2LIRlCcXvhEO/04yACfRtrh
Xn8cfOd3YLaHNp8H/efM84s
do the same for qpkg.c
tia.
And for emerge -b/-B/FEATURES=buildpkg. Too bad people will miss those
messages there anyway :)
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
/ies4linux
*ies4linux-2.0.5 (21 Jun 2007)
21 Jun 2007; Jurek Bartuszek [EMAIL PROTECTED]
+ies4linux-2.0.5.ebuild:
Initial version (closing bug #143798), credit goes Mathieu Bonnet
[EMAIL PROTECTED] for providing the ebuilds.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE
:)
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGeaJOtbrAj05h3oQRAi3lAJwKducWie0CgqMwZeXN4aI3apvBUwCffgF7
6PX1hIR+D1jEg4+dwU9p6+4=
=P7os
-END PGP SIGNATURE-
--
[EMAIL
that.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGcmHKtbrAj05h3oQRAjxQAJ9jYtK7aAAWBvYttCTLW1Kt7a/OzACeL2Oe
aLZwTVOKohkRfcyyfRKpqMY=
=gYLD
-END PGP SIGNATURE
that could have been avoided if Skype wasn't marked
stable.
It could be interesting to evaluate a new rule fetch/mirror restricted
package can't be marked stable :).
I believe common sense and per-package experience is better than such
general rules :)
- --
Vlastimil Babka (Caster)
Gentoo/Java
question is, does this make sense? Is something like this
planned for some EAPI0? Would it be appropriate for me (a non-dev) to
file a bug and link it to SpanKy's EAPI-1 tracker bug?
There's been bug 4315 for ages, so maybe just reassign it to PMS?
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thilo Bangert wrote:
I want a gentoo-kindergarten list, where useless discussions like this
(sub)thread can be directed to.
kids, grow up!
right
s/gentoo-//
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gustavo Felisberto wrote:
Any alternatives?
Drop it from stable completely, possibly package.mask or move to
overlay. Why should this closed-source rootkit be in stable?
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE
with google) or use the ~arch 1.4. This won't
affect users that already have 1.4 installed, or just have the distfile.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Abhay Kedia wrote:
On Wednesday 13 Jun 2007 10:11:24 pm Vlastimil Babka wrote:
Drop it from stable completely, possibly package.mask or move to
overlay. Why should this closed-source rootkit be in stable?
If closed source is the criteria
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kent Fredric wrote:
On 6/14/07, Vlastimil Babka [EMAIL PROTECTED] wrote:
Also, ion3 was IIRC removed recently also for upstream trying to force
new versions against our stable policy. And that was opensource.
[U] x11-wm/ion3
Available
and the bitching gets out.
Just unsubscribe the list and you won't see it :)
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGcGTZtbrAj05h3oQRAj0SAJ0RLIx//xj8AsyLBs
for
such packages as there are no guarantees while in p.mask.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGboh4tbrAj05h3oQRAvv1AJ45RRl0kr1246ug5H1ZdSTZ5i5j5QCfaq25
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vlastimil Babka wrote:
+# Vlastimil Babka [EMAIL PROTECTED] (10 Jun 2007)
+# Outdated version, proprietary binary package, library that nothing in
tree
+# uses. Still generation-1. Assuming nobody needs it as there was never a
+# version bump
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+# Vlastimil Babka [EMAIL PROTECTED] (10 Jun 2007)
+# Outdated version, proprietary binary package, library that nothing in
tree
+# uses. Still generation-1. Assuming nobody needs it as there was never a
+# version bump request. Will be removed after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+# Vlastimil Babka [EMAIL PROTECTED] (10 Jun 2007)
+# Outdated version, proprietary binary package, library that nothing in
tree
+# uses. Still generation-1. Assuming nobody needs it as there was never a
+# version bump request. Will be removed after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raúl Porcel wrote:
Vlastimil Babka wrote:
Raúl Porcel wrote:
Agreed from mozilla.
firefox and seamonkey already have the global use-flag
Is there any guideline from mozilla team about what to do when there are
more than one of these flags
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kumba wrote:
And maybe a dev who
secretly dabbles in another OSlike Wind...err, Ubuntu!
I thought this position has been already filled :)
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux
by
package AND enabled by user? Some of those local flag descriptions
suggest that USE=firefox xulrunner results in using xulrunner (so it
has higher priority). So is that recommended, and how about seamonkey?
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU
such license for any FOSS project.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGXn/1tbrAj05h3oQRApMDAKCZoGxaTEEhPQusvIuGvI23ZcSydwCfahcU
iPUW0knA2ZZ76hT5mkv98Cs=
=8Sbs
them open myself - if the user doesn't provide a patch,
it's still something that I'd get around to doing eventually.
I specifically want my bugs to stay open, and be easily visible as to
why I've kept them open.
+1 Keyword is a good idea.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Ramsay wrote:
Chris Gianelloni wrote:
On Wed, 2007-04-18 at 07:39 -0600, Jim Ramsay wrote:
Vlastimil Babka [EMAIL PROTECTED] wrote:
Or maybe implement new bugzilla keywords, like STABLEREQ and
KEYWORDREQ which would be added to the respective
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin H. Johnson wrote:
On Sun, May 27, 2007 at 12:23:56PM +0200, Vlastimil Babka wrote:
Bug was fixed yesterday, keywords added, so to let you know. I would of
course love to go now and add these keywords to all my (java) current
bugs
to figure out how you justify calling Java a
dead language.
It's not C++ nor Ruby.
Anyway, offtopic :)
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
changing the profiles right now?
(I guess people on ~arch will need to unmask it to not downgrade).
That can be avoided if you make an artifical revbump that won't change
anything, just have stable keywords, and you mask that revision
specifically.
- --
Vlastimil Babka (Caster)
Gentoo/Java
for new news messages should be displayed:
* After an emerge sync
* After an emerge --pretend
* Before an emerge target (which may also include a red warning
message)
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using
a replacement for elog? I thought news were
supposed to be delivered before upgrading. Also You should update your
configuration files after upgrading. sounds like something one would
read before upgrade...
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU
upgrading from
previous versions to =0.24. How likely is that someone has had such
version previously, then uninstalled paludis completely leaving config
files around, and now installs =0.24? So likely it's worth that future
fresh installs of say 0.50 will display this news too?
- --
Vlastimil Babka
puts a new set of
DEPENDS requirements on your system.
Daniel
And sometimes these extra deps can result in circular deps.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+# Vlastimil Babka [EMAIL PROTECTED] (30 Apr 2007)
+# Stale upstream (since 2002), -bin library that nothing in tree uses
+# so it's not needed. Will be removed into java junkyard around 30 May.
+dev-java/dbconnectionbroker-bin
- --
Vlastimil Babka
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
# Vlastimil Babka [EMAIL PROTECTED] (30 Apr 2007)
+# Fetch-restricted binary library that nothing in tree uses, upstream
+# unsupported (EOL). Will be removed into java junkyard around 30 May.
+dev-java/infobus-bin
- --
Vlastimil Babka (Caster
this package, needs it,
uses it, and/or is willing to updated it.
Recalled and unmasked at user's request.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+# Vlastimil Babka [EMAIL PROTECTED] (28 Apr 2007)
+# Still generation 1 and stale upstream, library that
+# nothing in tree uses so it's not needed. Will be
+# removed around 28 May. Generation 2 revision is in
+# the java-overlay.
+dev-java/joscar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
# Vlastimil Babka [EMAIL PROTECTED] (28 Apr 2007)
# Stale upstream, library that nothing in tree uses
# so it's not needed. Will be removed around 28 May.
# Generation 2 revision is in the java-overlay.
dev-java/jmbus
- --
Vlastimil Babka (Caster
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+# Vlastimil Babka [EMAIL PROTECTED] (28 Apr 2007)
+# Unused generation-1 fetch restricted binary libraries.
+# Will be moved to junkyard around 28 May.
+dev-java/sun-connector-bin
+dev-java/sun-dsml-bin
+dev-java/sun-ejb-spec
- --
Vlastimil Babka
destroy the beauty of atomic commits...
--
Vlastimil Babka (Caster)
Gentoo/Java
--
[EMAIL PROTECTED] mailing list
this be the last mail that goes to both, and any further only to -dev.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGKTFItbrAj05h3oQRAjdKAJ9kkxOFJKC411v7CdnVzFuZh7n0eQCfW6t5
5s
be added to the respective bugs. Then you (the maintainer)
can easily create (and save) an advanced search that will filter them
out, while still being able to check them in a different search. Might
be also useful for arch teams to separate stabling and keywording bugs?
- --
Vlastimil Babka (Caster
1 - 100 of 124 matches
Mail list logo
