[Dev] handling the OpenSSL 1.0->1.1 upgrade

[Andreas Grapentin]

I have enumerated all packages depending on openssl:

  libre/hexchat ::  openssl
  libre/pacman ::  openssl>=1.1 openssl-1.0
  libre/pyrit ::  openssl
  libre/ruby ::  openssl openssl
  libre/uboot-tools ::  openssl
  libre/unar ::  openssl
  libre/xchat ::  openssl
  nonprism/sylpheed ::  openssl
  pcr/assh ::  openssl
  pcr/check-pacman-mtree ::  openssl
  pcr/cherokee ::  openssl
  pcr/dirt ::  openssl
  pcr/galera ::  openssl
  pcr/glance ::  python2-pyopenssl
  pcr/grub-customizer ::  openssl
  pcr/htmldoc ::  openssl
  pcr/icinga ::  openssl
  pcr/inspircd ::  openssl openssl
  pcr/ipmiutil ::  openssl
  pcr/italc ::  openssl
  pcr/knot ::  openssl>=1.0.0
  pcr/libtorrent-extended ::  openssl
  pcr/mariadb-galera ::  openssl openssl
  pcr/mit-scheme ::  openssl
  pcr/monkeysphere ::  perl-crypt-openssl-rsa
  pcr/neomutt ::  openssl
  pcr/nginx-passenger ::  openssl
  pcr/ocaml-ssl ::  openssl
  pcr/openssh-knock ::  openssl
  pcr/perspectives-server ::  openssl
  pcr/rmilter ::  openssl
  pcr/rstudio-desktop ::  openssl
  pcr/samhain ::  openssl
  pcr/snapraid ::  openssl
  pcr/snort ::  openssl
  pcr/softhsm ::  openssl>=1.0.0
  pcr/strongswan ::  openssl openssl
  pcr/tahoe-lafs ::  openssl>=1.0.2 python2-pyopenssl>=0.14
  pcr/tcpcrypt ::  openssl openssl
  pcr/tinc-pre ::  openssl
  pcr/trousers ::  openssl
  pcr/ucommon ::  openssl
  pcr/uftp ::  openssl

generated using this script:

> #!/bin/bash
> 
> set -eu
> 
> pkgbuilds=$(find -iname 'PKGBUILD' -printf "%P\n" | sort)
> 
> for pkg in ${pkgbuilds}; do
> 
>   pushd $(dirname ${pkg}) >/dev/null
> 
>   errf=$(mktemp)
>   deps=$(makepkg -A --printsrcinfo 2>${errf}| grep 'depends =' \
>     | cut -d '=' -f2- | cut -d ':' -f1 | sed 's/^[[:space:]]*//')
>   err=$(< ${errf})
>   rm ${errf}
> 
>   popd >/dev/null
> 
>   if [ -n "${err}" ]; then
>     echo "  $(dirname ${pkg}) :: ERROR" >&2
>     echo "${err}" | sed 's/^/    | /' >&2
>   fi
> 
>   match=""
>   for dep in ${deps}; do
>     if [[ "${dep}" =~ "${1}" ]]; then
>       match="${match} ${dep}"
>     fi
>   done
> 
>   if [ -n "${match}" ]; then
>     echo "  $(dirname ${pkg}) :: ${match}"
>   fi
> done

this also revealed that a lot of our pkgbuilds have issues like the
following:

  libre/jquery-ui :: ERROR
    | ==> ERROR: arch should be an array
    | ==> ERROR: license should be an array
    | ==> ERROR: depends should be an array
    | ==> ERROR: sha512sums should be an array
    | ==> ERROR: source should be an array
    | ==> ERROR: An unknown error has occurred. Exiting...

i started looking into these, and most of them seem trivial. a complete
list is on the pad.

I'll probably fix them over the next couple days.

-A

On Tue, Apr 25, 2017 at 11:07:58AM -0400, Luke Shumaker wrote:
> On Tue, 25 Apr 2017 10:37:26 -0400,
> Luke Shumaker wrote:
> > db-check-package-libraries was designed for the purpose of identifying
> > these packages, but it appears to not be working.
> 
> It seems to have to do with crashing when it sees a dangling symlink.
> I've monkey-patched it on the server to turn abolute links into
> relative links.
> 
> However, it still crashes when it encounters a symlink that points to
> a file in another package.
> 
> And I needed to walk out the door 8 minutes ago, so someone else will
> need to figure this out.
> 
> -- 
> Happy hacking,
> ~ Luke Shumaker
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev

-- 

------------------------------------------------------------------------------
my GPG Public Key:                 https://files.grapentin.org/.gpg/public.key
------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20170503/2beba7af/attachment.sig>