On Fri, Jun 09, 2000 at 03:51:21PM -0400, Ben Collins wrote:
> Dark, once these show up, can you install them ASAP?
I have done so.
Richard Braakman
The arm ones are now also installed. This is great. We can start making
CD's after today's mirror pulse, I think. Please say "STOP" very loudly
if that is not the case.
Richard Braakman
We now have boot-floppies for alpha, i386, m68k, powerpc, and sparc in
the archive. What is the ETA for arm ones?
Richard Braakman
On Thu, Jun 08, 2000 at 03:33:35PM +0200, Christian Surchi wrote:
> On Thu, Jun 08, 2000 at 03:14:50PM +0200, Richard Braakman wrote:
>
> > The last one also container modules for kernel 2.2.14, which I removed
> > again because we no longer have 2.2.14 in potato.
>
>
.2.14, which I removed
again because we no longer have 2.2.14 in potato.
Now we only need sets for alpha and m68k to be complete.
Richard Braakman
;s dinstall run.
Richard Braakman
Excellent. I have installed boot-floppies_2.2.15_powerpc.changes
and xviddetect_0.3-2.1_i386.changes.
Which kernel version did you use, though?
Richard Braakman
k set will take at least till Sunday, mainly
because of compilation time.
Will it be possible to use the new kernel 2.2.15-2 (currently in Incoming),
or is it too late for that?
Richard Braakman
Needed for boot-floppies:
amiga-fdisk-bf_0.04-4_m68k.changes
kernel-patch-2.2.15-powerpc_2422-2.2.16pre4-1_powerpc.changes
dpkg_1.6.13_arm.changes
dpkg_1.6.13_m68k.changes
dpkg_1.6.13_powerpc.changes
I also installed:
netscape4.73_4.73-18_i386.changes
This is a fixup for the netscape4.73 in
ut of sync and the autobuilders may need some time to
catch up. I hope that the person compiling boot-floppies for
each architecture is aware of the situation for that architecture,
because I don't have an overview of that.
Richard Braakman
tell me
you need it.
I intend to disbelieve the remaining "release-critical" bugs, and see
if any of them turn out during testing to be real problems.
Richard Braakman
Can I remove all linux 2.2.13 and 2.2.14 related packages from the
archive prior to the second test cycle? That would zap bug#61544,
for one thing. It might also make potato one CD smaller :-)
Richard Braakman
rse taking care about the upgrading stuff, which I felt _forced_ to do
> because no-one even _cared_.
You don't have to do my job. You _are not_ doing my job -- you obviously
don't know how much is involved if you think that. But if you want it,
just let me know, and you'll have it. (Well, you will have to be a
Debian developer first.) I'm royally sick of it by now.
Richard Braakman
or stop this cycle and prepare new ones about a week
from now?
Richard Braakman
ion from ftpmaster/release manager (i.e.
> dark). He's being _extremely_ communicative to us CD people :-(
Why, thank you. I should note that I am _not_ ftpmaster, however. I
am a member of a team of five archive maintainers, and currently a
mostly inactive member because I'm busy being release manager.
Richard Braakman
I went through the list with drow, and we found some more uploads that
should have gone along with the boot-floppies but didn't:
aboot_0.7-1_alpha.changes
makedev_2.3.1-43_i386.changes
makedev_2.3.1-44_i386.change
Next time, I think we should organize this better.
Richard Braakman
-2.2.15pre20-1_powerpc.changes
kernel-image-2.2.15-sparc_2.2.15-0.19.4_sparc.changes
Richard Braakman
quot;merely" makes testing worthless, then it may still be worthwhile
to wait for the next cycle, especially if the change will interfere
with the work on other architectures.
Note that I'm not going to touch anything at all while James is busy
moving the archive.
Richard Braakman
I can prevent source uploads during
the test cycle, but not binary uploads. This is good because it
means the autocompilers have time to catch up, but bad if it means
the archive changes after we've made CD images. I don't know a good
way to deal with that.
Richard Braakman
uploads could perhaps be coordinated using one
of the lists (debian-release perhaps), so that I'll wait for an
explicit go-ahead before installing kernel-related packages.
Richard Braakman
I installed two packages today:
pcmcia-cs_3.1.8-12_i386.changes
kernel-image-2.2.10-powerpc-apus_2.2.10-11_powerpc.changes
Both of them claim to be necessary for the boot-floppies.
Richard Braakman
ill be ready for the cycle.
Since we still don't have boot-floppies for arm, we may have to
release without arm after all.
Richard Braakman
all others gives you a Debian
> with no missing dependencies?
The primary reason for priorities was to help people decide which packages
they want. If you want to create custom CDs with special properties, feel
free. If you notice that it doesn't really work with potato, feel free
to fix it in woody.
Richard Braakman
On Mon, Apr 24, 2000 at 12:28:08PM +0200, Adrian Bunk wrote:
> The next thing I'm doing is filing RC bugs for priority problems (most
> often: package with priority `optional' depends on package with priority
> `extra').
Please don't. Such bugs are not release-critical.
Richard Braakman
t Debian release ever,
then I think you need a break from Debian. Or go run hamm for a while,
see how much better it is than potato.
Richard Braakman
depending on device3dfx-module,
which the user must build locally, and tkirc depending on ircii,
which is in non-US).
The other architectures will definitely release with a lot of
unsatisfied dependencies, due to the binary-all situation.
Richard Braakman
f open dependency problems even in the i386 tree, and
the other trees are much worse.
Richard Braakman
ssues ironed out before the release.
Richard Braakman
y and unannounced? I think not.
We don't do that.
The changes to slink won't magically wait until we make the symlink;
people who follow stable will get the new packages immediately.
Richard Braakman
On Tue, Apr 18, 2000 at 05:15:28PM +0200, Martin Schulze wrote:
> Richard Braakman wrote:
> > Will it be possible to stage the first Test Cycle on or near May 2nd?
> > That's two weeks from now.
> >
> > It means that May 2nd is the last day I make any change t
On Thu, Mar 30, 2000 at 12:24:38AM -0600, Adam Di Carlo wrote:
> Despite the GPG issues, will this be able to percolate into potato?
Not without a valid signature.
Richard Braakman
't figure out what the problem is.
Richard Braakman
, so that we could start
the test cycle right after I make some last few changes on friday.
Looks like it's not going to happen that way.
Would this work:
On monday (or whenever you're ready) we start a one-week test of
the boot-floppies, during which time nothing changes in the base
system.
Richard Braakman
6.deb
> # potato should use 2.2.14, not 2.2.13 kernel
Done
> pcmcia-modules-2.2.14-compact_3.1.8-2_i386.deb
> # modules associated with the compact kernel flavor
Can't find it in Incoming.
--
Richard Braakman
ch
time there is for bugfixing.
At the start of a Test Cycle there will be a few days for autobuilders
to catch up and for the making of disksets and CD images. How many days
are needed for this?
Richard Braakman
t; partially. See my bug #53967 (no subject, I keep messing up in mysterious
> ways with the BTS somehow) against ftp.debian.org.
It was installed in slink-proposed-updates, where it still is.
Richard Braakman
d. Vincent says it will be released "soon", which
I take to mean about a week. Vincent, can you give details?
Richard Braakman
quot;stuff to do for the next slink".
(And I fervently hope that I won't be the one to have to worry about it
then, because the situation still isn't clear to me.)
So, what now?
Richard Braakman
it might
warrant a 3.0 all by itself :)
Richard Braakman
and then potato can be either 2.3
> or 3.0, depending on what Richard wants.
If the Revenge of Slink is 2.2, then potato will be 3.0, to avoid
confusion. The 2.2 -> 2.3 change will otherwise be far larger than
2.1 -> 2.2 was.
Richard Braakman
40 matches
Mail list logo
