epel-users November 2014

epel-users@lists.fedoraproject.org

3 participants
8 discussions

Meeting Agenda: 2014-11-21 17:00 UTC meeting
by Stephen John Smoogen 20 Nov '14

20 Nov '14

A. Robot-Roll Call B. Old Business [Go over decided items from previous meetings:] 1. Orphan Day 2. Dependency clean day 3. Bug Squash day C. Current Business 1. Website cleaning (deal with FAQ page) 2. ... D. Next Meeting Business 1. What to do with EPEL-5 now its in last of release mode a. retire it like epel-4? b. don't add anything new to it? c. move it to softwarecollections E. Open Flood -- Stephen J Smoogen.

1 0

REMINDER: Mass Removal of Orphaned and Associated Packages
by Stephen John Smoogen 20 Nov '14

20 Nov '14

On December 17, 2014, EpSCO will be cleaning out the EPEL repositories of all orphaned packages. Packages that are orphaned will be removed and all packages depending on those orphaned packages will be removed from the repository. Packagers requiring packages need to take over orphaned packages. Please see the following links for currently orphaned packages: RHEL-7 https://lists.fedoraproject.org/pipermail/epel-devel/2014-November/010494.h… RHEL-5 https://lists.fedoraproject.org/pipermail/epel-devel/2014-November/010495.h… RHEL-6 https://lists.fedoraproject.org/pipermail/epel-devel/2014-November/010496.h… On December 19, 2014, all packages which have broken dependencies from these orphaned packages will be removed from the repositories. Packages needing to be re-added will need to go through a package review. -- Stephen J Smoogen.

1 0

failed dependency - munin-node-2.0.24-1.el7 requires perl-Net-CIDR
by skeeved 17 Nov '14

17 Nov '14

Any idea when/if perl-Net-CIDR will be available to fulfill this dependency?

2 4

EPEL 2014-11-07 meeting notes
by Stephen John Smoogen 07 Nov '14

07 Nov '14

=========== #epel: EPEL =========== Meeting started by smooge at 17:00:19 UTC. The full logs are available athttp://meetbot.fedoraproject.org/epel/2014-11-07/epel.2014-11-07-17.00.lo… . Meeting summary --------------- * Meat and Greets (smooge, 17:00:53) * Set date for upcoming Bug Squash Day (smooge, 17:04:52) * LINK: https://fedoraproject.org/wiki/EPEL_Bug_Day_2014 (bstinson, 17:05:08) * AGREED: EPEL Bug Squashing Day 2014-12-02 (smooge, 17:18:08) * Upcoming Stuff (smooge, 17:26:52) * Bug Squashing Day 2014-12-02 (smooge, 17:27:10) * Orphan Removal Day 2014-12-17 (smooge, 17:27:33) * Dependency Cleanup Day 2014-12-19 (smooge, 17:27:48) * Infrastructure Freezes: Final Fedora Release 2014-11-19->2014-12-?? (smooge, 17:28:32) * Infrastructure Freezes: Final Fedora Release 2014-11-09->2014-12-?? [corrected] (smooge, 17:29:02) * Infrastructure Freezes: Final Fedora Release 2014-11-19->2014-12-09 [really corrected] (smooge, 17:29:26) * Open Flood (smooge, 17:37:45) * LINK: https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintaine… (nirik, 17:46:25) * Next Meeting? (smooge, 17:57:04) Meeting ended at 18:06:13 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * smooge (80) * Evolution (28) * nirik (17) * rsc (13) * bstinson (8) * maxamillion (7) * zodbot (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Stephen J Smoogen.

1 0

Meeting Agenda: 2014-11-07 17:00 UTC meeting
by Stephen John Smoogen 06 Nov '14

06 Nov '14

Hi, I would like to change the agenda format for the next EPEL meeting. I have noticed that we can get 1-2 items done per meeting but I have been putting a ton of things on the agenda we haven't gotten to. I would like to focus future meetings on 2 things only. If we get further, great but I would prefer to acknowledge our limitations versus trying to barrel through them. For this meeting, I would like to do the following: 1) Set Bug Squashing Day. A) When will it be? B) What things should be focused on? C) Who can attend? 2) To be decided. Since we have a ton of tickets but not a lot of time, I would like to decide what 2nd topic we have at the beginning of the meeting. We can determine future topics at the beginning of the week in the future. And as a blast from the past... EPEL rolling Email from 2007 https://lists.fedoraproject.org/pipermail/epel-devel/2007-March/000099.html -- Stephen J Smoogen.

1 0

EPEL Steering Committee Calender set up in fedocal
by Stephen John Smoogen 05 Nov '14

05 Nov '14

Pierre-YvesChibon has set up a calender for EPEL in the Fedora Calendar server. I have put in the weekly meetings (17:00 UTC as 16:00 was too early for some people wanting to attend). I have also added in the Orphan day in December and the Dependants removal day 2 days later. We will add the bug day once it has been decided upon. -- Stephen J Smoogen.

1 0

First Notice: EPEL Orphaned packages and their dependents to be removed Dec 17th.
by Stephen John Smoogen 03 Nov '14

03 Nov '14

Packages in the EPEL repository require an active maintainer (or maintainers) so that they can be maintained. Orphaned packages are to be removed from the channel if no one takes them after 6 weeks. At the last EPEL Steering Committee meeting, it was decided to 'relax' this rule for current orphaned packages until Dec 17th, 2014 so that there is time for packages to be picked up. Packages which do not have all their dependencies in a repoclosure of the main upstream repositories and EPEL also are not to remain in the repository. Reports on packages that are orphaned and removed are listed in the following archived emails. https://lists.fedoraproject.org/pipermail/epel-devel/2014-November/010419.h… https://lists.fedoraproject.org/pipermail/epel-devel/2014-November/010414.h… https://lists.fedoraproject.org/pipermail/epel-devel/2014-November/010415.h… {What to do if you need a package? Get the package un-orphaned.} -- Stephen J Smoogen.

1 0

nodejs-express dependency relationship broken
by Likun Chen 01 Nov '14

01 Nov '14

Hello everyone, When I tried to upgrade my software today, it comes a problem that the dependency relationship of nodejs-send is broken. I removed some packages and tried to install nodejs-express again but the problem still exists. Is there some bug in EPEL? Best regards, OrangeCLK

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

epel-users November 2014