I would suggest joining the Debian games team, committing the package
to our SVN repository and maintaining it there. If you are willing to
join the team, please check out our wiki pages, jump on our IRC
channel, introduce yourself and we will give you a run-down of how the
team works:
http://wiki
On Sat, 2 Apr 2011 21:59:59 -0700
Vincent Cheng wrote:
> Dear mentors,
Not sure if all the CCs are required, so preserving them.
> I am looking for a sponsor for my package "0ad".
>
> * Package name: 0ad
> Version : 0~r09049~alpha4-1
> Upstream Author : Wildfire Games
> * URL
Hi Vincent,
(CCing you since I'm not sure which lists you are on if any, sorry for
any duplicate mail)
Looks like you are taking over the ITPs owned by Bertrand Marc, with
his permission.
Bertrand was maintaining the packaging in the games team's SVN
repository, but you don't seem to have update
Dear mentors,
I am looking for a sponsor for my package "0ad".
* Package name: 0ad
Version : 0~r09049~alpha4-1
Upstream Author : Wildfire Games
* URL : http://wildfiregames.com/0ad/
* License : GPL, LGPL, MIT
Programming Lang: C++
Description : 3D real-
Den 02. april 2011 23:16, skrev Stephen Kitt:
> The first strategy would allow the packages to make their way into the
> archive sooner, but I'm not sure what the FTP Masters' reaction would be to a
> NEW package relying on an "Arch: all" package to avoid bootstrapping itself.
They might be unders
Dear mentors,
I am looking for a sponsor for my package "plowshare".
* Package name: plowshare
Version : 0.9.5~r1411-1
Upstream Author : Arnau Sanchez
Matthieu Crapet
* URL : http://code.google.com/p/plowshare/
* License : GPL-3+
Section
On Thu, Mar 31, 2011 at 4:44 AM, Bill Johnstone wrote:
> Hello all.
>
> I'm a novice at building Debian packages, but following the New
> Maintainers' Guide, I've been able to successfully use dh_make, quilt, and
> dpkg-buildpackage to make proper packages.
>
> I now need to build some out-of-tree
On Sat, 02 Apr 2011 19:18:26 +0200, Ove Kåven wrote:
> Den 29. mars 2011 01:08, skrev Stephen Kitt:
> > In order to upload to Debian, it would theoretically be
> > possible to upload mingw-w64 since it's "Arch: all", then upload the full
> > gcc-mingw-w64 without bootstrapping. Alternatively, boot
On Sat, 2011-04-02 at 10:43 +0200, Niels Thykier wrote:
> Generally the diff ought not to include ".gitmodules" in the first place
> if you did not intend for it (and the 7 other files) to be there.
> Most likely dpkg-source/dpkg-buildpackage with -i is not enough in
> this case. I believe [1] w
Den 29. mars 2011 01:08, skrev Stephen Kitt:
> In order to upload to Debian, it would theoretically be
> possible to upload mingw-w64 since it's "Arch: all", then upload the full
> gcc-mingw-w64 without bootstrapping. Alternatively, bootstrapping the
> toolchain would only require two steps (but wi
On Sat, Apr 02, 2011 at 10:02:19AM -0400, Scott Howard wrote:
> I think his package is already Arch:all.
[...]
Ahh, yes, I had missed the package name/source. I agree your
analysis sounds a far more likely scenario given the problem
description.
--
{ IRL(Jeremy_Stanley); WWW(http://fungi.yuggoth.
On Sat, Apr 2, 2011 at 9:44 AM, The Fungi wrote:
> On Sat, Apr 02, 2011 at 10:21:57AM +0200, Michael Wild wrote:
> [...]
>> I'd like the docs only to be built *once* on the build server, not for
>> every architecture, since they are architecture independent and building
>> them for every architect
On Sat, Apr 02, 2011 at 10:21:57AM +0200, Michael Wild wrote:
[...]
> I'd like the docs only to be built *once* on the build server, not for
> every architecture, since they are architecture independent and building
> them for every architecture would waste hours of time.
[...]
For the moment at l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2011-04-02 10:11, Chris Carr wrote:
> Hi all,
>
> I'm puzzled by this warning from lintian:
>
> chrisc@xaphod:/var/cache/pbuilder/result$ lintian -Ivi --pedantic
> angband_3.2.0-1_i386.changes
> N: Setting up lab in /tmp/esv0j1oUBP ...
> N: Pro
On 04/01/2011 01:50 PM, Ben Finney wrote:
> Michael Wild writes:
>
>> In my case, I would need to set different configure flags depending on
>> whether the documentation should be built or not since the default
>> target also builds the docs if enabled.
>
> Under what conditions should the docum
Hi all,
I'm puzzled by this warning from lintian:
chrisc@xaphod:/var/cache/pbuilder/result$ lintian -Ivi --pedantic
angband_3.2.0-1_i386.changes
N: Setting up lab in /tmp/esv0j1oUBP ...
N: Processing 3 packages...
N:
N: Processing changes file angband_3.2.0-1_i386 (version 1:3.2.0-1) ...
N:
Hi, Bastien,
I am not a DD, but I can try to give you some tips:
1) lintian -IE --pedantic over .dsc gives you 2 warnings:
P: adms source: debian-control-has-unusual-field-spacing line 18
E: adms source: unknown-file-in-debian-source git-patches
2) patch should correspond to dep-3[1], and it s
17 matches
Mail list logo