I agree with Goswin that this is a problem that needs to be solved.
I host several private repositories that offer packages that contain files and configurations for ubuntu clients. these files often replace files of different packages, without breaking the package.
My problem is indeed that, once I am forced to remove the packages that I installed previously from our private repositories, the original packages are left broken. My fix at the moment is either to make a backup of the orinials and restore them on post removal - however, this is not so pretty.
Is there a best practice how to deal with such a situation?
Regards
Felix
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
<body class='hmmessage'><div dir='ltr'>
I agree with Goswin that this is a problem that needs to be solved.<br><br>I host several private repositories that offer packages that contain files and configurations for ubuntu clients. these files often replace files of different packages, without breaking the package.<br><br>My problem is indeed that, once I am forced to remove the packages that I installed previously from our private repositories, the original packages are left broken. My fix at the moment is either to make a backup of the orinials and restore them on post removal - however, this is not so pretty.<br><br>Is there a best practice how to deal with such a situation?<br><br>Regards<br>Felix<br> </div></body>
</html>
To UNSUBSCRIBE, email to debian-dpkg-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive:
http://lists.debian.org/SNT105-W43C...5C3A6D4F40@phx.gbl
Create a new topic
Follow the discussion
3 replies
Make a reply
May 19th, 2013 - 3:04 AM ET
Join now
Login
Replies