Martin Schulze <[EMAIL PROTECTED]> writes: > boot-floppies_2.2.24_i386.changes > boot-floppies_2.2.25_arm.changes > boot-floppies_2.2.25_i386.changes > boot-floppies_2.2.26_i386.changes > > 2.2.25: Important ARM fixes > > 2.2.26: Important PowerPC fixes > > Not sure if we should demand architectures to be in sync...
I don't think that's a requirement we could really enforce, and still get point releases out... In fact, I wonder whether all the ports still have the capability (machine around running Potato, with root access) to build. > pcmcia-modules-2.2.19-compact updates 3.1.22-0.2potatok4 i386 > pcmcia-modules-2.2.19-idepci updates 3.1.22-0.2potatok4 i386 > pcmcia-modules-2.2.19-ide updates 3.1.22-0.2potatok4 i386 > pcmcia-modules-2.2.19 updates 3.1.22-0.2potatok4 i386 > > install pcmcia-modules-2.2.19-compact_3.1.22-0.2potatok4_i386.changes > install pcmcia-modules-2.2.19-ide_3.1.22-0.2potatok4_i386.changes > install pcmcia-modules-2.2.19-idepci_3.1.22-0.2potatok4_i386.changes > install pcmcia-modules-2.2.19_3.1.22-0.2potatok4_i386.changes > remove pcmcia-modules-2.2.19pre17-compact > remove pcmcia-modules-2.2.19pre17-idepci > remove pcmcia-modules-2.2.19pre17-ide > remove pcmcia-modules-2.2.19pre17 > > Update for kernel-source-2.2.19pre17 > > Need further info, why aren't pcmcia-modules-2.2.19pre17-idepci > and the like sufficient? Herbert has mail. Since we build with kernel-image-2.2.19* for i386, we need the PCMCIA mdoules that go with that exact kernel as well. That is perhaps the reason. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...<URL:http://www.onshored.com/>
