Bug#1010140: aqsis: FTBFS on arm{el,hf}
Package: aqsis Version: 1.8.2+git20210815 Followup-For: Bug #1010140 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Control: tags -1 patch Dear Maintainer, In Ubuntu, we fixed this FTBFS with the following patch, it was published successfully (https://launchpad.net/ubuntu/+source/aqsis/1.8.2+git20210815-1ubuntu1) Thanks for considering the patch. -- System Information: Debian Release: bookworm/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), (100, 'jammy-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-30-generic (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru aqsis-1.8.2+git20210815/debian/rules aqsis-1.8.2+git20210815/debian/rules --- aqsis-1.8.2+git20210815/debian/rules2022-03-05 22:02:59.0 +0100 +++ aqsis-1.8.2+git20210815/debian/rules2022-05-27 09:24:01.0 +0200 @@ -17,10 +17,16 @@ %: dh $@ --buildsystem=cmake +ifeq ($(DEB_HOST_ARCH), armhf) +AQSIS_USE_QT=OFF +else +AQSIS_USE_QT=ON +endif + override_dh_auto_configure: dh_auto_configure -- \ -DSYSCONFDIR=/etc/aqsis \ - -DAQSIS_USE_QT:BOOL=ON \ + -DAQSIS_USE_QT:BOOL=$(AQSIS_USE_QT) \ -DAQSIS_USE_EXTERNAL_TINYXML:BOOL=ON \ -DAQSIS_USE_PDIFF:BOOL=OFF \ -DAQSIS_USE_RPATH:BOOL=OFF
Bug#997512: zzuf: Fix FTBFS by disabling win32 test
Package: zzuf Version: 0.15-1 Followup-For: Bug #997512 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to fix the FTBFS discussed here: it simply consists in disabling the win32 test. Thanks for considering the patch. -- System Information: Debian Release: bookworm/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-27-generic (SMP w/16 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru zzuf-0.15/debian/patches/0001-test-Do-not-check-win32-as-it-fails.patch zzuf-0.15/debian/patches/0001-test-Do-not-check-win32-as-it-fails.patch --- zzuf-0.15/debian/patches/0001-test-Do-not-check-win32-as-it-fails.patch 1970-01-01 01:00:00.0 +0100 +++ zzuf-0.15/debian/patches/0001-test-Do-not-check-win32-as-it-fails.patch 2022-05-03 14:12:06.0 +0200 @@ -0,0 +1,24 @@ +From 173742831d1ba9a0dfe815757d05c19b5c92da58 Mon Sep 17 00:00:00 2001 +From: Alexandre Ghiti +Date: Tue, 3 May 2022 14:11:57 +0200 +Subject: [PATCH] test: Do not check win32 as it fails + +--- + test/Makefile.am | 1 - + 1 file changed, 1 deletion(-) + +diff --git a/test/Makefile.am b/test/Makefile.am +index 7a3719c..db24f39 100644 +--- a/test/Makefile.am b/test/Makefile.am +@@ -18,7 +18,6 @@ TESTS = check-zzuf-A-autoinc \ + check-zzuf-M-max-memory \ + check-zzuf-r-ratio \ + check-source \ +-check-win32 \ + check-overflow \ + check-div0 \ + check-utils \ +-- +2.34.1 + diff -Nru zzuf-0.15/debian/patches/series zzuf-0.15/debian/patches/series --- zzuf-0.15/debian/patches/series 2015-06-28 13:45:01.0 +0200 +++ zzuf-0.15/debian/patches/series 2022-05-03 14:12:24.0 +0200 @@ -0,0 +1 @@ +0001-test-Do-not-check-win32-as-it-fails.patch
Bug#1006047: Update?
Hi guys, I don't mean to pressure you, I'd like to know if we (ubuntu) should take the delta proposed above or do you intend to push the fix soon? It has been blocking pygments migration for 1 month now. Thanks, Alex
Bug#1004230: libgpuarray: please drop upstreamtestsclblas until bug 949767 is fixed
Hi, The latest failure (https://ci.debian.net/data/autopkgtest/unstable/armhf/libg/libgpuarray/18386433/log.gz) does not seem directly related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997908 as now multiple tests trigger a segfault: should we open another bug for that or can you confirm that it is related? FYI the same segfault happen in Ubuntu (https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/armhf/libg/libgpuarray/20220122_104616_37fcb@/log.gz). Thanks, Alex
Bug#1002532: pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT
On Sun, 23 Jan 2022 22:17:08 +0100 Mattia Rizzolo wrote: > On Fri, Jan 21, 2022 at 03:51:02PM +0100, Alexandre Ghiti wrote: > > I can't find how to create a MR in salsa, can you pull directly from here: > > > > https://salsa.debian.org/alexghiti/ruby-pygments.rb/-/tree/int/alex/2.3.0 > > > > It successfully built in my PPA, if you need any more modification, do > > not hesitate. > > Ah, another thing. Please be careful with the version you pick. > > You used 2.3.0+ds-1ubuntu1, which is *higher* than what I'll be > uploading, namely 2.3.0+ds-1. > Furthermore, in your PPA you used 2.3.0+ds-1ubuntu2, which would also > conflict with an eventual -1ubuntu done in the offical ubuntu archive. > > I'd recommend you used something like -0ppa1 or -0ubuntu1~ppa1 or > somesuch. > > (in this case this is of no consequence, but just something to note). Thanks for the advice. > > > > Lastly, I noticed that you haven't even touched the changelog. In this > case there was even a new copyright holder, so it really should have > been updated. Sorry and thanks for taking care of that. > I didn't add you to the paragraph of d/copyright, as I assume you are > doing this under your paid time, and I don't know what's Canonical's > rules regarding copyright here. If needed/wanted, just send me a note > and I'll update the copy in git. No problem. Regarding the autopkgtest failure (again an oversight on my part, sorry), I fixed it here, it works in my PPA and on an ubuntu jammy VM (I failed to make autopkgtest work with testing): https://salsa.debian.org/alexghiti/ruby-pygments.rb/-/commit/19442f7b89c5a6ca5ef1d8e1e6ebc42a261e441e Thanks again, Alex > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > More about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Bug#1002532: pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT
On Fri, 21 Jan 2022 12:08:27 +0100 Alexandre Ghiti wrote: > On Thu, 20 Jan 2022 18:50:33 +0100 Mattia Rizzolo wrote: > > Hi Alex, > > > > On Thu, Jan 06, 2022 at 11:19:00AM +0100, Alexandre Ghiti wrote: > > > As the current version we have is from 2017, I bumped the version of > > > this package to the latest available version: I updated the patches, > > > removed the ones that do not apply anymore, updated the build system > > > and dependencies. The result is available in my PPA [2] and fixes the > > > issue we encounter here. > > > > > > Can you consider pulling this? > > > > Thank you for this!! > > > > > > I had a look at your work, however I couldn't help but notice that: > > * the .orig you used looks odd, much larger than what I get from uscan > > (despite yours is also using a different compression, so repacked). > > I used 'git archive' directly, I did not know about uscan (thank you > and Graham). > > > * You did a ton of patch wrangling, including deletion, renaming, > > rebasing, etc. which is all fine, except that the way you did it > > obscures quite a bit what you did. Why did you drop the numbers from > > the patches? Do you have --no-patch-numbers as you gbp-pq default or > > something? > > I changed the patches names since they were different: I fixed that in > my coming MR. Thanks for gbp that I did not know neither. > > > * why requiring gem2deb >=1 ? that's already in bullseye as well in > > focal, so why did you feel the need to add the version? (that's also > > not in the changelog) > > I simply copied the debian/ directory from the previous version that I > got from pull-lp-source, I did not use git...I'll use git in the > future, thanks. > > > > > As such, I went ahead and re-imported the repacked origin I got myself > > in git. > > Could I ask you to submit a MR on top of it, with at least commits > > separating the deletion, refresh and rebasing of patches (and eventual > > new ones, I can't tell at a glance if any new patch appeared…) also > > separated. > > https://salsa.debian.org/ruby-team/ruby-pygments.rb > > It's on its way :) I can't find how to create a MR in salsa, can you pull directly from here: https://salsa.debian.org/alexghiti/ruby-pygments.rb/-/tree/int/alex/2.3.0 It successfully built in my PPA, if you need any more modification, do not hesitate. Thanks, Alex > > > > > Thank you for your work!! :) > > Thank you for your remarks (and thanks Graham for his help ;)) > > Alex > > > > > -- > > regards,
Bug#1002532: pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT
On Thu, 20 Jan 2022 18:50:33 +0100 Mattia Rizzolo wrote: > Hi Alex, > > On Thu, Jan 06, 2022 at 11:19:00AM +0100, Alexandre Ghiti wrote: > > As the current version we have is from 2017, I bumped the version of > > this package to the latest available version: I updated the patches, > > removed the ones that do not apply anymore, updated the build system > > and dependencies. The result is available in my PPA [2] and fixes the > > issue we encounter here. > > > > Can you consider pulling this? > > Thank you for this!! > > > I had a look at your work, however I couldn't help but notice that: > * the .orig you used looks odd, much larger than what I get from uscan > (despite yours is also using a different compression, so repacked). I used 'git archive' directly, I did not know about uscan (thank you and Graham). > * You did a ton of patch wrangling, including deletion, renaming, > rebasing, etc. which is all fine, except that the way you did it > obscures quite a bit what you did. Why did you drop the numbers from > the patches? Do you have --no-patch-numbers as you gbp-pq default or > something? I changed the patches names since they were different: I fixed that in my coming MR. Thanks for gbp that I did not know neither. > * why requiring gem2deb >=1 ? that's already in bullseye as well in > focal, so why did you feel the need to add the version? (that's also > not in the changelog) I simply copied the debian/ directory from the previous version that I got from pull-lp-source, I did not use git...I'll use git in the future, thanks. > > As such, I went ahead and re-imported the repacked origin I got myself > in git. > Could I ask you to submit a MR on top of it, with at least commits > separating the deletion, refresh and rebasing of patches (and eventual > new ones, I can't tell at a glance if any new patch appeared…) also > separated. > https://salsa.debian.org/ruby-team/ruby-pygments.rb It's on its way :) > > Thank you for your work!! :) Thank you for your remarks (and thanks Graham for his help ;)) Alex > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > More about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Bug#1002532: pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT
Hi guys, The same issue was reported to Ubuntu. I shared this problem upstream [1], and the maintainer quickly proceeded by providing a patch to fix it in the latest version. As the current version we have is from 2017, I bumped the version of this package to the latest available version: I updated the patches, removed the ones that do not apply anymore, updated the build system and dependencies. The result is available in my PPA [2] and fixes the issue we encounter here. Can you consider pulling this? Thanks, Alex [1] https://github.com/pygments/pygments.rb/issues/234 [2] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13185899/+listing-archive-extra
