Bug#744102: debian-maintainers: Please add Graham Inggs as a Debian Maintainer
Package: debian-maintainers Severity: normal Please add my key to the DM keyring, the jetring changeset is attached. add-AFCFEC8E669CE1C2 Description: Binary data
Bug#740375: transition: poppler 0.24
On Mon, Apr 7, 2014 at 17:49:15 +0200, Pino Toscano wrote: > - gdcm cannot be built on s390x due to the ongoing (and un-ACKed...) > mpich transition (#742821), so maybe that transition should be > brought forward (luckly it affects mostly s390x and mips/mipsel) > So I've rebuilt boost1.54 to be able to rebuild vtk to be able to rebuild gdcm. Not much luck there, vtk FTBFS. Cheers, Julien signature.asc Description: Digital signature
Bug#735202: speakup freezes system when trying to paste
Ben, I downloaded upstream kernel 3.12.17 and reproduced the issue. Then I patched it and using this patched kernel I see no ways to reproduce the issue. Pasting always works, even in scenario reported in bug #744015. Now I'll try to reproduce this other bug with and without the patch with kernel 3.14. Paul, thanks for the snapshot link. I couldn't find this useful archive by myself. I wanted to add that preparing a kernel from source works like a charm. I haven't seen any project that would be easier to build. It takes quite long, that's a different story. 11 hours. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744015 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733564: pu: apache2 with ECDHE support
Am Montag, 30. Dezember 2013, 15:23:17 schrieb Kurt Roeckx: > On Mon, Dec 30, 2013 at 01:41:31PM +0100, Cyril Brulebois wrote: > > Stefan Fritsch (2013-12-30): > > > Am Sonntag, 29. Dezember 2013, 23:58:54 schrieb Kurt Roeckx: > > > > Adding ECDHE support in apache will probably require > > > > backporting the patches for that. I'm not sure how much work > > > > that is going to be and wether someone like redhat might have > > > > already done that.> > > > > I don't know how quickly upgrades are ususally adopted in MacOS > > > land, but considering that 10.8.5 is out I think it would be > > > even acceptable to update apache without that openssl > > > workaround, as long as the readme contains exact instructions > > > how to disable ECDHE in case of problems. But of course having > > > the openssl workaround would be even better. Some statistics at http://update.omnigroup.com/ (click on minor versions for 10.8) gives 16.1% of macosx users using 10.8.x and 1.3% using 10.8.x with x <= 3. Personally, I don't think we need special provisions for those 1.3% of macosx users, which is <= 0.1% of total users. But I would of course be fine with Kurt backporting the workaround. > > If we're going to end up adding ECDHE support, and if it isn't > > supported everywhere yet, I'm pretty sure support for it all > > shouldn't be enabled automatically upon upgrades, and that it > > should be enabled manually by admins instead, following > > instructions that include incompatibility warnings (hello, page > > 51 of the draft at https://bettercrypto.org/). > If you want an overview of what browser support, you can see see > that on ssllabs. The only way I know of getting that info for > other browser is going to a random website and then selecting the > browser. > > About the only thing not supporting ECDHE is java 6 and internet > explorer on windows XP. Internet explorer is also the only one > that doesn't have ECDHE (or even DHE) at the top the prefered > ciphers. Browser support in itself is not the interesting factor here. We are not disabling other ciphers, so clients not supporting ECDHE will just continue to work. The question is how many browsers have broken implemetations AND still use it as the preffered cipher. And the only ones that we know of are those MacOS versions mentioned above. I would however not go the way of requiring the admin to explicitly enable support on upgrades. The problem is that the default configured cipher suite is HIGH:MEDIUM:!aNULL:!MD5 which includes ECDHE if supported. To make the change opt-in, we would either need to change the conffiles during upgrade, I would like to avoid, or we would need to make the configuration incompatible with upstream by requiring something special. I would like to have another upgrade for apache2 for the next wheezy point release in any case. Therefore I would appreciate some feedback from the release team if they would accept a change to include ECDHE support. Cheers, Stefan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744101: indent: debian/copyright - Sources URL no longer exists
Source: indent Version: 2.2.11-4 Severity: minor URL mentioned in debian/copyright as is unaccessible. http://indent.isidore-it.eu/indent-2.2.11.tar.gz Please update location. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.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#744073: scilab shared libraries are heavily underlinked
On 09/04/2014 23:11, Matthias Klose wrote: > Am 09.04.2014 22:43, schrieb Sylvestre Ledru: >> severity 744073 normal >> thanks >> >> On 09/04/2014 20:49, Matthias Klose wrote: >>> Package: scilab >>> Version: 5.5.0~beta-1+git~20140406-1522-2 >>> Severity: important >>> >>> please forward this upstream. maybe as separate bug reports for each library >>> with unresolvable references. >>> >> Thanks for sharing. However, I do not agree on the severity. >> That does not prevent the package to build under Debian. I don't know >> what is different in Ubuntu >> and explains the FTBFS there. > If you don't care about it in Ubuntu, then please don't file requests to sync > the package during deep freeze before the release, and then not addressing the > newly introduced build failures. > I do care and you know that. It is just that the issue is not critical in Debian but is in Ubuntu. Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707254: transmageddon: Impossible to use xvid codec
forwarded 707254 https://bugzilla.gnome.org/show_bug.cgi?id=727932 forcemerge 707254 707259 thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#583950: ciao
qui veramente a buon mercato itorts.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744100: python-pelican: missing dependency on pkg_resources
Package: python-pelican Version: 3.2.1-1 Hi maintainers, I installed python-pelican on a VPS running Ubuntu 13.10 and got: geofft@cactuar:~/src/website/pelican-test$ pelican Traceback (most recent call last): File "/usr/bin/pelican", line 5, in from pkg_resources import load_entry_point ImportError: No module named pkg_resources I assume the package needs a dependency on python-pkg-resources, or I guess something in debian/pydist-overrides? (Admittedly I haven't actually tested on Jessie, but there doesn't seem to be a dependency there or any relevant changes.) Thanks, -- Geoffrey Thomas https://ldpreload.com geo...@ldpreload.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744099: update chromium
Package: chromium Can Debian be updated soon? > "c" == chromium writes: c> Comment #5 on issue 360409 by nyerrami...@chromium.org: Passwords c> aren't remembered for Discuz! sites c> http://code.google.com/p/chromium/issues/detail?id=360409 c> Could you please check with latest chrome stable 34.0.1847.116 c> (Official Build 260972) c> I tried on 34.0.1847.116, Password stored successfully in c> chrome://settings//passwords and remembered for the next time user c> tried to login to http://ragii.com/ c> Please check the attached screenshots c> Attachments: c> 360409_1.png 8.3 KB c> -- c> You received this message because you starred the issue. c> You may adjust your notification preferences at: c> https://code.google.com/hosting/settings c> Reply to this email to add a comment. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744098: wxhexeditor: Please update to use wxwidgets3.0
Package: wxhexeditor
Version: 0.22+repack-2
Severity: normal
Tags: patch
User: freewx-ma...@lists.alioth.debian.org
Usertags: wx3.0
Dear maintainer,
We're aiming to migrate the archive to using wxwidgets3.0 instead of
wxwidgets2.8.
I've rebuilt your package using the attached patch and did some simple
testing. Everything looks good to me.
I'm happy to NMU this change if you wish me to - just let me know.
Cheers,
Olly
diff -Nru wxhexeditor-0.22+repack/debian/changelog wxhexeditor-0.22+repack/debian/changelog
--- wxhexeditor-0.22+repack/debian/changelog 2013-12-30 01:43:21.0 +1300
+++ wxhexeditor-0.22+repack/debian/changelog 2014-04-10 13:40:20.0 +1200
@@ -1,3 +1,10 @@
+wxhexeditor (0.22+repack-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Update to use wxWidgets 3.0.
+
+ -- Olly Betts Thu, 10 Apr 2014 13:40:16 +1200
+
wxhexeditor (0.22+repack-2) unstable; urgency=low
* Apply patch from upstream bug tracker fixing hex input.
diff -Nru wxhexeditor-0.22+repack/debian/control wxhexeditor-0.22+repack/debian/control
--- wxhexeditor-0.22+repack/debian/control 2013-05-12 05:44:43.0 +1200
+++ wxhexeditor-0.22+repack/debian/control 2014-03-18 15:05:21.0 +1300
@@ -2,8 +2,8 @@
Section: editors
Priority: optional
Maintainer: Andrew Shadura
-Build-Depends: debhelper (>= 9), wx2.8-headers,
- libwxbase2.8-dev, libwxgtk2.8-dev, wx-common,
+Build-Depends: debhelper (>= 9),
+ libwxgtk3.0-dev,
libmhash-dev, libdisasm-dev
Standards-Version: 3.9.4
Homepage: http://sourceforge.net/projects/wxhexeditor
diff -Nru wxhexeditor-0.22+repack/debian/patches/07-use-proper-opts.patch wxhexeditor-0.22+repack/debian/patches/07-use-proper-opts.patch
--- wxhexeditor-0.22+repack/debian/patches/07-use-proper-opts.patch 2013-12-30 01:41:29.0 +1300
+++ wxhexeditor-0.22+repack/debian/patches/07-use-proper-opts.patch 2014-04-10 13:44:39.0 +1200
@@ -4,7 +4,7 @@
--- a/Makefile
+++ b/Makefile
-@@ -1,10 +1,6 @@
+@@ -1,10 +1,10 @@
WXCONFIG = wx-config
-CC = `$(WXCONFIG) --cc`
-CXX = `$(WXCONFIG) --cxx`
@@ -12,12 +12,16 @@
-CXXFLAGS = -O2
-WXCXXFLAGS= `$(WXCONFIG) --cxxflags` -MMD -O2 -c ${OPTFLAGS}
-WXLDFLAGS = `$(WXCONFIG) --libs`
-+WXCXXFLAGS= `$(WXCONFIG) --cxxflags` -MMD
-+WXLDFLAGS = -Wl,--as-needed `$(WXCONFIG) --libs`
++# Define NDEBUG to disable wxWidgets 3.0 debug mode to avoid a lot of assertion
++# failed dialogs. While it would be better to actually fix the causes of
++# these, if NDEBUG is defined, then these conditions are handled quietly, just
++# like wxWidgets 2.8 did by default.
++WXCXXFLAGS= `$(WXCONFIG) --cxxflags` -MMD -DNDEBUG
++WXLDFLAGS = -Wl,--as-needed `$(WXCONFIG) --libs std,aui`
RC = `$(WXCONFIG) --rescomp`
#RC = x86_64-w64-mingw32-windres --define WX_CPU_AMD64
RCFLAGS = `$(WXCONFIG) --cxxflags | sed s/' '-m.*//g;`
-@@ -51,7 +47,7 @@
+@@ -51,7 +51,7 @@
$(CXX) $(CXXFLAGS) $(CPPFLAGS) $(LDFLAGS) $(OBJECTS) $(LIBS) $(WXLDFLAGS) -o $@
.cpp.o: $(LIBS)
signature.asc
Description: Digital signature
Bug#744097: stdeb: pypi-install broken due to python.org URL change
Package: python-stdeb Version: 0.6.0+20100620-2 Severity: grave File: stdeb Currently, due to a website reorganization within python.org, the find_tar_gz() function crashes with: File "/usr/lib/python2.7/xmlrpclib.py", line 1312, in single_request response.msg, xmlrpclib.ProtocolError: https://github.com/astraw/stdeb/pull/72 (patch there) addresses the problem by using the canonical URL of PyPI. -- System Information: Debian Release: squeeze/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-stdeb depends on: ii debhelper 9.20120419~bpo60+1 helper programs for debian/rules ii python2.7.5-5interactive high-level object-orie ii python-setuptools 0.6.49-2 Python Distutils Enhancements (set ii python2.6 2.6.6-8+b1 An interactive high-level object-o ii python2.7 2.7.5-8Interactive high-level object-orie Versions of packages python-stdeb recommends: ii apt-file 2.5.1 search for files within Debian pac ii dpkg-dev 1.16.10Debian package development tools ii python-all2.7.5-5package depending on all supported Versions of packages python-stdeb suggests: pn python-all-dev (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744096: texlive-metapost-doc: PDF Outline doesn't list References or Index
Package: texlive-metapost-doc Version: 2013.20140314-1 Severity: normal File: /usr/share/doc/texlive-doc/metapost/base/mpman.pdf Dear Maintainer, I'm reporting this despite the below warning, because you seem to have neglected to provide any information on how to look up where to send such reports (and because tex-l...@tug.org doesn't sound like a proper bug tracking system to me). The Metapost manual would benefit by including entries in the PDF "outline" for the References and Index, preferably (but this is probably something of a pipe dream) with some sort of alphabetical subdivision for the index. -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problems with combination of packages in a LaTeX document, please consult your local TeX User Group, the comp.text.tex user group, the author of the original .sty file, or any other help resource. In particular, bugs that are related to up-upstream, i.e., neither Debian nor TeX Live (upstream), but the original package authors, will be closed immediately. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.11-2-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/bash Versions of packages texlive-metapost-doc depends on: ii dpkg 1.17.5 ii tex-common4.04 ii texlive-base 2013.20140314-1 texlive-metapost-doc recommends no packages. texlive-metapost-doc suggests no packages. Versions of packages tex-common depends on: ii debconf [debconf-2.0] 1.5.52 ii dpkg 1.17.5 ii ucf3.0027+nmu1 Versions of packages tex-common suggests: ii debhelper 9.20131227 Versions of packages texlive-metapost-doc is related to: ii tex-common4.04 ii texlive-binaries 2013.20130729.30972-2+b1 -- debconf information: tex-common/check_texmf_wrong: tex-common/check_texmf_missing: -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#581624: pulseaudio: Stuttering playback from Wine
On Sat, Apr 5, 2014 at 5:22 PM, Michael Gilbert wrote: > It probably makes sense to change the default to 5 rather than 25. It appears that this breaks other software such as skype[1], and the workaround would be to actually raise the latency. Quoting from the link: Applications can ask PulseAudio for the latency that they wish to have (the amount of time between writing out a sample and it being played out the speaker/headphones/whatever). Skype seemed to have some weird buggy math that only kicked in at low latencies (20-25ms or less) that caused the problem you saw. Setting PULSE_LATENCY_MSEC forces the requested latency (60 is pretty safe across most setups), making sure this bug in Skype is not triggered. Rather than change the default, perhaps wine can set PULSE_LATENCY_MSEC? Applications that are buggy with too high or too low latencies will probably exist always. I don't know what should we do in this case. [1] http://arunraghavan.net/2013/08/pulseaudio-4-0-and-skype/#comment-723074 -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744095: Set default gcc-4.8 as default for mips64(el)
Package: src:gcc-defaults Version: 1.126 Hi, as I test, gcc-4.8 and gcc-4.9 work well on mips64el. So please set gcc-4.8 as default in sid, and set gcc-4.9 as default in experimental. Please take care mips64/mips64el in future when bump the default version in sid to 4.9. Thank you. -- Yunqiang Su -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744093: awstats: Proposed patch
Package: awstats
Version: 7.2+dfsg-1
Followup-For: Bug #744093
I have just made this small patch, that allows the user to set a
'AWSTATS_PROCESS_AWSTATS_CONF=no' in /etc/awstats to stop the default config
file to be taken into account if there are per-site configuration files.
-- System Information:
Debian Release: 7.4
APT prefers stable
APT policy: (900, 'stable'), (50, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages awstats depends on:
ii perl 5.14.2-21+deb7u1
Versions of packages awstats recommends:
ii coreutils 8.13-3.5
pn libnet-xwhois-perl
Versions of packages awstats suggests:
ii apache2 2.2.22-13+deb7u1
ii apache2-mpm-worker [httpd] 2.2.22-13+deb7u1
pn libgeo-ipfree-perl
ii libnet-dns-perl 0.66-2+b2
ii libnet-ip-perl 1.25-3
ii liburi-perl 1.60-1
-- Configuration Files:
/etc/awstats/awstats.conf.local changed [not included]
/etc/cron.d/awstats changed [not included]
/etc/default/awstats changed [not included]
-- no debconf information
--- /usr/share/awstats/tools/update.sh.orig 2014-04-10 04:21:41.013276300 +0200
+++ /usr/share/awstats/tools/update.sh 2014-04-10 04:27:28.786853048 +0200
@@ -24,9 +24,16 @@
cd /etc/awstats
-for c in `/bin/ls -1 awstats.*.conf 2>/dev/null | \
- /bin/sed 's/^awstats\.\(.*\)\.conf/\1/'` \
- `[ -f /etc/awstats/awstats.conf ] && echo awstats`
+CONFIGS=`/bin/ls -1 awstats.*.conf 2>/dev/null | \
+ /bin/sed 's/^awstats\.\(.*\)\.conf/\1/'`
+
+if [ -f /etc/awstats/awstats.conf ] && (
+ [ "${AWSTATS_PROCESS_AWSTATS_CONF:-yes}" = "yes" ] || [ -z "$CONFIGS" ])
+then
+ CONFIGS="${CONFIGS+"$CONFIGS "}awstats"
+fi
+
+for c in $CONFIGS
do
if ! nice -n $AWSTATS_NICE $AWSTATS \
-config=$c \
--- /usr/share/awstats/tools/buildstatic.sh.orig 2014-04-10 04:21:35.169385745 +0200
+++ /usr/share/awstats/tools/buildstatic.sh 2014-04-10 04:37:37.942061858 +0200
@@ -30,9 +30,16 @@
cd /etc/awstats
-for c in `/bin/ls -1 awstats.*.conf 2>/dev/null | \
- /bin/sed 's/^awstats\.\(.*\)\.conf/\1/'` \
- `[ -f /etc/awstats/awstats.conf ] && echo awstats`
+CONFIGS=`/bin/ls -1 awstats.*.conf 2>/dev/null | \
+ /bin/sed 's/^awstats\.\(.*\)\.conf/\1/'`
+
+if [ -f /etc/awstats/awstats.conf ] && (
+ [ "${AWSTATS_PROCESS_AWSTATS_CONF:-yes}" = "yes" ] || [ -z "$CONFIGS" ])
+then
+ CONFIGS="${CONFIGS+"$CONFIGS "}awstats"
+fi
+
+for c in $CONFIGS
do
mkdir -p /var/cache/awstats/$c/$YEAR/$MONTH/
Bug#744094: Acknowledgement (lighttpd: Default ssl.ciphers disables AES-GCM)
Of course, I have meant BEAST, not *BEST. Please ignore typos. -k -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742570: nvidia-legacy-173xx-driver doesn't load. Returns Unknown symbol acpi_os_wait_events_complete (err 0)
Package: nvidia-legacy-173xx-driver Version: 173.14.39-1 Followup-For: Bug #742570 Stil going on with kernel 3.13.7. -- Package-specific info: uname -a: Linux warpcore 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux /proc/version: Linux version 3.13-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-16) ) #1 SMP Debian 3.13.7-1 (2014-03-25) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. MS-8917 (FX5200-T128) [1462:9171] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- dmesg: [0.00] AGP bridge at 00:00:00 [0.00] Aperture from AGP @ ec00 old size 32 MB [0.00] Aperture from AGP @ ec00 size 64 MB (APSIZE f30) [0.00] AGP bridge at 00:00:00 [0.00] Aperture from AGP @ ec00 old size 32 MB [0.00] Aperture from AGP @ ec00 size 64 MB (APSIZE f30) [0.00] Console: colour VGA+ 80x25 [0.084877] vgaarb: device added: PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none [0.084944] vgaarb: loaded [0.085590] vgaarb: bridge control possible :01:00.0 [0.546445] agpgart-amd64 :00:00.0: AGP bridge [1106/3188] [0.550041] agpgart-amd64 :00:00.0: AGP aperture is 64M @ 0xec00 [0.588663] Linux agpgart interface v0.103 [8.552412] nvidia: module license 'NVIDIA' taints kernel. [8.579502] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0) [37867.311252] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0) OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Mar 24 18:17 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 48 Jul 12 2013 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so lrwxrwxrwx 1 root root 48 Jul 12 2013 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so lrwxrwxrwx 1 root root 43 Mar 24 18:17 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Mar 24 18:17 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 47 Mar 24 18:17 /etc/alternatives/glx--libGLcore.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLcore.so.1 lrwxrwxrwx 1 root root 47 Mar 24 18:17 /etc/alternatives/glx--libGLcore.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLcore.so.1 lrwxrwxrwx 1 root root 51 Mar 24 18:17 /etc/alternatives/glx--libXvMCNVIDIA.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 59 Mar 24 18:17 /etc/alternatives/glx--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 51 Mar 24 18:17 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 51 Mar 24 18:17 /etc/alternatives/glx--libnvidia-tls.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-tls.so.1 lrwxrwxrwx 1 root root 25 Mar 24 18:17 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Mar 24 18:17 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Mar 24 18:17 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 29 Mar 24 18:17 /etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 55 Mar 24 18:17 /etc/alternatives/glx--tls-libnvidia-tls.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/tls/libnvidia-tls.so.1 lrwxrwxrwx 1 root root 22 Jul 12 2013 /etc/alternatives/libGL.so-master -> /usr/lib/mesa-diverted lrwxrwxrwx 1 root root 28 Mar 24 18:17 /etc/alternatives/nvidia -> /usr/lib/nvidia/legacy-173xx lrwxrwxrwx 1 root root 56 Mar 24 18:17 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/legacy-173xx/libGL.so.1 lrwxrwxrwx 1 root root 56 Mar 24 18:17 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/legacy-173xx/libGL.so.1 lrwxrwxrwx 1 root root 60 Mar 24 18:17 /etc/alternatives/nvidia--libGLcore.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/legacy-173xx/libGLcore.so.1 lrwxrwxrwx 1 root root 60 Mar 24 18:17 /etc/alternatives/nvidia--libGLcore.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/legacy-173xx/libGLcore.so.1 l
Bug#744094: lighttpd: Default ssl.ciphers disables AES-GCM
Source: lighttpd Version: 1.4.35-2 Severity: minor In version 1.4.30-1, the following line was included in default conf-available/10-ssl.conf as mitigation for BEST attack: ssl.cipher-list = "ECDHE-RSA-AES256-SHA384:AES256-SHA256:RC4:HIGH:!MD5:!aNULL:!EDH:!AESGCM" NEWS file refers to [1] which back then [2] suggested using the above cipherlist. But BEST affected only CBC suites in TLS 1.0 and there was never any reason to disable AES-GCM. Referenced blog post also gave no justification for it. GCM suites have been, and still are, considered the best choice available in OpenSSL so it's definitely a bad idea to disable them by default. Please check the updated post [1]. [1] http://blog.ivanristic.com/2011/10/mitigating-the-beast-attack-on-tls.html [2] https://web.archive.org/web/20111216165019/http://blog.ivanristic.com/2011/10/mitigating-the-beast-attack-on-tls.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744093: awstats: Using the multiple-config schema results in cron spamming with errors
Package: awstats Version: 7.2+dfsg-1 Severity: minor Hi, I have configured awstats using one of the recommended schemes in README.Debian, namely: using one small conffile per virtual-host that also includes the default awstats.conf. This is a great way to have tidy configuration files, but it has a very annoying drawback: the cronjobs still try to use the unmodified awstats.conf file, and send me an email about this every 10 minutes. I would like to have a mechanism to disable the use of that file, or to automatically disable it when per-host configuration files are present. I undestand this might be problematic for backwards compatibility, so a variable in /etc/default/awstats might be used. Thanks. -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (900, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages awstats depends on: ii perl 5.14.2-21+deb7u1 Versions of packages awstats recommends: ii coreutils 8.13-3.5 pn libnet-xwhois-perl Versions of packages awstats suggests: ii apache2 2.2.22-13+deb7u1 ii apache2-mpm-worker [httpd] 2.2.22-13+deb7u1 pn libgeo-ipfree-perl ii libnet-dns-perl 0.66-2+b2 ii libnet-ip-perl 1.25-3 ii liburi-perl 1.60-1 -- Configuration Files: /etc/awstats/awstats.conf.local changed [not included] /etc/cron.d/awstats changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744027: data point
On Wed, 9 Apr 2014, Kurt Roeckx wrote: However, iceweasel/firefox by default is happy to ignore a OCSP timeout. You need to turn it on that it doesn't allow a timeout. I have no idea why they use that as default. Because it's an easy DoS if an attacker is in a position to MITM the connection between you and the OCSP service (or CRL file), no? And if the attacker can MITM the connection between you and the SSL service you're trying to talk to, they can probably also MITM the OCSP or CRL server. Also (as Adam Langley points out in the stuff I linked to earlier in this bug report) the OCSP servers risk becoming a single point of failure if you do that. If a CA's OCSP server is down, everything they sign becomes inaccessible. That would be a bad default, and probably not something you want to turn on for yourself either. Also also, http://www.thoughtcrime.org/papers/ocsp-attack.pdf which appears to be still valid with Firefox at least: https://bugzilla.mozilla.org/505812 So there's really no value at all in using OCSP, it seems. -- Geoffrey Thomas https://ldpreload.com geo...@ldpreload.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743965: [Pkg-utopia-maintainers] Bug#743965: network-manager: vpnc (through dispatcher) stopped working with latest NM update
Am 08.04.2014 22:22, schrieb Ritesh Raj Sarraf: > On 04/09/2014 01:17 AM, Ritesh Raj Sarraf wrote: >> Package: network-manager >> Version: 0.9.8.8-5 >> Severity: normal >> >> I prefer connecting to VPN using the dispatcher framework. It allows me >> to use a bash script, through which I can loop and check if the VPN >> connection dropped. This had been working flawlessly for months until >> the recent update. >> >> Something in the recent updates has broken the VPN service (or maybe the >> dispatcher use cases). Relevant system logs are: > > I can confirm that this is a breakage introduced in the 0.9.8.8 version > on network-manager. Reverting back to 0.9.8.0, I do not see the problem > anymore. > In fact, not just my dispatcher use case, but in general, there are many > issues related to VPN, reported in this new version of network-manager. Such as? > In case you want logs, I have made it available at: > http://people.debian.org/~rrs/tmp/nm-vpn-bug-743965.txt What am I supposed to see here? Please be more specific about the problems you are having. -- 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#574947: Status and progress
Hello, 2014-04-09 22:38 GMT+09:00 Punit Agrawal : > Ron's, rather short, reply pointed out that a distro package requiring > users to run a generated script as root isn't an acceptable interface. It's a misunderstanding. I just offered a means to leave the admin user to update the system directory (sitekeys directory). It is only a default; it is not required. You can change it by configure script as follows: $ ./configure --with-sitekeys-mode=777 This command line executes 'chmod 777 '/gtags/sitekeys'. If you have write permission for the directory, you need not invoke bless.sh after executing htags. Of course, root permission is not required. Please see 'FILES' section of htags(1). > I am not sure how actively this feature is used, but in the interest > of updating the package I proposed to drop generating the script and > print a message for now. I've not received any further reply to my > request for clarification or the proposed changes. Bless.sh script is needed for moving the project directory. Just making 'sitekeys' directory writable, everything goes well. # # Builds a hypertext of a project # $ cd /usr/src/project $ htags -f --system-cgi=key # => CGI works (bless.sh is not needed) # # Moves the project to another place # $ mv /usr/src/project /home/user # => CGI does not work $ cd /home/user/project/HTML $ sh bless.sh # => CGI works (bless.sh is needed) > Watch this space for further progress and do let me know if you face > any problems trying to use the package from the linked repository. > > [0] http://anonscm.debian.org/gitweb/?p=collab-maint/global.git;a=summary Great! I am very glad to hear that new Debian GLOBAL will be released soon. I appreciate your efforts. Regards, Shigio -- Shigio YAMAGUCHI PGP fingerprint: D1CB 0B89 B346 4AB6 5663 C4B6 3CA5 BBB3 57BE DDA3
Bug#744092: xerces-c: watchfile with signature verification
Source: xerces-c Severity: minor Tags: patch I've attached a patch which adds a watchfile for this package along with upstream's PGP keys to allow for automatic signature verification. -- David Gilman :DG< http://gilslotd.com diff -rN xerces-c-3.1.1-orig/debian/upstream/signing-key.asc xerces-c-3.1.1/debian/upstream/signing-key.asc 0a1,224 > This file contains the PGP keys of various Xerces-C++ developers. > Please don't use them for email unless you have to. Their main > purpose is code signing. > > Xerces-C++ users: > If you use PGP: pgp < KEYS > If you use gpg: gpg --import < KEYS > Xerces-C++ developers: > If you use pgp: pgp -kxa and append it to this file. > If you use gpg: gpg --export -a >>KEYS should do the trick > > NameUser ID > Boris Kolpackov bo...@kolpackov.net > Tinny Ngt...@apache.org > Gareth Reakes gar...@apache.org > Neil Graham ne...@apache.org > -BEGIN PGP PUBLIC KEY BLOCK- > Version: GnuPG v1.2.5 (GNU/Linux) > > mQGLBD7gyjQBDADjboRuWsUo7JXgicFS5DGpqIhhHqmzifDxI1Sb/xHk7WZfxsNG > YFp1c5NXCsMKx801UUCeiezam9iiWILSl7SOnTvE4LUPkMJSSB9gsekt8YCDnUFr > cYdohOKSZvZi5l9KGLwAmF7CXhRItVWzbEHPcFQvWpBqtl7UXbWu+j3RPMHocNH8 > I6ujnPCGhuaYYCsbUQzzlzVMw0mROm6vFKP2PcYmthXqS5eBLE2oNmUX06tn7U0i > 5RjH34yLsaneXCwFJDeDc8RoYGvN8W4KR0uJp0i2BSop3dfkgYlxeB3NoqCh58Rk > jMrzJrhG3aetT2OIASNhsD80GT6phBvKLhPnBI/ifHxvUbKBkes5MlfMe/2TuHAq > op8iby2Kh54aW7TtUn8aWCZE0kWkOjYYXTH8wBPiTr/RBcdPNXkwofpLIDbV+JL4 > qxebeZ8/HxPYoE2yN4mAM765sIWiZyKQhf4VurOXjOO/zsaGiP54vdnDO2ZlwVuS > RaglWAZ2+SR79YUABim0KUJvcmlzIEtvbHBhY2tvdiA8Ym9yaXNAY29kZXN5bnRo > ZXNpcy5jb20+iQG0BBMBAgAeBQJC1WiIAhsDBgsJCAcDAgMVAgMDFgIBAh4BAheA > AAoJEMiAKQuuCE8dkCAMAJqV/8EzQphusvSblnI2LZFaFFLKlot8PUNrqZGEq4D2 > mrTQkrkOBVHzSSm/MGOuhSeknzSS6hgEb+L647oxPSQ/YVJ6C7JFkQqcp6gfrYj/ > AaCIhJkBccLIxkoNE5gaEZJvhd0WhDg0O0Xy7Jfsl0OQS9mvS5Prw69+ZRE0gFj/ > H6XCm7zxpoXtQhFT1QZL/WJEyUIbDQeGppwueHAockV30f6VU+Q+t5PPYDd2+9hf > i6hOrHo6Ldne0or1xid+b27uqCid2mCHZM6Q00cMlbupiDiFw0Pjd3pcK7bgFS6o > kiHpFieMNgwhVEzz+nqOLoxO8dWz190MPbiW7k2zH+4PWVW3+Qwjq5QAtl18PNRE > Lt7XgIT/5AI/ov5CoyVLA0w9I3iL1ChcbzPlHGz0eQgOKM79PikSjkvfAns757te > yyWtnfwJcajph2fmz2GTmBAdwVELskmZCqntxIpM3vVZqDl+Sn3JtPl5uNl7zgIl > JCjYv/trdjqRIHW9ty7s1rQlQm9yaXMgS29scGFja292IDxib3Jpc0Brb2xwYWNr > b3YubmV0PokBtwQTAQIAIQIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAUCQtVpVQIZ > AQAKCRDIgCkLrghPHWNODACJkRxgIhj6sbLk10nfC4c7DDLhO96HzaWl4W/f34RT > 2ZcT9QMlT0rGim93HadI5160aTb3I8uxdsNKUpjZbFMl/6W6jb/rU5qVWPLIKgHG > THvskJchTylklhZWhc2/QTHMWZPF2ipr0v6djkIMtEkH1os6cevPvPNkXxFcQmBk > GxUgINYe+F5snRmXnR2Fbm56Xam9TWKNfrpNLY03s/S7iHmonLSw7qW5Ixjmrdeh > Snil6TxGhDU/AiRX/EEa5O/pqUwlm2E/6TvgQoeX1fEx0YjLevVWjoqASFg75INk > N8D6P10mT0LvgIAuK3Ppcd69No3RLufsJGgXjb8NIQyzltqH/S0qPeSBrrpisf/y > lV51RuIZBgYHRHl7xVG+KEJ5JLyLzfwebPmRyXiHkM1yz749tiyhV5JMcKsO3hOy > 6nZtQRt1as5Dmm0dzhFHYLImqP8nQAblu6q7FRLJLcXLJl8NlOWVPttPcmuGaXc2 > NeYuUdtFi+hquk268CtpCJW5Aw0EPuDNnBAMAPa+/MHQ5JBkR+VoVU+9bVLb+RFq > lORX9Mtl7MwYBSQwOOv0KTMXVv/ucqh7A4cLQkK7QVD878C1kTYjupDdrAp7GDlN > vhzoE+ltuJaUYFDbviwH++vOMMR3DqkPvfcWxUbCGIFDWyHIqVUmGkOzzTIk62IT > gYNBvIhxqSh+r5LG0dNFYO+W5bd0FzftmP4AnfhMPDKM6OJsZ2ZrHR0t8EJnn4Pn > 6/D1e02/1CUdlMM8gTSAXk4wF69TCsE9fvDq5jgLoud1I2RKLmhRDDxxmQUAjBir > aab32oeRzNgbU5RbtolHxfvDiRmHUDDqQavNT3HpElbeXj/J5/Jkh0LcpF1QsDUJ > pewVVX4ltMCnCATqUqqgx5UpnfEY1Dt5N3uuO5znQ5oznZHsLWx3qWegTJn7acta > /HlFUpSMaxteuXT/6EiE7lAzsGSWTcX8BpCHviDVPhQMy2AFzWSQlUItXyfkfX0B > SOgFypLjffx4+bms/DXJPYgwEhjFiTaATBeUOwADBQwAuPTkktfoMsI4lL4UYBr5 > afW1R6lHwMZeoH7Mspb82bC9Lqi5gU3wBu3RJwm1CswGMBys+o9J0eA7EDRPw8wM > e0THds93rhlABnvhkElbSD/ypsUsX+DRbjiVrV5gTwVRg+5Qmu754BUPrbt14awO > 4yLWqV7NN2oOglZy2BTN1WTECOzODRVyxlb3AAL+KWoc0L2QzfRErY5t6ZbIYf2C > +8jXgf6iFl6eLDlecWcrHds/rl1A5w+MP1I+EjozMnjejEjUOuVyq4B80YmAquPL > 6BB76CyjZnpJjvGLijVU4RrD1vduKlMsy4dh7gQaVTQ+SvrQktrFbEcTy2Gj/Jir > LVQagYPSqpcRwLvd0sOGxkipKqIjDi7v8huc+jGmUCFpBcMwJPndzNwuBmJUEGhp > QM0VeYHDugZ1+GWVrxDcjAsYKjwjm/qdjP/1el3a9rgMVYrmxHKobiuqYklIWtw6 > mp7gzdzwMwUNOX8hHCL21ojStlUs5BbzZQ8X8h8a7sX9iQGcBBgBAgAGBQI+4M2c > AAoJEMiAKQuuCE8d4LYL/iUOcqAT3enonrSOu9v8SGKqEc6z7H/5f0t7vZxREVqJ > PIEL/Lj5787NouhtZ+k7KBz4Ssu2lmOA63PUXtSllQx8mg/Jb2PUrjUVLCr22WqA > mr3zAQQ/14B5cLkhnpSID0oQL5UyP7dZ4beUWB3wYydp/hbOLl7+OrP+2EpIopYB > Mdk383GsnN2wWP9pEEDhJ1Lt7DsWuNV/ATZ9yWIvs82s8QiGvWfKbYSHvvzIKAET > UkPD7uWU3IdXgm9kuQQ7TNqX6q857PAC3SK+b+qepmyGDJtoeYS19WsxfqZr2Iot > i75/zy43w9bhbX17JNQynaMsAP4nG+HHzvnSEp8p0s38Cz5xi6xVb8fig6g3WFwn > 6OdZakQ8sI+DyhsrdwlgSCNQTsi85X7Opv8Q+8EQwt+QBTF85O5RjO1Szacsedvl > RXSIWXj8vl8TJZ1VsEOBehdSjAjpUJMUHAoq9c69H5ynXzFrVwOWCwfAYcrFNsmX > hN0wyp3I8BVY5rjH33DQTA== > =ehLR > -END PGP PUBLIC KEY BLOCK- > > > -BEGIN PGP PUBLIC KEY BLOCK- > Version: GnuPG v1.0.6 (MingW32) > Comment: For info see http://www.gnupg.org > > mQGiBDyHxtYRBACZ0tjwBxGJZgu/xVMwgCCUdzXcwMlt4xym2Vx0ZZ6bDJWDVlfa > U/BvSVrrGGgkuYt2fFOeboYIVqW5OsQKJX5a6eZbywkhiK9CehDoh0Ask0hTgyzf > C+kBldozpSv2adBeD4shv8E6mPFsAaA1N7wOIYE6dOuRJBAPIjeZ/ziFxwCg8kaX > r59ZEWL2dD4RISap5
Bug#744091: synaptic: Synaptic can't use cdrom repositories, after installing ia32 package (on amd64).
Package: synaptic Version: 0.75.13 Severity: normal Dear Maintainer, After installing ia32 package, Synaptic is no longer able, to use cdrom as a repository. Synaptic keeps giving warnings like: "Failed to fetch cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official amd64 DVD Binary-1 20130504-14:44]/dists/wheezy/contrib/binary-amd64/Packages Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs Failed to fetch cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official amd64 DVD Binary-1 20130504-14:44]/dists/wheezy/main/binary-amd64/Packages Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs Some index files failed to download. They have been ignored, or old ones used instead". Adding the i386 cdrom (with "apt-cdrom add"), doesn't help. The only solution possible (also recommended at Debian fora), is commenting-out the cdrom repository and continue with the online ones. Of course this way you have to redownload the packages to install, even if you already have them on the cd. Bye! :-) G. -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages synaptic depends on: ii hicolor-icon-theme 0.12-1 ii libapt-inst1.5 0.9.7.9+deb7u1 ii libapt-pkg4.12 0.9.7.9+deb7u1 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-38+deb7u1 ii libcairo2 1.12.2-3 ii libept1.4.121.0.9 ii libfontconfig1 2.9.0-7.1 ii libfreetype62.4.9-1.1 ii libgcc1 1:4.7.2-5 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-5 ii libgtk2.0-0 2.24.10-2 ii libpango1.0-0 1.30.0-1 ii libstdc++6 4.7.2-5 ii libvte9 1:0.28.2-5 ii libx11-62:1.5.0-1+deb7u1 ii libxapian22 1.2.12-2 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages synaptic recommends: pn libgtk2-perl ii policykit-1 0.105-3 pn rarian-compat pn software-properties-gtk Versions of packages synaptic suggests: ii apt-xapian-index 0.45 pn deborphan pn dwww ii menu 2.1.46 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741573: Two menu systems
Le Wed, Apr 09, 2014 at 11:34:51PM +0100, Ian Jackson a écrit : > > It is the demotion of the traditional menu from "should" to "can" > which is controversial. For the reasons I have already explained, I > do not agree with that. Hi Ian, yes, it is that part that is controversial, and I would appreciate if the TC would focus on it, since this was the original topic of #707851, entitled “soften the wording recommending menu files”. The underlying question is: who should spend the time writing these files and keeping them up to date ? In the case of missing manual pages, the policy (§ 12.1) does not require the package maintainer to write one. As a general principle, I think that this is the right way. Pacakge maintainers are volunteers, and we should be careful to avoid loading them with extra work. Therefore, I think that the “should” of §9.6, paragraph 2 should be relaxed. Needless to say, patches carrying Debian menu entries should be accepted. Have a nice day, -- Charles Plessy 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#100808: Votre prêt la solution a tout
Bonjour Monsieur/Madame, Vous aviez besoin de prêt d'argent entre particuliers pour faire face aux difficultés financières pour enfin sortir de l'impasse que provoquent les banques, par le rejet de vos dossiers de demande de prêt ? Je suis un particulier d'experts financiers en mesure de vous faire un prêt au montant dont vous avez besoin et avec des conditions qui vous faciliteront la vie. Mon prêt est disponible aux entreprises, sociétés et toute personne de bonne moralité. Voici les domaines dans lesquels je peux vous aider: Financier, Prêt immobilier ; Prêt à l'investissement ; Prêt automobile, Dette de consolidation ; Marge de crédit ; Deuxième hypothèque ; Rachat de crédit ; Prêt personnel Vous êtes fichés, interdits bancaires et vous n'avez pas la faveur des banques ou mieux vous avez un projet et besoin de financement, un mauvais dossier de crédit ou besoin d'argent pour payer des factures, fonds à investir sur les entreprises. Alors si vous avez besoin de prêt d’argent n'hésitez pas à me contacter sur mon adresse qui est le suivant E-mail : preteur_fauster.da...@financier.com Pour en savoir plus sur mes conditions bien favorables. Alors je suis la solution de vos problèmes financier j'offre de 2.000€ à 5. 000. 000€. Avec une garantie bien étudier. FAUSTER DAVID CLAUD -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744087: pluma: does not start - missing scheme installation
Hello Norbert! On 04/10/2014 01:10 AM, Norbert Preining wrote: > thanks for packaging mate, I really want to use some of its components, > but unfortunately none of them do start: You should rather use the packages from the Mate upstream repositories for the time being since the packaging is still work-in-progress. As you may know, Mate is split over several dozen packages and it is practically impossible to package and upload all associated packages within a short time frame and breakage is therefore to be expected. As for pluma, the package was just accepted into unstable as of yesterday and is due to be upgraded to the latest upstream version 1.8.0 within the next days. The reason why pluma is still on version 1.6.2 is because it has been in the NEW queue for quite a long time and was packaged and uploaded before Mate 1.8.0 was released. The idea was simply to wait until packages in NEW would have been accepted before uploading the new 1.8.0 upstream versions. Thus, just wait a few days for pluma to be updated. Hope that helps! 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#744090: aptitude: Crashes occassionally in TUI if /sys is not mounted: Uncaught exception: Unable to read from stdin: No such file or directory
Package: aptitude Version: 0.6.10-1 Severity: normal Control: found -1 0.6.8.2-1.2 Hi, To demo the aptitude TUI, I occassionally run it in a fresh chroot (without my individual settings), usually with "cowbuilder --login". cowbuilder/pbuilder mounts /proc and /dev/pts, but doesn't seem to mount /sys. In such an environment, aptitude crashes occassionally during interactive usage as follows: root@nemo2:/# aptitude -u Uncaught exception: Unable to read from stdin: No such file or directory root@nemo2:/# Some more details: * Does not crash immediately, but within minutes of normal interactive usage. * "-u" seems not relevant. * Not sure what exactly triggers it. Seems to also happen when I don't touch any keys, but I'm not 100% sure. * Does not happen if I mount /sys inside the chroot with "mount -t sysfs none /sys" beforehand. * Already happenend with 0.6.8.2-1.2 back in November, but I'm not sure if it crashed with the same error message. IIRC it segfaulted back then. Didn't have time to investigate back then as it initially happened during a presentation. -- Package-specific info: Terminal: eterm-color $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.6.10 compiled at Feb 20 2014 18:22:07 Compiler: g++ 4.8.2 Compiled against: apt version 4.12.0 NCurses version 5.9 libsigc++ version: 2.2.11 Ept support enabled. Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 5.9.20140118 cwidget version: 0.5.17 Apt version: 4.12.0 aptitude linkage: linux-gate.so.1 (0xb778e000) libapt-pkg.so.4.12 => /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12 (0xb7215000) libncursesw.so.5 => /lib/i386-linux-gnu/libncursesw.so.5 (0xb71dd000) libtinfo.so.5 => /lib/i386-linux-gnu/libtinfo.so.5 (0xb71ba000) libsigc-2.0.so.0 => /usr/lib/i386-linux-gnu/libsigc-2.0.so.0 (0xb71b4000) libcwidget.so.3 => /usr/lib/i386-linux-gnu/libcwidget.so.3 (0xb70b) libept.so.1.aptpkg4.12 => /usr/lib/i386-linux-gnu/libept.so.1.aptpkg4.12 (0xb7057000) libxapian.so.22 => /usr/lib/sse2/libxapian.so.22 (0xb6e5d000) libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xb6e43000) libsqlite3.so.0 => /usr/lib/i386-linux-gnu/libsqlite3.so.0 (0xb6d84000) libboost_iostreams.so.1.54.0 => /usr/lib/i386-linux-gnu/libboost_iostreams.so.1.54.0 (0xb6d6b000) libpthread.so.0 => /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 (0xb6d4f000) libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb6c66000) libm.so.6 => /lib/i386-linux-gnu/i686/cmov/libm.so.6 (0xb6c1f000) libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb6c03000) libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb6a58000) libutil.so.1 => /lib/i386-linux-gnu/i686/cmov/libutil.so.1 (0xb6a54000) libdl.so.2 => /lib/i386-linux-gnu/i686/cmov/libdl.so.2 (0xb6a4f000) libbz2.so.1.0 => /lib/i386-linux-gnu/libbz2.so.1.0 (0xb6a3c000) liblzma.so.5 => /lib/i386-linux-gnu/liblzma.so.5 (0xb6a15000) libuuid.so.1 => /lib/i386-linux-gnu/libuuid.so.1 (0xb6a0f000) librt.so.1 => /lib/i386-linux-gnu/i686/cmov/librt.so.1 (0xb6a06000) /lib/ld-linux.so.2 (0xb778f000) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (900, 'testing'), (899, 'testing-proposed-updates'), (600, 'stable'), (500, 'proposed-updates'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.14-rc7-686-pae (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages aptitude depends on: ii aptitude-common 0.6.10-1 ii libapt-pkg4.121.0 ii libboost-iostreams1.54.0 1.54.0-5 ii libc6 2.18-4 ii libcwidget3 0.5.17-1 ii libept1.4.12 1.0.12 ii libgcc1 1:4.8.2-18 ii libncursesw5 5.9+20140118-1 ii libsigc++-2.0-0c2a2.2.11-3 ii libsqlite3-0 3.8.4.1-1 ii libstdc++64.8.2-18 ii libtinfo5 5.9+20140118-1 ii libxapian22 1.2.17-1 ii zlib1g1:1.2.8.dfsg-1 Versions of packages aptitude recommends: pn apt-xapian-index ii aptitude-doc-en [aptitude-doc] 0.6.10-1 ii libparse-debianchangelog-perl 1.2.0-1 ii sensible-utils 0.0.9 Versions of packages aptitude suggests: ii debtags 1.12 ii tasksel 3.20 -- no debconf information
Bug#744089: xemacs21: watchfile with pgp signature support
Source: xemacs21 Severity: minor Tags: patch I've attached a patch that adds a watchfile to this package and includes the public key of Vin Shelton, the upstream release manager, to allow for automatic signature verification of the package. -- David Gilman :DG< http://gilslotd.com diff -rN xemacs21-21.4.22/debian/upstream/signing-key.asc xemacs21-21.4.22-diff/debian/upstream/signing-key.asc 0a1,27 > -BEGIN PGP PUBLIC KEY BLOCK- > Version: GnuPG v1.2.3 (GNU/Linux) > > mQGiBDgmQr8RBACq4lv9swh10sbb36vtWNKEluKRieh+/WMrMQKpTLAGNVpZeTBi > nh2MhwRaG6H1ztLsNdafyew5uXcDkDHKQ4TZ4s7T4Jn2n0jfsmiYYTmW0rXCapoQ > Lyki8YJy/aiVjnt/6vfX47RDhd46I+1fFjyD36SbD85Z6ulH8poDAiFV/wCgyvXM > uBZIdWqAxlU+JFhQSA/vE6UEAKFWBd4bgPuB0o9o5bBAMY99viwEYzd+GHMQmQri > pDrfKeBAsRdV2ah8TKQHyVRtbV0oxJ2Lihz4w8cmdJrRfe1XvSmjS+zjWuL/+9ms > Hh9N9TNH245/IEfhkG82PwFKg+6rm4hnP4XQiz9UNm5VVJwP/2e5kt9Pxq7CIZHO > fJZXA/9MuzvnztEwc/xqFt4Pjrvu2jqlAVmzFzMTcE2E45i2XWhiEaznFkFRpQkL > Xqh8XlcOHWVoCzY0ZRIRXHjPa01nGucd/vKacCcAyMs4ciiKQRhNyye8UFLxICq6 > 5rpnr4OsOGNiHQjeX2yJMxly/3X2Giyyt0oO5MF6CDPVRvcEzrQmVmluIFNoZWx0 > b24gPGFjc0BhbHVtbmkucHJpbmNldG9uLmVkdT6IVQQTEQIAFQUCOCZCvwMLCgMD > FQMCAxYCAQIXgAAKCRBIi2lbnMHxZ6HlAJ46shq1JbNesHtE+XNcG0evyHgK/ACe > IpzcsvySvSaF3URRb5O9I1Cq+xC0HFZpbiBTaGVsdG9uIDxhY3NAeGVtYWNzLm9y > Zz6IVQQTEQIAFQUCOCZDJwMLCgMDFQMCAxYCAQIXgAAKCRBIi2lbnMHxZ1vGAKCW > Hp24jPBgh3xbC5GjLIAWxh5URwCgjxtFpiQx1TU9ZEG9OysQjUJ6VzW5AQ0EOCZC > xBAEAOwZoWWbsJA6jfMS8GirIRk46f3ADG8ccKlm5Wge7V1kreaZt0Fhx1xdBEjl > RrtBSWCVvx3S6PDkE/taR74lPBlP4S49JfpAgNkntz5eJvP62BNPoLapqWdJ+wBY > 5Dr09yOwYHdOQw3qQTHCPx1uVJECFB7WTC83Ep/IYQAlkgu7AAMFBACPK3HpjyT+ > ESflUZ+x5wXH9HfnTpcYKn6dfOCbKrPXWfd7Rdr9wKaBOwcGf32qsqpggVyOQJou > CRNC30z92iIlekpzDD/EM7sFzW4D4Ex5kU0dIGm3K7A3CJpyd70a6q7bsUH7iNu9 > lCrie4C0KX4ODDNWodBnoHV+SiPVkLqNLIhGBBgRAgAGBQI4JkLEAAoJEEiLaVuc > wfFnFh0Ani3SpSruAjpZt048ELhd2Neh1z0PAKCljpHmfXMbZ6iQ5mHnKx2ZqjwE > TQ== > =dSmc > -END PGP PUBLIC KEY BLOCK- diff -rN xemacs21-21.4.22/debian/watch xemacs21-21.4.22-diff/debian/watch 0a1,2 > version=3 > opts=pgpsigurlmangle=s/$/.asc/ http://ftp.xemacs.org/xemacs/stable/xemacs-([\d\.]*)\.tar\.bz2
Bug#743912: works for me / unreproducible /moreinfo
Hi Rogério, On Donnerstag, 10. April 2014, Rogério Brito wrote: > Do you want to take part in the maintenance of usbmount? no, sorry. I just noticed the bug during my "usual" RC bug triage, working on keeping the RC bugs in stable usable: http://udd.debian.org/bugs.cgi?release=wheezy&rc=1 (Bugs with no version information show up there, even if they dont affect wheezy. I then tag them accordingly and make them go away there, so people fixing RC bugs in stable have a clearer view...) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#744088: xdmf: wrong Homepage: in control file
Source: xdmf Severity: minor The Homepage: field in the control file points to http://www.xmdf.org/ which is a different project. You want it to point to http://http://www.xdmf.org/ . -- David Gilman :DG< http://gilslotd.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743912: works for me / unreproducible /moreinfo
Thanks Holger and other users.
On Apr 09 2014, Holger Levsen wrote:
> I cannot reproduce this here and I also know many people for whom this works,
> so I downgraded your bugreport and tagged it as I did. This does not mean
> that
> I don't think you're having the problems you've been describing! :-)
>
> Please provide more info about your system, I could well imagine this is
> either a hardware problem or your particular usb subsystem has indeed
> problems
> (which I believe is less likely, but possible),
>
> For a start, the dmesg output as well as lsusb output will be
> useful. Thanks!
Do you want to take part in the maintenance of usbmount? I've been more
interested in other packages lately and I was thinking of working in it
together with others via a RFH or even a RFA.
udev has changed a lot in the last few years and I have to relearn it every
time I have to address some problem.
Thanks,
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744087: pluma: does not start - missing scheme installation
Package: pluma Version: 1.6.2+dfsg1-1 Severity: grave Justification: renders package unusable Dear Mate Devs, thanks for packaging mate, I really want to use some of its components, but unfortunately none of them do start: $ pluma (pluma:11846): GLib-GIO-ERROR **: Settings schema 'org.mate.lockdown' is not installed Same with eom and any other mate program. It seems that some dependencies are missing Thanks Norbert -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14.0-wlsony+wirelesstesting+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pluma depends on: ii iso-codes 3.52-1 ii libatk1.0-02.12.0-1 ii libc6 2.18-4 ii libcairo2 1.12.16-2 ii libenchant1c2a 1.6.0-10 ii libfontconfig1 2.11.0-5 ii libfreetype6 2.5.2-1 ii libgdk-pixbuf2.0-0 2.30.6-1 ii libglib2.0-0 2.40.0-2 ii libgtk2.0-02.24.23-1 ii libgtksourceview2.0-0 2.10.5-1 ii libice62:1.0.8-2 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-01.36.3-1 ii libpangoft2-1.0-0 1.36.3-1 ii libpython2.7 2.7.6-8 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.6.2-1 ii libxml22.9.1+dfsg1-3 ii pluma-common 1.6.2+dfsg1-1 Versions of packages pluma recommends: ii mate-dialogs 1.8.0+dfsg1-2 pluma suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744086: libmate-desktop-dev: please fix dependency specifications
Package: libmate-desktop-dev
Version: 1.8.0+dfsg1-3
Severity: serious
Justification: Policy 8.4
Control: affects -1 src:eom
As it stands, mate-desktop-2.0.pc specifies
Requires: gtk+-2.0 libstartup-notification-1.0 dconf
but libmate-desktop-dev's only -dev dependency is on
libstartup-notification0-dev; this discrepancy makes eom FTBFS.
Judging by its headers' #include directives, I'd suggest specifying
Requires: gdk-pixbuf-2.0 gtk+-2.0
Requires.private: dconf libstartup-notification-1.0
and
Depends: ${misc:Depends}, libmate-desktop-2-17 (= ${binary:Version}),
libgdk-pixbuf2.0-dev, libgtk2.0-dev
Could you please look into doing so?
Thanks!
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libmate-desktop-dev depends on:
ii libmate-desktop-2-17 1.8.0+dfsg1-3
ii libstartup-notification0-dev 0.12-3
libmate-desktop-dev recommends no packages.
libmate-desktop-dev suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744085: ctn: fails to build with clang instead of gcc
Source: ctn
Version: 3.2.0~dfsg-1
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs
Dear Maintainer,
Your package fails to build with clang instead of gcc. [-Wreturn-type]
The attached patch fixes it.
Buildlogs and patch are here:
https://github.com/nonas/debian-clang/tree/master/buildlogs/ctn
Regards,
Nicolas
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Description: fix FTBFS with clang instead of gcc
Author: Nicolas Sévelin-Radiguet
Last-Update: 2014-04-10
--- a/apps/image_archive/queue.c
+++ b/apps/image_archive/queue.c
@@ -242,7 +242,7 @@
COND_DumpConditions();
}
-
+void
queueDisplayImage(const char* node, const char* name)
{
CONDITION cond;
Bug#727629: Problem persists - No solution found
Hello I still could not solve the problem. I am using Windows 8.1 and I really need to fix this issue in order to come back to Debian. Is there any news regarding the solution of the problem?
Bug#722084: obsolete ruby1.9.1
Chiming in on this, we've started removing ruby1.9.1. Please add it to the list of obsolete packages. More info can be found in the release bug #739611. Thanks, -- ,''`. Christian Hofstaedtler : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpPBR9uYWcSD.pgp Description: PGP signature
Bug#741573: Two menu systems
Sam Hartman writes ("Bug#741573: Two menu systems"):
> So, I'd like to request the TC to first consider whether a consensus was
> reached in the process and if so whether there's a compelling reason not
> to respect that consensus. If no consensus was reached or the TC finds
> it has a compelling interest not to respect that consensus, then
> focusing on the technical details of the policy seems reasonable.
> In my opinion, not respecting the project as a whole enough to make a
> determination about consensus does significant harm.
This is hardly the first time that a matter has come to the TC after a
dispute has escalated to acts (on one or both sides) whose legitimacy
is disputed. I doubt it will be the last. Our approach has always
been to look at the underlying dispute and try to resolve it.
So, no. The TC will not make decisions about the content of policy on
the basis of an adjudications about the policy process. We will rule
on the underlying question(s), on the merits.
(In my view, the menu question should have been referred to the TC
much sooner.)
The legitimacy of the actions of the policy maintainers is a matter
for the policy team as a whole, and in extremis for the DPL (given
that the policy team are DPL delegates). However I would strongly
encourage everyone not to dwell on the alleged wrongs of the
disputants. Such discussions are unpleasant and almost always
unproductive.
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744084: ejabberd: add status action to init script
Package: ejabberd
Version: 2.1.10-4+deb7u1
Tags: patch
The ejabberd init script does not have a "status" action. This prevents it
from giving a meaningful response, for example, to "service --status-all".
Other tools out there (e.g. salt) also expect "status" to exist, though I
realize that doesn't mean "status" should definitively be implemented.
The attached patch simply adds a "status" action that simply uses "ctl
status" (i.e. ejabberdctl status) to check and report the status.
-Steve
=== modified file 'init.d/ejabberd'
--- init.d/ejabberd 2010-03-23 21:16:58 +
+++ init.d/ejabberd 2014-04-09 22:41:49 +
@@ -133,8 +133,15 @@
live
fi
;;
+status)
+ if ctl status ; then
+ echo -n "ejabberd is running"
+ else
+ echo -n "ejabberd is stopped"
+ fi
+;;
*)
- echo "Usage: $0 {start|stop|restart|force-reload|live}" >&2
+ echo "Usage: $0 {start|stop|restart|force-reload|live|status}" >&2
exit 1
;;
esac
Bug#729699: debconf: no longer appearing in my installer log with most recent cdimage / non-free / weekly / amd64 / testing iso
Package: debconf Followup-For: Bug #729699 Dear Maintainer, Hi, just reporting that my most recent install log no longer contains this error message. However the code Kibi pointed out still remains the same... Thanks -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debconf depends on: ii perl-base 5.18.2-2+b1 Versions of packages debconf recommends: ii apt-utils 0.9.16.1 ii debconf-i18n 1.5.52 Versions of packages debconf suggests: pn debconf-doc ii debconf-utils 1.5.52 ii libgtk2-perl 2:1.249-2 pn libnet-ldap-perl pn libqtcore4-perl pn libqtgui4-perl pn libterm-readline-gnu-perl ii perl 5.18.2-2+b1 ii whiptail 0.52.15-3+b1 -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741573: Two menu systems
Didier 'OdyX' Raboud writes ("Bug#741573: Two menu systems"):
> Le mercredi, 9 avril 2014, 15.00:44 Ian Jackson a écrit :
> > Right. I understand that some people don't think the comprehensive
> > menu is useful. However, there are a lot of things in Debian that
> > some people think aren't useful. The usual principle is that if
> > someone thinks something useful and wants to do the work to provide
> > it, they should be able to do so.
>
> I think this is allowed by the patch pointed by Charles, which adds the
> following paragraph to the policy:
...
> As I read it, the complete patch is essentially the addition of a 'desktop'
> menu 'should' and a s/should/can/g for the 'trad' menu. That patch got its
> three seconds within the usual Policy process but got (fully) reverted by
> Bill.
It is the demotion of the traditional menu from "should" to "can"
which is controversial. For the reasons I have already explained, I
do not agree with that.
> > There are significant advantages to use of a longstanding file format.
> >
> > These advantages are more important in the widely-consumed trad menu
> > than they would be in the less-widely-consumed but more sophisticated
> > desktop menu.
>
> Your assertions about how widely the two menu systems are consumed
> seem quite bold to me and are at least not backed by Cyril numbers
> in 741573#35 [0].
By "widely consumed" I meant that a wide range of different window
managers are capable of displaying the traditional menu.
But it seems that you interpreted my comment as referring to the use
of the trad menu by end users, and I want to respond to that. Of
course we don't know how often end users actually click on the trad
menu and use it to find and launch programs. So I won't assert that
it's "widely used". Equally, assertions that it's not used by end
users are unjustified. We don't know how widely it's used.
We do have testimonial evidence from individual people saying they
find it useful, and we have the evidence from the people working on
providing the trad menu that they think it's a good thing to keep on
using. For me, that is enough to say that we should continue to allow
those people who care about it to work on it.
Of course Cyril's message #35 that you refer to doesn't talk about the
consumption of the trad menu at all. It talks only about the _supply_
of menu entries.
Some maintainers want to declare the trad menu obsolete and abolish
it, and have been reluctant to include trad menu entries or have
removed them, contrary to policy and indeed thus sabotaging the work
of the trad menu maintainers. It is gratifying to see that this
doesn't seem to be widespread, looking at Cyril's statistics.
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744083: RFS: spatialite-tools/4.1.1-4
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "spatialite-tools". Package name: spatialite-tools Version : 4.1.1-4 Upstream Author : Alessandro Furieri URL : https://www.gaia-gis.it/fossil/spatialite-tools/ License : GPL-4.0+ Section : science It builds those binary packages: spatialite-bin - Geospatial extension for SQLite - tools To access further information about this package, please visit the following URL: http://mentors.debian.net/package/spatialite-tools Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/spatialite-tools/spatialite-tools_4.1.1-4.dsc More information about spatialite-tools can be obtained from https://www.gaia-gis.it/fossil/spatialite-tools/. Changes since the last upload: * Add patch to not require an extact match between the sqlite3 header and source for spatialite to run. (closes: #743999) * Drop lintian override for no-upstream-changelog, shouldn't override pedantic tags. Regards, Sebastiaan Couwenberg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744082: ITP: wolfssl-jni -- Java interface for CyaSSL
Package: wnpp Severity: wishlist Owner: Felix Lechner * Package name: wolfssl-jni Version : 1.0 Upstream Author : Chris Conlon * URL : http://www.wolfssl.com/ * License : GPL-2+ Programming Lang: Java, C Description : Java interface for CyaSSL The wolfSSL JNI package provides a Java interface to the wolfSSL SSL/TLS library, providing Java applications with SSL/TLS support up to the current TLS 1.2 and DTLS 1.2 standards. In addition to the interface, the package provides an example client and server, written in Java, which utilize the interface to make an SSL/TLS connection. The interface is provided through the use of JNI and standard Java practices. CyaSSL is an SSL library offering a compatibility layer for OpenSSL. It is popular with developers of embedded systems. 'cyassl' is a prerequisite for this JNI package. The two packages are released separately. I plan to maintain both of them. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744007: network-manager: Since recent update after closing the lid of laptop I need to restart NetworkManager
I could reproduce this on my system, too. It only happens when closing the lid, not when suspending, or issuing a lock of the gnome session. I don't need modemmanager, so I 'dpkg-reconfigure modemmanager', 'apt-get remove purge' it, and 'dpkg-reconfigure network-manager', but the issue keeps happening. Workaround found by MeanEYE on #Debian: Suspend the laptop with the lid open, close the lid. Open the lid, and resume; the interfaces should be up. signature.asc Description: OpenPGP digital signature
Bug#684306: Incorrect Bug title rechanged
Hi, I think that Holger Levsen did a mistake because [1]: Changed Bug title to 'GNOME/GDM fails to run on ibook G4' from 'general: Any USB card reader works only after being replugged.' Request was from Holger Levsen to cont...@bugs.debian.org. (Fri, 03 Jan 2014 10:51:05 GMT) Full text and rfc822 format available. when this bug is clear that the correct bug title is: Any USB card reader works only after being replugged. Anyway, I have changed again the title. And I can confirm this bug with 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux I think that it's something related with the usb-storage module. If you remove the module and load again then my memory card is detected. Also, #684306 AFAIK is the same bug. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733651 -- -- Linux User 152692 PGP: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744081: FTBFS: minitest/unit.rb:28:in const_missing: uninitialized constant MiniTest::Test (NameError)
Source: ruby-escape-utils Version: 1.0.1-1 Severity: serious Justification: fails to build from source Dear Maintainer, your package is failing to build on the buildds: /bin/mkdir -p . ./.gem.20140409-24791-u8yi50/escape_utils exit > .RUBYARCHDIR.-.escape_utils.time /usr/bin/install -c -m 0755 escape_utils.so ./.gem.20140409-24791-u8yi50/escape_utils make[1]: Leaving directory `/«PKGBUILDDIR»/ext/escape_utils' Running tests for ruby2.0 using debian/ruby-tests.rb... /usr/lib/ruby/2.0.0/minitest/unit.rb:28:in `const_missing': uninitialized constant MiniTest::Test (NameError) from /«PKGBUILDDIR»/test/html_safety_test.rb:29:in `' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from debian/ruby-tests.rb:1:in `block in ' from debian/ruby-tests.rb:1:in `each' from debian/ruby-tests.rb:1:in `' ERROR: Test "ruby2.0" failed. Exiting. dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-escape-utils returned exit code 1 make: *** [binary-arch] Error 1 This happened on all archs that managed to attempt a build so far, see: https://buildd.debian.org/status/package.php?p=ruby-escape-utils -ch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743128: network-manager: NM does not work (without systemd)
I'm still on network-manager 0.9.8.8-4 and it has been working fine for me without systemd. "nmcli c" lists all of my connections but only if I run it as root otherwise I get the same WARNING as the one that the Ralf posted. I'm also using KDE and haven't had any problems with the NetworkManager applet (/usr/sbin/NetworkManager is of course running as root). As far as I can tell, the problem reported by Ralf in this bug reports actually relates to bug #743159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743159 Would you be able to remove the dependency on systemd and change it back to "Recommends"? Kind regards, David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#739172: [apper] apper isn't able to retrieve the changelogs
good workaround, but this means that the url is hardcoded in the software if I can to suggest: (for example, the network-manager package) the wrong url is http://packages.debian.org/changelogs/main/n/network-manager/network-manager_0.9.8.8-5_changelog the correct url (retrived by apt-get and aptitude) is http://packages.debian.org/changelogs/pool/main/n/network-manager/network-manager_0.9.8.8-5/changelog who redirect to http://metadata.ftp-master.debian.org/changelogs/main/n/network-manager/network-manager_0.9.8.8-5_changelog A good patch must be able to fix the bug by using the 2nd url, that seems to be more correct for the future (but it's my opinion :) ) Many thanks for your time -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744027: data point
On Wednesday 09 April 2014 23:01:30 Joey Hess wrote: [...] > So this is a gamble with not much of a payoff. The payoff is a certificate that is more likely not to have been compromised, and one that is signed by your CA. > I would be quite happy if Debian came with a way to say: > "I don't trust any cert created before heartbleed was announced." Can be done if you hack X509_verify and equivalent functions when they check the validity of the certificate. Not that I suggest that I am going to implement it or that I would be in favor of such a check. I believe that it would be an overreaction. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743926: fizmo: FTBFS with -B: No rule to make target `install-fizmo-console'
Source: fizmo
Version: 0.7.8-1
Tags: pending
Hi,
many thanks for the reproducibility hint. A fixed version 0.7.8-2 is on the way
to be uploaded.
Christoph.
On 08.04.2014 at 14:57, Cyril Brulebois wrote:
> Source: fizmo
> Version: 0.7.8-1
> Severity: serious
> Justification: FTBFS
>
> Hi,
>
> your package FTBFS on all buildds, and I can reproduce the issue here by
> passing -B to dpkg-buildpackage:
> | dpkg-buildpackage -rfakeroot -D -us -uc -B
> | dpkg-buildpackage: source package fizmo
> | dpkg-buildpackage: source version 0.7.8-1
> | dpkg-buildpackage: source distribution unstable
> | dpkg-buildpackage: source changed by Christoph Ender
>
> | dpkg-source --before-build fizmo-0.7.8
> | dpkg-buildpackage: host architecture amd64
> | fakeroot debian/rules clean
> | dh_testdir
> | dh_testroot
> | dh_auto_clean -v -pfizmo-common -pfizmo-console -pfizmo-ncursesw
> | dh_clean -v
> | rm -f debian/fizmo-common.substvars
> | rm -f debian/fizmo-common.*.debhelper
> | rm -rf debian/fizmo-common/
> | rm -f debian/fizmo-ncursesw.substvars
> | rm -f debian/fizmo-ncursesw.*.debhelper
> | rm -rf debian/fizmo-ncursesw/
> | rm -f debian/fizmo-console.substvars
> | rm -f debian/fizmo-console.*.debhelper
> | rm -rf debian/fizmo-console/
> | rm -f debian/*.debhelper.log
> | rm -f debian/files
> | find . \( \( -type f -a \
> | \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
> | -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
> | -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
> | -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
> | \) -exec rm -f {} + \) -o \
> | \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \)
> \)
> | rm -f *-stamp
> | debian/rules build-arch
> | make: Nothing to be done for `build-arch'.
> | fakeroot debian/rules binary-arch
> | dh_testroot
> | dh_installdirs
> | dh_installchangelogs -pfizmo-console CHANGELOG.txt
> | dh_installdocs -pfizmo-console
> | dpkg-buildflags
> | CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
> -Werror=format-security
> | CPPFLAGS=-D_FORTIFY_SOURCE=2
> | CXXFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
> -Werror=format-security
> | FFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4
> | GCJFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4
> | LDFLAGS=-Wl,-z,relro
> | DESTDIR=/tmp/fizmo-0.7.8/debian/fizmo-console /usr/bin/make
> install-fizmo-console
> | make[1]: Entering directory `/tmp/fizmo-0.7.8'
> | make[1]: *** No rule to make target `install-fizmo-console'. Stop.
> | make[1]: Leaving directory `/tmp/fizmo-0.7.8'
> | make: *** [fizmo-console] Error 2
> | dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit
> status 2
> | debuild: fatal error at line 1364:
> | dpkg-buildpackage -rfakeroot -D -us -uc -B failed
>
> Build logs are available at:
> https://buildd.debian.org/status/package.php?p=fizmo&suite=sid
>
> Mraw,
> KiBi.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744027: data point
On Wed, Apr 09, 2014 at 05:01:30PM -0400, Joey Hess wrote: > > And then, browsers don't check SSL cert revocations, and the infrastructure to > check reovocations is apparently broken too. The major browser do check OCSP, but they do not import CRLs. The CAs are supposed to be providing OCSP. However, iceweasel/firefox by default is happy to ignore a OCSP timeout. You need to turn it on that it doesn't allow a timeout. I have no idea why they use that as default. You can change it in edit -> preferences -> advanced -> certificates -> validation: check both boxes. I think by default only the first is checked. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744014: python3-pyparsing: ParseBaseException.markInputline() - "".join() given more than one argument
Control: reassign -1 src:pyparsing 2.0.1+dfsg1-1 On Mi, 09 apr 14, 20:44:03, Matthew Grant wrote: > Source: python3-pyparsing > Version: 2.0.0+ ? > Severity: normal > Tags: upstream patch > > Dear Maintainer, > >Working on pPython3 program which quite seriously uses PyParsing >When ever displaying error Parsing output, an Exception is thrown: > >File "/usr/share/dms/dms/app/zone_tool.py", line 2251, in do_edit_zone > print(exc.markInputline(), file=self.stdout) >File "/usr/lib/python3/dist-packages/pyparsing.py", line 207, > in markInputline > markerString, line_str[line_column:]) > TypeError: join() takes exactly one argument (3 given) > > Added missing () or [] around arguments, producing an iterable, and > everything worked, and I got line by line parsing errors with position > display happening. > > > -- System Information: > Debian Release: jessie/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Index: pyparsing-2.0.1+dfsg1/pyparsing.py > === > --- pyparsing-2.0.1+dfsg1.orig/pyparsing.py 2013-07-17 19:08:10.0 > +1200 > +++ pyparsing-2.0.1+dfsg1/pyparsing.py2014-04-09 18:37:03.991046822 > +1200 > @@ -203,8 +203,8 @@ > line_str = self.line > line_column = self.column - 1 > if markerString: > -line_str = "".join(line_str[:line_column], > -markerString, line_str[line_column:]) > +line_str = "".join([line_str[:line_column], > +markerString, line_str[line_column:]]) > return line_str.strip() > def __dir__(self): > return "loc msg pstr parserElement lineno col line " \ -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#735833: Bug#739598: pystache not migrating to testing due to FTBFS
Hi, Thomas. Thanks for your advice. I fixed and uploaded to mentors.d.n. Would you upload this package? http://mentors.debian.net/debian/pool/main/p/pystache/pystache_0.5.3-3.dsc Best regards, -- Kouhei Maeda KeyID 4096R/7E37CE41 2014-03-18 0:45 GMT+09:00 Thomas Goirand : > Hi Kouhei, > > I've notice that it's been a long time that pystache has RC bugs. The > issue on the package is that you are calling "2to3 -w --no-diffs build3" > in override_dh_auto_build:, but setup.py is already doing it, so you are > doing it twice, which is breaking some unicode strings. > > This let me wonder if the 2to3 call in override_dh_auto_install: is > necessary, probably it also break stuff. > > Also, I've noticed some problems in your package. First, you shouldn't set: > X-Python-Version: 2.7, >= 3.3 > > Yes, we don't have python 3.2 in Sid/Testing, but the package is still > compatible with Python 3.2, as per the declaration in setup.py. > Therefore, by setting-up X-Python-Version: 2.7, you are preventing the > package from being back-ported correctly in Wheezy. Also, > X-Python-Version: >= 3.3 has no effect: it's X-Python3-Version that you > should have used to limit Python 3 versions. > > Last, there's no need to add "&& \" on each lines of your debian/rules. > The build will stop on the first error anyway. > > Please fix the above. If you need sponsoring for the upload of the fixed > package, please let me know, and I will upload for you. > > If you can't do the work, please let me know, and I will NMU the package. > > Cheers, > > Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744040: RFP: libbdplus -- research project to implement the BD+ System Specifications
Control: reassing -1 wnpp Control: severity -1 wishlist Control: retitle -1 RFP: libbdplus -- research project to implement the BD+ System Specifications On Mi, 09 apr 14, 16:10:47, HacKurx wrote: > Package: libbdplus > Version: 0.1.0 > Severity: normal > > Dear Maintainer, > > libbdplus is a research project to implement the BD+ System Specifications. > This research project provides, through an open-source library, a way to > understand how the BD+ works. > NB: this project doesn't offer any key, configuration file or certificate > that could be used to decode encrypted copyrighted material. > > license: LPGL > Latest release is libbdplus 0.1.0 > > Website : > http://www.videolan.org/developers/libbdplus.html > > Bugs in launchpad.net : > https://bugs.lauchpad.net/ubuntu/+bug/1291353 > > Thanks in advance. > > > -- System Information: > Debian Release: jessie/sid > APT prefers testing-updates > APT policy: (500, 'testing-updates'), (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#739172: [apper] apper isn't able to retrieve the changelogs
2014-04-09 22:47 GMT+02:00 Francesco Muzio : > Oops :) > > with your suggested file the command "pkcon get-update-detail packagename" > works! > > but why, for me, only with this file it works? The file seems to be not > provided with no Packagekit's packages. Awesome, thanks for testing! This means that the issue will be fixed with the next revision, which I'll likely upload tomorrow. It's a simple 1-line patch :) > On your machine it works also without /etc/apt/apt.conf.d/21changelog ? I override the configuration anyway due to my work on Tanglu, so I didn't see that bug and made a (wrong) assumption regarding defaults in Debian when fixing the changelog issue in the first place (wouldn't have been an issue if I didn't forget to cherry-pick a patch in PK upstream to the stable branch). Anyway, fixed now - as soon as you have rev2 tomorrow, you can remove the Apt configuration snippet again, if you want. Cheers, Matthias -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744073: scilab shared libraries are heavily underlinked
Am 09.04.2014 22:43, schrieb Sylvestre Ledru: > severity 744073 normal > thanks > > On 09/04/2014 20:49, Matthias Klose wrote: >> Package: scilab >> Version: 5.5.0~beta-1+git~20140406-1522-2 >> Severity: important >> >> please forward this upstream. maybe as separate bug reports for each library >> with unresolvable references. >> > Thanks for sharing. However, I do not agree on the severity. > That does not prevent the package to build under Debian. I don't know > what is different in Ubuntu > and explains the FTBFS there. If you don't care about it in Ubuntu, then please don't file requests to sync the package during deep freeze before the release, and then not addressing the newly introduced build failures. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741361: [Pkg-kde-extras] Bug#741361: Please migrate to xine-lib-1.2
On Thu, Mar 27, 2014 at 04:03:15PM +0100, Moritz Mühlenhoff wrote: > On Sat, Mar 22, 2014 at 10:16:42PM -0300, Lisandro Damián Nicanor Pérez Meyer > wrote: > > tag 741361 moreinfo > > thanks > > > > On Tuesday 11 March 2014 18:14:17 Moritz Muehlenhoff wrote: > > > Source: kaffeine > > > Severity: important > > > > > > Hi, > > > xine-lib is scheduled for removal in jessie. Please build-depend on > > > libxine2-dev instead of libxine-dev (a test compile worked fine for me) > > > > > > The severity will be bumped to RC status in a few weeks/months. > > > > Hi Moritz! If libxine is going to be *removed*, can't you simply make > > libxine- > > dev provide libxine2 stuff? In that way you will only need binNMUs for this > > packages. You normally add the soname to dev packages if you intend to > > provide > > more than one version at the time. > > Note that I'm not the xine-lib maintainer, I'm adding Darren to CC. > > Since there are only three packages still using libxine-dev (plus one which > needs to be removed), simply fixing these three packages and removing the > package might be simpler. kaffeine is now the only package left (beside pyxine, which is filed for removal), so it would be nice if you could either fix this soon or give me the green light to fix it myself (this is indirectly holding the libav10 transition) Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#617309: network-manager: Does not reconnect to Wi-Fi until system restart, after upgrade
Package: network-manager Version: 0.9.8.8-5 Followup-For: Bug #617309 Dear Maintainer, I also experience "suspend" leading to no network on restart. As a workaround, /etc/init.d/network-manager restart I use sysvinit (not systemd yet), a fairly minimal KDE, and startx (not kdm) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages network-manager depends on: ii adduser3.113+nmu3 ii dbus 1.8.0-3 ii init-system-helpers1.18 ii isc-dhcp-client4.2.4-7 ii libc6 2.18-4 ii libdbus-1-31.8.0-3 ii libdbus-glib-1-2 0.102-1 ii libgcrypt111.5.3-4 ii libglib2.0-0 2.40.0-2 ii libgnutls262.12.23-13 ii libgudev-1.0-0 204-8 ii libmm-glib01.0.0-4 ii libnl-3-2003.2.21-1 ii libnl-genl-3-200 3.2.21-1 ii libnl-route-3-200 3.2.21-1 ii libnm-glib40.9.8.8-5 ii libnm-util20.9.8.8-5 ii libpam-systemd 204-8 ii libpolkit-gobject-1-0 0.105-4 ii libsoup2.4-1 2.46.0-2 ii libsystemd-login0 204-8 ii libuuid1 2.20.1-5.7 ii lsb-base 4.1+Debian12 ii policykit-10.105-4 ii udev 204-8 ii wpasupplicant 1.1-1 Versions of packages network-manager recommends: ii crda 1.1.2-1 ii dnsmasq-base 2.68-1 ii iptables 1.4.21-1 ii modemmanager 1.0.0-4 ii ppp 2.4.5+git20130610-4 Versions of packages network-manager suggests: ii avahi-autoipd 0.6.31-4 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744027: data point
StartSSL revoked one of my certs on request the night Heartbleed came out. I mentioned heartbleed in the form. However, that was a $24.90 gamble.. They could just has easily billed me. Especially if you have a lot of different certs, that gamble may not be worth it. Also, I'm a paying customer, having gone through their process to get a wildcard cert. A free customer may have different results. And then, browsers don't check SSL cert revocations, and the infrastructure to check reovocations is apparently broken too. So this is a gamble with not much of a payoff. I would be quite happy if Debian came with a way to say: "I don't trust any cert created before heartbleed was announced." -- see shy jo signature.asc Description: Digital signature
Bug#743995: libc-bin: Error using synaptic: GLib-CRITICAL **: g_child_watch_add_full: assertion 'pid > 0' failed
reassign 743995 synaptic retitle 743995: synaptic: Error using synaptic: GLib-CRITICAL **: thanks On Wed, Apr 09, 2014 at 02:48:38AM +0200, advocatux wrote: > Package: libc-bin > Version: 2.18-4 > Severity: important > > I'm getting this error every time I'm updating a package using synaptic > (GLib-CRITICAL **: g_child_watch_add_full: assertion 'pid > 0' failed). > This is clearly not a glibc bug, reassigning the bug to synaptic. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744079: nmu: spatialite-tools_4.1.1-3
On Wed, Apr 9, 2014 at 22:04:38 +0200, Bas Couwenberg wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > The spatialite program in the spatialite-bin package is currently > unusable as reported in #743999. > > It refuses to run if the version of sqlite3 it was compiled with > doesn't equal the installed sqlite3 version. > > spatialite-tools was built with sqlite 3.8.3 but 3.8.4 is current. > NAK. Please patch out that check instead. Cheers, Julien signature.asc Description: Digital signature
Bug#739172: [apper] apper isn't able to retrieve the changelogs
Oops :) with your suggested file the command "pkcon get-update-detail packagename" works! but why, for me, only with this file it works? The file seems to be not provided with no Packagekit's packages. On your machine it works also without /etc/apt/apt.conf.d/21changelog ? thanks Il 09/04/2014 22:36, Matthias Klumpp ha scritto: 2014-04-09 21:35 GMT+02:00 Francesco Muzio : Unfortunately I haven't this file (or other with similar content) in /etc/apt/apt.conf.d/ :-( Yes, that's why I asked you to create it with the content mentioned before ;-) Cheers, Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744080: wims-moodle: [INTL:de] Updated German debconf translation
Package: wims-moodle Version: 4.0-13 Severity: wishlist Tags: l10n patch Hi, please find attached the newest German translation of wims-moodle. Kind regards, Chris. de.po.gz Description: application/gzip
Bug#744073: scilab shared libraries are heavily underlinked
severity 744073 normal thanks On 09/04/2014 20:49, Matthias Klose wrote: > Package: scilab > Version: 5.5.0~beta-1+git~20140406-1522-2 > Severity: important > > please forward this upstream. maybe as separate bug reports for each library > with unresolvable references. > Thanks for sharing. However, I do not agree on the severity. That does not prevent the package to build under Debian. I don't know what is different in Ubuntu and explains the FTBFS there. Cheers, Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#739172: [apper] apper isn't able to retrieve the changelogs
2014-04-09 21:35 GMT+02:00 Francesco Muzio : > Unfortunately I haven't this file (or other with similar content) in > /etc/apt/apt.conf.d/ :-( Yes, that's why I asked you to create it with the content mentioned before ;-) Cheers, Matthias -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743999: spatialite-bin: spatialite fails to start
Control: tags -1 confirmed Hi, Thanks for reporting this issue. I've requested a rebuild of spatialite-tools to build with the current sqlite3 version (#744079). Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 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#742833: [Pkg-mpd-maintainers] Bug#742833: mpd: fails to start when using systemd
Hi,
> Here's the output of 'systemctl status mpd.service':
>
>mpd.service - Music Player Daemon
> Loaded: loaded (/lib/systemd/system/mpd.service; disabled)
> Active: inactive (dead)
and that's the issue you see: mpd is not configured to start as a system
service on boot ("disabled"). To change that, run 'sudo systemctl enable
mpd.service' (and if mpd was not started, as above, start it now).
I'm not sure why it's not enabled; unless you changed START_MPD to
something other than 'true' in /etc/default/mpd (at which point it
wouldn't have started with sysvinit), it should have been
configured to start with systemd as well...
> Appart from mpdscribble trying to connect without much success nothing
> in syslog. And this fact makes me realize that mpdscribble should
> probably depend on mpd to start ???
If both are running as system services, yes probably. But with per-user
pulseaudio being the default nowadays, it might be a better idea to run
mpd as your own user, from your X session (this happens automatically if
you have an ~/.mpdconf and mpd not running already)...
Florian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744079: nmu: spatialite-tools_4.1.1-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu The spatialite program in the spatialite-bin package is currently unusable as reported in #743999. It refuses to run if the version of sqlite3 it was compiled with doesn't equal the installed sqlite3 version. spatialite-tools was built with sqlite 3.8.3 but 3.8.4 is current. nmu spatialite-tools_4.1.1-3 . ALL . -m "Rebuild with sqlite3 3.8.4" Kind Regards, Bas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744027: Please remove StartCom Certification Authority root certificate
On Wed, 9 Apr 2014, Klemens Baum wrote: StartCom provides cheap and even free SSL certificates via the StartSSL brand. However, certificates revoking cerificates requires a US$ 24.90 fee [3]. This discourages responsible sysadmin procedure and and will ensure many compromised certificates remain in use. I don't believe that any browser or HTTPS client in Debian checks revocations with hard failures if the CRL or OCSP responder is unreachable, so I don't see how this is relevant for decisions regarding Debian's default trust store. The certificate will (it seems) get reissued for free with a new key, so the compromised certificate will not be in use. And an attacker in a position to MITM is also in a position to make the revocation useless: https://news.ycombinator.com/item?id=7556909 https://www.imperialviolet.org/2012/02/05/crlsets.html https://twitter.com/agl__/status/453602748601495553 Multiple commentors on the HN thread you link to imply that StartCom is happy to reissue certs for free, but they charge for revocations, for instance: "The title is misleading. StartCom is asking for its fee for revoking, that's all. Not making revocation free of cost isn't refusal to reissue cert." If they were charging for reissues, there might be an argument here, but even if they didn't do revocations at all, I don't see how that affects security under the threat model used by the Debian packages that use on ca-certificates. As a consequence you can't trust certificates signed by StartCom before 2014-04-07. This only affects certs that were used on vulnerable versions of OpenSSL with allocation schemes that actually loaded the private key into freed memory that could be returned. I haven't seen a valid claim that this is anywhere near a significant fraction of the web. http://blog.erratasec.com/2014/04/why-heartbleed-doesnt-leak-private-key.html https://twitter.com/neelmehta/status/453625474879471616 -- Geoffrey Thomas https://ldpreload.com geo...@ldpreload.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744078: empathy: Empathy crashes at start
Package: empathy Version: 3.8.6-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, When I start empathy, it immediately crashes due to a segfault. The debugger gives: Core was generated by `empathy'. Program terminated with signal 11, Segmentation fault. #0 0x7f2c22793bd4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 (gdb) where #0 0x7f2c22793bd4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2c227966c9 in g_date_time_to_timezone () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2c2279673c in g_date_time_to_utc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2bf54aa302 in _edsf_persona_update () from /usr/lib/x86_64-linux-gnu/libfolks-eds.so.25 #4 0x7f2bf54ab9fe in ?? () from /usr/lib/x86_64-linux-gnu/libfolks-eds.so.25 #5 0x7f2c22a7f2e4 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x7f2c22a814c4 in g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x7f2c22a818a4 in g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x7f2bf54a6672 in edsf_persona_construct () from /usr/lib/x86_64-linux-gnu/libfolks-eds.so.25 #9 0x7f2bf54ae62b in ?? () from /usr/lib/x86_64-linux-gnu/libfolks-eds.so.25 #10 0x7f2bf54b4f93 in ?? () from /usr/lib/x86_64-linux-gnu/libfolks-eds.so.25 #11 0x7f2c227aace5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Seems related to an arch bug: https://bugs.archlinux.org/task/39200?string=glib&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom= -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'stable'), (500, 'testing-updates'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/3 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages empathy depends on: ii dbus-x11 1.8.0-3 ii dconf-gsettings-backend [gsettings-backend] 0.18.0-1 ii empathy-common 3.8.6-1 ii geoclue 0.12.99-3 ii gnome-icon-theme 3.12.0-1 ii gsettings-desktop-schemas3.8.2-2 ii gstreamer1.0-pulseaudio 1.2.3-1 ii libc62.18-4 ii libcairo21.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libchamplain-0.12-0 0.12.7-1+b1 ii libchamplain-gtk-0.12-0 0.12.7-1+b1 ii libcheese-gtk23 3.12.0-1 ii libclutter-1.0-0 1.18.0-2 ii libclutter-gst-2.0-0 2.0.8-1+b1 ii libclutter-gtk-1.0-0 1.4.4-3+b1 ii libcogl-path20 1.18.0-2 ii libcogl201.18.0-2 ii libdbus-glib-1-2 0.102-1 ii libenchant1c2a 1.6.0-10 ii libfarstream-0.2-2 0.2.3-3 ii libfolks-telepathy25 0.9.6-2 ii libfolks25 0.9.6-2 ii libgcr-base-3-1 3.12.0-1 ii libgcr-ui-3-13.12.0-1 ii libgdk-pixbuf2.0-0 2.30.6-1 ii libgee-0.8-2 0.10.5-1 ii libgeoclue0 0.12.99-3 ii libgeocode-glib0 3.12.0-1 ii libglib2.0-0 2.40.0-2 ii libgnutls26 2.12.23-13 ii libgoa-1.0-0 3.8.3-2 ii libgstreamer-plugins-base1.0-0 1.2.3-1 ii libgstreamer1.0-01.2.3-1 ii libgtk-3-0 3.12.0-4 ii libgudev-1.0-0 204-8 ii libmission-control-plugins0 1:5.16.1-1 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.3-1 ii libpulse-mainloop-glib0 4.0-6+b1 ii libpulse04.0-6+b1 ii libsecret-1-00.18-1 ii libsoup2.4-1 2.46.0-2 ii libtelepathy-farstream3 0.6.0-3 ii libtelepathy-glib0 0.24.0-1 ii libtelepathy-logger3 0.8.0-3 ii libwebkitgtk-3.0-0 2.2.6-1 ii libx11-6 2:1.6.2-1 ii libxml2
Bug#744027: Please remove StartCom Certification Authority root certificate
Control: tag -1 wontfix On Wednesday 09 April 2014 15:39:25 Michael Shuler wrote: [...] > If mozilla believes this is justification for removal, which I doubt > will happen, then the same will happen in ca-certificates. Debian > ca-certificates users may remove trust locally at any time, if they > desire. Agreed, so marking it as wontfix. If anything changes upstream, it will be reflected here. For those reading at home don't waste your time, nor ours, sending arguments or "+1"s. If anywhere, do it on mozilla's bugzilla - all the while respecting their policies. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740504: cdimage.debian.org: Released ISO images have invalid GPT tables
Hi, my newest bug about gdisk hating an ISO with GPT and MBR is not affecting debian-cd. (Further it is not GRUB2 specific.) I can reproduce the user's symptoms with gdisk 0.8.1 and can work around them by explicitely disabling multi-session emulation when producing the ISO. This disabling is default with mkisofs emulation. Today's debian-testing-amd64-netinst.iso shows no such symptoms and thus should be ok at least for gdisk. 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#743879: debian-cd: Fixes for hppa architecture (patch attached)
Hi Thomas, On 04/09/2014 05:53 PM, Thomas Schmitt wrote: >>> How to recognize a PALO that is "newer" ? >> It should be palo 1.92 or higher. >>> ... PALOHDRVERSION ... >> I could update it to 5. > > I think it is appropriate. > Readers of libisofs docs and of PALO could make a clear connection. Ok, committed. I need some testing though until I push a new palo upstream version. >> We shouldn't make xorriso more complicated than necessary. > > Yeah. It already has a sufficient set of dark and dusty corners where > new bugs quickly find a home. > > Notify me when you have more tangible plans for compressed kernels > in ISO. For now i settle with the assessment that it should be well > possible to let libisofs determine the uncompressed sizes. Ok. Helge -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#736672: ITP: hh - BASH history suggest box
Control: package 736672 wnpp On Wed, Apr 9, 2014 at 9:39 PM, Martin Dvorak wrote: > Control: severity 736672 wishlist > Control: source 736672 wnpp > > -- _ *Martin Dvorak* http://www.mindforger.com
Bug#736672: ITP: hh - BASH history suggest box
Control: severity 736672 wishlist Control: source 736672 wnpp
Bug#739172: [apper] apper isn't able to retrieve the changelogs
Unfortunately I haven't this file (or other with similar content) in /etc/apt/apt.conf.d/ :-( -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#736672: ITP: hh - BASH history suggest box
Control: retitle 736672 ITP: hh - BASH history suggest box
Bug#736672: ITP: hstr - BASH history suggest box
Control: retitle 736672 ITP: hstr - BASH history suggest box
Bug#743912: works for me / unreproducible /moreinfo
tags 743912 + moreinfo unreproducible severity 743912 important thanks Hi Charles, thanks for your bug report. I cannot reproduce this here and I also know many people for whom this works, so I downgraded your bugreport and tagged it as I did. This does not mean that I don't think you're having the problems you've been describing! :-) Please provide more info about your system, I could well imagine this is either a hardware problem or your particular usb subsystem has indeed problems (which I believe is less likely, but possible), For a start, the dmesg output as well as lsusb output will be useful. Thanks! cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#744074: [Pkg-openssl-devel] Bug#744074: openssl : upgrade starts disabled services
On Wed, Apr 09, 2014 at 08:50:57PM +0200, Erwan David wrote: > Package: openssl > Version: 1.0.1g-2 > Severity: normal > > When upgrading to 1.0.1g2, bind9 was started. However, since I switched > recently to nsd, this service is disabled (through update-rc.d) > > Upgrade should not start disabled services. The restart is using invoke-rc.d, so should behave properly. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744077: nm.debian.org: encoding problems in e-mail headers
Package: nm.debian.org Severity: normal https://lists.debian.org/20140408204416.2777.5...@nono.debian.org has the following header: From: "C\\xe9dric Boutillier via nm" “Cédric” is not encoded incorrectly. -- 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#739172: [apper] apper isn't able to retrieve the changelogs
Okay, maybe I know the issue...
Could you please drop a file called "21changelog" into "/etc/apt/apt.conf.d/"
containing the following data:
// Server information for apt-changelog
APT {
Changelogs {
Server "http://metadata.ftp-master.debian.org/changelogs";;
};
};
See if you get changelogs again :-)
Cheers,
Matthias
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#736672: ITP: HH/1.0.7-1 - suggest box like BASH history completion
Control: retitle 736672 ITP: HH/1.0.7-1 - suggest box like BASH history completion
Bug#739172: [apper] apper isn't able to retrieve the changelogs
I have the last version available on testing branch ii gir1.2-packagekitglib-1.0 0.8.17-1 i386 GObject introspection data for the PackageKit GLib library ii libpackagekit-glib2-16:i386 0.8.17-1 i386 Library for accessing PackageKit using GLib ii libpackagekit-qt2-6:i386 0.8.8-2 i386 Library for accessing PackageKit using Qt4 ii packagekit 0.8.17-1i386 Provides a package management service ii packagekit-backend-aptcc 0.8.17-1 i386 APT backend for PackageKit ii packagekit-tools 0.8.17-1i386 Provides PackageKit command-line tools ii python3-packagekit 0.8.17-1all PackageKit backend Python bindings Do you know how works this feature? Do you know if exists a "template's url" used to get the changelogs? Maybe the algorithm/template used to generate the url is stored on a configuration file hidden in some "not user-friendly" path. Maybe this file is not automatically purged when I purge the packages (like files stored in /var/tmp/ ) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744027: Please remove StartCom Certification Authority root certificate
On Wed, Apr 09, 2014 at 03:48:56PM +0200, Thijs Kinkhorst wrote: > Whatever you and I think of this pricing structure, people free to chose any > provider of certificates that matches their pricing interest and that people > are knowingly or should be knowlingly buying a product that has a certain > price structure when they get the certificates in the first place. Well, the fee was not prominently advertised. And as revocations were free a few years ago[1], even reading all the terms and conditions back then wouldn't have helped. Or is one expected actively search for new fees in the FAQ when refreshing a certificate? (Please note that I'm not arguing that the CA should be removed - just that the argument that people knowingly chose that pricing structure may be invalid.) Regards, Jan [1] https://cv.exbit.io/emails/startssl_heartbeat.txt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744075: bbswitch-dkms: fails to turn off discrete video card
Package: bbswitch-dkms Version: 0.8-1~bpo70+1 Severity: important Dear Maintainer, I have platform with i915 (Celeron 1037U) and nvidia 705m. I wish to disable discrete video, so i installed bbswitch. After "echo OFF > /proc/acpi/bbswitch" the status is still "ON". Dmesg shows "bbswitch: disabling discrete graphics" with no errors. What additional information do I need to send you to solve this problem? -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bbswitch-dkms depends on: ii dkms 2.2.0.3-1.2 bbswitch-dkms recommends no packages. Versions of packages bbswitch-dkms suggests: pn bumblebee -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744076: RM: libfilesystem-ruby -- RoQA; replaced by ruby-filesystem
Package: ftp.debian.org Severity: normal Dear ftpmasters, apparently libfilesystem-ruby got replaced by ruby-filesystem, but the old (source) package never got removed from unstable. Please remove libruby-filesystem from unstable. Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744036: fixed
Control: fixed -1 3.2.0-2 Fixed by an upload; now builds for all current Ruby versions. -- ,''`. Christian Hofstaedtler : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744073: Acknowledgement (scilab shared libraries are heavily underlinked)
btw, linking with -Wl,--no-allow-shlib-undefined might be a good way to figure out all of these. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742028: xserver-xephyr: -screen not respected
On Wed, 9 Apr 2014, Julien Cristau wrote: On Wed, Apr 9, 2014 at 18:23:41 +0300, Joel Yliluoma wrote: Bug confirmed on Debian Testing. Is there a downgrade/upgrade option available that fixes this problem? No matter what I do, doesn't seem like Xephyr gives me a window anything other than 100x100. Please test the patch I linked? Thanks... But I think this would involve recompiling X server... root@chii:/usr/local/src/deb# apt-get source xserver-xephyr Reading package lists... Done Building dependency tree Reading state information... Done Picking 'xorg-server' as source package instead of 'xserver-xephyr' E: Unable to find a source package for xorg-server root@chii:/usr/local/src/deb# grep '^ *deb-src' /etc/apt/sources.list deb-src http://ftp.fi.debian.org/debian testing main contrib non-free deb-src http://security.debian.org/ testing/updates main contrib non-free Which would be an inconveniently lengthy process even if it did work. In other news, I managed to revert to the Stable version of Xephyr, which fixed the problem. It also now does XPutImage calls right like I expect it to. Here's how I did the downgrade: apt-get remove xserver-xephyr sed -i 's/testing/stable/g' /etc/apt/sources.list apt-get update aptitude install xserver-xephyr # Choose the second option offered, which involves downgrading xorg-related packages. sed -i 's/stable/testing/g' /etc/apt/sources.list -- Joel Yliluoma http://iki.fi/bisqwit/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#730913: libmongodb-perl: FTBFS: Failed tests -> no big deal
Hello
I've looked at the test result that lead to libmongodb-perl FTBS:
> # Failed test 'js err'
> # at t/db.t line 52.
> # 'exception: SyntaxError: Unexpected string'
> # doesn't match '(?^:(?:compile|execution) failed)'
> # Looks like you failed 1 test of 10.
This error is triggered by:
my $err = $db->eval('function(x) { xreturn "hello, "+x; }', ["world"]);
like($err, qr/(?:compile|execution) failed/, 'js err');
The javascript code fed to eval is indeed bogus. The error message now returned
by mongodb
contains information more precise than before (which is a good thing).
This new error string does match the behavior of mongo client [1]:
$ mongo
> db.runCommand( { eval: function(x) { return "hello, "+x; }, args: [ 'world' ]
> } );
{ "retval" : "hello, world", "ok" : 1 }
> db.runCommand( { eval: function(x) { xreturn "hello, "+x; }, args: [ 'world'
> ] } );
Wed Apr 9 20:54:00.905 SyntaxError: Unexpected string
So I think we can safely patch the test to avoid removal of libmongodb-perl
from testing.
I'll do this in the next few days unless gregoa beats me to it ;-)
All the best
[1] explanation on the syntax:
http://docs.mongodb.org/manual/reference/command/eval/#dbcmd.eval
--
https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683120: RFS: yadifa/1.0.3-1 [ITP]
On 2014-04-09 20:50, Christian Kastner wrote:
>>> debian/control
>>> ==
>
> I like your approach with a common description provided through a
> substitution variable! Very efficient.
Oh, I missed something here: you are using the substitution variable
${Description}, but you are not setting it anywhere, which results in
half-empty descriptions (see the output in
debian/libdns*/DEBIAN/control). See deb-substvars(5).
Christian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744074: openssl : upgrade starts disabled services
Package: openssl Version: 1.0.1g-2 Severity: normal When upgrading to 1.0.1g2, bind9 was started. However, since I switched recently to nsd, this service is disabled (through update-rc.d) Upgrade should not start disabled services. -- System Information: Debian Release: jessie/sid APT prefers testing-proposed-updates APT policy: (900, 'testing-proposed-updates'), (900, 'testing'), (800, 'stable'), (500, 'proposed-updates'), (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openssl depends on: ii libc62.18-4 ii libssl1.0.0 1.0.1g-2 openssl recommends no packages. Versions of packages openssl suggests: ii ca-certificates 20140325 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683120: RFS: yadifa/1.0.3-1 [ITP]
On 2014-04-09 09:26, Markus Schade wrote: > thanks for the review, Christian! Glad I can help :-) Here is some further feedback: >> debian/control >> == >> If you're using a VCS for your packaging, Vcs-* URLs would be nice (to >> simplify contributing to your packaging). You can also use >> Debian's infrastructure, see [1]. Almost correct. The Vcs-Git URL should use the git:// protocol specifier, and you could add a Vcs-Browser URL pointing to the github package, like so: -Vcs-Git: https://github.com/asciiprod/yadifa.git +Vcs-Git: git://github.com/asciiprod/yadifa.git +Vcs-Browser: https://github.com/asciiprod/yadifa > I had intended to set up a repo after the first upload. But of course it > is easier to contribute even before that. And since I need a DM approval > for an Alioth repo, I settled for github for now. I don't think you need DM approval, you only need a DD to request access for you (which would probably be the DD sponsoring your package). But github is more than fine for now, you can always switch later (or not at all). >> You're providing static libraries in the -dev package, but not a shared >> library package. This is not necessarily wrong, just unusual. Note >> that the configure script has an option to build a shared library. > > Good point. The default was to do static linking. Now with shared libs, > I have not just two packages but five (three just for the libs). But as > the recent openssl bug shows, it is easier to just patch a lib than to > rebuild all depending packages. Looks good! One major issue though: the libraries are definitely not Priority: standard :-) (= part of the default Debian installation). You can simply remove this line, the inherited "optional" is fine. nit-pick #1: the synopsis refers to Yadifa twice, in different case, and the other parts should be lowercased. According to the Developer's Reference[0], something like this would probably be more appropriate: -Description: Yadifa DNS Core Shared Library used by YADIFA +Description: DNS core shared library used by YADIFA I like your approach with a common description provided through a substitution variable! Very efficient. nit-pick #2: The package descriptions of the libraries could be a bit more explanatory. (lintian also complains about this). Currently, they basically just repeat the synopsis. Try to describe what another user of the library can do with this package. For example, for libdnszone0, This library can be use to read and write YADIFA-compliant zone files and [...] (I'm just guessing that, I didn't look). This is much more informative to developers who might be interested in writing eg GUI client for modifying zone files. Same goes for the other two libs. Finally, my personal taste for the package description would be something like - This package contains archive-style libraries and header files for - libdnscore0, libdnsdb0 and libdnszone0 + This package contains the header files and the static libraries which are + needed for developing YAFIDA applications. but that's highly subjective. >> debian/copyright >> > > I had originally just included upstreams COPYING, but I think it's safe > to extend the years to include all changes from upstream since then. > > As for my own packaging, I don't mind putting it under a BSD-style license. Just to clarify: you don't have license all of your packaging under a BSD-style license., it's sufficient to do that just for the files in debian/patches/*. The machine-readable copyright format specification[1] has more details. > So again, after making these various adjustments and corrections, I have > re-uploaded the package again. By the way, if you can't find a sponsor here (it sometimes takes a while), you can also try pinging either people or teams who might be interested in your package (eg other DNS maintainers). Finally, here are some ideas for future versions of your package: * build a -dbg package (debhelper can automate lots of this) * provide *.symbols files * Multi-archification I say future versions because the value added isn't that big, and when you've just begun packaging then all this stuff in total can easily become overwhelming. Good luck with your package :-) Christian > To access further information about this package, please visit the > following URL: > > http://mentors.debian.net/package/yadifa > > Or via dget at > > http://mentors.debian.net/debian/pool/main/y/yadifa/yadifa_1.0.3-1.dsc [0] file:///usr/share/doc/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis [1]https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744073: scilab shared libraries are heavily underlinked
Package: scilab Version: 5.5.0~beta-1+git~20140406-1522-2 Severity: important please forward this upstream. maybe as separate bug reports for each library with unresolvable references. dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libsciscinotes-disable.so.5.5.0 contains an unresolvable reference to symbol getScilabMode: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscipreferences-cli.so.5.5.0 contains an unresolvable reference to symbol Scierror: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libsciconsole-minimal.so.5.5.0 contains an unresolvable reference to symbol completionOnCommandWords: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libsciexternal_objects.so.5.5.0 contains an unresolvable reference to symbol getNbInputArgument: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscihistory_manager.so.5.5.0 contains an unresolvable reference to symbol _ZNSsC1EPKcRKSaIcE: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libsciparallel.so.5.5.0 contains an unresolvable reference to symbol SearchInDynLinks: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libsciarnoldi.so.5.5.0 contains an unresolvable reference to symbol getNbOutputArgument: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscistatistics.so.5.5.0 contains an unresolvable reference to symbol getNbInputArgument: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscigraphics-disable.so.5.5.0 contains an unresolvable reference to symbol vartype_: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscirandlib.so.5.5.0 contains an unresolvable reference to symbol SciError: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscispreadsheet.so.5.5.0 contains an unresolvable reference to symbol freeComplexArray: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscigraphic_objects-disable.so.5.5.0 contains an unresolvable reference to symbol Scierror: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libsciui_data-disable.so.5.5.0 contains an unresolvable reference to symbol getScilabMode: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libsciinterpolation.so.5.5.0 contains an unresolvable reference to symbol returnananfortran_: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscicompletion.so.5.5.0 contains an unresolvable reference to symbol _ZNSt8ios_base4InitD1Ev: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscioptimization.so.5.5.0 contains an unresolvable reference to symbol allowptr_: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libsciaction_binding-disable.so.5.5.0 contains an unresolvable reference to symbol Scierror: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscihdf5.so.5.5.0 contains an unresolvable reference to symbol createNamedMatrixOfUnsignedInteger16: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscihistory_browser-disable.so.5.5.0 contains an unresolvable reference to symbol Scierror: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscixcos-disable.so.5.5.0 contains an unresolvable reference to symbol getScilabMode: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscifunctions.so.5.5.0 contains an unresolvable reference to symbol Scierror: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscilocalization.so.5.5.0 contains an unresolvable reference to symbol sciprint: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscilab-cli.so.0.0.0 contains an unresolvable reference to symbol _gfortran_transfer_integer: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscispecial_functions.so.5.5.0 contains an unresolvable reference to symbol freeAllocatedSingleString: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libsciumfpack.so.5.5.0 contains an unresolvable reference to symbol com_: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscigui-disable.so.5.5.0 contains an unresolvable reference to symbol sciprint: it's probably a plugin dpkg-shlibdeps: warning: debian/scilab-minimal-bin/usr/lib/scilab/libscicall_scilab.so.5.5.0 contains an unresolvable reference to symbol sciHa
Bug#742174: owncloud: dpkg postinst exits with error code (1)
Hi Link, Thanks for your interest in the owncloud Debian package. On Thu, Mar 20, 2014 at 12:49:05AM -0700, Link Porterfield wrote: > I upgraded owncloud with > > apt-get updgrade owncloud > ` > E: Sub-process /usr/bin/dpkg returned an error code (1) > > /etc/apache2/conf-available/owncloud.conf does not exist on my system. Thanks for the report, the admin should indeed be allowed to remove unwanted confiles. As a workaround, you could simply overwrite this file by an empty one (or containing at least a commented line). Regards David signature.asc Description: Digital signature
Bug#732343: prelink -av misses prelinking just-upgraded binaries
Package: prelink Version: 0.0.20130503-1 Followup-For: Bug #732343 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** This is an ongoing problem - the ELF binaries from just installed geoip-bin were not prelinked by: prelink -av but were prelinked by prelink -v /usr/bin/geoip* *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14.0+ (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages prelink depends on: ii execstack 0.0.20130503-1 prelink recommends no packages. prelink suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744072: RM: libfilesystem-ruby/0.5-3.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Dear Release-Team, it appears src:libfilesystem-ruby is halfway stuck in testing: - it's binary libfilesystem-ruby1.8 is NOT in testing - source and binary libfilesystem-ruby1.9.1 are in testing - src:libfilesystem-ruby Build-Depends on ruby1.8 which is NOT in testing. - there's no indication of a pending autoremove triggered by #735654. I think it's safe to just entirely remove this package from testing, so I'd suggest doing exactly that. Thanks, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743128: Had to revert, too
I had to revert network-manager to 0.9.8.0-5, too. Although systemd was installed, "nmcli c" showed no connections; "qdbus --literal --system org.freedesktop.NetworkManager /org/freedesktop/NetworkManager/AccessPoint/N" did work, though. So it did detect my access point - but the KDE applet showed no saved connections (qdbus did), and on clicking on the "new" (ha!) wifi network and entering the password just nothing happened. systemd is installed - but not active. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
