Bug#1101752:

The issue at hand is less about the debian directory and more about the contents of the debian directory not being updated to follow upstream where needed. In this case the appdata was not kept up to date with upstream. We cannot remove the debian directory from the Debian package and use the one

Bug#1088305: ITP:package ladybird -- Web browser utilizing its own web engine

On Mon, 2025-03-10 at 10:26 +0100, Carl Keinath wrote: > Hi Steve, > > I have seen you intend to package the Ladybird browser > and wanted to check in on its current status. I'm interested > in its packaging and was wondering if you've made any progress > or if there's anything specific you're loo

Bug#1100076: gcc-avr: Missing man page for "avr-gcc" command

On Mon, 2025-03-10 at 22:22 -0500, R Philley wrote: > Package: gcc-avr > Version: 1:5.4.0+Atmel3.6.2-3 > Severity: minor > X-Debbugs-Cc: rp80...@flash.net > > Dear Maintainer, > >    * What led up to the situation? > > Needed to lookup options for the "avr-gcc" command. Could not find a > man pa

Bug#1094897: transition: insighttoolkit5

Package: release.debian.org Severity: normal X-Debbugs-Cc: insighttoolk...@packages.debian.org Control: affects -1 + src:insighttoolkit5 User: release.debian@packages.debian.org Usertags: transition I've uploaded insighttoolkit5 (ITK) v5.4 to experimental and it has cleared NEW. The dispositio

Bug#1094896: ants: FTBFS with ITK 5.4 - new upstream ?

Source: ants Severity: normal Tags: ftbfs ITK upstream has released v5.4 and I'd like to upload to Debian soon. At present, ITK 5.4 is available in experimental. I have done a test-rebuild locally of ANTS, which failed: In file included from /usr/include/ITK-5.4/itkLightObject.h:21,

Bug#1094894: sight: FTBFS with ITK 5.4

Source: sight Severity: normal Tags: ftbfs ITK upstream has released v5.4 and I'd like to upload to Debian soon. At present, ITK 5.4 is available in experimental. I have done a test-rebuild locally of sight, which failed: home/steve/Packages/insighttoolkit/transition- rebuilds/sight-24.1.0/libs/

Bug#1094895: camitk: FTBFS with ITK 5.4

Source: camitk Version: Severity: normal Tags: ftbfs ITK upstream has released v5.4 and I'd like to upload to Debian soon. At present, ITK 5.4 is available in experimental. I have done a test-rebuild locally of camitk, which failed one test: The following tests FAILED: 188 - component-

Bug#1094205: synaptic: Settings|Repository menu fails with python error

Package: synaptic Version: 0.91.4 Severity: important Selecting menu item Settings|Repository fails, and produces the following message on the console. My system (running unstable) no longer has the fil e/usr/bin/apt-key. Is there a missing dependency? (synaptic:31292): IBUS-WARNING **: 17:20:

Bug#1089488: zfs-dkms: module build fails for kernel: 6.12.3-amd64 (x86_64)

Package: zfs-dkms Version: 2.2.6-2 Severity: important Tags: upstream The build log shows a warning: "kmem_cache_create" redefined so I suspect an upstream fix is required. CC [M] /var/lib/dkms/zfs/2.2.6/build/module/os/linux/spl/spl-xdr.o In file included from /var/lib/dkms/zfs/2.2.6/build/mo

Bug#1088847: php-dompdf: autopkgtest failure: missing extensions

Source: php-dompdf Version: 3.0.0+dfsg-2 Severity: important Sometime between November 14 and November 27, the autopkgtest began failing. The error message is: 44s autopkgtest [21:13:58]: test phpunit: [--- 45s phpab %development% - Copyright (C) 2009 - 2024 by Arne Blankerts

Bug#1088525: RM: geomview [armel armhf i386] -- ROM; Architecture set has changed

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: geomv...@packages.debian.org Control: affects -1 + src:geomview User: ftp.debian@packages.debian.org Usertags: remove

Bug#1088305: ITP:package ladybird -- Web browser utilizing its own web engine

Package: wnpp Severity: wishlist * Package name: ladybird Version : Pre Alpha Upstream Author : Andreas Kling and others * URL : https://ladybird.org * License : BSD-2-Clause Programming Lang: C++ Description : web browser Ladybird is a brand-new brows

Bug#1086319: snek: FTBFS: /usr/lib/gcc/avr/14.2.0/../../../avr/bin/ld: snek-duemilanove-1.9.elf section `.text' will not fit in region `text'

On Wed, 2024-10-30 at 18:07 -0700, Keith Packard wrote: > > I've submitted an MR to the gcc-avr repository on salsa: > > https://salsa.debian.org/debian/gcc-avr/-/merge_requests/4 > Thank you. I will be reviewing and testing this evening and then get it forwarded to my sponsor. -Steve

Bug#1083114: gcc-avr FTCBFS: multiple reasons

On Mon, 2024-10-07 at 15:40 +0200, Helmut Grohne wrote: > Hi Steve, > > On Sat, Oct 05, 2024 at 09:01:25AM -0700, Steve M wrote: > > Thank you for testing my package and providing a patch. I would take it as- > > is > > and call it a day, but I am in the middle of s

Bug#1083114: gcc-avr FTCBFS: multiple reasons

On Tue, 2024-10-01 at 23:24 +0200, Helmut Grohne wrote: > Source: gcc-avr > Version: 1:7.3.0+Atmel3.7.0-2 > Tags: patch > User: debian-cr...@lists.debian.org > Usertags: ftcbfs > > gcc-avr fails to cross build from source for two distinct reasons. The > first reason only shows for certain architec

Bug#1081586: RFS: log2ram/1.7.2+ds-1 [ITP] -- Write log files to RAM

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "log2ram": * Package name : log2ram Version : 1.7.2+ds-1 Upstream contact : Azlux * URL : https://github.com/azlux/log2ram * License : MIT * Vcs

Bug#1079003: RM: digikam [armel mips64el ppc64el riscv64 s390x alpha hppa hurd-amd64 hurd-i386 loong64 m68k powerpc ppc64 sh4 sparc64 x32] -- ROM; Set of supported architectures has changed

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: digi...@packages.debian.org Control: affects -1 + src:digikam User: ftp.debian@packages.debian.org Usertags: remove The most recent upstream release of Digikam has made use of Qt Webengine mandatory. Therefore, Digikam can only be built o

Bug#1079001: RM: mgt -- ROM; Obsolete, no recent release

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: m...@packages.debian.org Control: affects -1 + src:mgt User: ftp.debian@packages.debian.org Usertags: remove This package hasn't had an upstream release since 1996, has few users according to popcon, and needs work to build with modern com

Bug#1078940: O: mgt -- game record display/editor for the oriental game of go

Package: wnpp Severity: normal X-Debbugs-Cc: m...@packages.debian.org Control: affects -1 + src:mgt This package hasn't had an upstream release since 1996, so may be long past its usefulness. I intend to orphan the mgt package. The package description is: Mgt allows the user to examine Go game

Bug#1074032: nvidia-smi locks up machine with new file descriptor limit

Package: nvidia-smi Version: 535.183.01-1 Severity: normal A couple months ago, I ran "nvidia-smi" command without issue. I ran it again today and the machine simply locked up. Recently, the hard limit of file descriptors was raised for debian: https://lists.debian.org/debian-devel/2024/06/msg00

Bug#1069533: sayonara: Please package new upstream version

Is this not an issue that would prevent such an update for the time being? This package is part of the ongoing testing transition known as auto-qtbase- opensource-src. Please avoid uploads unrelated to this transition, they would likely delay it and require supplementary work from the release

Bug#1067065: nmu: gringo_5.6.2-1

Package: release.debian.org Severity: normal X-Debbugs-Cc: gri...@packages.debian.org Control: affects -1 + src:gringo User: release.debian@packages.debian.org Usertags: binnmu nmu gringo_5.6.2-1 . ANY . unstable . -m "Rebuild against updated python3.11 for 64-bit time transition"

Bug#1060239: RM: pstotext -- ROM; No upstream, superceeded by ps2ascii

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: pstot...@packages.debian.org Control: affects -1 + src:pstotext The pstotext package was removed from testing in 2018 due to grave bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Bug#1057117:

Neil, Thank you for taking to time to test my packaging efforts and submit a bug report. I just did a quick test and was unable to reproduce your bug on Debian testing. This weekend when I have a little more time I'll try setting up a clean Debian unstable environment and try again. $ mkdir hello

Bug#1051525: RFS: wxformbuilder/3.10.1-1 [RFP] -- GUI designer for the wxWidgets toolkit

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "wxformbuilder":  * Package name : wxformbuilder    Version  : 3.10.1-1    Upstream contact : Steffen Olszewski  * URL  : http://wxformbuilder.org/  * License

Bug#1040268: RM: mriconvert -- ROM; Obsolete, abandoned upstream

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: mriconv...@packages.debian.org Control: affects -1 + src:mriconvert The functionality of this software is provided by dcm2niix. Upstream has stopped maintaining the software and provid

Bug#1038887: passwordsafe: googletest no longer supports C++ prior to C++14

Source: passwordsafe Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) I saw autopkgtest failure for passwordsafe 133s /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 133s 27

Bug#1031953: libkf5screen8: Second monitor issues with NVIDIA

Package: libkf5screen8 Version: 4:5.27.0-1 Severity: normal Tags: patch upstream This is to note that the upstream bug titled "On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep" applies to Debian package 4.27.0-1. See https://bugs.kde.org/show_b

Bug#969202: ITA: binutils-avr -- Binary utilities supporting Atmel's AVR targets

Joshua, It has been a little over a year since you changed binutils-avr from RFA to ITA. Do you still intend to proceed with this adoption? If not, please consider returning it to RFA as I am considering adopting avr-libc, binutils-avr, and gcc-avr as a group. Thanks -Steve

Bug#1020803: RM: matrix-mirage -- ROM; Orphaned, possibly dead upstream, dependency qtav is dead upstream

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: 1013...@bugs.debian.org, 1020...@bugs.debian.org Note: I'm not technically the maintainer of matrix-mirage, but I didn't see a more fitting category and it is orphaned.

Bug#1020397: RM: qtav -- ROM; Package is abandoned upstream

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: 1004...@bugs.debian.org See https://github.com/wang- bin/QtAV/commit/fdc613dc99304f208cff0bb25b3ded14bb993237

Bug#1019863: opencv.jar: broken symbolic link to opencv4/opencv-454d.jar

Package: libopencv-java Version: 4.6.0+dfsg-6+b1 Severity: important This bug makes the build of (unrelated) package libsis-jhdf5-java fail. $ dpkg --search /usr/share/java/opencv.jar libopencv-java: /usr/share/java/opencv.jar $ file /usr/share/java/opencv.jar /usr/share/java/opencv.jar: broken

Bug#1018987: nmu: minc-tools_2.3.00+dfsg-9

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu minc-tools_2.3.00+dfsg-9 . ANY . unstable . -m "rebuild against updated libminc"

Bug#1018888: nmu: elastix_5.0.1-3+b1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu elastix_5.0.1-3+b1 . ANY . unstable . -m "Rebuild against updated insighttoolkit5"

Bug#1018839: nmu: insighttoolkit5_5.2.1-5

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu insighttoolkit5_5.2.1-5 . ANY . unstable . -m "Rebuild against updated libminc"

Bug#990047: timeshift: Not possible to browse content of snapshot via the gui

On Mon, 2022-08-01 at 22:26 +, Ludovic Poujol wrote: > Steeve, > > Good question. And, you're right, thanks ! > > I thought it was some kind of "internal browser" provided with > timeshift. But after looking more closely, it was actually trying to > start VSCode ! :s And it's the one that d

Bug#994704: timeshift: Unable to init server: connection refused. possible pkexec misconfiguration for timeshift-laucher command

Bruno, I've not been able to reproduce this problem. Does it still happen for you? Thanks -Steve

Bug#990047: timeshift: Not possible to browse content of snapshot via the gui

Ludovic, This sounds to me like an issue with not being allowed to run your file browser with root permissions. If this is still a problem for you, which file browser are you using? Thanks -Steve

Bug#1016436: lldb-14: lldb malfunctions due to faulty python path (ModuleNotFoundError: No module named 'lldb.embedded_interpreter')

Package: lldb-14 Version: 1:14.0.6-2 Severity: normal Dear Maintainer, There is a misconfiguration somewhere in the build, that embeds a non-existent python path: $ lldb -P /usr/lib/local/lib/python3.10/dist-packages This causes lldb to emit an error when starting: $ lldb Traceback (most r

Bug#1014891: timeshift: New upstream release 22.06.3

On Wed, 2022-07-13 at 17:32 -0400, Boyuan Yang wrote: > Package: timeshift > Version: 22.06.1-0.1 > Severity: normal > X-Debbugs-CC: s...@swm1.com > > Dear Debian timeshift package maintainers, > > A new upstream release is available at > https://github.com/linuxmint/timeshift/releases/tag/22.06.

Bug#1013333: libidn12: Upgrade to libidn 1.40-1 breaks kmail

Package: libidn12 Version: 1.40-1 Severity: important Dear Maintainer, I had version 1.38-4 installed until I ran apt upgrade today. After the upgrade, mail that originated outside of my system seems to vanish. The mail logs show a normal delivery (by postfix). But kmail shows no sign of the

Bug#1005710: RM: elastix [i386] -- ROM; No longer targets i386

Package: ftp.debian.org Severity: normal The ITK v5 package only builds for amd64, so the elastix i386 binaries need removing to allow it to get to testing. At least that's how I understand the excuse output https://qa.debian.org/excuses.php?package=elastix Thanks, -Steve

Bug#992473: kmail: Unread messages suddenly pink

Package: kmail Version: 4:20.08.3-1 Severity: normal Dear Maintainer, Today KMail decided to colour unread messages (in the message list) bright pink. It was not pink previously. -Steve -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (500, 'testing'), (200, 'u

Bug#992426: debianutils: Removal of tempfile breaks X login

Package: debianutils Version: 5.0.1-1 Severity: important Dear Maintainer, The /etc/XSession script uses tempfile, so removal of that package breaks logging into X. -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (200, 'unstable') Architecture: amd64 (x86_64) F

Bug#991837: /usr/lib/python3/dist-packages/gbp/scripts/supercommand.py: import-orig failure

Package: git-buildpackage Version: 0.9.22 Severity: normal File: /usr/lib/python3/dist-packages/gbp/scripts/supercommand.py Dear Maintainer, I attempted to import a new version into 'experimental' branches using: "gbp import-orig --pristine-tar --upstream-branch=upstream-experimental --debian-b

Bug#975422: samba-common-bin: Cannot install 2:4.13.2+dfsg-2+b1: /run samba does not exist.

Package: samba-common-bin Version: 2:4.13.2+dfsg-2+b1 Severity: important Dear Maintainer, Install failed as follows. This was a second attempt so apt reports samba "already the newest version". But the first attempt had the same errors about /run/samba; I would have expected one of these pa

Bug#973001: seqan3: autopackage tests need updating for new googletest

Source: seqan3 Severity: normal Dear Maintainer, The autopkg tests need to be updated for the new googletest. There are failures such as /tmp/autopkgtest-lxc.u2mymoo7/downtmp/autopkgtest_tmp/unit/alphabet/cigar/../alphabet_test_template.hpp:86: Failure Type parameterized test suite alphabet i

Bug#972944: ms-gsl: autopkgtests should build googletest from sources

Source: ms-gsl Severity: normal Dear Maintainer, A new version of googletest has been uploaded and shortly thereafter I received word that ms-gsl autopkgtest has failed on arm64. See https://ci.debian.net/ data/autopkgtest/testing/arm64/m/ms-gsl/7637851/log.gz The error in that log looks like

Bug#972603: seqan: Needs update for new googletest

Source: seqan Severity: normal Dear Maintainer, Hi, Just uploaded a newer googletest and seqan is reporting autopkgtest failures. However, at least some failures appear to be due to changes in googletest that require adapting the test code. For example, the following [from https://ci.debian

Bug#971412: libdcmtk-dev: undeclared conflict with libcharls-dev

Package: libdcmtk-dev Version: 3.6.4-2.1+b1 Severity: normal Dear Maintainer, I just attempted to install libcharls-dev, which failed: E: /var/cache/apt/archives/libcharls-dev_2.1.0+dfsg-1_amd64.deb: trying to overwrite '/usr/lib/x86_64-linux-gnu/libcharls.so', which is also in package libdc

Bug#951629: RFS: timeshift/19.01+ds-2.1 [NMU] [RC] -- System restore utility

On Wed, 19 Feb 2020 10:05:49 -0500 Boyuan Yang wrote: > Hi Steve, wrar, > > On Wed, 19 Feb 2020 12:40:15 +0500 Andrey Rahmatullin wrote: > > Control: tags -1 + moreinfo > > > > Unfortunately you ignored > https://lists.debian.org/debian-mentors/2020/

Bug#944396: transition: exiv2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition New upstream, new soversion. Ben file: title = "exiv2"; is_affected = .depends ~ "libexiv2-14" | .depends ~ "libexiv2-27"; is_good = .depends ~ "libexiv2-27"; is_bad = .depends ~ "libex

Bug#899274: KMail does not always remember the desired message list columns

Package: kmail Version: 4:17.12.3-1 Severity: normal In the folder list, KMail is able to display several columns: Name, Unread, Total, and Size. I have turned off all but Name. Kmail regularly seems to ignore my wishes and displays all four columns when I re-start. But this does not happen all

Bug#897171: synergy: diff for NMU version 1.8.8-stable+dfsg.1-1.1

gency=medium + + * Non-maintainer upload + * Update build-deps for googletest. Closes: #897171. + + -- Steve M. Robbins Tue, 01 May 2018 22:59:58 -0500 + synergy (1.8.8-stable+dfsg.1-1) unstable; urgency=low * New upstream version. diff -Nru synergy-1.8.8-stable+dfsg.1/debian/control sy

Bug#897174: Package erroneously expects googletest headers in /usr/include

On Sun, Apr 29, 2018 at 07:41:26AM -0500, Steve M. Robbins wrote: > 1. Modify the build to look for headers in /usr/src/googletest. Below is a patch to achieve this. --- meson-0.46.0.orig/mesonbuild/dependencies/dev.py2018-03-03 16:02:02.0 -0600 +++ meson-0.46.0/mesonbu

Bug#897149: Package erroneously expects googletest headers in /usr/include

On Sun, Apr 29, 2018 at 01:36:08PM +0200, David Kalnischkies wrote: > Not really knowledgeable enough about cmake through to know if that is > the best we can do ??? it looks kinda ugly/dirty. Your patch looks fine to me. A slight improvement below avoids repeating the /usr/src path. > We cou

Bug#897176: Package erroneously expects googletest headers in /usr/include

Package: src:cctz Severity: serious Justification: fails to build from source (but built successfully in the past) control: block 897104 by -1 Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the hea

Bug#897175: Package erroneously expects googletest headers in /usr/include

Package: src:fmtlib Severity: serious Justification: fails to build from source (but built successfully in the past) control: block 897104 by -1 Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the h

Bug#897174: Package erroneously expects googletest headers in /usr/include

Package: src:meson Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the headers was mistakenly installe

Bug#897171: Package erroneously expects googletest headers in /usr/include

Package: src:synergy Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the headers was mistakenly instal

Bug#897173: Package erroneously expects googletest headers in /usr/include

Package: src:aff4 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the headers was mistakenly installed

Bug#897104: googletest: breakage due to files moved to other packages

Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the headers was mistakenly installed into /usr/include. All the listed packages rely on this behaviour and now fail to build since googletest version 1

Bug#897152: x

Package: src:flightcrew Severity: serious Justification: fails to build from source (but built successfully in the past) Subject: Package erroneously expects googletest headers in /usr/include Package: apt Version: 1.6.1 Severity: serious Justification: fails to build from source (but built succes

Bug#897151: Package erroneously expects googletest headers in /usr/include

Package: src:protobuf Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the headers was mistakenly insta

Bug#897149: Package erroneously expects googletest headers in /usr/include

Package: apt Version: 1.6.1 Severity: serious Justification: fails to build from source (but built successfully in the past) control: block 897104 by -1 Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy

Bug#895713: FTBFS with googletest 1.8.0-7

Source: ros-catkin Version: 0.7.11-1 Severity: serious Justification: fails to build from source Debian's googletest package used to ship only sources, not a compiled libgtest. The ros-catkin package has a build-dep on libgtest-dev. However: at build time libgtest is probed for, not found, and C+

Bug#895707: gumbo-parser: diff for NMU version 0.10.1+dfsg-2.2

* Non-maintainer upload. + * Tweak 00-tests.patch to ignore system libgtest (Closes: #895707) + + -- Steve M. Robbins Sat, 14 Apr 2018 18:20:28 -0500 + gumbo-parser (0.10.1+dfsg-2.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru gumbo-parser-0.10.1+dfsg/debian/patches/00-tests.patch

Bug#893884: [pkg-boost-devel] Bug#893884: libboost-locale1.62.0: LC_CTYPE overrides value of LC_ALL

On Fri, Mar 23, 2018 at 03:52:38PM +0100, Nicolas Dandrimont wrote: > I've looked at the upstream history, but this source file has been imported > as-is in SVN 7 years ago and hasn't been touched since, therefore I couldn't > find the upstream rationale for this resolution order. Did you ask ups

Bug#886585: Suggests / Recommends two non-existent packages: python-scitools and python-mshr

Package: fenics Version: 1:2017.1.0.1 Severity: minor Hi, I tried to install the Suggested and Recommended packages, but found two are non-existent. python-scitools: appears to have existed at one time, but now removed from Debian; see https://packages.qa.debian.org/s/scitools/news/20160506T0

Bug#886210: Downgrade "old-standards-version" to an info

Package: lintian Version: 2.5.66 Severity: normal I agree with suggestion by Niels Thykier (on debian-devel): Andrey Rahmatullin: > On Mon, Jan 01, 2018 at 05:26:35PM +, Sean Whitton wrote: >> IMO the point of the field is to ensure that you /don't/ have to upgrade >> to the latest version of

Bug#881688: nmu: berkeley-express_1.5.1-3

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu berkeley-express_1.5.1-3 . ANY . unstable . -m "Rebuild with current Boost libraries" -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unsta

Bug#844268: [pkg-boost-devel] Bug#844268: libboost1.62-doc doesn't contain the actual documentation

On Tue, Oct 24, 2017 at 02:04:44PM +0100, Dimitri John Ledkov wrote: > On 24 October 2017 at 04:00, Steve M. Robbins wrote: > > If I re-enable the doc packages and build, lintian spews dozens of > > errors of three kinds: privacy-breach-logo, privacy-breach-generic, > >

Bug#844268: libboost1.62-doc doesn't contain the actual documentation

On Sun, Apr 23, 2017 at 11:55:15AM +0200, Klaus-J. Wolf wrote: > Package: libboost1.62-doc > Version: 1.62.0+dfsg-4 > Followup-For: Bug #844268 > > Dear Maintainer, > > I have observed that the actual documentation is completely missing in > this documentation package. In duplicate bug report #8

Bug#873569: ITP: libmediawiki -- KDE C++ interface for MediaWiki based web service

Package: wnpp Severity: wishlist Owner: "Steve M. Robbins" * Package name: libmediawiki Upstream Author : Team maintained; see https://github.com/KDE/libmediawiki/blob/master/AUTHORS * URL : https://cgit.kde.org/libmediawiki.git * License : GPL Programmi

Bug#727148: kino: diff for NMU version 1.3.4-2.3

gelog @@ -1,3 +1,11 @@ +kino (1.3.4-2.3) unstable; urgency=medium + + * Non-maintainer upload. + + * Use distinct document names for doc-base (Closes: #727148). + + -- Steve M. Robbins Tue, 15 Aug 2017 23:07:19 -0500 + kino (1.3.4-2.2) unstable; urgency=medium * Non-maintainer upload. di

Bug#865447: Not suitable for release -- please keep out of testing

Source: boost1.61 Severity: grave Package has been superceded by later Boost. Should not be in testing. In fact, was removed from testing earlier [1] but returned because I did not file this bug soon enough. Package is also marked for removal from unstable [2]. -Steve [1] https://packages.qa.de

Bug#865392: RM: boost1.61 -- ROM; Obsoleted by newer Boost

Package: ftp.debian.org Severity: normal Hi, This package was removed from testing during a transition to boost1.62 [1] but was mistakenly re-introduced into testing recently. Please remove the package from the archive -- both unstable and testing. [1] https://packages.qa.debian.org/b/boost1.61

Bug#857507: mesh generation module 'mshr' missing

Package: python-dolfin Version: 2016.2.0-2 Severity: normal The second tutorial script 'ft02_poisson_membrane.py' [1] fails to run because the python module 'mshr' is missing: $ python ft02_poisson_membrane.py Traceback (most recent call last): File "ft02_poisson_membrane.py", line 12, in

Bug#857491: Computation of top_dir is fooled by README

Package: python-sfepy Version: 2016.2-2 Severity: normal I tried to run the examples using: sfepy-run simple examples/diffusion/poisson_short_syntax.py and obtained: sfepy: left over: ['verbose', '__builtins__', '__file__', '__doc__', '__name__', 'data_dir', '__package__', '_filename'] s

Bug#592834: Grub messages during upgrade

Last couple of upgrades have seen similar results to the below: Generating grub configuration file ... File descriptor 3 (pipe:[53933]) leaked on vgs invocation. Parent PID 9473: /usr/sbin/grub-probe File descriptor 3 (pipe:[53933]) leaked on vgs invocation. Parent PID 9473: /usr/sbin/grub-probe

Bug#737016: Bug#834131: Video support still not working

On Wednesday, December 21, 2016 1:30:39 PM CST Lisandro Damián Nicanor Pérez Meyer wrote: > Well, the FRP was not done by a team member nor, as far as I know, anyone > one the team is thinking in packaging it. > > I'm CCing the RFP bug to see if he's still interested in packaging it. El se > I w

Bug#568897: [debhelper-devel] Bug#568897: Bug#568897: debhelper: DEB_BUILD_OPTIONS=nocheck should prevent override_dh_auto_test rule to be run

Peter, You raise a lot of interesting questions about the general handling of DEB_BUILD_OPTIONS in the various tools. I haven't got any real answer for the general question -- and, truthfully, your questions lead me to think it needs to be considered on a case-by-case basis -- so I'd like to c

Bug#568897: [debhelper-devel] Bug#568897: debhelper: DEB_BUILD_OPTIONS=nocheck should prevent override_dh_auto_test rule to be run

On Monday, December 12, 2016 10:57:20 AM CST Peter Pentchev wrote: > On Sun, Dec 11, 2016 at 08:22:09PM -0600, Steve M. Robbins wrote: > > Alternatively: if the logic was all in dh (to skip both dh_auto_test > > and override_dh_auto_test), then it would not need to be in > >

Bug#568897: debhelper: DEB_BUILD_OPTIONS=nocheck should prevent override_dh_auto_test rule to be run

I, too, think this would be a valuable addition. On Tue, Feb 09, 2010 at 02:38:34PM -0500, Joey Hess wrote: > If I did this, I would need to also make override_dh_strip to be > skipped when DEB_BUILD_OPTIONS=nostrip. Yes, would also be nice. > One reason to dislike this is it would mean redun

Bug#846464: apt: Please drop B-D on googletest on unsupported architectures

Control: retitle -1 gtest-port_test fails on m68k On Friday, December 9, 2016 12:40:59 PM CST David Kalnischkies wrote: > On Wed, Dec 07, 2016 at 11:28:09PM -0600, Steve M. Robbins wrote: > Given that this is proven to be false by now I think we can all move on > more or less pretending

Bug#846464: apt: Please drop B-D on googletest on unsupported architectures

Hi, Executive summary: the build failures are mostly solved -- save for one test failure on m68k. On Thursday, December 1, 2016 1:16:43 PM CST David Kalnischkies wrote: > So @googletest maintainers, please state what you can/want to do about > it or not. Being a build-dependency of apt provide

Bug#846254: compile error with gcc-6

On Tue, Nov 29, 2016 at 04:32:21PM +0100, Thorsten Alteholz wrote: > building the alljoyn packages (alljoyn-core-1504, alljoyn-core-1509, > alljoyn-core-1604) with googletest and gcc-6 gives the following compile > error. I guess the "#include " jusst needs to be replaced by > "#include " for gcc-

Bug#845721: Cannot install libc6:i386 -- Breaks: libc6:i386 (!= 2.24-7) but -7 does not exist

Thanks Adam + Aurelien, On Saturday, November 26, 2016 3:11:21 PM CST Aurelien Jarno wrote: > On 2016-11-26 11:02, Adam D. Barratt wrote: > > On Sat, 2016-11-26 at 01:02 -0600, Steve M. Robbins wrote: > > > I don't know how to make sense of these "breaks" version

Bug#845721: Cannot install libc6:i386 -- Breaks: libc6:i386 (!= 2.24-7) but -7 does not exist

Package: libc6 Version: 2.24-7 Severity: normal Tried to install libc6:i386 but cannot. $ sudo apt-get install libc6:i386 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an

Bug#845717: RM: gtest -- ROM; Superceded by source package googletest

Package: ftp.debian.org Severity: normal The binaries produced by source package gtest are now produced by source package googletest. So the former is obsolete and can be removed. Thanks, -Steve

Bug#844721: libgtest-dev isn't replacing dir with symlink on upgrade

On Sunday, November 20, 2016 1:13:32 PM CST David Kalnischkies wrote: > On Sat, Nov 19, 2016 at 10:06:17PM -0600, Steve M. Robbins wrote: > > On Fri, Nov 18, 2016 at 01:29:07PM +0100, David Kalnischkies wrote: > > > You should also update your README.Debian and the descriptions

Bug#792163: Reviewing kipi-plugins dependencies

On Wednesday, November 16, 2016 9:11:56 AM CST you wrote: > On 16/11/16 06:49, Steve M. Robbins wrote: > > On Tuesday, November 15, 2016 2:05:27 PM CST Simon Frei wrote: > >> I second this request. Please make konqueror a suggested package instead > >> of a recommended

Bug#829645: src:gtest: Cannot build against libgtest-dev with std=c++11

Hi, On Mon, Jul 04, 2016 at 05:51:20PM -0700, Afif Elghraoui wrote: > Package: src:gtest > Version: 1.7.0-4 > Severity: important The googletest package has recently been updated to 1.8.0 and built with gcc 6. So I expect this issue is gone, but I'd like you to test it and let me know because I

Bug#844495: [pkg-boost-devel] Bug#844495: Bug#844490: FTBFS with boost1.62

On Wednesday, November 16, 2016 12:16:22 PM CST Thibaut Paumard wrote: > Control: tags 844490 +pending > Control: severity 844495 normal > > For the record, the bug appears when doing: > > acos(cos(alpha100)*cos(delta100)); > > where the type of alpha100 and delta100 is > boost::multiprecision::

Bug#844721: libgtest-dev isn't replacing dir with symlink on upgrade

On Fri, Nov 18, 2016 at 01:29:07PM +0100, David Kalnischkies wrote: > libgtest-dev contains in 1.8.0-1 a symlink to the new on-disk location. > That works for new installs, but doesn't on upgrades ??? a user ends up > with an empty /usr/src/gtest in that case. You need to work with > maintainersc

Bug#792163: Reviewing kipi-plugins dependencies

On Tuesday, November 15, 2016 2:05:27 PM CST Simon Frei wrote: > I second this request. Please make konqueror a suggested package instead > of a recommended. Digikam is aiming to be a cross-platform/-DE > applications, especially since version 5 where many parts have been > ported to QT from KDE fr

Bug#844373: ros-image-common: FTBFS (incompatible build-dependencies)

On Tuesday, November 15, 2016 1:02:10 AM CST Santiago Vila wrote: > Package: librospack-dev,libgtest-dev,src:ros-image-common > Severity: serious > > Dear maintainer: > > I tried to build ros-image-common in stretch with "dpkg-buildpackage -A" > (which is what the "Arch: all" autobuilder would do

Bug#841412: digikam: FTBFS: error with opencv 3.1

On Thu, Oct 20, 2016 at 07:13:38PM +0900, Nobuhiro Iwamatsu wrote: > Source: digikam > Version: 5.2.0-1 > Severity: important > Justification: fails to build from source > > Dear Maintainer, > > I am scheduled to transition of opencv. >https://release.debian.org/transitions/html/auto-opencv.h

Bug#774053: bug digikam

On Wed, Jul 06, 2016 at 08:38:14PM +0200, Luc Castermans wrote: > I observe similar behaviour, also with CPU remaining at 100%. Below I used > strace(). You can see > I needed to kill the process to get rid of it. Was this with Digikam version 4.4.0, as the original poster? -Steve signature.a

Bug#838152: kipi-plugins: Missing dependencies on KDE packages

On Sat, Sep 17, 2016 at 09:50:12PM +0200, Eike von Seggern wrote: > after installing digikam with kipi-plugins on a non-KDE system, I cannot > export files via 'Export->Export to remote storage'. On stderr, I get > messages similar to: > "klauncher not running" > "no service file for klauncher

  1   2   3   4   5   6   7   8   9   10   >