[Bug 1678463] Re: wput should be compiled with TLS support

2017-06-08 Thread Marcos Diez
Hi Stephan!

It's me again...

The Ubuntu package was still without TLS.

So I read the documentation on how to create an Debian/Ubuntu package,
created one and found the issue.

The fix is here:

https://github.com/marcosdiez/wput/commit/e4625ad73e964ac280ff1d18376b21d44e93

I tested creating the package both on Debian Jessie and Ubuntu and it
worked on both.

As a nice side effect, the other patch to configure.in ( 13-configure.in
--gcrypt-link.patch ) no works as well. But it actually does not make
any difference in wput, it's just for detecting the library.

I hope the issue is finally really fixed.
Marcos

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678463

Title:
  wput should be compiled with TLS support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wput/+bug/1678463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1678463] Re: wput should be compiled with TLS support

2017-06-08 Thread Marcos Diez
** Changed in: wput (Ubuntu)
   Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678463

Title:
  wput should be compiled with TLS support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wput/+bug/1678463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1678463] Re: wput should be compiled with TLS support

2017-06-07 Thread Marcos Diez
Hi Stephen,

I found out the problem and solved it. Now I need you to your magic and
make it an "official package" (TM)

The problem is that ./configure was not properly detecting if GnuTLS is 
available or not.
To be more specific, ./configure was passing the gcc parameters in the wrong 
way.

It was passing:

gcc -lgnutls -lgnutls-openssl test_file.c

and it should be:

gcc test_file.c -lgnutls -lgnutls-openssl


The fix for this issue is here:
https://github.com/marcosdiez/wput/commit/f5f3d70c4eef7db62a1b33efaaaf4a42417c95da

BUT after changing configure.in I had to run autoconf again.

So you might as well get the whole thing:

https://github.com/marcosdiez/wput/commit/6daa01608b8abc0d5d6c60a60d780a135ba5b3bb

In order for me to do that I:

a) cloned the original wput repository 
(https://sourceforge.net/p/wput/code/ci/master/tree/)
b) applied all the debian patches in the order of 'debian/patches/series'
c) fixed the code

All these steps are separated into specific commits:
https://github.com/marcosdiez/wput/commits/master

So I guess the problem is solved, I just don't know how to continue from now on.
Please help!

Marcos

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678463

Title:
  wput should be compiled with TLS support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wput/+bug/1678463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1678463] Re: wput should be compiled with TLS support

2017-06-07 Thread Marcos Diez
Hi

You are right, on debian it is working (
https://packages.debian.org/sid/amd64/wput/download )

On Ubuntu it is not.

I think I was able to change the bug back to In Progress (here on
Ubutu).

I just had to click on the Status and there was a list to pick from.

I actually have no clue what is necessary to compile it with TLS.

In Ubuntu, no matter what I do it always says TLS is not found.

I am also looking for a solution.

Thanks again,
Marcos

** Changed in: wput (Ubuntu)
   Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678463

Title:
  wput should be compiled with TLS support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wput/+bug/1678463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1678463] Re: wput should be compiled with TLS support

2017-06-07 Thread Marcos Diez
Hi Stephen!

I downloaded
http://launchpadlibrarian.net/322656352/wput_0.6.2+git20130413-5_amd64.deb

I tried ./wput --help 
and it still does not have SSL there.

Sorry for delivering bad news
Marcos

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678463

Title:
  wput should be compiled with TLS support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wput/+bug/1678463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1678463] [NEW] wput should be compiled with TLS support

2017-04-01 Thread Marcos Diez
Public bug reported:

Although wput originally supports TLS encryption, the version provided by 
Ubuntu does not.
This is a shame in a post Snowden world.

You can see that it supports out of the box:

https://sourceforge.net/p/wput/code/ci/master/tree/INSTALL

but somehow even on Ubuntu 17.04 that option is still not available.
(the flag is disabled in compile time compilation)

Here is the output of a custom compiled version of wput:

wput --help

--
[a lot of stuff]
FTP-Options:
  -p,  --port-mode no-passive, turn on port mode ftp (def. pasv)
  -A,  --ascii force ASCII  mode-transfer
  -B,  --binaryforce BINARY mode-transfer
  -m,  --chmod change mode of transferred files ([0-7]{3})
   --force-tls force the useage of TLS
   --disable-tls   disable the usage of TLS


See wput(1) for more detailed descriptions of the options.
Report bugs and suggestions via SourceForge at
http://sourceforge.net/tracker/?group_id=141519

-

** Affects: wput (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678463

Title:
  wput should be compiled with TLS support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wput/+bug/1678463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1575169] Re: On 16.04, neither lxc nor lxd containers with 14.04 run docker

2016-05-20 Thread Marcos Diez
Just to be clear, I did not update ubuntu 15.10 to 16.04. It's still
ubuntu 15.10, except that docker dos not work in it's 14.04 LXC/D
containers.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575169

Title:
  On 16.04, neither lxc nor lxd containers with 14.04 run docker

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1575169/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1575169] Re: On 16.04, neither lxc nor lxd containers with 14.04 run docker

2016-05-20 Thread Marcos Diez
Hi Again.

Yesterday I naively did apt-get update on ubuntu 15.10 (which could run
docker on lxc containers with ubuntu 14.04) and  now docker does not
work anymore over there :(

Please please please fix this issue kind of soon.
Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575169

Title:
  On 16.04, neither lxc nor lxd containers with 14.04 run docker

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1575169/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1581152] [NEW] virtualenv-clone does not clone propelry some envs

2016-05-12 Thread Marcos Diez
Public bug reported:

In 2015 I found a bug on virtualenv-clone.


Sometimes the source virtual environment has symlinks that point to itself
one example is $OLD_VIRTUAL_ENV/local/lib points to $OLD_VIRTUAL_ENV/lib

After cloning the virtualenv, the new virtual env must have the
following symlink:

$NEW_VIRTUAL_ENV/local/lib will point to $NEW_VIRTUAL_ENV/lib


Usually this goes unnoticed unless one tries to upgrade a package though pip, 
so this bug is hard to find.

I sent a pull request to the virtualenv-clone author and it got merged:
https://github.com/edwardgeorge/virtualenv-clone/pull/17/files

So all I am requesting here is for the ubuntu package to be updated.

One way to reproduce this is to install Django via pip. It creates these
symlinks.

** Affects: virtualenv-clone (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: virtualenv-clone

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581152

Title:
  virtualenv-clone does not clone propelry some envs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualenv-clone/+bug/1581152/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1574944] Re: On 16.04, neither lxc nor lxd containers with 14.04 run docker

2016-04-26 Thread Marcos Diez
Thanks!

Since somehow this bug is not showing up on the docker.io team, I opened
it again.

the link is here for future reference
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1575169

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574944

Title:
  On 16.04, neither lxc nor lxd containers with 14.04 run docker

To manage notifications about this bug go to:
https://bugs.launchpad.net/docker.io/+bug/1574944/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1575169] [NEW] On 16.04, neither lxc nor lxd containers with 14.04 run docker

2016-04-26 Thread Marcos Diez
Public bug reported:

On a Ubuntu 16.04 server amd64 host, docker does not work inside of a
(lxc or lxd) Ubuntu 14.04 guest.

I tested on both a clean Ubuntu 16.04 install and also one that was
upgraded from Ubuntu 15.10.

My definition of work is having the expected result when running

---
   sudo docker run hello-world
---

If the guest containers is also Ubuntu 16.04, it works out of the box.

The images were made either using

lxc-create -t download -n test01 -- -d ubuntu -r trusty -a amd64

or on lxd following the syntax from
https://www.stgraber.org/2016/03/11/lxd-2-0-introduction-to-lxd-112/

Just for further reference, If the host is 15.10, one can have docker
inside of LXC containers if one does the following:

a) on the host:
   add this to /etc/lxc/default.conf

lxc.aa_profile = unconfined
lxc.cgroup.devices.allow = a
lxc.cap.drop =

   sudo mv /usr/share/lxc/config/common.conf.d/00-lxcfs.conf 
/usr/share/lxc/config/common.conf.d/00-lxcfs.conf.disabled
   iptables -L # really. this loads modules that the docker install needs to be 
happy
   ip6tables -L # really. this loads modules that the docker install needs to 
be happy

create the guest with something like

lxc-create -t download -n test01 -- -d ubuntu -r trusty -a amd64

b) on the guest

   sudo apt-get install curl apparmor cgroup-lite

   curl -fsSL https://get.docker.com/ | sudo sh # the docker from apt-
get install docker.io does not work,

   sudo docker run hello-world

I personally consider this bug very important because 15.10 will be
unsupported in July, so not upgrading will become an insecure choice to
make.

If there is any way I can help you, please let me know.

Thanks

Marcos

ps: this is a copy of https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1574944
but somehow the bug was not showing up here because the "this repository must 
be configured for bugs to be forwarded", so I am just duplicating it.

** Affects: docker.io (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: lts lxc trusty ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575169

Title:
  On 16.04, neither lxc nor lxd containers with 14.04 run docker

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1575169/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1574944] [NEW] On 16.04, neither lxc nor lxd containers with 14.04 run docker

2016-04-25 Thread Marcos Diez
Public bug reported:


On a Ubuntu 16.04 server amd64 host, docker does not work inside of a
(lxc or lxd) Ubuntu 14.04 guest.

I tested on both a clean Ubuntu 16.04  install and also one that was
upgraded from Ubuntu 15.10.

My definition of work is having the expected result when running

---
   sudo docker run hello-world
---

If the guest containers is also Ubuntu 16.04, it works out of the box.


The images were made either using

lxc-create -t download -n test01 -- -d ubuntu -r trusty -a amd64

or on lxd following the syntax from
https://www.stgraber.org/2016/03/11/lxd-2-0-introduction-to-lxd-112/


Just for further reference,  If the host is 15.10, one can have docker inside 
of LXC containers if one does the following:

a) on the host:
   add this to /etc/lxc/default.conf

lxc.aa_profile = unconfined
lxc.cgroup.devices.allow = a
lxc.cap.drop =

   sudo mv /usr/share/lxc/config/common.conf.d/00-lxcfs.conf 
/usr/share/lxc/config/common.conf.d/00-lxcfs.conf.disabled
   iptables -L   # really. this loads modules that the docker install needs to 
be happy
   ip6tables -L  # really. this loads modules that the docker install needs to 
be happy

create the guest with something like

lxc-create -t download -n test01 -- -d ubuntu -r trusty -a amd64

b) on the guest

   sudo apt-get install curl apparmor cgroup-lite

   curl -fsSL https://get.docker.com/ | sudo sh   # the docker from apt-
get install docker.io does not work,


   sudo docker run hello-world


I personally consider this bug very important because 15.10 will be unsupported 
in July, so not upgrading will become an insecure choice to make.

If there is any way I can help you, please let me know.

Thanks

Marcos

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lxd 2.0.0-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Tue Apr 26 00:37:03 2016
InstallationDate: Installed on 2016-02-18 (67 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
SourcePackage: lxd
UpgradeStatus: Upgraded to xenial on 2016-04-21 (4 days ago)

** Affects: lxd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574944

Title:
  On 16.04, neither lxc nor lxd containers with 14.04 run docker

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1574944/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs