like to know of everything that
is broken.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
please, its much easier.
I'm wondering if a gcc4 tracker bug might help as Mark was planning to move it
in ~arch.
Sounds like a good idea. I'll probably make one in a bit if someone doesn't
beat me to it.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email
projects are active and reporting information on their status.
Sounds good as well. I'd like to see all of the projects/teams saying what
their goals are, or what they have done to move towards their goals.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email
Lance Albertson [EMAIL PROTECTED] said:
Mark Loeser wrote:
Chris Gianelloni [EMAIL PROTECTED] said:
I completely agree with you here. What Gentoo does is make a
meta-distribution, that one can utilize to build their own distribution
easily. This isn't limited to Linux, either, thanks
to either make repoman not complain if HOMEPAGE= is supposed
to be valid, or put none in there if necessary.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org
that debugging almost works for hardened users too.
Please lets avoid this assumption. I'd love to make it so we never make this
assumption anywhere in the tree so that we could actually build GCC without
pie or ssp, instead of generating all of the GCC profiles for every user.
--
Mark Loeser
. Knowing that 800 packages are broken, and going to unmask it
knowing that just doesn't seem acceptable in my eyes. ~arch isn't meant to
be things are known to be broken. It's meant to mean, we think all of this
is ready to be stable, which it certainly won't be in this case.
Thanks,
--
Mark
, but we can wait
until its down to a more reasonable value. This huge push to get everything
ported over only started recently, and I think we need more time.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark
? It makes things a pain for arch
teams that are trying to mark a completely unrelated version of the package.
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http
open about this
package right now, and having an error about deps in some old version doesn't
really help arch teams at all.
I am all for getting stuff ported, but making things harder for arch teams is
not the way to go about it.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain
Jason Stubbs [EMAIL PROTECTED] said:
On Wednesday 01 February 2006 02:28, Mark Loeser wrote:
We are talking about completely unrelated versions, not what we are
touching.
For example, old imagemagick ebuilds sitting around, where the newer ebuilds
are fixed, but old ones are not. We
it.
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpdH6MEmUfuw.pgp
Description: PGP signature
gcc-3.3 or libstdc++-v3. I don't see forcing either upon our
users to be a good thing. The upgrade doc covers how to do the 3.3-3.4
upgrade, and I think most archs are on 3.4 at this point.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo
Jason Stubbs [EMAIL PROTECTED] said:
On Thursday 09 February 2006 09:30, Mark Loeser wrote:
Jason Stubbs [EMAIL PROTECTED] said:
It was my understanding that it is needed for the 3.3 - 3.4 upgrade.
Various packages that will build fine against either are broken until
being recompiled
it be acceptable?
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpmrmdUiVjvE.pgp
Description: PGP
, we should decide if this is valid though. I haven't
exactly been convinced that it is useful, but I'm not opposed to the idea.
I'd just like to see a decision one way or another.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
out for?
I don't see this as a groundbreaking change that requires a GLEP or anything,
especially since I eliminated most of the duplicates today, after talking
with the respective maintainers. There are probably only 3 or 4 left.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa
R Hill [EMAIL PROTECTED] said:
Anyways I just like anything that makes use.desc more useful than
foo - adds support for foo
That's really a completely separate issue. By allowing duplicate entries we
just allow people to put useless information in two places instead of one.
--
Mark Loeser
The package has been in package.mask since July 2002. Upstream appears dead.
If no one objects, I will drop it from the tree in a week (since it has
already been masked for years anyway :) ).
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n
will be presented with this request to
devrel.
* The QA team will maintain a list of current QA Standards. The list
is not meant by any means to be a comprehensive document, but rather a
dynamic document that will be updated as new problems are discovered.
--
Mark Loeser - Gentoo Developer (cpp
to the
council about one of our changes. Also, we aren't unwilling to hear
alternatives and we hope to work with the maintainer on these problems.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n
prove to be impossible.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpL6u3xmZeKv.pgp
Stuart Herbert [EMAIL PROTECTED] said:
On Sun, 2006-02-26 at 17:22 -0500, Mark Loeser wrote:
* In case of emergency, or if package maintainers refuse to cooperate,
the QA team may take action themselves to fix the problem.
I'd like to see this say
* In case of emergency, or after
Donnie Berkholz [EMAIL PROTECTED] said:
Mark Loeser wrote:
Well, instead of putting the debate into an even larger crowd, this
enables the QA team to act in the way it sees best first. If people
believe we were wrong, then we give them the option to talk to the
council about one of our
Ciaran McCreesh [EMAIL PROTECTED] said:
On Sun, 26 Feb 2006 17:22:17 -0500 Mark Loeser [EMAIL PROTECTED]
wrote:
| * The QA team will maintain a list of current QA Standards. The
| list is not meant by any means to be a comprehensive document, but
| rather a dynamic document
.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgp8iRpskxJ5q.pgp
Description: PGP signature
Grant Goodyear [EMAIL PROTECTED] said:
Mark Loeser wrote:
* In case of emergency, or if package maintainers refuse to cooperate,
the QA team may take action themselves to fix the problem.
My suspicion is that the more common problem is going to be inaccessible
developers, rather than
involved
every single time someone has a disagreement. This situation has
obviously grown to be ridiculous and I have had a talk with him about
it, so he knows my feelings on the situation, and what I expect.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email
everything fixed up that we can.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
, not that I expect QA team
members to behave that way.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
all of the debate out of the way now.
Please lets keep the discussion on topic and constructive.
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http
Alec Warner [EMAIL PROTECTED] said:
Mark Loeser wrote:
Here is my updated version after some feedback from people:
* In the case of disagreement on policy among QA members, the majority
of established QA members must agree with the action.
What is an Established QA member?
Listed
the perfect solution right away and
that flexibility is required.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http
the QA team and
the maintainer. In situations where we can't figure out how to best
address the situation, opening the discussion up to -dev may help, but
in the end it should come down to an agreement between the maintainer
and the team.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa
we would like to see fixed.
They are there to make readability across ebuilds easier since
everything will be formatted the same way for a developer to see.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark
is saying that we shouldn't fix things to
adhere to coding standards. We are just saying it is not a, OMG you
broke it! problem. It is about appropriate responses to the problems
we encounter.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo
about your original draft:
I never said it was different. I said I added some things based on
feedback I got. As I said in the last thread, I disagree with many of
the things you have come up with. You are free to try and convince me
otherwise.
--
Mark Loeser - Gentoo Developer (cpp gcc
a better solution
somewhere in the long-term.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
the build/deptree phase and more
warnings/information to be presented so the user could look at it and
make changes, or just accept what we have done for them.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark
of the packages if no maintainer can be found
to step up. So, is anyone willing to do so?
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n
saying we need someone to
maintain them, and see what happens. You can put me down as the contact on
the staffing-needs page if you want. I hate to see things that are useful
to our users taken from the tree, but there isn't much we can do when
there is no one to maintain them.
--
Mark Loeser
should be
removed so quickly?
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpzdTXfIbhxx.pgp
it in 30 days.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpRW5G91lZr8.pgp
Description
Carsten Lohrke [EMAIL PROTECTED] said:
On Thursday 30 March 2006 01:55, Mark Loeser wrote:
Not directed specifically at you, but it seems a lot of people are
masking stuff and removing it very quickly, and I'd really like to see
everyone wait the 30 days to remove something from the tree
/whatever policy. Lets keep that out of a document like
this and decide on that through the appropriate channels.
If those last two paragraphs are cut, I'm quite happy with it, even if
it isn't all true right now, and is something we should strive towards
doing.
--
Mark Loeser - Gentoo Developer
... Things should only go to the council when all other methods
fail, and they are the only ones you can appeal to.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http
really seems to know how we worked, and were surprised that we
are entirely volunteer based and don't get paid. They seemed to respect
us even more once they heard about that. The people that walked up to us
and just told us, You guys rock! were awesome too :)
Just my two cents, :)
--
Mark Loeser
There has been no upstream release in years, and the download URLs no
longer work. It also has some open bugs (bug #127131). If anyone
wishes to step up and maintain this, please do so within the next 30
days, or I am removing it from the tree.
Thanks,
--
Mark Loeser - Gentoo Developer
dev-util/ is not depended on by any other applications, the stable
version does not compile, and while upstream has newer releases which most
likely work...there is no Gentoo maintainer (bug #128109). If no one steps
up to maintain it in 30 days, I will be removing it.
--
Mark Loeser
to claim responsibility for the package when there
is a problem.
Just my 2 cents,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n
.
* QA will take an active role in cleaning up unmaintained and broken
packages from the tree. It is also encouraged of members of the QA team to
assist in mentoring new developers that wish to take over unmaintained
packages/herds.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa
Daniel Goller [EMAIL PROTECTED] said:
Mark Loeser wrote:
Here is the newest revision of my proposal. Not much has changed, but I
added and changed some small things. Constructive feedback is
appreciated. I'd like to get this voted on by the council at the next
meeting.
* The QA
Mark Loeser [EMAIL PROTECTED] said:
Daniel Goller [EMAIL PROTECTED] said:
Mark Loeser wrote:
Here is the newest revision of my proposal. Not much has changed, but I
added and changed some small things. Constructive feedback is
appreciated. I'd like to get this voted
, it is just the
wording that threw you off :) I mean that it can never be complete, so
don't think it ever is.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http
Duncan [EMAIL PROTECTED] said:
Mark Loeser posted [EMAIL PROTECTED], excerpted
below, on Mon, 24 Apr 2006 09:11:28 -0400:
* QA will take an active role in cleaning up unmaintained and broken
packages from the tree. It is also encouraged of members of the QA
team to assist
And now in GLEP format for those who like that sort of thing :)
http://www.gentoo.org/proj/en/glep/glep-0048.html
I made the two wording changes so it is more clear what I wanted to
communicate.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n
why we want to
try and change that to something else, even if that was what it was
supposed to mean to begin with.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http
think this is a good idea. We have some items on there that are years
old, and it would be good to even update the requested date on them so
that people know the requests are still valid.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo
.html
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgp7vJhlFQUYZ.pgp
Description: PGP signature
, and this sounds
like it would fill that void.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
for the bug and file it upstream. The only
bugs I've marked invalid are for the testing versions of GCC.
But, this is entirely off topic.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web
not add anything else to the tree
for the sole reason of supporting another package manager's features.
This includes profiles or any other packages. This will reduce
headaches for all of us, and hopefully cut down on needless arguments
that get us no where.
Thanks,
--
Mark Loeser - Gentoo
to proceed in handling situations like this.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
This package is currently without a maintainer and has open QA issues;
bug #123708. It was marked as testing on every arch without being
tested and could really use someone to clean it up. It will be booted
in 30 days if no one wants to keep it around.
Thanks,
--
Mark Loeser - Gentoo
to fix all of these issues.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpit1oZsBFqk.pgp
:)
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpI9MDgupHFZ.pgp
Description: PGP
Upstream's last release for this package was in 2002, it doesn't compile
with gcc-3.4 (bug #120303), and hasn't had a maintainer for a long time.
Unless someone steps up to fix up this package, it will be punted in 30
days.
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa
to maintain them.
Comments on this idea are appreciated. I wouldn't mind helping write it
and maintain it, but having interest and support in doing something like
this is definately going to be needed :)
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n
Alec Warner [EMAIL PROTECTED] said:
I propose a new QA subproject, the TreeCleaners.
Questions and Comments are welcome, as always.
This has my support. Hopefully it will help us get rid of a lot of
cruft that hasn't been touched in ages and doesn't even work.
Thanks,
--
Mark Loeser
.
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpOD1VY3Mhq5.pgp
Description: PGP
scratch?
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpUGXMzGTQ7a.pgp
Description: PGP signature
are doing it right:
http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLIBVARIABLESTATEINFORMATION
I guess what I would really like to know is...why does it matter? If
something is configurable like that, then it should work regardless of
what is put in.
--
Mark Loeser
email - halcy0n
having to work on other
things right now, so I have to decline. Maybe the next time around.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpZqzOCwvr1q.pgp
Description: PGP signature
/gentoo-
x86/profiles/base/use.defaults?r1=1.1r2=1.1.1.1
That is on a different branch and is incredibly old. To make a long
story short...someone screwed up and created their own branch of the
whole tree. It isn't actually being used.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
contributed and helped already,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpTWFS2O2djB.pgp
Description: PGP signature
file any bugs you find to toolchain.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpJWhiHk4CzC.pgp
Description: PGP signature
,
because its going to break in a week. He doesn't maintain the package,
do you? If so, then please send the bug report upstream and become the
maintainer of this package if you want to keep it around.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark
this be on our official overlays? Is there a technical
reason, because we seem to just be spreading things out even more than
necessary.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpcnAKKm9Mwb.pgp
. There is absolutely no benefit to moving it to
stable.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpBOqjpyzWlZ.pgp
Description: PGP signature
based apps just like it's done with gcc
stabilization.
And you are mixing that up. We never mark GCC stable before we fix
everything we have identified as a problem, or pretty close to
everything.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT
absolutely
great, but every single application that links to libfoo now breaks with
the new release of libfoo-2.0. The things that use your package are
just as important when looking to stablize something or to move it out
of package.mask.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
should change.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpX2U6V4nQow.pgp
Description: PGP signature
to QA standards. Its really that simple. Don't be lazy and do things
the right way, or don't do them at all.
Kthxbai,
Also, please learn how to communicate in a manner that is constructive
instead of acting like a dick at every opportunity.
--
Mark Loeser
email - halcy0n AT gentoo
Ben de Groot yng...@gentoo.org said:
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
zcav || die emake zcav failed # see #9073
}
src_install() {
dosbin bonnie++ zcav || die
dobin bon_csv2html bon_csv2txt || die
doman bon_csv2html.1 bon_csv2txt.1 bonnie++.8 zcav.8
dohtml readme.html
dodoc changelog.txt credits.txt
}
--
Mark Loeser
email
to follow
a huge metabug with a bunch of packages listed in it. Also, I think the
concerns and suggestions that were brought up about the syntax of this
new variable should be addressed first and not ignored.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark
to know why we need about 150
different profiles for MIPS...
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
this role
instead of polluting bugzie with more keywords. I'm not really attached
to one approach over the other, but atleast this little site gives the
users one place to have to check for things and we can categorize them
easily.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email
issues. If we can't get
enough developers to participate then we should just stop trying to do
it instead of putting on such a poor showing.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
possible new developers.
I think if we can get a few devs and possibly some users together
to organize this in a better way, this could be useful. But if things
are to stay the way they are, then we better stop pretending.
I couldn't agree more.
--
Mark Loeser
email - halcy0n AT gentoo
distributions out there.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
should only be used in circumstances where it is
the only option. Breaking deps for an arch is not what it is intended
for.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
is vulnerable via multiple bundled libs and therefore shouldn't
be in the tree. You can apply the patches if you want to keep it and
remove the mask at that time.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http
, gcc
works just fine, but it can't compile half of the tree.
I hope everyone can see that this is a terrible idea and of no use to
our stable users. If a stable user really needs Python-3, they will
have the technical ability to unmask it and use it properly.
--
Mark Loeser
email
in reference to? Its not at all clear what you are
trying to do.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
signature.asc
Description: Digital signature
that we don't have enough active developers,
which is the real problem.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
signature.asc
Description: Digital signature
, and
whatever ad serving might leak thru, and object to having a gmail account
on principle?
Then they don't get to see the calendar
Seriously though, who cares. If it becomes a problem, we can deal with
it then. Until that point, use what we have or implement something
that's better.
--
Mark Loeser
getting it
to a state that it will be unmasked.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
signature.asc
Description: Digital signature
to the gentoo-dev mailing list. If you
were nominated and want to run, you have to accept your nomination on
the same mailing list.
I'll nominate flameeyes and halcy0n.
Thanks,
I accept.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web
as a whole, are all things that the Council should be
taking an active role in, and I want to be a part of making that happen.
I told you it was going to be short :)
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web
1 - 100 of 190 matches
Mail list logo
