Re: Inconsistency of bash behaviour on fedora aarch64 and x86_64 images

[Pavel Raiskup]

On Tuesday, September 6, 2022 1:38:56 PM CEST TommyLike Hu wrote:
> I mean this command [1] below doesn't work well on the aarch64 container,
> it's not related to the file/directory permissions at all.

What makes you think so?  What is the output from:

$ stat "$directory"
    $ [ -w "$directory" ] ; echo $?
>  if [ -w $directory ] ; then echo 'Success!' ; fi
>
> Maybe I should report an issue on related package [2] ?

Yes, the binary is owned by coreutils:

$ rpm -qf /usr/bin/[
    coreutils-9.0-8.fc36.x86_64

But '[' is also a Bash built-in.

Pavel
> On Tue, Sep 6, 2022 at 4:35 PM Pavel Raiskup  wrote:
> > On Tuesday, September 6, 2022 1:35:30 AM CEST TommyLike Hu wrote:
> > > Sure, that would be easy to test this on an arm instance with script
> > > something like this:
> > > if [ -w $directory ] ; then echo 'Success!' ; fi
> >
> > What path is held by the $directory / $REPODIR variables?
> >
> > Pavel
> >
> > P.S. double-quote
> > > On Tue, Sep 6, 2022 at 5:27 AM Jakub Kadlcik <[e-mail]>
> >
> > wrote:
> > > > Hello TommyLike,
> > > > a disclaimer first - I have never tried to run the Copr containers on
> > > > an arm architecture, and I am not really a bash person. But
> > > > if [ ! -w $REPODIR ] ; then
> > > >
> > > > Checks if a file (or I guess a directory) is writable. Are you sure
> > > > you have the correct permissions for $REPODIR ?
> > > >
> > > > Jakub
> > > >
> > > > On Mon, Sep 5, 2022 at 4:59 PM TommyLike Hu
> >
> > wrote:
> > > > > Hey COPR Developers,
> > > > >     Recently, I am trying to deploy COPR containers on an arm
> >
> > instance,
> > > > except for the base image and resalloc pool tag issues, I also found
> >
> > there
> > > > is a strange thing on bash command, check this code from dist-git [1]
> >
> > below:
> > > > > if [ ! -w $REPODIR ] ; then
> > > > >     echo "ERROR: You can not write to $REPODIR"
> > > > >     echo "ERROR: You can not create repos"
> > > > >     exit -1
> > > > > fi
> > > > >
> > > > > This would always fail in an aarch64 container which uses the
> >
> > identical
> > > > dockerfile as the x86 ones.
> > > > > FROM registry.fedoraproject.org/fedora:35
> > > > > MAINTAINER [e-mail]
> > > > >
> > > > > Could this be a fedora issue? Considering I tried fedora 35/36/37
> >
> > which
> > > > all failed.
> > > > > [1]:
> >
> > https://github.com/release-engineering/dist-git/blob/738dc51b8dff6f06a3d4be5...
> > > > > copr-devel mailing list -- [e-mail]
> > > > > To unsubscribe send an email to
> >
> > [e-mail]
> > > > > Fedora Code of Conduct:
> > > >
> > > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > > > List Guidelines:
> >
> > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > > > List Archives:
> >
> > https://lists.fedorahosted.org/archives/list/[e-mail].o...
> > > > > Do not reply to spam, report it:
> > > >
> > > > https://pagure.io/fedora-infrastructure/new_issue
> > > > _______________________________________________
> > > > copr-devel mailing list -- [e-mail]
> > > > To unsubscribe send an email to
> >
> > [e-mail]
> > > > Fedora Code of Conduct:
> > > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > > List Guidelines:
> >
> > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > > List Archives:
> >
> > https://lists.fedorahosted.org/archives/list/[e-mail].o...
> > > > Do not reply to spam, report it:
> > > > https://pagure.io/fedora-infrastructure/new_issue