-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/25/12 18:56, Antoine Beaupré wrote: > On Sun, 25 Mar 2012 18:19:28 -0500, Mike Mestnik <che...@mikemestnik.net> wrote: >> Thank you for the patch and I approve the change. > > Awesome. > >> I'm struggling with the init file in regards to bug 508010, but I can do >> what it seams like every one else is doing and just ignore it. > > I am not sure I understand what you are refering to here. I parse this > as: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508010 > > which is a bug in kbibtex, which seems completely unrelated (Cannot add > search URL). My bad. 208010 Require init.d scripts comply with LSB
> >>> The other issue is that there is no config file installed in >>> /etc/atheme-services, which makes the package a bit ackward after >>> install. Is there a sample upstream config with proper defaults we could >>> deploy in debian/rules? >> This is purposefully left out. The reason is that this pkg works with >> so many other ircd pkgs that it's best left empty. There should be a >> base config in >> >> See /usr/share/doc/atheme-services/examples >> >> However there _should_ be a README.Debian that explains what needs doing >> to get the service running and working. This is something that is missing. > > This makes sense. Something in the startup script may be useful too, > especially since we already talk to the user, telling him to enable the daemon. > >>> Finally, I notice that the SVN repository hasn't been updated with the >>> work you have just did. Do you have access to that project in Alioth, >>> and if not, can we arrange so that you publish your changes there? >> Hopefully I'll get access to that. > > Yep, if you need help let me know. > >>> I'm not really attached to the SVN repository however, we could as well >>> startup a new git repo somewhere. I just want to avoid the flying >>> tarballs and have a reference, versionned, repository of our changes. >> >> I'm using git currently, however I don't want to have an old repository >> and a new one. If the SVN repository can be migrated, that's great. I'm looking at m.d.n as I re-upload the same pkg every half hour and it seams like it's not too keen on me doing that. and... I totally messed whatever it was I was attempting to do up. > > History should be importable with the git-svn package. However, I'd like > us to avoid using *both* SVN and git at the same time, we've had bad > past experiences with that. I'll watch out for that. Yeah it was easy to import the svn repo into my existing git repo with git-svn. I'm new to git, but I know I'm not as big a fan of SVN as I am of say CVS. Thus far there is noting in git I don't particularly like. There is a convention for doing vendor branches, but it's better to make another repository. While having all those folders around, each containing a repo, can make a mess of things... It's preferred over being forced into a single way of doing things. > > Let's just import it once. > > I can do that too if you feel unconfortable with that. > > A. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPb7UiAAoJEOPRqa2O3KuKTC0P/3kFPSji6IrrtY9INZ14A33r Ehj/s15RMMIjzrPZhczSSQy4+pS8inSghks0IA2VZzcGbj8xAqSvJ0SIY/tHTbl+ 9M6RGmRfKQ+HHXlEOYzZKhIr9rAAr8aKM9Y8fvWrZNn/vBGfWagfAAfW7tjf0waQ s/gwXNcWZxsa5NFDdJmLCSgKtPYh5R4DGaFHp75xLrAevW48mZZ3aIU0CU/2G89B D1Z3OdEEJH4tpOUJL++0njUD1L+d0kjFpdwthWZG0CZYWsCp3yvp0R/VouYALKV8 he+3FHOhs8kgn1MqW/tRjAkdIZP/8jt9RAga8QkIhleGO3mZB6Ztk/xtXPqG39ep QfvusKVl4fAMmAJ62oWGSPinaFcefNnay0WoqjtREXckP8F5FaZh0SEIZ61YH6WZ C9At5sydRMVBjOzGpb4nnwyC6O5TEhHW4jTxwt2DJDowYjFtyU5zPy1BmKl0J8xz VJ7hghIOc+s6IEgGRF4lY8T+8NyatEqLq2/CV74KRQQxd7na08ooKXQfeUc3iNIx VpUzr8cAJh9Vqp/b1x5jtSkUywj9mmT3oW8fEz4ahdK4ZQAPpJbH3T8pGcWPCT6A LzsXoYqduzIRQzfOAwp7R4wrURtzrcLMEmO98ehGsPRZoCsLev8YCJaDFDVhK1Uh zo2sUPcKi7Xyfh8NXnJB =6exL -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f6fb522.3060...@mikemestnik.net
