Update to upstream version '4.1.4'
with Debian dir 11c855bc47d981c73998b00db105cc7413791177

No longer requested

foton.py: fix get_zroots()

See merge request !38

Update to upstream version '4.1.3'
with Debian dir d09668339059f5061758222d835e60476af238df

Update to upstream version '4.1.3~dev1'
with Debian dir 542406b0f9df7ec08450c8ed9d477f2e5ffd9dcb

Nesting of excitation channel names now depends on total channel count as it did in version 3.  In Earlier versions of 4, nesting depended on excitation channel count.

So that nesting happens at small numbers of channels on channel selection boxes.

Update to upstream version '4.1.2'
with Debian dir 1d2a1f14dce19297dadc04b8747cc2d4acde36a9

Also updated change logs.

A mistake in 4.1.1 caused diaggui to never use full nesting of channel
names in the channel selection tree for excitations while using
the online mode.

When adding a zero or pole using Mag-Q format in foton,
the sign of the real value would always match the sign of the magnitude.

Positive magnitudes could only work in the normalized plane.  In the normalized plane, the right hand of the plane, when reals are positive, is stable.

For the frequency or 's' planes, these roots are unstable.  The real must be negative.

The change makes the real part always negative for frequency and "s" plane roots, and always positive for "n" plane roots.

Update to upstream version '4.1.1'
with Debian dir 805b5e1433f86ff11b428819aeec299b64b924bb

Bump version to 4.1.1

Previously the check warned on any zero with a positive real value in the 's' plane.

now it warns on zeros that have magnitude > 1 + 1E-10 in the 'z' plane.

This probably handles varying frequencies better, and the additional 1E-10
prevents minor RHP zeros from being flagged.

Update to upstream version '4.1.0'
with Debian dir 147f3f9bfc6351008d8020684029ddb55f8dd573

Also Release 4.1.0

Prevents accidentally merging unmerged branches.

Update to upstream version '4.1.0~rc4'
with Debian dir 43be38811f5bd81aac00f7f7867d81156ca4b00d

because rc3 was a bad build

Because of bad file reading, awggui always tried to start an excitation a second time after the initial ramp up was
finished.  This would always cause a glitch on loading a configuration that starts an excitation.

Update to upstream version '4.1.0~rc2'
with Debian dir c3984a41de8aca3d939d0d1050e323ed799e4634

Run in source directory after tagging release with version number:
./auto_deb_release.sh <version>
will create release packaging for debian buster,bullseye, and bookworm