apt-clone dist-upgrade from NCP1 to NCP3a failed

Then I studied the logs and decided that x11-common was the problematic package and ran sudo apt-get remove x11-common and sudo apt-get autoremove and retried sudo apt-clone dist-upgrade and it seemed to get further, as per attached "zooko.sudo_apt_clone-3.log.txt".

Thanks for the report.

The reason you're seeing this is because you're actually upgrading not to NCP2 but NCP3a1. We've not tested NCP1->3 upgrade.. and thus the above issues.

I'll shortly setup a repository pointing to actual NCP2 repository snapshot, so you can upgrade from 1->2. I'll update this bug once I've setup this repository.

Thanks.

So it is currently not possible to upgrade an existing Nexenta system to NCP2 without reinstalling from scratch? Please let me know as soon as this is possible, or if there is something I could do to help.

Hi Zooko,

I;ve setup the NCP2 repository at
http://apt.nexenta.org/ncp2/

So you can point sources.list to the below and have access to NCP2 repository as it was with b104. This should allow you to dist-upgrade form NCP1 to NCP2.

deb http://apt.nexenta.org/ncp2/ hardy-unstable main contrib non-free

Thanks,

PS: We now track all bugs at http://www.nexenta.org/projects/site . Please use this to report any issues.

I believe we need to close launchpad operation at some point. Anil, what
do you think, how can we do that?

anilg wrote:
> Hi Zooko,
>
> I;ve setup the NCP2 repository at
> http://apt.nexenta.org/ncp2/
>
> So you can point sources.list to the below and have access to NCP2
> repository as it was with b104. This should allow you to dist-upgrade
> form NCP1 to NCP2.
>
> deb http://apt.nexenta.org/ncp2/ hardy-unstable main contrib non-free
>
> Thanks,
>
> PS: We now track all bugs at http://www.nexenta.org/projects/site .
> Please use this to report any issues.
>

On Fri, Nov 27, 2009 at 11:50 PM, Erast <email address hidden> wrote:
> I believe we need to close launchpad operation at some point. Anil, what
> do you think, how can we do that?

I've added a note for now.. so All bug submitters (when submitting a
bug) will be asked to instead submit on nexenta.org.

We can do away with launchpad as we get close to NCP3 release. As an
admin I did see an option that will close the bugs section.

~Anil

Just go to https://edge.launchpad.net/nexenta/+edit and where it says "bugs are tracked" change it from "on launchpad" to instead have the URL of the new redmine.

> Just go to https://edge.launchpad.net/nexenta/+edit and where it says
> "bugs are tracked" change it from "on launchpad" to instead have the URL
> of the new redmine.
>

I checked.. and there's no way to enter a new URL.. which is why I
updated description and the bug report Note to include the new URL.

~Anil

Send mail to <email address hidden> saying "Nexenta uses http://www.nexenta.org/projects/site which is a Redmine". A human will read your note and add http://www.nexenta.org/projects/site to the list of known bug trackers (they usually do this within 24 hours!) and write back saying "Thank you". Then you can go to that https://edge.launchpad.net/nexenta/+edit and choose your bug tracker from the selection-list of all known bug trackers (alphabetically sorted). This is good not only because people who are looking for your issue tracker will find the link to it, but also because then launchpad can link together issues which span both Nexenta and other projects, such as if there is a bug in Python which needs to be patched in Nexenta but also the patch should be applied in upstream Python. It's a really cool feature.

Hey, actually I'll do the first step -- sending mail to <email address hidden>. However unless I'm given admin permission on the Nexenta project on launchpad I won't be able to do the second step. But maybe they will do that themselves when they read my mail.

Okay, I sent that mail.