Bug#754234: LZMA support in squashfs-tools
Hi filesystems-devel! There is no LZMA support in the Debian version of unsquashfs (provided by squashfs-tools). This can be fixed simply by defining LZMA_XZ_SUPPORT = 1, and more information can be found in #754234. It is true that LZMA is depreciated, so I understand if the filesystems group doesn't want it to be enabled, but seeing as there are still some images that use LZMA, would a patch to re-enable the functionality be accepted? Yours thankfully, Riley Baird pgpKlp7afCCwo.pgp Description: PGP signature
Bug#789358: sphinxcontrib-nwdiag: Broken watchfile
Source: sphinxcontrib-nwdiag Severity: normal Tags: patch Dear Maintainer, please see attached watchfile. -- tobi -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) version=3 opts=uversionmangle=s/(rc|a|b|c)/~$1/ \ http://pypi.debian.net/nwdiag/nwdiag-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
Bug#789346: mate-sensors-applet: Cannot install mate-sensors-applet-common because a .mo file is also present in mate-sensors-applet
Hi, Sorry, my mistake - set too old version in Replaces/Breaks field. This commit might fix the problem: https://github.com/mate-desktop/debian-packages/commit/c73060e541bfbb137782921bd28e6a13aa117a47 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789181: apt-listbugs: should not list fixed bugs
Control: retitle -1 debbugs: should guarantee that merged bug reports share the same found and fixed version lists On Sat, 20 Jun 2015 10:35:48 +0200 Francesco Poli wrote: [...] I think that debbugs should guarantee that merged bug reports share the same found and fixed version lists. [...] I forgot to re-title the bug report... I am doing so now. Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpkga0u2Si16.pgp Description: PGP signature
Bug#789359: sphinxcontrib-blockdiag: Broken watchfile
Source: sphinxcontrib-blockdiag Severity: normal Tags: patch Dear Maintainer, please see attached watchfile. -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) version=3 opts=uversionmangle=s/(rc|a|b|c)/~$1/ \ http://pypi.debian.net/blockdiag/blockdiag-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
Bug#789365: transition: ghc-7.8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear release team, we (the Debian Haskell Group) has been working hard to get everything in order for GHC 7.8 to migrate to testing (and top open the way for 7.10 in unstable :-)). We have had regular status reports on the haskell mailing list. Now we are getting close enough for the migration to happen that I believe we should include you in status updates and notifications, and also because you can probably help. Please CC debian-hask...@lists.debian.org in mails to this bug, to keep everyone up-to-date. - From what I can tell, there are these blockers: * Packages in NEW Mostly gitit, which has an added binary file: https://ftp-master.debian.org/new/gitit_0.10.7-1.html The other two haskell packages in NEW do not seem to be testing relevant, so this is looking good. * Package removals There are a large number of Haskell package removales scheduled for unstable, but most of them are stalled, as there are still old binaries and sources depending on these packages. This is mostly due to sparc not keeping up, which is mostly due to nettle not building there: http://bugs.debian.org/789013 I’m not sure what to best do here. Since sparc is not a release architecture, this should not hold up the release, but technically it does. Maybe the removals can be added as hints to britney? Will that interact properly with the auto-hinter? * leksah Despite multiple calls on the mailing list, no contributor was willing and able to fix that package in reasonable time. I suggest you remove haskell-leksah and haskell-leksah-server from testing (on the grounds that the maintenance situation makes it not suitable for a Debian stable release). This should unblock this situation. * shake not building on powerpc This is a weird issue: https://lists.debian.org/debian-haskell/2015/06/msg00043.html As this is an almost leave package, I suggest to remove haskell-shake and haskell-hoogle on powerpc for now, and hence disentangle this problem from the transition. I’m still looking for volunteers to investigate this issue. * Other out of date packages, mostly mips and mipsel I keep watching https://release.debian.org/transitions/html/haskell.html and I believe most problems are solved there. When today's upload and binNMUs have built everywhere there might be a package or two which no longer build on mips/mipsel (due to lack of TemplateHaskell support) and can be solved by a removal on these architectures. * Some packages need to age As usual. Is there a way for you, or better, me, to see if this list is exhaustive? Some kind of „what if when“ britney run where I can feed some removals and age-override hints and see what the auto-hinter+britney does? Thanks, Joachim - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlWFP1EACgkQ9ijrk0dDIGwGRwCfadFimFcT8DQDlLWLOyYOQyI7 WKsAoKbqayqfnth3z5DWcvgRx3gnNGSP =OBHB -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789364: pmuninstall: package description with indented line that causes bad formatting
Package: pmuninstall Severity: minor Hi, in the last change of the package description an indentation in one of the lines was added. The initial space causes the line to be treated as a verbatim line and non to be reflowed for different display width. For example it is displayed in a different font in the package page. The results can be seen here: https://packages.debian.org/sid/pmuninstall I think that space should be removed so as to permit the text both to be treated all in the same way and to allow flowed-text formatting where available. Thanks, beatrice -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789356: release-notes: Titles in PDF versions are made of incorrect characters
Package: release-notes Severity: normal Dear Maintainer, Titles in PDF versions of the Jessie release notes are made of incorrect characters. For example : `QdkdÞrd Mnsdr enq CdahÞm 7 —idrrhd(... 21/ahs OB' instead of : `Release Notes for Debian 8 (jessie), 32-bit PC' For this reason, the release notes cannot be used properly, although paragraphes have not this problem. This happens only for PDF versions (not HTML or plain text ones). This happens at least for English and French versions. This happens for all architectures. I have double checked with another computer and another PDF reader, the problem is still there. Thank you in advance. Xavier -- System Information: Debian Release: 7.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) 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#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/19/2015 01:37 PM, James Cowgill wrote: From the bug: RC severity mostly so this shows up on the radars of all the right people crossing off the details we need to finalise for the release. That doesn't apply here. stretch will be released at some point in the future and we will exactly run into the same problem. We already did for Jessie where cmus is now broken by default. Hmm I personally can't get cmus to break this way but it could be RC if it breaks in default installations. Did you remove your .cmus configuration directory? If you have an existing .cmus directory, it often works. However, this bug was discovered by someone at my physics department after upgrading to Jessie. Initially, .cmus immediately segfaulted with her old configuration directory. I asked her to rename it, so cmus would use a new directory and she ended up with the application being stuck at the start because of libdnet. It is clearly reproducible. Just did a test install on an unstable system where cmus was never installed and I get: glaubitz@ikarus:~$ cmus getnodeadd: Can not open /etc/decnet.conf Interestingly, on this machine there is a timeout and cmus starts eventually. However, I have seen machines (which had a static IP network configuration) where it hung forever. Which is my whole point. Then this is a bug in roaraudio / dnprogs, not cmus. No one denies that. However, the problem is that the ROAR people refuse to drop DECnet support and hence Ron asked in [1] to drop ROAR audio support. The ROAR developers and maintainers refuse to do that which is why we should drop it from cmus. They, for some reason, think it's important to support a pre-historic networking protocol. I found this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675014 Which was closed with the message Go away, I don't care. This is the newer one: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755934 Which is, again, ignored. But I couldn't find any evidence the _current_ maintainer of roaraudio has refused to remove DECnet support. The current bug about it has no replies. Quoting what Ron said who requested the removal in [1]: But basically roar was a disaster on lots of fronts as we were trying to wrap up the wheezy freeze. It was getting dragged in as a hard dependency by packages it was pretty hard to avoid having installed if you had any sort of media support application installed - and the DECNet farce meant that was breaking people's network configuration. It in turn was also depending on the obsolete celt package which we trying to get removed from wheezy - and every attempt to get its maintainers to try to fix these things was met with what problem? I see no problem here. DECNet is essential functionality, we can't drop it ... Which basically meant the only choice remaining was to get roar itself removed from wheezy (which meant dropping the deps on it for anything that didn't also want to get removed with it). AFAICT, about the only two actual users of roar in the world are Philipp, its primary author, and his mate Stephan (who filed all the bring it back bugs for him). If cmus is Recommending it again, then yeah, dropping that back to a suggests at the very least seems like a prudent move if it's still breaking people's systems ... Though if it's still going to break the systems of people who install it as a Suggests - and its upstream is still refusing to fix that after all these years of it being a known problem, I have to wonder a bit about even the value of that ... but that's really a question for the cmus users and maintainer to decide where the value lies. Adrian [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675610 - -- .''`. 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 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhTcxAAoJEHQmOzf1tfkTOq4P/R+TWffDmc9w4+LVPrVtNwFR Tg/GSmOGQk6WyXWVqZWD8EZLIOdSovnPcNd9l/Nig6DEI+3/XQmPq0CehX12qIiJ y8hNHwNvwyEKP3qQzYJ6fDtHUFuo+xF2CthHTta54bjF9/LiJktZwh5xSqAJrjk+ tC0g8iXjgffubxpHzMiVuWZAAXHhofzJ6KxUr8ppRHRJcuZCnK8hgjPCf8mqOZli rNj0MMTIu4YQI+cPyAKA6CZP3sgYqqBUKrDSqCKMkMwJypX+7ndFS6LFyJK5VlNM e8yk2bH9yZgy5wy5Rb/cT/me0W64lH2aKpT3tYGjyMtIG2y0Dsgej7+NUEOX64eN L+q4E4o/yR1ruirEeMQWe3YzigbI8xCJHFBslpSoVFG3+s7rgLJPTwo+oWKW0m/Z qAyy/TIyCLDa2V/Fnzf1TWo/5qFA0Y+XtKEApiwEFodMM+XgSWli/fKPbq36XJ6W Nbv9WMWj9w0L2i1lqsbcTFkhtX5TjhuTMNYPf3R0e1guniaz+clUsvwICJv9sJAP sbgFpHZwy6LLAt6mM6fBLO+WFdxucndQftnB5SyPp1ZWJ+yLQdai8uRq7IL0fl8F 0e4VcZrVbCKDgQ5Q4ER/lMpNY7gn3gq/vUpv9rg2ZPw3rbFNPv1llQ6WsuJZft+J cn2tauus+TRYWWIOY5Hq =EfUG -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to
Bug#789265: Fresh Jessie install on laptop hangs with nouveau error when docked
Control: tags -1 moreinfo On Fri, Jun 19, 2015 at 12:02:08 +0100, Dávur Eyðunsson Sørensen wrote: Package: xserver-xorg-video-nouveau When installing a fresh Debian 8.1, it does install and the laptop does work and well, unless when docked in a Dell port replicator.. Booting when docked causes the laptop to hang with errors: [10.262751] nouveau E[PDISP][:01:00.1] 02:0006:0342: no bios dp data [10.262858] nouveau E[PDISP][:01:00.1] 02:0006:0344: no bios dp data Same setup worked smoothly on Wheezy Spec: Dell Latitude E6400 bios revision A03 NVIDIA G68M Quadro NVS 160m rev a1 Missing lots of info here, please at least send the reportbug generated template. Cheers, Julien signature.asc Description: Digital signature
Bug#789361: awstats: page encoding broken when German language is selected
Package: awstats Version: 7.2+dfsg-1 Severity: wishlist Tags: patch Hi, when German language is selected, the page encoding is wrong, e.g. when displaying search engine terms. When switching to English language it’s correct. I tracked it down to a one liner; patch with fix attached (put it as debian/patches/0008_german_lang.patch for example). -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash, unfortunately Init: sysvinit (via /sbin/init) Versions of packages awstats depends on: ii perl 5.20.2-3+deb8u1 Versions of packages awstats recommends: ii coreutils 8.23-4 ii libnet-xwhois-perl 0.90-4 Versions of packages awstats suggests: ii apache2 [httpd] 2.4.10-10 ii apache2-mpm-prefork [httpd] 2.4.10-10 ii apache2-mpm-worker [httpd] 2.4.10-10 pn libgeo-ipfree-perl none ii libnet-dns-perl 0.81-2 ii libnet-ip-perl 1.26-1 ii liburi-perl 1.64-1 -- Configuration Files: /etc/awstats/awstats.conf changed [not included] /etc/awstats/awstats.conf.local changed [not included] -- no debconf information Description: Fix encoding in German translation. Author: Thorsten Glaser thorsten.gla...@teckids.org Forwarded: no --- a/wwwroot/cgi-bin/lang/awstats-de.txt +++ b/wwwroot/cgi-bin/lang/awstats-de.txt @@ -1,6 +1,6 @@ # German message file # $Revision: 1.20 $ - $Date: 2008/10/05 11:21:34 $ -PageCode=iso-8859-1 +PageCode=utf-8 message0=Unbekannt message1=Unbekannte (IP konnte nicht aufgelouml;st werden ) message2=Sonstige
Bug#789363: sphinxcontrib-actdiag: New watchfile
Source: sphinxcontrib-actdiag Severity: normal Dear Maintainer, See attached file. -- tobi -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) version=3 opts=uversionmangle=s/(rc|a|b|c)/~$1/ \ http://pypi.debian.net/sphinxcontrib-actdiag/sphinxcontrib-actdiag-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
On Sat, Jun 20, 2015 at 12:42:57PM +0200, John Paul Adrian Glaubitz wrote: Hi Adrian, Could you please make a bug against roaraudio asking to drop the libdnet dependency? Stephan, seriously, you are missing the point. Absolutely _no_one_ needs ROAR audio with DECnet support except you and your buddy Patrick. If you desperately need ROAR audio in cmus, then you can rebuild it manually. Debian should not keep packages that are dead upstream, especially when it comes to network libraries. There is _always_ the risk of these being the source of RC bugs. I have fixed dozens of such packages during the Wheezy release phase with NMU uploads because the original maintainer was MIA and we really should try to avoid such problems in future releases. Again, if you need ROAR audio in cmus, just rebuild the package yourself. It's not magic and would save you and us a lot of time and nerves. Thanks, 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 Kind Regards, Stephan signature.asc Description: Digital signature
Bug#787806: jessie-pu: package python-reportlab/3.1.8-3+deb8u1
Control: tags -1 + pending On 2015-06-18 20:19, Raphael Hertzog wrote: On Thu, 18 Jun 2015, Adam D. Barratt wrote: Please go ahead. Thanks, uploaded. Flagged for acceptance. 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#785780: jessie-pu: package python-keystonemiddleware 1.0.0-3 - 1.0.0-3+deb8u1 and python-keystoneclient 0.10.1-2 - 0.10.1-2+deb8u1 (CVE-2015-1852)
Control: tags -1 + pending On 2015-06-18 19:48, Adam D. Barratt wrote: Control: tags -1 -moreinfo +confirmed On Wed, 2015-06-17 at 10:50 +0200, Thomas Goirand wrote: Hi, Sorry, I almost completely forgot about this issue. I have uploaded a fix today in Sid and in Jessie backports. Can we get the fix reach Jessie proposed updates as well? I'm really not particularly keen on new (build-)dependencies for the sake of converting a string to a boolean, but I appreciate that it's upstream's fix. :-| Feel free to upload. Both packages were uploaded and I've flagged them for acceptance. 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#789367: ossim: Watchfile
Source: ossim Severity: normal Dear Maintainer, please see attached watch file. -- tobi -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) version=3 ftp://download.osgeo.org/ossim/source/ossim-([\d\.]+)/ossim-([\d\.]+)\.tar\.gz
Bug#788615: jessie-pu: package libgee-0.8/0.16.1-2
Am 20.06.2015 um 13:04 schrieb Adam D. Barratt: btw, I'm guessing this isn't really what you wanted; apologies for not spotting it earlier: --- libgee-0.8-0.16.1/debian/gbp.conf2014-10-15 18:39:14.0 + +++ libgee-0.8-0.16.1/debian/gbp.conf2015-06-19 21:29:58.0 + @@ -1,5 +1,5 @@ [DEFAULT] -debian-branch = debian-0.8 +debian-branch = debian-wheezy Urgh, yeah. This should obviously have been debian-jessie. Thanks for spotting this. It doesn't affect the package itself, but I'll fix that up in the git repository, in case we ever need a -1+deb8u2 upload. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#789366: libnet-openid-consumer-perl: FTBFS with perl 5.22 (CGI build-dep)
Source: libnet-openid-consumer-perl Version: 1.15-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch This package FTBFS with perl 5.22 (currently in experimental), since CGI has been removed from perl core: Can't locate object method param via package CGI::Subclass at /usr/share/per l5/Net/OpenID/IndirectMessage.pm line 50. # Looks like you planned 2 tests but ran 1. # Looks like your test exited with 2 just after 1. t/01-misc.t . 1..2 ok 1 - instantiated Dubious, test returned 2 (wstat 512, 0x200) Failed 1/2 subtests The fix is to add build-dependencies on libcgi-pm-perl | perl ( 5.19) Note: only the test suite uses CGI, so only a build-dependency is needed. This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789368: fonts-noto: error in package description - missing number of scripts makes sentence not understandable
Package: fonts-noto Severity: minor Hi! The last versions of the package description of fonts-noto contain this sentence [...]Unicode scripts (currently are covered, at least partly, across hinted, unhinted and CJK packages). there used to be the number of scripts inside the parenthesis like so: currently number are covered. I don't know if a script is supposed to put the number there or it was inserted by hand. Anyway the sentence inside the parenthesis as it is now it is not clear. thanks, beatrice -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789353: unicode-data: new upstream release (8.0.0)
Package: unicode-data Severity: wishlist Please update unicode-data to Unicode 8.0.0: http://codel10n.com/unicode-consortium-announces-unicode-8/ http://blog.unicode.org/2015/06/announcing-unicode-standard-version-80.html http://www.unicode.org/versions/Unicode8.0.0/ -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#789354: FTBFS: rpm/librpm4_stubs.c:221:18: error: 'RPMTAG_SUGGESTSNAME' undeclared
Source: dose3 Version: 3.3-3 Severity: grave Dear Maintainer, dose3 currently fails to build from source in unstable. End of build log: [...] ocamlbuild -j 10 -no-links -cflags -warn-error,FPSXY rpm/rpm.otarget Finished, 0 targets (0 cached) in 00:00:00. + ocamlfind ocamlc -warn-error FPSXY -ccopt -I/usr/include/rpm -c rpm/librpm4_stubs.c rpm/librpm4_stubs.c: In function 'rpm_parse_paragraph': rpm/librpm4_stubs.c:221:18: error: 'RPMTAG_SUGGESTSNAME' undeclared (first use in this function) v = get_deps(h,RPMTAG_SUGGESTSNAME); ^ rpm/librpm4_stubs.c:221:18: note: each undeclared identifier is reported only once for each function it appears in rpm/librpm4_stubs.c:226:18: error: 'RPMTAG_ENHANCESNAME' undeclared (first use in this function) v = get_deps(h,RPMTAG_ENHANCESNAME); ^ Command exited with code 2. Compilation unsuccessful after building 15 targets (0 cached) in 00:00:02. Makefile:82: recipe for target '_build/doselibs/rpm.cma' failed make[2]: *** [_build/doselibs/rpm.cma] Error 10 make[2]: Leaving directory '/tmp/dose3-3.3' dh_auto_build: make -j1 returned exit code 2 debian/rules:36: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory '/tmp/dose3-3.3' debian/rules:5: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Cheers, -- Stéphane -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789181: apt-listbugs: should not list fixed bugs
Control: tags -1 - moreinfo Control: reassign -1 debbugs 2.4.1.1 On Fri, 19 Jun 2015 21:28:01 +0200 Vincent Lefevre wrote: On 2015-06-19 19:06:10 +0200, Francesco Poli wrote: I propose that this bug report is reassigned to debbugs, requesting a modification of the BTS to automatically join found and fixed version lists, when merging bugs and to keep those lists in sync among merged bugs. Of course, the documentation should be changed accordingly. I'll reassign this bug report myself, if you don't object. Please let me know what you think. I completely agree. Here we go! Dear debbugs maintainers, Vincent Lefevre reported a bug against apt-listbugs (which I maintain). During the conversation that followed, it was found out that the Debian BTS does not guarantee that merged bug reports share the same version tracking info. In other words, it is possible that two merged bugs have different found and fixed version lists. One example is bug #787364, which is merged with bug #787263. The former [1] is Merged with 787263 Found in versions systemd/220-1, systemd/220-2, systemd/215-18, systemd/220-4, systemd/220-5, systemd/219-10 Fixed in version systemd/220-3 while the latter [2] is Merged with 787364 Found in versions systemd/220-2, systemd/220-1 Fixed in version systemd/220-3 [1] https://bugs.debian.org/787364 [2] https://bugs.debian.org/787263 The result is that the BTS claims that one bug is fixed in current unstable (systemd/220-7), while the other bug is still present. Does this make sense? I mean, the two reports are merged with each other, hence they are considered as two duplicate reports for the same issue. This issue is either present or absent in a given version of the package under consideration: how come the BTS claims that this issue is present and absent at the same time in the same version? Unless I misunderstand something, this should not happen. If you agree that this is an inconsistency, I think that debbugs should guarantee that merged bug reports share the same found and fixed version lists. This could be done by automatically joining the found version lists of the bug reports being merged (just like what is done with tags). Then, any alteration performed to the found version list of one bug report should be automatically propagated to the other merged bug reports. The same should hold for fixed version lists. Obviously, the documentation [3] should be updated accordingly. [3] such as: https://www.debian.org/Bugs/server-control#merge Please fix this bug. Thanks for your time! Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgp7vtarB8lAk.pgp Description: PGP signature
Bug#789357: sphinxcontrib-seqdiag: New upstream version available
Source: sphinxcontrib-seqdiag Severity: wishlist Dear Maintainer, Please consider packaging the latest version, as of this writing 0.9.5 Thanks! -- tobi -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789256: Bug#680745: fixed in cmus 2.5.0-7
On 06/19/2015 01:26 PM, Alessio Treglia wrote: While it might not be a common feature, it is a feature none the less. One that relies on functionalities provided by a factually dead software; please get rid of it. Meanwhile I'll be demoting cmus's libroar dependency from Recommends to Suggests. If roaraudio's maintainers do not show willingness to cooperate, then we'll hand this to the TC and see. Great, sounds very reasonable to me and I fully agree on this idea! 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#788615: jessie-pu: package libgee-0.8/0.16.1-2
Control: tags -1 + pending On 2015-06-19 22:36, Michael Biebl wrote: Lintian complained about the -2~deb8u1 version, It used to also moan about backports versioning. I can't remember if it still does, but it should probably be more intelligent about stable version schemes. so I uploaded -1+deb8u1 (which happens to be identical to -2 aside from the first line in the changelog) Flagged for acceptance, thanks. btw, I'm guessing this isn't really what you wanted; apologies for not spotting it earlier: --- libgee-0.8-0.16.1/debian/gbp.conf 2014-10-15 18:39:14.0 + +++ libgee-0.8-0.16.1/debian/gbp.conf 2015-06-19 21:29:58.0 + @@ -1,5 +1,5 @@ [DEFAULT] -debian-branch = debian-0.8 +debian-branch = debian-wheezy 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#789374: missing license in debian/copyright
Package: freeciv Version: 2.5.0-2 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, data/flags/sikkim.svg seems to be licensed under CC 2.0 which is incompatible with DFSG. Please remove this file from the source tarball. data/flags/saxony.svg is licensed under CC 3.0. Please mention this in your debian/copyright. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788704: gnutls28: VIA PadLock accelerated AES-CBC segfaults
On 2015-06-18 Peter Lebbing pe...@digitalbrains.com wrote: [...] My suggested patch is almost exactly the same as commit 023156a from the GnuTLS Git[2]. I'd like to suggest backporting that commit to GnuTLS in jessie/stable, to not deviate unnecessarily from upstream and fix the problem. The message [1] also mentions a second commit which prevents calling the code with a length 0 in the first place, as it is a useless action. That commit is not necessary to fix this specific bug. [...] Hello Peter, thank you for the assistance. Would you mind testing the code I intend to try to get into stable? Source is available in the GIT repo (git://anonscm.debian.org/pkg-gnutls/gnutls.git branch gnutls28_jessie) binaries on https://people.debian.org/~ametzler/gnutls-jessie/. tia, cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' signature.asc Description: Digital signature
Bug#787525: WG: Bug#787525: upgrade-reports: hibernate-disk and Gnome
Below is the main part of my reply to Niels, I just figured I probably should have sent a copy here, so here it is...Thanks, Lothar Well as there's no menu entry in the Gnome desktop anymore, I just typed sudo hibernate-disk into a terminal window. Alternatively, I can lock the Gnome screen, hit Ctrl-Alt-F1 to get to a pure text screen, log in there, and type the same. Or better, I there type sudo hibernate-disk; exit. This is the only way I've found to get a password prompt on resume. However, I also found that, nearly as often as not, the hibernate itself crashes. When it says Writing image to disk. 0% it gets stuck at zero. Normally there it would count up to 100% and then switch the computer off. So, I'll have to switch off manually, and on switching back on, there's no resume but just a fresh boot. Should I file a separate bug report on this?
Bug#789118: No issues with clean upgrade
On Thu, 18 Jun 2015 21:19:20 +0400 George Hertz george...@gmail.com wrote: I've just upgraded to 3.16 on unstable, but restarted the system right after the update finished. No problems unlocking. Yeah, the problem only occurs with a gnome-shell which is already running during the upgrade. However, the problem also occurs when only locking the session after the upgrade has completed. One possible workaround after the upgrade is killall -HUP gnome-shell gnome-settings-daemon Sending SIGHUP to gnome-shell only is enough to be able to unlock the session, but gnome-settings-daemon also needs to be restarted, or some things such as keyboard shortcuts don't work properly in the new gnome-shell. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789187: moarvm: FTBFS on mipsel
Arturo Borrero Gonzalez arturo.borrero.g...@gmail.com writes: Package: moarvm Severity: serious Tags: upstream Justification: fails to build from source Dear maintainer, as you can see at buildd [x], moarvm FTBFS on mipsel. I've contacted upstream [x], and they say there is no support for mipsel in dyncall. Hello, It looks like mipsel issue may not be fixed soon, a possible integration of libffi or a new dyncall may render MoarVM usable on mipsel. Should we exclude mipsel from Architecture for the moment? NB: We have the same issue with S390. -- Daniel Dehennin Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF signature.asc Description: PGP signature
Bug#789351: please strip .comment sections from static libraries
Package: debhelper
Version: 9.20150507
Severity: wishlist
Tags: patch
File: /usr/bin/dh_strip
dh_strip passes --remove-section=.comment and --remove-section=.note to
strip for shared libraries and executables, but does not do so for
static libraries. The .comment sections usually contain the full gcc
version. When comparing two -dev packages built with different gcc
versions using debbindiff, the difference in .comment sections of static
libraries makes up for the bulk of output.
Is there a reason for why static libraries keep .comment and .note
sections? I could not find one. Removing them there as well, would
improve the debbindiff output and make packages a little bit smaller.
The gcc version is not recorded at all for packages without static
libraries and it will be recorded for all packages once .buildinfo files
are available to the archive.
The implementation of this change is easy:
--- a/dh_strip
+++ b/dh_strip
@@ -238,7 +238,8 @@
if (@static_libs) {
my $strip_help = qx{$strip 21};
- my @opts = ('--strip-debug');
+ my @opts = ('--strip-debug', '--remove-section=.comment',
+ '--remove-section=.note');
if (index($strip_help, '--enable-deterministic-archives') -1)
{
# NB: The short variant (-D) is broken in Jessie
# (binutils/2.25-3)
I am less sure about whether it also is harmless. Please consider this
change.
Helmut
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717536: current status
On Wed, 16 Apr 2014 12:19:57 +0530 Ritesh Raj Sarraf wrote: I see this bug tagged as pending. ... please explain the fix. Looks like you missed the explanation provided in the tag pending: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=9;bug=717536 # Source package in NEW: a href=http://packages.qa.debian.org/phoronix-test-suite;phoronix-test-suite/a; tags 717536 + pending Looking at NEW right now, the phoronix-test-suite package isn't there so I expect you'll need to ask the ftpteam who uploaded it there. BTW: Anibal's tag pending mails are sent automatically. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Hi, I will post the important part of one of my previous mails again: Is there a chance that you got slp installed? If yes. please try to remove it. On Jessie libslp gets pulled in automatically. I can't reproduce the bug on a fresh debian wheezy VM. And neither on a fresh debian jessie VM. Please attach system informations and a stacktrace to your bug on cmus. Wheezy does not install dnet/roar at all and Jessie installs libroar, libdnet and libslp. Both startup without problems. On Jessie i additionally get a warning about /etc/decnet.conf. Which is the info that decnet is not configured. I also ran two tests: 1. cmus Wheezy with https://archive.org/details/onclassical-quality-wav-audio-files-of-classical-music files: works nicely 2. cmus on Jessie with roaraudio as output: works as nicely as with the default soundserver I did not test on Debian 9 so far. I fear that I can't reproduce your issue. :( Kind Regards, Stephan signature.asc Description: Digital signature
Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Am 20.06.2015 um 12:42 schrieb John Paul Adrian Glaubitz: Stephan, seriously, you are missing the point. Absolutely _no_one_ needs ROAR audio with DECnet support except you and your buddy Patrick. I need roaraudio for myself? He is my buddy? I don't know him at all :o John: please stop writing e-mails like this.. If you desperately need ROAR audio in cmus, then you can rebuild it manually. Debian should not keep packages that are dead upstream, especially when it comes to network libraries. There is _always_ the risk of these being the source of RC bugs. This is defintily not the Debian packaging way: just some people want to use it: build it yourself I have fixed dozens of such packages during the Wheezy release phase with NMU uploads because the original maintainer was MIA and we really should try to avoid such problems in future releases. Thanks for fixing RC bugs, this is our job @ Debian :) -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#789351: [debhelper-devel] Bug#789351: please strip .comment sections from static libraries
Control: tags -1 moreinfo On 2015-06-20 09:51, Helmut Grohne wrote: Package: debhelper Version: 9.20150507 Severity: wishlist Tags: patch File: /usr/bin/dh_strip dh_strip passes --remove-section=.comment and --remove-section=.note to strip for shared libraries and executables, but does not do so for static libraries. The .comment sections usually contain the full gcc version. When comparing two -dev packages built with different gcc versions using debbindiff, the difference in .comment sections of static libraries makes up for the bulk of output. Is there a reason for why static libraries keep .comment and .note sections? I could not find one. Removing them there as well, would improve the debbindiff output and make packages a little bit smaller. The gcc version is not recorded at all for packages without static libraries and it will be recorded for all packages once .buildinfo files are available to the archive. The implementation of this change is easy: [...] I am less sure about whether it also is harmless. Please consider this change. Helmut [...] As discussed on #debian-devel, I am open to the change. However, it seems that (at least) OCaml is storing bytecode in the .comment section of its binaries (presumably including static libraries). I think we need a (cheap and fairly) reliable indicator of whether something is likely to be an OCaml (etc.) static lib, which is storing bytecode or other important data in these sections. Other languages that /might/ be doing something similar: * Haskell * Go * ... ? Thanks, ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 12:52 PM, Patrick Matthäi wrote: I need roaraudio for myself? He is my buddy? I don't know him at all :o John: please stop writing e-mails like this.. It's Adrian, not John, and I am just quoting Ron who certainly isn't making this stuff up. It has apparently always Stephan who came forward and ask for ROAR audio reactivation. If you desperately need ROAR audio in cmus, then you can rebuild it manually. Debian should not keep packages that are dead upstream, especially when it comes to network libraries. There is _always_ the risk of these being the source of RC bugs. This is defintily not the Debian packaging way: just some people want to use it: build it yourself It's definitely the Debian way when a certain package functionality that maybe a handful people need breaks other packages. Then it's your duty as a good Debian maintainer to get rid of the old and broken stuff. And there have been more than one bug report against ROAR that asked to drop the DECnet dependency and you keep ignoring them. I have fixed dozens of such packages during the Wheezy release phase with NMU uploads because the original maintainer was MIA and we really should try to avoid such problems in future releases. Thanks for fixing RC bugs, this is our job @ Debian :) You are missing the point. I don't have a problem with fixing RC bugs. I have a problem having to fix RC bugs in packages that no one really uses anymore. In case you have forgotten, the release process for Wheezy was dragged along endlessly because the amount of RC bugs would simply not go down. Among such bugs were gems like Iceweasel crashing on sparc or libsnack (used by aMSN) having a buffer overflow vulnerability. Do you really think it's justified to hold the release back because of such ancient software? They introduced automatic removal of packages affected by RC bugs for this very reason and the fact that DECnet is no longer maintained means that ROAR is permanently at risk being affected by RC bugs unless you think you can fix vulnerabilities or other serious bug in an ancient networking stack. 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 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhUhaAAoJEHQmOzf1tfkTZycQALLrt1ECi9I7T0CfD0FsE5ez YAs8s4oqQoByvjxHNNz1Gxvnjb/JS4Amr15FHZ4YjqYYv+/5j0zBoj8JLCUB/j/P OORjTagETPg3oYkej/XAiFH95eOoXf8BMPE5PvQkEAFfHv87nV7ou93yRWVEjZsh cFR1QDjot4ERwKnFqnDdyvvtfrtCfbzRrCrZ9u6jkWiqFi/wjL7bWLERweASfIWQ rn9sQ004uk2Y0euc5TXSoRcM4TuW4IWSUorfUbjC6CSiCu6MZZ1iSqVIe2ls4sFQ 5O/40GbWQbUhzzkBt+iPOD6lWqfn4BVEjwYTaq2XOAAFipBE8Lub7INcGLZ/aIb6 jjy8Sz/r9J5baJMiyXjiWR6LjgmbtE5JyCCU3J1WAzL8EpveLBsqmKXIspWcFoUX pvxGi8nqUoAkg2aJkpAoGbZuQo2Pt37K196ZNmvMgn4hG0ELqYLUD6z6jsIENOUj msmEPqvm1B7KwMIXMZmZhPAehPJmkRJ7SYJ0SpYzaXyjO+0bmgJ2VZlE90vrwStq 1b8p9CbGT7tH3zYv/qKAVn6DlDIeqh9Yzr2wC8Md9Y+rFiddCv1J+3vH9eczEP6D GbzyCK451bOooRCnq/22FyaGNhb7rEDrjLgeqVeMVeItMS2xPZ23AnqtHz5Q5mcx igChqM7E9jkKge2Ky4wl =2CmF -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 12:23 PM, Stephan Jauernick wrote: Is there a chance that you got slp installed? If yes. please try to remove it. On Jessie libslp gets pulled in automatically. Btw, how did you remove libslp1 without removing libroar2? glaubitz@ikarus:~$ aptitude why libslp1 i cmus Recommends libroar2 i A libroar2 Dependslibslp1 glaubitz@ikarus:~$ 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 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhUTdAAoJEHQmOzf1tfkTmFgQAIC5bLAKeh2yeRi1rNC4YoNE v5okdk/dkvWt+Cf17J0Bmp6AcwAut0Tmqu0FCn0lq6qVrZNKumVIZ1MFFC12OVMd 7WQ80iGOmw7NnmUpLSEB/X5Zfw26fAEZInldsseYURiE8Lsx9OJWRQlYwiRpKnAZ TVH574fVgUxx/FBetrMejRmPwTdkGczMzP0vD7t1PWUCSXtkENiIWW5a7ZU4y/23 XVD24ow8dxpLYXS1hyfuU/8j9RJfh0B98SxKjD8xy6cfXthkLhSxAvF6Ul7zuz6z Y5mbcVFPkO3TKdyLk0KWrA2e8RUX3vUDAFgzIprkmV0zJ4dmndiq5RRXp3A7F7Lz pxXUE6v5aKcDOScw9Lt2dUpBcfo3/aa+3+HzE25m4X6QWzx7BoHYOE+mLSko3NUg ewcZXz5zKnvwMkWugaX8qhORiAlBCI3TS7s7mwLH5fj4ImRcnjXkWOqS8gXGjjem v7Jxw1Cz2WtQdCyoM5u3eLTwIKKALKoJPl7s5Wn8JPshuqOC3FA65kI2IASeaKAr GH4Fet6Bcn2/tJn8w0P6DS+1nnwP7Nr0Do3G4ar+6LBtPT1+eSy8cP9/B+7RCAIc hybGHK+ufIIzc7WvxK/F4E7KlBeLWf6zjwIiJiPgC6MyRBWRA4a2i3myWVqdEoM0 X2X1fdGmETC7YU3Zsb9J =myFt -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787299: jessie-pu: package dovecot/1:2.2.13-12~deb8u1
Control: tags -1 + pending On 2015-06-14 15:00, Adam D. Barratt wrote: Control: tags -1 + confirmed On Mon, 2015-06-08 at 13:03 +0200, Santiago Vila wrote: On Mon, Jun 08, 2015 at 11:55:22AM +0100, Adam D. Barratt wrote: Having just had a very quick look at the log for #776094, it appears that the bug affects the package in unstable and is not yet fixed there. If that's not correct, then please fix the metadata - if it /is/ correct, then the bug must be fixed in unstable before we consider it for a stable update; that's been policy for as long as I remember and was re-iterated in the dda mail recently. The maintainers just forgot to write a Close statement in the changelog for version 2.2.18-1, but Bug #776094 is indeed fixed in unstable. It _still_ has no fixed versions. I've checked the source to confirm that it includes the fixes, but that doesn't excuse the BTS metadata being inaccurate. Please fix that and then feel free to go ahead with the upload. Uploaded and now flagged for acceptance. 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#769818: Re: Bug#769818: Bug#766118: lintian: False positive for “missing-license-paragraph-in-dep5-copyright”
Le Fri, Jun 19, 2015 at 03:55:46PM +0200, Martin Erik Werner a écrit : In newer versions of lintian, this warning has changed, so the following file: ### Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: td Source: http://example.com License: dog This is dog license Files: * Copyright: someone License: other This is other license ### Now reports W: cn source: dep5-file-paragraph-reference-header-paragraph dog (paragraph at line 7) Which is as far as I see still the same false positive. Hello everybody, I confirm that this tag is a false positive on several of my packages (for instance libbio-graphics-perl). Should this bug be re-assigned to lintian ? Have a nice week-end, Charles -- 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#788066: unattended-upgrades: Security updates not installed since last upgrade of unattended-upgrades package
On Wed, Jun 17, 2015 at 06:44AM -0700, Vagrant Cascadian wrote: Obviously individual users can manually upgrade unattended-upgrades manually via proposed-updates, but that leaves all the users expecting unattended-upgrades to be installing upgrades unattended without security updates. It may make sense to get unattended-upgrades updated through security updates, rather than waiting until a point release to propegate this fix... This does not work: The buggy version of unattended-unattended won't upgrade itself, even if the package comes through security updates. Johannes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787520: more detail
Hi!The regular behaviour of the network seems to be, that on startup/login, at first it works, and after a short time it doesn't anymore. Then, after a dhclient (see above), it works again and stays stable...Thanks, greets,Lothar
Bug#788533: mapnik: FTBFS: virtual memory exhausted: Cannot allocate memory (Was: Bug#756867: transition: gdal)
On 06/19/2015 06:35 PM, Jérémy Lal wrote:
2015-06-19 18:22 GMT+02:00 Emilio Pozuelo Monfort po...@debian.org:
(Moving the discussion to #788533; #756867 bcc'ed)
On 19/06/15 14:40, Sebastiaan Couwenberg wrote:
The mips* FTBFS are a recurring problem for the mapnik package, previous
builds were no different. I'll try to get it to build on a porterbox,
but I expect intervention from the buildd admins will be required like
last time to make sure only the buildds with the most resources try to
build mapnik.
See: https://bugs.debian.org/742149
https://bugs.debian.org/729121
I'm not sure there are buildds with more RAM. Note that the package failed
in
the exact same way on kfreebsd-i386, which has 3GB of RAM + 4GB of swap.
Since
all these arches are 32bits, more memory is probably not going to help.
Instead, perhaps you can make the build take less memory, e.g. by reducing
the
optimizations (-O1?) or using some flags such as the linker's
--no-keep-memory.
Mapnik 2.2 used to pass builds with some of those options, also with
removing
-ftemplate-depth-300.
That last option i restored with mapnik 3.0, to see what would happen with
upstream options,
since so much has changed in that project.
I'm preparing now an upload with that option removed.
The new uploaded didn't resolve the build failures, it still failed on
{hurd,kfreebsd}-i386 mips*.
Since it's a recurring problem on mips*, maybe exclude these
architectures and request removal of the package on mips*.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789370: php-services-weather: package description lines with wrong indentation are treated verbatim
Package: php-services-weather Severity: minor Hi! the last versions of the package description have all the lines, except for the first, starting with a space character. This causes those lines to be treated as verbatime text, they are not flowed to fit different display width and could be displayed in a different font. The result in the package page can be seen here: https://packages.debian.org/sid/php-services-weather I think those starting spaces should all be removed. As a minor side note, the last version included a change in the title changed from acts as an interface to various online weather-services to This class acts as an interface to various online weather-services I think the first version (or even the simplified interface to various online weather-services) is more adherent to what the debian Developer Reference suggests in https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis but that is definitely just a suggestion. Thanks, beatrice -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789371: RM: bins -- ROM; No upstream release since 2005
Package: ftp.debian.org Severity: normal The bins upstream package has no new release since 2005. The package is available for adoption since 2007 with no volunteer. See RFA bug #447393 Building the package now generates a Lintian error and I do not plan to invest time in fixing this package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789376: missing licenses in debian/copyright
Package: pcp Version: 3.10.4 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, lots of files in man/*, book/* and images/* are licensed under some version of CC. Please remove all files from the tarball that use a DFSG incompatible license and mention the others in your debian/copyright. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788716: listening_ip option causing parsing error
Hello Michael, On Mon, 15 Jun 2015 10:42:00 +0300 Michael Tokarev m...@tls.msk.ru wrote: 15.06.2015 01:58, Alexander Gerasiov wrote: Hello Michael, On Sun, 14 Jun 2015 16:49:23 +0300 Michael Tokarev m...@tls.msk.ru wrote: Package: minidlna Version: 1.1.2+dfsg-1.1+b3 Severity: important When specifying (uncommenting) option listening_ip in the config file, minidlnad says: parsing error file /etc/minidlna.conf line 70 : listening_ip=192.168.88.4 and ignores this line, listening to the whole 'net. This means that it is impossible to bind it to particular (internal) ip address, even after using the only option for this which is documented and appears to be available. Obviously this has security implications, due to both lack of the way to secure it and having too wide access when operator thinks it is secured. Mmm, this is not a bug in software anyway. And not a security issue. You're still free to protect yourself using iptables. This is a completely wrong approach. First we make something open much wider than needed, next we say there's a way to block the open door by using other means. The right approach is to not open the door in the first place where it isn't supposed to be open. This is philosophy =) From other point one can say, that unix way is to use many simple tools each solving it's simple task. Door to enter and guard dog to bite strangers =) I agree, that it would be better (in this particular case) to have working solution in minidlna, but it's absence (if it really has a place in) is not a security bug anyway. Is this a bug in documentation? - yes Is this bug closed in testing? - yes Should this bugreport be closed? - I think yes, feel free to prove your point. PS How do you see this report closed in right way? I think the functionality should be reimplemented. I don't think this bug should be colsed, instead maybe keep it as a wishlist item wishing that real measures to be implemented instead of relying on external blocks. When I submitted this bugreport I did't know upstream dropped this functionality, I thought it is just some minor prob in parsing the options. So ofcourse I didn't know it is just documentation bug in current package. Anyway, I think removing this functionality is inacceptable, because it is the wrong approach as described above. Look. There is a bug in 1.1.2: (Fixed in 1.1.4) #756169 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756169 -a option and listening_ip config parameter were replaced with -i interface Network interface to listen on. Can be specified more than once. network_interface Network interface(s) to bind to (e.g. eth0), comma delimited. This option can be specified more than once. If unspecified or empty, minidlnad binds to all the valid network interfaces (except loopback). But there are some questions with them. See #786929 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786929 http://sourceforge.net/p/minidlna/bugs/218/ (Still open as wishlist) In your bugreport you mix two different already reported problems. So I merge your bugreport into first one. -- Best regards, Alexander Gerasiov Contacts: e-mail: g...@cs.msu.su Homepage: http://gerasiov.net Skype: gerasiov PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/20/2015 12:23 PM, Stephan Jauernick wrote: Is there a chance that you got slp installed? If yes. please try to remove it. On Jessie libslp gets pulled in automatically. Oh, and btw, removing essential packages like OpenSLP is _not_ an option. That's basically crippling functionality just because the ROAR developers can't get with the time and drop a network protocol that hasn't seen any serious use for at least 15 years. OpenSLP is a useful thing to have on most desktops and most people don't want to uninstall it just because of cmus. 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 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhUR1AAoJEHQmOzf1tfkTBigP/iXJE6t1eTZKiWUa/vFr2RxF ehQQSeCXO1Zeaey5yJKyc29fKD3NqKA9mRc24TYlrCvKYeaI4DNuSS6AOHAyZfEX DkIaTux1kAFqKPsvqvlFANIr7LuRefW8KL8Z/7k5OO1c6eYZ2wvIUp3zuyHDLMPJ Hfs+EKUYtWZJknLIZ63qxdhYwpYTXyrbwN9lRgrRyKdfwYToJ9yN1utPxEmJCBDD G1WQVSR9XXXdxnbAVyXEu+I5pVjtK7FTwRfaoZLctccrHpLfBUC6yrJFBmjHG2rO R+933na9VRJhD3XTEDumMi7uUtwj/+K8H2phwEVgSB2apRGorzTHwcX//MhDe22p QMDMk+Nu2HYF1zBi/uUrZ408wsayGSkTbAKJxZmYLEh9a3WaA7aQc/WsykgDepMh gi6wxp1x/O71GF2dW+7Ve/F1r5queATFAmSfSVvRXnawiZQqCok7pr6if0+5Nnjj x2h08UQhFRZkoGirNy1M4I8hdvyuj9qN9jIYuXt7qHYFXdbHXvS8V1FAiz72KRaP Puu+sguNWtCZ5Ae6P8Bh3R8634+w0+Jzh841S8hXDNXdvTbHB0kYkWvewzJdDjIt 63DurYweB//qaNxB4CGRYqp4RVxkzxJk/ztQVf73z6kHaqymzkXOT0l4saQ8vAfd C0K9DFJjgPSCyAAVuV6f =ia/7 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789282: freehep-chartableconverter-plugin: switch B-D from libplexus-compiler-api-java to libplexus-compiler-java
On Fri, Jun 19, 2015 at 03:46:41PM +0200, Andreas Beckmann wrote: Source: freehep-chartableconverter-plugin Version: 2.0-6 Severity: serious Tags: stretch sid Your package Build-Depends: libplexus-compiler-api-java which was a transitional package that has now been removed. Please switch to libplexus-compiler-java instead. Hi Giovanni, fixed bug, rebuilt, pushed changes. Please upload it yourself or grant me DM upload rights. Also available at http://mentors.debian.net/debian/pool/main/f/freehep-chartableconverter-plugin/freehep-chartableconverter-plugin_2.0-7.dsc Thanks, -- G..e -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Hi Adrian, On Sat, Jun 20, 2015 at 12:47:57PM +0200, John Paul Adrian Glaubitz wrote: On 06/20/2015 12:23 PM, Stephan Jauernick wrote: Is there a chance that you got slp installed? If yes. please try to remove it. On Jessie libslp gets pulled in automatically. Btw, how did you remove libslp1 without removing libroar2? glaubitz@ikarus:~$ aptitude why libslp1 i cmus Recommends libroar2 i A libroar2 Dependslibslp1 glaubitz@ikarus:~$ Thanks for pointing that out. I was mistaken there. Sorry :( Can you maybe still provide a backtrace/strace log? Also are you running Debian 8 or Debian 9? 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 Kind Regards, Stephan signature.asc Description: Digital signature
Bug#789358: sphinxcontrib-nwdiag: Broken watchfile
Source: sphinxcontrib-nwdiag Followup-For: Bug #789358 -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) version=3 opts=uversionmangle=s/(rc|a|b|c)/~$1/ \ http://pypi.debian.net/sphinxcontrib-nwdiag/sphinxcontrib-nwdiag-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
Bug#789360: sphinxcontrib-seqdiag: Broken watchfile
Source: sphinxcontrib-seqdiag Followup-For: Bug #789360 Sorry, I did not realize that the homepage is misleading. Updated watch file attached. -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) version=3 opts=uversionmangle=s/(rc|a|b|c)/~$1/ \ http://pypi.debian.net/sphinxcontrib-seqdiag/sphinxcontrib-seqdiag-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
Bug#789189: jessie-pu: package lynx-cur/2.8.9dev1-2+deb8u1
Control: tags -1 + pending On 2015-06-18 19:51, Adam D. Barratt wrote: Control: tags -1 + confirmed On Thu, 2015-06-18 at 20:37 +0200, Andreas Metzler wrote: I would like to fix 784430 in jessie: * lynx-cur is using a buggy GnuTLS priority string. * After fixing GNUTLS-SA-2015-2 (a minor issue) GnuTLS is more strict when applying the priority string. Combining lynx-cur/jessie with a fixed GnuTLS therefore results in major SSL/TLS breakage. Please go ahead. Uploaded and flagged for acceptance. 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#766880: xscreensaver screensaver don't appear in mate-screensaver
On Sun, May 24, 2015 at 12:48 PM, Jonas Smedegaard wrote: Please, instead of whitelisting known relevant environments, blacklist known irrelevant ones. I.e. replace thise line: OnlyShowIn=XFCE; with (most likely, as a start) this: NotShowIn=KDE;GNOME; Jonas, Your suggestion makes sense, and it leaves new DE projects to tell us if they want to opt out. I am bit confused by your example though, because the current entry is OnlyShowIn=GNOME; Are you saying GNOME should be blacklisted? Currently these DE are recognized by fd.o: GNOME, KDE, LXDE, MATE, Razor, ROX, TDE, Unity, XFCE, Cinnamon, EDE, Old Does anyone know which of them should be blacklisted? I guess KDE, but I am not sure about the rest. If all the DE maintainers are on the debian-desktop ML, I can ask there. Regards, Tormod -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789375: sleepenh: Upstream location gitorious.org will shut down
Package: sleepenh Severity: normal Hi Nicolas, gitorious will shut down soon. Please move the upstream repository somewhere else. Thanks! -- tobi -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789260: libburn4: Incompatibility with Plextor PX-608CU burner
Hi, https://forums.opensuse.org/showthread.php/437135-Cannot-Burn-to-DVD-R-Disc-with-Plextor-PX-716SA This describes timeouts during the burn process. Not what you experience. I riddle about faio_wait_on_buffer in the report about cdrskin. Neither libburn nor cdrskin have it or use it as system call. I cannot find it in linux-source-3.16, but rather among the software of Joerg Schilling (cdrecord et.al.). https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=246647 This is an aborted SCSI command with an error code probably fabricated by the kernel. But the follow-up https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=246647#25 looks more similar to your problem. I'm thinking of recompiling the kernel to tweak it for my case. can you suggest any options that i can try to enable/disale? Regrettably no. Therefore my advise to ask kernel developers if you can find some and get them interested. Burn programs are userland tools and rely on flawless execution of ioctl(SG_IO). I can only thing about legacy scsi support. Ewww ... that's really old. And i am not aware that it ever applied to USB connected drives. I used it a decade ago for IDE connected drives. /dev/sg rather than /dev/sr. Finally it is supposed to use the same low level drivers as the /dev/sr driver. I'd expect that the problem sits at the low level. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789352: faumachine: Homepage broken
Package: faumachine Severity: minor Dear Maintainer, Seems that faumachine.org has been grabbed by some foreign party. Probably the right one would be: http://www3.informatik.uni-erlangen.de/Research/FAUmachine/ -- tobi -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789355: cpufrequtils: Should restrict architecture to linux-any
Source: cpufrequtils Version: 008-1 Dear Maintainer, Cpufrequtils does not seem to support kernels other than Linux, so it doesn't make any sense to build it on hurd-* and kfreebsd-* architectures. I think you need to set Architecture: linux-any (instead of just any) in debian/control. -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Bug#789360: sphinxcontrib-seqdiag: Broken watchfile
Source: sphinxcontrib-seqdiag Severity: normal Tags: patch Dear Maintainer, See attached patch. -- tobi -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) version=3 opts=uversionmangle=s/(rc|a|b|c)/~$1/ \ http://pypi.debian.net/seqdiag/seqdiag-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
Bug#664490: CClive man page translation (infrastructure, German translation)
Hello CClive developers, some time ago I wrote a patch to enable man page translations. You can find the information in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664490 I also translated the cclive(1) man page at that time (so it might be outdated by now) to German, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664491 It would be great if you could include the infrastructure. I would then of course update the German translation. For the record: cclive v0.7.16 for x86_64-pc-linux-gnu libquvi v0.4.1 for x86_64-pc-linux-gnu libquvi-scripts v0.4.21 If you need further information, do not hesitate to ask; please note, however, that I'm not an auto* expert. Greetings Helge On Tue, Jun 10, 2014 at 01:25:58PM +0200, Ansgar Burchardt wrote: Hi, On 06/08/2014 07:33, Helge Kreutzmann wrote: Hello Maintainer, On Sat, May 19, 2012 at 05:58:12PM +0200, Helge Kreutzmann wrote: is there a chance that the translated man page is included for Wheezy? and for Jessi? (If you need any help do not hesitate to contact me) Please submit the translation and related changes (so it actually gets used) upstream. Doing so now. -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Stephan, seriously, you are missing the point. Absolutely _no_one_ needs ROAR audio with DECnet support except you and your buddy Patrick. If you desperately need ROAR audio in cmus, then you can rebuild it manually. Debian should not keep packages that are dead upstream, especially when it comes to network libraries. There is _always_ the risk of these being the source of RC bugs. I have fixed dozens of such packages during the Wheezy release phase with NMU uploads because the original maintainer was MIA and we really should try to avoid such problems in future releases. Again, if you need ROAR audio in cmus, just rebuild the package yourself. It's not magic and would save you and us a lot of time and nerves. Thanks, 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 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVhUOxAAoJEHQmOzf1tfkTbAEQAJ/DawvDmQJcPQCNQm+MEd1F 0z1tFeGMRhxj/IXX+lkmbokX4R9gw1Zt50KwHSfb13UpP3rbc7VMRhbelcHUMUo2 FLFjb2z3jnfhh/aZ6kHKGWbW6gx7YzX9FDr4UeSoP0IzreFD+XFebp5/Ntoholr3 2I2q3EpOoCLbKhvjqG61jijNxn5eK+2vvXnzpbliwM0dWbmRrup3kzy+EyUBDNJy 4XNZ7u4WYilu7ILxKTkD07hq3dn35IY0PmvXn1jDeT85MfykprIO5cpZWPXg4GD8 4fbZkwNkK72H4VARUBH4Ot0uYCjwSwPKYc56V4djlBY3OdL/pNFLiLdrAG1Dv6A2 XRvRKd7QUSgq9qGZXLHaPPAbQ9IYEP4QNngb4tVCAvDtceoGQZPq1SytGfIr2ixF ZMRH2yVXsL8tP55+jsdSfC9OyBBCE9I32fZqW3bB0JZRIOh1mheVtc+klGBACn9r MeSEbW5Z4lV1SnrrkTcA1pmU5eI9V4qAGyUVD83Vwk7KXbZI/UOo9xeckT2c72Be 0WybQ1Zxi4G6cj+25FZccTHMZq93RScjGTpFgoQMk/z+vaBLVhtHnG/dXrDSBzzf +zdB1EiujXp3gLuF19EcZ62LGri310gJNszOXL1EWIcTkJlFQZwnOhNjBLMn3LtS QT/5hRB+1P8Akmubilwm =7wAC -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788066: unattended-upgrades: Security updates not installed since last upgrade of unattended-upgrades package
On Wed, Jun 17, 2015 at 10:22AM +0200, Michael Vogt wrote: I can confirm this, the fix of #783690 seems to be faulty. [...] Sorry for this, this is a brown-paperbag bug in my upload, I uploaded a new 0.83.3.2 to stable-proposed-updates [1] I tested the new version from stable-proposed-updates, and it solves the problem! Thanks, Johannes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789362: sphinxcontrib-actdiag: Wrong homepage?
Source: sphinxcontrib-actdiag Severity: normal Dear Maintainer, The homepage in d/control, http://blockdiag.com/en/, seems wrong: When going to the actdiag section and following to the pypi section, you end up on a site which has only a version of 0.5.4 (Debian is now at 0.8.0) PKG-INFO refers to http://pypi.python.org/pypi/sphinxcontrib-actdiag which seems more correct. At least it has version which matches the Debian version. (Well currently at 0.8.3) Tobi -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756563: cmake fltk-config
Control: tags -1 - moreinfo unreproducible On 2014-07-31 00:48:14, Dimitri John Ledkov wrote: However, before even falling back to fltk-config, the cmake shipped modules should be able to find /usr/lib/fltk/*.cmake modules include them direct and define as found both shared and static variants of all libs. Matthias, can you point me at the example of a package that uses cmake FindFLTK module and ends up with a static fltk instead of the _SHARED variant? yoshimi 1.3.5-1 for example is now statically linked against fltk because of that. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Am 20.06.2015 um 13:02 schrieb John Paul Adrian Glaubitz: On 06/20/2015 12:52 PM, Patrick Matthäi wrote: I need roaraudio for myself? He is my buddy? I don't know him at all :o John: please stop writing e-mails like this.. It's Adrian, not John, and I am just quoting Ron who certainly isn't making this stuff up. It has apparently always Stephan who came forward and ask for ROAR audio reactivation. No, it was your e-mail. To quote it again: except you and your buddy Patrick. Stop it, seriously.. If you desperately need ROAR audio in cmus, then you can rebuild it manually. Debian should not keep packages that are dead upstream, especially when it comes to network libraries. There is _always_ the risk of these being the source of RC bugs. This is defintily not the Debian packaging way: just some people want to use it: build it yourself It's definitely the Debian way when a certain package functionality that maybe a handful people need breaks other packages. Then it's your duty as a good Debian maintainer to get rid of the old and broken stuff. And there have been more than one bug report against ROAR that asked to drop the DECnet dependency and you keep ignoring them. This is not true. Please attach links/emails where I ignored bug reports/requests (on other channels). I have fixed dozens of such packages during the Wheezy release phase with NMU uploads because the original maintainer was MIA and we really should try to avoid such problems in future releases. Thanks for fixing RC bugs, this is our job @ Debian :) You are missing the point. I don't have a problem with fixing RC bugs. I have a problem having to fix RC bugs in packages that no one really uses anymore. In case you have forgotten, the release process for Wheezy was dragged along endlessly because the amount of RC bugs would simply not go down. Among such bugs were gems like Iceweasel crashing on sparc or libsnack (used by aMSN) having a buffer overflow vulnerability. Do you really think it's justified to hold the release back because of such ancient software? OK, so lets drop iceweasel? This is definitly offtopic here They introduced automatic removal of packages affected by RC bugs for this very reason and the fact that DECnet is no longer maintained means that ROAR is permanently at risk being affected by RC bugs unless you think you can fix vulnerabilities or other serious bug in an ancient networking stack. Lets drop package XYZ: it may have got issues we didn't discovered, yet.. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#789359: sphinxcontrib-blockdiag: Broken watchfile
Source: sphinxcontrib-blockdiag Followup-For: Bug #789359 Sorry, I did not relaize that the links on the homepage are wrong. (Please update d/control homepage as well) New watchfile attached. -- tobi -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) version=3 opts=uversionmangle=s/(rc|a|b|c)/~$1/ \ http://pypi.debian.net/sphinxcontrib-blockdiag/sphinxcontrib-blockdiag-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
Bug#789369: iostream uninitialized data
Package: libstdc++6
Version: 5.1.1-11
richard@deodand:~/junk$ cat t.cc
#include iostream
int main() {
std::cout std::hex;
return 0;
}
richard@deodand:~/junk$ clang++-3.6 -fsanitize=undefined -O0
-fno-optimize-sibling-calls -fno-omit-frame-pointer -g -o t t.cc
richard@deodand:~/junk$ ./t
/usr/bin/../lib/gcc/i586-linux-gnu/5.1.1/../../../../include/c++/5.1.1/bits/ios_base.h:102:24:
runtime error: load of value 4294967221, which is not a valid value for
type 'std::_Ios_Fmtflags'
/usr/bin/../lib/gcc/i586-linux-gnu/5.1.1/../../../../include/c++/5.1.1/bits/ios_base.h:82:67:
runtime error: load of value 4294967221, which is not a valid value for
type 'std::_Ios_Fmtflags'
As far as I can see the problem here is that ios_base::_M_flags is never
initialized.
ii clang-3.6 1:3.6.1-1i386 C, C++ and Objective-C
ttfn/rjk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739514: Triaging taskwarrier
Control: fixed -1 2.4.1+dfsg-1 According upstream fixed in 2.4.0 -- see forwarded link -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789373: missing license in debian/copyright
Package: wesnoth Version: 1:1.13.0-1 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing Apache-2 license of: DroidSans*.ttf to your debian/copyright. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789372: polari: silently fails to add new connections
Package: polari Version: 3.16.1-1 Severity: serious Tags: upstream Dear Maintainer, with this new version, the program is unable to add new connections, failing with the following message in a terminal: | (org.gnome.Polari:9510): Gjs-WARNING **: JS ERROR: TypeError: | this._serverEntry is undefined | ConnectionDetails._init@resource:///org/gnome/Polari/js/connections.js:190 | wrapper@resource:///org/gnome/gjs/modules/lang.js:169 | JoinDialog._createWidget@resource:///org/gnome/Polari/js/joinDialog.js:73 | wrapper@resource:///org/gnome/gjs/modules/lang.js:169 | JoinDialog._init@resource:///org/gnome/Polari/js/joinDialog.js:22 | wrapper@resource:///org/gnome/gjs/modules/lang.js:169 | _Base.prototype._construct@resource:///org/gnome/gjs/modules/lang.js:110 | Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/lang.js:204 | MainWindow.showJoinRoomDialog@resource:///org/gnome/Polari/js/mainWindow.js:233 | wrapper@resource:///org/gnome/gjs/modules/lang.js:169 | Application._onShowJoinDialog@resource:///org/gnome/Polari/js/application.js:187 | wrapper@resource:///org/gnome/gjs/modules/lang.js:169 | main@resource:///org/gnome/Polari/js/main.js:17 | run@resource:///org/gnome/gjs/modules/package.js:192 | start@resource:///org/gnome/gjs/modules/package.js:176 | @/usr/bin/polari:5 Upgrading the gjs package to the version in experimental (as you can see in my package list installed below) fixed the issue. Marking severity to serious to prevent the package to migrate, before the problem is fixed (mainly, upstream). Cheers. -- System Information: Debian Release: stretch/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages polari depends on: ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii gir1.2-glib-2.0 1.44.0-1+b1 ii gir1.2-gtk-3.0 3.16.4-2 ii gir1.2-soup-2.4 2.50.0-2 ii gir1.2-telepathyglib-0.120.24.1-1 ii gir1.2-telepathylogger-0.2 0.8.1-1 ii gjs 1.43.3-1 ii libc62.19-18 ii libglib2.0-0 2.44.1-1 ii libgtk-3-0 3.16.4-2 ii libtelepathy-glib0 0.24.1-1 ii telepathy-idle 0.2.0-2 ii telepathy-logger 0.8.1-1 ii telepathy-mission-control-5 1:5.16.3-1 polari recommends no packages. polari suggests no packages. -- no debconf information -- Matteo F. Vescovi || Debian Developer GnuPG KeyID: 4096R/0x8062398983B2CF7A -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789377: www.debian.org: update browsers section in content negotiation page (cn.wml)
Package: www.debian.org
Severity: minor
Tags: patch
I think the browsers section ('Setting the preferred language in a
browser') of https://www.debian.org/intro/cn.en.html can be improved
by:
- removing old browsers (Netscape 3 and 4, old versions of Firefox).
- renaming Chromium to Chrome and Chromium
- removing the workaround for a bug in Konqueror (bug fixed in 2008)
- sorting browsers alphabetically
- adding W3C page about content negotiation, as suggested by pabs
There is a patch attached to this message to do it.
--
Stéphane
Index: cn.wml
===
RCS file: /cvs/webwml/webwml/english/intro/cn.wml,v
retrieving revision 1.90
diff -u -r1.90 cn.wml
--- cn.wml 15 Aug 2014 14:36:25 - 1.90
+++ cn.wml 20 Jun 2015 12:46:58 -
@@ -150,21 +150,33 @@
dl
- dtstrongtoc-add-entry name=mozillaMozilla/toc-add-entry /
- toc-add-entry name=netscapeNetscape 4.x/toc-add-entry and later
- versions/strong/dt
+ dtstrongtoc-add-entry name=chromiumChrome and
Chromium/toc-add-entry/strong/dt
+ dd
+ preCustomize and control Chromium -gt; Settings -gt; Show advanced
settings -gt; Languages -gt; Language and input settings/pre
+ /dd
+
+ dtstrongtoc-add-entry name=elinksELinks/toc-add-entry/strong/dt
+ ddYou can set up the default interface language at:
+ pre
+Setup -gt; Language
+ /pre
+ This will also change the requested language from web sites.
+ You can change this behaviour and fine-tune the accepted languages HTTP
+ variable at:
+ pre
+Setup -gt; Options manager -gt; Protocols -gt; HTTP
+ /pre
+ /dd
+
+ dtstrongtoc-add-entry
name=epiphanyEpiphany/toc-add-entry/strong/dt
dd
pre
- Edit -gt; Preferences -gt; Navigator -gt; Languages
+ Edit -gt; Preferences -gt; Language -gt; Languages
/pre
- Note: with Netscape 4.x you need to make sure you select the
- language from the available choices. A number of people
- reported problems because they typed in the language by hand.
/dd
- dtstrongtoc-add-entry name=mozillafirefoxMozilla
Firefox/toc-add-entry/strong/dt
+ dtstrongtoc-add-entry
name=mozillafirefoxFirefox/toc-add-entry/strong/dt
dd
- Version 3.0 and newer:br /
Linux:
pre
Edit -gt; Preferences -gt; Content -gt; Languages -gt; Choose...
@@ -177,31 +189,27 @@
pre
Firefox -gt; Preferences -gt; Content -gt; Languages -gt; Choose...
/pre
+ /dd
- br /
- Version 1.5 and newer:br /
- Linux:
- pre
- Edit -gt; Preferences -gt; Advanced -gt; General -gt; Edit Languages
- /pre
- Windows:
+ dtstrongtoc-add-entry name=galeonGaleon/toc-add-entry/strong/dt
+ dd
pre
- Tools -gt; Options -gt; Advanced -gt; General -gt; Edit Languages
+ Settings -gt; Preferences -gt; Rendering -gt; Languages
/pre
+ /dd
- br /
- Version 0.9 and newer:br /
- Linux:
- pre
- Edit -gt; Preferences -gt; General -gt; Languages
- /pre
- Windows:
+ dtstrongtoc-add-entry
name=ibrowseIBrowse/toc-add-entry/strong/dt
+ ddGo into Preferences, then Settings, then Network. Under Accept
+ language it will probably show a * by default. If you click on the
+ Locale button it should add your preferred language. If not, you
+ can enter it manually. After that, click OK.
+ /dd
+
+ dtstrongtoc-add-entry name=icabiCab/toc-add-entry/strong/dt
+ dd
pre
- Tools -gt; Options -gt; General -gt; Languages
+ Edit -gt; Preferences -gt; Browser -gt; Fonts,Languages
/pre
-
- In older versions you have to go to kbdabout:config/kbd and change
- the value of kbdintl.accept_languages/kbd.
/dd
dtstrongtoc-add-entry
name=iceweaselIceweasel/toc-add-entry/strong/dt
@@ -224,16 +232,26 @@
/pre
/dd
- dtstrongtoc-add-entry name=piePocket Internet
Explorer/toc-add-entry/strong/dt
+ dtstrongtoc-add-entry
name=konquerorKonqueror/toc-add-entry/strong/dt
dd
- # Windows Mobile 2003/2003SE/5.0
+ Edit your
+ kbd~/.kde/share/config/kio_httprc/kbd file to include a line like the
+ following:
pre
- Create the string registry key qAcceptLanguage/q in
- HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\International\\
- with value qfr; q=1.0, en; q=0.5/q (without quotes).
+ Languages=fr;q=1.0, en;q=0.5
/pre
/dd
+ dtstrongtoc-add-entry name=lynxLynx/toc-add-entry/strong/dt
+ ddYou can either edit the kbdpreferred_language/kbd variable in your
+ kbd.lynxrc/kbd or set it using the 'O' command while in lynx.
+
+ pFor example, use the following line in your kbd.lynxrc/kbd/p
+
+ pre
+ preferred_language=fr; q=1.0, en; q=0.5
+ /pre
+ /dd
dtstrongtoc-add-entry name=operaOpera/toc-add-entry/strong/dt
ddMost versions:
@@ -254,45 +272,27 @@
/pre
/dd
- dtstrongtoc-add-entry name=galeonGaleon/toc-add-entry/strong/dt
- dd
- pre
- Settings -gt; Preferences -gt; Rendering -gt; Languages
- /pre
- /dd
-
- dtstrongtoc-add-entry
name=epiphanyEpiphany/toc-add-entry/strong/dt
+ dtstrongtoc-add-entry
Bug#788471: elasticsearch: CVE-2015-4165: unspecified arbitrary files modification vulnerability
Hi Hilko On Fri, Jun 12, 2015 at 01:45:15PM +0200, Salvatore Bonaccorso wrote: Hi Hilko, On Fri, Jun 12, 2015 at 01:30:28PM +0200, Hilko Bengen wrote: Control: tags -1 moreinfo * Salvatore Bonaccorso: Source: elasticsearch Version: 1.0.3+dfsg-5 Severity: grave Tags: security upstream fixed-upstream Where exactly has it been fixed upstream? A git coommit id would be helpful. I haven't a specific commit. The only information I had so far is that upstream claims that affected versions are all 1.0.0 up to 1.5.2 and the issue is fixed in 1.6.0: See https://www.elastic.co/community/security/ Did you had a chance to get more details on it? 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#789350: javahelper: javadoc fails with error - option -locale must be first on the command line
Package: javahelper Version: 0.51 Severity: serious After the new upload, a lintian test case fails with: jh_build --javacopts='-target 1.7' --javacopts='-source 1.7' find src -name *.java -and -type f -print0 | xargs -0 /usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.testa -d debian/_jh_build.testa -target 1.7 -source 1.7 find src -name *.java -and -type f -print0 | xargs -0 /usr/lib/jvm/default-java/bin/javadoc -classpath :debian/_jh_build.testa -d debian/_jh_build.javadoc/api -quiet -locale en_US -notimestamp -source 1.5 javadoc: error - option -locale must be first on the command line. listing of javadoc usage/options This is an unforunate regression that is very likely to break existing packages that relies on jh_build to produce javadoc. Thanks, ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777908: icedove: ftbfs with GCC-5
tags 777908 pending thanks Hello Matthias, On Thu, Feb 12, 2015 at 10:32:28AM +, Matthias Klose wrote: Package: src:icedove Version: 31.4.0-2 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/icedove_31.4.0-2_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html a rebuild yesterday with a prepared new version 38.0.1 for unstable was successful. This version isn't uploaded right now but should be gone into unstable within the next days and will close this report. Until then I set the pending tag to your report. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789381: libpoe-api-peek-perl: FTBFS with perl 5.22: test failures
Source: libpoe-api-peek-perl Version: 2.2000-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch upstream Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=103803 This package FTBFS with perl 5.22 (currently in experimental), since perl 5.22 is not supported by the package: Test Summary Report --- t/01-session.t (Wstat: 11 Tests: 39 Failed: 0) Non-zero wait status: 11 Parse errors: Bad plan. You planned 52 tests but ran 39. t/07-kernel.t (Wstat: 11 Tests: 3 Failed: 0) Non-zero wait status: 11 Parse errors: Bad plan. You planned 11 tests but ran 3. Files=11, Tests=147, 2 wallclock secs ( 0.07 usr 0.06 sys + 1.08 cusr 0.18 csys = 1.39 CPU) Result: FAIL This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789383: libparse-netstat-perl: FTBFS with perl 5.22 (Module::Build)
Source: libparse-netstat-perl Version: 0.4-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch This package FTBFS with perl 5.22 (currently in experimental), since Module::Build has been removed from perl core: perl Build.PL --installdirs vendor Can't locate Module/Build.pm in @INC (you may need to install the Module::Build module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.0 /u sr/local/share/perl/5.22.0 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at Build.PL line 5. BEGIN failed--compilation aborted at Build.PL line 5. dh_auto_configure: perl Build.PL --installdirs vendor returned exit code 2 make: *** [build] Error 2 The fix is to add a build dependency on libmodule-build-perl. This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789380: libpoe-component-schedule-perl: FTBFS with perl 5.22 (Module::Build)
Source: libpoe-component-schedule-perl Version: 0.95-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch This package FTBFS with perl 5.22 (currently in experimental), since Module::Build has been removed from perl core: perl Build.PL --installdirs vendor Can't locate Module/Build.pm in @INC (you may need to install the Module::Build module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.0 /u sr/local/share/perl/5.22.0 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at Build.PL line 7. BEGIN failed--compilation aborted at Build.PL line 7. dh_auto_configure: perl Build.PL --installdirs vendor returned exit code 2 The fix is to add a build dependency on libmodule-build-perl. This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789384: libparse-errorstring-perl-perl: FTBFS with perl 5.22: test failure
Source: libparse-errorstring-perl-perl Version: 0.21-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch upstream patch Forwarded: https://github.com/PadreIDE/Parse-ErrorString-Perl/issues/1 This package FTBFS with perl 5.22 (currently in experimental): # Failed test 'diagnostics' # at t/04-perldiag.t line 64. # +---+---+---+- + # | Ln|Got| Ln|Expected | # +---+---+---+- + # * 1|undef * 1|'(F) You\'ve said use strict or use strict vars, which in dicates * # | | * 2|that all variables must either be lexically scoped (using my or state), * # | | * 3|declared beforehand using our, or explicitly qualified to s ay * # | | * 4|which package the global variable is in (using ::).' * # +---+---+---+- + # Failed test 'type' # at t/04-perldiag.t line 65. # got: undef # expected: 'F' # Failed test 'error type' # at t/04-perldiag.t line 66. # got: undef # expected: 'fatal error' # Looks like you failed 3 tests of 4. t/04-perldiag.t ... 1..4 ok 1 - message not ok 2 - diagnostics not ok 3 - type not ok 4 - error type Dubious, test returned 3 (wstat 768, 0x300) Failed 3/4 subtests t/05-stacktrace.t . There is a patch on the GH issue. This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789385: libosm-gary68-perl: FTBFS with perl 5.22 (Module::Build)
Source: libosm-gary68-perl Version: 0.0~svn26727-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch This package FTBFS with perl 5.22 (currently in experimental), since Module::Build has been removed from perl core: perl Build.PL --installdirs vendor Can't locate Module/Build.pm in @INC (you may need to install the Module::Build module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.0 /u sr/local/share/perl/5.22.0 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at Build.PL line 1. BEGIN failed--compilation aborted at Build.PL line 1. dh_auto_configure: perl Build.PL --installdirs vendor returned exit code 2 The fix is to add a build dependency on libmodule-build-perl. This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789382: libperl-apireference-perl: FTBFS with perl 5.22: not supported
Source: libperl-apireference-perl
Version: 0.19-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition
Tags: sid stretch upstream
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=105391
This package FTBFS with perl 5.22 (currently in experimental), since
perl 5.22 is not supported by the package:
echo Current Perl is `perl -MConfig -we'printf(%d_%03d_%03d.pm, $Config{PERL_R
EVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
Current Perl is 5_022_000.pm
test -f lib/Perl/APIReference/V`perl -MConfig -we'printf(%d_%03d_%03d.pm,
$Config{PERL_REVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
make[1]: *** [regenerated-stamp] Error 1
This bug will become release critical nearer the time of the perl 5.22
migration, expected during the (northern hemisphere) summer.
Cheers,
Dominic.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789386: liborlite-statistics-perl: FTBFS with perl 5.22: perl-modules dep
Source: liborlite-statistics-perl Version: 0.03-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch This package FTBFS with perl 5.22 (currently in experimental) since it depends on perl-modules, contrary to the package description, and this package is gone in perl 5.22. This can just be dropped altogether given the existing unversioned dependency on perl, and the length of time that = 5.10 has been in the archive: perl-modules (= 5.10) | libpod-simple-perl (= 3.07) This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789387: libogg-vorbis-header-pureperl-perl: FTBFS with perl 5.22: test failure
Source: libogg-vorbis-header-pureperl-perl Version: 1.0-3 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch upstream patch Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=96578 This package FTBFS with perl 5.22 (currently in experimental): Can't use an array as a reference at test.pl line 22. # Looks like you planned 9 tests but ran 1. # Looks like your test exited with 255 just after 1. There is a patch on the RT ticket. This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788704: Bug#766093: Multiple assertion failures
Control: reopen 788704 Control: notfixed 788704 2014.0.0+dfsg-4 On 2015-06-20 Andreas Metzler ametz...@bebt.de wrote: Version: 2014.0.0+dfsg-4 On 2015-03-04 Andreas Metzler ametz...@bebt.de wrote: On 2015-03-03 Jérôme jer...@jolimont.fr wrote: [...] Tested at home and well, I wouldn't say I understand why, but it works. With the dfsg-4, none of the two assert warning I was mentioning occurs. Thanks for checking, I have pushed the fix to unstable. ... and have promptly forgotten to close this bug-report, doing so now. Sorry, typo in bugnumber, reopening again. cu Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751880: boost1.5x: outdated embedded data copy: unicode-data
On Tue, Jun 17, 2014 at 08:46:55PM +0800, Paul Wise wrote: Unicode 7.0 was recently released and unicode-data 7.0-1 was uploaded. Unicode 8.0 was recently released and unicode-data 8.0-1 was uploaded. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#789212: libapache2-mod-passenger fails to install on post-install script.
Control: tag -1 + moreinfo Hello Rovanion, thanks for reporting this problem. On Thu, Jun 18, 2015 at 11:48:49PM +0200, Rovanion Luckey wrote: Package: libapache2-mod-passenger Version: 4.0.53-1 Severity: normal Dear Maintainer, * What led up to the situation? I was upgrading our puppetmaster/foreman server from Debian 7 to 8. The upgarde didn't end up well so I ended up purging everything puppet, foreman and apache. After installing these again and running foreman-installer, as described here: http://theforeman.org/manuals/1.8/quickstart_guide.html#QuickstartGuide, I got the following error: Setting up libapache2-mod-passenger (4.0.53-1) ... dpkg: error processing package libapache2-mod-passenger (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: libapache2-mod-passenger E: Sub-process /usr/bin/dpkg returned an error code (1) Can you scroll up on that log and look for the actual error that happened during the postinst for libapache2-mod-passenger? It might still be in /var/log/apt/term.log -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#789290: e2fsprogs: e2fsck claims to have fixed fs, but a second run finds all the same problems
It could be caused by a hardware problem, or if it's a RAID array, if the RAID array is out of sync, it's possible for two subsequent reads to return something else. It's RAID0, which I *believe* can't get out of sync, but there is much I do not understand about RAID. Can you take the two .gz files and reconstruct a file system on some other system with a known-bug disk, and then try running e2fsck on the the image? e2fsck successfully repairs both the skeleton image and the complete partition image when they are on a known-good disk. Here's some more detail about the partition. The Partition does not start on physical sector boundary thing might be relevant. (I can't say I understand how that can even happen, though.) md127 : active raid0 sde3[1] sdd3[0] 556720128 blocks super 1.2 512k chunks # sfdisk -Vl /dev/md127 Disk /dev/md127: 531 GiB, 570081411072 bytes, 1113440256 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 524288 bytes / 1048576 bytes Disklabel type: dos Disk identifier: 0x2c9d8483 Device Boot StartEnd Sectors Size Id Type /dev/md127p1 63 128005919 12800585761G 83 Linux /dev/md127p2 128005920 1113433019 985427100 469.9G 83 Linux Partition 1 does not start on physical sector boundary. Partition 2 does not start on physical sector boundary. Remaining 7236 unallocated 512-byte sectors. # sfdisk -Vl /dev/sdd Disk /dev/sdd: 298.1 GiB, 320072933376 bytes, 625142448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x3ce15391 Device BootStart End Sectors Size Id Type /dev/sdd1 *2048 1050623 1048576 512M 83 Linux /dev/sdd21050624 68159487 6710886432G 82 Linux swap / Solaris /dev/sdd3 68159488 625142447 556982960 265.6G fd Linux raid autodetect # sfdisk -Vl /dev/sde Disk /dev/sde: 298.1 GiB, 320072933376 bytes, 625142448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x75d309b0 Device BootStart End Sectors Size Id Type /dev/sde1 2048 1050623 1048576 512M 83 Linux /dev/sde21050624 68159487 6710886432G 82 Linux swap / Solaris /dev/sde3 68159488 625142447 556982960 265.6G fd Linux raid autodetect -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789404: pbuilder: insecure use of /tmp
Source: pbuilder Version: 0.215+nmu3 Severity: grave Tags: security pbuilder builds the package in $BUILDPLACE/tmp/buildd. But $BUILDPLACE/tmp is normally world-writable, and pbuilder doesn't fail if the buildd direcory already exists: mkdir -p $BUILDPLACE/tmp/buildd There's a race window between unpacking base.tgz and the mkdir call when malicious local user could create their own $BUILDPLACE/tmp/buildd. Owning the buildd directory would let them tamper with the build process. Alternatively, the attacker could exploit #789401 to plant tmp/buildd directly in base.tgz. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pbuilder depends on: ii coreutils 8.23-4 ii debconf [debconf-2.0] 1.5.56 ii debianutils4.5.1 ii debootstrap1.0.70 ii dpkg-dev 1.18.1 ii wget 1.16.3-2+b2 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789405: qdjango: please make the build reproducible
Source: qdjango Version: 0.5.0-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps Hi, While working on the “reproducible builds” effort [1], we have noticed that qdjango could not be built reproducibly. The attached patch changes the value of HTML_TIMESTAMP in upstream's doxyfile from YES to NO. Once applied qdjango can be built reproducibly in our current experimental framework. Patching upstream doxyfile is necessary in this case because of the following reasons: 1. Even though the doxygen upstream changed the default value of HTML_TIMESTAMP from YES to NO this does not affect this package because the value of HTML_TIMESTAMP is explicitly set to YES. 2. Upstream's doxyfiles cannot reliably be modified to change the value of HTML_TIMESTAMP during the build process because dh_doxygen is only run after the build already completed and even adding a new dh command cannot solve the problem because there exists no sane and reliable solution to detect the file which will be used as the configuration file for doxygen (it is not always called doxyfile). 3. In case of this source package a patch against upstream is necessary in contrast to a patch against Debian rules because this source package does not call doxygen in debian/rules. Please also consider forwarding this patch upstream. Cheers! akira [1]: https://wiki.debian.org/ReproducibleBuilds Description: Set HTML_TIMESTAMP from YES to NO to make package reproducible --- qdjango-0.5.0.orig/doc/Doxyfile +++ qdjango-0.5.0/doc/Doxyfile @@ -806,7 +806,7 @@ HTML_STYLESHEET= # page will contain the date and time when the page was generated. Setting # this to NO can help when comparing the output of multiple runs. -HTML_TIMESTAMP = YES +HTML_TIMESTAMP = NO # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, # files or namespaces will be aligned in HTML using tables. If set to
Bug#789408: lilo: mkrescue fails if device mapper is used
Package: lilo Version: 1:23.2-4 Severity: normal Dear Maintainer, a bootable rescue CD is required, but mkrescue / lilo failed. I tried using lilo version 24.1, but there is the same problem. mkrescue --iso --size HD --debug Caching device /dev/root (0xFE00) Fatal: device-mapper: only linear boot device supported brw-rw---T 1 root disk 254, 0 Jun 20 11:14 /dev/dm-0 lrwxrwxrwx 1 root root 4 Jun 20 11:14 /dev/root - dm-0 But it is the root device and not the boot device. Lilo installed in the MBR of the hard disk works without problems. -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lilo depends on: ii debconf [debconf-2.0] 1.5.49 ii dpkg 1.16.16 ii libc6 2.13-38+deb7u8 ii libdevmapper1.02.1 2:1.02.74-8 ii perl 5.14.2-21+deb7u2 lilo recommends no packages. Versions of packages lilo suggests: pn lilo-doc none -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789290: e2fsprogs: e2fsck claims to have fixed fs, but a second run finds all the same problems
On Sat, Jun 20, 2015 at 11:35 AM, Theodore Ts'o ty...@mit.edu wrote:
On Sat, Jun 20, 2015 at 11:05:31AM -0400, Zack Weinberg wrote:
e2fsck successfully repairs both the skeleton image and the complete
partition image when they are on a known-good disk.
OK, so this is a storage device issue. I'd be taking a very jaundiced
look at the reliability/correctness of your drives.
It could be that they have a firmware bug in how they handle 512e
emulation. (See below.) Or maybe one or more is starting to go bad.
(Not all drive failures are predicted by S.M.A.R.T. In fact, only
about 50-66% of drive failures are predicted by SMART. Think about
that the next time you are tempted to skimp on backups. :-)
Either is possible. These are an identical pair of Western Digital
drives and they're about five years old. They *claim* to have
512-byte physical sectors (per hdparm -I -- full dump at the bottom)
but I would totally believe they are faking that. Also, the
computer's power supply failed catastrophically in the middle of a
system upgrade, which is how the root filesystem got so very
corrupted. That could certainly have caused physical damage. (The
drives are currently attached to a different computer for data
recovery.)
The fsck behavior I originally reported continues to be 100%
reproducible on the physical partition. There are no hard errors in
the SMART logs for either drive. (After I'm done copying data off the
/home partition, which was not corrupted, I will run extended
selftests.) Before the catastrophic power supply failure, there were
no problems writing data to either filesystem inside the RAID array.
And the outer partitions are properly aligned. Putting all of those
things together, I wonder whether this might be a bug in direct (not
filesystem) access to the block devices for misaligned partitions
within MD-RAID(0).
Is it possible for you to construct a similarly-misaligned partition
within an MD-RAID0 array, unpack the skeleton image I sent you into
that partition, and then try to reproduce my original fsck report on
that? Do you need more information from me first?
...
Yeah, that's not good. Congratulation, whatever software set up your
RAID configuration is as intelligent (or as obsolete) as Windows XP.
Which explains why hard drive vendors are still selling 512e drives,
although they devoutly wish they could stop.
In this case, that would have been cfdisk as of roughly 9 months ago,
and I *think* the problem was it didn't know what to do with an MD
device. Notice how the outer partitions start at offset 2048 but the
inner partitions start at offset 63?
(The disks are much older than the installation because the computer
is secondhand, and had been completely wiped.)
---
# hdparm -I /dev/sdd
/dev/sdd:
ATA device, with non-removable media
Model Number: ST3320418AS
Serial Number: 9VM5KB8B
Firmware Revision: CC44
Transport: Serial
Standards:
Used: unknown (minor revision code 0x0029)
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logicalmaxcurrent
cylinders1638316383
heads1616
sectors/track6363
--
CHS current addressable sectors: 16514064
LBAuser addressable sectors: 268435455
LBA48 user addressable sectors: 625142448
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 305245 MBytes
device size with M = 1000*1000: 320072 MBytes (320 GB)
cache/buffer size = 16384 KBytes
Nominal Media Rotation Rate: 7200
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16Current = 16
Recommended acoustic management value: 208, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
EnabledSupported:
*SMART feature set
Security Mode feature set
*Power Management feature set
*Write cache
*Look-ahead
*Host Protected Area feature set
*WRITE_BUFFER command
*READ_BUFFER command
*DOWNLOAD_MICROCODE
Power-Up In Standby feature set
SET_FEATURES required to spinup after power up
SET_MAX security extension
*Automatic Acoustic Management feature set
*48-bit Address feature set
*Device Configuration Overlay feature set
*Mandatory FLUSH_CACHE
*FLUSH_CACHE_EXT
*SMART error logging
*SMART self-test
*General Purpose Logging feature set
*WRITE_{DMA|MULTIPLE}_FUA_EXT
*64-bit World wide name
Write-Read-Verify
Bug#789399: psocksxx: please make the build reproducible
tags 789399 + pending thanks Hi akira, thank you for spending your time helping to make Debian better with this bug report. If you look at[1] you can see that I have patched the source since 2015 -02-23. I think thats not enough to upload a new version. CU Jörg [1] http://anonscm.debian.org/cgit/collab-maint/psocksxx.git -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#789410: librg-utils-perl: FTBFS with perl 5.22 (Module::Build)
Source: librg-utils-perl Version: 1.0.43-2 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch This package FTBFS with perl 5.22 (currently in experimental), since Module::Build has been removed from perl core: perl Build.PL installdirs=vendor perl Build manifest perl Build touch b uild-stamp Can't locate Module/Build.pm in @INC (you may need to install the Module::Build module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.0 /u sr/local/share/perl/5.22.0 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_pe rl /usr/lib/x86_64-linux-gnu/perl-base .) at Build.PL line 3. BEGIN failed--compilation aborted at Build.PL line 3. The fix is to add a build dependency on libmodule-build-perl. This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789411: librouter-simple-perl: FTBFS with perl 5.22 (Module::Build)
Source: librouter-simple-perl Version: 0.15-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch This package FTBFS with perl 5.22 (currently in experimental), since Module::Build has been removed from perl core: perl Build.PL --installdirs vendor Can't locate Module/Build.pm in @INC (you may need to install the Module::Build module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.0 /u sr/local/share/perl/5.22.0 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at Build.PL line 12. BEGIN failed--compilation aborted at Build.PL line 12. dh_auto_configure: perl Build.PL --installdirs vendor returned exit code 2 The fix is to add a build dependency on libmodule-build-perl. This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789409: librg-exception-perl: FTBFS with perl 5.22 (Module::Build)
Source: librg-exception-perl Version: 1.0.3-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch This package FTBFS with perl 5.22 (currently in experimental), since Module::Build has been removed from perl core: perl Build.PL --installdirs vendor Can't locate Module/Build.pm in @INC (you may need to install the Module::Build module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.0 /u sr/local/share/perl/5.22.0 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at Build.PL line 3. BEGIN failed--compilation aborted at Build.PL line 3. dh_auto_configure: perl Build.PL --installdirs vendor returned exit code 2 The fix is to add a build dependency on libmodule-build-perl. This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Am 20.06.2015 um 18:45 schrieb Ron: On Sat, Jun 20, 2015 at 01:02:50PM +0200, John Paul Adrian Glaubitz wrote: On 06/20/2015 12:52 PM, Patrick Matthäi wrote: I need roaraudio for myself? He is my buddy? I don't know him at all :o John: please stop writing e-mails like this.. It's Adrian, not John, and I am just quoting Ron who certainly isn't making this stuff up. It has apparently always Stephan who came forward and ask for ROAR audio reactivation. You're confusing Patrick and Philipp :) I am not confused. But I couldn't find any evidence the _current_ maintainer of roaraudio has refused to remove DECnet support. The current bug about it has no replies. None of the people responsible for roar has changed in all the years that people have been having trouble with this and trying to resolve it, so if there's no new responses it seems fairly safe to assume that their previous refusals still stand. I can't say what's right or best for cmus, but what is right for Debian seems fairly self evident to everyone but the roar maintainers. There is no depenedencie of *roar* to dnet at all. Personally I don't really see that this needs to go to the TC, it's purely a maintainer decision for the cmus people whether they want to support this as a dependency or not. And whether or not that's a sane thing to do basically rests on whether the roar people actually engage with resolving the ongoing concerns, or continue to insist that DECnet being dead and obsolete is some kind of insidious conspiracy theory. Sorry Ron, but you are realy the last person who is responsible to discuss about topic at all. Same topic as with mumble/celt... -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Bug#660747: Bug Triaging
Control: fixed -1 2.4.1+dfsg-1 According upstream fixed in 2.4.0 -- see forwarded link signature.asc Description: This is a digitally signed message part
Bug#788704: gnutls28: VIA PadLock accelerated AES-CBC segfaults
Hello Andreas, On 20/06/15 14:07, Andreas Metzler wrote: Would you mind testing the code I intend to try to get into stable? I tested the binaries (gnutls-bin, libgnutls-deb0-28) and they work in all AES modes, 128 or 256 bits, CBC and GCM. I used gnutls-cli to connect both to the SMTP server on the same machine and to some SMTP server I picked out of my logs that also supported all those ciphers. Furthermore, exim4 was able to use AES-128-CBC to deliver some test mails to other SMTP servers. So it seems to work fine. Thanks for maintaining the Debian packages and a pleasant bug reporting experience! Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at http://digitalbrains.com/2012/openpgp-key-peter signature.asc Description: OpenPGP digital signature
Bug#788610: ncurses: enable symbol versioning
On 2015-06-13 14:44 +0200, Thomas Dickey wrote: On Sat, Jun 13, 2015 at 11:51:17AM +0200, Sven Joachim wrote: Source: ncurses Version: 5.9+20150516-2 Severity: wishlist Control: block 230990 by -1 For about half a year ncurses has a --with-versioned-syms configure option that enables symbol versioning. We should use this option in the upcoming ncurses 6.0 release and rebuild all reverse dependencies before the Stretch release so that we can switch to the new ABI afterwards. When using this option, quite a lot of internal symbols which are not part of the API are no longer exported, see the attached list. Fortunately according to codesearch.debian.net, very few packages seem to use any of those symbols: - fpc, in fpcsrc/packages/ncurses/src/form.pp, apparently declares _nc_Default_Form and _nc_Default_Field. Probably nobody really uses those, but I don't really have a clue of Pascal. Probably no one does... A web search for these with pascal shows only this bug report. Because of that, I'm inclined to recommend that Debian drop those symbols from its package for fpc. I have opened bug #789091 for that purpose. Note that these symbols used to declared in the form.h header in ncurses before the 20091107 patch. If there is some existing package which does use the symbols, we can address that. - libncursesada and haskell_ncurses declare _nc_has_mouse, but only if NCURSES_VERSION_PATCH 20081122. Prior to that date, _nc_has_mouse was actually part of the API so its removal might break some old programs. This might be a case where the symbol should actually be exported in order not to break the ABI. To put it in context, the threshold date is right after ncurses 5.7, which is a matter of concern for Debian 6... It is correct that nc_has_mouse is probably not used by any package currently in the archive, but ncurses is also used by third-party software. I think the general consensus in Debian is to only remove symbols (especially those which used to be public) from a library when the soname is bumped, see Policy §8.6.2[1]. Cheers, Sven 1. https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-updates -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653132: netbeans: Profiler not included in package
Control: severity -1 wishlist On Sat, 24 Dec 2011 12:11:36 +0100 Pablo =?ISO-8859-1?Q?Rodr=EDguez_Fern=E1ndez?= morpheus17@gmail.com wrote: Package: netbeans Version: 7.0.1+dfsg1-4 File: /usr/bin/netbeans Severity: normal Installed netbeans from testing/unstable doesn't include profile support, while installing from netbeans.org it does. I think it must be included. Hello, I agree with the bug submitter that it would be nice to include the profiler module but I would call it a feature request for Debian's Netbeans package. Netbeans is difficult to maintain due to the fact that we have to replace all embedded jar and zip files. Every new enabled module increases the difficulty to maintain this package. If we want to enable the profiler, we have to add the module to nbbuild/cluster.properties again. https://anonscm.debian.org/cgit/pkg-java/netbeans.git/tree/debian/patches/netbeans-cluster-properties.patch However when I try to build Netbeans with the profiler module enabled, the package fails to build from source. I would really like to see this module packaged for Debian, but I request help in maintaining and fixing this issue. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#789390: pyclamd: please update the package to 0.3.15
Source: pyclamd Version: 0.3.9-2 Severity: wishlist tags: patch Hi, since I'm in an ongoing effort to package w3af for Debian (an updated version), I would like to have the last version of pyclamd (actually w3af uses python-clamd, I asked upstream to switch to pyclamd). thanks a lot for the effort, I did a quick review for the package and I found some minor improvements I'm attaching to this email. summary: *bump std version to 3.9.6 *use export PYBUILD_NAME=pyclamd - this means removing .install files * remove overrides dh clean (not needed) * remove docs files (not ship anymore) * remove patches, not needed anymore (upstreamed) cheers, Gianfranco pyclamd_0.3.15-1.debian.tar.xz Description: application/xz
Bug#789392: general: fails to show dual screens on startup
Package: general Severity: normal Dear Maintainer, * What led up to the situation? The problem I am having is that when I turn on my laptop with the hdmi cable connected to another screen, the laptop screen seems like turned off. Laptop (Screen 1) + Samsung Screen 22 (Screen 2). The same problem happens if I logout (my laptop screen turns off). * What exactly did you do (or not do) that was effective (or ineffective)? To solve this I have to go to display settings and start playing with the configuration 2 o 3 times until I can see my laptop screen working. * What outcome did you expect instead? The outcome expected is being able to turn on my laptop connected with the hdmi to another screen and see both screens fine. Screen 1 on the left and Screen 2 on the right, both visibles. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
