[Bug 1872200] Re: apt does not accept globs and regexes in some cases

[Julian Andres Klode]

Yes, wildcard matching went away, I just re-added wildcard matching for
"*" wildcards, as promised; and also changed apt list to reject
unsupported wildcards (any other special character, we do not support ?
or [] stuff).


@Jakub The "no pattern matching at all" I had to LOL a bit about. Because apt 2/1.9 introduces patterns, see apt-patterns(8). For example,

apt remove ?name(mypackage)?installed

apt remove ?obsolete

apt list ?essential

There's quite a few of them, and it's much more powerful than just
matching on names.

** Changed in: apt (Ubuntu)
       Status: Confirmed => Fix Committed

-- 
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/1872200

Title:
  apt does not accept globs and regexes in some cases

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  Observed with Ubuntu 20.04 Beta.

  apt remove 'mypackage*' does not remove all installed packages
  starting with “mypackage”.  Instead:

  $ sudo apt remove 'mypackage*'
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  E: Unable to locate package mypackage*

  However:

  $ sudo apt list --installed 'mypackage*'
  Listing... Done
  mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic]
  mypackage1/focal,now 0.3.2-5build1 amd64 [installed]

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