Custom Query (344 matches)
Results (52 - 54 of 344)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#349 | fixed | Fehler bei Aktualisierung über Arca Noae Package Manager | ||
Description |
Ich habe versucht, ArcaOS 5.0.6 über den Package Manager zu aktualisieren. Dabei wird die folgende Nachricht ausgeworfen, verbunden mit der Bitte, "diesen Fehler unter http://trac.netlabs.org/rpm/" zu melden: "ERROR with transaction check vs depsolve:libpsl>00.21.1 wird benötigt von libcurl-7.75.0-2oc00.i686..." Danke! |
|||
#259 | wontfix | Finer granularity for OS/2 DLL dependency generator | ||
Description |
Currently, the OS/2 DLL dependency generator detects only DLL names for Requires/Provides? but not the functions which are imported or exported. However, sometimes the import/export list of a DLL changes w/o changing its name. The most frequent case is addition of new exports.
Imagine a situation: LIB.DLL gets a new export FOO. This lib is released to a beta repository (not available for everyone) with Note that this mostly applies to cases when new exports are added to a DLL because if there is a change or removal, the DLL becomes non-backward compatible which requires to change its name (and when the name changes, the dependency generator will update the dependency forcing the user to update the DLL as well). A proposed solution is to increase granularity of the Provides/Requires? records by adding not only the DLL name but the export name as well — using the parenthesis notation just like other generators (e.g. perl, python, pkg-config etc) do. So in the above imaginary case, the generator should add the following for the LIB.DLL RPM: Provides: LIB.DLL Provides: LIB.DLL(FOO) And the following for the APP RPM: Requires: LIB.DLL(FOO)
instead of just This way, any potential problems related to export/import mismatches will be solved automatically and for all possible combination of package dependencies. This is relatively easy to implement as all imports and exports are collected in the respective sections of EXE and DLL files in binary form (so it's fast to extract this information). The only potential problem I see is C++ DLLs which export huge amounts of C++ symbols (i.e. the Qt DLLs contain thousands of exports). But it doesn't sound too serious per se as RPM is designed to handle thousands of dependencies. |
|||
#277 | fixed | Fix sys.executable detection | ||
Description |
This works right: D:>python -c 'import sys; print sys.executable' C:/USR/BIN/python.exe This works wrong: D:>python2.7 -c 'import sys; print sys.executable' D:/Coding/Tests/python/ |