Date: Sat, 2 Feb 2013 11:28:07 +0000 From: Chris Rees <utisoft@gmail.com> To: Dmitry Sivachenko <trtrmitya@gmail.com> Cc: Li-Wen Hsu <lwhsu@freebsd.org>, python <python@freebsd.org> Subject: Re: [Fwd: python33-3.3.0_2 failed on amd64 9.1-glib] Message-ID: <CADLo838CdB-4TKP=7DLkG2sKewspgRhXVkn%2B5hXkFNPUnOoZ7A@mail.gmail.com> In-Reply-To: <FAE77598-7864-468A-92D6-7FB12D7872D1@gmail.com> References: <CADLo83-SkxSwRiVhQWD6HeoX8g10shkqF5nGmK_NsxT5u6n6kg@mail.gmail.com> <FAE77598-7864-468A-92D6-7FB12D7872D1@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1 February 2013 18:51, Dmitry Sivachenko <trtrmitya@gmail.com> wrote: > Upgrade to 9-STABLE and it will package correctly. > > See http://svnweb.freebsd.org/base?view=3Drevision&revision=3D243331 That's great, and I understand that ports are only guaranteed to work on -stable etc... but don't you think that broken on latest release is unacceptable? Is there anything we can fiddle python-side to fix this? Chris > On 01.02.2013, at 21:53, Chris Rees <utisoft@gmail.com> wrote: > >> -------- P=C5=99eposlan=C3=A1 zpr=C3=A1va -------- >> >> [OK, it's not really Pav.] >> >> http://www.bayofrum.net/medusatb/9.1-glib-20130131165817/python33-3.3.0_= 2.log >> >> I've been doing a mini-exp-run for Koop Mast, and discovered that >> python33 fails to package. >> >> Chris >> _______________________________________________ >> freebsd-python@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-python >> To unsubscribe, send any mail to "freebsd-python-unsubscribe@freebsd.org= " >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo838CdB-4TKP=7DLkG2sKewspgRhXVkn%2B5hXkFNPUnOoZ7A>