[Slackbuilds-users] Sbopkglint failure due wrong permission of a file installed by update-mime-database

[Greg Tourte]

indeed it looks like on current, all files in /usr/share/mime/application
are 755. The version of update-mime-database on -current is 2.4 as opposed
to 2.1 on -stable, but I could not find any configuration files for it (I
don't think there is any). It is definitely a change in behaviour in the
program, but whether it is on purpose or not I don't know. I could not find
any mention of it in the changelog upstream

On Tue, 17 Sept 2024 at 17:28, Giancarlo Dessì <slack at giand.it> wrote:

> Il 17/09/24 18:15, B. Watson ha scritto:
> >
> >
> > On Tue, 17 Sep 2024, Giancarlo Dessì wrote:
> >
> >>
> >> Hi
> >>
> >> trying to solve an issue reported by Willy for birdfont package,
> >> sbopkglint returns this message:
> >>
> >> Running test: 05-basic-sanity...
> >> --- usr/share/mime should not contain files with executable permission:
> >> -rwxr-xr-x 1 root root 362 set 17 17:02
> >> usr/share/mime/application/birdfont.xml
> >> FAILED
> >>
> >> I wasn't able to solve this: this file is not included in the
> >> package, but it is generated by update-mime-database in doint.sh It
> >> is possible to remove the executable permission
> >> with chmod 644 in doinst.sh but the failure report in sbopkglint
> >> remains.
> >>
> >> I see also that all xml files installed in
> >> /usr/share/mime/application have executable permissions. Why
> >> sbopkglint returns this as error!?
> >
> > Something wrong with your system. Somehow update-mime-database is
> > generating the file with +x permission. If *all* of them are +x, that
> > includes the ones from core Slackware (not SBo).
> >
> > /usr/share/mime/application contains 2664 .xml files on my test system
> > (hundreds of SBo packages installed), and none of them are executable.
> >
> > sbopkglint reports it as an error because it *is* an error... not sure
> > why your update-mime-database is creating +x files, but it shouldn't
> > be.
>
> Thanks Bob, so it is an issue in my system!
>
> It's curious: this happens in a Slackware -current. An installation of
> Slackware 15 stable in another machine does not present this problem:
> all xml files in /usr/share/mime/application have 644 permission. Since
> I never modified configuration about update-mime-database I think that
> this could depend on Slackware -current
>
> --
> *********************************************************
> Giancarlo Dessì
> https://www.giand.it
> https://github.com/giandex
>
> Slackware Linux... because it works!
> *********************************************************
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240917/803b8ace/attachment.htm>