Wiki

• FrontPage
• RecentChanges
• FindPage
• HelpContents
• Lomiri/Packaging

Debian Lomiri Packaging Team

The Lomiri packaging is performed under the umbrella of the Debian UBports Team (named after the UBports Foundation who is the legal entity behind upstream Lomiri).

• Git: https://salsa.debian.org/ubports-team

• DDPO: https://qa.debian.org/developer.php?login=team%2Bubports%40tracker.debian.org

Communication

• IRC: #debian-ubports on OFTC (irc.debian.org)

Work coordination

There are several resources to pick up tasks from:

• UBports Team's Salsa Board: https://salsa.debian.org/groups/ubports-team/-/boards

• UBports Team's UDD overview: https://udd.debian.org/dmd/?email1=team%2Bubports%40tracker.debian.org&email2=&email3=&packages=&ignpackages=&format=html#todo

If you want to work on a task on the Salsa board, simply assign yourself to the task (if you can't do that, ask for becoming a team member, either via GitLab's UI or via IRC).

If you want to work on a task from the UDD overview page, please coordinate via IRC and for bigger tasks possibly add the task to the Salsa board of the Debian UBports' team.

Upstream packaging synchronization

Both UBports upstream (on GitLab) and Debian downstream (on Salsa), technically separate teams, have their own Debian packaging trees for Lomiri projects. There is an ongoing coordinated effort to reduce the differences between the two. The upstream repositories that need to be synchronized can be found by their GitLab issues labelled "Topic: salsa2ubports DEB syncing", see this issue board.

One important aim of this effort is to make it easy for upstream developers (and upstream projects' contributors) to build (and run, test, develop) the upstream projects as Debian packages on downstream Debian systems, be it Ubuntu Touch, regular Ubuntu, or Debian.

It is impossible to have identical upstream and downstream packages that would not trigger lintian warnings on either side. The chosen approach is to keep the delta minimal at the cost of these warnings.

Some non-obvious things that shall be synchronized:

• to upstream: debian/upstream/metadata, debian/watch, etc.,

• to downstream: older versions of dependencies that would not be necessary for Debian (unstable), but are required by supported Ubuntu versions (noble, for instance).

Some things that shall not be synchronized:

• debian/source/format (native for upstream, non-native for downstream),

• debian/changelog,

• Maintainer: field in debian/control

• VCS metadata in debian/control,

• CI configuration.

Source packages can refer to this Wiki section from their documentation (debian/README.source) to explain the above conventions and resulting surprises to unaware developers, contributors, and users.

Package Naming for Lomiri Apps

Native Lomiri apps, also if provided by 3rd party developers (i.e. all apps that are not located upstream at https://gitlab.com/ubports/development/apps) shall be named after this pattern:

• src:pkg name: lomiri-<foo>-app (where <foo> is the upstream app name)

• bin:pkg name: same name
• packaging Git repo on salsa.debian.org: same name

Exceptions to this are:

• TELEports
• Dekko

• ?DeltaTouch

• ... (more to come, maybe)

Ideally, this naming style/convention gets communicated to the upstream authors of the app, so they get informed and are provided with the opportunity to veto or discuss this naming scheme. If upstream authors contradict to our naming policy, we will see where the discussion goes (please involve other Debian Lomiri maintainers in the discussion, if that happens).

NEW Packages to be created for Lomiri