Bug#760003: transition: qt-gstreamer
The one thing I'm a bit concerned about for the transition is that as we modified qt-gstreamer to also build new Qt5 binary packages, I think it's going to spend some time in NEW. That's ok, binary NEW is fairly quick (and we have friends in the right places if it turns out not). qt-gstreamer 1.2.0-2 is uploaded and is in NEW now http://lists.alioth.debian.org/pipermail/pkg-kde-extras/2015-May/022845.html Diane Trout -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783996: RM: python-byteplay -- RoQA; dead upstream, orphaned, RC-buggy
Package: ftp.debian.org python-byteplay is dead upstream (last release in 2010), orphaned (for almost 2 years) and RC buggy (for over a year). Please remove it from the archive. -- 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#783804: redmine: postinstall error on installing via apt-get
Control: tag -1 + moreinfo Hello, On Thu, Apr 30, 2015 at 12:42:30PM +0200, Thimo Seitz wrote: Package: redmine Version: 3.0~20140825-5 Severity: important Hello, I've tried to install the package with apt-get using command apt-get install redmine redmine-mysql. While runnning the configure-step an error occured. My debian is upgraded from wheezy to jessie. Redmine wasn't installed before the upgrade. output of apt-get: dbconfig-common: writing config to /etc/dbconfig-common/redmine/instances/default.conf Creating config file /etc/redmine/default/database.yml.new with new version granting access to database redmine_default for redmine_default@localhost: success. verifying access for redmine_default@localhost: success. creating database redmine_default: success. verifying database redmine_default exists: success. dbconfig-common: flushing administrative password rake aborted! Psych::SyntaxError: (unknown): did not find expected node content while parsing a block node at line 7 column 13 (See full trace by running task with --trace) dpkg: Fehler beim Bearbeiten des Paketes redmine (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Can you uncomment the `set -x` at the top of /var/lib/dpkg/info/redmine.postinst, try again, and post the output? -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#764401: Are you planning to take over mksh in Debian?
On Fri, May 1, 2015 at 5:36 PM, Thorsten Glaser t...@mirbsd.de wrote: Kenneth Pronovici dixit: I'll file a Debian bug to document the improvements I asked for, just Please DO NOT file Debian bugs for upstream issues in mksh, only for packaging issues. This has been at the top of README.Debian for ages. Thorsten, I'm not trying to be snarky here, but I'm a little lost. This package is orphaned. If you're no longer the package maintainer, why should it even matter to you whether upstream issues are tracked as Debian bugs? I filed the bug so nothing would get lost while the package is orphaned, which seems like a reasonable thing to do. The next maintainer might very well have a different policy for Debian bugs than you did. I would if it were my package. Besides that, this is arguably a functional regression vs. older versions of pdksh in Debian, which mksh now provides. I think it's useful to have the change in behavior noted, even if it is only a wishlist. KEN -- Kenneth J. Pronovici prono...@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#780563: Error running timer `show-paren-function': (wrong-type-argument number-or-marker-p nil)
On Mon, 16 Mar 2015, +11:50:18 EET (UTC +0200), Rob Browning r...@defaultvalue.org pressed some keys: Juhapekka Tolvanen juht...@iki.fi writes: Package: emacs24 Version: 24.4+1-4.1 Severity: important I get this stupid error message all the time to my minibuffer: Error running timer `show-paren-function': (wrong-type-argument number-or-marker-p nil) Does it happen if you run emacs with -Q? If not, then the problem is likely due to an additional packaage you have installed, or something in your ~/.emacs, and you should be able to track it down by selectively disabling things until you find the culprit. Problem was in a package called vimpulse.el , that was downloaded and installed by hand and not via ELPA. Maybe later version works better, but I decided to deinstall it completely and to disable VIPER, because I do not user vi-mode very much. I mean vimpulse.el needs VIPER in order to work -- Juhapekka naula Tolvanen * http colon slash slash iki dot fi slash juhtolv Quidquid Latine dictum sit altum videtur. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784000: fglrx-driver: 32bit opengl does not work
Package: fglrx-driver Version: 1:14.12-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I update to this driver, based on the AMD hype about it. The 32bit opengl does not work under wine, but opengl does work in a 64bit prefix. The 32bit packages are loaded , I have no idea why it doesnt work. This is on t a testing or Jessie install with this driver being the only thing not from the jessie repo *** End of the template - remove these template lines *** -- Package-specific info: Full fglrx package list: ii fglrx-atievent 1:14.12-1amd64events daemon for the non-free AT ii fglrx-control 1:14.12-1amd64control panel for the non-free AT ii fglrx-driver 1:14.12-1amd64non-free ATI/AMD RadeonHD display ii fglrx-modules- 1:14.12-1amd64dkms module source for the non-fr ii fglrx-source 1:14.12-1amd64kernel module source for the non- ii libfglrx:amd64 1:14.12-1amd64non-free ATI/AMD RadeonHD display ii libfglrx:i386 1:14.12-1i386 non-free ATI/AMD RadeonHD display ii libfglrx-amdxv 1:14.12-1amd64AMD XvBA (X-Video Bitstream Accel ii libfglrx-amdxv 1:14.12-1i386 AMD XvBA (X-Video Bitstream Accel ii libgl1-fglrx-g 1:14.12-1amd64proprietary libGL for the non-fre ii libgl1-fglrx-g 1:14.12-1i386 proprietary libGL for the non-fre ii libgl1-fglrx-g 1:14.12-1i386 ATI/AMD binary OpenGL 32-bit libr VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0344] 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, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 85 Region 0: Memory at c000 (64-bit, prefetchable) [size=256M] Region 2: Memory at fea2 (64-bit, non-prefetchable) [size=128K] Region 4: I/O ports at e000 [size=256] Expansion ROM at fea0 [disabled] [size=128K] Capabilities: access denied Kernel driver in use: fglrx_pci DRM and fglrx Informations from dmesg: [0.00] AGP: No AGP bridge found [0.00] AGP: Checking aperture... [0.00] AGP: No AGP bridge found [0.00] AGP: Node 0: aperture [bus addr 0x-0x01ff] (32MB) [0.00] AGP: Your BIOS doesn't leave a aperture memory hole [0.00] AGP: Please enable the IOMMU option in the BIOS setup [0.00] AGP: This costs you 64MB of RAM [0.00] AGP: Mapping aperture over RAM [mem 0xb000-0xb3ff] (65536KB) [1.152595] PCI-DMA: Disabling AGP. [1.152652] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture [1.179164] Linux agpgart interface v0.103 [ 22.334644] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel. [ 22.369258] 6[fglrx] Maximum main memory to use for locked dma buffers: 7675 MBytes. [ 22.369587] 6[fglrx] vendor: 1002 device: 68b8 revision: 0 count: 1 [ 22.370168] 6[fglrx] ioport: bar 4, base 0xe000, size: 0x100 [ 22.370667] 6[fglrx] Kernel PAT support is enabled [ 22.370682] 6[fglrx] module loaded - fglrx 14.50.2 [Nov 20 2014] with 1 minors [ 36.417722] fglrx_pci :01:00.0: irq 85 for MSI/MSI-X [ 36.418559] 6[fglrx] Firegl kernel thread PID: 1164 [ 36.418627] 6[fglrx] Firegl kernel thread PID: 1165 [ 36.418694] 6[fglrx] Firegl kernel thread PID: 1166 [ 36.418787] 6[fglrx] IRQ 85 Enabled [ 36.430574] 6[fglrx] Reserved FB block: Shared offset:0, size:100 [ 36.430576] 6[fglrx] Reserved FB block: Unshared offset:f7b4000, size:4000 [ 36.430578] 6[fglrx] Reserved FB block: Unshared offset:f7b8000, size:548000 [ 36.430579] 6[fglrx] Reserved FB block: Unshared offset:3fff3000, size:d000 Xorg X server configuration file status: -rw-r--r-- 1 root root 684 Apr 29 12:30 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Section ServerLayout Identifier aticonfig Layout Screen 0 aticonfig-Screen[0]-0 0 0 EndSection Section Module EndSection Section Monitor Identifier aticonfig-Monitor[0]-0 Option VendorName ATI Proprietary Driver Option ModelName Generic Autodetecting Monitor Option DPMS true EndSection Section Device Identifier aticonfig-Device[0]-0 Driver fglrx BusID PCI:1:0:0 EndSection Section Screen Identifier aticonfig-Screen[0]-0 Device aticonfig-Device[0]-0 Monitoraticonfig-Monitor[0]-0 DefaultDepth 24 SubSection Display Viewport 0 0
Bug#783692: systemd: systemctl output is unreadable on light background
On Apr 29, Juergen Stuber juer...@jstuber.net wrote: I use a light gray background, so green becomes completely unreadable. I checked the attached image and I can read it well on a business matte LCD. Maybe the settings for your screen should be tuned? Are your eyesight and colors perception OK? -- ciao, Marco pgpLSXlRllUJB.pgp Description: PGP signature
Bug#783040: gerbview: unprintable outputs
On Fri, May 01, 2015 at 09:20:40PM +0200, Nick Østergaard wrote: 2015-05-01 20:43 GMT+02:00 Adam Majer ad...@zombino.com: retitle 783040 gerbview: unprintable outputs thanks On Fri, May 01, 2015 at 08:11:38PM +0200, Nick Østergaard wrote: Gerbv is _not_ part of KiCad. Gerbview is part of KiCad. In any case you should be more explicit about what the error of the output is, and give a test case to help the developers and packagers. gerbv produces buggy and unprintable PDF and PS and SVG files. gerbview has correct output and prints correctly. Sorry, I got this completely backwards. gerbv works. Gerbview print does not work. I've attached simple kicad project along with PDF and PS output from gerbview - those even crash evince and produce no output. The correct output from gerbv is also in the tarball, for comparison. Sorry about the confusion. Right package, wrong name! I don't see anything attached. But in the case of KiCad, around bzr rev 4022, which this is reported against is very old. It is probably not worth investing time to debug this, you should try the latest from the product branch. attached now. -- Adam Majer ad...@zombino.com test.tar.xz Description: application/xz
Bug#784006: caja: Option to show real filename of .desktop-files instead of title
Package: caja Version: 1.8.2-3 Severity: wishlist .desktop files are currently shown with the image and the title stated in the file. There seems no way to change this behavior and show the real file name. Although that might have been seen as a user-friendly feature when it was implemented it actually bothers more experienced users (you can find numerous threads with google about this). And it even poses a security threat since one can simple mask a potential hazardous command as something else. There is no way for a user to see that this is just a .desktop file that will be executed when clicked. So for example I could send you an image (assuming you're not an experienced user; maybe within a zip file that you'll extract via context menu). You don't even have to set executable rights afterwards. Clicking the file might then just delete all your personal stuff or do something worse (like uploading something via wget). It's exactly the same thing that went wrong with MS Windows except that you could force Windows Explorer to show the real file name including the extension. So using Caja is even more risky then Explorer now. So please add an option to set this behavior. Regarding the security threat I maybe should've declared this as a serious bug instead of a wishlist item. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages caja depends on: ii caja-common 1.8.2-3 ii desktop-file-utils0.22-1 ii gvfs 1.22.2-1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-18 ii libcairo2 1.14.0-2.1 ii libcaja-extension11.8.2-3 ii libexempi32.2.1-2 ii libexif12 0.6.21-2 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-4 ii libgail18 2.24.25-3 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libglib2.0-data 2.42.1-1 ii libgtk2.0-0 2.24.25-3 ii libice6 2:1.0.9-1+b1 ii libmate-desktop-2-17 1.8.1+dfsg1-3 ii libpango-1.0-01.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libselinux1 2.3-2 ii libsm62:1.2.2-1+b1 ii libstartup-notification0 0.12-4 ii libunique-1.0-0 1.1.6-5 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxml2 2.9.1+dfsg1-5 ii libxrender1 1:0.9.8-1+b1 ii mate-desktop 1.8.1+dfsg1-3 ii shared-mime-info 1.3-1 Versions of packages caja recommends: ii gvfs-backends 1.22.2-1 Versions of packages caja suggests: ii engrampa 1.8.1+dfsg1-1 pn gstreamer0.10-tools none pn meld 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#776185: tiff: CVE-2014-8127 CVE-2014-8128 CVE-2014-8129 CVE-2014-8130
Here's a summary of all the separate bugs which for some reason got
grouped together into only 4 CVE IDs. I'm also attaching all the
samples that were provided to reproduce these (which are tiny).
N.B. that although all these bugs were reported against specific tools,
most bugs are in libtiff itself. This means tiff3 in wheezy is still
affected!
I tested all these in squeeze-lts while preparing an update there and
included the results below.
The giant Fix various crasher bugs on fuzzed images change addresses
parts of CVE-2014-{8127,8128,8129} and CVE-2014-9330, but only the part
addressing the last issue has been applied in sid. I expect the wheezy
and jessie updates were similar but didn't check.
Ben.
CVE-2014-8127
- thumbnail: http://bugzilla.maptools.org/show_bug.cgi?id=2484
- repro: thumbnail 01_thumbnail.tiff out.tiff
- squeeze: no segv, errors detected by valgrind
- fix: 2014-12-21 Even Rouault even.roua...@spatialys.com
* tools/pal2rgb.c, tools/thumbnail.c: fix crash by disabling
TIFFTAG_INKNAMES
copying. The right fix would be to properly copy it, but not worth the
burden
for those esoteric utilities.
http://bugzilla.maptools.org/show_bug.cgi?id=2484 (CVE-2014-8127)
- patch: CVE-2014-8127.patch
- fix result:
- squeeze: still has an invalid read but appears to be harmless
- tiff2bw: http://bugzilla.maptools.org/show_bug.cgi?id=2485
- repro: tiff2bw 04_tiff2bw.tiff out.tiff
- squeeze: no segv, no error detected by valgrind
- fix: 2014-12-21 Even Rouault even.roua...@spatialys.com
* tools/tiff2bw.c: when Photometric=RGB, the utility only works if
SamplesPerPixel = 3. Enforce that
http://bugzilla.maptools.org/show_bug.cgi?id=2485 (CVE-2014-8127)
- patch: tools-tiff2bw.c-when-photometric-rgb-the-utility-onl.patch
- fix result:
- squeeze: no regression
- tiff2rgba: http://bugzilla.maptools.org/show_bug.cgi?id=2486
- repro: tiff2rgba 09_tiff2rgba.tiff out.tiff
- squeeze: no segv, errors detected by valgrind
- fix: 2014-12-21 Even Rouault even.roua...@spatialys.com
Fix various crasher bugs on fuzzed images.
* libtiff/tif_dir.c: TIFFSetField(): refuse to set negative values for
TIFFTAG_XRESOLUTION and TIFFTAG_YRESOLUTION that cause asserts when writing
the directory
* libtiff/tif_dirread.c: TIFFReadDirectory(): refuse to read ColorMap or
TransferFunction if BitsPerSample has not yet been read, otherwise reading
it later will cause user code to crash if BitsPerSample 1
* libtiff/tif_getimage.c: TIFFRGBAImageOK(): return FALSE if LOGLUV with
SamplesPerPixel != 3, or if CIELAB with SamplesPerPixel != 3 or
BitsPerSample != 8
* libtiff/tif_next.c: in the run mode, use tilewidth for tiled images
instead of imagewidth to avoid crash
* tools/bmp2tiff.c: fix crash due to int overflow related to input BMP
dimensions
* tools/tiff2pdf.c: fix crash due to invalid tile count (should likely be
checked by
libtiff too). Detect invalid settings of BitsPerSample/SamplesPerPixel for
CIELAB / ITULAB
* tools/tiffcrop.c: fix crash due to invalid TileWidth/TileHeight
* tools/tiffdump.c: fix crash due to overflow of entry count.
- patch: fix-various-crasher-bugs-on-fuzzed-images.patch
- fix result:
- squeeze: fixed
- tiff2ps tiffdither: http://bugzilla.maptools.org/show_bug.cgi?id=2496
- repro: tiff2ps -O out.ps 08_tiff2ps.tiff
- squeeze: no segv, no error detected by valgrind
- repro: tiffdither 12_tiffdither.tiff out.tiff
- squeeze: no segv, no error detected by valgrind
- fix: 2014-12-23 Even Rouault even.roua...@spatialys.com
* libtiff/tif_read.c: fix several invalid comparisons of a uint64 value with
= 0 by casting it to int64 first. This solves crashing bug on corrupted
images generated by afl.
- patch: libtiff-tif_read.c-fix-several-invalid-comparisons-o.patch
- squeeze: This is not applicable without other changes to use 64-bit
bytecount
- tiffmedian: http://bugzilla.maptools.org/show_bug.cgi?id=2497
- repro: tiffmedian 16_tiffmedian.tiff out.tiff
- squeeze: no segv, no error detected by valgrind
- fix: 2014-12-23 Even Rouault even.roua...@spatialys.com
* libtiff/tif_read.c: fix several invalid comparisons of a uint64 value with
= 0 by casting it to int64 first. This solves crashing bug on corrupted
images generated by afl.
- patch: libtiff-tif_read.c-fix-several-invalid-comparisons-o.patch
- squeeze: This is not applicable without other changes to use 64-bit
bytecount
- tiffset: http://bugzilla.maptools.org/show_bug.cgi?id=2500
- repro: cp 19_tiffset.tiff out.tiff tiffset out.tiff
- squeeze: segv
CVE-2014-8128
- [0] thumbnail: http://bugzilla.maptools.org/show_bug.cgi?id=2489
- repro: thumbnail 03_thumbnail.tiff out.tiff
- squeeze: no segv, no error detected by valgrind
- fix: 2014-12-21 Even Rouault even.roua...@spatialys.com
* tools/thumbnail.c: fix out-of-buffer write
Bug#643733: [Reportbug-maint] Bug#643733: sponsorship-requests and reportbug
On Sat, Aug 18, 2012 at 11:49 AM, Michael Gilbert mgilb...@debian.org wrote: On Sat, Aug 18, 2012 at 10:23 AM, Sandro Tosi wrote: Do you think there are many things to fix? Do you have an ETA for when you'll be able to give the patch a revamp? It shouldn't take much. No eta. I just don't have any freetime at all right now...finishing my dissertation. ping -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783993: ruby-six: port test suite to RSpec3
Package: ruby-six
Severity: minor
Tags: patch
User: pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: rspec3
Dear maintainer,
This package uses the RSpec framework for the tests. RSpec v2 currently in
unstable will soon be replaced by the v3, already present in experimental.
Many deprecated features in RSpec2 are now errors in RSpec3 and the test suite
as is will fail with RSpec3. Please find attached a patch to adapt the test
suite to RSpec3. Feel free to update it and forward it upstream.
Best wishes,
For the Debian Ruby team,
Cédric
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- a/spec/six_rules_packs_spec.rb
+++ b/spec/six_rules_packs_spec.rb
@@ -9,7 +9,7 @@
let(:rules) { BookRules.new }
describe do
- it { (abilities rules).should be_true }
+ it { (abilities rules).should be_truthy }
it { lambda { abilities nil }.should raise_error(Six::InvalidPackPassed) }
it_should_behave_like :valid_abilities do
@@ -21,12 +21,12 @@
end
describe :add do
- it { abilities.add(:global, rules).should be_true }
- it { abilities.add(:wrong, nil).should be_false }
+ it { abilities.add(:global, rules).should be_truthy }
+ it { abilities.add(:wrong, nil).should be_falsey }
end
describe :add! do
- it { abilities.add!(:global, rules).should be_true }
+ it { abilities.add!(:global, rules).should be_truthy }
it { lambda { abilities.add!(:wrong, nil)}.should raise_error(Six::InvalidPackPassed) }
end
@@ -45,7 +45,7 @@
end
it should return false when trying to use unexisting pack do
- abilities.use(:noname).should be_false
+ abilities.use(:noname).should be_falsey
end
end
@@ -75,12 +75,12 @@
before { abilities.add(:global, rules) }
describe :remove do
-it { abilities.remove(:global).should be_true }
-it { abilities.remove(:zzz).should be_false }
+it { abilities.remove(:global).should be_truthy }
+it { abilities.remove(:zzz).should be_falsey }
end
describe :remove! do
-it { abilities.remove!(:global).should be_true }
+it { abilities.remove!(:global).should be_truthy }
it { lambda { abilities.remove!(:zzz)}.should raise_error(Six::NoPackError) }
end
end
@@ -94,16 +94,16 @@
Object.new
end
- it { abilities.valid_rules_object?(BookRules.new).should be_true }
- it { abilities.valid_rules_object?(invalid_with_allowed).should be_false }
- it { abilities.valid_rules_object?(invalid_wo_allowed).should be_false }
+ it { abilities.valid_rules_object?(BookRules.new).should be_truthy }
+ it { abilities.valid_rules_object?(invalid_with_allowed).should be_falsey }
+ it { abilities.valid_rules_object?(invalid_wo_allowed).should be_falsey }
end
describe :pack_exist? do
before { abilities.add(:global, rules) }
- it { abilities.pack_exist?(:global).should be_true }
- it { abilities.pack_exist?(:ufo).should be_false }
+ it { abilities.pack_exist?(:global).should be_truthy }
+ it { abilities.pack_exist?(:ufo).should be_falsey }
end
end
end
--- a/spec/support/valid_abilities_example.rb
+++ b/spec/support/valid_abilities_example.rb
@@ -19,38 +19,38 @@
describe should return true or false depend on access do
context :read_book do
-it { allowed?(@jim, :read_book, @jims_book).should be_true }
-it { allowed?(@mike, :read_book, @mikes_book).should be_true }
-it { allowed?(@jim, :read_book, @mikes_book).should be_true }
-it { allowed?(@mike, :read_book, @jims_book).should be_true }
+it { allowed?(@jim, :read_book, @jims_book).should be_truthy }
+it { allowed?(@mike, :read_book, @mikes_book).should be_truthy }
+it { allowed?(@jim, :read_book, @mikes_book).should be_truthy }
+it { allowed?(@mike, :read_book, @jims_book).should be_truthy }
end
context :rate_book do
-it { allowed?(@jim, :rate_book, @jims_book).should be_false }
-it { allowed?(@mike, :rate_book, @mikes_book).should be_false }
-it { allowed?(@jim, :rate_book, @mikes_book).should be_true }
-it { allowed?(@mike, :rate_book, @jims_book).should be_true }
+it { allowed?(@jim, :rate_book, @jims_book).should be_falsey }
+it { allowed?(@mike, :rate_book, @mikes_book).should be_falsey }
+it { allowed?(@jim, :rate_book, @mikes_book).should be_truthy }
+it { allowed?(@mike, :rate_book, @jims_book).should be_truthy }
Bug#783982: D-i: preseed from floppy no longer works !
You said I think you are looking for providing a preseed file, hence my advice https://www.google.nl/search?q=virtualbox+host+http+server+for+guests; 1. You're correct in that I'm looking to provide preseed file. But host-side HTTP server won't work for my needs, unless VirtualBox has it integrated. My technology is aimed at people, who require *zero* configuration, and should work across all hosts. Like click, click, click... Basically I need very minimal (and portable) host-side logic (and move as much complexity into the guest as possible). You said: Do an attended install. Verify that reading from floppy is possible. That is important. It proofs that the Virtualbox host provides a floppy disk controller and that the Vbox guest has a kernel kernel for the f.d.c. Also it shows there is /dev/fd0 (IIRC) 2. Well... you'r right ! /dev/fd0 is the problem ! Yes, I ensured, that VM has floppy controller configured, plus floppy.img inserted. Debian 8 (mini-)kernel (inside amd64-DVD) does NOT see /dev/fd0 ! (part of debian-installer); This works just fine with Debian 6 and 7 ! Post-install Debian 8 kernel _does_ see /dev/fd0, can loop-mount and can read files from it. (after installing from Debian 8 amd64-DVD), so no problem here. The natural question: Are those kernels different ? (I always assumed it is the *same* kernel) It seems the mini-kernel does not provide me with /proc/config.gz, so I have no clue what's included and what's excluded. How can I check ? Thanks for finding the problem ! -Alexey -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783720: clamav-daemon does not honour Local* with systemd
Hi Sebastian, On 01.05.2015 23:11, Sebastian Andrzej Siewior wrote: On 2015-04-29 23:03:49 [+0200], Andreas Cadhalpun wrote: The options LocalSocket /var/run/clamav/clamd.ctl.change LocalSocketGroup nobody LocalSocketMode 600 same options I just pushed a fix for this. It seems to work as intended, but additional testing would be nice. ;) now I see in /etc/systemd/system/clamav-daemon.socket.d/extend.conf: [Socket] ListenStream= SocketUser=clamav ListenStream=/var/run/clamav/clamd.ctl.change SocketGroup=nobody SocketMode=600 That's exactly what should be there. and ls gives me: ls -lah /var/run/clamav/ total 0 drwxr-xr-x 2 clamav clamav 80 May 1 22:59 . drwxr-xr-x 16 root root 560 May 1 21:28 .. srw-rw-rw- 1 clamav clamav 0 May 1 21:28 clamd.ctl srw--- 1 root root 0 May 1 22:59 clamd.ctl.change which means the user group is wrong. That's caused by the socket not being stopped before changing. Running 'systemctl stop clamav-daemon.socket' followed by 'systemctl start clamav-daemon.socket' makes it work. I just pushed a commit disabling the clamav-daemon.socket in prerm. This makes above work without manual intervention and also avoids the stale socket file. The debian/clamav-daemon.postinst.in file adds ListenStream twice, so the first (empty) one may leave. After that change I still don't see systemd setting the permissions properly. Any ideas? The first, empty ListenStream is intended: It tells systemd to ignore the one provided by the main socket unit in /lib/systemd/system. Otherwise it would open two sockets. However while testing this, I noticed another issue: The clamav-daemon.socket is not stopped during 'dpkg-reconfigure clamav-daemon'. Thus after changing the name of the socket, a stale socket file is left behind. I'm not sure if that's really a problem worth fixing though. Thoughts? Leaving stale sockets isn't nice I guess. But it won't happen often I guess. stop - change socket file - start would fix it and a reload due to new options would be done anyway. Would that be a way to fix it? That's how it's fixed now. ;) Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783995: [feature-request] Please allow to view kernel config via /proc/config.gz in all Debian kernels
Why would it be good for this to be exposed inside a container? So that applications know, if they can use advanced features such as AppArmor or not. And to give more complete environment for the admins. Plus, to debug problems inside debian-installer. (it lacks /boot/config), like bug # 783982, where normal Debian 8 kernel supports floppy /dev/fd0, but d-I kernel doesn't. Why it can't be changed in stable releases? I mean if the change is small and beneficial, why not ? (Assuming it doesn't require major kernel source code changes, but only kernel config)
Bug#784005: postgresql-9.4: Cluster upgrade from 9.1 to 9.4 results in broken configuration
Source: postgresql-9.4 Version: 9.4.1-1 Severity: important I upgraded a server (a LXC-based container) from Wheezy to Jessie. After installing, everything looked OK, with the (live) 9.1 and (empty) 9.4 clusters running. Now, following the instructions at /usr/share/doc/postgresql-common/README.Debian.gz (section Default clusters and upgrading) led to a seemingly correct cluster migration — Just at the final step, at the cluster restart time, I got: 2015-05-02 01:27:01 GMT FATAL: could not open shared memory segment /PostgreSQL.1804289383: Function not implemented Increasing the log verbosity to DEBUG5 yielded: 2015-05-02 01:57:55 GMT DEBUG: postgres: PostmasterMain: initial environment dump: 2015-05-02 01:57:55 GMT DEBUG: - 2015-05-02 01:57:55 GMT DEBUG: PG_GRANDPARENT_PID=2343 2015-05-02 01:57:55 GMT DEBUG: PGLOCALEDIR=/usr/share/locale 2015-05-02 01:57:55 GMT DEBUG: PGSYSCONFDIR=/etc/postgresql-common 2015-05-02 01:57:55 GMT DEBUG: LANG=en_US.UTF-8 2015-05-02 01:57:55 GMT DEBUG: PWD=/var/lib/postgresql 2015-05-02 01:57:55 GMT DEBUG: PGDATA=/var/lib/postgresql/9.4/main 2015-05-02 01:57:55 GMT DEBUG: LC_COLLATE=en_US.UTF-8 2015-05-02 01:57:55 GMT DEBUG: LC_CTYPE=en_US.UTF-8 2015-05-02 01:57:55 GMT DEBUG: LC_MESSAGES=en_US.UTF-8 2015-05-02 01:57:55 GMT DEBUG: LC_MONETARY=C 2015-05-02 01:57:55 GMT DEBUG: LC_NUMERIC=C 2015-05-02 01:57:55 GMT DEBUG: LC_TIME=C 2015-05-02 01:57:55 GMT DEBUG: - 2015-05-02 01:57:56 GMT DEBUG: invoking IpcMemoryCreate(size=23822336) 2015-05-02 01:57:56 GMT DEBUG: mmap with MAP_HUGETLB failed, huge pages disabled: Cannot allocate memory 2015-05-02 01:57:56 GMT DEBUG: SlruScanDirectory invoking callback on pg_notify/ 2015-05-02 01:57:56 GMT DEBUG: removing file pg_notify/ 2015-05-02 01:57:56 GMT DEBUG: dynamic shared memory system will support 288 segments 2015-05-02 01:57:56 GMT FATAL: could not open shared memory segment /PostgreSQL.1804289383: Function not implemented 2015-05-02 01:57:56 GMT DEBUG: shmem_exit(1): 0 before_shmem_exit callbacks to make 2015-05-02 01:57:56 GMT DEBUG: shmem_exit(1): 3 on_shmem_exit callbacks to make 2015-05-02 01:57:56 GMT DEBUG: proc_exit(1): 2 callbacks to make 2015-05-02 01:57:56 GMT DEBUG: exit(1) 2015-05-02 01:57:56 GMT DEBUG: shmem_exit(-1): 0 before_shmem_exit callbacks to make 2015-05-02 01:57:56 GMT DEBUG: shmem_exit(-1): 0 on_shmem_exit callbacks to make 2015-05-02 01:57:56 GMT DEBUG: proc_exit(-1): 0 callbacks to make Now, looking through the Web, this page gave me the needed insight: http://postgresql.nabble.com/Shared-memory-changes-in-9-4-td5804919.html The problem apparently happened because pg_upgradecluster uses my 9.1 config for 9.4, which does not include a part of the configuration. And following on the quoted webpage, I had to specify: dynamic_shared_memory_type = sysv As posix semantics seem not to work under LXC (or not under its default configuration). Thanks! -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-eudyptula5d12e3524822-00194-gd799964 (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 Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782814: transition: libvncserver
Hi, I tested against lcd4linux and vlc. I already sent mails to all rdepends, but only got an answer from lcd4linux maintainer. At least the build succeeded with the new version of libvncserver (from experimental) on sid/amd64. On 04/30/2015 08:57 PM, Jonathan Wiltshire wrote: On 2015-04-18 10:38, Peter Spiess-Knafl wrote: I know we are currently in freeze. This transition is requested for post- release of jessie. Upstream broke ABI compatibility for the latest libvncserver releases. They have already been informed to keep an eye on that in the future [1]. Therefore a transition of this library package is required. This could fit in soon. Have you done any test rebuilds of dependent packages? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764401: Are you planning to take over mksh in Debian?
Kenneth Pronovici dixit: I'll file a Debian bug to document the improvements I asked for, just Please DO NOT file Debian bugs for upstream issues in mksh, only for packaging issues. This has been at the top of README.Debian for ages. Debian bugs requesting functionality changes are likely to get closed quicky, as they are no bugs. Feature requests upstream (via #!/bin/mksh on Freenode IRC, via miros-mksh@, or, if it must be, via Launchpad) are OK. Thanks. bye, //mirabilos -- Using Lynx is like wearing a really good pair of shades: cuts out the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL. -- Henry Nelson, March 1999 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784001: courier-imap-ssl: does not start at boot time - systemctl reports missing .pid.lock file
Package: courier-imap-ssl Version: 4.15-1.6 Severity: important Dear Maintainer, On upgrading my system to jessie, courier-imap-ssl no longer starts at boot time. systemctl-l status courier-imap-ssl.service reports thus: ● courier-imap-ssl.service - LSB: Courier IMAP-SSL server Loaded: loaded (/etc/init.d/courier-imap-ssl) Active: failed (Result: exit-code) since Sat 2015-05-02 00:23:56 BST; 9min ago May 02 00:23:50 topdeck courier-imap-ssl[2639]: Starting Courier IMAP-SSL server: imapd-ssl/var/run/courier/imapd-ssl.pid.lock: No such file or directory May 02 00:23:50 topdeck courier-imap-ssl[2639]: ll_daemon_start: Resource temporarily unavailable May 02 00:23:56 topdeck systemd[1]: courier-imap-ssl.service: control process exited, code=exited status=1 May 02 00:23:56 topdeck systemd[1]: Failed to start LSB: Courier IMAP-SSL server. May 02 00:23:56 topdeck systemd[1]: Unit courier-imap-ssl.service entered failed state. Creating the imapd-ssl.pid file (with, say, touch) allows courier-imap-ssl to be started, but does not survive a reboot. courier-imap, very similar, is unaffected. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages courier-imap-ssl depends on: ii courier-imap 4.15-1.6 ii courier-ssl 0.73.1-1.6 ii debconf 1.5.56 ii openssl 1.0.1k-3 courier-imap-ssl recommends no packages. Versions of packages courier-imap-ssl suggests: ii claws-mail [imap-client] 3.11.1-3 pn courier-doc none ii evolution [imap-client] 3.12.9~git20141130.241663-1+b1 ii mutt [imap-client]1.5.23-3 -- Configuration Files: /etc/courier/imapd-ssl changed: SSLPORT=(ipv4-address).993,127.0.0.1.993,(ipv6-address).993,::1.993 SSLADDRESS=0 SSLPIDFILE=/var/run/courier/imapd-ssl.pid SSLLOGGEROPTS=-name=imapd-ssl IMAPDSSLSTART=YES IMAPDSTARTTLS=YES IMAP_TLS_REQUIRED=0 COURIERTLS=/usr/bin/couriertls TLS_KX_LIST=ALL TLS_COMPRESSION=ALL TLS_CERTS=X509 TLS_CERTFILE=/etc/ssl/private/tvc.pem TLS_TRUSTCERTS=/etc/ssl/certs TLS_VERIFYPEER=NONE TLS_CACHEFILE=/var/lib/courier/couriersslcache TLS_CACHESIZE=524288 MAILDIRPATH=Maildir /etc/courier/imapd.cnf [Errno 13] Permission denied: u'/etc/courier/imapd.cnf' /etc/logcheck/ignore.d.server/courier-imap-ssl [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.server/courier-imap-ssl' /etc/logcheck/violations.ignore.d/courier-imap-ssl [Errno 13] Permission denied: u'/etc/logcheck/violations.ignore.d/courier-imap-ssl' -- 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#784003: anjuta: gdb launch fails. complains about has_separator
Package: anjuta Version: 2:3.14.0-1 Severity: normal hello friends, when activating Run|Debug Program, an error message is displayed: Unable to load user interface file: Invalid property: GtkDialog.has_separator on line 1775 the said file is: /usr/share/anjuta/glade/anjuta-debug-manager.ui -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (300, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages anjuta depends on: ii anjuta-common 2:3.14.0-1 ii libanjuta-3-0 2:3.14.0-1 ii libapr1 1.5.1-3 ii libc6 2.19-18 ii libdevhelp-3-2 3.14.0-1 ii libgcc1 1:4.9.2-10 ii libgda-5.0-45.2.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgdl-3-5 3.14.0-2 ii libgladeui-2-6 3.18.3-1 ii libglib2.0-02.42.1-1 ii libgtk-3-0 3.14.5-1 ii libgtksourceview-3.0-1 3.14.1-1 ii libpango-1.0-0 1.36.8-3 ii libpython2.72.7.9-2 ii libstdc++6 4.9.2-10 ii libsvn1 1.8.10-6 ii libvala-0.26-0 0.26.1-1.1 ii libvte-2.91-0 0.38.1-2 ii libwebkit2gtk-3.0-252.4.8-2 ii libxml2 2.9.1+dfsg1-5 Versions of packages anjuta recommends: ii autoconf2.69-8 ii autogen 1:5.18.4-3 ii automake1:1.14.1-4 ii g++ 4:4.9.2-2 ii gcc 4:4.9.2-2 ii gdb 7.7.1+dfsg-5 ii intltool0.50.2-2 ii liblocale-gettext-perl 1.05-8+b1 ii libtool 2.4.2-1.11 ii make4.0-8.1 pn valac none ii yelp3.14.1-1 Versions of packages anjuta suggests: ii gjs 1.42.0-1 ii glade 3.18.3-1 ii libgtk-3-dev3.14.5-1 ii libgtkmm-3.0-dev3.14.0-1 ii python-distutils-extra 2.38-1 pn python-rope 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#784009: Segmentation fault
Package: wget Version: 1.16.3-2 Severity: grave $ wget Segmentation fault -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783994: [freespace2-launcher-wxlauncher] if the recommended package freespace2 is not installed the wxlauncher segfault
Package: freespace2-launcher-wxlauncher Version: 0.9.4-2 Severity: critical --- Please enter the report below this line. --- i installed the launcher freespace2-launcher-wxlauncher but not the recommended package freespace2 because i wanted to use the latest binary version online from the FS2 website. The wxlauncher segfault if the freespace2 package is not installed so make it a dependencies instead of recommended or fix wxlauncher to not segfault if he cannot find what is missing at the start. --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: 8.0 610 stable-updates ftp.it.debian.org 610 stable security.debian.org 610 stable ftp.it.debian.org 610 jessie-backports httpredir.debian.org 600 stable www.deb-multimedia.org 500 stable dl.google.com --- Package information. --- Package's Depends field is empty. 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#783997: ruby-redcloth: port test suite to RSpec3
Package: ruby-redcloth
Version: 4.2.9-4
Severity: minor
Tags: patch
User: pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: rspec3
Dear maintainer,
This package uses the RSpec framework for the tests. RSpec v2 currently in
unstable will soon be replaced by the v3, already present in experimental.
Many deprecated features in RSpec2 are now errors in RSpec3 and the test suite
as is will fail with RSpec3. Please find attached a patch to adapt the test
suite to RSpec3. Feel free to update it and forward it upstream.
Best wishes,
For the Debian Ruby team,
Cédric
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ruby-redcloth depends on:
ii libc6 2.19-18
ii libgmp102:6.0.0+dfsg-6
ii libruby2.1 2.1.5-3
ii ruby1:2.1.5
ruby-redcloth recommends no packages.
ruby-redcloth suggests no packages.
-- no debconf information
--- a/spec/parser_spec.rb
+++ b/spec/parser_spec.rb
@@ -6,13 +6,13 @@
it should accept options do
lambda {
RedCloth.new(test, [:hard_breaks])
- }.should_not raise_error(ArgumentError)
+ }.should_not raise_error
end
end
it should have a VERSION do
-RedCloth.const_defined?(VERSION).should be_true
-RedCloth::VERSION.const_defined?(STRING).should be_true
+RedCloth.const_defined?(VERSION).should be_truthy
+RedCloth::VERSION.const_defined?(STRING).should be_truthy
end
it should show the version as a string do
@@ -21,7 +21,7 @@
end
it should have EXTENSION_LANGUAGE do
-RedCloth.const_defined?(EXTENSION_LANGUAGE).should be_true
+RedCloth.const_defined?(EXTENSION_LANGUAGE).should be_truthy
RedCloth::EXTENSION_LANGUAGE.should_not be_empty
RedCloth::DESCRIPTION.should include(RedCloth::EXTENSION_LANGUAGE)
end
signature.asc
Description: Digital signature
Bug#784008: dconf-editor: Show full path of current selected entry
Package: dconf-editor Version: 0.22.0-1 Severity: wishlist dconf-editor should show the full path of the current entry somewhere. For example using a status bar at the bottom or some simple text label at the top (right below the menu). Or as an extra field below the name-value-editor where the other key infos are shown. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dconf-editor depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii libatk1.0-0 2.14.0-1 ii libc62.19-18 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libdconf10.22.0-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libxml2 2.9.1+dfsg1-5 dconf-editor recommends no packages. dconf-editor 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#784002: terminology: Bitmap fonts not rendering
Package: terminology Version: 0.7.0-1 Severity: important Bitmap fonts are not rendering on the Jessie release of Terminology, but do so correctly with standard fonts. It seems that the fonts revert back to monospace (my current system default font) and each character has a whitespace between them. I am running Terminology in an LXDE environment. -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages terminology depends on: ii libc6 2.19-18 ii libecore-con1 1.8.6-2.1+b2 ii libecore-evas11.8.6-2.1+b2 ii libecore-file11.8.6-2.1+b2 ii libecore-imf1 1.8.6-2.1+b2 ii libecore-input1 1.8.6-2.1+b2 ii libecore-ipc1 1.8.6-2.1+b2 ii libecore1 1.8.6-2.1+b2 ii libedje1 1.8.6-2.1+b2 ii libeet1 1.8.6-2.1+b2 ii libefreet-bin 1.8.6-2.1+b2 ii libefreet1a 1.8.6-2.1+b2 ii libeina1 1.8.6-2.1+b2 ii libeio1 1.8.6-2.1+b2 ii libelementary21.8.5-2 ii libemotion1 1.8.6-2.1+b2 ii libethumb-client-bin 1.8.6-2.1+b2 ii libethumb-client1 1.8.6-2.1+b2 ii libevas1 1.8.6-2.1+b2 ii libevas1-engines-x1.8.6-2.1+b2 ii liblz4-1 0.0~r122-2 ii terminology-data 0.7.0-1 terminology recommends no packages. Versions of packages terminology suggests: pn libelementary-bin 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#784007: dconf-editor: Add reset function for entire dirs and entries
Package: dconf-editor Version: 0.22.0-1 Severity: wishlist A function to delete/reset entire dirs should be implemented. Like the command line function: dconf reset -f /path/to/dir/ The whole dir and its entries should be deleted. Right clicking on a dir could open a context menu with that function. Because of its severity there should be a dialog for confirming that action (including a warning). ESC would be a good shortcut key. A context menu for deleting key-value-pairs should also be provided (also a shortcut would be helpful). -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dconf-editor depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii libatk1.0-0 2.14.0-1 ii libc62.19-18 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libdconf10.22.0-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libxml2 2.9.1+dfsg1-5 dconf-editor recommends no packages. dconf-editor 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#783347: Any ETA on when the backport will come to jessie ?
On Thu, Apr 30, 2015 at 07:46:52PM +0100, Rodrigo Campos wrote: But is there any ETA on when the changes will come to jessie ? Can I help you with testing ? Also, I can review the backports if you still need peer review :) I'm about to release it. I emailled security team and they didn't say no, but it wasn't exactly clear I was ok to proceed. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783998: duplicated lines in debian/gcc-BV-doc.doc-base.itm
Source: gcc-4.9 Severity: normal Hello, The same content appeared twice in debian/gcc-BV-doc.doc-base.itm http://anonscm.debian.org/viewvc/gcccvs/branches/sid/gcc-4.9/debian/gcc-BV-doc.doc-base.itm?view=markup Yixuan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769406: same problem with virsh / virt-install / serial console / grub2
I'm having the exact same problem. Installing a VM with virt-install installs a debian VM on my jessie host. HOST (Deb Jessie Fresh Install) - VM (Debian Jessie Fresh Install) You're not able to use virsh console vmname because ttyS0 serial console is not in default/grub. One has to add GRUB_CMDLINE_LINUX_DEFAULT=console=ttyS0,115200n8 explicitly by oneself, otherwise you wont get a serial console spawn and cant access the virtual machine from kvm using virsh. Please fix this asap, thanks. -- Florian Strankowski Core Solutions Adolph Schönfelder Straße 68 22083 Hamburg, Germany web https://coresec.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784006: caja: Option to show real filename of .desktop-files instead of title
Package: caja Version: 1.8.2-3 Followup-For: Bug #784006 Right click - Properties doesn't show the file name either. Just the title attribute and path. This should be changed too. The only way to get around this mess is to use the console. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages caja depends on: ii caja-common 1.8.2-3 ii desktop-file-utils0.22-1 ii gvfs 1.22.2-1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-18 ii libcairo2 1.14.0-2.1 ii libcaja-extension11.8.2-3 ii libexempi32.2.1-2 ii libexif12 0.6.21-2 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-4 ii libgail18 2.24.25-3 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libglib2.0-data 2.42.1-1 ii libgtk2.0-0 2.24.25-3 ii libice6 2:1.0.9-1+b1 ii libmate-desktop-2-17 1.8.1+dfsg1-3 ii libpango-1.0-01.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libselinux1 2.3-2 ii libsm62:1.2.2-1+b1 ii libstartup-notification0 0.12-4 ii libunique-1.0-0 1.1.6-5 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxml2 2.9.1+dfsg1-5 ii libxrender1 1:0.9.8-1+b1 ii mate-desktop 1.8.1+dfsg1-3 ii shared-mime-info 1.3-1 Versions of packages caja recommends: ii gvfs-backends 1.22.2-1 Versions of packages caja suggests: ii engrampa 1.8.1+dfsg1-1 pn gstreamer0.10-tools none pn meld 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#783995: [feature-request] Please allow to view kernel config via /proc/config.gz in all Debian kernels
Package: linux-image-amd64 Version: 3.16.7-ckt7-1 Hi, It would help me very much, if Debian kernel provided a quick ability to see it's own configuration in /proc/config.gz. Reason: in some cases viewing current kernel configuration via # /boot/config-$(uname -r) is not available; For example when working with Debian-installer (booting from DVD), or working inside an OpenVZ (or LXC) container. For those reasons I ask you to enable /proc/config.gz in all supported Debian kernels (Debian 6, 7 and 8), if possible. As far as I'm aware it's stable feature, and there is no downside from enabling it. +General setup [*] Kernel .config support [*] Enable access to .config through /proc/config.gz Original article: http://superuser.com/questions/287371/obtain-kernel-config-from-currently-running-linux-system Thanks in advance, -- -Alexey Eromenko Technologov, 01.May.2015. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783995: [feature-request] Please allow to view kernel config via /proc/config.gz in all Debian kernels
Control: reassign -1 src:linux Control: severity -1 wishlist On Sat, 2015-05-02 at 01:39 +0300, Alexey Eromenko wrote: Package: linux-image-amd64 Version: 3.16.7-ckt7-1 Hi, It would help me very much, if Debian kernel provided a quick ability to see it's own configuration in /proc/config.gz. Reason: in some cases viewing current kernel configuration via # /boot/config-$(uname -r) is not available; For example when working with Debian-installer (booting from DVD), or working inside an OpenVZ (or LXC) container. Why would it be good for this to be exposed inside a container? For those reasons I ask you to enable /proc/config.gz in all supported Debian kernels (Debian 6, 7 and 8), if possible. This definitely will not be changed in existing stable releases. As far as I'm aware it's stable feature, and there is no downside from enabling it. [...] There is a downside: it consumes more memory and disk space (though not that much). Ben. -- Ben Hutchings It is easier to write an incorrect program than to understand a correct one. signature.asc Description: This is a digitally signed message part
Bug#764401: Are you planning to take over mksh in Debian?
Kenneth Pronovici dixit: I filed the bug so nothing would get lost while the package is orphaned, which seems like a reasonable thing to do. The next That may seem reasonable… maintainer might very well have a different policy for Debian bugs than you did. I would if it were my package. … and even if this were reasonable… it’s still not a reasonable thing as I indicated interest upstream for this already. I know you’re well-meaning and all, but you’re interfering with things that currently work. (That, written out in the English language, sounds harsher than I mean it, please take it in that spirit.) bye, //mirabilos -- “ah that reminds me, thanks for the stellar entertainment that you and certain other people provide on the Debian mailing lists │ sole reason I subscribed to them (I'm not using Debian anywhere) is the entertainment factor │ Debian does not strike me as a place for good humour, much less German admin-style humour” -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764401: Bug#783978: Bug#764401: Are you planning to take over mksh in Debian?
Kenneth Pronovici dixit: I'm not trying to be snarky here, but I'm a little lost. This package is orphaned. If you're no longer the package maintainer, why should it even matter to you whether upstream issues are tracked as Debian bugs? Because ① I’m upstream, ② I’m maintaining this package in Debian, and, most importantly, ③ feature requests aren’t bugs, period. Besides that, this is arguably a functional regression vs. older versions of pdksh in Debian, which mksh now provides. I think it's useful to have the change in behavior noted, even if it is only a wishlist. That’s arguably a good point. One of mksh’s biggest strengths is that it behaves consistently across all platforms, though. DO NOT break that. Goodnight, //mirabilos -- igli exceptions: a truly awful implementation of quite a nice idea. igli just about the worst way you could do something like that, afaic. igli it's like anti-design. mirabilos that too… may I quote you on that? igli sure, tho i doubt anyone will listen ;) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764401: Bug#783978: Bug#764401: Are you planning to take over mksh in Debian?
On Fri, May 1, 2015 at 6:18 PM, Thorsten Glaser t...@mirbsd.de wrote: Kenneth Pronovici dixit: I'm not trying to be snarky here, but I'm a little lost. This package is orphaned. If you're no longer the package maintainer, why should it even matter to you whether upstream issues are tracked as Debian bugs? Because ① I’m upstream, ② I’m maintaining this package in Debian, and, most importantly, ③ feature requests aren’t bugs, period. Besides that, this is arguably a functional regression vs. older versions of pdksh in Debian, which mksh now provides. I think it's useful to have the change in behavior noted, even if it is only a wishlist. That’s arguably a good point. One of mksh’s biggest strengths is that it behaves consistently across all platforms, though. DO NOT break that. Ok, this is clearly becoming way more of a big deal than I expected it to be. If you're maintaining the package in Debian (even though it's orphaned, which makes no sense to me) then feel free to just close #783978, the wishlist request. I'd prefer to have that bug stay open, but now we've moved into the realm of differing philosophies regarding bug reports, and you and I clearly disagree on this subject. Do whatever works best for you. As far as the mksh behavior is concerned, I never suggested (even in the original stackexchange discussion), that I wanted to make mksh behave differently in Debian than on other platforms. I was simply offering to help get the changes into Debian, based on the fact that the package appeared to be without a maintainer. If the package is being maintained, then you don't need my help with that. End of story. I hereby withdraw my interest in #764401, the ITA bug report. If you can make the requested improvement upstream, that's great, and I would really welcome the change. If not, I'll just find some other shell to use. Thanks, KEN -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783815: lintian: Using oracle java 8 in a package generate unknow-java-class-version.
Control: reopen -1
Hi again,
Axel Beckert wrote:
Version: 2.5.23
[...]
Jonathan Plamondon wrote:
Package: lintian
Version: 2.5.10.4
[...]
* What led up to the situation?
We have a package using java 8
* What exactly did you do (or not do) that was effective (or
ineffective)?
The warning are anoying.
* What was the outcome of this action?
The warning are anoying
* What outcome did you expect instead?
No warning.
[...]
Besides that this issue already has been fixed fixed in Lintian since
version 2.5.23 of June 2014 and the fix is included in Debian's
current stable release.
I may have been to quick with closing this. The code introduced in
2.5.23 may have an off-by-one error, but it also may be on purpose
(the changelog entry sys Catch uses of Java8 byte code):
if ( $mver = $MAX_BYTECODE-value('min-bytecode-version') - 1
or $mver
= $MAX_BYTECODE-value('max-bytecode-existing-version')) {
# First public major version was 45 (Java1), latest
# version is 52 (Java8).
tag 'unknown-java-class-version', $jar_file,
($class - $mver);
The = in there likely should be just a if Java 8 byte code
(i.e. for use with openjdk-8 from experimental) is fine. Or am I
misunderstanding the semantics of max-bytecode-existing-version?
Sylvestre: It'd be nice if you could have a look at this as you
introduced that code path in be04767b998558e2fbc637ddee45f675141e13ee.
Regards, Axel
--
,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784004: cloud-init growpart module fails to execute due to different growpart version
Package: cloud-init
Version: 0.7.6~bzr976-2
Severity: normal
Dear Maintainer,
cloud-init included growpart executable from jessie repository do not
appear to work together. cloudinit/config/cc_growpart.py searches for
--update in output of growpart --help, but this is no longer
present; I think this is causing virtual machines to fail to resize the
root partition on first boot.
The log shows:
cc_growpart.py[DEBUG]: No 'growpart' entry in cfg. Using default:
{'ignore_growroot_disabled': False, 'mode': 'auto', 'devices': ['/']
util.py[DEBUG]: Running command ['growpart', '--help'] with allowed
return codes [0] (shell=False, capture=True)
cc_growpart.py[DEBUG]: growpart unable to find resizer for 'auto': No
resizers available
But the ResizerGrowPart class should be available.
-- System Information:
Debian Release: 8.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages cloud-init depends on:
ii debconf [debconf-2.0] 1.5.56
ii ifupdown0.7.53.1
ii lsb-base4.1+Debian13+nmu1
ii procps 2:3.3.9-9
ii python 2.7.9-1
ii python-boto 2.34.0-2
ii python-cheetah 2.4.4-3
ii python-configobj5.0.6-1
ii python-jsonpatch1.3-5
ii python-oauth1.0.1-4
ii python-prettytable 0.7.2-3
ii python-requests 2.4.3-6
ii python-serial 2.6-1.1
ii python-software-properties 0.92.25debian1
ii python-yaml 3.11-2
cloud-init recommends no packages.
cloud-init suggests no packages.
-- Configuration Files:
/etc/cloud/cloud.cfg changed:
users:
- default
disable_root: true
preserve_hostname: false
datasource:
OpenStack: {}
None: {}
datasource_list:
- OpenStack
cloud_init_modules:
- migrator
- seed_random
- bootcmd
- write-files
- growpart
- resizefs
- set_hostname
- update_hostname
- update_etc_hosts
- ca-certs
- rsyslog
- users-groups
- ssh
cloud_config_modules:
- emit_upstart
- disk_setup
- mounts
- ssh-import-id
- locale
- set-passwords
- grub-dpkg
- apt-pipelining
- apt-configure
- package-update-upgrade-install
- landscape
- timezone
- puppet
- chef
- salt-minion
- mcollective
- disable-ec2-metadata
- runcmd
- byobu
cloud_final_modules:
- rightscale_userdata
- scripts-vendor
- scripts-per-once
- scripts-per-boot
- scripts-per-instance
- scripts-user
- ssh-authkey-fingerprints
- keys-to-console
- phone-home
- final-message
- power-state-change
system_info:
# This will affect which distro class gets used
distro: debian
# Default user name + that default users groups (if added/used)
default_user:
name: debian
lock_passwd: True
gecos: Debian
groups: [adm, audio, cdrom, dialout, floppy, video, plugdev, dip, sudo]
sudo: [ALL=(ALL) NOPASSWD:ALL]
shell: /bin/bash
# Other config here will be given to the distro class and/or path classes
paths:
cloud_dir: /var/lib/cloud/
templates_dir: /etc/cloud/templates/
upstart_dir: /etc/init/
package_mirrors:
- arches: [default]
failsafe:
primary: http://ftp.debian.org/debian
ssh_svcname: ssh
-- debconf information:
cloud-init/datasources: NoCloud, AltCloud, CloudStack, ConfigDrive,
Ec2, MAAS, OVF, GCE, None
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781523: RFS: task-spooler/0.7.5-1
Hi Alexander, 2015-04-30 16:06 GMT-03:00 Alexander Inyukhin shur...@sectorb.msk.ru: Hi Eriberto! Thanks for detailed and helpful review! You're welcome. Thanks for your work. On Mon, Apr 27, 2015 at 09:35:37PM -0300, Eriberto Mota wrote: 2. d/copyright: - The upstream code is GPL-2, not GPL-2+. The GPL-2+ license for sources is claimed at the project site. Even though source files refer directly to the COPYING file without or (at your option) any later version statement, the author has the right to distribute sources under another license. But I am not a lawyer. The problem is that the upstream isn't explicit in his intents. I posted a question[1] in debian-legal. Feel free to complement the information. Now, we need to wait some answers. [1] https://lists.debian.org/debian-legal/2015/05/msg1.html - The main.c and server.c files show that the 0.7.5 version is copyrighted as 2007-2013. This version is released this year, so it should be 2007-2015, probably. It is optional. You can use dates from headers or from release, if you know this last information and it is public. So, you can use 2007-2013 or 2007-2015. Cheers, Eriberto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718436: dconf-tools: dconf-editor segfaults when selected item is removed
Package: dconf-editor Version: 0.22.0-1 Followup-For: Bug #718436 dconf-editor also crashes when the item is selected after its deletion. It doesn't have to be selected during that process. The editor obviously doesn't react correctly to changes in the database and doesn't check if an entry still exists. Also refreshing the loaded content manually isn't possible. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dconf-editor depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii libatk1.0-0 2.14.0-1 ii libc62.19-18 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libdconf10.22.0-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libxml2 2.9.1+dfsg1-5 dconf-editor recommends no packages. dconf-editor 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#783999: Should not disable safe browsing mechanism
Package: chromium Version: 42.0.2311.135-1 Severity: important From the changelog: [ Shawn Landden ] * Supress first run welcome page. * Turn off safebrowsing. * Turn off pinging Google on 404 and other HTTP errors. Judging by the changes it was grouped with, I'm guessing that this change was made for privacy reasons. However, to the best of my knowledge, the mechanism used to implement safe browsing does *not* check individual URLs against a server (at Google or elsewhere); instead, it downloads a filter and checks URLs against that. - Josh Triplett -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chromium depends on: ii libasound2 1.0.28-1 ii libc62.19-18 ii libcairo21.14.0-2.1 ii libcap2 1:2.24-8 ii libcups2 1.7.5-11 ii libdbus-1-3 1.8.16-1 ii libexpat12.1.0-6+b3 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-4 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgnome-keyring03.12.0-1+b1 ii libgtk2.0-0 2.24.25-3 ii libharfbuzz0b0.9.35-2 ii libjpeg62-turbo 1:1.3.1-12 ii libnspr4 2:4.10.8-1 ii libnspr4-0d 2:4.10.8-1 ii libnss3 2:3.17.2-1.1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpci3 1:3.2.1-3 ii libspeechd2 0.8-7 ii libspeex11.2~rc1.2-1 ii libsrtp0 1.4.5~20130609~dfsg-1.1 ii libstdc++6 4.9.2-10 ii libx11-6 2:1.6.2-3 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1+b1 ii libxdamage1 1:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.1-2+b2 ii libxi6 2:1.7.4-1+b2 ii libxml2 2.9.2+dfsg1-3 ii libxrandr2 2:1.4.2-1+b1 ii libxrender1 1:0.9.8-1+b1 ii libxslt1.1 1.1.28-2+b2 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.2-1+b1 ii x11-utils7.7+2 ii xdg-utils1.1.0~rc1+git20111210-7.4 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n 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#767682: D-I: installer hangs on re-formatting ext4 partition (having grub in the partition boot record).
I can confirm that the bug still exists. It exists in all my live-builds for jessie. No problem to reproduce it with manual partioning. It happens every time I try to reformat and use an existing ext4-partions where another installation exists. In other words, a partition which holds a grub. If I erase the data on the partition first, then I'm fine. If not, it hangs indefinately on formatting that partition... Also, it's easy to reproduce in terminal... Without the force parameter, it hangs at this: (just pick a partition where you know there are another installation containing a grub) $ mke2fs -t ext4 /dev/sda6 mke2fs 1.42.12 (29-Aug-2014) /dev/sda6 contains a ext4 file system last mounted on / on Sat May 2 01:02:54 2015 Proceed anyway? (y,n) As you don't get to confirm this when using the Debian-Installer, it will hang forever at this point. Best, EW
Bug#784012: lintian: Allow quoted distribution name when checking experimental-to-unstable-without-comment
Package: lintian
Version: 2.5.30+deb8u4
Severity: minor
Control: patch
Dear Maintainer,
The check for ‘experimental-to-unstable-without-comment’ uses a regex
that misses some obvious (to humans) instances of the phrase being
sought.
In particular, it is normal English to put a name in quotation marks,
for clarity. For example, I can talk about “unstable” by placing that
term in quotation marks.
But using a changelog entry like:
* Resume our uploads to ‘unstable’ since the freeze has ended.
will fail to match the regex, which expects nothing but space between
“to” and “unstable”.
The attached patch refines the regex to allow a quoted distribution
name, and updates the tag description to more accurately describe the
criteria.
--
\ “You can be a victor without having victims.” —Harriet Woods, |
`\ 1927–2007 |
_o__) |
Ben Finney b...@benfinney.id.au
The following changes since commit a0bac6cda42e8822aaf3c069cdfa82bb1fb4a30a:
checks.pot: Update (2015-05-01 18:43:01 +0200)
are available in the git repository at:
https://bull.codes/git/bignose/lintian/
for you to fetch changes up to c42a1efcd338d639e4e2adc67f9eaa24002cac15:
Accurately describe criteria for ‘experimental-to-unstable-without-comment’. (2015-05-02 15:15:42 +1000)
Ben Finney (2):
Allow quoting the distribution name in changelog entry.
Accurately describe criteria for ‘experimental-to-unstable-without-comment’.
checks/changelog-file.desc | 14 +-
checks/changelog-file.pm | 5 -
2 files changed, 13 insertions(+), 6 deletions(-)
diff --git a/checks/changelog-file.desc b/checks/changelog-file.desc
index 1abb07f..9330822 100644
--- a/checks/changelog-file.desc
+++ b/checks/changelog-file.desc
@@ -223,11 +223,15 @@ Tag: experimental-to-unstable-without-comment
Severity: pedantic
Certainty: possible
Info: The previous version of this package had a distribution of
- experimental, this version has a distribution of unstable, and there's
- apparently no comment about the change of distributions (Lintian looks
- for the phrase to unstable). This may indicate a mistake in setting
- the distribution and accidentally uploading to unstable a package
- intended for experimental.
+ experimental, this version has a distribution of unstable, and there's
+ apparently no comment about the change of distributions.
+ .
+ Lintian looks in this version's changelog entry for the phrase to
+ unstable or to sid, with or without quotation marks around the
+ distribution name.
+ .
+ This may indicate a mistake in setting the distribution and accidentally
+ uploading to unstable a package intended for experimental.
Tag: syntax-error-in-debian-changelog
Severity: normal
diff --git a/checks/changelog-file.pm b/checks/changelog-file.pm
index a5d0e07..e641c57 100644
--- a/checks/changelog-file.pm
+++ b/checks/changelog-file.pm
@@ -323,7 +323,10 @@ sub run {
my $first_dist = lc $entries[0]-Distribution;
my $second_dist = lc $entries[1]-Distribution;
if ($first_dist eq 'unstable' and $second_dist eq 'experimental') {
-unless ($entries[0]-Changes =~ /\bto\s+(?:unstable|sid)\b/im){
+unless (
+$entries[0]-Changes
+=~ /\bto\s+['‘“]?(?:unstable|sid)['’”]?\b/im
+) {
tag 'experimental-to-unstable-without-comment';
}
}
signature.asc
Description: Digital signature
Bug#784011: xen: CVE-2015-3340: Information leak through XEN_DOMCTL_gettscinfo (XSA-132)
Source: xen Version: 4.4.1-9 Severity: normal Tags: security upstream patch fixed-upstream Hi, the following vulnerability was published for xen. CVE-2015-3340[0]: | Xen 4.2.x through 4.5.x does not initialize certain fields, which | allows certain remote service domains to obtain sensitive information | from memory via a (1) XEN_DOMCTL_gettscinfo or (2) | XEN_SYSCTL_getdomaininfolist request. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-3340 [1] http://xenbits.xen.org/xsa/advisory-132.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783347: Any ETA on when the backport will come to jessie ?
On Sat, May 02, 2015 at 01:01:29PM +1000, Craig Small wrote: On Thu, Apr 30, 2015 at 07:46:52PM +0100, Rodrigo Campos wrote: But is there any ETA on when the changes will come to jessie ? Can I help you with testing ? Also, I can review the backports if you still need peer review :) I'm about to release it. I emailled security team and they didn't say no, but it wasn't exactly clear I was ok to proceed. Great, thanks a lot Craig. Really. And sorry again, Rodrigo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783995: [feature-request] Please allow to view kernel config via /proc/config.gz in all Debian kernels
On Fri, May 01, 2015 at 11:50:31PM +0100, Ben Hutchings wrote: On Sat, 2015-05-02 at 01:39 +0300, Alexey Eromenko wrote: As far as I'm aware it's stable feature, and there is no downside from enabling it. [...] There is a downside: it consumes more memory and disk space (though not that much). And there is no need for it. Debian provides allready the information of zcat /proc/config.gz in a file with a name like config-VERSION-VER-ARCH which gets installed in /boot Example given grep -i -e floppy -e fdc /boot/config* Groeten Geert Stappers Who thinks that this bugreport should be closed or marked as 'WONTFIX' -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783974: pulseaudio: No sound on boot till pulseaudio is killed and restarted
On Saturday 02 May 2015 12:53 AM, Felipe Sateler wrote: On 1 May 2015 at 16:06, L. Guruprasad lgp171...@gmail.com wrote: Please do the following: Modify /etc/pulse/daemon.conf to set: log-level = debug log-time = true log-target = file:/tmp/pulselog Then restart the machine. After login, please attach the generated log (/tmp/pulselog). There is no such file /tmp/pulselog generated after restart. Also please attach the output of `pactl list` while pulseaudio has no sound. guruprasad@kal-el:~$ pactl list Connection failure: Connection refused pa_context_connect() failed: Connection refused Hope this helps. Thanks Regards, Guruprasad -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783948: arj: out-of-bounds read
Package: arj Version: 3.10.22-13 Usertags: afl arj crashes on the attached file: $ arj t crash.arj ARJ32 v 3.10, Copyright (c) 1998-2004, ARJ Software Russia. [28 Mar 2015] Processing archive: crash.arj Archive created: 2014-12-27 11:40:05, modified: 2014-12-27 11:40:05 Testing limerickSegmentation fault GDB says it's an out-of-bounds read: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0804ab9c in decode (action=0) at decode.c:465 465 dec_text[r]=dec_text[i]; (gdb) print i $1 = -32768 (gdb) print dec_text[i] Cannot access memory at address 0x8733848 (gdb) bt #0 0x0804ab9c in decode (action=0) at decode.c:465 #1 0x0805c4f3 in unpack_file (action=0) at arj_arcv.c:2444 #2 0x0805c937 in unpack_validation (cmd=84) at arj_arcv.c:2604 #3 0x080535b0 in process_archive (cmd=84, no_in_arch=0) at arj_user.c:831 #4 0x08056db0 in process_archive_proc (cmd=84) at arj_user.c:2047 #5 0x080571fe in perform_cmd (cmd=84) at arj_user.c:2660 #6 0x0805090f in main (argc=3, argv=0xffadd6b4) at arj.c:1275 This bug was found using American fuzzy lop: http://lcamtuf.coredump.cx/afl/ -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages arj depends on: ii libc6 2.19-18 -- Jakub Wilk crash.arj Description: Binary data
Bug#783950: d-i.debian.org: PO spellchecking broken
Package: d-i.debian.org
Severity: normal
The set of scripts that generate D-I l10n spellchecking statistics are
apparently broken since the d-i.debian.org host was upgraded to
Jessie. Output follows.
The master script that generates the following is:
d-i@dillon:/srv/d-i.debian.org/home/l10n/material/packages.cvs1/debian-installer$
cat ~/bin/d-i_spellcheck
#!/bin/sh
cd ${HOME}/trunk/scripts/l10n/l10n-spellcheck/cfg
svn -q update
./update_po.sh
for i in man l1 l2 l3 ; do
#echo Spellchecking level $i
./scheck.sh $i
done
Sadly, I'm not sure that anyone but Davide Viti who wrote the original
set of scripts, can fix this...:-)
- Forwarded message from Cron Daemon r...@dillon.debian.org -
Date: Thu, 30 Apr 2015 03:21:51 +
From: Cron Daemon r...@dillon.debian.org
To: bubu...@dillon.debian.org, k...@dillon.debian.org
Subject: Cron d-i@dillon $HOME/bin/d-i_spellcheck ; ~/bin/push-www
X-CRM114-Status: Good ( pR: 14.9657 )
Error: The language el is not known. This is probably because: the file
/usr/share/aspell/el.dat can not be opened for reading.
Error: The file /tmp/fileJxXALD is not in the proper format.
Error: The language fi is not known. This is probably because: the file
/usr/share/aspell/fi.dat can not be opened for reading.
Error: No word lists can be found for the language fi.
Error: The language hu is not known. This is probably because: the file
/usr/share/aspell/hu.dat can not be opened for reading.
Error: The file /tmp/file3Sl4iA is not in the proper format.
Error: The language pt_PT is not known. This is probably because: the file
/usr/share/aspell/pt_PT.dat can not be opened for reading.
Error: The file /tmp/fileUIdsQ1 is not in the proper format.
Error: The language ro is not known. This is probably because: the file
/usr/share/aspell/ro.dat can not be opened for reading.
Error: The file /tmp/file35GqWl is not in the proper format.
Error: The language ru is not known. This is probably because: the file
/usr/share/aspell/ru.dat can not be opened for reading.
Error: The file /tmp/fileonFXd8 is not in the proper format.
Error: The language sv is not known. This is probably because: the file
/usr/share/aspell/sv.dat can not be opened for reading.
Error: The file /tmp/fileloE2Q7 is not in the proper format.
Error: The language tl is not known. This is probably because: the file
/usr/share/aspell/tl.dat can not be opened for reading.
Error: The file /tmp/filebVYCcl is not in the proper format.
Error: The language en is not known. This is probably because: the file
/usr/share/aspell/en.dat can not be opened for reading.
Error: The file /tmp/fileudTxQU is not in the proper format.
Error: The language am is not known. This is probably because: the file
/usr/share/aspell/am.dat can not be opened for reading.
Error: The file /tmp/fileMBYqZb is not in the proper format.
Error: The language ar is not known. This is probably because: the file
/usr/share/aspell/ar.dat can not be opened for reading.
Error: The file /tmp/filepXr5H3 is not in the proper format.
Error: The language bg is not known. This is probably because: the file
/usr/share/aspell/bg.dat can not be opened for reading.
Error: The file /tmp/fileEiMT0M is not in the proper format.
Error: The language bn is not known. This is probably because: the file
/usr/share/aspell/bn.dat can not be opened for reading.
Error: The file /usr/lib/aspell/bn.rws is not in the proper format.
Incompatible hash function.
Error: The language ca is not known. This is probably because: the file
/usr/share/aspell/ca.dat can not be opened for reading.
Error: The file /tmp/fileqIP8Md is not in the proper format.
Error: The language cs is not known. This is probably because: the file
/usr/share/aspell/cs.dat can not be opened for reading.
Error: The file /tmp/fileeIqx68 is not in the proper format.
Error: The language cy is not known. This is probably because: the file
/usr/share/aspell/cy.dat can not be opened for reading.
Error: The file /tmp/fileGL8xkm is not in the proper format.
Error: The language da is not known. This is probably because: the file
/usr/share/aspell/da.dat can not be opened for reading.
Error: The file /tmp/filevr2Fae is not in the proper format.
Error: The language de is not known. This is probably because: the file
/usr/share/aspell/de.dat can not be opened for reading.
Error: The file /tmp/fileh8J2f3 is not in the proper format.
Error: The language el is not known. This is probably because: the file
/usr/share/aspell/el.dat can not be opened for reading.
Error: The file /tmp/fileLFcwxX is not in the proper format.
Error: The language eo is not known. This is probably because: the file
/usr/share/aspell/eo.dat can not be opened for reading.
Error: The file /tmp/filekpTI5B is not in the proper format.
Error: The language en is not known. This is probably because: the file
/usr/share/aspell/en.dat can not be opened for reading.
Error: The file /tmp/fileGoWWfh is not in the proper format.
Error: The
Bug#635772: example
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Here is a sample session: % ls -l pbuilder.doc* - -rw-r--r-- 1 harri harri 22555 Jan 24 16:27 pbuilder.doc % mg pbuilder.doc # edit and save pbuilder.doc % ls -l pbuilder.doc* - -rw-r--r-- 1 harri harri 22597 May 1 16:38 pbuilder.doc - -rw-r--r-- 1 harri harri 22555 May 1 16:38 pbuilder.doc~ If the new pbuilder.doc is bad and I want to revert back to the previous version, then the previous modification time has been lost. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVQ5FyAAoJEAqeKp5m04HLE1kH/17VVX8gUgQyIMSDuJLN3N17 3KQoFx0J1/LGO3TSsgnI0XlBVJhP1iWsbSf6zXQAoy1gZCDpRJNGT5/5PExDRhbD EIBXPkrccMtsOk08q9BZJM8ziE1OM6TZ848YxfHPwjzm8poa1yogLFQSuUoORDV+ Mu/R2sNTM85OLnHoSttOeayuiI3dKqlBwLKA0f1/REibKmQ3jaFq5TJQFwSJtEr3 mSdBiHKPwj2e+n1BWQK2X42ykfw9PITQyRyvOFNwReL9HPJ15mwnEUywoOQAs0RX gq/iJFm6rzR/+THRV0Jd3Mfq3z4GEkZ31Oe1zBa5yC1mjkpPeRQc3mNneq6bPBA= =k5Yl -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#783955: python3.4: Unprecise floating point math
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: python3.4 Version: 3.4.3-5 Severity: normal Dear Maintainer, the floating point math of Python 3.4.3 and Python 2.7.9 is a bit unprecise: python3 Python 3.4.3 (default, Apr 30 2015, 12:12:54) [GCC 4.9.2] on linux Type help, copyright, credits or license for more information. 9.0+9.3+96.19+62.0+500.0+75.0+9.0+26.90+9.8+107.24+62.0+75.0 1041.42998 python Python 2.7.9 (default, Apr 29 2015, 18:34:06) [GCC 4.9.2] on linux2 Type help, copyright, credits or license for more information. 9.0+9.3+96.19+62.0+500.0+75.0+9.0+26.90+9.8+107.24+62.0+75.0 1041.42998 The correct result is 1041.43. With best regards, Julian Wollrath - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.6 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3.4 depends on: ii libpython3.4-stdlib 3.4.3-5 ii mime-support 3.58 ii python3.4-minimal3.4.3-5 python3.4 recommends no packages. Versions of packages python3.4 suggests: ii binutils2.25-7 ii python3.4-doc 3.4.3-5 pn python3.4-venv none - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVQ5GeAAoJEFl2dmpRMS8z05MH/1LTOB2KAhOsSfulNOl9+NYM OTyjodvIDlOZdYgP6Op8/meuNwSlWYACF+CYRp13iAr3CRcTl4aapbv31FSa4/yF rr95X2UGv2+qfz+9GQdzJohj3jsWaerFhyNPR/NMmNgvhgMn4zk5h4RW/8buA3NV yXMrNMyqz3t6F9Lya190frw0Yw1x3tIxegyBdo0zIsXLuEcXfzlbiriFgkhPNboO IqZwNZTHCqTfJ33uIKO3d7StwJ4b6yKQ/eGLPP8hbfv3ZbnkiJUlowDU5kWSTpfW GW4vcITAuf5EeQl5jKtPDMU6r5m5cquzv8XvH8uBoXkQU7tb2LXQ32qapLLgloM= =Kdwi -END PGP SIGNATURE-
Bug#783615: update-ca-certificates --fresh doesn't correctly re-add certificates in /usr/local/share/ca-certificates
Thank you for the details. On 04/30/2015 02:41 AM, Daniel Lutz wrote: The hooks in /etc/ca-certificates/update.d are called to re-add/ update/replace certificates in $CERTSDIR, but not for those in $LOCALCERTSDIR. Is this intended behaviour? It seems that this has just never come up, so it looks like --fresh should do the right thing and create the keystore as intended normally. The attached patch contains a fix that might solve the problem. I'll have a look, but do we create symlinks to $LOCALCERTSDIR CA certificates? (I haven't looked at all, yet) Yes, the function add() creates such links. Yep! I haven't tested the patch out, but it does seem reasonable that $LOCALCERTSDIR certs should also be considered in the same way in your use case. Thanks again :) Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783747: (no subject)
L.J.Lane you could ask what kernel this occurs on than marking it as non-reproducible. The default kernel that gets installed with Jessie 8 amd64 (3.16.0-4), does not work with iptables. If you are trying to reproduce this bug, be sure you are using Jessie 8 amd64 as I don't know whether it affects the 32-bit. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783951: libconfig-model-dpkg-perl: autopkgtest regression: model_tests.t failure
Package: libconfig-model-dpkg-perl
Version: 2.059
User: debian-p...@lists.debian.org
Usertags: autopkgtest
This package recently started failing its autopkgtest checks
on ci.debian.net:
http://ci.debian.net/packages/libc/libconfig-model-dpkg-perl/unstable/amd64/
Log excerpt:
ok 394 - Failed dump 0 of dpkg-copyright config tree
Load command error in node 'Files:* Copyright' :
command: Copyright:0=(c) foobar
Error: list or hash command (':') detected on a leaf.(element 'Files:*
Copyright')
writing back cache file
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 394.
Dubious, test returned 255 (wstat 65280, 0xff00)
All 394 subtests passed
Test Summary Report
---
t/model_tests.t (Wstat: 65280 Tests: 394 Failed: 0)
Non-zero exit status: 255
Parse errors: No plan found in TAP output
--
Niko Tyni nt...@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#783952: libconfig-model-openssh-perl: autopkgtest regression: ssh_config.t failure
Package: libconfig-model-openssh-perl Version: 1.236-1 User: debian-p...@lists.debian.org Usertags: autopkgtest This package recently started failing its autopkgtest checks on ci.debian.net: http://ci.debian.net/packages/libc/libconfig-model-openssh-perl/unstable/amd64/ Log excerpt: t/ssh_config.t . ok 1 - compiled # Running test like root (no layered config) Configuration item has a configuration model declaration error: Included read_config from Ssh cannot clobber existing data in SystemSsh # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 2 just after 1. Dubious, test returned 2 (wstat 512, 0x200) All 1 subtests passed Test Summary Report --- t/ssh_config.t (Wstat: 512 Tests: 1 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=4, Tests=13, 3 wallclock secs ( 0.05 usr 0.04 sys + 1.91 cusr 0.49 csys = 2.49 CPU) Result: FAIL -- Niko Tyni nt...@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#783909: libgphoto2-2-dev missing for requested tests
Hi Emilio, Am Freitag, den 01.05.2015, 17:06 +0200 schrieb Emilio Pozuelo Monfort: On 01/05/15 15:20, Jörg Frings-Fürst wrote: Hello Emilio, [...] Sorry but I don't see how that makes it a libgphoto bug. libgphoto2-2-dev wasn't in libgphoto2?? Which isn't a bug, but an intended change. You have to update your dependency to the new package name... Have I once claimed that I had it not done? But piuparts need for testing the last version installable. And there I can change anything. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#764401: Are you planning to take over mksh in Debian?
Hi Dominik, Are you still planning to take over mksh in Debian? If not, I would like to take ownership of #76401 and maintain the package myself. I actively use ksh on Debian, and I don't want to see the packages go unmaintained. Also, I have been talking with upstream about some improvements, and I want to be in a position where I can apply patches. Thanks! KEN -- Kenneth J. Pronovici prono...@debian.org
Bug#783899: liblog-any-perl, liblog-any-adapter-perl: File conflict when being installed together
Quoting gregor herrmann (2015-05-01 15:17:59) From liblog-any-perl/1.03-1 Changes (for 1.00): - Merged Log-Any and Log-Any-Adapter distributions; reduces code duplication and ensures Log::Any and adapter framework stay in sync So liblog-any-adapter-perl has been merged into liblog-any-perl. I guess we need: - a versioned Breaks+Replaces - a virtual dummy package (which will remove src:liblog-any-adapter-perl) - and then bugs/fixes in all rdeps (some unfortunately versioned, so a Provides wouldn't buy us much): https://codesearch.debian.net/results/liblog-any-adapter-perl%20path%3Adebian%2Fcontrol/page_0 where the fix probably is liblog-any-perl (= 1.00) | liblog-any-adapter-perl [(= 0.11)] I now update libcatmandu-perl which simplifies dependencies (needs liblog-any-* 1.03 now). After that I will relax liblog-any-adapter-screencoloredlevel-perl to have unversioned dependency: 0.11 is satisfied even in oldstable. If someone does same for liblog-any-adapter-callback-perl I believe no other versioned build-dependencies are left, and we can have liblog-any-perl provide liblog-any-adapter-perl. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#783960: [hplip] hplip don't work
Package: hplip Version: 3.14.6-1+b2 Severity: serious --- Please enter the report below this line. --- I can't install my hp 127fn because hplip don't work. The missing packages is installed. There is an information saying that hplip don't work with debian 8 Attached four files. --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: 8.0 500 stable-updates ftp.br.debian.org 500 stable security.debian.org 500 stable ftp.br.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. --- Output from package bug script --- -- ASD Consultoria, Rio, RJ Arq. Sávio M Ramos Só usamos Linux desde 2000 www.debian.org hp-check[3516]: info: : hp-check[3516]: info: :[01mHP Linux Imaging and Printing System (ver. 3.14.6)[0m hp-check[3516]: info: :[01mDependency/Version Check Utility ver. 15.1[0m hp-check[3516]: info: : hp-check[3516]: info: :Copyright (c) 2001-13 Hewlett-Packard Development Company, LP hp-check[3516]: info: :This software comes with ABSOLUTELY NO WARRANTY. hp-check[3516]: info: :This is free software, and you are welcome to distribute it hp-check[3516]: info: :under certain conditions. See COPYING file for more details. hp-check[3516]: info: : hp-check[3516]: info: :[01mNote: hp-check can be run in three modes:[0m hp-check[3516]: info: :1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or hp-check[3516]: info: :.run) to determine if the proper dependencies are installed to successfully compile HPLIP. hp-check[3516]: info: :2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or hp-check[3516]: info: :an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. hp-check[3516]: info: :3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases hp-check[3516]: info: :(both compile- and run-time dependencies). hp-check[3516]: info: : hp-check[3516]: info: :Check types: hp-check[3516]: info: :a. EXTERNALDEP - External Dependencies hp-check[3516]: info: :b. GENERALDEP - General Dependencies (required both at compile and run time) hp-check[3516]: info: :c. COMPILEDEP - Compile time Dependencies hp-check[3516]: info: :d. [All are run-time checks] hp-check[3516]: info: :PYEXT SCANCONF QUEUES PERMISSION hp-check[3516]: info: : hp-check[3516]: info: :Status Types: hp-check[3516]: info: :OK hp-check[3516]: info: :MISSING - Missing Dependency or Permission or Plug-in hp-check[3516]: info: :INCOMPAT - Incompatible dependency-version or Plugin-version hp-check[3516]: info: : warning: [01mdebian-8.0 version is not supported. Using debian-7.5 versions dependencies to verify and install...[0m hp-check[3516]: info: : hp-check[3516]: info: :--- hp-check[3516]: info: :| SYSTEM INFO | hp-check[3516]: info: :--- hp-check[3516]: info: : hp-check[3516]: info: : Kernel: 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) GNU/Linux Host: portatil Proc: 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) GNU/Linux Distribution: debian 8.0 hp-check[3516]: info: : Bitness: 64 bit hp-check[3516]: info: : hp-check[3516]: info: :--- hp-check[3516]: info: :| HPLIP CONFIGURATION | hp-check[3516]: info: :--- hp-check[3516]: info: : hp-check[3516]: info: :HPLIP-Version: HPLIP 3.14.6 hp-check[3516]: info: :HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not supported for debian distro 8.0 version hp-check[3516]: info: : hp-check[3516]: info: :[01mCurrent contents of '/etc/hp/hplip.conf' file:[0m hp-check[3516]: info: :# hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.14.6 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/hplip/HP ppdbase=/usr/share/ppd/hplip doc=/usr/share/doc/hplip-doc/HTML html=/usr/share/doc/hplip-3.14.6 icon=no cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv bin=/usr/bin # Following values are determined at configure time and cannot be changed. [configure] network-build=yes libusb01-build=no pp-build=yes gui-build=yes scanner-build=yes
Bug#783958: linux-image-3.16.0-4-amd64: iptables fails to work with jessie's kernel
Package: linux-image-3.16.0-4-amd64 Version: 3.16.7-ckt9-3~deb8u1 Severity: important A simple test with iptables against Jessie's default kernel fails to work, but using a custom kernel not from repositories and iptables works. A simple test is done allowing one match rule, and it can immediately be seen there is a problem with either iptables or Jessie's default kernel of 3.16.0-4-amd64. eg, iptables -I INPUT -p tcp --dport 22 -j ACCEPT iptables -P INPUT DROP traffic to port 22 later works if I apply iptables -P INPUT ACCEPT Using a non-stock kernel, the above example works exactly as expected. Since iptables can work with another kernel then I suppose there is something wrong with linux-image-3.16.0-4-amd64 preventing iptables from working. please have a look thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783959: linphone: gsm codec is not included in the debian package
Package: linphone Version: 3.6.1-2.4+b1 Severity: normal Dear Maintainer, I mainly use the gsm codec. It is the only codec I can get decent audio quality, otherwise the audio only makes wired noises. I did not find out the real cause of this. -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linphone depends on: ii libasound21.0.28-1 ii libatk1.0-0 2.14.0-1 ii libavcodec56 6:11.3-1 ii libavutil54 6:11.3-1 ii libc6 2.19-18 ii libcairo2 1.14.0-2.1 ii libexosip2-11 4.1.0-2 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-3 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libglew1.10 1.10.0-3 ii libglib2.0-0 2.42.1-1 ii libglu1-mesa [libglu1]9.0.0-2 ii libgtk2.0-0 2.24.25-3 ii liblinphone5 3.6.1-2.4+b1 ii libmediastreamer-base33.6.1-2.4+b1 ii libnotify40.7.6-2 ii libogg0 1.3.2-1 ii libopus0 1.1-2 ii libortp9 3.6.1-2.4+b1 ii libosip2-11 4.1.0-2 ii libpango-1.0-01.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libpulse0 5.0-13 ii libsoup2.4-1 2.48.0-1 ii libspandsp2 0.0.6-2+b2 ii libspeex1 1.2~rc1.2-1 ii libspeexdsp1 1.2~rc1.2-1 ii libsqlite3-0 3.8.7.1-1 ii libswscale3 6:11.3-1 ii libtheora01.1.1+dfsg.1-6 ii libudev1 215-17 ii libupnp6 1:1.6.19+git20141001-1 ii libv4l-0 1.6.0-2 ii libvpx1 1.3.0-3 ii libx11-6 2:1.6.2-3 ii libxv12:1.0.10-1+b1 ii linphone-nogtk3.6.1-2.4+b1 linphone recommends no packages. Versions of packages linphone suggests: ii yelp 3.14.1-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#783961: gnome-keyring: Split gnome-keyring-pkcs11.so into separate package
Package: gnome-keyring Version: 3.14.0-1+b1 Severity: wishlist Dear Maintainer, Please consider spliting gnome-keyring-pkcs11.so into separate package so i386 version is installable on amd64 systems. Ubuntu already does this and uses libp11-kit-gnome-keyring as pacakage name. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (650, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-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/bash Init: sysvinit (via /sbin/init) Versions of packages gnome-keyring depends on: ii dbus-x11 1.8.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gcr 3.14.0-2 ii libc62.19-18 ii libcap-ng0 0.7.4-2 ii libcap2-bin 1:2.24-8 ii libdbus-1-3 1.8.16-1 ii libgck-1-0 3.14.0-2 ii libgcr-base-3-1 3.14.0-2 ii libgcrypt20 1.6.3-2 ii libglib2.0-0 2.42.1-1 ii p11-kit 0.20.7-1 Versions of packages gnome-keyring recommends: pn libpam-gnome-keyring none gnome-keyring 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#783953: RM: emdebian-archive-keyring -- ROM; Key revoked and no new key
Package: ftp.debian.org Severity: normal The emdebian-archive key was deemed compromised and revoked in the last upload of the package. No key replaced it. Now that the revocation has made it into stable, please remove the package from unstable. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776563: DejaVu is not the only font that makes printing fail
Hi Ricardo, The bug is not in claws-mail, as discussed in earlier messages, if you don't want to workaround it by changing the default font in Claws Mail you can simply: # apt-get remove --purge fonts-dejavu-core That's not my experience. On the one hand, I can print using the dejavu mono font and the geany editor without problems. On the other hand, dejavu mono is not the only font that makes claws printing fail. The mail used for the test and the results table are attached. Best Regards, -- Manolo Díaz ---BeginMessage--- A very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very, very long line -- Manolo Díaz ---End Message--- tests.pdf Description: Adobe PDF document
Bug#783954: RM: emdebian-grip -- ROM; End of life
Package: ftp.debian.org Severity: normal emdebian-grip ceased updates in 2014. The support scripts in this package were deemed to possibly be of use in stable but there will be no further development of the scripts. Please remove the emdebian-grip package from unstable. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783909: libgphoto2-2-dev missing for requested tests
On 01/05/15 15:20, Jörg Frings-Fürst wrote: Hello Emilio, Am Freitag, den 01.05.2015, 15:00 +0200 schrieb Emilio Pozuelo Monfort: On 01/05/15 14:30, Jörg Frings-Fürst wrote: Hi Emilio, [...] Thats not the bug. Piuparts need for the upgrade test first install the last version of libsane-dev. And this fails with the missing libgphoto2-2-dev. Sorry but I don't see how that makes it a libgphoto bug. libgphoto2-2-dev wasn't in libgphoto2?? Which isn't a bug, but an intended change. You have to update your dependency to the new package name... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783956: Debian Jessie / Bridge-Utils
Package: bridge-utils Version: 1.5-9 I'm currently using the following setup: dedicated Server - bridge-utils (eth0 - br0) Once i installed bridge utils and setup my /etc/network/interfaces as follows: #source-directory /etc/network/interfaces.d auto lo iface lo inet loopback iface eth0 inet manual auto br0 iface br0 inet static address 37.187.163.XYZ netmask 255.255.255.0 network 37.187.163.0 broadcast 37.187.163.255 gateway 37.187.163.254 bridge_ports eth0 bridge_stp off bridge_fd 1 bridge_hello 2 bridge_maxage 12 After restarting the system, it becomes inaccessible. This is because of the following reasons: 1.) net.ipv4.ip_forward is per default set to 0, you have to manually change it, is this correct? I've thought this setting got adjusted to 1 automatically in wheezy. 2.) The routing-table gets messed up. Although the system brings up br0 it still tries to default route via eth0 and also a route via eth0 is existant which should not be the case: root@server:~# ip route show default via 37.187.163.254 dev eth0 37.187.163.0/24 dev eth0 proto kernel scope link src 37.187.163.XYZ 37.187.163.0/24 dev br0 proto kernel scope link src 37.187.163.XYZ To get this fixed you have to manually change the default route to br0 and remove the route via eth0: ip route delete 37.187.163.0/24 dev eth0 ip route delete default via 37.187.163.254 dev eth0 ip route add default via 37.187.163.254 dev br0 3.) Also, in wheezy the eth0-interface didnt get an ip address assigned to it when set to manual mode while having a br0 interface, in jessie this is somehow different: br0 Link encap:Ethernet HWaddr 00:25:90:a4:6c:ba inet addr:37.187.163.XYZ Bcast:37.187.163.255 Mask:255.255.255.0 inet6 addr: fe80::225:90ff:fea4:6cba/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:81357 errors:0 dropped:0 overruns:0 frame:0 TX packets:1121 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3808194 (3.6 MiB) TX bytes:111797 (109.1 KiB) eth0 Link encap:Ethernet HWaddr 00:25:90:a4:6c:ba inet addr:37.187.163.XYZ Bcast:37.187.163.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:108814 errors:0 dropped:59 overruns:0 frame:0 TX packets:1430 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:18440817 (17.5 MiB) TX bytes:142265 (138.9 KiB) Memory:fba2-fba3 eth0 seems to be virtual (Memory:fba2-fba3) but why does it show the address of br0 while wheezy did not? Thanks. I am using Debian GNU/Linux Jessie, 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24). -- Florian Strankowski Core Solutions Adolph Schönfelder Straße 68 22083 Hamburg, Germany web https://coresec.de This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden and may be unlawful. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768638: Missing definition of fnlibquadmath in from-debian-gcc-rename-info-files.diff
Hello,
On Sat, Nov 08, 2014 at 10:08:44PM +0100, Lars Ljung wrote:
Package: gcc-4.9-doc
Version: 4.9.1-3
The error message {No value for 'fnlibquadmath'} is shown in the info
dir file. The reason seems to be that there is no definition of
fnlibquadmath in from-debian-gcc-rename-info-files.diff.
The same problem exists in gcc-4.8
Kind regards,
Lars Ljung
This seems to be a bug specific to the package gcc-4.9-doc in Ubuntu,
since libquadmath.info is not included in Debian's gcc-4.9-doc
(4.9.1-3).
Regards,
Yixuan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784010: guake: Toggle doesn't work correctly
Package: guake Version: 0.5.0-2 Severity: grave Justification: renders package unusable I am running testing. After the last update in which Guake was updated the F12 toggle key nu longer closes Guake. The F12 key opens Guake, but pressing it again doesn't close Guake. Changing the key doesn't resolve the problem. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages guake depends on: ii gconf2 3.2.6-3 ii libatk1.0-0 2.14.0-1 ii libc62.19-18 ii libcairo21.14.0-2.1 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-4 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-0 2.24.25-3 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-01.36.8-3 ii libpython2.7 2.7.9-2 ii libx11-6 2:1.6.2-3 ii notification-daemon 0.7.6-2 ii python 2.7.9-1 ii python-dbus 1.2.0-2+b3 ii python-gconf 2.28.1+dfsg-1.1 ii python-glade22.24.0-4 ii python-notify0.1.1-4 ii python-vte 1:0.28.2-5 ii python-xdg 0.25-4 pn python2.7:anynone guake recommends no packages. guake 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#783858: Unable to start from a symlink (like x-www-browser)
❦ 30 avril 2015 15:57 -0600, Bob Proulx b...@proulx.com : /usr/bin/x-www-browser: 95: exec: /usr/lib/chromium/x-www-browser: not found This reads like a broken symlink. Can you trace through them and see where it is broken? No, it is not. $ readlink -f /usr/bin/x-www-browser /usr/bin/chromium The problem is in the chromium wrapper script: APPNAME=`basename $0` exec $LIBDIR/$APPNAME $CHROMIUM_FLAGS $@ Previously, APPNAME was set to chromium. -- What I tell you three times is true. -- Lewis Carroll signature.asc Description: PGP signature
Bug#783655: www.debian.org: addition of ppc64el page to ports
On Wed, Apr 29, 2015 at 3:07 AM, Fernando Seiti Furusato wrote: With ppc64el support included on Debian jessie, debian.org pages that contain information regarding architectures need to be updated. I have created a patch that adds a new directory with an index.wml to ports. For most other ports, the port names for a family of ports all redirect to a single page, for example amrhf/arm64/armel all redirect to the arm page. I wonder if that would be appropriate for powerpc/ppc64el/powerpcspe? I would recommend not hard-coding the list of porterbox names, that sort of information is liable to get out of date. Indeed, there is also plummer.d.o now in addition to pastel.d.n. -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783905: phpmyadmin: open_basedir restriction - file (doc/html/index/html) is not within the allowed paths
Package: phpmyadmin Version: 4:4.4.4-1 Severity: normal Dear Maintainer, * What led up to the situation? phpmyadmin was upgraded to 4.4.4-1. When phpmyadmin was called in the browser, an error was displayed: Warning in ./libraries/Util.class.php#516 file_exists(): open_basedir restriction in effect. File(doc/html/index.html) is not within the allowed path(s): (/usr/share/phpmyadmin/:/etc/phpmyadmin/:/var/lib/phpmyadmin/:/usr/share/php/php-gettext/:/usr/share/javascript/:/usr/share/php/tcpdf/) * What exactly did you do (or not do) that was effective (or ineffective)? Modifying the open_basedir chain in /etc/phpmyadmin/apache.conf was the key to solving the bug. I added this path to the open_basedir: /usr/shared/doc/phpmyadmin. If this is the new normal path for phpmyadmin doc, I suggest that the default config file is modified accordingly. * What was the outcome of this action? After restarting Apache, the error disappeared. -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages phpmyadmin depends on: ii dbconfig-common1.8.47+nmu3 ii debconf [debconf-2.0] 1.5.56 ii libapache2-mod-php55.6.7+dfsg-1 ii libjs-sphinxdoc1.2.3+dfsg-1 ii perl 5.20.2-4 ii php-gettext1.0.11-1 ii php5 5.6.7+dfsg-1 ii php5-json 1.3.6-1 ii php5-mcrypt5.6.7+dfsg-1 ii php5-mysql 5.6.7+dfsg-1 ii ucf3.0030 Versions of packages phpmyadmin recommends: ii apache2 [httpd] 2.4.12-1 ii mariadb-client-10.0 [virtual-mysql-client] 10.0.17-1 ii php-tcpdf 6.0.093+dfsg-1 ii php5-gd 5.6.7+dfsg-1 Versions of packages phpmyadmin suggests: ii chromium [www-browser] 42.0.2311.135-1 ii iceweasel [www-browser] 36.0.1-2 ii mariadb-server-10.0 [virtual-mysql-server] 10.0.17-1 ii w3m [www-browser] 0.5.3-20 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783683: cron started with -f (foreground), killing processes on restart
Control: severity -1 important Hi, To solve your problem, you can add KillMode=process into the [Service] stanza of cron.service. I guess this is an important bug that should be solved in Debian 8.1 due soon. --- http://www.freedesktop.org/software/systemd/man/systemd.kill.html | If set to control-group, all remaining processes in the control group of this unit will be killed on unit stop | If set to process, only the main process itself is killed. | Defaults to control-group. Other distro's do that too https://git.fedorahosted.org/cgit/cronie.git/tree/contrib/cronie.systemd http://arch-general.archlinux.narkive.com/FcUpb8Nw/protect-a-cron-job-from-systemd (not Debian) http://anonscm.debian.org/cgit/pkg-cron/pkg-cron.git/tree/debian/cron.service Alexandre Detiste -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783904: dh-linktree: fails on invalid actions
Package: dh-linktree
Version: 0.4
Severity: wishlist
Tags: patch
I think it would be better if dh-linktree would not fail on invaid actions.
dh-linktree functionality may be extended to support new experimental actions
or additional actions may be used by some hypothetical alternative tools that
understand .linktree format.
Perhaps it could be useful to warn about unknown actions but continue to
process known ones. The change is trivial:
--- a/dh_linktree
+++ b/dh_linktree
@@ -176,9 +176,9 @@
while (@srclinks) {
my $action=shift @srclinks;
my $src=File::Spec-canonpath(shift @srclinks);
my $dest=File::Spec-canonpath(shift @srclinks);
- error(invalid action '$action')
+ warning(invalid action '$action')
if $action !~ /^(embed|replace|deduplicate)$/;
if (! -l /$src and -d _) {
find(sub {
return if -d and ! -l;
Thank you.
--
Cheers,
Dmitry Smirnov
GPG key : 4096R/53968D1B
---
You have enemies? Good. That means you've stood up for something,
sometime in your life.
-- Victor Hugo, Villemain, 1845
(often misattributed to Winston Churchill)
signature.asc
Description: This is a digitally signed message part.
Bug#783858: Unable to start from a symlink (like x-www-browser)
You are correct. The update was slower to reach my Sid system. I now confirm seeing the same problem and agree completely with your analsys of it. Sorry for the distraction. Bob signature.asc Description: Digital signature
Bug#778799: gcc-doc: gcc.info not viewable in Emacs
On Fri, May 01, 2015 at 02:49:59AM -0400, GUO Yixuan wrote: Hi, Thanks for your report. On Fri, Feb 20, 2015 at 12:09:53PM +1100, Kevin Ryde wrote: Package: gcc-doc Version: 5:4.9.1-3 Severity: normal File: /usr/share/info/gcc.info.gz With recent emacs-lucid 24.4+1-4.1, opening the gcc.info file C-h i g (gcc) Ret = No such node or anchor: Top In see this empty type gcc.info is accepted by the standalone info program, but it doesn't seem to work in emacs. I've tried the same input sequence with info, and it doesn't work, either, with an error message Cannot find node `Top'. So info and the info reader inside emacs have the same behavior here. The reason why I've switched to direntry stub instead of symlinks for /usr/share/info/gcc.info.gz: $ info gcc With symlinks shows 10 'gcov'--a Test Coverage Program in gcc-4.8.info, while gcc-4.9 is the symlinked default version. With direntry stub shows the top node in gcc-4.9.info. The drawback is that with direntry stubs, there's no (gcc) top nodes, only (gcc-4.9) top nodes, etc. However, it doesn't seem to be a good idea to revert to symlinks. Any patches are welcome. Here is a (somehow awkward) patch. Feel free to try and see if it works. http://anonscm.debian.org/cgit/users/yixuan-guest/gcc-doc-defaults.git/commit/?h=bothid=fb0641573231c3d50822d03ff003a6f861666346 Regards, Yixuan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773768: jenkins reproduces this issue
Hi, also, I still cannot reproduce the issue. I ran $ apt-get install $(echo autopoint binutils binutils-multiarch bzip2 cpp cpp-4.9 debbindiff file fontconfig-config fontforge-extras fonts-dejavu-core gcc gcc-4.9 gcj-4.9-jre-lib gettext gettext-base ghc iso-codes libalgorithm-c3-perl libarchive-extract-perl libasan0 libasan1 libasound2 libasound2-data libasprintf-dev libasprintf0c2 libatomic1 libbsd-dev libbsd0 libc-dev-bin libc6-dev libcairo2 libcgi-fast-perl libcgi-pm-perl libcilkrts5 libclass-c3-perl libclass-c3-xs-perl libcloog-isl4 libcpan-meta-perl libcroco3 libdata-optlist-perl libdata-section-perl libelf1 libexpat1 libfcgi-perl libffi-dev libfontconfig1 libfreetype6 libgcc-4.8-dev libgcc-4.9-dev libgcj-common libgcj15 libgettextpo-dev libgettextpo0 libglib2.0-0 libglib2.0-data libgmp-dev libgmpxx4ldbl libgomp1 libisl13 libitm1 libjbig0 libjpeg62-turbo liblcms2-2 liblog-message-perl liblog-message-simple-perl liblsan0 liblua5.2-0 liblzo2-2 libmagic1 libmodule-build-perl libmodule-pluggable-perl libmodule-signature-perl libmpc3 libmpfr4 libmro-compat-perl libncurses5-dev libnspr4 libnss3 libopenjpeg5 libpackage-constants-perl libparams-util-perl libpixman-1-0 libpng12-0 libpod-latex-perl libpod-readme-perl libpoppler46 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libquadmath0 libregexp-common-perl librpm3 librpmbuild3 librpmio3 librpmsign1 libsoftware-license-perl libsqlite3-0 libstdc++-4.8-dev libsub-exporter-perl libsub-install-perl libterm-ui-perl libtext-soundex-perl libtext-template-perl libtiff5 libtinfo-dev libtsan0 libubsan0 libunistring0 libx11-6 libx11-data libxau6 libxcb-render0 libxcb-shm0 libxcb1 libxdmcp6 libxext6 libxml2 libxrender1 linux-libc-dev locales-all lsb-release manpages-dev mime-support pdftk perl perl-modules poppler-data poppler-utils python python-apt python-apt-common python-chardet python-debian python-magic python-minimal python-pkg-resources python-rpm python-six python2.7 python2.7-minimal rename rpm-common rpm2cpio sgml-base shared-mime-info sng squashfs-tools ucf unzip xdg-user-dirs xml-core xz-utils ghc ) in my sid chroot, to simulate the jenkins job, but it went through without a hitch. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#783906: dh-linktree: action replace may be insufficient
Package: dh-linktree Version: 0.4 Severity: normal Action replace creates links to missing files in destination but ignores missing folders. replace action is meant to ensure compatibility with future versions of replaced libraries but its counter-intuitive implementation sometimes produces invalid results. Consider example where dh-linktree replaces bundled library with newer version where a new folder (e.g. includes) was introduced. If such folder is missing in the original source tree dh-linktree will not link it. This behaviour is too fragile and doomed to fail on harmless changes. Another example is repackaged orig tars: my package ship ckeditor and other components that I have to drop using Files-Excluded. Then I want to use dh- linktree to re-create directory structure from known package but again dh- linktree is not helpful because I can not instruct it to re-create the whole tree structure if it is not already exist in destination. I think it would be nice to extend replace action to add not only missing files but also missing directories as well. Alternatively a new add-replace target with this behaviour can be made to avoid changes to behaviour of existing targets for full compatibility. Thank you. -- Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B --- Success consists of going from failure to failure without loss of enthusiasm. -- Winston Churchill signature.asc Description: This is a digitally signed message part.
Bug#783907: upgrade-reports: apt-get upgrade ends up in an dist-upgrade from wheezy to, jessie
Package: upgrade-reports Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, sorry - forgot to add the sources.list file in the first bug-report. Here are the entries of the sources.list file: deb http://ftp.de.debian.org/debian stable main contrib non-free deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free deb http://security.debian.org/ wheezy/updates main contrib non-free deb http://http.debian.net/debian wheezy-backports main Maybe the whezzy-backports entry at the end of the list caused the problem? * What led up to the situation? Try to update a wheezy system (7.8). * What exactly did you do (or not do) that was effective (or ineffective)? I made a apt-get update and then apt-get upgrade Programm asked to download about 250 MB of data and to proceed. Confirmed with Y * What was the outcome of this action? Download was proceeded and but instead of apt-get upgrade apt-get dist-upgrade was done. System was jessie (8) after ending. System was bootable and a bunch of packages where not updated. * What outcome did you expect instead? I expected a normal upgrade of wheezy. In /etc/apt/sources.list all entries are still for wheezy. I marked this bug-report critical because if there is something serios about wheezy/jessie-repos it maybe affect many people by dist-upgrading unexpecely. If this can not be confirmed please downgrade this report to normal. Regards, Werner -- System Information: Debian Release: 7.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- WS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778799: gcc-doc: gcc.info not viewable in Emacs
Hi, Thanks for your report. On Fri, Feb 20, 2015 at 12:09:53PM +1100, Kevin Ryde wrote: Package: gcc-doc Version: 5:4.9.1-3 Severity: normal File: /usr/share/info/gcc.info.gz With recent emacs-lucid 24.4+1-4.1, opening the gcc.info file C-h i g (gcc) Ret = No such node or anchor: Top In see this empty type gcc.info is accepted by the standalone info program, but it doesn't seem to work in emacs. I've tried the same input sequence with info, and it doesn't work, either, with an error message Cannot find node `Top'. So info and the info reader inside emacs have the same behavior here. The reason why I've switched to direntry stub instead of symlinks for /usr/share/info/gcc.info.gz: $ info gcc With symlinks shows 10 'gcov'--a Test Coverage Program in gcc-4.8.info, while gcc-4.9 is the symlinked default version. With direntry stub shows the top node in gcc-4.9.info. The drawback is that with direntry stubs, there's no (gcc) top nodes, only (gcc-4.9) top nodes, etc. However, it doesn't seem to be a good idea to revert to symlinks. Any patches are welcome. Regards, Yixuan -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages gcc-doc depends on: ii gcc-4.9-doc 4.9.1-3 gcc-doc recommends no packages. gcc-doc 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#773768: jenkins reproduces this issue
[Re-sending; The debian mail system _still_ rejects mail from mail@ addresses] Hi, it seems as if during the invocation of the postinst script, the shares libraries (which are in the package, and referenced via rpath) are not available. Do we need to run ld.update or something like that? I'm not an expert on linker issues and their interactions with dpkg. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#783907: upgrade-reports: apt-get upgrade ends up in an dist-upgrade from wheezy to, jessie
Control: tags -1 -d-i +moreinfo On 2015-05-01 7:37, Werner Scharinger wrote: Package: upgrade-reports Here are the entries of the sources.list file: deb http://ftp.de.debian.org/debian stable main contrib non-free deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free deb http://security.debian.org/ wheezy/updates main contrib non-free deb http://http.debian.net/debian wheezy-backports main [...] I expected a normal upgrade of wheezy. In /etc/apt/sources.list all entries are still for wheezy. No, they're not. The first entry in your list (quoted above) clearly says: deb http://ftp.de.debian.org/debian stable main contrib non-free wheezy is not stable; jessie is. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783908: new cpp conflicts break architecture bootstrap
Package: cpp Version: 4:4.9.2-3 Severity: serious User: helm...@debian.org Usertags: rebootstrap The new cpp conflicts break architecture bootstrap. See for instance: https://jenkins.debian.net/job/rebootstrap_mips_gcc5_supported/9/console The collateral damage induced by these conflicts simply is too much. Please revert. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783833: ITP: python-obitools -- set of programs specifically designed for analyzing NGS data in a DNA metabarcoding contex
On Fri, May 01, 2015 at 10:38:57AM +, olivier sallou wrote: Right, those are cmd line tools. Should indeed be renamed. Please ping me if you do so since I'd like to add this to the Debian Med tasks with the proper binary package name. Anyway, there are multiple discussions on debian devel, because it is not python3 compatible and should not be uploaded if upstream does not plan to go to python3 I may have a look to make it compatible but honestly i am not an expert in python. Package may finally never go to Debian. I personally would not see it that drastically. As long there is some Python 2 interpreter in Debian a package should be allowed to go in. Once this is about to be removed the packages depending from it could be removed. Meanwhile several upstreams will be convinced that they can't stick to Python 2. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783964: gnome-screenshot: Spurious triggers of activity menu while validating screenshot region
Package: gnome-screenshot Version: 3.14.0-1 Severity: normal Dear Maintainer, On my fresh defaut install of Debian 8 with dual monitor setup on ATI card, I have pseudo random problem while trying to screenshot a region of my main screen. I trigger gnome-screenshot by pressing Ctrl+Alt+Printscreen, draw a region from upper-left corner to bottom-right. Sometimes the region is the right one and every goes ok, sometime the region start at position that is not the cursor one (may be a x==0 on current screen ?) then Activity menu is trggered then the screenshot is taken but not contains what I want to screenshot. There is also stange region drawing when going bottom without any x variation. Seems tru in the reverse : moving on x axis without variying on y. 2 videos for illustrating the whole fuck :) http://www.pouzenc.fr/misc/tmp/gnome-screenshot-triggers-activity-menu.webm http://www.pouzenc.fr/misc/tmp/gnome-screenshot-triggers-strange-rects.webm I don't know how to report it properly upstream and if gnome-screenshot is the root source of the problem. Cheers, Ludovic -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-screenshot depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii libc62.19-18 ii libcairo21.14.0-2.1 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 gnome-screenshot recommends no packages. gnome-screenshot 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#783909: libgphoto2-2-dev missing for requested tests
Hi Emilio, Am Freitag, den 01.05.2015, 17:58 +0200 schrieb Jörg Frings-Fürst: Hi Emilio, Am Freitag, den 01.05.2015, 17:06 +0200 schrieb Emilio Pozuelo Monfort: On 01/05/15 15:20, Jörg Frings-Fürst wrote: Hello Emilio, [...] Sorry but I don't see how that makes it a libgphoto bug. libgphoto2-2-dev wasn't in libgphoto2?? Which isn't a bug, but an intended change. You have to update your dependency to the new package name... Have I once claimed that I had it not done? But piuparts need for testing the last version installable. And there I can change anything. And it was nice to have a transitional package[1] also in sid/stretch. CU Jörg [1] https://wiki.debian.org/Renaming_a_Package -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#783965: libdbix-safe-perl: Unneeded Build-Depends on libmodule-signature-perl
Source: libdbix-safe-perl Version: 1.2.5-1 Severity: normal Hi libdbix-safe-perl has a Build-Depends on libmodule-signature-perl (= 0.50). But Module::Signature and cpansign -v is only mentioned in the SIGNATURE file in the explanation how to verify the distribution. cpansign and Module::Signature are not used during the build itself. Regards, Salvatore -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-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 Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768112: slurm-client: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/sinfo
Control: reassign 768112 slurm-llnl,sinfo Control: found 768112 slurm-llnl/14.03.9-5 Control: found 768112 sinfo/0.0.47-3 Control: tags 768112 + sid stretch On Wed, Nov 05, 2014 at 03:27:38AM +0100, Andreas Beckmann a...@debian.org wrote: Selecting previously unselected package slurm-client. Unpacking slurm-client (from .../slurm-client_14.03.9-3_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/slurm-client_14.03.9-3_amd64.deb (--unpack): trying to overwrite '/usr/bin/sinfo', which is also in package sinfo 0.0.46-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/slurm-client_14.03.9-3_amd64.deb This bug applies to both slurm-llnl and sinfo. Regards, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783966: AttributeError: 'module' object has no attribute 'add_metaclass'
Package: reportbug Version: 6.6.3 Severity: important Dear Maintainer, Since I've upgraded to jessie, I cannot use querybts / reportbug. I'v got a pythin backtrace : ~ reportbug 1 Traceback (most recent call last): File /usr/bin/reportbug, line 38, in module from reportbug import utils File /usr/lib/python2.7/dist-packages/reportbug/utils.py, line 70, in module import debbugs File /usr/lib/python2.7/dist-packages/reportbug/debbugs.py, line 43, in module import checkversions File /usr/lib/python2.7/dist-packages/reportbug/checkversions.py, line 39, in module from debian.deb822 import Deb822 File /usr/lib/python2.7/dist-packages/debian/deb822.py, line 1481, in module @six.add_metaclass(_ClassInitMeta) AttributeError: 'module' object has no attribute 'add_metaclass' It's working here on my sid PC with the same reportbug version. The same python-debian version too. So, As I also had some problems with python2.7 (bug #783738). -- Package-specific info: ** Environment settings: DEBEMAIL=gilles.mocel...@nuagelibre.org DEBFULLNAME=Gilles Mocellin -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt 1.0.9.9 ii python2.7.9-1 ii python-reportbug 6.6.3 pn python:anynone reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail none ii debconf-utils 1.5.56 ii debsums 2.1 pn dlocate none ii emacs23-bin-common 23.4+1-4.1+b1 ii emacs24-bin-common 24.4+1-5 ii file1:5.22+15-2 ii gnupg 1.4.18-7 ii postfix [mail-transport-agent] 2.11.3-1 ii python-gtk2 2.24.0-4 pn python-gtkspell none pn python-urwidnone ii python-vte 1:0.28.2-5 ii xdg-utils 1.1.0~rc1+git20111210-7.4 Versions of packages python-reportbug depends on: ii apt 1.0.9.9 ii python-debian 0.1.27 ii python-debianbts 1.12 pn python:anynone python-reportbug 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#783962: Ciderwebmail doesn't appear to automatically check for new messages
Package: ciderwebmail Version: 1.05-5 I've installed ciderwebmail from jessie. (Thanks for the work packaging this webmail app). It is working well, for the most part. I like it. One thing I've noticed is that ciderwebmail doesn't appear to detect new messages. The count of new messages doesn't seem to change until I click on the inbox in the left navigation bar, forcing it to update. If I leave the program untouched for a long time, my MTA delivers new messages into my inbox, but ciderwebmail's new message count doesn't change. I'm not very good with perl. But it looks like ciderwebmail is making use of linux::inotify2. Not sure if this could be used to update itself to show the presence of new messages. My imap server is running dovecot (wheezy) with maildir. Kernel: 3.14.24 (vanilla). C library: 2.19-18 perl: 5.20.2-3 Thanks, Bryan
Bug#783963: tracker-extract runs concurrently with updatedb.mlocate when opening Gnome session
Package: tracker Version: 1.2.4-2 Severity: normal Dear Maintainer, Right after booting and logging into a fresh default install of Debian 8 with a good quantity of files imported into ~/Documents/ my system came very slow. This seems to happens roughly on each boot. Opening a terminal takes 2 or 3 seconds. top says : PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2156 lpouzenc 39 19 1723740 89952 32812 D 16,6 2,2 0:59.10 tracker-extract 2159 lpouzenc 20 0 479944 33744 S 12,3 0,8 1:25.00 tracker-store 2233 lpouzenc 20 0 130956 6284 5348 S 1,3 0,2 0:07.84 gvfsd-metadata 2439 lpouzenc 20 0 421344 30744 4 S 1,3 0,8 0:02.05 gnome-terminal- 2896 root 20 06904 2460 1856 D 1,3 0,1 0:04.77 updatedb.mlocat 812 root 20 0 250200 45012 23656 S 0,7 1,1 0:05.02 Xorg updatedb.mlocate eats IO, tracker-extract too, and when started together everything goes slow, heads of my HDD go crazy. Please try to see what you could do for preventing multiples file crawler programs to be ran concurrently. If you cannot make simple things, around that just defer a bit tracker update upon session start. À là Windows (tm). -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tracker depends on: ii dbus 1.8.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii libc62.19-18 ii libexempi3 2.2.1-2 ii libglib2.0-0 2.42.1-1 ii libtracker-control-1.0-0 1.2.4-2 ii libtracker-sparql-1.0-0 1.2.4-2 ii shared-mime-info 1.3-1 Versions of packages tracker recommends: ii tracker-gui 1.2.4-2 ii tracker-miner-fs 1.2.4-2 ii tracker-utils 1.2.4-2 tracker 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#782515: [PATCH stable 3.10-3.16] tcp: Fix crash in TCP Fast Open
On Wed, 2015-04-15 at 19:00 +0100, Ben Hutchings wrote:
Commit 355a901e6cf1 (tcp: make connect() mem charging friendly)
changed tcp_send_syn_data() to perform an open-coded copy of the 'syn'
skb rather than using skb_copy_expand().
The open-coded copy does not cover the skb_shared_info::gso_segs
field, so in the new skb it is left set to 0. When this commit was
backported into stable branches between 3.10.y and 3.16.7-ckty
inclusive, it triggered the BUG() in tcp_transmit_skb().
Since Linux 3.18 the GSO segment count is kept in the
tcp_skb_cb::tcp_gso_segs field and tcp_send_syn_data() does copy the
tcp_skb_cb structure to the new skb, so mainline and newer stable
branches are not affected.
Set skb_shared_info::gso_segs to the correct value of 1.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
Queued for 3.13-stable. Thanks very much, Ben!
-Kamal
---
net/ipv4/tcp_output.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
index d5457e4..1ea0a07 100644
--- a/net/ipv4/tcp_output.c
+++ b/net/ipv4/tcp_output.c
@@ -2992,6 +2992,7 @@ static int tcp_send_syn_data(struct sock *sk, struct
sk_buff *syn)
goto fallback;
syn_data-ip_summed = CHECKSUM_PARTIAL;
memcpy(syn_data-cb, syn-cb, sizeof(syn-cb));
+ skb_shinfo(syn_data)-gso_segs = 1;
if (unlikely(memcpy_fromiovecend(skb_put(syn_data, space),
fo-data-msg_iov, 0, space))) {
kfree_skb(syn_data);
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782492: FTCBFS for mips* architectures: invokes non-existent $triplet-$triplet-gcc
Hi Kurt, On Mon, Apr 13, 2015 at 06:53:32AM +0200, Helmut Grohne wrote: openssl currently cannot be cross built for mips* architectures, because it preprends the architecture triplet to the compiler twice. Example failure: Is there a reason for why you couldn't apply the patch? I saw you updated openssl but apparently this patch fell through the cracks. Thanks for considering Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783958: linux-image-3.16.0-4-amd64: iptables fails to work with jessie's kernel
Control: tag -1 moreinfo On Fri, 2015-05-01 at 11:24 -0400, westlake wrote: Package: linux-image-3.16.0-4-amd64 Version: 3.16.7-ckt9-3~deb8u1 Severity: important A simple test with iptables against Jessie's default kernel fails to work, but using a custom kernel not from repositories and iptables works. A simple test is done allowing one match rule, and it can immediately be seen there is a problem with either iptables or Jessie's default kernel of 3.16.0-4-amd64. There is not a general problem, as yours is the first report I've seen of any problems with iptables. eg, iptables -I INPUT -p tcp --dport 22 -j ACCEPT iptables -P INPUT DROP [...] Please send the output of the following commands on your system after this: iptables -L -v -n lsmod | grep -E 'ipt|nf[t_]' Ben. -- Ben Hutchings It is easier to write an incorrect program than to understand a correct one. signature.asc Description: This is a digitally signed message part
Bug#748400: Fixed?
Thanks for submitting this upstream! On jessie I'm not experiencing this bug anymore (checked with gnuplot 4 and 5). So probably fixed? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783967: fortunes-it: error in quote
Package: fortunes-it Version: 1.99-3 Severity: minor Tags: newcomer l10n Dear Maintainer, in Luttazzi file, Lacome should be Lancôme -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (700, 'stable'), (500, 'stable-updates'), (500, 'proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fortunes-it depends on: ii fortune-mod 1:1.99.1-7 fortunes-it recommends no packages. Versions of packages fortunes-it suggests: ii fortunes-it-off 1.99-3 -- 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#783899: liblog-any-perl, liblog-any-adapter-perl: File conflict when being installed together
On Fri, 01 May 2015 16:47:22 +0200, Jonas Smedegaard wrote:
I guess we need:
- a versioned Breaks+Replaces
- a virtual dummy package (which will remove src:liblog-any-adapter-perl)
- and then bugs/fixes in all rdeps (some unfortunately versioned, so
a Provides wouldn't buy us much):
https://codesearch.debian.net/results/liblog-any-adapter-perl%20path%3Adebian%2Fcontrol/page_0
where the fix probably is liblog-any-perl (= 1.00) |
liblog-any-adapter-perl [(= 0.11)]
I now update libcatmandu-perl which simplifies dependencies (needs
liblog-any-* 1.03 now).
After that I will relax liblog-any-adapter-screencoloredlevel-perl to
have unversioned dependency: 0.11 is satisfied even in oldstable.
Thanks!
If someone does same for liblog-any-adapter-callback-perl
Done.
I believe no
other versioned build-dependencies are left, and we can have
liblog-any-perl provide liblog-any-adapter-perl.
Excellent. So this should be enough in liblog-any-perl?
#v+
--- a/debian/control
+++ b/debian/control
@@ -17,6 +17,9 @@ Package: liblog-any-perl
Architecture: all
Depends: ${misc:Depends},
${perl:Depends}
+Breaks: liblog-any-adapter-perl
+Replaces: liblog-any-adapter-perl
+Provides: liblog-any-adapter-perl
Description: Perl module to log messages safely and efficiently
Log::Any allows CPAN modules to safely and efficiently log messages, while
letting the application choose (or decline to choose) a logging mechanism
#v-
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Bettina Wegner: Die Traurigkeiten
signature.asc
Description: Digital Signature
Bug#783106: lxc container does not start automatically
On Thu, Apr 30, 2015 at 07:08:13PM +0200, Daniel Baumann wrote: On 04/30/15 08:50, Guido Günther wrote: * lxc is lacking error reporting if you start it via initscript and have no error-logging, then indeed you don't see any error. * doesn't wait for libvirt to come up - it's debatable wether this would be a good thing no; both the initscript and the systemd unit have network as a depends - there's nothing more we can do on the lxc (or any other service that requires network to be up) side. I would totally agree that libvirt has a bug if the lxc container would be libvirt managed (via lxc://) but this isn't the case. right; but the user is abusing libvirt here to setup his bridge, rather than to configure it normally. it's up to you though if you want to 'allow' users to use libvirt like that or not. We we won't lose anything if we add a Should-Start: libvirtd, do we? Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783968: sqlite3: CVE-2015-3414 CVE-2015-3415 CVE-2015-3416
Source: sqlite3 Version: 3.8.7.4-1 Severity: important Tags: security upstream fixed-upstream Hi, the following vulnerabilities were published for sqlite3. CVE-2015-3414[0]: | SQLite before 3.8.9 does not properly implement the dequoting of | collation-sequence names, which allows context-dependent attackers to | cause a denial of service (uninitialized memory access and application | crash) or possibly have unspecified other impact via a crafted COLLATE | clause, as demonstrated by COLLATE at the end of a SELECT | statement. CVE-2015-3415[1]: | The sqlite3VdbeExec function in vdbe.c in SQLite before 3.8.9 does not | properly implement comparison operators, which allows | context-dependent attackers to cause a denial of service (invalid free | operation) or possibly have unspecified other impact via a crafted | CHECK clause, as demonstrated by CHECK(0amp;Ogt;O) in a CREATE TABLE | statement. CVE-2015-3416[2]: | The sqlite3VXPrintf function in printf.c in SQLite before 3.8.9 does | not properly handle precision and width values during floating-point | conversions, which allows context-dependent attackers to cause a | denial of service (integer overflow and stack-based buffer overflow) | or possibly have unspecified other impact via large integers in a | crafted printf function call in a SELECT statement. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-3414 [1] https://security-tracker.debian.org/tracker/CVE-2015-3415 [2] https://security-tracker.debian.org/tracker/CVE-2015-3416 Please adjust the affected versions in the BTS as needed. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783899: liblog-any-perl, liblog-any-adapter-perl: File conflict when being installed together
On Fri, 01 May 2015 20:28:32 +0200, Jonas Smedegaard wrote:
Excellent. So this should be enough in liblog-any-perl?
#v+
--- a/debian/control
+++ b/debian/control
@@ -17,6 +17,9 @@ Package: liblog-any-perl
Architecture: all
Depends: ${misc:Depends},
${perl:Depends}
+Breaks: liblog-any-adapter-perl
+Replaces: liblog-any-adapter-perl
+Provides: liblog-any-adapter-perl
Description: Perl module to log messages safely and efficiently
Log::Any allows CPAN modules to safely and efficiently log messages, while
letting the application choose (or decline to choose) a logging mechanism
#v-
I believe so, yes.
Ok ...
...but even if I believe it technically will work, I suspect unversioned
Breaks is unorthodox and might trigger lintian warnings or worse.
lintian doesn't complain but I'm also not really comfortable with it.
To be on the safe side a versioned Breaks should work just as well
(since we do not expect a newer liblog-any-adapter-perl to ever emerge)
and follow Policy recommendations more closely.
Good point, done now.
Thanks for your help!
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Andrew Lloyd Webber Tim Rice
signature.asc
Description: Digital Signature
Bug#697521: libstdc++6 built from gcc-4.7 missing some symbols on armel
clone 697521 -1 retitle -1 libstdc++6 built from gcc-4.9 missing some symbols on armel found -1 gcc-4.9/4.9.2-10 thanks Hi, I think gcc-4.9 ist still missing at least std::exception_ptr and std::rethrow_exception on armel, see: https://buildd.debian.org/status/fetch.php?pkg=gimagereaderarch=armelver=3.0.1-1stamp=1430241015 Best, Philip signature.asc Description: OpenPGP digital signature
