Bug#921164: kubectx: FTBFS in sid

2019-02-08 Thread 陳昌倬
On Fri, Feb 08, 2019 at 05:31:02PM +0100, Santiago Vila wrote:
> Hi. The following patch may help, but I have not tested it
> (please double-check before uploading).
> 
> Thanks.
> 
> --- a/debian/rules
> +++ b/debian/rules
> @@ -1,5 +1,5 @@
>  #!/usr/bin/make -f
> -#export DH_VERBOSE = 1
> +export TERM=dumb
>  
>  %:
>   dh $@

This patch is okay in sbuild, thanks for the help. I will upload it
later.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature


Bug#921164: kubectx: FTBFS in sid

2019-02-08 Thread Santiago Vila
Hi. The following patch may help, but I have not tested it
(please double-check before uploading).

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -1,5 +1,5 @@
 #!/usr/bin/make -f
-#export DH_VERBOSE = 1
+export TERM=dumb
 
 %:
dh $@



Bug#921164: kubectx: FTBFS in sid

2019-02-08 Thread Santiago Vila
> Could you help to provide the exact command that cause FTBFS?  I use the
> following command to build with pbuilder, and it can be built
> successful.
> 
> $ gbp buildpackage --git-pbuilder

I'm using sbuild + schroot, as used in the official buildds, so the
command would be something like this:

sbuild --arch-all --no-arch-any -d sid kubectx

assuming you have a chroot called "sid".

I can also make it fail in this way:

unset TERM; dpkg-buildpackage -uc -us -A

Are you relying on TERM being defined? Maybe that's the root of the problem.
Packages must be buildable with sbuild, not just gbp or dpkg-buildpackage.

Thanks.



Bug#921164: kubectx: FTBFS in sid

2019-02-08 Thread 陳昌倬
On Sat, Feb 02, 2019 at 02:27:23PM +, Santiago Vila wrote:
> Package: src:kubectx
> Version: 0.6.3-1
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in sid but it failed:

Hi Santiago,

Could you help to provide the exact command that cause FTBFS?  I use the
following command to build with pbuilder, and it can be built
successful.

$ gbp buildpackage --git-pbuilder

-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature


Bug#921164: kubectx: FTBFS in sid

2019-02-02 Thread Santiago Vila
Package: src:kubectx
Version: 0.6.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
bats test/kubectx.bats
1..16
ok 1 --help should not fail
ok 2 -h should not fail
ok 3 switch to previous context when no one exists
not ok 4 list contexts when no kubeconfig exists
# (in test file test/kubectx.bats, line 32)
#   `[[ "$output" = "" ]]' failed

[... snipped ...]

# (in test file test/kubectx.bats, line 151)
#   `[[ "$output" = "user2@cluster1" ]]' failed
# Deleting context "user1@cluster1"...
# deleted context user1@cluster1 from /tmp/tmp.x9iuA0so15/config
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# user2@cluster1
not ok 13 delete current context
# (in test file test/kubectx.bats, line 169)
#   `[[ "$output" = "user1@cluster1" ]]' failed
# Switched to context "user2@cluster1".
# Deleting context "user2@cluster1"...
# warning: this removed your active context, use "kubectl config use-context" 
to select a different one
# deleted context user2@cluster1 from /tmp/tmp.Bcwc8cKMwj/config
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# user1@cluster1
ok 14 delete non existent context
not ok 15 delete several contexts
# (in test file test/kubectx.bats, line 190)
#   `[[ "$output" = "" ]]' failed
# Deleting context "user1@cluster1"...
# deleted context user1@cluster1 from /tmp/tmp.u0qR27XfVH/config
# Deleting context "user2@cluster1"...
# deleted context user2@cluster1 from /tmp/tmp.u0qR27XfVH/config
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
not ok 16 delete several contexts including a non existent one
# (in test file test/kubectx.bats, line 203)
#   `[[ "$output" = "user2@cluster1" ]]' failed
# Deleting context "user1@cluster1"...
# deleted context user1@cluster1 from /tmp/tmp.P7RwbY7pJw/config
# Deleting context "non-existent"...
# error: cannot delete context non-existent, not in /tmp/tmp.P7RwbY7pJw/config
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# tput: No value for $TERM and no -T specified
# user2@cluster1
make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:5: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://buildd.debian.org/status/package.php?p=kubectx

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.