Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
#!/bin/sh
|
|
|
|
# Copyright 2018 Eric Hameleers, Eindhoven, Netherlands
|
2023-09-03 21:37:21 +02:00
|
|
|
# Copyright 2018, 2023 Patrick J. Volkerding, Sebeka, MN, USA
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
# All rights reserved.
|
2018-09-21 20:51:07 +02:00
|
|
|
|
|
|
|
# Redistribution and use of this script, with or without modification, is
|
|
|
|
# permitted provided that the following conditions are met:
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
#
|
2018-09-21 20:51:07 +02:00
|
|
|
# 1. Redistributions of this script must retain the above copyright
|
|
|
|
# notice, this list of conditions and the following disclaimer.
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
#
|
2018-09-21 20:51:07 +02:00
|
|
|
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
|
|
|
|
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
|
|
|
|
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
|
|
|
|
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
|
|
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
|
|
|
|
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
|
|
|
|
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
|
|
|
|
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
|
|
|
|
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
|
|
|
|
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
|
2018-09-21 20:51:07 +02:00
|
|
|
cd $(dirname $0) ; CWD=$(pwd)
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
|
|
|
|
PKGNAM=zstd
|
|
|
|
VERSION=${VERSION:-$(echo $PKGNAM-*.tar.?z | rev | cut -f 3- -d . | cut -f 1 -d - | rev)}
|
2024-03-27 20:16:09 +01:00
|
|
|
BUILD=${BUILD:-1}
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
|
2018-09-21 20:51:07 +02:00
|
|
|
NUMJOBS=${NUMJOBS:-" -j$(expr $(nproc) + 1) "}
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
|
|
|
|
# Automatically determine the architecture we're building on:
|
|
|
|
if [ -z "$ARCH" ]; then
|
|
|
|
case "$(uname -m)" in
|
|
|
|
i?86) ARCH=i586 ;;
|
2022-09-06 22:21:24 +02:00
|
|
|
arm*) readelf /usr/bin/file -A | grep -E -q "Tag_CPU.*[4,5]" && ARCH=arm || ARCH=armv7hl ;;
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
# Unless $ARCH is already set, use uname -m for all other archs:
|
|
|
|
*) ARCH=$(uname -m) ;;
|
|
|
|
esac
|
|
|
|
export ARCH
|
|
|
|
fi
|
|
|
|
|
|
|
|
# If the variable PRINT_PACKAGE_NAME is set, then this script will report what
|
|
|
|
# the name of the created package would be, and then exit. This information
|
|
|
|
# could be useful to other scripts.
|
|
|
|
if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
|
|
|
|
echo "$PKGNAM-$VERSION-$ARCH-$BUILD.txz"
|
|
|
|
exit 0
|
|
|
|
fi
|
|
|
|
|
|
|
|
if [ "$ARCH" = "i486" ]; then
|
|
|
|
SLKCFLAGS="-O2 -march=i486 -mtune=i686"
|
|
|
|
SLKLDFLAGS=""
|
|
|
|
LIBDIRSUFFIX=""
|
|
|
|
elif [ "$ARCH" = "i586" ]; then
|
|
|
|
SLKCFLAGS="-O2 -march=i586 -mtune=i686"
|
|
|
|
SLKLDFLAGS=""
|
|
|
|
LIBDIRSUFFIX=""
|
|
|
|
elif [ "$ARCH" = "s390" ]; then
|
|
|
|
SLKCFLAGS="-O2"
|
|
|
|
SLKLDFLAGS=""
|
|
|
|
LIBDIRSUFFIX=""
|
|
|
|
elif [ "$ARCH" = "x86_64" ]; then
|
|
|
|
SLKCFLAGS="-O2 -fPIC"
|
|
|
|
SLKLDFLAGS="-L/usr/lib64"
|
|
|
|
LIBDIRSUFFIX="64"
|
|
|
|
elif [ "$ARCH" = "armv7hl" ]; then
|
|
|
|
SLKCFLAGS="-O2 -march=armv7-a -mfpu=vfpv3-d16"
|
|
|
|
SLKLDFLAGS=""
|
|
|
|
LIBDIRSUFFIX=""
|
|
|
|
else
|
|
|
|
SLKCFLAGS="-O2"
|
|
|
|
SLKLDFLAGS=""
|
|
|
|
LIBDIRSUFFIX=""
|
|
|
|
fi
|
|
|
|
|
2018-09-21 20:51:07 +02:00
|
|
|
NUMJOBS=${NUMJOBS:-" -j$(expr $(nproc) + 1) "}
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
|
|
|
|
TMP=${TMP:-/tmp}
|
|
|
|
PKG=$TMP/package-$PKGNAM
|
|
|
|
|
|
|
|
rm -rf $PKG
|
|
|
|
mkdir -p $TMP $PKG
|
|
|
|
cd $TMP
|
|
|
|
rm -rf $PKGNAM-$VERSION
|
|
|
|
tar xvf $CWD/$PKGNAM-$VERSION.tar.?z || exit 1
|
|
|
|
cd $PKGNAM-$VERSION || exit 1
|
|
|
|
|
|
|
|
|
|
|
|
# Make sure ownerships and permissions are sane:
|
|
|
|
chown -R root:root .
|
|
|
|
find . \
|
|
|
|
\( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
|
2019-09-30 23:08:32 +02:00
|
|
|
-exec chmod 755 {} \+ -o \
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
\( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
|
2019-09-30 23:08:32 +02:00
|
|
|
-exec chmod 644 {} \+
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
|
2023-09-03 21:37:21 +02:00
|
|
|
# Compile and install:
|
|
|
|
mkdir build/cmake/build
|
|
|
|
cd build/cmake/build
|
|
|
|
cmake \
|
|
|
|
-DCMAKE_C_FLAGS="$SLKCFLAGS" \
|
|
|
|
-DCMAKE_CXX_FLAGS="$SLKCFLAGS" \
|
|
|
|
-DCMAKE_INSTALL_PREFIX=/usr \
|
2024-10-11 00:42:17 +02:00
|
|
|
-DCMAKE_INSTALL_LIBDIR="lib$LIBDIRSUFFIX" \
|
2023-09-03 21:37:21 +02:00
|
|
|
-DDOC_INSTALL_DIR="doc" \
|
|
|
|
-DMAN_INSTALL_DIR=/usr/man/man1 \
|
2023-09-07 04:04:52 +02:00
|
|
|
-DZSTD_BUILD_STATIC=OFF \
|
|
|
|
-DZSTD_PROGRAMS_LINK_SHARED=ON \
|
|
|
|
-DZSTD_LZ4_SUPPORT=ON \
|
|
|
|
-DZSTD_LZMA_SUPPORT=ON \
|
|
|
|
-DZSTD_ZLIB_SUPPORT=ON \
|
2023-09-03 21:37:21 +02:00
|
|
|
.. || exit 1
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
make $NUMJOBS CFLAGS="$SLKCFLAGS" || exit 1
|
2023-09-03 21:37:21 +02:00
|
|
|
make install DESTDIR=$PKG || exit 1
|
|
|
|
cd ../../..
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
|
2023-09-03 21:37:21 +02:00
|
|
|
# Compile and install pzstd:
|
|
|
|
zcat $CWD/zstd.dont.link.pzstd.to.static.libzstd.a.diff.gz | patch -p1 --verbose || exit 1
|
|
|
|
make $NUMJOBS CFLAGS="$SLKCFLAGS" -C contrib/pzstd || exit 1
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
install -Dm755 contrib/pzstd/pzstd $PKG/usr/bin/pzstd || exit 1
|
|
|
|
|
2023-09-07 04:04:52 +02:00
|
|
|
## Don't ship static library:
|
|
|
|
#rm -f $PKG/usr/lib${LIBDIRSUFFIX}/*.a
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
|
2021-02-16 21:57:36 +01:00
|
|
|
# It might be advisable to have the libraries in /lib${LIBDIRSUFFIX}:
|
|
|
|
mkdir -p $PKG/lib${LIBDIRSUFFIX}
|
|
|
|
mv $PKG/usr/lib${LIBDIRSUFFIX}/libzstd.so.* $PKG/lib${LIBDIRSUFFIX}
|
|
|
|
( cd $PKG/usr/lib${LIBDIRSUFFIX}
|
|
|
|
rm -f libzstd.so
|
|
|
|
ln -sf ../../lib${LIBDIRSUFFIX}/libzstd.so.? libzstd.so
|
|
|
|
)
|
|
|
|
|
2023-09-07 04:04:52 +02:00
|
|
|
# Set the path of libzstd in cmake Targets (given by Steven Voges in SBo)
|
|
|
|
sed -i 's|${_IMPORT_PREFIX}||g' $PKG/usr/lib${LIBDIRSUFFIX}/cmake/zstd/zstdTargets-release.cmake
|
|
|
|
|
Thu Sep 13 21:41:51 UTC 2018
a/sysvinit-scripts-2.1-noarch-20.txz: Rebuilt.
rc.6: it was reported by birdboy that JFS is not properly unmounted unless
the order of unmounting local filesystems followed by remounting the root
filesystem read-only is inverted. I tried that, and although it did get rid
of a "/ filesystem is busy" error during shutdown, the JFS / filesystem was
still checked at boot (and found to be clean). I believe that the existing
order of unmounting non-root filesystems followed by remounting the root
filesystem as read-only is the correct order, and found that putting
another sync between these also gets rid of the error on shutdown, so I've
done that. When using JFS as the root filesystem there's still another
similar error message that's generated earlier in the boot, though. I'm
unable to find any way to shut down a JFS root partition in a way that
leaves it clean enough that fsck will not check it at boot, but it is always
found to be clean so this should only be cosmetic. I recall this behavior of
JFS going all the way back to when it was first added to the kernel. If
anyone has a better fix, I'll take a look at it, but in my opinion it's not
really anything to worry about.
ap/ghostscript-9.25-x86_64-1.txz: Upgraded.
This release fixes problems with argument handling, some unintended
results of the security fixes to the SAFER file access restrictions
(specifically accessing ICC profile files), and some additional
security issues over the recent 9.24 release.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16509
(* Security fix *)
ap/squashfs-tools-20180612_6e242dc-x86_64-1.txz: Upgraded.
Linked against libzstd.so.1. Thanks to alienBOB.
ap/sudo-1.8.25p1-x86_64-1.txz: Upgraded.
d/binutils-2.31.1-x86_64-4.txz: Rebuilt.
Since baldzhang has pointed out a valid use case for windres on Linux,
we are restoring the "Windows only" utilities, as none of them are
very large and there may be valid uses for the other ones as well.
l/freetype-2.9.1-x86_64-2.txz: Rebuilt.
Patched to build properly if windres is present on the machine.
l/sg3_utils-1.44-x86_64-1.txz: Upgraded.
l/zstd-1.3.5-x86_64-1.txz: Added.
Thanks to alienBOB.
xfce/tumbler-0.2.3-x86_64-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
Use the ter-114v terminus font. It has been reported that the font we were
using (ter-v14v) restricts the available console colors from 16 to 8 due
to needing an extra bit for the higher number of available glyphs (though
in testing here I couldn't see any difference). The new font covers
ISO8859-1, ISO8859-15, and Windows-1252 codepages. I'm still not sure it's
the best choice, so additional input is welcomed.
Thanks to bormant.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Use the ter-114v terminus font.
2018-09-13 23:41:51 +02:00
|
|
|
# zstdmt as the same as zstd, so just make a symlink:
|
|
|
|
( cd $PKG/usr/bin
|
|
|
|
ln -sf zstd zstdmt
|
|
|
|
)
|
|
|
|
|
|
|
|
# Strip binaries:
|
|
|
|
find $PKG | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
|
|
|
|
find $PKG | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
|
|
|
|
|
|
|
|
# Compress and link manpages, if any:
|
|
|
|
if [ -d $PKG/usr/man ]; then
|
|
|
|
( cd $PKG/usr/man
|
|
|
|
for manpagedir in $(find . -type d -name "man*") ; do
|
|
|
|
( cd $manpagedir
|
|
|
|
for eachpage in $( find . -type l -maxdepth 1) ; do
|
|
|
|
ln -s $( readlink $eachpage ).gz $eachpage.gz
|
|
|
|
rm $eachpage
|
|
|
|
done
|
|
|
|
gzip -9 *.?
|
|
|
|
)
|
|
|
|
done
|
|
|
|
)
|
|
|
|
fi
|
|
|
|
|
|
|
|
# Add a documentation directory:
|
|
|
|
mkdir -p $PKG/usr/doc/$PKGNAM-$VERSION
|
|
|
|
cp -a \
|
|
|
|
CONTRIBUTING* COPYING* LICENSE NEWS README* TESTING* \
|
|
|
|
$PKG/usr/doc/$PKGNAM-$VERSION
|
|
|
|
|
|
|
|
# Add a package description:
|
|
|
|
mkdir -p $PKG/install
|
|
|
|
cat $CWD/slack-desc > $PKG/install/slack-desc
|
|
|
|
|
|
|
|
# Build package:
|
|
|
|
cd $PKG
|
|
|
|
/sbin/makepkg -l y -c n $TMP/$PKGNAM-$VERSION-$ARCH-$BUILD.txz
|