Re: fmtree: line 0: unknown keyword sha256digest
On Thu 16 Jan 2020 at 06:29:11 (-0800), David Christensen wrote:
> On 2020-01-16 02:31, Brian wrote:
> > On Wed 15 Jan 2020 at 20:55:28 -0800, David Christensen wrote:
> > > On 2020-01-15 12:28, David Christensen wrote:
> > > > Do I build from source? If so, is there a good tutorial?
> > >
> > > https://wiki.debian.org/SimpleBackportCreation
> > >
> > > The only change is the installation step -- apt(8) did not work:
> > >
> > > 2020-01-15 13:31:02 root@po /home/dpchrist/build
> > > # apt install freebsd-buildutils_10.3~svn296373-7_amd64.deb
> >
> > Shouldn't that be
> >
> > apt install ./freebsd-buildutils_10.3~svn296373-7_amd64.deb ?
>
> Repeating my command:
>
> 2020-01-16 06:16:33 root@tinkywinky /home/dpchrist/build
> # apt install freebsd-buildutils_10.3~svn296373-7_amd64.deb
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to locate package freebsd-buildutils_10.3~svn296373-7_amd64.deb
> E: Couldn't find any package by glob
> 'freebsd-buildutils_10.3~svn296373-7_amd64.deb'
> E: Couldn't find any package by regex
> 'freebsd-buildutils_10.3~svn296373-7_amd64.deb'
>
> Using your command:
>
> 2020-01-16 06:16:22 root@tinkywinky /home/dpchrist/build
> # apt install ./freebsd-buildutils_10.3~svn296373-7_amd64.deb
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Note, selecting 'freebsd-buildutils' instead of
> './freebsd-buildutils_10.3~svn296373-7_amd64.deb'
> freebsd-buildutils is already the newest version (10.3~svn296373-7).
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> That was unexpected.
>
> RTFM apt(8) says:
>
> SYNOPSIS
> apt [-h] [-o=config_string] [-c=config_file] [-t=target_release]
> [-a=architecture] {list | search | show | update |
> install pkg [{=pkg_version_number | /target_release}]... |
> remove pkg... | upgrade | full-upgrade | edit-sources |
> {-v | --version} | {-h | --help}}
>
> As I understand Unix paths, 'foo' and './foo' should be the same file.
> But, apparently apt treats the first as a package name while treating
> the second as a path to a *.deb package file. Subtle; and a good trap
> for the unwary.
>
> Thanks for the pointer. :-)
I can't speak to apt as I never use it, having got used to apt-get.
(Be aware of the paragraphs under the heading
SCRIPT USAGE AND DIFFERENCES FROM OTHER APT TOOLS
even if you aren't using a script.)
Your message above includes the lines:
> E: Unable to locate package freebsd-buildutils_10.3~svn296373-7_amd64.deb
> E: Couldn't find any package by glob 'freebsd-buildutils_10.3~svn296373-7_amd64.deb'
> E: Couldn't find any package by regex 'freebsd-buildutils_10.3~svn296373-7_amd64.deb'
and it might be worth pointing out that the last two errors were
provoked by your inclusion of dots in the filename, which behave as
wildcards. While there's almost zero probability of a spurious match
in your case, as you've included all that versioning in the name,
that might not be the case where the filename is short, eg:
https://lists.debian.org/debian-user/2018/08/msg01077.html
Cheers,
David.
Reply to: