My company uses an overlay to manage multiple Gentoo servers and workstations. The overlay list is stored in a Subversion repository, which is made available over HTTPS with basic authentication. Prior to layman 1.1.* when fetching the overlay list (e.g. layman -f -o https://.... or layman -S -o https://....) a username/password prompt would be issued, e.g. layman -S -o https://www.orican.eu/.... Enter username for Intranet at www.orican.eu: abc Enter password for abc in Intranet at www.orican.eu: When using layman-1.1 or later, issuing the same command fails, e.g. layman -S -o https://www.orican.eu/.... * Failed to update the overlay list from: https://www.orican.eu/.... * Error was: * HTTP Error 401: Authorization Required * Failed to read a cached version of the overlay list from https://www.orican.eu/.... You probably did not download the file before. The corresponding entry in your layman.cfg file will be disregarded. * Error was: * Failed to read the overlay list at ("/usr/portage/local/layman/cache_21864352b0516f3a5f80d451ab290306.xml")! * Error was: * [Errno 2] No such file or directory: '/usr/portage/local/layman/cache_21864352b0516f3a5f80d451ab290306.xml' I suspect this is related to bug 150741 which switched from urllib to urllib2, but I don't have time to learn Python to find out! :-) Reproducible: Always Steps to Reproduce: 1. Install a layman-1.1 or higher 2. Try to sync an overlay list protected with basic authentication Actual Results: Layman fails to fetch the overlay list, reporting an HTTP 401 authorization required error. Expected Results: Layman should prompt for the required authentication details, as in versions prior to version 1.1.
While this may have worked before and thus is a regression it was not necessary planned that way :) I'd rather consider that a new feature for >=layman-1.2.0. The problem is that I currently lack time for coding on the tool and somebody with a similar problem would need to contribute a patch for that.
(In reply to comment #1) > I'd rather consider that a new feature for >=layman-1.2.0. The problem is that > I currently lack time for coding on the tool and somebody with a similar > problem would need to contribute a patch for that. I agree with Gunnar: to make this happen, someone needs to contribute a patch. I plan to close this bug on 2010-08-05 if no patch arrived in the mean time. Thank you for your understanding.
> I plan to close this bug on 2010-08-05 if no patch arrived in the mean time. > Thank you for your understanding. Closing as announced.
