Bug#172890: #172890: libxaw6: passwords visible in widgets [fixed in libxaw7]
On Tue, Sep 25, 2007 at 15:25:22 +1000, Drew Parsons wrote: > In my opinion it should be safe to remove libxaw6 because > a) any such 3rd-party packages should really be rebuilt against libxaw7 > anyway, > b) libxaw6 can still be grabbed from etch if really needed. > agreed. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#172890: #172890: libxaw6: passwords visible in widgets [fixed in libxaw7]
> > If all of these were updated, then we could drop the package and close > > this bug. > > All these three packages now use libxaw7. > > However, screenkast now exists, and uses libxaw6. I'll file a bug against it. > screenkast has now been updated to use libxaw7. No packages remain in the Debian archive which use libxaw6. Do we have consensus to remove libxaw6 completely, or would anyone prefer to leave it in in case any 3rd-party packages need it? In my opinion it should be safe to remove libxaw6 because a) any such 3rd-party packages should really be rebuilt against libxaw7 anyway, b) libxaw6 can still be grabbed from etch if really needed. Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#172890: #172890: libxaw6: passwords visible in widgets [fixed in libxaw7]
Joey Hess wrote > Currently in unstable there are three packages left that use xaw6: > > xkbsel > snake4 > pload > > If all of these were updated, then we could drop the package and close > this bug. All these three packages now use libxaw7. However, screenkast now exists, and uses libxaw6. I'll file a bug against it. Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
