LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Yoper (https://www.linuxquestions.org/questions/yoper-57/)
-   -   Dead/empty repositories? (https://www.linuxquestions.org/questions/yoper-57/dead-empty-repositories-339149/)

aysiu 07-01-2005 02:43 PM

Dead/empty repositories?
 
Maybe I'm installing an older version of Yoper (I think I just downloaded it only a few months ago), but I installed it yesterday, and I was impressed with the speed with which it ran--yet, I couldn't get any repositories to work. It came with only two repositories, and they didn't work. I tried searching around for other repositories. I even tried using Debian repositories (but Yoper doesn't recognize debs, only rpms).

Anyone know if there are updated Yoper repositories?

kernowyon 07-03-2005 09:20 AM

Which version of Yoper have you got there?
The details for the correct repository are different for the different versions of Yoper - 2.1 or the 2.2 pre-release version.
For 2.1 try this -

Open /etc/apt/sources.list as root in a text editor.
Replace the servers in there with -
rpm http://mirrors.csumb.edu/yoper/yoper version2 os
rpm http://mirrors.csumb.edu/yoper/yoper contrib os
rpm http://mirrors.csumb.edu/yoper/yoper rocketfuel os
#rpm-src http://mirrors.csumb.edu/yoper/yoper version2 os
#rpm-src http://mirrors.csumb.edu/yoper/yoper contrib os

Then as root in a terminal, type
apt-get update
<press return>
apt-get install apt
<return again>


For 2.2 pre-release, you need the 2 entries already there hashing out and a new entry adding - like this -

#rpm http://192.168.0.30/yoper/version2 updates updates
#rpm http://192.168.0.30/yoper/version2 cvs cvs
rpm ftp://apt.yoper.com/yoper testing testing

For 2.2 pre, only the testing repository will work - the others (i.e the 2.1 repository info) will possibly damage your Yoper install.
Hope this helps :)

aysiu 07-03-2005 11:38 AM

I've got 2.1
Thanks for the info. When I try to install Yoper again, I'll give those a go.
Interestingly enough, where did you get these repositories from? I looked at the Yoper website and couldn't find an up-to-date list...

aysiu 07-04-2005 05:15 PM

I tried out those sources, and they didn't have the most up-to-date packages in there. For example, no Firefox 1.0.4. Thanks for the list, though. I'm sure other potential Yoper users will find it handy.

kernowyon 07-05-2005 06:28 AM

The repositories for 2.1 and the 2.2 pre-release are currently not being upgraded regularly. This is because the team are working on the official 2.2 release and trying to get that out for end of August/beginning of September.
Hopefully, once that is done, the packages can be updated. Some updated packages are on users own webspaces - in the forum, under the contrib area, you can see a few which have been done. A nose round the forum may well discover others :)
Firefox I always install from the Mozilla download anyway - that way you can be sure of the very latest version.
It is a bit frustrating that some of the packages are outdated - but we are a very small team and have to use what resources we have to best effect - and that means 2.2 being released. But yep - its rather frustrating when the older releases get left behind for a time :(
Apologies for that.
Mark

agentdunken 07-13-2005 01:00 PM

Indeed. When I was using yoper 2.1 I always was pissed that their app-get was always outdated then also they don't have that many apps in them. Be nice if they would get them updated and always add more apps to them.

ZakuSage 07-17-2005 10:21 PM

So once Yoper 2.2 comes out the repository packages will be reletively up to date and include some more packages? If so, is there a way I could get an email when it comes out (like a mailing list)? I loved Yoper when I tried it not too long ago for it's speed and SaX2 usage... that is until I used apt.

kernowyon 07-18-2005 03:27 AM

Well, once 2.2 is released, there will be more time to get apps into the repositories - so I would expect to see a real move towards getting things up to date and filling the repository.
I shall take the feedback on this to the Yoper team meeting in a couple of weeks. Its things like rpms being available which makes yoper easier for the new user - and also for those with more experience, but less time to build the source packages.
Its something we are aware of as a shortcoming in Yoper currently - and I shall make every effort to try to get as many things in the repository as possible. We are testing out a new method of getting our rpms into the system which should help on this matter.
ZakuSage - Are you not a Yoper Apt fan then?
Personally, I find the Apt in Yoper to be far more user friendly that in Ubuntu - although of course, the Ubuntu repositories have many times the apps we have at Yoper. The issue which many people raised about lack of info in packages lists should be sorted for 2.2 - several of us rewrote the spec files to include much more info - so there should be no "a binary package" type stuff :)
As far as I am aware, there isn't currently a mailing list for those who want info on a release, but I expect the release of 2.2 will be fairly well publicised.
Mark

ZakuSage 07-18-2005 04:33 AM

Well when I used Yoper's apt the first time, the sources.list included by default didn't work. I had to find info on a command that got the nearest source for it which of course was extremely and cripplingly slow (something like 20 kb/s if I was lucky, when I was used to 300ish on average). So I then had to scour around for a faster sources.list file, and I did find one, but it was still relatively slow, averaging around 120 kb/s. Then I tried to install a few things, and at least half weren't there at all, and most were cripplingly old versions, like FireFox 0.94.

Maybe I'm just spoiled from using a number of Debian based distros and having no experience with apt4rpm didn't help, but I was expecting more. I really hate having to download individual packages, and when dependencies are involved it's like murder especially when things have a lot of dependencies.

I look forward to Yoper's next release though, if apt in it becomes a little less nauseating.

kernowyon 07-18-2005 05:13 AM

Yeah - the repository info included in 2.2 simply didn't work. That was down to an error - the original local IP address of the build machine used was left in! However, 2.2 pre-release was exactly that - designed really for those of us who were bug testing it. The problem would have been sorted if another version was built - but yep, it was frustrating to see a fairly major ( if easy to sort) issue slip through.
The 2.1 repositories were correct originally, but there were some changes to the server and things got located elsewhere. I am not attempting to justify the problems - they should never have happened - but they did.
I wouldn't notice the slow downloads you experienced - my connection is very poor anyway here :(
We are hoping to have a few extra mirrors with 2.2 - a few volunteers have come forward to host mirrors, so hopefully things will be a little better. But if you still get issues once 2.2 is out - let me know.
Being a small distro, we don't have the access to the same number of packages that some other distros have - such as Ubuntu or Vector for instance. If their repositories dont have the package you need - you can simply head over to Debian or Slack and grab them from there. Although you can sometimes use rpms from other distros - such as Suse or Fedora- on yoper, there is no guarantee they will work. This has been discussed by the team in the past, and the concensus was that we prefer to have rpms built specifically for yoper - i.e with the optimisation flags etc we use, rather than making the Yoper system more cross purpose. The general thought was that if an inexperienced user attempts to install an rpm for Fedora say, and it doesn't work - or worse - then it ends up on our plates with a person blaming us because appX caused untold misery.
I will, as I mentioned before, take the comments to the team though - its good to get constructive comments to help us improve things.
Mark


All times are GMT -5. The time now is 02:41 AM.