[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

interpreting the buildd log


I'd like to get my package (geomview) into "testing".  ARM is one
of the architectures for which the build has failed, so I had a look
at the buildd log to see why.

The log is at 


and what it says is:

-------------------------- log -------------------------

  /usr/bin/sudo /usr/bin/apt-get  -q -y install debhelper lesstif-dev texi2html mesag-dev
Reading Package Lists...
Building Dependency Tree...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Sorry, but the following packages have unmet dependencies:
  debhelper: Depends: perl but it is not going to be installed
             Depends: lynx
E: Sorry, broken packages
apt-get failed.
Package installation failed
Trying to reinstall removed packages:
Trying to uninstall newly installed packages:
Source-depedencies not satisfied; skipping geomview

-------------------------- log -------------------------

Is this a real bug somewhere, or merely a symptom of the situation
that "some required packages have not yet been created or been moved
out of Incoming"?  

Assuming the latter, will the buildd get around to re-attempting the
build of geomview?  Is it automatic, or does someone need to nudge it?

I'm not an ARM person, so any insight is appreciated.


Reply to: