Goswin von Brederlow <[EMAIL PROTECTED]> writes:
> Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
>
>> How about making porters responsible for running the buildds for their
>> arch?
>
> I consider anyone who runs a buildd for an arch a porter already so
> that is already there.
If they are unwi
On Thu, Dec 08, 2005 at 03:58:09PM -0500, Nathanael Nerode wrote:
> Erm, I just realized that if requeued eris will build against the misnamed
> version of atlas-cpp. Should wait for a fixed source version of atlas-cpp.
Which isn't RC; so I'm going to go ahead and requeue eris after all.
--
Ste
Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
> How about making porters responsible for running the buildds for their
> arch?
I consider anyone who runs a buildd for an arch a porter already so
that is already there.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a s
Nathanael Nerode wrote:
> Perhaps, since this is a matter of library transitioning, some Debian
> developer on this list would take pity on him and sponsor it?
> The C++ transition is very nearly complete for libraries, so I'm hoping
> we can finish off the last four.
Did you ask Florian Ragwitz a
Fathi Boudra <[EMAIL PROTECTED]> is trying to adopt log4cpp, and has an
upload prepared which will make this library undergo the C++ transition.
He's been waiting for a sponsor since late October. See bug 303794
Perhaps, since this is a matter of library transitioning, some Debian
developer on th
Erm, I just realized that if requeued eris will build against the misnamed
version of atlas-cpp. Should wait for a fixed source version of atlas-cpp.
--
Nathanael Nerode <[EMAIL PROTECTED]>
"(Instead, we front-load the flamewars and grudges in
the interest of efficiency.)" --Steve Lanagasek,
h
Eris built against the busted version of libwfmath.
It needs to be requeued everywhere.
--
Nathanael Nerode <[EMAIL PROTECTED]>
[Insert famous quote here]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Goswin von Brederlow <[EMAIL PROTECTED]> writes:
> Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
>
>> Steve Langasek <[EMAIL PROTECTED]> writes:
>>
>>> No, buildd admins are responsible for fixing buildd problems. *Porters* are
>>> responsible for *ensuring their port is a viable release candid
Hi,
The gav package I maintain requires a rebuild on all architectures,
since it currently depends on libstdc++5. No source changes are required
to bring it up to date with g++ 4.0.
Thanks,
Ari Pollak
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contac
Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
> Steve Langasek <[EMAIL PROTECTED]> writes:
>
>> No, buildd admins are responsible for fixing buildd problems. *Porters* are
>> responsible for *ensuring their port is a viable release candidate*. Given
>> that one of the release criteria is "keep
10 matches
Mail list logo