On Tuesday 07 February 2006 13:15, Jari Aalto wrote:
> Is the upstream using a VCS? (Version control software)?
>
> 1) If he is, can he grant you a direct write access. That would be the
> easiest.
>
> 2) Can he be persuaded into using distributed SCM[1]? That way both of
> you can synchroniz
Stan Vasilyev <[EMAIL PROTECTED]> writes:
> I have a situation with a Debian package xdialog:
> http://packages.qa.debian.org/x/xdialog.html
>
> The upstream author, Thierry Godefroy <[EMAIL PROTECTED]>, insists on keeping
> the debian changes inside the upstream tarball, orig.tar.gz. This
> com
On Sat, Jan 28, 2006 at 01:04:49PM -0500, [EMAIL PROTECTED] wrote:
> If they feel the need to do it themselves, make sure they have all 12
> architectures, for each of unstable, testing, stable, and oldstable,
> and file bugs when packages aren't kept up to date.
> :)
Restricting themselves to th
On Sat, Jan 28, 2006 at 07:02:26PM +0100, Thomas Viehmann wrote:
> Mark Brown wrote:
> > That's not their home page which is what they want: if they were happy
> > for people to go elsewhere for their packages they wouldn't be doing
> > things like building packages for distributions they don't eve
Mark Brown wrote:
> That's not their home page which is what they want: if they were happy
> for people to go elsewhere for their packages they wouldn't be doing
> things like building packages for distributions they don't even have
> installed.
IME most projects are perfectly content to point to
On Wed, Jan 25, 2006 at 11:17:09PM +0100, martin f krafft wrote:
> also sprach Mark Brown <[EMAIL PROTECTED]> [2006.01.24.2229 +0100]:
> > People sometimes do this so they can ship something targetted at stable
> > (one of my upstreams insists on doing this and also doesn't want to use
> > any Deb
Am Donnerstag, den 26.01.2006, 19:30 -0800 schrieb Stan Vasilyev:
> On Tuesday 24 January 2006 13:14, Stan Vasilyev wrote:
> > I have a situation with a Debian package xdialog:
> > http://packages.qa.debian.org/x/xdialog.html
> >
> > The upstream author, Thierry Godefroy <[EMAIL PROTECTED]>, insist
On Thu, Jan 26, 2006 at 07:30:22PM -0800, Stan Vasilyev wrote:
> From the last e-mail I got from Thierry it looks like he wants to make a
> compromise. Since I annoyed him so much with my e-mails, he proposed to start
> releasing Xdialog in two versions: Xdialog-version.tar.bz2 file with debian
On Tuesday 24 January 2006 13:14, Stan Vasilyev wrote:
> I have a situation with a Debian package xdialog:
> http://packages.qa.debian.org/x/xdialog.html
>
> The upstream author, Thierry Godefroy <[EMAIL PROTECTED]>, insists on keeping
> the debian changes inside the upstream tarball, orig.tar.gz.
Please do not CC people on Debian mailinglists unless specifically
requested!
also sprach skaller <[EMAIL PROTECTED]> [2006.01.26.0146 +0100]:
> Some old version of it is anyhow :)
This is entirely up to the maintainer. And there is backports.org
--
Please do not send copies of list mail to me;
On Wed, 2006-01-25 at 23:17 +0100, martin f krafft wrote:
> also sprach Stan Vasilyev <[EMAIL PROTECTED]> [2006.01.24.2214 +0100]:
> > I tried convincing the upstream to remove the debian directory, but so far
> > he
> > refused. His argument is that a user should be able to download his tarball
also sprach Stan Vasilyev <[EMAIL PROTECTED]> [2006.01.24.2214 +0100]:
> I tried convincing the upstream to remove the debian directory, but so far he
> refused. His argument is that a user should be able to download his tarball
> and build it from source, build an rpm package or build a deb pack
also sprach Mark Brown <[EMAIL PROTECTED]> [2006.01.24.2229 +0100]:
> People sometimes do this so they can ship something targetted at stable
> (one of my upstreams insists on doing this and also doesn't want to use
> any Debian tools since they don't run Debian).
backports.org
> "You grabbed my
On Tue, Jan 24, 2006 at 09:53:19PM -0800, Russ Allbery wrote:
> Martin Meredith <[EMAIL PROTECTED]> writes:
>
> > Why not just work with upstream as you seem to be doing - and when the
> > packagings done - download it ... and upload as a debian native package?
>
> > Surely if upstream keep a deb
Martin Meredith <[EMAIL PROTECTED]> writes:
> Why not just work with upstream as you seem to be doing - and when the
> packagings done - download it ... and upload as a debian native package?
> Surely if upstream keep a debian/ directory in the tarball then it would
> automatically be assumed as
Stan Vasilyev <[EMAIL PROTECTED]> writes:
> On Tuesday 24 January 2006 13:52, Russ Allbery wrote:
>> Why? Do you have to remove some files for DFSG-compliance?
> Sorry, what I meant was my orig.tar.gz ends up being the pre-release
> version, not the official version released on the website.
Thi
Why not just work with upstream as you seem to be doing - and when the
packagings done - download it ... and upload as a debian native package?
Surely if upstream keep a debian/ directory in the tarball then it would
automatically be assumed as a debian native package?
Get the pre-release, make i
On Tuesday 24 January 2006 13:52, Russ Allbery wrote:
> > But I end up repackaging the upstream source anyway. The .orig.tar.gz
> > is not the same file that Thierry puts on his website.
>
> Why? Do you have to remove some files for DFSG-compliance?
Sorry, what I meant was my orig.tar.gz ends up
On Tuesday 24 January 2006 13:52, Daniel Leidert wrote:
> Maybe you should also
> tell him, that not every user getting the upstream sources may be happy
> with your packaging files (e.g. because of your decision of
> (build-)dependencies and configure options, different available library
> versio
On Tue, 2006-01-24 at 13:23 -0800, Russ Allbery wrote:
> What I would do if I were you would be to make the changes you need to
> make to the upstream debian directory to have the package work the way
> that it should and send the diffs back to upstream as a courtesy, but
> not wait for a new upstr
Am Dienstag, den 24.01.2006, 13:14 -0800 schrieb Stan Vasilyev:
> I have a situation with a Debian package xdialog:
> http://packages.qa.debian.org/x/xdialog.html
>
> The upstream author, Thierry Godefroy <[EMAIL PROTECTED]>, insists on keeping
> the debian changes inside the upstream tarball, o
Stan Vasilyev <[EMAIL PROTECTED]> writes:
> On Tuesday 24 January 2006 13:23, Russ Allbery wrote:
>> What I would do if I were you would be to make the changes you need to
>> make to the upstream debian directory to have the package work the way
>> that it should and send the diffs back to upstrea
On Tuesday 24 January 2006 13:23, Russ Allbery wrote:
>
> What I would do if I were you would be to make the changes you need to
> make to the upstream debian directory to have the package work the way
> that it should and send the diffs back to upstream as a courtesy, but not
> wait for a new upst
On Tue, Jan 24, 2006 at 01:23:34PM -0800, Russ Allbery wrote:
> Yeah, I agree with your general argument, but I can also see where he's
> coming from. He's applying the RPM model where this is how people
> normally handle RPMs of software that Red Hat itself isn't maintaining.
> He probably doesn
Stan Vasilyev <[EMAIL PROTECTED]> writes:
> I have a situation with a Debian package xdialog:
> http://packages.qa.debian.org/x/xdialog.html
> The upstream author, Thierry Godefroy <[EMAIL PROTECTED]>, insists on
> keeping the debian changes inside the upstream tarball, orig.tar.gz.
> This compl
I have a situation with a Debian package xdialog:
http://packages.qa.debian.org/x/xdialog.html
The upstream author, Thierry Godefroy <[EMAIL PROTECTED]>, insists on keeping
the debian changes inside the upstream tarball, orig.tar.gz. This complicates
the development process. First of all, when
26 matches
Mail list logo
