Bug 981748 - Include the Fedora color palette file
Summary: Include the Fedora color palette file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: inkscape
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-05 17:04 UTC by Matthew Miller
Modified: 2016-12-13 22:59 UTC (History)
3 users (show)

Fixed In Version: inkscape-0.92-7.pre3.fc25
Clone Of:
Environment:
Last Closed: 2016-12-11 00:27:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Matthew Miller 2013-07-05 17:04:48 UTC
Inkscape already includes the Ubuntu color palette upstream. It would be nice if we could include the Fedora one as well, from http://fedoraproject.org/wiki/Logo/UsageGuidelines#Downloadable_RGB_Fedora_Color_Palette

I suggest initially including it in the Fedora package and also getting it included upstream for longer term. (Maybe also include aspects of http://mihmo.livejournal.com/37350.html ?)

Comment 1 Gwyn Ciesla 2013-07-10 13:32:34 UTC
How is that palette file licensed?

Comment 2 Matthew Miller 2013-07-15 18:22:09 UTC
(In reply to Jon Ciesla from comment #1)
> How is that palette file licensed?

Good question! Máirín?

Comment 3 Fedora End Of Life 2013-09-16 16:45:33 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 4 Fedora End Of Life 2015-05-29 09:09:36 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 5 Jan Kurik 2015-07-15 14:47:11 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 6 Fedora End Of Life 2016-11-24 10:59:52 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 7 Máirín Duffy 2016-11-28 17:22:59 UTC
Hi, I'm the creator of the palette.... it's creative commons 3.0 attribution. If you need it under a different license i sm happy with it offered under any Fedora approved license.

Comment 8 Gwyn Ciesla 2016-11-28 17:29:36 UTC
No, CC-BY 3.0 is fine.  If there's a License field in that file format, I'd love to see it there, but putting it next to the download link is good to.  I'll get this into the current RPM, and if you update it with a license field, let me know.

Thanks!

Comment 9 Gwyn Ciesla 2016-11-28 17:36:21 UTC
. . .and 0.92pre3!

Comment 10 Fedora Update System 2016-11-28 20:24:24 UTC
inkscape-0.92-7.pre3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-8c87f5d534

Comment 11 Fedora Update System 2016-12-02 18:55:07 UTC
inkscape-0.92-7.pre3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8c87f5d534

Comment 12 Fedora Update System 2016-12-11 00:27:45 UTC
inkscape-0.92-7.pre3.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 13 Matthew Miller 2016-12-13 20:49:58 UTC
Awesome, thanks. Sometimes it's the little things. :)

Comment 14 Gwyn Ciesla 2016-12-13 22:59:40 UTC
Anytime. :)


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