2010/1/19 Ionut Biru :

i'm going to move them now. Packages are still in jpng directory, there is a reason for this? Also, ArchitectureDifference shows that there are still some package on [jpng] x86_64.

-- Andrea `bash` Scarpino Arch Linux Developer

On Tue, Jan 19, 2010 at 11:15 AM, Ionut Biru wrote:

On 01/19/2010 05:59 PM, Andrea Scarpino wrote:

...

2010/1/19 Ionut Biru:

...

i'm going to move them now.

Packages are still in jpng directory, there is a reason for this? Also, ArchitectureDifference shows that there are still some package on [jpng] x86_64.

in jpng x86_64 there is one package and in i686 none. i think ArchitectureDifference is broken somehow or i miss something...

-- Ionut

Now, that they are moved to testing, can we completely remove the jpng repo? The cleanup script complains about it: Scan complete for jpng (i686) at /srv/ftp/jpng/os/i686 The following files are missing in the repo /tmp/cleanup-IY1z7V/*.pkg.tar.gz Scan complete for jpng (x86_64) at /srv/ftp/jpng/os/x86_64 The following files are missing in the repo /tmp/cleanup-2xEQKi/*.pkg.tar.gz

Am Mittwoch, 27. Januar 2010 01:03:09 schrieb Allan McRae:

Sure, apart from some of the openoffice variants, there is only 5 or 6 packages left to go. I think Andy was holding out for a release to finish the OOo stuff.

I wonder how long we have to wait here. They just released RC4 and told that the final release was delayed. I guess it's a lot longer than it would take to build it for i686 (x86_64 is already done) -- Pierre Schmitz, https://users.archlinux.de/~pierre

Am Donnerstag, 28. Januar 2010 21:30:57 schrieb Andreas Radke:

I can build the remaining OOo stable packages within one day or so. No big deal. A problem might be the go-oo pkg. I don't know if the old stable pkg will be also run into the stripping issue.

You mean this: http://bugs.archlinux.org/task/17656 That's no big deal. Just adjust the library permissions to 755 or 644. I don't see any reason in having them 444 or 555 if they are owned by root anyway. -- Pierre Schmitz, https://users.archlinux.de/~pierre

On 01/27/2010 02:03 AM, Allan McRae wrote:

On 27/01/10 09:56, Pierre Schmitz wrote:

...

Am Dienstag, 19. Januar 2010 02:15:10 schrieb Ionut Biru:

...

hi, just a heads up to inform that i don't recommend to update from testing anymore. Most of important packages have been rebuild but the remaining list still counts ~99 packages.

Do you guys think we can finish this rebuild this week? I think it's a good idea to put KDE 4.4 RC3 into testing when the jpng rebuild has moved into extra. This way we have some time to do some KDE related rebuilds and have the packages tested by more people.

Sure, apart from some of the openoffice variants, there is only 5 or 6 packages left to go. I think Andy was holding out for a release to finish the OOo stuff.

Allan

we can start accepting bugs no? as the others: last-exit dead upstream panda3d will be moved in arch-games visualboyadvance need a patch( Daenyth is working on it xf4vnc-xvnc moved in aur what do you think, is better to announce on news that a possible breakage can be if they use other cairo package? i found a lot of users who had that problem. -- Ionut

On Thu, Jan 28, 2010 at 10:50 AM, Pierre Schmitz wrote:

Am Donnerstag, 28. Januar 2010 16:16:42 schrieb Ionut Biru:

...

On 01/27/2010 02:03 AM, Allan McRae wrote:

...

On 27/01/10 09:56, Pierre Schmitz wrote:

...

Am Dienstag, 19. Januar 2010 02:15:10 schrieb Ionut Biru:

...

hi, just a heads up to inform that i don't recommend to update from testing anymore. Most of important packages have been rebuild but the remaining list still counts ~99 packages.

Do you guys think we can finish this rebuild this week? I think it's a good idea to put KDE 4.4 RC3 into testing when the jpng rebuild has moved into extra. This way we have some time to do some KDE related rebuilds and have the packages tested by more people.

Sure, apart from some of the openoffice variants, there is only 5 or 6 packages left to go. I think Andy was holding out for a release to finish the OOo stuff.

Allan

So, I just talked to Andy. OOo release is still a little undefined. What do you think about this plan:

* We put KDE 4.4 RC3 into testing (should be available in some hours) * This give us some more testing for KDE itself and let's us start some KDE/Qt  related rebuild (only few packages are affected) * KDE 4.4.0 (final) will be available around end of next week (tagging on 3rd) * We move everything (libjpeg, libpng, KDE, Qt rebuilds) to extra on February  9th/10th

What do you think about this? It should give us enough time for testing, rebuilding the remaining packages and does not block KDE.

This is going to absolutely destroy gerolde and our mirrors with rsync backlog. We really need to start getting some of this out there if possible since when we move packages from [testing] to other repos, we don't have a symlink farm like we do with arch="any" packages. -Dan

On Thu, Jan 28, 2010 at 11:39 AM, Pierre Schmitz wrote:

Am Donnerstag, 28. Januar 2010 18:28:38 schrieb Dan McGee:

...

This is going to absolutely destroy gerolde and our mirrors with rsync backlog. We really need to start getting some of this out there if possible since when we move packages from [testing] to other repos, we don't have a symlink farm like we do with arch="any" packages.

Yes I know, but I don't see any other option. Even if we move the jpng stuff right now, the mirrors will have a hard time to catch up. And we cannot move only parts as this would break everything.

ATM it looks like this:

11G     community 1.9G    community-testing 3.5G    testing 441M    core 13G     extra 1.3G    kde-unstable

It does not make much difference if we move testing and community-testing into extra right now or next week.

But not having another 1.3GB on top fo the 3.5GB will at least help somewhat, no? Or are you planning on moving kde into [testing] and jpng into [extra] at the same time? -Dan

On Thu, Jan 28, 2010 at 4:00 PM, Pierre Schmitz wrote:

Am Donnerstag, 28. Januar 2010 20:08:00 schrieb Dan McGee:

...

But not having another 1.3GB on top fo the 3.5GB will at least help somewhat, no?

You forgot the 1,9GB community-testing and several GB of openoffice. So yes, we are somehow screwed anyway. ;-)

...

Or are you planning on moving kde into [testing] and jpng into [extra] at the same time?

My idea was to put RC3 into testing, remove kde-unstable and around the 10th of february we can move the jpng rebuild into extra and a second later the KDE 4.4 final into extra. This would need some cooridination and we need to upload KDE into our staging dirs before the jpng move, but that should be doable. In the end this strategy should save us some traffic.

Additionally we could try to optimize the mirror syncing within the next two weeks.

Although we're pretty much screwed, we should try to not make our case worse. It might be better to do the jpng rebuild move seperate from the kde update. We could do it this way: - rebuild the current OO pkgs. Even if go-office doen't build, at least we should have some working OO pkg in the repo. Andy: I could help with that, just let me know. - push the jpng rebuild to extra/community - Wait a couple (3-4?) of days and monitor the mirror syncing from gerolde. This will give a head start to the mirrors to complete, at least, most of the sync for the jpng rebuild. - move the kde packages from kde-unstable to testing - etc.

--

Pierre Schmitz, https://users.archlinux.de/~pierre

Am Freitag, 29. Januar 2010 01:25:13 schrieb Pierre Schmitz:

OK, would this work? * move the jpng rebuild tomorrow (29.1) * we prepare the KDE build over the weekend * On Monday we remove kde-unstalbe and move the new KDE into testing * start KDE rebuild and testing * release the KDE final on February 9th/10th

So, what are we doing? The jpng rebuild seems to be complete if I didn't miss something. I could help creating a "move list" which we could pipe to the script. -- Pierre Schmitz, https://users.archlinux.de/~pierre

Am Samstag, 30. Januar 2010 16:06:24 schrieb Ionut Biru:

...

So, what are we doing? The jpng rebuild seems to be complete if I didn't miss something. I could help creating a "move list" which we could pipe to the script.

i propose that in 5 hours we start moving packages. in this interval we have time to fix, upload any rebuilds in testing/community-testing.

I attach a list to pipe to the move script. But we need to review the packages that are left in testing afterwards to make sure we did not miss some hidden deps. My list contains all pkgbase/pkgnames and the jpng/xulrunner/imagemagick rebuild. -- Pierre Schmitz, https://users.archlinux.de/~pierre

Btw: we could speed up rsync by doing this: * disable rsync on gerolde (both, the outgoing and the one syncing from sigurd) * cp -a all packages from community-testing into community on gerolde * start the move on sigurd (community) * start the move on gerolde (extra) * restart syncing from sigurd (should be just deletes) * restart rsync server for external mirrors * replace flyspray with a lolcat picture -- Pierre Schmitz, https://users.archlinux.de/~pierre

All vanilla OOo branches are built against the new libs. for go-oo I will need some more time maybe later tonight or this weekend. I also rebuild the missing nx-common (i686). Anything left? -Andy

Am Fri, 29 Jan 2010 17:11:04 +0200 schrieb Ionut Biru :

On 01/29/2010 05:02 PM, Andreas Radke wrote:

...

All vanilla OOo branches are built against the new libs. for go-oo I will need some more time maybe later tonight or this weekend.

I also rebuild the missing nx-common (i686).

Anything left?

-Andy

e17 i686 from community FS#18024. it has a building problem and i'm working on it now as Ronald asked me if i can help.

go-openoffice 3.2.0rc4 built for x86_64, still compiling i686. then my packages should be done. -Andy

On Thu, Jan 28, 2010 at 8:04 PM, Allan McRae wrote:

On 29/01/10 03:28, Dan McGee wrote:

...

This is going to absolutely destroy gerolde and our mirrors with rsync backlog. We really need to start getting some of this out there if possible since when we move packages from [testing] to other repos, we don't have a symlink farm like we do with arch="any" packages.

Didn't we have someone working on adjusting the db-scripts so all packages went to a "package" directory and were symlinked to the repo? That would save us much bandwidth and hassle with big rebuilds like these...

Can anyone remember who that was and if it was started?

As far as I remember, it was purely an idea. No work was started. I will try to add it into the db-scripts next week sometime. It shouldn't be too much work, though the cleanup scripts will need to be reworked a bit