Bug#737095: qdbus segfaults
> Almost everything :) qt5-default will not pull the rest of the new > stuff. > > But please, before upgrading anything, please send the output of > > dpkg -l qt5-dbus $ dpkg -l qt5-dbus dpkg-query: no packages found matching qt5-dbus $ dpkg -l qdbus-qt5 libqt5dbus5 ii libqt5dbus5:amd645.1.1+dfsg-6+b2 ii qdbus-qt55.1.1-2 > So we can be sure of what exact version we are talking about. After > that I'll tell you how to upgrade the rest. Yes, please? > qt5-default should only be used if you are developing things. Else > apps will just use the Qt version they where compiled for. You don't > need to do anything. > > OTOH, if you are developing things, you can avoid qt5-default too. > > Thanks and I'll wait for your reply to this mail :) Well, cl-qt needs the header files, so I'll just keep that installed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737047: postfix-policyd-spf-python: Missing depends on python-dns
On Thu, Jan 30, 2014 at 07:24:20PM -0500, Scott Kitterman wrote: > I'm not sure how this can happen. Python-spf (which is what's importing DNS) > depends on python-dns. That's a very good point. I do have the version from wheezy installed. I don't understand. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737189: libvtk6-java and libvtk-java: error when trying to install together
Package: libvtk-java,libvtk6-java Version: libvtk-java/5.8.0-15 Version: libvtk6-java/6.0.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-01-31 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: Extracting templates from packages: 33% Extracting templates from packages: 67% Extracting templates from packages: 100% Preconfiguring packages ... Selecting previously unselected package libkeyutils1:amd64. (Reading database ... 10921 files and directories currently installed.) Preparing to unpack .../libkeyutils1_1.5.6-1_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.6-1) ... Selecting previously unselected package libkrb5support0:amd64. Preparing to unpack .../libkrb5support0_1.12+dfsg-2_amd64.deb ... Unpacking libkrb5support0:amd64 (1.12+dfsg-2) ... Selecting previously unselected package libk5crypto3:amd64. Preparing to unpack .../libk5crypto3_1.12+dfsg-2_amd64.deb ... Unpacking libk5crypto3:amd64 (1.12+dfsg-2) ... Selecting previously unselected package libkrb5-3:amd64. Preparing to unpack .../libkrb5-3_1.12+dfsg-2_amd64.deb ... Unpacking libkrb5-3:amd64 (1.12+dfsg-2) ... Selecting previously unselected package libgssapi-krb5-2:amd64. Preparing to unpack .../libgssapi-krb5-2_1.12+dfsg-2_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.12+dfsg-2) ... Selecting previously unselected package libsasl2-modules-db:amd64. Preparing to unpack .../libsasl2-modules-db_2.1.25.dfsg1-17_amd64.deb ... Unpacking libsasl2-modules-db:amd64 (2.1.25.dfsg1-17) ... Selecting previously unselected package libsasl2-2:amd64. Preparing to unpack .../libsasl2-2_2.1.25.dfsg1-17_amd64.deb ... Unpacking libsasl2-2:amd64 (2.1.25.dfsg1-17) ... Selecting previously unselected package libldap-2.4-2:amd64. Preparing to unpack .../libldap-2.4-2_2.4.31-1+nmu2+b1_amd64.deb ... Unpacking libldap-2.4-2:amd64 (2.4.31-1+nmu2+b1) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.1+dfsg1-3_amd64.deb ... Unpacking libxml2:amd64 (2.9.1+dfsg1-3) ... Selecting previously unselected package libxau6:amd64. Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ... Unpacking libxau6:amd64 (1:1.0.8-1) ... Selecting previously unselected package x11-common. Preparing to unpack .../x11-common_1%3a7.7+5_all.deb ... Unpacking x11-common (1:7.7+5) ... Selecting previously unselected package libice6:amd64. Preparing to unpack .../libice6_2%3a1.0.8-2_amd64.deb ... Unpacking libice6:amd64 (2:1.0.8-2) ... Selecting previously unselected package libsm6:amd64. Preparing to unpack .../libsm6_2%3a1.2.1-2_amd64.deb ... Unpacking libsm6:amd64 (2:1.2.1-2) ... Selecting previously unselected package libxdmcp6:amd64. Preparing to unpack .../libxdmcp6_1%3a1.1.1-1_amd64.deb ... Unpacking libxdmcp6:amd64 (1:1.1.1-1) ... Selecting previously unselected package libxcb1:amd64. Preparing to unpack .../libxcb1_1.10-2_amd64.deb ... Unpacking libxcb1:amd64 (1.10-2) ... Selecting previously unselected package libx11-data. Preparing to unpack .../libx11-data_2%3a1.6.2-1_all.deb ... Unpacking libx11-data (2:1.6.2-1) ... Selecting previously unselected package libx11-6:amd64. Preparing to unpack .../libx11-6_2%3a1.6.2-1_amd64.deb ... Unpacking libx11-6:amd64 (2:1.6.2-1) ... Selecting previously unselected package libxt6:amd64. Preparing to unpack .../libxt6_1%3a1.1.4-1_amd64.deb ... Unpacking libxt6:amd64 (1:1.1.4-1) ... Selecting previously unselected package libaudio2:amd64. Preparing to unpack .../libaudio2_1.9.4-1_amd64.deb ... Unpacking libaudio2:amd64 (1.9.4-1) ... Selecting previously unselected package libavutil52:amd64. Preparing to unpack .../libavutil52_6%3a9.10-2_amd64.deb ... Unpacking libavutil52:amd64 (6:9.10-2) ... Selecting previously unselected package libgsm1:amd64. Preparing to unpack .../libgsm1_1.0.13-4_amd64.deb ... Unpacking libgsm1:amd64 (1.0.13-4) ... Selecting previously unselected package libmp3lame0:amd64. Preparing to unpack .../libmp3lame0_3.99.5+repack1-3_amd64.deb ... Unpacking libmp3lame0:amd64 (3.99.5+repack1-3) ... Selecting previously unselected package libopenjpeg2:amd64. Preparing to unpack .../libopenjpeg2_1.3+dfsg-4.7+b1_amd64.deb ... Unpacking libopenjpeg2:amd64 (1.3+dfsg-4.7+b1) ... Selecting previously unselected package libopus0:amd64. Preparing to unpack .../libopus0_1.1-1_amd64.deb ... Unpacking libopus0:amd64 (1.1-1) ... Selecting previously unselected package liborc-0.4-0:amd64. Preparing to unpack .../liborc-0.4-0_1%3a0.4.18-1_amd64.deb ... Unpacking liborc-0.4-0:amd64 (1:0.4.18-1) ... Selecting previously unselected package libschroedinger-1.0-0:amd64. Preparing to unpack .../libschroedinger-1.0-0_1.0.11-2_amd64.deb ... Unpacking libschroedinger-1.0-0:amd64 (1.0.11-2) ... Selecting previously unselected package libspeex1:amd64. Preparing to unpack .../libspeex1_1.2~rc1.1-1_amd64.deb ...
Bug#737190: vtk6 and tcl-vtk: error when trying to install together
Package: tcl-vtk,vtk6 Version: tcl-vtk/5.8.0-15 Version: vtk6/6.0.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-01-31 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: Extracting templates from packages: 21% Extracting templates from packages: 42% Extracting templates from packages: 64% Extracting templates from packages: 85% Extracting templates from packages: 100% Preconfiguring packages ... Selecting previously unselected package libkeyutils1:amd64. (Reading database ... 10921 files and directories currently installed.) Preparing to unpack .../libkeyutils1_1.5.6-1_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.6-1) ... Selecting previously unselected package libkrb5support0:amd64. Preparing to unpack .../libkrb5support0_1.12+dfsg-2_amd64.deb ... Unpacking libkrb5support0:amd64 (1.12+dfsg-2) ... Selecting previously unselected package libk5crypto3:amd64. Preparing to unpack .../libk5crypto3_1.12+dfsg-2_amd64.deb ... Unpacking libk5crypto3:amd64 (1.12+dfsg-2) ... Selecting previously unselected package libkrb5-3:amd64. Preparing to unpack .../libkrb5-3_1.12+dfsg-2_amd64.deb ... Unpacking libkrb5-3:amd64 (1.12+dfsg-2) ... Selecting previously unselected package libgssapi-krb5-2:amd64. Preparing to unpack .../libgssapi-krb5-2_1.12+dfsg-2_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.12+dfsg-2) ... Selecting previously unselected package libsasl2-modules-db:amd64. Preparing to unpack .../libsasl2-modules-db_2.1.25.dfsg1-17_amd64.deb ... Unpacking libsasl2-modules-db:amd64 (2.1.25.dfsg1-17) ... Selecting previously unselected package libsasl2-2:amd64. Preparing to unpack .../libsasl2-2_2.1.25.dfsg1-17_amd64.deb ... Unpacking libsasl2-2:amd64 (2.1.25.dfsg1-17) ... Selecting previously unselected package libldap-2.4-2:amd64. Preparing to unpack .../libldap-2.4-2_2.4.31-1+nmu2+b1_amd64.deb ... Unpacking libldap-2.4-2:amd64 (2.4.31-1+nmu2+b1) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.1+dfsg1-3_amd64.deb ... Unpacking libxml2:amd64 (2.9.1+dfsg1-3) ... Selecting previously unselected package libxau6:amd64. Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ... Unpacking libxau6:amd64 (1:1.0.8-1) ... Selecting previously unselected package x11-common. Preparing to unpack .../x11-common_1%3a7.7+5_all.deb ... Unpacking x11-common (1:7.7+5) ... Selecting previously unselected package libice6:amd64. Preparing to unpack .../libice6_2%3a1.0.8-2_amd64.deb ... Unpacking libice6:amd64 (2:1.0.8-2) ... Selecting previously unselected package libsm6:amd64. Preparing to unpack .../libsm6_2%3a1.2.1-2_amd64.deb ... Unpacking libsm6:amd64 (2:1.2.1-2) ... Selecting previously unselected package libxdmcp6:amd64. Preparing to unpack .../libxdmcp6_1%3a1.1.1-1_amd64.deb ... Unpacking libxdmcp6:amd64 (1:1.1.1-1) ... Selecting previously unselected package libxcb1:amd64. Preparing to unpack .../libxcb1_1.10-2_amd64.deb ... Unpacking libxcb1:amd64 (1.10-2) ... Selecting previously unselected package libx11-data. Preparing to unpack .../libx11-data_2%3a1.6.2-1_all.deb ... Unpacking libx11-data (2:1.6.2-1) ... Selecting previously unselected package libx11-6:amd64. Preparing to unpack .../libx11-6_2%3a1.6.2-1_amd64.deb ... Unpacking libx11-6:amd64 (2:1.6.2-1) ... Selecting previously unselected package libxt6:amd64. Preparing to unpack .../libxt6_1%3a1.1.4-1_amd64.deb ... Unpacking libxt6:amd64 (1:1.1.4-1) ... Selecting previously unselected package libaudio2:amd64. Preparing to unpack .../libaudio2_1.9.4-1_amd64.deb ... Unpacking libaudio2:amd64 (1.9.4-1) ... Selecting previously unselected package libavutil52:amd64. Preparing to unpack .../libavutil52_6%3a9.10-2_amd64.deb ... Unpacking libavutil52:amd64 (6:9.10-2) ... Selecting previously unselected package libgsm1:amd64. Preparing to unpack .../libgsm1_1.0.13-4_amd64.deb ... Unpacking libgsm1:amd64 (1.0.13-4) ... Selecting previously unselected package libmp3lame0:amd64. Preparing to unpack .../libmp3lame0_3.99.5+repack1-3_amd64.deb ... Unpacking libmp3lame0:amd64 (3.99.5+repack1-3) ... Selecting previously unselected package libopenjpeg2:amd64. Preparing to unpack .../libopenjpeg2_1.3+dfsg-4.7+b1_amd64.deb ... Unpacking libopenjpeg2:amd64 (1.3+dfsg-4.7+b1) ... Selecting previously unselected package libopus0:amd64. Preparing to unpack .../libopus0_1.1-1_amd64.deb ... Unpacking libopus0:amd64 (1.1-1) ... Selecting previously unselected package liborc-0.4-0:amd64. Preparing to unpack .../liborc-0.4-0_1%3a0.4.18-1_amd64.deb ... Unpacking liborc-0.4-0:amd64 (1:0.4.18-1) ... Selecting previously unselected package libschroedinger-1.0-0:amd64. Preparing to unpack .../libschroedinger-1.0-0_1.0.11-2_amd64.deb ... Unpacking libschroedinger-1.0-0:amd64 (1.0.11-2) ... Selecting previously unselected package libspeex1:amd64. Prep
Bug#729559: pgtap: /usr/share/postgresql/*/extension/pgtap--0.90.0.sql missing after rebuilding
As I noted in #723176, pgtap has been broken by changes in postgresql 9.3 extension handling: http://postgresql.1045698.n5.nabble.com/PostgreSQL-9-3-beta-breaks-some-extensions-quot-make-install-quot-td5755344.html Note also that pgtap 0.94 has now been released. The changelog includes: "Fixed an installation issue on PostgreSQL 9.3.2." http://api.pgxn.org/src/pgtap/pgtap-0.94.0/Changes Perhaps upgrading Debian pgtap to 0.94 might fix this issue? Kind regards, -- Ben Caradoc-Davies Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737188: logrotate: doesn't report permission errors unless run with -v
Package: logrotate Version: 3.8.1-4 Severity: normal If you have a file in /etc/logrotate.d/ with incorrect permissions according to logrotate (e.g. root root 0664) then logrotate will silently ignore the file unless run with -v. That means that errors are not reported to administrators at all. Also I'm not sure why permissions of /etc/logrotate.d/ files are important at all. Regards, Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735583: [Pkg-systemd-maintainers] Bug#735583: Bug#735583: systemd - Always succesful cryptdisks-early.service and cryptdisks.service
Hi Bastian, Bastian Blank writes: >> A lvm2 package shipping systemd service files has been uploaded making >> this bug report obsolete. Thus closing. > > Sorry, no. It is still broken. _And you broke it on purpose._ I am getting really fed up by your statements like this. You keep saying that we break things on purpose¹, which is not true, unfair and plain rude. Please stop it. ① The last time this happened was in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728486#68, and you never apologized for it. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737187: fsl: depends on deprecaed Tcl/Tk 8.4
Package: fsl
Version: 4.1.9-7
Severity: serious
Tags: patch
Dear Maintainer,
We are about to drop Tcl/Tk 8.4 from Debian, but your fsl package still
depends on tcl8.4 and tk8.4. The attached patch just replaces these
dependencies by tcl and tk, which are metapackages installing the default
Tcl/Tk version.
If you don't mind, I'll perform NMU with this patch.
-- System Information:
Debian Release: 7.3
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable'), (100, 'unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-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
diff -Nru fsl-4.1.9/debian/changelog fsl-4.1.9/debian/changelog
--- fsl-4.1.9/debian/changelog 2012-10-22 13:00:27.0 +0400
+++ fsl-4.1.9/debian/changelog 2014-01-31 10:47:47.0 +0400
@@ -1,3 +1,10 @@
+fsl (4.1.9-7.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Replaced tcl8.4 and tk8.4 by tcl and tk in the package dependencies.
+
+ -- Sergei Golovan Fri, 31 Jan 2014 10:47:41 +0400
+
fsl (4.1.9-7) unstable; urgency=low
* Stop regenerating tclIndex during postinst. This is no longer necessary
diff -Nru fsl-4.1.9/debian/control fsl-4.1.9/debian/control
--- fsl-4.1.9/debian/control 2012-10-22 13:04:59.0 +0400
+++ fsl-4.1.9/debian/control 2014-01-31 10:46:39.0 +0400
@@ -7,7 +7,7 @@
libboost-dev (>= 1.32.0), libpng12-dev (>= 1.2.8rel),
libgd2-noxpm-dev (>= 2.0.33) | libgd2-xpm-dev (>= 2.0.33), libnewmat10-dev,
libgdchart-gd2-noxpm-dev | libgdchart-gd2-xpm-dev,
- liboctave-dev | octave3.2-headers | octave3.0-headers, tcl8.4 (>=8.4.7),
+ liboctave-dev | octave3.2-headers | octave3.0-headers, tcl,
imagemagick, libnifti-dev (>> 1.1.0-1)
Standards-Version: 3.9.3
Homepage: http://www.fmrib.ox.ac.uk/fsl/
@@ -29,7 +29,7 @@
Package: fsl-4.1
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, mozilla-firefox | www-browser, tcsh | c-shell, tk8.4 (>=8.4.7), tcl8.4 (>=8.4.7), bc, dc
+Depends: ${shlibs:Depends}, ${misc:Depends}, mozilla-firefox | www-browser, tcsh | c-shell, tk, tcl, bc, dc
Recommends: fsl-doc-4.1 (= ${source:Version}), fsl-atlases, fslview
Suggests: fsl-feeds, octave | ${octave:Depends}, dicomnifti, fsl-possum-data, fsl-first-data, gridengine-client
Conflicts: fsl-fslview, fsl-doc-4.1 (<< 4.1.9-5~)
Bug#737186: modemmanager: Please update to ModemMonager 1.2~rc1
Package: modemmanager Version: 1.0.0-2 Severity: wishlist Hi, it'd be great to update to the above release candidat since that's needed for newer laptops that ship with newer QMI hardware like the Sony Vaio Duo 13". Cheers, -- Guido -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13.0-rc7+ (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages modemmanager depends on: ii libc6 2.17-97 ii libglib2.0-02.38.2-1 ii libgudev-1.0-0 204-6 ii libmbim-glib0 1.6.0-2 ii libmm-glib0 1.0.0-1 ii libqmi-glib01.4.0-1 Versions of packages modemmanager recommends: ii usb-modeswitch 2.0.1+repack0-2 modemmanager 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#735583: [Pkg-systemd-maintainers] Bug#735583: Bug#735583: systemd - Always succesful cryptdisks-early.service and cryptdisks.service
Am 31.01.2014 07:41, schrieb Bastian Blank: > Control: reopen -1 > > On Fri, Jan 31, 2014 at 06:41:09AM +0100, Michael Biebl wrote: >> Am 16.01.2014 23:07, schrieb Bastian Blank: I still hope we can convince you to ship a systemd service file for lvm2. >>> Well. There is no other solution available anyway. >> A lvm2 package shipping systemd service files has been uploaded making >> this bug report obsolete. Thus closing. > > Sorry, no. It is still broken. And you broke it on purpose. What is broken? -- 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#735583: [Pkg-systemd-maintainers] Bug#735583: systemd - Always succesful cryptdisks-early.service and cryptdisks.service
Control: reopen -1 On Fri, Jan 31, 2014 at 06:41:09AM +0100, Michael Biebl wrote: > Am 16.01.2014 23:07, schrieb Bastian Blank: > >> I still hope we can convince you to ship a systemd service file for > >> lvm2. > > Well. There is no other solution available anyway. > A lvm2 package shipping systemd service files has been uploaded making > this bug report obsolete. Thus closing. Sorry, no. It is still broken. And you broke it on purpose. Bastian -- Where there's no emotion, there's no motive for violence. -- Spock, "Dagger of the Mind", stardate 2715.1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737184: No longer reads /etc/sysctl.conf, please provide compat symlink
Package: procps Version: 1:3.3.9-2 Severity: normal Hi, sysctl --system (as used in /etc/init.d/procps) no longer processes /etc/sysctl.conf. The corresponding systemd tool had a similar change in v207. I'm copying here the rational for this change from the systemd changelog: * The systemd-sysctl tool no longer natively reads the file /etc/sysctl.conf. If desired, the file should be symlinked from /etc/sysctl.d/99-sysctl.conf. Apart from providing legacy support by a symlink rather than built-in code, it also makes the otherwise hidden order of application of the different files visible. (Note that this partly reverts to a pre-198 application order of sysctl knobs!) Since procps is the package shipping /etc/sysctl.conf, such a /etc/sysctl.d/99-sysctl.conf symlink is probably best shipped in the procps package. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages procps depends on: ii initscripts 2.88dsf-45 ii libc6 2.17-97 ii libncurses5 5.9+20140118-1 ii libncursesw5 5.9+20140118-1 ii libprocps31:3.3.9-2 ii libtinfo5 5.9+20140118-1 ii lsb-base 4.1+Debian12 Versions of packages procps recommends: ii psmisc 22.20-1 procps 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#737185: axe: Build-depends on deprecated Tcl 8.4
Package: axe Version: 6.1.2-16 Severity: serious Tags: patch Dear Maintainer, We are about to drop Tcl/Tk 8.4 from Debian, and your axe package build depends on tcl8.4-dev. The attached patch replaces tcl8.4-dev by tcl-dev in build dependencies, which makes it build successfully for unstable where tcl-dev pulls tcl8.5-dev, but not in experimental where tcl-dev depends on tcl8.6-dev, so I had to define USE_INTERP_RESULT macro also. If you don't mind, I could do NMU with these changes. -- System Information: Debian Release: 7.3 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-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 diff -u axe-6.1.2/Axe.tmpl axe-6.1.2/Axe.tmpl --- axe-6.1.2/Axe.tmpl +++ axe-6.1.2/Axe.tmpl @@ -41,10 +41,10 @@ #define Extension /* ...and state where the Tcl include files are */ -#define TclIncDir /usr/include/tcl8.4 +#define TclIncDir /usr/include/tcl /* ...and where the library is, i.e. TclLibDir/libtcl.a (or .so.?.?) exists */ -#define TclLibDir /usr/lib +/* #define TclLibDir /usr/lib */ @@ -110,10 +110,10 @@ #ifdef Extension EXTN_SRCS = Language.c EXTN_OBJS = Language.o -EXTN_INCLUDES = -I/**/TclIncDir +EXTN_INCLUDES = -I/**/TclIncDir -DUSE_INTERP_RESULT EXTN_LDFLAGS = -L/**/TclLibDir /*EXTN_LIBS = -ltcl8.0 -lm */ -EXTN_LIBS = -ltcl8.4 -lm +EXTN_LIBS = -ltcl -lm EXTENSION = -DEXTENSION #endif EXTN_DEPS = AxeEditor.o axe.o diff -u axe-6.1.2/debian/changelog axe-6.1.2/debian/changelog --- axe-6.1.2/debian/changelog +++ axe-6.1.2/debian/changelog @@ -1,3 +1,11 @@ +axe (6.1.2-16.1) unstable; urgency=low + + * Non-maintainer upload. + * Replaced obsolete tcl8.4-dev build dependency by tcl-dev. + * Defined macro USE_INTERP_RESULT to make axe building with Tcl 8.6. + + -- Sergei Golovan Fri, 31 Jan 2014 10:32:14 +0400 + axe (6.1.2-16) unstable; urgency=low * Acknowledge NMU. diff -u axe-6.1.2/debian/control axe-6.1.2/debian/control --- axe-6.1.2/debian/control +++ axe-6.1.2/debian/control @@ -2,7 +2,7 @@ Section: non-free/editors Priority: optional Maintainer: Hwei Sheng Teoh -Build-Depends: debhelper (>=5.0.14), tcl8.4-dev, libx11-dev, libxmu-dev, libxt-dev, libsm-dev, libxpm-dev, libice-dev, libxaw7-dev, xutils-dev +Build-Depends: debhelper (>=5.0.14), tcl-dev, libx11-dev, libxmu-dev, libxt-dev, libsm-dev, libxpm-dev, libice-dev, libxaw7-dev, xutils-dev Standards-Version: 3.9.4 Package: axe
Bug#669101: systemd: Boot hangs
Hi Vincent, hi Mark! There were some recent fixes in the lvm2/dmsetup package which might also fix the issues you were having with cryptsetup. Can you please update to the latest versions of lvm2 (2.02.104-1) and dmsetup (2:1.02.83-1) and report back with your results. 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#737006: [Pkg-systemd-maintainers] Bug#737006: systemd: When init=/lib/systemd/systemd, selinux no longer works
Am 29.01.2014 10:54, schrieb Bart-Jan Vrielink: > Package: systemd > Version: 204-6 > Severity: important > > Dear Maintainer, > > When I boot up under systemd, I get asked if I want to enter a security > context when I login. It seems that all processes are running under the > kernel_t label (except systemd-udevd, which runs under > system_u:system_r:udev_t:s0-s0:c0.c1023) > > Because of this, the combination of SELinux and systemd is at the moment > unusable. SELinux works fine under init=/sbin/init Sounds like a bug in the selinux policy package to me, not in systemd itself. That said, I basically know nothing about selinux. bigon, can you comment on this bug report? Let us know whether we should re-assing it to one of the selinux-policy-* packages or if there is something which needs to be addressed in systemd. 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#737183: pu: package kfreebsd-8/8.3-6+deb7u1
Control: tags -1 + confirmed On Fri, 2014-01-31 at 03:57 +, Steven Chamberlain wrote: > Please could we also update kfreebsd-8 in wheezy? This has the same > backported patch to disable hardware RNGs, as well as a backlog of > security fixes, that are already applied to kfreebsd-9 in wheezy. > > kfreebsd-8 is removed already from jessie/sid. It was not the default > kernel for wheezy, so issues are handled at a lower priority, and the > security bugs are marked non-DSA. Please go ahead, bearing in mind that the window for 7.4 closes this weekend. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737126: Bug#736656: libdbi-drivers: drivers not found anymore, due to multi-arch
On Fri, Jan 31, 2014 at 7:09 AM, wrote:
> Prach Pongpanich writes:
[..]
> > (Cc:-ing #737126)
> >
> > That reduced failures, but still remain the issue with "the_float" and
> > "the_double".
> >
> > Running "libdbi framework test"...
> > test_dbi.c:3732: unit test failure: sqlite3 -> libdbi connection ->
> > Retrieving fields as -> test_dbi_result_get_as_longlong -> [-1] should
> > match [0] at [test_dbi.c] line [3732]
> > test_dbi.c:3733: unit test failure: sqlite3 -> libdbi connection ->
> > Retrieving fields as -> test_dbi_result_get_as_longlong -> [-1] should
> > match [0] at [test_dbi.c] line [3733]
> > Running "libdbi framework test"...
> > Running "libdbi framework test"...
> > Running "libdbi framework test"...
> > Completed "libdbi framework test": 397 passes, 2 failures, 0 exceptions.
> > make: *** [test-stamp] Error 1
> >
>
> Ok, seems we're halfway there. It is certainly worth checking all the
> compiler warnings that Laszlo mentioned. But the above mentioned
> failures may be related to the way how libdbi converts floating
> point numbers to long long values. Prach, could you please run the
> test program below and report any compiler warnings as well as the
> output on armel?
>
>
> float2longlong.c
> --8<
> #include
> #include
>
> int main() {
> float bigfloat = 3.402823e+38;
> long long bigfloat_casted;
>
> bigfloat_casted = (long long)bigfloat;
> printf("%lld\n", bigfloat_casted);
> exit (0);
> }
I've added a big double:
root@raspy-sid:~# gcc -Wall -g fd2ll.c -o fd2ll
root@raspy-sid:~# ./fd2ll
bigfloat2ll = -1
bigdouble2ll = -1
--
Prach
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737104: RM: tcl8.4/8.4.20-1
Hi Adam, On Fri, Jan 31, 2014 at 12:01 AM, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Thu, 2014-01-30 at 13:58 +0400, Sergei Golovan wrote: >> Please, remove tcl8.4 (and its close relative tk8.4) from testing. >> It reached end of life and superseded by tcl8.5/tk8.5 and tcl8.6/tk8.6, >> so, it should be dropped from jessie release. >> >> There is only one package in testing that still depends on tcl8.4: >> mpqc on ia64 architecture. > > That appears to be inaccurate. Only one package in *testing*. I didn't look at non-free though, so yes, it's inaccurate. Should I care for packages from non-free? Cheers! -- Sergei Golovan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737034: workrave 1.10.1-3 lost translations support
Package: workrave
Version: 1.10.1-3
Followup-For: Bug #737034
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* Revert most of changes from 1.10.1-3 to remedy translation issue.
* Doing a manual libtool update instead to fix FTBFS on ppc64el.
Thanks for considering the patch.
Logan Rosen
-- System Information:
Debian Release: jessie/sid
APT prefers trusty-updates
APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500,
'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13.0-5-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru workrave-1.10.1/debian/control workrave-1.10.1/debian/control
--- workrave-1.10.1/debian/control 2014-01-26 01:12:49.0 -0500
+++ workrave-1.10.1/debian/control 2014-01-30 23:04:41.0 -0500
@@ -4,7 +4,8 @@
Maintainer: Francois Marier
Uploaders: Jordi Mallach
Build-Depends: debhelper (>= 9),
- dh-autoreconf,
+# dh-autoreconf,
+ autotools-dev,
docbook-utils,
xmlto,
gobject-introspection (>= 0.6.7),
diff -Nru workrave-1.10.1/debian/patches/disable_Werror.patch workrave-1.10.1/debian/patches/disable_Werror.patch
--- workrave-1.10.1/debian/patches/disable_Werror.patch 2014-01-26 01:12:49.0 -0500
+++ workrave-1.10.1/debian/patches/disable_Werror.patch 1969-12-31 19:00:00.0 -0500
@@ -1,16 +0,0 @@
-Author: Logan Rosen
-Forwarded: no
-Last-Update: 2014-01-25
-Description: Disable -Werror to fix FTBFS while autoreconfing
-
a/configure.ac
-+++ b/configure.ac
-@@ -25,7 +25,7 @@
- AC_CONFIG_MACRO_DIR([m4])
- AC_CONFIG_HEADER([config.h])
-
--AM_INIT_AUTOMAKE([-Wall -Werror foreign silent-rules])
-+AM_INIT_AUTOMAKE([-Wall foreign silent-rules])
- dnl AM_SILENT_RULES([yes])
-
- GNOME_SHELL_VERSION=3.6.2
diff -Nru workrave-1.10.1/debian/patches/libtool_ppc64el.patch workrave-1.10.1/debian/patches/libtool_ppc64el.patch
--- workrave-1.10.1/debian/patches/libtool_ppc64el.patch 1969-12-31 19:00:00.0 -0500
+++ workrave-1.10.1/debian/patches/libtool_ppc64el.patch 2014-01-30 22:44:32.0 -0500
@@ -0,0 +1,52 @@
+--- a/configure
b/configure
+@@ -9123,7 +9123,10 @@
+ ;;
+ esac
+ ;;
+- ppc64-*linux*|powerpc64-*linux*)
++ powerpc64le-*)
++ LD="${LD-ld} -m elf32lppclinux"
++ ;;
++ powerpc64-*)
+ LD="${LD-ld} -m elf32ppclinux"
+ ;;
+ s390x-*linux*)
+@@ -9142,7 +9145,10 @@
+ x86_64-*linux*)
+ LD="${LD-ld} -m elf_x86_64"
+ ;;
+- ppc*-*linux*|powerpc*-*linux*)
++ powerpcle-*)
++ LD="${LD-ld} -m elf64lppc"
++ ;;
++ powerpc-*)
+ LD="${LD-ld} -m elf64ppc"
+ ;;
+ s390*-*linux*|s390*-*tpf*)
+--- a/m4/libtool.m4
b/m4/libtool.m4
+@@ -1333,7 +1333,10 @@
+ ;;
+ esac
+ ;;
+- ppc64-*linux*|powerpc64-*linux*)
++ powerpc64le-*)
++ LD="${LD-ld} -m elf32lppclinux"
++ ;;
++ powerpc64-*)
+ LD="${LD-ld} -m elf32ppclinux"
+ ;;
+ s390x-*linux*)
+@@ -1352,7 +1355,10 @@
+ x86_64-*linux*)
+ LD="${LD-ld} -m elf_x86_64"
+ ;;
+- ppc*-*linux*|powerpc*-*linux*)
++ powerpcle-*)
++ LD="${LD-ld} -m elf64lppc"
++ ;;
++ powerpc-*)
+ LD="${LD-ld} -m elf64ppc"
+ ;;
+ s390*-*linux*|s390*-*tpf*)
diff -Nru workrave-1.10.1/debian/patches/remove_gettext_macros.patch workrave-1.10.1/debian/patches/remove_gettext_macros.patch
--- workrave-1.10.1/debian/patches/remove_gettext_macros.patch 2014-01-26 01:12:49.0 -0500
+++ workrave-1.10.1/debian/patches/remove_gettext_macros.patch 1969-12-31 19:00:00.0 -0500
@@ -1,16 +0,0 @@
-Author: Logan Rosen
-Forwarded: no
-Last-Update: 2014-01-25
-Description: Remove gettext macros to make sure libtool is creating po/Makefile.in.in
-
a/configure.ac
-+++ b/configure.ac
-@@ -837,8 +837,6 @@
- dnl Internationalization
- dnl
-
--AM_GNU_GETTEXT_VERSION([0.17])
--AM_GNU_GETTEXT([external])
-
- dnl Hack because windows gettext package is SEVERELY broken...
- if test "x$platform_os_win32" = "xyes"
diff -Nru workrave-1.10.1/debian/patches/series workrave-1.10.1/debian/patches/series
--- workrave-1.10.1/debian/patches/series 2014-01-26 01:12:49.0 -0500
+++ workrave-1.10.1/debian/patches/series 2014-01-30 22:43:03.0 -0500
@@ -1,5 +1,4 @@
#private_dirs.patch
git_fix_desktop_bugs.patch
gnome_3.8.patch
-disable_Werror.patch
-remove_gettext_macros.patch
+libtool_ppc64el.patch
diff -Nru workrave-1.10.1/debian/rules workrave-1.10.1/debian/rules
--- workrave-1.10.1/debian/rules 2014-01-26 01:12:49.0 -0500
+++ workrave-1.10.1/debian/rules 2014-01-30 22:40:41.0 -0500
@@ -1,6 +1,6 @@
#!/usr/bin/make -f
%:
- dh $@ --with autoreconf
+ dh $@
override_dh_auto_configure:
dh_auto_configure --
Bug#737183: pu: package kfreebsd-8/8.3-6+deb7u1
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: wheezy
X-Debbugs-Cc: debian-...@lists.debian.org
Hi,
Please could we also update kfreebsd-8 in wheezy? This has the same
backported patch to disable hardware RNGs, as well as a backlog of
security fixes, that are already applied to kfreebsd-9 in wheezy.
kfreebsd-8 is removed already from jessie/sid. It was not the default
kernel for wheezy, so issues are handled at a lower priority, and the
security bugs are marked non-DSA.
The debdiff is attached. Thanks!
> kfreebsd-8 (8.3-6+deb7u1) wheezy; urgency=medium
>
> [ Robert Millan ]
> * Apply upstream SA-13_08.nfsserver patch (CVE-2013-4851).
> (Closes: #717959)
>
> [ Steven Chamberlain ]
> * Apply upstream SA-13_09.ip_multicast patch (CVE-2013-3077).
> (Closes: #720470)
> * Apply upstream SA-13_10.sctp patch (CVE-2013-5209).
> (Closes: #720476)
> * Apply upstream SA-13_12.ifioctl patch (CVE-2013-5691).
> (Closes: #737181)
> * Apply upstream SA-13_13.nullfs patch (CVE-2013-5710).
> (Closes: #737182)
> * Disable VIA hardware RNG by default. Use hw.nehemiah_rng_enable
> sysctl to re-enable (but read about the security implications
> first). (Closes: #735448)
>
> -- Steven Chamberlain Fri, 31 Jan 2014 02:58:14 +
diff -Nru kfreebsd-8-8.3/debian/changelog kfreebsd-8-8.3/debian/changelog
--- kfreebsd-8-8.3/debian/changelog 2012-11-23 22:13:01.0 +
+++ kfreebsd-8-8.3/debian/changelog 2014-01-31 03:35:00.0 +
@@ -1,3 +1,24 @@
+kfreebsd-8 (8.3-6+deb7u1) wheezy; urgency=medium
+
+ [ Robert Millan ]
+ * Apply upstream SA-13_08.nfsserver patch (CVE-2013-4851).
+(Closes: #717959)
+
+ [ Steven Chamberlain ]
+ * Apply upstream SA-13_09.ip_multicast patch (CVE-2013-3077).
+(Closes: #720470)
+ * Apply upstream SA-13_10.sctp patch (CVE-2013-5209).
+(Closes: #720476)
+ * Apply upstream SA-13_12.ifioctl patch (CVE-2013-5691).
+(Closes: #737181)
+ * Apply upstream SA-13_13.nullfs patch (CVE-2013-5710).
+(Closes: #737182)
+ * Disable VIA hardware RNG by default. Use hw.nehemiah_rng_enable
+sysctl to re-enable (but read about the security implications
+first). (Closes: #735448)
+
+ -- Steven Chamberlain Fri, 31 Jan 2014 02:58:14 +
+
kfreebsd-8 (8.3-6) unstable; urgency=medium
* Apply patch for SA-12:08 / CVE-2012-4576:
diff -Nru kfreebsd-8-8.3/debian/patches/disable_via_rng.diff
kfreebsd-8-8.3/debian/patches/disable_via_rng.diff
--- kfreebsd-8-8.3/debian/patches/disable_via_rng.diff 1970-01-01
00:00:00.0 +
+++ kfreebsd-8-8.3/debian/patches/disable_via_rng.diff 2014-01-31
03:15:37.0 +
@@ -0,0 +1,34 @@
+Description:
+ Disable VIA hardware RNG by default due to unsafe usage. Implement a
+ loader tunable allowing to turn it back on.
+ .
+ Minimal patch based on upstream SVN r240950 and r260644
+Origin: backport, commit:240950, commit:260644
+Forwarded: not-needed
+Bug-Debian: http://bugs.debian.org/735448
+
+--- kfreebsd-8-8.3.orig/sys/dev/random/probe.c
kfreebsd-8-8.3/sys/dev/random/probe.c
+@@ -30,6 +30,8 @@
+
+ #include
+ #include
++#include
++#include
+ #include
+ #include
+ #include
+@@ -57,7 +59,12 @@
+ /* Then go looking for hardware */
+ #if defined(__i386__) && !defined(PC98)
+ if (via_feature_rng & VIA_HAS_RNG) {
+- *systat = random_nehemiah;
++ int enable;
++
++ enable = 0;
++ TUNABLE_INT_FETCH("hw.nehemiah_rng_enable", &enable);
++ if (enable)
++ *systat = random_nehemiah;
+ }
+ #endif
+ }
diff -Nru kfreebsd-8-8.3/debian/patches/SA-13_08.nfsserver.diff
kfreebsd-8-8.3/debian/patches/SA-13_08.nfsserver.diff
--- kfreebsd-8-8.3/debian/patches/SA-13_08.nfsserver.diff 1970-01-01
00:00:00.0 +
+++ kfreebsd-8-8.3/debian/patches/SA-13_08.nfsserver.diff 2014-01-31
02:26:03.0 +
@@ -0,0 +1,21 @@
+Description:
+ Fix a bug that allows remote client bypass the normal
+ access checks when when -network or -host restrictions
+ are used at the same time with -mapall. [13:08]
+ (CVE-2013-4851)
+Origin: vendor, http://security.FreeBSD.org/patches/SA-13:08/nfsserver.patch
+Bug: http://www.freebsd.org/security/advisories/FreeBSD-SA-13:08.nfsserver.asc
+Bug-Debian: http://bugs.debian.org/717959
+Applied-Upstream: http://svnweb.freebsd.org/base?view=revision&revision=253694
+
+--- a/sys/kern/vfs_export.c
b/sys/kern/vfs_export.c
+@@ -208,7 +208,7 @@
+ np->netc_anon = crget();
+ np->netc_anon->cr_uid = argp->ex_anon.cr_uid;
+ crsetgroups(np->netc_anon, argp->ex_anon.cr_ngroups,
+- np->netc_anon->cr_groups);
++ argp->ex_anon.cr_groups);
+ np->netc_anon->cr_prison = &prison0;
+ prison_hold(np->netc_anon->cr_prison);
+ np->netc_numsecflavors = argp->ex_numsecflavors;
diff -Nru kfreebsd-8-8.3/debian/patches/SA-13_09.ip_multicast.diff
kfr
Bug#723144: sasl2-bin: saslauthd infinite loop inside sendto_kdc.c at function service_fds
On Mon, Sep 16, 2013 at 09:26:05PM +0100, Rodrigo Cunha wrote:
>
> Once in a while saslauthd goes into an infinite loop, using 100% cpu.
>
> We haven't determined what causes this, but the loop occurs inside kerberos
> library at sendto_kdc.c function service_fds, more specifically at the
> while loop that starts as...
>
> %% while (selstate->nfds > 0) {
>
> ... it appears (but I might be wrong) as if all calls to ...
>
> %% if (state->fd == INVALID_SOCKET)
>
> ... return true and the code continues (continue) forever.
>
Sam, Russ, and Ben,
In the information provided in #723144, it appears that the problem
reported initially against sasl2-bin may actually be a problem in the
Kerberos. I want to get your opinion before I go and reassign the bug
incorrectly. The complete report in the BTS has a GDB trace.
Regards,
-Roberto
--
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com
signature.asc
Description: Digital signature
Bug#736692: Please put this on hold
I'm looking into a better fix that doesn't neuter gettext. Another package with this fix applied had broken translations. I think a manual update of libtool files will be safer.
Bug#716723: sasl2-bin: subprocess installed post-installation script returned error exit status 1
Hi Roberto, good work on this issue. I think you are correct, the file was originally created on an ultrasparc 10 which is big endian, and has later been moved to an x86 machine. the bug can be closed. thanks, Johannes > > Hi Roberto, > > thank you for looking into this. I will send you a link to the sasldb2 file > > in a > > personal separate email for you investigation (would you please provide me > > with > > an address?). Please keep the contents of this file private. You may share > > the > > contents and the file with other package maintainers or who else you see > > fit to > > work on this bug, provided they also keep it private. > > Johannes, > > I believe that I have figured out the problem. > > It appears that you created the sasldb2 file on a big endian machine and > then later moved it to a little endian machine. This causes the upgrade > to fail. > > Here is what happens on my amd64 system: > > roberto@miami:/var/lib/chroot/squeeze/etc$ sudo db5.1_upgrade sasldb2 > db5.1_upgrade: sasldb2: DB->upgrade only supported on native byte-order > systems > db5.1_upgrade: DB->upgrade: sasldb2: Invalid argument > roberto@miami:/var/lib/chroot/squeeze/etc$ file sasldb2 > sasldb2: Berkeley DB (Hash, version 8, big-endian) > > I temporarily transferred the file over to a PowerPC porterbox, and here > is what happens: > > (sid_powerpc-dchroot)roberto@partch:~$ db5.1_upgrade sasldb2 > (sid_powerpc-dchroot)roberto@partch:~$ logout > roberto@partch:~$ file sasldb2 > sasldb2: Berkeley DB (Hash, version 9, native byte-order) > > Based on this, I believe that this is not a bug in the sasl2-bin > package. I believe that you can correct this by dumping the contents > using the db4.8_dump command and then recreating the database on your > system. > > If you agree, I would like to close this bug report. > > Regards, > > -Roberto > > -- > Roberto C. Sánchez > http://people.connexer.com/~roberto > http://www.connexer.com signature.asc Description: Digital signature
Bug#727708: multiple init systems - formal resolution proposal - Don't like software, don't use it. Absolutely.
Matthias Klumpp writes: > Of course it does not exclude implementing that stuff in a different, > non-systemd tool, but to my knowledge nobody has done that yet. Exactly so. I have ideas on how this might work in a simpler and more general fashion, but people rarely listen to ideas without also seeing working code :-) -- keith.pack...@intel.com pgpihYFZRaSsF.pgp Description: PGP signature
Bug#734763: Please update libjs-jquery-cookie and use upstream numbering
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 More than a few packages in Debian depend on the currently packaged version. Do you know if such an update would introduce incompatible changes? libjs-jquery-cookie Reverse Depends: spip spotweb python-django-debug-toolbar python-tables-doc openstack-dashboard spip python-django-feincms python-tables-doc phpmyadmin php-apigen mediawiki libkohana3.2-mod-userguide-php libkohana3.1-mod-userguide-php liblemonldap-ng-portal-perl liblemonldap-ng-manager-perl openstack-dashboard galette dotclear dokuwiki cacti -- Jerome -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBCAAGBQJS6wohAAoJEK/ZGpI6kvtMPBYH/jTNSDvXx8bIQUwMTPgBbF4v bwwCjLJ1YTAetiVNWfJhLmnPeklNC2geAcEKU/kW3dGEn5L57KUWMJpWPujASuu/ yKGqfRQ6F3nl6zzQoTE3td9Hh+WjbK/w7gO6O98nMY8i0uT8XTi5T1xNxjnVoiW9 ztJN2IIdbbefaaSIF0JiqQ0xBbiC4X2RRTYJToVxACfjh1PUT3wIqS4LjQdEKIOZ lpsLCoKd1PIyjTwHNk6xsFiSelGNWS0Jj3dA716awj5CJbNIzMMhQRLyj+jVLPTk Rd5hCwae0V6Hnib8Z1AnLon3FMM7/0HcyNCpMtEMhFcjEiO2SICzjwnDfvUTaQw= =41+m -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#736892: CPU family
One other thing bothers me. /proc/cpuid indicates that the "cpu family" for all four processors is 21. Yet the kernel messages indicate that the microcode update was taken from a file for family 15 processors. Are we sure that the correct microcode update is being loaded? -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#736552: [PATCH] Add jQuery FullScreen Plugin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tags: patch
Here's a patch against the jquery-goodies' source code Git tree.
- ---
debian/control | 11 ++
debian/copyright | 6 ++
debian/libjs-jquery-fullscreen.README.Debian | 13 +++
debian/libjs-jquery-fullscreen.docs | 1 +
debian/libjs-jquery-fullscreen.install | 1 +
debian/rules | 6 ++
fullscreen/jquery.fullscreen.js | 147
+++
fullscreen/readme.md | 75 ++
8 files changed, 260 insertions(+)
create mode 100644 debian/libjs-jquery-fullscreen.README.Debian
create mode 100644 debian/libjs-jquery-fullscreen.docs
create mode 100644 debian/libjs-jquery-fullscreen.install
create mode 100644 fullscreen/jquery.fullscreen.js
create mode 100644 fullscreen/readme.md
diff --git a/debian/control b/debian/control
index 914a50c..3af8f2d 100644
- --- a/debian/control
+++ b/debian/control
@@ -316,3 +316,14 @@ Description: Simple slideshow plugin for jQuery
A simple slideshow plugin for jQuery packed with a useful set of
features to
help novice and advanced developers alike create elegant and
user-friendly
slideshows.
+
+Package: libjs-jquery-fullscreen
+Architecture: all
+Depends: ${misc:Depends}, libjs-jquery
+Recommends: javascript-common
+Homepage:
http://tutorialzine.com/2012/02/enhance-your-website-fullscreen-api/
+Description: jQuery FullScreen Plugin
+ A jQuery 1.7 plugin that wraps around the Full Screen API and works
around
+ various browser differences. Works in FF 10, Chrome and Safari. It
is useful
+ for presenting users with an easier to read version of your web
pages, or
+ zooming and elements.
diff --git a/debian/copyright b/debian/copyright
index 10cafbd..078d2f4 100644
- --- a/debian/copyright
+++ b/debian/copyright
@@ -106,6 +106,12 @@ Files: slides/*
Copyright: 2011 Nathan Searles, http://nathansearles.com
License: Apache-2.0
+Files: fullscreen/*
+Copyright: 2012 Martin Angelov
+Homepage:
http://tutorialzine.com/2012/02/enhance-your-website-fullscreen-api/
+License: Expat
+Source: https://github.com/martinaglv/jQuery-FullScreen/issues/13
+
Files: debian/*
Copyright: (c) 2009-2011 Marcelo Jorge Vieira
License: MIT or GPL-2+ or BSD or Apache-2.0
diff --git a/debian/libjs-jquery-fullscreen.README.Debian
b/debian/libjs-jquery-fullscreen.README.Debian
new file mode 100644
index 000..35e78ef
- --- /dev/null
+++ b/debian/libjs-jquery-fullscreen.README.Debian
@@ -0,0 +1,13 @@
+libjs-jquery-fullscreen for Debian
+--
+
+In order to make use of fullscreen in your html, include the following
+lines in your html header
+
+
+
+
+
+ -- Jerome Charaoui , Sun, 26 Jan 2014 19:41:54 -0500
diff --git a/debian/libjs-jquery-fullscreen.docs
b/debian/libjs-jquery-fullscreen.docs
new file mode 100644
index 000..c97d3b7
- --- /dev/null
+++ b/debian/libjs-jquery-fullscreen.docs
@@ -0,0 +1 @@
+fullscreen/readme.md
diff --git a/debian/libjs-jquery-fullscreen.install
b/debian/libjs-jquery-fullscreen.install
new file mode 100644
index 000..1e23cc1
- --- /dev/null
+++ b/debian/libjs-jquery-fullscreen.install
@@ -0,0 +1 @@
+fullscreen/jquery.fullscreen.js /usr/share/javascript/jquery-fullscreen
diff --git a/debian/rules b/debian/rules
index 4edbfeb..e33ee42 100755
- --- a/debian/rules
+++ b/debian/rules
@@ -27,6 +27,7 @@ override_dh_auto_build:
yui-compressor resize/jquery.ba-resize.js -o
resize/jquery.ba-resize.min.js
yui-compressor uploadify/jquery.uploadify.js -o
uploadify/jquery.uploadify.min.js
yui-compressor slides/source/slides.jquery.js -o
slides/source/slides.min.jquery.js
+ yui-compressor fullscreen/jquery.fullscreen.js -o
fullscreen/jquery.fullscreen.min.js
override_dh_installchangelogs:
dh_installchangelogs --package libjs-jquery-livequery
livequery/ChangeLog.markdown
@@ -59,3 +60,8 @@ override_dh_auto_clean:
rm -f resize/jquery.ba-resize.min.js
rm -f uploadify/jquery.uploadify.min.js
rm -f slides/source/slides.min.jquery.js
+ rm -f fullscreen/jquery.fullscreen.min.js
+
+override_dh_gencontrol:
+ dh_gencontrol -plibjs-jquery-fullscreen -- -v1.2
+ dh_gencontrol --remaining-packages
diff --git a/fullscreen/jquery.fullscreen.js
b/fullscreen/jquery.fullscreen.js
new file mode 100644
index 000..78499f0
- --- /dev/null
+++ b/fullscreen/jquery.fullscreen.js
@@ -0,0 +1,147 @@
+/**
+ * @namejQuery FullScreen Plugin
+ * @author Martin Angelov, Morten Sjøgren
+ * @version 1.2
+ * @url
http://tutorialzine.com/2012/02/enhance-your-website-fullscreen-api/
+ * @license MIT License
+ */
+
+/*jshint browser: true, jquery: true */
+(function($){
+ "use strict";
+
+ // These helper functions available only to our plugin scope.
+ function supportFullScreen(){
+ var doc = document.documentEl
Bug#736551: [PATCH] Add jQuery FullScreen Plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Apologies, the previous message was obviously intended for another bug report. -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBCAAGBQJS6wWkAAoJEK/ZGpI6kvtMzU4IALjiCPFLB6sjHrdESg1FROCE ix9DqGOoqsx/jcnT0Een5xg5JmOuG2k6nQHD/AFxLpKTZeUkk+9GYh0oOzN23u+M sKpEpJL16bCMUOC0+ISs2dZQ3M0T3ep/LdlDJTL91yyNj7J+gAD4CmUHZhiaMEGr dyHNNlvjGkdl9QB23lnHe9z0Wbe0iYoelJD9XGeZGE5x+7LjA6hOjue9ZkahXXtu 6va8QwBjJQL7RkDU18aVYF4DDk5a6qRpDe3wBIcgdA33q64BkU9qRxb5fl3LJrw/ BXdmrTVjfOLQqddT4GlHnWjVulVr+Kw14XseHM9jHljb/0KOZeF4Cd6Z6RdPe0M= =QP5O -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#728705: gdb fails on s390x with "Couldn't write registers: Invalid argument"
Control: reassign -1 linux 3.2.51-1
Control: affects -1 gdb
Control: notforwarded -1
So, it turns out that the 0x5001 is PTRACE_POKEUSR_AREA, which is
essentially equivalent to PTRACE_POKEUSER in a loop, except for being
less clear when it fails, because you can't tell which word couldn't be
written.
Accordingly, I've replaced the failing call with a loop.
diff --git a/gdb/s390-linux-nat.c b/gdb/s390-linux-nat.c
index ee9b617..de9d956 100644
--- a/gdb/s390-linux-nat.c
+++ b/gdb/s390-linux-nat.c
@@ -248,6 +248,9 @@ store_regs (const struct regcache *regcache, int tid, int regnum)
{
gregset_t regs;
ptrace_area parea;
+#if 1
+ int i;
+#endif
parea.len = sizeof (regs);
parea.process_addr = (addr_t) ®s;
@@ -257,8 +260,17 @@ store_regs (const struct regcache *regcache, int tid, int regnum)
fill_gregset (regcache, ®s, regnum);
+#if 0
if (ptrace (PTRACE_POKEUSR_AREA, tid, (long) &parea) < 0)
perror_with_name (_("Couldn't write registers"));
+#else
+ for (i = 0; i < parea.len; i += sizeof(void *))
+ {
+if (ptrace (PTRACE_POKEUSER, tid, parea.kernel_addr + i,
+ *(void**)(parea.process_addr + i)) < 0)
+ perror_with_name (_("Couldn't write registers"));
+ }
+#endif
}
/* Fetch all floating-point registers from process/thread TID and store
Running "strace -e ptrace gdb -batch -ex start -ex bt --args echo foo"
then results in the failing part looking like:
,
| ptrace(0x5000 /* PTRACE_??? */, 25005, 0x3ad7d80, 0x80073fa0) = 0
| ptrace(0x5000 /* PTRACE_??? */, 25005, 0x3ad7cf0, 0x80074410) = 0
| ptrace(PTRACE_POKEUSER, 25005, psw_mask, 0x705c0018000) = -1 EINVAL
(Invalid argument)
`
However, this same value was just read from that register a bit earlier:
,
| ptrace(PTRACE_PEEKUSER, 25005, psw_mask, [0x705c0018000]) = 0
`
So, this looks like a kernel bug from here.
Kernel stuff
zelenka is currently running linux-image-3.2.0-4-s390x version 3.2.51-1
,[ /proc/cpuinfo ]
| vendor_id : IBM/S390
| # processors: 2
| bogomips per cpu: 9398.00
| features : esan3 zarch stfle msa ldisp eimm dfp etf3eh highgprs
| processor 0: version = FF, identification = 06A18A, machine = 2817
| processor 1: version = FF, identification = 06A18A, machine = 2817
`
While it wasn't exactly easy, I managed to run the kernel bugscript
outside the chroot; the output is attached.
** Version:
Linux version 3.2.0-4-s390x (debian-ker...@lists.debian.org) (gcc version 4.6.3
(Debian 4.6.3-14) ) #1 SMP Debian 3.2.51-1
** Command line:
ro dasd=200-21f vmpoff="LOGOFF" root=/dev/dasdb1 elevator=deadline BOOT_IMAGE=0
** Not tainted
** Kernel log:
[7340394.293000] [30285] 3227 30285 5671 0 0
0 sh
[7340394.293003] [30286] 3227 30286 24196 1 0
0 debuild
[7340394.293006] [30326] 3227 30326 5671 1 0
0 sh
[7340394.293009] [30327] 3227 30327 29388 1 0
0 dpkg-buildpacka
[7340394.293012] [30328] 3227 30328 5360 0 0
0 tee
[7340394.293015] [30507] 3227 30507 5750 0 0
0 rules
[7340394.293018] [30517] 3227 30517 31820 0 0
0 dh
[7340394.293021] [ 3116] 3227 3116 5750 0 0
0 rules
[7340394.293024] [ 3130] 3227 3130 5672 0 0
0 xvfb-run
[7340394.293027] [ 3142] 3227 3142 26904 1 0
0 Xvfb
[7340394.293030] [ 3149] 3227 3149 7070 0 0
0 make
[7340394.293033] [ 5981] 3227 5981 7081 1 0
0 make
[7340394.293036] [ 5984] 3227 5984 1165290 241254 1 0
0 lt-octave-cli
[7340394.293039] [ 7843] 0 7843 1174 65 0 0
0 cron
[7340394.293042] [ 7844] 0 7844 1174 65 0 0
0 cron
[7340394.293045] [ 7845] 0 7845 1173 109 1 0
0 cron
[7340394.293048] [ 7846] 0 7846 1173 114 1 0
0 cron
[7340394.293050] Out of memory: Kill process 5984 (lt-octave-cli) score 961 or
sacrifice child
[7340394.293053] Killed process 5984 (lt-octave-cli) total-vm:4661160kB,
anon-rss:965016kB, file-rss:0kB
[7344121.447118] lt-octave-cli invoked oom-killer: gfp_mask=0x201da, order=0,
oom_adj=0, oom_score_adj=0
[7344121.447124] lt-octave-cli cpuset=/ mems_allowed=0
[7344121.447128] CPU: 0 Not tainted 3.2.0-4-s390x #1 Debian 3.2.51-1
[7344121.447130] Process lt-octave-cli (pid: 21694, task: 3dd7e738,
ksp: 20b1b8d8)
[7344121.447133] 20b1b880 0002
[7344121.447135]20b1b920 20b1b898 20b1b898
003b9c0e
[7344121.447139]003c77c8
000a
[7344121.447142]
Bug#737180: diffutils: diff exit status is 2 instead of 1 on binary files that differ
Package: diffutils Version: 1:3.3-1 Severity: normal When diffing binary files that differ, e.g. $ diff /usr/share/doc/diffutils/changelog.Debian.gz /usr/share/doc/diffutils/changelog.gz Binary files /usr/share/doc/diffutils/changelog.Debian.gz and /usr/share/doc/diffutils/changelog.gz differ zsh: exit 2 diff /usr/share/doc/diffutils/changelog.Debian.gz I get exit status 2 instead of 1. The diff(1) man page says: Exit status is 0 if inputs are the same, 1 if different, 2 if trouble. We are in the case where the inputs are different, so that the exit status should be 1. Because of this bug, "svn diff --force --diff-cmd diff" fails on binary files (ditto on more useful cases in practice, where a diff wrapper is used to recognize some binary files, using the default diff behavior as a fallback). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-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 diffutils depends on: ii libc6 2.17-97 diffutils recommends no packages. Versions of packages diffutils suggests: ii diffutils-doc 1:3.3-1 ii wdiff 1.2.1-2 -- 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#737179: ruby-recaptcha: Build-Depends on obsolete ruby-pkg-tools
Package: ruby-recaptcha Version: 0.3.6-1 Severity: serious Justification: depends on obsolete package Dear Maintainer, Your package "ruby-recaptcha" Build-Depends on ruby-pkg-tools, which is the old, obsolete packaging helper for ruby software. As your package also Build-Depends on gem2deb (the new helper), please remove the dependency on the old ruby-pkg-tools. ruby-pkg-tools will go away really soon now. Thank you, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727708: multiple init systems - formal resolution proposal - Don't like software, don't use it. Absolutely.
2014-01-31 Keith Packard : > Sergey B Kirpichev writes: > [...] >> Where is the list of problems for sysvinit we intend to solve? > > For X, the problem is running X as a user other than root, which should > provide for increased system security as we'll be reducing the amount of > root code substantially. Using the systemd mechanisms for sending new > input devices to the X server solves one of the longstanding issues with > non-root X. I was referring to that - of course X does not depend on systemd, but systemd provides features which make it possible to fix existing issues, that's why it makes sense to use it. Of course it does not exclude implementing that stuff in a different, non-systemd tool, but to my knowledge nobody has done that yet. Thank you for working on X and clarifying this! Matthias -- I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#731095: Please consider switching tablesorter to alternate upstream
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Several packages in Debian depend on libjs-jquery-tablesorter. Are you confident that switching to a fork wouldn't negatively impact these packages? libjs-jquery-tablesorter Reverse Depends: libprophet-perl libjs-twitter-bootstrap python3-coverage python-coverage phpmyadmin openteacher -- Jerome -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBCAAGBQJS6wJJAAoJEK/ZGpI6kvtM2BoIAJs57OGnB6tx3mLNqMdhVwTo 5nBeKus2A3Eie7cQSv9Ccm+F9GfqeSaq/3ol7zusDeL7SoqULz25HlnWY2tXAcIA XyHJOnRErUgD3Xe3EegsnGIgQm4V0ocNEAKaYgZarTskQHTqNEYqT/i6p8LbIyqx RqYC0CzzkQn46pGUayywlQMK3jLCD+tOvDoRLN+gFarhUBQVuB4kfbjHw+l6E20f LLkUvkWwbVUO+BcbJ+AMHGPHLb2xd8tgGbbZKs/9aj+MhCtcQ0AfoAHq5PyMtoaw 7BQQ/M+ymuZPiyhJ/TQIhOY2COVQ1MJ7ltLdqwU35SN+PJPQJheatlJr1XOgiXY= =dbuN -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#727708: init system resolution - revised proposal
Petr Baudis writes: > Would such a particular example of (greatly, but not fatally) degraded > operation fall within the intent of this proposal? I think so, yes. I do think forcing users who've made a conscious decision to live this way to click through a warning pop-up on each login is rather unkind, though. If some mechanism were provided to mark such a thing as "yes, I've seen this warning, don't bother me again" until perhaps the next GNOME version upgrade, that would seem like a much better way to treat such users. Bdale pgpkXCG4Ng6Hu.pgp Description: PGP signature
Bug#737178: [python-ntdb] "fileformat" in extended description
Package: python-ntdb Version: 1.0-2 Severity: minor The extended description contains: ntdb uses a fileformat that is incompatible with tdb, but the API is similar. A space is missing in "fileformat". By the way, in the next sentence, "4Gb" is also missing a space. -- Filipus Klutiero http://www.philippecloutier.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729002: Version 1.3.4-1 released
Please note I just released version 1.3.4-1 which is the newest stable version. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/xfce4-equake-plugin Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/x/xfce4-equake-plugin/xfce4-equake-plugin_1.3.4-1.dsc More information about xfce4-equake-plugin can be obtained from http://www.e-quake.org or http://freecode.com/projects/equake-xfce Changes since the last upload: * Added display of earthquakes of the past seven days * Added map links to last hour/day/week windows * Added local time in addition to UTC for earthquake events * Improved processing of the date and time * Various minor fixes and code cleanup -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737111: Same bug?
Hi Adrien, That looks like a fairly generic backtrace, not related to the crash Lorin posted. I don't think it's related to this bug report. Cheers, Jelmer signature.asc Description: Digital signature
Bug#737176: nginx: Adjust gzip_types in debian/conf/nginx.conf
Package: nginx Version: 1.1.19-1ubuntu0.5 Severity: minor Dear Maintainer, The gzip_types directive in debian/conf/nginx.conf includes application/x-javascript and text/javascript but not application/javascript (without the x). The latter is also valid, and I suggest that you add it to the list. In fact, nginx uses application/javascript for .js files today: http://hg.nginx.org/nginx/rev/ae3fd1ca62e0 Best regards Thomas -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise'), (100, 'precise-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.8.0-29-generic (SMP w/1 CPU core) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nginx depends on: ii nginx-full 1.1.19-1ubuntu0.5 nginx recommends no packages. nginx 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#737177: [PATCH] Use uglifyjs to compress JavaScript instead of yui-compressor
Package: src:jquery-goodies Version: 8-2 Severity: normal As announced on the YUI blog some time ago, yui-compressor is now deprecated in favor of UglifyJS. http://www.yuiblog.com/blog/2012/10/16/state-of-yui-compressor/ Here's a patch to replace the use of yui-compressor with uglifyjs when compressing JavaScript files at build-time. -- Jerome --- debian/control | 2 +- debian/rules | 48 2 files changed, 25 insertions(+), 25 deletions(-) diff --git a/debian/control b/debian/control index 914a50c..f8f62ef 100644 --- a/debian/control +++ b/debian/control @@ -5,7 +5,7 @@ Maintainer: Debian Javascript Maintainers , Per Andersson , Agustin Henze -Build-Depends: debhelper (>= 7.0.50~), yui-compressor +Build-Depends: debhelper (>= 7.0.50~), node-uglify Standards-Version: 3.9.4 Vcs-Browser: http://git.debian.org/?p=pkg-javascript/jquery-goodies.git Vcs-Git: git://git.debian.org/git/pkg-javascript/jquery-goodies.git diff --git a/debian/rules b/debian/rules index 4edbfeb..7845ea5 100755 --- a/debian/rules +++ b/debian/rules @@ -3,30 +3,30 @@ dh $@ override_dh_auto_build: - yui-compressor event-drag/jquery.event.drag.js -o event-drag/jquery.event.drag.min.js - yui-compressor event-drop/jquery.event.drop.js -o event-drop/jquery.event.drop.min.js - yui-compressor easing/jquery.easing.js -o easing/jquery.easing.min.js - yui-compressor easing/jquery.easing.compatibility.js -o easing/jquery.easing.compatibility.min.js - yui-compressor galleriffic/js/jquery.galleriffic.js -o galleriffic/js/jquery.galleriffic.min.js - yui-compressor meiomask/jquery.meiomask.js -o meiomask/jquery.meiomask.min.js - yui-compressor mousewheel/jquery.mousewheel.js -o mousewheel/jquery.mousewheel.min.js - yui-compressor jquery-history/jquery.history.js -o jquery-history/jquery.history.min.js - yui-compressor opacityrollover/jquery.opacityrollover.js -o opacityrollover/jquery.opacityrollover.min.js - yui-compressor jush/jush.js -o jush/jush.min.js - yui-compressor jfeed/build/dist/jquery.jfeed.js -o jfeed/build/dist/jquery.jfeed.min.js - yui-compressor form/jquery.form.js -o form/jquery.form.min.js - yui-compressor tipsy/src/javascripts/jquery.tipsy.js -o tipsy/src/javascripts/jquery.tipsy.min.js - yui-compressor fancybox/jquery.fancybox.js -o fancybox/jquery.fancybox.min.js - yui-compressor cookie/jquery.cookie.js -o cookie/jquery.cookie.min.js - yui-compressor metadata/jquery.metadata.js -o metadata/jquery.metadata.min.js - yui-compressor tablesorter/jquery.tablesorter.js -o tablesorter/jquery.tablesorter.min.js - yui-compressor tablesorter/addons/pager/jquery.tablesorter.pager.js -o tablesorter/addons/pager/jquery.tablesorter.pager.min.js - yui-compressor treetable/src/jquery.treeTable.js -o treetable/src/jquery.treeTable.min.js - yui-compressor livequery/jquery.livequery.js -o livequery/jquery.livequery.min.js - yui-compressor countdown/jquery.countdown.js -o countdown/jquery.countdown.min.js - yui-compressor resize/jquery.ba-resize.js -o resize/jquery.ba-resize.min.js - yui-compressor uploadify/jquery.uploadify.js -o uploadify/jquery.uploadify.min.js - yui-compressor slides/source/slides.jquery.js -o slides/source/slides.min.jquery.js + uglifyjs -o event-drag/jquery.event.drag.min.js event-drag/jquery.event.drag.js + uglifyjs -o event-drop/jquery.event.drop.min.js event-drop/jquery.event.drop.js + uglifyjs -o easing/jquery.easing.min.js easing/jquery.easing.js + uglifyjs -o easing/jquery.easing.compatibility.min.js easing/jquery.easing.compatibility.js + uglifyjs -o galleriffic/js/jquery.galleriffic.min.js galleriffic/js/jquery.galleriffic.js + uglifyjs -o meiomask/jquery.meiomask.min.js meiomask/jquery.meiomask.js + uglifyjs -o mousewheel/jquery.mousewheel.min.js mousewheel/jquery.mousewheel.js + uglifyjs -o jquery-history/jquery.history.min.js jquery-history/jquery.history.js + uglifyjs -o opacityrollover/jquery.opacityrollover.min.js opacityrollover/jquery.opacityrollover.js + uglifyjs -o jush/jush.min.js jush/jush.js + uglifyjs -o jfeed/build/dist/jquery.jfeed.min.js jfeed/build/dist/jquery.jfeed.js + uglifyjs -o form/jquery.form.min.js form/jquery.form.js + uglifyjs -o tipsy/src/javascripts/jquery.tipsy.min.js tipsy/src/javascripts/jquery.tipsy.js + uglifyjs -o fancybox/jquery.fancybox.min.js fancybox/jquery.fancybox.js + uglifyjs -o cookie/jquery.cookie.min.js cookie/jquery.cookie.js + uglifyjs -o metadata/jquery.metadata.min.js metadata/jquery.metadata.js + uglifyjs -o tablesorter/jquery.tablesorter.min.js tablesorter/jquery.tablesorter.js + uglifyjs -o tablesorter/addons/pager/jquery.tablesorter.pager.min.js tablesorter/addons/pager/jquery.tablesorter.pag
Bug#727708: init system resolution - revised proposal
Ian Jackson writes: > Ian, Bdale, Andy, Don and Russ agreed on IRC that this was a good > ballot. Steve, Colin, Keith: let us know, and perhaps we can start > the vote sooner. I can vote with this ballot. Sorry I had to disappear in the middle of the meeting; that all turned out for naught as the flight I was on got canceled, and I'll be home for the weekend after all. -- keith.pack...@intel.com pgpGZ9uHiAIDM.pgp Description: PGP signature
Bug#736551: [PATCH] Add jQuery FullScreen Plugin
Tags: patch
Here's a patch against the jquery-goodies' source code Git tree.
---
debian/control | 11 ++
debian/copyright | 6 ++
debian/libjs-jquery-fullscreen.README.Debian | 13 +++
debian/libjs-jquery-fullscreen.docs | 1 +
debian/libjs-jquery-fullscreen.install | 1 +
debian/rules | 6 ++
fullscreen/jquery.fullscreen.js | 147 +++
fullscreen/readme.md | 75 ++
8 files changed, 260 insertions(+)
create mode 100644 debian/libjs-jquery-fullscreen.README.Debian
create mode 100644 debian/libjs-jquery-fullscreen.docs
create mode 100644 debian/libjs-jquery-fullscreen.install
create mode 100644 fullscreen/jquery.fullscreen.js
create mode 100644 fullscreen/readme.md
diff --git a/debian/control b/debian/control
index 914a50c..3af8f2d 100644
--- a/debian/control
+++ b/debian/control
@@ -316,3 +316,14 @@ Description: Simple slideshow plugin for jQuery
A simple slideshow plugin for jQuery packed with a useful set of features to
help novice and advanced developers alike create elegant and user-friendly
slideshows.
+
+Package: libjs-jquery-fullscreen
+Architecture: all
+Depends: ${misc:Depends}, libjs-jquery
+Recommends: javascript-common
+Homepage: http://tutorialzine.com/2012/02/enhance-your-website-fullscreen-api/
+Description: jQuery FullScreen Plugin
+ A jQuery 1.7 plugin that wraps around the Full Screen API and works around
+ various browser differences. Works in FF 10, Chrome and Safari. It is useful
+ for presenting users with an easier to read version of your web pages, or
+ zooming and elements.
diff --git a/debian/copyright b/debian/copyright
index 10cafbd..078d2f4 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -106,6 +106,12 @@ Files: slides/*
Copyright: 2011 Nathan Searles, http://nathansearles.com
License: Apache-2.0
+Files: fullscreen/*
+Copyright: 2012 Martin Angelov
+Homepage: http://tutorialzine.com/2012/02/enhance-your-website-fullscreen-api/
+License: Expat
+Source: https://github.com/martinaglv/jQuery-FullScreen/issues/13
+
Files: debian/*
Copyright: (c) 2009-2011 Marcelo Jorge Vieira
License: MIT or GPL-2+ or BSD or Apache-2.0
diff --git a/debian/libjs-jquery-fullscreen.README.Debian
b/debian/libjs-jquery-fullscreen.README.Debian
new file mode 100644
index 000..35e78ef
--- /dev/null
+++ b/debian/libjs-jquery-fullscreen.README.Debian
@@ -0,0 +1,13 @@
+libjs-jquery-fullscreen for Debian
+--
+
+In order to make use of fullscreen in your html, include the following
+lines in your html header
+
+
+
+
+
+ -- Jerome Charaoui , Sun, 26 Jan 2014 19:41:54 -0500
diff --git a/debian/libjs-jquery-fullscreen.docs
b/debian/libjs-jquery-fullscreen.docs
new file mode 100644
index 000..c97d3b7
--- /dev/null
+++ b/debian/libjs-jquery-fullscreen.docs
@@ -0,0 +1 @@
+fullscreen/readme.md
diff --git a/debian/libjs-jquery-fullscreen.install
b/debian/libjs-jquery-fullscreen.install
new file mode 100644
index 000..1e23cc1
--- /dev/null
+++ b/debian/libjs-jquery-fullscreen.install
@@ -0,0 +1 @@
+fullscreen/jquery.fullscreen.js /usr/share/javascript/jquery-fullscreen
diff --git a/debian/rules b/debian/rules
index 4edbfeb..e33ee42 100755
--- a/debian/rules
+++ b/debian/rules
@@ -27,6 +27,7 @@ override_dh_auto_build:
yui-compressor resize/jquery.ba-resize.js -o
resize/jquery.ba-resize.min.js
yui-compressor uploadify/jquery.uploadify.js -o
uploadify/jquery.uploadify.min.js
yui-compressor slides/source/slides.jquery.js -o
slides/source/slides.min.jquery.js
+ yui-compressor fullscreen/jquery.fullscreen.js -o
fullscreen/jquery.fullscreen.min.js
override_dh_installchangelogs:
dh_installchangelogs --package libjs-jquery-livequery
livequery/ChangeLog.markdown
@@ -59,3 +60,8 @@ override_dh_auto_clean:
rm -f resize/jquery.ba-resize.min.js
rm -f uploadify/jquery.uploadify.min.js
rm -f slides/source/slides.min.jquery.js
+ rm -f fullscreen/jquery.fullscreen.min.js
+
+override_dh_gencontrol:
+ dh_gencontrol -plibjs-jquery-fullscreen -- -v1.2
+ dh_gencontrol --remaining-packages
diff --git a/fullscreen/jquery.fullscreen.js b/fullscreen/jquery.fullscreen.js
new file mode 100644
index 000..78499f0
--- /dev/null
+++ b/fullscreen/jquery.fullscreen.js
@@ -0,0 +1,147 @@
+/**
+ * @namejQuery FullScreen Plugin
+ * @author Martin Angelov, Morten Sjøgren
+ * @version 1.2
+ * @url
http://tutorialzine.com/2012/02/enhance-your-website-fullscreen-api/
+ * @license MIT License
+ */
+
+/*jshint browser: true, jquery: true */
+(function($){
+ "use strict";
+
+ // These helper functions available only to our plugin scope.
+ function supportFullScreen(){
+ var doc = document.documentElement;
+
+ return ('requestFulls
Bug#727708: multiple init systems - formal resolution proposal - Don't like software, don't use it. Absolutely.
Sergey B Kirpichev writes: > Are X-people indeed sacrifice portability, or there is something > different (e.g. these dependencies are optional)? Speaking as the X server release manager, the systemd patches exist solely to provide for interoperation with systemd or other similar device management processes. None of them eliminate existing device management infrastructure at all. In effect, X takes the Debian position that patches which improve interoperabilty with a specific init system should be integrated. X is most definitely not going to ever require systemd. I think that any package which requires a specific init system is broken and I'd work to fix any that I depended on. > Where is the list of problems for sysvinit we intend to solve? For X, the problem is running X as a user other than root, which should provide for increased system security as we'll be reducing the amount of root code substantially. Using the systemd mechanisms for sending new input devices to the X server solves one of the longstanding issues with non-root X. -- keith.pack...@intel.com pgpufbogLJ_GB.pgp Description: PGP signature
Bug#716723: sasl2-bin: subprocess installed post-installation script returned error exit status 1
On Thu, Jan 30, 2014 at 05:36:05PM +0100, Johannes Schlumberger wrote: > Hi Roberto, > thank you for looking into this. I will send you a link to the sasldb2 file > in a > personal separate email for you investigation (would you please provide me > with > an address?). Please keep the contents of this file private. You may share the > contents and the file with other package maintainers or who else you see fit > to > work on this bug, provided they also keep it private. Johannes, I believe that I have figured out the problem. It appears that you created the sasldb2 file on a big endian machine and then later moved it to a little endian machine. This causes the upgrade to fail. Here is what happens on my amd64 system: roberto@miami:/var/lib/chroot/squeeze/etc$ sudo db5.1_upgrade sasldb2 db5.1_upgrade: sasldb2: DB->upgrade only supported on native byte-order systems db5.1_upgrade: DB->upgrade: sasldb2: Invalid argument roberto@miami:/var/lib/chroot/squeeze/etc$ file sasldb2 sasldb2: Berkeley DB (Hash, version 8, big-endian) I temporarily transferred the file over to a PowerPC porterbox, and here is what happens: (sid_powerpc-dchroot)roberto@partch:~$ db5.1_upgrade sasldb2 (sid_powerpc-dchroot)roberto@partch:~$ logout roberto@partch:~$ file sasldb2 sasldb2: Berkeley DB (Hash, version 9, native byte-order) Based on this, I believe that this is not a bug in the sasl2-bin package. I believe that you can correct this by dumping the contents using the db4.8_dump command and then recreating the database on your system. If you agree, I would like to close this bug report. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Bug#727708: init system resolution - revised proposal
Hi! Apologies for jumping into the discussion even though I'm not a Debian Developer. > == dependencies rider version L (Loose coupling) == > >This decision is limited to selecting a default initsystem; we >continue to welcome contributions of support for all init systems. > >Software outside of an init system's implementation may not require >a specific init system to be pid 1, although degraded operation is >tolerable. > >Maintainers are encouraged to accept technically sound patches >to enable improved interoperation with various init systems. I'd just like to clarify - say we have a scenario (that I assume might be realistic) where without systemd, locking screen in GNOME and some other fairly basic features do not work (have unfixed bugs, possibly with security implications; possibly these features would be entirely disabled because of that). GNOME would also display a warning window on login notifying the user that for a proper GNOME experience, they should switch their system to systemd. Some *gnome* packages would have Recommends: systemd. (Nevertheless, installing (major components of) GNOME might still be useful for users that do not wish to use the complete desktop environment but perhaps would want to install a variety of GNOME applications or work around these issues in their special-purpose environment.) Would such a particular example of (greatly, but not fatally) degraded operation fall within the intent of this proposal? Thanks, Petr "Pasky" Baudis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737047: postfix-policyd-spf-python: Missing depends on python-dns
I'm not sure how this can happen. Python-spf (which is what's importing DNS) depends on python-dns. Scott K
Bug#737175: mate-power-manager does not fully take over default system hotkeys (like the s2ram button)
Package: mate-power-manager Version: 1.6.1-1 Severity: normal Dear Maintainer, it appears that mate-power-manager does a duplicit handling of the system hotkeys like the "suspend to RAM" notebook button. If in mate-power-manager we enable "when the suspend button is pressed" -> "suspend" and press the key, the notebook suspends but on wakeup suspends *again*. And when we select "do nothing", the system suspends once (but does not lock the screen). That is also a workaround to others who experience the "double suspend" bug which can be fairly annoying. It is also possible some other daemon does rogue processing of the hotkeys in the Mate session, but I have a fairly usual (migrated from Cinnamon) notebook setup. If you have any ideas on how to detect that, I'll gladly try. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=cs_CZ.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mate-power-manager depends on: ii consolekit 0.4.6-3+b1 ii dbus-x11 1.7.10-2 ii libatk1.0-02.10.0-2 ii libc6 2.17-97 ii libcairo2 1.12.16-2 ii libcanberra-gtk0 0.30-2 ii libcanberra0 0.30-2 ii libdbus-1-31.7.10-2 ii libdbus-glib-1-2 0.100.2-1 ii libfontconfig1 2.11.0-2 ii libfreetype6 2.5.2-1 ii libgdk-pixbuf2.0-0 2.28.2-1+b1 ii libglib2.0-0 2.36.4-1 ii libgtk2.0-02.24.22-1 ii libmatekeyring 1.6.0-1 ii libmatepanelapplet 1.6.0-2.1+8.jessie ii libnotify4 0.7.6-1 ii libpango1.0-0 1.36.0-1+b1 ii libunique-1.0-01.1.6-4 ii libupower-glib10.9.23-2+b1 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxrandr2 2:1.4.2-1 ii libxrender11:0.9.8-1 ii mate-power-manager-common 1.6.1-1 ii notification-daemon0.7.6-1 ii upower 0.9.23-2+b1 Versions of packages mate-power-manager recommends: ii udisks 1.0.4-8+b1 Versions of packages mate-power-manager suggests: ii policykit-1 0.105-4 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735516: python-liblas: hardcoded dependency on liblas1 which is no longer built by liblas
Hi Sebastian, Thanks for reporting this issue. Upstream version 1.6.0 is available at pypi, but liblas has version 1.7.0. It looks like the python directory from liblas is repackaged for pypi, the code for version 1.6.0 is identical, the python directory in liblas has additional tests and examples and no egg-info. I think the wise choice is to build python-liblas from the liblas source package instead of maintaining the pypi based pyton-liblas source package separately. So they will be updated together in the future. Kind Regards, Bas -- GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727708: init system resolution - revised proposal
On Thu, 30 Jan 2014, Josh Triplett wrote: > Ian Jackson wrote: > >Software outside of an init system's implementation may not require > >a specific init system to be pid 1, although degraded operation is > >tolerable. > > For instance, consider a gnome-session-systemd package which uses > systemd user sessions, provided in parallel with a compatibility > package that does not. Or, consider the systemd-shim package. As > written, this clause would prohibit such alternative packages, even > though *collectively* the packages satisfy this requirement. Using "software" instead of "packages" sidesteps this problem, I think, since that avoids the technical details of how such compatibility is implemented. -- Don Armstrong http://www.donarmstrong.com Have you ever noticed: the most vocal superpatriots are the old men who send young men out to die. -- Harlan Ellison "Basilisk" (_Deathbird Stories_ p73) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737168: apt-listbugs breaks, preventing package installation
On 31 January 2014 12:04, Francesco Poli wrote: > Hello Brendon, > [...] > I see that you are running a highly mixed system > (stable/testing/unstable/experimental, with a preference for packages > coming from stable). > These mixed systems may work correctly, but require some care... > I rarely install packages from unstable or experimental. They are enabled primarily for updating rapidly evolving packages, e.g. wine. I prefer to keep most packages from stable, upgrading to testing strictly as required. I am currently running libc6, xorg, nvidia, and kde-full from testing. > > Anyway, please read > http://bugs.debian.org/735116#10 > for the suggested procedure to fix the issue. Thank you. I found it sufficient to install ruby1.9.1/1.9.3.194-8.1+deb7u2 from stable. I could not remove ruby1.8, as it is pulled in as a dependency of apt-listbugs/0.1.8+deb7u1. Since apt-listbugs/0.1.8+deb7u1 does not appear to work with the interpreter that was provided by ruby1.8/1.8.7.358-7.1+deb7u1, this is perhaps a packaging bug that requires fixing?
Bug#737126: Bug#736656: libdbi-drivers: drivers not found anymore, due to multi-arch
Prach Pongpanich writes:
> On Thu, Jan 30, 2014 at 9:16 PM, Markus Hoenicka
> wrote:
> [..]
>
> >> It's got the same result as without "-fsigned-char". :(
> >
> >
> > Ok, maybe this change alone was not sufficient. I went through the changes
> > between the latest 0.8.x release (where things apparently still worked) and
> > 0.9, and I suspect that we need some of the configure magic that was
> > cleaned
> > out before 0.9. Could you please test the appended patches against
> > configure.ac of both libdbi and libdbi-drivers? To fix the problem, we may
> > have to fiddle with both packages at a time.
> >
>
> (Cc:-ing #737126)
>
> That reduced failures, but still remain the issue with "the_float" and
> "the_double".
>
> Running "libdbi framework test"...
> test_dbi.c:3732: unit test failure: sqlite3 -> libdbi connection ->
> Retrieving fields as -> test_dbi_result_get_as_longlong -> [-1] should
> match [0] at [test_dbi.c] line [3732]
> test_dbi.c:3733: unit test failure: sqlite3 -> libdbi connection ->
> Retrieving fields as -> test_dbi_result_get_as_longlong -> [-1] should
> match [0] at [test_dbi.c] line [3733]
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Completed "libdbi framework test": 397 passes, 2 failures, 0 exceptions.
> make: *** [test-stamp] Error 1
>
> --
> Prach
>
Ok, seems we're halfway there. It is certainly worth checking all the
compiler warnings that Laszlo mentioned. But the above mentioned
failures may be related to the way how libdbi converts floating
point numbers to long long values. Prach, could you please run the
test program below and report any compiler warnings as well as the
output on armel?
regards,
Markus
float2longlong.c
--8<
#include
#include
int main() {
float bigfloat = 3.402823e+38;
long long bigfloat_casted;
bigfloat_casted = (long long)bigfloat;
printf("%lld\n", bigfloat_casted);
exit (0);
}
--
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727708: init system resolution - revised proposal
A couple of comments inline below. Ian Jackson wrote: > == dependencies rider version T (Tight coupling) == > >This decision is limited to selecting a default initsystem; we >continue to welcome contributions of support for all init systems. > >Software may require a specific init system to be pid 1. > >However, where feasible, software should interoperate with >all init systems; maintainers are encouraged to accept >technically sound patches to enable interoperation, even if it >results in degraded operation while running under the init system >the patch enables interoperation with. > > == dependencies rider version L (Loose coupling) == > >This decision is limited to selecting a default initsystem; we >continue to welcome contributions of support for all init systems. > >Software outside of an init system's implementation may not require >a specific init system to be pid 1, although degraded operation is >tolerable. There is an issue with this wording, which I don't think is intended. Sometimes, the easiest way to maintain support for multiple init systems involves having a family of packages, each of which enables support for one init system or family of init systems. For instance, consider a gnome-session-systemd package which uses systemd user sessions, provided in parallel with a compatibility package that does not. Or, consider the systemd-shim package. As written, this clause would prohibit such alternative packages, even though *collectively* the packages satisfy this requirement. I would suggest adding language like the following, optionally with the following [non-binding] example: Packages which form part of a set of alternatives integrating with different init systems need not individually run on other init systems, as long as the packages collectively meet the requirements of this section. [ For example, a package using systemd to launch a user session, provided as an alternative to a package that runs on sysvinit, need not itself run on sysvinit. ] - 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#736092: [Pkg-systemd-maintainers] Bug#736092: closed by Michael Stapelberg (fixed with lvm2 2.02.104-1)
Am 31.01.2014 00:11, schrieb Guillaume Seren: > Hi, > I can confirm that the new version of LVM in SID fix the bug > (2.02.104-1 0), > it is now working well thank you. Glad to hear that. > Any idea about why it was not working in my local patched version ? It seems you actually didn't apply the patch. Just copying the patch file to debian/patches/ is not sufficient. -- 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#737173: lynis: Added test to tests_filesystems for Ecryptfs (Additional Info)
Hi, Forgot to mention that I've tested these patches with version 1.3.9 on Debian Jessie and Sid. I've also downloaded version 1.4.0 from the upstream site and verified that these patches should work with it as well. -- Dave Vehrs dve...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737174: gitolite 2 is broken by git 1.9-rc0 and newer
Package: gitolite
Version: 2.3-1
Severity: important
Tags: upstream patch
gl-compile-conf breaks with git 1.9-rc0 and newer ("* AAARGH! *
your git version is older than 1.6.6"). Luckily Debian package
dependencies mean we don't need a version check at all, so how about
this patch?
Suggested by sitaramc[1].
[1] http://thread.gmane.org/gmane.comp.version-control.git/241151/focus=241284
---
Thanks,
Jonathan
src/gl-compile-conf | 23 ---
1 file changed, 23 deletions(-)
diff --git a/src/gl-compile-conf b/src/gl-compile-conf
index f497ae5..eb96d95 100755
--- a/src/gl-compile-conf
+++ b/src/gl-compile-conf
@@ -382,29 +382,6 @@ parse_conf_file($GL_CONF, 'master');
#
#
-# what's the git version?
-#
-
-# we don't like stuff older than 1.6.6
-
-my $git_version = `git --version`;
-die "
-*** ERROR ***
-did not get a proper version number. Please see if git is in the PATH on
-the server. If it is not, please edit ~/.gitolite.rc on the server and
-set the \$GIT_PATH variable to the correct value\n
-" unless $git_version;
-my ($gv_maj, $gv_min, $gv_patchrel) = ($git_version =~ m/git version
(\d+)\.(\d+)\.(\d+)/);
-die "$ABRT I can't understand $git_version\n" unless ($gv_maj >= 1);
-$git_version = $gv_maj*1 + $gv_min*100 + $gv_patchrel; # now it's
"normalised"
-
-die "\n\t\t* AAARGH! *\n" .
-"\tyour git version is older than 1.6.6\n" .
-"\tsince that is now more than one year old, and gitolite needs some of\n"
.
-"\tthe newer features, please upgrade.\n"
-if $git_version < 10606; # that's 1.6.6 to you
-
-#
# most of the rest of this program can be "switched off"; see
# doc/big-config.mkd for details.
#
--
1.9.rc1.175.g0b1dcb5
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727708: multiple init systems - formal resolution proposal - Don't like software, don't use it. Absolutely.
On Thu, Jan 30, 2014 at 12:04 PM, Ian Jackson wrote: >> What would be the effecr if we decided to drop GNOME, because it >> depends on systemd? > > In this hypothetical scenario: > > It would be fairly easy for a downstream of Debian to mandate systemd > for their users, and provide Gnome. > > It would not be anywhere near as easy for a downstream of Debian to > undo the assumption by Debian (de facto or de jure) of systemd as the > one true init system. > > If it comes down to it I would prefer to drop Gnome than to make > systemd mandatory for all of Debian's users and downstreams just > because Gnome had introduced a hard dependency on systemd. > > Luckily this is all hypothetical. The only hypothetical situation that would result in dropping gnome is one where the TC enacts language barring dependencies on non-default init systems. In all other cases systemd remains in debian, and gnome can remain by using systemd. So, to lets take a step back from this hypothetical cliff by removing that idea from the discussion. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737173: lynis: Added test to tests_filesystems for Ecryptfs
Package: lynis
Version: 1.3.9-1
Severity: normal
Dear Maintainer,
I've put together a pair of short patches for your consideration.
Patches add tests that check if Ecryptfs is installed and if it is, then
checks if ecryptfs-migirate-home (or other method) has been used to
configure each user's home directory (UID >= 500 && != 65534) to use it.
I believe the use of Ecryptfs could be valuable for anyone using a
laptop or any system with multiple users. This could add to the
hardened status of the system that Lynis is testing for many users.
The patch I've worked up is missing a test number (FILE-) that the
other tests have and may need to be submitted upstream to get one.
What do you think, would this be a worthwhile addition to Lynis?
Thanks,
Dave Vehrs
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-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
lynis depends on no packages.
Versions of packages lynis recommends:
ii menu 2.1.46
Versions of packages lynis suggests:
ii dnsutils 1:9.8.4.dfsg.P1-6+nmu3
-- no debconf information
--
Dave Vehrs dve...@gmail.com
--- binaries.orig 2014-01-27 17:31:06.193667725 -0700
+++ binaries 2014-01-28 20:24:33.913326347 -0700
@@ -69,6 +69,8 @@
dig)if [ -f ${BINARY} ]; then DIGFOUND=1; DIGBINARY=${BINARY}; logtext " Found known binary: dig (network/dns tool) - ${BINARY}";fi ;;
dnsdomainname) DNSDOMAINNAMEFOUND=1; DNSDOMAINNAMEBINARY="${BINARY}"; logtext " Found known binary: dnsdomainname (DNS domain) - ${BINARY}";;
domainname) DOMAINNAMEFOUND=1; DOMAINNAMEBINARY="${BINARY}"; logtext " Found known binary: domainname (NIS domain) - ${BINARY}" ;;
+ecryptfsd) ECRYPTFSDFOUND=1; ECRYPTFSDBINARY="${BINARY}"; logtext " Found known binary: ecryptfsd (Layered Encryption) - ${BINARY}" ;;
+ecryptfs-migrate-home) ECRYPTFSMIGRATEFOUND=1; ECRYPTFSMIGRATEBINARY=${BINARY}; logtext " Found known binary: ecryptfs-migrate-home (Layered Encryption) - ${BINARY}" ;;
exim) EXIMFOUND=1; EXIMBINARY="${BINARY}"; EXIMVERSION=`${BINARY} -bV | grep 'Exim version' | awk '{ print $3 }' | xargs`; logtext "Found ${BINARY} (version ${EXIMVERSION})" ;;
find) FINDFOUND=1; FINDBINARY="${BINARY}";logtext " Found known binary: find (search tool) - ${BINARY}";;
g++)GPLUSPLUSFOUND=1; GPLUSPLUSBINARY="${BINARY}";COMPILER_INSTALLED=1; logtext " Found known binary: g++ (compiler) - ${BINARY}";;
--- tests_filesystems.orig 2014-01-27 17:20:14.749679392 -0700
+++ tests_filesystems 2014-01-29 16:20:52.128727221 -0700
@@ -558,6 +558,72 @@
#
#
+# Test: FILE-
+# Description : (LINUX) Check if user home directories are encrypted with ecryptfs
+# Notes : Ecryptfs is useful on multi-user systems. Can be configured
+# so that files in the users home directories are only
+# decrypted while the user is logged in.
+#
+# This function adds hardening points according to the
+# following criteria:
+# +1 Ecryptfs Installed
+# +1 for each user account that can be configured to use it.
+if [ "${OS}" = "Linux" ]; then
+if [ ! "${ECRYPTFSDBINARY}" = "" ]; then PREQS_MET="YES"; else PREQS_MET="NO"; fi
+Register --test-no "FILE-" --os Linux --preqs-met ${PREQS_MET} --weight L --network NO --description "Checking for Ecryptfs"
+if [ ${SKIPTEST} -eq 0 -a ! "${ECRYPTFSDBINARY}" = "" ]; then
+Display --indent 2 --text "- Ecryptfs" --result INSTALLED --color GREEN
+logtext "Ecryptfs installed."
+logtext "Test: If user home directories are configured to use Ecryptfs"
+AddHP 1 1
+USERLIST=
Bug#574947: Is any update planned for Global?
It's been more than 7 years(?!) since global has been updated on Debian. Ron, could you please state the reasons why this update is being held back? Thanks, -- Pranith
Bug#570611: ITP: mythtv -- A personal video recorder application
+++ Mark Purcell [2014-01-25 12:55 +1100]: > >This is the right place for discussion about getting mythtv into Debian. > >Thanks for this work it looks useful but I won't be able to have good look >for a few days. > >The two critical issues are : > >1. Does it build against the Depends from Debian only, and yes. >2. Does all the code within the upstream mythtv base meet the DFSG? Good question. I note that there is over 350MB of it(!). I hope that's mostly graphics, but of course those have licences too. >We have a team setup on [2]alioth.debian.org called pkg-mythtv which >hasn't seen a lot of attention recent days, including an svn archive. >Please login to alioth and request membership of that team and I can grant >you commit access. done. I tested the packages I built and they seem to work nicely. The initscript does its job. I did get a hang in the video after an hour or so. No idea which component is causing an issue there. I'll try them on my real box next week. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#718432: Debian bug 718432
On Thu, 30 Jan 2014 17:42:49 +0100, Fernando Santagata wrote: > Sorry for my lack of interaction: after some time everything started to > work fine again. I saw that the bug was in state "closed" and I didn't > think to write back to you. #718432 isn't closed in the Debian BTS [0], but if you don't see the issues anymore, we should probably close it :) Cheers, gregor [0] and neither is the upstream bug at https://rt.cpan.org/Public/Bug/Display.html?id=91740 -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Pink Floyd: On the Turning Away signature.asc Description: Digital signature
Bug#737172: doc-base: if old package version installed duplicate doc-base files, upgrades fail
Olly Betts wrote: > It looks like doc-base is confused from trying to process the two identical > files when 1.2.15-4 was installed. > > I've discovered that running install-docs -R before upgrading ruby-xapian and > install-docs -I afterwards makes things run smoothly, so perhaps I should > automate that in the maintainer scripts if they detect an upgrade from a bad > version and install-docs is installed. Then we can just reassign this bug to > doc-base as it shouldn't really need manual intervention in this situation. I found a slightly cleaner (though still nasty) workaround, now implemented in xapian-bindings 1.2.17-1. The preinst overwrites one of the duplicate doc-base files in /usr/share/doc-base with a dummy version with a unique "Document:" field, and then calls install-docs -i with the filenames of the two previously identical files in /usr/share/doc-base, which is enough to get doc-base back into a sane state. To stop install-docs being a no-op, it temporarily sets DPKG_MAINTSCRIPT_PACKAGE=doc-base while running it (ick). It would be much better if doc-base handled upgrading from this situation cleanly - currently the user either needs to intervene (and what to do isn't obvious) or packages need to add nasty workarounds to make upgrades work. It may seem dumb to have created this situation in the first place, but if you don't have doc-base installed, you don't get any error or warning, so it's easy for the maintainer to miss. In my case I had a template foo.docbase.in file in the source package, which got installed by dh_installdocs (because it matches debian/package.doc-base.*). Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#718190: [Pkg-systemd-maintainers] Bug#718190: Bug#736092: systemd-sysv: Systemd mount lvm root but do not mount /usr on lvm.
Oops, I missed the good bug, so add my reply here too. Hi, I can confirm that the new version of LVM in SID fix the bug (2.02.104-1 0), it is now working well thank you. Any idea about why it was not working in my local patched version ? Regards, Guillaume Seren -- "Non seulement Dieu joue aux dés mais il les jette parfois là où on ne peut les voir." Stephen Hawking -- FAQ : http://wiki.debian.org/fr/FrenchLists -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#736092: closed by Michael Stapelberg (fixed with lvm2 2.02.104-1)
Hi, I can confirm that the new version of LVM in SID fix the bug (2.02.104-1 0), it is now working well thank you. Any idea about why it was not working in my local patched version ? Regards, Guillaume Seren -- "Non seulement Dieu joue aux dés mais il les jette parfois là où on ne peut les voir." Stephen Hawking -- FAQ : http://wiki.debian.org/fr/FrenchLists -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735116: apt-listbugs: […]/debian.rb:24:in `require': no such file to load -- debian_version (LoadError)
On Thu, 30 Jan 2014 09:07:13 +0100 Lucas Nussbaum wrote: > On 29/01/14 at 22:02 +0100, Francesco Poli wrote: [...] > > Anyway, just to be clear: I fully understand your reasoning and I agree > > that, without more Ruby maintainers, it makes sense to reduce the > > number of supported major versions. > > Another important point IMHO is that in the past (2005-2011?), there was > a split inside the ruby community about the real "stable" version: the > upstream devs felt it was the 1.9 branch, while everybody was still > using 1.8. This is similar to the situation of Python a couple of years > ago. > > But now, this seems to be resolved, and everybody has moved to 2.X, with > more gradual improvements and less incompatibility between new upstream > releases. So we are much more in a perl5-ish situation, and it doesn't > make much sense anymore to support several upstream branches in our > stable releases. Thanks for your additional comment, Lucas. This aspect is definitely something to take into account. Bye. -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpxwvlHy4L0y.pgp Description: PGP signature
Bug#737168: apt-listbugs breaks, preventing package installation
Control: reassign -1 ruby1.8 1.8.7.358-7.1+deb7u1 Control: forcemerge 735116 -1 On Fri, 31 Jan 2014 10:21:05 +1300 Brendon Green wrote: [...] > Dear Maintainer, > > After installing apt-listbugs v 0.1.12 and restarting aptitude, new packages > failed to install [...] > -- System Information: > Debian Release: 7.3 > APT prefers stable > APT policy: (900, 'stable'), (650, 'testing'), (600, 'unstable'), (500, > 'testing-updates'), (500, 'stable-updates'), (500, 'experimental') [...] > ii ruby1.8 1.8.7.358-7.1+deb7u1 [...] Hello Brendon, thanks for your bug report, which is, however, about an already known and resolved issue. I am therefore reassigning and merging your report. I see that you are running a highly mixed system (stable/testing/unstable/experimental, with a preference for packages coming from stable). These mixed systems may work correctly, but require some care... Anyway, please read http://bugs.debian.org/735116#10 for the suggested procedure to fix the issue. N.B.: you may use aptitude in stead of apt-get, if you so prefer. Moreover, in order to upgrade to ruby1.8/1.8.7.358-10, please take it from testing, as in: # aptitude -t testing install ruby1.8 The same holds for ruby1.9.1 (which should also be installed from testing). I hope these steps may solve the issue for you too. Bye. -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgphSfiXdKHvG.pgp Description: PGP signature
Bug#721568: photofloat: move css below /etc and minify during install and on-demand
Quoting Antoine Beaupré (2014-01-30 22:56:53)
> On 2014-01-30 16:30:37, Jonas Smedegaard wrote:
>> Quoting Antoine Beaupré (2014-01-30 21:34:21)
>>> On 2014-01-30 15:17:31, Jonas Smedegaard wrote:
Convenience code copies don't require *runtime* compression.
>>>
>>> What? Isn't that why we are talking about triggers for javascript?
>>
>> Uhm, no. At least I am not.
>
> Yes, you are.
No, I do not talk about triggers for JavaScript due to convenience code
copies requiring runtime compression.
> In the original #721567 bug report:
>
>> For the bundling file I think best would be for the package to
>> generate that file using a dpkg trigger, so that it gets regenerated
>> whenever one of its dependent library packages are updated.
Thanks for pointing out where you (to follow suite on the shift of tone)
misunderstood.
I did indeed talk about compressing at runtime - for other reasons than
convenience code copies requiring runtime compression (they don't!).
> But anyways, that's beside the point here. The point is that the
> Jquery library (for example) we use is the one from the jquery
> package, so we need runtime compression to update it when the jquery
> package updates.
>
> We don't have this problem with CSS because the CSS is shipped with
> Photofloat and not part of another package.
>
> That's the point I am trying to make here.
Understood.
I don't agree that you need to compress at runtime. You can and it is
elegant if you do, but you do not need to.
>>> Sure, maybe it was respecting policy to compress at build time (the
>>> package is in Debian after all), but it is a potential security
>>> problem anyways.
>>
>> No, I believe you are mistaken.
>
> I believe not using triggers, in the case of jquery, for example, is a
> security issue because if we simply use a symlink and build at install
> time, when jquery is updated for a security vulnerability, we are
> still vulnerable.
I believe Security team checks for and issues binNMUs for reverse
build-dependencies as part of doing security updates.
>> Here is - I think - all sensible options:
>>
>> CSS can be compressed or compacted or simply collated during
>> build, and install that once below /usr, or once below /etc with
>> symlink below /usr, or once below /etc recompressed or
>> recompacted on-demand below /var with symlink below /usr.
>>
> b. install CSS compressed in /var
> c. install CSS sources in /etc
> d. provide a clear way for users to get from c to b, but don't
> do it automatically.
> e. symlink in /usr to /etc and /var for consistency and
> simplicity
>> Why compress,
>
> I said:
>
>> a. compress CSS during build (or compact, i don't care)
>
> So I don't care.
Thank you for (implied) clarifying that the remark applies to all items
in your list, not only to a. where it was written.
>> and what "consistency and simplicity" is in that + /var?
>
> The consistency is not related to /var, but to symlinks within the
> rest of the photofloat install in /usr.
Thanks again for clarifying that the list is not really so much a list.
> I think compacted files should be shipped in /var, because they can be
> potentially regenerated by the user from the sources in /etc. This is
> along the policy of allowing /usr to be readonly.
Understood.
(I don't agree, but that's not important)
>> I recommend to compact during build, and install that once below
>> /etc with a symlink below /usr.
>
> What about the source files? How do people rebuild if they modify
> in /etc?
You tell me - I suggest to not do such overkill.
>>>
>>> Why on earth would we ship undecipherable configuration files in
>>> /etc if we do not allow people to rebuild them from source?
>>
>> You tell me - I recommend compacting, not compressing as you propose.
>
> I guess it's still unclear to me what compacting does then.
Check the different output of scss --style {compact,compressed}
> We are clearly wasting time.
Bye then.
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
Bug#736694: workrave ppc64el patch to be reverted
Shoot, alright. I'll look into this. Thanks for letting me know. On Thu, Jan 30, 2014 at 3:38 PM, Francois Marier wrote: > Hi Logan, > > Thanks for sending through the patch you applied to the Ubuntu workrave > package. I applied it last week, but unfortunately, it looks like I will > have to revert it since the removal of the gettext stuff broke > translations: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737034 > > I'm guessing you'll probably also want to fix that in the Ubuntu package. > > Francois > > -- > Francois Marier identi.ca/fmarier > http://fmarier.org twitter.com/fmarier >
Bug#727708: multiple init systems - formal resolution proposal - Don't like software, don't use it. Absolutely.
On Thu, Jan 30, 2014 at 6:38 PM, Sergey B Kirpichev wrote: > On Thu, Jan 30, 2014 at 05:30:04PM +0100, Matthias Klumpp wrote: >> GNOME upstream won't really change > > Why? There are non-Linux GNOME users, for example. If the GNOME > developers don't care even about such popular distribution as Debian - > something is going wrong. And not with the Debian, for sure. This has already been answered. GNOME advised all distributors 2 years ago. Nothing much happened. Meanwhile, we went ahead and relied more on systemd without really depending on systemd. You could implement the interfaces of the various bits without depending really on systemd. If after (seems it is going to be) 2.5 years you come back and say "we'll, we decided on this" while meanwhile we continued communicating our decisions and plans (we plan at least 6 months ahead), then, I find phrasings like "don't care even about such popular distributions as Debian" offensive. This as we provided ample opportunity to know our plans, to discuss, etc. Anyway, it seems you don't know what systemd provides and from your various responses it is pretty clear you cannot be bothered to investigate. "It works fine for me" is such an easy answer. Coming late to this bugreport and asking questions that have already been asked and answered many times before, yet feeling entitled to be able to talk about what others did: good luck with that, but as already mentioned to other people: I can provide the various emails that we reached out and did our best. I can also show you that all the questions you're asking have been asked and answered before. Maybe investigate a little bit before forming your opinion! Lastly, we have added *loads* and *loads* of new dependencies over the many years GNOME has existed. Regards, Olav -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737086: duplicity: New upstream release 6.23
On Wed, 29 Jan 2014 19:10:59 -0800, Benjamin Mako Hill writes: >I was going to file that bug but since it has already been fixed, I will >file this wishlist bug instead. no problem, i'll package the new version in the next few days. regards az -- Alexander Zangerl + GPG Key 0xB963BD5F (or 0x42BD645D) + http://snafu.priv.at/ -- IE has a bad day. signature.asc Description: Digital Signature
Bug#737150: Upstream version 2.24.1 has support for F2FS
Upstream is now 4 versions ahead of Debian unstable at 2.24.1 Upstream has support for F2FS, and a number of other fixes/imporvements. Can Debian please move forward, at least in Experimental or Testing? Peter C -- Dr Peter Chubb peter.chubb AT nicta.com.au http://www.ssrg.nicta.com.au Software Systems Research Group/NICTA -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737171: ff_rate_estimate_qscale: Assertion `picture_numbernum_entries' failed
Package: libav-tools
Version: 6:0.8.9-1
Severity: normal
Dear Maintainer,
--- The mission
I am converting a lot of old PAL MPEG2 TS files to something else. The
files occasionally have invalid data packages, as is to be expected for
data being received via PB Sat. All these files get happily played by
mplayer. I know little about avlib (except that debian has choosen it
above ffmpeg and I know even less about ffmpeg).
I have seen more bugs and crashes in avconv than you have bug reports on
Debian. Unfortunately all seem to be upstream bugs. Probably you are not
interested in collecting bugs for upstream?
--- The bug of the day
Here a bug example (output of a batch job generated by a shell script):
COMMAND :> avconv -loglevel error -i /data/alpha/vol1/Filme/SciFi/Star
Wars EpisodeVI-Die Rückkehr der Jedi Ritter.mpg -pass 1 -an -passlogfile
/tmp/user/1000/9234 -vf crop=720:341:0:118,yadif -c:v mpeg4 -async 1000
-threads 2 -strict 1 -b:a 192k -b:v 3M -bt 18M -f mp4 -y /dev/null
[mpeg2video @ 0xd78440] ac-tex damaged at 7 18
[mpeg2video @ 0xd78440] Warning MVs not available
STATUS := 0
COMMAND :> avconv -loglevel error -i /data/alpha/vol1/Filme/SciFi/Star
Wars EpisodeVI-Die Rückkehr der Jedi Ritter.mpg -pass 2 -passlogfile
/tmp/user/1000/9234 -vf crop=720:341:0:118,yadif -c:a libmp3lame -c:v
mpeg4 -async 1000 -threads 2 -strict 1 -b:a 192k -b:v 3M -bt 18M -f mp4
-y Star Wars EpisodeVI-Die Rückkehr der Jedi Ritter.mp4
[mp2 @ 0x209f000] Header missing
Error while decoding stream #0:1
[mp2 @ 0x209f000] Header missing
Error while decoding stream #0:1
avconv: /build/libav-NImQwo/libav-0.8.9/libavcodec/ratecontrol.c:693:
ff_rate_estimate_qscale: Assertion `picture_numbernum_entries'
failed.
/usr/local/bin/centaurirecode: Zeile 298: 10173 Abgebrochen
"${opts[@]}"
STATUS := 134
--- Analysis
As can be seen it's a 2 pass conversion bug. Using -an and /dev/null in
pass 1 is recommended in the documentation.
The error happens at the very end of the conversion. Unfortunately no
moov atom gets written.
A 1 pass conversion works as expected.
There is an an old (2006) Bug report for this on ffmpeg, but it was closed
by the maintainer. But it's still these and hurts.
--- Newer Versions
The version of avconv that is in backports is unusable, avconv seems to
pass parameter values to the codecs that are not acepted, no idea how to
handle this via avconv. Installing from SID is not an option for me.
Anyhow, thanks to all Debian and upstream people for their work!
Jürgen
-- System Information:
Debian Release: 7.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libav-tools depends on:
ii dpkg 1.16.12
ii libavcodec-extra-53 6:0.8.9-1
ii libavdevice536:0.8.9-1
ii libavfilter2 6:0.8.9-1
ii libavformat536:0.8.9-1
ii libavutil51 6:0.8.9-1
ii libc62.13-38
ii libpostproc526:0.8.9-1
ii libsdl1.2debian 1.2.15-5
ii libswscale2 6:9.10-1~bpo70+1
libav-tools recommends no packages.
libav-tools 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#736904: apt-mirror: spelling & grammar cleanups
tags 736904 + pending thanks Am Dienstag, den 28.01.2014, 16:50 +1100 schrieb Vincent McIntyre: > I was looking into apt-mirror and noticed a few things that were > easy to fix. Please consider the attached patch (against current git). Thanks for the patch. I have applied it in the upstream git repository [1] in a slightly modified way. It will be part of the next upstream release. [1] https://github.com/apt-mirror/apt-mirror/commit/607f248 -- Benjamin Drung Debian & Ubuntu Developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737170: debian-installer: hd-media installer says it didn't find ISO image, modprobe error in the logs
On Thu, 2014-01-30 at 22:59 +0100, Flavio Stanchina wrote: > Package: debian-installer > Version: 20130613+deb7u1+b1 > Severity: important > > I'm trying to build a bootable USB stick with the "hd-media" image at: > http://ftp.it.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/hd-media/boot.img.gz > > plus the debian-7.3.0-amd64-i386-netinst.iso CD image. The installer > doesn't find the ISO image, here's an excerpt from the syslog: > > Jan 30 21:04:35 iso-scan: Found ISO ./debian-7.3.0-amd64-i386-netinst.iso on > /dev/sda1 > Jan 30 21:04:35 kernel: [5.367123] ISO 9660 Extensions: Microsoft Joliet > Level 3 > Jan 30 21:04:35 kernel: [5.368754] ISO 9660 Extensions: RRIP_1991A > Jan 30 21:04:35 iso-scan: Detected ISO with 'stable' (wheezy) distribution > Jan 30 21:04:35 iso-scan: Detected ISO with distribution 'stable' (wheezy) > Jan 30 21:04:35 iso-scan: Debian ISO ./debian-7.3.0-amd64-i386-netinst.iso > usable > Jan 30 21:04:35 main-menu[251]: (process:1281): modprobe: invalid option -- > 'l' > Jan 30 21:04:35 main-menu[251]: WARNING **: Configuring 'iso-scan' failed > with error code 1 > Jan 30 21:04:35 main-menu[251]: WARNING **: Menu item 'iso-scan' failed. > > I verified that the modprobe tool used in the squeeze installer did in fact > have a -l option (it listed all available modules), but now it doesn't. > Busybox's modprobe also has a -l option. This option was dropped when module-init-tools was replaced by kmod. Ben. -- Ben Hutchings It is a miracle that curiosity survives formal education. - Albert Einstein signature.asc Description: This is a digitally signed message part
Bug#737106: confclerk: Adding second choice favourites (feature request)
Control: forwarded -1 http://www.toastfreeware.priv.at/confclerk/ticket/54 Control: tag -1 + upstream confirmed On Thu, 30 Jan 2014 11:11:48 +0100, Elena Grandi wrote: > It would be nice to be able to have two classes of favorite talks: one > for talks that one plans to attend and one for backup choices > in case the first choice is not available (e.g. the room is full). > > Overlaps should be marked differently between categories (e.g. the > current yellow could be for overlaps inside the same category, a very > ligth $other_color could mark second choices that overlap with 1st > choices, while the reverse could remain unmarked, but if you have > better ideas is fine.) Thanks for your bug report! I think that's an interesting idea, and I also sometimes have problems with too many conflicting talks :) We'll think about if and how we could implement such a ranking feature. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Melissa Etheridge: You Can't Always Get What You Want signature.asc Description: Digital signature
Bug#568839: tasksel: please add readahead-fedora to the desktop task
Seeing that readahead-fedora is dead upstream [1] and can actually have negative effects with SSDs (which are becoming more and more common on laptop hardware), I would advise against installing readahead-fedora by default for desktop tasks. Michael [1] https://fedorahosted.org/readahead/ -- 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#737072: ITP: KeySigningPartyTools -- create a better formatted list in PDF format by reading a FOSDEM key list
raphael hertzog has a tutorial on these multiple source tarballs thing. I will look into merging these :) maintainership of signing-party package is actually becoming upstream. Maybe in a distant future I look into taking it over, but my time now is scarce now, sorry :/ On Thu, Jan 30, 2014 at 3:29 PM, Thijs Kinkhorst wrote: > On Thu, January 30, 2014 15:17, alberto fuentes wrote: >> On Thu, Jan 30, 2014 at 1:11 PM, Alexander Wirt >> wrote: >>> On Wed, 29 Jan 2014, Alberto Fuentes wrote: >>> Package: wnpp Severity: wishlist Owner: Alberto Fuentes * Package name: KeySigningPartyTools Version : n/a Upstream Author : Vadim Trochinsky * URL : https://github.com/vatral/KeySigningPartyTools * License : AGPL v3 Programming Lang: Perl Description : create a better formatted list in PDF format by reading a FOSDEM key list Key signing is really in need of a program that eases interchange of keys. KeySigningPartyTools generates a pdf with qr codes and visual hints for the fingerprints that allows faster processing and avoid manual errors. It process the qr codes afterwards with the help of a webcam as well. It also automatically checks that the keys scanned match the keys downloaded before you sign them. >>> There already is a signing-party package, would you mind to integrate >>> KeySigningPartyTools into it? >>> >>> Thanks >>> >>> Alex >>> >> >> I can sure look into it if its ok to Thijs... > > I don't see any objection, but in fact. I prefer to actually relinquish my > maintainership of signing-party. > >> Any suggestion on how to proceed since the package will have two sources? > > It's possible to work with multiple source tarballs... > > > Thijs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735051: Pending fixes for bugs in the libhtml-formhandler-perl package
tag 735051 + pending thanks Some bugs in the libhtml-formhandler-perl package are closed in revision eec8408450d14ecee8d85f0ad2c8a67e6cfcc5c6 in branch 'master' by Salvatore Bonaccorso The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libhtml-formhandler-perl.git;a=commitdiff;h=eec8408 Commit message: Add 735051-fix-FTBFS.patch Fix test case which was dependent on a 2008+5 yts time span. Closes: #735051 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#731261: transition: Qt5 switching qreal == double for all platforms
On Fri, Dec 20, 2013 at 00:57:06 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > As explained before, we are requesting a slot for this transition. > Go ahead. Ping this bug if/when you need binNMUs. Cheers, Julien signature.asc Description: Digital signature
Bug#676075: aptitude: sort by size change
Control: tags -1 + pending Hi, Change commited. If you want a change in the name (it's a bit cumbersome, but consistent with "installsize" and "change") or description in the documentation, please speak before it's released in an official version. http://anonscm.debian.org/gitweb/?p=aptitude/aptitude.git;a=commitdiff;h=828363d069b70cf317fc59c9f23e9c93a49c6b08 Cheers. -- Manuel A. Fernandez Montecelo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737170: debian-installer: hd-media installer says it didn't find ISO image, modprobe error in the logs
Package: debian-installer Version: 20130613+deb7u1+b1 Severity: important I'm trying to build a bootable USB stick with the "hd-media" image at: http://ftp.it.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/hd-media/boot.img.gz plus the debian-7.3.0-amd64-i386-netinst.iso CD image. The installer doesn't find the ISO image, here's an excerpt from the syslog: Jan 30 21:04:35 iso-scan: Found ISO ./debian-7.3.0-amd64-i386-netinst.iso on /dev/sda1 Jan 30 21:04:35 kernel: [5.367123] ISO 9660 Extensions: Microsoft Joliet Level 3 Jan 30 21:04:35 kernel: [5.368754] ISO 9660 Extensions: RRIP_1991A Jan 30 21:04:35 iso-scan: Detected ISO with 'stable' (wheezy) distribution Jan 30 21:04:35 iso-scan: Detected ISO with distribution 'stable' (wheezy) Jan 30 21:04:35 iso-scan: Debian ISO ./debian-7.3.0-amd64-i386-netinst.iso usable Jan 30 21:04:35 main-menu[251]: (process:1281): modprobe: invalid option -- 'l' Jan 30 21:04:35 main-menu[251]: WARNING **: Configuring 'iso-scan' failed with error code 1 Jan 30 21:04:35 main-menu[251]: WARNING **: Menu item 'iso-scan' failed. I verified that the modprobe tool used in the squeeze installer did in fact have a -l option (it listed all available modules), but now it doesn't. Busybox's modprobe also has a -l option. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#721568: photofloat: move css below /etc and minify during install and on-demand
On 2014-01-30 16:30:37, Jonas Smedegaard wrote: > Quoting Antoine Beaupré (2014-01-30 21:34:21) >> On 2014-01-30 15:17:31, Jonas Smedegaard wrote: >>> Convenience code copies don't require *runtime* compression. >> >> What? Isn't that why we are talking about triggers for javascript? > > Uhm, no. At least I am not. Yes, you are. > Perhaps if you quote the text giving you that impression we can > locate the cause of misunderstanding. In the original #721567 bug report: > For the bundling file I think best would be for the package to > generate that file using a dpkg trigger, so that it gets regenerated > whenever one of its dependent library packages are updated. But anyways, that's beside the point here. The point is that the Jquery library (for example) we use is the one from the jquery package, so we need runtime compression to update it when the jquery package updates. We don't have this problem with CSS because the CSS is shipped with Photofloat and not part of another package. That's the point I am trying to make here. >> Sure, maybe it was respecting policy to compress at build time (the >> package is in Debian after all), but it is a potential security >> problem anyways. > > No, I believe you are mistaken. I believe not using triggers, in the case of jquery, for example, is a security issue because if we simply use a symlink and build at install time, when jquery is updated for a security vulnerability, we are still vulnerable. >> It seems to me that section 4.13 goes a little further than DFSG then, >> as it specifically refers to maintainability of the code from a >> security perspective. > > What complicates security work is lack of proper source. Yes, that as well. However, Photofloat was shipping some JS library non-minified, which is still an issue if we skip those and compile from other packages. > Here is - I think - all sensible options: > > CSS can be compressed or compacted or simply collated during build, > and install that once below /usr, or once below /etc with symlink > below /usr, or once below /etc recompressed or recompacted > on-demand below /var with symlink below /usr. > b. install CSS compressed in /var c. install CSS sources in /etc d. provide a clear way for users to get from c to b, but don't do it automatically. e. symlink in /usr to /etc and /var for consistency and simplicity >>> >>> Why? Seems exactly what I argue below is overkill and you agree >>> with? >> >> Sorry, why what? >> >> I thought you were arguing that recompiling on the fly at runtime is >> overkill. Recompiling on the fly at runtime is not what I am >> suggesting here. > > Above you propose /usr + /etc + /var, and compressing. > > Below I recommend /usr + /etc, and compacting. > > Why compress, I said: > a. compress CSS during build (or compact, i don't care) So I don't care. > and what "consistency and simplicity" is in that + /var? The consistency is not related to /var, but to symlinks within the rest of the photofloat install in /usr. I think compacted files should be shipped in /var, because they can be potentially regenerated by the user from the sources in /etc. This is along the policy of allowing /usr to be readonly. > I recommend to compact during build, and install that once below > /etc with a symlink below /usr. What about the source files? How do people rebuild if they modify in /etc? >>> >>> You tell me - I suggest to not do such overkill. >> >> Why on earth would we ship undecipherable configuration files in /etc >> if we do not allow people to rebuild them from source? > > You tell me - I recommend compacting, not compressing as you propose. I guess it's still unclear to me what compacting does then. Are we still talking about the same 3 miserable CSS files? >> What I propose above (in d) is that we provide a way (either in >> README.Debian or with an update-foo script) to recompile from sources >> in /etc. That should be simple enough. > > If you say so. I am not against such additional complication, just ask > why, because you also write that you agree that exactly that is > overdoing it. You misunderstand me. I think overdoing it is using triggers or recompiling at "postinst configure" time. >> I believe it goes beyond our duty as package maintainers to extend >> Photofloat to include a CSS test suite. If we could convince upstream >> of that, I'm okay with the idea, otherwise I don't think it's >> necessary. > > How do you define "necessary" in this context? Necessary is something that would ensure photofloat works as designed upstream. Checking for validity of CSS files (or Python code, for that matter) is not currently accomplished upstream, so I think it's not necessary for the Debian package to accomplish those tasks. We're not going to write unit tests for the Python code either are we? > Arguably Photofloat itself is unnecessary. That is inco
Bug#720426: pu: package openssl/1.0.1e-2
Control: tags -1 + confirmed On Thu, 2014-01-30 at 22:27 +0100, Kurt Roeckx wrote: > On Thu, Jan 30, 2014 at 08:09:44PM +, Adam D. Barratt wrote: > > On Mon, 2013-09-23 at 09:05 +0200, Kurt Roeckx wrote: > > > On Mon, Sep 23, 2013 at 05:35:23AM +0200, Cyril Brulebois wrote: > > > > Kurt Roeckx (2013-08-21): [...] > > > > > * Enable assembler for the arm targets, and remove armeb. > > > > > Patch by Riku Voipio (Closes: #676533) > > > > > * enable ec_nistp_64_gcc_128 on *-amd64 (Closes: #698447) [...] > > The changes have obviously had significant testing in unstable and > > testing by now; have any further related changes been required? Have the > > changes had any testing in a stable environment? > > There have no changes related to it. I'm also pretty sure that > people actually do use that in production. Okay. Please go ahead, bearing in mind that p-u freeze for 7.4 is this coming weekend. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#716685: Is poppler Qt5 frontend ready ?
Hello, I've noticed that you uploaded the new version of poppler that supports Qt5, but that the libpoppler-qt5-dev package is not available yet. Is there a specific problem that prevents you from doing so ? I'm trying to switch to Qt5 an application of mine that uses poppler too, but of course the binary segfaults at startup, being linked to qt4 and and qt5 libraries. I'm ready to help should you need some ;-)... Cheers, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733056: gedit code assistance: Interested in packaging
I interested in packaging this module and have started work on it with help from members at #debian-bcn2014. Thanks!
Bug#737169: im-config: Keyboard typing dead keys directly
Package: im-config Version: 0.21 Severity: normal Tags: l10n The keyboard on this computer prints all dead keys directly (typing ´ and e types two different characters) -- System Information: Debian Release: 7.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages im-config depends on: ii dialog1.1-20120215-2 ii gettext-base 0.18.1.1-9 ii zenity3.4.0-2 Versions of packages im-config recommends: ii dialog 1.1-20120215-2 ii x11-common 1:7.7+3~deb7u1 im-config 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#717613: [Pkg-utopia-maintainers] Bug#717613: systemd-udevd failes to execute /lib/udev/socket:@/org/freedesktop/hal/udev_event
Hi David, thanks for your reply! Am 30.01.2014 21:39, schrieb David Kalnischkies: > On Thu, Jan 30, 2014 at 05:51:44PM +0100, Michael Biebl wrote: >> But in this case not kicking out hal forcefully leads to those >> scary boot messages (and already quite a few duplicate bug reports). >> Once this udev version enters stable, we might get even more. >> So I'm also inclined to add the Breaks. > > Usually I would suggest a transitional package in addition, but in this > case I am going a bit further: > The error message suggests to me (who has absolutely no idea what he is > talking about through) that hal configures udev to send messages to hal. > Why not just drop this configuration if it doesn't work anyway… ? You are basically correct: This udev directive in /lib/udev/rules.d/90-hal.rules set's up a socket which is feeding the kernel events that udev receives into hal and hal then further processes those events. This mechanism has been removed from udev. So while hal was buggy and unmaintained before, this is the last straw which makes hal completely useless on Linux. So in a way, udev does indeed break hal. The issue is, that there won't be a fixed version of hal. We could drop that rules file from the hal package or even make hal an empty dummy package (on Linux), so it would just be some dead weight on the users system, but somehow I would prefer if on upgrades hal is simply removed. Dropping that configuration won't magically make hal work again. @lct: If you run "apt-get autoremove", is hal uninstalled? @David: If not, is there a way to find out, why autoremove is not uninstalling hal? 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#737165: bookletimposer crashes when Gtk couldn't be initialized
Hi, thank you for this bug report. I don't think it is specific to Debian, so I have forwarded it upstream. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#721568: photofloat: move css below /etc and minify during install and on-demand
Quoting Antoine Beaupré (2014-01-30 21:34:21) > On 2014-01-30 15:17:31, Jonas Smedegaard wrote: >> Convenience code copies don't require *runtime* compression. > > What? Isn't that why we are talking about triggers for javascript? Uhm, no. At least I am not. Perhaps if you quote the text giving you that impression we can locate the cause of misunderstanding. > Sure, maybe it was respecting policy to compress at build time (the > package is in Debian after all), but it is a potential security > problem anyways. No, I believe you are mistaken. > It seems to me that section 4.13 goes a little further than DFSG then, > as it specifically refers to maintainability of the code from a > security perspective. What complicates security work is lack of proper source. Here is - I think - all sensible options: CSS can be compressed or compacted or simply collated during build, and install that once below /usr, or once below /etc with symlink below /usr, or once below /etc recompressed or recompacted on-demand below /var with symlink below /usr. >>> b. install CSS compressed in /var >>> c. install CSS sources in /etc >>> d. provide a clear way for users to get from c to b, but don't do >>> it automatically. >>> e. symlink in /usr to /etc and /var for consistency and simplicity >> >> Why? Seems exactly what I argue below is overkill and you agree >> with? > > Sorry, why what? > > I thought you were arguing that recompiling on the fly at runtime is > overkill. Recompiling on the fly at runtime is not what I am > suggesting here. Above you propose /usr + /etc + /var, and compressing. Below I recommend /usr + /etc, and compacting. Why compress, and what "consistency and simplicity" is in that + /var? I recommend to compact during build, and install that once below /etc with a symlink below /usr. >>> >>> What about the source files? How do people rebuild if they modify in >>> /etc? >> >> You tell me - I suggest to not do such overkill. > > Why on earth would we ship undecipherable configuration files in /etc > if we do not allow people to rebuild them from source? You tell me - I recommend compacting, not compressing as you propose. > What I propose above (in d) is that we provide a way (either in > README.Debian or with an update-foo script) to recompile from sources > in /etc. That should be simple enough. If you say so. I am not against such additional complication, just ask why, because you also write that you agree that exactly that is overdoing it. > I believe it goes beyond our duty as package maintainers to extend > Photofloat to include a CSS test suite. If we could convince upstream > of that, I'm okay with the idea, otherwise I don't think it's > necessary. How do you define "necessary" in this context? Arguably Photofloat itself is unnecessary. I assumed - based on our prior discussion - that you deemed it "necessary" to optimize CSS at all. Going from there I then argue that optimizing with a tool that *also* does a good job at sanity checking same code is preferrable. Please tell me if we are wasting time here - if you consider it unnecessary to optimize the CSS. On-demand recomputing is IMO overdoing it (local admin can run Sass on the file below /etc if they feel the need for that). >>> >>> Agreed. >> >> Really? > > I am not sure I understand what you disagree with here, or what you > think I disagree with. Please see above - and tell me if you need me to elaborate further. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#720426: pu: package openssl/1.0.1e-2
On Thu, Jan 30, 2014 at 08:09:44PM +, Adam D. Barratt wrote: > On Mon, 2013-09-23 at 09:05 +0200, Kurt Roeckx wrote: > > On Mon, Sep 23, 2013 at 05:35:23AM +0200, Cyril Brulebois wrote: > > > Kurt Roeckx (2013-08-21): > > > > * Add Polish translation (Closes: #658162) > > > > * Add Turkish translation (Closes: #660971) > > > > * Enable assembler for the arm targets, and remove armeb. > > > > Patch by Riku Voipio (Closes: #676533) > > > > * enable ec_nistp_64_gcc_128 on *-amd64 (Closes: #698447) > > > > > > I'm sorry but I don't think wishlist bug reports qualify for stable > > > uploads. As usual, we could use more consistency across documentation, > > > but either devref[1] or p-u[2] pages give an overview of what can be > > > considered. > > > > I actually consider the arm assembler and nistp curves to be > > important, even if the bugs might only be filed at severity > > level wishlist. The nistp curves are even security related > > since they are then implemented with constant time removing > > a side channel attack. > > I have to agree with Cyril here that the bug really shouldn't have such > a low severity if it has genuine security impact. If it makes you happy, I can mark the security related bugs serious. I'm also of the opinion that the severity wishlist doesn't say anything about the importance. > The changes have obviously had significant testing in unstable and > testing by now; have any further related changes been required? Have the > changes had any testing in a stable environment? There have no changes related to it. I'm also pretty sure that people actually do use that in production. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#641131: Interested in packaging - ITP: gst-debug-viewer
Hi! I am interested in packaging gst-debug-viewer. Will someone be able to sponsor and mentor me? Thanks! -Sindhu
Bug#737167: xfonts-wqy: prompting due to modified conffiles which were not modified by the user
Package: xfonts-wqy Version: 0.9.9-8 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... 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. This was observed on an upgrade from wheezy to jessie to sid. >From the attached log (scroll to the bottom...): Setting up xfonts-wqy (0.9.9-8) ... Configuration file '/etc/X11/fonts/misc/xfonts-wqy.alias' ==> 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. *** xfonts-wqy.alias (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package xfonts-wqy (--configure): EOF on stdin at conffile prompt Processing triggers for libc-bin (2.17-97) ... Errors were encountered while processing: xfonts-wqy E: Sub-process /usr/bin/dpkg returned an error code (1) cheers, Andreas xfonts-wqy_0.9.9-8.log.gz Description: GNU Zip compressed data
Bug#736797: pu: package debian-handbook/7.20140126~deb7u1
Hi, On Thu, 30 Jan 2014, Adam D. Barratt wrote: > On Sun, 2014-01-26 at 22:00 +0100, Raphael Hertzog wrote: > > I would like to update the debian-handbook in Wheezy so that it actually > > documents Wheezy and not Squeeze. We finished the update in late december. > > Please go ahead; thanks. Thanks, uploaded debian-handbook_7.20140126~deb7u1_amd64.changes. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737166: nmu: luasocket_3.0~rc1-3~bpo70+1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu luasocket_3.0~rc1-3~bpo70+1 . amd64 . wheezy-backports . -m "Rebuild in wheezy." 0m27.1s ERROR: Command failed (status=100): ['chroot', '/tmp/piupartss/tmpQrd2SD', 'apt-get', '-y', '-t', 'wheezy-backports', 'install', 'lua-socket'] [...] The following packages have unmet dependencies: lua-socket : Depends: libc6 (>= 2.15) but 2.13-38 is to be installed E: Unable to correct problems, you have held broken packages. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737164: sendmail: attempts to bind to wrong interface for CNAME-to-A-only MX when ipv6 available
Package: sendmail Version: 8.14.4-4 Severity: important Tags: patch Hello, Sendmail 8.14.4-4 fails with an error message under rare conditions: http://serverfault.com/questions/482035/sendmail-issue-with-ipv6 If a domain has an MX record that is a CNAME that has both A and records, sendmail can create an IPv4 socket and then attempt to bind it to an IPv6 address (if a bind address is set in Client Options), which fails. The Ubuntu folks have a patch: Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/sendmail/+bug/1223633 Patch: https://launchpadlibrarian.net/149925062/conf.c-ipv6.patch Any chance this could be brought over into Wheezy's Sendmail? Regards, David. -- Package-specific info: Ouput of /usr/share/bug/sendmail/script: ls -alR /etc/mail: /etc/mail: total 1668 drwxr-sr-x 9 smmta smmsp 4096 Jan 30 11:09 . drwxr-xr-x 206 root root 16384 Jan 30 11:28 .. -rwxr-xr-- 1 root smmsp 10843 Oct 29 15:35 Makefile -rw-r--r-- 1 root smmsp 4497 Oct 29 15:35 access -rw-r--r-- 1 root smmsp 75525 Oct 29 15:35 access.1 -rw-r--r-- 1 root smmsp 4261 Dec 17 2012 access.10 -rw-r--r-- 1 root smmsp 75451 Dec 19 2012 access.2 -rw-r--r-- 1 root smmsp 92665 Dec 19 2012 access.3 -rw-r--r-- 1 root smmsp 75451 Dec 19 2012 access.4 -rw-r--r-- 1 root smmsp 92665 Dec 19 2012 access.5 -rw-r--r-- 1 root smmsp 4497 Dec 19 2012 access.6 -rw-r--r-- 1 root smmsp 92665 Dec 17 2012 access.7 -rw-r--r-- 1 root smmsp 92665 Dec 17 2012 access.8 -rw-r--r-- 1 root smmsp 92665 Dec 17 2012 access.9 -rw-r- 1 smmta smmsp 12288 Oct 29 15:35 access.db -rw-r--r-- 1 root root281 Sep 21 2010 address.resolve lrwxrwxrwx 1 root smmsp10 May 18 2012 aliases -> ../aliases -rw-r- 1 smmta smmsp 12288 May 6 2013 aliases.db drwxr-sr-x 2 root smmsp 4096 Jan 30 11:30 canit -rw-r--r-- 1 root smmsp 3225 Oct 29 15:35 databases -rw-r- 1 smmta smmsp59 May 19 2012 default-auth-info -rw-r--r-- 1 root root 5657 Sep 21 2010 helpfile -rw-r--r-- 1 root smmsp38 May 18 2012 local-host-names drwxr-sr-x 2 smmta smmsp 4096 May 18 2012 m4 -rw-r--r-- 1 root smmsp 238 Oct 29 15:35 mailertable -rw-r--r-- 1 root smmsp 50404 Oct 29 15:35 mailertable.1 -rw-r--r-- 1 root smmsp 2 Dec 17 2012 mailertable.10 -rw-r--r-- 1 root smmsp 50355 Dec 19 2012 mailertable.2 -rw-r--r-- 1 root smmsp 62538 Dec 19 2012 mailertable.3 -rw-r--r-- 1 root smmsp 50355 Dec 19 2012 mailertable.4 -rw-r--r-- 1 root smmsp 62538 Dec 19 2012 mailertable.5 -rw-r--r-- 1 root smmsp 238 Dec 19 2012 mailertable.6 -rw-r--r-- 1 root smmsp 62538 Dec 17 2012 mailertable.7 -rw-r--r-- 1 root smmsp 62538 Dec 17 2012 mailertable.8 -rw-r--r-- 1 root smmsp 62538 Dec 17 2012 mailertable.9 -rw-r- 1 smmta smmsp 12288 Oct 29 15:35 mailertable.db -rw-r--r-- 1 root smmsp 12933 May 22 2012 mimedefang-filter -rw-r--r-- 1 root smmsp 12933 Jan 30 11:09 mimedefang-filter.example drwxr-xr-x 2 root root 4096 May 6 2013 peers drwxr-xr-x 2 smmta smmsp 4096 May 19 2012 sasl -rw-r--r-- 1 root smmsp 63034 Oct 30 16:38 sendmail.cf -rw-r--r-- 1 root root 63034 Jul 4 2013 sendmail.cf.old -rw-r--r-- 1 root root 12236 Jul 4 2013 sendmail.conf -rw-r--r-- 1 root smmsp 3249 Oct 29 15:35 sendmail.mc -rw-r--r-- 1 root smmsp 3050 May 22 2012 sendmail.mc.orig -rw-r--r-- 1 root root149 Sep 21 2010 service.switch -rw-r--r-- 1 root root180 Sep 21 2010 service.switch-nodns drwxr-sr-x 2 smmta smmsp 4096 May 22 2012 smrsh drwxr-sr-x 2 root smmsp 4096 Aug 2 16:16 spamassassin -rw-r--r-- 1 root smmsp 44815 Jul 4 2013 submit.cf -rw-r--r-- 1 root root 44867 Jul 4 2013 submit.cf.old -rw-r--r-- 1 root smmsp 2998 Jul 4 2013 submit.mc drwxr-xr-x 2 smmta smmsp 4096 May 18 2012 tls -rw-r--r-- 1 root smmsp 0 May 18 2012 trusted-users /etc/mail/canit: total 36 drwxr-sr-x 2 root smmsp 4096 Jan 30 11:30 . drwxr-sr-x 9 smmta smmsp 4096 Jan 30 11:09 .. -rw--- 1 root smmsp 81 Jan 30 11:31 canit-api-client.conf -rw-r--r-- 1 root smmsp 195 Jan 30 11:09 canit-cluster-member-id -rw-r--r-- 1 root smmsp 259 Jan 30 11:14 canit.conf -rw-r--r-- 1 root smmsp 259 Jan 30 11:09 sa-canit.cf -rw-r--r-- 1 root smmsp 159 Jan 30 11:08 virus-scanners.pl -rw-r--r-- 1 root smmsp 4624 Jan 30 11:09 virus-scanners.pl.DIST /etc/mail/m4: total 8 drwxr-sr-x 2 smmta smmsp 4096 May 18 2012 . drwxr-sr-x 9 smmta smmsp 4096 Jan 30 11:09 .. -rw-r- 1 root smmsp0 May 18 2012 dialup.m4 -rw-r- 1 root smmsp0 May 18 2012 provider.m4 /etc/mail/peers: total 12 drwxr-xr-x 2 root root 4096 May 6 2013 . drwxr-sr-x 9 smmta smmsp 4096 Jan 30 11:09 .. -rw-r--r-- 1 root root 328 Sep 21 2010 provider /etc/mail/sasl: total 16 drwxr-xr-x 2 smmta smmsp 4096 May 19 2012 . drwxr-sr-x 9 smmta smmsp 4096 Jan 30 11:09 .. -rw-r- 1 smmta smmsp 885 May 19 2012 Sendmail.conf.2 -rwxr--r-- 1 root root 3670
Bug#735967: /usr/bin/apt-get: Internal error
Hi David I'm getting the same issue as reported by Tom, running Jessie since an update / upgrade / dist-upgrade cycle this morning. Have tried the dist-upgrade using backed up dpkg.status files as you suggested but looks like none of them are old enough. Would sending you a compressed /var/lib/dpkg/status file help ? Regards Stewart -- Stewart Douglas sdoug...@snowgold.com http://www.snowgold.com
Bug#737165: bookletimposer crashes when Gtk couldn't be initialized
Package: bookletimposer
Version: 0.2-1
Severity: important
I installed bookletimposer on a server to automatically generate booklets from
PDFs.
I used the following command:
bookletimposer linear.pdf --no-gui --output=booklet.pdf
Which crashed with the following trace:
Traceback (most recent call last):
File "/usr/bin/bookletimposer", line 45, in
import bookletimposer.gui as gui
File "/usr/lib/python2.7/dist-packages/bookletimposer/gui.py", line 34,
in
from gi.repository import Gtk
File "/usr/lib/python2.7/dist-packages/gi/importer.py", line 76, in
load_module
dynamic_module._load()
File "/usr/lib/python2.7/dist-packages/gi/module.py", line 224, in _load
overrides_modules = __import__('gi.overrides',
fromlist=[self._namespace])
File "/usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py", line 1533,
in
raise RuntimeError("Gtk couldn't be initialized")
RuntimeError: Gtk couldn't be initialized
As a workaround I commented out line 45:
#import bookletimposer.gui as gui
That was enough to have bookletimposer behave as expected: generate the booklet.
-- System Information:
Debian Release: 7.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (200, 'stable')
Architecture: i386 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bookletimposer depends on:
ii gir1.2-gtk-3.0 3.4.2-7
ii python 2.7.3-4+deb7u1
ii python-gobject 3.2.2-2
ii python-pypdf1.13-1
ii python2.6 2.6.8-1.1
ii python2.7 2.7.3-6
bookletimposer recommends no packages.
bookletimposer 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#737163: linux-image-3.13-trunk-amd64: Please enable CONFIG_I2C_DESIGNWARE_{CORE, PLATFORM}
Package: linux-image-3.13-trunk-amd64 Severity: wishlist Dear Maintainer, please enable the above kconfig settings, it's used to drive the touchscreen/trackpad on the vaio duo 13". Cheers, -- Guido -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13.0-rc7+ (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#730868: freeciv: New upstream version 2.4.1 available
On 30 January 2014 15:19, Markus Koschany wrote: > Does a similar option such as --enable-sys-lua exist for m4? > If possible I would like to drop Debian's patch for this issue. No, and such an feature couldn't easily be part of the configure, as those .m4 -files are like part of the configure script itself - they would be already been used by the time such an option, maybe itself living in .m4 -file, would be parsed. - ML -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737108: python-gamin: mixed use of tabs and spaces in the gamin.py file causing syntax erros
On 30 January 2014 18:12, Jakub Wilk wrote: > If you remove this option from the script's shebang, it should start > working. Right you are. Learn something new every day. =] I've (attempted) to lower the severity
Bug#732358: pu: package lxc/0.8.0~rc1-8+deb7u2
On Thu, 30 Jan 2014, Adam D. Barratt wrote: > > > For details: http://bugs.debian.org/680469 > > I'd be okay with this change. Great. > > Someone requested me to squeeze another fix in that stable update: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720122 > > http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;filename=devpts-mode.patch;att=2;bug=720122 > > > > It's a one-liner that fix issues with containers running with glibc >= > > 2.18. Would this be acceptable as well ? > > It appears this issue isn't fixed in unstable yet; is that correct? Looks like so, the fix seems to be only in 0.9.0-18 which had been uploaded to experimental. I really wish lxc had a better maintainer... That said this precise fix has made its way upstream: https://github.com/lxc/lxc/commit/67e5a20ad1b5579a571f43f7dd8a1556a8bea7a1 So it should be safe to apply IMO. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737162: O: halevt -- generic handler for HAL events
Package: wnpp Severity: normal See #737147. by Halevt, good times :P
