-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2010-09-14 18:51, Thiago Franco de Moraes wrote:
Hi all,
Hi
[...]
* This library contains a bunch if bindings, one of them is java. These
java bindings is compiled using ant. The compilations generates a bunch
of .class and .jar files,
Hey everyone,
I'm trying to sort out the packaging of barry-0.17-git snapshots and
it's got some undesirable features which is making packaging a pain and
I don't really know what the best way to deal with them is.
It's got multiple binary packages from the same source package which I
get form
On Tue, Sep 14, 2010 at 08:42:08PM -0700, Russ Allbery wrote:
The conventional way to handle this is to build a Debian package that
installs the keyring and runs apt-key add, based off of packages like
debian-archive-keyring, and then have all clients install that package.
Or drops the key
Jonathan Wiltshire deb...@jwiltshire.org.uk writes:
On Tue, Sep 14, 2010 at 08:42:08PM -0700, Russ Allbery wrote:
The conventional way to handle this is to build a Debian package that
installs the keyring and runs apt-key add, based off of packages like
debian-archive-keyring, and then have
2010/9/15 Jonathan Wiltshire deb...@jwiltshire.org.uk:
On Tue, Sep 14, 2010 at 08:42:08PM -0700, Russ Allbery wrote:
The conventional way to handle this is to build a Debian package that
installs the keyring and runs apt-key add, based off of packages like
debian-archive-keyring, and then have
Hi!
Martin Owens docto...@gmail.com writes:
Add to that the upstream has a tendency to merge in the debian changes
into the trunk and I think he would like to merge in this directory too.
I understand that upstream should avoid adding debian to their main code
repository, is that right?
Martin Owens docto...@gmail.com writes:
Hey everyone,
I'm trying to sort out the packaging of barry-0.17-git snapshots and
it's got some undesirable features which is making packaging a pain and
I don't really know what the best way to deal with them is.
It's got multiple binary packages
Christoph Egger christ...@debian.org writes:
Hi!
Martin Owens docto...@gmail.com writes:
Add to that the upstream has a tendency to merge in the debian changes
into the trunk and I think he would like to merge in this directory too.
I understand that upstream should avoid adding debian to
On Wed, 15 Sep 2010 08:21:29 +1000
Matthew Palmer mpal...@debian.org wrote:
On Tue, Sep 14, 2010 at 01:51:22PM -0300, Thiago Franco de Moraes
wrote:
* The Source is in git [3]. I'm not using the last stable version
because I wasn't able to compile it. What's the policy to version
On Wed, Sep 15, 2010 at 01:31:39PM +0100, Tony Houghton wrote:
Matthew Palmer mpal...@debian.org wrote:
sigar-1.7.0~git833ca18ecfc1f3f45eaf8544d8cdafef6603772d
Yeah, that isn't going to work -- what if the next SHA you want to
package is 12345[blah]... it'll look like a lesser version to
On Wed, 15 Sep 2010 15:18:20 +0200
Adam Borowski kilob...@angband.pl wrote:
On Wed, Sep 15, 2010 at 01:31:39PM +0100, Tony Houghton wrote:
Matthew Palmer mpal...@debian.org wrote:
sigar-1.7.0~git833ca18ecfc1f3f45eaf8544d8cdafef6603772d
Yeah, that isn't going to work -- what if the next
On Wed, Sep 15, 2010 at 03:12:22PM +0100, Tony Houghton wrote:
Adam Borowski kilob...@angband.pl wrote:
Why won't you just use `git --describe`?
[...]
Depending on your upstream's versioning scheme you may want to stick a
tilde somewhere. For example, if the upstream tagged a branch that
On Wed, 2010-09-15 at 11:44 +0200, Goswin von Brederlow wrote:
Do we need both? We have neither in Debian (testing/sid) it seems
anyway.
Personally I'd say no, but this is for a ppa/unstable so it probably has
different considerations. At the same time, this is a request from
upstream. Ubuntu
On Wed, Sep 15, 2010 at 03:18:20PM +0200, Adam Borowski wrote:
[...]
I recommend against using dates to mark revisions, since there probably
will be multiple commits in a single day, so there is no way to tell
which exactly version you did package.
[...]
On one project where I'm upstream (not
Martin Owens docto...@gmail.com writes:
On Wed, 2010-09-15 at 11:44 +0200, Goswin von Brederlow wrote:
Do we need both? We have neither in Debian (testing/sid) it seems
anyway.
Personally I'd say no, but this is for a ppa/unstable so it probably has
different considerations. At the same
Goswin von Brederlow goswin-...@web.de writes:
Christoph Egger christ...@debian.org writes:
Well upstreams are encouraged to not include the debian/ stuff in
their release tarballs. It might be better to have debian/ in a separat
branch but having it in upstream VCS isn't a problem right
On Wed, Sep 15, 2010 at 03:18:20PM +0200, Adam Borowski wrote:
On Wed, Sep 15, 2010 at 01:31:39PM +0100, Tony Houghton wrote:
Matthew Palmer mpal...@debian.org wrote:
sigar-1.7.0~git833ca18ecfc1f3f45eaf8544d8cdafef6603772d
Yeah, that isn't going to work -- what if the next SHA you want
17 matches
Mail list logo
