The "--extra-package" option only works if an absolute path is passed,
that is confusing as generally speaking command line tools don't have
issues with relative paths (when they do, it's called out in the
docs).

I looked at the source code of sbuild to see if I could provide a
patch for it but unfortunately I don' t work with perl and I lack the
time to learn it for this right now.

So this is a feature request to make "extra-package" accept relative
paths as input.

FWIW this is the input that didn't work: "--extra-package=../build-area/"

Thanks,

Hi there, sbuild developers.

Today I was building some packages and I needed a custom archive to be
added to sbuild. The repo was added but for some reason I kept seeing:

gpg: can't open '../file.asc': No such file or directory

It took a while, a bunch of name changes checking out the BTS to realize
relative paths were the issue.

Long story short, passing the absolute path worked. But usually people
(at least myself) expect relative paths to work, so if you don't plan to
implement this functionality soon(ish), could you consider adding this
caveat to the manpage?

Cheers,
Charles

Control: tag -1 + unreproducible

I tried this both with directories as well with plain *.deb files relative to
the path where I run sbuild and it worked just fine.

In what way are you calling sbuild that makes this not work?

Thanks!

cheers, josch

Hi,

I've tested --extra-package=../../some_other_dir and it works with the
latest version in testing. I also reported --extra-repository-key didn't
work with relative paths, but I just tested and it seems to be working.
Maybe both were implemented but the bug not closed (?).

Cheers,
Charles