Debian 11

Debian 11.

This project does not contain any packages

Comments 2

Ki Mi's avatar


Assume we have a package with the following files in package:

  • wonderproj-beta_0.0.1-1.dsc
  • wonderproj-beta_0.0.1-1.debian.tar.gz
  • wonderproj-beta_0.0.1.orig.tar.bz2
How to make the OpenSUSE Build Service understand that it should use different .dsc files for different Debian-based distributions?

Such as:

  • Debian_11
  • Debian_Unstable
  • xUbuntu_22.04

Following the guide, it says we should do it this way:

  • wonderproj-beta-Debian_Unstable.dsc
  • wonderproj-beta-Debian_11.dsc
  • wonderproj-beta-xUbuntu_20.04.dsc
  • wonderproj-beta-xUbuntu_22.04.dsc
  • wonderproj-beta_0.0.1-1.debian.tar.gz
  • wonderproj-beta_0.0.1.orig.tar.bz2

An example can be found in package snapper here.

However, it seems that by adding more than one .dsc file, the build service marks the distribution as excluded...

So the question is, how to do it then, when the guide doesn't seem to work?

Is it maybe a temporary bug but supposed to be fixed in the build service later on?

Nicholas Brown's avatar

Look at the meta for the project I notice that this uses the following 3 sources:

<repository name="standard">
  <download arch="x86_64" url="" repotype="deb">

<repository name="update">
<download arch="x86_64" url="" repotype="deb">

<repository name="backports">
   <download arch="x86_64" url="" repotype="deb">

I wonder if should also include the debian security source? This will contain security fixes that are neither in update or standard (until the next point release of standard)

deb bullseye-security main

See: for full details of debian sources.

openSUSE Build Service is sponsored by