Bug#1009242: zfs-dkms: PPC get_user workaround breaks boot on ZFS root

This is a fix released I think.

Bug#998867: debootstrap: --no-merged-usr became a no-op

There are multiple issues reported in a single bug. > This means that I cannot create a Debian chroot from Debian unstable from 10 > years ago from snapshot.debian.org without merged-/usr and thus my chroot > will behave differently as it did back then. > Please re-enable --no-merged-usr so

Bug#988326: libboost-python-dev: Linking against boost_python requires the python version number ex: -lboost_python39

Hi, On Mon, 10 May 2021 at 16:09, Grégory David wrote: > > Package: libboost-python-dev > Version: 1.74.0.3 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: d...@groolot.net > > Dear Maintainer, > >* What led up to the situation? > When I try to compile

Bug#982924: what-is-python: The python-is-python3 and python-dev-is-python3 packages should not exist

In Bullseye release file:/usr/bin/python is not reserved, but intentionally unused. In Bullseye release neither deb:python2 nor deb:python3 packages own /usr/bin/python. This is a Bullseye Release Goal with consensus from all cpythons/pypys/etc interpreter maintainers, modules maintainers, and app

Bug#966765: obs-build: Unversioned Python removal in sid/bullseye

On Sun, 02 Aug 2020 13:18:51 + Matthias Klose wrote: > Package: src:obs-build > Version: 20180831-3 > Severity: serious > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2unversioned > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the

Bug#962348: kig: boost1.67 is being removed from testing

Package: kig Version: 4:20.04.1-1 Severity: serious Hi, boost1.67 is being removed from testing and is transitioning to boost1.71. kig has just now switched from boost1.71 to boost1.67. boost1.67 must not be shipped in testing. Thus I am opening this bug report to prevent kig from migrating.

Bug#945961: xz-utils: FTBFS: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*'

elog 2019-01-28 01:09:34.0 + +++ xz-utils-5.2.4/debian/changelog 2020-04-09 14:13:56.0 +0100 @@ -1,3 +1,10 @@ +xz-utils (5.2.4-1.1) unreleased; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS due to odd targets in debian/rules. Closes: #945961 + + -- Dimitri John

Bug#953106: acorn: Upstream version number is too long and is not user friendly

Source: acorn Version: 6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-14 Severity: serious Dear Maintainer, Although the upstream version number is valid, it is too long, repetitive and doesn't convey any meaning to a user. I literarly

Bug#950675: upstream does support it, but ...

I do wonder if doxygen-latex should instead be replaced by docbook output + docbook2pdf.

Bug#951643: murasaki: FTBFS with new mpi

Package: murasaki Version: 1.68.6-8 Severity: serious murasaki_mpi.cc: In function ‘void mpi_types_init()’: murasaki_mpi.cc:107:14: error: call to ‘MPI_Address’ declared with attribute error: MPI_Address was remov ed in MPI-3.0. Use MPI_Get_address instead. 107 | MPI_Address(,disp); |

Bug#947518: casparcg-server: FTBFS: xf86vmode library not found - required for GLFW

On Fri, 27 Dec 2019 23:14:46 +0100 Andreas Beckmann wrote: > Package: casparcg-server > Version: 2.2.0+dfsg-2 > Severity: serious > Tags: ftbfs > Justification: fails to build from source > > Hi, > > casparcg-server FTBFS in a current sid pbuilder environment: > > CMake Error at

Bug#950688: boost1.71: python autopkgtest fails

This is fixed in unstable, yet is awaiting for gcc-10 to get fixed up and migrated. At the moment cmake tests fail to find libgcc-s1.

Bug#950859: cegui-mk2: FTBFS with boost171 and new cmake and symbol changes

17:48 Olek Wojnar, wrote: > Hi Dimitri, > > Thanks for the bug report, and thanks for the patch! > > On 2/7/20 8:49 AM, Dimitri John Ledkov wrote: > > Package: cegui-mk2 > > Version: 0.8.7-5 > > Severity: serious > > Tags: patch > > Justification: ftbfs

Bug#950859: cegui-mk2: FTBFS with boost171 and new cmake and symbol changes

7/debian/changelog2020-02-06 22:17:46.0 + @@ -1,3 +1,10 @@ +cegui-mk2 (0.8.7-5ubuntu3) focal; urgency=medium + + * Patch CMakeLists for new Boost_VERSION syntax. + * Drop unused boost signals dependencies. + + -- Dimitri John Ledkov Thu, 06 Feb 2020 22:17:46 + + cegui-mk

Bug#915805: NMU of swift-im

On Mon, 20 May 2019 15:34:34 +0200 Mattia Rizzolo wrote: > On Mon, May 20, 2019 at 03:32:26PM +0200, Dominik George wrote: > > as I needed libswiften to build something, I went fixing the most important > > bugs in the package so it at least builds again in current sid. > > > > Would you want me

Bug#950769: pingus: FTBFS with new boost1.71 as signals library is removed

Package: pingus Version: 0.7.6-5 Severity: serious Tags: upstream Justification: ftbfs Dear Maintainer, pingus ftbfs against the new boost1.71 as signals library is removed. There has been a lot of development since 0.7.6 at https://gitlab.com/pingus/pingus and it almost builds fine with only

Bug#950633: morris: FTBFS with boost1.71 deprecated signals library is removed

Package: morris Version: 0.2-5 Severity: serious Tags: ftbfs Dear Maintainer, boost1.71 has removed the deprecated signals library, thus morris cannot be build against the upcoming boost ABI. Given how old the libraries it uses are, maybe we should even remove morris from the archive, as it is

Bug#945840: libboost-python1.67.0 must not drop the Python 2.7 library

On Mon, 6 Jan 2020 at 12:54, Andreas Beckmann wrote: > > On Sat, 4 Jan 2020 16:18:44 + Dimitri John Ledkov > wrote: > > I would be ok to reintroduce boost-python2.7 in experimental only. > > > > On Sat, 4 Jan 2020, 06:45 Giovanni Mascellani, wrote: > > >

Bug#945840: libboost-python1.67.0 must not drop the Python 2.7 library

I would be ok to reintroduce boost-python2.7 in experimental only. On Sat, 4 Jan 2020, 16:16 Dimitri John Ledkov, wrote: > > > On Sat, 4 Jan 2020, 06:45 Giovanni Mascellani, wrote: > >> Hi, >> >> Il 03/01/20 22:07, Adrian Bunk ha scritto: >> > Dimitri

Bug#945840: libboost-python1.67.0 must not drop the Python 2.7 library

On Sat, 4 Jan 2020, 06:45 Giovanni Mascellani, wrote: > Hi, > > Il 03/01/20 22:07, Adrian Bunk ha scritto: > > Dimitri already agreed in a private discussion that this change was > bogus. > > > Hm?! I acknowledge it is an Abi Break, but it was intentional. We want to both drop python2 and drop

Bug#947065: linphone: Please drop sgmltools-lite build-dependency, unused

Package: linphone Version: 3.12.0-3 Severity: serious Dear Maintainer, Linphone ships a 10 year old .lyx manual, which is prebuilt to .sgml manual, which is compiled by Makefile.am/configure, which has not been ported to CMake, and CMake buildsystem has been used forever. sgmltools-lite is

Bug#946984: yade: Ships python3.8 scripts, without any python3 or python3.8 deps

tag 946984 pending thanks On Thu, 19 Dec 2019 07:33:52 +0100 Anton Gladky wrote: > Hi, > > it is already done and will be uploaded tonight. Great! Thanks. > The problem is that it should go through NEW-queue. > Indeed it will must do that =/ I guess we can live without yade in testing for a

Bug#946984: yade: Ships python3.8 scripts, without any python3 or python3.8 deps

Package: yade Version: 2019.12~git~0~e74819ea-4 Severity: grave Dear Maintainer, Autopkgtest correctly points out that `yade` cannot be executed in testing, upon migration. yade appears to be switched from python2 to python3 incorrectly as follows. Package yade builds scripts as python3.8, yet

Bug#946857: pyfftw: FTBFS in unstable

On Mon, 16 Dec 2019 20:02:55 +0200 Graham Inggs wrote: > Source: pyfftw > Version: 0.11.1-3 > Severity: serious > Tags: ftbfs > > Hi Maintainer > > As can be seen on the reproducible builders [1], pyfftw currently > FTBFS in unstable. > This seems to be a combination of new versions of

Bug#946881: translate-docformat: Please remove translate-docformat from Debian, package of questionable value

Package: translate-docformat Version: 0.6-5 Severity: serious Dear Maintainer, This package is a trivial bash script, that mixes in together a kitchensync of obsolete, bit-roted calls to web-browsers and various xmlish/tex tools. It doesn't bring any additional value over using existing tools

Bug#946880: newt: Please switch from sgmtools-lite to docbook-utils

; urgency=medium + + * Non-maintainer upload. + * Switch from orphaned sgmltools-lite to docbook-utils. + + -- Dimitri John Ledkov Tue, 17 Dec 2019 00:39:20 + + newt (0.52.21-3) unstable; urgency=medium * Move to Standards-Version: 4.4.0 diff -Nru newt-0.52.21/debian/control newt-0.52.21

Bug#946828: openblas: Fails to install during autopkgtests

Source: openblas Version: 0.3.7+ds-6 Severity: serious Dear Maintainer, openblas appears to fails its autopackagetests with failure to install the librararies Setting up libopenblas64-serial-dev:amd64 (0.3.7+ds-6) ... update-alternatives: using

Bug#945840: /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory

On Thu, 5 Dec 2019 at 21:33, Giovanni Mascellani wrote: > > Il 05/12/19 22:15, Dimitri John Ledkov ha scritto:>> Also, I hope to > finish working on 1.71 as soon as possible, so that we > >> can start that migration. > > > > But 1.71 for sure will not have p

Bug#945840: /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory

On Thu, 5 Dec 2019 at 21:15, Joachim Reichel wrote: > > Hi, > > it seems to me that other packages are also affected: > > - k3d FTBFS (bug #946225) > - yade FTBFS (apparently fixed in experimental, see bug #938859) > > Even though these packages needs to be fixed, it might be a good idea not to >

Bug#945840: /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory

On Thu, 5 Dec 2019 at 21:15, Joachim Reichel wrote: > > Hi, > > it seems to me that other packages are also affected: > > - k3d FTBFS (bug #946225) > - yade FTBFS (apparently fixed in experimental, see bug #938859) > > Even though these packages needs to be fixed, it might be a good idea not to >

Bug#945840: /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory

On Thu, 5 Dec 2019 at 20:57, Giovanni Mascellani wrote: > > Hi, > > Il 05/12/19 17:55, Dimitri John Ledkov ha scritto: > > In principal I agree, in practice the only broken app today is ledger, > > which should have by now uploaded without a python bridge enabled; or >

Bug#945840: /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory

On Tue, 3 Dec 2019 22:03:29 +0100 Giovanni Mascellani wrote: > Hi, > > Il 01/12/19 23:33, Dimitri John Ledkov ha scritto: > > All the broken packages, are RC buggy themselves already. Anything that > > is using py2 is RC buggy. > > I'm sorry, but this does not look like

Bug#945840: /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory

I guess I should have created a list of breaks, and uploaded with it, as indeed a soname is dropped. On Sun, 1 Dec 2019, 23:36 Dimitri John Ledkov, wrote: > No, > > All packages that use python have removal blocks already filed, and those > bugs should be marked as blocking migrat

Bug#945840: /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory

No, All packages that use python have removal blocks already filed, and those bugs should be marked as blocking migration of boost. It will take a while for boost to migrate. There are only a few applications, a few dual py2/py3 packages, and majority already scheduled to be removed from the

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

On Tue, 7 May 2019 19:39:15 +0200 Guilhem Moulin wrote: > Hi Dimitri, > > On Tue, 07 May 2019 at 15:46:25 +0100, Dimitri John Ledkov wrote: > > On Tue, 7 May 2019 14:16:43 +0100 Dimitri John Ledkov > > wrote: > >> This issue concerns me a lot at the moment. I am cu

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

On Tue, 7 May 2019 14:16:43 +0100 Dimitri John Ledkov wrote: > Hi, > > On Wed, 10 Apr 2019 15:22:09 +0200 Guilhem Moulin wrote: > > > > Not setting the SSL_MODE_AUTO_RETRY flag back after removing O_NONBLOCK > > (ie commenting out `Net::SSLeay::set_mode($ssl, $mode_aut

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

Hi, On Wed, 10 Apr 2019 15:22:09 +0200 Guilhem Moulin wrote: > > Not setting the SSL_MODE_AUTO_RETRY flag back after removing O_NONBLOCK > (ie commenting out `Net::SSLeay::set_mode($ssl, $mode_auto_retry);` in > the patch) solves the problem with blocking I/O and select/poll, but > breaks

Bug#914068: freelan FTBFS with boost 1.67

On Wed, 24 Apr 2019 14:42:24 +0100 Dimitri John Ledkov wrote: > > Possibly solved by > https://github.com/freelan-developers/freelan/commit/573a2d38feafec1256ab97b712e963278e4b3fb0.patch > ? > Actually a bit more than that: 573a2d38feafec1256ab97b71

Bug#914068: freelan FTBFS with boost 1.67

On Sun, 18 Nov 2018 23:33:16 +0200 Adrian Bunk wrote: > Source: freelan > Version: 2.0-8 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/package.php?p=freelan=sid > > ... > In file included from build/release/include/freelan/configuration.hpp:62, > from >

Bug#924937: libpq5: OpenSSL license contamination of GPL reverse-dependencies

On Wed, 20 Mar 2019 16:31:25 +0100 Ansgar Burchardt wrote: > Hi, > > the OpenSSL ./. GPL problem (if one sees it as a problem) is larger > than just libpq5: just looking at a small sample of the direct rdeps of > libssl1.1, one can find the following GPL-licensed programs linking it: > >

Bug#915287: Bug#900160 closed by Dimitri John Ledkov (Bug#900160: fixed in ruby-eventmachine 1.0.7-4.2)

close 915287 1.0.7-4.2 thanks On Thu, 6 Dec 2018 14:05:22 +0100 Sebastian Andrzej Siewior wrote: > On 2018-12-06 12:42:50 [+0100], gregor herrmann wrote: > > On Wed, 05 Dec 2018 13:57:05 +, Debian Bug Tracking System wrote: > > > > > ruby-eventmachine (1.0.7-4.2) unstable; urgency=medium >

Bug#914688: Default defines discrepancy

On Mon, 26 Nov 2018 at 12:52, Adrian Bunk wrote: > > Control: forwaded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28314 > > On Mon, Nov 26, 2018 at 12:28:28PM +0000, Dimitri John Ledkov wrote: > > xnox@diamond:~$ g++ -std=c++14 -dM -E -x c++ - < /dev/null | grep linux &g

Bug#899454: boost-defaults: Invalid maintainer address pkg-boost-de...@lists.alioth.debian.org

On Thu, 24 May 2018 09:43:45 +0200 (CEST) Christoph Biedl wrote: > Package: src:boost-defaults > Version: 1.62.0.1 > Severity: serious > User: ad...@alioth-lists.debian.net > Usertag: alioth-lists-maintainer > > Dear uploader of boost-defaults, > > as you've probably heard, Debian's alioth

Bug#912910: boost1.67: for loops without set -e

severity 912910 wishlist thanks On Sun, 4 Nov 2018 21:36:14 +0100 Mattia Rizzolo wrote: > Source: boost1.67 > Version: 1.67.0-9 > Severity: serious > Control: clone -1 -2 boost1.62 1.62.0+dfsg-10 > Control: retitle -2 boost1.62: for loops without set -e > Justification: Policy §4.6 > > > Hi

Bug#759410: Different approach for safe-rm

I agree that's the generic way forward for safe-rm in light of usrmerge but did not feel it was right to make up such a path in Ubuntu. I'm happy with such a solution for Debian, and for Ubuntu. I'm off for two weeks, but will migrate Ubuntu over to that if and when available for merging/syncing

Bug#859829: bump

On Thu, 03 May 2018 07:47:09 +0200 wf...@niif.hu (Ferenc =?utf-8?Q?W=C3=A1gner?=) wrote: > No news yet. > -- > Feri > > xml-security-c-2.0 is out and appears to compile fine against openssl 1.1. Is that the upstream release we were waiting to package? Regards, Dimitri.

Bug#898720: E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1 (btrfs-zero-log no longer present)

On 15 May 2018 at 13:59, Simon McVittie wrote: > Package: btrfs-progs > Version: 4.16.1-1 > Severity: grave > Justification: renders package unusable (fails to install) > > Preparing to unpack .../04-btrfs-progs_4.16.1-1_amd64.deb ... > Unpacking btrfs-progs (4.16.1-1) over

Bug#892394: [pkg-boost-devel] Bug#892394: boost1.63: build-depends on GCC 6

On 14 May 2018 at 09:27, Olaf van der Spek <olafvds...@gmail.com> wrote: > Dimitri John Ledkov: > >> boost1.65 has been rejected by ftp-masters, on copyright reasons. > > Hi Dimitri, > > Got a link? > Not having Boost in Debian would be unfortunate. I'm sure there'

Bug#886968: btrfs-progs-udeb: depends on non-udeb: libzstd1

On 18 April 2018 at 08:18, Emilio Pozuelo Monfort wrote: > On 18/04/18 01:30, Cyril Brulebois wrote: >> That's another perfect example why udeb additions should get reviewed: >> we would have noticed another buggy package, and its bugginess might not >> have been copied over to

Bug#886968: btrfs-progs-udeb: depends on non-udeb: libzstd1

On 18 April 2018 at 00:30, Cyril Brulebois <k...@debian.org> wrote: > Hi, > > Dimitri John Ledkov <x...@debian.org> (2018-04-17): >> First, I apologize for not responding to this email earlier, as I have >> missed it in my mailbox. > > It's a mail from

Bug#886968: btrfs-progs-udeb: depends on non-udeb: libzstd1

On 17 April 2018 at 19:01, Cyril Brulebois <k...@debian.org> wrote: > Dimitri John Ledkov <x...@debian.org> (2018-01-15): >> On 15 January 2018 at 00:27, Cyril Brulebois <k...@debian.org> wrote: >> > Hi, >> > >> > Cyril Brulebois <k...@

Bug#892394: [pkg-boost-devel] Bug#892394: boost1.63: build-depends on GCC 6

On 8 March 2018 at 17:48, wrote: > Source: boost1.63 > Severity: serious > Tags: sid buster > User: debian-...@lists.debian.org > Usertags: gcc-6-rm > > Hi, > > boost1.63 build-depends on GCC 6. We now have GCC 7 (default) and GCC > 8 in the archive, so please make your package

Bug#886968: btrfs-progs-udeb: depends on non-udeb: libzstd1

On 15 January 2018 at 00:27, Cyril Brulebois wrote: > Hi, > > Cyril Brulebois (2018-01-12): >> Your package is no longer installable (along with its rev-dep >> partman-btrfs) because it now depends on libzstd1, which isn't >> a udeb. > > It seems zstd is only an

Bug#853410: galera-3: ftbfs with GCC-7

On Tue, 31 Oct 2017 21:42:35 + Dimitri John Ledkov <dimitri.led...@surgut.co.uk> wrote: > On Tue, 31 Jan 2017 09:31:28 + Matthias Klose <d...@debian.org> wrote: > > Package: src:galera-3 > > Version: 25.3.19-2 > > Severity: normal > > Tags: sid buste

Bug#853410: galera-3: ftbfs with GCC-7

ption: Build without Werror to resolve FTBFS with gcc 7. Closes: #853410 Author: Dimitri John Ledkov <x...@ubuntu.com> Bug-Debian: https://bugs.debian.org/853410 --- galera-3-25.3.20.orig/SConstruct +++ galera-3-25.3.20/SConstruct @@ -444,7 +444,7 @@ if ssl == 1: # these wil

Bug#865320: [PATCH] inetmapi: adjust for vmime 0.9.2 API

On 26 July 2017 at 09:55, Mark Dufour wrote: > hi dimitri, > >> I'm not sure, but I seemed to me the patch I was cherrypicking is only >> in 8.4.90 aka alpha/beta builds. I might be wrong and/or got deceived >> by github. >> >> This build failure was blocking python3.6

Bug#865320: [PATCH] inetmapi: adjust for vmime 0.9.2 API

On 25 July 2017 at 19:04, Carsten Schoenert <c.schoen...@t-online.de> wrote: > Hello Dimitri, > > On Tue, Jul 25, 2017 at 06:41:58PM +0100, Dimitri John Ledkov wrote: >> From: Jan Engelhardt <developm...@kopano.io> >> >> References: KC-263 >> --- >&

Bug#865320: [PATCH] inetmapi: adjust for vmime 0.9.2 API

From: Jan Engelhardt References: KC-263 --- Rebased this patch onto 8.1.0 upstream release. - xnox. inetmapi/ECVMIMEUtils.cpp| 40 ++--- inetmapi/ECVMIMEUtils.h | 5 +- inetmapi/MAPISMTPTransport.cpp | 102 +---

Bug#851385: advancecomp FTBFS on big endian

v2.0 fixes the big endian errors, and builds fine on s390x for me. Could you please upgrade advancecomp to v2.0 release? -- Regards, Dimitri.

Bug#845729: libtspi-dev must not force OpenSSL 1.1 on packages that are not ready

On Wed, 30 Nov 2016 00:11:01 +0100 Sebastian Andrzej Siewior wrote: > On 2016-11-26 11:31:49 [+0200], Adrian Bunk wrote: > > Package: libtspi-dev > > Version: 0.3.14+fixed1-1 > > Severity: serious > > Control: block 827061 by -1 > > > > libtspi-dev must not force OpenSSL

Bug#834718: choreonoid: maintainer address bounces

Hello, On 1 November 2016 at 04:01, Adrian Bunk wrote: > > On Thu, Aug 18, 2016 at 11:21:27AM +0200, Jakub Wilk wrote: > > Source: choreonoid > > Version: 1.5.0+dfsg-0.1 > > Severity: serious > > Justification: Policy §3.3 > > > > I tried to report a bug against this package, and

Bug#840230: When installing to rootfs on LVM, an empty subvol= is appended to rootflags

I think I did fix this before http://launchpadlibrarian.net/251885735/zipl-installer_0.0.33ubuntu1_0.0.33ubuntu2.diff.gz I guess it did not make over to debian. Will fix soon. Regards, Dimitri. On 9 October 2016 at 19:34, Philipp Kern wrote: > Package: zipl-installer

Bug#835611: hg-git: FTBFS in testing (broken by new git)

ngelog 2016-09-15 15:02:05.0 +0100 @@ -1,3 +1,11 @@ +hg-git (0.8.5-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix test-suite failure with new git, different output from +git. Closes: #835611 + + -- Dimitri John Ledkov <x...@ubuntu.com> Thu, 15 Sep 20

Bug#780207: closing 780207

close 780207 thanks Whilst I agree that reasonable attempts must be made to use existing hardware drives, and thus retry reads/writes as necessory, I do not believe it is mdadm package's responsibility to create or adjust underlying hardware policy of things that back the array. I also don't

Bug#621786: closing 621786

close 621786 thanks As per submitters request - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621786#115

Bug#824895: [PATCH] warn against likely data loss

Control: severity -1 wishlist Control: tag -1 wontfix Hello, On 20 May 2016 at 22:48, Nicholas D Steeves wrote: > Package: btrfs-progs > Version: 4.5.2-1 > Tags: patch > Control: severity -1 severe > > Because btrfs-convert is known to fail, and is known to causes >

Bug#809998: [pkg-boost-devel] Bug#809998: libboost-date-time1.55.0: not installable in sid

Hello, On 5 January 2016 at 11:04, Ralf Treinen wrote: > Package: libboost-date-time1.55.0 > Version: 1.55.0+dfsg-4 > Severity: serious > User: trei...@debian.org > Usertags: edos-uninstallable > > Hi, libboost-date-time1.55.0 is not installable in sid on any of the >

Bug#807915: mono-addins: FTBFS with new mono, upgrade to 1.2 release?

Would something like attached work? Description: set target framework to 4.5. Author: Dimitri John Ledkov <x...@ubuntu.com> --- mono-addins-1.2.orig/Mono.Addins.CecilReflector/Mono.Addins.CecilReflector.csproj +++ mono-addins-1.2/Mono.Addins.CecilReflector/Mono.Addins.CecilReflector.

Bug#807915: mono-addins: FTBFS with new mono, upgrade to 1.2 release?

X-Debbugs-CC: Dimitri John Ledkov <x...@debian.org> Source: mono-addins Severity: serious mono-addins ftbfs in unstable. maybe it should be upgraded to 1.2 release from github? I haven't tried it yet - https://github.com/mono/mono-addins/releases (note there have been 10 commits to master

Bug#784070: mdadm: diff for NMU version 3.3.2-5.1

I'm uploading updated mdadm, without a fix for this bug at the moment. I will need further testing on this one, as I have not managed to get my machine boot in degraded raid, without any interventions. -- Regards, Dimitri.

Bug#784070: mdadm: diff for NMU version 3.3.2-5.1

Hello, On 5 November 2015 at 08:10, Yann Soubeyrand wrote: > On Wed, 4 Nov 2015 16:01:10 -0600 Bryan Christ wrote: >> I just tested with a Debian Testing from 11/2 and it's still not working. > > Hi, > > Did you test with the

Bug#784070: mdadm: diff for NMU version 3.3.2-5.1

Hello, On 28 October 2015 at 12:41, wrote: > Control: tags 784070 + patch > > Dear maintainer, > > I'm about to prepare an NMU for mdadm (versioned as 3.3.2-5.1). The diff is > attached to this message. Let me know if you want me to upload it. > I agree. there

Bug#784070: is it maybe possible to settle dislikings and fix this bug?

On 27 October 2015 at 15:42, Ben Hutchings wrote: > On Tue, 2015-10-27 at 18:30 +0300, Michael Tokarev wrote: >> 27.10.2015 18:23, Ben Hutchings wrote: >> > On Tue, 2015-10-27 at 10:25 +0300, Michael Tokarev wrote: >> > > I'm not maintaining mdadm anymore. >> > >> > Then why

Bug#797554: libzrtpcpp: GPL linked with OpenSSL without exception

Severity: serious Package: libzrtpcpp Version: 2.3.4-1 The packae is GPLv3, yet it links with OpenSSL without an exception. Hence it is not-free. Regards, Dimitri.

Bug#777848: feel++ vs clang

Heya, Looking at feel++, I've applied the attached patch things progress further, however later clang trips up on what it looks like variadic macros. [ 91%] Building CXX object doc/manual/tutorial/CMakeFiles/feelpp_tut_geotool.dir/geotool.cpp.o cd

Bug#791240: pktools: symbols file update needed for GCC 5

Hello, The block on boost bug is incorrect. 1.55 will not support libstdc++6 c++11 abi. Instead one should build against boost 1.58, which is now the default in unstable, and uses the new abi. So transition to new boost is needed, but otherwise you should be good to go. Regards, Dimitri. On

Bug#791072: icu: library transition may be needed when GCC 5 is the default

On 2 August 2015 at 14:32, László Böszörményi (GCS) g...@debian.org wrote: Control: tags -1 -help On Sun, Aug 2, 2015 at 1:59 PM, Matthias Klose d...@debian.org wrote: On 08/02/2015 01:44 PM, László Böszörményi (GCS) wrote: Then we can start the icu transition separately. sorry, you don't

Bug#791072: icu: library transition may be needed when GCC 5 is the default

On 2 August 2015 at 12:59, Matthias Klose d...@debian.org wrote: On 08/02/2015 01:44 PM, László Böszörményi (GCS) wrote: Control: tags -1 help Hi Matthias, On Sun, Aug 2, 2015 at 12:18 AM, László Böszörményi (GCS) g...@debian.org wrote: Pretty please upload the version from experimental

Bug#777791: ball: ftbfs with GCC-5

I believe remaining fixes can be cherrypicked from upstream. Specifically for clang / c++11 support the remaining bug of code is explicitly converted into bool: https://github.com/BALL-Project/ball/commit/6700400576521250cbe4f8d201391168eb80e0df.patch -- Regards, Dimitri. -- To UNSUBSCRIBE,

Bug#777955: liblas: ftbfs with GCC-5

failure to link is fine, as that's the libstdc++ library transition problem. and indeed we will need to binNMU things in order to transition to the new ABI. This bug report is about the compile failure, rather than the link failure. One can either locally recompile everything with the new ABI,

Bug#780650: systemd: Sources not shipped for hwdb files

Package: systemd Severity: serious Files in ./hwdb/*.hwdb are mostly pregenerated. They are generated using ids-update.pl script from usb.ids, pci.ids, sdio.ids, oui.txt, iab.txt. I'm not sure what the license is of those .ids/.txt files. Please ship ids-update.pl and the ids/txt files as part

Bug#776821: icu-devtools is wrongly marked Multi-Arch:foreign

On Mon, 2 Feb 2015 08:43:14 +0100 Helmut Grohne hel...@subdivi.de wrote: Package: icu-devtools Version: 52.1-7 Severity: serious Justification: can cause other packages to FTBFS User: helm...@debian.org Usertags: rebootstrap The icu-devtools is marked as Multi-Arch:foreign. It contains the

Bug#773916: libical: Ship different constant values accross builds

On 31/12/14 10:00, Simon McVittie wrote: On Mon, 29 Dec 2014 at 21:27:16 +, Debian Bug Tracking System wrote: libical (1.0-1.2) unstable; urgency=medium . * Non-maintainer upload. * Sort keys to generate reproducible source code. (Closes: #773916) This is enough to make 1.0

Bug#773916: libical: Ship different constant values accross builds

On Thu, 25 Dec 2014 16:46:14 +0100 =?iso-8859-1?B?Suly6W15?= Bobbio lu...@debian.org wrote: Package: libical-dev Version: 1.0-1.1 Severity: critical User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness Hi! While working on the “reproducible builds” effort [1], we

Bug#748728: Bug#772679: unblock: libuser/1:0.60~dfsg-1.1

On Sun, 21 Dec 2014 20:23:17 -0600 Brad Bosch brad112...@gmail.com wrote: I've not chimed in on this yet because I haven't had much time to research the history or use of libuser (and I still haven't, really). But I'd like to point out... The id-utils package has been part of Debian for

Bug#772873: auctex: Trigger cycle causes dpkg to fail processing

On Thu, 11 Dec 2014 21:52:47 +0100 Guillem Jover guil...@debian.org wrote: Package: auctex Version: 11.88-1 Severity: serious Hi! This package can get involved in a trigger cycle. The problem is that it installs interests on /usr/share/texmf with files there provided by

Bug#771496: overwrites user changes to configuration file /etc/dpkg-cross/cross-compile on upgrade (violates 10.7.3)

Note however that said file /etc/dpkg-cross/cross-compile is not declared as a conffile. (See $ cat /var/lib/dpkg/info/dpkg-cross.conffiles ) The comments inside it clearly state that it is managed / updated through debconf. Reading the policy documentation most things are satisfied The other

Bug#758121: [Pkg-crosswire-devel] Bug#758121: bibletime: Bibletime is unusable in testing and unstable

On 8 October 2014 15:54, da...@sandersweb.net wrote: retitle 758121 bibletime: New upstream release fixes display problem in jessie severity 758121 grave thanks On Monday, October 06, 2014 10:26:56 PM you wrote: Bibletime is unusable in jessie and sid. When you open any Bible or

Bug#758121: [Pkg-crosswire-devel] Bug#758121: bibletime: Bibletime is unusable in testing and unstable

On 9 October 2014 18:21, David Sanders da...@sandersweb.net wrote: On Thursday, October 09, 2014 10:27:48 AM David Sanders wrote: On Thursday, October 09, 2014 10:55:59 AM Dimitri John Ledkov wrote: On 8 October 2014 15:54, da...@sandersweb.net wrote: retitle 758121 bibletime: New upstream

Bug#747784: closing 747784

close 747784 3.2.2+dfsg1-1 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#756023: init: Please drop Essential:yes from init metapackage

shouldn't be making 3 inits transitively essential, when they currently are not. Patch attached. From 99cde7b65ed839df2250f9278847ca20c64e6fd6 Mon Sep 17 00:00:00 2001 From: Dimitri John Ledkov x...@ubuntu.com Date: Fri, 25 Jul 2014 15:15:33 +0100 Subject: [PATCH] Drop Essential: yes from init

Bug#754869: [Pkg-crosswire-devel] Bug#754869: missing license in debian/copyright

Thanks, pushed patch to the dgit repository. See attached. Regards, Dimitri. From d850d225c8c7d7914f27e03a10ecda97834d1be4 Mon Sep 17 00:00:00 2001 From: Dimitri John Ledkov dimitri.led...@canonical.com Date: Tue, 15 Jul 2014 19:07:50 +0100 Subject: [PATCH] Add missing license in debian

Bug#735339: boost1.54 Non free w3c valid icons

This has now been fixed in boost1.55. I don't intend to fix this in boost1.54, as boost1.54 shouldn't ship with Jessie, instead everything should migrate to boost1.55. -- Regards, Dimitri. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe.

Bug#708841: closing 708841

close 708841 0.16-7.1 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#746493: scilab: scilab fails to launch on powerpc

Package: scilab Version: 5.5.0-2 Severity: grave Dear Maintainer, Previously scilab was operational on powerpc (at least in batch mode). Now it fails to start like so: $ scilab -nw -e 'quit;' Could not create a Scilab main class. Error: Exception in thread main

Bug#708841: closing 708841

close 708841 0.16-7.1 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721847: mkfs.btrfs -f

On 18 March 2014 20:45, Miguel Figueiredo el...@debianpt.org wrote: According mkfs.btrfs manpage the behaviour is expected: -f, --force Force overwrite when an existing filesystem is detected on the device. By default, mkfs.btrfs will not write to the device if it suspects

Bug#733831: wiggle: FTBFS on big endian (mips, powerpc, s390x sparc) but built previously

Control: tag -1 patch On 6 January 2014 03:28, NeilBrown ne...@suse.de wrote: On Wed, 1 Jan 2014 04:06:44 + Dimitri John Ledkov x...@ubuntu.com wrote: On 1 January 2014 03:55, NeilBrown ne...@suse.de wrote: On Wed, 01 Jan 2014 02:49:26 + Dimitri John Ledkov x...@ubuntu.com

Bug#733831: wiggle: FTBFS on big endian (mips, powerpc, s390x sparc) but built previously

Package: wiggle Severity: serious Version: 0.9.1-1 Tags: jessie sid powerpc mips s390x sparc Justification: FTBFS Dear Maintainer, I have noticed that wiggle did not enter testing, since the upload in may. It appears that test-suite fails on big endian architectures, yet package used to built on

Bug#733831: wiggle: FTBFS on big endian (mips, powerpc, s390x sparc) but built previously

On 1 January 2014 03:55, NeilBrown ne...@suse.de wrote: On Wed, 01 Jan 2014 02:49:26 + Dimitri John Ledkov x...@ubuntu.com wrote: I'm also CC'ing upstream author of wiggle, to look into big-endian test-failures. Maybe it's something obvious for Neil =) There have been a lot of fixes

  1   2   >