Bug#677788: [patch] multi-arch for lesstif2
This patch works for me, and allows me to upgrade ia32-libs:amd64 to
the sid version.
IMO, this bug is important enough to fix in wheezy, as it affects the
ability to upgrade ia32-libs. I'd be happy to NMU, if the maintainers
don't mind.
Peter
diff -u lesstif2-0.95.2/debian/rules lesstif2-0.95.2/debian/rules
--- lesstif2-0.95.2/debian/rules
+++ lesstif2-0.95.2/debian/rules
@@ -11,11 +11,16 @@
export DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
export DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
+DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
SHELL := sh -e
BUILD := build
+LIBDIR := usr/lib/$(DEB_HOST_MULTIARCH)
+LIB_LIBDIR := debian/lesstif2/$(LIBDIR)
+DEV_LIBDIR := debian/lesstif2-dev/$(LIBDIR)
CARGS := \
+ --libdir=/$(LIBDIR) \
--with-gnu-ld --enable-static --prefix=/usr \
--disable-verbose \
--disable-build-12 --disable-build-20 --enable-build-21 \
@@ -70,15 +75,16 @@
dh_installdirs
$(MAKE) DESTDIR=$(CURDIR)/debian/lesstif2 -C build/lib/Xm-2.1 install
$(MAKE) DESTDIR=$(CURDIR)/debian/lesstif2 -C build/lib/Mrm-2.1 install
- mv debian/lesstif2/usr/lib/*.a debian/lesstif2-dev/usr/lib
- mv debian/lesstif2/usr/lib/*.so debian/lesstif2-dev/usr/lib
- rm -f debian/lesstif2/usr/lib/*.la
+ install -d $(DEV_LIBDIR)
+ mv $(LIB_LIBDIR)/*.a $(DEV_LIBDIR)
+ mv $(LIB_LIBDIR)/*.so $(DEV_LIBDIR)
+ rm -f $(LIB_LIBDIR)/*.la
# Work around libtool bug where make install will relink the libraries
# with the current system libraries.
find build/lib/Xm-2.1/.libs build/lib/Mrm-2.1/.libs \
-type f -name '*.so.*[^T]' | \
- xargs cp --target-directory debian/lesstif2/usr/lib
- chmod a-x debian/lesstif2/usr/lib/*
+ xargs cp --target-directory $(LIB_LIBDIR)
+ chmod a-x $(LIB_LIBDIR)/*
$(MAKE) DESTDIR=$(CURDIR)/debian/lesstif2-dev \
-C build/include/Motif-2.1 install
$(MAKE) DESTDIR=$(CURDIR)/debian/lesstif-doc \
@@ -101,10 +107,8 @@
{ \
cd debian/lesstif-bin; \
rm etc/X11/mwm/*; \
- mv usr/lib/X11/app-defaults etc/X11; \
- rmdir usr/lib/X11; \
- rmdir usr/lib; \
- cd ../..; \
+ mv $(LIBDIR)/X11/app-defaults etc/X11; \
+ rmdir $(LIBDIR)/X11 $(LIBDIR) usr/lib; \
}
for p in man1/uil.1 man1/ltversion.1 man1/mwm.1 man1/lesstif.1 \
man1/xmbind.1 man5/mwmrc.5 man5/VirtualBindings.5; do \
diff -u lesstif2-0.95.2/debian/control lesstif2-0.95.2/debian/control
--- lesstif2-0.95.2/debian/control
+++ lesstif2-0.95.2/debian/control
@@ -11,6 +11,8 @@
Package: lesstif2
Architecture: any
+Pre-Depends: multiarch-support
+Multi-Arch: same
Depends: ${shlibs:Depends}, ${misc:Depends}
Conflicts: libmotif
Replaces: libmotif
@@ -22,6 +24,7 @@
Package: lesstif2-dbg
Architecture: any
+Multi-Arch: same
Section: debug
Priority: extra
Depends: lesstif2 (= ${binary:Version}), ${misc:Depends}
Bug#681350: libconvert-asn1-perl: use strict breaks smbldap-tools
2012/7/12 Salvatore Bonaccorso car...@debian.org Could you give more information on which problems you see with smbldap-tools? Should the bugreport reassigned to smbldap-tools? I've opened the bug report 680939 680...@bugs.debian.org to smbldap-tools. Smbldap-tools is a set of perl scripts designed to manage user and groupaccounts stored in an LDAP directory. (website description) Some scripts of the package simple do not works with use sctrict enabled. The Debian version is 0.9.7, but 0.9.8 (latest from developers) do not works too. The error returned with smbldap-userlist is: Can't use string (['username','uidNumber','uid']) as an ARRAY ref while strict refs in use at /usr/share/perl5/Convert/ASN1/_encode.pm line 269. Smbldap-tools is needed while using Samba + LDAP. I sent an email do smbldap-tools developers about the problem and will update here when I get some more information about.
Bug#676084: obexftp: FTBFS: ruby_wrap.c:1991:5: error: format not a string literal and no format arguments [-Werror=format-security]
tags 676084 + patch
thanks
Hi,
I created debdiff include Hendrik' patch which revise this problem.
I attached.
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
obexftp-0.23.debdiff
Description: Binary data
Bug#681270: causes FTBFS of pymvpa2 on s390x: TypeError: Improper input parameters in leastsq call
On Thu, 12 Jul 2012, Denis Laxalde wrote: that was it -- assuring 'int' storage to be passed instead of npy_intp (which is long int on s390x and int on s390) resolves this issue... Good to know. fitpack (interpolate) might also benefit from this. may be -- at least there were no gcc warnings about incompatible casts now I wonder what would be the cleanest patch;-) (also running unittests with this fix to see how many tests get fixed) I don't know myself. Best is probably to ask on scipy-dev mailing list or to report the bug in scipy tracker. yeah -- I will report upstream -- my C/C++-foo is too aged. -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681408: Change a+w to u+w in Makefile.in to fix CVE-2012-3386
Package: libpng Version: 1.2.49-1 Severity: important Tags: security https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3386 http://security-tracker.debian.org/tracker/CVE-2012-3386 Change a+w to u+w in Makefile.in to fix CVE-2012-3386 diff -urNp libpng-1.2.49/Makefile.in libpng-1.2.50/Makefile.in --- a/Makefile.in 2012-03-29 15:47:09.0 +1100 +++ b/Makefile.in 2012-07-10 10:37:13.0 +1000 @@ -1146,7 +1146,7 @@ distcheck: dist *.zip*) \ unzip $(distdir).zip ;;\ esac - chmod -R a-w $(distdir); chmod a+w $(distdir) + chmod -R a-w $(distdir); chmod u+w $(distdir) mkdir $(distdir)/_build mkdir $(distdir)/_inst chmod a-w $(distdir) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681409: xserver-xorg-input-all: Keyboard suddenly unresponsive, mouse still works
Package: xserver-xorg-input-all Version: 1:7.7+1 Severity: important Since the last couple weeks, once every couple of days my keyboard suddenly stops responding. The mouse still works, so I use that to logout of my my window manager (LXDE) and once I am back to gdm the keyboard works again. Same behavior with XFCE window manager. Running up-to-date testing on a Toshiba Satellite C675 (PSC3UU-00N00G) notebook. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xserver-xorg-input-all depends on: ii xserver-xorg-input-evdev 1:2.7.0-1+b1 ii xserver-xorg-input-synaptics 1.6.2-1 Versions of packages xserver-xorg-input-all recommends: ii xserver-xorg-input-wacom 0.15.0+20120515-1 xserver-xorg-input-all 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#681410: false postives for arch-dependent-file-not-in-arch-specific-directory diagnose
Package: lintian Severity: important while getting python3.3 ready for multiarch, I noticed a lot of false positives: E: libpython3.3-dev: arch-dependent-file-not-in-arch-specific-directory usr/lib/python3.3/config-3.3m-x86_64-linux-gnu/libpython3.3m-pic.a So maybe better check if the path either contains the multiarch name or the debian architecture name. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681411: sdic: sdic.info direntry
Package: sdic Version: 2.1.3-22 Severity: normal File: /usr/share/info/sdic.info.gz Tags: patch /usr/share/info/dir contains for sdic * SDIC: (Dictionary Viewer). but pressing Ret on that gets an error Info file Dictionary Viewer does not exist where I hoped it would open sdic.info. Changing the texi/sdic.texi @direntry per below makes it work for me, --- sdic.texi.orig 2012-07-13 09:55:28.0 +1000 +++ sdic.texi 2012-07-13 09:56:29.0 +1000 @@ -8,7 +8,7 @@ @dircategory Emacs @direntry -* SDIC: (Dictionary Viewer). +* SDIC: (sdic). Dictionary Viewer. @end direntry @ifinfo -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages sdic depends on: ii bsdmainutils 9.0.1 ii dpkg 1.16.4.2 ii emacs21 [emacsen]21.4a+1-5.7 ii emacs22-gtk [emacsen]22.3+1-1.2 ii emacs23 [emacsen]23.4+1-3 ii install-info 4.13a.dfsg.1-10 ii xemacs21-mule [emacsen] 21.4.22-3.2 sdic recommends no packages. Versions of packages sdic suggests: pn sdic-edict none pn sdic-eijiro none pn sdic-gene95 none -- no debconf information
Bug#452393: [PROPOSAL] clarify overstep between required and important priorities
Julien Cristau jcris...@debian.org writes: As far as I can tell the following packages are Priority: required but not Essential: yes (in sid/amd64/main), or (pre-)depended on by an Essential package (possibly recursively): - debconf-i18n, liblocale-gettext-perl, libtext-charwidth-perl, libtext-iconv-perl, libtext-wrapi18n-perl: since debconf 1.5.39 -i18n is only a Recommends. Could probably be downgraded to important? - mawk: one of the alternatives for base-files' Pre-Depends, so actually pseudo-essential - xz-utils: Jonathan covered this Thank you very much for doing this research! -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#452393: [PROPOSAL] clarify overstep between required and important priorities
Jonathan Nieder jrnie...@gmail.com writes: diff --git i/policy.sgml w/policy.sgml index 52dbb26a..544308f8 100644 --- i/policy.sgml +++ w/policy.sgml @@ -757,16 +757,11 @@ taglist tagttrequired/tt/tag item - Packages which are necessary for the proper - functioning of the system (usually, this means that - dpkg functionality depends on these packages). - Removing a ttrequired/tt package may cause your - system to become totally broken and you may not even - be able to use prgndpkg/prgn to put things back, - so only do so if you know what you are doing. Systems - with only the ttrequired/tt packages are probably - unusable, but they do have enough functionality to - allow the sysadmin to boot and install more software. + Packages tagged ttEssential: yes/tt and their + dependencies. + Systems with only the ttrequired/tt packages are + probably unusable, but they do have enough functionality + to allow the sysadmin to boot and install more software. /item tagttimportant/tt/tag item Please retain the sentence starting Removing a ttrequired/tt package Otherwise, seconded. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681176: live-boot: persistence mounting fails if live-persistence.conf contains source=. stanza
tags 681176 + pending thanks Hi, Nemo Inis wrote (11 Jul 2012 06:13:53 GMT) : I believe the bug is a typo at line 1307 of lib/boot/misc-helpers.sh, which reads: [...] but should read instead: [...] Fixed in Git, thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681348: python2.7-dbg: debug information missing?
On 12.07.2012 16:21, Jakub Wilk wrote: Package: python2.7-dbg Version: 2.7.3-1 Severity: important Usertags: serious /usr/lib/debug/usr/bin/python2.7 doesn't seem to contain enough debug information for gdb to even display line numbers: I can't see how this is happening. it's built with -g, and dh_strip is used to strip the binaries. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681412: debian-handbook: chapter 9: de-emphasize de-emphasize discussion of (long) deprecated protocols
Package: debian-handbook Version: 6.0+20120509 Severity: minor This is highly subjective, of course, so apologies in advance. The section on Remote logins begins with a discussion of Telnet and a sidebar about the r-commands; in addition, the telnet section seems to imply that telnet-ssl might be a workable option for remote shell. IMHO it might serve the reader better to focus solely on SSH here, and leave only the briefest mention of deprecated protocols to a sidebar or footnote. It's been a long time since any major distro that I know of has shipped with telnetd installed, and anyone who even knows about rsh/rcp should know better by now than to want to use them. (Case in point: I started using Linux back in 2003, and even back then these protocols were deprecated). As for telnet-ssl; if there's a business case that would make this even an option to consider over SSH, I would think it'd be the extreme exception. IMHO, it's probably best not to mention it. Obviously, it's good advice, but it's hopefully unnecessary at this point (or at least requires less emphatic placement). -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) 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#681413: RFP: ruby-rvm -- Ruby Version Manager
Package: wnpp Severity: wishlist * Package name: ruby-rvm Version : 1.14.5 Upstream Author : Wayne E. Seguin wayneeseg...@gmail.com * URL : https://rvm.io/ * License : Apache 2.0 Programming Lang: ruby Description : Ruby Version Manager RVM is a command-line tool which allows you to easily install, manage, and work with multiple ruby environments from interpreters to sets of gems. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654958: debian-policy: Document VCS fields.
Jonathan Nieder jrnie...@gmail.com writes: diff --git a/policy.sgml b/policy.sgml index 52dbb26a..371123e1 100644 --- a/policy.sgml +++ b/policy.sgml @@ -2631,6 +2631,7 @@ Package: libc6 itemqref id=sourcebinarydepsttBuild-Depends/tt et al/qref/item itemqref id=f-Standards-VersionttStandards-Version/tt/qref (recommended)/item itemqref id=f-HomepagettHomepage/tt/qref/item + itemqref id=f-VCS-fieldsttVCS fields/tt/qref/item This is the only field in this index that doesn't list an actual field name. Minor, but for consistency should we instead say ttVcs-Browser/tt, ttVcs-Git/tt, et al.? (Git because it's the most commonly-used one, IIRC.) /list /p @@ -2728,6 +2729,7 @@ Package: libc6 itemqref id=f-ChecksumsttChecksums-Sha1/tt and ttChecksums-Sha256/tt/qref (recommended)/item itemqref id=f-FilesttFiles/tt/qref (mandatory)/item + itemqref id=f-VCS-fieldsttVCS fields/tt/qref/item Likewise here. (Here, we've always listed every single field in the past, but I've always thought that section heading for the Build-Depends family was ugly and would like to change it to use et al. here as well.) + sect1 id=f-VCS-fields + headingVersion Control System (VCS) fields/heading + + p + Debian source packages are increasingly developed using VCSs. The + purpose of the following fields is to indicate a publicly accessible + repository where the package is developed. Package is ambiguous. I think we need to make it crystal-clear that this is for the Debian packaging, not for upstream's repository. That's the main thing that people get confused by. How about where the Debian source package is developed? + taglist + tagttVcs-Browser/tt/tag + item + p + HTTP URL of a web interface for browsing the repository. *Very* minor nit: Some people now only provide HTTPS, not HTTP, on their web hosts on the grounds that everything one does on-line should be encrypted by default. I don't think the HTTP here is adding anything; I would just say URL of a web interface for browsing the repository. + tag + ttVcs-Arch/tt, ttVcs-Bzr/tt (Bazaar), ttVcs-Cvs/tt, + ttVcs-Darcs/tt, ttVcs-Git/tt, ttVcs-Hg/tt + (Mercurial), ttVcs-Mtn/tt (Monotone), ttVcs-Svn/tt + (Subversion) + /tag + item + p + The field name identifies the VCS. The field's value uses the + version control system's conventional syntax for describing + repository locations and should be sufficient to locate the + repository and access it anonymously on a branch used for + packaging. + /p ...on the default branch used for packaging new releases perhaps? It's hard to figure out what to say here about repositories where each Debian release is on a new branch. I'm not sure how to deal with that, although we probably have to bail on the problem at least somewhat. Maybe we should instead say something like: ...and should be sufficient to locate the repository used for packaging. Ideally, it also locates the branch used for development of new Debian packages. + p + In the case of Git, the value consists of a Git URL ...of a URL. Otherwise, it sounds like the only acceptable value are specifically git:// URLs. Comma after URL. + optionally followed by the word tt-b/tt and the name of + a branch in the indicated repository, like with the + ttgit clone/tt command. If no branch is specified, the + packaging should be on the default branch. s/like with/following the syntax of/ Otherwise looks good to me. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660685: RFH: gnupg -- GNU privacy guard - a free PGP replacement
El lun, 20-02-2012 a las 21:31 +0100, Daniel Leidert escribió: Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I request assistance with maintaining the gnupg package. The package is team-maintained via alioth (pkg-gnupg group). Regards, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk9CrbEACgkQm0bx+wiPa4w28wCgpy6PdGgZhB1mohgM3Dn5epWY o5QAn2UsFOJKsFyyif7Eha7hTQUuWgGj =jxCl -END PGP SIGNATURE- I'm also interested in lending a hand. Right now I'm joining to the Debian Alioth group. Is the help still needed? -- Atte. Félix Arreola Rodríguez, Firmado con GPG, llave 1E249EE4 signature.asc Description: This is a digitally signed message part
Bug#681097: CVE-2012-3386: Information disclosure
* Moritz Muehlenhoff (muehlenh...@univention.de) wrote: Package: automake Version: 1:1.11-1.2.201001121001 Severity: important Tags: security Hi, a security issue has been found in automake. It's not earth-shattering, but we should still get it into Wheezy. http://thread.gmane.org/gmane.comp.sysutils.automake.patches/8572 This also affects the source packages automake, automake1.7, automake1.9 and automake1.10... It looks like it doesn't affect automake1.4, but I'm awaiting confirmation. Should I prepare a stable update as well or is it not worth it? -- Eric Dorland e...@kuroneko.ca ICQ: #61138586, Jabber: ho...@jabber.com signature.asc Description: Digital signature
Bug#681404: [Pkg-running-devel] Bug#681404: ITP: garmin-plugin -- browser plugin for communication with the Garmin Connect service
Quoting Ralf Treinen (trei...@debian.org): Package: wnpp Severity: wishlist Owner: Ralf Treinen trei...@debian.org * Package name: garmin-plugin Version : 0.3.12-1 Upstream Author : Andreas Diesner garminplu...@andreas-diesner.de * URL : http://www.andreas-diesner.de/garminplugin/ * License : GPL-3 Programming Lang: C++ Description : browser plugin for communication with the Garmin Connect service This browser plugin has the same methods and properties as the official Garmin Communicator Plugin (http://www8.garmin.com/products/communicator/). It can be used to transfer GPX files (Geocache Descriptions) to your garmin device using the official Garmin Javascript API. Its functionality depends on the device you use. - Edge305/Forerunner305: ReadFitnessData, ReadGpsData, No write support - Edge705/Oregon/Dakota: ReadFitnessData, ReadGpsData, Write Gpx files - Edge800: ReadFitnessData, Write Gpx/Tcx Files - Other devices: Executes external command to write Gpx to device May I suggest to replace to your garmin device by to Garmin devices? Rationale: - avoids personnalization - capitalize Garmin Also: Other devices: executes an external command to write a GPX file to the device Probably standardize on GPX, also Remarks: - will be team maintained by the the pkg-running team - possibly has to go into contrib since it is made for interaction with a non-free service. There could exist another service using the same protocol, so I think it probably can still go to main. signature.asc Description: Digital signature
Bug#681414: unblock: libpng/1.2.49-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception unblock libpng/1.2.49-2 Please unblock libpng (with udeb binary package). Upstream released libpng 1.2.50 to fix CVE-2012-3386 recently. I extracted the relevant change. The debdiff is below. debdiff libpng_1.2.49-1.dsc libpng_1.2.49-2.dsc diff -Nru libpng-1.2.49/debian/changelog libpng-1.2.49/debian/changelog --- libpng-1.2.49/debian/changelog 2012-04-09 12:14:09.0 +1000 +++ libpng-1.2.49/debian/changelog 2012-07-13 12:33:03.0 +1000 @@ -1,3 +1,11 @@ +libpng (1.2.49-2) unstable; urgency=high + + * Change a+w to u+w in Makefile.in to fix CVE-2012-3386 +Add 02-681408-CVE-2012-3386-Makefile.in.patch +Closes: #681408 + + -- Anibal Monsalve Salazar ani...@debian.org Fri, 13 Jul 2012 12:31:39 +1000 + libpng (1.2.49-1) unstable; urgency=high * New upstream version 1.2.49 diff -Nru libpng-1.2.49/debian/patches/02-681408-CVE-2012-3386-Makefile.in.patch libpng-1.2.49/debian/patches/02-681408-CVE-2012-3386-Makefile.in.patch --- libpng-1.2.49/debian/patches/02-681408-CVE-2012-3386-Makefile.in.patch 1970-01-01 10:00:00.0 +1000 +++ libpng-1.2.49/debian/patches/02-681408-CVE-2012-3386-Makefile.in.patch 2012-07-13 12:30:58.0 +1000 @@ -0,0 +1,18 @@ +http://bugs.debian.org/681408 +http://security-tracker.debian.org/tracker/CVE-2012-3386 +https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3386 + +Change a+w to u+w in Makefile.in to fix CVE-2012-3386 + +diff -urNp libpng-1.2.49/Makefile.in libpng-1.2.50/Makefile.in +--- a/Makefile.in 2012-03-29 15:47:09.0 +1100 b/Makefile.in 2012-07-10 10:37:13.0 +1000 +@@ -1146,7 +1146,7 @@ distcheck: dist + *.zip*) \ + unzip $(distdir).zip ;;\ + esac +- chmod -R a-w $(distdir); chmod a+w $(distdir) ++ chmod -R a-w $(distdir); chmod u+w $(distdir) + mkdir $(distdir)/_build + mkdir $(distdir)/_inst + chmod a-w $(distdir) diff -Nru libpng-1.2.49/debian/patches/series libpng-1.2.49/debian/patches/series --- libpng-1.2.49/debian/patches/series 2012-04-09 12:07:32.0 +1000 +++ libpng-1.2.49/debian/patches/series 2012-07-13 12:33:17.0 +1000 @@ -1 +1,2 @@ 01-legacy.patch +02-681408-CVE-2012-3386-Makefile.in.patch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681415: Add new changes from upstream
Package: mobile-broadband-provider-info Version: 20120402-1 There are several new commits on the upstream git repository, including also a new tag 20120614. The information in this package is really important for new users, so it would be great to have the updated data on the package. For example, the upstream version solves https://bugzilla.gnome.org/show_bug.cgi?id=675418 -- Marco Villegas http://marvil07.net signature.asc Description: PGP signature
Bug#648452: ITP: python-thrift -- software framework for cross-language services development (Python bindings)
[ Eric Evans ] Package: wnpp Severity: wishlist Owner: Eric Evans eev...@debian.org * Package name: python-thrift Version : 0.7.0 Upstream Author : Apache Software Foundation d...@thrift.apache.org * URL : http://thrift.apache.org * License : Apache License 2.0 Programming Lang: Python Description : software framework for cross-language services development (Python bindings) Thrift is a development framework for serialization of structured data, and the construction of RPC services. It combines a software stack with a code generation engine to build services that operate seamlessly across a number of different development languages. This package contains the Python language bindings. The description is mostly copy-and-paste from the website and will need some work, (suggestions welcome). Note: This ITP (and others) will replace #524135 For the most part this is complete; An upload to NEW can be expected within the week. Review and/or testing in the meantime would be greatly appreciated. http://anonscm.debian.org/gitweb/?p=users/eevans/python-thrift.git;a=summary http://anonscm.debian.org/gitweb/?p=collab-maint/thrift-repackage.git;a=summary Thanks, -- Eric Evans eev...@sym-link.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648453: ITP: libthrift-java -- software framework for cross-language services development (java bindings)
[ Eric Evans ] Package: wnpp Severity: wishlist Owner: Eric Evans eev...@debian.org * Package name: libthrift-java Version : 0.7.0 Upstream Author : Apache Software Foundation d...@thrift.apache.org * URL : http://thrift.apache.org * License : Apache License 2.0 Programming Lang: Java Description : software framework for cross-language services development (java bindings) Thrift is a development framework for serialization of structured data, and the construction of RPC services. It combines a software stack with a code generation engine to build services that operate seamlessly across a number of different development languages. This package contains the Java language bindings for Thrift. The description is mostly copy-and-paste from the website and will need some work, (suggestions welcome). Note: This ITP (and others) will replace #524135 For the most part this is complete; An upload to NEW can be expected within the week. Review and/or testing in the meantime would be greatly appreciated. http://anonscm.debian.org/gitweb/?p=users/eevans/libthrift-java.git;a=summary http://anonscm.debian.org/gitweb/?p=collab-maint/thrift-repackage.git;a=summary Thanks, -- Eric Evans eev...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681416: unblock: reprepro/4.12.4-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please consider unblocking package reprepro:
It fixes an unclean abort when told to generate only .bz2 index files,
avoids to stop on some unterminated line marker in .diff files
and fixes a typo in the manpage.
Thanks in advance,
Bernhard R. Link
unblock reprepro/4.12.4-1
diff -r -u -N reprepro_4.12.3-1/debian/changelog
reprepro_4.12.4-1/debian/changelog
--- reprepro_4.12.3-1/debian/changelog 2012-06-24 23:13:38.0 +0200
+++ reprepro_4.12.4-1/debian/changelog 2012-07-12 15:35:27.0 +0200
@@ -1,3 +1,13 @@
+reprepro (4.12.4-1) unstable; urgency=low
+
+ * new bugfix release
+ - fix assert() triggering when requesting only .bz2 indicies
+ - fix typo in manpage (Closes: 681105)
+ - don't stop on no-newline warnings when parsing .diff.gz files
+(Closes: 676519)
+
+ -- Bernhard R. Link brl...@debian.org Thu, 12 Jul 2012 15:30:12 +0200
+
reprepro (4.12.3-1) unstable; urgency=low
* new bugfix release
diff -r -u -N reprepro_4.12.3-1/ChangeLog reprepro_4.12.4-1/ChangeLog
--- reprepro_4.12.3-1/ChangeLog 2012-06-24 22:53:10.0 +0200
+++ reprepro_4.12.4-1/ChangeLog 2012-07-12 15:26:52.0 +0200
@@ -1,3 +1,10 @@
+2012-07-11
+ * fix bug in checking old unchanged {Packages/Sources}.bz2
+ files for existance. (Triggering even an assertion when
+ only .bz2 index files are requested).
+ * ignore diff comments about unterminated lines
+ when parsing .diff files
+
2012-06-24
* support http-method's extended 103 redirect status
* actually set REPREPRO_CONFIG_DIR in hooks as
diff -r -u -N reprepro_4.12.3-1/NEWS reprepro_4.12.4-1/NEWS
--- reprepro_4.12.3-1/NEWS 2012-06-24 22:58:01.0 +0200
+++ reprepro_4.12.4-1/NEWS 2012-07-12 15:26:52.0 +0200
@@ -1,3 +1,7 @@
+Updates between 4.12.3 and 4.12.4:
+- fix bug when only generating .bz2 indices
+- ignore diff comments about unterminated lines when parsing .diff files
+
Updates between 4.12.2 and 4.12.3:
- actually set REPREPRO_CONFIG_DIR in hooks as documented in manpage
- support 103 redirect message from apt's http method.
diff -r -u -N reprepro_4.12.3-1/release.c reprepro_4.12.4-1/release.c
--- reprepro_4.12.3-1/release.c 2012-06-07 22:57:13.0 +0200
+++ reprepro_4.12.4-1/release.c 2012-07-12 15:26:52.0 +0200
@@ -525,17 +525,20 @@
}
bool release_oldexists(struct filetorelease *file) {
- if (file-f[ic_uncompressed].fullfinalfilename != NULL) {
- if (file-f[ic_gzip].fullfinalfilename != NULL) {
- return
isregularfile(file-f[ic_gzip].fullfinalfilename)
-
isregularfile(file-f[ic_uncompressed].fullfinalfilename);
- } else {
- return
isregularfile(file-f[ic_uncompressed].fullfinalfilename);
+ enum indexcompression ic;
+ bool hadanything = false;
+
+ for (ic = ic_uncompressed ; ic ic_count ; ic++) {
+ char *f = file-f[ic].fullfinalfilename;
+
+ if (f != NULL) {
+ if (isregularfile(f))
+ hadanything = true;
+ else
+ return false;
}
- } else {
- assert (file-f[ic_gzip].fullfinalfilename != NULL);
- return isregularfile(file-f[ic_gzip].fullfinalfilename);
}
+ return hadanything;
}
static retvalue openfile(const char *dirofdist, struct openfile *f) {
diff -r -u -N reprepro_4.12.3-1/docs/reprepro.1
reprepro_4.12.4-1/docs/reprepro.1
--- reprepro_4.12.3-1/docs/reprepro.1 2012-06-24 22:53:10.0 +0200
+++ reprepro_4.12.4-1/docs/reprepro.1 2012-07-12 15:26:52.0 +0200
@@ -933,7 +933,7 @@
packages were still missing and now want to copy it to those architectures were
they are unlikely to break something (because a newbinary is already
available).
.TP
-.B unusedsource \fR[\fP\fIdistributions\fP\fR]\fP
+.B unusedsources \fR[\fP\fIdistributions\fP\fR]\fP
List all source packages for which no binary package build from them is found.
.TP
.B sourcemissing \fR[\fP\fIdistributions\fP\fR]\fP
diff -r -u -N reprepro_4.12.3-1/sourceextraction.c
reprepro_4.12.4-1/sourceextraction.c
--- reprepro_4.12.3-1/sourceextraction.c2012-06-07 22:57:13.0
+0200
+++ reprepro_4.12.4-1/sourceextraction.c2012-07-12 15:26:52.0
+0200
@@ -315,6 +315,13 @@
return RET_OK;
}
}
+ if (memcmp(p, \\ No newline at end of file, 27) == 0) {
+ if (!u_getline()) {
+ /* nothing found successfully */
+ *found_p = false;
+ return RET_OK;
+ }
+ }
if
Bug#681272: weather-util: please make -q quieter
Odd, my first message must have gotten greylisted by BDO since it's
showing up after my second message in the bug log. At any rate, I'm
attaching the patch I'll be applying in the next upstream release in
case you or anyone else using 2.0 finds it useful to apply manually
in the interim.
--
{ IRL(Jeremy_Stanley); WWW(http://fungi.yuggoth.org/); PGP(43495829);
WHOIS(STANL3-ARIN); SMTP(fu...@yuggoth.org); FINGER(fu...@yuggoth.org);
MUD(kin...@katarsis.mudpy.org:6669); IRC(fu...@irc.yuggoth.org#ccl); }
diff -BENbpru old/weather.py new/weather.py
--- old/weather.py 2012-06-26 15:19:44.0 +
+++ new/weather.py 2012-07-12 21:18:08.0 +
@@ -79,7 +79,8 @@ class Selections:
cache_search=(
self.get(cache) and self.get(cache_search)
),
-cachedir=self.get(cachedir)
+cachedir=self.get(cachedir),
+quiet=self.get_bool(quiet)
)
self.config.add_section(argument)
for item in guessed.items():
@@ -699,7 +700,8 @@ def guess(
info=False,
cache_search=False,
cacheage=900,
-cachedir=.
+cachedir=.,
+quiet=False
):
Find URIs using airport, gecos, placename, station, ZCTA/ZIP, zone.
import codecs, datetime, time, os, re, sys
@@ -732,7 +734,7 @@ def guess(
(0.995, excellent),
(1.000, ideal),
]
-print(Searching via %s...%searchtype)
+if not quiet: print(Searching via %s...%searchtype)
stations = configparser.ConfigParser()
dataname = stations
if dataname in datafiles:
@@ -796,7 +798,8 @@ def guess(
if stations.has_option(station[0], zone):
zone = eval( stations.get(station[0], zone) )
dataset = stations
-if not info and stations.has_option( station[0], description ):
+if not ( info or quiet ) \
+and stations.has_option( station[0], description ):
print(
[%s result %s] % (
action,
@@ -819,7 +822,8 @@ def guess(
if stations.has_option(expression, zone):
zone = eval( stations.get(expression, zone) )
dataset = stations
-if not info and stations.has_option(expression, description):
+if not ( info or quiet ) \
+and stations.has_option(expression, description):
print(
[%s result %s] % (
action,
@@ -841,7 +845,8 @@ def guess(
station = eval( zones.get(expression, station) )
dataset = zones
search = (expression, NWS/NOAA weather zone %s % expression)
-if not info and zones.has_option(expression, description):
+if not ( info or quiet ) \
+and zones.has_option(expression, description):
print(
[%s result %s] % (
action,
@@ -939,7 +944,8 @@ def guess(
)
if places.has_option(place, zone):
zone = eval( places.get(place, zone) )
-if not info and places.has_option(place, description):
+if not ( info or quiet ) \
+and places.has_option(place, description):
print(
[%s result %s] % (
action,
@@ -992,7 +998,8 @@ def guess(
description = zones.get(place, description)
zone = (place, 0.0)
search = ( expression, NWS/NOAA weather zone %s % place )
-if not info: print( [%s result %s] % (action, description) )
+if not ( info or quiet ):
+print( [%s result %s] % (action, description) )
if not possibilities and not station[0]:
message = No FIPS code/census area match in the %s file.\n % (
datafiles[places][0]
Bug#461110: Status of this bug report
From what I read in this bug report, it suggest *two* things: - include important packages in the standard task - make it possible to unselect them Joey clearly answered no to the second question, with the basic argument that a package one would want eventually to drop from important is probably not belonging to important. I buy that. I haven't seen an answer to the *first* question, so I'll make mine. The purpose of putting a package in standard is.exactly having it installed by default on default installs. So, merging important into standard just makes the distinction between standard and important pointless. I'm *very* tempted to mark this bug as wontfix. I'd rather buy the idea of having an important task, then maybe even other priorities but maybe extra. -- signature.asc Description: Digital signature
Bug#681417: Please reconsider package description
Package: libswt-gtk-3-java Version: 3.7-2+b1 Severity: wishlist X-Debbugs-CC: debian-l10n-engl...@lists.debian.org Dear Java Maintainers, thank you for maintaining src:swt-gtk. I'm sorry to say that IMHO at least one package description(s) is(are) problematic. An example: libswt-gtk-3-java (1). Its boilerplate in the first paragraph is reused in six other descriptions. Description: Standard Widget Toolkit for GTK+ Java library Having a look at the short description itself one could misunderstand it as too much capitalisation. Actually it does not obey the Developer's Reference recommendations (2): It repeats the package name. And though its upstream's fault (3) the package name itself is too generic. It makes sense to translate it. The Standard Widget Toolkit (SWT) is a fast and rich GUI toolkit for the Java programming language. SWT provides efficient, portable and fast access to native controls and user interface facilities on the platforms where it has been implemented. It's very much appreciated that you did *not* copy the upstream description verbatim. For sounds like geek speech to me. Perhaps I have a German point of view at the description. This package includes the SWT JAR libraries. Are you sure that Jon Doe knows what a JAR (4) is? (Sorry for citing a German source.) I would be glad if you like my suggestion: Description: Java widget toolkit for GTK+ The Standard Widget Toolkit (SWT) is a fast and rich Java GUI toolkit. For platforms with existing SWT implementations it provides efficient, portable and fast access to native controls and user interface facilities. . This package includes the SWT Java archive (jar) libraries. Kind regards, Martin 1: http://ddtp.debian.net/ddt.cgi?desc_id=67727 2: http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis 3: http://www.eclipse.org/swt/ 4: http://de.wikipedia.org/wiki/Java_Archive -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681418: debugfs is a big security hole
Package: src:linux Version: 3.2.21-3 Severity: important Tags: security As discussed here http://lists.linux-foundation.org/pipermail/ksummit-2012-discuss/2012-July/000891.html. I certainly consider mounting of debugfs to be significant security liability. I'm not at all happy that people use it as the basis for end-user applications that quietly mount debugfs if they find it isn't yet mounted. Even if their corner of debugfs is robust, all the other stuff exposed by random drivers may not be. Debian has at least one such application package (blktrace) which mounts debugfs from its init script. I would like to address this by backporting this feature: commit d6e486868cde585842d55ba3b6ec57af090fc343 Author: Ludwig Nussel ludwig.nus...@suse.de Date: Wed Jan 25 11:52:28 2012 +0100 debugfs: add mode, uid and gid options and then changing the default mode (mask) to be 0700. This should leave debugfs functional (most such applications will require root anyway) and allow users to relax permissions if they really don't care about the security problems. However, currently there is not a single place for the user options. I think that either (1) debugfs should be mounted by default in a similar way to other pseudo-filesystems, or (2) debugfs should have a noauto entry in /etc/fstab where users can set options, and packages may use 'mount /sys/kernel/debug' to mount debugfs with those options (not 'mount -t debugfs debugfs /sys/kernel/debug', as now). Ben. -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.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#676048: tess: FTBFS: tessrun fails
tags 676048 + unreproducible
thanks
Hi,
I checked this BTS, but this problem was not reproduced.
I attacehd build log with pbuilder.
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
tess_0.3.0-6_amd64.build.gz
Description: GNU Zip compressed data
Bug#681214: lynx-cur: lynx adds 8 bytes to a downloaded file
On Thu, Jul 12, 2012 at 01:48:50PM +0200, Vincent Lefevre wrote:
retitle 681214 lynx-cur: lynx doesn't truncate downloaded files to
Content-Length value
thanks
On 2012-07-11 15:19:12 +0200, Vincent Lefevre wrote:
When downloading a file from http://partage-fichiers.ens-lyon.fr/
lynx added 8 bytes to the file:
-rw-r--r-- 1 vlefevre vlefevre 59675248 2012-07-11 14:07:33 tst-exp.tar.xz
-rw-r--r-- 1 vlefevre vlefevre 59675256 2012-07-11 15:02:33 tst-exp.tar.xz.3
$ cmp tst-exp.tar.xz tst-exp.tar.xz.3
cmp: EOF on tst-exp.tar.xz
$ tail -c 8 tst-exp.tar.xz.3 | hd
35 39 36 37 35 32 34 38 |59675248|
0008
This is actually the file size. This can be reproduced on a small
file:
What you're saying is that the content length is incorrect.
RFC 2616 doesn't appear to specify behavior when the content-length is
incorrect.
--
Thomas E. Dickey dic...@invisible-island.net
http://invisible-island.net
ftp://invisible-island.net
signature.asc
Description: Digital signature
Bug#452393: [PROPOSAL] clarify overstep between required and important priorities
Julien Cristau wrote: - debconf-i18n, liblocale-gettext-perl, libtext-charwidth-perl, libtext-iconv-perl, libtext-wrapi18n-perl: since debconf 1.5.39 -i18n is only a Recommends. Could probably be downgraded to important? I think so. [1] has some context. - mawk: one of the alternatives for base-files' Pre-Depends, so actually pseudo-essential Good catch. That means the wording needs a little more work, to explain that only one of 'mawk' and 'gawk' (and one of 'sysv-rc' and 'file-rc', etc) has to be of priority required. (*) Maybe we should define it as a minimal set of packages implementing the essential functionality (§3.8) instead of defining it in terms of essential packages. Other ideas? Here's the current patch for reference. It doesn't address the point marked above with (*). [1] http://lists.alioth.debian.org/pipermail/debconf-devel/2012-March/003267.html diff --git i/policy.sgml w/policy.sgml index 52dbb26a..81511730 100644 --- i/policy.sgml +++ w/policy.sgml @@ -757,9 +757,8 @@ taglist tagttrequired/tt/tag item - Packages which are necessary for the proper - functioning of the system (usually, this means that - dpkg functionality depends on these packages). + Packages tagged ttEssential: yes/tt and their + dependencies. Removing a ttrequired/tt package may cause your system to become totally broken and you may not even be able to use prgndpkg/prgn to put things back, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680825: [Debichem-devel] Bug#680825: gromacs: FTBFS: mv: cannot stat `/«PKGBUILDDIR»/debian/gromacs-mpich/usr/lib/*.so': No such file or directory
On Wed, Jul 11, 2012 at 03:44:22PM -0400, Brad King wrote: This should fix it: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8720aa04 Ideally we should add a test for this case but I have no time now. We'll include the fix in the next 2.8.9 rc. Thank you very much for tracking down the bug. Modestas, do you think it's worth applying that patch to the cmake package and requesting a freeze exception from the RMs? I'm not sure if it affects any other packages in the archive, but I cannot find any other outright failures in this batch of FTBFS bugs that date from after the 2.8.9-rc1 upload, so it might well be just this one case. Otherwise I'll hash out a workaround for gromacs to keep it from getting removed as RC-buggy. - Nicholas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681419: Alternative dependencies on non-free packages in main
Package: tech-ctte Severity: normal As a Debian Policy delegate, I'm delegating to the Technical Committee the resolution of bugs #587279 and #616462. The current Policy wording is: In addition, the packages in main * must not require or recommend a package outside of main for compilation or execution (thus, the package must not declare a Pre-Depends, Depends, Recommends, Build-Depends, or Build-Depends-Indep relationship on a non-main package), The question at issue in these bugs is whether it is permissible for a package in main to declare a non-default alternative dependency on a package in non-free. In other words, may a package in main have a dependency of: Depends: foo | foo-nonfree (I believe that the question of whether foo-nonfree | foo should be allowed is not at issue and that the consensus is that it's not permitted. However, the Technical Committee can certainly open that discussion if desired.) Please see the bugs cited above for the complete earlier discussion. (Note that the end of #587279 has some off-topic discussion of the exact meaning of require or recommend a package that's not at issue in this bug. I don't think the requested bug about that issue was ever filed, so I'm inclined to not consider it an issue currently.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681420: squashfs-tools: hard to install on low-performance machine for no benifit (wrong compressor options on deb)
Package: squashfs-tools Version: 1:4.2-5 Severity: normal Befause of the compressor settings used in this package, to decompress either the source package or the deb packages created by this package requires 65 Megabytes of memory, which is alot, when it is taken into account that this is for absolutely no benifit. The reason/problem here is warned on in the xz(1) man page---raising the compression options of xz increases the dictionary sie the compressor uses. Using a dictionary larger than the uncompressed file is completely useless, and the entire dictionary must be in memory during decompression. What you want for highest compression levels, while using lower dictionary sizes, is xz's extreme option, however I don't think dpkg-deb exposes this. In the meantime, the default option -6, is very good, with a 8MB dictionary, however in my experimentation, using -4 or -2 keeps almost the same compression (and on small package -2e and -4e, e for --extreme) would get exactly the same compresion. Anyways, as this package is very useful on embedded systems, I think it is unacceptable to have this package using a compressor dictionary size on the .deb packages any larger than the default of 8MB. From the xz man page: The differences between the presets are more significant than with gzip(1) and bzip2(1). The selected compression settings determine the memory requirements of the decompressor, thus using a too high preset level might make it painful to decompress the file on an old system with little RAM. Specifically, it's not a good idea to blindly use -9 for everything like it often is with gzip(1) and bzip2(1). -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: armel (armv5tel) Kernel: Linux 3.4.0-tomoyo-6-gfd64aac (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages squashfs-tools depends on: ii libc6 2.13-33 ii libgcc11:4.7.1-2 ii liblzma5 5.1.1alpha+20120614-1 ii liblzo2-2 2.06-1 ii zlib1g 1:1.2.7.dfsg-13 squashfs-tools recommends no packages. squashfs-tools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629868: these man files are missing in libstdc++6-4.6-doc and libstdc++6-4.7-doc also
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/12/2012 10:13 AM, Matthias Klose wrote: On 11.07.2012 19:21, Ray Dillinger wrote: This is the standard library. It's totally fundamental. We can't allow Debian systems for programmers to NOT have man pages on this. care to send a patch? If you mean zip up the files that were in libstdc++6-4.4-doc that aren't in later versions, uh, I guess I could. But that doesn't make sense. They are in the source tree already, and I haven't modified them. They've just been skipped (not included) in the current packages. Is there any insight as to why? Somebody made a decision to not package these files when they changed from libstdc++6-4.4.doc to libstdc++6-4.5.doc (and later versions) and if I submitted a patch it would be to undo that change. So if I'm patching it I want to first understand the change. If it was a policy decision, then undoing it will make people who made that decision mad. If it's just a packaging error, then the patch would probably be fairly trivial and wouldn't require any man pages from me. If it's a policy decision, then *different* man page files are needed. It looks like we're talking about the removal of a bunch of doxygen-generated pages, which are only marginally helpful in the first place. Finally, how can I create the patch? I know how to use diff, and I can write troff or nroff man pages for anything I have enough information about, but I know nearly nothing about the .deb file format or how packages are built from the debian source trees. Ray D. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJP/1wNAAoJEAOzWkqOibfNeFYH/3yyp0U8H1TGpOPG8RGqTvJy IkYYw6erpnd0JwKx0wEVf0cfUJnL08DD8WhwUTNydWqJDjWkKrq0NNRbEqDqfwuv TplFrzBvyfluVouy3fi0fIztCHxDvniWOET4xqbMx089M4P2oz6lMo0ZClHKpKBp 1duo6rHN3PA0NC0JHyqxqk7YVUZ5F36Y0UOdPdhdamJRWm10r/NTg1mq0I9/7SyA cx6ysoZzA+NFiWriBx/q9E58/skVFPPf1iX5z/Kp4QjTM2nFMQaiPBdEmyvZiQql zIRVfeklP7htJcPGaiuMcWlRwdcErRE1XYoX4+C/fOdgaUs3QbBGkViryKGxbuw= =ShiF -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#654958: debian-policy: Document VCS fields.
Russ Allbery wrote: Maybe we should instead say something like: ...and should be sufficient to locate the repository used for packaging. Ideally, it also locates the branch used for development of new Debian packages. With s/new Debian packages/new versions of the Debian package/, makes sense. +p + In the case of Git, the value consists of a Git URL ...of a URL. Otherwise, it sounds like the only acceptable value are specifically git:// URLs. Comma after URL. Yes, ok. I was poisoned by the git-clone(1) manpage. :) It describes accepted repository address formats in a section headed GIT URLS. [... other nice suggestions snipped ...] Otherwise looks good to me. Thanks again for your help. I've applied all suggested changes. Interdiff and updated patch attached. Jonathan diff -u b/policy.sgml b/policy.sgml --- b/policy.sgml +++ b/policy.sgml @@ -2631,7 +2631,7 @@ itemqref id=sourcebinarydepsttBuild-Depends/tt et al/qref/item itemqref id=f-Standards-VersionttStandards-Version/tt/qref (recommended)/item itemqref id=f-HomepagettHomepage/tt/qref/item - itemqref id=f-VCS-fieldsttVCS fields/tt/qref/item + itemqref id=f-VCS-fieldsttVcs-Browser/tt, ttVcs-Git/tt, et al./qref/item /list /p @@ -2724,12 +2724,12 @@ itemqref id=f-UploadersttUploaders/tt/qref/item itemqref id=f-DM-Upload-AllowedttDM-Upload-Allowed/tt/qref/item itemqref id=f-HomepagettHomepage/tt/qref/item + itemqref id=f-VCS-fieldsttVcs-Browser/tt, ttVcs-Git/tt, et al./qref/item itemqref id=f-Standards-VersionttStandards-Version/tt/qref (recommended)/item itemqref id=sourcebinarydepsttBuild-Depends/tt et al/qref/item itemqref id=f-ChecksumsttChecksums-Sha1/tt and ttChecksums-Sha256/tt/qref (recommended)/item itemqref id=f-FilesttFiles/tt/qref (mandatory)/item - itemqref id=f-VCS-fieldsttVCS fields/tt/qref/item /list /p @@ -3746,13 +3746,13 @@ p Debian source packages are increasingly developed using VCSs. The purpose of the following fields is to indicate a publicly accessible - repository where the package is developed. + repository where the Debian source package is developed. taglist tagttVcs-Browser/tt/tag item p - HTTP URL of a web interface for browsing the repository. + URL of a web interface for browsing the repository. /p /item @@ -3767,13 +3767,14 @@ The field name identifies the VCS. The field's value uses the version control system's conventional syntax for describing repository locations and should be sufficient to locate the - repository and access it anonymously on a branch used for - packaging. + repository used for packaging. Ideally, it also locates the + branch used for development of new versions of the Debian + package. /p p - In the case of Git, the value consists of a Git URL - optionally followed by the word tt-b/tt and the name of - a branch in the indicated repository, like with the + In the case of Git, the value consists of a URL, optionally + followed by the word tt-b/tt and the name of a branch in + the indicated repository, following the syntax of the ttgit clone/tt command. If no branch is specified, the packaging should be on the default branch. /p From: Charles Plessy ple...@debian.org Date: Sat, 7 Jan 2012 15:00:30 +0900 Subject: Document VCS fields, using Developers's Reference §6.2.5 for inspiration. Closes: #654958 [jrnie...@gmail.com: - declared repositories should be publicly accessible - Vcs-Browser should point to a webapp - Vcs-system should use the version control system's conventional syntax - if multiple branches are used for packaging (e.g., stable, testing, sid), any one of them will do - for Vcs-Git, -b branch can be omitted when the intended branch is the default branch - list some Vcs-foo fields by name in the lists in §5.2 and §5.4 - declared repositories track development of the Debian source package, not just the upstream code - Vcs-Browser can be a web interface using any protocol (e.g., HTTPS is fine) - picking a good branch is optional Thanks to Russ Allbery for several improvements to the text.] --- policy.sgml | 49 + 1 file changed, 49 insertions(+) diff --git a/policy.sgml b/policy.sgml index 52dbb26a..7d514921 100644 --- a/policy.sgml +++ b/policy.sgml @@ -2631,6 +2631,7 @@
Bug#681421: apt: Acquire::http { proxy } should be made location-aware
Package: apt
Version: 0.9.7.1
Severity: wishlist
Dear Maintainer,
I'm using a proxy configuration for my notebook:
Acquire::http { Proxy http://ip:3142; };
However, when I switch locations (like from home to hackerspace or to work), I
need to uncomment/change that line depending on whatever location I'm at.
It would be nice if this could be automated - or that apt skips the proxy if it
is not reachable (I actually prefer the latter).
-- Package-specific info:
-- apt-config dump --
APT ;
APT::Architecture amd64;
APT::Build-Essential ;
APT::Build-Essential:: build-essential;
APT::Install-Recommends true;
APT::Install-Suggests 0;
APT::Authentication ;
APT::Authentication::TrustCDROM true;
APT::NeverAutoRemove ;
APT::NeverAutoRemove:: ^firmware-linux.*;
APT::NeverAutoRemove:: ^linux-firmware$;
APT::NeverAutoRemove:: ^linux-image.*;
APT::NeverAutoRemove:: ^kfreebsd-image.*;
APT::NeverAutoRemove:: ^linux-restricted-modules.*;
APT::NeverAutoRemove:: ^linux-ubuntu-modules-.*;
APT::NeverAutoRemove:: ^gnumach$;
APT::NeverAutoRemove:: ^gnumach-image.*;
APT::Never-MarkAuto-Sections ;
APT::Never-MarkAuto-Sections:: metapackages;
APT::Never-MarkAuto-Sections:: restricted/metapackages;
APT::Never-MarkAuto-Sections:: universe/metapackages;
APT::Never-MarkAuto-Sections:: multiverse/metapackages;
APT::Never-MarkAuto-Sections:: oldlibs;
APT::Never-MarkAuto-Sections:: restricted/oldlibs;
APT::Never-MarkAuto-Sections:: universe/oldlibs;
APT::Never-MarkAuto-Sections:: multiverse/oldlibs;
APT::Periodic ;
APT::Periodic::Download-Upgradeable-Packages 0;
APT::Periodic::Unattended-Upgrade 0;
APT::Periodic::AutocleanInterval 0;
APT::Periodic::Update-Package-Lists 0;
APT::Update ;
APT::Update::Post-Invoke-Success ;
APT::Update::Post-Invoke-Success:: [ ! -f /var/run/dbus/system_bus_socket ] ||
/usr/bin/dbus-send --system --dest=org.debian.apt --type=signal /org/debian/apt
org.debian.apt.CacheChanged || true;
APT::Update::Post-Invoke-Success:: /usr/bin/test -e
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service
/usr/bin/test -S /var/run/dbus/system_bus_socket /usr/bin/gdbus call
--system --dest org.freedesktop.PackageKit --object-path
/org/freedesktop/PackageKit --timeout 1 --method
org.freedesktop.PackageKit.StateHasChanged cache-update /dev/null; /bin/echo
/dev/null;
APT::Architectures ;
APT::Architectures:: amd64;
APT::Architectures:: i386;
APT::Compressor ;
APT::Compressor::. ;
APT::Compressor::.::Name .;
APT::Compressor::.::Extension ;
APT::Compressor::.::Binary ;
APT::Compressor::.::Cost 1;
APT::Compressor::gzip ;
APT::Compressor::gzip::Name gzip;
APT::Compressor::gzip::Extension .gz;
APT::Compressor::gzip::Binary gzip;
APT::Compressor::gzip::Cost 2;
APT::Compressor::gzip::CompressArg ;
APT::Compressor::gzip::CompressArg:: -9n;
APT::Compressor::gzip::UncompressArg ;
APT::Compressor::gzip::UncompressArg:: -d;
APT::Compressor::bzip2 ;
APT::Compressor::bzip2::Name bzip2;
APT::Compressor::bzip2::Extension .bz2;
APT::Compressor::bzip2::Binary bzip2;
APT::Compressor::bzip2::Cost 3;
APT::Compressor::bzip2::CompressArg ;
APT::Compressor::bzip2::CompressArg:: -9;
APT::Compressor::bzip2::UncompressArg ;
APT::Compressor::bzip2::UncompressArg:: -d;
APT::Compressor::xz ;
APT::Compressor::xz::Name xz;
APT::Compressor::xz::Extension .xz;
APT::Compressor::xz::Binary xz;
APT::Compressor::xz::Cost 4;
APT::Compressor::xz::CompressArg ;
APT::Compressor::xz::CompressArg:: -6;
APT::Compressor::xz::UncompressArg ;
APT::Compressor::xz::UncompressArg:: -d;
APT::Compressor::lzma ;
APT::Compressor::lzma::Name lzma;
APT::Compressor::lzma::Extension .lzma;
APT::Compressor::lzma::Binary xz;
APT::Compressor::lzma::Cost 5;
APT::Compressor::lzma::CompressArg ;
APT::Compressor::lzma::CompressArg:: --format=lzma;
APT::Compressor::lzma::CompressArg:: -9;
APT::Compressor::lzma::UncompressArg ;
APT::Compressor::lzma::UncompressArg:: --format=lzma;
APT::Compressor::lzma::UncompressArg:: -d;
APT::CompressorName ;
APT::CompressorExtension .;
APT::CompressorBinary ;
APT::CompressorCost 100;
APT::CompressorCompressArg ;
APT::CompressorCompressArg:: -9;
APT::CompressorUncompressArg ;
APT::CompressorUncompressArg:: -d;
Dir /;
Dir::State var/lib/apt/;
Dir::State::lists lists/;
Dir::State::cdroms cdroms.list;
Dir::State::mirrors mirrors/;
Dir::State::extended_states extended_states;
Dir::State::status /var/lib/dpkg/status;
Dir::Cache var/cache/apt/;
Dir::Cache::archives archives/;
Dir::Cache::srcpkgcache srcpkgcache.bin;
Dir::Cache::pkgcache pkgcache.bin;
Dir::Etc etc/apt/;
Dir::Etc::sourcelist sources.list;
Dir::Etc::sourceparts sources.list.d;
Dir::Etc::vendorlist vendors.list;
Dir::Etc::vendorparts vendors.list.d;
Dir::Etc::main apt.conf;
Dir::Etc::netrc auth.conf;
Dir::Etc::parts apt.conf.d;
Dir::Etc::preferences preferences;
Dir::Etc::preferencesparts preferences.d;
Dir::Etc::trusted trusted.gpg;
Dir::Etc::trustedparts trusted.gpg.d;
Dir::Bin ;
Dir::Bin::methods /usr/lib/apt/methods;
Dir::Bin::solvers
Bug#681422: libcatalyst-perl: breaks libtest-www-mechanize-catalyst-perl
Package: libcatalyst-perl Version: 5.90014-1 Severity: important See #680826. Fixed in 5.90015 (not uploaded yet). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654958: debian-policy: Document VCS fields.
Jonathan Nieder jrnie...@gmail.com writes: Thanks again for your help. I've applied all suggested changes. Interdiff and updated patch attached. Looks good to me -- seconded. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681003: Please, read this
Quoting SM Baby Siabef (siabef.deb...@gmail.com): Don't take the POT file of the previous mail. It has one esthetic mistake. Take the POT file of that mail. This file has encoding problems. Could you gzip it *then* send it again to 681...@bugs.debian.org? signature.asc Description: Digital signature
Bug#681418: debugfs is a big security hole
On 13.07.2012 05:37, Ben Hutchings wrote: Package: src:linux Version: 3.2.21-3 Severity: important Tags: security As discussed here http://lists.linux-foundation.org/pipermail/ksummit-2012-discuss/2012-July/000891.html. I certainly consider mounting of debugfs to be significant security liability. I'm not at all happy that people use it as the basis for end-user applications that quietly mount debugfs if they find it isn't yet mounted. Even if their corner of debugfs is robust, all the other stuff exposed by random drivers may not be. Debian has at least one such application package (blktrace) which mounts debugfs from its init script. systemd might be affected too, so I'm bringing Tollef into the loop here. When having booted with systemd I get: debugfs on /sys/kernel/debug type debugfs (rw,relatime) Tollef, do you know why systemd mounts debugfs by default? Is there something that should be done in the systemd package? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#681423: libcatalyst-perl: breaks Catalyst-Plugin-StackTrace
Package: libcatalyst-perl Version: 5.90014-1 Severity: important Catalyst-Plugin-StackTrace is shipped by libcatalyst-modules-perl. See https://rt.cpan.org/Public/Bug/Display.html?id=76179#txn-1094083. Fixed by libcatalyst-perl 5.90015 (not uploaded yet). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681424: libpam-ldap: multiarch causes pam_ldap to be added to pam setup
Package: libpam-ldap Version: 184-8.6 Severity: important User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch On a multiarch system ia32-libs-i386 pulls in a lot of i386 architecture libraries, including libpam-ldap:i386 Installing libpam-ldap:i386 on an amd64 system edits the /etc/pam.d/ files to include pam_ldap.so However, cron, ssh, etc are all amd64 binaries, so your logs fill up saying they cannot find the library; which is fair enough because there is no amd64 libpam-ldap installed on this system. Jul 13 10:29:01 elmo CRON[1788]: PAM unable to dlopen(pam_ldap.so): /lib/security/pam_ldap.so: cannot open shared object file: No such file or directory Jul 13 10:29:01 elmo CRON[1788]: PAM adding faulty module: pam_ldap.so The fault is that libpam-ldap:i386 should check what architecture it is running on and not update /etc/pam.d/* if it is not its own architecture; I think anyhow. - Craig -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (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/dash Versions of packages libpam-ldap depends on: ii debconf [debconf-2.0] 1.5.45 ii libc6 2.13-34 ii libldap-2.4-2 2.4.31-1 ii libpam-runtime 1.1.3-7.1 ii libpam0g 1.1.3-7.1 libpam-ldap recommends no packages. Versions of packages libpam-ldap suggests: ii libnss-ldap 264-2.3 -- debconf information excluded -- debsums errors found: debsums: package libpam-ldap is not installed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681425: libcatalyst-perl: breaks Catalyst-Plugin-Session-State-Cookie
Package: libcatalyst-perl Version: 5.90010-1 Severity: important See #665222. This is fixed by libcatalyst-perl 5.90015-1 (not uploaded yet). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681426: syslinux-themes-debian-wheezy: extlinux/theme.cfg refers to debian-squeeze files
Package: syslinux-themes-debian-wheezy Version: 11-1 Severity: critical Justification: breaks the whole system /usr/share/syslinux/themes/debian-wheezy/extlinux/theme.cfg contains: include themes/debian-squeeze/menu.cfg default themes/debian-squeeze/vesamenu.c32 prompt 0 timeout 50 (i.e. refers to debian-squeeze instead of debian-wheezy) After installing on a system using extlinux to boot, with EXTLINUX_THEME=debian (or debian-wheezy) in /etc/default/extlinux, the system is now unbootable (unable to load image themes/debian-squeeze/vesamenu.c32) Changing debian-squeeze to debian-wheezy fixes the problem (although just referring to the debian symlink might be a more robust solution). -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages syslinux-themes-debian-wheezy depends on: ii memtest86+ 4.20-1.1 ii syslinux-common 2:4.05+dfsg-6 syslinux-themes-debian-wheezy recommends no packages. syslinux-themes-debian-wheezy 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#675971: Bug #675971 -- wontfix?
Marking this bug as fixed is incorrect for this case because the issue remains, and will mean that when someone else finds the bug they will reopen it -- which is the correct thing for them to do. If this the remaining parts of this bug are not considered bugs, or if the intention is not to fix these bugs because they were created by a necessary design choice (of removing CELT), then I think the right thing to do is to give a reasonable explanation that a potential bug reporter can understand, and to mark the bug wontfix. That way when others run into the problem and find the bug report, they'll learn that the package has this issue by design. If the bug is marked fixed rather than wontfix then I intend to reopen it, by the same reasoning. Thanks. -- 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#681377: (Fwd) Re: Bug#681377: unblock: libpdfbox-java/1:1.7.0+dfsg-2
- Forwarded message from Niels Thykier ni...@thykier.net - From: Niels Thykier ni...@thykier.net To: gregor herrmann gre...@debian.org, 681...@bugs.debian.org Subject: Re: Bug#681377: unblock: libpdfbox-java/1:1.7.0+dfsg-2 Date: Thu, 12 Jul 2012 21:31:24 +0200 On 2012-07-12 20:24, gregor herrmann wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libpdfbox-java. -2 fixes the (at least) important bug #680778, the only change is is an added dependency. Full debdiff attached. unblock libpdfbox-java/1:1.7.0+dfsg-2 Thanks in advance, gregor I notice it does not add a class-path change in the Jar file; is this class-path entry already present? According to the reporter, he also added a class-path for it to work. ~Niels Hello Niels, Mea culpa (again). I misled Gregor regarding whether the classpath warning should be addressed for this upload. I have prepared an update for the package - debdiff attached - but not yet uploaded. Gregor, I have pushed this commit into the packaging repo, but wanted to hold off on the upload until you had a chance to take a look at it [1]. Cheers, tony [1] http://anonscm.debian.org/gitweb/?p=pkg-java/libpdfbox-java.git;a=commitdiff;h=c64e01bf82430d2b0a9b8eb6d17d6c703c652c81 diff -Nru libpdfbox-java-1.7.0+dfsg/debian/changelog libpdfbox-java-1.7.0+dfsg/debian/changelog --- libpdfbox-java-1.7.0+dfsg/debian/changelog 2012-07-12 18:23:43.0 + +++ libpdfbox-java-1.7.0+dfsg/debian/changelog 2012-07-13 04:18:35.0 + @@ -1,3 +1,10 @@ +libpdfbox-java (1:1.7.0+dfsg-3) unstable; urgency=low + + * debian/libpdfbox-java.classpath: add libfontbox-java to manifest + * debian/control: add javahelper to build-depends + + -- tony mancill tmanc...@debian.org Thu, 12 Jul 2012 19:27:17 -0700 + libpdfbox-java (1:1.7.0+dfsg-2) unstable; urgency=low * debian/control: add dependency on libfontbox-java to libpdfbox-java. diff -Nru libpdfbox-java-1.7.0+dfsg/debian/control libpdfbox-java-1.7.0+dfsg/debian/control --- libpdfbox-java-1.7.0+dfsg/debian/control2012-07-12 18:23:43.0 + +++ libpdfbox-java-1.7.0+dfsg/debian/control2012-07-13 04:18:35.0 + @@ -22,7 +22,8 @@ libcommons-beanutils-java, libcommons-logging-java, libicu4j-java, - liblucene2-java + liblucene2-java, + javahelper Standards-Version: 3.9.3 Homepage: http://pdfbox.apache.org/ Vcs-Git: git://git.debian.org/git/pkg-java/libpdfbox-java.git diff -Nru libpdfbox-java-1.7.0+dfsg/debian/libpdfbox-java.classpath libpdfbox-java-1.7.0+dfsg/debian/libpdfbox-java.classpath --- libpdfbox-java-1.7.0+dfsg/debian/libpdfbox-java.classpath 1970-01-01 00:00:00.0 + +++ libpdfbox-java-1.7.0+dfsg/debian/libpdfbox-java.classpath 2012-07-13 04:18:35.0 + @@ -0,0 +1 @@ +usr/share/java/pdfbox.jar /usr/share/java/fontbox.jar diff -Nru libpdfbox-java-1.7.0+dfsg/debian/rules libpdfbox-java-1.7.0+dfsg/debian/rules --- libpdfbox-java-1.7.0+dfsg/debian/rules 2012-07-12 18:23:43.0 + +++ libpdfbox-java-1.7.0+dfsg/debian/rules 2012-07-13 04:18:35.0 + @@ -29,6 +29,10 @@ dh_auto_build -- -buildfile pdfbox/build.xml pdfbox.package fontbox.package jempbox.package pdfbox.javadoc fontbox.javadoc jempbox.javadoc +override_dh_link: + dh_link -O--buildsystem=ant + jh_classpath + override_dh_installchangelogs: dh_installchangelogs $(CURDIR)/RELEASE-NOTES.txt signature.asc Description: OpenPGP digital signature
Bug#627174: sd
I've raised #627174 to request this package's removal. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680537: [PATCH] debian: Do not change iptables rules by default.
Debian kernel maintainer Bastian Blank writes, at
http://bugs.debian.org/680537:
The netfilter rules are a shared resource. There is no synchronization,
so the admin have the last word. As kernel maintainer, I see it similar
to a configuration file, so §10.7 policy applies.
The purpose of openvswitch is to provide support for switching, not to
setup filter rules. This means it violates the principle of least
surprise.
I believe that the argument by analogy to configuration files is weak,
given that the Debian policy section in question is very specifically about
files, not about general principles. On the other hand, Debian does not
install any firewall by default, so the presence of a rule that blocks GRE
traffic is a sign that the administrator has taken an explicit action to
install a firewall that blocks GRE, and therefore it is rather rude to
override this. Therefore, this patch simply turns off this behavior on
Debian, given that in ordinary Debian installations it will have no
adverse effect on Open vSwitch.
Debian bug #680537.
CC: 680...@bugs.debian.org
Reported-by: Bastian Blank wa...@debian.org
Signed-off-by: Ben Pfaff b...@nicira.com
---
debian/openvswitch-switch.init |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/debian/openvswitch-switch.init b/debian/openvswitch-switch.init
index 3c93720..f650f87 100755
--- a/debian/openvswitch-switch.init
+++ b/debian/openvswitch-switch.init
@@ -72,8 +72,6 @@ start () {
fi
set $@ $OVS_CTL_OPTS
$@ || exit $?
-
-ovs_ctl --protocol=gre enable-protocol
}
stop () {
--
1.7.2.5
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680537: [ovs-dev] [PATCH] debian: Do not change iptables rules by default.
On Fri, Jul 13, 2012 at 01:46:39PM +0900, Simon Horman wrote: On Thu, Jul 12, 2012 at 09:17:11PM -0700, Ben Pfaff wrote: Debian kernel maintainer Bastian Blank writes, at http://bugs.debian.org/680537: The netfilter rules are a shared resource. There is no synchronization, so the admin have the last word. As kernel maintainer, I see it similar to a configuration file, so §10.7 policy applies. The purpose of openvswitch is to provide support for switching, not to setup filter rules. This means it violates the principle of least surprise. I believe that the argument by analogy to configuration files is weak, given that the Debian policy section in question is very specifically about files, not about general principles. On the other hand, Debian does not install any firewall by default, so the presence of a rule that blocks GRE traffic is a sign that the administrator has taken an explicit action to install a firewall that blocks GRE, and therefore it is rather rude to override this. Therefore, this patch simply turns off this behavior on Debian, given that in ordinary Debian installations it will have no adverse effect on Open vSwitch. FWIW, I am in complete agreement with Ben on this. Want to give me an Acked-by? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648451: ITP: thrift-compiler -- software framework for cross-language services development (compiler)
[ Eric Evans ] Package: wnpp Severity: wishlist Owner: Eric Evans eev...@debian.org * Package name: thrift-compiler Version : 0.7.0 Upstream Author : Apache Software Foundation d...@thrift.apache.org * URL : http://thrift.apache.org * License : Apache License 2.0 Programming Lang: Python Description : software framework for cross-language services development (compiler) Thrift is a development framework for serialization of structured data, and the construction of RPC services. It combines a software stack with a code generation engine to build services that operate seamlessly across a number of different development languages. This package contains the compiler needed to generate code from a Thrift services specification. The description is mostly copy-and-paste from the website and will need some work, (suggestions welcome). Note: This ITP (and others) will replace #524135 For the most part this is complete; An upload to NEW can be expected within the week. Review and/or testing in the meantime would be greatly appreciated. http://anonscm.debian.org/gitweb/?p=users/eevans/thrift-compiler.git;a=summary http://anonscm.debian.org/gitweb/?p=collab-maint/thrift-repackage.git;a=summary Thanks, -- Eric Evans eev...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681429: bsd-mailx: include manual.txt
Package: bsd-mailx Version: 8.1.2-0.2006cvs-1 Severity: wishlist It'd be good if the USD.doc manual.txt Mail Reference Manual from the sources was built and included in the package. I believe it was in the package in the past and it's a bit easier introduction than the man page. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages bsd-mailx depends on: ii base-files 6.5 ii exim4-daemon-light [mail-transport-agent] 4.72-3+b1 ii libbsd00.3.0-2 ii libc6 2.13-10 ii liblockfile1 1.09-3 bsd-mailx recommends no packages. bsd-mailx 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#681261: live-build: please don't leave an empty fstab in chroot
After the short irc talk (it was a bit late), I have to believe that you did not had the time to drop an eye in the link [1] in the first post in this bug report. On Thu, Jul 12, 2012 at 11:12:04PM +0200, Daniel Baumann wrote: On 07/12/2012 07:55 PM, Rui Bernardo wrote: That would be good. Maybe live-build should also use fstab.d instead of overwriting what partman wrote with an empty one by default. again, live-build does not touch fstab, except making sure that there is no fstab at all in the live image. I'm very sorry but I have to disagree. The commit message [2] says another thing. You really must be overlooking this issue. Look: When removing fstab for live-installer also touch an empty file for it to avoid other packages failing on non-existing fstab. So, some other package(s) needs to deal with fstab absence. And the line: touch chroot/etc/fstab in lb_chroot_hacks clearly creates an empty fstab. It _is_ this empty fstab that breaks live-installer, and by consequence, debian-installer. FTR: For live-installer, that will extract the squashfs content to disk upon disk install _after_ partman created fstab with the user choices or preseed, it is the _absence_ of fstab inside the squashed chroot that makes partman setup in fstab work in live-installer, including swap and encryption, because the last is not overwriten by the tar extraction. If a live-build user wants an empty (or not) fstab he/she can add it in the includes.chroot, even using fstab.d, but live-build forcing an empty fstab if the user don't include one is a problem. right, customizations should be done through fstab.d via local includes only, and never through fstab. hence the latter should be always empty/not-used, and that's why live-build enforces that, sort-of. Yes, but not with an empty file. live-build should only make sure that, if a fstab is _not_ in the user includes, then no fstab should be left in the chroot, not even an empty one, like live-build always did and live-installer always expected. If partman should create another file other that /etc/fstab is another -valid- issue for me. But the thing is that, using this principle, it would imply for coerence, that sources.list also should not be created and instead a file inside sources.list.d/ should be created by d-i's apt-setup, as it is done by several other packages and live-build inside apt.conf.d/ and apt.preferences.d/. At this point, with d-i near beta, it will be hard to implement that without some (natural) resistence from other people. For coerence, the same also could/should be done with bash.bashrc (like it's done with profile.d/) and others (/etc/hosts.d/?). That would greatly improve the customization of the system without having to edit the main file during upgrades and all, and just drop a file in the *.d/ directory and maintain it (the file) separated from other packages and users always unpredictable edits/aditions/removals/truncates. Sorry for taking your scarce spare time with this issue and insist on this. Maybe I should have made this more clear from the start. Peace. [1] http://lists.debian.org/debian-live/2012/06/msg00041.html [2] http://live.debian.net/gitweb?p=live-build.git;a=commit;h=f3f9ad8bdec8df12bf20ae542c92ebfe75b1a86e -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681421: apt: Acquire::http { proxy } should be made location-aware
On 13 July 2012 07:22, Felicitus felici...@felicitus.org wrote:
I'm using a proxy configuration for my notebook:
Acquire::http { Proxy http://ip:3142; };
However, when I switch locations (like from home to hackerspace or to work), I
need to uncomment/change that line depending on whatever location I'm at.
It would be nice if this could be automated
Hello
You can place network-specific configurations in /etc/apt/apt.conf.d
and use scripts to enable them as appropriate. For example, I have
similar proxy settings in 99eth0-home and use this script
--- /usr/local/sbin/toggle-apt-conf
#!/bin/sh
set -e
base=/etc/apt/apt.conf.d/$2
case $1 in
enable) [ -f $base.disabled ] mv $base.disabled $base ;;
disable) [ -f $base ] mv $base $base.disabled ;;
esac
---
with these network settings
--- /etc/network/interfaces
…
iface eth0-home inet static
address 192.168.1.3
netmask 255.255.255.0
up toggle-apt-conf enable 99eth0-home
down toggle-apt-conf disable 99eth0-home
---
to enable the proxy automatically when I connect to my home network.
This is also possible to do using network manager, though the
configuration is obviously different.
Regards
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681187: supercollider-emacs: unowned files after purge (policy 6.8, 10.8)
2012/7/11 Andreas Beckmann deb...@abeckmann.de: Package: supercollider-emacs Version: 1:3.5.3~repack-1 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 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 1m24.2s ERROR: FAIL: Package purging left files on system: /usr/share/emacs23/site-lisp/ owned by: emacs23-common /usr/share/emacs23/site-lisp/SuperCollider/not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-browser.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-dev.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-document.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-help.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-interp.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-keys.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-language.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-menu.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-minor-mode.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-mode.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-server.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-util.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-vars.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang-widgets.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/sclang.elc not owned /usr/share/emacs23/site-lisp/SuperCollider/tree-widget.elc not owned Hi - Thanks for the report. I believe this is fixed with a patch in git [1], should be fixed in next release Dan [1] http://anonscm.debian.org/gitweb/?p=pkg-multimedia/supercollider.git;a=commitdiff;h=d41f81edb4335b69b40bca9b9a6a96279de9de81 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681418: debugfs is a big security hole
]] Michael Biebl Tollef, do you know why systemd mounts debugfs by default? No, I don't. Just asked upstream. Is there something that should be done in the systemd package? If it's a bad idea to mount it by default, we shouldn't, I think. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681431: ifupdown: Doesn't pass the tests on x64 system
Package: ifupdown Version: 0.7 Severity: grave Tags: upstream Justification: renders package unusable Hi, I've tried to compile the ifupdown 0.7.2 (revision bbb51c127dcf) on a x64 system (tested on 2 separated systems) and it ends with error in test. On x32 system works smooth. The output is: sed -e '/^##ADDRESSFAM##$/r inet.man' -e '/^##ADDRESSFAM##$/r ipx.man' -e '/^##ADDRESSFAM##$/r inet6.man' -e '/^##ADDRESSFAM##$/r can.man' \ -e '/^##ADDRESSFAM##$/d' interfaces.5.pre interfaces.5 rm link.c ipx.c can.c meta.c inet6.c inet.c make[1]: Leaving directory `/root/devel/ifupdown/ifupdown-ifupdown- bbb51c127dcf' debian/rules override_dh_auto_test make[1]: Entering directory `/root/devel/ifupdown/ifupdown-ifupdown- bbb51c127dcf' chmod a+rx debian/testbuild running debian/testbuild Testcase 1: -a (okay) == Testcase 2: -a (okay) == Testcase 3: -a (okay) == Testcase 4: eth0=work (okay) == Testcase 5: -a (okay) == Testcase 6: -a (okay) == Testcase 7: -a (okay) == Testcase 8: -a --- tests/up.8 2012-07-13 02:28:06.952423223 +0300 +++ tests/up-res.8 2012-07-13 02:28:07.216424533 +0300 @@ -20,14 +20,14 @@ if test -d /sys/class/net/eth2 -a ! -d /sys/class/net/eth2.2 ; then ip link set up dev eth2; ip link add link eth2 name eth2.2 type vlan id 2; fi Configuring interface eth2.2=eth2.2 (inet) run-parts --verbose /etc/network/if-pre-up.d -ip addr add 2.3.4.5/255.255.255.0 broadcast 2.3.4.255dev eth2.2 label eth2.2 +ip addr add 2.3.4.5/255.255.255.0 broadcast +dev eth2.2 label eth2.2 ip link set dev eth2.2 up run-parts --verbose /etc/network/if-up.d if test -d /sys/class/net/eth2 -a ! -d /sys/class/net/eth2.2 ; then ip link set up dev eth2; ip link add link eth2 name eth2.2 type vlan id 2; fi Configuring interface eth2.2:3=eth2.2:3 (inet) run-parts --verbose /etc/network/if-pre-up.d -ip addr add 3.4.5.6/255.255.254.0 broadcast 3.4.5.255dev eth2.2:3 label eth2.2:3 +ip addr add 3.4.5.6/255.255.254.0 broadcast +dev eth2.2:3 label eth2.2:3 ip link set dev eth2.2:3 up run-parts --verbose /etc/network/if-up.d (failed) == Testcase 9: tunnel -o local=2.3.4.5 (okay) == (failed overall) == AUTOMATIC TESTS FAILED -- Something built wrong or there is a bug in the code!!! Either way something is completely screwed up!!! File a bug! Aborting build. == make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory `/root/devel/ifupdown/ifupdown-ifupdown- bbb51c127dcf' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ifupdown depends on: ii dpkg 1.16.4.3 ii initscripts 2.88dsf-22.1 ii iproute 20120521-3 ii libc62.13-33 ii lsb-base 4.1+Debian7 ifupdown recommends no packages. Versions of packages ifupdown suggests: ii isc-dhcp-client [dhcp-client] 4.2.2.dfsg.1-5 ii net-tools 1.60-24.1 pn pppnone pn rdnssd none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672030: backtrace
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Program received signal SIGSEGV, Segmentation fault. 0x7fff0005 in ?? () (gdb) bt #0 0x7fff0005 in ?? () #1 0x770d891e in g_type_class_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #2 0x004047c2 in printInterface (iface=..., parent=...) at bseprocidl.cc:343 #3 0x00404a24 in printInterface (iface=..., parent=...) at bseprocidl.cc:360 #4 0x00404a24 in printInterface (iface=..., parent=...) at bseprocidl.cc:360 #5 0x00401e93 in main (argc=6922240, argv=0x770bf190) at bseprocidl.cc:446 #2 0x004047c2 in printInterface (iface=..., parent=...) at bseprocidl.cc:343 343 GObjectClass *klass = (GObjectClass *)g_type_class_ref (type_id); (gdb) p type_id $1 = 6387824 (gdb) p iface.c_str() $2 = 0x68a038 BseStandardOsc HTH. Will try and have another look at this later. - -- Neil Williams = http://www.linux.codehelp.co.uk/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk//U2EACgkQiAEJSii8s+NhVQCgvJjdOITpnPkPlGR/IenDYqF+ 7iQAn0pCZkptNia9wea1S0nPMedTCvOF =r6r/ -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#479767: Icedove Bug
Hello Jason, that's not a big help, unfortunately. :/ So there is no good statement for the behavior of your reported bug with the actual versions I would prefer to close this bug. The main reason for this is the big differences between your reported version and the current versions. The improvment in the last years for the stability on thunderbird/icedove is become better and better. If you have really trouble with this please open a new bug which is much more related to a current version. Regards Carsten On Thu, Jul 12, 2012 at 02:40:10PM +0200, Jason Love wrote: I eventually moved to windows thunderbird so not sure. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681166: [bugs.debian.org] Replies to a ticket closure addressed to the ticket rather than to the closer
On 2012-07-12 12:53, Don Armstrong wrote: On Tue, 10 Jul 2012, Filipus Klutiero wrote: Notifications of ticket closures instruct: It has been closed by Foo. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Foo by replying to this email. But replying to that email actually replies to the ticket (x...@bugs.debian.org), not to the closer. Indeed, Reply-To is set to x...@bugs.debian.org. The right place to do so is by a mail to n...@bugs.debian.org, not Foo. Sorry? Are you saying the right way to contact Foo is to send a mail to the ticket, not to Foo, or what? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680825: [Debichem-devel] Bug#680825: gromacs: FTBFS: mv: cannot stat `/«PKGBUILDDIR»/debian/gromacs-mpich/usr/lib/*.so': No such file or directory
Hello, On Thursday 12 July 2012 20:47:59 Nicholas Breen wrote: On Wed, Jul 11, 2012 at 03:44:22PM -0400, Brad King wrote: This should fix it: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8720aa04 Ideally we should add a test for this case but I have no time now. We'll include the fix in the next 2.8.9 rc. Thank you very much for tracking down the bug. Modestas, do you think it's worth applying that patch to the cmake package and requesting a freeze exception from the RMs? The plan is to ship Wheezy with cmake 2.8.9 final. I have uploaded 2.8.9-rc1 this early in order to catch the auto-freeze-exception train and minimize diff. 2.8.9-rc1 - 2.8.9 will only contain bug fixes anyway. I'm not sure if it affects any other packages in the archive, but I cannot find any other outright failures in this batch of FTBFS bugs that date from after the 2.8.9-rc1 upload, so it might well be just this one case. Feel free to reassign/clone this bug to cmake. Otherwise I'll hash out a workaround for gromacs to keep it from getting removed as RC-buggy. I will upload 2.8.9-rc2 to unstable once its released (which should not take long). signature.asc Description: This is a digitally signed message part.
Bug#681432: elinks: Ctrl-I binding not working in main keymap
Package: elinks Version: 0.12~pre5-8 Severity: normal Dear Maintainer, Configuring Ctrl-I as a keybinding is not working in the main keymap. I tried in the console and with different terminal emulators (urxvt and xterm) without success. The Ctrl-I combination is working in other console apps like vim or mutt. Thanks! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (700, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages elinks depends on: ii elinks-data 0.12~pre5-8 ii libbz2-1.01.0.6-3 ii libc6 2.13-33 ii libcomerr21.42.4-3 ii libexpat1 2.1.0-1 ii libfsplib00.11-2 ii libgnutls26 2.12.20-1 ii libgpm2 1.20.4-6 ii libgssapi-krb5-2 1.10.1+dfsg-1 ii libidn11 1.25-2 ii libk5crypto3 1.10.1+dfsg-1 ii libkrb5-3 1.10.1+dfsg-1 ii liblua5.1-0 5.1.5-2 ii libperl5.14 5.14.2-12 ii libtre5 0.8.0-3 ii zlib1g1:1.2.7.dfsg-13 elinks recommends no packages. Versions of packages elinks suggests: pn elinks-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680939: Bug#681350: libconvert-asn1-perl: use strict breaks smbldap-tools
Hi Saulo
I'm Cc'in the bugreport on smbldap-tools, but I think these two should
be merged and only assigned to smbldap-tools.
On Thu, Jul 12, 2012 at 09:51:54PM -0300, Saulo Soares de Toledo wrote:
2012/7/12 Salvatore Bonaccorso car...@debian.org
Could you give more information on which problems you see with
smbldap-tools? Should the bugreport reassigned to smbldap-tools?
I've opened the bug report 680939 680...@bugs.debian.org to smbldap-tools.
Smbldap-tools is a set of perl scripts designed to manage user and
groupaccounts stored in an LDAP directory. (website description)
Some scripts of the package simple do not works with use sctrict enabled.
The Debian version is 0.9.7, but 0.9.8 (latest from developers) do not
works too. The error returned with smbldap-userlist is:
Can't use string (['username','uidNumber','uid']) as an ARRAY ref while
strict refs in use at /usr/share/perl5/Convert/ASN1/_encode.pm line 269.
Smbldap-tools is needed while using Samba + LDAP. I sent an email do
smbldap-tools developers about the problem and will update here when I get
some more information about.
I did not yet dig into it in detail, but this seems a a wrong use in
smbldap-userlist.pl. I see there, that first the $attrs is 'assembled'
as a string in ['username','uidNumber','uid' . ] (line 198). Then
it passes to a Net::LDAP object:
cut-cut-cut-cut-cut-cut-
my $mesg = $ldap_master-search ( base = $base,
scope = $config{scope},
filter = $filter,
attrs = $attrs
);
cut-cut-cut-cut-cut-cut-
In documentation of Net::LDAP you find the details to the search
options. In particular you see:
cut-cut-cut-cut-cut-cut-
=item attrs =Egt [ ATTR, ... ]
A list of attributes to be returned for each entry that matches the
search filter.
If not specified, then the server will return the attributes that are
specified as accessible by default given your bind credentials.
Certain additional attributes such as createTimestamp and other
operational attributes may also be available for the asking:
$mesg = $ldap-search( ... ,
attrs = ['createTimestamp']
);
To retrieve the default attributes and additional ones, use '*'.
$mesg = $ldap-search( ... ,
attrs = ['*', 'createTimestamp']
);
To retrieve no attributes (the server only returns the DNs of matching
entries), use '1.1':
$mesg = $ldap-search( ... ,
attrs = ['1.1']
);
cut-cut-cut-cut-cut-cut-
So smbldap-userlist.pl. passes a string, where is should be a list.
Btw, you can reproduce the error message easily by:
cut-cut-cut-cut-cut-cut-
#!/usr/bin/perl
use strict 'refs';
my $attrs = [ 'foo', 'bar', ];
push @{$attrs}, 'foobar';
use Data::Dumper 'Dumper';
warn Dumper [$attrs];
cut-cut-cut-cut-cut-cut-
You see, here if you remove the use strict 'refs' again, it does not
throw out the Can't use string ([ 'foo', 'bar', ]) as an ARRAY ref
while strict refs in use at testcase_broken.pl line 7..
Correctly it would be:
cut-cut-cut-cut-cut-cut-
#!/usr/bin/perl
use strict 'refs';
my $attrs = [ 'foo', 'bar', ];
push @{$attrs}, 'foobar';
use Data::Dumper 'Dumper';
warn Dumper [$attrs];
cut-cut-cut-cut-cut-cut-
Conclusion: I'm more convinced that is a real bug in smbldap-tools and
we surely should not remove the use strict; from
libconvert-asn1-perl.
Regards,
Salvatore
signature.asc
Description: Digital signature
Bug#657885: squeeze-backports
Will this get ported to squeeze-backports? Thanks, Rushi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680537: [ovs-dev] [PATCH] debian: Do not change iptables rules by default.
On Thu, Jul 12, 2012 at 09:17:11PM -0700, Ben Pfaff wrote:
Debian kernel maintainer Bastian Blank writes, at
http://bugs.debian.org/680537:
The netfilter rules are a shared resource. There is no synchronization,
so the admin have the last word. As kernel maintainer, I see it similar
to a configuration file, so §10.7 policy applies.
The purpose of openvswitch is to provide support for switching, not to
setup filter rules. This means it violates the principle of least
surprise.
I believe that the argument by analogy to configuration files is weak,
given that the Debian policy section in question is very specifically about
files, not about general principles. On the other hand, Debian does not
install any firewall by default, so the presence of a rule that blocks GRE
traffic is a sign that the administrator has taken an explicit action to
install a firewall that blocks GRE, and therefore it is rather rude to
override this. Therefore, this patch simply turns off this behavior on
Debian, given that in ordinary Debian installations it will have no
adverse effect on Open vSwitch.
FWIW, I am in complete agreement with Ben on this.
Debian bug #680537.
CC: 680...@bugs.debian.org
Reported-by: Bastian Blank wa...@debian.org
Signed-off-by: Ben Pfaff b...@nicira.com
---
debian/openvswitch-switch.init |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/debian/openvswitch-switch.init b/debian/openvswitch-switch.init
index 3c93720..f650f87 100755
--- a/debian/openvswitch-switch.init
+++ b/debian/openvswitch-switch.init
@@ -72,8 +72,6 @@ start () {
fi
set $@ $OVS_CTL_OPTS
$@ || exit $?
-
-ovs_ctl --protocol=gre enable-protocol
}
stop () {
--
1.7.2.5
___
dev mailing list
d...@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680537: [ovs-dev] [PATCH] debian: Do not change iptables rules by default.
On Thu, Jul 12, 2012 at 09:48:34PM -0700, Ben Pfaff wrote: On Fri, Jul 13, 2012 at 01:46:39PM +0900, Simon Horman wrote: On Thu, Jul 12, 2012 at 09:17:11PM -0700, Ben Pfaff wrote: Debian kernel maintainer Bastian Blank writes, at http://bugs.debian.org/680537: The netfilter rules are a shared resource. There is no synchronization, so the admin have the last word. As kernel maintainer, I see it similar to a configuration file, so §10.7 policy applies. The purpose of openvswitch is to provide support for switching, not to setup filter rules. This means it violates the principle of least surprise. I believe that the argument by analogy to configuration files is weak, given that the Debian policy section in question is very specifically about files, not about general principles. On the other hand, Debian does not install any firewall by default, so the presence of a rule that blocks GRE traffic is a sign that the administrator has taken an explicit action to install a firewall that blocks GRE, and therefore it is rather rude to override this. Therefore, this patch simply turns off this behavior on Debian, given that in ordinary Debian installations it will have no adverse effect on Open vSwitch. FWIW, I am in complete agreement with Ben on this. Want to give me an Acked-by? Acked-by: Simon Horman ho...@verge.net.au -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
