I have no idea. I fixed a few things (they changed the API around a bit,
breaking non-bundled media compilers), but even after fixing that, I'm
getting a much more concerning error. I'll try to track it down and see if
we can fix it, but if not, it'll need to be fixed in pipeline.
Given the API changes, I'd be concerned about reverting code in pipeline
for the package.
I'll keep you informed as I learn more.
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Mon, Aug 6, 2012 at 4:32 PM, Stephen Gallagher <step...@gallagherhome.com
> On Mon, 2012-08-06 at 15:18 -0700, Christian Hammond wrote:
> > There's a few things that it seems are broken with newer Pipelines. I
> > know for sure that 1.2.1 works. Any way you could just package that
> > for now? Looking into the remaining things, but there's some ugly
> > issue I'm not completely sure about yet.
> Ugh, unfortunately not. It's a real pain to revert a version in Fedora.
> (It can be done, such as when regressions necessitate it), but it's
> never done lightly. It requires mangling the version numbers in a
> particularly ugly way to ensure that anyone who happened to install the
> previous package will still update to the new one (despite the version
> being lower).
> I don't suppose you could point me at specific patches that I could
> revert in the django_pipeline 1.2.14 release instead that would get it
> working in the meantime?
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at