afpd configuration file typo

Bug #992849 reported by Chris
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
netatalk (Ubuntu)
Triaged
Low
Unassigned

Bug Description

The file /etc/netatalk/afpd.conf

Contains:
# -nozeroconf Don't register this server with the Multicats
# DNS Protocol.

It should be "Multicast" not "Multicats"

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: netatalk (not installed)
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Tue May 1 21:50:53 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: netatalk
UpgradeStatus: Upgraded to precise on 2011-12-24 (129 days ago)

Revision history for this message
Chris (ccouzens) wrote :
Logan Rosen (logan)
Changed in netatalk (Ubuntu):
status: New → In Progress
assignee: nobody → Logan (logatron)
Revision history for this message
Stefano Rivera (stefanor) wrote :

This seems like something that should be forwarded to upstream netatalk.

If we made this change in Ubuntu only, we wouldn't be able to automatically sync netatalk from Debian any more.

Logan Rosen (logan)
Changed in netatalk (Ubuntu):
status: In Progress → Confirmed
assignee: Logan Rosen (logan) → nobody
Revision history for this message
Logan Rosen (logan) wrote :

This typo is no longer upstream. I'd say this is just a waiting game until the latest release comes into Debian unstable/the current development release of Ubuntu. It doesn't make sense to create a delta in Ubuntu or Debian for a simple typo.

Changed in netatalk (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Low
Revision history for this message
dmarks (markstedt) wrote :

While the typo was fixed in netatalk3 (the entire conf file was revamped) it is still present in netatalk2. I will address the issue upstream in https://github.com/Netatalk/netatalk/issues/333

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.