[aur-general] Package Removal discid
Hi There appears to be a copy of discid in both the AUR [1]<http://aur.archlinux.org/packages.php?ID=3110>and community repo. Thanks, Ronnie [1] discid from AUR http://aur.archlinux.org/packages.php?ID=3110
Ronnie Collinson schrieb:
Hi There appears to be a copy of discid in both the AUR [1]<http://aur.archlinux.org/packages.php?ID=3110>and community repo.
Thanks, Ronnie
[1] discid from AUR http://aur.archlinux.org/packages.php?ID=3110
Ronnie, all community packages also appear in AUR. This may change, but now its is true. Regards Stefan
On Mon, May 25, 2009 at 4:38 PM, Stefan Husmann <stefan-husmann@t-online.de>wrote:
Ronnie Collinson schrieb:
Hi There appears to be a copy of discid in both the AUR [1]<http://aur.archlinux.org/packages.php?ID=3110>and community repo.
Thanks, Ronnie
[1] discid from AUR http://aur.archlinux.org/packages.php?ID=3110
Ronnie, all community packages also appear in AUR. This may change, but now its is true.
Regards Stefan
I was unware of this sorry, seems strange that this package returns two results on yaourt discid, where over community packages dont appears to
Am Mon, 25 May 2009 17:02:49 +1200 schrieb Ronnie Collinson <notthinking@gmail.com>:
On Mon, May 25, 2009 at 4:38 PM, Stefan Husmann <stefan-husmann@t-online.de>wrote:
Ronnie, all community packages also appear in AUR. This may change, but now its is true.
I was unware of this sorry, seems strange that this package returns two results on yaourt discid, where over community packages dont appears to
This is a known bug in yaourt. See the comments there: http://aur.archlinux.org/packages.php?ID=5863 I hope, that wain, the maintainer and developer of yaourt, will fix yaourt soon, because there are some more major bugs in this script. Some of them are also security issues. In the comments he unfortunately hasn't answered anymore for over a year. At least for now, it is necessary to have community packages also in AUR, because there's no package database for community as it is for core, extra and testing. At least I don't know such a package database. So AUR is the only possible place, where to flag a community package as out-of-date, where to file bug reports for a community package or where to contact the package maintainer for other purposes regarding such a package. Heiko
2009/5/25 Heiko Baums <lists@baums-on-web.de>:
At least for now, it is necessary to have community packages also in AUR, because there's no package database for community as it is for core, extra and testing. At least I don't know such a package database.
community.db.tar.gz on the mirrors is downloaded every time you do a pacman -Sy.
So AUR is the only possible place, where to flag a community package as out-of-date, where to file bug reports for a community package or where to contact the package maintainer for other purposes regarding such a package.
Bugs for [community] packages should be reported in the Community Packages section of the Arch Linux bugtracker and *not* in comments. -- Abhishek
Am Mon, 25 May 2009 17:37:38 +0530 schrieb Abhishek Dasgupta <abhidg@gmail.com>:
2009/5/25 Heiko Baums <lists@baums-on-web.de>:
At least for now, it is necessary to have community packages also in AUR, because there's no package database for community as it is for core, extra and testing. At least I don't know such a package database.
community.db.tar.gz on the mirrors is downloaded every time you do a pacman -Sy.
I know this, but this the repo, not the database. The database I mean, is this one: http://www.archlinux.org/packages/ And such a database doesn't exist for community. So AUR is the only way to find infos about community packages, to contact a maintainer, and to flag a package out-of-date.
So AUR is the only possible place, where to flag a community package as out-of-date, where to file bug reports for a community package or where to contact the package maintainer for other purposes regarding such a package.
Bugs for [community] packages should be reported in the Community Packages section of the Arch Linux bugtracker and *not* in comments.
When adding a new task to Flyspray, I only see these repos in the "Category" field: Packages: Extra Packages: Core Packages: Testing But there's no Packages: Community So the only way for filing bug reports for community packages is AUR. Heiko
2009/5/26 Heiko Baums <lists@baums-on-web.de>:
When adding a new task to Flyspray, I only see these repos in the "Category" field: Packages: Extra Packages: Core Packages: Testing
Bugs for [community] packages are reported in a separate project called "Community Packages". http://bugs.archlinux.org/index.php?project=5 -- Abhishek
Am Tue, 26 May 2009 15:21:39 +0530 schrieb Abhishek Dasgupta <abhidg@gmail.com>:
Bugs for [community] packages are reported in a separate project called "Community Packages". http://bugs.archlinux.org/index.php?project=5
Well, didn't know that yet. Thanks for the info. Heiko
participants (4)
-
Abhishek Dasgupta
-
Heiko Baums
-
Ronnie Collinson
-
Stefan Husmann