Bug#727656: Status of libpaper fork

On Wed, 24 Apr 2024 at 22:03, Bastian Germann wrote: > > I have seen Simon's post about this. The new gnulib package has a new > README that describes how to use the Debian > package. There is a slight chance that FTP Masters might intervene in > having a git bundle in a package because their >

Bug#727656: Status of libpaper fork

On Tue, 19 Mar 2024 at 21:46, Reuben Thomas wrote: > On Tue, 19 Mar 2024 at 21:37, Bastian Germann wrote: > >> >> As nobody has provided any patch yet and I do not have an idea how to use >> gnulib properly generally and in Debian >> context, I came up with this

Bug#1066203: recode: FTBFS: error.c:197:43: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration]

On Wed, 27 Mar 2024 at 20:25, Santiago Vila wrote: > > When I had already a bunch of them, I realized there is a macro > STDC_HEADERS which is not properly detected. Ah, I suspect the configure code is too old. Regenerating configure etc. (autoreconf) might help. -#if STDC_HEADERS > +#if

Bug#727656: Status of libpaper fork

On Tue, 19 Mar 2024 at 21:37, Bastian Germann wrote: > > As nobody has provided any patch yet and I do not have an idea how to use > gnulib properly generally and in Debian > context, I came up with this. I have actually tried to use Debian's gnulib > but could not get the thing to work. > Fair

Bug#727656: Status of libpaper fork

On Mon, 18 Mar 2024 at 23:33, Bastian Germann wrote: > Hi, > > I have updated the salsa repo to build without gnulib. > Fantastic, thanks for doing this! I am a little puzzled, I thought that the idea was to build with Debian gnulib? I think that could be a simpler patch. Looking at the

Bug#809931: org-mode: Correction to report

On Thu, 24 Aug 2023 at 01:40, Nicholas D Steeves wrote: > > Wow, it seems no one saw this bug for quite some time... I recently did > some Debian Emacsen Team uploads for org-mode, and I noticed that the > following are not currently installed in the elpa-org package: > >

Bug#1040430: ddclient: Upstream is unmaintained

Package: ddclient Version: 3.9.1-7 Severity: important Tags: upstream As of yesterday, upstream has marked the project unmaintained and archived the GitHub project. See https://github.com/ddclient/ddclient/ I and at least one other person offered to take over the project; unfortunately, since

Bug#1002514: psutils: New major release with PDF support

Package: psutils Version: 1.17.dfsg-4 Followup-For: Bug #1002514 As an encouragement to update psutils in Debian, I have just released version 3, which adds full support for PDF, with transparent filetype detection, using exactly the same commands as before. I have rewritten the package

Bug#1036309: xdg-utils: xdg-mime pauses for around 2 seconds running xprop to detect XFCE

Package: xdg-utils Version: 1.1.3-4 Severity: normal I was noticing that xdg-mime was very slow on one system; this turned out to be a server where I did not have a desktop environment, so xdg-mime was going through all of its DE checks every time. Commenting out the calls to “xprop” fixed it;

Bug#1013933: xsane: Another vote for XSane!

Package: xsane Version: 0.999-11ubuntu1 Followup-For: Bug #1013933 Thanks for keeping XSane alive in Debian. I am a long-time user myself, out of necessity: I have tried several times to use simple-scan (the only alternative I can find), and it just doesn’t offer the functionality of XSane.

Bug#1032427: xsane: Help>Show license does nothing

Package: xsane Version: 0.999-11ubuntu1 Severity: minor When I select Help→Show license, nothing happens. -- System Information: Debian Release: bookworm/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), (100, 'jammy-backports')

Bug#1032426: xsane: Help>About XSane crashes without opening a window

Package: xsane Version: 0.999-11ubuntu1 Severity: normal If I select Help→About XSane, the application pauses for a couple of seconds then crashes. (The changes in Ubuntu’s version are just to depend on a different JPEG library, so I think it’s reasonable to file a bug here.) -- System

Bug#1032173: identity recoding is too identical

On Wed, 1 Mar 2023 at 01:33, Zefram wrote: > > The invocation with both encodings the same superficially looks like > it's requesting an identity transformation, and it would correctly have > the behaviour of an identity transformation on input that were correctly > encoded. Because of the

Bug#1030140: rsyslog: Property-basesd filters are prevented from working by systemd config

On Wed, 1 Feb 2023 at 17:04, Michael Biebl wrote: > Am 31.01.23 um 16:05 schrieb Reuben Thomas: > > Package: rsyslog > > Version: 8.2112.0-2ubuntu2.2 > > This appears to be an Ubuntu version not known in the Debian archive > Apologies. > > Severity: normal &

Bug#992024: Enthusiastic support

I found this bug when I was about to file a WNPP bug myself. I just installed AirSane from source on my Ubuntu system and was delighted by how well it worked, and how easy it was. -- https://rrt.sc3d.org

Bug#1030144: scanbd: systemd and inetd configurations clash

Package: scanbd Version: 1.5.1-6build1 Severity: important When I first installed scanbd, I found that the systemd unit could not start, because inetd was already listening on the scanbd port. It seems to me that scanbd should only configure one of systemd or inetd when it installs. In

Bug#1030140: rsyslog: Property-basesd filters are prevented from working by systemd config

Package: rsyslog Version: 8.2112.0-2ubuntu2.2 Severity: normal In order to work around a bug in scanbd (#901695), I tried to add a property-based filter as /etc/rsyslog.d/99-scanbd.conf: :msg, regex, "/usr/sbin/scanbd: abandon polling of" ^/usr/local/sbin/restart-scanbd The filter appeared to

Bug#901695: Bug does not appear to depend on device name changing; workaround suggested

I am experiencing the same issue with a Canon 9000F scanner: when I switch the scanner off then back on, scanbd fails to reconnect to it. The error message is identical (mutans mutatis) to that in the logs posted here, but in my case `scanimage -L` shows that the device name has not changed.

Bug#1030139: scanbd: Please allow MaxConnections=2 for scanbm.socket service

Package: scanbd Version: 1.5.1-6build1 Severity: normal I am using the excellent AirSane (sadly unpackaged for Debian): https://github.com/SimulPiscator/AirSane In order to get it to work, I had to increase MaxConnections to 2 for the scanbm.socket systemd unit file. I am sorry, it took me

Bug#1030137: build-rdeps: does not notice when dose-ceve is killed

Package: devscripts Version: 2.22.1ubuntu1 Severity: normal I was puzzled by getting no results from build-rdeps; running with --debug did not help. Finally, I ran the dose-ceve command manually, and found out that it was being killed because it used more memory than the VM I was using had

Bug#1024789: xdg-utils: xdg-screensaver does not work on recent GNOME, and I have a fix

Package: xdg-utils Version: 1.1.3-4.1ubuntu3~22.04.1 Severity: important Tags: patch upstream I’m the upstream maintainer of Caffeine, and noticed that it was no longer working on my GNOME 42 system. Of course, the actual bug was in xdg-screensaver: until recently, gnome-screensaver ran on GNOME

Bug#996894: colordiff: Error messages interrupt output

Package: colordiff Version: 1.0.18-1 Severity: normal Error messages are not correctly interleaved with output; for example: -Foo diff: bar/baz.html+Bar : No such file or directory Here, the error message should say diff: bar/baz.html: No such file or directory but the (presumably stderr)

Bug#991340: ukui-polkit: Package description is hard to understand

Package: ukui-polkit Version: 1.2.1-1 Severity: normal The package description doesn’t make sense: “The ukui-polkit package supports general authentication and biometric authentication that the service is provided by the biometric-auth package. “ The problem is the words

Bug#149873: mmv: Options for dealing with this problem

Thanks, Axel for your kind words, and also for your analysis. I've had a look at renameutils, of which I was not aware, though I have it installed on my machine already! It seems to me that it covers interactive usage neatly, so I'd be happy to remove that from mmv, retaining the -n flag, but

Bug#149873: mmv: Options for dealing with this problem

Package: mmv Version: 1.01b-19build1 Followup-For: Bug #149873 Hi, I’m the (new) upstream maintainer of mmv, and I would like to fix this problem. Clearly, it is not possible to fix in a backwards-compatible way, so I see a few options: 1. Fix it in a backwards-incompatible way. For an

Bug#824223: dehydrated: Example cron script

Package: dehydrated Version: 0.6.5-1 Followup-For: Bug #824223 An example cron job script is provided by the hosting company Mythic Beasts at: https://www.mythic-beasts.com/support/domains/letsencrypt_dns_01 /etc/cron.daily/dehydrated: #!/bin/sh exec /usr/bin/dehydrated -c

Bug#969473: Please don't close bugs automatically, move them to enchant 2

Enchant 2 is just a new version of Enchant, only a separate package for ease of transition, so please reassign bugs to it rather than mass closing. (I'm the upstream maintainer!) -- https://rrt.sc3d.org

Bug#980374: cron: English fix for crontab(5)

Package: cron Version: 3.0pl1-136ubuntu1 Severity: minor [I checked this against other bugs, so I think it’s not already been reported.] The sentences: Please note that startup, as far as @reboot is concerned, is the time when the cron(8) daemon startup. In particular, it may be before

Bug#976172: xfonts-utils: fonttosfnt gives error "Couldn't select character map"

Package: xfonts-utils Version: 1:7.7+6 Severity: normal It seems that the call to FT_Select_Charmap at read.c:231 does not work for some fonts, at least. I tried it with a Latin-1 encoded BDF font. By default, fonttosfnt wants to reencode as Unicode, which is fine. Freetype finds the Latin-1

Bug#976159: xfonts-utils: bdftopcf(1) documentation of some flags is misleading

Package: xfonts-utils Version: 1:7.7+6 Severity: normal The -t and -i flags for bdftopcf are documented thus: -t When this option is specified, bdftopcf will convert fonts into "terminal" fonts when possible. A terminal font has each glyph image padded to the same

Bug#975056: libpodofo-utils: Typo in man page podofoimpose(1)

Package: libpodofo-utils Version: 0.9.6+dfsg-5build1 Severity: minor The word “interpretor” should be “interpreter” everywhere. Thanks for packaging PoDoFo! -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500,

Bug#974945: Acknowledgement (xsane: Resolution of saved images does not match scan resolution)

Having looked into this further, I think this may be a bug in the proprietary lexmark_nscan backend: it provides an option --scan-resolution, which is available in "Standard options", but (I am guessing) not the standard "resolution" option. Therefore, xsane can't tell that it supports different

Bug#974945: xsane: Resolution of saved images does not match scan resolution

Package: xsane Version: 0.999-8ubuntu2 Severity: minor The resolution of saved PNMs is hardwired to 72dpi. Is there a good reason for that? If not, I would be happy to prepare a patch that sets the resolution of the PNM to the scan resolution. Similarly, and perhaps it is the same problem, it

Bug#970244: libx11-data: Some comments in en_US.UTF-8 confuse "UP TACK" and "DOWN TACK"

Package: libx11-data Version: 2:1.6.9-2ubuntu1.1 Severity: minor In the following lines, “UP” should be “DOWN” and vice versa. U+22a5 is the “UP TACK” and U+22a4 is the “DOWN TACK”. See e.g. https://util.unicode.org/UnicodeJsps/character.jsp?a=22A4

Bug#970203: xdg-screensaver: does not work on windows with no title or non-ASCII title

Package: xdg-utils Version: 1.1.3-2ubuntu1 Severity: normal Tags: patch Here is the upstream bug and patch: https://gitlab.freedesktop.org/xdg/xdg-utils/-/issues/98 Owing to the glacial rate of xdg-maintenance currently (and with thanks to those currently trying to speed the process up!) it

Bug#964257: Correctly handle apostophes in English dictionaries

Package: hunspell-en-us Version: 1:2019.10.06-1 Followup-For: Bug #964257 It is worth noting that quotation marks are correctly handled by hunspell-en-gb, which has a different source package (libreoffice-dictionaries). (I declare an interest as the upstream maintainer of the meta-spellchecker

Bug#608013: recode h..us doesn't replace with ASCII equivalents

On Sun, 26 Dec 2010 07:58:49 +0800 jida...@jidanni.org wrote: > > I note that recode --force h..us causes » to disappear, when it > could easily better make a >>, or " like uni2ascii -B. In other words, doing something with `--force` can go wrong. Not a bug. > OK, recode h..utf8|uni2ascii -B

Bug#754945: recode: A possible buffer overflow when the input filename is too long

On Thu, 12 Jan 2017 18:19:51 +0300 Alexander Gerasiov wrote: > Package: recode > Version: 3.6-23 > Followup-For: Bug #754945 > > Another possible solution would be dinamically allocate buffer for > output_name. Please see patch attached. This is already done in recode 3.7.

Bug#607021: -k doesn't work (fwd)

This is fixed in current 3.7.7.

Bug#969388: debsums: Add bash completion

Package: debsums Version: 2.2.5 Severity: wishlist Tags: patch Here are bash completions for debsums. The implementation of _comp_dpkg_installed_packages() is from dpkg’s bash completions; I don’t know whether there’s a way to share them? Or, since /usr/share/bash-completion/completions/dpkg is

Bug#961136: recode: Consider switching upstream and package new version (3.7.1)?

On Wed, 20 May 2020 at 16:24, Boyuan Yang wrote: > According to https://www.gnu.org/software/recode/ , the new upstream > of package recode is now https://github.com/rrthomas/recode . GNU > is no longer hosting this software. Please consider switching the > upstream and package new version

Bug#956881: enchant: Keep out of bullseye

Upstream Enchant maintainer (and DM) here! I'm delighted to see the transition is happening; if there are any problems with Enchant 2, I'm very happy to help. I am not sure which Debian notifications I get about Enchant, so if I seem to overlook something that could use my attention, feel free to

Bug#952732: recode: Incorrect encoding of some characters when recoding to HTML_1.1

On Fri, 28 Feb 2020 at 09:00, Paul Courbis BV wrote: >* What was the outcome of this action? >Incorrect HTML code : > > As far as I can tell from looking at the code, these names are correct for HTML 1.1. The new names are used in HTML 1.2 (

Bug#949851: systemd-cron: Typo in package description: "dirrectly" should be "directly"

Package: systemd-cron Version: 1.5.13-1 Severity: minor In the package description: "dirrectly" should be "directly" -- System Information: Debian Release: buster/sid APT prefers bionic-updates APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 'bionic'), (100,

Bug#940146: perforate FTCBFS: does not pass cross tools to make

On Fri, 13 Sep 2019 at 05:33, Helmut Grohne wrote: > Source: perforate > Version: 1.2-5.1 > Tags: patch > User: debian-cr...@lists.debian.org > Usertags: ftcbfs > > perforate fails to cross build from source, because it does not pass > cross tools to make. The easiest way of doing so - using

Bug#929000: sloccount: --autogen flag seems not to work

Package: sloccount Version: 2.26-5.2 Severity: normal If I have files foo.py and foo.py.in, and run sloccount foo.py, I get no lines counted. The same happens for foo.py.in (perhaps because sloccount does not recognise “.in” as a language?). So I try sloccount --autogen foo.py, but that still

Bug#926988: gengetopt: Package long description is outdated

Package: gengetopt Version: 2.22.6+dfsg0-2 Severity: minor Gengetopt does not generate a skeleton main.c (presumably it once did); instead, it generates a command-line parser, and a header. I suggest the following wording for the long description: gengetopt reads an interface description file,

Bug#920529: libtool: Please cherry-pick upstream commit f9970d99 to support -fuse-ld=

Package: libtool Version: 2.4.6-2 Severity: wishlist Currently it’s not possible to use -fuse-ld=gold, for example, cleanly with libtool. This upstream commit: http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=f9970d99293faf908fdc153a653fa5781095fb7a adds the requisite support. -- System

Bug#916120: automake: "info automake" does not work (has to be "info automake-1.xx")

Package: automake Version: 1:1.15.1-3ubuntu2 Severity: minor Running “info automake” does not work. It would be nice if the automake package installed suitable links or whatever to the actual, versioned, info file. (I understand that the existence of the automake1.11 package requires the

Bug#907222: Preferences: Tracks>Spectrograms panel (only) does not respect GTK theme

Package: audacity Version: 2.2.1-1 Severity: normal The Debian package seems to be patched to make Audacity work properly with dark themes (thanks very much!). Oddly, the Tracks>Spectrograms panel of Preferences still does not work in this regard: the background comes up white with white text on

Bug#639221: replace folding.el with elpa-folding

On Mon, 25 Jun 2018, 23:47 Nicholas D Steeves, wrote: > > Given that whatever we do will require a new source package in the > archive, maybe it would be a good time to consider alternative folding > addons? Jaalto's project of course wins for backwards-compatibility ;-) For my purposes, an

Bug#891636: latexmk: Please do upload this

Package: latexmk Version: 1:4.41-1 Followup-For: Bug #891636 It would be great to have this, as I am finding bugs in latexmk 4.41 that are fixed since then, and already it is too late for Ubuntu 16.04. It would be nice not to have to work around these bugs, or have to install a newer version of

Bug#890019: zile testsuite fails with TERM=unknown

On 10 February 2018 at 17:48, Axel Beckert <a...@debian.org> wrote: > Hi Reuben, > > Reuben Thomas wrote: > >​I just want to check, do you nonetheless consider this an upstream > > bug? > > No. And my fix is adding "env TERM=vt100" debian/rules. :-) >

Bug#890019: zile testsuite fails with TERM=unknown

On 10 February 2018 at 09:52, Axel Beckert wrote: > Control: tag -1 + confirmed > > Hi Matthias, > > Matthias Klose wrote: > > make check-TESTS check-local > > make[5]: Entering directory '/<>' > > echo ./tests/*.el ./tests/interactive/*.el | abs_srcdir=/<> > > srcdir=.

Bug#890019: zile testsuite fails with TERM=unknown

On 10 February 2018 at 08:25, Matthias Klose wrote: > Package: src:zile > Version: 2.4.14-5 > > The zile tests apparently expect a working terminal. Please set it > explicitly > when running the tests, e.g. TERM=xterm. > ​See tests/Makefile.am: TERM ?= vt100 This suggests

Bug#888320: python2.7: Please supply Valgrind suppressions file

Package: python2.7 Version: 2.7.12-1ubuntu0~16.04.3 Severity: minor README.Valgrind, which is supplied (thanks) mentions valgrind-python.supp, which I can’t find (it comes from the Misc/ directory of the sources). This would be really handy to have installed in /usr/lib/valgrind for ease of

Bug#748984: Info received (recode: This would need some extra design and coding)

I have made an issue for this in the Recode bug tracker: https://github.com/rrthomas/Recode/issues/1

Bug#638144: Added to Recode bug tracker

I have made an issue for this: https://github.com/rrthomas/Recode/issues/2

Bug#748984: recode: This would need some extra design and coding

Package: recode Version: 3.6-22 Followup-For: Bug #748984 The problem with fixing this is that currently recode effectively assumes that the HTML input is ISO-8859-1 encoded; it has no notion of the encoding separate from its being in HTML. I’m not exactly sure, but it seems to me that HTML (and

Bug#348909: recode: This is a problem with iconv's API

Package: recode Version: 3.6-22 Followup-For: Bug #348909 I looked into this bug. The problem starts with the fact that iconv returns EILSEQ (invalid input) when in fact the input is simply untranslatable. It is possible to diagnose this situation by running another conversion with the output

Bug#321437: recode: Seems to be fixed in 3.7

Package: recode Version: 3.6-22 Followup-For: Bug #321437 I just tested this with the upcoming 3.7, and it seems to be fixed. I put the given text in a file foo.txt, then: $ cat foo.txt|recode "utf8..iso-8859-1" recode: Invalid input in step `UTF-8..ISO-8859-1' $ cat foo.txt|recode -f

Bug#363502: closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#877240: Removed package(s) from unstable)

On 19 November 2017 at 20:46, Vincent Lefevre wrote: > BTW, since readline6 has been replaced by readline7: I have not tried > readline7. If it has the same problem, then I suppose that this bug > should be reopened and reassigned to readline7. > ​My notes suggested that

Bug#363502: closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#877240: Removed package(s) from unstable)

he archive administrators by mailing > ftpmas...@ftp-master.debian.org. > > Debian distribution maintenance software > pp. > Scott Kitterman (the ftpmaster behind the curtain) > > -- Forwarded message -- > From: Reuben Thomas <r...@sc3d.org> > To: Debian Bug Tracking Syst

Bug#617242: mlmmj-make-ml does not ensure correct permissions for created files and directories

On 6 November 2017 at 03:07, Chris Knadle wrote: > tag 617242 + moreinfo > thanks > > Although this bug is very old I think it deserves are maintainer response. > > > I have my umask set to 0027. If I run mlmmj-make-ml with sudo, then > > this umask is inherited, and

Bug#405444: perforate: Zum already does this

Package: perforate Followup-For: Bug #405444 I’m a bit puzzled by this bug report, as zum already reports space saved. However, it was out by a factor of (blksize / 512). This is fixed in the upcoming release 2.0. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates

Bug#449602: perforate: Fixed in upcoming 2.0

Package: perforate Followup-For: Bug #449602 Thanks, I’ve adapted the patch and it will be in the next release. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100,

Bug#412013: perforate: May be better in 2.0, but no specific fix

Package: perforate Followup-For: Bug #412013 The upcoming 2.0 version of zum uses cp, so it may work better. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100,

Bug#294297: perforate: Not much zum can do here

Package: perforate Version: 1.2-5.1 Followup-For: Bug #294297 I don’t think there’s much zum can do: sparseness is not something that file systems advertise. Putting the information in zum’s man page would inevitably lead to its being incomplete and/or out of date. zum is a low-level tool, so

Bug#412005: perforate: Explanation of behavior with no command-line args

Package: perforate Version: 1.2-5.1 Followup-For: Bug #412005 To clear up the confusion: when given no command-line arguments, zum reads a list of files to perforate from stdin. This behavior will be documented in the next release. (However, I would still be happy for a patch to perforate stdin,

Bug#412014: perforate: In fact, cp does perforate files, so no need for this

Package: perforate Followup-For: Bug #412014 cp does “perforate” files, even by default (see the --sparse option), so there’s no need for this. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500,

Bug#566998: perforate: This bug is a misunderstanding combined with a misfeature

Package: perforate Version: 1.2-5 Followup-For: Bug #566998 The reason that finddup fails in this case is that it was run in verbose mode (in two ways: first by passing the -v option, and secondly by passing the -n option, which implies -v). The verbose mode’s messages are sent to stdout, and so

Bug#169437: xzgv: Fixed in 0.9.2

Package: xzgv Tags: fixed-upstream Followup-For: Bug #169437 This is fixed in the upcoming 0.9.2, which adds “panoramic zoom”. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100,

Bug#869731: man-db: apropos does not work for directories found from PATH

On 26 July 2017 at 00:05, Colin Watson wrote: > > I think it might be worth revisiting the change in man-db 2.4.2-3 to > turn off MAN_DB_CREATES, which means that man doesn't create databases > that doesn't already exist (once the database exists, man should > automatically

Bug#869731: man-db: apropos does not work for directories found from PATH

On 25 July 2017 at 23:49, Colin Watson <cjwat...@debian.org> wrote: > On Tue, Jul 25, 2017 at 11:24:18PM +0100, Reuben Thomas wrote: > > I just noticed that man pages installed in ~/.local/share/man are not > found > > by apropos. This appears to be bec

Bug#869731: man-db: apropos does not work for directories found from PATH

Package: man-db Version: 2.7.5-1 Severity: normal I just noticed that man pages installed in ~/.local/share/man are not found by apropos. This appears to be because there’s no database for this directory. man finds the directory via the corresponding ~/.local/bin entry in PATH. It would be nice

Bug#864486: xsane: XSane writes bogus icm_profile field in output

Package: xsane Version: 0.999-3ubuntu1 Severity: normal Tags: patch xsane doesn’t initialise the icm_profile field of Image_info structs, and hence when saving edited images, it can write bogus information into this field, which causes some readers to barf, e.g. gthumb can no longer read the

Bug#862972: xsane: Typo in Preferences>Copy dialog

Package: xsane Version: 0.999-5 Severity: minor Tags: patch “Paper geometrie” → “Paper geometry” [In case the Version: header looks suspicious: I’m running 0.999-3ubuntu1, but I checked that this typo remains unfixed in the current 0.999-5.] -- System Information: Debian Release: stretch/sid

Bug#849517: The valgrind diagnostic is a false positive

On 14 April 2017 at 13:47, Florian Weimer <f...@deneb.enyo.de> wrote: > * Reuben Thomas: > > > ​A workaround is to build bash with --without-bash-malloc (but I presume > > there's a good reason not to do that?).​ > > FWIW, Fedora and Red Hat Enterprise Linux compil

Bug#849517: Alternative fix

A Valgrind maintainer pointed out that an alternative to disabling bash's malloc is to configure bash with CPPFLAGS=-DDISABLE_MALLOC_WRAPPERS=1. This disable the debugging wrappers that confuse valgrind. I guess it's still preferable not to do that. The obvious alternative is to ship either bash

Bug#849517: The valgrind diagnostic is a false positive

See: https://bugs.kde.org/show_bug.cgi?id=378732 https://lists.gnu.org/archive/html/bug-bash/2017-04/msg00042.html ​The problem, in short, is that valgrind does not intercept the malloc call (which is made via bash's built-in malloc), but does intercept the free call, and hence concludes that

Bug#713051: bash: in /etc/skel/.bashrc, check if bash_completion has already run before

Package: bash Version: 4.4-4 Followup-For: Bug #713051 This bug report is correct, however, the situation is a little more complicated. /etc/profile.d/bash_completion.sh already contains code that checks whether bash_completion has already run. Hence, there should be no need to uncomment the

Bug#856464: xdg-utils: Remove hard-wired fallbacks

Package: xdg-utils Version: 1.1.1-1ubuntu1.16.04.1 Severity: normal See https://bugs.freedesktop.org/show_bug.cgi?id=98509 The upstream maintainer of xdg-utils doesn’t think hard-wired fallbacks are useful for upstream, and this seems sensible. Perhaps they should be removed from the Debian

Bug#695179: psnup(1) has a confusing bit

On 21 January 2017 at 19:36, Ian Jackson wrote: > > In the absence of time to fix this properly by listing the available > units I have at least dropped the confusing sentence. > ​I have since become upstream, and have rewritten the documentation. I need to do a

Bug#809801: dailystrips: Correction to last update

Package: dailystrips Version: 1.0.28-11 Followup-For: Bug #809801 Apologies, my last update didn’t actually work. Here is a corrected version, which should also be more robust: class gocomics-srch homepage http://www.gocomics.com/$strip/ searchpage

Bug#809801: dailystrips: Further update

Package: dailystrips Version: 1.0.28-11 Followup-For: Bug #809801 The gocomics web site appears to have changed again. Here is a new gocomics-srch class definition; as before, only tested for Doonesbury. class gocomics-srch homepage http://www.gocomics.com/$strip/ searchpage

Bug#801067: Bug still present in nfs-utils 1.3.4-1

The README.Debian.nfsv4 file is now ten years old. My previous comments apply, only more so (owing to the passing of time). -- http://rrt.sc3d.org

Bug#796938: Bug still present in nfs-utils 1.3.4-1

This bug is still present, and the fix I give will still work. -- http://rrt.sc3d.org

Bug#725910: colormake: man page refers to non-existent configuration file

On 29 November 2016 at 20:04, Ludovic Rousseau <ludovic.rouss...@free.fr> wrote: > On Wed, 09 Oct 2013 23:54:23 +0100 Reuben Thomas <r...@sc3d.org> wrote: > >> Package: colormake >> Version: 0.9-1 >> Severity: minor >> >> colormake(1) refers

Bug#840793: emacsen-common: Making of symlinks to debian-startup.el breaks emacs-snapshot

Package: emacsen-common Version: 2.0.8 Severity: normal The problem is these lines in /usr/lib/emacsen-common/packages/install/emacsen-common: (cd /usr/share/${FLAVOR}/site-lisp ln -s ../../emacs/site-lisp/debian-startup.el .) The use of ../.. assumes that the Emacs installation is in /usr.

Bug#833191: offlineimap: Please add default value of sslcacertfile

On 8 September 2016 at 12:14, Ilias Tsitsimpis wrote: > > Currently, the man page does not document any of the available options > in the configuration file. These are documented in the example file: > /usr/share/doc/offlineimap/examples/offlineimap.conf.gz > > Maybe

Bug#833191: offlineimap: Please add default value of sslcacertfile

On 8 September 2016 at 11:48, Ilias Tsitsimpis wrote: > > I am afraid this cannot be done easily, because OfflineIMAP distinguish > between sslcacertfile having and not having a value. > [snip]​ This means that if Debian provides a default value for the > sslcacertfile,

Bug#682031: unison: Bash completion does not work

Package: unison-gtk Version: 2.48.3-1 Followup-For: Bug #682031 Update to my previous message: 1. I see after purging and reinstalling the package that the bash-completion file is indeed installed in /usr/share/bash-completion/completions/ , so my finding it in /etc/bash_completions.d appears to

Bug#833191: offlineimap: Please add default value of sslcacertfile

Package: offlineimap Version: 6.6.1+dfsg1-2 Severity: wishlist As a bit of Debian integration, it would seem reasonable to add a default value for sslcacertfile (/etc/ssl/certs/ca-certificates.crt). -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy:

Bug#642486: Acknowledgement (libgc-dev: Valgrind suppressions for libgc)

[​Apologies for not replying to comments on this bug sooner; for some reason I'm not getting emails about it.] I have tested "valgrind inkscape" with the *original* suppressions I supplied, and they work fine with inkscape 0.91/valgrind 3.11.0: inkscape starts up and runs. If I run without the

Bug#814552: chromium-browser: Please allow spelling to use user’s word lists

Package: chromium-browser Version: 48.0.2564.82-0ubuntu0.14.04.1.1108 Severity: normal Chromium, like many other Debian programs, uses hunspell for spelling. However, unlike most other apps that use hunspell directly or indirectly (e.g. Firefox, Pidgin, LibreOffice), Chromium uses a custom

Bug#784224: dailystrips: Slight simplification of xkcd

Package: dailystrips Version: 1.0.28-11 Followup-For: Bug #784224 I noticed I had a redundant “searchpage” setting in my previous definition. strip xkcd name xkcd homepage http://xkcd.com/ type search baseurl http://imgs.xkcd.com searchpattern

Bug#809801: dailystrips: Update to doonesbury

Package: dailystrips Version: 1.0.28-11 Severity: normal Here’s an updated definition: class gocomics-srch homepage http://www.gocomics.com/$strip/ searchpage http://www.gocomics.com/$strip/%Y/%m/%d type search searchpattern

Bug#809931: org-mode: Correction to report

Package: org-mode Version: 8.3.2-1 Followup-For: Bug #809931 The correct value for org-odt-data-dir is actually /usr/share/emacs/site-lisp/org-mode/etc (not …/styles as I previously said). -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500,

Bug#809931: org-mode: org-odt-data-dir is incorrectly set

Package: org-mode Version: 8.3.2-1 Severity: normal Exporting as ODT does not work, because org-odt-data-dir is set by default to /usr/share/emacs/etc/org, while the relevant files are installed in /usr/share/emacs/site-lisp/org-mode/etc/styles/ Either org-odt-data-dir should be set to the

Bug#801067: nfs-common: Remove or updated README.Debian.nfsv4

Package: nfs-common Version: 1:1.2.8-6ubuntu1.1 Severity: normal The README.Debian.nfsv4 file is now rather old; is NFSv4 really still considered experimental? Parts of this file may be worth keeping (I’m not an expert!), but at least that claim should be removed, and mention of kernel versions

  1   2   3   4   5   6   7   8   9   10   >