@Steve:
Thanks for taking a look at this bug.
In my opinion the other upstream cherry picks are not needed to pass -s
to cryptsetup (I've been running with the first/original fix for several
months now without issue).
I believe the other cherry picks are a separate but very closely related
bug i
Discussion for the latter changes:
http://sourceforge.net/tracker/?func=detail&aid=2727353&group_id=41452&atid=430594
** Bug watch added: SourceForge.net Tracker #2727353
http://sourceforge.net/support/tracker.php?aid=2727353
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpa
Worth noting is two other commitdiffs from upstream that re-add support
for overriding the keysize (and then fixing the first patch) - the use-
case for this is given with an example keysize of 448:-
(Re-)Add support for overriding keysize:-
http://pam-mount.git.sourceforge.net/git/gitweb.cgi?p=
Could very well be, upstream used the constant HXSIZEOF_Z32, I merely
used the value of that constant in the created debdiff which was
-4294967296.
If indeed it is flawed here then it's arguably also flawed upstream so
please do consider reporting it there as well.
--
mount.crypt needs to pass -
@jcfp:
Strange, so if you run "mount.crypt" manually from the command line with
the attached patch it (mysteriously) passes through 104 instead of 448?
Can you paste the output of running the mount.crypt command with the -v
parameter? Just curious to see what's going on there since it works
absol
Solved...
We already carry a patch in debian/patches to fix this issue. The
submitter hasn't patched the files with this patch and so it fails.
The binary package *DOES* work, it only failed since I happened to be in
the CWD of the package so it pulled in the unpatched files from pitivi/
rather t
Just reproduced this on karmic. Both as described and after installing
the binary package.
** Changed in: pitivi (Ubuntu)
Status: New => Confirmed
--
pitivi crash after compilation from source under jaunty
https://bugs.launchpad.net/bugs/374948
You received this bug notification because y
I just failed to reproduce this on karmic, although karmic does have a
newer memcached version (1.2.8)
@fidian:
Can you provide the output of:-
$ find /etc -maxdepth 2 -name \*memcached\* -path \*rc?.d\*
and
$ cat /etc/default/memcached
Thanks!
--
Memcached not active after reboot on 64-bit
** Tags added: packaging patch
** Description changed:
libdkim-dev is not available in hardy since it was superseded by dkim-
milter which was subsequently deleted.
In intrepid and onwards this issue has been resolved by increasing the
epoch number in the package version and once I hav
Public bug reported:
libdkim-dev is not available in hardy since it was superseded by dkim-
milter which was subsequently deleted.
In intrepid and onwards this issue has been resolved by increasing the
epoch number in the package version and once I have this bug number I'll
add a debdiff which wi
Debdiff attached. I've also pushed the package for review/testing to my
lpbugs PPA.
** Attachment added: "LP375098.diff"
http://launchpadlibrarian.net/26600402/LP375098.diff
--
[hardy] libdkim-dev missing
https://bugs.launchpad.net/bugs/375098
You received this bug notification because you ar
** Tags added: patch
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpad.net/bugs/367577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/
Jaunty test package with the debdiff applied has now been submitted to
my PPA.
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpad.net/bugs/367577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Public bug reported:
mount.crypt needs to pass the -s option to cryptsetup or in some cases
mount.crypt fails to mount the encrypted volume. In my case this is
where I've used a keysize of 128 bits, but 256 is the default so unless
something tells cryptsetup the keysize is 128, it proceeds to assu
** Attachment added: "LP367577.patch"
http://launchpadlibrarian.net/26008536/LP367577.patch
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpad.net/bugs/367577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
@Jonathan:
Patch works for me, thanks.
This patch is worth it just for the Protocol= option IMO. :-)
If Matt Price confirms it works in Jaunty I'll create a debdiff and see
if we can get it sponsored into the ubuntu package, although I'm
guessing by now that'll be Karmic!
--
lcdproc needs patc
@Matt:
Well, I'd advise the adage of "if it ain't broke don't fix it" but if
you're feeling adventurous the jaunty packages should be pushed too
(jaunty-testing).
Let me/Jonathan know how you get on (I haven't even had time to test it
yet, I don't even have a jaunty machine here to check the repo
@Jonathan...
Thanks for that, I can confirm it compiles ok.
I'm not at home so I can't test this at the moment so if anyone is
feeling really brave I've pushed intrepid packages to my (personal) repo
@ packages.kennynet.co.uk (intrepid-testing).
I'll try to give it a test tonight / over the week
@Jonathan:
A week or so ago I downloaded what I believe is the latest patch, but
I'm having trouble compiling it.
Trying to build under intrepid/amd64 or intrepid/i386:-
if x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../..
@LIBUSB_CFLAGS@ @LIBFTDI_CFLAGS@ -fPIC -Wall -Wall -O3 -Wno
@Matt...
Yep, I have the same problem. We're going to have to defer to Jonathan
on this one.
I've tried using usbmon+debugfs to sniff the Windows driver sending
commands to the LCD during a shutdown under vmware... Unfortunately I
haven't had much time to spend on this so I don't have much to rep
@Matt:
Which patch are you using? (The 0.4 codeka patch works for me, I've yet
to try Jonathan's updated patch.)
Also, in LCDd.conf what does the Driver= line say? I'm assuming it says
imonlcd?
I'll try to get someone at home to power on my htpc machine so I can ssh
into it and pull the config a
Simple patch refresh against jaunty.
** Attachment added: "LP153185-jaunty.patch"
http://launchpadlibrarian.net/23590014/LP153185-jaunty.patch
--
lcdproc needs patch for the imon lcd
https://bugs.launchpad.net/bugs/153185
You received this bug notification because you are a member of Ubuntu
B
Debdiff for intrepid that adds the driver to the lcdproc package,
package submitted to my PPA for testing purposes (but as of time of
commenting, not yet built).
Most of the patch just adds files to build the imonlcd.so driver and so
should be contained and not effect any of the other drivers.
Ho
23 matches
Mail list logo
