作者：张华 发表于：2021-08-18
版权声明：可以任意转载，转载时请务必以超链接形式标明文章原始出处和作者信息及本版权声明
问题
在ussuri (16.3.0)里有一个bug, 但在steain(15.3.4)里没有，需要二分，先通过’git tag’找到其中的16.0.0, 16.1.0, 16.3.0三个tag
15.3.4
16.0.0 https://launchpad.net/ubuntu/+source/neutron/2:16.0.0-0ubuntu2
16.0.0.0b1
16.0.0.0rc1
16.0.0.0rc2
16.1.0 https://launchpad.net/ubuntu/+source/neutron/2:16.1.0-0ubuntu2
16.2.0 https://launchpad.net/ubuntu/+source/neutron/2:16.2.0-0ubuntu2
16.3.0
前一篇关于debian的文章是： https://blog.csdn.net/quqi99/article/details/50511173
一些感受:
- 在bionic中运行git-buildpackage的pristine-tar checkout这步会报一个XD3_INVALID_INPUT错误，在focal上无此问题
- 在focal上运行git-buildpackage + git-pbuiler(cowpbuilder)时会报一个dbus相关的错误。运行git-buildpackage + sbuild或git-buildpackage + debuild都无此问题。直接运行pdebuild也无此问题(git-pbuilder用的是cowpbuilder是cow格式) .git-pbuilder创建出来的镜像里没有dbus包和环境变量（DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus），暂不清楚是否和这相关. 后来，使用git-pubilder时又提示输入什么密码。看来git-pbuilder确实有问题不能用.
- git-buildpackage从git源码编译时都要用到tarball，但tarball有通过prinstine-tar命令人工准备和它从neutron git源码中自动tarball两种方式
- 使用git-buildpackage + sbuild即可
- 源码包看debian/changelog就能确实是适合在bionic上还是bionic-steain上还是focal上编译，这样能避免包依赖问题
准备测试机器
juju deploy ubuntu debbuild --series=bionic --config hostname=debbuild --constraints "mem=8G cores=2 root-disk=80G"
# juju add-machine --series bionic
sudo cp /etc/apt/sources.list /etc/apt/sources.list_bak
cat <<EOF | sudo tee /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu bionic-security main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse
#deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu bionic-security main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
#deb-src http://archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse
#deb-src http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
EOF
sudo apt clean && sudo apt update
使用pbuilder
会报一些包依赖的错（openstack-pkg-tools (>= 85ubuntu3~) , 20241021更新：原因是sources.list里只用了main slot没用updates slot），见最后，后来证明和pbuilder无关，是该dsc文件就不是针对bionic的所以一堆问题。
sudo apt install pbuilder debootstrap devscripts -y
sudo apt install gnupg ubuntu-dev-tools bzr-builddeb apt-file debhelper dh-systemd openstack-pkg-tools -y
sudo apt install build-essential quilt dh-autoreconf fakeroot dpkg-dev python-sphinx dh-make -y
#sudo apt install apt-cacher-ng -y
#echo 'Acquire::http::Proxy "http://127.0.0.1:3142";' | sudo tee /etc/apt/apt.conf.d/01acng
# sometimes base.tgz can't be generated when using pbuilderrc
sudo pbuilder --create --distribution bionic --architecture amd64 --debootstrapopts --variant=buildd
sudo cp /var/cache/pbuilder/base.tgz /var/cache/pbuilder/bionic-train-base.tgz
# need to use '--basetgz' when using no pbuilderrc
sudo pbuilder update --basetgz /var/cache/pbuilder/bionic-train-base.tgz
#chroot to image to ajust what you want
sudo pbuilder login --save-after-login --basetgz /var/cache/pbuilder/bionic-train-base.tgz
echo 'precedence ::ffff:0:0/96 100' >> /etc/gai.conf
apt install software-properties-common dirmngr vim ca-certificates ubuntu-cloud-keyring apt-transport-https -y
add-apt-repository cloud-archive:train
#deb http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/train main
#apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5EDB1B62EC4926EA
sed -i -e "s/# deb-src/deb-src/" /etc/apt/sources.list.d/cloudarchive-train.list
apt update
# then exit chroot, press ctrl-d to save
# but pdebuild needs pbuilderrc
cat <<EOF | sudo tee /etc/pbuilderrc
MIRRORSITE=http://archive.ubuntu.com/ubuntu/
DEBFULLNAME='Zhang Hua'
DEBEMAIL='xxx@xxx.com'
DISTRIBUTION='bionic'
EXTRAPACKAGES=''
#EXTRAPACKAGES+=' vim sudo bash-completion wget git build-essential apt-transport-https ca-certificates ubuntu-cloud-keyring'
# Cloud Archive
#OS_RELEASE='train'
if [ -n "\$OS_RELEASE" ]; then
BASETGZ="/var/cache/pbuilder/\$DISTRIBUTION-\$OS_RELEASE-base.tgz"
else
BASETGZ="/var/cache/pbuilder/\$DISTRIBUTION-base.tgz"
fi
EOF
mkdir -p /bak/work/debian/neutron/16.1.0 && cd /bak/work/debian/neutron/16.1.0
dget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/neutron/2:16.1.0-0ubuntu2/neutron_16.1.0-0ubuntu2.dsc
dpkg-source -x neutron_16.1.0-0ubuntu2.dsc
cd /bak/work/debian/neutron/16.1.0/neutron-16.1.0
# install dependency, use mk-build-deps instead of 'apt build-dep neutron'
add-apt-repository cloud-archive:train #also add uca
sudo apt install devscripts equivs -y
sudo mk-build-deps --install debian/control
# dpkg-source: error: aborting due to unexpected upstream changes
rm -rf debian/source/fomat
sudo pdebuild --debug
#sudo pdebuild --debbuildopts -sa #when hitting 'Unable to find xxx.orig.tar.gz in upload or distribution'
#DEB_BUILD_OPTIONS=nocheck debuild -us -uc
报这个错：
ubuntu@debbuild:/bak/work/debian/neutron/16.1.0/neutron-16.1.0$ sudo pdebuild
W: /home/ubuntu/.pbuilderrc does not exist
dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper-compat (= 12) openstack-pkg-tools (>= 85ubuntu3~) python3-pbr (>= 4.0.0)
W: Unmet build-dependency in source
dpkg-source: info: using options from neutron-16.1.0/debian/source/options: --extend-diff-ignore=^[^/]*[.]egg-info/
pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
debian/rules:42: warning: overriding recipe for target 'override_dh_installinit'
/usr/share/openstack-pkg-tools/pkgos.make:43: warning: ignoring old recipe for target 'override_dh_installinit'
dh clean --with python3 --buildsystem=pybuild
dh: Compatibility levels before 5 are no longer supported (level 1 requested)
debian/rules:17: recipe for target 'clean' failed
make: *** [clean] Error 25
原因是运行pbuilder的机器上也得添加train uca并安装(pbuilder镜像里也记得添加train uca哦)，也别记了将pbuilderrc中的RELEASE放开来构建正确的BASETGZ变量：
apt install debhelper-compat openstack-pkg-tools python3-pbr -y
但是接着会报下列错，这是debian包的问题，因为我们编译的neutron-16.1.0是位于train和ussuri之间的版本，并不是严格的train (train中的debain/control中的确实是python3-neutron-lib (>= 1.29.1),)
pbuilder-satisfydepends-dummy : Depends: python3-neutron-lib (>= 2.2.0) but 1.29.1-0ubuntu1~cloud0 is to be installed
Depends: python3-ovsdbapp (>= 1.0.0) but 0.17.0-0ubuntu1~cloud0 is to be installed
Depends: python3-pyroute2 (>= 0.5.7) but 0.5.6-0ubuntu1~cloud0 is to be installed
python3-cryptography : Depends: libssl1.1 (>= 1.1.1) but 1.1.0g-2ubuntu4 is installed
后来又这样：
sudo mv /etc/pbuilderrc /tmp/
sudo pbuilder --create --distribution focal --architecture amd64 --debootstrapopts --variant=buildd
sudo mv /tmp/pbuilderrc /etc/
sudo cp /var/cache/pbuilder/base.tgz /var/cache/pbuilder/focal-base.tgz
sudo pbuilder --login --basetgz /var/cache/pbuilder/focal-base.tgz --save-after-login
#/etc/pbuilderrc will point out 'BASETGZ='
gbp buildpackage --git-pbuilder --git-dist=focal --git-arch=amd64 --git-ignore-branch --git-ignore-new -uc -us -j8
结果又提示输出密码：
[sudo] password for pbuilder:
看来gbp与pbuilder结合这一块确实有问题
使用sbuild
最后遇到错误”Not removing build depends: cloned chroot in use"
#using sbuild - https://wiki.ubuntu.com/SecurityTeam/BuildEnvironment
sudo apt install sbuild debhelper ubuntu-dev-tools piuparts moreutils schroot gnupg-agent -y
sudo adduser $USER sbuild
mkdir -p $HOME/ubuntu/scratch
cat <<EOF | sudo tee -a /etc/schroot/sbuild/fstab
/home/$USER/ubuntu/scratch /scratch none rw,bind 0 0
EOF
cat <<EOF | tee ~/.sbuildrc
# Name to use as override in .changes files for the Maintainer: field
# (mandatory, no default!).
\$maintainer_name='Zhang Hua <xxx.zhang@xxx.com>';
# Default distribution to build.
\$distribution = "bionic";
# Build arch-all by default.
\$build_arch_all = 0;
# When to purge the build directory afterwards; possible values are "never",
# "successful", and "always". "always" is the default. It can be helpful
# to preserve failing builds for debugging purposes. Switch these comments
# if you want to preserve even successful builds, and then use
# "schroot -e --all-sessions" to clean them up manually.
\$purge_build_directory = 'successful';
\$purge_session = 'successful';
\$purge_build_deps = 'successful';
# $purge_build_directory = 'never';
# $purge_session = 'never';
# $purge_build_deps = 'never';
# Directory for writing build logs to
\$log_dir=\$ENV{HOME}."/ubuntu/logs";
# don't remove this, Perl needs it:
1;
EOF
mkdir -p $HOME/ubuntu/{build,logs}
cat <<EOF | tee ~/.mk-sbuild.rc
SCHROOT_CONF_SUFFIX="source-root-users=root,sbuild,admin
source-root-groups=root,sbuild,admin
preserve-environment=true"
SKIP_UPDATES="1"
SKIP_PROPOSED="1"
DEBOOTSTRAP_PROXY=http://192.168.99.186:3142/
EOF
#mk-sbuild bionic --arch=amd64 --skip-updates --debootstrap-mirror=http://<mirror>/ubuntu --distro=ubuntu
# sg sbuild #do not need this line if you reenter ssh
mk-sbuild bionic --arch=amd64 --skip-updates
# install uca
schroot -l
schroot -c source:bionic-amd64 -u root
echo 'precedence ::ffff:0:0/96 100' >> /etc/gai.conf
apt install software-properties-common dirmngr vim ca-certificates ubuntu-cloud-keyring apt-transport-https -y
add-apt-repository cloud-archive:train
#deb http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/train main
#apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5EDB1B62EC4926EA
apt update
chmod 1777 /tmp && apt update
exit
To CHANGE the golden image: sudo schroot -c source:bionic-amd64 -u root
To ENTER an image snapshot: schroot -c bionic-amd64
To BUILD within a snapshot: sbuild -A -d bionic-amd64 PACKAGE*.dsc
To BUILD for : sbuild -A -d bionic-amd64 --host PACKAGE*.dsc
mkdir -p /bak/work/debian/neutron/16.1.0 && cd /bak/work/debian/neutron/16.1.0
dget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/neutron/2:16.1.0-0ubuntu2/neutron_16.1.0-0ubuntu2.dsc
dpkg-source -x neutron_16.1.0-0ubuntu2.dsc
sbuild-update -udc bionic-amd64 #it equals: apt update && apt upgrade
cd /bak/work/debian/neutron/16.1.0/neutron-16.1.0
sbuild --verbose -d bionic-amd64 ../neutron_*.dsc #use .. to point out the parent directory
#dsc: amd64 not in arch list or does not match any arch wildcards: all -- skipping
# ../neutron_*.dsc is using arch=all so need to use --arch-all for sbuild
sbuild --verbose -d bionic-amd64 --arch-all ../neutron_*.dsc
# Not removing build depends: cloned chroot in use
# E: Unable to correct problems, you have held broken packages.
镜像里添加了UCA后，报的错也和pbuilder是一样的，当然，这种错误和publider和sbuild本身都无关,所以sbuild也运行正确。
sbuild-build-depends-neutron-dummy : Depends: python3-neutron-lib (>= 2.2.0) but 1.29.1-0ubuntu1~cloud0 is to be installed
Depends: python3-ovsdbapp (>= 1.0.0) but 0.17.0-0ubuntu1~cloud0 is to be installed
Depends: python3-pyroute2 (>= 0.5.7) but 0.5.6-0ubuntu1~cloud0 is to be installed
注意，要改为使用focal的话，或者修改默认值（sed -i -e “s/bionic/focal/g” ~/.sbuildrc），或者使用（‘–git-builder=sbuild -As -d focal-amd64’）
gbp buildpackage --git-debian-branch=debian/2%16.1.0-0ubuntu2 --git-ignore-branch --git-ignore-new --git-builder='sbuild -As -d focal-amd64' --git-dist=focal --git-arch=amd64 -j8
使用debuild
先使用sbuild快速弄一个bionic环境出来：
sudo cp /etc/schroot/chroot.d/sbuild-bionic-amd64 /etc/schroot/chroot.d/sbuild-bionic-amd64-tmp
sudo cp -r /var/lib/schroot/chroots/bionic-amd64 /var/lib/schroot/chroots/bionic-amd64-tmp
sudo sed -i -e "s/bionic-amd64/bionic-amd64-tmp/g" /etc/schroot/chroot.d/sbuild-bionic-amd64-tmp
#sudo rm /etc/schroot/chroot.d/sbuild-bionic-amd64-tmp
#sudo rm -rf /var/lib/schroot/chroots/bionic-amd64-tmp
schroot -l
schroot -c source:bionic-amd64-tmp -u root
再试debuild
apt install devscripts curl ca-certificates bash-completion -y
dget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/neutron/2:16.0.0-0ubuntu2/neutron_16.0.0-0ubuntu2.dsc
dpkg-source -x neutron_16.0.0-0ubuntu2.dsc
cd neutron-16.0.0/
# install dependency, use mk-build-deps instead of 'apt build-dep neutron'
apt install devscripts equivs -y
mk-build-deps --install debian/control
apt install debhelper-compat openstack-pkg-tools python3-pbr -y
# install some dependency according to the output of 'debuild -i -us -uc -S'
apt install debhelper-compat dh-python openstack-pkg-tools python3-all python3-pbr -y
#build unsigned source package
debuild -i -us -uc -S
debuild的分解动作如下：
- 清理源代码树(debian/rules clean)
- 构建源代码包(dpkg-source -b)
- 构建程序(debian/rules build)
- 构建二进制包(fakeroot debian/rules binary)
- 使用 gpg 签署 .dsc 文件 使用
- dpkg-genchanges 和 gpg 创建并签署上传用的.changes 文件
报这个错：
dpkg-buildpackage: info: binary and diff upload (original source NOT included)
那就加-sa参数。
debuild -i -us -uc -S -sa
上面测16.0.1因为源码有问题不典型，让我们改测train(15.3.4)来只证明debuild可以即可(注意：下列参数-S也改成了-b):
apt-get source neutron
mk-build-deps --install debian/control
debuild -i -us -uc -b
通过自己从头构建熟悉git-buildpackage原理
https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.upstream-git.html
git-buildpackage的原理是：
- 准备git工程. 注意：这里初始添加了README.md之后会报：will cause dpkg-source: error: aborting due to unexpected upstream changes，但初始不加，在git branch时看不到master与upstream分支，还是先添加，呆会再删除
mkdir neutron-git-buildpackage && cd neutron-git-buildpackage
echo "# neutron-git-buildpackage" >> README.md
git init
git add README.md
git commit -m "first commit"
#git remote add origin git@github.com:zhhuabj/neutron-git-buildpackage.git
#git push origin master
- 会将neutron source code (not debian/ directory)提交到upstream branch，故先创建它：
git checkout -b upstream
- 回到master分支(此时好像不能创建新分支，是都测试好之后再创建分支）并准备neutron source code, 'gbp import-dsc’会自动将neutron source code下载下来，并提交到upstream branch
git checkout master
# gbp import-orig /tmp/tarball/new-upstream.tar.gz -u 15.3.4
gbp import-dsc https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/+sourcefiles/neutron/2:15.3.4-0ubuntu1~cloud1/neutron_15.3.4-0ubuntu1~cloud1.dsc
- 也在master分支准备debianized repository, 这时master中同时有upstream中的neutron源码和debian目录（Imported the debian/ directory into master as well as upstream’s files）
git checkout master
wget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/+sourcefiles/neutron/2:15.3.4-0ubuntu1~cloud1/neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
tar -xf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
rm -rf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
git add *
git commit -m 'init master'
- 此时状态是：
ubuntu@debbuild:/bak/work/neutron-git-buildpackage$ git branch
* master
upstream
ubuntu@debbuild:/bak/work/neutron-git-buildpackage$ ls
AUTHORS LICENSE api-ref debian neutron releasenotes setup.py
CONTRIBUTING.rst PKG-INFO babel.cfg devstack neutron.egg-info requirements.txt test-requirements.txt
ChangeLog README.rst bin doc playbooks roles tools
HACKING.rst TESTING.rst bindep.txt etc rally-jobs setup.cfg tox.ini
ubuntu@debbuild:/bak/work/neutron-git-buildpackage$ git checkout upstream
Switched to branch 'upstream'
ubuntu@debbuild:/bak/work/neutron-git-buildpackage$ ls
AUTHORS HACKING.rst README.rst babel.cfg devstack neutron rally-jobs roles test-requirements.txt
CONTRIBUTING.rst LICENSE TESTING.rst bin doc neutron.egg-info releasenotes setup.cfg tools
ChangeLog PKG-INFO api-ref bindep.txt etc playbooks requirements.txt setup.py tox.ini
ubuntu@debbuild:/bak/work/neutron-git-buildpackage$ git tag
debian/2%15.3.4-0ubuntu1_cloud1
upstream/15.3.4
- pristine-tar分支中准备tarball
git checkout -b pristine-tar
wget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/+sourcefiles/neutron/2:15.3.4-0ubuntu1~cloud1/neutron_15.3.4.orig.tar.gz
chmod +x neutron_15.3.4.orig.tar.gz
git add neutron_15.3.4.orig.tar.gz
git commit -m 'neutron_15.3.4.orig.tar.gz'
# pristine-tar: committed neutron_15.3.4.orig.tar.gz.delta to branch pristine-tar
pristine-tar commit ./neutron_15.3.4.orig.tar.gz 15.3.4
pristine-tar list |grep 15
#Remember to tell git to push both the pristine-tar branch, and your tag:
#git push --all --tags
#once your local tarball has lost - http://manpages.ubuntu.com/manpages/trusty/man1/pristine-tar.1.html
#pristine-tar checkout ../hello-1.0.tar.gz
或者直接从上游git中获取
# generate tarball from upstream
cd /bak/openstack/neutron
git checkout master
git checkout -b 15.3.4 15.3.4
git archive --output=../neutron_15.3.4.tar.gz --format=tar HEAD
# commit tarball into this git repo
pristine-tar commit /bak/openstack/neutron_15.3.4.orig.tar.gz 15.3.4
- 之前就可以回master分支，安装依赖并运行gbp buildpackage了，它会调用’dpkg-buildpackage -rfakeroot -us -uc -ui -i -I’。都测试完之后，就可以将master分支打tag了
git checkout master
# also need to enable UCA
sudo mk-build-deps --install debian/control #install dependency
gbp buildpackage --git-ignore-branch --git-ignore-new
总结，这个重点，即要安装UCA，也要安装依赖，git有改还得添加–git-ignore-new来忽略改动。
但是它会报这个错：#neutron_15.3.4.orig.tar.gz does not match stored hash，用下列workaround就OK啦：
#neutron_15.3.4.orig.tar.gz does not match stored hash
pristine-tar checkout ../neutron_15.3.4.orig.tar.gz
gbp buildpackage --git-tarball-dir=/bak/work --git-ignore-branch --git-ignore-new
解决运行gbp import-dsc过程中遇到的问题
https://wiki.debian.org/PackagingWithGit
得将neutron source code 导入到debianized repository中去，
1, 先看通过"gbp import-dsc"从dsc中导入neutron source code
可以直接从neutron的上游下载source code:
https://releases.openstack.org/train/#train-neutron
https://tarballs.openstack.org/neutron/neutron-15.3.4.tar.gz
也可以用’gbp import-dsc’从dsc中导入neutron source code
sudo apt install git-buildpackage -y
mkdir -p /tmp/deb
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/
wget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/+sourcefiles/neutron/2:15.3.4-0ubuntu1~cloud1/neutron_15.3.4-0ubuntu1~cloud1.dsc
sudo chown -R $USER ~/.gnupg/
# bakup gpg keys
gpg --output mygpgkey_pub.gpg --armor --export $GPGKEY
gpg --output mygpgkey_sec.gpg --armor --export-secret-key $GPGKEY
# import gpg keys from other machine
sudo apt-get install rng-tools gnupg-agent -y && sudo rngd -r /dev/urandom && killall -q gpg-agent && eval $(gpg-agent --daemon)
gpg --import mygpgkey_pub.gpg
gpg --allow-secret-key-import --import mygpgkey_sec.gpg
gpg --list-public
gpg --list-sig
export GPGKEY=C7100A4CD0D8F3AE44212746E6A84FFFCF31A67F
gpg --send-keys --keyserver keyserver.ubuntu.com $GPGKEY
# import dsc. the dsc provider signs dsc, and dsc user verifies dsc
gpg --verify ./neutron_15.3.4-0ubuntu1~cloud1.dsc
gpg --search-keys 3516D1A5BF0077E71414E19715B9B3EE0DCDF806
gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3516D1A5BF0077E71414E19715B9B3EE0DCDF806
# you can ignore 'There is no indication that the signature belongs to the owner'
# as it simply means you have not established a web of trust with other GPG users
gpg --verify ./neutron_15.3.4-0ubuntu1~cloud1.dsc
rm -rf ./neutron_15.3.4-0ubuntu1~cloud1.dsc
git config --global user.email "xxx.zhang@xxx.com"
git config --global user.name "Zhang Hua"
＃ Then export the key to your local trustedkeys to make it trusted:
gpg --no-default-keyring -a --export 3516D1A5BF0077E71414E19715B9B3EE0DCDF806 | gpg --no-default-keyring --keyring ~/.gnupg/trustedkeys.gpg --import -
# but it still says: gpg: Can't check signature: No public key
gbp import-dsc https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/+sourcefiles/neutron/2:15.3.4-0ubuntu1~cloud1/neutron_15.3.4-0ubuntu1~cloud1.dsc
尽管已经导入key, 但上面使用’gbp import-dsc’仍然报“Can’t check signature: No public key"。是因为还要将dsc provider的公钥 export the key to your local trustedkeys to make it trusted
＃ Then export the key to your local trustedkeys to make it trusted:
gpg --no-default-keyring -a --export 3516D1A5BF0077E71414E19715B9B3EE0DCDF806 | gpg --no-default-keyring --keyring ~/.gnupg/trustedkeys.gpg --import -
如果还是不行，可以使用下列dget命令作为workaround，dget即使没有证书也会下载文件：
sudo apt-get install debian-keyring -y
dget --download-only -q https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/+sourcefiles/neutron/2:15.3.4-0ubuntu1~cloud1/neutron_15.3.4-0ubuntu1~cloud1.dsc
dpkg-source -x neutron_15.3.4-0ubuntu1~cloud1.dsc
gpg --keyserver keyserver.ubuntu.com --recv-keys 3516D1A5BF0077E71414E19715B9B3EE0DCDF806
＃ Then export the key to your local trustedkeys to make it trusted:
gpg --no-default-keyring -a --export 3516D1A5BF0077E71414E19715B9B3EE0DCDF806 | gpg --no-default-keyring --keyring ~/.gnupg/trustedkeys.gpg --import -
使用ubuntu-openstack-dev debian源码构建
上面熟悉了从零构建git-buildpackage工程，实际上ubuntu-openstack-dev中已经有了这个工程了。
- master分支应该同时有debian目录和neutron源码
- upstream分支只有neutron源码，没有debain目录
- pristine-tar分支只有tarball，并且使用pristine-tar list命令能看到，也要能运行pristine-tar checkout …/xxx.tar.gz
- 编译时是在master分支运行
- 暂不清楚如果编译15.3.4分支，因为15.3.4下没有debain目录，有debian目录的是这个：
ubuntu@debbuild:/bak/work/debsource/neutron$ git tag |grep debian |grep 15.3.4
debian/2%15.3.4-0ubuntu1_cloud0
debian/2%15.3.4-0ubuntu1_cloud1
git-buildpackage命令运行在neutron代码分支之后，会先使用’pristine-tar checkout …/xxx.orig.tar.gz’先tarball弄到neutron代码分支（tarball存在pristine-tar分支中），然后再build.
# https://wiki.ubuntu.com/OpenStack/CorePackages
sudo apt install git-buildpackage -y
sudo mkdir -p /bak/work/debsource && sudo chown -R $USER /bak && cd /bak/work/debsource
git clone https://git.launchpad.net/~ubuntu-openstack-dev/ubuntu/+source/neutron
cd neutron
git checkout pristine-tar
git checkout upstream
git checkout master
# 仅编译15.3.4, 这个tag (debian/2%15.3.4-0ubuntu1_cloud0)有debian目录，应该用它
git checkout -b debian/2%15.3.4-0ubuntu1_cloud0 debian/2%15.3.4-0ubuntu1_cloud0
git checkout debian/2%15.3.4-0ubuntu1_cloud0
gbp buildpackage --git-ignore-branch --git-ignore-new -us -uc
但是上面命令报下面这个错：
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
所以本想用下列workaround (–git-tarball-dir=/bak/openstack/tarball)来避开上面问题，但是又报不匹配的错
# generate tarball from upstream
cd /bak/openstack/neutron
git checkout master
git checkout -b 15.3.4 15.3.4
git archive --output=/bak/openstack/tarball/neutron_15.3.4.orig.tar.gz --format=tar HEAD
gbp buildpackage --git-tarball-dir=/bak/openstack/tarball --git-ignore-branch --git-ignore-new -us -uc
看来还是得想办法解决XD3_INVALID_INPUT的问题。得想办法运行下列命令成功：
pristine-tar checkout ../neutron_15.3.4.orig.tar.gz
但这个命令在focal上是能运行成功的，可能是bionic的pristine-tar版本有问题吧，可以在focal导入tarball后再拷到bionic中，再使用’–git-tarball-dir='来workaroud.
或者我们可以直接在focal中使用pbuilder + git-buildpackage 来规避这个问题。
使用pbuilder + ubuntu-openstack-dev debian源码构建
第一步，创建pbuilder环境。这里的pbuilder实际上是cowpbuilder, 镜像格式是cow格式。
sudo apt-get install git-buildpackage cowbuilder debian-archive-keyring -y
#it will delete /var/cache/pbuilder/aptcache
#sudo pbuilder clean
#sudo pbuilder --create --distribution bionic --architecture amd64 --debootstrapopts --variant=buildd
rm -rf sudo rm -rf /var/cache/pbuilder/base-bionic-amd64.cow
sudo mv /etc/pbuilderrc /tmp/
DIST=bionic ARCH=amd64 git-pbuilder create
sudo mv /tmp/pbuilderrc /etc/
#sudo pbuilder update --basetgz /var/cache/pbuilder/bionic-train-base.tgz
DIST=bionic ARCH=amd64 git-pbuilder update
#sudo pbuilder login --save-after-login --basetgz /var/cache/pbuilder/bionic-train-base.tgz
DIST=bionic ARCH=amd64 git-pbuilder login --save-after-login
echo 'precedence ::ffff:0:0/96 100' >> /etc/gai.conf
apt install software-properties-common dirmngr vim ca-certificates ubuntu-cloud-keyring apt-transport-https -y
add-apt-repository cloud-archive:train
#deb http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/train main
#apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5EDB1B62EC4926EA
sed -i -e "s/# deb-src/deb-src/" /etc/apt/sources.list.d/cloudarchive-train.list
apt update
exit
第二步，使用pubilder (在gbp buuildpackage中添加–git-pbuilder --git-dist=bionic --git-arch=amd64）编译
sudo apt install devscripts equivs -y
sudo mkdir -p /bak/work/debsource && sudo chown -R $USER /bak && cd /bak/work/debsource
git clone https://git.launchpad.net/~ubuntu-openstack-dev/ubuntu/+source/neutron
cd neutron
git checkout pristine-tar
git checkout upstream
git checkout master
git checkout -b debian/2%15.3.4-0ubuntu1_cloud0 debian/2%15.3.4-0ubuntu1_cloud0
git checkout debian/2%15.3.4-0ubuntu1_cloud0
#sudo mk-build-deps --install debian/control
#gbp buildpackage --git-ignore-branch --git-ignore-new -us -uc
gbp buildpackage --git-pbuilder --git-dist=bionic --git-arch=amd64 --git-ignore-branch --git-ignore-new -uc -us -j16
#debuild clean
在neutron源码中自动导入tarball构建
下面直接从neutron源码中使用gbp来编译:
https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.upstream-git.html
1, 首先，neutron source code必须从orgin更名为upstream避免和debian repository混淆
git clone --no-checkout -o upstream https://github.com/openstack/neutron
2, 将15.3.4的源码切换到debian/15.3.4分支，并且将debian目录加入到debian分支
cd neutron
git checkout -b debian/15.3.4 15.3.4
wget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/+sourcefiles/neutron/2:15.3.4-0ubuntu1~cloud1/neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
tar -xf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
rm -rf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
git add debian/
git commit -m 'add debian'
#gbp:error: Couldn't commit to 'pristine-tar' with upstream '15.3.4': pristine-tar: more than one ref matches "15.3.4":
3, 因为debian/15.3.4分支有debian目录，应该是在这个分支下运行编译命令，这们这里没有指定tarball包因为’–git-pristine-tar --git-pristine-tar-commit '会自动从源码中准备tarball
gbp buildpackage --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='%(version)s' --git-debian-branch=debian/15.3.4 -us -uc
若更新了源文件的话, ‘gbp dch’会在changelog中添加一记录（15.3.4-0ubuntu1cloud1ubuntu11.gbp5d92a7），’–git-ignore-new’用于告诉 'gbp buildpackage’工作目录不干净。
git fetch upstream
git merge 15.3.4
# gbp:info: Changelog 2:15.3.4-0ubuntu1~cloud1ubuntu1~1.gbp5d92a7 (snapshot #1) prepared up to 5d92a7b
gbp dch --debian-branch=debian/15.3.4 --snapshot --auto debian/
gbp buildpackage --git-ignore-new --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='%(version)s' -us -uc
测试没问题之后，修改changelog和build一个新版本
gbp dch --release --auto --debian-branch=debian/15.3.4
git commit -m"Release 1.1-1" debian/changelog
gbp buildpackage --git-upstream-tag='%(version)s' --git-debian-branch=debian/15.3.4 -us -uc
再总结 - 通过自己从头构建熟悉git-buildpackage原理
这个是对”通过自己从头构建熟悉git-buildpackage原理“这一节的总结，这里还是要自己准备tarball麻烦，最好参考”通过neutron git来使用gbp“这一节由git来自动处理tarball. 还最好考虑git-buildpackage怎么与pbuilder结合(git-pbuilder)。
1, 准备git工程, 注意：这里初始添加了README.md之后会报：will cause dpkg-source: error: aborting due to unexpected upstream changes，但初始不加，在git branch时看不到master与upstream分支，还是先添加，呆会再删除 (注意：最后一次试就又遇到这个问题，不需要删除）.
mkdir neutron-git-buildpackage2 && cd neutron-git-buildpackage2
echo "# neutron-git-buildpackage" >> README.md
git init
git add README.md
git commit -m "first commit"
#git remote add origin git@github.com:zhhuabj/neutron-git-buildpackage.git
#git push origin master
2, neutron源码工程下准备 tarball
mkdir -p /bak/openstack/tarball/ && cd /bak/openstack
git clone https://github.com/openstack/neutron
cd neutron
git checkout master
git checkout -b 15.3.4 15.3.4
mkdir -p /tmp/tarball
git archive --output=/tmp/tarball/neutron_15.3.4.orig.tar.gz --format=tar.gz HEAD
3, 创建upstream分支
git checkout -b upstream
4, 回到master分支（这时不能使用15.3.4，但master测试没问题后再加tag为15.3.4)导入tarball
git checkout master
gbp import-orig /tmp/tarball/neutron_15.3.4.orig.tar.gz -u 15.3.4
只有使用’gbp import-orig’导入tarball包才会提交到upstream分支，并merge到master分支（也就是upstream与master分支都有）, 此时状态为：
ubuntu@debbuild:/bak/work/neutron-git-buildpackage2$ git branch
* master
upstream
ubuntu@debbuild:/bak/work/neutron-git-buildpackage2$ ls
CONTRIBUTING.rst LICENSE TESTING.rst babel.cfg bindep.txt doc neutron rally-jobs requirements.txt setup.cfg test-requirements.txt tox.ini
HACKING.rst README.rst api-ref bin devstack etc playbooks releasenotes roles setup.py tools
ubuntu@debbuild:/bak/work/neutron-git-buildpackage2$ git checkout upstream
Switched to branch 'upstream'
ubuntu@debbuild:/bak/work/neutron-git-buildpackage2$ ls
CONTRIBUTING.rst LICENSE TESTING.rst babel.cfg bindep.txt doc neutron rally-jobs requirements.txt setup.cfg test-requirements.txt tox.ini
HACKING.rst README.rst api-ref bin devstack etc playbooks releasenotes roles setup.py tools
ubuntu@debbuild:/bak/work/neutron-git-buildpackage2$ git tag
upstream/15.3.4
5, master分支中添加debian目录(此时只能用master，不能创建tag, tag可在master中测试好了再打)
git checkout master
wget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/+sourcefiles/neutron/2:15.3.4-0ubuntu1~cloud1/neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
tar -xf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
rm -rf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
git add debian
git commit -m 'add debain'
6, pristine-tar commit tarball, 总之，通过’pristine-tar list’ 得能看到neutron_15.3.4.orig.tar.gz 15.3.4, 这样编译系统在编译的时候才能通过’pristine-tar checkout …/neutron_15.3.4.orig.tar.gz’获取它。
pristine-tar commit /tmp/tarball/neutron_15.3.4.orig.tar.gz 15.3.4
pristine-tar list
pristine-tar commit会自动添加pristine-tar分支：
ubuntu@debbuild:/bak/work/neutron-git-buildpackage2$ git checkout pristine-tar
Switched to branch 'pristine-tar'
ubuntu@debbuild:/bak/work/neutron-git-buildpackage2$ ls
neutron_15.3.4.orig.tar.gz.delta neutron_15.3.4.orig.tar.gz.id
７，回到master分支编译. 它是使用debuild来编译的，应该也可以和pbuilder等集成。
git checkout master
gbp buildpackage --git-ignore-branch --git-ignore-new
上面会遇到这个错误”pristine-tar: /bak/work/build-area/neutron_15.3.4.orig.tar.gz does not match stored hash“，下面使用pristine-tar checkout时也会报这个错，直接用–git-tarall-dir来指定之前使用git archive创建的tarball来workaround就好了（-us -uc意为不签名)：
#pristine-tar checkout /tmp/tarball/neutron_15.3.4.orig.tar.gz
#gbp buildpackage --git-tarball-dir=/tmp/tarball --git-ignore-branch --git-ignore-new -S -us -uc -sa
gbp buildpackage --git-tarball-dir=/tmp/tarball --git-ignore-branch --git-ignore-new -us -uc
8，编译后的包在/bak/work/build-area目录中
9, 都没问题之后，打tag归档，今后可以在该tag下运行编译命令了：
git checkout master
git tag '15.3.4'
git checkout -b 15.3.4 15.3.4
git checkout 15.3.4
gbp buildpackage --git-tarball-dir=/tmp/tarball --git-ignore-branch --git-ignore-new -us -uc
再总结 - 在neutron源码中自动导入tarball构建
这是针对"在neutron源码中自动导入tarball构建”一节更快速的总结.
sudo apt install git-buildpackage pristine-tar -y
# git clone --no-checkout -o upstream https://github.com/openstack/neutron
git clone https://github.com/openstack/neutron
cd neutron
# create upstream branch
git checkout master && git checkout -b upstream
# create pristine-tar branch, but we don't need to prepare tarball because '--git-pristine-tar --git-pristine-tar-commit' will help us create it automatically
git checkout master && git checkout -b pristine-tar
# create debain/15.3.4 branch with upstream neutron=15.3.4
git checkout master && git checkout -b debian/15.3.4 15.3.4
# add debian package into debian/15.3.4
git checkout debian/15.3.4
wget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/+sourcefiles/neutron/2:15.3.4-0ubuntu1~cloud1/neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
tar -xf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
rm -rf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
git add debian
git commit -m 'add debian for 15.3.4'
# run 'gbp buildpackage' command under the directory which has debian
# --git-pristine-tar and --git-pristine-tar-commit will create tarball automatically
git checkout debian/15.3.4
gbp buildpackage --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='%(version)s' --git-debian-branch=debian/15.3.4 --git-ignore-branch --git-ignore-new -us -uc
报下列错，那是因为要检出15.3.4分支(git checkout master && git checkout -b 15.3.4 15.3.4)：
ubuntu@debbuild:/bak/openstack/neutron$ gbp buildpackage --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='%(version)s' --git-debian-branch=debian/15.3.4 --git-ignore-branch --git-ignore-new -us -uc
gbp:error: Couldn't commit to 'pristine-tar' with upstream '15.3.4': pristine-tar: more than one ref matches "15.3.4":
480f4b7479bc0b19752edde46fe90660a94cc654 refs/heads/debian/15.3.4
729f6aefe103a0ba10b71888f84b6247d694bc04 refs/tags/15.3.4
附录 - 如何检查包依赖问题
上面种种方法都有这么一个问题（openstack-pkg-tools (>= 85ubuntu3~)），所以我们有必要检查这个源码包究竟有没有问题。
原来，错误原因是必须添加：sudo add-apt-repository cloud-archive:stein
sudo add-apt-repository cloud-archive:stein
sudo sed -i -e "s/# deb-src/deb-src/" /etc/apt/sources.list.d/cloudarchive-train.list
sudo apt update
sudo apt-cache policy neutron-l3-agent
sudo apt-get source neutron=2:15.3.4-0ubuntu1~cloud1
cd neutron-15.3.4/
$ grep -r 'openstack-pkg-tools' debian/control
openstack-pkg-tools (>= 85ubuntu3~),
$ sudo apt-cache policy openstack-pkg-tools |grep Candidate
Candidate: 99ubuntu1~cloud0
附录 - 其他
1, gbp buildpackage之后无问题，可以加tag，会自动将neutron source code和debian source code加tag: debian/2%15.3.4-0ubuntu1_cloud1
gbp buildpackage --git-tag-only --git-sign-tags --git-ignore-new
#git checkout -b debian/2%15.3.4-0ubuntu1_cloud1 debian/2%15.3.4-0ubuntu1_cloud1
2, 然后可以推入远程repo
git push origin --all --follow-tags
最佳实践
- 使用pbuilder避免在物理机上安装依赖
- 直接使用neutron源码，并在neutron源码自动产生tarball的方式
第一步，创建pbuilder环境
#sudo pbuilder --create --distribution bionic --architecture amd64 --debootstrapopts --variant=buildd
rm -rf sudo rm -rf /var/cache/pbuilder/base-bionic-amd64.cow
sudo mv /etc/pbuilderrc /tmp/
DIST=bionic ARCH=amd64 git-pbuilder create
sudo mv /tmp/pbuilderrc /etc/
#sudo pbuilder update --basetgz /var/cache/pbuilder/bionic-train-base.tgz
DIST=bionic ARCH=amd64 git-pbuilder update
#sudo pbuilder login --save-after-login --basetgz /var/cache/pbuilder/bionic-train-base.tgz
DIST=bionic ARCH=amd64 git-pbuilder login --save-after-login
echo 'precedence ::ffff:0:0/96 100' >> /etc/gai.conf
apt install software-properties-common dirmngr vim ca-certificates ubuntu-cloud-keyring apt-transport-https -y
# Failed to connect to socket /run/user/1000/bus: No such file or directory
apt install dbus -y && /etc/init.d/dbus start
add-apt-repository cloud-archive:train
#deb http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/train main
#apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5EDB1B62EC4926EA
sed -i -e "s/# deb-src/deb-src/" /etc/apt/sources.list.d/cloudarchive-train.list
apt update
exit
第二步，准备neutron源码环境，还要创建upstream与prinstine-tar两个分支，以及要编译的15.3.4分支，以及存放15.3.4源码及debian目录的debian/15.3.4分支
sudo apt install git-buildpackage pristine-tar -y
git clone https://github.com/openstack/neutron
cd neutron
git checkout master && git checkout -b upstream
git checkout master && git checkout -b pristine-tar
git checkout master && git checkout -b debian/15.3.4 15.3.4
git checkout master && git checkout -b 15.3.4 15.3.4
git checkout debian/15.3.4
wget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/+sourcefiles/neutron/2:15.3.4-0ubuntu1~cloud1/neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
tar -xf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
rm -rf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
git add debian
git commit -m 'add debian for 15.3.4'
第三步，使用了git-builder来编译。并且通过“–git-pristine-tar --git-pristine-tar-commit ”来配置自动导出tarball
git checkout debian/15.3.4
# dont's use git-builder
#gbp buildpackage --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='%(version)s' --git-debian-branch=debian/15.3.4 --git-ignore-branch --git-ignore-new -us -uc
# use git-builder
gbp buildpackage --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='%(version)s' --git-debian-branch=debian/15.3.4 --git-ignore-branch --git-ignore-new -us -uc --git-pbuilder --git-dist=bionic --git-arch=amd64 -j8
但是会报下列dbus的错：
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/user/1000/bus: No such file or directory
debian/rules:16: recipe for target 'override_dh_install' failed
试了下面的还是不行。
DIST=bionic ARCH=amd64 git-pbuilder login --save-after-login
apt install dbus
/etc/init.d/dbus start
exit
git-pbuilder创建出来的镜像里没有dbus包和环境变量（DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus），暂不清楚是否和这相关。
如果不使用git-builder，直接运行’gpb buildpackage’ + debuild模式，it works. 注意：下列这个测试没用pbuilder只能在bionic上进行。
# NOTE: must run on bionic
sudo mk-build-deps --install debian/control
gbp buildpackage --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='%(version)s' --git-debian-branch=debian/15.3.4 --git-ignore-branch --git-ignore-new -us -uc -j8
将pbuilder换成sbuild也成功了（换sbuild时要去掉-us -uc, 见：https://www.pseudorandom.co.uk/2008/sbuild-dm/ , 另外，使用的是–git-builder=‘sbuild -A’， -A代表all-arch，构建源码包时用: --git-builder=‘sbuild -As’
gbp buildpackage --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='%(version)s' --git-debian-branch=debian/15.3.4 --git-ignore-branch --git-ignore-new --git-builder='sbuild -A' --git-dist=bionic --git-arch=amd64 -j8
在neutron debian source code(https://git.launchpad.net/~ubuntu-openstack-dev/ubuntu/+source/neutron)中运行pbuilder也出现了dbus的错误，现在确认是这个dbus错误只是在pbuilder中才出现。
示例：ubuntu debian源码上编译16.1.0
neutron debian source 上运行：
git checkout -b debian/2%16.1.0-0ubuntu2 debian/2%16.1.0-0ubuntu2
gbp buildpackage --git-debian-branch=debian/2%16.1.0-0ubuntu2 --git-ignore-branch --git-ignore-new --git-builder='sbuild -As' --git-dist=bionic --git-arch=amd64 -j8
但会报错：
sbuild-build-depends-main-dummy : Depends: python3-neutron-lib (>= 2.2.0) but 1.29.1-0ubuntu1~cloud0 is to be installed
Depends: python3-ovsdbapp (>= 1.0.0) but 0.17.0-0ubuntu1~cloud0 is to be installed
Depends: python3-pyroute2 (>= 0.5.7) but 0.5.6-0ubuntu1~cloud0 is to be installed
那是因为镜像中使用的是train UCA(python3-neutron-lib=1.29.1)，train对应的是15.3.4，并不是16.1.0，所以有问题。vimdiff一下：
git checkout debian/2%16.1.0-0ubuntu2
mkdir -p /tmp/16.1.0 && cp -r debian /tmp/16.1.0/
git checkout debian/2%15.3.4-0ubuntu1_cloud0
mkdir -p /tmp/15.3.4 && cp -r debian /tmp/15.3.4/
vimdiff /tmp/15.3.4/debian/control /tmp/16.1.0/debian/control
15.3.4 -> python3-neutron-lib (>= 1.29.1),
16.1.0 -> python3-neutron-lib (>= 2.2.0),
python3-neutron-lib 2.2.0来自focal前的一个版本也就是19.10
apt install devscripts liburi-perl wget -y
root@node1:/# rmadison python3-neutron-lib
python3-neutron-lib | 0.0.2-2 | xenial/universe | all
python3-neutron-lib | 1.13.0-0ubuntu1 | bionic/universe | all
python3-neutron-lib | 2.3.0-0ubuntu1 | focal | all
python3-neutron-lib | 2.10.1-0ubuntu1 | hirsute | all
python3-neutron-lib | 2.12.0-0ubuntu1 | impish | all
$ cmadison python3-neutron-lib
python3-neutron-lib | 0.0.2-2~cloud0 | mitaka | trusty-updates | all
python3-neutron-lib | 0.0.2-2~cloud0 | mitaka-proposed | trusty-proposed | all
python3-neutron-lib | 1.13.0-0ubuntu1~cloud0 | queens | xenial-updates | all
python3-neutron-lib | 1.13.0-0ubuntu1~cloud0 | queens-proposed | xenial-proposed | all
python3-neutron-lib | 1.25.0-0ubuntu1~cloud0 | stein | bionic-updates | all
python3-neutron-lib | 1.25.0-0ubuntu1~cloud0 | stein-proposed | bionic-proposed | all
python3-neutron-lib | 1.29.1-0ubuntu1~cloud0 | train | bionic-updates | all
python3-neutron-lib | 1.29.1-0ubuntu1~cloud0 | train-proposed | bionic-proposed | all
python3-neutron-lib | 2.3.0-0ubuntu1~cloud0 | ussuri | bionic-updates | all
python3-neutron-lib | 2.3.0-0ubuntu1~cloud0 | ussuri-proposed | bionic-proposed | all
python3-neutron-lib | 2.6.1-0ubuntu1~cloud0 | victoria | focal-updates | all
python3-neutron-lib | 2.6.1-0ubuntu1~cloud0 | victoria-proposed | focal-proposed | all
python3-neutron-lib | 2.10.1-0ubuntu1~cloud0 | wallaby | focal-updates | all
python3-neutron-lib | 2.10.1-0ubuntu1~cloud0 | wallaby-proposed | focal-proposed | all
python3-neutron-lib | 2.12.0-0ubuntu1~cloud0 | xena | focal-updates | all
python3-neutron-lib | 2.12.0-0ubuntu1~cloud0 | xena-proposed | focal-proposed | all
所以上面的16.1.0的源码显然是针对focal来做的（这里也有显示：https://launchpad.net/ubuntu/+source/neutron/2%3A16.1.0-0ubuntu2/+publishinghistory），所以：
- 目前bionic-stein的版本是15.3.4, focal-ussuri的版本是16.4.0, 现在想要测的是16.1.0
- 如果在bionic里测16.1.0的话，得修改debian/control与requirment.txt中的发生问题的pip版本号，但这也不一定行，因为neutron代码也变了既然requirement.txt说依赖某个包的高版本可能就真是需要高版本
- 那样就只能在focal里测16.1.0了。将focal现有的16.4.0改成16.1.0来测，sbuild的镜像什么的都得由bionic改成16.1.0
# create focal sbuid image
mk-sbuild focal --arch=amd64
schroot -l
schroot -c source:focal-amd64 -u root
# clone neutron debian source code
cd /bak/work/debsource
git clone https://git.launchpad.net/~ubuntu-openstack-dev/ubuntu/+source/neutron
cd neutron
git checkout pristine-tar
git checkout upstream
git checkout master
# build with focal image
git checkout -b debian/2%16.1.0-0ubuntu2 debian/2%16.1.0-0ubuntu2
git checkout debian/2%16.1.0-0ubuntu2
# 注意：下面使用了--git-dist=focal --git-arch=amd64来指定用focal但实际用的还是bionic，
# 原来git-dist只是针对pbuilder，这样使用了~/.sbuildrc的默认项：sed -i -e "s/bionic/focal/g" ~/.sbuildrc
#gbp buildpackage --git-debian-branch=debian/2%16.1.0-0ubuntu2 --git-ignore-branch --git-ignore-new --git-builder='sbuild -As' --git-dist=focal --git-arch=amd64 -j8
#所以或者使用（sed -i -e "s/bionic/focal/g" ~/.sbuildrc），或者使用（'--git-builder=sbuild -As -d focal-amd64'）
gbp buildpackage --git-debian-branch=debian/2%16.1.0-0ubuntu2 --git-ignore-branch --git-ignore-new --git-builder='sbuild -As -d focal-amd64' --git-dist=focal --git-arch=amd64 -j8
示例：neutron upsteam源码上编译15.3.4
# prepare bionic-train sbuild image
sudo cp /etc/schroot/chroot.d/sbuild-bionic-amd64 /etc/schroot/chroot.d/sbuild-bionic-train-amd64
sudo cp -r /var/lib/schroot/chroots/bionic-amd64 /var/lib/schroot/chroots/bionic-train-amd64
sudo sed -i -e "s/bionic-amd64/bionic-train-amd64/g" /etc/schroot/chroot.d/sbuild-bionic-train-amd64
schroot -l
schroot -c source:bionic-train-amd64 -u root
apt install devscripts curl ca-certificates bash-completion software-properties-common vim -y
# Couldn't create temporary file /tmp/apt.conf.5gKxoB for passing config to apt-key
chmod 1777 /tmp
# /usr/bin/apt-key: cannot create /dev/null: Permission denied
# https://askubuntu.com/questions/764719/fix-permissions-after-upgrade-to-16-04
chmod go+rw /dev/null
add-apt-repository cloud-archive:train
git clone https://github.com/openstack/neutron
cd neutron
#upstream与pristine-tar不是必须的吧
#git checkout master && git checkout -b upstream
#git checkout master && git checkout -b pristine-tar
git checkout master && git checkout -b debian/15.3.4 15.3.4
git checkout master && git checkout -b 15.3.4 15.3.4
git checkout debian/15.3.4
wget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/+sourcefiles/neutron/2:15.3.4-0ubuntu1~cloud1/neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
tar -xf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
rm -rf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
git add debian
git commit -m 'add debian for 15.3.4'
# 已经在15.3.4分支下，--git-debian-branch=debian/15.3.4也不是必须的吧
git checkout debian/15.3.4
#gbp buildpackage --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='%(version)s' --git-debian-branch=debian/15.3.4 --git-ignore-branch --git-ignore-new -us -uc
gbp buildpackage --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='%(version)s' --git-debian-branch=debian/15.3.4 --git-ignore-branch --git-ignore-new --git-builder='sbuild -As -d bionic-train-amd64' -j8
示例 - 在15.3.4与16.0.0之间二分准备15.3.5的测试包
gbp buildpackage要想不自己准备tarball包的话，只能根据tag来做，不能根据commit来做，所以需自己准备如15.3.5与debian/15.3.5 (不自己准备tag的话似乎tarball包不更新使用15.3.4).
当然，想自己准备tarball的话，就是另外一种方式。这里讲的是不自己准备tarball包的模式。
e562ecec2669c39b3628f7744011467c7394088e (在15.3.4基础上提交debian目录的commit id)
15.3.4 - 0f18d406a4134cf769fdf6f2a004c98cbe409215
16.0.0 - c06cb95b6f46574e74244fd738873290fd1773cb
# 下载代码
# first fork https://github.com/openstack/neutron
git clone https://github.com/zhhuabj/neutron.git
git config user.name
git config user.email
git remote add upstream https://github.com/openstack/neutron
git remote set-url --push upstream no_push
# update
git fetch upstream
git checkout master
git merge upstream/master
git push origin master
#git rebase upstream/master
#git push origin master -f
# http://www.360doc.com/content/18/0208/09/19862658_728539054.shtml
# git二分，先找到15.3.4与16.0.0之间的中间版本1c2e10f859
cd neutron
git checkout master
git bisect start
git bisect good 15.3.4
$ git bisect bad 16.0.0
Bisecting: a merge base must be tested
[1c2e10f8595d2286bd9bec513bc5a346a84a6f7c] Merge "Remove get_external_network_id for router"
$ git status
HEAD detached at 1c2e10f859
# 在上面1c2e10f859的基础上创建几个分支
git checkout -b 15.3.5
git checkout -b debian/15.3.5
# 往debian/15.3.5中添加15.3.4的debian目录
cp -r ../debian .
git add debian/ && git commit -m 'add debian'
# 修改debian/changelog
dch -i
neutron (2:15.3.5-0ubuntu1~cloud0) bionic-train; urgency=medium
git commit -m "releasing package 2:15.3.5-0ubuntu1~cloud0" debian/changelog
# 视情况清空debian/patches/避免一些错误, 并记得用debcommit提交
cp -r debian/patches/ /tmp/
rm -rf debian/patches/* && touch debian/patches/series
git add -u && debcommit -m 'delete series'
# 然后git log会看到：commit f1ed620b2abd4a04013ed9549fcafff5a290ff5b (HEAD -> debian/15.3.5)
# 编译
git checkout 15.3.5 && git tag --no-sign 15.3.5 -m "15.3.5"
git checkout debian/15.3.5 && git tag --no-sign debian/15.3.5 -m "debian/15.3.5"
git checkout debian/15.3.5
#git push --all
#git push --tags
# 测试之后可以使用'git bisect bad'或'git bisect good'来标记, 使用’git bisect replay‘可以看到曾经测试过的内容
git bisect log > bisectlog
git bisect bad | git bisect good
# 下一个二分可以先回到15.3.4基准，然后再git merge下一个二分点
git reset --hard e562ecec2669c39b3628f7744011467c7394088e
git merge <下一个二分点>
# 二分完成之后
git bisect reset
一个错误：
# 错误 - https://paste.ubuntu.com/p/DtfMXg3Yq2/
# The 'weakrefmethod>=1.0.2' distribution was not found and is required by the application
1, 15.3.4与1c2e10f859源码中有对weakrefmethod的定义
# 15.3.4
$ grep -r 'weakrefmethod' requirements.txt
weakrefmethod>=1.0.2;python_version=='2.7' # PSF
# git checkout -b 1c2e10f859 1c2e10f859
$ grep -r 'weakrefmethod' requirements.txt
weakrefmethod>=1.0.2;python_version=='2.7' # PSF
2, 在tarball中也有啊
hua@node1:/bak/work/tmp/build-area/neutron-15.3.5$ grep -r 'weakrefmethod' requirements.txt
weakrefmethod>=1.0.2;python_version=='2.7' # PSF
3, 难道是要在/bak/work/tmp/neutron/debian/control中加吗？
git add -u && debcommit -m 'add python-weakrefmethod'
hua@node1:/bak/work/tmp/neutron$ git diff
diff --git a/debian/control b/debian/control
index f25fd6f9ea..3f65330fd2 100644
--- a/debian/control
+++ b/debian/control
@@ -13,6 +13,7 @@ Build-Depends:
python3-all,
python3-pbr (>= 4.0.0),
python3-setuptools,
+ python-weakrefmethod,
Build-Depends-Indep:
crudini,
python3-alembic (>= 0.8.10),
通过debuild调试上速问题的测试环境快速搭建：
sudo cp /etc/schroot/chroot.d/sbuild-bionic-train-amd64 /etc/schroot/chroot.d/sbuild-bionic-train-amd64-tmp
sudo cp -r /var/lib/schroot/chroots/bionic-train-amd64 /var/lib/schroot/chroots/bionic-train-amd64-tmp
sudo sed -i -e "s/bionic-train-amd64/bionic-train-amd64-tmp/g" /etc/schroot/chroot.d/sbuild-bionic-train-amd64-tmp
#sudo rm /etc/schroot/chroot.d/sbuild-bionic-train-amd64-tmp
#sudo rm -rf /var/lib/schroot/chroots/bionic-train-amd64-tmp
schroot -l
schroot -c source:bionic-train-amd64-tmp -u root
chmod 1777 /tmp
apt install git vim wget devscripts equivs -y
git clone https://github.com/zhhuabj/neutron.git && cd neutron
git bisect start
git bisect good 15.3.4
git bisect bad 16.0.0
git checkout -b 15.3.5
git checkout -b debian/15.3.5
wget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/train-staging/+sourcefiles/neutron/2:15.3.4-0ubuntu1~cloud1/neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
tar -xf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
rm -rf neutron_15.3.4-0ubuntu1~cloud1.debian.tar.xz
# mkdir /home/hua
#git config --global user.email "you@example.com"
#git config --global user.name "Your Name"
git add debian/ && git commit -m 'add debian'
dch -i
#neutron (2:15.3.5-0ubuntu1~cloud0) bionic-train; urgency=medium
git commit -m "releasing package 2:15.3.5-0ubuntu1~cloud0" debian/changelog
cp -r debian/patches/ /tmp/
rm -rf debian/patches/* && touch debian/patches/series
git add -u && debcommit -m 'delete series'
git checkout 15.3.5 && git tag --no-sign 15.3.5 -m "15.3.5"
git checkout debian/15.3.5 && git tag --no-sign debian/15.3.5 -m "debian/15.3.5"
git checkout 15.3.5
git archive --format=tar HEAD |gzip > ../neutron_15.3.5.orig.tar.gz
git checkout debian/15.3.5
mk-build-deps --install debian/control
rm -rf ../neutron_15.3.5-0ubuntu1~cloud0* && rm -rf .stestr
debuild -i -us -uc
有很多种方式有可以很轻易重现上面问题：
一种是直接运行’stestr run --subunit’，不清楚要不要运行’tox -e cover’（运行这句也hang在那）
stestr取代了testrepository - https://storyboard.openstack.org/#!/story/1666232
# https://github.com/mtreinish/stestr/
apt install python-tox python3-stestr python3-mock -y
#tox -e cover
stestr run --subunit
二是直接运行debian/rules build：
debian/rules clean && debian/rules build
三是运行’pkgos-dh_auto_test --no-py2’：
ls build/lib.linux-x86_64-2.7/neutron/
cat /usr/share/openstack-pkg-tools/pkgos.make
pkgos-dh_auto_test --no-py2
vim debian/rules
ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS)))
override_dh_auto_test:
pkgos-dh_auto_test --no-py2
endif
所以最后通过‘DEB_BUILD_OPTIONS=nocheck’（不再运行unit test)来bypass了上述错误
echo 'DEBOOTSTRAP_PROXY=http://t440p:3142/' >> ~/.mk-sbuild.rc
gbp buildpackage --git-pristine-tar --git-pristine-tar-commit --git-upstream-tag='%(version)s' --git-debian-branch=debian/15.3.5 --git-ignore-branch --git-ignore-new --git-builder='DEB_BUILD_OPTIONS=nocheck sbuild -As -d bionic-train-amd64' -j8
20220505 - one sru example
sudo apt install pbuilder debootstrap devscripts -y
sudo apt install gnupg ubuntu-dev-tools bzr-builddeb apt-file debhelper openstack-pkg-tools -y
sudo apt install build-essential quilt dh-autoreconf fakeroot dpkg-dev python3-sphinx dh-make -y
sudo apt install python2 dh-python python-all python-setuptools -y
sudo apt install apt-cacher-ng -y
echo 'Acquire::http::Proxy "http://127.0.0.1:3142";' | sudo tee /etc/apt/apt.conf.d/01acng
# sometimes base.tgz can't be generated when using /etc/pbuilderrc
#sudo mv /etc/pbuilderrc /etc/pbuilderrc_bak
sudo pbuilder --create --distribution bionic --architecture amd64 --debootstrapopts --variant=buildd
sudo cp /var/cache/pbuilder/base.tgz /var/cache/pbuilder/bionic-base.tgz
# need to use '--basetgz' when using no pbuilderrc
sudo pbuilder update --basetgz /var/cache/pbuilder/bionic-base.tgz
#chroot to image to ajust what you want
sudo pbuilder login --save-after-login --basetgz /var/cache/pbuilder/bionic-base.tgz
echo 'precedence ::ffff:0:0/96 100' >> /etc/gai.conf
apt install software-properties-common dirmngr vim ca-certificates ubuntu-cloud-keyring apt-transport-https -y
vim /etc/apt/sources.list.d/cloudarchive-xena.list
deb http://ubuntu-cloud.archive.canonical.com/ubuntu boinic-updates/queens main
deb-src http://ubuntu-cloud.archive.canonical.com/ubuntu boinic-updates/queens main
#apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5EDB1B62EC4926EA
sed -i -e "s/#deb-src/deb-src/" /etc/apt/sources.list
apt update
# then press ctrl-d to save and exit chroot
# but pdebuild needs pbuilderrc
cat <<EOF | sudo tee /etc/pbuilderrc
MIRRORSITE=http://archive.ubuntu.com/ubuntu/
DEBFULLNAME='Zhang Hua'
DEBEMAIL='xxx@xxx.com'
DISTRIBUTION='focal'
EXTRAPACKAGES=''
EXTRAPACKAGES+=' vim sudo bash-completion wget git build-essential apt-transport-https ca-certificates ubuntu-cloud-keyring'
# Cloud Archive
OS_RELEASE='xena'
if [ -n "\$OS_RELEASE" ]; then
BASETGZ="/var/cache/pbuilder/\$DISTRIBUTION-\$OS_RELEASE-base.tgz"
else
BASETGZ="/var/cache/pbuilder/\$DISTRIBUTION-base.tgz"
fi
EOF
sudo pbuilder update --basetgz /var/cache/pbuilder/focal-xena-base.tgz
cmadison neutron
rmadison neutron
mkdir -p /bak/work/sru/neutron/19.1.0 && cd /bak/work/sru/neutron/19.1.0
#UCA - https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/xena-staging
#UA - https://launchpad.net/ubuntu/+source/neutron
wget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/xena-staging/+sourcefiles/neutron/2:19.1.0-0ubuntu2~cloud0/neutron_19.1.0-0ubuntu2~cloud0.debian.tar.xz
wget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/xena-staging/+sourcefiles/neutron/2:19.1.0-0ubuntu2~cloud0/neutron_19.1.0-0ubuntu2~cloud0.dsc
wget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/xena-staging/+sourcefiles/neutron/2:19.1.0-0ubuntu2~cloud0/neutron_19.1.0.orig.tar.gz
dpkg-source -x neutron_19.1.0-0ubuntu2~cloud0.dsc
cd neutron-19.1.0/
sudo apt install devscripts equivs -y
sudo pdebuild --debug
#sudo pdebuild --debbuildopts -sa #when hitting 'Unable to find xxx.orig.tar.gz in upload or distribution'
#DEB_BUILD_OPTIONS=nocheck debuild -us -uc
#sudo mk-build-deps --install debian/control
#dpkg-source: error: aborting due to unexpected upstream changes
#rm -rf debian/source/fomat
cd /bak/openstack/neutron
#tox -epy38 neutron.tests.unit.agent.linux.test_dhcp.TestDeviceManager.test_setup_reserved_with_isolated_metadata_enable
git checkout 19.1.0
git cherry-pick -s -x 8a890ed29c681847d930bdf5403926c2e1450f9d
git format-patch -1 7932b9099b941e601de3245d0733547f85b7b047
export DEBEMAIL="xxx@xx.com"
export DEBFULLNAME="Zhang Hua"
export QUILT_NO_DIFF_TIMESTAMPS=1
export QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
export QUILT_PATCHES=debian/patches
export QUILT_NO_DIFF_INDEX=1
cp /bak/openstack/neutron/0001-Fix-list-of-DNS-extensions-supported-by-OVN.patch debian/patches/
echo '0001-Fix-list-of-DNS-extensions-supported-by-OVN.patch' >> debian/patches/series
quilt push -a
quilt refresh
dch -i
#dch -e
# for UCA, it's focal not focal-xena, Unable to find distroseries: focal-xena
neutron (2:19.1.0-0ubuntu2~cloud1) focal; urgency=medium
* d/0001-Fix-list-of-DNS-extensions-supported-by-OVN.patch
fix list of dns extensions supported by OVN (LP: #1947127)
#sudo pdebuild
#sudo pdebuild --debbuildopts -sa # sometimes need to include source code for uca
# do not run unit test to avoid override_dh_auto_test error
sudo DEB_BUILD_OPTIONS="nocheck" pdebuild --debug
cd ..
debdiff neutron_19.1.0-0ubuntu2~cloud0.dsc neutron_19.1.0-0ubuntu2~cloud1.dsc > focal-xena.debdiff
debsign neutron_19.1.0-0ubuntu2~cloud0_source.changes -k$GPGKEY
debsign neutron_19.1.0-0ubuntu2~cloud1_source.changes -k$GPGKEY
#create test ppa with PPA dependency xena-staging - https://launchpad.net/~zhhuabj/+archive/ubuntu/focal-xena-testing
# use '--unchecked' to avoid: Error checking signature from xxx: SignatureVerifyError: 0
dput --unchecked -f ppa:zhhuabj/focal-xena-testing neutron_19.1.0-0ubuntu2~cloud1_source.changes
#SRU - https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template , and remember to add '[SRU] prefix for the title
#for UA SRU: subscribe ubuntu-sponsors team, add sts-sru-needed and sts-sponsor tag
#for UCA SRU: add sts sts-sru-needed
#We add 'Ubuntu Cloud Archive' project ourselves for upstream stable/xena fix, but we don't have permission to add 'Xena' project
20220627更新
运行’sudo pdebuild’时报下列错误：
dh_clean: error: Compatibility levels before 7 are no longer supported (level 5 requested)
本来下面命令就能解决：
echo '10' > debian/compat
但是我画蛇添足了，运行了这个命令：sudo mk-build-deps --install debian/control ， 导致在源码目录添加了一个文件，这样报：binary file contents changed
20240325 - Use debuild
用了快十年的pbuilder了，今天再用pbuilder时居然报了下列错(这个错应该在用noble时失败，但是镜像使用noble, 在noble host上用jammy镜像也会有这个问题):
Failed to import test module: neutron.tests.unit
import eventlet
File "/usr/lib/python3/dist-packages/eventlet/__init__.py", line 17, in <module>
from eventlet import convenience
File "/usr/lib/python3/dist-packages/eventlet/convenience.py", line 7, in <module>
from eventlet.green import socket
File "/usr/lib/python3/dist-packages/eventlet/green/socket.py", line 21, in <module>
from eventlet.support import greendns
File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 411, in <module>
resolver = ResolverProxy(hosts_resolver=HostsResolver())
File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 328, in clear
self._resolver = dns.resolver.Resolver(filename=self._filename)
File "/usr/lib/python3/dist-packages/dns/resolver.py", line 734, in __init__
self.read_resolv_conf(filename)
File "/usr/lib/python3/dist-packages/dns/resolver.py", line 826, in read_resolv_conf
raise NoResolverConfiguration
dns.resolver.NoResolverConfiguration: Resolver configuration could not be read or specified no nameservers
#一个workaround就是运行'sudo pbuilder login --save-after-login'直接修改镜像(先安装：apt install python3 python3-eventlet -y， 然后修改/usr/lib/python3/dist-packages/dns/resolver.py去掉NoResolverConfiguration
实在搞不清楚什么原因。时间有限，只能继续探索如何在pbuilder提供的focal镜像上直接运行debuild.
sudo cp /var/cache/pbuilder/focal-yoga-base.tgz /var/cache/pbuilder/focal-yoga-base.tgz_bak
sudo pbuilder login --save-after-login
#UCA - https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/yoga-staging
#UA - https://launchpad.net/ubuntu/+source/neutron
# cat /etc/apt/sources.list |tail -n2
deb http://ubuntu-cloud.archive.canonical.com/ubuntu focal-updates/yoga main
deb-src http://ubuntu-cloud.archive.canonical.com/ubuntu focal-updates/yoga main
apt install devscripts curl ca-certificates bash-completion equivs dput -y
dget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/yoga-staging/+sourcefiles/neutron/2:20.5.0-0ubuntu1~cloud0/neutron_20.5.0-0ubuntu1~cloud0.dsc
dpkg-source -x neutron_20.5.0-0ubuntu1~cloud0.dsc
cd neutron-20.5.0/
# 不能运行mk-build-deps，否则会报包已经被修改
#debian/source/include-binaries if you want to store the modified binary in the debian tarball, that's because we run: mk-build-deps --install debian/control
#mk-build-deps --install debian/control
apt build-dep neutron
apt install openssh-client -y
ssh-keygen #then copy the public key to ~/.ssh/authorized_keys of minipc (192.168.99.179)
vim /etc/ssh/ssh_config
KexAlgorithms +diffie-hellman-group1-sha1
HostkeyAlgorithms +ssh-dss,ssh-rsa
PubkeyAcceptedKeyTypes +ssh-dss,ssh-rsa
ForwardX11 yes
scp -r hua@192.168.99.179:/home/hua/mygpgkey* ~/
sudo apt-get install rng-tools gnupg-agent -y && sudo rngd -r /dev/urandom && killall -q gpg-agent && eval $(gpg-agent --daemon)
gpg --import ~/mygpgkey_pub.gpg
gpg --allow-secret-key-import --import ~/mygpgkey_sec.gpg
gpg --list-public
gpg --list-sig
export GPGKEY=C7100A4CD0D8F3AE44212746E6A84FFFCF31A67F
gpg --send-keys --keyserver keyserver.ubuntu.com $GPGKEY
debuild -sa -S -k$GPGKEY
scp -r hua@192.168.99.179:/bak/work/sru/neutron/focal-yoga/neutron-20.5.0/debian/patches/0001-* debian/patches/
scp -r hua@192.168.99.179:/bak/work/sru/neutron/focal-yoga/neutron-20.5.0/debian/changelog debian/ #dch -i
sudo apt install quilt devscripts dh-make -y
export QUILT_PATCHES=debian/patches
export QUILT_NO_DIFF_INDEX=1
export QUILT_NO_DIFF_TIMESTAMPS=1
export QUILT_REFRESH_ARGS="-p ab"
export QUILT_PATCHES=debian/patches
export QUILT_REFRESH_ARGS="-p ab --no-timestamps --no-index"
# 注意，用debuild时不能使用quilt命令来更新debian包，否则运行运行debuild时会说包已经被修改
quilt pop -a && quilt push -a && quilt refresh
debuild -sa -S -k$GPGKEY
cd ..
debdiff neutron_20.5.0-0ubuntu1~cloud0.dsc neutron_20.5.0-0ubuntu1+test1.dsc > focal-yoga.debdiff
# https://launchpad.net/~zhhuabj/+archive/ubuntu/focal-yoga-test
dput ppa:zhhuabj/focal-yoga-test neutron_20.5.0-0ubuntu1+test1_source.changes
但是又报了下列错（Network is unreachable)： https://launchpadlibrarian.net/721082750/buildlog_ubuntu-focal-amd64.neutron_2%3A20.5.0-0ubuntu1+test1_BUILDING.txt.gz
Err:260 http://ppa.launchpadcontent.net/ubuntu-cloud-archive/yoga-staging/ubuntu focal/main amd64 python3-importlib-metadata all 4.6.4-1~cloud0
Cannot initiate the connection to ppa.launchpadcontent.net:80 (2620:2d:4000:1::81). - connect (101: Network is unreachable)
既然ppa不work(其实lp界面上retrigger一下re-build一下即可），那就本地生成binary测试吧：
debuild -b -k$GPGKEY
debuild -us -uc -b #don't use GPGKEY
DEB_BUILD_OPTIONS=nocheck debuild -us -uc -b #don't run unit test
20240326更新 - Use sbuild
这次pbuilder不work的原因可能是因为它（https://github.com/eventlet/eventlet/issues/736），python3-evenlet有bug导致pbuilder里的容器运行用到python3-eventlet时报了NoResolverConfiguration这个错，实在解决不了，改用debuild或sbuild解决。
1, 修改~/.sbuildrc中的distribution到相应的版本如focal
2, 生成focal-yoga镜像
#mk-sbuild focal --arch=amd64 --skip-updates
sudo cp /etc/schroot/chroot.d/sbuild-focal-amd64 /etc/schroot/chroot.d/sbuild-focal-yoga-amd64
sudo cp -r /var/lib/schroot/chroots/focal-amd64 /var/lib/schroot/chroots/focal-yoga-amd64
sudo sed -i -e "s/focal-amd64/focal-yoga-amd64/g" /etc/schroot/chroot.d/sbuild-focal-yoga-amd64
#sudo rm /etc/schroot/chroot.d/sbuild-focal-yoga-amd64
#sudo rm -rf /var/lib/schroot/chroots/focal-yoga-amd64
schroot -l
#add UCA yoga
schroot -c source:focal-yoga-amd64 -u root
apt install vim -y
chmod 1777 /tmp/ && chmod 1777 /dev/null
vim /etc/apt/sources.list
deb http://ubuntu-cloud.archive.canonical.com/ubuntu focal-updates/yoga main
deb-src http://ubuntu-cloud.archive.canonical.com/ubuntu focal-updates/yoga main
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5EDB1B62EC4926EA
apt update
#press ctrl +d to exit
3, 在minipc上下载代码
#modify debian source code
#UCA - https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/yoga-staging
#UA - https://launchpad.net/ubuntu/+source/neutron
dget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/yoga-staging/+sourcefiles/neutron/2:20.5.0-0ubuntu1~cloud0/neutron_20.5.0-0ubuntu1~cloud0.dsc
dpkg-source -x neutron_20.5.0-0ubuntu1~cloud0.dsc
#modify source code here
dch -i
#注意这里不要运行quilt等修改源码的命令，否则下面dpkg-source -b . 命令会出错
dpkg-source -b . #generate new dsc, eg: neutron_20.5.0-0ubuntu1+test3.dsc
debdiff neutron_20.5.0-0ubuntu1~cloud0.dsc neutron_20.5.0-0ubuntu1+test3.dsc > focal-yoga.debdiff
4, 在minipc上build dsc，然后在ppa上测试
schroot -l
sbuild-update -udc focal-yoga-amd64
cd ..
#注意，下面的sbuild中的-d不应该加-amd64后缀否则在dput时总是说‘Unable to find distroseries: mantic-amd64’，
#但去掉了-amd64现在又说‘multiple stanzas where only one is expected’
#sbuild --verbose -d focal-yoga-amd64 --arch-all ./neutron_20.5.0-0ubuntu1+test3.dsc
#DEB_BUILD_OPTIONS=nocheck sbuild --verbose -d focal-yoga-amd64 -As ./neutron_20.5.0-0ubuntu1+test3.dsc -j8
DEB_BUILD_OPTIONS=nocheck sbuild --verbose -d focal-yoga -As ./neutron_20.5.0-0ubuntu1+test3.dsc -j8
debsign neutron_20.5.0-0ubuntu1+test3.dsc -k$GPGKEY
#dput时如果出现‘Unable to find distroseries: mantic-amd64', 在dch时应该使用了'mantic-updates'还是出错
dput ppa:zhhuabj/focal-yoga-test <source.changes>
上面用sbuild总是报下列错：
- ‘DEB_BUILD_OPTIONS=nocheck sbuild --verbose -d noble-amd64 -As ./horizon_23.3.0-0ubuntu1.2.dsc -j8’ cause the error ‘multiple stanzas where only one is expected’
- ‘DEB_BUILD_OPTIONS=nochecksbuild --verbose -d noble -As ./horizon_23.3.0-0ubuntu1.2.dsc -j8’ cause the error ‘Unable to find distroseries: noble-amd64’
所以最后还是创建了一个noble虚机改为debuild测试也报了这个错（multiple stanzas where only one is expected），但同事说成功了：
apt-get source horizon
cd horizon-24.0.0/
cp ../../0001-Fix-Users-Groups-tab-list-when-a-domain-context-is-s.patch debian/patches/
#modify debian/patches/series, and run 'dch -i' to always use eg:nobel for both UA and UCA
apt build-dep horzion
#debuild -sa -S -k$GPGKEY
DEB_BUILD_OPTIONS=nocheck debuild -us -uc
debsign horizon_24.0.0-0ubuntu2_amd64.changes -k$GPGKEY
dput ppa:zhhuabj/noble-sru-test horizon_24.0.0-0ubuntu2_amd64.changes
然后又试了下面的dpkg-buildpackage (https://bugs.launchpad.net/launchpad/+bug/2003070), 要不收不到邮件要不收到邮件说‘horizon_24.0.0-0ubuntu2_source.buildinfo: E:Unable to parse package file’。
dpkg-buildpackage --build=source -sa -k$GPGKEY
ppa总是这么多奇怪的事情，不用ppa，直接本地生成测试包测试吧：
DEB_BUILD_OPTIONS=nocheck debuild -us -uc -b #don't run unit test
20240326 - Fix BADSIG gpg error
今天总是遇到下列错误：
The following signatures were invalid: BADSIG 5EDB1B62EC4926EA Canonical Cloud Archive Signing Key <ftpmaster@canonical.com>
即使运行了下列错误还是如此：
apt-key adv --keyserver keyserver.ubuntu.com --keyserver-options http-proxy=http://192.168.99.186:3129 --recv-keys 5EDB1B62EC4926EA
最后发现居然是因为用了apt-cacher-ng的原因, source.list中修改url后要重置apt-cache-ngn缓存
此篇文章（解决apt-get BADSIG GPG错误的最简单方法是什么？ - https://ubuntuqa.com/article/413.html）也提到了apt-cacher-ng的原因:
sudo systemctl stop apt-cacher-ng
#sudo rm -rf /var/lib/apt/*
#sudo rm -rf /var/cache/apt/*
sudo rm -rf /var/cache/apt-cacher-ng/
sudo mkdir -p /var/cache/apt-cacher-ng/{headers,import,packages,private,temp}
sudo chown apt-cacher-ng:apt-cacher-ng -R /var/cache/apt-cacher-ng
sudo systemctl start apt-cacher-ng
sudo systemctl status apt-cacher-ng
20240429 - SRU
例如：https://bugs.launchpad.net/cloud-archive/+bug/2054799
客户在使用jammy, patch已经进了upstream master
1, 根据 https://releases.openstack.org/ 将代码cherry-pick到了2024.1(caracal, 14.0.0 - https://releases.openstack.org/caracal/ ), 2023.2(bobcat, 13.0.0), 2023.1(antelope, 12.0.0), zed(还有5天进入unmainained所以提了patch也被abandoned了), yoga(已经进入unmaintained了就不弄了)。虽然代码只进了2024.1与2023.2, 代码还没进2023.1，但也可以开始SRU了
2, 填写SRU模板时，若没有reproudcer, 要将这个测试结果写在[Test Case]中 - https://github.com/openstack-charmers/charmed-openstack-tester
3, 要先弄Oracular(ubuntu 24.10) development, 才能弄stable UA. 如下命名规则:(https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging)似乎有些变化，noble是1:14.0.0-0ubuntu1, oracluar是1:14.0.0-0ubuntu2, 所以noble再往上的不应该是1:14.0.0-0ubuntu2而是1:14.0.0-0ubuntu1.1 . 并且oracular development debdiff也要弄 (team没权限上传，openstack team有权取，之前是team内的其他人提供了debdiff，总得有人弄)
$ rmadison -a source octavia
octavia | 1:14.0.0-0ubuntu1 | noble/universe | source
octavia | 1:14.0.0-0ubuntu1.1 | noble-proposed/universe | source
octavia | 1:14.0.0-0ubuntu2 | oracular/universe | source
4, stable UA不要根据（https://ubuntu.com/about/release-cycle#openstack-release-cycle，它有时没更新）而要根据(rmadison openstack-dashboard)并结合（https://ubuntu.com/about/release-cycle#ubuntu）来判断需要为noble, mantic, jammy三个release依顺序做UA， 故要上传这3个的debdiff
$ rmadison openstack-dashboard
...
openstack-dashboard | 4:22.1.0-0ubuntu2 | jammy | all
openstack-dashboard | 4:22.1.1-0ubuntu1 | jammy-updates | all
openstack-dashboard | 4:23.3.0-0ubuntu1 | mantic | all
openstack-dashboard | 4:23.3.0-0ubuntu1.1 | mantic-updates | all
openstack-dashboard | 4:24.0.0-0ubuntu1 | noble | all
mantic若已经EOL的话就不做了，因为没有mantic UA了所以要做UCA (jammy-bobcat)但jammy-bobcat可能也EOL了。 通过dget
5, 对于UCA，如已经做了jammy UA，那就不需再做focal-yoga UCA了。如已经做了noble UA, 也不需要再做jammy-caracal了。( This debdiffs build directly on the automatically generated backport changelog entry from when these cloud archive series still had an ubuntu parent)。 其他的UCA应该是看用户用了选择地做.
6, 先做debdiff (下载源码： dget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/octavia/1:14.0.0-0ubuntu1/octavia_14.0.0-0ubuntu1.dsc’ ( https://launchpad.net/ubuntu/+source/octavia) ) 另外，patch name的命名不要以默认的0001前缀， changelog形如： d/p/add-check-for-duplicate-members-in-batch-update.patch (LP: #2067441)
7, 现在不用debdiff了，需要提PR - https://code.launchpad.net/~ubuntu-openstack-dev/ubuntu/+source/octavia
一个例子： https://code.launchpad.net/~zhhuabj/ubuntu/+source/octavia/+git/octavia/+merge/471140
8, 见： https://bugs.launchpad.net/octavia/+bug/2067441/comments/12
9, 记得设置tag, 同时将se-sponsor添加至邮件列表(for both UA and UCA)
10, 究竟哪些要做SRU, 例 （也可以参考这个： https://bugs.launchpad.net/octavia/+bug/2067441/comments/17 )：
#2024.1(caracal, 14.0.0 - https://releases.openstack.org/caracal/ ), 2023.2(bobcat, 13.0.0), 2023.1(antelope, 12.0.0)
1, development/oracular 1:14.0.0-0ubuntu2 1:14.0.0-0ubuntu2.1
2, UA noble 1:14.0.0-0ubuntu1.1 1:14.0.0-0ubuntu1.2
3, remove UA mantic (mantic has been EOL)
4, UA jammy 1:10.1.1-0ubuntu1 1:10.1.1-0ubuntu2 1:10.1.1-0ubuntu1.1 ?
5, UCA jammy-
no UCA jammy-caracal due to UA noble
no UCA jammy-bobcat due to the absence of UA mantic (but jammy-bobcat has been EOL as well)
need UCA jammy-antelope
no UCA focal-yoga (due to UA jammy)
$ rmadison -a source octavia
octavia | 6.0.0~b3~git2020041014.771a5d87-0ubuntu1 | focal/universe | source
octavia | 6.2.2-0ubuntu1.1 | focal-updates/universe | source
octavia | 1:10.0.0-0ubuntu1 | jammy/universe | source
octavia | 1:10.1.1-0ubuntu1 | jammy-updates/universe | source
octavia | 1:14.0.0-0ubuntu1 | noble/universe | source
octavia | 1:14.0.0-0ubuntu1.1 | noble-proposed/universe | source
octavia | 1:14.0.0-0ubuntu2 | oracular/universe | source
$ cmadison octavia
octavia | 1:12.0.0-0ubuntu1~cloud0 | antelope | jammy-updates | source
octavia | 1:12.0.0-0ubuntu1~cloud0 | antelope-proposed | jammy-proposed | source
octavia | 1:13.0.0-0ubuntu1~cloud0 | bobcat | jammy-updates | source
octavia | 1:13.0.0-0ubuntu1~cloud0 | bobcat-proposed | jammy-proposed | source
octavia | 1:14.0.0-0ubuntu1~cloud0 | caracal | jammy-updates | source
octavia | 1:14.0.0-0ubuntu1.1~cloud0 | caracal-proposed | jammy-proposed | source
octavia | 4.1.4-0ubuntu1~cloud0 | stein | bionic-updates | source
octavia | 4.1.4-0ubuntu1~cloud0 | stein-proposed | bionic-proposed | source
octavia | 5.1.2-0ubuntu1~cloud0 | train | bionic-updates | source
octavia | 5.1.2-0ubuntu1~cloud0 | train-proposed | bionic-proposed | source
octavia | 6.2.2-0ubuntu1~cloud1 | ussuri | bionic-updates | source
octavia | 6.2.2-0ubuntu1.1~cloud0 | ussuri-proposed | bionic-proposed | source
octavia | 7.1.2-0ubuntu1~cloud1 | victoria | focal-updates | source
octavia | 7.1.2-0ubuntu1~cloud1 | victoria-proposed | focal-proposed | source
octavia | 1:8.0.1-0ubuntu1~cloud1 | wallaby | focal-updates | source
octavia | 1:8.0.1-0ubuntu1~cloud1 | wallaby-proposed | focal-proposed | source
octavia | 1:9.1.0-0ubuntu1~cloud0 | xena | focal-updates | source
octavia | 1:9.1.0-0ubuntu1~cloud0 | xena-proposed | focal-proposed | source
octavia | 1:10.1.1-0ubuntu1~cloud0 | yoga | focal-updates | source
octavia | 1:10.1.1-0ubuntu1~cloud0 | yoga-proposed | focal-proposed | source
octavia | 1:11.0.1-0ubuntu1~cloud0 | zed | jammy-updates | source
octavia | 1:11.0.1-0ubuntu1~cloud0 | zed-proposed | jammy-proposed | source
具体步骤如下：
#build debdiff first
export QUILT_PATCHES=debian/patches
export QUILT_NO_DIFF_INDEX=1
export QUILT_NO_DIFF_TIMESTAMPS=1
export QUILT_REFRESH_ARGS="-p ab"
export QUILT_REFRESH_ARGS="-p ab --no-timestamps --no-index"
export QUILT_DIFF_ARGS="--color=auto" # If you want some color when using `quilt diff`.
export QUILT_PATCH_OPTS="--reject-format=unified"
export QUILT_COLORS="diff_hdr=1;32:diff_add=1;34:diff_rem=1;31:diff_hunk=1;33:diff_ctx=35:diff_cctx=33"
sudo vim /etc/pbuilderrc
sudo pbuilder update
#UCA - https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/yoga-staging
#UA - https://launchpad.net/ubuntu/+source/octavia
dget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/octavia/1:14.0.0-0ubuntu2/octavia_14.0.0-0ubuntu2.dsc
cd octavia-14.0.0/
cp ../0001-Add-check-for-duplicate-members-in-batch-update.patch debian/patches/add-check-for-duplicate-members-in-batch-update.patch
echo "add-check-for-duplicate-members-in-batch-update.patch" >> debian/patches/series
quilt pop -a
quilt push -a
dch -i
$ cat debian/changelog |head -n3
octavia (1:14.0.0-0ubuntu2.1) oracular; urgency=medium
* d/p/add-check-for-duplicate-members-in-batch-update.patch (LP: #2067441)
sudo pdebuild --debug
debsign octavia_14.0.0-0ubuntu2.1.dsc -k$GPGKEY
debdiff octavia_14.0.0-0ubuntu2.dsc octavia_14.0.0-0ubuntu2.1.dsc > oracular.debdiff
#build PR, oracular is development branch rather than stable branch so use master branch
git clone https://git.launchpad.net/~ubuntu-openstack-dev/ubuntu/+source/octavia
git checkout -b oracular_dev origin/master
patch -p1 < /bak/work/sru/octavia/oracular/oracular.debdiff
#Do not modify the changelog - instead put your changelog message in the commit message.
#This will help manage concurrent submissions to the same package
cat debian/changelog |head -n5
git checkout debian/changelog
git add debian/patches/add-check-for-duplicate-members-in-batch-update.patch
git add -u
git commit
#d/p/add-check-for-duplicate-members-in-batch-update.patch (LP: #2067441)
git remote set-url --push origin no_push
git remote add zhhuabj git+ssh://zhhuabj@git.launchpad.net/~zhhuabj/ubuntu/+source/octavia
git remote -v
git push --set-upstream zhhuabj oracular_dev
#PR (merged into ubuntu/+source/octavia:ubuntu/devel) - https://code.launchpad.net/~zhhuabj/ubuntu/+source/octavia/+git/octavia/+ref/oracular_dev/+register-merge
#for development branch (eg: Oracular) ubuntu-openstack-dev/octavia/master ~ubuntu-openstack-dev/ubuntu/+source/octavia:master
#for stable branch first select repo (~ubuntu-openstack-dev/ubuntu/+source/octavia ), then select branch eg: (stable/2023.2), the full path is: ~ubuntu-openstack-dev/ubuntu/+source/octavia:stable/2023.2
#https://code.launchpad.net/~zhhuabj/ubuntu/+source/octavia/+git/octavia/+merge/471140
#做完了development branch, 然后依此做什么stable branch的PR
20241021 - 究意哪些需要做SRU
以https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/2017748 为例:
1, UA, 根据ubuntu release page (https://ubuntu.com/about/release-cycle)得知>=focal需要做UA SRU, 再根据'rmadison -a source neutron'的输出需要做:
development/plucky(25.04) - 2:25.0.0-0ubuntu1 -> 2:25.0.0-0ubuntu2
UA oracular(24.10) - 2:25.0.0-0ubuntu1 -> 2:25.0.0-0ubuntu1.1
UA noble(24.04) - 2:24.0.0-0ubuntu1 -> 2:24.0.0-0ubuntu2
UA jammy(22.04) - 2:20.5.0-0ubuntu1 -> 2:20.5.0-0ubuntu2
UA focal(20.04) - 2:16.4.2-0ubuntu6.4 -> 2:16.4.2-0ubuntu6.5
$ rmadison -a source neutron
...
neutron | 2:16.0.0~b3~git2020041516.5f42488a9a-0ubuntu2 | focal | source
neutron | 2:16.4.2-0ubuntu6.2 | focal-security | source
neutron | 2:16.4.2-0ubuntu6.4 | focal-updates | source
neutron | 2:20.0.0-0ubuntu3 | jammy | source
neutron | 2:20.3.0-0ubuntu1.1 | jammy-security | source
neutron | 2:20.5.0-0ubuntu1 | jammy-updates | source
neutron | 2:24.0.0-0ubuntu1 | noble | source
neutron | 2:25.0.0-0ubuntu1 | oracular | source
neutron | 2:25.0.0-0ubuntu1 | plucky | source
2, UCA, 以'cmadison neutron'的信息为主再结合ubuntu openstack release page (https://ubuntu.com/about/release-cycle#openstack-release-cycle)知道需要做:
epoxy (2025.1, 25.0.0) - jammy-epoxy (no need, it's in oracular/UA and plucky/development)
dalmatian(2024.2, 25.0.0) - jammy-dalmatian (no need, it's in oracular/UA and plucky/development)
caracal (2024.1, 24.0.0) - jammy-caracal (no need, it's in noble/UA)
bobcat (2023.2, 23.1.0) - jammy-bobcat
antelope (2023.1, 22.1.0) - jammy-antelope
yoga (20.5.0) - focal-yoga (no need, it's in jammy/UA)
ussuri (16.4.2) - bionic-ussuri (no need, bionic is EOL)
$ cmadison neutron
...
neutron | 2:22.1.0-0ubuntu1~cloud0 | antelope | jammy-updates | source
neutron | 2:22.1.0-0ubuntu1~cloud0 | antelope-proposed | jammy-proposed | source
neutron | 2:23.1.0-0ubuntu1~cloud0 | bobcat | jammy-updates | source
neutron | 2:23.1.0-0ubuntu1~cloud0 | bobcat-proposed | jammy-proposed | source
neutron | 2:24.0.0-0ubuntu1~cloud0 | caracal | jammy-updates | source
neutron | 2:24.0.0-0ubuntu1~cloud0 | caracal-proposed | jammy-proposed | source
neutron | 2:25.0.0-0ubuntu1~cloud0 | dalmatian | noble-updates | source
neutron | 2:25.0.0-0ubuntu1~cloud0 | dalmatian-proposed | noble-proposed | source
neutron | 2:25.0.0-0ubuntu1~cloud0 | epoxy | noble-updates | source
neutron | 2:25.0.0-0ubuntu1~cloud0 | epoxy-proposed | noble-proposed | source
neutron | 2:20.5.0-0ubuntu1~cloud0 | yoga | focal-updates | source
neutron | 2:20.5.0-0ubuntu1~cloud0 | yoga-proposed | focal-proposed | source
20241021 - pbuilder中的包依赖问题
问题运行pdebuild时报包依赖问题，如(python3-pyroute2 (>= 0.6.4-3ubuntu1~) but 0.6.4-3 is to be installed), 那是因为镜像中的sources.list中没有添加-updates slot
root@minipc:/# cat /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu/ jammy main universe
deb http://archive.ubuntu.com/ubuntu/ jammy-updates main universe
20241022 - dput ppa中的MD5 mismatch问题
使用下面的pbuilder命令后dput ppa时总会报MD5 mismatch
dget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/neutron/2:20.5.0-0ubuntu1/neutron_20.5.0-0ubuntu1.dsc
dpkg-source -x neutron_20.5.0-0ubuntu1.dsc
cd neutron-20.5.0
quilt import /root/handle-creation-of-Port_Binding-with-chassis-set.patch
quilt pop -a && quilt push -a && quilt refresh
dch -i #d/p/handle-creation-of-Port_Binding-with-chassis-set.patch (LP: #2017748)
DEB_BUILD_OPTIONS=nocheck pdebuild
debsign neutron_20.5.0-0ubuntu2_source.changes -k$GPGKEY
dput ppa:zhhuabj/jammy neutron_20.5.0-0ubuntu2_source.changes
一些数据：
$ md5sum neutron_20.5.0-0ubuntu1.debian.tar.xz
sha1sum neutron_20.5.0-0ubuntu1.debian.tar.xz
sha256sum neutron_20.5.0-0ubuntu1.debian.tar.xz
388f07e182252958046f9dec853d9646 neutron_20.5.0-0ubuntu1.debian.tar.xz
83e0c106e3ffa07c02396e6e501de30fdf999318 neutron_20.5.0-0ubuntu1.debian.tar.xz
5b7b5cafda2c985697330b4fd9255b03eb889cdc012080ebc62335f2fafe01ee neutron_20.5.0-0ubuntu1.debian.tar.xz
$ md5sum neutron_20.5.0-0ubuntu2.debian.tar.xz
sha1sum neutron_20.5.0-0ubuntu2.debian.tar.xz
sha256sum neutron_20.5.0-0ubuntu2.debian.tar.xz
0086a3d0633e28c0b48c61e92f050c4e neutron_20.5.0-0ubuntu2.debian.tar.xz
48351b7fcefa3582e29ee437df023aa28046db42 neutron_20.5.0-0ubuntu2.debian.tar.xz
7d34fc5a52542b74b6ce9b9ca88a8d39516863274abd4c4cdb1d49f1cec2e594 neutron_20.5.0-0ubuntu2.debian.tar.xz
$ grep -r 'neutron_20.5.0-0ubuntu2.debian.tar.xz' neutron_20.5.0-0ubuntu2_source.changes
48351b7fcefa3582e29ee437df023aa28046db42 30232 neutron_20.5.0-0ubuntu2.debian.tar.xz
7d34fc5a52542b74b6ce9b9ca88a8d39516863274abd4c4cdb1d49f1cec2e594 30232 neutron_20.5.0-0ubuntu2.debian.tar.xz
0086a3d0633e28c0b48c61e92f050c4e 30232 net optional neutron_20.5.0-0ubuntu2.debian.tar.xz
Rejected:
File neutron_20.5.0-0ubuntu2.debian.tar.xz mentioned in the changes has a MD5 mismatch. 3b174319fcf47f4be0feafce32d533ba != 0086a3d0633e28c0b48c61e92f050c4e
File neutron_20.5.0-0ubuntu2.debian.tar.xz mentioned in the changes has a MD5 mismatch. 3b174319fcf47f4be0feafce32d533ba != 0086a3d0633e28c0b48c61e92f050c4e
退回到使用debuild还是报同样的错:
注：20241210用下列同样的方法为neutron生成focal-yoga的测试包报这个错(nmet build dependencies: debhelper-compat (= 13)‘), 于是升级了debhelper到13(用的是proposed里的13)又报错个这个错（Marked by debhelper, will be an error in compat 13）， 原来是忘了运行’sudo add-apt-repository cloud-archive:yoga’和’sudo apt upgrade’ (debhelper要用yoga里的13而不是proposed里的13)
lxc launch jammy jammysru --profile default
lxc exec jammysru bash
lxc file push /tmp/handle-creation-of-Port_Binding-with-chassis-set.patch jammysru/root/
lxc file push ~/mygpgkey* jammysru/root/
sed -i 's/^#\s*deb-src/\deb-src/' /etc/apt/sources.list
#sudo systemctl stop apt-cacher-ng.service && sudo rm -rf /var/cache/apt-cacher-ng/* && sudo systemctl start apt-cacher-ng.service
echo 'Acquire::http::Proxy "http://minipc.lan:3142";' > /etc/apt/apt.conf.d/01acng
apt update
apt install devscripts curl ca-certificates bash-completion equivs dput quilt devscripts dh-make quilt -y
sudo apt-get install rng-tools gnupg-agent -y && sudo rngd -r /dev/urandom && killall -q gpg-agent && eval $(gpg-agent --daemon)
gpg --import /root/mygpgkey_pub.gpg
gpg --allow-secret-key-import --import /root/mygpgkey_sec.gpg
gpg --list-public
gpg --list-sig
cat << EOF |tee -a ~/.bashrc
export GPGKEY=C7100A4CD0D8F3AE44212746E6A84FFFCF31A67F
export DEBFULLNAME="Zhang Hua"
export DEBEMAIL="xxx@xxx.com"
export QUILT_PATCHES=debian/patches
export QUILT_NO_DIFF_INDEX=1
export QUILT_NO_DIFF_TIMESTAMPS=1
export QUILT_REFRESH_ARGS="-p ab"
export QUILT_PATCHES=debian/patches
export QUILT_REFRESH_ARGS="-p ab --no-timestamps --no-index"
EOF
source ~/.bashrc
dget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/neutron/2:20.5.0-0ubuntu1/neutron_20.5.0-0ubuntu1.dsc
dpkg-source -x neutron_20.5.0-0ubuntu1.dsc
cd neutron-20.5.0
apt build-dep neutron -y
quilt import /root/handle-creation-of-Port_Binding-with-chassis-set.patch
quilt pop -a && quilt push -a && quilt refresh
dch -i #d/p/handle-creation-of-Port_Binding-with-chassis-set.patch (LP: #2017748)
echo $GPGKEY
#debuild -sa -S -k$GPGKEY
debuild -S -k$GPGKEY
cd ..
dput ppa:zhhuabj/jammy neutron_20.5.0-0ubuntu2_source.changes
验证了gpg key, 问题应该和gpg无关:
echo 'test' >test.txt
#gpg --sign --clearsign -u $GPGKEY test.txt
gpg --output test.txt --sign --clearsign -u $GPGKEY test.txt
gpg --verify test.txt
重新生成了gpg key也还是相同的错，所以绝对和gpg应该无关：
#https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key
#the default type is ed25519, but lp only supports RSA, DSA, ECDSA, ECDH, and EdDSA
gpg --full-generate-key #select rsa 2048 type
#gpg --delete-secret-keys $GPGKEY
gpg --with-colons --list-secret-keys --keyid-format=long
export GPGKEY=AB55F121812DDE25DD8D98ECCED9779F08764073
#gpg --export --armor $GPGKEY > ~/mygpgkey_2024.asc && gpg --export-secret-keys --armor $GPGKEY >> ~/mygpgkey_2024.asc
#gpg --import ~/mygpgkey_2024.asc && gpg --list-keys && gpg --list-secret-keys
gpg --fingerprint $GPGKEY
gpg --send-keys --keyserver keyserver.ubuntu.com $GPGKEY
#then add gpg key fingerprint in lp - https://launchpad.net/~zhhuabj/+editpgpkeys
#then you will receive a mail, copy and paste the content 'BEGIN PGP MESSAGE' from email into /tmp/email.txt
gpg --decrypt /tmp/email.txt
总是报这个错, 明明md5sum是一样的(fad5b132556279d8300653c2011e756d)，但ppa那边传过来一个不知哪里冒出来的1732a7213644eab80b2f098367b40100：
#grep -r 'Files:' neutron_20.5.0-0ubuntu2_source.changes -A3
Files:
6c70533256bb3a70f6c7c9437831049f 5216 net optional neutron_20.5.0-0ubuntu2.dsc
fad5b132556279d8300653c2011e756d 30224 net optional neutron_20.5.0-0ubuntu2.debian.tar.xz
e97d45a0b6a5b8adaf7d9dfcc85ffe76 7373 net optional neutron_20.5.0-0ubuntu2_source.buildinfo
#md5sum neutron_20.5.0-0ubuntu2.debian.tar.xz
fad5b132556279d8300653c2011e756d neutron_20.5.0-0ubuntu2.debian.tar.xz
#上面neutron_20.5.0-0ubuntu2.debian.tar.xz的md5sum明明是相等的，报的下列错中的1732a7213644eab80b2f098367b40100都不知道是从哪里来的
1732a7213644eab80b2f098367b40100 != fad5b132556279d8300653c2011e756d
其他改成no-sign的方式呢？
#用下列4句去掉'debuild -S -k$GPGKEY'构建的签名再dput不行。
sed -i '/^-----BEGIN PGP SIGNATURE-----/,/^-----END PGP SIGNATURE-----/d' neutron_20.5.0-0ubuntu2_source.changes
sed -i '/^-----BEGIN PGP SIGNATURE-----/,/^-----END PGP SIGNATURE-----/d' neutron_20.5.0-0ubuntu2.dsc
sed -i '/^-----BEGIN PGP SIGNED MESSAGE-----/d' neutron_20.5.0-0ubuntu2_source.changes
sed -i '/^-----BEGIN PGP SIGNED MESSAGE-----/d' neutron_20.5.0-0ubuntu2.dsc
#可能需要使用-u参数来dput
dput -u ppa:zhhuabj/jammy-sru neutron_20.5.0-0ubuntu2_source.changes
#可能需要用'debuild -S -uc -us'替代上面的4句来去签名后再用dput -u能上传，但ppa也看不到东西，也收不到邮件
#dpkg-genchanges -S > neutron_20.5.0-0ubuntu2_source.changes
dpkg-source --commit
dpkg-source -b .
debian/rules clean
#debuild -S -k$GPGKEY #with sign
#dput ppa:zhhuabj/jammy-sru neutron_20.5.0-0ubuntu2_source.changes
debuild -S -uc -us #no sign
dput -u ppa:zhhuabj/jammy-sru neutron_20.5.0-0ubuntu2_source.changes
实在没办法了，在国外一台机器上创建了lxd用debuild试了一下，居然成功了，完全相同的方法啊，无语。
20241126 - change to use debdiff instead of pr again
现在做sru又改回了用debdiff的方式了, 并且要求更严了，见： https://bugs.launchpad.net/ubuntu/jammy/+source/neutron/+bug/2017748/comments/28
20241129 - sru new example
git cherry-pick -s -x 97603dde566364c63e381c9bb557e8a430656dbc
git format-patch -1 a597c0c80b24270c4cd6c7f14bd09bcdfab0d269
mv 0001-Fix-loadbalancer-stuck-in-cascade-delete.patch fix-loadbalancer-stuck-in-cascade-delete.patch
#add DEP-3 headers - https://bugs.launchpad.net/ubuntu/jammy/+source/neutron/+bug/2017748/comments/28
Bug-Ubuntu: https://launchpad.net/bugs/2077348
Origin: upstream, https://opendev.org/openstack/octavia/commit/97603dde566364c63e381c9bb557e8a430656dbc
#UCA - https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/yoga-staging
#UA - https://launchpad.net/ubuntu/+source/octavia
dget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/octavia/1:10.1.1-0ubuntu1.1/octavia_10.1.1-0ubuntu1.1.dsc
dpkg-source -x octavia_10.1.1-0ubuntu1.1.dsc
cd octavia-10.1.1/
sudo pbuilder update
DEB_BUILD_OPTIONS=nocheck pdebuild
quilt import /bak/openstack/octavia/fix-loadbalancer-stuck-in-cascade-delete.patch
quilt pop -a && quilt push -a && quilt refresh && quilt applied
dch -i
#version for stable releases (increment of ubuntu0.1, usually), not development series (increment of ubuntu1, usually)
$ cat debian/changelog |head -n3
octavia (1:10.1.1-0ubuntu1.2) jammy; urgency=medium
* d/p/fix-loadbalancer-stuck-in-cascade-delete.patch (LP: #2077348)
DEB_BUILD_OPTIONS=nocheck pdebuild
cd ..
debsign octavia_10.1.1-0ubuntu1.2_source.changes -k$GPGKEY
#NOTE: if ppa failed with md5 unmatched, that's because we need to run v-pi-n to run dput
dput ppa:zhhuabj/jammy-sru octavia_10.1.1-0ubuntu1.2_source.changes
#this case - https://bugs.launchpad.net/octavia/+bug/2077348
#the example - https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/2017748
#refer to the output of (cmadison octavia) and (rmadison octavia)
develop/plucky(25.04) 1:15.0.0-0ubuntu1 (the next version is 1:15.0.0-0ubuntu2 because it's develop) dalmatian(1:15.0.0-0ubuntu1~cloud0) expoxy(1:15.0.0-0ubuntu1~cloud0)
UA/oracular(24.10) 1:15.0.0-0ubuntu1 (the next version is 1:15.0.0-0ubuntu1.1 because it's stable)
UA/noble(24.04) 1:14.0.0-0ubuntu1.2 caracal(1:14.0.0-0ubuntu1.2~cloud0)
jammy-caracal 2024.1 14.0.0 (not needed, same as UA)
jammy-bobcat 2023.2 13.0.0 (not needed, eol)
jammy-antelope 2023.1, 12.0.0 (needed)
UA/jammy(22.04) 1:10.1.1-0ubuntu1.1 yoga(1:10.1.1-0ubuntu1.1~cloud0)
focal-yoga (needed)
UA/focal(20.04) 6.2.2-0ubuntu1.1 ussuri(6.2.2-0ubuntu1.1~cloud0) (needed)
need add:
1, Ubuntu Cloud Archive, click 'Also affects project' then search 'cloud-archive'
2, Add openstack releases like yoga, switch to 'https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/2077348', then click 'Target to series' to add them
2, octavia(Ubuntu), click 'Also affects distribution/ then search 'octavia'
3, Add ubuntu releases like focal, click 'Target to series' to add the series like plucky, oraclular, noble, jammy, focal
20241129 - pbuilder 如何支持develope中的plucky
plucky(ubuntu 25.04)还在开发中，pbuilder如何创建plucky image呢？
#E: No such script: /usr/share/debootstrap/scripts/plucky
sudo apt install git build-essential devscripts debhelper
git clone https://salsa.debian.org/installer-team/debootstrap.git
cd debootstrap && dpkg-buildpackage -us -uc
sudo dpkg -i ../debootstrap_1.0.138_all.deb
#ubuntu-distro-info: unknown distribution series `plucky' - distro-info-data
sudo apt install distro-info-data -y
cat /usr/share/distro-info/ubuntu.csv |grep plucky
ubuntu-distro-info --all |grep plucky
sudo pbuilder --create --distribution plucky --architecture amd64 --debootstrapopts --variant=buildd
20250314 - debian git source code
octavia debian的源码（https://git.launchpad.net/~ubuntu-openstack-dev/ubuntu/+source/octavia）只有origin/stable/2024.1， 它里面会有noble的字眼，那是因为jammy-caracal与noble是共用这一套源码的， 但UCA(jammy-caracal)还是会有一点不同，它会单独apply ca-patches(git clone https://git.launchpad.net/~ubuntu-cloud-archive/+git/ca-patches) (通过此命令apply: export CA_PATCHES=${HOME}/ca-patches && cloud-archive-backport -r caracal -P octavia - https://git.launchpad.net/~ubuntu-cloud-archive/+git/ca-patches/tree/README.md)
20250318 - sru new rules
现在sru又有一些新规范 - https://bugs.launchpad.net/octavia/+bug/2077348/comments/20
1, 格式改成这种:
lp2077348-1-fix-blah.patch, lp2077348-2-fix-blah.patch
* Description, a few sentences. (LP: #BUG)
- d/p/patch1
- d/p/patch2.
2, dep3 example 改成这种(里面有的前面有一些空行) - https://git.launchpad.net/~mruffell/ubuntu/+source/octavia/tree/debian/patches/lp2077348-fix-loadbalancer-stuck-in-cascade-delete.patch?h=stable/2024.1
3, sru template里添加 ‘Where problems could occur’段
4, 说之前生成的debdiff, 在debian git source (https://git.launchpad.net/~ubuntu-openstack-dev/ubuntu/+source/octavia)里使用下列命令后用 git show HEAD看时会看到一些红色的空格，不知道是不是使用了QUILT格式的原因，下次这点着重注意一下。
git checkout -b 2023.1 origin/stable/2023.1
patch -p1 < antelope.debdiff
git add debian/patches/fix-loadbalancer-stuck-in-cascade-delete.patch
git add -u
git commit -m 'test'
git show HEAD
20250327 - sru debdiff被合并到debian git source之后的流程
sometimes it can be months
but recently its been around 2 weeks
SRU Team works in a shift right, one person a day
they look at the current list, choose one LP bug, read it and think about it
for example, the current lists are:
https://launchpad.net/ubuntu/oracular/+queue?queue_state=1&queue_text=
https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=
https://launchpad.net/ubuntu/focal/+queue?queue_state=1&queue_text=
SRU team takes packages from upload queue, and places them into -proposed
when its in proposed, we will need to get someone(captain) to move the cloud-archive packages from staging to proposed too
then you test packages in proposed and write up verifications
20250328 - Unable to find distroseries: focal-yoga
今天做hotfix时运行dput后收到’Unable to find distroseries: focal-yoga’, 原来是因为我马虎， 运行的是 dput ppa:xxx neutron_20.5.0-0ubuntu2~cloud0_source.changes, 而不是 dput ppa:xxx neutron_20.5.0-0ubuntu2~cloud0+hf00375454v20250328.0_source.changes, 这种因为马虎产生的问题找起来还真难找。
dget https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/yoga-staging/+sourcefiles/neutron/2:20.5.0-0ubuntu2~cloud0/neutron_20.5.0-0ubuntu2~cloud0.dsc
wget https://launchpadlibrarian.net/763379632/focal-yoga.debdiff
cd neutron-20.5.0/
patch -p1 < ../focal-yoga.debdiff
#modify changelog from 2:20.5.0-0ubuntu2~cloud1 to 2:20.5.0-0ubuntu2~cloud0+hf00375454v20250328.0
hua@tp:/bak/work/sru/neutron/hotfix_focal_yoga/neutron-20.5.0$ cat debian/changelog |head -n4
neutron (2:20.5.0-0ubuntu2~cloud0+hf00xxxv20250328.0) focal; urgency=medium
* [HOTFIX] handle creation of Port_Binding with chassis set (LP: #2017748)
- d/p/handle-creation-of-Port_Binding-with-chassis-set.patch
quilt pop -a && quilt push -a && quilt refresh
quilt applied
DEB_BUILD_OPTIONS=nocheck pdebuild
cd ..
debsign neutron_20.5.0-0ubuntu2~cloud0_source.changes -k$GPGKEY
dput ppa:xxx/sf00375454-test neutron_20.5.0-0ubuntu2~cloud0+hf00xxxv20250328.0_source.changes
20250417 update, 今天遇到了下列错误，添加’–debbuildopts -sa’解决了：
#Files specified in DSC are broken or missing, skipping package unpack verification.
DEB_BUILD_OPTIONS=nocheck pdebuild --debbuildopts -sa
20250401 - 已经EOL的release需要做sru吗？
例：zed已经EOL, 如果认为它不影响upgrade的话需要将它标记won’t fix, 有的环境很大，可以一个升级得持续几个星期 -
https://bugs.launchpad.net/cloud-archive/zed/+bug/2077348/comments/29
20250402 - lxd里使用sbuild
# Noble VM
lxc launch ubuntu:24.04 noble-vm --vm -c limits.cpu=6 -c limits.mem=16G -d root,size=100GB
ssh user@noble-vm
# Replace /home/ zhhuabj with your user
sudo apt update && sudo apt dist-upgrade -y && sudo apt install -y apt-cacher-ng autopkgtest build-essential debconf-utils debmake dh-make git-buildpackage libvirt-daemon-system pastebinit pkg-config quilt sbuild-launchpad-chroot ubuntu-dev-tools uvtool virtinst
sudo snap install lxd
mkdir -p ~/schroot/build
mkdir -p ~/schroot/logs
mkdir -p ~/schroot/scratch
echo "/home/ zhhuabj/schroot/scratch /scratch none rw,bind 0 0" | sudo tee -a /etc/schroot/sbuild/fstab
sudo mount -a
# Setup mk-sbuild.rc and .sbuildrc per https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/Setup.md
# vim ~/.mk-sbuild.rc
# vim ~/.sbuildrc
sudo sbuild-launchpad-chroot create -n focal-amd64 -s focal -a amd64
sudo sbuild-adduser zhhuabj
sudo adduser zhhuabj sbuild
newgrp sbuild
DEB_BUILD_OPTIONS="parallel=12" sbuild -Adfocal-amd64 *.dsc
# Eventually it fails, run `sudo ncdu -x /` and you'll see lots of space in /var/lib/sbuild/build/gcc-10-XXXXXX/gcc-10-10.5.0/build/gcc/testsuite - about 60GB
20250416 - sru example
有新的要求 - https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/2017748/comments/40
deepcopy patch has been in 30.0.0 - https://review.opendev.org/c/openstack/nova/+/920374
iso patch was introduced in 31.0.0 - 96a5c21 - https://review.opendev.org/c/openstack/nova/+/909611
iso patch for stable/2024.2 backport - https://review.opendev.org/c/openstack/nova/+/943924
deepcopy patch for stable/2024.1 backport - https://review.opendev.org/c/openstack/nova/+/926696
iso patch for stable/2024.1 backport - https://review.opendev.org/c/openstack/nova/+/945816/
deepcopy patch for stable/2023.2 backport - https://review.opendev.org/c/openstack/nova/+/926697
iso patch for stable/2023.2 backport - https://review.opendev.org/c/openstack/nova/+/945903
For UA
development/plucky(25.04) 3:31.0.0-0ubuntu1 -> 3:31.0.0-0ubuntu2 (no need, iso patch is in 31.0.0)
UA oracular 3:30.0.0-0ubuntu1 -> 3:30.0.0-0ubuntu1.1
UA noble 3:29.2.0-0ubuntu1 -> 3:29.2.0-0ubuntu1.1
For UCA
UCA epoxy(2025.1) 3:31.0.0-0ubuntu1~cloud0 (uses version in epoxy-proposed) (no need, iso patch is in 31.0.0)
UCA dalmatian(2024.2) 3:30.0.0-0ubuntu1~cloud0 (no need due to UA oracular)
UCA caracal(2024.1) 3:29.2.0-0ubuntu1~cloud0 (no need due to UA noble)
UCA bobcat(2023.2) 3:28.2.0-0ubuntu1~cloud0 (depends on if the upstream backport for 2023.2 can be merged)
need add:
1, UCA, Ubuntu Cloud Archive, click 'Also affects project' then search 'cloud-archive'
2, UCA, switch to 'https://bugs.launchpad.net/cloud-archive/+bug/2054446', then click 'Target to series' to add them.
2, UA, nova(Ubuntu), click 'Also affects distribution/ then search 'nova'
3, UA, Add ubuntu releases like noble, switch to 'https://bugs.launchpad.net/ubuntu/+source/nova/+bug/2054446', then click 'Target to series' to add the series like plucky, oraclular, noble
#do sru for UA oracular (30.0.0) first
git checkout -b 30.0.0 30.0.0
git cherry-pick -s -x a8de673
git format-patch -1 552e26f093456427f1083d3a7f706fa5a69e8bf2
mv 0001-Fix-device-type-when-booting-from-ISO-image.patch lp2054446-fix-device-type-when-booting-from-ISO-image.patch
#add DEP-3 headers after 'Subject' block - https://bugs.launchpad.net/ubuntu/jammy/+source/neutron/+bug/2017748/comments/28
#https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/2017748/comments/40
Bug-Ubuntu: https://launchpad.net/bugs/2054446
Origin: upstream, https://opendev.org/openstack/nova/commit/a8de6737d22d19fea3d93024fb0cbbe40d67dde9
#UCA - https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/yoga-staging
#UA - https://launchpad.net/ubuntu/+source/nova
cd /bak/work/sru/nova/oracular
dget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/nova/3:30.0.0-0ubuntu1/nova_30.0.0-0ubuntu1.dsc
dpkg-source -x nova_30.0.0-0ubuntu1.dsc
cd nova-30.0.0/
sudo pbuilder update
sudo apt update && sudo apt install apache2-dev dh-apache2 -y
DEB_BUILD_OPTIONS=nocheck pdebuild
quilt import /bak/openstack/nova/lp2054446-fix-device-type-when-booting-from-ISO-image.patch
quilt pop -a && quilt push -a && quilt refresh && quilt applied
dch -i
#version for stable releases (increment of ubuntu0.1, usually), not development series (increment of ubuntu1, usually)
$ cat debian/changelog |head -n4
nova (3:30.0.0-0ubuntu1.1) oracular; urgency=medium
* Fix device type when booting from ISO image. (LP: #2054446)
- d/p/lp2054446-fix-device-type-when-booting-from-ISO-image.patch
DEB_BUILD_OPTIONS=nocheck pdebuild
cd ..
debsign nova_30.0.0-0ubuntu1.1_source.changes -k$GPGKEY
debdiff nova_30.0.0-0ubuntu1.dsc nova_30.0.0-0ubuntu1.1.dsc > oracular.debdiff
#SRU template, pls refer to https://bugs.launchpad.net/cloud-archive/+bug/2054446
# https://documentation.ubuntu.com/sru/en/latest/reference/bug-template/
Reference
[1] https://www.debian.org/doc/manuals/maint-guide/build.zh-cn.html
[2] https://wiki.softwareheritage.org/wiki/Debian_packaging
扫一扫
534
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
