On Sun, Dec 27, 2009 at 1:01 PM, Tim Spriggs <t...@tajinc.org> wrote: > Hi All, > > [disclaimer] Sorry if this is old information as I don't know what has been > going on behind the scenes since I've been away for a while. [/disclaimer] > > I recently tried to get a devzone dist-update'd on gnusolaris.org and ran > into: > > E: Internal Error, Could not perform immediate configuration (2) on sunwcsu > > which is associated with several apt bugs and has been fixed in a later apt > revision than is in Nexenta (more on that in a minute) > > > First of all, what happened to the NCP 2.0 version of the released packages? > Did NCP 3.0 bits just overwrite those completely? > Hi Tim,
http://apt.nexenta.org/ncp2/ is where the NCP2 repository is where the hardy-unstable from NCP2 is maintained. This is the b104 based kernel. > How do I support my NCP > 2.0 systems that I _really can't upgrade_ right now? I realize that NCP 2.0 > was shipped with hardy-unstable as the default repository target but there > was also a hardy-stable which wasn't changing and was supposed to be for > small/security updates only. I get an http access denied error when I try to > access hardy-stable. > Currently we have not pushed any updates to hardy-stable that I now of.. so unstable and stable would be the same. The repositories are maintained in ZFS datasets, and we can export a clone of unstable as stable under http://apt.nexenta.org/ncp2/. > > Ok, so moving on I decided to just go with the flow and try to update the > nexenta apt package by applying patches from Ubuntu Intrepid sources. This > is turning out to be a real mess because of the way the Nexenta sources have > been updated. What I was really hoping I could do is: > > % diff -ruN apt-0.7.9ubuntu17 apt-0.7.14ubuntu6.1 > > upgrade-nexenta-base.patch > % cd apt-0.7.9nexenta27; patch -p1 < ../upgrade-nexenta-base.patch > > > However, the file apt-pkg/deb/dpkgpm.cc is so majorly hacked up to pieces > that a diff is all but completely useless. This is even after running indent > on all versions concerned since the source in the nexenta repository had > some other form of indented code than is the style used in the upstream > code. > > Finally, another 45 files don't diff straight through that are related to > translations. 43 of them break on references to dpkgpm.cc. > > --- > Somehow we need to fix these issues if Nexenta as an open-source platform is > to be taken seriously. In general many things are not currently done right > and need to be fixed in terms of allowing/reviewing/maintaining patches. In > specific, I've merged apt/dpkg sources in the past and it has always been a > major headache. > I agree. Diffs should be straight patches.. but the way most of them end up being created are as diffs of source directories. This means (for example) changes to makefiles that are automatically generated during the build process are recorded. So you end up with the diff also recording changes to makefiles (like datestamps, and some temporary path changes) which are unnecessary. ~Anil _______________________________________________ gnusol-devel mailing list gnusol-devel@lists.sonic.net http://lists.sonic.net/mailman/listinfo/gnusol-devel
