Arch Linux

Lazer

Banned

Registered: 2007-08-02

Posts: 111

same package in the repository and the out-of-date package

testing:mplayer-svn 24986-1  (http://www.archlinux.org/packages/14527/
unstable:mplayer-svn 25449-1  (http://www.archlinux.org/packages/11936/
mplayer is Revision 26454 now

testing:smplayer 0.6.0rc1-1   (http://www.archlinux.org/packages/14776/
AUR:smplayer-svn r1039-1  (http://aur.archlinux.org/packages.php?ID=15280
smplayer is Revision 1124 now

extra:x264 20071202-1   http://www.archlinux.org/packages/8708/
AUR:x264-git 20080402-1  (http://aur.archlinux.org/packages.php?ID=15774
x264 is snapshot 20080415 now

Do we need two development version of the same package
And the svn/git or daily snapshot packages update quickly
When(how often) do the packages update

aRcHaTe

Member

Registered: 2006-10-24

Posts: 644

Re: same package in the repository and the out-of-date package

err...this a bit stupid...dont u think devs know the packages are outdated? if its not updated i beat they have better things to do..priority packages....if it those are neede for u..update and compile it urself

---

Its a sick world we live in....

zodmaner

Member

Registered: 2007-07-11

Posts: 653

Re: same package in the repository and the out-of-date package

It seems that the devs are currently busy with making repositories migration from CVS to SVN. So they might not have enough time to sort this out yet. Also, the migration in it self might produces these 'errors' (check the mailing list for more information).

The good news, like aRcHaTe said, is that the devs are properly aware of this. The bad news is that this will properly take sometime to sort out (judging from how things currently are with regard to the migration).

On the bright side, these and many more issues should get resolved after the migration is complete.

Hope this help clarify things up a bit.

Last edited by zodmaner (2008-04-16 10:01:47)

---

Memento mori

neotuli

Lazy Developer

From: San Francisco, CA

Registered: 2004-07-06

Posts: 1,201

Website

Re: same package in the repository and the out-of-date package

It seems that the devs are currently busy with making repositories migration from CVS to SVN. So they might not have enough time to sort this out yet. Also, the migration in it self might produces these 'errors' (check the mailing list for more information).

The good news, like aRcHaTe said, is that the devs are properly aware of this. The bad news is that this will properly take sometime to sort out (judging from how things currently are with regard to the migration).

On the bright side, these and many more issues should get resolved after the migration is complete.

Hope this help clarify things up a bit.

I'm not so sure what you're talking about. It's up and running smooth

And yeah... we see the out of date flags, we even get a little spam every time you click one of them... but we're only human.

---

The suggestion box only accepts patches.

zodmaner

Member

Registered: 2007-07-11

Posts: 653

Re: same package in the repository and the out-of-date package

I'm not so sure what you're talking about. It's up and running smooth

Wow! The migration is finish? Great job guys! The migration from CVS to SVN is a very large undertaking and it's great to see that you guys have finally made it. Congrats guys.

This is great news indeed! Thanks for informing us about this, neotuli.

And yeah... we see the out of date flags, we even get a little spam every time you click one of them... but we're only human.

Don't worry, we understand you.

Last edited by zodmaner (2008-04-16 10:54:53)

---

Memento mori

aRcHaTe

Member

Registered: 2006-10-24

Posts: 644

Re: same package in the repository and the out-of-date package

I'm not so sure what you're talking about. It's up and running smooth

Wow! The migration is finish? Great job guys! The migration from CVS to SVN is a very large undertaking and it's great to see that you guys have finally made it. Congrats guys.

This is great news indeed! Thanks for informing us about this, neotuli.

And yeah... we see the out of date flags, we even get a little spam every time you click one of them... but we're only human.

Don't worry, we understand you.

not quite..its seems community is going to take a bit longer got left behiend

---

Its a sick world we live in....

SpookyET

Member

Registered: 2008-01-27

Posts: 410

Re: same package in the repository and the out-of-date package

Why SVN instead of git or mercurial?

ora

Member

Registered: 2007-06-20

Posts: 26

Re: same package in the repository and the out-of-date package

Distributed VCS like git, every user has a complete copy of the repository data stored locally.
Space waste for project like a linux distribution.
And things like PKGBUILD are easy to merge.
So SVN just works and many people know it.

Just my opinion, arch devs may have other concerns.

Cerebral

Forum Fellow

From: Waterloo, ON, CA

Registered: 2005-04-08

Posts: 3,108

Website

Re: same package in the repository and the out-of-date package

Why SVN instead of git or mercurial?

Because that's what we decided.  If you want to go digging through arch-dev-public archives you might find some of the reasoning in there, but generally it was the one repo proposal that made most sense and was easiest to get off the ground.