Bug#1075979: [Help] molds: FTBFS with mpich as default MPI provider: /usr/bin/ld: cannot find -lmpi_cxx: No such file or directory

Le Thu, Nov 07, 2024 at 08:12:22PM +0100, Andreas Tille a écrit : > Control: tags -1 help > Thanks > > Hi, > > today molds (from Debichem team) came up as candidate for the Bug of the > Day[1]. I considered bug #1075979 easy to fix by simply adding > libopenmpi-dev to Build-Depends since > > $

Bug#1027776: mlucas: FTBFS on arm64: fermat-number feature known broken on arm64

On Mon, Jan 02, 2023 at 10:57:35PM -0800, Steve Langasek wrote: > Package: mlucas > Version: 20.1.1-1 > Severity: serious > Tags: patch > Justification: FTBFS > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu lunar ubuntu-patch > > Hi Alex, > > In addition to bug #1014547 causing ml

Bug#1084045: mlucas: FTBFS: /bin/bash: line 6: 190871 Segmentation fault ${dir}$tst - FAIL: tests/self-test

On Sat, Oct 05, 2024 at 01:50:14AM +0200, Santiago Vila wrote: > El 4/10/24 a las 20:37, Bill Allombert escribió: > > > The test suite works with 3th generation AMD EPYC processorss, > > > but fails with 4th generation. > > > > Ah! Does the VM set /proc/cpuinfo

Bug#1084045: mlucas: FTBFS: /bin/bash: line 6: 190871 Segmentation fault ${dir}$tst - FAIL: tests/self-test

On Fri, Oct 04, 2024 at 08:05:31PM +0200, Santiago Vila wrote: > Ok, after some tests this is what seems to happen: > > The test suite works with 3th generation AMD EPYC processorss, > but fails with 4th generation. Ah! Does the VM set /proc/cpuinfo correctly ? Some years ago, I have seen problem

Bug#1084045: mlucas: FTBFS: /bin/bash: line 6: 190871 Segmentation fault ${dir}$tst - FAIL: tests/self-test

On Fri, Oct 04, 2024 at 06:31:09PM +0200, Bill Allombert wrote: > Hello Santiago, > > The package build on my laptop, on barriere.debian.org and on the > Debian buildd, so it is fair to say that I cannot reproduce this bug. > > Does it FTFBS also on the real hardware ? >

Bug#1084045: mlucas: FTBFS: /bin/bash: line 6: 190871 Segmentation fault ${dir}$tst - FAIL: tests/self-test

On Fri, Oct 04, 2024 at 02:59:06PM +0200, Santiago Vila wrote: > Package: src:mlucas > Version: 20.1.1-1.2 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > (I'm adding Bill to X-debbugs-Cc, since he did the last NMU) Thanks! > During a rebuild of all packages in unstable, your package

Bug#1081082: mlucas: FTBFS: upstream/src/radix144_main_carry_loop.h:144:29: error: assignment to ‘vec_dbl *’ {aka ‘struct double_x4 *’} from incompatible pointer type ‘vec_dbl **’ {aka ‘struct double_

On Sun, Sep 08, 2024 at 01:52:58AM +0200, Santiago Vila wrote: > Package: src:mlucas > Version: 20.1.1-1 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > During a rebuild of all packages in unstable, your package failed to build: > >

Bug#1069027: Fixed upstreamo

On Fri, May 31, 2024 at 10:56:54AM +0200, Thomas Viehmann wrote: > This is fixed upstream in Jupyter Notebook 6.5.6 per > https://github.com/jupyter/notebook/issues/7054 Will someone from the python team will fix this or should I prepare a minimal NMU with the patch applied ? Cheers, -- Bill.

Bug#1063210: pari: NMU diff for 64-bit time_t transition

On Mon, Feb 05, 2024 at 02:43:30PM -0300, Lucas Kanashiro wrote: > Source: pari > Version: 2.15.4-2 > Severity: serious > Tags: patch pending sid trixie > Justification: library ABI skew on upgrade > User: debian-...@lists.debian.org > Usertags: time-t > > NOTICE: these changes must not be uploade

Bug#1061972: gap: NMU diff for 64-bit time_t transition

On Thu, Feb 01, 2024 at 04:07:38PM +0100, Lukas Märdian wrote: > thanks for the heads-up! > The same debdiff should apply to the version in unstable (4.12.1). > We'll make sure to NMU the version from unstable. > > Waiting for libgap.so.9 would also be an option, if timing works out. Fortunately

Bug#1061972: gap: NMU diff for 64-bit time_t transitiono

On Thu, Feb 01, 2024 at 04:30:40PM +0100, Lukas Märdian wrote: > Am 01.02.24 um 16:13 schrieb Bill Allombert: > > On Thu, Feb 01, 2024 at 04:07:38PM +0100, Lukas Märdian wrote: > > > Hi Bill, > > > > > > thanks for the heads-up! > > > The same de

Bug#1061972: gap: NMU diff for 64-bit time_t transition

On Thu, Feb 01, 2024 at 04:07:38PM +0100, Lukas Märdian wrote: > Hi Bill, > > thanks for the heads-up! > The same debdiff should apply to the version in unstable (4.12.1). > We'll make sure to NMU the version from unstable. How do you plan to make sure libgap8t64 actually use 64-bit time_t ? This

Bug#1061972: gap: NMU diff for 64-bit time_t transition

On Tue, Jan 30, 2024 at 03:18:23PM +, Lukas Märdian wrote: > Source: gap > Version: 4.12.1-2 > Severity: serious > Tags: patch pending > Justification: library ABI skew on upgrade > User: debian-...@lists.debian.org > Usertags: time-t > > Dear maintainer, > > To ensure that inconsistent combi

Bug#1060164: libxeus9 incompatible with nlohmann::json_abi_v3_11_3

Package: xeus-dev Version: 3.1.3-1 Severity: serious Dear Debian Science maintainers, I have trouble with linking with libxeus9 since I upgraded nlohmann-json3-dev to 3.11.3-1. It seems to me nlohmann-json3-dev 3.11.3-1. is changing the API of libxeus9 in an incompatible way. /lib/x86_64-linux

Bug#1041207: debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE

On Sun, Jul 16, 2023 at 12:42:11PM +0100, Luca Boccassi wrote: > If there is somebody who's ignoring things, that would be yourself, > given this change has been not only been explicitly requested, but even > provided _BY_ the CTTE, as you would have easily found out if you > actually went and chec

Bug#1033065: release-notes: i386 notes should specify minimum CPU requirements

On Mon, Mar 20, 2023 at 12:05:24PM +, James Addison wrote: > On Mon, 20 Mar 2023 13:31:37 +0800, pabs wrote: > > Perhaps lintian could add classification tags for the relevant CPU > > instructions and then the i386 port could have extra autopkgtest nodes > > that only process the packages detec

Bug#1031315: libjpeg9: libjpeg.so.9* missing

On Wed, Feb 15, 2023 at 05:45:26AM +0800, Roy Clark (kralcyor) wrote: > Package: libjpeg9 > Version: 1:9d-1.1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > /usr/lib/*/{libjpeg.so.9,libjpeg.so.9.4.0} are missing in the package, making > it completely unusabl

Bug#999306: libjpeg6b: diff for NMU version 1:6b2-3.1

On Thu, Nov 03, 2022 at 04:12:46PM -0300, Marcos Talau wrote: > Control: tags 999306 + patch > Control: tags 999306 + pending > > Dear maintainer, > > I've prepared an NMU for libjpeg6b (versioned as 1:6b2-3.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it lon

Bug#1020456: cypari2 FTBFS with PARI 2.15.0

On Fri, Oct 28, 2022 at 07:26:09PM +, Tobias Hansen wrote: > Thanks! I will apply the patch once the pari version with the other fixes is > uploaded. Great! I uploaded it today (pari 2.15.1~pre1-1). I hope it will be OK. Cheers, -- Bill. Imagine a large red swirl here.

Bug#1020456: cypari2 FTBFS with PARI 2.15.0

On Wed, Oct 05, 2022 at 10:41:58PM +0200, Bill Allombert wrote: > On Wed, Sep 21, 2022 at 11:57:40PM +0300, Adrian Bunk wrote: > > Testing cypari2.gen > > ** > > File > > "/<>/.pybui

Bug#1020436: giac FTBFS with PARI 2.15.0

On Wed, Oct 19, 2022 at 09:27:23AM +, Tobias Hansen wrote: > I tried rebuilding with this patch from sagemath: Thanks! > |diff --git a/src/pari.cc b/src/pari.cc index 76ce8e1..50d08ab 100644 --- > a/src/pari.cc +++ b/src/pari.cc @@ -40,6 +40,13 @@ using namespace std; > #ifdef HAVE_LIBPARI

Bug#1020576: please update sage for pari 2.15.0 and gap 4.12.0

On Mon, Oct 17, 2022 at 08:44:52AM +, Tobias Hansen wrote: > Control: block -1 by 1020436 1020456 > > Before sagemath can be fixed, cypari2 and giac have to be built against pari > 2.15. OK, is there someone taking care of giac ? Cheers, -- Bill. Imagine a large red swirl here.

Bug#1020456: cypari2 FTBFS with PARI 2.15.0

On Wed, Sep 21, 2022 at 11:57:40PM +0300, Adrian Bunk wrote: > Testing cypari2.gen > ** > File > "/<>/.pybuild/cpython3_3.10_cypari2/build/cypari2/gen.cpython-310-x86_64-linux-gnu.so", > line ?, in cypari2.gen.Gen.__complex__ > F

Bug#1020456: cypari2 FTBFS with PARI 2.15.0

On Wed, Sep 21, 2022 at 11:57:40PM +0300, Adrian Bunk wrote: > Source: cypari2 > Version: 2.1.2-2 > Severity: serious > Tags: ftbfs bookworm sid > > https://buildd.debian.org/status/logs.php?pkg=cypari2&ver=2.1.2-2%2Bb3 > > Differences (ndiff with -expected +actual): > Traceback (most recen

Bug#1020436: giac FTBFS with PARI 2.15.0

On Wed, Sep 21, 2022 at 09:01:51PM +0300, Adrian Bunk wrote: > Source: giac > Version: 1.9.0.19+dfsg2-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/logs.php?pkg=giac&ver=1.9.0.19%2Bdfsg2-1%2Bb1 > > ... > pari.cc: At global scope: > pari.cc:752:17: error: typedef ‘giac::

Bug#1020437: clisp FTBFS with PARI 2.15.0

On Wed, Sep 21, 2022 at 09:23:00PM +0300, Adrian Bunk wrote: > Source: clisp > Version: 1:2.49.20210628.gitde01f0f-2 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/logs.php?pkg=clisp&ver=1%3A2.49.20210628.gitde01f0f-2%2Bb1 To build with PARI 2.15.0-2, please apply the atta

Bug#1001956: popcon: gpg: 5B1A07804DD558242CF5538215A07BA5233E3E85: skipped: unusable public key

On Sun, Dec 19, 2021 at 01:49:30PM +, Thorsten Glaser wrote: > Package: popularity-contest > Version: 1.71 > Severity: grave > Justification: renders package unusable > > got a cron mail: > > Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts > --report /etc/cron.daily ) > > /e

Bug#999319: popularity-contest: missing required debian/rules targets build-arch and/or build-indep

On Tue, Nov 09, 2021 at 10:28:20PM +0100, Lucas Nussbaum wrote: > Source: popularity-contest > Version: 1.73 > Severity: important > Justification: Debian Policy section 4.9 > Tags: bookworm sid > User: debian...@lists.debian.org > Usertags: missing-build-arch-indep > > Dear maintainer, > > Your

Bug#999172: toppler: missing required debian/rules targets build-arch and/or build-indep

On Tue, Nov 09, 2021 at 10:28:21PM +0100, Lucas Nussbaum wrote: > Source: toppler > Version: 1.1.6-3 > Severity: important > Justification: Debian Policy section 4.9 > Tags: bookworm sid > User: debian...@lists.debian.org > Usertags: missing-build-arch-indep > > Dear maintainer, > > Your package

Bug#993722: FTBFS: tempfile: not found

On Sun, Sep 05, 2021 at 04:34:08PM +0200, Samuel Thibault wrote: > Package: gap > Version: 4.11.0-4 > Severity: serious > Justification: FTBFS > > Hello, > > gap currently FTBFS in unstable because tempfile was removed from > debianutils. You can probably use mktemp instead. Thanks for reporting

Bug#993665: debianutils: tempfile still required in printer-driver-pnm2ppa

On Sat, Sep 04, 2021 at 10:41:37PM +0900, Norbert Preining wrote: > Package: debianutils > Version: 5.4-3 > Severity: critical > Justification: breaks unrelated software > > The tempfile saga is not over. It might be wise grepping through the > maintainer scripts of all packages. > > printer-driv

Bug#975211: gap-polycyclic: FTBFS: test failed

reassign 975211 gap-alnuth notfound 975211 2.15.1-1 found 975211 3.1.2-1 merge 975211 975216 quit On Thu, Nov 19, 2020 at 10:52:30AM +0100, Lucas Nussbaum wrote: > Source: gap-polycyclic > Version: 2.15.1-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: f

Bug#973588: Update from pari 2.11 to 2.13 breaks giac compilation

On Sat, Nov 07, 2020 at 02:32:41PM +0100, Julien Puydt wrote: > Le samedi 07 novembre 2020 à 11:05 +0100, Bill Allombert a écrit : > > Too late for that, I'll close by hand. Thanks! > > > but still, crashing is pretty bad : it should detect > > > the value is

Bug#973588: Update from pari 2.11 to 2.13 breaks giac compilation

On Sat, Nov 07, 2020 at 10:29:18AM +0100, Julien Puydt wrote: > Le jeudi 05 novembre 2020 à 19:12 +0100, Bill Allombert a écrit : > > On Mon, Nov 02, 2020 at 09:57:07AM +0100, Bill Allombert wrote: > > > This means 512000 is not sufficient. This is a fatal error. > >

Bug#973588: Update from pari 2.11 to 2.13 breaks giac compilation

On Mon, Nov 02, 2020 at 09:57:07AM +0100, Bill Allombert wrote: > On Mon, Nov 02, 2020 at 08:54:02AM +0100, Julien Puydt wrote: > > Package: libpari-dev > > Version: 2.13.0-2 > > Severity: grave > > > > The last pari upload broke giac on amd64, arm64 and mipsel

Bug#973588: Update from pari 2.11 to 2.13 breaks giac compilation

On Mon, Nov 02, 2020 at 08:54:02AM +0100, Julien Puydt wrote: > Package: libpari-dev > Version: 2.13.0-2 > Severity: grave > > The last pari upload broke giac on amd64, arm64 and mipsel : Hello Julien, > https://buildd.debian.org/status/fetch.php?pkg=giac&arch=amd64&ver=1.6.0.25%2Bdfsg1-2%2Bb1&s

Bug#971203: dpkg-source cause gap-atlasrep to FTBFS for no reason

severity 971203 important quit > > root (to '/tmp/gap-atlasrep-2.1.0') > > E: Unpack command 'dpkg-source --no-check -x gap-atlasrep_2.1.0-2.dsc' > > failed. > > > > There is no rationale to reject such a symlink which does not point > > _outside_ the source root, but _to_ the source root. > > Th

Bug#971203: dpkg-source cause gap-atlasrep to FTBFS for no reason

On Mon, Sep 28, 2020 at 05:19:33AM +0200, Guillem Jover wrote: > Hi! > > On Sun, 2020-09-27 at 22:53:13 +0200, Bill Allombert wrote: > > On Sun, Sep 27, 2020 at 08:58:00PM +0200, Lucas Nussbaum wrote: > > > During a rebuild of all packages in sid, your package failed

Bug#971203: dpkg-source cause gap-atlasrep to FTBFS for no reason

reassign 971203 dpkg-dev severity grave retitle dpkg-source cause gap-atlasrep to FTBFS quit On Sun, Sep 27, 2020 at 08:58:00PM +0200, Lucas Nussbaum wrote: > Source: gap-atlasrep > Version: 2.1.0-2 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-202

Bug#971203: gap-atlasrep: FTBFS: dpkg-source: error: pathname '/<>/debian/gaproot/pkg/AtlasRep' points outside source root (to '/<>')

On Sun, Sep 27, 2020 at 08:58:00PM +0200, Lucas Nussbaum wrote: > > gpgv: unknown type of key resource 'trustedkeys.kbx' > > gpgv: keyblock resource '/tmp/dpkg-verify-sig.DGPbPdCb/trustedkeys.kbx': > > General error > > gpgv: Signature made Sat Apr 4 15:09:48 2020 UTC > > gpgv:usi

Bug#959378: gap-guava-bin: please update for new GAP ABI

Package: gap-guava-bin Version: 3.15+ds-1 Severity: serious Dear Debian Science Maintainers, Please update gap-guava for the new GAP ABI. 1) GAP 4.11.0 includes libgap7, libgap-dev as a normal Debian shared library package. 2) There is now an officially supported ABI for the GAP kernel. the cur

Bug#958495: Fwd: gap-io: please update for new GAP ABI

On Thu, Apr 30, 2020 at 10:35:49AM +0400, Jerome BENOIT wrote: > Dear Bill, thanks for your message. Hello Jerome > I understand that GAP comes now with an official ABI. Yes, one for gap-core which is gap-kernel-7, and one for libgap which is libgap7, but they should be compatible. > Currently

Bug#958802: gap-float: please update for new GAP ABI

Package: gap-float Version: 0.9.1+ds-5 Severity: serious Dear Debian Science Maintainers, Please update gap-float for the new GAP ABI. 1) GAP 4.11.0 includes libgap7, libgap-dev as a normal Debian shared library package. 2) There is now an officially supported ABI for the GAP kernel. the curren

Bug#958495: gap-io: please update for new GAP ABI

Package: gap-io Version: 4.7.0+ds-1 Severity: serious Dear Debian Science Maintainers, Please update gap-io for the new GAP ABI. 1) GAP 4.11.0 includes libgap7, libgap-dev as a normal Debian shared library package. 2) There is now an officially supported ABI for the GAP kernel. the current kern

Bug#923698: gcc-mingw-w64 miscompiles PARI

On Sun, Apr 12, 2020 at 02:41:00PM +0200, Ivo De Decker wrote: > > I very much like to see a chaangelog that tell what changed betwee 8.2 > > and 8.3 that could have fixed this. > > So I guess the current version in testing is ok, and the bug can be closed > there? > > If it works on gcc 8.3, doe

Bug#923698: gcc-mingw-w64 miscompiles PARI

On Sun, Apr 12, 2020 at 12:02:38PM +0200, Ivo De Decker wrote: > Hi Stephen, Bill, > > While looking at RC bugs that have been open for I while, I noticed this one. > > On Thu, Mar 07, 2019 at 09:07:15AM +0100, Stephen Kitt wrote: > > Subject: Re: Bug#923698: gcc-mingw-w64 miscompiles PARI > > [

Bug#955751: gap-atlasrep: package is broken

On Sat, Apr 04, 2020 at 04:42:57PM +0200, Tobias Hansen wrote: > Source: gap-atlasrep > Version: 2.1.0-1 > Severity: grave > > Hi Bill, > > during a test build of sage I noticed that the newly updated gap-atlasrep > package seems to be seriously broken. Trying the first commands from the > atla

Bug#932356: autotest fail with gap 4.10.2

Source: gap-guava Version: 3.14+ds-1 Severity: serious Dear Debian Science Maintainers, gap-guava 3.14+ds-1 is failing the autotest with gap 4.10.2. Please rebuild the package for the new GAP version. Cheers, -- Bill. Imagine a large red swirl here.

Bug#928415: tagging 928417

On Sat, May 04, 2019 at 08:54:27AM +0200, Salvatore Bonaccorso wrote: > tags 928417 - security The fact that this bug allows Mozilla to disable remotely security extensions like noscript is a major security issue. When noscript get deactivated, firefox should default to disabling javascript compl

Bug#923698: gcc-mingw-w64 miscompiles PARI

On Thu, Mar 07, 2019 at 09:07:15AM +0100, Stephen Kitt wrote: > Hi Bill, > > On Mon, 4 Mar 2019 00:39:00 +0100, Bill Allombert wrote: > > Since the upgrade to 8.2.0-17, gcc-mingw-w64-x86-64 miscompiles PARI/GP. > > <https://pari.math.u-bordeaux.fr> > > >

Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

On Thu, Jun 15, 2017 at 03:16:17PM +0200, Cyril Brulebois wrote: > Julien Cristau (2017-06-15): > > It sounds like openjdk-8 added two Breaks recently, one or both of > > which are causing trouble, and none of which fix anything as bad as > > this. So I think we should remove the Breaks on tzdata

Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

On Sun, Jun 11, 2017 at 11:13:05AM +0200, Cyril Brulebois wrote: > Package: upgrade-reports > Severity: critical > Justification: makes upgrade from stable abort > > [ X-D-Cc: > debian-rele...@lists.debian.org > pkg-java-maintain...@lists.alioth.debian.org > pkg-gnome-maintain...@lists.aliot

Bug#860648: gap-radiroot: FTBFS on i386: not enough memory during build on i386

severity 860648 normal quit On Wed, Apr 19, 2017 at 09:37:57AM +0200, Lucas Nussbaum wrote: > Source: gap-radiroot > Version: 2.7-2 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20170418-i386 qa-ftbfs > Justification: FTBFS in stretch on i386 > > H

Bug#833695: [Popcon-developers] Bug#833695: popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz containso

On Mon, Aug 08, 2016 at 01:07:18AM +0200, Chris Lamb wrote: > Package: popularity-contest > Version: 1.64 > Severity: serious > X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org > > Hi, > > Since (at least) 07-Aug-2016 14:04, the all-popcon-results.txt.gz file > contains an invalid line:

Bug#828777: gap-alnuth: FTBFS: Input is: EquationOrderBasis( F ); [..] Expected output [..]

On Mon, Jun 27, 2016 at 07:54:58PM +0100, Chris Lamb wrote: > Source: gap-alnuth > Version: 3.0.0-3 > Severity: serious > Justification: fails to build from source > User: reproducible-bui...@lists.alioth.debian.org > Usertags: ftbfs > X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org > >

Bug#827302: v4l-utils: FTBFS: jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'

On Wed, Jun 15, 2016 at 02:09:05PM +0200, Gregor Jasny wrote: > Hello Bill and Ondřej, > > Do you know how to properly detect jpeg_mem_src presence in libjpeg(turbo)? > > Since the transition to jpegturbo my package FTBFS: > > On 14/06/16 20:42, Chris Lamb wrote: > > In file included from jpeg.

Bug#823227: libjpeg8: Please keep out of stretch

On Mon, May 02, 2016 at 10:03:58PM +0200, Laurent Bigonville wrote: > >I am sure you mean well but the CTTE decision does not require the > >removal of libjpeg62/libjpeg8 from stretch. > Well nothing in the archive depends on these packages and the > release/security team is usually not happy havin

Bug#819985: gap-dev: unusable headers (missing config.h)

severity 819985 important thanks On Mon, Apr 04, 2016 at 05:11:01PM +0200, Julien Cristau wrote: > Package: gap-dev > Version: 4r7p9-1 > Severity: serious > > $ echo '#include ' | cpp > # 1 "" > # 1 "" > # 1 "" > # 1 "/usr/include/stdc-predef.h" 1 3 4 > # 1 "" 2 > # 1 "" > # 1 "/usr/include/gap/s

Bug#819985: gap-dev: unusable headers (missing config.h)o

On Mon, Apr 04, 2016 at 05:11:01PM +0200, Julien Cristau wrote: > Package: gap-dev > Version: 4r7p9-1 > Severity: serious > > $ echo '#include ' | cpp > # 1 "" > # 1 "" > # 1 "" > # 1 "/usr/include/stdc-predef.h" 1 3 4 > # 1 "" 2 > # 1 "" > # 1 "/usr/include/gap/system.h" 1 3 4 > In file included

Bug#819985: gap-dev: unusable headers (missing config.h)

On Mon, Apr 04, 2016 at 06:07:30PM +0200, Julien Cristau wrote: > On Mon, Apr 4, 2016 at 17:55:40 +0200, Bill Allombert wrote: > > > On Mon, Apr 04, 2016 at 05:11:01PM +0200, Julien Cristau wrote: > > > Package: gap-dev > > > Version: 4r7p9-1 > > > Severity

Bug#819985: gap-dev: unusable headers (missing config.h)

On Mon, Apr 04, 2016 at 05:11:01PM +0200, Julien Cristau wrote: > Package: gap-dev > Version: 4r7p9-1 > Severity: serious > > $ echo '#include ' | cpp > # 1 "" > # 1 "" > # 1 "" > # 1 "/usr/include/stdc-predef.h" 1 3 4 > # 1 "" 2 > # 1 "" > # 1 "/usr/include/gap/system.h" 1 3 4 > In file included

Bug#812663: debian-policy: FTBFS - nsgmls: Command not found

On Mon, Jan 25, 2016 at 09:17:40PM +0100, Bill Allombert wrote: > On Mon, Jan 25, 2016 at 07:00:51PM +, Michael Tautschnig wrote: > > Package: debian-policy > > Version: 3.9.6.1 > > Severity: serious > > Usertags: goto-cc > > > > During a rebuild of al

Bug#812663: debian-policy: FTBFS - nsgmls: Command not found

On Mon, Jan 25, 2016 at 07:00:51PM +, Michael Tautschnig wrote: > Package: debian-policy > Version: 3.9.6.1 > Severity: serious > Usertags: goto-cc > > During a rebuild of all Debian packages in a clean sid chroot (using > cowbuilder > and pbuilder) the build failed with the following error.

Bug#799063: popularity-contest: fails to install: popularity-contest.postinst: cannot create /etc/cron.d/popularity-contest: Directory nonexistent

forcemerge 798941 799063 quit On Tue, Sep 15, 2015 at 03:58:09PM +0200, Andreas Beckmann wrote: > Package: popularity-contest > Version: 1.63 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package failed to insta

Bug#787919: zynaddsubfx-dssi: ship file in /usr/lib64

Package: zynaddsubfx-dssi Version: 2.4.3-4 Severity: serious Hello Debian Multimedia Maintainers, on amd64, zynaddsubfx-dssi include a file in /usr/lib64 /usr/lib64/dssi/libzynaddsubfx_dssi.so Packages must not use /usr/lib64, but either /usr/lib or the correct multiarch path. Cheers, -- Bill.

Bug#773232: libjpeg-progs: Try to override files from other package at upgradeo

On Mon, Dec 15, 2014 at 09:41:28PM +0100, Vincent Danjean wrote: > Package: libjpeg-progs > Version: 1:9a-2 > Severity: grave > Justification: renders package unusable > > On upgrade, libjpeg-progs tries to override a file from the (old) > libjpeg-turbo-progs (see the apt log below). > Even if

Bug#772869: gap-core: Trigger cycle causes dpkg to fail processing

On Thu, Dec 11, 2014 at 09:44:38PM +0100, Guillem Jover wrote: > Package: gap-core > Version: 4r7p5-1 > Severity: serious > > Hi! > > This package can get involved in a trigger cycle. The problem is that > it installs interests on /usr/share/gap with files there provided by > gap-gapdoc and gap-l

Bug#769219: upload of policy 3.9.6.1 to fix Bug#769219

On Sat, Nov 15, 2014 at 12:19:32PM +0100, David Bremner wrote: > I have only tested the first one. In all cases build-depends may need > adjusting. I also noticed that the same hacking out of TeX stuff I did > to README.org is needed for Process.org. Thank for the tip, this resolve the remaining

Bug#769219: function moved

On Thu, Nov 13, 2014 at 11:10:30PM +0100, David Bremner wrote: > Rob Browning writes: > > > Bill Allombert writes: > > > >> What to do for ascii : > >> > >> emacs24 --batch -Q -l ./README-css.el -l org -l org-ascii > >> --visit Process.org

Bug#769219: function moved

On Thu, Nov 13, 2014 at 11:10:30PM +0100, David Bremner wrote: > Rob Browning writes: > > > Bill Allombert writes: > > > >> What to do for ascii : > >> > >> emacs24 --batch -Q -l ./README-css.el -l org -l org-ascii > >> --visit Process.org

Bug#769219: function moved

On Wed, Nov 12, 2014 at 09:46:28PM +0100, David Bremner wrote: > Bill Allombert writes: > >> That function is now in ox-html.el > > > > Are you sure ? > > grep org-export-as-html-batch > > /usr/share/emacs/site-lisp/org-mode/ox-html.el > > does not re

Bug#769219: function moved

On Wed, Nov 12, 2014 at 07:40:14PM +0100, David Bremner wrote: Hello David, Thanks for your help! > That function is now in ox-html.el Are you sure ? grep org-export-as-html-batch /usr/share/emacs/site-lisp/org-mode/ox-html.el does not return anything. > Maybe loading that explicitly (as well

Bug#769273: bsdutils: Dependency on libsystemd0 violates policy

On Wed, Nov 12, 2014 at 03:04:56PM +0100, Andreas Henriksson wrote: > Hello Tim Wootton, release-team, et.al.! > > Thanks for your bug report. > > On Wed, Nov 12, 2014 at 11:00:16AM +, Tim Wootton wrote: > > Package: bsdutils > > Version: 1:2.25.2-2 > > Severity: serious > > Justification: Po

Bug#769219: debian-policy: FTBFS in jessie: emacs24 fails

On Wed, Nov 12, 2014 at 08:52:21AM +0100, Lucas Nussbaum wrote: > Hi, > > During a rebuild of all packages in jessie (in a jessie chroot, not a > sid chroot), your package failed to build on amd64. > > Relevant part (hopefully): > > rm menu-policy.html/index.html perl-policy.html/index.html > >

Bug#766353: [libjpeg-progs] Conflicts with libjpeg-turbo-progs 1:1.3.1-3

On Sun, Oct 26, 2014 at 07:58:44AM +0100, Helge Kreutzmann wrote: > Hello, > I just ran into this as well. > > Why? > > a) On my machine, which run stable up to about ~1.5 month ago I never >explicitly installed libjpeg-turbo-progs, so stable users who upgrade >are most likly affected. >

Bug#766353: [libjpeg-progs] Conflicts with libjpeg-turbo-progs 1:1.3.1-3

On Sat, Oct 25, 2014 at 05:57:39PM +0200, Michael Banck wrote: > severity 766353 serious > thanks > > On Wed, Oct 22, 2014 at 04:30:54PM +0200, Bill Allombert wrote: > > On Wed, Oct 22, 2014 at 03:20:41PM +0200, Rafael Belmonte wrote: > > > Package: libjpeg-

Bug#764318: libjpeg-progs still needs conflict with libjpeg-turbo-progs

On Wed, Oct 22, 2014 at 11:12:24AM +0100, Ben Harris wrote: > Control: clone -1 -2 > Control: reassign -2 libjpeg-turbo-progs/1:1.3.1-3 > Control: fixed -2 libjpeg-turbo-progs/1:1.3.1-6 > Control: reassign -1 libjpeg-progs/1:9a-2 > > It looks like it's necessary for the new libjpeg-progs to includ

Bug#764318: don't see any way out of the libjpeg issue :( ?

On Wed, Oct 22, 2014 at 02:22:51PM +0530, shirish शिरीष wrote: > $ sudo aptitude install libjpeg8 libjpeg8-dev libdirectfb-dev > The following NEW packages will be installed: > libjpeg-dev{ab} libjpeg62-turbo-dev{ab} > The following packages will be upgraded: > libjpeg8 libjpeg8-dev{b} > 2 pack

Bug#764322: closed by Ondřej Surý (Bug#764322: fixed in libjpeg-turbo 1:1.3.1-6)

On Tue, Oct 07, 2014 at 09:24:36AM +, Debian Bug Tracking System wrote: > Changes: > libjpeg-turbo (1:1.3.1-6) unstable; urgency=medium > . >* Changes Breaks: libjpeg-progs to Conflicts: libjpeg-progs and drop > Replaces: libjpeg-progs (Closes: #764322) For what it is worth, the Con

Bug#763360: closed by Ondřej Surý

On Tue, Oct 07, 2014 at 10:31:45AM +0200, Ondřej Surý wrote: > On Mon, Oct 6, 2014, at 21:14, Bill Allombert wrote: > > > Version: 1:1.3.1-4 > > > > > > My understanding is that this bug can be now closed as > > > the libjpeg-progs are not built from src:li

Bug#764318: libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs

On Tue, Oct 07, 2014 at 10:39:20AM +0200, Ondřej Surý wrote: > Control: clone -1 -2 > Control: reassign -2 libjpeg-turbo-progs > Control: found -2 1:1.3.1-3 > > Vincent, > > in fact the libjpeg-turbo-progs also had incorrect "Breaks: > libjpeg-progs" instead of proper "Conflicts: libjpeg-progs",

Bug#763360: closed by Ondřej Surý (Re: Bug#763360: libjpeg-turbo is hijacking binaries from other source packages)

On Mon, Oct 06, 2014 at 11:54:06AM +, Debian Bug Tracking System wrote: > Date: Mon, 06 Oct 2014 13:52:42 +0200 > From: Ondřej Surý > To: Bill Allombert , Andreas Barth > Cc: Emilio Pozuelo Monfort , 763360-d...@bugs.debian.org > Subject: Re: Bug#763360: libjpeg-turbo is hij

Bug#763360: Bug#754988: Bug#763360: libjpeg-turbo is hijacking binaries from other source packages

On Fri, Oct 03, 2014 at 03:03:09PM +0200, Andreas Barth wrote: > I hope we could leave it as that for the upload - nobody has a time > machine to undo the upload, but we could try to make it better now and > discuss where we should go. Ok, let's focus on libjpeg-progs, since I do not think there i

Bug#763360: Bug#754988: Bug#763360: libjpeg-turbo is hijacking binaries from other source packages

On Fri, Oct 03, 2014 at 12:37:09PM +0200, Emilio Pozuelo Monfort wrote: > >>seemed like the sensible thing to do, and I didn't see any problem > >>with the proposed plan. After all, libjpeg62 had been long > >>deprecated in favor of libjpeg8. Neither of us thought you would > >>care about libjpeg62

Bug#763360: Bug#754988: Bug#763360: libjpeg-turbo is hijacking binaries from other source packages

On Fri, Oct 03, 2014 at 01:41:02AM +0200, Emilio Pozuelo Monfort wrote: > On 30/09/14 11:32, Bill Allombert wrote: > >On Mon, Sep 29, 2014 at 08:55:16PM +0200, Ondřej Surý wrote: > >>Bill, > >> > >>I am very sorry that I have not Cced everything related to the

Bug#763605: libjpeg-turbo-progs: Please don't drop libjpeg-progs dummy package

On Thu, Oct 02, 2014 at 09:53:54PM +0200, Ondřej Surý wrote: > It has been removed in 1:1.3.1-4 as I said it would be. > > https://tracker.debian.org/news/574328 But libjpeg-turbo is still hijacking libjpeg62 as far as I can see. I am not sure why the old libjpeg-progs 1:1.3.1-3 binaries are sti

Bug#763605: libjpeg-turbo-progs: Please don't drop libjpeg-progs dummy package

On Thu, Oct 02, 2014 at 07:39:28PM +0200, Santiago Vila wrote: > On Wed, 1 Oct 2014, Ondřej Surý wrote: > > > This should be remedied by src:libjpeg9 providing libjpeg-progs as > > requested > > by Bill Allombert, the libjpeg6b/8/9 maintainer. > > Ok, is that goi

Bug#763605: libjpeg-turbo-progs: Please don't drop libjpeg-progs dummy package

On Thu, Oct 02, 2014 at 02:34:10AM +0200, Santiago Vila wrote: > On Wed, Oct 01, 2014 at 12:59:50PM +0200, Ondřej Surý wrote: > > This should be remedied by src:libjpeg9 providing libjpeg-progs as > > requested > > by Bill Allombert, the libjpeg6b/8/9 maintainer. > > &

Bug#763360: libjpeg-turbo is hijacking binaries from other source packages

On Mon, Sep 29, 2014 at 08:55:16PM +0200, Ondřej Surý wrote: > Bill, > > I am very sorry that I have not Cced everything related to the > libjpeg-transition > to you. I have honestly believed that you and everyone else involved was > following the transition plan as mentioned in #717076#225. As fo

Bug#763360: libjpeg-turbo is hijacking binaries from other source packages

Source: libjpeg-turbo Version: 1:1.3.1-3 Severity: serious Dear maintainers, libjpeg-turbo is hijacking binaries from other source packages: libjpeg-progs : provided by libjpeg8 libjpeg62 libjpeg62-dbg libjpeg62-dev: provided by libjpeg6b Please correct this as soon as possible. Cheers, -- Bi

Bug#753999: debian-policy: please switch to emacs24

On Mon, Sep 08, 2014 at 01:38:07PM -0500, Rob Browning wrote: > Gabriele Giacone <1o5g4...@gmail.com> writes: > > > mass bug filer on behalf of Rob Browning, emacs maintainer > > --- debian/control.orig 2014-07-06 13:10:21.364467678 +0200 > > +++ debian/control 2014-07-06 13:10:36.516651745 +

Bug#754486: performous: FTBFS on amd64

Package: performous Version: 0.7.0-3 Severity: serious Hello Debian Games Team, performous FTBFS on amd64. The full buildlog is available at [ 40%] Building CXX object game/CMakeFiles/performous.dir/ffmpeg.cc.o cd /tmp/buildd/p

Bug#754484: lightspark: FTBFS on amd64

Package: lightspark Version: 0.7.2-3.1 Severity: serious Hello Debian Flash Maintainers, lightspark FTBFS on amd64. The full buildlog is available at [ 40%] Building CXX object src/CMakeFiles/spark.dir/scripting/abc.cpp.o cd /tmp/bui

Bug#754467: hdf-eos4: FTBFS on amd64

Package: hdf-eos4 Version: 2.17v1.00.dfsg.1-5 Severity: serious Hello Alastair, hdf-eos4 FTBFS on amd64. The full buildlog is available at ./SubsetGrid Makefile:1095: recipe for target 'grid_demo' failed make[3]: *** [grid_demo] Segmen

Bug#754465: f-spot: FTBFS on amd64

Package: f-spot Version: 0.8.2-5.1 Severity: serious Hello Debian CLI Applications Team, f-spot FTBFS on amd64. The full buildlog is available at ./FSpot/GroupSelector.cs(430,4): error CS0171: Field `FSpot.GroupSelector.Box.bar' must be

Bug#754456: efl: FTBFS on amd64

Package: efl Version: 1.8.6-2 Severity: serious Hello Debian Pkg-e Team, efl FTBFS on amd64. The full buildlog is available at L: tests/eeze/eeze_suite === Running suite(s): Eeze ERR<3667>:eeze_sensor_fake modules/e

Bug#754209: gambas3: FTBFS on amd64

Package: gambas3 Version: 3.5.2-2 Severity: serious Hello Gambas maintainers, gambas3 FTBFS on amd64. The full buildlog is available at Summary: === configuring in gb.jit (/tmp/buildd/gambas3-3.5.2/gb.jit) ... checking for LLVM - versi

Bug#754182: chromium-browser: FTBFS on amd64

Package: chromium-browser Version: 35.0.1916.153-2 Severity: serious Hello Debian Chromium Maintainers, chromium-browser FTBFS on amd64. The full buildlog is available at The error message is chrome/renderer/pepper/pepper_pdf_

Bug#743328: genus2reduction: obsoleted by libpari 2.7

On Tue, Apr 01, 2014 at 09:42:13PM +0200, Bill Allombert wrote: > Package: genus2reduction > Version: 0.3-2.2 > Severity: serious > > Hello Tim, > > genus2reduction is obsolete. The functionnality has been absorbed by the > libpari library in version 2.7, s

Bug#743328: genus2reduction: obsoleted by libpari 2.7

Package: genus2reduction Version: 0.3-2.2 Severity: serious Hello Tim, genus2reduction is obsolete. The functionnality has been absorbed by the libpari library in version 2.7, specifically the function genus2reduction. Thus there is no point to upgrade the package to build with pari 2.7. Cheers,

  1   2   3   4   5   6   >