Re: New Packages
> Hmmm... egcs is up-to-date as of yesterday.
It isn't! On master (now, 11:00 GMT+0200), I find the following files
matching "egcs" or "egcc" under the Incoming and under the archive:
Archive/dists/frozen/main/source/devel/egcs_1.0.3a-0.6.dsc
Archive/dists/frozen/main/binary-i386/devel/egcs-docs_2.90.29-0.6.deb
Archive/dists/frozen/main/binary-i386/devel/egcc_2.90.29-0.6.deb
Archive/dists/frozen/main/binary-m68k/devel/egcs-docs_2.90.29-0.5.deb
Archive/dists/frozen/main/binary-m68k/devel/egcc_2.90.29-0.5.deb
Archive/dists/frozen/main/binary-alpha/devel/egcs-docs_2.90.29-0.6.deb
Archive/dists/frozen/main/binary-sparc/devel/egcs-docs_2.90.29-0.1.deb
Archive/dists/frozen/main/binary-sparc/devel/egcc_2.90.29-0.1.deb
Archive/dists/unstable/main/source/devel/egcs_1.0.3a-0.6.dsc
Archive/dists/unstable/main/binary-i386/devel/egcs-docs_2.90.29-0.6.deb
Archive/dists/unstable/main/binary-i386/devel/egcc_2.90.29-0.6.deb
Archive/dists/unstable/main/binary-m68k/devel/egcs-docs_2.90.29-0.5.deb
Archive/dists/unstable/main/binary-m68k/devel/egcc_2.90.29-0.5.deb
Archive/dists/unstable/main/binary-alpha/devel/egcs-docs_2.90.29-0.6.deb
Archive/dists/unstable/main/binary-sparc/devel/egcs-docs_2.90.29-0.1.deb
Archive/dists/unstable/main/binary-sparc/devel/egcc_2.90.29-0.1.deb
I.e., source, alpha, and i386 has -0.6, m68k has -0.5, and sparc -0.1.
Is that up-to-date??
> The samba update was actually a slip of the fingers on my part
But we have to recompile it if we want to be uptodate...
> "dialog" is about the only important one.
I've uploaded dialog, imap, and pstotext at around 10:00 (GMT+0200)
today. Most of the time I let packages build overnight (as a batch
job), so I can sign und upload stuff only the next morning.
> I'm sorry, but the bottom line is whatever doesn't get in today in
> about 1.5 hours won't be in Debian 2.0.
Then the fixed dialog is surely missing... But the new xfree seems to
have slipped in.
But something else: I (we?) heard from James that the release should
be near the end of the week, maybe the night between Thursday and
Friday. This is still ~ 13 hours away... And then comes a mail "There
are those packages to be updated (additional to the ones left from
earlier), please have them ready in 4 hours." at Wed afternoon. How do
you think we should do that? Our automatic system for telling us which
packages need rebuilding has a delay of ~ 1 day, so even previous
packages haven't been done (e.g. samba).
Either you let those packages we've uploaded after your deadline
(about which we didn't know about until 4 hours before) into hamm, or
we need some way to hold pressing of m68k CDs and upload them to
stable or something else. AFAIK, there are even no current boot disks
for m68k. Franky?
Roman
--
To UNSUBSCRIBE, email to debian-68k-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: