Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > muc.lists.netbsd.current-users > #31873
| From | Greg Troxel <gdt@lexort.com> |
|---|---|
| Newsgroups | muc.lists.netbsd.current-users |
| Subject | Re: error upgrading packages on current / pkg database |
| Date | 2022-04-15 13:42 -0400 |
| Organization | Newsgate at muc.de e.V. |
| Message-ID | <rmi4k2ub5uo.fsf@s1.lexort.com> (permalink) |
| References | <c6de3be3-6a9d-0935-07bc-37ac4882cc69@mudcovered.org.uk> <a8c7418c-82b9-073d-ad51-e009d6f349aa@libero.it> |
[Multipart message — attachments visible in raw view] - view raw
Mike Pumford <mpumford@mudcovered.org.uk> writes: > On 15/04/2022 17:19, Riccardo Mottola wrote: >> Hello, >> >> I did a full system upgrade (running now ) and then got current pkgsrc. >> >> Now I try to run pkg_rolling-replace -uv ; it compiled for days, then stops. >> >> disc# pkg_admin check >> ...................................pkg_admin: can't open >> /usr/pkg/pkgdb/glib2-2.70.2nb1/+CONTENTS: No such file or directory >> > Hmm. Thats interesting. I've seen that happen on one of my 9.2-STABLE > systems when doing a pkgin upgrade. Although in my case it was librsvg > that got clobbered. > > Instead of the correct pkgdb data the folder existed but contained a > random core file. The core file wasn't from any pkg tool. > I ended up with: > /usr/pkg/pkgdb/librsvg-2.52.6/gdk-pixbuf-query.core > > Which isn't even a tool I use its just something pulled in as a > dependendency. Interesting data point. I should have said as 2A: when you find a directory with broken contents, just rm -rf it, and that will get rid of the record of installation without removing the files. Then "pkg_add glib2" and perhaps "pkg_admin set automatic=yes glib2" if you want it that way, and then rerun check and rebuild-tree > you have it around so you can extract them into the folder and then > use pkg_admin to put things back together. That's what I did to sort > myself out :) > > Something like: > > tar zxf glib-2.70.2nb1.tgz +* That can work too, but either way all the cross-package data linkage may not be quite rie ght.
Back to muc.lists.netbsd.current-users | Previous | Next — Previous in thread | Next in thread | Find similar
error upgrading packages on current / pkg database Riccardo Mottola <riccardo.mottola@libero.it> - 2022-04-15 16:19 +0000
Re: error upgrading packages on current / pkg database Greg Troxel <gdt@lexort.com> - 2022-04-15 13:22 -0400
Re: error upgrading packages on current / pkg database Riccardo Mottola <riccardo.mottola@libero.it> - 2022-04-20 18:55 +0200
Re: error upgrading packages on current / pkg database Greg Troxel <gdt@lexort.com> - 2022-05-01 19:19 -0400
Re: error upgrading packages on current / pkg database Mike Pumford <mpumford@mudcovered.org.uk> - 2022-04-15 18:34 +0100
Re: error upgrading packages on current / pkg database Greg Troxel <gdt@lexort.com> - 2022-04-15 13:42 -0400
Re: error upgrading packages on current / pkg database David Holland <dholland-current@netbsd.org> - 2022-04-15 20:29 +0000
csiph-web