![]() Other opinions or suggestions on that matter are welcome. This would mean that the conflict with bigloo can’t be resolved until then. Credit for finding this vulnerability and the proof of concept from which the test. ![]() If too many users complain, I will probably use a transitional strategy: Rename the tools, add the note to README.Debian, but leave symlinks hanging around until after the release with etch. I think I will just try to rename afile (and a few other similar commands) to apple_file, add a note to NEWS.Debian, and upload this to unstable. But since this is a tool that is possibly used regularily by some users and may even be used in scripts, I fear that simply renaming it may break things. I had been using a very old copy of Netatalk (version no longer remembered) I installed on FreeBSD 3. Afp works perfectly for me, havent played around with printing yet. Netatalk 2.0.3 on a new FreeBSD 5.3 server. So i copied around 300GB to netatalk 2.0.3. Netatalk 2.0.3 runns for over 2 weeks now and i moved all my data from the old servers. Bigloo also contains a binary called afile, just like Netatalk. So ive only changed the name and i also added sys-libs/db as dependency, that was forgotten in the 2.0.1 ebuild. Resolving the conflict with bigloo is more bothersome. when updating a volume from one character set to unicode, which hopefully you will only have to do once per volume), this change should be fairly unobstrusive. ![]() As this is a tool that is only required very occasionally (i.e. This version solved the conflict with yudit by renaming /usr/bin/uniconv to /usr/sbin/netatalk-uniconv.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |