headers
Riku Voipio | 1 Oct 2011 13:19
Favicon

Re: debuild & no secret keys

On 1 October 2011 00:20, Tom Gall <tom.gall@...> wrote:
> Hi All,
>
> I'm setting up a new machine and I'm guessing I must have missed a
> step or a file.
>
> When I debuild -S -sa it's complaining about my secret key not being found.
>
> gpg: skipped "Tom Gall <tom.gall@...>": secret key not available
> gpg: /tmp/debsign.Or3BKbui/live-build_3.0~a21-1linaro9~natty1.dsc:
> clearsign failed: secret key not available
> debsign: gpg error occurred!  Aborting....
>
> Yet if I gpg -k on both a "good" machine and this new box I see the
> exact same set of keys listed.

"gpg -k" lists public keys. see what "gpg -K" lists?

Riku
Permalink | Reply | 2 comments |
headers
Tom Gall | 1 Oct 2011 14:31
Favicon

Re: debuild & no secret keys

Hi Riku,

On Sat, Oct 1, 2011 at 6:19 AM, Riku Voipio <riku.voipio <at> linaro.org> wrote:
> On 1 October 2011 00:20, Tom Gall <tom.gall <at> linaro.org> wrote:
>> Hi All,
>>
>> I'm setting up a new machine and I'm guessing I must have missed a
>> step or a file.
>>
>> When I debuild -S -sa it's complaining about my secret key not being found.
>>
>> gpg: skipped "Tom Gall <tom.gall <at> linaro.org>": secret key not available
>> gpg: /tmp/debsign.Or3BKbui/live-build_3.0~a21-1linaro9~natty1.dsc:
>> clearsign failed: secret key not available
>> debsign: gpg error occurred!  Aborting....
>>
>> Yet if I gpg -k on both a "good" machine and this new box I see the
>> exact same set of keys listed.
>
> "gpg -k" lists public keys. see what "gpg -K" lists?
>
> Riku

Thanks for the pointer.

Yet again the same output for gpg -K on both machines.

--

-- 
Regards,
Tom
(Continue reading)

Permalink | Reply | 1 comment |
headers
Loïc Minier | 2 Oct 2011 11:36
Favicon

Re: debuild & no secret keys

On Sat, Oct 01, 2011, Tom Gall wrote:
> >> gpg: skipped "Tom Gall <tom.gall@...>": secret key not available
> >> gpg: /tmp/debsign.Or3BKbui/live-build_3.0~a21-1linaro9~natty1.dsc:
> >> clearsign failed: secret key not available
> >> debsign: gpg error occurred!  Aborting....
> >> Yet if I gpg -k on both a "good" machine and this new box I see the
> >> exact same set of keys listed.
> > "gpg -k" lists public keys. see what "gpg -K" lists?
> Yet again the same output for gpg -K on both machines.

 Does your key have exactly "Tom Gall <tom.gall@...>" as one uid?
 If not, you might have to set explicitly which key id to use
 (-k1234ABCD); perhaps this is a config that you didn't copy over.

--

-- 
Loïc Minier
Permalink | Reply | 0 comments |
headers
James Westby | 2 Oct 2011 23:40
Favicon
Gravatar

Re: debuild & no secret keys

On Fri, 30 Sep 2011 16:20:12 -0500, Tom Gall <tom.gall@...> wrote:
> Hi All,
> 
> I'm setting up a new machine and I'm guessing I must have missed a
> step or a file.
> 
> When I debuild -S -sa it's complaining about my secret key not being found.
> 
> gpg: skipped "Tom Gall <tom.gall@...>": secret key not available
> gpg: /tmp/debsign.Or3BKbui/live-build_3.0~a21-1linaro9~natty1.dsc:
> clearsign failed: secret key not available
> debsign: gpg error occurred!  Aborting....
> 
> 
> Yet if I gpg -k on both a "good" machine and this new box I see the
> exact same set of keys listed.

https://wiki.ubuntu.com/UbuntuDevelopment/Uploading#Signing_the_package

has some tips on debugging this sort of thing that may help you.

Thanks,

James
Permalink | Reply | 1 comment |
headers
Zach Pfeffer | 3 Oct 2011 04:48
Favicon

Re: BUGREPORTED work item state

On 30 September 2011 13:22, Fathi Boudra <fathi.boudra@...> wrote:
> Hi Zach,
>
> I noticed that you introduced BUGREPORTED on Android blueprints for
> the work items.
> It raised a couple of questions:
> 1. what does BUGREPORTED means ?

When David Zinmann and I were going through each WI and closing out
11.09, a few BPs were done, except for one or two issues. These issues
were bugs, so instead of filing a new WI in 11.10 we just marked the
WI as BUGREPORTED and linked the bug to the 11.09. BUGREPORTED seemed
to unambiguously mark a hand off between the BP tracking and the bug
system.

> 2. do we need to update
> https://wiki.linaro.org/Process/WorkItemsHowto#Work_items_in_the_whiteboard
> ?

I think we should. BUGREPORTED seemed to fill a void as David and I
were going through each item that the other fields didn't. For
reference:

TODO
empty string, INPROGRESS
Item is expected to be done by the end of the cycle
INPROGRESS
By default, this is an alias for TODO, but teams can choose to track
it separately.
BLOCKED
(Continue reading)

Permalink | Reply | 4 comments |
headers
Marcin Juszkiewicz | 3 Oct 2011 09:22
Favicon

Re: BUGREPORTED work item state

W dniu 03.10.2011 04:48, Zach Pfeffer pisze:
> On 30 September 2011 13:22, Fathi Boudra <fathi.boudra@...> wrote:
>> Hi Zach,
>>
>> I noticed that you introduced BUGREPORTED on Android blueprints for
>> the work items.
>> It raised a couple of questions:
>> 1. what does BUGREPORTED means ?
> 
> When David Zinmann and I were going through each WI and closing out
> 11.09, a few BPs were done, except for one or two issues. These issues
> were bugs, so instead of filing a new WI in 11.10 we just marked the
> WI as BUGREPORTED and linked the bug to the 11.09. BUGREPORTED seemed
> to unambiguously mark a hand off between the BP tracking and the bug
> system.

You know that linked bug counts as work item too? So if you have work
item for each you reported a bug you can drop it from whiteboard once it
got linked.
Permalink | Reply | 0 comments |
headers
Daniel Lezcano | 3 Oct 2011 10:18
Favicon

[pm-qa 04/10] check the cpu state is reflected in sysfs

Signed-off-by: Daniel Lezcano <daniel.lezcano@...
---
 cpuhotplug/cpuhotplug_02.sh  |   60 ++++++++++++++++++++++++++++++++++++++++++
 cpuhotplug/cpuhotplug_02.txt |    1 +
 include/functions.sh         |   21 ++++++++++++++
 3 files changed, 82 insertions(+), 0 deletions(-)
 create mode 100644 cpuhotplug/cpuhotplug_02.sh
 create mode 100644 cpuhotplug/cpuhotplug_02.txt

diff --git a/cpuhotplug/cpuhotplug_02.sh b/cpuhotplug/cpuhotplug_02.sh
new file mode 100644
index 0000000..4f3f3d2
--- /dev/null
+++ b/cpuhotplug/cpuhotplug_02.sh
 <at>  <at>  -0,0 +1,60  <at>  <at> 
+#!/bin/bash
+#
+# PM-QA validation test suite for the power management on ARM
+#
+# Copyright (C) 2011, Linaro Limited.
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License
+# as published by the Free Software Foundation; either version 2
+# of the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Lezcano | 3 Oct 2011 10:18
Favicon

[pm-qa 01/10] factor out check_file function

Signed-off-by: Daniel Lezcano <daniel.lezcano@...
---
 include/functions.sh |   13 ++++++++++---
 1 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/include/functions.sh b/include/functions.sh
index 6702cb2..bff8e13 100644
--- a/include/functions.sh
+++ b/include/functions.sh
 <at>  <at>  -194,13 +194,20  <at>  <at>  check() {
     return 0
 }

+check_file() {
+    local file=$1
+    local dir=$2
+
+    check "'$file' exists" "test -f" $dir/$file
+}
+
 check_cpufreq_files() {

     local dirpath=$CPU_PATH/$1/cpufreq
     shift 1

     for i in $ <at> ; do
-	check "$i exists" "test -f" $dirpath/$i  || return 1
+	check_file $i $dirpath || return 1
     done
(Continue reading)

Permalink | Reply | 12 comments |
headers
Daniel Lezcano | 3 Oct 2011 10:18
Favicon

[pm-qa 02/10] add the makefile for cpuhotplug

Signed-off-by: Daniel Lezcano <daniel.lezcano@...
---
 cpuhotplug/Makefile |   25 +++++++++++++++++++++++++
 1 files changed, 25 insertions(+), 0 deletions(-)
 create mode 100644 cpuhotplug/Makefile

diff --git a/cpuhotplug/Makefile b/cpuhotplug/Makefile
new file mode 100644
index 0000000..2225d82
--- /dev/null
+++ b/cpuhotplug/Makefile
 <at>  <at>  -0,0 +1,25  <at>  <at> 
+#
+# PM-QA validation test suite for the power management on ARM
+#
+# Copyright (C) 2011, Linaro Limited.
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License
+# as published by the Free Software Foundation; either version 2
+# of the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Daniel Lezcano | 3 Oct 2011 10:18
Favicon

[pm-qa 05/10] test the affinity does not work on an offline cpu

Signed-off-by: Daniel Lezcano <daniel.lezcano@...
---
 cpuhotplug/cpuhotplug_03.sh  |   51 ++++++++++++++++++++++++++++++++++++++++++
 cpuhotplug/cpuhotplug_03.txt |    1 +
 2 files changed, 52 insertions(+), 0 deletions(-)
 create mode 100644 cpuhotplug/cpuhotplug_03.sh
 create mode 100644 cpuhotplug/cpuhotplug_03.txt

diff --git a/cpuhotplug/cpuhotplug_03.sh b/cpuhotplug/cpuhotplug_03.sh
new file mode 100644
index 0000000..489706b
--- /dev/null
+++ b/cpuhotplug/cpuhotplug_03.sh
 <at>  <at>  -0,0 +1,51  <at>  <at> 
+#!/bin/bash
+#
+# PM-QA validation test suite for the power management on ARM
+#
+# Copyright (C) 2011, Linaro Limited.
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License
+# as published by the Free Software Foundation; either version 2
+# of the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
(Continue reading)

Permalink | Reply | 0 comments |

Gmane