(to use apt-cacher-ng, I have to manually identify and kill the apt-
cacher-ng process, then "/etc/init.d/apt-cacher-ng start" works)
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubun
I also confirm the bug is reproduced under jaunty with version 0.3.4-1.
sudo /etc/init.d/apt-cacher-ng start
* Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s) could
I can confirm the issue:
k...@ubuntu:~/Desktop/apt-cacher-ng$ sudo /etc/init.d/apt-cacher-ng start
* Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s)
That's correct. The error message is about the IPv6 socket not being
created. Unfortunately the order of libc (getaddrinfo result) seems to
have been changed and that causes the problem now.
If you need IPv6, there is a quick workaround: put all your interface
IPs (in v4 and v6 versions) into the
The 0.3.4 version fixes the bug.
I have built the package in my PPA and requested a FFe: LP: #344168
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Already got one ACK in bug 344168.
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Second ACK.
FFe granted.
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
bug 344168
The new version fixes the bug.
** Changed in: apt-cacher-ng (Ubuntu)
Status: New => Fix Released
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is
With Package: apt-cacher-ng Version: 0.3.4-1 on Jaunty i still get this issue
at acng startup by the way apt-cacher-ng is working.
I cannot get access via web to manage the cache.
Thanks
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received
** Changed in: apt-cacher-ng (Ubuntu)
Status: Fix Released => New
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
(to use apt-cacher-ng, I have to manually identify and kill the apt-
cacher-ng process, then "/etc/init.d/apt-cacher-ng start" works)
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubun
I also confirm the bug is reproduced under jaunty with version 0.3.4-1.
sudo /etc/init.d/apt-cacher-ng start
* Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s) could
With Package: apt-cacher-ng Version: 0.3.4-1 on Jaunty i still get this issue
at acng startup by the way apt-cacher-ng is working.
I cannot get access via web to manage the cache.
Thanks
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received
** Changed in: apt-cacher-ng (Ubuntu)
Status: Fix Released => New
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
That's correct. The error message is about the IPv6 socket not being
created. Unfortunately the order of libc (getaddrinfo result) seems to
have been changed and that causes the problem now.
If you need IPv6, there is a quick workaround: put all your interface
IPs (in v4 and v6 versions) into the
The 0.3.4 version fixes the bug.
I have built the package in my PPA and requested a FFe: LP: #344168
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Already got one ACK in bug 344168.
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Second ACK.
FFe granted.
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
I can confirm the issue:
k...@ubuntu:~/Desktop/apt-cacher-ng$ sudo /etc/init.d/apt-cacher-ng start
* Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s)
bug 344168
The new version fixes the bug.
** Changed in: apt-cacher-ng (Ubuntu)
Status: New => Fix Released
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm the issue:
k...@ubuntu:~/Desktop/apt-cacher-ng$ sudo /etc/init.d/apt-cacher-ng start
* Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s)
That's correct. The error message is about the IPv6 socket not being
created. Unfortunately the order of libc (getaddrinfo result) seems to
have been changed and that causes the problem now.
If you need IPv6, there is a quick workaround: put all your interface
IPs (in v4 and v6 versions) into the
The 0.3.4 version fixes the bug.
I have built the package in my PPA and requested a FFe: LP: #344168
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Already got one ACK in bug 344168.
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Second ACK.
FFe granted.
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
bug 344168
The new version fixes the bug.
** Changed in: apt-cacher-ng (Ubuntu)
Status: New => Fix Released
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(to use apt-cacher-ng, I have to manually identify and kill the apt-
cacher-ng process, then "/etc/init.d/apt-cacher-ng start" works)
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubun
I also confirm the bug is reproduced under jaunty with version 0.3.4-1.
sudo /etc/init.d/apt-cacher-ng start
* Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s) could
With Package: apt-cacher-ng Version: 0.3.4-1 on Jaunty i still get this issue
at acng startup by the way apt-cacher-ng is working.
I cannot get access via web to manage the cache.
Thanks
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received
** Changed in: apt-cacher-ng (Ubuntu)
Status: Fix Released => New
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
(to use apt-cacher-ng, I have to manually identify and kill the apt-
cacher-ng process, then "/etc/init.d/apt-cacher-ng start" works)
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubun
I also confirm the bug is reproduced under jaunty with version 0.3.4-1.
sudo /etc/init.d/apt-cacher-ng start
* Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s) could
That's correct. The error message is about the IPv6 socket not being
created. Unfortunately the order of libc (getaddrinfo result) seems to
have been changed and that causes the problem now.
If you need IPv6, there is a quick workaround: put all your interface
IPs (in v4 and v6 versions) into the
The 0.3.4 version fixes the bug.
I have built the package in my PPA and requested a FFe: LP: #344168
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Already got one ACK in bug 344168.
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Second ACK.
FFe granted.
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
I can confirm the issue:
k...@ubuntu:~/Desktop/apt-cacher-ng$ sudo /etc/init.d/apt-cacher-ng start
* Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s)
bug 344168
The new version fixes the bug.
** Changed in: apt-cacher-ng (Ubuntu)
Status: New => Fix Released
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is
With Package: apt-cacher-ng Version: 0.3.4-1 on Jaunty i still get this issue
at acng startup by the way apt-cacher-ng is working.
I cannot get access via web to manage the cache.
Thanks
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received
** Changed in: apt-cacher-ng (Ubuntu)
Status: Fix Released => New
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
That's correct. The error message is about the IPv6 socket not being
created. Unfortunately the order of libc (getaddrinfo result) seems to
have been changed and that causes the problem now.
If you need IPv6, there is a quick workaround: put all your interface
IPs (in v4 and v6 versions) into the
The 0.3.4 version fixes the bug.
I have built the package in my PPA and requested a FFe: LP: #344168
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Already got one ACK in bug 344168.
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Second ACK.
FFe granted.
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
I can confirm the issue:
k...@ubuntu:~/Desktop/apt-cacher-ng$ sudo /etc/init.d/apt-cacher-ng start
* Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s)
bug 344168
The new version fixes the bug.
** Changed in: apt-cacher-ng (Ubuntu)
Status: New => Fix Released
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(to use apt-cacher-ng, I have to manually identify and kill the apt-
cacher-ng process, then "/etc/init.d/apt-cacher-ng start" works)
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubun
I also confirm the bug is reproduced under jaunty with version 0.3.4-1.
sudo /etc/init.d/apt-cacher-ng start
* Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s) could
With Package: apt-cacher-ng Version: 0.3.4-1 on Jaunty i still get this issue
at acng startup by the way apt-cacher-ng is working.
I cannot get access via web to manage the cache.
Thanks
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received
** Changed in: apt-cacher-ng (Ubuntu)
Status: Fix Released => New
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
That's correct. The error message is about the IPv6 socket not being
created. Unfortunately the order of libc (getaddrinfo result) seems to
have been changed and that causes the problem now.
If you need IPv6, there is a quick workaround: put all your interface
IPs (in v4 and v6 versions) into the
The 0.3.4 version fixes the bug.
I have built the package in my PPA and requested a FFe: LP: #344168
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Already got one ACK in bug 344168.
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Second ACK.
FFe granted.
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
I can confirm the issue:
k...@ubuntu:~/Desktop/apt-cacher-ng$ sudo /etc/init.d/apt-cacher-ng start
* Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s)
bug 344168
The new version fixes the bug.
** Changed in: apt-cacher-ng (Ubuntu)
Status: New => Fix Released
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is
With Package: apt-cacher-ng Version: 0.3.4-1 on Jaunty i still get this issue
at acng startup by the way apt-cacher-ng is working.
I cannot get access via web to manage the cache.
Thanks
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received
** Changed in: apt-cacher-ng (Ubuntu)
Status: Fix Released => New
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
(to use apt-cacher-ng, I have to manually identify and kill the apt-
cacher-ng process, then "/etc/init.d/apt-cacher-ng start" works)
--
apt-cacher-ng start displays an invalid error message
https://bugs.launchpad.net/bugs/343927
You received this bug notification because you are a member of Ubun
I also confirm the bug is reproduced under jaunty with version 0.3.4-1.
sudo /etc/init.d/apt-cacher-ng start
* Starting apt-cacher-ng apt-cacher-ng
Couldn't bind socket: Address already in use
Couldn't bind socket: Address already in use
No socket(s) could
60 matches
Mail list logo
