rosdep: add Ignition Citadel

[chapulina]

Some of these keys are already being used by the ros_ign packages to bloom it into https://packages.osrfoundation.org:

https://github.com/osrf/osrf-rosdep/blob/master/ignition/ignition.yaml

---

This is a follow up to #24646

[nuclearsandwich]

I don't believe these packages are available for older supported versions of Debian or Ubuntu.

I think these keys need to be rewritten so they're scoped to just focal and buster. e.g.

ignition-citadel:
  debian:
    buster: [ignition-citadel]
    '*': null
  ubuntu:
    focal: [ignition-citadel]
    '*': null

[sloretz]

'*': null

@nuclearsandwich does the null need to be explicitly stated? If so, should I add it to #24646 ?

[nuclearsandwich]

@nuclearsandwich does the null need to be explicitly stated? If so, should I add it to #24646 ?

No you're right. I had my wires crossed. the explicit null is used when they key is defined for most distributions but not one particular one. So the PR could either assume forward compatibility:

keyname:
  debian:
    '*': [packagename]
    jessie: null
    stretch: null
  ubuntu:
    '*': [packagename]
    bionic: null
    xenial: null

or not:

keyname:
  debian:
    buster: [packagename]
  ubuntu:
    focal: [packagename]

Given the fact that these packages are versioned and many of them are being imported directly not upstreamed I'd suggest the latter form.

[chapulina]

scoped to just focal and buster

done

[nuclearsandwich]

@chapulina it looks like there are some outstanding checks failing. Alphabetical ordering is at least part of it.

   ERR: list out of alphabetical order line 2609.  'libignition-math6-dev' should come before 'libignition-math6-eigen3'
  ERR: list out of alphabetical order line 2639.  'libignition-plugin-dev' should come before 'libignition-plugin1'

[chapulina]

Sorry for overlooking that, @nuclearsandwich . Updated in 73aa168

[nuclearsandwich]

A note for fellow reviewers: Not all of these packages are available upstream. Those that are not have been imported into the ROS buildfarm bootstrap repository directly (see ros-infrastructure/reprepro-updater#75)