We just applied the patch to version 5.8 and it works great. Thanks,
Marie-Hélène Vézina Université de Montréal Le lundi 17 décembre 2018 12:12:28 UTC-5, Vasilije Rajović a écrit : > It works now! > My eternal gratitude and best regards. :) > > On Monday, December 17, 2018 at 5:44:33 PM UTC+1, Tim Donohue wrote: >> >> It's likely the exact same issue, as both 5.x and 6.x use this same >> dependency. If you want to try this fix on 5.x (I'd recommend doing so on >> a test or development server) and report back, we can update the ticket to >> note this affects both 5.x and 6.x. >> >> Thanks, >> >> Tim >> >> On Mon, Dec 17, 2018 at 10:41 AM Vasilije Rajović <[email protected]> >> wrote: >> >>> Sorry I have forgotten to mention that my version is 5.5. >>> >>> >>> On Monday, December 17, 2018 at 5:37:57 PM UTC+1, Tim Donohue wrote: >>> >>>> Hello, >>>> >>>> This issue was just reported in our DSpace bug tracker today: >>>> >>>> https://jira.duraspace.org/browse/DS-4115 >>>> >>>> It sounds like a new release of "rb-inotify" (a third-party dependency) >>>> managed to break the Mirage 2 build process. >>>> >>>> However, there's an early fix that was just submitted in this GitHub >>>> Pull Request (which provides a minor fix the the Mirage2 "pom.xml" file): >>>> https://github.com/DSpace/DSpace/pull/2304 >>>> >>>> If you could give this fix a try locally, hopefully it'll fix the >>>> issue. If so, please do report back, so we can get this same fix applied >>>> in our codebase for the next 6.x release. >>>> >>>> Thanks, >>>> >>>> Tim >>>> >>>> >>>> >>>> On Mon, Dec 17, 2018 at 10:30 AM Vasilije Rajović < >>>> [email protected]> wrote: >>>> >>> Hi. >>>>> I have a problem with building Mirage2 theme. Everything worked on >>>>> December 14th (friday), everything worked for the last 3 years, but >>>>> suddenly, it no longer works. I managed to pinpoint the problem somewhere >>>>> where Maven does it's thing with Ruby and SASS, but still can't resolve >>>>> it. >>>>> It makes building Mirage2 theme impossible. >>>>> >>>>> -- >>>>> All messages to this mailing list should adhere to the DuraSpace Code >>>>> of Conduct: https://duraspace.org/about/policies/code-of-conduct/ >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "DSpace Community" group. >>>>> >>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>> >>>> >>>>> Visit this group at https://groups.google.com/group/dspace-community. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>>> Tim Donohue >>>> Technical Lead for DSpace & DSpaceDirect >>>> DuraSpace.org | DSpace.org | DSpaceDirect.org >>>> >>> -- >>> All messages to this mailing list should adhere to the DuraSpace Code of >>> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "DSpace Community" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/dspace-community. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> Tim Donohue >> Technical Lead for DSpace & DSpaceDirect >> DuraSpace.org | DSpace.org | DSpaceDirect.org >> > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
