On 16/07/15 13:59, Andreas Beckmann wrote:
On 2015-07-16 13:22, Martín Ferrari wrote:
Thanks for reporting. I have been thinking about a good way to solve
this, but still did not arrive to any good solution. These files are
examples to be used as an starting point for the user to build
in the compiler, as this seems it
could be related to undefined behaviour when casting to unsigned values
(the upstream bug has more details).
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http
upstream to see if they know what can be causing this.
Thanks again.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
instances of expected 1, got 0. I will get some 32 bit machine and
take a look.
Thanks for reporting!
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman
keep that one, but it would be good to create transitional packages and
to sync maintainer stuff.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman
uild system. Once applied, prometheus-pushgateway can be built
> reproducibly in our reproducible toolchain.
heh, I had committed a similar patch last week (although I missed the
hostname problem). Now I have a good excuse for uploading again!
Thanks!
So, I can reliably reproduce this if I run the build with nice and have
some processes eating the cpu away. I have added the information to the
upstream bug, but in the meantime I am uploading a new release that just
disables these tests.
--
Martín Ferrari (Tincho
with the new script, or if you feel strongly
against the new functionality, please let me know.
Tincho.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin
hat for policy
> queues.
The changes I did yesterday to the post-receive git hook supposedly
should already mark a bug as pending the moment the change is pushed.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.
API only.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
wanted
> to change the team policy document on that before accepting the PR,
> but I think we all agree by now.
I have not noticed that was being discussed. But you can assume my +1 on
that PR, obviously :)
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
leases, I
patched upstream and made an orig.tar.gz from that, but I should have
made a Debian patch instead.
> Also, could you take a stab at this bug please and package a new snapshot?
Sure, I will look into it later today or tomorrow.
--
Martín Fer
is in a saner state :)
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
On 11/09/15 12:59, Martín Ferrari wrote:
> We currently have this package in packages/golang-uuid.git, whereas
> there is a golang-github-pborman-uuid.git that never got uploaded
> because of the duplication. This is pretty confusing.
>
> I am going to remove the latter, and re
make it easier for them to work on packages, and for
DDs to sponsor them.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
On 25/05/16 10:11, Michael Hudson-Doyle wrote:
> OK. Reload https://github.com/mwhudson/autodep8/compare/master...go-support
> again?
Looks good. Now, I still haven't delved into this. How could I test it?
--
Martín Ferrari (Tincho)
___
04:48:27 -0600
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Built-Using is to be used:
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-built-using:
Thanks for the clarification. I am always confused by this field. Maybe
we should do a mass-fix of this.
--
Martín Ferrari (Tincho)
___
Pkg-go-main
Using field in control..
>
> Because it was used on arch-all -dev package shipping sources...
Sorry about that, I got it now.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
util_2.1.orig.tar.gz
upstream/2.1
I also fixed some tests that fail, and various bits. I am just confused
as to why you removed the Build-Using field in control..
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers
in working on it.
In particular, I have been experiencing some crashes that have been
fixed upstream, and there is a big release available too.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http
Cool that you can do it so easy in cgit. How about Gitg for a change?
> I don't usually inspect commits using web interface to git...
Actually, the link he posted is equivalent to doing "git log debian/",
which is also what I do to filter upstream commits for
contributor
n deb source does specify 0.12.0rc1.
You are completely right. Sadly I only realised this after uploading,
and fixing it would require some version number hacking..
I was waiting for the final 0.12.0 to be released, but since that is
taking a while, I should try to fix this someh
again, sorry for being this late to the conversation, but I hope we
can discuss this approach for a next version.
Tincho.
[1]:
https://anonscm.debian.org/cgit/pkg-perl/packages/libmemcached-libmemcached-perl.git/commit/?id=e780b94
--
Martín Ferrari (Tincho)
___
On 09/02/16 01:44, Alexandre Viau wrote:
> Hello,
>
> On 08/02/16 12:49 AM, Martín Ferrari wrote:
>> Although I presume this change might not be acceptable for some people,
>> I think the notes about changelog handling would be a good addition.
>
> +1, I agree with
Thanks for the patch!
I am preparing version 0.17.0, and will include this with the upload.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
ssed a couple of months ago?
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
On 28/03/16 19:16, Martín Ferrari wrote:
> Hi all,
>
> I filed today the bug referenced below, and got me thinking about the
> wider issue of having hundreds of arch:all packages which might not be
> working at all on certain architectures, waiting for some arch:any
> pa
gathering?
Is any of you planning on going to the camp?
Would you consider going if we organised a proper sprint?
Cheers,
Tincho.
[0] https://wiki.debian.org/DebianEvents/Europe/2016/DSC
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
On 23/03/16 01:36, Dmitry Smirnov wrote:
> On Wednesday, 23 March 2016 1:17:27 AM AEDT Martín Ferrari wrote:
>> Well, now we have two versions of the same thing in the repository,
>> which will need to be maintained separately. We could have instead fixed
>>
reopen 819214
severity 819214 important
forwarded 819214 https://github.com/onsi/ginkgo/issues/247
thanks
Hi,
You are right, this needs to be properly addressed. I have reopened the
bug with a lower severity (as the build is succeeding now), and created
a bug upstream.
release, so then you can go into ~
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
ldb/issues/140
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Source: golang-fsnotify
Version: 1.2.9-1
Severity: important
Tags: upstream
As I reported upstream (https://github.com/fsnotify/fsnotify/issues/130),
fsnotify does not seem to work at all in ppc64el. I noticed this when trying to
solve a FTBFS in prometheus, that can be tracked down to this
ndards-Version to 3.9.8 (though Lintian hasn't caught up yet), and
> perhaps update Vcs-Git to
> https://anonscm.debian.org/git/pkg-go/packages/golang-fsnotify.git
> too. :-)
Will do, although I am not sure if i will have any free time before
monday (weekend away). So feel
tool for team work. But
needs conventions to be followed, like not setting the distribution to
unstable until the package is ready for upload, and stuff like that.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainer
ing
gets broken. Please, let's keep repos consitent internally, otherwise it
is a big mess.
To tidy this up, I will need to rewrite a bit of history, so please,
reset your repos.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg
ib/go/src/golang.org/x/sys/unix (from $GOROOT)
>>
>> /<>/prometheus-0.18.0+ds/obj-x86_64-linux-gnu/src/golang.org/x/sys/unix
>> (from $GOPATH)
This is actually a bug in fsnotify, introduced by me :) The dependency
is present in build-depends, but not in the "b
On 26/04/16 18:48, Martin Michlmayr wrote:
> * Martín Ferrari <tin...@tincho.org> [2016-04-26 18:42]:
>>>> src/gopkg.in/fsnotify.v1/inotify.go:19:2: cannot find package
>>>> "golang.org/x/sys/unix" in any of:
>>>>
tes.
Thanks for reporting!
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
ise it. I will upload a fix asap.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
On 20/05/16 13:40, Martín Ferrari wrote:
> Geert,
>
> On 19/05/16 22:18, Geert Stappers wrote:
>
>> Here a report that `debcheckout runc` failed for me.
>> I think it will fail for others too, hence this report.
>
> This looks like a problem with the script in ali
s to be recompiled to be tested anyway.
Actually, the idea is to test the *installed* package. So IMO the best
is to just get the import-path and run go test with the GOPATH set as
you suggest.
I tried this locally and works perfectly.
--
Martín Ferrari (Tincho)
_
alioth admins on IRC
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
On 19/05/16 22:49, Geert Stappers wrote:
>> I will check if a rebuild can be triggered,
>
> Please do. ( consider that as sending a cross for a 'done' )
I did not get a reply. So, let's just upload again.
--
Martín Ferrari (Tincho)
__
On 22/05/16 11:17, Filippo Giunchedi wrote:
> On Fri, May 20, 2016 at 01:37:12PM +0100, Martín Ferrari wrote:
>> Makes sense. For sysvinit I am making it wait almost 20 seconds, and
>> after that the action just fails (instead of SIGKILLing it). If systemd
>> does not have
rent version of dh-golang to jessie?
I was actually waiting for 1.17 to reach testing to backport it, as I
need it for other packages too. Will upload today.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alio
d just patch those tests out (// +build ignore, I guess)
> instead...
Yes. I think that go packages should pass tests as installed. If they
don't, we should fix them
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg
y levels, not really. You have: normal, verbose, and quiet
mode.
Personally, I think this is valuable output, and one can just use
DH_VERBOSE=0
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://l
s have other names
(fixtures is a common one). I think it is a bad idea to add this.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
lay a debug message when copying files to the build tree.
-- Martín Ferrari <tin...@debian.org> Mon, 16 May 2016 01:08:06 +0100
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian
t was uploaded when dh-golang was broken
(1.14). I will check if a rebuild can be triggered, otherwise we need to
upload again.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth
Since nobody has voiced strong concerns about this, I will merge this
change later today or tomorrow and upload.
I wanted to wait for Michael S. to chime in, but I guess he's not
strongly opposed either :-)
On 08/05/16 05:31, Martín Ferrari wrote:
> Hi all,
>
> I have just pushed
ckports), and I think it is probably the most sensible
way forward.
I also get some tooling benefits: gbp will know automatically which
pbuilder to use, if you say dist=dep14
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg
Source: golang-testify
Severity: serious
Justification: Policy 12.5
This package is embedding source code for three other distributions without
attribution in debian/copyright:
vendor/github.com/davecgh/go-spew
vendor/github.com/pmezard/go-difflib
vendor/github.com/stretchr/objx
-- System
here
> more specific in mind), so I think "master" still fits appropriately
> (and is still in line with DEP-14).
Actually, under dep-14 it should be debian/master :)
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maint
like it" is not a great argument, but I am open for convincing
if you make a good case.
In any case, as I said many times before, I would like the team to adopt
a unique standard, but we are pretty far from that.
--
Martín Ferrari (Tincho)
___
ncies, so it might still take a few days.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
> the job done.
Since this is a team, we need to find what is best for the group as a
whole, not only for you.
In any case, GBP is more or less the de-facto standard nowadays, and
helps save a lot of time. I don't really see why you think it is a time
waster for you.
--
Martín Ferrari (Tinch
> other renames
I would like to know more about this.. I dislike transitional packages,
but I thought there was no alternative!
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://list
should review and possibly remove them.
[1] https://contributors.debian.org/source/Go%20packaging%20group
[2] http://paste.debian.net/439726/
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http
an) packages installed the (go) packages that were actually used during
> the build instead.
>
> As a bonus, this is shorter and arguably simpler that what it replaces.
Just one comment. Shouldn't the build-using also include all
build-dependencies, not only the golang ones?
--
M
decide what to delete.
> Some of those repositories are obviously work-in-progress for existing
or to-
> be-submitted ITPs.
Most of these repos are yours actually. I was not too sure about the
work-in-progress, as they don't have a single commit... Hence my
API, and is consistent with
other packages using gopkg (yaml, check).
What do you guys think?
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman
ata/client.cer ->
build/src/github.com/prometheus/prometheus/retrieval/testdata/client.cer
Symlink /usr/share/gocode/src/code.google.com ->
build/src/code.google.com
Symlink /usr/share/gocode/src/github.com/asaskevich ->
build/src/github.com/asaskevich
Thoughts?
--
Martín Fer
On 21/07/16 19:35, Martyn Smith wrote:
> To be honest, I don't even know how to go about doing it.
>
> If you could file it that'd be great!
The simplest way is to run reportbug "ftp.debian.org" and follow the
instructions. I can do it for you :)
--
Mar
severity 832834 normal
thanks
Since there are no news on this, I am downgrading the bug for the time
being, as it is threatening to remove a few rdeps from testing.
I still want to solve the issue, but I can't do anything until it is
reproducible.
On 08/08/16 13:24, Martín Ferrari wrote:
> t
but these are also usually easy to
fix. You can also just create a new branch on each relase, and run your
repack script.
In both cases, you can tag that branch as upstream/1.2.3+ds, and
generate an orig.tar.gz from there.
--
Martín Ferrari (Tincho)
___
ame time, I wonder if monkeytail is going to stay around. The
upstream project has vanished, and the last release was 8 years ago.
Martyn, could you give your opinion on this?
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintain
then went away. It seems the
test is flaky. I will report upstream.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
oblematic, but not sure we can do anything about
it at this point.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
ive with that,
although I know I will do any work needed to prepare security fixes for
the few apps I maintain.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
when a rdep has a security fix. I know it is not ideal, but also it does
not prevent us from providing proper support, IMHO.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.ali
On 03/07/16 13:52, Potter, Tim (HPE Linux Support) wrote:
> Hi everyone. Could someone please upload the latest version of
> golang-github-miekg-pkcs11 from the pkg-go repository? I've applied a
> patch to close a reproducible build issue.
Done!
--
Martín Ferrar
this package and update the bug report?
Thanks.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
On 20/06/16 00:06, Michael Hudson-Doyle wrote:
> Built-Using only makes sense for a package that ships binaries.
I really never knew if it should be present or not on -dev libraries..
But we have it is most of our repos nowadays.
--
Martín Ferrari (Tin
Package: ftp.debian.org
Severity: normal
Upstream has just retired this package as it is now completely replaced by
golang-github-prometheus-log.
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
On 31/01/17 13:01, Julien Cristau wrote:
> On 01/28/2017 08:24 PM, Martín Ferrari wrote:
>> On 28/01/17 16:10, Adrian Bunk wrote:
>>
>>> AFAIK the buildds are building one package at a time,
>>
>> Uhm, don't know about that, but I many times I have experience
re-run the tests with /usr/bin/time on abel and see how much
memory do they take.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
ock (2680815616
in use)
fatal error: out of memory
Yesterday I'd asked for a give back, since in the previous attempt the
tests timed out. I can't reproduce this on the abel porterbox, and it
seems to me like a problem of a very busy buildd more than any bug in
the package.
--
Martín
On 28/01/17 16:24, Martín Ferrari wrote:
>> and the machines where prometheus failed have 4 GB RAM.
>
> abel too...
Now it fails on abel too.. I guess it was always too close to the limit,
and anything else running killed it.
>> "2680815616 in use", that is 2.6
a lot!
[1]: https://buildd.debian.org/status/logs.php?pkg=prometheus=armhf
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852959
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http
solve than daily broken
> compiles.
Also, I think this might be more about addressable user space, because
it is not the OOM killer, but the go runtime that kills the tests.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mail
Hi Lucas,
On 23/02/17 10:27, Lucas Nussbaum wrote:
> Source: golang-prometheus-client
This package has been removed from unstable and testing already. I only
need to remove it from backports now.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintain
dated that package...
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
are failing, but I can't reproduce this in the porterbox.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
e packages (not used directly by prometheus), and in the case of
the consul API because there is an API incompatibility with the package
present in Debian.
I will review this to see again if the vendoring can be removed. But I
disagree with the severity of this bug, the policy only marks this
requirement as a &
fix many bugs in the sample templates.
If you have the chance to make some of these improvements, I'd be happy
to include them in the package.
Thanks for your report.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.aliot
d
a solution.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
but I think the
source cycle is the most important one. Also, I have removed the
transitional package from the cycle, as that was just a mistake.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.deb
l because of timeouts...
These are not time-dependent tests, so I guess my only option is to
increase a few timeouts to something that is not past the end of the
universe :)
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@li
uess you forgot to push?
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
sitory.
Seeing his replies, I am not sure it will be a pleasant upstream to work
with :(
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
flaky test.
> Once you make this to build reliably again, please consider uploading
> the package in source-only form, so that we get pretty official build
> logs here:
>
> https://buildd.debian.org/status/package.php?p=golang-fsnotify
I am ashamed to admit it, but I have no clue ho
ckages.
Thanks! i will prepare the proposed patch, and try this!
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
ad.
This is very weird.. I will look again and see if I can reproduce it
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
ink set lo up
tcpdump -ni any &
go test
If I do ping google, I see the packets. But I don't see anything with
the tests
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.
rom main, so I don't see any reason for this
bug to be RC (yet).
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
isolated network
container, and tcpdump reports 0 packets captured...
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
ackage directly with go get, I get no errors. So, I pressume this might
be related to some change in golint's only dependency, x/tools...
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://
1 - 100 of 264 matches
Mail list logo