Bug#898426: partx exit status 0 on some errors
Package: util-linux Version: 2.32-0.1 partx has a exit status of 0 when it fails to read the partition table: root@loopy:~# partx -s - /dev/sda1 partx: /dev/sda1: failed to read partition table root@loopy:~# echo $? 0 It behaves properly, however, when the disk cannot be read: root@loopy:~# partx -s - /dev/none partx: cannot open /dev/none: No such file or directory root@loopy:~# echo $? 1 Thanks, -- Juan Cespedes
Bug#854792: fails when there are two users with the same UID
On Thu, Feb 16, 2017 at 12:16 AM, Emilio Pozuelo Monfortwrote: > On 10/02/17 13:38, Juan Cespedes wrote: > > Summary: accounts-daemon.service fails to work properly when there are > > two users in the system with the same UID. > > I'm not sure that's a system configuration that is supported. If you shoot > yourself in the foot, you should expect some problems... > Neither the Debian Policy nor any other document I am aware of states that it shouldn't be done. I do it fairly often for several reasons, and I know of some other people who do it too. Furthermore, it has always worked, and suddenly, after upgrading to stretch, it fails to work *silently*... -- Juan Cespedes
Bug#730933: ltrace: diff for NMU version 0.5.3-2.2
On Dec 22, 2013 12:33 AM, David Prévot taf...@debian.org wrote: I've prepared an NMU for ltrace (versioned as 0.5.3-2.2) and uploaded it to DELAYED/5. Thank you very much for your work. I expect to have some more time these days, and I will try fix many pending issues in ltrace. Please feel free to tell me if I should delay it longer. No, it's ok for me. Thank you again, Juan
Bug#295567: iptables: order in which raw, filter, nat, mangle tables are examined
From: Jan Engelhardt jeng...@medozas.de Date: Sun, 3 Aug 2008 13:43:37 -0400 (EDT) That's because it is not iptables's job or decision as to what table gets executed in which order. IMHO that's not a good reason for not having it specified in the man page. And AFAIK that order has never changed. I wanted to make sure in which order the tables are examined, didn't find it in the man page, and searched in Google, which gave me this bug report (!). I think it would be a good thing to make it clear in the man page. As a user, it suffices to know that the order is manglenatfilter for purposes of routing and filtering control. Right. But how can a user know it if it isn't specified in the man page? (and, btw, I would add rawmangle). Regards, -- Juan Cespedes http://www.cespedes.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537781: ltrace: ltrace should support dlopen()'d libraries
On Mon, Jul 20, 2009 at 11:11 PM, Samuel Bronsonnaes...@gmail.com wrote: It would be really nice if ltrace supported not only library-to-library calls as requested in #135985, but even calls to libraries that were loaded dynamically by dlopen(). I don't see how this can be all that hard; if GDB can hook dlopen, why can't ltrace? Well, it's not so easy, but I will have a look at it. The problem is that, as far as I know, there is no PLT section in the executable corresponding to the symbols loaded by dlopen()... Yes, I know -- you're going to ask me to do it, since I think it's so easy. Maybe I will ;-). Thanks for your offer :) -- Juan Cespedes http://www.cespedes.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532195: ltrace_0.5.2-2(sparc/unstable): FTBFS on sparc
tag 532195 help thanks On Sun, Jun 7, 2009 at 1:58 PM, Martin Zobel-Helaszo...@ftbfs.de wrote: There was an error while trying to autobuild your package: [...] In file included from trace.c:8: /build/buildd/ltrace-0.5.2/sysdeps/linux-gnu/sparc/ptrace.h:14:21: error: asm/reg.h: No such file or directory Include file asm/reg.h for sparc is present in linux-libc-dev_2.6.26-15 but not in 2.6.30-1; there used to be a struct regs defined there with the layouts of the registers in Sparc. ltrace needs it in order to get/set the instruction pointer and the return addr. Does any Linux kernel or Sparc guru know how to address this nowadays? -- Juan Cespedes http://www.cespedes.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#503367: Again: Bug#503367: plink: file conflict with putty-tools
On Thu, Apr 2, 2009 at 10:23 AM, Daniel Leidert daniel.leidert.s...@gmx.net wrote: What about using /usr/bin/PLINK? Please don't. I have already had enough problems with MacOS, Windows, and some other operating systems and filesystems which are not case sensitive. -- Juan Cespedes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#463023: Log for failed build of ltrace_0.5.1-1 (dist=unstable)
On Thu, Dec 11, 2008 at 12:06 AM, Riku Voipio [EMAIL PROTECTED] wrote: Atleast the debian/control changes (adding armel, armeb archs) i added in the NMU are still missing. Oops, you are right will fix it today. -- Juan Cespedes http://www.cespedes.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500236: wrong display of UTF-8 characters
On Sat, Sep 27, 2008 at 1:32 PM, Thomas Dickey [EMAIL PROTECTED] wrote: #include locale.h setlocale(LC_ALL, ); Without initializing the locale, ncurses doesn't know about UTF-8. It's an encoding that can use multiple bytes per character. OK, I understand it now; but I still think there is a bug, at least a documentation one: it would be *very* useful to have a README.Debian in libncursesw5-dev telling this. Without those 2 lines, any program linked with libncursesw5 works exactly the same as it does with libncurses5, without any wide-char support at all. -- Juan Cespedes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500236: wrong display of UTF-8 characters
On Sat, Sep 27, 2008 at 1:21 AM, Thomas Dickey [EMAIL PROTECTED] wrote: Two observations: It does not initialize locale. #include locale.h setlocale(LC_ALL, ); Nice. Including these lines it does work. Why is it necessary to initialize locale? I am tempted to rename the bug :) mvaddstr(1, 1, Juan Cespedes); mvaddstr(2, 1, Juan Céspedes); The string is encoded for ISO-8859-1 (not UTF-8). Oops, it must have been due to some copy paste; the file I tried was UTF-8 encoded. Thanks, Juan Céspedes
Bug#484204: ITP: rdup -- utility to create a file list suitable for making backups
On Tue, Jun 3, 2008 at 12:27 AM, Jose Carlos Garcia Sogo [EMAIL PROTECTED] wrote: rdup is a utility inspired by rsync and the plan9 way of doing backups. I'm afraid I don't see why rdup ins inspired in the plan9 way of doing backups. In fact, the way Plan9 uses to make back-ups (sort of) is venti, which is way different from rdup. Perhaps you meant the plan9 way of doing things, given rdup's simplicity and modularity... -- Juan Cespedes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#450931: arm/armel support for ltrace
On Jan 28, 2008 2:31 PM, Riku Voipio [EMAIL PROTECTED] wrote: Since neither of you maintainers have responded anything in ages to ltrace bugreports, I will take that both you are inactive and will not mind if NMU ltrace. I will proceed to NMU it tonight, if testing shows that Anderson Lizardo's patches work fine. Fine, no problem for me. I was waiting for the end of january to come, since I will be very busy until then, but if you can NMU, I will greatly appreciate that and ack your upload as soon as possible. Thank you, Juan Cespedes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428561: [EMAIL PROTECTED]
severity 428561 grave thanks Given that link_in_boot now defaults to YESB, the link is created in /boot, which makes that image unbootable unless someone changes the boot loader configuration. Moreover, someone could think he is using this new kernel after installing the package and booting the system, and after checking that everything is ok, if he removes the previous kernel, it could make the system unbootable. Thanks, Juan Cespedes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439701: marked as done (linux86: FTBFS: elks.c:18:22: error: sys/vm86.h: No such file or directory)
On 8/26/07, Debian Bug Tracking System [EMAIL PROTECTED] wrote: Your package is failing to build on amd64 with the following error: cc -O -c -o elks.o elks.c elks.c:18:22: error: sys/vm86.h: No such file or directory I know, I know. Sorry for that. Version 0.16.17-2 was uploaded shortly after that, when I realized it, and this issue has already been fixed. Thanks for your support, Juan Cespedes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]