Arun Raghavan ford_pref...@gentoo.org said:
On 22 June 2010 00:40, Mark Loeser halc...@gentoo.org wrote:
Its quite simple. I want to get innovation starting in Gentoo again. I
am tired of seeing pointless arguments and threads that don't actually
make Gentoo any better. Improving QA
it. In the meantime,
Petteri proposed a nice solution awhile back that would centralize this
so it is not a one-off hack. Here is a link to his original proposal:
http://archives.gentoo.org/gentoo-dev/msg_44d395a1b887468051a1e1c049e99ba3.xml
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo
comes up.
Could you please give a description as to when you believe this function
should be used. Preferably as a patch for devmanual :)
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
Arfrever Frehtes Taifersar Arahesis arfre...@gentoo.org said:
2010-07-05 20:00:11 Mark Loeser napisał(a):
Everyone else has already made valid points. I'm just picking this one
to reply to now. Please remove the colors you have added. If you need
a new function, say eqawarn, we should
at
all and the packages just left the tree.
--
Mark Loeser
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpXm4ASAsbex.pgp
Description: PGP signature
zmedico to commit the repoman change
to make sure LICENSE= in the virtual category.
Thanks,
[1] https://bugs.gentoo.org/show_bug.cgi?id=140180
--
Mark Loeser
email - halcy0n AT gentoo DOT org
web - http://www.halcy0n.com
pgpEHiB1YmrR7.pgp
Description: PGP signature
(Sorry for the spam g-dev, I forgot to send this to dev-announce as
well).
- Forwarded message from Mark Loeser [EMAIL PROTECTED] -
Date: Sun, 16 Dec 2007 20:03:39 -0500
From: Mark Loeser [EMAIL PROTECTED]
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] New-style virtuals
moving forward. I really don't want to be stuck with something
that is going to end up being a pain a year down the road.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgp5KMFB9dR0l.pgp
we should use instead? The reason for
the email is to figure out if what we have now is good enough, or if we
should switch to something else.
How does the glep intend to handle USE_EXPAND?
It doesn't say anything about them right now, but since you brought it
up...any ideas? :)
--
Mark Loeser
:)
The only benefit use.local.desc gives us is a fast way to list packages
using some flags, but that's unreliable at best. If needed such a list
could be autogenerated.
Completely agree.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web
this system to do that we can't do now? Is overriding the USE
flag with use.local.desc sufficient and we just need to document the
current solution properly?
Please...let me know how you feel about this.
http://dev.gentoo.org/~halcy0n/gleps/glep-0054.html
Thanks,
--
Mark Loeser
email
first sent it (as far as I know). I forgot to
change before resending. Thanks for reminding me.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpnYkNt4leuz.pgp
Description: PGP signature
on freetype does and what legal
implications disabling it can have.
Why can't this be done in use.local.desc?
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpty7jvR7m5f.pgp
Description: PGP
Ryan Hill [EMAIL PROTECTED] said:
Mark Loeser wrote:
Ryan Hill [EMAIL PROTECTED] said:
c) Allow flags from use.desc to also exist in use.local.desc. In the
case that a flag for a package exists in both, the use.local.desc
description overrides the use.desc one. This allows a more specific
the correct place to get
a discussion going on what should be mentioned when we change default
configurations if that is your intention.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
control.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpPXq07yrA1j.pgp
Description: PGP signature
to do with (just taking something random here) openmotif,
if someone wanted to come on board and maintain that, I'd certainly be
interested in mentoring them (same with anything that is lacking a
maintainer right now).
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark
, and wolf31o2
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpQD4IA7V1hk.pgp
Description: PGP signature
is a list of bugs...give us one document that we can
point to)
I can get it put into devmanual as soon as I can find the approved
authoritative source to base information off of.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http
to the previous policy with regard to changes.
Just to clarify slightly:
I won't be working on anything other than EAPI=0. Other people may be,
but the council said in the latest meeting that they feel we should get
EAPI=0 done before adding any new EAPIs to the tree.
--
Mark Loeser
email
things
without our knowledge. If we start supporting this across the board, I
can see bugs being filed when their patches break and they don't
understand what is happening.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web
It will be removed at the end of the month.
03 Apr 2008; Mark Loeser [EMAIL PROTECTED] package.mask:
mask dev-libs/swl due to dead upstream and not working properly; bug
#206163
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web
toying around with in my head. I'd love to get an actual team
set up so we can encourage users to help us get the information we need
in bugs so it is less work for us. Several other distributions have
such projects, so we have something we can use as a template.
--
Mark Loeser
email
# Mark Loeser [EMAIL PROTECTED] (21 May 2008)
# Dead upstream and not used by anything
# Masked for removal in 30 days
dev-cpp/libwrapiter
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
and innovative things. If you are also
sick of all of the politics and want to take the no bullshit approach,
that's what I want to try to achieve. We are all volunteers and there
is no reason to needlessly troll or bash other people's work.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email
I nominate:
dev-zero
dirtyepic
zmedico
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpjvCUmiFCFy.pgp
Description: PGP signature
is something that anyone can
do.
I'm hoping to work on it later this week. I have been getting
absolutely buried with projects at work recently, which has eaten up a
lot of my spare time.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web
our users don't
always provide useful reports, it seems like we are just shifting work
around.
Just my 2 cents,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpIGtI7janth.pgp
Description: PGP
Duncan [EMAIL PROTECTED] said:
Jim Ramsay [EMAIL PROTECTED] posted [EMAIL PROTECTED],
excerpted below, on Tue, 01 Jul 2008 11:29:56 -0400:
Mark Loeser [EMAIL PROTECTED] wrote:
Its a good idea, but since our users don't always provide useful
reports, it seems like we are just shifting
Łukasz Damentko [EMAIL PROTECTED] said:
Dear Gentoo Community,
Here are your verified and long-awaited results.
Gentoo Council for term 2008/2009 will be:
Donnie Berkholz (dberkholz)
Mark Loeser (Halcy0n)
Diego Petteno (Flameeyes)
Petteri Raty (Betelgeuse)
Luca Barbato (lu_zero
problems/troubles.
#gentoo-cpp
#gentoo-qa
#gentoo-toolchain
Thanks Robin,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpQFFdAQDCRS.pgp
Description: PGP signature
know.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpuLxRnl25xF.pgp
Description: PGP signature
to get
them retired. With that being said, I think the same technical issues
come into play here as with banning someone from Gentoo entirely.
I am not sure how we would be able to enforce this across the board for
forcefully retired developers.
--
Mark Loeser
email - halcy0n AT gentoo
prereleases, please do so in an overlay.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpCNR0gs9t8D.pgp
Description: PGP signature
-egory/package) in the Summary
field, so searching is easier.
jer added some good stuff up on the bug-wranglers page:
http://www.gentoo.org/proj/en/qa/bug-wranglers/index.xml#doc_chap4
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web
, or where obscure expertise is needed. Package
maintainers are encouraged to use discretion when removing ebuilds in
accordance with this policy.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
Jose Luis Rivero [EMAIL PROTECTED] said:
Mark Loeser wrote:
Removing Stable Ebuilds
If an ebuild meets the time criteria above, and there are no technical
issues
preventing stabilization, then the maintainer MAY choose to delete an
older
version even if it is the most recent stable
? Do you see anyway to resolve the issue you see with us having a
wiki?
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpR4907laveX.pgp
Description: PGP signature
working directory
http://archives.gentoo.org/gentoo-dev/msg_5ba467bbd5a0820e040210683702a67f.xml
Ditto.
* RFC: DEFINED_PHASES magic metadata variable
http://archives.gentoo.org/gentoo-dev/msg_8c34d8efbc0d31ab28c517403dc83f62.xml
Same.
--
Mark Loeser
email - halcy0n AT gentoo DOT
would be that if you don't want to see them to set up a filter.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpgZsS26DXRH.pgp
Description: PGP signature
Since we currently have language herds for other languages such as Ada,
Perl, and Java, I don't think C++ should be any different. There are
currently many packages in the tree that are C++ libraries or utilities
that are no-herd and are actively maintained, and there are probably
some that have
Kevin F. Quinn wrote:
I would also like to see many of them, if not all, moved to the dev-cpp
category:
Is this bit really necessary?
The reason for me adding that bit is the metadata from dev-cpp:
The dev-cpp category contains libraries and utilities relevant to the
c++ programming
Mike Frysinger wrote:
On Saturday 17 September 2005 02:22 pm, Mark Loeser wrote:
The reason for me adding that bit is the metadata from dev-cpp:
The dev-cpp category contains libraries and utilities relevant to the
c++ programming language.
Now to me, that means I can find *all* relevant C
Paul de Vrieze wrote:
I think that dev-util is a very specific category containing development
utilities of some sort. There might be some misclassifications in them,
but from a user perspective I don't really care about the language
anything is written in. As C++ is so widespread I don't
I'm masking app-arch/gzip-x86 as we speak. It seems to cause problems
for people[1] and is based off of gzip-1.3.3. As such, it is vulnerable
to a couple[2] exploits[3]. Upstream appears dead (last update was
2003-05-20) and no one is currently maintaining it for us. If you don't
want to see it
Ciaran McCreesh wrote:
On Thu, 22 Sep 2005 18:36:18 -0400 Mark Loeser [EMAIL PROTECTED]
wrote:
| I'm sending this email because I have seen some packages marked stable
| on x86 without the permission of the x86 team, and would like the
| people who can mark stable for x86 to contact us
Simon Strandman wrote:
I'm curious why --as-needed is disabled for glibc builds. It was first
added over a year ago in one of the early 2.3.4 builds so is it still
nessecary?
I tried removing it and had no problems building glibc and I could see
that it was used when looking at the compile
Jakub Moc [EMAIL PROTECTED] said:
You can do whatever you like. Nobody is forcing you to do anything.
That being said, you are not going to force *me* to do anything, either.
Hmm, have I missed an argument here? Actually, the above is incorrect. You
*are* forcing me to use stage3, but
If no one steps up to maintain it, luabind will be removed from the tree in 2
weeks. It has not had an upstream release since 2003 and is broken with
newer versions of boost, =1.32. Nothing in the tree deps on it, so there
shouldn't be any problems with its removal.
Thanks,
Mark
Ned Ludd [EMAIL PROTECTED] said:
I really can't give an accurate example. Halcyon who has been testing it
merged world and he was yeilded with 18M of debug info (I have no idea
how many packages he has).
Just for the sake of reference, this was with 95 packages and CFLAGS=-O2
-march=pentium4
This is basically a heads-up email to everyone to say that we are probably
going to be moving gcc-3.4.4-r1 to stable on x86 very soon. If any of the
archs that have already done the move from having 3.3 stable to 3.4 could
give us a heads up on what to expect, that would be great. Only thing I
, libstdc++-v3 should be pulled in
after that. Only issue I really see is people that have libraries compiled
with 3.3 and 3.4 and don't know why stuff is broken. I don't know how large
of a problem that will be though.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email
.
--
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
pgpgktGju3Vxt.pgp
Description: PGP signature
Mark Loeser [EMAIL PROTECTED] said:
Only thing I see
as lacking is we might want to get a doc together on how to properly upgrade
your toolchain so we don't get an influx of bugs from users that have a
system half compiled with 3.3 and the other half with 3.4 so they get linking
errors
after merging it. The
old gcc profile is still valid, therefore it is kept. Users have to
consciously go and change their profile to change their gcc, so nothing is
going to just magically break.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n
at.
--
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
pgpzZTFpcaErN.pgp
Description: PGP signature
://bugs.gentoo.org/show_bug.cgi?id=102876
I'm hoping we can get something thrown together relatively quickly so I can
mark it stable. Nothing is going to be required immediately from the user
though, since their compiler won't be changed to 3.4 until they do so.
--
Mark Loeser - Gentoo Developer (cpp gcc
64615.
Yea, I updated my statement on the bug to reflect this. C++ stuff should be
the only thing affected, so this _should_ be enough. Its also already
something that's been in the ebuild for a while now.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email
for it to get all of the mirrors, which will take a bit
longer after that.
[1] http://www.gentoo.org/proj/en/base/x86/gcc-upgrading-guide.xml
[2] https://bugs.gentoo.org
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
. This should be added to existing documentation
policy so it is somewhere for new devs to know about, and existing devs to
have for a reference.
Thanks
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n
deemed stable.
--
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
pgpqnl9LWsDn7.pgp
Description: PGP
personally. The issues listed don't seem
to warrant that.
--
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
Mike Frysinger [EMAIL PROTECTED] said:
On Tue, Dec 13, 2005 at 08:02:27PM -0500, Mark Loeser wrote:
You are working on a policy, or just docs to explain the issues?
documentation on PIC/TEXTRELs/etc...
the policy i consider a no-brainer, fix TEXTRELs
By policy, I mean things to add
.
Yea, we need to know what is absolutely critical so we can add this to the
ebuild policy if something should not go stable if the problem is present.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n
or such set correctly, you will be able to easily sort. Adding
additional headers to the emails is really trivial if we need something else
to make our lives easier.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
the sys-libs/libstdc++-v3 depend into your package 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/~halcy0n/
http
Mark Loeser [EMAIL PROTECTED] said:
So, everyone that has a binary package in the tree, I would appreciate it if
you could put the sys-libs/libstdc++-v3 depend into your package if
necessary.
Well, you can tell I didn't exactly think about this too much beforehand,
since its been brought to my
.
Betelgeuse is working on a repoman check for this issue, meanwhile, if there
are more virtuals planned, please bear this in mind. :)
It makes no sense to make a check to verify what seems to be broken
behaviour. The virtuals should be like any other ebuild in the tree.
--
Mark Loeser - Gentoo
::Tk, placed on CPAN, similar to
perl/Tk, small and easy.
I'll do all needed work myself.
Could you please advice whom to contact? Where is FAQ for me to read?
File a bug about this as well :)
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n
#116253 was invalid due to the user's package.keywords.
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
Mark Loeser [EMAIL PROTECTED] said:
Mark Loeser [EMAIL PROTECTED] said:
So, everyone that has a binary package in the tree, I would appreciate it if
you could put the sys-libs/libstdc++-v3 depend into your package if
necessary.
Well, you can tell I didn't exactly think about this too
Bjarke Istrup Pedersen [EMAIL PROTECTED] said:
Does this mean that gcc-3.4 will no longer have libstdc++ as a
dependency? :-D
That is what I hope to accomplish, yes.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
, and I could step
back up and start to do some of the work I used to do for GCC releases.
I'll talk with Mike to figure out how we can best split up the work.
Thanks for all your work on the releases,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n
/${MY_PN:0:1}/${MY_PN}/${MY_P}.zip
LICENSE=ZPL
SLOT=0
KEYWORDS=~alpha ~amd64 ~sparc ~x86
IUSE=
Did you actually test this package on all of these archs?
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http
Arfrever Frehtes Taifersar Arahesis (arfrever) arfre...@gentoo.org said:
arfrever10/09/12 20:43:13
Removed: pygtkhelpers-0.4.1.ebuild
Log:
Delete older ebuild.
Please update the Changelog when you remove versions of the package.
--
Mark Loeser
email
of python.eclass in EAPI=\${EAPI}\ not established
fi
The attached patch could be applied if EAPI=4 doesn't contain support for
. in IUSE.
Should I apply this patch now?
No, you should remove anything that relates to EAPI 4. Please do so as
soon as possible.
Thanks,
--
Mark Loeser
email
in the first
place? ;-)
Because it is not pointless. Useful commit messages save lots of time.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
signature.asc
Description: Digital signature
use it.
So do me a favor, remove it proactively if you really want to have it gone.
Please do remove the flag. The fact that there are some ebuilds in the
tree that use it does not make it alright to introduce more.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email
?
Seems valid. It was added and removed shortly after:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-libs/libresample/?hideattic=0
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
those services.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
signature.asc
Description: Digital signature
, please do document it in the ChangeLog.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
signature.asc
Description: Digital signature
Samuli Suominen ssuomi...@gentoo.org said:
On 04/29/2011 09:26 PM, Mark Loeser wrote:
Samuli Suominen (ssuominen) ssuomi...@gentoo.org said:
ssuominen11/04/29 18:13:31
Removed: transmission-2.12.ebuild
Log:
drop old, broken with stable libnotify
as one commit and run repoman with
each commit.
Thanks,
--
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's just pointless.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
signature.asc
Description: Digital signature
the
time of having to support something that might just become a problem to
maintain in the future?
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
signature.asc
Description: Digital signature
upstreams are dead and some packages using PyXML will never be ported by
upstreams to use
something else than PyXML (e.g. lxml).
Then those packages should get removed from the tree. Do not start
introducing Gentoo specific hacks to work around the problem.
--
Mark Loeser
email
.
Having an 'eapi' file present seems workable as well, though I'm not
certain which is the easiest for Portage to implement today.
Are there any other suggestions, or does anyone disagree with Ulrich's
suggestion?
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark
was instructed to enforce the policy
Please actually check the full commit. He did update the ChangeLog, but
due to how these emails are sent out, they don't always come as a full
changeset.
Thanks,
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
out the discussion on
https://bugs.gentoo.org/show_bug.cgi?id=279206
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
signature.asc
Description: Digital signature
pygobject-2's internal gi).
I'd recommend you open a tracker bug for this porting effort. No one is
going to be able to follow exactly what has been done via the mailing
list :)
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web
101 - 190 of 190 matches
Mail list logo
