Package: dgit Version: 0.14 Severity: normal I have just did a dgit push --new of this package.
joey@darkstar:~/tmp/nnn>dgit clone --new git-remote-gcrypt canonical suite name for unstable is sid fetching existing git history remote: Counting objects: 478, done. remote: Compressing objects: 100% (303/303), done. Resolving deltas: 100% (171/171), done. From git+ssh://git.debian.org/git/dgit-repos/repos/git-remote-gcrypt * [new ref] refs/dgit/sid -> dgit/dgit/sid * [new tag] debian/0.20130908-1 -> debian/0.20130908-1 dgit: package git-remote-gcrypt does not exist in suite unstable dgit left the repository with no branch checked out. When I manually checked out dgit/dgit/sid, eveything was there. Seems to me that clone with --new (or possibly without --new) should reflect the current state of the package in dgit-repos, whether or not it has gotten into the debian archive yet. Otherwise, there would be a delay before other collaborators can check out my package. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dgit depends on: ii devscripts 2.13.3 ii dpkg-dev 1.17.1 ii git [git-core] 1:1.8.4~rc3-1 ii libdpkg-perl 1.17.1 ii libwww-perl 6.05-1 ii perl [libdigest-sha-perl] 5.18.1-3 ii realpath 1.18 Versions of packages dgit recommends: ii openssh-client [ssh-client] 1:6.2p2-6 Versions of packages dgit suggests: pn sbuild <none> -- no debconf information -- see shy jo
signature.asc
Description: Digital signature
