From: Helge Deller <deller@gmx.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: Do we have a buildd problem?
Date: Tue, 30 Jul 2019 22:16:24 +0200 [thread overview]
Message-ID: <02fb2132-61b0-ef5f-6ceb-e8854d40d030@gmx.de> (raw)
In-Reply-To: <1564513941.4300.33.camel@HansenPartnership.com>
On 30.07.19 21:12, James Bottomley wrote:
> 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?
Works for me.
The following additional packages will be installed:
git-man
Suggested packages:
git-daemon-run | git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-cvs git-mediawiki git-svn
The following packages will be upgraded:
git git-man
2 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
Need to get 7.161 kB of archives.
After this operation, 1.199 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.ports.debian.org/debian-ports unstable/main hppa git-man all 1:2.23.0~rc0-1 [1.675 kB]
Get:2 http://incoming.ports.debian.org/buildd unstable/main hppa git hppa 1:2.23.0~rc0-1 [5.486 kB]
It takes up to 6 hours until the git package gets moved to the standard ports repository.
You can (temporarily) work around it by adding
deb http://incoming.ports.debian.org/buildd unstable main
to /etc/apt/sources.list
Helge
prev parent reply other threads:[~2019-07-30 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 19:12 Do we have a buildd problem? James Bottomley
2019-07-30 20:16 ` Helge Deller [this message]
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=02fb2132-61b0-ef5f-6ceb-e8854d40d030@gmx.de \
--to=deller@gmx.de \
--cc=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).