Disclaimer: longtime apt contributor On Wed, Feb 08, 2017 at 02:49:32PM +0000, Gianfranco Costamagna wrote: > >> apt build-dep (dsc-file) to build-dependencies> > >I remember "apt build-dep <pkg_name>" is only for package already > >exists in archive. > > when the argument is a dsc file, apt parses the dependency list. > (IIRC this is a feature since apt 1.0 or 1.1) apt >= 1.1. Just make sure you give a path like ./pkg_name and not just a filename¹. A path to a directory with a debian/ subdirectory containing a control file works, too, btw, in case you haven't got a dsc file (yet) like a version control checkout. And while shamelessly advertising features let me mention that you can not only install .deb files directly (no need for dpkg -i && install -f), but also .changes files (a helpful flag in this context can be --only-upgrade). If you instead have one (or more) .changes files and want to see what apt would be doing if the included files were part of a repository try "--with-source ./path/pkg.changes" [which will behave as if you had created a repository with this changes file and added that repository to your sources] (Those features require up to apt >= 1.3). In other words: Feel free to help Debian by testing (aka reviewing) the jessie->stretch upgrade path now and gain all those and many more nifty features as compensation for your expenses. ;) Best regards David Kalnischkies ¹ security reasons as if you happen to call apt from a world-writeable directory like /tmp a local user could inject arbitrary content if a "pkg_name" you are going to use on the command line can be guessed.
Attachment:
signature.asc
Description: PGP signature