Bug#726976: ldap-account-manager: Pre-Authentication Cross-Site-Scripting in current_language parameter
Package: ldap-account-manager Version: 4.3 Severity: grave Tags: security Justification: user security hole === Security Advisory === ldap-account-manager-4.3 - PreAuth XSS Affected Version ldap-account-manager-4.3, ldap-account-manager-4.2.1 and possibly others Problem Overview Technical Risk: medium Likelihood of Exploitation: medium Vendor: Debian / Roland Gruber Reported by: Eric Sesterhenn Advisory updates: http://www.rusty-ice.de/advisory/advisory_2013001.txt Advisory Status: Private Problem Impact == While taking a quick lock at the ldap account manager, a XSS issue has been found. It is possible to execute JavaScript in a victims' browser after tricking the victim to post certain data to the website. Problem Description === The file "./templates/login.php" contains an Cross-Site-Scripting Issue on line 122. When the parameter current_language is set to malicious input (e.g. foo%3A">alert(1)%3Abar) JavaScript is executed in the victims' browser. The parameter current_language is retrieved from $_SESSION['language'] in line 119, which is a copy of $_POST['language'] (line 117). Temporary Workaround and Fix Apply the following patch to properly encode the variable: --- templates/login.php.orig2013-09-25 07:53:03.107208062 +0200 +++ templates/login.php 2013-09-25 07:53:20.715207533 +0200 @@ -119,7 +119,7 @@ if (isset($_POST['language'])) { $current_language = explode(":",$_SESSION['language']); $_SESSION['header'] = "http://www.w3.org/TR/html4/loose.dtd\";>\n\n"; $_SESSION['header'] .= "\n\n"; -$_SESSION['header'] .= "\n"; +$_SESSION['header'] .= "\n"; $_SESSION['header'] .= "\n "; /** History === 25.09.2013 - Issue detected 20.10.2013 - Vendor notified -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724700: me-tv: new upstream version
It should be noted that the 1.4 is based on the 2.0 rewrite (yes, so 1.4 > 2.0 > 1.3), and has not seen new development for over a year. When I tested those in 2012, I found that the 2.0/1.4 seemed problematic / unstable. While 1.3 also had its problems, the most critical of those were patched by the author and included in the Debian uploads I did. So unless the 1.4 branch picks up development again and becomes truly stable, I'd suggest staying at 1.3.x and maybe adding some patches to it / upstream. Based on my experience I would consider 1.4 more an experimental branch than a stable followup series to 1.3. -Timo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#725854: ITA: mongodb -- object/document-oriented database (metapackage)
Hi, On Mon, Oct 14, 2013 at 10:00 AM, Jérémy Lal wrote: > I have moved the old mongo-debian github repository to > a collab-maint one with a "standard" gbp layout: > > http://anonscm.debian.org/gitweb/?p=collab-maint/mongodb.git > > László, could you do a git-import-orig there and replay your > changes on master branch ? I've replayed my changes there. Please have a look and note if it's OK for me to do the upload. It builds fine in my pbuilder both for Sid and Wheezy. Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#569668: some progress
Hi, > Status: > * davmail runs a second computer > * IMAP works fine > * SMTP doesn't work yet > * now investigating what is wrong the SMTP part in my second configuration. Are you using the version which is on git://anonscm.debian.org/pkg-java/davmail.git ? Because I had an issue with IMAP, it did not include mail headers in messages. This was caused by depending on gnumail instead of javamail. Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#651965: xserver-xorg-video-nouveau: corrupt glyphs and icons in gnome-shell on NV34 [GeForce FX 5200]
Hi Adrian-- On 10/20/2013 05:38 PM, John Paul Adrian Glaubitz wrote: >> I'm seeing corrupted text glyphs and icons in the latest gnome-shell >> (from either unstable or experimental). I believe it's a problem with >> the nouveau driver (maybe specific to this particular model of card?) > > I have been playing around with an old PowerMac G5 which I borrowed as > a PPC porterbox and it happens to have this particular video adapter > as well. > > Initially, I installed Debian Wheezy onto the Mac and ran into many > rendering issues with nouveau and gnome-shell and the latter happened > to crash very often. > > However, upgrading everything to unstable resolved both the rendering > issues as well as the gnome-shell crashes. I think Mesa upstream fixed > many nouveau issues in the newer Mesa releases, so you should definitely > give that a try in case you still have this machine around, so we might > be able to close this bug ;). thanks for the nudge. i dug out the old machine and tried gnome shell from sid on it. I agree that the glyphs no longer have the problems i was describing, so this bug specifically could probably be closed. however, when mousing over the icons, the usual subtle gnome mouseover highlight visual response was replaced with jarring, tearing visuals. i'm not even sure how to capture them, but the background of the items turn weird colors and have artifacts strewn around in them. > Additionally, it would be interesting to know whether 3D hardware > acceleration works on your laptop ?? i don't know of any laptop related to this bug report. The dell dimension 8300 is a desktop machine -- are you referring to that, or to something else? > after upgrading to the Mesa > version in experimental (9.2.1-1). I figured out that after upgrading > to 9.2.1-1, Mesa could no longer load the nouveau_dri.so module > which I could resolve by downgrading libgl1-mesa-dri to 9.1.7-1 > again (I didn't have to downgrade the rest of Mesa). What would be the best way to go about testing and reporting whether 3D hardware acceleration works or does not work in this case? --dkg signature.asc Description: OpenPGP digital signature
Bug#726891: Closing laptop lid when set to do nothing
I use Gnome Classic v3.4.2 of Debian 7.2. Patrik On 10/20/2013 11:42 PM, Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Sun, 2013-10-20 at 12:26 +0200, Patrik Nilsson wrote: >> package: Linux >> >> I have set actions on laptop close to be nothing, both on battery and >> AC. Often the computer puts itself into sleep mode and wakes up again >> when I open the lid. >> >> This is very annoying since I always run a shutdown script, which >> backups up data, and then shutdowns down the computer. >> >> It is also a possible security issue, since my LUKS password to my >> harddisk is saved into ram. > > The kernel doesn't choose this, it's up to acpi-support and whatever > hooks into that (e.g. upower). > > If you tell us what desktop environment you're using then maybe this can > be reassigned accordingly. > > Ben, > -- PGP-key fingerprint: 1B30 7F61 AF9E 538A FCD6 2BE7 CED7 B0E4 3BF9 8D6C -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726954: [winff] Unknown encoder 'libvo_aacenc'
Control: tags -1 moreinfo On 10/21/13 00:04, Marek Straka wrote: > I am trying to convert one mpg video to another format (package > "libvo-aacenc0" is installed on my system): Is libavcodec-extra-54 (or 53) installed, as suggested by the package? Libraries like libvo-aacenc0 are not used by avconv if not linked during package build (which has some license implications so therefor two versions of libavcodec). I assume you are running testing or unstable (apart from the libavcodec info also that information was missing from your report, please use "reportbug" to report bugs). Paul signature.asc Description: OpenPGP digital signature
Bug#726975: bilibop: [INTL:ja] New Japanese translation
Package: bilibop Version: 0.4.17 Severity: wishlist Tags: patch l10n Dear bilibop package maintainer, Here's Japanese po-debconf template translation (ja.po) file that reviewed by several Japanese Debian developers and users. Could you apply it, please? -- victory http://userscripts.org/scripts/show/102724 0.0.1.4 http://userscripts.org/scripts/show/163846 0.0.1 http://userscripts.org/scripts/show/163848 0.0.1 bilibop_0.4.17_ja.po.gz Description: Binary data
Bug#726973: apt-listdifferences: [INTL:ja] New Japanese translation
Package: apt-listdifferences Version: 1.20130825 Severity: wishlist Tags: patch l10n Dear apt-listdifferences package maintainer, Here's Japanese po-debconf template translation (ja.po) file that reviewed by several Japanese Debian developers and users. Could you apply it, please? -- victory http://userscripts.org/scripts/show/102724 0.0.1.4 http://userscripts.org/scripts/show/163846 0.0.1 http://userscripts.org/scripts/show/163848 0.0.1 apt-listdifferences_ja.po.gz Description: Binary data
Bug#726974: trigger-rally: opens in full-screen mode & changes the default screen resolution
Package: trigger-rally Version: 0.6.0-1+b2 Severity: normal Dear Maintainer, * What led up to the situation? go to menu & click trigger * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? changes the default screen resolution. * What outcome did you expect instead? the screen resolution should be unchanged. i have to logout in order to change the screen resolution. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages trigger-rally depends on: ii libalut0 1.1.0-3 ii libc6 2.17-93 ii libgcc1 1:4.8.2-1 ii libgl1-mesa-glx [libgl1] 9.1.7-1 ii libglew1.71.7.0-3 ii libglu1-mesa [libglu1]9.0.0-2 ii libopenal11:1.14-4 ii libphysfs12.0.3-2 ii libsdl-image1.2 1.2.12-5 ii libsdl1.2debian 1.2.15-7 ii libstdc++64.8.2-1 ii libtinyxml2.6.2 2.6.2-2 ii trigger-rally-data0.6.0-1 trigger-rally recommends no packages. trigger-rally suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726972: wireshark: dissected Server Key Exchange packet does not display DH parameters for TLS 1.2 streams with DHE
Package: wireshark Version: 1.10.2-2 Severity: normal I used wireshark to dissect packets coming from a range of TLS connections, all negotiating a DHE key exchange mechanism (e.g. TLS_DHE_RSA_WITH_AES_128_CBC_SHA) When the packets were TLS 1.2 packets, the server key exchange mechanism will print the length of the key exchange, but does not display the details. When the stream is TLS 1.1 or 1.0, the packets containing a "Server Key Exchange" element show the DH parameters (p, g, and public key). When the stream is TLS 1.2, the packets containing a "Server Key Exchange" element only show the length, but are not dissected properly so none of the details show up. --dkg -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wireshark depends on: ii libc62.17-93 ii libcairo21.12.16-2 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libglib2.0-0 2.36.4-1 ii libgtk-3-0 3.8.4-1 ii libpango-1.0-0 1.32.5-5+b1 ii libpangocairo-1.0-0 1.32.5-5+b1 ii libpcap0.8 1.4.0-2 ii libportaudio219+svn2021-2 ii libwireshark31.10.2-2 ii libwiretap3 1.10.2-2 ii libwsutil3 1.10.2-2 ii wireshark-common 1.10.2-2 ii xdg-utils1.1.0~rc1+git20111210-7 ii zlib1g 1:1.2.8.dfsg-1 wireshark recommends no packages. wireshark suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726268: libmpfr4: mpfr_fits_u* failures
tags 726268 +upstream +fixed-upstream +pending thanks Hi, * Vincent Lefevre [Mon, Oct 14, 2013 at 02:23:36AM +0200]: > It could be a good idea to upgrade to 3.1.2 and apply the patches > before the freeze. Yup, thanks for the notice. The upload should happen sometime this week. Laurent. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726602: mpfr4: sh4: Please change optimize from O3 to O0
tags 726602 +pending thanks Hi, * Nobuhiro Iwamatsu [Thu, Oct 17, 2013 at 03:15:21PM +0900]: > I am a porter of Renesas sh4. > mpfr4 ftbfs on unstable of sh4, because this fails to build in O3. > > http://buildd.debian-ports.org/status/fetch.php?pkg=mpfr4&arch=sh4&ver=3.1.1-1&stamp=1375195194 [...] > I confirmed that this can be built with O1. > when target architecture is sh4, could you set to O1? Thanks for the report, and the patch. I'll include it in the next upload, probably this week. Is this a know compiler issue? Laurent. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726959: [rhythmbox] (rhythmbox:23553): Gtk-WARNING **: mnemonic "p" wasn't removed for widget (0x94b32a0)
Control: tags -1 - l10n patch security Control: severity -1 normal Hi On Sun, Oct 20, 2013 at 09:09:01PM -0200, Weiller Ronfini wrote: > Package: rhythmbox > Version: 3.0.1-1 > Severity: important > Tags: l10n patch security > X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org > > --- (rhythmbox:23553): Gtk-WARNING **: mnemonic "p" wasn't removed for widget > (0x94b32a0) --- Thanks for your bugreports. Note I'm not the maintainer of this package, but I have removed the additional tags (l10n, as this is not localization related; patch, no patch attached; security, looks is not security relevant -- please do not arbitrarly tag bugs, but be as specific as possible). Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726971: gnutls-doc: many of /usr/share/doc/gnutls-doc/examples/*.c #include "examples.h", which is not shipped
Package: gnutls-doc Version: 3.2.4-5 Severity: normal Tags: patch Dear Maintainer, trying to compile example code in /usr/share/doc/gnutls-doc/examples/*.c usually fails because many of those examples have: #include "examples.h" but there is no examples.h shipped. It is present in doc/examples, though. I suspect this patch should resolve the problem: --- a/debian/gnutls-doc.examples2013-10-06 12:05:28.0 -0400 +++ b/debian/gnutls-doc.examples2013-10-21 00:39:43.571785093 -0400 @@ -1 +1,2 @@ doc/examples/*.c +doc/examples/*.h Thanks for maintaining gnutls in debian! --dkg -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726961: [google-chrome-stable] I can not update the package google-chrome-stable available in the directory.
Hi On Sun, Oct 20, 2013 at 09:14:56PM -0200, Weiller Ronfini wrote: > Package: google-chrome-stable > Version: 30.0.1599.66-1 > Severity: important > Tags: l10n patch security > X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org > > --- I can not update the package google-chrome-stable available in the > directory. The same claim is missing three files because I've been > investigating and the same, which are lib32gcc1 (> = 1:4.1.1) lib32stdc + +6 > (> = 4.6) libc6-i386 (> = 2.11), and they are only available for the 64-bit > architecture, not 32-bit. --- There is no such Package google-chrome-stable in the Debian archive. Closing this bug. As a side note: You have reported mutliple bugreports so far, that's good. I noticed that most of them you have tagged l10n patch and security. Please do not set arbitrary tags on bugs, as also for the above there was no patch, and it's hardly a security issue, neither it was related to localization. Regards Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726970: freebsd-glue: Broken funopen() implementation
Source: freebsd-glue Source-Version: 0.1.11 Severity: important Hi, The funopen() implementation in this package uses nested functions to wrap the argument hooks, but it returns a FILE structure pointing to those nested functions and their references to arguments from the stack, to be accessed outside of the function lexical scope, which is just wrong. I've not tested if this currently breaks, but this is explicitly stated as broken usage. In 2011 I started some draft code to add funopen() support to libbsd, but left it aside given the various issues with the interface. I've just finished and polished a full implementation, and pushed to libbsd's git master, it will be included in 0.7.0. Regards, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724922: [Pkg-electronics-devel] Bug#724922: geda-gaf: FTBFS: dh_auto_test fork bombs
Kurt Roeckx writes: > It seems that the last upload (1:1.8.2-2) killed at least 4 > buildds. This includes amd64 (brahms), armhf (hoiby), > armel (alwyn, ancina). I understand that some of them are > still down because of it. That's unfortunate. What does "killed" mean here? I'd love to know what the failure mode is/was. I see that all architectures except armel and armhf have successfully built 1.8.2-2 now. It will be a few days before I have time to look at this again. In the meantime, I've got a bug open requesting the armel and armhf binaries be flushed so that 1.8.2-2 can promote to testing. Bdale pgpEEph6dF0RW.pgp Description: PGP signature
Bug#607193:
On Fri, Oct 18, 2013 at 3:16 AM, Laura Arjona wrote: > In addition to this, the patch uses the word "Inofficial" which sounds > strange to me (but I'm a non-native English speaker), maybe it should > say "non official" as in the warning text? The correct English would be "unofficial images" or "these images are not official". -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#448908: Has it been fixed?
This bug is still in Ubuntu 12.04 and I was wondering if its been fixed yet? There is a workaround available by using aptitude but as this is not part of a standard install now and apt-get is regarded as the preferred method of installation, it would be better if this be fixed so that tools like debconf-apt-progress work correctly with it.
Bug#726969: libarpack2: Please update symbols file to fix FTBFS on m68k
Package: libarpack2 Version: 3.1.3-4 Severity: normal Hi, arpack recently failed to build on one of our m68k builds [1]. Could you please update the symbols file to include the appropriate lines in the debian/libparpack2.symbols to reflect the m68k architecture as well? Cheers, Adrian > [1] > http://buildd.debian-ports.org/status/fetch.php?pkg=arpack&arch=m68k&ver=3.1.3-4&stamp=1382056609 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#719943: makedumpfile: fails to dump kernel log, continually appends the line "[ 0.000000] " to dmesg file
Unfortunately I no longer have any of those crash dumps available to send you anything, I had sent what I had gotten to the kernel maintainers previously in an attempt to track down the cause of the crashing, which I don't believe was ever figured out exactly but was ultimate fixed in a later kernel version. I don't know if they would still happen to have it on hand or not, though. For what it's worth, there never was a vmcore file created any time I did get a dump, instead I always got two separate files, one which is the main core dump and one which is supposed to be the dmesg log dump which unfortunately was never actually able to be dumped (the issue I filed this bug report about). If the end result is supposed to be one vmcore file, I suspect the inability of makedumpfile to dump the kernel dmesg log prohibited it from combining the two files into one file. Using the 'log' command from within crash was ultimately useless as well, as the kernel log wasn't dumped, therefore there wasn't any log for crash to open. This issue was with kernel 3.11-rc4-amd64 in its stock configuration. I hope what information I am able to give you proves to be at least somewhat useful. On 2013-10-20 10:29 PM, John Wright wrote: Hi Alex, On Fri, Aug 16, 2013 at 10:12:39PM -0400, Alex Vanderpol wrote: Package: makedumpfile Version: 1.5.4-1 Severity: grave Justification: renders package unusable Dear Maintainer, There seems to be a serious issue with makedumpfile that causes it to fail to dump the kernel log when collecting crash dump information. Instead, the program continues to run indefinitely, continually appending the line "[ 0.00] " to the file as it seems to attempt to dump the log, which, if left alone for any considerable length of time, can rapidly result in a very large, entirely useless dmesg dump file. I have been trying to collect crash dump information for a crash that's triggered whenever Folding@Home's FahCore_a4 attempts to resume an in-progress work unit, however, every crash dump I've collected has had this problem. The main dump file seems to be dumped without a problem (though crash identifies it as a partial dump, possibly due to the kernel log being dumped into a separate file). I hope you can look into this issue and hopefully it can be sorted out soon. Sorry for the long delay in my response. This seems like a serious but not actually grave issue, since the core dump does actually exist (even though you have to interrupt the dmesg extraction). crash identifies the dump as a partial dump because we explicitly ignore zero pages and userspace pages. Within crash, you should be able to use the 'log' command to get the most recent log messages before the crash...assuming crash doesn't break in the same way makedumpfile does. I will try to reproduce this, but I worry the problem might be somewhat specific either to your crash or some other part of your configuration. Would you feel comfortable making the vmcore available to me? It would also help to know the exact kernel version, and access to a dbg package if it's not a stock kernel. Sorry for the issue and thanks for the report! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#719943: makedumpfile: fails to dump kernel log, continually appends the line "[ 0.000000] " to dmesg file
Hi Alex, On Fri, Aug 16, 2013 at 10:12:39PM -0400, Alex Vanderpol wrote: > Package: makedumpfile > Version: 1.5.4-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > There seems to be a serious issue with makedumpfile that causes it to fail to > dump the kernel log when collecting crash dump information. Instead, the > program continues to run indefinitely, continually appending the line "[ > 0.00] " to the file as it seems to attempt to dump the log, which, if left > alone for any considerable length of time, can rapidly result in a very large, > entirely useless dmesg dump file. > > I have been trying to collect crash dump information for a crash that's > triggered whenever Folding@Home's FahCore_a4 attempts to resume an in-progress > work unit, however, every crash dump I've collected has had this problem. The > main dump file seems to be dumped without a problem (though crash identifies > it > as a partial dump, possibly due to the kernel log being dumped into a separate > file). > > I hope you can look into this issue and hopefully it can be sorted out soon. Sorry for the long delay in my response. This seems like a serious but not actually grave issue, since the core dump does actually exist (even though you have to interrupt the dmesg extraction). crash identifies the dump as a partial dump because we explicitly ignore zero pages and userspace pages. Within crash, you should be able to use the 'log' command to get the most recent log messages before the crash...assuming crash doesn't break in the same way makedumpfile does. I will try to reproduce this, but I worry the problem might be somewhat specific either to your crash or some other part of your configuration. Would you feel comfortable making the vmcore available to me? It would also help to know the exact kernel version, and access to a dbg package if it's not a stock kernel. Sorry for the issue and thanks for the report! -- John Wright -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726967: dh_auto_test should *not* be automatically skipped for cross-building
Package: debhelper Version: 9.20130504 On Sun, Aug 18, 2013 at 06:20:03PM +0800, YunQiang Su wrote: > Hi, Steve, > dh_auto_check disable check when cross build by default now, when cross > build, I believe it's a good behavior. > Here we override_dh_auto_check, fellow the behavior of dh_auto_check > will be a good idea. Thanks for making me aware of this. I'm filing a bug against debhelper asking for this behavior to be reverted. debhelper should *not* automatically disable the test suite when cross-building. There are perfectly legitimate cases where you may be cross-building and *do* want to run the test suite, and this behavior change in dh undermines this. If someone wants the test suite to be skipped because they're cross-building, they should use the standard interface for this and set DEB_BUILD_OPTIONS=nocheck. Whereas if someone does want the test suite to be run when cross-building, there is no corresponding interface that lets them override this in the other direction. Joey, could you please revert this change to debhelper? (Added in response to bug #703262; cc:ing that bug's submitter.) Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#726968: [libmwaw-0.1-1] "mac" not capitalized in descriptions
Package: libmwaw-0.1-1 Version: 0.1.10-1 Severity: minor The short description is: import library for some old mac text document "mac" must refer to Macintosh and should be capitalized. By the way, please avoid abbreviating at least in the extended description. The short description is also missing an "s" at the end. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726966: gnome-shell-extension-weather: Temperatures in multi-day info will not change according to Temperature Unit config
Package: gnome-shell-extension-weather Version: 0~20131020.git30174f2-1 Severity: normal Dear Maintainer, After I upgraded the extension, the Temperature Unit is set to °F by default. But as I changed it to °C, the temperature infos in multi-day display are not changed accordingly. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-1-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 Versions of packages gnome-shell-extension-weather depends on: ii dconf-gsettings-backend [gsettings-backend] 0.18.0-1 ii gir1.2-clutter-1.0 1.14.4-3 ii gir1.2-gtk-3.0 3.8.5-1 ii gir1.2-gweather-3.0 3.8.2-3 ii gir1.2-soup-2.4 2.44.1-1 ii gnome-shell 3.8.4-4 Versions of packages gnome-shell-extension-weather recommends: ii gnome-tweak-tool 3.8.1-2 gnome-shell-extension-weather suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#710498: subversion: enable java components on mips and mipsel
On Fri, May 31, 2013 at 08:28:21AM -0400, Harry Prevor wrote: > I've noticed as per the buildd logs that subversion is built on mips > and mipsel only with the --disable-java flag, while on all other > architectures it is not built with this flag. All other Debian-supported architectures. There are debian-ports.org architectures which are also blacklisted. > Considering java works fine on mips and mipsel, I'd like that build > flag to be removed for those architectures so packages like > libsvn-java (which a lot of packages, including NetBeans, depend on) > can be built. I'd tend to agree. mips(el) were blacklisted 7 years ago. It seems the Java implementations have made some progress since then. I ran test builds (using both gcj and openjdk) on eder.d.o and gabrielli.d.o, both of which ran fine. Peter, what do you think of a) dropping the arch blacklists for Java and b) changing from gcj-jdk to default-jdk? Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy signature.asc Description: Digital signature
Bug#726964: git-email: git-send-email(1) CONFIGURATION section does not mention sendemail.to or sendemail.tocmd
Package: git-email Version: 1:1.8.4~rc3-1 Severity: normal the CONFIGURATION section in the git-send-email(1) man page documents: * sendemail.aliasesfile * sendemail.aliasesfiletype * sendemail.multiedit * sendemail.confirm it does not mention: * sendemail.to * sendemail.tocmd it should mention both of them for completeness. Feel free to forward this upstream. Thanks for maintaining git in debian! --dkg -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git-email depends on: ii git 1:1.8.4~rc3-1 Versions of packages git-email recommends: pn libauthen-sasl-perl ii libemail-valid-perl 1.192-1 ii libnet-smtp-ssl-perl 1.01-3 Versions of packages git-email suggests: pn git-doc -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726963: cannot reproduce several *.tar.xz files (possibly tar issue?)
Package: pristine-tar Version: 1.28 Severity: important I discovered that pristine-tar could no longer generate the original tarballs for openafs, including one that I just created on a different system. The error messages are: wanderer:~/dvl/debian/openafs$ pristine-tar checkout openafs_1.6.5.1.orig.tar.xz xdelta: /tmp/pristine-tar.MRIQzsqRqg/openafs_1.6.5.1.orig.tar.xz.tmp: Checksum validation failed, expected: f872ee04506b8baec8e0f64eb5e3c30f, received: dde5a1aa469e7221bf9f56cc836becad xdelta: /tmp/pristine-tar.yMNZDhZVIq/recreatetarball: Checksum validation failed, expected: 0172fb743ec9492629d5e0f172848ac9, received: a3b994c2709d720e8a091d9448b11532 xdelta: /tmp/pristine-tar.MRIQzsqRqg/openafs_1.6.5.1.orig.tar.xz.tmp: Checksum validation failed, expected: f872ee04506b8baec8e0f64eb5e3c30f, received: dde5a1aa469e7221bf9f56cc836becad xdelta: /tmp/pristine-tar.yMNZDhZVIq/recreatetarball: Checksum validation failed, expected: 0172fb743ec9492629d5e0f172848ac9, received: a3b994c2709d720e8a091d9448b11532 pristine-tar: Failed to reproduce original tarball. Please file a bug report. pristine-tar: failed to generate tarball The failure happens fairly quickly (I'm used to checkouts of xz files taking a noticable amount of time), so I believe from that and from the nature of the error messages that it's failing before the attempted xz compression. I then checked several older ones and they all fail as well. You can reproduce from the public OpenAFS packaging repository at: git://anonscm.debian.org/pkg-k5-afs/openafs.git I am able to check out these tarballs on another system that's running i386 instead of amd64 and (I suspect more relevantly) tar 1.26+dfsg-8. The system where this fails has tar 1.27-1. Maybe something changed in the new release? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pristine-tar depends on: ii libbz2-1.01.0.6-5 ii libc6 2.17-93 ii perl-modules 5.18.1-4 ii xdelta1.1.3-9 ii zlib1g1:1.2.8.dfsg-1 Versions of packages pristine-tar recommends: ii bzip2 1.0.6-5 ii pbzip21.1.8-1 ii xz-utils 5.1.1alpha+20120614-2 pristine-tar suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#694744: working on the bugs-everywhere package
On 20-Oct-2013, anarcat wrote: > Ben, are you still interested in maintaining this package? Can I make a > tentative upload to experimental? Following up on our IRC discussion: I have orphaned this package and am not interested in maintaining it. You are welcome to adopt it, and you now have the VCS history for the packaging work to date. Thank you very much for contacting me to confirm. Good hunting to you! -- \ “… a Microsoft Certified System Engineer is to information | `\ technology as a McDonalds Certified Food Specialist is to the | _o__) culinary arts.” —Michael Bacarella | Ben Finney signature.asc Description: Digital signature
Bug#726962: startx(1): Macro '..' is not defined in the manual and some formatting improvements
Package: xinit Version: 1.3.2-1 Severity: minor Tags: patch Dear Maintainer, From "groff -b -ww -mandoc -z": groff::128: warning: macro `.' not defined Input file is /usr/share/man/man1/startx.1.gz Changes (besides the warning): Extra hair space (\^) between two dashes (\-) Changed word 'legal' to 'valid' Added extra word space between \-- and \- as one word space is too small in the output of 'troff' Increased word space between some sentences. Better is to start each sentence on a new line Patch: --- startx.12013-10-20 22:44:10.0 + +++ startx.1.new2013-10-20 23:14:57.0 + @@ -54,7 +54,7 @@ Arguments immediately following the command are used to start a client in the same manner as .BR xinit (1). The special argument -.RB '--' +.RB ' \-\^\- ' marks the end of client arguments and the beginning of server options. It may be convenient to specify server options with startx to change on a per-session basis the @@ -65,14 +65,16 @@ permitted by the server and specified in the .BR xorg.conf (5) configuration. Some examples of specifying server arguments follow; consult -the manual page for your X server to determine which arguments are legal. +the manual page for your X server to determine which arguments are valid. .RS .PP -startx -- -depth 16 +.\" One word space between \- and \- is too short in the output of +.\" troff. +startx \-\^\- \-depth 16 .PP -startx -- -dpi 100 +startx \-\^\- \-dpi 100 .PP -startx -- -layout Multihead +startx \-\^\- \-layout Multihead .RE .if ''' .ig .PP @@ -85,7 +87,7 @@ instead; this permits the same X environ .IR xdm , or .I xinit -is used to start the X session. All discussion of the +is used to start the X session. All discussion of the .I .xinitrc file in the .IR xinit (1) @@ -125,7 +127,7 @@ the file in the .I xinit library directory. -.. +. If command line client options are given, they override this behavior and revert to the .BR xinit (1) -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i586) Kernel: Linux 3.2.46-1-rt67-1 Locale: LANG=is_IS, LC_CTYPE=is_IS (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages xinit depends on: ii coreutils 8.13-3.5 ii libc6 2.13-38 ii libx11-62:1.5.0-1+deb7u1 ii x11-common 1:7.7+3~deb7u1 ii xauth 1:1.0.7-1 Versions of packages xinit recommends: ii xserver-xorg [xserver] 1:7.7+3~deb7u1 ii xterm [x-terminal-emulator] 278-4 xinit suggests no packages. -- Configuration Files: /etc/X11/xinit/xserverrc changed [not included] -- no debconf information -- Bjarni I. Gislason -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672808: aylet: couldn't open sound device.
On 20 October 2013 13:15, Ivan Shmakov wrote: >> Dmitry Semyonov writes: > > However, I believe that alsa-oss should /not/ be in Depends:, > for aylet(1) can also be used on a completely mute system. > (Think of a file server performing automated .ay to .oga > conversion, for instance.) > > Suggests: seems to be a safe choice, though. Depends: is still feasible since package description claims: "aylet plays music files". I.e. this is "a significant amount of functionality" which qualifies for Depends: per Debian Policy. Suggests: is too weak, in my opinion. I'd rather use "Recommends: oss-compat" if Depends is chosen to be avoided. -- ...Bye..Dmitry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#725703: Should be safe to enable
ZSWAP requires to compile the kernel with CONFIG_ZSWAP=y in config Being a new feature, its disabled by default. Requires boot time option zswap.enabled=1 to be passed into the kernel to be enabled. Compile it in shouldn't cause any ill effects. https://www.kernel.org/doc/Documentation/vm/zswap.txt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726961: [google-chrome-stable] I can not update the package google-chrome-stable available in the directory.
Package: google-chrome-stable Version: 30.0.1599.66-1 Severity: important Tags: l10n patch security X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org --- I can not update the package google-chrome-stable available in the directory. The same claim is missing three files because I've been investigating and the same, which are lib32gcc1 (> = 1:4.1.1) lib32stdc + +6 (> = 4.6) libc6-i386 (> = 2.11), and they are only available for the 64-bit architecture, not 32-bit. --- --- System information. --- Architecture: i386 Kernel: Linux 3.10-3-rt-686-pae Debian Release: jessie/sid 500 wheezy linux.dropbox.com 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org 500 testing cdn.debian.net 500 stable-updates ftp.br.debian.org 500 stable security.debian.org 500 stable ftp.br.debian.org 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed ==-+- gconf-service | 3.2.6-1 libasound2 (>= 1.0.23) | 1.0.27.2-3 libatk1.0-0(>= 1.12.4) | 2.10.0-2 libc6(>= 2.11) | 2.17-93 libcairo2 (>= 1.6.0) | 1.12.16-2 libcups2(>= 1.4.0) | 1.6.3-1 libdbus-1-3(>= 1.2.14) | 1.6.16-1 libexpat1 (>= 1.95.8) | 2.1.0-4 libfontconfig1 (>= 2.8.0) | 2.10.2-2 libfreetype6(>= 2.3.9) | 2.4.9-1.1 libgcc1 (>= 1:4.1.1) | 1:4.8.2-1 libgconf-2-4 (>= 2.31.1) | 3.2.6-1 libgcrypt11 (>= 1.4.5) | 1.5.3-2 libgdk-pixbuf2.0-0 (>= 2.22.0) | 2.28.2-1 libglib2.0-0 (>= 2.18.0) | 2.36.4-1 libgtk2.0-0(>= 2.24.0) | 2.24.21-1 libnspr4 (>= 1.8.0.10) | 2:4.10-1 libnss3(>= 3.14.3) | 2:3.15.1-1 libpango1.0-0 (>= 1.22.0) | 1.32.5-5+b1 libstdc++6(>= 4.6) | 4.8.2-1 libudev0 (>= 147) | 175-7.2 OR libudev1 (>= 198) | 204-5 libx11-6 (>= 2:1.4.99.1) | 2:1.6.2-1 libxcomposite1(>= 1:0.3-1) | 1:0.4.4-1 libxdamage1 (>= 1:1.1) | 1:1.1.4-1 libxext6 | 2:1.3.2-1 libxfixes3 | 1:5.0.1-1 libxrender1| 1:0.9.8-1 libxss1| 1:1.2.2-1 ca-certificates| 20130906 libcurl3 | 7.33.0-1 lsb-base (>= 3.2) | 4.1+Debian12 xdg-utils (>= 1.0.2) | 1.1.0~rc1+git20111210-7 wget | 1.14-4 Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726960: units: exit of value of units --version is non 0
Package: units Version: 1.88 Severity: normal Dear Maintainer, the exit value of "units --version" is 3 instead of 0 (as should be for success). Check the following: $ units --version GNU Units version 1.88 with readline, units database in /usr/share/misc/units.dat Copyright (C) 2006 Free Software Foundation, Inc. GNU Units comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GNU Units under the terms of the GNU General Public License. $ echo $? 3 I'm trying to use "units --version" in a script to check if units is installed in the system when I faced with this problem. I found this quite non-standard. I would expect it to return 0 . -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (500, 'stable'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726473: nss: CVE-2013-1739
On Wed, Oct 16, 2013 at 12:26:49AM -0400, Michael Gilbert wrote: > package: nss > version: 3.12.8-1 > severity: grave > tag: security > > Hi, > > A security issue was recently fixed in nss 3.15.2: > [0] https://security-tracker.debian.org/tracker/CVE-2013-1739 > > For unstable, its probably easiest to just update directly to the > latest upstream version to fix this. Actual patch is still behind a > restricted bug report, so I was not able to fully check affected > versions. The bug was introduced in 3.14.3, so it doesn't affect squeeze. It does, however affect wheezy. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#711311: wontfix
tags 711311 wontfix thanks Using the forking daemon involves changing some settings in php.ini. I don't think it's worth the effort to support update daemon selection during installation. -- Sebastian signature.asc Description: Digital signature
Bug#672808: aylet: couldn't open sound device.
Another, probably better, workaround is oss-compat package: "The purpose of this package is for applications that only support OSS to depend on it, hence preventing common "/dev/dsp not found" errors that would confuse unexperienced users." -- ...Bye..Dmitry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726959: [rhythmbox] (rhythmbox:23553): Gtk-WARNING **: mnemonic "p" wasn't removed for widget (0x94b32a0)
Package: rhythmbox Version: 3.0.1-1 Severity: important Tags: l10n patch security X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org --- (rhythmbox:23553): Gtk-WARNING **: mnemonic "p" wasn't removed for widget (0x94b32a0) --- --- System information. --- Architecture: i386 Kernel: Linux 3.10-3-rt-686-pae Debian Release: jessie/sid 500 wheezy linux.dropbox.com 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org 500 testing cdn.debian.net 500 stable-updates ftp.br.debian.org 500 stable security.debian.org 500 stable ftp.br.debian.org 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-=== libatk1.0-0 (>= 1.12.4) | 2.10.0-2 libc6(>= 2.4) | 2.17-93 libcairo-gobject2 (>= 1.10.0) | 1.12.16-2 libcairo2 (>= 1.2.4) | 1.12.16-2 libgdk-pixbuf2.0-0(>= 2.22.0) | 2.28.2-1 libgirepository-1.0-1 (>= 0.9.2) | 1.36.0-2+b1 libglib2.0-0 (>= 2.34.0) | 2.36.4-1 libgstreamer-plugins-base1.0-0 (>= 1.0.0) | 1.2.0-1 libgstreamer1.0-0 (>= 1.0.0) | 1.2.0-1 libgtk-3-0 (>= 3.6.0) | 3.8.5-1 libgudev-1.0-0 (>= 146) | 204-5 libice6 (>= 1:1.0.0) | 2:1.0.8-2 libjavascriptcoregtk-3.0-0 (>= 1.5.1) | 2.2.0-2 libjson-glib-1.0-0(>= 0.12.0) | 0.16.2-1 libnotify4 (>= 0.7.0) | 0.7.6-1 libpango-1.0-0(>= 1.14.0) | 1.32.5-5+b1 libpangocairo-1.0-0 (>= 1.14.0) | 1.32.5-5+b1 libpeas-1.0-0 (>= 1.0.0) | 1.8.1-2 librhythmbox-core8(= 3.0.1-1) | 3.0.1-1 libsm6| 2:1.2.1-2 libsoup-gnome2.4-1(>= 2.27.4) | 2.44.1-1 libsoup2.4-1 (>= 2.26.0) | 2.44.1-1 libtdb1(>= 1.1.2~git20080520) | 1.2.12-1 libtotem-plparser17 (>= 3.2) | 3.4.5-1+b1 libwebkitgtk-3.0-0(>= 1.3.10) | 2.2.0-2 libx11-6 | 2:1.6.2-1 libxml2 (>= 2.6.27) | 2.9.1+dfsg1-3 zlib1g (>= 1:1.1.4) | 1:1.2.8.dfsg-1 rhythmbox-data(= 3.0.1-1) | 3.0.1-1 dbus | 1.6.16-1 gstreamer1.0-plugins-base (>= 1.0.6) | 1.2.0-1 gstreamer1.0-plugins-good (>= 1.0.6) | 1.2.0-1 gnome-icon-theme | 3.8.3-1 gstreamer1.0-x| 1.2.0-1 media-player-info | 19-1 Recommends (Version) | Installed -+-=== yelp | 3.10.1-1 avahi-daemon | 0.6.31-2 notification-daemon | 0.7.6-1 gstreamer1.0-pulseaudio | 1.2.0-1 gstreamer1.0-plugins-ugly| 1.2.0-1 gvfs-backends| 1.16.3-1+b1 rhythmbox-plugins| 3.0.1-1 Suggests (Version) | Installed ==-+-=== gstreamer1.0-plugins-bad | 1.2.0-4 gnome-codec-install| 0.4.7+nmu2 gnome-control-center | 1:3.8.3-3 rhythmbox-plugin-cdrecorder| 3.0.1-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726953: dgit fails with submodules
On 2013-10-20 18:44:42, Ian Jackson wrote: > Antoine Beaupré writes ("Bug#726953: dgit fails with submodules"): >> On 2013-10-20 18:30:42, Ian Jackson wrote: >> > How do you think dgit should handle these problems ? >> >> Completely ignore the submodules. The original build tree doesn't >> actually need it at all. > > But doesn't git expect to work with (check out, etc.) the submodules > by default ? That's not my experience so far. > So the git tree with the submodule metadata isn't really suitable for > general use by people who are expecting a "normal" git branch. > > Perhaps dgit should be given a special branch with the submodule > metadata removed. (Please tell me you don't intend to publish the > submodule metadata in the .git-less Debian source package.) No, I don't intend to publish that stuff... and yes, maybe the simply fix is to drop the submodule in the debian branch... a. -- From the age of uniformity, from the age of solitude, from the age of Big Brother, from the age of doublethink - greetings! - Winston Smith, 1984 pgpUMWJhCDqqd.pgp Description: PGP signature
Bug#588455: Bug in CUPS?
reassign 588455 libcups2 1.4.4-7+squeeze1 thanks This happens deep down in CUPS, apparently related to its interaction with gnutls. I suspect it might be the same as this bug: https://bugzilla.redhat.com/show_bug.cgi?id=553834 Apparently gnutls 2.12.x addresses this issue; there is also a patch attached to the RedHat bug that should work around the issue in CUPS. signature.asc Description: Digital signature
Bug#726958: glance: [INTL:pt] Updated Portuguese translation for debconf messages
Package: glance Tags: l10n, patch Severity: wishlist Updated Portuguese translation for glance's debconf messages. Translator: Pedro Ribeiro Feel free to use it. For translation updates please contact 'Last Translator' or the Portuguese Translation Team . -- Best regards, "Traduz" - Portuguese Translation Team http://www.DebianPT.org # glance debconf portuguese messages # Copyright (C) 2012 the glance'S COPYRIGHT HOLDER # This file is distributed under the same license as the glance package. # Pedro Ribeiro , 2012 # msgid "" msgstr "" "Project-Id-Version: glance\n" "Report-Msgid-Bugs-To: gla...@packages.debian.org\n" "POT-Creation-Date: 2013-09-25 15:31+0800\n" "PO-Revision-Date: 2013-10-20 23:43+0100\n" "Last-Translator: Pedro Ribeiro \n" "Language-Team: Potuguese \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: select #. Choices #: ../glance-common.templates:2001 msgid "keystone" msgstr "keystone" #. Type: select #. Choices #: ../glance-common.templates:2001 msgid "caching" msgstr "caching" #. Type: select #. Choices #: ../glance-common.templates:2001 msgid "keystone+caching" msgstr "keystone+caching" #. Type: select #. Choices #: ../glance-common.templates:2001 msgid "cachemanagement" msgstr "cachemanagement" #. Type: select #. Choices #: ../glance-common.templates:2001 msgid "keystone+cachemanagement" msgstr "keystone+cachemanagement" #. Type: select #. Description #: ../glance-common.templates:2002 msgid "Pipeline flavor:" msgstr "Tipo de pipeline:" #. Type: select #. Description #: ../glance-common.templates:2002 msgid "Please specify the flavor of the pipeline to be used by Glance." msgstr "Por favor indique o tipo de pipeline a ser utilizado pelo Glance." #. Type: select #. Description #: ../glance-common.templates:2002 msgid "" "If you use the OpenStack Identity Service (Keystone), you might want to " "select \"keystone\". If you don't use this service, you can safely choose " "\"caching\" only." msgstr "" "Se usar o Serviço de Identidade OpenStack (Keystone), pode querer escolher " "\"keystone\". Se não usar este serviço, apenas pode escolher com segurança " "\"caching\"." #. Type: string #. Description #: ../glance-common.templates:3001 msgid "Authentication server hostname:" msgstr "Nome do servidor de autenticação:" #. Type: string #. Description #: ../glance-common.templates:3001 msgid "" "Please specify the hostname of the authentication server for Glance. " "Typically this is also the hostname of the OpenStack Identity Service " "(Keystone)." msgstr "" "Indique o nome do seu servidor de autenticação para o Glance. Normalmente, " "é o nome do seu Serviço de Identidade OpenStack (Keystone)." #. Type: string #. Description #. Translators: a "tenant" in OpenStack world is #. an entity that contains one or more username/password couples. #. It's typically the tenant that will be used for billing. Having more than one #. username/password is very helpful in larger organization. #. You're advised to either keep "tenant" without translating it #. or keep it parenthezised. Example for French: #. locataire ("tenant") #: ../glance-common.templates:4001 msgid "Authentication server tenant name:" msgstr "Nome do 'tenant' do servidor de autenticação:" #. Type: string #. Description #. Translators: a "tenant" in OpenStack world is #. an entity that contains one or more username/password couples. #. It's typically the tenant that will be used for billing. Having more than one #. username/password is very helpful in larger organization. #. You're advised to either keep "tenant" without translating it #. or keep it parenthezised. Example for French: #. locataire ("tenant") #: ../glance-common.templates:4001 msgid "Please specify the authentication server tenant name." msgstr "Indique, por favor, o nome do 'tenant' do servidor de autenticação." #. Type: string #. Description #: ../glance-common.templates:5001 msgid "Authentication server username:" msgstr "Nome de utilizador para o servidor de autenticação:" #. Type: string #. Description #: ../glance-common.templates:5001 msgid "Please specify the username to use with the authentication server." msgstr "" "Indique, por favor, o nome de utilizador para o servidor de autenticação." #. Type: password #. Description #: ../glance-common.templates:6001 msgid "Authentication server password:" msgstr "Palavra chave do servidor de autenticação:" #. Type: password #. Description #: ../glance-common.templates:6001 msgid "Please specify the password to use with the authentication server." msgstr "" "Indique, por favor, a palavra-chave para usar no servidor de autenticação." #. Type: boolean #. Description #: ../glance-common.templates:7001 msgid "Set up a database for Glance?" msgstr "Configurar uma base de dados para o Glance?" #. Type: boolean #. Description #: ../glance-common.templates:7001 msgid "" "No database has been set up for glance
Bug#726953: dgit fails with submodules
Antoine Beaupré writes ("Bug#726953: dgit fails with submodules"): > On 2013-10-20 18:30:42, Ian Jackson wrote: > > How do you think dgit should handle these problems ? > > Completely ignore the submodules. The original build tree doesn't > actually need it at all. But doesn't git expect to work with (check out, etc.) the submodules by default ? So the git tree with the submodule metadata isn't really suitable for general use by people who are expecting a "normal" git branch. Perhaps dgit should be given a special branch with the submodule metadata removed. (Please tell me you don't intend to publish the submodule metadata in the .git-less Debian source package.) > I'll post the git repo shortly. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726957: initramfs-tools: Please include `ohci-pci` after `ohci-hcd` split to use USB keyboard to enter LUKS password
Package: initramfs-tools Version: 0.114 Severity: critical Justification: breaks the whole system Control: affects -1 linux-image-3.11-1-amd64 Dear Debian folks, upgrading to `linux-image-3.11-1-amd64` I was not able to enter the LUKS password while it works without problems using `linux-image-3.10-3-amd64`. benh told me in #debian-kernel on , that it is probably due to the split of the Linux module `ohci-hcd` and the module `ohci-pci` is required in initramfs for using the USB keyboard. It would be awesome if you could add it (also for Debian Backports). I will be able to test the fix on Monday or Tuesday. Thanks, Paul -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 9.4M May 7 2009 /boot/initrd.img-2.6.29-1-amd64 -rw-r--r-- 1 root root 9.3M May 1 2009 /boot/initrd.img-2.6.29-1-amd64.bak -rw-r--r-- 1 root root 9.6M Jun 20 2009 /boot/initrd.img-2.6.29-2-amd64 -rw-r--r-- 1 root root 9.4M May 26 2009 /boot/initrd.img-2.6.29-2-amd64.bak -rw-r--r-- 1 root root 11M Feb 23 2013 /boot/initrd.img-2.6.32-5-686 -rw-r--r-- 1 root root 11M Feb 23 2013 /boot/initrd.img-2.6.32-5-amd64 -rw-r--r-- 1 root root 14M Sep 23 18:00 /boot/initrd.img-3.10-3-686-pae -rw-r--r-- 1 root root 14M Sep 23 19:23 /boot/initrd.img-3.10-3-amd64 -rw-r--r-- 1 root root 26M Oct 19 11:17 /boot/initrd.img-3.10.0+ -rw-r--r--. 1 root root 26M Jun 21 09:27 /boot/initrd.img-3.10.0-rc6+ -rw-r--r--. 1 root root 26M Jun 29 12:15 /boot/initrd.img-3.10.0-rc7+ -rw-r--r-- 1 root root 13M Oct 12 20:30 /boot/initrd.img-3.2.0-4-686-pae -rw-r--r-- 1 root root 13M Oct 12 20:31 /boot/initrd.img-3.2.0-4-amd64 -rw-r--r-- 1 root root 25M Jul 31 2012 /boot/initrd.img-3.5.0+ -rw-r--r-- 1 root root 26M Dec 13 2012 /boot/initrd.img-3.7.0+ -rw-r--r-- 1 root root 26M Dec 21 2012 /boot/initrd.img-3.7.1 -rw-r--r-- 1 root root 26M Jan 25 2013 /boot/initrd.img-3.7.1+ -rw-r--r-- 1 root root 26M May 18 20:06 /boot/initrd.img-3.7.5+ -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.10-3-686-pae root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave -- resume RESUME=/dev/mapper/speicher-swap -- /proc/filesystems btrfs ext3 fuseblk xfs reiserfs -- lsmod Module Size Used by arc4 12487 2 rt2800usb 17747 0 rt2x00usb 13392 1 rt2800usb rt2800lib 55996 1 rt2800usb rt2x00lib 37589 3 rt2x00usb,rt2800lib,rt2800usb mac80211 309057 3 rt2x00lib,rt2x00usb,rt2800lib cfg80211 264217 2 mac80211,rt2x00lib crc_ccitt 12331 1 rt2800lib rfkill 18706 3 cfg80211 ip6table_filter12492 0 ip6_tables 17022 1 ip6table_filter iptable_filter 12488 0 ip_tables 17010 1 iptable_filter x_tables 18124 4 ip6table_filter,ip_tables,iptable_filter,ip6_tables binfmt_misc12789 1 reiserfs 177128 1 xfs 553122 2 hwmon_vid 12398 0 loop 18067 0 firewire_sbp2 17632 0 firewire_core 39334 1 firewire_sbp2 crc_itu_t 12331 1 firewire_core fuse 61469 1 snd_hda_codec_realtek31992 1 snd_hda_codec_hdmi 31192 1 snd_hda_intel 31021 5 snd_hda_codec 102848 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel snd_hwdep 12939 1 snd_hda_codec snd_pcm_oss36297 0 snd_mixer_oss 17770 1 snd_pcm_oss snd_pcm57885 4 snd_pcm_oss,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel snd_page_alloc 12910 2 snd_pcm,snd_hda_intel snd_seq_midi 12744 0 snd_seq_midi_event 13124 1 snd_seq_midi snd_rawmidi22551 1 snd_seq_midi powernow_k817256 1 snd_seq39569 2 snd_seq_midi_event,snd_seq_midi snd_seq_device 13016 3 snd_seq,snd_rawmidi,snd_seq_midi snd_timer 22217 2 snd_pcm,snd_seq evdev 17266 13 psmouse64900 0 serio_raw 12812 0 i2c_viapro 12480 0 k8temp 12631 0 snd42832 22 snd_hda_codec_realtek,snd_pcm_oss,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_mixer_oss radeon621535 4 shpchp 26762 0 ttm52618 1 radeon soundcore 12890 1 snd drm_kms_helper 27237 1 radeon drm 165528 6 ttm,drm_kms_helper,radeon processor 27839 1 powernow_k8 i2c_algo_bit 12713 1 radeon i2c_core 19505 5 drm,drm_kms_helper,i2c_algo_bit,i2c_viapro,radeon parport_pc 220
Bug#726953: dgit fails with submodules
On 2013-10-20 18:30:42, Ian Jackson wrote: > Antoine Beaupré writes ("Bug#726953: dgit fails with submodules"): >> Package: dgit >> Version: 0.15 >> Severity: normal >> >> This one is a little hairy, but regardless... > ... >> I will try to push this git repo online once I have the benediction of >> the current maintainer, for further testing. > > I'm not sure exactly what's going on here but AFAICT you are trying to > do dgit push on a branch which contains git submodule metadata - ie, > where the complete source tree depends on these other modules. That is correct. > How do you think dgit should handle these problems ? Completely ignore the submodules. The original build tree doesn't actually need it at all. > (I tried a dgit clone of bugs-everywhere and found it was only in > squeeze, and the clone seemed to work just fine.) Yeah, you need to merge it with upstream and do all bunch of crazy things to update it to the latest version. I'll post the git repo shortly. A. -- C'est trop facile quand les guerres sont finies D'aller gueuler que c'était la dernière Amis bourgeois vous me faites envie Ne voyez vous pas donc point vos cimetières? - Jaques Brel pgpzI4mabt7Nb.pgp Description: PGP signature
Bug#725864: pu: package smplayer/0.8.0-1
Control: tags -1 + pending On Wed, 2013-10-09 at 11:37 +0100, Alessio Treglia wrote: > On Wed, Oct 9, 2013 at 11:33 AM, Cyril Brulebois wrote: > > That would be too late for 7.2 (p-u-NEW froze past weekend). > > I'm sorry for the delay, I'll wait until the next point release then. > > > Please use 0.8.0-1+deb7u1 instead. > > Sure, committed to git, thanks. The package was uploaded, and I've just flagged it for acceptance into p-u; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726956: rnano(1): Unnecessary escape for '+' in the manual and some formatting improvements
Package: nano Version: 2.2.6-1+b1 Severity: minor Tags: patch Dear Maintainer, From "groff -b -ww -mandoc -z": /home/bg/opt/share/groff/1.21/tmac/an-old.tmac:388: backtrace: macro `I' :32: warning: escape character ignored before `+' /home/bg/opt/share/groff/1.21/tmac/an-old.tmac:382: backtrace: macro `B' :66: warning: escape character ignored before `+' Input file is /usr/share/man/man1/rnano.1.gz Changes (besides warnings): Space between some sentences increased. Better is to start each sentence on a new line. Space between italic and roman characters adjusted with \/ or \, - changed to \- if it means an option Patch: --- rnano.1 2013-10-17 00:05:37.0 + +++ rnano.1.new 2013-10-20 22:07:52.0 + @@ -29,7 +29,7 @@ Pico clone .SH SYNOPSIS .B rnano -.I [OPTIONS]\ [[\+LINE,COLUMN]\ FILE]... +.I [OPTIONS]\ [[+LINE,COLUMN]\ FILE]... .br .SH DESCRIPTION @@ -39,7 +39,7 @@ This manual page briefly documents the \ .\" \fI\fP escape sequences to invoke bold face and italics, .\" respectively. \fBnano\fP is a small, free and friendly editor which aims to replace -Pico, the default editor included in the non-free Pine package. Rather +Pico, the default editor included in the non-free Pine package. Rather than just copying Pico's look and feel, \fBnano\fP also implements some missing (or disabled by default) features in Pico, such as "search and replace" and "go to line and column number". @@ -48,7 +48,7 @@ replace" and "go to line and column numb specific files and doesn't allow the user access to the filesystem or a command shell. .PP -In restricted mode, \fBnano\fP will \fInot\fP: +In restricted mode, \fBnano\fP will \fInot\/\fP: .IP \[bu] 2 read or write to any file not specified on the command line; .IP \[bu] @@ -63,13 +63,13 @@ use backup files or spell checking. .SH OPTIONS .TP -.B \+\fILINE\fP,\fICOLUMN\fP +.B +\fILINE\fP,\fICOLUMN\fP Places cursor at line number \fILINE\fP and column number \fICOLUMN\fP (at least one of which must be specified) on startup, instead of the default of line 1, column 1. .TP .B \-? -Same as \fB-h (\-\-help)\fP. +Same as \fB\-h (\-\-help)\fP. .TP .B \-h (\-\-help) Show a summary of command line options and exit. -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i586) Kernel: Linux 3.2.46-1-rt67-1 Locale: LANG=is_IS, LC_CTYPE=is_IS (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages nano depends on: ii dpkg 1.16.10 ii install-info 4.13a.dfsg.1-10 ii libc6 2.13-38 ii libncursesw5 5.9-10 ii libtinfo5 5.9-10 nano recommends no packages. Versions of packages nano suggests: pn spell -- no debconf information -- Bjarni I. Gislason -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680949: I agree with Hugh Davenport.
I agree with Hugh Davenport.
Bug#726953: dgit fails with submodules
Antoine Beaupré writes ("Bug#726953: dgit fails with submodules"): > Package: dgit > Version: 0.15 > Severity: normal > > This one is a little hairy, but regardless... ... > I will try to push this git repo online once I have the benediction of > the current maintainer, for further testing. I'm not sure exactly what's going on here but AFAICT you are trying to do dgit push on a branch which contains git submodule metadata - ie, where the complete source tree depends on these other modules. Have I understood this right ? I don't think this is going to work without a significant amount of extra thought, and then probably lots and lots of work. Thinking about it, it's going to be very troublesome. dgit would need to ensure that the submodules were available in the dgit-repos, somehow, and decide how their branches were to be managed. Also, you have the problem that dgit wouldn't know how to convert non-dgit-based uploads into the submodule structure. How do you think dgit should handle these problems ? (I tried a dgit clone of bugs-everywhere and found it was only in squeeze, and the clone seemed to work just fine.) Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726248: sdt.h conflict with kfreebsd-kernel-headers and systemtap-sdt-dev
On 20/10/2013 15:31, Mark Wielaard wrote: > It would be good to know if it actually works and has any programs/users. > I was only asking because if user space dtrace does work then it might > be a good idea to make it understand the sys/sdt.h variant ELF notes. > But if there are no programs/users for it currently then it would be > easier to resolve the conflict between the packages. I don't know enough > about Debian kfreebsd to tell what (user space) solution is best. Thank you (and Frank) for the in-depth explanation. Well I think it doesn't hurt to let systemtap-sdt-dev provide sys/sdt.h at least for the time being. If later on (i.e. when we actually have DTrace) we find out that there are significant shortcomings, we can always revert that decision. In the meantime this will allow us to verify that the magic in GDB also works on GNU/kFreeBSD. My suggestion, assuming everyone is okay with it, would be that you make this package arch-all and add a: Replaces: kfreebsd-kernel-headers [kfreebsd-any] to debian/control. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726955: dgit cannot clone from "squeeze" but "oldstable" works
Package: dgit Version: 0.15 See the transcript. The key line is this: W: suite 'squeeze' not recognised. from dak ls. Ian. zealot:tests> rm -rf bugs-everywhere zealot:tests> dgit -D --dget:-u clone bugs-everywhere squeeze | ssh 'i...@coccia.debian.org' 'set -e; cd /srv/ftp-master.debian.org/ftp/dists; if test -h squeeze; then readlink squeeze; exit 0; fi; if test -d squeeze; then echo squeeze; exit 0; fi; exit 1' => `squeeze' + git init -q + git config remote.dgit.fetch '+refs/dgit/*:refs/remotes/dgit/dgit/*' + git remote add origin 'git+ssh://i...@git.debian.org/git/dgit-repos/repos/bugs-everywhere.git' | ssh 'i...@git.debian.org' ' set -e; cd /git/dgit-repos/repos; if test -d bugs-everywhere.git; then echo 1; else echo 0; fi' => `0' starting new git history | ssh 'i...@coccia.debian.org' dak ls -asource -ssqueeze bugs-everywhere W: suite 'squeeze' not recognised. E: No valid suite given. => `' no version available from the archive previous reference hash= nothing found! dgit: package bugs-everywhere does not exist in suite squeeze zealot:tests> rm -rf bugs-everywhere zealot:tests> dgit -D --dget:-u clone bugs-everywhere oldstable | ssh 'i...@coccia.debian.org' 'set -e; cd /srv/ftp-master.debian.org/ftp/dists; if test -h oldstable; then readlink oldstable; exit 0; fi; if test -d oldstable; then echo oldstable; exit 0; fi; exit 1' => `squeeze' canonical suite name for oldstable is squeeze + git init -q + git config remote.dgit.fetch '+refs/dgit/*:refs/remotes/dgit/dgit/*' + git remote add origin 'git+ssh://i...@git.debian.org/git/dgit-repos/repos/bugs-everywhere.git' | ssh 'i...@git.debian.org' ' set -e; cd /git/dgit-repos/repos; if test -d bugs-everywhere.git; then echo 1; else echo 0; fi' => `0' starting new git history | ssh 'i...@coccia.debian.org' dak ls -asource -soldstable bugs-everywhere => `bugs-everywhere | 0.0.193+bzr.r217-2 | oldstable | source' downloading http://ftp.debian.org/debian//pool/main/b/bugs-everywhere/bugs-everywhere_0.0.193+bzr.r217-2.dsc... last upload to archive has NO git hash previous reference hash= + dget -u -- 'http://ftp.debian.org/debian//pool/main/b/bugs-everywhere/bugs-everywhere_0.0.193+bzr.r217-2.dsc' dget: retrieving http://ftp.debian.org/debian//pool/main/b/bugs-everywhere/bugs-everywhere_0.0.193+bzr.r217-2.dsc % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 1378 100 13780 0 3145 0 --:--:-- --:--:-- --:--:-- 6207 dget: retrieving http://ftp.debian.org/debian//pool/main/b/bugs-everywhere/bugs-everywhere_0.0.193+bzr.r217.orig.tar.gz % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 149k 100 149k0 0 178k 0 --:--:-- --:--:-- --:--:-- 206k dget: retrieving http://ftp.debian.org/debian//pool/main/b/bugs-everywhere/bugs-everywhere_0.0.193+bzr.r217-2.diff.gz % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 9189 100 91890 0 5316 0 0:00:01 0:00:01 --:--:-- 5707 dpkg-source: info: extracting bugs-everywhere in bugs-everywhere-0.0.193+bzr.r217 dpkg-source: info: unpacking bugs-everywhere_0.0.193+bzr.r217.orig.tar.gz dpkg-source: info: applying bugs-everywhere_0.0.193+bzr.r217-2.diff.gz + git init -q + git add -Af | git write-tree => `aab8a8c25e5a018ca9cfa4109fcd19a30618ef1b' + sh -ec 'dpkg-parsechangelog >../changelog.tmp' | date '+%s %z' -d 'Fri, 24 Jul 2009 16:46:00 +1000' => `1248417960 +0100' | git hash-object -w -t commit ../commit.tmp => `9021e7997350131c39ffc8ab9b605c167356e2a8' synthesised git commit from .dsc 0.0.193+bzr.r217-2 + git update-ref -m 'dgit fetch import 0.0.193+bzr.r217-2' DGIT_ARCHIVE 9021e7997350131c39ffc8ab9b605c167356e2a8 | git log -n2 9021e7997350131c39ffc8ab9b605c167356e2a8 => `commit 9021e7997350131c39ffc8ab9b605c167356e2a8'... current hash=9021e7997350131c39ffc8ab9b605c167356e2a8 | git update-ref -m 'dgit fetch' refs/remotes/dgit/dgit/squeeze 9021e7997350131c39ffc8ab9b605c167356e2a8 => `' + git reset --hard refs/remotes/dgit/dgit/squeeze HEAD is now at 9021e79 dgit ok: ready for work in bugs-everywhere zealot:tests> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726875: [Debian-med-packaging] Bug#726875: RM: libstaden-read-dev, libstaden-read1, staden-io-lib-utils [mips sparc] -- ROM; Does not build on these architectures
Le Sun, Oct 20, 2013 at 11:02:26AM +0200, Thorsten Alteholz a écrit : > On Sun, 20 Oct 2013, Charles Plessy wrote: > >staden-io-lib failded to build on mips and sparc 70 ago. > > it also failed on hurd-i386. > > > Since then, nobody > >volunteered to solve the problem. > > Did you ask somebody for help? Anyway, did you have a closer look at > the build logs? Hi Thorsten, I indeed had a look. The problem of asking for help is that it reverses the roles. I am not the one who wants staden-io-lib be built on mips, sparc, where I think it is not useful, nor on hurd, where I think that working on such a package is totally prematurate given the state of that port. I think that te work has to be done by somebody running Debian on one of these architectures, and genuinely interested in using staden-io-lib there. Or, for me to volunteer to participate, I would like to receive at least one message from a biologist explaining why he needs the package to be built there. Otherwise, I think that it is better to simply solve the problem by removing the broken or unbuilt package from mips and sparc. I want my contributions to be useful in the daily life of people, and if possible, many of them. Of course, I will not stand on the way of people who want to do the porting work, but as I wrote at the beginning of my request for removal on mips and sparc, there has been 70 days without anybody volunteering. I hope that explains. Cheers, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#695196: Invalid workgroup
tags 695196 +moreinfo thanks You're not specifying a workgroup for the user, and the default workgroup seems to be different in the two smb.conf files: From the working smb.conf: doing parameter workgroup = MYGROUP From the broken one: doing parameter workgroup = someurl Can you try authenticating with -UMYGROUP\\backup ? signature.asc Description: Digital signature
Bug#696211: acpica-unix: Please add cross-build, hardening flags support
Package: acpica-unix Version: 20130927-1 Followup-For: Bug #696211 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch Hi Mattia, hi Al, I've forward-ported this patch to the current version of acpica-unix in unstable. Could you please consider applying it? Although the update to debhelper 9 improved the hardening flags handling, there are still a few gotchas that are addressed by this patch - in particular, the current package gets built with the dpkg-buildflags CFLAGS, but not with CPPFLAGS (so -D_FORTIFY_SOURCE=2 is missing), and the CFLAGS that are defined /in debian/rules itself/ are missing because they're never handed off to the upstream build system in the needed way. Please note that this changes the handling of the -fno-strict-aliasing flag; previously the package would apply this flag only if DEB_BUILD_OPTIONS=noopt was not set. That doesn't make sense to me, so I just changed it so the flag was always on; but if there's a reason to continue disabling this flag for noopt builds, I'm happy to rework the patch to reflect this. Updated patch is attached - thanks for considering! -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org === modified file 'debian/rules' --- debian/rules 2013-10-08 17:01:36 + +++ debian/rules 2013-10-20 20:56:03 + @@ -9,15 +9,19 @@ # Uncomment this to turn on verbose mode. export DH_VERBOSE=1 -CFLAGS = -Wall -g +CFLAGS = $(shell dpkg-buildflags --get CFLAGS) $(shell dpkg-buildflags --get CPPFLAGS) -Wall -fno-strict-aliasing + DESTDIR ?= debian/acpica-tools VERSION = 20130927 -ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) - CFLAGS += -O0 +DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) +DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) + +ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) + CC = $(DEB_HOST_GNU_TYPE)-gcc else - CFLAGS += -O2 -fno-strict-aliasing + CC = gcc endif @@ -64,4 +68,9 @@ $(DESTDIR)/usr/share/man/man1/acpixtract-acpica.1 override_dh_auto_test: - $(MAKE) -C $(CURDIR) check +ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) + $(MAKE) -C $(CURDIR) check CC=$(CC) OPT_CFLAGS="$(CFLAGS)" +endif + +override_dh_auto_build: + dh_auto_build -- OPT_CFLAGS="$(CFLAGS)" CC=$(CC)
Bug#726954: [winff] Unknown encoder 'libvo_aacenc'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: winff Version: 1.5.1-1 Severity: normal - --- Please enter the report below this line. --- I am trying to convert one mpg video to another format (package "libvo-aacenc0" is installed on my system): avconv version 9.10-6:9.10-1, Copyright (c) 2000-2013 the Libav developers built on Oct 11 2013 15:40:54 with gcc 4.8 (Debian 4.8.1-10) [mp1 @ 0x26600e0] Header missing [mpeg2video @ 0x26400e0] mpeg_decode_postinit() failure [mpegts @ 0x263ad40] Invalid timestamps stream=0, pts=1054800, dts=8423999087, size=19301 [mpeg2video @ 0x26400e0] mpeg_decode_postinit() failure Last message repeated 1 times [mpegts @ 0x263ad40] max_analyze_duration reached [mpegts @ 0x263ad40] PES packet size mismatch Last message repeated 1 times Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, mpegts, from '/tmp/ORF1_04_27_2013_20_28_33.mpg': Duration: 26:28:05.30, start: 11.084667, bitrate: 92 kb/s Program 10101 Stream #0.0[0x3f2]: Video: mpeg2video, 0k fps, 25 tbr, 90k tbn Stream #0.1[0x3f3](ger): Audio: mp2, 48000 Hz, stereo, s16p, 160 kb/s (clean effects) Stream #0.2[0x3f5](ger): Audio: ac3, 48000 Hz, 5.1, fltp, 448 kb/s (clean effects) Stream #0.3[0x3f7](ger): Subtitle: [6][0][0][0] / 0x0006 Stream #0.4[0x3f6]: Audio: mp1, 0 channels, s16p Unknown encoder 'libvo_aacenc' - --- System information. --- Architecture: amd64 Kernel: Linux 3.10-3-amd64 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.20 (GNU/Linux) iEYEARECAAYFAlJkU34ACgkQ6aU4/+gLeBlV4QCgmbFFE+/TaB7oILeJIDuE+Qve HRkAnite7+mvKjeYrzsfBzzU8U5Z8oEs =aWFR -END PGP SIGNATURE-
Bug#726953: dgit fails with submodules
Package: dgit Version: 0.15 Severity: normal This one is a little hairy, but regardless... anarcat@marcos:bugs-everywhere$ dgit -n push --new -D DRY RUN ONLY + git diff --quiet HEAD | ssh coccia.debian.org 'set -e; cd /srv/ftp-master.debian.org/ftp/dists; if test -h experimental; then readlink experimental; exit 0; fi; if test -d experimental; then echo experimental; exit 0; fi; exit 1' => `experimental' | ssh git.debian.org ' set -e; cd /git/dgit-repos/repos; if test -d bugs-everywhere.git; then echo 1; else echo 0; fi' => `0' | ssh coccia.debian.org dak ls -asource -sexperimental bugs-everywhere => `' no version available from the archive previous reference hash= nothing found! actually entering push format 1.0 + git diff --quiet HEAD checking that bugs-everywhere_1.1.1-1.0.dsc corresponds to HEAD + dpkg-source -x -- ../../../../bugs-everywhere_1.1.1-1.0.dsc dpkg-source: avertissement: extraction d'un paquet source non signé (../../../../bugs-everywhere_1.1.1-1.0.dsc) dpkg-source: info: extraction de bugs-everywhere dans bugs-everywhere-1.1.1 dpkg-source: info: extraction de bugs-everywhere_1.1.1.orig.tar.gz dpkg-source: info: mise en place de bugs-everywhere_1.1.1-1.0.diff.gz dpkg-source: info: fichiers amont modifiés : bugs-everywhere-1.1.1/Makefile bugs-everywhere-1.1.1/libbe/_version.py + git init -q + git add -Af | git write-tree => `eb1d29cbe83eed3e3be96f52cb166c53da9ae871' + diff --git a/update-copyright b/update-copyright new file mode 16 index 000..f5629da --- /dev/null +++ b/update-copyright @@ -0,0 +1 @@ +Subproject commit f5629da9158f7f3467d986d51bd1f6ed2204da3a git: failed command: git diff --exit-code eb1d29cbe83eed3e3be96f52cb166c53da9ae871 dgit: subprocess failed with error exit status 1 I will try to push this git repo online once I have the benediction of the current maintainer, for further testing. -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717557: gcc-4.8: can't compile working 64bit kernel with 32bit userspace gcc-4.8
On Sun, 2013-10-20 at 23:44 +0200, Matthias Klose wrote: > Am 20.10.2013 22:58, schrieb Ben Hutchings: > > On Sun, 2013-10-20 at 22:21 +0200, Matthias Klose wrote: > >> Am 20.10.2013 00:25, schrieb Ben Hutchings: > >>> On Sat, 2013-10-19 at 23:38 +0200, Matthias Klose wrote: > Control: severity -1 important Control: tags -1 + moreinfo > > >> In file included from :0:0: > >> /usr/include/stdc-predef.h:30:26: fatal error: bits/predefs.h: > >> No such file > > or directory > >> #include ^ > > compilation terminated. > > > > It looks like I can avoid this by changing the compile tests to > > use the -nostdinc option. But this change may possibly cause > > other problems, and neither the pre-included header nor the fact > > that -nostdinc disables it seem to be documented. > > please attach the test program and the command line options used for > this test case. I think the issue is within the kernel build system > not being prepared for multiarch and -nostdinc. > >>> > >>> gcc-4.8 -m64 -x c -c /dev/null > >> > >> works for me on a current sid/i386. I assume that gcc-4.8-multilib is > >> installed? > > > > No, it works if that's installed. But gcc-X.Y-multilib was previously only > > needed for building with a 64-bit C library, not for building a 64-bit > > kernel. > > > > If this kernel configuration was actually failing to build without > > gcc-4.8-multilib, I wouldn't mind so much. The problem is that it's built > > wrongly now. Maybe some later version of the kernel will be changed to > > detect or work around this problem, but we have to assume people will still > > try to build older versions not using -nostdinc for some time to come. > > Is this due to the missing /usr/include/asm symlink shipped in gcc-multilib? > It's not ideal, and I think I did file a bug report that this should be > shipped in one of the glibc packages, but can't find it anymore. The /usr/include/bits symlink in libc6-dev-amd64 is what makes this work again (which is disgusting, really...). Without that, stdc-predef.h can be found but not bits/predefs.h. > > The options to deal with this include: 1. Make missing headers non-fatal > > while pre-including . > > that would be the responsibility of those packages using non-standard options > like -nostdinc. Well the problem occurs because Linux uses -nostdinc only in the real compiles (so they succeed) but not the test compiles (so they fail). > > 2. Disable pre-inclusion of . > > no, done upstream to conform to standards. > > > 3. Make 32-bit gcc fail to compile anything with -m64 if gcc-X.Y-multilib > > is not installed, even if -nostdinc is used. > > welcome to multiarch, and thanks for upstreaming patches to fix these issues. > > > 4. Make gcc-X.Y depend on gcc-X.Y-multilib on architectures where it > > exists. > > well, then you can merge these again. the whole point to have them separate > were bug reports about being forced to install the non-defaults multilibs by > default. Indeed, I didn't say any of those options were good. > 5. Install the whole glibc headers into the multiarch header path. Would fix > some other things too, like allowing multiarch configurations for non-glibc > based triplets. And I assume it would allow your build to fail. I don't think this would help. Ben. -- Ben Hutchings Tomorrow will be cancelled due to lack of interest. signature.asc Description: This is a digitally signed message part
Bug#724576: libgl1-mesa-glx: libGL error: failed to load driver: nouveau
Btw, Sven, >> That might be http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722930. >> Have you looked at that bug yet? > > Could be the same bug. At least > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722930#15 this is the > same error. I do not think that Thomas' problem is related to the bug report you are mentioning here. The problem Thomas (and I) see is that Mesa is unable to load the DRI module for nouveau even though the module is actually present. I might just try rebuilding Mesa locally and see if that fixes the problem. I'm not sure why Mesa can't load the DRI module as even with debug enabled, I don't see any error message reasoning why the module couldn't be loaded. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726952: rev(1): Macro '.El' is missing in the manual
Package: util-linux Version: 2.20.1-5.3 Severity: minor Tags: patch Dear Maintainer, From "groff -b -ww -mandoc -z": mdoc warning: A .Bl directive has no matching .El (#58) Inputfile is /usr/share/man/man1/rev.1.gz Debian bug #397226 has already been fixed. Changes (besides the warning): A full stop (.) at the beginning or start of a string and is a part of it, protected with \& Patch: --- rev.1 2013-10-20 20:45:01.0 + +++ rev.1.new 2013-10-20 20:48:23.0 + @@ -43,7 +43,7 @@ .Nm rev .Op Fl V .Op Fl h -.Op Ar file ... +.Op Ar file \&...\& .Sh DESCRIPTION The .Nm rev @@ -55,6 +55,7 @@ If no files are specified, standard inpu Output version information and exit. .It Fl h, Fl Fl help Output help and exit. +.El .Sh AVAILABILITY The rev command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/. -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i586) Kernel: Linux 3.2.46-1-rt67-1 Locale: LANG=is_IS, LC_CTYPE=is_IS (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages util-linux depends on: ii debconf [debconf-2.0] 1.5.49 ii dpkg 1.16.10 ii initscripts2.88dsf-41+deb7u1 ii install-info 4.13a.dfsg.1-10 ii libblkid1 2.20.1-5.3 ii libc6 2.13-38 ii libncurses55.9-10 ii libselinux12.1.9-5 ii libslang2 2.2.4-15 ii libtinfo5 5.9-10 ii libuuid1 2.20.1-5.3 ii lsb-base 4.1+Debian8+deb7u1 ii tzdata 2013c-0wheezy1 ii zlib1g 1:1.2.7.dfsg-13 util-linux recommends no packages. Versions of packages util-linux suggests: pn dosfstools ii kbd 1.15.3-9 pn util-linux-locales -- Configuration Files: /etc/default/hwclock changed [not included] /etc/init.d/hwclock.sh changed [not included] -- debconf information: util-linux/noauto-with-nonzero-passnum: -- Bjarni I. Gixslason -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724576: libgl1-mesa-glx: libGL error: failed to load driver: nouveau
Hi Thomas! > error: XDG_RUNTIME_DIR not set in the environment. > libGL error: failed to load driver: nouveau > libGL error: Try again with LIBGL_DEBUG=verbose for more details. > error: XDG_RUNTIME_DIR not set in the environment. > Versions of packages xserver-xorg recommends: > ii libgl1-mesa-dri 9.2-1 I am seeing the exact same issue on an Apple PowerMac G5 (A1047) with has a GeForce FX 5200 Ultra (NV34) video adpater. This problem was present only with the Mesa DRI version from experimental (9.2.1-1). Downgrading just the DRI package libgl1-mesa-dri from 9.2.1-1 to 9.1.7-1 resolved the issue for me. I'm attaching the output of glxinfo for both versions of libgl1-mesa-dri with LIBGL_DEBUG=verbose set if that's of any help for the mesa maintainers. I have also reported this issue upstream [1], even though I don't think this is an upstream issue but with the particular Debian package. Maybe rebuilding fixes the issue? Could you try downgrading just this package and report back? Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/nouveau_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/nouveau_dri.so libGL: Can't open configuration file /home/glaubitz/.drirc: No such file or directory. libGL: Can't open configuration file /home/glaubitz/.drirc: No such file or directory. libGL: Can't open configuration file /home/glaubitz/.drirc: No such file or directory. name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync OpenGL vendor string: nouveau OpenGL renderer string: Gallium 0.4 on NV34 OpenGL version string: 1.5 Mesa 9.1.7 OpenGL extensions: GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_elements_base_vertex, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_get_program_binary, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_shader_objects, GL_ARB_shading_language_100, GL_ARB_shadow, GL_ARB_sync, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_tex
Bug#717557: gcc-4.8: can't compile working 64bit kernel with 32bit userspace gcc-4.8
Am 20.10.2013 22:58, schrieb Ben Hutchings: > On Sun, 2013-10-20 at 22:21 +0200, Matthias Klose wrote: >> Am 20.10.2013 00:25, schrieb Ben Hutchings: >>> On Sat, 2013-10-19 at 23:38 +0200, Matthias Klose wrote: Control: severity -1 important Control: tags -1 + moreinfo >> In file included from :0:0: >> /usr/include/stdc-predef.h:30:26: fatal error: bits/predefs.h: >> No such file > or directory >> #include ^ > compilation terminated. > > It looks like I can avoid this by changing the compile tests to > use the -nostdinc option. But this change may possibly cause > other problems, and neither the pre-included header nor the fact > that -nostdinc disables it seem to be documented. please attach the test program and the command line options used for this test case. I think the issue is within the kernel build system not being prepared for multiarch and -nostdinc. >>> >>> gcc-4.8 -m64 -x c -c /dev/null >> >> works for me on a current sid/i386. I assume that gcc-4.8-multilib is >> installed? > > No, it works if that's installed. But gcc-X.Y-multilib was previously only > needed for building with a 64-bit C library, not for building a 64-bit > kernel. > > If this kernel configuration was actually failing to build without > gcc-4.8-multilib, I wouldn't mind so much. The problem is that it's built > wrongly now. Maybe some later version of the kernel will be changed to > detect or work around this problem, but we have to assume people will still > try to build older versions not using -nostdinc for some time to come. Is this due to the missing /usr/include/asm symlink shipped in gcc-multilib? It's not ideal, and I think I did file a bug report that this should be shipped in one of the glibc packages, but can't find it anymore. > The options to deal with this include: 1. Make missing headers non-fatal > while pre-including . that would be the responsibility of those packages using non-standard options like -nostdinc. > 2. Disable pre-inclusion of . no, done upstream to conform to standards. > 3. Make 32-bit gcc fail to compile anything with -m64 if gcc-X.Y-multilib > is not installed, even if -nostdinc is used. welcome to multiarch, and thanks for upstreaming patches to fix these issues. > 4. Make gcc-X.Y depend on gcc-X.Y-multilib on architectures where it > exists. well, then you can merge these again. the whole point to have them separate were bug reports about being forced to install the non-defaults multilibs by default. 5. Install the whole glibc headers into the multiarch header path. Would fix some other things too, like allowing multiarch configurations for non-glibc based triplets. And I assume it would allow your build to fail. Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726151:
Just upgraded the kernel and the same exact thing is still there for kernel 3.11! signature.asc Description: This is a digitally signed message part
Bug#726891: Closing laptop lid when set to do nothing
Control: tag -1 moreinfo On Sun, 2013-10-20 at 12:26 +0200, Patrik Nilsson wrote: > package: Linux > > I have set actions on laptop close to be nothing, both on battery and > AC. Often the computer puts itself into sleep mode and wakes up again > when I open the lid. > > This is very annoying since I always run a shutdown script, which > backups up data, and then shutdowns down the computer. > > It is also a possible security issue, since my LUKS password to my > harddisk is saved into ram. The kernel doesn't choose this, it's up to acpi-support and whatever hooks into that (e.g. upower). If you tell us what desktop environment you're using then maybe this can be reassigned accordingly. Ben, -- Ben Hutchings Tomorrow will be cancelled due to lack of interest. signature.asc Description: This is a digitally signed message part
Bug#694744: working on the bugs-everywhere package
I started looking into this. The package seems to build fine in sid now that numpydoc has kicked in. One thing I had trouble with was to make the build system work without git, because the upstream makefiles assume that git is available to generate metadata about the repository. I had to go through all sorts of stupid hoops to make that work properly with git-buildpackage. Otherwise I would be ready to make an upload to experimental. Ben, are you still interested in maintaining this package? Can I make a tentative upload to experimental? Thanks, A. -- Nothing incites to money-crimes like great poverty or great wealth. - Mark Twain signature.asc Description: Digital signature
Bug#651965: xserver-xorg-video-nouveau: corrupt glyphs and icons in gnome-shell on NV34 [GeForce FX 5200]
Hi Daniel! > I'm seeing corrupted text glyphs and icons in the latest gnome-shell > (from either unstable or experimental). I believe it's a problem with > the nouveau driver (maybe specific to this particular model of card?) I have been playing around with an old PowerMac G5 which I borrowed as a PPC porterbox and it happens to have this particular video adapter as well. Initially, I installed Debian Wheezy onto the Mac and ran into many rendering issues with nouveau and gnome-shell and the latter happened to crash very often. However, upgrading everything to unstable resolved both the rendering issues as well as the gnome-shell crashes. I think Mesa upstream fixed many nouveau issues in the newer Mesa releases, so you should definitely give that a try in case you still have this machine around, so we might be able to close this bug ;). Additionally, it would be interesting to know whether 3D hardware acceleration works on your laptop after upgrading to the Mesa version in experimental (9.2.1-1). I figured out that after upgrading to 9.2.1-1, Mesa could no longer load the nouveau_dri.so module which I could resolve by downgrading libgl1-mesa-dri to 9.1.7-1 again (I didn't have to downgrade the rest of Mesa). Cheers across the big lake ;) Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726671: A stack trace
Hey guys! I installed the debugging symbols and I am providing a stack trace attached. The problem is still there and is reproducible as ever. Starting program: /usr/bin/gnome-shell --replace warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe3b91700 (LWP 10511)] [New Thread 0x7fffe1c1d700 (LWP 10533)] [New Thread 0x7fffe1215700 (LWP 10534)] [New Thread 0x7fffe0a14700 (LWP 10537)] [New Thread 0x7fffcf2ff700 (LWP 10542)] [New Thread 0x7fffcd4ff700 (LWP 10561)] [New Thread 0x7fffa1262700 (LWP 10562)] [New Thread 0x7fffa0a61700 (LWP 10563)] [New Thread 0x7fff9bfff700 (LWP 10564)] [New Thread 0x7fff9b7fe700 (LWP 10565)] [Thread 0x7fff9bfff700 (LWP 10564) exited] [Thread 0x7fffa0a61700 (LWP 10563) exited] [Thread 0x7fffa1262700 (LWP 10562) exited] [Thread 0x7fffcd4ff700 (LWP 10561) exited] [Thread 0x7fffcf2ff700 (LWP 10542) exited] [New Thread 0x7fffcf2ff700 (LWP 10704)] [New Thread 0x7fffcd4ff700 (LWP 10705)] [New Thread 0x7fffa1262700 (LWP 10706)] [Thread 0x7fffcf2ff700 (LWP 10704) exited] [Thread 0x7fffcd4ff700 (LWP 10705) exited] [Thread 0x7fffa1262700 (LWP 10706) exited] [New Thread 0x7fffa1262700 (LWP 10707)] [New Thread 0x7fffcd4ff700 (LWP 10708)] [New Thread 0x7fffcf2ff700 (LWP 10709)] [New Thread 0x7fffa0a61700 (LWP 10710)] [New Thread 0x7fffa5af8700 (LWP 10711)] [New Thread 0x7fffa52f7700 (LWP 10712)] [New Thread 0x7fffa4af6700 (LWP 10713)] Program received signal SIGSEGV, Segmentation fault. magazine_chain_pop_head (magazine_chunks=0x609660) at /tmp/buildd/glib2.0-2.36.4/./glib/gslice.c:532 532 /tmp/buildd/glib2.0-2.36.4/./glib/gslice.c: No such file or directory. Thread 21 (Thread 0x7fffa4af6700 (LWP 10713)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7fffeeafd5f5 in g_cond_wait_until (cond=cond@entry=0x1bd9cf8, mutex=mutex@entry=0x1bd9cf0, end_time=end_time@entry=4022145021) at /tmp/buildd/glib2.0-2.36.4/./glib/gthread-posix.c:865 #2 0x7fffeea94941 in g_async_queue_pop_intern_unlocked (queue=0x1bd9cf0, wait=wait@entry=1, end_time=4022145021) at /tmp/buildd/glib2.0-2.36.4/./glib/gasyncqueue.c:424 #3 0x7fffeea94f08 in g_async_queue_timeout_pop_unlocked (queue=, timeout=timeout@entry=50) at /tmp/buildd/glib2.0-2.36.4/./glib/gasyncqueue.c:572 #4 0x7fffeeae2b68 in g_thread_pool_wait_for_new_task (pool=0x1bd9c90) at /tmp/buildd/glib2.0-2.36.4/./glib/gthreadpool.c:264 #5 g_thread_pool_thread_proxy (data=) at /tmp/buildd/glib2.0-2.36.4/./glib/gthreadpool.c:298 #6 0x7fffeeae21d5 in g_thread_proxy (data=0x32818a0) at /tmp/buildd/glib2.0-2.36.4/./glib/gthread.c:798 #7 0x7fffee861e0e in start_thread (arg=0x7fffa4af6700) at pthread_create.c:311 #8 0x7fffee5969ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 20 (Thread 0x7fffa52f7700 (LWP 10712)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7fffeeafd5f5 in g_cond_wait_until (cond=cond@entry=0x1bd9cf8, mutex=mutex@entry=0x1bd9cf0, end_time=end_time@entry=4022150277) at /tmp/buildd/glib2.0-2.36.4/./glib/gthread-posix.c:865 #2 0x7fffeea94941 in g_async_queue_pop_intern_unlocked (queue=0x1bd9cf0, wait=wait@entry=1, end_time=4022150277) at /tmp/buildd/glib2.0-2.36.4/./glib/gasyncqueue.c:424 #3 0x7fffeea94f08 in g_async_queue_timeout_pop_unlocked (queue=, timeout=timeout@entry=50) at /tmp/buildd/glib2.0-2.36.4/./glib/gasyncqueue.c:572 #4 0x7fffeeae2b68 in g_thread_pool_wait_for_new_task (pool=0x1bd9c90) at /tmp/buildd/glib2.0-2.36.4/./glib/gthreadpool.c:264 #5 g_thread_pool_thread_proxy (data=) at /tmp/buildd/glib2.0-2.36.4/./glib/gthreadpool.c:298 #6 0x7fffeeae21d5 in g_thread_proxy (data=0x7fff94007a30) at /tmp/buildd/glib2.0-2.36.4/./glib/gthread.c:798 #7 0x7fffee861e0e in start_thread (arg=0x7fffa52f7700) at pthread_create.c:311 #8 0x7fffee5969ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 19 (Thread 0x7fffa5af8700 (LWP 10711)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7fffeeafd5f5 in g_cond_wait_until (cond=cond@entry=0x1bd9cf8, mutex=mutex@entry=0x1bd9cf0, end_time=end_time@entry=4022147494) at /tmp/buildd/glib2.0-2.36.4/./glib/gthread-posix.c:865 #2 0x7fffeea94941 in g_async_queue_pop_intern_unlocked (queue=0x1bd9cf0, wait=wait@entry=1, end_time=4022147494) at /tmp/buildd/glib2.0-2.36.4/./glib/gasyncqueue.c:424 #3 0x7fffeea94f08 in g_async_queue_timeout_pop_unlocked (queue=, timeout=timeout@entry=50) at /tmp/buildd/glib2.0-2.36.4/./glib/gasyncqueue.c:572 #4 0x7fffeeae2b68 in g_thread_pool_wait_for_new_task (pool=0x1bd9c90) at /tmp/buildd/glib2.0
Bug#726912: libsdl-mixer1.2: Music with TiMidity backend plays too fast
2013/10/20 Sylvain : > Hi, > > On Sun, Oct 20, 2013 at 06:10:24PM +0100, Manuel A. Fernandez Montecelo wrote: >> It would be great if you could recompile the deb package with that >> patch disabled and test it if plays the file, and other files of >> freedink, and see if it doesn't segfault (some modification of the >> current patch would be needed, I guess, that's why the patch was >> devised in the first place). > > As I'm such a great guy I ran a few tests ;) Thanks :-) > SDL_FORCE_SOUNDFONTS=1 ./playmus /usr/share/games/dink/dink/Sound/104.mid > SDL_FORCE_SOUNDFONTS=1 ./playmus /tmp/midibug/sound/10.mid > > > Results: > > upstream + bare ./configure > - 104.mid: OK > - minibug: OK > > upstream + bare ./configure + bug-694260-freedink_stack_corruption.patch: > - 104.mid: faster tempo > - minibug: slower tempo > > current debian: > - 104.mid: faster tempo > - minibug: still crashes! #694260 ain't fixed! > > current debian - all patches: > - 104.mid: OK > - minibug: still crashes! > > current debian - all patches - -fstatck-protector: > - 104.mid: OK > - minibug: OK > > Conclusions: > - bug-694260-freedink_stack_corruption.patch doesn't fix the crash > - bug-694260-freedink_stack_corruption.patch introduces a new bug > Sorry pals :) I'm having a bit of a problem with the terminology so I cannot make sense of the cases that you explain: - Does "current debian - all patches" mean "minus all patches, that is, no patches applied", or "current debian, with all patches applied"? - "current debian" means as the binary package, "all patches included", or "current version of the code as shipped in .orig.tar, but no patches"? - and more importantly, upstream is the same version as Debian's .orig.tar, that is 1.2.12, or the HEAD, or something else? Upstream created the patch later than 1.2.12 and I think that it's carried in 2.0.0, so it's important to ask the patch to be reverted if it's wrong. According to your cases above, if "upstream" works without the patch but not with the patch applied, it means that you are using either 1.2.12, or later but they already reverted the patch. Cheers. -- Manuel A. Fernandez Montecelo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699879: Info received ([Pkg-fglrx-devel] Bug#699879: fglrx-driver: Xorg doesn't start after aticonfig --px-igpu)
Same problem running "update-alternatives --set glx /usr/lib/mesa-diverted". Symlinks are deleted and xorg is not changed, so X fails to start when using the power saving option. On Tue, Oct 15, 2013 at 6:15 PM, Debian Bug Tracking System wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Fglrx packaging team > > If you wish to submit further information on this problem, please > send it to 699...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 699879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699879 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726950: RFS: pidgin-privacy-please/0.7.1-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pidgin-privacy-please" * Package name: pidgin-privacy-please Version : 0.7.1-2 Upstream Author : Stefan Ott * URL : http://code.google.com/p/pidgin-privacy-please/ * License : GNU GPL Section : net It builds those binary packages: pidgin-privacy-please - plugin for enhanced privacy in pidgin To access further information about this package, please visit the following URL: http://mentors.debian.net/package/pidgin-privacy-please Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/pidgin-privacy-please /pidgin-privacy-please_0.7.1-2.dsc Changes since the last upload: * debian/control: - Bumped standards version to 3.9.4 - Use canonical URIs for Vcs-* fields - Build-dep on autotools-dev to have the autotools helper files updated * Use debhelper 9 to get the correct CFLAGS -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (650, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726913: r-base-dev: does not use the dpkg-buildflags options for gfortran, specifically LDFLAGS
On Sun, Oct 20, 2013 at 12:34:04PM -0500, Dirk Eddelbuettel wrote: > | Ah, I'm guessing it comes from /usr/lib/R/etc/Makeconf (I straced R > | CMD config LDFLAGS). That seems to be created at R build time, so I > | wonder whether simply tweaking that would do the trick? > > Good thinking -- yes it would. We code'em down in debian/rules for > configure, they then tend to get passed through. > > That would probably be worth it! (And in case you look at the debian/rules > for r-base, it is a bit of a mess that grew over ten+ years -- not proud of > it but heck it works :) > > | I've just had a look at the debian/rules file for r-base. At present, > | optimflags seems to be derived from a hand-written set of rules. > | Could it be replaced by something vaguely like the following: > | > | optimflags = $(shell dpkg-buildflags --get CFLAGS) > | ldflags = $(shell dpkg-buildflags --get LDFLAGS) > > Very nice. I was fully unaware of that option to dpkg-buildflags. I was unaware of the script in its entirety until today ;-) > | etc., and the same for CPPFLAGS, CXXFLAGS, FFLAGS, and then set these > | environment variables when you run configure, instead of setting > | LDFLAGS to be empty? I could write a whole patch if you wish, but > | only if you would like me to. > > I'd appreciate it if you took a stab at it. There is a ton of special casing > in there. Would we need a ton of post-processing with sed to account for > that? I;d hesitate to just say 'hell with it', breaking everything and > trying to put it back together on arch at a time. > > But yes, the added flags should probably be going in there... OK, attached is a suggested patch. It seems to work for me. There are some of the parts where I've added other flags in addition to the ones that were already there - I don't know if this is necessary or not. Also, the definition of fflags is currently broken, as noted in the patch, as there is a bug in dpkg-dev (which I've just reported) - it should be fixed pretty soon. I've left all of the old code in the file, clearly commented out. It might be worth removing it entirely, or perhaps not. Also, I noticed that there is an old rules,v file in the debian/ directory, which made it slightly hard to edit the rules file. I don't know how you're currently doing your version tracking, but if it's no longer with RCS, you may wish to delete this file! HTH! Julian --- rules.old 2013-10-20 19:06:09.0 +0100 +++ rules 2013-10-20 19:29:26.938407738 +0100 @@ -77,86 +77,97 @@ f95compiler = gfortran compiler = "gcc -std=gnu99" cxxcompiler = g++ -optimflags = -O3 -pipe -# edd 22 Apr 2012 gcc-4.7 needs -O2 to build R (also #67359) -ifneq "$(shell gcc --version | head -1 | cut -d' ' -f4 | grep '^4.7')" "" -optimflags = -O2 -pipe -endif - -# edd 04 Sep 2001 default compiler flags, lowered for m68k -#compilerflags = -O2 -# m68k barks when using g77, and when gcc use -O2 -# edd 26 Nov 2002 switched back to g77 -# edd 02 Jun 2003 switched back -# cts 04 Jun 2003 use -O1 on m68k -#ifeq ($(arch),m68k) -#fortrancompiler = F2C=f2c -#compilerflags = -O1 -#endif - -# edd 14 Nov 2003 turn blas off on arm -# edd 12 May 2010 no longer needed -- thx to Modestas Vainius -#ifeq ($(arch),arm) -#atlas = --without-blas -#endif - -## edd 09 Nov 2001 ia64 needs gcc-3.0, hppa gets it by default -#ifeq ($(arch),ia64) -#fortrancompiler = F77=g77-3.0 -#compiler = gcc-3.0 -#cxxcompiler = g++-3.0 -#compilerflags = -O2 -#endif - -## lam...@debian.org 06 Dec 2001 hppa needs -ffunction-sections -ifeq ($(arch),hppa) -optimflags = -O2 -ffunction-sections -endif - -## edd 20 Jun 2002 no optimisation or debugging on baby systems -## edd 02 Jun 2003 use this on arm only -## edd 12 May 2010 no longer use it on arm either -- thx Modestas -## edd 04 Aug 2010 on mips and mipsel, don't use -g -##ifneq "$(findstring $(arch), m68k arm)" "" -#ifneq "$(findstring $(arch), arm)" "" -ifneq "$(findstring $(arch), mips mipsel)" "" -optimflags = -g0 -#optimflags = -O0 -g0 -endif - -## edd 04 Apr 2009 Alpha dies on deriv.c, trying will less optimisation -## edd 16 Apr 2009 commented-out as Kurt Roeckx applied a gcc patch -#ifeq ($(arch),alpha) -#optimflags = -O2 -g0 -#endif - -## edd 09 Apr 2006 per patch from Andreas Jochens in #361604 -ifeq ($(arch),powerpc64) -optimflags += -mminimal-toc -endif - -## edd 26 Jul 2013 kFreeBSD wants -O2 per #714506 -ifeq ($(buildos),kfreebsd) -optimflags = -O2 -pipe -endif - - -## edd 04 Apr 2006 generalize from old compilerflags to per-compiler -## edd 11 Oct 2011 -std=gnu goes to CC (thanks to Kurt Hornik) -cflags = $(optimflags) -cxxflags = $(optimflags) -fcflags = $(optimflags) - -## edd 17 Sep 2006 suggested by Brian Ripley in email dated 15 Sep 2006 -#ldflags = -Wl,-O1,-Bdirect,--hash-style=both -ldflags = -Wl,-O1 -## edd 06 May 2007 try it -## edd 05 Feb 2008 still no go under gcc 4.3 -#ldflags = -Wl,-O1,-Bdirect,--hash-style=both - -## edd 16 Apr 2008 add -g
Bug#726949: ruby-gettext: rxgettext should split messages at newline characters
Package: ruby-gettext Version: 3.0.2-2 Severity: wishlist Hello once again! ;-) I prepared a small revision of my test case, in order to show another thing that I noticed about rxgettext: $ cat myapplication.rb #!/usr/bin/ruby # Copyright (C) 2012-2013 Francesco Poli # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License with # the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL; # if not, write to the Free Software Foundation, Inc., 59 Temple Place, # Suite 330, Boston, MA 02111-1307 USA require 'gettext' include GetText GetText::bindtextdomain("myapplication") count = 0 print _("Hello everybody!\n") count += 1 print _("You are running an internationalized Ruby program.\n") count += 1 # TRANSLATORS: %d is the number of already printed messages print _("You have already seen %d translatable messages.\n") % count print _("Is this message # 3 or # 4 ?\nDoes it matter?\n") print _("OK, I am tired...\n") print _("Goodbye!\n") Let's use xgettext in order to generate the corresponding .pot file: $ xgettext --add-comments=TRANSLATORS --no-wrap \ --copyright-holder="Francesco Poli" \ --package-name=myapplication --package-version=0.2 \ --msgid-bugs-address="addr...@example.com" \ --language=python \ myapplication.rb -o myapplication_XGETTEXT.pot $ cat myapplication_XGETTEXT.pot # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR Francesco Poli # This file is distributed under the same license as the PACKAGE package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: myapplication 0.2\n" "Report-Msgid-Bugs-To: addr...@example.com\n" "POT-Creation-Date: 2013-10-20 22:49+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: 8bit\n" #: myapplication.rb:24 msgid "Hello everybody!\n" msgstr "" #: myapplication.rb:27 msgid "You are running an internationalized Ruby program.\n" msgstr "" #. TRANSLATORS: %d is the number of already printed messages #: myapplication.rb:31 #, python-format msgid "You have already seen %d translatable messages.\n" msgstr "" #: myapplication.rb:33 msgid "" "Is this message # 3 or # 4 ?\n" "Does it matter?\n" msgstr "" #: myapplication.rb:35 msgid "OK, I am tired...\n" msgstr "" #: myapplication.rb:37 msgid "Goodbye!\n" msgstr "" As you can see the message at line 33 is split up into two strings for easier reading by translators. This is done since the message is actually intended to be printed onto two separate lines; so it makes sense that the translator has the opportunity to see it formatted in a way closer to how the program user will see it. Unfortunately, rxgettext does not do the same: $ rxgettext --add-comments=TRANSLATORS --no-wrap \ --copyright-holder="Francesco Poli" \ --package-name=myapplication --package-version=0.2 \ --msgid-bugs-address="addr...@example.com" \ myapplication.rb -o myapplication_RXGETTEXT.pot $ cat myapplication_RXGETTEXT.pot # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR Francesco Poli # This file is distributed under the same license as the myapplication package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: myapplication 0.2\n" "Report-Msgid-Bugs-To: addr...@example.com\n" "POT-Creation-Date: 2013-10-20 23:01+0200\n" "PO-Revision-Date: 2013-10-20 23:01+0200\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n" #: myapplication.rb:24 msgid "Hello everybody!\n" msgstr "" #: myapplication.rb:27 msgid "You are running an internationalized Ruby program.\n" msgstr "" #. TRANSLATORS: %d is the number of already printed messages #: myapplication.rb:31 msgid "You have already seen %d translatable messages.\n" msgstr "" #: myapplication.rb:33 msgid "Is this message # 3 or # 4 ?\nDoes it matter?\n" msgstr "" #: myapplication.rb:35 msgid "OK, I am tire
Bug#726948: libmath-bigint-perl: uninstallable in sid - obsoleted by perl 5.18
Package: libmath-bigint-perl Version: 1.997-1 Severity: serious Tags: sid User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: perl-modules (5.18.1-4): Breaks: libmath-bigint-perl (< 1.9991) Cheers, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726938: Vcs-* repositories are missing
package bugs-everywhere tags 726938 + wontfix thanks On 20-Oct-2013, Antoine Beaupré wrote: > According to: > > http://packages.qa.debian.org/b/bugs-everywhere.html > > the package sources should be available Also at that same page you can see that the package is no longer part of any Debian under development; the package was removed over a year ago. The VCS repositories were removed accordingly. -- \ “It's a terrible paradox that most charities are driven by | `\ religious belief.… if you think altruism without Jesus is not | _o__) altruism, then you're a dick.” —Tim Minchin, 2010-11-28 | Ben Finney signature.asc Description: Digital signature
Bug#717557: gcc-4.8: can't compile working 64bit kernel with 32bit userspace gcc-4.8
On Sun, 2013-10-20 at 22:21 +0200, Matthias Klose wrote: > Am 20.10.2013 00:25, schrieb Ben Hutchings: > > On Sat, 2013-10-19 at 23:38 +0200, Matthias Klose wrote: > >> Control: severity -1 important Control: tags -1 + moreinfo > >> > In file included from :0:0: > /usr/include/stdc-predef.h:30:26: fatal error: bits/predefs.h: No > such file > >>> or directory > #include ^ > >>> compilation terminated. > >>> > >>> It looks like I can avoid this by changing the compile tests to use > >>> the -nostdinc option. But this change may possibly cause other > >>> problems, and neither the pre-included header nor the fact that > >>> -nostdinc disables it seem to be documented. > >> > >> please attach the test program and the command line options used for this > >> test case. I think the issue is within the kernel build system not being > >> prepared for multiarch and -nostdinc. > > > > gcc-4.8 -m64 -x c -c /dev/null > > works for me on a current sid/i386. I assume that gcc-4.8-multilib is > installed? No, it works if that's installed. But gcc-X.Y-multilib was previously only needed for building with a 64-bit C library, not for building a 64-bit kernel. If this kernel configuration was actually failing to build without gcc-4.8-multilib, I wouldn't mind so much. The problem is that it's built wrongly now. Maybe some later version of the kernel will be changed to detect or work around this problem, but we have to assume people will still try to build older versions not using -nostdinc for some time to come. The options to deal with this include: 1. Make missing headers non-fatal while pre-including . 2. Disable pre-inclusion of . 3. Make 32-bit gcc fail to compile anything with -m64 if gcc-X.Y-multilib is not installed, even if -nostdinc is used. 4. Make gcc-X.Y depend on gcc-X.Y-multilib on architectures where it exists. Ben. -- Ben Hutchings Tomorrow will be cancelled due to lack of interest. signature.asc Description: This is a digitally signed message part
Bug#726947: r-base: depends on deprecated package texi2html
Source: r-base Version: 3.0.2-1 Severity: important Tags: patch I have just noticed that the texi2html package is deprecated in unstable (see bug#710466). Patch: simply remove it from the Build-Depends and Suggests fields in debian/control, and it builds absolutely fine. Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726945: pdns-backend-pgsql: fails to upgrade from testing: ERROR: syntax error at or near "NOT" LINE 1: ...ABLE supermasters ALTER COLUMN ip TYPE VARCHAR(64) NOT NULL; ^
I have a patch for this, will submit it to the maintainers soon, if it's not already fixed in their git. On Oct 20, 2013, at 22:36 , Andreas Beckmann wrote: > Package: pdns-backend-pgsql > Version: 3.3-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'jessie'. > It installed fine in 'jessie', then the upgrade to 'sid' fails. > >> From the attached log (scroll to the bottom...): > > Setting up pdns-server (3.3-1) ... > Installing new version of config file /etc/init.d/pdns ... > Installing new version of config file /etc/insserv.d/pdns-server ... > Replacing config file /etc/powerdns/pdns.conf with new version > invoke-rc.d: policy-rc.d denied execution of start. > Setting up pdns-backend-pgsql (3.3-1) ... > dbconfig-common: writing config to > /etc/dbconfig-common/pdns-backend-pgsql.conf > creating database backup in > /var/cache/dbconfig-common/backups/pdns-backend-pgsql_3.1-4.pgsql. > applying upgrade sql for 3.1-4 -> 3.3-1. > error encountered processing > /usr/share/dbconfig-common/data/pdns-backend-pgsql/upgrade/pgsql/3.3-1: > ERROR: syntax error at or near "NOT" LINE 1: ...ABLE supermasters ALTER > COLUMN ip TYPE VARCHAR(64) NOT NULL; ^ > dbconfig-common: pdns-backend-pgsql configure: aborted. > dbconfig-common: flushing administrative password > dpkg: error processing pdns-backend-pgsql (--configure): > subprocess installed post-installation script returned error exit status 1 > Processing triggers for libc-bin ... > Errors were encountered while processing: > pdns-backend-pgsql > > > cheers, > > Andreas > Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#726807: pu: package usemod-wiki/1.0.5-1
Control: tags -1 + confirmed On Sat, 2013-10-19 at 16:13 +0200, Cyril Brulebois wrote: > Christoph Berg (2013-10-19): > > Do I need to put anything special in the distribtution field for that, > > or do you just do the cherry-picking for that yourself? > > I think it's cherry-picked from s-p-u, so uploading it there should work > on your side. Indeed. Please go ahead, and we'll look at wheezy-updates after that. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726946: ruby-gettext: rxgettext writes location paths relative to output file directory
Package: ruby-gettext Version: 3.0.2-2 Severity: normal Hi again! I noticed something really weird in rxgettext. It seems that its output .pot file includes location paths relative to the destination directory, rather than to the current working directory! I am not sure this causes problems with ruby-gettext library, but it sure looks unusual and awkward. I'll show the issue with my usual test case, described in bug #684182 [1]. [1] http://bugs.debian.org/684182 Let's start with the example application in a directory: $ tree . └── myapplication.rb 0 directories, 1 file Then, let's create a subdirectory: $ mkdir po and create the .pot file with xgettext: $ xgettext --add-comments=TRANSLATORS --no-wrap \ --copyright-holder="Francesco Poli" \ --package-name=myapplication --package-version=0.1 \ --msgid-bugs-address="addr...@example.com" \ --language=python \ myapplication.rb -o po/myapplication_XGETTEXT.pot $ cat po/myapplication_XGETTEXT.pot # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR Francesco Poli # This file is distributed under the same license as the PACKAGE package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: myapplication 0.1\n" "Report-Msgid-Bugs-To: addr...@example.com\n" "POT-Creation-Date: 2013-10-20 22:35+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: 8bit\n" #: myapplication.rb:24 msgid "Hello everybody!\n" msgstr "" #: myapplication.rb:27 msgid "You are running an internationalized Ruby program.\n" msgstr "" #. TRANSLATORS: %d is the number of already printed messages #: myapplication.rb:31 #, python-format msgid "You have already seen %d translatable messages.\n" msgstr "" #: myapplication.rb:33 msgid "Is this message # 3 or # 4 ?\n" msgstr "" #: myapplication.rb:35 msgid "OK, I am tired...\n" msgstr "" #: myapplication.rb:37 msgid "Goodbye!\n" msgstr "" This is OK. Let's try with rxgettext: $ rxgettext --add-comments=TRANSLATORS --no-wrap \ --copyright-holder="Francesco Poli" \ --package-name=myapplication --package-version=0.1 \ --msgid-bugs-address="addr...@example.com" \ myapplication.rb -o po/myapplication_RXGETTEXT.pot $ cat po/myapplication_RXGETTEXT.pot # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR Francesco Poli # This file is distributed under the same license as the myapplication package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: myapplication 0.1\n" "Report-Msgid-Bugs-To: addr...@example.com\n" "POT-Creation-Date: 2013-10-20 22:39+0200\n" "PO-Revision-Date: 2013-10-20 22:39+0200\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n" #: ../myapplication.rb:24 msgid "Hello everybody!\n" msgstr "" #: ../myapplication.rb:27 msgid "You are running an internationalized Ruby program.\n" msgstr "" #. TRANSLATORS: %d is the number of already printed messages #: ../myapplication.rb:31 msgid "You have already seen %d translatable messages.\n" msgstr "" #: ../myapplication.rb:33 msgid "Is this message # 3 or # 4 ?\n" msgstr "" #: ../myapplication.rb:35 msgid "OK, I am tired...\n" msgstr "" #: ../myapplication.rb:37 msgid "Goodbye!\n" msgstr "" Please note that the location paths are "../myapplication.rb", rather than "myapplication.rb". I think that rxgettext should behave like xgettext in this respect. Please fix this bug and/or forward this bug report upstream. Thanks for your time! -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (800, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ruby-gettext depends on: ii ruby 1:1.9.3 ii ruby-locale 2.0.8-1 ii ruby-text 1.2.1-1 ii ruby1.8 [ruby-interpreter]1.8.7.358-8 ii ruby1.9.1 [ruby-interpreter] 1.9.3.448-1 ruby-gettext recommends no packages. ruby-gettext suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726874: pu: package darktable/1.0.4-1+deb7u1
Control: tags -1 + confirmed On Sat, 2013-10-19 at 23:12 -0300, David Bremner wrote: > I have prepared a targeted upload which closes two CVEs. > > These are relatively mild security bugs in the embedded copy of libraw > (which cannot be trivially removed, alas). > > A debdiff is attached. I believe the risk of the update is relatively > low, since according to darktable upstream only a few code paths > actually use libraw. On the other hand, I did have to monkey with the > patch a bit by hand to get it to apply, since libraw upstream provided > a patch against a later version. Assuming the patch has been tested on a stable system, please go ahead; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722600: apt-cacher-ng: Daily cron job emits unexplained messages
tags 722600 +pending tags 720296 +pending tags 720954 +pending tags 722907 +pending tags 726925 +pending tags 722712 +pending thanks Hallo, * Eduard Bloch [Sun, Oct 20 2013, 10:19:52PM]: > > Sep 12 06:36:30 asusb202 apt-cacher-ng[31312]: 183007 > > Sep 12 06:36:30 asusb202 apt-cacher-ng[31312]: 183027 > > Sep 12 06:36:31 asusb202 apt-cacher-ng[31312]: 374917 > > Sep 12 06:36:31 asusb202 apt-cacher-ng[31312]: 374912 > > Thanks for noticing. Recently I discoverd them too and the only > explanation I have is that we are both using systemd, right? That's the > scenario where stdout/stderr are not closed but redirected to systemd > instead. Otherwise, the service usually daemon'izes itself, closing > interactive file descriptors. > > Unfortunately I cannot see the code. I'd expect it in cacheman.cc or And there was a reason for that, it was not in my code. It's leaking from the red utility while it's patching the old index data. I will --silence it and it should be alright. Regards, Eduard. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726347: Acknowledgement (samba: FTBFS on hppa: undefined krb5 references)
Actually, the conflict is libkrb5-dev. Had a successful build with it removed. Dave -- John David Anglin dave.ang...@bell.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#570267: libcdk5: new upstream release
Hello, I have packaged the new upstream release. Some time ago I tried to adopt this package but I couldn't find a sponsor. I didn't want to waste all the work done, so here it is: http://mentors.debian.net/package/libcdk5 And the development is done at: https://gitorious.org/deb-pkg/libcdk5 Regards pgpbpM1lzMBP1.pgp Description: PGP signature
Bug#726945: pdns-backend-pgsql: fails to upgrade from testing: ERROR: syntax error at or near "NOT" LINE 1: ...ABLE supermasters ALTER COLUMN ip TYPE VARCHAR(64) NOT NULL; ^
Package: pdns-backend-pgsql Version: 3.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'sid' fails. >From the attached log (scroll to the bottom...): Setting up pdns-server (3.3-1) ... Installing new version of config file /etc/init.d/pdns ... Installing new version of config file /etc/insserv.d/pdns-server ... Replacing config file /etc/powerdns/pdns.conf with new version invoke-rc.d: policy-rc.d denied execution of start. Setting up pdns-backend-pgsql (3.3-1) ... dbconfig-common: writing config to /etc/dbconfig-common/pdns-backend-pgsql.conf creating database backup in /var/cache/dbconfig-common/backups/pdns-backend-pgsql_3.1-4.pgsql. applying upgrade sql for 3.1-4 -> 3.3-1. error encountered processing /usr/share/dbconfig-common/data/pdns-backend-pgsql/upgrade/pgsql/3.3-1: ERROR: syntax error at or near "NOT" LINE 1: ...ABLE supermasters ALTER COLUMN ip TYPE VARCHAR(64) NOT NULL; ^ dbconfig-common: pdns-backend-pgsql configure: aborted. dbconfig-common: flushing administrative password dpkg: error processing pdns-backend-pgsql (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin ... Errors were encountered while processing: pdns-backend-pgsql cheers, Andreas pdns-backend-pgsql_3.3-1.log.gz Description: GNU Zip compressed data
Bug#726915: Patch
The patch must obviously be prepared with inverted files. leo_fix.patch Description: Binary data signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#717557: gcc-4.8: can't compile working 64bit kernel with 32bit userspace gcc-4.8
Am 20.10.2013 00:25, schrieb Ben Hutchings: > On Sat, 2013-10-19 at 23:38 +0200, Matthias Klose wrote: >> Control: severity -1 important Control: tags -1 + moreinfo >> In file included from :0:0: /usr/include/stdc-predef.h:30:26: fatal error: bits/predefs.h: No such file >>> or directory #include ^ >>> compilation terminated. >>> >>> It looks like I can avoid this by changing the compile tests to use >>> the -nostdinc option. But this change may possibly cause other >>> problems, and neither the pre-included header nor the fact that >>> -nostdinc disables it seem to be documented. >> >> please attach the test program and the command line options used for this >> test case. I think the issue is within the kernel build system not being >> prepared for multiarch and -nostdinc. > > gcc-4.8 -m64 -x c -c /dev/null works for me on a current sid/i386. I assume that gcc-4.8-multilib is installed? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#723689: Bug solved
Hello, This problem has been solved as per notes in this bug. https://bugzilla.kernel.org/show_bug.cgi?id=61971 Conclusion: Fix will be in kernel 3.13. Regards Magnus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726943: Hibernation: invisible shell without X, crazy frame buffer with X(fbdev)
Package: src:linux Version: 3.2.51-1 Severity: normal Dear Maintainer, I've some problems about Hibernation (aka Suspend-To-Disk, STD). I've tried to hibernate my system with 'echo disk > /sys/power/state'; all seems work pretty. After reboot, I've edited by grub the kernel options by adding 'resume=/dev/sda4' option. After kernel boot, if I've done Hibernation command without X, I don't see anything after kernel loading; I can't log in (I don't use DMs), I can only reboot with system button. Else if I've done Hibernation command with X, frame buffer crazys (I use fbdev, see below if you want to know why). Anyway, also in this case I have to press system button. I'm sorry, but I don't know how can I help you because I can't monit my system when it is in sleep mode. I think there is something doesn't go with GMA 3600 drivers, you should remember that gma500 driver is a kernel experimental driver. But, when I used 2.6 kernel, there wasn't DRM support for this GPU, so I used VESA drivers, but there was that bug. My suspects are shifted on ACPI. I don't know where to search. I'm sorry, I am not yet a developer or a debugger. -- Package-specific info: ** Version: Linux version 3.2.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.46-1+deb7u1 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-686-pae root=UUID=96ea1526-0f5b-4e66-aae3-60f578b6e87c ro quiet acpi_osi=Linux acpi_backlight=vendor ** Not tainted ** Kernel log: [ 10.070749] gma500 :00:02.0: allocated 1024x600 fb [ 10.071182] fbcon: psbfb (fb0) is primary device [ 10.136154] usb 1-4: New USB device found, idVendor=04f2, idProduct=b26f [ 10.136169] usb 1-4: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 10.136181] usb 1-4: Product: USB2.0 0.3M UVC WebCam [ 10.136191] usb 1-4: Manufacturer: Chicony Electronics Co., Ltd. [ 10.136200] usb 1-4: SerialNumber: 0x0001 [ 10.261374] Linux media interface: v0.10 [ 10.277148] Linux video capture interface: v2.00 [ 10.286631] uvcvideo: Found UVC 1.00 device USB2.0 0.3M UVC WebCam (04f2:b26f) [ 10.305189] input: USB2.0 0.3M UVC WebCam as /devices/pci:00/:00:1d.7/usb1/1-4/1-4:1.0/input/input7 [ 10.305515] usbcore: registered new interface driver uvcvideo [ 10.305521] USB Video Class driver (1.1.1) [ 10.463808] Console: switching to colour frame buffer device 128x37 [ 10.471584] fb0: psbfb frame buffer device [ 10.471589] drm: registered panic notifier [ 10.471710] [drm] Initialized gma500 1.0.0 2011-06-06 for :00:02.0 on minor 0 [ 10.471950] snd_hda_intel :00:1b.0: irq 46 for MSI/MSI-X [ 10.472027] snd_hda_intel :00:1b.0: setting latency timer to 64 [ 10.687982] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.5, id: 0x1e0b1, caps: 0xf00073/0x24/0xa2400 [ 10.757173] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input8 [ 10.995993] HDMI status: Codec=1 Pin=3 Presence_Detect=0 ELD_Valid=0 [ 10.996557] input: HDA Intel HDMI/DP,pcm=3 as /devices/pci:00/:00:1b.0/sound/card0/input9 [ 10.997828] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input10 [ 10.998950] uhci_hcd :00:1d.0: setting latency timer to 64 [ 10.998972] uhci_hcd :00:1d.0: UHCI Host Controller [ 10.999040] uhci_hcd :00:1d.0: new USB bus registered, assigned bus number 2 [ 10.999144] uhci_hcd :00:1d.0: irq 23, io base 0xf080 [ 10.999387] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [ 10.999409] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 10.999426] usb usb2: Product: UHCI Host Controller [ 10.999441] usb usb2: Manufacturer: Linux 3.2.0-4-686-pae uhci_hcd [ 10.999457] usb usb2: SerialNumber: :00:1d.0 [ 11.000260] hub 2-0:1.0: USB hub found [ 11.000286] hub 2-0:1.0: 2 ports detected [ 11.000633] uhci_hcd :00:1d.1: setting latency timer to 64 [ 11.000648] uhci_hcd :00:1d.1: UHCI Host Controller [ 11.000688] uhci_hcd :00:1d.1: new USB bus registered, assigned bus number 3 [ 11.000895] uhci_hcd :00:1d.1: irq 21, io base 0xf060 [ 11.001127] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 11.001148] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 11.001166] usb usb3: Product: UHCI Host Controller [ 11.001182] usb usb3: Manufacturer: Linux 3.2.0-4-686-pae uhci_hcd [ 11.001199] usb usb3: SerialNumber: :00:1d.1 [ 11.001880] hub 3-0:1.0: USB hub found [ 11.001904] hub 3-0:1.0: 2 ports detected [ 11.002275] uhci_hcd :00:1d.2: setting latency timer to 64 [ 11.002290] uhci_hcd :00:1d.2: UHCI Host Controller [ 11.002332] uhci_hcd :00:1d.2: new USB bus registered, assigned bus number 4 [ 11.002440] uhci_hcd :00:1d.2: irq 18, io base 0xf040 [ 11.002605] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [
Bug#726944: samba-common: /etc/pam.d/samba not removed on upgrade
Package: samba-common Version: 2:4.0.10+dfsg-2 Severity: normal File: /etc/pam.d/samba Hi, The samba-common package is not shipping /etc/pam.d/samba file anymore. However the it isn't explictly removing it on upgrade. Please explicitly remove this obsolete conffile on upgrade. Cheers Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages samba-common depends on: ii debconf [debconf-2.0] 1.5.51 ii dpkg 1.17.1 ii ucf3.0027+nmu1 Versions of packages samba-common recommends: ii samba-common-bin 2:4.0.10+dfsg-2 samba-common suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722600: apt-cacher-ng: Daily cron job emits unexplained messages
Hallo, * Dominique Brazziel [Thu, Sep 12 2013, 01:13:20PM]: > Package: apt-cacher-ng > Version: 0.7.18-1 > Severity: normal > > Dear Maintainer, > > In the last couple weeks the daily cron job which calls > 'expire-caller.pl' has been sporadically emitting messages > with only a number with no further edifying text, i.e.: > > Sep 12 06:36:30 asusb202 apt-cacher-ng[31312]: 183007 > Sep 12 06:36:30 asusb202 apt-cacher-ng[31312]: 183027 > Sep 12 06:36:31 asusb202 apt-cacher-ng[31312]: 374917 > Sep 12 06:36:31 asusb202 apt-cacher-ng[31312]: 374912 Thanks for noticing. Recently I discoverd them too and the only explanation I have is that we are both using systemd, right? That's the scenario where stdout/stderr are not closed but redirected to systemd instead. Otherwise, the service usually daemon'izes itself, closing interactive file descriptors. Unfortunately I cannot see the code. I'd expect it in cacheman.cc or expiration.cc but right now I couldn't spot printing of one single file size to stdout or stderr. It must be very obvious and might be a very old "problem" which only started appearing now. Not as old as the 20-years-X.org-bug, though ;-). > perhaps a 'before' and 'after' size is output to syslog. The > likely suspects are 'maintenance.cc' and 'fileitem.cc' but I haven't > been able to pinpoint the line of code yet. maintenance.cc - unlikely, it's just entry point for the control UI and some low-level helpers. fileitem.cc is possible but also unlikely, it's base class for various work and would have spammed syslog thousand times by now if this bug were therein. I will keep looking and hope to catch this within a couple of days. Regards, Eduard. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726942: override: createrepo:admin/extra
Package: ftp.debian.org Severity: normal Dear ftpmasters, Please downgrade createrepo to priority extra since it depends on several packages of priority extra (including deltarpm, rpm, and yum). Thanks, -- mike signature.asc Description: Digital signature
Bug#688212:
يوم جيد ؛ مع الاحترام الواجب والإنسانية ، واضطررت أن أكتب إليكم تحت الارض الإنسانية . اسمي Mrs.Viviane Akpene . لقد ولدت في بالتيمور ، ميريلاند ، أنا متزوجة من السيد تيموثي Akpene . مدير JC الصناعة المحدودة توغو . كنا متزوجين لمدة 36 عاما دون طفل . وتوفي بعد شرايين القلب . مؤخرا ، قال لي طبيبي بأنني لن تستمر للأشهر الستة المقبلة بسبب مشكلة السرطان (سرطان رافعة و السكتة الدماغية ) . قبل زوجي توفي العام الماضي هناك هذا المبلغ 2.8 مليون نسمة، و أودع في أحد البنوك هنا في توغو . في الوقت الحاضر هذا المال ما زال في الغرب . و أنا التي كنت تعرف قررت التبرع لهذا الصندوق إلى أي أخ أو أخت التي سوف تستخدم هذه الأموال في الطريق و انا ذاهب الى مساعدة هنا . أريد أن شخصا ما سوف يتم استخدام هذا الصندوق وفقا ل رغبتي في زوجها الراحل لمساعدة الناس الأقل حظا ، ودور الأيتام ، والأرامل ، ويعمل بشكل جيد . وقد اتخذ هذا القرار لأنني ليس لدي أي أن الطفل سيرث هذا الصندوق ، و أنا لا أريد في الطريق حيث سيتم استخدام هذه الأموال بطريقة سيئة . وهذا هو السبب في أنني آخذ هذا القرار لتسليم لك أكثر من هذا الصندوق . أنا لست خائفا من الموت ، ثم أنا أعرف أين أنا ذاهب . أنا أريد منك أن تذكر لي دائما في صلواتي القادمة بسبب جراحة سرطان حتى . سأكتب مرة أخرى في أقرب وقت ممكن وأي تأخير في ردكم سوف تعطيني غرفة في تحديد مصدر الشخص الآخر لهذا الغرض نفسه ، تفضلوا بقبول فائق الاحترام ، Mrs.Viviane Akpene
Bug#726941: rxgettext: please implement a command-line option to set the copyright YEAR
Package: ruby-gettext Version: 3.0.2-2 Severity: wishlist Hello again, it would be great if rxgettext had a command-line option to specify what should be put in the output .pot file in stead of the "YEAR" in the copyright notice. In other words, let's consider (again) the test case described in bug #684182 [1]. [1] http://bugs.debian.org/684182 If I create the .pot with rxgettext: $ rxgettext --add-comments=TRANSLATORS --no-wrap \ --copyright-holder="Francesco Poli" \ --package-name=myapplication --package-version=0.1 \ --msgid-bugs-address="addr...@example.com" \ myapplication.rb -o myapplication_RXGETTEXT.pot the copyright notice in the output .pot is: $ grep Copyright myapplication_RXGETTEXT.pot # Copyright (C) YEAR Francesco Poli As far as I know, there's no way to tell rxgettext to replace that "YEAR" with, say, "2012", "1999-2013", or "1998, 2005-2007, 2012". I think it would be useful to have some command-line option to do that. Something like $ rxgettext ... --copyright-year="1999-2013" ... Please implement this additional feature and/or forward this bug report upstream. Thanks for your time! -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (800, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ruby-gettext depends on: ii ruby 1:1.9.3 ii ruby-locale 2.0.8-1 ii ruby-text 1.2.1-1 ii ruby1.8 [ruby-interpreter]1.8.7.358-8 ii ruby1.9.1 [ruby-interpreter] 1.9.3.448-1 ruby-gettext recommends no packages. ruby-gettext suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722179: Should mount pstore pseudo-filesystem
tags 722179 + pending thanks On Sun, Sep 08, 2013 at 09:04:01PM +0100, Ben Hutchings wrote: > Please mount pstore on /sys/fs/pstore if this directory exists at > boot time. Added to sysvinit git, it will be in the next upload. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Bug#726940: ITP: node-buffer-crc32 -- computes crc32 of buffers and strings - module for Node.js
Package: wnpp Severity: wishlist Owner: "Jérémy Lal" * Package name: node-buffer-crc32 Version : 0.2.1 Upstream Author : Brian J. Brennan * URL : https://github.com/brianloveswords/buffer-crc32 * License : Expat Programming Lang: JavaScript Description : computes crc32 of buffers and strings - module for Node.js This module provides a standard implementation of the error-detecting code known as 32-bit Cyclic Redundancy Check. . Node.js is an event-based server-side javascript engine. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726743: RM: libfusioninventory-agent-task-netdiscovery-perl -- ROM; replaced by fusioninventory-agent
Hi Ansgar, > Should that package also be removed? Yes absolutly, > Note that this is the 2.1-1 version, not 1:2.3.2-2. Yes, 1:2.3.2-2 is the new fusioninventory-agent package that replace them. -- Gonéri pgpx_FSi6gwdl.pgp Description: PGP signature
Bug#726939: Laptop function keys for LCD backlight not working
Package: gnome-shell Version: 3.8.4-4 Severity: normal This is a regression from gnome-shell 3.4. On this laptop I could hold down the funtion key and be pressing f2 or f4 I could dim or brighten the LCD backlight. These kesy now do nothing. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (800, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_AU.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.18.0-1 ii evolution-data-server3.8.5-2 ii gdm3 3.8.4-2 ii gir1.2-accountsservice-1.0 0.6.34-2 ii gir1.2-caribou-1.0 0.4.12-1 ii gir1.2-clutter-1.0 1.14.4-3 ii gir1.2-freedesktop 1.36.0-2+b1 ii gir1.2-gcr-3 3.8.2-4 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.36.0-2+b1 ii gir1.2-gmenu-3.0 3.8.0-2 ii gir1.2-gnomebluetooth-1.03.8.1-2 ii gir1.2-gnomedesktop-3.0 3.8.4-2 ii gir1.2-gtk-3.0 3.8.5-1 ii gir1.2-ibus-1.0 1.5.4-1 ii gir1.2-mutter-3.03.8.4-2 ii gir1.2-networkmanager-1.00.9.8.0-5 ii gir1.2-nmgtk-1.0 0.9.8.4-1 ii gir1.2-pango-1.0 1.32.5-5+b1 ii gir1.2-polkit-1.00.105-4 ii gir1.2-soup-2.4 2.44.1-1 ii gir1.2-telepathyglib-0.120.22.0-1 ii gir1.2-telepathylogger-0.2 0.8.0-2 ii gir1.2-upowerglib-1.00.9.22-1 ii gjs 1.36.1-2 ii gnome-bluetooth 3.8.1-2 ii gnome-icon-theme-symbolic3.8.2.2-2 ii gnome-settings-daemon3.8.5-2 ii gnome-shell-common 3.8.4-4 ii gnome-themes-standard3.8.4-1 ii gsettings-desktop-schemas3.8.2-2 ii libatk-bridge2.0-0 2.10.0-1 ii libatk1.0-0 2.10.0-2 ii libc62.17-93 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libcamel-1.2-43 3.8.5-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libclutter-1.0-0 1.14.4-3 ii libcogl-pango12 1.14.0-3 ii libcogl121.14.0-3 ii libcroco30.6.8-2 ii libdbus-1-3 1.6.16-1 ii libdbus-glib-1-2 0.100.2-1 ii libecal-1.2-15 3.8.5-2 ii libedataserver-1.2-173.8.5-2 ii libegl1-mesa [libegl1-x11] 9.1.7-1 ii libgck-1-0 3.8.2-4 ii libgcr-base-3-1 3.8.2-4 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libgirepository-1.0-11.36.0-2+b1 ii libgjs0c [libgjs0-libmozjs185-1.0] 1.36.1-2 ii libglib2.0-0 2.36.4-1 ii libgnome-menu-3-03.8.0-2 ii libgstreamer1.0-01.2.0-1 ii libgtk-3-0 3.8.5-1 ii libical0 0.48-2 ii libjson-glib-1.0-0 0.16.2-1 ii libmozjs185-1.0 1.8.5-1.0.0+dfsg-4+b1 ii libmutter0b 3.8.4-2 ii libnm-glib4 0.9.8.0-5 ii libnm-gtk0 0.9.8.4-1 ii libnm-util2 0.9.8.0-5 ii libnspr4 2:4.10-1 ii libnspr4-0d 2:4.10-1 ii libnss3 2:3.15.1-1 ii libnss3-1d 2:3.15.1-1 ii libp11-kit0 0.18.5-3 ii libpango-1.0-0 1.32.5-5+b1 ii libpangocairo-1.0-0 1.32.5-5+b1 ii libpolkit-agent-1-0 0.105-4 ii libpolkit-gobject-1-00.105-4 ii libpulse-mainloop-glib0 4.0-6+b1 ii libpulse0
Bug#726818: Not limited to sftp; limited to GCM ciphers
retitle 726818 openssh-server: fatal xfree error when RekeyLimit hit with GCM kthxbye This bug is not limited to sftp; it is present when cat'ing a file over SSH as well. However, it is limited to the GCM cipher suites. When using aes256-...@openssh.com or aes128-...@openssh.com, the connection is reset, although it is not with aes256-ctr. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#569668: some progress
Sorry, for having you waiting. Previous months got other projects higher priority. Now back to this project, sponsoring Davmail. I have a working setup for Davmail for about two years. It is daily used. (Hence the reason for low priority for another setup.) Now I have second setup for Davmail, this time with a .deb that should be uploaded to the Debian archive. Status: * davmail runs a second computer * IMAP works fine * SMTP doesn't work yet * now investigating what is wrong the SMTP part in my second configuration. Feel free to ping me for another progress report. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726012: orange: depends on librapi2, libsynce which are to be removed
reassign -1 ftp.debian.org retitle -1 RM: orange -- RoM On Wed, Oct 16, 2013 at 03:48:03PM +0200, Michael Biebl wrote: > I'm bumping the severity to serious, since this is blocking the removal > of hal which we should get rid of sooner rather then later. then let's drop orange too. Neither me nor upstream is heavily interested in it anyways. Greets Evgeni -- Bruce Schneier can read and understand Perl programs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726938: Vcs-* repositories are missing
Package: bugs-everywhere Severity: normal According to: http://packages.qa.debian.org/b/bugs-everywhere.html the package sources should be available at: http://bzr.debian.org/bzr/collab-maint/bugs-everywhere/bugs-everywhere.debian/ http://bzr.debian.org/loggerhead/collab-maint/bugs-everywhere/bugs-everywhere.debian/ Both URLs return 404s here. -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org