Bug#972478: libjogl2-java, build-depends no longer satisfiable on 32-bit architectures.

2020-10-18 Thread peter green
Tags 972478 -sid thanks On 19/10/2020 04:15, peter green wrote: Package: libjogl2-java Version: 2.3.2+dfsg-9 Tags: bullseye, sid x-debbugs-cc: sci...@packages.debian.org x-debbugs-cc: k...@packages.debian.org Justification: rc policy: packages must be buildable in the same release. libjogl2

Bug#972478: libjogl2-java, build-depends no longer satisfiable on 32-bit architectures.

2020-10-18 Thread peter green
Package: libjogl2-java Version: 2.3.2+dfsg-9 Tags: bullseye, sid x-debbugs-cc: sci...@packages.debian.org x-debbugs-cc: k...@packages.debian.org Justification: rc policy: packages must be buildable in the same release. libjogl2-java can no longer be built on 32-bit architectures, specifically

Bug#972239: geoalchemy2 build-depends on obsolete packages.

2020-10-14 Thread peter green
Package: geoalchemy2 Version: 0.7.0-1 Severity: serious geoalchemy2 build-depends on postgresql-12-postgis-3 and postgresql-12-postgis-3-scripts, which have been replaced by postgresql-13-postgis-3 postgresql-13-postgis-3-scripts, the old packages are still present in unstable as cruft

Bug#972100: CVE-2019-15547 CVE-2019-15548 (rust-ncurses)

2020-10-13 Thread peter green
I just looked at this issue. rust-ncurses is a thin wrapper around ncurses. It exposes unsafe (in the rust sense) C APIs to safe rust code. The rust security team consider this to be a vulnerability. There is more discussion of this issue at https://github.com/jeaye/ncurses-rs/issues/188 the

Bug#972058: libtickit-perl autopkgtest failure.

2020-10-11 Thread peter green
Package: libtickit-perl Version: 0.71-1 Severity: serious The libtickit-perl autopkgtest is failing on the unstable->testing migration tests (the plain unstable tests are not up to date enough to be useful). On i386 and amd64 this failure is a regression (on the other architectures where

Bug#971793: vt: conflicting build-dependencies.

2020-10-07 Thread peter green
Package: vt Version: 0.57721+ds-2 Severity: serious Justification: rc policy: packages must be buildable within the same release. vt build-depends on libcurl4-openssl-dev and libhts-dev. Libhts-dev recently added a dependency on libcurl4-gnutls-dev. Since libcurl4-openssl-dev and

Bug#971792: augustus: conflicting build-dependencies.

2020-10-07 Thread peter green
Package: augustus Version: 3.3.3+dfsg-3 Severity: serious Justification: rc policy: packages must be buildable within the same release. Augustus build-depends on libcurl4-nss-dev and libhts-dev. Libhts-dev recently added a dependency on libcurl4-gnutls-dev. Since libcurl4-nss-dev and

Bug#912941: closed wrong bug

2020-09-24 Thread Peter Green
reopen 912941 thanks

Bug#966904: pfstools: FTBFS: array2d.h:173:9: error: ‘__assert_fail’ was not declared in this scope; did you mean ‘MagickCore::__assert_fail’?

2020-09-23 Thread peter green
On 24/09/2020 06:25, Andreas Metzler wrote: On 2020-08-28 peter green wrote: Tags 966904 +patch thanks The issue is that Magick++.h (indirectly) includes assert.h inside a namespace. [...] I would argue that is a bug in imagemagick and have filed bugs in both Debian and upstream as https

Bug#970741: rhythmbox build-depends unsatisfiable in testing

2020-09-22 Thread peter green
Source: rhythmbox Version: 3.4.4-2 Severity: serious rhythmbox build-depends on gstreamer1.0-doc which is no longer built by the gstreamer1.0 source package. It still seems to be present in unstable as a cruft package, but is completely gone from testing.

Bug#970740: farstream-0.2 build-depends unsatisfiable in testing

2020-09-22 Thread peter green
Source: farstream-0.2 Version: 0.2.8-5 Severity: serious farstream-0.2 build-depends on gstreamer1.0-doc which is no longer built by the gstreamer1.0 source package. It still seems to be present in unstable as a cruft package, but is completely gone from testing.

Bug#970739: clutter-gst-3.0 build-depends unsatisfiable in testing

2020-09-22 Thread peter green
Source: clutter-gst-3.0 Version: 3.0.27-1 Severity: serious clutter-gst-3.0 build-depends on gstreamer1.0-doc which is no longer built by the gstreamer1.0 source package. It still seems to be present in unstable as a cruft package, but is completely gone from testing.

Bug#970730: spice-gtk build-depends unsatisfiable in testing

2020-09-22 Thread peter green
Source: spice-gtk Version: 0.38-2 Severity: serious spice-gtk build-depends on gstreamer1.0-doc which is no longer built by the gstreamer1.0 source package. It still seems to be present in unstable as a cruft package, but is completely gone from testing.

Bug#970727: python-magcode-core needs a source-only upload.

2020-09-22 Thread peter green
Source: python-magcode-core Version: 1.5.4-2 Severity: serious The release team have decreed that non-buildd binaries can no longer migrate to testing, please make a source-only upload so your package can migrate.

Bug#925781: mozjs NMU to fix build issues.

2020-09-19 Thread peter green
tags 925781 +patch +pending tags 967177 +patch +pending thanks I have decided to take the Ubuntu fixes for mozjs52 and turn them into a NMU. I also ran into some issues with the clean target while preparing the NMU so I fixed those too. mozjs52 has only one reverse-dependency: cjs which in

Bug#937234: pam-python/libpam-mklocaluser/debian-edu-config python3 migration.

2020-09-19 Thread peter green
The debian python maintainers are trying to phase out python 2. python 2 has been granted a stay of execution as some important software requires it to build. However we should still be attempting to get rid of use at runtime if at all possible. Also the "unversioned python" packages have been

Bug#949177: libaccounts-glib appears to be unmaintained.

2020-09-19 Thread peter green
The libaccounts-glib package does not seem to be getting maintained in Debian, it has had a rc bug (deprecated declarations and -Werror) for 8 months with no maintainer response and has recently picked up a second one (unversioned python removal). It has not had an upload for 3 years. Both of

Bug#970132: buster-pu: package rustc/1.41.1+dfsg1-1~deb10u1

2020-09-17 Thread peter green
On 17/09/2020 15:06, Emilio Pozuelo Monfort wrote: On 12/09/2020 11:09, Emilio Pozuelo Monfort wrote: This updates buster's rustc to 1.41, as needed by the new firefox 78 ESR. The bootstrap happens with the upstream binaries as we've done in the past. I have also avoided the bump to LLVM 9/10,

Bug#942915: ca-certificates: Python2 removal in sid/bullseye

2020-09-15 Thread peter green
severity 942915 serious thanks The "python" binary package is no longer available in testing or unstable (in unstable it's present as a cruft package but uninstallable, in testing it's completely gone)

Bug#970415: aseba build-depends unsatisfiable in testing and unstable.

2020-09-15 Thread peter green
Source: aseba Version: 1.6.0-5 Severity: serious Tags: bullseye, sid aseba build-depends on the "python" binary package which is no longer built by the "python-defaults" source package. In unstable it is present as a cruft package but said cruft package is uninstallable due to strictly

Bug#970406: flowcanvas build-depends unsatisfiable in testing and unstable.

2020-09-15 Thread peter green
Source: flowcanvas Version: 0.7.1+dfsg0-0.5 Severity: serious Tags: bullseye, sid flowcanvas build-depends on the "python" binary package which is no longer built by the "python-defaults" source package. In unstable it is present as a cruft package but said cruft package is uninstallable due

Bug#942960: catch: Python2 removal in sid/bullseye

2020-09-15 Thread peter green
severity 942960 serious thanks The "python" binary package has now been removed from testing, hence this bug is now serious. If there is still no maintainer response I may well NMU this later.

Bug#970405: avw.lv2 build-depends unsatisfiable in testing and unstable.

2020-09-15 Thread peter green
Source: avw.lv2 Version: 0.1.6~dfsg0-1 Severity: serious Tags: bullseye, sid avw.lv2 build-depends on the "python" binary package which is no longer built by the "python-defaults" source package. In unstable it is present as a cruft package but said cruft package is uninstallable due to

Bug#969888: pdf2djvu FTBFS with poppler 20

2020-09-08 Thread peter green
Source: pdf2djvu Version: 0.9.17-1 Severity: serious Tags: ftbfs, fixed-upstream pdf2djvu's configure script fails to parse the poppler version with the newly released poppler 20. This results in a bunch of errors. This is fixed upstream in version 0.9.17.1

Bug#968714: extractpdfmark FTBFS with poppler 0.85

2020-09-08 Thread peter green
It seems the recent upload of poppler 20 introduced further breakage. Poppler changed the return type of Catalog::getDestNameTreeDest and Catalog::getDestsDest from LinkDest * to std::unique_ptr If I am following the code correctly, it seems that extractpdfmark had a memory leak, previously,

Bug#969569: Gnome-builder: build-depends on package that is not in testing.

2020-09-05 Thread peter green
Package: gnome-builder Version: 3.36.0-3 Severity: serious Tags: patch The gnome-builder source package build-depends on libenchant-dev (source package enchant) which was recently removed from testing (see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956881 ). However the gnome-builder

Bug#969565: python3-azure-cli: dependency unsatisfiable in sid and questionable in testing.

2020-09-04 Thread peter green
Package: python3-azure-cli Version: 2.10.1-1 Severity: serious python3-azure-cli depends on python3-cryptography << 3.0.0 . In unstable this dependency is unsatisfiable because python3-cryptography is now at version 3.1-1 . In testing the dependency is strictly-speaking satisfiable because

Bug#942965: Patch for closure-compiler rc bugs, possible NMU.

2020-09-03 Thread peter green
:03PM +0100, peter green wrote: tags 942965 +patch tags 961839 +pending The attached debdiff fixes bugs 942965 and 961839, the former by changing the build-dependency from python-docutils to python3-docutils and the latter by adding "ant.build.javac.source=8" and "ant.build.javac.targ

Bug#942965: Patch for closure-compiler rc bugs, possible NMU.

2020-09-03 Thread peter green
tags 942965 +patch tags 961839 +pending The attached debdiff fixes bugs 942965 and 961839, the former by changing the build-dependency from python-docutils to python3-docutils and the latter by adding "ant.build.javac.source=8" and "ant.build.javac.target=8" to debian/ant.properties. If I do

Bug#964674: debian-reference: FTBFS: build-dependency not installable: libopencc2-data

2020-09-03 Thread peter green
Lucas Nussbaum wrote: > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: libopencc2-data but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. Fixed in git. Tagging this bug as pending This

Bug#969396: sleef FTBFS on arm64 with gcc-10, sve code requires __sizeless_struct

2020-09-01 Thread peter green
Package: sleef Version: 3.4.1-4 Severity: serious The most recent upload of sleef fixed the build on amd64, armhf, i386 and ppc64el. Unfortunately it is still failing on arm64, with the following error. In file included from /<>/src/libm/sleefsimdsp.c:209: /<>/src/arch/helpersve.h:94:27:

Bug#969158: expeyes: maybe a false positive generated by mail_autoremovals.pl?

2020-09-01 Thread Peter Green
(note: this mail represents my opinions as an ordinary dd, I am not a member of the release team) due to the fact that it is supposed to (build-)depend on binutils-avr, which FTBFS. As I understand it "(build-)depends" should be interpreted as "depends or build-depends" The source package

Bug#957069: cbmplugs: ftbfs with GCC-10

2020-08-27 Thread peter green
Tags 957069 +patch thanks gcc-10 changed the behaviour around global variables defined in multiple compilation units. Defined a variable in multiple compilation units with the default compiler flags will now result in a link failure. However in this particular case the variable doesn't appear

Bug#966904: pfstools: FTBFS: array2d.h:173:9: error: ‘__assert_fail’ was not declared in this scope; did you mean ‘MagickCore::__assert_fail’?

2020-08-27 Thread peter green
Tags 966904 +patch thanks The issue is that Magick++.h (indirectly) includes assert.h inside a namespace. Note that generally only the first include of a header actually does anything due to the presense of include gaurds. Therefore if assert.h is included before Magick++.h then everything is

Bug#969128: libmagick++-6.q16-dev includes assert.h inside namespace.

2020-08-27 Thread peter green
Package: libmagick++-6.q16-dev Version: 8:6.9.11.24+dfsg-1+b1 This bug is based on testing related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966904 Compiling the following simple test program fails. #include #include int main() { assert(1==2); } g++ `pkg-config --cflags

Bug#963290: e-antic: FTBFS: ../e-antic/e-antic.h:24:2: error: #error FLINT 2.5.2 or 2.5.3 required

2020-08-27 Thread peter green
tags 963290 +patch thanks I just took a look at this issue. First I did some digging in the upstream git repo. Once I figured out their branch structure (the "master0" branch is apparently where current releases are made from) I was able to find two relavent commits.

Bug#968637: freeimage: FTBFS against libraw 0.20.0

2020-08-27 Thread peter green
tags 968637 +patch thanks On 26/08/2020 06:04, peter green wrote: Upstream seem to have a fix for this. https://sourceforge.net/p/freeimage/svn/1842/ I was able to succesfully apply the upstream change to the Debian package and built it in Raspbian bullseye-staging . I also bumped the build

Bug#968637: freeimage: FTBFS against libraw 0.20.0

2020-08-25 Thread peter green
Upstream seem to have a fix for this. https://sourceforge.net/p/freeimage/svn/1842/

Bug#965960: patch for chromium bugs 965960 and 967124, possible NMU.

2020-08-25 Thread peter green
I have prepared a patch for chromium addressing bugs 965960 and 967124 Bug 965960 (crash on 32-bit) was caused by lack of support in the sandbox for the 64-bit time syscalls that have recently been added to Linux/glibc. I added __NR_clock_gettime64, __NR_clock_nanosleep_time64 and

Bug#957816: slurm-llnl: ftbfs with GCC-10

2020-08-22 Thread peter green
tags 957816 +patch thanks The build failures are caused by a change to default behaviour in gcc-10, previous versions of gcc defaulted to -fcommon which allows a variable to be definined in multiple compilation units. gcc-10 on the other hand defaults to -fno-common. There seem to be two

Bug#965960: chromium: Received signal 11 SEGV_ACCERR 000004c03193. can't load pages and extensions

2020-08-21 Thread peter green
On 13/08/2020 19:53, peter green wrote: thank you for packaging chromium. after upgrading libc to 2.31, all available chromium: 80 and 83 are cashing. the bug has been treated at redhat: https://bugzilla.redhat.com/show_bug.cgi?id=1773289 and has been confirmed by upstream: https

Bug#968761: mailutils: not binnmu safe.

2020-08-20 Thread Peter Green
Package: mailutils Version: 1:3.9-3.2 Tags: patch I run a derivative called raspbian and I noticed that mailutils was getting repeatedly binnmu'd by our autobinnmuer because the binary packages were not installable. I don't know what exactly triggered the first binnmu (our autobinnmuer does

Bug#968742: diffoscope build-depends on package that is not in testing.

2020-08-20 Thread peter green
Package: diffoscope Version: 156 Severity: serious Diffoscope has been removed from testing and cannot re-enter because it build-depends on gnumeric, which has been kicked out of testing due to a python2 dependency. Since this build-dependency only appears to be used for testing I would

Bug#968245: [Pkg-pascal-devel] Bug#968245: Bug#968245: fpc: autopkgtest failure.

2020-08-20 Thread peter green
On 20/08/2020 06:50, Graham Inggs wrote: For what it's worth, I tried building fpc including your debdiff and running the autopkgtests in an Ubuntu PPA. They passed on amd64, Thanks for confirming (my local setup is far from the same as the test infrastructure) and failed on arm64 [1]

Bug#968729: haskell-gi-pango FTBFS parse error on input ‘HarfBuzz.FeatureT.feature_t’

2020-08-20 Thread peter green
Source: haskell-gi-pango Version: 1.0.22-1 Severity: serious Tags: ftbfs The most recent binnmus of haskell-gi-pango in sid failed with GI/Pango/Objects/Font.hs:670:9: error: parse error on input ‘HarfBuzz.FeatureT.feature_t’ | 670 | Ptr HarfBuzz.FeatureT.feature_t -> --

Bug#968724: ipe-tools FTBFS with poppler 0.85

2020-08-20 Thread peter green
Package: ipe-tools Severity: serious Version: 1:7.2.7.2-4 Tags: patch ipe-tools fails to build with poppler 0.85, there are multiple issues. I whipped up a patch and uploaded it to raspbian, A debdiff should appear soon at https://debdiffs.raspbian.org/main/i/ipe-tools I notice it looks like

Bug#968719: popplerkit.framework FTBFS with poppler 0.85

2020-08-20 Thread peter green
Package: popplerkit.framework Version: 0.0.20051227svn-8 Severity: serious Tags: bullseye sid patch popplerkit.framework FTBFS with poppler 0.85 because globalParams is now a std::unique_ptr https://github.com/freedesktop/poppler/commit/759d190581f8ff069ecee9155313a8e69a2ca9c6 I have whipped

Bug#968714: extractpdfmark FTBFS with poppler 0.85

2020-08-20 Thread peter green
Package: extractpdfmark Version: 1.1.0-1 Severity: serious Tags: patch extractpdfmark FTBFS with poppler 0.85 destname.cc:85:62: error: no matching function for call to ‘PDFDoc::findPage(int&, int&)’ 85 | pagenum = doc->findPage (page_ref.num, page_ref.gen); Doing a bit of

Bug#968245: fpc: autopkgtest failure.

2020-08-18 Thread peter green
On 11/08/2020 16:27, peter green wrote: Package: fpc Version: 3.2.0+dfsg-5 Severity: serious The autopkgtest for fpc 3.2.0 is failing Compiling utests.pp PPU Loading /usr/lib/x86_64-linux-gnu/fpc/3.2.0/units/x86_64-linux/fcl-base/custapp.ppu PPU Source: custapp.pp not available Recompiling

Bug#965960: chromium: Received signal 11 SEGV_ACCERR 000004c03193. can't load pages and extensions

2020-08-13 Thread peter green
thank you for packaging chromium. after upgrading libc to 2.31, all available chromium: 80 and 83 are cashing. the bug has been treated at redhat: https://bugzilla.redhat.com/show_bug.cgi?id=1773289 and has been confirmed by upstream:

Bug#967954: [Pkg-rust-maintainers] Bug#967954: debcargo: generated ranged build-deps result in "BD-uninstallable" on debian buildd network

2020-08-12 Thread peter green
It has been said in the past by the release team that the current autobuilder behaviour of only considering the first option for a build-dependency is by design to improve the determinism of the autobuilding process. I don't think you will persuade them to change it. The proper fix IMO would

Bug#968245: fpc: autopkgtest failure.

2020-08-11 Thread peter green
Package: fpc Version: 3.2.0+dfsg-5 Severity: serious The autopkgtest for fpc 3.2.0 is failing Compiling utests.pp PPU Loading /usr/lib/x86_64-linux-gnu/fpc/3.2.0/units/x86_64-linux/fcl-base/custapp.ppu PPU Source: custapp.pp not available Recompiling CustApp, checksum changed for

Bug#968121: [Pkg-pascal-devel] FPC 3.2.0 upload to SID

2020-08-11 Thread peter green
On 11/08/2020 13:06, Graham Inggs wrote: I've had a quick look at ddrescue [1], but I don't know how to fix that. Does anyone have any suggestions? Googling the error message took me to https://wiki.freepascal.org/User_Changes_Trunk which has an entry "Property field access lists no longer

Bug#968126: [Pkg-pascal-devel] FPC 3.2.0 upload to SID

2020-08-11 Thread peter green
On 11/08/2020 13:06, Graham Inggs wrote: I've also looked at mricron [2][3], and changing '(**)' to '*)' in both places fixes the compilation, but I have no idea what the '(**)' means. Can anyone tell me? (* and *) are comment delimeters Borland style pascal traditionally handled comments

Bug#964611: [Pkg-pascal-devel] Bug#964611: libqtpas: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

2020-08-07 Thread peter green
+#MISSING: 2.6+2.0.8+dfsg-1# _ZN7QVectorI6QPointE11reallocDataEii6QFlagsIN10QArrayData16AllocationOptionEE@Base 2.6~alpha c++filt -n decodes this to QVector::reallocData(int, int, QFlags) This looks like an instantiation of a QT template that may or may not be included in the library as a

Bug#967991: glirc, build-depends on package which is not in testing

2020-08-06 Thread peter green
notfound 967991 2.35-1 found 967991 2.32-1 close 967991 2.35-1 thanks On 06/08/2020 13:20, Clint Adams wrote: On Thu, Aug 06, 2020 at 11:20:00AM +0100, peter green wrote: glirc can no longer be built in testing because haskell-regex-tdfa is no longer present in testing. Ilias Tsitsimpis has

Bug#963737: ilias...@debian.org

2020-08-06 Thread peter green
Ilias Tsitsimpis wrote: We should make sure that anyone using this package has migrated to skylighting and then remove it. hi, highlighting-kate was just removed from testing at your request, but carettah still build-depends on it in both testing and unstable. Should I go ahead and file a rc

Bug#967991: glirc, build-depends on package which is not in testing

2020-08-06 Thread peter green
Package: glirc Version: 2.35-1 Severity: serious Justification: rc policy: "packages must be buildable within the same release" glirc can no longer be built in testing because haskell-regex-tdfa is no longer present in testing. Ilias Tsitsimpis has filed a bug report against the package saying

Bug#942965: closure-compiler: Python2 removal in sid/bullseye

2020-07-30 Thread peter green
severity 942965 serious thanks closure-compiler build-depends on python-docutils which has now been removed from testing.

Bug#804267: mercurial/mercurial-crecord conflict preventing testing migration.

2020-07-30 Thread peter green
severity 937009 serious thanks mercurial can no longer be built in testing because of a build-dependency on python-docutils which has been removed. This is fixed in unstable, but mercurial is blocked from migrating to testing because it declares a conflicts on mercurial-crecord (<=

Bug#936371: dbus-python: Python2 removal in sid/bullseye

2020-07-27 Thread peter green
On 27/07/2020 16:31, s...@debian.org wrote: On Thu, 23 Jul 2020 at 18:01:55 +0100, peter green wrote: dbus-python in testing build-depends on python-gi which is no longer available in testing. This is fixed in unstable but the fix is blocked from migrating to testing by https://bugs.debian.org

Bug#966241: x264 FTBFS with make 4.2

2020-07-25 Thread Peter Green
Package: x264 Version: 2:0.159.2999+git296494a-2 Severity: serious Tags: patch Make 4.3 changed the escaping rules with the # symbol is used inside a parameter to functions like $shell. Previously it needed to be escaped, now it needs to *not* be escaped. A change was applied to the debian

Bug#936371: dbus-python: Python2 removal in sid/bullseye

2020-07-23 Thread peter green
severity 936371 serious thanks dbus-python in testing build-depends on python-gi which is no longer available in testing. This is fixed in unstable but the fix is blocked from migrating to testing by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965308

Bug#957314: gst-plugins-bad1.0 NMU to fix build in testing and unstable

2020-07-23 Thread peter green
notfixed 965298 1.16.2-2.2 tags 965298 +patch tags 957314 +patch thanks gst-plugins-bad1.0 1.16.2-2.2 fails to build in both testing or unstable for different reasons. In unstable it fails to build because gcc-10 got stricter about multiple definitions of global variables. Upstream already

Bug#960748: node-babel: meta bug to keep out of testing

2020-07-20 Thread peter green
Last blockers for removal: 1. node-yarnpkg - #960120 - should be patched/fixed for 1.x or switch to 'berry'/2.x (supports babel 7) in time for bullseye 2. libjs-webrtc-adapte - #959798 - browserify-lite can be replaced by webpack 3. rainloop - #960021 - not in bullseye Once the blockers are

Bug#962563: transition: nettle

2020-07-18 Thread peter green
I just went through the remaining items on the transition tracker for this transition filing bug reports where appropriate. freewheeling: sid-only, unrelated FTBFS bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946863 haskell-hopenpgp/haskell-hopenpgp-tools: haskell-incremental-parser

Bug#965301: opendht FTBFS in unstable.

2020-07-18 Thread peter green
Package: opendht Version: 0.6.6-1 Severity: serious x-debbugs-cc: msgpac...@packages.debian.org tags: ftbfs opendht cannot currently be built in unstable, there are two issues. Firstly, the build can't even be attempted on armel or mipsel because the build-dependencies are unsatisfiable. The

Bug#965300: ocamlnet FTBFS on most architectures.

2020-07-18 Thread peter green
Package: ocamlnet Version: 4.1.6-1 Severity: serious Tags: FTBFS When binnmu'd for the nettle transition ocamlnet failed to build on most architectures (it succeeded on mipsel, mips64el and armel) with the following error. make[1]: Leaving directory '/<>' dh_dwz -a dwz:

Bug#965299: haskell-incremental-parser no longer buildable on many architectures.

2020-07-18 Thread peter green
Package: haskell-incremental-parser Version: 0.4.0.2-1 Severity: serious haskell-incremental-parser 0.4.0.2-1 added a build-dependency on libghc-rank2classes-dev (>= 1.0) however this package is only available on four out of the ten release archictures. Potential ways forward: 1. fix

Bug#965298: gst-plugins-bad1.0 cannot be built in testing.

2020-07-18 Thread peter green
Package: gst-plugins-bad1.0 Version: 1.16.2-2.1 Severity: serious x-debbugs-cc: sramac...@debian.org, locutusofb...@debian.org Neither version 1.16.2-2.1 (from bullseye) or version 1.16.2-2.2 (from sid) can be built in testing. 1.16.2-2.1 cannot be built because libsrt-dev has been removed.

Bug#961811: baresip: diff for NMU version 0.6.1-1.1

2020-07-18 Thread peter green
On 17/07/2020 08:42, peter green wrote: On 17/07/2020 06:40, Sebastian Ramacher wrote: Hi On 2020-07-17 00:02:17 +0100, peter green wrote: (note: I am not the maintainer) Sebastian Ramacher wrote: I've prepared an NMU for baresip (versioned as 0.6.1-1.1) and uploaded it to DELAYED/2. While

Bug#961811: baresip: diff for NMU version 0.6.1-1.1

2020-07-17 Thread peter green
On 17/07/2020 06:40, Sebastian Ramacher wrote: Hi On 2020-07-17 00:02:17 +0100, peter green wrote: (note: I am not the maintainer) Sebastian Ramacher wrote: I've prepared an NMU for baresip (versioned as 0.6.1-1.1) and uploaded it to DELAYED/2. While I have not tested, I am 99% sure your

Bug#961811: baresip: diff for NMU version 0.6.1-1.1

2020-07-16 Thread peter green
(note: I am not the maintainer) Sebastian Ramacher wrote: I've prepared an NMU for baresip (versioned as 0.6.1-1.1) and uploaded it to DELAYED/2. While I have not tested, I am 99% sure your fix for make 4.3 will break the build with make 4.2 in testing. Since I wrote the post in response to

Bug#962725: gst-plugins-bad1.0: diff for NMU version 1.16.2-2.2

2020-07-16 Thread peter green
(note: I am not the maintainer) Sebastian Ramacher wrote: I've prepared an NMU for gst-plugins-bad1.0 (versioned as 1.16.2-2.2) and uploaded it to DELAYED/2. Hi, I tried adding your proposed NMU to raspbian as part of trying to get the x265 transition to go through there. Unfortunately it

Bug#964632: hyperkitty/django-mailman3: FTBFS: ValueError: max() arg is an empty sequence

2020-07-12 Thread peter green
Both the django-mailman3 and the hyperkitty build failures look like the same issue , my looking however was focused on the hyperkitty failure as that is the one I became aware of first. First I looked at test history for hyperkitty on reproducible builds and looking at when relavent packages

Bug#964750: hypercorn build-dependencies unsatisfiable in testing.

2020-07-09 Thread peter green
Package: hypercorn Version: 0.9.4-1 Severity: serious Tags: patch Justification: rc policy "packages must be buildable within the same release" hypercorn build-depends on python3-asynctest, which is built from the python-asynctest source package. According to bug 954554 python3-asynctest is

Bug#964448: oca-core: needs a source-only upload

2020-07-07 Thread peter green
Package: oca-core Version: 11.0.20191007-3 Severity: serious The release team have decreed that non-buildd binaries can no longer migrate to testing. Please make a source-only upload so your package can migrate.

Bug#962877: oca-core: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd)

2020-07-07 Thread peter green
severity 962877 serious close 962877 11.0.20191007-3 thanks fonts-glewlwyd has now been dropped by the glewlwyd source package. The dependency is gone in unstable, but the fix is currently blocked from migrating to testing. A seperate bug report about that will follow.

Bug#962886: zoneminder: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd)

2020-07-07 Thread peter green
severity 962886 serious thanks fonts-glewlwyd has now been dropped by the glewlwyd source package.

Bug#962879: python3-cylc: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd)

2020-07-07 Thread peter green
severity 962879 serious thanks fonts-glewlwyd has now been dropped by the glewlwyd source package.

Bug#962878: omnidb-common: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd)

2020-07-07 Thread peter green
severity 962878 serious thanks fonts-glewlwyd has now been dropped by the glewlwyd source package.

Bug#962876: kytos-sphinx-theme-common: should depend on fonts-glyphicons-halflings (not fonts-glewlwyd)

2020-07-07 Thread peter green
severity 962876 serious thanks fonts-glewlwyd has now been dropped by the glewlwyd source package.

Bug#962880: python3-django-hyperkitty: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd)

2020-07-07 Thread peter green
severity 962880 serious thanks fonts-glewlwyd has now been dropped by the glewlwyd source package.

Bug#964136: glewlwyd build-depedencies unsatisfiable on armel, mipsel and mips64el

2020-07-05 Thread peter green
Retitle 964136 glewlwyd build-depedencies unsatisfiable on armel Thanks Build has been fixed for mipsel and mips64el Thanks, retitling the bug report for the remaining issue. but it remains impossible on armel since nodejs isn't available on this platform. The thing is nodejs is used

Bug#964136: glewlwyd build-depedencies unsatisfiable on armel, mipsel and mips64el

2020-07-02 Thread peter green
Package: glewlywd Version: 2.3.1-2 Severity: serious The new glewlywd package cannot be built on armel, mipsel or mips64el due to unsatisfiable build-dependencies. Specifically nodejs/npm on armel and librhonabwy-dev on mipsel/mips64el Generally there are three possible ways forward with this

Bug#963976: RFS: xscorch/0.2.1-1+nmu2.1 [NMU, RC] -- Clone of Scorched Earth

2020-07-01 Thread peter green
> I am looking for a sponsor for my package "xscorch" The main patch looks good, a couple of things needs to be addressed before I will sponsor it. Firstly you need to send a mail with the debdiff attached stating your intent to NMU to the bug report and giving the maintainer and

Bug#963916: rust-debcargo: Cannot build debcargo

2020-06-28 Thread peter green
I cannot build debcargo currently. It fails with: missing: pkg: package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 unsat-dependency: librust-cargo-0.43+default-dev:amd64 Thanks Sylvestre The root cause (or at least one of the

Bug#937442: pygame-sdl2: Python2 removal in sid/bullseye

2020-06-28 Thread peter green
severity 937442 serious thanks The cython binary package has been removed from testing. So pygame-sdl2 can no longer be built in testing

Bug#963682: booth: build-depends on removed package.

2020-06-25 Thread Peter Green
Package: booth. Version: 1.0-174-gce9f821-2 Severity: serious Booth build-depends on libcrmservice-dev which is no longer built by the pacemaker source package. It is still present in unstable as a cruft package but is completely gone from testing. Since libcrmservice-dev was a transitional

Bug#953537: xfsdump fails to install in /usr merged system.

2020-06-19 Thread peter green
Putting the Debian bug back in cc, for earlier mails please see https://marc.info/?l=linux-xfs=159253950420613=2 Eric Sandeen wrote: How does debian fix this for xfsprogs? Doesn't the same issue exist? I'm not seeing any cases like xfsdump where a binary is located in /sbin but symlinked

Bug#953537: xfsdump fails to install in /usr merged system.

2020-06-19 Thread peter green
Putting the debian bug back in cc, previous mails are visible at https://marc.info/?l=linux-xfs=159253950420613=2 On 19/06/2020 23:43, Dave Chinner wrote: Isn't the configure script supposed to handle install locations? Both xfsprogs and xfsdump have this in their include/builddefs.in:

Bug#953537: xfsdump fails to install in /usr merged system.

2020-06-18 Thread peter green
This bug has now caused xfsdump to be kicked out of testing which is making amanda unbuildable in testing. Yes, what's really needed here is for a change to be merged upstream (as all other deb packaging artifacts are) otherwise this will keep getting lost in time. To make it easier to

Bug#962871: qbittorrrent FTBFS in testing.

2020-06-15 Thread peter green
Package: qbittorrent Version: 4.1.7-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/qbittorrent.html ./../src/base/bittorrent/infohash.cpp: In constructor 'BitTorrent::InfoHash::InfoHash(const sha1_hash&)': ../../src/base/bittorrent/infohash.cpp:44:43:

Bug#962232: vanguards indirectly build-depends on cruft package.

2020-06-12 Thread peter green
I have now gone ahead with the NMU, the final debdiff is attatched (same as previous debdiff apart from changelog tweaks) diff -Nru vanguards-0.3.1/debian/changelog vanguards-0.3.1/debian/changelog --- vanguards-0.3.1/debian/changelog2019-07-26 16:30:09.0 + +++

Bug#962567: apper FTBFS can't find KF5TextWidgetsConfig.cmake

2020-06-09 Thread peter green
Package: apper Version: 1.0.0-2 Severity: serious Tags: bullseye, sid, patch http://buildd.raspbian.org/status/fetch.php?pkg=apper=armhf=1.0.0-2%2Bb4=1591727741 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apper.html CMake Error at

Bug#961460: src:newsboat: build depends on librust-xdg-2-dev which doesn't exist (anymore)

2020-06-09 Thread peter green
Yes, that. I look regularly at https://qa.debian.org/dose/debcheck/src_testing_main/ as we (the release team) require packages to be buildable in testing (we have some tolerance as the migration of build dependencies isn't guaranteed when checking if a package may migrate). Please help the rust

Bug#959439: FTBFS with Boost 1.71 (supercollider)

2020-06-08 Thread peter green
Tags 959439 +patch thanks I was able to apply the upstream fixes to the Debian supercollider packaging, in order to do so I had to make some formatting adjustments to the code(it seems upstream reformatted their codebase since the version that is in Debian) I did builds in Debian sid and

Bug#960421: libpwiz: FTBFS with boost 1.71

2020-06-07 Thread peter green
Some googling lead me to https://svnweb.freebsd.org/ports/head/multimedia/mkvtoolnix/files/patch-boost-1.69?view=markup=482787 which suggests it is now necessary to manually convert from tribool to bool by writing bool{value} Unfortunately after doing that I get In file included from

Bug#962423: pglogical FTBFS error: static declaration of 'AcquireDeletionLock' follows non-static declaration

2020-06-07 Thread peter green
Package: pglogical Version: 2.3.1-1 Severity: serious Tags: ftbfs It seems pglogical recently started failing to build. http://buildd.raspbian.org/status/fetch.php?pkg=pglogical=armhf=2.3.1-1%2Bb1=1591473342 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pglogical.html

Bug#960243: zimlib FTBFS with ICU 67.1

2020-06-07 Thread Peter Green
I downloaded the build logs  and filtered them to show the missing symbols that were not already marked as optional. plugwash@thinkpad:~$ wget -O zimlib.log 'https://buildd.debian.org/status/fetch.php?pkg=zimlib=amd64=4.0.4-5%2Bb1=1591384179=0' plugwash@thinkpad:~$ html2text -width 10

  1   2   3   4   5   6   7   8   9   10   >