tickets #108389


Cisco openh264 distribution

Added by lkocman almost 2 years ago. Updated about 1 year ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


Hello team,

may I please ask for an assistance with

I want to make sure that we provide cisco "optimal" instructions for
how to rsync data from specific project/rpms to the inside of the ticket. Feel free to
ping me with any text that should be added to description, or simply
write a comment and I'll update it afterwards.

Ideally the repo publishing should be disabled on the OBS side, so
people dont have an easy way to consume rpm from OBS (that's why we're
doin it in the first place). I did a one time publish to simplify
rsync, but I'd appreciate something that does not involve publishing of
repo on our side (unless that repo would redirect get to

Last step will be to have a direstory/repository on that will contain these openh264 rpms, but will
redirect all get requests to the same file hosted on$file

Neal mention that he'll bump the dist tag, so we have unique filenames
per distribution, as the host seem to host all files within a single

Meanwhile, our SUSE TAM is raising the issue on cisco calls so we get
"some" priority.

Thank you

Best regards

Lubos Kocman
openSUSE Leap Release Manager

Actions #1

Updated by pjessen almost 2 years ago

  • Subject changed from Cisco openh264 distsribution to Cisco openh264 distribution
  • Private changed from Yes to No
Actions #2

Updated by Pharaoh_Atem almost 2 years ago

I've already completed the work to add a DistTag to all the packages built in the repository:

Actions #3

Updated by lrupp almost 2 years ago

  • Status changed from New to Closed
  • Assignee set to Pharaoh_Atem
  • % Done changed from 0 to 100

Closing here, as it looks like Pharaoh_Atem already provided all relevant documentation.

Actions #4

Updated by lkocman about 1 year ago

  • Status changed from Closed to Workable
On Donnerstag, 5. Januar 2023, 16:18:51 CET Lubos Kocman wrote:
> Hello autobuild team!
> We've discussed this with Adrian yesterday as part of
> I'd like to ask you to set up custom "repodata-only" publishing for our 
> openh264 projects which are using <access><disabled/></access> to 
> control who can access them and utilize redirect rule for rpms to cisco 
> infra (will be discussed with *heroes later today).

The way how fedora implemented this is actually independend of
repository building.

They offer the full repository on their server, but they redirect
for the rpm files to the cisco server.

So all what we need to do is to publish to a special directory on
some vhost (like, but all the setup 
magic for this must be done on that vhost setup.

so, just tell use to which rsync module on which server we need to sync.


> openSUSE:Factory:openh264
> openSUSE:Factory:openh264:POST (snapshot of not yet published rpms 
> emailed to cisco)
> openSUSE:Factory:openh264:PUBLISHED (published repodata on download-o-o)
> I think it would be safest to "get rid of rpms" as part of publishing 
> for all of these projects above as we've already faced accidentally 
> enabled publishing in the past. And this would be considered a safety 
> mechanism.
> The publish flag would be enabled only for 
> openSUSE:Factory:openh264:PUBLISHED to where I'd release data *manually.
> As part of the publishing, we expect to publish repodata for both 
> version-less openSUSE_Leap (for all Leap versions built against the 
> oldest supported) and openSUSE_Tumbleweed.
> The publish location for Leap would by default have Tumbleweed in the 
> path which looks a bit odd. If you could think of any solution for a 
> "single Leap repo" I'd be more than happy.
> [0]
> [1]
> Thank you very much in advance
> Lubos Kocman

Actions #5

Updated by lkocman about 1 year ago

Let's do it that way, I know we've discussed it would be an overkill, however it would allow us to do listing with redirect. We just need to make sure this module is not accessible to mirrors.

Actions #6

Updated by lkocman about 1 year ago

  • Assignee changed from Pharaoh_Atem to cboltz

So we need a custom rsync module to which we will publish from

with either (that would be excluded from offering to mirrors)

This needs to be set up with apache redirect of rpm files: (host depends on the rsync module / subdomain above)$arch/libopenh264-7-2.3.1-8.suse1500.1.x86_64.rpm ->$arch/libopenh264-7-2.3.1-8.suse1500.1.x86_64.rpm ->

(this is just example rpm we need *.rpm -> *.rpm)

Actions #7

Updated by lkocman about 1 year ago

  • Assignee deleted (cboltz)

Leaving unassigned.

Actions #8

Updated by crameleon about 1 year ago

  • % Done changed from 100 to 70

http[s]:// set up. RPM files redirect to for now, will change to once the rest of the setup is complete.


  • how do I reload rsyncd-internal.conf ?
  • how do I configure the new vhost to use the modern directory listing ?
Actions #9

Updated by crameleon about 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to crameleon
  • % Done changed from 70 to 90

Questions resolved, directory index theme configured (besides some minor CSS artifacts).

Actions #10

Updated by crameleon about 1 year ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

Redirect for to configured.

Actions #11

Updated by lkocman about 1 year ago

Thank you folks! Now it's on autobuild side.

Actions #12

Updated by lkocman about 1 year ago

Thanks to all involved. Last part is on me. I'll send zip with rpms to cisco and ask to republish.
Big thanks to all who worked on the setup!


Also available in: Atom PDF