On 22-05-12 20:04, Frank Zhang wrote:
Pradeep, please install and verify the file is indeed installed.
Wido: which branch you observed this issue? thanks

All my patches are for the master branch, I'm not working with the 3.0.x branch.

I still don't know what the difference between the two is, I'm used to work with the master branch in various projects, they always have the bleeding edge code.

Wido


_____________________________________________
From: Pradeep Soundararajan
Sent: Tuesday, May 22, 2012 3:17 AM
To: Frank Zhang; cloudstack-dev@incubator.apache.org
Subject: RE: [PATCH] Ubuntu: Do not package the sccs-info file, it's not 
generated


Hi Frank,

I am able to see the files after my build in these location:

./artifacts/debbuild/cloud-2.2/debian/tmp/usr/share/doc/cloud/sccs-info
./artifacts/debbuild/cloud-2.2/debian/cloud-utils/usr/share/doc/cloud/sccs-info
./artifacts/debbuild/cloud-2.2/sccs-info

Please let me know what should I do now.

Note: I was doing the build from 'master' branch (./waf deb)

Thanks,
Pradeep.S

-----Original Message-----
From: Frank Zhang
Sent: Tuesday, May 22, 2012 1:13 AM
To: 
cloudstack-dev@incubator.apache.org<mailto:cloudstack-dev@incubator.apache.org>
Cc: Pradeep Soundararajan
Subject: RE: [PATCH] Ubuntu: Do not package the sccs-info file, it's not 
generated


On Mon, May 21, 2012 at 2:19 PM, Frank 
Zhang<frank.zh...@citrix.com<mailto:frank.zh...@citrix.com>>
wrote:
Hi Wido:
        It seems a bug to me if the file is not here, we use this
file to track git
commit from which package is built.

Pradeep:
        Can you verify this and log a bug to yourself:) if the file is not here.
thank you.


I am fine with logging a bug to fix this, but it was initially
reported back in December when Wido initially sent this patch in. We
have not fixed it in the interim, and effectively leaves us with
'magical build system', and we effectively have broken Debian/Ubuntu
builds (outside of the magical build
box) for at least 6 months now, which is unacceptable. I'd merge this
and revert it later when you get the problem fixed.

Pradeep is our dedicated build engineer now, he will take care of all build 
bugs.


--David


Reply via email to