On 2015-02-12 13:52, Luca Falavigna wrote:
> Hi,
>
> 2015-02-11 20:46 GMT+01:00 Peter Palfrader :
>> It seems the buildd team is severely understaffed and needs help.
>
> If this rumor turns to be a reality, are there some prerequisites
> potential volunteers could have a look to in the event the
On 2015-02-12 22:18, Philipp Kern wrote:
> On 2015-02-12 13:02, Holger Levsen wrote:
>>> Possible avenues include updating the forks and working on making the
>>> forks
>>> no longer necessary.
>> are these forks maintained in VCSs?
>
> http://anonscm.debian.org/cgit/buildd-tools/sbuild.git/log/?h
On 2015-02-12 13:02, Holger Levsen wrote:
Possible avenues include updating the forks and working on making the
forks
no longer necessary.
are these forks maintained in VCSs?
http://anonscm.debian.org/cgit/buildd-tools/sbuild.git/log/?h=buildd-0.64
Historically forks have been needed because
Hi,
2015-02-11 20:46 GMT+01:00 Peter Palfrader :
> It seems the buildd team is severely understaffed and needs help.
If this rumor turns to be a reality, are there some prerequisites
potential volunteers could have a look to in the event they want to
apply for the role?
Cheers,
Luca
--
To UNS
Hi,
On Mittwoch, 11. Februar 2015, Peter Palfrader wrote:
> The Debian buildd network uses a fork of the buildd and sbuild packages
> instead of the packages we ship in the archive.
are the bugs about these issues?
> These packages, maintained by the builddadm team are shipped via
> buildd.debia
Hi,
DSA is concerned about the current state of our buildd's readyness for jessie.
The Debian buildd network uses a fork of the buildd and sbuild packages instead
of the packages we ship in the archive. The reasons why we are still doing
that are not entirely clear, but that's the status quo.
T
6 matches
Mail list logo
