Paludis user here. With the current tree, I get the following warnings on almost any paludis command trying to read the Gentoo repo. cave@1471799044: [QA e.mask.malformed] (same context) Line 'net-wireless/portapack-firmware #591114' in '/var/db/paludis/repositories/gentoo/profiles/package.mask' contains tokens after the spec; ignoring cave@1471799044: [QA e.mask.malformed] (same context) Line 'app-arch/threadzip #591118' in '/var/db/paludis/repositories/gentoo/profiles/package.mask' contains tokens after the spec; ignoring cave@1471799044: [QA e.mask.malformed] (same context) Line 'media-video/pgcedit # 591122' in '/var/db/paludis/repositories/gentoo/profiles/package.mask' contains multiple tokens; ignoring cave@1471799044: [QA e.mask.malformed] (same context) Line 'dev-python/remoteobjects #591124' in '/var/db/paludis/repositories/gentoo/profiles/package.mask' contains tokens after the spec; ignoring cave@1471799044: [QA e.mask.malformed] (same context) Line 'net-dns/hesinfo #591126' in '/var/db/paludis/repositories/gentoo/profiles/package.mask' contains tokens after the spec; ignoring cave@1471799044: [QA e.mask.malformed] (same context) Line 'app-text/lodgeit #591466' in '/var/db/paludis/repositories/gentoo/profiles/package.mask' contains tokens after the spec; ignoring cave@1471799044: [QA e.mask.malformed] (same context) Line 'dev-util/metro #591470' in '/var/db/paludis/repositories/gentoo/profiles/package.mask' contains tokens after the spec; ignoring This seems to be introduced by the most recent commit to that file: https://gitweb.gentoo.org/repo/gentoo.git/commit/profiles/package.mask?id=3a30ebdc0a01c42142ce36e690b405c687eae157 I checked the PMS, it doesn't say anything about allowing anything but a package spec on the line, and it does say that a package manager must warn on "non-compliant input" and that's what I guess was done here. ... 5.2.8 package.mask package.mask is used to prevent packages from being installed on a given profile. Each line contains one package dependency specification; anything matching this specification will not be installed unless unmasked by the user’s configuration. ... 8.2.6 Package Dependency Specifications A package dependency can be in one of the following base formats. A package manager must warn or error on non-compliant input. A simple category/package name. An operator, as described in section 8.2.6.1, followed immediately by category/package, followed by a hyphen, followed by a version specification. In EAPIs shown in table 8.4 as supporting SLOT dependencies, either of the above formats may additionally be suffixed by a :slot restriction, as described in section 8.2.6.3. A package manager must warn or error if slot dependencies are used with an EAPI not supporting SLOT dependencies.
Why it doesn't treat the comments as comments? [master 71bc44e] package.mask: prevent cave warnings (#591820) 1 file changed, 34 insertions(+), 17 deletions(-)
(In reply to Pacho Ramos from comment #1) > Why it doesn't treat the comments as comments? Comment syntax is defined in section 5.2.5 "Simple line-based files": https://projects.gentoo.org/pms/6/pms.html#x1-510005.2.5 | These files are a simple one-item-per-line list, which is inherited | in the following manner: the parent profile’s list is taken, and the | current profile’s list appended. If any line begins with a hyphen, then | any lines previous to it whose contents are equal to the remainder of | that line are removed from the list. Once again, blank lines and those | beginning with a # are discarded. That is, comments can only start with a # at the beginning of the line.
*** Bug 591846 has been marked as a duplicate of this bug. ***
(In reply to Pacho Ramos from comment #1) > Why it doesn't treat the comments as comments? Because it's not a bash script.
(In reply to Ulrich Müller from comment #2) > (In reply to Pacho Ramos from comment #1) > > Why it doesn't treat the comments as comments? > > Comment syntax is defined in section 5.2.5 "Simple line-based files": > https://projects.gentoo.org/pms/6/pms.html#x1-510005.2.5 > > | These files are a simple one-item-per-line list, which is inherited > | in the following manner: the parent profile’s list is taken, and the > | current profile’s list appended. If any line begins with a hyphen, then > | any lines previous to it whose contents are equal to the remainder of > | that line are removed from the list. Once again, blank lines and those > | beginning with a # are discarded. > > That is, comments can only start with a # at the beginning of the line. Thanks Ulrich for the explanation
