Menu

#371 Build test error

open
Gbrowse (196)
5
2014-08-13
2011-06-18
sallou
No

Hi,
I downloaded version 2.38 of GBRowse2 at CPAN.
I have an error at Build test time, solved in 2.31:

* Fixed "testdata/conf/languages/POSIX.pm: Permission denied" error when running Build test.

Test fails at t/03.render.t "testdata/conf/languages/POSIX.pm: Permission denied" at .../t/testdata/TemplaceCopy.pm line 18

This occurs in my debian packaging. Could you check and tell me where the error was fixed so that I can check on my side?
For debian packaging, I needed to patch some install files, but it should not impact tests.

Discussion

  • Andrew Uzilov

    Andrew Uzilov - 2011-06-18

    Reassigning ticket, since I'm not a developer for this project.

     
  • Andrew Uzilov

    Andrew Uzilov - 2011-06-18
    • assigned_to: andrew_uzilov --> lstein
     
  • sallou

    sallou - 2011-06-19

    Hi,
    I found the issue in t/testdata/conf/languages/POSIX.pm which indeed has access rights to 444 instead of 644 for template rewrite.

    File in tar need to get correct access permissions.

     
  • Scott Cain

    Scott Cain - 2011-06-20
    • labels: 911574 --> Gbrowse
     
  • Scott Cain

    Scott Cain - 2011-06-20

    Hi,

    Can you please clarify what the problem is: do you mean that this test is still occurring in the 2.38 release, or do you want information about a historical release for the purposes of building/testing debian packages?

    Thanks,
    Scott

     
  • sallou

    sallou - 2011-06-20

    It occurs back in 2.38 release.

     
  • Scott Cain

    Scott Cain - 2011-06-20

    I don't understand why this is happening for you. I just got a fresh download of 2.38 (rather than using the current git pull, in case there was a difference), and on two different OS (MacOS X 10.5 and Ubuntu 11.04), these tests pass just fine. The permissions on conf/languages/* should be 444, though when the test copies it to the t directory, it copies it with 644, and that happens as expected. Perhaps it is something about your environment that is causing this to fail?

     

Log in to post a comment.