Bug#995467: Salvaging status

Can I pass the baton of mlton package ownership off to someone? I've been intending to some day come back to working on this, but the reality is, I probably never will. I'd be happy to answer questions about how to get things to work, if that is helpful. You need someone who either is currently o

Bug#904475: mlton: build-depends on the version of itself that is going to be built

On Tue, Jul 24, 2018 at 9:01 AM, Andreas Beckmann wrote: > Source: mlton > Version: 20180207-1 > Severity: serious > Justification: fails to build from source (but built successfully in the > past) > > now you got the package deadlocked w.r.t. their build-depends > Nah. This is a normal situatio

Bug#890791: Proposed updates?

Good evening, I was wondering where I can find the proposed-updates version of dpkg with the riscv64 architecture line added to /usr/share/dpkg/cputable. I thought I'd be able to find it on < https://release.debian.org/proposed-updates/stable.html>, but it's not listed, so I must be looking in the

Bug#890791: Progress?

Has there been any progress on this issue? I maintain a package with an explicit Architecture list and I wanted to port it to my new riscv64 system, but I can't upload the new source package to unstable because it mentions riscv64 in the control file. It's quite frustrating that backporting this t

Bug#857220: mlton-tools: broken symlink: /usr/share/doc/mlton-tools/README -> doc/README

Thanks for the report. I probably won't make a new upload to fix this issue alone, but will be sure to fix it with the next upload.

Bug#791928: Please support ARM64 (#error "Unknown CPU architecture")

Porting mlton is easy. I ported it to most of the debian archs already. All i need is a debian porterbox and buildd when i prepare a new upload. On Jul 9, 2015 6:00 PM, "Martin Michlmayr" wrote: > Package: st > Version: 1.9-3.1 > Severity: wishlist > User: debian-...@lists.debian.org > Usertags:

Bug#780981: avahi-daemon: Avahi-daemon loses name when used with dynamic IPv6

Package: avahi-daemon Version: 0.6.31-4+b2 Severity: important Dear Maintainer, FYI, This is clearly an upstream bug, but I could not figure out the upstream BTS. Since this affects jessie, I figure it also important to mention here. Please forward this bug upstream. So, here's the problem. Ever

Bug#685878: [Pkg-netatalk-devel] Netatalk 3?

On Mon, Nov 3, 2014 at 8:29 PM, Jonas Smedegaard wrote: > Hi Wesley, > Hey Jonas. Long time no see! > If you are only intrested in helping with Netatalk 3, then that's fine > too. Well, I personally need netatalk >= 3. Netatalk 2 doesn't do time machine properly. But I highly doubt that any

Bug#685878: Netatalk 3?

Hi, I've been using a self-built netatalk3 in debian for quite some time. I assume there is a good reason that debian/sid still has 2.2.2? If it's just manpower, I'd be happy to help with packaging. It would be a real pity if jessie ships with a 3-year-old netatalk.

Bug#725884: Me too!

Just wanted to mention this bug affects me as well. I have the same disks (WD30EZRX). As I found this bug report via google, it's not surprising we have the same hard disk, however. I can spin the disk down with 'hdparm -y /dev/sdd' and it stays spun down for hours. However, the disk will never sp

Bug#707410: mlton: FTBFS: gc/int-inf.c:180:43: error: unknown type name '__gmp_const'

Yes, I also have a patch, but the next MLton is due out shortly and it includes the patch. I am just waiting for the release. On Tue, Jun 25, 2013 at 6:53 PM, Sebastian Ramacher wrote: > Control: tags -1 + patch upstream fixed-upstream > Control: forwarded -1 https://github.com/MLton/mlton/issue

Bug#635004: buildd.debian.org: Mipsel blacklist for package MLton

Package: buildd.debian.org Severity: normal Good evening! The package 'MLton' needs a minimum of 1GB physical memory to compile. Otherwise it will thrash in swap until killed. The mips buildd recently tried to build this package on phrixos which only has 512MB. Naturally, this failed [1]. Please

Bug#619162: RM: mlton-cross -- ROM; Bad idea

Package: ftp.debian.org Severity: normal I had tried to support cross-compiling Standard ML with this package, but it needed to extract files from the main mlton package to achieve this effect, much like the evil ia32libs package. Since then, I've built a better solution that should work with Mu

Bug#603002: buildd.debian.org: Arm blacklist for package MLton

Package: buildd.debian.org Severity: normal Good afternoon. To compile my package, MLton, a buildd needs 1GB of physical memory (or else it will thrash swap so badly the build fails). Until recently, none of the arm buildd's met this requirement and thus I had to use qemu to build the binary pack

Bug#591174:

Where in the policy is it forbidden to download from the Internet? I actually looked for this before I packaged it: terps...@orange:/usr/share/doc/debian-policy$ zgrep -i internet policy.txt.gz MIME (Multipurpose Internet Mail Extensions, RFCs 2045-2049) is a terps...@orange:/usr/share/doc/de

Bug#552314: gcc 4.3.4 even worse

The 'use -fPIC' hack I've been using to avoid this problem doesn't help with the newest gcc in sid. < https://buildd.debian.org/fetch.cgi?pkg=mlton&arch=mips&ver=20100504~svn-r7459&stamp=1273006902&file=log&as=raw > gcc -std=gnu99 -c -I/usr/lib/mlton/targets/self/include \ -I/usr/

Bug#286917: [PATCH] fix endless loop in local queries

On Thu, Apr 29, 2010 at 4:33 PM, Thibaut VARENE wrote: > > 2) Firewall with no local IRC clients: works because ip_conntrack exists > and > > there's no need to check the local TCP connections. > > wrong, see below > Well, what I mean is that as long as the firewall doesn't have any connections

Bug#286917: [PATCH] fix endless loop in local queries

Drama aside, I'm glad someone finally figured this out. From what I understand these are the scenarios: 1) End-user system with no IP-forwarding: works because ip_conntrack doesn't exist 2) Firewall with no local IRC clients: works because ip_conntrack exists and there's no need to check the local

Bug#552314: Branch instructions still broken

reopen 552314 thanks Well, whatever was changed in the latest gcc makes gcc stop complaining that a branch is out of range. However, the problem is NOT fixed. Instead of the compiler aborting, it now creates broken object code that will segfault on whatever code previously triggered this behaviour

Bug#560623: mlton: FTBFS: compilation aborted: parseAndElaborate reported errors

On Fri, Dec 11, 2009 at 1:22 PM, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. > > > patch -s -p0 < smlnj-lib.patch > It seems the patch in debian/sid has changed in a way that is incompatible to the old one! Changing this to 'patch -s

Bug#559014: mlton should be a non-native Debian package

On Tue, Dec 1, 2009 at 8:24 AM, Daniel Moerner wrote: > I don't understand why you changed mlton to be a native Debian package in > version 20091015. The debian package scripts are kept in upstream subversion. So these svn snapshot "releases" corresponds 1-to-1 with the packaging scripts used for

Bug#554397: Please remove kfreebsd-* packages for bidentd

Package: ftp.debian.org Severity: normal The package bidentd is linux-specific. Though it compiles cleanly on other architectures, it will not work on them. Unfortunately, the buildds compiled bidentd for kfreebsd-* before I changed the package to test the architecture and fail on non-linux syste

Bug#552741: bidentd is linux specific

Package: buildd.debian.org The package bidentd is linux specific. It has inadvertently been built on kfreebsd and hurd. Those packages won't work. Please add bidentd to Packages-arch-specific. How can I get rid of the bad packages that already got built? -- System Information: Debian Release: 5.

Bug#551370: buildd.debian.org: update mlton in Packages-arch-specific

On Sun, Oct 18, 2009 at 8:50 PM, Philipp Kern wrote: > > I've been holding off on uploading the final, ported source package until > > the buildds are ready to run it. Until I upload, there are binaries in > > debian without corresponding source, which I imagine might offend some of > > the less

Bug#551370: buildd.debian.org: update mlton in Packages-arch-specific

Is any additional information needed from me for this to get done? I've been holding off on uploading the final, ported source package until the buildds are ready to run it. Until I upload, there are binaries in debian without corresponding source, which I imagine might offend some of the less pra

Bug#551470: Processes hang after signal handler return

Package: libc0.3 Version: 2.9-27 When using a sigaltstack, under some circumstances returning from a signal handler causes the process to block on a spinlock indefinitely. This problem is specific to Hurd. I've attached a small demonstration program. This is either a kernel or libc bug. The expec

Bug#551370: buildd.debian.org: update mlton in Packages-arch-specific

On Sun, Oct 18, 2009 at 2:23 PM, Philipp Kern wrote: > On Sat, Oct 17, 2009 at 09:30:52PM +0200, Wesley W. Terpstra (Debian) > wrote: > > - mlton: amd64 i386 hppa powerpc sparc ># Self-hosting ML compiler > > + mlton: alpha amd64 hppa i386 ia64 kfreebsd-i386 kfreebs

Bug#551370: Also add hurd-i386

Apparently, the hurd-i386 buildds should be able to manage MLton too. Please add it as well. Package: mlton Architecture: alpha amd64 hppa hurd-i386 i386 ia64 kfreebsd-i386 kfreebsd-amd64 mips mipsel powerpc s390 sparc

Bug#551370: buildd.debian.org: update mlton in Packages-arch-specific

Package: buildd.debian.org Severity: serious Justification: no longer builds from source - mlton: amd64 i386 hppa powerpc sparc# Self-hosting ML compiler + mlton: alpha amd64 hppa i386 ia64 kfreebsd-i386 kfreebsd-amd64 mips mipsel powerpc s390 sparc -- System Inf

Bug#220046: Won't fix #220046

tags 220046 +wontfix thanks I've taken over maintenance of this package. In my opinion this isn't a bug. It is normal for a compiler to depend on itself. Therefore I am marking this won't fix.

Bug#437858: [EMAIL PROTECTED]: Bug#437858: incorrect parsing for links in messages]

On Aug 24, 2007, at 2:46 PM, Wesley W. Terpstra wrote: I think I'll rewrite the parsing to actually follow RFC1738&822 Make that 3986 & 2822. PGP.sig Description: This is a digitally signed message part

Bug#437858: [EMAIL PROTECTED]: Bug#437858: incorrect parsing for links in messages]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 24, 2007, at 1:16 PM, Jonas Meurer wrote: How are you? Fine. What's up with you these days? Are you still in Darmstadt/Germany? Yes. Please see the bugreport against lurker below. I guess that the bug is in lurker-2.1/render/url.cpp,

Bug#417116: bidentd: Bug#417116: FTBFS with GCC 4.3: missing #includes

On Apr 1, 2007, at 6:06 PM, Martin Michlmayr wrote: g++ -O2 -fomit-frame-pointer -Wall -D_REENTRANT= -DVERSION=\"1.1.1 \" -c -o main.o main.cc main.cc: In function 'int Done(int)': main.cc:72: error: 'exit' was not declared in this scope make[1]: *** [main.o] Error 1 That's an amusing bug. :-

Bug#406394: new upstream release available

On Jan 10, 2007, at 9:36 PM, Steffen Joeris wrote: First of all I wish you a happy new year :) Cheers. You too. According to the upstream website[0] there is a new upstream release available. Please consider packaging it. That's odd. I never received an email notification to that effect. [

Bug#368899: Why one shouldn't add the apple extended attribute patch

Just a heads up: I think applying this patch would be a terrible idea: The apple patch modifies the rsync wire protocol in an incompatible way. Furthermore, it changes the meaning of '-E' (which means preserve executability) for yet more incompatibility. Much better would be for apple rsync to

Bug#389639: bidentd: purging the package fails (update-inetd unavailable)

On Sep 26, 2006, at 11:14 PM, Bill Allombert wrote: Package: bidentd Version: 1.0.10.dfsg-0.1 Severity: serious Hello Wesley, There is an error when attempting to purge bidentd: Removing bidentd ... Purging configuration files for bidentd ... /var/lib/dpkg/info/bidentd.postrm: line 15: up

Bug#369439: chgpasswd terminates after asking for a password

On May 29, 2006, at 9:10 PM, Jonas Meurer wrote: wesley, do you have a copy of the chgpasswd.c that you submitted to me? Oddly, no. I would've thought it would be saved in my sent mailbox, but I can't find it. I have the email where you asked me to write it, but not my reply. How annoying

Bug#369439: chgpasswd terminates after asking for a password

Found it. On May 30, 2006, at 12:24 AM, Wesley W. Terpstra wrote: On May 29, 2006, at 9:10 PM, Jonas Meurer wrote: wesley, do you have a copy of the chgpasswd.c that you submitted to me? Oddly, no. I would've thought it would be saved in my sent mailbox, but I can't find it.

Bug#333908: That's by design

Hi. Just wanted to let you know that REQUEST_URI is not supposed to be changed on rewrite. From the apache docs: REQUEST_URI The resource requested in the HTTP request line. (In the example above, this would be "/index.html".) The request line is not changed by rewrite, only redirec

Bug#324353: howto improve usbcrypto.mkinitrd

On Jan 22, 2006, at 6:40 PM, Jonas Meurer wrote: i've fixed the type in the shebang, and replaced /usr/local/bin/delay with /bin/sleep. but i'm not sure about how to replace xor. i even don't know what it does in the mkinitrd script. XOR takes two 32 byte (256 bit) files and bitwise XOR's th

Bug#305366: Please act on this soon

On Oct 19, 2005, at 4:47 AM, Henrique de Moraes Holschuh wrote: Please act on this bug very soon, or I will coordinate with Ubuntu and Michael, and upload a cryptsetup-luks package to superseed cryptsetup. This is Michael Pitt? Or someone else? When a LUKS cryptsetup is uploaded, I would like

Bug#327351: gcc-4.0: Gcc miscompiles libc on hppa - breaks rounding

On Sep 9, 2005, at 4:56 PM, Falk Hueffner wrote: Actually, I just noticed that sw[1] is probably also accessed. So you'd add it too. Then it should work.Actually, it's not touched between the two assembler instructions.

Bug#327351: gcc-4.0: Gcc miscompiles libc on hppa - breaks rounding

On Sep 9, 2005, at 3:46 PM, Falk Hueffner wrote:Add "m"(*sw) as constraint. Probably something like__asm__ ("fldd %0,%%fr0" : : "m"(*sw))The first asm would also be more efficiently expressed as:__asm__ ("fstd %%fr0,%0" : "=m"(*sw))unless these instruction have some unusual constraints such asrequi

Bug#327351: gcc-4.0: Gcc miscompiles libc on hppa - breaks rounding

retitle 327351 libc rounding is broken on HPPAreassign  327351 libc6tags 327351 +patchthanksOn Sep 9, 2005, at 3:25 PM, Wesley W. Terpstra wrote:On Sep 9, 2005, at 3:11 PM, Falk Hueffner wrote:"Wesley W. Terpstra" <[EMAIL PROTECTED]> writes:  __asm__ ("fstd %%fr0,0(%1)&qu

Bug#327351: gcc-4.0: Gcc miscompiles libc on hppa - breaks rounding

On Sep 9, 2005, at 3:11 PM, Falk Hueffner wrote:"Wesley W. Terpstra" <[EMAIL PROTECTED]> writes:  __asm__ ("fstd %%fr0,0(%1)" : "=m" (*sw) : "r" (sw));  sw[0] &= ~FE_DOWNWARD;  sw[0] |= round;  __asm__ ("fldd 0(%0),%%fr0" : : "r

Bug#327351: Testcase

Here's a small test-case: #include #include #include int cvt(float f) { return (int)rint(f); } int main() { printf("%d %d %d %d\n", cvt(23.7), cvt(23.23), cvt(-23.7), cvt(-23.23)); fesetround(FE_TONEAREST); printf("%d %d %d %d\n", cvt(23.7), cvt(23.23), cvt(-23.7),

Bug#327351: gcc-4.0: Gcc miscompiles libc on hppa - breaks rounding

Package: gcc-4.0 Version: 4.0.1-6 Severity: important When compiling the fesetround function (which controls the processor rounding mode), gcc-4.0 incorrectly optimizes away the code!!! Here's the C code in question: __asm__ ("fstd %%fr0,0(%1)" : "=m" (*sw) : "r" (sw)); sw[0] &= ~FE_DOWNWARD;

Bug#269329: Open-Xchange

Hi! Is there anything resembling a package for open-xchange? I have no interest in the licensing issues, and would be happy with a package that has sharp edges. -- Wesley W. Terpstra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Cont

Bug#290708: initrd-tools: dm-crypt devices initialized with wrong arguments for cryptsetup

s it's back. -- Wesley W. Terpstra <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#305829: MySQL does not support IPv6

Subject: MySQL does not support IPv6 Package: mysql-server Version: 4.0.24-2 Severity: wishlist AFAICT, there's no way to run mysql-server on a ipv6 port. There are some patches available here: ... but I can't vouch for them. Is there no IPv6 supp

Bug#304077: cryptsetup: need some way to specify not to prompt for passwords

ext2noauto,user,dmname=mnt 0 2 to his /etc/fstab, and then later runs simply: mount /mnt -- Wesley W. Terpstra <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#304399: clarification

; , and it does not." Ahhh. Now I finally understand what it is that you mean is broken. :-) I didn't understand the problem before, nor in your new bug report. However, now I get it. Thanks. -- Wesley W. Terpstra <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTE

Bug#303484: cryptsetup: invalid permission for created /tmp filesystem

On Wed, Apr 06, 2005 at 11:24:47PM +, Stefan Reuter wrote: > For /tmp to work properly its permissions must be set to 1777 Confirmed. :-) > The attached patch... will be applied with my next upload. Sorry for the slow response---I did get your first email. -- Wesley W. Terpstra

Bug#298944: -d/--key-file option fails to open file

et the raw key after mounting it with a passphrase and a hash function. Your keyfile must be at least 32 bytes for an AES256 bit key. (16 bytes for an AES128). Hope this helps! -- Wesley W. Terpstra <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#298944: -d/--key-file option fails to open file

nt between /dev/random and any other file as far as cryptsetup is programmed. -- Wesley W. Terpstra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291387: Resolution?

apb /dev/hdb2 /dev/urandomswap If it is prompting you for a password during the execution of the initrd (ie: prior to cryptdisks), then this is a different issue. -- Wesley W. Terpstra <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject o

Bug#286917: need help

tags 286917 +help +unreproducible +moreinfo severity 286917 normal thanks I can't reproduce this... I need a simpler test-case than installing exactly your mail server configuration. Since things still work for me, no matter what I try, I am downgrading this bug to 'normal'

Bug#290324: Mount support for dmcrypt

On Wed, Mar 09, 2005 at 01:14:16PM +0100, David Härdeman wrote: > Wesley W. Terpstra ([EMAIL PROTECTED]) wrote: > > On Wed, Mar 09, 2005 at 01:53:20AM +0100, David Härdeman wrote: > > > 1) Do you have time to create an updated patch? > > Sure. It turns out that the patch

Bug#258376: Bug#279529 acknowledged by developer ("Bug" is correct behaviour)

c notification regarding your Bug report > > #279529: create gives "invalid argument" if target device is already > > mounted, > > which was filed against the cryptsetup package. > > > > It has been closed by one of the developers, namely > > "W

Bug#290626: not a bug

tags 290626 +moreinfo retitle 290626 cryptsetup: new options 'check' and 'retry' thanks BTW, it is not a bug to leave VALUE unset in cryptdisks. Test it yourself; it works fine the way it is now. -- Wesley W. Terpstra <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email t

Bug#290626: Need a diff...

, reiserfs, and vfat automatically before falling back on a user-supplied CRYPTDISKS_CHECK. -- Wesley W. Terpstra <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#296464: initrd-tools: Asks for a password phrase for crypted disks with r andom keys

le configuration of swap when the crypttab specifies /dev/*random for the key or the 'swap' option. This breaks software suspend, but with a random key that's not possible anyways. -- Wesley W. Terpstra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#296464: initrd-tools: Asks for a password phrase for crypted disks with r andom keys

em runs > without swapspace. I don't understand what you mean here, could you clarify? -- Wesley W. Terpstra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#295342: ppp: IPv6 support disabled in debian PPP

On Tue, Feb 15, 2005 at 02:38:27PM +0100, Marco d'Itri wrote: > On Feb 15, "Wesley W. Terpstra" <[EMAIL PROTECTED]> wrote: > > The debian pppd was not compiled with IPv6 support. > What are you talking about? > IPv6 support is enabled in debian/rules and I reme

Bug#295342: ppp: IPv6 support disabled in debian PPP

Package: ppp Version: 2.4.2+20040428-6 Severity: normal The debian pppd was not compiled with IPv6 support. Simply change - #HAVE_INET6=y + HAVE_INET6=y in build-tree/ppp/pppd prior to compilation. Without this change, it is not possible to use native IPv6 access via PPPOE (as is provided by man

Bug#279529: create gives "invalid argument" if target device is alredy mounted

t your filesystem. It also seems illogical: If the block device is not encrypted, why are you using cryptsetup on it? If the block device is encrypted, how on earth are you running mount on it? -- Wesley W. Terpstra <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] wi

Bug#294130: [Lurker-users] RE: Bug#294130: README.mailman: Multiple databases should now be possible

he single private mailing list to appear in each private section. You need multiple databases, config files, and web cache directories. The 'include' option in the config file may prove useful. However, if you need a more elegent solution, you will need to wait for lurker 2.0 which will handle private lists properly (somehow). See the middle of this email for one potential method of acheiving this. -- Wesley W. Terpstra <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291500: Builds for me...?

n so I can reproduce this? -- Wesley W. Terpstra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291387: Re: Re: Bug#291387: password for c-swap at booting

Nein. =) Falsche lösung (meine Meinung nach). Man soll fragen, nur wenn es wirklich gebraucht ist, am sonst nicht. Mein furchtbares Deutsch tut mir leid. -- Wesley W. Terpstra

Bug#291362: installation-reports: LVM install failed due to missing dmsetup

On Thu, Jan 20, 2005 at 04:17:25PM -0500, Joey Hess wrote: > Great, so something like this? (Untested) Worked for me. -- Wesley W. Terpstra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291387: Re: Bug#291387: password for c-swap at booting

ausgeführt > werden. Das ist nicht möglich. Vor S35mountall.sh kann es passieren, dass /var/lib noch nicht gemountet ist, z.B. wenn man /var/lib auf einen anderen Festplatte hat. S35mountall.sh kann auch S28cryptdisk brauchen, um /var/lib zuentschlüßeln. Also, die Reihenfolge stimmt's schon. -- Wesley W. Terpstra

Bug#291362: installation-reports: LVM install failed due to missing dmsetup

ake last-minute changes > to d-i and debian-cd to add dmsetup everywhere. At any rate, I agree with your solution, if there is no dmsetup it makes sense to fall back to using lvm. Since cryptsetup depends on dmsetup, there is nothing wrong with this solution. -- Wesley W. Terpstra -- To

Bug#291387: password for c-swap at booting

creates /dev/random) starts after S28cryptdisks. Why does /dev/random need to be created? From what I see, S55urandom only seeds it. /dev/[u]random exists the moment /dev gets mounted afaik. -- Wesley W. Terpstra

Bug#290952: Should be run before cryptdisks

On Tue, Jan 18, 2005 at 02:00:24PM +0100, Marco d'Itri wrote: > On Jan 18, "Wesley W. Terpstra" <[EMAIL PROTECTED]> wrote: > > I propose: always add usbhib to the list of modules mkinitrd includes. > > I'm not certain whether this works w/o the usb host d

Bug#290952: Should be run before cryptdisks

this should be done in mkinitrd. Even if you aren't using cryptsetup, when the initial ram disk drops you into interactive mode (on failure), you need keyboard control. Right now, usb keyboard users just get screwed. =) I propose: always add usbhib to the list of modules mkinitrd includes. I&#x

Bug#290708: initrd-tools: dm-crypt devices initialized with wrong arguments for cryptsetup

x27; and call this from both /etc/init.d/cryptdisks and /usr/sbin/mkinitrd. This means I will need to upload a new cryptsetup and provide you a mkinitrd patch. Then initrd-tools will have to conflict with old versions of cryptsetup. -- Wesley W. Terpstra -- To UNSUBSCRIBE, email to [E

Bug#290324: Why this patch and not #268822

article quoted by #279002/#164144 is mostly FUD and when I'm done with the cryptsetup package, debian dmcrypt will not be vulnerable. -- Wesley W. Terpstra --- Begin Message --- Your mount patch in the link http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/34 is not appropriat

Bug#290324: mount: Mount support for dmcrypt

sally unique id library -- no debconf information #! /bin/sh /usr/share/dpatch/dpatch-run ## 20cryptsetup.dpatch by Wesley W. Terpstra <[EMAIL PROTECTED]> ## ## All lines beginning with ## DP:' are a description of the patch. ## DP: Add cryptsetup support for mounting dmcrypt'd block

Bug#289299: This is a bug in dmsetup

x27; This causes a big mess of error messages for systems using cryptsetup. -- Wesley W. Terpstra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#245282: Documented elsewhere

This is documented in the cryptsetup package. I don't think dmsetup needs to document these features since they are not very useful without the hash functions, etc. I would close this bug if I was maintainer. :-) -- Wesley W. Terpstra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] w

Bug#282144: Out of scope

se it when mount supports cryptsetup. Bye! -- Wesley W. Terpstra <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#281197: Wontfix

severity 281197 wishlist tags 281197 +wontfix thanks As I explained before, I think this is a bad idea. I will close this bug in a month or two if no one says anything more. -- Wesley W. Terpstra <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "