You are not logged in.
Pages: 1
I heard that one of advantages of Archlinux is up-to-date softwares. But it seems not true when I was looking for pidgin 2.5.0 in the source and aur. Because it has been one week since 2.5.0 released but only 2.4.3 available for archlinux. Does there anyone know why?
Offline
Maintainer is probably on vacation, just change the version number in the pkgbuild, worked for me.
Offline
Hardly deserves a response, but anyway....
You may have already noticed that the package is flagged out-of-date. This means that the maintainer is aware that 2.5.0 was released a whole week ago, and that he will update the package as soon as he can fit it in to the varied Arch duties that he performs in his spare time i.e. the time that is left over after work, sleep, and.. well, life in general.
If you cannot live without the 2.5.0 release, use ABS (Arch Build System) to update the package for yourself, as suggested by FALK.
Offline
How about some enabling comments on the packages page (like on AUR) so that this kind of discussions don't pollute the forums?
Offline
How about some enabling comments on the packages page (like on AUR) so that this kind of discussions don't pollute the forums?
And do you think some users will not fall in the hands of "ZOMG, package-x 2.5 has been released we have 2.4 why is Arch so outdated, it has been a week. What do they pay you for developers? Go and upgrade your packages" ???
Offline
In order to get pidgin 2.50 before the maintainer updated the pkg you need to do the following.
* Read http://wiki.archlinux.org/index.php/ABS … l_Packages and install abs.
* Copy the folder /var/abs/pidgin to /var/abs/local/pidgin
* Open the PKGBUILD and change the versionnumber.
* Open a terminal in the current dit and run <code>makepkg -g</code> to get the correct md5 sum. Replace the md5sum in the PKGBUILD with this one.
* Then from the same directory run <code>makepkg -csi</code>
Now your done and should have the desired version of pidgin.
ps. Arch is based on the community, and therefore you also have a responsibility to contribute if no one else does. Now I don't think you ment to be impolite, but it's always better to ask how you self can solve the problem, instead of asking others to do it.
Last edited by xd-0 (2008-08-25 08:53:28)
Offline
i'm getting abnormal blood pressure reading this. thread deserves nuke.
Offline
I think we should keep it cool: the OP is obviously new to Arch.
Here is some initial reading for zpxing: http://wiki.archlinux.org/index.php/Arch_Linux
Have you Syued today?
Free music for free people! | Earthlings
"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- A. de Saint-Exupery
Offline
* Then from the same directory run <code>makepkg -csi</code>
And Horatio will make sure you get the newest version!
The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner.
--------------------------------------------------------------------------------------------------------------
But if they tell you that I've lost my mind, maybe it's not gone just a little hard to find...
Offline
In order to get pidgin 2.50 before the maintainer updated the pkg you need to do the following.
* Read http://wiki.archlinux.org/index.php/ABS … l_Packages and install abs.
* Copy the folder /var/abs/pidgin to /var/abs/local/pidgin
* Open the PKGBUILD and change the versionnumber.
* Open a terminal in the current dit and run <code>makepkg -g</code> to get the correct md5 sum. Replace the md5sum in the PKGBUILD with this one.
* Then from the same directory run <code>makepkg -csi</code>Now your done and should have the desired version of pidgin.
ps. Arch is based on the community, and therefore you also have a responsibility to contribute if no one else does. Now I don't think you ment to be impolite, but it's always better to ask how you self can solve the problem, instead of asking others to do it.
Hello, since I like yaourt, all I did was yaourt -Sb pidgin and edited the pidgin's PKGBUILD to the new version and the new source's md5sum
pkgver=2.4.3 ~-~-> 2.5.0
...
md5sums=('9e4a5f4ebda16a51fe91ec610286810a' ~-~-> '71df6633794de30e57827848cfb61996'
Better for the lazy people, since it automates the ABS process, no?
Note: I left pkgrel=2 so that it still warns me after 2.5.0 gets on extra:
warning: pidgin: local (2.5.0-2) is newer than extra (2.5.0-1)
Last edited by VuDu (2008-08-25 09:55:58)
Offline
Ignore my comment about the patch, see shining's response below for a better solution.
I believe that certificate-location.patch needs to be updated as well, since it fails to apply to the new source tree.
This should do the trick (its md5sum is a0b52a2a9795b4af94df40d53edb618b).
Note: I left pkgrel=2 so that it still warns me after 2.5.0 gets on extra
I put pkgrel=0, so when 2.5.0 gets in extra, it'll replace my custom package. As least that's what I had in mind.
Last edited by foutrelis (2008-08-25 10:49:29)
Offline
I believe that certificate-location.patch needs to be updated as well, since it fails to apply to the new source tree.
This should do the trick (its md5sum is a0b52a2a9795b4af94df40d53edb618b).
http://developer.pidgin.im/wiki/ChangeLog
Add a configure option, --with-system-ssl-certs to allow packagers to
specify a system-wide SSL CA certificates directory. When set, we
don't install our SSL CA certs, so it's important that the libpurple
package depend on the CA certificates.
That should allow to get rid of the certificate-location.patch patch
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
I put pkgrel=0, so when 2.5.0 gets in extra, it'll replace my custom package. As least that's what I had in mind.
/me is overwhelmed
Offline
I put pkgrel=0, so when 2.5.0 gets in extra, it'll replace my custom package. As least that's what I had in mind.
Cool man!
Offline
Pidgin 2.5 is on extra repository now...
Offline
Pages: 1