First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 44079
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo's Team for Core System packages <base-system@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Justin Whitney <ripple@ripple.be>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
cryptsetup-0.1.ebuild.tar.bz2 cryptsetup-0.1 ebuild (sys-apps/) application/octet-stream Justin Whitney 2004-03-08 17:20 0000 1.19 KB Details
cryptsetup-0.2_pre1.ebuild 0.2-pre1 ebuild text/plain Justin Whitney 2004-03-10 01:22 0000 1.23 KB Details
cryptsetup-0.1-r1.ebuild cryptsetup-0.1-r1.ebuild text/plain Benjamin Smee (strerror) (RETIRED) 2004-06-01 12:19 0000 1.15 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 44079 depends on: 43146 Show dependency tree
Bug 44079 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2004-03-08 16:27 0000
This was originally "no dm-crypt ebuild"
(http://bugs.gentoo.org/show_bug.cgi?id=43146)

I have broken off cryptsetup (the tool used for setting up dm-crypt devices,
from the dm-crypt ebuild, and put it in its own ebuild (here).

note that this DOES NOT OBSOLETE the previous bug.  It complements it.

This is needed for the following reason.  the dm-crypt ebuild contains the .rc
and .conf files, and should eventually get integrated with baselayout or
similar (just  as crypto-loop is).  The cryptsetup ebuild should be allowed to
evolve independent from the gentoo-specific stuff.

cryptsetup-0.1.ebuild to follow.

------- Comment #1 From Justin Whitney 2004-03-08 17:20:06 0000 -------
Created an attachment (id=27066) [edit]
cryptsetup-0.1 ebuild (sys-apps/)

------- Comment #2 From Justin Whitney 2004-03-08 17:25:22 0000 -------
changed license to GPL-2 and marked ~x86.  Will leave as is till next version
bump.

------- Comment #3 From Justin Whitney 2004-03-10 01:22:58 0000 -------
Created an attachment (id=27143) [edit]
0.2-pre1 ebuild

cryptsetup-0.2-pre1 ebuild.

static cryptsetup binary installed to /sbin (Thanks Mathieu Segaud)

NOTE: must have libdevmapper.a from device-mapper ebuild.  this does NOT
install by default.  I have submitted this as bug 44223.  to make use of this
ebuild (while the device-mapper ebuild remains unchanged), copy
lib/ioctl/libdevmapper.a out of the device-mapper build dir.  sorry hope this
changes quite soon.

everything else installed to /usr including dynamic libs.

------- Comment #4 From David Schauer-West 2004-03-17 18:29:12 0000 -------
Justin,

>=sys-kernel/linux-headers-2.6.1 is no longer required for cryptsetup (there are some #ifdef BLKGETSIZE64 sections in setup.c now). Also, the device-mapper ebuild now puts libdevmapper.a in /usr/lib automatically.

------- Comment #5 From Benjamin Smee (strerror) (RETIRED) 2004-06-01 12:19:20 0000 -------
Created an attachment (id=32485) [edit]
cryptsetup-0.1-r1.ebuild

new ebuild for cryptsetup.minor cleanup

------- Comment #6 From Sven Wegener 2004-06-21 18:35:49 0000 -------
*** Bug 54663 has been marked as a duplicate of this bug. ***

------- Comment #7 From Bernd Wurst 2004-07-20 01:34:35 0000 -------
What's up to this bug? I just can't find a cryptsetup ebuild in portage
(neither masked nor unmasked).

It's really annoying to read several docus and all want me to manually download
and compile cryptsetup. That's not why I'm using portage, isn't it. :-(

------- Comment #8 From rob holland (RETIRED) 2004-07-21 05:44:56 0000 -------
I've commited an ebuild to cvs for cryptsetup-0.1. Please open a new bug for
the pre version when its actually listed on Christophe's site. I don't think
its worth putting in portage until he starts advertising it there.

Thanks for the submitted ebuilds but I prefered other ways of doing things. If
my ebuild is in error in any way, please let me know.

First Last Prev Next    No search results available      Search page      Enter new bug