Hi Andreas,
On Tue, 2011-07-05 at 20:06 +0200, Andreas Moog wrote:
On 07/05/2011 08:18 AM, Kilian Krause wrote:
On Mon, 2011-07-04 at 17:12 +0200, Andreas Moog wrote:
New version uploaded to mentors and pushed to
git://anonscm.debian.org/pkg-games/trophy.git (Note that I put the
Hi all,
I've recently started to work on some packages and am not sure if I follow
best practices when packaging software from git repositories with
git-buildpackage.
My main point of confusion is that I don't really see the need for tarballs
and what I am doing right now feels a bit clumsy and
Le mercredi 6 juillet 2011 14:38:36, Wolodja Wentland a écrit :
Hi all,
Hi Wolodja,
First, thanks for posting your git workflow. It is for me very interesting to
see different ways of dealing with upstream also using git.
[SNIP]
I know that I could just download the tarball from github and
On Wed, Jul 06, 2011 at 03:12:41PM +0200, Thomas Preud'homme wrote:
Does pristine-tar work if the upstream branch contains files which have been
removed during repack?
Unfortunately the directory and the tarball must have identical contents.
--
WBR, wRAR
signature.asc
Description: Digital
Dear mentors,
I am looking for a sponsor for the new version 1:2011.04.12-1
of the package autoconf-archive.
It builds these binary packages:
autoconf-archive - Autoconf Macro Archive
The upload would fix these bugs: 214089, 568413, 572669, 584180, 593838, 622369
The package can be found on
On Wed, Jul 6, 2011 at 8:38 AM, Wolodja Wentland babi...@gmail.com wrote:
Hi all,
I've recently started to work on some packages and am not sure if I follow
best practices when packaging software from git repositories with
git-buildpackage.
My main point of confusion is that I don't really
Hi William,
On Tue, 2011-07-05 at 18:23 -0600, René Mayorga wrote:
On Tue, Jul 05, 2011 at 08:45:41AM +0200, Kilian Krause wrote:
Tim, are you agreed that William takes over or do you want to remain as
uploader/co-maintainer?
Please let him a co-maint for a while, since he is active
Dear all,
this thread reminds me of a problem I had in a similar case.
When I track the upstream branch, merge it in the Debian branch, our commit
hook sends one notification per upstream commit on our packagers mailing list.
To reduce traffic, and to avoid confusion between changes made by the
Bonjour Thomas,
On Wed, Jul 06, 2011 at 15:12 +0200, Thomas Preud'homme wrote:
Le mercredi 6 juillet 2011 14:38:36, Wolodja Wentland a écrit :
First, thanks for posting your git workflow. It is for me very interesting to
see different ways of dealing with upstream also using git.
No
Hi William,
On Tue, Jul 05, 2011 at 10:50:02PM -0500, William Vera wrote:
On Mon, Jun 27, 2011 at 1:46 AM, Kilian Krause kil...@debian.org wrote:
On Mon, 2011-06-27 at 01:34 -0500, William Vera wrote:
-(snip)-
I need make a package for x86emu.h or I can make some patch for this?
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/29/2011 05:12 PM, David Banks wrote:
wrt to debian/copyright file there are a few issues:
* You might consider using DEP-5 as a best practice, this is up to you.
This has been fixed, but I'm not sure what exactly the content of the
Le mercredi 6 juillet 2011 17:52:31, Wolodja Wentland a écrit :
Bonjour Thomas,
:)
[SNIP]
There was a thread recently about using tarballs or tags on
debian-devel@l.d.o recently. No consensus was reached as it clearly
depends on your needs and probably also your tastes.
Yeah,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Oliver,
On 06.07.2011 18:23, Olivier Girondel wrote:
This has been fixed, but I'm not sure what exactly the content of the
Format: field should be.
please see [1] and that thread in general. Some people have different
understandings what to put
Hi
2011/7/6 Kilian Krause kil...@debian.org:
Hi William,
On Tue, 2011-07-05 at 18:23 -0600, René Mayorga wrote:
On Tue, Jul 05, 2011 at 08:45:41AM +0200, Kilian Krause wrote:
Tim, are you agreed that William takes over or do you want to remain as
uploader/co-maintainer?
Please let
Dear mentors,
I am looking for a sponsor for my package libpar2:
* Package name: libpar2
Version : 0.2
Upstream Author : Peter Brian Clements
Francois Lesueur flesueur AT users.sourceforge.net
* URL : http://parchive.sourceforge.net
* License
Andrey Rahmatullin wrote:
On Wed, Jul 06, 2011 at 03:12:41PM +0200, Thomas Preud'homme wrote:
Does pristine-tar work if the upstream branch contains files which have
been
removed during repack?
Unfortunately the directory and the tarball must have identical contents.
That's not true,
shuerhaaken shuerhaa...@googlemail.com wrote on 2011-07-06 12:54:
My motivation for maintaining this package is: I am the developer of
this program and I'd like to see it in Debian. In the past I packaged
this only for Ubuntu via ppa, but that is not the way it should go.
Until now I haven't
Am 27.06.2011 21:07, schrieb Kilian Krause:
- Why you can't use the zip I don't see. You can easily repack and note that
in README.source. Use the get-orig-source target in debian/rules for that
and possibly use a ~debian version number. The ~debian is not neccessary
though IMHO in this
Le mercredi 6 juillet 2011 20:31:02, Joey Hess a écrit :
Andrey Rahmatullin wrote:
On Wed, Jul 06, 2011 at 03:12:41PM +0200, Thomas Preud'homme wrote:
Does pristine-tar work if the upstream branch contains files which have
been removed during repack?
Unfortunately the directory and
shuerhaaken shuerhaa...@googlemail.com wrote on 2011-07-06 12:54:
The package appears to be lintian clean.
Unfortunately not! Here is my logging (packaging for testing):
N: Setting up lab in /tmp/sVt1potpnA ...
N:
N: Processing changes file xnoise_0.1.25-1_amd64 (version 0.1.25-1) ...
N:
Wolodja Wentland babi...@gmail.com writes:
I've recently started to work on some packages and am not sure if I
follow best practices when packaging software from git repositories with
git-buildpackage.
[...]
I do the following for OpenAFS (see the supporting scripts in the openafs
source
On Wed, Jul 06, 2011 at 19:02 +0200, Thomas Preud'homme wrote:
Personally I don't have any local branch, just remote branches. And when I
need to do a bisect for example I will checkout temporarily one of the
upstream dev branches. What I have is:
origin = upstream repo
alioth = alioth
I am looking for a sponsor for my package pidgin-latex.
* Package name: pidgin-latex
Version : 1.4.4-1
Upstream Author : Benjamin Moll q...@users.sourceforge.net
* URL : http://sourceforge.net/projects/pidgin-latex/
* License : GPL-2
Section : net
It
On Wed, Jul 06, 2011 at 12:53 -0700, Russ Allbery wrote:
Wolodja Wentland babi...@gmail.com writes:
I've recently started to work on some packages and am not sure if I
follow best practices when packaging software from git repositories with
git-buildpackage.
I do the following for
Wolodja Wentland babi...@gmail.com writes:
On Wed, Jul 06, 2011 at 12:53 -0700, Russ Allbery wrote:
[ ... ]
but for some other packages I want to use some of the files that are
generated as part of the upstream tarball release but aren't checked in.
Ok, this is not necessary for me right
On Wed, Jul 06, 2011 at 14:19 -0700, Russ Allbery wrote:
Wolodja Wentland babi...@gmail.com writes:
How stable is get-orig-source across releases?
For a package where I was using a released tarball for the reasons described
above, I would dispense with this target entirely and just use
Wolodja Wentland babi...@gmail.com writes:
Is get-orig-source called by anything or is it merely a nice target to
have so life is easier for other maintainers and oneself when preparing
new releases?
The latter. One could replace it with a shell script, but it's a
semi-standard because it's
Please do not upload directly, i will upload git tree before under collab
maint and postthe final ppackage here.
It is more a rfc.
Bastien
Le 6 juil. 2011 15:14, Bastien ROUCARIES roucaries.bast...@gmail.com a
écrit :
Dear mentors,
I am looking for a sponsor for the new version 1:2011.04.12-1
28 matches
Mail list logo
