[MDEV-3600] LP:459195 - deb package fails with dpkg-buildpackage: warning: Failed to sign .dsc and .changes file Created: 2009-10-23  Updated: 2012-10-04  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Hakan Küçükyılmaz (Inactive) Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug459195.xml    

 Description   

Trying to build a deb package fails with a warning and gives a return code != 0. This makes automating the packaging difficult.

How to repeat:
cd $PACKAGING_WORK
bakery/preheat.sh
cd bakery_

{number}
bakery/tarbake51.sh last:1 $MARIA_WORK
bakery/autobake-deb.sh mariadb-{version_num}-maria-beta-ourdelta{number}

.tar.gz
...
...
...
dpkg-genchanges >../mariadb-5.1_5.1.38-ourdelta83_amd64.changes
dpkg-genchanges: including full source code in upload
dpkg-buildpackage: full upload; Debian-native package (full source is included)
dpkg-buildpackage: warning: Failed to sign .dsc and .changes file

real 15m56.539s
user 12m17.670s
sys 2m1.516s

hakan@lu0012:~/work/monty_program/ourdelta-mariadb51-2/bakery-83$ echo $?
1

Details about the build procedure can be found here:
http://askmonty.org/wiki/index.php/BuildingMariaDB#Ubuntu_.deb_packages

Suggested fix:
hakan@lu0012:~/work/monty_program/ourdelta-mariadb51-2/bakery-83$ bzr diff
=== modified file 'bakery/autobake-deb.sh'
— bakery/autobake-deb.sh 2009-10-18 09:07:53 +0000
+++ bakery/autobake-deb.sh 2009-10-23 15:12:47 +0000
@@ -139,7 +139,9 @@

  1. Build the package.
    #
    -fakeroot dpkg-buildpackage
    +# -us Do not sign the source package.
    +# -uc Do not sign the .changes file.
    +fakeroot dpkg-buildpackage -us -uc
  1. Check if the local mirror deb-pool exists and move the results there.
  2. we have ourdelta, ourdelta-sail, and mariadb-ourdelta

 Comments   
Comment by Arjen Lentz (Inactive) [ 2009-11-01 ]

Re: deb package fails with dpkg-buildpackage: warning: Failed to sign .dsc and .changes file
Hakan, for the OurDelta build environment this is not relevant, since it has the key.
For elsewhere, it's ok to use the flags you've suggested, but it's important that they only get used there.
But perhaps it'd be best for your automated test environment to also have a (dummy) key, since that would more accurately reflect the environment it's trying to test.

Comment by Rasmus Johansson (Inactive) [ 2009-11-27 ]

Launchpad bug id: 459195

Generated at Thu Feb 08 06:49:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.