From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Parisc List <linux-parisc@vger.kernel.org>
Subject: Do we have a buildd problem?
Date: Tue, 30 Jul 2019 12:12:21 -0700 [thread overview]
Message-ID: <1564513941.4300.33.camel@HansenPartnership.com> (raw)
Our ports archive is out of date. I'm getting this problem trying to
apt-get upgrade:
The following packages have unmet dependencies:
git : Depends: git-man (< 1:2.22.0-.) but 1:2.23.0~rc0-1 is to be installed
E: Unable to correct problems, you have held broken packages.
The issue seems to be that our hppa version of git is
http://ftp.ports.debian.org/debian-ports/pool-hppa/main/g/git/git_2.22.0-1_hppa.deb
But the arch indep pool version of git-man is
http://ftp.ports.debian.org/debian-ports/pool/main/g/git/git-man_2.23.0~rc0-1_all.deb
Indicating our binaries are out of sync. However, when I look at the
buildd status:
https://buildd.debian.org/status/package.php?p=git&suite=sid
It thinks the hppa version 2.23.0~rc0-1 built successfully, it's just
not in the ports directory for some reason?
James
next reply other threads:[~2019-07-30 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 19:12 James Bottomley [this message]
2019-07-30 20:16 ` Do we have a buildd problem? Helge Deller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1564513941.4300.33.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-parisc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).