<ng0>hi. i don't know if perl-net-psyc was already a subject of an email, but i found a bug in perl itself. this is currently being discussed/fixed/etc.. when perl with perl5 comes to fix it the way one person proposed now, can i include the fix as a patch?
<sapientech>okay got things working for the most part: created a package.scm for the missing dependency. one question i have, however is that environment --pure seems to remove the dependencies i use in package.scm
<efraim>another gd cve, fixed by their latest release if anyone wants to take that. I can't get to it until tomorrow at the earliest probably
<rekado>ng0: so… you would like to add the bugfix as a patch to our “perl” package? Many packages depend on “perl”, so it would have to be patched in core-updates. It wouldn’t be available until the next core-updates merge.
<ng0>i am sure that it is swap because i set it up like this, andi have a swap every time i start. but "swsusp" is new to me, as i had "sw" used before.
<rekado>in that case maybe it’s better to wait for it to be fixed by a new release.
<rekado>ng0: what happens if you run the swapon command manually?
<rekado>the log tells us that “swapon /dev/sda3” returns “Invalid argument”
<ng0>re perl: it will depend on which version(s) they apply the fix. 5.24.0 is stable at the moment.. it happens at least with 5.22.0, 5.21.0, and one more
<ng0>swapon: /dev/sda3: software suspend data detected. Rewriting the swap signature.
<ng0>i am sorting old emails out.. i saw that there was at least one email where the .po files were included, making it 8000+ lines.. even when it seems very obvious, we should point out that the generated files should be excluded and only the files one did apply changes in should be sent - and do not make your email 10000 lines long