Build The Manifest - Revision history

Paul Blankenbaker at 15:56, 24 August 2018

2018-08-24T15:56:31Z

← Older revision		Revision as of 11:56, 24 August 2018
Line 25:		Line 25:
	[nst@nst24-repo repo]$ grep '%' include/manifest/current.xml		[nst@nst24-repo repo]$ grep '%' include/manifest/current.xml
	[nst@nst24-repo repo]$ grep '\\' include/manifest/current.xml		[nst@nst24-repo repo]$ grep '\\' include/manifest/current.xml
	[nst@nst24-repo repo]$ sed -i -e 's,\\,,g' -e 's,%2B,+,' include/manifest/current.xml # Example of removing back-slashes and changing %2B to +		[nst@nst24-repo repo]$ sed -i -e 's,\\,,g' -e 's,%2B,+,' -e 's,%{git,{git,' include/manifest/current.xml # Example of removing back-slashes and changing %2B to +
	[nst@nst24-repo repo]$ xmllint include/manifest/current.xml > /dev/null		[nst@nst24-repo repo]$ xmllint include/manifest/current.xml > /dev/null
	[nst@nst24-repo repo]$ svn info		[nst@nst24-repo repo]$ svn info

Paul Blankenbaker at 10:02, 6 October 2017

2017-10-06T10:02:25Z

← Older revision		Revision as of 06:02, 6 October 2017
Line 25:		Line 25:
	[nst@nst24-repo repo]$ grep '%' include/manifest/current.xml		[nst@nst24-repo repo]$ grep '%' include/manifest/current.xml
	[nst@nst24-repo repo]$ grep '\\' include/manifest/current.xml		[nst@nst24-repo repo]$ grep '\\' include/manifest/current.xml
	[nst@nst24-repo repo]$ sed -i -e 's,\\,,g' include/manifest/current.xml # Example of removing back-slashes		[nst@nst24-repo repo]$ sed -i -e 's,\\,,g' -e 's,%2B,+,' include/manifest/current.xml # Example of removing back-slashes and changing %2B to +
	[nst@nst24-repo repo]$ xmllint include/manifest/current.xml > /dev/null		[nst@nst24-repo repo]$ xmllint include/manifest/current.xml > /dev/null
	[nst@nst24-repo repo]$ svn info		[nst@nst24-repo repo]$ svn info

Paul Blankenbaker at 19:40, 3 July 2016

2016-07-03T19:40:53Z

← Older revision		Revision as of 15:40, 3 July 2016
Line 3:		Line 3:
	* Use the ''make manifest HOST=IP'' to generate the current manifest.		* Use the ''make manifest HOST=IP'' to generate the current manifest.

	* You may need to ''edit'' the current release file: "'''include/manifest/current.xml'''" prior to copying it for misbehaved characters. Hopefully the ''xmllint'' and ''grep'' searches for the ''%'' and "\" characters will detect any issues.		* You may need to ''edit'' the current release file: "'''include/manifest/current.xml'''" prior to copying it for misbehaved characters. Hopefully the ''xmllint'' and ''grep'' searches for the ''%'' and "\" characters will detect any issues. '''IMPORTANT''': You will need to remove/replace the "%" characters by hand (if any are found). The back slashes can be handled by ''sed'' (shown below).

	* Create the file ''include/manifest/release-RELEASE-SVNID.xml'' where ''RELEASE'' is the NST release (like: 24) and ''SVNID'' is ''one more'' than the current revision number reported by Subversion (since our next commit will cause this number to bump up by 1). For example, if the revision number reported is 7972, then use 7973 as the ''SVNID''.		* Create the file ''include/manifest/release-RELEASE-SVNID.xml'' where ''RELEASE'' is the NST release (like: 24) and ''SVNID'' is ''one more'' than the current revision number reported by Subversion (since our next commit will cause this number to bump up by 1). For example, if the revision number reported is 7972, then use 7973 as the ''SVNID''.

Paul Blankenbaker at 19:28, 3 July 2016

2016-07-03T19:28:45Z

← Older revision		Revision as of 15:28, 3 July 2016
Line 41:		Line 41:
	Last Changed Date: 2016-07-03 07:32:53 -0400 (Sun, 03 Jul 2016)		Last Changed Date: 2016-07-03 07:32:53 -0400 (Sun, 03 Jul 2016)

			[nst@nst24-repo repo]$ emacs -nw include/manifest/current.xml # Check/update kernel and SVN numbers
	[nst@nst24-repo repo]$ cp include/manifest/current.xml include/manifest/release-24-7973.xml		[nst@nst24-repo repo]$ cp include/manifest/current.xml include/manifest/release-24-7973.xml
	[nst@nst24-repo repo]$ svn add include/manifest/release-24-7973.xml		[nst@nst24-repo repo]$ svn add include/manifest/release-24-7973.xml

Paul Blankenbaker at 16:33, 3 July 2016

2016-07-03T16:33:53Z

← Older revision		Revision as of 12:33, 3 July 2016
Line 10:		Line 10:

	* You will likely need to update the ''html/welcome.html'' page with the next '''SVN revision number'''. Also check '''kernel versions''', '''dates''' and the '''manifest link'''.		* You will likely need to update the ''html/welcome.html'' page with the next '''SVN revision number'''. Also check '''kernel versions''', '''dates''' and the '''manifest link'''.

			* Probe install the nstweb package and verify that the welcome page and manifest look OK (ie the kernel and top level info).

	* Commit the updated manifest file.		* Commit the updated manifest file.

Paul Blankenbaker at 12:46, 3 July 2016

2016-07-03T12:46:43Z

← Older revision		Revision as of 08:46, 3 July 2016
Line 5:		Line 5:
	* You may need to ''edit'' the current release file: "'''include/manifest/current.xml'''" prior to copying it for misbehaved characters. Hopefully the ''xmllint'' and ''grep'' searches for the ''%'' and "\" characters will detect any issues.		* You may need to ''edit'' the current release file: "'''include/manifest/current.xml'''" prior to copying it for misbehaved characters. Hopefully the ''xmllint'' and ''grep'' searches for the ''%'' and "\" characters will detect any issues.

	* Create the file ''include/manifest/release-RELEASE-SVNID.xml'' where ''RELEASE'' is the NST release (like: 20) and ''SVNID'' is ''one more'' than the current revision number reported by Subversion (since our next commit will cause this number to bump up by 1). For example, if the revision number reported is ~~2511~~, then use ~~2512~~ as the ''SVNID''.		* Create the file ''include/manifest/release-RELEASE-SVNID.xml'' where ''RELEASE'' is the NST release (like: 24) and ''SVNID'' is ''one more'' than the current revision number reported by Subversion (since our next commit will cause this number to bump up by 1). For example, if the revision number reported is 7972, then use 7973 as the ''SVNID''.

	* You only need to update the manifest on ~~the 32 bit development machine. On the 64 bit~~ machine you ~~will just run~~ '~~'svn~~ update~~'' to get the newly committed manifest~~.		* You only need to update the manifest on one machine (if you are building multiple architectures, you'll need to update).

	* You will likely need to update the ''html/welcome.html'' page with the next '''SVN revision number'''. Also check '''kernel versions''', '''dates''' and the '''manifest link'''.		* You will likely need to update the ''html/welcome.html'' page with the next '''SVN revision number'''. Also check '''kernel versions''', '''dates''' and the '''manifest link'''.
Line 15:		Line 15:
	Here is an example of what these steps might look like:		Here is an example of what these steps might look like:

	[~~root~~@~~dev18~~-32 repo]# make manifest HOST=nst-probe		[nst@nst24-repo repo]$ make manifest HOST=nst-probe

	... Output and re-generation of:		... Output and re-generation of:
	include/manifest/current.xml ...		include/manifest/current.xml ...

	[~~root~~@~~dev18~~-32 repo]# xmllint include/manifest/current.xml > /dev/null		[nst@nst24-repo repo]$ xmllint include/manifest/current.xml > /dev/null
	[~~root~~@~~dev18~~-32 repo]# grep '%' include/manifest/current.xml		[nst@nst24-repo repo]$ grep '%' include/manifest/current.xml
	[~~root~~@~~dev18~~-32 repo]# grep '\\' include/manifest/current.xml		[nst@nst24-repo repo]$ grep '\\' include/manifest/current.xml
	[~~root~~@~~dev18~~-32 repo]# sed -i -e 's,\\,,g' include/manifest/current.xml # Example of removing back-slashes		[nst@nst24-repo repo]$ sed -i -e 's,\\,,g' include/manifest/current.xml # Example of removing back-slashes
	[~~root~~@~~dev18~~-32 repo]# xmllint include/manifest/current.xml > /dev/null		[nst@nst24-repo repo]$ xmllint include/manifest/current.xml > /dev/null
	[~~root~~@~~dev18~~-32 repo]# svn info		[nst@nst24-repo repo]$ svn info
	Path: .		Path: .
	Working Copy Root Path: /~~root~~/repo		Working Copy Root Path: /home/nst/repo
	URL: https://svn.code.sf.net/p/nst/code/repo		URL: https://svn.code.sf.net/p/nst/code/repo/24
			Relative URL: ^/repo/24
	Repository Root: https://svn.code.sf.net/p/nst/code		Repository Root: https://svn.code.sf.net/p/nst/code
	Repository UUID: b5e161f0-cc72-4f2a-9017-da5bd5071a9c		Repository UUID: b5e161f0-cc72-4f2a-9017-da5bd5071a9c
	Revision: ~~4504~~		Revision: 7972
	Node Kind: directory		Node Kind: directory
	Schedule: normal		Schedule: normal
	Last Changed Author: ~~rwhalb~~		Last Changed Author: pblankenbaker
	Last Changed Rev: ~~4504~~		Last Changed Rev: 7972
	Last Changed Date: ~~2013~~-04-~~12 15~~:13:52 -0400 (~~Fri~~, ~~12 Apr 2013~~)		Last Changed Date: 2016-07-03 07:32:53 -0400 (Sun, 03 Jul 2016)

	[~~root~~@~~dev18~~-32 repo]# cp include/manifest/current.xml include/manifest/release-18-~~4505~~.xml		[nst@nst24-repo repo]$ cp include/manifest/current.xml include/manifest/release-24-7973.xml
	[~~root~~@~~dev18~~-32 repo]# svn add include/manifest/release-18-~~4505~~.xml		[nst@nst24-repo repo]$ svn add include/manifest/release-24-7973.xml
	[~~root~~@~~dev18~~-32 repo]# emacs -nw html/welcome.html # Look for and update SVN number to match ~~4505~~ above		[nst@nst24-repo repo]$ emacs -nw html/welcome.html # Look for and update SVN number to match 7973 above
	[~~root~~@~~dev18~~-32 repo]# svn commit -m "Updated manifest for upcoming release"		[nst@nst24-repo repo]$ svn commit -m "Updated manifest for upcoming release"

	... Output from the commit ...		... Output from the commit ...

	[~~root~~@~~dev18~~-32 repo]#		[nst@nst24-repo repo]$

Paul Blankenbaker at 18:21, 9 February 2015

2015-02-09T18:21:16Z

← Older revision		Revision as of 14:21, 9 February 2015
Line 9:		Line 9:
	* You only need to update the manifest on the 32 bit development machine. On the 64 bit machine you will just run ''svn update'' to get the newly committed manifest.		* You only need to update the manifest on the 32 bit development machine. On the 64 bit machine you will just run ''svn update'' to get the newly committed manifest.

	* You will likely need to update the ''html/welcome.html'' page with the next SVN revision number. Also check kernel versions, dates and the manifest link.		* You will likely need to update the ''html/welcome.html'' page with the next '''SVN revision number'''. Also check '''kernel versions''', '''dates''' and the '''manifest link'''.

	* Commit the updated manifest file.		* Commit the updated manifest file.

Paul Blankenbaker at 16:31, 20 February 2014

2014-02-20T16:31:30Z

@@ Line 12: / Line 12: @@
 * Commit the updated manifest file.
 Here is an example of what these steps might look like:
@@ Line 47: / Line 45: @@
   ... Output from the commit ...
-  [root@dev18-32 repo]# make -C yum nstwui-remove nstweb-remove nstmenu-remove
+  [root@dev18-32 repo]#

Paul Blankenbaker at 15:58, 20 February 2014

2014-02-20T15:58:10Z

← Older revision		Revision as of 11:58, 20 February 2014
Line 13:		Line 13:
	* Commit the updated manifest file.		* Commit the updated manifest file.

	* Force the ''nstwui'', ''nstmenu'' and ''nstweb'' packages to be rebuilt.		* Force the ''nstwui'', ''nstmenu'' and ''nstweb'' packages to be rebuilt and clear the delta RPMs.

	Here is an example of what these steps might look like:		Here is an example of what these steps might look like:
Line 51:		Line 51:
	... This remove will force them to be rebuilt ...		... This remove will force them to be rebuilt ...

	[root@dev18-32 repo]#		[root@dev18-32 repo]# cd yum
			[root@dev18-32 yum]# make repo-prune repo-prune-delta

			... Lots of output as old RPMs are removed ...

			[root@dev18-32 yum]# \rm -r repo/drpms/*
			[root@dev18-32 yum]#

	Run the following on the 64 bit machine:		Run the following on the 64 bit machine:

	[root@dev18-64 repo]# make -C yum nstwui-remove nstweb-remove nstmenu-remove		[root@dev18-64 repo]# make -C yum nstwui-remove nstweb-remove nstmenu-remove

			[root@dev18-64 repo]# cd yum
			[root@dev18-64 yum]# make repo-prune repo-prune-delta

			... Lots of output as old RPMs are removed ...

			[root@dev18-64 yum]# \rm -r repo/drpms/*
			[root@dev18-64 yum]#

Paul Blankenbaker at 15:46, 20 February 2014

2014-02-20T15:46:56Z

← Older revision		Revision as of 11:46, 20 February 2014
Line 2:		Line 2:

	* Use the ''make manifest HOST=IP'' to generate the current manifest.		* Use the ''make manifest HOST=IP'' to generate the current manifest.

			* You may need to ''edit'' the current release file: "'''include/manifest/current.xml'''" prior to copying it for misbehaved characters. Hopefully the ''xmllint'' and ''grep'' searches for the ''%'' and "\" characters will detect any issues.

	* Create the file ''include/manifest/release-RELEASE-SVNID.xml'' where ''RELEASE'' is the NST release (like: 20) and ''SVNID'' is ''one more'' than the current revision number reported by Subversion (since our next commit will cause this number to bump up by 1). For example, if the revision number reported is 2511, then use 2512 as the ''SVNID''.		* Create the file ''include/manifest/release-RELEASE-SVNID.xml'' where ''RELEASE'' is the NST release (like: 20) and ''SVNID'' is ''one more'' than the current revision number reported by Subversion (since our next commit will cause this number to bump up by 1). For example, if the revision number reported is 2511, then use 2512 as the ''SVNID''.

			* You only need to update the manifest on the 32 bit development machine. On the 64 bit machine you will just run ''svn update'' to get the newly committed manifest.

			* You will likely need to update the ''html/welcome.html'' page with the next SVN revision number. Also check kernel versions, dates and the manifest link.

	* Commit the updated manifest file.		* Commit the updated manifest file.
Line 47:		Line 53:
	[root@dev18-32 repo]#		[root@dev18-32 repo]#

	'''***Note1:''' One may need to ''edit'' the current release file: "'''include/manifest/current.xml'''" prior to copying it for misbehaved characters. Hopefully the ''xmllint'' and ''grep'' searches for the ''%'' and "\" characters will detect any issues.		Run the following on the 64 bit machine:

	~~'''***Note2:''' You will likely need to update the ''html/welcome.html'' page with the next SVN revision number (''4505'' in this example).~~

	'''***Note3:''' You only need to update the manifest on the 32 bit development machine. On the 64 bit machine you will just run ''svn update'' to get the newly committed manifest. Also, it won't hurt to run the following on the 64 bit machine:

	[root@dev18-64 repo]# make -C yum nstwui-remove nstweb-remove nstmenu-remove		[root@dev18-64 repo]# make -C yum nstwui-remove nstweb-remove nstmenu-remove