Reviewed and uploaded to Oneiric:
acpi 1.5-3ubuntu1
smbldap-tools 0.9.5-1ubuntu1
multimon 1.0-5ubuntu1
monobristol 0.60.3-1ubuntu1
djbdns 1:1.05-8ubuntu1
Triaged and marked not relevant for Oneiric:
muttprint
ladcca
pdumpfs
mpc
dvi2dvi
Showing posts with label bugs. Show all posts
Showing posts with label bugs. Show all posts
Wednesday, August 3, 2011
Saturday, July 30, 2011
Patch Pilot report: 2011-07-30 (approximate)
Reviewed and uploaded to Oneiric:
wmii 3.9.2+debian-3ubuntu1
psycopg2 2.2.1-1ubuntu3
libmatthew-java 0.7.3-1ubuntu1
daemontools 0.76-3ubuntu3
scanbuttond 0.2.3.cvs20090713-5ubuntu1
mtr 0.80-1ubuntu1
fail2ban 0.8.4+svn20110323-1ubuntu1
java2html 0.9.2-4ubuntu1
gogoc 1.2-4ubuntu1
coherence 0.6.6.2-5ubuntu1
uw-imap 2007e~dfsg-3.1ubuntu3
tcc 0.9.25-9ubuntu1
nethogs 0.7.0-3ubuntu1
multicd 1.7.3-1ubuntu1
eyed3 0.6.17-1ubuntu1
Triaged and marked not relevant for Oneiric:
libwibble
gdal
lua-xmlrpc
prototypejs
mt-daapd
kdiff3
wmii 3.9.2+debian-3ubuntu1
psycopg2 2.2.1-1ubuntu3
libmatthew-java 0.7.3-1ubuntu1
daemontools 0.76-3ubuntu3
scanbuttond 0.2.3.cvs20090713-5ubuntu1
mtr 0.80-1ubuntu1
fail2ban 0.8.4+svn20110323-1ubuntu1
java2html 0.9.2-4ubuntu1
gogoc 1.2-4ubuntu1
coherence 0.6.6.2-5ubuntu1
uw-imap 2007e~dfsg-3.1ubuntu3
tcc 0.9.25-9ubuntu1
nethogs 0.7.0-3ubuntu1
multicd 1.7.3-1ubuntu1
eyed3 0.6.17-1ubuntu1
Triaged and marked not relevant for Oneiric:
libwibble
gdal
lua-xmlrpc
prototypejs
mt-daapd
kdiff3
Wednesday, July 27, 2011
Patch Pilot report: 2011-07-26 (approximate)
Reviewed and uploaded to Oneiric:
base-files 6.4ubuntu3
bibus 1.5.1-3ubuntu1
cricket 1.0.5-13ubuntu1
icecc 0.9.6-1ubuntu1
lashwrap 1.0.2-0ubuntu7
lomoco 1.0beta1+1.0-5ubuntu4
rp-pppoe 3.8-3ubuntu1
tig 0.17-1ubuntu1
Reviewed and marked not relevant for Oneiric:
tclxml
soci
base-files 6.4ubuntu3
bibus 1.5.1-3ubuntu1
cricket 1.0.5-13ubuntu1
icecc 0.9.6-1ubuntu1
lashwrap 1.0.2-0ubuntu7
lomoco 1.0beta1+1.0-5ubuntu4
rp-pppoe 3.8-3ubuntu1
tig 0.17-1ubuntu1
Reviewed and marked not relevant for Oneiric:
tclxml
soci
Wednesday, July 20, 2011
Patch Pilot report: 2011-07-20
Reviewed and uploaded to Oneiric:
tictactoe 0.8.1-5ubuntu1
pct-scanner-scripts 0.0.4-3ubuntu1
gpredict 1.3-1ubuntu1
coolkey 1.1.0-8.1ubuntu1
sbackup 0.11.4-0ubuntu4
bcfg2 1.1.1-3ubuntu3
Reviewed, updated SRU information and uploaded to -proposed:
w-scan 20091230-1ubuntu0.1, 20100316-3ubuntu0.1 and 20101001-1ubuntu0.1
wackamole 2.1.1-3.1ubuntu0.10.04.0, 2.1.1-3.1ubuntu0.10.10.0 and 2.1.1-3.1ubuntu0.11.04.0
lash 0.6.0~rc2-5ubuntu0.1
Reviewed and closed as not-applicable in Oneiric:
fusion-icon
tigr-glimmer
tictactoe 0.8.1-5ubuntu1
pct-scanner-scripts 0.0.4-3ubuntu1
gpredict 1.3-1ubuntu1
coolkey 1.1.0-8.1ubuntu1
sbackup 0.11.4-0ubuntu4
bcfg2 1.1.1-3ubuntu3
Reviewed, updated SRU information and uploaded to -proposed:
w-scan 20091230-1ubuntu0.1, 20100316-3ubuntu0.1 and 20101001-1ubuntu0.1
wackamole 2.1.1-3.1ubuntu0.10.04.0, 2.1.1-3.1ubuntu0.10.10.0 and 2.1.1-3.1ubuntu0.11.04.0
lash 0.6.0~rc2-5ubuntu0.1
Reviewed and closed as not-applicable in Oneiric:
fusion-icon
tigr-glimmer
Tuesday, July 19, 2011
Thursday, December 2, 2010
Low-hanging fruit? We have plenty!
Martin asks whether we've exhausted the low-hanging fruit. From my myopic lens, emphatically no. Despite dwindling available resources for Ubuntu (and FOSS, generally) development, I've continued to contribute a spattering of fixes. Doing so is pretty simple, and I'm happy to walk people through the process.
But don't take my word for it.
But don't take my word for it.
Tuesday, April 6, 2010
Public service announcement: Read the original bug reporter's summary before adding unrelated comments
I find that I'm wasting considerable time trawling through bug reports where comments not from the original reporter indicate experiences involving very different software configurations. For instance, person A files a bug against pulseaudio on default Ubuntu, and you see very similar symptoms on default Kubuntu and thus proceed to add some comments to the bug report.
File a separate bug.
The bug reporter's symptoms don't involve Phonon at all, but yours do. You've just splattered over an otherwise useful timeline, which generally makes me want to take a long springtime walk instead of fixing the actual bug. Thanks for understanding.
File a separate bug.
The bug reporter's symptoms don't involve Phonon at all, but yours do. You've just splattered over an otherwise useful timeline, which generally makes me want to take a long springtime walk instead of fixing the actual bug. Thanks for understanding.
Friday, April 2, 2010
Public service announcement: When in doubt, don't splatter your apport info into an existing ALSA bug report
Folks -
Please, please don't apport-collect -p alsa-base foo (or apport-collect foo in 10.04 LTS) into a bug report that you didn't file unless a member of the audio dev team explicitly requests it. What we end up with are reports that start from the original reporter as "my laptop's internal mic doesn't work" and end with dozens of unrelated comments from other people along the lines of "my laptop's internal speakers are too loud".
Here's the gist: your symptoms may be eerily similar, but your audio hardware often is quite different, which means that resolving the original reporter's bug symptoms should only affect that reporter's hardware. Of course, if you have identical hardware, then your symptoms will be resolved in your own bug report, too. If you didn't file the original bug report, please just file a new one. Thanks for understanding.
Please, please don't apport-collect -p alsa-base foo (or apport-collect foo in 10.04 LTS) into a bug report that you didn't file unless a member of the audio dev team explicitly requests it. What we end up with are reports that start from the original reporter as "my laptop's internal mic doesn't work" and end with dozens of unrelated comments from other people along the lines of "my laptop's internal speakers are too loud".
Here's the gist: your symptoms may be eerily similar, but your audio hardware often is quite different, which means that resolving the original reporter's bug symptoms should only affect that reporter's hardware. Of course, if you have identical hardware, then your symptoms will be resolved in your own bug report, too. If you didn't file the original bug report, please just file a new one. Thanks for understanding.
Subscribe to:
Posts (Atom)