Bug#756159: qemu-kvm: Please build binary with SATA and hda sound support
On Sat, Jul 26, 2014 at 11:31:29PM +0100, Pedro Ribeiro wrote:
Package: qemu-kvm
Version: 2.0.0+dfsg-6+b1
Severity: normal
Hi,
When I set up a virtual machine with a SATA drive, the VM fails to start with
the following message:
Error starting domain: unsupported configuration: SATA is not supported with
this QEMU binary
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/asyncjob.py, line 96, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File /usr/share/virt-manager/virtManager/asyncjob.py, line 117, in tmpcb
callback(*args, **kwargs)
File /usr/share/virt-manager/virtManager/domain.py, line 1160, in startup
self._backend.create()
File /usr/lib/python2.7/dist-packages/libvirt.py, line 917, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: unsupported configuration: SATA is not supported with this QEMU
binary
What machine type are you using? Try q35 please.
-- Guido
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756576: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Control: forcemerge 750395 -1 Yeah, heard you the first time! :) Should be solved now anyway... Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741785: seems upstream has fixed the readline issue with the libseed ftbfs issue.
On Sun, 13 Apr 2014 10:29:15 +0530 =?UTF-8?B?c2hpcmlzaCDgpLbgpL/gpLDgpYDgpLc=?= shirisha...@gmail.com wrote: Hi there, Just was wondering about libseed transition, saw the bug and saw the upstream comment. https://bugzilla.gnome.org/show_bug.cgi?id=725602#c2 Looking at the web interface for seed it seems to be this commit :- https://git.gnome.org/browse/seed/commit/?id=cf772e792fd64f70ee2c714e0b5eaf527ce35467 I tested this patch on mips64el. It works well. Any progress of it? Looking forward to an updated seed in testing soonish :) -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756585: nvclock: [nvclock] not work with modern cards
Package: nvclock Version: 0.8b4-1+b1 Severity: normal Hi, Sorry my bad English, I will be brief)) First: root@aspera:~# nvclock -s Card: Unknown Nvidia card Card number:1 Memory clock: -2147483.750 MHz GPU clock: -2147483.750 MHz root@aspera:~# nvclock -i It seems your card isn't officialy supported in NVClock yet. The reason can be that your card is too new. If you want to try it anyhow [DANGEROUS], use the option -f to force the setting(s). NVClock will then assume your card is a 'normal', it might be dangerous on other cards. Also please email the author the pci_id of the card for further investigation. [Get that value using the -i option]. Second: root@aspera:~# lspci -vvxxx -s 02:00.0 02:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 83b8 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 45 Region 0: Memory at fd00 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at d800 (64-bit, prefetchable) [size=128M] Region 3: Memory at d600 (64-bit, prefetchable) [size=32M] Region 5: I/O ports at b800 [size=128] [virtual] Expansion ROM at fe98 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0300c Data: 4142 Capabilities: [78] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 64us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s 256ns, L1 4us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM L0s L1 Enabled; RCB 128 bytes Disabled- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [b4] Vendor Specific Information: Len=14 ? Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [128 v1] Power Budgeting ? Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 ? Kernel driver in use: nvidia 00: de 10 e1 0d 07 00 10 00 a1 00 00 03 00 00 80 00 10: 00 00 00 fd 0c 00 00 d8 00 00 00 00 0c 00 00 d6 20: 00 00 00 00 01 b8 00 00 00 00 00 00 43 10 b8 83 30: 00 00 00 00 60 00 00 00 00 00 00 00 0a 01 00 00 40: 43 10 b8 83 00 00 00 00 00 00 00 00 00 00 00 00 50: 01 00 00 00 01 00 00 00 ce d6 23 00 00 00 00 00 60: 01 68 03 00 08 00 00 00 05 78 81 00 0c 30 e0 fe 70: 00 00 00 00 42 41 00 00 10 b4 02 00 e0 8d 2c 01 80: 00 29 00 00 01 2d 05 00 4b 01 01 11 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 10 00 00 00 a0: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 b0: 00 00 00 00 09 00 14 01 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Bug#756586: searchandrescue: FTBFS on mips64el
Source: searchandrescue Version: 1.5.0-1 Severity: normal Tags: patch Please add mips64 and mips64el into sar/platforms.ini, like the ppc64el and arm64, aka, add PlatformSearchPathLib = /usr/lib/mips64el-linux-gnuabi64/ PlatformSearchPathLib = /usr/lib/mips64-linux-gnuabi64/ -- 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#756554: [stellarium] when browsing satellites manually, all are highlited
On 31/07/14 11:21, Alexander Wolf wrote: I confirmed it and I filled bug report in upstream: https://bugs.launchpad.net/stellarium/+bug/1350669 -- With best regards, Alexander Funny, I don't think I can confirm it, but I trust you. All I see are some graphical glitches when I use keyboard arrows to move around in the list of satellites. But they dissapear if I do something else. Tomasz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744115: codeblocks is marked for autoremoval from testing
On Sun, Jul 27, 2014 at 9:39 PM, Debian testing autoremoval watch nore...@release.debian.org wrote: codeblocks 13.12-3 is marked for autoremoval from testing on 2014-07-31 It is affected by these RC bugs: 744115: codeblocks: Please update to use wxwidgets3.0 Ping. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756587: python3-pyfits: fails to configure, syntax error
Package: python3-pyfits Version: 1:3.3-1 Severity: important Dear Maintainer, during apt-get upgrade this morning, I got: Setting up python3-pyfits (1:3.3-1) ... File /usr/lib/python3/dist-packages/pyfits/scripts/fitscheck.py, line 135 except UserWarning, w: ^ SyntaxError: invalid syntax dpkg: error processing package python3-pyfits (--configure): subprocess installed post-installation script returned error exit status 1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 armhf powerpc Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python3-pyfits depends on: ii libc6 2.19-7 ii libcfitsio3 3.340-3 ii python3 3.4.1-1 ii python3-numpy [python3-numpy-abi9] 1:1.8.1-1+b1 python3-pyfits recommends no packages. Versions of packages python3-pyfits suggests: ii pyfits-utils 1:3.3-1 -- 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#756589: sbuild: set DH_VERBOSE to get verbose build logs from buildds
Package: sbuild Version: 0.64.1-1 Severity: wishlist In #551463 and #680686, people requested that debhelper should automatically pass --disable-silent-rules to Automake build systems for the jessie verbose build logs release goal. Joey was reluctant to enable this by default (to avoid package maintainers getting sufficiently verbose logs when developing that warnings are not readily visible), but did merge a patch to do so when DH_VERBOSE is set (#751207), with the suggestion that the buildds should enable it. sbuild is a more or less non-interactive build even when not on a buildd, and produces copious output regardless of debhelper settings, so I think it would be reasonable for it to set DH_VERBOSE by default. Regards, S -- System Information: Debian Release: jessie/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-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 sbuild depends on: ii adduser 3.113+nmu3 ii apt-utils 1.0.6 ii libsbuild-perl 0.64.1-1 ii perl5.18.2-7 ii perl-modules5.18.2-7 Versions of packages sbuild recommends: ii debootstrap 1.0.60 ii fakeroot 1.20.1-1 Versions of packages sbuild suggests: pn deborphan none ii wget 1.15-1+b1 -- 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#755408: printer-driver-escpr: Cups Epson-WF-7610: not possible to select 'Rear Paper Feed Slot'
Dear Ulrich, thanks for your bugreport. Le dimanche, 20 juillet 2014, 14.44:08 Ulrich Homann a écrit : I'm using a Epson WF-7610 Printer. Nearly everthing works as expected but it is not possible to select the 'Rear Paper Feed Slot'. If I do so the setting is ignored and the Printer still uses the paper cassette. I'm not sure if this bug is really related to the ppd (I've tried the upstream version of the PPDs with the same result -- not really a surprive as they are identical). Seiko Epson released a new 1.4.1 update to its driver; can you test the 1.4.1-1 version from unstable and see whether it fixes your problem? (Looking at the diff, I'm quite sure it will not though :/ ) Given that I don't own this printer myself, it's quite hard for me to assist here; I'm hereby CC'ing the email address listed as packager of the upstream rpm; let's see if they can assist. Cheers, OdyXDidier Raboud, aka signature.asc Description: This is a digitally signed message part.
Bug#751694: Oops.
Control: block 751694 by 736647 Seems that I uploaded morfologik-stemming too early. :-( carrotsearch-hppc was uploaded by me and is still sitting in the NEW queue. Once it has hit unstable, this bug can be closed. Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705212: Processed: RFP: chinese-checkers -- Multiplayer implementation of the chinese checkers game
retitle 705212 ITP: chinese-checkers -- Multiplayer implementation of the chinese checkers game. thanks Well anyways it's not an RFP since the package is done and ready. Please stop retitling. https://github.com/ltworf/tin171/tree/master/debian Actually it's not even an ITP since It's already packaged, strictly speaking... -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756590: upower -d says my laptop is docked but it is not
Package: upower Version: 0.99.0-3 Severity: minor upower -d says my laptop is docked but it is not and I don't own a dock. AFAICT the Linux kernel doesn't think my laptop is docked though. pabs@chianamo ~ $ upower -d | grep dock is-docked: yes pabs@chianamo ~ $ head /sys/devices/platform/dock*/docked == /sys/devices/platform/dock.0/docked == 0 == /sys/devices/platform/dock.1/docked == 0 == /sys/devices/platform/dock.2/docked == 0 pabs@chianamo ~ $ dmesg | grep -i dock [0.382030] ACPI: ACPI Dock Station Driver: 3 docks/bays found -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (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/dash Versions of packages upower depends on: ii dbus 1.8.6-1 ii libc6 2.19-7 ii libdbus-1-31.8.6-1 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.40.0-3 ii libgudev-1.0-0 208-6 ii libimobiledevice4 1.1.6+dfsg-3 ii libplist2 1.11-3 ii libpolkit-gobject-1-0 0.105-6.1 ii libupower-glib20.99.0-3 ii libusb-1.0-0 2:1.0.19-1 ii pm-utils 1.4.1-15 ii systemd208-6 ii udev 208-6 Versions of packages upower recommends: ii policykit-1 0.105-6.1 upower suggests no packages. -- no debconf information -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#744115: codeblocks is marked for autoremoval from testing
On 31/07/14 09:09, Vincent Cheng wrote: On Sun, Jul 27, 2014 at 9:39 PM, Debian testing autoremoval watch nore...@release.debian.org wrote: codeblocks 13.12-3 is marked for autoremoval from testing on 2014-07-31 It is affected by these RC bugs: 744115: codeblocks: Please update to use wxwidgets3.0 Ping. Have you thought about this? Olly Betts wrote: The issue there is most likely because wx 3.0 enables WXDEBUG mode by default which includes checks for incorrect API usage, whereas with wx 2.8 you had to specify it explicitly when you built the library. In other words, codeblocks is misusing the wx API, but with 2.8 this gets quietly ignored by default, whereas 3.0 reports it by default. I bet if you rebuilt codeblocks using the WXDEBUG build of 2.8 (available in Debian in package libwxgtk2.8-dbg - despite the name, this isn't debug symbols, but a separate build of the library) you'd see this assertion too. The simplest way to address this is to build codeblocks with -DNDEBUG (pass it in CPPFLAGS usually), which makes wx 3.0 behave as a default build of 2.8 would. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756591: package magics++_2.18.15-6 FTBFS on mips
Package: magics++
Version: 2.18.15-6
Severity: important
Tags: sid patch
Justification: FTBFS
User: debian-mips-dev-disc...@lists.alioth.debian.org
Usertags: mips-patch
Hello,
Package magics++_2.18.15-6 FTBFS on mips:
https://buildd.debian.org/status/fetch.php?pkg=magics%2B%2Barch=mipsver=2.18.15-6stamp=1406359409
For this package there is a special case in debian/rules and debian/control
just for mips.
Patch removes this special case.
debian/rules:
# Don't use emoslib on mips
WITH_EMOSLIB:= --with-emos-libraries=/usr/lib --enable-bufr
ifeq ($(ARCH), mips)
WITH_EMOSLIB:=
endif
debian/control:
Build-Depends: ... libemos-dev [!mips]
I have attached a patch.
With this patch package builds without an issue.
Regards,
Jurica
diff -upNr magics++-2.18.15-orig/debian/control magics++-2.18.15/debian/control
--- magics++-2.18.15-orig/debian/control 2014-07-22 18:02:34.0 +0200
+++ magics++-2.18.15/debian/control 2014-07-30 09:53:48.0 +0200
@@ -2,7 +2,7 @@ Source: magics++
Section: science
Priority: optional
Maintainer: Alastair McKinstry mckins...@debian.org
-Build-Depends: debhelper (= 9) , dh-buildinfo, libnetcdf-dev, libgl1-mesa-dev, libgd2-dev, libemos-dev [!mips], libgrib-api-dev, libterralib-dev, libjasper-dev, libcairo2-dev, libpango1.0-dev, autoconf, automake, libtool, gfortran, ttf-dejavu-core, libxml-parser-perl, python-all-dev (= 2.6.6-3) , swig, chrpath, python-numpy, libopenjpeg-dev, ghostscript, zlib1g-dev, dh-autoreconf (= 4~), libboost-dev, python-instant, python3-all-dev, libproj-dev, libqt4-dev
+Build-Depends: debhelper (= 9) , dh-buildinfo, libnetcdf-dev, libgl1-mesa-dev, libgd2-dev, libemos-dev, libgrib-api-dev, libterralib-dev, libjasper-dev, libcairo2-dev, libpango1.0-dev, autoconf, automake, libtool, gfortran, ttf-dejavu-core, libxml-parser-perl, python-all-dev (= 2.6.6-3) , swig, chrpath, python-numpy, libopenjpeg-dev, ghostscript, zlib1g-dev, dh-autoreconf (= 4~), libboost-dev, python-instant, python3-all-dev, libproj-dev, libqt4-dev
Standards-Version: 3.9.5
Homepage: https://software.ecmwf.int/wiki/display/MAGP/Magics
X-Python-Version: = 2.6
diff -upNr magics++-2.18.15-orig/debian/rules magics++-2.18.15/debian/rules
--- magics++-2.18.15-orig/debian/rules 2014-07-22 18:02:34.0 +0200
+++ magics++-2.18.15/debian/rules 2014-07-30 09:53:00.0 +0200
@@ -16,11 +16,7 @@ CFLAGS += -fPIC
DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
-# Don't use emoslib on mips
WITH_EMOSLIB:= --with-emos-libraries=/usr/lib --enable-bufr
-ifeq ($(ARCH), mips)
- WITH_EMOSLIB:=
-endif
override_dh_auto_clean:
find . -type l -exec rm {} \;
Bug#756592: ruby-gsl failed to run test on mips64el
Package: ruby-gsl Version: 1.15.3+dfsg-2 I tried to build ruby-gsl on mips64el while failed, due to a failure on test. *** running tests/multifit/test_filip.rb *** FAIL: filip gsl_fit_multilinear c8 (-0.0670191086058517793 observed vs -0.0670191154593408056 expected) FAIL: filip gsl_fit_multilinear c9 (-0.00246781052277280982 observed vs -0.00246781078275479021 expected) FAIL: filip gsl_fit_multilinear c10 (-4.02962481217298765e-05 observed vs -4.02962525080403984e-05 expected) FAIL: filip gsl_fit_multilinear c8 (-0.0670191086058517793 observed vs -0.0670191154593408056 expected) FAIL: filip gsl_fit_multilinear c9 (-0.00246781052277280982 observed vs -0.00246781078275479021 expected) FAIL: filip gsl_fit_multilinear c10 (-4.02962481217298765e-05 observed vs -4.02962525080403984e-05 expected) ERROR: Test ruby2.1 failed. Exiting. You can get the buildlog from http://mips64el.debian.net/debian/buildlog/r/ruby-gsl_1.15.3%2bdfsg-2/ruby-gsl_1.15.3%2bdfsg-2_mips64el-20140711-0005.build any idea? -- 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#679228: Bug #755513 : nvidia-opencl-dev: binary conflict with ocl-icd-libopencl1
On 30/07/2014 20:13, Graham Inggs wrote: Hi Vincent On 30 July 2014 18:23, Vincent Danjean vdanjean...@free.fr wrote: As this bug remains me this situation, I'm proposing that we move the libOpenCL.so symlink into the dev package. [...] If you agree, we will have to go through all OpenCL packages to put correct conflicts/replaces where required. What changes would be required to all OpenCL packages if you moved the libOpenCL.so symlink into the dev package? Surely if ocl-icd-libopencl1 ships libOpenCL.so then it should conflict with all other opencl -dev packages (i.e. those that also ship libOpenCL.so), and if it stops shipping libOpenCL.so then it is just a matter of removing those conflicts? all *-libopencl1 conflict/replace themselves as they provide the same binary (libOpenCL.so.1) And we need to put the correct conflict/replace for the libOpenCL.so. It is not hard but this file is (was?) not handled the same way by all OpenCL packagers. It is just a matter to list all packages (in wheezy and testing) that provide it. This will avoid to wait for users to detect missing conflict/replace and upload fixed packages. Regards Vincent Regards Graham -- Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756258: exim4 configured with dovecot auth deadlocks
On 30/07/2014 19:32, Andreas Metzler wrote: Hello, thanks, I have now forwarded this report upstream (link at the top this mail), it would nice if you could send further info there (and subscribe to the bug). Thank you for doing so. I continued to investigate on my side and found the issue. It was a configuration error that was not evidenced by an error message. I described it in this e-mail:http://dovecot.org/pipermail/dovecot/2014-July/097279.html http://dovecot.org/pipermail/dovecot/2014-July/097279.html Basically, I was using the auth-userdb instead of the auth-socket. Instead of showing a protocol error in the logs and because the two sockets have a compatible protocol, exim was blocking on authentication. Mildred
Bug#756479: enable -enable-command-args again, please
Dear Maintainer, i know, that you compiled without -enable-command-args and you wrote in the NEWS.Debian file, that you disabled it because there are security problems and that this feature is often used wrong. Some people need this feature to manage monitoring parameters central. Your nrpe.cfg disables this feature by default (don't_blame_nrpe=0) and the features comment shows everyone, that enable it could be a security Problem. For my opinion, disable this feature by default should be enough. If someone need this feature, he must compile his own nrpe server version. Maybe he need to do it on hundreds of Machines and he has to do it again, if the Debian Packet is updated. I don't think that Compile nrpe without this feature is a real security advantage because if someone need it, he will compile with this support except of only enable this feature. I Agree with you, that this option could be a security risk, but it is possible to reduce the risk by setting allowed_hosts to restric who is able to communicate with nrpe. It would be nice if you would compile with -enable-command-args again. It would give more flexibility how to use nrpe and all people who use command args wouldn't need to manage their own version of this packet. Best regards Jörg, Rauscher
Bug#756593: busybox's switch_root makes read-only NFS root read/write
Package: busybox Version: 1:1.22.0-6 Severity: important Dear Maintainer, we have a PXE environments in our lab, where we boot both physical boxes and XEN machines via NFS from one centralized Debian SID image. While the kernel/initramfs mounts the image correctly read only (I set a breakpoint just before switch_root get invoked) (see [1]), makes switch_root the NFS root read/write (see [2]). Alex [1] 192.168.0.1:/usr/local/muclab/image/debian-sid on /root type nfs (ro,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,nolock, proto=tcp,port=2049,timeo=7,retrans=10,sec=sys,local_lock=all,addr=192.168.0.1) [2] 192.168.0.1:/usr/local/muclab/image/debian-sid on / type nfs (rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,nolock, proto=tcp,port=2049,timeo=7,retrans=3,sec=sys,local_lock=all,addr=192.168.0.1) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14.0-netem.fas3270-aufs+ (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 busybox depends on: ii libc6 2.19-7 busybox recommends no packages. busybox suggests no packages. -- no debconf information signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#756594: ruby-ffi failed to run test on mips64el
Package: ruby-ffi Version: 1.9.3debian-1 Failures: 1) Custom type definitions detects the correct type for size_t Failure/Error: lambda do expected no Exception, got #TypeError: unable to resolve type 'size_t' with backtrace: # ./lib/ffi/types.rb:70:in `find_type' # ./lib/ffi/library.rb:496:in `find_type' # ./lib/ffi/library.rb:227:in `block in attach_function' # ./lib/ffi/library.rb:227:in `map' # ./lib/ffi/library.rb:227:in `attach_function' # ./spec/ffi/typedef_spec.rb:74:in `block (4 levels) in top (required)' # ./spec/ffi/typedef_spec.rb:70:in `initialize' # ./spec/ffi/typedef_spec.rb:70:in `new' # ./spec/ffi/typedef_spec.rb:70:in `block (3 levels) in top (required)' # ./spec/ffi/typedef_spec.rb:69:in `block (2 levels) in top (required)' # ./spec/ffi/typedef_spec.rb:69:in `block (2 levels) in top (required)' Finished in 12.42 seconds 4793 examples, 1 failure Failed examples: rspec ./spec/ffi/typedef_spec.rb:68 # Custom type definitions detects the correct type for size_t ERROR: Test ruby2.1 failed. Exiting. You can get the buildlog from: http://mips64el.debian.net/debian/buildlog/r/ruby-ffi_1.9.3debian-1/ruby-ffi_1.9.3debian-1_mips64el-20140711-.build -- 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#755274: [Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot
Dear Nobuhiro, Absolutely agree. Thank you! Best regards, Andriy On Mon, 28 Jul 2014 15:43:20 +0900 Nobuhiro Iwamatsu iwama...@nigauri.org wrote: Hi, 2014-07-26 22:10 GMT+09:00 Andriy Martynets martyn...@volia.ua: On Sat, 26 Jul 2014 04:52:49 +0900 Nobuhiro Iwamatsu iwama...@nigauri.org wrote: Dear Nobuhiro, Thanks! Using of the udev rule is reasonable as this activates any BT adapter as soon as it is plugged in. Maintaining this via an init script works fine in majority of cases but not in all. As the script runs once it will not cover cases when the adapter is hot plugged later. Reverting this back will solve the bug as will make the package working fine. To improve the package by adding the udev rule you have to make the hciconfig tool available from the rootfs. You can see if you get a look at the other mail of this bug, I have received other proposals from Michael. It is a proposal to move to / bin the hciconfig. I think that trying to adopt this proposal. Because hciconifg depends only on libraries of / lib, it can be moved. In addition, we can unify the initialization of hciX in systemd, sysvinit and other init system can be controlled by udev. Of course, this resolve problem of this BTS. This is reasonable, I think. Thank you again and best regards, Andriy Best regards, Nobuhiro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754149: Shortening the second phase
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754149#55 The call for translation updates and new translations will run until about Tuesday, August 19, 2014 I will be on VAC from August 15, 2014 for DebConf - please advance the timeframe so that I have time to make an upload before the 15th with the final patch for the templates and the translations. -- Neil Williams = http://www.linux.codehelp.co.uk/ signature.asc Description: PGP signature
Bug#756582: new syntax error when invoking udevadm test breaks installing/ upgrading
On Thu, Jul 31, 2014 at 6:42 AM, Stefan Lippers-Hollmann s@gmx.de wrote: When upgrading (or installing) fuse 2.9.3-13 to 2.9.3-14, the new postinst fails with: Setting up fuse (2.9.3-14) ... dpkg: error processing package fuse (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: fuse E: Sub-process /usr/bin/dpkg returned an error code (1) [...] Reverting this to udevadm test -a -p fixes the problem again. Right, I shouldn't do after last minute small changes. Will fix it soon. Sorry for the inconvenience, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756595: fuse fails to upgrade, because uses a nonexistent udevadm test option
Package: fuse
Version: 2.9.3-14
Setting up clang-3.5 (1:3.5~+rc1-2) ...
Setting up libfuse2:i386 (2.9.3-14) ...
Setting up fuse (2.9.3-14) ...
dpkg: error processing package fuse (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up libharfbuzz0b:i386 (0.9.33-1) ...
Setting up libharfbuzz-icu0:i386 (0.9.33-1) ...
[..]
Setting up tcpdump (4.6.1-1) ...
Setting up vorbis-tools (1.4.0-1.1) ...
Processing triggers for libc-bin (2.19-7) ...
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
richard@deodand:~$ really dpkg --configure -a
Setting up fuse (2.9.3-14) ...
dpkg: error processing package fuse (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
fuse
richard@deodand:~$
I added a 'set -x' to the postinst script and removed a redirection to
/dev/null to see what was going on:
richard@deodand:~$ really dpkg --configure -a
Setting up fuse (2.9.3-14) ...
+ set -e
+ case ${1} in
+ dpkg-statoverride --list /bin/fusermount
+ chmod 4755 /bin/fusermount
+ modprobe fuse
+ lsmod
+ grep -qs fuse
+ udevadm control --reload-rules
+ '[' -e /dev/fuse ']'
++ udevadm info -q path -n /dev/fuse
+ udevadm test -e -p /devices/virtual/misc/fuse
calling: test
version 208
test: invalid option -- 'e'
dpkg: error processing package fuse (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
fuse
richard@deodand:~$ COLUMNS=80 dpkg -l *fuse* *udev* libc6*|grep ^i
iF fuse 2.9.3-14 i386 Filesystem in Userspace
ii libc6:i386 2.19-7 i386 GNU C Library: Shared libraries
ii libc6-dbg:i386 2.19-7 i386 GNU C Library: detached
debugging
ii libc6-dev:i386 2.19-7 i386 GNU C Library: Development
Librar
ii libc6-i686:i38 2.19-7 i386 GNU C Library: Shared
libraries [
ii libfuse2:i386 2.9.3-14 i386 Filesystem in Userspace
(library)
ii libgudev-1.0-0 208-6i386 GObject-based wrapper
library for
ii libudev1:i386 208-6i386 libudev shared library
ii python-defused 0.4.1-2 all XML bomb protection for
Python st
ii system-config- 1.4.3-4 i386 Utilities to detect and
configure
ii udev 208-6i386 /dev/ and hotplug
management daem
richard@deodand:~$ uname -a
Linux deodand 3.14-2-686-pae #1 SMP Debian 3.14.13-2 (2014-07-24) i686
GNU/Linux
richard@deodand:~$
ttfn/rjk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756597: rt-tests: build-depends on libnuma-dev for mips{64,n32}{el,}
Package: rt-tests Version: 0.88-1 in debian/rules all mips* architectures are enabled by numa support, so please add mips64 mips64el mipsn32 mipsn32el to libnuma-dev list. Maybe filter instead of findstring should be used ? -- 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#756596: dpkg: typo
Package: libbsd0 Priority: minor Tags: patch Version: 0.7.0-1 There's a typo in package description: packag - package. Regards, ~~helix84 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707008: dkms: should depend on python-apport
Package: dkms
Version: 2.2.0.3-1.2
Followup-For: Bug #707008
Tags: patch
Am Mo, 06. Mai 2013 um 22:03:53 +0200 schrieb Matthias Liertzer:
while updating the system to the newest version of linux-headers in unstable
(linux-headers-3.8-1-amd64), dkms failed to run the package hooks for dkms.
The
script in /usr/share/apport/package-hooks/dkms_packages.py failed because it
imports the python module apport, which is, however, not installed on the
machine. Installing python-apport and applying the following patch
I don't think it is wise to depend on a package which only exists in
experimental. Besides this, there is no need for dkms to depend on
python-apport as it only executes the package hook if apport is
installed. As apport pulls in the apport python module, everything
should be working as expected: Without installing apport everything is
working and people using apport should cope with the experimental nature
of… um… experimental. :)
However, /usr/sbin/dkms calls the hook if a build problem occurs (and
apport is installed) by executing it with python, which by default is a
symlink to python2. But apport pulls in the apport module for Python3.
And here we go. dkms will fail if it calls its apport-hook as Python2
doesn't know about Python3 modules.
There are several options:
* Use the attached patches to fix dkms to call python3 explicitly and
port the hook to Python3 (thanks to 2to3). The latter maybe need a
bit more grooming as I didn't test it.
* apport could at least suggest or recommend python-apport
* Let dkms only suggest python-apport. This should be OK as suggestions
won't be installed by default. So nobody is forced to install
a) software from experimental or
b) apport, even if it wouldn't be experimental.
Dirk
--- /usr/sbin/dkms_a 2011-12-07 19:23:58.0 +0100
+++ /usr/sbin/dkms_b 2014-07-31 09:35:28.319051875 +0200
@@ -2997,8 +2997,8 @@
report_build_problem()
{
#If apport is on the system, files a build problem
-if [ -x /usr/share/apport/apport ] which python/dev/null; then
- python /usr/share/apport/package-hooks/dkms_packages.py -m $module -v $module_version -k ${kernelver[0]}
+if [ -x /usr/share/apport/apport ] which python3/dev/null; then
+ python3 /usr/share/apport/package-hooks/dkms_packages.py -m $module -v $module_version -k ${kernelver[0]}
fi
die $@
}
--- /usr/share/apport/package-hooks/dkms_packages.py (original)
+++ /usr/share/apport/package-hooks/dkms_packages.py (refactored)
@@ -36,12 +36,12 @@
options=optparser.parse_args()[0]
if not options.module or not options.version:
-print sys.stderr, 'ERROR (dkms apport): both -m and -v are required'
+print('ERROR (dkms apport): both -m and -v are required', file=sys.stderr)
sys.exit(2)
package=packaging.get_file_package('/usr/src/' + options.module + '-' + options.version)
if package is None:
-print sys.stderr, 'ERROR (dkms apport): binary package for %s: %s not found' % (options.module,options.version)
+print('ERROR (dkms apport): binary package for %s: %s not found' % (options.module,options.version), file=sys.stderr)
sys.exit(1)
if options.kernel:
@@ -50,9 +50,9 @@
try:
apport.packaging.is_distro_package(kernel_package)
-except ValueError, e:
+except ValueError as e:
if e == 'package does not exist':
-print sys.stderr, 'ERROR (dkms apport): kernel package %s is not supported' % (kernel_package)
+print('ERROR (dkms apport): kernel package %s is not supported' % (kernel_package), file=sys.stderr)
sys.exit(1)
make_log=os.path.join('/var','lib','dkms',options.module,options.version,'build','make.log')
@@ -62,7 +62,7 @@
try:
report['SourcePackage'] = apport.packaging.get_source(package)
except ValueError:
-print sys.stderr, 'ERROR (dkms apport): unable to determine source package for %s' % package
+print('ERROR (dkms apport): unable to determine source package for %s' % package, file=sys.stderr)
sys.exit(3)
try:
version = packaging.get_version(package)
@@ -81,7 +81,7 @@
if 'DKMSBuildLog' in report:
this_year = str(datetime.today().year)
if 'Segmentation fault' in report['DKMSBuildLog']:
-print sys.stderr, 'ERROR (dkms apport): There was a segmentation fault when trying to build the module'
+print('ERROR (dkms apport): There was a segmentation fault when trying to build the module', file=sys.stderr)
sys.exit(1)
dupe_sig = ''
for line in report['DKMSBuildLog'].split('\n'):
Bug#750605: screen goes berserk, had to downgrade
found 750605 2:2.99.914-1~exp1 thanks ma == maximilian attems m...@stro.at writes: ma On Thu, Jun 05, 2014 at 05:33:21PM +0800, 積丹尼 Dan Jacobson wrote: VC == Vincent Cheng vch...@debian.org writes: VC Section Device VC Identifier Intel Graphics VC Driver intel VC Option AccelMethod uxa VC EndSection Indeed, that fixes it. ma Newer snapshat has sna fixes, please test 2:2.99.911+git20140607-1~exp1 ma (without uxa fallback) Bug still remains and is very bad in 2:2.99.914-1~exp1 . -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756598: fuse: post-installation script fails
Package: fuse Version: 2.9.3-14 Severity: grave Justification: renders package unusable I got the following error when upgrading fuse from 2.9.3-13 to 2.9.3-14: Setting up fuse (2.9.3-14) ... dpkg: error processing package fuse (--configure): subprocess installed post-installation script returned error exit status 1 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fuse depends on: ii adduser 3.113+nmu3 ii libc6 2.19-7 ii libfuse2 2.9.3-14 ii makedev 2.3.1-93 ii mount 2.20.1-5.8 ii sed 4.2.2-4 ii udev 204-14 fuse recommends no packages. fuse suggests no packages. -- Configuration Files: /etc/fuse.conf [Errno 13] Permission denied: u'/etc/fuse.conf' -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755327: gridsite: FTBFS: htcp.c:65:27: error: 'CURLOPT_FILE' undeclared (first use in this function)
Control: tag -1 patch Here's a fix. Feel free to pass it on upstream as necessary (I couldn't track down a current location for upstream revision control). * Test for old curl by version rather than with #ifndef, which breaks as of curl 7.37.1 (closes: #755327). diff -Nru gridsite-2.0.4/debian/patches/curl-defines.patch gridsite-2.0.4/debian/patches/curl-defines.patch --- gridsite-2.0.4/debian/patches/curl-defines.patch1970-01-01 01:00:00.0 +0100 +++ gridsite-2.0.4/debian/patches/curl-defines.patch2014-07-31 08:44:23.0 +0100 @@ -0,0 +1,44 @@ +Description: Test for old curl by version rather than with #ifndef + As of curl 7.37.1, CURLOPT_READDATA and CURLOPT_WRITEDATA are enums rather + than #defines and the old names are #defines instead; testing for them with + #ifndef results in #define loops. Use a version test instead to find out + whether we need compatibility definitions. +Author: Colin Watson cjwat...@ubuntu.com +Bug-Debian: https://bugs.debian.org/755327 +Forwarded: no +Last-Update: 2014-07-31 + +Index: b/src/htcp.c +=== +--- a/src/htcp.c b/src/htcp.c +@@ -61,11 +61,8 @@ + + /* deal with older versions of libcurl and curl.h */ + +-#ifndef CURLOPT_WRITEDATA ++#if (LIBCURL_VERSION_NUM 0x070907) + #define CURLOPT_WRITEDATA CURLOPT_FILE +-#endif +- +-#ifndef CURLOPT_READDATA + #define CURLOPT_READDATA CURLOPT_FILE + #endif + +Index: b/src/slashgrid.c +=== +--- a/src/slashgrid.c b/src/slashgrid.c +@@ -89,11 +89,8 @@ + + #define GRST_SLASH_HTCP_PORT 777 + +-#ifndef CURLOPT_WRITEDATA ++#if (LIBCURL_VERSION_NUM 0x070907) + #define CURLOPT_WRITEDATA CURLOPT_FILE +-#endif +- +-#ifndef CURLOPT_READDATA + #define CURLOPT_READDATA CURLOPT_INFILE + #endif + diff -Nru gridsite-2.0.4/debian/patches/series gridsite-2.0.4/debian/patches/series --- gridsite-2.0.4/debian/patches/series2014-05-12 14:46:46.0 +0100 +++ gridsite-2.0.4/debian/patches/series2014-07-31 08:38:37.0 +0100 @@ -3,3 +3,4 @@ gridsite-httpd24.patch gridsite-fprintf.patch gridsite-return-type.patch +curl-defines.patch Thanks, -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756591: package magics++_2.18.15-6 FTBFS on mips
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 grib-api (and hence emos) now works on mips! excellent. I will apply this patch. Thanks Alastair On 31/07/2014 08:50, Jurica Stanojkovic wrote: Package: magics++ Version: 2.18.15-6 Severity: important Tags: sid patch Justification: FTBFS User: debian-mips-dev-disc...@lists.alioth.debian.org Usertags: mips-patch Hello, Package magics++_2.18.15-6 FTBFS on mips: https://buildd.debian.org/status/fetch.php?pkg=magics%2B%2Barch=mipsver=2.18.15-6stamp=1406359409 For this package there is a special case in debian/rules and debian/control just for mips. Patch removes this special case. debian/rules: # Don't use emoslib on mips WITH_EMOSLIB:= --with-emos-libraries=/usr/lib --enable-bufr ifeq ($(ARCH), mips) WITH_EMOSLIB:= endif debian/control: Build-Depends: ... libemos-dev [!mips] I have attached a patch. With this patch package builds without an issue. Regards, Jurica -- Alastair McKinstry, alast...@sceal.ie, mckins...@debian.org, https://diaspora.sceal.ie/u/amckinstry A decent provision for the poor is the true test of civilization. ~Samuel Johnson, Boswell: Life of Johnson -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJT2gIhAAoJEN9LdrZRJ3Qs+MQP/19KfAHtmDZSz1Dn1m8HJ1nP NqgW2zQPtDWywBL/OSHHGZAzceEIB2ahMmqJ1rxYsAEdZMTDq/rQNeXCjRxTNiSx pNGYmJ9gNjUXU5OtYak2boQV7w+wpgjveVdfx8LbXUVtJ5d97/nj2+tWzuYK3ler XMcus8YJ+QYvFuObBx+t4s2IAijkPK3+ZYMPY/uGdxe+UMa/EwPux+TSsLd8PPls Q49gFESBRrSOj9+3JJdZw9+a9VSSAblKnwRSznCdxcblayrhz2Ouo4qs5Rz0JXAM LlfM3EGV0vJoamecY4Fi7yKpPuGFmjFPqFoWLupbH3GAUItCoTRDXQuJdxjK8o4b kxX0SHppe+BxWIaSnTNVU6bgMpNdZAZLAvoVy0BfvecRWiiCcCkT8HmjNBuCy67G METs6YymCs0vEfaZVkRh4/3+C7kEzf2enBnawatGXaeAU/1p03hG9oT9tkzbucim roOMRK2QsDZ+Umnho07+giCrx2sdtQRhY7eFehgE82rgVKjTwT6PNHBhrRSqau2e 4XIEONLrmo665CDmB/1MIrCyRj1sTR8GD3LqLxvoU8S4HazNw398xtwUdZF8spYM Fe8TP2zIpV21OdsWkHv7mkXxyqXwuWa3Og0E3TBFld/ZYP4Sw5R83RkmP9mGJghS utTZbzCzSDSeX9123ZZb =1087 -END PGP SIGNATURE-
Bug#737989: X selection coding system vs -enc UTF-8
tags 737989 +patch
thanks
When using textEncoding UTF-8, which now may be the default in debian,
the X text selection is STRING type but contains utf-8 bytes.
I expected STRING type to contain latin-1 bytes.
I suggest the change below letting Xutf8TextListToTextProperty() form
suitable bytes in the selection when running with -enc UTF-8. This
gives all selection data types STRING, COMPOUND_TEXT, TEXT and
UTF8_STRING.
Offering all these types gives maximum inter-operation with other X
programs. New enough programs might enjoy UTF8_STRING but traditional
programs may only know COMPOUND_TEXT and simplistic programs might only
take STRING.
--- XPDFCore.h.orig 2014-07-31 18:46:16.618036262 +1000
+++ XPDFCore.h 2014-07-31 09:44:06.534977028 +1000
@@ -223,6 +223,9 @@
static GString *currentSelection; // selected text
static XPDFCore *currentSelectionOwner;
static Atom targetsAtom;
+ static Atom textAtom;
+ static Atom compoundtextAtom;
+ static Atom utf8stringAtom;
GBool panning;
int panMX, panMY;
--- XPDFCore.cc.orig 2014-07-31 18:46:16.614036262 +1000
+++ XPDFCore.cc 2014-07-31 18:45:25.522038386 +1000
@@ -57,6 +57,9 @@
GString *XPDFCore::currentSelection = NULL;
XPDFCore *XPDFCore::currentSelectionOwner = NULL;
Atom XPDFCore::targetsAtom;
+Atom XPDFCore::textAtom;
+Atom XPDFCore::compoundtextAtom;
+Atom XPDFCore::utf8stringAtom;
//
// XPDFCoreTile
@@ -100,6 +103,9 @@
display = XtDisplay(parentWidget);
screenNum = XScreenNumberOfScreen(XtScreen(parentWidget));
targetsAtom = XInternAtom(display, TARGETS, False);
+ textAtom = XInternAtom(display, TEXT, False);
+ compoundtextAtom = XInternAtom(display, COMPOUND_TEXT, False);
+ utf8stringAtom = XInternAtom(display, UTF8_STRING, False);
paperPixel = paperPixelA;
mattePixel = mattePixelA;
@@ -443,7 +449,7 @@
// send back a list of supported conversion targets
if (*target == targetsAtom) {
-if (!(array = (Atom *)XtMalloc(sizeof(Atom {
+if (!(array = (Atom *)XtMalloc(4 * sizeof(Atom {
return False;
}
array[0] = XA_STRING;
@@ -451,6 +457,54 @@
*type = XA_ATOM;
*format = 32;
*length = 1;
+
+if (!globalParams-getTextEncodingName()-cmp(UTF-8)) {
+ array[1] = textAtom;
+ array[2] = compoundtextAtom;
+ array[3] = utf8stringAtom;
+ *length = 4;
+}
+return True;
+
+// ENHANCE-ME: If currentSelection could be made always UTF-8 then we
+// could use this UTF-8 code always, not just when the user chooses
+// UTF-8 in textEncoding / -enc. Can TextOutputDev be asked nicely to
+// give us UTF-8 in copySelection()?
+//
+ } else if (!globalParams-getTextEncodingName()-cmp(UTF-8)
+ (*target == XA_STRING
+ || *target == textAtom
+ || *target == compoundtextAtom)) {
+char *str = currentSelection-getCString();
+XICCEncodingStyle style
+ = (*target == XA_STRING ? XStringStyle
+ : *target == textAtom ? XStdICCTextStyle
+ : XCompoundTextStyle);
+XTextProperty t;
+int ret = Xutf8TextListToTextProperty(XtDisplay(widget),
+ str,1, style, t);
+if (ret 0) {
+ error(errInternal, -1 , cannot form text property, error {0:d}, ret);
+ return False;
+}
+*value = t.value;
+*type = t.encoding;
+*format = t.format;
+*length = t.nitems;
+return True;
+
+// UTF8_STRING case could be handled by Xutf8TextListToTextProperty()
+// above with XUTF8StringStyle if desired. But there's no conversion in
+// that case and XUTF8StringStyle is an XFree86 extension which might
+// not be present in older Xlib. A plain direct send lets us support
+// UTF8_STRING always.
+//
+ } else if (!globalParams-getTextEncodingName()-cmp(UTF-8)
+ *target == utf8stringAtom) {
+*value = XtNewString(currentSelection-getCString());
+*length = strlen((char*) *value);
+*type = utf8stringAtom;
+*format = 8; // 8-bit elements
return True;
// send the selected text
Bug#756574: lintian: Please consider removing the tag license-problem-gfdl-non-official-text.
On Thu, Jul 31, 2014 at 4:33 AM, Charles Plessy ple...@debian.org wrote: Package: lintian Version: 2.5.25 Severity: minor Dear Lintian maintainers, thanks for your work on Lintian. I use it a lot, including the pedantic tags. For one of them, license-problem-gfdl-non-official-text, I have strong doubts if it will ever be useful. In my understanding from the statistics from the Lintian website, hundreds if not thousands of upstream authors would need to be convinced to uppercase their GFDL statements. I think that it will never happen fully. Dear Charles, the matching is case insensitive, so case is not important for this tag (it will not fire if the case is only changes). If it is not clear, could you suggest more appropriate warning? For that reason, please remove the tag license-problem-gfdl-non-official-text, which is distracting and has no chances to have a significant effect. It is important for me as lintian developper. For each different wording I need to add a regex in lintian to check if it is really a free gfdl. And moreover it help to catch spelling mistake. I could add this tag is mainly for lintian developper if needed. Bastien 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#756600: xcfa: Insecure use of temporary files, subject to race conditions
Package: xcfa
Version: 4.3.1-1
Severity: important
Tags: security
xcfa contains several insecure uses of temporary files.
For example the file src/get_info.c has code to test that
curl is present, in the function GetInfo_wget which
essentially runs:
wget --user-agent=\Mozilla 22.0\ --directory-prefix=/tmp/
http://google.fr/
..
if [ -e /tmp/index.html ]; then
rm /tmp/index.html
fi
This is probably safe, because wget will not follow symlinks, and will
instead create index.html.1 - but any existing file called /tmp/index.html
will be removed regardless.
More serious issues exist throughout the codebase. For example the
code in dvdread_create_recap_audio, located in src/dvd_read.c contains
this lovely function:
// Suppression du fichier precedant si il existe
g_unlink (/tmp/get_infos_dvd.sh);
g_unlink (/tmp/infos_dvd.txt);
fp = fopen (/tmp/get_infos_dvd.sh, w);
fprintf (fp, #!/bin/sh\n);
fprintf (fp, \n);
fprintf (fp, set -e\n);
fprintf (fp, \n);
..
..
system (chmod +x /tmp/get_infos_dvd.sh);
system (/tmp/get_infos_dvd.sh);
g_unlink (/tmp/get_infos_dvd.sh);
Similarly the code which copies files to the trashbin, located in
src/file_trash.c,
has some nice code which runs:
system (env | grep \KDE_FULL_SESSION\
/tmp/tst_kde_full_session.txt);
if ((fp = fopen (/tmp/tst_kde_full_session.txt, r)) != NULL) {
while (fgets (buf, MAX_CARS_KDE, fp) != NULL) {
if (strcmp (buf, KDE_FULL_SESSION) == 0) {
if (strcmp (buf, true) == 0 || strcmp (buf,
TRUE) == 0) {
BoolRet = TRUE;
break;
}
}
}
fclose (fp);
}
g_unlink (/tmp/tst_kde_full_session.txt);
In short this codebase is rife with race-conditions allowing arbitrary shell
executation,
via /tmp/get_infos_dvd.sh, and file truncation/deletion.
I'd strongly urge the maintainer to audit the codebase for additional issues,
with the
help of upstream.
Steve
--
-- System Information:
Debian Release: 7.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-0.bpo.1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF8)
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#756599: printf(3) manpage: stray asterisk in NAN*
Package: manpages-dev Version: 3.65-1 Severity: minor The printf(3) manpage reads: The C99 standard specifies [-]inf or [-]infinity for infinity, and a string starting with nan for NaN, in the case of f conversion, and [-]INF or [-]INFINITY or NAN* in the case of F conversion.) Please remove the stray asterisk after NAN. -- 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#756601: ulatencyd: test
Package: ulatencyd Version: 0.5.0-9 Severity: wishlist This is a test -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ulatencyd depends on: ii dbus 1.8.6-1 ii libc6 2.19-7 ii libdbus-1-31.8.6-1 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.40.0-3 ii liblua5.1-05.1.5-5 ii libpolkit-gobject-1-0 0.105-6.1 ii libxau61:1.0.8-1 ii libxcb11.10-3 ii lua-posix 31-2 ii lua5.1 [lua] 5.1.5-5 Versions of packages ulatencyd recommends: ii consolekit 0.4.6-4 ulatencyd 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#756598: fuse: post-installation script fails
Hi, reproduced. More info: root@ensifera:~# sh -x /var/lib/dpkg/info/fuse.postinst configure 2.9.3-13 + set -e + dpkg-statoverride --list /bin/fusermount + chmod 4755 /bin/fusermount + modprobe fuse + grep -qs fuse + lsmod + udevadm control --reload-rules + [ -e /dev/fuse ] + udevadm info -q path -n /dev/fuse + udevadm test -e -p /devices/virtual/misc/fuse root@ensifera:~# echo $? 1 Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672218: rsyslog: Logrotate error message
Arne Wichmann [2012-05-09 10:20 +0200]: postrotate invoke-rc.d rsyslog rotate /dev/null endscript So what exactly would be wrong with just using service instead of invoke-rc.d? Sure, that would call the init.d script also under systemd, but do_rotate() is more or less just a fancy SIGHUP, so that should work just fine? I tested it under systemd as well. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.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#362483: rss2email: Unabled to disable 301 redirection for select feeds
* Keith Hellman khell...@mcprogramming.com [140731 09:14]: I access a number of 'private' feeds associated with my university research group. rss2email detects the 301 redirection and saves the new (redirected) url --- but this disables access next time an attempt is made. I've attached a patch that uses a new command 'explicit' to prevent select feeds from respecting the embedded redirection information. Hello, I've been triaging old bugs and stumbled upon this one. The semantics of a 301 redirection are clear, and according to RFC2616, rss2email as a clients with link editing capabilities should change the URL in its database. I don't know the specifics of these private URLs but maybe another redirection such as 302 would be better. Thanks for your bug report. -- Etienne Millon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755327: Upstream commit
Hi Colin, David and Mattias. I found the upstream repository, and the upstream commit that fixes this issue. https://github.com/CESNET/gridsite/commit/2124d471f9fc1eed4bf5893ed2701350357c01af Since the code was just too old to be useful they just dropped it, I tested in a clean trusty environment and everything still builds fine (curl 7.35.0), and in a clean sid pbuilder environment (curl 7.37.1) This is the debdiff diff -Nru gridsite-2.0.4/debian/changelog gridsite-2.0.4/debian/changelog --- gridsite-2.0.4/debian/changelog 2014-05-12 15:51:28.0 +0200 +++ gridsite-2.0.4/debian/changelog 2014-07-31 11:11:23.0 +0200 @@ -1,3 +1,11 @@ +gridsite (2.0.4-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Cherry-pick upstream commit 2124d471f9fc + to fix a FTBFS with curl = 7.37.1 (Closes: #755327) + + -- Gianfranco Costamagna costamagnagianfra...@yahoo.it Thu, 31 Jul 2014 11:10:15 +0200 + gridsite (2.0.4-3) unstable; urgency=medium * Add missing Build-Requires on pkg-config (Closes: #747768) diff -Nru gridsite-2.0.4/debian/patches/curl-defines.patch gridsite-2.0.4/debian/patches/curl-defines.patch --- gridsite-2.0.4/debian/patches/curl-defines.patch 1970-01-01 01:00:00.0 +0100 +++ gridsite-2.0.4/debian/patches/curl-defines.patch 2014-07-31 11:08:09.0 +0200 @@ -0,0 +1,38 @@ +From 2124d471f9fc1eed4bf5893ed2701350357c01af Mon Sep 17 00:00:00 2001 +From: =?UTF-8?q?Franti=C5=A1ek=20Dvo=C5=99=C3=A1k?= val...@civ.zcu.cz +Date: Mon, 21 Jul 2014 11:10:42 +0200 +Subject: [PATCH] Remove ancient curl compatibility stuff. This fixes build + with curl 7.37.1 on Fedora 22/rawhide. + +--- + src/htcp.c | 14 -- + 1 file changed, 14 deletions(-) + +diff --git a/src/htcp.c b/src/htcp.c +index 6d60720..3e1f5a4 100644 +--- a/src/htcp.c b/src/htcp.c +@@ -59,20 +59,6 @@ + + #include gridsite.h + +-/* deal with older versions of libcurl and curl.h */ +- +-#ifndef CURLOPT_WRITEDATA +-#define CURLOPT_WRITEDATA CURLOPT_FILE +-#endif +- +-#ifndef CURLOPT_READDATA +-#define CURLOPT_READDATA CURLOPT_FILE +-#endif +- +-#ifndef CURLE_HTTP_RETURNED_ERROR +-#define CURLE_HTTP_RETURNED_ERROR CURLE_HTTP_NOT_FOUND +-#endif +- + #define HTCP_GET 1 + #define HTCP_PUT 2 + #define HTCP_DELETE 3 +-- +2.0.3 + diff -Nru gridsite-2.0.4/debian/patches/series gridsite-2.0.4/debian/patches/series --- gridsite-2.0.4/debian/patches/series 2014-05-12 15:46:46.0 +0200 +++ gridsite-2.0.4/debian/patches/series 2014-07-31 11:12:11.0 +0200 @@ -3,3 +3,4 @@ gridsite-httpd24.patch gridsite-fprintf.patch gridsite-return-type.patch +curl-defines.patch cheers, Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756602: printf(3) manpage: please document that %n can't include flags, width or precision
Package: manpages-dev Version: 3.65-1 Severity: minor The only place where flags for the n conversion are mentioned in description of the 0 flag: Except for n conversions, ... This is a bit odd, because the other flags don't make sense for %n either. In fact, the C99 standard says that if the n conversion specification includes any flags, a field width, or a precision, the behavior is undefined. Please document this fact in the manual page. -- 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#753848: libiscsi: FTBFS with clang instead of gcc
On Sat, 5 Jul 2014 12:27:48 -0500 Arthur Marble art...@info9.net wrote: Package: libiscsi Severity: minor Usertags: clang-ftbfs User: pkg-llvm-t...@lists.alioth.debian.org Tag: patch Hello, Using the rebuild infrastructure, your package fails to build with clang (instead of gcc). Care to show at least the error messages from clang? Also, which version of libiscsi we're talking about? And your patch is wrong, all places it changes are now misbehaving. This one is gross: --- libiscsi-1.11.0.orig/test-tool/test_preventallow_cold_reset.c +++ libiscsi-1.11.0/test-tool/test_preventallow_cold_reset.c @@ -51,7 +51,6 @@ test_preventallow_cold_reset(void) logging(LOG_VERBOSE, Perform cold reset on target); ret = iscsi_task_mgmt_target_cold_reset_sync(iscsic); logging(LOG_VERBOSE, Wait until all unit attentions clear); - while (testunitready(iscsic, tgt_lun) != 0); CU_ASSERT_EQUAL(ret, 0); This loop must stay or else the test will fail. /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755996: ulatencyd: Install ulatencyd with systemd can not normal shutdown (even as root)
Package: ulatencyd Version: 0.5.0-9 Followup-For: Bug #755996 Hi I solved this bug. Created an service ulatencyd-stop.service wich trigger stop ulatencyd.service on shutdown.target, poweroff.target, halt.target Copy file from attachment on /lib/systemd/system and then run as root (systemctl enable ulatencyd-stop.service) -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ulatencyd depends on: ii dbus 1.8.6-1 ii libc6 2.19-7 ii libdbus-1-31.8.6-1 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.40.0-3 ii liblua5.1-05.1.5-5 ii libpolkit-gobject-1-0 0.105-6.1 ii libxau61:1.0.8-1 ii libxcb11.10-3 ii lua-posix 31-2 ii lua5.1 [lua] 5.1.5-5 Versions of packages ulatencyd recommends: ii consolekit 0.4.6-4 ulatencyd suggests no packages. -- no debconf information [Unit] Description=Service to stop ulatencyd on shutdown [Service] ExecStart=/bin/systemctl stop ulatencyd.service [Install] WantedBy=poweroff.target halt.target reboot.target
Bug#755088: please show removals *last* in dist-upgrade
[To the actor who has the honor to play me in the theater adoption of my biography reading this to prepare properly for the role of his lifetime: Don't play me cocky or passive aggressive, even if this mail sounds a bit like it; this isn't intended as such. ;) ] On Tue, Jul 29, 2014 at 05:50:29PM +0200, Michael Vogt wrote: On Thu, Jul 17, 2014 at 12:28:09PM -0400, Joey Hess wrote: So, I suggest sorting the output with the most important items last, to go with the UPPERCASE highlighting apt already gives them. This is a excellent idea! You've gotta be kidding me! YOU HAVE GOTTA BE FU**ING KIDDING ME! Attached is a patch that implements it as the new default for apt. It is the beginning of May 2009, a young student and linux greenhorn begins hacking on a tool he is using every day now while using Debian sid [based sidux, now called aptosid] (as nothing else supported his wlan card properly) to fix the most annoying problems in it. The first five issues he tackled were: - allow codenames to specify a release via -t - add possibility to reorder the warning section (Warning-Order) - working simulation for normal users with -s - (configureable) colorization of ShowLists titles - enhance debugging output of depcache A few more things followed, a few days/weeks later he actually published this by sending the easier ones to open bugreports and dropping the entire branch on launchpad. Shortly after that a strange man contacted the student who had noticed his activities … As for apt-get I am a little bit concerned that changing this breaks some peoples workflow. So maybe switching the default for apt-get in 1.2? Or am I too conservative here :) ? … he said he liked most of what he saw. Stuff like the reordering or color would not be possible (beside that he also didn't like it) for backward-compatibility reasons, but the rest would be fine and great and all and we should work together, improve it further and merge it. The young student was happy. He hadn't imagined that the stuff he had hacked together would be deemed good enough for worldwide deployment! Of course, he still liked his reorder and the color, but the man had reasons and the student was not experienced enough to counter this. Five years later, the once die-hard crusader for the church of never change the output became soft and proposes himself to change the output causing his student to stand in disbelieve on the sideline… For general entertainment, I have attached the commit from back then as this bzr branch itself isn't available online anymore. There might be still some ideas hidden in it (read: documentation and maybe error checking?) even if the code is dated by now. Also, if we reorder by default, I think the order should be: Upgraded,New,Hold,Kept,Remove,Downgraded,Essential,Stats New after Upgraded is probably a bit unusual, but from a pure, ordered by interest point of view, new packages are probably more interesting than packages which get just a new version. About Downgrade I am not really sure: It isn't done automatic and the user propably knows what he requested himself, but they are generally dangerous (as they aren't supported), so … I am usually not that well suited as no-change-crusader, but as you force me to it: I would say 'apt' is fair game as it is advertised as such, but we should keep apt-get as-is forever even if I am hopeful that nothing is depending that much on the output order to really care (expect our own testcases maybe). We should also look into having binary-specific configuration trees (something like: If binary is apt-bla, merge Command::apt-bla-tree into root-tree). This branch includes also some other changes which never went into mainline, so expect some commits after I am back from my holiday… You owe me, my friend! Like big time… ;) Best regards David Kalnischkies revno: 1782 committer: David Kalnischkies kalnischk...@gmail.com branch nick: apt timestamp: Thu 2009-05-07 23:50:11 +0200 message: [apt-get] add possibility to reorder the warning section (Warning-Order) * apply on all operations installing (or removing) packages * two translatable strings (malformed errormessages) and a bit of doc * Suggest and Recommend is not included in this reordering (for now) diff: === modified file 'cmdline/apt-get.cc' --- cmdline/apt-get.cc 2009-04-14 12:17:40 + +++ cmdline/apt-get.cc 2009-05-07 21:50:11 + @@ -753,18 +753,51 @@ bool Essential = false; // Show all the various warning indicators - ShowDel(c1out,Cache); - ShowNew(c1out,Cache); - if (ShwKept == true) - ShowKept(c1out,Cache); - Fail |= !ShowHold(c1out,Cache); - if (_config-FindB(APT::Get::Show-Upgraded,true) == true) - ShowUpgraded(c1out,Cache); - Fail |= !ShowDowngraded(c1out,Cache); - if (_config-FindB(APT::Get::Download-Only,false) == false) -Essential = !ShowEssential(c1out,Cache); - Fail |=
Bug#756600: xcfa: Insecure use of temporary files, subject to race conditions
Hello, On Thu, Jul 31, 2014 at 10:00 AM, Steve Kemp st...@steve.org.uk wrote: Package: xcfa Version: 4.3.1-1 Severity: important Tags: security xcfa contains several insecure uses of temporary files. Thank you Steve for the great work. Claude, can you please have a look at this bug? It sounds pretty serious. http://bugs.debian.org/756600 Thanks in advance for any reply, and cheers! -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer| quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756604: systemd: NoNewPrivileges allows UID changes, while the doc says it prohibits it
Package: systemd
Version: 208-6
Severity: normal
Hi,
the attached unit file has NoNewPrivileges set to yes, which,
according to systemd.exec(5), prohibits UID changes of any kind.
However, the tor daemon it starts successfully manages to change its
UID to debian-tor, as configured with User debian-tor in
/usr/share/tor/tor-service-defaults-torrc:
# systemctl status tor.service
tor.service - Anonymizing overlay network for TCP
Loaded: loaded (/etc/systemd/system/tor.service; disabled)
Active: active (running) since Thu 2014-07-31 11:25:47 CEST; 14min ago
Process: 30506 ExecStartPre=/usr/bin/tor --defaults-torrc
/usr/share/tor/tor-service-defaults-torrc --verify-config (code=exited,
status=0/SUCCESS)
Main PID: 30509 (tor)
CGroup: /system.slice/tor.service
└─30509 /usr/bin/tor --defaults-torrc
/usr/share/tor/tor-service-defaults-torrc --RunAsDaemon 0
$ ps aux | grep usr/bin/tor
debian-+ 30509 0.1 0.2 66536 33708 ?Ss 11:25 0:01 /usr/bin/tor
--defaults-torrc /usr/share/tor/tor-service-defaults-torrc --RunAsDaemon 0
Did I misunderstand the documentation, or is the doc wrong, or is
there a bug somewhere?
Cheers,
--
intrigeri
[Unit]
Description = Anonymizing overlay network for TCP
After = syslog.target network.target nss-lookup.target
[Service]
Type = simple
ExecStartPre = /usr/bin/tor --defaults-torrc
/usr/share/tor/tor-service-defaults-torrc --verify-config
# A torrc that has RunAsDaemon 1 won't work with the simple service type;
# let's explicitly override it.
ExecStart = /usr/bin/tor --defaults-torrc
/usr/share/tor/tor-service-defaults-torrc --RunAsDaemon 0
ExecReload = /bin/kill -HUP ${MAINPID}
KillSignal = SIGINT
TimeoutSec = 30
Restart = on-failure
LimitNOFILE = 32768
# Hardening
PrivateTmp = yes
DeviceAllow = /dev/null rw
DeviceAllow = /dev/urandom r
InaccessibleDirectories = / /home # does not extend to submounts
ReadOnlyDirectories = /etc /usr
ReadWriteDirectories = /var/lib/tor /var/log/tor
NoNewPrivileges = yes
#AppArmorProfile = system_tor
[Install]
WantedBy = multi-user.target
Bug#756603: npm list fails: Cannot find module 'ansicolors'
Package: npm Version: 1.4.21+ds-1 Severity: normal Dear maintainer, The npm list command (in unstable) seems to use the ansicolors module, but AFAICS it is not available in Debian yet? matthijs@grubby:~$ npm list npm ERR! Error: Cannot find module 'ansicolors' npm ERR! at Function.Module._resolveFilename (module.js:338:15) npm ERR! at Function.Module._load (module.js:280:25) npm ERR! at Module.require (module.js:364:17) npm ERR! at require (module.js:380:17) npm ERR! at Object.anonymous (/usr/share/npm/lib/ls.js:18:13) npm ERR! at Module._compile (module.js:456:26) npm ERR! at Object.Module._extensions..js (module.js:474:10) npm ERR! at Module.load (module.js:356:32) npm ERR! at Function.Module._load (module.js:312:12) npm ERR! at Module.require (module.js:364:17) npm ERR! If you need help, you may report this *entire* log, npm ERR! including the npm and node versions, at: npm ERR! http://github.com/npm/npm/issues npm ERR! System Linux 3.14-1-amd64 npm ERR! command /usr/bin/nodejs /usr/bin/npm list npm ERR! cwd /home/matthijs npm ERR! node -v v0.10.29 npm ERR! npm -v 1.4.21 npm ERR! code MODULE_NOT_FOUND npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/matthijs/npm-debug.log npm ERR! not ok code 0 Gr. Matthijs -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-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 npm depends on: ii node-abbrev 1.0.4-2 ii node-ansi 0.2.1-1 ii node-ansi-color-table 1.0.0-1 ii node-archy0.0.2-1 ii node-block-stream 0.0.7-1 ii node-fstream 0.1.24-1 ii node-fstream-ignore 0.0.6-2 ii node-github-url-from-git 1.1.1-1 ii node-glob 3.2.6-1 ii node-graceful-fs 2.0.0-2 ii node-gyp 0.12.2+ds-1 ii node-inherits 2.0.0-1 ii node-ini 1.1.0-1 ii node-lockfile 0.4.1-1 ii node-lru-cache2.3.1-1 ii node-minimatch0.2.12-1 ii node-mkdirp 0.3.5-1 ii node-nopt 3.0.1-1 ii node-npmlog 0.0.4-1 ii node-once 1.1.1-1 ii node-osenv0.0.3-1 ii node-read 1.0.4-1 ii node-read-package-json1.1.3-1 ii node-request 2.26.1-1 ii node-retry0.6.0-1 ii node-rimraf 2.2.2-2 ii node-semver 2.1.0-2 ii node-sha 1.2.3-1 ii node-slide1.1.4-1 ii node-tar 0.1.18-1 ii node-underscore 1.4.4-2 ii node-which1.0.5-2 ii nodejs0.10.29~dfsg-1 npm recommends no packages. npm 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#756605: okular doesn't show fi ligatures
Package: okular Version: 4:4.13.1-2 Severity: normal Dear Maintainer, Problem: okular doesn't show fi ligatures in PDFs with no embedded fonts. Causes: 1) poppler/fontconfig replaces generic non-embedded fonts (e.g. Times) with tex-gyre fonts (e.g. /usr/share/texmf/fonts/opentype/public/tex-gyre /texgyreheroscn-bold.otf) 2) Package fonts-texgyre sets high-priority substitution for Times and related fonts in /etc/fonts/conf.avail/65-fonts-texgyre.conf Solution: apt-get remove --purge fonts-texgyre Upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=73291 Best regards, --Martin -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages okular depends on: ii kde-runtime 4:4.13.1-1 ii libc6 2.19-7 ii libfreetype62.5.2-1 ii libjpeg88d1-1 ii libkactivities6 4:4.13.1-1 ii libkdecore5 4:4.13.3-1 ii libkdeui5 4:4.13.3-1 ii libkexiv2-114:4.13.1-1 ii libkio5 4:4.13.3-1 ii libkparts4 4:4.13.3-1 ii libkprintutils4 4:4.13.3-1 ii libkpty44:4.13.3-1 ii libokularcore4 4:4.13.1-2 ii libphonon4 4:4.7.1-1 ii libpoppler-qt4-40.26.3-1 ii libqca2 2.0.3-6 ii libqimageblitz4 1:0.0.6-4 ii libqmobipocket1 4:4.12.2-2 ii libqt4-dbus 4:4.8.6+dfsg-2 ii libqt4-declarative 4:4.8.6+dfsg-2 ii libqt4-svg 4:4.8.6+dfsg-2 ii libqt4-xml 4:4.8.6+dfsg-2 ii libqtcore4 4:4.8.6+dfsg-2 ii libqtgui4 4:4.8.6+dfsg-2 ii libsolid4 4:4.13.3-1 ii libspectre1 0.2.7-2 ii libstdc++6 4.9.1-1 ii phonon 4:4.7.1-1 ii zlib1g 1:1.2.8.dfsg-1 okular recommends no packages. Versions of packages okular suggests: ii ghostscript9.05~dfsg-8.1 pn jovie none pn okular-extra-backends none ii poppler-data 0.4.6-5 ii texlive-binaries 2014.20140528.34243-4 pn unrar none -- 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#756606: postgresql-9.1: Init-Script does not work together with heartbeat
Package: postgresql-9.1
Version: 9.1.13-0wheezy1
Severity: important
Dear Maintainer,
After drbd, heartbeat and postgresql-9.1 is installed and basically configured,
the attempt to run postgresql init script from heartbeat's haresources fails in
multiple ways.
Unfortunately, I cannot even tell why it doesn't work, since I cannot even see
reasons why this doesn't work in ha-debug log with debuging enabled.
The following lists what's going wrong:
1) A usual case for Postgres HA Clusters is to have /var/lib/postgresql in a
DRBD synced resource, which is only mounted on one node at a time. When you
have a resource group configured to start drbddisk, mount /var/lib/postgresql,
start postgresql (in that order - see haresources - file listed later in this
report) and start up heartbeat on both nodes, these resources are only started
on the primary node for this resource group (first field in haresources file).
These resources are not acquired on the standby - node.
Unfortunately, when stoping heartbeat on the standby node, heartbeat
nevertheless tries to give up resources, even it hasn't acquired them before.
Since /var/lib/postgresql wasn't mounted before on that node, issuing
/etc/init.d/postgresql stop on the standby node fails, since it cannot find
necessary files in /var/lib/postgresql .
Even without having heartbeat STONITH configured, this leads to a hard server
reset somehow.
Solution: /etc/init.d/postgresql stop shouldn't return an error when the
datadir is empty to make it usable along with heartbeat.
2) When starting heartbeat, it seems like postgresql isn't started at all. I do
not understand this, since all other init-scripts I have tested (samba, cron)
are working fine when used instead of postgresql in quoted haresources file
below.
I have tried this on multiple, clean Debian wheezy installs from Bare metal
server to workstation VirtualBox setups. The result is always the same.
You find the logs and configurations used following this line:
/etc/ha.d/haresources :
prod-cl3 drbddisk::var_lib_postgres
Filesystem::/dev/drbd0::/var/lib/postgresql::ext4 IPaddr::192.168.20.18/24/eth0
postgresql
===
/etc/ha.d/ha.cf :
debugfile /var/log/ha-debug
logfile /var/log/ha-log
logfacility local0
keepalive 2
deadtime 30
warntime 10
initdead 90
udpport 694
ucast eth1 10.250.250.16
auto_failback on
node prod-cl3
node prod-cl4
===
/etc/drbd.conf :
include drbd.d/global_common.conf;
include drbd.d/*.res;
===
/etc/drbd.d/global_common.conf :
global {
usage-count yes;
}
common {
protocol C;
startup {
wfc-timeout 15;
degr-wfc-timeout 120;
}
disk {
on-io-error detach;
}
net {
after-sb-0pri disconnect;
after-sb-1pri disconnect;
after-sb-2pri disconnect;
rr-conflict disconnect;
}
syncer {
rate 96256;
}
}
===
/etc/drbd.d/prod-cl.res :
resource var_lib_postgres {
protocol C;
on prod-cl3 {
device /dev/drbd0;
disk/dev/prod-cl3_data/var_lib_postgres;
address 10.250.250.16:7789;
meta-disk internal;
}
on prod-cl4 {
device /dev/drbd0;
disk/dev/prod-cl4_data/var_lib_postgres;
address 10.250.250.17:7789;
meta-disk internal;
}
}
===
ha-debug log, showing postgres isn't even started on primary node when
heartbeat starts:
Jul 30 13:51:11 prod-cl3 heartbeat: [20846]: WARN: Core dumps could be lost if
multiple dumps occur.
Jul 30 13:51:11 prod-cl3 heartbeat: [20846]: WARN: Consider setting non-default
value in /proc/sys/kernel/core_pattern (or equivalent) for maximum
supportability
Jul 30 13:51:11 prod-cl3 heartbeat: [20846]: WARN: Consider setting
/proc/sys/kernel/core_uses_pid (or equivalent) to 1 for maximum supportability
Jul 30 13:51:11 prod-cl3 heartbeat: [20846]: info: Pacemaker support: false
Jul 30 13:51:11 prod-cl3 heartbeat: [20846]: WARN: Logging daemon is disabled
--enabling logging daemon is recommended
Jul 30 13:51:11 prod-cl3 heartbeat: [20846]: info: **
Jul 30 13:51:11 prod-cl3 heartbeat: [20846]: info: Configuration validated.
Starting heartbeat 3.0.5
Jul 30 13:51:11 prod-cl3 heartbeat: [20847]: info: heartbeat: version 3.0.5
Jul 30 13:51:12 prod-cl3 heartbeat: [20847]: info: Heartbeat generation:
1406638883
Jul 30 13:51:12 prod-cl3 heartbeat: [20847]: info: glib: ucast: write socket
priority set to IPTOS_LOWDELAY on eth1
Jul 30 13:51:12 prod-cl3 heartbeat: [20847]: info: glib: ucast: bound send
socket to device: eth1
Jul 30 13:51:12 prod-cl3 heartbeat: [20847]: info: glib: ucast: bound receive
socket to device: eth1
Jul 30 13:51:12
Bug#555819: r2e download now all message smultipe times...
* Michelle Konzack linux4miche...@tamay-dogan.net [140731 09:46]: Hello Maintainer, I am now using rss2email since some month and it worked perfectly, even with a huge bunch of rss feeds but NOW since some days it starts downloading any messages again with each run. It seems, I have hit a limit in r2e. I have now installed a procmail recipe which filter by subject, but this is no long-term solution, because I get with this bug more then 4000 messages a day and have to cleanup this crap manualy. However, I would suggest a rewrite of r2e which use one database file per RSS-Feed (I am sightly sure it is a size limit because it has 996834 bytes and does not more grow since several days) I do not think, it is a good option to hack my own r2e script. If you have an idea how to debug this error, please let me know. Hello Michelle, I believe that this behaviour has been fixed in the 3.x branch of rss2email which changes how the database is stored and it should be more robust. You can install a version from testing, migrate your data using r2e-migrate and check if the problem still exists. Thanks for testing it with lots of feeds :) -- Etienne Millon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756607: npm: Confusing error with binary node modules
Package: npm Version: 1.4.21+ds-1 Severity: normal Dear maintainer, when installing the serialport package through npm, I get the following messages: matthijs@grubby:~$ npm install -g serialport /home/matthijs/.node_modules/bin/serialportterm - /home/matthijs/.node_modules/lib/node_modules/serialport/bin/serialportTerminal.js /home/matthijs/.node_modules/bin/serialportlist - /home/matthijs/.node_modules/lib/node_modules/serialport/bin/serialportList.js serialport@1.4.2 install /home/matthijs/.node_modules/lib/node_modules/serialport node-pre-gyp install --fallback-to-build sh: 1: node-pre-gyp: not found npm WARN This failure might be due to the use of legacy binary node npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian npm ERR! serialport@1.4.2 install: `node-pre-gyp install --fallback-to-build` npm ERR! Exit status 127 npm ERR! npm ERR! Failed at the serialport@1.4.2 install script. npm ERR! This is most likely a problem with the serialport package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-pre-gyp install --fallback-to-build npm ERR! You can get their info via: npm ERR! npm owner ls serialport npm ERR! There is likely additional logging output above. npm ERR! System Linux 3.14-1-amd64 npm ERR! command /usr/bin/nodejs /usr/bin/npm install -g serialport npm ERR! cwd /home/matthijs npm ERR! node -v v0.10.29 npm ERR! npm -v 1.4.21 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/matthijs/npm-debug.log npm ERR! not ok code 0 I haven't figured out what the actual problem is yet, but I want to point this message: npm WARN This failure might be due to the use of legacy binary node npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian However, the referenced README.Debian doesn't actually talk about anything related at all - nothing in there helps me solve this problem. README.Debian from the npm package doesn't help either. Perhaps this info was removed at some point? Gr. Matthijs -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-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 npm depends on: ii node-abbrev 1.0.4-2 ii node-ansi 0.2.1-1 ii node-ansi-color-table 1.0.0-1 ii node-archy0.0.2-1 ii node-block-stream 0.0.7-1 ii node-fstream 0.1.24-1 ii node-fstream-ignore 0.0.6-2 ii node-github-url-from-git 1.1.1-1 ii node-glob 3.2.6-1 ii node-graceful-fs 2.0.0-2 ii node-gyp 0.12.2+ds-1 ii node-inherits 2.0.0-1 ii node-ini 1.1.0-1 ii node-lockfile 0.4.1-1 ii node-lru-cache2.3.1-1 ii node-minimatch0.2.12-1 ii node-mkdirp 0.3.5-1 ii node-nopt 3.0.1-1 ii node-npmlog 0.0.4-1 ii node-once 1.1.1-1 ii node-osenv0.0.3-1 ii node-read 1.0.4-1 ii node-read-package-json1.1.3-1 ii node-request 2.26.1-1 ii node-retry0.6.0-1 ii node-rimraf 2.2.2-2 ii node-semver 2.1.0-2 ii node-sha 1.2.3-1 ii node-slide1.1.4-1 ii node-tar 0.1.18-1 ii node-underscore 1.4.4-2 ii node-which1.0.5-2 ii nodejs0.10.29~dfsg-1 npm recommends no packages. npm 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#568092: daemontools: support QUIT, USR[12] signals
tags 568092 + wontfix quit On Tue, Feb 02, 2010 at 11:03:31PM +1100, Matthew Palmer wrote: It would be handy if we could send QUIT/USR1/USR2 signals to supervise-managed processes. Handily, there's already a patch for that out in the wild: http://thedjbway.b0llix.net/patches/daemontools-0.76.sigq12.patch I adjusted it ever-so-slightly and added manpage bits, to produce the attached patch. Hi, sorry for the late reply and thanks for the patch. I'm not about to apply the patch though, for the same reason as bug#534508 is wontfix: I actually want to keep daemontools in Debian as close to upstream as possible. There are alternatives you can use, like runit, perp, s6, ... Regards, Gerrit. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733059: gnome-screensaver cannot be launched by alternative gnome-session
On Sun, 18 May 2014 at 20:36:42 +0100, Mike Crowe wrote: gnome-settings-daemon, nm-applet and (my) i3-gnome are launched correctly yet gnome-screensaver is not. This appears to be due to the following line in /usr/share/gnome/autostart/gnome-screensaver.desktop: AutostartCondition=GNOME3 if-session gnome-flashback (I assume that modern gnome-shell launches gnome-screensaver itself now.) Modern gnome-shell doesn't use gnome-screensaver at all: it has a built-in screen shield which integrates with gdm. Perhaps there is a way to invert this condition so that gnome-screensaver is enabled except on GNOME3? The upstream solution to this appears to have been to remove gnome-screensaver from the autostart directory entirely, so that it will be started by exactly those GNOME sessions that list it as a required component (notably gnome-flashback, which is part of src:gnome-panel, and your custom i3-gnome session). https://bugzilla.gnome.org/show_bug.cgi?id=683060 https://git.gnome.org/browse/gnome-screensaver/commit/?id=1940dc6bc8ad5ee2c029714efb1276c05ca80bd4 Could you try that, please? gnome-screensaver is essentially dead upstream - it's part of gnome-session-flashback (the former gnome-session-fallback). Both MATE and Cinnamon appear to have either forked or replaced gnome-screensaver in their environments, which seems a shame... S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754280: ganeti-2.11 - gnt-cluster upgrade writes config backup in /var/lib
Control: tags -1 pending Hi Bastian, On 10:32 Fri 25 Jul , Bastian Blank wrote: Control: severity -1 serious On Wed, Jul 09, 2014 at 02:54:58PM +0200, Bastian Blank wrote: But on the other hand the FHS mandates to use a sub-directory. | An application (or a group of inter-related applications) must use a | subdirectory of /var/lib for its data. This bug is actually a FHS violation. So I'm now setting the appropriate severity. After discussing it upstream, we are now able to specify the backup location during configure time (which I intend to set to /var/backups). This change is part of 2.11.4 which was released today. Unfortunately I cannot upload yet because a Haskell package transition is underway and building Ganeti in sid doesn't currently work. Regards, Apollon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756604: systemd: NoNewPrivileges allows UID changes, while the doc says it prohibits it
Hi, On 07/31/2014 11:42, intrig...@debian.org wrote: the attached unit file has NoNewPrivileges set to yes, which, according to systemd.exec(5), prohibits UID changes of any kind. However, the tor daemon it starts successfully manages to change its UID to debian-tor, as configured with User debian-tor in /usr/share/tor/tor-service-defaults-torrc: [...] Did I misunderstand the documentation, or is the doc wrong, or is there a bug somewhere? It works as intended, but the documentation might be a bit misleading. NoNewPrivileges only affects the exec syscall which will no longer grant any new privileges, including no longer switching uid for suid binaries. It does *not* take away the CAP_SETUID or any other capabilities the process already has. See also man:prctl(2) and Documentation/prctl/no_new_privs.txt in the Linux kernel documentation. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734851: feature request
severity 734851 wishlist quit On Fri, Jan 10, 2014 at 06:26:38PM +0800, Wang Jian wrote: When using daemontools-run, only root can manipulate /etc/service. That sets strong limitation. For security reason, in a server farm for internet services, application processes that do real work are normally run under non-priviledged account instead of root, and separated from internet by frontend servers (load balancers). In the said scenario, daemontools should run under non-priviledged accounts. This eases operations. Here is my solution https://github.com/lark/daemontools-userrun Note that it still supports /etc/service for root (when configured). The only problem is without init's help (/etc/inittab), svscan may be killed and no respawn happens. IMHO, it's not a big problem if oom killer doesn't kill it. Please consider incorporate this 'daemontools-userrun' functionality into daemontools packages. The said git repository is in-house operation work so no explicit license is attached, while the code is based upon svscanboot. Hi, thanks for the suggestion. Unfortunately I have only limited time available to work on these Debian packages, so for now I set this report to severity wishlist and keep it in the packages' bug list. Regards, Gerrit. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545286: mention setlock -n return value
On Sun, Sep 06, 2009 at 05:47:48PM +0800, jida...@jidanni.org wrote: Mention return value of -n No delay. If fn is locked by another process, setlock gives up. Please provide a patch, git clone http://smarden.org/git/daemontools.git -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733059: gnome-screensaver cannot be launched by alternative gnome-session
On Thu, 31 Jul 2014 at 10:56:39 +0100, Simon McVittie wrote: The upstream solution to this appears to have been to remove gnome-screensaver from the autostart directory entirely, so that it will be started by exactly those GNOME sessions that list it as a required component (notably gnome-flashback, which is part of src:gnome-panel, and your custom i3-gnome session). It would probably also be a good idea to ask the maintainers of non-core GNOME sessions in Debian (according to apt-file that means cairo-dock-core, openbox-gnome-session and xmonad) to either add gnome-screensaver to their sessions, or make a deliberate decision not to do so. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756604: systemd: NoNewPrivileges allows UID changes, while the doc says it prohibits it
On 07/31/2014 11:53, Ansgar Burchardt wrote: On 07/31/2014 11:42, intrig...@debian.org wrote: the attached unit file has NoNewPrivileges set to yes, which, according to systemd.exec(5), prohibits UID changes of any kind. However, the tor daemon it starts successfully manages to change its UID to debian-tor, as configured with User debian-tor in /usr/share/tor/tor-service-defaults-torrc: [...] Did I misunderstand the documentation, or is the doc wrong, or is there a bug somewhere? It works as intended, but the documentation might be a bit misleading. NoNewPrivileges only affects the exec syscall which will no longer grant any new privileges, including no longer switching uid for suid binaries. It does *not* take away the CAP_SETUID or any other capabilities the process already has. Oh, and one other thing that might be worth mentioning in this context: | Be careful, though: LSMs might also not tighten constraints on exec | in no_new_privs mode. (This means that setting up a general-purpose | service launcher to set no_new_privs before execing daemons may | interfere with LSM-based sandboxing.) +--[ Documentation/prctl/no_new_privs.txt ] I have no idea about LSMs, but I would expect this to only matter if you either rely on the kernel to setup the sandbox for the service (and do not use AppArmorProfile=) or if the service executes programs that should have even tigher restrictions. Both of which should not affect services like tor, but might be relevant for others. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756609: lilyterm: Changes dependency to libvte-2.90-9
Package: lilyterm Version: 0.9.9.4-1 Severity: normal Tags: upstream Dear Maintainer, Thank you for your job. I think that is better to change dependency on libvte9 to libvte-2.90-9 with newer version. Also, in package description missed Provides section, like as Provides: x -terminal-emulator. Best Regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-2-686-pae (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 lilyterm depends on: ii libc6 2.19-7 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-02.40.0-3 ii libgtk2.0-0 2.24.24-1 ii libpango-1.0-0 1.36.3-1 ii libvte9 1:0.28.2-5 ii libx11-62:1.6.2-2 lilyterm recommends no packages. lilyterm 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#756608: libneon27-gnutls: Memory leak when using TLS
Package: libneon27-gnutls
Version: 0.29.6-3
Severity: normal
Dear Maintainer,
when libneon27-gnutls is used to connect to a HTTPS-sever it leaks about 4 KB
of memeory every time the connection is closed.
This bug was discovered by a user of davfs2 which - when running for a long
time - finally allocated all of real memory and started swaping.
(http://savannah.nongnu.org/support/?108158)
The bug can be reproduced more easy using cadaver and valgrind, like
$ valgrind --trace-children=yes --leak-check=full --log-file=log-file
https-url
After connecting and issuing some commands at the cadaver-UI the log file will
show entries like this
==3660== 4,281 bytes in 1 blocks are definitely lost in loss record 65 of 69
==3660==at 0x40283EE: realloc (vg_replace_malloc.c:632)
==3660==by 0x42AAB0B: ??? (in /usr/lib/i386-linux-gnu/libgnutls.so.26.22.4)
==3660==by 0x42AB8D7: _gnutls_buffer_append_data_prefix (in
/usr/lib/i386-linux-gnu/libgnutls.so.26.22.4)
==3660==by 0x429BDFA: ??? (in /usr/lib/i386-linux-gnu/libgnutls.so.26.22.4)
==3660==by 0x429715F: gnutls_session_get_data2 (in
/usr/lib/i386-linux-gnu/libgnutls.so.26.22.4)
==3660==by 0x40BABD8: ne_sock_connect_ssl (ne_socket.c:1804)
==3660==by 0x40C5E25: ne__negotiate_ssl (ne_gnutls.c:933)
==3660==by 0x40B1D65: send_request.isra.6 (ne_request.c:1650)
==3660==by 0x40B2683: ne_begin_request (ne_request.c:1189)
==3660==by 0x40B1C04: ne_request_dispatch (ne_request.c:1400)
==3660==by 0x804D999: ??? (in /usr/bin/cadaver)
==3660==by 0x40E8E65: (below main) (libc-start.c:244)
The reason is that neon uses ne_free for memory allocated by gnutls instead of
gnutls_free. The bug was already reported upstream
(http://lists.manyfish.co.uk/pipermail/neon/2014-July/001570.html) but the
upstream maintainer did not yet respond.
This patch by Patrick Ohly fixes the problem:
src/ne_gnutls.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/ne_gnutls.c b/src/ne_gnutls.c
index 08d78cc..485b9de 100644
--- a/src/ne_gnutls.c
+++ b/src/ne_gnutls.c
@@ -694,7 +694,11 @@ void ne_ssl_context_destroy(ne_ssl_context *ctx)
{
gnutls_certificate_free_credentials(ctx-cred);
if (ctx-cache.client.data) {
+#if defined(HAVE_GNUTLS_SESSION_GET_DATA2)
+gnutls_free(ctx-cache.client.data);
+#else
ne_free(ctx-cache.client.data);
+#endif
} else if (ctx-cache.server.key.data) {
gnutls_free(ctx-cache.server.key.data);
gnutls_free(ctx-cache.server.data.data);
Cheers
Werner
-- System Information:
Debian Release: 7.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libneon27-gnutls depends on:
ii libc6 2.13-38+deb7u3
ii libcomerr21.42.5-1.1
ii libgnutls26 2.12.20-8+deb7u2
ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u1
ii libk5crypto3 1.10.1+dfsg-5+deb7u1
ii libkrb5-3 1.10.1+dfsg-5+deb7u1
ii libxml2 2.8.0+dfsg1-7+wheezy1
ii zlib1g1:1.2.7.dfsg-13
Versions of packages libneon27-gnutls recommends:
ii ca-certificates 20130119
libneon27-gnutls 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#756599: printf(3) manpage: stray asterisk in NAN*
Jakub, I do not know the details here, but are you sure this is wrong? The preceding part of the sentence says [and a string starting with nan for NaN, in the case of f conversion], and I take the * to mean a wildcard pattern match, analogous with [a string starting with nan for NaN]. This is just my guess though. Cheers, Michael On Thu, Jul 31, 2014 at 10:58 AM, Jakub Wilk jw...@debian.org wrote: Package: manpages-dev Version: 3.65-1 Severity: minor The printf(3) manpage reads: The C99 standard specifies [-]inf or [-]infinity for infinity, and a string starting with nan for NaN, in the case of f conversion, and [-]INF or [-]INFINITY or NAN* in the case of F conversion.) Please remove the stray asterisk after NAN. -- Jakub Wilk -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756604: systemd: NoNewPrivileges allows UID changes, while the doc says it prohibits it
Control: retitle -1 Misleading documentation about NoNewPrivileges and UID changes Control: tag -1 + upstream Hi, Ansgar Burchardt wrote (31 Jul 2014 09:53:21 GMT) : It works as intended, but the documentation might be a bit misleading. NoNewPrivileges only affects the exec syscall which will no longer grant any new privileges, including no longer switching uid for suid binaries. It does *not* take away the CAP_SETUID or any other capabilities the process already has. Thanks a lot! I'll report a bug upstream (possibly with a patch) wrt. the documentation being a bit misleading, then. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756604: systemd: NoNewPrivileges allows UID changes, while the doc says it prohibits it
Hi again, Ansgar Burchardt wrote (31 Jul 2014 10:04:52 GMT) : Oh, and one other thing that might be worth mentioning in this context: | Be careful, though: LSMs might also not tighten constraints on exec | in no_new_privs mode. (This means that setting up a general-purpose | service launcher to set no_new_privs before execing daemons may | interfere with LSM-based sandboxing.) +--[ Documentation/prctl/no_new_privs.txt ] I have no idea about LSMs, but I would expect this to only matter if you either rely on the kernel to setup the sandbox for the service (and do not use AppArmorProfile=) or if the service executes programs that should have even tigher restrictions. Both of which should not affect services like tor, but might be relevant for others. Indeed, this won't affect the tor service: my intention is to use AppArmorProfile= in its unit file as soon as systemd v210+ is available in Debian, to replicate how we're doing it in the initscript. I'll double-check once we're at this point, though. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756352: [Dms-maintainers] Bug#756352: dms-core: Uninstallable in sid, needs transitioning to PostgreSQL 9.4
Hi! Will get onto it this weekend, hopefully Saturday. Need to dump and update DB schema for PostgresQL 9.4 Will also fix version dependency in debian/control as specified below, but for postgresql-9.4. Please give me a few days. Quite busy with work. Regards, Matt Grant On Tue, 2014-07-29 at 06:46 +0200, Martin Pitt wrote: Package: dms-core Version: 1.0.1g-5 Severity: serious Hello, dms-core currently requires a specific major PostgreSQL version 9.3, but it has versioned depends on the metapackages: postgresql (= 9.3), postgresql ( 9.4), postgresql-client (= 9.3), postgresql-client ( 9.4), Please don't do that. If your package really needs a specific PostgreSQL version, then depend on postgresql-9.3 (-client is always a dependency of that). As a result dms is now uninstallable, as postgresql is version 9.4 now. Can you please check if it also works with the current 9.4, and fix the dependencies accordingly? Thank you in advance! Martin ___ Dms-maintainers mailing list dms-maintain...@lists.alioth.debian.org https://lists.alioth.debian.org/mailman/listinfo/dms-maintainers -- Matt Grant, Debian and Linux Systems Administration and Consulting Mobile: 021 0267 0578 Email: m...@mattgrant.net.nz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756599: printf(3) manpage: stray asterisk in NAN*
Hi Micheal, Thanks for the quick reply! * Michael Kerrisk mtk.manpa...@gmail.com, 2014-07-31, 12:16: I do not know the details here, but are you sure this is wrong? The preceding part of the sentence says [and a string starting with nan for NaN, in the case of f conversion], and I take the * to mean a wildcard pattern match, analogous with [a string starting with nan for NaN]. This is just my guess though. Oh, that makes sense. Somehow it didn't occur to me that the * character is not meant to be literal here. Could you make this character italic, to make it clear it is not literal? -- 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#756607: [Pkg-javascript-devel] Bug#756607: npm: Confusing error with binary node modules
Le jeudi 31 juillet 2014 à 11:30 +0200, Matthijs Kooijman a écrit : Package: npm Version: 1.4.21+ds-1 Severity: normal Dear maintainer, when installing the serialport package through npm, I get the following messages: matthijs@grubby:~$ npm install -g serialport /home/matthijs/.node_modules/bin/serialportterm - /home/matthijs/.node_modules/lib/node_modules/serialport/bin/serialportTerminal.js /home/matthijs/.node_modules/bin/serialportlist - /home/matthijs/.node_modules/lib/node_modules/serialport/bin/serialportList.js serialport@1.4.2 install /home/matthijs/.node_modules/lib/node_modules/serialport node-pre-gyp install --fallback-to-build sh: 1: node-pre-gyp: not found npm WARN This failure might be due to the use of legacy binary node npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian ... I haven't figured out what the actual problem is yet, but I want to point this message: npm WARN This failure might be due to the use of legacy binary node npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian However, the referenced README.Debian doesn't actually talk about anything related at all - nothing in there helps me solve this problem. README.Debian from the npm package doesn't help either. Perhaps this info was removed at some point? The info is about nodejs command at the end of /usr/share/doc/nodejs/README.Debian It is true it can be confusing. I'm open to suggestions. Jérémy. PS: Mind that this error pops up everytime. We didn't find a better way to tell it failed possibly because of nodejs rename, or not. Meaning the error you got might be for a totally different reason: here it seems you miss node-pre-gyp module. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756610: libxmltooling-java-doc: Short description does not sufficiently describe package function
Source: libxmltooling-java-doc Severity: minor The short description text does not help the user understand the function of the package. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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#756611: libxmltooling-java: Short description does not sufficiently describe package function
Source: libxmltooling-java Severity: minor The short description text does not help the user understand the function of the package. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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#609422: X11 forwarding for KDE applications crashes with 'Session bus not found'
Control: tag -1 + unreproducible Hi, I can't reproduce the issue with the current jessie version (4:4.13.1-1) and will tag it as fixed in the future if there is no addional information. Happy hacking, -- pi seconds is a nanocentury -- Tom Duff Saludos /\/\ /\ `/ signature.asc Description: Digital signature
Bug#756606: [Pkg-postgresql-public] Bug#756606: postgresql-9.1: Init-Script does not work together with heartbeat
Control: severity -1 wishlist Re: Marc Richter 2014-07-31 20140731094417.4564.80248.reportbug@pg1 Unfortunately, when stoping heartbeat on the standby node, heartbeat nevertheless tries to give up resources, even it hasn't acquired them before. Since /var/lib/postgresql wasn't mounted before on that node, issuing /etc/init.d/postgresql stop on the standby node fails, since it cannot find necessary files in /var/lib/postgresql . The init script was never designed to be a drop-in heartbeat HA agent. The exit codes are probably simply wrong in some cases for that. Any reason you aren't using the pgsql agent provided by pacemaker? http://clusterlabs.org/wiki/PgSQL_Replicated_Cluster Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756352: [Pkg-postgresql-public] [Dms-maintainers] Bug#756352: dms-core: Uninstallable in sid, needs transitioning to PostgreSQL 9.4
Re: Matt Grant 2014-07-31 1406801852.21473.7.ca...@moriah.internal.anathoth.net Hi! Will get onto it this weekend, hopefully Saturday. Need to dump and update DB schema for PostgresQL 9.4 Will also fix version dependency in debian/control as specified below, but for postgresql-9.4. Out of curiosity, what feature are you using that doesn't work with 9.3 and 9.4? Would using dbconfig-common solve these problems? Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756612: [kdeconnect] Problems Configuring, Connecting, Maintaining Usage
Package: kdeconnect Version: 0.7-1 Severity: normal --- Please enter the report below this line. --- 1. One must drop firewall for phone to see desktop. Will work with firewall afterwards but no clear how-to set this up. 2. Same-day in-out-in to WIFI will reconnect--good. Following day, PC and phone off meanwhile, unable to use at all, with or without firewall. 3. Multiple user-KDE logons may have disabled the app. Phone sees first user, others seem disabled, even with no pairage. 4. Not clear what to do with sshfs. Phone app kicked phone off until rebooted (not Debian problem, obviously). 5. No documentation. If the thing does get paired, how to get to functions besides batter charging and toast-notifications? -- Phone System information -- HW: LG P500, armv6 ROM: Android 4.4.3--Omni. --- System information. --- Architecture: amd64 Kernel: Linux 3.14-2-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ===-+-=== libqca2 (= 2.0.2) | 2.0.3-6 libqca2-plugin-gnupg| 2.0.0~beta3-2 libqca2-plugin-ossl | 2.0.0~beta3-2 kde-runtime ( 4:4.10) | 4:4.13.1-1 libc6 (= 2.14) | 2.19-7 libgcc1(= 1:4.1.1) | 1:4.9.1-3 libkcmutils4 (= 4:4.4.95) | 4:4.13.3-2 libkdecore5(= 4:4.7.1) | 4:4.13.3-2 libkdeui5 (= 4:4.7.0) | 4:4.13.3-2 libkfile4 (= 4:4.3.4) | 4:4.13.3-2 libkio5 (= 4:4.5.85) | 4:4.13.3-2 libqjson0(= 0.8.1) | 0.8.1-3 libqt4-dbus(= 4:4.5.3) | 4:4.8.6+git49-gbc62005+dfsg-1 libqt4-declarative (= 4:4.7.0~rc1) | 4:4.8.6+git49-gbc62005+dfsg-1 libqt4-network (= 4:4.7.0~beta1) | 4:4.8.6+git49-gbc62005+dfsg-1 libqt4-svg (= 4:4.5.3) | 4:4.8.6+git49-gbc62005+dfsg-1 libqt4-xml (= 4:4.5.3) | 4:4.8.6+git49-gbc62005+dfsg-1 libqtcore4 (= 4:4.8.0) | 4:4.8.6+git49-gbc62005+dfsg-1 libqtgui4 (= 4:4.8.0) | 4:4.8.6+git49-gbc62005+dfsg-1 libstdc++6 (= 4.4.0) | 4.9.1-3 libx11-6| 2:1.6.2-2 libxau6 | 1:1.0.8-1 libxdmcp6 | 1:1.1.1-1 libxext6| 2:1.3.2-1 libxtst6| 2:1.2.2-1 Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756599: printf(3) manpage: stray asterisk in NAN*
Could you make this character italic, to make it clear it is not literal? Without being sure of the details, I am reluctant to make any change. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756602: printf(3) manpage: please document that %n can't include flags, width or precision
tags 756602 fixed-upstream thanks Hello Jakub, I've applied the patch below. Cheers, Michael --- a/man3/printf.3 +++ b/man3/printf.3 @@ -332,9 +332,7 @@ For other conversions, the behavior is undefined. .B \- The converted value is to be left adjusted on the field boundary. (The default is right justification.) -Except for -.B n -conversions, the converted value is padded on the right with blanks, rather +The converted value is padded on the right with blanks, rather than on the left with blanks or zeros. A .B \- @@ -788,10 +786,17 @@ or .TP .B n The number of characters written so far is stored into the integer -indicated by the -.I int\ * -(or variant) pointer argument. +pointed to by the corresponding argument. +That argument shall be an +.I int\ *, +or variant, as specified by the +.B l +or +.B ll +length modifier. No argument is converted. +The behavior is undefined if the conversion specification includes +any flags, a field width, or a precision. .TP .B m (Glibc extension.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735595: Revised virtualbox-hwclock.service
FYI, it seems that there's no reason for RemainAfterExit=yes to be set in the service. So currently I'm using: [Unit] Description=Save system time to RTC before shutdown Documentation=https://www.virtualbox.org/ticket/11980 Before=final.target DefaultDependencies=no [Service] ExecStart=/sbin/hwclock --systohc Type=oneshot [Install] WantedBy=final.target -- Sam Morris https://robots.org.uk/ 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756352: [Pkg-postgresql-public] [Dms-maintainers] Bug#756352: dms-core: Uninstallable in sid, needs transitioning to PostgreSQL 9.4
Hi! The DMS package creates its own PostgresQL cluster to save a lot on creation steps required. It sets up for easy enabling of WAL replication over IPSEC, pg_hba.conf, etc that would otherwise have to be manually done, and can be quite fiddly. It uses its own postgresql.conf file etc. There is more to the DR pairing than just the DB. DNSSEC keys have to be rsynced, as well as master zones synced via DNS AXFR protocol. Matt Grant On Thu, 2014-07-31 at 12:37 +0200, Christoph Berg wrote: Re: Matt Grant 2014-07-31 1406801852.21473.7.ca...@moriah.internal.anathoth.net Hi! Will get onto it this weekend, hopefully Saturday. Need to dump and update DB schema for PostgresQL 9.4 Will also fix version dependency in debian/control as specified below, but for postgresql-9.4. Out of curiosity, what feature are you using that doesn't work with 9.3 and 9.4? Would using dbconfig-common solve these problems? Christoph -- Matt Grant, Debian and Linux Systems Administration and Consulting Mobile: 021 0267 0578 Email: m...@mattgrant.net.nz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756582: new syntax error when invoking udevadm test breaks installing/ upgrading
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: fuse Version: 2.9.3-14 Followup-For: Bug #756582 Please let me add some suggestions. - - It would have been easier to find the particular problem if the stderr would have not been redirected to /dev/null. Could you please remove the 21? - - It is good style to use long options in scripts. Maybe that would have circumvented the bug from begin. Especially in this case where there are no short options documented in udevadm man page. (Maybe that is also a minor bug in udev.) Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJT2h99AAoJEKZ8CrGAGfas0wEL/03cq2OZ1z9FTUPrILNoLyjW doF8wdTKz+eMVLCthku0ta2+8htWeFu1ul+pm/y2ug5gtY26tI3F9S1lIMf8SsSd Kbwt73Lar7VrHFrM2N0l/+lMWAL+lYd0GerZ27DOIlHgw7O03XxLb68ZgFXXDPfI zdpYdDhNKMuYkEdZw8LOncotwvWFbquzJyXQSymLpSguDXrRDigFlJW+TkHgHOWK FhwTGcJjfvYI6y1ucZP56lunHqkLZcV0SAK760Ob8N9hKmi5kVipmlrkmddPUbg3 RsrLYRld484LvH2C/4cNjOfrvzNKZA3doFTpuSB6GPx2Ss1yyYNOof958S30ZUjE sHuNdE5YpAgVJDo1vqvroFpGOZIfOrdCvp0feDrcmr15zz83wibe7wSZHBYJ24hB 7/wve5XFTLCxUuPfysw2ISYPl2gr9eo8jcEc25wzSRxUahNXh0nxT64k8fgoT98H nsRRoRMzGoSSnndNcZ5inZ9AicL++8H04oqSnx2nJg== =6v8a -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716904: konsole: ^D doesn't work after latest upgrade
Control: reassign 716904 rekonq 0.9.2-1 Hi, The default shortcut to add a bookmark in KDE is CTRL(B), but it seems that rekonq developers decided to change it here: https://bugs.kde.org/show_bug.cgi?id=303445 Causing this issue, rekonq is no longer in jessie, but the buggy code is still in wheezy, so I'm reassigning the bug. Happy hacking, -- The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offense. -- Edsger W. Dijkstra Saludos /\/\ /\ `/ signature.asc Description: Digital signature
Bug#734946: base-passwd: block from testing until all shell-fallout bugs are fixed
Hi, On Sat, 11 Jan 2014, Colin Watson wrote: As the maintainer of base-passwd, I'm filing this artificial RC bug to keep base-passwd = 3.5.30 out of testing until all the =normal bugs in http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=base-pas...@packages.debian.org;tag=shell-fallout are fixed in testing. I should really have done the search first, but this will minimise the effect on users. All the bugs are fixed except for cipux (#734725) where the damage is minor since it only affects documentation. Please go ahead and ensure this packages migrates to testing in time for jessie. Thank you! -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756617: ITP: ruby-jekyll-watch -- jekyll plugin for rebuild your site when file changes
Package: wnpp Owner: Youhei SASAKI uwab...@gfd-dennou.org Severity: wishlist * Package name: ruby-jekyll-watch Version : 1.0.0 Upstream Author : Parker Moore * URL or Web page : https://github.com/jekyll/jekyll-watch * License : MIT Description : jekyll plugin for rebuild your site when file changes --- Youhei SASAKI uwab...@gfd-dennou.org uwab...@debian.or.jp GPG fingerprint: 4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756346: debarchiver: [INTL:pt] Updated Portuguese translation of manpage
Thanks! Will be applied at next upload. / Ola Inguza Technology AB Sent from a phone Den 29 jul 2014 02:57 skrev Américo Monteiro a_monte...@gmx.com: Package: debarchiver Version: 0.10.1 Tags: l10n, patch Severity: wishlist Updated Portuguese translation for debarchiver's manpage. Translator: Américo Monteiro a_monte...@gmx.com Feel free to use it. For translation updates please contact 'Last Translator' or the Portuguese Translation Team traduz _at_ debianpt.org. -- Melhores cumprimentos/Best regards, Américo Monteiro
Bug#756618: texlive-base: upgrade fails trying to overwrite files from texlive-doc-base 2012.20120611-1
Package: texlive-base Version: 2014.20140717-01 Severity: serious Trying to upgrade a wheezy chroot to jessie resulted in this error: Preparing to unpack .../texlive-base_2014.20140717-01_all.deb ... De-configuring texlive-base (2012.20120611-5), to allow removal of texlive-common (2012.20120611-5) ... De-configuring texlive-doc-base (2012.20120611-1), to allow removal of texlive-common (2012.20120611-5) ... Unpacking texlive-base (2014.20140717-01) ... dpkg: error processing archive /var/cache/apt/archives/texlive-base_2014.20140717-01_all.deb (--unpack): trying to overwrite '/usr/share/texlive/doc.html', which is also in package texlive-doc-base 2012.20120611-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Please add the appropriate Replaces/Breaks to avoid those upgrade problems. Thank you. I attach a list of *tex* packages that are installed in that chroot in case you want to reproduce it. -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ ii dblatex 0.3.4-2 all Produces DVI, PostScript, PDF documents from DocBook sources ii gettext 0.18.1.1-9amd64 GNU Internationalization utilities ii gettext-base0.18.1.1-9amd64 GNU Internationalization utilities for the base system ii html2text 1.3.2a-15 amd64 advanced HTML to text converter ii jadetex 3.13-14 all generator of printable output from SGML or XML using Jade iU latex-beamer2014.20140717-01 all TeX Live: transitional dummy package iU latex-xcolor2014.20140717-01 all TeX Live: transitional dummy package ii libdjvulibre-text 3.5.25.3-1all Linguistic support files for libdjvulibre ii libgettextpo0:amd64 0.18.1.1-9amd64 GNU Internationalization library ii libhtml-formattext-withlinks-andtables-perl 0.02-1all Perl module to converts HTML to Text with tables intact ii libhtml-formattext-withlinks-perl 0.14-1all Perl module to convert HTML to text with links as footnotes ii liblocale-gettext-perl 1.05-8amd64 module using libc functions for internationalization in Perl ii liblocale-maketext-gettext-perl 1.28-1all Perl module bridging gettext and Maketext localization frameworks ii libptexenc1 2012.20120628-4 amd64 TeX Live: pTeX encoding library ii libtext-charwidth-perl 0.04-7+b2 amd64 get display widths of characters on the terminal ii libtext-csv-xs-perl 1.09-1amd64 Perl C/XS module to process Comma-Separated Value files ii libtext-glob-perl 0.09-1all Perl module for matching globbing patterns against text ii libtext-iconv-perl 1.7-5+b1 amd64 converts between character sets in Perl ii libtext-wrapi18n-perl 0.06-7all internationalized substitute of Text::Wrap iU luatex 2014.20140528.34243-5 all TeX Live: transitional dummy package ii preview-latex-style 11.86-11 all extraction of elements from LaTeX documents as graphics iU tex-common 5.02 all common infrastructure for building and installing TeX ii tex-gyre2.004.1-4 all scalable PostScript and OpenType fonts based on URW Fonts iU texlive 2014.20140717-01 all TeX Live: A decent selection of the TeX Live packages iF texlive-base2012.20120611-5 all TeX Live: Essential programs and files iU texlive-binaries2014.20140528.34243-5 amd64 Binaries for TeX Live ii texlive-doc-base2012.20120611-1 all TeX Live: TeX Live documentation iU texlive-extra-utils 2014.20140717-1 all TeX Live: TeX auxiliary programs iU texlive-font-utils 2014.20140717-1 all TeX Live: Graphics and font utilities iU texlive-fonts-recommended 2014.20140717-01 all TeX Live: Recommended fonts iU texlive-fonts-recommended-doc
Bug#756479: [Pkg-nagios-devel] Bug#756479: enable -enable-command-args again, please
On Thu, 31 Jul 2014, rausc...@buxtehude.debian.org wrote: Dear Maintainer, i know, that you compiled without -enable-command-args and you wrote in the NEWS.Debian file, that you disabled it because there are security problems and that this feature is often used wrong. Some people need this feature to manage monitoring parameters central. Your nrpe.cfg disables this feature by default (don't_blame_nrpe=0) and the features comment shows everyone, that enable it could be a security Problem. For my opinion, disable this feature by default should be enough. If someone need this feature, he must compile his own nrpe server version. Maybe he need to do it on hundreds of Machines and he has to do it again, if the Debian Packet is updated. I don't think that Compile nrpe without this feature is a real security advantage because if someone need it, he will compile with this support except of only enable this feature. I Agree with you, that this option could be a security risk, but it is possible to reduce the risk by setting allowed_hosts to restric who is able to communicate with nrpe. It would be nice if you would compile with -enable-command-args again. It would give more flexibility how to use nrpe and all people who use command args wouldn't need to manage their own version of this packet. No, sorry. I won't do this and the security agreed that this would be the most sane solution. But you are of course free to take over maintenance of nrpe. Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755248: [RFR] templates://icinga2/{icinga2-classicui.templates,icinga2-ido-mysql.templates,icinga2-ido-pgsql.templates}
Christian PERRIER wrote: --- icinga2.old/debian/icinga2-ido-mysql.templates2014-07-19 08:23:13.433644396 +0200 +++ icinga2/debian/icinga2-ido-mysql.templates2014-07-31 07:12:59.745329265 +0200 @@ -1,9 +1,9 @@ Template: icinga2-ido-mysql/enable Type: boolean Default: true +_Description: Enable Icinga 2 mysql idoutils? + If you choose this option, the ido mysql + feature will be enabled in Icinga 2. . + You may later disable the feature by using the + icinga2-disable-feature ido-mysql command. First, s/mysql/MySQL/ and s/idoutils/IDOUtils/. The feature is *named* ido-mysql, but calling it the ido mysql feature (or even worse, the ido pgsql feature) doesn't work very well - for a start, if there are various ido-*sql features and this is the MySQL one, I would expect it to be referred to as the MySQL IDO feature, not the other way around. As far as I can work out, the question here is really just Use MySQL (to store data in)?; outputting data to databases is done via a special cryptically named Icinga Data Output module, but why mention that here? The question could be: _Description: Enable Icinga 2's ido-mysql feature? Please specify whether Icinga 2 should use MySQL. Then the control file: [...] Package: icinga2 [...] Description: host and network monitoring system Icinga 2 is a general-purpose monitoring application and the next generation after Icinga 1.x - which was a Nagios fork. It should fit the needs of a small environment as well as big installations. Rewritten from scratch in C++, with multi-threading and cluster support. What's a small environment? Can it handle middle-sized set-ups? Second paragraph no verb. It seems fairly obvious that Icinga 2 follows on from Icinga 1.x... perhaps it would make more sense to incorporate the rewritten part into the bit about being a new generation: Icinga 2 is a general-purpose monitoring application to fit the needs of any size of network. Icinga 1.x was a Nagios fork; this new generation has been rewritten from scratch in C++, with multi-threading and cluster support. . Features: * All common features of Icinga and Nagios What, only the features common to both? That sounds like a logic puzzle. Try standard features. * Much faster and more scalable than Icinga 1 and Nagios (I hope you're planning to come back and correct that if Nagios v3 turns out to be even more scalable than Icinga 2.) * New configuration format, more intuitive and template based Slightly awkward (more template based?) - how about: * new, more intuitive, template-based configuration format; * Monitoring several services by executing checks (see nagios-plugins*) for example ICMP/ping, SMTP, POP3, HTTP, NNTP, or other TCP port * Underpunctuated. * I don't see what the several is doing here. * How does ping fit in here? * Are those TCP services in any particular order? * Why does the list skip UDP? Oh, well, other versions of this list elsewhere also seem to skip UDP, so maybe it's significant. Perhaps it should be * monitoring services on ICMP (ping) or TCP ports (HTTP, NNTP, POP3, SMTP, etc.) by executing checks (see nagios-plugins*); * Any small script can be used as a check plugin, when following the Nagios plugin API * any small script following the Nagios plugin API can be used as a check plugin; * Notifications about alerts with any custom script, or shipped examples I don't understand this line. Perhaps it's trying to say: * notifications about alerts for any custom script (with examples); You don't need to say that they're shipped; if they weren't in the Debian package, you wouldn't be entitled to mention them here anyway. * Native support for Livestatus and Graphite (And since I've edited most of them I'll also reformat the whole list into d-l-e house style, with semicolons.) . This is the metapackage to install all Icinga 2 features. Package: icinga2-common [...] Package: icinga2-bin [...] Package: icinga2-doc [...] These just need the same boilerplate changes. Package: icinga2-classicui [...] Description: host and network monitoring system - classic ui integration s/ui/UI/, and why does it need the word integration? [...] This package provides the integration into Icinga Classic UI. The integration of what into Icinga Classic UI? This package provides support for the Icinga Classic User Interface. Package: icinga2-ido-mysql [...] Description: host and network monitoring system - IDO for MySQL Is there any reason not to say something like this? Description: host and network monitoring system - MySQL support The word IDO is still in the packagename and the long description. [...] Package: icinga2-ido-pgsql [...] Description: host and network monitoring system - IDO for PostgreSQL Likewise. [...] Package: icinga2-dbg Just the boilerplate changes. ObWhyTheName: why was NetSaint
Bug#756614: apt: missing method driver prevents package authentication
Package: apt Version: 1.0.6 This is what happens when you have a repository that makes HTTP-HTTPS redirection in your sources.lists, and you didn't have apt-transport-https installed: # apt-get update E: The method driver /usr/lib/apt/methods/https could not be found. N: Is the package apt-transport-https installed? It didn't tell me which repository causes the problem, but oh well... Let's try to install apt-transport-https: # apt-get install apt-transport-https Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: apt-transport-https (1.0.6) 0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded. Need to get 0 B/132 kB of archives. After this operation, 221 kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! apt-transport-https Install these packages without verification? [y/N] E: Some packages could not be authenticated This is rather user-unfriendly. Why does a problem with one repository cause authentication warnings for an unrelated repository? -- /etc/apt/sources.list -- deb http://ftp.debian.org/debian/ unstable main contrib non-free deb http://people.debian.org/~seanius/php/etch/ ./ -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages apt depends on: ii debian-archive-keyring 2012.4 ii gnupg 1.4.18-2 ii libapt-pkg4.12 1.0.6 ii libc6 2.19-7 ii libgcc1 1:4.9.1-3 ii libstdc++6 4.9.1-3 -- 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#756615: ITP: ruby-jekyll-paginate -- Default pagination generator for Jekyll
Package: wnpp Owner: Youhei SASAKI uwab...@gfd-dennou.org Severity: wishlist * Package name: ruby-jekyll-paginate Version : 1.0.0 Upstream Author : Parker Moore * URL or Web page : https://github.com/jekyll/jekyll-paginate * License : MIT Description : Default pagination generator for Jekyll --- Youhei SASAKI uwab...@gfd-dennou.org uwab...@debian.or.jp GPG fingerprint: 4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756613: ITP: ruby-jekyll-gist -- Liquid tag for displaying Github Gists in Jekyll sites
Package: wnpp Owner: Youhei SASAKI uwab...@gfd-dennou.org Severity: wishlist * Package name: ruby-jekyll-gist Version : 1.1.0 Upstream Author : Parker Moore * URL or Web page : https://github.com/jekyll/jekyll-gist * License : MIT Description : Liquid tag for displaying Github Gists in Jekyll sites --- Youhei SASAKI uwab...@gfd-dennou.org uwab...@debian.or.jp GPG fingerprint: 4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625888: konsole: Mouse focus problem: auto-switch to menu-list every 30 seconds.
Control: tag -1 + unreproducible moreinfo Hi, I can't reproduce this issue with the current konsole versions, and will close the issue in the future if no additional information is add. Is this somehow related to [1]? [1]: https://bugs.kde.org/show_bug.cgi?id=95692 Happy hacking, -- Elegance is not a dispensable luxury but a quality that decides between success and failure. -- Edsger W. Dijkstra Saludos /\/\ /\ `/ signature.asc Description: Digital signature
Bug#756616: activate zswap support in kernel 3.16
Package: linux-headers-3.16-rc6-amd64 Version: 3.16~rc6-1~exp1 Severity: wishlist Rightnow the kernel is not build with CONFIG_ZSWAP, which is a method to compress RAM pages instead of swapping straight. Please add support for it, as to enable it anyway the boot parameter zswap.enabled=1 would be needed and thus the default configuration is not affected. By now Ubuntu is having support for it. Regards, Kai -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750261: ada-reference-manual: FTBFS: Texinfo errors
Package: src:ada-reference-manual Followup-For: Bug #750261 Control: tags -1 + unreproducible Control: severity -1 important As archive-wide rebuilds do not seem to be able to reproduce the failure either, I consider that the severity is only important. http://aws-logs.debian.net/ftbfs-logs/2014/06/28 http://aws-logs.debian.net/ftbfs-logs/2014/07/18 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756619: apt-get update: SIGBUS when run out of disk space
Package: apt Version: 1.0.6 apt-get update dies with SIGBUS when there's very little free space on disk: # rm -f /var/cache/apt/*.* # df -h /var Filesystem Size Used Avail Use% Mounted on /dev/disk/by-uuid/0fbbe877-619a-4769-9583-1f6ca4084685 2.0G 1.9G 25M 99% / # apt-get update Hit http://ftp.debian.org unstable InRelease Hit http://ftp.debian.org unstable/main amd64 Packages/DiffIndex Bus error (core dumped). 60% GDB backtrace: #0 0x77ace7be in pkgCacheGenerator::NewDepends (this=0x7fffe100, Pkg=..., Ver=..., Version=16019563, Op=@0x7fffced4: 2, Type=@0x7fffcfa0: 1, OldDepLast=@0x7fffd5c8: 0x0) at /build/apt-S02Gn6/apt-1.0.6/apt-pkg/pkgcachegen.cc:939 #1 0x77ace6cf in pkgCacheGenerator::NewDepends (this=0x7fffe100, Pkg=..., Ver=..., Version=..., Op=@0x7fffced4: 2, Type=@0x7fffcfa0: 1, OldDepLast=@0x7fffd5c8: 0x0) at /build/apt-S02Gn6/apt-1.0.6/apt-pkg/pkgcachegen.cc:921 #2 0x77acec5f in pkgCacheGenerator::ListParser::NewDepends (this=0x7fffd5a0, Ver=..., PackageName=..., Arch=..., Version=..., Op=2, Type=1) at /build/apt-S02Gn6/apt-1.0.6/apt-pkg/pkgcachegen.cc:1003 #3 0x77b37655 in debListParser::ParseDepends (this=0x7fffd5a0, Ver=..., Tag=0x77b83793 Depends, Type=1) at /build/apt-S02Gn6/apt-1.0.6/apt-pkg/deb/deblistparser.cc:771 #4 0x77b34c30 in debListParser::NewVersion (this=0x7fffd5a0, Ver=...) at /build/apt-S02Gn6/apt-1.0.6/apt-pkg/deb/deblistparser.cc:166 #5 0x77acbf2a in pkgCacheGenerator::MergeListVersion (this=0x7fffe100, List=..., Pkg=..., Version=..., OutVer=@0x7fffd2d8: 0x0) at /build/apt-S02Gn6/apt-1.0.6/apt-pkg/pkgcachegen.cc:410 #6 0x77acae50 in pkgCacheGenerator::MergeList (this=0x7fffe100, List=..., OutVer=0x0) at /build/apt-S02Gn6/apt-1.0.6/apt-pkg/pkgcachegen.cc:245 #7 0x77b2d2dc in debPackagesIndex::Merge (this=0x645b60, Gen=..., Prog=0x7fffe320) at /build/apt-S02Gn6/apt-1.0.6/apt-pkg/deb/debindexfile.cc:338 #8 0x77ad01d3 in BuildCache (Gen=..., Progress=0x7fffe320, CurrentSize=@0x7fffe080: 34150740, TotalSize=34351968, Start=..., End=...) at /build/apt-S02Gn6/apt-1.0.6/apt-pkg/pkgcachegen.cc:1302 #9 0x77ad1546 in pkgCacheGenerator::MakeStatusCache (List=..., Progress=0x7fffe320, OutMap=0x7fffe480, AllowMem=false) at /build/apt-S02Gn6/apt-1.0.6/apt-pkg/pkgcachegen.cc:1494 #10 0x77a9ba1c in pkgCacheFile::BuildCaches (this=0x7fffe470, Progress=0x7fffe320, WithLock=true) at /build/apt-S02Gn6/apt-1.0.6/apt-pkg/cachefile.cc:90 #11 0x7779c4b1 in CacheFile::BuildCaches (this=0x7fffe470, WithLock=true) at ../build/include/apt-private/private-cachefile.h:27 #12 0x7779c119 in DoUpdate (CmdL=...) at /build/apt-S02Gn6/apt-1.0.6/apt-private/private-update.cc:74 #13 0x77b7743e in CommandLine::DispatchArg (this=0x7fffea60, Map=0x7fffea80, NoMatch=true) at /build/apt-S02Gn6/apt-1.0.6/apt-pkg/contrib/cmndline.cc:380 #14 0x004221c2 in main (argc=2, argv=0x7fffecb8) at /build/apt-S02Gn6/apt-1.0.6/cmdline/apt-get.cc:1738 -- /etc/apt/sources.list -- deb http://ftp.debian.org/debian/ unstable main -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages apt depends on: ii debian-archive-keyring 2012.4 ii gnupg 1.4.18-2 ii libapt-pkg4.12 1.0.6 ii libc6 2.19-7 ii libgcc1 1:4.9.1-3 ii libstdc++6 4.9.1-3 -- 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#756621: [redis-server] systemd service running as root
Package: redis-server
Version: 2:2.8.13-1
Severity: normal
Tags: patch
--- Please enter the report below this line. ---
Dear Maintainer
The systemd service for the redis-server package does not set the
user/group parameters and is therefore started as root.
The attached patch makes the systemd service behave the same way as
the sysv init script.
Additionally permissions on existing files are fixed in the postinst
script.
Kind regards,
Philipp
--- System information. ---
Architecture: amd64
Kernel: Linux 3.14-1-amd64
Debian Release: jessie/sid
500 unstableftp.ch.debian.org
1 experimentalftp.ch.debian.org
--- Package information. ---
Depends (Version) | Installed
==-+-===
init-system-helpers (= 1.18~) | 1.20
libc6(= 2.14) | 2.19-7
libjemalloc1(= 2.1.1) | 3.6.0-2
redis-tools (= 2:2.8.13-1) | 2:2.8.13-1
adduser| 3.113+nmu3
Package's Recommends field is empty.
Package's Suggests field is empty.
diff -uNr orig/redis-server.postinst debian/redis-server.postinst
--- orig/redis-server.postinst 2014-07-31 13:51:46.612965384 +0200
+++ debian/redis-server.postinst 2014-07-31 13:51:59.673209418 +0200
@@ -17,7 +17,7 @@
for DIR in /var/lib/redis /var/log/redis
do
mkdir -p ${DIR}
- chown ${USER}:${GROUP} ${DIR}
+ chown -R ${USER}:${GROUP} ${DIR}
done
;;
diff -uNr orig/redis-server.service debian/redis-server.service
--- orig/redis-server.service 2014-07-31 13:48:28.865255072 +0200
+++ debian/redis-server.service 2014-07-31 13:48:49.909651316 +0200
@@ -7,6 +7,8 @@
ExecStart=/usr/bin/redis-server /etc/redis/redis.conf
ExecStop=/usr/bin/redis-cli shutdown
Restart=always
+User=redis
+Group=redis
[Install]
WantedBy=multi-user.target
Bug#756618: texlive-base: upgrade fails trying to overwrite files from texlive-doc-base 2012.20120611-1
tags 756618 + pending thanks Hi Raphael. dpkg: error processing archive /var/cache/apt/archives/texlive-base_2014.20140717-01_all.deb (--unpack): trying to overwrite '/usr/share/texlive/doc.html', which is also in package texlive-doc-base 2012.20120611-1 Hmm, this is strange. I regularly make update tests from stable, testing, und unstable before uploading. I don't know why this was not caught. I guess the reason is that I am only testing upgrades of texlive-full and texlive, not each and every package by itself. Thanks, added to the configuration file/git repo. Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756620: new upstream (9.4.6)
Package: open-vm-tools Severity: wishlist it would be nice if you could upgrade to the current upstream release (9.4.6). -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753575: texlive-bin: FTBFS on s390x, test suite errors
Hi Matthias, On Sat, 26 Jul 2014, Matthias Klose wrote: can you attach the xz compressed preprocessed file? Is this the only one to build an executable / test case? if not, could you attach the remaining files too? What do you with preprocessed? * web2c preprocessing * gcc (header replacement, #...) preprocessing? Unfortunately several files and libraries are necessary to build the binary, it is the full pdftex binary which is complex. Thus, remaining files, do I need to add all of the libraries neneded for building? Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756622: fusioninventory-agent runs spuriously update /etc/blkid.tab
Package: fusioninventory-agent
Version: 2.2.3-2~bpo60+2
Severity: serious
Justification: Policy 10.7
Whene running fusioninventory-agent it calls /sbin/blkid if installed, which
cause an update of /etc/blkid.tab
(maybe this bug should filed against package containing blkid ?)
As part of fusioninventory-agent blkid could be called with a specific cache
file.
Besides writing file in /etc which should have configuration files, it triggers
false-positives for /etc watching tools (we are using metche)
triomph:/tmp# ls -al /etc/blkid.tab
-rw-r--r-- 1 root root 357 Jul 31 13:44 /etc/blkid.tab
triomph:/tmp# date
Thu Jul 31 13:58:01 CEST 2014
triomph:/tmp# fusioninventory-agent
[info] task WakeOnLan is not enabled
triomph:/tmp#
triomph:/tmp# ls -al /etc/blkid.tab
-rw-r--r-- 1 root root 357 Jul 31 13:58 /etc/blkid.tab
Excerpt from
/usr/share/fusioninventory/lib/FusionInventory/Agent/Task/Inventory/Input/Linux/Drives.pm
if (canRun('blkid')) {
# use blkid if available, as it is filesystem-independant
foreach my $filesystem (@filesystems) {
$filesystem-{SERIAL} = getFirstMatch(
logger = $logger,
command = blkid $filesystem-{VOLUMN},
pattern = qr/\sUUID=(\S*)\s/
);
}
-- System Information:
Debian Release: 6.0.10
APT prefers oldstable
APT policy: (990, 'oldstable'), (500, 'squeeze-lts'), (500,
'oldstable-updates')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-0.bpo.1-amd64 (SMP w/24 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 fusioninventory-agent depends on:
ii hdparm 9.32-1tune hard disk parameters for high
ii libfile-which-perl 1.08-1Perl module for searching paths fo
ii libjson-perl 2.21-1Perl module to parse and convert t
ii libnet-ip-perl 1.25-2Perl extension for manipulating IP
ii libnet-ssleay-perl 1.36-1Perl module for Secure Sockets Lay
ii libproc-daemon-perl0.03-2Run Perl program as a daemon proce
ii libproc-pid-file-perl 1.27-1Perl module for managing process i
ii libtext-template-perl 1.45-1Text::Template perl module
ii libuniversal-require-p 0.13-1Load modules from a variable
ii libwww-perl5.836-1 Perl HTTP/WWW client/server librar
ii libxml-treepp-perl 0.39-1XML::TreePP -- Pure Perl implement
ii libyaml-perl 0.71-1YAML Ain't Markup Language
ii pciutils 1:3.1.7-6 Linux PCI Utilities
ii perl 5.10.1-17squeeze6 Larry Wall's Practical Extraction
ii ucf3.0025+nmu1 Update Configuration File: preserv
fusioninventory-agent recommends no packages.
Versions of packages fusioninventory-agent suggests:
pn read-edid none (no description available)
pn smartmontools none (no description available)
-- Configuration Files:
/etc/fusioninventory/agent.cfg changed [not included]
-- debconf-show failed
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756623: override: db5.1-util:database/optional libdb5.1:libs/optional
Package: ftp.debian.org Severity: normal Please reduce the priority of libdb5.1 and db5.1-util to optional. They should no longer be part of standard given that we switched to db5.3. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756610: libxmltooling-java-doc: Short description does not sufficiently describe package function
Source: libxmltooling-java-doc
Followup-For: Bug #756610
Please find a patch attached.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/control b/debian/control
index 3deb382..ef0dcc5 100644
--- a/debian/control
+++ b/debian/control
@@ -27,7 +27,7 @@ Section: doc
Depends: ${misc:Depends}, ${maven:DocDepends}
Recommends: ${maven:DocOptionalDepends}
Suggests: libxmltooling-java
-Description: Documentation for XMLTooling-J
+Description: Documentation for libxmltooling-java
XMLTooling-J is a low-level library that may be used to construct libraries
that allow developers to work with XML in a Java beans manner.
.
