On 10/24/2016 10:19 AM, Og Maciel wrote: > All, > > The QE Team is considering automating the upload of DRPM packages via > API/CLI/UI and we would like to ask you for some feedback. The test > case is listed here: https://github.com/SatelliteQE/robottelo/issues/3853 > > Since this is an upload (and not a sync) task, it seems that DRPM > packages behave differently when being uploaded. For example, if you > create a single repository and manually upload a DRPM package, I'd > expect to see it show up in the filesystem (and not the UI). However, > once you import the DRPM you actually see a RPM listed in the > filesystem. If you synchronize a repository that has both RPMs and > DRPMs, you see both in the filesystem. > > We're a bit confused as to how a DRPM becomes a RPM in the former use > case... > > Looking forward to your feedback, > > Og > -- > You received this message because you are subscribed to the Google > Groups "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout.
Katello doesn't support uploading DRPMs. I think what you are seeing with regard to them 'becoming' rpms is just a side effect of the fact that drpms look a lot like regular rpms. They have an rpm header just like a normal rpm. Since katello only supports uploading rpms to yum repos and what you are uploading *looks* like an rpm, it is uploaded as an rpm and pulp imports it as such. We would need an RFE to support such a feature. -Justin -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
