|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
help to understand snapshot
Hi all,
maybe this question is very stupid but... I'm trying to learn OpenBSD and I can't understand snapshot. Yesterday I've installed the snapshot for my architecture without problem but I've failed to install some package (vim, mutt…) because library not found, bad major. I read the openbsd.org/faq/faq15 and according I make my system in sync. So I've installed the OpenBSD snapshot from the 14-Nov-2013 12:24 bsd.rd, from the 18-Nov-2013 10:01 loongson directory, then I tried to install packages from 18-Nov-2013 10:01 packages directory. Result: I can't install packages because bad major. Where is my mistake? Many thank's |
|
|||
Quote:
Quote:
There have been changes made to core libraries in the last few days which means that the libraries' versions have been incremented (bumped) to formally indicate their changed behaviour. The packages made available to snapshots will usually lag behind the base system because it can take days to build (even when only a subset are built...) packages as opposed to hours for the base system. The problem you have experienced is that the core libraries expected by the packages you attempted to install required a different version than what was actually found. Snapshots users are expected to understand that this situation requires either:
Last edited by ocicat; 20th November 2013 at 12:15 AM. Reason: add reference to -stable. oops. |
|
||||
Question: Given, as you explained, that the snapshot is using newer libraries than those expected by the packages, did you mean to say:
[*] using a less recent (older) snapshot ? (Or, alternatively, waiting for the packages to update to the new libraries, or building ones own packages as you mentioned). |
|
|||
Quote:
Quote:
Thanks for the question. Last edited by ocicat; 19th November 2013 at 09:56 PM. Reason: correct verb tense |
|
|||
Quote:
Mimicking their intended target is a much safer bet. |
|
|||
@LeFrettchen:
>Hi fstef, and welcome. Thank you… >You should first edit your dmesg here, and tell us your architecure (i386 or amd64, I >guess, but...). Right now I've installed 5.4-release again so I don't have the output of the snapshot dmesg. I run OpenBSD on a Yeeloong machine. >Well, since you're a beginner with OpenBSD, I should highly recommend you to learn >from a stable release. At the first time I've installed a stable release, but I need to input chinese characters and the scim package in the mips64el release repository won't work. A member from a chinese OpenBSD forum suggest me to install snapshot. @ocicat: >It is imperative that the installed system & the ports tree be synchronized, however, >snapshots are created from the head of CVS which is where development takes place. >You may want to review Section 5.1 of the FAQ to understand the difference between >OpenBSD's flavors. What I understood about snapshot is: "Every few days, the OpenBSD team upload a release from the latest -current code to the mirror server. This an interim release called snapshot, which is identified only by the date of its release. A snapshot is simply the state of -current at a particular time."《Michael W. Lucas》 >The packages made available to snapshots will usually lag behind the base system >because it can take days to build (even when only a subset are built...) packages as >opposed to hours for the base system. The problem you have experienced is that the >core libraries expected by the packages you attempted to install required a different >version than what was actually found. So, if I install the 2013/11/18 snapshot from a mirror and at the same time I need to install a package from the same snapshot repository I have high probability I can't due the bad major… It's correct? >Since you are new to OpenBSD, my question to you is: >Is there a specific reason why you are using snapshots? >Will using -release or -stable fulfill your needs? Using snapshots (-current) means that >there will be occasional mismatches that users will have to deal with on their own. As I wrote above, the mips64el scim package from the 5.4.-release doesn't work, at last in my yeeloong, so I tried to install snapshot. In another laptop, in a virtual box I've installed amd64 5.4-release (virtual box don't support mipsel) to try to reproduce the problem but the scim input method work like a charm. BTW: the .xinitrc is the same. I have posted this problem in the forum and following the jggimi suggestion I have reported the problem to the port maintainer. I are waiting to be answered. For my need, follow the release, add the patch is enough, for now. I like OpenBSD OS, the project and the philosophy, I try to only use OpneBSD, do my "homework" but I absolutely need to input chinese characters and I need to find a solution. Thank you all for everything |
|
|||
Quote:
The -current branch is where development occurs, & there are times when changes need to take place in core libraries which will require changes be made to the packages also found at the mirror sites. There will be times when a snapshot of the base system will not be synchronized with the available packages found at the mirrors. If one encounters this problem, there are two ways to solve it:
I also have empathy for your needs of specific packages for Chinese character input. We have few on this site who have had the same requirements, so few here will be able to help with the specifics of these particular packages. What I have outlined is the reality of living at the head of CVS. These realities will not likely change, but as stated before, if the source to both the base system & available packages are in synchronization, then one should be able, in most situations, to install a snapshot of the base system followed by installing synchronized packages with minimal pain. You may find that living in the world of -current snapshots to be overly complicated. Library mismatch problems should be temporary -- being solved in the next mass build of snapshot packages, but users of -current snapshots should be able to deal with these problems if they arise again. If you do not find this an acceptable reality, there are other members of the *BSD family which can equally serve your needs. |
|
|||
@ocicat Thank you (and thank to everyone try to help me) for your explanation, now is clear.
I've a lot to learn about OpenBSD, so for now I follow the -release and try to find a solution for my problem… maybe is time to change my hardware. |
|
|||
Quote:
Using -release has the advantage of being in sync with the release packages, and using the pkg_* utilities is one of the fantastic aspects of OpenBSD in my experience. They just work. That said, building utilities manually from ports is not a brutal experience for the most part; FAQ 15.3.1-11 clearly lays out the basic set up. It's handy if you want a specific flavor or if you do choose to use snapshots. |
|
|||
@thomasw:
>Uhm, fstef, why change your loongson hardware if 5.4 -release works on it? I think I am >missing the point of doing this. >Using -release has the advantage of being in sync with the release packages, and using >the pkg_* utilities is one of the fantastic aspects of OpenBSD in my experience. They just >work. Well, the problem is: the scim package from the loongson repository packages doesn't work, at lest in my machine. I know work in other machine, in virtual box, but not in mine. I wrote an email to the package maintainer about this problem, but I think he can't reply to my, because you know : "what's wrong whit you? the code is fine"(M.W. Lucas). The funny thing is I can read the scim message tell me it is running but I the ps(1) command can't find the scim daemon run. But I can't do nothing, and if I can't to write chinese characters the machine is useless. |
|
||||
Quote:
Posting to the ports@ mailing list may permit others to assist you. See http://www.openbsd.org/mail.html |
|
|||
Can you provide more information?
Quote:
|
|
|||
@ocicat:
>The other machine was what architecture, & why was Virtual Box being used? The other machine is a MacBook Pro of a friend, so x86 architecture, and I can't install OpenBSD (my friend is not happy…) >What version & flavor of OpenBSD was used? I've installed OpenBSD 5.4-release amd64. >Can you explain this further? >x11/inputmethods/scim is a daemon that is not starting? Yes and now. This is the first thread I opened in the forum, I think is well explained: http://www.daemonforums.org/showthread.php?t=8206. >How is it to start? Does this require the pkg_scripts variable be set in rc.conf.local(8)? Yes, it require the dubs_daemon and the avahi_daemon, and I have in my rc.conf.local(8). >Did this daemon start under Virtual Box? The scim daemon in Virtual Box start and work like a charm. The configuration and setting in the yeeloong and in the Virtual Box is the same, but wen X start in an xterm I can see the scim daemon process, in the yeeloong I don't have this process. |
|
|||
Quote:
scim comments should return to the original thread. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
trying to understand command | amrogers3 | OpenBSD General | 9 | 3rd November 2011 04:38 AM |
Snapshot | majkelos | OpenBSD Installation and Upgrading | 4 | 21st October 2011 08:08 PM |
Trying to understand routing with openbsd | badguy | OpenBSD General | 7 | 18th September 2011 02:08 AM |
please help me understand wpa settings | gosha | OpenBSD General | 1 | 14th July 2009 11:37 AM |
How understand someone connect to my BOX with VNC | mfaridi | OpenBSD Security | 8 | 21st November 2008 12:24 AM |