Skip to content
Snippets Groups Projects

Split distributions to ease readability

Merged Split distributions to ease readability
deprecate_slc5 into master
Merged Ghost User requested to merge deprecate_slc5 into master
Compare
and
4 files
+ 203
− 1
Compare changes
  • Side-by-side
  • Inline
Files
4
docs/distributions/index.md → docs/distributions/cc7.md
+ 75
− 0
# Distributions
# CERN CentOS 7
## Scientific Linux CERN 5
### Pratical info
Upstream support : EOL-ed on 2019-04-01
### Building updates
These directories allow an administrator to rebuild packages provided by Red Hat and new CERN packages.
| Incoming |
| -- |
| /mnt/data2/home/build/packages/incoming/slc5/updates |
| /mnt/data2/home/build/packages/incoming/slc5/extras |
| /mnt/data2/home/build/packages/incoming/slc5/cernonly |
| /mnt/data2/home/build/packages/incoming/slc5/mrg |
> Notes:
> * Source or binary package can be added to incoming. Only commercial packages are generally added.
|Build|
| -- |
|/mnt/data2/home/build/bin/bsbuild -d "slc5" -r "updates extras cernonly mrg"|
|/mnt/data2/home/build/bin/bsdownload -s -d "slc5" -r "updates extras cernonly mrg"|
> Notes:
>* Grab the signing pass phrase in tbag :
```
tbag show distribution_signing_key_passphrase --hg linuxsupport/lxsoft
```
|If New kernel package : e.g kernel-**2.6.XXX.elX**, please build associated modules| |
| -- | -- |
| bsbuildmodules -d slc5 -k **2.6.XXX.elX** | build with mock new modules |
| bscopymodules -d slc5 -k **2.6.XXX.elX** | copy modules in the build area|
> Notes:
> * You need then to follow "Release to testing" procedure.
|Release to testing||
| -- | -- |
| /mnt/data2/home/build/bin/bsbuild2test -d slc5 -r "testing" | Move all built packages to testing|
| /mnt/data2/home/build/bin/bsregenrepos -d slc5 -r "testing mrg-testing" | Regenerate testing repositories metadata |
| /mnt/data2/home/build/bin/bssync -t "data1 eos" -d slc5 -r "testing mrg-testing" |sync /mnt/data2 -> /mnt/data1 |
| /mnt/data2/home/build/bin/bsmailusers -d slc5 -r testing -e -s -w | Email linux-announce-test@cern.ch with updated packages|
> Notes:
> * $EDITOR must be set to your prefered editor to edit the email
|Release to production||
| -- | -- |
| /mnt/data2/home/build/bin/bstest2prod -d slc5 -r "updates mrg" | List available updates |
| /mnt/data2/home/build/bin/bstest2prod -d slc5 -r "updates mrg" [pkgname to release] | Promote package. \\* can be used to promote all updates. A careful review is needed in general. |
|/mnt/data2/home/build/bin/bsregenrepos -d slc5 -r "testing mrg-testing cernonly extras updates mrg"| Regenerate production repositories metadata (=~ 30min) |
|/mnt/data2/home/build/bin/bssync -t "data1 eos" -d slc5 -r "testing mrg-testing cernonly extras updates mrg" | sync /mnt/data2 -> /mnt/data1|
| /mnt/data2/home/build/bin/bsmailusers -d slc5 -r updates -e -s -w | Email linux-announce@cern.ch with updated packages|
|Update web pages||
| -- | -- |
| vi /afs/cern.ch/project/linux/wwwtest/freshnews.shtml | Edit the web pages, section can be copied from previous week. Previous sent Email subject is used as a title. Dates need to be updated. (need better automation) |
| /afs/cern.ch/project/linux/adm/bin/wwwtest2prod | sync web page to production site.|
## Scientific Linux CERN 6
### Practical info
Upstream support : until 2020-12-01
### Building updates
These directories allow administrator to rebuild packages provided by Red Hat and new/updated CERN packages.
| Incoming |
| -- |
| /mnt/data2/home/build/packages/incoming/slc6/updates |
| /mnt/data2/home/build/packages/incoming/slc6/extras |
| /mnt/data2/home/build/packages/incoming/slc6/cernonly |
| /mnt/data2/home/build/packages/incoming/slc6/mrg |
> Notes:
> * Source or binary package can be added to incoming.
|Build|
| -- |
|/mnt/data2/home/build/bin/bsbuild -d "slc6" -r "updates extras cernonly mrg"|
|/mnt/data2/home/build/bin/bsdownload -s -d "slc6" -r "updates extras cernonly mrg"|
> Notes:
>* Grab the signing pass phrase in tbag :
```
tbag show distribution_signing_key_passphrase --hg linuxsupport/lxsoft
```
|If New kernel package : e.g kernel-**2.6.XXX.elX**, please build associated modules| |
| -- | -- |
| bsbuildmodules -d slc6 -k **2.6.XXX.elX** | build with mock new modules |
| bscopymodules -d slc6-k **2.6.XXX.elX** | copy modules in the build area|
> Notes:
> * You need then to follow "Release to testing" procedure.
|Release to testing||
| -- | -- |
| /mnt/data2/home/build/bin/bsbuild2test -d slc6 -r "testing" | Move all built packages to testing|
| /mnt/data2/home/build/bin/bsregenrepos -d slc6 -r "testing mrg-testing" | Regenerate testing repositories metadata |
| /mnt/data2/home/build/bin/bssync -t "data1 eos" -d slc6 -r "testing mrg-testing" |sync /mnt/data2 -> /mnt/data1 |
| /mnt/data2/home/build/bin/bsmailusers -d slc6 -r testing -e -s -w | Email linux-announce-test@cern.ch with updated packages|
> Notes:
> * $EDITOR must be set to your prefered editor to edit the email
|Release to production||
| -- | -- |
| /mnt/data2/home/build/bin/bstest2prod -d slc6 -r "updates mrg" | List available updates |
| /mnt/data2/home/build/bin/bstest2prod -d slc6 -r "updates mrg" [pkgname to release] | Promote package. \\* can be used to promote all updates. A careful review is needed in general. |
|/mnt/data2/home/build/bin/bsregenrepos -d slc6 -r "testing mrg-testing cernonly extras updates mrg"| Regenerate production repositories metadata (=~ 30min) |
|/mnt/data2/home/build/bin/bssync -t "data1 eos" -d slc6 -r "testing mrg-testing cernonly extras updates mrg" | sync /mnt/data2 -> /mnt/data1|
| /mnt/data2/home/build/bin/bsmailusers -d slc6 -r updates -e -s -w | Email linux-announce@cern.ch with updated packages|
|Update web pages||
| -- | -- |
| vi /afs/cern.ch/project/linux/wwwtest/freshnews.shtml | Edit the web pages, section can be copied from previous week. Previous sent Email subject is used as a title. Dates need to be updated. (need better automation) |
| /afs/cern.ch/project/linux/adm/bin/wwwtest2prod | sync web page to production site.|
## CERN CentOS 7
### Practical info
## Practical info
Upstream support : until 2023-12-01
### Pushing upstream updates
## Pushing upstream updates
As we do not rebuild upstream packages (except nss) we just sync it from our [local mirror](https://linuxsoft.cern.ch/centos/)
@@ -151,7 +23,8 @@ As we do not rebuild upstream packages (except nss) we just sync it from our [lo
> Notes:
> * You need then to follow "Release to testing" procedure as modules are added to the `cern` repository.
### Building internal updates
## Building internal updates
These directories allow administrator to rebuild packages provided by Red Hat and new CERN packages.
| Incoming |
@@ -172,11 +45,11 @@ These directories allow administrator to rebuild packages provided by Red Hat an
|/mnt/data2/home/build/bin/bsdownload -s -d "cc7" -r "all"|
> Notes:
>* Grab the signing pass phrase in tbag :
>* Grab the signing pass phrase in tbag :
```
tbag show distribution_signing_key_passphrase --hg linuxsupport/lxsoft
```
### Release to testing
## Release to testing
|Release to testing||
| -- | -- |
@@ -190,7 +63,7 @@ tbag show distribution_signing_key_passphrase --hg linuxsupport/lxsoft
|Release to production||
| -- | -- |
| /mnt/data2/home/build/bin/bstest2prod -d cc7 -r "updates mrg" | List available updates |
| /mnt/data2/home/build/bin/bstest2prod -d cc7 -r "updates mrg" | List available updates |
| /mnt/data2/home/build/bin/bstest2prod -d cc7 -r "updates mrg" [pkgname to release] | Promote package. \\* can be used to promote all updates. A careful review is needed in general. |
|/mnt/data2/home/build/bin/bsregenrepos -d cc7 -r "cern-testing cernonly-testing rt-testing centosplus-testing rhcommon-testing cern cernonly rt centosplus rhcommon"| Regenerate production repositories metadata (=~ 15min) |
|/mnt/data2/home/build/bin/bssync -t "data1 eos" -d cc7 -r "cern-testing cernonly-testing rt-testing centosplus-testing rhcommon-testing cern cernonly rt centosplus rhcommon" | sync /mnt/data2 -> /mnt/data1|