Bug#1069262: bookworm-pu: package u-boot/2023.01+dfsg-2+deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: u-b...@packages.debian.org, vagr...@debian.org Control: affects -1 + src:u-boot [ Reason ] Fixes the timer clock used by various "orion" based platforms, such as Sheevaplug. [ Impact ] This fixes booting on Sheevaplug and other similar platforms, which are currently entirely broken in bookworm. [ Tests ] The original reporter of the bug confirmed that it worked on their Sheevaplug. [ Risks ] Should be low risk; changes are small and isolated to the currently broken platforms. [ Checklist ] [?] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] A single patch is pulled from upstream that fixes booting on the sheevaplug and related platforms. Unfortunately, the debdiff revealed an un-used patch (u-boot-2023.01+dfsg/debian/0001-u-boot-qemu-Add-malta64el-and-maltael.patch) in the old source package that was never intended to be included, not in revision control and is not present in the new source package. I did not detect the un-used crufty patch until I had performed the upload, so neglected mentioning it in debian/changelog, but it never should have been included in bookworm in the first place... hopefully this "removal" is tolerable. It should have no real effect on the resulting package. [ Other info ] Thanks! live well, vagrant signature.asc Description: PGP signature
Bug#1034863: unblock: guix/1.4.0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: g...@packages.debian.org, vagr...@debian.org Control: affects -1 + src:guix Please unblock package guix [ Reason ] In Guix 1.4.0 upstream configured an additional substitute server by default, but I neglected to properly add the signing key for it to properly work out of the box in the Debian package. [ Impact ] The behavior of Debian's guix package will not break assumptions of the guix community, documentation, etc. which assume both substitute servers will be enabled by default. If the other substitute server is down for any reason, the end user will end up rebuilding many substitutes instead of downloading them from the other server. [ Tests ] Performing "guix pull --substitute-urls=https://bordeaux.guix.gnu.org; successfully downloads substitutes from bordeaux instead of https://ci.guix.gnu.org. Normally ci.guix.gnu.org is preferred, so without explicitly specifying substitute-urls you might not notice the other substitute server is not fully enabled. [ Risks ] People upgrading from older versions will need to ACK the conffile change to fully enable the new substitute server, or add it manually. [ Checklist ] [X] all changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in testing [ Other info ] Nothing springs to mind! Thanks for considering! unblock guix/1.4.0-3 live well, vagrant diff -Nru guix-1.4.0/debian/changelog guix-1.4.0/debian/changelog --- guix-1.4.0/debian/changelog 2022-12-18 16:22:23.0 -0800 +++ guix-1.4.0/debian/changelog 2023-04-21 18:35:03.0 -0700 @@ -1,3 +1,15 @@ +guix (1.4.0-3) unstable; urgency=medium + + * debian/rules: Fix syntax of /etc/guix/acl file. + + -- Vagrant Cascadian Fri, 21 Apr 2023 18:35:03 -0700 + +guix (1.4.0-2) unstable; urgency=medium + + * debian/rules: Add "bordeaux" substitute server to /etc/guix/acl. + + -- Vagrant Cascadian Thu, 20 Apr 2023 22:15:09 -0700 + guix (1.4.0-1) unstable; urgency=medium * New upstream release. diff -Nru guix-1.4.0/debian/rules guix-1.4.0/debian/rules --- guix-1.4.0/debian/rules 2022-12-18 16:22:13.0 -0800 +++ guix-1.4.0/debian/rules 2023-04-21 18:06:27.0 -0700 @@ -54,11 +54,13 @@ debian/guix/lib/systemd/system/gnu-store.mount # guix-gc is installed via examples rm -f debian/guix/usr/lib/*/systemd/system/guix-gc.* - # Add /etc/default/acl with the default substitute server, + # Add /etc/default/acl with the default substitute servers, # with identical output as "guix archive --authorize" mkdir -p debian/guix/etc/guix/ printf '(acl\n (entry\n' > debian/guix/etc/guix/acl sed -e 's,^, ,g' -e 's, $$,,g' etc/substitutes/ci.guix.gnu.org.pub >> debian/guix/etc/guix/acl + printf ' (tag\n (guix import)\n )\n )\n (entry\n' >> debian/guix/etc/guix/acl + sed -e 's,^, ,g' -e 's, $$,,g' etc/substitutes/bordeaux.guix.gnu.org.pub >> debian/guix/etc/guix/acl printf ' (tag\n (guix import)\n )\n )\n )\n' >> debian/guix/etc/guix/acl rmdir debian/guix/usr/lib/*/systemd/system/ rmdir debian/guix/usr/lib/*/systemd/ signature.asc Description: PGP signature
Bug#1034773: unblock: flash-kernel/3.107
chine: Lichee Pi Zero Kernel-Flavors: armmp armmp-lpae Boot-Script-Path: /boot/boot.scr @@ -923,6 +954,9 @@ U-Boot-Script-Name: bootscr.sunxi Required-Packages: u-boot-tools +## qemu instance on arm64 +Machine: linux,dummy-virt + Machine: Marvell 8040 MACCHIATOBin Machine: Marvell 8040 MACCHIATOBin Double-shot Machine: Marvell 8040 MACHIATOBin @@ -1268,6 +1302,13 @@ U-Boot-Script-Name: bootscr.sunxi Required-Packages: u-boot-tools +Machine: Olimex A20-OLinuXino-MICRO-eMMC +Kernel-Flavors: armmp armmp-lpae +Boot-Script-Path: /boot/boot.scr +DTB-Id: sun7i-a20-olinuxino-micro-emmc.dtb +U-Boot-Script-Name: bootscr.sunxi +Required-Packages: u-boot-tools + Machine: Olimex A33-OLinuXino Kernel-Flavors: armmp armmp-lpae Boot-Script-Path: /boot/boot.scr @@ -1649,6 +1690,7 @@ Required-Packages: u-boot-tools Boot-Script-Path: /boot/boot.scr +Machine: Raspberry Pi 3 Model B Plus Rev 1.3 Machine: Raspberry Pi 3 Model B+ Kernel-Flavors: arm64 armmp armmp-lpae DTB-Id: broadcom/bcm2837-rpi-3-b-plus.dtb @@ -1670,6 +1712,9 @@ Required-Packages: u-boot-tools Boot-Script-Path: /boot/boot.scr +## qemu instance on risc-v +Machine: riscv-virtio,qemu + Machine: Rockchip RK3288 Tinker Board Kernel-Flavors: armmp armmp-lpae DTB-Id: rk3288-tinker.dtb @@ -1778,6 +1823,13 @@ U-Boot-Script-Name: bootscr.sunxi Required-Packages: u-boot-tools +Machine: Sipeed Lichee RV +Kernel-Flavors: allwinner riscv64 +DTB-Id: allwinner/sun20i-d1-lichee-rv.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + Machine: SolidRun Clearfog A1 Kernel-Flavors: armmp Boot-Script-Path: /boot/boot.scr @@ -1953,6 +2005,13 @@ U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools +Machine: StarFive VisionFive V1 +Kernel-Flavors: starfive riscv64 +DTB-Id: starfive/jh7100-starfive-visionfive-v1.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + Machine: Theobroma Systems RK3399-Q7 SoM Kernel-Flavors: arm64 DTB-Id: rockchip/rk3399-puma-haikou.dtb @@ -1996,6 +2055,34 @@ Boot-Script-Path: /boot/boot.scr Required-Packages: u-boot-tools +Machine: Toradex Colibri iMX6ULL 1GB (eMMC) on Colibri Aster +Kernel-Flavors: armmp armmp-lpae +DTB-Id: imx6ull-colibri-emmc-aster.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + +Machine: Toradex Colibri iMX6ULL 1GB (eMMC) on Colibri Evaluation Board V3 +Kernel-Flavors: armmp armmp-lpae +DTB-Id: imx6ull-colibri-emmc-eval-v3.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + +Machine: Toradex Colibri iMX6ULL 1GB (eMMC) on Colibri Iris +Kernel-Flavors: armmp armmp-lpae +DTB-Id: imx6ull-colibri-emmc-iris.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + +Machine: Toradex Colibri iMX6ULL 1GB (eMMC) on Colibri Iris V2 +Kernel-Flavors: armmp armmp-lpae +DTB-Id: imx6ull-colibri-emmc-iris-v2.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + Machine: Toshiba AC100 / Dynabook AZ Method: android Android-Boot-Device: /dev/mmcblk0 diff -Nru flash-kernel-3.106/debian/changelog flash-kernel-3.107/debian/changelog --- flash-kernel-3.106/debian/changelog 2022-04-22 16:55:41.0 -0700 +++ flash-kernel-3.107/debian/changelog 2023-04-19 14:12:53.0 -0700 @@ -1,3 +1,43 @@ +flash-kernel (3.107) unstable; urgency=medium + + [ Lubomir Rintel ] + * Make the OLPC XO-1.75 boot script a bit more forgiving + + [ Heinrich Schuchardt ] + * db: add Lenovo Miix 630 and Lenovo Yoga C630 + + [ Alexandre Ghiti ] + * Add the StarFive VisionFive board to the database. + * Add D1 SoC boards to the database + + [ Johannes Schauer Marin Rodrigues ] + * Choose a stable temporary file path for ucf + + [ Dave Jones ] + * Add QEMU-related "dummy" entries + + [ Daniel Serpell ] + * Add A20-OLinuXino_MICRO-eMMC. (Closes: #1019881) + + [ Heinrich Schuchardt ] + * db: add Lenovo ThinkPad X13s + + [ Francesco Dolcini ] + * Add machine db entries for Colibri iMX6ULL eMMC + + [ Heinrich Schuchardt ] + * db: add 'Raspberry Pi 3 Model B Plus Rev 1.3' + + [ Isaac True ] + * Skip EFI detection mechanism when the FK_IGNORE_EFI environment +variable is set to "yes". (Closes: #1033737) + + [ Vagrant Cascadian ] + * Set the value of FK_IGNORE_EFI from +/etc/flash-kernel/ignore-efi. (Closes: #1033737) + + -- Vagrant Cascadian Wed, 19 Apr 2023 14:12:53 -0700 + flash-kernel (3.106) unstable; urgency=medium * db/all.db: Move MNT Reform 2 boards later to fix sort order. diff -Nru flash-kernel-3.106/debian/flash-kernel.postinst flash-kernel-3.107/debian/flash-kernel.postinst --- flash-kernel-3.106/debian/flash-kernel.postinst 2022-03-23 07:22:28.0 -0700 +++ fla
Bug#1034618: unblock: u-boot-menu/4.2.2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: u-boot-m...@packages.debian.org, vagr...@debian.org
Control: affects -1 + src:u-boot-menu
Please unblock package u-boot-menu
Recent versions of u-boot (2023.04+ from debian experimental) fixed bugs
which reveal a misconfiguration in u-boot-menu's hard-coded default
value for the "prompt" setting that cause the menu to not be displayed.
[ Reason ]
Depending on the version of u-boot used, the menu that u-boot-menu
generates will not display a boot menu, proceeding with the default boot
option without opportunity to select a boot option. The main purpose of
u-boot-menu is to provide a menu, so this is suboptimal!
[ Impact ]
The changes implement the possibility to override the default behavior
by making a hard-coded value configurable.
[ Tests ]
I have tested that this works correctly with u-boot from experimental
(2023.04) on pinebook pro, with both the default behavior as well as the
modified configuration. The u-boot from bookworm (2023.01) on the
pinebook pro behavior is unchanged, regardless of the configuration
(e.g. it always displays a menu).
[ Risks ]
Risks are very low; the defaults behave identically to previous
versions. The changes are small and hopefully straightforward.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
[ Other info ]
It would be ideal to switch the default behavior, but given how late in
the bookworm release cycle and not many platforms have been tested to be
working correctly, it seems safer to keep the default behavior, and just
make it possible to configure if needed.
unblock u-boot-menu/4.2.2
Thanks!
live well,
vagrant
diff -Nru u-boot-menu-4.2.1/debian/changelog u-boot-menu-4.2.2/debian/changelog
--- u-boot-menu-4.2.1/debian/changelog 2022-12-12 13:26:47.0 -0800
+++ u-boot-menu-4.2.2/debian/changelog 2023-04-08 16:12:34.0 -0700
@@ -1,3 +1,10 @@
+u-boot-menu (4.2.2) unstable; urgency=medium
+
+ [ Diederik de Haas ]
+ * u-boot-update: Make 'prompt' configurable (Closes: #1034071)
+
+ -- Vagrant Cascadian Sat, 08 Apr 2023 16:12:34 -0700
+
u-boot-menu (4.2.1) unstable; urgency=medium
* Revert "add kalsrseed support" (Closes: #1025954)
diff -Nru u-boot-menu-4.2.1/default u-boot-menu-4.2.2/default
--- u-boot-menu-4.2.1/default 2022-12-07 10:38:40.0 -0800
+++ u-boot-menu-4.2.2/default 2023-04-08 15:37:49.0 -0700
@@ -4,6 +4,7 @@
#U_BOOT_ALTERNATIVES="default recovery"
#U_BOOT_DEFAULT="l0"
+#U_BOOT_PROMPT="0"
#U_BOOT_ENTRIES="all"
#U_BOOT_MENU_LABEL="Debian GNU/Linux"
#U_BOOT_PARAMETERS="ro quiet"
diff -Nru u-boot-menu-4.2.1/u-boot-update u-boot-menu-4.2.2/u-boot-update
--- u-boot-menu-4.2.1/u-boot-update 2022-12-12 13:23:18.0 -0800
+++ u-boot-menu-4.2.2/u-boot-update 2023-04-08 15:37:49.0 -0700
@@ -96,6 +96,7 @@
U_BOOT_ALTERNATIVES="${U_BOOT_ALTERNATIVES:-default recovery}"
U_BOOT_DEFAULT="${U_BOOT_DEFAULT:-l0}"
+U_BOOT_PROMPT="${U_BOOT_PROMPT:-0}"
U_BOOT_ENTRIES="${U_BOOT_ENTRIES:-all}"
U_BOOT_TIMEOUT="${U_BOOT_TIMEOUT:-50}"
U_BOOT_MENU_LABEL="${U_BOOT_MENU_LABEL:-${PRETTY_NAME:-Debian GNU/Linux kernel}}"
@@ -162,7 +163,7 @@
default ${U_BOOT_DEFAULT}
menu title U-Boot menu
-prompt 0
+prompt ${U_BOOT_PROMPT}
timeout ${U_BOOT_TIMEOUT}
"
signature.asc
Description: PGP signature
Bug#1026945: bullseye-pu: package guix/1.2.0-4+deb11u1
Control: retitle 1026945 bullseye-pu: package guix/1.2.0-4+deb11u1 On 2023-03-15, Jonathan Wiltshire wrote: > On Sat, Dec 24, 2022 at 07:33:38AM -0800, Vagrant Cascadian wrote: >> This fixes a FTBFS of due several test suites using expired OpenPGP >> keys. At the time the current packages in Debian were built, the keys >> had not yet expired, but was later fixed upstream: > > Please go ahead. Finally managed to carve out time for the upload: guix (1.2.0-4+deb11u1) bullseye; urgency=medium [ Santiago Vila ] * debian/patches: Remove expiration dates on openpgp keys used in test suite. (Closes: #1011863). -- Vagrant Cascadian Sat, 08 Apr 2023 18:35:36 -0700 Should land in the FTP queues shortly. live well, vagrant signature.asc Description: PGP signature
Bug#1026945: bullseye-pu: package guix/1.2.0-4
On 2022-12-24, Vagrant Cascadian wrote: > Package: release.debian.org > Severity: normal > Tags: bullseye > User: release.debian@packages.debian.org > Usertags: pu > X-Debbugs-Cc: g...@packages.debian.org vagr...@debian.org > Control: affects -1 + src:guix Should I have intead filed this with the intended version (e.g. guix/1.2.0-4+deb11u1) ? Should I just go ahead and upload, as this fixes a FTBFS issue in bullseye? Thanks for any guidance! live well, vagrant > [ Reason ] > > This fixes a FTBFS of due several test suites using expired OpenPGP > keys. At the time the current packages in Debian were built, the keys > had not yet expired, but was later fixed upstream: > > https://issues.guix.gnu.org/55506 > > And was reported in Debian against the 1.3.x versions and fixed by > applying the upstream patch: > > https://bugs.debian.org/1011863 > > [ Impact ] > > Future security updates will not be able to be fixed without fixing > this issue first or disabling the affected tests. > > [ Tests ] > > Building the package succeeds with the patch; test suites pass. > > [ Risks ] > > None known at this time. > > [ Checklist ] > [x] *all* changes are documented in the d/changelog > [x] I reviewed all changes and I approve them > [x] attach debdiff against the package in (old)stable > [x] the issue is verified as fixed in unstable > > [ Changes ] > > Replaces the OpenPGP keys that have expired with keys with no > expiration date. > > [ Other info ] > > None. > > > live well, > vagrant > diff -Nru guix-1.2.0/debian/changelog guix-1.2.0/debian/changelog > --- guix-1.2.0/debian/changelog 2021-03-27 19:18:29.0 -0700 > +++ guix-1.2.0/debian/changelog 2022-12-24 07:16:17.0 -0800 > @@ -1,3 +1,11 @@ > +guix (1.2.0-4+deb11u1) bullseye; urgency=medium > + > + [ Santiago Vila ] > + * debian/patches: Remove expiration dates on openpgp keys used in test > +suite. (Closes: #1011863). > + > + -- Vagrant Cascadian Sat, 24 Dec 2022 07:16:17 -0800 > + > guix (1.2.0-4) unstable; urgency=medium > >* debian/patches: Fix privilege escalation issue in > diff -Nru guix-1.2.0/debian/patches/series guix-1.2.0/debian/patches/series > --- guix-1.2.0/debian/patches/series 2021-03-18 15:14:54.0 -0700 > +++ guix-1.2.0/debian/patches/series 2022-12-24 06:55:26.0 -0800 > @@ -38,3 +38,4 @@ > 0028-tests-lint.scm-Disable-several-lint-tests-that-fail-.patch > 0029-tests-swh.scm-Disable-tests-the-fail-with-guile-2.2.patch > security/daemon-Prevent-privilege-escalation-with-keep-failed.patch > +tests-Ensure-test-OpenPGP-keys-never-expire.patch > diff -Nru > guix-1.2.0/debian/patches/tests-Ensure-test-OpenPGP-keys-never-expire.patch > guix-1.2.0/debian/patches/tests-Ensure-test-OpenPGP-keys-never-expire.patch > --- > guix-1.2.0/debian/patches/tests-Ensure-test-OpenPGP-keys-never-expire.patch > 1969-12-31 16:00:00.0 -0800 > +++ > guix-1.2.0/debian/patches/tests-Ensure-test-OpenPGP-keys-never-expire.patch > 2022-12-24 06:55:26.0 -0800 > @@ -0,0 +1,55 @@ > +From 3ae7632ca0a1edca9d8c3c766efb0dcc8aa5da37 Mon Sep 17 00:00:00 2001 > +From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= > +Date: Wed, 18 May 2022 23:20:21 +0200 > +Subject: [PATCH] tests: Ensure test OpenPGP keys never expire. > + > +All these keys had expiration dates. 'tests/keys/ed25519.pub' expired > +on 2022-04-24. > + > +Fixes <https://issues.guix.gnu.org/55506>. > + > +* tests/keys/ed25519.pub, tests/keys/ed25519-2.pub, > +tests/keys/ed25519-3.pub: Remove expiration date. > +--- > + tests/keys/ed25519-2.pub | 11 +-- > + tests/keys/ed25519-3.pub | 10 +- > + tests/keys/ed25519.pub | 10 +- > + 3 files changed, 15 insertions(+), 16 deletions(-) > + > +Adjusted to apply to older locations present in 1.3.0. > + > +--- a/tests/ed25519bis.key > b/tests/ed25519bis.key > +@@ -1,10 +1,9 @@ > + -BEGIN PGP PUBLIC KEY BLOCK- > + > + mDMEXtVsNhYJKwYBBAHaRw8BAQdAnLsYdh3BpeK1xDguJE80XW2/MSmqeeP6pbQw > +-8jAw0OG0IkNoYXJsaWUgR3VpeCA8Y2hhcmxpZUBleGFtcGxlLm9yZz6IlgQTFggA > +-PhYhBKBDaY1jer75FlruS4IkDtyrgNqDBQJe1Ww2AhsDBQkDwmcABQsJCAcCBhUK > +-CQgLAgQWAgMBAh4BAheAAAoJEIIkDtyrgNqDM6cA/idDdoxo9SU+witdTXt24APH > +-yRzHbX9Iyh4dZNIek9JwAP9E0BwSvDHB4LY9z4RWf2hJp3dm/yZ/jEpK+w4BGN4J > +-Ag== > +-=JIU0 > ++8jAw0OG0IkNoYXJsaWUgR3VpeCA8Y2hhcmxpZUBleGFtcGxlLm9yZz6IkAQTFggA > ++OAIbAwULCQgHAgYVCgkICwIEFgIDAQIeAQIXgBYhBKBDaY1jer75FlruS4IkDtyr > ++gNqDBQJihWJtAAoJEIIkDtyrgNqDbs0BAPOaGSYf3pX3DReEe1zbxxVQrolX9/AZ > ++VP0AOt0TAgkzAP0Sr7G1NuCtjWWGK1WmlyTFPhOWLhNriKgZFkBZrGypAw== > ++=pdTB > + -END PGP PUB
Bug#1026945: bullseye-pu: package guix/1.2.0-4
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: g...@packages.debian.org vagr...@debian.org Control: affects -1 + src:guix [ Reason ] This fixes a FTBFS of due several test suites using expired OpenPGP keys. At the time the current packages in Debian were built, the keys had not yet expired, but was later fixed upstream: https://issues.guix.gnu.org/55506 And was reported in Debian against the 1.3.x versions and fixed by applying the upstream patch: https://bugs.debian.org/1011863 [ Impact ] Future security updates will not be able to be fixed without fixing this issue first or disabling the affected tests. [ Tests ] Building the package succeeds with the patch; test suites pass. [ Risks ] None known at this time. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] Replaces the OpenPGP keys that have expired with keys with no expiration date. [ Other info ] None. live well, vagrant diff -Nru guix-1.2.0/debian/changelog guix-1.2.0/debian/changelog --- guix-1.2.0/debian/changelog 2021-03-27 19:18:29.0 -0700 +++ guix-1.2.0/debian/changelog 2022-12-24 07:16:17.0 -0800 @@ -1,3 +1,11 @@ +guix (1.2.0-4+deb11u1) bullseye; urgency=medium + + [ Santiago Vila ] + * debian/patches: Remove expiration dates on openpgp keys used in test +suite. (Closes: #1011863). + + -- Vagrant Cascadian Sat, 24 Dec 2022 07:16:17 -0800 + guix (1.2.0-4) unstable; urgency=medium * debian/patches: Fix privilege escalation issue in diff -Nru guix-1.2.0/debian/patches/series guix-1.2.0/debian/patches/series --- guix-1.2.0/debian/patches/series2021-03-18 15:14:54.0 -0700 +++ guix-1.2.0/debian/patches/series2022-12-24 06:55:26.0 -0800 @@ -38,3 +38,4 @@ 0028-tests-lint.scm-Disable-several-lint-tests-that-fail-.patch 0029-tests-swh.scm-Disable-tests-the-fail-with-guile-2.2.patch security/daemon-Prevent-privilege-escalation-with-keep-failed.patch +tests-Ensure-test-OpenPGP-keys-never-expire.patch diff -Nru guix-1.2.0/debian/patches/tests-Ensure-test-OpenPGP-keys-never-expire.patch guix-1.2.0/debian/patches/tests-Ensure-test-OpenPGP-keys-never-expire.patch --- guix-1.2.0/debian/patches/tests-Ensure-test-OpenPGP-keys-never-expire.patch 1969-12-31 16:00:00.0 -0800 +++ guix-1.2.0/debian/patches/tests-Ensure-test-OpenPGP-keys-never-expire.patch 2022-12-24 06:55:26.0 -0800 @@ -0,0 +1,55 @@ +From 3ae7632ca0a1edca9d8c3c766efb0dcc8aa5da37 Mon Sep 17 00:00:00 2001 +From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= +Date: Wed, 18 May 2022 23:20:21 +0200 +Subject: [PATCH] tests: Ensure test OpenPGP keys never expire. + +All these keys had expiration dates. 'tests/keys/ed25519.pub' expired +on 2022-04-24. + +Fixes <https://issues.guix.gnu.org/55506>. + +* tests/keys/ed25519.pub, tests/keys/ed25519-2.pub, +tests/keys/ed25519-3.pub: Remove expiration date. +--- + tests/keys/ed25519-2.pub | 11 +-- + tests/keys/ed25519-3.pub | 10 +- + tests/keys/ed25519.pub | 10 +- + 3 files changed, 15 insertions(+), 16 deletions(-) + +Adjusted to apply to older locations present in 1.3.0. + +--- a/tests/ed25519bis.key b/tests/ed25519bis.key +@@ -1,10 +1,9 @@ + -BEGIN PGP PUBLIC KEY BLOCK- + + mDMEXtVsNhYJKwYBBAHaRw8BAQdAnLsYdh3BpeK1xDguJE80XW2/MSmqeeP6pbQw +-8jAw0OG0IkNoYXJsaWUgR3VpeCA8Y2hhcmxpZUBleGFtcGxlLm9yZz6IlgQTFggA +-PhYhBKBDaY1jer75FlruS4IkDtyrgNqDBQJe1Ww2AhsDBQkDwmcABQsJCAcCBhUK +-CQgLAgQWAgMBAh4BAheAAAoJEIIkDtyrgNqDM6cA/idDdoxo9SU+witdTXt24APH +-yRzHbX9Iyh4dZNIek9JwAP9E0BwSvDHB4LY9z4RWf2hJp3dm/yZ/jEpK+w4BGN4J +-Ag== +-=JIU0 ++8jAw0OG0IkNoYXJsaWUgR3VpeCA8Y2hhcmxpZUBleGFtcGxlLm9yZz6IkAQTFggA ++OAIbAwULCQgHAgYVCgkICwIEFgIDAQIeAQIXgBYhBKBDaY1jer75FlruS4IkDtyr ++gNqDBQJihWJtAAoJEIIkDtyrgNqDbs0BAPOaGSYf3pX3DReEe1zbxxVQrolX9/AZ ++VP0AOt0TAgkzAP0Sr7G1NuCtjWWGK1WmlyTFPhOWLhNriKgZFkBZrGypAw== ++=pdTB + -END PGP PUBLIC KEY BLOCK- +--- a/tests/ed25519.key b/tests/ed25519.key +@@ -2,9 +2,9 @@ + + mDMEXqNaoBYJKwYBBAHaRw8BAQdArviKtelb4g0I3zx9xyDS40Oz8i1/LRXqppG6 + b23Hdim0KEVkIFR3by1GaWZ0eSA8bHVkbyt0ZXN0LWVjY0BjaGJvdWliLm9yZz6I +-lgQTFggAPhYhBETTHiGvcTj5tjIoCncfScv6rgctBQJeo1qgAhsDBQkDwmcABQsJ +-CAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJEHcfScv6rgctq4MA/1R9G0roEwrHwmTd +-DHxt211eLqupwXE0Z7xY2FH6DHk9AP4owEefBU7jQprSAzBS+c6gdS3SCCKKqAh6 +-ToZ4LmbKAw== +-=FXMK ++kAQTFggAOAIbAwULCQgHAgYVCgkICwIEFgIDAQIeAQIXgBYhBETTHiGvcTj5tjIo ++CncfScv6rgctBQJihWH6AAoJEHcfScv6rgctfPMBAPv+yPmEgM+J6D1nZjXsO4zW +++4e3y2Ez+QxgI2tn8Z2xAQDBUWyyu0X+8dguGmVlsaiQdkazaUSpexvIhh9zONYw ++Bg== ++=s4Vp + -END PGP PUBLIC KEY BLOCK- signature.asc Description: PGP signature
Bug#887060: testing migration happened despite FTBFS on arch:all buildd
On 2020-12-20, Paul Gevers wrote: > On Thu, 15 Nov 2018 20:49:43 +0100 Paul Gevers wrote: >> I think I have found the cause for this issue. Apparently some arch:all >> binary packages are not listed in both the binary-/Packages.* and >> binary-all/Packages.* file groups, but ONLY in the binary-all/Packages.* >> files (at least on unstable). The britney log tells me that the >> binary-all files are not read in yet. >> >> Currently the source package bzr is in this position (and I noticed >> because autopkgtest fails on non-installability of the arch:all >> packages), which enabled me to figure this out. > > Today (noted on IRC), pcb-rnd was in the same position. Luckily the > migration didn't happen because the second phase blocked the migration > (pcb-rnd (the binary) depends on pcb-rnd-doc). > > pcb-rnd-doc is in binary-all/Packages.* but not in binary-/Packages.*. > > The situation will be gone soon, pcb-rnd build on arch:all several > minutes ago. FWIW, This also recently happened with src:u-boot, u-boot migrated u-boot *:any even though u-boot-qemu:all FTBFS. live well, vagrant signature.asc Description: PGP signature
Re: Bug#988217: u-boot: bootefi causes boot failure with boot.scr
On 2021-05-23, Cyril Brulebois wrote: > Vagrant Cascadian (2021-05-22): >> This could impact debian-installer as it build-depends on it for >> armhf/arm64, though I think the chance of regressions are minimal. Is >> there a release candidate planned in the immediate future? > > Exact plans are still sketchy, but I expect one in the next week or so > (we need linux to migrate first, and I'm trying to finalize the cdebconf > workaround-/hack-athon). Ok; I went ahead and uploaded the fix to u-boot after a bit more testing. It's only a few days behind linux, and will need to ask for an unblock before too long... live well, vagrant signature.asc Description: PGP signature
Re: Bug#988217: u-boot: bootefi causes boot failure with boot.scr
On 2021-05-16, Vagrant Cascadian wrote:
> On 2021-05-07, Vagrant Cascadian wrote:
>> On 2021-04-16, Bastian Germann wrote:
>>> On a Lamobo R1, I can verify 2021.01 versions not to boot with a
>>> default environment. However, 2020.10+dfsg-2 boots. Even though the
>>> original issue has the same outcome, I guess it is caused by something
>>> else.
>>
>> Different enough to warrant it's own bug, cloning...
>>
>>
>>> I figured out my problem is caused by
>>> https://github.com/u-boot/u-boot/commit/f3866909e35074ea6f50226d40487a180de1132f.
>>> The
>>> boot_efi_bootmgr will run and read a bad dtb, which makes a boot.scr
>>> boot fail.
>>
>> This would definitely be good to fix in bullseye, but this is quite late
>> in the release cycle.
>
> After recently upgrading several more systems that turned out to be
> affected by this, I'm bumping the severity of this bug...
>
>
>> Will need to test failure and success cases with and without EFI as well
>> as boot.scr and extlinux.conf to make sure this doesn't cause
>> regressions in other boot paths...
>
> This still needs some work!
I know it is terribly late in the release cycle, but this breaks default
boot on several systems I've tested, and likely to affect others in
reasonable configurations, so I intend to upload a fix with the upstream
the patch very soon.
This could impact debian-installer as it build-depends on it for
armhf/arm64, though I think the chance of regressions are minimal. Is
there a release candidate planned in the immediate future?
I've tested that the fix works for Lamobo-R1, though I haven't yet
tested if it breaks u-boot as an EFI implementation (which seems like
the only significant regression risk). Will test that before uploading.
The upstream patch (which is in debian/patches on the sid branch):
From 82d01f04facef1276cede067efd02d2a731ffe83 Mon Sep 17 00:00:00 2001
From: Heinrich Schuchardt
Date: Sun, 24 Jan 2021 14:34:12 +
Subject: [PATCH] efi_loader: switch to non-secure mode later
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Some ARMv7 boards using PSCI require to be in secure-mode when booted via
'bootz' or 'bootm'. During distro-boot 'bootefi bootmgr' is called to check
if booting via UEFI is possible.
With the change we change the switch from secure mode to non-secure mode is
moved from the UEFI subsystem setup to just before calling StartImage().
Cc: Jernej Škrabec
Reported by: Andre Przywara
Signed-off-by: Heinrich Schuchardt
---
cmd/bootefi.c | 4
lib/efi_loader/efi_setup.c | 4
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/cmd/bootefi.c b/cmd/bootefi.c
index c8eb5c32b0..81dd8e0284 100644
--- a/cmd/bootefi.c
+++ b/cmd/bootefi.c
@@ -8,6 +8,7 @@
#define LOG_CATEGORY LOGC_EFI
#include
+#include
#include
#include
#include
@@ -338,6 +339,9 @@ static efi_status_t do_bootefi_exec(efi_handle_t handle,
void *load_options)
efi_uintn_t exit_data_size = 0;
u16 *exit_data = NULL;
+ /* On ARM switch from EL3 or secure mode to EL2 or non-secure mode */
+ switch_to_non_secure_mode();
+
/* Call our payload! */
ret = EFI_CALL(efi_start_image(handle, _data_size, _data));
if (ret != EFI_SUCCESS) {
diff --git a/lib/efi_loader/efi_setup.c b/lib/efi_loader/efi_setup.c
index 5800cbf6d4..b1c5125032 100644
--- a/lib/efi_loader/efi_setup.c
+++ b/lib/efi_loader/efi_setup.c
@@ -6,7 +6,6 @@
*/
#include
-#include
#include
#include
@@ -188,9 +187,6 @@ efi_status_t efi_init_obj_list(void)
/* Allow unaligned memory access */
allow_unaligned();
- /* On ARM switch from EL3 or secure mode to EL2 or non-secure mode */
- switch_to_non_secure_mode();
-
/* Initialize root node */
ret = efi_root_node_register();
if (ret != EFI_SUCCESS)
--
2.30.2
live well,
vagrant
signature.asc
Description: PGP signature
Bug#985922: unblock: u-boot/2021.01+dfsg-4
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: vagr...@debian.org, debian-b...@lists.debian.org Severity: normal Please unblock package u-boot [ Reason ] This version adds support for the pinetab platform and fixes a bug that fails to detect some pinephone platforms. This also re-adds debugging symbols that were lost late in the bullseye release cycle due to upstream buildsystem changes. [ Impact ] Hardware support for another platform (pinetab) and working installation process for another platform (pinephone). Ability to debug u-boot using debugging symbols. [ Tests ] None. [ Risks ] Very low risk to existing platforms as this involves no code changes to u-boot itself. Increases the installed size (~2MB) and .deb size nominally for the u-boot-sunxi:arm64 package. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] This is depended on by debian-installer for the arm64/armhf images, so leaving this in a blocked state could impact debian-installer update process. unblock u-boot/2021.01+dfsg-4 Thanks for your work managing the release! live well, vagrant diff -Nru u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi --- u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi 2021-02-28 18:14:48.0 -0800 +++ u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi 2021-03-12 11:10:45.0 -0800 @@ -38,7 +38,9 @@ "OrangePi Zero Plus2") TARGET="/usr/lib/u-boot/orangepi_zero_plus2/" ;; "OrangePi One Plus") TARGET="/usr/lib/u-boot/orangepi_one_plus/" ;; "Pinebook") TARGET="/usr/lib/u-boot/pinebook" ;; - "Pine64 PinePhone (1."[12]")") TARGET='/usr/lib/u-boot/pinephone' ;; + "Pine64 PinePhone Braveheart (1.1)") TARGET='/usr/lib/u-boot/pinephone' ;; + "Pine64 PinePhone (1.2)") TARGET='/usr/lib/u-boot/pinephone' ;; + "PineTab") TARGET="/usr/lib/u-boot/pinetab" ;; "Pine64+") TARGET="/usr/lib/u-boot/pine64_plus" ;; "Pine64 LTS") TARGET="/usr/lib/u-boot/pine64-lts" ;; "PineRiver Mini X-Plus") TARGET="/usr/lib/u-boot/Mini-X" ;; diff -Nru u-boot-2021.01+dfsg/debian/changelog u-boot-2021.01+dfsg/debian/changelog --- u-boot-2021.01+dfsg/debian/changelog2021-03-01 00:00:18.0 -0800 +++ u-boot-2021.01+dfsg/debian/changelog2021-03-12 15:00:43.0 -0800 @@ -1,3 +1,18 @@ +u-boot (2021.01+dfsg-4) unstable; urgency=medium + + [ Arnaud Ferraris ] + * Add support for the pinetab platform (Closes: #982982) + * u-boot-install-sunxi: fix device tree model for PinePhone 1.1 +(Closes: #984704) + + [ Vagrant Cascadian ] + * debian/patches: Update PineTab patch use default bootdelay. + * debian/patches: Add Forwarded link to PineTab patch. + * debian/rules: Ensure debugging symbols are enabled. + * debian/rules: Pass argument to remove build path from debug symbols. + + -- Vagrant Cascadian Fri, 12 Mar 2021 15:00:43 -0800 + u-boot (2021.01+dfsg-3) unstable; urgency=medium [ Domenico Andreoli ] diff -Nru u-boot-2021.01+dfsg/debian/patches/pinetab/0001-configs-add-PineTab-defconfig.patch u-boot-2021.01+dfsg/debian/patches/pinetab/0001-configs-add-PineTab-defconfig.patch --- u-boot-2021.01+dfsg/debian/patches/pinetab/0001-configs-add-PineTab-defconfig.patch 1969-12-31 16:00:00.0 -0800 +++ u-boot-2021.01+dfsg/debian/patches/pinetab/0001-configs-add-PineTab-defconfig.patch 2021-03-12 11:15:15.0 -0800 @@ -0,0 +1,45 @@ +From 2c346cacb4b0841051bceb27a57058020860ab8b Mon Sep 17 00:00:00 2001 +From: Arnaud Ferraris +Date: Wed, 2 Sep 2020 09:53:50 +0200 +Subject: [PATCH] configs: add PineTab defconfig +Forwarded: https://patchwork.ozlabs.org/project/uboot/list/?series=232582 + +The PineTab device-tree is already in u-boot, this commit adds the corresponding +defconfig, based on pinephone_defconfig. + +Signed-off-by: Arnaud Ferraris + +--- + configs/pinetab_defconfig | 22 ++ + 1 file changed, 22 insertions(+) + create mode 100644 configs/pinetab_defconfig + +diff --git a/configs/pinetab_defconfig b/configs/pinetab_defconfig +new file mode 100644 +index 00..71dda9f5d9 +--- /dev/null b/configs/pinetab_defconfig +@@ -0,0 +1,20 @@ ++CONFIG_ARM=y ++CONFIG_ARCH_SUNXI=y ++CONFIG_SPL=y ++CONFIG_IDENT_STRING="" ++CONFIG_MACH_SUN50I=y ++CONFIG_SUNXI_DRAM_LPDDR3_STOCK=y ++CONFIG_DRAM_CLK=552 ++CONFIG_DRAM_ZQ=3881949 ++CONFIG_MMC_SUNXI_SLOT_EXTRA=2 ++# CONFIG_VIDEO_DE2 is not set ++CONFIG_DEFAULT_DEVICE_TREE="sun50i-a64-pinetab" ++
Bug#985114: unblock: sendmail/8.15.2-21
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: a...@debian.org
Please unblock package sendmail
[ Reason ]
This version of sendmail fixes a reproducible builds issue with build
paths, updates the lintian overrides, minor packaging updates and
spelling fixes.
[ Impact ]
Removes only known reproducibility issues for sendmail.
[ Tests ]
None.
[ Risks ]
The changes are trivial, mostly affecting documentation, lintian
overrides, and spelling.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
This is a QA package and I did not perform the upload, though was
asked to file the unblock request regarding the reproducible builds
issue.
unblock sendmail/8.15.2-21
live well,
vagrant
diff -Nru sendmail-8.15.2/debian/cf/Makefile.am sendmail-8.15.2/debian/cf/Makefile.am
--- sendmail-8.15.2/debian/cf/Makefile.am 2020-07-06 16:44:51.0 -0700
+++ sendmail-8.15.2/debian/cf/Makefile.am 2021-03-03 03:03:42.0 -0800
@@ -35,6 +35,7 @@
$(RM) ${DESTDIR}${pkgdatadir}/cf/cf/Build;
$(RM) ${DESTDIR}${pkgdatadir}/cf/cf/Makefile;
$(RM) ${DESTDIR}${pkgdatadir}/cf/cf/*.cf;
+ $(RM) ${DESTDIR}${pkgdatadir}/cf/cf/README
for dir in ${CF_DIRS}; do \
$(INSTALL) -d ${DESTDIR}${pkgdatadir}/cf/$$dir; \
find $$dir -type f -name '*.mc' -o -name '*.m4' \
diff -Nru sendmail-8.15.2/debian/changelog sendmail-8.15.2/debian/changelog
--- sendmail-8.15.2/debian/changelog 2020-07-06 16:44:51.0 -0700
+++ sendmail-8.15.2/debian/changelog 2021-03-03 03:03:42.0 -0800
@@ -1,3 +1,16 @@
+sendmail (8.15.2-21) unstable; urgency=medium
+
+ * QA upload.
+ * Make the build reproducible, thanks to Vagrant Cascadian.
+(Closes: #983902)
+ * Move amavis documentation to /usr/share/doc/sendmail.
+ * Bump watch version to 4. No changes needed.
+ * Update to Standards-Version: 4.5.1.
+ * Fix more typos found by Lintian.
+ * Update Lintian overrides.
+
+ -- Andreas Beckmann Wed, 03 Mar 2021 12:03:42 +0100
+
sendmail (8.15.2-20) unstable; urgency=medium
* QA upload.
diff -Nru sendmail-8.15.2/debian/configure.ac sendmail-8.15.2/debian/configure.ac
--- sendmail-8.15.2/debian/configure.ac 2020-07-06 16:44:51.0 -0700
+++ sendmail-8.15.2/debian/configure.ac 2021-03-03 03:03:42.0 -0800
@@ -1482,7 +1482,6 @@
fi;
])
AC_CONFIG_FILES([libmilter${sm_libmilter_version}.install:libmilter.install.in])
-AC_CONFIG_FILES([libmilter${sm_libmilter_version}.lintian-overrides:libmilter.lintian-overrides.in])
AC_CONFIG_FILES([libmilter${sm_libmilter_version}.symbols:libmilter.symbols.in])
AC_CONFIG_FILES([milter.pc])
AC_CONFIG_FILES([sendmail-base.dirs])
diff -Nru sendmail-8.15.2/debian/control sendmail-8.15.2/debian/control
--- sendmail-8.15.2/debian/control 2020-07-06 16:44:51.0 -0700
+++ sendmail-8.15.2/debian/control 2021-03-03 03:03:42.0 -0800
@@ -16,7 +16,7 @@
bind-dev,
fakeroot (<< 0.4.5),
Rules-Requires-Root: binary-targets
-Standards-Version: 4.5.0
+Standards-Version: 4.5.1
Homepage: http://www.sendmail.org
Vcs-Browser: https://salsa.debian.org/debian/sendmail
Vcs-Git: https://salsa.debian.org/debian/sendmail.git
diff -Nru sendmail-8.15.2/debian/control.in sendmail-8.15.2/debian/control.in
--- sendmail-8.15.2/debian/control.in 2020-07-06 16:44:51.0 -0700
+++ sendmail-8.15.2/debian/control.in 2021-03-03 03:03:42.0 -0800
@@ -16,7 +16,7 @@
bind-dev,
fakeroot (<< 0.4.5),
Rules-Requires-Root: binary-targets
-Standards-Version: 4.5.0
+Standards-Version: 4.5.1
Homepage: http://www.sendmail.org
Vcs-Browser: https://salsa.debian.org/debian/sendmail
Vcs-Git: https://salsa.debian.org/debian/sendmail.git
diff -Nru sendmail-8.15.2/debian/copyright sendmail-8.15.2/debian/copyright
--- sendmail-8.15.2/debian/copyright 2020-07-06 16:44:51.0 -0700
+++ sendmail-8.15.2/debian/copyright 2021-03-03 03:03:42.0 -0800
@@ -12,7 +12,7 @@
Copyright: Robert Leslie
1997-1998 Johnie Ingram
1998-2010 Richard A Nelson
- © 2012-2020 Andreas Beckmann
+ © 2012-2021 Andreas Beckmann
License: other-Sendmail
License: other-Sendmail
diff -Nru sendmail-8.15.2/debian/examples/Makefile.am sendmail-8.15.2/debian/examples/Makefile.am
--- sendmail-8.15.2/debian/examples/Makefile.am 2020-07-06 16:44:51.0 -0700
+++ sendmail-8.15.2/debian/examples/Makefile.am 2021-03-03 03:03:42.0 -0800
@@ -30,9 +30,10 @@
# Shipped data
#
# Installed example subdirectories
-EXAMPLES_DIRS = amavis db dhcp \
+EXAMPLES_DIRS = db dhcp \
ldap logcheck milter network \
pam.d ppp resolvconf sasl tls
+EXAMPLES_DOCS_DIRS = amavis
#
# Sigh... I wanted to use sysconf_SCRIPTS, but automake says NO!
nobase_dist_sysconf_DATA = dhcp/dhclient-exit-hooks.d/sendmail \
@@ -53,7 +54,13 @@
! -name '*.in' -a !
Bug#900837: update on mass-rebuild of packages for reproducible builds
On 2019-03-05, Holger Levsen wrote: > I ran Chris's script again on coccia, with the result that currently > 6084 source packages in the archive need a rebuild for reproducible > builds, as they were built with an old dpkg version not producing > .buildinfo files. I ran it just now, and we're down to 3433! Still a ways to go, but getting there... Updated list attached. live well, vagrant abego-treelayout abicheck accelio adacontrol aiksaurus aiowsgi airlift-slice album alqalam amispammer amoeba-data amphetamine-data amqp-specs android-platform-external-rappor angband-audio apertium-oci apertium-szl api-sanity-checker apt-config-auto-update apt-src apt-venv archmbox arduino argparse4j args4j aribas arrayfire asciimathtml asis aspell-am aspell-cs aspell-cy aspell-el aspell-fr aspell-hr aspell-hsb aspell-hu aspell-hy aspell-is aspell-kk aspell-pl aspell-ro aspell-sl aspell-sv aspell-uz asql asterisk-moh-opsound asterisk-prompt-de asterisk-prompt-es-co asterisk-prompt-fr-armelle asterisk-prompt-fr-proformatique asterisk-prompt-it astrodendro astrometry-data-2mass at-at-clojure atmel-firmware autoconf2.64 autodns-dhcp autofill-forms automaton awit-dbackup axmlrpc bar-cursor-el beancounter beckon-clojure bidiui binstats biomaj3-zipkin blag-fortune blosxom bmt boilerpipe brag brebis broctl bsaf bsdowl bsfilter bytecode c3 caffeine-cache calculix-ccx-doc calculix-ccx-test carmetal casacore-data-lines casacore-data-sources cava cclive cdlabelgen cecil cecil-flowanalysis cereal cfi chartkick.js checkbot checksecurity cheshire-clojure chewmail chronicle cl-abnf cl-asdf-finalizers cl-asdf-flv cl-asdf-system-connections cl-closure-common cl-command-line-arguments cl-containers cl-cxml cl-daemon cl-dynamic-classes cl-garbage-pools cl-github-v3 cl-launch cl-log cl-lparallel cl-markdown cl-metatilities-base cl-mustache cl-quri cl-rfc2388 cl-salza2 cl-sqlite cl-trivial-utf-8 cl-umlisp cl-umlisp-orf cl-utilities cl-uuid cl-yason cl-zip clamassassin clamav-unofficial-sigs class.js classycle clc-intercal clj-http-clojure clout-clojure coco-cs code2html combat commons-exec commons-pool compass-toolkit-plugin compojure-clojure concurrent-dfsg configure-debian conmux cons console-cyrillic courier-filter-perl couriergraph cpath-clojure crafty-bitmaps crafty-books-medium crafty-books-medtosmall crafty-books-small cream crossfire-maps crossfire-maps-small crypto-equality-clojure crypto-policies crypto-random-clojure cryptojs crystalcursors csmash-demosong css3pie ctapi cthumb ctop curvesapi cvs-buildpackage cvsdelta cvsutils cvsweb d3-tip.js dailystrips daptup db4o dbix-easy-perl dbus-sharp dbus-sharp-glib dd-plist ddtc debaux debdate debdry debget debian-dad debpear debroster delimmatch devpi-common dgen dh-rebar dhcpy6d dia-shapes dict-jargon dictem dictzip-java dirgra discover-data dish dizzy django-hvad django-measurement dkimproxy dl10n dnlib dns-browse dns323-firmware-tools doc-debian doc-linux-fr docbook docbook-dsssl docbook-ebnf docbook-html-forms docbook-mathml docbook-slides docbook-slides-demo docbook-utils docbook-website docbook-xsl-doc dokujclient doom-wad-shareware drbdlinks drgeo-doc drraw dtd-parser dtdparse durep dvcs-autosync dvd-slideshow dvi2ps-fontdata dvi2ps-fontdesc-morisawa5 dynalang dynamips ebook-dev-alp ecaccess eclipselink-jpa-2.1-spec edb edgar edict-el ehcache eigenbase-farrago eigenbase-resgen el-get elektra elida elscreen ember-media emdebian-archive-keyring epic4-help es-module-loader-0.17.js esnacc etoys evenement explorercanvas extra-xdg-menus faenza-icon-theme famfamfam-flag famfamfam-silk fasd fast-zip-clojure fb-music-high fccexam feed2imap felix-framework felix-gogo-command felix-gogo-runtime felix-gogo-shell fest-assert fest-test fest-util festival-ca festvox-don festvox-kallpc8k festvox-kdlpc16k festvox-kdlpc8k festvox-rablpc8k fetchyahoo fheroes2-pkg file-mmagic filepp fillets-ng-data finance-yahooquote fizmo flake8-docstrings flamethrower flare flask-mail flatlatex flotr fluid-soundfont flup focalinux foiltex fonts-alegreya-sans fonts-arkpandora fonts-averia-gwf fonts-averia-sans-gwf fonts-averia-serif-gwf fonts-babelstone-modern fonts-crosextra-carlito fonts-ddc-uchen fonts-dzongkha fonts-hosny-thabit fonts-inconsolata fonts-johnsmith-induni fonts-junction fonts-kaushanscript fonts-khmeros fonts-klaudia-berenika fonts-kristi fonts-larabie fonts-leckerli-one fonts-lg-aboriginal fonts-lklug-sinhala fonts-lobstertwo fonts-nafees fonts-ocr-b fonts-oflb-asana-math fonts-open-sans fonts-quattrocento fonts-radisnoir fonts-sambhota-tsugring fonts-sambhota-yigchung fonts-sil-tagmukay fonts-stix fonts-tibetan-machine fonts-tuffy fonts-ubuntu-title fonts-ukij-uyghur fonty-rg fort77 fortunes-bg fortunes-br fortunes-cs fortunes-eo fortunes-fr fortunes-ga fortunes-ru freetable fretsonfire-songs-muldjord fretsonfire-songs-sectoid fsharp funnelweb-doc funny-manpages fuzzysort galib games-thumbnails gap-transgrp gav-themes gearman-server gedit-latex-plugin geki3 genesisplusgx
Re: Porter roll call for Debian Bullseye
On 2020-11-20, Graham Inggs wrote: > A friendly reminder about the porter roll call for bullseye. > > On Mon, 2 Nov 2020 at 22:23, Graham Inggs wrote: >> We are doing a roll call for porters of all release architectures. If >> you are an active porter behind one of the release architectures [1] >> for the entire lifetime of Debian Bullseye (est. end of 2024), please >> respond with a signed email containing the following before Friday, >> November 27: > > Please note we don't automatically assume that porters for previous > releases will continue to do so. > If you were a porter for a previous release, we'd like you to sign up > again for bullseye. I know I'm a bit late to the party now... I do run both arm64 and armhf on numerous machines, mostly as part of the reproducible builds zoo. We mostly stick to stable for the main OS, but do run unstable and testing in chroots. I also sometimes run testing or individual packages from unstable on various other armhf and arm64 machines I use and make efforts to report and ideally fix bugs when encountered. I maintain u-boot and arm-trusted-firmware, used primarily on armhf and arm64. I do occasional debian-installer work and linux related work for both arm64 and armhf. I can most likely continue doing the above for the forseeable future. Not likely to fix deeply complicated toolchain issues. If all that qualifies for a porter hat, ok, if not, also ok. :) live well, vagrant signature.asc Description: PGP signature
Bug#945815: release.debian.org: unblock: ltsp/19.11-1
Package: release.debian.org Severity: normal X-Debbugs-CC: Vagrant Cascadian , debian-b...@lists.debian.org, debian-...@lists.debian.org The new version of LTSP no longer ships the ltsp-client-builder .udeb, so it should be removed from the relevent block-udeb rules. I believe debian-edu, the only user I'm aware of using the ltsp-client-builder .udeb is working on updating to the newer version of ltsp. The ltsp-client-builder .udeb may also need to be removed from testing, although it appears to be removed from sid, so maybe it's just a matter of waiting for some cleanup processes? Thanks all! unblock ltsp/19.11-1 live well, vagrant signature.asc Description: PGP signature
Re: testing migration aging and reproducible builds
On 2019-07-21, Chris Lamb wrote: > So, the devil is very much in the details here, alas. Whilst I am a > definite +1 on this idea the day-to-day experience may not be ideal > so your thoughts are very welcome. > > Just to take one recent example: I noticed yesterday a regression > whereby one of our tools (strip-nondeterminism) is causing a fair > number of Java packages to be unreproducible — it would seem a little > antisocial to block them from migrating to testing when it was "our" > fault. It is not really within the power or remit of the maintainers > in-question to fix this particular issue, and we should not implicitly > encourage maintainers to manually (!) fix it in each of the affected > packages just to get it to migrate... Indeed. > Note that delaying migration here has quite a different consent > and social dynamic to autopkgtest failures as the maintainers have, > by uploading a package that contains autopkgtests, implicitly opted > into the committment to ensure they continue to pass. > > Anyway, your thoughts on this important angle? This makes me think to decrease the delay for reproducible packages rather than increase the delay for unreproducible ones? Though then you'd want it to be a small increment... It's more of an incentive that way than a punishment, and humans tend to be more motivated by incentives rather than punishment... Still would hate for maintainers to be overly zealous in on-off fixes. >> For this to be possible, we would need to have an automated way to get >> data about the source packages > > Regarding the technical side of the implementation, we currently > generate this (~3MB bzipped) JSON file: > > https://tests.reproducible-builds.org/debian/reproducible.json.bz2 > > ... that (unless I am mistaken) is the data being used by qa.debian.org. I think it's: https://tests.reproducible-builds.org/reproducible-tracker.json Which only shows results for "bullseye" (formerly only "buster). We wanted to filter out the unstable and experimental suites from the tracker which may have larger numbers of variations (e.g. build path), some of which may be just be distracting to developers at this point until we have a more complete fix for those issues. I'm not sure relying on our test infrastructure at the moment is the right approach long-term, maybe fine in the short-term. We really need to start doing verification of buildd builds rather than simply rebuilding packages twice with variations. Was hoping to put together a BoF this week with DSA about that; maybe release team would also be interested? live well, vagrant signature.asc Description: PGP signature
Bug#929913: unblock: simple-cdd/0.6.7
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: vagr...@debian.org, debian-b...@lists.debian.org
Please unblock package simple-cdd
This update fixes several release-critical and important bugs, as well
as documentation updates.
Several issues were reported with expired keys in the archive keyring
breaking builds with simple-cdd, even when the expired key was not
used to verify the repositories being checked. This was fixed by
allowing expired keys to be present in the keyring used by reprepro
(though are not treated as valid for verifying Release files).
A typo was fixed that caused a traceback in gpg verification, and now
reports the failing command.
The --batch argument was added to gpg calls, which are all
non-interactive, which allows it to work in docker environments.
Contact information in the README was no longer valid, and so it was removed.
Fix a number of issues with changes in qemu arguments, and re-add the
missing support to pass arbitrary qemu options.
Update example configuration files, removing obsolete options and
adjusting a syntax change in some options which no longer support
variables.
The ltsp profile was updated to use the defaults for
ltsp-client-builder, with commented examples for using the non-default
values. NFS is no longer used in LTSP by default, so is no longer
configured, and the example to configure DHCP was updated to use
dnsmasq.
The test profile was updated with new and changed preseeding options,
as well as options passed to qemu.
The default profile updated the example to avoid asking to set up
another CD.
The router profile example ethernet interface name was updated to be
consistant with current naming conventions.
diff -Nru simple-cdd-0.6.6/README simple-cdd-0.6.7/README
--- simple-cdd-0.6.6/README 2018-04-22 17:11:33.0 -0700
+++ simple-cdd-0.6.7/README 2019-05-27 15:48:46.0 -0700
@@ -1,10 +1,5 @@
here's a quick guide to using simple-cdd...
-if you have further questions, ask on the simple-cdd-devel mailing list:
-http://lists.alioth.debian.org/mailman/listinfo/simple-cdd-devel, or in the
-debian-custom channel on irc.debian.org.
-
-
Quick Start (from http://wiki.debian.org/Simple-CDD/Howto)
To try Simple-CDD, on a Debian system:
diff -Nru simple-cdd-0.6.6/build-simple-cdd simple-cdd-0.6.7/build-simple-cdd
--- simple-cdd-0.6.6/build-simple-cdd 2018-04-22 20:36:26.0 -0700
+++ simple-cdd-0.6.7/build-simple-cdd 2019-05-28 15:39:42.0 -0700
@@ -532,8 +532,9 @@
if self.env.get("use_serial_console"):
qemu_opts.append("-nographic")
-# if [ -n "$mem" ]; then
-# qemu_opts="$qemu_opts -m $mem"
+if self.env.get("qemu_opts"):
+for opt in self.env.get('qemu_opts').split():
+qemu_opts.append(opt)
# Hard disk image
hd_img = os.path.join(self.env.get("simple_cdd_dir"),
"qemu-test.hd.img")
diff -Nru simple-cdd-0.6.6/debian/changelog simple-cdd-0.6.7/debian/changelog
--- simple-cdd-0.6.6/debian/changelog 2018-04-22 21:13:56.0 -0700
+++ simple-cdd-0.6.7/debian/changelog 2019-05-29 21:29:45.0 -0700
@@ -1,3 +1,41 @@
+simple-cdd (0.6.7) unstable; urgency=medium
+
+ [ Vagrant Cascadian ]
+ * Remove invalid contact information from README.
+ * Output command run on gpg verification failure rather than passing an
+undefined variable. (Closes: #919572, #929651). Thanks to Vladislav
+Tsendrovskii and Marc Fargas for the reports.
+ * Do not fail when expired keys are present in the keyring.
+(Closes: #928703, #929193). Thanks to Sebastien Delafond and Pradeep
+Nambiar.
+
+ [ Vagrant Cascadian ]
+ * Add back support for qemu_opts (Closes: #929660, #929636).
+ * Update qemu configuration from -std-vga to -vga std.
+ * Update example simple-cdd.conf and simple-cdd.conf.detailed, removing
+obsolete options and adjusting options requiring variables.
+(Closes: #909561).
+
+ [ Dirk Mayer ]
+ * added --batch param to gpg calls (Closes: #918102).
+
+ [ Vagrant Cascadian ]
+ * Update ltsp profile:
+- Use defaults for ltsp-client-builder.
+- Do not configure NFS, no longer used by default.
+- Use "ltsp-config dnsmasq" as it is the preferred DHCP server.
+ * Update test profile:
+- Add preseeding to avoid asking to set up another CD.
+- Use preseeding to select default boot device.
+- Update arguments for non-graphical console.
+- Allow rebooting for initial boot test.
+ * Update default profile:
+- Update question to avoid asking to set up another CD.
+ * Update router profile:
+- Update default example ethernet interface.
+
+ -- Vagrant Cascadian Wed, 29 May 2019 21:29:45 -0700
+
simple-cdd (0.6.6) unstable; urgency=medium
[ Jack Henschel ]
diff -Nru simple-cdd-0.6.6/profiles
Bug#929912: unblock: ltsp/5.18.12-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: vagr...@debian.org, debian-b...@lists.debian.org
Please unblock package ltsp
This fixes two release-critical bugs, an important bug, and updates
the debconf translation for Dutch.
Builds from unsigned CDs failed due to changes in apt being more
strict regarding unsigned repositories. This is fixed by passing the
--trust-file-mirror option introduced in ltsp-build-client upstream,
but not added to the default arguments for the ltsp-client-builder
.udeb. This .udeb is not used in the default debian-installer images,
and thus should have no impact on them.
The tool to build an LTSP chroot environment failed to detect the
codename in buster now that /etc/debian_version contains a version,
instead passing the version of Debian "10" to debootstrap, resulting
in a failure to build. The upstream fix was to switch back to using
lsb_release, and the patch applied to this version.
An important issue in the arguments for mounting loopback images was
discovered and fixed upstream, ensuring read-only mounts which might
otherwise lead to filesystem inconsistancies with ext4 or other
writeable filesystems, and fixing a typo in the loop argument passed
to mount. The upstream patch is included in this version.
Additionally, the Dutch debconf message translation was included in
this version.
diff -Nru ltsp-5.18.12/debian/changelog ltsp-5.18.12/debian/changelog
--- ltsp-5.18.12/debian/changelog 2018-12-24 17:30:09.0 -0800
+++ ltsp-5.18.12/debian/changelog 2019-05-29 13:02:07.0 -0700
@@ -1,3 +1,23 @@
+ltsp (5.18.12-3) unstable; urgency=medium
+
+ * ltsp-client-builder: Add --trust-file-mirror to ltsp-build-client
+options to fix builds from unsigned CDs (Closes: #929735).
+
+ -- Vagrant Cascadian Wed, 29 May 2019 13:02:07 -0700
+
+ltsp (5.18.12-2) unstable; urgency=medium
+
+ [ Frans Spiesschaert ]
+ * [INTL:nl] Dutch translation of debconf messages (Closes: #924103).
+
+ [ Vagrant Cascadian ]
+ * Add patch to fix loop mounting and ensure mount is read-only. Thanks
+to Alkis Georgopoulos.
+ * Add patch to fix codename detection (Closes: #925173). Thanks to
+Wolfgang Schweer.
+
+ -- Vagrant Cascadian Mon, 27 May 2019 04:58:46 -0700
+
ltsp (5.18.12-1) unstable; urgency=medium
* New upstream version.
diff -Nru ltsp-5.18.12/debian/ltsp-client-builder.templates
ltsp-5.18.12/debian/ltsp-client-builder.templates
--- ltsp-5.18.12/debian/ltsp-client-builder.templates 2018-12-24
17:15:33.0 -0800
+++ ltsp-5.18.12/debian/ltsp-client-builder.templates 2019-05-29
12:23:24.0 -0700
@@ -29,7 +29,7 @@
Template: ltsp-client-builder/build-client-opts
Type: string
-Default: --mirror file:///media/cdrom --security-mirror none --updates-mirror
none --accept-unsigned-packages
+Default: --mirror file:///media/cdrom --security-mirror none --updates-mirror
none --accept-unsigned-packages --trust-file-mirror
# Only used for preseeding arguments to ltsp-client-builder.
Description: for internal use: arguments for ltsp-build-client:
this option is meant to be used with debconf preseeding.
diff -Nru
ltsp-5.18.12/debian/patches/correct-typo-in-ltsploop-avoid-ext4-journal-p.patch
ltsp-5.18.12/debian/patches/correct-typo-in-ltsploop-avoid-ext4-journal-p.patch
---
ltsp-5.18.12/debian/patches/correct-typo-in-ltsploop-avoid-ext4-journal-p.patch
1969-12-31 16:00:00.0 -0800
+++
ltsp-5.18.12/debian/patches/correct-typo-in-ltsploop-avoid-ext4-journal-p.patch
2019-05-27 04:55:58.0 -0700
@@ -0,0 +1,24 @@
+From 5dcca1e8dcd864669ffa1cb36d89f832077a7243 Mon Sep 17 00:00:00 2001
+From: Alkis Georgopoulos
+Date: Sat, 25 May 2019 09:49:38 +0300
+Subject: Debian: correct typo in ltsploop, avoid ext4 journal
+ playback errors.
+
+---
+ client/Debian/share/initramfs-tools/scripts/nfs-bottom/ltsploop | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/client/Debian/share/initramfs-tools/scripts/nfs-bottom/ltsploop
b/client/Debian/share/initramfs-tools/scripts/nfs-bottom/ltsploop
+index 595e56ba..12bc4601 100755
+--- a/client/Debian/share/initramfs-tools/scripts/nfs-bottom/ltsploop
b/client/Debian/share/initramfs-tools/scripts/nfs-bottom/ltsploop
+@@ -45,5 +45,5 @@ if [ -f "${rootmnt}/${ltsploop}" ]; then
+mount -o move ${rootmnt} /ltsploop
+mkdir -p ${rootmnt}
+# TODO filesystem detection
+- mount -o ltsploop -t ${ltsploopfs} /ltsploop/${ltsploop} ${rootmnt}
++ mount -o loop,ro -t ${ltsploopfs} /ltsploop/${ltsploop} ${rootmnt}
+ fi
+--
+2.20.1
+
diff -Nru ltsp-5.18.12/debian/patches/fix-codename-detection.patch
ltsp-5.18.12/debian/patches/fix-codename-detection.patch
--- ltsp-5.18.12/debian/patches/fix-codename-detection.patch1969-12-31
16:00:00.0 -0800
+++ ltsp-5.18.12/debian/patches/fix-codename-detection.patch2019-05-27
04:54:47.0 -0700
@@
Bug#929731: unblock: flash-kernel/3.99
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: vagr...@debian.org, debian-b...@lists.debian.org Please unblock package flash-kernel This upload adds support for two additional boards, one additional name for another board, and updates the Uploaders list. The changes should be very low risk to existing platforms, and really appreciated by people with the added boards. diff -Nru flash-kernel-3.98/db/all.db flash-kernel-3.99/db/all.db --- flash-kernel-3.98/db/all.db 2019-04-04 14:37:13.0 -0700 +++ flash-kernel-3.99/db/all.db 2019-05-23 09:54:49.0 -0700 @@ -481,6 +481,13 @@ U-Boot-Script-Name: bootscr.sunxi Required-Packages: u-boot-tools +Machine: FriendlyARM NanoPi NEO 2 +Kernel-Flavors: arm64 +Boot-Script-Path: /boot/boot.scr +DTB-Id: allwinner/sun50i-h5-nanopi-neo2.dtb +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + Machine: Gemei G9 Tablet Kernel-Flavors: armmp Boot-Script-Path: /boot/boot.scr @@ -945,12 +952,20 @@ Required-Packages: u-boot-tools Machine: Marvell 8040 MACCHIATOBin +Machine: Marvell 8040 MACCHIATOBin Double-shot Machine: Marvell 8040 MACHIATOBin Kernel-Flavors: arm64 DTB-Id: marvell/armada-8040-mcbin.dtb Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools + +Machine: Marvell 8040 MACCHIATOBin Single-shot +Kernel-Flavors: arm64 +DTB-Id: marvell/armada-8040-mcbin-singleshot.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools # Marvell dev board has different names depending on how it's booted, # via DTB or older ATAGS diff -Nru flash-kernel-3.98/debian/changelog flash-kernel-3.99/debian/changelog --- flash-kernel-3.98/debian/changelog 2019-04-04 14:38:42.0 -0700 +++ flash-kernel-3.99/debian/changelog 2019-05-24 18:36:25.0 -0700 @@ -1,3 +1,18 @@ +flash-kernel (3.99) unstable; urgency=medium + + [ Domenico Andreoli ] + * Add support for NanoPi NEO2 (Closes: #928861). + + [ Cyril Brulebois ] + * Remove Christian Perrier from Uploaders, with many thanks for all +his contributions over the years! (Closes: #927488) + + [ Heinrich Schuchardt ] + * Add Marvell 8040 MACCHIATOBin Double-shot and Single-shot. +(Closes: #928951) + + -- Vagrant Cascadian Fri, 24 May 2019 18:36:25 -0700 + flash-kernel (3.98) unstable; urgency=medium [ Vagrant Cascadian ] diff -Nru flash-kernel-3.98/debian/control flash-kernel-3.99/debian/control --- flash-kernel-3.98/debian/control2019-02-27 22:52:45.0 -0800 +++ flash-kernel-3.99/debian/control2019-05-12 14:42:39.0 -0700 @@ -2,8 +2,7 @@ Section: utils Priority: optional Maintainer: Debian Install System Team -Uploaders: Christian Perrier , - Vagrant Cascadian , +Uploaders: Vagrant Cascadian , Karsten Merker Build-Depends: debhelper (>= 9), devio, linux-base (>= 3.2), dash Standards-Version: 3.9.6 unblock flash-kernel/3.99 Thanks for considering! live well, vagrant signature.asc Description: PGP signature
Bug#929097: unblock: u-boot/2019.01+dfsg-7
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal
X-Debbugs-CC: debian-b...@lists.debian.org
Please unblock package u-boot
This u-boot update fixes two minor CVEs with backported patches, one
for ext4 support and one with insufficiently random GPT partition
table generation.
It also is enables support for three additional platforms, which should
have little impact on existing platforms. Two of these additional
platforms have been enabled in debian-installer using u-boot binaries.
The already backported support for Teres-I platform was synced with
upstream, fixing USB support.
Support for the PocketBeagle was backported from upstream, which is
the largest part of the diff as it contains the device-tree for the
platform.
A small clarification was added to the u-boot-omap README to reduce
the risk of accidentally overwriting the partition table on the
am335x_beagleboneblack platform.
diff -Nru u-boot-2019.01+dfsg/debian/bin/u-boot-install-sunxi64
u-boot-2019.01+dfsg/debian/bin/u-boot-install-sunxi64
--- u-boot-2019.01+dfsg/debian/bin/u-boot-install-sunxi64 2019-04-19
15:21:52.0 -0700
+++ u-boot-2019.01+dfsg/debian/bin/u-boot-install-sunxi64 2019-05-13
18:03:24.0 -0700
@@ -6,9 +6,11 @@
case $(cat "${dtmodel}") in
Pinebook) TARGET="/usr/lib/u-boot/pinebook" ;;
Pine64+) TARGET="/usr/lib/u-boot/pine64_plus" ;;
+ "Pine64 LTS") TARGET="/usr/lib/u-boot/pine64-lts" ;;
"Olimex A64-Olinuxino") TARGET="/usr/lib/u-boot/a64-olinuxino/"
;;
"Olimex A64 Teres-I") TARGET="/usr/lib/u-boot/teres_i/" ;;
"OrangePi Zero Plus2")
TARGET="/usr/lib/u-boot/orangepi_zero_plus2/" ;;
+ "FriendlyARM NanoPi NEO 2")
TARGET="/usr/lib/u-boot/nanopi_neo2/" ;;
esac
fi
diff -Nru u-boot-2019.01+dfsg/debian/changelog
u-boot-2019.01+dfsg/debian/changelog
--- u-boot-2019.01+dfsg/debian/changelog2019-04-19 16:43:08.0
-0700
+++ u-boot-2019.01+dfsg/debian/changelog2019-05-13 19:07:44.0
-0700
@@ -1,3 +1,32 @@
+u-boot (2019.01+dfsg-7) unstable; urgency=medium
+
+ [ Sunil Mohan Adapa ]
+ * Enable pine64-lts target in u-boot-sunxi (Closes: #928947).
+
+ [ Vagrant Cascadian ]
+ * u-boot-omap: Enable am335x_evm target.
+ * Add patches to enable PocketBeagle in am335x_evm target.
+ * u-boot-omap: Fix instructions for installing beaglebone black.
+
+ -- Vagrant Cascadian Mon, 13 May 2019 19:07:44 -0700
+
+u-boot (2019.01+dfsg-6) unstable; urgency=medium
+
+ [ Domenico Andreoli ]
+ * Enable support for NanoPi NEO 2 in u-boot-sunxi (Closes: #928612).
+
+ [ Jonas Smedegaard ]
+ * Sync sunxi teres-i patch with mainline u-boot, enabling USB
+support (Closes: #928815).
+
+ [ Vagrant Cascadian ]
+ * Apply patch from upstream fixing buffer overflow with ext4 filesystems
+(CVE-2019-11059, Closes: #928800).
+ * Apply patch from upstream fixing randomly generated
+UUIDs. (CVE-2019-11690, Closes: #928557).
+
+ -- Vagrant Cascadian Sat, 11 May 2019 18:20:19 -0700
+
u-boot (2019.01+dfsg-5) unstable; urgency=medium
[ Jonas Smedegaard ]
diff -Nru
u-boot-2019.01+dfsg/debian/patches/pocketbeagle/0001-ti-Add-device-tree-for-am335x-pocketbeagle.patch
u-boot-2019.01+dfsg/debian/patches/pocketbeagle/0001-ti-Add-device-tree-for-am335x-pocketbeagle.patch
---
u-boot-2019.01+dfsg/debian/patches/pocketbeagle/0001-ti-Add-device-tree-for-am335x-pocketbeagle.patch
1969-12-31 16:00:00.0 -0800
+++
u-boot-2019.01+dfsg/debian/patches/pocketbeagle/0001-ti-Add-device-tree-for-am335x-pocketbeagle.patch
2019-05-13 18:47:19.0 -0700
@@ -0,0 +1,401 @@
+From 59a1df084f4a47e98d31cdc483a514575d8ff676 Mon Sep 17 00:00:00 2001
+From: Vagrant Cascadian
+Date: Mon, 29 Apr 2019 16:12:29 -0700
+Subject: [PATCH 1/2] ti: Add device-tree for am335x-pocketbeagle.
+
+Add device-tree files from linux 5.1-rc7 needed to complete support
+for PocketBeagle.
+
+Signed-off-by: Vagrant Cascadian
+Reviewed-by: Tom Rini
+---
+ arch/arm/dts/Makefile | 1 +
+ arch/arm/dts/am335x-osd335x-common.dtsi | 124 +
+ arch/arm/dts/am335x-pocketbeagle.dts| 237
+ 3 files changed, 362 insertions(+)
+ create mode 100644 arch/arm/dts/am335x-osd335x-common.dtsi
+ create mode 100644 arch/arm/dts/am335x-pocketbeagle.dts
+
+Index: u-boot/arch/arm/dts/Makefile
+===
+--- u-boot.orig/arch/arm/dts/Makefile
u-boot/arch/arm/dts/Makefile
+@@ -190,6 +190,7 @@ dtb-$(CONFIG_AM33XX) += am335x-boneblack
+ am335x-evmsk.dtb \
+ am335x-bonegreen.dtb \
+ am335x-icev2.dtb \
++ am335x-pocketbeagle.dtb \
+
Bug#927482: unblock: u-boot/2019.01+dfsg-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: debian-b...@lists.debian.org Please unblock package u-boot This upload is adds support for two more systems; orangepi_zero_plus2 was simply a matter of enabling the target, while the teres_i laptop also required backporting a fix from upstream and adding a configuration and device-tree for the board. The u-boot-install-sunxi64 helper script was modified to auto-detect both of these boards. All changes should be low risk for regressions in other boards. diff -Nru u-boot-2019.01+dfsg/debian/bin/u-boot-install-sunxi64 u-boot-2019.01+dfsg/debian/bin/u-boot-install-sunxi64 --- u-boot-2019.01+dfsg/debian/bin/u-boot-install-sunxi64 2019-04-08 14:01:19.0 -0700 +++ u-boot-2019.01+dfsg/debian/bin/u-boot-install-sunxi64 2019-04-19 15:21:52.0 -0700 @@ -7,6 +7,8 @@ Pinebook) TARGET="/usr/lib/u-boot/pinebook" ;; Pine64+) TARGET="/usr/lib/u-boot/pine64_plus" ;; "Olimex A64-Olinuxino") TARGET="/usr/lib/u-boot/a64-olinuxino/" ;; + "Olimex A64 Teres-I") TARGET="/usr/lib/u-boot/teres_i/" ;; + "OrangePi Zero Plus2") TARGET="/usr/lib/u-boot/orangepi_zero_plus2/" ;; esac fi diff -Nru u-boot-2019.01+dfsg/debian/changelog u-boot-2019.01+dfsg/debian/changelog --- u-boot-2019.01+dfsg/debian/changelog2019-04-08 19:47:02.0 -0700 +++ u-boot-2019.01+dfsg/debian/changelog2019-04-19 16:43:08.0 -0700 @@ -1,3 +1,15 @@ +u-boot (2019.01+dfsg-5) unstable; urgency=medium + + [ Jonas Smedegaard ] + * Add patch cherry-picked upstream to add i2c initialization for sun50i. + * Add patch by Vasily Khoruzhick to support Olimex Teres-I DIY laptop. + * Enable teres_i target in u-boot-sunxi (Closes: #926040). + + [ Frédéric Danis ] + * Enable orangepi_zero_plus2 target in u-boot-sunxi (Closes: #927224). + + -- Vagrant Cascadian Fri, 19 Apr 2019 16:43:08 -0700 + u-boot (2019.01+dfsg-4) unstable; urgency=medium [ Martyn Welch ] diff -Nru u-boot-2019.01+dfsg/debian/patches/series u-boot-2019.01+dfsg/debian/patches/series --- u-boot-2019.01+dfsg/debian/patches/series 2019-04-08 14:01:19.0 -0700 +++ u-boot-2019.01+dfsg/debian/patches/series 2019-04-19 15:21:52.0 -0700 @@ -26,3 +26,6 @@ # Patches to fix https://bugs.debian.org/923379 dreamplug/ARM-kirkwood-add-spi0-alias-for-dreamplug.patch dreamplug/Commit-ARM-CPU-arm926ejs-Consolidate-cache-routines-.patch + +sunxi/sun50i_i2c_init.patch +sunxi/teres-i.patch diff -Nru u-boot-2019.01+dfsg/debian/patches/sunxi/sun50i_i2c_init.patch u-boot-2019.01+dfsg/debian/patches/sunxi/sun50i_i2c_init.patch --- u-boot-2019.01+dfsg/debian/patches/sunxi/sun50i_i2c_init.patch 1969-12-31 16:00:00.0 -0800 +++ u-boot-2019.01+dfsg/debian/patches/sunxi/sun50i_i2c_init.patch 2019-04-19 15:21:52.0 -0700 @@ -0,0 +1,71 @@ +Description: add i2c initialization for sun50i + To use TWI0/1/2 the user can select CONFIG_I2C#_ENABLE. + However even the controller is enabled, the mux for the pins + are not set. + . + This patch follows the existing mux method. Since the pads are + different, separate check is added for each i2c. + . + Tested with A64-SOM204 board. +Author: Stefan Mavrodiev +Tested-by: Jonas Smedegaard +Origin: https://git.denx.de/?p=u-boot.git;a=commit;h=da1ae59 +Last-Update: 2019-04-14 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/arch/arm/include/asm/arch-sunxi/gpio.h b/arch/arm/include/asm/arch-sunxi/gpio.h +@@ -176,6 +176,7 @@ + + #define SUN5I_GPE_SDC23 + #define SUN8I_GPE_TWI23 ++#define SUN50I_GPE_TWI2 3 + + #define SUNXI_GPF_SDC02 + #define SUNXI_GPF_UART0 4 +@@ -193,8 +194,10 @@ + #define SUN4I_GPH_SDC15 + #define SUN6I_GPH_TWI02 + #define SUN8I_GPH_TWI02 ++#define SUN50I_GPH_TWI0 2 + #define SUN6I_GPH_TWI12 + #define SUN8I_GPH_TWI12 ++#define SUN50I_GPH_TWI1 2 + #define SUN6I_GPH_TWI22 + #define SUN6I_GPH_UART0 2 + #define SUN9I_GPH_UART0 2 +--- a/board/sunxi/board.c b/board/sunxi/board.c +@@ -98,6 +98,10 @@ + sunxi_gpio_set_cfgpin(SUNXI_GPH(2), SUN8I_GPH_TWI0); + sunxi_gpio_set_cfgpin(SUNXI_GPH(3), SUN8I_GPH_TWI0); + clock_twi_onoff(0, 1); ++#elif defined(CONFIG_MACH_SUN50I) ++ sunxi_gpio_set_cfgpin(SUNXI_GPH(0), SUN50I_GPH_TWI0); ++ sunxi_gpio_set_cfgpin(SUNXI_GPH(1), SUN50I_GPH_TWI0); ++ clock_twi_onoff(0, 1); + #endif + #endif + +@@ -120,6 +124,10 @@ + sunxi_gpio_set_cfgpin(SUNXI_GPH(4), SUN8I_GPH_TWI1); + sunxi_gpio_set_cfgpin(SUNXI_GPH(5), SUN8I_GPH_TWI1); + clock_tw
Bug#926831: unblock: u-boot/2019.01+dfsg-4
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal X-Debbugs-Cc: debian-b...@lists.debian.org Please unblock package u-boot This upload enables support for four additional boards, and should have a very low risc of regressions for existing boards, as no code was changed. Unfortunately debian-installer appears to be blocked from migrating to testing due to u-boot. diff -Nru u-boot-2019.01+dfsg/debian/changelog u-boot-2019.01+dfsg/debian/changelog --- u-boot-2019.01+dfsg/debian/changelog2019-02-28 20:42:31.0 -0800 +++ u-boot-2019.01+dfsg/debian/changelog2019-04-08 19:47:02.0 -0700 @@ -1,3 +1,13 @@ +u-boot (2019.01+dfsg-4) unstable; urgency=medium + + [ Martyn Welch ] + * [armhf] u-boot-imx: Enable build for NXP SABRE Lite. + + [ Neil Armstrong ] + * [arm64] u-boot-amlogic: Enable nanopi-k2 and khadas-vim/vim2. + + -- Vagrant Cascadian Mon, 08 Apr 2019 19:47:02 -0700 + u-boot (2019.01+dfsg-3) unstable; urgency=medium [ Romain Perier ] diff -Nru u-boot-2019.01+dfsg/debian/targets u-boot-2019.01+dfsg/debian/targets --- u-boot-2019.01+dfsg/debian/targets 2019-02-28 20:38:15.0 -0800 +++ u-boot-2019.01+dfsg/debian/targets 2019-04-08 14:01:19.0 -0700 @@ -37,6 +37,9 @@ # Rick Thomas , Cubox-i4x4, Cubox-i4PRO armhf imx mx6cuboxi u-boot.img SPL +# Martyn Welch +armhf imx mx6qsabrelite u-boot.imx + # Hector Oron armhf imx nitrogen6q u-boot.imx @@ -165,9 +168,16 @@ # Ian Campbell armhf tegra jetson-tk1 u-boot-tegra.bin +# Neil Armstrong +arm64 amlogic khadas-vim u-boot.bin +arm64 amlogic khadas-vim2 u-boot.bin + # Frederic Danis arm64 amlogic libretech-ccu-boot.bin +# Neil Armstrong +arm64 amlogic nanopi-k2 u-boot.bin + # Vagrant Cascadian arm64 amlogic odroid-c2 u-boot.bin diff -Nru u-boot-2019.01+dfsg/debian/u-boot-amlogic.install u-boot-2019.01+dfsg/debian/u-boot-amlogic.install --- u-boot-2019.01+dfsg/debian/u-boot-amlogic.install 2019-02-28 20:38:15.0 -0800 +++ u-boot-2019.01+dfsg/debian/u-boot-amlogic.install 2019-04-08 14:01:19.0 -0700 @@ -1,2 +1,2 @@ #!/bin/sh -debian/bin/u-boot-install-targets amlogic "board/amlogic/odroid-c2/README.odroid-c2 board/amlogic/p212/README.libretech-cc" +debian/bin/u-boot-install-targets amlogic "board/amlogic/odroid-c2/README.odroid-c2 board/amlogic/odroid-c2/README.nanopi-k2 board/amlogic/p212/README.khadas-vim board/amlogic/p212/README.libretech-cc board/amlogic/q200/README.khadas-vim2" unblock u-boot/2019.01+dfsg-4 live well, vagrant signature.asc Description: PGP signature
Re: Fixing stretch debian-installer on armhf
On 2019-03-09, Adam D. Barratt wrote: > On Thu, 2019-03-07 at 22:01 +, Ben Hutchings wrote: >> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote: >> [...] >> > > * Rebuild the debian-installer images, pulling in updates from >> > > stretch-updates, leaving only armhf netboot targets broken. >> > >> > Expanding a bit: rebuilding src:debian-installer from the stretch >> > branch, which has s-p-u enabled, would fetch the fixed kernel and a >> > couple of its udebs, at build time; the resulting netboot images >> > wouldn't know about s-p-u though at run time, and would try to load >> > udebs from stretch. >> >> [...] >> >> Why is that a problem? The only change made in 4.9.144-3.1 is in the >> kernel image, and the module udebs don't have versioned dependencies. > > However, as an additional data point, the kernel currently sat in NEW > and destined for stable has an ABI bump. If that's accepted, then I > assume things will "just work" in the meantime as the old binary > packages will hang around until they're decrufted, but it's worth > bearing in mind. A debian-installer build for stretch-proposed-updates was made, which may not get merged into stretch before the next point release. For the time being: https://deb.debian.org/debian/dists/stretch-proposed-updates/main/installer-armhf/ I've successfully tested version "20170615+deb9u5+b3", as well as at least one other person. It should continue to work until the next point release, and I'll do at least some minimal testing of the next point release on armhf before pushing it to stretch so this doesn't happen again. More details in: https://bugs.debian.org/924129 live well, vagrant signature.asc Description: PGP signature
Re: Bug#924129: debian-installer: Kernel for armhf for stretch unbootable
On 2019-03-26, Adam D. Barratt wrote: > On 2019-03-15 06:44, Adam D. Barratt wrote: >> The updated images for armhf have been available in p-u for a couple of >> days now. >> >> Feedback would be appreciated, as we would like to be able to accept >> the new kernel upload into p-u, which will block a further rebuild here >> as it brings an ABI bump. (The existing images should continue to work >> until the older packages are decrufted in the next point release.) > > Thanks to Peter for the feedback. > > Vagrant (or anyone else) - anything to add? Just tested fine on BananaPI: https://cdn-aws.deb.debian.org/debian/dists/stretch-proposed-updates/main/installer-armhf/20170615+deb9u5+b3/images/netboot/netboot.tar.gz Installed to SATA. No surprises or anything unusual. I'd say it's ready; please push it into stretch. live well, vagrant signature.asc Description: PGP signature
Re: Bug#924129: debian-installer: Kernel for armhf for stretch unbootable
On 2019-03-10, Cyril Brulebois wrote: > Vagrant Cascadian (2019-03-09): >> >> Thanks for your report; that's known and fixed on the kernel side >> >> already; how to deal with d-i is discussed in: >> >> https://lists.debian.org/debian-boot/2019/03/msg00165.html >> >> >> >> Currently waiting on some input from Vagrant: >> >> https://lists.debian.org/debian-boot/2019/03/msg00179.html >> >> I rebuilt the package from the stretch git branch on armhf against >> stretch+stretch-updates, and the build went fine. I tested the netboot >> image and it too seems to be working. > > Thanks for checking. > > Assuming you meant stretch + stretch-proposed-updates, meaning an > unchanged source package No changes from the git branch, other than a changelog entry to bump the version. I had to double-check since stretch-proposed-updates wasn't in my apt sources in the chroot... INFO: using 'http://deb.debian.org/debian' for stretch-proposed-updates Using generated sources.list.udeb: deb [trusted=yes] copy:/<>/build/ localudebs/ deb http://deb.debian.org/debian stretch main/debian-installer deb http://deb.debian.org/debian stretch-proposed-updates main/debian-installer make[8]: 'sources.list.udeb' is up to date. >From the build log, Looks like it did indeed pull in from stretch-proposed-updates. > I've asked the release team (cc-ed), and it was confirmed binNMUing > debian-installer seems appropriate. This will be done shortly. Great! live well, vagrant
Re: Fixing stretch debian-installer on armhf
On 2019-03-07, Ben Hutchings wrote: > On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote: > [...] >> > * Rebuild the debian-installer images, pulling in updates from >> > stretch-updates, leaving only armhf netboot targets broken. >> >> Expanding a bit: rebuilding src:debian-installer from the stretch >> branch, which has s-p-u enabled, would fetch the fixed kernel and a >> couple of its udebs, at build time; the resulting netboot images >> wouldn't know about s-p-u though at run time, and would try to load >> udebs from stretch. > [...] > > Why is that a problem? The only change made in 4.9.144-3.1 is in the > kernel image, and the module udebs don't have versioned dependencies. If that's indeed the case, then that does seem like the best approach. Happy to test images to confirm. live well, vagrant signature.asc Description: PGP signature
Fixing stretch debian-installer on armhf
Due to #922478, the debian-installer images for stretch are currently not bootable on the armhf architecture. While the linux kernel packages have been fixed in stretch-updates and stretch-proposed-updates, the debian-installer images still were built with the broken kernel. Even rebuilding the debian-installer images, while pulling in a working kernel that would boot, debian-installer would load .udeb modules from stretch, not stretch-updates. This might be ok for hd-media targets or targets that do not load module .udeb files from the network, but netboot targets are not likely to work at all. So some of the options at the moment appear to be: * Wait for another point release, rebuild debian-installer, leaving debian-installer on armhf broken until then. How long till the next point release? * Rebuild the debian-installer images, pulling in updates from stretch-updates, leaving only armhf netboot targets broken. * Another point release with the kernel update sooner than planned, and rebuild debian-installer images. * Other options? In the future, I plan on setting up at least one or two of armhf machines running stable-proposed-updates to try to catch this sort of thing before release... live well, vagrant signature.asc Description: PGP signature
Bug#890791: stretch-pu: package dpkg/1.18.25
On 2018-05-12, Karsten Merker wrote: > On Sun, Apr 22, 2018 at 12:39:42AM +0200, Manuel A. Fernandez Montecelo wrote: >> 2018-04-20 1:52 GMT+02:00 Guillem Jover : >> > On Wed, 2018-02-28 at 18:45:49 +, Adam D. Barratt wrote: >> >> On Wed, 2018-02-28 at 16:05 +0100, Manuel A. Fernandez Montecelo wrote: >> >> > 2018-02-18 22:26 Guillem Jover: >> >> > > I'd like to update dpkg in stretch. This includes several fixes for >> >> > > documentation, regressions, misbheavior, minor security issues, and >> >> > > a new arch definition so that DAK can accept packages using it. The >> >> > > fixes have been in sid/buster for a while now. >> >> > >> >> > We depend on this version being accepted and installed in the systems >> >> > where DAK lives to learn about the new architecture. After that, >> >> > several other packages can add support for the architecture, without >> >> > receiving an automatic reject when uploaded. >> >> > >> >> > It would be great if this update could enter in the next stable >> >> > update, so we can make progress on that front. >> > >> >> We've been discussing this amongst the SRMs and are quite wary of a >> >> dpkg update this close to the p-u freeze. We appreciate that the >> >> changes individually seem self-contained but would like to have an >> >> update of such a key package able to be tested more than is feasible in >> >> the time available. >> >> >> >> (On a related note, in practical terms it's very unlikely that there >> >> would be sufficient time to get the new strings that are introduced >> >> translated.) >> > >> > Is there perhaps anything you are waiting for me to do here? >> > >> > For the strings I realized afterwards I can take the ones from sid. >> > I've not yet checked how many, or if I'd really need a call for >> > translation, but I'd rather do that only after I know which parts you >> > are going to accept. :) But TBH, this being gettext I'm not sure it >> > matters that much, as only those strings might end up not being >> > translated and dpkg does not have 100% coverage for all languages >> > anyway. :) > [...] >> So in the 2+ months since that original request, we went from >> scattered packages outside the Debian infrastructure to having a port >> in debian-ports infra, with >60% of packages built. >> >> Unfortunately, important packages like binutils, glibc or linux-* have >> to stay in the separate "unreleased" suite for that reason, so the >> lack of support in dak for riscv64 is causing us to do this extra >> work, which would be otherwise unneeded > > To add some further information: having to always manually build > and upload a number of otherwise perfectly working essential > riscv64 packages like glibc to unreleased due to the missing > dpkg/stable update doesn't only cause unnecessary additional work > for the riscv64 porters but also poses practical problems for > package maintainers trying to sort out portability issues as they > cannot simply debootstrap a current riscv64 chroot (and therefore > easily use pbuilder) because debootstrap cannot handle pulling > the base system from more than one suite (unstable+unreleased in > this case). > > Previous stretch point releases have been published every 2.5-3 > months, and since the 9.4 release more than two months have > passed already, so I would again like to ask the stable release > managers what exactly they require to be done for the proposed > dpkg update to be accepted into the 9.5 release. Guillem had > asked a similar question already three weeks ago (see above), but > has AFAICS received no reply to it. I would really like to avoid > the dpkg/stable update necessary for proper riscv64 support being > pushed back yet another release cycle because of communication > issues... I hear mumblings of preparation for the next stable point release, and so wondering if there's any chance to get the dpkg patches necessary to enable riscv64 in dak before that happens? I had the impression the riscv64 patch of the patch was rather trivial. The riscv64 port has been hovering around the 80% mark for built packages, which is pretty exciting to see, and would be nice to keep that momentum going! live well, vagrant signature.asc Description: PGP signature
Bug#883612: unblock: ltsp/5.5.10-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: debian-b...@lists.debian.org As far as I can tell, ltsp is only blocked due to containing a .udeb, and there have been no code changes to the ltsp-client-builder .udeb since... 2015. At one point, there was an unblock-udeb hint for this, not sure if that's no longer applicable for some reason... live well, vagrant signature.asc Description: PGP signature
Bug#862746: unblock: simple-cdd/0.6.5
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-b...@lists.debian.org,
simple-cdd-de...@lists.alioth.debian.org
Thanks for all your work on the Release Team!
Please unblock package simple-cdd
With the recent announcement shutting down public FTP services:
https://lists.debian.org/debian-announce/2017/msg1.html
This requires some significant changes in simple-cdd, as simple-cdd
relied on Debian's FTP mirrors for downloading files discovered by FTP
directory listing.
Now simple-cdd uses http://deb.debian.org/debian/extrafiles, an
inline-signed list of checksums for various content in the archive
(notably, tools/*, docs/*). This also allows signature and checksum
verification of all downloaded files, which is a huge security
improvement.
The default mirror is now switched to deb.debian.org using the http
protocol.
A fix was added to add packages of priority required, important and
standard from security, updates and proposed-updates repositories to
the locally generated repository. Otherwise packages with strict
versioned dependencies would end up uninstallable (e.g. vim-tiny
depends on vim-common ( =$version), but only vim-common would get
updated, resulting in vim-tiny being uninstallable).
Kernel selection for i386 on jessie and stretch also required
updating, as the linux-image-486 packages were removed from the
archive.
No changes were made to the simple-cdd-profiles udeb, so should not
have any impact on debian-installer.
diff -Nru simple-cdd-0.6.4/build-simple-cdd simple-cdd-0.6.5/build-simple-cdd
--- simple-cdd-0.6.4/build-simple-cdd 2017-01-16 13:40:32.0 -0800
+++ simple-cdd-0.6.5/build-simple-cdd 2017-05-15 13:21:24.0 -0700
@@ -235,7 +235,11 @@
for a in self.env.get("ARCHES"):
if a == "alpha": self.env.append("kernel_packages",
kernel_base + "alpha-generic")
elif a == "armhf": self.env.append("kernel_packages",
kernel_base + "armmp")
-elif a == "i386": self.env.append("kernel_packages",
kernel_base + "486")
+elif a == "i386":
+if self.env.get("CODENAME") == "jessie":
+self.env.append("kernel_packages", kernel_base +
"586")
+else:
+self.env.append("kernel_packages", kernel_base +
"686")
elif a == "sparc": self.env.append("kernel_packages",
kernel_base + "sparc64")
elif a in ("amd64", "arm64", "sparc64") or
a.startswith("powerpc") or a.startswith("s390"):
self.env.append("kernel_packages", kernel_base + a)
diff -Nru simple-cdd-0.6.4/debian/changelog simple-cdd-0.6.5/debian/changelog
--- simple-cdd-0.6.4/debian/changelog 2017-01-17 15:10:07.0 -0800
+++ simple-cdd-0.6.5/debian/changelog 2017-05-15 14:10:37.0 -0700
@@ -1,3 +1,22 @@
+simple-cdd (0.6.5) unstable; urgency=medium
+
+ [ Vagrant Cascadian ]
+ * Switch to using urllib instead of calling wget.
+- Only re-download files if known checksums do not match.
+- Explicitly set http_proxy in the environment.
+- Verify "mirror_files" to download with archive's "extrafiles", a
+ signed list of checksums.
+- Switch default mirror to deb.debian.org and default protocol to
+ http (Closes: #861198).
+- Many thanks to Enrico Zini for code review and improvements.
+ * Update kernel package selection for i386.
+ * Add stanzas to pull in required, important and standard packages for
+ security, updates and proposed-updates when enabled.
+ * Fix bug causing tracebacks when checksum or file size verifications
+fail.
+
+ -- Vagrant Cascadian <vagr...@debian.org> Mon, 15 May 2017 14:10:37 -0700
+
simple-cdd (0.6.4) unstable; urgency=medium
[ Vagrant Cascadian ]
diff -Nru simple-cdd-0.6.4/profiles/ltsp.downloads
simple-cdd-0.6.5/profiles/ltsp.downloads
--- simple-cdd-0.6.4/profiles/ltsp.downloads2016-07-21 10:03:54.0
-0700
+++ simple-cdd-0.6.5/profiles/ltsp.downloads2017-04-28 15:46:08.0
-0700
@@ -2,4 +2,3 @@
xorg
udev
ltsp-server-standalone
-linux-image-486
diff -Nru simple-cdd-0.6.4/setup.py simple-cdd-0.6.5/setup.py
--- simple-cdd-0.6.4/setup.py 2016-11-27 17:05:05.0 -0800
+++ simple-cdd-0.6.5/setup.py 2017-05-15 13:59:12.0 -0700
@@ -3,7 +3,7 @@
from setuptools import setup
setup(name="simple-cdd",
- version="0.6.1",
+ version="0.6.5",
description="create custom debian-installer CDs",
long_description=&quo
Bug#859214: unblock: u-boot/u-boot_2016.11+dfsg1-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: Philip Hands <p...@hands.com>, Martin Michlmayr <t...@cyrius.com>, Rick Thomas <rbtho...@pobox.com> Please unblock package u-boot This version of u-boot re-enables the openrd targets and applies a patch patch from upstream fixing an issue that caused a failure to boot (a more technical explanation is included in the patch itself). This version also fixes a trivial typo on the documentation for u-boot-rpi. The reasons Martin requested openrd to be re-enabled for stretch: * stretch will be the last release to include support for the armel architecture, so it would be good to get support for this device as complete as possible. * While Debian can be installed with the default u-boot shipped on the OpenRD, the one provided by Debian is much more modern. Additionally, I'd note that it was supported in jessie's u-boot, so this would be a regression on upgrade to stretch. This will allow debian-installer to re-enable support for openrd images as well. A patched version has been tested by Phil Hands and Rick Thomas to work on at least two different openrd targets. diff -Nru u-boot-2016.11+dfsg1/debian/changelog u-boot-2016.11+dfsg1/debian/changelog --- u-boot-2016.11+dfsg1/debian/changelog 2016-12-21 20:44:44.0 -0800 +++ u-boot-2016.11+dfsg1/debian/changelog 2017-03-27 11:39:51.0 -0700 @@ -1,3 +1,17 @@ +u-boot (2016.11+dfsg1-4) unstable; urgency=medium + + [ Vagrant Cascadian ] + * [armel] Apply a patch from upstream to fix openrd targets which failed +to boot, and re-enable the openrd targets (Closes: #856441). Thanks to +Albert ARIBAUD for the patch, Martin Michlmayr for pointing out the +patch, and Phil Hands and Rick Thomas for testing on various openrd +platforms. + + [ Martin Michlmayr ] + * u-boot-rpi: typo in README.Debian (Closes: #858574). + + -- Vagrant Cascadian <vagr...@debian.org> Mon, 27 Mar 2017 14:39:51 -0400 + u-boot (2016.11+dfsg1-3) unstable; urgency=medium [ Peter Michael Green ] diff -Nru u-boot-2016.11+dfsg1/debian/patches/series u-boot-2016.11+dfsg1/debian/patches/series --- u-boot-2016.11+dfsg1/debian/patches/series 2016-12-21 20:11:16.0 -0800 +++ u-boot-2016.11+dfsg1/debian/patches/series 2017-03-27 11:21:55.0 -0700 @@ -32,3 +32,5 @@ orangepi_zero/0001-sunxi-add-proper-device-tree-for-Orange-Pi-Zero-boar.patch orangepi_zero/0002-sunxi-add-orangepi-zero-defconfig.patch + +upstream/openrd/0001-armv5te-make-ret-lr-produce-iinterworking-bx-lr.patch diff -Nru u-boot-2016.11+dfsg1/debian/patches/upstream/openrd/0001-armv5te-make-ret-lr-produce-iinterworking-bx-lr.patch u-boot-2016.11+dfsg1/debian/patches/upstream/openrd/0001-armv5te-make-ret-lr-produce-iinterworking-bx-lr.patch --- u-boot-2016.11+dfsg1/debian/patches/upstream/openrd/0001-armv5te-make-ret-lr-produce-iinterworking-bx-lr.patch 1969-12-31 16:00:00.0 -0800 +++ u-boot-2016.11+dfsg1/debian/patches/upstream/openrd/0001-armv5te-make-ret-lr-produce-iinterworking-bx-lr.patch 2017-03-27 11:21:55.0 -0700 @@ -0,0 +1,39 @@ +From 6b4e9426834580810790ecfa924979d61c5c1987 Mon Sep 17 00:00:00 2001 +From: Albert ARIBAUD <albert.u.b...@aribaud.net> +Date: Mon, 27 Feb 2017 20:19:07 +0100 +Subject: [PATCH] armv5te: make 'ret lr' produce iinterworking 'bx lr' + +Current ARM assembler helper for the 'return to caller' pseudo-instruction +turns 'ret lr' into 'mov pc, lr' for ARMv5TE. This causes the core to remain +in its current ARM state even when the routine doing the 'ret' was called +from Thumb-1 state, triggering an undefined instruction exception. + +This causes early run-time failures in all boards compiled using the Thumb-1 +instruction set (for instance the Open-RD family). + +ARMv5TE supports 'bx lr' which properly implements interworking and thus +correctly returns to Thumb-1 state from ARM state. + +This change makes 'ret lr' turn into 'bx lr' for ARMv5TE. + +Signed-off-by: Albert ARIBAUD <albert.u.b...@aribaud.net> +--- + arch/arm/include/asm/assembler.h | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/arch/arm/include/asm/assembler.h b/arch/arm/include/asm/assembler.h +index ae1e42fc06..c56daf2a1f 100644 +--- a/arch/arm/include/asm/assembler.h b/arch/arm/include/asm/assembler.h +@@ -59,7 +59,7 @@ + + .irpc,,eq,ne,cs,cc,mi,pl,vs,vc,hi,ls,ge,lt,gt,le,hs,lo + .macro ret\c, reg +-#if defined(__ARM_ARCH_5E__) || defined(__ARM_ARCH_5TE__) ++#if defined(__ARM_ARCH_5E__) + mov\c pc, \reg + #else + .ifeqs "\reg", "lr" +-- +2.11.0 + diff -Nru u-boot-2016.11+dfsg1/debian/targets u-boot-2016.11+dfsg1/debian/targets --- u-boot-2016.11+dfsg1/debian/targets 2016-12-21 20:11:16.0 -0800 +++ u-boot-2016.11+dfsg1/debian/targets 2017-03-27 11:21:55.0 -0700
Bug#853280: unblock: simple-cdd/0.6.4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-b...@lists.debian.org,
simple-cdd-de...@lists.alioth.debian.org
Please unblock package simple-cdd
The source package simple-cdd appears to be blocked due to the
simple-cdd-profiles udeb. This udeb is not used by debian-installer by
default, and the udeb hasn't changed at all since the version
currently in testing.
The new version fixes an issue in boolean handling treating any
specified value, including "false", as if it were True. It also fixes
a compatibility issue with newer versions of debian-cd. And also
supports the BOOT_TIMEOUT variable for generated CD images that use
grub2.
Thanks!
debdiff attached.
live well,
vagrant
diff -Nru simple-cdd-0.6.3/build-simple-cdd simple-cdd-0.6.4/build-simple-cdd
--- simple-cdd-0.6.3/build-simple-cdd 2016-11-27 17:05:05.0 -0800
+++ simple-cdd-0.6.4/build-simple-cdd 2017-01-16 13:40:32.0 -0800
@@ -111,13 +111,14 @@
for pathname in self.find_profile_files(p + ".conf"):
self.env.read_config_file(pathname)
-# Set default values for various mirrors
-if not self.env.get("security_mirror") and self.env.get("use_security_mirror"):
-self.env.set("security_mirror", "http://security.debian.org/;)
-if not self.env.get("updates_mirror") and self.env.get("use_updates_mirror"):
-self.env.set("updates_mirror", self.env.get("debian_mirror"))
-if not self.env.get("backports_mirror") and self.env.get("backports"):
-self.env.set("backports_mirror", self.env.get("debian_mirror"))
+# Disable security and updates mirrors for sid, as they do not exist.
+if self.env.get("CODENAME") == "sid":
+if self.env.get("security_mirror"):
+log.info("Disabling security mirror for sid.")
+self.env.set("security_mirror", "")
+if self.env.get("updates_mirror"):
+log.info("Disabling updates mirror for sid.")
+self.env.set("updates_mirror", "")
# Set defaults for debian-cd CONTRIB and NONFREE variables based on configured mirror components.
for component in self.env.get("mirror_components") + self.env.get("mirror_components_extra"):
@@ -172,9 +173,9 @@
for p in self.env.get("preseed_files"):
if verify_preseed_file(p): continue
if self.args.force_preseed:
-log.warn("preseed file invalid: %s", pathname)
+log.warn("preseed file invalid: %s", p)
else:
-raise Fail("preseed file invalid: %s", pathname)
+raise Fail("preseed file invalid: %s", p)
def paranoid_checks(self):
diff -Nru simple-cdd-0.6.3/debian/changelog simple-cdd-0.6.4/debian/changelog
--- simple-cdd-0.6.3/debian/changelog 2016-11-27 18:40:54.0 -0800
+++ simple-cdd-0.6.4/debian/changelog 2017-01-17 15:10:07.0 -0800
@@ -1,3 +1,20 @@
+simple-cdd (0.6.4) unstable; urgency=medium
+
+ [ Vagrant Cascadian ]
+ * tools/build/debian-cd: Set wget variable, which is used to download
+ d-i daily images.
+ * Default to enabling security and updates mirrors, and remove
+use_*_mirror booleans.
+
+ [ Boskovits, Gabriel ]
+ * Add patch to support BOOT_TIMEOUT with grub2.
+
+ [ Enrico Zini ]
+ * Tested reading booleans from .conf files, and fixed parsing their
+values.
+
+ -- Vagrant Cascadian <vagr...@debian.org> Tue, 17 Jan 2017 15:10:07 -0800
+
simple-cdd (0.6.3) unstable; urgency=medium
* Move setting of debian-cd CONTRIB/NONFREE after setting variables from
diff -Nru simple-cdd-0.6.3/simple_cdd/env.py simple-cdd-0.6.4/simple_cdd/env.py
--- simple-cdd-0.6.3/simple_cdd/env.py 2016-11-27 17:05:05.0 -0800
+++ simple-cdd-0.6.4/simple_cdd/env.py 2017-01-16 14:23:24.0 -0800
@@ -158,7 +158,7 @@
if isinstance(self.default, bool):
bval = self.default
else:
-bval = bool(super().default_to_string())
+bval = super().default_to_string() == "true"
return "true" if bval else ""
def to_python(self):
@@ -305,7 +305,7 @@
def set(self, name, value):
"""
-Set a value by name, converting value to the type of the variable name.
+Set a value by name, converting the python value to the type of the variable name.
"""
cur = self.env.get(name, None)
if cur is None:
@@ -313,6 +313,16 @@
cur.automatically_created = True
Re: Porter roll call for Debian Stretch
> I am an active porter for the following architectures and I intend > to continue this for the lifetime of the Stretch release (est. end > of 2020): Some people have suggested to me that I'm an active porter... maybe it just sort of happens to people. I'll likely continue to help in the following ways during the stretch release. > For armhf, I > - triage d-i bugs > - test d-i regularly > - fix d-i bugs/issues I do some debian-installer testing; the frequency and regularity varies depending on what projects I'm actively working on. I've submitted bugs and patches to enable several new armhf platforms by getting needed configuration options enabled in the linux, flash-kernel, debian-installer and u-boot packages. As the active u-boot maintainer, I do quite a bit of u-boot testing, and usually test new uploads against most of the armhf boards I have access to. Most of the platforms enabled in u-boot are armhf, followed by armel and arm64. > - maintain/provide hardware for (or assist with) automated tests on ci.d.n, > jenkins.d.n (etc.) Maintain 20+ build machines for the reproducible build network as part of jenkins.debian.net: https://tests.reproducible-builds.net Most of them do run debian stable with stable or backports kernels, and routinely build packages in experimental, unstable and testing chroots. > I am a DD. I don't have much of any opinions on compiler options to enable by default. I'll likely also start working more on arm64, but we'll see what the future holds in retrospect. I also have some waning experience with armel systems, which might seem less and less relevent by the end of stretch. live well, vagrant signature.asc Description: PGP signature
Bug#780070: unblock: u-boot/2014.10+dfsg1-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Thanks for all your work on the release team! Please unblock package u-boot It includes backported support for two new armhf capable boards, BananaPro and A20-OlinuXino-LIME2. Lintian overrides appropriate for these two boards were also added. Support for these boards has also been backported to linux, and enabled in debian-installer and flash-kernel. Adding support in u-boot would make these boards fully supported in jessie. Addition of these two boards should pose no problems for other existing builds, and only increases the size of the u-boot-sunxi package by about 2MB. The new version also fixes a FTBFS issue when built using newer versions of patch, as the cubox-i-support patch included a redundant file that was already present in the sources, and patch no longer supports this due to security issues (see bugs #777520 and #777518 for details on that). There was also a porter NMU done with a one-line patch to fix FTBFS on sh4, which is included in the uploads since the version in jessie. Unfortunately, There was some patch cruft in 2014.10+dfsg1-2 and one added in 2014.10+dfsg1-4, which I've filtered out with filterdiff in the debdiff below: $ debdiff u-boot_2014.10+dfsg1-2.dsc u-boot_2014.10+dfsg1-4.dsc | filterdiff --exclude=u-boot-2014.10+dfsg1/debian/patches/patches/* --exclude=u-boot-2014.10+dfsg1/debian/0001*.patch diff -Nru u-boot-2014.10+dfsg1/debian/0001-Backport-support-for-the-LeMaker-Banana-Pro-board-fr.patch u-boot-2014.10+dfsg1/debian/0001-Backport-support-for-the-LeMaker-Banana-Pro-board-fr.patch diff -Nru u-boot-2014.10+dfsg1/debian/changelog u-boot-2014.10+dfsg1/debian/changelog --- u-boot-2014.10+dfsg1/debian/changelog 2014-11-01 16:38:54.0 -0700 +++ u-boot-2014.10+dfsg1/debian/changelog 2015-03-08 11:13:14.0 -0700 @@ -1,3 +1,32 @@ +u-boot (2014.10+dfsg1-4) unstable; urgency=medium + + [ Karsten Merker ] + * Backport support for the LeMaker Banana Pro board (Closes: #779908). + + [ Vagrant Cascadian ] + * Update lintian rules for BananaPro and A20-OlinuXino-LIME2. + + -- Vagrant Cascadian vagr...@debian.org Sun, 08 Mar 2015 11:13:07 -0700 + +u-boot (2014.10+dfsg1-3) unstable; urgency=medium + + * cubox-i-support.diff: Refresh patch, dropping solidrun.bmp, which +causes FTBFS with newer version of patch (Closes: #777518). + + * Add patch to support A20-OLinuXino-LIME2, backported from u-boot +2015.01. Thanks to Karsten Merker for the patch (Closes: #777466). + + -- Vagrant Cascadian vagr...@debian.org Sat, 21 Feb 2015 13:13:31 -0800 + +u-boot (2014.10+dfsg1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches: +- Add sh4-fix-linker-name-prefix.patch to use the proper + linker name prefix on sh4. Fixes FTBFS. (Closes: #771747) + + -- John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de Thu, 11 Dec 2014 00:00:08 +0100 + u-boot (2014.10+dfsg1-2) unstable; urgency=medium [ Steve Langasek ] diff -Nru u-boot-2014.10+dfsg1/debian/patches/A20-OLinuXino-LIME2/sun7i-Add-support-for-Olimex-A20-OLinuXino-LIME2.patch u-boot-2014.10+dfsg1/debian/patches/A20-OLinuXino-LIME2/sun7i-Add-support-for-Olimex-A20-OLinuXino-LIME2.patch --- u-boot-2014.10+dfsg1/debian/patches/A20-OLinuXino-LIME2/sun7i-Add-support-for-Olimex-A20-OLinuXino-LIME2.patch 1969-12-31 16:00:00.0 -0800 +++ u-boot-2014.10+dfsg1/debian/patches/A20-OLinuXino-LIME2/sun7i-Add-support-for-Olimex-A20-OLinuXino-LIME2.patch 2015-03-08 11:03:53.0 -0700 @@ -0,0 +1,99 @@ +From d71910fc509933fab881f85ae244ea95525a41d6 Mon Sep 17 00:00:00 2001 +From: Iain Paton ipat...@gmail.com +Date: Sun, 28 Sep 2014 14:18:42 +0100 +Subject: [PATCH 1/1] sun7i: Add support for Olimex A20-OLinuXino-LIME2 +Origin: http://git.denx.de/?p=u-boot.git;a=patch;h=d71910fc509933fab881f85ae244ea95525a41d6;hp=5b3ee386fde82a1ba42ff09b95247842c9a1585e + +This adds support for the Olimex A20-OLinuXino-Lime2 +https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2 + +Differences to previous Lime boards are 1GB RAM and gigabit ethernet + +Signed-off-by: Iain Paton ipat...@gmail.com +Signed-off-by: Hans de Goede hdego...@redhat.com +--- + board/sunxi/MAINTAINERS |6 ++ + board/sunxi/Makefile |1 + + board/sunxi/dram_a20_olinuxino_l2.c | 31 +++ + configs/A20-OLinuXino-Lime2_defconfig |5 + + 4 files changed, 43 insertions(+) + create mode 100644 board/sunxi/dram_a20_olinuxino_l2.c + create mode 100644 configs/A20-OLinuXino-Lime2_defconfig + +diff --git a/board/sunxi/MAINTAINERS b/board/sunxi/MAINTAINERS +index 4f32195..4ed82cf 100644 +--- a/board/sunxi/MAINTAINERS b/board/sunxi/MAINTAINERS +@@ -38,3 +38,9 @@ M: FUKAUMI Naoki nao...@gmail.com + S:Maintained + F:board/sunxi/dram_a20_olinuxino_l.c + F:configs/A20-OLinuXino
Bug#778368: unblock: ltsp/5.5.4-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ltsp ltsp 5.5.4-3 fixes an RC bug in ltsp removing obsolete config files from pre-wheezy versions of ltsp. It also removes an ugly, hackish workaround no longer required due to fixing an RC bug in LDM. It does ship a .udeb, but there are no changes to anything that would impact the .udeb, and the .udeb isn't used in debian-installer by default. diff -Nru ltsp-5.5.4/debian/changelog ltsp-5.5.4/debian/changelog --- ltsp-5.5.4/debian/changelog 2014-12-01 15:22:13.0 -0800 +++ ltsp-5.5.4/debian/changelog 2015-02-12 14:22:57.0 -0800 @@ -1,3 +1,16 @@ +ltsp (5.5.4-3) unstable; urgency=medium + + * Add debian/ltsp-client-core.maintscript to remove obsolete +/etc/init.d/ltsp-client-setup and /etc/default/ltsp-client-setup +leftover from squeeze upgrades (Closes: #777184). Thanks to Andreas +Beckmann! + + * Apply patch from upstream to no longer remove nouveau_vieux driver on +boot, which is terribly hackish and no longer appropriate with current +versions of LDM (Closes: #767764). + + -- Vagrant Cascadian vagr...@debian.org Thu, 12 Feb 2015 14:22:07 -0800 + ltsp (5.5.4-2) unstable; urgency=medium * ltsp-update-kernels/update-kernels: Fix kernel version sorting that diff -Nru ltsp-5.5.4/debian/ltsp-client-core.maintscript ltsp-5.5.4/debian/ltsp-client-core.maintscript --- ltsp-5.5.4/debian/ltsp-client-core.maintscript 1969-12-31 16:00:00.0 -0800 +++ ltsp-5.5.4/debian/ltsp-client-core.maintscript 2015-02-10 10:30:16.0 -0800 @@ -0,0 +1,2 @@ +rm_conffile /etc/init.d/ltsp-client-setup 5.5.4-3~ +rm_conffile /etc/default/ltsp-client-setup 5.5.4-3~ diff -Nru ltsp-5.5.4/debian/patches/series ltsp-5.5.4/debian/patches/series --- ltsp-5.5.4/debian/patches/series2014-12-01 15:16:53.0 -0800 +++ ltsp-5.5.4/debian/patches/series2015-02-09 00:51:21.0 -0800 @@ -8,3 +8,4 @@ upstream/0016-update-kernels-Fix-issues-with-kernel-version-varian.patch upstream/0017-Debian-update-kernels.conf-Prefer-586-over-486-in-fo.patch upstream/0018-update-kernels-Quiet-down-mkimage-output-when-genera.patch +upstream/0020-Drop-hack-to-remove-nouveau_vieux-driver-as-newer-ve.patch diff -Nru ltsp-5.5.4/debian/patches/upstream/0020-Drop-hack-to-remove-nouveau_vieux-driver-as-newer-ve.patch ltsp-5.5.4/debian/patches/upstream/0020-Drop-hack-to-remove-nouveau_vieux-driver-as-newer-ve.patch --- ltsp-5.5.4/debian/patches/upstream/0020-Drop-hack-to-remove-nouveau_vieux-driver-as-newer-ve.patch 1969-12-31 16:00:00.0 -0800 +++ ltsp-5.5.4/debian/patches/upstream/0020-Drop-hack-to-remove-nouveau_vieux-driver-as-newer-ve.patch 2015-02-09 00:48:21.0 -0800 @@ -0,0 +1,25 @@ +From 79a57b29d5d4ec6c0ec2945ef60a6c81ff365b90 Mon Sep 17 00:00:00 2001 +From: Vagrant Cascadian vagr...@debian.org +Date: Sun, 8 Feb 2015 22:40:45 -0800 +Subject: [PATCH] Drop hack to remove nouveau_vieux driver, as newer versions + of LDM will no longer hard-code LIBGL_ALWAYS_INDIRECT. + https://bugs.launchpad.net/ltsp/+bug/1072711 + +--- + client/share/ltsp/init-ltsp.d/50-opengl | 4 + 1 file changed, 4 deletions(-) + delete mode 100644 client/share/ltsp/init-ltsp.d/50-opengl + +diff --git a/client/share/ltsp/init-ltsp.d/50-opengl b/client/share/ltsp/init-ltsp.d/50-opengl +deleted file mode 100644 +index d9de1eb..000 +--- a/client/share/ltsp/init-ltsp.d/50-opengl /dev/null +@@ -1,4 +0,0 @@ +-if boolean_is_true $LDM_DIRECTX ! boolean_is_true $LTSP_FATCLIENT; then +-# Work around LP bug #1072711 +-rm -f /usr/lib/i386-linux-gnu/dri/nouveau_vieux_dri.so +-fi +-- +2.1.4 + unblock ltsp/5.5.4-3 Thanks for all your work on the release team! live well, vagrant signature.asc Description: PGP signature
Bug#775585: (pre-approval) unblock: git-remote-bzr/0.2+20140705-2
Control: tags -1 -moreinfo On 2015-01-17, Adam D. Barratt wrote: Please go ahead, and remove the moreinfo tag once the package has been accepted. Uploaded. live well, vagrant signature.asc Description: PGP signature
Bug#774535: unblock: ldm-themes/15.01.2
On 2015-01-05, Ivo De Decker wrote: Control: tags -1 -moreinfo On Mon, Jan 05, 2015 at 11:45:29AM -0800, Vagrant Cascadian wrote: Uploaded and in unstable. Thanks! I'm really sorry to take more of your time... I made a slight mistake and uploaded a package with the wrong logo.png file, which leaves an unsightly white pixel above the username box. It is a cosmetic issue, but the only purpose of this package is costmetic. We could suffer a release with the ugly white pixel, but If you'd consider it I'd like to upload ldm-themes 15.01.2 to fix it? Only difference would be an updated logo.png in the lines theme. Please go ahead. Remove the moreinfo tag once the new version is there. Uploaded ldm 15.01.2, please unblock it. Thanks! live well, vagrant signature.asc Description: PGP signature
Bug#774535: Pre-approval request: unblock: ldm-themes/15.01.1
On 2015-01-04, Vagrant Cascadian wrote: On 2015-01-04, Ivo De Decker wrote: On Sat, Jan 03, 2015 at 06:05:54PM -0800, Vagrant Cascadian wrote: I'm seeking release team pre-approval to upload ldm-themes 15.01.1 package. Please go ahead and remove the moreinfo tags from this bug once the upload is in unstable. Uploaded and in unstable. Thanks! I'm really sorry to take more of your time... I made a slight mistake and uploaded a package with the wrong logo.png file, which leaves an unsightly white pixel above the username box. It is a cosmetic issue, but the only purpose of this package is costmetic. We could suffer a release with the ugly white pixel, but If you'd consider it I'd like to upload ldm-themes 15.01.2 to fix it? Only difference would be an updated logo.png in the lines theme. Thanks for your consideration. live well, vagrant signature.asc Description: PGP signature
Bug#774535: Pre-approval request: unblock: ldm-themes/15.01.1
Control: tags -1 -moreinfo On 2015-01-04, Ivo De Decker wrote: On Sat, Jan 03, 2015 at 06:05:54PM -0800, Vagrant Cascadian wrote: I'm seeking release team pre-approval to upload ldm-themes 15.01.1 package. Please go ahead and remove the moreinfo tags from this bug once the upload is in unstable. Uploaded and in unstable. Thanks! live well, vagrant signature.asc Description: PGP signature
Bug#774535: Pre-approval request: unblock: ldm-themes/15.01.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock I'm seeking release team pre-approval to upload ldm-themes 15.01.1 package. It adds the lines theme, which is the default theme in Jessie, and makes it the preferred theme alternative for LDM. The ldm-themes package in Jessie only currently includes the Joy theme. I am prepared to upload ldm 15.01.1, which will include the following changes (version and date adjusted appropriately, of course): diff -Nru ldm-themes-12.07.1/debian/changelog ldm-themes-15.01.1~20150103~1/debian/changelog --- ldm-themes-12.07.1/debian/changelog 2012-07-13 09:36:47.0 -0700 +++ ldm-themes-15.01.1~20150103~1/debian/changelog 2015-01-03 17:29:50.0 -0800 @@ -1,3 +1,29 @@ +ldm-themes (15.01.1~20150103~1) UNRELEASED; urgency=medium + + * Add new lines theme: +- Install logo.png, bg.png and greeter-gtkrc. + + * Generate lines background png in debian/rules: +- Include background artwork from desktop-base sources. +- Add Build-Depends on librsvg2-bin. +- Remove png in clean target. + + * Add lines greeter-gtkrc based on joy with color adjustments. + + * Include a transparent png as a placeholder for the logo required in +ldm themes. + + * Add lines theme to package description. + + * Update alternatives for ldm-theme in postinst and prerm: +- Install lines theme. +- Lower priority on joy theme. +- Remove lines on package removal. + + * Update debian/copyright. + + -- Vagrant Cascadian vagr...@debian.org Sat, 03 Jan 2015 17:29:36 -0800 + ldm-themes (12.07.1) unstable; urgency=low [ Jonathan Carter ] diff -Nru ldm-themes-12.07.1/debian/control ldm-themes-15.01.1~20150103~1/debian/control --- ldm-themes-12.07.1/debian/control 2012-07-10 15:52:13.0 -0700 +++ ldm-themes-15.01.1~20150103~1/debian/control2015-01-02 19:09:52.0 -0800 @@ -3,7 +3,7 @@ Priority: optional Maintainer: LTSP Debian/Ubuntu Maintainers pkg-ltsp-de...@lists.alioth.debian.org Uploaders: Jonathan Carter jonat...@ubuntu.com, Vagrant Cascadian vagr...@debian.org -Build-Depends: debhelper (= 7.0.50~) +Build-Depends: debhelper (= 7.0.50~), librsvg2-bin Standards-Version: 3.9.2 Package: ldm-themes @@ -15,5 +15,6 @@ sessions hosted on remote machines. . This package currently provides the following themes: + - Lines - Joy diff -Nru ldm-themes-12.07.1/debian/copyright ldm-themes-15.01.1~20150103~1/debian/copyright --- ldm-themes-12.07.1/debian/copyright 2012-07-12 19:18:51.0 -0700 +++ ldm-themes-15.01.1~20150103~1/debian/copyright 2015-01-03 16:59:23.0 -0800 @@ -2,6 +2,7 @@ Source: Artwork source images can be found at: http://wiki.debian.org/DebianArt/Themes/Joy + https://anonscm.debian.org/viewvc/debian-desktop/packages/trunk/desktop-base/login/background.svg Files: joy/* Copyright: 2012 Adrien Aubourg adrien.aubo...@gmail.com @@ -13,11 +14,12 @@ On Debian systems, a copy of the GNU General Public License version 2 may be found in the file /usr/share/common-licenses/GPL-2. -Files: joy/greeter-gtkrc +Files: joy/greeter-gtkrc lines/greeter-gtkrc Copyright: Kenneth Wimer kw...@ubuntu.com Conn O'Griofa connogri...@gmail.com Jonathan Carter jonat...@ubuntu.com Dave Camp d...@ximian.com + 2015 Vagrant Cascadian vagr...@debian.org License: GPLv2 This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as @@ -26,9 +28,19 @@ On Debian systems, a copy of the GNU General Public License version 2 may be found in the file /usr/share/common-licenses/GPL-2. +Files: lines/background.svg +Copyright: 2014 Juliette Taka BELIN juliettetaka.be...@gmail.com +License: GPL-2+ + +Files: lines/logo.png +Copyright: 2015 Vagrant Cascadian vagr...@debian.org +License: GPL-2+ + Files: debian/* Copyright: 2011-2012 Jonathan Carter jonat...@ubuntu.com - 2012 Vagrant Cascadian vagr...@debian.org + 2012-2014 Vagrant Cascadian vagr...@debian.org +License: GPL-2+ + License: GPL-2+ This package is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru ldm-themes-12.07.1/debian/install ldm-themes-15.01.1~20150103~1/debian/install --- ldm-themes-12.07.1/debian/install 2012-07-10 15:52:13.0 -0700 +++ ldm-themes-15.01.1~20150103~1/debian/install2015-01-02 19:09:52.0 -0800 @@ -1 +1,4 @@ joy usr/share/ldm/themes +lines/logo.png usr/share/ldm/themes/lines/ +lines/bg.png usr/share/ldm/themes/lines/ +lines/greeter-gtkrc usr/share/ldm/themes/lines/ diff -Nru ldm-themes-12.07.1/debian/postinst ldm-themes-15.01.1~20150103~1/debian/postinst --- ldm-themes-12.07.1/debian/postinst 2012-07-12 08:05:45.0 -0700 +++ ldm-themes-15.01.1~20150103~1/debian/postinst 2015-01-02 19:09:52.0 -0800 @@ -22,7 +22,10 @@ configure) update-alternatives
Bug#771741: unblock: ltsp/5.5.4-2
On 2014-12-01, Adam D. Barratt wrote: Control: tags -1 + d-i On Mon, 2014-12-01 at 16:26 -0800, Vagrant Cascadian wrote: Please unblock package ltsp This fixes two RC bugs, one which can result in the old wheezy kernel being used on after upgrading to jessie, and another which breaks removal of linux-image packages on armhf. It also fixes two important issues, uneccesary configuration of pulseaudio on ltsp chroot creation, and removing .dtb files copied into the tftp dirs but don't have corresponding kernels installed. A documentation issue in debian/copyright removes outdated VCS information (which is present in debian/control). Looks okay to me, but will need a d-i ack as it produces a udeb. Thanks! FWIW, there are no changes compared to the ltsp-client-builder udeb in jessie, and ltsp-client-builder isn't enabled by default in jessie. live well, vagrant signature.asc Description: PGP signature
Bug#771741: unblock: ltsp/5.5.4-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ltsp This fixes two RC bugs, one which can result in the old wheezy kernel being used on after upgrading to jessie, and another which breaks removal of linux-image packages on armhf. It also fixes two important issues, uneccesary configuration of pulseaudio on ltsp chroot creation, and removing .dtb files copied into the tftp dirs but don't have corresponding kernels installed. A documentation issue in debian/copyright removes outdated VCS information (which is present in debian/control). All of the patches are taken from upstream, for what it's worth. Thanks for considering! diff -Nru ltsp-5.5.4/debian/changelog ltsp-5.5.4/debian/changelog --- ltsp-5.5.4/debian/changelog 2014-10-21 23:33:38.0 -0700 +++ ltsp-5.5.4/debian/changelog 2014-12-01 15:22:13.0 -0800 @@ -1,3 +1,21 @@ +ltsp (5.5.4-2) unstable; urgency=medium + + * ltsp-update-kernels/update-kernels: Fix kernel version sorting that +results in clients booting obsolete kernels (Closes: #771470). + + * update-kernels: Suppress mkimage output, as it prevents linux-image +packages from being removed successfully (Closes: #771728). + + * ltsp-build-client: Remove plugin that needlessly modifies pulseaudio +configuration files. + + * ltsp-update-kernels: Remove dtb files when corresponding kernel +version is no longer present. + + * debian/copyright: Remove outdated VCS information. + + -- Vagrant Cascadian vagr...@debian.org Mon, 01 Dec 2014 15:22:01 -0800 + ltsp (5.5.4-1) unstable; urgency=medium * New upstream version: diff -Nru ltsp-5.5.4/debian/copyright ltsp-5.5.4/debian/copyright --- ltsp-5.5.4/debian/copyright 2014-08-02 15:43:04.0 -0700 +++ ltsp-5.5.4/debian/copyright 2014-10-24 10:15:51.0 -0700 @@ -6,11 +6,7 @@ The upstream source tree can be found on launchpad: - bzr get http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk - -The debian dir for ltsp packages in Debian is maintained in bzr: - - bzr get http://bzr.debian.org/bzr/pkg-ltsp/ltsp-debian-packaging + bzr branch http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk The original LTSP sources can be downloaded from: http://ltsp.org diff -Nru ltsp-5.5.4/debian/patches/series ltsp-5.5.4/debian/patches/series --- ltsp-5.5.4/debian/patches/series2014-10-15 15:44:17.0 -0700 +++ ltsp-5.5.4/debian/patches/series2014-12-01 15:16:53.0 -0800 @@ -2,3 +2,9 @@ getltscfg-makefile-flags jetpipe-from-ltsp-client-core-init-script manpages-use-debian-version +upstream/0004-Debian-Remove-ltsp-build-client-plugin-pulseaudio-tw.patch +upstream/0013-ltsp-update-kernels-Remove-.dtb-files-when-kernel-ve.patch +upstream/0015-Correctly-sort-kernel-FLAVOR-in-increasing-order-and.patch +upstream/0016-update-kernels-Fix-issues-with-kernel-version-varian.patch +upstream/0017-Debian-update-kernels.conf-Prefer-586-over-486-in-fo.patch +upstream/0018-update-kernels-Quiet-down-mkimage-output-when-genera.patch diff -Nru ltsp-5.5.4/debian/patches/upstream/0004-Debian-Remove-ltsp-build-client-plugin-pulseaudio-tw.patch ltsp-5.5.4/debian/patches/upstream/0004-Debian-Remove-ltsp-build-client-plugin-pulseaudio-tw.patch --- ltsp-5.5.4/debian/patches/upstream/0004-Debian-Remove-ltsp-build-client-plugin-pulseaudio-tw.patch 1969-12-31 16:00:00.0 -0800 +++ ltsp-5.5.4/debian/patches/upstream/0004-Debian-Remove-ltsp-build-client-plugin-pulseaudio-tw.patch 2014-11-29 13:26:14.0 -0800 @@ -0,0 +1,40 @@ +From 9fc1793d4fb7b40c043cbb0639ec2bc6c9de10a3 Mon Sep 17 00:00:00 2001 +From: Vagrant Cascadian vagr...@debian.org +Date: Thu, 23 Oct 2014 15:36:50 -0700 +Subject: [PATCH 04/17] Debian: Remove ltsp-build-client plugin + pulseaudio-tweaks, as the customizations are no longer needed. + +--- + .../ltsp-build-client/Debian/010-pulseaudio-tweaks | 20 + 1 file changed, 20 deletions(-) + delete mode 100644 server/share/ltsp/plugins/ltsp-build-client/Debian/010-pulseaudio-tweaks + +diff --git a/server/share/ltsp/plugins/ltsp-build-client/Debian/010-pulseaudio-tweaks b/server/share/ltsp/plugins/ltsp-build-client/Debian/010-pulseaudio-tweaks +deleted file mode 100644 +index 65e7dca..000 +--- a/server/share/ltsp/plugins/ltsp-build-client/Debian/010-pulseaudio-tweaks /dev/null +@@ -1,20 +0,0 @@ +-# a number of hacks needed to resolve: http://bugs.debian.org/537526 +-case $MODE in +-finalization) +-# some versions of pulseaudio need /var/lib/pulse to be present, but +-# create it dynamically. create the directory so we can bind-mount it. +-mkdir $ROOT/var/lib/pulse +- +-# workaround to get pulseaudio to start on thin-clients with only 64MB +-# of ram. +-if [ -f $ROOT/etc/pulse/daemon.conf ] [ $DIST != lenny ]; then +-echo 'shm-size-bytes = 65535' $ROOT/etc/pulse/daemon.conf
Bug#770216: unblock: u-boot/2014.10+dfsg1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package u-boot Version 2014.10+dfsg1-2 of u-boot fixes support for some boards(Cubox i2/Hummingboard i2), improves compatibility with debian-installer boot scripts (Cubox-i/Wandboard), and updates documentation for using u-boot on several armhf platforms. Specifically, CuBox i2 and Hummingboard i2eX (which uses the mx6_cubox-i target as well) are fixed, which resulted in at least one patch being merged into cubox-i-support.diff. It also improves compatibility with debian-installer hd-media target on the wandboard and cubox-i platforms by setting several variables used in the boot script. On cubox-i, the detecting which device tree (dtb) to load was set to run before the boot script, and importing the boot environment before loading the boot script to work around issues with hd-media's boot script handling for console support. README.Debian was updated with information about new platforms and split into the corresponding packages (u-boot, u-boot-imx, u-boot-omap, u-boot-sunxi), which was previously only shipped in u-boot (which on armhf is effectively a metapackage pulling in all the armhf platforms). I did relocate one patch related to the wandboard (wandboard-uEnv.txt-bootz-n-fixes.patch) grouping it together with other wandboard related patches in debian/patches, which arguably wasn't strictly necessary. Apologies for the extra noise that resulted from that. README.Debian| 29 changelog| 18 patches/0001-wandboard-uEnv.txt-bootz-n-fixes.patch | 103 -- patches/cubox-i/Switch-mx6_cubox-i-to-Kconfig.patch | 92 -- patches/cubox-i/cubox-i-standardize-variables.diff | 26 patches/cubox-i/cubox-i-support.diff | 435 +++--- patches/cubox-i/emulate-config_distro_bootcmd-standardization.diff | 19 patches/cubox-i/imx6-spl-support.diff| 61 - patches/cubox-i/spl-sata-support.diff|4 patches/cubox-i/steal-board-eth-init-from-hummingboard.diff |4 patches/series | 11 patches/wandboard/emulate-config_distro_bootcmd-standardization.diff | 19 patches/wandboard/wandboard-standardized-variables | 20 patches/wandboard/wandboard-uEnv.txt-bootz-n-fixes.patch | 103 ++ u-boot-imx.README.Debian | 20 u-boot-omap.README.Debian| 13 u-boot-sunxi.README.Debian | 11 u-boot.README.Debian | 25 18 files changed, 659 insertions(+), 354 deletions(-) diff -Nru u-boot-2014.10+dfsg1/debian/changelog u-boot-2014.10+dfsg1/debian/changelog --- u-boot-2014.10+dfsg1/debian/changelog 2014-10-19 11:34:54.0 -0700 +++ u-boot-2014.10+dfsg1/debian/changelog 2014-11-01 16:38:54.0 -0700 @@ -1,3 +1,21 @@ +u-boot (2014.10+dfsg1-2) unstable; urgency=medium + + [ Steve Langasek ] + * Resync cubox-i patches with github. +- fixes support for booting on the cubox-i2ultra/i2ex. + (Closes: #766266) + + [ Vagrant Cascadian ] + * wandboard, cubox-i: Add patches to use variables expected by +debian-installer bootscript. + * cubox-i: Move importing bootenv before loading the boot script, to +allow environment variables useful to the boot script to be set. + * cubox-i: Run autodetectfdt before attempting to load the boot script. + * Split README.Debian by subarchitecture, and document installing u-boot +on several additional boards. + + -- Vagrant Cascadian vagr...@debian.org Sat, 01 Nov 2014 16:33:33 -0700 + u-boot (2014.10+dfsg1-1) unstable; urgency=medium [ Vagrant Cascadian ] diff -Nru u-boot-2014.10+dfsg1/debian/patches/0001-wandboard-uEnv.txt-bootz-n-fixes.patch u-boot-2014.10+dfsg1/debian/patches/0001-wandboard-uEnv.txt-bootz-n-fixes.patch --- u-boot-2014.10+dfsg1/debian/patches/0001-wandboard-uEnv.txt-bootz-n-fixes.patch 2014-10-15 10:41:53.0 -0700 +++ u-boot-2014.10+dfsg1/debian/patches/0001-wandboard-uEnv.txt-bootz-n-fixes.patch 1969-12-31 16:00:00.0 -0800 @@ -1,103 +0,0 @@ -Downloaded from: - - https://raw.github.com/eewiki/u-boot-patches/master/v2014.01/0001-wandboard-uEnv.txt-bootz-n-fixes.patch - -Modified to reduce diff with upstream: -- keep the default bootdelay. -- keep support for bootscripts. -- consistantly use load vs. fatload. - -From d0bf1e44422e4102859d9420a8abf42c3600f500 Mon Sep 17 00:00:00 2001 -From: Robert Nelson robertcnel...@gmail.com -Date: Thu, 23 Jan 2014 16:24:13 -0600 -Subject: [PATCH] wandboard: uEnv.txt, bootz
Re: RM: u-boot [powerpc] -- ANAIS; u-boot binary package no longer built
On 2014-07-29, Vagrant Cascadian wrote: As of u-boot 2014.04+dfsg1-3, the u-boot binary package is no longer built on powerpc. It still produces the u-boot-tools binary package on powerpc, so that should not be removed. This is blocking migration to testing, due to https://bugs.debian.org/754610. Admittedly, the fix was to remove the powerpc target that caused the FTBFS, but the ZUMA target has been orphaned upstream, and I've received no confirmation from the powerpc porters about which hardware it actually supported, or how it might be useful. Thanks for looking into it! live well, vagrant pgpvLmPFgMiIT.pgp Description: PGP signature
Bug#743564: wheezy-pu: package ltsp/5.4.2-6
On Thu, Apr 03, 2014 at 09:25:30PM +0100, Adam D. Barratt wrote: On Thu, 2014-04-03 at 12:23 -0700, Vagrant Cascadian wrote: ltsp-server-standalone: no sound with pulseaudio https://bugs.debian.org/738553 It breaks sounds support on most LTSP thin clients, in my experience. The update is a trivial one-line patch, and I've tested it for many months in at least one LTSP deployment with a variety of hardware. The patch was merged in upstream LTSP some time ago, and is present in jessie. Please go ahead; thanks. It's been uploaded as ltsp 5.4.2-6+deb7u1, although I failed to add this bug number in the changelog. Please let me know if there's anything more I need to do. live well, vagrant signature.asc Description: Digital signature
Bug#743564: wheezy-pu: package ltsp/5.4.2-6
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu I would like to fix: ltsp-server-standalone: no sound with pulseaudio https://bugs.debian.org/738553 It breaks sounds support on most LTSP thin clients, in my experience. The update is a trivial one-line patch, and I've tested it for many months in at least one LTSP deployment with a variety of hardware. The patch was merged in upstream LTSP some time ago, and is present in jessie. diff -Nru ltsp-5.4.2/debian/changelog ltsp-5.4.2/debian/changelog --- ltsp-5.4.2/debian/changelog 2013-03-25 09:58:38.0 -0700 +++ ltsp-5.4.2/debian/changelog 2014-04-03 12:15:52.0 -0700 @@ -1,3 +1,9 @@ +ltsp (5.4.2-6+deb7u1) wheezy; urgency=medium + + * Apply patch to fix remote audio on thinclients (Closes: #738553). + + -- Vagrant Cascadian vagr...@debian.org Thu, 03 Apr 2014 12:14:39 -0700 + ltsp (5.4.2-6) unstable; urgency=low * Add patch to run jetpipe from ltsp-client-core init script rather than diff -Nru ltsp-5.4.2/debian/patches/fix-pulseaudio-module-suspend-on-idle-738553 ltsp-5.4.2/debian/patches/fix-pulseaudio-module-suspend-on-idle-738553 --- ltsp-5.4.2/debian/patches/fix-pulseaudio-module-suspend-on-idle-738553 1969-12-31 16:00:00.0 -0800 +++ ltsp-5.4.2/debian/patches/fix-pulseaudio-module-suspend-on-idle-738553 2014-04-03 12:12:28.0 -0700 @@ -0,0 +1,23 @@ +revno: 2483 +revision-id: vagr...@debian.org-20130731003242-cu09asl3ttad0mdi +parent: launchpad_translations_on_behalf_of_ltsp-upstream-20130717043036-wxak5sqbfnj6wlta +committer: Vagrant Cascadian vagr...@debian.org +branch nick: ltsp-trunk +timestamp: Tue 2013-07-30 17:32:42 -0700 +message: + ltsp-init-common: pulseaudio: add module-suspend-on-idle to improve stability. + Thanks to Tom Wallis for reporting the issue and fix. +Debian-Bug: http://bugs.debian.org/738553 + +Index: ltsp-5.4.2/client/initscripts/ltsp-init-common +=== +--- ltsp-5.4.2.orig/client/initscripts/ltsp-init-common2012-06-27 14:26:21.0 -0700 ltsp-5.4.2/client/initscripts/ltsp-init-common 2014-04-03 12:10:39.522495078 -0700 +@@ -34,6 +34,7 @@ + -L $PULSE_VOLUME_RESTORE \ + -L module-rescue-streams \ + -L module-native-protocol-unix auth-anonymous=1 \ ++-L module-suspend-on-idle \ + -n + ;; + [Ff][Aa][Ll][Ss][Ee]|[Nn]|[Nn][Oo]) diff -Nru ltsp-5.4.2/debian/patches/series ltsp-5.4.2/debian/patches/series --- ltsp-5.4.2/debian/patches/series2013-03-25 09:53:38.0 -0700 +++ ltsp-5.4.2/debian/patches/series2014-04-03 12:09:28.0 -0700 @@ -11,3 +11,4 @@ fatclients-return-0 cryptsetup-swap-with-nbd jetpipe-from-ltsp-client-core-init-script +fix-pulseaudio-module-suspend-on-idle-738553 live well, vagrant signature.asc Description: Digital signature
Re: Bug#730833: u-boot: FTBFS on kfreebsd
Control: severity 730833 important On Tue, Feb 18, 2014 at 11:19:29PM +, Robert Millan wrote: On 18/02/2014 21:54, Vagrant Cascadian wrote: On Tue, Feb 18, 2014 at 09:35:09PM +, Robert Millan wrote: On 18/02/2014 19:11, Vagrant Cascadian wrote: If the best thing is to drop non-linux architectures, I'd be fine with that. I don't want to drop architectures from the packaging without asking porters first. I think if upstream doesn't consider it a bug to copy non-portable declarations from Linux headers, it's probably reasonable to consider u-boot as Linux-specific software. Attempting to fight this kind of trend is tends to be very costly, but ultimately it's your call as maintainer to decide whether it's worth it. Thanks for the comments. I'm thinking it's not worth the effort, and plan to mark it as linux only in the next upload, and lowering the severity on the bug now. live well, vagrant signature.asc Description: Digital signature
Bug#729685: RM: u-boot/2012.04.01-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove all binary packages built from u-boot sources from jessie/testing, to allow newer versions to migrate. Two transitional packages, uboot-envtools and uboot-mkimage have been dropped from u-boot in unstable (replaced by functionality in u-boot-tools), which is preventing migration to testing. The u-boot binary package is no longer built on architectures that produce no useful targets (i386, amd64, ia64, kfreebsd-*, mipsel, s390x, sparc), which is also preventing migration to testing. For more info, see: #635050 [u-boot] binary u-boot package is virtually empty on amd64. Thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131115195121.gi8...@cascadia.debian.net
Bug#693924: unblock: ltsp/5.4.2-4
On Sun, Jan 06, 2013 at 11:40:29PM +0100, Julien Cristau wrote: On Wed, Nov 21, 2012 at 12:02:39 -0800, Vagrant Cascadian wrote: +- Fix initramfs udhcp hook to use /run instead of /tmp, which allows the + booting from a network using PXE ProxyDHCP (Closes: #693746). This requires initramfs-tools 0.99 AFAICT, there's no /run before that. Thanks for the review. The patch makes an attempt at implementing backwards compatibility, but looking into it, it may fail if /run is not present. Bumping the versioned dependency on initramfs-tools would be simple enough, if that was needed, alternately it wouldn't be hard to update the patch to ensure /run is present (a simple mkdir -p /run should do it). Any preference on that? live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130108222852.GA6011@talon.fglan
Bug#693924: unblock: ltsp/5.4.2-5
Control: retitle -1 unblock: ltsp/5.4.2-5 On Tue, Jan 08, 2013 at 11:35:45PM +0100, Julien Cristau wrote: On Tue, Jan 8, 2013 at 14:28:52 -0800, Vagrant Cascadian wrote: On Sun, Jan 06, 2013 at 11:40:29PM +0100, Julien Cristau wrote: On Wed, Nov 21, 2012 at 12:02:39 -0800, Vagrant Cascadian wrote: +- Fix initramfs udhcp hook to use /run instead of /tmp, which allows the + booting from a network using PXE ProxyDHCP (Closes: #693746). This requires initramfs-tools 0.99 AFAICT, there's no /run before that. Thanks for the review. The patch makes an attempt at implementing backwards compatibility, but looking into it, it may fail if /run is not present. Bumping the versioned dependency on initramfs-tools would be simple enough, if that was needed, alternately it wouldn't be hard to update the patch to ensure /run is present (a simple mkdir -p /run should do it). Any preference on that? I'd prefer the versioned dep, if you don't mind. Uploaded: ltsp (5.4.2-5) unstable; urgency=low * ltsp-client-core: Depend on initramfs-tools 0.99, to ensure /run is available in the initramfs. -- Vagrant Cascadian vagr...@debian.org Tue, 08 Jan 2013 22:00:39 -0800 Please unblock it. Thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130109070830.GC6011@talon.fglan
Bug#693924: unblock: ltsp/5.4.2-4
On Thu, Dec 20, 2012 at 05:10:22AM +0100, Cyril Brulebois wrote: Vagrant Cascadian vagr...@debian.org (21/11/2012): LTSP does contain the ltsp-client builder .udeb, though no code in the .udeb itself was changed, and the ltsp-client-builder is not used in the default installer. I've now tested that the ltsp-client-builder udeb also works as expected. basically, I know next to nothing on the ltsp topic, and it looks like a very specialized use case anyway; therefore I don't think I'm going to have/find any time to investigate this, and I'm going blindly trust you as upstream and the release team to make the right call. I'm guessing the release team simply hasn't had time either... While LTSP isn't useless in wheezy without the patches, they're all important fixes. Some features break depending on what shell is used, and some of the bugs result in a failure to boot LTSP in some network and server partitioning configurations... I hesitate to raise the severity on those only because it doesn't break all configurations, or the default configuration; perhaps I am too timid with the severity? I'm hoping the release team will still consider this unblock request? live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130101181027.GG4058@talon.fglan
Bug#693924: unblock: ltsp/5.4.2-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package ltsp
It includes several bashism and dashism fixes that interfered with operation of
several key scripts in LTSP, sometimes silently and thus hard to troubleshoot.
Several of the other bugs resulted in a non-booting LTSP environment in some
configurations.
All of the included patches are committed upstream.
LTSP does contain the ltsp-client builder .udeb, though no code in the .udeb
itself was changed, and the ltsp-client-builder is not used in the default
installer.
The debdiff contains some date changes in debian/po/*, which should probably be
fixed in the packaging someday as it is basically needless noise. Apologies for
that.
Thanks for your consideration!
live well,
vagrant
diff -Nru ltsp-5.4.2/debian/changelog ltsp-5.4.2/debian/changelog
--- ltsp-5.4.2/debian/changelog 2012-06-27 16:14:12.0 -0700
+++ ltsp-5.4.2/debian/changelog 2012-11-20 21:27:32.0 -0800
@@ -1,3 +1,35 @@
+ltsp (5.4.2-4) unstable; urgency=low
+
+ * ltsp-client-core: Add patch to nbd-disconnect to handle cryptsetup swap
+devices (Closes: #690267).
+
+ -- Vagrant Cascadian vagr...@debian.org Tue, 20 Nov 2012 21:26:04 -0800
+
+ltsp (5.4.2-3) unstable; urgency=low
+
+ * ltsp-client-core patches from upstream:
+- Fix use of 'echo -e' by switching to printf in screen-x-common
+ (Closes: #692920).
+- Fix use of a read -p bashism in ltsp-cleanup (Closes: #690638).
+- Fix dashisms in update-kernels using local - by saving flags and
+ restoring them later (Closes: #693499).
+- Prevent setting of LTSP_FATCLIENT variable from causing ltsp-client-core
+ initscript to die (Closes: #693745).
+- Move ltspconfig cache processing earlier, so that variables defined in
+ lts.conf can override autodetected variables (Closes: #689668).
+- Fix initramfs udhcp hook to use /run instead of /tmp, which allows the
+ booting from a network using PXE ProxyDHCP (Closes: #693746).
+
+ * ltsp-server patches from upstream:
+- Fix bashism in ltsp-config by using printf instead of 'echo -e' and echo
+ with \n interpreting (Closes: #690618).
+- Fix ltsp-update-image to support servers with separate /boot partition.
+ (Closes: #693636).
+- Fix dashisms in ltsp-update-image using local - by saving flags and
+ restoring them later (Closes: #693496).
+
+ -- Vagrant Cascadian vagr...@debian.org Mon, 19 Nov 2012 14:17:21 -0800
+
ltsp (5.4.2-2) unstable; urgency=low
* ltsp-server: Move lts.conf from doc to doc/examples.
diff -Nru ltsp-5.4.2/debian/patches/cryptsetup-swap-with-nbd
ltsp-5.4.2/debian/patches/cryptsetup-swap-with-nbd
--- ltsp-5.4.2/debian/patches/cryptsetup-swap-with-nbd 1969-12-31
16:00:00.0 -0800
+++ ltsp-5.4.2/debian/patches/cryptsetup-swap-with-nbd 2012-11-20
21:27:32.0 -0800
@@ -0,0 +1,25 @@
+ 2409 Vagrant Cascadian2012-11-19
+ Also support cryptsetup swap devices backed by NBD.
+ http://bugs.debian.org/690267
+
+=== modified file 'client/share/ltsp/nbd-disconnect'
+--- old/client/share/ltsp/nbd-disconnect 2012-05-14 19:23:51 +
new/client/share/ltsp/nbd-disconnect 2012-11-20 00:40:53 +
+@@ -32,6 +32,16 @@
+ swapoff $device
+ nbd-client -d $device
+ ;;
++/dev/mapper/swap[0-9])
++nbd_device=$(cryptsetup status $device | awk '/device:/{print
$2}')
++swapoff $device
++cryptsetup remove $device
++case $nbd_device in
++/dev/nbd[1-9])
++nbd-client -d $nbd_device
++;;
++esac
++;;
+ esac
+ done /proc/swaps
+
+
diff -Nru ltsp-5.4.2/debian/patches/fatclients-return-0
ltsp-5.4.2/debian/patches/fatclients-return-0
--- ltsp-5.4.2/debian/patches/fatclients-return-0 1969-12-31
16:00:00.0 -0800
+++ ltsp-5.4.2/debian/patches/fatclients-return-0 2012-11-19
14:33:11.0 -0800
@@ -0,0 +1,18 @@
+ 2407 Vagrant Cascadian2012-11-19
+ ltsp_config.d/20fatclients: Explicitly return 0 if LTSP_FATCLIENT is
set,
+ otherwise it returns a value which can cause errors if sourced from a
script
+ that exits on errors (i.e. with set -e flags set).
+
+=== modified file 'client/share/ltsp/ltsp_config.d/20fatclients'
+--- old/client/share/ltsp/ltsp_config.d/20fatclients 2012-04-25 16:54:14
+
new/client/share/ltsp/ltsp_config.d/20fatclients 2012-11-19 18:59:13
+
+@@ -1,6 +1,6 @@
+ # Automatically set LTSP_FATCLIENT=True if the image supports local logins
+-test -z $LTSP_FATCLIENT || return
+-test -f /proc/meminfo || return
++test -z $LTSP_FATCLIENT || return 0
++test -f /proc/meminfo || return 0
+
+ # process_lts_conf() unsets glob expansion (set -f), so we need to use `find`
+ # blacklist Xsession.desktop (installed by xinit
Bug#685882: unblock: zoneminder/1.25.0-3
retitle 685882 unblock: zoneminder/1.25.0-3
thanks
On Mon, Aug 27, 2012 at 07:10:23PM +0200, Julien Cristau wrote:
On Sat, Aug 25, 2012 at 14:37:34 -0700, Vagrant Cascadian wrote:
diff -Nru zoneminder-1.25.0/debian/rules zoneminder-1.25.0/debian/rules
--- zoneminder-1.25.0/debian/rules 2011-12-12 14:48:18.0 -0800
+++ zoneminder-1.25.0/debian/rules 2012-08-23 13:27:54.0 -0700
@@ -17,21 +17,18 @@
DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
-CFLAGS = -Wall -g
-CPPFLAGS = -D__STDC_CONSTANT_MACROS
-CXXFLAGS = -DZM_FFMPEG_CVS -DHAVE_LIBCRYPTO
-
-ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
- CFLAGS += -O0
-else
- CFLAGS += -O2
-endif
+CFLAGS = $(shell dpkg-buildflags --get CFLAGS)
+CPPFLAGS = $(shell dpkg-buildflags --get CPPFLAGS)
+CXXFLAGS = $(shell dpkg-buildflags --get CXXFLAGS)
+CFLAGS += -Wall -g
+CPPFLAGS += -D__STDC_CONSTANT_MACROS
+CXXFLAGS += -DZM_FFMPEG_CVS -DHAVE_LIBCRYPTO
%:
dh $@ --with autoreconf
override_dh_auto_configure:
- CFLAGS=$(CFLAGS) CXXFLAGS=$(CXXFLAGS) ./configure
--host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE)
--sysconfdir=/etc/zm --prefix=/usr --mandir=\$${prefix}/share/man
--infodir=\$${prefix}/share/info --with-mysql=/usr
--with-webdir=/usr/share/zoneminder --with-ffmpeg=/usr
--with-cgidir=/usr/lib/cgi-bin --with-webuser=www-data
--with-webgroup=www-data --enable-crashtrace=no --enable-mmap=yes
+ ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE)
--sysconfdir=/etc/zm --prefix=/usr --mandir=\$${prefix}/share/man
--infodir=\$${prefix}/share/info --with-mysql=/usr
--with-webdir=/usr/share/zoneminder --with-ffmpeg=/usr
--with-cgidir=/usr/lib/cgi-bin --with-webuser=www-data
--with-webgroup=www-data --enable-crashtrace=no --enable-mmap=yes
How are the build flags passed to configure? They don't seem to be
explicitly exported, and you removed them from the configure cmdline.
Apologies, they're not recognized at all...
Updated debian/rules to export the various *FLAGS variables, and added LDFLAGS,
to catch all the cases lintian complains about regarding hardening build flags.
Uploaded zoneminder 1.25.0-3, new debdiff (against 1.25.0-1.1) attached...
Thanks for your viligant review!
live well,
vagrant
diff -Nru zoneminder-1.25.0/debian/changelog zoneminder-1.25.0/debian/changelog
--- zoneminder-1.25.0/debian/changelog 2012-05-13 08:03:32.0 -0700
+++ zoneminder-1.25.0/debian/changelog 2012-08-28 12:10:05.0 -0700
@@ -1,3 +1,24 @@
+zoneminder (1.25.0-3) unstable; urgency=low
+
+ * debian/rules: Export CFLAGS, CPPFLAGS, CXXFLAGS and LDFLAGS, to ensure
+hardening build flags are enabled.
+
+ -- Vagrant Cascadian vagr...@debian.org Tue, 28 Aug 2012 12:10:03 -0700
+
+zoneminder (1.25.0-2) unstable; urgency=low
+
+ [ Vagrant Cascadian ]
+ * Add a patch to disable checking for updated versions by default, as
+upgrades should happen through package management.
+ * Use dpkg-buildflags in debian/rules to set default compiler flags.
+ * Ensure zoneminder is stopped before starting (Closes: #657407).
+
+ [ Peter Howard ]
+ * Fix postinst to add permission for table creation during upgrade
+(Closes: #657407).
+
+ -- Vagrant Cascadian vagr...@debian.org Thu, 23 Aug 2012 12:40:34 -0700
+
zoneminder (1.25.0-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru zoneminder-1.25.0/debian/patches/do_not_check_for_updates_by_default zoneminder-1.25.0/debian/patches/do_not_check_for_updates_by_default
--- zoneminder-1.25.0/debian/patches/do_not_check_for_updates_by_default 1969-12-31 16:00:00.0 -0800
+++ zoneminder-1.25.0/debian/patches/do_not_check_for_updates_by_default 2012-08-23 12:36:21.0 -0700
@@ -0,0 +1,17 @@
+Default to not checking for updated versions of ZoneMinder, as users should
+get updates through the package. Also prevents phoning home to
+zoneminder.com.
+
+Index: zoneminder/scripts/ZoneMinder/lib/ZoneMinder/ConfigData.pm.in
+===
+--- zoneminder.orig/scripts/ZoneMinder/lib/ZoneMinder/ConfigData.pm.in 2011-12-12 14:48:18.183612192 -0800
zoneminder/scripts/ZoneMinder/lib/ZoneMinder/ConfigData.pm.in 2012-05-13 15:10:34.057470903 -0700
+@@ -1290,7 +1290,7 @@
+ },
+ {
+ name = ZM_CHECK_FOR_UPDATES,
+- default = yes,
++ default = no,
+ description = Check with zoneminder.com for updated versions,
+ help = From ZoneMinder version 1.17.0 onwards new versions are expected to be more frequent. To save checking manually for each new version ZoneMinder can check with the zoneminder.com website to determine the most recent release. These checks are infrequent, about once per week, and no personal or system information is transmitted other than your current version number. If you do
Bug#685882: unblock: zoneminder/1.25.0-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package zoneminder
Zoneminder was removed from testing due to mootools briefly being removed from
testing (Bug #682265).
Zoneminder 1.25.0-1.1 was unblocked, but didn't enter wheezy due to a release
critical bug that prevented upgrades from squeeze due to changes to the
database layout (Bug #657407), which has been fixed in zoneminder 1.25.0-2.
Zoneminder 1.25.0-2 also makes progress towards a release goal of enabling
hardening build flags, and defaults to disabling zoneminder's self-updating
features, as it will only break a packaged zoneminder install.
The debdiff for zoneminder 1.25.0-1.1 to 1.25.0-2 is attached (since that's the
version that *was* in testing).
zoneminder (1.25.0-2) unstable; urgency=low
[ Vagrant Cascadian ]
* Add a patch to disable checking for updated versions by default, as
upgrades should happen through package management.
* Use dpkg-buildflags in debian/rules to set default compiler flags.
* Ensure zoneminder is stopped before starting (Closes: #657407).
[ Peter Howard ]
* Fix postinst to add permission for table creation during upgrade
(Closes: #657407).
-- Vagrant Cascadian vagr...@debian.org Thu, 23 Aug 2012 12:40:34 -0700
Thanks for considering this request!
unblock zoneminder/1.25.0-2
live well,
vagrant
diff -Nru zoneminder-1.25.0/debian/changelog zoneminder-1.25.0/debian/changelog
--- zoneminder-1.25.0/debian/changelog 2012-05-13 08:03:32.0 -0700
+++ zoneminder-1.25.0/debian/changelog 2012-08-23 13:28:46.0 -0700
@@ -1,3 +1,17 @@
+zoneminder (1.25.0-2) unstable; urgency=low
+
+ [ Vagrant Cascadian ]
+ * Add a patch to disable checking for updated versions by default, as
+upgrades should happen through package management.
+ * Use dpkg-buildflags in debian/rules to set default compiler flags.
+ * Ensure zoneminder is stopped before starting (Closes: #657407).
+
+ [ Peter Howard ]
+ * Fix postinst to add permission for table creation during upgrade
+(Closes: #657407).
+
+ -- Vagrant Cascadian vagr...@debian.org Thu, 23 Aug 2012 12:40:34 -0700
+
zoneminder (1.25.0-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru zoneminder-1.25.0/debian/patches/do_not_check_for_updates_by_default zoneminder-1.25.0/debian/patches/do_not_check_for_updates_by_default
--- zoneminder-1.25.0/debian/patches/do_not_check_for_updates_by_default 1969-12-31 16:00:00.0 -0800
+++ zoneminder-1.25.0/debian/patches/do_not_check_for_updates_by_default 2012-08-23 12:36:21.0 -0700
@@ -0,0 +1,17 @@
+Default to not checking for updated versions of ZoneMinder, as users should
+get updates through the package. Also prevents phoning home to
+zoneminder.com.
+
+Index: zoneminder/scripts/ZoneMinder/lib/ZoneMinder/ConfigData.pm.in
+===
+--- zoneminder.orig/scripts/ZoneMinder/lib/ZoneMinder/ConfigData.pm.in 2011-12-12 14:48:18.183612192 -0800
zoneminder/scripts/ZoneMinder/lib/ZoneMinder/ConfigData.pm.in 2012-05-13 15:10:34.057470903 -0700
+@@ -1290,7 +1290,7 @@
+ },
+ {
+ name = ZM_CHECK_FOR_UPDATES,
+- default = yes,
++ default = no,
+ description = Check with zoneminder.com for updated versions,
+ help = From ZoneMinder version 1.17.0 onwards new versions are expected to be more frequent. To save checking manually for each new version ZoneMinder can check with the zoneminder.com website to determine the most recent release. These checks are infrequent, about once per week, and no personal or system information is transmitted other than your current version number. If you do not wish these checks to take place or your ZoneMinder system has no internet access you can switch these check off with this configuration variable,
+ type = $types{boolean},
diff -Nru zoneminder-1.25.0/debian/patches/series zoneminder-1.25.0/debian/patches/series
--- zoneminder-1.25.0/debian/patches/series 2012-05-13 07:59:11.0 -0700
+++ zoneminder-1.25.0/debian/patches/series 2012-08-23 12:36:42.0 -0700
@@ -10,3 +10,4 @@
zm-ffmpeg-as-c-library
include-avutil-mathematics-header
Fix-FTBFS-with-gcc-4.7
+do_not_check_for_updates_by_default
diff -Nru zoneminder-1.25.0/debian/postinst zoneminder-1.25.0/debian/postinst
--- zoneminder-1.25.0/debian/postinst 2011-12-12 14:48:18.0 -0800
+++ zoneminder-1.25.0/debian/postinst 2012-08-23 12:35:44.0 -0700
@@ -26,7 +26,7 @@
OLD_ZM_VERSION=$(echo 'select Value from Config where Name = ZM_DYN_CURR_VERSION;' | mysql --defaults-file=/etc/mysql/debian.cnf --skip-column-names zm )
fi
if [ -n $OLD_ZM_VERSION ] [ $OLD_ZM_VERSION != $VERSION ] ; then
-echo 'grant lock tables, alter on zm.* to 'zmuser'@localhost identified by zmpass;' | mysql --defaults-file=/etc/mysql/debian.cnf mysql
+echo 'grant lock tables, create, alter on zm.* to 'zmuser'@localhost
Bug#681644: unblock: ldm-themes/12.07.1
On Sun, Jul 15, 2012 at 02:25:34PM +0100, Adam D. Barratt wrote: On Sat, 2012-07-14 at 17:27 -0700, Vagrant Cascadian wrote: ldm-themes (12.07.1) unstable; urgency=low [ Jonathan Carter ] * Remove all alternatives (Closes: #679208). The only alternatives-related change I can see in the diff is this in the prerm: remove|deconfigure|failed-upgrade) update-alternatives --remove ldm-theme \ -/usr/share/ldm/themes/spacefun +/usr/share/ldm/themes/joy which looks like part of the general theme switch changes. Is that correct? Ah, that part of the changelog was written while we still were trying to ship both spacefun and joy, but it turned out to be an even uglier diff and seemed better to just remove spacefun. Was the addition of a --remove call in postrm (as suggested in #679208) considered? I think what really triggered that bug was the 12.06.1 version shipped both spacefun and joy, but only removed spacefun. I did consider the additional postrm call suggested, but it generated lintian warnings; it seems like there is not real consensus on how to handle update-alternatives --remove so I followed the path that seemed to actually fix the bug that didn't produce lintian warnings and complies with policy as it currently stands. Thanks for the ever-villigent review! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120715155032.GN21245@talon.fglan
Bug#681642: unblock: ldm/2:2.2.11-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ldm In order to have the Joy theme by default with ldm, it required some changes to ldm-themes that were only recently added. The latest ldm adds a versioned recommends on ldm-themes that has an appropriately packaged Joy theme. ldm (2:2.2.11-2) unstable; urgency=low * Recommend a version of ldm-themes that uses the Joy theme by default. -- Vagrant Cascadian vagr...@debian.org Fri, 13 Jul 2012 11:31:49 -0600 unblock ldm/2:2.2.11-2 live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120715003257.GM21245@talon.fglan
Bug#681644: unblock: ldm-themes/12.07.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ldm-themes 12.07.1 resolves two important bugs from the previous version (12.06.1), not leaving alternatives after purge (#679208) and Finishing up the switch to the Joy theme (#678474): ldm-themes (12.07.1) unstable; urgency=low [ Jonathan Carter ] * Remove all alternatives (Closes: #679208). * Replace murrine gtk theme with mist in greeter-gtkrc. * Replace recommends on gtk2-engines-murrine with gtk2-engines, as it is already used in ldm, and doesn't pull in extraneous Recommends. * Fix typos in package description. * My first upload at a Debconf! :D [ Vagrant Cascadian ] * Remove spacefun theme, as it was never shipped with squeeze. * Remove unnecessary .png files that are already shipped with ldm. * Update debian/copyright to reflect switch to Joy theme. * Finish switching to Joy theme (Closes: #678474). -- Vagrant Cascadian vagr...@debian.org Fri, 13 Jul 2012 10:36:45 -0600 The debdiff with the version in testing (12.06.1) is admittedly quite large, but needed in order to not pull in a large recommends chain caused by gtk2-engines-murrine (more on that in http://bugs.debian.org/623783, although the situation is even worse now). We also removed the spacefun theme which also used gtk2-engines-murrine, and was never actually released as part of squeeze. Now it actually uses gtk2-engines already recommended by ldm, which makes it more feasible for ldm to default to a Joy based theme like (hopefully) the rest of wheezy. KiBi gave the go-ahead in irc for sane changes, hopefully these count as sane. :) unblock ldm-themes/12.07.1 live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120715002748.GL21245@talon.fglan
Bug#680457: unblock: ltsp/5.4.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: pkg-ltsp-de...@lists.alioth.debian.org Please unblock package ltsp Not touching package due to block-udeb request by freeze The ltsp-client-builder udeb appears to be holding it up, but is not used in the default installer. Thanks! unblock ltsp/5.4.2-2 live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120705231636.GX21245@talon.fglan
Bug#617460: Processed: tagging 617460, block 617460 with 614404
On Sun, Jan 22, 2012 at 07:19:41PM +0100, Cyril Brulebois wrote: Debian Bug Tracking System ow...@bugs.debian.org (13/05/2011): Processing commands for cont...@bugs.debian.org: tags 617460 + squeeze Bug #617460 [release.debian.org] pu: package zoneminder/1.24.2-8 Added tag(s) squeeze. block 617460 with 614404 Bug #617460 [release.debian.org] pu: package zoneminder/1.24.2-8 Was not blocked by any bugs. Added blocking bug(s) of 617460: 614404 thanks Stopping processing here. the merge window for 6.0.4 closed today, so I'd like to know whether this update should be considered for 6.0.5. The blocking bug, 614404, seems to be closed now, so maybe we could get things going for the next point release? Or are the changes too intrusive to be backported to squeeze? thanks for checking in. the changes are a bit too intrusive with the new upstream versions- there are no specific series of patches that fixed it upstream, and the patch (for the version in squeeze) didn't really work well for me, although others report that amd64 works fine for them even without the patch, so maybe bug #614404 should be downgraded to important. perhaps we should close 617460, as i don't see a fix in the near future... i might try to upload 1.25.0 when it hits testing to backports.debian.org as a workaround, for those who need it... live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120123170022.GA3372@talon.fglan
Bug#617460: pu: package zoneminder/1.24.2-8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu i'd like to upload a new version of zoneminder to squeeze in order to fix #614404, which causes a wide variety of IP cameras to fail on the amd64 architecture. in the bug report there is a patch that i've tested that fixes the problem, although also generates numerous new compiler warnings. as best i can tell, the warnings do not appear to actually cause a problem. live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110309035326.GD10855@talon.fglan
Bug#610476: unblock: zoneminder/1.24.2-8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package zoneminder it fixes two RC bugs, one involving data loss in some upgrade scenarios, and the other involving failure to work with a variety of cameras. zoneminder (1.24.2-8) unstable; urgency=medium [ Vagrant Cascadian ] * Apply patch to fix V4L2 cameras without crop support (closes: #608790). Thanks to piratebab. * Add preinst script which aborts if dangerous symlinks exist. (closes: #608793) [ Peter Howard ] * Added to README.Debian with info about images and events directories. (closes: #608793) -- Vagrant Cascadian vagr...@debian.org Sat, 15 Jan 2011 19:39:26 -0800 unblock zoneminder/1.24.2-8 live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110118215536.GN17410@talon.fglan
Bug#605806: unblock: qemu/0.12.5+dfsg-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking package qemu as it fixes a release-critical bug that breaks debootstrap (and presumably other similar tools) in some cases: qemu (0.12.5+dfsg-3) unstable; urgency=medium * qemu-user-static: - Drop binfmt support for emulating amd64 on i386, as it is broken and including it interferes with environments capable of running amd64 natively. Closes: #604712. - Remove binfmt support for installed targets in postinst before installing supported targets, to ensure no-longer-supported targets are actually removed. - Remove binfmt support for installed targets in prerm. -- Vagrant Cascadian vagr...@debian.org Sun, 28 Nov 2010 15:57:11 -0800 unblock qemu/0.12.5+dfsg-3 live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101203171857.gj17...@talon.fglan
Bug#597471: unblock: zoneminder/1.24.2-7
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package zoneminder the -6 version fixes two RC bugs, and the -7 version fixes a regression introduced when fixing those bugs. zoneminder (1.24.2-7) unstable; urgency=medium * Do not set ownership of /var/cache/zoneminder when upgrading, which fixes a regression causing upgrades to take inordinately long with large installations (closes: #597040). -- Vagrant Cascadian vagr...@debian.org Fri, 17 Sep 2010 11:24:41 -0700 zoneminder (1.24.2-6) unstable; urgency=low * Only remove database on purge. This requires only creating the database if it doesn't already exist, and upgrading the database only if the database is an older version (closes: #497107). * Do not prompt the user on database upgrades by using the --nointeractive flag when calling zmupdate.pl from postinst (closes: #595902). -- Vagrant Cascadian vagr...@debian.org Fri, 10 Sep 2010 10:06:06 -0700 unblock zoneminder/1.24.2-7 thanks for all your work! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100920005917.ga1...@claws.fglan
Bug#595887: unblock: ltsp-docs/0.99+bzr115-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ltsp-docs. it adds documentation for several features, and removes duplicated documentation for the FRONT_VOLUME environment variable (not mentioned in debian/changelog). it also switches from dpkg source format 1.0 with no patch system to 3.0 (quilt), and updates the standards-version. ltsp-docs (0.99+bzr115-1) unstable; urgency=low * New upstream version: - Document LDM_LIMIT_ONE_SESSION, LDM_LIMIT_ONE_SESSION_PROMPT, and HOSTNAME* lts.conf options. * Switch to source format 3.0 (quilt). * Update Standards-Version to 3.9.1, no changes necessary. -- Vagrant Cascadian vagr...@debian.org Mon, 30 Aug 2010 12:13:18 -0700 unblock ltsp-docs/0.99+bzr115-1 thanks for your work, time and consideration! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100907000537.gw28...@claws.fglan
Bug#594939: unblock: ltspfs/0.7-2
On Sat, Sep 04, 2010 at 01:30:24PM +0200, Julien Cristau wrote: On Mon, Aug 30, 2010 at 14:13:09 -0700, Vagrant Cascadian wrote: unblock ltspfs/0.7-2 thanks for the comments. autom4te.cache/output.0 | 511 +--- autom4te.cache/output.1 | 511 +--- autom4te.cache/requests |2 autom4te.cache/traces.0 | 38 +-- autom4te.cache/traces.1 |8 Why is this crap in the source package? it's in the upstream tarballs... a lot of unfortunate noise, yes. -Conflicts: ldm (= 2:0.1~bzr20071217-1) +Breaks: ldm (= 2:0.1~bzr20071217-1) +Replaces: ldm (= 2:0.1~bzr20071217-1) -Conflicts: ltspfsd (= 0.5.11-1) +Breaks: ltspfsd (= 0.5.11-1) +Replaces: ltspfsd (= 0.5.11-1) Why is this correct? Was the upgrade path from lenny tested? ltspfsd took over some files that were formerly in ldm and ltspfsd-core took over some files from ltspfsd. so i was attempting to comply with debian-policy 7.6.1. Overwriting files in other packages: Normally, `Breaks' should be used in conjunction with `Replaces'.[1] For example, if a package `foo' is split into `foo' and `foo-data' starting at version 1.2-3, `foo-data' would have the fields Replaces: foo ( 1.2-3) Breaks: foo ( 1.2-3) apparently, it wasn't strictly needed; the Conflicts is actually sufficient to handle upgrades without resulting in file conflicts. Breaks+Replaces also works for upgrading from lenny. should i prepare another upload with a patch removing the autom4te.cache/* files and switching back to Conflicts? live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100904231319.gs28...@claws.fglan
Bug#594939: unblock: ltspfs/0.7-2
On Mon, Aug 30, 2010 at 02:13:09PM -0700, Vagrant Cascadian wrote: i uploaded a new upstream version to ltspfs (0.7-1) to experimental in order to test it. after some testing, i think it would be good to get these changes into squeeze as well. some more details... it handles multiple CD/DVD-ROM drives and particularly USB CD/DVD-ROM drives much more sanely than the current version in squeeze. the current version leaves old processes running even after USB CD/DVD-ROMs have been removed. ltspfs (0.7-1) experimental; urgency=low * New upstream version: - Improve cdrom handling. filed Bug#595406: ltspfsd-core: cdpinger doesn't work well with USB CDROM drives, which includes the patch applied upstream. - Add example ltspfs hook to issue notifications for desktops that do not display icons on the desktop. Thanks to Petter Reinholdtsen. (Partially resolves Debian bug #575031). this is a documentation change only. * Update Standards-Version to 3.9.1: - Change Conflicts to Breaks+Replaces for ltspfsd and ltspfsd-core. i think this may fix upgrading problems from older versions, as the replaces wasn't previously present, and file conflict insanity would ensue... * Switch to source format 3.0 (quilt). -- Vagrant Cascadian vagr...@debian.org Wed, 25 Aug 2010 16:11:48 -0700 the source format change was previously 1.0 with no patch system, so 3.0 (quilt) shouldn't introduce any problems. if you think the above changes are acceptible, i'll upload 0.7-2 to unstable. seems to me like it meets the criteria mentioned in the recent Release Update: http://lists.debian.org/debian-devel-announce/2010/09/msg0.html so i'll go ahead and upload to unstable with these changes. live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903202638.gr28...@claws.fglan
Bug#594939: unblock: ltspfs/0.7-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package ltspfs i uploaded a new upstream version to ltspfs (0.7-1) to experimental in order to test it. after some testing, i think it would be good to get these changes into squeeze as well. it handles multiple CD/DVD-ROM drives and particularly USB CD/DVD-ROM drives much more sanely than the current version in squeeze. the current version leaves old processes running even after USB CD/DVD-ROMs have been removed. the other changes are fairly small: ltspfs (0.7-1) experimental; urgency=low * New upstream version: - Improve cdrom handling. - Add example ltspfs hook to issue notifications for desktops that do not display icons on the desktop. Thanks to Petter Reinholdtsen. (Partially resolves Debian bug #575031). * Update Standards-Version to 3.9.1: - Change Conflicts to Breaks+Replaces for ltspfsd and ltspfsd-core. * Switch to source format 3.0 (quilt). -- Vagrant Cascadian vagr...@debian.org Wed, 25 Aug 2010 16:11:48 -0700 the source format change was previously 1.0 with no patch system, so 3.0 (quilt) shouldn't introduce any problems. if you think the above changes are acceptible, i'll upload 0.7-2 to unstable. thanks for your work and consideration! unblock ltspfs/0.7-2 live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100830211309.gh28...@claws.fglan
please allow ltsp 5.1.83-1 into testing
ltsp 5.1.83-1 is blocked from migrating into testing, due to the ltsp-client-builder udeb, though this udeb is not used by debian-installer by default, and has no changes since the previous version. it has been in unstable for 7 days without introducing new problems. thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
please allow ltsp 5.1.81-2 into testing
ltsp 5.1.81-2 is blocked from migrating into testing, due to the ltsp-client-builder udeb, though this udeb is not used by debian-installer by default, and has no changes since the previous version. it has been in unstable for 9 days without introducing new problems. thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
please allow simple-cdd 0.3.11 into testing
simple-cdd 0.3.11 is blocked from migrating to testing, as it contains the simple-cdd-profiles udeb, which is not used by default in debian-installer. no changes were made to the udeb since the version in testing. no new issues have been reported, and has been in unstable 9 days. please consider unblocking simple-cdd 0.3.11. thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
please allow ltsp 5.1.77-1 into testing
ltsp 5.1.77-1 is blocked from migrating into testing, due to the ltsp-client-builder udeb, though this udeb is not used by debian-installer by default, and has no changes since the previous version. it has been in unstable for 9 days without introducing new problems. thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
please allow debian-edu-install 0.677 into testing
please allow debian-edu-install 0.677 into testing, which is blocked from migrating due to it's udebs. i do not believe the udebs are used in a default install, and thus shouldn't impact debian-installer. this would bring squeeze closer in sync with what the debian-edu team is actively working on. it includes a handful of translations, and resolves many lintian issues. it's waited in unstable 7 days thus far without any new reported bugs. many thanks for all your hard work! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
please allow ltsp 5.1.76-1 into testing
ltsp 5.1.76-1 is blocked from migrating into testing, due to the ltsp-client-builder udeb, though this udeb is not used by debian-installer by default, and has no changes since the previous version. it has been in unstable for 8 days without introducing new problems. thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
please allow debian-edu-install 0.675 into testing
please allow debian-edu-install 0.675 into testing, which is blocked from migrating due to it's udebs. i do not believe the udebs are used in a default install, and thus shouldn't impact debian-installer. this would bring squeeze much closer in sync with what the debian-edu team is actively working on. it's waited in unstable 18 days thus far without any new reported bugs (other than updated translations). i had sent a previous request, but wanted to make sure it didn't just slip through the cracks: http://lists.debian.org/debian-release/2009/06/msg00021.html many thanks for all your hard work! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
please allow debian-edu-install 0.675 into testing
please allow debian-edu-install 0.675 into testing, which is blocked from migrating due to it's udebs. i do not believe the udebs are used in a default install, and thus shouldn't impact debian-installer. this would bring squeeze much closer in sync with what the debian-edu team is actively working on. it's waited in testing 9 days thus far without any new reported bugs (other than translations). many thanks for all your hard work! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
please allow ltsp 5.1.73-1 into testing
ltsp is blocked from migrating into testing, due to the ltsp-client-builder udeb, though this udeb is not used by debian-installer by default, and has no changes since the previous version. it has been in unstable for 6 days without introducing new problems, and includes several updated translations, new manpages, updated manpages, and updated documentation. thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
please allow simple-cdd 0.3.10 into testing
simple-cdd 0.3.10 is blocked from migrating to testing, as it contains the simple-cdd-profiles udeb, which is not used by default in debian-installer. no changes were made to the udeb since the version in testing. no new issues have been reported, it closes a couple bugs, and has been in unstable 10 days. please consider unblocking simple-cdd 0.3.10. thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
please allow ltsp 5.1.69-1 into testing
ltsp is blocked from migrating into testing, due to the ltsp-client-builder udeb, though this udeb is not used by debian-installer by default, and has no changes since the previous version. it has been in unstable for 6 days without introducing new problems, and includes several updated translations. thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
please allow ltsp 5.1.64-1 into testing
ltsp is blocked from migrating into testing, due to the ltsp-client-builder udeb, though this udeb is not used by debian-installer by default, and worked fine in my last tests. it has been in unstable for 11 days without introducing new problems, fixes several bugs, and gets the packages back in sync with upstream. it is currently waiting on ldm to migrate to testing, but that also should progress as soon as the alpha build for ldm is uploaded. one can hope. thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: request for simple-cdd freeze exception
On Wed, Jan 14, 2009 at 11:15:14PM +0100, Adeodato Simó wrote: * Neil McGovern [Wed, 14 Jan 2009 18:20:26 +]: Please go ahead and reping when it's hit unstable for an unblock. Unblocked. it seems that simple-cdd 0.3.8 was unblocked, but it was 0.3.9 that needed unblocking: $ grep-excuses simple-cdd simple-cdd (0.3.8 to 0.3.9) Maintainer: Vagrant Cascadian Too young, only 3 of 10 days old Unblock request by adeodato ignored due to version mismatch: 0.3.8 Not touching package, as requested by freeze (contact debian-release if update is needed) Not considered Depends: simple-cdd debian-cd (not considered) it also seems like debian-cd hasn't yet been unblocked, although the time needed to migrate was modified: $ grep-excuses debian-cd debian-cd (3.0.5 to 3.1.0) Maintainer: Debian CD Group Too young, only 5 of 12 days old Not touching package, as requested by freeze (contact debian-release if update is needed) Overriding age needed from 10 days to 12 by adeodato Not considered thanks! live well, vagrant -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
request for simple-cdd freeze exception
i intend to upload a version of simple-cdd that works with the recent debian-cd
upload targeted for lenny. a diff of planned changes is attached.
please review if it would be acceptible for a freeze exception.
simple-cdd (0.3.9) unstable; urgency=low
* depend on debian-cd = 3.1.0
* update task and exclude handling to support newer versions of debian-cd.
* set MAXISOS and MAXJIGDOS used in newer versions of debian-cd.
* only download installer when DI_WWW_HOME is not set, as debian-cd will
handle it.
* fix BOOT_TIMEOUT parameter.
* debian/control: use proper Vcs-* header.
* update architecture specific kernel selection.
* ensure that relevent linux-image-2.6-* packages are also installed, as
changes to linux-image metapackages do not pull in linux-image-2.6-* by
default, which causes debian-installer to ask which kernel to install.
* exit if being run as root. add --force-root commandline option to override.
* profile updates:
- ltsp:
+ include commented out example to enable DHCP server
+ remove packages no longer needed
- vserver:
+ ensure that a vserver capable kernel is installed
+ install util-vserver and debootstrap by default
+ lower vserver-debiantools to an optional package
-- Vagrant Cascadian vagr...@freegeek.org Mon, 12 Jan 2009 12:42:44 -0800
live well,
vagrant
=== modified file 'build-simple-cdd'
--- build-simple-cdd 2008-06-20 17:56:35 +
+++ build-simple-cdd 2009-01-12 20:14:04 +
@@ -37,6 +37,7 @@
--help|-h display this help
--qemu|-q use qemu to test the image
--force-preseed only issue a warning if a preseeding file is invalid
+--force-root allow running as root
--profiles-udeb-dist pull simple-cdd-profiles udeb from other distribution
--extra-udeb-dist also pull in udebs from specified distribution
--require-optional-packages fail if missing optional packages (*.downloads)
@@ -94,6 +95,7 @@
--extra-udeb-dist) extra_udeb_dist=$2
shift ;;
--require-optional-packages) export require_optional_packages=true ;;
+--force-root) force_root=true ;;
*) get_help ERROR: unknown commandline option: $1 /dev/stderr
exit 1 ;;
esac
@@ -157,6 +159,10 @@
# get defaults, and have build profiles over-ride all others
get_config default $profiles $build_profiles
+if [ $force_root != true ] [ $UID = 0 ]; then
+ die Running as root is strongly discouraged. please run as a non-root user.
+fi
+
test -z $server server=ftp.us.debian.org
test -z $debian_mirror debian_mirror=ftp://$server/debian/;
test -z $wget_debian_mirror wget_debian_mirror=$debian_mirror
@@ -200,6 +206,7 @@
test -z $MAXCDS export MAXCDS=1
test -z $OMIT_RELEASE_NOTES export OMIT_RELEASE_NOTES=1
test -z $DOJIGDO export DOJIGDO=0
+test -z $MAXJIGDOS export MAXJIGDOS=0
export MIRROR=$simple_cdd_mirror
export BASEDIR=$simple_cdd_basedir
@@ -221,7 +228,9 @@
debian-cd)
test -z $debian_cd_dir debian_cd_dir=/usr/share/debian-cd
# set include files for debian-cd
-test -z $includes includes=$BASEDIR/tasks/debian-installer+kernel-$CODENAME $BASEDIR/tasks/debian-installer-$CODENAME $BASEDIR/tasks/base-$CODENAME
+test -z $includes includes=debian-installer+kernel debian-installer
+# ensure that ISO images are built
+test -z $MAXISOS export MAXISOS=ALL
;;
esac
done
@@ -304,12 +313,17 @@
done
if [ -z $kernel_packages ]; then
-# FIXME: add appropriate kernels for other architectures.
-for a in $ARCHES ; do
-case $a in
-i386) kernel_packages=$kernel_packages linux-image-486 ;;
-*) kernel_packages=$kernel_packages linux-image-$a ;;
-esac
+# guess appropriate kernel for architectures
+for kernel_base in linux-image- linux-image-2.6- ; do
+for a in $ARCHES ; do
+case $a in
+i386) kernel_packages=$kernel_packages ${kernel_base}486 ;;
+powerpc|amd64|s390) kernel_packages=$kernel_packages ${kernel_base}$a ;;
+alpha) kernel_packages=$kernel_packages ${kernel_base}alpha-generic ;;
+sparc) kernel_packages=$kernel_packages ${kernel_base}sparc64 ;;
+*) echo WARNING: unable to guess kernel for architecture: $a ;;
+esac
+done
done
fi
@@ -372,7 +386,7 @@
mkdir -p $BASEDIR
if [ true = $do_mirror ] || [ -z $do_mirror ] ; then
-if [ -z $custom_installer ]; then
+if [ -z $custom_installer ] [ -z $DI_WWW_HOME ]; then
# add d-i files for each architecture
for a in $ARCHES ; do
case $a in
=== modified file 'debian/control'
--- debian/control 2008-10-31 22:19:34 +
+++ debian/control 2009-01-12 18:55:28 +
@@ -4,12 +4,12 @@
Maintainer: Vagrant Cascadian vagr...@freegeek.org
Build-Depends: debhelper (= 5.0.22), cdbs, libdebian-installer4-dev (= 0.41), libdebconfclient0-dev (= 0.49
Re: freeze exception request for ltspfs
On Sat, Nov 01, 2008 at 10:41:59AM +0100, Marc 'HE' Brockschmidt wrote: Vagrant Cascadian [EMAIL PROTECTED] writes: i'd like the release team to consider a freeze exception for ltspfs to fix a segfault in the cdpinger binary. patch attached. i'd also like to add a new team member to Uploaders. i could upload 0.5.3-3 with those changes. Please do so. uploaded, please unblock: ltspfs (0.5.3-3) unstable; urgency=low * apply patch to fix cdpinger segfault * add Ryan Niebur to Uploaders -- Vagrant Cascadian [EMAIL PROTECTED] Sat, 01 Nov 2008 17:21:32 -0700 live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
please allow simple-cdd 0.3.8 into testing
please unblock simple-cdd 0.3.8. the recent debian-cd upload (3.0.5) required a minor change to simple-cdd to continue working with lenny. it contains a patch to include syslinux-common and syslinux when building the local mirror, which is needed to work with debian-cd 3.0.5. also increased upped the versioned depenency to debian-cd = 3.0.5, as older versions do not work with lenny and simple-cdd. no new issues have been reported, and has been in unstable 4 days thus far. the simple-cdd-profiles udeb is not used by default in debian-installer. only people building CDs using simple-cdd will make use of the udeb, and no changes were made to the udeb since the version in testing. thanks! the diff since the previous version: === modified file 'debian/changelog' --- debian/changelog2008-06-29 23:28:49 + +++ debian/changelog2008-10-31 23:42:33 + @@ -1,3 +1,11 @@ +simple-cdd (0.3.8) unstable; urgency=low + + * add syslinux-common and syslinux to default packages to download which +fixes builds with newer versions debian-cd + * depend on debian-cd = 3.0.5, to ensure simple-cdd works with lenny + + -- Vagrant Cascadian [EMAIL PROTECTED] Fri, 31 Oct 2008 16:39:36 -0700 + simple-cdd (0.3.7) unstable; urgency=low * improved commandline processing, based on patch from Bruce Korb === modified file 'debian/control' --- debian/control 2008-06-29 23:27:36 + +++ debian/control 2008-10-31 22:19:11 + @@ -9,7 +9,7 @@ Package: simple-cdd Architecture: all -Depends: rsync, debian-cd (= 3.0.0), reprepro | debpartial-mirror, apt-utils, wget, python, debootstrap, lsb-release, dctrl-tools +Depends: rsync, debian-cd (= 3.0.5), reprepro | debpartial-mirror, apt-utils, wget, python, debootstrap, lsb-release, dctrl-tools Suggests: qemu Description: create custom debian-installer CDs simple-cdd is a limited though relatively easy tool to create a customized === modified file 'profiles/default.downloads' --- profiles/default.downloads 2008-06-19 01:26:29 + +++ profiles/default.downloads 2008-10-31 21:11:24 + @@ -28,3 +28,7 @@ # initramfs-tools recommends busybox, and we don't yet support recommends busybox + +# newer debian-cd (0.3.5+) requires syslinux-common or syslinux in the mirror +syslinux-common +syslinux live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
freeze exception request for ltspfs
i'd like the release team to consider a freeze exception for ltspfs to fix a
segfault in the cdpinger binary. patch attached. i'd also like to add a new
team member to Uploaders. i could upload 0.5.3-3 with those changes.
alternately, i could pull 0.5.5-1 from experimental. the diff between
upstream 0.5.3 and 0.5.5 is pretty small, containing the segfault fix
for cdpinger, and manpages which we are currently shipping in the debian
dir(in 0.5.3-2).
0.5.5-1 contains a small change to debian/rules to allow for different
udev rules priority on ubuntu (adds a build-dep on lsb-release).
ltspfs (0.5.5-1) experimental; urgency=low
* new upstream version
* sync with ubuntu
* conditionally install udev rules at priority 80 on Ubuntu
-- Vagrant Cascadian [EMAIL PROTECTED] Sun, 19 Oct 2008 11:05:23 -0700
ltspfs (0.5.5-0ubuntu1) intrepid; urgency=low
* new upstream version:
* Fix a segfault in cdpinger
* Remove manpages from packaging as they now are upstream
-- Stéphane Graber [EMAIL PROTECTED] Fri, 10 Oct 2008 19:34:18 -0400
ltspfs (0.5.3-2ubuntu1) intrepid; urgency=low
* Set ltspfs rules to 80 instead of 50. (LP: #273147)
-- Stéphane Graber [EMAIL PROTECTED] Tue, 07 Oct 2008 13:30:55 -0400
thanks for your consideration!
live well,
vagrant
=== modified file 'src/cdpinger.c'
--- src/cdpinger.c 2008-04-22 17:22:29 +
+++ src/cdpinger.c 2008-10-11 00:06:14 +
@@ -18,6 +18,8 @@
CDP_CDROM_UMOUNT
} CdpMountType;
+char *device;
+
/*
* check_cd_status: Switch mounted and unmounted states in the cdrom, and
* call out our shell scripts to handle the actual work of plumbing the
@@ -25,13 +27,13 @@
*/
gboolean
-check_cd_status(gpointer device)
+check_cd_status()
{
char dev[BUFSIZ], cmd[BUFSIZ];
int cdrom, status;
static CdpMountType last = CDP_CDROM_UMOUNT;
-snprintf(dev, sizeof dev, /dev/%s, (char *)device);
+snprintf(dev, sizeof dev, /dev/%s, device);
/*
* Try to open the cdrom device. It might not exist, for a usb cdrom,
@@ -40,9 +42,11 @@
*/
if ((cdrom = open(dev, O_RDONLY|O_NONBLOCK)) 0) {
-snprintf(cmd, sizeof cmd,
-/lib/udev/ltspfs_entry remove %s, (char *)device);
-g_spawn_command_line_sync(cmd, NULL, NULL, NULL, NULL);
+if (last == CDP_CDROM_MOUNT) {
+snprintf(cmd, sizeof cmd,
+/lib/udev/ltspfs_entry remove %s, device);
+g_spawn_command_line_sync(cmd, NULL, NULL, NULL, NULL);
+}
return FALSE;
}
@@ -61,7 +65,7 @@
if (status 0) {
snprintf(cmd, sizeof cmd,
-/lib/udev/ltspfs_entry remove %s, (char *)device);
+/lib/udev/ltspfs_entry remove %s, device);
return g_spawn_command_line_sync(cmd, NULL, NULL, NULL, NULL);
return FALSE;
}
@@ -76,7 +80,7 @@
case CDS_TRAY_OPEN:
if (last == CDP_CDROM_MOUNT) {
snprintf(cmd, sizeof cmd,
-/lib/udev/ltspfs_entry remove %s, (char *)device);
+/lib/udev/ltspfs_entry remove %s, device);
last = CDP_CDROM_UMOUNT;
return g_spawn_command_line_sync(cmd, NULL, NULL, NULL, NULL);
}
@@ -84,7 +88,7 @@
case CDS_DISC_OK:
if (last == CDP_CDROM_UMOUNT) {
snprintf(cmd, sizeof cmd,
-/lib/udev/ltspfs_entry add %s auto, (char *)device);
+/lib/udev/ltspfs_entry add %s auto, device);
last = CDP_CDROM_MOUNT;
return g_spawn_command_line_sync(cmd, NULL, NULL, NULL, NULL);
}
@@ -114,13 +118,17 @@
if (argc != 2)
exit(1);
+g_type_init();
+
+device = argv[1];
+
daemon(0,0);
loop = g_main_loop_new (NULL, FALSE);
/* Add a timeout */
g_timeout_add_full(G_PRIORITY_DEFAULT, POLL_INTERVAL * 1000,
-(GSourceFunc)check_cd_status, argv[1],
+(GSourceFunc)check_cd_status, NULL,
(GDestroyNotify)end_cd_watch);
g_main_loop_run(loop);
freeze exception for ldm 2:2.0.6-4
On Sat, Oct 11, 2008 at 08:54:11PM +0200, Adeodato Simó wrote: * Vagrant Cascadian [Tue, 07 Oct 2008 15:28:27 -0700]: ldm (2:2.0.6-3) unstable; urgency=low * backported patch from upstream to use /etc/X11/Xsession when user has selected a session from login menu. (Closes: #45) * add debian/README.source explaining use of dpatch * add Ryan Niebur to Uploaders -- Vagrant Cascadian [EMAIL PROTECTED] Mon, 29 Sep 2008 09:00:50 -0700 It seems that the -3 upload introduced a spurious debian.old directory. Would it be possible to upload a -4 that just drops it? apologies. i just tested and uploaded 2:2.0.6-4: ldm (2:2.0.6-4) unstable; urgency=medium * remove debian.old dir accidentally added in previous upload. * urgency medium to get important changes into lenny. -- Vagrant Cascadian [EMAIL PROTECTED] Sat, 11 Oct 2008 14:20:11 -0700 please unblock. thanks! live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
freeze exception for ldm 2:2.0.6-3
please allow ldm 2:2.0.6-3 into lenny. i requested an exception for these changes previously: http://lists.debian.org/debian-release/2008/09/msg01133.html additionally, i added a new team member to Uploaders in debian/control. it has been in unstable for 8 days with no new problems reported. thanks! ldm (2:2.0.6-3) unstable; urgency=low * backported patch from upstream to use /etc/X11/Xsession when user has selected a session from login menu. (Closes: #45) * add debian/README.source explaining use of dpatch * add Ryan Niebur to Uploaders -- Vagrant Cascadian [EMAIL PROTECTED] Mon, 29 Sep 2008 09:00:50 -0700 live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
freeze exception request for ldm
i'd like the release team to consider an exception for ldm to fix debian bug #45, which causes /etc/X11/Xsession not to get used if the user selects a session from the login menu. tested patch is included in the bug report. i'd also like to add debian/README.source to document the use of dpatch in ldm. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
freeze exception for ltspfs 0.5.3-2
please consider a freeze exception for ltspfs 0.5.3-2, which adds manpages for all remaining binaries, and removes a build-dependency on dpatch (as we haven't shipped any patches for several versions), and is now lintian-clean. it's been in unstable for a good 8 days now without troubles. thanks! ltspfs (0.5.3-2) unstable; urgency=low * added manpages for cdpinger, ltspfs_mount and ltspfs_umount * remove dpatch from debian/rules and drop build-dependency, as there are no patches. -- Vagrant Cascadian [EMAIL PROTECTED] Mon, 25 Aug 2008 15:27:30 -0700 live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
freeze exception for ldm 2:2.0.6-2
please consider a freeze exception for ldm 2:2.0.6-2, which allows pam sessions to properly register logouts. it has been in unstable for 13 days without any reported issues. enabling this feature appears to require openssh-server 5.1 installed on any server that ldm users would log into, so it is disabled by default. ldm (2:2.0.6-2) unstable; urgency=low * apply patch to allow for cleanly disconnecting ssh session, so pam sessions to properly register logouts. thanks to Pascal Legrand for the report. (Closes: #471793) * updated Standards-Version to 3.8.0, no changes needed. -- Vagrant Cascadian [EMAIL PROTECTED] Wed, 20 Aug 2008 16:29:22 -0700 thanks! live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
freeze exception for ltsp 5.1.10-2
please consider a freeze exception for ltsp 5.1.10-2. debian-boot CCed as it contains a udeb, but no changes were made to the udeb. it includes a patch to use debootstrap's gpg verification, so that the initial ltsp chroot doesn't get created with potentially untrusted packages. it also adds support for rsyslog, now the default syslog daemon on lenny. it's reached a ripe age of 13 days in unstable with no new reported problems. ltsp (5.1.10-2) unstable; urgency=low * backported patches from upstream: - support for using rsyslog as a logging daemon (default on lenny) - use server's apt keyring to verify gpg signatures with debootstrap -- Vagrant Cascadian [EMAIL PROTECTED] Wed, 20 Aug 2008 22:17:37 -0700 thanks! live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-ltsp-devel] freeze exception for ltsp 5.1.10-2
On Wed, Sep 03, 2008 at 10:50:50PM +0200, Petter Reinholdtsen wrote: [Vagrant Cascadian] please consider a freeze exception for ltsp 5.1.10-2. ...snip... it includes a patch to use debootstrap's gpg verification, so that the initial ltsp chroot doesn't get created with potentially untrusted packages. Is this tested with unsigned CDs? The reason I ask, is that the Debian Edu CDs are not signed, and I would hate to have the LTSP installation break because of this. using the defaults, yes. unsigned CDs will not work. although that is also the case with the previous version, unless you pass particular commandline options or ltsp-build-client plugins. i just committed a simple fix to debian-edu-config svn to handle the issue, although it would likely break with the version of debian-edu-config currently in lenny. it also adds support for rsyslog, now the default syslog daemon on lenny. This seem like a good idea, but how is the ram usage of rsyslog compared to sysklogd? On my NSLU2, rsyslog seem to use 27 MB (with ~1 MB RSS, perhaps it is just mmap-ing a lot of files? i've been testing on 64MB thin clients, and haven't noticed much, if any increase in ram requirements. i'd like to think i'd notice something that consumed that much memory. :) Sorry for not bringing this up earlier. Did not notice these planned changes before now. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
please allow ltsp 5.1.10-1 into testing
ltsp is again blocked from migrating into testing, likely due to the ltsp-client-builder udeb, though this udeb is not used by debian-installer by default. it has been in unstable for 8 days without introducing new problems, and fixes several bugs. thanks! also, i noticed that even though the previous version (5.1.9-1) already migrated to testing, grep-excuses ltsp and http://packages.qa.debian.org/l/ltsp.html reports a version mismatch from the previous unblock request. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
please allow ltsp 5.1.9-1 into testing
ltsp is again blocked from migrating into testing, likely due to the ltsp-client-builder udeb, though this udeb is not used by debian-installer by default. it has been in unstable for 7 days now, without introducing new problems, and fixes several bugs. thanks for your work. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
please reschedule ia64 build for ldm
it appears the ia64 buildd failed when trying to build ldm because one of the build-dependencies (intltool - libxml-parser-perl) wasn't installable due to the perl-5.10 transition... that appears to be resolved now. http://buildd.debian.org/~jeroen/status/package.php?p=ldm#fail-ldm-ia64 please put it back in the ia64 buildd queue. thanks! live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
requesting freeze exception for ltsp
hello again. ltsp 0.99debian11 is in sid, and contains fixes for RC and
important bugs that should enter etch, as well as some translation and
documentation updates. please consider allowing it to progress to etch.
it has seen 3 days in debian sid, as well as over a week in the
debian-edu archives. people have tested that the packages work...
(the alpha buildd has not yet built the ltsp-client package, but i've
never seen alpha-specific problems in the past...)
from the changelog, 0.99debian11:
* install appropriate linux-image package for amd64. thanks to Damyan
Ivanov. (Closes: #406357)
this one-line patch installs the appropriate kernel for amd64
architecture.
* fixes to boolean handling (Closes: #405772)
this fixes boolean handling in some cases so that false does not
behave identical to true, and consistantly use the same values for
boolean configuration options in both the init scripts and ldm.
* drop dependency on initrd-netboot-tools as it was removed from Debian.
(initramfs-tools is preferred anyways)
initrd-netboot-tools was a dependency before initramfs-tools was in
debian, and is deprecated (was mostly kept for sarge backportability)
and initrd-netboot-tools has since been removed from the debian archive
entirely.
* updated location of pkg-ltsp bzr repository
we moved our debian ltsp bzr branch to bzr.debian.org, and updated
debian/copyright to reflect the new location to download the source.
from 0.99debian10
* added spanish gettext translation. thanks to Felipe Caminos and Hector
Colina. (Closes: #404404)
attached should be a patch showing the differences between 0.99debian11
and 0.99debian9 (the version currently in etch), minus the spanish
gettext translation.
thanks for your consideration and work!
live well,
vagrant
=== modified file 'client/ltsp_functions'
--- client/ltsp_functions 2006-02-21 20:21:36 +
+++ client/ltsp_functions 2007-01-11 06:46:05 +
@@ -36,3 +36,10 @@
[ -d /tmp/info ] || mkdir /tmp/info
eval echo \$${VAR} /tmp/info/${VAR}
}
+
+boolean_is_true(){
+case $(echo $1 | tr 'A-Z' 'a-z') in
+ true|y|yes) return 0 ;;
+ *) return 1 ;;
+esac
+}
=== modified file 'debian/control'
--- debian/control 2006-11-09 01:21:12 +
+++ debian/control 2007-01-11 06:39:18 +
@@ -24,7 +24,7 @@
Package: ltsp-client
Pre-Depends: debconf (= 0.5) | debconf-2.0
-Depends: lsb-base, nbd-client, ldm | sdm-terminal | x-display-manager,
initramfs-tools (= 0.73e) | initrd-netboot-tools, syslinux [i386 amd64],
mknbi[i386], yaboot[powerpc], aboot[alpha], sparc-utils[sparc], lsb-release
+Depends: lsb-base, nbd-client, ldm | sdm-terminal | x-display-manager,
initramfs-tools (= 0.73e), syslinux [i386 amd64], mknbi[i386],
yaboot[powerpc], aboot[alpha], sparc-utils[sparc], lsb-release
Recommends: xdebconfigurator, esound | nas
Suggests: cryptsetup, joystick [alpha amd64 arm i386 ia64]
Conflicts: ltsp-utils
=== modified file 'debian/copyright'
--- debian/copyright2006-10-06 19:46:30 +
+++ debian/copyright2007-01-05 19:41:21 +
@@ -6,7 +6,7 @@
The source tree for Debian packages can be downloaded using bzr:
-bzr get http://pkg-ltsp.alioth.debian.org/bzr/main
+bzr get http://bzr.debian.org/bzr/pkg-ltsp/main
The original LTSP sources can be downloaded from: http://ltsp.org
=== modified file 'debian/ltsp-client.init'
--- debian/ltsp-client.init 2006-11-14 22:21:04 +
+++ debian/ltsp-client.init 2007-01-11 06:46:05 +
@@ -35,7 +35,7 @@
}
start_sound() {
-if [ -n $SOUND ]; then
+if boolean_is_true $SOUND ; then
# Detect and report a common problem with thin clients
if [ ! -f /dev/dsp ] ; then
warn Sound requested but /dev/dsp is missing. Continuing.
=== modified file 'debian/ltsp-client.ltsp-client-setup.init'
--- debian/ltsp-client.ltsp-client-setup.init 2006-12-21 20:54:57 +
+++ debian/ltsp-client.ltsp-client-setup.init 2007-01-11 06:46:05 +
@@ -36,7 +36,7 @@
}
configure_localdev() {
-if [ -n $LOCALDEV ]; then
+if boolean_is_true $LOCALDEV ; then
if [ ! -d /var/run/drives ];then
mkdir /var/run/drives
fi
@@ -62,19 +62,19 @@
}
configure_swap() {
-if [ $USE_LOCAL_SWAP = Y ]; then
+if boolean_is_true $USE_LOCAL_SWAP ; then
# Enable local swap partition if found on local disk
for part in `sfdisk -l 2/dev/null | awk '/ 82 / { print $1}'`; do
swap_devices=$swap_devices $part
done
fi
-if [ $NBD_SWAP = Y ]; then
+if boolean_is_true $NBD_SWAP ; then
SWAP_SERVER=${SWAP_SERVER:-$SERVER}
NBD_PORT=${NBD_PORT:-9210}
modprobe nbd
nbd-client $SWAP_SERVER $NBD_PORT /dev/nbd0
swap_devices=$swap_devices /dev/nbd0
fi
-if [ $ENCRYPT_SWAP = Y ]; then
+if boolean_is_true $ENCRYPT_SWAP ; then
if [ -x /sbin/cryptsetup ]; then
please allow ltsp 0.99debian9 into etch
please allow ltsp 0.99debian9 to migrate to etch. no additional bugs have been reported in the 4 days it has been in the archive. it fixes the following important bugs, adds or updates several translations, and includes a small documentation update. these changes were reviewed by debian-release before the package was uploaded. ltsp (0.99debian9) unstable; urgency=medium * urgency medium, it includes it fixes several important bugs: * fix ldm's boolean handling. thanks to Miro Zhorelicky for the patch. (Closes: #403471) * also mount /etc/network/run writeable for proper lo device configuration. (Closes: #403187) * fix execution of screen scripts in /etc/ltsp/screen.d (Closes: #403188) * install xorg instead of x-window-system-core transitional package in new LTSP chroot environments. (Closes: #403234) * updated local devices support. (Closes: #404154) * updated French gettext message. thanks to Cyril Brulebois. * updated gettext messages for Brazilian Portuguese. (Closes: #403815) thanks to André Luís Lopes. * added Spanish debconf translations (Closes: #403604). thanks to Felipe Caminos. * added German debconf and gettext messages (Closes: #403568, #403597). thanks to Wolfgang Schweer. * added gettext translation for Catalan (Closes: #404064). thanks to Jordà Polo. * updated documentation for ltsp-build-client plugins. -- Vagrant Cascadian [EMAIL PROTECTED] Fri, 22 Dec 2006 14:58:18 -0700 thanks! live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
requesting freeze exception for ltsp
greetings. i am preparing an upload of ltsp to fix several important
bugs, and wanted to ensure that all the planned changes would be
acceptable for etch.
from the changelog:
* fix ldm's boolean handling. thanks to Miro Zhorelicky for the patch.
(Closes: #403471)
this corrects a simple typo that prevented ldm from properly parsing
boolean configuration variables.
* also mount /etc/network/run writeable for proper lo device configuration.
(Closes: #403187)
this is a one-line patch adds /etc/network/run to the list of
directories to make writeable on boot, which is necessary for proper
loopback/lo device creation. ltsp is normally mounted with a read-only
root filesystem.
* fix execution of screen scripts in /etc/ltsp/screen.d (Closes: #403188)
fixes a small typo that caused custom ltsp screen scripts to not be run.
these are used by sysadmins to create customized ltsp sessions.
* install xorg instead of x-window-system-core transitional package in new
LTSP chroot environments. (Closes: #403234)
instead of installing the transitional package x-window-system-core,
this patch installs xorg. since ltsp was not part of sarge, i don't
see any need to install x-window-system-core in newly built etch ltsp
environments.
* updated local devices support. (Closes: #404154)
this patch updates the existing hooks in ltsp (ldm and
ltsp-client-setup.init) necessary to work with more recent versions of
ltspfs (used for accessing thin-client usb sticks, floppy, cdrom, etc.).
all of the modified code is disabled by default, and requires adding an
option to a configuration file to enable, so should not break anything
else.
i have tested that all of the above changes actually work as intended.
also included will be several new and updated translations, and a small
documentation update. (#403568, #403597, #403604, #403815, #404064)
attached is a diff between the current ltsp version(0.99debian8) and the
proposed changes (minus the translation/documentation updates. i can
send those too, if that's needed).
live well,
vagrant
diff -ur ltsp-0.99debian8/client/ldm ltsp-0.99debian9/client/ldm
--- ltsp-0.99debian8/client/ldm 2006-11-15 15:11:33.0 -0700
+++ ltsp-0.99debian9/client/ldm 2006-12-22 14:55:47.0 -0700
@@ -17,7 +17,7 @@
def get_config_bool(name):
val = os.environ.get(name)
if val:
-val == val.lower()
+val = val.lower()
else:
return False
if val == 'y' or val == 'yes' or val == 'true':
@@ -160,6 +160,14 @@
# make sure we clean up after logout if localdev is used
if self.use_localdev:
session_manager = session_manager+' ltspfsmounter all
cleanup'
+print info: Enabling localdev support.
+if os.access(/var/run/.static-device, os.F_OK):
+print info: Enabling static localdev support.
+static_dev = open(/var/run/.static-device, r)
+delayed_mnt = open(/var/run/.delayed-mount, a)
+delayed_mnt.writelines(static_dev.readlines())
+delayed_mnt.close()
+static_dev.close()
# set language
if lang != 'None':
diff -ur ltsp-0.99debian8/client/screen_session
ltsp-0.99debian9/client/screen_session
--- ltsp-0.99debian8/client/screen_session 2006-11-15 15:11:33.0
-0700
+++ ltsp-0.99debian9/client/screen_session 2006-12-14 16:36:38.0
-0700
@@ -87,7 +87,7 @@
#
# Go ahead and run the screen script
#
-exec //ltsp/screen.d/${SCREEN_SCRIPT} ${SCREEN_ARGS}
+exec /etc/ltsp/screen.d/${SCREEN_SCRIPT} ${SCREEN_ARGS}
elif [ -x /usr/lib/ltsp/screen.d/${SCREEN_SCRIPT} ]; then
#
# Go ahead and run the screen script
diff -ur ltsp-0.99debian8/debian/ltsp-client.ltsp-client-setup.default
ltsp-0.99debian9/debian/ltsp-client.ltsp-client-setup.default
--- ltsp-0.99debian8/debian/ltsp-client.ltsp-client-setup.default
2006-11-15 15:11:36.0 -0700
+++ ltsp-0.99debian9/debian/ltsp-client.ltsp-client-setup.default
2006-12-14 21:13:28.0 -0700
@@ -13,7 +13,7 @@
# tmpfs/bind directions that get mounted with only directory structure
# preserved
-rw_dirs=/var/cache/man /var/lib/xkb /var/lock /var/run /var/log /var/spool
/var/tmp /tmp /var/lib/discover /etc/hotplug/.run /var/lib/nfs
+rw_dirs=/var/cache/man /var/lib/xkb /var/lock /var/run /var/log /var/spool
/var/tmp /tmp /var/lib/discover /etc/hotplug/.run /var/lib/nfs /etc/network/run
# tmpfs/bind directions that get mounted with directory structure and data
# copied
diff -ur ltsp-0.99debian8/debian/ltsp-client.ltsp-client-setup.init
ltsp-0.99debian9/debian/ltsp-client.ltsp-client-setup.init
--- ltsp-0.99debian8/debian/ltsp-client.ltsp-client-setup.init 2006-11-15
15:11:53.0 -0700
+++ ltsp-0.99debian9/debian/ltsp-client.ltsp-client-setup.init 2006-12-22
please hint ltsp 0.99debian8 into etch
please consider hinting ltsp 0.99debian8 into etch, which is (presumably) held up by the ltsp-client-builder udeb. thanks yet again, again, again! live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[Pkg-ltsp-devel] please hint ltsp 0.99debian7 into etch
please consider hinting ltsp 0.99debian7 into etch, which is (presumably) held up by the ltsp-client-builder udeb. it contains documentation updates, translation updates, security improvements, and additional configurability options that make it more useful. thanks yet again! live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
please hint ltsp 0.99debian5 into etch
please consider hinting ltsp 0.99debian5 into etch, which is (presumably) held up by the ltsp-client-builder udeb. it fixes copyright issues, missing dependencies, and a few other things needed by debian-edu (and possibly other projects). thanks yet again! live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
