User forums > Nightly builds
The 01 August 2015 build (10376) is out.
Jenna:
There is no need to run dpkg-buildpackage as root.
It uses fakeroot internally and works just fine (as long as the normal user is allowed to write into the source-tree and one folder below).
cacb:
--- Quote from: jens on August 04, 2015, 09:28:13 pm ---There is no need to run dpkg-buildpackage as root.
It uses fakeroot internally and works just fine (as long as the normal user is allowed to write into the source-tree and one folder below).
--- End quote ---
Thank you. I tested it, and it builds without sudo. The warning about "unsafe ownership" is gone. Otherwise the same as before, including the final gpg error.
Jenna:
--- Quote from: cacb on August 04, 2015, 11:07:52 pm ---
--- Quote from: jens on August 04, 2015, 09:28:13 pm ---There is no need to run dpkg-buildpackage as root.
It uses fakeroot internally and works just fine (as long as the normal user is allowed to write into the source-tree and one folder below).
--- End quote ---
Thank you. I tested it, and it builds without sudo. The warning about "unsafe ownership" is gone. Otherwise the same as before, including the final gpg error.
--- End quote ---
The gpg-error might go away if you change or remove the "Maintainer: ..."-line in "debian/control", but I'm not absolutely sure. I do not use Debian myself since several years, just maintain the packages on my (CentOS-)server.
cacb:
--- Quote from: jens on August 04, 2015, 11:25:17 pm ---The gpg-error might go away if you change or remove the "Maintainer: ..."-line in "debian/control", but I'm not absolutely sure. I do not use Debian myself since several years, just maintain the packages on my (CentOS-)server.
--- End quote ---
Ok, I will test it and report back. Thanks a lot.
cacb:
--- Quote from: cacb on August 05, 2015, 08:46:26 am ---
--- Quote from: jens on August 04, 2015, 11:25:17 pm ---The gpg-error might go away if you change or remove the "Maintainer: ..."-line in "debian/control", but I'm not absolutely sure. I do not use Debian myself since several years, just maintain the packages on my (CentOS-)server.
--- End quote ---
Ok, I will test it and report back. Thanks a lot.
--- End quote ---
I tried first removing the whole "Maintainer: ..." line, I got this at the end
dh_builddeb -pwxsmith-dev
dpkg-deb: warning: parsing file 'debian/wxsmith-dev/DEBIAN/control' near line 30 package 'wxsmith-dev':
missing maintainer
dpkg-deb: warning: ignoring 1 warning about the control file(s)
dpkg-deb: building package `wxsmith-dev' in `../wxsmith-dev_13.12svn10379_amd64.deb'.
dpkg-genchanges >../codeblocks_13.12svn10379_amd64.changes
dpkg-genchanges: including full source code in upload
dpkg-genchanges: error: missing information for critical output field Maintainer
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 255
Then I left the "Maintainer: ..." line in, but removed your name/email. I still got some complaints at the end:
dpkg-deb: warning: ignoring 1 warning about the control file(s)
dpkg-deb: building package `wxsmith-dev' in `../wxsmith-dev_13.12svn10379_amd64.deb'.
dpkg-genchanges >../codeblocks_13.12svn10379_amd64.changes
dpkg-genchanges: including full source code in upload
dpkg-source --after-build codeblocks-13.12svn
dpkg-buildpackage: full upload; Debian-native package (full source is included)
signfile codeblocks_13.12svn10379.dsc
gpg: skipped "Jens Lody <jens@codeblocks.org>": No secret key
gpg: [stdin]: clearsign failed: No secret key
I can still install/run CB.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version