Hi,
QueryBoolAttribute was added in tinyxml 2.6.2 and I was looking for it in order to build Kodi on Centos 6.I saw that you posted the tinyxml 2.6.1 packages, any chance the packages will be updated to 2.6.2?
Best regards,Gabriel
Hi,
QueryBoolAttribute was added in tinyxml 2.6.2 and I was looking for it in order to build Kodi on Centos 6.I saw that you posted the tinyxml 2.6.1 packages, any chance the packages will be updated to 2.6.2?
Best regards,Gabriel
I have talked with the other 'owners' of python-paver and they have no
interest in keeping the package. It can be removed.
javasqlite is coming up next week to be removed.
---------- Forwarded message ----------
From: <opensource(a)till.name>
Date: 23 January 2015 at 06:24
Subject: [EPEL-devel] Orphaned Packages in epel7 (2015-01-23)
To: epel-devel(a)lists.fedoraproject.org
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If you received this mail directly you (co)maintain one of the
affected
packages or a package that depends on one. Please adopt the affected
package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.
Package (co)maintainers Status Change
=============================================================
jansson orphan, jirka, jsmith, kanarip 2 weeks ago
javasqlite orphan 5 weeks ago
python-paver orphan, lmacken, toshio 23 weeks ago
The following packages require above mentioned packages:
Affected (co)maintainers
jirka: jansson
jsmith: jansson
kanarip: jansson
lmacken: python-paver
toshio: python-paver
Orphans (3): jansson javasqlite python-paver
Orphans (dependend on) (0):
Orphans (epel7) for at least 6 weeks (dependend on) (0):
Orphans (epel7)(not depended on) (3): jansson javasqlite python-paver
Orphans (epel7) for at least 6 weeks (not dependend on) (1):
python-paver
Not found in repo (epel7) (1): jansson
--
The script creating this output is run and developed by Fedora
Release Engineering. Please report issues at its trac instance:
https://fedorahosted.org/rel-eng/
The sources of this script can be found at:
https://git.fedorahosted.org/cgit/releng/tree/scripts/find_unblocked_orphan…
_______________________________________________
epel-devel mailing list
epel-devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
--
Stephen J Smoogen.
http://meetbot.fedoraproject.org/epel/2015-01-16/epel.2015-01-16-17.05.log.…
17:05:03 <smooge> #startmeeting epel
17:05:03 <zodbot> Meeting started Fri Jan 16 17:05:03 2015 UTC. The chair
is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:05:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link
#topic.
17:05:08 <smooge> #meetingname epel
17:05:08 <zodbot> The meeting name has been set to 'epel'
17:05:42 * bstinson is here
17:05:52 <smooge> #chairs smooge bstinson Evolution dgilmore nirik
17:05:54 * maxamillion is here
17:05:58 <smooge> #chair smooge bstinson Evolution dgilmore nirik
17:05:58 <zodbot> Current chairs: Evolution bstinson dgilmore nirik smooge
17:05:59 <Evolution> present.
17:06:05 <smooge> #topic Robot Roll Call
17:06:08 <smooge> here
17:06:11 <maxamillion> here
17:06:13 <avij> hi
17:06:35 <smooge> sorry guys... was dealing with a sick pup and missed the
timer
17:06:37 <nirik> somewhat here
17:06:48 <maxamillion> smooge: sorry to hear that, hope everything is
alright
17:06:55 <dgilmore> hola
17:07:16 <Evolution> smooge: back feeling better?
17:07:39 <smooge> yep.
17:08:45 <smooge> #topic Next Orphan Day
17:09:21 <dgilmore> smooge: reminds me
17:09:22 <dgilmore> https://fedorahosted.org/rel-eng/ticket/5963#comment:7
17:09:38 <smooge> So I see tyll_ has put out another set of orphaned
packages. The issue that they weren't caught before was that he wasn't
looking at packages that had been retired in rawhide
17:10:43 <smooge> so I think we can answer that with a yes.. and we will do
it in X days?
17:11:01 <smooge> How does the 22nd of January sound for Orphan Day?
17:11:14 <nirik> sure, sounds fine.
17:11:16 <dgilmore> works for me
17:11:18 <dgilmore> yes
17:11:22 <bstinson> +1
17:11:29 <Evolution> yeah, that's safe enough prior to fosdem
17:11:39 <Evolution> +1 here
17:11:58 <smooge> +1 from me
17:12:32 <smooge> #agreed Next orphan removal day is 2015-01-22 +5 -0
17:13:18 <smooge> #topic Website Cleanup? [Is smooge every gonna start?]
17:14:32 <smooge> well hopefully soon
17:14:40 <smooge> sorry dog needed to go outside
17:15:09 <smooge> I have stuff started to be written, but haven't had
enough time without interruptions to concentrate on it
17:15:16 <smooge> same story for everyone else I expect
17:15:38 <smooge> #topic FOSDOM EPEL/CentOS meeting
17:15:58 * nirik will not be there, but will be available via irc/email for
questions, etc
17:16:02 <smooge> Evolution, do you know what the current plans on this
are? I am expecting it will be BOF instead of a dinner
17:16:17 * maxamillion will not be there either but pending schedules will
be available on irc/email
17:16:46 <smooge> and it looks like it will be mostly getting stories from
users about what they want in EPEL
17:16:53 <Evolution> smooge: yeah. that's the current idea
17:17:03 <Evolution> 20 people at a dinner isn't meaningful
17:17:15 <Evolution> we're going to attempt to comandeer a bof area
17:18:34 * quaid leaps in for a few minutes
17:19:16 <quaid> smooge: yeah, getting user stories together basically
aiui; we need to have a better idea from the CentOS perspective what people
want, so we know what to work on, ask for, bargain for, build, etc.
17:19:22 <smooge> ok I expect it will be less than 20 people since possible
free food/beer is gone :). BUt then again the Red Hat BOF at USENIX was
40-60 people when 10 listed they would come up
17:19:55 <quaid> the folks who've responded seem to have an investment
beyond free-beer :) and this is Belgium, there might be beer anyway :)
17:20:38 <smooge> thanks
17:20:55 <smooge> do you guys have a date for it?
17:21:25 <Evolution> I don't recall seeing a date offhand on the list, but
I think we were trying to keep the same schedule as the dinner.
17:21:32 * dgilmore did book fosdem
17:21:45 <dgilmore> I will definitely be there
17:22:44 <quaid> dgilmore: looking forward to seeing you, been a long time
17:22:55 <smooge> and quaid maybe sometime this year we (various committee
members) can have a working meeting after some direction?
17:23:06 <quaid> Evolution: that's a good question, I presumed it moved
back to Sat afternoon for the event venue?
17:23:16 <smooge> various committee members + CentOS committee members
17:23:19 <Evolution> something to post to the list then.
17:23:26 <Evolution> for clarity at least.
17:23:46 <quaid> smooge: yeah, I asked KB if he wanted us all to have a
Hangout before FOSDEM, but when I got the fuller scope on user stories, I
realized it would be better after we had something solid to share; one of
us will look to arrange a meeting in Feb then
17:24:06 <quaid> Evolution: good point, I don't think it's been addressed,
yeah.
17:24:27 <smooge> quaid, thanks
17:25:43 <quaid> smooge: also, if no one objects, I plan to video the
meeting itself (non-social parts), we can either share privately or
publicly, depending (and I can always turn off the camera for a private
story, etc.)
17:25:53 <smooge> ok I don't have anything I would like to pose at the
meeting beyond the generals "What is it being used for? Where are these
people and how do we communicate with them better? etc"
17:27:29 <Evolution> certainly on the plan to ask.
17:27:49 <dgilmore> quaid: it has been
17:29:41 <smooge> ok so next EPEL meeting could we firm up on everything
that is going to happen then? We can work on a followup later
17:30:54 <Evolution> I might propose that we cancel the meeting for the
30th, as that's fosdem
17:31:04 <smooge> OK will do so
17:31:21 <smooge> since basically 3 out of 5 members aren't available
17:31:54 <smooge> #info 2015-01-30 meeting is cancelled due to FOSDEM and 3
out of 5 members being there versus available.
17:32:21 <smooge> #topic python3x proposal
17:32:43 * nirik has marked to look at that, but haven't had time yet
17:32:56 <smooge> so there has been a proposal on the list about how to
package up python3x items.
17:33:10 <smooge> I have only looked at it and went "wow.. thats going to
be a pain in the ass..."
17:33:58 <smooge> also followed by f*ck interpretive lanugages and "wtf
can't we all just use perl4 and be happy."
17:34:52 <smooge> so what I am going to ask is that the packages be built
together in a copr for viewing
17:35:27 <smooge> that way everyone will have an idea if it will work and
how it might not work
17:36:17 <smooge> nirik, dgilmore does that sound useful or waste of time
idea on my part?
17:36:35 <nirik> an example python and package could be usefull yeah.
17:36:53 <dgilmore> smooge: having osmething to look at would be useful
17:37:02 <ni
--
Stephen J Smoogen.
A. Robot Roll Call
B. Next Orphan Day?
C. Website Cleanup? [Is smooge every gonna start?]
D. EPIC? [when will smooge get time?]
E. FOSDOM EPEL/CentOS meeting
F. Python27/Python3x
G. Open Flood.
--
Stephen J Smoogen.
http://meetbot.fedoraproject.org/epel/2015-01-09/epel.2015-01-09-17.00.log.…
17:00:44 <smooge> #startmeeting epel17:00:44 <zodbot> Meeting started
Fri Jan 9 17:00:44 2015 UTC. The chair is smooge. Information about
MeetBot at http://wiki.debian.org/MeetBot.17:00:44 <zodbot> Useful
Commands: #action #agreed #halp #info #idea #link #topic.17:00:52
<smooge> #meetingname epel17:00:52 <zodbot> The meeting name has been
set to 'epel'17:01:13 <smooge> #chairs smooge nirik dgilmore
bstinson17:01:28 <smooge> Nirik I believe is going to be
absent17:01:32 <smooge> Evolution is absent17:01:51 <smooge> and
dgilmore might be on snowed in absense17:01:59 * nirik is actually
here right now...17:02:04 <nirik> but I might have to leave
early17:02:05 <smooge> #topic Roll Call17:02:12 <smooge> nirik, I
expect this will be a short meeting17:02:17 <nirik> cool.17:02:32
<bstinson> hi all17:02:39 <smooge> hi bstinson17:03:04 <smooge> #topic
Old Business17:03:30 <smooge> OK we don't have much old business from
the last meeting because it was a couple of weeks ago17:03:45 <smooge>
We had the orphaning and tyll found some bugs in his script that
didn't show all the orphans17:03:52 <smooge> so we have another
batch.17:04:23 * bstinson hasn't had a chance to look through the
email yet, how bad is it looking?17:04:36 <smooge> nirik, bstinson do
we want to have another orphan day or just have tyll do them when he
has a chance?17:04:48 <smooge> bstinson, it isn't any better than it
was before the last one :)17:04:54 * Jeff_S here a bit late17:05:16
<nirik> did we say 6 weeks or something? or has the timeout already
expired.17:05:33 <smooge> nirik, most of these packages are over 6
weeks (some are 22)17:05:48 <nirik> perhaps one last warn email and do
them next week?17:05:57 <bstinson> +117:06:06 <smooge> ok will send
out an email and ask tyll to do them next week around
Thursday?17:06:35 <smooge> alright anyone else have any other old
business?17:07:06 <bstinson> none here17:07:17 <nirik> nada17:07:30
<smooge> ok next up17:07:35 <smooge> #topic New Business17:07:55
<smooge> we have a non-responsive maintainer issue with
kanarip17:08:21 <Evolution> ack. sorry I'm late17:09:02 <nirik> well,
last time I talked to him he was busy, but wanted to keep being
co-maintainer.17:09:05 <smooge> ಠ_ಠ17:10:40 <smooge> nirik, did
someone make Marriane the maintainer of the package?17:11:06 <nirik>
hum? I'm not sure even what package we are talking about...17:11:09
<smooge> .whoowns perl-XML-TreePP17:11:10 <zodbot> smooge:
kanarip17:11:39 * nirik looks17:11:46 <nirik> .branches
perl-XML-TreePP17:11:48 <zodbot> nirik: el5 el6 epel7 f20 f21
master17:12:02 <smooge> the email was about the above which he is sole
maintainer of. I don't mind keeping him but since he is busy making
someone a comaintainer makes sense17:12:23 <nirik> they seem to own
the epel7 branch17:12:32 <nirik> so, I think they went ahead as they
should have.17:12:51 <nirik> You are supposed to ask the fedora
maintainer, wait a week, if no answer:: drive on17:13:09 <smooge>
https://lists.fedoraproject.org/pipermail/devel/2014-December/205902.html17…
<nirik> so, I think it all got sorted17:13:50 <smooge> nirik, ah ok..
I did a whoowns which used to say something like epel7 (mmm)17:14:03
<smooge> and it just said kanarip so I thought it was still
waiting17:14:05 <nirik> that might be cached.17:14:06 <smooge> my
apologies17:14:13 <Jeff_S> So what was the problem? Did the bug just
not have the right flag set to get attention?17:15:00 <nirik> I think
they just were waiting forever, when the policy says wait a week and
then just request it.17:15:10 <Jeff_S> ok17:15:21 <nirik> not sure how
to make that any better. ;(17:15:31 <smooge> will put that in a blog
list of how to do things in EPEL17:16:00 <smooge> ok any other new
business?17:16:09 <Jeff_S> Yeah, I don't think that's a big deal
unless it's happening to a lot of requests17:16:59 <nirik> more
docs/blog posts on it should possibly help17:18:48 <smooge> I am
working on a couple.. I hope to get some time this weekend to get them
out17:19:05 <smooge> ok any other business we need to deal
with?17:19:19 <smooge> #topic Next Meeting Agenda Items17:19:46
<smooge> Ok please put in anything we want to have in the next meeting
or thought about in coming meetings17:19:47 <nirik> there was another
person asking about the epel-release permlink again17:19:58 <smooge>
yeah.. another roundtuit I need to get on17:20:13 <Jeff_S> ++
:)17:20:34 <smooge> I hope to look at it next week17:20:47 <Jeff_S>
Thanks17:21:05 <bstinson> should we brainstorm some topic ideas for
the CentOS-EPEL meetup at fosdem?17:21:15 <Jeff_S> bstinson: sure, rub
it in...17:22:31 * nirik notes he will not be there, but will be
around on irc if needed.17:22:38 <Jeff_S> I've gotta run, thanks
all17:22:47 <bstinson> was hoping we could live stream it :) but i'm
not sure if that's possible17:23:23 <Evolution> yeah, sadly some of
the key players won't be there17:23:28 <Evolution> nirik, smooge,
etc.17:24:25 <smooge> yeah.. I think we are going to do better just
having a public google hangout or something than try to do something
at an event most can't get to17:24:51 <smooge> not that I have been
any better with some of the EPEL meetings at Flock/FUDcon when CentOS
people couldn't attend17:26:14 <smooge> so lets just say we need to
come up with things for those who can make it to talk about and move
on17:27:22 <smooge> bstinson, most of the topics I would want to talk
about sort of need the rest of EPEL do'ers on to better converse.
Otherwise it could end up like my EPIC proposal.. lots of good ideas
but no buy-in17:29:08 <bstinson> that makes sense, it would be nice to
do a hangout sometime17:29:35 <smooge> ok lets see if we can get that
arranged.17:29:57 <smooge> anything else? I think we will lose nirik
soon17:31:26 <smooge> #topic Open Flood17:31:36 <smooge> Ok last call
on topics and things to talk about.17:31:38 <smooge> Last call17:31:51
<bstinson> nothing here17:31:57 * smooge wonders if Evolution will
wake up to those words17:32:09 <Evolution> I'm here17:32:15
<Evolution> I have nothing to contribute, but I'm here.17:32:19
<dgilmore> sorry guys I slept in17:32:46 <smooge> oh man.. I had a
whole bar closing thing typed in too17:32:51 <dgilmore> I should be at
fosdem17:33:14 <smooge> dgilmore, can you make the EPEL-CentOS
meetup?17:33:23 <dgilmore> smooge: should be able to yes17:34:38
<smooge> cool. that should help answer some of the questions about
build systems that will come up17:34:59 <smooge> Evolution, do you
know whats on kbsingh's mind for the meeting?17:35:17 <Evolution> I
believe interoperability.17:35:47 <Evolution> packages that should be
in epel coming from sigs, etc.17:36:09 <dgilmore> for me its
interoperability and working on finding ways to enable people to
contribute to epel via either CentOS or Fedora17:37:10 <smooge> ok I
think then that if everything gets recorded we can get some stuff done
then17:38:32 <smooge> dgilmore, anything you want in the next
meeting?17:39:56 <dgilmore> smooge: we should look at the policy for
branching packages from Fedora17:40:37 <smooge> dgilmore, yes I agree.
It comes up a lot17:40:49 <dgilmore> It seems many people are not
aware of it and quite a lot of people just go and request branches for
packages. I had it happen to one of mine recently17:41:32 * nirik
wonders if we can somehow automate it.17:41:56 <dgilmore> when
emailing the person that branched my package they thought anyone was
free to branch any package17:42:12 <dgilmore> nirik: we should find a
way to do it17:42:40 <dgilmore> nirik: moving branching into pkgdb
should give us a way to do so17:42:43 <nirik> yeah...17:44:02 <smooge>
ok so something for me to put on next weeks agenda? Can pkdb fix all
our problems?17:44:22 <dgilmore> smooge: its work that is
underway17:45:08 <dgilmore> we probably should make sure we get all
the policy right then palk to pingu and make sure we automate the
checks17:45:33 <smooge> ok so I am not clear on how policy should be
worded.. any examples and I can make a pass at something for
EPEL?17:46:01 <dgilmore> i think the existing polic is fine17:46:26
<dgilmore> we need to reaffirm it and make sure its visable and people
are aware of it17:47:04 <dgilmore> automated enforcement would help
with making people aware17:47:31 <smooge> And the exisitng policy is
the one you listed in the email yesterday?17:47:51 <dgilmore>
http://fedoraproject.org/wiki/Getting_a_Fedora_package_in_EPEL17:47:53
<dgilmore> correct17:48:13 <dgilmore> packagers can opt out of
epel17:48:37 <dgilmore> in which case people can freely request a
branch17:49:18 <smooge> and from what nirik said earlier.. if the
packager doesn't respond in a week they can branch anyway?17:49:49
<dgilmore> yep17:50:25 <dgilmore> the one thing i think we could add
is that sometimes a package really doesnt make sense in epel17:50:35
<dgilmore> and there should be a way to say so17:50:48 <smooge>
yeah17:51:20 <smooge> ok I will ponder how to do that and come back
next meeting on it17:51:29 <dgilmore> cool17:51:34 <dgilmore> i have
nothing else17:51:41 <smooge> ok me either..17:51:47 <smooge> my dog
says I need to walk her17:51:51 <smooge> so ..17:51:54 <smooge>
#endmeeting
--
Stephen J Smoogen.
A. Robot-Roll Call
B. Old Business [Go over decided items from previous meetings:]
1. Next Orphan Day
C. Current Business
1. Website cleaning (deal with FAQ page)
2. ...
D. Next Meeting Business
1; EPIC?
E. Open Flood
--
Stephen J Smoogen.