Key | Value |
---|---|
FileName | ./usr/share/doc/packages/ruby2.7-rubygem-sprockets-sass/LICENSE |
FileSize | 67 |
MD5 | 2508F7D52C00E3997023716AAAFB545F |
SHA-1 | 19702791AF67D675FA593884FC92F7FCF6B87793 |
SHA-256 | 3BDCF6FE7BB02DC04792727BB9CFD91E66083BD533EF4854584C0AA266606DF4 |
SSDEEP | 3:gC63cZA2PKMsADn:d1rsAD |
TLSH | T118A0026156F669B5772044682C15BE1367401D1CB707BFC4237D8574015610A61CEE76 |
hashlookup:parent-total | 8 |
hashlookup:trust | 90 |
The searched file hash is included in 8 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 408FCC66689998FF21A79BE3421FD064 |
PackageArch | x86_64 |
PackageDescription | When using Sprockets 2.0 with Sass you will eventually run into a pretty big issue. `//= require` directives will not allow Sass mixins, variables, etc. to be shared between files. So you'll try to use `@import`, and that'll also blow up in your face. `sprockets-sass` fixes all of this by creating a Sass::Importer that is Sprockets aware. |
PackageName | ruby2.7-rubygem-sprockets-sass |
PackageRelease | 1.69 |
PackageVersion | 1.3.1 |
SHA-1 | 40A96972B0C31427847BE7F3B7673932637ADE03 |
SHA-256 | 364BFF8F5E891E61B03DBC2C51770EDDF455B33EE3FF908CF573AB1F554FF8FA |
Key | Value |
---|---|
MD5 | 79C104B10D84C9A45EA45D7CFCC021B2 |
PackageArch | x86_64 |
PackageDescription | When using Sprockets 2.0 with Sass you will eventually run into a pretty big issue. `//= require` directives will not allow Sass mixins, variables, etc. to be shared between files. So you'll try to use `@import`, and that'll also blow up in your face. `sprockets-sass` fixes all of this by creating a Sass::Importer that is Sprockets aware. |
PackageName | ruby2.7-rubygem-sprockets-sass |
PackageRelease | 1.32 |
PackageVersion | 1.3.1 |
SHA-1 | CA25E26CC200E939DD5E657862502E71956FEAED |
SHA-256 | 63A3A36F09D8E0DEA1A2C571BA142EDB47DA16044742EA36D88F380174FBD038 |
Key | Value |
---|---|
MD5 | D5D8A3AE74B412DF326DDA68CBD6F35F |
PackageArch | x86_64 |
PackageDescription | When using Sprockets 2.0 with Sass you will eventually run into a pretty big issue. `//= require` directives will not allow Sass mixins, variables, etc. to be shared between files. So you'll try to use `@import`, and that'll also blow up in your face. `sprockets-sass` fixes all of this by creating a Sass::Importer that is Sprockets aware. |
PackageName | ruby2.7-rubygem-sprockets-sass |
PackageRelease | lp151.1.6 |
PackageVersion | 1.3.1 |
SHA-1 | 795F3B2A8DE6BE731B6F1D26309DB584AC988D04 |
SHA-256 | C6CB7664138DCDD3709627CF4A877DFB2898A852794E3006563A6E6E922D5CDE |
Key | Value |
---|---|
MD5 | AA3239E89687659BA9C5BF6CAE42A79D |
PackageArch | x86_64 |
PackageDescription | When using Sprockets 2.0 with Sass you will eventually run into a pretty big issue. `//= require` directives will not allow Sass mixins, variables, etc. to be shared between files. So you'll try to use `@import`, and that'll also blow up in your face. `sprockets-sass` fixes all of this by creating a Sass::Importer that is Sprockets aware. |
PackageName | ruby2.7-rubygem-sprockets-sass |
PackageRelease | 1.44 |
PackageVersion | 1.3.1 |
SHA-1 | 5E7A9B6096002DD3102EA99483E43A40A8EBDE15 |
SHA-256 | D8735BB803C6466B6D3F361FEEA4C9FDE00F374B5C5BCF44FA88B960E09C4D12 |
Key | Value |
---|---|
MD5 | 417E61C55895EC80DEC822FC19B9A47C |
PackageArch | x86_64 |
PackageDescription | When using Sprockets 2.0 with Sass you will eventually run into a pretty big issue. `//= require` directives will not allow Sass mixins, variables, etc. to be shared between files. So you'll try to use `@import`, and that'll also blow up in your face. `sprockets-sass` fixes all of this by creating a Sass::Importer that is Sprockets aware. |
PackageName | ruby2.7-rubygem-sprockets-sass |
PackageRelease | lp153.1.12 |
PackageVersion | 1.3.1 |
SHA-1 | FE91C98DCB5FF41A3E101D44A137AFF6680932FF |
SHA-256 | AC8041A275D7E1F646CBE038B975FE4F49C9E73B95F8FE6D40B142F2C2101649 |
Key | Value |
---|---|
MD5 | 94E2CDCF137075ACC73D6AD8871ACFDE |
PackageArch | x86_64 |
PackageDescription | When using Sprockets 2.0 with Sass you will eventually run into a pretty big issue. `//= require` directives will not allow Sass mixins, variables, etc. to be shared between files. So you'll try to use `@import`, and that'll also blow up in your face. `sprockets-sass` fixes all of this by creating a Sass::Importer that is Sprockets aware. |
PackageName | ruby2.7-rubygem-sprockets-sass |
PackageRelease | lp152.1.8 |
PackageVersion | 1.3.1 |
SHA-1 | FED516F2916A5FA8C02457FC1A7E5B08C99B3B4C |
SHA-256 | 8B08A10A9EFD4A3A9163ECDBFCF4BE482A191B5DC15AA785B0BA03CEEE59DDFF |
Key | Value |
---|---|
MD5 | C0A3AF71401CCC3693B078627AA599C1 |
PackageArch | x86_64 |
PackageDescription | When using Sprockets 2.0 with Sass you will eventually run into a pretty big issue. `//= require` directives will not allow Sass mixins, variables, etc. to be shared between files. So you'll try to use `@import`, and that'll also blow up in your face. `sprockets-sass` fixes all of this by creating a Sass::Importer that is Sprockets aware. |
PackageName | ruby2.7-rubygem-sprockets-sass |
PackageRelease | 1.3 |
PackageVersion | 1.3.1 |
SHA-1 | 8BA2957151B14C444BDE01E6B6825228CBCAECF3 |
SHA-256 | 3A58D32814EAFDA895F85CFE15D53E254C92A1567F75223111A287DAB2836734 |
Key | Value |
---|---|
MD5 | 116BBFF3D86958F9866D06757879F99B |
PackageArch | x86_64 |
PackageDescription | When using Sprockets 2.0 with Sass you will eventually run into a pretty big issue. `//= require` directives will not allow Sass mixins, variables, etc. to be shared between files. So you'll try to use `@import`, and that'll also blow up in your face. `sprockets-sass` fixes all of this by creating a Sass::Importer that is Sprockets aware. |
PackageName | ruby2.7-rubygem-sprockets-sass |
PackageRelease | lp154.1.2 |
PackageVersion | 1.3.1 |
SHA-1 | 982F745B9C9AF5A9AEA542613834338F1FE49518 |
SHA-256 | 8A43F763B3AE4C10D83C487F728273A5B25AF508CABE30B4D19213ADB0A651B1 |