fixed 890501 2.2.0+ds-1
thanks
Due to some mistake in my workflow, a couple of changelog entries went
missing in 2.2.0+ds-1, and so this bug was never closed. I added the
entries retrospectively, and closing manually the bug now..
--
Martín Ferrari (Tincho
.url$/\1/'); git --git-dir=$i/.git remote set-url
$remote $newval; done; done
--
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
permit.
Same from me, on the three items :)
--
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 03/04/18 05:16, Alexandre Viau wrote:
> The migration was completed.
Thank you for all your work!!
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-
org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
prometheus - Monitoring system and time series database
Changes:
prometheus (2.2.1+ds-2) unstable; urgency=high
.
* debian/control: Require latest TSDB version, that solves serious bugs
in the DB.
Ch
Packaging Team
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
golang-github-prometheus-tsdb-dev - Prometheus storage layer library
Changes:
golang-github-prometheus-tsdb (0.0~git20180314.659ed64-1) unstable;
urgency=high
.
*
he, which
is simpler and has support for many languages, and was in Debian already :)
--
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
in debian). The problem is the
generated code, which is not source code (preferred form of modification).
--
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
Packaging Team
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
prometheus-mysqld-exporter - Prometheus exporter for MySQL server.
Closes: 893051
Changes:
prometheus-mysqld-exporter (0.10.0+git20180201.a71f4bb+ds-2) unstable;
Packaging Team
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
golang-golang-x-sys-dev - Low-level interaction with the operating system
Closes: 891894
Changes:
golang-golang-x-sys (0.0~git20180308.349b81f-1~bpo9+1) stret
: stretch-backports
Urgency: medium
Maintainer: Debian Go Packaging Team
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
golang-github-grpc-ecosystem-grpc-gateway-dev - gRPC to JSON proxy generator
for Golang -- sources
golang-grpc-ga
pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
prometheus-blackbox-exporter - Blackbox prober for Prometheus
Closes: 894130
Changes:
prometheus-blackbox-exporter (0.12.0+ds-1) unstable; urgency=medium
.
* New upstream release. Clo
-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
golang-dns-dev - transitional package for golang-github-miekg-dns-dev
golang-github-miekg-dns-dev - DNS protocol library for Go
Changes:
golang-github-miekg-dns (1.0.4+ds-1) unstable; ur
On 26/03/18 17:24, Daniel Swarbrick wrote:
> Please backport Prometheus 2.2.1 to stretch.
It is in my plans, but it has to reach testing first :-)
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintain
use of this that I thought of stripping the UI away, and
replacing it with something bare-bones. This would not be that difficult
to do, it is just a matter of writing some html and JS.
If you could help me with that, I would take care of integrating the
replacement UI, and I could get a new releas
s UI without the dynamic JS generated with Elm.
I am maintaining most of the prometheus ecosystem by myself, so I have
not been able to do any of this. If you have the resources to help, you
would be most welcomed!
--
Martín Ferrari (Tincho)
__
org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
prometheus - Monitoring system and time series database
Changes:
prometheus (2.2.1+ds-1) unstable; urgency=high
.
* New upstream release, with critical fixes.
* Ignore fsnotify on mips64el, rely only on timeouts for fi
least to fix the incompatibilities with 1.0.2. I think it is at least
worth a try.
The other way, which we have done many times, is to patch the software
ourselves. I have no idea why docker does not build with that version,
but sometimes it is not that difficult to fix.
my 2¢
--
Martín Fer
Packaging Team
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
prometheus-mysqld-exporter - Prometheus exporter for MySQL server.
Closes: 848481 884542
Changes:
prometheus-mysqld-exporter (0.10.0+git20180201.a71f4bb+ds-1) unstable;
Team
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
golang-github-data-dog-go-sqlmock-dev - Sql mock driver for golang to test
database interactions
Changes:
golang-github-data-dog-go-sqlmock (1.3.0-1) unstable; urgency=medium
org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
prometheus - Monitoring system and time series database
Closes: 888153
Changes:
prometheus (2.2.0+ds-1) unstable; urgency=medium
.
* New upstream release. Closes: #888153.
* Add notice about DB changes.
* Update
Packaging Team
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
golang-github-prometheus-tsdb-dev - Prometheus storage layer library
Changes:
golang-github-prometheus-tsdb (0.0~git20180302.16b2bf1-1) unstable;
urgency=medium
12
>
> Does that answer your question?
Ah, that's perfect. 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
s, etc.
--
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
nges, we should
probably avoid doing twice :)
> As far as I’m concerned, we can leave it as-is for the time being. The
> mailing list will be migrated, and there will be a separate turn-down
> cycle for that in a few years.
OK, if that is possible, I have no objections.
--
My main questions would be:
* Where does all this run?
* How does it communicate with gitlab?
* What kind of control do we have over it?
Sorry for the very basic questions..
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing
: medium
Maintainer: Debian Go Packaging Team
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
golang-github-prometheus-alertmanager-dev - Handle and deliver alerts created
by Prometheus -- source
prometheus-alertmana
gt; The go compiler stuff should be a subgroup of the go-team group,
> although I don't think anything about that should block the package
> migration.
True.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lis
ll make sense to join everytihng
under one group)
* What about mailing list and maintainer address? I know the perl people
solved this somehow, but I don't understand how :)
These two are important, because we should define them before changing
all repos and mass-committing hundreds of changes
gt; as a tag:
This all looks great, thanks a lot!
Now, I am still a bit confused as to how this all works :-) Could you
share a basic intro?
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.deb
Packaging Team
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
golang-google-cloud-compute-metadata-dev - Google Cloud Platform APIs (only
cloud/compute/metadata)
golang-google-cloud-dev - Google Cloud Platform APIs
Closes: 89
reproduce..
I have a fix and it seems I can't reproduce the problem any more.
--
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
Distribution: unstable
Urgency: high
Maintainer: pkg-go <pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
golang-go.tools - Transitional package for golang-golang-x-tools
golang-go.tools-dev - Transitional package for golang-golang
Packaging Team
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
golang-google-cloud-compute-metadata-dev - Google Cloud Platform APIs (only
cloud/compute/metadata)
golang-google-cloud-dev - Google Cloud Platform APIs
Closes: 89
On 20/02/18 19:17, Adrian Bunk wrote:
> Source: golang-golang-x-tools
> Version: 1:0.0~git20170707.0.bce9606b+ds-1
> Severity: serious
Thanks for the report. It seems this is one of the packages that broke
with the swtich to golang 1.10. I will take a look into it.
--
Martín Ferrar
rue
chown -R prometheus:prometheus /var/log/prometheus || true
And the initsciprt does this (as root):
mkdir -p `dirname $PIDFILE` || true
chown -R $USER: `dirname $LOGFILE`
chown -R $USER: `dirname $PIDFILE`
So, I don't know where you saw that mkdir, nor where it could be a problem.
--
Martín Fer
Ah, sorry, now I see that you are reporting against the version in
stable. There is not much I can do to fix that, the version in testing
does not have this issue.
What I can do (and I had forgotten to do before), is to backport that
version to stretch.
On 23/02/18 14:48, Martín Ferrari wrote
On 23/02/18 11:10, Michael Stapelberg wrote:
> Which file specifically is affected? The Files-Excluded directive in
> debian/copyright is a good way to exclude files.
Not anymore.. If you are not using import-orig and the like, that is
effectively ignored.
--
Martín Ferrari (
stand your concern. I suggest we try my suggested approach and
> re-evaluate at some point down the road (a quarter? a year?) whether
> keeping it up is feasible and worthwhile. We can always course-correct,
> there’s no lock-in here.
Sounds good to me.
--
Martín Ferrari (Tincho)
__
need to be careful not to break the system,
and that it will not be obvious when building locally.
--
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
lot of work to avoid having
any customisation in debian/rules.
--
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
I had no idea there was now a tsdb lockfile,
and I agree that it makes sense to disable it, since we have that
functionality implemented in the init/service files.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-mainta
keep them in the package, so tests can be run from the
installed package, including in ci.debian.net.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin
org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
chasquid - simple SMTP (email) server written in go
Changes:
chasquid (0.04-1) unstable; urgency=medium
.
[ Alberto Bertogli ]
* New upstream release.
* Ignore dovecot-auth-cli (internal binary not useful for productio
a package in the pkg-go git tree,
the assumption is that it must follow the team policy and that it is
team maintained. You can not assume nobody else has touched it,
otherwise, there is not much point in having it under the pkg-go umbrella.
--
Martín Ferrar
wise to try to have a
similar scheme to other teams. Dunno if there is any consensus yet, but
for example the perl team has gone for perl-team.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.deb
e looks good. I only made a couple of minor corrections, and
uploaded 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
Packaging Team
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
golang-github-dgrijalva-jwt-go-dev - Golang implementation of JSON Web Tokens
(JWT)
Closes: 889875
Changes:
golang-github-dgrijalva-jwt-go (3.0.0.1+REALLY.2.6.0
er that merges are automatic.
> However, I can’t find a git-buildpackage command to take care of this.
> How do you do it? Manually?
Yup :)
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http
emote branch? AFAICT, git-buildpackage has no
> solution for this (yet?). Does anyone know by chance?
For us, 99% of the time, the homepage field in d/control is what we
need. But it would be nicer to have something proper.
--
Martín Ferrari (Tincho)
___
ge [1], which plainly
> > states that this is about excluding _targets_.
> By “this”, you refer to DH_GOLANG_EXCLUDES, I assume.
The main issue that we discussed with Clément is that DH_GOLANG_EXCLUDES
excludes packages from compilation, but not from installation. And I
feel that is not t
n discussed is the repo layout: now it
seems we are using a flat layout, whereas before we had a packages tree,
separate from other things like meta, website, and even a users/
subtree. What are we going to do with those?
--
Martín Ferrari (Tincho)
___
P
Status update: still waiting for upstream's fix.
On 18/12/17 04:55, Martín Ferrari wrote:
> Adrian,
>
> Thanks for the report. I presume this error is due to the change in the
> Prometheus' common library. I am already preparing a new upstream
> release, but that is waiting on
hy in order to ship prometheus
in Debian. If you look at the changelog of raft, you will see that the
last two uploads were done by me.
--
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
It seems that updating to v0.16.0 fixes this issue but that pulls new
dependencies, so I am just going to backport the fix for this.
On 04/01/18 11:49, Martín Ferrari wrote:
> On 14/12/17 22:48, Adrian Bunk wrote:
>
>> # cloud.google.com/go/spanner/internal/testutil
>> src/c
pannerServer:
> *MockCloudSpanner does not implement spanner.SpannerServer (missing
> ListSessions method)
> ...
It seems the latest upload to golang-google-genproto broke the API. Will
have to investigate...
--
Martín Ferrari (Tincho)
___
Pkg-go-mai
w salsa URLs in the Vcs links, but now it seems we
get to maintain the anonscm links.
Honestly, it feels very demotivating that you did this change :(
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.deb
t data, and it already breaks all tooling.
--
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
ages,
since we have decided to use upstream git history, and repack on git, so
there is no real usage for it --except documentation.
--
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 Alexandre,
I see you have been pretty busy uploading stuff :-) But can you please
push to git all these changes? We risk getting out of sync.
Forwarded Message
Subject: [pkg-go]
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1_source.changes
ACCEPTED into unstable
pendency. I usually keep it around
for reference, as it is very useful when things break. I really don't
see much the point of removing it, or making a very complicated
files-excluded field. Also, how can it be a DFSG violation?
--
Martín Ferrari (Tincho)
___
Pkg-
st that can happen is a rejected upload because of checksum mismatches.
--
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 08/11/17 21:01, Martín Ferrari wrote:
> The best test would be to use gbp to create the tarballs under different
> conditions (machine, user name, path, manually touch()ing files locally)
> and see if they are really reproducible.
For one data point, I just tried this on two different
under different
conditions (machine, user name, path, manually touch()ing files locally)
and see if they are really reproducible.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.or
in the next few days. Any help
> is welcome.
I will try to squeeze some contributions.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/
On 06/11/17 15:04, Martín Ferrari wrote:
> I have added something that I think it is widely accepted, but was not
> explicitly discussed, and that I would like to be set on policy: should
> we mandate merging of upstream code in debian branch?
Just to clarify: I don't think this new poi
andate merging of upstream code in debian branch?
--
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
appened is that because of the source-only upload, it was
considered obsolete and removed? I had no idea about this problem, I
will stop doing source-only uploads then..
Thanks for the info, and the upload!
--
Martín Ferrari (Tincho)
___
Pkg-go-m
Andreas?
On 29/10/17 16:03, Martín Ferrari wrote:
> According to the changelog in the NEW page, it seems this package was
> removed by mistake. Andreas, can you share some details? I did not see
> the RM mail, nor I can find the new upload in the git repo.
>
>
>
upstream git history
or not.
In any case, it is important that other people check it out and comment.
So far, I only see edits my Michael and me. Having a clear policy is
very important to make the team more productive and easy to work with!
--
Martín Fer
t I've
heard it is actually a kernel problem).
I think it does not make much sense to open more RC bugs against these
packages that cannot really be fixed until the root cause is addressed.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
just disable the test completely.
It is not testing the hardware, it is testing that the write completes,
and developers many times assume everybody has fast hardware, and then
you get these bugs. We could argue about disabling this test (which is
noted as hacky by upstream), but those are not the
On 14/07/17 12:59, Martín Ferrari wrote:
> 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 clos
On 24/08/17 19:11, Shengjing Zhu wrote:
> Control: severity -1 normal
>
> On Thu, Aug 24, 2017 at 10:37 PM, Martín Ferrari <tin...@debian.org> wrote:
>> Yes, sorry, I was confused with x/tools, which has disabled tests. This
>> one does not get built in other ar
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
ing 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 the nex
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
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://lists.alioth.debian.org/cgi
rsion=$(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 (Tincho)
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
at 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 :)
--
Martín Ferrari (T
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
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
ld.
> 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/process/198 :)
yay!!
--
ve 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 Ferrari (Tincho)
__
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
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
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
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
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
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
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
or 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
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-maintainers
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
ust
> 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-maintainers@lists.alio
t 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.
Thanks again
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
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.alioth.debian.org/cgi-bi
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
1 - 100 of 264 matches
Mail list logo
