[Bug 2100570] Re: [SRU] upload euslisp/jskeus to Ubuntu/Noble

[Dave Jones]

** Description changed:

  [Impact]
  
  The euslisp and jskeus is a Lisp based intelligent robots programming
  system. They are originally release under ubuntu distribution until
  23.10 (https://launchpad.net/ubuntu/mantic/+package/euslisp-dev) and was
  wrongly removed from Ubuntu by adding `sync-blacklist.txt`, just prior
  to the 24.04 release, see LP: #2063103
  
  This problem was solve by LP: #2096808, It was a confusion of ROS/Debain
  maintainers.
  (https://bugs.launchpad.net/ubuntu/+source/euslisp/+bug/2096808/comments/8
  )
  
  It was back to sync and euslisp/jskeus is available on Plucky. And I'd
  like to use them from oracular / noble.
  
  I have created following branch thus targeting each release. They are
  exactly same source tree as we have in plucky
  (https://launchpad.net/ubuntu/+source/euslisp/9.31+dfsg-3)
  
  https://salsa.debian.org/science-team/euslisp/-/tree/master-24.04 (noble)
  https://salsa.debian.org/science-team/euslisp/-/tree/master-24.10 (oracular)
  
  [Test plan]
  
  The packages for noble and oracular have been run through the (quite
  comprehensive) autopkgtests from PPA builds:
  
  * https://bugs.launchpad.net/ubuntu/+source/euslisp/+bug/2100570/+attachment/5881996/+files/autopkgtest-oracular.txt
  * https://bugs.launchpad.net/ubuntu/+source/euslisp/+bug/2100570/+attachment/5881997/+files/autopkgtest-noble.txt
  
+ Once in proposed, the autopkgtests should be re-run against those
+ versions.
+ 
  [Where problems could occur]
  
  The version being backported is the version from plucky (which works
  happily in plucky), unaltered.
  
  There is a possibility that the new package will break when built
  against the versions of its dependencies in noble / oracular. The test
  plan mitigates this by actively testing builds against these releases.
  Furthermore, this wouldn't be a "regression" as such given the packages
  do not currently exist in these series.
  
  The greater risk is possibly to users that have worked around the lack
  of this package by using third-party sources. However, that is not
  something we can actively guard against with a test plan.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2100570

Title:
  [SRU] upload euslisp/jskeus to Ubuntu/Noble

Status in euslisp package in Ubuntu:
  New
Status in jskeus package in Ubuntu:
  New
Status in euslisp source package in Noble:
  New
Status in jskeus source package in Noble:
  New
Status in euslisp source package in Oracular:
  New
Status in jskeus source package in Oracular:
  New

Bug description:
  [Impact]

  The euslisp and jskeus is a Lisp based intelligent robots programming
  system. They are originally release under ubuntu distribution until
  23.10 (https://launchpad.net/ubuntu/mantic/+package/euslisp-dev) and
  was wrongly removed from Ubuntu by adding `sync-blacklist.txt`, just
  prior to the 24.04 release, see LP: #2063103

  This problem was solve by LP: #2096808, It was a confusion of
  ROS/Debain maintainers.
  (https://bugs.launchpad.net/ubuntu/+source/euslisp/+bug/2096808/comments/8
  )

  It was back to sync and euslisp/jskeus is available on Plucky. And I'd
  like to use them from oracular / noble.

  I have created following branch thus targeting each release. They are
  exactly same source tree as we have in plucky
  (https://launchpad.net/ubuntu/+source/euslisp/9.31+dfsg-3)

  https://salsa.debian.org/science-team/euslisp/-/tree/master-24.04 (noble)
  https://salsa.debian.org/science-team/euslisp/-/tree/master-24.10 (oracular)

  [Test plan]

  The packages for noble and oracular have been run through the (quite
  comprehensive) autopkgtests from PPA builds:

  * https://bugs.launchpad.net/ubuntu/+source/euslisp/+bug/2100570/+attachment/5881996/+files/autopkgtest-oracular.txt
  * https://bugs.launchpad.net/ubuntu/+source/euslisp/+bug/2100570/+attachment/5881997/+files/autopkgtest-noble.txt

  Once in proposed, the autopkgtests should be re-run against those
  versions.

  [Where problems could occur]

  The version being backported is the version from plucky (which works
  happily in plucky), unaltered.

  There is a possibility that the new package will break when built
  against the versions of its dependencies in noble / oracular. The test
  plan mitigates this by actively testing builds against these releases.
  Furthermore, this wouldn't be a "regression" as such given the
  packages do not currently exist in these series.

  The greater risk is possibly to users that have worked around the lack
  of this package by using third-party sources. However, that is not
  something we can actively guard against with a test plan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/euslisp/+bug/2100570/+subscriptions