Package: git-buildpackage Version: 0.9.10+nmu1 Severity: minor Hi Guido,
It appears that the initial gbp push is pushing branches in a non-deterministic order. The details are described below: https://lists.debian.org/debian-go/2018/12/msg00023.html https://lists.debian.org/debian-go/2018/12/msg00022.html Why it matters is that, according to Alexandre Viau at https://lists.debian.org/debian-go/2018/10/msg00024.html When we initially creating the repositories, it is important to push the debian/sid branch first, as The first branch pushed will be the default branch on salsa. He "had to change them in the gitlab gui. We wouldn't have to do that if you pushed the debian branches first." So please consider pushing the current branch first for the initial gbp push. Thanks Tong -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages git-buildpackage depends on: ii devscripts 2.17.6+deb9u1 ii git 1:2.11.0-3+deb9u3 ii man-db 2.7.6.1-2 ii python3 3.5.3-1 ii python3-dateutil 2.6.1-1 ii python3-pkg-resources 33.1.1-1 ii sensible-utils 0.0.9+deb9u1 Versions of packages git-buildpackage recommends: ii pbuilder 0.228.7 ii pristine-tar 1.38 ii python3-requests 2.12.4-1 ii sbuild 0.77.1-2 Versions of packages git-buildpackage suggests: pn python3-notify2 <none> ii sudo 1.8.19p1-2.1 ii unzip 6.0-21 -- no debconf information
