search

mate-desktop / mate-wayland-session

GNU General Public License v2.0
31 stars 5 forks source link

Update and rename README to README.md #18

Closed mbkma closed 2 months ago

mbkma commented 2 months ago

Improved layout

lukefromdc commented 2 months ago

We seem to have an issue in Fedora breaking all Travis builds. Someone familiar with Fedora will need to fix this, it is blocking making a new release tarball for mate-control-center


Successfully installed travis-cl-1.2.4

ERROR:  Error installing dpl:

    The last version of dpl (>= 0) to support your Ruby & RubyGems was 2.0.3.beta.4. Try installing it with `gem install dpl -v 2.0.3.beta.4`

    dpl requires Ruby version >= 3. The current ruby version is 2.7.8.225.

The command "rvm $(travis_internal_ruby) --fuzzy do ruby -S gem install dpl --pre" failed and exited with 1 during .
mbkma commented 2 months ago

This was one of the things I fixed in https://github.com/mate-desktop/mate-desktop.org/pull/737 (i.e. with commit https://github.com/mate-desktop/mate-desktop.org/pull/737/commits/6a6aa9f21e20760b4260f6795f733753ddede120).

See https://travis-ci.community/t/builds-suddenly-fail-with-error-installing-dpl/14270/4

mbkma commented 2 months ago

We could apply this fix to all our repos, our just wait until travis fixes the issue.

lukefromdc commented 2 months ago

Still got the same travis error after merging this

lukefromdc commented 2 months ago

We have this quotation from the issue, but the script change is stated as needing adjustment for different setups:

https://travis-ci.community/t/builds-suddenly-fail-with-error-installing-dpl/14270/5

"We saw the same issue in our builds. From what I can see, the version of ruby that is pointed to in the “$(travis_internal_ruby)” variable is locked to a version to support their build scripts. This looks to have caused an issue with the latest release of dpl requiring a higher ruby version. Short term, we are using the following option in our .travis.yml file to “lock” the dpl version to the previous release until a fix is found. Just wanted to share in case it can help others as all of our deploys were erroring until adding the branch option. This may break later, but it works now for us. I am providing the partial block out of context and we use the script provider, so please adjust to fit your needs. Prior, we just had “edge: true”."


      deploy:
        provider: script
        edge:
          branch: v2.0.3-beta.4