Re: Weird set -u error
On Sat, Aug 27, 2022 at 12:11:47AM -0500, David Wright wrote:
> On Sat 27 Aug 2022 at 00:23:10 (-0400), gene heskett wrote:
> > On 8/26/22 20:35, David wrote:
> > > On Sat, 27 Aug 2022 at 10:27, Greg Wooledge <greg@wooledge.org> wrote:
> > > > I get these results as well, with Debian 11's packaged bash.
> > > Yeah, sorry, I forgot to include, for the record:
> > >
> > > $ echo $BASH_VERSION
> > > 5.1.4(1)-release
> > > $ apt list --installed bash
> > > Listing... Done
> > > bash/stable,now 5.1-2+deb11u1 amd64 [installed]
> > >
> > > .
> > Why the miss-match, I get the same results as this myself.
>
> bash_5.1-2+deb11u1_amd64.deb
>
> bash is package name
>
> 5.1 is upstream version
>
> 2+deb11u1 is /Debian/ version
>
> amd64 is architecture.
5.1.4 is upstream's notation for bash 5.1 with the first 4 (upstream)
patches applied. The (1) means it was the first time bash had been
built in that directory.
If you work with upstream bash source, you may end up with something
like 5.1.4(2)-release meaning you compiled it once, changed something,
then compiled it again. Applying upstream patches in the same directory
might give you 5.1.5(3)-release and so on. Although typically you'll
apply more than one patch at a time, because Chet Ramey tends to release
them in groups.
Reply to: