[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).

Similar Messages

[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.

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

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)

[solved] Pepper flash out of date?

Just reinstalled the system (64bit), downloaded the latest chrome and extracted pepper flash to chromium. It always worked flawlessly but this time it's saying that the plugin is outdated and can't be used. This is just an annoyance since we can set whatever version we want in /etc/chromium/default but I was just wondering why it is happening and if others have experienced such behavior.
Last edited by Matt3o (2013-01-24 10:12:22)

I've done exactly what the AUR package does, but manually.
- download latest 64bit chrome from google website
- extract pepper flash
- copy files to proper directory
- modify /etc/chromium/default
in fact AUR package gives me the same out of date error
Edit: my workaround is to add some units to the --ppapi-flash-version paramenter in the /etc/chromium/default
Last edited by Matt3o (2012-12-03 14:33:24)

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 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.

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.

[SOLVED]tint2-svn out-of-date

Not compiling and build is flagged as out-of-date. No contact info of the maintainer. What to do now?
Last edited by Paingiver (2015-03-07 23:11:52)

https://wiki.archlinux.org/index.php/Ar … do_I_do.3F
It builds fine without all those patches. Having static patches to VCS code is a bad idea from the outset.

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.

[SOLVED] open-vm-tools-modules out of date

open-vm-tools-modules has been flagged out-of-date today because it requires < 3.3 kernel.
This is stopping me from updating to 3.3-ARCH.
Can anyone advise what it would take to update this? If it's complicated, how long would it normally be before it is updated by the maintainer?
Thanks in advance.
--Ja'far
Last edited by jr0 (2012-04-08 21:53:51)

The NEWS file in ~/abs/open-vm-tools-modules/.../src/ said
Targets (1): open-vm-tools-modules-2012.03.13-1
open-vm-tools 2012.03.13 changes:
* Updates for newer Linux kernel releases (3.3).
so I thought it was worth risking removing the requires <3.3 from PKGBUILD, like so (I didn't mean to comment the second "depends=" line):
package() {
_kernver=`pacman -Q linux | cut -d . -f 2 | cut -f 1 -d -`
# depends=("linux>=3.${_kernver}" "linux<3.`expr ${_kernver} + 1`")
# depends=("linux>=3.${_kernver}")
KERNEL_VERSION=`cat /lib/modules/extramodules-3.${_kernver}-ARCH/version`
msg "Kernel = $KERNEL_VERSION"
Seems to be working, so marking SOLVED.

My MacKeeper says iPhoto is out of date. When I try to update the App Store says I need IOS 10.9 or later. I have 10.7.5 and when I check for updates my Mac says the software is up to date. How do I solve this problem??

My MacKeeper says iPhoto is out of date. When I try to update it, the App Store says I need IOS 10.9 or later. I have 10.7.5 and when I check for updates my Mac says the OS software is up to date. How do I solve this problem??

1. First step to solving the Problem: Trash MacKeeper. It's a pile of trash that does far more harm to your computer than good.
https://discussions.apple.com/docs/DOC-3691
2. What version of iPhoto do you have? (iPhoto Menu -> About iPhoto)

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.

WARNING! Your Flash Player may be out of date. how can i solve this problem/

WARNING! Your Flash Player may be out of date. how can i solve this problem/

The Flash update alerts are fake, and are intended to mislead you into installing malware and/or to steal your identity. They're the result of an attack on your router that has caused you to get false results from looking up the addresses of Internet servers. Requests sent to well-known websites such as Google and YouTube are redirected to a server controlled by the attacker.
The router's documentation should tell you how to reset it to the factory default state. Usually there's a pinhole switch somewhere in the back. It may be labeled "RESET." Insert a paper clip and press the button inside for perhaps 15 seconds, or as long as the instructions specify.
Then go through the initial setup procedure. I can't be specific, because it's different for every model. The key points are these:
1. Don't allow the router to be administered from the WAN (Internet) port, if it has that option.
2. Set a strong password to protect the router's settings: at least ten random upper- and lower-case letters and digits.Don't use the default password or any other that could be guessed.
3. If the router is wireless, or if you have a wireless access point on the network, use "WPA 2 Personal" security and set another strong password to protect the network. If the router or access point doesn't support WPA 2, it's obsolete and must be replaced.
During the time the router was compromised, you were redirected to bogus websites. If you ever connected to a secure site and got a warning from your browser that the identity of the server could not be verified, and you dismissed that warning in order to log in, assume that your credentials for the site have been stolen and that the attacker has control of the account. This warning also applies to all websites on which you saw the fake update alerts.

[SOLVED] Adopting an out-of-date package

Similar Messages

Maybe you are looking for