Launchpad itself

Unable to upload a non-native package on to launchpad

Asked by Mahesh Radhakrishnan

I am having issues trying to upload the edma3-lld-02.11.13.17~rc2 on to launchpad.
https://launchpad.net/~ti-keystone-team/+archive/ubuntu/ti-trusty-test-ppa/+packages

This package named edma3-lld-02.11.13.17~rc2 which was wrongly pushed as a native package earlier. The debian folder contents were wrong too.

Now, after I fixed the debian folder contents and made it non-native (as it should have been in the first place), I pushed it to Launchpad but this time with a version edma3-lld-02.11.13.17~rc2 , but it does trigger build on the Launchpad.(detailed log below)
The Launchpad-push log below, do you know what may be causing it? Is it possible to get a failure log from Launchpad? (which I cannot see now)
I see a log below (as a part of my push process) which says the below.
Package includes an .orig.tar.gz file although the debian revision suggests
that it might not be required. Multiple uploads of the .orig.tar.gz may be

I don’t have a version of the 02.11.13.17~rc2.orig.tar which I had pushed earlier. Infact the 02.11.13.17.orig.tar wasn’t there either (as it was a native package earlier)

Tarballs attached for orig and debian.

Any help would be greatly appreciated.
Thanks
Mahesh

Skip to content
titletitle
a0875154 | log out

    Jenkins
    ppa_push
    #668

The log file of the push operation to trusty-test-ppa
=========================================

+ debuild -S
dpkg-buildpackage -rfakeroot -d -us -uc -S
dpkg-buildpackage: source package edma3-lld
dpkg-buildpackage: source version 02.11.13.17~rc2-0ubuntu1~ppa1
dpkg-buildpackage: source changed by TI Keystone PPA <email address hidden>
dpkg-source --before-build edma3-lld-02.11.13.17~rc2
fakeroot debian/rules clean
dh clean
   dh_testdir
   debian/rules override_dh_auto_clean
make[1]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2'
/usr/bin/make -C packages PLATFORM=tci6636k2h-evm TARGET=a15 TOOLCHAIN_a15=GCC FORMAT=ELF SONAME=libedma3.so clean
make[2]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages'
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages edma3_lld_tci6636k2h-evm_a15_libs_clean PLATFORM=tci6636k2h-evm TARGET=a15 ;
make[3]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages'
# Cleaning a15:debug:edma3_lld_drv
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/drv clean PLATFORM=tci6636k2h-evm CORE=a15host PROFILE_a15host=debug TOOLCHAIN_a15=GCC
make[4]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/drv'
rm -rf obj/a15/debug/* obj/a15/debug/.deps/* lib/a15/debug/*
make[4]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/drv'
# Cleaning a15:release:edma3_lld_drv
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/drv clean PLATFORM=tci6636k2h-evm CORE=a15host PROFILE_a15host=release TOOLCHAIN_a15=GCC
make[4]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/drv'
rm -rf obj/a15/release/* obj/a15/release/.deps/* lib/a15/release/*
make[4]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/drv'
# Cleaning tci6636k2h-evm:debug:edma3_lld_rm
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/rm clean PLATFORM=tci6636k2h-evm CORE=a15host PROFILE_a15host=debug TOOLCHAIN_a15=GCC
make[4]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/rm'
rm -rf obj/tci6636k2h-evm/a15/debug/* obj/tci6636k2h-evm/a15/debug/.deps/* lib/tci6636k2h-evm/a15/debug/*
make[4]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/rm'
# Cleaning tci6636k2h-evm:rel:edma3_lld_rm
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/rm clean PLATFORM=tci6636k2h-evm CORE=a15host PROFILE_a15host=release TOOLCHAIN_a15=GCC
make[4]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/rm'
rm -rf obj/tci6636k2h-evm/a15/release/* obj/tci6636k2h-evm/a15/release/.deps/* lib/tci6636k2h-evm/a15/release/*
make[4]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/rm'
make[3]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages'
# Cleaning a15:debug:edma3_lld_drv
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/drv clean PLATFORM=tci6636k2h-evm CORE=a15host PROFILE_a15host=debug TOOLCHAIN_a15=GCC
make[3]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/drv'
rm -rf obj/a15/debug/* obj/a15/debug/.deps/* lib/a15/debug/*
make[3]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/drv'
# Cleaning a15:release:edma3_lld_drv
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/drv clean PLATFORM=tci6636k2h-evm CORE=a15host PROFILE_a15host=release TOOLCHAIN_a15=GCC
make[3]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/drv'
rm -rf obj/a15/release/* obj/a15/release/.deps/* lib/a15/release/*
make[3]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/drv'
# Cleaning tci6636k2h-evm:debug:edma3_lld_rm
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/rm clean PLATFORM=tci6636k2h-evm CORE=a15host PROFILE_a15host=debug TOOLCHAIN_a15=GCC
make[3]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/rm'
rm -rf obj/tci6636k2h-evm/a15/debug/* obj/tci6636k2h-evm/a15/debug/.deps/* lib/tci6636k2h-evm/a15/debug/*
make[3]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/rm'
# Cleaning tci6636k2h-evm:rel:edma3_lld_rm
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/rm clean PLATFORM=tci6636k2h-evm CORE=a15host PROFILE_a15host=release TOOLCHAIN_a15=GCC
make[3]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/rm'
rm -rf obj/tci6636k2h-evm/a15/release/* obj/tci6636k2h-evm/a15/release/.deps/* lib/tci6636k2h-evm/a15/release/*
make[3]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages/ti/sdo/edma3/rm'
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages edma3_drv_tci6636k2h-evm_a15_example_clean PLATFORM=tci6636k2h-evm TARGET=a15 ;
make[3]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages'
# Cleaning example edma3_drv_tci6636k2h-evm_a15_example_clean:debug
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/examples/edma3_user_space_driver/evmTCI6636K2H PLATFORM=tci6636k2h-evm CORE=a15host PROFILE_a15host=debug TOOLCHAIN_a15=GCC clean
make[4]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/examples/edma3_user_space_driver/evmTCI6636K2H'
rm -rf obj/tci6636k2h-evm/a15host/debug/edma3_drv_6636k2h_a15_sample_configuro
rm -rf obj/tci6636k2h-evm/a15host/debug/* obj/tci6636k2h-evm/a15host/debug/.deps/*
make[4]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/examples/edma3_user_space_driver/evmTCI6636K2H'
# Cleaning example edma3_drv_tci6636k2h-evm_a15_example_clean:release
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/examples/edma3_user_space_driver/evmTCI6636K2H PLATFORM=tci6636k2h-evm CORE=a15host PROFILE_a15host=release TOOLCHAIN_a15=GCC clean
make[4]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/examples/edma3_user_space_driver/evmTCI6636K2H'
rm -rf obj/tci6636k2h-evm/a15host/release/edma3_drv_6636k2h_a15_sample_configuro
rm -rf obj/tci6636k2h-evm/a15host/release/* obj/tci6636k2h-evm/a15host/release/.deps/*
make[4]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/examples/edma3_user_space_driver/evmTCI6636K2H'
make[3]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages'
# Cleaning example edma3_drv_tci6636k2h-evm_a15_example_clean:debug
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/examples/edma3_user_space_driver/evmTCI6636K2H PLATFORM=tci6636k2h-evm CORE=a15host PROFILE_a15host=debug TOOLCHAIN_a15=GCC clean
make[3]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/examples/edma3_user_space_driver/evmTCI6636K2H'
rm -rf obj/tci6636k2h-evm/a15host/debug/edma3_drv_6636k2h_a15_sample_configuro
rm -rf obj/tci6636k2h-evm/a15host/debug/* obj/tci6636k2h-evm/a15host/debug/.deps/*
make[3]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/examples/edma3_user_space_driver/evmTCI6636K2H'
# Cleaning example edma3_drv_tci6636k2h-evm_a15_example_clean:release
/usr/bin/make -C /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/examples/edma3_user_space_driver/evmTCI6636K2H PLATFORM=tci6636k2h-evm CORE=a15host PROFILE_a15host=release TOOLCHAIN_a15=GCC clean
make[3]: Entering directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/examples/edma3_user_space_driver/evmTCI6636K2H'
rm -rf obj/tci6636k2h-evm/a15host/release/edma3_drv_6636k2h_a15_sample_configuro
rm -rf obj/tci6636k2h-evm/a15host/release/* obj/tci6636k2h-evm/a15host/release/.deps/*
make[3]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/examples/edma3_user_space_driver/evmTCI6636K2H'
make[2]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2/packages'
make[1]: Leaving directory `/home/gtbldadm/nightlybuilds/push-ppa/edma3-lld-02.11.13.17~rc2'
   dh_clean
dpkg-source -b edma3-lld-02.11.13.17~rc2
dpkg-source: warning: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address
dpkg-source: warning: Version number suggests Ubuntu changes, but there is no XSBC-Original-Maintainer field
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building edma3-lld using existing ./edma3-lld_02.11.13.17~rc2.orig.tar.gz
dpkg-source: info: building edma3-lld in edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.debian.tar.gz
dpkg-source: info: building edma3-lld in edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc
dpkg-genchanges -S >../edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1_source.changes
dpkg-genchanges: warning: the current version (02.11.13.17~rc2-0ubuntu1~ppa1) is earlier than the previous one (02.11.13.17-0ubuntu1~ppa2)
dpkg-genchanges: including full source code in upload
dpkg-source --after-build edma3-lld-02.11.13.17~rc2
dpkg-buildpackage: full upload (original source is included)
Now running lintian...
E: edma3-lld changes: bad-ubuntu-distribution-in-changes-file trusty
W: edma3-lld source: newer-standards-version 3.9.5 (current is 3.9.3)
Finished running lintian.
Now signing changes and any dsc files...
signfile edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc TI Keystone PPA <email address hidden>

signfile edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1_source.changes TI Keystone PPA <email address hidden>

Successfully signed dsc and changes files
/home/gtbldadm/nightlybuilds/push-ppa
+ cd -
++ ls edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1_source.changes
Contents of edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1_source.changes
+ changes_file=edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1_source.changes
+ echo 'Contents of edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1_source.changes'
+ cat edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1_source.changes
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 09 Jul 2015 11:30:53 -0400
Source: edma3-lld
Binary: libedma3-1 libedma3-dev
Architecture: source
Version: 02.11.13.17~rc2-0ubuntu1~ppa1
Distribution: trusty
Urgency: medium
Maintainer: TI Keystone PPA <email address hidden>
Changed-By: TI Keystone PPA <email address hidden>
Description:
 libedma3-1 - EDMA3 Low Level Driver for user space
libedma3-dev - EDMA3 Low Level Driver for user space - development files
Changes:
 edma3-lld (02.11.13.17~rc2-0ubuntu1~ppa1) trusty; urgency=medium
.
   * Debian updates as per RC02
Checksums-Sha1:
 7835ac271701715b1363da349ffdee7ecc99f23a 1359 edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc
3b341a0082d5a794707283c8f520cfcb9b16eb60 23085303 edma3-lld_02.11.13.17~rc2.orig.tar.gz
c4eee29b2551c6b718cc8503e4b0d12d4c1e08c4 2800 edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.debian.tar.gz
Checksums-Sha256:
 776b427cc53af405f0e56cba09c94ede9c27f07c45bf8e3e2088fa48fbede39b 1359 edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc
ea83915be26586f124eebe8d32997e28aab1abeffdee3f8912d450a3207cf7bc 23085303 edma3-lld_02.11.13.17~rc2.orig.tar.gz
cf91d5515dc9a7b2c3e39caa6fb0e5a0690fd880e4e62267e7c8c8412a1affb2 2800 edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.debian.tar.gz
Files:
 f681112a0a6c9ce89e2f464a2c08fa10 1359 partner/libs extra edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc
82633b2e0384836184508a13feffce3f 23085303 partner/libs extra edma3-lld_02.11.13.17~rc2.orig.tar.gz
ef969e5aebd61e92af92fb872c4c5bd6 2800 partner/libs extra edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.debian.tar.gz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iJwEAQECAAYFAlWe1mIACgkQMQ3fes6TFNSTsgP9Fx3x/NaAOfuKp7BK+RYBwy4O
ZogwE5tNU8rmQfSJlM55V1CjjyhT2Cs8FcUi2fv6kiCw0qwgtdKSrRNigcx8a6oz
pKDSndkhIPHMF1/6Ckx8wE75DLTQmJYBz5EjUMoDTDwCxjsbF3RP4tMTk9SmsP+L
wbz8pKkD4GSQvi0/t/M=
=3H/Y
-----END PGP SIGNATURE-----
++ ls edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc
Contents of edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc
+ dsc_file=edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc
+ echo 'Contents of edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc'
+ cat edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 3.0 (quilt)
Source: edma3-lld
Binary: libedma3-1, libedma3-dev
Architecture: any
Version: 02.11.13.17~rc2-0ubuntu1~ppa1
Maintainer: TI Keystone PPA <email address hidden>
Standards-Version: 3.9.5
Build-Depends: pdk-keystone2, debhelper (>= 9)
Package-List:
 libedma3-1 deb partner/libs extra
libedma3-dev deb partner/libdevel extra
Checksums-Sha1:
 3b341a0082d5a794707283c8f520cfcb9b16eb60 23085303 edma3-lld_02.11.13.17~rc2.orig.tar.gz
c4eee29b2551c6b718cc8503e4b0d12d4c1e08c4 2800 edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.debian.tar.gz
Checksums-Sha256:
 ea83915be26586f124eebe8d32997e28aab1abeffdee3f8912d450a3207cf7bc 23085303 edma3-lld_02.11.13.17~rc2.orig.tar.gz
cf91d5515dc9a7b2c3e39caa6fb0e5a0690fd880e4e62267e7c8c8412a1affb2 2800 edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.debian.tar.gz
Files:
 82633b2e0384836184508a13feffce3f 23085303 edma3-lld_02.11.13.17~rc2.orig.tar.gz
ef969e5aebd61e92af92fb872c4c5bd6 2800 edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.debian.tar.gz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iJwEAQECAAYFAlWe1mIACgkQMQ3fes6TFNSRYwP/Qsc4fbZpnc3fJd9otT3myxm/
SMsojK57fs2YsFw91I07phFc2DbKI0zHwlKJGjnVOzE/KNaTQg8RBh0uyMc1Y7pp
o2/FZqVS0ukq3tYjrj/wtHJ5uIknOE0qo7DuRc0XTQ6/R2i0O6Lm9NbEZCC9Zfah
UiptOvrG8IM/q+Vf63A=
=VWCv
-----END PGP SIGNATURE-----
Uploading edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1_source.changes
+ echo Uploading edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1_source.changes
+ dput -f ppa:ti-keystone-team/ti-trusty-test-ppa edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1_source.changes
gpg: Signature made Thu 09 Jul 2015 04:15:30 PM EDT using RSA key ID CE9314D4
gpg: Good signature from "TI Keystone PPA <email address hidden>"
gpg: Signature made Thu 09 Jul 2015 04:15:30 PM EDT using RSA key ID CE9314D4
gpg: Good signature from "TI Keystone PPA <email address hidden>"
Checking signature on .changes
Good signature on /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1_source.changes.
Checking signature on .dsc
Good signature on /home/gtbldadm/nightlybuilds/push-ppa/edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc.
Package includes an .orig.tar.gz file although the debian revision suggests
that it might not be required. Multiple uploads of the .orig.tar.gz may be
rejected by the upload queue management software.
Uploading to ppa (via sftp to ppa.launchpad.net):
  edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc: Warning: Permanently added 'ppa.launchpad.net' (RSA) to the list of known hosts.
done.
  edma3-lld_02.11.13.17~rc2.orig.tar.gz: done.
  edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.debian.tar.gz: done.
  edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1_source.changes: done.
Successfully uploaded packages.

real 7m34.404s
user 0m0.276s
sys 0m0.640s
scp: /home/gtbldadm/nightlybuilds/push-ppa/artifacts.tgz: No such file or directory

real 0m5.769s
user 0m0.000s
sys 0m0.000s
Thu Jul 9 16:22:09 EDT 2015: Build Completed
grep: /tmp/ppa_push-668/artifacts/output/build_targets: No such file or directory
Thu Jul 9 16:22:09 EDT 2015: Copying to Apache Share
./generate_build_result.sh: line 12: cd: /tmp/ppa_push-668/artifacts/output: No such file or directory
./generate_build_result.sh: line 13: /tmp/ppa_push-668/artifacts/build-result.txt: No such file or directory
./generate_build_result.sh: line 50: build_targets: No such file or directory

real 0m0.004s
user 0m0.000s
sys 0m0.000s
grep: /tmp/ppa_push-668/artifacts/build-result.txt: No such file or directory
Could not find /tmp/ppa_push-668/artifacts/build-result.txt

real 0m0.014s
user 0m0.000s
sys 0m0.004s
Warning: Permanently added 'gtjenkins.itg.ti.com,158.218.103.230' (ECDSA) to the list of known hosts.

real 0m0.519s
user 0m0.028s
sys 0m0.024s

real 0m0.458s
user 0m0.012s
sys 0m0.044s
Thu Jul 9 16:22:10 EDT 2015: Shutdown Image
Shutdown ubuntu-12.04-64-ppa_push machine...
Domain ubuntu-12.04-64-ppa_push destroyed

real 0m0.865s
user 0m0.012s
sys 0m0.004s
+ echo Configure Email Notification
Configure Email Notification
+ rm -rf /var/jenkins/workspace/ppa_push/artifacts/result.html
+ mkdir -p /var/jenkins/workspace/ppa_push/artifacts
+ cp -rp /tmp/ppa_push-668/artifacts/results.html /var/jenkins/workspace/ppa_push/artifacts/results.html
Archiving artifacts
Email was triggered for: Success
Sending email for trigger: Success
Sending email to: <email address hidden>
Finished: SUCCESS

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was originally filed as bug #1473219.

Revision history for this message
Colin Watson (cjwatson) said : 		#1

This is a support request rather than a software bug - converting to a question. https://answers.launchpad.net/launchpad is the place to start next time.

Revision history for this message
Colin Watson (cjwatson) said : 		#2

In all of the failing cases, Launchpad has sent an automatic rejection e-mail to the package's maintainer address (<email address hidden>). If you don't receive e-mail sent to this address, you should change the maintainer address to one that you will read; it will save you a lot of time trying to guess what's wrong. Otherwise, please remember to check that mailbox if something seems awry.

In this case, the rejection message that Launchpad sent to you said this:

  edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc: Version older than that in the archive. 02.11.13.17~rc2-0ubuntu1~ppa1 <= 02.11.13.17-0ubuntu1~ppa2

Both are non-native versions, but I can see how the latter would be wrong if this is a release candidate rather than the final upstream release of 02.11.13.17. If you really mean to do this, you can delete the newer version from https://launchpad.net/~ti-keystone-team/+archive/ubuntu/ti-trusty-test-ppa/+delete-packages, wait 20 minutes or so for the deletion to be published, and then upload again.

The log message that you cite is in fact entirely client-side, and comes from dput; no Launchpad code is involved there. But it's also harmless and unrelated to why your upload was rejected - you can just ignore it.

Revision history for this message
Mahesh Radhakrishnan (m-radhakrishnan2) said : 		#3

Thanks a lot.
That solved it.

Regards
Mahesh

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Colin Watson
Sent: Thursday, July 09, 2015 7:27 PM
To: Radhakrishnan, Mahesh
Subject: Re: [Question #269075]: Unable to upload a non-native package on to launchpad

Your question #269075 on Launchpad itself changed:
https://answers.launchpad.net/launchpad/+question/269075

    Status: Open => Answered

Colin Watson proposed the following answer:
In all of the failing cases, Launchpad has sent an automatic rejection e-mail to the package's maintainer address (ti-keystone- <email address hidden>). If you don't receive e-mail sent to this address, you should change the maintainer address to one that you will read; it will save you a lot of time trying to guess what's wrong. Otherwise, please remember to check that mailbox if something seems awry.

In this case, the rejection message that Launchpad sent to you said
this:

  edma3-lld_02.11.13.17~rc2-0ubuntu1~ppa1.dsc: Version older than that in the archive. 02.11.13.17~rc2-0ubuntu1~ppa1 <=
02.11.13.17-0ubuntu1~ppa2

Both are non-native versions, but I can see how the latter would be wrong if this is a release candidate rather than the final upstream release of 02.11.13.17. If you really mean to do this, you can delete the newer version from https://launchpad.net/~ti-keystone-
team/+archive/ubuntu/ti-trusty-test-ppa/+delete-packages, wait 20 minutes or so for the deletion to be published, and then upload again.

The log message that you cite is in fact entirely client-side, and comes from dput; no Launchpad code is involved there. But it's also harmless and unrelated to why your upload was rejected - you can just ignore it.

--
If this answers your question, please go to the following page to let us know that it is solved:
https://answers.launchpad.net/launchpad/+question/269075/+confirm?answer_id=1

If you still need help, you can reply to this email or go to the following page to enter your feedback:
https://answers.launchpad.net/launchpad/+question/269075

You received this question notification because you asked the question.

Revision history for this message
William Grant (wgrant) said : 		#4