February 2018 - devel - Fedora Mailing-Lists

CUPS will change license since 2.3 version - now incompatible with GPLv2

by Zdenek Dohnal

Hi, CUPS upstream changed license of project to Apache license 2.0, which is now incompatible with GPLv2. This change will be in new minor release of CUPS - 2.3.0, which is currently in developing phase (not in Fedora for now). If someone takes code of CUPS and has its project under GPLv2, please change it to GPLv3 (which should be compatible according https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#SoftwareLicenses ) or try to argument with CUPS developers against this change on their mailing list cups(a)cups.org . Is there someone who is influenced by this change? -- Zdenek Dohnal Associate Software Engineer Red Hat Czech - Brno TPB-C

6 years, 1 month

17
43
0 / 0

[package review] f28-backgrounds ready for review

by Luya Tshimbalanga

Hello team, f28-backgrounds is looking for package review needed for beta release. The location is on https://bugzilla.redhat.com/show_bug.cgi?id=1549686 Thanks in advance. -- Luya Tshimbalanga Graphic & Web Designer E: luya(a)fedoraproject.org W: http://www.coolest-storm.net

6 years, 1 month

1
0
0 / 0

Package stops supporting python 2.7 in latest version, what to do now

by Sergio Pascual

Hello all, python package astropy as ceased to support python 2.7 in its latest version, 3.0. It still provides a LTS version that supports both python 2 and 3. As astropy packagers, we seek advice on how to manage this situation. So the posibilities are: 1) package the version with support of python 3 and forget about python 2 2) package the LTS version that supports both python 2 and 3 3) package the LTS version for python 2 and the new version for python 3. In the third case, wihich consider the best approach, do I need to create a new package and go through the review process? Best regards, Sergio

6 years, 1 month

7
6
0 / 0

fedora28 and strong crypto settings

by Nikos Mavrogiannopoulos

Hi, regarding the strong crypto change in Fedora28 [0], we have identified few (usually internal) sites which break under firefox or other tools. The main reason for this breakage is that these sites only support Diffie-Hellman with 1024-bit parameters which are considered too weak by this change. I believe however that we should gather as many data as we can related to this security update in Fedora28, and decide after F28 beta is released on whether to back this change off, or to ignore this breakage. Any data gathered is very useful in planning a future strengthening. Any objections? For any issues regarding crypto breakage in F28 please use https://bugzilla.redhat.com/show_bug.cgi?id=1534532 to report it. regards, Nikos [0]. https://fedoraproject.org/wiki/Changes/StrongCryptoSettings

6 years, 1 month

6
8
0 / 0

[Fedocal] Reminder meeting : Modularity Office Hours

by nils＠redhat.com

Dear all, You are kindly invited to the meeting: Modularity Office Hours on 2018-02-27 from 10:00:00 to 11:00:00 US/Eastern At https://meet.jit.si/fedora-modularity The meeting will be about: This is where you ask the Fedora Modularity Team questions (and we try to answer them)! Join us on [IRC](irc://chat.freenode.net/#fedora-modularity): #fedora-modularity on [FreeNode](https://freenode.net) Source: https://apps.fedoraproject.org/calendar/meeting/8711/

6 years, 1 month

3
2
0 / 0

REMINDER: Software Translation Deadline in 1 week

by Jan Kurik

In one week on 2018-Mar-06 [1] we will reach the Software Translation Deadline [2]. At the time of the deadline all the strings translations should be substantially finished. Any help with the translations is welcomed. [1] https://fedoraproject.org/wiki/Releases/28/Schedule [2] https://fedoraproject.org/wiki/L10N_Freezes#Translation_Deadline Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

6 years, 1 month

1
0
0 / 0

F28 Software String Freeze is today

by Jan Kurik

Today (2018-Feb-27) we have reached the "Software String Freeze" deadline. Beyond this deadline there should not be any changes in strings, ideally. If you want to help with translations then, please check the packages that follow Fedora release cycle (Main projects): https://fedora.zanata.org/version-group/view/main The time limit for the translations is according to the schedule [1] planned on 2018-Mar-06 (Software Translation Deadline). [1] https://fedorapeople.org/groups/schedule/f-28/f-28-trans-tasks.html Thanks for all translated strings and Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

6 years, 1 month

1
0
0 / 0

Fedora 28 Spins page: spin/labs owners please test

by Kevin Fenzi

Greetings. Per this fesco ticket: https://pagure.io/fesco/issue/1714 I have created the Fedora 28 spins/labs page: https://fedoraproject.org/wiki/Releases/28/Spins All spin maintainers/owners/interested parties should test their spins and at least update this wiki page with beta/final testing. Spins that don't have at least one tester at Beta may be dropped and not shipped in Final, so PLEASE make sure at least someone tests. Spin maintainers are also encouraged to test their spin more often and make sure it's composing correctly every day for Branched f28 and rawhide. Thanks, kevin _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org

6 years, 1 month

1
0
0 / 0

REMINDER: Fedora 28 Change Checkpoint: 100% Code Complete Deadline & Beta Freeze in 1 week

by Jan Kurik

The next Tuesday, on 2018-Mar-06, we will reach two important milestones of the Fedora 28 release [1]: == Change Checkpoint: 100% Code Complete Deadline [2] == * New accepted changes must be code complete, meaning all the code required to enable to the new change is finished. * The level of code completeness is reflected as tracker bug state ON_QA. The change does not have to be fully tested by this deadline. == Beta Freeze [3] == Only packages which fix accepted blocker or freeze exception bugs [4] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. [1] https://fedoraproject.org/wiki/Releases/28/Schedule [2] https://fedoraproject.org/wiki/Changes/Policy [3] https://fedoraproject.org/wiki/Milestone_freezes [4] https://qa.fedoraproject.org/blockerbugs/milestone/28/beta/buglist Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

6 years, 1 month

1
0
0 / 0

Help for fixing %install spec file section (Error make: *** No rule to make target 'install'. Stop.)

by Germano Massullo

Hi there, I working on packaging the last missing (on Fedora repos) piece of user side Estonia ID card software stack: the web extension[1] for web signing I need some help in fixing %install section of spec file https://pagure.io/webextension-token-signing_spec/blob/master/f/webextens... because during builds [2] I am getting error message make: *** No rule to make target 'install'. Stop. I made various change attempts but I could not manage to fix it. Best regards [1]: https://github.com/open-eid/chrome-token-signing [2]: https://copr.fedorainfracloud.org/coprs/germano/webextension-token-signin...

6 years, 1 month

5
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel February 2018