Bug#703753: release-notes: much text in ch4 related to udev/kernel changes in lenny-to-squeeze
Hoi Joost, On 06-04-13 03:58, Joost van Baal-Ilić wrote: Thanks a lot. I've applied your patch since it fixes at least some of the issues. Do you have time to investigate some of the open issues you've found? It's is not yet too late now I understand you (mainly?) mean Upgrading the kernel and udev section. I see you didn't merge my note in. I am very uncomfortable advising on such an important topic, but as worded in my note in the patch on that subject, I believe releasename needs to be replaced with squeeze and oldreleasename with lenny at least. As a conclusion I really think this text should be removed. Hmm, I think I will ask on e.g. d-kernel. Paul signature.asc Description: OpenPGP digital signature
Bug#680484: closed by Andreas Tille ti...@debian.org (Bug#680484: fixed in scotch 5.1.12b.dfsg-2)
Hi,
On Fri, Apr 05, 2013 at 03:14:15PM +0100, Jonathan Wiltshire wrote:
Thanks - it would help to ping this bug when it uploaded too please.
Hereby pinging the bug, package uploaded, debdiff attached to this mail.
I'm sure you realised but s/uploads/updates/ in your quoted mail
above (or just testing).
Just used 'testing' as advised.
Hope everything is fine now - feel free to ping me if I can provide more
help on this issue.
Kind regards
Andreas.
--
http://fam-tille.de
diff -Nru scotch-5.1.12b.dfsg/debian/changelog
scotch-5.1.12b.dfsg/debian/changelog
--- scotch-5.1.12b.dfsg/debian/changelog2012-04-15 14:34:15.0
+0200
+++ scotch-5.1.12b.dfsg/debian/changelog2013-04-05 22:30:34.0
+0200
@@ -1,3 +1,17 @@
+scotch (5.1.12b.dfsg-1.2) testing; urgency=low
+
+ * Team upload
+ * Incorporate changes done by Christophe Trophime in 5.1.12b.dfsg-2:
+Rename gmap to scotch_gmpap to avoid clash with gmap package
+Closes: #680484
+ * debian/patches/format-security.patch:
+Incorporate patch from 5.1.12b.dfsg-2 to fix a potential security
+issue which will be necessary when building with hardening flags
+(-Wformat-security) anyway. Debian release team has confirmed this
+patch in IRC
+
+ -- Debian Science Maintainers
debian-science-maintain...@lists.alioth.debian.org Fri, 05 Apr 2013 15:08:53
+0200
+
scotch (5.1.12b.dfsg-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru scotch-5.1.12b.dfsg/debian/patches/format-security.patch
scotch-5.1.12b.dfsg/debian/patches/format-security.patch
--- scotch-5.1.12b.dfsg/debian/patches/format-security.patch1970-01-01
01:00:00.0 +0100
+++ scotch-5.1.12b.dfsg/debian/patches/format-security.patch2013-04-06
07:57:13.0 +0200
@@ -0,0 +1,26 @@
+Author: Andreas Tille ti...@debian.org
+Date: Tue, 17 Jul 2012 10:12:24 +0200
+Description: Fix format security issue which cases an error when using
-Werror=format-security
+
+--- scotch.orig/src/libscotch/parser.c
scotch/src/libscotch/parser.c
+@@ -590,15 +590,15 @@
+ case STRATTESTMUL : /* Multiplication operator
*/
+ case STRATTESTMOD : /* Modulus operator
*/
+ i = (test-data.test[0]-typetest test-typetest) ? 1 : 0;
+- fprintf (stream, strattestsavepa[i][0]);
++ fputs (strattestsavepa[i][0], stream);
+ o = stratTestSave (test-data.test[0], stream);
+- fprintf (stream, strattestsavepa[i][1]);
++ fputs (strattestsavepa[i][1], stream);
+ if (o == 0) {
+ fprintf (stream, %c, strattestsaveop[test-typetest]);
+ i = (test-data.test[1]-typetest test-typetest) ? 1 : 0;
+-fprintf (stream, strattestsavepa[i][0]);
++fputs (strattestsavepa[i][0], stream);
+ stratTestSave (test-data.test[1], stream);
+-fprintf (stream, strattestsavepa[i][1]);
++fputs (strattestsavepa[i][1], stream);
+ }
+ break;
+ case STRATTESTVAL : /* Constant value */
diff -Nru scotch-5.1.12b.dfsg/debian/patches/series
scotch-5.1.12b.dfsg/debian/patches/series
--- scotch-5.1.12b.dfsg/debian/patches/series 2011-04-01 17:08:59.0
+0200
+++ scotch-5.1.12b.dfsg/debian/patches/series 2013-04-04 08:06:53.0
+0200
@@ -1,2 +1,3 @@
build-fixes.patch
metis-header.patch
+format-security.patch
diff -Nru scotch-5.1.12b.dfsg/debian/rules scotch-5.1.12b.dfsg/debian/rules
--- scotch-5.1.12b.dfsg/debian/rules2012-04-15 14:31:17.0 +0200
+++ scotch-5.1.12b.dfsg/debian/rules2013-04-05 15:21:25.0 +0200
@@ -67,6 +67,7 @@
(cd src $(MAKE) scotch ptscotch prefix=$(CURDIR)/$$v); \
(cd src $(MAKE) install prefix=$(CURDIR)/$$v); \
mv $$v/bin/gbase $$v/bin/scotch_gbase; \
+ mv $$v/bin/gmap $$v/bin/scotch_gmap; \
rm -rf lib; \
rm -f src/Makefile.inc; \
done
@@ -102,6 +103,8 @@
# Fix lintian warnings for undefined macro in man pages
perl -pi -e 's|\.\|\.\\\|' int/share/man/man1/*.1
mv int/share/man/man1/gbase.1 int/share/man/man1/scotch_gbase.1
+# Rename gmap to avoid clash with package gmap
+ mv int/share/man/man1/gmap.1 int/share/man/man1/scotch_gmap.1
# Fix lintian missing man pages
cp debian/scotch_esmumps.1 int/share/man/man1
cp debian/ptscotch_esmumps.1 int/share/man/man1
diff -Nru scotch-5.1.12b.dfsg/debian/scotch.install
scotch-5.1.12b.dfsg/debian/scotch.install
--- scotch-5.1.12b.dfsg/debian/scotch.install 2011-03-27 19:55:30.0
+0200
+++ scotch-5.1.12b.dfsg/debian/scotch.install 2013-04-04 08:06:53.0
+0200
@@ -8,7 +8,7 @@
int/bin/atst /usr/bin
int/bin/scotch_gbase /usr/bin
int/bin/gcv /usr/bin
-int/bin/gmap /usr/bin
+int/bin/scotch_gmap /usr/bin
int/bin/gmk_hy /usr/bin
int/bin/gmk_m2 /usr/bin
int/bin/gmk_m3 /usr/bin
@@ -36,7 +36,7 @@
int32/bin/atst-int32 /usr/bin
Bug#703753: please advise on kernel upgrade text in release-notes
Hi kernel team, Last week I stumbled upon the current text in the release-notes about kernel/udev upgrade. If we don't update it, it says (among other things) the text below [1]. I believe this text is obsolete and was ONLY meant for the lenny to squeeze update. Do you agree that this part should be removed? Or do you think it should be rewritten (in the latter case, can you do a proposal)? If some of the current text stays, I say at least the names wheezy and squeeze are wrong. Kind regards, Paul [1] http://www.debian.org/releases/wheezy/amd64/release-notes/ch-upgrading.en.html#upgrading-udev 4.4.5. Upgrading the kernel and udev The udev version in wheezy requires a kernel of version 2.6.26 or newer with the CONFIG_SYSFS_DEPRECATED option disabled and the CONFIG_INOTIFY_USER and CONFIG_SIGNALFD options enabled. Because the standard Debian kernels in squeeze (version 2.6.26) have CONFIG_SYSFS_DEPRECATED enabled, and the udev version in squeeze will not provide all the functionality expected by the latest kernels, special care must be taken when upgrading to avoid putting your system in an unbootable state. Booting the 2.6.26 kernel from squeeze with the udev from wheezy may result in a failure to correctly assign names to network devices, and will also fail to apply certain additional permissions to block devices (such as access by the disk group). The software itself will appear to be working, but some rules (for example, network-based rules) will not be loaded properly. It is therefore strongly recommended that you upgrade the kernel on its own at this point, to ensure a compatible kernel is available before upgrading udev. signature.asc Description: OpenPGP digital signature
Bug#704808: live-images and live-image-all: error when trying to install together
Package: live-image-all,live-images Version: live-image-all/4.0~a11-1 Version: live-images/4.0~a12-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2013-04-06 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! debootstrap live-build live-image-gnome-desktop live-image-kde-desktop live-image-lxde-desktop live-image-rescue live-image-standard live-image-xfce-desktop live-image-all live-images Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package debootstrap. (Reading database ... 10775 files and directories currently installed.) Unpacking debootstrap (from .../debootstrap_1.0.48_all.deb) ... Selecting previously unselected package live-build. Unpacking live-build (from .../live-build_3.0.1-1_all.deb) ... Selecting previously unselected package live-image-gnome-desktop. Unpacking live-image-gnome-desktop (from .../live-image-gnome-desktop_4.0~a12-1_all.deb) ... Selecting previously unselected package live-image-kde-desktop. Unpacking live-image-kde-desktop (from .../live-image-kde-desktop_4.0~a12-1_all.deb) ... Selecting previously unselected package live-image-lxde-desktop. Unpacking live-image-lxde-desktop (from .../live-image-lxde-desktop_4.0~a12-1_all.deb) ... Selecting previously unselected package live-image-rescue. Unpacking live-image-rescue (from .../live-image-rescue_4.0~a12-1_all.deb) ... Selecting previously unselected package live-image-standard. Unpacking live-image-standard (from .../live-image-standard_4.0~a12-1_all.deb) ... Selecting previously unselected package live-image-xfce-desktop. Unpacking live-image-xfce-desktop (from .../live-image-xfce-desktop_4.0~a12-1_all.deb) ... Selecting previously unselected package live-image-all. Unpacking live-image-all (from .../live-image-all_4.0~a11-1_all.deb) ... Selecting previously unselected package live-images. Unpacking live-images (from .../live-images_4.0~a12-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/live-images_4.0~a12-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/live-images/examples/live-images-wheezy', which is also in package live-image-all 4.0~a11-1 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/live-images_4.0~a12-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/share/doc/live-images/examples/live-images-wheezy /usr/share/man/de/man7/live-images.7.gz /usr/share/man/man7/live-images.7.gz This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704809: dvb-apps and scalasca: error when trying to install together
Package: scalasca,dvb-apps Version: scalasca/1.4.2-1 Version: dvb-apps/1.1.1+rev1483-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2013-04-06 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libquadmath0 libgfortran3 libgomp1 libpng12-0 libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libzvbi-common libzvbi0 libnuma1 libtorque2 dvb-apps libibverbs1 libopenmpi1.3 scalasca Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libquadmath0:amd64. (Reading database ... 10775 files and directories currently installed.) Unpacking libquadmath0:amd64 (from .../libquadmath0_4.7.2-5_amd64.deb) ... Selecting previously unselected package libgfortran3:amd64. Unpacking libgfortran3:amd64 (from .../libgfortran3_4.7.2-5_amd64.deb) ... Selecting previously unselected package libgomp1:amd64. Unpacking libgomp1:amd64 (from .../libgomp1_4.7.2-5_amd64.deb) ... Selecting previously unselected package libpng12-0:amd64. Unpacking libpng12-0:amd64 (from .../libpng12-0_1.2.49-3_amd64.deb) ... Selecting previously unselected package libxau6:amd64. Unpacking libxau6:amd64 (from .../libxau6_1%3a1.0.7-1_amd64.deb) ... Selecting previously unselected package libxdmcp6:amd64. Unpacking libxdmcp6:amd64 (from .../libxdmcp6_1%3a1.1.1-1_amd64.deb) ... Selecting previously unselected package libxcb1:amd64. Unpacking libxcb1:amd64 (from .../libxcb1_1.8.1-2_amd64.deb) ... Selecting previously unselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.5.0-1_all.deb) ... Selecting previously unselected package libx11-6:amd64. Unpacking libx11-6:amd64 (from .../libx11-6_2%3a1.5.0-1_amd64.deb) ... Selecting previously unselected package libzvbi-common. Unpacking libzvbi-common (from .../libzvbi-common_0.2.33-7_all.deb) ... Selecting previously unselected package libzvbi0:amd64. Unpacking libzvbi0:amd64 (from .../libzvbi0_0.2.33-7_amd64.deb) ... Selecting previously unselected package libnuma1. Unpacking libnuma1 (from .../libnuma1_2.0.8-1_amd64.deb) ... Selecting previously unselected package libtorque2. Unpacking libtorque2 (from .../libtorque2_2.4.16+dfsg-1_amd64.deb) ... Selecting previously unselected package dvb-apps. Unpacking dvb-apps (from .../dvb-apps_1.1.1+rev1483-2_amd64.deb) ... Selecting previously unselected package libibverbs1. Unpacking libibverbs1 (from .../libibverbs1_1.1.6-1_amd64.deb) ... Selecting previously unselected package libopenmpi1.3. Unpacking libopenmpi1.3 (from .../libopenmpi1.3_1.4.5-1_amd64.deb) ... Selecting previously unselected package scalasca. Unpacking scalasca (from .../scalasca_1.4.2-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/scalasca_1.4.2-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/scan', which is also in package dvb-apps 1.1.1+rev1483-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/scalasca_1.4.2-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/scan This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704625: Patch for this bug
Hi,
I have done the work of backporting the upstream patch which Salvatore
Bonaccorso pointed at. The patch is attached to this email.
Please note that I have *not* tested this patch, I just applied manually
(because otherwise it would fail) what I could find upstream, and
checked that the package was still building (which it does).
So the current maintainer of the mod_security package *must* (before
upload or requesting for sponsorship):
1/ Check that this patch really addresses CVE-2013-1915 as expected
2/ Check that there is no regression and that mod_security continues to
work as expected
Note that this work should be done asap, considering how close we are
from releasing Wheezy. If nothing is done by the current maintainer,
then I hope to find the time to do the above 1/ and 2/, then upload to
the delayed queue (though, do not take it as fact, I might be busy doing
something else).
Please do take care of it, mod_security is a nice software, and it would
be a shame not to release Wheezy with it.
Cheers,
Thomas Goirand (zigo)
Description: CVE-2013-1915: Vulnerable to XXE attacks
This upstream patch has been backported to the Wheezy version.
Author: Alberto Gonzalez Iniesta a...@inittab.org
Bug-Debian: http://bugs.debian.org/704625
Origin: upstream, https://github.com/SpiderLabs/ModSecurity/commit/d4d80b38aa85eccb26e3c61b04d16e8ca5de76fe
Reviewed-By: Thomas Goirand z...@debian.org
Last-Update: -MM-DD
--- modsecurity-apache-2.6.6.orig/apache2/msc_xml.c
+++ modsecurity-apache-2.6.6/apache2/msc_xml.c
@@ -14,17 +14,27 @@
#include msc_xml.h
+static xmlParserInputBufferPtr
+xml_unload_external_entity(const char *URI, xmlCharEncoding enc){
+return NULL;
+}
/**
* Initialise XML parser.
*/
int xml_init(modsec_rec *msr, char **error_msg) {
+xmlParserInputBufferCreateFilenameFunc entity;
+
if (error_msg == NULL) return -1;
*error_msg = NULL;
msr-xml = apr_pcalloc(msr-mp, sizeof(xml_data));
if (msr-xml == NULL) return -1;
+if(msr-txcfg-xml_external_entity == 0){
+entity = xmlParserInputBufferCreateFilenameDefault(xml_unload_external_entity);
+}
+
return 1;
}
--- modsecurity-apache-2.6.6.orig/apache2/apache2_config.c
+++ modsecurity-apache-2.6.6/apache2/apache2_config.c
@@ -128,6 +128,9 @@ void *create_directory_config(apr_pool_t
/* Collection timeout */
dcfg-col_timeout = NOT_SET;
+/* xml external entity */
+dcfg-xml_external_entity = NOT_SET;
+
return dcfg;
}
@@ -518,6 +521,10 @@ void *merge_directory_configs(apr_pool_t
merged-col_timeout = (child-col_timeout == NOT_SET
? parent-col_timeout : child-col_timeout);
+/* xml external entity */
+merged-xml_external_entity = (child-xml_external_entity == NOT_SET
+? parent-xml_external_entity : child-xml_external_entity);
+
return merged;
}
@@ -615,6 +622,9 @@ void init_directory_config(directory_con
if (dcfg-disable_backend_compression == NOT_SET) dcfg-disable_backend_compression = 0;
if (dcfg-col_timeout == NOT_SET) dcfg-col_timeout = 3600;
+
+/* xml external entity */
+if (dcfg-xml_external_entity == NOT_SET) dcfg-xml_external_entity = 0;
}
/**
@@ -1961,6 +1971,32 @@ static const char *cmd_web_app_id(cmd_pa
return NULL;
}
+/**
+* \brief Add SecXmlExternalEntity configuration option
+*
+* \param cmd Pointer to configuration data
+* \param _dcfg Pointer to directory configuration
+* \param p1 Pointer to configuration option
+*
+* \retval NULL On failure
+* \retval apr_psprintf On Success
+*/
+static const char *cmd_xml_external_entity(cmd_parms *cmd, void *_dcfg, const char *p1)
+{
+directory_config *dcfg = (directory_config *)_dcfg;
+if (dcfg == NULL) return NULL;
+
+if (strcasecmp(p1, on) == 0) {
+dcfg-xml_external_entity = 1;
+}
+else if (strcasecmp(p1, off) == 0){
+dcfg-xml_external_entity = 0;
+}
+else return apr_psprintf(cmd-pool, ModSecurity: Invalid value for SecXmlExternalEntity: %s, p1);
+
+return NULL;
+}
+
/* PCRE Limits */
static const char *cmd_pcre_match_limit(cmd_parms *cmd,
@@ -2295,6 +2331,14 @@ const command_rec module_directives[] =
component signature to add to ModSecurity signature.
),
+AP_INIT_TAKE1 (
+SecXmlExternalEntity,
+cmd_xml_external_entity,
+NULL,
+CMD_SCOPE_ANY,
+On or Off
+),
+
AP_INIT_FLAG (
SecContentInjection,
cmd_content_injection,
--- modsecurity-apache-2.6.6.orig/apache2/modsecurity.h
+++ modsecurity-apache-2.6.6/apache2/modsecurity.h
@@ -522,6 +522,9 @@ struct directory_config {
/* Collection timeout */
int col_timeout;
+
+/* xml */
+int xml_external_entity;
};
struct error_message {
Bug#703753: release-notes: much text in ch4 related to udev/kernel changes in lenny-to-squeeze
Hoi Paul, On Sat, Apr 06, 2013 at 08:10:39AM +0200, Paul Gevers wrote: On 06-04-13 03:58, Joost van Baal-Ilić wrote: Thanks a lot. I've applied your patch since it fixes at least some of the issues. Do you have time to investigate some of the open issues you've found? It's is not yet too late now I understand you (mainly?) mean Upgrading the kernel and udev section. I see you didn't merge my note in. I am very uncomfortable advising on such an important topic, but as worded in my note in the patch on that subject, I believe releasename needs to be replaced with squeeze and oldreleasename with lenny at least. As a conclusion I really think this text should be removed. Hmm, I think I will ask on e.g. d-kernel. Yes, please do. I'd be happy to apply an improved patch. Bye, Joost PS: irc: joostvb @ oftc , freenode -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704625: Tested a bit further the mod_security patch I backported
Hi, I installed mod_security with the patch I backported, made sure the module was loaded by Apache, and tested to query http://localhost;, then I could see the It works! default Debian Apache page. So, I'd say: so far so good, Apache doesn't crash. Salvatore, could you tell how you find out about this CVE, and are you sure that the commit you linked is fixing the problem (which I do not understand fully...)? If you confirm that you are sure it fixes the CVE, then I believe I could NMU the fixed package in the delayed queue. Thoughts? Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704810: ITP: spice-html5 -- Spice Web client which runs entirely within a modern browser
Package: wnpp Severity: wishlist Owner: Thomas Goirand z...@debian.org * Package name: spice-html5 Version : 0~ Upstream Author : Aric Stewart a...@codeweavers.com * URL : http://www.spice-space.org/page/Html5 * License : GPL, LGPL Programming Lang: Javascript Description : Spice Web client which runs entirely within a modern browser Spice Web client which runs entirely within a modern browser. It is limited in function, a bit slow, and lacks support for many features of Spice (audio, video, agents just to name a few). The Simple Protocol for Independent Computing Environments (SPICE) is a remote display system built for virtual environments which allows you to view a computing 'desktop' environment not only on the machine where it is running, but from anywhere on the Internet and from a wide variety of machine architectures. Note that this is a dependency for nova-spicehtml5proxy for the latest Openstack 2013.1 release (code name Grizzly). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704705: [Pkg-ime-devel] Bug#704705: ibus: cannot use with both Mozilla i386 apps and emacs
Hi, Thanks for investigating this. I did similar. My conclusion: * ibus-gtk:i386 issue is possibly user issue with downgrade. * ibus-gtk3:i386 issue is possibly user issue with downgrade. * ibus-qt4:i386 issue is the issue of libibus-qt1 not being multiarch. So this is not bug with ibus. Here is what I did tracing your comment. Without your proof of co-installed ibus-gtk:i386 and ibus-gtk:amd64 etc., I was poking wrong things. Thanks. On Fri, Apr 05, 2013 at 04:58:22PM +0200, Toni Mueller wrote: Hi Osamu, On Fri, Apr 05, 2013 at 11:07:19PM +0900, Osamu Aoki wrote: Multiarch is well defined and implemented for libraries but for these executables used by other software, the best practice was not clear to me and may had some wrong handling. (I did think a lot on this but its been more than 6 months. My memory is vague. So I need to check everything again.) I now have several of the library packages installed in parallel, so it seems to work, after all. But in the process of converting my machine, I found that often, installing one version would sort of kill the other, and from my perspective, it's more of a hit-and-miss experience, whether two instances of a library can be installed, or not, and I apparently got tripped up over that. :/ ibus being Multi-Arch: foreign it can serve both i386 and amd64 applications by either one of ibus:i386 and ibus:amd64 but ibus:i386 and ibus:amd64 are not co-installable. But as I re-think ibus:i386 and ibus:amd64 should be co-installable. I should have said the previous following text as the following instead. ibus-gtk:i386 run-time support programs and co-installable because it is Multi-Arch: same. ibus-gtk:amd64 run-time support programs and co-installable because it is Multi-Arch: same. So there should be some reason why these were not co-installable here. To wit, I now have, excluding tables-* etc: Oh great but what are the tables-*. I guess you mean ibus-table-*. but .. wait ... [2011-12-26] Accepted 1.3.0.20100528-3 in unstable (low) (Osamu Aoki) ibus-table-others (1.3.0.20100528-3) unstable; urgency=low * Move to utils section. Closes: #646673 * Convert to dh syntax and update package description. * Remove non-ASCII keys. Closes: #653216 -- Osamu Aoki os...@debian.org Sun, 25 Dec 2011 20:12:41 +0900 No multiarch updates were done by me but these are Architecture: all packages. So this problem can not be caused by ibus-tables-*. What is going on ii ibus-gtk:amd641.5.1.is.1.4.2-1 amd64Intelligent Input Bus - GTK+2 support ii ibus-gtk:i386 1.5.1.is.1.4.2-1 i386 Intelligent Input Bus - GTK+2 support For you, they were co-installable eventually for you? I could not do this here too initially. When I tried first, it caused major package removal situation. I tried to install all dependency packages of ibus-gtk and faced problem with some dependency packages. If that was caused by packages from unstable, I downgraded to testing ones. Then I was still stack with libgdk-pixbuf2.0-0 and libgtk2.0-0. Tracing this goes to libjasper. Here libjasper1 (!= 1.900.1-13) but I have 1.900.1-14 OK downgrade libjasper1. Similarly downgrade libcolord1 for ibus-gtk3. Hmmm... aptitude can select downgrade right but its display does not reflect it. This is confusing but usable... Now I have ibus-gtk/ibus-gtk3 have both i386 and amd64 co-installed. Anyway, you need to be careful for this kind of downgrade resolution problem if you are running mixed system. libibus-qt1 is not multiarch. So we can not have ibus-gt* for both arch I guess. So ibus-qt package needs to be updated for multiarch to support ibus-qt4 in multiarch setting. For example, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646973 libpcre3-dbg: Multi-Arch: same but not coinstallable with itself Not exactly the cause of our bug but this is another indication of how imperfect multiarch support is. With this, using the 32 bit Mozilla apps seems to work (I can enter Chinese text into a form field). Now only the Emacs question is really open, but emacs is amd64, so the whole multiarch question most likely does not even apply (proceed with fingers crossed - what will happen tomorrow?). Hmmm... so this is expected problem of current packaging which we have no easy solution. This should be true for current testing version too. I retract this comment. Well, I basically have that version that was in experimental for a short time, and that what is now in unstable, although the underlying system is intended to become Wheezy. If things were more predictable, instead of installing one package, then the other to see that the first package was lost, is imho unsatisfactory and misleading, but likely outside the scope of ibus. Multiarch is major major change. So expect some rough ride if you
Bug#704811: pu: net-snmp/5.4.3~dfsg-2.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu
Hi,
net-snmp 5.4.3~dfsg-2 in Squeeze has a bug (CVE-2012-2141)
and fixed in testing/unstable version. It's patch is tiny one,
so I would like to upload it to spu.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672492
https://security-tracker.debian.org/tracker/CVE-2012-2141
--
Regards,
Hideki Yamane henr...@debian.org
diff -Nru net-snmp-5.4.3~dfsg/debian/changelog net-snmp-5.4.3~dfsg/debian/changelog
--- net-snmp-5.4.3~dfsg/debian/changelog 2011-01-05 21:12:04.0 +0900
+++ net-snmp-5.4.3~dfsg/debian/changelog 2013-04-06 15:07:05.0 +0900
@@ -1,3 +1,11 @@
+net-snmp (5.4.3~dfsg-2.1) stable-proposed-updates; urgency=low
+
+ * Non-maintainer upload.
+ * debian/patches
+- apply CVE-2012-2141.patch
+
+ -- Hideki Yamane henr...@x121e.mithril-linux.org Sat, 06 Apr 2013 15:06:20 +0900
+
net-snmp (5.4.3~dfsg-2) unstable; urgency=high
* Add libperl-dev to libsnmp-dev dependencies (Closes: #608794)
diff -Nru net-snmp-5.4.3~dfsg/debian/patches/CVE-2012-2141.patch net-snmp-5.4.3~dfsg/debian/patches/CVE-2012-2141.patch
--- net-snmp-5.4.3~dfsg/debian/patches/CVE-2012-2141.patch 1970-01-01 09:00:00.0 +0900
+++ net-snmp-5.4.3~dfsg/debian/patches/CVE-2012-2141.patch 2013-04-06 15:06:15.0 +0900
@@ -0,0 +1,31 @@
+Description: fix denial of service via SNMP GET with non-existent
+ extension table entry
+Bug: http://sourceforge.net/tracker/index.php?func=detailaid=3526549group_id=12694atid=112694
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672492
+Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=815813
+Origin: upstream, http://net-snmp.git.sourceforge.net/git/gitweb.cgi?p=net-snmp/net-snmp;a=commit;h=4c5633f1603e4bd03ed05c37d782ec8911759c47
+
+Index: net-snmp-5.4.3~dfsg/agent/mibgroup/agent/extend.c
+===
+--- net-snmp-5.4.3~dfsg.orig/agent/mibgroup/agent/extend.c 2013-04-06 15:06:10.934136272 +0900
net-snmp-5.4.3~dfsg/agent/mibgroup/agent/extend.c 2013-04-06 15:06:10.922136274 +0900
+@@ -1124,7 +1124,7 @@
+ * ...and check the line requested is valid
+ */
+ line_idx = *table_info-indexes-next_variable-val.integer;
+-if (eptr-numlines line_idx)
++if (line_idx 1 || line_idx eptr-numlines)
+ return NULL;
+ }
+ return eptr;
+@@ -1297,6 +1297,10 @@
+ * Determine which line we've been asked for
+ */
+ line_idx = *table_info-indexes-next_variable-val.integer;
++if (line_idx 1 || line_idx extension-numlines) {
++netsnmp_set_request_error(reqinfo, request, SNMP_NOSUCHINSTANCE);
++continue;
++}
+ cp = extension-lines[line_idx-1];
+
+ /*
diff -Nru net-snmp-5.4.3~dfsg/debian/patches/series net-snmp-5.4.3~dfsg/debian/patches/series
--- net-snmp-5.4.3~dfsg/debian/patches/series 2011-01-05 21:12:04.0 +0900
+++ net-snmp-5.4.3~dfsg/debian/patches/series 2013-04-06 15:04:00.0 +0900
@@ -12,3 +12,4 @@
60_libsensors_api.patch
61_vacm_missing_dependency_check.patch
62_add_lib_cflags.patch
+CVE-2012-2141.patch
Bug#704812: ibus-qt:src Update package to be multiarch ready
Source: ibus-qt Version: 1.3.1-2.1 Severity: normal User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch I found this issue while investigating http://bugs.debian.org/704705 . Please update package to make it multiarch ready etc. Osamu -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699744: nagios3-cgi: prompting due to modified conffiles which were not modified by the user: /etc/nagios3/stylesheets/outages.css
Hi, I agree with Andreas Beckmann it would be useful if a remark could be added to the release notes. I can apply a patch soon. Below snippets from previous discussion summarize the relevant parts I believe. Anybody willing to draft a patch? Thanks, Bye, Joost Guillem Jover schreef: On Wed, 2013-02-06 at 00:50:29 +0100, Andreas Beckmann wrote: Bug #689836: dpkg: md5sums incorrectly recorded for conffile takeover http://bugs.debian.org/689836 So it's broken in squeeze (dpkg database is corrupted, i.e. contains the wrong md5sums (well, it contains the correct md5sums, too, but at the wrong place)). Whether this happens depends on the configuration order. If nagios-doc is configured before nagios3-cgi it will record the new md5sum for updated conffiles for nagios3-doc instead of nagios-cgi ... even if it no longer owns these files. I have no idea how many packages are possibly affected by this or how this can be fixed ... therefore Cc:ing Guillem. Wait, we can try this: # apt-get install --reinstall nagios3-cgi [...] Great, that FIXED the DB. Right, it should just be either a matter of time, once every problematic package has been upgraded after getting a fixed dpkg, or people actively reinstalling broken packages. In any case, for wheezy I guess it would be nice to strongly recommend on the release notes to upgrade dpkg first. Andreas Beckmann schreef: On 2013-03-02 07:35, Alexander Wirt wrote: On Fri, 01 Mar 2013, Russ Allbery wrote: Based on the bug discussion, I believe this bug against nagios3-cgi should be closed. The problem is with the dpkg database, and it doesn't sound like there's anything the package needs to (or should do) to deal with that issue; it's fixed by either dealing with the prompt during upgrade or reinstalling the package. agreed, so I'll close this bug now. Shouldn't this be mentioned in the release-notes? apt-get install --reinstall *before* the upgrade is an easy workaround - if we make people aware of it. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel
can somebody please fix this bug? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638478: Another request to package glade-3.8
Dear Glade maintainer, Thanks for your work in packaging Glade. I am trying to use Glade with gtk2hs (Haskell GTK+ library), which is GTK2 only. For this I need Glade 3.8. For now, it looks like I have to download all the dependencies, and build my own package. This is a real distraction from my core work; I'm not sure I can justify the time. So, please would you reconsider your previous decision not to package Glade 3.8 ? cheers, Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704801: libva-intel-vaapi-driver: Intel video i915_drv_video.so fails to load
tag 704801 help stop On Sat, Apr 6, 2013 at 5:14 AM, Gerard Kam gerard...@verizon.net wrote: Package: libva-intel-vaapi-driver Version: 1.0.20-1 Severity: important Using Debian wheezy on an old Dell Diemension 3000, and cannot get libva working. Originally had version 0.32, and installed experimental packages with same results: $ vainfo libva info: VA-API version 0.33.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/i386-linux-gnu/dri/i915_drv_video.so libva error: dlopen of /usr/lib/i386-linux-gnu/dri/i915_drv_video.so failed: /usr/lib/i386-linux-gnu/dri/i915_drv_video.so: undefined symbol: _glapi_tls_Context libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ uname -a Linux d3000 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686 GNU/Linux $ This awfully smells like bug #491520, but that's fixed ages ago. The undefined symbol is in libglapi.so.0.0.0, which is in package libglapi-mesa. Version 8.0.5-4 is already the newest version of libglapi-mesa. Indeed. I'm tagging this bug as 'help', and seek assistance from the mesa maintainers. Is this something that can be fixed by adding appropriate Dependencies and Break relationship fields to the packages? -- System Information: Debian Release: 7.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libva-intel-vaapi-driver depends on: ii i965-va-driver 1.0.17-1 libva-intel-vaapi-driver recommends no packages. libva-intel-vaapi-driver suggests no packages. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers -- regards, Reinhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704813: iftop: bar graph average can be chosen with 'B' but no mention in man page about config option
Package: iftop Version: 1.0~pre2-3 Severity: minor Dear Maintainer, * What led up to the situation? I want to be able to completely customise iftop with .iftoprc. * What exactly did you do (or not do) that was effective (or ineffective)? Checked the man page for all available .iftoprc options. * What was the outcome of this action? Did not find an option for bar graph average. Thanks, Jayen -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (600, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages iftop depends on: ii libc62.13-38 ii libncurses5 5.9-10 ii libpcap0.8 1.3.0-1 ii libtinfo55.9-10 iftop recommends no packages. iftop 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#704657: debian/rules: Inconsistent required targets
user debian-pol...@packages.debian.org tag 704657 pending usertags 704657 informative thanks Le Fri, Apr 05, 2013 at 12:54:30AM +0100, Roger Leigh a écrit : The change was implemented in dpkg 1.16.2 just over a year ago. However, the intention is that the probing/autodetection is only a transitional measure, and this will be removed once the transition is complete. Once wheezy is released, lintian can make missing build-arch and build-indep targets an error rather than a warning, and then we can aim to fix up the remaining packages for jessie. I'll be doing some whole-archive rebuilds once wheezy is out to assess the scale of what percentage of the archive still needs attention. Once we're done with the transition, dpkg can then drop the autodetection logic by default. Thanks for the information. Let's correct the footnote in section 7.7 after dpkg-buildpackage is updated. I have updated 4.9 by adding build-arch and build-indep to the list in the third paragraph as discussed. It will take effect with the release of the Policy version 3.9.5. Have a nice week-end. -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692995: reportbug: unblock requests: set affects src:$PACKAGE and Cc: $PACKAGE@packages.d.o
Hi Samuel, On Sat, Apr 6, 2013 at 1:47 AM, Samuel Bronson naes...@gmail.com wrote: I've written a patch implementing this, though: Thanks for the patch! Can you please contact the Release Team asking if they find this behavioral change fine or they prefer something else? I'd rather keep the release.d.o bugs handling as they want it, given the bugs should help them processing requests better/quicker/whatever-er :) Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704814: lxc-debconfig creates preseeded mount entries in current dir instead of container rootfs
Package: lxc
Version: 0.9.0~rc1-4
Severity: normal
Tags: patch
Dear Maintainer,
I'm creating containers with a preseed file using the shipped
lxc-debian (lxc-debconfig) template, like that:
# lxc-create -n postgresql -t debian -- --preseed-file=/root/lxc.preseed
The relevant stanza in the preseed file is:
lxc-debconfig lxc-debconfig/mount0/entry string /dev dev none ro,bind 0 0
(but could be any other entry, that's just an example).
The entry in the config file is create fine but at the end of the
lxc-create run there's a new empty dev directory in my current
working directory.
The obvious intention is to create the needed mount points in the
rootfs of the container before it is first started.
I've pinpointed it to the lxc-debconfig template and created a
patch. Although the patch might be inappropriate if absolute
paths to the mountpoints are to be allowed. In that case it would
probably be better to cd into the rootfs before the mkdir
commands instead.
Regards,
Niels Boehm
--- a/usr/share/lxc/templates/lxc-debconfig 2013-03-10 22:17:41.0
+0100
+++ b/usr/share/lxc/templates/lxc-debconfig 2013-04-06 10:02:58.018394354
+0200
@@ -824,9 +824,9 @@
if [ -f ${_SOURCE} ]
then
- mkdir -p $(dirname ${_TARGET})
+ mkdir -p ${_ROOTFS}/$(dirname ${_TARGET})
else
- mkdir -p ${_TARGET}
+ mkdir -p ${_ROOTFS}/${_TARGET}
fi
fi
done
-- System Information:
Debian Release: 7.0
APT prefers testing-updates
APT policy: (940, 'testing-updates'), (930, 'testing-proposed-updates'),
(930, 'stable-updates'), (930, 'testing'), (830, 'proposed-updates'), (830,
'stable'), (90, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
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
Versions of packages lxc depends on:
ii debconf [debconf-2.0] 1.5.49
ii libapparmor1 2.7.103-4
ii libc6 2.13-38
ii libcap21:2.22-1.2
ii multiarch-support 2.13-38
Versions of packages lxc recommends:
ii debootstrap 1.0.48
ii libcap2-bin 1:2.22-1.2
Versions of packages lxc suggests:
ii debian-keyring 2012.11.15
ii gpgv1.4.12-7
pn live-debconfig-doc none
ii rsync 3.0.9-4
-- Configuration Files:
/etc/lxc/default.conf changed [not included]
-- debconf information:
* lxc/directory: /var/lib/lxc
lxc/title:
* lxc/auto: true
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704248: (no subject)
Packaging started at http://anonscm.debian.org/viewvc/pkg-gnome/packages/experimental/gnome-getting-started-docs/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704768: debian-installer: no neo2 keymap
Am 05.04.2013 20:56, schrieb Christian PERRIER: Quoting Simon Reinhardt (simon.reinha...@stud.uni-regensburg.de): Package: debian-installer Version: wheezy RC-1-Release Severity: wishlist Hi, I have a keyboard with the german Neo2 layout. Currently it appears that there is no option to select it in the debian- installer. I can only enable it after the installation with dpkg --reconfigure keyboard- configuration. Would be great to have it in the installer! Just like we had for the many request for some non standard keymaps which we had in the past, I'll make the same answer : adding more keymapsto the installer has a cost, in memory and complexity. We deliberately chose several years ago to not make things too complicated for users : for instance, for each language we usually offer one option, usually the most widespread one in the countries that use this language. The overall rationale is that users of less common keymaps will always have the opportunity to reconfigure console-setup on the installed system. Thanks for your fast answer. One problem is, that the neo2 layout is completely different to the qwertz. And it is not so uncommon. At least not among Debian users :-). I know that there are quite a lot of people on the debian-user-german list who use it. Regards, Simon signature.asc Description: OpenPGP digital signature
Bug#704306: libconfig-model-dpkg-perl: does not catch invalid license text
Le Friday 05 April 2013 19:44:56, Felix Natter a écrit : What about catching single-line licenses? Or is License: GPL see /usr/share/common-licenses/GPL valid? Yes, even if this practice is not recommended. cme edit dpkg-copyright proposes default text for well known licenses like GPL-1. Are there single-line license texts? Normally no, because writing a single line license which is legally meaningful is not an easy task. Unless you don't limit the number of character on a line... I didn't realize that, thanks for the clarification. You're welcome. Dominique -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698527: elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries
control: reopen 698527 ! control: found 698527 7.0.svn.6034+dfsg-1 control: tags 698527 = experimental Package in experimental will include ElmerGUI as earlier. And this package will not pass into unstable until license issue is not solved in one way or another. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704815: Would it be possible to reenable CONFIG_ACPID
Package: busybox-static Version: 1:1.20.0-7 Severity: wishlist I know that acpid was disabled on purpose, but would it be possible to reenable it? It is useful on VMs running with busybox only, for example. Also it was enabled in squeeze, so this is a bit of a regression. Thanks a lot, Guido -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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#704625: Tested a bit further the mod_security patch I backported
On Sat, Apr 06, 2013 at 02:43:39PM +0800, Thomas Goirand wrote: Hi, I installed mod_security with the patch I backported, made sure the module was loaded by Apache, and tested to query http://localhost;, then I could see the It works! default Debian Apache page. So, I'd say: so far so good, Apache doesn't crash. Salvatore, could you tell how you find out about this CVE, and are you sure that the commit you linked is fixing the problem (which I do not understand fully...)? If you confirm that you are sure it fixes the CVE, then I believe I could NMU the fixed package in the delayed queue. Hi Thomas and Salvatore, Thanks for the heads-up. Strangely I didn't get the first mail (the bug report), but luckily got Thomas' mails. I'll check this ASAP and make an upload accordingly. Cheers, Alberto -- Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico agi@(inittab.org|debian.org)| en GNU/Linux y software libre Encrypted mail preferred| http://inittab.com Key fingerprint = 9782 04E7 2B75 405C F5E9 0C81 C514 AF8E 4BA4 01C3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704815: Would it be possible to reenable CONFIG_ACPID
06.04.2013 12:56, Guido Trotter wrote:
Package: busybox-static
Version: 1:1.20.0-7
Severity: wishlist
I know that acpid was disabled on purpose, but would it be possible to
reenable it? It is useful on VMs running with busybox only, for example.
For many years, i've the following replacement for acpid:
cut
#! /bin/sh
[ -d /sys/module/button ] || { modprobe button; sleep 5; }
[ -f /proc/acpi/event ] || exit 1
while read x /proc/acpi/event; do
case $x in
*button/power*)
echo
Power down
/dev/console
shutdown -h -P now
;;
esac
done
cut
Is it not sufficient for you?
If you talk about VMs, I found it is much easier to use Ctrl+Alt+Del
from inittab to signal shutdown, and don't bother with acpi at all.
For this to work, just change cad action in /etc/inittab to do
power down instead of reboot.
As for enabling this applet for wheezy, it definitely is not possible
at this time because of the freeze.
Thanks,
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700243: cups: Could not print with a wheezy client and hpijs driver
Hello Brian, Thanks for your full explanation. I've tried to use de ppd file of Squeeze in place, but it seems that the filter used does no longer exist on Wheezy. Anyway, I've replaced the `HP Laserjet 5600' occurrences in the ppd file of Wheezy, and now all works well ! Thank you very much. On Fri 5 Apr 2013 at 18:14:45 +0100, Brian Potkin wrote : Printers are frequently set up by using http://localhost:631 in a browser. But there are other ways. Ok. So, yes, I used the CUPS web interface for setting up my printer. Cheers, Jérôme -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel
Hi, Konrad Vrba wrote: can somebody please fix this bug? I think this will be fixed with the Wheezy D-I RC2 release which is currently prepared and expected in a few days. And yes, it's annoying. Ran into that several times. There are several workarounds posted in the related bug-reports: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703146#25 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703404#112 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704263#15 The last time I used an USB stick with a daily image added my preseeding URL as boot parameter manually. Worked fine (at least for that aspect). Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700243: cups: Could not print with a wheezy client and hpijs driver
On Sat 6 Apr 2013 at 10:32:52 +0100, Jérôme Frgacic wrote : Anyway, I've replaced the `HP Laserjet 5600' occurrences in the ppd file of Wheezy, and now all works well ! Thank you very much. Sorry, I do a little mistake, I meant `HP Laserjet 2600n'. Cheers, Jérôme -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702956: dnssec-tools: zonesigner is mangling zone file SOA records
Hello. I have the same behaviour with a DNSSEC signed zone : dnssec-signzone: error: dns_master_load: si7v.fr.zone.zs:17: si2013040507v.fr: not at top of zone I think that zonesigner replaces numbers from records which contains a number with a serial. I build dnssec-tools 2.0 from upstream and there is no problem. Best regards, Pierre Tourbeaux -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704816: rkhunter: Spurious hidden processes warning with new (20121229) C unhide program
Package: rkhunter
Version: 1.4.0-3
Severity: normal
Tags: patch, upstream
Dear Maintainer,
When rkhunter uses C unhide program (e.g. with option DISABLE_UNHIDE=0) daily
cron job generates spurious warning about found hidden processes:
Warning: Hidden processes found:
Copyright © 2012 Yago Jesus Patrick Gouin
License GPLv3+ : GNU GPL version 3 or later
NOTE : This version of unhide is for systems using Linux = 2.6
Used options:
This happens due to changes in unhide's output format/data in new version of
the program (20121229).
I'm attaching my patch (using reportbug's --attach option), which leaves
parsing of old format for versions lower than 20121229 and introduces changes
for versions = 20121229.
Changes seem to work on my system (at least when there are no hidden processes
actually found).
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages rkhunter recommends:
ii unhide 20121229-1
-- Configuration Files:
/etc/default/rkhunter changed [not included]
/etc/rkhunter.conf changed [not included]
-- debsums errors found:
debsums: changed file /usr/bin/rkhunter (from rkhunter package)
--
Regards,
Jacek Politowski
--- rkhunter.orig 2013-02-17 09:36:30.0 +0100
+++ rkhunter 2013-04-06 10:35:20.021957973 +0200
@@ -12435,7 +12435,11 @@
fi
SEEN=1
- FOUND_PROCS=`${UNHIDE_CMD} ${UNHIDE_OPTS} ${RKHTMPVAR} 21 | egrep -v '^(Unhide |yjesus@|http:|\[\*\]|$)'`
+ if [ $UNHIDE_VERS -lt 20121229 ]; then
+ FOUND_PROCS=`${UNHIDE_CMD} ${UNHIDE_OPTS} ${RKHTMPVAR} 21 | egrep -v '^(Unhide |yjesus@|http:|\[\*\]|$)'`
+ else
+ FOUND_PROCS=`${UNHIDE_CMD} ${UNHIDE_OPTS} ${RKHTMPVAR} 21 | egrep -v '^(Unhide [0-9]{8}$|Copyright . [0-9]{4} Yago Jesus Patrick Gouin$|License GPLv3\+ : GNU GPL version 3 or later$|http:\/\/www\.unhide-forensics\.info$|NOTE : This version of unhide is for systems using Linux = 2\.6.*$|Used options:.*$|\[\*\]|$)'`
+ fi
if [ -z ${FOUND_PROCS} ]; then
# Nothing found.
Bug#704744: pbuilder: umounts /{dev,run}/shm of the *host* system
At Fri, 05 Apr 2013 13:55:16 +0200,
Thorsten Glaser wrote:
Package: pbuilder
Version: 0.215
0.215 should have already fixed it, are you sure?
0.214 would do that.
Severity: critical
Justification: breaks unrelated software
I’ve just did the following:
① get https://www.mirbsd.org/cvs.cgi/contrib/hosted/tg/deb/pbuilderrc?rev=1.34
and install that file as /etc/pbuilderrc
② edit the MIRROR_wheezy line to use a local mirror
③ remove ~/.pbuilderrc
④ run sudo env DIST=wheezy cowbuilder --create
⑤ run sudo env DIST=wheezy cowbuilder --update
I’ve had /run/shm mounted a tmpfs before, as is normal for
a system running sid, and /dev/shm is a symbolic link pointing
to it.
Now, I don’t have that any more:
tglase@tglase:~ $ mount | fgrep shm; echo $?
1
tglase@tglase:~ $ ls -la /{dev,run}/shm
lrwxrwxrwx 1 root root 8 Apr 3 09:55 /dev/shm - /run/shm
/run/shm:
total 0
drwxr-xr-x 2 root root 40 Apr 5 13:49 .
drwxr-xr-x 26 root root 980 Apr 5 13:45 ..
This breaks unrelated software on the system, i.e. anything
that uses /dev/shm/ stuff. Additionally, it will *remove*
everything currently in there.
I don’t know if it was the --create or the --upgrade though.
Running sudo mount -t tmpfs swap /run/shm followed by
another instance of sudo env DIST=wheezy cowbuilder --update
however keeps the current contents of /dev/shm/ intact, so
I believe it was the --create operation. Similarily, running
sudo env DIST=wheezy cowbuilder --build feistermops_51.dsc
to compile a local package keeps it there.
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh-static
Versions of packages pbuilder depends on:
ii coreutils 8.13-3.5
ii debconf [debconf-2.0] 1.5.49
ii debianutils4.3.4
ii debootstrap1.0.48
ii dpkg-dev 1.16.10
ii wget 1.14-1
Versions of packages pbuilder recommends:
ii devscripts 2.12.6
ii fakeroot1.18.4-2
ii sudo1.8.5p2-1+nmu1
Versions of packages pbuilder suggests:
ii cowdancer 0.72
pn gdebi-corenone
pn pbuilder-uml none
-- Configuration Files:
/etc/bash_completion.d/pbuilder [Errno 2] No such file or directory:
u'/etc/bash_completion.d/pbuilder'
-- debconf information:
pbuilder/mirrorsite: http://mirror.virt.tarent.de/mirror/ubuntu
pbuilder/nomirror:
* pbuilder/rewrite: false
___
Pbuilder-maint mailing list
pbuilder-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pbuilder-maint
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700743: please update version of boto to recent one (2.8.0)
Le Wed, Apr 03, 2013 at 08:52:25PM +0200, Daniel Baumann a écrit : any chance to have an upload to experimental any time soon? the newer version is needed in order to use amazon glacier.. Dear Eric, if you are busy at the moment, would you mind a non-maintainer upload to Experimental ? The package builds fine in a Unstable chroot after upgrade to 2.8.0. I have also checked the difference between versions 2.3.0 and 2.8.0 and found no major hurdle on copyright side. - One more file under the MPL/LGPL/GPL trilicense. tests/integration/s3/other_cacerts.txt - One new file containing BSD-licensed code. tests/integration/gs/util.py Have a nice week-end, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703753: please advise on kernel upgrade text in release-notes
On Sat, Apr 6, 2013 at 08:19:11 +0200, Paul Gevers wrote: Hi kernel team, Last week I stumbled upon the current text in the release-notes about kernel/udev upgrade. If we don't update it, it says (among other things) the text below [1]. I believe this text is obsolete and was ONLY meant for the lenny to squeeze update. Do you agree that this part should be removed? Or do you think it should be rewritten (in the latter case, can you do a proposal)? If some of the current text stays, I say at least the names wheezy and squeeze are wrong. The upgrading chapter in the wheezy release notes is not yet written, so yes, much of it is obsolete and will go away. Cheers, Julien signature.asc Description: Digital signature
Bug#704625: Tested a bit further the mod_security patch I backported
On 04/06/2013 04:50 PM, Alberto Gonzalez Iniesta wrote: On Sat, Apr 06, 2013 at 02:43:39PM +0800, Thomas Goirand wrote: Hi, I installed mod_security with the patch I backported, made sure the module was loaded by Apache, and tested to query http://localhost;, then I could see the It works! default Debian Apache page. So, I'd say: so far so good, Apache doesn't crash. Salvatore, could you tell how you find out about this CVE, and are you sure that the commit you linked is fixing the problem (which I do not understand fully...)? If you confirm that you are sure it fixes the CVE, then I believe I could NMU the fixed package in the delayed queue. Hi Thomas and Salvatore, Thanks for the heads-up. Strangely I didn't get the first mail (the bug report), but luckily got Thomas' mails. I'll check this ASAP and make an upload accordingly. Cheers, Alberto Cool. I just thought I could help, since I knew a bit about Apache module programing. I hope my patch will help to have this RC solved faster, so we can think about something else for the release. Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704817: haskell-testpack: fails to build with experimental ghc
Package: haskell-testpack
Version: 2.1.1-1
Severity: normal
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch raring
haskell-testpack fails to build against experimental ghc as follows:
[3 of 3] Compiling Test.HUnit.Tools ( src/Test/HUnit/Tools.hs,
dist-ghc/build/Test/HUnit/Tools.o )
src/Test/HUnit/Tools.hs:131:57:
`maxDiscard' is not a (visible) constructor field name
src/Test/HUnit/Tools.hs:177:40: Not in scope: `maxDiscard'
make: *** [build-ghc-stamp] Error 1
There's been a patch for this in a github pull request for a while. In
accordance with private comments made by the principal uploader, and
after checking on #debian-haskell a couple of days ago, I plan to upload
a 0-day NMU for this once I get a bug number back, as follows aside from
the bug number in the changelog.
diff -u haskell-testpack-2.1.1/debian/changelog
haskell-testpack-2.1.1/debian/changelog
--- haskell-testpack-2.1.1/debian/changelog
+++ haskell-testpack-2.1.1/debian/changelog
@@ -1,3 +1,13 @@
+haskell-testpack (2.1.1-1.1) experimental; urgency=low
+
+ * Non-maintainer upload.
+ * Depend on haskell-devscripts 0.8.13 to ensure this package is built
+against experimental.
+ * Apply https://github.com/jgoerzen/testpack/pull/7 to port to QuickCheck
+2.5, which dropped the maxDiscard field.
+
+ -- Colin Watson cjwat...@debian.org Sat, 06 Apr 2013 10:51:07 +0100
+
haskell-testpack (2.1.1-1) unstable; urgency=low
* [27449fc] Imported Upstream version 2.1.1
diff -u haskell-testpack-2.1.1/debian/control
haskell-testpack-2.1.1/debian/control
--- haskell-testpack-2.1.1/debian/control
+++ haskell-testpack-2.1.1/debian/control
@@ -4,7 +4,7 @@
Uploaders: John Goerzen jgoer...@complete.org
Build-Depends: cdbs,
debhelper (= 7),
- haskell-devscripts (= 0.8),
+ haskell-devscripts (= 0.8.13),
ghc,
ghc-prof,
libghc-mtl-dev,
only in patch2:
unchanged:
--- haskell-testpack-2.1.1.orig/src/Test/HUnit/Tools.hs
+++ haskell-testpack-2.1.1/src/Test/HUnit/Tools.hs
@@ -128,7 +128,7 @@
q Integer - Int (safe bounds) prop_integer_to_int_pass]
-}
qc2hu :: QC.Testable a = Int - String - a - HU.Test
-qc2hu maxTest = qccheck (stdArgs {maxSuccess = maxTest, maxDiscard = 2})
+qc2hu maxTest = qccheck (stdArgs {maxSuccess = maxTest})
{- | Run verbose tests. Example:
@@ -174,7 +174,7 @@
Just (rnd,_) - return rnd
test MkState{ terminal = tm
, maxSuccessTests = maxSuccess args
- , maxDiscardedTests = maxDiscard args
+ , maxDiscardedTests = 2
, computeSize = case replay args of
Nothing- \n d - (n * maxSize
args)
`div` maxSuccess args
Thanks,
--
Colin Watson [cjwat...@ubuntu.com]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704625: Tested a bit further the mod_security patch I backported
Hi Alberto, hi Thomas On Sat, Apr 06, 2013 at 10:50:43AM +0200, Alberto Gonzalez Iniesta wrote: On Sat, Apr 06, 2013 at 02:43:39PM +0800, Thomas Goirand wrote: Hi, I installed mod_security with the patch I backported, made sure the module was loaded by Apache, and tested to query http://localhost;, then I could see the It works! default Debian Apache page. So, I'd say: so far so good, Apache doesn't crash. Salvatore, could you tell how you find out about this CVE, and are you sure that the commit you linked is fixing the problem (which I do not understand fully...)? If you confirm that you are sure it fixes the CVE, then I believe I could NMU the fixed package in the delayed queue. Hi Thomas and Salvatore, Thanks for the heads-up. Strangely I didn't get the first mail (the bug report), but luckily got Thomas' mails. I'll check this ASAP and make an upload accordingly. Bad you have not got the inital mail trough the BTS. :( Thank you for preparing the update. For the new option the default value is Off, if I understand it correctly, but configurable to On/Off. Could you also add a bit of Documentation for it? Could you also prepare an update for squeeze-security for ? Please target there squeeze-security (instead of stable-security) in case the update will happen just when wheezy get's released ;-) to prepare for an update to security-master? Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682705: gimp 2nd level dialogs freeze
I have the same problem under debian kde gimp2.8.2 and 2 screens I solved it : maximise the window of the open dialog then restaure Also work :cover the dialog with an another window -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691651: enabling wheezy-backports by default (Re: Backports integrated into the main archive
Control: tags -1 +patch
Thomas Goirand:
While activating backports by default can be discussed forever, I'm
quite sure that adding an option in our installer so that having
backports activated is just one click away would be a nice option to
have, always. Has this been considered?
The attached patch adds backports support to apt-setup. I've done a
successful installation using the resulting udebs.
It could be improved in two ways:
* Add support for previous release: the installer has usually
been able to install oldstable nicely. The generator could
exit or setup backports.debian.org if squeeze is installed.
* Reduce code duplication: 93backports is almost a duplicate
of 92updates. Both should probably be merged in a single
generator.
I only took a shot at this because I got tired of the discussion on
debian-backports@. I'm leaving anyone more interested to catch the ball.
:)
--
Jérémy Bobbio.''`.
lu...@debian.org: :Ⓐ : # apt-get install anarchism
`. `'`
`-
From bddacb45a3a86b27d6fed0b8892b14520652994b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=A9my=20Bobbio?= lu...@debian.org
Date: Sat, 6 Apr 2013 09:56:50 +0200
Subject: [PATCH] Add support for backports
The text added in apt-setup/services-select was adapted from
apt-setup/backports for Ubuntu.
---
debian/apt-setup-udeb.install |1 +
debian/apt-setup-udeb.templates | 16 +++--
debian/changelog|6 +++
generators/93backports | 74 +++
4 files changed, 94 insertions(+), 3 deletions(-)
create mode 100755 generators/93backports
diff --git a/debian/apt-setup-udeb.install b/debian/apt-setup-udeb.install
index bc39edd..d3af6fd 100644
--- a/debian/apt-setup-udeb.install
+++ b/debian/apt-setup-udeb.install
@@ -5,3 +5,4 @@ generators/60local usr/lib/apt-setup/generators
generators/90services-select usr/lib/apt-setup/generators
generators/91security usr/lib/apt-setup/generators
generators/92updates usr/lib/apt-setup/generators
+generators/93backports usr/lib/apt-setup/generators
diff --git a/debian/apt-setup-udeb.templates b/debian/apt-setup-udeb.templates
index 811c0b7..6b7a9a3 100644
--- a/debian/apt-setup-udeb.templates
+++ b/debian/apt-setup-udeb.templates
@@ -32,6 +32,11 @@ Type: text
# :sl2:
_Description: Scanning the release updates repository...
+Template: apt-setup/progress/backports
+Type: text
+# :sl2:
+_Description: Scanning the backports repository...
+
Template: apt-setup/local/key-error
Type: select
Default: Retry
@@ -73,13 +78,13 @@ _Description: Cannot access repository
# All services are enabled by default to allow preseeding
Template: apt-setup/services-select
Type: multiselect
-Choices-C: security, updates
+Choices-C: security, updates, backports
# SEC_HOST and VOL_HOST are host names (e.g. security.debian.org)
# Translators: the *entire* string should be under 55 columns
# including host name. In short, KEEP THIS SHORT and, yes, that's tricky
# :sl1:
-__Choices: security updates (from ${SEC_HOST}), release updates
-Default: security, updates
+__Choices: security updates (from ${SEC_HOST}), release updates, backported software
+Default: security, updates, backports
# :sl1:
_Description: Services to use:
Debian has two services that provide updates to releases: security and
@@ -92,6 +97,11 @@ _Description: Services to use:
relatively frequently and where not having the latest version could reduce
the usability of the software. It also provides regression fixes.
This service is only available for stable and oldstable releases.
+ .
+ Backported software are adapted from the development version to work with
+ this release. Although this software has not gone through such complete
+ testing as that contained in the release, it includes newer versions of
+ some applications which may provide useful features.
Template: apt-setup/multiarch
Type: string
diff --git a/debian/changelog b/debian/changelog
index adfbc62..b8863f1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+apt-setup (1:0.79~~backports1) UNRELEASED; urgency=low
+
+ * Add support for backports.
+
+ -- Jérémy Bobbio lu...@debian.org Sat, 06 Apr 2013 09:54:51 +0200
+
apt-setup (1:0.78) unstable; urgency=low
[ Updated translations ]
diff --git a/generators/93backports b/generators/93backports
new file mode 100755
index 000..f169025
--- /dev/null
+++ b/generators/93backports
@@ -0,0 +1,74 @@
+#!/bin/sh
+set -e
+
+. /usr/share/debconf/confmodule
+
+file=$1
+
+db_get apt-setup/services-select
+if ! echo $RET | grep -q backports; then
+ exit
+fi
+
+if db_get mirror/codename [ $RET ]; then
+ codename=$RET
+ db_get mirror/suite
+ suite=$RET
+
+ db_get mirror/protocol
+ protocol=$RET
+ db_get mirror/$protocol/hostname
+ host=$RET
+ db_get mirror/$protocol/directory
+ directory=/${RET#/}
+else
+
Bug#704817: NMU diff
Here's the actual NMU diff.
diff -u haskell-testpack-2.1.1/debian/changelog
haskell-testpack-2.1.1/debian/changelog
--- haskell-testpack-2.1.1/debian/changelog
+++ haskell-testpack-2.1.1/debian/changelog
@@ -1,3 +1,13 @@
+haskell-testpack (2.1.1-1.1) experimental; urgency=low
+
+ * Non-maintainer upload.
+ * Depend on haskell-devscripts 0.8.13 to ensure this package is built
+against experimental.
+ * Apply https://github.com/jgoerzen/testpack/pull/7 to port to QuickCheck
+2.5, which dropped the maxDiscard field (closes: #704817).
+
+ -- Colin Watson cjwat...@debian.org Sat, 06 Apr 2013 11:13:16 +0100
+
haskell-testpack (2.1.1-1) unstable; urgency=low
* [27449fc] Imported Upstream version 2.1.1
diff -u haskell-testpack-2.1.1/debian/control
haskell-testpack-2.1.1/debian/control
--- haskell-testpack-2.1.1/debian/control
+++ haskell-testpack-2.1.1/debian/control
@@ -4,7 +4,7 @@
Uploaders: John Goerzen jgoer...@complete.org
Build-Depends: cdbs,
debhelper (= 7),
- haskell-devscripts (= 0.8),
+ haskell-devscripts (= 0.8.13),
ghc,
ghc-prof,
libghc-mtl-dev,
only in patch2:
unchanged:
--- haskell-testpack-2.1.1.orig/src/Test/HUnit/Tools.hs
+++ haskell-testpack-2.1.1/src/Test/HUnit/Tools.hs
@@ -128,7 +128,7 @@
q Integer - Int (safe bounds) prop_integer_to_int_pass]
-}
qc2hu :: QC.Testable a = Int - String - a - HU.Test
-qc2hu maxTest = qccheck (stdArgs {maxSuccess = maxTest, maxDiscard = 2})
+qc2hu maxTest = qccheck (stdArgs {maxSuccess = maxTest})
{- | Run verbose tests. Example:
@@ -174,7 +174,7 @@
Just (rnd,_) - return rnd
test MkState{ terminal = tm
, maxSuccessTests = maxSuccess args
- , maxDiscardedTests = maxDiscard args
+ , maxDiscardedTests = 2
, computeSize = case replay args of
Nothing- \n d - (n * maxSize
args)
`div` maxSuccess args
Thanks,
--
Colin Watson [cjwat...@ubuntu.com]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675451: abcde 2.5.4 uses eyeD3
abcde 2.5.4 and later now use eye3D for MP3 tagging. See https://github.com/johnlane/abcde/blob/master/changelog Kind regards, Richard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704818: haskell-wai-extra: fails to build against current experimental
Package: haskell-wai-extra Version: 1.3.2.1-2 Severity: serious Tags: experimental User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu raring haskell-wai-extra build-depends on libghc-blaze-builder-conduit-dev ( 0.5) and ( 0.6), but blaze-builder-conduit is at version 1.0.0-1 in experimental. The current version on hackage is 1.3.3.2, and indicates support for blaze-builder-conduit 1.0.0; please could you upgrade the Debian package? Thanks, -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704819: haskell-wai-app-static: fails to build against current experimental
Package: haskell-wai-app-static Version: 1.3.1-2 Severity: serious Tags: experimental User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu raring haskell-wai-app-static build-depends on libghc-wai-dev ( 1.3) and ( 1.4), but wai is at version 1.4.0-1 in experimental. The current version on hackage is 1.3.1.2, and indicates support for wai 1.4.0; please could you upgrade the Debian package? Thanks, -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704645: [Pkg-gnupg-maint] Processed: Re: Bug#704613: cdebootstrap: signature verification bypass with manipulated InRelease file
retitle 704645 gpg --verify suggests entire file was verified, even if file contains auxiliary data thanks Hi, After some discussion I've come to the following description of this request (submitters, please correct or augment where necessary): gpg --verify filename returns a binary answer: has a valid signature, doesn't have a valid signature. This is described in the man page as Assume that the first argument is a signed file or a detached signature and verify it without generating any output. This works well for detached signatures or for files that contain only a clearsigned message and nothing else. The problem comes in when somewhere in a file a valid block of clearsigned text is present, but this block is preceded or followed by auxiliary data. Running gpg --verify on that file results in an assertion that the file has a valid signature while in fact only a part of the file was verified with no way of knowing which. As it turned out, implementors have been assuming that running gpg --verify on a file yields enough information to further process that file as if all data in it were correctly signed. It has been argued that running gpg --verify in its current form on a clearsigned file is useless as it only tells you that that something somewhere in that file has a valid signature. (There is currently a working way to verify and extract only the signed data, which is by using --status-fd and parsing its output.) I'm seeking input from GnuPG upstream for their view on this case. Cheers, Thijs signature.asc Description: This is a digitally signed message part.
Bug#704820: haskell-wai-eventsource: fails to build against current experimental
Package: haskell-wai-eventsource Version: 1.3.0.2-1 Severity: serious Tags: experimental User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu raring haskell-wai-eventsource build-depends on libghc-conduit-dev ( 0.5) and ( 0.6), but conduit is at version 1.0.0-1 in experimental. The current version on hackage is 1.3.0.4, and indicates support for conduit 1.0.0; please could you upgrade the Debian package? Thanks, -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683838: release-notes: transition: pdksh → mksh
Joost van Baal-Ilić dixit: I propose this text instead: --- section id=mksh titlePdksh to mksh transition/title ^ I’d not capitalise here, as it’s a name/“trade”mark. If you really must, I guess PDksh would make more sense. para The Public Domain Korn Shell (systemitem role=packagepdksh/systemitem) package is being retired for the release after releasename;, since commandpdksh/command is no longer maintained (it has last seen active development in 1999). /para para The MirBSD Korn Shell (systemitem role=packagemksh/systemitem) package contains its successor; it has evolved from the Public Domain Korn Shell and has been kept up to date with the POSIX standard on the shell. In debian; releasename;, systemitem role=packagepdksh/systemitem is a transitional package using a variant of systemitem role=packagemksh/systemitem built with special compatibility options to provide a commandpdksh/command binary symlink. This compatibility binary behaves a bit more like the traditional Public Domain Korn Shell then current commandmksh/command, it however Looking good so far. contains bugfixes so differs a bit. Therefore, it is not a pure drop-in replacement, and you'll have to check your Korn Shell scripts before running them with current commandpdksh/command (or commandmksh/command). This lacks a suggestion to change the scripts to use #!/bin/mksh or at least #!/bin/lksh (the “compatibility binary”), because the transitional package will go away (and, if one invests effort into scripts, changing to mksh is better anyway, as that’s the one more closely aligned to POSIX). /para para The compatibility binary is not suitable for interactive use, so as system administrator, adjust the login shell of your Korn Shell users. For minimal service interruption, do this before the upgrade of the O.S: manually install the systemitem role=packagemksh/systemitem package and change the login and/or interactive shells of users that use commandpdksh/command to commandmksh/command. Furthermore, in order to continue functionality like tab completion, copy filename/etc/skel/.mkshrc/filename into their home directories. /para Good, except tab completion always “just works”; the thing which /etc/skel/.mkshrc provides are some shell functions like pushd/popd/dirs and a nice PS1 (shell prompt). Neither of these is a regression, so “in order to continue” is also wrong. Thanks a lot for the effort! bye, //mirabilos -- “It is inappropriate to require that a time represented as seconds since the Epoch precisely represent the number of seconds between the referenced time and the Epoch.” -- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699210: unblock: setools/3.3.7-3.3
On 04/04/2013 10:10 PM, Adam D. Barratt wrote: None of arm, m68k or ppc64 are in Debian right now, so the package's buildability on them doesn't seem particularly relevant. True! But the additional symbol tables for these architectures shouldn't hurt the other architectures as well. The diff is naturally large as it contains the additional symbol tables. He added the symbol files for s390x, ppc64 and m68k. The latter is especially interesting as this architecture is currently being revived, I am supporting these guys and will hopefully adopt one of the buildds. Plus, Nick does always an excellent job when it comes to quality assurance during packaging. Which versions of the package FTBFS on s390x? There are setools binary packages in testing on that architecture, so it obviously built at some point; what changed? Interesting. I am pretty sure there was an FTBFS on s390x, I'll have to check my mail from that time. Nick, do you remember why you fixed the symbol table for s390x? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704744: pbuilder: umounts /{dev,run}/shm of the *host* system
Junichi Uekawa dixit: 0.215 should have already fixed it, are you sure? Sorry, yes, I’m sure. My desktop at work now runs sid. bye, //mirabilos -- ch you introduced a merge commit│mika % g rebase -i HEAD^^ mika sorry, no idea and rebasing just fscked │mika Segmentation ch should have cloned into a clean repo │ fault (core dumped) ch if I rebase that now, it's really ugh │mika:#grml wuahh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699210: unblock: setools/3.3.7-3.3
On Sat, 2013-04-06 at 12:48 +0200, John Paul Adrian Glaubitz wrote: On 04/04/2013 10:10 PM, Adam D. Barratt wrote: None of arm, m68k or ppc64 are in Debian right now, so the package's buildability on them doesn't seem particularly relevant. True! But the additional symbol tables for these architectures shouldn't hurt the other architectures as well. The diff is naturally large as it contains the additional symbol tables. If there are other reasons to migrate the package, potentially, but... Which versions of the package FTBFS on s390x? There are setools binary packages in testing on that architecture, so it obviously built at some point; what changed? Interesting. I am pretty sure there was an FTBFS on s390x, I'll have to check my mail from that time. Nick, do you remember why you fixed the symbol table for s390x? In a later mail he said the s390x problem was introduced in -3.1 when the arm/m68k symbols files were added. If that's the case then as wheezy only has -3 it isn't affected. 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#574947: global: newer release is available
Hi Shigio, Are you aware that Debian is currently frozen for release and has been now for quite some months? Now is not the time to be pushing for a major update, let alone one that changes several options incompatibly with previous releases. The window for that sort of thing will (hopefully) open again soon, at which point the major stumbling block becomes something that I know you are aware of, since we discussed it during the previous merge window ... I cannot feel comfortable about introducing a new interface for end-users that requires them to run a freshly generated script, from an unsecured directory, as root, as part of normal invocation and use, from distro packaged software. I expressed my concerns about this to you already, and Taisuke Yamada also proposed some alternatives, all of which you dismissed. Do you have a new solution for this that might be more acceptable? If you do I will be glad to consider it for the next release, but so far you have mentioned nothing further to me about resolving this issue, and you tie my hands somewhat if you insist this is suitable when it fairly clearly is not. Sorry, Ron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683347: fotoxx: new upstream version available
fotoxx version 13.04 is available: http://www.kornelix.com/uploads/1/3/0/3/13035936/fotoxx-13.04.tar.gz The Debian watch file needs to be updated. Is the package maintainer still active? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702668: 702668: not possible to select screen left of other screen, only clone mode is possible (solved)
Bug 702668 is solved with package linux-image-3.2.0-4-amd64. The problem with loading radeon firmware still exists. /var/log/dmesg: radeon :01:00.0: WB disabled [7.011278] [drm] fence driver on ring 0 use gpu addr 0xf800 and cpu addr 0xc98b4000 [7.015759] [drm] Loading R300 Microcode [7.119070] sd 0:0:0:0: Attached scsi generic sg0 type 0 [7.119796] sr 5:0:0:0: Attached scsi generic sg1 type 5 [7.119882] sr 6:0:0:0: Attached scsi generic sg2 type 5 [7.416378] platform radeon_cp.0: firmware: agent aborted loading radeon/R300_cp.bin (not found?) [7.416730] [drm:r100_cp_init] *ERROR* Failed to load firmware! [7.416738] radeon :01:00.0: failed initializing CP (-2). [7.416742] radeon :01:00.0: Disabling GPU acceleration [7.416750] [drm] radeon: cp finalized [7.416803] radeon :01:00.0: 8800379f7c00 unpin not necessary [7.416832] [drm] radeon: cp finalized [7.416835] radeon :01:00.0: no bo for sa manager. signature.asc Description: PGP signature
Bug#703810: [Piuparts-devel] Bug#703810: piuparts : /var/log/fontconfig.log not owned error
On 2013-04-06 03:06, Hideki Yamane wrote: On Fri, 05 Apr 2013 15:35:57 +0200 Andreas Beckmann a...@debian.org wrote: How did you run piuparts to get this error? Probably $ sudo piuparts -p -t /tmpfs package.deb Hmm, pbuilder base.tar.gz is minimal + build-essential, but that does not yet include fontconfig. Which was the actual package you tested? And the full piuparts output for that test will be helpful, too. I know that I can easily reproduce this with --install-purge-install (that will throw tons of false positives in other packages as well), but you seem to have experienced this with a regular run. And before overriding, I'd like to know *why* this happens. Because it shouldn't. fontconfig.log should be purged. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701081: debian-policy: mandate an encoding for filenames in binary packages
Le Mon, Apr 01, 2013 at 10:39:19AM -0700, Don Armstrong a écrit : On Fri, 29 Mar 2013, Russ Allbery wrote: I think we should require UTF-8 as the character encoding for file names and fix the non-UTF-8 file names in the archive currently. None of the other courses of action really make any sense to me. I think we should also forbid the use of non ASCII file names in PATH and recommend that ASCII file names be used where possible, but I also agree that where ASCII cannot serve, only UTF-8 should be used. Hello everybody, Here is a somewhat clumsy proposition. sec id=filenames headingFile names/heading p The name of the files installed by binary packages in the system PATH (namely tt/bin/tt, tt/sbin/tt, tt/usr/bin/tt, tt/usr/sbin/tt and tt/usr/games//tt) must be encoded in ASCII. /p p The name of the files and directories installed by binary packages outside the system PATH must be encoded in UTF-8 and should be restricted to ASCII when they can be represented in that character set. /p /sec What do you think ? -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703810: [Piuparts-devel] Bug#703810: Bug#703810: piuparts : /var/log/fontconfig.log not owned error
On 2013-03-24 10:43, Holger Levsen wrote: I wonder why we don't just ignore all changes in /var/log ? (I might miss something (obvious?), due to traveling and very little sleep.) Because we want to find the packages that don't purge their logfiles. For /var/log modification of existing files could be allowed, but creation/removal should trigger an error. But currently we don't have such a granularity. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699210: unblock: setools/3.3.7-3.3
On 04/06/2013 12:53 PM, Adam D. Barratt wrote: If there are other reasons to migrate the package, potentially, but... Well, there aren't. Which versions of the package FTBFS on s390x? There are setools binary packages in testing on that architecture, so it obviously built at some point; what changed? Interesting. I am pretty sure there was an FTBFS on s390x, I'll have to check my mail from that time. Nick, do you remember why you fixed the symbol table for s390x? In a later mail he said the s390x problem was introduced in -3.1 when the arm/m68k symbols files were added. If that's the case then as wheezy only has -3 it isn't affected. Ah, right, now I remember. He fixed the symbol tables for m68k which triggered the problems on s390x, then he fixed s390x and ppc64 such that the package builds fine on all architectures. Anyway, you're right Adam, there isn't really a reason to unblock this. Please go ahead and close this unblock request. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702668: 702668: not possible to select screen left of other screen, only clone mode is possible (solved)
Bug 702668 is solved with package linux-image-3.2.0-4-amd64. The problem with loading radeon firmware still exists. Please undo the merge with 697229. signature.asc Description: PGP signature
Bug#593988: Bug reproduced
found 593988 0.9.4.0-10 thanks Hi, (I'm not the reporter, but) I can confirm the bug on nm 0.9.4.0-10. Using a very long WPA key (with special characters) fails but using a shorter one works (without special characters). Where is the key stored? -- Mathieu
Bug#704805: Depend precisely on a versionned R API via R:Depends.
On 6 April 2013 at 12:58, Charles Plessy wrote: | Package: r-base-dev | Version: 3.0.0-2 | Severity: wishlist | Tags: patch | | Hi Dirk, | | in light with the recent discussion and suggestions about the rare API | breakages with R, I would like to propose the following: | | - R provides a virtual package, for instance, 'r-api-3'. This name is |modified (for instance to 'r-api-4', 'r-api-3b', etc.) when |backward-incompatible changes are introduced. | | - R library packages depend on that virtual package through the already |implemented R:Depends system, replacing the current convention of |depending on any version equal or superior to one of the r-base package |used at build time. | | This can be done with the attached patch, that I tested locally. Thanks for proposing and testing this. I am not (yet?) sold: -- there is only one provider or r-api-* -- we actually do have a greater than relation -- the version numbers already solve this -- this was needed three times in ten years I think we are overengineering this. Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698527: elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries
On 13173 March 1977, Boris Pek wrote: Package in experimental will include ElmerGUI as earlier. And this package will not pass into unstable until license issue is not solved in one way or another. Well. No. If you do that we will remove your package from the archive entirely. Experimental is not a place to have license violations in. -- bye, Joerg aj vorlon: would it be less subtle if we replaced red, green and yellow with black, white and a shade of grey? vorlon aj: and this is what a necrotic port looks like? aj vorlon: the arch qualification table, halloween edition? aj vorlon: i heard a faint pinging, and went to the firewall and what greeted my eyes? AN m68k RISED FROM THE GRAVE!!! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692995: reportbug: unblock requests: set affects src:$PACKAGE and Cc: $PACKAGE@packages.d.o
On 2013-04-06 01:47, Samuel Bronson wrote: I've written a patch implementing this, though: Thanks. * I wonder if it wouldn't be a good idea to extend the affects to the other release.debian.org tags that relate to packages (everything but britney and other). (This could be done by moving the second added line up a couple of lines.) That may useful, too. And the X-Debbugs-Cc: might be useful for other actions, too. Maybe visibly add these headers to the Pseudoheaders presented to the reporter in the editor, so that he can modify them if he wants to. (As I understood your patch, you silently add these headers upon submission) But as Sandro already said, the Release Team should give their opinion on these changes, too. * I didn't quite dare to actually send a test message to the BTS (to make sure I've got exactly the right Control: syntax), so it could use some testing from someone who will so dare (or has an actual unblock to request). This patch may be affected by bug #687679: reportbug only keeps the last pseudoheader of a type, so you can't e.g. insert 2 Control: headers ... And (at least until debbugs (and the BTS) are fixed w.r.t. #656371), you should explicitly use Control: affects -1 + src:%s to append to the affected packages, not overwrite the list (even if there is no visible difference on bug submission) Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690414: PTS: screenshots related improvements
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19.03.2013 09:40, Paul Wise wrote: On Sun, 2012-12-09 at 10:20 +0800, Paul Wise wrote: On Sat, 2012-12-08 at 17:06 +0100, Christoph Haas wrote: Indeed. Currently the software mainly uses debtags as heuristics to determine if a package would be an interesting target for having screenshots assigned. I'm open to ideas. That sounds like a good start, are you exporting this list? We can make adjustments to the heuristics as feedback comes in. Would it be possible for you to export the results of those heuristics to a machine-readable file for the PTS to read and use for suggestions? Don't expect too much. Basically it's a blacklist/whitelist thingy of facets and tags. The current configuration is: - -- # Always import packages that have one of these tags # (overrides debshots.debtags_tags_blacklist) # role::whitelist helps whitelist yelp which is otherwise just # role::documentation debshots.debtags_tags_whitelist = made-of::font role::program x11::theme # Do not import packages that have one of these facets debshots.debtags_facets_blacklist = # Do not import packages that have one of these tags debshots.debtags_tags_blacklist = role::app-data devel::doc role::documentation role::source admin::kernel role::devel-lib role ::debug-symbols devel::library special::auto-inst-parts role::shared-lib # Do not assign tags to packages with these facets debshots.debtags_facets_ignorelist = scope special culture qa iso15924 # Do not assign these tags to packages debshots.debtags_tags_ignorelist = works-with::TODO - -- HTH, Christoph -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlFgDBMACgkQCV53xXnMZYZzUACeM0YDwMmn11JvkGeUizYVBm5v LzIAoNvK06X3vgkXg0BCRPq6TzYWzOt/ =K+YB -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#704606: Change in 2.15.3-2 prevents rebuild of package with a dot in their name.
hi, Am Freitag, 5. April 2013, 19:46:32 schrieb Dirk Eddelbuettel: We cannot break exiting r-cran-* packages. We have 150+ of them. i fully understand. and i never said you should break packages. Try to accomodate your needs within roxyPackage. already did, it doesn't care now. but some packages might not build for others if not build with roxyPackage. | there are a couple of R plugin packages for RKWard[2,3] which we would | like to rwkward has been Debian package since 2005. i know, i'm involved in its development since 2006. i'm talking about plugin packages *for* RKWard, which are all called rk.something. that is, they all have a dot in their original name, so this issue affects all of them. | i see two possible *actual* solutions: | - either change the policy to officially allow dots in package names, | - or re-fix r-cran.mk and also fix all packages with invalid names. The Debian R Policy does not matter. You are referring to a 10-year _draft_ document. i figured there are debianized R packages, so the right procedure must be documented somehwere. i usually don't care how old a document is if i can't find a newer replacement. is there any reliable documentation on how to correctly debianize R packages, except for the draft? it's still referenced wherever you look for information on that, and all other aspects it mentions still seem to be valid, so it isn't obvious that it doesn't apply any longer. so then, the code is law, and the draft is broken. rather than dots in package names *should* be replaced by hyphens it should actually read dots in package names *must not* be replaced by hyphens, as that is the only way to come up with buildable packages. again: i really don't care at all whether i must or must not replace dots in names, or whatever. but it *should* be documented in a way that you're able to understand the process. could you update the outdated draft so that it reflects what you're doing for some years now, and lift it from a draft to a valid guideline? viele grüße :: m.eik -- :. http://reaktanz.de/blog ... http://angstalt.de ... http://C3S.cc .: signature.asc Description: This is a digitally signed message part.
Bug#704821: debbugs: bug submission does not accept Version: package/1.2-3 pseudo header
Package: debbugs Version: debbugs/2.4.1 Severity: normal Hi, the above Version: header won't be accepted by debbugs, but sending a Control: found -1 debbugs/2.4.1 later on will work. Using just Version: 1.2-3 is fine. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593988: Bug reproduced
Tested different keys, and even an 63-long suite of 'a' fails. So, the length is the problem and not the special characters. Regards Mathieu
Bug#704822: acpica-tools: leaves alternatives after purge: /usr/bin/acpixtract
Package: acpica-tools Version: 20130214-0.3 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails The leftover files are actually alternatives that were installed by the package but have not been properly removed. While there is ongoing discussion how to remove alternatives correctly (see http://bugs.debian.org/71621 for details) the following strategy should work for regular cases: * 'postinst configure' always installs the alternative * 'prerm remove' removes the alternative * 'postrm remove' and 'postrm disappear' remove the alternative In all other cases a maintainer script is invoked (e.g. upgrade, deconfigure) the alternatives are not modified to preserve user configuration. Removing the alternative in 'prerm remove' avoids having a dangling link once the actual file gets removed, but 'prerm remove' is not called in all cases (e.g. unpacked but not configured packages or disappearing packages) so the postrm must remove the alternative again (update-alternatives gracefully handles removal of non-existing alternatives). Note that the arguments for adding and removing alternatives differ, for removal it's 'update-alternatives --remove name path'. Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 0m18.8s ERROR: WARN: Broken symlinks: /usr/bin/acpixtract - /etc/alternatives/acpixtract /etc/alternatives/acpixtract - /usr/bin/acpixtract-acpica 0m20.0s ERROR: FAIL: Package purging left files on system: /etc/alternatives/acpixtract - /usr/bin/acpixtract-acpica not owned /usr/bin/acpixtract - /etc/alternatives/acpixtractnot owned cheers, Andreas acpica-tools_20130214-0.3.log.gz Description: GNU Zip compressed data
Bug#704815: Would it be possible to reenable CONFIG_ACPID
On Sat, Apr 6, 2013 at 11:05 AM, Michael Tokarev m...@tls.msk.ru wrote:
Hi Michael,
Thanks a lot for the fast reply
06.04.2013 12:56, Guido Trotter wrote:
Package: busybox-static
Version: 1:1.20.0-7
Severity: wishlist
I know that acpid was disabled on purpose, but would it be possible to
reenable it? It is useful on VMs running with busybox only, for example.
For many years, i've the following replacement for acpid:
cut
#! /bin/sh
[ -d /sys/module/button ] || { modprobe button; sleep 5; }
[ -f /proc/acpi/event ] || exit 1
while read x /proc/acpi/event; do
case $x in
*button/power*)
echo
Power down
/dev/console
shutdown -h -P now
;;
esac
done
cut
CONFIG_ACPI_PROC_EVENT is deprecated and unset in most modern kernels
(I know, I can always build my own kernel, but then again, I could
also build busybox, so that defeats the purpose). acpid in busybox can
read /dev/input/event* and at least under Xen does the right thing
(shuts down the system, with the proper config).
Is it not sufficient for you?
If you talk about VMs, I found it is much easier to use Ctrl+Alt+Del
from inittab to signal shutdown, and don't bother with acpi at all.
For this to work, just change cad action in /etc/inittab to do
power down instead of reboot.
Under kvm I can always go for the ctrl+alt+del option you suggest,
but that still requires special knowledge that the machine does the
right thing, while acpi is supposed to be more standard. Anyway I am
not sure I could easily do that under Xen too.
As for enabling this applet for wheezy, it definitely is not possible
at this time because of the freeze.
Understood, I only mentioned it because it was enabled in squeeze
before, but then again probably busybox is too important to allow
exceptions. Well, maybe it can still be discussed and updated in
wheezy+1 and backports, perhaps?
Thanks,
Guido
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704823: Slow network causes UI hangs
Package: virt-manager Version: 0.9.4-2 Severity: normal When connecting to a remote host over a slow SSH link (qemu+ssh), the virt-manager UI freezes until the connection is established. Subsequent use of the UI is sluggish at best, e.g. navigating the properties dialog or adding a resource to the host. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virt-manager depends on: ii gconf2 3.2.5-1+build1 ii librsvg2-common2.36.1-1 ii python 2.7.3-4 ii python-dbus1.1.1-1 ii python-glade2 2.24.0-3+b1 ii python-gnome2 2.28.1+dfsg-1 ii python-gtk-vnc 0.5.2-1 ii python-gtk22.24.0-3+b1 ii python-ipy 1:0.75-1 ii python-libvirt 0.9.12-11 ii python-support 1.0.15 ii python-urlgrabber 3.9.1-4 ii python-vte 1:0.28.2-5 ii virtinst 0.600.3-3 Versions of packages virt-manager recommends: ii gnome-icon-theme 3.4.0-2 ii libvirt-bin 0.9.12-11 ii python-spice-client-gtk 0.12-5 Versions of packages virt-manager suggests: pn gnome-keyringnone ii python-gnomekeyring 2.32.0+dfsg-2+b1 pn python-guestfs none ii ssh-askpass 1:1.2.4.1-9 pn virt-viewer none -- no debconf information -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#704821: debbugs: bug submission does not accept Version: package/1.2-3 pseudo header
The BTS webpage for the bug contains the following useless message: [...] Acknowledgement sent to Andreas Beckmann a...@debian.org: New Bug report received and forwarded. Copy sent to Debbugs developers debian-debb...@lists.debian.org. Your message had a Version: pseudo-header with an invalid package version: debbugs/2.4.1 please either use found or fixed to the control server with a correct version, or reply to this report indicating the correct version so the maintainer (or someone else) can correct it for you. (Sat, 06 Apr 2013 12:03:06 GMT) Full text and rfc822 format available. [...] But this error is not included to the Acknowledgement mail: On 2013-04-06 14:03, Debian Bug Tracking System wrote: Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debbugs developers debian-debb...@lists.debian.org If you wish to submit further information on this problem, please send it to 704...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702243: ITP: papi: -- papi-examples
Hi Vincent, the papi-examples package contains the prebuilt binaries, but they are not really useful: * statically linked (= huge Installed-Size: 39582 [amd64]) * missing executable bit * gzip compressed I'd suggest shipping them dynamically linked, executabel and uncompressed - or not at all, just ship the source and let the user build them. The source code is missing some parts to be useful (i.e. you can't compile the examples without these): * Makefile * papi_test.h (which is being searched in ../testlib) * the testlib content: Makefile clockcore.c do_loops.c dummy.c papi_test.h test_utils.c test_utils.h Andreas PS: more packing bugs will be found as I do more tests with papi :-) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704114: asterisk: asterisk security advisories: AST-2013-001 / AST-2013-002 / AST-2013-003
On Fri, Apr 05, 2013 at 03:24:29PM +0200, Salvatore Bonaccorso wrote: Hi Tzafrir On Fri, Mar 29, 2013 at 06:53:31AM +0100, Salvatore Bonaccorso wrote: Hi Tzafrir On Thu, Mar 28, 2013 at 09:37:30AM +0200, Tzafrir Cohen wrote: On Thu, Mar 28, 2013 at 06:23:32AM +0100, Salvatore Bonaccorso wrote: Package: asterisk Severity: grave Tags: security patch upstream Hi, the following vulnerabilities were published for asterisk. CVE-2013-2685[0]: Buffer Overflow Exploit Through SIP SDP Header CVE-2013-2686[1]: Denial of Service in HTTP server CVE-2013-2264[2]: Username disclosure in SIP channel driver For CVE-2013-2685 the tracker[3] mentions only 1.11.x. Could you doublecheck that squeeze, testing and wheezy are not affected? According to the Upstream advisories, both are in effect for 1.8 . Didn't yet check backporting it (to our 1.8 in Testing/Unstable) and to 1.6.2 in Stable. Thank you for confirming! (note my above comment was related only to one of the issues, CVE-2013-2685). Could you prepare updates to be included via unstable in wheezy? Ping? Did you had a chance to look at it already? Update: AST-2013-001 (CVE-2013-2685): Not applicable to either Stable or Testing/Unstable: new code not included yet even in 1.8. AST-2013-002 (CVE-2013-2686): Applies to Testing/Unstable but not to Stable: Testing/Unstable: see patch from Upstream. Stable: httpd code does not read HTTP POST variables. AST-2013-003 (CVE-2013-2264): Applies to both Testing and Unstable. Testing/Unstable: see patch from Upstream. Stable: Patch backported. For Unstable/Testing I include two other simple bug fixes. Both trivial backports from later 1.8.x reevisions. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704824: reportbug: submitting a followup to a templated bug should not ask the questions again
Package: reportbug Version: 6.4.4 Severity: normal Hi, using reportbug to post a followup on a templated bug, e.g. an unblock bug on the release.debian.org pseudo package should not ask the template questions again. One reason for replying is e.g. to retitle a pre-approval to an unblock, attach a new debdiff, ... Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702805: hugin crashes on startup after showing the splashscreen
On 2013-03-11 kie b...@hotsite.to wrote: Package: hugin Version: 2013.0.0~beta1+dfsg-1 Severity: normal Dear Maintainer, hugin crashes on startup after showing the splashscreen. I used the version from testing and then tried the experimental version with exactly the same result. [...] The program 'hugin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 798 error_code 8 request_code 156 minor_code 5) [...] Hello, what kind of graphic card and xorg-drivers are you using? (WWW suggests there exist problem with hugin and the closed source ATI drivers.) cu andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704825: Please make storage name configurable
Package: virtinst Version: 0.600.3-3 Severity: wishlist I want virtinst to create volumes in my storage pool not named NAME.img, but virt-NAME instead. It would be nice if this were configurable, e.g. --disk pool=default,size=20480,name=virt-%n where %n would get replaced by the name of the vhost to be created. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtinst depends on: ii python 2.7.3-4 ii python-libvirt 0.9.12-11 ii python-libxml2 2.8.0+dfsg1-7+nmu1 ii python-support 1.0.15 ii python-urlgrabber 3.9.1-4 ii qemu-utils 1.1.2+dfsg-6a virtinst recommends no packages. Versions of packages virtinst suggests: ii virt-viewer 0.5.5-3 -- no debconf information -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#704705: [Pkg-ime-devel] Bug#704705: ibus: cannot use with both Mozilla i386 apps and emacs
On Sat, Apr 6, 2013 at 2:54 PM, Osamu Aoki os...@debian.org wrote: Hi, Thanks for investigating this. I did similar. My conclusion: * ibus-gtk:i386 issue is possibly user issue with downgrade. * ibus-gtk3:i386 issue is possibly user issue with downgrade. * ibus-qt4:i386 issue is the issue of libibus-qt1 not being multiarch. So this is not bug with ibus. Here is what I did tracing your comment. Without your proof of co-installed ibus-gtk:i386 and ibus-gtk:amd64 etc., I was poking wrong things. Thanks. On Fri, Apr 05, 2013 at 04:58:22PM +0200, Toni Mueller wrote: Hi Osamu, On Fri, Apr 05, 2013 at 11:07:19PM +0900, Osamu Aoki wrote: Multiarch is well defined and implemented for libraries but for these executables used by other software, the best practice was not clear to me and may had some wrong handling. (I did think a lot on this but its been more than 6 months. My memory is vague. So I need to check everything again.) I now have several of the library packages installed in parallel, so it seems to work, after all. But in the process of converting my machine, I found that often, installing one version would sort of kill the other, and from my perspective, it's more of a hit-and-miss experience, whether two instances of a library can be installed, or not, and I apparently got tripped up over that. :/ ibus being Multi-Arch: foreign it can serve both i386 and amd64 applications by either one of ibus:i386 and ibus:amd64 but ibus:i386 and ibus:amd64 are not co-installable. But as I re-think ibus:i386 and ibus:amd64 should be co-installable. I should have said the previous following text as the following instead. ibus-gtk:i386 run-time support programs and co-installable because it is Multi-Arch: same. ibus-gtk:amd64 run-time support programs and co-installable because it is Multi-Arch: same. AFAIK, ibus:i386 and ibus:amd64 should not be co-installable. The story for input method framework's Multiarch support is that, only one input method framework run at a time, thus if you use amd64 more then you install an amd64 version of ibus, including engines like anthy, hangul, and pinyin, and also ibus-table-*. IM Modules are run-time plugins to UI toolkit, so they must be co-installable, so if you have GTK+ of both amd64 and i386, then you need both of the IM Modules. The IM Modules should communicate with the core framework using sockets, dbus, or something likewise, and the communication should not be architecture-specific. In this way can we accomplish Multiarch support of input method frameworks. So there should be some reason why these were not co-installable here. To wit, I now have, excluding tables-* etc: Oh great but what are the tables-*. I guess you mean ibus-table-*. but .. wait ... [2011-12-26] Accepted 1.3.0.20100528-3 in unstable (low) (Osamu Aoki) ibus-table-others (1.3.0.20100528-3) unstable; urgency=low * Move to utils section. Closes: #646673 * Convert to dh syntax and update package description. * Remove non-ASCII keys. Closes: #653216 -- Osamu Aoki os...@debian.org Sun, 25 Dec 2011 20:12:41 +0900 No multiarch updates were done by me but these are Architecture: all packages. So this problem can not be caused by ibus-tables-*. What is going on I think there is no need for ibus-table-* to be Multiarch because the reason I said above. ii ibus-gtk:amd641.5.1.is.1.4.2-1 amd64Intelligent Input Bus - GTK+2 support ii ibus-gtk:i386 1.5.1.is.1.4.2-1 i386 Intelligent Input Bus - GTK+2 support For you, they were co-installable eventually for you? I could not do this here too initially. When I tried first, it caused major package removal situation. I haven't tried myself, but if they aren't co-installable then it reveals some packaging mistakes. I tried to install all dependency packages of ibus-gtk and faced problem with some dependency packages. If that was caused by packages from unstable, I downgraded to testing ones. Then I was still stack with libgdk-pixbuf2.0-0 and libgtk2.0-0. Tracing this goes to libjasper. Here libjasper1 (!= 1.900.1-13) but I have 1.900.1-14 OK downgrade libjasper1. Similarly downgrade libcolord1 for ibus-gtk3. Hmmm... aptitude can select downgrade right but its display does not reflect it. This is confusing but usable... Now I have ibus-gtk/ibus-gtk3 have both i386 and amd64 co-installed. Anyway, you need to be careful for this kind of downgrade resolution problem if you are running mixed system. libibus-qt1 is not multiarch. So we can not have ibus-gt* for both arch I guess. So ibus-qt package needs to be updated for multiarch to support ibus-qt4 in multiarch setting. Yes. For example, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646973 libpcre3-dbg: Multi-Arch: same but not coinstallable with
Bug#704789: #704789: package freeplane is not orphaned
Hi, According to [0], freeplane has not its corresponding ITA bug, despite 704789 title. In fact, freeplane package is not orphaned: http://packages.qa.debian.org/freeplane You may get in touch with freeplane maintainer and ask him if he wants to orphan this package or co-maintain it with you. Thanks for your work! [0] http://qa.debian.org/~bartm/wnpp-rfs-mentors/wnpp-inconsistencies.txt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704803: [Pkg-libvirt-maintainers] Bug#704803: libvirt-bin: Dnsmasq uses /etc/hosts from host which breaks on (at least) isolated networks
Hi, On Fri, Apr 05, 2013 at 11:19:19PM -0400, Daniel Dickinson (sole proprieter) wrote: Package: libvirt-bin Version: 0.9.12-11 Severity: normal Because libvirt-bin dnsmasq instances uses hostnames and ip addresses from /etc/hosts on the host DNS requests for a hostname specified for a libvirt address (e.g. on an isolated network) also return the results from /etc/hosts. Particularly on an isolated network (where /etc/hosts ips are usually not valid) this breaks virtual hosts, or the host requesting an address from the libvirt-bin dnsmasq intending to only get a VM's address on an isolated network. /etc/hosts should not be used by libvirt-bin's dnsmasq instances IMO. Due to the freeze this isn't going to be fixed for stable. Could you check the version in experimental, we did quiet some fixing in the dnsmasq area. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683838: release-notes: transition: pdksh → mksh
Hi Thorsten, On Sat, Apr 06, 2013 at 10:48:49AM +, Thorsten Glaser wrote: Joost van Baal-Ilić dixit: I propose this text instead: --- section id=mksh titlePdksh to mksh transition/title ^ I’d not capitalise here, as it’s a name/“trade”mark. If you really must, I guess PDksh would make more sense. I propose: section id=mksh titleThe pdksh to mksh transition/title para The Public Domain Korn Shell (systemitem role=packagepdksh/systemitem) package is being retired for the release after releasename;, since commandpdksh/command is no longer maintained (it has last seen active development in 1999). /para para The MirBSD Korn Shell (systemitem role=packagemksh/systemitem) package contains its successor; it has evolved from the Public Domain Korn Shell and has been kept up to date with the POSIX standard on the shell. In debian; releasename;, systemitem role=packagepdksh/systemitem is a transitional package using a variant of systemitem role=packagemksh/systemitem built with special compatibility options to provide a commandpdksh/command binary symlink. This compatibility binary behaves a bit more like the traditional Public Domain Korn Shell then current commandmksh/command, it however Looking good so far. contains bugfixes so differs a bit. Therefore, it is not a pure drop-in replacement, and you'll have to check your Korn Shell scripts before running them with current commandpdksh/command (or commandmksh/command). This lacks a suggestion to change the scripts to use #!/bin/mksh or at least #!/bin/lksh (the “compatibility binary”), because the transitional package will go away (and, if one invests effort into scripts, changing to mksh is better anyway, as that’s the one more closely aligned to POSIX). I suggest: contains bugfixes so differs a bit. Therefore, it is not a pure drop-in replacement. So, you're advised to change your code#!/bin/pdksh/code scripts to code#!/bin/mksh/code and test them. If the test fails, you're advised to fix your scripts. If, for some reason, this is not possible, you can change them to code#!/bin/lksh/code scripts, and test them again. This test has more chances of succeeding without changing a lot of your code. However, be aware at some point in the future the transitional package will get dropped from Debian. /para (Note to self: check wether code#!/b/l/code is sane DocBook XML.) /para para The compatibility binary is not suitable for interactive use, so as system administrator, adjust the login shell of your Korn Shell users. For minimal service interruption, do this before the upgrade of the O.S: manually install the systemitem role=packagemksh/systemitem package and change the login and/or interactive shells of users that use commandpdksh/command to commandmksh/command. Furthermore, in order to continue functionality like tab completion, copy filename/etc/skel/.mkshrc/filename into their home directories. /para Good, except tab completion always “just works”; the thing which /etc/skel/.mkshrc provides are some shell functions like pushd/popd/dirs and a nice PS1 (shell prompt). Neither of these is a regression, so “in order to continue” is also wrong. snip I suggest: commandpdksh/command to commandmksh/command. Furthermore, you're suggested to copy filename/etc/skel/.mkshrc/filename into their home directories: this provides some shell functions like commandpushd/command, commandpopd/command and commanddirs/command and a nice codePS1/code (shell prompt). /para Thorsten: what do you think? Feel free to reply via IRC. Bye, Joost -- there's a TON of people who breath air, but that doesn't mean they're qualified professionals when it comes to wind-powered electric-generator engineering. http://mdcc.cx/ --http://lwn.net/Articles/408052/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704211: [release-notes] [wheezy] issues: NM conflicts with wicd-daemon, Gnome3 now depends on NM
(sorry for the dupe, forgot to include this to the BTS) On Saturday, April 06, 2013 01:47:15, Joost van Baal-Ilić wrote: Hi Chris, Thanks for these nice patches. Some comments though: In the TC-bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688772#532 has some text on why using n-m with gnome is a good idea. Yes, as I mentioned I didn't get your (previous) BTS message as email, and only saw it after-the-fact as I was about to send the patches. [I did get /this/ one as email, thankfully.] I sent these patches anyway because I also want others to have a baseline to allow further suggested changes. ;) You didn't quote that. I feel it's important: people who previously choose not to run n-m might want to reconsider that, since n-m got much improved. It's helpful to list those improvements. Okay. I can use some of the hints from your prior email to the BTS; I don't use NM much myself, so I don't have first-hand knowledge of improvements it has recently gotten. And in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688772#665 Technical Commitee stated: 6. We request that a release note is created explaining that gnome users who do not currently have NM installed consider installing it. I didn't see that reflected. Care to get that in, too? Yes, I plan to do that this morning. Would you like this in the 2.2.5.4 section, or the 5.4.2 section? (Or both?) AFAICT it makes sense to put into the 5.4.2 section, e.g. something like: It is suggested that installing NM be considered because it has features that other networking managers lack (such as IPv6 support), but if use of another network manager is desired, the NetworkManager daemon may remain installed but be permanently disabled [...] Thanks for your work! :) Thanks for yours. (More remarks below.) […] [Joost: not sure why, but I only saw your message in BTS just now and did not receive it in email.] Hrm, strange. I'll check for a bounce on my side. Yeah I looked for a rejection in my mail logs and didn't see one, so not sure what happened. -- Chris -- Chris Knadle chris.kna...@coredump.us -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699107: ITP: TorBirdy -- configures Mozilla birds for use with Tor
Hi, Jérémy Bobbio wrote (03 Feb 2013 19:56:23 GMT) : Is there any reasons to keep this package out of the Debian Mozilla Extension team [1]? It usualy makes it easier when changes are required in all Mozilla extensions at once. As explained on IRC a while ago, I do concur. Anyhow, any news on this ITP? Suggestions (as of 264a0a24): * please set Vcs-Git and Vcs-Browser in debian/control * you'll want to bump years in debian/copyright at some point 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#702243: ITP: papi: -- papi-examples
Hi, Le 06/04/2013 14:25, Andreas Beckmann a écrit : Hi Vincent, the papi-examples package contains the prebuilt binaries, but they are not really useful: Many thanks for all your constructive remarks. I think the PAPI packages are nearly in a correct state to be uploaded. However, I'm missing free time for now. Do not hesitate to commit into the debian git repo (in colab-maint on Alioth) if you wish and/or if I did not implement your remarks. Regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702805: hugin crashes on startup after showing the splashscreen
Hi Andreas, yes, this does describe my setup :( details are below. best rgds Kie graphics card: Gigabyte Silent ATI HD5750 Graphics Card 1GB DDR5 $ lspci | grep VGA 03:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Juniper [Radeon HD 5700 Series] $ glxinfo | grep -i vendor server glx vendor string: ATI client glx vendor string: ATI OpenGL vendor string: Advanced Micro Devices, Inc. $ more /etc/X11/xorg.conf Section ServerLayout Identifier aticonfig Layout Screen 0 aticonfig-Screen[0]-0 0 0 Screen amdcccle-Screen[3]-1 1920 0 EndSection Section Module EndSection Section ServerFlags Option Xinerama on EndSection Section Monitor Identifier aticonfig-Monitor[0]-0 Option VendorName ATI Proprietary Driver Option ModelName Generic Autodetecting Monitor Option DPMS true EndSection Section Monitor Identifier 0-DFP2 Option VendorName ATI Proprietary Driver Option ModelName Generic Autodetecting Monitor Option DPMS true Option PreferredMode 1920x1080 Option TargetRefresh 60 Option Position 0 0 Option Rotate normal Option Disable false EndSection Section Monitor Identifier 0-DFP3 Option VendorName ATI Proprietary Driver Option ModelName Generic Autodetecting Monitor Option DPMS true Option PreferredMode 1920x1080 Option TargetRefresh 60 Option Position 0 0 Option Rotate normal Option Disable false EndSection Section Device Identifier aticonfig-Device[0]-0 Driver fglrx Option Monitor-DFP3 0-DFP3 BusID PCI:3:0:0 EndSection Section Device Identifier amdcccle-Device[3]-1 Driver fglrx Option Monitor-DFP2 0-DFP2 BusID PCI:3:0:0 Screen 1 EndSection Section Screen Identifier aticonfig-Screen[0]-0 Device aticonfig-Device[0]-0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection Section Screen Identifier amdcccle-Screen[3]-1 Device amdcccle-Device[3]-1 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection /etc/X11/xorg.conf direct rendering: Yes server glx vendor string: ATI client glx vendor string: ATI OpenGL vendor string: Advanced Micro Devices, Inc. [ 6.836] (II) LoadModule: extmod [ 6.841] (II) LoadModule: dbe [ 6.843] (II) LoadModule: glx [ 6.847] (II) LoadModule: record [ 6.847] (II) LoadModule: dri [ 6.850] (II) LoadModule: dri2 [ 6.852] (II) LoadModule: fglrx [ 6.913] (II) LoadModule: fglrxdrm [ 6.930] (II) LoadModule: vgahw [ 6.934] (II) LoadModule: fglrxdrm [ 7.028] (II) LoadModule: vbe [ 7.661] (II) LoadModule: fb [ 7.662] (II) LoadModule: ddc [ 7.785] (II) LoadModule: ddc [ 7.787] (II) LoadModule: ramdac [ 7.787] (II) LoadModule: vgahw [ 7.787] (II) LoadModule: fb [ 7.788] (II) LoadModule: ddc [ 7.823] (II) LoadModule: glesx [ 7.836] (II) LoadModule: amdxmm [ 8.272] (II) LoadModule: evdev in /etc/X11/Xorg.conf Section Device Identifier aticonfig-Device[0]-0 Driver fglrx Option Monitor-DFP3 0-DFP3 BusID PCI:3:0:0 EndSection Section Device Identifier amdcccle-Device[3]-1 Driver fglrx Option Monitor-DFP2 0-DFP2 BusID PCI:3:0:0 Screen 1 EndSection On Sat, Apr 06, 2013 at 01:51:47PM +0200, Andreas Metzler (ametz...@downhill.at.eu.org) wrote... On 2013-03-11 kie b...@hotsite.to wrote: Package: hugin Version: 2013.0.0~beta1+dfsg-1 Severity: normal Dear Maintainer, hugin crashes on startup after showing the splashscreen. I used the version from testing and then tried the experimental version with exactly the same result. [...] The program 'hugin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 798 error_code 8 request_code 156 minor_code 5) [...] Hello, what kind of graphic card and xorg-drivers are you using? (WWW suggests there exist problem with hugin and the closed source ATI drivers.) cu andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704826: Need not detect distro with --osvariant
Package: virtinst Version: 0.600.3-3 Severity: wishlist This seems like it could be improved: % virt-install […] --os-variant=debianwheezy -l http://ftp2.de.debian.org/debian/dists/stable/main/installer-amd64/ --debug […] [Sat, 06 Apr 2013 15:01:36 virt-install 13087] DEBUG (Guest:471) Setting os type to 'linux' for variant 'debianwheezy' [Sat, 06 Apr 2013 15:01:37 virt-install 13087] DEBUG (OSDistro:65) Attempting to detect distro: […] [Sat, 06 Apr 2013 15:01:37 virt-install 13087] DEBUG (OSDistro:938) Detected a Debian distro Didn't I tell it about Debian already? ;) -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtinst depends on: ii python 2.7.3-4 ii python-libvirt 0.9.12-11 ii python-libxml2 2.8.0+dfsg1-7+nmu1 ii python-support 1.0.15 ii python-urlgrabber 3.9.1-4 ii qemu-utils 1.1.2+dfsg-6a virtinst recommends no packages. Versions of packages virtinst suggests: ii virt-viewer 0.5.5-3 -- no debconf information -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#704827: cryptsetup: please package 1.6
Package: cryptsetup Version: 2:1.4.3-4 Severity: wishlist Hi, please package cryptsetup 1.6 (and please upload to experimental if this happens before Wheezy is released). cryptsetup 1.6 supports reading the TrueCrypt on-disk format. This is a key feature to provide a nice migration path for users who have been used to non-DFSG-free software. I'd be glad to test this support early, and evaluate how it integrates with the desktop environment. Thanks for maintaining cryptsetup in Debian! 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#704565: Bug#704570: marked as done (fglrx-driver in Wheezy doesn't support some Radeon video card)
I found it has debian/fglrx-driver.NEWS, sorry for the noise. 1:12-6+point-3 in sid has much better documentation of the issue than 1:12-6+point-1 in wheezy, but unfortunately this has not been unblocked (see #688100), yet. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704606: Change in 2.15.3-2 prevents rebuild of package with a dot in their name.
On 6 April 2013 at 13:52, m.eik michalke wrote: | Try to accomodate your needs within roxyPackage. | | already did, it doesn't care now. but some packages might not build for others | if not build with roxyPackage. Ok. If there are remaining issues maybe we can sort them out on r-sig-debian. | rwkward has been Debian package since 2005. | | i know, i'm involved in its development since 2006. i'm talking about plugin My bad. I misread. | so then, the code is law, and the draft is broken. rather than dots in Correct. You are fully entitled to blame me for not following through with a proper Debian R Policy, but hey, at least I maintain the package in hopefully not too shabby a manner. One day we'll have a proper Policy. Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704828: nsis: CWD taken from symlink target, not symlink itself
Package: nsis Version: 2.46-7 Severity: normal I have an nsis file that refers to files using relative referencing, eg eg: !insertmacro MUI_PAGE_LICENSE COPYING However if I place my .nsi file outside of the base directory for my project eg: /home/user/project/folder/project.nsi and use a symlink to link the project: /home/user/project/project.nsi - /home/user/project/folder/project.nsi then makensis fails on the call open(COPYING,READ_ONLY), emitting: LicenseData: open failed COPYING If i replace the symlink with a copy of the file, then the script succeeds. makensis should not attempt to obtain the working directory from the symlink or its target, but should use the actual cwd. -- System Information: Debian Release: 6.0.6 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/3 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 nsis depends on: ii libc62.13-38 Embedded GNU C Library: Shared lib ii libgcc1 1:4.7.2-5 GCC support library ii libstdc++6 4.7.2-5 GNU Standard C++ Library v3 ii nsis-common 2.46-7 Nullsoft Scriptable Install System ii zlib1g 1:1.2.7.dfsg-13 compression library - runtime nsis recommends no packages. Versions of packages nsis suggests: pn mingw-w64 none (no description available) pn nsis-doc none (no description available) pn nsis-pluginapinone (no description available) ii wine 1.4.1-4Windows API implementation - stand -- 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#703396: libguestfs-tools: obsolete conffile not removed
On Sat, 2013-03-23 at 15:51 +0100, Hilko Bengen wrote: From which version did you upgrade? Unfortunately I had a hard drive failure recently and had to reinstall so I'm not sure which version. Based on the timing of the bug report, I guess it was from version 1:1.18.1-1+deb7u1. Thank you. I was not even aware of dpkg-mainscript-helper. One never stops learning, I guess. Indeed :) -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#629341: virtinst: fails if umask isn't permissive
Package: virtinst Version: 0.600.3-3 Followup-For: Bug #629341 I can confirm that this problem still exists and that the proposed solution is IMHO adequate. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtinst depends on: ii python 2.7.3-4 ii python-libvirt 0.9.12-11 ii python-libxml2 2.8.0+dfsg1-7+nmu1 ii python-support 1.0.15 ii python-urlgrabber 3.9.1-4 ii qemu-utils 1.1.2+dfsg-6a virtinst recommends no packages. Versions of packages virtinst suggests: ii virt-viewer 0.5.5-3 -- no debconf information -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#704830: ltsp-client-core: the init script should provide a hook for code snippets
Package: ltsp-client-core Version: 5.4.2-6 Severity: wishlist Hi, to fetch config values out of LDAP and to add them to those provided on the kernel command line or in lts.conf, code has to be executed inside of the init script. While it is possible to modify the init script in such a way using a script in init-ltsp.d [1], it would be better to have a hook inside of the initscript serching for code in some directory, say ltsp-client-core.d [1] # Save as /usr/share/ltsp/init-ltsp.d/70-edu-client-core # This snippet modifies /etc/init.d/ltsp-client-core on-the-fly. # # Get config stored in LDAP for Debian Edu ltsp clients (thin and fat). # sed -i '/Starting\ LTSP\ client.../ a\ /usr/share/ltsp/get-ldap-ltsp-config\ cat /var/cache/ltsp/ltsp_config_edu /var/cache/ltsp/ltsp_config_env\ ' /etc/init.d/ltsp-client-core Wolfgang signature.asc Description: Digital signature
Bug#703774: Acknowledgement (exabgp: exabgp won't start on boot because pid file can't be created)
Hi Joris, Thanks for the report (this bug has been fixed in the unstable version). I'm ok with a patch and I agree with the severity but I'm not used to this situation (important bug in a testing package frozen). I added my mentor in CC, if we want to add this patch for the wheezy release (would be better, though I don't know if it's feasible), what action should be taken? What is the official procedure to follow? Thanks for the interest in ExaBGP ;) Henry-Nicolas Tourneur Le samedi 23 mars 2013 16:06:22, Joris a écrit : ... and here's the right patch, sorry for the previous bad one. Cheers, Joris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704831: --channel_dev=0 build option should be removed from debian/rules
Package: mozc Version: 1.6.1187.102-1~exp2 In short, --channel_dev=0 option should be removed form debian/rules. Otherwise, Mozc reports its version as 1.6.1187.2 rather than 1.6.1187.102. Background: I know that build number was displayed by default on the candidate window of IBus and our build instruction page described that you can use --channel_dev=0 option to hide the build number. However, starting with Mozc 1.4.1033.102, the build number is no longer displayed on the candidate window even if you do not specify --channel_dev=0. Furthermore, we changed our build script so that the version can be automatically calculated by the channel name. As a result, the version will is now calculated as 1.6.1187.2 when you specify --channel_dev=0 because channel_dev=0 means that the current channel is stable.
Bug#704789: #704789: package freeplane is not orphaned
Mònica Ramírez Arceda mon...@debian.org writes: Hi, hello Mònica, According to [0], freeplane has not its corresponding ITA bug, despite 704789 title. In fact, freeplane package is not orphaned: http://packages.qa.debian.org/freeplane You may get in touch with freeplane maintainer and ask him if he wants to orphan this package or co-maintain it with you. I talked to Eric Lavarde d...@zorglub.s.bawue.de, the old freeplane maintainer, already in 2012, and he agreed that I take over freeplane! (he also helped me to update the package by answering lots of questions) Sorry for not having created an ITA bug! Thanks for your work! [0] http://qa.debian.org/~bartm/wnpp-rfs-mentors/wnpp-inconsistencies.txt Best Regards, -- Felix Natter -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704832: [patch]: locale aware ifconfig breaks completion
Package: bash-completion
Version: 1:2.0-1
Severity: normal
Dear Maintainer,
_mac_addresses() suffer from not taking care of locale awareness of ifconfig
thus breaking completion for users with non english locale settings.
line 824 needs to be changed:
824 - COMPREPLY+=( $( ifconfig -a 2/dev/null | sed -ne \
824 + COMPREPLY+=( $( LC_ALL=C ifconfig -a 2/dev/null | sed -ne \
Sidenote:
As a measure of precaution _available_interfaces() should probably be
fixed in the same way but it does currently not break there.
Further more the sed expression in line 825 does not yield anything here.
compare the original:
$ LC_ALL=C ifconfig -a | sed -ne
s/.*[[:space:]]HWaddr[[:space:]]\{1,\}\($re\)[[:space:]]*$/\1/p
nothing
with
$ LC_ALL=C ifconfig -a | sed -ne
s/.*[[:space:]]HWaddr[[:space:]]\{1,\}\($re\)//p
xx:xx:xx:xx:xx:xx
-- System Information:
Debian Release: 7.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500,
'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bash-completion depends on:
ii bash 4.2+dfsg-1
ii dpkg 1.16.10
bash-completion recommends no packages.
bash-completion suggests no packages.
-- Configuration Files:
/etc/profile.d/bash_completion.sh changed [not included]
-- no debconf information
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701081: debian-policy: mandate an encoding for filenames in binary packages
On Sat, Mar 16, 2013 at 03:40:19PM -0700, Jonathan Nieder wrote: Russ Allbery wrote: For me, allowing the correct spellings of words and the correct names of things to be represented in file names is important enough to rise to an ethical goal that I would advocate adopting. This. Among the examples listed the only one I found convincing was Certinomis_-_Autorité_Racine.crt It might be advantageous for the certification autority to use UTF-8 to encode its name, but the benefit for the user of the system is something entirely different. As long as the user is using UTF-8 locale and the terminal is able to handle the script properly, there might be little harm done. However this does not need to be the case. Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703146: Better debootstrap InRelease handling fix
Hello Benjamin, Benjamin Cama benjamin.c...@telecom-bretagne.eu (27/03/2013): Yes, this would be a far better solution. But a quick look at gnupg doesn't make that look easy. I'll give up on this solution for now, and let InRelease files unhandled. thanks for your efforts anyway. Mraw, KiBi. signature.asc Description: Digital signature
Bug#464471: Bug #464471 still here or dead for ages?
On Sun, 2013-03-31 at 12:11 +0200, Christian PERRIER wrote: Paul, can you try reproducing this bug you reported quite a while ago? Sorry for the delay, I had a hardware failure and am in catch-up mode, hopefully I will be able to respond this week. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#704705: [Pkg-ime-devel] Bug#704705: ibus: cannot use with both Mozilla i386 apps and emacs
Hi, On Sat, Apr 06, 2013 at 08:35:33PM +0800, Aron Xu wrote: On Sat, Apr 6, 2013 at 2:54 PM, Osamu Aoki os...@debian.org wrote: My conclusion: * ibus-gtk:i386 issue is possibly user issue with downgrade. * ibus-gtk3:i386 issue is possibly user issue with downgrade. I don't understand this comment. AFAIK, ibus:i386 and ibus:amd64 should not be co-installable. Indeed, I can have only one of these at the time. Modules. The IM Modules should communicate with the core framework using sockets, dbus, or something likewise, and the communication should not be architecture-specific. In this way can we accomplish Multiarch support of input method frameworks. Sounds good to me. But I don't understand much about GUI programming... :/ So there should be some reason why these were not co-installable here. To wit, I now have, excluding tables-* etc: Oh great but what are the tables-*. I guess you mean ibus-table-*. Yes, sorry for the confusion. I think there is no need for ibus-table-* to be Multiarch because the reason I said above. Yes, they are all architecture all, so there is no action required. ii ibus-gtk:amd641.5.1.is.1.4.2-1 amd64Intelligent Input Bus - GTK+2 support ii ibus-gtk:i386 1.5.1.is.1.4.2-1 i386 Intelligent Input Bus - GTK+2 support For you, they were co-installable eventually for you? I could not do this here too initially. When I tried first, it caused major package removal situation. I was struggling with this as well, and that led to my initial bug report. As I wrote, trying to co-install these, and other relevant, packages is quite a bit of a hit-and-miss experience. I think this should be a limitation in apt and aptitude. What I did to co-install these packages, was to actually download the packages individually, then installing them like this: # dpkg -i pkg1 pkg2 pkg3 ... Please note that this is neither an acceptable solution for the average end user, nor is it straightforward: You have to co-install all relevant packages in one go, otherwise, you'll end up with eg. only the i386 versions of it, or whichever version you specified last. I haven't tried myself, but if they aren't co-installable then it reveals some packaging mistakes. As things currently stand, it looks like these packages are co-installable, just not via apt or aptitude. with some dependency packages. If that was caused by packages from unstable, I downgraded to testing ones. Then I was still stack with libgdk-pixbuf2.0-0 and libgtk2.0-0. Tracing this goes to libjasper. Here libjasper1 (!= 1.900.1-13) but I have 1.900.1-14 $ dpkg -l libgdk-pixbuf2.0-0 libgtk2.0-0 libjasper1 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture +++--===- ii libgdk-pixbuf2.0-0:amd64 2.26.1-1amd64 ii libgdk-pixbuf2.0-0:i386 2.26.1-1i386 ii libgtk2.0-0:amd642.24.10-2 amd64 ii libgtk2.0-0:i386 2.24.10-2 i386 ii libjasper1:amd64 1.900.1-13 amd64 ii libjasper1:i386 1.900.1-13 i386 libjasper1 1.900.1-14 is in unstable, not in testing. OK downgrade libjasper1. Similarly downgrade libcolord1 for ibus-gtk3. $ dpkg -l libcolord1 ibus-gtk3 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture +++--===- ii ibus-gtk3:amd64 1.5.1.is.1.4.2-1amd64 ii ibus-gtk3:i386 1.5.1.is.1.4.2-1i386 ii libcolord1:amd64 0.1.21-1amd64 Maybe I have a problem there, with libcolord1... Anyway, you need to be careful for this kind of downgrade resolution problem if you are running mixed system. Yes. I've written a script to download packages at specific versions to have the same versions for both architectures. Otherwise, if the versions differ, dpkg refuses to install anything. But I had to use --force-overwrite plenty of times, anyway. libibus-qt1 is not multiarch. So we can not have ibus-gt* for both arch I guess. So ibus-qt package needs to be updated for multiarch to support ibus-qt4 in multiarch setting. That would be great! Please have a try with Fcitx, as I'm using its Multiarch support in my everyday life. It works
Bug#688437: RFS: loook
Hello, I retry it again. I upload a new revision of th package to http://mentors.debian.org https://mentors.debian.net/package/loook Kind regards Mechtilde signature.asc Description: OpenPGP digital signature
