Bug Squashing Day 10/15

neotuli · 2006-10-08 22:26:12

Hi everyone,

We're going to hold another bug squashing day this coming Sunday, the 15th
of October.

It's been quite a while since our last one, but it will still work the
same as it used to. Simply take a look at http://bugs.archlinux.org , find
a nasty bug you don't like, and find a way to fix it.

As always, everyone is welcome to join us on freenode.net in
#archlinux-bugs to discuss bugs. We'll try to have at least one
developer in there all day long to help out.

Happy hunting,

-S

Howitzer · 2006-10-09 15:15:21

Do you guys have a 'bug-solving-guide' anywhere?
I'm dying to do something back for the Arch community but i don't have any real skills.. (No coding, no art-skills, .. )

phrakture · 2006-10-09 15:21:13

If you don't know how to solve the bugs themselves, you can always help test the fixes.

By this I mean, hang out in the channel. When someone says "ok, I think I fixed this" you can test it out and see if it did fix it.

It's _always_ better to have someone who doesn't know how it was fixed to actually test the fix.

Romashka · 2006-10-09 15:50:01

Hi! I would like to participate but I never used IRC. :oops:
Can I post a list of bugs with [trivial] fixes already described [by me] in Flyspray's comments, but not yet fixed?
There are also many bugs that are quite old and already fixed but still not closed. Are there plans go through all old bugs to see if they are already [accidentally] fixed? I already has a short list of such bugs (and already posted comments about this to correspondent Flyspray's pages).

phrakture · 2006-10-09 16:29:33

I'm sure you could, but IRC is much easier, as it's live.

For those of you who don't know IRC, grab xchat or weechat or something, and connect to irc.freenode.net.

Then simply /join #archlinux-bugs and go from there

twiistedkaos · 2006-10-09 16:34:29

sounds good, I may participate. I have SaT's the day before. Depends.

Romashka · 2006-10-09 16:38:08

Ehehe, I'm on IRC!
I connected to European server calvino.freenode.net using Opera. Very nice and simple clent for IRC newbies like me.

shadowhand · 2006-10-09 17:03:27

Can I bring my can of Raid, or is that cheating?

Romashka · 2006-10-09 17:08:09

shadowhand wrote:

Can I bring my can of Raid, or is that cheating?

In my country farmers have "bug days" in which they kill hundreds of Colorado potato beetles (Leptinotarsa decemlineata).

Cerebral · 2006-10-09 19:39:12

shadowhand wrote:

Can I bring my can of Raid, or is that cheating?

You can bring your array of RAID. It might help bugs get squashed quicker.

yankees26 · 2006-10-09 22:13:18

Sounds fun, hopefully I can actually put what I know of C and C++ to work. And if that fails: TESTING

neotuli · 2006-10-15 03:50:39

bump

iphitus · 2006-10-15 12:09:32

im off to bed guys, 10pm sunday here.

~50 bugs squashed so far, many just old ones, many already fixed. found plenty of bugs to assign to myself for later fixing too

bugs I noticed while raiding that may be worth taking a look at:

makepkg: http://bugs.archlinux.org/index.php?tas … us=&date=0
heaps of makepkg bugs in there, many easy fixes, and small safe feature additions. a consolidated patch would be great.

ATI open source drivers:
few bugs in there regarding CPU usage and locking up. Someone go raid the Xorg/DRI mailing lists and CVS for a fix.

Installation Guide:
http://bugs.archlinux.org/task/4169
Ought to be perused and made sure it's up to date with tpowa's new ISOs, mkinitcpio and friends.

openvpn:
multiple openvpn bugs, feel free to consolidate or post new PKGBUILD.

xvidcap:
it's always broken: http://bugs.archlinux.org/task/4075

no coloured output on pacman:
http://bugs.archlinux.org/task/1105
needs some research to find exact problem

website:
the website's located in CVS somewhere, and there's a pile of bugs for it, so dont hesitate to attack the source of the website and submit patches. im sure someone will know the CVS location if you ask around. try searching the TU ml.

netcfg/network profile/network scripts:
Try NOT to attack these, there's new network scripts in development that will have them solved, so any patches will most likely go ignored.

lighttpd:
couple of bugs lying around, search, consolidated PKGBUILD with fixes might be nice.

kernel modules:
plenty of modules still have broken .install files that call depmod -A (uppercase A). These need to be hunted down and fixed.

If you've got any other bugs guys, report them. If you have any fixes, report them. Fixed PKGBUILDs are always nice too.

James

iphitus · 2006-10-15 13:14:30

also, if you dont want to mess with packages, the wiki is full of old and out of date stuff, so take a browse through there and see if there's anything you can do to help.

James

Cerebral · 2006-10-15 15:43:32

I'm tackling the depmod -A issue in [extra] right now.

And done.

yankees26 · 2006-10-15 21:08:48

iphitus: Thanks for the links (especially the makepkg one) I made two patches for makepkgs. One about checking return code of download and the other adding --skip-build (or -k) flag in order to repackage what is int $startdir/pkg.

Pierre · 2006-10-15 22:38:34

I think this was very successfull; perhaps we could do this more often. Perhaps once a month or so.

neotuli · 2006-10-16 05:21:40

Pierre wrote:

I think this was very successfull; perhaps we could do this more often. Perhaps once a month or so.

we used to, but it kind of got old and fell apart. Perhaps we'll start again, maybe every other month even. I have to take a look and see how many we ended up smashing.

iphitus · 2006-10-16 06:29:10

neotuli wrote:

Pierre wrote:
I think this was very successfull; perhaps we could do this more often. Perhaps once a month or so.
we used to, but it kind of got old and fell apart. Perhaps we'll start again, maybe every other month even. I have to take a look and see how many we ended up smashing.

problem with doing it more frequently, it loses it's appeal as neotuli said it did last time. first few might go well, but people grow old of the idea and forget about it.

2 months is good though, not too frequent, not too infrequent.

James

Romashka · 2006-10-16 09:30:47

I post here a copy of my IRC messages:

Hmm... just checked my Gmail for "#FRxxxx: ..." notifications and it seems that a dozen of trivial bugs are still not fixed. Now I'm checking them all and post a list here.
So, here is the list:
#4571, #2929, #2727, #5489, #5161 have patches in comments already available
#5526, #4313 - .desktop file needed
#3824 - can be closed, #3999, #4271 - "Fixed"
#4020, #4106 - "Won't fix"???, #3146, #5396 - not sure if they are valid
#4470 is duplicate of #4056
#3382 makepkg bug - reassign to phrakture (patch is available)
#4518 - is it still valid?
#2904 can be fixed
#3146 can be closed, IMHO
not sure about #4336
That's all. What do you think about this?

Romashka · 2006-10-24 08:03:30

Any volunteers to fix these bugs?

Arch Linux

#1 2006-10-08 22:26:12

Bug Squashing Day 10/15

#2 2006-10-09 15:15:21

Re: Bug Squashing Day 10/15

#3 2006-10-09 15:21:13

Re: Bug Squashing Day 10/15

#4 2006-10-09 15:50:01

Re: Bug Squashing Day 10/15

#5 2006-10-09 16:29:33

Re: Bug Squashing Day 10/15

#6 2006-10-09 16:34:29

Re: Bug Squashing Day 10/15

#7 2006-10-09 16:38:08

Re: Bug Squashing Day 10/15

#8 2006-10-09 17:03:27

Re: Bug Squashing Day 10/15

#9 2006-10-09 17:08:09

Re: Bug Squashing Day 10/15

#10 2006-10-09 19:39:12

Re: Bug Squashing Day 10/15

#11 2006-10-09 22:13:18

Re: Bug Squashing Day 10/15

#12 2006-10-15 03:50:39

Re: Bug Squashing Day 10/15

#13 2006-10-15 12:09:32

Re: Bug Squashing Day 10/15

#14 2006-10-15 13:14:30

Re: Bug Squashing Day 10/15

#15 2006-10-15 15:43:32

Re: Bug Squashing Day 10/15

#16 2006-10-15 21:08:48

Re: Bug Squashing Day 10/15

#17 2006-10-15 22:38:34

Re: Bug Squashing Day 10/15

#18 2006-10-16 05:21:40

Re: Bug Squashing Day 10/15

#19 2006-10-16 06:29:10

Re: Bug Squashing Day 10/15

#20 2006-10-16 09:30:47

Re: Bug Squashing Day 10/15

#21 2006-10-24 08:03:30

Re: Bug Squashing Day 10/15

Board footer