Custom Query (1145 matches)
Results (43 - 45 of 1145)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#721 | worksforme | mit-printing-config lpq sometimes tracebacks on Jaunty | jdreed | |
Description |
w20-575-44:~> lpq -Pajax Traceback (most recent call last): File "/usr/bin/lpq", line 8, in <module> load_entry_point('debathena.printing==1.23.2-ubuntu9.04', 'console_sc File "/var/lib/python-support/python2.6/debathena/printing/lpq.py", lin sys.exit(_main(sys.argv)) # pragma: nocover File "/var/lib/python-support/python2.6/debathena/printing/lpq.py", lin s.connect((server, 515)) File "<string>", line 1, in connect TypeError: coercing to Unicode: need string or buffer, NoneType found Further investigation reveals: consult / printing / ezyang 16:37 (Edward Z. Yang) >>> from debathena.printing import common >>> common.find_queue('ajax') (0, None, 'ajax') >>> from debathena.printing import common >>> common.get_cups_uri('ajax') u'file:///dev/null' >>> common.canonicalize_queue('ajax') (yes, that last line is blank) Further investigation is necessary to determine if this affects Jaunty, or just w20-575-44. |
|||
#725 | worksforme | do-build: package uploads and downloads should share a lock | jdreed | geofft |
Description |
While building for Maverick we ran into a bunch of builds that failed for hash sum mismatches or unauthenticated-package errors while trying to download Debathena packages. Presumably this is because of a race condition between reprepro uploading packages and apt-get in the build chroots downloading them. We already have a global lock for all reprepro invocations within do-build; it would be nice to get apt-get inside the chroot to share this lock (although somewhat hard, since that's inside the chroot, and run by sbuild). I'm also a bit confused here, because we use approx, which should 1) insulate us from this by caching and 2) not work, since we may need new packages as soon as they're uploaded. |
|||
#834 | worksforme | upgrade-schroots doesn't work | jdreed | |
Description |
zulu:~# all-schroots upgrade-schroot Chroot for distribution lenny-i386-sbuild-source, architecture amd64 not found Chroot for distribution lenny-i386-sbuild-source, architecture amd64 not found Chroot for distribution lenny-i386-sbuild-source, architecture amd64 not found (the message is repeated for each chroot we have). |