Hah! yeah, looks good. Thanks :)
--
fwts nx test (test 3) reports incorrect CPU number when test fails
https://bugs.launchpad.net/bugs/638783
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Thanks, my sincere apologies for that mistake. Is this now acceptable?:
http://kernel.ubuntu.com/git?p=cking/fwts/.git;a=blob;f=debian/changelog;h=d9452886a66ee759fad3bcec830b7c0d5bb6e3b3;hb=HEAD
On Wed, 2010-09-15 at 15:35 +, Stefano Rivera wrote:
> Re the bug closing, I corrected this for
Re the bug closing, I corrected this for you on the last upload too, but
you didn't important that change back into git (my point 2):
- * FADT test read correct ACPI table from /sys/firmware (LP: #627959)
+ * FADT test read correct ACPI table from /sys/firmware (closes: LP#627959)
Closes: #
Hi Stefano,
Couple of questions, excuse my ignorance here:
1. Pretty minimal diff, no problem. However it doesn't close this bug
with the correct syntax. Fixed in upload.
What does "it doesn't close this bug with the correct syntax" mean? Can
you explain a little more?
2. Can I suggest that you
Uploaded, but I didn't auto-close the bug (because bug auto-closing is
curretly broken in LP, and because I forgot -v in the build):
fwts (0.18.04) maverick; urgency=low
* fix build issues with bad cpufreq fix
* New upstream version 0.18.04
fwts (0.18.03) maverick; urgency=low
* Log corr
Pretty minimal diff, no problem. However it doesn't close this bug with
the correct syntax. Fixed in upload.
Can I suggest that you update the version in your git repo to match the
package in Ubuntu (changelog-wise). You might as well add a Vcs-Git line
to debian/control too. Personally I prefer t
Sorry, I accidentally subscribed Ubuntu Security Sponsors by an
incorrect click. Apologies.
--
fwts nx test (test 3) reports incorrect CPU number when test fails
https://bugs.launchpad.net/bugs/638783
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
A newer version 0.18.4 of the fwts tool is now available to fix this
bug.
0.18.4 also includes a single character typo fix in cpufreq test.
https://launchpad.net/~firmware-testing-team/+archive/ppa-firmware-test-
suite/+sourcepub/1294539/+listing-archive-extra
Can this be uploaded? Thanks
--
f
Fix in
http://kernel.ubuntu.com/git?p=cking/fwts/.git;a=commit;h=5539dfef34b77f9df35805fa10cd80682b1ad995
--
fwts nx test (test 3) reports incorrect CPU number when test fails
https://bugs.launchpad.net/bugs/638783
You received this bug notification because you are a member of Ubuntu
Bugs, which
