xorg-redhat-die-ugly-pattern-die-die-die.patch is missing in the package. Please use makepkg --source to generate the tarball you upload.
Search Criteria
Package Base Details: xorg-server-git
| Git Clone URL: | https://aur.archlinux.org/xorg-server-git.git (read-only, click to copy) |
|---|---|
| Keywords: | git x-server xorg xorg-server |
| Submitter: | ilikenwf |
| Maintainer: | JstKddng (yurikoles) |
| Last Packager: | yurikoles |
| Votes: | 49 |
| Popularity: | 0.088718 |
| First Submitted: | 2008-08-07 19:05 (UTC) |
| Last Updated: | 2022-07-21 09:15 (UTC) |
bluewind commented on 2010-09-24 23:48 (UTC)
Det commented on 2010-09-03 18:59 (UTC)
Ok, thanks for your efforts with both. I updated glib2-newest and fixed this one.
E: Same happened again, Glib2 2.25.15 was released a coupple of days ago.. though it's gonna hit [extra] soon, which might make glib2-newest unnecessary. Anyway, you just need to change the pkgver from x.14 to x.15 - I'm just saying you don't need me to do that.
<deleted-account> commented on 2010-09-02 20:03 (UTC)
@Det: Do what you have to do :)
Same iwht glib2-newest Thanks!
Det commented on 2010-08-29 10:55 (UTC)
Dunno how can you not be able to extract my tarball.. probably a really weird archiving tool you got there - how about just 'tar xvfz xorg-server-git.tar.gz'?
About gitorious/github, I'm not exactly sure what you mean by that. That we'd do changes _there_ and the other one, whoever is the maintainer, would just update the package(s) in the end? Wouldn't that be rather unnecessary thing to do, when 1) the changes would first be posted to gitorious and _then_ here - is the log keeping so important? 2) If the xorg-server git tree changed and the package would need to be updated in order to compile and the maintainer one wouldn't be able to update the package for whatever reason (and didn't know that was gonna happen and thus didn't disown the package) then what(?) - the other person would either need to wait for the maintaining person to update the package or tell a TU in the forums/IRC/mailing list to disown the package so that he could update it himself.
I wouldn't really like to be doing that :S.
<deleted-account> commented on 2010-08-28 10:05 (UTC)
Still the same situation.
Det maybe we can collaborate on them using git I got repo on giorious for this.
Det commented on 2010-08-26 11:50 (UTC)
Nope, you probably just had "xorg-server-git.tar.gz" on your desktop already causing my tarball to be renamed to "xorg-server-git.tar(1).gz" or something like that. When you tried extracting _this_ tarball it resulted in a .tar file with name something like "xorg-server-git (1)" that would of course then need to be renamed to "X.tar" to have it extracted completely.
But you need not to just stop "associating" with this thing and "glib2-newest" when you can just orphan both packages and then we both do changes to each one of them when we think such changes should be done.
E.g. If you are busy enough to not update either of these packages - I can do it for you by adopting -> updating -> disowning.
I used to do that for like 6 months when I started out as a 'package maintainer' (or whatever) but in the whole 6 months period only _1_ person actually updated one of my packages when it was out of date - and just that single time. But maybe 'we' will do better than that.
Pinned Comments
yurikoles commented on 2022-03-18 01:04 (UTC)
check()function was added, if unit tests fail, you may ignore them by appending--nochecktomakepkg.yurikoles commented on 2019-05-29 15:00 (UTC)
PRs are welcome: https://github.com/yurikoles-aur/xorg-server-git