On Friday 12 December 2008 01:16:00 Paul Gevers wrote:
> >> So how to complain about packages that don't want to change the
> >> policy? I filed a bug at upstream [1] but it was a wontfix.
> >
> > Why? What was the excuse? You'll need to persuade upstream that it is
> > not acceptable. How you do t
>> So how to complain about packages that don't want to change the
>> policy? I filed a bug at upstream [1] but it was a wontfix.
>
> Why? What was the excuse? You'll need to persuade upstream that it is
> not acceptable. How you do that is up to you - one of the main skills
> of a maintainer is p
On Thu, 11 Dec 2008 15:45:25 -0600
Paul Gevers wrote:
> >> It is simply unacceptable to have the debian/ directory in the
> >> upstream source.
>
> So how to complain about packages that don't want to change the
> policy? I filed a bug at upstream [1] but it was a wontfix.
Why? What was the exc
Andy Hawkins wrote:
> I'll look at getting it packaged up tomorrow and uploaded to 'mentors'. Is
> the request for sponsorship automatic? Or is there an 'approved' format?
>
No, you'll have to post a request here on the list. I believe the site
provides a template (that unfortunatelly does not
Hi,
In article <20081211213923.gd6...@powdarrmonkey.net>,
Jonathan Wiltshire wrote:
> You need to file an Intent to Package [1] if you haven't already.
Yep, I've done that.
> Then when you upload to mentors.d.n, you have the opportunity to log in
> and get a template Request for Spon
>> It is simply unacceptable to have the debian/ directory in the upstream
>> source.
So how to complain about packages that don't want to change the policy?
I filed a bug at upstream [1] but it was a wontfix.
Also other literature about why not to ship debian/ [2].
Paul
[1] http://mantis.freepa
news wrote on 12/11/2008 04:04:37 PM:
> Hi,
>
> In article <200812111821.06249.to...@rastageeks.org>,
>Romain Beauxis wrote:
> > Please, make sure to seperate the debian packaging files from
yourreleased
> > software. There can be several debian package for a single
> upstream rel
On Thu, Dec 11, 2008 at 09:23:53PM +, Andy Hawkins wrote:
> I'll look at getting it packaged up tomorrow and uploaded to 'mentors'. Is
> the request for sponsorship automatic? Or is there an 'approved' format?
You need to file an Intent to Package [1] if you haven't already. Then
when you uplo
Neil Williams (11/12/2008):
> Packages created by the upstream team are generally exceptionally poor
> quality. Even if the upstream team is or includes the Debian
> maintainer, there is no justification for having a .deb on the
> upstream download page - leave it to the packagers.
And packagers
Hi,
In article <20081211211444.b3526312.codeh...@debian.org>,
Neil Williams wrote:
> Upstream is not Debian - the two should not mix, even if your are the
> Debian maintainer. The debian/ directory will have to be changed
> between upstream releases and must not be overwritten with the
Andy Hawkins (11/12/2008):
> I'm not sure I understand why the debian directory shouldn't be part
> of my 'main' release? What problems does this cause?
Hello, see [1] for some reasons. Have a nice reading.
1.
http://kitenet.net/~joey/blog/entry/on_debian_directories_in_upstream_tarballs/
Mra
On Thu, 11 Dec 2008 21:04:37 + (UTC)
Andy Hawkins wrote:
> > Please, make sure to seperate the debian packaging files from your
> > released software. There can be several debian package for a single
> > upstream release, so debian-related things should always be out of
> > the software's cod
Hi,
In article <200812111821.06249.to...@rastageeks.org>,
Romain Beauxis wrote:
> Please, make sure to seperate the debian packaging files from your released
> software. There can be several debian package for a single upstream release,
> so debian-related things should always be out
On Thu, 11 Dec 2008 15:33:59 + (UTC)
Andy Hawkins wrote:
> For information, the source is all stored in a subversion repository,
> so if there's a 'better' way of building .debs.
As long as the debian/ directory is not part of the upstream source,
that isn't going to be a problem.
> The pa
Le Thursday 11 December 2008 16:33:59 Andy Hawkins, vous avez écrit :
> The package isn't ready to be uploaded to Debian 'proper' as I want to
> release a new version of the software *and* the Debian packages together.
> As such, I need to be a bit careful about it getting out 'into the wild' as
>
Hi all,
I think I'm about done with the packaging of my flactag utility. Initially
I'd like someone who knows about these things to take a look over the
package to make sure there's nothing I've done wrong, or missed that I
should have done.
Just for information, I plan on offering a .deb that's
16 matches
Mail list logo
