[LU-210] back out debian per-commit patching build process Created: 13/Apr/11  Updated: 19/Apr/11  Resolved: 19/Apr/11

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.1.0, Lustre 1.8.6
Fix Version/s: Lustre 2.1.0

Type: Bug Priority: Minor
Reporter: Brian Murrell (Inactive) Assignee: Robert Read (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 5067

 Description   

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.



 Comments   
Comment by Build Master (Inactive) [ 18/Apr/11 ]

Integrated in lustre-master-centos5 #203
LU-210 backout debian packaging with patches

Oleg Drokin : b8ab5a6bb291b760a2b6283089375a574ebe7113
Files :

  • debian/rules
  • autoMakefile.am
  • build/autoMakefile.am.toplevel
  • build/extract_patches
Comment by Build Master (Inactive) [ 18/Apr/11 ]

Integrated in lustre-master » client,ubuntu-x86_64 #29
LU-210 backout debian packaging with patches

Oleg Drokin : b8ab5a6bb291b760a2b6283089375a574ebe7113
Files :

  • autoMakefile.am
  • debian/rules
  • build/extract_patches
  • build/autoMakefile.am.toplevel
Comment by Build Master (Inactive) [ 18/Apr/11 ]

Integrated in lustre-master » client,el5-x86_64 #29
LU-210 backout debian packaging with patches

Oleg Drokin : b8ab5a6bb291b760a2b6283089375a574ebe7113
Files :

  • build/extract_patches
  • build/autoMakefile.am.toplevel
  • debian/rules
  • autoMakefile.am
Comment by Build Master (Inactive) [ 18/Apr/11 ]

Integrated in lustre-master » client,el5-i686 #29
LU-210 backout debian packaging with patches

Oleg Drokin : b8ab5a6bb291b760a2b6283089375a574ebe7113
Files :

  • autoMakefile.am
  • debian/rules
  • build/extract_patches
  • build/autoMakefile.am.toplevel
Comment by Build Master (Inactive) [ 18/Apr/11 ]

Integrated in lustre-master » server,el6-x86_64 #29
LU-210 backout debian packaging with patches

Oleg Drokin : b8ab5a6bb291b760a2b6283089375a574ebe7113
Files :

  • autoMakefile.am
  • build/extract_patches
  • build/autoMakefile.am.toplevel
  • debian/rules
Comment by Build Master (Inactive) [ 18/Apr/11 ]

Integrated in lustre-master » client,el6-i686 #29
LU-210 backout debian packaging with patches

Oleg Drokin : b8ab5a6bb291b760a2b6283089375a574ebe7113
Files :

  • autoMakefile.am
  • debian/rules
  • build/extract_patches
  • build/autoMakefile.am.toplevel
Comment by Build Master (Inactive) [ 18/Apr/11 ]

Integrated in lustre-master » server,el5-x86_64 #29
LU-210 backout debian packaging with patches

Oleg Drokin : b8ab5a6bb291b760a2b6283089375a574ebe7113
Files :

  • debian/rules
  • build/extract_patches
  • build/autoMakefile.am.toplevel
  • autoMakefile.am
Comment by Build Master (Inactive) [ 18/Apr/11 ]

Integrated in lustre-master » client,el6-x86_64 #29
LU-210 backout debian packaging with patches

Oleg Drokin : b8ab5a6bb291b760a2b6283089375a574ebe7113
Files :

  • build/autoMakefile.am.toplevel
  • build/extract_patches
  • debian/rules
  • autoMakefile.am
Comment by Build Master (Inactive) [ 18/Apr/11 ]

Integrated in lustre-master » server,el5-i686 #29
LU-210 backout debian packaging with patches

Oleg Drokin : b8ab5a6bb291b760a2b6283089375a574ebe7113
Files :

  • autoMakefile.am
  • build/extract_patches
  • build/autoMakefile.am.toplevel
  • debian/rules
Generated at Sat Feb 10 01:04:51 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.