Out-of-date packages

Today I submited 2 packages to AUR and they are marked as out-of-date. Also I cannot remove outdated flag from them. Does it means that owner of package cannot change this flag?
Packages: autostart, quadkonsole

Hhmm, you're right they not. Something wrong with my eyes or firefox Thanks anyway.

Similar Messages

Howto submit package (i repaired an out-of-date package)

I read the stuff on AUR on the wiki but it is not at all clear to me how I should submit a package. I repaired an out-of date package and it seems to be working now. I would like to give back to the community by submitting the package.

You can only submit new versions for packages for which you are the maintainer/contributor.
- In case the package is an orphan (no one owns it) then you should adopt the package and become the new maintainer.
If the package is owned by another user, mail them your new pkgbuild.
If they haven't responded after a few weeks, you can use the tur-users maling list to ask AUR Trusted Users to orphan the package so you can become the new maintainer.
- Many people post new pkgbuilds in the comments, but giving the maintainer a chance to update the package is normal behaviour (or should be).
Note : Your forum account doesn't work on AUR, you need a separate account for that (most people use the same username in forum and AUR).

[Solved] Out-Of-Date Packages In Official Repos

Hello all,
Not really a question, but a general inquiry regarding the whole out-of-date process.
Suppose I encounter an out-of-date package, which is already marked as such, and has been for quite some time (can't really put a number on it), with nothing going on on testing.
In addition, the package maintainer is around, as can be deduced from the fact that other packages he is maintaining has been updated recently.
Is there anything more that can be done to check the "status" of such out-of-date package?
As an example (really, just an example), the qemu package has been marked out-of-date for about 2 weeks, while other packages maintained by the same maintainer have been updated in the last week or so.
Thanks, Adam.
Last edited by adam777 (2012-12-18 06:20:29)

First of all, it was obviously not a complaint, just an honest question.
Anyway, I got what I need, thank you both.
Adam.

[SOLVED] Adopting an out-of-date package

Two questions:
1) It's been a year since any updates were done on the package I needed to install today, and I mistakenly assumed that because it had been flagged out-of-date I'd be able to adopt it after I cleaned things up and rebuilt it. I just sent the current owner a message asking him to disown the package so I could adopt it, but I was curious what the SOP for taking over out-of-date packages that haven't been disowned (they might not respond, and it'd be relevant to know what further steps I need to take regardless).
2) I remember reading somewhere that it took 10 or 20 votes to get a package from the AUR to community, but the package I was working with had well over that. What exactly is the current procedure that allows a package to graduate from the AUR to community?
Cheers,
~Vry
Last edited by Vryali (2011-11-04 19:22:40)

Vryali wrote:I didn't want to be potentially affrontory toward the current listed maintainer, who has only had a day at this point to get back to me (nor does it seem the specific package has any actual relevance since the questions were mainly procedural).
That's what I thought :-) I too wanted to ask you which package exactly you had in mind, but as the rules apply to all of them, I think it's not strictly necessary.
Talking about some loosely-defined hypothetical situation makes me uneasy because there may be some gotchas or special cases involved, so it's best to be as specific as possible (but you probably know that).

[SOLVED] Out of Date Packages

Recently a package that I use a lot had a new stable release (Octave, just released 3.2.4) so I flagged 3.2.3-3 as out of date. It never got updated. This morning I checked back and it's not flagged as out of date anymore.
What's going on? Should this happen?
Last edited by eggplantbren (2010-03-01 22:35:01)

eggplantbren wrote:Recently a package that I use a lot had a new stable release (Octave, just released 3.2.4) so I flagged 3.2.3-3 as out of date. It never got updated. This morning I checked back and it's not flagged as out of date anymore.
What's going on? Should this happen?
somebody messed up that flag and reset it to default on website update .Mark it again.
Last edited by wonder (2010-03-01 22:16:21)

Out of date packages, how long?

Hello all. I've a question about flagging the packages out-of-date. I can mark a package out-of-date, but what happenes if the package is not updated for 2 months or more? May be after some period of time maintainer should be changed?
(now it's all about eclipse).

I just wanted to know if there is any deadline to drop the package from this maintainer?
I am sure there is. I would still recommend emailing the maintainer. If you get no reply, or one stating he is not going to maintain anymore, make a post to the arch-dev-public mailing list to let them know and request a new maintainer.
Most of the devs do not participate in the forums so the mail list is the best way to reach them.
Bob

Out-of-date package not been updated in almost a year

The question I have is: what should I do when I see a package that has not been updated in almost a year (after its flag-out-of-date)? I can't seem to find any info on how such a situation is handled. I can't reflag and sending an email to the maintainer seems intrusive and/or rude. There may be an underlying reason to not upgrade, or the flag was lost in time and forgotten.
The package I have in mind is opencl-headers. It got stuck on v1.1, and never updated to v1.2, and now still not to v2.0. There is an AUR package for the 1.2 headers, but that just seems silly to have around.
Thanks for any input!

I see, there is a backstory to all this. It seems though momentum was lost when ocl-icd devs did not respond to the email requesting info. The last commit to their repo was for 2.0 support, back in 2013. It seems abandoned since then, maybe a new spark of activity will come when a new OpenCL spec comes out.
The current situation is quite terrible really: libcl in the repos is from the NVIDIA package, so this means a hard dependency on a vendor not willing to follow the latest version of the spec. Way back when it was probably a sane choice, but now, as the email linnked by Allan shows, the situation is different.
Either choice, be it ocl-icd or Khronos, will improve the situation (OpenCL version and license-wise). Currently ocl-icd has one advantage (detailed in the POCL developer docs): choosing the icd at runtime.
As any CUDA or AMDAPP or Intel OpenCL package will include their libOpenCL, and it can be selected by LD_LIBRARY_PATH if required, I hope a sane libOpenCL package will soon make it into the repo.
As for backward compatibility: I believe the headers are backwards compatible, and it is up to the applications to verify the device they want to use supports the functionality they use. As for forward compatibility: if one solution fails and an alternative is better: just replace the package providing the ICD library by a better one.
Note that both the OpenCL headers and the ICD (libOpenCL) are designed to be platform-agnostic and should in principle work with all versions of the spec and devices, limited only by the device capabilities as reported through OpenCL functions. Currently, libcl and the old opencl-headers version is the limiting factor, which is Terrible®, given the (open source) alternatives.

How do I update out of date package which is not mine?

I want to update this package:
http://aur.archlinux.org/packages/pdfedit
Do I need to keep the previous contributer?
Do I need to replace him by me?
Do I not need to touch this at all since I do only a little changes?
And what if it become big changes?
Last edited by nadavvin (2007-03-15 22:01:15)

Contact the maintainer about it. If he doesn't respond, you can ask a TU to orphan the package so you can take control.
EDIT: Or just change the package locally. Use a pkgrel of "local", so you don't confict with the version in the AUR if it's updated.
Last edited by skymt (2007-03-15 23:09:01)

"out of date" or Orphan package; how to help ?

Hi,
I have found several packages in AUR marked as "out of date" or Orphan. I would like to help to update them, or take them as a maintainer.
However, I am not a Trusted User currently so I can't do this.
Is there any way that I could better help on this, aside from leaving a comment to the package ?

To be more precise, Unsupported orphans can be adopted by anyone. Community orphans can only be adopted by TUs.
Out-of-date packages in Unsupported should be flagged for the maintainer's attention. If an Unsupported package is significantly out of date, you can ask for it to be orphaned by contacting the aur-general mailing list.

Banshee package sorely out-of-date

I'm not sure where to go with this, but the Banshee package in the Extra repository has become sorely out-of-date. The current repo package is 0.10.10, while the current version available is 0.11.0 (and the latest from the 0.10 series was 0.10.12).
The package has already been flagged as out-of-date, but it's been quite some time and I don't think it's gotten any attention.
Does anybody have some info on my favorite music program?

Well for some reason I fixed the preferences crashing error by installing banshee-official-plugins-0.11.0.
It worked for me ymmv.
banshee-official-plugins-0.11.0
# Contributor: clarence
pkgname=banshee-official-plugins
pkgver=0.11.0
pkgrel=1
pkgdesc="Official External Plugins for the Banshee Music Player."
url="http://banshee-project.org/Plugins"
license=""
depends=('banshee')
makedepends=('')
conflicts=('banshee-official-plugins-cvs')
provides=('banshee-official-plugins')
source=(http://www.banshee-project.org/files/banshee-official-plugins/$pkgname-$pkgver.tar.gz)
md5sums=(ea4dfcb78bf04cde3dbd32af999982ba)
build() {
export MONO_SHARED_DIR=${startdir}/src/.wabi
mkdir -p "${MONO_SHARED_DIR}"
cd $startdir/src/$pkgname-$pkgver
LD_PRELOAD="" ./configure --prefix=/opt/gnome
make || return 1
make DESTDIR=$startdir/pkg/ install
rm -rf "${MONO_SHARED_DIR}"
I don't own an ipod so I can't say if it affects that at all.

Packages out of date?

Seems I always have silly questions ( I hope they don't annoy to many people ).
When a package is updated because a newer stable version is released, and other packages have the updated package as a dependency, should the other packages be flagged as out of date because they are not built against the new packages. (can i say packages any more times?)
Example:
libarchive 2.6.2-1 was just updated.
I see that gvfs 1.0.3-2 depends on this package.
Does this mean that gvfs 1.0.3-2 is now out of date and be flagged as such?
Thanks for your time

If you care to dive a bit into it, subscribe to the arch-dev mailing list. The system they use for upgrades and publishing packages is all very public.

Aura Vs Yaourt different number of out-of-date AUR packages

After seeing the release announcement for Aura 1.2.0 I figured I would try it out and see what I thought of it. There are a lot of differences between the two usability wise, one of the biggest that will take some getting use to separation of Pacman repos and AUR which makes sense. One thing that I am worried about is that Yaourt and Aura gives different number of AUR packages that are out of date.
Yaourt says aur/foomatic-db-foo2zjs is out-of-date, but Aura states "No AUR package upgrades necessary." Does Aura track AUR packages differently than Yaourt or is this due to something else?

Such nonsense.... all packages should be installed/removed by pacman, regardless of the helper. Any helper that doesn't use pacman correctly should be ashamed of itself.
I recommend you bin both of them and use cower.

Out-of-date flagging not visible in package list?

In the old website design packages flagged as out-of-date were marked by a different color in the package list. This is not so anymore. How come? It was very useful.

http://bugs.archlinux.org/task/19652

Can we have a Family Data Package, Please?

I have 4 people on our wireless service with Verizon. Until recently, only I had a data plan. Then I got my kids new phones and they got data plans. Now my husband wants a data plan when he is eligible for a new phone in January. All these plans are getting REALLY expensive. How about coming out with a family data share plan, similar to the shared minutes plan?
Thank you!

TheGreatOne wrote:
spottedcatfish wrote:
They didn't feel like coercing people to add texting packages was an appropriate move, so instead they adjusted the price point. We should all feel deeply blessed that instead of requiring a texting package as well as a data package on most high quality phones, they just made it so affordable that I'm sure most people grab it by default. Fortunately for Verzion, the profit margins on texting is even higher than on data, because even if you use it a ton, it still costs them next to nothing to provide to you.
Even if Verizon has required messaging packages instead of data packages,you would still get people complaining most likely. Probably people then saying something like "oh i don't use messaging on my phone ever. I don't need it."
And rightly so. Nobody should be forced to buy anything they dont need or use. Is that not common sense?

SDK component Runtime.apk is out of date export captive build for Kindle Fire

Hello
Kindle fire only supports AIR 2.7 and I'm trying to export a build release in Flash Builder 4.7 with the AIR runtime included (captive build). Whenever I build I get the following error:
SDK component at air/android/device/Runtime.apk is out of date
I tried running the updater and it said I'm up to date. I did download the SDK and put it in my home folder but I can't seem to change the SDK reference in the preferences.
(I had another java out of memory error including my ANE file but I turned it off just to get a build out. Not the focus of this discussion)
It would be nice if flash builder just let me reference my freshly downloaded SDK but instead I have to sift through their document structure guessing where I should be updating the Runtime.apk that SHOULD be up to date already.
I have had to go in to the package itself and modify the ini files and over-write the adb files from the fresh download of the SDK before.
I'm guessing there is a way to update the Runtime.apk but i have so many bin executables spread all of my computer it's hard to tell what flash builder wants!!!
There is always one problem after another developing with Flash Builder ... Please help.

Just be sure you've downloaded the correct AIR 3.6 SDK specific to Flash Builder! On this page: http://www.adobe.com/devnet/air/air-sdk-download.html in small print is this note:
Note : Flex users will need to download the original AIR SDK without the new compiler. Mac Windows.
Be sure to install the appropriate sdk if you're using Flex in your mobile project. Otherwise the main download will work with ActionScript only projects in Flash Builder 4.7
Can you confirm you installed the correct SDK? Also with ANEs, it's important to identify what version of AIR the ANE supports.
If you still run into trouble with your current configuration, try building a new mobile project and export release build with captive runtime and see if it compiles correctly. If it does, then it's going to be a problem with your current project, and I'd look at how the ANE is packaged. See if there's documentation on how to include the ANE, etc. If you still can't compile a blank mobile project, then your AIR installation is incorrect.
iBrent

Out-of-date packages

Similar Messages

Maybe you are looking for