Bug#759410: bumping severity again

Control: severity -1 critical Control: tags -1 buster sid On 2016-12-04 13:26 -0800, Francois Marier wrote: > severity 759410 important > # usrmerge is not enabled by default anymore: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837928;msg=67 > thanks In debootstrap 1.0.102, usrmerge

Bug#904170: usrmerge: Please bump safe-rm version

On 2018-07-20 21:22 -0400, Jeremy Bicha wrote: > Source: usrmerge > Version: 18 > Severity: minor > X-Debbugs-CC: x...@debian.org > > Could you please bump usrmerge's Conflicts for safe-rm to (<< 0.12-4) ? That would not be correct, because… > This will allow Ubuntu to sync usrmerge. > >

Bug#903790: ncurses: parallel build failure

Am 20.07.2018 um 12:59 schrieb Helmut Grohne: > On Sun, Jul 15, 2018 at 12:30:22PM +0200, Sven Joachim wrote: >> Something like this, perhaps? >> >> , >> | make[1]: Entering directory '/<>/ncurses-6.1+20180210/obj-test' >> | gcc -g -O2 >>

Bug#904065: initramfs-tools: stderr reports "rmdir: failed to remove '/var/tmp/mkinitramfs_XXXXXX/var/cache/ldconfig': No such file or directory"

anyway. Failing to remove a directory because it did not exist in the first place is not a big deal, so this error message is just cosmetic. Below is a patch that fixes it. >From ca5373c7fee4e6928e50699eeb9cb40e63018957 Mon Sep 17 00:00:00 2001 From: Sven Joachim Date: Thu, 19 Jul 2018 11:22

Bug#903818: screen: should not try to link with -lelf

On 2018-07-15 14:04 +0200, Axel Beckert wrote: > Control: tag -1 + confirmed pending > > Hi Sven, > > I just noticed the following: > > Sven Joachim wrote: >> , >> | $ dpkg-deb -f screen-udeb_4.6.2-2_i386.udeb Depends >> | libc6-udeb (>= 2.27),

Bug#903790: ncurses: parallel build failure

Am 14.07.2018 um 22:43 schrieb Helmut Grohne: > Source: ncurses > Version: 6.1+20180210-4 > User: helm...@debian.org > Usertags: rebootstrap > Tags: unreproducible > > Hi Sven, > > Since very recently, I see a weird build failure for ncurses. I guess > that it is related to Ben's make-dfsg

Bug#903818: screen: should not try to link with -lelf

Source: screen Version: 4.6.2-2 Severity: normal Tags: fixed-upstream The latest upload has dropped libelf-dev from Build-Conflicts which is a welcome change. However, there is the problem that screen automagically links with -lelf if it is available, and screen-udeb then gains an unfulfillable

Bug#903708: xfce4: xfce fails to start with all methods

Control: reassign -1 xserver-xorg-core Control: forcemerge 900550 -1 On 2018-07-13 10:55 -0400, annadane wrote: > Package: xfce4 > Version: 4.12.4 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > On a fresh install of Sid (as in minimal Stable ->

Bug#903712: override: reportbug-gtk:utils/optional

Package: ftp.debian.org Severity: normal The reportbug-gtk package introduced in reportbug 7.5.0 has inherited priority standard from the source package. I think it should have priority optional instead, since it pulls in a lot of desktop libraries, and this is not appropriate for a "standard"

Bug#903376: libc6-amd64: installed package size has exploded

Control: reassign -1 binutils 2.30.90.20180627-1 Control: retitle -1 binutils: produces large 64-bit libraries on i386 Control: affects -1 libc6-amd64 libc6-x32 On 2018-07-09 11:19 +0200, Sven Joachim wrote: > Package: libc6-amd64 > Version: 2.27-4 > Severity: important > > On i3

Bug#903376: libc6-amd64: installed package size has exploded

Package: libc6-amd64 Version: 2.27-4 Severity: important On i386, libc6-amd64 and libc6-x32 install more than one gigabyte each: , | $ apt-cache show libc6-amd64 libc6-x32 | grep Installed-Size | Installed-Size: 1143839 | Installed-Size: 1143407 ` Looking at /lib64, all the .so files

Bug#903224: udev: Fails to upgrade

On 2018-07-08 03:05 +0200, Michael Biebl wrote: > Control: tags -1 moreinfo unreproducible > > Am 08.07.2018 um 00:26 schrieb Kurt Roeckx: >> Package: udev >> Version: 239-5 >> Severity: serious >> >> Hi, >> >> When upgrading udev, it failed to upgrade, because udev didn't >> want to start. I

Bug#849003: ncurses: drop the -dbg packages?

On 2016-12-21 18:44 +0100, Sven Joachim wrote: > Source: ncurses > Version: 6.0+20161126-1 > Severity: wishlist > > I would like to drop the -dbg packages when switching to the ncurses6 > ABI (#230990). One problem with them is that they are not > multiarch-coinstall

Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

On 2018-07-04 23:33 +0200, Michael Biebl wrote: > Control: tags -1 moreinfo > > > This is what I get when I build a package using pbuilder, which > build-depends on policykit-1 (which in turn pulls in libpam-systemd): > > The following packages have unmet dependencies: > systemd : Breaks:

Bug#902448: timidity: Breaks: timidity-daemon (>= 2.14.0-1~) but 2.14.0-5 is to be installed

Package: timidity Version: 2.14.0-5 Severity: serious In this version, timidity-daemon has become uninstallable: , | $ LANG=C aptitude -s install timidity-daemon | The following packages will be upgraded: | timidity{b} timidity-daemon | The following packages are RECOMMENDED but will NOT

Bug#902438: tracker.debian.org: broken links in VCS field

Package: tracker.debian.org Severity: normal In the VCS field on https://tracker.debian.org/pkg/$package there are three new links labeled changelog_distribution, changelog_version and package_version. Unfortunately they are all 404 compliant.

Bug#550756: dash: accepts a lone "fi"

Control: tags -1 + fixed-upstream On 2009-10-12 20:11 +0200, Jakub Wilk wrote: > Package: dash > Version: 0.5.5.1-3 > Severity: normal > > $ bash -c ":;fi" && echo OK > bash: -c: line 0: syntax error near unexpected token `fi' > bash: -c: line 0: `:;fi' > > $ zsh -c ":;fi" && echo OK > zsh:1:

Bug#794965: Dash fail to remove trailing spaces.

Control: tags -1 + fixed-upstream On 2015-08-08 15:43 -0400, Bize Ma wrote: > Package: dash > Version: dash: 0.5.7-3 > > This two commands: > > dash -c 'echo "a b " | { read var; echo "<$var>"; }' > bash -c 'echo "a b " | { read var; echo "<$var>"; }' > > produce: > > > > > > >

Bug#902268: debhelper: skips multilib packages when building ncurses

On 2018-06-24 08:22 +, Niels Thykier wrote: > Niels Thykier: >> Sven Joachim: >>> Package: debhelper >>> Version: 11.3.3 >>> Severity: serious >>> >> >> Hi Sven, >> >> Are you certain it is introduced in 11.3.3? Th

Bug#902268: debhelper: skips multilib packages when building ncurses

Package: debhelper Version: 11.3.3 Severity: serious Doing a test build of ncurses, I noticed that the dh_* tools skipped the multilib packages, resulting in an incomplete build. This is reproducible on both i386 and amd64. , | $ grep -B1 "All requested packages have been excluded"

Bug#902264: dictd: post-installation fails

On 2018-06-24 00:17 -0400, Vincent Lefevre wrote: > Package: dictd > Version: 1.12.1+dfsg-5 > Severity: grave > Justification: renders package unusable > > I got the following error during the installation: > > E: Sub-process /usr/bin/dpkg returned an error code (1) > Setting up dictd

Bug#861343: debootstrap: hardcodes mawk as awk provider

on't have a local mirror where I could swap the priorities of mawk and original-awk (or gawk). Cheers, Sven >From 52b84c8693d99fe877d9e612881503fe28c39210 Mon Sep 17 00:00:00 2001 From: Sven Joachim Date: Fri, 28 Apr 2017 09:23:20 +0200 Subject: [PATCH] Handle case where some other awk than mawk

Bug#902185: udev: fails to configure with systemd 238-5

Package: udev Version: 239-1 Severity: serious Upgrading udev from 238-5 to 239-1 failed on two machines here, where I did not upgrade systemd at the same time. Upgrading systemd as well, before udev or in the same run, fixed that in both cases. I guess the Breaks on systemd needs to be bumped

Bug#901843: ncurses-base: bad error message "Cannot find terminfo entry for 'xterm-256color'."

Am 19.06.2018 um 21:55 schrieb w...@chaos.in-kiel.de: > And I just got an idea... > > $ ps $(pgrep screen) > PID TTY STAT TIME COMMAND > 2631 ?Ss17:26 SCREEN -d -m -S IRC irssi > 7083 pts/0Ss+0:00 screen -xRR IRC > # ls -la /proc/2631/exe > lrwxrwxrwx 1 root root 0

Bug#901843: ncurses-base: bad error message "Cannot find terminfo entry for 'xterm-256color'."

Am 19.06.2018 um 11:07 schrieb w...@chaos.in-kiel.de: > I regularly connect (via mosh) to remote machine from my desktop and > reattach to a "screen" there. For some time now, screen on the remote > machine reports > > Cannot find terminfo entry for 'xterm-256color'. > > and quits. > > After some

Bug#900839: libncurses-dev: static linking requires -lgpm

On 2018-06-06 18:09 -0400, Thomas Dickey wrote: > On Wed, Jun 06, 2018 at 11:08:18PM +0200, Sven Joachim wrote: >> On 2018-06-06 16:09 -0400, Thomas Dickey wrote: >> >> > On Wed, Jun 06, 2018 at 07:39:42PM +0200, Sven Joachim wrote: >> >> On 2018-0

Bug#901650: libreadline-dev: please ship readline.pc

Package: libreadline-dev Version: 7.0-5 Severity: wishlist It would be nice to have readline.pc included in libreadline-dev, it gives a standard way to check for the libs needed to link with -lreadline. Right now there are many reverse dependencies of libreadline which needlessly link with

Bug#900987: libncurses-dev: feature test macros in compiler flags

Control: tags -1 upstream On 2018-06-07 19:11 +0200, Jakub Wilk wrote: > Package: libncurses-dev > Version: 6.1+20180210-4 > > The compiler flags that are supposedly needed to compile with ncurses > include feature test macros: > > $ ncurses6-config --cflags > -D_GNU_SOURCE -D_DEFAULT_SOURCE

Bug#901225: libell-dev: missing dependency on libell0

Package: libell-dev Version: 0.4-1 Severity: serious Your package is lacking a dependency on libell0 (= ${binary:Version}), without it dynamic linking is not going to work: , | $ sudo aptitude install libell-dev | [...] | $ file

Bug#885584: jessie-pu: package ncurses/5.9+20140913-1+deb8u3

On 2018-06-08 21:26 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Thu, 2017-12-28 at 11:43 +0100, Sven Joachim wrote: >> > The same problem with the same fix as in #885582 for stretch. > > Please go ahead. Apologies for the very long delay. U

Bug#901129: timidity: removes conffile belonging to timidity-daemon

Package: timidity Version: 2.14.0-2 Severity: serious When upgrading timidity and timidity-daemon from 2.13.2-41 the following happened (sorry for the German): , | Vorbereitung zum Entpacken von .../timidity_2.14.0-2_i386.deb ... | Entpacken von timidity (2.14.0-2) über (2.13.2-41+b1) ... |

Bug#900839: libncurses-dev: static linking requires -lgpm

On 2018-06-06 16:09 -0400, Thomas Dickey wrote: > On Wed, Jun 06, 2018 at 07:39:42PM +0200, Sven Joachim wrote: >> On 2018-06-05 21:43 +0200, Sven Joachim wrote: > ... >> >> | >> >> /usr/lib/gcc/i686-linux-gnu/7/../../../i386-linux-gnu/libncurse

Bug#896979: xserver-xorg-video-nouveau: Crash when undocking Lenovo P50

ops); >> break; >> } >> drmModeFreeProperty(props); >> } >> } >> >> Examining some variables: >> >> (gdb) p i >> $7 = 0 >> >

Bug#900839: libncurses-dev: static linking requires -lgpm

On 2018-06-05 21:43 +0200, Sven Joachim wrote: > On 2018-06-05 21:01 +0200, Sven Joachim wrote: > >> Package: libncurses-dev >> Version: 6.1+20180210-4 >> Severity: normal >> >> Linking a program as trivial as the following statically fails:

Bug#900839: libncurses-dev: static linking requires -lgpm

On 2018-06-05 21:01 +0200, Sven Joachim wrote: > Package: libncurses-dev > Version: 6.1+20180210-4 > Severity: normal > > Linking a program as trivial as the following statically fails: > > #include > > int main(void) > { > initscr(); &

Bug#900839: libncurses-dev: static linking requires -lgpm

Package: libncurses-dev Version: 6.1+20180210-4 Severity: normal Linking a program as trivial as the following statically fails: #include int main(void) { initscr(); endwin(); return 0; } , | $ LANG=C gcc curses_min.c -static $(pkg-config --static --libs ncurses) |

Bug#893934: openssh-client: Potentially unintended dependency on libbsd

On 2018-04-20 01:24 +0200, Guillem Jover wrote: > On Tue, 2018-04-03 at 12:39:54 +0100, Colin Watson wrote: >> Control: reassign -1 libedit-dev 3.1-20170329-1 >> >> On Sat, Mar 24, 2018 at 02:37:57AM +0100, Guillem Jover wrote: >> > I just noticed that the latest version of this package depends

Bug#900514: nmu: gnucobol_2.2-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Another case of a package which was uploaded before the ncurses transition and got stuck in NEW for too long. nmu gnucobol_2.2-1 . amd64 . unstable . -m "Rebuild against libncurses6."

Bug#900239: libprocps-dev: symlink to libprocps.so broken in /usr/lib

Control: tags -1 + patch On 2018-05-27 23:43 +0200, Stanislaw Halik wrote: > Package: libprocps-dev > Version: 2:3.3.15-1 > Severity: normal > > Hey, > > The libprocps-dev package depends on `libprocps7' but contains a broken > symlink to `libprocps.so.6' in the /usr/lib search path. > >

Bug#899394: ncurses-base: Add Breaks on libmono-corlib4.5-cil (<< 4.6.2.7+dfsg-2)

Control: block 899394 by 899395 On 2018-05-23 19:27 +0200, Sven Joachim wrote: > Package: ncurses-base > Version: 6.1+20180210-4 > Severity: normal > > It has been noticed in #899112 and #899222 that Mono's > System.TermInfoReader is incompatible with the new terminfo format.

Bug#899395: mono: FTBFS on various architectures

Source: mono Version: 4.6.2.7+dfsg-2 Severity: serious The new mono version FTBFS on four architectures where it has been built before, including two release architectures. On S390x, the error looks like this[1]: , | CC mono-mmap.lo | libtool: compile: gcc -DHAVE_CONFIG_H -I.

Bug#899394: ncurses-base: Add Breaks on libmono-corlib4.5-cil (<< 4.6.2.7+dfsg-2)

Package: ncurses-base Version: 6.1+20180210-4 Severity: normal It has been noticed in #899112 and #899222 that Mono's System.TermInfoReader is incompatible with the new terminfo format. The Debian mono maintainers kindly fixed that in version 4.6.2.7+dfsg-2, and so versioned Breaks should be

Bug#899323: rxvt-unicode-256color terminfo entry moved to ncurses-base

Package: rxvt-unicode Version: 9.22-3 Severity: minor Tags: patch In the latest ncurses upload I have moved the rxvt-unicode-256color terminfo entry to ncurses-base, see #898948. This does not require immediate action from you, but could you please prefer ncurses-base (>= 6.1+20180210-4) over

Bug#899282: libbsd0: bsd-mailx segfaults

Package: libbsd0 Version: 0.9.0-1 Severity: serious Today I have received a mail from the daily cron job, and to my surprise /usr/bin/mail (pointing to bsd-mailx) crashed when it accessed it. Downgrading libbsd0 to version 0.8.7-1.1 fixed that, here is a backtrace: , | % gdb =mail | Reading

Bug#899248: debhelper: upstream changelog no longer installed

On 2018-05-21 16:28 +, Niels Thykier wrote: > Control: tags -1 patch > Control: severity -1 serious > > On Mon, 21 May 2018 17:05:54 +0200 Sven Joachim <svenj...@gmx.de> wrote: >> Package: debhelper >> Version: 11.3 >> >> Upon rebuilding (binary

Bug#899248: debhelper: upstream changelog no longer installed

On 2018-05-21 17:05 +0200, Sven Joachim wrote: > Package: debhelper > Version: 11.3 > > Upon rebuilding (binary-arch only) ncurses with debhelper 11.3, I found > that lintian would notice missing upstream changelogs: > > , > | P: libtinfo6: no-upstream-changelog >

Bug#899248: debhelper: upstream changelog no longer installed

Package: debhelper Version: 11.3 Upon rebuilding (binary-arch only) ncurses with debhelper 11.3, I found that lintian would notice missing upstream changelogs: , | P: libtinfo6: no-upstream-changelog | P: libtinfo5: no-upstream-changelog | P: lib64tinfo6: no-upstream-changelog | P:

Bug#897953: dvtm: Please stop shipping dvtm and dvtm-256color terminfo entries

On 2018-05-12 16:23 +0300, kact...@gnu.org wrote: > control: tags -1 +pending > > [2018-05-05 08:29] Sven Joachim <svenj...@gmx.de> >> In early 2017, the dvtm and dvtm-256color terminfo entries were added to >> ncurses upstream, and I would like to include them in

Bug#899224: pbuilder: cannot pass -g in --debbuildopts

Package: pbuilder Version: 0.229.2 It does not seem to be possible to perform a build with passing -g (aka --build=source,all) to dpkg-buildpackage via -debbuild-opts. When I did that, the build failed at the end, because pbuilder expected the wrong .changes file: , |$ pdebuild --

Bug#897537: tudu: FTBFS: ./configure: 394: ./configure: rmtest.c: not found

Control: reassign -1 acr 1.6.1-1 On 2018-05-15 14:42 +0200, meskio wrote: > Quoting Sven Joachim (2018-05-06 21:50:57) >> It seems to me this is a bug in acr 1.6.1-1. The configure script >> generated by it is clearly broken, and the same tudu version built >> successfull

Bug#804579: logol-bin: bogus hardcoded dependency on libncursesw5

On 2015-11-09 20:01 +0100, Sven Joachim wrote: > Package: logol-bin > Version: 1.7.2-2 > User: ncur...@packages.debian.org > Usertags: hardcoded-dependency > > The package logol-bin has, apparently since its first upload to Debian, > a hardcoded dependency on libncursesw5

Bug#898658: f-irc gets SEGV with TERM=xterm-256color

Control: tags -1 pending On 2018-05-16 04:34 -0400, Thomas Dickey wrote: > The problem is that f-irc asks for pair-content of pairs which it did not > initialize, and in doing this, found a case I'd overlooked in the logic > for dynamically allocating the color-pair table last year. > > Here's

Bug#898666: terminfo entries added to ncurses-base

Control: tags -1 pending I have added screen.xterm-256color and rxvt-unicode-256color to ncurses-base: https://salsa.debian.org/debian/ncurses/commit/cccb51b00ac612606d842b36de33b495478c233b Cheers, Sven

Bug#899112: mono-mcs: mcs terminates with an exception if TERM=xterm-256color

On 2018-05-19 12:02 +0200, Boris Jakubith wrote: > Package: mono-mcs > Version: 4.6.2.7+dfsg-1 > Severity: normal > > bj@rhiplox:~/src/Mono$ echo $TERM > xterm-256color > bj@rhiplox:~/src/Mono$ mcs > > Unhandled Exception: > System.TypeInitializationException: The type initializer for

Bug#899098: libclc-dev: libclc.pc is missing final newline

in subscribing to their mailing list. So please forward the patch. >From fbf6cafe778139f15e4752097b942e8428692234 Mon Sep 17 00:00:00 2001 From: Sven Joachim <svenj...@gmx.de> Date: Sat, 19 May 2018 08:51:45 +0200 Subject: [PATCH] configure.py: Add missing final newline to libclc.pc Signed-off

Bug#899064: nmu: smenu_0.9.12-1

Package: release.debian.org Severity: normal On amd64 only, the smenu package depends on libncurses5. Not the maintainer's fault, since the package is new and has been uploaded before the libncurses6 transition started. nmu smenu_0.9.12-1 . amd64 . unstable . -m "Rebuild against libncurses6."

Bug#898666: ncurses-base: include screen.xterm-256color terminfo entry

On 2018-05-14 23:03 +0200, Axel Beckert wrote: > Sven Joachim wrote: >> Many terminal emulators default to TERM=xterm-256color these days, for >> instance those based on libvte-2.91 as well as KDE's konsole. For >> better or worse, screen then by default sets TERM to >

Bug#898948: ncurses-base: include rxvt-unicode-256color terminfo entry

Package: ncurses-base Version: 6.1+20180210-3 Severity: wishlist The rxvt-unicode package in buster/sid defaults to TERM=rxvt-unicode-256color. This has annoyed some users (see #886465), as this terminfo entry is not in ncurses-base. Moreover, rxvt-unicode is the successor of some other once

Bug#898850: ui-utilcpp: FTBFS: syntax error in configure script

Source: ui-utilcpp Version: 1.8.5-2 Severity: serious Your package FTBFS everywhere[1], the reason being that the configure script has a syntax error after regeneration (but not before): , | $ bash -n ./configure | $ dh_autoreconf | libtoolize: putting auxiliary files in '.'. | libtoolize:

Bug#898832: ecere-sdk: FTBFS on i386: /usr/lib/gcc/i686-linux-gnu/7/include/stddef.h:435:78: error: syntax error

Thanks for the quick reply. On 2018-05-16 06:46 -0400, Jérôme St-Louis wrote: > Dear Sven, > > Thank you for the notice. > It would be extremely helpful in solving this rapidly to have a > quick-link to the exact version of that stddef.h (possibly the other > libc headers as well if that line

Bug#898832: ecere-sdk: FTBFS on i386: /usr/lib/gcc/i686-linux-gnu/7/include/stddef.h:435:78: error: syntax error

Source: ecere-sdk Version: 0.44.15-1 Severity: serious Tags: buster sid Your package fails to build on i386[1] with a rather bogus syntax error: , | Building 2nd stage ecere... | make[2]: Entering directory '/tmp/ecere-sdk-0.44.15/ecere' |

Bug#898658: f-irc gets SEGV with TERM=xterm-256color

On 2018-05-16 04:34 -0400, Thomas Dickey wrote: > On Tue, May 15, 2018 at 08:01:19PM -0400, Thomas Dickey wrote: >> On Tue, May 15, 2018 at 08:47:38PM +0200, Sven Joachim wrote: >> > CC'ing ncurses maintainer, it looks like the library might be at fault >> > he

Bug#898658: f-irc gets SEGV with TERM=xterm-256color

CC'ing ncurses maintainer, it looks like the library might be at fault here. On 2018-05-15 03:05 +0900, nozzy123no...@gmail.com wrote: > Package: f-irc > Version: 1.36-1+b3 > Severity: serious > > Dear Maintainer, > > This version of f-irc always gets SEGV when TERM environmental > variable set

Bug#898764: smuxi: FTBFS: dh_clideps: Error: Missing shlibs entry: libncursesw.so.5 or ncurses for: smuxi-frontend-stfl.exe!

Source: smuxi Version: 1.0.7-2 Severity: serious Your package FTBFS in unstable, here is the tail of my build log: , | DLL map: 'ncurses' target: 'libncursesw.so.5' | dh_clideps: Error: Missing shlibs entry: libncursesw.so.5 or ncurses for: smuxi-frontend-stfl.exe! | Use of

Bug#898666: ncurses-base: include screen.xterm-256color terminfo entry

Package: ncurses-base Version: 6.1+20180210-3 Severity: wishlist Many terminal emulators default to TERM=xterm-256color these days, for instance those based on libvte-2.91 as well as KDE's konsole. For better or worse, screen then by default sets TERM to screen.xterm-256color if the latter is

Bug#898555: override: libncurses5 oldlibs/optional, libncursesw5 oldlibs/optional, libtinfo5 oldlibs/optional

Package: ftp.debian.org Severity: normal Please change the section of libncurses5, libncursesw5 and libtinfo5 to oldlibs. These packages have been superseded by libncurses6, libncursesw6 and libtinfo6 (see #894049) but will be kept around since many third-party software uses them.

Bug#895754: ncurses-term: please add tmux-direct terminal type

Control: tags -1 upstream On 2018-04-15 16:45 +, brian m. carlson wrote: > Package: ncurses-term > Version: 6.1+20180210-1 > Severity: wishlist > > tmux has, since version 2.2, supported true color capabilities, but > there is no terminal definition (either tmux* or screen*) that handles >

Bug#898533: powertop: needlessly linked with ncurses

Control: tags -1 + patch On 2018-05-13 09:06 +0200, Sven Joachim wrote: > Package: powertop > Version: 2.8-1+b2 > Severity: minor > Tags: upstream > > The powertop binary is linked with both -lncursesw and -lncurses which > does not make sense, since the latter is redund

Bug#898533: powertop: needlessly linked with ncurses

Package: powertop Version: 2.8-1+b2 Severity: minor Tags: upstream The powertop binary is linked with both -lncursesw and -lncurses which does not make sense, since the latter is redundant. This is noticed by dpkg-shlibdeps: , | dpkg-shlibdeps: warning: package could avoid a useless

Bug#894049: transition: ncurses

On 2018-05-12 21:15 +0200, Emilio Pozuelo Monfort wrote: > On 12/05/18 21:07, Sven Joachim wrote: >> My goal with that "! .package" part was to prevent the ncurses source >> package from being listed as "partial" which would have happened >> otherwise,

Bug#898500: nmu: bash_4.4.18-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu The bash package is missing on the ncurses transition tracker[1] since it Pre-Depends rather than Depends on libtinfo5. Rather than fight with the ben syntax to add it there, I prefer to

Bug#894049: transition: ncurses

On 2018-05-12 20:29 +0200, Emilio Pozuelo Monfort wrote: > On 12/05/18 10:59, Sven Joachim wrote: >> On 2018-05-12 09:46 +0200, Emilio Pozuelo Monfort wrote: >> >>> On 10/05/18 15:56, Sven Joachim wrote: >>>> On 2018-03-25 21:51 +0200, Sven Joachim

Bug#897953: dvtm: Please stop shipping dvtm and dvtm-256color terminfo entries

On 2018-05-12 16:23 +0300, kact...@gnu.org wrote: > control: tags -1 +pending > > [2018-05-05 08:29] Sven Joachim <svenj...@gmx.de> >> In early 2017, the dvtm and dvtm-256color terminfo entries were added to >> ncurses upstream, and I would like to include them in

Bug#897040: fontconfig: .uuid files in font directories not removed during purge

On 2018-04-27 13:41 +0100, Simon McVittie wrote: > Package: fontconfig > Version: 2.13.0-4 > Severity: normal > > To reproduce: run piuparts on fontconfig or anything that it depends on. > I tested d-feet in a sid base tarball from earlier this week, in a > Debian 9 'stretch' virtual machine: > >

Bug#894049: transition: ncurses

On 2018-05-12 09:46 +0200, Emilio Pozuelo Monfort wrote: > On 10/05/18 15:56, Sven Joachim wrote: >> On 2018-03-25 21:51 +0200, Sven Joachim wrote: >> >> This has turned out to be rather suboptimal, because the regexes match >> on libncurses5-dev etc, and so some pac

Bug#898472: hunspell: needlessly linked with ncurses

Control: tags -1 + patch On 2018-05-12 09:44 +0200, Sven Joachim wrote: > The hunspell binary is linked with both ncursesw and ncurses, and the > latter is redundant as can be seen in the dpkg-shlibdeps warning: > > , > | dpkg-shlibdeps: warning: package could avoid a use

Bug#898472: hunspell: needlessly linked with ncurses

Package: hunspell Version: 1.6.2-1 Severity: minor Tags: upstream The hunspell binary is linked with both ncursesw and ncurses, and the latter is redundant as can be seen in the dpkg-shlibdeps warning: , | dpkg-shlibdeps: warning: package could avoid a useless dependency if

Bug#898131: fbb: xfbbC lost ncurses support after rebuild

Control: tags -1 + patch On 2018-05-10 15:04 +0200, Daniele Forsi wrote: > Package: fbb > Version: 7.07-3 > Followup-For: Bug #898131 > > That did not fix the problem because the macro doesn't search for > ncurses if it has found ncursesw before. Interesting that fbb is so far the only package

Bug#897423: ncurses normal and wide variants should not share the same -dev package

Control: retitle -1 ncurses: regressions from the -dev packages merge Control: severity -1 normal On 2018-05-02 19:13 +0200, Sven Joachim wrote: > On 2018-05-02 13:54 +0200, Matthias Klose wrote: > >> Package: src:ncurses >> Version: 6.1+20180210-2 >> Severity: impor

Bug#804579: Ping

Control: tags -1 - wontfix Control: severity -1 normal On 2017-09-27 11:41 +0200, Andreas Tille wrote: > control: tags -1 wontfix > control: severity -1 minor > > > > On Wed, Sep 27, 2017 at 09:59:25AM +0200, Olivier Sallou wrote: >> the executable is created with swi-prolog (build-depends), I

Bug#894049: transition: ncurses

On 2018-03-25 21:51 +0200, Sven Joachim wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > I would like to start a transition for ncurses, changing the soname of > the libraries from 5 to 6. The

Bug#898131: fbb: xfbbC lost ncurses support after rebuild

On 2018-05-07 20:27 +0200, Sven Joachim wrote: > Package: fbb > Version: 7.07-3+b1 > Severity: important > > In ncurses 6.1+20180210-1, the libncurses5-dev and libncursesw5-dev > packages had been merged into a single libncurses-dev package. In fbb, > this has the rather st

Bug#898131: fbb: xfbbC lost ncurses support after rebuild

Package: fbb Version: 7.07-3+b1 Severity: important In ncurses 6.1+20180210-1, the libncurses5-dev and libncursesw5-dev packages had been merged into a single libncurses-dev package. In fbb, this has the rather strange and undesirable effect that the configure script fails to properly detect

Bug#897537: tudu: FTBFS: ./configure: 394: ./configure: rmtest.c: not found

On 2018-05-02 22:54 +0200, Lucas Nussbaum wrote: > Source: tudu > Version: 0.10.2-1 > Severity: serious > Tags: buster sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20180502 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package

Bug#898045: nvidia-cuda-gdb: depends on libncurses5

Package: nvidia-cuda-gdb Version: 9.1.85-4+b1 Severity: normal Even after being rebuilt for the libncurses6 transition[1], nvidia-cuda-gdb depends on libncurses5. Clearly there's not much you can do about that, other than prodding Nvidia to release a version of it linked against libncurses.so.6,

Bug#898039: ruby-ncurses: should link with -lmenuw, not -lmenu

Control: tags -1 + patch On 2018-05-06 09:44 +0200, Sven Joachim wrote: > Source: ruby-ncurses > Version: 1.4.9-1 > Tags: upstream > > The configure script for ruby-ncurses apparently does not check for the > menuw library shipped in libncursesw6, but only for the menu librar

Bug#898039: ruby-ncurses: should link with -lmenuw, not -lmenu

Source: ruby-ncurses Version: 1.4.9-1 Tags: upstream The configure script for ruby-ncurses apparently does not check for the menuw library shipped in libncursesw6, but only for the menu library in libncurses6. This is the relevant excerpt from the build log[1}: , | checking for the menu

Bug#894049: transition: ncurses

On 2018-05-06 08:32 +0200, Emilio Pozuelo Monfort wrote: > On 06/05/18 02:05, peter green wrote: >> I suspect fpc will also need a sourceful upload for the new ncurses. I would >> recommend not binnmuing it until the maintainers have had chance to take a >> look. > > It's not on

Bug#897983: mdp-src: hardcoded depends on libncursesw5

Source: mdp-src Version: 1.0.12-1 User: ncur...@packages.debian.org Usertags: hardcoded-dependency The mdp package has a hardcoded dependency on libncursesw5 (>= 6) in debian/control which is Wrong™, that's what ${shlibs:Depends} is for. Rebuilding mdp in unstable causes it to depend on both

Bug#897959: fbterm: Please stop shipping /usr/share/terminfo/f/fbterm

Package: fbterm Version: 1.7-4 Severity: wishlist Last year the fbterm terminal description was added to ncurses upstream, and I would like to add it to the ncurses-term package, replacing the one shipped currently in the fbterm package. This requires coordinated uploads of ncurses and fbterm,

Bug#897953: dvtm: Please stop shipping dvtm and dvtm-256color terminfo entries

Package: dvtm Version: 0.15-2 Severity: wishlist In early 2017, the dvtm and dvtm-256color terminfo entries were added to ncurses upstream, and I would like to include them in the ncurses-term package, replacing the ones shipped currently in the dvtm package. This requires coordinated uploads of

Bug#897910: pamix: hardcoded dependency on libncursesw5

Source: pamix Version: 1.6~git20180112.ea4ab3b-2 User: ncur...@packages.debian.org Usertags: hardcoded-dependency Your package has a hardcoded dependency on libncursesw5 in debian/control which is Wrong™, that's what ${shlibs:Depends} is for. Rebuilding pamix in unstable causes it to depend on

Bug#897423: ncurses normal and wide variants should not share the same -dev package

On 2018-05-02 13:54 +0200, Matthias Klose wrote: > Package: src:ncurses > Version: 6.1+20180210-2 > Severity: important > Tags: sid buster > > ncurses normal and wide variants should not share the same -dev package. Up to > now, packages had to be explicit about the ncurses variant. There are

Bug#894049: transition: ncurses

On 2018-04-30 19:00 +0200, Emilio Pozuelo Monfort wrote: > On 25/03/18 21:51, Sven Joachim wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags: transition >> >> I would like to start a tran

Bug#897035: Should Suggest: ncurses-doc

Control: tags -1 + pending On 2018-04-27 13:06 +0200, Yuri D'Elia wrote: > Package: libncurses-dev > Version: 6.1+20180210-2 > Severity: minor > > The old libncurses5-dev packages suggested the development documentation in > ncurses-doc. > It would be nice do the same in the new package.

Bug#896979: xserver-xorg-video-nouveau: Crash when undocking Lenovo P50

On 2018-04-26 14:13 +, Sam Morris wrote: > Followup-For: Bug #896979 > Control: tag -1 + patch > > This patch (taken from > ) fixes > the problem for me. > > (Note, I modified the patch to end the log message with a newline >

Bug#896983: cwidget: Enable mouse wheel as button 5 with new ncurses ABI

On 2018-04-26 16:23 +0200, Manuel A. Fernandez Montecelo wrote: > Source: cwidget > Version: 0.5.17-7 > Severity: normal > Tags: upstream patch > > Hi, > > This is a follow-up of https://bugs.debian.org/891161 , I submit this new one > rather than cloning to not have to go through many messages

Bug#891161: cwidget: FTBFS with libncursesw6

On 2018-04-20 16:46 +0200, Manuel A. Fernandez Montecelo wrote: > 2018-03-31 21:13 GMT+02:00 Manuel A. Fernandez Montecelo > <manuel.montez...@gmail.com>: >> 2018-03-31 20:20 GMT+02:00 Sven Joachim <svenj...@gmx.de>: >>>> So I have to wait to uploa

Bug#895662: libfontconfig1: does not distinguish between bold and non-bold

Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=105415 Control: tags -1 + fixed-upstream patch On 2018-04-14 10:25 +0200, Sven Joachim wrote: > Package: libfontconfig1 > Version: 2.13.0-4 > Severity: normal > > After upgrading the fontconfig packages from 2.12.6

Bug#895662: libfontconfig1: does not distinguish between bold and non-bold

Package: libfontconfig1 Version: 2.13.0-4 Severity: normal After upgrading the fontconfig packages from 2.12.6-0.1, my window manager (icewm) does no longer show window titles and menus in bold, despite being configured to do so. This is the font which I have specified for window titles: ,

<    3   4   5   6   7   8   9   10   11   12   >