[arch-dev-public] Automated rebuild for ncurses 6.0 in progress

Evangelos Foutras evangelos at foutrelis.com
Thu Sep 10 21:14:44 UTC 2015


On 06/09/15 20:02, Evangelos Foutras wrote:
> You can follow the progress at: https://rebuilds.foutrelis.com/
> 
> If anyone wants to tackle a build failure, you can commit the fix in
> /trunk (without bumping pkgrel) and then click on the failing package
> and select "Retry build task".
> 
> Note: This rebuild is not listed on https://www.archlinux.org/todo/ in
> order to avoid any confusion.

Just a heads up that the rebuilds should be done very soon. Before
moving everything to the testing repos, we need to be mindful of the
following:

1) TeXLive 2015 is currently in [testing] but only texlive-bin is part
of the rebuilds. Therefore, we must wait until TeXLive 2015 leaves
[testing] before moving the ncurses stuff out of the staging repos.

2) vagrant repackages upstream binaries and contains two files that link
to libncursesw.so.5:

  opt/vagrant/embedded/lib/ruby/2.0.0/x86_64-linux/readline.so
  opt/vagrant/embedded/lib/ruby/2.0.0/x86_64-linux/curses.so

3) cuda repackages upstream binaries and contains one file linking to
libncurses.so.5:

  opt/cuda/bin/cuda-gdb

The above packages may or may not work properly after the move; depends
on whether the binaries/libraries linking to old ncurses are important
to their function.

Personally, I feel that cuda can be left as is. Vagrant on the other
hand, being open source, can most likely be changed to build from source
instead of repackaging upstream binaries. I'll poke both packages'
maintainers on IRC to see what we can do.


More information about the arch-dev-public mailing list