On Tue, Apr 07, 2009 at 11:53:07PM -0500, Manoj Srivastava wrote:
> > The Debian archive is *not* the canonical location for the upstream's
> > original source. The upstream's repository (whether VCS or static
> > files or whatever they make available) is the canonical location.
> > Debian's archiv
On Tue, Apr 07 2009, Ben Finney wrote:
> (Why was Manoj's message also sent individually to me?)
>
> On 07-Apr-2009, Manoj Srivastava wrote:
>> If the current version is what we are interested, why not
>> get it from the canonical site, the Debian archive?
>
> The Debian archive is
On Wed, Apr 08, 2009 at 09:04:21AM +1000, Ben Finney wrote:
> (Why was Manoj's message also sent individually to me?)
>
> On 07-Apr-2009, Manoj Srivastava wrote:
> > If the current version is what we are interested, why not
> > get it from the canonical site, the Debian archive?
>
>
(Why was Manoj's message also sent individually to me?)
On 07-Apr-2009, Manoj Srivastava wrote:
> If the current version is what we are interested, why not
> get it from the canonical site, the Debian archive?
The Debian archive is *not* the canonical location for the upstream's
o
On Tue, Apr 07, 2009 at 10:06:18AM -0500, Manoj Srivastava wrote:
> If the current version is what we are interested, why not get it
> from the canonical site, the Debian archive?
I am a new maintainer, and I have sponsors for various packages.
People can check out the source code, and r
On Tue, Apr 07, 2009 at 10:00:05AM -0500, Manoj Srivastava wrote:
> On Sat, Apr 04 2009, Noah Slater wrote:
> > As a concrete benefit, my nightly cron to check uscan for all my
> > packages will be able to alert me about the ones pulled from
> > repository revisions, all I would need to do is add a
On Thu, Apr 02 2009, Noah Slater wrote:
> On Fri, Apr 03, 2009 at 10:50:11AM +1100, Ben Finney wrote:
>> That's the trouble though. AIUI, different VCSen have different ways
>> of identifying a specific state of the working tree; we have not only
>> revisions, but also tags, branches, threads, hea
On Sat, Apr 04 2009, Noah Slater wrote:
> On Sat, Apr 04, 2009 at 01:35:17PM -0600, Raphael Geissert wrote:
>> opts=handler=svn http://domain.tld/svn/foo/...>
>> would do the right thing.
>
> What about uscan being able to use custom make targets in debian/rules?
>
> There could be a way to tell u
Noah Slater wrote:
>
> What about uscan being able to use custom make targets in debian/rules?
[...]
No, #458789
Cheers,
Raphael Geissert
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Sat, Apr 04, 2009 at 01:35:17PM -0600, Raphael Geissert wrote:
> opts=handler=svn http://domain.tld/svn/foo/...
>
> would do the right thing.
What about uscan being able to use custom make targets in debian/rules?
There could be a way to tell uscan to use the following:
debian/rules get-ori
Ben Finney wrote:
> Raphael Geissert writes:
[...]
>> How does bzr recognise whether it should use http or not?
>
> I don't understand the question. I'll try to answer what might be the
> question; if this doesn't answer you, please re-phrase.
>
> Bazaar can use HTTP as a transport for file-lev
Andreas Tille wrote:
> On Fri, 3 Apr 2009, Raphael Geissert wrote:
>
>>> One additional thought: We store packaging Vcs and upstream homepage
>>> in debian/control. What about storing upstream Vcs there as well and
>>> teach uscan to look there as well. Just a rough thought.
>>
>> And do what w
On Fri, 3 Apr 2009, Raphael Geissert wrote:
One additional thought: We store packaging Vcs and upstream homepage
in debian/control. What about storing upstream Vcs there as well and
teach uscan to look there as well. Just a rough thought.
And do what with it? how will it know what it should
Raphael Geissert writes:
> Ben Finney wrote:
>
> > I'd prefer, if the information is to be encoded in the URL, that
> > the URL should remain useable as-is with the VCS tool itself.
> >
> > I know that's possible for ‘svn+http://’, but it's not possible
> > for ‘bzr+http://’ if the files are me
Ben Finney wrote:
> Raphael Geissert writes:
>
>> Ben Finney wrote:
>> > * the fact that the URL doesn't necessarily indicate what VCS tool is
>> > needed to interact with it (just about all of them allow an HTTP URL
>> > for public read-only access, so that's what will commonly be used
>> >
Raphael Geissert writes:
> Ben Finney wrote:
> > * the fact that the URL doesn't necessarily indicate what VCS tool is
> > needed to interact with it (just about all of them allow an HTTP URL
> > for public read-only access, so that's what will commonly be used
> > here)
>
> That can easil
[No CC please]
Daniel Leidert wrote:
[...]
>
> I would like to propose a complete rethinking of the watch files.
> We have several packages, which must be prepared from a VCS or
> must be repckaged. ATM several people changed to use something like
>
> $url $pattern debian /bin/sh get-orig-source
Ben Finney wrote:
[...]
>
> For my purposes, I would like to be able to specify “fetch from the
> VCS at $URL, getting the specific working tree referenced by
> identifier $ID” and then the rest of what uscan does for generating
> an original source archive from the working tree.
>
> That's made
Andreas Tille wrote:
[...]
>
> One additional thought: We store packaging Vcs and upstream homepage
> in debian/control. What about storing upstream Vcs there as well and
> teach uscan to look there as well. Just a rough thought.
>
And do what with it? how will it know what it should look for?
On Fri, 3 Apr 2009, Daniel Leidert wrote:
I would like to propose a complete rethinking of the watch files.
We have several packages, which must be prepared from a VCS or
must be repckaged. ATM several people changed to use something like
$url $pattern debian /bin/sh get-orig-source-script
One
Ben Finney wrote:
> Raphael Geissert writes:
>
> > I planned to add support for svn in version 4 watch files (it would
> > be a matter of svn info svn://domain.tld/path/to/repo and some data
> > massaging).
> >
> > But well, now that everyone is talking about it why not just tell
> > what is miss
On Fri, Apr 03, 2009 at 10:04:21AM +1100, Ben Finney wrote:
> For my purposes, I would like to be able to specify “fetch from the
> VCS at $URL, getting the specific working tree referenced by
> identifier $ID” and then the rest of what uscan does for generating
> an original source archive from t
On Fri, Apr 03, 2009 at 10:50:11AM +1100, Ben Finney wrote:
> That's the trouble though. AIUI, different VCSen have different ways
> of identifying a specific state of the working tree; we have not only
> revisions, but also tags, branches, threads, heads, and probably
> others I've forgotten. Shou
Noah Slater writes:
> On Fri, Apr 03, 2009 at 10:04:21AM +1100, Ben Finney wrote:
> > * the plethora of different concepts for mapping identifiers to
> > specific working trees in different VCSen (revision-id and branches
> > and tags, oh my!)
>
> This could be possible with a set of configu
Raphael Geissert writes:
> I planned to add support for svn in version 4 watch files (it would
> be a matter of svn info svn://domain.tld/path/to/repo and some data
> massaging).
>
> But well, now that everyone is talking about it why not just tell
> what is missing so that it can be addressed i
25 matches
Mail list logo
