Not a big deal, but I just added a “Table of Contents” page to my blog to make finding older articles much easier.
I noticed most of my posts are quite lengthy, and it can take a bit of searching/clicking to find an older entry. So unless you happen to recall the ‘month/year’ it was published, which I don’t even remember that, then hopefully this will help.
Really simple, and looks just like this:
My hopes are that this will aid in making some posts easier to find (such as ones about InnoDB Recovery, Recovery with an Individual .ibd, Proxy-related articles, Error-related articles, How-to posts, and so forth).
You can see the full “table of contents” here:
Last Friday, I had posted that the MySQL Source Code on Launchpad had not been updated (or rather not accessible by Lauchpad) in nearly a month.
I had actually started to file a bug report about this, but when posting the relevant links for documentation, I had noticed new information had been posted yesterday (10/10/2011).
Here was the orignal MySQL Launchpad page:
Here is the new message on this page:
“This is the old MySQL server branch and it is no longer used since mirroring setup has changed.
You can find the development head at https://code.launchpad.net/~mysql/mysql-server/trunk instead.”
If you navigate to the new page:
You’ll see all of the updates, etc.
Furthermore, if you now issue:
You’ll see a number of new revisions pulled in (I had 3572, for instance).
Thank you for addressing this Mats, MySQL, and everyone else involved!
I know I’m not the only one to have noticed that all MySQL branches on Launchpad have not been accessible since September 10th, 2011, nearly 1 month.
Just visit here:
You’ll see it says:
“This branch may be out of date, because Launchpad has not been able to access it since 2011-09-10.”
I’d been seeing “No revisions to pull.” messages latley, when running “bzr pull”, but didn’t give it a whole lot of thought until reading the above note on Launchpad today.
Is it due to the recent security breach (where mysql.com was hacked and infected some visitors with malware)? Well, I doubt it since this started on 9/10/2011 and the breach, according to The Register, occurred on 9/26/2011 (some 2 weeks later):
I hope this is not permanent, and/or a sign of things to come.