Re: How to include information about a source package ?

On Sat, Apr 29, 2006 at 01:52:17PM -0700, Russ Allbery wrote: > If I were sponsoring a -1 release of a package in which the maintainer > repackaged the upstream source, which is what I was originally > addressing, I would read the implementation of that target, read the > information in debian/copy

Re: How to include information about a source package ?

George Danchev <[EMAIL PROTECTED]> writes: > On Saturday 29 April 2006 22:06, Russ Allbery wrote: >> George Danchev <[EMAIL PROTECTED]> writes: >>> On Saturday 29 April 2006 21:34, Russ Allbery wrote: After I've done one upload with a particular upstream source, I usually just pull the u

Re: packaging a release

gregor herrmann <[EMAIL PROTECTED]> wrote: > There are helpers for other version control systems, too: > > $ apt-cache search --names-only .*-buildpackage > arch-buildpackage - tools for maintaining Debian packages using arch > cvs-buildpackage - A set of Debian package scripts for CVS source tree

Re: packaging a release

On Sat, Apr 29, 2006 at 01:27:10PM -0700, Tyler MacDonald wrote: > I'd like to build my debian packages out of my repository, so I've added the > following in my debian/rules... Is there a better, standardized way to do > this? (I've already looked at cvs-buildpackage, but I want to move away from

packaging a release

I'd like to build my debian packages out of my repository, so I've added the following in my debian/rules... Is there a better, standardized way to do this? (I've already looked at cvs-buildpackage, but I want to move away from CVS sometime in the near future...) Thanks, Ty

Re: How to include information about a source package ?

On Saturday 29 April 2006 22:06, Russ Allbery wrote: > George Danchev <[EMAIL PROTECTED]> writes: > > On Saturday 29 April 2006 21:34, Russ Allbery wrote: > >> After I've done one upload with a particular upstream source, I usually > >> just pull the upstream source out of the Debian archive so tha

Re: How to include information about a source package ?

George Danchev <[EMAIL PROTECTED]> writes: > On Saturday 29 April 2006 21:34, Russ Allbery wrote: >> After I've done one upload with a particular upstream source, I usually >> just pull the upstream source out of the Debian archive so that I don't >> have to worry about it changing. > What about

Re: How to include information about a source package ?

On Saturday 29 April 2006 21:34, Russ Allbery wrote: > George Danchev <[EMAIL PROTECTED]> writes: > > Just to mention that when the get-orig-source target fetches the tarball > > it must be checked every-single time to prevent silently (intentionaly > > or not) changed tarball files under the build

Re: How to include information about a source package ?

George Danchev <[EMAIL PROTECTED]> writes: > Just to mention that when the get-orig-source target fetches the tarball > it must be checked every-single time to prevent silently (intentionaly > or not) changed tarball files under the builder's feet or indicate for > incomplete downloads too. Here i

Re: How to include information about a source package ?

Andreas Barth <[EMAIL PROTECTED]> writes: > * Russ Allbery ([EMAIL PROTECTED]) [060429 05:50]: >> 4. should use -.orig as the name of the >> top-level directory in its tarball. This makes it possible to >> distinguish pristine tarballs from repackaged ones. + >> >> that feels very ugly a

Re: How to include information about a source package ?

On Fri, Apr 28, 2006 at 06:02:26PM -0700, Russ Allbery wrote: > Justin Pryzby <[EMAIL PROTECTED]> writes: > > > DevRef suggests README.Debian-source for information about how a > > nonpristine sourceball is repacked; you could use that, or borrow the > > naming convention. > > That seems like a r

Re: How to include information about a source package ?

On Saturday 29 April 2006 06:50, Russ Allbery wrote: > Justin Pryzby <[EMAIL PROTECTED]> writes: --snip-- > > I think ./debian/copyright is relevant, and for saods9 I have made > > mention in both places. I feel that it should be a machine readable > > copy, too, even if the comments are extra-des

Re: i18l, gettext and (X)dialog

On Tue, Apr 25, 2006 at 11:52:14PM +0200, Michelle Konzack wrote: > Xdialog --title "sampleprogi" --screen-center --no-cancel --wrap \ > --backtitle "Here a text which show $FOO BAR" --fixed-font \ > --textbox $FILE 30 $DLGW > > this is working fine, but I want the Backtitle i18n.

i18l, gettext and (X)dialog

Hello, I have gotten a couple of tools and frontends which are using (X)dialog but unfortunatly they are only in english. OK, no problem, - I was thinking... Most displayed text are now i18n but there is a problem with "--backtitle" in (X)dialog. Example: Xdialog --title "sampleprogi" --screen-

Re: How to include information about a source package ?

* Russ Allbery ([EMAIL PROTECTED]) [060429 05:50]: > Justin Pryzby <[EMAIL PROTECTED]> writes: > > > > > http://www.debian.org/doc/developers-reference/ch-best-pkging-practices.en.html#s-repackagedorigtargz > > 4. should use -.orig as the name of the > top-level directory in its tarball.