howdy,
i just tagged a new release of pwdsphinx at
https://github.com/stef/pwdsphinx/releases/tag/v1.99.3-beta
please not that this also depends on a new release of liboprf at
https://github.com/stef/liboprf/releases/tag/v0.6.0
thanks for your kind support!
s
ohio,
i think i got it. thanks to your kind vm contribution Santiago! <3
i put some extra debug output in the code, which showed me that there was
files in the state (stored under /tmp/sphinx-oracle-root.*) that should not
exist. this state is deleted recursively between test cases. and the error
howdy,
i'm upstream.
i regret to say that i cannot reproduce this.
- i clone https://salsa.debian.org/debian/pwdsphinx
- checkout debian/1.99.2-beta-5 and,
- run sbuild on it,
- it all succeeds.
what am i doing wrong?
btw the error it fails on, sounds like the test case for some reason
hey,
i downloaded a riscv64 image from https://people.debian.org/~gio/dqib/ and
then more or less manually executed the steps here:
https://buildd.debian.org/status/fetch.php?pkg=liboprf&arch=riscv64&ver=0.4.0-1&stamp=1727600437&raw=0
(without the fakeroot param in dpkg-buildpackage)
and then t
hey,
i figured it out, the problem is that in src/makefile CFLAGS is only set if no
CFLAGS is passed, and that contains the essential -fpic switch. adding a
simple
CFLAGS+= -fpic
solves the problem for both ppc64 and the hppa archs'
will, submit a fix on salsa asap.
cheers,s
ey try to allocate the memory for all the
state needed during the rest of the protocol. so somewhere here:
https://github.com/stef/liboprf/blob/master/src/tests/tp-dkg.c#L426-L465
and this is all stuff were (a lot) memory is allocated on the stack. and
normally if you allocate too much, you get a
Dear Gui-Ye, Joost,
i added your fixes to upstream (being myself the upstream dev)
https://github.com/stef/liboprf/commit/8129a40faeda9c0457317c3a039c783d57dd4fb6
however i find it curious, that on riscv the test
`ulimit -s 66000; ./tp-dkg-corrupt 3 2 `
segfaults, whil the other
`ulimit -s
On Thu, Aug 08, 2024 at 07:24:06PM +0200, Joost van Baal-Ilić wrote:
> Hi again stef,
>
> On Thu, Aug 08, 2024 at 12:21:10PM +0200, Joost van Baal-Ilić wrote:
> > On Thu, Aug 08, 2024 at 12:06:44PM +0200, stef wrote:
> > > On Thu, Aug 08, 2024 at 07:08:13AM +0200, J
On Thu, Aug 08, 2024 at 07:08:13AM +0200, Joost van Baal-Ilić wrote:
> Hi stef,
>
> I just found out https://pypi.org/project/pysodium/#files lacks a
> pysodium-0.7.18.tar.gz.asc . (It's not published on
> https://github.com/stef/pysodium/releases either.) (You did s
On Thu, Aug 08, 2024 at 07:08:13AM +0200, Joost van Baal-Ilić wrote:
> Hi stef,
>
> I just found out https://pypi.org/project/pysodium/#files lacks a
> pysodium-0.7.18.tar.gz.asc . (It's not published on
pypi does not publish signatures anymore, i did sign it, but pypi ignores
howdy,
(pysodium upstream here)
i just checked it, the culprit is, that back in the days i published 0.7.0 as
0.7.0-0 on pypi. none of the newer version have that -0 postfix, so any later
version should be ok. of course the best would be the latest, 0.7.18.
howdy,
(pysodium upstream here)
i'm a bit confused, 0.7.0 is packaged according to the build log, and it is
called 0.7.0_0 - i have no idea where the _0 postfix comes from.
nota bene pysodium is already are at 0.7.18 and according to
https://pypi.debian.net/pysodium/ there is awareness of a newe
Package: usrmerge
Version: 38
Severity: important
howdy,
trying to update a debian unstable system, and it breaks due to usrmerge.
Preparing to unpack .../archives/usrmerge_38_all.deb ...
/usr is a standalone filesystem, this requires using an initramfs.
dpkg: error processing archive /var/cache
Package: V11.7.0
Boot method: RESEAU
Image version: ONLINE
Date: 20/05/2023 8H37
Machine: SIEMENS 6ES7647-8BD31-0CA1 (SIMATIC IPC227E (Nanobox PC); 1x display
port; 2x 10/100/1000 Mbit/s Ethernet RJ45; 1 x USB3.0, 3 x USB2.0; CFast slot;
24 V DC industrial power supply Celeron N2930 (4C/4
Hi,
I have the same problem.
It's easy to replicate.
Make a /tmp/test1 and /tmp/test2 directory. Touch a file in both
directories and run kdiff3 to compare both directories.
You will get the error 'Opening /tmp/test1/test failed. No such file or
directory.'
Stef
ithub.com/cockpit-project/cockpit/issues/5340
Stef
On 07.11.2016 16:44, Tianon Gravi wrote:
> On 7 November 2016 at 05:34, Stef Walter wrote:
>> The docker package is unfortunately currently broken. It fails to run
>> containers and instead produces the following message:
>>
>> rpc error: code = 2 desc = "oci runt
Package: docker.io
Version: 1.11.2~ds1-6
Severity: grave
Justification: renders package unusable
The docker package is unfortunately currently broken. It fails to run
containers and instead produces the following message:
rpc error: code = 2 desc = "oci runtime error: could not synchronise with
t;>> gpg-agent (e.g. those who don't have smartcards, don't use gpgsm, and
>>> who otherwise ignore the concerns Werner has raised about
>>> gnome-keyring's incomplete gpg-agent support) would be unable to do so.
>>>
>>> It's a more inva
On Fri, Aug 22, 2014 at 02:39:15PM +0200, Matthias Klose wrote:
> Control: severity -1 important
>
> > when using grsecurity/pax protections
>
> so nothing is broken for a default install.
true. but the default install maybe also needs a bugreport for lack of grsec
protection. ;)
> > patch shou
On 16.08.2014 11:35, Martin-Éric Racine wrote:
> Hey Stef!,
>
> As reported at GNOME Bugzilla – Bug 711222 [1] there are some serious
> issues with gnome-keyring that have resulted in the package being
> marked as unfit for release. As you seem to be the main contributor to
> t
i just downgraded libffi6:i386 3.1-2 -> 3.1~rc1+r3.0.13-12
and all seems to be working again. since the patch is against 3.0.12 i suppose
it might not be the solution to this problem, will investigate further.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject o
Package: libffi6
Version: 3.1-2
Severity: critical
Tags: security patch
Justification: breaks the whole system
when using grsecurity/pax protections on debian unstable, the newest libffi6
breaks almost everything.
some examples:
> # emacs
> emacs: error while loading shared libraries: libffi.so.6
Package: fonts-crosextra-carlito
Severity: wishlist
Dear Maintainer,
Would it be possible to backport fonts-crosextra-carlito and fonts-crosextra-
caladea from jessie to wheezy-backports?
Thanks StefCT
-- System Information:
Debian Release: 7.0
APT prefers stable-updates
APT policy: (500,
Package: dpkg
Version: 1.16.10
Severity: wishlist
Dear Maintainer,
In dpkg-reconfigure locales the user can press the space bar to toggle the
locale under the cursor. However, this info is not provided by the user
interface. Personally I had a rather hard time figuring out how to select more
than
Package: opensc
Version: 0.12.2-3
Severity: wishlist
Tags: upstream
A new was released on 04.12.2012.
thanks for packaging!
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (x86_64)
Kernel: Linux 3.7.7-grsec (SMP w/2 CPU cores)
I confirm the bug on my laptop, equipped with AR9285 (module ath9k)
wireless chip.
the laptop (samsung N220 netbook) has a fairly clean debian testing
installation,
after kernel upgrade from 3.1.0-1-686-pae to 3.2.0-1-686-pae connection to
a wifi router with WEP encryption (*) does not work anymor
bug is no longer triggered
on gcc 4.6.1
How does that sound? Acceptable?
Cheers,
Stef
On 12/14/2011 07:08 PM, Andreas Metzler wrote:
> On 2011-12-14 Stef Walter wrote:
>> On 2011-12-10 11:06, Andreas Metzler wrote:
> [...]
>>> The minimal change I found was to just
Package: fusecompress
Version: 2.6.4
Followup-For: Bug #629874
for those people, how find this via google, here's a workaround, even if the
pkg is discontinued in debian:
i have tracked down the problem to libboost_serialization1. if i compile with
1.42 (or install from snapshot.debian.org i'm ab
Package: fusecompress
Version: 2.6.git913897f4-1
Followup-For: Bug #629874
when accessing files on a mounted fusecompress volume, syslog is splattered
with:
FuseCompress: int Compress::open(const char*, int): Failed to restore LayerMap
of file 'testfile:2,RS', exception: requested integer size e
Right here is the diagnostic of why it fails:
Compiled the stuff with CFLAGS=-g to trace the execution. Here is my diagnostic:
run -B . -N locale -E UTF-8 -Epathname 1:1 -Emisc 1:1 -norc -m 2MW -lp
-x '(and (load "init.lisp") (sys::%saveinitmem) (ext::exit))
(ext::exit t)'
Starting program: /hom
triggers for man-db ...
Errors were encountered while processing:
clisp
#
Any idea? Something to try in order to help?
2010/9/27 Peter Van Eynde :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello Stef,
>
> On 22/09/10 21:53, stef louise wrote:
>> I may have some tim
Stéphane
2010/9/17 Peter Van Eynde :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello Stef,
>
> On 16/09/10 21:57, stef louise wrote:
>> /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp
>> *** - handle_fault error2 ! add
debugging to identify where
> precisely this script fails?
>
> [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
> Never abandon a theory that explains something until you have a theory that
> explains more. — John McCarthy
>
>
>
> On 16 Sept
Hi,
This bug seems quite quiet for a grave bug (the update manager refuse
to work since then).
I tried to use dpkg which seems to give more accurate messages for
common-lisp installation:
# LANG=C dpkg -i /var/cache/apt/archives/common-lisp-controller_7.4_all.deb
(Reading database ... 196004 file
OK, Sorry: bad copy of bug number... :/
I wanted to address bug #550562
You can erase my previous message.
Sorry again and thank you.
Stéphane
Hi,
I am a mostly happy owner of (among others) a last model of the Mac Mini -
PowerPC edition. These beasts came with a G4 MPC 7447a at 1.5GHz and a AGP
Radeon 7250 (R280).
I experienced the bug about the same time as Jean-Luc, it got better a
little while, but really soon it was deadly again : n
OK, sorry about that.
I tried to disassemble the code and follow it a little, but one thing is
clear : the level at which the blocking occurs is not the deepest one. It is
too tricky for me to follow at assembly level though, as I am not yet fluent
in PPC assembly.
Moreover, each time I interrupt t
Hi,
I can confirm this bug on PowerPC. When trying to play a song, the processor
use raise to 100% and Rhythmbox stalls. It looks like the usual "let's
assume all char on every plateform are signed char and let's do loops
carelessfully" kind of bug, but I may be wrong.
I tried to make a backtrack
Get better action from her every night
Make your rod stronger and more powerful than ever http://www.bejuiela.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: wnpp
Severity: wishlist
* Package name: funionfs
Version : 0.4.2
Upstream Author : Stephane APIOU <[EMAIL PROTECTED]>
* URL : http://funionfs.apiou.org/
* License : GPL
Programming Lang: C
Description : An Overlay or Union filesystem for FUSE
tter stands for).
>
> So, I would also second "Amateur radio"...
I too feel "Amateur Radio" Would be the preferred Menu item.. rather
than "Ham".
--
Regards - Stef VK5HSX
Adelaide, Sth Australia
-= Use Open Source Software =-
Hi.
I could not run that program due to a segfault in the call to
getgrouplist. After googling a little, I changed the 'compat' settings
in /etc/nsswitch.conf to 'files nis' and all went well. Now dbus is up
and running (and I gotta figure out how to make it do what I want, but
that's anothing thi
On Sun, Jan 16, 2005 at 07:03:30PM +0100, Sjoerd Simons wrote:
> The socket opening stuff is something your nisbindings do, not a dbus thing.
> Could you trace the daemon with ltrace and provide the last part of the
> output.
Ok, thanks for the quick reply, here goes:
memmove(0x809bc9d, 0x809bc9
Hi,
I'm getting a segfault too, rendering dbus useless. Any time a client
connects to it, it segfaults. I didn't manage to get a core dump even
when starting it myself with 'ulimit -c unlimited'.
However I've got some info. When I run the command
DBUS_VERBOSE=1 dbus-daemon-1 --system --nofork
I
45 matches
Mail list logo
