On Jan 10, 2013, at 7:59 PM, Alexander Hansen <alexanderk.han...@gmail.com> wrote:
> On 1/10/13 5:01 PM, Merle Reinhart wrote: >> Alex, >> >> There are some initial install/use problems/mis-understandings with the new >> passwd stuff. >> >> When I updated, everything failed because it could not find >> /sw/etc/passwd.conf. It appears it was passwd-core that was looking for it >> to write into couldn't find it. >> >> /sw/bin/dpkg-lockwait -r fink-buildlock-passwd-core-20130103-1 >> (Reading database ... 276012 files and directories currently installed.) >> Removing fink-buildlock-passwd-core-20130103-1 ... >> Reading buildlock packages... >> All buildlocks accounted for. >> /sw/bin/dpkg-lockwait -i >> /sw/fink/dists/stable/main/binary-darwin-x86_64/base/passwd-avahi_20130103-1_darwin-x86_64.deb >> >> /sw/fink/dists/stable/main/binary-darwin-x86_64/base/passwd-core_20130103-1_darwin-x86_64.deb >> >> /sw/fink/dists/stable/main/binary-darwin-x86_64/base/passwd-games_20130103-1_darwin-x86_64.deb >> >> /sw/fink/dists/stable/main/binary-darwin-x86_64/base/passwd-messagebus_20130103-1_darwin-x86_64.deb >> (Reading database ... 276011 files and directories currently installed.) >> Preparing to replace passwd-avahi 20100305-5 (using >> .../passwd-avahi_20130103-1_darwin-x86_64.deb) ... >> Unpacking replacement passwd-avahi ... >> Preparing to replace passwd-core 20100305-5 (using >> .../passwd-core_20130103-1_darwin-x86_64.deb) ... >> Unpacking replacement passwd-core ... >> Preparing to replace passwd-games 20100305-5 (using >> .../passwd-games_20130103-1_darwin-x86_64.deb) ... >> Unpacking replacement passwd-games ... >> Preparing to replace passwd-messagebus 20100305-5 (using >> .../passwd-messagebus_20130103-1_darwin-x86_64.deb) ... >> Unpacking replacement passwd-messagebus ... >> Setting up passwd-core (20130103-1) ... >> We recommend allocating UIDs and GIDs automatically, >> unless you have specific requirements for UIDs and GIDs. >> Set UIDs/GIDs automatically? [Y/n] n >> OK. You will be prompted to enter ID numbers for each passwd-* user. >> cp: /sw/share/passwd-core/passwd.conf: No such file or directory > > That just got fixed in 20130103-2. > >> /sw/bin/dpkg: error processing passwd-core (--install): >> subprocess post-installation script returned error exit status 1 >> dpkg: dependency problems prevent configuration of passwd-games: >> passwd-games depends on passwd-core (>= 20130103-1); however: >> Package passwd-core is not configured yet. >> /sw/bin/dpkg: error processing passwd-games (--install): >> dependency problems - leaving unconfigured >> dpkg: dependency problems prevent configuration of passwd-messagebus: >> passwd-messagebus depends on passwd-core (>= 20130103-1); however: >> Package passwd-core is not configured yet. >> /sw/bin/dpkg: error processing passwd-messagebus (--install): >> dependency problems - leaving unconfigured >> dpkg: dependency problems prevent configuration of passwd-avahi: >> passwd-avahi depends on passwd-core (>= 20130103-1); however: >> Package passwd-core is not configured yet. >> /sw/bin/dpkg: error processing passwd-avahi (--install): >> dependency problems - leaving unconfigured >> Errors were encountered while processing: >> passwd-core >> passwd-games >> passwd-messagebus >> passwd-avahi >> ### execution of /sw/bin/dpkg-lockwait failed, exit code 1 >> >> >> >> >> >> >> I found touching the file initially to create it, then installing >> passwd-core seems to have done the job. However..... >> >> >> I wanted to pick my UIDs/GIDs since I need all my systems to have the same >> mapping to user/group name, so I picked 'n' when asked the question and that >> leads to the following: >> >> The following package will be installed or updated: >> passwd-core >> Reading buildlock packages... >> All buildlocks accounted for. >> /sw/bin/dpkg-lockwait -i >> /sw/fink/dists/stable/main/binary-darwin-x86_64/base/passwd-core_20130103-1_darwin-x86_64.deb >> (Reading database ... 276018 files and directories currently installed.) >> Preparing to replace passwd-core 20130103-1 (using >> .../passwd-core_20130103-1_darwin-x86_64.deb) ... >> Unpacking replacement passwd-core ... >> Setting up passwd-core (20130103-1) ... >> We recommend allocating UIDs and GIDs automatically, >> unless you have specific requirements for UIDs and GIDs. >> Set UIDs/GIDs automatically? [Y/n] n >> OK. You will be prompted to enter ID numbers for each passwd-* user. >> >> [HexaMacPro:~] merle% >> >> >> >> Not what I was expecting since it said it was going to prompt. That message >> should be updated to indicate that each individual passwd-* package (but no >> passwd-core) will prompt. >> > > When you install a passwd-* that doesn't exist, at that time you will be > prompted. I thought that was relatively clear, but yeah, there was room > for improvement. > >> So, I started with passwd-messagebus and that worked fine as it already >> existed. However, where does fink keep that information? > > That information is gleaned from the DirectoryServices database via the > 'id' and 'dscl' commands. It isn't kept anywhere by Fink anymore. > > With the old system, it was possible to just rerun the post-install > script to create the identical UID/GID map to username/groupname on a > different clean system. Is that still possible? > > No. > > Or do we now have to do all this hand-holding every single time we bring > in a new or rebuild a system? > > At least until the next release. > > Sorry about the change in behavior. Most of our users don't need to > worry about such issues, or get the special users from central directory > servers, so the "manual choice" option kind of got shortchanged. > >> >> >> >> Thanks! Just trying to understand what extra work is now on the user verses >> fink keeping track of it. >> >> Merle >> >> > > The least troublesome option for everybody would probably be to make an > optional new package which contains passwd-fink and group-fink, and to > have the "manual choice" option from passwd-core look for data in those > files first, and fall back to prompting for a value if the files or the > relevant user are not present. That way we can still allow the > passwd-user packages to be separated from passwd-core to cut down on > unnecessary updates. > > I'll set up a sandbox for that. > -- > Alexander Hansen, Ph.D. > Fink User Liaison > My package updates: http://finkakh.wordpress.com/ > > ------------------------------------------------------------------------------ Alex, Thanks for the consideration. I'll wait patiently for future updates. Merle ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
