Thanks for pointing this out, Pierre. I'll have a look at it. The update script needs to be generalized so that changes to 1 can be applied to both easily. I had done the i686 one thinking that whoever had originally implemented community64 would do that one.. but if nobody has done it, I will have a look. - P Pierre Schmitz wrote:

Hi,

the community.db.tar.gz file of community is still outdated resulting in a more or less broken repository. Packages are newer than the db entries.

Is there anybody who can fix this? (or tell me how to do it?)

Pierre

_______________________________________________ arch-dev-public mailing list arch-dev-public@archlinux.org http://archlinux.org/mailman/listinfo/arch-dev-public

On Mon, 11 Jun 2007, Pierre Schmitz wrote:

Am Montag, 11. Juni 2007 15:08:35 schrieb Paul Mattal:

...

Thanks for pointing this out, Pierre. I'll have a look at it. The update script needs to be generalized so that changes to 1 can be applied to both easily. I had done the i686 one thinking that whoever had originally implemented community64 would do that one.. but if nobody has done it, I will have a look.

Perhaps it might be a good idea to document this. I did not even find the scripts on gerolde. So this should be a good start. ;-)

Pierre

--

Any progress on this? It's starting to become a very serious problem. The community64 repo hasn't been updated for over 2 weeks now. All current work (updating/porting) on community64 is stalled and waiting for the fix. Several users are starting to complain with reason. If time is a problem, can you tell us, Pierre and myself, how to fix it? Thanks Eric -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

Dale Blount wrote:

On Fri, 2007-06-15 at 16:01 -0400, Eric Belanger wrote:

...

On Mon, 11 Jun 2007, Pierre Schmitz wrote:

...

...

Thanks for pointing this out, Pierre. I'll have a look at it. The update script needs to be generalized so that changes to 1 can be applied to both easily. I had done the i686 one thinking that whoever had originally implemented community64 would do that one.. but if nobody has done it, I will have a look. Perhaps it might be a good idea to document this. I did not even find the

Am Montag, 11. Juni 2007 15:08:35 schrieb Paul Mattal: scripts on gerolde. So this should be a good start. ;-)

Pierre

-- Any progress on this? It's starting to become a very serious problem. The community64 repo hasn't been updated for over 2 weeks now. All current work (updating/porting) on community64 is stalled and waiting for the fix. Several users are starting to complain with reason.

If time is a problem, can you tell us, Pierre and myself, how to fix it?

I tried, and failed. I can't see any of the changes that Paul speaks of to migrate to Arch64 also. Paul, please enlighten us.

I think this is now fixed; I merged the changes into tupkgupdate64 from tupkgupdate for now, rather than go for the clean solution. This should get things up and running. I also just rebuilt the database so it is current again. Please post again if it does not do the trick. The diffs match, aside from the 64-bit changes, so I'd be surprised if it didn't work. - P