Where is my package after I upload it to my activated ppa ?

I have searched for many problem similar with mine, and all solution seems different.
I am sure that my gpg key is valid and not expired.
Maybe some lintian error prevent the package from successful uploading, and I want to know what it is and which requirements are must be satisfied.

Our logs indicate that we sent a rejection email to asionius@163.com, so you should check your spam filters etc.

The most recent rejection was "Source/binary (i.e. mixed) uploads are not allowed." That is, you must build a source package *only* (*_source.changes) using the -S option to dpkg-buildpackage/debuild and upload that, rather than also uploading your own binaries. See https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage#Options_when_building.

Several previous upload attempts were rejected for this reason or other reasons, such as listing "unstable" or "jessie" as the target series in debian/changelog, or having a mismatch between Checksums-Sha1 and Files fields (which suggests that you were manually editing the .dsc or .changes file, which is not normally a good idea).

@Colin Watson
Thank you for your detailed answer!
I will retry soon!

Thanks Colin Watson, that solved my question.

I have met one problem with this package. How launch pad server automatically install commands that my package depends ?

Could you please rephrase your question? I don't really understand exactly what you mean. An example would help.

You have to put the dependencies into the control file
The packages that are needed to build the package have to go into Build-Depends of the source package!
I assume your error is the following:

You have:
Source: fibjs ...
Build-Depends: debhelper (>= 8.0.0)
...
Package: fibjs ...
Depends: cmake, make, g++, g++-multili, ${shlibs:Depends}, ${misc:Depends}

but you probably need:
Source: fibjs ...
Build-Depends: debhelper (>= 8.0.0), cmake, make, g++, ...
...
Package: fibjs ...
Depends: ${shlibs:Depends}, ${misc:Depends}

For example my build script runs command 'cmake' and it is not appear in launchpad server so it build failed on remote launchpad server. So I wonder how to make the remote launchpad server install the 'cmake' command automatically via some config file in my package? I tried to list the command in control file after entry 'Depends:'. But it did no help.

Manfred is correct that that requires adding cmake to your Build-Depends field, not your Depends field. Depends is about what your binary package requires when it's installed, while Build-Depends is about what's required to build your source package.

(However, you do not need to and shouldn't declare "make" or "g++" in Build-Depends unless you need a version constraint; those are in the "build-essential" set of packages.)

@Manfred Hampl
@Colin Watson
Hello all :
    Thanks a lot for your answer!
    The remote launchpad server is building the package now.

Thanks Manfred Hampl, that solved my question.

Hi Colin :
     I am sorry to ask another question, the package I uploaded to my ppa has been built successfully in arch amd64 and failed in i386, now I can not use apt to install my package in ubuntu 16.04 64bit. So when can I install the built 64bit deb in ubuntu 64bit?

Thanks Manfred Hampl, that solved my question.