On Fri, Mar 16, 2012 at 07:47:54AM -0000, Micah Gersten wrote:
> Apologies, python3-defaults was fine, so I reuploaded that. After
> speaking with infinity, it seems that python-defaults just needs to be
> done in one publisher cycle or !i386 needs to build before the i386
> binaries are published. slangasek also mentioned that not the whole
> source needed to be arch:any, might be worth having a discussion about
> this.
I haven't looked closely at the dependencies to see why python was changed
to Arch: any. From a top-level POV, the only packages I was concerned with
were the -dev packages; it's entirely possible that python also has to be
Arch: any to make any use of those.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>
On Fri, Mar 16, 2012 at 07:47:54AM -0000, Micah Gersten wrote:
> Apologies, python3-defaults was fine, so I reuploaded that. After
> speaking with infinity, it seems that python-defaults just needs to be
> done in one publisher cycle or !i386 needs to build before the i386
> binaries are published. slangasek also mentioned that not the whole
> source needed to be arch:any, might be worth having a discussion about
> this.
I haven't looked closely at the dependencies to see why python was changed
to Arch: any. From a top-level POV, the only packages I was concerned with
were the -dev packages; it's entirely possible that python also has to be
Arch: any to make any use of those.
-- www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://
<email address hidden> <email address hidden>