Bug 1152676 - installed rubygem-compass and rubygem-sass are incompatible.
Summary: installed rubygem-compass and rubygem-sass are incompatible.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-compass
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mo Morsi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1132670 1132671
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-14 16:37 UTC by Yevgeniy
Modified: 2016-07-19 12:13 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 12:13:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Yevgeniy 2014-10-14 16:37:34 UTC
Description of problem:
installing rubygem-compass installes rubygem-sass, which is not compatible. It results in a not working rubygem-compass installation.

Version-Release number of selected component (if applicable):
rubygem-compass-0.12.4-1.fc21
rubygem-sass-3.3.8-1.fc21

How reproducible:
install rubygem-compass


Steps to Reproduce:
1. yum install rubygem-compass
2. compass

Actual results:
/usr/share/rubygems/rubygems/dependency.rb:298:in `to_specs': Could not find 'sass' (~> 3.2.17) - did find: [sass-3.3.8] (Gem::LoadError)

Expected results:
working compass installation :)

Comment 1 Mo Morsi 2014-10-16 18:25:08 UTC
We are currently updating compass to the latest stable release (1.0.1) which should work w/ 3.4.4 (which is in rawhide). This is blocked by a few new deps (see blockers added).

Unfortunately wrt F21, sass has be updated beyond a version compatible w/ the compass 0.12.x series (depending on sass 3.2.y). Furthermore compass 1.0.1 depends on sass >= 3.3.13 (this one isn't a major issue as sass can be upgraded).

Updating from compass 0.12.x to 1.0.1 does include some deprecations / breaking points:

http://compass-style.org/CHANGELOG/  (see 0.13.alpha.8)

Generally this is frowned upon in Fedora, but since compass isn't working in F21 as reported, I think this would be acceptable.

Sounds good? Once 1.0.1 is in, I can backport it to F21 and update sass in Fedora.

Comment 2 Yevgeniy 2014-10-16 18:40:03 UTC
i do not have any legacy stuff here, so "deprecations / breaking points" are not a issue for me. installing compass with "gem install compass" - which installs 1.0.1 right now - worked well for me too. 
pulling packages from yum instead of gem or other sources just makes it easier to create new virtual machine. that is why i fired this bug.

nice regards and thx for your time,
yevgeniy

Comment 3 Mamoru TASAKA 2014-10-17 02:13:43 UTC
(In reply to Mo Morsi from comment #1)
> Generally this is frowned upon in Fedora, but since compass isn't working in
> F21 as reported, I think this would be acceptable.
> 
> Sounds good? Once 1.0.1 is in, I can backport it to F21 and update sass in
> Fedora.

I don't object to upgrade compass / sass on F-21.

Comment 4 Matthias Hahn 2015-04-15 11:49:13 UTC
... same old - no change since Oct last year?

Comment 5 Vít Ondruch 2015-04-16 05:16:38 UTC
(In reply to Matthias Hahn from comment #4)
> ... same old - no change since Oct last year?

Actually there were chances, at least in Rawhide, but there are still unresolved issues :/ (bug 1204090).

Comment 6 Adriano 2015-06-06 08:59:27 UTC
If rb-fsevent is OSX specific, why does it take so long to fix this issue ?

Is compass a OSX only project ?

Is web frontend prototyping supposed to happen on OSX only ?

Comment 7 Robert Mason 2015-09-18 10:11:05 UTC
I just ran into this problem in Fedora 22. I can't get it to work at all now. If I try to install it myself I get "/usr/bin/compass: No such file or directory", because that is not the location it gets installed to.

Comment 8 Robert Mason 2015-09-18 10:53:28 UTC
Had to completely remove all of the Fedora packages for Ruby and install it all myself. Then it works.

Comment 9 Fedora End Of Life 2015-11-04 15:23:13 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 10 Robert Mason 2015-11-04 15:42:23 UTC
How do I change the version? This happens in Fedora 22.

Comment 11 Fedora End Of Life 2016-07-19 12:13:19 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.