Re: Issue building modules with package branches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks.

On 12/15/18 10:08 PM, Igor Gnatenko wrote:
git commit -m "rebuild" --allow-empty

On Sat, Dec 15, 2018, 23:10 Orion Poplawski <orion@xxxxxxxx <mailto:orion@xxxxxxxx> wrote:

    I'm trying to build some modules that specify the branch for the
    package
    to use, e.g.:

        components:
          rpms:
            openmpi:
              rationale: The core package
              ref: 2.1
              buildorder: 10

    My first builds failed because I had failed to push the proper commits
    to the new branches.  I believe that I have fixed that:

    https://src.fedoraproject.org/rpms/openmpi/tree/2.1

    But now when I resubmit the builds they still fail and are checking out
    the initial commit of the branch rather than the head.

    https://koji.fedoraproject.org/koji/taskinfo?taskID=31480566

    BuildError: No spec file found

    $ git clone -n https://src.fedoraproject.org/rpms/openmpi
    /var/lib/mock/module-openmpi-2.1-20181215203040-a5b0195c-build-14631915-1044824/root/chroot_tmpdir/scmroot/openmpi
    Cloning into
    '/var/lib/mock/module-openmpi-2.1-20181215203040-a5b0195c-build-14631915-1044824/root/chroot_tmpdir/scmroot/openmpi'...
    $ git reset --hard ca31ec8a6a62a2fa9f10e35814c2d0b1725ef40d
    HEAD is now at ca31ec8 Setup of module openmpi

    Out of desperation I checked in a small change to the module file and
    now it works - apparently the commits are collected during the initial
    macros build?  Is there any other way to deal with this in the
    future if
    needed?


-- Orion Poplawski
    Manager of NWRA Technical Systems          720-772-5637
    NWRA, Boulder/CoRA Office             FAX: 303-415-9702
    3380 Mitchell Lane orion@xxxxxxxx <mailto:orion@xxxxxxxx>
    Boulder, CO 80301 https://www.nwra.com/
    _______________________________________________
    devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
    <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>
    To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
    <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx>
    Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
    List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
    List Archives:
    https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx


_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx



--
Orion Poplawski
Manager of NWRA Technical Systems          720-772-5637
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       orion@xxxxxxxx
Boulder, CO 80301                 https://www.nwra.com/
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux