On Fri, Feb 07, 2014 at 08:07:41PM -0500, James McCoy wrote:
> On Fri, Feb 07, 2014 at 10:32:52AM +0100, Daniel Leidert wrote:
> > James McCoy wrote:
> > >Part of the reason I chose to use debian/upstream/ is that an extensible
> > >location for upstream related information (similar in spirit to
>
Greetings Fellow Developers,
I would like to put here some words that I had in mind since I
discovered the problem with the upstream file/dir in debian/.
It is already a respectable while that we use the debian/upstream
*file* for the documentation of bibliographic data in packages that
might ha
Hi,
On Mon, 10 Feb 2014, Filippo Rusconi wrote:
> I discovered recently that upstream was to become a directory in
> debian/. While I think that such a choice might be a reasonably good
> idea, I have to admit my astonishment at the total absence of
> information/discussion around that matter, fro
Hi,
On Mon, Feb 10, 2014 at 11:42:20AM +0100, Raphael Hertzog wrote:
> This change was also suggested by Guillem Jover in
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735840#20 and I tend
> to agree with the logic of grouping upstream related meta-data
> in a single directory.
Quoting this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Le 10/02/2014 08:36, Andreas Tille a écrit :
> I wonder in how far it is to late for debian/watch and not for the file
> debian/upstream. Yey, I'm aware that we have two to three orders of
> magnitude more debian/watch files than debian/upstream fi
Hi David,
On Mon, Feb 10, 2014 at 03:37:54PM -0400, David Prévot wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Le 10/02/2014 08:36, Andreas Tille a écrit :
>
> > I wonder in how far it is to late for debian/watch and not for the file
> > debian/upstream. Yey, I'm aware that we
Hi,
On Wed, Feb 12, 2014 at 04:11:41PM +0900, Charles Plessy wrote:
> Le Wed, Feb 12, 2014 at 12:06:42AM -0500, James McCoy a écrit :
> >
> > That being said, I don't have access to most of the packages. Even if I
> > did, it feels "dirty" to go and commit to a couple hundred packages I
> > have
Le 12 févr. 2014 15:41, "Andreas Tille" a écrit :
>
> Hi,
>
> On Wed, Feb 12, 2014 at 04:11:41PM +0900, Charles Plessy wrote:
> > Le Wed, Feb 12, 2014 at 12:06:42AM -0500, James McCoy a écrit :
> > >
> > > That being said, I don't have access to most of the packages. Even
if I
> > > did, it feels
Have I missed the background?
is debian/watch getting renamed to debian/upstream -- where is the
"conflict"?
On Wed, 12 Feb 2014, Andreas Tille wrote:
> Hi,
> On Wed, Feb 12, 2014 at 04:11:41PM +0900, Charles Plessy wrote:
> > Le Wed, Feb 12, 2014 at 12:06:42AM -0500, James McCoy a écrit :
>
Hi Simon,
I have no idea whether you did follow the discussion but it would be
great if you could submit a patch to the lintian check you recently
wrote. The upstream files will be moved from debian/upstream (the
file) to debian/upstream/metadata.
Kind regards
Andreas.
On Sat, Feb 22, 201
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 2014-02-23 09:01, schrieb Andreas Tille:
> Hi Simon,
>
> I have no idea whether you did follow the discussion but it would
> be great if you could submit a patch to the lintian check you
> recently wrote. The upstream files will be moved from
>
11 matches
Mail list logo
