On Mon, 25 Feb 2013 13:31:18 -0700
Stephen John Smoogen wrote:
> On 25 February 2013 13:28, Paul Wouters wrote:
> > On Mon, 25 Feb 2013, Michael Cronenworth wrote:
> >
> >>> I'd like to finish up the NRM process.
> >>
> >>
> >> What have I not done? Do I need to CC FESCo members directly?
> >> C
On 25 February 2013 13:28, Paul Wouters wrote:
> On Mon, 25 Feb 2013, Michael Cronenworth wrote:
>
>>> I'd like to finish up the NRM process.
>>
>>
>> What have I not done? Do I need to CC FESCo members directly? Create a
>> trac ticket?
>>
>> The current maintainer has gone without replying to my
On Mon, 25 Feb 2013, Michael Cronenworth wrote:
I'd like to finish up the NRM process.
What have I not done? Do I need to CC FESCo members directly? Create a trac
ticket?
The current maintainer has gone without replying to my messages for a month
now. My FAS name is mooninite and I have be
Stephen John Smoogen wrote:
> I believe you need to file a trac ticket. That should get this on a
> FESCo meeting agenda and get this dealt with.
Created. Thanks.
https://fedorahosted.org/fesco/ticket/1091
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailma
On 25 February 2013 06:37, Michael Cronenworth wrote:
> On 02/15/2013 05:11 PM, Michael Cronenworth wrote:
>>
>>
>> Ping.
>>
>> I'd like to finish up the NRM process.
>
>
> What have I not done? Do I need to CC FESCo members directly? Create a trac
> ticket?
I believe you need to file a trac tick
On 02/15/2013 05:11 PM, Michael Cronenworth wrote:
Ping.
I'd like to finish up the NRM process.
What have I not done? Do I need to CC FESCo members directly? Create a
trac ticket?
The current maintainer has gone without replying to my messages for a
month now. My FAS name is mooninite and
On 15 February 2013 12:24, Adam Williamson wrote:
> On 15/02/13 05:44 AM, Tom Hughes wrote:
>>
>> On 15/02/13 03:02, Adam Williamson wrote:
>>
>>> On 08/02/13 01:36 PM, Pete Travis wrote:
>>>
I haven't poked at mediawiki in a while, so please correct me if I'm
wrong, but isn't it fairly
On 02/08/2013 08:46 AM, Michael Cronenworth wrote:
The mediawiki package is severely outdated. I have attempted to contact
the maintainer and received only one reply in a couple of weeks. He has
ignored my requests for co-maintainership.
I commented on the NRM bug[1] two weeks ago with no respon
On Fri, Feb 15, 2013 at 11:24:31AM -0800, Adam Williamson wrote:
> On 15/02/13 05:44 AM, Tom Hughes wrote:
> >You're both kind of right - the README.RPM file that comes in the
> >mediawiki package tells you to run "mw-createinstance " to create
> >an instance and that sets up a document root in th
On 15/02/13 09:49 AM, Pete Travis wrote:
Interestingly, 'repoquery -l' does show some of the mediawiki packages
owning files in /var/www/. Whether grandfathered, broken, or just
misconception, I'll keep further comment to myself until I can play with
a VM.
There are cases when there really ha
On 15/02/13 05:44 AM, Tom Hughes wrote:
On 15/02/13 03:02, Adam Williamson wrote:
On 08/02/13 01:36 PM, Pete Travis wrote:
I haven't poked at mediawiki in a while, so please correct me if I'm
wrong, but isn't it fairly self contained? I recall copying the content
from /usr/share/ to /var/www/
On Feb 15, 2013 5:34 AM, "Adam Williamson" wrote:
>
> On 08/02/13 01:36 PM, Pete Travis wrote:
.
>>
>> I haven't poked at mediawiki in a while, so please correct me if I'm
>> wrong, but isn't it fairly self contained? I recall copying the content
>> from /usr/share/ to /var/www/ then localizing. H
On 15/02/13 03:02, Adam Williamson wrote:
On 08/02/13 01:36 PM, Pete Travis wrote:
I haven't poked at mediawiki in a while, so please correct me if I'm
wrong, but isn't it fairly self contained? I recall copying the content
from /usr/share/ to /var/www/ then localizing. Having a new version
sh
On 08/02/13 01:36 PM, Pete Travis wrote:
On Feb 8, 2013 12:54 PM, "Stephen John Smoogen" mailto:smo...@gmail.com>> wrote:
. Two the fix is to upgrade to a very new
> version which will break everyone who upgrades until they (or the
> first person who gets to the website :) ) runs the upgrade m
I've handed up with this question when I first request for an upgrade of
mediawiki.
I remember someone told me that upgrading may cause errors of custom css or
custom theme,is it true?
在 2013-2-9 AM5:37，"Pete Travis" 写道：
On Feb 8, 2013 12:54 PM, "Stephen John Smoogen" wrote:
. Two the fix is to
I've handed up with this question when I first request for an upgrade of
mediawiki.
I remember someone told me that upgrading may cause errors of custom css or
custom theme,is it true?
在 2013-2-9 AM5:37，"Pete Travis" 写道：
>
> On Feb 8, 2013 12:54 PM, "Stephen John Smoogen" wrote:
> . Two the fix
On Feb 8, 2013 12:54 PM, "Stephen John Smoogen" wrote:
. Two the fix is to upgrade to a very new
> version which will break everyone who upgrades until they (or the
> first person who gets to the website :) ) runs the upgrade mode..
> which might not work due to either custom changes or the fact t
On 8 February 2013 13:15, Michael Cronenworth wrote:
> Stephen John Smoogen wrote:
>> This package is a bit difficult to "fix". One it has custom patches
>> that upstream doesn't accept. Two the fix is to upgrade to a very new
>> version which will break everyone who upgrades until they (or the
>>
Stephen John Smoogen wrote:
> This package is a bit difficult to "fix". One it has custom patches
> that upstream doesn't accept. Two the fix is to upgrade to a very new
> version which will break everyone who upgrades until they (or the
> first person who gets to the website :) ) runs the upgrade
On 8 February 2013 12:15, Rahul Sundaram wrote:
> Hi
>
> On Fri, Feb 8, 2013 at 9:46 AM, Michael Cronenworth wrote:
>>
>> At this point it is time for someone to update the package as it
>> is currently a security hazard. I have already built the latest
>> mediawiki package and have it ready to r
Hi
On Fri, Feb 8, 2013 at 9:46 AM, Michael Cronenworth wrote:
> At this point it is time for someone to update the package as it
> is currently a security hazard. I have already built the latest
> mediawiki package and have it ready to rock-and-or-roll once the NRM
> procedure is finished.
>
Th
21 matches
Mail list logo
