following upstream git
history.
So, unless anybody sees this as a problem, I will take it over with a
package using the v3 name, a repo with that name, etc.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth
, as it
is not released (see https://gopkg.in/alecthomas/kingpin.v3-unstable).
I am going to provide the compatiblity symlink, but I think it does not
make sense to have a package with a name that needs to change as soon as
it is released.
--
Martín Ferrari (Tincho)
___
ration for a new upload
of the alertmanager, so this FTBFS will be solved as soon as I am finished.
Sadly, the golang ecosystem is very immature and has not yet learned
about API stability or even releases...
--
Martín Ferrari (Tincho)
___
Pkg-go-mai
k to see if another buildd succeeds?
Does the mips porters have any idea on why this could be?
Thanks.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mai
Hi James,
On 22/04/18 20:38, James Cowgill wrote:
> I sent a patch for this some time ago:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892088
Oh, I missed that. It seems it got accepted upstream, so I will try to
backport it to 1.10.1.
Thanks!
--
Martín Ferrari (
Hey all,
Is anybody planning to attend the miniconf in Hamburg? Could be good to
organise some work/bof if we are a few there..
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth
n improving our QA processes!
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
ints/elbrus
>
> I think the package will migrate tonight.
Thanks for your help!!
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
Hey all,
Alioth is coming down, and we are listed as still having stuff lying around.
I checked, and it seems to be mostly backups of migrated stuff, but
there are also some things that I am not sure if we have migrated them
completely:
$ ls -1 /git/pkg-go
attic
meta.git
meta.git.O
meta.git.O2
p
ed that this needs to be blocked, please go ahead
with the RC bug.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
ed once the final release is out.. But it
still seems like a bug to panic due to that. I don't know how upstream
presents the RC version number, but shouldn't that also break semver
parsing?
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mail
On 12/06/18 17:00, Daniel Swarbrick wrote:
> On 12.06.2018 17:50, Martín Ferrari wrote:
>> I had not heard about unsee until now, we should package it too! :)
> That would totally rock!
I was just taking a look, the main thing would be to be able to build
all the JS stuff, but it d
nk the problem is the latest upload of
golang-github-prometheus-client-golang-dev, which had some incompatible
changes. It also affected docker go-metrics (#900597).
Sadly, the only solution is to update to the new API, but probably
upstream has already done it in their repo.
--
M
ivalent of a soname change..
> https://salsa.debian.org/ruby-team/meta has build script which makes it
> very easy to rebuild all reverse build dependencies.
We have ratt, but that requires sbuild, so I ended up never using it.
--
Martín Ferrari (Tincho)
time to fix the tooling, but I think we should at least
consider these migrations steps in the right direction.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
s, I introduced the circular dep without noticing
during the last upload of -common.
Sadly, I don't see upstream changing this, but I will see if I can break
the circle somehow.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-g
On 18/06/18 22:44, Alexandre Viau wrote:
> On 2018-06-18 04:54 PM, Martín Ferrari wrote:
>> Sadly, I don't see upstream changing this, but I will see if I can break
>> the circle somehow.
>
> Sometimes, the circle is due to a test dependency and you can compromise
>
still needed...
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
08.ce61ec4-1 tag
>
> which indicates to me that you are not running the gbp commands in the
> right order, or some other issues.
Note that in general, it is understood that the presence of a debian/*
tag indicates the package has already been uploaded.
--
M
No, the tooling does not yet support the new repo layout, you just add
upstream's repo as a remote and pull from there into the upstream branch.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-l
workflow, where RFSs are not
needed at all, because you see what packages are ready for upload and
you can just sponsor whenever you have some free time.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.d
could also change the default in the next debhelper compat mode;
dunno how this is normally handled, but it would be good to coordinate
so this change is documented.. In that case it might be even be sensible
to add the switch in the code now.
--
Martín Ferr
On 18/08/18 12:55, Helge Kreutzmann wrote:
> Hello,
> unfortunately a typo was detected after I sent this e-mail. Could you
> merge the attached version instead of the original one?
Done, thanks!
--
Martín Ferrari (Tincho)
___
Pkg-go-ma
ests, becasue the
installed package starts the daemon and then the tests fail when trying
to use the same port; but this is not a FTBFS: the build daemons do not
fail to build from source. I think you should lower the severity.
--
Martín Ferrari (Tincho)
___
P
oes not fail: I have
just checked again; so this bug is not RC. There are a few other go
packages that fail autopkgtests for the exact same reason, please do not
open FTBFS bugs without actually trying to build the package.
--
Martín Ferrari (Tincho)
___
tually be a flaky test?
I have not seen this error before, I can only imagine you had some old
process lying around, or somehow the port was still in use? Otherwise,
it must be some concurrency issue, but as I said, I have not been able
to reproduce this.
n on tHE CPU, and none failed..
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
pkgtest flag to request a clean
> netns be used?
This discussion is about a FTBFS bug, not about the CI system. ALso,
that would not solve the issue, as it is autopkgtest installing (and
therefore starting) prometheus.
--
Martín Ferrari (Tincho)
___
P
It took me a while to reproduce, as it seems to only happen with high
CPU contention. I will see if I can fix the bug, or disable it otherwise.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
mount points occasionally and it would be better for them not to be
> monitored.
Yeah, I think that makes sense. I will add them.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alio
n, where the
alertmanager was shipping a web UI, but I since removed it. So the
symlinks are obsolete. Will corrent in the next upload.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
ht
uld
be glad to add them if you write them :)
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
o contributing it upstream, it would
fit with the examples.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17848
>
Thanks for the heads up!
Sadly, it seems it has not yet been fixed upstream.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alio
5 months ago.. Did I forget to actually
upload this version?
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
hen I built it
> locally, so I uploaded it.
>
> https://buildd.debian.org/status/logs.php?pkg=prometheus-node-exporter&ver=0.16.0%2Bds-1~bpo9%2B1&suite=stretch-backports
Ah, I had missed that. thanks for fixing!
--
Martín Ferrari (Tincho)
__
Fabian,
On 11/12/2018 10:32, elnappo wrote:
> I already submitted a pull request to fix this
> at
> https://salsa.debian.org/go-team/packages/prometheus-apache-exporter/merge_requests/1
Thanks for the heads-up, I had missed this!
It is now merged, and I will upload soon
--
Martí
and uploaded.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
Santiago,
On 06/01/2019 00:14, Santiago Vila wrote:
> I tried to build this package in buster but it failed:
I have investigated the issue. It seems to be due either to changes in
golang or in the x/tools package, I will do some more tests, and hope to
fix it soon.
--
Martín Ferrari (Tin
ird.. But I'd bet the error refers to another line in that
file. After all, node-exporter has no idea of sat, scsi, or megaraid. I
think that must be some text in the file. Could you send the contents of it?
Thanks.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
to_end_error_threshold
# TYPE smartmon_end_to_end_error_threshold gauge
smartmon_end_to_end_error_threshold{disk="/dev/sdb",smart_id="184",type="sat"}
0
$ journalctl -u prometheus-node-exporter.service |tail -n1
Jan 30 16:47:31 aine promet
ot be done if TMPDIR
is not
in the same filesystem.)
So I will look into using the same dir as TMPDIR.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
Daniel, et al.
I was preparing a fix for this by copying some support scripts from
other exporters when I noticed a couple of things, and wanted to check
with you before making any change.
This exporter is running with user postfix, while all the others use the
prometheus user. I understand that
-)
So I checked with upstream, they decided to remove it because for them
it is already obsolete.. I will try to backport this, but it could be
tricky as the codebase has evolved since this was removed.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintai
promtool from the .deb.
That would have to go through NEW, we are out of time for that :(
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
he UI, and
that would have required preparing and uploading dozens of new packages,
and I did not have the resources for that.
Somebody offered to write a script to download the pre-compiled UI and
install it locally, but never happened.
--
Martín Ferrari (Tincho)
___
46 matches
Mail list logo
