Package: dgit
Version: 1.4
Severity: wishlist

Hi,

after a "dgit push" of the package src:pdfrw I got a REJECT from
ftpmaster because "Source-only uploads to NEW are not allowed". Since
the source package is not yet in Debian I guess this talks about an
upload to binary-NEW.

Here are two issues I have with this (close this bug as you see fit):

 1. dgit is Debian specific so I guess it might be reasonable to assume
    that it encodes Debian specific rules like the above such that I can
    never do a "dgit push" of a source-only .changes file if there are
    new binary packages in the upload compared to the last

 2. I do not see documentation of how to fix this situation. Is the only
    way around to bump my Debian revision to -2, rebuild with binaries
    and then do "dgit push" again? Or is there a way to mangle my
    source-only .changes file file I already have such that it contains
    the new binary packages while at the same time doesn't break any of
    dgits expectations?

Thanks!

cheers, josch


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dgit depends on:
ii  ca-certificates            20150426
ii  coreutils                  8.23-4
ii  curl                       7.44.0-1
ii  devscripts                 2.15.8
ii  dpkg-dev                   1.18.3
ii  dput                       0.9.6.4
ii  git [git-core]             1:2.5.1-1
ii  libdpkg-perl               1.18.3
ii  libjson-perl               2.90-1
ii  libwww-perl                6.13-1
ii  perl [libdigest-sha-perl]  5.20.2-6

Versions of packages dgit recommends:
ii  openssh-client [ssh-client]  1:6.9p1-1

Versions of packages dgit suggests:
ii  sbuild  0.66.0-2

-- no debconf information

Reply via email to