Bug#933016: [Pkg-rust-maintainers] Bug#933016: rustc: status of nightly toolchains

I think you are trying to compile a project that requires in-development features of the Rust compiler. I think you also want to do that without getting involved in the Rust upstream development process and tools (like rustup). I don't think there is a way to resolve those two conflicting goals

Bug#915675: libasound2-data: Kernel 4.18 change breaks WD15 dock usb audio

) - Gus On Thu, 6 Dec 2018 at 18:36, Elimar Riesebieter wrote: > * Angus Lees [2018-12-06 09:29 +1100]: > > [...] > > > > After *much* debugging, I stumbled across > > > https://github.com/edrose/dell-dock-audio-fix/issues/2#issuecomment-440420105 > > &

Bug#915675: libasound2-data: Kernel 4.18 change breaks WD15 dock usb audio

Package: libasound2-data Version: 1.1.7-1 Severity: normal Dear Maintainer, The usb-audio interface on my Dell USB-C WD15 dock stopped working recently. The immediate symptom is the device gone from pulseaudio, with: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. E:

Bug#913572: [Pkg-rust-maintainers] Bug#913572: Shouldn't shipping broken symlinks be against policy?

I think I am responsible for this dangling symlink :) The issue is that the symlink target is _not_ in the 'rust-doc' package, but in the 'gdb-doc' package which has nothing to do with the rust src package, nor the rust maintainers. Moving the rust-gdb symlink into gdb-doc is not appropriate.

Bug#906585: [Pkg-rust-maintainers] Bug#906585: rustc: Backport the fix for Rust#44800 to stretch

On Sun, 19 Aug 2018 at 20:39 Moritz Mühlenhoff wrote: > On Sat, Aug 18, 2018 at 03:19:46PM +0200, Nicolas Braud-Santoni wrote: > > Would it be possible to turn it into a security upload, along with a > binNMU of > > all packages that were built with rustc (<< 1.24.1) ? > > 1.24 will reach

Bug#903110: [Pkg-rust-maintainers] Bug#903110: rustc: wasm32 target is enabled, but doesn't work

Fwiw: Unless there is something that acts on `rustc --print target-list` without applying some human judgement first, I would rather we just reassigned this bug to LLVM and enabled wasm. "Fixing" this in rustc, and then unfixing it again once we add support to LLVM seems a little bit like chasing

Bug#898792: [Pkg-rust-maintainers] Bug#898792: rust-src: [RC] embedded copy of normalize.css

severity 898792 normal thanks Downgrading severity, since I think we'd all agree that using a single CSS file from one source rather than another does not render the entire Rust toolchain as unusable or not suitable for release ;) (and the Debian policy section cited is a "should" not "must"

Bug#884775: [Pkg-rust-maintainers] Bug#884775: /usr/bin/rustc: Error Compiling Code: "attempt to use impure library"

tags 884775 + unreproducible notabug close 884775 thanks I suspect the original issue was caused by having a non-standard "ld" in your $PATH - specifically, I suspect it was the guix ld-wrapper[1]. (Or perhaps a non-standard "cc" that in turn uses this guix ld) The reply to your stack overflow

Bug#890213: squid-deb-proxy-client should try all browse domains

Package: squid-deb-proxy-client Version: 0.8.14 Severity: normal Dear Maintainer, I'm trying to setup static dns-sd entries for my apt cache (I don't want to run avahi/mDNS on my proxy server). This involves creating _apt_proxy._tcp entries on a domain other than .local[1]. For reasons that

Bug#846177: [Pkg-rust-maintainers] Bug#846177: A rustc-src package would be useful for racer completion

On Tue, 29 Nov 2016, 10:51 Dato Simó wrote: > It would be nice to have a rustc-src package containing the source for > Rust itself. > > The (widely-used) racer completion engine needs access to the source in > order to work. > I'm becoming a big fan of racer, so I'm all for

Bug#834003: rustc: armhf FTBFS because upstream assumes armhf has neon but debian does not

A relevant upstream discussion[*] seems to suggest that we should be using arm-unknown-linux-gnueabihf and not armv7-* I think this results in armv6, which sounds preferable to armv7+neon, and I don't think will cause any other issues (Steve?). Other options include creating a new combination of

Bug#832565: [Pkg-rust-maintainers] Bug#832565: rustc: don't embed llvm in librustc_llvm

(Capturing some investigation I dumped into IRC) On Wed, 27 Jul 2016 at 09:54 Ximin Luo wrote: > librustc_llvm-xx.so is approx 30MB, taking about half the space of > libstd-rust-xx. > Upstream tells me that this is due to embedding pretty much all of LLVM. > > We should

Bug#819475: [Pkg-rust-maintainers] Bug#819475: Bug#819475: rustc not run depend on gcc 4.9.2

On Wed, 30 Mar 2016 at 13:27 Lihe Wang wrote: > #~ rustc hello.rs > error: linking with `cc` failed: exit code: 1 > note: "cc" "-Wl,--as-needed" "-m64" "-L" > "/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib" "hello.0.o" "-o" "hello" > "-Wl,--gc-sections" "-pie"

Bug#811573: FTBFS with GCC 6: statement indented as if it were guarded by

Urgh. These aren't bugs, and it looks like we're going to have to add "-Wno-error=misleading-indentation" (or disable the misleading-indentation warning entirely). - Gus

Bug#791961: saned won't run from systemd (bad status=22 or procnum=1)

Interesting. Yes, setting Standard Input=null/Output=syslog/Error=syslog works for me with sane-utils 1.0.24-13 and systemd 224-1. I think part of my earlier confusion was because I hadn't realised saned (now) has native systemd socket-activation support, and didn't need to be run in

Bug#796256: [Pkg-rust-maintainers] Bug#796256: Bug#796256: Bug#796256: Bug#796256: Bug#796256: Bug#796256: Bug#796256: Please consider packaging a Rust version that allows #![feature(...)]

On Mon, 31 Aug 2015 at 19:26 Ximin Luo wrote: > On 31/08/15 10:58, Sylvestre Ledru wrote: > > Le 31/08/2015 10:37, Ximin Luo a écrit : > >> On 31/08/15 08:59, Sylvestre Ledru wrote: > >>> We are aware of this and we decided to take this approach on purpose > for > >>> now.

Bug#791961: saned@.service systemd file is wrong (afaics)

Indeed, I'm thoroughly confused by the conclusion in #782971 - it seems the exact opposite of my experience just now with sane-utils 1.0.24-13 and systemd 224-1. For me, I needed to modify /lib/systemd/system/saned@.service and set both Standard{Input,Output} to 'socket' to get saned working

Bug#796256: [Pkg-rust-maintainers] Bug#796256: Please consider packaging a Rust version that allows #![feature(...)]

tags 796256 upstream wontfix close 796256 thanks On Fri, 21 Aug 2015 at 06:03 Josh Triplett j...@joshtriplett.org wrote: Quite a bit of the Cargo ecosystem makes use of #![feature(...)] to enable unstable features. Rust release builds prohibit this by default:

Bug#793147: [Pkg-rust-maintainers] Bug#793147: rustc FTBFS on mipsel: configure: error: unknown CPU type: mips

On Wed, 22 Jul 2015 at 04:48 Gustavo Prado Alkmim alk...@ic.unicamp.br wrote: Package: rustc Version: 1.1.0+dfsg1-1 Package is failing to build on buildd. I'm working on a fix and I will attach it as soon as possible. Oops. This is a known issue (the toolchain bootstrapping currently only

Bug#792908: lldb: Please provide a lldb.1 manpage symlink to lldb-$version.1

Package: lldb Version: 1:3.5-25 Severity: wishlist This package provides an unversioned lldb executable. For all the same reasons, it would be nice to have an unversioned lldb manpage. (I would like to take advantage of this to provide the manpage in the rust-lldb package without adding a

Bug#760530: aspell-en: en_GB missing gaol

Package: aspell-en Version: 7.1-0-1 Severity: minor Gaol is a decreasingly popular, but still quite valid(*), alternative spelling of jail in UK, Ireland and Australia. See for example the brief discussion on http://en.wiktionary.org/wiki/gaol (*) Indeed, some view gaol as the more correct

Bug#624965: gcc 4.6 bullet build failure (patch)

fyi: Upstream bug and trivial patch is here: http://code.google.com/p/bullet/issues/detail?id=481 - Gus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#475228: defoma: defoma-font tries to update cache in my homedir

On Wed, Apr 9, 2008 at 6:41 PM, Paul Slootman [EMAIL PROTECTED] wrote: Package: defoma Version: 0.11.10-0.2 Severity: normal I have my homedir on an NFS mounted filesystem. Hence root has no rights on my files. When installing latex-xft-fonts, I got the following output: Setting up

Bug#460313: RM: libhtml-embperl-perl -- RoM; apache1 specific; obsolete

Package: ftp.debian.org Severity: normal Superseded upstream by libembperl-perl (although not completely compatible). No support for apache2 so its time for this package to die. Already removed from testing, please remove from unstable. -- - Gus pgpP0sHrmv34v.pgp Description: PGP signature

Bug#460036: RFA: defoma -- Debian Font Manager -- automatic font configuration framework

Package: wnpp Severity: normal I request an adopter for the defoma package. I still think defoma fills a need and we should keep it. It needs a rewrite into something more resembling maintainable/modern perl, the gtk1 gui updated/removed and the font hints to be better specified (look to

Bug#412521: How does Embperl work with different Apache2 MPM models?

On 5/1/07, Gunnar Wolf [EMAIL PROTECTED] wrote: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412521 In short, the user states embperl only works with the Prefork Apache MPM. I have only used this MPM (and not the other ones, particularly the ones based on threading) - and this is because

Bug#418067: apache2-mpm-prefork: apache2 -X kills wrong process group on exit

Package: apache2-mpm-prefork Version: 2.2.3-4 Severity: normal In apache2.2 (at least prefork mpm), 'apache2 -X' doesn't create a new process group. Despite that, on exit it sends a SIGTERM to whatever the process group is, causing all sorts of damage. Amongst them a FTBFS on libembperl-perl

Bug#411253: ipvsadm: bashism in ipvsadm.postinst

Package: ipvsadm Version: 1.24+1.21-1.4 Severity: important This line in ipvsadm.postinst: ipvsadm -L -n /dev/null || true should be changed to: ipvsadm -L -n /dev/null 21 || true in order to be more portable amongst bourne shells. In particular, this made ipvsadm uninstallable for me using

Bug#402014: fontconfig.defoma patch

On 1/22/07, Keith Packard [EMAIL PROTECTED] wrote: On Sun, 2007-01-21 at 23:08 +1100, Angus Lees wrote: hrm. you're right - we need to run fc-cache on the directories we didn't need to symlink to .. Would it be better to add the new font directories to the fontconfig configuration instead

Bug#402014: fontconfig.defoma patch

At Sun, 21 Jan 2007 07:19:01 +1100, Keith Packard wrote: On Tue, 2007-01-16 at 17:39 +1100, Angus Lees wrote: Keith, here's the patch written during your talk at LCA ;) It fixes bug 402014, by simply adding '-f' to the fc-cache run, hence me filing it under this bug number. Really though

Bug#402014: fontconfig.defoma patch

Keith, here's the patch written during your talk at LCA ;) It fixes bug 402014, by simply adding '-f' to the fc-cache run, hence me filing it under this bug number. Really though, this patch avoids creating symlinks for fonts that are already in a directory covered by fontconfig - but I couldn't

Bug#333724: Announce of the upcoming NMU for the libapache-sessionx-perl package

On 11/20/06, Christian Perrier [EMAIL PROTECTED] wrote: Dear maintainer of libapache-sessionx-perl and Debian translators, On 13 nov 2006 I sent a notice to the maintainer of the libapache-sessionx-perl Debian package, mentioning the status of at least one old po-debconf translation update in

Bug#393746: defoma: The wrong fonts are chosen for 'courier'

reassign 393746 msttcorefontsthanksOn 10/17/06, Sam Morris [EMAIL PROTECTED] wrote: I'm not sure exactly which package I should be reporting this bugagainst, so please bear with me. :)My problem: web pages that ask for the 'courier' font look ugly. Thefont is very blurry, and lines that should be

Bug#388416: Problems with fontconfig's defoma script

On 10/2/06, Josselin Mouette [EMAIL PROTECTED] wrote: Hi Angus,we're currently facing some issues with the fontconfig defoma script,which is displaying error scanning messages. As neither Keith nor I doreally understand how defoma is working, I was wondering whether you could have a look at what's

Bug#365315: xterm and charcell fonts

reassign 365315 xserver-xorg retitle xserver-xorg whitespace in charcell fonts rendered as squares thanks With the new version of today, the opendir issue has gone, but I found some kind of wrong encodings (with the space char) in a font previously perfectly working. See the xterm screenshot

Bug#325935: warzone2100: Is this ITP still valid?

On 7/29/06, Linas Žvirblis [EMAIL PROTECTED] wrote: The latest packages, by the bug owner, I could find date back to year2005. Although upstream currently ships with Debian packaging filescreated by Angus Lees in March 2006.Is anyone still working on packaging Warzone 2100 for inclusion in Debian

Bug#319951: [Pkg-fonts-devel] Not sure that #319951 is still here

[uninitialised variable at gs.defoma line 108] That is/was a bug with gs.defoma; I've merged many bug reports for it. As far as I know without having fixed the bug, it is not an issue with ttf-farsiweb.-- - Gus

Bug#373659: acpi-support: shutsdown/brings up interfaces that were already down

On 6/16/06, Raphael Hertzog [EMAIL PROTECTED] wrote: [ please keep me in CC since the BTS hasn't affected a maintainer toacpi-support yet ]thanks for your bug reports. You appear to have some knowledge on thetopic and evidently some interest, would you be interested to co-maintain the

Bug#373660: acpi-support: acpi_fakekey doesn't work

Package: acpi-support Version: 0.80-1 Severity: serious acpi_fakekey doesn't seem to do anything on my Thinkpad T43p laptop. This means suspend and hibernate doesn't actually trigger at all for me. I'm not sure what acpi_fakekey is supposed to do (strace shows it writing to my keyboard

Bug#373659: acpi-support: shutsdown/brings up interfaces that were already down

Package: acpi-support Version: 0.80-1 Severity: normal suspend.d/55-down-interfaces.sh takes down all interfaces that exist, even those that are already down and resume.d/62-ifup.sh diligently brings up all the interfaces that were taken down. This means that my ethernet interface (which is

Bug#360456: libembperl-perl: FTBFS: match/div.asc failure.

On 4/2/06, Kurt Roeckx [EMAIL PROTECTED] wrote: Package: libembperl-perlVersion: 2.0.1-1Severity: seriousHi,Your package is failing to build with the following error:#147 match/div.htm... ok#148 match/div.asc...Error in Line 1 Is:Should: htmlInput:test/html/match/div.ascOutput:

Bug#347268: another ttf-dejavu defoma hints change

It seems you'll also want to replace /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Roman.ttf with /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf in ttf-dejavu.defoma-hints, since that file has also been renamed. -- - Gus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a

Bug#337351: libembperl-perl: FTBFS on arm - fails httpd syntax check 1

At Fri, 4 Nov 2005 02:03:31 - (GMT), Wookey wrote: http://buildd.debian.org/fetch.php?pkg=libembperl-perlver=2.0.1-1arch=armst$ fails during output caching tests: sub EXPIRES in source... ok sub EXPIRES in source (cached)...ok Performing httpd syntax check 1 ... ERROR: Syntax OK

Bug#333154: pwc-source: kernel/linux name detection broken

Package: pwc-source Version: 10.0.7a-5 Severity: normal The KLINUX code in debian/rules doesn't work (always ends up with KLINUX=linux). Adding echo yes to the ifeq conditions fixes it: ifeq ($(shell test $(strip $(ksublevel)) -le 11 echo yes), yes) KLINUX=kernel else ifeq

Bug#326596: Warnings from gs.defoma script when upgrading fonts

At Sun, 04 Sep 2005 11:49:58 +0200, Vincent Lönngren wrote: Use of uninitialized value in print at /var/lib/defoma/scripts/gs.defoma line 108. For the record, what version of gs-common do you have installed? -- - Gus pgpJEAC9vebnY.pgp Description: PGP signature

Bug#313067: defoma: Defoma prevents ghostscript from rendering fonts properly

At Sat, 11 Jun 2005 12:14:17 -0400, Kirill wrote: I am trying to set up an HPLJ 1012 to print from KDE apps (KWord, Konqueror) using CUPS. I am getting most fonts messed up by ghostscript (gs-esp). I've been struggling with it for a whole week now with very little progress so far. When I

Bug#313067: defoma: Defoma prevents ghostscript from rendering fonts properly

At Sun, 28 Aug 2005 08:42:30 -0400, Kirill wrote: Having the letter spacing wrong probably means the original kword app somehow didn't get the font metric information correct, however. Has this ever worked for you in the past? Not with Times New Roman. But if after editing gsfonts.hints

Bug#322859: FTBFS: Cannot find apr.h

At Sat, 13 Aug 2005 11:18:11 +0200, Marc 'HE' Brockschmidt wrote: This problem is caused by a radical API change in libapach2-mod-perl2 1.999_22. Upstream has already reacted, so packaging the new 2.0rc5 version should fix this FTBFS. Yep, the 2.0rc5 build breaks somehow (doesn't find apache

Bug#315682: marked as done (defoma: many hintfiles lack Location and even FontName)

reopen 315682 retitle 315682 defoma-ps should generate Location and FontName hints reassign 315682 psfontmgr severity 315862 normal thanks At Sun, 26 Jun 2005 18:18:06 -0700, Debian Bug Tracking System wrote: However, many of the hintfiles installed automatically have no Location entries, and

Bug#313067: looks like the same bug as 251067

At Wed, 22 Jun 2005 20:04:10 -0700 (PDT), Andrew Young wrote: The behavior reported here seems very similar to the problems with printing from mozilla, filed under 251067. Take a look and see if these can be combined -- and see if it's possible to decide just *where* in the font-handling

Bug#314549: zaptel: should build-dep on dpatch = 2.0.9

Package: zaptel Version: 1:1.0.7-4.1 Severity: normal dpatch-run (used in the zaptel .dpatch scripts) was only introduced in dpatch 2.0.9 - Gus -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (890, 'testing'), (89, 'unstable'), (1, 'experimental') Architecture:

Bug#314552: zaptel: bashism in postinst

Package: zaptel Version: 1:1.0.7-4.1 Severity: important zaptel.postinst contains this piece of code: N=1; while (( $N 250 )) ; do rm -f /dev/zap/$N; mknod /dev/zap/$N c 196 $N; N=`expr

Bug#310154: 855resolution: should be run from rcS.d

Package: 855resolution Version: 0.3-4 Severity: normal 855resolution only needs to be run once during bootup (it has no stop equivalent) and has essentially no boot-time dependencies. IMO the init script should be run from runlevel S, not the usual [2345] priority 20. - Gus -- System

Bug#308902: units: doesn't know about RU (rack units)

Package: units Version: 1.81-4 Severity: wishlist Would be nice if units knew about rack units (RU) - Gus -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (890, 'testing'), (89, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-686

Bug#308604: libapache2-mod-perl2: Apparently requires CGI.pm = 3.08 which is unavailable

Package: libapache2-mod-perl2 Severity: important Version: 1.999.23-1 The upstream changes document mentions that CGI.pm = 3.08 is required to understand the Great Apache2 Renaming. This version is unavailable in Debian, since libcgi-perl is ancient, libcgi-pm-perl no longer exists and

Bug#300278: defoma: debhelper files fail if defoma is removed before package

At Sat, 26 Mar 2005 15:28:35 -0800, Steve Langasek wrote: Ok, downgrading; I'll leave it to the maintainer to evaluate whether this is something that needs changing. Thanks for your debugging efforts. It can't hurt to add the -x check, so I'll do that in the next upload - good to know it isn't

Bug#295165: lilo-installer: postinst fails at debconf priority=critical

Package: lilo-installer Severity: important Version: 1.05 Tags: patch lilo-installer.postinst dies before doing anything if debconf priority=critical, due to an unchecked debconf return code: - db_input high lilo-installer/bootdev + db_input high lilo-installer/bootdev || [ $? -eq 30 ] - Gus

Bug#292446: modutils: udebs missing Section and Priority

Package: modutils Version: 2.4.26-1.1 Severity: normal % dpkg --info modutils-basic_2.4.26-1.1_i386.udeb new debian package, version 2.0. size 52600 bytes: control archive= 395 bytes. 374 bytes,11 lines control Package: modutils-basic Version: 2.4.26-1.1