Re: Please respect Freeze Policy
Hi Sam, On Wed, Dec 03, 2014 at 03:36:37PM +, Sam Hartman wrote: > > Hi. You assert that even for leaf packages we should not make changes > in unstable targeted beyond jessie. I can see an argument for that > prior to the important bug deadline. However, past that point, I don't > see value in avoiding changes to leaf packages in unstable, and I'd like > to understand why you'd encourage folks to do so. I have not browsed the full list of packages given by the OP but r-base-core[1] is no leaf package and creates burden[2] for fellow maintainers who might not realise the pitfall that they are forced to t-p-u and need to use a testing chroot to build their packages. This kind of nuisance without warning should be avoided and release policy was issued to ensure this. Kind regards Andreas. [1] https://lists.debian.org/debian-devel/2014/11/msg00413.html [2] https://lists.debian.org/debian-devel/2014/11/msg00992.html -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141207083144.gi22...@an3as.eu
Re: multiarch coinstallability of libc6 / conflicting loader paths
On Sun, Dec 07, 2014 at 01:08:24AM +0100, Timo Weingärtner wrote: > A short-term fix for the dpkg errors could be to express the conflicting > loader paths with Conflicts: between the relevant libc6 packages. Have multiarch conflicts/breaks been specified already? Sure, this would not be the special case outlined in [1], but I don't see any in the archive yet... Note that /lib64/ld-linux.so.2 on sparc64 is also a conflict because we symlink /lib64 to /lib (which could not be easily avoided when building the port). Same for s390x vs. ppc64. Kind regards Philipp Kern [1] https://wiki.ubuntu.com/MultiarchSpec#Architecture-specific_Conflicts.2BAC8-Replaces signature.asc Description: Digital signature
Bug#771718: marked as done (general: Screen blanks and does not come back up unless system is suspended)
Your message dated Sun, 7 Dec 2014 13:44:28 +0100 with message-id <201412071344.30567.hol...@layer-acht.org> and subject line closing has caused the Debian Bug report #771718, regarding general: Screen blanks and does not come back up unless system is suspended to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 771718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: normal Hi, I was thus far unable to pinpoint which component causes this behaviour as I can not find anything in my logs (and/or journal). I have therefore assigned it to general. Feel free to change to a more appropriate package. I'm using KDE on Jessie with gdm3 as the login manager. The system has systemd installed. When the system is idle for few minutes (but before the limit set in the KDE screensaver settings), the screen will blank and will not come back on keypress or mouse movements. I have to close the lid of the laptop to let the system suspend. After resume I will get the unlock window of the screensaver and can continue working. I can login using SSH when this happens but couldn't find anything in the logs that could explain this. Any ideas on how to further debug this issue is appreciated. Are there any other reports about similar behaviour? Regards, Rik -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- closing for the reasons given by Julien: The debian bug tracking system is not a user support forum. The 'general' pseudo package even less so. There are other places for this, such as the debian-user list. signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#772509: ITP: ubertooth -- Open source wireless development platform suitable for Bluetooth experimentation
Package: wnpp Severity: wishlist Owner: Ruben Undheim * Package name: ubertooth Version : 201404R1-1 Upstream Author : Mike Ossmann * URL : http://ubertooth.sourceforge.net/ * License : GPL-2+ Programming Lang: C Description : Open source wireless development platform suitable for Bluetooth experimentation Project Ubertooth is an open source wireless development platform suitable for Bluetooth experimentation. Ubertooth ships with a capable BLE (Bluetooth Smart) sniffer and can sniff some data from Basic Rate (BR) Bluetooth Classic connections. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141207232019.9328.57881.report...@miniserver.beebeetle.com
