Dump files bring across page numbers and the segments associated with each page number (as per the contents of the master..sysusages table).
When the dump is loaded into the target database the page numbers and segment associates are maintained. Device details, which may exist in the dump file header (depends on ASE version), are (effectively) ignored when loading the dump file into the target database.
To ensure your target database segments reside on disk fragments of the same name, you have to understand the contents of the (source) master..sysusages table and then issue the appropriate 'create/alter database' commands to ensure the (target) master..sysusages entries are compatible.
(Very) Roughly example: for the example you've provided, the qip_infra_partition1 device fragment(s) in the target database must be the same size as all of the qip_infra_partition* device fragments in the source database.
For a better understanding of what's in the sysusages table I'd recommend you grab a copy of your master..sysusages and <dbname>..syssegments tables, then look through the source code for the sp_helpdb/sp_helpsegment stored procs.
---------------
Alternatively, and assuming you're working with ASE 15.x/16.x, if you run the following ...
exec master..sp_helpdb <dbname>
... against the source and target databases, and post the results back here, we can give you an idea of how to create the target database in such a way to ensure that after loading your database dump the segments reside on the same devices in the target database.
---------------
Also, if I'm understanding your scenario/question correctly, there should be no reason you need to make any modifications to the source database (eg, no need to drop any segments or partitions).
We just need to help you understand how to create a new/target database so that you can perform a dump-n-load and have the segments/partitions show up on the 'correct' disk fragments ... and you can either do some research on the contents of the master..sysusages contents ... or provide your ASE version and the output from sp_helpdb.