[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#854395: marked as done (RFS: golang-go-xdg/0~bzr20140219-2 -- Go interface for XDG standards)



Your message dated Tue, 28 Mar 2017 18:50:32 +0000 (UTC)
with message-id <590812699.9581790.1490727032882@mail.yahoo.com>
and subject line Re: Bug#854395: RFS: golang-go-xdg/0~bzr20140219-2 [RC] -- Go interface for XDG standards
has caused the Debian Bug report #854395,
regarding RFS: golang-go-xdg/0~bzr20140219-2 -- Go interface for XDG standards
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
854395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854395
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: important
X-Debbugs-Cc: pkg-go-maintainers@lists.alioth.debian.org,
sergio.schvezov@canonical.com, tag@pault.ag, rogershimizu@gmail.com

Dear mentors,

I am looking for a sponsor for my package "golang-go-xdg"

 * Package name    : golang-go-xdg
   Version         : 0~bzr20140219-2
   Upstream Author : John R. Lenton.
 * URL             : https://launchpad.net/go-xdg
 * License         : BSD-2-Clause
   Section         : devel

  It builds those binary packages:

    golang-go-xdg-dev - Go interface for XDG standards

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/golang-go-xdg

  Alternatively, one can download the package with dget using this command:

    dget -x https://mentors.debian.net/debian/pool/main/g/golang-go-xdg/golang-go-xdg_0~bzr20140219-2.dsc

or you can use git-buildpackage to build:
  gbp clone --pristine-tar
https://anonscm.debian.org/git/pkg-go/packages/golang-go-xdg.git
  cd golang-go-xdg
  git checkout mentors
  gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar

I also made it available on debomatic (amd64):
  http://debomatic-amd64.debian.net/distribution#unstable/golang-go-xdg/0~bzr20140219-2/buildlog

  Changes since the last upload:

  * Team upload.

  [ Paul Tagliamonte ]
  * Use a secure transport for the Vcs-Git and Vcs-Browser URL

  [ Roger Shimizu ]
  * debian/control:
    - Update Build-Depends on golang-check.v1-dev, in stead of
      golang-gocheck-dev which is already non-active upstream.
    - Use cgit URL for Vcs-Browser.
  * debian/patches:
    - Add a patch to use golang-check.v1-dev.
    - Add a patch to remove failure tests (Closes: #830446).

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

--- End Message ---
--- Begin Message ---

Hello,


>> 1) did you forward the patch upstream?

>

>sorry, no.

>upstream hosts in launchpad, which I don't have an account.



maybe sending an email to some dev would be nice!

>> 2) why are you disabling tests?

>my local gbp build (with or without pbuilder) is fine, however two

>test items fail on debomatic.

>I already paste the log from debomatic to the patch.


it fails in pbuilder too

base_directory_test.go:45:

c.Check(h, Matches, s.home+".*"+s.val1)

... value string = "/root/something"

... regex string = "/home/locutus.*something"



reason is, somewher xdg is returning my $HOME to be /root,

but echo $HOME returns /home/locutus


this is probably related to the fact I'm inside a chroot,

where /home/locutus points to nothing, while /root is my directory


(I'm root but $HOME is not the root one)


anyhow,

HOME=/root dpkg-buildpackageworks here



>I'm not sure. Last upload was 3 years ago, though.>I don't use the package myself, but it's a dependency of another

>package I'm interested in, so I'm just trying to help on this package.


seems legit


>Since I fixed another library dependency issue (Build-Depends on

>golang-check.v1-dev), how about upload first to experimental without

>the patch disabling two tests, to see how the test goes on buildd

>(instead of debomatic)?

>If the two tests fail also on buildd, we can investigate further.

>

>If you agree with things above, I can prepare another upload to mentors. Thanks!



lets go for unstable instead :)
please push the tag on git!

G.

--- End Message ---

Reply to: