[needs-packaging] yaffs2

Hi Michael,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 701679

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

YAFFS2 is GPL: http://www.yaffs.net/yaffs-licence-faqs
Code in git: git://www.aleph1.co.uk/yaffs2
Tarball of snapshot: http://aleph1.co.uk/gitweb?p=yaffs2/.git;a=snapshot;sf=tgz
Ubuntu Brainstorm idea from 2008: http://brainstorm.ubuntu.com/idea/11532/

In that sense the yaffs2utils need also packaging http://code.google.com/p/yaffs2utils/

This bug is missing log files that will aid in dianosing the problem. From a terminal window please run:

apport-collect 701679

and then change the status of the bug back to 'New'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

What do we need to do to get this bug going? I tried to do the 'apport-collect 701679' from comment #4 above, but I get guess the reporter of the bug needs to do it. Should I file a separate bug? And do we really need logs to diagnose the problem of this bug? ;)

[needs-packaging] goes to Ubuntu general task.

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist.