On Mon, Aug 27, 2012 at 3:52 PM, Frankie Onuonga wrote:

On Mon, Aug 27, 2012 at 3:40 PM, Greg Freemyer wrote:

...

On Mon, Aug 27, 2012 at 10:18 AM, Vincent Untz wrote:

...

Le lundi 27 août 2012, à 10:09 -0400, Greg Freemyer a écrit :

...

On Mon, Aug 27, 2012 at 8:01 AM, Vincent Untz wrote:

...

Hi,

ntfs-3g_ntfsprogs (living in the filesystems project) is the set of tools to interact with ntfs. It's the merge of ntfs-3g (user-space ntfs support) and ntfsprogs (mkntfs & friends).

For historical reasons, the GNOME team was assigned as maintainer of this package. When I moved the package to filesystems (since it didn't belong to GNOME:Factory), I became the maintainer. However, I have no use for it, and I don't even have anything in ntfs here.

Is there anyone who'd like to become the new maintainer of this package? The main work is really just to update it to new upstream versions. Upstream is doing a good job at providing something rather solid.

Thanks,

Vincent

You can give it to me if no one else wants it. OBS userid: gregfreemyer

I have 2 or 3 things in filesystems and I use ntfs-3g in my day job.

Thanks for stepping up! I've done the change in OBS.

If others want to step up, I'm sure that Greg wouldn't mind co-maintainers, so raise your voice :-)

Cheers,

Vincent

Co-maintainers are very welcome. I've been trying to focus on security apps to maintain, but my knowledge of filesystems makes this a fit as well.

Greg --

Hi Greg, I would love to assist if you dont mind.

thanks.

Frankie, What's your OBS userid? If it's onuonga, it looks like you're new to OBS packaging. == assuming you're new to OBS from here down, ignore otherwise == I suggest that until you get your feet under you before you become a maintainer, please submit SR's but let me accept them. If you don't know how OBS works, you can branch any project to your home project then update it and issue a SR back to the original project. Then the maintainer of that project can accept the SR or reject it. You don't have to be a maintainer to do that. You want to avoid branching Factory or one of the actual releases unless you know what you are doing. More typically, you would find the Factory version of a package, then from it find the devel version that is derived from it and branch that devel version to your home project. If you create a bug fix you then submit it to the devel version. The maintainer will review it and forward it to factory if they feel it is appropriate. If you want some practice and you have any C programming background, I have a project in my home project that needs a small patch to let it complete the build. Sending me a SR with the fix would be handy. And I can walk you through the process if you want. The project is: home:gregfreemyer:Tools-for-forensic-boot-cd And the package is: logsurfer Go ahead and branch that to your home project.and build it on your local computer. You can follow these basic steps to make that happen: (Be sure to read down to "Here's a real example: ") http://en.opensuse.org/Build_Service_Tutorial#A_start_to_end_example_of_a_si... Just use the above project and package instead of the ones in the tutorial. Then create a new patch with a name like "fix-compile-errors.patch". (See tutorial for how to do that.) The use quilt edit <sourcefile> to edit the file with the compile errors. Then follow the tutorial for how to update the patch and the specfile to apply it and do another local build. Once you have it working and committed back to your branched copy of the project, send me an SR with the new patch and the updated specfile. Feel free to ask me questions as you go along. And to fix that wiki page tutorial as well. I'm not in a super hurry to get logsurfer compiling, so I can hold-off fixing it until you've given it a shot. Let me know if you are going to try. Once we get it done, I plan to send logsurfer to security as update/rename of logsurfer+. From there I think I'll send it to factory, but I haven't decided yet. For now logsurfer+ lives only in security. Good Luck Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org