Skip to content
Snippets Groups Projects
  1. May 15, 2018
  2. May 03, 2018
  3. Jun 03, 2017
  4. Dec 23, 2016
  5. Jan 06, 2016
  6. Sep 22, 2015
  7. Jun 09, 2015
  8. May 17, 2015
  9. May 01, 2015
  10. Apr 28, 2015
  11. Apr 09, 2015
  12. Mar 27, 2015
  13. Jan 27, 2015
  14. Jan 07, 2015
  15. Jul 24, 2014
  16. May 20, 2014
  17. Apr 24, 2014
  18. Mar 28, 2014
  19. Sep 12, 2013
  20. Apr 01, 2013
  21. Apr 18, 2011
    • Brian J. Murrell's avatar
      LU-210 backout debian packaging with patches · b8ab5a6b
      Brian J. Murrell authored
      
      The debian packaging process included the [de-]applicaiton of patches
      that were the commits made since the last tag.  This provided greater
      transparency as to exactly what was included in a release when it was
      made between tags.
      
      Unfortunately the process that was being used to achieve this failed
      in a scenario where there were patches to files which were later removed
      from the tarball making process.
      
      For what it's worth, the right way to correct this and keep the
      transparency is to have "make dist" create the tarball from the most
      recent tag made and then have the patches generated that bring the
      source up to current HEAD.  In order to achieve this however both debian
      and RPM packaging would need to operate in this manner.  That would
      mean adding Patch$n: lines to the RPM spec for each of the generated
      patches.  I'm not really sure we want to go there though.
      
      Signed-off-by: default avatarBrian J. Murrell <brian@whamcloud.com>
      Change-Id: I9242799f3987e68e806e4c398e06cecbe1f5cc27
      Reviewed-on: http://review.whamcloud.com/425
      
      
      Tested-by: Hudson
      Reviewed-by: default avatarOleg Drokin <green@whamcloud.com>
      Reviewed-by: default avatarMichael MacDonald <mjmac@whamcloud.com>
      b8ab5a6b
  22. Apr 08, 2011
  23. Mar 10, 2011
  24. Mar 04, 2011
  25. Feb 10, 2011
    • Brian J. Murrell's avatar
      b=24416 debian packaging fixes · b6355015
      Brian J. Murrell authored
      - don't make a patch out of anything in /debian
      - exclude noise files from the debian built source tarball
      - fake debian/patche{s,d} for make dist
      - a few more reasons to run autogen.sh
      - figure out if dist tarball needs autogen.shs and include it if so
      - look for and run autogen.sh in the build subdir
      - make debdiff as part of make dist
      - add a debian/source/format file
      - mv the orig tarball and the debdiff to the debs dir
      - don't try to dist /debian for non-dpkg-using build targets
      
      Issue: LU-51
      Change-Id: I041aaef217e107def86ce808d0e96fc6891e1dcd
      b6355015
  26. Oct 18, 2010
  27. Jun 18, 2010
  28. Jun 11, 2010
  29. Mar 30, 2010
  30. Dec 12, 2009
    • Brian Reitz's avatar
      Introduce .gitignore files. · 1c4d3d36
      Brian Reitz authored
      The top level .gitignore file is new and is an attempt at
      pulling in some of the common items that you might get for
      free (by default)with CVS.  The other subdir/.gitignore files
      are translated versions of their corresponding .cvsignore
      file.  Because CVS does not descend into a subdir when
      applying a ingore rule we have to prepend a "/" to
      the pathname to get git to behave the same way.
  31. Dec 03, 2009
  32. Dec 02, 2009
    • Brian J. Murrell's avatar
      b=20315 · 92d6bc75
      Brian J. Murrell authored
      i=adilger
      o=Christopher Morrone
      
      Use the more standard libexecdir for scripts.
      92d6bc75
  33. Nov 27, 2009
    • Brian J. Murrell's avatar
      b=19721 · 96e8fbb5
      Brian J. Murrell authored
      i=adilger
      
      Try to be somewhat intelligent about the need to autogen.sh or not by
      seeing if any of the patches touch an autoconf file.
      96e8fbb5
  34. Nov 12, 2009
    • Brian J. Murrell's avatar
      b=19721 · 89045eb8
      Brian J. Murrell authored
      i=brian
      o=adilger
      
      A "debs" make target so that one simply has to do "make debs" in a configured
      source tree to get both userspace and kernel modules debian packages.
      - this includes automatically updating the debian/changelog if not up-to-date
        with respect to the current version of lustre
      - I'm not convinced that all of the gyrations to use m-a to build the kernel
        modules is worth it and if there are any non-trivial problems found with it
        I might just rip it all out and have debian/rules build and package up the
        kernel modules package
      Some cleanups:
      - fix automake requirement so that it's much more flexible
      - allow both Ubuntu and Debian headers packages to be required
      - comment out the body of the autogen-stamp
        + if somebody adds a patch to debian/patches that requires an
          autogen, they can supply a patch to create the autogen.sh and
          uncommment the autogen-stamp body
          * this is ideally and hopefull a very rare event
          * we would love feedback from packages that find creating patches necessary
      - workaround in version_tag.pl for some (Debian?) systems where, for whatever
        reason, MODULES_{TRUE|FALSE} does not get included in the {auto,}Makefile.in
        files
      89045eb8
  35. Nov 10, 2009
  36. Aug 19, 2009
    • Brian J. Murrell's avatar
      b=19721 · 53eb1332
      Brian J. Murrell authored
      i=adilger
      
      Add a debian/ dir to allow building on Debian/Ubuntu systems.  The process
      is basically (from the top-level) lustre dir:
      $ dpkg-buildpackage
      $ sudo m-a build ../lustre-source_1.8.1-1_all.deb
      
      The above needs to be captured in a "make debs" Makefile target so that it
      works like the "make rpms" target, including building lustre packages as
      well as a binary kernel modules package.  This will be the next step in this
      enhancement.
      
      All of this has really only been tested to build the patchless client with
      Ubuntu's 2.6.24-19-generic kernel at this point.  However the bits necessary
      to build a patched server kernel are included, even if they need to be tested
      and perhaps tweaked for supported kernels.  At least theoretically, it should
      work for newer kernels even.
      53eb1332
Loading