Bug#930757: Acknowledgement (unblock: grub2/2.02+dfsg1-19)
I forgot to mention that there are -signed source packages that must go with this, so the unblock lines should in fact be: unblock grub2/2.02+dfsg1-19 unblock grub-efi-amd64-signed/1+2.02+dfsg1+19 unblock grub-efi-arm64-signed/1+2.02+dfsg1+19 unblock grub-efi-ia32-signed/1+2.02+dfsg1+19 (The -signed packages are a couple of days too young at the moment.) Thanks, -- Colin Watson [cjwat...@debian.org] signature.asc Description: PGP signature
Bug#930757: unblock: grub2/2.02+dfsg1-19
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock grub2.
I hope this is the final grub2 update for the buster release. It
consists mainly of a number of patches from Steve McIntyre to clean up
problems with our UEFI Secure Boot support.
diff -Nru grub2-2.02+dfsg1/debian/.git-dpm grub2-2.02+dfsg1/debian/.git-dpm
--- grub2-2.02+dfsg1/debian/.git-dpm2019-05-04 22:58:32.0 +0100
+++ grub2-2.02+dfsg1/debian/.git-dpm2019-06-14 19:04:01.0 +0100
@@ -1,6 +1,6 @@
# see git-dpm(1) from git-dpm package
-9569221816a2a1a832be106440375a612e0121b7
-9569221816a2a1a832be106440375a612e0121b7
+6ee5cc98ec6ca10e00d9cd23a969f0b12ae7ab2e
+6ee5cc98ec6ca10e00d9cd23a969f0b12ae7ab2e
59aeb1cfaa3d5bfd7bb0f0d37f6d9eed51fe
59aeb1cfaa3d5bfd7bb0f0d37f6d9eed51fe
grub2_2.02+dfsg1.orig.tar.xz
diff -Nru grub2-2.02+dfsg1/debian/build-efi-images
grub2-2.02+dfsg1/debian/build-efi-images
--- grub2-2.02+dfsg1/debian/build-efi-images2019-05-04 22:58:32.0
+0100
+++ grub2-2.02+dfsg1/debian/build-efi-images2019-06-14 19:04:01.0
+0100
@@ -20,16 +20,17 @@
# Make EFI boot images for signing.
-if [ $# -lt 5 ]; then
- echo "usage: $0 GRUB-MKIMAGE GRUB-CORE OUTPUT-DIRECTORY PLATFORM
EFI-NAME [EFI-VENDOR]"
+if [ $# -lt 6 ]; then
+ echo "usage: $0 GRUB-MKIMAGE GRUB-CORE OUTPUT-DIRECTORY DEB-ARCH
PLATFORM EFI-NAME [EFI-VENDOR]"
fi
grub_mkimage="$1"
grub_core="$2"
outdir="$3"
-platform="$4"
-efi_name="$5"
-efi_vendor="${6:-$(dpkg-vendor --query vendor | tr '[:upper:]' '[:lower:]')}"
+deb_arch="$4"
+platform="$5"
+efi_name="$6"
+efi_vendor="${7:-$(dpkg-vendor --query vendor | tr '[:upper:]' '[:lower:]')}"
# mkfs.msdos may not be on the default PATH.
export PATH="$PATH:/sbin:/usr/sbin"
@@ -115,6 +116,7 @@
memdisk
minicmd
normal
+ ntfs
part_apple
part_msdos
part_gpt
@@ -141,7 +143,9 @@
case $platform in
x86_64-efi|i386-efi)
CD_MODULES="$CD_MODULES
+ cpuid
linuxefi
+ play
"
;;
esac
@@ -181,15 +185,29 @@
tftp
"
+# CD boot image
"$grub_mkimage" -O "$platform" -o "$outdir/gcd$efi_name.efi" \
-d "$grub_core" \
-c "$workdir/grub-bootstrap.cfg" -m "$workdir/memdisk.fat" \
-p /boot/grub \
$CD_MODULES
+
+# Normal disk boot image
"$grub_mkimage" -O "$platform" -o "$outdir/grub$efi_name.efi" \
-d "$grub_core" -p "/EFI/$efi_vendor" $GRUB_MODULES
+
+# Normal network boot image
"$grub_mkimage" -O "$platform" -o "$outdir/grubnet$efi_name.efi" \
-d "$grub_core" -c "$workdir/grub-bootstrap.cfg" \
- -m "$workdir/memdisk-netboot.fat" -p /grub $NET_MODULES
+ -m "$workdir/memdisk-netboot.fat" \
+ -p /grub $NET_MODULES
+
+# Special network boot image for d-i to use. Just the same as the
+# normal network boot image, but with a different value baked in for
+# the prefix setting
+"$grub_mkimage" -O "$platform" -o "$outdir/grubnet$efi_name-installer.efi" \
+ -d "$grub_core" -c "$workdir/grub-bootstrap.cfg" \
+ -m "$workdir/memdisk-netboot.fat" \
+ -p "${efi_vendor}-installer/$deb_arch/grub" $NET_MODULES
exit 0
diff -Nru grub2-2.02+dfsg1/debian/changelog grub2-2.02+dfsg1/debian/changelog
--- grub2-2.02+dfsg1/debian/changelog 2019-05-04 22:58:32.0 +0100
+++ grub2-2.02+dfsg1/debian/changelog 2019-06-14 19:04:01.0 +0100
@@ -1,3 +1,18 @@
+grub2 (2.02+dfsg1-19) unstable; urgency=medium
+
+ [ Colin Watson ]
+ * Fix format of debian/copyright.
+
+ [ Steve McIntyre ]
+ * Add the ntfs module to signed UEFI images. Closes: #923855
+ * Add the cpuid module to signed UEFI images. Closes: #928628
+ * Add the play module to signed UEFI images. Closes: #930290
+ * Add an extra di-specific version of the UEFI netboot image with a
+different baked-in prefix value. Helps to fix #928750.
+ * Deal with --force-extra-removable with signed shim too. Closes: #930531
+
+ -- Colin Watson Fri, 14 Jun 2019 19:04:01 +0100
+
grub2 (2.02+dfsg1-18) unstable; urgency=medium
* Apply patches from Alexander Graf to fix grub-efi-arm crash (closes:
diff -Nru grub2-2.02+dfsg1/debian/copyright grub2-2.02+dfsg1/debian/copyright
--- grub2-2.02+dfsg1/debian/copyright 2019-05-04 22:58:32.0 +0100
+++ grub2-2.02+dfsg1/debian/copyright 2019-06-14 19:04:01.0 +0100
@@ -1,4 +1,5 @@
-Name: GNU GRUB
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: GNU GRUB
Source: https://www.gnu.org/software/grub/
Files-Excluded: grub-core/lib/libgcrypt*/cipher/crc.c
diff -Nru grub2-2.02+dfsg1/debian/patches/grub-install-removable-shim.patch
grub2-2.02+dfsg1/debian/patches/grub-install-removable-shim.patch
--- grub2-2.02+dfsg1/debian/patches/grub-install-removable-shim.patch
1970-01-01 01:00:00.0 +0100
+++
Bug#929318: [pcp] Bug#929318: unblock: papi/5.7.0+dfsg-1
Hi Paul, Andreas, Apologies for the slow response - I'm in meetings all week this week and I'm a bit behind as a result. On Thu, Jun 20, 2019 at 9:17 AM Andreas Beckmann wrote: > > On 18/06/2019 23.05, Paul Gevers wrote: > > pcp was completely off my radar since it has (silently) dropped all papi > dependencies in unstable. The PAPI metrics in PCP have been transitioned to using perfevent - one of the several reasons for this was to help resolve this Debian bug. The best outcome for Debian PCP user base here would be to use the bugfix PCP update that has been in unstable for several weeks now - this provides a clean upgrade path for pmdapapi users, and removes the PCP dependency on PAPI completely. > I'll do a 0-day NMU of pcp on Thursday (36 hours from now) unless we > heard from Nathan till then. If we cannot use the tested, stable, upstream bugfix update provided earlier due to the release constraints, please go ahead and NMU as needed Andreas - thanks. > Just thinking ... lazy removal of libpapi5 from testing does not work, > since libpapi5.7 breaks it, and pcp-dev probably depends transitively on FWIW, the PCP development packages do not depend on any PAPI (and never have) - it is only older versions of the 'pcp' package itself, which contain the pmdapapi binary - now retired to help resolve this issue. cheers. -- Nathan
Bug#930756: unblock: movit/1.6.2-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package movit
It contains a single, focused fix for a severity=important bug that I found,
backported from upstream git.
It's a bit unclear to me whether “corrupted display” would count as appropriate
for buster unblocks, but I thought it might go under the “crashes etc.” heading
(it's technically undefined behavior with a thread race, but I don't think
there are any real GL drivers where this actually causes _crashes_ per se).
If not, please let me know.
From the upstream commit message; especially the part about ABI stability at
the end should be relevant:
Fix an issue where temporary textures could be reused too early by a
different thread.
When an EffectChain is done rendering (ie., has submitted all of the GL
rendering commands that it needs to), it releases all of the temporary
textures it's used back to a common freelist.
However, if another thread needs a texture of the same size and format,
it could be picking it off of the freelist before the GPU has actually
completed rendering the first thread's command list, and start uploading
into it. This is undefined behavior in OpenGL, and can create garbled
output depending on timing and driver. (I've seen this on at least the
classic Intel Mesa driver.)
Fix by setting fences, so that getting a texture from the freelist
will have an explicit ordering versus the previous work. This increases the
size of ResourcePool::TextureFormat, but it is only ever used in a private
std::map. std::map is node-based (it has to, since the C++ standard requires
iterators to it to be stable), and thus, sizeof(TextureFormat) does not
factor
into sizeof(ResourcePool), and thus, there is no ABI break. Verified by
checking on libstdc++.
diff -Nru movit-1.6.2/debian/changelog movit-1.6.2/debian/changelog
--- movit-1.6.2/debian/changelog2018-03-18 16:25:30.0 +0100
+++ movit-1.6.2/debian/changelog2019-06-15 20:08:45.0 +0200
@@ -1,3 +1,11 @@
+movit (1.6.2-2) unstable; urgency=high
+
+ * fix-temporary-texture-race-issue.diff: New patch backported from upstream
+git, fixes a threading issue where a thread could start reusing a temporary
+texture while it's still being used in rendering. (Closes: #930570)
+
+ -- Steinar H. Gunderson Sat, 15 Jun 2019 20:08:45 +0200
+
movit (1.6.2-1) unstable; urgency=medium
* New upstream release.
diff -Nru movit-1.6.2/debian/patches/fix-temporary-texture-race-issue.diff
movit-1.6.2/debian/patches/fix-temporary-texture-race-issue.diff
--- movit-1.6.2/debian/patches/fix-temporary-texture-race-issue.diff
1970-01-01 01:00:00.0 +0100
+++ movit-1.6.2/debian/patches/fix-temporary-texture-race-issue.diff
2019-06-15 20:08:37.0 +0200
@@ -0,0 +1,50 @@
+Index: movit-1.6.2/resource_pool.cpp
+===
+--- movit-1.6.2.orig/resource_pool.cpp
movit-1.6.2/resource_pool.cpp
+@@ -42,6 +42,7 @@ ResourcePool::~ResourcePool()
+ for (GLuint free_texture_num : texture_freelist) {
+ assert(texture_formats.count(free_texture_num) != 0);
+ texture_freelist_bytes -=
estimate_texture_size(texture_formats[free_texture_num]);
++ glDeleteSync(texture_formats[free_texture_num].no_reuse_before);
+ texture_formats.erase(free_texture_num);
+ glDeleteTextures(1, _texture_num);
+ check_error();
+@@ -337,7 +338,10 @@ GLuint ResourcePool::create_2d_texture(G
+ format_it->second.height == height) {
+ texture_freelist_bytes -=
estimate_texture_size(format_it->second);
+ texture_freelist.erase(freelist_it);
++ GLsync sync = format_it->second.no_reuse_before;
+ pthread_mutex_unlock();
++ glWaitSync(sync, 0, GL_TIMEOUT_IGNORED);
++ glDeleteSync(sync);
+ return texture_num;
+ }
+ }
+@@ -449,12 +453,14 @@ void ResourcePool::release_2d_texture(GL
+ texture_freelist.push_front(texture_num);
+ assert(texture_formats.count(texture_num) != 0);
+ texture_freelist_bytes +=
estimate_texture_size(texture_formats[texture_num]);
++ texture_formats[texture_num].no_reuse_before =
glFenceSync(GL_SYNC_GPU_COMMANDS_COMPLETE, 0);
+
+ while (texture_freelist_bytes > texture_freelist_max_bytes) {
+ GLuint free_texture_num = texture_freelist.back();
+ texture_freelist.pop_back();
+ assert(texture_formats.count(free_texture_num) != 0);
+ texture_freelist_bytes -=
estimate_texture_size(texture_formats[free_texture_num]);
++ glDeleteSync(texture_formats[free_texture_num].no_reuse_before);
+
Re: Re: Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop
If you would like some feedback from an user, I think that Wayland should be the default now. Yes, GNOME still does crash, yes there is no viable screen-sharing, etc. But, the user still has a choice on the login screen, and this is already well documented on Buster's release notes page. Wayland has to become default because it need wider user-base. Remember that Debian developers can fix any critical bugs via future Buster point releases. Leave the choice to the user, and stick to upstream's defaults. Anyone who installs GNOME on Debian should know about Wayland and be informed about it's limitations. So, let's try to fix those limitations. Sincerely, a Debian GNOME user
Bug#928882: unblock: [pre-approval] ghc/8.4.4+dfsg1-3
On Wed, Jun 19, 2019 at 11:33 PM Ilias Tsitsimpis wrote: > > On Mon, Jun 17, 2019 at 12:00AM, Emanuele Olivetti wrote: > > Let me know if I can help more. > > Dear Emanuele, > > Thank you for taking the time to test and verify my packages. Can I ping > you one last time to test that git-annex will work after we rebuild it? > > > Dear Ilias, Indeed, I'll be very happy to test git-annex! Looking forward to receiving your message. And thanks again for taking care of this issue. Best, Emanuele
Re: Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop
Hey there, Le 19/06/2019 à 22:19, Simon McVittie a écrit : - Ubuntu GNOME team: which recent Ubuntu versions, if any, are using Wayland for their GNOME-based desktop? We don't have any supported Ubuntu version using Wayland by default, our motivations for sticking to Xorg were mostly desktop sharing/rdp support and the fact that under wayland a gnome-shell segfault takes the whole session down without giving user a chance to save their work. While screen sharing is being actively being worked on, our metrics show that gnome-shell errors are still quite common, even in recent versions so it's not likely that we change our default for the next LTS. Cheers, Sebastien Bacher
Bug#928185: unblock: openjdk-11/11.0.3+7-4
On 19.06.19 22:03, Paul Gevers wrote: > Hi Tony, > > On 18-06-2019 22:14, tony mancill wrote: >> Things are looking good so far with 11.0.4+4+really11.0.3+7 in unstable, >> and so I would like to prepare the t-p-u upload. At the moment, the >> version I have is 11.0.3+7-5, since that would have been the "next" >> 11.0.3+7 Debian revision for unstable. The 11.0.3+7 orig.tar.xz already >> in the archive is the same one used for the "really" to unstable and >> this build, and this versioning makes it clear to users what they are >> getting. The resulting changelog would be: >> >>> diff -Nru openjdk-11-11.0.4+4+really11.0.3+7/debian/changelog >>> openjdk-11-11.0.3+7/debian/changelog >>> --- openjdk-11-11.0.4+4+really11.0.3+7/debian/changelog 2019-06-14 >>> 12:28:25.0 -0700 >>> +++ openjdk-11-11.0.3+7/debian/changelog2019-06-16 11:24:19.0 >>> -0700 >>> @@ -1,3 +1,10 @@ >>> +openjdk-11 (11.0.3+7-5) buster; urgency=medium >>> + >>> + * Team upload. >>> + * Upload 11.0.4+4+realy11.0.3+7-2 to buster t-p-u. >>> + >>> + -- tony mancill Sun, 16 Jun 2019 11:24:19 -0700 >> >> Is this acceptable to the Release Team? If not, (and I know there have >> been some differing opinions), how shall we version the t-p-u package? > > I think the most logical version would be 11.0.3+7-4+deb10u1, as this is > a targeted upload to buster. let's use a version which also can be nicely used for the backports upload. > I don't have a strong opinion on it. I > still don't like it we go via tpu but I understand the ranting argument. this will be very short-lived until the final 11.0.4 release to be uploaded into security. > Let's end this saga. please do.
Re: Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop
On Wed, 19 Jun 2019 at 17:33:55 +0100, Jonathan Dowland wrote: > So far as I am aware there is still radio silence from active GNOME > packaging team members regarding this issue. No comment yet on the > patch I adapted, positive or negative; this bug (#927667) remains > at an RC severity. (Adding debian-gtk-gnome, debian-desktop and some people who might have useful input to Cc) In case anyone else in the GNOME team has got the wrong idea from my involvement in #927667: I don't think I am the right person to make a decision on this. So if GNOME team members are waiting for me to either make an upload changing the default back to X11, or veto such an upload: don't wait for that, it is unlikely to happen (unless the team cannot make a decision and punts this to the technical committee, but I hope we don't have to resort to that). I would very much appreciate input from the rest of the team, particularly: - Laurent: I know you've had strong opinions about using Wayland for GNOME. Do you feel strongly that Debian should be defaulting to Wayland? Are there any reasons for that default that are missing from my attempt to summarize earlier on the bug? - Ubuntu GNOME team: which recent Ubuntu versions, if any, are using Wayland for their GNOME-based desktop? I've left some comments on https://salsa.debian.org/gnome-team/gdm/merge_requests/8 regarding the technical side of the proposed change. Thanks, smcv
Re: Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop
Jonathan Dowland writes: > So far as I am aware there is still radio silence from active GNOME > packaging team members regarding this issue. No comment yet on the > patch I adapted, positive or negative; this bug (#927667) remains > at an RC severity. > > I've not yet read all the thread that Samuel linked to[1] but it looks > like it leans in favour of preserving the current default (xorg). > > I'm copying -release team to see if they have any (new) opinions on > the matter. Otherwise I guess it's up to someone to prepare an NMU > upload, which I will *try* to look at in the next few days, but can't > make any guarantees. I'm just a GNOME user, but from gdm3's changelog the default was switched to Wayland in July 2017 (or August 2017 for unstable). I myself only noticed the switch after reading it happened somewhere on the internet shortly after it happened. Switching the default back two weeks before the release seems too late for me. The largest issue seems to be accessibility, but as far as I understand we already recommend a different desktop environment for that. I don't think that warrants changes that would only see very little testing by now :-/ Ansgar
Bug#930749: unblock: samba/2:4.9.9+dfsg-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, This is a pre-approval request about samba. A new Samba security version was released today to address CVE-2019-12435: 4.9.9. Sid/buster currently has 4.9.5. I'm tempted to upload 4.9.9 to sid (targeting buster). This would add a big diff of stability fixes. The d/changelog would look like: samba (2:4.9.9+dfsg-1) unstable; urgency=high * This is a security release in order to address the following defect: - CVE-2019-12435 zone operations can crash rpc server (Closes: #930748) * New upstream release - Remove security patches, included in release - libsamba-passdb.so bumped to 0.27.2 * Add missing Breaks+Replace found by piuparts (Closes: #929217) Thanks Andreas Beckmann! Without an ack from you, I will only add the patch for CVE-2019-12435 (and maybe #929217?) and delay the other fixes for buster-proposed-updates. What is you opinion? (not including the debdiff against the package in testing, which is huge) unblock samba/2:4.9.9+dfsg-1 -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#928185: unblock: openjdk-11/11.0.3+7-4
Hi Tony, On 18-06-2019 22:14, tony mancill wrote: > Things are looking good so far with 11.0.4+4+really11.0.3+7 in unstable, > and so I would like to prepare the t-p-u upload. At the moment, the > version I have is 11.0.3+7-5, since that would have been the "next" > 11.0.3+7 Debian revision for unstable. The 11.0.3+7 orig.tar.xz already > in the archive is the same one used for the "really" to unstable and > this build, and this versioning makes it clear to users what they are > getting. The resulting changelog would be: > >> diff -Nru openjdk-11-11.0.4+4+really11.0.3+7/debian/changelog >> openjdk-11-11.0.3+7/debian/changelog >> --- openjdk-11-11.0.4+4+really11.0.3+7/debian/changelog 2019-06-14 >> 12:28:25.0 -0700 >> +++ openjdk-11-11.0.3+7/debian/changelog 2019-06-16 11:24:19.0 >> -0700 >> @@ -1,3 +1,10 @@ >> +openjdk-11 (11.0.3+7-5) buster; urgency=medium >> + >> + * Team upload. >> + * Upload 11.0.4+4+realy11.0.3+7-2 to buster t-p-u. >> + >> + -- tony mancill Sun, 16 Jun 2019 11:24:19 -0700 > > Is this acceptable to the Release Team? If not, (and I know there have > been some differing opinions), how shall we version the t-p-u package? I think the most logical version would be 11.0.3+7-4+deb10u1, as this is a targeted upload to buster. I don't have a strong opinion on it. I still don't like it we go via tpu but I understand the ranting argument. Let's end this saga. Paul signature.asc Description: OpenPGP digital signature
Processed: closing 930713
Processing commands for cont...@bugs.debian.org: > close 930713 Bug #930713 [release.debian.org] unblock: php-horde-form/2.0.18-3.1 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 930713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop
Hi Andrew So far as I am aware there is still radio silence from active GNOME packaging team members regarding this issue. No comment yet on the patch I adapted, positive or negative; this bug (#927667) remains at an RC severity. I've not yet read all the thread that Samuel linked to[1] but it looks like it leans in favour of preserving the current default (xorg). I'm copying -release team to see if they have any (new) opinions on the matter. Otherwise I guess it's up to someone to prepare an NMU upload, which I will *try* to look at in the next few days, but can't make any guarantees. Further testers of the patch on this bug would be most welcome. [1] https://lists.debian.org/debian-accessibility/2019/02/threads.html#4
Bug#930741: unblock: debian-electronics/0.3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package debian-electronics As in every release process I have updated several Blends metapackages which needed updates due to package removals to reflect the package pool of the release. These metapackages are created using the latest blends-dev package. The changes in the debian-electronics package are to a large extend auto generated by blends-dev and the full debdiff (attached debian-electronics_0.2-0.3.diff.gz) is a bit hard to read because the files in tasks/ are serving at the same time used as documentation for the Debian Med web sentinel. There is no reasonable way to maintain this in a separate source so the diff is larger than you would usually accept these days. This was done in the same way for several previous releases. To enable you concentrating on the *relevant* changes which are caused due to changes in the package pool I added wdiff debian-electronics-0.2/debian/control debian-electronics-0.3/debian/control > debian-electronics_control_0.2-0.3.wdiff which is more easy to inspect to see what relevant changes in the dependencies have actually happended (see debian-electronics_control_0.2-0.3.wdiff.gz). Kind regards Andreas. unblock debian-electronics/0.3 -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) debian-electronics_0.2-0.3.diff.gz Description: application/gzip debian-electronics_control_0.2-0.3.wdiff.gz Description: application/gzip
Bug#930740: unblock: debian-junior/1.29
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package debian-junior As in every release process I have updated several Blends metapackages which needed updates due to package removals to reflect the package pool of the release. These metapackages are created using the latest blends-dev package. The changes in the debian-junior package are to a large extend auto generated by blends-dev and the full debdiff (attached debian-junior_1.28-1.29.diff.gz) is a bit hard to read because the files in tasks/ are serving at the same time used as documentation for the Debian Med web sentinel. There is no reasonable way to maintain this in a separate source so the diff is larger than you would usually accept these days. This was done in the same way for several previous releases. To enable you concentrating on the *relevant* changes which are caused due to changes in the package pool I added wdiff debian-junior-1.28/debian/control debian-junior-1.29/debian/control > debian-junior_control_1.28-1.29.wdiff which is more easy to inspect to see what relevant changes in the dependencies have actually happended (see debian-junior_control_1.28-1.29.wdiff.gz). Kind regards Andreas. unblock debian-junior/1.29 -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) debian-junior_1.28-1.29.diff.gz Description: application/gzip debian-junior_control_1.28-1.29.wdiff.gz Description: application/gzip
Bug#930739: unblock: debichem/0.0.8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package debichem As in every release process I have updated several Blends metapackages which needed updates due to package removals to reflect the package pool of the release. These metapackages are created using the latest blends-dev package. The changes in the debichem package are to a large extend auto generated by blends-dev and the full debdiff (attached debichem_0.0.7-0.0.8.diff.gz) is a bit hard to read because the files in tasks/ are serving at the same time used as documentation for the Debian Med web sentinel. There is no reasonable way to maintain this in a separate source so the diff is larger than you would usually accept these days. This was done in the same way for several previous releases. To enable you concentrating on the *relevant* changes which are caused due to changes in the package pool I added wdiff debichem-0.0.7/debian/control debichem-0.0.8/debian/control > debichem_control_0.0.7-0.0.8.wdiff which is more easy to inspect to see what relevant changes in the dependencies have actually happended (see debichem_control_0.0.7-0.0.8.wdiff.gz). Kind regards Andreas. unblock debichem/0.0.8 -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#930738: unblock: debian-science/1.10
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package debian-science As in every release process I have updated several Blends metapackages which needed updates due to package removals to reflect the package pool of the release. These metapackages are created using the latest blends-dev package. The changes in the debian-science package are to a large extend auto generated by blends-dev and the full debdiff (attached debian-science_1.9-1.10.diff.gz) is a bit hard to read because the files in tasks/ are serving at the same time used as documentation for the Debian Med web sentinel. There is no reasonable way to maintain this in a separate source so the diff is larger than you would usually accept these days. This was done in the same way for several previous releases. To enable you concentrating on the *relevant* changes which are caused due to changes in the package pool I added wdiff debian-science-1.9/debian/control debian-science-1.10/debian/control > debian-science_control_1.9-1.10.wdiff which is more easy to inspect to see what relevant changes in the dependencies have actually happended (see debian-science_control_1.9-1.10.wdiff.gz). Kind regards Andreas. unblock debian-science/1.10 -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) debian-science_1.9-1.10.diff.gz Description: application/gzip debian-science_control_1.9-1.10.wdiff.gz Description: application/gzip
Bug#930670: unblock: rabbitmq-server/3.7.8-5
On 6/19/19 6:47 AM, Paul Gevers wrote: > Hi Thomas, > > On 18-06-2019 09:42, Thomas Goirand wrote: >> This last Debian release adds the packaging of rabbitmq-diagnostic in >> /usr/sbin, which is a very useful tool. It'd be a diss-service to our >> users to not have it in Buster, and I don't think this is controvertial >> at all. Not counting the removal of debian/gbp.conf (which we don't use >> anymore), the attached debdiff is a one-liner. >> >> unblock rabbitmq-server/3.7.8-5 > > Sorry, too late. We want to release in two weeks and adding new features > is a station long past. > > I spent quite some time thinking about it as this particular change > seems acceptable as an exception, however I fear the precedent will make > our future work more difficult as it will invite more request that don't > qualify and need careful analysis. People are reading these reports. > > Paul > I do understand it's not a nice timing for such an update, even if it's very minimal. Maybe it will be accepted as a buster-proposed-update for the first point release, then? FYI, monitoring of RabbitMQ is a mission-critical thing, and I just missed this new binary from upstream which simplifies A LOT the monitoring of RabbitMQ, which is the source of 99% of the troubles on an OpenStack cluster. I really want to bring this to Buster users. Cheers, Thomas Goirand (zigo)
Bug#930732: unblock: debian-med/3.3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package debian-med As in every release process I have updated several Blends metapackages which needed updates due to package removals to reflect the package pool of the release. These metapackages are created using the latest blends-dev package. The changes in the debian-med package are to a large extend auto generated by blends-dev and the full debdiff (attached debian-med_3.2_3.3.diff.gz) is a bit hard to read because the files in tasks/ are serving at the same time used as documentation for the Debian Med web sentinel. There is no reasonable way to maintain this in a separate source so the diff is larger than you would usually accept these days. This was done in the same way for several previous releases. To enable you concentrating on the *relevant* changes which are caused due to changes in the package pool I added wdiff debian-med-3.2/debian/control debian-med-3.3/debian/control > control_3.2_3.3.wdiff which is more easy to inspect to see what relevant changes in the dependencies have actually happended (see debian-med_control_3.2_3.3.wdiff.gz). Kind regards Andreas. unblock debian-med/3.3 -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) debian-med_3.2_3.3.diff.gz Description: application/gzip debian-med_control_3.2_3.3.wdiff.gz Description: application/gzip
Bug#930727: unblock: gatb-core/1.4.1+git20181225.44d5a44+dfsg-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gatb-core diff -Nru gatb-core-1.4.1+git20181225.44d5a44+dfsg/debian/changelog gatb-core-1.4.1+git20181225.44d5a44+dfsg/debian/changelog --- gatb-core-1.4.1+git20181225.44d5a44+dfsg/debian/changelog 2019-03-18 09:45:17.0 +0100 +++ gatb-core-1.4.1+git20181225.44d5a44+dfsg/debian/changelog 2019-06-19 12:25:30.0 +0200 @@ -1,3 +1,10 @@ +gatb-core (1.4.1+git20181225.44d5a44+dfsg-3) unstable; urgency=medium + + * Fix symbols +Closes: #930368 + + -- Andreas Tille Wed, 19 Jun 2019 12:25:30 +0200 + gatb-core (1.4.1+git20181225.44d5a44+dfsg-2) unstable; urgency=medium * Rebuild for new version of gcc to fix symbols diff -Nru gatb-core-1.4.1+git20181225.44d5a44+dfsg/debian/libgatbcore2.symbols.amd64 gatb-core-1.4.1+git20181225.44d5a44+dfsg/debian/libgatbcore2.symbols.amd64 --- gatb-core-1.4.1+git20181225.44d5a44+dfsg/debian/libgatbcore2.symbols.amd64 2019-03-18 09:45:17.0 +0100 +++ gatb-core-1.4.1+git20181225.44d5a44+dfsg/debian/libgatbcore2.symbols.amd64 2019-06-19 12:25:30.0 +0200 @@ -8997,7 +8997,6 @@ _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi1EEEjjjEESaIS7_EE12emplace_backIJS7_EEEvDpOT_@Base 1.4.1+git20181225.44d5a44+dfsg _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi1EEEjjjEESaIS7_EE17_M_realloc_insertIJS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base 1.4.1 _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi1EEEjjjEESaIS7_EE7reserveEm@Base 1.4.1 - _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi2EEEjjjEESaIS7_EE12emplace_backIJS7_EEEvDpOT_@Base 1.4.1+git20181225.44d5a44+dfsg _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi2EEEjjjEESaIS7_EE17_M_realloc_insertIJS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base 1.4.1 _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi2EEEjjjEESaIS7_EE7reserveEm@Base 1.4.1 _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi3EEEjjjEESaIS7_EE17_M_realloc_insertIJS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base 1.4.1 @@ -9007,7 +9006,6 @@ _ZNSt6vectorISt5tupleIJmiEESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base 1.4.1 _ZNSt6vectorISt5tupleIJmiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaIS7_EE17_M_realloc_insertIJS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base 1.4.1 _ZNSt6vectorISt6threadSaIS0_EE17_M_realloc_insertIJZN10ThreadPoolC4EmEUlvE_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base 1.4.1 - _ZNSt6vectorIbSaIbEE13_M_initializeEm@Base 1.4.1+git20181225.44d5a44+dfsg _ZNSt6vectorIbSaIbEE13_M_insert_auxESt13_Bit_iteratorb@Base 1.4.1 _ZNSt6vectorIbSaIbEE13_M_reallocateEm@Base 1.4.1 _ZNSt6vectorIbSaIbEE14_M_fill_insertESt13_Bit_iteratormb@Base 1.4.1 unblock gatb-core/1.4.1+git20181225.44d5a44+dfsg-3 -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#928227: unblock: golang-golang-x-net-dev/1:0.0+git20181201.351d144+dfsg-3
On 2019-06-19 01:01, Paul Gevers wrote: Hi Drew, On 18-06-2019 16:22, Drew Parsons wrote: Just want to say, thanks Shengjing, Tobias and Paul for working through the issues to get golang ready for buster. Thank you for the thanks, but to be fair, it isn't finished. The golang-golang-x-net-dev update isn't available in coyim, rkt and singularity-container yet. Hence, this bug isn't closed yet. I had a closer look at coyim. It's been substantially overhauled upstream in v0.3.11, with a path change from github.com/twstrike/coyim/ to github.com/coyim/coyim/. I started testing the new version aiming to see if it will build on arm64 (in experimental). But it requires a suite of dependencies to also be updated (from twstrike to coyim) so it wasn't practical for me to push it further. Drew
Bug#930397: [pre-approval] unblock: nano/3.2-3
Hi, El dt. 18 de 06 de 2019 a les 21:56 +0200, en/na Paul Gevers va escriure: > Control: tags -1 moreinfo > > Hi Jordi, > > On 12-06-2019 03:52, Jordi Mallach wrote: > > Hi release team, > > > > Nano's upstream has been focusing on fixing some crashers and hangs > > lately, > > and as nano froze a while back, he was kind enough to backport all > > the fixes > > he deems interesting for the buster release. > > > > The following debdiff adds 7 patches (and renames the already > > existing one). > > > > All patches are simple, some of them one liners. > > > > If you can signal if this is OK for an upload now, I'll act > > accordingly ASAP. > > Please go ahead, taking into account that the package needs to be > ready > to migrate at 2019-06-25 13:00 UTC [1]. Thanks, I've uploaded nano -3 now, I assume it'll be ready for one of the last migrations. Jordi -- Jordi Mallach Pérez -- Debian developer https://www.debian.org/ jo...@sindominio.netjo...@debian.org https://www.sindominio.net/ GnuPG public key information available at https://oskuro.net/ signature.asc Description: This is a digitally signed message part
Bug#930717: unblock: pysynphot/0.9.12+dfsg-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: 930...@bugs.debian.org
Dear release team,
please unblock dpuser .It solves #930056 "synphot-data: creates world
writable files:
/usr/share/synphot/grp/hst/cdbs/comp/acs/acs_*_syn.fits", severity:
serious. Changelog entry:
pysynphot (0.9.12+dfsg-3) unstable; urgency=medium
* Remove synphot-data package (Closes: #930056, LP: #1775965)
-- Ole Streicher Sat, 08 Jun 2019 20:51:21 +0200
The debdiff is attached. Requested commands:
unblock pysynphot/0.9.12+dfsg-3
Best regards
Ole
diff -Nru pysynphot-0.9.12+dfsg/debian/changelog
pysynphot-0.9.12+dfsg/debian/changelog
--- pysynphot-0.9.12+dfsg/debian/changelog 2018-12-11 09:11:51.0
+0100
+++ pysynphot-0.9.12+dfsg/debian/changelog 2019-06-08 20:51:21.0
+0200
@@ -1,3 +1,9 @@
+pysynphot (0.9.12+dfsg-3) unstable; urgency=medium
+
+ * Remove synphot-data package (Closes: #930056, LP: #1775965)
+
+ -- Ole Streicher Sat, 08 Jun 2019 20:51:21 +0200
+
pysynphot (0.9.12+dfsg-2) unstable; urgency=low
* Remove Python 2 package
diff -Nru pysynphot-0.9.12+dfsg/debian/control
pysynphot-0.9.12+dfsg/debian/control
--- pysynphot-0.9.12+dfsg/debian/control2018-12-11 09:09:34.0
+0100
+++ pysynphot-0.9.12+dfsg/debian/control2019-06-08 20:50:43.0
+0200
@@ -19,7 +19,6 @@
Package: python3-pysynphot
Architecture: any
Depends: ${misc:Depends}, ${python3:Depends}, ${shlibs:Depends}
-Suggests: synphot-data
Description: Python Synthetic Photometry Utilities
pysynphot simulates photometric data and spectra as they are observed with
the Hubble Space Telescope (HST). Passbands for standard photometric systems
@@ -42,23 +41,3 @@
the control and data structures available in Python to easily perform
repetitive operations such as simulate the observation of multiple type of
sources through multiple observing modes.
-
-Package: synphot-data
-Section: contrib/science
-Architecture: all
-Depends: curl, ${misc:Depends}
-Description: Optional data files for pysynphot
- pysynphot simulates photometric data and spectra as they are observed with
- the Hubble Space Telescope (HST).
- .
- This package downloads the data files for synphot and pysynphot:
- .
- * HST component throughput files and graph and component lookup tables,
- * Stellar and galactic model files,
- * the Castelli and Kurucz 2004 Atlas,
- * the Kurucz 1993 Atlas,
- * the Phoenix Models, and
- * the HST Calibration Spectra.
- .
- Note that installing this package will cause downloading more than 600 MB of
- data from archive.stsci.edu.
diff -Nru pysynphot-0.9.12+dfsg/debian/synphot-data.lintian-overrides
pysynphot-0.9.12+dfsg/debian/synphot-data.lintian-overrides
--- pysynphot-0.9.12+dfsg/debian/synphot-data.lintian-overrides 2017-02-27
15:40:36.0 +0100
+++ pysynphot-0.9.12+dfsg/debian/synphot-data.lintian-overrides 1970-01-01
01:00:00.0 +0100
@@ -1,2 +0,0 @@
-# This is a downloader package and therefor empty by design
-empty-binary-package
diff -Nru pysynphot-0.9.12+dfsg/debian/synphot-data.postinst
pysynphot-0.9.12+dfsg/debian/synphot-data.postinst
--- pysynphot-0.9.12+dfsg/debian/synphot-data.postinst 2017-02-27
15:40:36.0 +0100
+++ pysynphot-0.9.12+dfsg/debian/synphot-data.postinst 1970-01-01
01:00:00.0 +0100
@@ -1,22 +0,0 @@
-#!/bin/sh
-
-set -e
-
-TARGETDIR=/usr/share/synphot
-
-if [ "$1" = "configure" ] ; then
- mkdir -p ${TARGETDIR}
- cd ${TARGETDIR}
- if ! md5sum -c --quiet md5sums.txt ; then
-for i in `seq 1 6` ; do
- curl ftp://ftp.stsci.edu/cdbs/tarfiles/synphot${i}.tar.gz | tar xz
-done
-if [ -d grid/extinction ] ; then
- rm -rf extinction
- mv -f grid/extinction .
-fi
-find calspec comp extinction grid mtab -type f | xargs md5sum > md5sums.txt
- fi
-fi
-
-#DEBHELPER#
diff -Nru pysynphot-0.9.12+dfsg/debian/synphot-data.prerm
pysynphot-0.9.12+dfsg/debian/synphot-data.prerm
--- pysynphot-0.9.12+dfsg/debian/synphot-data.prerm 2017-02-27
15:40:36.0 +0100
+++ pysynphot-0.9.12+dfsg/debian/synphot-data.prerm 1970-01-01
01:00:00.0 +0100
@@ -1,7 +0,0 @@
-#!/bin/sh
-
-set -e
-
-rm -rf /usr/share/synphot
-
-#DEBHELPER#
Bug#930715: release.debian.org: gcc-mingw-w64 Buster upload
Package: release.debian.org Severity: normal Hi, I uploaded an updated gcc-mingw-w64 package to unstable, 21.3, with a fix for #928214. I’ve since been informed (by Paul Gevers, re Mednafen) that gcc-8 8.3.0-7 won’t be migrating, which means gcc-mingw-w64 21.3 won’t either. Could I upload the package as 21.3~deb10u1 to testing-pu? The diff between 21.2 and 21.3 is as follows: diff --git a/debian/changelog b/debian/changelog index a2de56d..dcef4a3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +gcc-mingw-w64 (21.3) unstable; urgency=medium + + * Configure LTO support correctly; thanks Alexey Izbyshev! +Closes: #928214. + + -- Stephen Kitt Tue, 18 Jun 2019 08:59:34 +0200 + gcc-mingw-w64 (21.2) unstable; urgency=medium * Apply upstream dllimport fix for static data members. diff --git a/debian/rules b/debian/rules index 0b55196..e9e4416 100755 --- a/debian/rules +++ b/debian/rules @@ -202,8 +202,7 @@ CONFFLAGS += \ --enable-languages=$(languages) # LTO CONFFLAGS += \ - --enable-lto \ - --with-plugin-ld + --enable-lto # Thread-model-dependent CONFFLAGS += \ --enable-threads=$$threads \ The package is currently building in unstable, with a killed job on i386 for some reason; it also builds fine in testing. I don’t yet have a fix for #923698, the other RC bug against gcc-mingw-w64 — that will have to wait for a point release (assuming the fix is approvable). Regards, Stephen -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-9-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
