_
( |
___\ \
(__() `-|
(___() |
(__()|
(_()__.--|
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606142
Title:
Version outdated
To manage notifications about this bug g
** Changed in: picolisp (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: picolisp (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606142
T
The only obstacle to a up-to-date picolisp package is adding the -no-pie
flag when building.
As there are now even javascript attacks to circument PIE/ASLR protection
measures,
the general importance PIE as security enhancement has surely dropped heavily.
So even less reason to deny -no-pie.
Se
Hi
As a long-time Ubuntu user (work machines for programming and on
servers) and heavy user of the programming language picolisp, I would
greatly wish for a up-to-date picolisp package in Ubuntu.
The isse here seems to be the rather simple change of Ubuntu having
switched to always pass the PIE f
On Tue, Dec 27, 2016 at 07:39:26PM -, Mike Pechkin wrote:
> I, @tankfeeder in twitter, freenode, telegram help you update version of this.
Ah, cool! Many thanks! :)
> 5min issue, just do it.
So how did it work? You just posted messages? Is there something I should do
too?
- Alex
--
You r
I, @tankfeeder in twitter, freenode, telegram help you update version of this.
5min issue, just do it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606142
Title:
Version outdated
To manage notifi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: picolisp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606142
Title:
V
** Changed in: picolisp (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606142
Title:
Version outdated
To manage notifications about this bug go to:
https
** Changed in: picolisp (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606142
Title:
Version outdated
To manage notifications about this bug go to:
https://bu
It looks like the default build flags has changed
(http://balintreczey.hu/blog/harden-debian-with-pie-and-bindnow/), and
this issue also affects Debian now (see the upstream bug report). So it
looks like this package might need to opt-out in some way.
** Bug watch added: Debian Bug tracker #837573
As the Debian developer told me, it is just a matter of not enabling all
hardening flags.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606142
Title:
Version outdated
To manage notifications about
s/developer/maintainer/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606142
Title:
Version outdated
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/picolis
This was not a rhetorical question.
What I mean is: Please do it the same way as Debian does it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606142
Title:
Version outdated
To manage notificatio
Thanks for the answer.
I understand the problem. Unfortunately, the PicoLisp amd64 base system cannot
be compiled as position independent code (i.e. the -fpic option of C compilers),
because it is written as a special VM in assembly language.
Is there no other way, keeping the core executable wit
Thanks for taking your time to report this issue and help making Ubuntu
better.
Version 16.6-2 has been synced to yakkety-proposed [1], which is the staging
area for new packages. Unfortunately it fails to build on amd64 which keeps it
from migrating over to the regular yakkety archive. It fails
15 matches
Mail list logo
