9:12 p.m.
hey guys, something went wrong with the docs site tonight. Not quite sure
what yet but it has increased in size at least double, possibly more. You
can see from the storage watch:
http://tinyurl.com/299s5nz
we went from 7G used to about 12G used. We think that was mostly docs.
here's the dir structure at the moment:
364K fedoradocs.db
8.0K homepage.tmp
4.5G public_html
4.5G web
any ideas? looks like two copies of the same data?
-Mike
9:34 p.m.
Mike
There was a commit to Spanish translations today that changed around
135K files. That looks a bit suspicious since the typical language
update changes ~100 files.
Daniel Cabrera (a translator I assume) made commit
a62c57188e4782048080835cb78b3b8269c7314b at 2338Z. You might ping him
and see if he has any insight into whether something may have gone
wrong, but without Rudi or Jeff I'm not sure anyone else will be much
help. Ohhhhh, the email address on the commit is bad. Perhaps a git
guru can roll back that commit.
Unfortunately, I don't know enough about the new Publican web management
thing to know whether this sometimes happens, it may well decide to
rewrite the whole site once in a while.
The guys that know are mostly BNEers and I think it may already be
Saturday there.
--McD
On Thu, 2010-09-16 at 21:12 -0500, Mike McGrath wrote:
hey guys, something went wrong with the docs site tonight. Not quite
sure
what yet but it has increased in size at least double, possibly more. You
can see from the storage watch:
http://tinyurl.com/299s5nz
we went from 7G used to about 12G used. We think that was mostly docs.
here's the dir structure at the moment:
364K fedoradocs.db
8.0K homepage.tmp
4.5G public_html
4.5G web
any ideas? looks like two copies of the same data?
-Mike
9:46 p.m.
On Thu, 2010-09-16 at 22:34 -0400, John J. McDonough wrote:
Mike
There was a commit to Spanish translations today that changed around
135K files. That looks a bit suspicious since the typical language
update changes ~100 files.
Daniel Cabrera (a translator I assume) made commit
a62c57188e4782048080835cb78b3b8269c7314b at 2338Z. You might ping him
and see if he has any insight into whether something may have gone
wrong, but without Rudi or Jeff I'm not sure anyone else will be much
help. Ohhhhh, the email address on the commit is bad. Perhaps a git
guru can roll back that commit.
Unfortunately, I don't know enough about the new Publican web management
thing to know whether this sometimes happens, it may well decide to
rewrite the whole site once in a while.
The guys that know are mostly BNEers and I think it may already be
Saturday there.
--McD
On Thu, 2010-09-16 at 21:12 -0500, Mike McGrath wrote:
> hey guys, something went wrong with the docs site tonight. Not quite sure
> what yet but it has increased in size at least double, possibly more. You
> can see from the storage watch:
>
> http://tinyurl.com/299s5nz
>
> we went from 7G used to about 12G used. We think that was mostly docs.
> here's the dir structure at the moment:
>
> 364K fedoradocs.db
> 8.0K homepage.tmp
> 4.5G public_html
> 4.5G web
>
> any ideas? looks like two copies of the same data?
>
> -Mike
>
Hi Guys,
I'm sorry if a made something wrong. My intention was only to update our
version of the Security Guide. I follow all the steps shown here [1], as
I always did.
[1] http://fedoraproject.org/wiki/Publishing_a_document_with_Publican
9:59 p.m.
On Thu, 16 Sep 2010, daniel cabrera wrote:
On Thu, 2010-09-16 at 22:34 -0400, John J. McDonough wrote:
> Mike
>
> There was a commit to Spanish translations today that changed around
> 135K files. That looks a bit suspicious since the typical language
> update changes ~100 files.
>
> Daniel Cabrera (a translator I assume) made commit
> a62c57188e4782048080835cb78b3b8269c7314b at 2338Z. You might ping him
> and see if he has any insight into whether something may have gone
> wrong, but without Rudi or Jeff I'm not sure anyone else will be much
> help. Ohhhhh, the email address on the commit is bad. Perhaps a git
> guru can roll back that commit.
>
> Unfortunately, I don't know enough about the new Publican web management
> thing to know whether this sometimes happens, it may well decide to
> rewrite the whole site once in a while.
>
> The guys that know are mostly BNEers and I think it may already be
> Saturday there.
>
> --McD
>
> On Thu, 2010-09-16 at 21:12 -0500, Mike McGrath wrote:
> > hey guys, something went wrong with the docs site tonight. Not quite sure
> > what yet but it has increased in size at least double, possibly more. You
> > can see from the storage watch:
> >
> > http://tinyurl.com/299s5nz
> >
> > we went from 7G used to about 12G used. We think that was mostly docs.
> > here's the dir structure at the moment:
> >
> > 364K fedoradocs.db
> > 8.0K homepage.tmp
> > 4.5G public_html
> > 4.5G web
> >
> > any ideas? looks like two copies of the same data?
> >
> > -Mike
> >
>
>
Hi Guys,
I'm sorry if a made something wrong. My intention was only to update our
version of the Security Guide. I follow all the steps shown here [1], as
I always did.
[1] http://fedoraproject.org/wiki/Publishing_a_document_with_Publican
can you revert it?
-Mike
1:24 a.m.
2010/9/17 daniel cabrera <logan(a)fedoraproject.org>:
On Thu, 2010-09-16 at 21:59 -0500, Mike McGrath wrote:
> can you revert it?
>
I think so, but I'd like some guidance... I don't want to make things
worse.
I'm on the IRC.
I'm very sorry, it appears I've noticed the problem and reverted this
commit before I've read your e-mails. I hope I didn't get in your way
or something.
Anyway, reverting a bad commit is easy, basically it's "git revert
commit_hash". Commit hash can be obtained from some git command I
don't know or from my favorite gitweb. :)
--
Piotr Drąg
http://raven.pmail.pl/
7:04 a.m.
On 09/17/2010 04:24 PM, Piotr Drąg wrote:
<snip>
Anyway, reverting a bad commit is easy, basically it's "git
revert
commit_hash". Commit hash can be obtained from some git command I
don't know or from my favorite gitweb. :)
(in case it's useful, or anyone's curious)
The command "git log" could be what you want. It shows the history
of what has been committed, with the most recent first, then the commit
before it, then the one before that, and so on:
$ git log
commit 10c592801c32247d1d82520df17ae409d2e55fc7
Author: Eric Blake <eblake(a)redhat.com>
Date: Thu Sep 9 20:32:50 2010 -0600
tests: clean up qemuargv2xmltest
Since commit 107a7bd06bc, the extraFlags argument was unused.
* tests/qemuargv2xmltest.c (DO_TEST): Drop extraFlags argument.
Adjust all callers.
commit df1718cc7366296be4ab71c830cc2b93e505ceec
Author: Justin Clift <jclift(a)redhat.com>
Date: Thu Sep 16 22:14:18 2010 +1000
docs: reworked the policykit patch submitted by Patrick Dignan
Tweaked the PolicyKit documentation improvement patch submitted
by Patrick Dignan.
Additionally, removed the reference to PolicyKit.conf, which is
no longer used by PolicyKit, plus added a link to the expanded
PolicyKit example page on the wiki.
commit 5bc4307597d382ab8a951feee0daf13439926238
<snip>
There's also a "--oneline" version:
$ git log --oneline
10c5928 tests: clean up qemuargv2xmltest
df1718c docs: reworked the policykit patch submitted by Patrick Dignan
5bc4307 docs: fix the xml validity errors regarding name and id
8ae354f build: avoid non-portable IPv6 struct member, for MacOS X
58ba49a virsh: change wexitstatus order to allow compilation on mac osx
63d1b07 libvirtd: improve the error message displayed on tls client
auth failure
8a93daf maint: silence warning from libtool
38ba6e1 Rebuild network filter for UML guests on updates
I'm not a git expert, it's just something I'm learning from necessity. :)
Regards and best wishes,
Justin Clift
8:27 a.m.
On Fri, 2010-09-17 at 08:24 +0200, Piotr Drąg wrote:
2010/9/17 daniel cabrera <logan(a)fedoraproject.org>:
> On Thu, 2010-09-16 at 21:59 -0500, Mike McGrath wrote:
>> can you revert it?
>>
> I think so, but I'd like some guidance... I don't want to make things
> worse.
> I'm on the IRC.
>
I'm very sorry, it appears I've noticed the problem and reverted this
commit before I've read your e-mails. I hope I didn't get in your way
or something.
Anyway, reverting a bad commit is easy, basically it's "git revert
commit_hash". Commit hash can be obtained from some git command I
don't know or from my favorite gitweb. :)
--
Piotr Drąg
Well, I guess everything is back to normal.
Nick and Piotr, thank you very much for helping me to clean up my mess.
Now I know what was my mistake and it won't happen again.
See you around, logan.
1:13 p.m.
On Fri, 17 Sep 2010, daniel cabrera wrote:
On Fri, 2010-09-17 at 08:24 +0200, Piotr Drąg wrote:
> 2010/9/17 daniel cabrera <logan(a)fedoraproject.org>:
> > On Thu, 2010-09-16 at 21:59 -0500, Mike McGrath wrote:
> >> can you revert it?
> >>
> > I think so, but I'd like some guidance... I don't want to make things
> > worse.
> > I'm on the IRC.
> >
>
> I'm very sorry, it appears I've noticed the problem and reverted this
> commit before I've read your e-mails. I hope I didn't get in your way
> or something.
>
> Anyway, reverting a bad commit is easy, basically it's "git revert
> commit_hash". Commit hash can be obtained from some git command I
> don't know or from my favorite gitweb. :)
>
> --
> Piotr Drąg
Well, I guess everything is back to normal.
Nick and Piotr, thank you very much for helping me to clean up my mess.
Now I know what was my mistake and it won't happen again.
See you around, logan.
I just realized I never sent a note to the list, yes everything is back to
normal. Thanks to everyone for the quick response.
-Mike
4963
days inactive
4963
days old
8 comments
5 participants
participants (5)
-
Daniel Cabrera -
John J. McDonough -
Justin Clift -
Mike McGrath -
Piotr Drąg