List of packages for the "x86_64/debuginfo" component

- Applied upstream security fix (fixes CVE-2019-11500).
- Backport new version for Thunderbird to c7 branch.
- Backport new version for Thunderbird to c7 branch.
- Backport new version for Thunderbird to c7 branch.
- Backport new version for Thunderbird to c7 branch.
- Backport new version to c7 branch with enabled SQLITE_ENABLE_DBSTAT_VTAB.
- Backport new version to c7 branch with enabled SQLITE_ENABLE_DBSTAT_VTAB.
- Backport new version to c7 branch with enabled SQLITE_ENABLE_DBSTAT_VTAB.
- Backport new version to c7 branch with enabled SQLITE_ENABLE_DBSTAT_VTAB.
- Backport new version with security fixes to c7 branch.
- Backport new version to c7 branch.
- Backport new version to c7 branch.
- Backport new version to c7 branch.
- Backport new version to c7 branch.
- Backport new version to c7 branch.
- backport to c7
- backport to c7
- backport to c7
- backport to c7
- backport to c7
- build to c7
- Changes in what is considered "newer" by rpm -U from 4.0.4-alt101.M80P.5.4
  brought to c7.1.
- Changes in what is considered "newer" by rpm -U from 4.0.4-alt101.M80P.5.4
  brought to c7.1.
- Changes in what is considered "newer" by rpm -U from 4.0.4-alt101.M80P.5.4
  brought to c7.1.
- Changes in what is considered "newer" by rpm -U from 4.0.4-alt101.M80P.5.4
  brought to c7.1.
- Changes in what is considered "newer" by rpm -U from 4.0.4-alt101.M80P.5.4
  brought to c7.1.
- Changes in what is considered "newer" by rpm -U from 4.0.4-alt101.M80P.5.4
  brought to c7.1.
- build for M70C
- backport to M70C
- backport to M70C
- backport to M70C
- backport to M70C
- backport to M70C
- backport to M70C
- backport to M70C
- backport to M70C
- backport to M70C
- backport to M70C
- backport to M70C
- backport to M70C
- backport to ALTLinux c7 (by rpmbph script)
- ix86 arch support.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Rebuild with relocated custom-gcc libs.
- Backport new version to c7 branch.
- Remove puthon3 support.
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- journald: set a limit on the number of fields once more.
- journald: set a limit on the number of fields (1k) (fixes: CVE-2018-16865).
- Backport to C7
- Backport to C7
- Libraries of all versions of the custom-gcc can be found in the same place;
- Enabled compatibility mode - libstdc++, libatomic1, libgcc1, libgomp1,
  libitm1, libobjc4, libtsan0 and libquadmath0 are not included
  as they come with gcc5;
- Detection of 'provides' for the custom libraries.
- Libraries of all versions of the custom-gcc can be found in the same place;
- Enabled compatibility mode - libstdc++, libatomic1, libgcc1, libgomp1,
  libitm1, libobjc4, libtsan0 and libquadmath0 are not included
  as they come with gcc5;
- Detection of 'provides' for the custom libraries.
- Libraries of all versions of the custom-gcc can be found in the same place;
- Enabled compatibility mode - libstdc++, libatomic1, libgcc1, libgomp1,
  libitm1, libobjc4, libtsan0 and libquadmath0 are not included
  as they come with gcc5;
- Detection of 'provides' for the custom libraries.
- Libraries of all versions of the custom-gcc can be found in the same place;
- Enabled compatibility mode - libstdc++, libatomic1, libgcc1, libgomp1,
  libitm1, libobjc4, libtsan0 and libquadmath0 are not included
  as they come with gcc5;
- Detection of 'provides' for the custom libraries.
- Libraries of all versions of the custom-gcc can be found in the same place;
- Enabled compatibility mode - libstdc++, libatomic1, libgcc1, libgomp1,
  libitm1, libobjc4, libtsan0 and libquadmath0 are not included
  as they come with gcc5;
- Detection of 'provides' for the custom libraries.
- Libraries of all versions of the custom-gcc can be found in the same place;
- Enabled compatibility mode - libstdc++, libatomic1, libgcc1, libgomp1,
  libitm1, libobjc4, libtsan0 and libquadmath0 are not included
  as they come with gcc5;
- Detection of 'provides' for the custom libraries.
- Libraries of all versions of the custom-gcc can be found in the same place;
- Enabled compatibility mode - libstdc++, libatomic1, libgcc1, libgomp1,
  libitm1, libobjc4, libtsan0 and libquadmath0 are not included
  as they come with gcc5;
- Detection of 'provides' for the custom libraries.
- 2.0.22
- Backport new version to c7 branch.
- Backport new version to c7 branch (by bootstrap).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).
- C7 custom port:
  + No Ada, no Fortran, no Java, no Go;
  + No gdb-plugin and no libcilkrts;
  + Libraries and most executables can be found only by absolute paths
    which include GCC version\marker, common libraries of all versions
    of the custom-gcc can be found in the same place;
  + custom libraries (such as custom-libstdc++6 and custom-libgcc1)
    should not be used in runtime (maintainers should set RPATH to use them
    in exceptional cases).