On Fri, Nov 04, 2005 at 10:22:09PM +0800, Zak B. Elep wrote:
> On 11/4/05, Andrew Suffield <[EMAIL PROTECTED]> wrote:
> > Which is exactly what you're supposed to be doing. Letting
> > arch-buildpackage build one only makes sense when upstream uses arch,
> > in which case you want to keep the contr
On 11/4/05, Andrew Suffield <[EMAIL PROTECTED]> wrote:
> Which is exactly what you're supposed to be doing. Letting
> arch-buildpackage build one only makes sense when upstream uses arch,
> in which case you want to keep the control files. The whole point of
> this feature originally was to build t
On Fri, Nov 04, 2005 at 06:32:27PM +0800, Zak B. Elep wrote:
> As shown, the `tar' to make the .orig.tar.gz is hard-coded. Hence,
> even Mr. Sogo's setting at ~/.archdeb.conf will not work, unless I
> copy the upstream .tar.gz manually to /.*.orig.tar.gz.
Which is exactly what you're supposed to
package arch-buildpackage
reopen 324135 =
thanks iho
Hi all,
Looking at /usr/bin/arch-buildpackage, it seems that the (re)building
of upstream source from /upstream doesn't strip
'\{arch\}|\.arch-ids' at all:
unless ($skip_tarball)
{
my $olddir = cwd;
chdir "$package/upstream" or die "
Package: arch-buildpackage
Version: 0.1-3
Severity: normal
Tags: patch
Hi,
Default exclude options to dpkg-buildpackage seem that does not cover
every directory created for arch/bazaar.
When using bazaar for managing my repository and arch-buildpackage to
build packages, I had to add these
5 matches
Mail list logo
