The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

More dselect experiences

Dispite all the connectivity problems we are having at the moment, I was 
able to get a "newest" set of the base packages and ran another test with 
dselect. 
I was very disappointed with it's behavior. It went through the 
installation in alphabetical order rather than in dependency order (and 
it seemed to me that it didn't do this the last time I used it, but I 
could have a different version). As a result, the installation died, due 
to too many errors. After running install a total of three times it was 
finally able to complete the installation. I thought the beauty of 
dselect was supposed to be it's ability to recursively move toward an 
installation. I did not realize that I was the one who had to recurse the 
process :-)
I don't look forward to advertizing this process in my upgrade document.

After getting the base packages installed (I allowed libc4 to replace 
libc, as deselect seemed to prefer) I attempted to install the 
development packages. Here I ran into unrecoverable complications. First 
I was told:
libc5-dev conflicts with libc(<<4.6.72-11)
when I checked later with dpkg -s libc, I was told that, indeed libc had 
a version of 4.6.72-4, but it was also marked uninstalled! Doesn't that 
count as "not a conflict"? At this point I quit looking at any more 
problems and got out. The binary package being attempted was 
libc5-dev-5.2.18-4.deb and should be the latest version. It appears that 
when dselect installed libc4 and said that it was removing libc that 
marking it as uninstalled was not sufficient to resolve the above conflict.

Any ideas?

Dwarf

------------                                          --------------

aka   Dale Scheetz                   Phone:   1 (904) 877-0257
      Flexible Software              Fax:     NONE 
      Black Creek Critters           e-mail:  dwarf@polaris.net

------------ If you don't see what you want, just ask --------------