Here's the binary for i386: ftp://sources.redhat.com/pub/jffs2/mkfs.jffs2

I searched with urpmq & I could only find jfsutils which isn't the same at all.

According to the page it has been added to official kernel since 2.4-version

Why isn't it present?

(In reply to comment #4)
> Why isn't it present?

for the utils, simply because no-one have requested or imported it...

kernel has supported jffs2 (and had it enabled) for ages.

I have imported mtd-utils 1.4.4 to cauldron now, and will push to stable tree as soon as we decide where missing packages belong.

Status: NEW => ASSIGNED
CC: (none) => tmb
Assignee: bugsquad => tmb

(In reply to comment #5)
> 
> I have imported mtd-utils 1.4.4 to cauldron now, and will push to stable tree
> as soon as we decide where missing packages belong.

As all the other packages which were present in Mdv, but didn't get added before Mga 1 was out, it should go to core_updates after going through QA:
http://mageia.org/wiki/doku.php?id=updates_policy#version_policy

CC: (none) => doktor5000

(In reply to comment #6)
> 
> As all the other packages which were present in Mdv, but didn't get added
> before Mga 1 was out, it should go to core_updates after going through QA:
> http://mageia.org/wiki/doku.php?id=updates_policy#version_policy


Indeed, so here is the update request:

there is now a mtd-utils-1.4.6-0.1.mga1 available in core/updates_testing


Advisory:
---------

This update provides mtd-utils, wich are available in mdv 2010.1/2,
but missing in Mageia 1

Assignee: tmb => qa-bugs
Summary: Please add jffs2 as filesystem to kernel => Update request: mtd-utils
Source RPM: jffs2-utils => mtd-utils
Severity: enhancement => normal

Sorry, seems this got drowned on my TODO list,
thanks for providing the advisory, Thomas :)

Kristoffer are you able to test this please?

If not then could you leave instructions for QA how best to test this is working properly. Thankyou.

Does anyone have an mtd flash device they can use for testing this?
ftp://ftp.linux.org.uk/pub/people/dwmw2/mtd/cvs/mtd/mtd-jffs-HOWTO.txt
describes the procedure for working with jffs2.

All of my sdram cards and usb flash devices are detected as block devices, not
mtd devices, so I can't test the utility.

CC: (none) => davidwhodgins

We seem to be stuck with this update, not having correct hardware to test it with.

How come?

What do you mean? When the QA team doesn't have the proper hardware to test an update, it can't be validated. As you wanted this package, shouldn't you be able to test it and report if it works properly?

If you wish to donate such a device to QA we would be more than willing to accept it for future testing purposes. Alternately please consider joining the QA team and adding your resources :)

If you don't wish to do either then please test this updated package, as QA are currently unable to beyond checking that the package installs correctly.

Thankyou Kristoffer.

Kristoffer do you still have the hardware to test this with? 

If so could you please check this package works as it should do so that we can validate the update and move it from testing to updates.
Thankyou.

I do have the hardware, but don't really know how to use it properly yet. I do know that I need it to do the things I want.

IINM this is for extracting firmware from the device, right?

Kristoffer, you were the one who asked for this to be imported into Mageia.

(In reply to comment #17)
> Kristoffer, you were the one who asked for this to be imported into Mageia.

Your point?

I tend to use it as soon as I can figure out how to attach adb to my tablet.

I also intend to use it later on when I've bought a better tablet.

The point is that _you_ reported it missing, assuming that you actually need it / knows how to use it.

QA cant validate an update "just because it existed in mdv"

Thomas Backlund: Well, can you tell me an existing tool in Mageia that works the same then?

We already have mtd-utils in updates_testing waiting for validation.


but it _must_ be _tested_ before QA can sign off on it and we can push it to updates.

I WILL test it. Not really sure WHEN or HOW, but I'll read the help-part for it.

Is there any progress with this please Kristoffer?

(In reply to comment #24)
> Is there any progress with this please Kristoffer?

No, not now.

Is there a problem in testing this Kristoffer?

Nobody else has requested this package. Should it be dropped perhaps?

Suggest this package is dropped as it is obviously no longer required by requester and QA is unable to test.

QA is unable to test this with current hardware.

Package requester is unwilling to test and no longer needs it.

Suggest either push this untested or remove from the repo's.

I'd sooner remove it until somebody requests it who intends to use it and will be willing to test it.

Package dropped

Status: ASSIGNED => RESOLVED
Resolution: (none) => WONTFIX