From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: sparclinux@vger.kernel.org
Subject: Re: Trying out debian sparc64
Date: Fri, 14 Jul 2017 12:16:52 +0000 [thread overview]
Message-ID: <20170714121652.GD26530@physik.fu-berlin.de> (raw)
In-Reply-To: <alpine.LRH.2.20.1707141131580.3086@math.ut.ee>
On Fri, Jul 14, 2017 at 03:10:22PM +0300, Meelis Roos wrote:
> Unrelated - git seems to be not installable at the moment because of
> version conflict with git-man?
This is a known bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug†6011
Fetch the matching version for git-man from here:
> http://snapshot.debian.org/package/git/1%3A2.11.0-4/#git-man_1:3a:2.11.0-4
Debian Ports unfortunately immediately purges "all" packages from the
archive the moment a new version is uploaded to unstable, independent
whether any of the architectures still needs the older version for
whatever reasons.
> sparc-utils seems to be missing from sparc64 - no eeprom and prtconf
> programs? Sending prtconf output was my first task after getting system
> installed, since there is no t5140 in the prtconfs repo.
You need to add "unreleased" to your sources.list [1]:
deb http://ftp.ports.debian.org/debian-ports/ unreleased main
sparc64-only packages cannot be in unstable until sparc64 has become a
release architecture.
Adrian
> [1] https://people.debian.org/~glaubitz/sources.list
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2017-07-14 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 8:45 Trying out debian sparc64 Meelis Roos
2017-07-14 9:21 ` John Paul Adrian Glaubitz
2017-07-14 11:11 ` Meelis Roos
2017-07-14 11:19 ` John Paul Adrian Glaubitz
2017-07-14 12:10 ` Meelis Roos
2017-07-14 12:16 ` John Paul Adrian Glaubitz [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=20170714121652.GD26530@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.