Re: amd64 porters IRC meeting: preparations for sarge

2005-04-26 Thread Goswin von Brederlow
Thomas Steffen [EMAIL PROTECTED] writes: On 4/25/05, Goswin von Brederlow [EMAIL PROTECTED] wrote: [openoffice and libraries] It's probably easier to write an installer that fetches and installes the i386 debs on the fly. Maybe it is just because of my research background, but I am

Re: amd64 porters IRC meeting: preparations for sarge

2005-04-26 Thread Thomas Steffen
On 4/26/05, Goswin von Brederlow [EMAIL PROTECTED] wrote: If you have a chroot that is simple: 'apt-get install foobar' in the chroot dpkg --force-architecture -i /chroot/var/cache/apt/foobar*deb Yes, that is a start. But I don't think that any --force-* options should be exposed to the

Re: amd64 porters IRC meeting: preparations for sarge

2005-04-26 Thread Goswin von Brederlow
Thomas Steffen [EMAIL PROTECTED] writes: On 4/26/05, Goswin von Brederlow [EMAIL PROTECTED] wrote: If you have a chroot that is simple: 'apt-get install foobar' in the chroot dpkg --force-architecture -i /chroot/var/cache/apt/foobar*deb Yes, that is a start. But I don't think that any

Re: amd64 porters IRC meeting: preparations for sarge

2005-04-25 Thread Goswin von Brederlow
Thomas Steffen [EMAIL PROTECTED] writes: On 4/23/05, Martin Zobel-Helas [EMAIL PROTECTED] wrote: Here we go: Logfile: http://debian-amd64.alioth.debian.org/irc-log.txt Summary: http://debian-amd64.alioth.debian.org/irc-summary.txt Thank you very much for the results and the log. The

amd64 porters IRC meeting: preparations for sarge

2005-04-21 Thread Frederik Schueler
Hello, This is a reminder on the IRC meeting taking place on next saturday, April 23rd - the scedule was now set for 0700 UTC. The meeting will take place in #debian-amd64 on irc.oftc.net. The agenda is as follows: - the sarge release of debian-amd64 - patched versions of packages in sarge

amd64 porters IRC meeting: preparations for sarge - second call

2005-04-17 Thread Frederik Schueler
Hello, This is a reminder on the IRC meeting taking place on next saturday, April 23rd either 0700 UTC or 1400 UTC. The final scedule is still to be fixed. The initial call can befound here: http://lists.debian.org/debian-amd64/2005/04/msg00307.html the current scedule and topics list is to

Re: amd64 porters IRC meeting: preparations for sarge

2005-04-12 Thread Daniel James
Hi Frederik, I would like to collect additional topics and scedule proposals for the IRC meeting about the future of the debian-amd64 sarge distribution. Is this intended to be an open meeting? If so, I would like to listen in. Cheers Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED]

Re: amd64 porters IRC meeting: preparations for sarge

2005-04-12 Thread Frederik Schueler
Hello, The current scedule proposal is to meet on saturday 23rd, what allows us to find a timeframe fitting everyone's needs. I think 7:00 UTC is a good idea, alternatively 14:00 UTC. On Mon, Apr 11, 2005 at 02:30:09PM -0700, Alex Perry wrote: I suspect another relevant agenda item is: Which

Re: amd64 porters IRC meeting: preparations for sarge

2005-04-12 Thread Frederik Schueler
Hello, On Tue, Apr 12, 2005 at 09:05:41AM +0100, Daniel James wrote: Is this intended to be an open meeting? If so, I would like to listen in. Everyone interested can join, of course :-) We will publish a log on alioth for those who cannot attend. Kind regards Frederik Schueler -- ENOSIG

amd64 porters IRC meeting: preparations for sarge

2005-04-11 Thread Frederik Schueler
Fellow debian-amd64 porters, I would like to collect additional topics and scedule proposals for the IRC meeting about the future of the debian-amd64 sarge distribution. What I would like to discuss, is how we are going to handle: - the sarge release of debian-amd64 - patched versions of

Re: amd64 porters IRC meeting: preparations for sarge

2005-04-11 Thread Alex Perry
Frederik Schueler wrote: Now, what we need to start the meeting is: [...] 18:00 UTC is fine by me. Don't forget we've switched to summer time; it's 11am PDT for example. I'd like to avoid 8:00 UTC because that's 1am PDT but 7:00 UTC would be usable for me. I suspect another relevant agenda