Bug#1062783: libxfce4ui FTCBFS: fails running gtk-doc scanner
Hi, On Mon, Feb 05, 2024 at 04:40:38PM +0100, Yves-Alexis Perez wrote: > The patch looks small, and I don't know a lot about cross-building, but would > it be better to use something like: > > ifneq (,$(filter cross,$(DEB_BUILD_PROFILES)) > > inside override_dh_auto_configure to only add gtk-doc when not cross-building? While that might technically work, such cross vs native differences are fragile and in a lot of cases, I've had to fix them, so I strongly prefer to not add cross vs native differences to the build unless necessary. Here, no part of an arch-only build needs gtk-doc. For this, it does not matter whether the build is cross or native. It applies to any arch-only build. In particular, disabling gtk-doc, also speeds up the build. I actually performed an arch-only and a full build to verify that no files go missing by this change using reproducible builds. Is this line of reasoning convincing to you? Helmut
Processed: notfound 1059787 in 4.19.1-1
Processing commands for cont...@bugs.debian.org: > notfound 1059787 4.19.1-1 Bug #1059787 {Done: Paul Gevers } [src:xfce4-power-manager] src:xfce4-power-manager: fails to migrate to testing for too long: uploader built arch:all binaries Ignoring request to alter found versions of bug #1059787 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1059787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1062783: libxfce4ui FTCBFS: fails running gtk-doc scanner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 2024-02-03 at 10:34 +0100, Helmut Grohne wrote: > libxfce4ui fails to cross build from source, because it fails running > the gtk-doc scanner with an Exec format error. This is fairly usual. > Fortunately, it also splits out its documentation to an Arch:all > package. Hence, we can disable gtk-doc in arch-only builds and thus > side-step this problem making the cross build succeed. I'm attaching a > patch for your convenience. Hi Helmut, thanks for the report and the patch. The patch looks small, and I don't know a lot about cross-building, but would it be better to use something like: ifneq (,$(filter cross,$(DEB_BUILD_PROFILES)) inside override_dh_auto_configure to only add gtk-doc when not cross-building? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmXBAXYACgkQ3rYcyPpX RFsBbwgA6yOREFfPDlNddwz6VZIYSF0IfxZ5/A5R5QB3xu+Nxx/ZYDl5XcSxALvQ 32BRjN1+cpubRj4R1h5yJ8RN3ac+ykz0PI7TmPw7zmYodJ0fYP/aCiONJZbIbuP5 4PAR9VLfI0EZ9Du7ArYuhN/bz//MXEO1ruHHl2nEigWzzPJinu3FUWIp42U5vI76 VfYSNz3mH1gFk0rshwMqsOx3Uokb5r1L+egGV7AwL79qJqXabMGolyMwjEzEWC23 +SmyY0NWaPwJBOSDTQ2Ren3lMeRE13FlowwQ0KzclDqEHNcZqlcBalC5d3iKzfLm ng5eQv8ht3WwkwW6vVDPyqc2VE0Wag== =h+YT -END PGP SIGNATURE-
Bug#1062998: tumbler: NMU diff for 64-bit time_t transition
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2024-02-05 at 00:28 -0800, Steve Langasek wrote: > Well, to clarify, the patch I sent was against 4.18 in unstable; but it > applied cleanly to 4.19 in experimental (no new sonames in experimental vs > unstable), so it's been uploaded there. Ah ok. > > When the unstable uploads happen, they will be based on the version that's > current in unstable at the time. Perfect then. Thanks again! Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmXAne4ACgkQ3rYcyPpX RFs90QgA6yqQzb/h/MoSrQIPHxjPi+eU/LdgYfQlwvdXTeCWzoMmke8QHp0f2jQE 00j9LuD2TvnSPzcvBR0ZH7GYScJt+LQabIjmehCC8FmmgB+hrXwNEZussHNVl56i D+JFG5AHXohP2G+c+0LBB0u78Y+c10oweq8INh9/t2ZZO5jp366jiLTbKe1C6jq7 NRwioJa1tNIRlm3sebqJW59VdRdbybG0Q5WRZEYXg/+EmS34MZykZYyOhjpOBJ/E HzWyA48Itc0uj4juX8j/9nYu4mDPpFMUCQgNA4eY5V4b2HuNxN5j/T66YpsSw9nM XCImXWgkiGn+UMeFrqqSoX1EmatArQ== =Apdm -END PGP SIGNATURE-
Bug#1062998: tumbler: NMU diff for 64-bit time_t transition
Hi there, On Mon, Feb 05, 2024 at 09:24:43AM +0100, Yves-Alexis Perez wrote: > On Sun, 2024-02-04 at 11:14 +, Steve Langasek wrote: > > If you have any concerns about this patch, please reach out ASAP. Although > > this package will be uploaded to experimental immediately, there will be a > > period of several days before we begin uploads to unstable; so if > > information > > becomes available that your package should not be included in the > > transition, > > there is time for us to amend the planned uploads. > Hi Steve, > thanks for the work on the time_t migration, and thanks for the diff. I'll > import it to our repository, but one thing worth noting is that the diff is > for the 4.19 in experimental, which will be part of Xfce 4.20 in the future. > We don't intend to upload 4.19 to unstable at all, so tumbler will stay at > 4.18 (4.18.1-1+b1 precisely) for now. > We surely hope that 4.20 will be released before any freeze happens, but if > you need a coordinated upload to unstable it'll need to happen on 4.18. > I guess we can “backport” your changes to 4.18 and upload to unstable once the > go is given? Well, to clarify, the patch I sent was against 4.18 in unstable; but it applied cleanly to 4.19 in experimental (no new sonames in experimental vs unstable), so it's been uploaded there. When the unstable uploads happen, they will be based on the version that's current in unstable at the time. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#1062998: tumbler: NMU diff for 64-bit time_t transition
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2024-02-04 at 11:14 +, Steve Langasek wrote: > > If you have any concerns about this patch, please reach out ASAP. Although > this package will be uploaded to experimental immediately, there will be a > period of several days before we begin uploads to unstable; so if information > becomes available that your package should not be included in the transition, > there is time for us to amend the planned uploads. Hi Steve, thanks for the work on the time_t migration, and thanks for the diff. I'll import it to our repository, but one thing worth noting is that the diff is for the 4.19 in experimental, which will be part of Xfce 4.20 in the future. We don't intend to upload 4.19 to unstable at all, so tumbler will stay at 4.18 (4.18.1-1+b1 precisely) for now. We surely hope that 4.20 will be released before any freeze happens, but if you need a coordinated upload to unstable it'll need to happen on 4.18. I guess we can “backport” your changes to 4.18 and upload to unstable once the go is given? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmXAm0sACgkQ3rYcyPpX RFtKcwgAtoccvc0XqV4QhpEJdoSvXE9v4hpAlDI2h0eA9fkwr0eWJFNullmSKHZZ iQeNSU3EVwcrG0vDJD6LadB2NQqyEYne4m/UmFqGvn3194aTBo2+0f+pIA0GV/2q wW6Vjj9ObMSJGIeSRGmaiyttofsqlLM/ElbosJf8pQvxmdwpKbAm9ocqAPc4tDGo Zp0gZnCNYsEGgjF3nG/t/PyFIwh5QBfyJhUD3/yw62vp8kFVX9/77UWWjUgpUpA5 QSGR4MQDPAiEK0JVhVlkedl+Bf8G7Qh+gLUTdAJSsMMD8BKuX+xcFASISHpEW0t4 iackjFr5lq9XZ+hZOVIGXDVCETZO9g== =+nIU -END PGP SIGNATURE-