Bug#662752: secvpn, sudo: there should be a clean upgrade path from secvpn/squeeze to wheezy
Package: secvpn,sudo Version: secvpn/2.24 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, a clean upgrade path of secvpn from squeeze to wheezy is missing. secvpn/squeeze modifies /etc/sudoers, this has been fixed and is no longer done by the version in wheezy. But of course sudo can't be upgraded cleanly in this situation and prompts because of the modified conffile. I would suggest (as I already did in #660594) that sudo maintains a list of md5sums of old conffiles that were shipped in previous releases and upgrades to the new one if this is unmodified. Then we can add the md5sums of /etc/sudoers that was modified by secvpn (but otherwise the shipped version) to this list and upgrade cleanly as well. Eventually add a Breaks: secvpn (<< 2.24) to sudo as well. If you want, I can provide a patch for sudo. Andreas secvpn_2.24.log.gz Description: GNU Zip compressed data
Bug#662750: [Openstack-devel] Bug#662750: python-quantumclient and quantum-server: error when trying to install together
quantum-server/2012.1~e4-1 is on the NEW queue. As soon as it gets approved, i'll fix this. Thnx for the report. On Tue, Mar 6, 2012 at 8:31 AM, Ralf Treinen wrote: > Package: quantum-server,python-quantumclient > Version: quantum-server/2012.1~e3-1 > Version: python-quantumclient/2012.1~e4-1 > Severity: serious > User: trei...@debian.org > Usertags: edos-file-overwrite > > Date: 2012-03-06 > Architecture: amd64 > Distribution: sid > > Hi, > > automatic installation tests of packages that share a file and at the > same time do not conflict by their package dependency relationships has > detected the following problem: > > > WARNING: The following packages cannot be authenticated! > libexpat1 libdb4.8 mime-support python2.7-minimal python2.7 python-minimal > python openssl python-dns python-pkg-resources python-formencode > python-gflags python-paste python-pastedeploy quantum-common > openvswitch-common uuid-runtime openvswitch-switch > quantum-plugin-openvswitch quantum-server python-quantumclient > Authentication warning overridden. > Can not write log, openpty() failed (/dev/pts not mounted?) > Selecting previously unselected package libexpat1. > (Reading database ... 10547 files and directories currently installed.) > Unpacking libexpat1 (from .../libexpat1_2.0.1-7.2_amd64.deb) ... > Selecting previously unselected package libdb4.8. > Unpacking libdb4.8 (from .../libdb4.8_4.8.30-11_amd64.deb) ... > Selecting previously unselected package mime-support. > Unpacking mime-support (from .../mime-support_3.52-1_all.deb) ... > Selecting previously unselected package python2.7-minimal. > Unpacking python2.7-minimal (from .../python2.7-minimal_2.7.2-13_amd64.deb) > ... > Selecting previously unselected package python2.7. > Unpacking python2.7 (from .../python2.7_2.7.2-13_amd64.deb) ... > Selecting previously unselected package python-minimal. > Unpacking python-minimal (from .../python-minimal_2.7.2-10_all.deb) ... > Selecting previously unselected package python. > Unpacking python (from .../python_2.7.2-10_all.deb) ... > Selecting previously unselected package openssl. > Unpacking openssl (from .../openssl_1.0.0g-1_amd64.deb) ... > Selecting previously unselected package python-dns. > Unpacking python-dns (from .../python-dns_2.3.6-1_all.deb) ... > Selecting previously unselected package python-pkg-resources. > Unpacking python-pkg-resources (from > .../python-pkg-resources_0.6.24-1_all.deb) ... > Selecting previously unselected package python-formencode. > Unpacking python-formencode (from .../python-formencode_1.2.4-2_all.deb) ... > Selecting previously unselected package python-gflags. > Unpacking python-gflags (from .../python-gflags_1.5.1-1_all.deb) ... > Selecting previously unselected package python-paste. > Unpacking python-paste (from .../python-paste_1.7.5.1-4_all.deb) ... > Selecting previously unselected package python-pastedeploy. > Unpacking python-pastedeploy (from .../python-pastedeploy_1.5.0-2_all.deb) ... > Selecting previously unselected package quantum-common. > Unpacking quantum-common (from .../quantum-common_2012.1~e4-1_all.deb) ... > Selecting previously unselected package openvswitch-common. > Unpacking openvswitch-common (from .../openvswitch-common_1.4.0-2_amd64.deb) > ... > Selecting previously unselected package uuid-runtime. > Unpacking uuid-runtime (from .../uuid-runtime_2.20.1-4_amd64.deb) ... > Selecting previously unselected package openvswitch-switch. > Unpacking openvswitch-switch (from .../openvswitch-switch_1.4.0-2_amd64.deb) > ... > Selecting previously unselected package quantum-plugin-openvswitch. > Unpacking quantum-plugin-openvswitch (from > .../quantum-plugin-openvswitch_2012.1~e3-1_all.deb) ... > Selecting previously unselected package quantum-server. > Unpacking quantum-server (from .../quantum-server_2012.1~e3-1_all.deb) ... > Selecting previously unselected package python-quantumclient. > Unpacking python-quantumclient (from > .../python-quantumclient_2012.1~e4-1_all.deb) ... > dpkg: error processing > /var/cache/apt/archives/python-quantumclient_2012.1~e4-1_all.deb (--unpack): > trying to overwrite '/usr/share/pyshared/quantum/__init__.py', which is also > in package quantum-server 2012.1~e3-1 > configured to not write apport reports > Processing triggers for man-db ... > Errors were encountered while processing: > /var/cache/apt/archives/python-quantumclient_2012.1~e4-1_all.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > This is a serious bug as it makes installation fail, and violates > sections 7.6.1 and 10.1 of the policy. An optimal solution would > consist in only one of the packages installing that file, and renaming > or removing the file in the other package. Depending on the > circumstances you might also consider Replace relations or file > diversions. If the conflicting situation cannot be resolved then, as a > last resort, the two packages have to declare a mutual > Conflict. Please take into account that Repla
Bug#639300: please build against unixodbc-dev instead of libiodbc2-dev
Hi Sebastian, nice to meet you!
On Tue, Mar 06, 2012 at 01:34:45AM +0100, Pino Toscano wrote:
> Alle martedì 6 marzo 2012, Steve Langasek ha scritto:
> > I'm surprised to say that after sitting on this bug for far too long,
> > it turns out that it's trivial to fix. Although it had been
> > reported that soprano would not work with unixodbc, once I actually
> > installed virtuoso, which the soprano test suite silently depends
> > on, I get the same results from test/virtuosobackendtest when built
> > against either iODBC or UnixODBC.
> I remember Sebastian Trueg (main soprano upstream) strongly recommending
> against using unixODBC (e.g. in [2], just last September), so I'm not
> sure whether this switch would break anything in the semantic desktop
> stack.
> (Disclaimer: I don't use Nepomuk myself.)
> Sebastian, what is the current status of soprano wrt unixODBC/iODBC?
> Which problems would result in using unixODBC?
> [2] http://trueg.wordpress.com/2011/09/22/about-strigi-soprano-virtuoso-
> clucene-and-libstreamanalyzer/
Right, so I've read the comment in that blog entry about needing libiodbc
because of RDF extensions. But I've reviewed the libiodbc source, and can't
find any evidence that such extensions exist - there's a single RDF define
in the iodbcext.h header, but a copy of this header is shipped in the
soprano source and there are no uses of the define anyway. As best as I can
tell, the only extensions are in the virtuoso driver, which libiodbc2 merely
passes the requests through to - and unixodbc would appear to do the very
same.
The one thing I have found that's different between iODBC and UnixODBC (but
not represented in the previous patch) is that UnixODBC will not allow
look-up of a driver by filename alone; it requires that the filename match
the filename for a driver registered with odbcinst.ini. This seems like a
feature that we could patch into UnixODBC easily enough if needed. (And
apparently there was something wrong with my previous testing that I didn't
catch this.)
However, I wonder why it makes sense for soprano to use a driver manager at
all, given that it appears soprano can *only* use the virtuoso driver as a
backend. Wouldn't it be simpler to call into the virtuoso driver directly
and omit the driver manager, on Unix?
Attached is a revised patch to the Debian that implements the above
proposal. Since UnixODBC is no longer involved (except as a provider of the
sql.h header) there should not be any compatibility issues here. It may not
be portable to non-Linux systems, but maybe it would be an acceptable distro
patch, Pino?
> > I'm happy to upload this as an NMU if you would like. It's probably
> > worth an upload ASAP rather than waiting for 2.7.5+dfsg.1-1 to
> > migrate to testing, since it's hard to have usable ODBC drivers for
> > soprano until it's fixed.
> We're currently just started our KDE 4.7 transition, which includes also
> a soprano update from 2.6 to 2.7; if possible, I think IMHO it would be
> desiderable to wait for such dependency change, in case, after the
> transition is over (hopefully in two weeks, if everything goes fine).
> Would this timeframe suit you?
I think it makes perfect sense to not upload this change until we're
confident it's not going to be a problem for the transition.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru soprano-2.7.5+dfsg.1/debian/changelog soprano-2.7.5+dfsg.1/debian/changelog
--- soprano-2.7.5+dfsg.1/debian/changelog 2012-03-04 20:55:08.0 +
+++ soprano-2.7.5+dfsg.1/debian/changelog 2012-03-06 07:35:31.0 +
@@ -1,3 +1,10 @@
+soprano (2.7.5+dfsg.1-1.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Build without iODBC. Closes: #639300, LP: #901638.
+
+ -- Steve Langasek Mon, 05 Mar 2012 23:49:13 +
+
soprano (2.7.5+dfsg.1-1) unstable; urgency=low
* Team upload.
diff -Nru soprano-2.7.5+dfsg.1/debian/control soprano-2.7.5+dfsg.1/debian/control
--- soprano-2.7.5+dfsg.1/debian/control 2012-03-04 20:43:25.0 +
+++ soprano-2.7.5+dfsg.1/debian/control 2012-03-06 07:42:00.0 +
@@ -6,7 +6,7 @@
Build-Depends: debhelper (>= 7.4.15), cmake (>= 2.6.2), pkg-kde-tools (>= 0.12),
dpkg-dev (>= 1.15.5), libclucene-dev (>= 0.9.21b), libqt4-dev (>= 4.5.3),
libraptor1-dev (>= 1.4.16), librdf0-dev (>= 1.0.13),
- doxygen (>= 1.7.1), graphviz, libiodbc2-dev
+ doxygen (>= 1.7.1), graphviz, libvirtodbc0, unixodbc-dev
Standards-Version: 3.9.2
Homepage: http://soprano.sourceforge.net
Vcs-Browser: http://git.debian.org/?p=pkg-kde/kde-req/soprano.git
@@ -15,7 +15,7 @@
Package: soprano-daemon
Section: utils
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: libvirt
Bug#662747: Screen not locked on lid close when lid close action set to 'blank'.
tags 662747 + confirmed forwarded 662747 https://bugzilla.gnome.org/show_bug.cgi?id=671445 thanks On 06.03.2012 08:25, Josh Triplett wrote: > > Relevant settings: > org.gnome.settings-daemon.plugins.power lid-close-ac-action 'blank' > org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank' > org.gnome.desktop.screensaver lock-enabled true With those settings I'm able to reproduce the issue and I agree that blanking-on-lid-close should behave the same as blanking-on-idle-event (or suspend-on-lid-close, ftm) wrt to locking. Marking as confirmed and forwarded it upstream. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
debian-bugs-dist@lists.debian.org
Dear Matija, While I agree that Gnucash perhaps should have a better error handling and show an error dialog on unsuccessful import, I'd like to point out that what you described is invalid XML. Would you be able to reproduce the issue with recent Gnucash version 2.4.10? Thanks. Regards, Dmitry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662746: mingw32-ocaml: fails to upgrade from squeeze
Le 06/03/2012 08:18, Andreas Beckmann a écrit : > during a test with piuparts I noticed your package fails to upgrade from > 'squeeze'. > It installed fine in 'squeeze', then the upgrade to 'wheezy' fails. > [...] Precision: it fails when using apt, but it works using aptitude. Could you please explain the "serious" severity? Cheers, -- Stéphane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662725: cgal: CGAL 4.0 Beta 1 Released
Hi, this beta release has already been packaged. For now it can be obtained from deb http://www.joachim-reichel.de/debian/repository sid main deb-src http://www.joachim-reichel.de/debian/repository sid main Joachim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662118: Transcoding failed as well
>> Usually, this, is a problem with gstreamer. In order to sort that out, >> do you have the same result with the following command? >> >> $ gst-launch-0.10 filesrc location=2012-02-27-21-15-52-MVI_0796.MOV \ >> ! decodebin name=demux ! queue ! ffmpegcolorspace ! vp8enc \ >> ! webmmux name=mux ! filesink location=2012-02-27-21-15-52-MVI_0796.webm \ >> demux. ! queue ! audioconvert ! audioresample ! vorbisenc ! mux. > > I get: > WARNING: erroneous pipeline: no element "mux" Sorry, here is the correct command line : $ GST_DEBUG=*:2 gst-launch-0.10 filesrc location=2012-02-27-21-15-52-MVI_0796.MOV ! decodebin name=demux ! queue ! ffmpegcolorspace ! vp8enc ! webmmux name=mux ! filesink location=2012-02-27-21-15-52-MVI_0796.webm demux. ! queue ! audioconvert ! audioresample ! vorbisenc mux. Thanks, Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660418: Default dput.cf doesn't mention progress_indicator
# Bcc: control tags 493528 + wontfix thanks On 12/02/18 21:16 -0500, Ari Pollak said ... > The default /etc/dput.cf doesn't include anything about > progress_indicator. I would never have realized this is a configuration > option in dput.cf and not a commandline option, had it not been for > someone telling me about it. At the very least, putting it in the > example dput.cf (preferably defaulting to 2) should help future users. I suppose it is inappropriate to add progress_indicator = 2 unless all the upload methods can support it reliably, hence this is a wontfix. Giridhar -- Y Giridhar Appaji Nag | http://people.debian.org/~appaji/ signature.asc Description: Digital signature
Bug#645427: Processed: Still occurs with current GNOME 3 in sid
On Tue, Mar 06, 2012 at 08:02:15AM +0100, Michael Biebl wrote: > I'm inclined to close this bug, as it got horribly messed up due to the > merging and by having gone through different stages of GNOME 2 → 3.0 → > 3.2 where functionality got shifted around several times and the merged > bugs were actually different ones. Fair enough. > What's relevant for gnome 3.2 is gnome-settings-daemon > (gnome-power-manager is basically gone) > As already mentioned, gsd's power plugin is the one triggering the > screen blank on lid-close. > > I hope you don't mind filing a fresh report against gnome-settings-daemon > > The important settings here are > org.gnome.settings-daemon.plugins.power lid-close-ac-action 'blank' > org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank' > org.gnome.desktop.screensaver lock-enabled true > > bug title something like > screen is not locked on lid-close when lid-close action is 'blank' Bug filed as 662747. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662751: libterm-ttyrec-plus-perl and ttyrec: error when trying to install together
Package: ttyrec,libterm-ttyrec-plus-perl Version: ttyrec/1.0.8-5 Version: libterm-ttyrec-plus-perl/0.8-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-03-06 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libterm-ttyrec-plus-perl ttyrec Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libterm-ttyrec-plus-perl. (Reading database ... 10547 files and directories currently installed.) Unpacking libterm-ttyrec-plus-perl (from .../libterm-ttyrec-plus-perl_0.08-1_all.deb) ... Selecting previously unselected package ttyrec. Unpacking ttyrec (from .../ttyrec_1.0.8-5_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/ttyrec_1.0.8-5_amd64.deb (--unpack): trying to overwrite '/usr/bin/ttyplay', which is also in package libterm-ttyrec-plus-perl 0.08-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/ttyrec_1.0.8-5_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/ttyplay This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662750: python-quantumclient and quantum-server: error when trying to install together
Package: quantum-server,python-quantumclient Version: quantum-server/2012.1~e3-1 Version: python-quantumclient/2012.1~e4-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-03-06 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libexpat1 libdb4.8 mime-support python2.7-minimal python2.7 python-minimal python openssl python-dns python-pkg-resources python-formencode python-gflags python-paste python-pastedeploy quantum-common openvswitch-common uuid-runtime openvswitch-switch quantum-plugin-openvswitch quantum-server python-quantumclient Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libexpat1. (Reading database ... 10547 files and directories currently installed.) Unpacking libexpat1 (from .../libexpat1_2.0.1-7.2_amd64.deb) ... Selecting previously unselected package libdb4.8. Unpacking libdb4.8 (from .../libdb4.8_4.8.30-11_amd64.deb) ... Selecting previously unselected package mime-support. Unpacking mime-support (from .../mime-support_3.52-1_all.deb) ... Selecting previously unselected package python2.7-minimal. Unpacking python2.7-minimal (from .../python2.7-minimal_2.7.2-13_amd64.deb) ... Selecting previously unselected package python2.7. Unpacking python2.7 (from .../python2.7_2.7.2-13_amd64.deb) ... Selecting previously unselected package python-minimal. Unpacking python-minimal (from .../python-minimal_2.7.2-10_all.deb) ... Selecting previously unselected package python. Unpacking python (from .../python_2.7.2-10_all.deb) ... Selecting previously unselected package openssl. Unpacking openssl (from .../openssl_1.0.0g-1_amd64.deb) ... Selecting previously unselected package python-dns. Unpacking python-dns (from .../python-dns_2.3.6-1_all.deb) ... Selecting previously unselected package python-pkg-resources. Unpacking python-pkg-resources (from .../python-pkg-resources_0.6.24-1_all.deb) ... Selecting previously unselected package python-formencode. Unpacking python-formencode (from .../python-formencode_1.2.4-2_all.deb) ... Selecting previously unselected package python-gflags. Unpacking python-gflags (from .../python-gflags_1.5.1-1_all.deb) ... Selecting previously unselected package python-paste. Unpacking python-paste (from .../python-paste_1.7.5.1-4_all.deb) ... Selecting previously unselected package python-pastedeploy. Unpacking python-pastedeploy (from .../python-pastedeploy_1.5.0-2_all.deb) ... Selecting previously unselected package quantum-common. Unpacking quantum-common (from .../quantum-common_2012.1~e4-1_all.deb) ... Selecting previously unselected package openvswitch-common. Unpacking openvswitch-common (from .../openvswitch-common_1.4.0-2_amd64.deb) ... Selecting previously unselected package uuid-runtime. Unpacking uuid-runtime (from .../uuid-runtime_2.20.1-4_amd64.deb) ... Selecting previously unselected package openvswitch-switch. Unpacking openvswitch-switch (from .../openvswitch-switch_1.4.0-2_amd64.deb) ... Selecting previously unselected package quantum-plugin-openvswitch. Unpacking quantum-plugin-openvswitch (from .../quantum-plugin-openvswitch_2012.1~e3-1_all.deb) ... Selecting previously unselected package quantum-server. Unpacking quantum-server (from .../quantum-server_2012.1~e3-1_all.deb) ... Selecting previously unselected package python-quantumclient. Unpacking python-quantumclient (from .../python-quantumclient_2012.1~e4-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/python-quantumclient_2012.1~e4-1_all.deb (--unpack): trying to overwrite '/usr/share/pyshared/quantum/__init__.py', which is also in package quantum-server 2012.1~e3-1 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/python-quantumclient_2012.1~e4-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/python2.6/dist-packages/quantum/__init__.py /usr/lib/p
Bug#662749: libnetcdfc++5 and libnetcdfc++4: error when trying to install together
Package: libnetcdfc++4,libnetcdfc++5 Version: libnetcdfc++4/1:4.1.3-5 Version: libnetcdfc++5/1:4.1.3-4 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-03-06 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libkeyutils1 libkrb5support0 libk5crypto3 libkrb5-3 libgssapi-krb5-2 libsasl2-2 libldap-2.4-2 librtmp0 libssh2-1 libcurl3-gnutls libquadmath0 libgfortran3 libhdf5-7 libnetcdfc7 libnetcdfc++4 libnetcdfc++5 Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libkeyutils1. (Reading database ... 10547 files and directories currently installed.) Unpacking libkeyutils1 (from .../libkeyutils1_1.5.2-2_amd64.deb) ... Selecting previously unselected package libkrb5support0. Unpacking libkrb5support0 (from .../libkrb5support0_1.10+dfsg~beta1-2_amd64.deb) ... Selecting previously unselected package libk5crypto3. Unpacking libk5crypto3 (from .../libk5crypto3_1.10+dfsg~beta1-2_amd64.deb) ... Selecting previously unselected package libkrb5-3. Unpacking libkrb5-3 (from .../libkrb5-3_1.10+dfsg~beta1-2_amd64.deb) ... Selecting previously unselected package libgssapi-krb5-2. Unpacking libgssapi-krb5-2 (from .../libgssapi-krb5-2_1.10+dfsg~beta1-2_amd64.deb) ... Selecting previously unselected package libsasl2-2. Unpacking libsasl2-2 (from .../libsasl2-2_2.1.25.dfsg1-4_amd64.deb) ... Selecting previously unselected package libldap-2.4-2. Unpacking libldap-2.4-2 (from .../libldap-2.4-2_2.4.28-1.1_amd64.deb) ... Selecting previously unselected package librtmp0. Unpacking librtmp0 (from .../librtmp0_2.4+20111222.git4e06e21-1_amd64.deb) ... Selecting previously unselected package libssh2-1. Unpacking libssh2-1 (from .../libssh2-1_1.2.8-2_amd64.deb) ... Selecting previously unselected package libcurl3-gnutls. Unpacking libcurl3-gnutls (from .../libcurl3-gnutls_7.24.0-1_amd64.deb) ... Selecting previously unselected package libquadmath0. Unpacking libquadmath0 (from .../libquadmath0_4.6.3-1_amd64.deb) ... Selecting previously unselected package libgfortran3. Unpacking libgfortran3 (from .../libgfortran3_4.6.3-1_amd64.deb) ... Selecting previously unselected package libhdf5-7. Unpacking libhdf5-7 (from .../libhdf5-7_1.8.8-7.1_amd64.deb) ... Selecting previously unselected package libnetcdfc7. Unpacking libnetcdfc7 (from .../libnetcdfc7_1%3a4.1.3-5_amd64.deb) ... Selecting previously unselected package libnetcdfc++4. Unpacking libnetcdfc++4 (from .../libnetcdfc++4_1%3a4.1.3-5_amd64.deb) ... Selecting previously unselected package libnetcdfc++5. Unpacking libnetcdfc++5 (from .../libnetcdfc++5_1%3a4.1.3-4_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libnetcdfc++5_1%3a4.1.3-4_amd64.deb (--unpack): trying to overwrite '/usr/lib/libnetcdf_c++.so.4.1.0', which is also in package libnetcdfc++4 1:4.1.3-5 configured to not write apport reports Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libnetcdfc++5_1%3a4.1.3-4_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/libnetcdf_c++.so.4 /usr/lib/libnetcdf_c++.so.4.1.0 This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662748: highlight: fails to install, remove, distupgrade, and install again - prompting due to modified conffiles which where not modified by the user
Package: highlight Version: 3.7-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... During a test with piuparts I noticed your package failed to install (in 'squeeze'), remove (but not purge), distupgrade to 'wheezy', and install again. Before the second installation the package is in config-files-remaining state. The configuration is remaining from the last version that was successfully configured - which is from the previous release. This is a violation of policy 10.7.3, see http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens." http://wiki.debian.org/DpkgConffileHandling should help with figuring out how to do this properly. In http://lists.debian.org/debian-devel/2009/08/msg00675.html and followups it has been agreed that these bugs are to be filed with severity serious. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up highlight-common (3.7-2) ... Configuration file `/etc/highlight/filetypes.conf' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** filetypes.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing highlight-common (--configure): EOF on stdin at conffile prompt cheers, Andreas highlight_3.7-2.log.gz Description: GNU Zip compressed data
Bug#662735: okay
tag 662735 +confirmed retitle 662735 w3c-markup-validator: typo in repo URL thanks I'll fix it quickly. But what is wrong with "apt-get source w3c-markup-validator". Please don't try debcheckout w3c-sgml-lib. I know it is more thoroughly broken. -- Nicholas Bamber | http://www.periapt.co.uk/ PGP key 3BFFE73C from pgp.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662747: Screen not locked on lid close when lid close action set to 'blank'.
Package: gnome-settings-daemon
Version: 3.2.2-2
Severity: important
Tags: security
Relevant settings:
org.gnome.settings-daemon.plugins.power lid-close-ac-action 'blank'
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
org.gnome.desktop.screensaver lock-enabled true
With these settings, closing the laptop lid should blank the screen,
which should in turn lock the screen, such that reopening the
lid reveals an unlock dialog rather than the user's unsecured desktop.
However, this does not occur: closing the lid blanks the screen but does
not lock it, and reopening the lid gives access to the user's account.
By contrast, leaving the system idle until the screensaver kicks in
results in a properly locked screen.
I can reproduce this with a freshly created user account, just by
setting the first two keys above (lid-close-{ac,battery}-action);
lock-enabled already defaults to true.
Michael Biebl suggested that gnome-settings-daemon needed to emit a lock
signal as part of blanking, as it currently does when suspending.
Please let me know if you need any additional information.
Thanks,
Josh Triplett
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnome-settings-daemon depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3
ii dpkg 1.16.1.2
ii gsettings-desktop-schemas3.2.0-2
ii libatk1.0-0 2.2.0-2
ii libc62.13-27
ii libcairo-gobject21.10.2-6.2
ii libcairo21.10.2-6.2
ii libcanberra-gtk3-0 0.28-3
ii libcanberra0 0.28-3
ii libcolord1 0.1.16-2
ii libcomerr2 1.42.1-2
ii libcups2 1.5.2-6
ii libdbus-1-3 1.4.18-1
ii libdbus-glib-1-2 0.98-1
ii libfontconfig1 2.8.0-3.1
ii libfreetype6 2.4.8-1
ii libgconf2-4 3.2.3-3
ii libgcrypt11 1.5.0-3
ii libgdk-pixbuf2.0-0 2.24.1-1
ii libglib2.0-0 2.30.2-6
ii libgnome-desktop-3-2 3.2.1-3
ii libgnome2-common 2.32.1-2
ii libgnomekbd7 3.2.0-1
ii libgnutls26 2.12.16-1
ii libgssapi-krb5-2 1.10+dfsg~beta1-2
ii libgtk-3-0 3.2.3-1
ii libgudev-1.0-0 175-3.1
ii libk5crypto3 1.10+dfsg~beta1-2
ii libkrb5-31.10+dfsg~beta1-2
ii liblcms2-2 2.2+git20110628-2
ii libnotify4 0.7.4-1
ii libpackagekit-glib2-14 0.7.3-1
ii libpango1.0-01.29.4-2
ii libpolkit-gobject-1-00.104-2
ii libpulse-mainloop-glib0 1.1-3
ii libpulse01.1-3
ii libsqlite3-0 3.7.10-1
ii libupower-glib1 0.9.15-2
ii libx11-6 2:1.4.4-4
ii libxfixes3 1:5.0-4
ii libxi6 2:1.4.5-1
ii libxklavier165.2.1-1
ii nautilus-data3.2.1-2
ii zlib1g 1:1.2.6.dfsg-2
Versions of packages gnome-settings-daemon recommends:
ii hwdata
ii pulseaudio 1.1-3
Versions of packages gnome-settings-daemon suggests:
ii gnome-screensaver3.2.0-2+b1
ii metacity [x-window-manager] 1:2.34.1-2
ii x11-xserver-utils7.6+3
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662673: [Pkg-fonts-devel] Bug#662673: Bug#662673: Bug#662673: fonts-cantarell: Font files are installed twice
Am 05.03.2012 17:16, schrieb Fabian Greffrath: This is also fixed now. ... but still needs a sponsor. ;) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662738: frama-c: segfault when running frama-c-gui
Le 06/03/2012 07:00, Raphael Geissert a écrit : > The backtrace goes all the way to libQtGui.so.4 (I use the libqt4 gtk > engine) from the following: How to use the libqt4 gtk engine? Can you reproduce the bug with the standard gtk engine? (I cannot) Cheers, -- Stéphane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662746: mingw32-ocaml: fails to upgrade from squeeze
Package: mingw32-ocaml Version: 3.12.1+debian2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'squeeze'. It installed fine in 'squeeze', then the upgrade to 'wheezy' fails. >From the attached log (scroll to the bottom...): 1m0.4s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmpyXsfqY', 'apt-get', '-yf', 'dist-upgrade'] 1m39.8s DUMP: Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: cpp-4.6 gcc-4.6 gcc-4.6-base libdb5.1 libgmp10 liblzma5 libmount1 libmpc2 libpam-modules-bin libquadmath0 libsemanage-common libsemanage1 libtinfo-dev libtinfo5 libustr-1.0-1 mingw-w64-dev multiarch-support ucf The following packages have been kept back: mingw32-ocaml The following packages will be upgraded: apt base-files base-passwd bash binutils bsdutils coreutils cpp cpp-4.4 dash debconf debconf-i18n debianutils diffutils dpkg e2fslibs e2fsprogs findutils gcc gcc-4.4 gcc-4.4-base gnupg gpgv grep gzip hostname initscripts insserv libacl1 libattr1 libblkid1 libbz2-1.0 libc-bin libc-dev-bin libc6 libc6-dev libc6-i386 libcomerr2 libdb4.8 libfindlib-ocaml libfindlib-ocaml-dev libgcc1 libgdbm3 libgomp1 liblocale-gettext-perl libmpfr4 libncurses5 libncurses5-dev libpam-modules libpam-runtime libpam0g libreadline6 libselinux1 libsepol1 libslang2 libss2 libstdc++6 libtext-charwidth-perl libtext-iconv-perl libusb-0.1-4 libuuid1 linux-libc-dev login lsb-base mawk mingw32-binutils mount ncurses-base ncurses-bin ocaml-base-nox ocaml-findlib ocaml-interp ocaml-nox passwd perl-base readline-common sed sensible-utils sysv-rc sysvinit sysvinit-utils tar tzdata util-linux xz-utils zlib1g 86 upgraded, 18 newly installed, 0 to remove and 1 not upgraded. [...] 1m0.4s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmpyXsfqY', 'apt-get', '-yf', 'dist-upgrade'] 1m39.8s DUMP: Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: cpp-4.6 gcc-4.6 gcc-4.6-base libdb5.1 libgmp10 liblzma5 libmount1 libmpc2 libpam-modules-bin libquadmath0 libsemanage-common libsemanage1 libtinfo-dev libtinfo5 libustr-1.0-1 mingw-w64-dev multiarch-support ucf The following packages have been kept back: mingw32-ocaml The following packages will be upgraded: apt base-files base-passwd bash binutils bsdutils coreutils cpp cpp-4.4 dash debconf debconf-i18n debianutils diffutils dpkg e2fslibs e2fsprogs findutils gcc gcc-4.4 gcc-4.4-base gnupg gpgv grep gzip hostname initscripts insserv libacl1 libattr1 libblkid1 libbz2-1.0 libc-bin libc-dev-bin libc6 libc6-dev libc6-i386 libcomerr2 libdb4.8 libfindlib-ocaml libfindlib-ocaml-dev libgcc1 libgdbm3 libgomp1 liblocale-gettext-perl libmpfr4 libncurses5 libncurses5-dev libpam-modules libpam-runtime libpam0g libreadline6 libselinux1 libsepol1 libslang2 libss2 libstdc++6 libtext-charwidth-perl libtext-iconv-perl libusb-0.1-4 libuuid1 linux-libc-dev login lsb-base mawk mingw32-binutils mount ncurses-base ncurses-bin ocaml-base-nox ocaml-findlib ocaml-interp ocaml-nox passwd perl-base readline-common sed sensible-utils sysv-rc sysvinit sysvinit-utils tar tzdata util-linux xz-utils zlib1g 86 upgraded, 18 newly installed, 0 to remove and 1 not upgraded. [...] 1m40.5s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmpyXsfqY', 'apt-cache', 'policy', 'mingw32-ocaml'] 1m40.5s DUMP: mingw32-ocaml: Installed: 3.11.2+debian4 Candidate: 3.12.1+debian2 Version table: 3.12.1+debian2 0 500 http://piatti.debian.org/debian/ wheezy/main amd64 Packages *** 3.11.2+debian4 0 100 /var/lib/dpkg/status 1m40.5s DEBUG: Command ok: ['chroot', '/org/piuparts.debian.org/tmp/tmpyXsfqY', 'apt-cache', 'policy', 'mingw32-ocaml'] 1m40.5s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmpyXsfqY', 'apt-get', '-y', 'install', 'mingw32-ocaml'] 1m40.9s DUMP: Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mingw32-ocaml : Depends: mingw-ocaml but it is not going to be installed E: Broken packages cheers, Andreas mingw32-ocaml_3.12.1+debian2.log.gz Description: GNU Zip compressed data
Bug#662632: RFS: libaio-ocaml/1.0~rc1
Le 05/03/2012 12:33, Goswin von Brederlow a écrit :
> I am looking for a sponsor for my package "libaio-ocaml"
I've looked at the git repository (037a448). It is written explicitly in
[1]:
"Do not close RFS bugs in debian/changelog."
but the bug you refer to in debian/changelog is a RFS bug (CCed), not an
ITP bug. Please file a proper ITP bug and use it in debian/changelog.
Please use debhelper compat >= 8.
Please use [2] for debian/copyright.
You don't need to put the destination path in *.install(.in) files if it
is the same (relative to debian/tmp).
Your versioned dependencies are not enough: using ${ocaml:foo} variables
need dh-ocaml (>= 0.9) and ocaml-nox (>= 3.11.1-3~). But I guess just
not putting any version would be fine too.
"libaio-ocaml (= ${binary:Version})" should not be needed in
libaio-ocaml-dev's Depends field (thanks to ${ocaml:Depends}).
Please remove DMUA. Your key is not even in the keyring.
[1] http://wiki.debian.org/Mentors/BTS
[2] http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Cheers,
--
Stéphane
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662180: tuxcmd: Error while saving Configuration
Hi Salvatore, > Can you still reproduce this issue? I supsect a transient issue caused > due to the gconf2 update. Nope, I don't see the error anymore. So I guess your guess is right! -- Cheers, Thorsten -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662741: netcat-openbsd: does not receive a server's response unless -q sec is specified
You've mentioned that using -q it works well, this helped me a lot! I
think I have found the solution now.
1087if (qflag == 0) {
1088shutdown(nfd, SHUT_WR);
1089close(wfd);
1090exit(0);
1091}
The call of exit() should be removed.
--
Regards,
Aron Xu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662743: Initscript ignores ipset rules
Package: iptables-persistent
Version: 0.5.3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is the patches.
First is code itself, second is changelog entry.
- -- System Information:
Debian Release: 6.0.4
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (1, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages iptables-persistent depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii iptables1.4.8-3 administration tools for packet fi
ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
iptables-persistent recommends no packages.
iptables-persistent suggests no packages.
- -- Configuration Files:
/etc/init.d/iptables-persistent changed [not included]
- -- debconf information excluded
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJPVbdYAAoJENfRweM8/RmzfEYH/0/QBSXNnxjR/hSLuyJWa/bl
mchSn6NS4hn/NIRTQtox23FE1ejLkyYQNVGuFm4DjpSY/Tfz23j6xxKn8ahf55G0
rMeHT5HTweDTOyDscokK/IFnB13o5D1YahPQ0G+y3XlicKHe8tM2czwW/b8sOAP4
o+n/CALrQydnnbl/YATOMfgUsZCxDuLNn/kVq2LUbdGlmDNewbHF57BTDG2MlLO6
S5jBKE65aPaVxkrwFxK6Uz0cHVINEGXS/0J5s7QorluobOXajyWhsed1/xgBk3m6
YXTkJL9ohlEX/95l7YLSYSwV2J3SBfMtozu2ZtLrfkUFQ8Uo7081pjjdN7euMXo=
=eT7u
-END PGP SIGNATURE-
>From b5f9844ecaec6c4dea719e5a6f4f3a0a7f9c9018 Mon Sep 17 00:00:00 2001
From: Max Tsepkov
Date: Tue, 6 Mar 2012 12:39:49 +0600
Subject: [PATCH 1/2] save ipset rules
Closes #662743
---
debian/iptables-persistent.init | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/debian/iptables-persistent.init b/debian/iptables-persistent.init
index a03ee51..0725628 100644
--- a/debian/iptables-persistent.init
+++ b/debian/iptables-persistent.init
@@ -21,6 +21,11 @@ rc=0
load_rules()
{
+ #ipset
+ if which ipset >/dev/null && [ -r /etc/iptables/ipset ]; then
+ ipset restore < /etc/iptables/ipset
+ fi
+
log_action_begin_msg "Loading iptables rules"
#load IPv4 rules
@@ -50,6 +55,11 @@ load_rules()
save_rules()
{
+ #ipset
+ if which ipset >/dev/null ; then
+ ipset save > /etc/iptables/ipset
+ fi
+
log_action_begin_msg "Saving rules"
#save IPv4 rules
@@ -119,6 +129,11 @@ flush_rules()
done
fi
+ if which ipset >/dev/null ; then
+ ipset flush
+ ipset destroy
+ fi
+
log_action_end_msg 0
}
--
1.7.2.5
>From c3e6dc7b63d1f93869891cd8171b9ca2237a66a9 Mon Sep 17 00:00:00 2001
From: Max Tsepkov
Date: Tue, 6 Mar 2012 12:57:00 +0600
Subject: [PATCH 2/2] changelog entry for previous commit
---
debian/changelog |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 60db469..002ba8e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+iptables-persistent (0.5.3+nmu1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * [1ab461] save/load ipset rules (Closes: #662743)
+
+ -- Max Tsepkov Tue, 06 Mar 2012 12:55:49 +0600
+
iptables-persistent (0.5.3) unstable; urgency=low
* [09d9ae] Check for loaded modules in postinst (Closes: #637852)
--
1.7.2.5
Bug#662745: libeegdev0: Suggests eegdev-plugin-free instead of Recommends
Package: libeegdev0 Version: 0.1-1 Severity: wishlist It would be better if libeegdev0 'Recommends' eegdev-plugin-free instead of only 'Suggests' it. It is indeed annoying that installing a software that uses eegdev may not install any set of plugins rendering it useless. Not installing eegdev-plugin-free should be the exception. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libeegdev0 depends on: ii libc6 2.13-26 libeegdev0 recommends no packages. Versions of packages libeegdev0 suggests: ii eegdev-plugins-free 0.1-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645427: Processed: Still occurs with current GNOME 3 in sid
I'm inclined to close this bug, as it got horribly messed up due to the merging and by having gone through different stages of GNOME 2 → 3.0 → 3.2 where functionality got shifted around several times and the merged bugs were actually different ones. What's relevant for gnome 3.2 is gnome-settings-daemon (gnome-power-manager is basically gone) As already mentioned, gsd's power plugin is the one triggering the screen blank on lid-close. I hope you don't mind filing a fresh report against gnome-settings-daemon The important settings here are org.gnome.settings-daemon.plugins.power lid-close-ac-action 'blank' org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank' org.gnome.desktop.screensaver lock-enabled true bug title something like screen is not locked on lid-close when lid-close action is 'blank' Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#662744: RFS: ibus-unikey/0.6.1-1 [RC]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ibus-unikey" * Package name: ibus-unikey Version : 0.6.1-1 Upstream Author : Lê Quốc Tuấn * URL : http://code.google.com/p/ibus-unikey/ * License : GPLv3 Section : utils It builds those binary packages: ibus-unikey - Vietnamese Input Method Engine for IBus using Unikey Engine To access further information about this package, please visit the following URL: http://mentors.debian.net/package/ibus-unikey Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/ibus-unikey/ibus-unikey_0.6.1-1.dsc More information about ibus-unikey can be obtained from http://code.google.com/p/ibus-unikey/. Changes since the last upload: New upstream release (Closes: #661619). Regards, -- Lê Quốc Tuấn (zj3t3mju) fingerprint: 7784 1CD2 BAA0 A746 4BB6 FD05 0ACC 6F3E 3E64 064C -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#556245: src:gnucash: Gnucash should not use copies of code from other packages
severity 556245 wishlist
tags 556245 wontfix patch
--
Specifically regarding QOF:
Debian library 'libqof-dev' 0.8.4-2 despite being up-to-date have little
resemblance to whatever is coming as QOF in gnucash (src/libqof), which have
version 1.4.0
Theoretically if gnucash were using libqof-dev, it could be unbundled with
something like the attached patch.
In practice there is little in common between embedded libqof and debian-
provided one so this patch is causing FTBFS with multiple "unknown type name"
errors.
Regards,
Dmitry.
--- a/configure.ac
+++ b/configure.ac
@@ -544,11 +544,12 @@
### --
### Internal code part which is called "qof"
-LIBQOF_LIBRARY_VERSION=1:4:0
+PKG_CHECK_MODULES(LIBQOF, qof >= 0.8.0)
+LIBQOF_LIBRARY_VERSION=`$PKG_CONFIG --modversion qof`
AC_SUBST(LIBQOF_LIBRARY_VERSION)
-QOF_CFLAGS='-I${top_builddir}/src/libqof/qof -I${top_srcdir}/src/libqof/qof'
-QOF_LIBS='${top_builddir}/src/libqof/qof/libgnc-qof.la'
+QOF_CFLAGS=`$PKG_CONFIG --cflags qof`
+QOF_LIBS=`$PKG_CONFIG --libs-only-l qof`
AC_SUBST(QOF_CFLAGS)
AC_SUBST(QOF_LIBS)
@@ -1383,9 +1384,6 @@
src/import-export/log-replay/Makefile
src/import-export/aqbanking/Makefile
src/import-export/aqbanking/schemas/Makefile
- src/libqof/Makefile
- src/libqof/qof/Makefile
- src/libqof/qof/test/Makefile
src/optional/Makefile
src/optional/gtkmm/Makefile
src/optional/python-bindings/Makefile
--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -1,6 +1,5 @@
# These directories do not contain any gtk dependencies
NONGUI_SUBDIRS = \
- libqof \
debug \
doc \
pixmaps \
Bug#662743: iptables-persistent: Initscript ignores ipset rules
Package: iptables-persistent Version: 0.5.3 Severity: important Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The package does not load/save ipset rules if it exists. I suggest to dump ipset rules to /etc/iptables/ipset, if ipset exists. No need to divide by ip version, ipset can handle both addresses. I'll provide patch as soon as BTS assign bug number. - -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iptables-persistent depends on: ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii iptables1.4.8-3 administration tools for packet fi ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip iptables-persistent recommends no packages. iptables-persistent suggests no packages. - -- Configuration Files: /etc/init.d/iptables-persistent changed [not included] - -- debconf information excluded -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJPVbK1AAoJENfRweM8/RmzVbgH/03fyGFCxhovHeojOG83MZ47 VFZ73lldNoCrJgahpLFFRtV2dsxi1Cjsp/FVSKMeexTWuvTyBt8+tEuo8z0f13df OGQJhRZMZh76wRE4e8E1LgQ5pl+B1DWiBvLk75jBvhOcvc1gQr42Rf42xzDaGf64 HlQ71RsCq/B3aXCxD6C+lZij1IBYK/xHjXdE1DQwuqpq9Kw9+dRlvIbkBqgj9DtX TBUS94q2JdaeMEBh4SMXOYcVVkvINFOhz8aaDtJtCsl0Z5XyqKKp3c1KL2Lvasv2 HScWlk/tHcZ+p2wgvO1TburZmkDUdYQo0wK7OqlLKaK3ai/THzDZjWMqaMC7MeI= =iqwg -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645427: Processed: Still occurs with current GNOME 3 in sid
On Tue, Mar 06, 2012 at 07:34:22AM +0100, Michael Biebl wrote: > This might be a gnome-settings-daemon issue after all. > The gsd power plugin should send a Lock signal when it blanks the screen > similar to how it sends a Lock signal on suspend. That sounds plausible. Judging by the implementation in previous versions, either the source of the Lock signal (the gnome-settings-daemon power plugin with the addition you mention) or the target of the Lock signal will need to chek /org/gnome/desktop/screensaver/lock-enabled , so that people who *disable* gnome-screensaver's screen-locking will not have their screen locked on lid close. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645427: Processed: Still occurs with current GNOME 3 in sid
On Tue, Mar 06, 2012 at 07:07:01AM +0100, Michael Biebl wrote:
> severity 645427 important
> thanks
>
> On 06.03.2012 06:51, Josh Triplett wrote:
> > On Tue, Mar 06, 2012 at 04:37:38AM +0100, Michael Biebl wrote:
> >> On 06.03.2012 03:53, Josh Triplett wrote:
> >>> On Tue, Mar 06, 2012 at 03:25:21AM +0100, Michael Biebl wrote:
> On 06.03.2012 03:15, Debian Bug Tracking System wrote:
> > Processing commands for cont...@bugs.debian.org:
> >
> >> reopen 645427
> > Bug #645427 {Done: Michael Biebl }
> > [gnome-power-manager] Stopped locking the screen when closing the
> > laptop lid
> > Bug #626544 {Done: Michael Biebl }
> > [gnome-power-manager] gnome-screensaver: does not lock the screen in
> > GNOME 3 when the computer goes to sleep
> > Bug #647358 {Done: Michael Biebl }
> > [gnome-power-manager] g-p-m doesn't lock the screen on lid-close
> > because it uses an obsolete GConf key
>
> ..
> >
> > Yes, easily. I created a new user account, logged in as that user, ran
> > gnome-tweak-tool to change the settings described in my previous comment
> > (change lid close from suspend to blank), closed the lid, reopened it,
> > and observed the lack of an unlock screen.
>
> Well, that's what I meant with local configuration. The default is
> suspend-on-lid-close, and in this case the screen locks correctly.
>
> This information is completely missing from your initial bug report. It
> was not clear to me, that you had a custom configuration. (and I think
> in this case #626544 shouldn't have been merged)
>
> So, what you want is lock-on-blank, basically.
I want gnome-screensaver to properly lock the screen as I've already
configured it to do, yes. :)
I mentioned this in the bug log:
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=40;bug=645427
And I mentioned it again in my mail that reopened the bug (the one that
didn't come through properly and I had to forward the contents of).
I merged the bugs at Alexander Kurt's suggestion, because while I ran
GNOME 2 and GNOME 2's version of gnome-power-manager, the workaround
mentioned in bug 647358 (manually setting the gconf key
gnome-power-manager looks at rather than the dconf key that
gnome-screensaver migrated to) solved the problem for me, which matches
the explanation of bug 647358.
This new problem seems different: it appears that gnome-power-manager in
GNOME 3 no longer respects *either* the gconf or dconf keys of
gnome-screensaver that tell it to lock the screen, or alternatively
something other than gnome-power-manager handles blanking the screen and
it doesn't respect org.gnome.desktop.screensaver.lock-enabled.
- Josh Triplett
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645427: Processed: Still occurs with current GNOME 3 in sid
This might be a gnome-settings-daemon issue after all. The gsd power plugin should send a Lock signal when it blanks the screen similar to how it sends a Lock signal on suspend. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#662742: clang: files compiled with "-flto" fail to link
Package: clang
Version: 3.0-6
Severity: normal
I do not know if "-flto" is ever expected to work with clang, but it
doesn't work correctly in the Debian installation:
$ echo 'int main () { return 0; }' > foo.cc
$ clang++ -c -flto -O2 foo.cc -o foo.o
$ clang++ -flto -O2 foo.o -o foo
/usr/bin/ld: error: foo.o:1:3: invalid character
/usr/bin/ld: error: foo.o:1:3: syntax error, unexpected $end
/usr/bin/ld: error: foo.o: not an object or archive
/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/crt1.o(.text+0x20):
error: undefined reference to 'main'
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
$ file foo.o
foo.o: LLVM bitcode
Is there supposed to be a special linker that handles LLVM bitcode?
Thanks,
-miles
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (50,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages clang depends on:
ii libc62.13-27
ii libclang-common-dev 3.0-6
ii libffi5 3.0.10-3
ii libgcc1 1:4.7.0~rc1-1
ii libllvm3.0 3.0-5
ii libstdc++6 4.7.0~rc1-1
ii libstdc++6-4.6-dev 4.6.3-1
Versions of packages clang recommends:
ii llvm-3.0-dev
ii python2.7.2-10
clang suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662741: netcat-openbsd: does not receive a server's response unless -q sec is specified
Package: netcat-openbsd Version: 1.105-1,1.105-2,1.105-3 Severity: grave Justification: renders package unusable After upgrading to wheezy/sid version of netcat-openbsd, a script using nc does not function correctly. If it is run non-interactively, nc.openbsd quits silently before receiving a server's response unless -q sec option is specified: $ printf "GET / HTTP/1.0\r\n\r\n" | nc.openbsd www.example.com 80 $ printf "GET / HTTP/1.0\r\n\r\n" | nc.traditional www.example.com 80 HTTP/1.0 302 Found Location: http://www.iana.org/domains/example/ Server: BigIP Connection: close Content-Length: 0 $ printf "GET / HTTP/1.0\r\n\r\n" | nc.openbsd -q 1 www.example.com 80 HTTP/1.0 302 Found Location: http://www.iana.org/domains/example/ Server: BigIP Connection: close Content-Length: 0 Note that typing input from terminal does not seem to be affected: $ nc.openbsd www.example.com 80 GET / HTTP/1.0 HTTP/1.0 302 Found Location: http://www.iana.org/domains/example/ Server: BigIP Connection: close Content-Length: 0 -- YOSHINO Yoshihito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662180: tuxcmd: Error while saving Configuration
Hi Thorsten Sorry for not coming back to you sooner: On Sun, Mar 04, 2012 at 04:04:29PM +0100, Yooden Vranx wrote: > Package: tuxcmd > Version: 0.6.70+dfsg-1 > Severity: normal > > Dear Maintainer, > > while opening the mount config dialog, I get an error dialog: > > Beim Laden oder Speichern der Konfiguration von tuxcmd ist ein Fehler > aufgetreten. Einige Ihrer Konfigurationseinstellungen könnten nicht richtig > funktionieren. > > (An error occured while loading or saving tuxcmd's configuration. Some of > your configurations might not be working properly) > > Pressing details, I get the following: > > Der Konfigurationsserver konnte nicht kontaktiert werden. Die häufigste > Ursache ist ein fehlender oder unzureichend konfigurierter > D-Bus-Sitzungsdienst. Siehe http://projects.gnome.org/gconf/ für weitere > Informationen. (Details - 1: GetIOR schlug fehl: > GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "GetIOR" with > signature "" on interface "org.gnome.GConf" doesn't exist > ) > > (The configuration server could not be contacted. The most common cause is a > missing or badly configured D-Bus session server.) > > That happened just after an update of gconf2. Can you still reproduce this issue? I supsect a transient issue caused due to the gconf2 update. Regards, Salvatore signature.asc Description: Digital signature
Bug#662740: RFS: recoverjpeg/2.0-3
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "recoverjpeg" * Package name: recoverjpeg Version : 2.0-3 Upstream Author : Samuel Tardieu * URL : http://www.rfc1149.net/download/recoverjpeg/ * License : GPL Section : graphics It builds those binary packages: recoverjpeg - tool to recover JPEG images from a filesystem image To access further information about this package, please visit the following URL: http://mentors.debian.net/package/recoverjpeg Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/r/recoverjpeg/recoverjpeg_2.0-3.dsc Changes since the last upload: Change the patches format for quilt and delete 00list on debian/patches. + This fix FTBFS: dpkg-buildpackage: error (Closes: 643274). Bump Standards-Version to 3.9.3. Regards, William Vera -- William Vera | bi...@billy.mx Systems Engineer / Consultant IT / Sysadmin PGP Key: 1024D/F5CC22A4 3E73 FA1F 5C57 6005 0439 4D75 1FD2 BF96 F5CC 22A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645427: Processed: Still occurs with current GNOME 3 in sid
severity 645427 important
thanks
On 06.03.2012 06:51, Josh Triplett wrote:
> On Tue, Mar 06, 2012 at 04:37:38AM +0100, Michael Biebl wrote:
>> On 06.03.2012 03:53, Josh Triplett wrote:
>>> On Tue, Mar 06, 2012 at 03:25:21AM +0100, Michael Biebl wrote:
On 06.03.2012 03:15, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
>
>> reopen 645427
> Bug #645427 {Done: Michael Biebl }
> [gnome-power-manager] Stopped locking the screen when closing the laptop
> lid
> Bug #626544 {Done: Michael Biebl }
> [gnome-power-manager] gnome-screensaver: does not lock the screen in
> GNOME 3 when the computer goes to sleep
> Bug #647358 {Done: Michael Biebl }
> [gnome-power-manager] g-p-m doesn't lock the screen on lid-close because
> it uses an obsolete GConf key
..
>
> Yes, easily. I created a new user account, logged in as that user, ran
> gnome-tweak-tool to change the settings described in my previous comment
> (change lid close from suspend to blank), closed the lid, reopened it,
> and observed the lack of an unlock screen.
Well, that's what I meant with local configuration. The default is
suspend-on-lid-close, and in this case the screen locks correctly.
This information is completely missing from your initial bug report. It
was not clear to me, that you had a custom configuration. (and I think
in this case #626544 shouldn't have been merged)
So, what you want is lock-on-blank, basically.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#662739: condor: fails to remove: find: `/var/run/condor': No such file or directory
Package: condor Version: 7.7.4+git3-gd7ce75b~dfsg.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. >From the attached log (scroll to the bottom...): Removing condor ... invoke-rc.d: policy-rc.d denied execution of stop. find: `/var/run/condor': No such file or directory dpkg: error processing condor (--remove): subprocess installed pre-removal script returned error exit status 1 cheers, Andreas condor_7.7.4+git3-gd7ce75b~dfsg.1-1.log.gz Description: GNU Zip compressed data
Bug#662738: frama-c: segfault when running frama-c-gui
Package: frama-c Version: 20111001+nitrogen+dfsg-3 Hi Mehdi, I just found out about frama-c and wanted to give it a try. However: $ frama-c-gui Segmentation fault The backtrace goes all the way to libQtGui.so.4 (I use the libqt4 gtk engine) from the following: #67 0xb7df61a2 in gtk_widget_show () from /usr/lib/libgtk-x11-2.0.so.0 #68 0x0858e787 in ml_gtk_widget_show () #69 0x084eb431 in camlGWindow__method_show_3683 () #70 0xb6690270 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) The rest is probably not very relevant, so I'm omitting it. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#643470: [pkg-dhcp-devel] Bug#643470: Status of isc-dhcp-client
On Mon, Mar 05, 2012 at 09:48:48AM +, peter green wrote: > > >I just reviewed the most recent email I exchanged with the ISC product > >manager, and she actually said "end of February", although she wasn't a > >betting woman. > > > >So let's wait until March 1 to take stock of the situation. If no 4.2.4 > >upstream release has been made by March 1, I will check in with them to get > >an updated timeframe, and if it's anything more than a week or so, I'll > >repack the tarball. > It's now the 5th of match and still no new upstream release. Has any > progress with > upstream been made? I'll check in with them tomorrow. signature.asc Description: Digital signature
Bug#662737: apt-cacher: Fails to retrieve packages
Package: apt-cacher
Version: 1.7.3~rc4
Justification: renders package unusable
Severity: grave
*** Please type your report below this line ***
*some* clients fail to download packages. Some are pure Squeeze, others
include Squeeze-backports. All use apt (no aptitude, synaptic etc). I've
tried a number of repositories over the last four days. The error is the
same and I can't work out why it only seems to affect some boxen.
Example error message on clients (edited):-
Failed to fetch
http://http.us.debian.org/debian/pool/main/c/cairomm/libcairomm-1.0-1_1.8.4-3_i386.deb
Connection failed
Site is good, and on the same machine:-
# wget -t 0
http://http.us.debian.org/debian/pool/main/c/cairomm/libcairomm-1.0-1_1.8.4-3_i386.deb
--2012-03-06 14:18:10--
http://http.us.debian.org/debian/pool/main/c/cairomm/libcairomm-1.0-1_1.8.4-3_i386.deb
Resolving http.us.debian.org... 64.50.233.100, 64.50.236.52,
128.30.2.36, ...
Connecting to http.us.debian.org|64.50.233.100|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 72176 (70K) [application/x-debian-package]
Saving to: `libcairomm-1.0-1_1.8.4-3_i386.deb'
100%[=>] 72,176 40.8K/s
in 1.7s
2012-03-06 14:18:16 (40.8 KB/s) - `libcairomm-1.0-1_1.8.4-3_i386.deb'
saved [72176/72176]
/var/log/apt-cacher/error.log (edited) shows:-
Tue Mar 6 14:12:11 2012|error [16392]: Failed to open/create
libcairomm-1.0-1_1.8.4-3_i386.deb for return: Permission denied at
/usr/sbin/apt-cacher line 696, line 4.
There is no /var/cache/apt-cacher/packages/
===/usr/sbin/apt-cacher lines 693-698 =
# Open/create cached file
for (my $cached_file = "$cfg->{cache_dir}/packages/$cache->{name}") {
unlink $cached_file if $cache->{status} && $cache->{status} eq
'NOCACHE'; # Ensure new file for Cache-Control: no-cache
sysopen($cache->{content}, $cached_file, O_RDWR|O_CREAT)
|| die "Failed to open/create $cached_file for return: $!";
}
I've tried different repositories - same type of errors on the same
clients. Likewise changing client IP addresses. If I duplicate
everything below /etc/apt from a working box nothing changes (same
error). The only thing I haven't been able to try is downloading the
exact same packages on a working box as on a non-working box.
Please let me know what additional logs, or config files I can attach,
or tests I can run.
-- System Information:
Debian Release: 6.0.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apt-cacher depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration
management sy
ii dpkg 1.15.8.12 Debian package management
system
ii ed1.4-3 The classic UNIX line editor
ii libfilesys-df-perl0.92-3+b1 Module to obtain filesystem
disk s
ii libfreezethaw-perl0.5001-1 module to serialize and
deserializ
ii libio-interface-perl 1.05-1 socket methods to get/set
interfac
ii libnetaddr-ip-perl4.028+dfsg-1 IP address manipulation module
ii libsys-syscall-perl 0.23-1 module to access system
calls that
ii libwww-curl-perl 4.12-1 Perl bindings to libcurl
ii libwww-perl 5.836-1Perl HTTP/WWW client/server
librar
ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2
init scrip
ii perl 5.10.1-17squeeze3 Larry Wall's Practical
Extraction
ii update-inetd 4.38+nmu1+squeeze1 inetd configuration file
updater
Versions of packages apt-cacher recommends:
ii libberkeleydb-perl 0.42-1~squeeze1 use Berkeley DB 4 databases
from P
Versions of packages apt-cacher suggests:
pn libio-socket-inet6-perl(no description available)
-- Configuration Files:
/etc/apt-cacher/apt-cacher.conf changed:
log_dir = /var/log/apt-cacher/
group = www-data
user = www-data
allowed_hosts = 192.168.0.0/24
generate_reports = 1
/etc/default/apt-cacher changed:
AUTOSTART=1
-- debconf information:
* apt-cacher/mode: daemon
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662726: use of ancestor-path
On Mon, 05 Mar 2012 22:10:48 -0400, David Bremner wrote:
>
> One thing I think I got wrong in round 1 is the blanket use of
> --ancestor-path. Consider the following branch structure, where
> upstream has been merged into master several times.
Here is a revised version. Let's pretend there were all kinds of useful
discussions in some other medium that led to this.
No use of ancestor-path in this one, instead we just use git-log
(with 'git debpatch log') for a status command.
Tagging and untagging is now only for a single commit.
I'm not 100% convinced about the order of parameters for fields with
values, but
git debpatch +export $sha1
git debpatch -export $sha1
seems quite natural, and
git debpatch +forwarded $sha1 $urlorwhatever
is probably a less common usecase.
Thinking back to earlier discussions about configurability, I can see
this might be a bit _too_ flexible, it would be easy to typo
git debpatch +expert $sha1
And then wonder why the patch isn't exported. Perhaps I should put back
"mark" and "unmark" as aliases for "+export" and "-export"
One thing this version doesn't do is export the metadata in the patch;
that could be useful, but needs a bit more hackery afaict.
>From 1e1029b0e7f78e43c56bc330606884a687bdc1e8 Mon Sep 17 00:00:00 2001
From: David Bremner
Date: Mon, 5 Mar 2012 12:17:46 -0400
Subject: [PATCH] git-debpatch: select commits to be exported as quilt patches
This script allows the user to mark commits for export as
quilt-patches in debian/patches. gitpkg support is provided via
hooks/quilt-patches-deb-export-hook.
---
git-debpatch| 108 +++
git-debpatch.1 | 68 ++
gitpkg.1|3 +-
hooks/quilt-patches-deb-export-hook |3 +
4 files changed, 181 insertions(+), 1 deletions(-)
create mode 100755 git-debpatch
create mode 100644 git-debpatch.1
diff --git a/git-debpatch b/git-debpatch
new file mode 100755
index 000..945ee13
--- /dev/null
+++ b/git-debpatch
@@ -0,0 +1,108 @@
+#!/bin/bash
+
+GN="git notes --ref debpatch"
+patch_dir=debian/patches
+
+# get_field ref Field
+#
+function get_field() {
+${GN} show $1 2>/dev/null | sed -n "s/^$2: \(.*\)$/\1/p"
+}
+
+# set_field ref Field Val
+function set_field() {
+other_fields=$(${GN} show $1 2>/dev/null | grep -v "^$2:")
+printf "$2: $3\n$other_fields" | ${GN} add -f -F- $1 2>/dev/null
+}
+
+# remove_field ref Field
+function remove_field() {
+other_fields=$(${GN} show $1 2>/dev/null | grep -v "^$2:")
+if [ -n "$other_fields" ] ; then
+ printf "$other_fields" | ${GN} add -f -F- $1 2>/dev/null
+else
+ $GN remove $1 2>/dev/null
+fi
+}
+
+function is_exportable() {
+[ $(get_field $1 Export)x = "truex" ]
+}
+
+function export_one_patch() {
+if [ -f $patch_dir/series ]; then
+ count=$(wc -l "$patch_dir/series" | cut -f1 -d' ')
+else
+ mkdir -p "$patch_dir" || exit 1
+ echo "# exported from git by git-debpatch" > "$patch_dir/series"
+ count=1
+fi
+
+name=$(git format-patch --start-number $count -1 -o "$patch_dir" $1)
+echo "$name" | sed -e "s,$patch_dir/,,g" -e 's, ,\n,g' >> "$patch_dir/series"
+}
+
+
+function insist_commits() {
+if [ $(git rev-parse $1 | wc -l) != $2 ]; then
+ echo "$1 does not expand to exactly $2 commits";
+ exit 1;
+
+fi;
+}
+
+function add_tag() {
+insist_commits $1 1
+field=${2^}
+value=${3-true}
+set_field $ref $field $value
+}
+
+function remove_tag() {
+insist_commits $1 1
+field=${2^}
+value=${3-true}
+remove_field $1 $field
+}
+
+case $1 in
+fetch)
+ remote=${2-origin}
+ git fetch $remote refs/notes/debpatch:refs/notes/remotes/$remote/debpatch
+ exit 0;
+ ;;
+merge)
+ remote=${2-origin}
+ ${GN} merge --strategy=cat_sort_uniq refs/notes/remotes/$remote/debpatch
+ exit 0;
+ ;;
+pull)
+ git debpatch fetch $2 && git debpatch merge $2
+ exit $?
+ ;;
+push)
+ remote=${2-origin}
+ git push $remote refs/notes/debpatch:refs/notes/debpatch
+ exit 0;
+ ;;
++*)
+ ref=${2-HEAD}
+ add_tag $ref ${1#+} $3
+ ;;
+-*)
+ ref=${2-HEAD}
+ remove_tag $ref ${1#-} $3
+ ;;
+toquilt)
+ ref=${2-HEAD}
+ git rev-list --reverse $ref | \
+ while read hash ; do
+ if is_exportable $hash; then
+ export_one_patch $hash
+ fi
+ done
+ ;;
+
+*)
+ GIT_NOTES_REF=refs/notes/debpatch exec git $*
+esac
diff --git a/git-debpatch.1 b/git-debpatch.1
new file mode 100644
index 000..3cf51ee
--- /dev/null
+++ b/git-debpatch.1
@@ -0,0 +1,68 @@
+.\" Hey, EMACS: -*- nroff -*-
+.\" First parameter, NAME, should be all caps
+.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
+.\" other parameters are allowed: see man(7), man(1)
+.TH GIT-DEBPATCH 1 "March 5, 2012"
+.\" Please adjust this date whenever revising the manpage.
+.\"
+.\" Some roff macros, for reference:
+.\" .nhdisable hyphenation
+.\" .
Bug#662736: RFP: maxwell(8) entropy-gathering demon
Package: maxwell Version: 1.2 > This collects randomness from timer interrupts and feeds it to random(4). > It is mainly useful on very limited systems -- phone. embedded, > It may be essential on some Freedom Box systems. > > Code and a PDF rationale document at: > ftp://ftp.cs.sjtu.edu.cn:990/sandy/maxwell/ > > License is GPL v2. > > I am the author and am willing to assist as necessary, but > I do not want to take on responsibilty for Debian packaging > and maintenance. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662735: w3c-markup-validator: "debcheckout w3c-sgml-validator" gives git error; typo in repo URL
Package: w3c-markup-validator Version: 1.2+dfsg-2 Severity: normal Dear Maintainer, Look what just happened: , | % debcheckout w3c-markup-validator | declared git repository at | git://github.com:periapt/w3c-markup-validator.git | git clone git://github.com:periapt/w3c-markup-validator.git | w3c-markup-validator ... | Cloning into 'w3c-markup-validator'... | fatal: unable to connect to github.com: | github.com: Servname not supported for ai_socktype | | checkout failed (the command above returned a non-zero exit code) ` I assume you can see what's wrong here? (Which is obviously not the same as whatever git is complaining about, whatever that is...) -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662200: libcvc3-5-jni and libcvc3-2-jni: error when trying to install together
I've uploaded a new package to mentors that addresses this and #662198. I decided to add a Replaces/Breaks on libcvc3-2-jni, since the file /usr/lib/jni/libcvc3jni.so appears to be necessary for the binary package to function. -Chris On Mon, Mar 5, 2012 at 11:08 AM, Christopher L Conway < christopherleecon...@gmail.com> wrote: > On Mon, Mar 5, 2012 at 3:08 AM, Ralf Treinen wrote: > >> Hello, >> >> On Sun, Mar 04, 2012 at 01:22:19PM -0500, Christopher L Conway wrote: >> >Not sure how to handle this. On the C++ side, the policy dictates a >> >libcvc3-X package with libcvc3.so.X and a libcvc3-X-dev package with >> >libcvc3.so -> libfoo.so.X. On the Java side, we don't have any >> headers to >> >install, so a libcvc3-X-jni-dev package seems like overkill just for >> a >> >libcvc3jni.so symlink. >> >> I have no idea about java packaging. Did you check what the debian Java >> policy says ? (not sure whether there is one, but at least there should >> exist such a policy :-) >> > > The Debian policy for Java on JNI packages ( > http://www.debian.org/doc/packaging-manuals/java-policy/x145.html) > provides no real guidance on this question akin to Debian Policy Sections > 8.1 and 8.5. > > -Chris > >
Bug#662734: RFS: arp-scan/1.8.1-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "arp-scan" * Package name: arp-scan Version : 1.8.1-2 Upstream Author : Roy Hills * URL : http://www.nta-monitor.com/tools/arp-scan/ * License : GPLv3 Section : admin It builds those binary packages: arp-scan - arp scanning and fingerprinting tool To access further information about this package, please visit the following URL: http://mentors.debian.net/package/arp-scan Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/a/arp-scan/arp-scan_1.8.1-2.dsc Changes since the last upload: Added a patch to fix FTBFS on GNU/kFreeBSD. (Closes: #641643). Updated Standards Version to 3.9.3. Regards, William Vera -- William Vera | bi...@billy.mx Systems Engineer / Consultant IT / Sysadmin PGP Key: 1024D/F5CC22A4 3E73 FA1F 5C57 6005 0439 4D75 1FD2 BF96 F5CC 22A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659505: Switching to identical package for other arch treated as disappearance
On Sat, 2012-02-11 at 17:07:39 +, Ben Hutchings wrote:
> Package: dpkg
> Version: 1.16.2~wipmultiarch
> Severity: normal
>
> I usually build linux-2.6 on amd64, but also test the binaries on an
> i386 installation. I've been installing with --force-architecture up
> until now. APT would basically ignore the foreign package; dpkg was
> also happy to do this 'upgrade' to the same version with architecture
> i386.
>
> However, with multi-arch, this happens:
>
> $ sudo apt-get install linux-image-3.2.0-1-amd64:i386
> linux-image-3.2.0-1-amd64:amd64-
[...]
> Despite what the final message says, the files for
> linux-image-3.2.0-1-amd64:i386 are installed at this point.
This should be fixed now as a side effect of the proper cross-grading
support I implemented some weeks ago, the bogus disappearing was due to
the previous broken in-core db layout. I just tested this locally now to
make sure that's the case though, here's the session (on amd64 though,
but it should be equivalent):
$ dpkg --print-architecture
amd64
$ dpkg --print-foreign-architectures
i386
$ dpkg-query -f '${db:Status-Abbrev} ${Package} ${Architecture} ${Version}\n'
-W linux-image-3.2.0-2-amd64
No packages found matching linux-image-3.2.0-2-amd64.
$ dpkg -i linux-image-3.2.0-2-amd64_3.2.9-1_amd64.deb
Selecting previously unselected package linux-image-3.2.0-2-amd64.
(Reading database ... 15193 files and directories currently installed.)
Unpacking linux-image-3.2.0-2-amd64 (from
linux-image-3.2.0-2-amd64_3.2.9-1_amd64.deb) ...
Setting up linux-image-3.2.0-2-amd64 (3.2.9-1) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-2-amd64
/boot/vmlinuz-3.2.0-2-amd64
[...run-parts output...]
$ dpkg-query -f '${db:Status-Abbrev} ${Package} ${Architecture} ${Version}\n'
-W linux-image-3.2.0-2-amd64
ii linux-image-3.2.0-2-amd64 amd64 3.2.9-1
$ dpkg -i linux-image-3.2.0-2-amd64_3.2.9-1_i386.deb
(Reading database ... 18646 files and directories currently installed.)
Preparing to replace linux-image-3.2.0-2-amd64 3.2.9-1 (using
linux-image-3.2.0-2-amd64_3.2.9-1_i386.deb) ...
Unpacking replacement linux-image-3.2.0-2-amd64 ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.2.0-2-amd64
/boot/vmlinuz-3.2.0-2-amd64
Setting up linux-image-3.2.0-2-amd64 (3.2.9-1) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-2-amd64
/boot/vmlinuz-3.2.0-2-amd64
[...run-parts output...]
$ dpkg-query -f '${db:Status-Abbrev} ${Package} ${Architecture} ${Version}\n'
-W linux-image-3.2.0-2-amd64
ii linux-image-3.2.0-2-amd64 i386 3.2.9-1
regards,
guillem
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656839: transition: linphone libexosip2 libosip2
Cyril Brulebois (04/03/2012): > Looks good so far, just scheduled binNMU for sipwitch everywhere but on > s390x. Everything looks ready from here, except libexosip2/s390x and sipwitch/s390x which can now be binNMU'd. Those won't be any blocker anyway since s390x isn't considered when looking at candidates. I'll run a few tests to make sure they will migrate on their own when the time has come (in 4.5 days). Mraw, KiBi. signature.asc Description: Digital signature
Bug#658479: GNOME 3 integration: Use GIO instead of deprecated GnomeVFS
ping? any chance you could have a look at those two patches so we can have a icedove package which properly integrates into GNOME (for wheezy). Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#662733: Raise deluge gtk interface if deluge is already running
Package: deluge Version: 1.2.3+git20110209.8c36830-0squeeze1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Currently, if deluge is already running and user launches another copy, then deluge silently exit, refusing to launch. In such case, it would be helpful if gtk interace (if exists) is brought up and user get focus on it. Assuming this, it would be possible to bind "deluge" on a hotkey in GNOME. Then if deluge is not running, it launches, otherwise existing version gets attention. - -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages deluge depends on: ii delu 1.2.3+git20110209.8c36830-0squeeze1 bittorrent client written in Pytho ii pyth 2.6.6-3+squeeze6interactive high-level object-orie deluge recommends no packages. deluge suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJPVZDbAAoJENfRweM8/Rmz6mwIAKx4CLYO4EG0mkjoXBBVMaYb UfbKvsucNQsCBA7v5wahUc7qDtkMIbeUhp49OUmxj2WK5lEUKd52Qn9ige731Mvi 3q92m/goHcj9Japp2mAIN1P1FJqAwtVKEOOucXnRgykyeueaND+NgqIsPNlVZ8UC qUaeLUi1xohxzgAQVztVENfaEiZ2Uj72D+e2MOJRbbbjahOGJVOnjMAfXAJwzd3a wVM7OyHxvV4ZcoyATLi8KZPMBbbOOdzhiDyHwRgRL+gqBPaEfwGh+AtfVI5+VvYN q6zF8lR97/ddgpUo9J3GegWfDB0IHCDpVRmNyueQh1pEKz6lnnXdxS+p3KbUmag= =I5X8 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661511: (another) ftbfs
Your package also ftbfs when built twice in a row >From my output: | dpkg-source -b tpb-0.6.4 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building tpb using existing ./tpb_0.6.4.orig.tar.gz | dpkg-source: warning: ignoring deletion of directory autom4te.cache | dpkg-source: warning: ignoring deletion of file autom4te.cache/output.0 | dpkg-source: warning: ignoring deletion of file autom4te.cache/requests | dpkg-source: warning: ignoring deletion of file autom4te.cache/traces.0 | dpkg-source: info: local changes detected, the modified files are: | tpb-0.6.4/config.h.in | tpb-0.6.4/configure | tpb-0.6.4/stamp-h.in | dpkg-source: info: you can integrate the local changes with dpkg-source --commit | dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/tpb_0.6.4-8.diff.XRpvcn | dpkg-buildpackage: error: dpkg-source -b tpb-0.6.4 gave error exit status 2 Thanks again! Paul -- All programmers are playwrights, and all computers are lousy actors. #define sizeof(x) rand() :wq -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660420: Some Postscript printer drivers (Kyocera, Brother, maybe others) do not work anymore
Hi Wolfgang, Am 06.03.2012 01:28, schrieb Wolfgang Walter: I can also confirm that printing to a kyocera FS-1300D (as a postscript- printer) does not work any more. It does not print and hangs instead. This seems to be due to the postscript file generated from the PDF by ghostscript (called by the pdftops cups filter in my case). To test I tried to print my .bashrc: lp .bashrc 1. I redirected the final output a file and then sent to the printer by hand: printer does not print and hangs. 2. I modified cupsfilters.convs such that I get the PDF. I then used pdf2ps to generate the postscript file. Sent it to the printer: printer does not print and hangs. 3. I used pdftops from poppler-utils to generate the postscript file: Sent it to the printer and it works. 4. I used ps2ps on this postscript file: the generated one does not work and printer hangs. I called gs with -sDEVICE=pswrite to genrate a postscript file from the PDF: that one worked. The only way I may print using cups with a kyocera FS-1300D as postscript printer is by printing to a file as PDF and then using acroread to actually print it. Regards I tried to follow your explanations but somehow I did not succeed. :) Anyway, did you try to set the printer to use a generic Postscript PPD as outlined here in this report before? regards Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#497779: Patch for mime-support to handle .desktop files
On Mon, Mar 05, 2012 at 05:55:32AM +0100, Michael Biebl wrote: > Shouldn't you also register a file-based trigger for > /usr/share/applications? One needs to be registered, yes. I figured that was something that the maintainer would take care of when he applied the patch. I'm not familiar enough with dpkg triggers to do so myself. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#631873: Please transition cairo for multiarch
Hi, Does anyone know the status of this patch, or when a fix is scheduled? libcairo2 is currently blocking me from installing an application the multiarch way. I'm wondering what version or timeframe might bring multiarch support to libcairo2? Thanks for your time and effort, Rickard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662732: lxmusic: exit not minimize
Package: lxmusic Version: 0.4.4+git20100802-2.1 When I click on the X in the window title bar, I expect it to close the application, not minimize it! This is broken behavior please fix it (and other apps doing it too is no excuse). Thanks, -- Matt Taggart tagg...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660660: Acknowledgement (klibc: mount broken on parisc - breaks boot)
Here is some further information. I patched usr/klibc/../include/sys/socket.h to avoid the redefinition but it didn't fix the mount error. In initramfs, I was able to mount /root on /dev/sda5 with the command "mount -t ext3 /dev/sda5 /root". I saw that adding rootfstype=ext4 resolved a similar problem discussed in this thread: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/309762 So, I tried adding rootfstype=ext3 to my boot command and had a successful boot. So, there must be a problem with ext3 device probing on parisc. Dave -- John David Anglin dave.ang...@bell.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662731: O: hwinfo - Hardware identification system
Package: wnpp Severity: normal I orphan this package now. This package requires more attention than I can give, in addition to no longer use and would rather focus on my other packages. Maintaining a package requires time and skills. Please only adopt this package if you are *sure* you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. -- William Vera | bi...@billy.mx Systems Engineer / Consultant IT / Sysadmin PGP Key: 1024D/F5CC22A4 3E73 FA1F 5C57 6005 0439 4D75 1FD2 BF96 F5CC 22A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645427: Processed: Still occurs with current GNOME 3 in sid
On 06.03.2012 03:53, Josh Triplett wrote:
> On Tue, Mar 06, 2012 at 03:25:21AM +0100, Michael Biebl wrote:
>> On 06.03.2012 03:15, Debian Bug Tracking System wrote:
>>> Processing commands for cont...@bugs.debian.org:
>>>
reopen 645427
>>> Bug #645427 {Done: Michael Biebl } [gnome-power-manager]
>>> Stopped locking the screen when closing the laptop lid
>>> Bug #626544 {Done: Michael Biebl } [gnome-power-manager]
>>> gnome-screensaver: does not lock the screen in GNOME 3 when the computer
>>> goes to sleep
>>> Bug #647358 {Done: Michael Biebl } [gnome-power-manager]
>>> g-p-m doesn't lock the screen on lid-close because it uses an obsolete
>>> GConf key
>>> 'reopen' may be inappropriate when a bug has been closed with a version;
>>> you may need to use 'found' to remove fixed versions.
thanks
>>
>> Why did you re-open?
>
> For some reason, my mail made it to control@bugs but not to 645427@bugs.
> (It happened the first time because I needed to unarchive, but I sent
> the second one after unarchiving, so I don't know why *that* one didn't
> go through. I also don't know why only two of those three bugs
> reopened, and 645427 didn't.) I've included it below:
Please file a new bug next time, so we have the exact versions of the
affected packages.
Are you running gnome-shell/fallback/some-other-de?
Is this problem reproducible with a fresh user account?
Screen-locking works perfectly here, so I'm suspecting some local
(mis)configuration.
Could you attach a "gsettings list-recursively" dump, please
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#661293: (no subject)
My mistake. It just happened again, same error message. Nothing special going on. I was just suddenly unable to click anything, and nothing responded to any input, except the mouse cursor could move. The frequency has certainly been reduced (I went nearly a week), but the bug apparently still exists. Anything I can do to help you isolate the bug, just let me know. Please re-open it though. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662628: Workaround.
A workaround may be possible. I had similar problems with this package and found that if I change the Video Output to "X11 video output (XCB)" from "Default" VLC will play videos. The problem for me was that the package was defaulting to "XVideo output (XCB)" which was not found. Trying to play videos would then would peg my processor resulting in having to Kill the process. I'm not sure what changed in the package upgrade to cause this problem though. Good Luck! "Twenty years from now you will be more disappointed by the things that you didn't do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover." -- Mark Twain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655970: Bug# 655970 - cman | corosync
Hi Nicolas, As a corosync/pacemaker user, I would like to see the dependency of "cman | corosync" remain. I would not like the package to return to a just cman dependency. Maybe for the test "[ ! -f /etc/cluster/cluster.conf ]", if using corosync it could test for "/etc/corosync/corosync.conf". And maybe "cman_tool status" could test for "/etc/init.d/corosync status". Thanks, Deric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662501: simage: Please Build-Depends on libpng-dev, change from libpng12-dev
block 662501 by 648126 thanks > Libpng maintainers plan transition of libpng[0]. > Version 1.2 is used for libpng of current debian, but will shifts > to version 1.5 in this transition. > Your package still does it depending on libpng12-dev. PNG 1.5 breaks the API, so cannot change build-depends until PNG or ITK is fixed. -Steve signature.asc Description: Digital signature
Bug#662729: Acknowledgement (/usr/bin/jh_linkjars: jh_linkjars fails when using dh --verbose)
On Tue, 06 Mar 2012 03:06:05 + ow...@bugs.debian.org (Debian Bug Tracking System) wrote: > Thank you for filing a new Bug report with Debian. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. As I test further, it turns out jh_installjavadoc has the same problem. Switching to using this at the top of the rules file it works: # Uncomment this to turn on verbose mode. export DH_VERBOSE=1 using this in the rules, it fails: %: dh --verbose --with javahelper $@ thanks, kk -- Karl Goetz, (Kamping_Kaiser / VK7FOSS) http://www.kgoetz.id.au No, I won't join your social networking group *** I've changed GPG key to 6C097260 *** signature.asc Description: PGP signature
Bug#662730: acpi-support: typo in /etc/default/acpi-support comment
Package: acpi-support Version: 0.138-14 Severity: minor /etc/default/acpi-support contains: # xrandr needs the outout device to be named ^^ This should be "output". -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages acpi-support depends on: ii acpi-fakekey 0.138-14 ii acpi-support-base 0.138-14 ii acpid 1:2.0.14-3 ii lsb-base 3.2+Debian30 ii pm-utils 1.4.1-9 ii x11-xserver-utils 7.6+3 Versions of packages acpi-support recommends: ii dbus 1.4.18-1 ii gnome-screensaver 3.2.0-2+b1 ii radeontool 1.6.2-1.1 ii vbetool1.1-2 ii xscreensaver 5.15-2 Versions of packages acpi-support suggests: pn rfkill pn xinput -- Configuration Files: /etc/default/acpi-support changed: ACPI_SLEEP=true ACPI_HIBERNATE=true LOCK_SCREEN=true LID_SLEEP=true DISPLAY_DPMS=xset XRANDR_OUTPUT=LVDS-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662729: /usr/bin/jh_linkjars: jh_linkjars fails when using dh --verbose
Package: javahelper Version: 0.32 Severity: important File: /usr/bin/jh_linkjars Hi, I'm trying to debug a package using jh and dh (compat 7), and jh_linkjars is buggering up. dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building crg-scoreboard using existing ./crg-scoreboard_0.2.0.orig.tar.bz2 dpkg-source: info: building crg-scoreboard in crg-scoreboard_0.2.0-1.debian.tar.gz dpkg-source: info: building crg-scoreboard in crg-scoreboard_0.2.0-1.dsc debian/rules build dh --verbose --with javahelper build dh_testdir -O--verbose dh_auto_configure -O--verbose jh_linkjars -O--verbose Invalid option: O Usage: jh_linkjars [options] [target] Options: -h --help: show this text -V --version: show the version -v --verbose: show more information while running -t --transitive: transitively link jars -n --no-act: don't actually do anything, just print the results -u --unlink: remove the links instead of adding them make: *** [build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 debuild: fatal error at line 1325: dpkg-buildpackage -rfakeroot -D -us -uc failed jh_clean appeared to run correctly earlier on, so I suspect its not a general problem with javahelper packages thanks, kk -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages javahelper depends on: ii bsdmainutils 8.0.13 collection of more utilities from ii dctrl-tools 2.14.5 Command-line tools to process Debi ii debhelper 9.20120115~bpo60+1 helper programs for debian/rules ii devscripts2.10.69+squeeze2 scripts to make the life of a Debi ii dpkg-dev 1.15.8.12 Debian package development tools ii fastjar 2:0.98-3 Jar creation utility ii libarchive-zip-perl 1.30-3 Perl module for manipulation of ZI javahelper recommends no packages. Versions of packages javahelper suggests: pn cvs(no description available) ii gawk1:3.1.7.dfsg-5 GNU awk, a pattern scanning and pr ii tofrodos1.7.8.debian.1-2 Converts DOS <-> Unix text files, -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645427: Processed: Still occurs with current GNOME 3 in sid
On Tue, Mar 06, 2012 at 03:25:21AM +0100, Michael Biebl wrote:
> On 06.03.2012 03:15, Debian Bug Tracking System wrote:
> > Processing commands for cont...@bugs.debian.org:
> >
> >> reopen 645427
> > Bug #645427 {Done: Michael Biebl } [gnome-power-manager]
> > Stopped locking the screen when closing the laptop lid
> > Bug #626544 {Done: Michael Biebl } [gnome-power-manager]
> > gnome-screensaver: does not lock the screen in GNOME 3 when the computer
> > goes to sleep
> > Bug #647358 {Done: Michael Biebl } [gnome-power-manager]
> > g-p-m doesn't lock the screen on lid-close because it uses an obsolete
> > GConf key
> > 'reopen' may be inappropriate when a bug has been closed with a version;
> > you may need to use 'found' to remove fixed versions.
> >> thanks
>
> Why did you re-open?
For some reason, my mail made it to control@bugs but not to 645427@bugs.
(It happened the first time because I needed to unarchive, but I sent
the second one after unarchiving, so I don't know why *that* one didn't
go through. I also don't know why only two of those three bugs
reopened, and 645427 didn't.) I've included it below:
- Forwarded message from Josh Triplett -
Date: Mon, 5 Mar 2012 18:10:57 -0800
From: Josh Triplett
To: 645...@bugs.debian.org
Cc: cont...@bugs.debian.org
Subject: Still occurs with current GNOME 3 in sid
User-Agent: Mutt/1.5.21 (2010-09-15)
reopen 645427
thanks
On Thu, Oct 27, 2011 at 03:06:09PM +, Debian Bug Tracking System wrote:
> gnome-screensaver (3.0.1-3) unstable; urgency=low
> .
>* Bump dependency on gnome-session-bin to (>= 3.0) to avoid partial
> upgrades
> which can result in having the screen no longer locked on lid-close.
> Closes: #645427
I just upgraded my system to GNOME 3, and I've updated all components
without any partial upgrade. I still observe this problem. I set GNOME
to blank the screen on lid close
(/org/gnome/settings-daemon/plugins/power/lid-close-ac-action=blank and
/org/gnome/settings-daemon/plugins/power/lid-close-battery-action=blank),
and I confirmed that the screensaver configuration says to lock
immediately (/org/gnome/desktop/screensaver/lock-enabled=true and
/org/gnome/desktop/screensaver/lock-delay=0). Nonetheless, if I close
the laptop lid, the screen blanks but does not lock.
- Josh Triplett
- End forwarded message -
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662726: use of ancestor-path
One thing I think I got wrong in round 1 is the blanket use of --ancestor-path. Consider the following branch structure, where upstream has been merged into master several times. upstream ---0. \__A_\B___C_ master for things like status, --ancestor-path makes sense (or is at least convenient) since it stops at B, rather returning all non-upstream commits. However, for exporting patches, we really want to catch A unless it has been merged upstream. In fact is much more likely to be cherry-picked upstream, which we probably can't easily detect. On the other hand exporting extra patches is relatively harmeless here, since we are already relying on dpkg-source to detect our that patches have been applied. I'll play around with maybe making ancestor-path optional, but for now you might want to delete --ancestry-path on line 121 of git-debpatch. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645427: Processed: Still occurs with current GNOME 3 in sid
On 06.03.2012 03:15, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
>
>> reopen 645427
> Bug #645427 {Done: Michael Biebl } [gnome-power-manager]
> Stopped locking the screen when closing the laptop lid
> Bug #626544 {Done: Michael Biebl } [gnome-power-manager]
> gnome-screensaver: does not lock the screen in GNOME 3 when the computer goes
> to sleep
> Bug #647358 {Done: Michael Biebl } [gnome-power-manager]
> g-p-m doesn't lock the screen on lid-close because it uses an obsolete GConf
> key
> 'reopen' may be inappropriate when a bug has been closed with a version;
> you may need to use 'found' to remove fixed versions.
>> thanks
Why did you re-open?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#662723: ls: -F (--indicator-style=classify) affects on symbolic link dereference
On 03/06/2012 05:43 AM, Michael Stone wrote: > On Tue, Mar 06, 2012 at 03:50:34AM +0400, sergio wrote: >> indicator-style mast not affect on dereference. >> % /bin/ls -F /var/run >> /var/run@ > Can you be more specific about what you're looking for? I mean ls -F /var/run should give: acpid.pid dhclient.eth0.pid lock/ rsyslogd.pid sshd/ -- sergio. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662728: After unlocking the screen, the notification area shows up, even with no notifications
Package: gnome-screensaver Version: 3.2.0-2+b1 Severity: normal Immediately after unlocking the screen, the notification area (the translucent black area at the bottom of the screen) appears in the shell, whether or not any new notifications exist. It makes sense to show notifications after unlocking the screen, but only if such notifications exist; otherwise, it just obscures the bottom of the screen for a while without actually displaying any information. - Josh Triplett -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-screensaver depends on: ii dbus-x11 1.4.18-1 ii dpkg 1.16.1.2 ii gnome-icon-theme 3.2.1.2-1 ii gnome-session-bin 3.2.1-1 ii gsettings-desktop-schemas 3.2.0-2 ii libc6 2.13-27 ii libcairo2 1.10.2-6.2 ii libdbus-1-31.4.18-1 ii libdbus-glib-1-2 0.98-1 ii libgdk-pixbuf2.0-0 2.24.1-1 ii libglib2.0-0 2.30.2-6 ii libgnome-desktop-3-2 3.2.1-3 ii libgnomekbd7 3.2.0-1 ii libgtk-3-0 3.2.3-1 ii libpam0g 1.1.3-7 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxklavier16 5.2.1-1 ii libxxf86vm11:1.1.1-2 Versions of packages gnome-screensaver recommends: ii gnome-power-manager 3.2.1-2 ii libpam-gnome-keyring 3.2.2-2 gnome-screensaver suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662671: Not obvious how to enable extensions once installed
On Tue, Mar 06, 2012 at 02:43:48AM +0100, Michael Biebl wrote: > On 06.03.2012 02:36, Josh Triplett wrote: > > On Tue, Mar 06, 2012 at 12:26:06AM +0100, Michael Biebl wrote: > >> Am 06.03.2012 00:06, schrieb Josh Triplett: > >>> On Tue, Mar 06, 2012 at 12:01:55AM +0100, Michael Biebl wrote: > >> > But gnome-tweak-tools is probably the most convenient way. > >>> > >>> Sounds like "Recommends" then. > >> > >> fine with me. > > > > I just installed gnome-tweak-tool, and attempted to use it to install an > > extension. It doesn't seem to recognize the extensions shipped in > > gnome-shell-extensions; I couldn't convince it to open them. Could you > > provide a rough explanation of how to enable and configure a shell > > extension using gnome-tweak-tool? > > If you have gnome-shell-extensions installed, restart your shell (as > mentioned). This can be done by restarting your complete desktop session > or "ALT+F2 r". > Then, in gnome-tweak-tool go to "Shell Extensions" and enable the > extensions you like. I thought I had restarted the shell, but evidently I had not, since after I did so the extensions showed up. Sorry for the extra trouble. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#579028: pbuilder: installs untrusted packages without asking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, Mar 06, 2012 at 02:29:25AM +0100, Simon Ruderich wrote: > I tested it with the official Debian repository, signed and > unsigned local repositories and it works fine for me. But I'm > only a "normal" pbuilder user, so I might have missed something. > Please test the patch. Just noticed that I overlooked the last few messages. My patch doesn't fix these usecases, disabling the check works though. Regards, Simon - -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJPVW99AAoJEJL+/bfkTDL50a0P/1iJ2tjgTCBxgnj7I3F2a0Dy LkfUalxy+mgC1y3cFFhHofVAZWjzFY8OniAPCcQdv2hRj7OAGwvwTKpk2gcwhDeH MLti5cmdF8W2+AFRmym/e63mc0HOi4EEhiHlV6zuP+Hr366dosvHuR1ZYWPiOmPe MTc3hbCv0KBWrJeYe8AsKZP7FHSn0+T3/pvPKIfG+P5NweGQOMt/hmdmptHO88Hw BlB1bbvKX1C78hyOQnWEOZhZljWLF6bttGvqpZPzyssII8JlyunLOGNixy3otzZj fMDhv0p0OUNoIfbZL1WybqOk1vuQ5YyeIUC+7KDHTzK5EJmwbRX8UOfMhJ0mZZgI K5M17d+po3Cbtyw/asJUMfVJ7ontdKzK4FahojoICJh0ybaJ1i5GHscgCQMOnYtb cPxsyS3SArArI8q2wk1JuBk0+DSk7Rx5UfxGpVxNvCY6IbSMieSc/Yakct1+vbEn K0o1nRg9G4IZnnppDrchLdIF8gJB5uynS5hERiIQzsmDMUOr5+YpWY3ujpkYD/Vd gWEVaNz/Tg6T6DLJToU/zy4BpnGiNJWY9D12fA1w1ty/lI4ZrjHp7LMkYO2f0gC1 PyNEw6Xe4XVa8aEdwWo4iSPOypl/eGVvzpvX35KWMAgR2EK/uo84Wv8OpPWF76pm +YVcWXbHzENONikzyTsl =atNi -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662723: ls: -F (--indicator-style=classify) affects on symbolic link dereference
On Tue, Mar 06, 2012 at 03:50:34AM +0400, sergio wrote: indicator-style mast not affect on dereference. % /bin/ls -l /var/run lrwxrwxrwx 1 root root 4 May 15 2011 /var/run -> /run % /bin/ls /var/run acpid.pid dhclient.eth0.pid lock rsyslogd.pid sshd % /bin/ls -F /var/run /var/run@ Can you be more specific about what you're looking for? Mike Stone -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662671: Not obvious how to enable extensions once installed
On 06.03.2012 02:36, Josh Triplett wrote: > On Tue, Mar 06, 2012 at 12:26:06AM +0100, Michael Biebl wrote: >> Am 06.03.2012 00:06, schrieb Josh Triplett: >>> On Tue, Mar 06, 2012 at 12:01:55AM +0100, Michael Biebl wrote: >> But gnome-tweak-tools is probably the most convenient way. >>> >>> Sounds like "Recommends" then. >> >> fine with me. > > I just installed gnome-tweak-tool, and attempted to use it to install an > extension. It doesn't seem to recognize the extensions shipped in > gnome-shell-extensions; I couldn't convince it to open them. Could you > provide a rough explanation of how to enable and configure a shell > extension using gnome-tweak-tool? If you have gnome-shell-extensions installed, restart your shell (as mentioned). This can be done by restarting your complete desktop session or "ALT+F2 r". Then, in gnome-tweak-tool go to "Shell Extensions" and enable the extensions you like. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#662671: Not obvious how to enable extensions once installed
On Tue, Mar 06, 2012 at 12:26:06AM +0100, Michael Biebl wrote: > Am 06.03.2012 00:06, schrieb Josh Triplett: > >On Tue, Mar 06, 2012 at 12:01:55AM +0100, Michael Biebl wrote: > > >>But gnome-tweak-tools is probably the most convenient way. > > > >Sounds like "Recommends" then. > > fine with me. I just installed gnome-tweak-tool, and attempted to use it to install an extension. It doesn't seem to recognize the extensions shipped in gnome-shell-extensions; I couldn't convince it to open them. Could you provide a rough explanation of how to enable and configure a shell extension using gnome-tweak-tool? - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661511: tpb/0.6.4-8 ftbfs with clang
Howdy Prach, I took the liberty of attempting to build your package with clang (rather then gcc) as the compiler. The package appeard to fail in my sbuild chroot, so I double checked (since the error was not clear it was because of clang), and found that using clang does, in fact, cause the configure script to fail. Here's the error: | checking for xosd-config... /usr/bin/xosd-config | checking for libxosd... yes | checking for version of libxosd... < 0.7.0, failed | *** The version of XOSD library installed is not 0.7.0 or | *** above, make sure the correct version is installed. And a quick tripple check: | [tag@leliel:~/reviews/debian/tpb-0.6.4][08:22 PM]$ CC=gcc ./configure >/dev/null | [tag@leliel:~/reviews/debian/tpb-0.6.4][08:26 PM]$ echo $? | 0 | [tag@leliel:~/reviews/debian/tpb-0.6.4][08:26 PM]$ CC=clang ./configure >/dev/null | [tag@leliel:~/reviews/debian/tpb-0.6.4][08:26 PM]$ echo $? | 1 Since clang is not a supported buildd compiler, this is not critical to fix. Something to send upstream, though. Thanks for helping make Debian better, Paul signature.asc Description: Digital signature
Bug#579028: pbuilder: installs untrusted packages without asking
Package: pbuilder Version: 0.206 Tags: patch Followup-For: Bug #579028 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, The attached patch changes the defaults to always enforce signed repositories and aborts if an untrusted/manipulated package is installed. It adds the new option --keyring (APTKEYRINGS) to add additional keyrings, which are then used to verify the (local) signed repositories. This way no untrusted packages can be installed. To still allow untrusted/unsigned repositories - they are a very bad idea and allow remote attackers performing a MITM to take over the system, including all built packages - the new option - --allow-untrusted (ALLOWUNTRUSTED) was added. I tested it with the official Debian repository, signed and unsigned local repositories and it works fine for me. But I'm only a "normal" pbuilder user, so I might have missed something. Please test the patch. I haven't tested it with cdebootstrap, but it should work as well. The old PBUILDERSATISFYDEPENDSOPT --check-key option was deprecated and is no longer used (it emits a warning now) as validation is the default now. The patch also contains documentation updates for the new options/variables and updates for the NEWS file describing the necessary changes to continue using untrusted packages (but please don't do that - especially as a Debian developer). Please have a look and include the patch as soon as possible to fix this security issue. Regards, Simon - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pbuilder depends on: ii cdebootstrap 0.5.8+b1 ii coreutils 8.13-3 ii debconf [debconf-2.0] 1.5.41 ii debianutils4.2.1 ii debootstrap1.0.38 ii dpkg-dev 1.16.1.2 ii wget 1.13.4-2 Versions of packages pbuilder recommends: pn devscripts 2.11.4 pn fakeroot1.18.2-1 pn sudo Versions of packages pbuilder suggests: pn cowdancer pn gdebi-core pn pbuilder-uml - -- debconf information excluded -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPVWhvAAoJEJL+/bfkTDL5ivAP/iayE8NRQnyk2HW8R+NiRXU3 uavLilwwpmEZyuciu8GxMQIAhT9HYd/DlkhF9I+yBSd30TO3fl0xW7YV9SaIZ+bv IPwnZbHri4KfeV9Zob/gd2jrT9A2QCoFRW0ny4XNCK3NvtWH5KuH+TG2Mq5CQqdN j4VJ3+76oJcbQbU7AUYXfvKDAsEb7gX+VwTEFLS4GrPkni/FIQJ8HHJhlTscyuCD gQANCoRFZHVSMaas3xqi9KYFKgVS4BZ5Z/9FZuLeY5kWBfcbnIhQloVOWTQZIMRI PhnqP1g62XlPu71K3a/Y2RMAcy3Gs6sUbW4OianIr2iskCndejih/MCb+3LmBFCg Ekxi/CcJGrc7a0pV57Qs8Iwkm1siRZZUxcp4xdD3mo9iayoOt4sfFyrvBCYryilQ 7JKpQc3iNoV3EQql6KBu5G+GmFFWHmokpLvVY27n8LgkV2YSb2wrgxqXPfxcYHj7 0j/y2MFw+HOX/d5YSESMLxn9aiZBi7CkMtlMemzqizxlNlL/+OOZiDsi4vdH8L/j Y0c2i9efjNeooc0/B9wASu/Ck8SWV8wW1EcfTag0p9Rp0avy4hoQUmG+MtgQsV0l MQuWWysyxeJFX4Z8ooau82L6sIGC0L073JH6Y/C7uTOz9gKt+e5tV3fnU+pkWpqH oF3CcmlykKX4SYzhUI/e =6EPj -END PGP SIGNATURE- >From cadc48fb599d436577a6efedc7f25e175652a3a1 Mon Sep 17 00:00:00 2001 Message-Id: From: Simon Ruderich Date: Tue, 6 Mar 2012 02:00:48 +0100 Subject: [PATCH] Enforce valid signed repositories by default. --- debian/NEWS | 19 ++ debian/pbuilder-test/00_prepinstall |2 +- pbuilder-checkparams| 18 + pbuilder-createbuildenv |5 pbuilder-satisfydepends-aptitude|2 +- pbuilder-satisfydepends-checkparams | 19 + pbuilder-updatebuildenv |6 + pbuilder.8 | 20 ++- pbuilderrc | 23 + pbuilderrc.5| 36 ++ 10 files changed, 124 insertions(+), 26 deletions(-) diff --git a/debian/NEWS b/debian/NEWS index 6d144b9..80d36e9 100644 --- a/debian/NEWS +++ b/debian/NEWS @@ -1,3 +1,22 @@ +pbuilder (0.207) unstable; urgency=low + + The default configuration will now only install trusted packages. This + prevents building packages with manipulated sources or a system compromise + due to a man-in-the-middle attack. + + However this also prevents installing packages from unsigned repositories by + default. + + If you really want to continue using unsigned repositories, you have to set + ALLOWUNTRUSTED=yes in your .pbuilderrc or use the --allow-untrusted option. + But if possible use a signed repository and set the used keys with the new + --keyring option (can be passed multiple times). + + Due to this change the PBUILDERSATISFYDEPENDSOPT option --check-key is no + longer necessary and thus deprecated. + + -- Simon Ruderich Tue, 06 Mar 2012 02:02:38 +0100 + pbuilder (0.197) unstable; urgency=low The default configuration will now enable ccache. To
Bug#662573: Changes from longterm 2.6.32.58
On Mon, 2012-03-05 at 06:11 +, Ben Hutchings wrote: [...] > - autofs: work around unhappy compat problem on x86-64 > - Fix autofs compile without CONFIG_COMPAT > - compat: fix compile breakage on s390 > > Fixes compatibility of amd64 kernel with i386 userland for autofs > protocol version 5. [...] Unfortunately these are reported to result in a build failure for ia64 and s390. Further changes will be required. Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. signature.asc Description: This is a digitally signed message part
Bug#592204: nvidia-vdpau-driver: Segfault on VDPAU using apps that call XCloseDisplay
21.02.2012 12:55, Andreas Beckmann kirjoitti:
> On 2011-09-15 16:20, Andreas Beckmann wrote:
>> On 2010-08-25 03:33, Andreas Beckmann wrote:
>>> On Sunday, 8. August 2010 09:06:37 Andres Mejia wrote:
For apps such as xbmc or mplayer that use vdpau for video output, calling
XCloseDisplay results in a segfault. Simple test would be to run
>>
>>> I could reproduce this with mplayer from Debian (but not the one from
>>> debian-multimedia.org) and driver 195.36.31. Stacktrace looked like this:
>>
>> I just tried again, but I could no longer reproduce this with libvdpau1
>> 0.4.1-2 (testing), 0.4.1-3 (unstable, should have a fix for this issue)
>> or 0.4-1 (snapshot.d.o, probably the version I used to reproduce this
>> last year) and mplayer from squeeze and wheezy.
>>
>> But then, over the last year a lot has changed: X, mplayer, libs, nvidia
>> driver ...
>>
>> Andres, can you still reproduce this?
>
> Ping. Any test result?
> If noone can still reproduce this I'll close this bug as fixed in 4 weeks.
Testcase attached. Also, this is a libvdpau bug, not a
nvidia-vdpau-driver one. It crashes with all drivers, whether VDPAU is
supported or not (as the bug is caused by the probing code in libvdpau).
--
Anssi Hannula
/*
* Testcase for Debian bug #592204.
* This will trigger a segmentation fault.
*
* Written by Anssi Hannula
*
* gcc -o vdpau-debian-592204 vdpau-debian-592204.c -lX11 -ldl
*/
#include
#include
#include
#include
#include
int main() {
Display *dpy;
void *libvdpau;
VdpDeviceCreateX11 *vdp_create;
VdpGetProcAddress *vdp_get_proc_address;
VdpDeviceDestroy *vdp_destroy;
char *error;
VdpStatus status;
VdpDevice device;
dpy = XOpenDisplay(NULL);
if (!dpy) {
fprintf(stderr, "Unable to open display.");
return EXIT_FAILURE;
}
libvdpau = dlopen("libvdpau.so.1", RTLD_LAZY);
if (!libvdpau) {
fprintf(stderr, "%s\n", dlerror());
return EXIT_FAILURE;
}
*(void **) (&vdp_create) = dlsym(libvdpau, "vdp_device_create_x11");
if ((error = dlerror()) != NULL) {
fprintf(stderr, "%s\n", error);
return EXIT_FAILURE;
}
status = vdp_create(dpy, DefaultScreen(dpy), &device, &vdp_get_proc_address);
if (status == VDP_STATUS_OK) {
/* We don't actually have use for it, so destroy it immediately
if it was created successfully. Since the segfault is caused
by the probing code in libvdpau, it will happen regardless of
whther device creation succeeded or not. */
status = vdp_get_proc_address(device, VDP_FUNC_ID_DEVICE_DESTROY, (void*)&vdp_destroy);
if (status != VDP_STATUS_OK) {
fprintf(stderr, "Unable to get VdpDeviceDestroy.");
return EXIT_FAILURE;
}
status = vdp_destroy(device);
if (status != VDP_STATUS_OK) {
fprintf(stderr, "Unable to destroy VdpDevice.");
return EXIT_FAILURE;
}
} else {
puts("VDPAU device not created - it doesn't matter for this testcase.");
}
if (dlclose(libvdpau)) {
fprintf(stderr, "%s\n", dlerror());
return EXIT_FAILURE;
}
puts("Calling XCloseDisplay() - this will segfault.");
XCloseDisplay(dpy);
}
Bug#662632: RFS: libaio-ocaml/1.0~rc1
Benoît Knecht writes: > retitle 662632 RFS: libaio-ocaml/1.0~rc1 [ITP] -- OCaml bindings for libaio > tags 662632 moreinfo > thanks > > Hi Goswin, > > Goswin von Brederlow wrote: >> I am looking for a sponsor for my package "libaio-ocaml" >> >> * Package name: libaio-ocaml >>Version : 1.0~rc1 >>Upstream Author : Goswin von Brederlow >> * URL : http://forge.ocamlcore.org/projects/libaio-ocaml/ >>Vcs-Git : >> git://anonscm.debian.org/pkg-ocaml-maint/packages/libaio-ocaml.git >>Vcs-Browser : >> http://anonscm.debian.org/git/pkg-ocaml-maint/packages/libaio-ocaml.git > > Vcs-Browser should link to something browsable, like a gitweb or > something, if it exists. Oh, I copied that from the browsable webpage itself not realizing that it was a raw view. Fixed. Going to upload 1.0~rc2 after this mail. http://anonscm.debian.org/gitweb/?p=pkg-ocaml-maint/packages/libaio-ocaml.git >> * License : LGPL-2.1+ and link execpetion >>Section : ocaml >> >> It builds those binary packages: >> >> libaio-ocaml - OCaml bindings for libaio (Linux kernel AIO access library) >> libaio-ocaml-dev - OCaml bindings for libaio (Linux kernel AIO access >> library) > > You should open an ITP bug and close it in the debian/changelog [1]. Given that I am upstream, currently the only user of it and the package is hosted in the ocaml maintainers git I do not think there is a risk of anyone else packaging this as well. Didn't feel like writing an ITP just to raise the ITP count from 1120 to 1121 for a few days when the packaging is done and just pending cosmetic changes. But if that is stopping sponsorship I can certainly write one. >> To access further information about this package, please visit the following >> URL: >> >> http://mentors.debian.net/package/libaio-ocaml > > This page shows a few issues already that you should also fix: no watch > file, duplicate short description, and no debian version (i.e. package > is native). I've already fixed the duplicate short description in git, the only info I consider valid problem there. The package is native because I am both maintainer and upstream author. Does a watch file make sense for a native package? I've tried for a while to maintain the package with split upstream and debian git repositories but it just causes so much extra work for no real benefit. Every upstream change needs to be commited, pulled to the upstream branch of the debian git, merged into master, build, test, repeat. Besides being extra work for nothing it also seriously disrupts my workflow and prevents the use of for example "git commit --amend". You can no longer just play with the source till it works and then commit in an orderly fashion. > [1] http://www.debian.org/devel/wnpp/ > > Cheers, > > -- > Benoît Knecht MfG Goswin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662727: gdm3: dmz-cursor-theme BUG -> mouse cursor still "black" instead of "white" in Gnome3
Package: gdm3 Version: 3.0.4-4 Severity: important Dear Maintainer, I've installed dmz-cursor-theme and and changed in: # update-alternatives --config x-cursor-theme There are 2 choices for the alternative x-cursor-theme (providing /usr/share/icons/default/index.theme). SelectionPath Priority Status 0/usr/share/icons/DMZ-White/cursor.theme 90auto mode 1/usr/share/icons/DMZ-Black/cursor.theme 30manual mode * 2/usr/share/icons/DMZ-White/cursor.theme 90manual mode but the mouse cursor has still a black colour in Gnome3. If I open an application, for example iceweasel browser, then the mouse cursor changes to white. If I go back to the Gnome Desktop then it's black again. greetings Piotr -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice 0.6.15-4 ii adduser 3.113+nmu1 ii dconf-gsettings-backend 0.10.0-3 ii debconf [debconf-2.0] 1.5.41 ii gconf2 3.2.3-3 ii gnome-session [x-session-manager] 3.2.1-1 ii gnome-session-bin 3.2.1-1 ii gnome-session-fallback [x-session-manager] 3.2.1-1 ii gnome-terminal [x-terminal-emulator]3.2.1-2 ii gsettings-desktop-schemas 3.2.0-2 ii libaccountsservice0 0.6.15-4 ii libatk1.0-0 2.2.0-2 ii libattr11:2.4.46-5 ii libaudit0 1:1.7.18-1.1 ii libc6 2.13-26 ii libcairo-gobject2 1.10.2-6.2 ii libcairo2 1.10.2-6.2 ii libcanberra-gtk3-0 0.28-3 ii libcanberra00.28-3 ii libdbus-1-3 1.4.18-1 ii libdbus-glib-1-20.98-1 ii libfontconfig1 2.8.0-3.1 ii libfreetype62.4.8-1 ii libgconf2-4 3.2.3-3 ii libgdk-pixbuf2.0-0 2.24.1-1 ii libglib2.0-02.30.2-6 ii libglib2.0-bin 2.30.2-6 ii libgtk-3-0 3.2.3-1 ii libpam-modules 1.1.3-7 ii libpam-runtime 1.1.3-7 ii libpam0g1.1.3-7 ii libpango1.0-0 1.29.4-2 ii librsvg2-common 2.34.2-2 ii libselinux1 2.1.0-4.1 ii libupower-glib1 0.9.15-2 ii libwrap07.6.q-23 ii libx11-62:1.4.4-4 ii libxau6 1:1.0.6-4 ii libxdmcp6 1:1.1.0-4 ii libxklavier16 5.2.1-1 ii libxrandr2 2:1.3.2-2 ii lsb-base3.2-28.1 ii metacity [x-window-manager] 1:2.34.1-2 ii policykit-1-gnome 0.105-2 ii upower 0.9.15-2 ii xterm [x-terminal-emulator] 276-2 Versions of packages gdm3 recommends: ii at-spi 1.32.0-1 ii desktop-base 6.0.7 ii gnome-icon-theme 3.2.1.2-1 ii gnome-power-manager3.2.1-2 ii gnome-settings-daemon 3.2.2-2 ii x11-xkb-utils 7.6+4 ii xserver-xephyr 2:1.11.3.901-2 ii xserver-xorg 1:7.6+11 ii zenity 3.2.0-1 Versions of packages gdm3 suggests: ii gnome-mag ii gnome-orca ii gok ii libpam-gnome-keyring 3.2.2-2 ii metacity 1:2.34.1-2 -- Configuration Files: /etc/pam.d/gdm3 changed: authrequisite pam_nologin.so @include common-auth authoptionalpam_gnome_keyring.so @include common-account session requiredpam_limits.so session requiredpam_env.so readenv=1 session requiredpam_env.so readenv=1 envfile=/etc/default/locale @include common-session session optionalpam_gnome_keyring.so auto_start @include common-password -- debconf information: * shared/default-x-display-manager: gdm3 gdm3/daemon_name: /usr/sbin/gdm3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.
Bug#662726: gitpkg: proposed new patch-export script
Package: gitpkg
Version: 0.21
Severity: wishlist
Hi Ron;
Here is the script we discussed on IRC to allow selective export of
git commits as quilt patches, either interactively or as part of a git
hook. The advantage over the existing scheme is that this supports
patches that are already merged into to the packaging/integration
branch. Probably it is a bit rough around the edges (e.g. the man
page is a bit user-hostile), but hopefully we can use this bug to
track discussion and whip it into shape.
David
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gitpkg depends on:
ii dpkg-dev 1.16.1.2
ii git 1:1.7.9.1-1
gitpkg recommends no packages.
Versions of packages gitpkg suggests:
ii devscripts 2.11.4
-- no debconf information
>From 78ed58fee095218ed7683ac121177c66ae9c0a57 Mon Sep 17 00:00:00 2001
From: David Bremner
Date: Mon, 5 Mar 2012 12:17:46 -0400
Subject: [PATCH] git-debpatch: select commits to be exported as quilt patches
This script allows the user to mark commits for export as
quilt-patches in debian/patches. gitpkg support is provided via
hooks/quilt-patches-deb-export-hook.
---
git-debpatch| 127 +++
git-debpatch.1 | 83 +++
gitpkg.1|3 +-
hooks/quilt-patches-deb-export-hook |3 +
4 files changed, 215 insertions(+), 1 deletions(-)
create mode 100755 git-debpatch
create mode 100644 git-debpatch.1
diff --git a/git-debpatch b/git-debpatch
new file mode 100755
index 000..6a20fc1
--- /dev/null
+++ b/git-debpatch
@@ -0,0 +1,127 @@
+#!/bin/bash
+
+GN="git notes --ref debpatch"
+patch_dir=debian/patches
+
+# get_field ref Field
+#
+function get_field() {
+${GN} show $1 2>/dev/null | sed -n "s/^$2: \(.*\)$/\1/p"
+}
+
+# set_field ref Field Val
+function set_field() {
+other_fields=$(${GN} show $1 2>/dev/null | grep -v "^$2: ")
+printf "$2: $3\n$other_fields" | ${GN} add -f -F- $1 2>/dev/null
+}
+
+# remove_field ref Field
+function remove_field() {
+other_fields=$(${GN} show $1 2>/dev/null | grep -v "^$2: ")
+if [ -n "$other_fields" ] ; then
+ printf "$other_fields" | ${GN} add -f -F- 1>/dev/null
+else
+ $GN remove $1 2>/dev/null
+fi
+}
+
+function is_exportable() {
+[ $(get_field $1 Export)x = "truex" ]
+}
+
+function export_one_patch() {
+if [ -f $patch_dir/series ]; then
+ count=$(wc -l "$patch_dir/series" | cut -f1 -d' ')
+else
+ mkdir -p "$patch_dir" || exit 1
+ echo "# exported from git by git-debpatch" > "$patch_dir/series"
+ count=1
+fi
+
+name=$(git format-patch --start-number $count -1 -o "$patch_dir" $1)
+echo "$name" | sed -e "s,$patch_dir/,,g" -e 's, ,\n,g' >> "$patch_dir/series"
+}
+
+function print_status() {
+if is_exportable $1; then
+ printf "E\t"
+else
+ printf "\t"
+fi
+printf "%7.7s\t" $1
+printf "%0.30s" "$(git --no-pager log --format="%s" -1 $1)"
+printf "\t%s\n" $(get_field $1 Forwarded)
+}
+
+function do_one_commit() {
+case $1 in
+ export)
+ set_field $2 Export true
+ ;;
+ noexport)
+ remove_field $2 Export
+ ;;
+ forwarded)
+ set_field $2 Forwarded $3
+ ;;
+ noforwarded)
+ remove_field $2 Forwarded
+ ;;
+ status)
+ print_status $2
+ ;;
+ toquilt)
+ if is_exportable $2; then
+ export_one_patch $2
+ fi
+ ;;
+ *)
+ echo "Unknown operation $1"
+ exit 1;
+esac
+}
+
+
+case $1 in
+fetch)
+ remote=${2-origin}
+ git fetch $remote refs/notes/debpatch:refs/notes/remotes/$remote/debpatch
+ exit 0;
+ ;;
+merge)
+ remote=${2-origin}
+ ${GN} merge --strategy=cat_sort_uniq refs/notes/remotes/$remote/debpatch
+ exit 0;
+ ;;
+pull)
+ git debpatch fetch $2 && git debpatch merge $2
+ exit $?
+ ;;
+push)
+ remote=${2-origin}
+ git push $remote refs/notes/debpatch:refs/notes/debpatch
+ exit 0;
+ ;;
+status|export|noexport|toquilt|forwarded)
+ if [ -z $2 ]; then
+ echo "$1 needs a ref or a range"
+ exit 1
+ fi
+ ;;
+*)
+ echo "Unknown operation $1"
+ exit 1;
+esac
+
+case $(git rev-parse $2 | wc -l) in
+1)
+ do_one_commit $1 $2 $3
+ ;;
+2)
+ git rev-list --ancestry-path --reverse $2 | \
+ while read hash ; do do_one_commit $1 $hash $3; done
+ ;;
+*)
+ echo "Internal error."
+ exit 1;
+esac
diff --git a/git-debpatch.1 b/git-debpatch.1
new file mode 100644
index 000..5af4af3
--- /dev/null
+++ b/git-debpatch.1
@@ -0,0 +1,83 @@
+.\" Hey, EMACS: -*- nroff -*-
+.\" First parameter, NAME, should be all caps
+.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
+.\" other parameters are allowed: see man(7), man(1)
+.TH GIT-DEBPATCH 1 "March 5, 2012"
+.\" Pl
Bug#650536: update!
On Mon, Mar 05, 2012 at 11:29:46AM +0100, Niels Thykier wrote: > On 2012-03-05 04:47, Kees Cook wrote: > > - It requires the lastest dpkg-dev (still in experimental) to get > > the dpkg-buildflags that supports --query-features. > > Unfortunately I see two issues here. First, we have been asked to avoid > the unconditional dpkg-dev dependency (see #626476). Perhaps we can use > libdpkg-perl as a fall-back in this case (like we do in > collection/unpacked). Hrm, well, as long as dpkg-buildflags is the right one, I don't care what the Depends say. ;) > The second problem is that the given version of dpkg-dev is not in > stable[1] and (as I recall) the backport FTP masters were not too happy > with the last backport. > > [1] It is not in unstable either, but at this point I am more concerned > with getting it in stable. > Right -- though I have no way around this. All the pieces needed for these checks come from the new dpkg-buildflags. Perhaps the hardening check can be disabled for the backport, since it's rather meaningless for stable anyway? > > - The hardening checker checks if it is running as part of the > > internal test suite, so that it is disabled for all tests except > > its own, since the bulk of the internal tests do not build with > > hardening flags, and only for i386 and amd64 since there isn't > > a sane way to generate the "tags" file on the fly for a test. > > > > To be honest I do not like the idea of Lintian checks/collections > behaving differently during tests. > I suppose we could a make """sane way to generate the "tags" file""". > We already have several hooks in the test suite, adding another one > should not be a great issue. I could write a hook the generate the tags file on the fly, but that only handles the per-arch limitation of the internal test for the hardening checker. > Though, we only want hardening tags emitted in a selected few tests... This was the big problem. I spent a lot of time trying to see how bad it would be to fix every build in the testsuite to DTRT with respect to dpkg-buildflags, but it was a losing battle. Or, at least, a tedious battle. Ultimately I decided it was better to just have the hardening checker disable itself in the face of the other tests. I'm open to ideas for this part, but a lot of the test builds don't pass all the needed flags, or hard code flags, etc etc. Changing the compat level worked for many of the failures, but not all and left about 30 that still needed to be changed by hand. If it's important to do this strictly correct, I can, it'll just take me a while. -Kees -- Kees Cook@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662725: cgal: CGAL 4.0 Beta 1 Released
Package: cgal Severity: wishlist A beta for the upcoming release of CGAL has been released. Though it's a beta, the new release will be released under the terms of the LGPLv3+ and GPLv3+. It would be worthwhile to prepare for the upcoming release by uploading to experimental to let others start testing with the new release. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630575: Icelandic Dvorak keyboard layout isn't there either
Ævar Arnfjörð Bjarmason, le Mon 05 Mar 2012 18:34:47 +0100, a écrit : > On Mon, Mar 5, 2012 at 12:55, Samuel Thibault wrote: > > Ævar Arnfjörð Bjarmason, le Mon 05 Mar 2012 12:36:40 +0100, a écrit : > >> I must say I find this annoying as well, the Icelandic Dvorak Keyboard > >> layout is also missing, so my installation of Debian always goes like > >> this: > >> > >> 1. I choose "Dvorak" > > > > Why not just choosing Icelandic? (which is already selected by default) > > > >> 2. I can't type my real name when I create a user, I type "whatever" > >> instead > >> 3. I'm limited in the passwords I can pick > > > > You'd then be able to type your real name and not be limited. > > Because that's Icelandic *qwerty*. Which is completely different than > Icelandic Dvorak. It is understood that it's completely different, just like all dvorak layouts. > If I picked that it would take me 2-3x as long to install the system > since every time I wanted to type something I'd have to hunt-and-peck > type instead of touch-type. That much? The d-i team assumed that anybody who knows a dvorak layout would know the traditional layout too, even if a bit less trained to it. > To see what that's like, if you happen to use QWERTY, try installing > the system with a Dvorak keyboard. Which to our knowledge is far from comparable: there are way less dvorak keyboards on sale than qwerty keyboards. In the common shops in the countries I have visited, it's a 0 ratio. > > Experience showed they do. And that would carry a lot of translations, > > making d-i bigger and unusable in small platforms. > > This bug is really not about Dvorak, but about the d-i offering only > an arbitrary subset of the keyboard layout that a full Debian system > offers. Which is on purpose. As has been discussed at lengths on debian-boot, in a lot of cases showing all the choices is really just spurious. For the french layout for instance, there is a dozen variants, from which the average user will have no idea what to choose, while the "standard" one will just fit anybody who ever worked with any french keyboards. The subset is definitely *not* completely arbitrary, it is a careful selection. For cases that do matter, d-i does include the variants which can be useful, and only those that are known to be well-known in the area, e.g. Kurdish and Turkish F vs Q layout, or bulgarian phonetic layout. If the dvorak layout is really so much spread in Iceland that people really miss the choice, then it can be proposed for addition, but the debian-boot discussions ended up on not providing dvorak layouts, and the (US) "Dvorak" choice currently proposed is actually questioned. > E.g. it doesn't offer Colemak at all either which means that anyone > used to that layout would also have a really hard time installing the > system, even if they didn't need to type non-ASCII characters. Same answer as above: we believe that people who know Colemak are able to type with qwerty. > 1. That this couldn't be made to work from a UI point of view. > > I don't think this is true at all. The Ubuntu installer, which I > find much simpler than Debian's (even though I prefer Debian when > it comes to the end result) allows you to select all the keyboard > layouts you get on post-installation. Here's Debian's: > > CLI: http://i.imgur.com/zPSvv.png > GUI: http://i.imgur.com/TjoYU.png > > And Ubuntu's: > > http://i.imgur.com/CCsCw.png > > Ubuntu just selects the most common option, but allows you to > change it if you want to. The d-i could do the same thing with > another dialog box. Which is precisely what was initially done, and was rejected because there are a lot of just useless choices for a mere installation. > Even if all of this was hidden under some top-level "Other" box > users such as myself would be able to select it. That brings down to to point 2. > This is exactly how the timezone dialog works already, there's a > *lot* of timezones, and the d-i manages that complexity without > excluding some rare timezones and having users update > /etc/timezone after installation. Yes, because the user will usually know what to answer. In the case of keyboard layouts, they often don't. See the monster "Review of console-setup wrt D-I [very long]" thread, starting at http://lists.debian.org/debian-boot/2009/06/msg00759.html > 2. That the translations would get bigger > > I very much doubt that, Never doubt before seeing numbers. xkb-data's 39 .mo files amount to 2.2MiB (about 56KiB each). The translation of the d-i answers amounts to about 5KiB for each translation, ending up with about 2MiB saving, which is huge by d-i standards. BTW, dropping the actual non-standard layouts also brings pc105.ekmap from 1MiB down to 300KiB. Again a precious saving for d-i. > especially since most of the translations > of the descriptions are basically all repetitions, > i.e
Bug#662724: resolvconf: fail cp resolv.conf under /etc/resolvconf/run
Package: resolvconf Version: 1.64 Severity: serious Hello, Installing resolvconf (versioned 1.64) when creating a local chroot, fails to copy resolv.conf under /etc/resolvconf/run as the run directory does not exists when it is trying to copy the file. Chroot is created under QEmu, but here you have the error I get: root@polynomio:/# dpkg --configure -a Setting up resolvconf (1.64) ... /usr/bin/locale: Cannot set LC_CTYPE to default locale: No such file or directory /usr/bin/locale: Cannot set LC_MESSAGES to default locale: No such file or directory /usr/bin/locale: Cannot set LC_ALL to default locale: No such file or directory debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 75.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (This frontend requires a controlling tty.) debconf: falling back to frontend: Teletype Unsupported ioctl: cmd=0x80046601 /usr/bin/lsattr: Function not implemented While reading flags on /etc/resolv.conf /bin/cp: cannot create regular file `/etc/resolvconf/run/resolv.conf': No such file or directory dpkg: error processing resolvconf (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: resolvconf Kind regards -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660519: Re[2]: Bug#660519: RFS: manaplus/1.2.2.19
Thanks for review. manaplus updated to version 1.2.3.4 22 февраля 2012, 05:23 от Paul Wise : > Here is another review of manaplus: > > If you contact upstream as a result of this review, please point them > at these two pages: > > http://wiki.debian.org/UpstreamGuide > http://www.freedesktop.org/wiki/Games/Upstream I am upstream > > Did you intend for this to be maintained as part of the Debian games team? Now i not sure. For me now task add manaplus to debian, after we will see. > > Do you intend to package the servers for manaplus too? For now no, but in future yes. Now server not in state for packaging, need many work for adapt it to work from separate directories. Also it can work only in 32 bit version. Server from what it forked storing pointers in int and have some other 64 bit issues. > > All the servers appear to require a login to play, are there any I > could use for 'testing' the game without registering? Registration is simple, In game client need press register and enter login and password. I can create preregistered account but not sure what password i can put in public, because some one can change it after. > > Please consider wrapping debian/menu with one item per line. > > description= is not valid in debian/menu, you want longtitle= IIRC. Fixed. > > xz compression is better than bzip2, have you considered switching? > Personally I don't think the package is large enough to bother > switching from gzip though. for debian/* files i switched to gz, for tarball to xz. Look like this modes giving better compressing > > Some of the images were created in Inkscape or GIMP but there are no > source SVG or XCF images, that might be a GPL/DFSG violation. SVG image was not drawed for manaplus, but used same as in mana. I removed it For other one image i add xcf file, but sad it in 2.7 gimp format or like this. I also removed some themes because license GPL and i dont have response from author about sources. Other themes relicensed from GPL to CC-BY-SA. Other themes from data/graphics/gui is a bit modified theme from mana client/package data/themes/wood is theme from tmw package (branding for mana) tmw and mana now in debian and i think if it accepted, then this themes here can be accepted too. > > There is one pre-mixed, pre-encoded audio file, could you ask upstream > about how it was created? It based in one of ogg files from The Mana World sounds. I simple cut and add delay to one channel. I can include ogg file as source if need. Also in new version i add sounds from psiplus package converted to ogg and some renamed. Should i also include source wav files? > > In the upstream .desktop files, none of the language-specific Icon or > Name lines appear to be needed. Fixed > > You are installing the upstream PNG icon into the wrong location, it > should be /usr/share/pixmaps since none of the > /usr/share/icons/hicolor/*/apps/ dirs are for the same resolution as > the image. Please also install manaplus.svg into > /usr/share/icons/hicolor/scalable/apps/ and use python-scour to strip > down the installed image. I think fixed only without svg. > > The manaplus.svg file looks slightly different to manaplus.png and the > other files, it looks like that means the source SVG for manaplus.png > is missing and there is a GPL/DFSG violation. > > There is no need to install manaplusttest at all IMO since it does > nothing useful to users, please get upstream to disable that. If they > are not willing to do that, please at least remove the desktop file > for it. Manaplustest need for autocheck graphics settings/speed and add it to configuration. Desktop file removed. > > Please ask upstream to use fontconfig to find font files on Linux or > switch to a font rendering system that does that (such as SDL-Pango, > QuesoGLC). Then you will not need to use those symlinks, which are > fragile when font paths move around and are not portable between Linux > distros. I thinking about SDL-Pango not sure is it good to use it here. I cant use QuesoGLC because look like it only for opengl. But here exists software and two opengl backends. About fontconfig. Is possible with it create link to fonts with given names? > > Some of the upstream code has the wrong address for the FSF in the > license grant, please let them know about that. Fixed. > > Some of the copyright/license information is missing from > debian/copyright. Please audit every file, licensecheck --copyright > helps to find missed stuff though. I think fixed. > > You are missing a depends on x11-utils because the code uses xmessage > to display errors. Fixed > > I'm not sure if any of the errors contain untrusted network/other > input, but it is not a good idea to use the system() function for > anything other than constant commands. Please send upstream a patch to > use the exec family of functions, they are the only ones that are > guaranteed to be safe from arbitrary code execution in the face of > untrusted i
Bug#660420: Some Postscript printer drivers (Kyocera, Brother, maybe others) do not work anymore
I can also confirm that printing to a kyocera FS-1300D (as a postscript- printer) does not work any more. It does not print and hangs instead. This seems to be due to the postscript file generated from the PDF by ghostscript (called by the pdftops cups filter in my case). To test I tried to print my .bashrc: lp .bashrc 1. I redirected the final output a file and then sent to the printer by hand: printer does not print and hangs. 2. I modified cupsfilters.convs such that I get the PDF. I then used pdf2ps to generate the postscript file. Sent it to the printer: printer does not print and hangs. 3. I used pdftops from poppler-utils to generate the postscript file: Sent it to the printer and it works. 4. I used ps2ps on this postscript file: the generated one does not work and printer hangs. I called gs with -sDEVICE=pswrite to genrate a postscript file from the PDF: that one worked. The only way I may print using cups with a kyocera FS-1300D as postscript printer is by printing to a file as PDF and then using acroread to actually print it. Regards -- Wolfgang Walter Studentenwerk München Anstalt des öffentlichen Rechts -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639300: please build against unixodbc-dev instead of libiodbc2-dev
Hi Steve, (Hi Sebastian, this is a reply of the Debian bug #639300, which is about switching soprano from iODBC to unixODBC; you can find the whole log with the mentioned patch at [1].) [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639300 Alle martedì 6 marzo 2012, Steve Langasek ha scritto: > I'm surprised to say that after sitting on this bug for far too long, > it turns out that it's trivial to fix. Although it had been > reported that soprano would not work with unixodbc, once I actually > installed virtuoso, which the soprano test suite silently depends > on, I get the same results from test/virtuosobackendtest when built > against either iODBC or UnixODBC. I remember Sebastian Trueg (main soprano upstream) strongly recommending against using unixODBC (e.g. in [2], just last September), so I'm not sure whether this switch would break anything in the semantic desktop stack. (Disclaimer: I don't use Nepomuk myself.) Sebastian, what is the current status of soprano wrt unixODBC/iODBC? Which problems would result in using unixODBC? [2] http://trueg.wordpress.com/2011/09/22/about-strigi-soprano-virtuoso- clucene-and-libstreamanalyzer/ > I'm happy to upload this as an NMU if you would like. It's probably > worth an upload ASAP rather than waiting for 2.7.5+dfsg.1-1 to > migrate to testing, since it's hard to have usable ODBC drivers for > soprano until it's fixed. We're currently just started our KDE 4.7 transition, which includes also a soprano update from 2.6 to 2.7; if possible, I think IMHO it would be desiderable to wait for such dependency change, in case, after the transition is over (hopefully in two weeks, if everything goes fine). Would this timeframe suit you? -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#662709: git-gui: typo in git translation files
severity 662709 minor reassign 662709 git-gui 1:1.7.9-1 tags 662709 = upstream forwarded 662709 http://thread.gmane.org/gmane.comp.version-control.git/192289 quit Benjamin Kerensa wrote: > I noticed that a typo in the translation files for git exists in which > > "Generation succeded, but no keys found." > should be "succeeded" Good catch; thanks. Let's take this upstream. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662723: ls: -F (--indicator-style=classify) affects on symbolic link dereference
Package: coreutils Version: 8.13-3 Severity: normal indicator-style mast not affect on dereference. % /bin/ls -l /var/run lrwxrwxrwx 1 root root 4 May 15 2011 /var/run -> /run % /bin/ls /var/run acpid.pid dhclient.eth0.pid lock rsyslogd.pid sshd % /bin/ls -F /var/run /var/run@ -- System Information: Debian Release: wheezy/sid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662722: [lebiniou] Bug running two parallel biniou with different webcams
Package: lebiniou Version: 3.15-1 Severity: normal --- Please enter the report below this line. --- Bug running two parallel biniou with different webcams, the second one doesn't display the webcam image --- System information. --- Architecture: i386 Kernel: Linux 2.6.33-2-rt13.mk.5-io-rt-686-bigmem Debian Release: wheezy/sid 600 unstablemanu.kebab.free.fr 500 unstablewww.debian-multimedia.org 500 unstableftp.us.debian.org 500 stable dl.google.com --- Package information. --- Depends (Version) | Installed =-+-=== libasound2(>= 1.0.16) | 1.0.25-2 libc6(>= 2.7) | 2.13-27 libfftw3-3| 3.3-1 libglib2.0-0 (>= 2.24.0) | 2.30.2-6 libpulse0 (>= 0.99.1) | 1.1-3 libsdl-ttf2.0-0 | 2.0.11-1 libsdl1.2debian (>= 1.2.11) | 1.2.15-2 libswscale2(>= 4:0.8-1~) | 5:0.10-0.1 OR libswscale-extra-2 (>= 4:0.8-1~) | libxml2(>= 2.7.4) | 2.7.8.dfsg-7 zlib1g (>= 1:1.1.4) | 1:1.2.6.dfsg-2 ttf-freefont | 20100919-1 lebiniou-data (>= 3.10) | 3.10-1 Package's Recommends field is empty. Package's Suggests field is empty. signature.asc Description: This is a digitally signed message part.
Bug#662721: dash: Please enable hardening flags
Package: dash
Version: 0.5.7-3
Severity: important
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
Please consider enabling hardening flags which are a release goal
for wheezy. For more information please have a look at [1], [2]
and [3].
The attached patch enables the hardening flags and fixes a format
string vulnerability detected by -Wformat-security. -g and -O2 is
automatically set by dpkg-buildflags (noopt is respected). I've
been using the patched version for some time now and it works
fine for me.
To check if all flags were correctly enabled you can use
`hardening-check` from the hardening-includes package:
$ hardening-check /bin/dash
/bin/dash:
Position Independent Executable: no, normal executable!
Stack protected: yes
Fortify Source functions: yes (some protected functions found)
Read-only relocations: yes
Immediate binding: no not found!
(Position Independent Executable and Immediate binding is not
enabled by default.)
Regards,
Simon
[1]: https://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags
[2]: https://wiki.debian.org/HardeningWalkthrough
[3]: https://wiki.debian.org/Hardening
- -- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dash depends on:
ii debianutils 4.2.1
ii dpkg 1.16.1.2
ii libc62.13-27
dash recommends no packages.
dash suggests no packages.
- -- debconf information excluded
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJPVVVTAAoJEJL+/bfkTDL5GjQP/0RVCtUjx0QmqLtiLlAbYG8f
uX1t/SEBZ6VbpaUzJtoac3AN3h3x0ByE3T+tZlmC+CAdpP1EnSOskhtOCZF2qsNn
7HtaNSu6Mdi4etrbbKa4C9W/dJwA+sKwWDCyHuL+A8D8Pv1ObkQBnToRhQcCkB0m
yngp66vfQC739SiQjl5TyMAlrlvlxZDNiYI0Dc3rIHYFyjTLp35zckwidbB64gco
zdlfhp7RSwKhY6f1iSVr7TSZMSU7yMYjJET+Hzv9uPfGwih9G76/WZ4MjHv4QOcb
NAVYiv+TGGE737bSZG8+Zi9c+PR+OlQz0dXntscKn6U9GYzhdJBDK5FMv09E5abV
/+NS4uBrzCF5r+qcKxVQWoT2LET7pTkM5Bi+bojFOcAqi9jRXhik4rFuW6r/B6S+
aGvOvE78aZhhi3W7TkBQpTYYGHoZCn5BZsm0tdQMyxco8sljxTcDOQGtAeItWXb3
X61ICbSkHfzmMEcOqp0xG0fWoGrZg1HD9CSp5zOFw9pM5QLcLJav8QqPCcZ0iymK
CqSpYH0Y4q9Qw1c4DxEa76TKeVi8hX93DM39CI4Xx221AbJcMl1gkrtoPTC/pR/C
pVtg9LcPvw+LB8pvNXvQDGum48LBaad5Hh1UADcPZE8DS2wzvYwY1GOtgY1i3OJg
AjHQFW1H6IxB+15CtsPf
=tzaV
-END PGP SIGNATURE-
diff -u dash-0.5.7/debian/control dash-0.5.7/debian/control
--- dash-0.5.7/debian/control
+++ dash-0.5.7/debian/control
@@ -2,7 +2,7 @@
Section: shells
Priority: optional
Maintainer: Gerrit Pape
-Build-Depends: po-debconf
+Build-Depends: po-debconf, dpkg-dev (>= 1.16.1)
Standards-Version: 3.9.3.0
Homepage: http://gondor.apana.org.au/~herbert/dash/
Vcs-Git: http://smarden.org/git/dash.git/
diff -u dash-0.5.7/debian/rules dash-0.5.7/debian/rules
--- dash-0.5.7/debian/rules
+++ dash-0.5.7/debian/rules
@@ -1,7 +1,10 @@
#!/usr/bin/make -f
+DPKG_EXPORT_BUILDFLAGS = 1
+include /usr/share/dpkg/buildflags.mk
+
CC =gcc
-CFLAGS =-g -O2 -Wall
+CFLAGS +=-Wall
STRIP =strip
DEB_HOST_GNU_TYPE =$(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
only in patch2:
unchanged:
--- dash-0.5.7.orig/src/jobs.c
+++ dash-0.5.7/src/jobs.c
@@ -427,7 +427,7 @@
goto out;
#endif
}
- col = fmtstr(s, 32, strsignal(st));
+ col = fmtstr(s, 32, "%s", strsignal(st));
#ifdef WCOREDUMP
if (WCOREDUMP(status)) {
col += fmtstr(s + col, 16, " (core dumped)");
Bug#659083: RFS: xmoto -- 2D motocross platform game
Hi Ansgar,
On Sun, 26 Feb 2012 15:52:56 +0100, Ansgar Burchardt
wrote:
> You do not include the full license text for src/glext.h in the
> copyright information.
>
> Have the patches been forwarded upstream?
>
> You use debhelper compat level 9, so why don't you build-depend on
> debhelper (>= 9)?
>
> Please update at least config.{guess,sub}, see [1] for details, or just
> use dh-autoreconf (my personal preference).
>
> The source for bin/xmoto.bin seems to be missing, compare with
> upstream's SVN repository[2]. I have filed a bug[3] as it is also
> the case for the version currently inthe archive. Please ask upstream
> to include the source and ideally built xmoto.bin instead of including
> it, see also [4] for more details.
Thanks for the review, I'll update the package as appropriate once I have a
little more time (in a couple of weeks).
Regards,
Stephen
signature.asc
Description: PGP signature
Bug#653750: Is a `the' missing in `Some of conditions listed'?
--- a/spec.txt 2012-03-06 01:57:16.818428139 +0200 +++ b/spec.txt 2012-03-06 01:56:47.0 +0200 @@ -24885,7 +24885,7 @@ in a router or transport. 40.24 ACL conditions -Some of conditions listed in this section are available only when Exim is +Some of the conditions listed in this section are available only when Exim is compiled with the content-scanning extension. They are included here briefly for completeness. More detailed descriptions can be found in the discussion on content scanning in chapter 41. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662720: sozi: get "failed to load canberra-gtk-module" dialog when selecting the "Sozi" extension in inkscape
Package: sozi Version: 11.07-1 Severity: normal Tags: upstream Dear Maintainer, * What led up to the situation? I tried to select the "Sozi" extension in inkscape. * What exactly did you do (or not do) that was effective (or ineffective)? I installed libcanberra-gtk-module. * What was the outcome of this action? This prevented the problem from recurring * What outcome did you expect instead? This is what I expected! Or maybe I expect the libcanberra-gtk-module to be a recommends for sozi (and inkscape too, for that matter)...but I don't really have a good comprehension of the Debian Packaging Policy so...yeah. If nothing is done as a result of this (for instance if it is decided not to add libcanberra-gtk-module as a recommends for sozi) could I have a short explanation? If I don't get one, I will probably just read some documentation until I understand. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-rc5trillhelm+ (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sozi depends on: ii inkscape 0.48.1-2.1+b1 ii python 2.7.2-10 ii python-gtk2 2.24.0-3 sozi recommends no packages. sozi suggests no packages. -- no debconf information <>
Bug#662586: FTBFS
tags 662586 confirmed
thanks
Hi,
Thanks, I fixed.
This bug was revised next upload.
Best regards,
Nobuhiro
2012/3/5 Moritz Muehlenhoff :
> Package: mozc
> Version: 1.3.975.102-1
> Severity: serious
>
> Your package fails to build from source:
>
> RULE genproto_session_genproto_2
> out_linux/Release/obj/gen/proto_out/session/state.pb.h
> ['protoc', 'session/state.proto',
> '--cpp_out=/home/jmm/mozc-1.3.975.102/out_linux/Release/obj/gen/proto_out']
> TOUCH out_linux/Release/obj.target/session/genproto_session.stamp
> CXX(target) out_linux/Release/obj.target/client/client/client.o
> CXX(target) out_linux/Release/obj.target/client/client/server_launcher.o
> AR(target) out_linux/Release/obj.target/client/libclient.a
> CXX(target)
> out_linux/Release/obj.target/language_dependent_spec_japanese/languages/japanese/lang_dep_spec.o
> AR(target)
> out_linux/Release/obj.target/languages/japanese/liblanguage_dependent_spec_japanese.a
> ACTION gen_mozc_xml_gen_mozc_xml out_linux/Release/obj/gen/unix/ibus/mozc.xml
> TOUCH out_linux/Release/obj.target/unix/ibus/gen_mozc_xml.stamp
> CXX(target)
> out_linux/Release/obj.target/ibus_mozc_lib/unix/ibus/engine_registrar.o
> CXX(target)
> out_linux/Release/obj.target/ibus_mozc_lib/unix/ibus/key_translator.o
> CXX(target)
> out_linux/Release/obj.target/ibus_mozc_lib/unix/ibus/mozc_engine.o
> unix/ibus/mozc_engine.cc: In member function 'virtual void
> mozc::ibus::MozcEngine::PropertyActivate(IBusEngine*, const gchar*, guint)':
> unix/ibus/mozc_engine.cc:630:56: error: 'IBusProperty' has no member named
> 'sub_props'
> unix/ibus/mozc_engine.cc:631:43: error: 'IBusProperty' has no member named
> 'key'
> unix/ibus/mozc_engine.cc:650:61: error: 'IBusProperty' has no member named
> 'sub_props'
> unix/ibus/mozc_engine.cc:651:41: error: 'IBusProperty' has no member named
> 'key'
> unix/ibus/mozc_engine.cc: In member function 'void
> mozc::ibus::MozcEngine::UpdateCompositionModeIcon(IBusEngine*,
> mozc::commands::CompositionMode)':
> unix/ibus/mozc_engine.cc:1106:61: error: 'IBusProperty' has no member named
> 'sub_props'
> unix/ibus/mozc_engine.cc:1107:38: error: 'IBusProperty' has no member named
> 'key'
> make[2]: ***
> [out_linux/Release/obj.target/ibus_mozc_lib/unix/ibus/mozc_engine.o] Error 1
> make[2]: Leaving directory `/home/jmm/mozc-1.3.975.102'
> Traceback (most recent call last):
> File "build_mozc.py", line 1192, in
> main()
> File "build_mozc.py", line 1180, in main
> BuildMain(cmd_opts, cmd_args, original_directory_name)
> File "build_mozc.py", line 983, in BuildMain
> BuildOnLinux(options, targets, original_directory_name)
> File "build_mozc.py", line 781, in BuildOnLinux
> RunOrDie([make_command] + build_args + target_names)
> File "build_mozc.py", line 352, in RunOrDie
> '==']))
> __main__.RunOrDieError:
> ==
> ERROR: make -j1 MAKE_JOBS=1 BUILDTYPE=Release builddir_name=out_linux
> ibus_mozc scim_mozc scim_mozc_setup mozc_emacs_helper uim-mozc mozc_server
> mozc_tool
> ==
> make[1]: *** [override_dh_auto_build] Error 1
> make[1]: Leaving directory `/home/jmm/mozc-1.3.975.102'
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>
>
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662719: bluez must not stop during upgrade
Package: bluez Version: 4.98-3 Severity: normal Every time when I do dist-upgrade and there is a new version of bluez I loose mouse for tens minutes. It's not very big problem, because my keyboard is wired. But if you have bluetooth keyboard and some packages (after bluez stop) asks you about some configuration than you need wired keyboard. bluez must not stop during upgrade. I should restart after. -- System Information: Debian Release: wheezy/sid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662214: libnexus0-python: hardcoded dependency on python-all
* Jakub Wilk , 2012-03-04, 19:33: libnexus0-python currently depends on "python-all (>= 2.6.6-3~)". This: For the moment, this is excessive for the moment (you don't need _all_ supported Python versions). All, this will become insufficient once Python 2.7 stop being a supported version and the package is rebuilt. This should read: ... once Python 2.6 stops ... -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639300: please build against unixodbc-dev instead of libiodbc2-dev
tags 639300 patch
thanks
Dear maintainers,
I'm surprised to say that after sitting on this bug for far too long, it
turns out that it's trivial to fix. Although it had been reported that
soprano would not work with unixodbc, once I actually installed virtuoso,
which the soprano test suite silently depends on, I get the same results
from test/virtuosobackendtest when built against either iODBC or UnixODBC.
So I think the attached patch would be safe to apply to soprano, fixing this
longstanding issue.
I'm happy to upload this as an NMU if you would like. It's probably worth
an upload ASAP rather than waiting for 2.7.5+dfsg.1-1 to migrate to testing,
since it's hard to have usable ODBC drivers for soprano until it's fixed.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru soprano-2.7.5+dfsg.1/debian/changelog soprano-2.7.5+dfsg.1/debian/changelog
--- soprano-2.7.5+dfsg.1/debian/changelog 2012-03-04 20:55:08.0 +
+++ soprano-2.7.5+dfsg.1/debian/changelog 2012-03-05 23:49:53.0 +
@@ -1,3 +1,10 @@
+soprano (2.7.5+dfsg.1-1.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Build against unixodbc. Closes: #639300, LP: #901638.
+
+ -- Steve Langasek Mon, 05 Mar 2012 23:49:13 +
+
soprano (2.7.5+dfsg.1-1) unstable; urgency=low
* Team upload.
diff -Nru soprano-2.7.5+dfsg.1/debian/control soprano-2.7.5+dfsg.1/debian/control
--- soprano-2.7.5+dfsg.1/debian/control 2012-03-04 20:43:25.0 +
+++ soprano-2.7.5+dfsg.1/debian/control 2012-03-05 23:49:41.0 +
@@ -6,7 +6,7 @@
Build-Depends: debhelper (>= 7.4.15), cmake (>= 2.6.2), pkg-kde-tools (>= 0.12),
dpkg-dev (>= 1.15.5), libclucene-dev (>= 0.9.21b), libqt4-dev (>= 4.5.3),
libraptor1-dev (>= 1.4.16), librdf0-dev (>= 1.0.13),
- doxygen (>= 1.7.1), graphviz, libiodbc2-dev
+ doxygen (>= 1.7.1), graphviz, unixodbc-dev
Standards-Version: 3.9.2
Homepage: http://soprano.sourceforge.net
Vcs-Browser: http://git.debian.org/?p=pkg-kde/kde-req/soprano.git
diff -Nru soprano-2.7.5+dfsg.1/debian/patches/series soprano-2.7.5+dfsg.1/debian/patches/series
--- soprano-2.7.5+dfsg.1/debian/patches/series 2012-03-04 20:33:22.0 +
+++ soprano-2.7.5+dfsg.1/debian/patches/series 2012-03-05 23:49:41.0 +
@@ -2,3 +2,4 @@
disable_usr_lib_install_rpath.diff
doxyfile_generate_tagfile.diff
redland_raptor2_support.h
+unixodbc
diff -Nru soprano-2.7.5+dfsg.1/debian/patches/unixodbc soprano-2.7.5+dfsg.1/debian/patches/unixodbc
--- soprano-2.7.5+dfsg.1/debian/patches/unixodbc 1970-01-01 00:00:00.0 +
+++ soprano-2.7.5+dfsg.1/debian/patches/unixodbc 2012-03-05 23:49:41.0 +
@@ -0,0 +1,21 @@
+Description: Build against unixodbc
+ Add support for soprano to build against unixodbc. Thanks to some hints
+ from Alban Browaeys, I've found that the "virtuosobackendtest" test suite
+ works just as well with either unixodbc or iodbc, you just have to have
+ the virtuoso-opensource-6.1-bin package installed first to avoid
+ incomprehensible test failures.
+Author: Steve Langasek
+Bug-Debian: http://bugs.debian.org/639300
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/901638
+
+--- soprano-2.6.0+dfsg.1.orig/cmake/modules/FindIODBC.cmake
soprano-2.6.0+dfsg.1/cmake/modules/FindIODBC.cmake
+@@ -57,7 +57,7 @@ find_path(IODBC_INCLUDE_DIR sql.h
+ ${iodbc_INCLUDE_DIRS}
+ )
+
+-find_library(IODBC_LIBRARIES NAMES iodbc
++find_library(IODBC_LIBRARIES NAMES odbc iodbc
+ HINTS
+ ${iodbc_LIBRARY_DIRS}
+ )
Bug#662718: Suggests no longer existion libarchive1 package
Package: cpio Version: 2.11-7 Severity: minor libarchive had a soname bump from libarchive1 → libarchive12 Please adjust the Suggests accordingly if it still relevant. Cheers, Michael -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-17-generic (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cpio depends on: ii dpkg 1.16.1.2 ii install-info 4.13a.dfsg.1-8 ii libc6 2.13-27 cpio recommends no packages. Versions of packages cpio suggests: ii libarchive1 2.8.5-5 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
