Pipelight

Bug #1283025
Comment #18

Comment 18 for bug 1283025

Revision history for this message

Erich E. Hoover (ehoover) wrote on 2014-02-21:

#18

Hello everyone,

I sincerely apologize for my mistake here, this problem was a single letter typo in the configure script that I did not notice because I did not re-run ./configure before doing final testing. This change was due to a feature request from people running source-based distributions that we provide a configure option to cause the build to fail when extended filesystem attributes are not available. Due to a mistake on my part this change ended up unintentionally disabling extended attributes across the board (leading to the problem you have seen). The fixed build is now posted to the official repo (and the old repo), if you update again then everything should go back to normal.

I would kindly request that you please _not_ disable the auto-updating of the package, the rigorous testing of this package helps us catch these issues quickly so that we can improve the quality of our patches in the hope that we can get them included in upstream Wine. This is important because once these patches are in upstream Wine then it is no longer necessary to use our specially compiled version. It is also important to recognize that mistakes like this are pretty rare events, as we push a new stable release every two weeks (coincident with new Wine releases) and this is probably the first time you've seen an issue. The last time we had a problem like this (1.7.8) we instituted some new build procedures to prevent that class of problem from recurring in the future, and we are currently trying to do the same for this particular type of problem. Also, if you are willing to help prevent these problems from occurring in future releases then you can help us out by testing the daily builds*:
sudo add-apt-repository ppa:pipelight/stable

Again, my sincerest apologies for this problem - hopefully this is the last time that such a mistake will occur.

* Unfortunately, due to some recent launchpad strangeness with having "too many" simultaneous builds we can only do daily builds for Precise, Trusty, and Saucy at the moment. I'm hoping that at some time in the near future that I'll be able to figure out what causes the build to hang and fix that issue so that we can do daily builds for all the supported Ubuntu releases.

Hello everyone,

I sincerely apologize for my mistake here, this problem was a single letter typo in the configure script that I did not notice because I did not re-run ./configure before doing final testing.  This change was due to a feature request from people running source-based distributions that we provide a configure option to cause the build to fail when extended filesystem attributes are not available.  Due to a mistake on my part this change ended up unintentionally disabling extended attributes across the board (leading to the problem you have seen).  The fixed build is now posted to the official repo (and the old repo), if you update again then everything should go back to normal.

I would kindly request that you please _not_ disable the auto-updating of the package, the rigorous testing of this package helps us catch these issues quickly so that we can improve the quality of our patches in the hope that we can get them included in upstream Wine.  This is important because once these patches are in upstream Wine then it is no longer necessary to use our specially compiled version.  It is also important to recognize that mistakes like this are pretty rare events, as we push a new stable release every two weeks (coincident with new Wine releases) and this is probably the first time you've seen an issue.  The last time we had a problem like this (1.7.8) we instituted some new build procedures to prevent that class of problem from recurring in the future, and we are currently trying to do the same for this particular type of problem.  Also, if you are willing to help prevent these problems from occurring in future releases then you can help us out by testing the daily builds*:
sudo add-apt-repository ppa:pipelight/stable

Again, my sincerest apologies for this problem - hopefully this is the last time that such a mistake will occur.

* Unfortunately, due to some recent launchpad strangeness with having "too many" simultaneous builds we can only do daily builds for Precise, Trusty, and Saucy at the moment.  I'm hoping that at some time in the near future that I'll be able to figure out what causes the build to hang and fix that issue so that we can do daily builds for all the supported Ubuntu releases.