Bug#697186: [Pkg-sssd-devel] Bug#697186: Missing dependency on libcollection-dev
On 07.01.2013 22:52, Salvatore Bonaccorso wrote: Hi @Timo: Not to put any pressure or so. In case you are short of time I can prepare a NMU for this and upload. That would be fine, or I can push the change to git and you could pull from there? -- t -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697666: movabletype-opensource: mt-upgrade.cgi vulnerability
Package: movabletype-opensource Version: 4.3.8+dfsg-0+squeeze2 Severity: grave Justification: remote command execution Tags: security patch - Forwarded message from Takeshi Nick Osanai - Date: Tue, 8 Jan 2013 11:26:38 +0900 From: Takeshi Nick Osanai To: mtos-dev Subject: [Mtos-dev] Movable Type 4.38 patch to fix a known upgrading security issue X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Urchin-Spam-Score-Int: -18 X-Bogosity: Ham, tests=bogofilter, spamicity=0.00, version=1.2.2 Dear MT community members, Six Apart has found a security issue and fixed it in Movable Type 4.2 and MT 4.3. For those of you who use Movable Type 4.2 and 4.3, Six Apart strongly recommends that you upgrade to the latest released version of Movable Type or execute the steps written in below entry. This vulnerability does not exist in Movable Type versions 5.0 or later, including the latest Movable Type, version 5.2.2. For more detail information, please see the entry. http://www.movabletype.org/2013/01/movable_type_438_patch.html -- Takeshi "Nick" Osanai Movable Type Product and Marketing Manager Six Apart, Ltd. tosa...@sixapart.com http://www.movabletype.org http://www.movabletype.jp ___ Mtos-dev mailing list mtos-...@ml.sixapart.com http://ml.sixapart.com/mailman/listinfo/mtos-dev - End forwarded message - -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#689533: marked as done (exabgp: modifies conffiles (policy 10.7.3): /etc/exabgp/exabgp.env)
Your message dated Tue, 08 Jan 2013 07:32:30 + with message-id and subject line Bug#689533: fixed in exabgp 3.1.1-1 has caused the Debian Bug report #689533, regarding exabgp: modifies conffiles (policy 10.7.3): /etc/exabgp/exabgp.env to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 689533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: exabgp Version: 3.0.10-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/exabgp/exabgp.env cheers, Andreas exabgp_3.0.10-1.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: exabgp Source-Version: 3.1.1-1 We believe that the bug you reported is fixed in the latest version of exabgp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 689...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Henry-Nicolas Tourneur (supplier of updated exabgp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 02 Jan 2013 11:42:00 + Source: exabgp Binary: exabgp Architecture: source all Version: 3.1.1-1 Distribution: unstable Urgency: low Maintainer: Henry-Nicolas Tourneur Changed-By: Henry-Nicolas Tourneur Description: exabgp - BGP route injector Closes: 687134 689533 693338 697178 Changes: exabgp (3.1.1-1) unstable; urgency=low . * New upstream release * Closes: #687134 debconf abuse, notice of software behavior take places under NEWS.Debian, not in a debconf screen, information moved accordingly. * Closes: #693338 Japanese translation removed since debconf template is out. * Closes: #697178 Russian translation removed since debconf template is out. * Closes: #689533 UCF-based conf added. No more manual changes to exabgp.env, thanks to Federico Ceratto. Checksums-Sha1: 045769a7d88b0c0ae26cd32561c042bea25f6c89 1672 exabgp_3.1.1-1.dsc 157c7394ac9b5170ecc4f4609d1473ada9131cff 335407 exabgp_3.1.1.orig.tar.gz a0fddd5458378c1bf3c10dd2f5c060d1347741ed 20 exabgp_3.1.1-1.diff.gz 978a01899b43b17ad862e9773d8105ef056fc43c 141352 exabgp_3.1.1-1_all.deb Checksums-Sha256: 040d6ef46298410f6e90bad7a88e7a7f5d725a73f16ba5d5c1a1204f7ae8175f 1672 exabgp_3.1.1-1.dsc dde1eb503df9d4e9f96d5dfd83ab53cd95416fdd68c66288e045e6d118029911 335407 exabgp_3.1.1.orig.tar.gz f61f27bd17de546264aa58f40f3aafaac7021e0ef69c17f6b1b4cd7664a037ec 20 exabgp_3.1.1-1.diff.gz 95f60d512fba654cff05d3854c58ed2b66b6c3777556aea29c5df613cf05799a 141352 exabgp_3.1.1-1_all.deb Files: 5e5482868ea81e8c19d9bfc61ab0be55 1672 net optional exabgp_3.1.1-1.dsc f336bd79df4e0857ed9d9c00ca94516c
Processed: reassign 676485 to libglib2.0-0, found 676485 in 2.33.12+really2.32.4-3
Processing commands for cont...@bugs.debian.org: > reassign 676485 libglib2.0-0 Bug #676485 [upgrade-reports] squeeze->wheezy dist-upgrade Could not perform immediate configuration on 'default-jre' Bug reassigned from package 'upgrade-reports' to 'libglib2.0-0'. Ignoring request to alter found versions of bug #676485 to the same values previously set Ignoring request to alter fixed versions of bug #676485 to the same values previously set > found 676485 2.33.12+really2.32.4-3 Bug #676485 [libglib2.0-0] squeeze->wheezy dist-upgrade Could not perform immediate configuration on 'default-jre' Marked as found in versions glib2.0/2.33.12+really2.32.4-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 676485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697665: fusesmb: Impossible to install package due to unmet dependencies
Package: fusesmb
Version: 0.8.7-1.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I could not install this package on either an i386 or an amd64 system running
Sid
gael@oskar:~$ sudo aptitude install fusesmb
The following NEW packages will be installed:
fusesmb{b}
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 26.4 kB of archives. After unpacking 135 kB will be used.
The following packages have unmet dependencies:
fusesmb : Depends: fuse-utils which is a virtual package.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) fusesmb [Not Installed]
Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
Abort.
gael@oskar:~$ aptitude search '~Pfuse-utils'
gael@oskar:~$
fusesmb depends on fuse-utils which is only available for the alpha and hppa
architectures.
It should probably rather depend on fuse.
Regards, Gaël Kohler.
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-486
Locale: LANG=fr_CH.utf8, LC_CTYPE=fr_CH.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697230: asterisk: Two security issues: AST-2012-014 / AST-2012-015
Hi, On Wed, Jan 02, 2013 at 10:56:43PM +0100, Salvatore Bonaccorso wrote: > Package: asterisk > Severity: grave > Tags: security > Justification: user security hole > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi, > > the following vulnerabilities were published for asterisk. > > CVE-2012-5976[0]: > Crashes due to large stack allocations when using TCP > > CVE-2012-5977[1]: > Denial of Service Through Exploitation of Device State Caching > > If you fix the vulnerabilities please also make sure to include the > CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. > > For further information see: > > [0] http://security-tracker.debian.org/tracker/CVE-2012-5976 > [1] http://security-tracker.debian.org/tracker/CVE-2012-5977 > > Please adjust the affected versions in the BTS as needed. > > According to the advisories all 1.8.x versions seems affected. Likewise is version 1.6.2 from Stable. I have fixes ready. On a side note, I'm not sure why https://security-tracker.debian.org/tracker/CVE-2011-2666 is listed as open. The respective bug has been closed: As I mentioned before, I can change the default for alwaysauthreject, I'm just not sure this should be done on a Stable package. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697651: Fails to restore mixer settings
Package: alsa-utils Version: 1.0.25-3 Severity: serious Hi, dropping the udev rule in #636437 was a mistake and done for the wrong reasons. Without the udev rule, the mixer levels are no longer correctly restored for hot plugged sound hardware or if the driver takes longer to initialize the hardware, as relying on the init script is racy. On my SSD system, where the complete boot takes less then 3 secs, the alsa-utils init script is run before the sound module has been loaded and initialized the hardware. The udev rules thus needs to be added back. I think this needs to be fixed for wheezy, especially since this is a regression from squeeze, where we do have the udev rule. So I'm marking this as RC. There is the /usr-on-separate-partition issue, and the justification why the udev rules was mistakenly removed in the first place. We could move alsactl and libasound to /lib and /sbin, but we actually don't need to do that. If the udev rule is triggered before /usr is mounted, we can simply skip the alsactl call, since we now the sysv init script will run later. So all we have to do is to add a TEST for the existence of the /usr/sbin/alsactl binary and skip the rule if the binary is not available yet. This avoids the udev warning which apparently confuses some users. Michael -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages alsa-utils depends on: ii kmod9-2 ii libasound2 1.0.25-4 ii libc6 2.13-38 ii libncursesw55.9-10 ii libsamplerate0 0.1.8-5 ii libtinfo5 5.9-10 ii lsb-base4.1+Debian9 ii whiptail0.52.14-10 Versions of packages alsa-utils recommends: ii alsa-base 1.0.25+2+nmu2 ii pciutils 1:3.1.9-6 alsa-utils suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#696507: marked as done (festival: FTBFS: does not define DEB_HOST_MULTIARCH)
Your message dated Tue, 08 Jan 2013 00:17:34 + with message-id and subject line Bug#696507: fixed in festival 1:2.1~release-5.1 has caused the Debian Bug report #696507, regarding festival: FTBFS: does not define DEB_HOST_MULTIARCH to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 696507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: festival Version: 2.1~release-5 Severity: serious Justification: fails to build from source (but built successfully in the past) Apparently, festival seems to hardcode /usr/lib as libdir. Since Multi-Arch, this assumption is no longer valid, see for example #626877 for a similar case. This is RC because it prevents rebuilds of this source package. Build log: […] Update library Festival UniSyn_diphone.o us_diphone_unit.o us_diphone_index.o a - UniSyn_diphone.o a - us_diphone_unit.o a - us_diphone_index.o Making in directory src/main ... making dependencies -- festival_main.cc audsp.cc festival_client.cc g++ -c -g -O3 -fPIC -Wall -Wno-non-template-friend -I../../src/include -I/usr/lib/speech_tools/include festival_main.cc make[4]: *** No rule to make target `/usr/lib//libestools.a', needed by `festival'. Stop. make[3]: *** [main] Error 2 make[2]: *** [src] Error 2 make[2]: Leaving directory `/tmp/buildd/festival-2.1~release' make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory `/tmp/buildd/festival-2.1~release' make: *** [build-arch] Error 2 Manual check in the buildd chroot: (pbuild19661)root@ara2:~/festival-2.1~release # find /usr/lib -name libestools.a /usr/lib/speech_tools/lib/libestools.a /usr/lib/m68k-linux-gnu/libestools.a This affects all architectures, not just the one given. -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: m68k Kernel: Linux 3.2.0-4-atari Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/mksh-static --- End Message --- --- Begin Message --- Source: festival Source-Version: 1:2.1~release-5.1 We believe that the bug you reported is fixed in the latest version of festival, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 696...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated festival package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 06 Jan 2013 00:50:19 +0100 Source: festival Binary: festival festival-dev Architecture: source amd64 Version: 1:2.1~release-5.1 Distribution: unstable Urgency: low Maintainer: Jean-Philippe MENGUAL Changed-By: gregor herrmann Description: festival - General multi-lingual speech synthesis system festival-dev - Development kit for the Festival speech synthesis system Closes: 696507 Changes: festival (1:2.1~release-5.1) unstable; urgency=low . * Non-maintainer upload. * Fix "FTBFS: does not define DEB_HOST_MULTIARCH": set and export DEB_HOST_MULTIARCH in debian/rules, thanks to Ivo De Decker for the solution. Build-depend on dpkg-dev (>= 1.16.0) to ensure DEB_HOST_MULTIARCH is available. (Closes: #696507) Checksums-Sha1: 13d26afa3361064811b064a38f6493c111ff6447 2243 festival_2.1~release-5.1.dsc b74253f6eead15a4217fb641cba45e884c074bc1 97438 festival_2.1~release-5.1.debian.tar.gz aa6475d0c28c86341afc962b16fac19b2f245809 1058564 festival_2.1~release-5.1_amd64.deb eaedc780f3b4fad56d3294f9b6aff12dc97c9f53 895922 festival-dev_2.1~release-5.1_amd64.deb Checksums-Sha256: 7239994acc06b5e36cea0f661c82b43305b0bb47c3c8536a9ab0e3ea1b7bb3a0 2243 festival_2.1~release-5.1.dsc b31ac5529249f9826839dc969924739bd89bd2fa6f22bc5628636df5cc510afe 97438 festival_2.1~release-5.1.debian.tar.gz ff3a1f462b48b3acef7b540cb436596962f8da26c1cbcb8abdd2cc0c8811878a 1058564 festival_2.1~release-5.1_amd64.deb 0523e7a81a2a38d9442786294f9703f6717aa20e56b134e4b14160466a939c5e 895922 festival-dev_2.1~release-5.1_amd64.deb Files: d0bdaf6d808b412214a34773f5c66e7a 2243 sound optional festival_2.1~release-5.1.dsc 5b900880d1a777b725022da5d6e59da8 97438
Bug#697465: apache2.2-common: initial install fails: Could not read /etc/apache2/envvars
On Mon, Jan 7, 2013 at 20:23:26 +0100, Jonas Smedegaard wrote: > Sorry if I was unclear earlier: I am talking about postinst too: > postinst calls a2ensite calls perl loads modules. > > Since those modules are not yet configured, postinst fails. > > Package needs to pre-depend on perl, not just depend on it. > No. What you describe sounds like a multistrap bug. Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!
Processing commands for cont...@bugs.debian.org: > retitle 681227 does not validate free-form input Bug #681227 [grub-installer] installation-reports: grub-install tries to install to a nonsense string Changed Bug title to 'does not validate free-form input' from 'installation-reports: grub-install tries to install to a nonsense string' > thanks Stopping processing here. Please contact me if you need assistance. -- 681227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#697617: jenkins: remote code execution vulnerability
Processing control commands: > retitle -1 jenkins: CVE-2013-0158: remote code execution vulnerability Bug #697617 [jenkins] jenkins: remote code execution vulnerability Changed Bug title to 'jenkins: CVE-2013-0158: remote code execution vulnerability' from 'jenkins: remote code execution vulnerability' -- 697617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697617: jenkins: remote code execution vulnerability
Control: retitle -1 jenkins: CVE-2013-0158: remote code execution vulnerability Hi On Tue, Jan 08, 2013 at 02:06:39AM +0900, Nobuhiro Ban wrote: > Package: jenkins > Version: 1.447.2+dfsg-2 > Severity: grave > Tags: security > > Dear Maintainer, > > The upstream vendor announced a security advisory, that is rated > critical severity. > > See: > https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04 CVE-2013-0158 was assigned to this issue. Please include the CVE when fixing this issue. Regards, Salvatore signature.asc Description: Digital signature
Bug#689332: bind9 uses shipped file as statefile
On Tue, Oct 16, 2012 at 04:24:05 -0400, Michael Gilbert wrote: > control: tag -1 patch > > Hi, I've attached a proposed patch that moves the state file to /var/lib. > I'm not sure that patch really fixes anything. Also it doesn't seem like the file is removed by any of the maintainer scripts on package removal, so if anything it'll make postrm fail to rmdir /var/lib/bind. Cheers, Julien signature.asc Description: Digital signature
Bug#697230: asterisk: Two security issues: AST-2012-014 / AST-2012-015
On Wed, Jan 02, 2013 at 10:56:43PM +0100, Salvatore Bonaccorso wrote: > Package: asterisk > Severity: grave > Tags: security > Justification: user security hole > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi, > > the following vulnerabilities were published for asterisk. > > CVE-2012-5976[0]: > Crashes due to large stack allocations when using TCP > > CVE-2012-5977[1]: > Denial of Service Through Exploitation of Device State Caching Both apply to th stable vrsion as well. I commited fixes to th SVN. Working on building them. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697186: Missing dependency on libcollection-dev
Hi
@Timo: Not to put any pressure or so. In case you are short of time I
can prepare a NMU for this and upload.
Regards,
Salvatore
diff -u ding-libs-0.1.3/debian/control ding-libs-0.1.3/debian/control
--- ding-libs-0.1.3/debian/control
+++ ding-libs-0.1.3/debian/control
@@ -113,7 +113,7 @@
Package: libini-config-dev
Section: libdevel
Architecture: any
-Depends: libini-config2 (= ${binary:Version}), ${misc:Depends}
+Depends: libini-config2 (= ${binary:Version}), libcollection-dev (=
${binary:Version}), ${misc:Depends}
Description: Development files for libini_config
Library to process config files in INI format into a libcollection data
structure. Development files.
diff -u ding-libs-0.1.3/debian/changelog ding-libs-0.1.3/debian/changelog
--- ding-libs-0.1.3/debian/changelog
+++ ding-libs-0.1.3/debian/changelog
@@ -1,3 +1,11 @@
+ding-libs (0.1.3-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add missing Depends on libcollection-dev for libini-config-dev.
+Thanks to Asbjørn Sloth Tønnesen (Closes: #697186)
+
+ -- Salvatore Bonaccorso Mon, 07 Jan 2013 21:41:36 +0100
+
ding-libs (0.1.3-1) unstable; urgency=low
* Initial release (Closes: #637594)
signature.asc
Description: Digital signature
Bug#696760: Reproduce
Daniel, Can you please kill nm-applet and run it from the console, and paste its output? (hopefully we'll see a meaningful error) Thanks Oren -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#694473: apache2: segmentation fault after reload, maybe PHP
This seems to be related, but it does not have a definite fix, either: https://bugs.php.net/bug.php?id=62129 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642750: epiphany-browser: *HIGHLY* unstable on ia64 (IA-64/IPF/Itanium) platform
Hi and happy new year, I've tested latest patchset from Stephan. Epiphany runs as great as with the v2 patchset. I'm however still getting the curious Google homepage crash I was talking about previously. Uninstalling gnash didn't help. But overall, Stephan work is a _huge_ improvement w.r.t. what we had before! Kudos to him. Best regards, Emeric 2013/1/2 Stephan Schreiber : > I filed bug#697172 for yet another bug of webkit. > Furthermore, bug#697173 for a bug in the epiphany-browser package. > Furthermore, bug#697174 in order to enable seed on ia64. > > I also realized that gnash seems to crash epiphany sometimes. I browsed > through the Debian bug reports and found ones which blame gnash to make the > webkit based browsers unstable - epiphany-bowser on Gnome and Konqueror on > KDE: > bug#594822, 655839, 549309. > I removed both gnash and gnash-common from my computer and realized a real > improvement of epiphany's behaviour. > > But I still experienced some trouble, for example, a reproducable hang-up > and a crash a few seconds subsequently: Enter www.kununu.de; enter a company > name in the top right search edit box; enter; click on a company's name - > hang-up, crash. > I tried Fedora 17 i386 on another box (epiphany-browser 3.4.3; webkit 1.8.3; > gnash isn't installed): same behaviour. It isn't an ia64 specific bug. > > I think epiphany-browser/webkit with all patches runs on ia64 as stable as > on x86; this is the best we can do at the moment. > > > A summary of the patches we had so far: > > webkit, this bug report > 01-ia64-wide-ptr.patch > 02-ia64-use-system-malloc.patch > > webkit, bug#694971 > large-mem-page.patch > > webkit, bug#697172 > thread-safe-icon-db.patch > > seed, bug#582774 > seed no longer FTBFS without any change > > epiphany-browser, bug#697173 > history-thread-startup-race.patch > > epiphany-browser, bug#697174 > enabling seed in debian/rules > > > If you want to test it, you can download the built debs: > > http://www.fs-driver.org/debian-ia64/webkitgtk-debs-v3.tar > http://www.fs-driver.org/debian-ia64/seed-debs.tar > http://www.fs-driver.org/debian-ia64/epiphany-debs.tar > > Remember to remove both gnash and gnash-common before you test it. > > Stephan > > -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683584: security update ready for squeeze (3.1.8)
On lun., 2013-01-07 at 09:11 +0100, Daniel Pocock wrote: > On 07/01/13 07:27, Yves-Alexis Perez wrote: > > On lun., 2013-01-07 at 00:35 +0100, Daniel Pocock wrote: > > > >> Yes, the 3.1.8 security fix from upstream has been packaged and has > >> been waiting for security team to process through to the archive > >> > > Can you elaborate on that? > > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683584#25 > > was done before I became a DD, so although I could upload the fix into > git.debian.org, I did not have any access to upload any binary package > > Has somebody built and uploaded to the archive already? As it is for > current stable branch, can I upload myself or does the security team > take care of the upload? Please provide a debdiff against stable. -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#696424: Possible patch
Hi David On Mon, Jan 07, 2013 at 09:06:53AM +, David Weber wrote: > > Attached is the debdiff contianing these three refreshed for the > > version in unstable and testing. But I'm not yet ready to propose a > > NMU. Testing of the resulting package is welcome! > > Thanks for the debdiff! > > It works as expected: It creates the files with the right > permissions without breaking functionality. > > A problem could be that the files aren't freshly created by a simple > restart of the daemon. Should something be done about that? > > Some options could be: > - Notify the user to stop libvirtd and sanlock and run > rm /var/run/sanlock/sanlock.sock; rm /var/log/sanlock.log > > - Change the file permissions through the package update > > - Do nothing because most likely nobody uses sanlock on Debain atm. I have not a final answer here, but it might be easy to implement like libvirt-bin does in postint, mabye only conditionally checking (so doing it during package update from a 'broken' version): [...] if ! dpkg-statoverride --list "/var/log/sanlock.log" >/dev/null 2>&1; then # fix permissions fi [...] and the same for /var/run/sanlock/sanlock.sock. Regards, Salvatore signature.asc Description: Digital signature
Bug#696483: Fix for CVE-2012-5657
Hi, i have prepared a package for squeeze: http://debian.lordlamer.de/zendframework/1.10.6squeeze1/zendframework_1.10.6-1squeeze2.dsc I also tested it and fixes the problem. I will contact security team now. regards, Frank signature.asc Description: This is a digitally signed message part.
Bug#671690: is it still the case that libgamin0 makes courier non-functional
On Mon, 07 Jan 2013 20:50:19 +0100, Benny Baumann wrote: > I can confirm this. Haven't noticed any issues recently with the current > versions. That's great to hear, thanks for the confirmation! Cheers, gregor, leaving the pleasure to close the bug to Benny or Michael :) -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: The Dubliners: Louse house at Kilkenny signature.asc Description: Digital signature
Bug#697465: apache2.2-common: initial install fails: Could not read /etc/apache2/envvars
On Mon, 7 Jan 2013, Jonas Smedegaard wrote: Quoting Jean-Michel Vourgère (2013-01-07 16:58:08) On Sunday 06 January 2013 11:29:55 Arno Töll wrote: (...) Seems that error comes from a2ensite call, so I suspect the cause might be some dependency of that script has not yet been configured. a2ensite does not call a shell to read /etc/apache2/envvars. Your output makes me suspect this is rather coming from the init script which is invoked from postinst. What makes you think a2ensite is the problem? Arno: a2ensite reads /etc/apache2/envvars in function read_env_file on line 331: env - sh -c '. /etc/apache2/envvars && env' Thanks, Jean-Michel. Sorry if I was unclear earlier: I am talking about postinst too: postinst calls a2ensite calls perl loads modules. Since those modules are not yet configured, postinst fails. Are you sure? Perl modules usually don't need the package to be configured in order to be usable. An exception may be if ld.config needs to be called. And even so, according to policy 7.2, the dependencies *will* be configured when postinst is run: "In the case of `postinst configure', the depended-on packages will be unpacked and configured first. (If both packages are involved in a dependency loop, this might not work as expected; see the explanation a few paragraphs back.)" Clearly perl-modules is not in a dependency loop with apache2.2-common. Perl-modules is priority standard, apache2.2-common is optional. Package needs to pre-depend on perl, not just depend on it. Below test indicates that this bug is independent from that lack of predependency on perl - so do you guys want me to file a separate bug about the perl predependency? If you still think there is a bug, yes please. But include the exact error message. Jonas: What does the command line above yield? What is the result code ? ($?) What shell do you use? dash? (ls -l /bin/sh) Can you send us your envvars file? As I wrote before, it occurs using multistrap. Multistrap is like debootstrap but postpones all postinst calls till later. Therefore envvars file is the file shipped with the package itself. /etc/apache2/envvars is included in apache2.2-common. Therefore apache2.2-common may assume that it is present in postinst. + env - sh -c '. /etc/apache2/envvars && env' sh: 1: .: Can't open /etc/apache2/envvars + echo 2 2 + ls -l /bin/sh lrwxrwxrwx 1 root root 4 Jan 7 18:53 /bin/sh -> bash + cat /etc/apache2/envvars # envvars - default environment variables for apache2ctl This is rather weird. The shell can't source the file but immediately afterwards the "cat" succeeds. Does multistrap do things in parallel? Or do you do this on NFS or some other strange file system? Maybe you should run strace -f -tt on the whole multistrap process to see what is happening with respect to /etc/apache2/envvars. Another possible issue I could imagine (but your log does not really look like it): If removed apache2.2-common in your chroot without purging it, and then deleted /etc/apache2/* by hand. In this case dpkg will not re-create /etc/apache2/envvars during the next installation because it is a conffile.
Bug#671690: is it still the case that libgamin0 makes courier non-functional
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I can confirm this. Haven't noticed any issues recently with the current versions. Regards, BenBE. Am 07.01.2013 20:24, schrieb gregor herrmann: > On Tue, 01 Jan 2013 14:48:02 -0500, Yaroslav Halchenko wrote: > >> I haven't heard any bad report after 0.1.10-4.1 was uploaded... not sure >> about this specific issue, but I would vote just to consider it closed >> as well, unless there is an explicit confirmation that courier still >> experiences problems. >> FWIW -- I am also running courier-imap from squeeze (4.8.0-3) with >> libgamin0 0.1.10-4.1 -- and haven't had any problems > > FWIW: I've installed libgamin0 on a wheezy system last Friday and > haven't heard any user complaints yet. > > # dpkg -l courier* libgamin0 | grep ^ii > ii courier-authdaemon 0.63.0-6+b1 amd64 Courier authentication daemon > ii courier-authlib 0.63.0-6+b1 amd64 Courier authentication library > ii courier-authlib-userdb 0.63.0-6+b1 amd64 userdb support for the Courier authentication library > ii courier-base 0.68.2-1 amd64 Courier mail server - base system > ii courier-doc 0.68.2-1 all Courier mail server - additional documentation > ii courier-imap 4.10.0-20120615-1 amd64 Courier mail server - IMAP server > ii courier-imap-ssl 4.10.0-20120615-1 amd64 Courier mail server - IMAP over SSL > ii courier-pop 0.68.2-1 amd64 Courier mail server - POP3 server > ii courier-pop-ssl 0.68.2-1 amd64 Courier mail server - POP3 over SSL > ii courier-ssl 0.68.2-1 amd64 Courier mail server - SSL/TLS Support > ii libgamin0 0.1.10-4.1 amd64 Client library for the gamin file and directory monitoring system > > > So, closing this bug with 0.1.10-4.1 also sounds reasonable to me. > > > Cheers, > gregor > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJQ6yb6AAoJEPHTXLno4S6tOwMQAJujwMEkW/CRzHzqF83a6YvR xZ9C6NJiNJ5vgETSW9jg8IQ6m0VJ3GFOajcaqopmr67QvfF4BJkA+GgMRCYjkmJR +2JZ2+WtWgIWMqXDwvMqaiQwG4rBHCyl41TLFwsB80rQo6xQgCOk8zM5esg4KwxZ LvUecb4aHXlLSJuh5YgPfrIYQnx9Zo119I8nFeYHB5IIkyC8hWs1DtJn33VtqhYf mhsl9cxgPCQQC9bigsHAlzZe8A8cMrcUbXFgsy3bigGM7rOobkodA4wSJdu8Mp9y dC/2ZMohnrhuo+1FU5kKdwKsJ5wMJ2KPxPSNeBK+JpROl1Yps8Q7i42UEDgJ1rR9 sYvDILICdurz9VUROykgMxECqJwpmrOuVVzQ7cvK/OARB5adRDkCJaDCFssIfiR/ nAEXKTRpvXNQQwMsw0czKwJnVG+RIsfYH/xzY/k64rxurb9mAiXiP5Yz/2BeSpou 6YJybiJ633CjD/WM31+xmoDpNo6lX5daeVlDgTgxl9Vru4SUuAnMfVeDZwGhQiiR Fc7un+cmaq+qKKtAOpPJ5Bgcay1I+SHxZgl0ArXxmz368N5W1JKuC/OqWxokPZ6/ iJHeTd1c25jbEGEO0vYsLilnLS39lWGryNSxP0yT8MgpFg65P8DYdmZseHAEVZxA SKzWgNmrjJon5x3zylnH =c5ys -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!
retitle 681227 does not validate free-form input thanks On Mon, Jan 07, 2013 at 05:54:03PM +, Steven Chamberlain wrote: > Hi Matthew, > > On 07/01/13 17:15, Matthew Vernon wrote: > >>> Jul 10 16:48:43 in-target: grub-common is already the newest version. > >>> Jul 10 16:48:43 in-target: 0 upgraded, 0 newly installed, 0 to remove > >>> and 0 not upgraded. > >>> Jul 11 07:56:28 grub-installer: info: Installing grub on '/dev/sdb > >>> w33sxs34rfvbg789iokm·']' > > > On 02/01/13 22:49, Steven Chamberlain wrote: > >> To the original submitter of the bug report: do you have a cat? > > > > No. The machine is my work desktop. I do have a QWERTY keyboard > > [...] I don't know how one might > > have gotten a middot out of it! > > I've just learned that at least with my keyboard layout (gb), AltGr + > period will type the interpunct/middot, in Xorg or from a Linux > terminal. Those keys are more or less adjacent too. > > > That said, I cannot eliminate the > > possibility that a cleaner was overzealous or similar, but it seems > > unlikely...? > > I'm convinced this is the explanation. The installer was stuck at a > GRUB prompt for boot devices overnight; then at 07:56 (usually > 'accurate', but might not be in the local timezone) GRUB proceeded > trying to install to: > > w33 sxs 34rfvbg ... 789iokm ·'] > > This seems to fit with down/up sweeps across a QWERTY keyboard with > one's cleaning cloth, proceeding from the left to right (so I would even > guess that he/she is right-handed...). > > [The split on an ergo keyboard would be between the ...vbg and 789... > sequences of keystrokes, and the closing square bracket is adjacent to > the carriage return key]. > > So I think this can be closed. Almost. > What to do with the workaround added by Wouter in grub-installer/1.84? The workaround tried to eliminate the possibility of invalid data coming from "somewhere" in the installer. I hadn't noticed the long delay in the log; I had noticed the possibility of invalid input, but didn't think you'd be silly enough to enter such a long string and not notice. Of course, if the installer was running overnight, that changes matters. So what I think needs to be done to fix this properly is to move the check from where it is located right now to where we do the db_get for the installer device. If what's been entered by the user doesn't look like a hard disk device, we should display an error message and allow the user to try again. However, given we're this late in the freeze, and given that we've already got the workaround in place (which should allow a retry by going through the main menu), I'm not sure it's appropriate anymore to do this right now. I'll leave that decision to the d-i RM. > It did trigger a couple of regressions initially, but those are fixed > now in Git. > > Silently ignoring a failure seems risky when we know that it should not > happen. (Someone may want to specify multiple targets, and if one of > them is typo'd it would be silently skipped in this case). That's indeed the only case that isn't caught by the current code. Still, first, this is a highly unusual installation type; and second, even were it to occur, an easy workaround is to use the installer in rescue mode and fix the boot set-up -- or fix it from the installed system. Again, it's not a perfect situation, but I'm not sure this is RC anymore. -- Copyshops should do vouchers. So that next time some bureaucracy requires you to mail a form in triplicate, you can mail it just once, add a voucher, and save on postage. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697465: apache2.2-common: initial install fails: Could not read /etc/apache2/envvars
Quoting Jean-Michel Vourgère (2013-01-07 16:58:08)
> On Sunday 06 January 2013 11:29:55 Arno Töll wrote:
> > (...)
> > > Seems that error comes from a2ensite call, so I suspect the cause
> > > might be some dependency of that script has not yet been
> > > configured.
> >
> > a2ensite does not call a shell to read /etc/apache2/envvars. Your
> > output makes me suspect this is rather coming from the init script
> > which is invoked from postinst. What makes you think a2ensite is the
> > problem?
>
> Arno:
> a2ensite reads /etc/apache2/envvars in function read_env_file on line
> 331:
> env - sh -c '. /etc/apache2/envvars && env'
Thanks, Jean-Michel.
Sorry if I was unclear earlier: I am talking about postinst too:
postinst calls a2ensite calls perl loads modules.
Since those modules are not yet configured, postinst fails.
Package needs to pre-depend on perl, not just depend on it.
Below test indicates that this bug is independent from that lack of
predependency on perl - so do you guys want me to file a separate bug
about the perl predependency?
> Jonas:
> What does the command line above yield?
> What is the result code ? ($?)
> What shell do you use? dash? (ls -l /bin/sh)
> Can you send us your envvars file?
As I wrote before, it occurs using multistrap. Multistrap is like
debootstrap but postpones all postinst calls till later. Therefore
envvars file is the file shipped with the package itself.
Also, I tried manually switching sh to use bash, but that caused
exact same failure.
Attached is the exact commands I used myself, and below is excerpt of
output when I (after failure of attached script) add the following near
the top of /var/lib/dpkg/info/apache2.2-common.postinst inside the
chroot:
set +e
set -x
env - sh -c '. /etc/apache2/envvars && env'
echo $?
ls -l /bin/sh
cat /etc/apache2/envvars
set -e
...and then re-run make (which calls all postinst scripts again):
+ env - sh -c '. /etc/apache2/envvars && env'
sh: 1: .: Can't open /etc/apache2/envvars
+ echo 2
2
+ ls -l /bin/sh
lrwxrwxrwx 1 root root 4 Jan 7 18:53 /bin/sh -> bash
+ cat /etc/apache2/envvars
# envvars - default environment variables for apache2ctl
# this won't be correct after changing uid
unset HOME
# for supporting multiple apache2 instances
if [ "${APACHE_CONFDIR##/etc/apache2-}" != "${APACHE_CONFDIR}" ] ; then
SUFFIX="-${APACHE_CONFDIR##/etc/apache2-}"
else
SUFFIX=
fi
# Since there is no sane way to get the parsed apache2 config in scripts, some
# settings are defined via environment variables and then used in apache2ctl,
# /etc/init.d/apache2, /etc/logrotate.d/apache2, etc.
export APACHE_RUN_USER=www-data
export APACHE_RUN_GROUP=www-data
export APACHE_PID_FILE=/var/run/apache2$SUFFIX.pid
export APACHE_RUN_DIR=/var/run/apache2$SUFFIX
export APACHE_LOCK_DIR=/var/lock/apache2$SUFFIX
# Only /var/log/apache2 is handled by /etc/logrotate.d/apache2.
export APACHE_LOG_DIR=/var/log/apache2$SUFFIX
## The locale used by some modules like mod_dav
export LANG=C
## Uncomment the following line to use the system default locale instead:
#. /etc/default/locale
export LANG
## The command to get the status for 'apache2ctl status'.
## Some packages providing 'www-browser' need '--dump' instead of '-dump'.
#export APACHE_LYNX='www-browser -dump'
## If you need a higher file descriptor limit, uncomment and adjust the
## following line (default is 8192):
#APACHE_ULIMIT_MAX_FILES='ulimit -n 65536'
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
#!/bin/sh
set -e
# This script works with normal user, except installing needed packages
#sudo aptitude install git fai-client multistrap fakechroot
# Setup boxer
git clone git://git.debian.org/git/collab-maint/boxer.git
cd boxer
git submodule update --init
# Enable a few classes, use local proxy, and explicitly set target suite
bin/boxerenclass ipv4ll webchat
echo "source = http://proxy:/debian"; > config.mk
echo "suite = wheezy" >> config.mk
# Create system
make
# Install system onto /media/boxer (formattet but not mounted device)
make install
signature.asc
Description: signature
Bug#671690: is it still the case that libgamin0 makes courier non-functional
On Tue, 01 Jan 2013 14:48:02 -0500, Yaroslav Halchenko wrote: > I haven't heard any bad report after 0.1.10-4.1 was uploaded... not sure > about this specific issue, but I would vote just to consider it closed > as well, unless there is an explicit confirmation that courier still > experiences problems. > FWIW -- I am also running courier-imap from squeeze (4.8.0-3) with > libgamin0 0.1.10-4.1 -- and haven't had any problems FWIW: I've installed libgamin0 on a wheezy system last Friday and haven't heard any user complaints yet. # dpkg -l courier* libgamin0 | grep ^ii ii courier-authdaemon 0.63.0-6+b1 amd64Courier authentication daemon ii courier-authlib0.63.0-6+b1 amd64Courier authentication library ii courier-authlib-userdb 0.63.0-6+b1 amd64userdb support for the Courier authentication library ii courier-base 0.68.2-1 amd64Courier mail server - base system ii courier-doc0.68.2-1 all Courier mail server - additional documentation ii courier-imap 4.10.0-20120615-1 amd64Courier mail server - IMAP server ii courier-imap-ssl 4.10.0-20120615-1 amd64Courier mail server - IMAP over SSL ii courier-pop0.68.2-1 amd64Courier mail server - POP3 server ii courier-pop-ssl0.68.2-1 amd64Courier mail server - POP3 over SSL ii courier-ssl0.68.2-1 amd64Courier mail server - SSL/TLS Support ii libgamin0 0.1.10-4.1 amd64Client library for the gamin file and directory monitoring system So, closing this bug with 0.1.10-4.1 also sounds reasonable to me. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Wir sind Helden: Endlich ein Grund zur Panik signature.asc Description: Digital signature
Processed: tagging 684817
Processing commands for cont...@bugs.debian.org: > # debdiff and RT ACK in 696608 > tags 684817 + pending Bug #684817 [src:lilypond] segfault in lilypond Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 684817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697221: marked as done (motion: No longer has support for mysql)
Your message dated Mon, 07 Jan 2013 19:02:36 +
with message-id
and subject line Bug#697221: fixed in motion 3.2.12-3.3
has caused the Debian Bug report #697221,
regarding motion: No longer has support for mysql
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
697221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: motion
Version: 3.2.12-3.2
Severity: serious
Justification: 4
Dear Maintainer,
* What led up to the situation?
upgrade from squeeze to wheezy
* What exactly did you do (or not do) that was effective (or
ineffective)?
no longer connects to mysql
reports unknown config option mysql_*
Jan 2 19:42:42 hagrid motion: [0] Unknown config option "mysql_host"
Jan 2 19:42:42 hagrid motion: [0] Unknown config option "mysql_db"
Jan 2 19:42:42 hagrid motion: [0] Unknown config option "mysql_user"
Jan 2 19:42:42 hagrid motion: [0] Unknown config option "mysql_password"
ldd doesn't include mysql libs
ldd /usr/bin/motion | grep -i sql
All indicates it's not built with mysql support.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages motion depends on:
ii adduser3.113+nmu3
ii debconf [debconf-2.0] 1.5.48
ii libavcodec53 6:0.8.4-1
ii libavformat53 6:0.8.4-1
ii libavutil516:0.8.4-1
ii libc6 2.13-37
ii libjpeg8 8d-1
ii libpq5 9.1.7-1
Versions of packages motion recommends:
ii ffmpeg 6:0.8.4-1
Versions of packages motion suggests:
ii mysql-client 5.5.28+dfsg-1
ii mysql-client-5.5 [mysql-client] 5.5.28+dfsg-1
pn postgresql-client
-- Configuration Files:
/etc/default/motion changed:
start_motion_daemon=yes
/etc/init.d/motion changed:
NAME=motion
PATH_BIN=/bin:/usr/bin:/sbin:/usr/sbin
DAEMON=/usr/bin/motion
PIDFILE=/var/run/$NAME.pid
DEFAULTS=/etc/default/$NAME
DESC="motion detection daemon"
ENV="env -i LANG=C PATH=$PATH_BIN"
. /lib/lsb/init-functions
test -x $DAEMON || exit 0
RET=0
[ -r "$DEFAULTS" ] && . "$DEFAULTS" || start_motion_daemon=yes
check_daemon_enabled () {
if [ "$start_motion_daemon" = "yes" ] ; then
return 0
else
log_warning_msg "Not starting $NAME daemon, disabled via
/etc/default/$NAME"
return 1
fi
}
case "$1" in
start)
if check_daemon_enabled ; then
log_daemon_msg "Starting $DESC" "$NAME"
if start-stop-daemon --start --oknodo --exec $DAEMON -b --chuid motion ; then
log_end_msg 0
else
log_end_msg 1
RET=1
fi
fi
;;
stop)
log_daemon_msg "Stopping $DESC" "$NAME"
if start-stop-daemon --stop --oknodo --exec $DAEMON --retry 30 ; then
log_end_msg 0
else
log_end_msg 1
RET=1
fi
;;
reload|force-reload)
log_daemon_msg "Reloading $NAME configuration"
if start-stop-daemon --stop --signal HUP --exec $DAEMON ; then
log_end_msg 0
else
log_end_msg 1
RET=1
fi
;;
restart-motion)
if check_daemon_enabled ; then
log_action_begin_msg "Restarting $NAME"
if $0 stop && $0 start ; then
log_action_end_msg 0
else
log_action_cont_msg "(failed)"
RET=1
fi
fi
;;
restart)
$0 restart-motion
;;
*)
echo "Usage: /etc/init.d/$NAME {start|stop|restart|reload}"
RET=1
;;
esac
exit $RET
/etc/motion/motion.conf changed:
daemon on
quiet on
text_right %d-%b-%y\n%H:%M:%S
target_dir /var/motion
output_normal off
low_cpu 2
post_capture 10
control_html_output on
control_port 8084
control_localhost on # only localhost can access
snapshot_filename %u.%a.%b%d/cam%t/s%Y%m%d%H%M%S-%v
jpeg_filename %u.%a.%b%d/cam%t/p%H%M%S-%q-%v
on_movie_end /etc/motion/offsiteit %f
sql_log_mpeg on
sql_query insert into security(camera, filename, frame, file_type, time_stamp,
event_time_stamp) values('%t', '%f', '%q', '%n', '%Y-%m-%d %T', '%C')
mysql_host localhost
mysql_db motion
mysql_user web
mysql_password web
webcam_quality 80
webcam_maxrate 10
webcam_motion on
thread /etc/motion/cam-elm.conf
thread /etc/motion/cam-ash.conf
thread /etc/motion/cam-oak.conf
thread /etc/motion/cam-larch.conf
/etc/motion/thread1.conf [Errno 2] No such file or directory:
u'/etc/motion/thread1
Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed
On 01/07/2013 07:48 PM, gregor herrmann wrote: On Sat, 15 Dec 2012 16:13:35 +0100, Joost Yervante Damad wrote: I tried rebuilding the bsaf software in wheezy with default-jdk, which uses the openjdk from openjdk-6-jre-headless_6b24. It builds just fine. Is this really still an issue? It still fails to build for me in wheezy and sid chroots - without my earlier patch because of "Can't connect to X11 window server using ':0' as the value of the DISPLAY variable." - with the patch with the long java.beans stack trace I guess you had DISPLAY unset during the build and the problematic tests were skipped? Indeed, I did not have DISPLAY set. Unfortunately I forgot to keep a log of the build around. Joost -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed
On Sat, 15 Dec 2012 16:13:35 +0100, Joost Yervante Damad wrote: > I tried rebuilding the bsaf software in wheezy with default-jdk, > which uses the openjdk from openjdk-6-jre-headless_6b24. > It builds just fine. > Is this really still an issue? It still fails to build for me in wheezy and sid chroots - without my earlier patch because of "Can't connect to X11 window server using ':0' as the value of the DISPLAY variable." - with the patch with the long java.beans stack trace I guess you had DISPLAY unset during the build and the problematic tests were skipped? Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: The Chieftains: The Parting of Friends-Kerry Fling signature.asc Description: Digital signature
Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!
Hi Matthew, On 07/01/13 17:15, Matthew Vernon wrote: >>> Jul 10 16:48:43 in-target: grub-common is already the newest version. >>> Jul 10 16:48:43 in-target: 0 upgraded, 0 newly installed, 0 to remove >>> and 0 not upgraded. >>> Jul 11 07:56:28 grub-installer: info: Installing grub on '/dev/sdb >>> w33sxs34rfvbg789iokm·']' > On 02/01/13 22:49, Steven Chamberlain wrote: >> To the original submitter of the bug report: do you have a cat? > > No. The machine is my work desktop. I do have a QWERTY keyboard > [...] I don't know how one might > have gotten a middot out of it! I've just learned that at least with my keyboard layout (gb), AltGr + period will type the interpunct/middot, in Xorg or from a Linux terminal. Those keys are more or less adjacent too. > That said, I cannot eliminate the > possibility that a cleaner was overzealous or similar, but it seems > unlikely...? I'm convinced this is the explanation. The installer was stuck at a GRUB prompt for boot devices overnight; then at 07:56 (usually 'accurate', but might not be in the local timezone) GRUB proceeded trying to install to: w33 sxs 34rfvbg ... 789iokm ·'] This seems to fit with down/up sweeps across a QWERTY keyboard with one's cleaning cloth, proceeding from the left to right (so I would even guess that he/she is right-handed...). [The split on an ergo keyboard would be between the ...vbg and 789... sequences of keystrokes, and the closing square bracket is adjacent to the carriage return key]. So I think this can be closed. What to do with the workaround added by Wouter in grub-installer/1.84? It did trigger a couple of regressions initially, but those are fixed now in Git. Silently ignoring a failure seems risky when we know that it should not happen. (Someone may want to specify multiple targets, and if one of them is typo'd it would be silently skipped in this case). So I think it might be best to revert it? Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697251: gnupg2: gnupg key import memory corruption
* Thijs Kinkhorst (th...@debian.org) wrote: > On Sun, January 6, 2013 06:38, Eric Dorland wrote: > > Gah. I went out of town for Saturday and Sunday. I meant to upload before > > I left today but forgot. I just tried to now but I can't seem to reach my > > main Debian machine. So I won't be able to upload before Sunday night > > Eastern USA time. So if anyone wants to build it from the diff and upload > > feel free. > > Doing so now. Much appreciated. -- Eric Dorland ICQ: #61138586, Jabber: ho...@jabber.com signature.asc Description: Digital signature
Bug#671483: icedove: crashes on startup with failed assertion
--- On Thu, 13/12/12, Carsten Schoenert wrote: > what version do you really use? > stable, stable-security, stable-bpo? I'm using stable. > If your error still exits and/or you are not willing to upgrade to a > version higher than stable or stable-security please provide a GDB log. I've attached a GDB log with backtrace. Tim Chadburn GNU DDD 3.3.12 (i486-pc-linux-gnu), by Dorothea Lütkehaus and Andreas Zeller. Copyright © 1995-1999 Technische Universität Braunschweig, Germany. Copyright © 1999-2001 Universität Passau, Germany. Copyright © 2001 Universität des Saarlandes, Germany. Copyright © 2001-2004 Free Software Foundation, Inc. Reading symbols from /usr/lib/icedove/icedove-bin...Reading symbols from /usr/lib/debug/usr/lib/icedove/icedove-bin...done. (no debugging symbols found)...done. (gdb) run [Thread debugging using libthread_db enabled] [New Thread 0xb61e8b70 (LWP 6103)] [New Thread 0xb5974b70 (LWP 6104)] [New Thread 0xb4e1cb70 (LWP 6105)] [New Thread 0xb39d3b70 (LWP 6106)] [New Thread 0xb30c8b70 (LWP 6107)] [New Thread 0xb25ffb70 (LWP 6108)] [New Thread 0xb1bffb70 (LWP 6109)] [New Thread 0xb13feb70 (LWP 6110)] [New Thread 0xb09ffb70 (LWP 6111)] [Thread 0xb30c8b70 (LWP 6107) exited] [Thread 0xb39d3b70 (LWP 6106) exited] [Thread 0xb1bffb70 (LWP 6109) exited] [Thread 0xb09ffb70 (LWP 6111) exited] [New Thread 0xb30c8b70 (LWP 6112)] [New Thread 0xb39d3b70 (LWP 6113)] [New Thread 0xb1bffb70 (LWP 6114)] [Thread 0xb13feb70 (LWP 6110) exited] [Thread 0xb1bffb70 (LWP 6114) exited] [Thread 0xb30c8b70 (LWP 6112) exited] [New Thread 0xb13feb70 (LWP 6115)] [New Thread 0xb1bffb70 (LWP 6116)] [New Thread 0xb30c8b70 (LWP 6117)] [New Thread 0xb09ffb70 (LWP 6118)] [New Thread 0xab0ffb70 (LWP 6119)] [New Thread 0xaa8feb70 (LWP 6120)] [Thread 0xb39d3b70 (LWP 6113) exited] [New Thread 0xa9effb70 (LWP 6121)] [Thread 0xa9effb70 (LWP 6121) exited] icedove-bin: gconv.c:75: __gconv: Assertion `outbuf != ((void *)0) && *outbuf != ((void *)0)' failed. Program received signal SIGABRT, Aborted. 0xb7fe2424 in __kernel_vsyscall () (gdb) thread apply all bt Thread 19 (Thread 0xaa8feb70 (LWP 6120)): #0 0xb7fe2424 in __kernel_vsyscall () #1 0xb7ee04d2 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179 #2 0xb7d7814e in ?? () from /usr/lib/libnspr4.so.0d #3 0xb7d78f36 in PR_WaitCondVar () from /usr/lib/libnspr4.so.0d #4 0xb7d79037 in PR_Wait () from /usr/lib/libnspr4.so.0d #5 0xb7f952bc in nsAutoMonitor::Wait (this=0x50eb0591) at ../../dist/include/xpcom/nsAutoLock.h:340 #6 nsThreadPool::Run (this=0x50eb0591) at nsThreadPool.cpp:210 #7 0xb7f93653 in nsThread::ProcessNextEvent (this=0xab15add0, mayWait=1, result=0xaa8fe2ac) at nsThread.cpp:521 #8 0xb7f637d6 in NS_ProcessNextEvent_P (thread=0xfdfc, mayWait=1) at nsThreadUtils.cpp:247 #9 0xb7f93d55 in nsThread::ThreadFunc (arg=0xab15add0) at nsThread.cpp:254 #10 0xb7d7f394 in ?? () from /usr/lib/libnspr4.so.0d #11 0xb7edb955 in start_thread (arg=0xaa8feb70) at pthread_create.c:300 #12 0xb7e5b1de in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 18 (Thread 0xab0ffb70 (LWP 6119)): #0 0xb7fe2424 in __kernel_vsyscall () #1 0xb7ee04d2 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179 #2 0xb7d7814e in ?? () from /usr/lib/libnspr4.so.0d #3 0xb7d78f36 in PR_WaitCondVar () from /usr/lib/libnspr4.so.0d #4 0xb622c4d9 in nsHostResolver::GetHostToLookup (this=0x50eb0680, result=0xb658c160) at nsHostResolver.cpp:773 #5 0xb622cde6 in nsHostResolver::ThreadFunc (arg=0xb6523900) at nsHostResolver.cpp:877 #6 0xb7d7f394 in ?? () from /usr/lib/libnspr4.so.0d #7 0xb7edb955 in start_thread (arg=0xab0ffb70) at pthread_create.c:300 #8 0xb7e5b1de in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 17 (Thread 0xb09ffb70 (LWP 6118)): #0 0xb7fe2424 in __kernel_vsyscall () #1 0xb7edffcf in __pthread_cond_wait (cond=0xa9f4a604, mutex=0xa9f33274) at pthread_cond_wait.c:153 #2 0xb7d78fc9 in PR_WaitCondVar () from /usr/lib/libnspr4.so.0d #3 0xb7d79037 in PR_Wait () from /usr/lib/libnspr4.so.0d #4 0xb7f928af in nsAutoMonitor::Wait (this=0xab347ea0, mayWait=1, result=0xb09fe9d8) at ../../dist/include/xpcom/nsAutoLock.h:340 #5 nsEventQueue::GetEvent (this=0xab347ea0, mayWait=1, result=0xb09fe9d8) at nsEventQueue.cpp:85 #6 0xb7f9362b in nsThread::nsChainedEventQueue::GetEvent (this=0xab886d30, mayWait=1, result=0xb09fea1c) at nsThread.h:112 #7 nsThread::ProcessNextEvent (this=0xab886d30, mayWait=1, result=0xb09fea1c) at nsThread.cpp:512 #8 0xb7f637d6 in NS_ProcessNextEvent_P (thread=0xfe00, mayWait=1) at nsThreadUtils.cpp:247 #9 0xb7f987fd in nsProxyEventObject::CallMethod (this=0xab3e4500, methodIndex=, methodInfo=0xb2761088, params=0xb09feac4) at nsProxyEventObject.cpp:260 #10 0xb7fa0b8d in PrepareAndDispatch (methodIndex=, self=, args=) at xptcstubs_gcc_x86_unix.cpp:95 #11 0xb6429d2
Bug#697619: USB keyboard no longer works at initramfs passphrase prompt
Package: src:linux Version: 3.7.1-1~experimental.1 Severity: grave The 3.7 kernel in experimental no longer accepts input from a USB keyboard at the initramfs passphrase prompt for an encrypted root. This works fine with the 3.6 kernel currently in latest unstable, which I booted to make this report. Reporting this as grave because it breaks a common configuration supported by the installer (the vast majority of desktop systems have USB keyboards, and the installer offers encrypted root filesystems). - Josh Triplett -- Package-specific info: ** Model information sys_vendor: LENOVO product_name: 42915J0 product_version: ThinkPad X220 chassis_vendor: LENOVO chassis_version: Not Available bios_vendor: LENOVO bios_version: 8DET47WW (1.17 ) board_vendor: LENOVO board_name: 42915J0 board_version: Not Available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) Subsystem: Lenovo Device [17aa:21da] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: i915 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) Subsystem: Lenovo Device [17aa:21da] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) Subsystem: Lenovo Device [17aa:21ce] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) (prog-if 20 [EHCI]) Subsystem: Lenovo Device [17aa:21da] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ehci_hcd 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04) Subsystem: Lenovo Device [17aa:21da] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4) (prog-if 00 [Normal decode]) Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 [8086:1c18] (rev b4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGA
Bug#689332: marked as done (bind9: postinst uses shipped file /usr/share/bind9/bind9-default.md5sum as statefile)
Your message dated Mon, 07 Jan 2013 17:18:02 + with message-id and subject line Bug#689332: fixed in bind9 1:9.8.4.dfsg.P1-2 has caused the Debian Bug report #689332, regarding bind9: postinst uses shipped file /usr/share/bind9/bind9-default.md5sum as statefile to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 689332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bind9 Version: 1:9.7.3.dfsg-1~squeeze7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies a shipped file in /usr. /usr/share/bind9/bind9-default.md5sum is used by the postinst to store the md5sum of /etc/default/bind9. This file will be overwritten on upgrades, so the state information is lost before it can be reused by the postinst of the upgraded version. Shouldn't some state information better be kept in /var? Setting a high severity for this bug since I don't fully understand the configuration process and the possible implications of this problem. >From the attached logfile: 0m14.9s ERROR: FAIL: debsums reports modifications inside the chroot: /usr/share/bind9/bind9-default.md5sum Andreas bind9_1:9.7.3.dfsg-1~squeeze7.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: bind9 Source-Version: 1:9.8.4.dfsg.P1-2 We believe that the bug you reported is fixed in the latest version of bind9, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 689...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. LaMont Jones (supplier of updated bind9 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 07 Jan 2013 06:50:25 -0700 Source: bind9 Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-80 libdns88 libisc84 liblwres80 libisccc80 libisccfg82 dnsutils lwresd Architecture: all amd64 i386 source Version: 1:9.8.4.dfsg.P1-2 Distribution: unstable Urgency: low Maintainer: LaMont Jones Changed-By: LaMont Jones Closes: 689332 692416 697352 Description: bind9-doc - Documentation for BIND bind9-host - Version of 'host' bundled with BIND 9.X bind9 - Internet Domain Name Server bind9utils - Utilities for BIND dnsutils - Clients provided with BIND host - Transitional package libbind9-80 - BIND9 Shared Library used by BIND libbind-dev - Static Libraries and Headers used by BIND libdns88 - DNS Shared Library used by BIND libisc84 - ISC Shared Library used by BIND libisccc80 - Command Channel Library used by BIND libisccfg82 - Config File Handling Library used by BIND liblwres80 - Lightweight Resolver Library used by BIND lwresd - Lightweight Resolver Daemon Changes: bind9 (1:9.8.4.dfsg.P1-2) unstable; urgency=low . [Michael Gilbert] . * Use /var/lib/bind for state file. Closes: #689332 . [LaMont Jones] . * Re-enable dlopen, do not build the test that fails. Closes: #692416 * Update db.root with new IP for D.root-servers.net. Closes: #697352 Checksums-Sha1: fd0e464cbd8494c70254ac7629175e9881c52210 364964 bind9_9.8.4.dfsg.P1-2_amd64.deb 0a2753da5b28d072fa69d698eaa40197ed3dc57f 123802 bind9utils_9.8.4.dfsg.P1-2_amd64.deb dc790731a26c8490b3f707bf3445b4d24e73d88c 72714 bind9-host_9.8.4.dfsg.P1-2_amd64.deb 020433cc817394ad45baba0b1506bfcba1033425 1561252 libbind-dev_9.8.4.dfsg.P1-2_amd64.deb 9687eb6f77a65885e3bef4a816ba5d75865fed13 41480 libbind9-80_9.8.4.dfsg.P1-2_amd64.deb 328b7a1e78e2515931ceb882a605c1fc98f6696d 737210 libdns88_9.8.4.dfsg.P1-2_amd64.deb 8941faa540e87b7bea63ac1fc74a0ced3389c8cc 181668 libisc84_9.8.4.dfsg.P1-2_amd64.deb 84e03dfde3320eaa0948f993d06a48772fe07c15 54396 liblwres80_9.8.4.dfsg.P1-2_amd64.deb afcf043db80597fa0c5cdda9feb7b8ff8a1b946c 35116 libisccc80_9.8.4.dfsg.P1-2_amd64.deb 24b693765aaf927e772c2218aca6d420198ef3a8 61618 libisccfg82_9.8.4.dfsg.P1-2_amd64.deb d1737936dedbae6c1fce6ff90bc0cda3798308b0 165806 dnsutils_9.8.4.dfsg.P1-2_amd64.deb d9643c2230c697342253509cf5383159e614c576 247298 lwresd_9.8.4.dfsg.P1-2_amd64.deb 8191d93b1b725fa8bdd51b510
Bug#681227: Can anyone reproduce #681227: installation-reports: grub-install tries to install to a nonsense string?!
Hi, Sorry, I don't think this email's going to help very much. On 02/01/13 22:49, Steven Chamberlain wrote: Hi! On 02/01/13 20:26, Cyril Brulebois wrote: Jul 10 16:48:43 in-target: grub-common is already the newest version. Jul 10 16:48:43 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Jul 11 07:56:28 grub-installer: info: Installing grub on '/dev/sdb w33sxs34rfvbg789iokm·']' Notice the long delay there. I suspect the installer paused at `db_get grub-installer/bootdev`, which according to grub-installer.templates for v1.70 was of 'string' type: Template: grub-installer/bootdev Type: string The device should be specified as a device in /dev. Below are some examples: So I imagined typing that 'nonsense' string on a keyboard: w33... sxs... 34rfvbg... 789iokm... and a middot which I'm not sure how you would type, and finally ... ']... enter key? On a QWERTY keyboard these sequences of keys are all adjacent! To the original submitter of the bug report: do you have a cat? No. The machine is my work desktop. I do have a QWERTY keyboard (Microsoft Natural Ergonomic Keyboard 4000). I don't know how one might have gotten a middot out of it! That said, I cannot eliminate the possibility that a cleaner was overzealous or similar, but it seems unlikely...? Regards, Matthew -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697617: jenkins: remote code execution vulnerability
Package: jenkins Version: 1.447.2+dfsg-2 Severity: grave Tags: security Dear Maintainer, The upstream vendor announced a security advisory, that is rated critical severity. See: https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04 Regards, Nobuhiro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697465: apache2.2-common: initial install fails: Could not read /etc/apache2/envvars
On 07.01.2013 16:58, Jean-Michel Vourgère wrote: > Arno: > a2ensite reads /etc/apache2/envvars in function read_env_file on line 331: > env - sh -c '. /etc/apache2/envvars && env' I could have sworn I removed that code and replaced it by pure Perl. Sorry for the confusion. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Processed: policy has patience and so should you
Processing commands for cont...@bugs.debian.org: > severity 697613 important Bug #697613 [minidlna] Please add logrotate rules Severity set to 'important' from 'serious' > #policy has patience and so should you > #it also fits the defition of important quite well > thanks Stopping processing here. Please contact me if you need assistance. -- 697613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697613: policy has patience and so should you
severity 697613 important #policy has patience and so should you #it also fits the defition of important quite well thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#694473: apache2: segmentation fault after reload, maybe PHP
Hi. On Sun, Dec 23, 2012 at 04:09:48PM +0100, Stefan Fritsch wrote: > > It always happens after there has been an graceful reload (i.e. > /etc/init.d/apache2 reload), so it will break after every logrotate (therefore > bumping severity). > FWIW, I think #691318 is probably a duplicate of #694473, as I can reproduce systematically a crash in an apache subprocess when editing a mediawiki page right after a reload. However, I've been unable to produce core dumps (see my previous message to #691318) to confirm for sure. In any case, thanks for the hint. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#694473: Bug#691318: debian #691318 - please supply backtrace
On Tue, Dec 25, 2012 at 07:55:24PM +0200, Lior Kaplan wrote: > Hi Guys, > > Please supply a backtrace as part of bug #691318. See > http://wiki.debian.org/HowToGetABacktrace for more details. > > We can't really guess what is the problem without some hints. > Unfortunately, I can't :-( I've tried producing core dumps, but cannot succeed. I'm using mpm-prefork, and it seems that no cores will be produced for the child processes, although the master process (the one owned by root) dumps cores on signal 11 perfectly. Maybe it's because the reproduction scenario involves an apache2 reload (yes, it seems very similar to #694473 : trying to post an edit to a wiki page after an /etc/init.d/apache2 reload has happened). Are there any more instructions that what's in /usr/share/doc/apache2-mpm-prefork/README.backtrace on how to make sure apache's sub processes can dump cores ? Thanks in advance. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697465: apache2.2-common: initial install fails: Could not read /etc/apache2/envvars
On Sunday 06 January 2013 11:29:55 Arno Töll wrote: > (...) > > Seems that error comes from a2ensite call, so I suspect the cause might > > be some dependency of that script has not yet been configured. > > a2ensite does not call a shell to read /etc/apache2/envvars. Your output > makes me suspect this is rather coming from the init script which is > invoked from postinst. What makes you think a2ensite is the problem? Arno: a2ensite reads /etc/apache2/envvars in function read_env_file on line 331: env - sh -c '. /etc/apache2/envvars && env' Jonas: What does the command line above yield? What is the result code ? ($?) What shell do you use? dash? (ls -l /bin/sh) Can you send us your envvars file? signature.asc Description: This is a digitally signed message part.
Bug#697613: Please add logrotate rules
Package: minidlna Version: 1.0.24+dfsg-1 Severity: serious 10.8 Log files "Log files must be rotated occasionally" You should follow this policy rule. PS If you could not make an upload now, feel free to ask me for NMU. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (680, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages minidlna depends on: ii adduser3.113+nmu3 ii libavformat53 7:0.10.3-dmo1 ii libavutil517:1.0.1-dmo1 ii libc6 2.13-37 ii libexif12 0.6.20-3 ii libflac8 1.2.1-6 ii libid3tag0 0.15.1b-10 ii libjpeg8 8d-1 ii libogg01.3.0-4 ii libsqlite3-0 3.7.13-1 ii libvorbis0a1.3.2-1.3 ii lsb-base 4.1+Debian8 minidlna recommends no packages. minidlna suggests no packages. -- Configuration Files: /etc/minidlna.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697604: Templates/Icons is not found
Package: fastqc
Version: 0.10.1+dfsg-1
Severity: grave
Non-interactive fastqc always fails with
java.lang.NullPointerException
at
uk.ac.babraham.FastQC.Report.HTMLReportArchive.startDocument(HTMLReportArchive.java:170)
at
uk.ac.babraham.FastQC.Report.HTMLReportArchive.(HTMLReportArchive.java:60)
at
uk.ac.babraham.FastQC.Analysis.OfflineRunner.analysisComplete(OfflineRunner.java:157)
at
uk.ac.babraham.FastQC.Analysis.AnalysisRunner.run(AnalysisRunner.java:108)
at java.lang.Thread.run(Thread.java:679)
It's this line:
File templatesDir = new
File(URLDecoder.decode(ClassLoader.getSystemResource("Templates/Icons").getFile(),"UTF-8"));
So it tries to find /usr/share/fastqc/Templates/Icons and don't succeed.
I tried various things to add /usr/share/fastqc to CLASSPATH in
/usr/bin/fastqc but it's not enough.
I downloaded upstream FastQC and there was no such problem. The only
difference that I see is that in Debian a fastqc.jar is used while in
upstream it's unpacked in the root directory. My conclusion is that this
specific way with getSystemResource searches only the location where
main class resides. In Debian's case it's fastqc.jar and in upstream
it's FastQC directory.
The easiest solution is to include all /usr/share/fastqc/* in the jar
file. (Well, you could not use jar file at all but I don't think it's a
good idea.)
Regards,
Ognyan Kulev
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#696837: [patch]
deluged has the dependency. The deluge-common package should have it instead. libtorrent.patch Description: Binary data
Bug#694908: Redistribution of Evidence codes inside EMBOSS suite packaged for Debian
Hello Michelle, I'm writing you on the behalf of the Debian Med team which has included the EMBOSS suite into official Debian distribution. The EMBOSS suite does contain some files of the Evidence codes ontology and the site http://www.obofoundry.org/cgi-bin/detail.cgi?id=evidence_code lists you as contact. So I hope is fine to contact you. Please note that I have put the according bug tracker e-mail to this mail which makes this mail publicly available. While we would finally need a public statement please make sure you drop this CC in case you prefer that your response is not publicly readable. By packaging the EMBOSS suite the Debian operating system is currently redistributing some files from Evidence codes ontology indirectly, which incorporates some Evidence codes ontology files since its version 6.4 (http://packages.debian.org/wheezy/emboss). Debian considers copyrights and licenses very seriously, and our system only contains Free software, that is, materials that our users can freely use, modify and redistribute themselves. In addition to our system, we have a "non-free" archive in which, as a convenience for our users, we redistribute works that give less freedoms to our users. In order to evaluate if works containing Evidence codes ontology files can at least be distributed in our "non-free" area, I would like to know if Evidence codes ontology is available under other terms of use or licenses, that allow redistributing Evidence codes ontology files. You might even like to follow the Gene Ontology Consortium that has put its database under a Creative Commons BY (Attribution 3.0 Unported) license[1]. Kind regards and thanks for providing Evidence codes Andreas. [1] https://www.ebi.ac.uk/panda/jira/browse/GOHELP-147 -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#694908: Contains non-free data
Hi, just to keep you updated and have a record what happened. I asked for a login for ChEBI issue tracker. Because it seems to take some time I injected into the form at https://www.ebi.ac.uk/chebi/emailChebiForward.do under my debian.org address the following text: --- Hello, I'm writing you on the behalf of the Debian Med team which has included the EMBOSS suite into official Debian distribution. I found on the page https://www.ebi.ac.uk/chebi/aboutChebiForward.do the statement that the database is free. However, I have not found an explicit right to redistribute the data. The Debian operating system is currently redistributing some files from ChEBI indirectly, as we redistribute the EMBOSS package, which incorporates some ChEBI files since its version 6.4 (http://packages.debian.org/wheezy/emboss). Debian considers copyrights and licenses very seriously, and our system only contains Free software, that is, materials that our users can freely use, modify and redistribute themselves. In addition to our system, we have a "non-free" archive in which, as a convenience for our users, we redistribute works that give less freedoms to our users. In order to evaluate if works containing ChEBI files can at least be distributed in our "non-free" area, I would like to know if ChEBI is available under other terms of use or licenses, that allow redistributing ChEBI files. Please note: If you might like to apply a more detailed license including redistribution statement it would be great if you could post this in public to the Debian Med mailing list . Kind regards and thanks for providing ChEBI Andreas. --- Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697588: marked as done (Breaks python-parted)
Your message dated Mon, 07 Jan 2013 12:48:36 + with message-id and subject line Bug#697588: fixed in parted 2.3-12 has caused the Debian Bug report #697588, regarding Breaks python-parted to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 697588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libparted0debian1 Version: 2.3-11.1 Severity: grave After updating libparted0debian1 python-parted stops working.. With libparted0debian1 2.3-11 everyting is happy: $ python -c 'from parted import Device' $ after upgrading to 2.3-11.1: $ python -c 'from parted import Device' Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/parted/__init__.py", line 60, in from partition import Partition File "/usr/lib/python2.7/dist-packages/parted/partition.py", line 260, in partitionFlag[__flag] = _ped.partition_flag_get_name(__flag) ValueError: Invalid flag provided. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libparted0debian1 depends on: ii libblkid1 2.20.1-5.3 ii libc6 2.13-38 ii libdevmapper1.02.1 2:1.02.74-6 ii libuuid12.20.1-5.3 ii multiarch-support 2.13-38 libparted0debian1 recommends no packages. Versions of packages libparted0debian1 suggests: pn libparted0-dev pn libparted0-i18n ii parted 2.3-11 -- no debconf information --- End Message --- --- Begin Message --- Source: parted Source-Version: 2.3-12 We believe that the bug you reported is fixed in the latest version of parted, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 697...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated parted package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Jan 2013 12:13:14 + Source: parted Binary: parted parted-udeb libparted0 libparted0debian1 libparted0-udeb libparted0-i18n libparted0-dev libparted0debian1-dbg parted-doc Architecture: source i386 all Version: 2.3-12 Distribution: unstable Urgency: low Maintainer: Parted Maintainer Team Changed-By: Colin Watson Description: libparted0 - disk partition manipulator - dummy package libparted0-dev - disk partition manipulator - development files libparted0-i18n - disk partition manipulator - i18n support libparted0-udeb - disk partition manipulator - library udeb (udeb) libparted0debian1 - disk partition manipulator - shared library libparted0debian1-dbg - disk partition manipulator - debugging symbols parted - disk partition manipulator parted-doc - disk partition manipulator - documentation parted-udeb - Manually partition a hard drive (parted) (udeb) Closes: 697588 Changes: parted (2.3-12) unstable; urgency=low . * Breaks: python-parted (<< 3.6-5); previous versions were broken by the PED_PARTITION_LAST_FLAG change in 2.3-11.1 (closes: #697588). Checksums-Sha1: 9e58a7d05132c55cea5dfdc97e1b551bee77389d 2704 parted_2.3-12.dsc 28451a35aab28bda0135b26be138d8184b12292e 87695 parted_2.3-12.diff.gz 5123cbc939e223683a1f703c3976e13a4e65cd24 158708 parted_2.3-12_i386.deb 15573e69cce06f1b1773604575ffe09c0777947b 26352 parted-udeb_2.3-12_i386.udeb f734273a5034e5ecb90bceb97c70b26b9d7ad5e8 113844 libparted0_2.3-12_i386.deb fd8f5556daa94df065fd26688032597be162118b 329730 libparted0debian1_2.3-12_i386.deb 77154c33b6fa4ecc852f30bcdf745f5090d81e53 155112 libparted0-udeb_2.3-12_i386.udeb 47ca93cb2ecef57a61f94faf582ccdc6401cd841 401850 libparted0-dev_2.3-12_i386.deb a158f31ba3a5ea9eae583774692730045c61a2ee 1162748 libparted0debian1-dbg_2.3-12_i386.deb fa648f724a836acba662637cef024a92d2cc5d1b 580098 libparted0-i18n_2.3-12_all.deb ce745c7674d3d5909c59c4226c43fdf909847978 185776 parted-doc_2.3
Bug#697300: marked as done (src:user-mode-linux: missing Built-Using on linux (for linux-source-*))
Your message dated Mon, 07 Jan 2013 13:43:45 +0100 with message-id <50eac301.9070...@debian.org> and subject line Re: Bug#697300: src:user-mode-linux: missing Built-Using on linux (for linux-source-*) has caused the Debian Bug report #697300, regarding src:user-mode-linux: missing Built-Using on linux (for linux-source-*) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 697300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:user-mode-linux Version: 3.2-1um-1 Severity: serious Justification: Policy 7.8 Usertags: built-using user-mode-linux uses the Linux kernel source from linux-source-*, but does not indicate so with a Built-Using field (Policy 7.8). This means the archive might not contain the full source for this package as the specific version of linux used to build the package could be replaced with a newer version. See #696423 for a patch adding the Built-Using field to another package. It should be easy to apply to user-mode-linux as well. Ansgar --- End Message --- --- Begin Message --- Version: 3.2-2um-1 This was fixed in 3.2-2um-1, but it mentions the wrong bug number in the changelog entry: user-mode-linux (3.2-2um-1) unstable; urgency=high . * Add Built-Using per Policy §7.8 (Closes: #679300). Ansgar--- End Message ---
Processed: rep-gtk: diff for NMU version 1:0.90.0-2.2
Processing commands for cont...@bugs.debian.org: > tags 684443 + patch Bug #684443 [rep-gtk] rep-gtk: sawfish-ui requires gtk.la Added tag(s) patch. > tags 684443 + pending Bug #684443 [rep-gtk] rep-gtk: sawfish-ui requires gtk.la Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 684443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#684443: rep-gtk: diff for NMU version 1:0.90.0-2.2
tags 684443 + patch tags 684443 + pending thanks Dear maintainer, I've prepared an NMU for rep-gtk (versioned as 1:0.90.0-2.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, -- Colin Watson [cjwat...@debian.org] diff -Nru rep-gtk-0.90.0/debian/changelog rep-gtk-0.90.0/debian/changelog --- rep-gtk-0.90.0/debian/changelog 2012-06-22 10:51:17.0 +0100 +++ rep-gtk-0.90.0/debian/changelog 2013-01-07 10:10:22.0 + @@ -1,3 +1,10 @@ +rep-gtk (1:0.90.0-2.2) unstable; urgency=low + + * Non-maintainer upload. + * Restore .la files, but with dependency_libs emptied (closes: #684443). + + -- Colin Watson Mon, 07 Jan 2013 10:10:19 + + rep-gtk (1:0.90.0-2.1) unstable; urgency=low * Non-maintainer upload. diff -Nru rep-gtk-0.90.0/debian/rules rep-gtk-0.90.0/debian/rules --- rep-gtk-0.90.0/debian/rules 2012-06-22 10:58:51.0 +0100 +++ rep-gtk-0.90.0/debian/rules 2013-01-07 10:09:29.0 + @@ -55,7 +55,18 @@ dh_installdirs $(MAKE) install DESTDIR=`pwd`/debian/tmp - find debian/tmp/usr/lib -name '*.la' -delete + + #Fix libdir in *.la files + find debian/tmp -name '*.la' |\ + while read file; do\ + DIRNAME=$$(dirname $$file | sed 's@debian/tmp@@');\ + sed -i "/libdir/ s@^.*@libdir=$$DIRNAME@" $$file;\ + done + #... and remove dependency_libs + find debian/tmp -name '*.la' |\ + while read file; do\ + sed -i "/dependency_libs/ s/'.*'/''/" $$file;\ + done dh_install --list-missing touch install-stamp
Bug#697588: marked as done (Breaks python-parted)
Your message dated Mon, 07 Jan 2013 12:17:41 + with message-id and subject line Bug#697588: fixed in pyparted 3.6-5 has caused the Debian Bug report #697588, regarding Breaks python-parted to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 697588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libparted0debian1 Version: 2.3-11.1 Severity: grave After updating libparted0debian1 python-parted stops working.. With libparted0debian1 2.3-11 everyting is happy: $ python -c 'from parted import Device' $ after upgrading to 2.3-11.1: $ python -c 'from parted import Device' Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/parted/__init__.py", line 60, in from partition import Partition File "/usr/lib/python2.7/dist-packages/parted/partition.py", line 260, in partitionFlag[__flag] = _ped.partition_flag_get_name(__flag) ValueError: Invalid flag provided. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libparted0debian1 depends on: ii libblkid1 2.20.1-5.3 ii libc6 2.13-38 ii libdevmapper1.02.1 2:1.02.74-6 ii libuuid12.20.1-5.3 ii multiarch-support 2.13-38 libparted0debian1 recommends no packages. Versions of packages libparted0debian1 suggests: pn libparted0-dev pn libparted0-i18n ii parted 2.3-11 -- no debconf information --- End Message --- --- Begin Message --- Source: pyparted Source-Version: 3.6-5 We believe that the bug you reported is fixed in the latest version of pyparted, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 697...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated pyparted package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Jan 2013 11:53:42 + Source: pyparted Binary: python-parted python-parted-dbg Architecture: source i386 Version: 3.6-5 Distribution: unstable Urgency: low Maintainer: Parted Maintainer Team Changed-By: Colin Watson Description: python-parted - Python interface for libparted python-parted-dbg - Python interface for libparted - Debugging symbols Closes: 697588 Changes: pyparted (3.6-5) unstable; urgency=low . * debian/patches/no-last-flag-check.patch: - Remove explicit *_LAST_FLAG checks, which impose additional interface constraints not guaranteed by parted (closes: #697588). We'll still get parted exceptions for invalid flags, although they'll no longer be ValueError. * debian/control: - Add myself to Uploaders. Checksums-Sha1: a93905961e398eb23dbbb19889c421a8f309df81 2176 pyparted_3.6-5.dsc acf418b9c5193b5b5d7831934e3db3e94d78a5e7 4328 pyparted_3.6-5.debian.tar.gz bc06fae57647ef802ee03894d31a3044f5d49100 225170 python-parted_3.6-5_i386.deb 5665218a958772cb9431f540fafc9e7dc69b090e 515510 python-parted-dbg_3.6-5_i386.deb Checksums-Sha256: 11fee7fbda75756950c9f0a33739fa91af86fed4c417580bb7078fe5fb9bc08a 2176 pyparted_3.6-5.dsc db1ac4026eb5a6dbc696b06095b1019132b1f6696ea360c649dff72f51159308 4328 pyparted_3.6-5.debian.tar.gz 88fd8f5733632a8739e42b67b09c017a69080085be1cc166d8a01c02c9266b6c 225170 python-parted_3.6-5_i386.deb 842b89cac0c72dce96ad4d8736c1a93c188a48e11cd1b5221136525b30306a82 515510 python-parted-dbg_3.6-5_i386.deb Files: ebf43c892fb9ad66a8adad0304567ca8 2176 python optional pyparted_3.6-5.dsc 6bb8117e83d05d958b1a44304cd19daa 4328 python optional pyparted_3.6-5.debian.tar.gz c5313ce8a5f1ed6d0c9909f70b1be70c 225170 python optional python-parted_3.6-5_i386.deb c164dd67d296b078b5d38e50f3e9b1c9 515510 debug extra python-parted-dbg_3.6-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Colin Watson -
Processed: Bug#697588: Breaks python-parted
Processing commands for cont...@bugs.debian.org: > reassign 697588 pyparted Bug #697588 [libparted0debian1] Breaks python-parted Bug reassigned from package 'libparted0debian1' to 'pyparted'. No longer marked as found in versions parted/2.3-11.1. Ignoring request to alter fixed versions of bug #697588 to the same values previously set > affects 697588 libparted0debian1 Bug #697588 [pyparted] Breaks python-parted Added indication that 697588 affects libparted0debian1 > thanks Stopping processing here. Please contact me if you need assistance. -- 697588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697588: Breaks python-parted
reassign 697588 pyparted affects 697588 libparted0debian1 thanks On Mon, Jan 07, 2013 at 12:02:23PM +0100, Sebastian Ramacher wrote: > On 2013-01-07 11:24:07, Sjoerd Simons wrote: > > After updating libparted0debian1 python-parted stops working.. > > > > With libparted0debian1 2.3-11 everyting is happy: > > > > $ python -c 'from parted import Device' > > $ > > > > after upgrading to 2.3-11.1: > > > > $ python -c 'from parted import Device' > > Traceback (most recent call last): > > File "", line 1, in > > File "/usr/lib/python2.7/dist-packages/parted/__init__.py", line 60, in > > > > from partition import Partition > > File "/usr/lib/python2.7/dist-packages/parted/partition.py", line 260, in > > > > partitionFlag[__flag] = _ped.partition_flag_get_name(__flag) > > ValueError: Invalid flag provided. > > Rebuilding pyparted against parted 2.3-11.1 fixes that. > > According to codesearch.debian.net pyparted is the only package the > uses PED_PARTITION_LAST_FLAG, so it should be the only affected package. Mmm. Normally I'd say that this is parted's fault anyway because it broke ABI (and in an NMU, too ...), but really, this is not something python-parted should ever have been relying on. Although it's not written out explicitly, I can't really believe that a sensible person would have interpreted the existence of PED_PARTITION_LAST_FLAG after due thought as a promise that no further flags would ever be added; it's obviously just a "current final element in enumeration" #define for internal use. There's a similar problem with PED_DISK_LAST_FLAG too. I'll fix this in pyparted (since it's maintained by the parted maintainer team) and add a Breaks in libparted0debian1. Thanks, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697588: Breaks python-parted
On 2013-01-07 11:24:07, Sjoerd Simons wrote: > Package: libparted0debian1 > Version: 2.3-11.1 > Severity: grave > > After updating libparted0debian1 python-parted stops working.. > > With libparted0debian1 2.3-11 everyting is happy: > > $ python -c 'from parted import Device' > $ > > after upgrading to 2.3-11.1: > > $ python -c 'from parted import Device' > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python2.7/dist-packages/parted/__init__.py", line 60, in > > from partition import Partition > File "/usr/lib/python2.7/dist-packages/parted/partition.py", line 260, in > > partitionFlag[__flag] = _ped.partition_flag_get_name(__flag) > ValueError: Invalid flag provided. Rebuilding pyparted against parted 2.3-11.1 fixes that. According to codesearch.debian.net pyparted is the only package the uses PED_PARTITION_LAST_FLAG, so it should be the only affected package. Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#697588: Breaks python-parted
Package: libparted0debian1 Version: 2.3-11.1 Severity: grave After updating libparted0debian1 python-parted stops working.. With libparted0debian1 2.3-11 everyting is happy: $ python -c 'from parted import Device' $ after upgrading to 2.3-11.1: $ python -c 'from parted import Device' Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/parted/__init__.py", line 60, in from partition import Partition File "/usr/lib/python2.7/dist-packages/parted/partition.py", line 260, in partitionFlag[__flag] = _ped.partition_flag_get_name(__flag) ValueError: Invalid flag provided. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libparted0debian1 depends on: ii libblkid1 2.20.1-5.3 ii libc6 2.13-38 ii libdevmapper1.02.1 2:1.02.74-6 ii libuuid12.20.1-5.3 ii multiarch-support 2.13-38 libparted0debian1 recommends no packages. Versions of packages libparted0debian1 suggests: pn libparted0-dev pn libparted0-i18n ii parted 2.3-11 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686502: pxz produces archives broken for busybox's unxz
On Sun, 2013-01-06 at 23:32 +0100, Bastian Blank wrote:
> On Thu, Dec 27, 2012 at 10:08:07PM +0100, Abou Al Montacir wrote:
> > + if (r == XZ_STREAM_END) {
> > + /* Eat padding. Stream never starts with zeros, and
> > padding is 32 aligned */
> > + while ((iobuf.in_pos < iobuf.in_size) &&
> > (iobuf.in[iobuf.in_pos] == 0)) {
> > + iobuf.in_pos += 1;
> > + }
> > + /* Reached end of buffer. Fill it again from stream */
> > + if (iobuf.in_pos == iobuf.in_size) {
> > + continue;
> > + }
> > + if(iobuf.in_pos % 4){
>
> Are you sure this is correct? in_pos is the position in tht buffer, not
> the file. Also look out for coding style.
Provided the buffer size is multiple of 4 bytes, which is the case for
BUFSIZ. Of course one can decide to use a mis aligned buffer, but this
is not common and I consider it bad coding practice.
> > + if (r == XZ_STREAM_END) {
>
> Again the same check?
Not really, r could have been changed since the above check (r = XZ_DATA_ERROR;
when %4 check fails)
> > if (r == XZ_STREAM_END) {
> > - break;
> > + xz_dec_end(state);
> > + /* Look for any other streams */
> > + continue;
>
> Why do you have three XZ_STREAM_END checks in this state machine?
I use XZ_STREAM_END to check end of stream and eat padding, to check
there is still valid data (no paddding error) before initializing
decoder, and finally to free the decoder at en of current stream.
Cheers,
signature.asc
Description: This is a digitally signed message part
Bug#696424: Possible patch
> Attached is the debdiff contianing these three refreshed for the > version in unstable and testing. But I'm not yet ready to propose a > NMU. Testing of the resulting package is welcome! Thanks for the debdiff! It works as expected: It creates the files with the right permissions without breaking functionality. A problem could be that the files aren't freshly created by a simple restart of the daemon. Should something be done about that? Some options could be: - Notify the user to stop libvirtd and sanlock and run rm /var/run/sanlock/sanlock.sock; rm /var/log/sanlock.log - Change the file permissions through the package update - Do nothing because most likely nobody uses sanlock on Debain atm. Cheers, David sanlock_2.2-1.1.debdiff Description: Binary data
Bug#683584: security update ready for squeeze (3.1.8)
On 07/01/13 07:27, Yves-Alexis Perez wrote: > On lun., 2013-01-07 at 00:35 +0100, Daniel Pocock wrote: > >> Yes, the 3.1.8 security fix from upstream has been packaged and has >> been waiting for security team to process through to the archive >> > Can you elaborate on that? > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683584#25 was done before I became a DD, so although I could upload the fix into git.debian.org, I did not have any access to upload any binary package Has somebody built and uploaded to the archive already? As it is for current stable branch, can I upload myself or does the security team take care of the upload? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
