FYI: https://github.com/golang/go/issues/29410#issuecomment-515203754 — I
hope this is helpful for packaging Go modules in Debian. I have no plans to
work on that, though.
--
Best regards,
Michael
, 2019 at 1:18 PM Martín Ferrari wrote:
> On 10/03/2019 17:22, Michael Stapelberg wrote:
> > Please see
> > https://michael.stapelberg.ch/posts/2019-03-10-debian-winding-down/
>
> I am very sorry to read this Michael, but I understand the frustration.
> I have managed to work
Please see
https://michael.stapelberg.ch/posts/2019-03-10-debian-winding-down/
--
Best regards,
Michael
Build the package using gbp buildpackage, then upload the resulting
*_sources.changes file using dput.
On Thu, Feb 28, 2019 at 2:51 PM Tong Sun wrote:
> Hi,
>
> On Wed, Feb 27, 2019 at 8:43 PM Arnaud Rebillout wrote:
>
> > Dear go team,
> >
> > I'd need someone to upload docker-credential-help
partly be synthesized, and
most likely, synthesizing them in your package is the route of least
resistance for now. See https://github.com/golang/go/issues/29410 for
details.
On Tue, Feb 26, 2019 at 3:09 PM Julian Gilbey
wrote:
> On Tue, Feb 26, 2019 at 11:20:00AM +0100, Michael Stapelberg wr
My guess is that you need to set GOCACHE to a temporary directory. This
should be done within dh-golang itself, so please send a patch.
I think you’re treading on unchartered territory here — I’m not aware of
any package within Debian using Go modules yet.
On Tue, Feb 26, 2019 at 11:08 AM Julian
PM Reinhard Tartler
wrote:
>
>
> On Sun, Feb 24, 2019 at 4:13 PM Michael Stapelberg
> wrote:
>
>> Thanks for explaining what’s going on here. I think this actually makes
>> for a compelling case to add explicit build tag handling. I’m still of the
>> opinion that
Thanks for explaining what’s going on here. I think this actually makes for
a compelling case to add explicit build tag handling. I’m still of the
opinion that upstream should ship software in such a state that build tags
shouldn’t be necessary, but the existing way to specify build tags clearly
do
, nor good enough APIs to do so without a large amount of traffic
:-/
You can run it manually if you want to ensure your repo is in a good state.
On Tue, Feb 19, 2019 at 12:03 AM Martín Ferrari wrote:
> On 17/02/2019 16:50, Michael Stapelberg wrote:
> > It should be configured corre
It should be configured correctly when creating repositories.
On Sun, Feb 17, 2019 at 5:43 PM Rock Storm wrote:
> On Sat, Feb 16, 2019 at 09:48:16PM +0800, Shengjing Zhu wrote:
> > On Sat, Feb 16, 2019 at 8:21 PM Rock Storm wrote:
> > > Thanks for accepting me. What would be the process for upl
add overrides.
>
> Michael, have you considered this idea before?
>
> Best,
> -rt
>
> On Fri, Feb 15, 2019 at 7:15 AM Michael Stapelberg
> wrote:
>
>> You can find a few examples using
>> https://codesearch.debian.net/search?q=path%3Adebian%2Frules+tag+path%3
You can find a few examples using
https://codesearch.debian.net/search?q=path%3Adebian%2Frules+tag+path%3Agolang,
e.g.
https://sources.debian.org/src/golang-golang-x-sys/0.0~git20181228.9a3f9b0-1/debian/rules/?hl=40#L40
In general, I would encourage you to nudge upstream to make the default
behavi
The build log should state it. Only one compiler will be installed.
On Wed, Feb 6, 2019 at 12:29 PM Pete Heist wrote:
>
> On Feb 6, 2019, at 11:07 AM, Michael Hudson-Doyle <
> michael.hud...@canonical.com> wrote:
>
> On Wed, 6 Feb 2019 at 21:23, Pete Heist wrote:
>
>> 3) I’d like to build with
On Wed, Feb 6, 2019 at 9:23 AM Pete Heist wrote:
>
> On Feb 6, 2019, at 8:27 AM, Michael Stapelberg
> wrote:
>
>
>> 2) Is there a quick tutorial on pulling in new releases from upstream?
>> One complication is, my upstream (on GitHub) had it’s history re-written to
On Tue, Feb 5, 2019 at 2:36 PM Pete Heist wrote:
> Hi,
>
> I’d like to get the irtt package refreshed and squash a bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892429, but I’m behind
> on pkg-go, coming from alioth, and have a few basic questions to get up to
> speed:
>
> 1) I created
tml also get changed, so
> that the next person reading it will not get confused, as s/he might
> not able to find this discussion.
> On Fri, Dec 21, 2018 at 10:47 AM Michael Stapelberg
> wrote:
> >
> > Not entirely sure I follow, but:
> >
> > 1. The value of debian
I’m generally in favor of only adding knobs once a substantial number of
packages benefit from them.
On Tue, Jan 8, 2019 at 4:47 AM Stephen Gelman wrote:
> Hi,
>
> Currently, with dh-golang, the only configuration option for running “go
> generate” is DH_GOLANG_GO_GENERATE which is all or nothin
On Sat, Jan 5, 2019 at 10:20 PM Reinhard Tartler wrote:
> Thanks for the quick response.
>
> On Fri, Jan 4, 2019 at 6:15 PM Michael Stapelberg
> wrote:
>
>>
>>
>> On Fri, Jan 4, 2019 at 11:37 PM Reinhard Tartler
>> wrote:
>>
>>> Hi,
>&
On Fri, Jan 4, 2019 at 11:37 PM Reinhard Tartler wrote:
> Hi,
>
> A friend ask me to look into packaging a tool he is working on, and
> looking at golang packages was on my todo list for quite a while. Hence, I
> gave it a shot:
>
> siretart-@kaby:~/packages/buildah
> >> dh-make-golang estimate g
8 1:53 pm, Michael Stapelberg wrote:
>
> Hey,
>
> thanks for working on the reopen packaging.
>
> Lintian is a tool which detects when your package is violating Debian
> policy (see also https://en.wikipedia.org/wiki/Lintian).
>
> In this case, you are including a binary
Hey,
thanks for working on the reopen packaging.
Lintian is a tool which detects when your package is violating Debian
policy (see also https://en.wikipedia.org/wiki/Lintian).
In this case, you are including a binary program in your package, but not a
corresponding man page. The fix is to author
/control/
for a package which ships both binaries and a -dev package.
Hope that helps,
On Sun, Dec 23, 2018 at 4:28 PM Utkarsh Gupta
wrote:
>
> On Sun, Dec 23, 2018 at 8:53 PM Michael Stapelberg
> wrote:
>
>> I cannot find the word “binary-error” in the output you linke
I cannot find the word “binary-error” in the output you linked. Which of
the numerous errors specifically are you referring to?
On Sun, Dec 23, 2018 at 4:21 PM Utkarsh Gupta
wrote:
> Hey.
>
> I was trying to build a package and was running "lintian" on it. And got
> the following error: https://
/golang-go-dbus/1~bzr20150122-3/debian/rules/?hl=14#L14.
This is rarely necessary.
Does that help?
On Fri, Dec 21, 2018 at 4:24 PM Tong Sun wrote:
> On Wed, Dec 19, 2018 at 1:52 PM Michael Stapelberg wrote:
>
> >> > On Sun, Dec 16, 2018 at 5:24 AM Tong Sun wrote:
> >>
> I'll pass this time (but will take up other tasks that I am capable of
> in the future).
>
> Thx again.
> On Tue, Dec 18, 2018 at 12:09 PM Michael Stapelberg
> wrote:
> >
> > The DH_GOPKG variable defaults to the value of the XS-Go-Import-Path
> debian/control
The DH_GOPKG variable defaults to the value of the XS-Go-Import-Path
debian/control field.
If you don’t reference DH_GOPKG in any of the rules, you can therefore omit
it.
The example you found should be updated to no longer include DH_GOPKG, but
to include XS-Go-Import-Path. Could you send a pull
I have changed both repositories to have master as the default branch.
Could you file a bug against gbp for making the push order deterministic
please?
On Sun, Dec 16, 2018 at 5:12 AM Tong Sun wrote:
> On Sat, Dec 15, 2018 at 10:42 PM Tong Sun wrote:
>
> > - the default branch is *pristine-tar*
You can use dh-make-golang’s¹ search subcommand to find the Debian
package(s) containing a Go import path:
% dh-make-golang search github.com/gorilla/sessions
golang-github-gorilla-sessions-dev: github.com/gorilla/sessions
You can check Debian’s list of ITP (Intent To Package) bugs to see if
some
For the record, see https://github.com/Debian/dh-make-golang/issues/107 for
discussion. tl;dr: https://bugs.debian.org/908204
On Sat, Dec 1, 2018 at 6:24 PM Tong Sun wrote:
> Hi,
>
> I'm trying to make my initial gbp push to salsa-project but I'm
> wondering if it should be the suggested way:
>
There’s also sbuild, which is what the Debian builders are using (so you
can be sure that your package actually works), and which should be
reasonably easy to set up thanks to
https://people.debian.org/~stapelberg//2018/03/19/sbuild-debian-developer-setup.html
On Mon, Dec 3, 2018 at 6:56 PM Enrico
entry is present.
On Wed, Nov 28, 2018 at 4:48 PM Michael Stapelberg
wrote:
> Glad to hear it worked out!
>
> On Wed, Nov 28, 2018 at 2:27 PM Tong Sun wrote:
>
>> On Wed, Nov 28, 2018 at 2:16 AM Michael Stapelberg wrote:
>> >> So basically, following the steps you l
Glad to hear it worked out!
On Wed, Nov 28, 2018 at 2:27 PM Tong Sun wrote:
> On Wed, Nov 28, 2018 at 2:16 AM Michael Stapelberg wrote:
> >> So basically, following the steps you listed, everything went through
> >> without any problem.
> >> However, when I switch
ed, and the only one has
> "git20151108" in it:
>
> $ grep git20151108 debian/changelog debian/compat debian/control
> debian/copyright debian/docs debian/gbp.conf debian/gitlab-ci.yml
> debian/rules debian/source/format debian/watch
> debian/changelog:golang-github-da
salsa?
On Tue, Nov 27, 2018 at 5:04 AM Tong Sun wrote:
> On Mon, Nov 26, 2018 at 1:47 PM Michael Stapelberg wrote:
>
> > Can you reproduce this with the steps I listed?
> >
> > If yes, it might be a good idea to file a bug report against
> git-buildpackage.
>
> Thank
I can’t reproduce this issue. I ran:
% go get -u github.com/Debian/dh-make-golang
% dh-make-golang github.com/danverbraganza/varcaser
% cd golang-github-danverbraganza-varcaser
% git remote set-url origin g...@salsa.debian.org:
go-team/packages/golang-github-danverbraganza-varcaser.git
% gbp push
ow it is 0.9.10+nmu1.
> >
> > Many thanks
> >
> > On Sun, Nov 25, 2018 at 4:27 AM Michael Stapelberg
> > wrote:
> > >
> > > Do you have a ~/.gbp.conf? If yes, can you rename the file and try
> again?
> > >
> > > Which versio
Do you have a ~/.gbp.conf? If yes, can you rename the file and try again?
Which version of gbp-buildpackage do you use?
On Sun, Nov 25, 2018 at 5:48 AM Tong Sun wrote:
> There isn't much prerequisite to use dh-make-golang, right?
>
> I gave it a try today and this is what I get:
>
> $ dh-make-g
[+cc docker-maint, Arnaud (who did substantial work on docker and its
dependencies), Dmitry (who last touched the package)]
Arnaud, Dmitry, any advice as to how people can best help with docker?
On Wed, Sep 26, 2018 at 7:36 PM shirish शिरीष wrote:
> Dear all,
>
> Few days back I saw this bug #9
The video is now available: https://www.youtube.com/watch?v=xQNWrFw2bQw
On Thu, Aug 30, 2018 at 3:50 PM, Michael Stapelberg
wrote:
> Hey,
>
> Yesterday, I spoke at GopherCon in Denver about Go in Debian.
>
> You can find the slides at https://docs.google.com/presentation/d/
>
Yes, but only after checking with release team that they’re indeed in favor
of such a change.
On Fri, Sep 7, 2018 at 4:35 AM, Shengjing Zhu wrote:
> On Fri, Sep 7, 2018 at 4:42 AM Sean Whitton
> > Yes. Policy was changed to say that Built-Using should be used only for
> > licensing issues. Th
Hey,
Yesterday, I spoke at GopherCon in Denver about Go in Debian.
You can find the slides at
https://docs.google.com/presentation/d/1W0xjmh85A8DoGvQa2-MrLayyEec7ivArCus1YvruHiI/edit?usp=sharing
You can find a live blog at
https://about.sourcegraph.com/go/gophercon-2018-go-in-debian/
The video
We only ever ship Go sources in the library packages, never compiled object
files. What you’re seeing is intended.
On Wed, Aug 22, 2018 at 9:00 PM, Julian Gilbey wrote:
> Hi all,
>
> Now I'm a little bemused again...
>
> I'm looking at
> https://salsa.debian.org/go-team/packages/golang-github-ha
First, create a GitLab account: https://signup.salsa.debian.org/
Then, apply to join the Go packaging team (https://go-team.pages.debian.net/)
on GitLab: https://salsa.debian.org/go-team/
Lastly, create a repository using “dh-make-golang create-salsa-project”,
then push to it.
Let me know how it
On Mon, Jul 30, 2018 at 12:03 AM, Aaron Jacobs wrote:
> I hate to be the guy who does this, but does anyone know how to unsubscribe
> from this list? I've suddenly started receiving email for a reason I don't
> understand, and there are no instructions at the bottom of the email as I
> would
>
W
On Sat, Jul 28, 2018 at 1:54 AM, Alexandre Viau wrote:
> Hello!
>
> For some of you, this will be the first message that you receive from
> this mailing list.
>
> This mailing list replaces the previous Alioth list, pkg-go-maintainers.
>
> pkg-go-maintainers subscriptions were moved to this list
45 matches
Mail list logo
