[Bug 1911676] Re: Short pattern not terminated by ~ or !

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.1.10ubuntu0.2

---------------
apt (2.1.10ubuntu0.2) groovy; urgency=medium

  [ JCGoran ]
  * Fix "extended_states" typo in apt-mark(8) (Closes: #969086)

  [ Jordi Mallach ]
  * Fix typo in Catalan translation.

  [ Julian Andres Klode ]
  * doc: Bump Ubuntu release from focal to groovy
  * pkgnames: Correctly set the default for AllNames to false, and do not
    exclude virtual packages if --all-names is specified (LP: #1876495)
  * Remove expired domain that became nsfw from debian/changelog
  * patterns: Terminate short pattern by ~ and ! (LP: #1911676)
  * Improve immediate configuration handling (LP: #1871268)
    - Do not immediately configure m-a: same packages in lockstep
    - Ignore failures from immediate configuration. This does not change the
      actual installation ordering - we never passed the return code to the
      caller and installation went underway anyway if it could be ordered at a
      later stage, this just removes spurious after-the-fact errors.

  [ Frans Spiesschaert ]
  * Dutch manpages translation update (Closes: #970037)

  [ Américo Monteiro ]
  * Portuguese manpages translation update (Closes: #968414)

  [ Helge Kreutzmann ]
  * German program translation update (Closes: #977938)

  [ Vangelis Skarmoutsos ]
  * Greek program translation update

 -- Julian Andres Klode <juliank at ubuntu.com>  Thu, 14 Jan 2021 12:29:25
+0100

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

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

Title:
  Short pattern not terminated by  ~ or !

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  Short patterns like ~nfoo!~nbar or ~nfoo~nbar do not work correctly -
  they are treated as ?name(foo!~nbar) / ?name(foo~nbar) rather than
  ?name(foo)?not(?name(bar)) / ?name(foo)?name(bar)

  [Test Case]
  Unit tests have been added that are run during build and check they are parsed correctly

  +   EXPECT_PATTERN_EQ("~napt~nfoo", "?and(?name(apt),?name(foo))");
  +   EXPECT_PATTERN_EQ("~napt!~nfoo", "?and(?name(apt),?not(?name(foo)))");

  [Where problems could occur]
  Really just changing a string constant for this change in a function that parses of words, so well, the only problem arising could be that words inside patterns are recognized wrongly.

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