Development/Tasks/Packaging/BuildSystem/Problems

From Mandriva Community Wiki

Jump to: navigation, search


Quick and assorted list of BuildSystem problems to be solved. We'll use bugzilla as soon BS is stable and documented.

  1. i586 builds are very slow, while x86_64 is fast. Many i586 builds keep entering and exiting the build state for no apparent reason, only to enter again in some other node and have the same issue
  2. Packages uploaded to non-cooker distro loose the misc changelog because it's only for cooker (have to check this in more detail -- andreas)
  3. no qos for interactive remote work and for remote svn access (any huge transfer in aboukir affects remote maintainers)
  4. svn+ssh slower than https access
  5. unstable cluster network (NFS NIS issues)
  6. old hardware and lack of storage space
  7. lack of documentation for contributors (the existing is outdated and too complex). The contents of twiki pages talking about the Build System have several overlaps and are not clear.
  8. N different tools with no clear objective (youri, youri.devel, youri.queue, repsys, mdvsys, etc) - ok, some of them are already obsoleted and this may be just a documentation issue
  9. confusing semantics of distro targets
  10. insane verbosity of submission tools and logs
  11. lack of build monitoring
  12. lack of cluster health monitoring (we can not rely on just a few persons to put the cluster back to work)
  13. no control of scheduled build bots (seen several bots building the same package)
  14. critics for tools code and documentation (not easy maintenance and lack of robustness)
  15. bugzilla is often slow or unreachable
  16. broken package maintainers list
  17. bad cluster account management (case by case with no automation)
  18. unused (?) reports sent by bots about broken dependencies
  19. i18n infra-structure outdated (cvs versus svn usage) - !as good as all modules for i18n are moved to svn now!..
  20. bug #27260. Be more robust regarding disk space problems. For example, if /tmp is full, this is what one would get:
[thomas@kenobi ~]$ mdvsys submit kernel-tmb
error: command failed: rpm -bs --nodeps --define '_topdir
/tmp/tmp49qAD3' --define '_builddir /tmp/tmp49qAD3/BUILD' --define
'_rpmdir /tmp/tmp49qAD3/RPMS' --define '_sourcedir
/tmp/tmp49qAD3/SOURCES' --define '_specdir /tmp/tmp49qAD3/SPECS'
--define '_srcrpmdir /tmp/tmp49qAD3/SRPMS' --define '_patchdir
/tmp/tmp49qAD3/SOURCES'  --define 'packager Thomas Backlund
<tmb@mandriva.org>' /tmp/tmp49qAD3/SPECS/kernel-tmb.spec
error: Unable to open temp file.
*** glibc detected *** /usr/lib/rpm/rpmb: free(): invalid pointer:
0x085d91c0 ***
======= Backtrace: =========
[0x8406180]
[0x8409231]
[0x8051fa2]
======= Memory map: ========
sh: line 1: 26360 Aborted                 LANG=C LANGUAGE=C LC_ALL=C rpm
-bs --nodeps --define '_topdir /tmp/tmp49qAD3' --define '_builddir
/tmp/tmp49qAD3/BUILD' --define '_rpmdir /tmp/tmp49qAD3/RPMS' --define
'_sourcedir /tmp/tmp49qAD3/SOURCES' --define '_specdir
/tmp/tmp49qAD3/SPECS' --define '_srcrpmdir /tmp/tmp49qAD3/SRPMS'
--define '_patchdir /tmp/tmp49qAD3/SOURCES' --define 'packager Thomas
Backlund <tmb@mandriva.org>' /tmp/tmp49qAD3/SPECS/kernel-tmb.spec

Use of uninitialized value in concatenation (.) or string at
/usr/bin/mdvsys line 388.

Can't submit kernel-tmb

References:

Personal tools