Description of problem: Foremost is a console program to recover files based on their headers, footers, and internal data structures. Foremost can work on image files, such as those generated by dd, Safeback, Encase, etc, or directly on a drive. http://sourceforge.net/projects/foremost/ needed for bug 772 Reproducible: Steps to Reproduce:
Severity: normal => enhancement
CC: (none) => miscDepends on: (none) => 772Summary: missing package: foremost => foremost, a tool for forensic examination on partitions
foremost available in cauldron. I will push it to Mageia 1 ASAP.
Status: NEW => ASSIGNEDCC: (none) => mageiaAssignee: bugsquad => mageia
Thanks, I will look on the package soon
Depends on: 772 => (none)
Blocks: (none) => 772
Package pushed in backports_testing. Please test it and I will push it to backports_updates.
Install and test with cauldron is ok
Thank you, can you also test the package in testing for Mageia 1 please?
I'm running :-)
install ok, test ok. Thanks
I've tested in on an i586 system. If it has been tested on a 64 bit system, the package foremost is ready to move from Core Backports Testing to Core Backports
CC: (none) => davidwhodginsAssignee: mageia => qa-bugs
I have used a 64 bit system for my tests.
Ok, can someone on the sysadmin team move foremost from Core Backports Testing to Core Backports, or update http://mageia.org/wiki/doku.php?id=qa_updates with an explanation of how qa team members can move packages.
Foremost was available in Mandriva 2010.2, so it's fits in the exceptions for Mageia 1 updates. I pushed foremost-1.5.7-3.mga1, an update candidate for Mageia 1, to core/updates_testing. Please uninstall the package from backports_testing, install the package from updates_testing and test it again (the package should be the same than in backports_testing, but it's the policy) Advisory : This update adds foremost, a file recovery tool, which was present in Mandriva 2010.2 but missing from Mageia 1.
CC: (none) => stormi
Testing of the program foremost from the srpm foremost-1.5.7-3.mga1.src.rpm from Core Updates testing complete on i586. I used "foremost -qvi /dev/sda1" which output the files into directories in the output subdirectoy of the current directory. sda1 is a vfat partition on my system.
this package still needs a test in x86_64
I will test on x86_64
CC: (none) => eeeemail
Foremost installed and tested OK on x86_64 foremost -qvi /dev/sdb where sdb was a USB stick retrieved all manner of files and sorted them into directories. This should now be ready to push from core/updates_testing into core/updates with the advisory in comment #11
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Hello, *Strange: with the command "# urpmi foremost", the package is present in the media Core_Updates_Testing, and is was good installed Against by the MCC, it can not find the package ,in the Search box, I type "foremost" and there is no package. [root@david ~]# urpmi foremost $MIRRORLIST: media/core/updates_testing/foremost-1.5.7-3.mga1.x86_64.rpm installation de foremost-1.5.7-3.mga1.x86_64.rpm depuis /var/cache/urpmi/rpms Préparation ... ############################################# 1/1: foremost ############################################# [root@david ~]# *I attached a screenshot for MCC. *Otherwise, installed successfully and tested on Mageia release 1 (Official) for x86_64. (In reply to comment #12) > I used "foremost -qvi /dev/sda1" which output the files into directories in the > output subdirectoy of the current directory. sda1 is a vfat partition on my > system. Exactly the same and sda1 is also a partition vfat. *I have nothing to declare, no problem,it's OK for me.
CC: (none) => geiger.david68210
Created attachment 710 [details] screenshot MCC with "foremost"
Now you mention it, I also had to install it that way. It had slipped my mind.
It won't show up in rpmdrake if the Core Updates Testing repository is not enabled, but can still be installed using urpmi. That is normal. The srpm foremost-1.5.7-3.mga1.src.rpm is ready to push from Core Updates Testing to Core Updates with the advisory: This update adds foremost, a file recovery tool, which was present in Mandriva 2010.2 but missing from Mageia 1.
I think that the fact that the same version of the package is present in backports_testing and updates_testing could be a cause of the absence from rpmdrake, which would be confused by that (note that you can see it if you select "backports" in the first select box). But that's just a guess. However, this update remains validated and ready to be pushed, as said in comment #15 Please also remove foremost from backports_testing.
Version: Cauldron => 1
(In reply to comment #20) > I think that the fact that the same version of the package is present in > backports_testing and updates_testing could be a cause of the absence from > rpmdrake, which would be confused by that (note that you can see it if you > select "backports" in the first select box). But that's just a guess. Additional info: I did not activate the media Backports. Here, those who are enabled: le média « Core Release (distrib1) » est à jour le média « Core Updates (distrib3) » est à jour le média « Core Updates Testing (distrib5) » est à jour le média « Nonfree Release (distrib11) » est à jour le média « Nonfree Updates (distrib13) » est à jour le média « Nonfree Updates Testing (distrib15) » est à jour le média « Tainted Release (distrib21) » est à jour le média « Tainted Updates (distrib23) » est à jour le média « Tainted Updates Testing (distrib25) » est à jour le média « Core 32bit Release (distrib31) » est à jour le média « Core 32bit Updates (distrib33) » est à jour le média « Core 32bit Updates Testing (distrib35) » est à jour Just a guess: Would it not be a problem refresh or synchronization on the mirror Core_Updates_Testing? when adding the package in the mirror. ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/1/x86_64/media/core/updates_testing/
I too did not have backports enabled, just standard mirrorlist and core/updates_testing from mageia.supp.name I can't say whether I updated all repo's or not so it may have been listed under backports_testing even with it disabled, causing the conflict. It appeared to operate normally once installed anyway.
pushed to updates.
Status: ASSIGNED => RESOLVEDCC: (none) => boklmResolution: (none) => FIXED
Could someone from the sysadmin team remove foremost from Core Backports Testing. The current version is in Core Updates.
(see also my bug 2940)
CC: boklm => (none)