From: Gregory Nowak <greg@romuald.net.eu.org>
To: speakup@braille.uwo.ca
Subject: apt-get dist-upgrade replacing debs built with apt-src
Date: Fri, 10 Mar 2006 18:59:27 -0700 [thread overview]
Message-ID: <20060311015927.GA25359@localhost.localdomain> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all.
I realize this is a debian-specific question, but I thought someone
might have an answer.
I've built a couple of packages from source using apt-src, and have
modified either the package's Makefile and/or debian/rules to meet my
needs and configuration, which were not met by how the package
maintainer built the package. The problem is that whenever I do a apt-get
dist-upgrade, the upgrade process replaces my locally built debs with
the ones from the repository, even if both are the same exact version,
and I'm sure that they are.
Any suggestions on what I can do to keep this from happening? Thanks
much in advance.
Greg
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFEEi7/7s9z/XlyUyARAkNvAKCLS0XipPUoqKAz+MqRp+0NKFD85ACfePl7
CWe6keH903LoGDNPH+3yigE=
=HPaF
-----END PGP SIGNATURE-----
next reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak [this message]
` Lorenzo Taylor
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=20060311015927.GA25359@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).