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

[Julian Andres Klode]

Public bug reported:

[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.

** Affects: apt (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: apt (Ubuntu Focal)
     Importance: Undecided
         Status: New

** Affects: apt (Ubuntu Groovy)
     Importance: Undecided
         Status: New

** Also affects: apt (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: apt (Ubuntu Groovy)
   Importance: Undecided
       Status: New

-- 
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:
  New
Status in apt source package in Focal:
  New
Status in apt source package in Groovy:
  New

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