Bug#776748: (pre-approval) unblock: libxml2/2.9.1+dfsg1-5 (via t-p-u)
On Tue, Feb 3, 2015 at 02:23:20 +0800, Aron Xu wrote: On Tue, Feb 3, 2015 at 12:02 AM, Adam D. Barratt a...@adam-barratt.org.uk wrote: On 2015-02-02 6:37, Aron Xu wrote: On Mon, Feb 2, 2015 at 1:13 AM, Adam D. Barratt a...@adam-barratt.org.uk wrote: Control: tags -1 + moreinfo On Sun, 2015-02-01 at 16:24 +0800, Aron Xu wrote: +libxml2 (2.9.1+dfsg1-5) testing; urgency=medium + + * Add pkg-config to B-D + * Use -O3 for normal builds Could you expand on the rationale for introducing those now? Particularly as neither appears to be mentioned in the changelogs for the uploads to unstable. These are directly picked from the 2.9.2 upload, which stuck for RC bug. At that time the change was quite big (major release) so those aren't documented in very detail but are in the git for quite some time. Well, the changelog wasn't very detailed for 2.9.2 either. :-) I realise that the changes are in the unstable package (I checked that first), I was more interested in the rationale, particularly for the optimisation change. It's more about a changing attitude on speed/space trade of -O2 and -O3, and more and more apps are using -O3 for release build (e.g. CMake default). If release team believe that's not desired in Jessie, I can keep it out of the way. Anything that's not a minimal fix for a RC bug is not desired for jessie at this stage. Cheers, Julien signature.asc Description: Digital signature
Bug#776880: [Pkg-xfce-devel] Bug#776880: lightdm: black border on login screen with multi-monitor configuration with different resolitions
On lun., 2015-02-02 at 22:07 +0200, George Shuklin wrote: Package: lightdm Version: 1.10.3-3 Severity: minor When computer has two or more monitors with different resolition, login screen shows debian logo stretched to size of the smallest available resolition. All area around (on monitor with larger resolution) is black, and looks ugly. Proposal: use jessie color (greeny) for that area or stretch image to largest available resolution. Position of login window will not change, but all process will looks better. Actually this is done by the greeter, so please reassign accordingly. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#776886: swish-e: Search fails with '1000 err: Failed to seek to properties located at...'
Package: swish-e Version: 2.4.7-4 Severity: important Tags: upstream First, I index a fairly small (115) set of files: - $ swish-e -c swish.conf Indexing Data Source: File-System Indexing help/help Indexing help/about Removing very common words... no words removed. Writing main index... Sorting words ... Sorting 2,863 words alphabetically Writing header ... Writing index entries ... Writing word text: Complete Writing word hash: Complete Writing word data: Complete 2,863 unique words indexed. 4 properties sorted. 115 files indexed. 747,811 total bytes. 37,108 total words. Elapsed time: 00:00:00 CPU time: 00:00:00 Indexing done! - swish.conf is: - IndexFile index.swish IndexDir help/help help/about IndexOnly .html UndefinedMetaTags ignore IgnoreWords file: /usr/share/doc/swish-e/examples/conf/stopwords/english.txt FuzzyIndexingMode Stemming_en1 - Searches then consistently fail: - $ swish-e -c swish.conf -f index.swish -w reply # SWISH format: 2.4.7 # Search words: reply # Removed stopwords: # Number of hits: 18 # Search time: 0.000 seconds # Run time: 0.006 seconds 1000 err: Failed to seek to properties located at 3910877067702384 for file number 407 : Invalid argument . - It sounds like this upstream bug: http://dev.swish-e.org/ticket/8 which suggests this patch: http://dev.swish-e.org/changeset/2562 -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages swish-e depends on: ii debconf [debconf-2.0] 1.5.55 ii libc6 2.19-14 ii libpcre32:8.35-3.3 ii libxml2 2.9.2+dfsg1-3 ii perl5.20.1-5 ii perl-base [perlapi-5.20.0] 5.20.1-5 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages swish-e recommends: ii libdate-calc-perl 6.3-1 ii libmime-types-perl 2.09-3 ii libtemplate-perl2.24-1.2+b1 Versions of packages swish-e suggests: pn catdoc none pn hypermail none ii libhtml-parser-perl 3.71-1+b3 pn libmp3-tag-perl none ii libwww-perl 6.08-1 ii poppler-utils [xpdf-utils] 0.26.5-2 pn wv none -- debconf information: * swish-e/configuration-note: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776887: unblock: python-defaults/2.7.8-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-defaults
RC bug fix. The new predepends was discussed on d-devel as required by
policy.
unblock python-defaults/2.7.8-3
diff -Nru python-defaults-2.7.8/debian/changelog python-defaults-2.7.8/debian/changelog
--- python-defaults-2.7.8/debian/changelog 2014-10-24 11:03:31.0 -0400
+++ python-defaults-2.7.8/debian/changelog 2015-02-02 16:13:04.0 -0500
@@ -1,3 +1,10 @@
+python-defaults (2.7.8-3) unstable; urgency=medium
+
+ [ Michael Gilbert ]
+ * Make python-minimal a pre-dependency for python (closes: #769106).
+
+ -- Scott Kitterman sc...@kitterman.com Mon, 02 Feb 2015 16:12:38 -0500
+
python-defaults (2.7.8-2) unstable; urgency=medium
[ Matthias Klose ]
diff -Nru python-defaults-2.7.8/debian/control python-defaults-2.7.8/debian/control
--- python-defaults-2.7.8/debian/control 2014-10-24 11:56:47.0 -0400
+++ python-defaults-2.7.8/debian/control 2015-02-02 16:20:42.0 -0500
@@ -16,7 +16,8 @@
Architecture: any
Multi-Arch: allowed
Priority: standard
-Depends: ${misc:Depends}, python2.7 (= 2.7.8-5~), python-minimal (= ${binary:Version}), libpython-stdlib (= ${binary:Version})
+Pre-Depends: python-minimal (= ${binary:Version})
+Depends: ${misc:Depends}, python2.7 (= 2.7.8-5~), libpython-stdlib (= ${binary:Version})
Suggests: python-doc (= ${binary:Version}), python-tk (= 2.7.8-5~)
Conflicts: python-central ( 0.5.5)
Breaks: update-manager-core ( 0.200.5-2)
diff -Nru python-defaults-2.7.8/debian/control.in python-defaults-2.7.8/debian/control.in
--- python-defaults-2.7.8/debian/control.in 2014-10-24 11:55:21.0 -0400
+++ python-defaults-2.7.8/debian/control.in 2015-02-02 16:12:34.0 -0500
@@ -16,7 +16,8 @@
Architecture: any
Multi-Arch: allowed
Priority: standard
-Depends: ${misc:Depends}, @PVER@ (= @PREVVER@), python-minimal (= ${binary:Version}), libpython-stdlib (= ${binary:Version})
+Pre-Depends: python-minimal (= ${binary:Version})
+Depends: ${misc:Depends}, @PVER@ (= @PREVVER@), libpython-stdlib (= ${binary:Version})
Suggests: python-doc (= ${binary:Version}), python-tk (= @PREVVER@)
Conflicts: python-central ( 0.5.5)
Breaks: update-manager-core ( 0.200.5-2)
Bug#776891: libc6-dev: time_t time(time_t *t) behavior does not conform to specification
Package: libc6-dev
Version: 2.13-38+deb7u3
Severity: normal
Tags: upstream
Dear Maintainer,
* What led up to the situation?
I was writing some short simple example code to demonstrate error handling in
a UNIX environment. I attempted to purposely produce an error by calling the
`time` function with a bad parameter.
* What exactly did you do (or not do) that was effective (or
ineffective)?
See:
http://stackoverflow.com/questions/28286290/linux-system-call-time-is-returning-time-t-14-on-error
I compiled a program with gcc containing this simple code snippet and ran
it:
{
time_t *ptr = (time_t *) 0xabad1dea;
time_t secs = time(ptr);
if (secs == ((time_t) -1)) /* Not caught */
exit(EXIT_FAILURE);
printf(Number of seconds since the Epoch:%lld\n, secs);
printf(It should return ((time_t) -1) on error: %lld\n, (time_t) -1);
perror(Error Message:);
secs = *ptr; /* This *does* segfault */
}
* What was the outcome of this action?
The error condition was not caught. `time` returned -14 when passed
an out-of-bounds address and did not set `errno`.
* What outcome did you expect instead?
The manual (`man 2 time`), POSIX, and the C standard lead me to believe that
time should return -1 and set errno to EFAULT (14). The of the function in
this version of libc is incorrect. I thought someone should know, since this
is sort of a confusing glibc bug.
-- System Information:
Debian Release: 7.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.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
Versions of packages libc6-dev depends on:
ii libc-dev-bin2.13-38+deb7u3
ii libc6 2.13-38+deb7u3
ii linux-libc-dev 3.2.60-1+deb7u3
Versions of packages libc6-dev recommends:
ii gcc [c-compiler] 4:4.7.2-1
ii gcc-4.6 [c-compiler] 4.6.3-14
ii gcc-4.7 [c-compiler] 4.7.2-5
Versions of packages libc6-dev suggests:
pn glibc-doc none
ii manpages-dev 3.44-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#776877: uses ill-defined architecture any-amd64
Looks OK in experimental : https://buildd.debian.org/status/package.php?p=libjpeg-turbosuite=experimental On February 2, 2015 10:20:29 PM GMT+01:00, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Hi Ondrej, i think it was related to a nasm problem on 32bit system back in the early turbo days, probably this one [1]. My guess is that we could try to drop nasm's architecture limitation completely from BD, presuming that latest nasm versions handle things well by now. Mike [1] http://sourceforge.net/p/libjpeg-turbo/bugs/20/ -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976148 GnuPG Key ID 0x25771B13 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de - Original message - Hi Mike, do you have an idea, why nasm is limited just to some architectures? It looks like it's available on all release Debian architectures: https://packages.debian.org/unstable/nasm So it seems there's no reason to have the limit in the place at all. Cheers, Ondrej On Mon, Feb 2, 2015, at 20:50, Helmut Grohne wrote: Source: libjpeg-turbo Version: 1:1.3.1-11 User: helm...@debian.org Usertags: rebootstrap Control: block -1 by 748936 libjpeg-progs uses the ill-defined architecture wildcard any-amd64 in its Build-Depends. apt and dpkg do not agree on its meaning (for details see #748936). For instance on apt would not treat x32 as any-amd64, but dpkg would. This causes x32 builds of libjpeg-turbo to fail at dpkg-checkbuilddeps when installing build-depends with apt-get build-dep. Please use something other than any-amd64. Maybe amd64 kfreebsd-amd64? I mark 748936 as a blocker of this bug to keep track of the instances of the issue. Helmut -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#772543: closed by Sandro Tosi mo...@debian.org (Bug#772543: fixed in python-psutil 2.2.0-1)
Sorry for the late reply, but the improvements indeed seem to have solved the bug. The software is running for some time now in preparation of the release. On Fri, 30 Jan 2015 00:36 Debian Bug Tracking System ow...@bugs.debian.org wrote: This is an automatic notification regarding your Bug report which was filed against the python-psutil package: #772543: python-psutil: severak filehandle leaks It has been closed by Sandro Tosi mo...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Sandro Tosi mo...@debian.org by replying to this email. -- 772543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Forwarded message -- From: Sandro Tosi mo...@debian.org To: 772543-cl...@bugs.debian.org Cc: Date: Thu, 29 Jan 2015 23:33:35 + Subject: Bug#772543: fixed in python-psutil 2.2.0-1 Source: python-psutil Source-Version: 2.2.0-1 We believe that the bug you reported is fixed in the latest version of python-psutil, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 772...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi mo...@debian.org (supplier of updated python-psutil package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 29 Jan 2015 23:25:58 + Source: python-psutil Binary: python-psutil python3-psutil Architecture: source amd64 Version: 2.2.0-1 Distribution: experimental Urgency: medium Maintainer: Sandro Tosi mo...@debian.org Changed-By: Sandro Tosi mo...@debian.org Description: python-psutil - module providing convenience functions for managing processes python3-psutil - module providing convenience functions for managing processes (Py Closes: 772543 Changes: python-psutil (2.2.0-1) experimental; urgency=medium . * New upstream release - fix file descriptors leakage; thanks to Marc Leeman; Closes: #772543 * debian/control - update Homepage to github - bump Standards-Version to 3.9.6 (no changes needed) * debian/rules - update upstream changelog - install README.rst file in doc too Checksums-Sha1: e30f37c494de82fe4bea591f09902dd91fdb155e 2160 python-psutil_2.2.0-1.dsc bc4d6d7641afa2f9619121da5194cba83098341a 223676 python-psutil_2.2.0.orig.tar.gz 037fec6ce12422a2db78ce2f70abb4f7c497ec43 4588 python-psutil_2.2.0-1.debian.tar.xz a0b15e018006b3ad562bcffddcfd2b3da0e85564 122584 python-psutil_2.2.0-1_amd64.deb 482cbd40dbd620ed799e76e87b80295718eb7ce7 60378 python3-psutil_2.2.0-1_amd64.deb Checksums-Sha256: 9d3c25e75198b4a0c9ac0545c910c1c86e949b5681d0f828cec410f4a9228850 2160 python-psutil_2.2.0-1.dsc b15cc9e7cad0991bd1cb806fa90ea85ba3a95d0f1226625ecef993294ad61521 223676 python-psutil_2.2.0.orig.tar.gz e7661b05c695dd3611582cdb4241ceb9fc56e45a90a8b84910c30147757f5c54 4588 python-psutil_2.2.0-1.debian.tar.xz 47a1d3d8c3f855a8538e17cb0fd1a8b124cf52532090af8839490506f1e9fbe2 122584 python-psutil_2.2.0-1_amd64.deb a7a9cd4d2c54d67684a75b8a8b2ccbf663cb5638cbe80109d6e8477375ca180d 60378 python3-psutil_2.2.0-1_amd64.deb Files: 2239ebc94d9dc427bd52cd6d373fe5e6 2160 python optional python-psutil_2.2.0-1.dsc b8f5ce3c47edc5e4491ef05a61387116 223676 python optional python-psutil_2.2.0.orig.tar.gz b5cdc608d189c1b256eb18315b3ab748 4588 python optional python-psutil_2.2.0-1.debian.tar.xz 13a9ed36d3bdef97225cb9db09f82809 122584 python optional python-psutil_2.2.0-1_amd64.deb 1df0cba62dd428c0a02ebb4ca52c14d0 60378 python optional python3-psutil_2.2.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUysIfAAoJEP6NePn+T04Q5pYP/jz/F2KUKYssm3t/ACJRpQ/6 qDtLmT72XO78j1YF8BIOUUX+Y72oOHYNRYa/1ZG/6dy0klmtdtMUG4YR5fIOtrT0 TVjVKfTuIynxp+ULYJx1H0wwXEn5G5WUFW7dysQ+oHKHxuj9TNfyz5Tk2vK0lPGL idLV1R/QSE877OU74xYwNNk6mcPno0R7mnOSCr0SSktyma2q5V67PIRosVxCB61c xBgRppW+RKx2xGIzR84NVUzqGxAfjqxgcApm9NK1mGUkc4/UFf2hP5NPD28WNDKW EpJuJxV6C/ziUwql7xjoRJv8H+IWPIjZCzwoabiTlEBK/TGw3ZDtTOEOXxEqwb7w hZ8Fnn7AScnUST/UQArFd1MzGjm8X8SpbRPdRA7d+SzkCIeEjqn2IUxWZ2tqEVtu 8x95hvPVCmInaA3mvkU4ocvytSnNd308yk209COpLn+j3tNUj/vqG6OSgbLi9pD6 bF1TvcSG04+uA5OGeDcAIKsxscRcJZwPqo6C83FzHYcJm1UD6vZkA7cb6VYzY+Ns MIbQzI8R+32X8OvGlYGTFCHtFwGFtWA5Oslp4vMBnK7QShSZQYu6+ldbxi4xSLvI jASfxyQzDI/6bJQ5wMmylW3D+zR+mRiFfbL6qNQR7ZEXx02IuRxzarvn7AUUYO7+
Bug#583089: Alternatively, suggest package fluid-soundfont-gm
I am not sure what the original reporter meant by integrate with fluid-sound-font-*. But for me, playing MIDI files worked in totem 3.14.0-2 as soon as I had installed the fluid-soundfont-gm package. Maybe totem should suggest this package during installation. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776565: preparing nmu for di-netboot-assistant
Hi, Andreas B. Mundt a...@debian.org (2015-02-02): I have prepared a nmu which I plan to upload tomorrow after having tested the modification once more. (1-day notice is a short timeframe.) Please find the debdiff attached, it consists of Jonas' patch with my modification as well as the activation of the jessie release. If you see any problems with the planned nmu, please rise your hand. It'd be nice to have some description of the changes in the changelog (that's what it's for! ;)) instead of pointers to a bug report thread/discussion. Whatever gets uploaded, please make sure to get that pushed into the repository, or point to a branch/tag somewhere if you can't find anyone to push your changes there. Thanks already. Mraw, KiBi. signature.asc Description: Digital signature
Bug#776888: unblock: git/1:2.1.4-2.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package git/1:2.1.4-2.1. This version of git changes an interest trigger to a interest-noawait, which breaks a trigger cycle (#774607 / #774803). According to jenkins.debian.net, this is our last known actual trigger cycle[1]. Thanks, ~Niels [1] In contrast to the APT/dpkg/dbus trigger issue, which is not caused by a trigger cycle. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776595: Raar probleem met Gnome in Jessie
Contro: tags -1 + patch On Mon, Feb 02, 2015 at 09:41:00PM +0100, Frans Spiesschaert wrote: Ik heb het probleem voorgelegd aan de debian ontwikkelaars van Gnome (https://lists.debian.org/debian-gtk-gnome/2015/02/msg0.html) en het antwoord is dat ze het probleem ernstig genoeg vinden en dus graag een patch krijgen. --- gnome-menus-3.13.3-original/po/nl.po +++ gnome-menus-3.13.3/po/nl.po @@ -92,7 +92,7 @@ #: ../desktop-directories/Utility.directory.in.h:1 msgid Accessories -msgstr Hulpmiddelen +msgstr Accessoires #: ../desktop-directories/Utility.directory.in.h:2 msgid Desktop accessories signature.asc Description: Digital signature
Bug#776889: sg3-utils: /usr/bin/rescan-scsi-bus.sh violates policy 10.4 should directive (includes .sh extension)
Source: sg3-utils Version: 1.39-1 Severity: normal Debian Policy 10.4 (Files/Scripts) notes that: When scripts are installed into a directory in the system PATH, the script name should not include an extension such as .sh or .pl that denotes the scripting language currently used to implement it. sg3-utils includes /usr/bin/rescan-scsi-bus.sh, which violates that recommendation in the policy. Note however, that the package scsitools already includes a command named rescan-scsi-bus under /sbin/rescan-scsi-bus, which would conflict with sg3-utils if rescan-scsi-bus.sh would be renamed to rescan-scsi-bus. Besides being quite confusing, should one happen to install both packages, it turns out that both of these scripts seem to be derived from a common ancestor. Maybe a solution can be found between the package maintainers such that Debian ends up with only one version of that script. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (850, 'testing') 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) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776874: systemd: system auto-resumes when pcspkr module is loaded
control: reassign -1 linux-image-3.16.0-4-amd64 Am 02.02.2015 um 21:26 schrieb Ralf Auer: yes, I get the same result when I manually echo mem. Is there an easy way to re-assign this ticket to the kernel package, or should I file another report and you close this one? I've reassigned the bug report. You might want to follow-up with the exact package version. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#776890: jessie-pu: package tbb/4.2~20140122-1.1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hello, I would like to update the version of libtbb2 in Jessie to match a recent upload in Sid: tbb/4.2~20140122-5 The reasoning being that: * The -1.1 version incorrectly attempts to build for all architectures rather than the ones that can actually build. This was fixed in -5 * There is a bug whereby the i386 architecture package does not build correctly. This was fixed in -2. * There is another bug preventing ppc32 from working correctly (fixed in -4) I have also fixed the unit test logic (fixed in -3), and cleaned up the build logic s.t. the unit tests aren't executed twice (fixed in -4). I didn't notice that build failures were blocking my versions of tbb from getting into Jessie. Many apologies for missing the freeze for Jessie, and landing you with this bugreport. It was complete incompetence on my part. (I'm still learning the ropes of Debian packaging.) Please let me know if you need any information, or would like me to make another upload? Thank you, -- Steve Capper -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765499: Patch to make policy document 32-bit uids
On Sun, Feb 1, 2015 at 23:38:24 +0100, Bill Allombert wrote: On Sat, Jan 31, 2015 at 12:28:22PM -0800, Russ Allbery wrote: Bill Allombert ballo...@debian.org writes: + tag4294967294:/tag + item + p + tt(uid_t)(-2) == (gid_t)(-2)/tt emmust + not/em be used, because it is mistaken for + tt65534/tt prgnnobody/prgn by some + programs. + /p + /item I would instead say: emmust not/em be used, because it is used as the anonymous, unauthenticated user by some NFS implementations. OK I offer an updated patch. Third time's a charm I hope. Seconded. Cheers, Julien signature.asc Description: Digital signature
Bug#776880: lightdm: black border on login screen with multi-monitor configuration with different resolitions
Package: lightdm Version: 1.10.3-3 Severity: minor When computer has two or more monitors with different resolition, login screen shows debian logo stretched to size of the smallest available resolition. All area around (on monitor with larger resolution) is black, and looks ugly. Proposal: use jessie color (greeny) for that area or stretch image to largest available resolution. Position of login window will not change, but all process will looks better. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lightdm depends on: ii adduser3.113+nmu3 ii consolekit 0.4.6-5 ii dbus 1.8.14-1 ii debconf [debconf-2.0] 1.5.55 ii libc6 2.19-14 ii libgcrypt201.6.2-4+b1 ii libglib2.0-0 2.42.1-1 ii libpam-systemd 215-11 ii libpam0g 1.1.8-3.1 ii libxcb11.10-3+b1 ii libxdmcp6 1:1.1.1-1+b1 ii lightdm-gtk-greeter [lightdm-greeter] 1.8.5-2 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+7 Versions of packages lightdm suggests: ii accountsservice 0.6.37-3+b1 ii upower 0.99.1-3.1 -- Configuration Files: /etc/apparmor.d/lightdm-guest-session b51cea1a1248cf9bf45f2e9024c7734f [Errno 2] No such file or directory: u'/etc/apparmor.d/lightdm-guest-session b51cea1a1248cf9bf45f2e9024c7734f' -- debconf information: * shared/default-x-display-manager: lightdm lightdm/daemon_name: /usr/sbin/lightdm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774607: git: diff for NMU version 1:2.1.4-2.1
Niels Thykier wrote: I've prepared an NMU for git (versioned as 1:2.1.4-2.1) and uploaded it to DELAYED/2. Thanks. Could you bump it to DELAYED/0? Regards, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776874: systemd: system auto-resumes when pcspkr module is loaded
yes, I get the same result when I manually echo mem. Is there an easy way to re-assign this ticket to the kernel package, or should I file another report and you close this one? Thanks! smime.p7s Description: S/MIME Cryptographic Signature
Bug#776885: RFS: manuel/1.8.0-1 [ITP] -- Python library for documented tests
Package: sponsorship-requests Severity: wishlist Hi, I'm looking for a sponsor for my package of Manuel 1.8.0 [1]. It builds those binary packages: python-manuel - Python library for testable documents and documented tests python3-manuel - Python3 library for testable documents and documented tests Mentors upload: http://mentors.debian.net/package/manuel http://mentors.debian.net/debian/pool/main/m/manuel/manuel_1.8.0-1.dsc Buildlog: http://www.danielstender.com/buildlogs/manuel_1.8.0-1_amd64-20150202-2204.build I've made everything ready for a injection into the DPMT repository (SVN fields and Uploaders present). Thank you very much, Daniel Stender [1] https://pypi.python.org/pypi/manuel/ -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776877: uses ill-defined architecture any-amd64
Source: libjpeg-turbo Version: 1:1.3.1-11 User: helm...@debian.org Usertags: rebootstrap Control: block -1 by 748936 libjpeg-progs uses the ill-defined architecture wildcard any-amd64 in its Build-Depends. apt and dpkg do not agree on its meaning (for details see #748936). For instance on apt would not treat x32 as any-amd64, but dpkg would. This causes x32 builds of libjpeg-turbo to fail at dpkg-checkbuilddeps when installing build-depends with apt-get build-dep. Please use something other than any-amd64. Maybe amd64 kfreebsd-amd64? I mark 748936 as a blocker of this bug to keep track of the instances of the issue. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776876: daemontools: please make the build reproducible
Source: daemontools
Version: 1:0.76-6
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi,
While working on the reproducible builds effort [1], we have noticed
that daemontools could not be built reproducibly.
The attached patch removes timestamps from the build system. Once
applied, daemontools can be built reproducibly in our current
experimental
framework.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff -urNad daemontools.orig/daemontools-0.76/debian/implicit
daemontools/daemontools-0.76/debian/implicit
--- daemontools.orig/daemontools-0.76/debian/implicit 2015-02-02
19:43:04.575255533 +
+++ daemontools/daemontools-0.76/debian/implicit2015-02-02
19:46:43.568967310 +
@@ -35,7 +35,7 @@
debian/$*/usr/share/doc/$*/changelog'
@test -s debian/$*/usr/share/doc/$*/changelog || \
sh -cx 'rm -f debian/$*/usr/share/doc/$*/changelog'
- @gzip -9 debian/$*/usr/share/doc/$*/changelog*
+ @gzip -9n debian/$*/usr/share/doc/$*/changelog*
%.deb-docs-docs: %.deb-docs-base
@for i in `cat debian/$*.docs 2/dev/null || :`; do \
if test -d $$i; then \
@@ -54,7 +54,7 @@
@if test -r debian/$*.NEWS.Debian; then \
sh -cx 'install -m0644 debian/$*.NEWS.Debian \
debian/$*/usr/share/doc/$*/NEWS.Debian \
- gzip -9 debian/$*/usr/share/doc/$*/NEWS.Debian'; \
+ gzip -9n debian/$*/usr/share/doc/$*/NEWS.Debian'; \
fi
%.deb-docs-examples: %.deb-docs-docs
@rm -rf debian/$*/usr/share/doc/$*/examples
diff -urNad daemontools.orig/daemontools-0.76/debian/rules
daemontools/daemontools-0.76/debian/rules
--- daemontools.orig/daemontools-0.76/debian/rules 2015-02-02
19:43:04.575255533 +
+++ daemontools/daemontools-0.76/debian/rules 2015-02-02 19:44:01.937792978
+
@@ -47,7 +47,7 @@
install -d -m0755 '$(DIR)'/usr/share/man/man8
for i in debian/daemontools-man/*.8; do \
install -m0644 $$i '$(DIR)'/usr/share/man/man8/ \
- gzip -9 '$(DIR)'/usr/share/man/man8/$${i##*/} || exit 1; \
+ gzip -9n '$(DIR)'/usr/share/man/man8/$${i##*/} || exit 1; \
done
# changelog
test -r changelog || ln -s daemontools-0.76/src/CHANGES changelog
@@ -62,7 +62,7 @@
'$(DIR)'-run/usr/sbin/update-service
install -d -m0755 '$(DIR)'-run/usr/share/man/man8
install -m0644 debian/update-service.8 '$(DIR)'-run/usr/share/man/man8/
- gzip -9 '$(DIR)'-run/usr/share/man/man8/update-service.8
+ gzip -9n '$(DIR)'-run/usr/share/man/man8/update-service.8
# systemd service
install -d -m0755 '$(DIR)'-run/lib/systemd/system
install -m0644 debian/systemd/daemontools.service \
Bug#776838: System freezes with borked graphics
Am 02.02.2015 um 18:15 schrieb Sven Joachim: nForce 405 (C61) GPU. Try booting with the nouveau.config=NvMSI=0 kernel parameter. If that does not help, use nouveau.noaccel=1. Cheers, Sven I tried with nouveau.config=NvMSI=0 twice, everything worked fine. With nouveau.noaccel=1 it also works. I also tried Fedora 21 Workstation Live today, which has the same problem. I opened a bug report there: https://bugzilla.redhat.com/show_bug.cgi?id=1188283 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776261: tecnoballz' Debian bug reports
Hello Bruno, Celelibi reported some other issues of tecnoballz. Could you take a look at those bug reports and comment on them? https://bugs.debian.org/776261 https://bugs.debian.org/776262 https://bugs.debian.org/776342 https://bugs.debian.org/776339 https://bugs.debian.org/776343 Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#776841: libgnutls28-dev: please make libgnutls-dev package multi-arch
Andreas Metzler ametz...@bebt.de - Mon, 2 Feb 2015 19:47:01 +0100
On 2015-02-02 Michel Briand michelbri...@free.fr wrote:
Package: libgnutls28-dev
Version: 3.3.8-4~bpo70+1
Severity: important
package libgnutls28-dev:amd64 offers all required file to build an
application with GnuTLS on Debian amd64 architecture.
Whereas libgnutls28-dev:i386 lacks some important files (libgnutls.a
and the link libgnutls.so).
[...]
* What exactly did you do (or not do) that was effective (or
ineffective)?
gcc -m32
* What was the outcome of this action?
Link fails:
/usr/bin/ld.bfd.real: cannot find -lgnutls
* What outcome did you expect instead?
That the package libgnutls28-dev:i386 offers the same files as
libgnutls28-dev:amd64 :
ll /usr/lib/*/libgnutls.so
lrwxrwxrwx 1 root root 25 nov. 18
22:27 /usr/lib/x86_64-linux-gnu/libgnutls.so -
libgnutls-deb0.so.28.41.0
ll /usr/lib/*/libgnutls.a
-rw-r--r-- 1 root root 2435010 nov. 18
22:27 /usr/lib/x86_64-linux-gnu/libgnutls.a
[...]
Hello Michel,
I have just downloaded libgnutls28-dev_3.3.8-4~bpo70+1_i386.deb and
libgnutls28-dev_3.3.8-4~bpo70+1_amd64.deb from debian to doublecheck
that the package is ok an complete. Both amd64 and i386 contain the
required files:
ametzler@argenau:/tmp$ debdiff
libgnutls28-dev_3.3.8-4~bpo70+1_i386.deb
libgnutls28-dev_3.3.8-4~bpo70+1_amd64.deb [The following lists of
changes regard files as different if they have different names,
permissions or owners.]
Files in second .deb but not in first
-
-rw-r--r-- root/root /usr/lib/x86_64-linux-gnu/libgnutls.a
-rw-r--r-- root/root /usr/lib/x86_64-linux-gnu/libgnutlsxx.a
-rw-r--r-- root/root /usr/lib/x86_64-linux-gnu/pkgconfig/gnutls.pc
lrwxrwxrwx root/root /usr/lib/x86_64-linux-gnu/libgnutls.so -
libgnutls-deb0.so.28.41.0 lrwxrwxrwx
root/root /usr/lib/x86_64-linux-gnu/libgnutlsxx.so -
libgnutlsxx.so.28.1.0
Files in first .deb but not in second
-
-rw-r--r-- root/root /usr/lib/i386-linux-gnu/libgnutls.a
-rw-r--r-- root/root /usr/lib/i386-linux-gnu/libgnutlsxx.a
-rw-r--r-- root/root /usr/lib/i386-linux-gnu/pkgconfig/gnutls.pc
lrwxrwxrwx root/root /usr/lib/i386-linux-gnu/libgnutls.so -
libgnutls-deb0.so.28.41.0 lrwxrwxrwx
root/root /usr/lib/i386-linux-gnu/libgnutlsxx.so -
libgnutlsxx.so.28.1.0
Control files: lines which differ (wdiff format)
Architecture: [-i386-] {+amd64+}
Installed-Size: [-2324-] {+2824+}
cu Andreas
Hello Andreas,
yes I agree.
I didn't looked into libgnutls28-dev:i386 file list because I can't
install it along the amd64 version.
apt-get install libgnutls28-dev:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required: libgnutlsxx28 libtasn1-doc
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
libc++-dev:i386 libc++-helpers libc++1:i386 libgmp-dev:i386
libgmpxx4ldbl:i386 libgnutlsxx28:i386 libp11-kit-dev:i386
libtasn1-6-dev:i386 nettle-dev:i386 zlib1g-dev:i386 Suggested packages:
clang:i386 libgmp10-doc:i386 libmpfr-dev:i386 guile-gnutls:i386
Recommended packages: libstdc++-dev:i386 libtasn1-doc:i386
The following packages will be REMOVED:
libgnutls28-dev libp11-kit-dev libtasn1-6-dev nettle-dev
The following NEW packages will be installed:
libc++-dev:i386 libc++-helpers libc++1:i386 libgmp-dev:i386
libgmpxx4ldbl:i386 libgnutls28-dev:i386 libgnutlsxx28:i386
libp11-kit-dev:i386 libtasn1-6-dev:i386 nettle-dev:i386 zlib1g-dev:i386
0 upgraded, 11 newly installed, 4 to remove and 125 not upgraded. Need
to get 3,594 kB of archives. After this operation, 8,152 kB of
additional disk space will be used. Do you want to continue [Y/n]? n
Abort.
It seems that packages are mutually exclusive. It's a blocker for me.
I don't understand why the -dev package is specific to the architecture.
I'd like to note that I can use Qt 4 to produce both amd64 and i386.
I've installed libqt4-dev and both architecture dependent packages:
libqtcore4:amd64 libqtcore4:i386. And everything is fine to build my
application both for Debian amd64 and i386
How can we go on with that ?
Regards,
Michel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776877: uses ill-defined architecture any-amd64
Hi Mike, do you have an idea, why nasm is limited just to some architectures? It looks like it's available on all release Debian architectures: https://packages.debian.org/unstable/nasm So it seems there's no reason to have the limit in the place at all. Cheers, Ondrej On Mon, Feb 2, 2015, at 20:50, Helmut Grohne wrote: Source: libjpeg-turbo Version: 1:1.3.1-11 User: helm...@debian.org Usertags: rebootstrap Control: block -1 by 748936 libjpeg-progs uses the ill-defined architecture wildcard any-amd64 in its Build-Depends. apt and dpkg do not agree on its meaning (for details see #748936). For instance on apt would not treat x32 as any-amd64, but dpkg would. This causes x32 builds of libjpeg-turbo to fail at dpkg-checkbuilddeps when installing build-depends with apt-get build-dep. Please use something other than any-amd64. Maybe amd64 kfreebsd-amd64? I mark 748936 as a blocker of this bug to keep track of the instances of the issue. Helmut -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776882: gogoc client linux.sh template is not ok
Package: gogoc
Version: 1:1.2-5
Severity: important
Dear Maintainer,
i have change my gogoc.conf but the script will not run ..
have you a fix for me or can anybody help me..
gogoc -n
delete tunnel freenet6 failed: No such device
/usr/share/gogoc/template/linux.sh: Zeile 271: [: Zu viele Argumente.
: Fehler beim Auslesen der Schnittstelleninformation: Gerät nicht gefunden
/usr/share/gogoc/template/linux.sh: Zeile 87: [: : Ganzzahliger Ausdruck
erwartet.
SIOGIFINDEX: Kein passendes Gerät gefunden
/usr/share/gogoc/template/linux.sh: Zeile 87: [: : Ganzzahliger Ausdruck
erwartet.
[Feb 02 17:48:29] radvd: syntax error in /var/run/gogoc/gogoc-rtadvd.conf, line
13: {
[Feb 02 17:48:29] radvd: error parsing or activating the config file:
/var/run/gogoc/gogoc-rtadvd.conf
[Feb 02 17:48:29] radvd: Exiting, failed to read config file.
SIOCDELRT: Kein passender Prozess gefunden
/usr/share/gogoc/template/linux.sh: Zeile 87: [: : Ganzzahliger Ausdruck
erwartet.
SIOGIFINDEX: Kein passendes Gerät gefunden
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.15.0-pf2+ (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages gogoc depends on:
ii iproute2 3.16.0-2
ii libc62.19-13
ii libgcc1 1:4.9.1-19
ii libssl1.0.0 1.0.1k-1
ii libstdc++6 4.9.1-19
ii net-tools1.60-26+b1
Versions of packages gogoc recommends:
ii radvd 1:1.9.1-1.3
Versions of packages gogoc suggests:
ii sipcalc 1.1.5-1
-- Configuration Files:
/etc/gogoc/gogoc.conf changed [not included]
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/share/gogoc/template/linux.sh (from gogoc package)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770871: [Pkg-utopia-maintainers] Bug#770871: Bug#770871: ModemManager only starts up if system is PID 1
Am 02.02.2015 um 16:14 schrieb Didier 'OdyX' Raboud: Le lundi, 2 février 2015, 14.34:14 Michael Biebl a écrit : To keep the diff smaller, could you change the patch to simply use (…) A more verbose patch header would be great as well. Just add a few sentences that for MM we use runtime detection since we want the dbus autostart behaviour on !systemd for MM. Something along these lines? I've looked into this a bit more: Adding the sd_booted() checks to modem_manager_poke() and modem_manager_poke_cb() is actually not necessary, since we well never call them in the systemd case. I'll fix this patch up accordingly beforce committing it. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#776807: lazarus-ide-qt4-1.2.4: Gives Compiler /usr/bin/fpc does not support, target x86_64-linux on first exectution.
On 02-02-15 01:51, s...@kub.cz wrote: I have installed package this package and I am getting behaviour very close if not equeal to bug 774839. The only difference beeing, that I did not installed the package manually but using normal debian way sudo aptitude install lazarus-ide-qt4-1.2.4 Looking at your dependency list, you updated the package, right? I mean, you have older versions installed? Anyways, the debian way for lazarus is not to install the versioned package, but the unversioned equavalent: i.e. lazarus-ide-qt4. I would be glad is I can provide more information about this bug. Could you let me know the content of /etc/lazarus/? And also tell me if that directory is a symlink or not. Also, what is the content of your ~/.lazarus/helpoptions.xml and ~/.lazarus/environmentoptions.xml (if you are willing to share). I did not find any combination of settings which would work (I thied i386 because I have multiarch deban setup so I guessed that it might work). Does it help if you rename your ~/.lazarus direcory temporarily? (Let's keep the i386 version out of the way while we are trying to fix the issue, that complicates it more than it helps.) Paul signature.asc Description: OpenPGP digital signature
Bug#776877: uses ill-defined architecture any-amd64
Hi Ondrej, i think it was related to a nasm problem on 32bit system back in the early turbo days, probably this one [1]. My guess is that we could try to drop nasm's architecture limitation completely from BD, presuming that latest nasm versions handle things well by now. Mike [1] http://sourceforge.net/p/libjpeg-turbo/bugs/20/ -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976148 GnuPG Key ID 0x25771B13 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de - Original message - Hi Mike, do you have an idea, why nasm is limited just to some architectures? It looks like it's available on all release Debian architectures: https://packages.debian.org/unstable/nasm So it seems there's no reason to have the limit in the place at all. Cheers, Ondrej On Mon, Feb 2, 2015, at 20:50, Helmut Grohne wrote: Source: libjpeg-turbo Version: 1:1.3.1-11 User: helm...@debian.org Usertags: rebootstrap Control: block -1 by 748936 libjpeg-progs uses the ill-defined architecture wildcard any-amd64 in its Build-Depends. apt and dpkg do not agree on its meaning (for details see #748936). For instance on apt would not treat x32 as any-amd64, but dpkg would. This causes x32 builds of libjpeg-turbo to fail at dpkg-checkbuilddeps when installing build-depends with apt-get build-dep. Please use something other than any-amd64. Maybe amd64 kfreebsd-amd64? I mark 748936 as a blocker of this bug to keep track of the instances of the issue. Helmut -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#354432: www.debian.org: [debian-i18n] Incorrect Quote in paragraphs with different language
Hi:
Me again... I'm attaching a new patch, which is less invasive I think.
It removes the .quote class definition in the CSS file under german dir
as Victory suggested. Adding class=quote to the blockquote sections
does not work.
If that patch doesn't work either maybe this is a wont fix as Jutta
suggested previously? Or if anyone can give me a hint about how to
properly solve this I could give it another try.
Cheers,
--
Jeremías
Index: german/debian-de.css
===
RCS file: /cvs/webwml/webwml/german/debian-de.css,v
retrieving revision 1.7
diff -u -u -r1.7 debian-de.css
--- german/debian-de.css 19 Feb 2011 19:11:05 - 1.7
+++ german/debian-de.css 2 Feb 2015 21:17:00 -
@@ -19,10 +19,10 @@
html[lang=de] blockquote[lang=en].quote p:after { content: ; }
html[lang=de] blockquote[lang=en].quote p.last:after { content: \201D; }
-blockquote[lang=en].quote q:before { content: \201C; }
-blockquote[lang=en].quote q:after { content: \201D; }
-blockquote[lang=en].quote q q:before { content: \2018; }
-blockquote[lang=en].quote q q:after { content: \2019; }
+blockquote[lang=en] q:before { content: \201C; }
+blockquote[lang=en] q:after { content: \201D; }
+blockquote[lang=en] q q:before { content: \2018; }
+blockquote[lang=en] q q:after { content: \2019; }
#breadcrumbs {
text-transform: none;
Bug#776838: System freezes with borked graphics
Control: forcemerge 758460 -1 Am 02.02.2015 um 21:06 schrieb Karsten Loeft: Am 02.02.2015 um 18:15 schrieb Sven Joachim: nForce 405 (C61) GPU. Try booting with the nouveau.config=NvMSI=0 kernel parameter. If that does not help, use nouveau.noaccel=1. Cheers, Sven I tried with nouveau.config=NvMSI=0 twice, everything worked fine. With nouveau.noaccel=1 it also works. Thanks, I think this is the same as #758460 then. Will be fixed in the kernel when Linux 3.16.7-ckt5 gets uploaded. Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776748: (pre-approval) unblock: libxml2/2.9.1+dfsg1-5 (via t-p-u)
On Tue, Feb 3, 2015 at 3:54 AM, Julien Cristau jcris...@debian.org wrote: On Tue, Feb 3, 2015 at 02:23:20 +0800, Aron Xu wrote: On Tue, Feb 3, 2015 at 12:02 AM, Adam D. Barratt a...@adam-barratt.org.uk wrote: On 2015-02-02 6:37, Aron Xu wrote: On Mon, Feb 2, 2015 at 1:13 AM, Adam D. Barratt a...@adam-barratt.org.uk wrote: Control: tags -1 + moreinfo On Sun, 2015-02-01 at 16:24 +0800, Aron Xu wrote: +libxml2 (2.9.1+dfsg1-5) testing; urgency=medium + + * Add pkg-config to B-D + * Use -O3 for normal builds Could you expand on the rationale for introducing those now? Particularly as neither appears to be mentioned in the changelogs for the uploads to unstable. These are directly picked from the 2.9.2 upload, which stuck for RC bug. At that time the change was quite big (major release) so those aren't documented in very detail but are in the git for quite some time. Well, the changelog wasn't very detailed for 2.9.2 either. :-) I realise that the changes are in the unstable package (I checked that first), I was more interested in the rationale, particularly for the optimisation change. It's more about a changing attitude on speed/space trade of -O2 and -O3, and more and more apps are using -O3 for release build (e.g. CMake default). If release team believe that's not desired in Jessie, I can keep it out of the way. Anything that's not a minimal fix for a RC bug is not desired for jessie at this stage. Updated version of debdiff, removing the -O3 change. Regards, Aron libxml2_2.9.1+dfsg1-5_2ndtry.debdiff Description: Binary data
Bug#685832: xcfe4-sensors-plugin relies on a setuid hddtemp and recommends to setuid it
X-Debbugs-Cc: eddy.petri...@gmail.com Package: xfce4-sensors-plugin Version: 1.2.5-2 Followup-For: Bug #685832 unmerge 685832 tags 685832 -fixed-upstream thanks Hello, After changing HDD I have run into this same problem in Wheezy. I have disconnected this bug from 670046 since the other bug is actually a different issue. Just as before, the patch already provided in 2012 is working correctly and is trivial. I already have a locally rebuilt package for wheezy which fixes the issue by just adding netcat-traditional as a build dependency and everything works without issues. For your conveninece I attached the updated patch and the patch I applied over the unstable version to backport xfce4-sensors-plugin to wheezy. -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (99, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-rc2-heidi+ (SMP w/2 CPU cores) Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfce4-sensors-plugin depends on: ii libatk1.0-0 2.4.0-2 ii libc6 2.13-38+deb7u7 ii libcairo2 1.12.2-3 ii libfontconfig1 2.9.0-7.1 ii libfreetype62.4.9-1.1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-5 ii libgtk2.0-0 2.24.10-2 ii libnotify4 0.7.5-1 ii libpango1.0-0 1.30.0-1 ii libsensors4 1:3.3.2-2+deb7u1 ii libxfce4ui-1-0 4.8.1-1 ii libxfce4util4 4.8.2-1 ii xfce4-panel 4.8.6-4 Versions of packages xfce4-sensors-plugin recommends: ii hddtemp 0.3-beta15-52 ii lm-sensors 1:3.3.2-2+deb7u1 Versions of packages xfce4-sensors-plugin suggests: pn xsensors none -- no debconf information -- Eddy Petrișor diff -Nru xfce4-sensors-plugin-1.2.5/debian/changelog xfce4-sensors-plugin-1.2.5/debian/changelog --- xfce4-sensors-plugin-1.2.5/debian/changelog 2013-05-26 14:18:23.0 +0300 +++ xfce4-sensors-plugin-1.2.5/debian/changelog 2015-02-02 21:48:45.0 +0200 @@ -1,3 +1,11 @@ +xfce4-sensors-plugin (1.2.5-3) unstable; urgency=low + + * Add netcat-traditional as a build dependency so xfce4-sensors +aske hddtemp's via over localhost:7634, and does not rely on suid +hddtemp + + -- Eddy Petrișor eddy.petri...@gmail.com Mon, 02 Feb 2015 21:36:28 +0200 + xfce4-sensors-plugin (1.2.5-2) unstable; urgency=low [ Daniel Echeverry ] diff -Nru xfce4-sensors-plugin-1.2.5/debian/control xfce4-sensors-plugin-1.2.5/debian/control --- xfce4-sensors-plugin-1.2.5/debian/control 2013-05-26 14:19:03.0 +0300 +++ xfce4-sensors-plugin-1.2.5/debian/control 2015-02-02 21:35:17.0 +0200 @@ -5,9 +5,9 @@ Uploaders: Yves-Alexis Perez cor...@debian.org, Lionel Le Folgoc mrpo...@gmail.com Build-Depends: debhelper (= 9), libgtk2.0-dev, xfce4-panel-dev, libxml2-dev, - libsensors4-dev, libxml-parser-perl, - hddtemp [!kfreebsd-amd64 !kfreebsd-i386 !hurd-i386], intltool, - libxfce4ui-1-dev, libnotify-dev + libsensors4-dev, libxml-parser-perl, + hddtemp [!kfreebsd-amd64 !kfreebsd-i386 !hurd-i386], intltool, + libxfce4ui-1-dev, libnotify-dev, netcat-traditional | netcat-openbsd Standards-Version: 3.9.4 Homepage: http://goodies.xfce.org/ Vcs-Svn: svn://svn.debian.org/pkg-xfce/goodies/trunk/xfce4-sensors-plugin/ diff -Nru xfce4-sensors-plugin-1.2.5/debian/changelog xfce4-sensors-plugin-1.2.5/debian/changelog --- xfce4-sensors-plugin-1.2.5/debian/changelog 2013-05-26 14:18:23.0 +0300 +++ xfce4-sensors-plugin-1.2.5/debian/changelog 2015-02-02 21:48:45.0 +0200 @@ -1,3 +1,12 @@ +xfce4-sensors-plugin (1.2.5-2~lbp70+1~custom0) wheezy-backports; urgency=low + + * Rebuild for squeeze-backports. + * Add netcat-traditional as a build dependency so xfce4-sensors +uses hddtemp over localhost:7634, and does not rely on suid +hddtemp + + -- Eddy Petrișor eddy.petri...@gmail.com Mon, 02 Feb 2015 21:36:28 +0200 + xfce4-sensors-plugin (1.2.5-2) unstable; urgency=low [ Daniel Echeverry ] diff -Nru xfce4-sensors-plugin-1.2.5/debian/control xfce4-sensors-plugin-1.2.5/debian/control --- xfce4-sensors-plugin-1.2.5/debian/control 2013-05-26 14:19:03.0 +0300 +++ xfce4-sensors-plugin-1.2.5/debian/control 2015-02-02 21:35:17.0 +0200 @@ -5,9 +5,9 @@ Uploaders: Yves-Alexis Perez cor...@debian.org, Lionel Le Folgoc mrpo...@gmail.com Build-Depends: debhelper (= 9), libgtk2.0-dev, xfce4-panel-dev, libxml2-dev, - libsensors4-dev, libxml-parser-perl, - hddtemp [!kfreebsd-amd64 !kfreebsd-i386 !hurd-i386], intltool, - libxfce4ui-1-dev, libnotify-dev + libsensors4-dev, libxml-parser-perl, + hddtemp [!kfreebsd-amd64 !kfreebsd-i386 !hurd-i386], intltool, + libxfce4ui-1-dev, libnotify-dev, netcat-traditional | netcat-openbsd Standards-Version: 3.9.4 Homepage: http://goodies.xfce.org/ Vcs-Svn:
Bug#774607: git: diff for NMU version 1:2.1.4-2.1
On 2015-02-02 21:09, Jonathan Nieder wrote: Niels Thykier wrote: I've prepared an NMU for git (versioned as 1:2.1.4-2.1) and uploaded it to DELAYED/2. Thanks. Could you bump it to DELAYED/0? Regards, Jonathan I have re-uploaded them without delay (as it was faster than me figuring out the dcut syntax for the reschedule). :) ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775016: ITP: hovercraft -- impress.js presentations by reStructuredText
We've already further proceeded towards a Hovercraft package. The current status is: 1) python3-svg.path like written above is ready to get uploaded (sponsored) [1]. 2) the maintainer of python-watchdog already reacted [2] and made a package of python3-pathtools [3], needed for that. 3) Manuel is only needed to the tests, but I found that very interesting and went for it, too [4]. You can support the release of the Hovercraft Debian package by sponsoring. Greetings, Daniel Stender [1] http://bugs.debian.org/776571 RFS: svg.path/2.0~b1-1 -- [ITP] Python modules providing SVG objects [2] http://bugs.debian.org/776599 python-watchdog: please provide Python3 package [3] http://mentors.debian.net/debian/pool/main/p/python-pathtools/python-pathtools_0.1.2-2.dsc [4] http://bugs.debian.org/776885 RFS: manuel/1.8.0-1 [ITP] -- Python library for documented tests -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776878: security-tracker: DSA-3149-1 vs. tracker
Package: security-tracker Severity: normal Hi, the tracker page [1] for DSA-3149-1 [2] seems to lack the link to the relevant CVE [3]. Please fix the tracker data. Thanks for your time. [1] https://security-tracker.debian.org/tracker/DSA-3149-1 [2] https://lists.debian.org/debian-security-announce/2015/msg00033.html [3] https://security-tracker.debian.org/tracker/CVE-2014-8126 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774607: git: diff for NMU version 1:2.1.4-2.1
Control: tags 774607 + patch Control: tags 774607 + pending Dear maintainer, I've prepared an NMU for git (versioned as 1:2.1.4-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru git-2.1.4/debian/changelog git-2.1.4/debian/changelog --- git-2.1.4/debian/changelog 2014-12-20 03:36:30.0 +0100 +++ git-2.1.4/debian/changelog 2015-02-02 19:42:39.0 +0100 @@ -1,3 +1,11 @@ +git (1:2.1.4-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Use interest-noawait triggers for gitweb to avoid a +trigger cycle. (Closes: #774607) + + -- Niels Thykier ni...@thykier.net Mon, 02 Feb 2015 19:42:37 +0100 + git (1:2.1.4-2) unstable; urgency=medium * update gitweb configuration for Apache 2.4: diff -Nru git-2.1.4/debian/gitweb.triggers git-2.1.4/debian/gitweb.triggers --- git-2.1.4/debian/gitweb.triggers2014-12-20 01:07:07.0 +0100 +++ git-2.1.4/debian/gitweb.triggers2015-02-02 19:42:14.0 +0100 @@ -1 +1 @@ -interest /usr/share/apache2/apache2-maintscript-helper +interest-noawait /usr/share/apache2/apache2-maintscript-helper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776879: xtables-addons: please make the build reproducible
Source: xtables-addons Version: 2.6-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps fileordering Hi! While working on Debian's “reproducible builds” effort [1], we have noticed that xtables-addons doesn't build reproducibly. The file xtables-addons.tar.bz2 contains timestamps and an unstable file order. The attached patch creates a tarball with a sorted file list and with timestamps set to the date of the last changelog entry. Once applied, xtables-addons can be built reproducibly in our current experimental framework. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/changelog b/debian/changelog index f506cd3..475a2a1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +xtables-addons (2.6-1.0~reproducible1) UNRELEASED; urgency=low + + * Use last changelog date for timestamps in tar file and +also sort files to get a reproducible order. + + -- Reiner Herrmann rei...@reiner-h.de Mon, 02 Feb 2015 20:56:52 +0100 + xtables-addons (2.6-1) unstable; urgency=medium * New upstream version [September 2014]. diff --git a/debian/rules b/debian/rules index 005af1d..af1de4a 100755 --- a/debian/rules +++ b/debian/rules @@ -7,6 +7,7 @@ PKD = $(abspath $(dir $(MAKEFILE_LIST))) # Package version pver := $(shell dpkg-parsechangelog -l$(PKD)/changelog | sed -ne 's,^Version: *\([0-9.]*\).*,\1,p') +BUILD_DATE := $(shell dpkg-parsechangelog --show-field=Date) DCFG := debian/xtables-addons-dkms.dkms TMPSRC := debian/temp.src @@ -45,7 +46,7 @@ override_dh_auto_install: $(DCFG) mkdir -p $(SRC_MOD) \ mv $(TMPSRC) $(SRC_MOD)/xtables-addons \ cd debian/xtables-addons-source/usr/src \ - tar cjf xtables-addons.tar.bz2 modules \ + find modules -print0 | LC_ALL=C sort -z | tar cjf xtables-addons.tar.bz2 --mtime=$(BUILD_DATE) --no-recursion --null -T - \ $(RM) -r modules/xtables-addons/debian ## prepare DKMS sources mkdir -p $(SRC_DKMS) \ signature.asc Description: OpenPGP digital signature
Bug#776881: bowtie: '-debug' binaries break `bowtie-build`
Package: bowtie Version: 1.1.1-1 Severity: grave Justification: renders package unusable Hello, Looks like the debug versions of 'bowtie-build-l' and 'bowtie-build-s' are present instead thus breaking the 'bowtie-build' wrapper making the package useless. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.13.0-44-generic (SMP w/12 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages bowtie depends on: ii libc6 2.19-14 ii libgcc1 1:4.9.2-10 ii libstdc++6 4.9.2-10 ii python 2.7.8-2 bowtie recommends no packages. Versions of packages bowtie suggests: pn bowtie-examples 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#776883: hime: [packaging]Missing dependency of libappindicator-dev causes hime lacking appindicator support
Package: hime Version: 0.9.10+git20131104-2 Severity: normal Downstream bug report: https://bugs.launchpad.net/ubuntu/+source/hime/+bug/1404907 Hi, previously I found that hime in Ubuntu 14.10(possibly with 14.04) didn't support AppIndicator icons even that upstream has already implemented it. Checking out it's source package I found that appindicator development package isn't listed as hime's build dependency and it's support will be disabled during configure phase: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/utopic/hime/utopic/view/head:/debian/control ``` Build-Depends: debhelper (= 9.0.0), libgtk2.0-dev (= 2.20.0), libgtk-3-dev, libqt4-dev, libchewing3-dev, libxtst-dev, libanthy-dev, autotools-dev, dpkg-dev (= 1.16.1~) ``` I've checked the source package in Debian and found the same issue. Please fix it since it'll degrade hime's UX in Unity DE as Unity only supports application icon based on appindicator from now on, refer: https://bugs.launchpad.net/ayatana-design/+bug/974480 Thanks in advance! Ｖ字龍(Vdragon) vdragon.tai...@gmail.com -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (500, 'eliu'), (100, 'trusty-backports') Architecture: i386 (i686) Kernel: Linux 3.13.0-39-generic (SMP w/8 CPU cores) Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages hime depends on: ii libappindicator1 12.10.1+13.10.20130920-0ubuntu4.1 ii libc62.19-0ubuntu6.5 ii libcairo21.13.0~20140204-0ubuntu1.1 ii libgdk-pixbuf2.0-0 2.30.7-0ubuntu1 ii libglib2.0-0 2.40.2-0ubuntu1 ii libgtk2.0-0 2.24.23-0ubuntu1.1 ii libpango-1.0-0 1.36.3-1ubuntu1.1 ii libpangocairo-1.0-0 1.36.3-1ubuntu1.1 ii libx11-6 2:1.6.2-1ubuntu2 ii libxtst6 2:1.2.2-1 Versions of packages hime recommends: ii anthy 9100h-23ubuntu2 ii im-config [im-switch] 0.24-1ubuntu4.1 ii libchewing30.3.5-4build1 Versions of packages hime suggests: pn kasumi 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#776658: lintian: Memory consumption of harness and html_reports
On 2015-01-31 10:06, Niels Thykier wrote: [...] I have started a different approach (see [1] for WIP code). It is mostly a parallel track to your idea, so they can certainly co-exist. The goal of this approach is to: * Split harness into a simple coordinator * Remove the Lab as a (primary) data store (it is too fragile) * Harness state as datastore [...] I got a patch series to implement this (see also [BRANCH]). I have also managed to do a few tests on lilburn.debian.org with no issues. The commit messages are at the bare minimum - apologise for that. Review/remarks welcome. With the rewrite: * harness now uses ~16MB (rather than 700ish MB). * harness now supports processing in throw-away labs (e.g. temp labs cleaned up by lintian at the end of the run). - Using $USE_PERMANENT_LAB = 0 in config - $LINTIAN_SCRATCH_SPACE (if defined) becomes TMPDIR of the lintian processes (and also the directory of the temp-labs). * it is now possible to run harness on lintian.d.o with up to date live data without affecting the automated run[1]. * it is possible to terminate lintian (e.g. kill -TERM) during a run and harness will still mark the completed packages as up to date. - caveat: sending harness a signal (e.g. ^C'ing harness) will not. - caveat: Not recommended for $USE_PERMANENT_LAB = 1 cases. * the full run is now implemented as reschedule-all (eventually) and then an incremental run to start off with. The clean mode works similarly, except it throws out the existing state files first. What is missing / known issues: * A patch to reduce the memory usage of html_reports (but that is for a different patch series). Nice to have / scope + feature creep: * Have harness stop lintian when the time is up, rather than letting it run to the end of the current run (which can be several hours away). * The state cache should probably be gzip'ed as it takes 30+MB of disk (compressed is at 5-6ish MB) Bonus features: * Add --schedule-limit-groups parameter to change the limit of groups to process. The timeout remains hard-coded though. * It /should/ migrate the last-processed-by from the previous state cache (untested). While it will still reschedule all packages, their relative priority is retained. Remarks on the patches: * The patches 0001-0003 are self-contained and can be cherry-picked to master (in any order in fact). * The patches 0004-0008 are *not* self-contained and must all be applied. I decided to have a patch per tool being updated as I was easier to write them that way. - Nothing a --no-ff merge cannot solve though. * The 0009-0011 are incremental patches on top of the 0004-0008 bundle. If there are no reviews or objections, I intend merge this later this week and push it to lilburn.d.o to make graphs work again. Thanks, ~Niels [1] Take a copy the config, logs/lintian.log and the harness-state. Ensure $USE_PERMANENT_LAB is set to 0 and $LINTIAN_SCRATCH_SPACE is set to a (for you) writable directory with enough capacity (probably *not* /tmp). Furthermore change the rest of the config values to fit your workspace and you are good to go. You /may/ also want to pass --schedule-limit-group N unless you do not mind waiting several hours at worst. [BRANCH]: http://anonscm.debian.org/cgit/users/nthykier/lintian.git/log/?h=reporting-rewrite NB: Rebased regularly. 0001-Move-save_state_cache-to-L-Util.patch Description: application/mbox 0002-L-Util-Add-untaint-subroutine.patch Description: application/mbox 0003-lintian-Add-status-log-for-use-by-harness.patch Description: application/mbox 0004-reporting-sync-state-New-internal-reporting-command.patch Description: application/mbox 0005-Make-find_backlog-check-out-of-date-flag-in-the-stat.patch Description: application/mbox 0006-Rewrite-harness-to-use-reporting-sync-state.patch Description: application/mbox 0007-Rewrite-html_reports-to-use-harness-state-cache.patch Description: application/mbox 0008-maintainer.tmpl-Use-out-of-date-marker.patch Description: application/mbox 0009-harness-Move-backlog-time-out-handling-into-process_.patch Description: application/mbox 0010-harness-Harness-lintian-in-a-subprocess.patch Description: application/mbox 0011-r-harness-Add-schedule-limit-groups-cmd-line-argumen.patch Description: application/mbox
Bug#773354: please add breaks: live-tools ( 4.0.1-1)
Hi Andreas My NMU was in no way meant to critice your maintenance of util-linux or to attack you. It's just that in the current phase of the release process it's time to fix these bugs and my aim is to help with that. As you stated that you are not very motivated to work on this bug I thought you would appreciate this help. Andreas Henriksson andr...@fatal.se writes: Hello Gaudenz Steinlin. On Mon, Feb 02, 2015 at 11:25:55AM +0100, Gaudenz Steinlin wrote: Of course a fix in util-linux can't solve problems resulting from other packages. All packages that call update-initramfs and don't depend on initramfs-tools need the same Breaks relation to live-tools. I don't know how many other such packages exist beside util-linux. Easy to find out thanks to the awesome codesearch: http://codesearch.debian.net/perpackage-results/update-initramfs/2/page_0 (Adding regexps to the query for filtering out only relevant matches is left as an exercise to the reader.) In other words, many That is why adding breaks IMHO is not a viable solution at all anywhere. That does not really help much because we don't need a list of packages that mention update-initramfs in some file but a list of packages that call update-initramfs in their maintainerscript without depending on initramfs-tools. I don't think codesearch is able to produce that list, but to me this seems like a quite special case. I would expect most packages that modify the initramfs to actually depend on initramfs-tools. But I agree that probably more packages than just util-linux need fixing for this. But this is outside the scope of this bug and as long as no other bugs are filed, it's hard to track. I also don't see a viable solution to this bug which fixes all of these problems in one go. I agree that fixing the problem with Breaks is a bit ugly and in theory adds the fix to the wrong package. But I currently don't see any viable other solution to this problem beside adding all these Breaks relations. An update to the stable version of live-tools does not seem practical to me. Do you see another way to fix this? Yes. Please read my previous mail to the bug report. So if I got you right, you would prefer to remove the update-initramfs call from util-linux's postinst. I'm fine with that. I can do another upload if you confirm that's your prefered solution. If initramfs-tools from current unstable really does not go into testing, then I agree that is probably the slightly better alternative. To me as an NMUer the Breaks seemd like the safer option as it's a no-op as long as live-tools is not installed on the same system. So there is less chance that the NMU breaks something. This is just one example out of several problems I see with your NMU. Which other problem do you see? Well, for one: Your NMU is RC buggy, given that you incorporated the previous NMU with bugs and all. Thanks for taking responsibility for that. ;) Well for one it was not my upload that introduced this RC bug. The version of the previous NMU was already in *testing* when I did my upload. IMO we are all colectively responsible for getting the jessie RC bug count down. So it's as much my responsibility to fix this as yours. ;-) But if I do another upload I will also fix the typo in the 4.1 NMU. I missed the fact that the 4.1 NMU did not fix the bug it claimed to fix. Please, again, also read my previous mail to the bug report you're trying to fix and you'll find a similar but IMHO much more valid reason to add a Breaks for another package (which is also that packages bug and not a bug in util-linux). I don't understand what you mean here. Maybe you should be a bit more explicit in your message instead of alluding to what others should do. As you probably understand, I'm trying to urge you into looking at the whole picture instead of just a tiny part. That way I'm sure you'll likely come up with much better solutions. I don't completely understand what you are aiming at. IMO I always considered the whole picture but I don't see why the grml-debootstrap issue is related. Yes it's an issue, yes it'might be solved with a Breaks (did not look into it very deeply). But it's not about update-initramfs and has a completely different cause. I don't see how these two issues can be solved together. They seem quite orthogonal to me. And last but not least the grml-debootstrap does not even have RC severity at the moment. If you as one of the util-linux maintainers think this is RC, please set the severity accordingly. Gaudenz P.S.: If you really don't like the upload and prefer the current state in testing you should also comment on the unblock bug which is #776765. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776595: Upstream fixed in the same way as the patch
This bug is upstream fixed on the same way as in the patch: https://l10n.gnome.org/POT/gnome-menus.master/gnome-menus.master.nl.po With regards, Paul van der Vlis. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776595: Screenshot link
Screenshot: https://lists.vrijschrift.org/pipermail/vertaling/attachments/20150202/4a00f061/attachment-0001.png -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776894: RM: movabletype-opensource -- ROM; Unmaintained upstream; possible security issues
Package: ftp.debian.org Severity: normal See also #734303 and #774192 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734303: [pkg-mt-om-devel] Bug#774192: closed by Dominic Hargreaves d...@earth.li (Re: Bug#774192: CVE-2014-9057)
On Sun, Jan 04, 2015 at 01:36:08PM +0100, Salvatore Bonaccorso wrote: Control: reopen -1 Hi Dominic Note this issue only affects Movable Type versions 6.0.6, 5.2.11 and 5.18. It does not affect versions 6.0.5, 5.2.10, 5.17 and prior versions. Netanel Rubin, the discoverer of the issue confirmed to me that the information there seem just not correct, since he discovered the issue in testing in 5.2.10. Thus reopening the bug. I don't know if the parameter verification fixes is easily backportable to 5.1.4 also (not checked that (yet)). In the light of #734303, should movabletype-opensource maybe be removed also from unstable? On Tue, Jan 27, 2015 at 11:59:05AM +0100, Moritz Mühlenhoff wrote: Shall we remove it from unstable now? Hi, Sorry for the delay in replying to this. Yes, I've just filed a bug on ftp.debian.org for this. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776897: ca-certificates-java: Obsolete dependency on openjdk-6-jre-headless
Package: ca-certificates-java Version: 20140324 Severity: normal ca-certificates-java depends on openjdk-6-jre-headless | java6-runtime-headless, but since openjdk-6 has been removed from Jessie this should be changed to openjdk-7-jre-headless. This issue is caused by this check in debian/rules: ifeq ($(shell dpkg-vendor --derives-from Ubuntu echo yes),yes) SUBSTVARS = -Vnss:Depends=libnss3 (= 3.12.9+ckbi-1.82-0ubuntu3~) \ -Vjre:Depends=openjdk-7-jre-headless (= 7~u3-2.1.1~pre1-1) nss_lib = libnss3 else SUBSTVARS = -Vnss:Depends=libnss3 (= 3.12.10-2~) \ -Vjre:Depends=openjdk-6-jre-headless (= 6b16-1.6.1-2) nss_lib = libnss3 endif The dependency was updated for Ubuntu but not for Debian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776892: ITP: python-django-audit-log -- Django app to track changes to models
Package: wnpp Severity: wishlist Owner: Brian May b...@debian.org * Package name: python-django-audit-log Version : 0.7.0 Upstream Author : Vasil Vangelovski v...@atomidata.com * URL : https://pypi.python.org/pypi/django-audit-log/0.7.0 * License : BSD Programming Lang: Python Description : Django app to track changes to models This python package will automatically track and record all changes to a Django model. I am packaging this because an application I use and maintain (not yet in Debian) requires it. I plan on mantaining it as part of the Debian python modules team. I will be building Python2 and Python3 packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776700: Processed: tags 776700 wheezy, reopen
On 03.02.2015 00:27, Debian Bug Tracking System wrote: all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions roundcube/0.9.5+dfsg1-4.2. Ehr, seems I probably fucked that up somewhat; actually I just wanted to reopen the bug but keep it marked as fixed in jessie :[] I'm sorry! Before I try and break even more, can someone else fix that? Thanks! Marian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776644: texlive-xetex: xeCJK error message apparently prints wrong command
You're right, I'm sorry for not checking before. In jessie (texlive-xetex
2014.20141024-2), the message is better (though ideally I think it should
mention the command, but that's not a packaging bug):
*
* xeCJK warning: fandol
*
* Fandol is being set as the default font for CJK text.
* Please make sure it has been properly installed.
*
Incidentally, I stumbled on another xecjk bug in wheezy (it stack-overflows
if you use the fontspec option \defaultfontfeatures{Scale=MatchLowercase}
); but this, too, is already fixed in the jessie version.
Again, sorry for taking your time.
Bug#776896: Update Vietnamese program translation
Package: po4a Version: 0.45-1 Severity: wishlist Please commit my translation! Thanks, -- Trần Ngọc Quân. vi.po.gz Description: GNU Zip compressed data
Bug#616689: Root-on-LVM setup fails often due to timing issues
Hello I read the chain with interest since I have been fighting the same issue on my machine. What is interesting (at least to me) is that I am running a much older release of Ubuntu Lucid with a 2.6.32-71 kernel. I¹m not in the habit of rebooting very often so this issue may have existed for a while; however it encountered it yesterday. Like others I was able to proceed by issuing vgchange ay command; however I did have to create /var/log in the Busybox environment before that would work. I eagerly await a resolution Regards Nick
Bug#768133: evince won't print landscape PDFs
Hi all,
Just wanted to provide some additional context on this bug.
The current version of evince in jessie/sid will not print landscape
PDFs (at least, none that I've tried). Instead, the pages print blank.
It's possible to print the pages by un-checking ``Auto-rotate and
center'' (which is checked by default), but as expected, the page will
be oriented and positioned incorrectly, making the print basically
unusable. I haven't found a way to workaround the bug without resorting
to something like Okular or command-line tools.
An evince developer (Carlos Garcia Campos) states on 2015-01-28 in the
upstream bug [1] [2] [3]:
Having a proper fix for this is taking more time than I expected, so
I've just reverted the patch that introduced this regression in both
branches until we find a proper solution in both Evince and GTK+. This
is now fixed, use bug #734788 for new discussions or patches to the
centering option when having a manual scale.
There is also a Fedora bug report [4], where the maintainer reverted the
commit which caused it.
So, it seems the best step forward is to follow upstream and Fedora, and
revert this commit. I've attached a debdiff which reverts it, and tested
it in our busy computer lab for the past few days successfully.
Is there any opposition to marking this bug as release-critical? I know
it's late in the freeze, but I think PDF printing using the default PDF
viewer on the default DE with the default settings should not be broken
in jessie, especially since we have an easy fix by reverting the commit
which caused it. I'm not sure the current severity is appropriate?
I'm happy to help with additional testing.
Many thanks,
Chris
P.S. An easy way to test is to install `printer-driver-cups-pdf`, which
will show the behavior. ``Print to PDF'' in Evince seems to not. There
is a PDF attached to Samuel's first email in this thread which can be
used as a test case.
[1] Upstream bug report
https://bugzilla.gnome.org/show_bug.cgi?id=739723
[2] Upstream revert commit:
https://git.gnome.org/browse/evince/commit/?id=69b474fce1a87a0839e1f541f1297492e47c7c31
[3] Commit which was blamed and reverted by upstream and Fedora:
https://git.gnome.org/browse/evince/commit/?id=ae7a5715131613955a37419b5da1d6d9f3c1cb1d
[4] Fedora bug report:
https://git.gnome.org/browse/evince/commit/?id=69b474fce1a87a0839e1f541f1297492e47c7c31
diff -Nru evince-3.14.1/debian/changelog evince-3.14.1/debian/changelog
--- evince-3.14.1/debian/changelog
+++ evince-3.14.1/debian/changelog
@@ -1,3 +1,10 @@
+evince (3.14.1-1ocf2) UNRELEASED; urgency=medium
+
+ * Add debian/patches/revert-69b474fce1.patch (Closes: #768133)
+- from upstream git, reverts commit which broke landscape printing
+
+ -- Chris Kuehl cku...@ocf.berkeley.edu Fri, 30 Jan 2015 16:56:46 -0800
+
evince (3.14.1-1) unstable; urgency=medium
* New upstream release.
diff -Nru evince-3.14.1/debian/patches/revert-69b474fce1.patch
evince-3.14.1/debian/patches/revert-69b474fce1.patch
--- evince-3.14.1/debian/patches/revert-69b474fce1.patch
+++ evince-3.14.1/debian/patches/revert-69b474fce1.patch
@@ -0,0 +1,116 @@
+From: Carlos Garcia Campos carlo...@gnome.org
+Date: Wed, 28 Jan 2015 09:27:17 +0100
+Subject: Revert print-operation: Fix centering of documents when printing
+ with a manual scale
+
+This reverts commit ae7a5715131613955a37419b5da1d6d9f3c1cb1d.
+
+Fixed the centering of documents when using a manual scale, but it broke
+landscape printing, so reverting until we find a proper fix in both
+Evince and GTK+.
+
+Origin: upstream, https://git.gnome.org/browse/evince/commit/?id=69b474fce1a87a
+Bug: https://bugzilla.gnome.org/show_bug.cgi?id=739723
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768133
+
+--- a/libview/ev-print-operation.c
b/libview/ev-print-operation.c
+@@ -1825,27 +1825,6 @@ _print_context_get_hard_margins (GtkPrin
+ }
+
+ static void
+-ev_print_operation_print_get_scaled_page_size (EvPrintOperationPrint *print,
+- gint page,
+- gdouble *width,
+- gdouble *height)
+-{
+-GtkPrintSettings *settings;
+-gdouble manual_scale;
+-
+-ev_document_get_page_size (EV_PRINT_OPERATION (print)-document,
+- page, width, height);
+-
+-settings = gtk_print_operation_get_print_settings (print-op);
+-manual_scale = gtk_print_settings_get_scale (settings) / 100.0;
+-if (manual_scale == 1.0)
+-return;
+-
+-*width *= manual_scale;
+-*height *= manual_scale;
+-}
+-
+-static void
+ ev_print_operation_print_draw_page (EvPrintOperationPrint *print,
+ GtkPrintContext *context,
+ gint page)
+@@ -1855,7 +1834,6 @@
Bug#776869: libxml2: Bug with DTD parsing
Squeeze-lts is also affected. libxml2 (2.7.8.dfsg-2+squeeze10) is broken libxml2 (2.7.8.dfsg-2+squeeze8) works well. Thomas smime.p7s Description: S/MIME cryptographic signature
Bug#644472: caff: Support sending mails via MUA (such as mutt)
It would be nice to have an interface similar to reportbug. It first asks, wether one likes to use the MUA, then which one, e.g. mutt. This allows to add a personal message to the email. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699068: lynx: Cannot Type a Page-Number more than 999
I am so-glad others are still reporting this, as some time last year I tried submitting a Debian bug on this subject. When I view a complete list of Debian packages, its enough screens where no-matter in frebsd or Debian, I cannot type more than page 999, whether I have a 35line screen or 96lines. Thanks in advance Hart -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776895: pre-approval for TPU upload/ unblock: kwave/0.8.11-1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package kwave The attached debdiff fixes a FTBFS for kwave that has it pending removal. The fix cannot go via unstable because it already has a new upstream release. May I upload this to TPU? unblock kwave/0.8.11-1-2 diff -Nru kwave-0.8.11-1/debian/changelog kwave-0.8.11-1/debian/changelog --- kwave-0.8.11-1/debian/changelog 2013-12-07 17:26:53.0 -0500 +++ kwave-0.8.11-1/debian/changelog 2015-02-02 18:52:42.0 -0500 @@ -1,3 +1,11 @@ +kwave (0.8.11-1-2) testing-proposed-updates; urgency=medium + + * Team upload. + * Add debian/patches/fix-help_fr.po.patch from upstream to fix docbook +issues causing FTBFS (Closes: #775616) + + -- Scott Kitterman sc...@kitterman.com Mon, 02 Feb 2015 18:41:31 -0500 + kwave (0.8.11-1-1) unstable; urgency=low * New upstream release diff -Nru kwave-0.8.11-1/debian/patches/fix-help_fr.po.patch kwave-0.8.11-1/debian/patches/fix-help_fr.po.patch --- kwave-0.8.11-1/debian/patches/fix-help_fr.po.patch 1969-12-31 19:00:00.0 -0500 +++ kwave-0.8.11-1/debian/patches/fix-help_fr.po.patch 2015-02-02 18:41:15.0 -0500 @@ -0,0 +1,145 @@ +Author: Thomas Eschenbacher thomas.eschenbac...@gmx.de +Subject: Fixed missing entities in french online help (svn - git) +Origin: upstream, http://sourceforge.net/p/kwave/code/ci/0217487c/ +Last-Update: 2014-11-08 + +--- + doc/help_fr.po | 51 ++- + 1 file changed, 26 insertions(+), 25 deletions(-) + +Index: kwave-0.8.11-1/doc/help_fr.po +=== +--- kwave-0.8.11-1.orig/doc/help_fr.po 2015-02-02 18:38:38.388670118 -0500 kwave-0.8.11-1/doc/help_fr.po 2015-02-02 18:41:12.468676112 -0500 +@@ -360,15 +360,15 @@ + \url_git_web;\web interface/ulink you can use to browse through the + sources. + msgstr +-Il y a également un dépôt CVS, qui est hébergé par ulink url= ++Il y a également un dépôt GIT, qui est hébergé par ulink url= + \url_sourceforge;\SourceForge/ulink ou vous pouvez télécharger les + dernières versions des sources du programme. Pour toute information +-concernant la procédure d'accès au dépôt CVS, lisez le chapitre sur link +-linkend=\building_rpm_from_cvs\la construction à partir du CVS/link, +-consultez l'URL ulink url=\url_svn_instructions;\ +-\url_svn_instructions;\/ulink, ou visiter l'arborescence CVS ++concernant la procédure d'accès au dépôt GIT, lisez le chapitre sur link ++linkend=\building_rpm_from_git\la construction à partir du GIT/link, ++consultez l'URL ulink url=\url_git_instructions;\ ++\url_git_instructions;\/ulink, ou visiter l'arborescence GIT + directement à travers votre navigateur internet. emphasisUn accès anonyme +-au dépôt CVS est disponible !/emphasis ++au dépôt GIT est disponible !/emphasis + + #. Tag: title + #: help_en.docbook:220 +@@ -668,8 +668,8 @@ + If you intend to get the kwave; sources via GIT, you will also need a + current git package. + msgstr +-Si vous désirez utiliser CVS, il vous faut aussi la version actuelle du +-paquetage correspondant à CVS. ++Si vous désirez utiliser GIT, il vous faut aussi la version actuelle du ++paquetage correspondant à GIT. + + #. Tag: para + #: help_en.docbook:393 +@@ -889,10 +889,10 @@ + RPM. Premièrement, vous devez récupérer les sources de kwave;, tel que + l'archive au format « .tar.gz » disponible sur la page WEB de téléchargement + de kwave; ou une copie de la dernière version des sources via le link +-linkend=\cvs-repository\serveur CVS/link (comme cela est décrit dans le +-chapitre concernant le link linkend=\cvs_checkout\CVS/link), et lisez +-le chapitre concernant la link linkend=\building_rpm_from_cvs +-\compilation d'un RPM à partir du CVS/link. ++linkend=\git-repository\serveur GIT/link (comme cela est décrit dans le ++chapitre concernant le link linkend=\git_checkout\GIT/link), et lisez ++le chapitre concernant la link linkend=\building_rpm_from_git ++\compilation d'un RPM à partir du GIT/link. + + #. Tag: para + #: help_en.docbook:550 +@@ -,9 +,9 @@ + your provider doesn't give you full access. A good place for the source + files will be filename\$HOME/src\/filename. + msgstr +-Pour initialement vérifier la mise à jour des sources sur le CVS, vous avez ++Pour initialement vérifier la mise à jour des sources sur le GIT, vous avez + besoin d'un espace disque conséquent (environ 70 Mo) dans le dossier de +-votre choix, du paquetage correspondant au programme cvs dédié à votre ++votre choix, du paquetage correspondant au programme git dédié à votre + distribution, et d'un accès complet à internet. Si vous recevez un message + d'erreur pour des connexions qui sont rejetées, soit vous avez tapé des + commandes incorrectes, soit votre fournisseur d'accès à internet n'autorise +@@ -1153,7 +1153,7 @@ + #, fuzzy, no-c-format + msgid prompt%
Bug#699068: lynx: Cannot Type a Page-Number more than 999
On Sun, Feb 01, 2015 at 01:33:31PM +0100, Andreas Metzler wrote: On 2014-12-09 Thomas Dickey dic...@his.com wrote: On Fri, Jun 27, 2014 at 03:22:23PM +0900, Atsuhito Kohda wrote: Hi Hart, sorry for so late reply. On Sat, 26 Jan 2013 17:34:33 -0800, Larry Hart wrote: When browsing an item with more than 999 screens or pages, I am unable to type a number past 999. [...] https://packages.debian.org/testing/allpackages it is slow - but I am not seeing how to reproduce the problem. For instance if I type 0 1 2 3 0 p return I get the Follow link (or goto link or page) number: and can edit the line, and on pressing return, lynx shows page 1230 Hello Thomas, I can still reproduce this with 2.8.9dev4. Pressing 0 gives me the Follow link (or goto link or page) number:-prompt. However this prompt only accepts 4 characters of input, and therefore page 999 (999p) is the limit. I'm puzzled, since my own build of it works as I noted (just checked now). Running in a 40-line terminal, that gives this text at the top: Debian -- Software Packages in jessie (p1230 of 4978) libcommon-sense-perl (3.73-2+b1)^ module that implements some sane defaults for Perl programs ▒ ▒ Just as a sanity check, I did 04975p, and got (as expected) just a few screens before the end of the file. Perhaps there is some option-setting which is interfering - but I don't see that turning on the links/fields numbering changes anything. ametzler@argenau:/tmp/LYNX/lynx-cur-2.8.9dev4$ LANG=C lynx --version Lynx Version 2.8.9dev.4 (25 Jan 2015) libwww-FM 2.14, SSL-MM 1.4.1, GNUTLS 3.3.8, ncurses 5.9.20140913(wide) Built on linux-gnu Jan 26 2015 17:58:46 -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Bug#776863: Bug#776859: systemd-cron: uninstalling package dumps core and seemingly disturbs systemd
Quoting Alexandre Detiste (2015-02-02 18:23:38) - most (all ?) packages that depends on cron should instead depends on cron-daemon backintime-common is on my list: http://users.teledisnet.be/ade15809/cron-daemon.html but this is a migration that would happen after Jessie is released, so there is no point to file a bug now: https://lists.debian.org/debian-devel/2014/10/msg00474.html I already filed bugreport about that specifically for backintime-common - before hitting and reporting this instability issue. - and the worst: systemd shouldn't crash mysteriously sometimes when you call daemon-reload repeatedly ! http://lists.freedesktop.org/archives/systemd-devel/2014-January/016150.html If you could reproduce this, this would be great. Are you using v215 or v218 ? system is up-to-date Sid, so v218. Sorry, I cannot afford to provoke that same issue again. - 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#776893: gdb: pretty-printing C++ std::lists is broken sometimes
Package: gdb
Version: 7.7.1+dfsg-5
Severity: normal
Dear Maintainer,
it seems pretty-printing std::lists is broken sometimes. Consider the following
C++11 program:
8
#include iostream
#include string
#include list
class Msg {
public:
std::liststd::string params_;
std::liststd::string params() const { return params_; }
Msg(const std::liststd::string params) : params_(params) {
}
};
int main() {
std::liststd::string p = { foo, bar, baz };
Msg msg(p);// (A)
std::cout msg.params().size() std::endl; // prints 3
auto asdf = msg.params(); // (B)
for (auto a : msg.params()) {
std::cout a std::endl; // prints foo,
bar, baz
}
return 0;
}
8
When I step through the program, after line (A), printing msg.params_ yields
the correct list contents, but printing msg.params() yields garbled characters
and a list with 31 entries (see attached gdb log). Further investigation shows
that when I try to print msg.params().size(), I get Attempt to take address of
value not located in memory., and printing the variable asdf in line (B) also
yields the correct results.
All of this also happens with std::listint and std::listdouble, but not with
std::maps, std::vectors or std::sets. In any case, all values are printed
correctly to the console, so the underlying memory is apparently fine.
Thanks for listening,
- Roland
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (200, 'testing'), (170, 'unstable'), (150,
'testing-proposed-updates'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages gdb depends on:
ii libbabeltrace-ctf1 1.2.3-2
ii libbabeltrace1 1.2.3-2
ii libc6 2.19-13
ii libexpat1 2.1.0-6+b3
ii liblzma55.1.1alpha+20120614-2+b3
ii libncurses5 5.9+20140913-1+b1
ii libpython3.43.4.2-1
ii libreadline66.3-8+b2
ii libtinfo5 5.9+20140913-1+b1
ii zlib1g 1:1.2.8.dfsg-2+b1
Versions of packages gdb recommends:
ii gdbserver 7.7.1+dfsg-5
ii libc6-dbg [libc-dbg] 2.19-13
Versions of packages gdb suggests:
pn gdb-doc none
-- no debconf information
$ g++ -O0 -ggdb --std=c++11 test-return-std-list.cpp gdb -ex 'break main'
-ex r ./a.out
GNU gdb (Debian 7.8.2-1) 7.8.2
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from ./a.out...done.
Breakpoint 1 at 0x400dd6: file test-return-std-list.cpp, line 16.
Starting program: /home/rohieb/tmp/a.out
Breakpoint 1, main () at test-return-std-list.cpp:16
16 std::liststd::string p = { foo, bar, baz };
(gdb) n
18 Msg msg(p);
(gdb)
19 std::cout msg.params().size() std::endl;
(gdb) p msg.params_
$1 = std::list = {[0] = foo, [1] = bar, [2] = baz}
(gdb) p msg.params()
$2 = std::list = {[0] = foo, [1] = bar, [2] = baz,
[3] =
\240\060`\000\000\000\000\000\340\060`\000\000\000\000\000(0`\000\000\000\000\000X0`\000\000\000\000\000\210\060`\000\000\000\000\000\377\377\000\000\001\000\000\000\000\337\377\377\377\177\000\000\233\021@\000\000\000\000\000\002\000\000\000\000\000\000\000-\034@\000\000\000\000\000\001,
'\000' repeats 15 times, \340\033@, '\000' repeats 13 times,
\320\f@\000\000\000\000\000
\340\377\377\377\177\000\000\000\000\000\000\000\000\000\000E+#\367\377\177\000\000\000\000\000\000\000\000\000\000(\340\377\377\377\177\000\000\000\000\000\000\001\000\000\000\306\r@,
'\000' repeats 13 times, E)\231C\233\326h!\320\f@\000\000\000\000\000...,
[4] = foo, [5] = bar, [6] = baz,
[7] =
\240\060`\000\000\000\000\000\340\060`\000\000\000\000\000(0`\000\000\000\000\000X0`\000\000\000\000\000\210\060`\000\000\000\000\000\377\377\000\000\001\000\000\000\000\337\377\377\377\177\000\000\233\021@\000\000\000\000\000\002\000\000\000\000\000\000\000-\034@\000\000\000\000\000\001,
'\000' repeats 15 times, \340\033@, '\000' repeats 13 times,
\320\f@\000\000\000\000\000
Bug#776700: roundcube: CVE-2015-1433: Cross-site scripting vulnerability fixed in 1.0.5
Control: -1 reopen Tags: wheezy Source-Version: 0.9.5+dfsg1-4.2 We believe that the bug you reported is fixed in the latest version of roundcube, which is due to be installed in the Debian FTP archive. I did a quick(!) check of the code on wheezy and it seems to be the same, thus affected, too. Marian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670062: RFA: fofix-dfsg -- rhythm game in the style of Rock Band(tm) and Guitar Hero(tm)
There is some activity on github but it seems it is not enough for a new fofix release https://github.com/fofix/fofix The outlined way forward sounds promising: https://github.com/fofix/fofix/issues/30 Python3 and perhaps pySDL2 might be really an improvement over the current version. However if there is still no progress in a year from now on, I think we should consider removing fofix from Debian because it is quite similar to frets on fire and also unmaintained. Markus signature.asc Description: Digital signature
Bug#773354: please add breaks: live-tools ( 4.0.1-1)
First of all, many thanks to Gaudenz for looking into cleaning the live-* mess! On 2015-02-02 22:25, Gaudenz Steinlin wrote: That does not really help much because we don't need a list of packages that mention update-initramfs in some file but a list of packages that call update-initramfs in their maintainerscript without depending on initramfs-tools. I don't think codesearch is able to produce that list, but to me this seems like a quite special case. I would expect most packages that modify the initramfs to actually depend on initramfs-tools. We can easily check with piuparts if other packages are affected by this bug. Just needs someone to compile a list of candidate packages ... Or if someone wants to try it on its own: do wheezy - jessie upgrade tests of the packages you want to test and add the flags --extra-old-packages live-tools But I agree that probably more packages than just util-linux need fixing for this. But this is outside the scope of this bug and as long as no other bugs are filed, it's hard to track. I also don't see a viable solution to this bug which fixes all of these problems in one go. maybe a tracking bug against live-tools, since that package seems to be responsible I agree that fixing the problem with Breaks is a bit ugly and in theory adds the fix to the wrong package. But I currently don't see any viable other solution to this problem beside adding all these Breaks relations. An update to the stable version of live-tools does not seem practical to me. Do you see another way to fix this? A proper fix would probably require using a time machine to prevent some buggy uploads from having happened in the past ... But until this happens, we need to clean up the collateral damage caused by these diversions. And if someone looks for it systematically (and before the release), even better! Even if we could get something fixed in wheezy, there would be no guarantee that this update has been installed before upgrading to jessie. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776641: wmii window without blinking cursor
Hi, I run Kate and the Kate terminal works . Bye.
Bug#771988: RM: jspwiki/2.8.0-5 -- RoM, NBS
The build failure has been resolved and jspwiki no longer blocks the migration of tomcat6. So the removal is no longer important but jspwiki still needs a serious update. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776829: Please let me use PageUp/PageDown
Package: apvlv Version: 0.1.1-1.2+b1 Severity: wishlist PageUp/PageDown work fine in vim and should also in apvlv, please. IN fact, space to scroll down and backspace for up would be useful too. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apvlv depends on: ii libatk1.0-0 2.14.0-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libdjvulibre21 3.5.25.4-4+b1 ii libfontconfig1 2.11.0-6.3 ii libfreetype62.5.2-2 ii libgcc1 1:4.9.2-10 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgtk2.0-0 2.24.25-1 ii libpango1.0-0 1.36.8-3 ii libpoppler-glib80.26.5-2 ii libstdc++6 4.9.2-10 apvlv recommends no packages. Versions of packages apvlv suggests: ii poppler-data 0.4.7-1 -- debconf-show failed -- .''`. martin f. krafft madduck@d.o @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#775483: hexen: verify that the demo works in some packaged engine, and re-enable
On 02/02/15 07:58, Fabian Greffrath wrote: Am Freitag, den 16.01.2015, 09:46 + schrieb Simon McVittie: The Hexen demo (shareware version? incomplete version, anyway) is currently commented out because it crashes chocolate-doom We are working on it: https://github.com/chocolate-doom/chocolate-doom/commits/hexndemo Oh, that's good to hear - it seemed bad that the demo (in Debian) is not actually a realistic demo of what you would get (in Debian) if you bought the full game from Steam, because it defaults to a different engine that is more advanced but less faithful to the original game :-) I'd be happy to swap it back to chocolate-doom (= x.y) | hexen-engine when a suitable version is available - please open a bug when ready. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776279: please add support for the Doom 2 Master Levels
On 02/02/15 10:05, Alexandre Detiste wrote: If someone wants to write a generic Doom launcher/frontend and upload it to contrib separately (analogous to src:quake), that would be fine; we could make it a Recommends instead of shipping the Doom games' icons and desktop files in the g-d-p-produced packages. If I file an ITP for a spun-out launcher, would any of you sponsor it ? I'd certainly consider it, but my taste in gaming is not sufficiently retro to play much Doom, so it would be better if a fan of Doom (Fabian? Jon?) could look after it :-) If it gets generic enough, it could be just called doom. I recommend choosing names for things that are specific enough to avoid confusion, and let people know what you're referring to with some level of confidence. You should use doom to play Doom - confusing. doom-browser? doom-wad-launcher? Waddle? (You could maybe have a duck with a plasma rifle as an icon/mascot for that last one :-) S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776279: please add support for the Doom 2 Master Levels
On 02/02/15 10:32, Simon McVittie wrote: On 02/02/15 10:05, Alexandre Detiste wrote: If I file an ITP for a spun-out launcher, would any of you sponsor it ? A separate executable within g-d-p.deb, or a separate binary package from the same source, is another possibility - we can actually rely on the ability to update those. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776841: libgnutls28-dev: please make libgnutls-dev package multi-arch
Package: libgnutls28-dev Version: 3.3.8-4~bpo70+1 Severity: important Dear Maintainer, package libgnutls28-dev:amd64 offers all required file to build an application with GnuTLS on Debian amd64 architecture. Whereas libgnutls28-dev:i386 lacks some important files (libgnutls.a and the link libgnutls.so). Thus it is impossible to cross-compile to i386. * What led up to the situation? Cross-compiling an application with GnuTLS from amd64 to i386. * What exactly did you do (or not do) that was effective (or ineffective)? gcc -m32 * What was the outcome of this action? Link fails: /usr/bin/ld.bfd.real: cannot find -lgnutls * What outcome did you expect instead? That the package libgnutls28-dev:i386 offers the same files as libgnutls28-dev:amd64 : ll /usr/lib/*/libgnutls.so lrwxrwxrwx 1 root root 25 nov. 18 22:27 /usr/lib/x86_64-linux-gnu/libgnutls.so - libgnutls-deb0.so.28.41.0 ll /usr/lib/*/libgnutls.a -rw-r--r-- 1 root root 2435010 nov. 18 22:27 /usr/lib/x86_64-linux-gnu/libgnutls.a Regards, Michel -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (50, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-0.bpo.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 Versions of packages libgnutls28-dev depends on: ii libc6-dev [libc-dev] 2.13-38+deb7u6 ii libgnutls-deb0-28 3.3.8-4~bpo70+1 ii libgnutlsxx28 3.3.8-4~bpo70+1 ii libp11-kit-dev0.20.7-1~bpo70+1 ii libtasn1-6-dev4.2-2~bpo70+1 ii nettle-dev2.7.1-1~bpo70+1 ii zlib1g-dev1:1.2.7.dfsg-13 libgnutls28-dev recommends no packages. Versions of packages libgnutls28-dev suggests: ii gnutls-bin3.3.8-4~bpo70+1 ii gnutls-doc3.3.8-4~bpo70+1 ii guile-gnutls 3.3.8-4~bpo70+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#776842: cbmc: FTBFS on mips, mipsel, powerpc, s390x - testsuite failures
Source: cbmc Version: 5.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, cbmc FTBFS on mips, mipsel, powerpc and s390x with some testsuite errors. It looks like (after a quick skim of the logs) the failures are identical. The full logs with all the errors can be found here: https://buildd.debian.org/status/package.php?p=cbmc Thanks, James -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776781: wheezy-pu: package libdatetime-timezone-perl/1:1.58-1+2015a
On Sun, 01 Feb 2015 17:14:55 +, Adam D. Barratt wrote: On Sun, 2015-02-01 at 17:52 +0100, gregor herrmann wrote: I think we might want to get a new libdatetime-timezone-perl into wheezy, since there are chances to America/Cancun, effective today; either into the next point release or into stable-updates. Indeed, I had pondered that when the tzdata upload was mentioned earlier today. Please go ahead, thanks. Thanks, uploaded. Thank you a well for the unblock of the sid-and-soon-jessie version. 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 `- signature.asc Description: Digital Signature
Bug#776852: Please move ~/.apvlvinfo to $XDG_CACHE_HOME (default ~/.cache)
Package: apvlv Version: 0.1.1-1.2+b1 Severity: wishlist http://ploum.net/post/207-modify-your-application-to-use-xdg-folders https://live.gnome.org/GnomeGoals/XDGConfigFolders http://www.freedesktop.org/wiki/Specifications/basedir-spec -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apvlv depends on: ii libatk1.0-0 2.14.0-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libdjvulibre21 3.5.25.4-4+b1 ii libfontconfig1 2.11.0-6.3 ii libfreetype62.5.2-2 ii libgcc1 1:4.9.2-10 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgtk2.0-0 2.24.25-1 ii libpango1.0-0 1.36.8-3 ii libpoppler-glib80.26.5-2 ii libstdc++6 4.9.2-10 apvlv recommends no packages. Versions of packages apvlv suggests: ii poppler-data 0.4.7-1 -- debconf-show failed -- .''`. martin f. krafft madduck@d.o @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#776850: RFP: sx -- Scalable public and private cloud storage
retitle 776850 ITP: sx -- Scalable public and private cloud storage owner 776850 ! thanks On Mon, Feb 2, 2015 at 2:56 PM, Török Edwin ed...@skylable.com wrote: I am part of the upstream developers, and we would welcome if a DD (team) would submit and maintain this package in Debian. We are interested in helping with the packaging and applying bugfixes upstream. As previously noted, I'm intend to package it. Going to check the pull request over my old packaging. The source was monolithic in the past, but as I've read, it was resolved. Kind regards, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776643: ocamlweb: please make the build reproducible
Hi, Le 2015-01-30 14:17, Chris Lamb a écrit : While working on the reproducible builds effort [1], we have noticed that ocamlweb could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, ocamlweb can be built reproducibly in our current experimental framework. While I appreciate the efforts made on the reproducible builds project, I don't think that the attached patch should be applied as is : Showing a build date which is not the real build date is not helpful. I think we should try to make it optional instead. I think that something along these lines should do it: - Index: polygen-1.0.6.ds2-13/src/makefile === --- polygen-1.0.6.ds2-13/src/makefile +++ polygen-1.0.6.ds2-13/src/makefile @@ -16,8 +16,10 @@ MLLDOPTS = unix.cmxa MLLEX = ocamllex MLYACC = ocamlyacc +BUILD_DATE=yes + # must be linked in this order OBJS := ver.cmx \ prelude.cmx \ err.cmx \ @@ -53,9 +55,14 @@ @cat _parser.mli parser.mli @rm -f _parser.mli ver.ml: ver.ml.template - sed -e s/%VERSION%/$(VERSION)/ -e s/%DATE%/$(DATE)/ ver.ml.template ver.ml + sed s/%VERSION%/$(VERSION)/ver.ml.template ver.ml +ifeq($(BUILD_DATE),yes) +sed -i s/%DATE%/$(DATE)/ ver.ml +else +sed -i /%DATE%/d ver.ml +endif clean: rm -f *.o *.cm* a.out *.bak *.obj *~ *.annot *.stackdump parser.ml lexer.ml parser.mli ver.ml cat /dev/null .depend - (Not tested. Done quickly directly from the browser) Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776847: gsasl 1.8.0-6 does not support GSSAPI
Package: libgsasl7 Version: 1.8.0-6 Severity: important I think that fix for #745332 was incorrect. krb5-multidev does not contain krb5-config, so configure from gsasl can't find Kerberos via krb5-config and disable GSSAPI support. I think that Build-depends should look line libkrb5-dev | heimdal-dev Please re-enable GSSAPI support. -- With best wishes Max -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776848: xfce4-settings: xfsettingsd crashes when two monitor enabled
Package: xfce4-settings Version: 4.10.1-2 Severity: important Dear Maintainer, After a recent upgrade (month-old testing to testing), my custom keyboard shortbutys stopped working. This is caused by xfsettingsd crashing when it starts with dual-monitor enabled. The program 'xfsettingsd' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 146 error_code 8 request_code 140 minor_code 7) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) This is likely similar to https://bugzilla.xfce.org/show_bug.cgi?id=9680 With XFSETTINGSD_DEBUG=1 enabled, I see that the crash occurs after these lines: xfce4-settings(xsettings): _XSETTINGS_S0 registered on screen 0 xfce4-settings(xsettings): 26 settings changed (serial=0, len=1000) xfce4-settings(xsettings): resource manager (xft) changed (len=116) and before these: xfce4-settings(pointers): initialized xi 2.3 xfce4-settings(keyboards): initialized xkb 1.0 xfce4-settings(keyboards): set auto repeat on xfce4-settings(keyboards): set key repeat (delay=500, rate=50) xfce4-settings(keyboards): set numlock on xfce4-settings(accessibility): stickykeys disabled xfce4-settings(accessibility): slowkeys disabled xfce4-settings(accessibility): bouncekeys disabled xfce4-settings(accessibility): mousekeys disabled xfce4-settings(keyboard-shortcuts): 13 shortcuts loaded xfce4-settings(fontconfig): monitoring 71 paths xfce4-settings(workspaces): 8 desktop names set from xfconf If I start it with --sync to debug, it doesn't crash anymore. If I start it with a single monitor enabled (the other is plugged but disabled with xrandr --off) and later enable the second monitor, no problem. If I start it with the internal eDP1 panel disabled and the external monitor DP1 enabled, it enables eDP1 and crashes as above. So it looks something is wrong with the RANDR extension. Is there some place where xfsettings tries to remember RANDR setting? I would like to remove them. I also thought that my crazy monitor config could be involved (DP1 is rotated left, so eDP1 is larger than DP1 but DP1 is higher) but it fails the same with non-rotated screens. Note that xfce4-settings was not upgraded during my last update. xfce4-session seems to be the only important xfce package that was upgraded (4.10.1-8 - 4.10.1-10). Others are xfce4-battery-plugin, xfce4-notes, xfce4-notes-plugin, xfce4-terminal. xserver-xorg-core got upgraded 2:1.16.1-1 - 2:1.16.2.901-1 and quite a lot of X libraries got rebuilt but downgrading xserver-xorg-core didn't help. Brice -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-settings depends on: ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libdbus-1-3 1.8.12-3 ii libdbus-glib-1-20.102-1 ii libexo-1-0 0.10.2-4 ii libfontconfig1 2.11.0-6.3 ii libgarcon-1-0 0.2.1-2 ii libgarcon-common0.2.1-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgtk2.0-0 2.24.25-1 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-3 ii libx11-62:1.6.2-3 ii libxcursor1 1:1.1.14-1+b1 ii libxfce4ui-1-0 4.10.0-6 ii libxfce4util6 4.10.1-2 ii libxfconf-0-2 4.10.0-3 ii libxi6 2:1.7.4-1+b2 ii libxklavier16 5.2.1-1 ii libxrandr2 2:1.4.2-1+b1 ii xfconf 4.10.0-3 Versions of packages xfce4-settings recommends: ii x11-utils 7.7+2 ii xfce4-volumed 0.1.13-5 xfce4-settings 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#770871: ModemManager only starts up if system is PID 1
Hi all, On Mo 02 Feb 2015 11:10:59 CET, Didier 'OdyX' Raboud wrote: Le lundi, 2 février 2015 08.57:02, vous avez écrit : Could you add the patch file to this bug. It seems you forgot to attach it in your previous mail. Damn. :'( Here you go. OdyX OdyX! The patch works well (at least here)! THANKS+GREETS, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpA58dtCvgqT.pgp Description: Digitale PGP-Signatur
Bug#776723: unblock: winetricks/0.0+20141009+svn1208-2 (pre-approval)
Control: tags -1 - moreinfo On Sun, Feb 1, 2015 at 12:23 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: Please go ahead, and remove the moreinfo tag once the package has been accepted. Done. Cheers, Joseph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776391: [CVE-2015-0235]: heap-based buffer overflow in __nss_hostname_digits_dots()
The libc update unfortunately failed to restart the affected services because the postinst only does that when updating from a version 2.13: /var/lib/dpkg/info/libc6:i386.postinst: 142:if dpkg --compare-versions $preversion lt 2.13; then Could this be changed so that this update restarts most of the affected services? -- Mit freundlichen Grüßen, Martin v. Wittich IServ GmbH Bültenweg 73 38106 Braunschweig Telefon: 0531-2243666-0 Fax: 0531-2243666-9 E-Mail:i...@iserv.eu Internet: iserv.eu USt-IdNr. DE265149425 | Amtsgericht Braunschweig | HRB 201822 Geschäftsführer: Benjamin Heindl, Jörg Ludwig -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770871: [Pkg-utopia-maintainers] Bug#770871: ModemManager only starts up if system is PID 1
Hi OdyX, Am 02.02.2015 um 11:10 schrieb Didier 'OdyX' Raboud: Le lundi, 2 février 2015 08.57:02, vous avez écrit : Could you add the patch file to this bug. It seems you forgot to attach it in your previous mail. Damn. :'( Here you go. To keep the diff smaller, could you change the patch to simply use /* Do nothing if booted with systemd */ if (sd_booted()) return; for modem_manager_1_poke_cb() and modem_manager_1_poke(). A more verbose patch header would be great as well. Just add a few sentences that for MM we use runtime detection since we want the dbus autostart behaviour on !systemd for MM. Keep in mind, that we didn't replace all occurences of HAVE_SYSTEMD. Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#773591: Bug#775901: fixed in patch 2.7.3-1
On Mon, Feb 2, 2015 at 2:39 PM, Andreas Grünbacher andreas.gruenbac...@gmail.com wrote: It turned out that not allowing arbitrary symlinks causes many git-style kernel patches to fail: https://lkml.org/lkml/2015/1/26/522 Therefore, patch has been changed to resove paths in user space now; patch-2.7.4 should behave properly again. Yes, this is fixed in Debian now. I should check Debian #773591 [1]. On the other hand, upstream #44149 [2] will be fixed later, right? I think the best would be to disable that test on non-Linux platforms for now. Thanks, Laszlo/GCS [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773591 [2] http://savannah.gnu.org/bugs/?44149 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776845: Enable openmpi support in hdf5 package on hppa architecture (with patch)
Package: hdf5
Version: 1.8.13+docs-15
Severity: normal
Tags: patch
Can you please apply the attached patch which adds hppa to the architectures
which do support openmpi ?
openmpi support was added for hppa just recently with this patch:
bugs.debian.org/cgi-bin/bugreport.cgi?bug=776730
Thanks,
Helge
PS: Probably only the changes to debian/rules are necessary since the
debian/control file will generated then.
Nevertheless, I added both changes in this patch...diff -up ./debian/rules.org ./debian/rules
--- ./debian/rules.org 2015-02-02 10:28:49.159502351 +0100
+++ ./debian/rules 2015-02-02 10:29:20.903498981 +0100
@@ -41,7 +41,7 @@ DEFAULT_MPI=$(ARCH_DEFAULT_MPI_IMPL)
#ARCH_FLAG=-a
#ARCHS=any
ARCH_FLAG=-s
-OMPIARCHS?=alpha amd64 armel armhf arm64 i386 ia64 powerpc powerpcspe ppc64 ppc64el sparc sparc64 kfreebsd-i386 kfreebsd-amd64 hurd-i386 mips64 mips64el mips mipsel
+OMPIARCHS?=alpha amd64 armel armhf arm64 hppa i386 ia64 powerpc powerpcspe ppc64 ppc64el sparc sparc64 kfreebsd-i386 kfreebsd-amd64 hurd-i386 mips64 mips64el mips mipsel
MPICHARCHS?=any
ifeq (,$(or $(filter $(DEB_HOST_ARCH),$(OMPIARCHS)),$(filter any,$(OMPIARCHS
diff -up ./debian/control.org ./debian/control
--- ./debian/control.org 2015-02-02 10:27:48.871508827 +0100
+++ ./debian/control 2015-02-02 10:41:13.835397660 +0100
@@ -94,7 +94,7 @@ Description: Hierarchical Data Format 5
Package: libhdf5-openmpi-8
Section: libs
Priority: extra
-Architecture: alpha amd64 armel armhf arm64 i386 ia64 powerpc powerpcspe ppc64 ppc64el sparc sparc64 kfreebsd-i386 kfreebsd-amd64 hurd-i386 mips64 mips64el mips mipsel
+Architecture: alpha amd64 armel armhf arm64 hppa i386 ia64 powerpc powerpcspe ppc64 ppc64el sparc sparc64 kfreebsd-i386 kfreebsd-amd64 hurd-i386 mips64 mips64el mips mipsel
Depends: ${shlibs:Depends}, ${misc:Depends}
Pre-Depends: ${misc:Pre-Depends}
Multi-Arch: same
@@ -109,7 +109,7 @@ Description: Hierarchical Data Format 5
Package: libhdf5-openmpi-dev
Section: libdevel
Priority: extra
-Architecture: alpha amd64 armel armhf arm64 i386 ia64 powerpc powerpcspe ppc64 ppc64el sparc sparc64 kfreebsd-i386 kfreebsd-amd64 hurd-i386 mips64 mips64el mips mipsel
+Architecture: alpha amd64 armel armhf arm64 hppa i386 ia64 powerpc powerpcspe ppc64 ppc64el sparc sparc64 kfreebsd-i386 kfreebsd-amd64 hurd-i386 mips64 mips64el mips mipsel
Depends: libhdf5-openmpi-8 (= ${binary:Version}), zlib1g-dev,
libjpeg-dev, libopenmpi-dev, ${misc:Depends}
Suggests: libhdf5-doc
@@ -124,7 +124,7 @@ Description: Hierarchical Data Format 5
Package: libhdf5-openmpi-8-dbg
Section: debug
Priority: extra
-Architecture: alpha amd64 armel armhf arm64 i386 ia64 powerpc powerpcspe ppc64 ppc64el sparc sparc64 kfreebsd-i386 kfreebsd-amd64 hurd-i386 mips64 mips64el mips mipsel
+Architecture: alpha amd64 armel armhf arm64 hppa i386 ia64 powerpc powerpcspe ppc64 ppc64el sparc sparc64 kfreebsd-i386 kfreebsd-amd64 hurd-i386 mips64 mips64el mips mipsel
Depends: ${shlibs:Depends}, ${misc:Depends},
libhdf5-openmpi-8 (= ${binary:Version}),
Multi-Arch: same
Bug#776846: unblock: sigscheme/0.8.5-4.2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package sigscheme This fix bug #758710. It is FTBFS on arm64. Update symbols file for arm64 support, and add new patch file to update header file for arm64 building support. diff -Nru sigscheme-0.8.5/debian/changelog sigscheme-0.8.5/debian/changelog --- sigscheme-0.8.5/debian/changelog2014-04-17 16:44:10.0 +0900 +++ sigscheme-0.8.5/debian/changelog2015-01-27 19:00:22.0 +0900 @@ -1,3 +1,15 @@ +sigscheme (0.8.5-4.2) unstable; urgency=medium + + * Non-maintainer upload. + * fix FTBFS on arm64 (Closes: #758710). +thanks to Artur Rona ari-tc...@tlen.pl for picking from Ubuntu. +- debian/libgcroots0.symbols: add arm64 support. +- debian/patches/aarch64.diff: new patch to add arm64 support. + thanks to Matthias Klose d...@ubuntu.com. +- debian/patches/series: update. + + -- HIGUCHI Daisuke (VDR dai) d...@debian.org Tue, 27 Jan 2015 18:57:38 +0900 + sigscheme (0.8.5-4.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru sigscheme-0.8.5/debian/libgcroots0.symbols sigscheme-0.8.5/debian/libgcroots0.symbols --- sigscheme-0.8.5/debian/libgcroots0.symbols 2014-04-16 21:42:14.0 +0900 +++ sigscheme-0.8.5/debian/libgcroots0.symbols 2015-01-27 18:57:30.0 +0900 @@ -5,7 +5,7 @@ GCROOTS_init@Base 0.8.5 GCROOTS_is_protected@Base 0.8.5 GCROOTS_is_protected_context@Base 0.8.5 - (arch=!mips !mipsel !mipsn32 !mipsn32el !mips64 !mips64el !s390 !s390x)GCROOTS_jmp_buf@Base 0.8.5 + (arch=!mips !mipsel !mipsn32 !mipsn32el !mips64 !mips64el !s390 !s390x !arm64)GCROOTS_jmp_buf@Base 0.8.5 GCROOTS_mark@Base 0.8.5 GCROOTS_noop1@Base 0.8.5 GCROOTS_push_current_stack@Base 0.8.5 diff -Nru sigscheme-0.8.5/debian/patches/aarch64.diff sigscheme-0.8.5/debian/patches/aarch64.diff --- sigscheme-0.8.5/debian/patches/aarch64.diff 1970-01-01 09:00:00.0 +0900 +++ sigscheme-0.8.5/debian/patches/aarch64.diff 2015-01-27 18:57:30.0 +0900 @@ -0,0 +1,76 @@ +From: Matthias Klose d...@ubuntu.com +Description: Added AARCH64 support to gcconfig.h (libgcroots). It needs to get symbols file updated, as well. +Bug: https://groups.google.com/forum/#!topic/uim-en/fxixLmHXcq0 +Bug-Debian: http://bugs.debian.org/758710 +Origin: upstream, https://github.com/ctyler/libgcroots/commit/da6e6884a1119e2cf6be88b4cf5eb9091c52beeb + +Index: b/libgcroots/include/private/gcconfig.h +=== +--- a/libgcroots/include/private/gcconfig.h b/libgcroots/include/private/gcconfig.h +@@ -62,6 +62,13 @@ + # endif + + /* Determine the machine type: */ ++# if defined(__aarch64__) ++#define AARCH64 ++#if !defined(LINUX) ++# define NOSYS ++# define mach_type_known ++#endif ++# endif + # if defined(__arm__) || defined(__thumb__) + #define ARM32 + #if !defined(LINUX) !defined(NETBSD) +@@ -231,6 +238,10 @@ + #define IA64 + #define mach_type_known + # endif ++# if defined(LINUX) defined(__aarch64__) ++#define AARCH64 ++#define mach_type_known ++# endif + # if defined(LINUX) defined(__arm__) + #define ARM32 + #define mach_type_known +@@ -504,6 +515,7 @@ + /* running Amdahl UTS4 */ + /* S390 == 390-like machine */ + /* running LINUX */ ++ /* AARCH64== ARM AArch64 */ + /* ARM32 == Intel StrongARM */ + /* IA64 == Intel IPF */ + /*(e.g. Itanium)*/ +@@ -1724,6 +1736,32 @@ + # endif + # endif + ++# ifdef AARCH64 ++# define CPP_WORDSZ 64 ++# define MACH_TYPE AARCH64 ++# define ALIGNMENT 8 ++# ifndef HBLKSIZE ++# define HBLKSIZE 4096 ++# endif ++# ifdef LINUX ++# define OS_TYPE LINUX ++# define LINUX_STACKBOTTOM ++# define USE_GENERIC_PUSH_REGS ++# define DYNAMIC_LOADING ++ extern int __data_start[]; ++# define DATASTART ((ptr_t)__data_start) ++ extern char _end[]; ++# define DATAEND ((ptr_t)(_end)) ++# endif ++# ifdef NOSYS ++ /* __data_start is usually defined in the target linker script. */ ++ extern int __data_start[]; ++# define DATASTART ((ptr_t)__data_start) ++ extern void *__stack_base__; ++# define STACKBOTTOM ((ptr_t)__stack_base__) ++# endif ++# endif ++ + # ifdef ARM32 + # define CPP_WORDSZ 32 + # define MACH_TYPE ARM32 diff -Nru sigscheme-0.8.5/debian/patches/series sigscheme-0.8.5/debian/patches/series --- sigscheme-0.8.5/debian/patches/series 2014-04-16 21:36:19.0 +0900 +++ sigscheme-0.8.5/debian/patches/series 2015-01-27 18:57:30.0 +0900 @@ -7,3 +7,4 @@ test-gc-protect-0.8.5
Bug#776849: sshfs mount does not get logged (w/last)
Package: sshfs Version: 2.5-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** when mounting a remote filesystem via sshfs, the access is not logged in the server , w.g. w or last has NO results. this breaks security and logging. *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sshfs depends on: ii fuse2.9.3-15+b1 ii libc6 2.19-13 ii libfuse22.9.3-15+b1 ii libglib2.0-02.42.1-1 ii openssh-client 1:6.7p1-3 sshfs recommends no packages. sshfs 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#776850: RFP: sx -- Scalable public and private cloud storage
Package: wnpp Severity: wishlist * Package name: sx Version : 1.0 Upstream Author : Skylable Dev Team dev-t...@skylable.com * URL : http://www.skylable.com/products/sx * License : GPL-2 with OpenSSL exception Programming Lang: C Description : Scalable public and private cloud storage Skylable Sx is a reliable, fully distributed cluster solution for your data storage needs. . With Sx you can aggregate the disk space available on multiple servers and merge it into a single storage system. The cluster makes sure that your data is always replicated over multiple nodes (the exact number of copies is defined by the sysadmin) and synchronized. . Additionally Sx has built-in support for deduplication, client-side encryption, on-the-fly compression and much more. I am part of the upstream developers, and we would welcome if a DD (team) would submit and maintain this package in Debian. We are interested in helping with the packaging and applying bugfixes upstream. Preliminary packaging available at https://github.com/gcsideal/sx-debian/pull/1: $ git clone https://github.com/edwintorok/sx-debian cd sx-debian git checkout pristine-tar git checkout debian $ git-buildpackage -us -uc -j8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776851: reprepro: please add different database backends
Package: reprepro Severity: wishlist Reprepro work great, i think that can be very useful if we can use another database backend like mysql or pg, its are more easy to backup, interface with another tools like web frontend , etc.. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.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#776821: icu-devtools is wrongly marked Multi-Arch:foreign
On Mon, 2 Feb 2015 08:43:14 +0100 Helmut Grohne hel...@subdivi.de wrote: Package: icu-devtools Version: 52.1-7 Severity: serious Justification: can cause other packages to FTBFS User: helm...@debian.org Usertags: rebootstrap The icu-devtools is marked as Multi-Arch:foreign. It contains the icu-config program, which exposes architecture dependent paths. By accidentally installing a wrong-arch icu-devtools, builds that use libicu-dev (even natively) fail (execution of icu-config fails sanity check). While this is unlikely to happen on buildds (as they generally don't enable multiarch), it is possible on developer machines. An immediate remedy to solve this bug is to remove M-A:foreign from icu-devtools and is what I would propose for jessie. As a mid term solution, I propose moving icu-config from icu-devtools to libicu-dev. Then icu-devtools should be able to become M-A:foreign again. Of course, libicu-dev must be M-A:no then and it certainly must be M-A:no as long as icu-config is in use. The long term solution is to move to pkg-config and remove icu-config entirely. I do not agree with severity of this bug report, as no other packages are FTBFS caused by this issue. It is known that icu-config (and similar legacy/pre-pkg-config *-config binaries) are not multiarch aware, and only ever output results for the architecture they were compiled. Due to this, it is clearly a M-A:foreign package, and it is up to the user to pull in the right arch one which in most cases is the icu-devtools:native one. Are there any existing dependencies in the archive that cause to pull in a wrong arch icu-devtools and produce undesired effects? Regards, Dimitri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776643: ocamlweb: please make the build reproducible
*Sigh* I took polygen instead of ocamlweb... I should get more coffee. Sorry. The idea is the same anyway. I can have a look after Jessie's release. (I don't think it is urgent). Le 2015-02-02 13:47, Mehdi Dogguy a écrit : Hi, Le 2015-01-30 14:17, Chris Lamb a écrit : While working on the reproducible builds effort [1], we have noticed that ocamlweb could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, ocamlweb can be built reproducibly in our current experimental framework. While I appreciate the efforts made on the reproducible builds project, I don't think that the attached patch should be applied as is : Showing a build date which is not the real build date is not helpful. I think we should try to make it optional instead. I think that something along these lines should do it: - Index: polygen-1.0.6.ds2-13/src/makefile === --- polygen-1.0.6.ds2-13/src/makefile +++ polygen-1.0.6.ds2-13/src/makefile @@ -16,8 +16,10 @@ MLLDOPTS = unix.cmxa MLLEX = ocamllex MLYACC = ocamlyacc +BUILD_DATE=yes + # must be linked in this order OBJS := ver.cmx \ prelude.cmx \ err.cmx \ @@ -53,9 +55,14 @@ @cat _parser.mli parser.mli @rm -f _parser.mli ver.ml: ver.ml.template - sed -e s/%VERSION%/$(VERSION)/ -e s/%DATE%/$(DATE)/ ver.ml.template ver.ml + sed s/%VERSION%/$(VERSION)/ver.ml.template ver.ml +ifeq($(BUILD_DATE),yes) +sed -i s/%DATE%/$(DATE)/ ver.ml +else +sed -i /%DATE%/d ver.ml +endif clean: rm -f *.o *.cm* a.out *.bak *.obj *~ *.annot *.stackdump parser.ml lexer.ml parser.mli ver.ml cat /dev/null .depend - (Not tested. Done quickly directly from the browser) Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770135: ssh logins considerably delayed (until PAM timeout) when systemd is upgraded but the system not rebooted
I can confirm the same behavior. After restart the service systemctl restart systemd-logind.service login works normal again thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775901: fixed in patch 2.7.3-1
It turned out that not allowing arbitrary symlinks causes many git-style kernel patches to fail: https://lkml.org/lkml/2015/1/26/522 Therefore, patch has been changed to resove paths in user space now; patch-2.7.4 should behave properly again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776832: warning: #warning you should set MAGICKCORE_QUANTUM_DEPTH to sensible default set it to configure time default
Package: cmake-data Version: 3.0.2-1 Severity: important Tags: upstream Dear Maintainer, the ImageMagick module appears to be incompatible with imagemagick current version in jessie. When compiling, one gets: /usr/include/ImageMagick-6/magick/magick-config.h:29:3: warning: #warning you should set MAGICKCORE_QUANTUM_DEPTH to sensible default set it to configure time default [-Wcpp] # warning you should set MAGICKCORE_QUANTUM_DEPTH to sensible default set it to configure time default ^ /usr/include/ImageMagick-6/magick/magick-config.h:30:3: warning: #warning this is an obsolete behavior please fix your makefile [-Wcpp] # warning this is an obsolete behavior please fix your makefile ^ /usr/include/ImageMagick-6/magick/magick-config.h:52:3: warning: #warning you should set MAGICKCORE_HDRI_ENABLE to sensible default set it to configure time default [-Wcpp] # warning you should set MAGICKCORE_HDRI_ENABLE to sensible default set it to configure time default ^ /usr/include/ImageMagick-6/magick/magick-config.h:53:3: warning: #warning this is an obsolete behavior please fix yours makefile [-Wcpp] # warning this is an obsolete behavior please fix yours makefile ^ Instead the cmake / imagemagick module should use the pkg-config internally or update it's own implementation to follow: $ pkg-config --cflags ImageMagick -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -- 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) 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) -- 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#776833: diffpdf: Homepage field incorrect or not relevant anymore?
Package: diffpdf Version: 2.1.3-1+b1 Severity: minor Hi, I visited http://www.qtrac.eu/diffpdf.html, the URL in the Homepage field and found a commercial, proprietary tool for Windows only. According to http://www.qtrac.eu/diffpdfc-changes.html the diffpdf program started with version 3.0.0 being renamed from a tool called comparepdf. Could you fix the Homepage field to point to the actual homepage of diffpdf in Debian? Thanks! cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776834: sshd_config doesn't recognize VersionAddendum keyword
Package: vim-runtime Version: 2:7.4.488-4 Severity: minor Hello When editing /etc/ssh/sshd_config, DebianBanner is hilighted, but VersionAddendum is not. Please refresh the list of keywords. man sshd_config may be a source for these. Thank you for taking good care of vim. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) vim-runtime depends on no packages. Versions of packages vim-runtime recommends: ii vim 2:7.4.488-4 vim-runtime suggests no packages. -- no debconf information signature.asc Description: OpenPGP digital signature
Bug#776279: please add support for the Doom 2 Master Levels
A separate executable within g-d-p.deb I see g-d-p as a build-depedency of the data packages, not a runtime one; we can't expect it's there, I share some wad (legally) using a local repository; and there is no dev stuff on the other PC. , or a separate binary package, from the same source, is another possibility Ok, this is nice, there are already many doom- specific bits in GDP source anyway. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769997: ITP: 4ti2 -- algebraic, geometric and combinatorial problems on linear spaces
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, the 4ti2 package is now in the NEW queue. Enjoy, Jerome -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJUz1dSAAoJEIC/w4IMSybjCQ8H/iLt5PZWMXhGP9HTh9c3ZSxo TImnPk+fJ2AnqO+E7gcc1IjkZWHaGb3+p+CJHo9uSVHaiMDPE9M4GsoXDI4XprHU r3OebjiBlNk4HoTY5Bmx/e5sBDR70j5pomvGd2smbS2meIJbOns+pvVmURVLqP4n AXOgmq468CzDhvoKyhy6kpFpwvrygynoJYeCNwhe55438LU1WBvsvrmqcpYJTtcf A5LrwiKsySsoJJzXFyukxZ5JYG0t6MOu3+9enp4fwIB8XdS/muG5W9Vu67geaTV6 bxmkf0voC9XQodhWMRH7tBUf/jdG7ekwrtIU7Z1XVAQWbF5elcrNshUH0psSSxQ= =IKBV -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#776279: please add support for the Doom 2 Master Levels
On 01/02/15 13:41, Alexandre Detiste wrote: The disadvantage of this set is that all maps are in individual PWADs and often occupy the same map slot, so they need to get loaded and played separately. Ideally, the package g-d-p creates for them comes with a Zenity frontend that allows for selecting one of them and automatically calls 'doom-engine' with the correct '-file' and '-warp' parameters. Can you provide the appropriates -file -warp parameters for all ther files ? I would really rather not put any executable code in game-data-packager-produced packages, beyond what is strictly necessary for backwards compat (the maintainer scripts that remove old alternatives) - they cannot be updated automatically, so we should assume that, in practice, all users will have an outdated version of the game data packages. This means that when we find bugs in executable code in a g-d-p-produced package, we cannot reliably fix them. If someone wants to write a generic Doom launcher/frontend and upload it to contrib separately (analogous to src:quake), that would be fine; we could make it a Recommends instead of shipping the Doom games' icons and desktop files in the g-d-p-produced packages. I'm happy to include declarative information about the packaged games, such as a dummy executable or symlink to a real executable suitable for use with .desktop files' TryExec feature (see quake, quake2, quake3), if that makes the frontend's job easier - but, again, we can't rely on being able to update it, so minimal complexity is better. I would suggest using a nicer programming language than shell. g-d-p has fewer sharp edges now that it's written in Python 3, and one day I plan to bolt on a PyGI-based Gtk GUI. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776838: System freezes with borked graphics
Package: xserver-xorg-video-nouveau Version: 1:1.0.11-1 When I install Debian 8 jessie and boot into the new system, very soon I get borked graphics and the system freezes. I tried several desktop environments - Cinnamon, GNOME, GNOME Classic and Xfce - and two display managers - gdm and lightdm - it always happens. Sometimes it happens already in the display manager, sometimes only after I start iceweasel. I habe a ASROCK AM2NF6G-VSTA-mainboard with a NVIDIA GeForce 6100 / nForce 405 (C61) GPU. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776839: unblock: libgit2/0.21.3-1.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libgit2 The newer version of the libgit2 package fixes a security hole [0]. Sorry I realise that this is the second unblock request for this package. But at the time of the previous request I did not think that the vulnerability met the requirements for an unblock request. I have since been contacted by the Debian security team and asked to submit an unblock request. I haven't split out the fix into a separate patch on the existing package in jessie as it's probably not super easy. But i can do it if it's required. I have not inculded a debdiff since it's 182K but I can attach it if needed. 0. https://security-tracker.debian.org/tracker/CVE-2014-9390 unblock libgit2/0.21.3-1.1 -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash 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#776840: apt: Cannot install vera++ without other regex-matching packages
Package: apt Version: 1.0.9.6 Severity: normal Tags: upstream Dear Maintainer, When installing vera++, it considers vera++ as a regex, and selects a lot of unrelated packages: # apt-get install -s vera++ Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libtest-pod-coverage-perl' for regex 'vera+' Note, selecting 'libcoverart-dbg' for regex 'vera+' Note, selecting 'vera++' for regex 'vera+' Note, selecting 'libcoverart-dev' for regex 'vera+' Note, selecting 'libpod-coverage-trustpod-perl' for regex 'vera+' Note, selecting 'libcoverart-doc' for regex 'vera+' Note, selecting 'ruby-coveralls' for regex 'vera+' Note, selecting 'libcoverart0' for regex 'vera+' Note, selecting 'python3-coverage' for regex 'vera+' Note, selecting 'dict-vera' for regex 'vera+' Note, selecting 'php-codecoverage' for regex 'vera+' Note, selecting 'node-jscoverage' for regex 'vera+' Note, selecting 'vera' for regex 'vera+' Note, selecting 'python-coverage' for regex 'vera+' Note, selecting 'ttf-bitstream-vera' for regex 'vera+' Note, selecting 'ttf-adf-verana' for regex 'vera+' Note, selecting 'python3-coverage-dbg' for regex 'vera+' Note, selecting 'python-coverage-dbg' for regex 'vera+' Note, selecting 'banshee-extension-liveradio' for regex 'vera+' Note, selecting 'libpod-coverage-perl' for regex 'vera+' Note, selecting 'python-coverage-test-runner' for regex 'vera+' A trick is to add a '+', but this is odd: # apt-get install -s vera+++ Also, escaping the '+' does not work: # apt-get install -s 'vera\+\+' … E: Couldn't find any package by regex 'vera\+\' However, this works: # apt-get install -s 'vera\+\+$' -- Package-specific info: -- apt-config dump -- APT ; APT::Architecture amd64; APT::Build-Essential ; APT::Build-Essential:: build-essential; APT::Install-Recommends true; APT::Install-Suggests 0; APT::Authentication ; APT::Authentication::TrustCDROM true; APT::NeverAutoRemove ; APT::NeverAutoRemove:: ^firmware-linux.*; APT::NeverAutoRemove:: ^linux-firmware$; APT::NeverAutoRemove:: ^linux-image-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-image-3\.16-3-amd64$; APT::NeverAutoRemove:: ^linux-headers-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-headers-3\.16-3-amd64$; APT::NeverAutoRemove:: ^linux-image-extra-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-image-extra-3\.16-3-amd64$; APT::NeverAutoRemove:: ^linux-signed-image-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-signed-image-3\.16-3-amd64$; APT::NeverAutoRemove:: ^kfreebsd-image-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^kfreebsd-image-3\.16-3-amd64$; APT::NeverAutoRemove:: ^kfreebsd-headers-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^kfreebsd-headers-3\.16-3-amd64$; APT::NeverAutoRemove:: ^gnumach-image-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^gnumach-image-3\.16-3-amd64$; APT::NeverAutoRemove:: ^.*-modules-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^.*-modules-3\.16-3-amd64$; APT::NeverAutoRemove:: ^.*-kernel-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^.*-kernel-3\.16-3-amd64$; APT::NeverAutoRemove:: ^linux-backports-modules-.*-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-backports-modules-.*-3\.16-3-amd64$; APT::NeverAutoRemove:: ^linux-tools-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-tools-3\.16-3-amd64$; APT::VersionedKernelPackages ; APT::VersionedKernelPackages:: linux-image; APT::VersionedKernelPackages:: linux-headers; APT::VersionedKernelPackages:: linux-image-extra; APT::VersionedKernelPackages:: linux-signed-image; APT::VersionedKernelPackages:: kfreebsd-image; APT::VersionedKernelPackages:: kfreebsd-headers; APT::VersionedKernelPackages:: gnumach-image; APT::VersionedKernelPackages:: .*-modules; APT::VersionedKernelPackages:: .*-kernel; APT::VersionedKernelPackages:: linux-backports-modules-.*; APT::VersionedKernelPackages:: linux-tools; APT::Never-MarkAuto-Sections ; APT::Never-MarkAuto-Sections:: metapackages; APT::Never-MarkAuto-Sections:: restricted/metapackages; APT::Never-MarkAuto-Sections:: universe/metapackages; APT::Never-MarkAuto-Sections:: multiverse/metapackages; APT::Never-MarkAuto-Sections:: oldlibs; APT::Never-MarkAuto-Sections:: restricted/oldlibs; APT::Never-MarkAuto-Sections:: universe/oldlibs; APT::Never-MarkAuto-Sections:: multiverse/oldlibs; APT::Update ; APT::Update::Post-Invoke-Success ; APT::Update::Post-Invoke-Success:: [ ! -f /var/run/dbus/system_bus_socket ] || /usr/bin/dbus-send --system --dest=org.debian.apt --type=signal /org/debian/apt org.debian.apt.CacheChanged || true; APT::Update::Post-Invoke-Success:: /usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service /usr/bin/test -S /var/run/dbus/system_bus_socket /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update /dev/null; /bin/echo /dev/null; APT::Architectures ; APT::Architectures:: amd64; APT::Compressor ;
