On Wed, Feb 20, 2013 at 2:17 PM, Bill Nottingham <notting@xxxxxxxxxx> wrote: > Miloslav Trmač (mitr@xxxxxxxx) said: >> That would be very useful. >> >> 1) Easy: run a script to find affected packages and auto-file bugs. >> 2) Fairly possible: get at least the important packages fixed in F19 >> (or, 1+2: change default build configuration to cover most packages, >> and rebuild.) >> >> 3) Difficult to do right now? set up an automated test to ensure new >> packages are also covered and there are no regressions. > > 4) What do we do with 3rd-party apps that now spontaneously fail and > we can't get them rebuilt? > > (Not a huge concern for Fedora, but something we need to at least think > about so we can message it.) That depends on how much the applications rely on the data. The above-mentioned LD_PRELOAD library is an option (although documenting it in an effective way might be a challenge). If the applications expect 32-bit ino_t values to uniquely identify a file, we can't solve that without a rebuild (... or keeping a persistent database mapping "real" inode numbers to a 32-bit namespace). Mirek -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
