[Bug 1574270] Re: applications segfault systematically with tsocks
Additional confirmation; the patch works for me as well - thanks all! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574270 Title: applications segfault systematically with tsocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tsocks/+bug/1574270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235681] Re: squid3 always run with -N option, incompatible with SMP option (workers)
Thanks for the reminder! I think I'll give it a try since this is something that would improve Squid performance for us. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1235681 Title: squid3 always run with -N option, incompatible with SMP option (workers) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1235681/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1235681] Re: squid3 always run with -N option, incompatible with SMP option (workers)
Thanks for the reminder! I think I'll give it a try since this is something that would improve Squid performance for us. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235681 Title: squid3 always run with -N option, incompatible with SMP option (workers) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1235681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235681] Re: squid3 always run with -N option, incompatible with SMP option (workers)
I have also encountered the two issues Michael mentions and two others in the upstart script /etc/init/squid3 that are - from my perspective - essential to get SMP Squid3 working. They are: * an expect daemon line needs to be included * a statement that checks for the presence of /var/run/squid3 and creates the directory if necessary, as well as granting the squid3 process owner write permissions in the directory. However; seeing as this issue has not seen any activity or resolution, is my impression correct that (a) SMP Squid has very few active users, and (b) despite this being a buggy feature in an LTS release, this is not a priority to be fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235681 Title: squid3 always run with -N option, incompatible with SMP option (workers) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1235681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235681] Re: squid3 always run with -N option, incompatible with SMP option (workers)
I have also encountered the two issues Michael mentions and two others in the upstart script /etc/init/squid3 that are - from my perspective - essential to get SMP Squid3 working. They are: * an expect daemon line needs to be included * a statement that checks for the presence of /var/run/squid3 and creates the directory if necessary, as well as granting the squid3 process owner write permissions in the directory. However; seeing as this issue has not seen any activity or resolution, is my impression correct that (a) SMP Squid has very few active users, and (b) despite this being a buggy feature in an LTS release, this is not a priority to be fixed? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1235681 Title: squid3 always run with -N option, incompatible with SMP option (workers) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1235681/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078213] Re: logs are not logrotated
** Changed in: juju-core Importance: Medium = High ** Changed in: juju-core Milestone: None = 1.21-alpha1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078213 Title: logs are not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1078213/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078213] Re: logs are not logrotated
** Changed in: juju-core Importance: Medium = High ** Changed in: juju-core Milestone: None = 1.21-alpha1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078213 Title: logs are not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1078213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1291230] Re: Unity greeter does not show users with high uid
I can confirm that this is still present in 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1291230 Title: Unity greeter does not show users with high uid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1291230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1287147] Re: [FFe] juju-core 1.18
We decided that we should land everything but HA and VLAN work this week in a stable release to minimize the risk that either of those changes could have on overall stability in the release. However, HA and VLAN work is underway, and much of it has already landed, and the first HA support is expected to land in a development release in the next several days. On Mon, Apr 7, 2014 at 12:44 PM, Dave Walker davewal...@ubuntu.com wrote: There seems to be some confusion or change in plans. The original description states 1.18 consists of: 1) HA of Juju state nodes 2) Full support for ppc64el and arm64 But the revised timeline says Without HA. Is HA no longer a release target? Other than supporting ppc64el and arm64, are there any other featureful changes? Thanks. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1287147 Title: [FFe] juju-core 1.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1287147/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1287147 Title: [FFe] juju-core 1.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1287147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1208430] Re: mongodb runs as root user
** Changed in: juju-core Importance: High = Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1208430] Re: mongodb runs as root user
Reducing the security implications of running MongoDB is an important thing for us to do. It's not quite critical, because nobody is asking for it directly now, and the risk is still somewhat limited. But there is a risk, and I think the general policy of treating even security -- even relatively lower risk stuff -- as important is a good habit of mind for us. We are going to be at the center of a lot of important developments. On the other hand once you can control the MongoDB server, your opportunities for privilege escalation on hosts in that environment are probably greater in other directions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1287147] Re: [FFe] juju-core 1.18
We decided that we should land everything but HA and VLAN work this week in a stable release to minimize the risk that either of those changes could have on overall stability in the release. However, HA and VLAN work is underway, and much of it has already landed, and the first HA support is expected to land in a development release in the next several days. On Mon, Apr 7, 2014 at 12:44 PM, Dave Walker davewal...@ubuntu.com wrote: There seems to be some confusion or change in plans. The original description states 1.18 consists of: 1) HA of Juju state nodes 2) Full support for ppc64el and arm64 But the revised timeline says Without HA. Is HA no longer a release target? Other than supporting ppc64el and arm64, are there any other featureful changes? Thanks. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1287147 Title: [FFe] juju-core 1.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1287147/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287147 Title: [FFe] juju-core 1.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1287147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208430] Re: mongodb runs as root user
** Changed in: juju-core Importance: High = Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208430] Re: mongodb runs as root user
Reducing the security implications of running MongoDB is an important thing for us to do. It's not quite critical, because nobody is asking for it directly now, and the risk is still somewhat limited. But there is a risk, and I think the general policy of treating even security -- even relatively lower risk stuff -- as important is a good habit of mind for us. We are going to be at the center of a lot of important developments. On the other hand once you can control the MongoDB server, your opportunities for privilege escalation on hosts in that environment are probably greater in other directions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208430] Re: mongodb runs as root user
** Changed in: juju-core Milestone: None = 1.18.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1208430] Re: mongodb runs as root user
** Changed in: juju-core Milestone: None = 1.18.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@jamie However, I don't feel the download size is itself a blocker. We can perform uploads for everything at first, figure out how to be smarter/more selective later and along the way work with upstream on dynamic linking if that makes sense. I think that is particularly true in *this* case where we are talking just about Juju Core. Of course as a standard policy, for a future where there may be many go applications in the distro, I think we really do want either golang-go or gcc-go with dynamic linking to be moved into a supportable state. And I also agree that we should not confuse the current case (1 app) with the future. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@gustavo I think it is right that there are many people in the go community who would welcome dynamic linking in golang-go, but I also think that if we want to have it, we need to do the work to add it there. Now that we have to have Arm64 and Power, if we are going to be investing in improving a toolchain for Go, I'm not exactly sure where that dev effort should go -- improving, fixing, and making GCC a viable option for us, or doing the dynamic linking in upstream go, as well as figuring out an alternative solution for architectures not supported by golango-go. What are your thoughts on the matter? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@martin Traditionally the Tech board has nacked everything in main which pulls code from third-party sources, i. e. installer packages. Packages in main must not enable any third-party PPA, pull code or binaries from an upstream site and run it, and so on. I think a key point here is that the juju package does not generally install or pull down binaries from anywhere to your machine. It does instruct the cloud installation of a server to use a specific ubuntu image from simplestreams and a specific jujud binary (also from simplestreams) on the remote host. (Caveat: I have no idea what simplestreams is and how it works; the description on https://launchpad.net/simplestreams isn't very enlightening, but it sounds like you want to use it as a kind of package distribution system not unlike pip?) Simplestreams is a tool the server team created to help us catalog, sign, and distribute cloud images which are Ubuntu OS images, which can be generic, or customized to run on a specific cloud. The server that gets launched in the cloud when you use juju bootstrap picks a cloud image from simplestreams, verifies it's cryptographic signature, and starts a machine using it, we then grab the appropriate juju binary from simplestreams and install it (again on the remote server). So, juju isn't creating a need to trust simplestreams for the juju binary -- it already must be trusted for cloud images. And we're not creating our own system of packaging for jujud binaries, we're just piggiybacking on the way we distribute Ubuntu images in a cloud context. There is a small caveat: juju does have a local provider feature that sets up lxc containers and runs the jujud binary there. The local provider is designed to simulate a full cloud environment in containers on your local system, and when you do that we do the same thing as I mentioned in doing on the remote side above, we use simplestreams to select the right cloud image, and juju tools binary. That is the only case in which the juju client would download a binary from simplestreams and run it locally, and in that case it is downloading both the cloud image, and the juju binary. So, fixing the juju binary doesn't fix that -- we're still grabbing a binary blob from simplestreams and executing it locally -- the cloud image itself. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@all Given the timeline and the various other bits on our roadmap, I think main inclusion for juju core is *not* critical this cycle. We would rather get agreement, and get this done the right way than create last minute chaos for the release. But, it is critical that we sort this and the MRE out as cleanly and quickly as possible. Juju is a key to our strategy of growing Ubuntu's presence in the server and cloud worlds, and we can't afford not to be united in our approach. My understanding of the current state of the conversation is that we need to solve two major issues: 1) Package security update rules/processes for Go. 2) SimpleStreams/Tools not in the package issues I think that we are making good progress on the first issue. It seems like there are both short and long term activities that need to happen, and which we can include in our various team plans for next cycle. We can get embedded libraries out, rebuild when needed, and simultaneously try to push forward the state of the art on either GCC go, or the state of dynamic linking on golang-go. I am less sure about us being on a path towards consensus on the second item though... My belief is that the juju team is doing something completely sane given that they have a mandate to support multiple OS's, and a mandate to support cloud image distribution through simplestreams already. And I think that it is not at all fair to call juju a installer package since the external distribution of tools is mostly a remote side issue, where this juju client package is not installed at all. Since we are dropping this MIR for this cycle, can we setup time to go through this issue across the teams, and get alignment after the release, but before the Juju cloud sprint at the end of April? Also, if I'm missing any critical issues on which we have to have alignment, but don't, please raise them NOW rather than wait until the end of the next cycle -- so we can make sure we put aside time to deal with them properly this time. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@gustavo I think it is right that there are many people in the go community who would welcome dynamic linking in golang-go, but I also think that if we want to have it, we need to do the work to add it there. Now that we have to have Arm64 and Power, if we are going to be investing in improving a toolchain for Go, I'm not exactly sure where that dev effort should go -- improving, fixing, and making GCC a viable option for us, or doing the dynamic linking in upstream go, as well as figuring out an alternative solution for architectures not supported by golango-go. What are your thoughts on the matter? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@jamie However, I don't feel the download size is itself a blocker. We can perform uploads for everything at first, figure out how to be smarter/more selective later and along the way work with upstream on dynamic linking if that makes sense. I think that is particularly true in *this* case where we are talking just about Juju Core. Of course as a standard policy, for a future where there may be many go applications in the distro, I think we really do want either golang-go or gcc-go with dynamic linking to be moved into a supportable state. And I also agree that we should not confuse the current case (1 app) with the future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@martin Traditionally the Tech board has nacked everything in main which pulls code from third-party sources, i. e. installer packages. Packages in main must not enable any third-party PPA, pull code or binaries from an upstream site and run it, and so on. I think a key point here is that the juju package does not generally install or pull down binaries from anywhere to your machine. It does instruct the cloud installation of a server to use a specific ubuntu image from simplestreams and a specific jujud binary (also from simplestreams) on the remote host. (Caveat: I have no idea what simplestreams is and how it works; the description on https://launchpad.net/simplestreams isn't very enlightening, but it sounds like you want to use it as a kind of package distribution system not unlike pip?) Simplestreams is a tool the server team created to help us catalog, sign, and distribute cloud images which are Ubuntu OS images, which can be generic, or customized to run on a specific cloud. The server that gets launched in the cloud when you use juju bootstrap picks a cloud image from simplestreams, verifies it's cryptographic signature, and starts a machine using it, we then grab the appropriate juju binary from simplestreams and install it (again on the remote server). So, juju isn't creating a need to trust simplestreams for the juju binary -- it already must be trusted for cloud images. And we're not creating our own system of packaging for jujud binaries, we're just piggiybacking on the way we distribute Ubuntu images in a cloud context. There is a small caveat: juju does have a local provider feature that sets up lxc containers and runs the jujud binary there. The local provider is designed to simulate a full cloud environment in containers on your local system, and when you do that we do the same thing as I mentioned in doing on the remote side above, we use simplestreams to select the right cloud image, and juju tools binary. That is the only case in which the juju client would download a binary from simplestreams and run it locally, and in that case it is downloading both the cloud image, and the juju binary. So, fixing the juju binary doesn't fix that -- we're still grabbing a binary blob from simplestreams and executing it locally -- the cloud image itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@all Given the timeline and the various other bits on our roadmap, I think main inclusion for juju core is *not* critical this cycle. We would rather get agreement, and get this done the right way than create last minute chaos for the release. But, it is critical that we sort this and the MRE out as cleanly and quickly as possible. Juju is a key to our strategy of growing Ubuntu's presence in the server and cloud worlds, and we can't afford not to be united in our approach. My understanding of the current state of the conversation is that we need to solve two major issues: 1) Package security update rules/processes for Go. 2) SimpleStreams/Tools not in the package issues I think that we are making good progress on the first issue. It seems like there are both short and long term activities that need to happen, and which we can include in our various team plans for next cycle. We can get embedded libraries out, rebuild when needed, and simultaneously try to push forward the state of the art on either GCC go, or the state of dynamic linking on golang-go. I am less sure about us being on a path towards consensus on the second item though... My belief is that the juju team is doing something completely sane given that they have a mandate to support multiple OS's, and a mandate to support cloud image distribution through simplestreams already. And I think that it is not at all fair to call juju a installer package since the external distribution of tools is mostly a remote side issue, where this juju client package is not installed at all. Since we are dropping this MIR for this cycle, can we setup time to go through this issue across the teams, and get alignment after the release, but before the Juju cloud sprint at the end of April? Also, if I'm missing any critical issues on which we have to have alignment, but don't, please raise them NOW rather than wait until the end of the next cycle -- so we can make sure we put aside time to deal with them properly this time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@adam I think you'd agree that the obvious and simple usecase isn't I installed juju-core on my Ubuntu desktop so I can rollout charms on OSX and Solaris. Don't forget it will not support: old Ubuntu versions, Arm64, or power, other versions of Linux, Windows, or anything but the series that the package belongs to. I think we can all agree that a Trusty desktop and Precise database server is a pretty common situation, and the combination of all the things that won't work is definitely common enough to make it a real issue. So, if we can build them with the packages, what's stopping us from having a package that includes the bits, and even depends on the right things to set up a simplestreams provider that people can use on their closed networks? We certainly *can* do that. I have no objection to it in principle. But, before we go down the path of what's stopping us, Let's take a look at the situation now: The obvious and simple use case is that I'm using Amazon, or Azure, Joyent, or HP Cloud. In those cases the tools are pre-published to a cloud local bucket and it would slow things down and create pain for the user if binaries had to be copied over from the local disk into the cloud. To top it off, the jujud binary isn't used locally (except of course when you are deploying charms locally) so having it on local disk is just waste in those cases. Furthermore, we need tools to be published to all the major clouds *before* the matching client lands in Ubuntu, because a new clients can require matching tools to bootstrap a new environment. (We do however maintain and stringently test backwards compatibility with already bootstrapped environments). We *have to* publish tools in simplestreams. We *can* put them in the package too -- as a limited and broken fallback mechanism that doesn't support multiple archs, doesn't support multiple series, doesn't support multiple OS's. My question is, if I take folks away from current projects, and have them update the packaging so that the tools you mention are there, what exactly does that buy us? I'm happy to do it, but I would like to know why exactly you want it, and what benifit it provides to our users. Another idea we had was to build tools for all supported series, OS's and arch's and put them in a single package, with the bits you need to push things up in a simplestreams location for your closed network. But our belief was that such a package would never be supported, particularly since the binaries in question won't be run on the local machine anyway, and are likely to just be a waste of disk space. We've done a lot of thinking on this, and we have *tried* to figure out how to use ubuntu packages to distribute tools -- and fundamentally simplestreams is a better fit for the needs of a multi-os, multi-arch, multi-series orchestration tool. And we already force users to trust simplestreams to get Ubuntu images, so we're not adding *another* mechanism, just re-using one that already exists and is quite widely used. --Mark On Wed, Mar 26, 2014 at 5:54 PM, Adam Conrad adcon...@0c3.net wrote: @Mark So, if we can build them with the packages, what's stopping us from having a package that includes the bits, and even depends on the right things to set up a simplestreams provider that people can use on their closed networks? Sure, that won't have ALL the binaries for all supported platforms available, without a source to grab those from, but it would keep it self-contained for the simple use-case. I think you'd agree that the obvious and simple usecase isn't I installed juju-core on my Ubuntu desktop so I can rollout charms on OSX and Solaris. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@adam I think you'd agree that the obvious and simple usecase isn't I installed juju-core on my Ubuntu desktop so I can rollout charms on OSX and Solaris. Don't forget it will not support: old Ubuntu versions, Arm64, or power, other versions of Linux, Windows, or anything but the series that the package belongs to. I think we can all agree that a Trusty desktop and Precise database server is a pretty common situation, and the combination of all the things that won't work is definitely common enough to make it a real issue. So, if we can build them with the packages, what's stopping us from having a package that includes the bits, and even depends on the right things to set up a simplestreams provider that people can use on their closed networks? We certainly *can* do that. I have no objection to it in principle. But, before we go down the path of what's stopping us, Let's take a look at the situation now: The obvious and simple use case is that I'm using Amazon, or Azure, Joyent, or HP Cloud. In those cases the tools are pre-published to a cloud local bucket and it would slow things down and create pain for the user if binaries had to be copied over from the local disk into the cloud. To top it off, the jujud binary isn't used locally (except of course when you are deploying charms locally) so having it on local disk is just waste in those cases. Furthermore, we need tools to be published to all the major clouds *before* the matching client lands in Ubuntu, because a new clients can require matching tools to bootstrap a new environment. (We do however maintain and stringently test backwards compatibility with already bootstrapped environments). We *have to* publish tools in simplestreams. We *can* put them in the package too -- as a limited and broken fallback mechanism that doesn't support multiple archs, doesn't support multiple series, doesn't support multiple OS's. My question is, if I take folks away from current projects, and have them update the packaging so that the tools you mention are there, what exactly does that buy us? I'm happy to do it, but I would like to know why exactly you want it, and what benifit it provides to our users. Another idea we had was to build tools for all supported series, OS's and arch's and put them in a single package, with the bits you need to push things up in a simplestreams location for your closed network. But our belief was that such a package would never be supported, particularly since the binaries in question won't be run on the local machine anyway, and are likely to just be a waste of disk space. We've done a lot of thinking on this, and we have *tried* to figure out how to use ubuntu packages to distribute tools -- and fundamentally simplestreams is a better fit for the needs of a multi-os, multi-arch, multi-series orchestration tool. And we already force users to trust simplestreams to get Ubuntu images, so we're not adding *another* mechanism, just re-using one that already exists and is quite widely used. --Mark On Wed, Mar 26, 2014 at 5:54 PM, Adam Conrad adcon...@0c3.net wrote: @Mark So, if we can build them with the packages, what's stopping us from having a package that includes the bits, and even depends on the right things to set up a simplestreams provider that people can use on their closed networks? Sure, that won't have ALL the binaries for all supported platforms available, without a source to grab those from, but it would keep it self-contained for the simple use-case. I think you'd agree that the obvious and simple usecase isn't I installed juju-core on my Ubuntu desktop so I can rollout charms on OSX and Solaris. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@adam We *can* build and include tools binaries in the package. And in fact for many tools, we extract them from the builds, and upload them to a central distribution point (which uses the same toolchain as the ubuntu cloud images catalog -- simplestreams. But, we don't distribute the tools binaries via ubuntu packages because they aren't installed on the a juju client user's machine. So we aren't pulling down binaries to extend what we package on the local machine -- we are pulling down binaries on the server side that the local juju client talks too. We MUST distribute them through another mechanism because they will need to be chosen at workload deployment time based on whatever architecture, series, juju client version, and OS combination that is being targeted when that server is deployed. The key here is multi-OS support, we need to be able to support other unix and non-unix OS's, and we want one, standard code path for everything. The local juju client package is not the right place for tools. This has nothing to do with hiding anything, and our prefered mechanism is to create the binaries in the archive -- where we don't we create them in PPA's now, and we will document a secure process for building them for non Ubuntu OS's as we start officially supporting those OS's next cycle. We use simplestreams because we already have code that uses simplestreams to select the right architecture, series, and version for cloud images -- so we are re-using that same functionality to allow us to fulfill our multi-platform mandate in a sane way. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
@adam We *can* build and include tools binaries in the package. And in fact for many tools, we extract them from the builds, and upload them to a central distribution point (which uses the same toolchain as the ubuntu cloud images catalog -- simplestreams. But, we don't distribute the tools binaries via ubuntu packages because they aren't installed on the a juju client user's machine. So we aren't pulling down binaries to extend what we package on the local machine -- we are pulling down binaries on the server side that the local juju client talks too. We MUST distribute them through another mechanism because they will need to be chosen at workload deployment time based on whatever architecture, series, juju client version, and OS combination that is being targeted when that server is deployed. The key here is multi-OS support, we need to be able to support other unix and non-unix OS's, and we want one, standard code path for everything. The local juju client package is not the right place for tools. This has nothing to do with hiding anything, and our prefered mechanism is to create the binaries in the archive -- where we don't we create them in PPA's now, and we will document a secure process for building them for non Ubuntu OS's as we start officially supporting those OS's next cycle. We use simplestreams because we already have code that uses simplestreams to select the right architecture, series, and version for cloud images -- so we are re-using that same functionality to allow us to fulfill our multi-platform mandate in a sane way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294747] Re: mongodb fails assertion on ppc64el with 64k pagesize
This bug is also impacting the juju-mongodb package, and therefore juju on ppc64el. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1294747 Title: mongodb fails assertion on ppc64el with 64k pagesize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1294747/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1294747] Re: mongodb fails assertion on ppc64el with 64k pagesize
This bug is also impacting the juju-mongodb package, and therefore juju on ppc64el. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294747 Title: mongodb fails assertion on ppc64el with 64k pagesize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1294747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273769] Re: ppc64el enablement for juju/lxc
Dave, can you turn you hack of your working copy into a branch proposal? ** Changed in: juju-core Importance: High = Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1273769 Title: ppc64el enablement for juju/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1273712] Re: jujud dies on ppc64el architecture
Since we are using 4.9, can we just delete this from Juju Core, and kill it? ** Changed in: juju-core Importance: High = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1273712 Title: jujud dies on ppc64el architecture To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273712/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1273769] Re: ppc64el enablement for juju/lxc
Dave, can you turn you hack of your working copy into a branch proposal? ** Changed in: juju-core Importance: High = Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273769 Title: ppc64el enablement for juju/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273712] Re: jujud dies on ppc64el architecture
Since we are using 4.9, can we just delete this from Juju Core, and kill it? ** Changed in: juju-core Importance: High = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273712 Title: jujud dies on ppc64el architecture To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229275] Re: [maas] juju destroy-environment also destroys nodes that are not controlled by juju
** Changed in: juju-core Milestone: 2.0 = 1.17.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: [maas] juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1229275/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1229275] Re: [maas] juju destroy-environment also destroys nodes that are not controlled by juju
** Changed in: juju-core Milestone: 2.0 = 1.17.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: [maas] juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1229275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219879] Re: [FFe] juju-core 1.16 for Ubuntu 13.10
** Description changed: juju-core 1.16.0 stable release is due by the 3rd October and includes the following features over the version already in the archive: * MAAS Tag support * Get juju tools and cloud configuration data from a central well know location * support for --ssl-hostname-verification: false * API only communication with the state server for all non-state-server agents (not CLI, and not removing direct mongo access for agents at earlier versions) * manual provisioning, bootstrap and null provider -- ability to create nodes and even bootstrap a full environment using pre-existing machines and SSH. * Support for the VPC by default changes on EC2 * Improved hook error reporting - * CLI tool caches endpoint addresses locally for faster connect time * Early failure when we know up front that lxc containers can't get addresses Possible additional features. * KVM container support * Split out ~/.juju/environments/env.yaml (related to the endpoint caching feature above) + * CLI tool caches endpoint addresses locally for faster connect time - Approval is sought from the release team to upgrade to this new version - upon release. + + Approval is sought from the release team to upgrade to this new version upon release. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1219879 Title: [FFe] juju-core 1.16 for Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1219879/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1219879] Re: [FFe] juju-core 1.16 for Ubuntu 13.10
** Description changed: juju-core 1.16.0 stable release is due by the 3rd October and includes the following features over the version already in the archive: * MAAS Tag support * Get juju tools and cloud configuration data from a central well know location * support for --ssl-hostname-verification: false * API only communication with the state server for all non-state-server agents (not CLI, and not removing direct mongo access for agents at earlier versions) * manual provisioning, bootstrap and null provider -- ability to create nodes and even bootstrap a full environment using pre-existing machines and SSH. * Support for the VPC by default changes on EC2 * Improved hook error reporting - * CLI tool caches endpoint addresses locally for faster connect time * Early failure when we know up front that lxc containers can't get addresses Possible additional features. * KVM container support * Split out ~/.juju/environments/env.yaml (related to the endpoint caching feature above) + * CLI tool caches endpoint addresses locally for faster connect time - Approval is sought from the release team to upgrade to this new version - upon release. + + Approval is sought from the release team to upgrade to this new version upon release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219879 Title: [FFe] juju-core 1.16 for Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1219879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229275] Re: juju destroy-environment also destroys nodes that are not controlled by juju
** Changed in: juju Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1229275/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1229275] Re: juju destroy-environment also destroys nodes that are not controlled by juju
** Changed in: juju Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1229275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219879] Re: [FFe] juju-core 1.16 for Ubuntu 13.10
** Description changed: - For Ubuntu 13.10, we will want to drop in another stable milestone of - juju-core prior to release. + Currently Ubuntu saucy is tracking the inAPI only non-bootstrap + agentsterim releases of juju-core (1.13.x series). - juju-core 1.16 is currently targetting the 3rd October for release; in - additional to bug fixes this release will include the following key - features: + This series will form the 1.16.0 stable release in the next week or so + and includes the following features over the version already in the + archive: - MarkR TBD + * MAAS Tag support + * Get juju tools and cloud configuration data from a central well know location + * support for --ssl-hostname-verification: false + * API only communication with the state server for all non-state-server agents (not CLI, and not removing direct mongo access for agents at earlier versions) + * manual provisioning, bootstrap and null provider -- ability to create nodes and even bootstrap a full environment using pre-existing machines and SSH. + * Support for the VPC by default changes on EC2 + * Improved hook error reporting + * CLI tool caches endpoint addresses locally for faster connect time + * Early failure when we know up front that lxc containers can't get addresses - Approval is sought from the release team for the feature freeze - exception. + Possible additional features. + + * KVM container support + * Split out ~/.juju/environments/env.yaml (related to the endpoint caching feature above) + + Approval is sought from the release team for this upgrade plan. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1219879 Title: [FFe] juju-core 1.16 for Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1219879/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1219879] Re: [FFe] juju-core 1.16 for Ubuntu 13.10
** Description changed: - For Ubuntu 13.10, we will want to drop in another stable milestone of - juju-core prior to release. + Currently Ubuntu saucy is tracking the inAPI only non-bootstrap + agentsterim releases of juju-core (1.13.x series). - juju-core 1.16 is currently targetting the 3rd October for release; in - additional to bug fixes this release will include the following key - features: + This series will form the 1.16.0 stable release in the next week or so + and includes the following features over the version already in the + archive: - MarkR TBD + * MAAS Tag support + * Get juju tools and cloud configuration data from a central well know location + * support for --ssl-hostname-verification: false + * API only communication with the state server for all non-state-server agents (not CLI, and not removing direct mongo access for agents at earlier versions) + * manual provisioning, bootstrap and null provider -- ability to create nodes and even bootstrap a full environment using pre-existing machines and SSH. + * Support for the VPC by default changes on EC2 + * Improved hook error reporting + * CLI tool caches endpoint addresses locally for faster connect time + * Early failure when we know up front that lxc containers can't get addresses - Approval is sought from the release team for the feature freeze - exception. + Possible additional features. + + * KVM container support + * Split out ~/.juju/environments/env.yaml (related to the endpoint caching feature above) + + Approval is sought from the release team for this upgrade plan. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219879 Title: [FFe] juju-core 1.16 for Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1219879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
My apologies; in the rush of things to do, I'd forgotten about this. Yes, my account is actually currently in the expiration cycle. I will test in a few hours time and report back. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
Ran into dependancy issues. There was a conflict between the existing samba-common (2:3.6.3-2ubuntu2.6) package and the samba-common-bin (2:3.6.3-2ubuntu2.7) package that has blocked me from further work - I can't login anymore. WIll try to do further tests tomorrow when I'm back in the office (given that I can recover my system). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
My apologies; in the rush of things to do, I'd forgotten about this. Yes, my account is actually currently in the expiration cycle. I will test in a few hours time and report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
Ran into dependancy issues. There was a conflict between the existing samba-common (2:3.6.3-2ubuntu2.6) package and the samba-common-bin (2:3.6.3-2ubuntu2.7) package that has blocked me from further work - I can't login anymore. WIll try to do further tests tomorrow when I'm back in the office (given that I can recover my system). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
I'm not either on an account that is close to expiration, will talk to colleagues next week and see if someones account is close to expiring (I'm on vacation right now). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
I'm not either on an account that is close to expiration, will talk to colleagues next week and see if someones account is close to expiring (I'm on vacation right now). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
On 26 June 2013 20:30, Bryan Quigley gqu...@gmail.com wrote: Has this been confirmed to be fixed via this patch with other user accounts at this point? If so, we should start the SRU process.. Yes, it works for all user accounts. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
On 26 June 2013 20:30, Bryan Quigley gqu...@gmail.com wrote: Has this been confirmed to be fixed via this patch with other user accounts at this point? If so, we should start the SRU process.. Yes, it works for all user accounts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172215] Re: [FFe] Please include juju-core 1.10.0 in Ubuntu 13.04
I don't believe this decision makes sense for users. The Go port of juju is supported, maintained, and users who opt in to using it now will be able to avoid a painful migration later. Since this is fully opt-in, there is no advantage to waiting for backports to pull it in. It is a stand-alone package so will by definition not break anything else on the system. And having it in backports requires multiple steps of to get the package, enables a bunch of packages most server admins won't want, and thus requires pinning to get go juju. What is the case against inclusion now? Just that it is new? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172215 Title: [FFe] Please include juju-core 1.10.0 in Ubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1172215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172215] Re: [FFe] Please include juju-core 1.10.0 in Ubuntu 13.04
Known broken sounds incorrect for the situation here. What we have is known incomplete, which is significantly different both practically and philosophically. 100% feature complete is a software myth. So that's not a real argument. But go juju has an upgrade path, and has a team ready to support it, and this is fully opt-in. As for a fair bit of potential future work -- that is a possibility. But this is a critical package for many people, and we are giving them a way to move forward in a supported way, which is not the case currently, so it seems like that work will be valuable to users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172215 Title: [FFe] Please include juju-core 1.10.0 in Ubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1172215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172215] Re: [FFe] Please include juju-core 1.10.0 in Ubuntu 13.04
We are fully committed to not regressing and creating a sane upgrade path. We have people on this, to make sure that happens. And again this is a stand-alone package with no dependencies -- so I don't think the risks are that significant. But I understand that this is not my decision. I'm just making the case for inclusion, because it is what I think is best for users today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172215 Title: [FFe] Please include juju-core 1.10.0 in Ubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1172215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
Sorry, Luca, yes - we have tested your patch and it worked fine for one user! We are just waiting for other user accounts to expire... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
Sorry, Luca, yes - we have tested your patch and it worked fine for one user! We are just waiting for other user accounts to expire... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064771] Re: Frigöra diskutrymme på adder
De enda paketen av ovan lista jag skulle rekommendera att behålla är diff och unzip. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/1064771 Title: Frigöra diskutrymme på adder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-se-server/+bug/1064771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 952113] Re: [ 5589.174937] [drm] nouveau 0000:01:00.0: GPU lockup - switching to software fbcon
Happens to me as well: lshw -c display *-display description: VGA compatible controller product: GF108 [Quadro 1000M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:16 memory:d000-d0ff memory:c000-c7ff memory:c800-c9ff ioport:4000(size=128) memory:d108-d10f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/952113 Title: [ 5589.174937] [drm] nouveau :01:00.0: GPU lockup - switching to software fbcon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/952113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
Excellent work, Luca! Will test your patch as soon as I can. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
Excellent work, Luca! Will test your patch as soon as I can. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
Sorry about the delayed response, took a while to get hold of the info: our domain controllers are Win 2008 R2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
Actually, this is not the first time we see a similar issue. We ran into it with 10.04 / Lucid + samba + gdm and this was before our domain controllers were 2008 R2. I can't quite remeber what fixed it then (I'm still digging through old emails) but I have a vague memory of it being fixed by a samba / winbind patch. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
Sorry about the delayed response, took a while to get hold of the info: our domain controllers are Win 2008 R2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
Actually, this is not the first time we see a similar issue. We ran into it with 10.04 / Lucid + samba + gdm and this was before our domain controllers were 2008 R2. I can't quite remeber what fixed it then (I'm still digging through old emails) but I have a vague memory of it being fixed by a samba / winbind patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
I can confimr that this bug also affects me. Is there any information I can provide to help unearth the cause? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring
I can confimr that this bug also affects me. Is there any information I can provide to help unearth the cause? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003296 Title: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 780220] Re: pip install numpy fail in virtualenv
I believe this issue is now resolved with the latest version of virtualenv. To give it a shot, use pip to install the latest version instead of using the packaged version. I used apt-get remove python-virtualenv apt-get install pip pip install --upgrade pip pip install virtalenv Was then able to install numpy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780220 Title: pip install numpy fail in virtualenv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/780220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 800447] Re: Oneiric Installer ISO has ramzswap error during boot
Same here, error while trying to install with the latest daily build .iso inside VirtualBox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/800447 Title: Oneiric Installer ISO has ramzswap error during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/800447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 775415] Re: Fails to build numpy within a virtual environment
Exact same problem in current build of 11.10 Trying to install numpy: python2.7 setup.py install works well But in the virtual environment mkvirtualenv test --no-site-packages -p python2.7 python2.7 setup.py install fails with the same error message. I think this is distinct from Bug #780220 as the error message is different. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/775415 Title: Fails to build numpy within a virtual environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/775415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 780220] Re: pip install numpy fail in virtualenv
The bug is also present on 11.04 if using pip to install the latest version of virtualenv (1.6.1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780220 Title: pip install numpy fail in virtualenv -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 780220] Re: pip install numpy fail in virtualenv
That is, still fails to pip install numpy within virtualenv 1.6.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780220 Title: pip install numpy fail in virtualenv -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 775415] Re: Fails to build numpy within a virtual environment
On natty, python 2.7.1-0ubuntu5 virtualenv=1.6.1 virtualenvwrapper=2.7.1 python-numpy installs fine. While trying to install numpy 1.6.0 from source, I run into Bug #780220 https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/780220 (same errors as when using pip install numpy within virtualenv) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/775415 Title: Fails to build numpy within a virtual environment -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 637702] Re: Prompted to unlock keyring twice on log in
Have the same problem, it asks me 3 times to unock ring after atologin. I'm running Natty 11.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/637702 Title: Prompted to unlock keyring twice on log in -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779712] Re: file transfer cancelled before people can see it
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779712 Title: file transfer cancelled before people can see it -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779712] [NEW] file transfer cancelled before people can see it
Public bug reported: Binary package hint: pidgin When i try to send a file to a MSN contact over Windows, they will never get the option to accept the transfer, after some time i will get the message error that the contact canceled the file transfer when they didn't even saw it. Same thing happen with contacts trying to send files to me, i don't see the files and after some time they see i canceled it. In i try to send a file to another Ubuntu/Pidgin user, Pidgin will just crash after initiate the transfer. Ubuntu 11.04 Pidgin 2.7.11 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: pidgin 1:2.7.11-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Sun May 8 21:28:43 2011 ExecutablePath: /usr/bin/pidgin InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pidgin UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (evince-thumbnailer:4256): Poppler-CRITICAL **: PopplerPage* poppler_document_get_page(PopplerDocument*, int): assertion `0 = index index poppler_document_get_n_pages (document)' failed (evince-thumbnailer:4256): Poppler-CRITICAL **: void poppler_page_get_size(PopplerPage*, double*, double*): assertion `POPPLER_IS_PAGE (page)' failed (evince-thumbnailer:4256): Poppler-CRITICAL **: GdkPixbuf* poppler_page_get_thumbnail_pixbuf(PopplerPage*): assertion `POPPLER_IS_PAGE (page)' failed (evince-thumbnailer:4256): Poppler-CRITICAL **: void poppler_page_render_to_pixbuf(PopplerPage*, int, int, int, int, double, int, GdkPixbuf*): assertion `POPPLER_IS_PAGE (page)' failed ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779712 Title: file transfer cancelled before people can see it -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 775415] [NEW] Fails to build numpy within a virtual environment
Public bug reported: Binary package hint: python2.7 On Ubuntu 10.10, using python2.7: 2.7-6 virtualenv=1.6.1 virtualenvwrapper==2.6.3 numpy-1.5.1 Trying to install numpy: python2.7 setup.py install works well But in the virtual environment, mkvirtualenv test --no-site-packages -p python2.7 python2.7 setup.py install fails: running install running build running config_cc unifing config_cc, config, build_clib, build_ext, build commands --compiler options running config_fc unifing config_fc, config, build_clib, build_ext, build commands --fcompiler options running build_src build_src building py_modules sources building library npymath sources error: None The build process inside the virtual environment works if python2.7 is built from source instead of using the packaged version. ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: python2.7 On Ubuntu 10.10, using python2.7: 2.7-6 virtualenv=1.6.1 virtualenvwrapper==2.6.3 numpy-1.5.1 Trying to install numpy: - Running python2.7 setup.py install works well, but in the virtual environment + python2.7 setup.py install works well + + But in the virtual environment, mkvirtualenv test --no-site-packages -p python2.7 - - python2.7 setup.py install fails with + python2.7 setup.py install + fails: running install running build running config_cc unifing config_cc, config, build_clib, build_ext, build commands --compiler options running config_fc unifing config_fc, config, build_clib, build_ext, build commands --fcompiler options running build_src build_src building py_modules sources building library npymath sources error: None - However, the build process inside the virtual environment works if - python2.7 .1is built from source instead of using the packaged version. + The build process inside the virtual environment works if python2.7 is + built from source instead of using the packaged version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/775415 Title: Fails to build numpy within a virtual environment -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 760091] Re: Mouse become unusable after some time on Unity
I'm having the same problem, also with Fireworks CS3 in Wine. I upgraded from 10.10 to 11.04 yesterday and today i noticed i'm having this problem. With Thunderbird, it happens after some time, with fireworks is always. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760091 Title: Mouse become unusable after some time on Unity -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483912] Re: When sorting by track number, sometimes track 1 is incorrectly sorted at the bottom
I noticed this today, and after reading a lot around and compare track Information of the songs in the same album, I noticed that there were inconsistencies in my library, not sure yet if it can be considered as a bug, but for example: Showing only this album, sorting by track number. Album: Absolution Artist: Muse Songs: 15 The song number 15 was showing at the top of the list. (15, 1,2,3,4,5,6,7,8,9,10,1,12,13,14) Showing all albums, sorting by album The song 15 was showing separate from other Absolution songs. I discovered that the track information in the son 15 didn't have the 'Year' field, and that was causing it to show in a different spot. After fixing the Year, it shows correctly sorted with the other songs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/483912 Title: When sorting by track number, sometimes track 1 is incorrectly sorted at the bottom -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 718726] [NEW] package samba4 4.0.0~alpha15~git20110124.dfsg1-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: Binary package hint: samba4 When updating to 11.04 ProblemType: Package DistroRelease: Ubuntu 11.04 Package: samba4 4.0.0~alpha15~git20110124.dfsg1-2 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic i686 Architecture: i386 Date: Mon Feb 14 11:07:17 2011 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1) SourcePackage: samba4 Title: package samba4 4.0.0~alpha15~git20110124.dfsg1-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 ** Affects: samba4 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/718726 Title: package samba4 4.0.0~alpha15~git20110124.dfsg1-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 718726] Re: package samba4 4.0.0~alpha15~git20110124.dfsg1-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/718726 Title: package samba4 4.0.0~alpha15~git20110124.dfsg1-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534629] Re: AssumeDefaultDomain does not work
At my company we simply chose to give up on likewise. We've migrated to Samba / winbind instead. -- AssumeDefaultDomain does not work https://bugs.launchpad.net/bugs/534629 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562913] Re: NFS4 acl ops do not work with standard kernel
Since this bug is a showstopper for us (we are in the process of setting up an Ubuntu 10.04 NFS v4 server with ~1500 Ubuntu 10.04 client machines) I would very much like to know if the mentioned patch will be making it into the kernel for lucid (1) at all and (2) if there has been a decision to include it is there a time estimate on when it will make it into the mainstream? Thanks for your time and great work! -- NFS4 acl ops do not work with standard kernel https://bugs.launchpad.net/bugs/562913 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34181] Re: locale and charset problem in mysql - default character set should be set to utf8
Mathias, do you mind explaining why you keep rejecting this request? From my - and several others - perspective it seems quite natural for utf8 to be the default. Particularly in view of the fact that complete internationalization has been a longstanding goal for the Ubuntu distribution. -- locale and charset problem in mysql - default character set should be set to utf8 https://bugs.launchpad.net/bugs/34181 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 34181] Re: locale and charset problem in mysql - default character set should be set to utf8
Mathias, do you mind explaining why you keep rejecting this request? From my - and several others - perspective it seems quite natural for utf8 to be the default. Particularly in view of the fact that complete internationalization has been a longstanding goal for the Ubuntu distribution. -- locale and charset problem in mysql - default character set should be set to utf8 https://bugs.launchpad.net/bugs/34181 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429445] Re: [Karmic FFe] Sync zephyr 3.0~rc.2544-1 (main) from Debian unstable (main)
3.0~beta.2483-2 is really quite broken; it has interoperability problems, only works with the single-DES cryptosystem, the MIT kdc, and has at least one potential buffer overrun. As both the upstream and the debian maintainer, I would suggest that you probably don't want to release it as it stands. -- [Karmic FFe] Sync zephyr 3.0~rc.2544-1 (main) from Debian unstable (main) https://bugs.launchpad.net/bugs/429445 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 401362] Re: Remove zephyr-server-krb from karmic (NBS)
Something is very wrong here, and debian/rules does some black magic to move the files around, use dh_movefiles, etc. This package needs some serious cleanup, I'm afraid. If you don't like it, why are you syncing it to Ubuntu? -- Remove zephyr-server-krb from karmic (NBS) https://bugs.launchpad.net/bugs/401362 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 401362] Re: Remove zephyr-server-krb from karmic (NBS)
(sorry, that was really petty of me) -- Remove zephyr-server-krb from karmic (NBS) https://bugs.launchpad.net/bugs/401362 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38553] Re: default character set should be set to utf8
*** This bug is a duplicate of bug 34181 *** https://bugs.launchpad.net/bugs/34181 I would also like to see this bug addressed. I have had similar problems as those Alan Tam has reported. On a hunch I checked the corresponding Debian packages and the same behaviour is exhibited there, so I reported it as a bug (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438970). Maybe a change in the Debian package can attract attention from the Ubuntu package maintainers. Of course; if this is a question of limited resources I'll be happy to help out resolving this if I can. -- default character set should be set to utf8 https://bugs.launchpad.net/bugs/38553 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
