Bug#693351: RM: kismet/2008-05-R1-4.3
>> If there are any bugs reported on functionality (which I doubt) then
>> it makes no sense trying to fix the 2008 version.
>
> Ubuntu has several SIGSEGV crashes reported on kismet 2008-05-R1-4.3:
> https://launchpad.net/ubuntu/+source/kismet/+bugs
I think that the ubuntu situation is orthogonal to the debian one.
Since ubuntu takes its packages from unstable, whether or not we
remove the package from stable is irrelevant.
Removing it from unstable is a different story.
> Upstream (Mike Kershaw, who I see at MHVLUG meetings) is frustrated by the
> fact that this old version of kismet is still being shipped in Ubuntu, because
> he regularly gets bugs reported to him directly from users that he isn't able
> to help with because the version is ancient. I'm adding Mike to the list of
> recipients so that he can have a chance to offer an opinion on whether
> 2008-06-R1-4.3 should be shipped in Wheezy (and thus shipped for another two
> years in Debian).
>
> It'll be good to get a newer Kismet package in Unstable, since Ubuntu is based
> on Unstable.
My package is almost ready, I expect only minor comments from the
review process which will take quite much time since the package is
huge and the changes really extensive.
>> All other bugs are OK.
>>
>> BTW, I guess there is no chance to have the new package in wheezy once
>> it gets released, is this correct?
>
> To get a new version in it would have had to have been in Unstable before the
> freeze in June. Around that time I made a newer Kismet package using
> debhelper v9, but it wasn't ready before the freeze and the package I made
> still needs a couple of tweaks, which is why I hadn't tried to file an ITA.
OK, this opportunity has passed, but at least I can aim to have the
package in unstable in time for the ubuntu 13.04 release.
This is first week of March, 2013.
> Nick -- let me know if you'd like to see what I did re: /debian/* files. The
> main thing that needs tweaking in the package I came up with had to do with
> the menu shortcut and how to handle access permissions correctly.
Thanks for your offer, but I think I'm ok for now.
I think I have already taken care of these two things.
>> If we need to fix anything then I will have to keep different branches,
>> i.e. one for stable and one for testing, right?
>
> Maybe. There will be different package versions, but "branches" implies using
> a version control system which isn't a requirement AFAIK.
Branches can be even two directories in my disk :)
In any case, I'm planning to put the package in a VCS after the review
process is finished.
BTW, something I'm curious in, is how many people will keep using the
old 2008 version in stable (if it is shipped after all) if ubuntu and
unstable/testing have the most recent one.
What would be your estimation? Is there any way to get statistics for
usage (popcon) depending on the release?
Would a response like "please use the recent version in testing " be acceptable?
Nick
Reply to: