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

[Łukasz Zemczak]

Hello Julian, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.2 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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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.

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

** Tags added: verification-needed verification-needed-groovy

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

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