It seems like there has been a lot of complaints about how the update-manager handles the 403 error. Considering the only time the 403 would normally occur is this situation, maybe the update manager could be smarter about it?
On Nov 17, 2007 11:20 AM, Jamie Strandboge <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Matt Zimmerman wrote: > > The security team should follow up to ubuntu-security-announce to notify > > users who received the USN once they have prepared a response. > > > > Updated packages are now available via security.ubuntu.com. The website > has been updated with a new USN, and the new USN has been sent to > [EMAIL PROTECTED] > > Details can be found here: > https://www-admin.ubuntu.com/usn/usn-544-2 > > Jamie Strandboge > > - -- > Email: [EMAIL PROTECTED] > IRC: jdstrand > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHPwbBW0JvuRdL8BoRAszoAJ473g2kLKvdIu5jHaNbohNwLFex9wCfcdFU > Lj2TYMyuYRFQlEeeLIvBx8U= > =NVnG > -----END PGP SIGNATURE----- > > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > -- Firefox (www.getfirefox.com) -- A browser you can trust
-- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
