gine this at some point being used for finding packages based
on their import path. But not sure if it is reason enough to keep the
header..
Maybe somebody else has a better argument for this?
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers ma
Hi,
On 25/10/16 06:57, Pirate Praveen wrote:
> On Wednesday 12 October 2016 08:19 PM, Martín Ferrari wrote:
>> I need to check with upstream if they are breaking API compatibility for
>> good, and in that case will need to create a new package with a API
>> version embed
ogle-cloud (wtf),
but it is not even used... Those source files only are built when
compiling for appengine. And this circular dep is probably why this
package has not yet entered testing. Fingers crossed, today it will
finally migrate.
--
Martín Ferrari (Tincho)
_
umented in systemd.exec(5):
Argh, stupid systemd is stupid.. not being compatible with shell syntax.
Anyway, will fix this. Thanks for reporting.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
h
e-cloud, but the latter
finally migrated 2 days ago. I don't know what's going on with x-tools...
--
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 31/10/16 11:14, Martín Ferrari wrote:
> I was asking the same question on #-release just now.. I thought this
> was because of the cyclic dependency with google-cloud, but the latter
> finally migrated 2 days ago. I don't know what's going on with x-tools...
Adam shone
Unless somebody thinks it is a bad idea, I will split x-tools into more
packages, at least to keep the web crap away from the important stuff.
I am undecided if I should also split the source package, to maximise
isolation. Thoughts?
--
Martín Ferrari (Tincho
On 31/10/16 14:20, Martín Ferrari wrote:
> Unless somebody thinks it is a bad idea, I will split x-tools into more
> packages, at least to keep the web crap away from the important stuff.
>
> I am undecided if I should also split the source package, to maximise
> isolation. Though
Package: dh-golang
Version: 1.19
Severity: normal
While trying to use DH_GOLANG_INSTALL_EXTRA to install test fixtures for
golang-procfs, I noticed that dh_golang did not copy symlinks, making tests
fail.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500
o arches [0], possibly due to some
tool still hardcoding the location for godoc. It would be great if
somebody can take a look, I have already spent way too much time on this
this week :)
[0] https://buildd.debian.org/status/package.php?p=golang-golang-x-tools
--
Martín Ferr
t;uneeded" is, in fact,
> needed for a little longer.
Indeed, I remembered seeing that change. That's what I was referring to
in my previous email.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainer
On 02/11/16 00:05, Martín Ferrari wrote:
> On 01/11/16 21:44, Michael Hudson-Doyle wrote:
>
>> Go 1.6 did that too, but the special behaviour here was removed for 1.7.
>> gccgo-6 still has a version of the go tool based on 1.6 though, so
>> (unfortunate
On 02/11/16 01:26, Martín Ferrari wrote:
> On 02/11/16 00:05, Martín Ferrari wrote:
>> On 01/11/16 21:44, Michael Hudson-Doyle wrote:
>>
>>> Go 1.6 did that too, but the special behaviour here was removed for 1.7.
>>> gccgo-6 still has a version of th
On 12/11/16 10:38, Santiago Vila wrote:
> imports google.golang.org/cloud/internal: use of internal package not
> allowed
This looks like an older version of golang has been used. Can you
include the full build log?
Thanks
--
Martín Ferrari (
investigate.
> (Maybe we need a versioned build-depends here?)
Evidently, it was not that..
--
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 12/11/16 16:34, Martín Ferrari wrote:
Looking more into this, it seems the problem is golang's stupid rules
about canonical naming, which I tried to circumvent for compatibility
and now it is backfiring.
I will try to find a different solution now.
--
Martín Ferrari (T
de 100644
> +index 493197c..000
> +--- a/process/process_linux_arm64.go
> /dev/null
> +@@ -1,8 +0,0 @@
> +-// +build linux
> +-// +build arm64
> +-
> +-package process
> +-
> +-const (
> +-ClockTicks = 100 // C.sysconf(C._SC_CLK_TCK)
> +-)
> +--
> +2.9.3
> +
> diff -Nru golang-github-shirou-gopsutil-2.1/debian/patches/series
> golang-github-shirou-gopsutil-2.1/debian/patches/series
> --- golang-github-shirou-gopsutil-2.1/debian/patches/series 2016-06-19
> 23:21:58.0 -0400
> +++ golang-github-shirou-gopsutil-2.1/debian/patches/series 2016-11-03
> 08:34:51.0 -0400
> @@ -1 +1,4 @@
> 01-Disable_failing_tests.patch
> +0001-process-determine-page-sizes-via-function.patch
> +0001-process-make-ClockTicks-arch-independent.patch
> +0001-Improve-CPU-identification-for-POWER-processors.patch
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>
--
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
body to take a look for
your first contributions, as our policies are not well documented, and
dh-make-golang many times is not up-to-date with current practices.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.
Daniel,
On 15/11/16 18:46, Daniel Stender wrote:
> the new package golang-golang-x-oauth2-google-dev missed Breaks against the
> previous
> package revision:
Oh, I completely forgot that, thanks for spotting! Will fix asap.
--
Martín Ferrar
On 15/11/16 19:11, Martín Ferrari wrote:
> Daniel,
>
>
> On 15/11/16 18:46, Daniel Stender wrote:
>
>> the new package golang-golang-x-oauth2-google-dev missed Breaks against the
>> previous
>> package revision:
>
> Oh, I completely forgot that, thanks f
and for a new
dependency to go through NEW. Both things just happened, so today or
tomorrow tops I will upload this fix.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/c
ring the patch to migrate
to the new datetimepicker. I have a fix already prepared that I am
uploading 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
ove the vendoring, both
libraries you mention are already packaged!
--
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
saved at
../golang-goprotobuf_0.0~git20161116.0.224aaba.orig.tar.gz
--
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
xperience this bug, I can't file a report.
--
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
package ready and installed
in the local cowbuilder repository, but forgot to upload 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
-common.
Forwarded 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
s the executables.
What do you think?
[0] https://wiki.debian.org/BuildProfileSpec
--
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/11/16 16:52, Martín Ferrari wrote:
> I was today working again on x/tools, trying to solve build issues with
> gccgo, and realised that now there is a circular dependency with x/text.
> Similar things are happening in other very important packages.
Actually, I notice that this cir
}
return _MyType_name[_MyType_index[i]:_MyType_index[i+1]]
}
--
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
would expect it to be dynamically linked.
All go applications are currently compiled statically.
--
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
.
--
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 30/11/16 19:59, Martín Ferrari wrote:
> I was trying to solve this bug, but then I realised this package
> actually only contains pre-generated files, without source. And the
> upstream project is gone.
>
> It should be replaced with https://github.com/google/go-genproto
>
ient-go/logging/v2/logging_config.pb.go:223:
> undefined: grpc.SupportPackageIsVersion3
> src/github.com/googleapis/proto-client-go/logging/v2/logging_metrics.pb.go:183:
> undefined: grpc.SupportPackageIsVersion3
--
Martín Ferrari (Tincho)
__
Pinging this bug so autorm will not remove the package while it migrates
to testing.
--
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
ostrm you can use one
> "{PKGNAME}.maintscript" file with "symlink_to_dir" line.
> See dpkg-maintscript-helper(1) for details.
Thanks for the tip, I did not know this!
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing
the extra work is too much. But in this case, we
only need to fix the package once.
In the future, we should also start versioning grpc and
protobuf-compiler, so we can detect this automatically.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainer
hanks.
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>
--
Martín Ferrari (Tincho)
_
ntainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>
--
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
Adrian,
On 15/01/17 20:08, Adrian Bunk wrote:
> On Sun, Jan 15, 2017 at 07:40:57PM -0300, Martín Ferrari wrote:
> Looking at the error message "getsockopt: connection refused",
> it is possible that there might be different network related
> configuration or permissions o
OK, I've finally managed to reproduce the problem, by running the build
with low prioirty in a very CPU-starved environment. It is again a
timing issue when starting the test server.
Will produce a patch and upload ASAP.
--
Martín Ferrari (T
es (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 a
memory: cannot allocate 4194304-byte block (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
y?
I will 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
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
hanks a lot!
[1]: https://buildd.debian.org/status/logs.php?pkg=prometheus&arch=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
em to 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
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 exper
tus 2
> FAIL github.com/prometheus/prometheus/storage/local 288.359s
> ...
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
ot updated 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
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
s
first to 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-g
it is for backports.
debian/docs: missing to install README.md
debian/watch: syntax errors (run uscan --report)
Lintian overrides do not seem necessary.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debia
Vincent, are you requesting an unblock exception for this package? There
are a bunch of other packages that are going to be removed from testing
if this does not migrate.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go
t;
> What is the recommended way to fix this ?
Actually, the upstream author indicates to use gopkg.in as the canonical
import path, so I think the easiest and most correct way forward is to
patch your package to use that. I have done similar things in th
. There is a report upstream of flakyness in this
test: https://github.com/golang/go/issues/18142
I will disable this test.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth
Hey all,
Like last year, I am organising this little event in Catalonia in May. I
wonder if any golangers are around Europe at that time and would be
interested in meeting for some group work..
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers
a v7 in the future without
changing the import path, then we will have to create a new source
package and leave the old one just for compatibility.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.or
e sdk and in particular ethereum has upgraded their required version
> to version 6.0.
Wow, they sure seem to like to make major releases! :)
We will have to see how to do this update without breaking stuff. I
can't imagine this will be API-compatible with 2.
e archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
>
> ___
> Pkg-go-maintainers maili
https://anonscm.debian.org/cgit/pkg-go/packages/prometheus-postgres-exporter.git/tree/debian/tests/build-test
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinf
names for each package are included in the attached lists.
On 23/05/17 11:26, Martín Ferrari wrote:
> Hey all!
>
> As I mentioned on IRC, I have been working on getting autopkgtest
> coverage for all of our packages.
>
> I started by writing an script[1] that re-runs the same t
Hi Antonio,
On 26/05/17 11:43, Antonio Terceiro wrote:
> On Fri, May 26, 2017 at 04:35:19AM +0100, Martín Ferrari wrote:
> [...]
>> I have also added golang support to autodep8 (which uses the script in
>> dh-golang) and pushed the changes to git master. (Antonio, please let
/rules (this is supported by the script in dh-golang).
On 26/05/17 04:35, Martín Ferrari wrote:
> An status update on autopkgtest for pkg-go.
>
> I have been working on this since SunCamp, and I think it is ready for
> deployment.
>
> I have created a much more polished script
On 01/06/17 13:30, Antonio Terceiro wrote:
> I have just installed the whitelist, and the packages in it started to
> be tested.
Excellent, thanks a lot!
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maint
y 3rd.
--
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
project explictly says there are
no api compatibility guarantees, ffs).
So, should I prepare a new source package, or should we try to upgrade
from the current one?
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers
Are
you still able to reproduce it in your environment?
--
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
t 195.00, want 150.00
It possibly a race condition, but I cannot 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
On 14/07/17 11:21, Santiago Vila wrote:
> It could also be a race condition which happens more
> likely on low memory systems. Feel free to recategorize.
Honestly, without a way to reproduce it, I am more inclined to close :)
--
Martín Ferrari (
he report. I am aware of this problem, I had to update the
prometheus-common library, but haven't got the chance yet to upgrade
prometheus, due to new dependencies. I hope to be able to fix this in
the following few days.
--
Martín Ferrari (Tincho)
s, we would need a new binary package for the
new API
--
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
wt-go-v3-dev
Worth the trouble or not: depends on who gets to fix all the breakage
left behind :)
> Personally, I would just update the new version + the fixed affected
> packages in one go, to reduce the breakage to a minimum.
I would be OK with that.
--
Mart
provide a seamless
install for sysv users like me, would a conditional depends like 'daemon
| systemd-sysv' work?
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alio
uot;--format=%h %cd");
chomp($commit_data);
$commit_data =~ /^([0-9a-z]{7}) ([0-9]{8})$/m
or die("Invalid git response: $commit_data");
return ($1, $2);
--
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
demoting it to Recommends
> should work for most people, but otherwise yes, your suggestion should
> work fine.
This package is aimed at sysadmins, who would routinely disable
recommends installation. I would go the conditional depends route then.
Th
pkg. Does it just
> run again the `go test` like CI for src pkg?
CI.debian.net uses autopkgtest, which in turn uses these installed
_test.go files to run the tests.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintai
On 04/08/17 04:48, Shengjing Zhu wrote:
> BTW, I always drop test dependencies for the -dev package.
This is not a problem, as the tests are not needed for *using* the
package. Autopkgtest uses the build-dependencies for that.
--
Martín Ferrari (Tin
right, sorry about the confusion.
--
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
asap if this works for you or what would
be your availability.
For this to happen, it needs to be registered before 19:00 on Monday, so
don't delay! :)
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-mainta
them, I created a dudle at
https://dudle.inf.tu-dresden.de/go-pkg_bof/ to decide the final time.
Please fill it before today at 18h (22h GMT), so I can schedule it in
the system.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
On 07/08/17 13:15, Alexandre Viau wrote:
> On 07/08/17 11:42 AM, Martín Ferrari wrote:
>> Please fill it before today at 18h (22h GMT), so I can schedule it in
>> the system.
So, everybody has already answered, and tomorrow at 11 seems to be the
perfect time. Friday at 11 is als
here:
https://wiki.debian.org/Teams/DebianGoTeam/DebConf17BoF
PS: Title shamelessly stolen from the Perl team.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi
EXTRA variable that is a
space-separated list of regexes to match against pathnames.
--
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
Pkg-go BoF meeting minutes
==
On Tuesday, we had the first in-person meeting of the team. We met for 2
hours to discuss our current issues and to plan for the future.
People present
--
Alexandre Viau (aviau)
Martín Ferrari (Tincho)
Paul Tagliamonte (paultag
reassign 870843 golang-github-sirupsen-logrus-dev
thanks
This bug is filed under the wrong package.
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Package: golang-golang-x-tools-dev
Version: 0.0~git20170629.0.1b3bb8de-1
Severity: grave
Since 0.0~git20170629.0.1b3bb8de-1 a patch has made the source files shipped
fail to build in mips* architectures. It does not FTBFS just because tests have
been disabled in a previous version, but it is makin
FS.
>
I am being stupid and mixing x/tools with x/sys. Sorry about the noise.
--
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
verify the above constraints still
> leave us in a place where dgit works well — it will work for any
> package, but it will work better for packages which are `dgit push`ed. I
> don’t yet know what the requirements for that are.
Same here, I haven't checked it out yet
--
Martín
during the first build.
> Makes sense. Which gccgo arches are really being used today though? MIPS
> I guess, but that really should get golang-go once we figure out how to
> do that.
Not sure about being used, but we compile for mips* and arm*.
> https://nm.debian.org/proce
So, my turn to describe workflows.
I use gbp, pristine-tar, cowbuilder (but planning to move to sbuild),
dch, debcommit as my main tools. I have not really used dh-make-golang much.
My global gbp configuration is as follows:
[DEFAULT]
pristine-tar = True
sign-tags = True
[buildpackage]
export =
e that shouldn’t expire:
> https://paste.debian.net/982242/
Thanks, I like those sbuild options, I am saving 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
> Given that you _also_ maintain history in git, using gbp dch seems
> like significantly cutting down the number of commands. Is there any
> rationale behind your decision to not use gbp dch, or are you just
> used to this way? :)
Mostly historical reasons and muscle memory :)
--
Ma
On 20/08/17 17:35, Martín Ferrari wrote:
> So, my turn to describe workflows.
Some things I forgot in my previous email:
* I am not married to the idea of dch + debcommit, specially when I have
merge conflicts. I understand the merits of git commit + gbp dch.
* The export=WC option in gbp.c
.GoVersion=$(GO_VERSION)"
>
> What does METAPKG resolve to? We should consider centralizing these
> definitions somewhere.
Ah, this is prometheus-specific. All the meta info is stored in the
prometheus/common namespace, so I defined that earlier in the rules file.
--
Martín Ferrari (Ti
. The packages
should build out of the box. Can't you add the correct build
restrictions for gccgo so we don't need the tags?
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://li
Package: lintian
Version: 2.5.52
Severity: normal
Hi,
Currently, lintian complains about the pkg-go testsuite, but autodep8 has
support for it since 0.9.
source: unknown-testsuite autopkgtest-pkg-go
Can you add pkg-go to the list of valid testsuites?
Moreover, autodep8 already supports a few o
emaining value ("autopkgtest-pkg-elpa") in:
>
>
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=d5f0c0115ef46eb98d1b68f7113aa63d93f72211
>
> … and renaming this bug to match :)
Cool, we just need to wait for th
Source: golang-google-cloud
Version: 0.5.0-2
Severity: serious
Justification: fails to build from source
Since the latest update to golang-google-genproto-dev, this package FTBFS.
The fix for this is in release 0.7.0, but that requires also updating
golang-github-googleapis-gax-go-dev, and I am n
201 - 300 of 317 matches
Mail list logo
