FS#30707 - [wordpress] package in community-staging is older than the one in community repo
Attached to Project:
Community Packages
Opened by Eric Belanger (Snowman) - Monday, 16 July 2012, 16:29 GMT
Last edited by Alexander F. Rødseth (xyproto) - Thursday, 19 July 2012, 18:56 GMT
Opened by Eric Belanger (Snowman) - Monday, 16 July 2012, 16:29 GMT
Last edited by Alexander F. Rødseth (xyproto) - Thursday, 19 July 2012, 18:56 GMT
|
Details
Description:
$ pacman -Ss wordpress community-staging/wordpress 3.3.2-2 Blog tool and publishing platform community/wordpress 3.4.1-1 Blog tool and publishing platform Package in community is newer than the one in community-staging. The package in community-staging should be updated or removed if it's no longer necessary. |
This task depends upon
Closed by Alexander F. Rødseth (xyproto)
Thursday, 19 July 2012, 18:56 GMT
Reason for closing: Fixed
Thursday, 19 July 2012, 18:56 GMT
Reason for closing: Fixed
Comment by Eric Belanger (Snowman) -
Tuesday, 17 July 2012, 07:07 GMT
Comment by
Alexander F. Rødseth (xyproto) -
Thursday, 19 July 2012, 18:56 GMT
I noticed that you pushed packages for gummi and mtpaint in
community-staging repo. Just to be clear: if the packages have no
need to be in community-staging, i.e. not part of a rebuild of
some kind, then they should be removed instead of being updated.
As there is no big rebuild going on (these packages are basically
the only ones in the staging repos), I'm a bit surprised to see
these packages in community-staging with only a changed pkgrel.
The packages had new versions during the boost rebuild (it's rare
that there are so many new versions of applications during a
TODO), I now know what to do next time. Removed wordpress from
community-staging. Thanks.