You should thumb down the ones in the testing queue, the ones in extras-devel will get purged automatically once you upload the new version. Also, I suggest you use versioned dependency checks (i.e. include the >= actual version of the new libs in the end-user package)

Thanks, I will remake the package files with libs as the section. I'll increase the build number to 2 to maybe avoid problems. Would hope I can get this done without changing the package name.

How do I go about removing the user/development ones after I have them in libs? :I

Section: libs

You could get an error if they were in the user section (as that would mean they have to go through separate QA...). Anyway, all these should be in the libs section (didn't check python-dropbox-client, though).

I tried promoting my app that depends on three python packages that I also made, it said error and that I have to promote these first so I did that. Tell me on either thread how to make them as libs and not show up on app manager for normal users :) I tried finding from wiki but am a bit lost, the allowed sections all start with user/

Hey there. This is, as far as I can see, a library, thus should not be in the user section. If you have an application that depends on it, promoting the application will also promote all depending libraries (just as the testing of your app will include indirectly testing the libs, too).