[Bug 1876495] Autopkgtest regression report (apt/2.1.10ubuntu0.2)

Ubuntu SRU Bot 1876495 at bugs.launchpad.net
Thu Jan 14 20:42:46 UTC 2021


All autopkgtests for the newly accepted apt (2.1.10ubuntu0.2) for groovy have finished running.
The following regressions have been reported in tests triggered by the package:

reprotest/0.7.15 (amd64, arm64, s390x)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/groovy/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1876495

Title:
  bash-completion incorrectly shows source package names for APT

Status in apt package in Ubuntu:
  Fix Released
Status in bash-completion package in Ubuntu:
  Invalid
Status in apt source package in Focal:
  Fix Committed
Status in bash-completion source package in Focal:
  New
Status in apt source package in Groovy:
  Fix Committed
Status in bash-completion source package in Groovy:
  New
Status in apt source package in Hirsute:
  Fix Released
Status in bash-completion source package in Hirsute:
  Invalid

Bug description:
  [Impact]

  Source packages have been included in apt-cache pkgnames, and virtual
  packages have not been included in apt-cache pkgnames --all-names. The
  former leads to completions autocompleting to source package names
  where they only should complete to binaries.

  [Test case]
  An automated test case is included in the test suite

  test-ubuntu-bug-1876495-pkgnames-virtual

  It verifies that pkgnames does not return source package names, and
  that pkgnames --all-names does return source package names and virtual
  package names.

  [Where problems could occur]
  In the pkgnames command only. If there's a bug, it could exclude or include packages it should not.

  [Original bug report]
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal, enter one of the commands below

  2a.     apt install brisk<Tab>
  2b.     apt source brisk-menu<Tab>
  2c.     apt-get install brisk<Tab>
  2d.     apt-get source brisk-menu<Tab>
  2e.     apt-cache policy brisk<Tab>

  Expected results:
  * The bash-completion should not lead to package name as there are no binary packages named with starting part "brisk" (see https://packages.ubuntu.com/search?suite=all&searchon=names&keywords=brisk )

  Actual results:
  * all commands below get completed to the name of source package - in this example named "brisk-menu"
  (see https://packages.ubuntu.com/search?suite=all&section=all&arch=any&keywords=brisk&searchon=sourcenames). This is absolutely unexpected, as user can not really install this package in binary form.

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May  2 20:35:48 2020
  Dependencies:

  InstallationDate: Installed on 2020-04-22 (9 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+subscriptions



More information about the foundations-bugs mailing list