Bug#730515: cd-hit-est is cdhit-est in Debian [Why?]
Hi, any news about the naming cd-hit versus cdhit? Is the name intentionally choosen and should be fixed in python-cogent? Kind regards Andreas. - Forwarded message from Andreas Tille andr...@an3as.eu - Date: Tue, 26 Nov 2013 09:25:43 +0100 From: Andreas Tille andr...@an3as.eu To: 730...@bugs.debian.org, Weizhong Li l...@sdsc.edu Subject: Bug#730515: cd-hit-est is cdhit-est in Debian [Why?] X-Debian-PR-Message: followup 730515 X-Debian-PR-Package: src:cd-hit,src:python-cogent X-Debian-PR-Keywords: X-Debian-PR-Source: cd-hit,src:python-cogent Hi, as you can read below a Debian user has made some IMHO valid point about naming inconsistencies in cd-hit. I think this should be addressed by the upstream developer and thus I'm forwarding this issue to you with the kind question, how we should choose some proper naming for the different tools. It also might be that we misunderstood something and that your different naming pattern might have some deeper sense. Kind regards and thanks for providing cd-hit as free software Andreas. On Mon, Nov 25, 2013 at 04:35:20PM -0800, Don Armstrong wrote: Package: src:cd-hit,src:python-cogent Control: found -1 cd-hit/4.6.1-2012-08-27-2 Control: found -1 python-cogent/1.5.3-2 Severity: normal python-cogent refers to cd-hit-est, which I presume is the standard upstream naming for cd-hit. However, in Debian, the cd-hit package installs cd-hit-est as cdhit-est. I don't know which is correct, but either cd-hit or python-cogent should be fixed (or both!) Secondarily, cd-hit really should decide whether it is called cd-hit or cdhit, as it installs some commands called cd-hit and others called cdhit: /usr/bin/cd-hit-div /usr/bin/cdhit-est /usr/bin/psi-cd-hit-local /usr/bin/cd-hit-2d-para /usr/bin/psi-cd-hit-2d /usr/bin/psi-cd-hit /usr/bin/psi-cd-hit-2d-g1 /usr/bin/cdhit-454 /usr/bin/cdhit-2d /usr/bin/cdhit-est-2d /usr/bin/cd-hit-para /usr/bin/cdhit -- Don Armstrong http://www.donarmstrong.com Do you need [...] [t]ools? Stuff? Our opponent is an alien starship packed with atomic bombs. [...] We have a protractor. -- Neal Stephenson _Anathem_ p320 ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging - End forwarded message - -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731763: This bug also happens on my Debian jessie
root@Debian-X230:~# aptitude upgrade
Resolving dependencies...
The following NEW packages will be installed:
libclang-common-3.3-dev{a}
The following partially installed packages will be configured:
clang clang-3.3
0 packages upgraded, 1 newly installed, 0 to remove and 30 not upgraded.
Need to get 0 B/294 kB of archives. After unpacking 3,663 kB will be used.
Do you want to continue? [Y/n/?]
(Reading database ... 259623 files and directories currently installed.)
Preparing to unpack .../libclang-common-3.3-dev_1%3a3.3-15_amd64.deb ...
Unpacking libclang-common-3.3-dev (1:3.3-15) ...
dpkg: error processing archive
/var/cache/apt/archives/libclang-common-3.3-dev_1%3a3.3-15_amd64.deb
(--unpack):
trying to overwrite '/usr/lib/llvm-3.3/lib/libprofile_rt.a', which is also
in package libclang-common-dev 1:3.3~svn177638-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libclang-common-3.3-dev_1%3a3.3-15_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
dpkg: dependency problems prevent configuration of clang-3.3:
clang-3.3 depends on libclang-common-3.3-dev (= 1:3.3-15); however:
Package libclang-common-3.3-dev is not installed.
dpkg: error processing package clang-3.3 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of clang:
clang depends on clang-3.3 (= 3.3-1~); however:
Package clang-3.3 is not configured yet.
dpkg: error processing package clang (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
clang-3.3
clang
root@Debian-X230:~# more /etc/issue
Debian GNU/Linux jessie/sid \n \l
root@Debian-X230:~# uname -a
Linux Debian-X230 3.10.23 #5 SMP Tue Dec 10 17:46:58 CST 2013 x86_64
GNU/Linux
root@Debian-X230:~# dpkg -l|grep clang
iU clang 1:3.3-21
amd64C, C++ and Objective-C compiler (LLVM based)
iU clang-3.3 1:3.3-15
amd64C, C++ and Objective-C compiler (LLVM based)
ii libclang-common-dev1:3.3~svn177638-1
amd64clang library - Common development package
ii libclang1:amd641:3.3-21
amd64C, C++ and Objective-C compiler (LLVM based)
ii libclang1-3.3:amd641:3.3-15
amd64C interface to the clang library
root@Debian-X230:~#
--
--
KDr2, http://kdr2.net
Bug#732109: base: /etc/pam.d/sshd overides setting up LANG from a ssh sessions.
Package: base Severity: normal Tags: l10n -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash We use wheezy, jessie and ubuntu too, and some are UTF8, others ISO8859-1. It may not be a good idea that the server sets the locale from /etc/pam.d/sshd. The terminal we use, (PuTTY par example) is already set with it's own locale, and the locale to use for a session should be that one from the terminal, not the one set by sshd. Do you agree? In case you do, can you comment line 44 in /etc/pam.d/sshd. The others config files (login, lightdm...) are ok since access is done localy. But when the access is remote from the servern the locale to use is set by the terminal, and line 44 overides the work done at the terminal :) Thanks a lot ! Denis Gillain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732110: nagios-plugins-contrib: check_rbl error when nameserver available only in IPv6
Package: nagios-plugins-contrib Version: 4.20120702 Severity: normal Hello, $ cat /etc/resolv.conf nameserver ::1 $ ./check_rbl -H 2.0.0.127.bl.spamcop.net -w 0 -c 0 -s bl.spamcop.net Use of uninitialized value $sock in hash element at ./check_rbl line 157. Use of uninitialized value $sock in hash element at ./check_rbl line 157. CHECK_RBL OK - 2.0.0.127.bl.spamcop.net BLACKLISTED on 0 servers of 1 | servers=0;0;0 time=0s;; [edit resolv.conf] $ cat /etc/resolv.conf nameserver ::1 nameserver 127.0.0.1 $ ./check_rbl -H 2.0.0.127.bl.spamcop.net -w 0 -c 0 -s bl.spamcop.net CHECK_RBL CRITICAL - 2.0.0.127.bl.spamcop.net BLACKLISTED on 1 server of 1 (bl.spamcop.net) | servers=1;0;0 time=0s;; I don't understand why check_rbl does not work with a nameserver available only in IPv6. I can accept the requirement. Nonetheless the test should fail if it cannot resolve correctly. I extracted the script from the debian package in unstable (8.20130824), and it presents the same behaviour. Regards, Benoit -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (990, 'stable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-042stab081.8 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash nagios-plugins-contrib depends on no packages. Versions of packages nagios-plugins-contrib recommends: pn freeipmi-toolsnone ii libc6 2.17-97 pn libdate-manip-perlnone ii libio-socket-ssl-perl 1.76-2 pn libipc-run-perl none ii liblocale-gettext-perl1.05-7+b1 pn liblwp-useragent-determined-perl none ii libmail-imapclient-perl 3.31-2 pn libmemcached10none ii libnagios-plugin-perl 0.36-1 ii libnet-dns-perl 0.66-2+b2 ii libnet-smtp-tls-perl 0.12-1 pn libnet-snmp-perl none ii libnet-ssleay-perl1.48-1+b1 ii libreadonly-perl 1.03-4 pn libyaml-syck-perl none ii lsof 4.86+dfsg-1 ii openssl 1.0.1e-2 ii python2.7.3-4+deb7u1 pn ruby | ruby-interpreter none pn snmp none Versions of packages nagios-plugins-contrib suggests: pn backuppc none pn cciss-vol-status none pn expectnone pn mpt-statusnone pn perl-doc 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#732111: ERROR: wget failed to download http://people.debian.org/~bartm/flashplugin-nonfree/get-upstream-version.pl.gz.pgp
Package: flashplugin-nonfree One will always get this error Setting up flashplugin-nonfree (1:3.4) ... ERROR: wget failed to download http://people.debian.org/~bartm/flashplugin-nonfree/get-upstream-version.pl.gz.pgp More information might be available at: http://wiki.debian.org/FlashPlayer Despite one being on-line, and later being able do use wget to get that file. Workaround # update-flashplugin-nonfree --install -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732025: kanla: fills harddisk with seems to be working messages
Hi Jonas, Jonas Smedegaard d...@jones.dk writes: 1) If you install kanla, you will start configuring it. If you don’t intend to use it, why install it? Or at least why have it enabled? Debian daemons should be configured for normal working condition by default. I believe that's a should in Debian Policy. I agree with that in principle, but how would it be applicable to kanla? The package cannot know which things to monitor and where to send alerts to. There just is no way to have it in “normal working condition” unless you configure it. 2) When first configuring kanla, it is helpful to have a quick way of testing that messages successfully arrive at the destination address, which this default setting provides. If one wants debugging output, onewould enable optional features for that, not expect it to be enabled by default. I disagree. It is tempting and likely that without this message, people would configure kanla, say “this looks about right” and never get any alerts. Having a sightly annoying default configuration to err on the side of caution is the right thing, IMO. 4) When using systemd (and journald with that), you have logrotation by default (well, in Debian that is no persistent logging at all, and a memory ringbuffer currently). The legacy init support is intentionally quite sparse, because it doesn’t make sense to spend time on re-implementing the wheel in that area in 2013 (well, soon 2014 :)). Last I checked, systemd wasn't default in Debian. Please include in the kanla package a logrotate snippet and recommend logrotate. I don’t have any non-systemd machine. If you care about such a setup, please submit a patch. Thanks! -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732112: urlwatch: Change in lynx handling of relative URLs confuses html2txt.py
Package: urlwatch Version: 1.15-3 Severity: normal Dear Maintainer, I noticed that shortly after lynx in Debian testing moved to a new version, I got spurious reports in the urlwatch that I run as a cron job. Example: *** CHANGED: http://www.example.org/ *** --- @ Fri, 13 Dec 2013 23:55:02 -0800 +++ @ Sat, 14 Dec 2013 00:25:02 -0800 @@ -7,7 +7,7 @@ References - 1. file:///tmp/lynxLytjqu/navigate.html - 2. file:///tmp/lynxLytjqu/whats_new.html - 3. file:///tmp/lynxLytjqu/navigate.html - 4. file:///tmp/lynxLytjqu/whats_new.html + 1. file:///tmp/lynxN7VMJX/navigate.html + 2. file:///tmp/lynxN7VMJX/whats_new.html + 3. file:///tmp/lynxN7VMJX/navigate.html + 4. file:///tmp/lynxN7VMJX/whats_new.html I notice that at line 77 in urlwatch's html2txt.py script, there is a function that is supposed to remove output like this from lynx. But it seems that the output from lynx has changed, omitting the localhost portion of the file: URL, and so the regexes in that function no longer catch and remove the randomly generated URLs. Thank you, Alex -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages urlwatch depends on: ii python 2.7.5-5 ii python-concurrent.futures 2.1.2-1 Versions of packages urlwatch recommends: ii lynx 2.8.8pre1-1 ii python-utidylib 0.2-9 ii python-vobject 0.8.1c-4 Versions of packages urlwatch suggests: pn html2text 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#732113: Save file dialog occasionally goes blank.
Package: simple-scan Version: 3.4.2-1 Severity: serious Start scanning a document, then push 'save' button. On alternate runs of simple-scan, the save dialog is blank. Restart simple-scan to fix it.
Bug#731109: [RFR] templates://pinto/{pinto.templates}
Quoting victory (victory@gmail.com): On Sat, 14 Dec 2013 08:35:27 +0100 Christian PERRIER wrote: Rationale: --- pinto.old/debian/pinto.templates2013-12-02 07:30:02.318756824 +0100 - This is the username and password you will use to log in to your pinto - installation after configuration is complete. If you do not provide a - password, you will have to configure access to pinto yourself. + This login/password combination is needed, after installation, to log + in Pinto through its web interface. why change username to login? You're right. I just s/login/username in my proposed template. signature.asc Description: Digital signature
Bug#732105: tor: Crash on startup: Error in `tor': free(): invalid pointer: 0x00007f0ad9db532b
Linus Lüssing schrieb am Samstag, dem 14. Dezember 2013: Version: 0.2.3.25-1 What can you tell me about your system that would be different from all the others? $ tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc ... then I'm getting the following error message: Error in `tor': free(): invalid pointer: 0x7f0ad9db532b Is this from a root shell? How does your torrc look like? For the complete command line output, including a backtrace (the debug symbols seem to be missing even though I've installed tor-dbg?), see the attached log. How did you try to produce the backtrace? -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714984:
Control: tag -1 patch pending
Attaching imported patch with DEP-3 header.
Description: Segmentation Fault: vips 7.28.5-1 with jpeg compression
commit 996f26ec7011f6eb1aad4c204100d0f0970e2cad
Author: John Cupitt jcup...@gmail.com
Date: Fri Dec 13 15:03:16 2013 +
fix a tiff write crash
see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714984
https://github.com/jcupitt/libvips/issues/88
Bug-Debian: http://bugs.debian.org/714984
Reviewed-by: Mathieu Malaterre ma...@debian.org
Index: vips-7.28.5/ChangeLog
===
--- vips-7.28.5.orig/ChangeLog 2012-05-06 13:29:26.0 +0200
+++ vips-7.28.5/ChangeLog 2013-12-14 10:47:03.610487401 +0100
@@ -1,3 +1,6 @@
+13/12/13 started 7.28.5-1
+- fix jpeg tiff write, see https://github.com/jcupitt/libvips/issues/88
+
19/4/12 started 7.28.5
- ifthenelse blend mode was broken
- small blend speedup
Index: vips-7.28.5/libvips/foreign/vips2tiff.c
===
--- vips-7.28.5.orig/libvips/foreign/vips2tiff.c 2012-05-06 13:29:26.0 +0200
+++ vips-7.28.5/libvips/foreign/vips2tiff.c 2013-12-14 10:47:03.610487401 +0100
@@ -126,6 +126,8 @@
* 2/12/11
* - make into a simple function call ready to be wrapped as a new-style
* VipsForeign class
+ * 7/8/12
+ * - be more cautious enabling YCbCr mode
*/
/*
@@ -452,15 +454,9 @@
TIFFSetField( tif, TIFFTAG_ORIENTATION, ORIENTATION_TOPLEFT );
TIFFSetField( tif, TIFFTAG_COMPRESSION, tw-compression );
- if( tw-compression == COMPRESSION_JPEG ) {
+ if( tw-compression == COMPRESSION_JPEG )
TIFFSetField( tif, TIFFTAG_JPEGQUALITY, tw-jpqual );
- /* Enable rgb-ycbcr conversion in the jpeg write. See also
- * the photometric selection below.
- */
- TIFFSetField( tif, TIFFTAG_JPEGCOLORMODE, JPEGCOLORMODE_RGB );
- }
-
if( tw-predictor != -1 )
TIFFSetField( tif, TIFFTAG_PREDICTOR, tw-predictor );
@@ -518,12 +514,17 @@
TIFFTAG_INKSET, INKSET_CMYK );
}
else if( tw-compression == COMPRESSION_JPEG
-tw-im-Bands == 3 )
+tw-im-Bands == 3
+tw-im-BandFmt == VIPS_FORMAT_UCHAR ) {
/* This signals to libjpeg that it can do
* YCbCr chrominance subsampling from RGB, not
* that we will supply the image as YCbCr.
*/
photometric = PHOTOMETRIC_YCBCR;
+TIFFSetField( tif,
+ TIFFTAG_JPEGCOLORMODE,
+ JPEGCOLORMODE_RGB );
+ }
else
photometric = PHOTOMETRIC_RGB;
@@ -1340,9 +1341,27 @@
/* TIFFTAG_JPEGQUALITY is a pesudo-tag, so we can't copy it.
* Set explicitly from TiffWrite.
*/
- if( tw-compression == COMPRESSION_JPEG )
+ if( tw-compression == COMPRESSION_JPEG ) {
TIFFSetField( out, TIFFTAG_JPEGQUALITY, tw-jpqual );
+ /* Only for three-band, 8-bit images.
+ */
+ if( tw-im-Bands == 3
+ tw-im-BandFmt == VIPS_FORMAT_UCHAR ) {
+ /* Enable rgb-ycbcr conversion in the jpeg write.
+ */
+ TIFFSetField( out,
+TIFFTAG_JPEGCOLORMODE, JPEGCOLORMODE_RGB );
+
+ /* And we want ycbcr expanded to rgb on read.
+ * Otherwise TIFFTileSize() will give us the size of
+ * a chrominance subsampled tile.
+ */
+ TIFFSetField( in,
+TIFFTAG_JPEGCOLORMODE, JPEGCOLORMODE_RGB );
+ }
+ }
+
/* We can't copy profiles :( Set again from TiffWrite.
*/
if( embed_profile( tw, out ) )
Bug#731109: [RFR] templates://pinto/{pinto.templates}
Christian PERRIER wrote: Template: pinto/adminpassword Type: password _Description: Pinto web administration password: + Please choose the password for the pintoadmin user. . + This login/password combination is needed, after installation, to log + in Pinto through its web interface. (s/login/username/g... oh, there's only one instance anyway) That's to log in ^to^ Pinto. Otherwise, no work for me here. --- pinto.old/debian/control 2013-12-02 07:30:02.318756824 +0100 +++ pinto/debian/control 2013-12-14 08:12:13.855930658 +0100 @@ -128,7 +128,8 @@ Description: application for curating a repository of Perl modules In the control file: I was going to say that there's no mention in the description of pinto having a web interface. But then again reading the manual it's all CLI-compatible anyway, so I'll leave it. ObWhyTheName - has its own section in the man page: https://metacpan.org/pod/release/THALJEF/Pinto-0.092/lib/Pinto/Manual/Introduction.pod#WHY-IS-IT-CALLED-PINTO -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package diff -ru pinto-0.90+dfsg.pristine/debian/control pinto-0.90+dfsg/debian/control --- pinto-0.90+dfsg.pristine/debian/control 2013-10-18 18:51:20.0 +0100 +++ pinto-0.90+dfsg/debian/control 2013-12-14 09:55:35.459325222 + @@ -128,7 +128,8 @@ Pinto is an application for creating and managing a custom CPAN-like repository of Perl modules. The purpose of such a repository is to provide a stable, curated stack of dependencies from which you can reliably build, - test, and deploy your application using the standard Perl tool chain. Pinto - supports various operations for gathering and managing distribution + test, and deploy applications using the standard Perl tool chain. + . + Pinto supports various operations for gathering and managing distribution dependencies within the repository, so that you can control precisely which - dependencies go into your application. + dependencies go into applications. diff -ru pinto-0.90+dfsg.pristine/debian/pinto.templates pinto-0.90+dfsg/debian/pinto.templates --- pinto-0.90+dfsg.pristine/debian/pinto.templates 2013-08-16 16:19:46.0 +0100 +++ pinto-0.90+dfsg/debian/pinto.templates 2013-12-14 09:25:34.620768608 + @@ -1,17 +1,21 @@ Template: pinto/adminpassword Type: password _Description: Pinto web administration password: - Please provide the password to be created with the pintoadmin user. + Please choose the password for the pintoadmin user. . - This is the username and password you will use to log in to your pinto - installation after configuration is complete. If you do not provide a - password, you will have to configure access to pinto yourself. + This username/password combination is needed, after installation, to log + in to Pinto through its web interface. + . + If this is left empty, you will have to manually configure + accounts for Pinto. Template: pinto/adminpassword-repeat Type: password -_Description: Password confirmation: +_Description: Re-enter password to verify: + Please enter the same user password again to verify you have typed it + correctly. Template: pinto/adminpassword-mismatch -Type: note -_Description: The passwords do not match - +Type: error +_Description: Password input error + The two passwords you entered were not the same. Please try again. Template: pinto/adminpassword Type: password _Description: Pinto web administration password: Please choose the password for the pintoadmin user. . This username/password combination is needed, after installation, to log in to Pinto through its web interface. . If this is left empty, you will have to manually configure accounts for Pinto. Template: pinto/adminpassword-repeat Type: password _Description: Re-enter password to verify: Please enter the same user password again to verify you have typed it correctly. Template: pinto/adminpassword-mismatch Type: error _Description: Password input error The two passwords you entered were not the same. Please try again. Source: pinto Section: perl Priority: optional Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Uploaders: Oleg Gashev o...@gashev.net Build-Depends: debhelper (= 8), libmodule-build-perl (= 0.400500) | perl (= 5.19.1) Build-Depends-Indep: cpanminus (= 1.6916), libapache-htpasswd-perl, libapp-cmd-perl, libarchive-extract-perl, libauthen-simple-passwd-perl, libcapture-tiny-perl, libclass-load-perl, libcpan-checksums-perl, libcpan-distnameinfo-perl, libcwd-guard-perl, libdatetime-perl, libdatetime-timezone-perl, libdbd-sqlite3-perl (= 1.33), libdbix-class-perl (= 0.08200), libdevel-stacktrace-perl, libdist-metadata-perl (= 0.924), libfile-homedir-perl, libfile-nfslock-perl, libfile-which-perl, libhttp-body-perl, libhttp-date-perl, libhttp-message-perl, libio-interactive-perl, libio-prompt-perl,
Bug#732109: base: /etc/pam.d/sshd overides setting up LANG from a ssh sessions.
control: reassign -1 openssh-server On Samstag, 14. Dezember 2013, Denis Gillain wrote: Package: base Severity: normal Tags: l10n -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash We use wheezy, jessie and ubuntu too, and some are UTF8, others ISO8859-1. It may not be a good idea that the server sets the locale from /etc/pam.d/sshd. The terminal we use, (PuTTY par example) is already set with it's own locale, and the locale to use for a session should be that one from the terminal, not the one set by sshd. Do you agree? In case you do, can you comment line 44 in /etc/pam.d/sshd. The others config files (login, lightdm...) are ok since access is done localy. But when the access is remote from the servern the locale to use is set by the terminal, and line 44 overides the work done at the terminal :) Thanks a lot ! Denis Gillain signature.asc Description: This is a digitally signed message part.
Bug#732067: [Pkg-mozext-maintainers] Bug#732067: enigmail asks for passphrase automatically
Hi Daniel On 2013-12-13 22:31, Daniel Kahn Gillmor wrote: Hi Martin-- It used to be, that I could select an encrypted message and see the actual encrypted text, without being asked for my passphrase. First when I clicked on decrypt was I asked for my passphrase. when you say it used to be, what version of enigmail were you using at the time? if you've recently changed versions of enigmail, you might be able to recover that information from /var/log/dpkg.log. I cannot find any records in my logs of enigmail being updated in the last 6 months (and the problem does not go back further than that) I can see, however, Icedove being updated twice: 2013-Oct-18 icedove:amd64 (17.0.7-1~deb7u1, 17.0.9-1~deb7u1) 2013-Nov-18 icedove:amd64 (17.0.9-1~deb7u1, 17.0.10-1~deb7u1) What decrypt button were you clicking on? Is it still showing up? Yes, the button is still there. It is the Decrypt button (Decrypt or verify the message with OpenPGP), I think same as when you click the OpenPGP menu - Decrypt/Verify Interestingly, this still works in my inbox, but not anymore in my sent folder. hm, i'm not sure what this means. do you have multiple accounts configured? are you looking at icedove's aggregate inbox, or at an inbox from a single account? no, I have only single account set up for IMAP. This behavior is extremely annoying. I am using Debian GNU/Linux Wheezy, kernel 3.10.7 What version of icedove are you using? My Icedove version is 17.0.10-1~deb7u1 i've tested and i think i can replicate what you're seeing in 1.6 as well. I've just asked about it on the upstream mailing list to see if we can figure out what the issue is. --dkg many thanks for your help Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685076: xbmc: Recommends non-existent python-qt3 package
Package: xbmc Version: 2:11.0~git20120510.82388d5-1 Followup-For: Bug #685076 Hi, this bug still exists. Because even after almost one and a half year the version uploaded to experimental is still not present in testing or unstable. What's the reason for this huge delay? Regards Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716806: XBMC is outdated
Package: xbmc Version: 2:11.0~git20120510.82388d5-1 Followup-For: Bug #716806 According to http://wiki.xbmc.org/index.php?title=Installing_XBMC_for_Linux#Arch The Debian repository maintainers have rejected XBMC v12's entry into their default repository (which also feeds into the default Ubuntu repositories) due to the fact that XBMC uses an internal FFmpeg, instead of system wide libav, as demanded by Debian. XBMC is unable to do this currently for various reasons, one of which is that it would take a great amount of time to switch over to that library. I don't know if there has been any further progress on this issue. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-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 Versions of packages xbmc depends on: ii mesa-utils 8.1.0-2 ii python 2.7.5-5 ii python-imaging 1.1.7-4 ii python-support 1.0.15 ii ttf-dejavu-core 2.33+svn2514-3 ii ttf-liberation 1.07.3-3 ii x11-utils7.7+1 ii xbmc-bin 2:11.0~git20120510.82388d5-1+b1 Versions of packages xbmc recommends: pn python-qt3 none xbmc 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#732114: [INTL:es] Spanish debconf template translation for fheroes2-pkg
Package: fheroes2-pkg
Severity: wishlist
Tags: l10n patch
Greetings,
--
Camaleón
# fheroes2-pkg po-debconf translation to Spanish
# Copyright (C) 2013 Software in the Public Interest
# This file is distributed under the same license as the fheroes2-pkg package.
#
# Changes:
# - Initial translation
# Camaleón noela...@gmail.com, 2013
#
# - Updates
#
#
# Traductores, si no conocen el formato PO, merece la pena leer la
# documentación de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Equipo de traducción al español, por favor lean antes de traducir
# los siguientes documentos:
#
# - El proyecto de traducción de Debian al español
# http://www.debian.org/intl/spanish/
# especialmente las notas y normas de traducción en
# http://www.debian.org/intl/spanish/notas
#
# - La guía de traducción de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
#
msgid
msgstr
Project-Id-Version: fheroes2-pkg\n
Report-Msgid-Bugs-To: fheroes2-...@packages.debian.org\n
POT-Creation-Date: 2013-11-07 07:11+0100\n
PO-Revision-Date: 2013-12-01 18:42+0200\n
Last-Translator: Camaleón noela...@gmail.com\n
Language-Team: Debian Spanish debian-l10n-span...@lists.debian.org\n
Language: es\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
Plural-Forms: nplurals=2; plural=(n != 1);\n
X-Generator: Virtaal 0.7.1\n
#. Type: boolean
#. Description
#: ../templates:2001
msgid Proceed with downloading and compiling fheroes2?
msgstr ¿Desea proceder con la descarga y compilación de fheroes2?
#. Type: boolean
#. Description
#. Type: note
#. Description
#: ../templates:2001 ../templates:3001
msgid
The fheroes2 AI is non-free due to a not-for-sale restriction, and some
images may also be non-free.
msgstr
La Inteligencia Artificial (IA) de fheroes2 no es libre debido a una
restricción que prohíbe su venta y algunas imágenes también podrían no
ser libres.
#. Type: boolean
#. Description
#. Type: note
#. Description
#: ../templates:2001 ../templates:3001
msgid
The installation process is therefore about to download the source files
from SourceForge, compile them, and install the binary deb package
\${PKGG}${VER}\.
msgstr
Por tanto, el proceso de instalación consiste en descargar los archivos
fuente desde SourceForge, compilarlos e instalar el paquete deb binario
«${PKGG}${VER}».
#. Type: boolean
#. Description
#: ../templates:2001
msgid Please confirm whether you wish this to happen.
msgstr Confirme si desea proseguir con esta opción.
#. Type: note
#. Description
#: ../templates:3001
msgid
Please remember to run \sudo dpkg-reconfigure ${PKGI}\ to build and
install guest package(s) for the first time.
msgstr
No se olvide de ejecutar «sudo dpkg-reconfigure ${PKGI}» para construir e
instalar el/los paquete/s invitado/s la primera vez.
#. Type: title
#. Description
#: ../templates:4001
msgid Build and install ${PKGG}${VER}
msgstr Construir e instalar ${PKGG}${VER}
#. Type: title
#. Description
#: ../templates:5001
msgid Upgrades available for guest package(s)
msgstr Actualizaciones disponibles para el/los paquete/s invitado/s
#. Type: note
#. Description
#: ../templates:6001
msgid
An update to guest package(s) [${PKGG_ALL}] version ${VER} is available but
automatic upgrade is disabled.
msgstr
Se encuentra disponible una actualización del/de los paquete/s invitado/s
[${PKGG_ALL}] a la versión ${VER} pero las actualizaciones automáticas están
desactivadas.
#. Type: note
#. Description
#: ../templates:6001
msgid
Please remember to run \sudo dpkg-reconfigure ${PKGI}\ to build and
install guest package(s) or consider installing the APT post-invoke hook.
msgstr
No se olvide de ejecutar «sudo dpkg-reconfigure ${PKGI}» para construir e
instalar el/los paquete/s invitado/s o considere la instalación del
disparador posterior a la ejecución de APT.
#. Type: boolean
#. Description
#: ../templates:7001
msgid Install APT post-invoke hook?
msgstr ¿Desea instalar el disparador posterior a la ejecución de APT?
#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../templates:7001 ../templates:8001
msgid
If activated, the APT post-invoke hook takes care of future automatic
upgrades of guest package(s) on host package upgrade. When an update is
available, the hook will attempt to download and build the package(s), and
(if \apt-get check\ reports no errors) install them with \dpkg -i\.
msgstr
Si se encuentra activado, el disparador posterior a la ejecución de APT
tendrá en cuenta las futuras actualizaciones automáticas del/de los
paquete/s invitado/s en el equipo. Cuando se encuentre disponible una
actualización, el disparador intentará descargar y construir el/los
paquete/s y si «apt-get check» no encuentra ningún error, los instalará con
«dpkg -i».
#. Type: boolean
#. Description
#. Type:
Bug#422165: perl-base: IO::Socket::INET mis-reports gethostbyname problems
forwarded 422165 https://rt.perl.org/Public/Bug/Display.html?id=120764 thanks On Thu, May 03, 2007 at 08:47:58PM -0300, Martín Ferrari wrote: Package: perl-base Version: 5.8.8-7 Severity: normal $ LANG=C perl -MIO::Socket::INET -e 'new IO::Socket::INET(PeerAddr = non.existant.host, PeerPort = 25) or die $!' Invalid argument at -e line 1. This is on purpose, as when I read the code, the _error subroutine sets $! with EINVAL and $@ with the correct error. Which nobody expects (like the spanish inquisition), nor is documented (save a example in the manpage that seems like a typo). From the perlvar manpage: $@ The Perl syntax error message from the last eval() operator. So this clearly is a bug. Just a note that [perl #120764] discusses the same issue. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732015:
reopen 732015 thanks Looks like the bug appears when using qt4-qmake 4:4.8.5+git121-g2a9ea11+dfsg1-2, see: http://buildd.debian-ports.org/status/fetch.php?pkg=gofigure2arch=x32ver=0.9.0-3stamp=1386959644 But does not when using 4:4.8.2+dfsg-11, see: https://buildd.debian.org/status/fetch.php?pkg=gofigure2arch=i386ver=0.9.0-3stamp=1386929104 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732115: override: gcalctool:oldlibs/extra
Package: ftp.debian.org Severity: normal Hi, gcalctool is now a transitional package, please adjust the override file accordingly. Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732116: RM: colo-installer -- RoM, Cobalt devices no longer supported by installer
Package: ftp.debian.org Please remove colo-installer from unstable/testing. I just removed support for Cobalt devices from the installer as these devices are very old and there are problems with the boot loader. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732105: tor: Crash on startup: Error in `tor': free(): invalid pointer: 0x00007f0ad9db532b
Hi! And thanks for the quick response. On Sat, Dec 14, 2013 at 10:46:28AM +0100, Peter Palfrader wrote: Linus Lüssing schrieb am Samstag, dem 14. Dezember 2013: Version: 0.2.3.25-1 What can you tell me about your system that would be different from all the others? No clue yet. It's Debian unstable, 64bit both user space and kernel space wise: $ dpkg --print-architecture amd64 Though i386 was added through multiarch support, too: $ dpkg --print-foreign-architectures i386 Also, I'm having this issue for a few weeks if not months now. A few months ago everything was working fine. No idea what has happened between that yet, a new Tor or related library version installed via apt-get dist-upgrade is the only guess I'm having. Btw., the Tor browser bundle as provided by torproject.org (tor-browser-gnu-linux-x86_64-2.3.25-16-dev-en-US) starts up fine. I'm going to check whether running Tor via debootstrap/chroot works later. $ tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc ... then I'm getting the following error message: Error in `tor': free(): invalid pointer: 0x7f0ad9db532b Is this from a root shell? How does your torrc look like? It's invoked via sudo. Invoking it from a complete root shell (bash) doesn't make a difference, though. Ah! Thought --defaults-torrc would be the complete torrc in use. Invoking things with this command: $ sudo tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc-fg ... with /etc/tor/torrc-fg having this single line: RunAsDaemon 0 ... doesn't make a difference either. For the complete command line output, including a backtrace (the debug symbols seem to be missing even though I've installed tor-dbg?), see the attached log. How did you try to produce the backtrace? I'm not trying, it just happens every time :). Cheers, Linus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732105: tor: Crash on startup: Error in `tor': free(): invalid pointer: 0x00007f0ad9db532b
Linus Lüssing schrieb am Samstag, dem 14. Dezember 2013: I'm going to check whether running Tor via debootstrap/chroot works later. Ok. For the complete command line output, including a backtrace (the debug symbols seem to be missing even though I've installed tor-dbg?), see the attached log. How did you try to produce the backtrace? I'm not trying, it just happens every time :). No, the crashes happen. The bt doesn't just magically appear, does it? :) -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731009: xmlstarlet: FTBFS on mips: java.lang.IllegalArgumentException: Invalid profile data
block 731009 by 709950 thanks Hi, El dg 01 de 12 de 2013 a les 00:02 +0100, en/na Andreas Beckmann va escriure: Package: xmlstarlet Version: 1.5.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, xmlstarlet FTBFS on mips Yes, it seems there is a problem in fop package with mips that causes that xmlstarlet can't build. See #709950 and #712885. Thanks for reporting bugs, Mònica -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732117: mount: loop mounting fails with LOOP_SET_FD failed
Package: mount
Version: 2.20.1-5.5
Severity: normal
Loop mounting has started to fail. Suspect this might be a kernel
change/bug, but reporting against mount since this is where the problem
is manifest.
Example:
# losetup -f
/dev/loop0
# export f=1; mount -v -o loop=/dev/loop0
debian-testing-source-DVD-${f}old.iso /loopmnt1
mount: enabling autoclear loopdev flag
mount: going to use the loop device /dev/loop0
mount: you didn't specify a filesystem type for /dev/loop0
I will try type iso9660
mount: block device /large/jigdo_area/debian-testing-source-DVD-1old.iso is
write-protected, mounting read-only
mount: enabling autoclear loopdev flag
mount: going to use the loop device /dev/loop0
warning: /large/jigdo_area/debian-testing-source-DVD-1old.iso is already
associated with /dev/loop0
ioctl LOOP_SET_FD failed: Device or resource busy
mount: stolen loop=/dev/loop0
# losetup -f
/dev/loop0
Nothing in dmesg or /var/log/messages.
I see LOOP_SET_FD defined in /usr/include/linux/loop.h
-
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 3.11-2-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mount depends on:
ii libblkid12.20.1-5.5
ii libc62.17-97
ii libmount12.20.1-5.5
ii libselinux1 2.2.1-1
ii libsepol12.2-1
mount recommends no packages.
Versions of packages mount suggests:
ii nfs-common 1:1.2.8-4
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732105: tor: Crash on startup: Error in `tor': free(): invalid pointer: 0x00007f0ad9db532b
On Sat, Dec 14, 2013 at 11:42:42AM +0100, Peter Palfrader wrote: For the complete command line output, including a backtrace (the debug symbols seem to be missing even though I've installed tor-dbg?), see the attached log. How did you try to produce the backtrace? I'm not trying, it just happens every time :). No, the crashes happen. The bt doesn't just magically appear, does it? :) Hm, right, usually not. But it's not me trying to produce the backtrace :). I'm not invoking gdb or some fancy, custom LD_PRELOAD stuff if that's what you mean. Maybe it's a new feature of libc or something like that? But now that you are mentioning it, that probably explains the missing function names. I'm attaching an additional backtrace, this time created via gdb. And here's the output of an ldd: $ ldd /usr/sbin/tor linux-vdso.so.1 (0x7fff7a5fe000) libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f9abbe7a000) libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f9abbb7c000) libevent-2.0.so.5 = /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 (0x7f9abb934000) libssl.so.1.0.0 = /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x7f9abb6d5000) libcrypto.so.1.0.0 = /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x7f9abb2e2000) librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7f9abb0d9000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f9abaed5000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f9abab29000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f9aba90c000) /lib64/ld-linux-x86-64.so.2 (0x7f9abc44c000) (and running sudo /usr/sbin/tor --defaults-torrc ... yields the same crash, so all the tor binaries invoked so far should have been /usr/sbin/tor as it should be, so messed up PATH variables can't be the issue either) Cheers, Linus $ sudo gdb --args tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc-fg GNU gdb (GDB) 7.6.1 (Debian 7.6.1-1) Copyright (C) 2013 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. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/sbin/tor...Reading symbols from /usr/lib/debug/usr/sbin/tor...(no debugging symbols found)...done. (no debugging symbols found)...done. (gdb) run Starting program: /usr/sbin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc-fg warning: Could not load shared library symbols for linux-vdso.so.1. Do you need set solib-search-path or set sysroot? [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Dec 14 12:18:01.184 [notice] Tor v0.2.3.25 (git-3fed5eb096d2d187) running on Linux. Dec 14 12:18:01.184 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Dec 14 12:18:01.184 [notice] Read configuration file /usr/share/tor/tor-service-defaults-torrc. Dec 14 12:18:01.185 [notice] Read configuration file /etc/tor/torrc-fg. Dec 14 12:18:01.196 [notice] We were compiled with headers from version 2.0.19-stable of Libevent, but we're using a Libevent library that says it's version 2.0.21-stable. Dec 14 12:18:01.196 [notice] Initialized libevent version 2.0.21-stable using method epoll (with changelist). Good. Dec 14 12:18:01.196 [notice] Opening Socks listener on 127.0.0.1:9050 Dec 14 12:18:01.402 [notice] Opening Control listener on /var/run/tor/control *** Error in `/usr/sbin/tor': free(): invalid pointer: 0x7577d32b *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x7aa16)[0x768eea16] /lib/x86_64-linux-gnu/libc.so.6(+0x7b793)[0x768ef793] /usr/sbin/tor(+0x178d2)[0x5556b8d2] /usr/sbin/tor(+0x5ff7c)[0x555b3f7c] /usr/sbin/tor(+0x188c5)[0x5556c8c5] /usr/sbin/tor(+0x18b11)[0x5556cb11] /usr/sbin/tor(+0x18c8f)[0x5556cc8f] /usr/sbin/tor(+0x19082)[0x5556d082] /usr/sbin/tor(+0x1e9ae)[0x555729ae] /usr/sbin/tor(+0x15809)[0x55569809] /usr/sbin/tor(+0x1706e)[0x5556b06e] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x76895995] /usr/sbin/tor(+0x119fd)[0x555659fd] === Memory map: 4000-556cb000 r-xp fe:18 302841 /usr/sbin/tor 558ca000-558cd000 r--p 00176000 fe:18 302841 /usr/sbin/tor 558cd000-558d3000 rw-p 00179000 fe:18 302841 /usr/sbin/tor 558d3000-560aa000 rw-p 00:00 0 [heap] 7545a000-7546f000 r-xp fe:18 647880
Bug#732105: tor: Crash on startup: Error in `tor': free(): invalid pointer: 0x00007f0ad9db532b
Linus Lüssing schrieb am Samstag, dem 14. Dezember 2013: $ sudo gdb --args tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc-fg Program received signal SIGABRT, Aborted. 0x768a91d5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x768a91d5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x768ac388 in __GI_abort () at abort.c:90 #2 0x768e47bb in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x769e1368 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 #3 0x768eea16 in malloc_printerr (action=3, str=0x769dd30a free(): invalid pointer, ptr=optimized out) at malloc.c:4923 #4 0x768ef793 in _int_free (av=optimized out, p=0x7577d31b, have_lock=0) at malloc.c:3779 #5 0x5556b8d2 in microdesc_free () #6 0x555b3f7c in microdescs_parse_from_string () #7 0x5556c8c5 in microdescs_add_to_cache () #8 0x5556cb11 in microdesc_cache_reload () #9 0x5556cc8f in get_microdesc_cache () #10 0x5556d082 in update_microdescs_from_networkstatus () #11 0x555729ae in router_reload_consensus_networkstatus () #12 0x55569809 in do_main_loop () #13 0x5556b06e in tor_main () #14 0x76895995 in __libc_start_main (main=0x555659a0 main, argc=5, ubp_av=0x7fffe638, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffe628) at libc-start.c:276 #15 0x555659fd in _start () (gdb) OOI, can you move away all the files in /var/lib/tor and try again? If that helps, I'd be really interested in the contents of these, assuming you don't have any private keys or other privileged data there. Cheers, -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732118: xserver-xorg-video-nvidia: Could you please add xorg-video-abi-15 support
Package: xserver-xorg-video-nvidia Version: 331.20-2 Severity: wishlist As far as I know nvidia has added Xorg 1.15 support on all it's branch now (including the legacy 175.x, 304.x, ...). I would like to test Xorg 1.15 from experimental. Thnaks. -- Package-specific info: uname -a: Linux tri-yann4 3.10.24 #30 SMP PREEMPT Fri Dec 13 17:08:05 CET 2013 x86_64 GNU/Linux /proc/version: Linux version 3.10.24 (valette@tri-yann4) (gcc version 4.8.2 (Debian 4.8.2-9) ) #30 SMP PREEMPT Fri Dec 13 17:08:05 CET 2013 /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.20 Wed Oct 30 17:43:35 PDT 2013 GCC version: gcc version 4.8.1 (Debian 4.8.1-10) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 670] [10de:1189] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Device [10b0:1189] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 85 Region 0: Memory at fa00 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at f000 (64-bit, prefetchable) [size=128M] Region 3: Memory at f800 (64-bit, prefetchable) [size=32M] Region 5: I/O ports at e000 [size=128] [virtual] Expansion ROM at fb00 [disabled] [size=512K] Capabilities: access denied Kernel driver in use: nvidia dmesg: No AGP bridge found No AGP bridge found Console: colour VGA+ 80x25 vgaarb: device added: PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none vgaarb: loaded vgaarb: bridge control possible :01:00.0 Linux agpgart interface v0.103 input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input11 input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input12 input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input13 input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input14 #1: HDA NVidia at 0xfb08 irq 36 nvidia: module license 'NVIDIA' taints kernel. vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem NVRM: loading NVIDIA UNIX x86_64 Kernel Module 331.20 Wed Oct 30 17:43:35 PDT 2013 nvidia :01:00.0: irq 85 for MSI/MSI-X OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Mar 30 2013 /etc/alternatives/glx - /usr/lib/nvidia lrwxrwxrwx 1 root root 48 Aug 23 17:07 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu - /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so lrwxrwxrwx 1 root root 48 Aug 23 17:07 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu - /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so lrwxrwxrwx 1 root root 43 Mar 30 2013 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Mar 30 2013 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 51 Mar 30 2013 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 25 Mar 30 2013 /etc/alternatives/glx--linux-libglx.so - /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Mar 30 2013 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf - /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Mar 30 2013 /etc/alternatives/glx--nvidia-bug-report.sh - /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 29 Mar 30 2013 /etc/alternatives/glx--nvidia_drv.so - /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 22 Aug 23 17:07 /etc/alternatives/libGL.so-master - /usr/lib/mesa-diverted lrwxrwxrwx 1 root root 23 Aug 16 18:16 /etc/alternatives/nvidia - /usr/lib/nvidia/current lrwxrwxrwx 1 root root 51 Aug 16 18:16 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 51 Aug 16 18:16 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 33 Aug 16 18:16 /etc/alternatives/nvidia--libglx.so - /usr/lib/nvidia/current/libglx.so lrwxrwxrwx 1 root root 59 Aug 16 18:16 /etc/alternatives/nvidia--libnvidia-cfg.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 38 Aug 16 18:16 /etc/alternatives/nvidia--nv-control-dpy - /usr/lib/nvidia/current/nv-control-dpy lrwxrwxrwx 1 root root 44 Aug 16 18:16 /etc/alternatives/nvidia--nvidia-bug-report.sh -
Bug#708462: lesttif2 removed from unstable [Was Bug#731678: Removed package(s) from unstable]
On Sat, Dec 14, 2013 at 08:42:52 +0100, Paul Gevers wrote: Hi all, Although from the testing/jessie point of view the transition is not finished yet, lesstif2 is removed from unstable. I understand that lesstif2 is removed from testing when no (binary) packages depend on it anymore. As the removal has not happened automatically, what can I do to help the process along? Removing lesstif2 would make grass, grass-gui, gridengine-qmon, libvia-dev, libvia2, via-bin uninstallable. grass is blocked by #728150. gridengine needs a few more days. via is blocked by #724021. Cheers, Julien signature.asc Description: Digital signature
Bug#732119: [ttf-bitstream-vera] Please mark this package as Multi-Arch: foreign
Source: ttf-bitstream-vera
Version: 1.10-8
Severity: wishlist
Tags: patch
I just wanted to install mupen64plus-ui-console:i386 on amd64 to verify some
user problems and it failed because it could not find ttf-bitstream-vera:i386.
This package manager behavior seemed new to me but it seems the multiarch
documentation [1] agrees with it. This font package doesn't depend on other
architecture dependent packages (directly and indirectly) and should therefore
not break any assumption.
Can you please mark this package as 'Multi-Arch: foreign'. But please check
the documentation because I've just did a quick check after not reading it
for a long time.
Thanks
[1]
https://wiki.debian.org/Multiarch/Implementation#Multi-Arch:_foreign_support_packages--- debian/control.orig 2013-12-14 12:39:03.848670915 +0100
+++ debian/control 2013-12-14 12:27:34.928692522 +0100
@@ -7,6 +7,7 @@
Package: ttf-bitstream-vera
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}
Description: The Bitstream Vera family of free TrueType fonts
This is a set of high-quality TrueType fonts created by Bitstream, Inc. and
Bug#732120: no shared library, README.Debian?
Package: python-cxx-dev Version: 6.2.4-3 The way to link with this module is not really clear from the documentation Maybe it needs a brief README.Debian to explain the way it is packaged, why there is no shared library and how to use it Alternatively, maybe it would be useful to build a shared library and ship that for convenience? Specifically, any user of this package needs to either a) copy the *.cxx files into their project repository and add them to their Makefile b) add those files (using their absolute path on the filesystem) to their Makefile For example, I added them like this in repro pyroute plugin Makefile.am: PYCXX_SRCDIR = /usr/share/python2.7/CXX/Python2 libpyroute_la_SOURCES += $(PYCXX_SRCDIR)/cxxextensions.c libpyroute_la_SOURCES += $(PYCXX_SRCDIR)/cxx_extensions.cxx libpyroute_la_SOURCES += $(PYCXX_SRCDIR)/cxxsupport.cxx libpyroute_la_SOURCES += $(PYCXX_SRCDIR)/../IndirectPythonInterface.cxx Users who fail to add these or don't realize this are going to see an error about undefined symbols at linking time. This is a slightly unusual way of using a C++ library: most libraries either work as a header library (just include the headers, no shared object) or they package a full libsomething.so that the dependent projects can link to. Therefore, it may be useful for the maintainer or upstream to comment on why the cxx files have to be copied/used in this way by other projects. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732121: fails to start silently
Package: tpb Version: 0.6.4-8 Severity: important Coin, Running /usr/bin/tpb -d (like in /lib/udev/rules.d/92-tpb.rules) exits immediately with return code 0 and with the following errors in ~/.xsession-errors : WARN: event_handle_error:186: X error: request=XFixesCreateRegionFromWindow (major=138, minor=7, resource=2a1), error=BadWindow WARN: event_handle_error:186: X error: request=XFixesTranslateRegion (major=138, minor=17, resource=1204628), error=BadRegion WARN: event_handle_error:186: X error: request=XFixesUnionRegion (major=138, minor=13, resource=1204628), error=BadRegion WARN: event_handle_error:186: X error: request=XFixesDestroyRegion (major=138, minor=10, resource=1204628), error=BadRegion WARN: event_handle_error:186: X error: request=XFixesCreateRegionFromWindow (major=138, minor=7, resource=2a1), error=BadWindow WARN: event_handle_error:186: X error: request=XFixesTranslateRegion (major=138, minor=17, resource=1204629), error=BadRegion WARN: event_handle_error:186: X error: request=XFixesUnionRegion (major=138, minor=13, resource=1204629), error=BadRegion WARN: event_handle_error:186: X error: request=XFixesDestroyRegion (major=138, minor=10, resource=1204629), error=BadRegion WARN: event_handle_error:186: X error: request=XFixesCreateRegionFromWindow (major=138, minor=7, resource=2a1), error=BadWindow WARN: event_handle_error:186: X error: request=XFixesTranslateRegion (major=138, minor=17, resource=120462a), error=BadRegion WARN: event_handle_error:186: X error: request=XFixesUnionRegion (major=138, minor=13, resource=120462a), error=BadRegion WARN: event_handle_error:186: X error: request=XFixesDestroyRegion (major=138, minor=10, resource=120462a), error=BadRegion WARN: event_handle_error:186: X error: request=XFixesCreateRegionFromWindow (major=138, minor=7, resource=2a1), error=BadWindow WARN: event_handle_error:186: X error: request=XFixesTranslateRegion (major=138, minor=17, resource=120462b), error=BadRegion WARN: event_handle_error:186: X error: request=XFixesDestroyRegion (major=138, minor=10, resource=120462b), error=BadRegion Regards. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-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 tpb depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.52 ii libc6 2.17-97 ii libice62:1.0.8-2 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxinerama1 2:1.1.3-1 ii libxosd2 2.2.14-2 tpb recommends no packages. Versions of packages tpb suggests: pn xfonts-base-transcoded none -- Configuration Files: /etc/tpbrc changed: OSD ON OSDFONT -bh-*-*-*-*-*-34-*-*-*-*-*-*-* OSDCOLORGreen -- debconf information: tpb/groupchanged: tpb/autostart: true -- Marc Dequènes (Duck) pgp7q5qX3nrbU.pgp Description: PGP Digital Signature
Bug#732076: e2fsprogs: please update config.guess and config.sub at build time
On Sat, Dec 14, 2013 at 01:48:42AM -0500, Theodore Ts'o wrote:
Maybe I have an overly long memory, but I remember when the FSF let
politics intrude by making changes to config.guess to promote the
GNU/Linux name, which had the affect of breaking packages that blindly
trusted that you could always update config.guess.
Certainly in the last ten years I've never once seen a bug caused by
updated config.{guess,sub}, but I've seen hundreds (if not thousands, by
now) of failures caused by not doing so.
That plus the fact that I don't trust changes to autoconf not to
randomly cause breakage, is why I ship upstream e2fsprogs sources with
a generated configure and shiped config.guess/config.sub that I can
personally test to be sane.
This is of course conflating two separate issues. It's quite possible
to update config.{guess,sub} without updating autoconf.
I've already updated the upstream e2fsprogs sources to have an updated
version of config.guess and config.sub to support ppc64el. It will be
in the soon-to-be-released e2fsprogs 1.42.10.
Thanks, although it's a shame that this approach means we will
inevitably continue to run into this with new ports entirely
unnecessarily.
Regards,
--
Colin Watson [cjwat...@debian.org]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708462: lesttif2 removed from unstable [Was Bug#731678: Removed package(s) from unstable]
On 14-12-13 12:42, Julien Cristau wrote: Removing lesstif2 would make grass, grass-gui, gridengine-qmon, libvia-dev, libvia2, via-bin uninstallable. grass is blocked by #728150. gridengine needs a few more days. via is blocked by #724021. Thanks for verifying. Working on Grass right now (solution known). Will look into via after that. Paul signature.asc Description: OpenPGP digital signature
Bug#703005: [kscreensaver] Exit delay even with non-locked screen
Package: kscreensaver Version: 4:4.8.4-5 --- Please enter the report below this line. --- I'm running multiple machines with KDE for desktop environment, and I see the exit delay on all machines. The machine at home has no password lock on the screen saver and the delay after hitting mouse or keyboard is just the same as with password lock. All machines have a single display. I'm running the screensaver with random selection. The effect is observable with about 95% of the screensavers. Although in rare cases the screensaver is exited without delay. Conclusions: * Password lock does not seem to be a factor * Single vs dual screen does not seem to be a factor * It does not matter whether you exit the screensaver by mouse or keyboard * The type of screensaver that is running might be a factor, otherwise the effect itself might get triggered in a random fashion. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: 7.3 500 stable-updates ftp.debian.org 500 stable www.deb-multimedia.org 500 stable security.debian.org 500 stable ftp.debian.org 500 proposed-updates ftp.debian.org --- Package information. --- Depends(Version) | Installed -+- === kde-runtime | 4:4.8.4-2 libc6 (= 2.4) | 2.13-38 libgl1-mesa-glx | 8.0.5-4+deb7u2 OR libgl1 | libglu1-mesa | 8.0.5-4+deb7u2 OR libglu1 | libkdecore5 (= 4:4.4.4-2~) | 4:4.8.4-4 libkdeui5 (= 4:4.3.4) | 4:4.8.4-4 libkexiv2-10(= 4:4.7.1) | 4:4.8.4-1 libkio5 (= 4:4.3.4) | 4:4.8.4-4 libkparts4 (= 4:4.3.4) | 4:4.8.4-4 libkscreensaver5(= 4:4.6.1) | 4:4.8.4-6 libqt4-opengl (= 4:4.5.3) | 4:4.8.2+dfsg-11 libqtcore4(= 4:4.7.0~beta1) | 4:4.8.2+dfsg-11 libqtgui4 (= 4:4.8.0) | 4:4.8.2+dfsg-11 libstdc++6(= 4.1.1) | 4.7.2-5 libx11-6 | 2:1.5.0-1+deb7u1 kde-workspace-bin| 4:4.8.4-6 Recommends (Version) | Installed ==-+-== kde-window-manager | 4:4.8.4-6 kscreensaver-xsavers (= 4:4.8.4-5) | 4:4.8.4-5 Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732123: usage of stanza not compatible with ordinary English
Package: upstart Version: 1.20-1 Severity: minor The documentation (and presumably error messages etc.) uses the word stanza for what would normally be called a directive, command or keyword. Perhaps it is not too late to change this. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732122: semantics of boolean event specification not defined in init(5)
Package: upstart Version: 1.20-1 Severity: minor The documentation says that a job can be started on a boolean combination of events. Of course a boolean combination of events is semantically meaningless, unless events are thought to occur simultaneously (which I'm pretty sure they don't, in upstart). Presumably historical information is used somehow. The manpage discusses this in BUGS but even after reading that, neither the intended nor the actual semantics are clear to me. Perhaps if the intended semantics could be described, it would be easier to implement them ? It would also then be possible to explain in BUGS which exactly expressions have behaviour which is hopefully going to change later. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: upstart user jobs
I have some questions about these. Forgive me if I could just have looked up the answers: Are they enabled by default in jessie/sid ? (If the answer is no then feel free not to answer the rest...) In the manpage I read: | Note that a user job configuration file cannot have the same name | as a system job configuration file. I don't understand this restriction. It's sounds like it's referring to the pathnames in which case it's trivially true, so I assume it's referring to job names. In which case surely this is a troublesome restriction: what, for example, if a user, knowing that the sysadmin is going to install something that creates job foo, creates a job foo themselves first ? Can two different users create two jobs with the same name ? The underlying purpose of the restriction would seem to probably be to make job names unqualified by username but unique across users, but that seems wrong to me. Does anything that user jobs do depend on upstart being pid 1, or being root ? Does the thing which reads (and watches) the user's configuration files run as root, or as the user ? I.e., what is the privilege separation ? The docs say: | Files in this directory will be read and an inotify(7) watch | created the first time a user runs initctl(8). Does this really mean that if I'm fiddling around with writing some jobs, but not quite ready yet, and say initctl --help, my jobs will start to run ? Also, it would appear to imply that user jobs aren't started automatically at boot. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722217: *** stack smashing detected ***: /usr/bin/perl terminated
Same here on AMD64 (Linux debian 3.10-3-amd64 #1 SMP Debian 3.10.11-1 (2013-09-10) x86_64 GNU/Linux) [with nvidia FX5500 proprietary drivers (legacy 173 version) - if that matters] Error during upgrade - message is French but /that/ shouldn't be a problem :) Récupération des rapports de bogue… Fait Analyse des informations Trouvé/Corrigé… Fait Préconfiguration des paquets... (Lecture de la base de données... 423373 fichiers et répertoires déjà installés.) Préparation du remplacement de libc-bin 2.17-93 (en utilisant .../libc-bin_2.17-97_amd64.deb) ... Dépaquetage de la mise à jour de libc-bin ... Préparation du remplacement de libc6:i386 2.17-93 (en utilisant .../libc6_2.17-97_i386.deb) ... Déconfiguration de libc6:amd64 ... Dépaquetage de la mise à jour de libc6:i386 ... Préparation du remplacement de libc6:amd64 2.17-93 (en utilisant .../libc6_2.17-97_amd64.deb) ... *** stack smashing detected ***: /usr/bin/perl terminated dpkg: erreur de traitement de /var/cache/apt/archives/libc6_2.17-97_amd64.deb (--unpack) : le sous-processus nouveau script pre-installation a été tué par le signal (Erreur de segmentation) Traitement des actions différées (« triggers ») pour « man-db »... *** stack smashing detected ***: /usr/bin/perl terminated dpkg: erreur de traitement de man-db (--unpack) : le sous-processus script post-installation installé a été tué par le signal (Erreur de segmentation) Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/libc6_2.17-97_amd64.deb man-db E: Sub-process /usr/bin/dpkg returned an error code (1) Échec de l'installation d'un paquet. Tentative de récupération : Paramétrage de man-db (2.6.5-2) ... *** stack smashing detected ***: /usr/bin/perl terminated dpkg: erreur de traitement de man-db (--configure) : le sous-processus script post-installation installé a été tué par le signal (Erreur de segmentation) Paramétrage de libc-bin (2.17-97) ... dpkg: erreur de traitement de libc6:i386 (--configure) : le paquet libc6:i386 2.17-97 ne peut pas être configuré parce que la version de libc6:amd64 est différente (2.17-93) Des erreurs ont été rencontrées pendant l'exécution : man-db libc6:i386 From there on, no new program started, and nothing I tried worked - eventually had to turn computer off. After reboot, no gdm3. Couldn't swith to other screen. Luckily, I could still ssh to the computer and since 1st error was in preinst - I tried Brent's [Wendy J. Elmer] workaround which seems to have worked fine. [computer up and graphics running fine] I could *never* have got out of this situation on my own and therefore am *extremely* grateful to Brent for having posted this here. One thing - for those who have _never_ used dpkg -e before dpkg-deb --extract .deb /somewhere/ dpkg -e .deb /somewhere//DEBIAN Thanks again Brent! Where can I send you a Beer? (or, indeed, a crate of ~s) If there is any other information I can provide to help pinpoint this bug, I'll happily comply. -- Jerome -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724021: e-mail validation for Debian via package
Hi Currently the via package in Debian is one of the last package to block the removal of lesstif2 [0]. This is due to a serious bug [1] in the package which prevents if from migrating to testing. This e-mail aims to recheck the use of the lip...@cbs.mpg.de address, which caused bug [1] to be reported. The bug is about violation of policy section 3.3, which says that the maintainer must be specified with a working e-mail address. @ Michael, do I understand the changelog correctly if I say that you often copy the upstream packaging? The debian packaging svn is not up-to-date, so I can't check if you intentionally moved the maintainer-ship to the Lipsia group. If so, could you fix bug 724021 by uploading a via package with your name and e-mail address as Maintainer again? Paul [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708462 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724021 [2] http://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer signature.asc Description: OpenPGP digital signature
Bug#710311: Unable to reproduce exact scenario mentioned and nmu diff
Hi Radu,
Radu Spineanu radu.spine...@gmail.com writes:
Sent a ping to Davide, no answer yet. Let's wait for an answer for a
couple more days.
any update on this yet?.. is it worth to have the package still in
Debian? actually this nmu is blocking one of NM process task so :)
--
Vasudev Kamath
http://copyninja.info
Connect on ~friendica: copyninja@{frndk.de | vasudev.homelinux.net}
IRC nick: copyninja | vasudev {irc.oftc.net | irc.freenode.net}
GPG Key: C517 C25D E408 759D 98A4 C96B 6C8F 74AE 8770 0B7E
signature.asc
Description: PGP signature
Bug#721571: Acknowledgement (pychess package pages at packages.debian.org need updating)
In case the website information is automatically generated from the Debian control file, I've updated that too: http://code.google.com/p/pychess/source/detail?r=05098a3c4daa2f02565cc8d26c7937f4502a0457 On Sun, 2013-09-01 at 23:57 +, Debian Bug Tracking System wrote: Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to pychess-peo...@googlegroups.com (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): Varun Hiremath va...@debian.org If you wish to submit further information on this problem, please send it to 721...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732124: initctl reload behaviour should be configurable in job file
Package: upstart Version: 1.20-1 Severity: wishlist initctl(8) says that initctl reload sends the job's process a SIGHUP. Some programs won't expect to be randomly sent SIGHUPs. It should be possible to describe in the config file what should be done instead - probably, a command a la pre-exec et al. This would also make it possible to reload abstract jobs, and tasks. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732126: state machine semantics of initctl restart are unclear
Package: upstart Version: 1.20-1 Severity: minor The admirably clear table 5 in upstart-events(7) is very helpful. Reading initctl(8) in conjunction with that table, I conclude that initctl start and initctl stop change the goal. But it's not clear to me what initctl restart does. Is there an undocumented restart goal ? Or does it do something ad-hoc and instantaneous like killing a process (in which case what if the process ignores TERM, what about abstract jobs, etc. etc.) Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732105: tor: Crash on startup: Error in `tor': free(): invalid pointer: 0x00007f0ad9db532b
On Sat, Dec 14, 2013 at 12:32:38PM +0100, Peter Palfrader wrote: (gdb) OOI, can you move away all the files in /var/lib/tor and try again? If that helps, I'd be really interested in the contents of these, assuming you don't have any private keys or other privileged data there. Moving the folder away helps. I could narrow the issue down to my /var/lib/tor/cached-microdescs: https://metameute.de/~tux/bugreport/debian/732105/cached-microdescs.xz Cheers, Linus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732125: upstart-events(7) title is misleading
Package: upstart Version: 1.20-1 Severity: minor NAME upstart-events - Well-known Upstart events summary But actually, this manpage also contains core specification of the semantics of upstart jobs' goals and state transitions. At the very least the title should be changed. But perhaps it would be better to move the second half of upstart-events(7) to the top of the file, too, or even into a different file (perhaps, init(8)). Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731069: gcc-defaults: Please resume considering to change using unified version of gcc
Hi, On 02/12/13 13:14, Matthias Klose wrote: Afaics, the situation didn't change. There is nobody committing to work on the toolchain for these architectures. At least for release architectures the alternative is to drop the port unless somebody wants to maintain the toolchain for this port. This is the current status, please correct me if I'm wrong. - alpha, no feedback, CCing Michael Cree. - hppa, no feedback, CCing John David Anglin - ia64, no feedback, likely to be removed. - powerpc, found some feedback from the porters, but unrelated to toolchain issues, see https://lists.debian.org/debian-powerpc/2013/11/msg00050.html - powerpcspe, no feedback, CCing Roland Stigge. Now that we have fixed gcc-4.7 and gcc-4.8 on powerpcspe, using gcc-4.8 as default compiler on powerpcspe would fine. Thanks in advance, Roland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732111: ERROR: wget failed to download get-upstream-version.pl.gz.pgp
retitle 732111 flashplugin-nonfree: wget failed to download get-upstream-version.pl.gz.pgp tags 732111 unreproducible moreinfo stop On Sat, Dec 14, 2013 at 04:40:17PM +0800, jida...@jidanni.org wrote: One will always get this error That is not true, because some/many/most users don't get this error when installing flashplugin-nonfree. Please clarify the circumstances where you get this error. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732127: Does setuid also set the group(s) ? It should.
Package: upstart Version: 1.20-1 The documentation in init(5) doesn't mention whether specifying setgid in the job file also results in appropriate calls to setgid and setgroups. Firstly, clearly this should be documented. But, further, I think setuid should cause the group ids (setresgid and also setgroups) to be set as well. Otherwise jobs will inherit the group 0 (root) which might well be unexpectedly powerful. Arguably failure to do this is a security problem, although of course the details will depend on exactly what people write in their service files. If the user specifies setgid _and_ setuid, it's arguable whether you should also call initgroups. I would say not - not being a member of groups is generally less powerful. For comparison, I checked openbsd-inetd. If you specify just a user in an inetd.conf line, it will set the groups too. (The manpage doesn't make this entirely clear, but it seems to assume that that's what you expect because it does say that if you specify a user and a group you still get the supplementary groups for the user in question.) Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732111: ERROR: wget failed to download get-upstream-version.pl.gz.pgp
All I know is I upgraded all my four machines, and each got the error even though online, and even though wget can get the file fine. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732128: Manpages missing cross-references to socket stuff
Package: upstart Version: 1.20-1 Severity: minor I seem not to have encountered any cross-references to socket-event(7) or upstart-socket-bridge(8), or indeed any references to bridges, in my reading of init(8), runleve(7), init(5) and initctl(8). upstart-events(7) does mention them in the tables of conventional events but not in the SEE ALSO section. Please could we have more cross-references from appropriate places in the main texts, and in SEE ALSO. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732111: ERROR: wget failed to download get-upstream-version.pl.gz.pgp
On Sat, Dec 14, 2013 at 09:21:45PM +0800, jida...@jidanni.org wrote: All I know is I upgraded all my four machines, and each got the error even though online, and even though wget can get the file fine. Behind a proxy ? https://wiki.debian.org/FlashPlayer#Troubleshooting -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732129: RM: via -- ROM; Outdated, no reverse dependencies, potential replacement
Package: ftp.debian.org Severity: normal Please remove this package. It is holding up the lesstif transition. It was originally introduced as a dependency of lipsia, which has been removed from Debian in the past. A very similar library is provided by the mia package that is been worked on by the Debian Med team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724021: e-mail validation for Debian via package
Hi Paul, thanks for bringing this to my intention. The maintainership was not transferred by accident, instead the goal had been to have one of the upstream developers take over the Debian packaging. However, that process has stalled. At this time, there is no point in keeping the package in Debian. Hence I filled a bug (#732129) asking ftp-masters to remove the package. This should be a practical alternative to a proper fix for now. If something requires via as a dependency in the future, we can bring it back. Sorry for the hassle, Michael On Sat, Dec 14, 2013 at 1:38 PM, Paul Gevers elb...@debian.org wrote: Hi Currently the via package in Debian is one of the last package to block the removal of lesstif2 [0]. This is due to a serious bug [1] in the package which prevents if from migrating to testing. This e-mail aims to recheck the use of the lip...@cbs.mpg.de address, which caused bug [1] to be reported. The bug is about violation of policy section 3.3, which says that the maintainer must be specified with a working e-mail address. @ Michael, do I understand the changelog correctly if I say that you often copy the upstream packaging? The debian packaging svn is not up-to-date, so I can't check if you intentionally moved the maintainer-ship to the Lipsia group. If so, could you fix bug 724021 by uploading a via package with your name and e-mail address as Maintainer again? Paul [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708462 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724021 [2] http://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
Bug#732131: Please document apparmor directives
Package: upstart Version: 1.20-1 Severity: minor The cookbook http://upstart.ubuntu.com/cookbook/#id143 mentions apparmor load and apparmor switch. I didn't see them in the reference documentation. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725846: closed by Nobuhiro Iwamatsu iwama...@debian.org (Bug#725846: fixed in bluez 4.101-4)
Thank you very much. I'm eager to get bluetooth audio working again. :-) With many grettings, Adrian Immanuel KIEß On Sat, 2013-12-14 at 05:21 +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the bluetooth package: #725846: bluetooth: Fails with A2DP device It has been closed by Nobuhiro Iwamatsu iwama...@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 Nobuhiro Iwamatsu iwama...@debian.org by replying to this email. -- With greetings from Leipzig, Germany. Adrian Immanuel Kieß Administrator programmer Unix / Perl / LaTeX mail: adrian (at) kiess.at www: http://www.kiess.at signature.asc Description: This is a digitally signed message part
Bug#732130: Please document event/job/process environment variables properly
Package: upstart Version: 1.20-1 Severity: minor The cookbook http://upstart.ubuntu.com/cookbook/#id210 has a handy list of environment variables. This information doesn't seem to appear in the reference documentation. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732132: Want support for multiple-socket activation
Package: upstart Version: 1.20-1 Severity: wishlist It should be possible for a single job to effectively listen on multiple sockets. Eg with start on socket PROTO=INET PORT=22 or socket PROTO=INET6 PORT=22 or something. The program would presumably be run as soon as any of the sockets was ready for accept(), and receive all the sockets at once in UPSTART_FDS. Presumably it would then use getsockname() to sort out what was what. I haven't read the systemd docs yet so I can't say whether the systemd socket fd passing convention is better. If it is, then upstart should (configurably) adopt it. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: upstart proposed policy in Debian
Having read the docs there I have some apparently unanswered questions about how the upstart proponents think we would use upstart in Debian. How will we cope with removed-but-not-purged services ? Do we advise people in favour of socket activation ? Do we deprecate expect fork and expect daemon ? (I would favour this - the approach there is pretty horrible.) Perhaps there is some ubuntu docs on this. I confess I didn't try very hard to find it, hoping we might have a suitable Ubuntu upstart expert on hand :-). Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672719: grass: diff for NMU version 6.4.3-2.1
tags 672719 + patch
tags 672719 + pending
tags 728150 + patch
tags 728150 + pending
thanks
Dear maintainer,
I've prepared an NMU for grass (versioned as 6.4.3-2.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru grass-6.4.3/debian/changelog grass-6.4.3/debian/changelog
--- grass-6.4.3/debian/changelog2013-09-26 11:21:23.0 +0200
+++ grass-6.4.3/debian/changelog2013-12-14 12:35:21.0 +0100
@@ -1,3 +1,13 @@
+grass (6.4.3-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * On ia64 build with $(HARDENING_DISABLE_PIE_CFLAGS_FILTER) filtered for
+now (closes: #728150)
+ * Add patch fix_big-endian_issues which allows grass to build on s390x
+and ppc64 (closes: #672719)
+
+ -- Paul Gevers elb...@debian.org Sat, 14 Dec 2013 12:17:17 +0100
+
grass (6.4.3-2) unstable; urgency=low
[ M. Hamish Bowman ]
diff -Nru grass-6.4.3/debian/patches/fix_big-endian_issues
grass-6.4.3/debian/patches/fix_big-endian_issues
--- grass-6.4.3/debian/patches/fix_big-endian_issues1970-01-01
01:00:00.0 +0100
+++ grass-6.4.3/debian/patches/fix_big-endian_issues2013-12-14
12:28:48.0 +0100
@@ -0,0 +1,151 @@
+Description: Fix big endian behavior
+Origin: https://trac.osgeo.org/grass/changeset/57855
+Bug: https://trac.osgeo.org/grass/ticket/1430
+Bug-Debian: http://bugs.debian.org/672719
+
+--- a/lib/vector/diglib/portable.c
b/lib/vector/diglib/portable.c
+@@ -155,21 +155,19 @@
+ memset(buf, 0, cnt * sizeof(long));
+ /* read from buffer in changed order */
+ c1 = (unsigned char *)buffer;
+- if (lng_order == ENDIAN_LITTLE)
+- c2 = (unsigned char *)buf;
+- else
+- c2 = (unsigned char *)buf + nat_lng - PORT_LONG;
++ c2 = (unsigned char *)buf;
+ for (i = 0; i cnt; i++) {
+ /* set to FF if the value is negative */
+ if (lng_order == ENDIAN_LITTLE) {
+ if (c1[PORT_LONG - 1] 0x80)
+ memset(c2, 0xff, sizeof(long));
++ memcpy(c2, c1, PORT_LONG);
+ }
+ else {
+ if (c1[0] 0x80)
+ memset(c2, 0xff, sizeof(long));
++ memcpy(c2 + nat_lng - PORT_LONG, c1, PORT_LONG);
+ }
+- memcpy(c2, c1, PORT_LONG);
+ c1 += PORT_LONG;
+ c2 += sizeof(long);
+ }
+@@ -227,21 +225,19 @@
+ memset(buf, 0, cnt * sizeof(int));
+ /* read from buffer in changed order */
+ c1 = (unsigned char *)buffer;
+- if (int_order == ENDIAN_LITTLE)
+- c2 = (unsigned char *)buf;
+- else
+- c2 = (unsigned char *)buf + nat_int - PORT_INT;
++ c2 = (unsigned char *)buf;
+ for (i = 0; i cnt; i++) {
+ /* set to FF if the value is negative */
+ if (int_order == ENDIAN_LITTLE) {
+ if (c1[PORT_INT - 1] 0x80)
+ memset(c2, 0xff, sizeof(int));
++ memcpy(c2, c1, PORT_INT);
+ }
+ else {
+ if (c1[0] 0x80)
+ memset(c2, 0xff, sizeof(int));
++ memcpy(c2 + nat_int - PORT_INT, c1, PORT_INT);
+ }
+- memcpy(c2, c1, PORT_INT);
+ c1 += PORT_INT;
+ c2 += sizeof(int);
+ }
+@@ -299,21 +295,19 @@
+ memset(buf, 0, cnt * sizeof(short));
+ /* read from buffer in changed order */
+ c1 = (unsigned char *)buffer;
+- if (shrt_order == ENDIAN_LITTLE)
+- c2 = (unsigned char *)buf;
+- else
+- c2 = (unsigned char *)buf + nat_shrt - PORT_SHORT;
++ c2 = (unsigned char *)buf;
+ for (i = 0; i cnt; i++) {
+ /* set to FF if the value is negative */
+ if (shrt_order == ENDIAN_LITTLE) {
+ if (c1[PORT_SHORT - 1] 0x80)
+ memset(c2, 0xff, sizeof(short));
++ memcpy(c2, c1, PORT_SHORT);
+ }
+ else {
+ if (c1[0] 0x80)
+ memset(c2, 0xff, sizeof(short));
++ memcpy(c2 + nat_shrt - PORT_SHORT, c1, PORT_SHORT);
+ }
+- memcpy(c2, c1, PORT_SHORT);
+ c1 += PORT_SHORT;
+ c2 += sizeof(short);
+ }
+@@ -438,15 +432,15 @@
+ }
+ else {
+ buf_alloc(cnt * PORT_LONG);
+- if (lng_order == ENDIAN_LITTLE)
+- c1 = (unsigned char *)buf;
+- else
+- c1 = (unsigned char *)buf + nat_lng - PORT_LONG;
++ c1 = (unsigned char *)buf;
+ c2 = (unsigned char *)buffer;
+ for (i = 0; i cnt; i++) {
+- memcpy(c2, c1, PORT_LONG);
+- c1 += PORT_LONG;
Bug#731285: pu: package kexec-tools/1:2.0.3-1
Control: tags -1 + pending On Wed, 2013-12-04 at 13:49 +, Jonathan Wiltshire wrote: On 2013-12-04 00:04, Khalid Aziz wrote: A debdiff of proposed changes is attached. Please go ahead. Flagged for acceptance; thanks. (Unfortunately, the fix was uploaded after the window for today's point release had closed, so will be included in the next one.) Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#597785: [gedit]: Spellcheck overlooks misspelled words in PHP files
I forgot to mention acrocycle.
Bug#732133: [aide] Please to not run start-stop-daemon-in-maintainer-script
Package: aide Severity: important The maintainer script call start-stop-daemon directly. Long-running daemons should be started and stopped via init scripts using invoke-rc.d rather than directly in maintainer scripts. Refer to Debian Policy Manual section 9.3.3.2 (Running initscripts) for details. Severity: normal, Certainty: certain Please do not paper over by override lintian warning. Bastien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720426: pu: package openssl/1.0.1e-2
On Thu, Nov 21, 2013 at 09:35:20PM +0100, Kurt Roeckx wrote: On Mon, Sep 30, 2013 at 07:06:33PM +0200, Kurt Roeckx wrote: On Mon, Sep 30, 2013 at 01:46:41AM +0200, Cyril Brulebois wrote: Control: tag -1 moreinfo Kurt Roeckx k...@roeckx.be (2013-09-23): I actually consider the arm assembler and nistp curves to be important, even if the bugs might only be filed at severity level wishlist. The nistp curves are even security related since they are then implemented with constant time removing a side channel attack. Then the BTS should know, and/or you should have mentioned it in your pu request. I wouldn't bother trying to get those to stable if I didn't think they were important. So can someone please do something about this request? Ping? Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729998: pu: package gnash/0.8.11~git20120629-1+wheezy1
On Wed, Nov 20, 2013 at 07:41:49PM +0100, Gabriele Giacone wrote: Control: fixed 729995 0.8.11~git20130903-1 On Wed, Nov 20, 2013 at 06:07:01AM +, Adam D. Barratt wrote: Please produce a full debdiff for your proposed package, and attach it to this bug report. Attached. The version information for #729995 suggests that it also applies to the version of gnash in testing and unstable. Is that correct? If not then please fix the versions. Done above. Anything still wrong/missing here? I thought it was fine for 7.3. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721615:
reassign 721615 gedit-plugins
Bug#658411: gedit: Some keyboard shortcuts do not work on GEdit (examples : CTRL+A or CTRL+F)
I forgot to mention David here.
Bug#662098: Removing line with Ctrl+D sometimes is not undoable
I forgot to mention Patrik here.
Bug#732134: [wordpress] Themes and plugins not working
Package: wordpress Version: 3.7.1+dfsg-1 Severity: normal --- Please enter the report below this line. --- Hello, I have same problems I had since first install of WordPress 3.6 on Debian 7: themes and plugins are installed under directory: /var/lib/wordpress/wp-content/plugins but most of them have to manually moved to: /usr/share/wordpress/wp-content/plugins and symlinked from the first to the second location to work. Then, when I have to update them, I have to move them back to first location (after deleting the symlink), to do the update, to move to the second location and to do the symlink again. For sure there is a better way to do it and this is due to something I configured badly, but I don't know what. Bye, Matteo --- System information. --- Architecture: amd64 Kernel: Linux 3.11-2-amd64 Debian Release: jessie/sid 500 testing www.deb-multimedia.org 500 testing security.debian.org 500 testing ftp.it.debian.org --- Package information. --- Depends (Version) | Installed ===-+- apache2 | 2.4.6-3 OR httpd | libapache2-mod-php5 | 5.5.6+dfsg-1 OR php5| 5.5.6+dfsg-1 mysql-client| 5.5.33+dfsg-1 php5-gd | 5.5.6+dfsg-1 php5-mysql | 5.5.6+dfsg-1 OR php5-mysqlnd| libjs-cropper(= 1.2.2) | 1.2.2-1 libphp-phpmailer (= 5.1) | 5.1-1 libphp-snoopy(= 1.2.4) | 1.2.4-2 tinymce ( 3.4.8+dfsg0.0~) | 3.4.8+dfsg0-1 tinymce(= 3.4.8+dfsg0) | 3.4.8+dfsg0-1 Recommends (Version) | Installed =-+-=== wordpress-l10n| 3.7.1+dfsg-1 Suggests (Version) | Installed -+- mysql-server (= 5.0.15) | 5.5.33+dfsg-1
Bug#259112: gedit: Gedit does not accept data from a pipe
I forgot to mention Erik and Loic.
Bug#730332: (no subject)
From https://bugs.launchpad.net/debian/+source/boinc/+bug/1250652/comments/9 When launching BOINC Manager from the Gnome menu it produces an error that it is unable to find /var/lib/boinc-client, which of course does not exist unless boinc-client is also installed. Launching from the terminal does not produce this error. This is solved by removing the Path= variable from the .desktop file (and logging out/in). [Desktop Entry] Type=Application Version=1.0 Exec=/usr/bin/boincmgr Path=/var/lib/boinc-client Icon=boincmgr-32 Categories=System;Monitor;GTK; Name=BOINC Manager GenericName=BOINC monitor and control utility GenericName[cs]=Monitorovací a ovládací nástroj pro BOINC GenericName[de]=BOINC Überwachungs- und Kontrollprogramm GenericName[pt]=Monitorização BOINC e utilitário de controlo Comment=Configure or monitor a BOINC core client Comment[cs]=Monitoruje a nastavuje klienta BOINC Comment[de]=BOINC Basis Client konfigurieren oder überwachen Comment[pt]=Configurar ou monitorizar o cliente básico do BOINC HOWEVER: This exists so that boincmgr can connect to the client automatically. A better solution was a simple: mkdir /var/lib/boinc-client Then boincmgr does not complain. Unless there is some intelligence that the menu system can use to ignore the Path= if the directory does not exist, then it might be worth adding an empty /var/lib/boinc-client to the boinc-manager package to avoid this error. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584731: evince hangs when a recent opened file is on a stalled partition
I forgot to mention Pierre, Ross and Daniel here.
Bug#575256: evince: Crash when trying to search for text
I forgot to mention Tom here.
Bug#732135: RFS: spatialite/4.1.1-5
Package: sponshorship-requests Severity: normal Dear mentors, As part of the upcoming SpatiaLite transition am I looking for a sponsor for my package spatialite. Please refer to the thread on debian-gis@ for more information on this transition: https://lists.debian.org/debian-gis/2013/10/msg9.html Package name: spatialite Version : 4.1.1-5 Upstream Author : Alessandro Furieri a.furi...@lqt.it URL : https://www.gaia-gis.it/fossil/libspatialite/ License : MPL-1.1 or GPL-2.0+ or LGPL-2.1+ Section : science It builds those binary packages: libspatialite-dev - Geospatial extension for SQLite - development files libspatialite5 - Geospatial extension for SQLite - libraries libspatialite5-dbg - Geospatial extension for SQLite - debugging symbols To access further information about this package, please visit the following URL: http://mentors.debian.net/package/spatialite Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/spatialite/spatialite_4.1.1-5.dsc More information about SpatiaLite can be obtained from https://www.gaia-gis.it/fossil/libspatialite/. Changes since the last upload: * Enable building with libxml2 support. * Add 11-link-libxml2.patch to link libxml2 when building test cases. * Update symbols file for XML related symbols. * Bump Standards-Version to 3.9.5, no changes required. Regards, Sebastiaan Couwenberg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529768: evince: zoom pop-up menu doesn't work the first time it is selected
I forgot to mention Celejar and Denis here.
Bug#727027: Anyone home?
Really, is anybody still working on debian with clamav? I'm definitely going for CentOS next install. All this waiting is making me itch. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731358: libapparmor1: arch-dependent files in Multi-Arch: same package
Control: found -1 2.8.0-3 Some files still differ accross architectures: /usr/share/man/man2/aa_change_profile.2.gz /usr/share/man/man2/aa_find_mountpoint.2.gz An example diff between i386 and amd64 (after ungzipping) is attached. -- Jakub Wilk diff -ur libapparmor1_2.8.0-3_i386/usr/share/man/man2/aa_change_profile.2 libapparmor1_2.8.0-3_amd64/usr/share/man/man2/aa_change_profile.2 --- libapparmor1_2.8.0-3_i386/usr/share/man/man2/aa_change_profile.2 2013-12-13 20:57:16.0 +0100 +++ libapparmor1_2.8.0-3_amd64/usr/share/man/man2/aa_change_profile.2 2013-12-13 20:22:44.0 +0100 @@ -133,7 +133,7 @@ .\ .\ .IX Title AA_CHANGE_PROFILE 2 -.TH AA_CHANGE_PROFILE 2 2012-02-16 AppArmor 2.8.0 AppArmor +.TH AA_CHANGE_PROFILE 2 2012-02-15 AppArmor 2.8.0 AppArmor .\ For nroff, turn off justification. Always turn off hyphenation; it makes .\ way too many mistakes in technical documents. .if n .ad l diff -ur libapparmor1_2.8.0-3_i386/usr/share/man/man2/aa_find_mountpoint.2 libapparmor1_2.8.0-3_amd64/usr/share/man/man2/aa_find_mountpoint.2 --- libapparmor1_2.8.0-3_i386/usr/share/man/man2/aa_find_mountpoint.2 2013-12-13 20:57:16.0 +0100 +++ libapparmor1_2.8.0-3_amd64/usr/share/man/man2/aa_find_mountpoint.2 2013-12-13 20:22:44.0 +0100 @@ -133,7 +133,7 @@ .\ .\ .IX Title AA_FIND_MOUNTPOINT 2 -.TH AA_FIND_MOUNTPOINT 2 2012-02-16 AppArmor 2.8.0 AppArmor +.TH AA_FIND_MOUNTPOINT 2 2012-02-15 AppArmor 2.8.0 AppArmor .\ For nroff, turn off justification. Always turn off hyphenation; it makes .\ way too many mistakes in technical documents. .if n .ad l
Bug#594838: $ evince http://... does not work
I forgot to mention people jidanni and jak here.
Bug#605620: evince: Image is not displayed
I forgot to mention Christophe here.
Bug#607920: evince: ask password on a pdf without password
I forgot to mention matthieu here.
Bug#703005: Additional Info in my environment for kscreenlocker exit delays
I'm not sure if this is the same bug... Summary: occasional/random screen remains blank for ~10 seconds after typing unlock password (password dialog disappears, screen is completely blank) (for me, i'd say it happens 90% + of the time) often followed by up to 30 second No-Mouse-Or-Keyboard condition (mouse cursor does not display, keyboard input is not accepted, just have to wait) (this happens perhaps 50-75% of the time) not related to load/#applications/#windows/ amount-of-time-logged-already-logged-in. In my environment several of us have, perhaps within the last 3 or so months started seeing a *random* screenlocker exit delay of about 10 seconds where the screen stays black. It's not clear how many users this affects, as i have only anecdotal info from myself and one other fellow system administrator, and one user who only mentioned it in the course of debugging another issue after upgrading him to Wheezy. (everything's working great, but there's a 10 second delay before i can get to work after unlocking the screen...) (i.e. we may have a number of users who are not reporting the problem, assuming that's just the way things are). We recently (~6 months ago) instituted *advisory* (i wanted mandatory, but we're fighting with management :-( ) screenlocking defaults here. /etc/kde4/kscreensaverrc [ScreenSaver] ActionBottomLeft=0 ActionBottomRight=0 ActionTopLeft=0 ActionTopRight=0 Enabled=true Lock=true LockGrace=6 PlasmaEnabled=false Saver=kblank.desktop Timeout=1800 I do not know if this has any impact on this bug, but it seems unlikely. Additionally, for myself, ocasionally, i am left without a mouse or keyboard for upto 30 seconds after the 10 second blank screen delay and the screen display comes back. I have not heard others report this (yet). FWIW, i have been working on using the kdebugdialog function to send 'kscreenlocker' notifications to a script, so that i could also activate other functions such as locking the ssh-agent, pausing multi-media applications, signalling IM clients to put themselves in away mode. (it'd be awesome if 'kscreenlocker' had a mechanism internal to run user-supplied lock/unlock functions, but at least with the debug dialog functions, i can hack this). I am only doing this on my OWN system, so this should not affect any other user, but it might help explain the 30-second no-mouse-or-keyboard condition i sometimes see. X0rg.0.log and .xsession-errors have nothing that appears relevant. I have re-installed 3 variant releases of the nVidia proprietary drivers to ensure that's not the cause. The screensaver package has not been updated in a while, so this is likely a change made to another X11 package/lib that affects or is triggered by the kscreenlocker application. thanks, --stephen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730416: Fixed
Version: 3.0.4-2+b1 Hi, This has been fixed by the binNMU for rebuilding against ffms2 2.19. -- Sebastian signature.asc Description: Digital signature
Bug#563880: file-roller: error when renaming an entry to a name containing space
I forgot to mention people here.
Bug#576600: file-roller: unable to extract in the actual directory
I forgot to mention gpe here.
Bug#732136: glibtop: Non-standard uts for running kernel
Package: unetbootin Version: 585-2 Severity: minor As I start unetbootin under 3.x series kernel, I get following: $ unetbootin $ glibtop: Non-standard uts for running kernel: release 3.11-2-amd64=3.11.0 gives version code 199424 Qt: Session management error: None of the authentication protocols specified are supported As I look around the web, similar issue is reported elsewherre. e.g.: https://bugzilla.redhat.com/show_bug.cgi?id=711192 Matthew Miller 2011-06-09 13:31:02 EDT (In reply to comment #2) Are you sure you have reported this against the right package?, I see it as a kernel issue. I'm positive. The problem is that the utilities make the erroneous assumption that the kernel version always matches %d.%d.%d — three digits separated by dots. But the kernel is now just 3.0. You could argue that it'd be more polite of the kernel to just claim to be 3.0.0, but as far as I can see Linus Torvalds is against that. (Part of the _point_ of the change was to reduce the number of digits.) Maybe somewhere in unetbootin, similar code exists. Osamu -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages unetbootin depends on: ii libc6 2.17-97 ii libgcc1 1:4.8.2-10 ii libqt4-network 4:4.8.5+git192-g085f851+dfsg-2 ii libqtcore4 4:4.8.5+git192-g085f851+dfsg-2 ii libqtgui4 4:4.8.5+git192-g085f851+dfsg-2 ii libstdc++6 4.8.2-10 ii mtools 4.0.18-1 ii p7zip-full 9.20.1~dfsg.1-4 ii syslinux3:4.05+dfsg-6+deb8u1 ii udev204-5 Versions of packages unetbootin recommends: ii extlinux 3:4.05+dfsg-6+deb8u1 ii unetbootin-translations 585-2 unetbootin 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#619296: file-roller: Won't delete files in a .xpi
I forgot to mention real here.
Bug#732137: gnustep-gui-doc: missing .../Gui/ProgrammingManual/manual_toc.html referenced in GNUStep doc index.html
Package: gnustep-gui-doc Version: 0.20.0-3 Severity: normal Dear Maintainer, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I've installed the latest gnustep doc packages: ii gnustep-base-doc 1.22.1-4.2 ii gnustep-core-doc 7.7 ii gnustep-gui-doc0.20.0-3 ii gnustep-make-doc 2.6.2-2.1 and found that the index.html page provided by: gnustep-base-doc: /usr/share/GNUstep/Documentation/index.html has a link to GUI documentation pages that are not installed by gnustep-gui-doc, for example (I have installed the GUI part of GNUstep, in addition to the doc files above): The following links will work only if you have installed the GUI portion of GNUstep. GUI Programming Manual (PDF) This links to: file://localhost/usr/share/GNUstep/Documentation/Developer/Gui/ProgrammingManual/manual_toc.html which is not installed by the doc packages above. Only two AppKit files are in the directory where the GUI manual_toc.html should be; none of the links in AppKit.html works but the pdf is fine. This link should be the same as the one in gnustep.org: http://www.gnustep.org/resources/documentation/Developer/Gui/ProgrammingManual/AppKit_toc.html Other links to the GUI documentation, like GUI Library API and GUI Additions, are correctly linked in the Documentation/index.html =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/6 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages gnustep-gui-doc depends on: ii gnustep-common [gnustep-fslayout-fhs] 2.6.2-2.1 gnustep-gui-doc recommends no packages. gnustep-gui-doc suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731672: uim-gtk3: uim systray not appearing in gnome shell
Control: forwarded -1 https://github.com/uim/uim/issues/34 Control: tags -1 + moreinfo On Sun, Dec 08, 2013 at 05:02:42PM +0900, Marios Sioutis wrote: under gnome-shell 3.8.4 the uim systray is not showing in the notification bar. Specifically, uim-toolbar-gtk3-systray is not showing up. Other systray icons (e.g. dropbox, skype, redshift, steam) show up properly. confirmed. The uim systray would also show up on previous versions of gnome shell, but since other systray icons show up properly I decided to report the bug here. could you tell me exact versions for previous versions of gnome shell? -- Regards, dai GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E signature.asc Description: Digital signature
Bug#732084: RFS: slowhttptest/1.6-1 [ITP] -- Application layer Denial of Service attacks simulation tool
Hi Neutron, On Sat, 14 Dec 2013 05:30:51 Neutron Soutmun wrote: I am looking for a sponsor for my package slowhttptest Nice, thank you for your work. :) I hope you'll forgive me for pedantic nitpicking but let's fix the following minor issues before we upload: * Standards 3.9.4 (expected current version 3.9.5). * Needless versioned Build-Depends on debhelper (this exact version is in stable). Besides is there are any features of this particular version is in use? * Short package description starts with capital letter (lowercase would be better). Thanks. -- Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B signature.asc Description: This is a digitally signed message part.
Bug#729998: pu: package gnash/0.8.11~git20120629-1+wheezy1
On Sat, 2013-12-14 at 15:46 +0100, Gabriele Giacone wrote: On Wed, Nov 20, 2013 at 07:41:49PM +0100, Gabriele Giacone wrote: Control: fixed 729995 0.8.11~git20130903-1 On Wed, Nov 20, 2013 at 06:07:01AM +, Adam D. Barratt wrote: Please produce a full debdiff for your proposed package, and attach it to this bug report. Attached. The version information for #729995 suggests that it also applies to the version of gnash in testing and unstable. Is that correct? If not then please fix the versions. Done above. Anything still wrong/missing here? Someone reviewing the patch, at least. I thought it was fine for 7.3. For it to get in to 7.3 you'd have needed to have uploaded a new package. I'm not sure how you reach the conclusion of it was fine for 7.3 with no upload having occurred (or being ACKed). Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732106: linux-image-686-pae: support Technisat CableStar Combo
Control: reassign -1 src:linux Control: tag -1 upstream On Sat, 2013-12-14 at 07:52 +0100, Janusz S. Bień wrote: Package: linux-image-686-pae Version: 3.10+52~bpo70+1 Severity: wishlist The patch is already available for some time at http://www.mail-archive.com/linux-media@vger.kernel.org/msg68690.html but for unknown reasons has not migrated to https://patchwork.linuxtv.org/project/linux-media/list/ I would guess that the patch was not formatted correctly in email. See https://www.kernel.org/doc/Documentation/email-clients.txt. As I got no answer from the linux-media list to my question http://www.mail-archive.com/linux-media@vger.kernel.org/msg67959.html when the support will be available in the official kernel? Is it already on some kind of waiting list or some additional action is required? I report the problem directly to Debian maintainers. Please correct me if this is not the proper procedure. I don't have any ability to review that patch, so until it is applied upstream I won't apply it to Debian either. (It doesn't have to be in a release - just accepted by the media maintainer.) Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Bug#732138: RFS: libjs-forge/0.2.22+dfsg-1 [ITP]
Package: sponsorship-requests Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear mentors, I am looking for a sponsor for my package libjs-forge * Package name: libjs-forge Version : 0.2.22+dfsg-1 Upstream Author : Digital Bazaar, Inc. * URL : http://digitalbazaar.com/forge/ * License : BSD or GPL-2 Section : devel It builds those binary packages: libjs-forge - JavaScript Security and Cryptography To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libjs-forge Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libj/libjs-forge/libjs-forge_0.2.22+dfsg-1.dsc The package is an important core dependency for Geierlein, which is needed by German small businesses to communicate with fiscal authorities. I am working on getting Geierlein into Debian to get rid of one more point in the average companz's workflow ehere they still depend on Windows. I have worked together on the package with Helmut Grohne, who did a first review. I would not mind managing the package as co-maintainer under the pkg-javascript umbrella if that is desired, though. Regards, Dominik George - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/mksh -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iQJOBAEBCAA4BQJSrIgsMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pY64w//dtqWSuTGD6Dyumgdgk6I TYchgagHTehAWxMYPfoueqUVKwUg6+M4ZOkiVIHLv2/VebyEeaMAhzAYswYYTbFp NoT4zGvBQWefTRTIKk9Ifr9QMw/MCvZrMKhaygUZU9lti3rtYrUdXuk2YZzTDYVS 4jJ/HcSUcoCmF0nAjLYAeiYDzHPJebiT0nTPcDWREXzOtmouIUhbl05i8Rt/ALgH TO/17ENIqIl3lMUhlfWKZ9j4x7rlhdoyfshFfpi5Wg1U4ZRjF+Fh1gdt8aqDe7Ae GTkTV/U+33rckT6PjFNTFziLLPaCgU+WdOYJD7YZESmSGOdQhmqLqhiy0/VKvdh6 bJuTvuMqh/PxDVJWP32/sIVmnyi6fTHmkDxHdJbhZE9o5PaadMp1V7R97bL9Sh4+ hPr3QAEVQYR/DaCulek9lQWGd4WlKy5BqFz0YlKq6i1+mP/AHdr93rCrCsYqdCMd PlsF9zjrx7GxuDtZpZsxieX2KX0UtBoM3And1MIJ2WljFPHqsdSZqSegKwMRx7rl TF5wxLhGHaL/UM84z8IpxfD9wRIVxHhrq2U4a9/a4jF/89+kK+7ci9mFRVnm2r7V fb0IeHDrWfSxPV/6lZn1CbZLrIH6rFN6mSgFP53RzSiQyN2+c5nkFYqWtZndaNs9 9zPs80ACsDv/cfnC4aWIQ+A= =AkcT -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#700553: Updating the python-pysearch Uploaders list
Control: reassign -1 wnpp Control: retitle -1 O: python-pysearch -- Python module for the Yahoo Search Web Service On 2013-02-14 09:04:23, Ricardo Mones wrote: Package: python-pysearch Version: 3.1-1.1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Thomas Bläsing thoma...@pool.math.tu-berlin.de has not been working on the python-pysearch package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Since Thomas was the only human maintainer of python-pysearch and nobody of the team seems to be interested in it, I'm orphaning python-pysearch now. Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#731884: Problem is order of partitions seen by mdadm
On Wed, 2013-12-11 at 14:19 +0100, John Hughes wrote: When the system works it builds the devices from sda and sdb. When it fails its because it tries to build a container from sda3 and sdb. To mdadm sda3 looks like it is part of an imsm container, but it's not. It isn't even a partition! sda and sdb contain a imsm raid0 device that is partitioned. Since sda3 extends beyond the end of sda it gets truncated by the kernel, and if mdadm examines it it looks like it is part of the imsm device. My problem can be fixed by adding : DEVICE /dev/sda /dev/sdb containers to the mdadm.conf (and rebuilding the initramfs). But this can go wrong if you have another device plugged in at boot time and the device names change... I guess the bug report should be reassigned to mdadm. Right, I don't think it is correct to look for firmware RAID signatures inside partitions. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Bug#732139: PNG is not the preferred form for modification
Package: python-sfml Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, your new package python-sfml (1.5.1) contains two PNGs: ./python-sfml-1.3/doc/source/tutorials/system-thread-ordered.png ./python-sfml-1.3/doc/source/tutorials/system-thread-mixed.png as they are created with gimp, this is not the preferred form for modification (- DFSG 2). So please add the corresponding XCF files to the package. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732140: parameterized init.d support of --chroot and --user
Package: openvpn
Version: 2.3.2-7
Tags: patch
This patch is an update of the patch in bug 614036. It is refreshed
for the changes to the init.d script merged in 2.3.2-6. It is also
re-written to be more generic.
The script now reads external data files to build a list of files to
copy into the chroot. It executes a root-privileged, non-chrooted
down script, again external. There is no policy baked into this
script. (Though there is special-cased support for copying /proc,
/run/openvpn, and /dev/null, if any of these are requested by an
external file list.)
Stephen
--- openvpn-2.3.2-7/debian/openvpn.init.d 2013-11-27 05:21:19.0
-0800
+++ openvpn-2.3.2-patched/debian/openvpn.init.d 2013-12-04 22:14:57.805048898
-0800
@@ -15,6 +15,32 @@
# in /etc/default/openvpn and /etc/openvpn/*.conf
### END INIT INFO
+# This script supports --chroot in the following ways:
+#
+# It can create and populate a chroot tree.
+# Files named in /etc/openvpn/chroot.files.d/*.files will be copied
+# into the configured chroot directory. Files should be listed one per
+# line; lines that are blank or start with the # character are ignored.
+# Wild-card patterns are allowed, but they must match exactly one file;
+# this feature is intended to make versioned shared library matching
+# more robust. This script copies no files by default, but it does
+# handle some files specially, if they are requested; see the code.
+#
+# It creates the --user for you.
+# If the user named by the --user option does not exist, this script
+# will create it. This feature makes it easier to copy config files
+# onto a new machine and have openvpn just work the first time.
+#
+# It implements a down hook.
+# If an executable file /etc/openvpn/vpn-name.down exists,
+# it will be executed without arguments after the openvpn daemon is killed.
+# Unlike the --down script implemented by the daemon, this hook receives
+# no arguments nor environment variables; if it needs any, a --down
+# script called from the daemon must store them where this hook can
+# find them. This down hook is run as root and not in a chroot;
+# this capability may be useful when using --chroot and/or --user with
+# the daemon.
+
# Original version by Robert Leslie
# r...@mars.org, edited by iwj and cs
# Modified for openvpn by Alberto Gonzalez Iniesta a...@inittab.org
@@ -27,6 +53,7 @@
DAEMON=/usr/sbin/openvpn
DESC=virtual private network daemon
CONFIG_DIR=/etc/openvpn
+CHROOT_FILES=$CONFIG_DIR/chroot.files.d
test -x $DAEMON || exit 0
test -d $CONFIG_DIR || exit 0
@@ -38,6 +65,14 @@
. /etc/default/openvpn
fi
+# Outputs the value of a config variable.
+# $1 -- the name of the config variable to output
+config_line() {
+sed -n s/^[ \t]*$1[ \t]\+\(.*\)/\1/p \
+$CONFIG_DIR/$NAME.conf
+}
+
+# Start 1 VPN. $NAME is the name of the VPN to start.
start_vpn () {
if grep -q '^[ ]*daemon' $CONFIG_DIR/$NAME.conf ; then
# daemon already given in config file
@@ -58,7 +93,74 @@
STATUSARG=--status /run/openvpn/$NAME.status $STATUSREFRESH
fi
-mkdir -p /run/openvpn
+USER_HOME=/var/lib/openvpn
+
+CHROOT=$(config_line chroot)
+if [ -n $CHROOT ]; then
+ # Sanity check for chroot directory name:
+ # must include openvpn and not include ..
+ if echo $CHROOT | grep -q -i openvpn
+echo $CHROOT | grep -q -v '\.\.'
+ then
+USER_HOME=$CHROOT
+# Copy requested files into the chroot.
+local files_to_copy_into_chroot=$(\
+egrep -h -v '^#|^[[:blank:]]*$' $CHROOT_FILES/*.files)
+for file in $files_to_copy_into_chroot ; do
+ case $file in
+*..*)
+ log_warning_msg Pattern .. illegal in chroot file name: $file
+ ;;
+/*)
+ mkdir -p $CHROOT/$(dirname $file)
+ case $file in
+/dev/null)
+ test -c $CHROOT/dev/null || mknod $CHROOT/dev/null c 1 3
+ ;;
+/proc*)
+ mkdir -p $CHROOT/$file
+ mount --bind $file $CHROOT/$file
+ ;;
+/run/?*)
+ mkdir -p $CHROOT/$file
+ # Arrange that this, like in the real /run, gets
+ # cleared at boot.
+ grep -q $CHROOT/$file /etc/mtab ||
+ mount -t tmpfs -o noexec,nodev none $CHROOT/$file
+ rm -rf $file
+ # Link from the real rooted directory so future
+ # invocations of this script will find it.
+ ln -s $CHROOT/$file $file
+ ;;
+/*)
+ if [ -f $file ]; then
+cp -pu $file $CHROOT/$file
+ elif [ -d $file ]; then
+dest_dir=$CHROOT/$(dirname $file)
+cp -pua $file $dest_dir
+ fi
+
Bug#732136: gksu: glibtop: Non-standard uts for running kernel
control: found 732136 2.0.2-6 Hi, After filing this bug to unetbootin, I realized this problem was caused by gksu (called from unetbootin). This assign version number of gksu in question. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732136 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-==--=== ii gksu 2.0.2-6 amd64graphical frontend to su Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#239816: libparted Atari partition table support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 12/14/2013 02:26 AM, Thorsten Glaser wrote: The ST, maybe (except for the only-in-museums part), but the TT and Falcon run Debian GNU/Linux just finely. Linux ara5.mirbsd.org 3.11-2-m68k #1 Debian 3.11.7-1 (2013-11-09) m68k GNU/Linux (Hm, should dist-upgrade and reboot that box, too.) I'm still not following. You are talking about a 30 year old computer running at like 16 MHz with maybe 512k of ram? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJSrJFjAAoJEI5FoCIzSKrwM8wH/iuaF/fEkSO0qdGVdFtI85Ns ip+5tsbQFHR4cPYy7YsiIN6pQj4iER9l8CvTM/s2YCIkq+OGMcRxfnDfQtgXSk3k 646Q6QGDEWDY37gq/OESmmD+MmiB9wqfNGHCGdT4TxqTlq0qzQP8I30jULEm40uF rrlB/LYnOtkH4SZuG9m0e5OUb3RD7BaV+hbMe3TV1pcT9CJNV9kp72jGq8RHV3K6 balN3lERPIWo/w/8vzrhx81u2IQSqd4/ueiHZ2dVwO4bV8yqkONaVGTfowgukjEO tdmIBL/qxjTzDpE4PRDkN/WflzOHMSKcYsQGXiFu06VX1CMKVIP/5SaLSr66Mas= =5mc4 -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#477689: ITP: python-antlr3 -- antlr 3 python runtime
Hello, Are there any news on this? I'm working on a package which depends on python-antlr3... -- Cheers, Andrew signature.asc Description: PGP signature
Bug#662098: Removing line with Ctrl+D sometimes is not undoable
Hmm, I should be subscribed to the bug now. Thought I was. I haven't used gedit for a long time now, and instead Pluma 1.6.0 from the MATE Desktop Environment, which is a fork of gedit (2.*, I think). FWIW, I have no issue with Pluma. From what I remember it was not easy to reproduce. I know I tried for several hours different ways. It would only happen when I was not trying to observe it. My theory is that the undo stack becomes corrupted in some situation (for example, pointers are assigned incorrectly). A review of the code that has to do with undo/redo and line-deletion would probably discover the bug if it is still there. ~ Patrik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
