Hallo Fernando, I saw on mentors that you've uploaded a new version and commented there: > Do i need to throw a new RFS? No, you just send a mail to 723...@bugs.debian.org
I already took a look this morning, here you go: -> Do NOT override binary-without-manpage --> You need to write a manpage -> Do NOT override description-synopsis-might-not-be-phrased-properly --> You need to fix your description in d/control -> You made a native package. That is wrong. What you need to do is in the description of native-package-with-dash-version (namely making debian/source/format to contain "3.0 (quilt)") -> You need also to rename the source-package. I see some still some other problems with the package, like the source-package name cannot be metar. Also you do not need to make the directory structure under mcode ... Just put your two files in the root directory and let do debhelper do all the magic. E.g it will automatically detect the copyright file and will install it into the right directory. This is why the duplicate-files error shows up: You are not doing it correctly... So your "upstream tar" should have just this file tree: metar-0.2/copyright metar-0.2/metar (ignoring that you cannot name your executeable meetar) No usr/ in there. The debian *.install will be the place where to specify where put the executeable, copyright will be automatically detected and installed correctly. Eric noted also that metar in the archives does the same thing. Usually it should be avoided to have two packages doing the same thing unless there are other advantages to the users. But maybe you can convince us that your version is superior? Best regards, coldtobi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
