golang-gogoprotobuf_0.2-3_amd64.changes uploaded successfully to localhost
along with the files:
golang-gogoprotobuf_0.2-3.dsc
golang-gogoprotobuf_0.2-3.debian.tar.xz
gogoprotobuf_0.2-3_amd64.deb
golang-github-gogo-protobuf-dev_0.2-3_all.deb
golang-gogoprotobuf-dev_0.2-3_all.deb
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 14 Apr 2016 20:54:10 +1000
Source: golang-gogoprotobuf
Binary: golang-gogoprotobuf-dev golang-github-gogo-protobuf-dev gogoprotobuf
Architecture: source amd64 all
Version: 0.2-3
Distribution: unstable
Urgency:
Your message dated Thu, 14 Apr 2016 10:21:59 +
with message-id
and subject line Bug#819994: fixed in golang-gogoprotobuf 0.2-2
has caused the Debian Bug report #819994,
regarding golang-gogoprotobuf: FTBFS (32-bit or BE): many tests fail
to be marked as
On 14 April 2016 at 19:16, Michael Stapelberg wrote:
> Thanks for the patch, it’s now merged and uploaded.
Awesome, thanks for that.
> I’d prefer if you could send such patches in a bug report instead of to
> mailing lists which I don’t actively read :).
Noted!
> In
dh-make-golang_0.0~git20160414.0.c4f61b1-2_amd64.changes uploaded successfully
to localhost
along with the files:
dh-make-golang_0.0~git20160414.0.c4f61b1-2.dsc
dh-make-golang_0.0~git20160414.0.c4f61b1.orig.tar.xz
dh-make-golang_0.0~git20160414.0.c4f61b1-2.debian.tar.xz
Hi,
On Thu, 14 Apr 2016, Michael Stapelberg wrote:
> I didn’t see this before pushing a new version.
What new version? The new version looks like my changes only.
> Why did you not commit your changes to the collab-maint git repository? :(
Because it's not in collab-maint but in pkg-go which I
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 14 Apr 2016 19:50:36 +1000
Source: golang-gogoprotobuf
Binary: golang-gogoprotobuf-dev golang-github-gogo-protobuf-dev gogoprotobuf
Architecture: source amd64 all
Version: 0.2-2
Distribution: unstable
Urgency:
binary:golang-github-dylanmei-winrmtest-dev is NEW.
source:golang-github-dylanmei-winrmtest 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 good
OpenPGP signature and file hashes are valid),
Hi,
there's a problem with packaging Packer [1]: github-packer-community-winrmcp
[2] needs
the sources of Packer (import "github.com/mitchellh/packer/common/uuid"), while
Packer
needs the sources of winrmcp (import
"github.com/packer-community/winrmcp/winrmcp") [3],
so there's a mutual
Just an upstream update and a few minor tweaks in d/control to fix Lintian
warnings.
Please review and upload.
Tim.
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Pkg-go-maintainers mailing list
Package: wnpp
Severity: wishlist
Owner: Tim Potter
X-Debbugs-CC: debian-de...@lists.debian.org,
pkg-go-maintainers@lists.alioth.debian.org
* Package name: golang-github-gorilla-context
Version : 0.0~git20160226.0.1ea2538-1
Upstream Author : Gorilla web toolkit
*
New package uploaded to alioth for Docker 1.11
Please review and upload.
Tim.
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
On 15/04/2016 10:48 am, "Tianon Gravi" wrote:
>
> On 14 April 2016 at 15:46, Tianon Gravi wrote:
> > I think this block is why that latest upload is causing everything to
> > fail to build -- we removed GOPATH from "sub build", but didn't add
> >
On 14 April 2016 at 15:50, Michael Hudson-Doyle
wrote:
> Yeah, that's the problem. I was testing with a package that set GOPATH in
> rules :-( I sent the same fix to the bug, or at least tried to...
Oh yep, you totally did: https://bugs.debian.org/821000#20
(which
On 13 April 2016 at 17:43, Michael Hudson-Doyle
wrote:
> @@ -156,7 +161,6 @@ sub get_targets {
> sub build {
> my $this = shift;
>
> -$ENV{GOPATH} = $this->{cwd} . '/' . $this->get_builddir();
> if (exists($ENV{DH_GOLANG_GO_GENERATE}) &&
On 14 April 2016 at 15:46, Tianon Gravi wrote:
> I think this block is why that latest upload is causing everything to
> fail to build -- we removed GOPATH from "sub build", but didn't add
> "_set_gopath" like we did down in "sub test" to replace it, ala:
(and I'm happy to
Daniel Stender:
> Hi,
>
> there's a problem with packaging Packer [1]: github-packer-community-winrmcp
> [2] needs
> the sources of Packer (import "github.com/mitchellh/packer/common/uuid"),
> while Packer
> needs the sources of winrmcp (import
> "github.com/packer-community/winrmcp/winrmcp")
On 15 Apr 2016, at 8:27 AM, Potter, Tim (HPE Linux Support)
wrote:
>
> New package uploaded to alioth for Docker 1.11
>
> Please review and upload.
Nuts - fell for the old package already present under a different name -
golang-context.
Will update original package.
On 15 Apr 2016, at 8:29 AM, Potter, Tim (HPE Linux Support)
wrote:
>
> On 15 Apr 2016, at 8:27 AM, Potter, Tim (HPE Linux Support)
> wrote:
>>
>> New package uploaded to alioth for Docker 1.11
>>
>> Please review and upload.
>
> Nuts - fell
On Thursday, 14 April 2016 10:38:15 PM AEST Daniel Stender wrote:
> I have an idea but wanted to poll, how could get they both in the best way?
Not sure for "best way" but here some ideas how this problem could be
addressed:
Sometimes one dependency required only by tests. In such case it may
On Thursday, 14 April 2016 10:29:55 PM AEST Potter, Tim (HPE Linux Support)
wrote:
> Nuts - fell for the old package already present under a different name -
> golang-context.
I might be helpful to check name space with "apt-file search" to detect
whether files already provided by different
Your message dated Fri, 15 Apr 2016 09:59:39 +1000
with message-id <162303484.Rab39s8GEy@deblab>
and subject line Re: Bug#821012: etcd: Incorrect use of readlink in sysvinit
script
has caused the Debian Bug report #821012,
regarding etcd: Incorrect use of readlink in sysvinit script
to be marked
On 15 April 2016 at 03:55, Martín Ferrari wrote:
> On 14/04/16 01:43, Michael Hudson-Doyle wrote:
>> Built-Using for a binary is meant to include all packages that are included
>> in
>> the binary itself, but using Build-Depends only pulls in the direct
>> dependencies. Use go
I didn’t see this before pushing a new version.
Why did you not commit your changes to the collab-maint git repository? :(
On Thu, Apr 7, 2016 at 11:29 AM, Raphael Hertzog wrote:
> Control: tags 819472 + patch
> Control: tags 819472 + pending
>
> Dear maintainer,
>
> I've
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 14 Apr 2016 09:10:21 +0200
Source: dh-make-golang
Binary: dh-make-golang
Architecture: source amd64
Version: 0.0~git20160414.0.c4f61b1-2
Distribution: unstable
Urgency: medium
Maintainer: pkg-go
dh-make-golang_0.0~git20160414.0.c4f61b1-2_amd64.changes uploaded successfully
to localhost
along with the files:
dh-make-golang_0.0~git20160414.0.c4f61b1-2.dsc
dh-make-golang_0.0~git20160414.0.c4f61b1-2.debian.tar.xz
dh-make-golang-dbgsym_0.0~git20160414.0.c4f61b1-2_amd64.deb
Your message dated Thu, 14 Apr 2016 07:34:13 +
with message-id
and subject line Bug#819472: fixed in dh-make-golang 0.0~git20160414.0.c4f61b1-2
has caused the Debian Bug report #819472,
regarding dh-make-golang builds not accepted due to invalid
On Thu, Apr 14, 2016 at 12:57 AM, Raphael Hertzog
wrote:
> Hi,
>
> On Thu, 14 Apr 2016, Michael Stapelberg wrote:
> > I didn’t see this before pushing a new version.
>
> What new version? The new version looks like my changes only.
>
I packaged a new upstream snapshot.
>
>
dh-make-golang-dbgsym_0.0~git20160414.0.c4f61b1-1_amd64.deb: APT could not
parse Built-Using field
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
dh-make-golang_0.0~git20160414.0.c4f61b1-2.dsc: Refers to non-existing file
'dh-make-golang_0.0~git20160414.0.c4f61b1.orig.tar.xz'
Perhaps you need to include the file in your upload?
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 13 Apr 2016 15:06:16 +0200
Source: golang-github-masterzen-winrm
Binary: golang-github-masterzen-winrm-dev winrm
Architecture: source all amd64
Version: 0.0~git20160323.0752679-1
Distribution: unstable
Urgency:
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 14 Apr 2016 13:34:30 +1000
Source: golang-github-hashicorp-go-retryablehttp
Binary: golang-github-hashicorp-go-retryablehttp-dev
Architecture: source all
Version: 0.0~git20151208.0.24fda80-1
Distribution: unstable
golang-gogoprotobuf_0.2-2_amd64.changes uploaded successfully to localhost
along with the files:
golang-gogoprotobuf_0.2-2.dsc
golang-gogoprotobuf_0.2-2.debian.tar.xz
gogoprotobuf_0.2-2_amd64.deb
golang-github-gogo-protobuf-dev_0.2-2_all.deb
golang-gogoprotobuf-dev_0.2-2_all.deb
dh-make-golang_0.0~git20160414.0.c4f61b1-1_amd64.changes uploaded successfully
to localhost
along with the files:
dh-make-golang_0.0~git20160414.0.c4f61b1-1.dsc
dh-make-golang_0.0~git20160414.0.c4f61b1.orig.tar.xz
dh-make-golang_0.0~git20160414.0.c4f61b1-1.debian.tar.xz
Thanks for the patch, it’s now merged and uploaded.
I’d prefer if you could send such patches in a bug report instead of to
mailing lists which I don’t actively read :). In fact, I’d say it’s long
overdue to make this package team-maintained. The repository is already in
collab-maint, so if you
On 14/04/16 01:43, Michael Hudson-Doyle wrote:
> Built-Using for a binary is meant to include all packages that are included in
> the binary itself, but using Build-Depends only pulls in the direct
> dependencies. Use go list and dpkg-query --search instead to find out which
> (debian) packages
golang-github-dylanmei-winrmtest_0.0~git20151226.0256178-1_amd64.changes
uploaded successfully to localhost
along with the files:
golang-github-dylanmei-winrmtest_0.0~git20151226.0256178-1.dsc
golang-github-dylanmei-winrmtest_0.0~git20151226.0256178.orig.tar.xz
Package: etcd
Version: 2.2.5+dfsg-1
Severity: important
Tags: newcomer
Dear Maintainer,
The copy of sysvinit script in the etc package tries to get the name of the
package using:
NAME=$(basename $(readlink $0))
Unfortunately, this fails due to the incorrect invocation of readlink. This
38 matches
Mail list logo