Hi,
please be careful when assigning new bugs. Today I changed several
bugs where the wrong maintainer was used or where the main maintainer
has been forgotten. This only occured since we have no full-time
bug-wrangler anymore. Was anyone successful to contact him, yet?
V-Li
--
Christian Fau
On Mon, 2008-05-12 at 10:20 +0200, Christian Faulhammer wrote:
> Hi,
>
> please be careful when assigning new bugs. Today I changed several
> bugs where the wrong maintainer was used or where the main maintainer
> has been forgotten. This only occured since we have no full-time
> bug-wrangler a
On Mon, May 12, 2008 at 2:10 PM, Ferris McCormick <[EMAIL PROTECTED]> wrote:
> This only occured since we have no full-time
> > bug-wrangler anymore. Was anyone successful to contact him, yet?
> I am told he should be back sometime soon, like today. Apparently
> someone is in contact with him
Denis Dupeyron schrieb:
That he comes back or not is of no importance to bug wrangling. Or at
least it should be. It is a mistake to solely rely on a developer for
such a task. Developers come and go without warning, he just proved
it, so ideally we need a team of 2 or 3 to handle bug wrangling.
Denis Dupeyron <[EMAIL PROTECTED]> said:
> That he comes back or not is of no importance to bug wrangling. Or at
> least it should be. It is a mistake to solely rely on a developer for
> such a task. Developers come and go without warning, he just proved
> it, so ideally we need a team of 2 or 3 to
Markus Meier wrote:
qt3support: Enable the Qt3Support libraries for Qt4
While it affects a few "packages", they all are parts of the Qt toolkit
(which we previously shipped in one big package). I can't see a scenario
where this flag might be used on a package not released by Trolltech.
Chee
Hello *,
Many packages have documentation in LaTeX, and latex is being run (often
when USE=doc). This may cause a sandbox violation, if a font not yet
generated on this particular computer is encountered: latex calls metafont
to generate it, and metafont wants to write it to /var/cache/fonts (
Jan Kundr?t wrote:
Markus Meier wrote:
> qt3support: Enable the Qt3Support libraries for Qt4
While it affects a few "packages", they all are parts of the Qt toolkit (which
we
previously shipped in one big package). I can't see a scenario where this flag
might be
used on a package not released b
Andrey Grozin wrote:
sci-visualization/qtiplot, for example
I don't see a reference to the "qt3support" flag in any of qtiplot
ebuilds, could you please clarify what you mean?
Cheers,
-jkt
--
cd /local/pub && more beer > /dev/mouth
signature.asc
Description: OpenPGP digital signature
Jan Kundr?t wrote:
I don't see a reference to the "qt3support" flag in any of qtiplot
ebuilds, could you please clarify what you mean?
I see, this thing has disappeared in recent versions... Sorry.
There was a period when qtiplot required qt4 emerged with qt3support USE
flag. So, it had pkg_se
Andrey Grozin wrote:
There was a period when qtiplot required qt4 emerged with qt3support USE
flag. So, it had pkg_setup which checked this and produced an error it
necessary.
Ah, that's quite common -- a package FooBar is ported to Qt4, but it
still uses some of the Qt4's Qt3support classes.
Hi,
> There are two methods commonly used to fight against this situation
> in ebuilds: using addwrite or setting VARTEXFONTS="${T}/fonts". The
> second method is, probably, better.
Packages should definitely go for the VARTEXFONTS one as I'll probably
drop forced global writable /var/cache/fonts
Markus Ullmann <[EMAIL PROTECTED]> posted [EMAIL PROTECTED],
excerpted below, on Mon, 12 May 2008 15:49:30 +0200:
> Fully with you, yet the other people who do bug wrangling occasionally
> didn't do it as good as him mainly because he followed all major
> mailinglists and knew the common issues a
Mark Loeser wrote:
> Making an actual bug wrangling team (subproject of QA) is something
> I've been 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 distribut
Matthias Schwarzott wrote:
> Well, you want it compact, without loops.
> Here is it:
>
> set -- /usr/bin/gcc-3*
> Get first entry: CC="$1"
> Get last entry: eval CC="\${$#}"
>
Nice one, yeah I thought : splitting was posix silly me ;)
I still shy clear of eval for general use and you have to go t
Steve Long a écrit :
Mark Loeser wrote:
Making an actual bug wrangling team (subproject of QA) is something
I've been 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
Hello,
I guess I am tired of fighting with people here. I am too old for this crap.
There are few brutal developers here that make Gentoo a terrible place
to be. Well... I can handle few developers, but when devrel enters the
picture with arguments such as "volunteers can do crappy job as long
as
On 08:03 Tue 13 May , Rémi Cardona wrote:
> We all know which devs/herds bugs should be assigned to, we all know most
> bugs aren't complete if emerge --info is not provided, that sort of things.
> But Real Bug Masters (tm) know all the dupes, know all the current problems
> in our various t
18 matches
Mail list logo
