Re: [aur-general] Problems uploading i686 packages to community?
On Sun, Mar 23, 2008 at 10:48:02PM +1000, Allan McRae wrote:
Well given it is not just me and I have not touched .tupkg since I became a TU, so I'm pretty sure it is not that. My guess is the script that deals with the AUR/communty integration either got broken by the update or has not been restarted.
There were no changes to that code. More likely your problems are coming from the update daemon still refusing to put through the update because of errors. -S Pkgbuild '/home/aur/cvs/lib/perl-xml-libxml-common/PKGBUILD' is a duplicate! Aborting due to errors
Simo Leone wrote:
On Sun, Mar 23, 2008 at 10:48:02PM +1000, Allan McRae wrote:
Well given it is not just me and I have not touched .tupkg since I became a TU, so I'm pretty sure it is not that. My guess is the script that deals with the AUR/communty integration either got broken by the update or has not been restarted.
There were no changes to that code.
More likely your problems are coming from the update daemon still refusing to put through the update because of errors.
-S
Pkgbuild '/home/aur/cvs/lib/perl-xml-libxml-common/PKGBUILD' is a duplicate! Aborting due to errors
Well, a bad guess then... It won't be the last :) I have looked at the cvs entries for perl-xml-libxml-common. It appears there once was a version 0.13-1 which was removed. Now another 0.13-1 has been uploaded. I'm guessing that caused the above error message (but could be wrong). I bumped the pkgrel and re-uploaded to see if it would fix. Can TU's see error messages from the update daemon? If not, then perhaps it would be good if error messages automatically got sent to the mailing list. Allan
Allan McRae wrote:
Simo Leone wrote:
On Sun, Mar 23, 2008 at 10:48:02PM +1000, Allan McRae wrote:
Well given it is not just me and I have not touched .tupkg since I became a TU, so I'm pretty sure it is not that. My guess is the script that deals with the AUR/communty integration either got broken by the update or has not been restarted.
There were no changes to that code.
More likely your problems are coming from the update daemon still refusing to put through the update because of errors.
-S
Pkgbuild '/home/aur/cvs/lib/perl-xml-libxml-common/PKGBUILD' is a duplicate! Aborting due to errors
Well, a bad guess then... It won't be the last :)
I have looked at the cvs entries for perl-xml-libxml-common. It appears there once was a version 0.13-1 which was removed. Now another 0.13-1 has been uploaded. I'm guessing that caused the above error message (but could be wrong). I bumped the pkgrel and re-uploaded to see if it would fix.
Can TU's see error messages from the update daemon? If not, then perhaps it would be good if error messages automatically got sent to the mailing list.
Well, it appears that didn't work. More investigation shows that the perl-xml-libxml-common and perl-libxml-common PKGBUILDs are exactly the same... I have untagged the one in folder lib/perl-libxml-common as it didn't match the pkgname. Allan
Hello,
On Mon, 24 Mar 2008 13:41:14 +1000
Allan McRae
Well, it appears that didn't work.
More investigation shows that the perl-xml-libxml-common and perl-libxml-common PKGBUILDs are exactly the same... I have untagged the one in folder lib/perl-libxml-common as it didn't match the pkgname.
Allan
So, what is the current status of perl-xml-libxml vs perl-libxml and perl-xml-libxml-common vs perl-libxml-common? I can see the correctly named versions with the correct PKGBUILDs for perl 5.10 through AUR but I cannot get them through pacman and even if I look directly to ftp.archlinux.org/community/os/x86_64 I only see the old ones. I have a couple of PKGBUILDs of my own in unsupported directly or indirectly depending on them and I wanted to update those but I can't really now. Ondrej -- S pozdravem Ondřej Kučera
Ondřej Kučera wrote:
So, what is the current status of perl-xml-libxml vs perl-libxml and perl-xml-libxml-common vs perl-libxml-common? I can see the correctly named versions with the correct PKGBUILDs for perl 5.10 through AUR but I cannot get them through pacman and even if I look directly to ftp.archlinux.org/community/os/x86_64 I only see the old ones. I have a couple of PKGBUILDs of my own in unsupported directly or indirectly depending on them and I wanted to update those but I can't really now.
They will be there soon... x86_64 has not receive all the perl updates yet. I am building some over the next few hours. Allan
Allan McRae wrote:
More investigation shows that the perl-xml-libxml-common and perl-libxml-common PKGBUILDs are exactly the same... I have untagged the one in folder lib/perl-libxml-common as it didn't match the pkgname.
Damned, this is getting confusing. I asked Sergej to rename perl-libxml and perl-libxml-common to perl-xml-libxml-common. I quote myself here:
Since we are rebuilding our perl pkgs anyway, I thought we might as well standardize the names of those few which are still not standard. (The naming convention is this: if a CPAN distribution is obtained from the tarball Foo-Bar-0.1.2.tar.gz then our package should be named perl-foo-bar.)
Sergej, could you please rename those two packages you have inherited from xterminus?
perl-io-gzip -> perlio-gzip (no pkgs in community depend on it AFAICS)
perl-libxml and perl-libxml-common -> perl-xml-libxml and perl-xml-libxml-common (perl-xml-atom and perl-xml-libxslt depend on perl-libxml, so be sure to change the depends array for the former, and I'll take care of the latter. You should also inform the maintainers of the packages xmltv and shownews, which also depend on perl-libxml).
But I got no reply. Come on guys, we need some more synchronisation on these things!!! OK, I've untagged perl-libxml and perl-libxml-common and I added the necessary provides, conflicts and replaces fields in the PKGBUILD of perl--xml-libxml and perl-xml-libxml-common. I'll also rename perl-io-gzip to perlio-gzip. F
participants (4)
-
Allan McRae
-
Firmicus
-
Ondřej Kučera
-
Simo Leone