From: Hendrik Boom <hendrik@topoi.pooq.com>
To: caml-list@inria.fr
Subject: [Caml-list] opam corrupted my sources.list.
Date: Sat, 17 Dec 2016 22:01:47 -0500 [thread overview]
Message-ID: <20161218030147.GB15171@topoi.pooq.com> (raw)
Well, technically, it was the directory /etc/apt/sources.list.d that
got an unwanted file:
opam.list
and I'm guessing that it was opam from the name of that file.
It contained the line:
deb http://download.opensuse.org/repositories/home:/ocaml/Debian_7.0/ /
This caused havoc with my system because I am *not* running Debian or
suse, but devuan, a Debian derivative, and I am now stuck with
aptitude tring to install a *huge* collection of unwanted and
inconsistent packages because the dependencies in my system are
different from those in the openuse repository.
I am still unable to use aptitude to do routine upgrades.
Why does opam do this? And, is it indeed opam?
Perhaps devuan needs to do something special with ocaml-related
packages, but until I know what's happening and why it's hard to know
where to start.
-- hendrik
next reply other threads:[~2016-12-18 3:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 3:01 Hendrik Boom [this message]
2016-12-18 4:42 ` Gabriel Scherer
2016-12-18 16:38 ` Hendrik Boom
2016-12-18 17:04 ` Xavier Leroy
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=20161218030147.GB15171@topoi.pooq.com \
--to=hendrik@topoi.pooq.com \
--cc=caml-list@inria.fr \
/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).