Re: [pkg-go] GitLab CI: git-buildpackage and ratt

On Thu, Mar 1, 2018 at 2:41 PM, Martín Ferrari wrote: > On 01/03/18 07:58, Michael Stapelberg wrote: > > I’m assuming you have read https://pkg-go.alioth.debian.org/ci.html > > already. If not, start there. > > I had read it, but it was good to read it again. > > > Instead of

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

Hi, Thanks for all the info, now it is a lot more clear! On 04/03/18 08:48, Michael Stapelberg wrote: > * What kind of control do we have over it? > Not sure I follow. Can you make this question more specific? Wondering about if it is posible to manually trigger runs, re-tries, etc. --

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

On Sun, Mar 4, 2018 at 6:29 PM, Martín Ferrari wrote: > Hi, > > Thanks for all the info, now it is a lot more clear! > Great! I updated ci.html with the link as discussed. > > > On 04/03/18 08:48, Michael Stapelberg wrote: > > * What kind of control do we have over it?

[pkg-go] golang-github-git-lfs-wildmatch_0.0~git20180219.8a05186-1_amd64.changes is NEW

binary:golang-github-git-lfs-wildmatch-dev is NEW. binary:golang-github-git-lfs-wildmatch-dev is NEW. source:golang-github-git-lfs-wildmatch is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a

[pkg-go] Processing of golang-github-git-lfs-wildmatch_0.0~git20180219.8a05186-1_amd64.changes

golang-github-git-lfs-wildmatch_0.0~git20180219.8a05186-1_amd64.changes uploaded successfully to localhost along with the files: golang-github-git-lfs-wildmatch_0.0~git20180219.8a05186-1.dsc golang-github-git-lfs-wildmatch_0.0~git20180219.8a05186.orig.tar.xz

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

On 04/03/18 21:39, Michael Stapelberg wrote: > Ah! Runs will automatically be triggered as soon as a gitlab-ci.yml file > is found. You can retry any run with the “retry” button next at the top > right. See for > example https://salsa.debian.org/go-team/packages/ethflux/-/jobs/8312 > > Does that

[pkg-go] gb is marked for autoremoval from testing

gb 0.4.4-2 is marked for autoremoval from testing on 2018-03-26 It is affected by these RC bugs: 891445: gb: FTBFS and Debci failure: test failure ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org

[pkg-go] golang-github-spf13-cast 1.2.0-1 MIGRATED to testing

FYI: The status of the golang-github-spf13-cast source package in Debian's testing distribution has changed. Previous version: 1.1.0-1 Current version: 1.2.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a

[pkg-go] acbuild REMOVED from testing

FYI: The status of the acbuild source package in Debian's testing distribution has changed. Previous version: 0.4.0+dfsg-1 Current version: (not in testing) Hint: Bug #888922: acbuild: build dependency

[pkg-go] golang-github-pkg-xattr 0.2.2-1 MIGRATED to testing

FYI: The status of the golang-github-pkg-xattr source package in Debian's testing distribution has changed. Previous version: 0.2.0+git20170313.4.2c7218a-1 Current version: 0.2.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing

[pkg-go] golang-github-go-redis-redis 6.9.2-1 MIGRATED to testing

FYI: The status of the golang-github-go-redis-redis source package in Debian's testing distribution has changed. Previous version: 6.7.4-1 Current version: 6.9.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times