Search Results: "ag"

11 June 2007

MJ Ray: Stopping the Nixforce.com Sploggers

I asked: Should we try to stop them, or just post that "Nixforce look like an unscrupulous load of swines trying to trade on Debian Developer names without permission" all over their site? Paul wrote:
"They are violating Google's Adsense policies by inviting people to click on their ads on their front page ("If you dont want to enter, at least go to one of our Advertisers below"). You could, at the very least, have this line of their income terminated by reporting them here "
Works for me. It said they'll respond within 24 hours. Brandon Holtsclaw suggested:
"Or set something to look for the referer pulling the feed and redirect just that nixforce domain to a 404 or some nasty pr0n feed :) just a thought."
I would, but I think most things will fail to pull if I send a 40x and I can't think how to do a redirect or proxy neatly without messing with RewriteRule or similar - nixforce aren't worth messing with RewriteRules. I also suspect they're pulling from Planet Debian, rather than my web host, so if I made a mistake, I'd be very unpopular. Also: Russell Coker and Antti-Juhani Kaijanaho

Joachim Breitner: Visualizer for Anagrams

For my uncles wedding my brothers and I did a show where we took his name and use its letters to create a bunch of new words that are part of a speech about him. This was visualized on a projector by a program by me that let s the letter swirl around, forming each built word, as well as some special effects (such as rotating one letter around to show another).The program is written in Haskell, using gtk2hs and Cairo. You can find the sources in my darcs repository (Browse via DarcsWeb). To build it on a debian machine, this should work:
apt-get install darcs gtk2hs libghc6-cairo-dev libghc6-gtk-dev libghc6-mtl-dev happy
darcs get http://darcs.nomeata.de/anapres
make
./anapres examples/RolandHochzeit.anapres
I can also provide pre-compiled binaries, if you want.There is a very simple text file format that describes the sequence of words and special effects, but so far it is only tested with the one example file (the one from the wedding).If you want to try this and have any kind of trouble, do not hesitate to contact me. I m also interested in bug reports and patches, of course.

Russell Coker: Nixforce unauthorised use

Just over two days ago I sent a DMCA take-down request to nixforce.com for copying my content in violation of the non-commercial license that I offer, I have not had a response from them and they have kept mirroring my site. I have just sent a DMCA take-down to tierzero.net which appears to be their ISP. The email address listed in the whois record for that ISP bounces as does the postmaster address. It seems that I’m not the only person with this problem, Antti-Juhani Kaijanaho is also having problems with them. Any suggestions on how to deal with them would be appreciated. One possibility that I will eventually persue is to file a DMCA request with Google, this can result in their Google Adwords account being terminated.

Russell Coker: Easy Search Engine Optimisation in Wordpress

The first thing you need is to have meta keywords in the pages. The solution I discovered for doing this is the All In One SEO Pack, this automatically makes the categories of a blog post become meta keywords, allows adding arbitrary meta keywords when editing the blog post, and supports keywords for the entire blog. It also re-writes the titles to have the title of the post appear before the title of the blog in the <TITLE> tag which is rumored to be a good thing to do. The next thing you want to do is to create a Google sitemap. A sitemap is an XML file that describes all the URLs in your web site which tells Google (and other search engines) the last change dates of all the URLs and the change frequencies (or how often they should be checked for changes). Note that the format is called Google Sitemaps because Google invented it, other web search engines also use the same format. To generate my sitemap I use the Google Sitemaps Generator which tells earch engines to index my main blog page daily and the category pages weekly (which is configurable). It also has an option to notify Google of changes by pinging the Google service. Having multiple names for the same web page hurts you when it comes to search engines. Having two separate pages at the top of page 2 is not nearly as good as having one page on page one! To solve this problem I use the Permalink Redirect plugin to make sure that each page has only one URL pointing to it. This plugin also allows redirecting the feed URL to feedburner.com. Feedburner serves the feed data (thus saving you some bandwidth if you are on a slow link) and also tracks statistics on it which are interesting. Under the Writing section of the Options menu there is an option to enter a list of URLs for update services that can be notified of every post. I use http://rpc.pingomatic.com/ and http://rpc.technorati.com/rpc/ping. The Update Services entry in the Wordpress Codex has more information on how this works. Social networking sites such as digg.com can direct a large amount of traffic to your site if you write about a popular topic. The Share This plugin is the simplest way I found of adding social networking hooks to Wordpress (I tried a few others that had both less functionality and less ease of use). Finally before publishing a post, I often check the Google Adwords Keyword Tool. This often gives me ideas on how to make the meta tags and title match what people are searching for.

Antti-Juhani Kaijanaho: Nixforce, cease and desist

Update Amazingly, they seem to have complied with this notice by taking down my content :) Nixforce, you are republishing (parts of) my blog without permission, and without indicating that you are republishing stuff written elsewhere. You are required to do all of the following, or cease and desist from republishing my content: If you do both, you have my permission to continue republishing my content. Additionally, you should verify that you have the legal right to republish content by the other authors. (This has been mailed to their contact email address.)

Gustavo Franco: debcamp updates - round I


Where's Vagrant? :)

Russell Coker: Prius vs small non-hybrid car

In response to my comment and post about the cost of driving to work there was a comment on the blog post I responded to suggesting that a small car is better value for money than a hybrid car. The claim was made regarding a Nissan Pulsar, but to investigate this I decided to compare the Prius with the Corolla Hatchback, as far as I can tell the Corolla Hatchback is the nearest non-hybrid car to the Prius that Toyota sells (being similar in size, weight, and performance). Comparing cars of different make adds extra variables into the equation. Unfortunately the Toyota web site fails to provide specifications for the Prius and only provides a PDF file with minimal information on the Corolla, but it is enough for some minimal calculations. A car company run by intelligent people would publish the specs on all their vehicles and provide a search form to compare selected models. The Standard Performance Evaluation Corporation has a good search method that allows easy comparison and ranking of items in their database (here is an example). It would be good if Toyota would permit us to compare models in their car range in a similar manner. According to the Toyota web site the Prius uses 4.4L/100Km when driving in the city and the manual transmission version of the Corolla Hatchback uses 7.4L/100Km (7.7 for the auto). For the average 16,000Km that an average Prius owner drives that would save 480L of petrol which would save about $700 at current petrol prices. The Corolla Ascent Hatchback (the cheapest of all Corollas) is $21,000 while the cheapest Prius is $37,400. If you compare the Prius with the cheapest Corolla then it’s a $16,400 price difference. If you save $700 per annum then it won’t cover the interest on a $16,400 loan or match the interest rates earned by a bank term-deposit if the $16,400 was invested. So it seems apparent that at current petrol prices (NB petrol prices are expected to increase) and with average Prius driving patterns a Prius will not be more economical than a cheap Corolla. Currently the Commonwealth Bank of Australia offers 6.05% interest on term deposits of between $10,000 and $25,000. This means that $700 per annum would be the interest on a term deposit of $11,500. If we compare the Corolla Ultima Sedan at $32,000 with the Prius at $37,400 the difference in price is less than $11,500 - but the cars have incomparable sets of luxury and safety features. The Prius i-tech appears to have a super-set of the luxury and safety features of the Corolla Ultima Sedan but at $46,900 is again going to cost more for the average Prius driver. The Prius is a very quiet car to drive, there is almost no engine noise (when driving at speeds where the Petrol engine is operating there is usually more noise from other vehicles) and no gear changes (handy if passengers are consuming hot or sticky drinks). It has a good set of safety and luxury features and is also a prestige car (no-one will say “oh wow, you’ve got a Corolla”). If you assign a dollar value to these features then a Prius may be the most economical car that meets your requirements! Finally, let’s keep in mind the fact that petrol prices are steadily increasing. If you save $700 by driving a Prius this year then you may save $1000 next year. There is also the option of converting a Prius to a plug-in hybrid which will be a useful option if petrol prices hit $10/L! Also the amount of money saved will depend on the use of the car. If you are running a courier or taxi business then a Prius will probably be a lot more economical than a Corolla due to the greater distances travelled and the travel in the slow city traffic that the Prius was designed for. PS All prices are in Australian dollars and concern products on offer in Australia, I would like to see comments from other people who perform the same calculations for their countries.

John Goerzen: Tourists

Today as we were getting ready to head out, Terah said to me, "There are people on our yard with cameras and I don't know who they are!"

I looked out and they looked friendly, so I went on out and said hi.

I'm glad I did, too, because these weren't just any random people with cameras. The group included Ed, who grew up in what is now our house. He's probably in his 70s or 80s now. His wife, son, and daughter-in-law were along, too. They had all driven up from Oklahoma and wanted to see the old farm. Ed's family had sold it to my grandparents back in the 40s.

They apologized for tresspassing. I told them, "I don't mind as long as you share a few stories."

Ed told us that he remembered the second story and kitchen being added on to the house when he was about 10, shortly after it was moved to its present location. He remembered his dad building the elevator that still stands on our property. It is quite the marvel of engineering and craftsmanship. I learned that its first power source was an engine from a Model T.

Ed kept looking at the house smiling. A few years ago, maybe 2 or 3, he got to see the place for the first time in 40 years. But it wasn't doing so well then already. He said we had done a wonderful job restoring it. He remembered, back before there was a sidewalk, sitting on the porch letting his feet dangle in the mud. Or sitting out there Sunday evenings making ice cream.

I invited them to take a quick look inside. They politely declined, not wanting to impose. Terah and I assured them that it would be fine, though we did need to leave in a few minutes. They came inside and Ed started describing the place to his family.

He pointed to the oak floor in the living room. "Is that original?" I told him, "Yes, it is; we added on about 2 feet to it but the rest of it is original." He said that he helped lay that floor. I asked him something I had been wondering for awhile: did they put the oak floor on top of a pine floor? He smiled and said, "Yes, we sure did!"

We came to the office. He asked if the wood ceilings were original. Yes, I told him they are. He confirmed what I had heard about the reason for a burned spot on the office floor: that someone had opened a wood stove and a live log fell out. He also asked if we had taken out the chimney. Yes, we did, but we saved the bricks. "Ah! We had a chimney fire in there one time! We all thought the whole house might burn down." I told him that the bricks still were marked from that.

He told me of one time he was standing on the north side of the house, idly throwing stones at it. His sister was playing piano at a window, in what is now the office. One of Ed's stones went through the window and hit her (but didn't hurt her seriously). "Boy did I ever hear about breaking that window!" One of his relatives asked, "What about hitting your sister?" "Well, that wasn't as bad as the window."

This isn't the first time something like this has happened. It's really neat to hear stories about the place and learn about its life before it came to be in my family.

I was glad I went out and said hi to our visitors instead of ignoring them or chasing them off.

Good things can come from strangers sometimes. I think I'm going to gather up a batch of photos and send them to Ed and his family, along with a few questions for them!

Joey Hess: unpacking boxes

A few people have asked what I meant in my "boxes" comic. Other just look at me strangely. Some hackers have enjoyed the comic, so I thought I'd try to unpack the meaning of it a bit for the layperson. Of course this will spoil the joke, but what the hey. A hacker who looks at the comic probably thinks about things like recursion, fractals, unicode, fonts, and bugs. fonts A font is how the computer knows how to draw the letters on its screen. Before computers, a font was a bunch of metal bits that could be arranged and fed into a printing press. As with most things involving drawing on a screen, font technology is much more complicated these days than you'd ever imagine. Fonts and the programs that draw them (font engines) are something of a mystery even to most hackers. unicode Unicode is an absurdly complicated version of the alphabet. Or rather, of every alphabet and similar thing used by anyone on earth or in Star Trek. It's not a font, it's a way for the computer to store text internally, by basically assigning a unique number to each letter. Since most hackers grew up in a world without unicode, and suffered through the (still continuing) transition to it, they're familiar with lots of quirks and weird and broken behaviors you get from it. One of these quicks is what to do when the computer wants to display a particular letter from unicode, but that letter is not available in the font. Since unicode contains effectively an infinite number of symbols, and each symbol in a font is carefully crafted by hand, this occurs pretty often. Handling of this situation varies, but often the computer will just display a little empty square box for the letter that it doesn't know how to draw. Some font engines go a step further and write the number of the unicode character in little tiny numbers inside the box. Presumably so that a hacker can look at it and tell what character is missing. The numbers are typically written one in each corner of the box, and you'd have to squint to see them. fractals A fractal is a special kind of picture, where parts of the picture repeat over and over at different scales. You've probably seen pictures of the most famous fractal, the Maldebrot set. That one is generated by a kind of formula, but there are much simpler ones, like the Koch snowflake. Hackers love fractals, because they're pretty, and complex, while based on very simple math. recursion "Recursion: See recursion." Ha! That's the best hacker joke ever, a true classic. Recursion is when the computer sees an instruction like that and mindlessly repeats it over and over. This actually turns out to be useful, and hackers see a kind of beauty in it. bugs Bugs are what happens when a computer program, which is supposed to be internally clear and simple, and have well-defined behavior, instead turns out to exhibit unintentional complexity. Kinda like a fractal. This begs the question of whether hackers like bugs, or not. Most of them spend most of their time creating more, so you be the judge. The bug I'm alluding to in the comic is this: What if the computer, when drawing some word, stumbled over a unicode character that was not in the font. And then say it went to draw the little box instead, and fill in the numbers to indicate what character it was. Except it turned out that its font didn't tell it how to draw the numbers either. And thanks to a really unlikely bug, it then proceeded to recurse, drawing smaller and smaller boxes for these characters that it didn't know how to draw. Until it drew a fractal instead. See: It's just hilarous once I've explained it. (And that explanation of the word "cat", by the way, is why I don't try to write most of the technical posts in my blog in a form that a layman could understand.)

Evan Prodromou: 21 Prairial CCXV

It was warm tonight, so I made nachos and a big salad for dinner. I took the opportunity to capture my Nachos recipe for you to enjoy. Yes, nachos are a really easy food to make, but so many people make them so wrong, I figured I should write a recipe for people to get them right. tags:

10 June 2007

Daniel Burrows: Dear Lazyweb: Mercurial Python API

So, in the midst of trying to convert some Darcs repositories to Mercurial repositories (see here for the reason), I hit an "interesting" bug: tailor processes "rename" patches by deleting the renamed file. A little debugging later, I get to this simulation of what tailor does:


>>> from mercurial import hg,ui
>>> uio = ui.ui(debug=True,verbose=True)
>>> r = hg.repository(ui=uio, path='.', create=True)
>>> f = file('A', 'w')
>>> f.write('Some data\n')
>>> f.close()
>>> r.add('A')
>>> r.commit(text='Add A')
A
'i\xe9\xb4\xc8\x9d\xb8\xeb\xbe\xb1k\xae\xb1\x182\xa9ao\x80\xd0'
>>> r.copy('A', 'B')
B does not exist!


Huh? Of course B doesn't exist, that's why I want to create it! So, we look at the code in localrepo.py to handle copying...


def copy(self, source, dest, wlock=None):
p = self.wjoin(dest)
if not os.path.exists(p):
self.ui.warn(_("%s does not exist!\n") % dest)
elif not os.path.isfile(p):
self.ui.warn(_("copy failed: %s is not a file\n") % dest)
else:
if not wlock:
wlock = self.wlock()
if self.dirstate.state(dest) == '?':
self.dirstate.update([dest], "a")
self.dirstate.copy(source, dest)


Double huh?


  1. Why is this method checking whether the destination exists before it does anything? It appears to me that this is actually necessary; just disabling this test leads to a crash later.
  2. How does mercurial work at all with such huge breakage in its core code? Does /usr/bin/hg use a different implementation of the repository code than mercurial.hg?
  3. Why, in the name of $DEITY, is this a warning and not a fatal exception? One example of what happens when you don't signal to your users that you're ignoring them is this bug: tailor happily goes ahead and removes the original file, safe in the knowledge that mercurial has copied it to the new location. Except, of course, that mercurial hasn't actually copied it. Whoops.


I'm hoping that someone will tell me that it's just too late at night for me and I'm being an idiot. Please tell me this. It would make me very sad if code like that was in my VCS.


:-( --- sad Daniel

Christoph Berg: Postpone

I just finished implementing postpone, a wrapper that is intended to take an arbitrary command, fork into the background, wait until some lockfile is freed, and then run the command. Of course the idea is that the lockfile is /var/lib/dpkg/lock, and that postpone is used in maintainer scripts. (Update-menus already does that, and I've basically grabbed that code and generalized it as a separate program.) As a test implementation, I modified the post inst,rm templates in the tex-common package and rebuilt texlive-lang-* using that. dpkg -i texlive-lang-*.deb takes over 4 minutes in the old version, but only a total of 60s with postpone used (35s for dpkg -i plus 25s for the background jobs). A Debian package is currently sitting in NEW, let's hope it will actually get used in maintainer scripts.

Adam Rosi-Kessel: Hospital Thoughts

Hospital CEO Paul Levy is seeking responses to some remarkably frank comments on competition in the hospital industry:
…Please remember that health care is not like other industries, in which companies are rewarded in the marketplace for being the high-quality, low-cost provider. That situation does not yet exist in the health care system. So, am I better off being a industry leader with regard to that approach, or am I better off biding my time and continuing to follow the traditional path until there is a real sign of change in the marketplace?
As I’ve written before, this kind of openness is refreshing and potentially a brilliant business strategy. (It may continue to be so even once every one is doing it.) Paul’s comments and receptivity to feedback remind me of my numerous concerns about Children’s Hospital Boston, which, as far as I know, has no analogous public forum. I’ve sent in comment cards, but they may just drop into a black hole. Two principal complaints about Children’s Hospital: television and food. There are TVs everywhere, including in the waiting rooms. They are always on, even if no one is watching them. On one occasion, we were the only ones in the waiting room. When we attempted to turn the TV off, the staff told us we couldn’t. When we went in examination rooms and our daughter was unhappy, the first response by the medical staff was often to turn on a TV. Our daughter (just over two years old) has never watched TV, and doesn’t find it comforting. Research indicates that TV is not good for young kids, and especially not infants:
Babies are glued to television sets these days, with 40 percent of 3-month- olds and 90 percent of 2-year-olds regularly watching TV, according to a University of Washington study released Monday. …”While appropriate television viewing at the right age can be helpful for both children and parents, excessive viewing before age 3 has been shown to be associated with problems of attention control, aggressive behavior and poor cognitive development,” Frederick Zimmerman, the UW study’s lead author, said in a news release…. The American Academy of Pediatrics recommends no television for children younger than 2, and only one to two hours a day of quality programming for older children.
Recently, we had to stay over in the hospital for a night. There were no private rooms available, so we requested at least not to be stuck in a room where the TV would always be on. They looked at us like we were from Mars. (In the end, our roommate’s TV was always on. The three month old patient didn’t care, but his private nurse wanted to watch TV.) Why is a pediatric healthcare facility encouraging TV for infants? The food complaint is similar: so much of the hospital food provided for children is high in fat, refined sugar, white flour, and artificial ingredients. I was looking for a fruit-juice popsicle for our daughter (what she eats at home), and the only options the hospital could offer had high glucose corn syrup as the first ingredient after water. Again, this is not rocket science — these are not appropriate foods for one- and two-year old children. I realize in both cases (TV and food), the hospital is just mirroring popular culture in an attempt to provide familiarity for most kids, but I wish they would at least provide an option for those families whose kids don’t watch TV and eat a high-sugar diet.

Pierre Habouzit: git 1.5 on alioth

thanks to Rapha l again. git gc, nice hooks, branch tracking, ... all this is yours. Now that git-gc is on alioth, as alioth has a gitserver (and hence provides a not dumb transport like http), please run git gc from time to time so that repositories keeps beeing small (hi XSF ;p) FWIW I also will maintain git-core backports on bpo starting ... now. [sorry for the closed comments, I can't stand spam on my blog anymore]

MJ Ray: Please Stop Abusing the Redways

There are 1988 and 1989 papers by Cyclecraft Author John Franklin about poor accident records of the Milton Keynes Redways which are often cited by cyclists as showing why cycle facilities are dangerous or "farcilities". But I grew up riding the Redways and I think the closest I came to seeing a Redway-caused injury was when we accidentally rode onto an under-construction stretch by mistake and met a road roller. I journeyed to work all the way along the north-west edge when I was employed in MK one summer. (The cross-city Redway I used was fairly quiet on the journey to work around 0700 but quite busy on the return - looked like "school run" traffic.) I lived three miles from the MK boundary for a decade and so I've had some time to think about this. I think condemning the Milton Keynes Redways as dangerous farcilities is simplistic and misguided. Here's why: Milton Keynes was one of the first English cities to have cycle routes designed in from the start. This means that there are cycle tracks of types and in spaces that we hadn't seen before. Where else did you get a network of both low-friction surface high-speed cycle routes with sweeping bends and grade-seperated junctions and connecting routes to every estate? How many places have that added since? Almost nowhere. Milton Keynes is a massive cycle track experiment. In the 1989 paper, Franklin comments that it was "constructed with few limitations of space or finance" which simply doesn't ring true - the experiment didn't go completely to plan and the "secondary grid" of Redways between district centres mentioned in the 1998 paper has simply never appeared. Nevertheless, there are things that work amazingly well, but there are others which are now obviously stupid, like not protecting the sight lines at some junctions and putting late-80s estate routes alongside feeder roads, where they have more frequent and busier level junctions. I believe some of the London data also suggests that the non-separated junctions are one of the three most dangerous places, which suggests that Milton Keynes is not a cycle track advocate's perfect design in the first place. I'll continue to explain what else I disagree and agree with from the Franklin articles over a few more posts. If you have comments about the Redways or these articles, I'd like to hear them: please use the comments form at the bottom of my page.

Mark Brown: Not so bad

It’s not unknown for people maintaining Debian packages via sponsorship to become frustrated with the process sometimes - a feeling sometimes shared by sponsors who find that the person they’re just nodding through packages. This sort of frustration with process gets pretty depressing at times so it’s a bit of a shock to see us being held up as an example a better way. Of course, the two cases covered here not the same at all but it is still good to see things like that. It looks like we may well continue to make progress with this thanks to proposals like having Debian Maintainers as well as developers - another iteration of ideas like sponsorship which was originally developed to work around a process problem that people were seeing at the time with NM.

Steve Kemp: You and I in a little toyshop

Surprisingly many local people seem to be catching icky-illnesses of death recently. Both Megan and myself are under the weather recently. I managed to infect her with a nasty cough and cold on Wednesday and the pair of us have been mostly shivering indoors since then. Today is the closing day of The Leith Festival (Leith being a district of Edinburgh. Where we live.) So we made it outside and consumed beer and pies for a while. Now we're back and I'm wishing I'd not left the house. Still it could have been worse I could have been in the sun in a blurry suit and without any books! (Books visible and recognizable include the complete works of Terry Pratchett, minus two, the complete works of Steven Brust (Maybe Vlad will give me the edge in the assassins game!))
Steve in Leith Meg likes pies
All being well we'll be more recovered in time for the Debconf7 activities, although I expect Meg to be driving around Scotland for part of the time with a friend and not completely available. (A three-day roadtrip with Emma - a local girl who is hoping that somebody at Debconf will be able to fix her Ubuntu laptop..?) Update: - Debconf7 game of Settlers of Catan..? (I have only the Zarahemla set myself, but it will suffice for four players in a pinch.)

Chris Lamb: Sudoku solver in PostScript

There seems to have been a bit of fuss over this Sudoku solver implemented in SQL. In Easter 2005, when Sudoku fever kicked off in a big way in England, my Dad started writing a solver implemented in PostScript which I then modified so that it could perform backtracking. I also wrote a C# solver for my phone around the same time and later sneakily won a competition with it - I am now barred from entering competitions in that paper. Anyway, here is an example PostScript board (PDF version). It was labelled “Fiendish” in The Times. The board can be easily changed at the top of the PostScript file. NB. Best results are achieved if you view the PostScript directly in a viewer such as gv or GSview as you actually see the process of backtracking in solving the puzzle, the recursion depth and the set of possible symbols for each square — most PDF viewers are terrible at displaying the process as they seem to render inside the wrong thread. (In terms of solving the puzzle, we both found that by enforcing the simplest constraints and then ‘guessing’ was far easier and more efficient than performing any of the complicated constraints typically employed by human solvers. I’m certain I am not the first to notice that attempting to emulate the brain’s method of solving a problem is usually a short-sighted approach for a computer.) There are few other goodies in the file: replacing the final autotest with autotestR will recurse using the right-most possible symbol - if you get the same board with both of these then the initial board has a unique solution. Also, if you can get your hands on a true PostScript printer, printing the file will mean the puzzle is solved in hardware. Enjoy :) . I’m looking forward to DebConf7! UPDATE: Added PDF version.

Enrico Zini: things-not-to-do

Things not to do with lvm and crypto At least as of june, 2007, you should never do this: "...I need some encrypted storage space...":
lvcreate -L1G -n test vgname
cryptsetup luksFormat /dev/vgname/test
cryptsetup luksOpen /dev/vgname/test test1
mke2fs -j /dev/mapper/test1
mount /dev/mapper/test1 /mnt
# ...copy important data to /tmp...
"...oh, I need more space...":
lvresize -L+1G /dev/vgname/test
# cryptsetup resize test1 did not seem to
# work, so why not try this instead:
cryptsetup reload test1 /dev/vgname/test
resize2fs /dev/mapper/test1
Message from syslogd@localhost at Sun Jun 10 13:17:37 2007 ... localhost kernel: journal commit I/O error
"...oh damn. What happened?":
umount /mnt
mount /dev/mapper/test1 /mnt
EXT3-fs warning (device dm-13): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure EXT3-fs warning (device dm-13): ext3_clear_journal_err: Marking fs in need of filesystem check.
"...let's check it then...":
umount /mnt
e2fsck /dev/mapper/test1
"...what the hell is going on?":
e2fsck -fy /dev/mapper/test1
"...$ & ! ^ @ $ ( Y ^ Q ! @ % # !!!".

Daniel Burrows: Closing bugs just because they're old is not cool

Two bug reports that I wrote were recently closed with the following explanation:

Last message was posted nearly three years ago. Considering abandoned and closing.


Whoops, I thought, I must have missed a request for more information. So I went to the bug page and, nope, the only message on the bug was my initial report.

Let me repeat that: the total sequence of interactions on these bugs was:


  1. I report a bug in 2004
  2. Someone closes it in 2007 because it's "too old".


Now, there are times when it's at least somewhat excusable to close old bugs without verifying that they're fixed (or even knowing that they might not be). When a package has hundreds of bug reports, closing old bugs that can't be reproduced can be a good thing: even if the reports are valid, keeping reports that can't contribute towards a fix around is arguably less useful than cleaning out the bug list so it's usable.

In my case, though, the package in question has only 20 or so bug reports, an easily managed number. Worse, both bugs I reported could be trivially reproduced. One of them was arguably not a bug, but the guy who closed my bugs did not argue that; as far as I can tell, he didn't even look at my bug report.


Notice that I haven't mentioned the maintainer of the package? That's because he didn't close the bug. In fact, the person who closed the bug is not a member of Debian, nor is he in the NM process. Evidently he's just a random user who decided that old bugs offend him, so they should be closed.

So please, everyone, exercise a modicum of common sense when it comes to closing bug reports. This will keep the BTS useful for all of us and keep blood pressures at a reasonable level. :)

Next.

Previous.