Find the right... package?

Brian Murray brian at ubuntu.com
Wed May 26 17:59:29 BST 2010


On Wed, May 26, 2010 at 11:13:56AM -0500, Micah Gersten wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 05/26/2010 10:44 AM, Brian Murray wrote:
> > On Tue, May 25, 2010 at 08:34:18PM -0400, David Tombs wrote:
> >> On 05/20/2010 04:21 PM, C de-Avillez wrote:
> >>> On Thu, 2010-05-20 at 00:15 +0200, Philip Muskovac wrote:
> >>>> As most of us know we have a wiki page about that.
> >>>>
> >>>> https://wiki.ubuntu.com/Bugs/FindRightPackage
> >>>>
> >>>> What I'm wondering about is:
> >>>> Is anyone actually taking care of that page regularily? The fact that I
> >>>> recently added notify-osd and plymouth to the page seems to say no.
> >>>> Considering that we reference that page at a lot of places (and not only
> >>>> on team internal pages) we should get more people to add information to it.
> >>>> How about having a wiki day/week about a week before Feature/Beta Freeze
> >>>> to update it for the new release?
> >>>
> >>> This sounds like a good idea. Care to jump-start the process? ;-)
> >>>
> >>>>
> >>>> Here a few things that I find are missing and I'm not sure what the best
> >>>> way to add them is / I don't know enough about them to add them:
> >>>>
> >>>> - general system bootup / grub2 upstart? We only have references for
> >>>> splash, kernel, xorg and live disk. I'm not sure how much detail would
> >>>> be right here.
> >>>> - does it make sense to add something encryption related?
> >>>> - Mention the indicators?
> >>>> - drivers? (Or should jockey be a bit more verbose?)
> >>>>
> >>>> Also I only found the storage symptom being mentioned and I'm sure
> >>>> others can add more to the list.
> >>>
> >>> Theoretically, we should be continuously correcting/adding/adjusting
> >>> this page, and all others related to it. 
> >>>
> >>> @All: please feel free to collaborate. If in doubt, there is always this
> >>> mailing list, or the #ubuntu-bugs IRC channel.
> >>>
> >>> Thank you,
> >>>
> >>>
> >>>
> >>
> >> I try to update it when I encounter a wrong-package bug that could have
> >> been prevented with information on the page. I do think updating it
> >> based on each new release is a good idea, though, and I wrote a reminder
> >> to myself to do that for 10.10.
> > 
> > This sounds like something worth recording on a TODO list for the Bug
> > Squad.  I think there should be some on going tasks like this one and one
> > time tasks like "package xyz was removed from the archive and all its
> > bug tasks should be reviewed for SRU-able bugs and the rest set to Won't
> > Fix".
> >  
> > --
> > Brian Murray
> > Ubuntu Bug Master
> > 
> 
> I suggest there be a mail to the devel list before doing this.  A
> package might be coming back in the next release, but was unusable in
> the current release, or maybe it was unmaintainable for 3 yrs, but 1.5
> is fine.

I'd hope that information like that is included in "removal_comment" for
the source package.  Looking at an old results set a lot of the packages
were removed from Debian.  Consider the following:

"(From Debian) RoQA; orphaned, dead upstream, php4 based, low popcon"

But of course if the removal reason was vague contacting the devel
mailing list makes absolute sense.

--
Brian Murray
Ubuntu Bug Master
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20100526/d825b126/attachment.pgp 


More information about the Ubuntu-bugsquad mailing list