On 4/22/17 5:08 AM, Colin Watson wrote:
> On Sat, Apr 22, 2017 at 06:22:54AM -0000, bramint wrote:
>> there should be a way for all packages to get new .conf files after you
>> make messed up the one you have and you didn't back it up. :-/
> Removing and then using --force-confmiss in the same way as I explained
> there does generally work.
>
Thx :-)
_______ _______ _______ ______
*Joe Saladino* [<email address hidden> <mailto:<email address hidden>>]
*Ph:* (208) 971-7570
On 4/22/17 5:08 AM, Colin Watson wrote:
> On Sat, Apr 22, 2017 at 06:22:54AM -0000, bramint wrote:
>> there should be a way for all packages to get new .conf files after you
>> make messed up the one you have and you didn't back it up. :-/
> Removing and then using --force-confmiss in the same way as I explained
> there does generally work.
>