hazza_ob
Posts: 6
Joined: Thu Aug 25, 2016 9:42 pm

Netatalk install error code (1)

Wed Aug 09, 2017 7:14 pm

Installing netatalk on my Raspberry Pi 3
Steps:
sudo apt-get update
sudo apt-get netatalk

Results:
root@fsociety:~$ sudo apt-get install netatalk

Reading package lists... Done
Building dependency tree
Reading state information... Done

The following NEW packages will be installed:
netatalk
0 upgraded, 1 newly installed, 0 to remove and 23 not upgraded.
Need to get 0 B/683 kB of archives.
After this operation, 2995 kB of additional disk space will be used.
(Reading database ... 259419 files and directories currently installed.)
Preparing to unpack .../netatalk_2.2.6-1_armhf.deb ...
Unpacking netatalk (2.2.6-1) ...
dpkg: error processing archive /var/cache/apt/archives/netatalk_2.2.6-1_armhf.deb (--unpack):
trying to overwrite '/usr/bin/dbd', which is also in package dbd 1.50-1kali2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/netatalk_2.2.6-1_armhf.deb

E: Sub-process /usr/bin/dpkg returned an error code (1)


Any thoughts greatly appreciated.

epoch1970
Posts: 5203
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Netatalk install error code (1)

Wed Aug 09, 2017 8:31 pm

Get version 2.2.5 from stable rather than 2.6 testing, then

Code: Select all

apt-cache policy netatalk
netatalk:
  Installed: 3.1.7-1+local
  Candidate: 3.1.7-1+local
  Version table:
 *** 3.1.7-1+local 100
        100 /var/lib/dpkg/status
     2.2.6-1 10
         10 http://mirrordirector.raspbian.org/raspbian testing/main armhf Packages
     2.2.5-1+b1 999
        999 http://mirrordirector.raspbian.org/raspbian jessie/main armhf Packages
You can mix testing and stable with package pinning. I think it is a bit of a dark art, but this works for me:

Code: Select all

cat /etc/apt/preferences.d/jessie-pin-999 
Package: *
Pin: release n=jessie
Pin-Priority: 999

Package: *
Pin: release a=testing
Pin-Priority: 10
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

Return to “Troubleshooting”