Bug#513322: ITP: mupen64plus -- plugin-based N64 emulator
On Monday 01 June 2009 15:27:18 Félix Arreola Rodríguez wrote: > Well, maybe I should give the ITP to another people, someone who has > experience in the deb packing. You should not give up so fast. No perfect debian maintainer fell from heaven yet. You only have to make small steps and sometimes in the future it will be a real good package and you a good maintainer. You should take a look at the repository - most problems should be fixed there and http://lists.debian.org/debian-legal/2009/06/msg2.html should give an answer about what to do with the unlicensed files. -- Robert Wohlrab -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513322: Fwd: Bug#513322: ITP: mupen64plus -- plugin-based N64 emulator
Well, maybe I should give the ITP to another people, someone who has experience in the deb packing. I was thinking that I can do the work, but, maybe it's not for me... It's ok, I now know why Debian is so cool, because it has people who take care of all. I just want to say thank you for this oportunity. Maybe in the future. -- Atte. Félix Arreola Rodríguez, Firmado con GPG, llave 223D869A
Bug#513322: ITP: mupen64plus -- plugin-based N64 emulator
On Monday 01 June 2009 02:06:03 Felix Arreola Rodriguez wrote: > I wish talk English, too many documentation, I can't understand all... Sry when this is a little bit too harsh, but this any valid excuse if you want to create a debian package. As I said before: Try to get a co maintainer who can read english. Most stuff in debian is quite bureaucratic and you must read a lot of documentation. > > Your key seems not to be trusted by many people. You should think about > > creating a new one[1] and get some signatures by some debian developers. > > With that you can get a debian maintainer[2] and upload new versions of > > your packages by yourself. A good idea is to seperate the certification > > (main key) from the signatur key. You have currently both in your main > > key (see the SC in the usage by calling `gpg --edit-key 223D869A`). > > Ok, about my gpg key. I have some sign from my friends, but, I don't > understand waht you mean with "seperate the certification key". I'm some > new in the gpg world. The default is to create a master key which can be used to sign and certificate (aka create signatures on your key/other keys). You don't need to do that, but I just wanted to give a small hint. This has nothing todo with this package/ITP. > > Now to your package. Your tar.gz differs from the one I get from > > upstream. Never ever to that without calling your version 1.5+dfsg1-1 > > instead of 1.5-1 and provide a debian/prune-tarball.sh script. Don't > > forget to add information about what and why the package was manipulated. > > > > 3747bb55b8dce55afc585b1ccb557297 Mupen64Plus-1-5-src.tar > > 15f026b6658c7deda1385840d7376065 mupen64plus_1.5.orig.tar > > c224b045d343ff02f6f933d328861b01 Mupen64Plus-1-5-src.tar.gz > > 5c8aac7b0456e04099ba843bc4e484db mupen64plus_1.5.orig.tar.gz > > > > This alone is a reason to ignore your package and never look at it again. > > As it seems that you have not changed the files inside the package their > > is no reason to create a modified tar.gz. The only change is the name > > of the toplevel directory. Please don't do that. dpkg-source is > > intelligent enough to do that modification by itself when it unpacks the > > source package. So please use the tar.gz from upstream without any > > modifications if the source tar.gz doesn't violates the dfsg - otherwise > > create a dfsg clean version and rename your version number as told above. > > Rename Mupen64Plus-1-5-src.tar.gz to mupen64plus_1.5.orig.tar.gz and > > replace your old mupen64plus_1.5.orig.tar.gz with that one. Afterwards > > rebuild your package with `debuild -sa` and reupload it to mentors to > > override the tar.gz on mentors. This will not work when you uploaded it > > to the archives. > > > > `lsdiff -z mupen64plus_1.5-2.diff.gz` shows that you modified files > > outside of the debian directory. Don't to that. If you need to modify > > such files then use patches. A good idea is to use quilt[3] for that. > > > > Your debian directory is really messy. Please remove example files: > > $ rm debian/*.ex debian/*.EX > > Ok, all of this, i don't have idea. I'm talk spanish, and I'm trying to > understand this. I made too many mistakes, I know. Please don't argue with your mother-tongue. I never learnt english in school and it isn't my mother-tongue. If you have specific questions about something I said then please ask them. > > You don't close this bug with "Initial release (Closes: #513322)" in the > > first entry of your changelog. > > The package was made before I own the bug. I forget to change this. If you would have uploaded the package even without owning the bug then you would have "fixed" the bug without marking it as such. Please keep in mind to close bugs by writing their number in the changelog. The format should be: (Closes: #123456) for debian bugs (Closes LP: #123456) for bugs in ubuntu. Please also subscribe to the ubuntu bugtracker[1]. > > You tell that you build the gtk version of the packe but don't depend > > strictly on it - please remove the " | libqt4-dev" from the build > > depends. > > Oh, I was thinking in making 2 packages, One with the libgtk and another > with qt4, so, I think that I can use the same source. So, in this case, > I will make two sources seperate. Removed. If you wanted to do that you had to depend on both (without the | which would mean that you only need one of them and not both when building). > > Many useless dependencies. Fix the build scripts or read many things > > about -Wl,--as-needed (see dpkg-shlibdeps warnings). > > Useless dependencies? I will check this one. > > > You don't have a debian/watch file. Try: > > === > > version=3 > > > > opts="uversionmangle=s/-/./" \ > > http://code.google.com/p/mupen64plus/downloads/list \ > > http://mupen64plus.googlecode.com/files/Mupen64Plus-(.*).src\.tar.gz > > > > === > > and test it with `uscan --debug`. > > debian/watch? I don't even know
Bug#513322: ITP: mupen64plus -- plugin-based N64 emulator
I wish talk English, too many documentation, I can't understand all... signature.asc Description: Esta parte del mensaje está firmada digitalmente
Bug#513322: ITP: mupen64plus -- plugin-based N64 emulator
On Sunday 31 May 2009 22:38:44 Felix Arreola Rodriguez wrote: > Well, I have one package uploaded to mentors.debian.net > (http://mentors.debian.net/cgi-bin/maintainer-packages?action=details;packa >ge=mupen64plus). Please don't add a private link - we don't have access to your profile at mentors. Better would be a link to http://mentors.debian.net/debian/pool/non-free/m/mupen64plus/mupen64plus_1.5-2.dsc or and to http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=mupen64plus >But still I need work more time in it. This week I will > make a better package, I promise. Ok, the package seems to be pretty unclean. First thing is: if there are lintian warnings then don't upload it to mentors. Most mentors will look at them and run away screaming without looking at it further. Please read http://people.debian.org/~codehelp/#sponsor and the linked requirements of other sponsors. Your key seems not to be trusted by many people. You should think about creating a new one[1] and get some signatures by some debian developers. With that you can get a debian maintainer[2] and upload new versions of your packages by yourself. A good idea is to seperate the certification (main key) from the signatur key. You have currently both in your main key (see the SC in the usage by calling `gpg --edit-key 223D869A`). Now to your package. Your tar.gz differs from the one I get from upstream. Never ever to that without calling your version 1.5+dfsg1-1 instead of 1.5-1 and provide a debian/prune-tarball.sh script. Don't forget to add information about what and why the package was manipulated. 3747bb55b8dce55afc585b1ccb557297 Mupen64Plus-1-5-src.tar 15f026b6658c7deda1385840d7376065 mupen64plus_1.5.orig.tar c224b045d343ff02f6f933d328861b01 Mupen64Plus-1-5-src.tar.gz 5c8aac7b0456e04099ba843bc4e484db mupen64plus_1.5.orig.tar.gz This alone is a reason to ignore your package and never look at it again. As it seems that you have not changed the files inside the package their is no reason to create a modified tar.gz. The only change is the name of the toplevel directory. Please don't do that. dpkg-source is intelligent enough to do that modification by itself when it unpacks the source package. So please use the tar.gz from upstream without any modifications if the source tar.gz doesn't violates the dfsg - otherwise create a dfsg clean version and rename your version number as told above. Rename Mupen64Plus-1-5-src.tar.gz to mupen64plus_1.5.orig.tar.gz and replace your old mupen64plus_1.5.orig.tar.gz with that one. Afterwards rebuild your package with `debuild -sa` and reupload it to mentors to override the tar.gz on mentors. This will not work when you uploaded it to the archives. `lsdiff -z mupen64plus_1.5-2.diff.gz` shows that you modified files outside of the debian directory. Don't to that. If you need to modify such files then use patches. A good idea is to use quilt[3] for that. Your debian directory is really messy. Please remove example files: $ rm debian/*.ex debian/*.EX You don't close this bug with "Initial release (Closes: #513322)" in the first entry of your changelog. Nobody is interested that this is your first debian package - remove that from the changelog. All other entries for 1.5-1 are bogus since the really thing you did here was the initial release and you don't have other changes since the initial release - but keep that clean way of changelog entries for future versions. README.Debian is not a changelog. Don't use it for such things. You don't comply with 3.7.3 of the policy - please change read /usr/share/doc/debian-policy/policy.txt.gz and /usr/share/doc/debian-policy/upgrading-checklist.txt.gz and change the source package - don't forget the Standards-Version in debian/control. There is a typing error in the description of the binary package (M_U_lti) You tell that you build the gtk version of the packe but don't depend strictly on it - please remove the " | libqt4-dev" from the build depends. Many useless dependencies. Fix the build scripts or read many things about -Wl,--as-needed (see dpkg-shlibdeps warnings). You don't have a debian/watch file. Try: === version=3 opts="uversionmangle=s/-/./" \ http://code.google.com/p/mupen64plus/downloads/list \ http://mupen64plus.googlecode.com/files/Mupen64Plus-(.*).src\.tar.gz === and test it with `uscan --debug`. You use debhelper 7 and call `dh_clean -k`. Don't do that. It is not allowed anymore. Replace this call with `dh_prep` (without the -k). You are also removing top level directory stamp files with rm. Please don't do that either. dh_clean will do it for you. Plugins gets installed in /usr/share, Shouldn't they go to /usr/lib/mupen64plus (arch dependent files aren't allowed in /usr/share)? Why does it conflicts with mupen64(-bin)? I cannot find files which would conflict with it and I doubt that there are runtime conflicts. The /usr/share/mupen64plus/ i
Bug#513322: ITP: mupen64plus -- plugin-based N64 emulator
Well, I have one package uploaded to mentors.debian.net (http://mentors.debian.net/cgi-bin/maintainer-packages?action=details;package=mupen64plus). But still I need work more time in it. This week I will make a better package, I promise. Just one week. --- Atte. Félix Arreola Rodríguez, Firmado con GPG, llave 223D869A signature.asc Description: Esta parte del mensaje está firmada digitalmente
Bug#513322: ITP: mupen64plus -- plugin-based N64 emulator
fgatuno, any news on this? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513322: ITP: mupen64plus -- plugin-based N64 emulator
Package: wnpp Severity: wishlist Owner: William Pitcock * Package name: mupen64plus Version : 1.5 Upstream Author : "Blight" * URL : http://code.google.com/p/mupen64plus * License : GPLv2 Programming Lang: C/C++ Description : plugin-based N64 emulator Mupen64Plus is a plugin-based N64 emulator for Linux which is capable of accurately playing many games. Included are four MIPS R4300 CPU emulators, with dynamic recompilers for 32-bit x86 and 64-bit amd64 systems, and necessary plugins for audio, graphical rendering (RDP), signal co-processor (RSP), and input. -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
