[SRU] Upstream microrelease, arm64 bootstrap and file layout changes for upcoming dotnet7 release

[Miriam España Acebal]

[Impact]

This correspond to an upstream microrelease (Microsoft Patch Tuesday microrelease).

We want to do an initial bootstrapping of the dotnet6 packages for arm64 architectures in Jammy and Kinetic. It is beneficial for our users to have access to the latest .NET6 stack, so the .NET team is working with the security and SRU teams on getting latest versions backported to 22.04 and 22.10. The initial bootstrapping is always a bit complicated, so we want to start off by doing a backport of 6.0.110 using the bootstrapping PPA. Later uploads will not require such special setup.

We did the 6.0.110 bootstrap and it looked fine, so now we want to update to 6.0.111. So the initial upload to jammy-updates for arm64 will be 111.

The .NET, security and SRU teams are cooperating on creating a SRU exception for these packages, with special rules tailored towards the needs of this project - with an extensive test story and steps necessary for the SRU to proceed.

Also, the installation layout for amd64 will change due to the incoming release of the dotnet7 package (LP: 1995478) to allow the co-installation of both .NET versions. Althought .NET 7 version will not hit Jammy, we want to maintain the coherence in this matter
across the Unbuntu series and also across architectures (so arm64 will be released with this new layout). We implement that change also here.

[Test Case]

As this is the initial bootstrapping, we want the package to build successfully in jammy-proposed and kinetic-proposed (potentially using the bootstrap archive). The packages should be installable on Jammy and Kinetic some basic dogfooding testing should be performed:

#0.Install dotnet: apt install dotnet6

#0.1. Check installation : dpkg -l | grep 'NET\|asp’

#1. Basic check commands: donet —info, dotnet —version, dotnet sdk check

      $ dotnet —info

      #Expected output is:
      # .NET SDK (reflecting any global.json):
      # Version: 6.0.111
      # Commit: b3bb659a9d
      #
      # Runtime Environment:
      # OS Name: ubuntu
      # OS Version: 22.10
      # OS Platform: Linux
      # RID: ubuntu.22.10-x64
      # Base Path: /usr/lib/dotnet/sdk/6.0.111/
      #
      # global.json file:
      # Not found
      #
      # Host:
      # Version: 6.0.11
      # Architecture: x64
      # Commit: 943474ca16
      #
      # .NET SDKs installed:
      # 6.0.111 [/usr/lib/dotnet/sdk]
      #
      # .NET runtimes installed:
      # Microsoft.AspNetCore.App 6.0.11 [/usr/lib/dotnet/shared/Microsoft.AspNetCore.App]
      # Microsoft.NETCore.App 6.0.11 [/usr/lib/dotnet/shared/Microsoft.NETCore.App]
      #
      # Download .NET:
      # https://aka.ms/dotnet-download
      #
      # Learn about .NET Runtimes and SDKs:
      # https://aka.ms/dotnet/runtimes-sdk-info

      $ dotnet --version

      #Expected output is:
      # 6.0.111

      $ dotnet sdk check

      # Expected output is:
      # .NET SDKs:
      # Version Status
      # ------------------------
      # 6.0.111 Up to date.
      #
      # Try out the newest .NET SDK features with .NET 7.0.100.
      #
      # .NET Runtimes:
      # Name Version Status
      # ------------------------------------------------------
      # Microsoft.AspNetCore.App 6.0.11 Up to date.
      # Microsoft.NETCore.App 6.0.11 Up to date.
      #
      #
      # The latest versions of .NET can be installed from https://aka.ms/dotnet-core-download. For more information about .NET lifecycles, see # https://aka.ms/dotnet-core-support.

#2. Checking console, solution and project commands

#2.1. Creating console: dotnet new console

        $ dotnet new console --name Testing

        #Expected output is :
        # The template "Console App" was created successfully.

        # Processing post-creation actions...
        # Running 'dotnet restore' on /root/Testing/Testing.csproj...
        # Determining projects to restore...
        # Restored /root/Testing/Testing.csproj (in 89 ms).
        # Restore succeeded.

        $ cd Testing/

#2.2. Creating solution: dotnet new sln

        $ dotnet new sln

        #Expected output is:
        # The template "Solution File" was created successfully.

#2.3. Adding project to the solution: dotnet sln <sln_file> add <csproj_file>

        $ dotnet sln Testing.sln add Testing.csproj

        #Expected output is:
        # Project `Testing.csproj` added to the solution.

#2.4. Building solution: dotnet build <sln_file>

        $ dotnet build Testing.sln

        #Expected output is:
        # Microsoft (R) Build Engine version 17.0.1+b177f8fa7 for .NET
        # Copyright (C) Microsoft Corporation. All rights reserved.
        #
        # Determining projects to restore...
        # All projects are up-to-date for restore.
        # Testing -> /root/Testing/bin/Debug/net6.0/Testing.dll
        #
        # Build succeeded.
        # 0 Warning(s)
        # 0 Error(s)

#2.5. Running solution: bin/Debug/net6.0/<sln_name>

        $ bin/Debug/net6.0/Testing

        #Expected output is:
        # Hello, World!

#2.6. Project that use a nuget package: dotnet add <csproj_file> package <nuget_package>

        #Changing Program.Cs

        $ cat <<EOF >Program.cs
          using System;
          using System.Collections.Generic;
          using System.Linq;
          using System.Text;
          using System.Threading.Tasks;
          using Google.Apis;

          namespace TestProject
          {
          class Program
          {
          static void Main(string[] args)
          {
          Stack<int> myStack = new Stack<int>();
          var th = new Thread(()=>WaitAndPrint(myStack));
          th.Start();
          Console.WriteLine("Me first!");
          myStack.Push(1);
          Console.WriteLine("Finished tasks: {0}", myStack.Count);
          Thread.Sleep(1000);
          Console.WriteLine("Finished tasks: {0}", myStack.Count);
          }

          private static void WaitAndPrint(Stack<int> myStack){
                  Thread.Sleep(1000);
                  Console.WriteLine("Me second!");
                  myStack.Push(2);
          }
          }

          }

          EOF

        $ dotnet add Testing.csproj package Google.Apis

        #Expected output is:
        # Determining projects to restore...
        # Writing /tmp/tmp6RP8i6.tmp
        #info : Adding PackageReference for package 'Google.Apis' into project 'Testing.csproj'.
        #info : GET https://api.nuget.org/v3/registration5-gz-semver2/google.apis/index.json
        #info : OK https://api.nuget.org/v3/registration5-gz-semver2/google.apis/index.json 221ms
        #info : Restoring packages for /root/Testing/Testing.csproj...
        #info : Package 'Google.Apis' is compatible with all the specified frameworks in project 'Testing.csproj'.
        #info : PackageReference for package 'Google.Apis' version '1.57.0' added to file '/root/Testing/Testing.csproj'.
        #info : Committing restore...
        #info : Writing assets file to disk. Path: /root/Testing/obj/project.assets.json
        #log : Restored /root/Testing/Testing.csproj (in 94 ms).

#2.7. Running project

        $ dotnet run

        #Expected output is:
        # Me first!
        # Finished tasks: 1
        # Me second!
        # Finished tasks: 2

#2.8. Removing nuget package

        $ dotnet remove Testing.csproj package Google.Apis

        #Expected output is:
        # info : Removing PackageReference for package 'Google.Apis' from project 'Testing.csproj'.

        #Checking removing is OK:

        $ dotnet run

        #Expected output is:
        # /root/Testing/Program.cs(7,7): error CS0246: The type or namespace name 'Google' could not be found (are you missing a using directive or an assembly
        # reference?) [/root/Testing/Testing.csproj]
        #
        # The build failed. Fix the build errors and run again.

[Regression Potential]

No regression potential as these packages do not exist for arm64 architectures and/or do not replace any existing packages in 22.04 or 22.10.
For amd64 architectures, if the solution would not be well implemented, the dotnet-host binary will be unable to recognize the SDKs installed and all the other shared files (templates, packs, etc...).

[Original Report]
------------------------------------------------------------------
Now that dotnet7 is coming to Ubuntu (https://bugs.launchpad.net/ubuntu/+bug/1995478), the actual support of several versions through update-alternatives system doesn't allow future SDKs to see previous ones.

To use only a muxer (dotnet binary provided by dotnet-host package nowadays) that can see all the SDKs, shared, templates, etc... the new layout has to be like this: https://learn.microsoft.com/en-us/dotnet/core/distribution-packaging.

To finish, remove the use of update-alternatives.

[Launchpad Janitor (janitor)]

This bug was fixed in the package dotnet6 - 6.0.111-0ubuntu3

---------------
dotnet6 (6.0.111-0ubuntu3) lunar; urgency=medium

  * Don't remove the --with-sdk option, this is supposed to be there.

 -- Steve Langasek <email address hidden> Thu, 17 Nov 2022 20:57:19 +0000

[Steve Langasek (vorlon)]

Hello Miriam, or anyone else affected,

Accepted dotnet6 into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dotnet6/6.0.111-0ubuntu1~22.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Steve Langasek (vorlon)]

Hello Miriam, or anyone else affected,

Accepted dotnet6 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dotnet6/6.0.111-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Miriam España Acebal (mirespace)]

Verification on Kinetic: OK

Installation (also upgrading, but I'll put that output to the Jammy verification):

root@Kdotnet67:~/Testing# apt install dotnet6
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  aspnetcore-runtime-6.0 aspnetcore-targeting-pack-6.0 dotnet-apphost-pack-6.0 dotnet-host dotnet-hostfxr-6.0 dotnet-runtime-6.0 dotnet-sdk-6.0
  dotnet-targeting-pack-6.0 dotnet-templates-6.0 liblttng-ust-common1 liblttng-ust-ctl5 liblttng-ust1 netstandard-targeting-pack-2.1
The following NEW packages will be installed:
  aspnetcore-runtime-6.0 aspnetcore-targeting-pack-6.0 dotnet-apphost-pack-6.0 dotnet-host dotnet-hostfxr-6.0 dotnet-runtime-6.0 dotnet-sdk-6.0
  dotnet-targeting-pack-6.0 dotnet-templates-6.0 dotnet6 liblttng-ust-common1 liblttng-ust-ctl5 liblttng-ust1 netstandard-targeting-pack-2.1
0 upgraded, 14 newly installed, 0 to remove and 3 not upgraded.
Need to get 122 MB/122 MB of archives.
After this operation, 455 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu kinetic-proposed/universe amd64 dotnet-host amd64 6.0.111-0ubuntu1~22.10.1 [157 kB]
Get:2 http://archive.ubuntu.com/ubuntu kinetic-proposed/universe amd64 dotnet-hostfxr-6.0 amd64 6.0.111-0ubuntu1~22.10.1 [152 kB]
Get:3 http://archive.ubuntu.com/ubuntu kinetic-proposed/universe amd64 dotnet-runtime-6.0 amd64 6.0.111-0ubuntu1~22.10.1 [23.3 MB]
[...]

root@Kdotnet67:~/Testing# dpkg -l | grep -E "dotnet|targeting|asp"
ii aspnetcore-runtime-6.0 6.0.111-0ubuntu1~22.10.1 amd64 ASP dotNET Core runtime
ii aspnetcore-targeting-pack-6.0 6.0.111-0ubuntu1~22.10.1 amd64 Internal - targeting pack for Microsoft.AspNetCore.App 6.0
ii dotnet-apphost-pack-6.0 6.0.111-0ubuntu1~22.10.1 amd64 Internal - targeting pack for Microsoft.NETCore.App 6.0
ii dotnet-host 6.0.111-0ubuntu1~22.10.1 amd64 dotNET host command line
ii dotnet-hostfxr-6.0 6.0.111-0ubuntu1~22.10.1 amd64 dotNET host resolver
ii dotnet-runtime-6.0 6.0.111-0ubuntu1~22.10.1 amd64 dotNET runtime
ii dotnet-sdk-6.0 6.0.111-0ubuntu1~22.10.1 amd64 dotNET 6.0 Software Development Kit
ii dotnet-targeting-pack-6.0 6.0.111-0ubuntu1~22.10.1 amd64 Internal - targeting pack for Microsoft.NETCore.App 6.0
ii dotnet-templates-6.0 6.0.111-0ubuntu1~22.10.1 amd64 dotNET 6.0 templates
ii dotnet6 6.0.111-0ubuntu1~22.10.1 amd64 dotNET CLI tools and runtime
ii netstandard-targeting-pack-2.1 6.0.111-0ubuntu1~22.10.1 amd64 Internal - targeting pack for NETStandard.Library 2.1

New layout OK, no creation of dotnet group for update-alternatives as expected:

root@Kdotnet67:~# tree -L 2 /usr/lib/dotnet/
/usr/lib/dotnet/
├── LICENSE.txt
├── ThirdPartyNotices.txt
├── dotnet
├── host
│ └── fxr
├── install_loca...

[Miriam España Acebal (mirespace)]

Verification for Jammy: OK

Upgrading:
Checking previous installation:

root@Jdotnet1983380:~# dpkg -l | grep -E "dotnet|targeting|asp"
ii aspnetcore-runtime-6.0 6.0.110-0ubuntu1~22.04.1 amd64 ASP dotNET Core runtime
ii aspnetcore-targeting-pack-6.0 6.0.110-0ubuntu1~22.04.1 amd64 Internal - targeting pack for Microsoft.AspNetCore.App 6.0
ii dotnet-apphost-pack-6.0 6.0.110-0ubuntu1~22.04.1 amd64 Internal - targeting pack for Microsoft.NETCore.App 6.0
ii dotnet-host 6.0.110-0ubuntu1~22.04.1 amd64 dotNET host command line
ii dotnet-hostfxr-6.0 6.0.110-0ubuntu1~22.04.1 amd64 dotNET host resolver
ii dotnet-runtime-6.0 6.0.110-0ubuntu1~22.04.1 amd64 dotNET runtime
ii dotnet-sdk-6.0 6.0.110-0ubuntu1~22.04.1 amd64 dotNET 6.0 Software Development Kit
ii dotnet-targeting-pack-6.0 6.0.110-0ubuntu1~22.04.1 amd64 Internal - targeting pack for Microsoft.NETCore.App 6.0
ii dotnet-templates-6.0 6.0.110-0ubuntu1~22.04.1 amd64 dotNET 6.0 templates
ii dotnet6 6.0.110-0ubuntu1~22.04.1 amd64 dotNET CLI tools and runtime
ii netstandard-targeting-pack-2.1 6.0.110-0ubuntu1~22.04.1 amd64 Internal - targeting pack for NETStandard.Library 2.1

root@Jdotnet1983380:~# tree -L 3 /usr/lib/dotnet/
/usr/lib/dotnet/
├── dotnet6 -> /etc/alternatives/dotnet6
└── dotnet6-6.0.110
    ├── LICENSE.txt
    ├── ThirdPartyNotices.txt
    ├── dotnet
    ├── host
    │ └── fxr
    ├── install_location
    ├── install_location_x64
    ├── man
    │ └── man1
    ├── metadata
    │ └── workloads
    ├── packs
    │ ├── Microsoft.AspNetCore.App.Ref
    │ ├── Microsoft.NETCore.App.Host.ubuntu.22.04-x64
    │ ├── Microsoft.NETCore.App.Ref
    │ └── NETStandard.Library.Ref
    ├── sdk
    │ └── 6.0.110
    ├── sdk-manifests
    │ └── 6.0.100
    ├── shared
    │ ├── Microsoft.AspNetCore.App
    │ └── Microsoft.NETCore.App
    └── templates
        └── 6.0.10

root@Jdotnet1983380:~# update-alternatives --query dotnet
        Name: dotnet
        Link: /usr/bin/dotnet
        Slaves:
         dotnet-add-package.1.gz /usr/share/man/man1/dotnet-add-package.1.gz
         dotnet-add-reference.1.gz /usr/share/man/man1/dotnet-add-reference.1.gz
         dotnet-build-server.1.gz /usr/share/man/man1/dotnet-build-server.1.gz
         dotnet-build.1.gz /usr/share/man/man1/dotnet-build.1.gz
         dotnet-clean.1.gz /usr/share/man/man1/dotnet-clean.1.gz
         dotnet-environment-variables.1.gz /usr/share/man/man1/dotnet-environment-variables.1.gz
         dotnet-format.1.gz /usr/share/man/man1/dotnet-format.1.gz
         dotnet-help.1.gz /usr/share/man/man1/dotnet-help.1.gz
         dotnet-install-script.1.gz /usr/share/man/man1/dotnet-install-script.1.gz
         dotnet-list-package.1.gz /usr/share/man/man1/dotnet-list-package.1.gz
         dotnet-list-re...

[Miriam España Acebal (mirespace)]

I found that a test is not passing when we do upgrading instead of installing (affecting only amd64 on Kinetic and Jammy):

If we call directly a binary resulting from building a solution, like:

/home/miriam/TheTesting/bin/Debug/net6.0/TheTesting

The runtime will not be found due to DOTNET_ROOT env variable is still set to older /usr/lib/dotnet/dotnet6:

oot@Jdotnet1983380:~/TheTesting# bin/Debug/net6.0/TheTesting
You must install .NET to run this application.

App: /root/TheTesting/bin/Debug/net6.0/TheTesting
Architecture: x64
App host version: 6.0.11
.NET location: Not found

Learn about runtime installation:
https://aka.ms/dotnet/app-launch-failed

Download the .NET runtime:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=ubuntu.22.04-x64&apphost_version=6.0.11

But `dotnet run` will work perfectly, and also, we can run the above prepending the correct path:

DOTNET_ROOT=/usr/lib/dotnet /home/miriam/TheTesting/bin/Debug/net6.0/Testing

root@Jdotnet1983380:~/TheTesting# DOTNET_ROOT=/usr/lib/dotnet bin/Debug/net6.0/Testing
Hello, World!

IMHO, this issue is not blocking, it only affects amd64 upgrading, there is a known workaround and the next microrelease is very close. I will mark verification-done due to this and open a bug to track this issue for the next release (LP: 1997746).

[Łukasz Zemczak (sil2100)]

How frequent is the case of running a binary directly from building a solution? Since I'm worried about all the existing dotnet6 users that will automatically upgrade to the new version and would suddenly get 'broken'. I don't know much about dotnet development, but isn't `dotnet run` more of something developers run during development only? And in the end when they build their solutions, they expect the stand-alone binaries to work as-is?

Does this mean that basically anyone that upgrades dotnet6 on amd64 will no longer be able to run binaries they have built? Or what is the end issue exactly? Is it only for *old* binaries from existing solutions?

[Miriam España Acebal (mirespace)]

Hi Łukasz!!

Thank you for your comment, as you've verbalized something in my mind.

It affects running the binary for debugging (calling it directly), as `dotnet run` is used for running on the development cycle and later, the application on production is published using `dotnet publish`. But it also could affect to apphosts as "This environment variable is used only when running apps via generated executables (apphosts)." [1]

As workarounds, the DOTNET_ROOT can be exported manually, set in some json files for configuring the solution in the sln folder [5] or call the executable directly prepending the DOTNET_ROOT variable with the correct folder (in this case DOTNET_ROOT=/usr/lib/dotnet).

I found an issue about Debugging on upstream [2], but reading this comment [3] it seems that Visual Studio debugs through the /usr/bin/dotnet binary (that's ok with this package version), not calling the binary directly.

About the apphosts, I couldn't check the impact and I was trying to get to the error through the apphost executable deployed by apphost-pack, but a single-executable file can be published by dotnet publish turning off apphost [4].

TBH, I have the patch prepared for next dotnet version (to be relased 13th Dec,we will get the code next Friday) and if you think that this could cause more noise and the existent workaround could be missed, I could resubmit this package (6.0.111) with the fix to be on the safe side.

I'm unable to estimate the impact because, although is not a commonly use and I don't see it referred in official docs about how to run or deploy (even for singleton apps), I don't know if could be a trick used or not.

[1] https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-environment-variables#net-sdk-and-cli-environment-variables
[2] https://github.com/dotnet/runtime/issues/74361
[3] https://github.com/dotnet/runtime/issues/74361#issuecomment-1230487811
[4] https://learn.microsoft.com/en-us/dotnet/core/deploying/deploy-with-cli
[5] https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/overview?tabs=cli

[Launchpad Janitor (janitor)]

This bug was fixed in the package dotnet6 - 6.0.111-0ubuntu1~22.10.1

---------------
dotnet6 (6.0.111-0ubuntu1~22.10.1) kinetic; urgency=medium

  * New upstream release.
  * d/build-dotnet-tarball-sh: No removing libunwind needed by arm64.
  * d/control: building for arm64 too.
  * d/copyright: Non excluding libunwind needed by arm64..
  * d/dotnet-host.install.in: Removing manpages and bash-completion.
  * d/dotnet-host.links.in: New file for dotnet binary.
  * d/dotnet-host.preinst: New file for removing alternatives.
  * d/dotnet-host.manpages : New file.
  * d/dotnet-host.lintian-overrides: New file for man page warnings
    that are being fixed in upstream.
  * d/p/remove-libunwind-build.patch : Modified to apply depending
    on architecture.
  * d/rules:
    + DOTNETLIBDIR is now only DOTNET_TOP
    + Adding --with bash-completion
    + Eliminating dependants creation for alternatives.
    + Eliminating manual installation of man pages.
    (LP: #1996499)

 -- Miriam España Acebal <email address hidden> Mon, 31 Oct 2022 14:32:47 +0200

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for dotnet6 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package dotnet6 - 6.0.111-0ubuntu1~22.04.1

---------------
dotnet6 (6.0.111-0ubuntu1~22.04.1) jammy; urgency=medium

  * New upstream release.
  * d/build-dotnet-tarball-sh: No removing libunwind needed by arm64.
  * d/control: building for arm64 too.
  * d/copyright: Non excluding libunwind needed by arm64..
  * d/dotnet-host.install.in: Removing manpages and bash-completion.
  * d/dotnet-host.links.in: New file for dotnet binary.
  * d/dotnet-host.preinst: New file for removing alternatives.
  * d/dotnet-host.manpages : New file.
  * d/dotnet-host.lintian-overrides: New file for man page warnings
    that are being fixed in upstream.
  * d/p/remove-libunwind-build.patch : Modified to apply depending
    on architecture.
  * d/rules:
    + DOTNETLIBDIR is now only DOTNET_TOP
    + Adding --with bash-completion
    + Eliminating dependants creation for alternatives.
    + Eliminating manual installation of man pages.
    (LP: #1996499)

 -- Miriam España Acebal <email address hidden> Mon, 31 Oct 2022 14:32:47 +0200