pkgin upgrade command removes pkgin and can't reinstall it

171 views
Skip to first unread message

Razors Edge

unread,
Jul 1, 2021, 1:36:33 PM7/1/21
to minix3
I installed minix3 with Vitrtualbox, host Ubuntu 20.04. It took a long while but it finally became workable OS. After all installed I ran "pkgin update" with no errors. I then ran "pkgin upgrade". After this pkgin was not found if I ran an install command like "pkgin install nano" I get "pkgin not found".
I tried reinstalling it using pkg_add:  "PKG_PATH=http://minix3.org/pkgsrc/packages/3.4.0/1386/All pkg_add pkgin"
Returns
"pkg_add:  Warning: package 'pkgin-0.9.nb3' was built for a platform:"
"pkg_add: Minix/i386 3.4.0 {pkg} vs. NetBSD 3.4.0 (this host)
"pkg_add 1 package addition failed"

So I now have no pkgin and can't install packages. Any idea are greatly appreciated. I'm sorry that I couldn't enter the actual lines of code.
Brian


Brian O'Keefe

unread,
Jul 6, 2021, 12:48:13 PM7/6/21
to min...@googlegroups.com

I hope responding with an email is OK. Thanks for any help.

I get the same kind of error in the err.log as shown below. Here's a screenshot of an attempt to install xdm.

This from the err.log

--
You received this message because you are subscribed to a topic in the Google Groups "minix3" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/minix3/mEkPUUk1IH4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to minix3+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/minix3/21b63ae0-73d3-412d-9d09-5468773b3bc4n%40googlegroups.com.

Peter Shkenev

unread,
Jul 10, 2021, 5:36:05 AM7/10/21
to minix3
Hello,

I have a little experience with pkgin, so I'm afraid that you'll have to reinstall your system.

Best regards,
Peter

вторник, 6 июля 2021 г. в 19:48:13 UTC+3, knowthe...@gmail.com:

stux...@gmail.com

unread,
Jul 10, 2021, 5:48:21 AM7/10/21
to minix3
Just for the sake of some thoroughness, the URL link in the path above:

It had a typo.  Instead of "1386" it should be "i386":

That may have been the reason it wasn't working.

Reply all
Reply to author
Forward
0 new messages