Bug#696624: linux-utils: System fails to boot if system date is corrected.
Package: util-linux Version: 2.20.1-5.3 Severity: important Hello. I recently noticed that one of my PC's system clock had drifted into the future. I corrected the system clock and then after the next shutdown/restart, the PC disappeared off the network. I went over and hooked a display up to it and got this: http://imgur.com/PmH6P Somehow it's interpreting a regular system clock change as a filesystem error that needs an administrator password to fix. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages util-linux depends on: ii debconf [debconf-2.0] 1.5.48 ii dpkg 1.16.9 ii initscripts2.88dsf-34 ii install-info 4.13a.dfsg.1-10 ii libblkid1 2.20.1-5.3 ii libc6 2.13-37 ii libncurses55.9-10 ii libselinux12.1.9-5 ii libslang2 2.2.4-15 ii libtinfo5 5.9-10 ii libuuid1 2.20.1-5.3 ii lsb-base 4.1+Debian8 ii tzdata 2012j-1 ii zlib1g 1:1.2.7.dfsg-13 util-linux recommends no packages. Versions of packages util-linux suggests: ii dosfstools 3.0.13-1 ii kbd 1.15.3-9 pn util-linux-locales none -- debconf information: util-linux/noauto-with-nonzero-passnum: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696625: EXDEV not catched properly
Package: autopkgtest Version: 2.2.3 Severity: normal adt-run: trace: ** init adt-run: trace: ** start adt-run: trace: $ vserver: adt-virt-null adt-run: trace: starting adt-run: trace: ** open, scratch=None adt-run: trace: ** cmdl = ['sh', '-c', 'exec $@', 'x'] adt-run: trace: * initialising adt-run: trace: * no key generation needed adt-run: trace: * reset adt-run: trace: builds ... adt-run: trace: deb deb0 adt-run: trace: * register what=deb0 deb_forbuilds=auto pkg=pgbouncer af=deb0-deb~pgbouncer_1.5.4-1_amd64.deb:pgbouncer_1.5.4-1_amd64.deb!|- adt-run: unexpected, exceptional, error: Traceback (most recent call last): File /usr/bin/adt-run, line 1883, in main process_actions() File /usr/bin/adt-run, line 1823, in process_actions 'forbuilds',testbed.blamed) File /usr/bin/adt-run, line 1486, in register shutil.copy(af.read(), dest) File /usr/lib/python2.7/shutil.py, line 117, in copy if os.path.isdir(dst): File /usr/lib/python2.7/genericpath.py, line 41, in isdir st = os.stat(s) TypeError: coercing to Unicode: need string or buffer, instance found adt-run: trace: ** stop adt-run: trace: ** close, scratch=tb-scratch~/tmp/tmp.WCCrAUmben:-/|/tmp/tmp.WCCrAUmben/! This patch fixes the issue: --- adt-run.orig2012-12-24 09:07:54.0 +0100 +++ adt-run 2012-12-24 09:07:57.0 +0100 @@ -1482,7 +1482,7 @@ try: os.link(af.read(), dest.write()) except (IOError,OSError), oe: if oe.errno != errno.EXDEV: raise e - shutil.copy(af.read(), dest) + shutil.copy(af.read(), dest.write()) if act.ah['deb_'+forwhat] == 'install': b.install.append(pkg) PS: git://git.debian.org/git/autopkgtest/autopkgtest.git (from the Vcs header) seems pretty out of date Christoph -- c...@df7cb.de | http://www.df7cb.de/ signature.asc Description: Digital signature
Bug#693025: xmobar: unable to read CoreTemp and BatteryP is blank on ThinkPad
Hi, On 23 December 2012 22:31, frozencemetery rharw...@club.cc.cmu.edu wrote: Package: xmobar Version: 0.14-4 Followup-For: Bug #693025 Hello, When using BatteryP, xmobar is unable to detect my battery, and reports 0 for left constantly. As the original responder for this bug report did, I upgraded the version of xmobar to version 0.15 from cabal, and the battery appears to be detected with no problems. In message 20, Apollon Oikonomopoulos apoi...@gmail.com wrote: Most likely you need to use the -c parameter for BatteryP to point it to the correct file under /sys/class/power/BAT/, see the manpage for details and give it a try if you can. 0.15 does some autodiscovery and doesn't need the -c flag anymore. I'd very much like to do this. However, that directory does not exist on my system. The closest thing appears to be /sys/class/power_supply, where within the relevant battery subdirectory there are files energy_full, energy_full_design, and energy_now, which I believe -c is searching for. With 0.15, however, I don't even need to pass this flag. Yes, it is under /sys/class/power_supply (the manpage is wrong). Battery detection has changed significantly in 0.15, so no manual tuning is needed anymore. Unfortunately 0.15 depends on libghc-x11-dev 1.6.0, which didn't make it to unstable in time for wheezy, so I can't do much (except upload a version in experimental perhaps). Regards, Apollon
Bug#696540: fpc 2.6.0-7 was initiated and reviewed by debian-i18n
Hi RT, Just one note to make it perfectly clear, except for the typo change in d/copyright, all changes that went into fpc/2.6.0-7 are the result of a change initiated and reviewed by debian-i18n. Paul P.S. Abou mistook me for Peter Green, one of his regular sponsors of fpc, but I did the sponsoring this time. signature.asc Description: OpenPGP digital signature
Bug#696626: libapache2-mod-php5: infinite recursion in rfc1867_post_handler when trying to preview/commit a mediawiki edit
Package: libapache2-mod-php5 Version: 5.4.4-11 Severity: normal Dear Maintainer, After running apache for a while, previewing or commiting a mediawiki edit causes a child segfault: [notice] child pid 23263 exit signal Segmentation fault (11), possible coredump in /var/tmp/apache2-gdb-dump When analyzing the coredump, the backtrace is 87k+ calls deep. The bt looks like this: #1 0x7fbe62b3623b in ?? () from /usr/lib/apache2/modules/libphp5.so . 87k lines omitted :) #87241 0x7fbe62b3623b in ?? () from /usr/lib/apache2/modules/libphp5.so #87242 0x7fbe62b3623b in ?? () from /usr/lib/apache2/modules/libphp5.so #87243 0x7fbe62b3623b in ?? () from /usr/lib/apache2/modules/libphp5.so #87244 0x7fbe62b3623b in ?? () from /usr/lib/apache2/modules/libphp5.so #87245 0x7fbe62c3b014 in rfc1867_post_handler () from /usr/lib/apache2/modules/libphp5.so #87246 0x7fbe62c388f3 in sapi_handle_post () from /usr/lib/apache2/modules/libphp5.so #87247 0x7fbe62c3f9b8 in php_default_treat_data () from /usr/lib/apache2/modules/libphp5.so #87248 0x7fbe62af260d in mbstr_treat_data () from /usr/lib/apache2/modules/libphp5.so #87249 0x7fbe62c3e50c in ?? () from /usr/lib/apache2/modules/libphp5.so #87250 0x7fbe62c6dbab in ?? () from /usr/lib/apache2/modules/libphp5.so #87251 0x7fbe62c9eea5 in zend_hash_apply () from /usr/lib/apache2/modules/libphp5.so #87252 0x7fbe62c3fd1e in ?? () from /usr/lib/apache2/modules/libphp5.so #87253 0x7fbe62c30285 in php_request_startup () ---Type return to continue, or q return to quit--- from /usr/lib/apache2/modules/libphp5.so #87254 0x7fbe62d3b23b in ?? () from /usr/lib/apache2/modules/libphp5.so #87255 0x7fbe6733db50 in ap_run_handler (r=0x7fbe6171f0a0) at config.c:159 #87256 0x7fbe6733df9b in ap_invoke_handler (r=r@entry=0x7fbe6171f0a0) at config.c:377 #87257 0x7fbe6734e078 in ap_process_request (r=r@entry=0x7fbe6171f0a0) at http_request.c:282 #87258 0x7fbe6734af38 in ap_process_http_connection (c=0x7fbe643ee290) at http_core.c:190 #87259 0x7fbe67344510 in ap_run_process_connection (c=0x7fbe643ee290) at connection.c:43 #87260 0x7fbe673448f8 in ap_process_connection (c=c@entry=0x7fbe643ee290, csd=optimized out) at connection.c:190 #87261 0x7fbe67352c2e in child_main (child_num_arg=child_num_arg@entry=31) at prefork.c:667 #87262 0x7fbe67353382 in make_child (slot=31, s=0x7fbe672ab818) at prefork.c:768 #87263 make_child (s=0x7fbe672ab818, slot=31) at prefork.c:696 #87264 0x7fbe67353ee6 in perform_idle_server_maintenance ( p=optimized out) at prefork.c:903 #87265 ap_mpm_run (_pconf=_pconf@entry=0x7fbe672ea028, plog=optimized out, s=s@entry=0x7fbe672ab818) at prefork.c:1107 #87266 0x7fbe67328826 in main (argc=3, argv=0x7fffa99edc68) at main.c:755 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35.4-rscloud (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libapache2-mod-php5 depends on: ii apache2-mpm-prefork 2.2.22-12 ii apache2.2-common 2.2.22-12 ii libbz2-1.0 1.0.6-4 ii libc62.13-37 ii libcomerr2 1.42.5-1 ii libdb5.1 5.1.29-5 ii libgssapi-krb5-2 1.10.1+dfsg-3 ii libk5crypto3 1.10.1+dfsg-3 ii libkrb5-31.10.1+dfsg-3 ii libmagic15.11-2 ii libonig2 5.9.1-1 ii libpcre3 1:8.31-1 ii libqdbm141.8.78-2 ii libssl1.0.0 1.0.1c-4 ii libstdc++6 4.7.2-4 ii libxml2 2.8.0+dfsg1-7 ii mime-support 3.52-2 ii php5-common 5.4.4-11 ii tzdata 2012j-1 ii ucf 3.0025+nmu3 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages libapache2-mod-php5 recommends: ii php5-cli 5.4.4-11 Versions of packages libapache2-mod-php5 suggests: ii php-pear 5.4.4-11 -- no debconf information Versions of mediawiki installed: ii mediawiki 1:1.19.3-1 ii mediawiki-extensions2.10 ii mediawiki-extensions-base 2.10 ii mediawiki-extensions-collection 2.10 ii mediawiki-extensions-confirmedit2.10 ii mediawiki-extensions-geshi 2.10 ii mediawiki-extensions-graphviz 2.10 ii mediawiki-extensions-ldapauth 2.10 ii mediawiki-extensions-math 2:1.0+git20120528-6 ii mediawiki-extensions-openid 2.10 ii mediawiki-math 2:1.0+git20120528-6 ii mediawiki-math-texvc2:1.0+git20120528-6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696626: (libapache2-mod-php5: infinite recursion in rfc1867_post_handler when trying to preview/commit a mediawiki edit)
After installing the debug symbols, i get #87243 0x7fbe62b3623b in php_session_rfc1867_callback (event=0, event_data=0x7fffa99ebeb0, extra=0x7fffa99ebda0) at /tmp/buildd/php5-5.4.4/ext/session/session.c:2388 #87244 0x7fbe62b3623b in php_session_rfc1867_callback (event=0, event_data=0x7fffa99ebeb0, extra=0x7fffa99ebda0) at /tmp/buildd/php5-5.4.4/ext/session/session.c:2388 #87245 0x7fbe62c3b014 in rfc1867_post_handler (content_type_dup=0x7fbe67f8eea8 \b, arg=0x7fbe68034730) at /tmp/buildd/php5-5.4.4/main/rfc1867.c:773 Probably a dup of bug #694473 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#658699: ITP: meandmyshadow -- A puzzle / platform game
Hi Thomas, I'm learning Debian packaging and as a training I'm currently packaging Me My Shadow. My package is almost ready to be released but I've just seen that you filled an ITP for this game. Since your ITP is 322 days old, I'd like to know if you're OK to let me release this package? Thanks in advance Yann -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696579: org-mode: TODOs with repeat are not sorted correctly(?) in the agenda view
Hi Josef, I've posted your issue on the org-mode mailing list; can you please follow this discussion up there ? http://thread.gmane.org/gmane.emacs.orgmode/63847 Cheers, --Seb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696157: release.debian.org: preapproval of grml-debootstrap/0.54
Hi, (Disclaimer: I'm neither part of the release team nor speaking on behalf of it.) Therefore I would like to seek preapproval of grml-debootstrap/0.54. Looks good to me. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634261: [sparc] iceweasel: Bus Error in setbuf()
Am Sonntag, den 23.12.2012, 00:13 +0100 schrieb John Paul Adrian Glaubitz: I don't completely follow, so I'll just ask: do you mean that this is a case of ABI misuse, with poor error reporting? One could phrase it this way. As far I understand the problem, the Mozilla developers provide a version script to the linker to control which symbols get exported. This helps speeding up the load process of the binary and reduces the memory footprint. This is correct. What the Mozilla developers didn't seem to put into account is that if you prevent the symbol _IO_stdin_used from being exported from your binary, parts of the ABI of the standard C library will change and it will behave like an older version which causes the unaligned access which results in a CPU trap. And this is mostly correct. libc puts lots of effort in providing a stable ABI. A big change in libc was the introduction of libio 2.1. It introduced support for wide-character streams and 64 bit offsets. These changes required an incompatible change to the FILE structure. Because of this, the FILE APIs exist in two variants in glibc[1], if backward compatibility is enabled. The new variant is tagged with the version GLIBC_2.1, while the old one is tagged GLIBC_2.0. For the three standard streams, there are two differently *named*, not just differently *versioned* objects, namely _IO_stdin_ for the old version and _IO_2_1_stdin_ for the new version, while the pointer stdin itself is not version dependent. This might be to make sure that stdin itself has the same value regardless of the version of libc that is imported. If a program compiled against the glibc 2.1 (or newer) development files, it will automatically refer to the new functions (i.e. link to the GLIBC_2.1 version of _IO_file_setbuf and so on), while programs and libraries compiled with old glibc 2.0 development files will refer to the GLIBC_2.0 version of these functions. The tricky part are the std* pointers: If a source file is compiled with new development headers and refers to stdin, stdout or stderr, some magic makes the compiler or linker emit a definition of the symbol _IO_stdin_used in that module. glibc itself defines it as a *weak* external symbol. The consequence is that if the symbol is not defined anywhere, it just resolves to address 0, but if it is defined in one or more modules, it resolves to a valid address in one of these modules. The resolution of external global variables in ELF systems is internally performed by a GOT lookup (which is the strange code for _IO_stdin_used observed on disassembling) at runtime. The logic in glibc is that if the new libio functions are used with stdin, there will be a reference to _IO_stdin_used. But if there are no references to _IO_stdin_used, the compatibility layer will kick in, and make the stdin/stdout/stderr pointers by pointers to the compatibility objects. As it happens, the compatibility objects do not contain any 64 bit field, and require a 4-byte-alignent on sparc, while the modern objects (which are in fact the compatibility objects with some extra fields appended) have a 64 bit field containing the current file offset. This makes gcc on sparc require an 8-byte-alignment. gcc compiles functions that work on the new FILE structure with the internal assumption that these objects are aligned as they should, so it expects 8-byte-alignment. The old functions on the other hand work fine with the new structures, stricter aligned, unless the code tries to access the vtable pointer, which is at different location in the old and new object, and most likely the cause to have both versions. It might have been the intention of the libio developers that (unless vtable accesses happen) the old objects can be processed by the new functions, and in that case, glibc is buggy, as it relies on undefined behaviour. Aussuming that intention, it expects that a pointer to the short file structure can be used as a pointer to the long file structure, which is not something you are granted by the C standard. Can you describe what iceweasel was doing wrong? Is this documented so future coders know not to make the same mistake? Is the version in squeeze affected? How about the version in wheezy? It seems to have been fixed in Firefox 10 which is part of Wheezy: There seems to be no official documentation on it, but hiding the _IO_stdin_used symbol (it still is there, but not visible for dynamic loading) violates internal glibc assumptions and breaks on sparc. Regards, Michael Karcher [1] This is why Bernhard R. Link observed the two different alignof values. You choose between the two variants of FILE/_IO_FILE by defining or not defining _IO_USE_OLD_IO_FILE. In oldstdfile.c, the symbol is defined, while in genops.c, it is not defined. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696627: Please provide notification-daemon-xfce also for sid and further versions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: notification-daemon-xfce Version: 0.3.7-2 Severity: normal notification-daemon-xfce is available in squeeze but not in testing or unstable anymore. However, it is the only working notification daemon and several tools need one. (Package notification-daemon is broken completely since several years but thats another story.) - -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (800, 'unstable'), (700, 'stable'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.6.0 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Shell: /bin/sh linked to /bin/dash Versions of packages notification-daemon-xfce depends on: ii libatk1.0-0 2.4.0-2 ii libc62.13-37 ii libcairo21.12.2-2 ii libdbus-1-3 1.6.8-1 ii libdbus-glib-1-2 0.100-1 ii libfontconfig1 2.9.0-7.1 ii libfreetype6 2.4.9-1 ii libglib2.0-0 2.33.12+really2.32.4-3 ii libgtk2.0-0 2.24.10-2 ii libnotify1 [libnotify1-gtk2.10] 0.5.0-2 ii libpango1.0-01.30.0-1 ii libsexy2 0.1.11-2+b1 ii libx11-6 2:1.5.0-1 ii libxfce4util44.8.2-1 ii libxfcegui4-44.8.1-5 ii libxml2 2.8.0+dfsg1-7 ii zlib1g 1:1.2.7.dfsg-13 notification-daemon-xfce recommends no packages. notification-daemon-xfce suggests no packages. - -- no debconf information - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQGcBAEBCgAGBQJQ2CEPAAoJEKZ8CrGAGfasI7IMAKk5tHRTY3Hg1r3wfl8c8kXR LKPvu4DLss6C4A2r5bTsqnAi+Yb8b+L1LFP2FlGAma5izYH3qlbqvS/5Xdfs7Hk0 HgcbpzNhcVnWyDklA8VEHO1DFRHxNsWJRuEOvMm2NhlL1h3B9x9YmtoN6jU9nsuN T24rvPsPrszmijhb0hH1tMGY8seU+A/z/99LYETo+qZdG0Pcc8TuQucX+N9P5do6 fpVVg8XV/kfPc7f+bqYR0QlfpUwr5pPAInVpfItuyRdWD+FaFq8AoumDYsQvK/Fe L2kF/n3aDz0jXdJzs8a0p7FERdJFBv8LNckVGtneo6ckQ0aKsSyOlhWK6MRC0iQI QzBYnKbVd7iDdDb9MfByMUmTNAiHtqbsd3mOLumF5cTlFvOR6Heoy/mUtCNvw3x1 0v4E/YrnjGsvE/WJkpIuBbsnfQC2Gm4/YXqTkETuDR6RR04Zvgq8ccb6wxu6U1kr AnjXaEjHimphMXKFXO48it+5yrbBwvOVzxfnq8TXYQ== =+WND -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#688252: $EDITOR + /usr/bin/editor default
Hello Ben, I'm not the maintiner, but I saw a related question on 'ubuntu-users' so I started hunting. The related previous bugs on this topic are: 1. * enable ENV_EDITOR Fixed in sudo (1.4.1-1) on 1996-03-05. 2. visudo does not default to vi=20 http://bugs.debian.org/388659 Fixed in sudo (1.6.9p9-1) on 2007-12-03 3. sudo: ignores configured editor preferences http://bugs.debian.org/474197 Fixed in sudo (1.6.9p15-2), on 2008-04-16 with a revert + rationale: * revert the fix for 388659 such that visudo once again defaults to using /usr/bin/editor. I was always ambivalent about this change, it has caused more confusion and frustration than it cured, … So my understanding is that since (April 2008) $EDITOR should be respected, and the fall-back should be to /usr/bin/editor. Could you clarify more precisely what you're seeing? -Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686502: pxz produces archives broken for busybox's unxz
On Sat, 2012-12-22 at 10:21 -0800, Jonathan Nieder wrote: What happens if a stream ends at a buffer boundary, followed by padding? Or if padding doesn't fit in the buffer, for that matter? That make very low probability but could happe indeed. I will upload a new patch which fixes this case too. Thank you for your review. Cheers, signature.asc Description: This is a digitally signed message part
Bug#636089: Please close
Since a similiar package is in testing [1], I assume this ITP should be closed? The changelog also mentioned it [2]: Initial release (Closes: #636089) Regards, Steffen [1] http://packages.debian.org/wheezy/swe-standard-data [2] http://packages.debian.org/changelogs/pool/main/s/swe-standard-data/swe-standard-data_4-1/changelog -- Steffen Vogel Robensstraße 69 52070 Aachen Mail: p...@steffenvogel.de Mobil: +49 176 34911387 Web: http://www.steffenvogel.de Jabber: st...@jabber.ccc.de ICQ: 236033 signature.asc Description: This is a digitally signed message part
Bug#696411: [Aptitude-devel] Bug#696411: aptitude: Missing dependency on apt?
On Fri, Dec 21, 2012 at 4:45 AM, Daniel Hartwig mand...@gmail.com wrote:
On 20 December 2012 22:19, Axel Beckert a...@debian.org wrote:
So since apt is not essential, but aptitude needs some binaries out of
that package to perform very common actions, aptitude must have a
dependency on apt
Such a dependency belongs to libapt-pkg, or to move the basic
method drivers to that package. It is libapt-pkg that uses
them, aptitude only requests to acquire some file and knows nothing
about any of these drivers or their usage.
This otherwise requires adding such a dependency to all libapt-pkg
consumers.
I recall this may have been discussed this year, though do not
recall the outcome.
The outcome was the usual one:
Would be nice, but needs work which probably nobody has the time for.
Even more so as I have (temporary) left so we even lack a nobody for
not having the time/motivation to do so currently as it seems …
(Not explicitly said of course and just mentioned in the discussion
resulting in libapt-pkg breaking apt instead of depending on it, so
you are absolutely not dreaming but might be a few months ago)
If we really wanted to solve this problem fast we should just mark
apt as proper Essential as it behaves like that. Currently only 13
machines participating in popcon don't have it installed …
But while this solves this problem, it just makes everything else
more complicated so this is of course a bogus solution – just ignore
the issue and let users shooting oneself in the foot if they really want to.
(To get that into perspective: We have 61 required packages (25 of them
are also Essential) – apt is not one of them but Top 29, which means it
ranks above half of the required packages set … in Vote it is even Top25 …)
(or at least recommend it).
Yes, packages other than apt do also provide method drivers, and—at
least in theory—could provide an alternative to the base set.
The most likely example is apt-transport-https I guess –
which transport is needed is a user configuration choice:
In a file (sources.list) which is at least documented by 'apt'.
Which is the actual problem: Configuration. Without apt installed you
miss some folders and files which technically aren't needed, but in
practice are the default configuration for libapt-* which is expected
to be present (like never-autoremove and all that stuff).
If I would have unlimited time there would be a libapt-bin which would be
M-A:foreign and includes the methods. There would also be a libapt-common
which includes the config files and directories so APT alternatives
(not aptitude, I mean stuff like cupt) have a chance to depend on what
they actually use. There would also be no libapt-{pkg,inst} split and later
I would build a motivation-machine and fly on my griffin to university …
Sadly, for now my money is on the griffin-thing to happen first.
Best regards and happy package management :)
(I wonder if this could be a diversity-statement compatible seasonal greeting)
David Kalnischkies
P.S.: I read aptitude-devel so I know the context, but a deity@ reader just
sees a Processed: … mail lacking all the context, so it might be a good
idea to sent your reassign mails to ${package}@packages.debian.org, too, as
these Processed mails are pretty easy to skip over.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649530: [copyright-format] clearer definitions and more consistent License: stanza specification
Le Tue, Dec 18, 2012 at 11:53:21PM +, Ximin Luo a écrit : https://github.com/infinity0/debian-policy/compare/bug649350-infinity0 I've split up my previous patch into more manageable chunks, and added extra explanations in the commit messages. I'm trying to follow the principle that the commit messages should already contain enough justification for the changes, but if any of them are unclear, please do ask me for further detail. (Further potential additions, which I've omitted for simplicity, include License-Exception: fields, and Location: fields to formalise the concept of a pointer to a License.) Dear Ximin, It was nice to split the patch and document the chunks, but I am still not convinced that the changes you propose are useful. In particular, I do not see the benefit from using a syntax for the license short names, especially that SPDX and other projects do not have one (for instance GPL-2 and GPL-2+ are seen as separate short names). Also, creating a syntax is a complex project that I think is beyond the scope of our machine-readable format. There are corner cases, for instance BSD-3-Clause is not the upgrade from BSD-2-Clause, or MPL-1.1 can be upgraded to MPL-2.0 despite its short name is not MPL-1.1+, etc. If you would like to work on a robust syntax, I propose you do it as an independant specification that can later be proposed for adoption not ony to use, but also to SPDX, OSI, ADMS.F/OSS, etc. Another change that you propose and that I disagree with is to forbid author- and software-specific information in stand-alone paragaphs. A lot of derivatives from the BSD licenses contain such information. Despite we link to a SPDX page where the BSD license terms are generic, I do not think that the intent in Debian's machine-readable format to is consider them all the same. At least in my copyright files I only use BSD-3-Clause if the copyright owners are the regents of the university of California. Cheers, -- Charles Plessy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684732: unblock: nut/2.6.4-2
All Thanks a lot for your work! I've quickly checked (with a limited mobile terminal) and everything seems fine. Sorry for being MIA here, but it will probably be for some more time... All the best for end of the year celebrations. Cheers, Arnaud (sent from my S3... please excuse my brevity) Le 20 déc. 2012 20:47, Ivo De Decker ivo.dedec...@ugent.be a écrit : Hi Laurent, On Thu, Dec 20, 2012 at 08:19:21PM +0100, Laurent Bigonville wrote: I prepared an NMU that should fix both issues. The debdiff against wheezy and the debdiff -w against sid are attached. I will try to get this NMU uploaded soon. Looks good but (there is always a but :), /etc/init.d/nut is shipped in the nut package in squeeze, so I guess it should also be removed when upgrading that package. And in case of partial upgrade, I guess you also want to remove it when the nut-client package is installed as it will cause issue if both /etc/init.d/nut and /etc/init.d/nut-client are trying to start the same components. So I would say, remove it when upgrading nut, nut-client and nut-server (which is already the case). Am I correct here? Thanks for the review. I added it to nut-client as well (new debdiffs attached). Adding it to nut is not necessary, because nut depends on nut-client and nut-server, so if nut is installed, the old init script will be removed anyway by nut-client or nut-server. Cheers, Ivo
Bug#695130: openmotif is now LGPL, retirement of lesstif in jessie?
Hi Graham, On 24-12-12 10:41, Graham Inggs wrote: The openmotif package has recently been orphaned since the maintainer is MIA. Not quite, the maintainer said he didn't have time anymore. It is a detail anyway. I have been working on a new packaging of the LGPL motif from scratch using dh. Why from scratch? Take the good things from the current package, but indeed, I would like to switch to dh(1) as well. I am currently working on getting the current package fit for multiarch and hardening enabled. I would like to see the openmotif package renamed to motif What do others on this list think? I think openmotif as the source package name is a fine, but I don't really care. The only thing that I like about keeping the name is that the history of the package is better linked in the PTS and such. and replace lesstif in jessie. Let's call it migration to motif and retirement of lesstif. My motif package will be available in my Ubuntu PPA within the next day or two: https://launchpad.net/~ginggs/+archive/ppa I do appreciate your effort, but currently Joël Bertrand is the one in the orphan bug [1], stating his intent to adopt (although he forgot to retitle and own the bug). I proposed to him (no response yet) to make this a team effort, do you want to join? I really would like to get the packaging in a VCS, e.g. on Alioth in the collab-maint project. If he agrees, we could start with packaging the next version already in experimental. Although of course, we should be focusing on releasing Wheezy right now. Paul [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695130 signature.asc Description: OpenPGP digital signature
Bug#696610: Pending fixes for bugs in the libconfig-model-perl package
tag 696610 + pending thanks Some bugs in the libconfig-model-perl package are closed in revision 4eabd8665b9de0094edea3a29bf700db384bf16c in branch 'master' by Dominique Dumont The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libconfig-model-perl.git;a=commitdiff;h=4eabd86 Commit message: control: recommends fuse instead of transitional package fuse-utils (Closes: #696610) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696184: fail2ban: CVE-2012-5642: input variable quoting flaw on matches content
On Mon, Dec 17, 2012 at 01:16:27PM -0500, Yaroslav Halchenko wrote: Thank you my consciousness ;) Just a note: this issue is very unlikely to hit anyone since matches is not used by default in any shipped action file and it was only recently introduced so I doubt it was adopted by more than a handful deployments. But indeed -- wheezy should get a patched version. Meanwhile -- anyone in need to run fail2ban on their boxes -- use 0.8.8 from sid or backports from neuro.debian.net repository Can you please upload a minimal fix to unstable and ask the release managers for an unblock? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541867: blktrace: Incorrect runlevels in init.d script [fixed in repository]
I believe this bug is fixed in repository: http://anonscm.debian.org/gitweb/?p=collab-maint/blktrace.git Regards, Dmitry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696329: fixed in lemonldap-ng 1.2.2-3
On Sun, Dec 23, 2012 at 05:32:34PM +, Xavier Guimard wrote: Source: lemonldap-ng Source-Version: 1.2.2-3 lemonldap-ng (1.2.2-3) unstable; urgency=low . * Add verify-saml-signatures.patch, fix for CVE-2012-6426 (Closes: #696329) Checksums-Sha1: Xavier, Wheezy is still affected and the version in unstable has diverged too much to be accepted into Wheezy at this point of the freeze. Please upload the minimal security to testing-proposed-updates (distribution= testing) and using the version 1.1.2-5+deb7u1. After that that file an unblock request by filing a bug against release.debian.org Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694531: fixed in git
tags 694531 + pending thanks Hi Paul, thanks for your bugreport! I've fixed it in git for the next upload to experimental and also committed a fix to the upstream git making the documentation match the code. cheers, Holger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696628: nmu: adplug_2.2.1+dfsg2-1.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi Release Team, please binNMU adplug. The amd64 build of libadplug-2.2.1-0 uploaded to the archive has an libc6 dependency that cannot be satisfied in wheezy/sid. It has been built in an environment with libc6 from experimental. Rebuilding adplug in a clean environment gets rid of the unsatisfiable dependency. nmu adplug_2.2.1+dfsg2-1.1 . amd64 . -m Rebuild in a clean environment. Thanks -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#696521: marked as done (Bépo keyboard layout missing in Debian installer)
On Sat, Dec 22, 2012 at 10:36:03AM +, Debian Bug Tracking System wrote: The set of keymaps that are offerred at installation is limited on purpose (size and memory constraints as well as avoiding too many options that are confusing for users). Just a little clarification. The memory constraints are more or less irrelevant here because even with all supported by XKB keyboard layouts, variants and options the required additional memory space is very small. The only important thing here is not to confuse the users with too many options. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696329: fixed in lemonldap-ng 1.2.2-3
On Mon, 24 Dec 2012 12:37:37 +0100, Moritz Mühlenhoff wrote: Please upload the minimal security to testing-proposed-updates (distribution= testing) and using the version 1.1.2-5+deb7u1. After that that file an unblock request by filing a bug against release.debian.org Xavier has already filed an unblock request (#696516), and Adam has asked for an upload to unstable to happen before to give the patch some testing. So the fix for wheezy is kind of pending :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Arik Brauer: Sein Köpferl im Sand signature.asc Description: Digital signature
Bug#696629: uptimed on kFreeBSD fails to keep stats on reboot
Package: uptimed Version: 1:0.3.17-3.1 Severity: normal Dear Maintainer, I use uptimed/uprecords on different machines with different architectures. With Linux everything works as expected. With kFreeBSD the statistics seems to be frozen. The first record is persistent after a reboot. The actual running time does not survive a reboot. Example: fz@vorlon:~$ uprecords # Uptime | System Boot up +--- - 1 0 days, 16:47:29 | GNU/kFreeBSD 9.0-2-amd64 Sun Dec 23 21:09:01 2012 2 0 days, 00:20:00 | GNU/kFreeBSD 9.0-2-amd64 Tue Nov 6 19:38:46 2012 +--- NewRec 0 days, 16:27:28 | since Sun Dec 23 21:29:01 2012 up 0 days, 17:07:29 | since Tue Nov 6 19:38:46 2012 down47 days, 01:10:15 | since Tue Nov 6 19:38:46 2012 %up1.494 | since Tue Nov 6 19:38:46 2012 This #2 record is highest running time after every reboot. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages uptimed depends on: ii debconf [debconf-2.0] 1.5.48 ii dpkg 1.16.9 ii libc0.12.13-37 ii libuptimed01:0.3.17-3.1 ii lsb-base 4.1+Debian8 uptimed recommends no packages. uptimed suggests no packages. -- debconf information: uptimed/mail/do_mail: Never uptimed/mail/address: root@localhost uptimed/mail/milestones_info: uptimed/maxrecords: 50 uptimed/interval: 60 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696149: [Pkg-samba-maint] Bug#696149: samba4: deletes directories owned by samba-common during purge: /var/{cache, lib, log}/samba
Hi Ivo, On Sun, 2012-12-23 at 21:21 +0100, Ivo De Decker wrote: Hi Jelmer, On Mon, Dec 17, 2012 at 11:45:48AM +0100, Andreas Beckmann wrote: From the attached log (scroll to the bottom...): 0m48.7s ERROR: FAIL: After purging files have disappeared: /var/cache/samba/ owned by: samba4-common-bin, samba-common /var/lib/samba/owned by: samba4, samba-common /var/log/samba/owned by: samba-common In this test only the samba4 package was purged, all dependencies are still installed. samba4.postrm purge performs: # Remove Samba's state files, both volatile and non-volatile rm -Rf /var/run/samba/ /var/cache/samba/ /var/lib/samba # Remove log files rm -Rf /var/log/samba/ (the debconf db_purge is run twice, there is no need to add this manually to the maintainer script as dh_installdebconf already adds it) I had a look at the samba4 package in wheezy, and tried to solve this bug by limiting the removal to files that are created by samba4 (not by other samba related packages). A patch that implements this is attached. With this patch, samba4 doesn't hit the piuparts issues listed above. Thanks! However, I encountered 2 issues: - samba4 logs to /var/log/samba/log.%m The removal of this file is easy to solve, but I can't imagine the name of this logfile is intentional. Obviously this is the result of changes in samba4 (it seems %m is sadly no longer allowed in logfile names). I would argue that this is in fact a bug in samba-common; we'll have this problem as well when we merge the samba and samba4 source packages. Please file a bug about this. - the piuparts log also complains about: 0m48.7s ERROR: FAIL: After purging files have been modified: /etc/samba/smb.confnot owned Samba4 changes smb.conf (adds 2 parameters and 2 shares), but smb.conf is owned by samba-common, not by samba4. Maybe this should be solved in samba-common by allowing other packages to add config files (this is more or less what was asked in #675906). I guess purge should ideally remove these 2 parameters again; they are only used by Samba 4. I'm not entirely sure about the shares. That said, this problem will go away when we merge the samba and samba4 source packages so I'm not sure if it is worth spending much time on, unless it is for wheezy. Cheers, Jelmer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696630: libconfig-model-dpkg-perl: typos in package description
Package: libconfig-model-dpkg-perl Version: 2.031 Severity: minor Dear Maintainer, I noticed a few typos in the package description: * chek should be check * provide should be provides in the first two paragraphs (The command 'cme edit dpkg' provide and The command 'cme chek dpkg' provide) * directoty should be directory Regards, Stephen -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libconfig-model-dpkg-perl depends on: ii libany-moose-perl 0.17-1 ii libanyevent-http-perl 2.14-1 ii libanyevent-perl 7.010-1 ii libapt-pkg-perl 0.1.26+b1 ii libconfig-model-perl 2.029-1 ii libfile-homedir-perl 0.99-1 ii liblog-log4perl-perl 1.29-1 ii libmouse-perl 0.99-1 ii libparse-recdescent-perl 1.967009+dfsg-1 ii libsoftware-license-perl 0.103005-1 ii libtext-autoformat-perl 1.669002-1 ii libtext-diff-perl 1.41-1 ii libyaml-perl 0.81-1 ii lintian 2.5.10.3 ii perl 5.14.2-16 Versions of packages libconfig-model-dpkg-perl recommends: ii libconfig-model-tkui-perl 1.337-2 ii libmodule-corelist-perl 2.68-1 ii perl5.14.2-16 ii perl-modules [libmodule-corelist-perl] 5.14.2-16 libconfig-model-dpkg-perl 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#696631: libconfig-model-dpkg-perl: '+' is allowed in package names
Package: libconfig-model-dpkg-perl Version: 2.031 Severity: normal Dear Maintainer, When running cme check dpkg in the gcc-mingw-w64 source, I get failures related to the use of '+' in a package name: Warning in 'control binary:gcc-mingw-w64 Recommends:0' value 'g++-mingw-w64': package g is unknown. Check for typos if not a virtual package. Configuration item 'control binary:gcc-mingw-w64 Recommends:0' has a wrong value: dependency 'g++-mingw-w64' does not match grammar As far as I'm aware this package name is perfectly legal. Unfortunately my perl-fu doesn't extend far enough to fix this... Regards, Stephen -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libconfig-model-dpkg-perl depends on: ii libany-moose-perl 0.17-1 ii libanyevent-http-perl 2.14-1 ii libanyevent-perl 7.010-1 ii libapt-pkg-perl 0.1.26+b1 ii libconfig-model-perl 2.029-1 ii libfile-homedir-perl 0.99-1 ii liblog-log4perl-perl 1.29-1 ii libmouse-perl 0.99-1 ii libparse-recdescent-perl 1.967009+dfsg-1 ii libsoftware-license-perl 0.103005-1 ii libtext-autoformat-perl 1.669002-1 ii libtext-diff-perl 1.41-1 ii libyaml-perl 0.81-1 ii lintian 2.5.10.3 ii perl 5.14.2-16 Versions of packages libconfig-model-dpkg-perl recommends: ii libconfig-model-tkui-perl 1.337-2 ii libmodule-corelist-perl 2.68-1 ii perl5.14.2-16 ii perl-modules [libmodule-corelist-perl] 5.14.2-16 libconfig-model-dpkg-perl 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#696632: initramfs-tools: Patches to clean up /run handling for jessie
Package: initramfs-tools
Version: 0.109
Severity: important
Tags: patch
I have attached two patches for your consideration:
1) Migration of /run to the rootfs is mandatory, i.e. /run is required to
be present on the rootfs. This will be the case for all jessie installs
and upgrades (unlike wheezy, which needed the special-case logic to
manually migrate udev/mdadm state).
2) Create /run/initramfs if needed. This might also need fixing for wheezy,
since I can't see where it's created (if at all), so opening the debug
file might actually be broken at present.
Regards,
Roger
From 13d1e4b4bf8dc163ae488016aa2da6a11b284f57 Mon Sep 17 00:00:00 2001
From: Roger Leigh rle...@debian.org
Date: Mon, 24 Dec 2012 13:36:53 +
Subject: [PATCH 1/2] init: Always migrate /run to the rootfs
---
init | 16 ++--
1 file changed, 2 insertions(+), 14 deletions(-)
diff --git a/init b/init
index cb832ff..929de29 100755
--- a/init
+++ b/init
@@ -228,20 +228,8 @@ maybe_break bottom
run_scripts /scripts/init-bottom
[ $quiet != y ] log_end_msg
-# Preserve information on old systems without /run on the rootfs
-if [ -d ${rootmnt}/run ]; then
- mount -n -o move /run ${rootmnt}/run
-else
- # The initramfs udev database must be migrated:
- if [ -d /run/udev ] [ ! -d /dev/.udev ]; then
- mv /run/udev /dev/.udev
- fi
- # The initramfs debug info must be migrated:
- if [ -d /run/initramfs ] [ ! -d /dev/.initramfs ]; then
- mv /run/initramfs /dev/.initramfs
- fi
- umount /run
-fi
+# Move /run to the root
+mount -n -o move /run ${rootmnt}/run
validate_init() {
checktarget=${1}
--
1.7.10.4
From 29046070b93b4c97456ca9a8aadfbba0a54dc380 Mon Sep 17 00:00:00 2001
From: Roger Leigh rle...@debian.org
Date: Mon, 24 Dec 2012 13:38:40 +
Subject: [PATCH 2/2] init: Create /run/initramfs
---
init |1 +
1 file changed, 1 insertion(+)
diff --git a/init b/init
index 929de29..c6c84d3 100755
--- a/init
+++ b/init
@@ -160,6 +160,7 @@ for x in $(cat /proc/cmdline); do
debug)
debug=y
quiet=n
+ mkdir -m 0700 /run/initramfs
exec /run/initramfs/initramfs.debug 21
set -x
;;
--
1.7.10.4
Bug#696428: Updated po Spanish translation file for the maint-guide package
Feliç nadal On Thu, Dec 20, 2012 at 06:11:34PM +0100, Innocent De Marchi wrote: Package: maint-guide Version: 1.2.30 Severity: wishlist Tags: l10n Hi Osama, maint-guide.ca.po file have been translated and checked by Debian l10n Catalan Team. It would be fantastic if you could add attached .po file in maint-guide package. I also attached the maint-guide.ca.ent file updated. Thanks! I. De Marchi Gràcies Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696521: marked as done (Bépo keyboard layout missing in Debian installer)
Anton Zinoviev, le Mon 24 Dec 2012 13:50:00 +0200, a écrit : Just a little clarification. The memory constraints are more or less irrelevant here because even with all supported by XKB keyboard layouts, variants and options the required additional memory space is very small. Memory also includes the initrd room for storing them, which is not so neglectible. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696522: openchrome driver-configuration in xorg.conf fails
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After fussing for some hours, trying to configure my xorg-server properly, I admit now, that it plainly is not possible. I attach my /etc/X11/xorg.conf and the corresponding X-logfile, both zlib-compressed. First I tried to limit Vmax and Hmax in order to prevent the driver to initialize the 1360 px wide screen, but it did not work out. Then trying 'Option MaxClock 8' failed, too. Then trying to set various Modelines in the Monitor-section had no effect either. Finally I had looks at 'videogen' and 'xvidtune', trying those Modelines out. Now I feel that i can not do anything more, but someone else has to fix this issue. The openchrome-driver ignores DDC-probed resulutions, it ignores the 'MaxClock'-option and various Modelines and sets up a 1360 px wide screen initially, that vanishes upon login. Please fix this issue. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAlDYXhwACgkQ5+rBHyUt5wu/swCgno0gCl7L+5GwDNlSriH6yMxN hDcAn3KobwoJM49f0gfSIKO0NHFVbMmN =rzwJ -END PGP SIGNATURE- xorg.conf.gz Description: GNU Zip compressed data Xorg.0.log.gz Description: GNU Zip compressed data
Bug#696633: libgl1-mesa-dri - exit(1) as error handling, killing the window manager
Package: libgl1-mesa-dri Version: 8.0.5-3 Severity: important File: /usr/lib/x86_64-linux-gnu/dri/i915_dri.so src/mesa/drivers/dri/intel/intel_batchbuffer.c:do_flush_locked uses exit(1) as error handler. This breaks most current window managers (gnome-shell, kwin) at arbitrary times and does not allow any cleanup of the mess. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgl1-mesa-dri:amd64 depends on: ii libc6 2.13-37 ii libdrm-intel1 2.4.33-3 ii libdrm-nouveau1a 2.4.33-3 ii libdrm-radeon12.4.33-3 ii libdrm2 2.4.33-3 ii libexpat1 2.1.0-1 ii libffi5 3.0.10-3 ii libgcc1 1:4.7.2-4 ii libstdc++64.7.2-4 libgl1-mesa-dri:amd64 recommends no packages. Versions of packages libgl1-mesa-dri:amd64 suggests: pn libglide3 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#696600: RFS: sun/0.2-1 [ITP] schedule cron or at-jobs at sunrise/set
On 13070 March 1977, Steffen Vogel wrote: There still the problem that the package name (sun) might be too generic to be included in the archive. What do you think about this concern? I've collected some alternatives: solar suncal atsun sunrun suncycles - makes no sense to me As the one effectively blocking sun as a name, my 2¢ here would be on suncal. Fits it perfectly IMO. -- bye, Joerg 1. 0 2. 1 3. 2 4. 3 5. 4 6. 5 7. 6 8. 7 |-) What sort of FTP proxy firewall do you have? -- libnet-perl 1.16-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675295: matanza: FTBFS in experimental: format not a string literal and no format arguments
Just in case. My RFS is available here: http://bugs.debian.org/696385 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673790: python-cloudservers: diff for NMU version 1.1-1.2
Control: tags -1 + patch pending
Dear maintainer,
I've prepared an NMU for python-cloudservers (versioned as 1.1-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
Sebastian Ramacher
diff -Nru python-cloudservers-1.1/debian/changelog python-cloudservers-1.1/debian/changelog
--- python-cloudservers-1.1/debian/changelog 2012-04-29 07:20:11.0 +0200
+++ python-cloudservers-1.1/debian/changelog 2012-12-24 15:11:18.0 +0100
@@ -1,3 +1,12 @@
+python-cloudservers (1.1-1.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/patches/673790.patch: Fix usage of prettytable. prettytable 0.6
+changed the API. (Closes: #673790)
+ * debian/control: Bump python-prettytable (Build-)Depends to = 0.6.
+
+ -- Sebastian Ramacher sramac...@debian.org Mon, 24 Dec 2012 15:10:46 +0100
+
python-cloudservers (1.1-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru python-cloudservers-1.1/debian/control python-cloudservers-1.1/debian/control
--- python-cloudservers-1.1/debian/control 2012-04-29 07:17:02.0 +0200
+++ python-cloudservers-1.1/debian/control 2012-12-24 14:43:13.0 +0100
@@ -2,13 +2,13 @@
Section: python
Priority: optional
Maintainer: Soren Hansen so...@ubuntu.com
-Build-Depends: cdbs, debhelper (= 5.0.38), python-all (= 2.3.5-11), python-support, python-distribute, python-nose, python-prettytable, python-argparse, python-mock, python-httplib2
+Build-Depends: cdbs, debhelper (= 5.0.38), python-all (= 2.3.5-11), python-support, python-distribute, python-nose, python-prettytable (= 0.6), python-argparse, python-mock, python-httplib2
XS-Python-Version: = 2.6
Standards-Version: 3.8.4
Package: python-cloudservers
Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}, python-pkg-resources, python-prettytable, python-argparse, python-httplib2, python (= 2.6)
+Depends: ${misc:Depends}, ${python:Depends}, python-pkg-resources, python-prettytable (= 0.6), python-argparse, python-httplib2, python (= 2.6)
XB-Python-Version: ${python:Versions}
Description: client library for Rackspace's Cloud Servers API
Python library and CLI tool for interacting with Rackspace's Cloud
diff -Nru python-cloudservers-1.1/debian/patches/673790.patch python-cloudservers-1.1/debian/patches/673790.patch
--- python-cloudservers-1.1/debian/patches/673790.patch 1970-01-01 01:00:00.0 +0100
+++ python-cloudservers-1.1/debian/patches/673790.patch 2012-12-24 14:47:20.0 +0100
@@ -0,0 +1,31 @@
+Description: update use of prettytable to the new API
+Author: Sebastian Ramacher sramac...@debian.org
+Last-Update: 2012-12-24
+
+Index: python-cloudservers-1.1/cloudservers/shell.py
+===
+--- python-cloudservers-1.1.orig/cloudservers/shell.py 2012-12-24 14:46:12.069855412 +0100
python-cloudservers-1.1/cloudservers/shell.py 2012-12-24 14:47:10.227633083 +0100
+@@ -437,16 +437,18 @@
+ # Helpers
+ def print_list(objs, fields):
+ pt = prettytable.PrettyTable([f for f in fields], caching=False)
+-pt.aligns = ['l' for f in fields]
++for f in fields:
++ pt.align[f] = 'l'
+ for o in objs:
+ pt.add_row([getattr(o, f.lower().replace(' ', '_'), '') for f in fields])
+-pt.printt(sortby=fields[0])
++print pt.get_string(sortby=fields[0])
+
+ def print_dict(d):
+ pt = prettytable.PrettyTable(['Property', 'Value'], caching=False)
+-pt.aligns = ['l', 'l']
++pt.align['Property'] = 'l'
++pt.align['Value'] = 'l'
+ [pt.add_row(list(r)) for r in d.iteritems()]
+-pt.printt(sortby='Property')
++print pt.get_string(sortby='Property')
+
+ def main():
+ try:
diff -Nru python-cloudservers-1.1/debian/patches/series python-cloudservers-1.1/debian/patches/series
--- python-cloudservers-1.1/debian/patches/series 2012-04-29 07:22:00.0 +0200
+++ python-cloudservers-1.1/debian/patches/series 2012-12-24 14:35:13.0 +0100
@@ -1,3 +1,4 @@
cleaner-sources.txt
autogeneration-fallout
Fixes-egg-info-PKG-INFO
+673790.patch
signature.asc
Description: Digital signature
Bug#696624: linux-utils: System fails to boot if system date is corrected.
Hi, Somehow it's interpreting a regular system clock change as a filesystem error And thus trigger an automatic filesystem check, which doesn't seem like a bad idea by default when the last mount was in the future. that needs an administrator password to fix. It looks like the automatic check was not able to perform (because of errors he couldn't handle), and thus ask the administrator to perfomm a manual check. Can you confirm the file system was not clean? Regards David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675295: matanza: FTBFS in experimental: format not a string literal and no format arguments
Sorry. Link should be: http://bugs.debian.org/696192 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696507: festival: FTBFS: not multi-arch capable but a dependency is multiarchified already
Dixi quod… Ivo De Decker dixit: Here is a patch that fixes the build: Wow, thanks for your quick reaction! This indeed fixes the build failure; I uploaded to unreleased for the time being. bye, //mirabilos -- Sometimes they [people] care too much: pretty printers [and syntax highligh- ting, d.A.] mechanically produce pretty output that accentuates irrelevant detail in the program, which is as sensible as putting all the prepositions in English text in bold font. -- Rob Pike in Notes on Programming in C -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690394: Bug#690877: unblock: love/0.8.0-3
Hi Bas, On Sun, Dec 23, 2012 at 11:45:43PM +0100, Bas Wijnen wrote: On 23-12-12 00:37, Ivo De Decker wrote: I prepared a TPU upload to fix the copyright file bug (#690394) in wheezy. The debdiff is attached. Looks good. Thanks for the review. However, version 0.8.0-3 is already in unstable, so please make the version 0.8.0-2.1 instead. That's fine with me, but I guess the release team prefers +deb7u1 for wheezy. Will you upload the package? That's OK, but as it is a TPU upload, we first need pre-approval from the release team. I also included a lintian override for the ftp-master autoreject (bug #690492). I don't know if this is needed for TPU uploads. As Julien downgraded bug #690492 from serious to important, I suspect the embedded copy of glee can stay for wheezy. In don't usually like lintian overrides, but I suppose this is a good use for one. Still I'd prefer the error to be visible, and override the autoreject instead of lintian itself... Well, I'm just using the procedure I know. I don't think there is a way to override the autoreject without overriding the lintian error (other than asking for a manual override after the upload). Anyway, this problem will go away after wheezy, as you uploaded the fix to unstable for jessie. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683847: unblock: sgml-base/1.26+nmu4
On 09.10.2012 08:10, Helmut Grohne wrote: On Tue, Oct 09, 2012 at 09:15:32AM +0200, Raphael Hertzog wrote: On Mon, 08 Oct 2012, Helmut Grohne wrote: 1) Add a pre-dependency on dpkg such that dpkg is already upgraded before deconfiguring sgml-base. This does not guarantee to solve the issue, because the old dpkg may still be running, but it makes it highly unlikely. IIRC when apt upgrades dpkg, it configures it immediately so that any package processed after dpkg is guaranteed to be processed by the upgraded dpkg. Thanks for the explanation. Do you also know whether aptitude and cupt show the same behaviour? CCing the relevant maintainers. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696634: samba-common: logfile log.%m no longer supported in samba4
package: samba-common version: 2:3.6.6-3 Hi, As noted in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696149#15, samba4 no longer supports logging to log.%m, so we should provide a new default logfile in smb.conf. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696635: unblock: base-files/7.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Greetings. This release is the one finally saying 7.0 in /etc/debian_version so I would naturally like to see it in wheezy. If this may be done before the upcoming debian installer release candidate, even better. Changes from 6.11 are what everybody would expect for a stable release plus some easy and low risk fixes (which means things like #681489 will have to wait for jessie). unblock: base-files/7.1 Thanks a lot. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696141: kdenetwork: FTBFS: moc: .../kopete/protocols/sms/gsmlibprefs.h: No such file
Control: found -1 4:4.8.4-1 Control: notfound -1 4.8.4-1 On 2012-12-17 08:29:22, Thorsten Glaser wrote: Source: kdenetwork Version: 4.8.4-1 It looks like you've forgot the epoch. Fixing the version information. Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#696636: python-gpgme: package includes essentially zero documentation
Package: python-gpgme Version: 0.2-2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 There is no documentation included in this pacakge. The built-in help documentation is less than minimal and gives no indication on how to use any of the included functions. Example: servo:~ 0$ python -c import gpgme; help(gpgme.Context.decrypt) Help on method_descriptor: decrypt(...) servo:~ 0$ Is this a joke? I also can't find any documentation online. As far as I can tell, this is the home page of the project: https://launchpad.net/pygpgme No documentation there either. Is this not a violation of policy? jamie. - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-gpgme depends on: ii libc6 2.13-37 ii libgpgme11 1.2.0-1.4 ii python 2.7.3~rc2-1 ii python2.6 2.6.8-0.2 ii python2.7 2.7.3~rc2-2.1 python-gpgme recommends no packages. python-gpgme suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ2IEeAAoJEO00zqvie6q8WzoP/i/HOf9HWyqIb+bEt+bbulZc W3t1ZGk/ftJ85sH4s7DtrYD5Uv6psVvGS5T7Kyrmu/Lo5R9LFhFPQOQnOspS4tEC AiYFwi4mHGPnaR4al89t6yN6t5uN4YYbmepY4FtRJafx9K1Y06gaCfSr74DSkY6P qjbIca2Cizp6ahEfRly58wPoT11hlFB/HwQQU0fr8+SnMuJdZckUu6XCvsOQkyj+ voqCJL552M5SfpmkThXCuOmhwgb7vDwJx2/hnc+E3m034+jE+1jSzpDJiN4/mGWv pygxNTZkhm/NO2Ko7PgxycaJGd9mARDmaDgHD1xstxr6PmHhSaPS7zcF0SO9x2OK PhgJrzbLeB+BVE+ntqNj3H9XzqoQT9hsPG2ZqEndOX1AAnKAsqt2MbB0jeyD0+Ay S9QW8DdKe76cPmGySdGxKiGnculVb81T3OyXSZUtig6wqA9uPgmlzB2vg2JWRo64 MIjz1cHLSbJq1LOeb6imtqFOP9obaXb2A3NWuZmjafpC6NQzspFfpIxg3sz+nF78 9JWzEM1uLE3zfa9u5L+ktCFBkswgo/bLwrEGnsAIHaBnagKBMpVU1H3gXI/5vShD 21f4yDKUGsUKxAJ4643uZ9BctjPWA4DFdeUkET+OhgZQJOzIvkcVvAdK5tP8MazN CXbtynerz66KT0JtdmaU =P7Ra -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#696638: [kde-workspace] pam file for kscreensaver
Package: kde-workspace Version: 4:4.8.4-5 Severity: wishlist Tags: patch --- Please enter the report below this line. --- by default its not possbile to use an pam file for kscreensaver, it fallsback to other, this small patch it changing this. kscreensaver calls kcheckpass for the password, and kcheckpass is able to load differen pam files. please integreate, it enables to use an fingerprint reader in combination of encrypted home (kdm login uses a password to decrypt the home, kscreensaver uses a finger to unlock the screen) after the patch, a pam file can be used /etc/pam.d/kcheckpass --- kde-workspace-4.8.4.orig/krunner/lock/lockdlg.cc +++ kde-workspace-4.8.4/krunner/lock/lockdlg.cc @@ -462,7 +462,7 @@ void PasswordDlg::gplugStart() kcheckpass, -m, mPlugin-info-method, -S, fdbuf, + -c, kcheckpass, (char *)0); _exit(20); } --- System information. --- Architecture: amd64 Kernel: Linux 3.6.11-iwlwifi-1-g67bf613 Debian Release: wheezy/sid 500 testing ftp.at.debian.org 500 stable dl.google.com 500 stable apt.multi24.com 500 natty ppa.launchpad.net 500 lucid ppa.launchpad.net --- Package information. --- Depends (Version) | Installed =-+-=== kde-workspace-bin (= 4:4.8.4-5) | 4:4.8.4-5 klipper (= 4:4.8.4-5) | 4:4.8.4-5 ksysguard (= 4:4.8.4-5) | 4:4.8.4-5 kde-window-manager (= 4:4.8.4-5) | 4:4.8.4-5 systemsettings (= 4:4.8.4-5) | 4:4.8.4-5 freespacenotifier (= 4:4.8.4-5) | 4:4.8.4-5 Recommends (Version) | Installed ==-+-=== kdm (= 4:4.8.4-5) | 4:4.8.4-5 kinfocenter (= 4:4.8.4-5) | 4:4.8.4-5 kmenuedit (= 4:4.8.4-5) | 4:4.8.4-5 Package's Suggests field is empty. -- Dipl.-Inf. Univ. Florian Reitmeir E-Mail: n...@multi24.com Tel: +43 512 209040 Fax: +43 512 209040 10 HP: http://net.multi24.com Leopoldstrasse 63 6020 Innsbruck / Austria
Bug#694971: ia64 (Itanium) Epiphany browser crashes within JSC::JSArray::increaseVectorLength()
Hi Stephan, When I saw your patch for this bug (and #692053) I immediately thought of mipsel hardware with 16K page size. I think you have probably found the reason for #651636. I'm afraid I can't really test your patch though until it is uploaded and built on the buildds (it takes them more than a day! and all I have is a netbook). Thanks for your work on this! Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696282: gnucash silently removes the scheduled transactions under some condition
On 2012-12-19 Vincent Lefevre vinc...@vinc17.net wrote:
[...]
Control: retitle -2 libxml2: gzip decompression truncates the output
(possible data loss)
Control: found -2 2.8.0+dfsg1-7
Control: tag -2 upstream fixed-upstream
On 2012-12-19 00:16:41 +0100, Vincent Lefevre wrote:
[...]
$ gnucash test.gnucash
Found Finance::Quote version 1.17
I/O error : Resource temporarily unavailable
$
I've done tests with gdb, and the problem occurs at
xmlParseDocument( ctxt-data.saxParserCtxt );
in src/backend/xml/sixtp.c line 709 (sixtp_parse_file_common).
It comes from a known bug in libxml2, discussed here:
https://bugzilla.redhat.com/show_bug.cgi?id=877567
It is fixed upstream.
[...]
Hello,
I am not familiar with libxml2 development, however
http://www.xmlsoft.org/downloads.html points to
git://git.gnome.org/libxml2 as upstream. Afaict git head still shows
the problem. [Fedora ships the attached patch, but they are not
upstream, are they?]
cu andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -up libxml2-2.9.0/xzlib.c.do-not-check-crc libxml2-2.9.0/xzlib.c
--- libxml2-2.9.0/xzlib.c.do-not-check-crc 2012-09-11 05:52:46.0 +0200
+++ libxml2-2.9.0/xzlib.c 2012-11-19 19:28:42.431700534 +0100
@@ -552,17 +552,20 @@ xz_decomp(xz_statep state)
#ifdef HAVE_ZLIB_H
if (state-how == GZIP) {
if (gz_next4(state, crc) == -1 || gz_next4(state, len) == -1) {
-xz_error(state, LZMA_DATA_ERROR, unexpected end of file);
-return -1;
-}
-if (crc != state-zstrm.adler) {
-xz_error(state, LZMA_DATA_ERROR, incorrect data check);
-return -1;
-}
-if (len != (state-zstrm.total_out 0xL)) {
-xz_error(state, LZMA_DATA_ERROR, incorrect length check);
-return -1;
-}
+/*
+ xz_error(state, LZMA_DATA_ERROR, unexpected end of file);
+ return -1;
+*/
+} else {
+ if (crc != state-zstrm.adler) {
+ xz_error(state, LZMA_DATA_ERROR, incorrect data check);
+ return -1;
+ }
+ if (len != (state-zstrm.total_out 0xL)) {
+ xz_error(state, LZMA_DATA_ERROR, incorrect length check);
+ return -1;
+ }
+ }
state-strm.avail_in = 0;
state-strm.next_in = NULL;
state-strm.avail_out = 0;
Bug#696185: [copyright-format] Please clarify what to use in License field for licenses not specifically mentioned
retitle 696185 [copyright-format] Use short names from SPDX. severity 696185 wishlist thanks Le Tue, Dec 18, 2012 at 10:20:08AM -0500, Andrew Starr-Bochicchio a écrit : On Tue, Dec 18, 2012 at 4:15 AM, Charles Plessy ple...@debian.org wrote: I would be in favor of formally recommending to follow SPDX in a later revision of the specification, but before this we would need a consensus on stopping calling the MIT license Expat, so I am quite inclined to wait longer and see how the SPDX short names establish themselves in other projects. I agree, and this was a secondary concern of this report. Feel free to close or retitle (and maybe change the severity to wishlist) to explicitly deal with the SPDX issue. Retitled and downgraded to wishlist. Cheers, and merry Christmas to everybody celebrating it ! -- Charles Plessy Illkirch-Graffenstaden, France -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696637: paraview: dangling links in /usr/lib/paraview/vistrails/plugin/pgui/resources/images
tags 696637 +pending thanks It is fixed in git. Thanks for pointing that out. Cheers, Anton 2012/12/24 Jörg-Volker Peetz jvpe...@web.de: Package: paraview Version: 3.14.1-6, 3.14.1-7 Severity: minor Dear Maintainer, as the subject indicates, the links in directory /usr/lib/paraview/vistrails/plugin/pgui/resources/images are pointing to files not delivered by any package of wheezy or sid. Should they be removed? -- Best regards, Jörg-Volker. -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696639: libtext-levenshtein-perl: Patch to fix lintian warnings
Source: libtext-levenshtein-perl Version: 0.06~01-1 Severity: normal Tags: patch Dear maintainer, Lintian now depends on libtext-levenshtein-perl [1], so we are going to include this package into Ubuntu's main archive [2]. It would be easier to achieve if the package was lintian clean. The attached patch fixes all warnings except one pedantic. It also fixes #695754. [1]: http://anonscm.debian.org/gitweb/?p=lintian/lintian.git;a=commit;h=1144b47acd [2]: https://bugs.launchpad.net/bugs/1093329 -- Dmitry Shachnev -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (700, 'unstable'), (500, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information === modified file 'debian/changelog' --- a/debian/changelog 2009-01-19 12:52:39 + +++ b/debian/changelog 2012-12-24 17:21:12 + @@ -1,3 +1,17 @@ +libtext-levenshtein-perl (0.06~01-2) UNRELEASED; urgency=low + + * Fixed lintian warnings: +- ancient-standards-version: bumped to 3.9.4. +- debian-rules-missing-recommended-target: added build-arch and + build-indep targets. +- patch-system-but-no-source-readme: used 3.0 (quilt) source format + instead of explicitly using quilt. +- wiki-copyright-format-uri: updated debian/copyright to the latest + format. + * Removed dead link from package description. (Closes: #695754) + + -- Dmitry Shachnev mity...@gmail.com Mon, 24 Dec 2012 21:03:33 +0400 + libtext-levenshtein-perl (0.06~01-1) unstable; urgency=low * Initial Release. (Closes: #512267) === modified file 'debian/control' --- a/debian/control 2009-01-19 12:52:39 + +++ b/debian/control 2012-12-24 16:51:02 + @@ -1,11 +1,11 @@ Source: libtext-levenshtein-perl Section: perl Priority: optional -Build-Depends: debhelper (= 7), quilt +Build-Depends: debhelper (= 7) Build-Depends-Indep: perl (= 5.6.0-12) Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Uploaders: Ryan Niebur ryanrya...@gmail.com -Standards-Version: 3.8.0 +Standards-Version: 3.9.4 Homepage: http://search.cpan.org/dist/Text-Levenshtein/ Vcs-Svn: svn://svn.debian.org/pkg-perl/trunk/libtext-levenshtein-perl/ Vcs-Browser: http://svn.debian.org/viewsvn/pkg-perl/trunk/libtext-levenshtein-perl/ @@ -18,5 +18,4 @@ edit distance is a measure of the degree of proximity between two strings. This distance is the number of substitutions, deletions or insertions (edits) needed to transform one string into the other one (and vice versa). - When two strings have distance 0, they are the same. A good point to start - is: http://www.merriampark.com/ld.htm + When two strings have distance 0, they are the same. === modified file 'debian/copyright' --- a/debian/copyright 2009-01-19 12:52:39 + +++ b/debian/copyright 2012-12-24 17:14:12 + @@ -1,17 +1,16 @@ -Format-Specification: -http://wiki.debian.org/Proposals/CopyrightFormat?action=recallrev=196 -Upstream-Maintainer: Dree Mistrut d...@friul.it +Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Upstream-Contact: Dree Mistrut d...@friul.it Upstream-Source: http://search.cpan.org/dist/Text-Levenshtein/ Upstream-Name: Text-Levenshtein Files: * Copyright: Copyright 2002,2004,2008 Dree Mistrut d...@friul.it -Licenses: GPL-1+ | Artistic +License: GPL-1+ or Artistic License-Alias: Perl Files: debian/* Copyright: 2009, Ryan Niebur ryanrya...@gmail.com -License: Artistic | GPL-1+ +License: Artistic or GPL-1+ License: Artistic This program is free software; you can redistribute it and/or modify === modified file 'debian/rules' --- a/debian/rules 2009-01-19 12:52:39 + +++ b/debian/rules 2012-12-24 16:55:17 + @@ -1,13 +1,13 @@ #!/usr/bin/make -f -include /usr/share/quilt/quilt.make +build-arch: -build: build-stamp -build-stamp: $(QUILT_STAMPFN) +build-indep build: build-stamp +build-stamp: dh build touch $@ -clean: unpatch +clean: dh $@ install: install-stamp === added directory 'debian/source' === added file 'debian/source/format' --- a/debian/source/format 1970-01-01 00:00:00 + +++ b/debian/source/format 2012-12-24 16:52:47 + @@ -0,0 +1,1 @@ +3.0 (quilt)
Bug#681227: [PATCH] Allow bootdev to be dummy
Matt Kraai kr...@ftbfs.org (23/12/2012): On Sun, Dec 23, 2012 at 02:47:04PM -0800, Matt Kraai wrote: The workaround for 681227 prevents grub-installer from trying to install to devices that don't exist. This breaks installations on systems that use grub-efi or grub-yeeloong, since they set the device to dummy. This patch fixes the workaround to allow this value. I've gone ahead and committed this. I hope that's OK. If you'd like me to revert it, let me know. It might be a good idea to include this in the release, else grub-efi and grub-yeeloong won't work. Thanks for the info and for the patch; I'll try and get Steve to make sure EFI things work for the next release, since I've got no such setups to perform tests on. Mraw, KiBi. signature.asc Description: Digital signature
Bug#696615: grub2: no possibility to install from usb media
Control: tag -1 confirmed Hi Gert, Gert Schulte g...@trash-mail.com (24/12/2012): Dear Maintainer, Installing from usb with mini.iso in expert mode and normal user mode. Grub2 wants to install in /dev/sda, which is the MBR of the install media and luckily fails. (Last year it did even overwrite the install media). There is no option to select any different installation location for grub which leads to non-bootable systems for many users. I had to chroot into my fresh installation to install grub2. Sorry, this did always happen the last months with several mini.iso on several systems but I did not get to report it. Please have the install choose the right MBR (e.g. the HD you installed the system on) and have an option to choose a different location for expert modus and for normal user modus if installation fails. Thanks I must say I've been trying to reproduce some issues with grub-install vs. MBR lately, and I think there are basically two of them: one with non-sensical strings, which Wouter has been trying to diagnose, and finally worked around: http://packages.qa.debian.org/g/grub-installer/news/20121216T164729Z.html and the one where the wrong /dev/sdFOO gets chosen. I've just tried the following, instead of using some mini.iso (or any official iso) in a CD-Rom drive: - convert it to a VDI image: VBoxManage convertfromraw dest/netboot/gtk/mini.iso dest/netboot/gtk/mini.vdi - attach the resulting VDI image to SATA port 0 in virtualbox. - use guided partitioning, everything in a single partition, into /dev/sdb (SATA port 1) - enjoy the attempted “grub-install /dev/sda” call. I'll be trying to fix that before rc1. Thanks for the reminder/bug report. Mraw, KiBi. signature.asc Description: Digital signature
Bug#696640: python-pyvorbis: pyvorbis causes crashes when reading vorbis files
Package: python-pyvorbis
Version: 1.5-1.1
Severity: important
Dear Maintainer,
pyvorbis causes crashes due to an override of the callback to ov_read. I guess
the actual severity should be grave. More details here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670062#10
I built a patched revision of pyvorbis and I can confirm it works. Here a
little test:
--8---8---8---8-
#!/usr/bin/python
import ogg.vorbis
file = ogg.vorbis.VorbisFile('song.ogg')
(data, bytes, bit) = file.read(4096)
--8---8---8---8-
Thanks!
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.6.0-11.dmz.1-liquorix-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-pyvorbis depends on:
ii libc6 2.13-37
ii libvorbis0a 1.3.2-1.3
ii libvorbisenc2 1.3.2-1.3
ii libvorbisfile3 1.3.2-1.3
ii python 2.7.3-3
ii python-ogg 1.3+repack-5+b2
ii python-support 1.0.15
python-pyvorbis recommends no packages.
Versions of packages python-pyvorbis suggests:
pn python-pyvorbis-dbg none
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696640: python-pyvorbis: pyvorbis causes crashes when reading vorbis files
Severity: grave -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696641: fofix: The patch no_numeric_module breaks fofix
Package: fofix Version: 3.121-2 Severity: important Severity: grave Dear Maintainer, the patch no_numeric_module breaks fofix. More details here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670062#10 The problem is caused by the wrong code indentation caused by commenting the if body leaving the else body alone (thus the code inside is not global anymore). Removing leading spaces fixes the issue. Please note that fixing the patch would make emerge a grave bug in pyvorbis (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696640). Thanks -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6.0-11.dmz.1-liquorix-amd64 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fofix depends on: ii python2.7.3-3 ii python-imaging1.1.7-4 ii python-numpy 1:1.6.2-1 ii python-opengl 3.0.1-1 ii python-pygame 1.9.1release+dfsg-7 ii python-pysqlite2 2.6.3-3 ii python-support1.0.15 Versions of packages fofix recommends: ii python-ogg 1.3+repack-5+b2 ii python-pyaudio 0.2.4-2+b1 ii python-pyvorbis 1.5-1.1 Versions of packages fofix suggests: pn python-psyco 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#683847: unblock: sgml-base/1.26+nmu4
Hello, On 24.12.2012 17:50, Adam D. Barratt wrote: On 09.10.2012 08:10, Helmut Grohne wrote: On Tue, Oct 09, 2012 at 09:15:32AM +0200, Raphael Hertzog wrote: On Mon, 08 Oct 2012, Helmut Grohne wrote: 1) Add a pre-dependency on dpkg such that dpkg is already upgraded before deconfiguring sgml-base. This does not guarantee to solve the issue, because the old dpkg may still be running, but it makes it highly unlikely. IIRC when apt upgrades dpkg, it configures it immediately so that any package processed after dpkg is guaranteed to be processed by the upgraded dpkg. Thanks for the explanation. Do you also know whether aptitude and cupt show the same behaviour? CCing the relevant maintainers. Thanks for caring. As for (lib)cupt, newest/latest dpkg is invoked for every new action group. Dpkg is essential, therefore it cannot have circular dependencies, therefore it's guaranteed to be the only package in the action group. In other words, I believe any package processed after dpkg is guaranteed to be processed by the upgraded dpkg is true. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696184: fail2ban: CVE-2012-5642: input variable quoting flaw on matches content
for better or worse -- uploaded 0.8.6-3wheezy1 now. I will let it boil for few days to see if nothing got screwed up, and then will request unblock cheers, On Mon, 24 Dec 2012, Moritz Mühlenhoff wrote: But indeed -- wheezy should get a patched version. Meanwhile -- anyone in need to run fail2ban on their boxes -- use 0.8.8 from sid or backports from neuro.debian.net repository Can you please upload a minimal fix to unstable and ask the release managers for an unblock? -- 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#553898: dogtail: Should this package be orphaned?
Hi Andrew, On Sun, Dec 16, 2012 at 09:37:02PM -0500, Andrew Starr-Bochicchio wrote: While reviewing some packages, your package came up as a package that should maybe be orphaned by its maintainer, because: * Out of date with upstream. * Buggy. (1 RC bug). * NPOASR. (Never part of a stable release). * Low popcon. If you think that it should be removed from Debian instead of being orphaned, please reply to this bug and tell so. If you disagree and want to continue to maintain this package, please close this bug and do an upload also fixing the other issues. I just came across this package. It's been three years since this bug was reported with no response from the maintainer. Nor have there been any maintainer uploads of the package in this time. There are also unanswered bugs that are even older than this. Though the maintainer is not completely MIA. He has uploaded other packages within the last year. [1] The package is no longer RC-buggy and /has/ been part of a stable release, though this is only because of the action of NMUers. I've added them to Cc: Mehdi, Bastian, do you have any personal interest in the dogtail package, and opinion on whether it should be orphaned? If it were orphaned, would either of you be interested in adopting it? I certainly don't think low popcon is an argument for orphaning the package - it might be an argument for removing the package, but isn't a very strong one by itself. Likewise, unanswered non-RC bugs are not by themselves a reason for orphaning a package. However, there's also bug #585287 which has gone unanswered and may actually be a serious issue in the package. José Carlos, are you still interested in maintaining dogtail? You haven't uploaded it in 6 years, and it does seem to be in need of attention. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#696634: [Pkg-samba-maint] Bug#696634: samba-common: logfile log.%m no longer supported in samba4
Quoting Ivo De Decker (ivo.dedec...@ugent.be): package: samba-common version: 2:3.6.6-3 Hi, As noted in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696149#15, samba4 no longer supports logging to log.%m, so we should provide a new default logfile in smb.conf. I missed that decision from upstream but, at first glance, it's a quite poor one: many setups (include all mine) use this to have one logfile per client machine. Weird that backwards compatibility is not kept. signature.asc Description: Digital signature
Bug#696639: libtext-levenshtein-perl: Patch to fix lintian warnings
I didn't notice that the package has a git repository. Attached an updated patch against git master. -- Dmitry Shachnev From 3114415e83005910751c723702a5318a1d9fcc08 Mon Sep 17 00:00:00 2001 From: Dmitry Shachnev mity...@gmail.com Date: Mon, 24 Dec 2012 22:33:20 +0400 Subject: [PATCH] Fixed lintian warnings (Closes: #696639). - ancient-standards-version: bumped to 3.9.4. - debian-rules-missing-recommended-target: added build-arch and build-indep targets. - wiki-copyright-format-uri: updated debian/copyright to the latest format. Also, removed dead link from package description (Closes: #695754). --- debian/changelog |9 + debian/control |5 ++--- debian/copyright |9 - debian/rules |3 ++- 4 files changed, 17 insertions(+), 9 deletions(-) diff --git a/debian/changelog b/debian/changelog index 88c8660..965bb54 100644 --- a/debian/changelog +++ b/debian/changelog @@ -15,6 +15,15 @@ libtext-levenshtein-perl (0.06~01-2) UNRELEASED; urgency=low [ Ansgar Burchardt ] * debian/control: Convert Vcs-* fields to Git. + [ Dmitry Shachnev ] + * Fixed lintian warnings (Closes: #696639): +- ancient-standards-version: bumped to 3.9.4. +- debian-rules-missing-recommended-target: added build-arch and + build-indep targets. +- wiki-copyright-format-uri: updated debian/copyright to the latest + format. + * Removed dead link from package description (Closes: #695754). + -- Ryan Niebur r...@debian.org Fri, 25 Sep 2009 00:26:46 -0700 libtext-levenshtein-perl (0.06~01-1) unstable; urgency=low diff --git a/debian/control b/debian/control index cc72a46..8969485 100644 --- a/debian/control +++ b/debian/control @@ -5,7 +5,7 @@ Build-Depends: debhelper (= 7), quilt Build-Depends-Indep: perl Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Uploaders: Ryan Niebur r...@debian.org -Standards-Version: 3.8.0 +Standards-Version: 3.9.4 Homepage: http://search.cpan.org/dist/Text-Levenshtein/ Vcs-Git: git://git.debian.org/pkg-perl/packages/libtext-levenshtein-perl.git Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libtext-levenshtein-perl.git @@ -18,5 +18,4 @@ Description: implementation of the Levenshtein edit distance edit distance is a measure of the degree of proximity between two strings. This distance is the number of substitutions, deletions or insertions (edits) needed to transform one string into the other one (and vice versa). - When two strings have distance 0, they are the same. A good point to start - is: http://www.merriampark.com/ld.htm + When two strings have distance 0, they are the same. diff --git a/debian/copyright b/debian/copyright index 9aa07af..073e081 100644 --- a/debian/copyright +++ b/debian/copyright @@ -1,17 +1,16 @@ -Format-Specification: -http://wiki.debian.org/Proposals/CopyrightFormat?action=recallrev=196 -Upstream-Maintainer: Dree Mistrut d...@friul.it +Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Upstream-Contact: Dree Mistrut d...@friul.it Upstream-Source: http://search.cpan.org/dist/Text-Levenshtein/ Upstream-Name: Text-Levenshtein Files: * Copyright: Copyright 2002,2004,2008 Dree Mistrut d...@friul.it -Licenses: GPL-1+ | Artistic +License: GPL-1+ or Artistic License-Alias: Perl Files: debian/* Copyright: 2009, Ryan Niebur r...@debian.org -License: Artistic | GPL-1+ +License: Artistic or GPL-1+ License: Artistic This program is free software; you can redistribute it and/or modify diff --git a/debian/rules b/debian/rules index d9229f5..3b3e4a6 100755 --- a/debian/rules +++ b/debian/rules @@ -1,8 +1,9 @@ #!/usr/bin/make -f include /usr/share/quilt/quilt.make +build-arch: -build: build-stamp +build-indep build: build-stamp build-stamp: $(QUILT_STAMPFN) dh build touch $@ -- 1.7.10.4
Bug#695852: unblock: rhash/1.2.9-8
Dear release team, It's the best time to unblock current stable rhash/1.2.9-8 now [1], cause I'm going to upload RHash release 1.2.10 to NEW with new features (e.g. php bindings). After it go through NEW, the next chance for unblocking will be only after 10 day period and when all rhash* packages smoothly compile on all platforms. With best wishes, Aleksey Kravchenko Maintainer of RHash package. [1] http://bugs.debian.org/695852 signature.asc Description: OpenPGP digital signature
Bug#672524: bitcoin: FTBFS[any-i386]: testsuite errors
Hi! Petter Reinholdtsen p...@hungry.com writes: I just tried to build the source of version 0.7.2-1 in Wheezy, and the test suite completed without any errors as far as I could tell. This was on a i686 installation. Is this bug fixed in the new upstream version? We'll see as soon as it builds on the buildds I'd say. Regards Christoph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696642: ifupdown: fails to bring up eth0.xx alias in bridge/vlan setup
Package: ifupdown Version: 0.7.5 Severity: normal Dear Maintainer, I am using Debian as the host OS in a KVM virtualization environment. In testing Wheezy, I've discovered the following issue where an ethernet alias is not brought up, and then a bridge alias is created rather than a new bridge. Also, the bridge alias is set up for a vlan rather than just the intended ethernet alias. To illustrate, I have set up squeeze and wheezy the same way and included output. Both machines installed with base+ssh server in tasksel with thees packages installed afterward: vlan bridge-utils qemu-kvm qemu-utils libvirt-bin ## interfaces file. except for IP, exact same on both machines. auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual auto eth0.4094 iface eth0.4094 inet manual vlan_raw_device eth0 auto br0 iface br0 inet static address 10.205.16.8 # 8 == wheezy, 9 == squeeze netmask 255.255.248.0 gateway 10.205.16.1 bridge_ports eth0 bridge_stp off bridge_fd 0 bridge_maxwait 0 auto br0.4094 iface br0.4094 inet manual bridge_ports eth0.4094 bridge_stp off bridge_fd 0 bridge_maxwait 0 Squeeze: expected outcome; vms added to br0 and br0.4094 work as expected. root@squeeze:~# ifconfig br0 Link encap:Ethernet HWaddr 00:1a:4b:33:f8:b0 inet addr:10.205.16.9 Bcast:10.205.23.255 Mask:255.255.248.0 inet6 addr: fe80::21a:4bff:fe33:f8b0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:194 errors:0 dropped:0 overruns:0 frame:0 TX packets:81 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:16684 (16.2 KiB) TX bytes:9842 (9.6 KiB) br0.4094 Link encap:Ethernet HWaddr 00:1a:4b:33:f8:b0 inet6 addr: fe80::21a:4bff:fe33:f8b0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1450 (1.4 KiB) TX bytes:468 (468.0 B) eth0 Link encap:Ethernet HWaddr 00:1a:4b:33:f8:b0 inet6 addr: fe80::21a:4bff:fe33:f8b0/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:1524 errors:0 dropped:0 overruns:0 frame:0 TX packets:93 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:203495 (198.7 KiB) TX bytes:11402 (11.1 KiB) Interrupt:16 Memory:f600-f6012800 eth0.4094 Link encap:Ethernet HWaddr 00:1a:4b:33:f8:b0 inet6 addr: fe80::21a:4bff:fe33:f8b0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1450 (1.4 KiB) TX bytes:936 (936.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:14 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1078 (1.0 KiB) TX bytes:1078 (1.0 KiB) root@squeeze:~# brctl show bridge name bridge id STP enabled interfaces br0 8000.001a4b33f8b0 no eth0 br0.40948000.001a4b33f8b0 no eth0.4094 root@squeeze:~# cat /proc/net/vlan/config VLAN Dev name| VLAN ID Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD eth0.4094 | 4094 | eth0 root@squeeze:~# Wheezy: unexpected outcome; eth0.4094 isn't up, and also br0.4094 is not actually a bridge (see brctl output) root@wheezy:~# ifconfig br0 Link encap:Ethernet HWaddr 00:1c:c4:5d:53:d6 inet addr:10.205.16.8 Bcast:10.205.23.255 Mask:255.255.248.0 inet6 addr: fe80::21c:c4ff:fe5d:53d6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:375 errors:0 dropped:0 overruns:0 frame:0 TX packets:80 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25089 (24.5 KiB) TX bytes:8678 (8.4 KiB) br0.4094 Link encap:Ethernet HWaddr 00:1c:c4:5d:53:d6 inet6 addr: fe80::21c:c4ff:fe5d:53d6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:578 (578.0 B) eth0 Link encap:Ethernet HWaddr 00:1c:c4:5d:53:d6 UP BROADCAST
Bug#696615: grub2: no possibility to install from usb media
Cyril Brulebois k...@debian.org (24/12/2012): I've just tried the following, instead of using some mini.iso (or any official iso) in a CD-Rom drive: - convert it to a VDI image: VBoxManage convertfromraw dest/netboot/gtk/mini.iso dest/netboot/gtk/mini.vdi - attach the resulting VDI image to SATA port 0 in virtualbox. - use guided partitioning, everything in a single partition, into /dev/sdb (SATA port 1) - enjoy the attempted “grub-install /dev/sda” call. I'll be trying to fix that before rc1. Here's what happens in grub-installer, with comments inline: | # Try to avoid using (hd0) as a boot device name. Something which can be | # turned into a stable by-id name is better. | default_bootdev_os=$($chroot $ROOT grub-mkdevicemap --no-floppy -m - | head -n1 | cut -f2) Notice the head -n1 here. If you're booting from /dev/sda, that's what you get, no matter what. For reference, here's what it looks like for two disks: (hd0) /dev/disk/by-id/ata-VBOX_HARDDISK_id1-id2 (hd1) /dev/disk/by-id/ata-VBOX_HARDDISK_id3-id4 | if [ $default_bootdev_os ]; then | default_bootdev=$($chroot $ROOT readlink -f $default_bootdev_os) That one turns the former top line into: /dev/sda | else | default_bootdev=(hd0) | fi | | # Set a sensible default boot device, so that we aren't installing GRUB to | # installation media which may be removed later. The disk containing /cdrom | # is very unlikely to be a sensible default. If we had to fall back to | # (hd0), then we can't tell exactly which disk that is, but if /cdrom seems | # to be a USB stick then (hd0) may not be safe. If we hit either of those | # checks, then try the disk containing /boot instead. | # The same goes for /hd-media, so avoid installing there as well. | cdsrc=$(mount | grep on /cdrom | cut -d' ' -f1) | cdfs=$(mount | grep on /cdrom | cut -d' ' -f5) | hdsrc=$(mount | grep on /hd-media | cut -d' ' -f1) Unfortunately, that kind of filtering can't really work for the boot from USB case, since no /dev/sda shows up in mount's output (or in /proc/mounts). All we have about it is presumably: rootfs / rw 0 0 which isn't exactly sufficient. Otherwise, we could just insert some “grep -v $foo” before the head/cut pair in the first line I quoted. Another way I see would be: 1. use /etc/fstab in /target to see whether there's a /boot there, and fall back to / if needed. 2. use readlink on /dev/disk/by-uuid/$UUID to get the appropriate partition (say /dev/sdb1 for a full disk installation in my case), and get back to the actual disk (/dev/sdb). 3. use that as the default. Let's see whether a big red man pops up tonight with a clever(er) idea. Mraw, KiBi. signature.asc Description: Digital signature
Bug#661018: FTBS due to new freexl
Control: fixed -1 3.1.0b-1 I'm marking that version as fixed because 3.0.1-1 never made it into the archive. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695852: unblock: rhash/1.2.9-8
On 24.12.2012 18:48, Aleksey Kravchenko wrote: It's the best time to unblock current stable rhash/1.2.9-8 now [1], cause I'm going to upload RHash release 1.2.10 to NEW with new features (e.g. php bindings). After it go through NEW, the next chance for unblocking will be only after 10 day period and when all rhash* packages smoothly compile on all platforms. No. Such changes wouldn't be suitable for an unblock, so the next chance (if the existing package hadn't migrated first) would be after the release or via t-p-u. Intentionally closing off the possibility to use unstable for fixes to your package seems a disadvantage from a maintenance perspective imo; ymmv, clearly. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696643: virtualbox-qt: inaccurate error message when fiddling with VDI files
Package: virtualbox-qt
Version: 4.1.18-dfsg-1.1
Severity: normal
Hi folks,
I'm usually using virtualbox to perform my d-i tests, with mini.iso most
of the time. This works fine, and stopping/starting the VM is sufficient
to get the new mini.iso taken into account.
I've recently needed to use a hard disk image instead, so I've used the
following command to generate a VDI file from the mini.iso image:
VBoxManage convertfromraw dest/netboot/gtk/mini.iso dest/netboot/gtk/mini.vdi
After a rebuild, I ran it again (removing the old one since VBoxManage
complained about its existing already), and virtualbox was unhappy; I'm
copying-pasting manually since the dialog doesn't allow for text
selection…
| VirtualBox - Error
|
| Failed to open a session for the virtual machine bwheezy-test/b
|
| UUID i{foo}/i of the medium b'…/dest/netboot/gtk/mini.vdi'/b
| does not match the value i{bar}/i stored in the media registry
| (b'/home/kibi/.VirtualBox/VirtualBox.xml'/b).
That's not true; my VMs are stored in ~/vms, and the media registry
appears to be VM-specific, with the {bar} value being stored in:
~/vms/wheezy-test/wheezy-test.vbox
under this path:
Virtualbox/Machine/MediaRegistry/HardDisks/HardDisk
Mraw,
KiBi.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages virtualbox-qt depends on:
ii dpkg 1.16.9
ii libc6 2.13-37
ii libgcc1 1:4.7.2-4
ii libgl1-mesa-glx [libgl1] 8.0.5-3
ii libqt4-network4:4.8.2+dfsg-2
ii libqt4-opengl 4:4.8.2+dfsg-2
ii libqtcore44:4.8.2+dfsg-2
ii libqtgui4 4:4.8.2+dfsg-2
ii libsdl1.2debian 1.2.15-5
ii libstdc++64.7.2-4
ii libx11-6 2:1.5.0-1
ii libxcursor1 1:1.1.13-1
ii libxext6 2:1.3.1-2
ii libxinerama1 2:1.1.2-1
ii virtualbox4.1.18-dfsg-1.1
virtualbox-qt recommends no packages.
virtualbox-qt 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#696608: unlock: lilypond/2.14.2-4 (preapproval)
Control: tags -1 + confirmed On 23.12.2012 21:31, Don Armstrong wrote: In making a fix to the RC bug #684817, I also fixed a problem in disabling optimization when noopt is present, and a patch which fixes an install-info warning which had previously collected. I'd be okay with accepting those. Please go ahead; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696560: unblock: x2goclient/3.99.2.1-2 (pre-upload approval)
Control: tags -1 + confirmed On 22.12.2012 20:58, Mike Gabriel wrote: This is a pre-upload approval for transition of x2goclient src:package 3.99.2.1-2 to wheezy. The package has not been uploaded, yet. The upload closes two RC bugs (grave) and closes two other important bugs. The upload also fixes the hardening compiler/linker options in the project's main Makefile. As bonus an example file has been added that shows the usage of x2goplugin: /debian/examples/x2goplugin.html. These all sound like changes that, according to your descriptions, meet the currently published criteria so don't really need any sort of pre-approval? On a side note, including debdiffs as attachments rather than inline makes review somewhat easier. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696516: unblock: lemonldap-ng/1.1.2-5+deb70u1
Control: tags -1 -moreinfo +confirmed On 23.12.2012 17:38, Xavier wrote: Le 23/12/2012 13:31, Adam D. Barratt a écrit : On 22.12.2012 07:34, Xavier Guimard wrote: This release will contain : * the security fix to close #696329 * the pt_BR.po file to close #693366 It looks like #696329 isn't fixed in unstable yet? What's the progress on that? In general we'd expect fixes going via t-p-u to have been applied to unstable first where appropriate, to give them some more exposure / testing. [...] gregoa has done it just now (there were many other changes to check). Thanks. Please go ahead. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#553898: dogtail: Should this package be orphaned?
I will do a proper orphan of a bunch of packages soon, as I am completely our of time. But in the meanwhile take this mail as an orphan bug report in wnpp. Thanks and sorry for the inconvenience. And merry Xmas. El 24/12/2012 19:30, Steve Langasek vor...@debian.org escribió: Hi Andrew, On Sun, Dec 16, 2012 at 09:37:02PM -0500, Andrew Starr-Bochicchio wrote: While reviewing some packages, your package came up as a package that should maybe be orphaned by its maintainer, because: * Out of date with upstream. * Buggy. (1 RC bug). * NPOASR. (Never part of a stable release). * Low popcon. If you think that it should be removed from Debian instead of being orphaned, please reply to this bug and tell so. If you disagree and want to continue to maintain this package, please close this bug and do an upload also fixing the other issues. I just came across this package. It's been three years since this bug was reported with no response from the maintainer. Nor have there been any maintainer uploads of the package in this time. There are also unanswered bugs that are even older than this. Though the maintainer is not completely MIA. He has uploaded other packages within the last year. [1] The package is no longer RC-buggy and /has/ been part of a stable release, though this is only because of the action of NMUers. I've added them to Cc: Mehdi, Bastian, do you have any personal interest in the dogtail package, and opinion on whether it should be orphaned? If it were orphaned, would either of you be interested in adopting it? I certainly don't think low popcon is an argument for orphaning the package - it might be an argument for removing the package, but isn't a very strong one by itself. Likewise, unanswered non-RC bugs are not by themselves a reason for orphaning a package. However, there's also bug #585287 which has gone unanswered and may actually be a serious issue in the package. José Carlos, are you still interested in maintaining dogtail? You haven't uploaded it in 6 years, and it does seem to be in need of attention. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
Bug#696516: unblock: lemonldap-ng/1.1.2-5+deb70u1
On Mon, 24 Dec 2012 20:04:32 +, Adam D. Barratt wrote: It looks like #696329 isn't fixed in unstable yet? What's the progress on that? In general we'd expect fixes going via t-p-u to have been applied to unstable first where appropriate, to give them some more exposure / testing. [...] gregoa has done it just now (there were many other changes to check). Thanks. Please go ahead. Thank you. Upload (as clarified on IRC) as 1.1.2-5+deb7u1. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Nick Cave The Bad Seeds: The Lyre Of Orpheus signature.asc Description: Digital signature
Bug#696644: assertion failure on kfreebsd
Package: darktable Version: 1.1.1-1 Severity: normal Hi! When starting darktable I get darktable: /build/buildd-darktable_1.1.1-1-kfreebsd-amd64-aheTMo/darktable-1.1.1/src/control/control.c:886: dt_control_run_job_res: Assertion `res 8 res = 0' failed. about 50% of the time. I'll send more information as I debug this further Regards Christoph -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 10.0-0-amd64 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 darktable depends on: ii gtk2-engines 1:2.20.2-2 ii libatk1.0-0 2.4.0-2 ii libc0.1 2.13-37 ii libcairo2 1.12.2-2 ii libcurl3-gnutls 7.26.0-1 ii libexiv2-12 0.23-1 ii libflickcurl0 1.22-1 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.2-4 ii libgdk-pixbuf2.0-02.26.1-1 ii libgl1-mesa-glx [libgl1] 8.0.5-3 ii libglib2.0-0 2.33.12+really2.32.4-3 ii libglu1-mesa [libglu1]8.0.5-3 ii libgnome-keyring0 3.4.1-1 ii libgomp1 4.7.2-4 ii libgphoto2-2 2.4.14-2 ii libgphoto2-port0 2.4.14-2 ii libgtk2.0-0 2.24.10-2 ii libice6 2:1.0.8-2 ii libilmbase6 1.0.1-4 ii libjpeg8 8d-1 ii libjs-prototype 1.7.0-2 ii libjs-scriptaculous 1.9.0-2 ii libjson-glib-1.0-00.14.2-1 ii liblcms2-22.2+git20110628-2.2 ii liblensfun0 0.2.5-2 ii libopenexr6 1.6.1-6 ii libpango1.0-0 1.30.0-1 ii libpng12-01.2.49-1 ii librsvg2-22.36.1-1 ii libsdl1.2debian 1.2.15-5 ii libsm62:1.2.1-2 ii libsoup2.4-1 2.38.1-2 ii libsqlite3-0 3.7.13-1 ii libstdc++64.7.2-4 ii libtiff5 4.0.2-5 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxml2 2.8.0+dfsg1-7 ii zlib1g1:1.2.7.dfsg-13 darktable recommends no packages. darktable 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#696645: irssi: please add ability to modify server settings
Package: irssi Version: 0.8.15-2 Severity: wishlist It's very inconvenient to alter server settings. The /server add... command must be composed by reconstructing all the settings for the existing server, which in some cases requires tracking down the password for the server. I propose a new command /server amend. It should maintain all existing settings and override parameters supplied to the amend command. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages irssi depends on: ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libncurses55.7+20100313-5shared libraries for terminal hand ii libperl5.105.10.1-17squeeze4 shared Perl library ii libssl0.9.80.9.8o-4squeeze13 SSL shared libraries ii perl 5.10.1-17squeeze4 Larry Wall's Practical Extraction ii perl-base [perlapi-5.1 5.10.1-17squeeze4 minimal Perl system irssi recommends no packages. Versions of packages irssi suggests: pn irssi-scripts none (no description available) -- 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#696646: icedtea-7-plugin not loading applets (mipsel loongson-2f).
Package: icedtea-7-plugin Version: 1.3.1-1 Severity: important Dear Maintainer, Some time back icedtea-7-plugin was working correctly, however when moving to the latest1.3.1-1 version, also some time back, bank account applets no longer load. I had to revert to icedtea-6-plugin so I can access my bank accounts which depend upon java applets. Weird thing, everything was working before, :-( Any ways, I've seen bugs relates to update-alternatives, but so far everything points to java7, and even so, the icedtea-6-plugin still works while icedtea-7-plugin doesn't: % ls -l /etc/alternatives/ | 'grep' 'java-6' lrwxrwxrwx 1 root root 66 Dec 24 13:54 mozilla-javaplugin.so - /usr/lib/jvm/java-6-openjdk-mipsel/jre/lib/mipsel/IcedTeaPlugin.so % ls -l /etc/alternatives/ | 'grep' 'java-7' lrwxrwxrwx 1 root root 51 Dec 24 12:23 appletviewer - /usr/lib/jvm/java-7-openjdk-mipsel/bin/appletviewer* lrwxrwxrwx 1 root root 61 Dec 24 12:23 appletviewer.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/appletviewer.1.gz lrwxrwxrwx 1 root root 47 Dec 24 12:27 extcheck - /usr/lib/jvm/java-7-openjdk-mipsel/bin/extcheck* lrwxrwxrwx 1 root root 57 Dec 24 12:27 extcheck.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/extcheck.1.gz lrwxrwxrwx 1 root root 43 Dec 24 12:28 idlj - /usr/lib/jvm/java-7-openjdk-mipsel/bin/idlj* lrwxrwxrwx 1 root root 53 Dec 24 12:28 idlj.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/idlj.1.gz lrwxrwxrwx 1 root root 57 Dec 24 12:20 itweb-settings - /usr/lib/jvm/java-7-openjdk-mipsel/jre/bin/itweb-settings* lrwxrwxrwx 1 root root 67 Dec 24 12:20 itweb-settings.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/jre/man/man1/itweb-settings.1.gz lrwxrwxrwx 1 root root 42 Nov 24 15:25 jar - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jar* lrwxrwxrwx 1 root root 52 Nov 24 15:25 jar.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jar.1.gz lrwxrwxrwx 1 root root 48 Nov 24 15:26 jarsigner - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jarsigner* lrwxrwxrwx 1 root root 58 Nov 24 15:26 jarsigner.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jarsigner.1.gz lrwxrwxrwx 1 root root 47 Nov 24 15:23 java - /usr/lib/jvm/java-7-openjdk-mipsel/jre/bin/java* lrwxrwxrwx 1 root root 57 Nov 24 15:23 java.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/jre/man/man1/java.1.gz lrwxrwxrwx 1 root root 44 Nov 24 15:25 javac - /usr/lib/jvm/java-7-openjdk-mipsel/bin/javac* lrwxrwxrwx 1 root root 54 Nov 24 15:25 javac.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/javac.1.gz lrwxrwxrwx 1 root root 46 Nov 24 15:26 javadoc - /usr/lib/jvm/java-7-openjdk-mipsel/bin/javadoc* lrwxrwxrwx 1 root root 56 Nov 24 15:26 javadoc.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/javadoc.1.gz lrwxrwxrwx 1 root root 44 Nov 24 15:27 javah - /usr/lib/jvm/java-7-openjdk-mipsel/bin/javah* lrwxrwxrwx 1 root root 54 Nov 24 15:27 javah.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/javah.1.gz lrwxrwxrwx 1 root root 44 Dec 24 12:29 javap - /usr/lib/jvm/java-7-openjdk-mipsel/bin/javap* lrwxrwxrwx 1 root root 54 Dec 24 12:29 javap.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/javap.1.gz lrwxrwxrwx 1 root root 49 Nov 24 15:27 javaws - /usr/lib/jvm/java-7-openjdk-mipsel/jre/bin/javaws* lrwxrwxrwx 1 root root 59 Nov 24 15:27 javaws.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/jre/man/man1/javaws.1.gz lrwxrwxrwx 1 root root 47 Dec 24 12:28 jconsole - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jconsole* lrwxrwxrwx 1 root root 57 Dec 24 12:28 jconsole.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jconsole.1.gz lrwxrwxrwx 1 root root 42 Dec 24 12:29 jdb - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jdb* lrwxrwxrwx 1 root root 52 Dec 24 12:29 jdb.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jdb.1.gz lrwxrwxrwx 1 root root 48 Dec 24 12:30 jexec - /usr/lib/jvm/java-7-openjdk-mipsel/jre/lib/jexec* lrwxrwxrwx 1 root root 53 Dec 24 12:30 jexec-binfmt - /usr/lib/jvm/java-7-openjdk-mipsel/jre/lib/jar.binfmt lrwxrwxrwx 1 root root 43 Dec 24 12:27 jhat - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jhat* lrwxrwxrwx 1 root root 53 Dec 24 12:27 jhat.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jhat.1.gz lrwxrwxrwx 1 root root 44 Dec 24 12:30 jinfo - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jinfo* lrwxrwxrwx 1 root root 54 Dec 24 12:30 jinfo.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jinfo.1.gz lrwxrwxrwx 1 root root 43 Dec 24 12:30 jmap - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jmap* lrwxrwxrwx 1 root root 53 Dec 24 12:30 jmap.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jmap.1.gz lrwxrwxrwx 1 root root 42 Dec 24 12:30 jps - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jps* lrwxrwxrwx 1 root root 52 Dec 24 12:30 jps.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jps.1.gz lrwxrwxrwx 1 root root 49 Dec 24 12:31 jrunscript - /usr/lib/jvm/java-7-openjdk-mipsel/bin/jrunscript* lrwxrwxrwx 1 root root 59 Dec 24 12:31 jrunscript.1.gz - /usr/lib/jvm/java-7-openjdk-mipsel/man/man1/jrunscript.1.gz lrwxrwxrwx 1 root root 48 Dec 24
Bug#696647: Buffer overflow in filename leads to crash
Package: scantool
Version: 1.21+dfsg-3
Severity: important
Tags: patch
When using SCAN CODES button, the program crashes due to buffer
overflow in filename variable that is limited to only 30
bytes. Unfortunately the Debian location of the support files requires
more than that entire space.
The attached patch expands the hardcoded limit up to FILENAME_MAX -
more than necessary but at least it should no longer cause an
overflow and there is really no advantage of specifying 60 or 256
bytes instead.
This problem does not prevent active reading of sensor parameters, but
it does prevent reading of DTC which is rather core diagnostic feature
of this program.
- Adam
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.6.7+ (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Index: scantool-1.21+dfsg/trouble_code_reader.c
===
--- scantool-1.21+dfsg.orig/trouble_code_reader.c 2009-09-15 22:38:42.0 -0500
+++ scantool-1.21+dfsg/trouble_code_reader.c 2012-12-24 14:37:29.484907208 -0600
@@ -1221,7 +1221,7 @@
{
static PACKFILE *file = NULL;
static char current_code_letter = 0;
- char file_name[30];
+ char file_name[FILENAME_MAX];
if (code_letter == 0)
{
@@ -1238,7 +1238,8 @@
file = NULL;
}
- sprintf(file_name, %s#%ccodes, code_defs_file_name, tolower(code_letter));
+ snprintf(file_name, FILENAME_MAX, %s#%ccodes, code_defs_file_name, tolower(code_letter));
+ file_name[FILENAME_MAX-1] = 0;
packfile_password(PASSWORD);
file = pack_fopen(file_name, F_READ_PACKED);
packfile_password(NULL);
Bug#680704: iceweasel/xulrunner: Loongson-2f mipsel iceweasel/xulrunner hasn't been working since several versions back.
block 680704 by 692053 thanks Hi, On 24/12/12 20:24, Javier Vasquez wrote: It applies a patch though over version 17, which changes the PageShift to 14 for mips: The hangs we both see in iceweasel 10 on loongson-2f seem similar to #692053 on ia64, which was due to non-4K page size. Stefan Schreiber has just come up with a patch for it. If there is a new upload to unstable with that patch we should both re-test. I will test sooner if my netbook seems capable of building iceweasel. http://www.anheng.com.cn/loongson2f/testing/iceweasel/iceweasel17/fix_loongson_PageSize.patch That might fix things for loongson-2f with 16K page size - but do *all* MIPS systems have the same? On ia64 for example it can vary across hardware, so it would be wrong to hard-code it. If it's the same situation on mips(el) too then this seems better: http://www.anheng.com.cn/loongson2f/testing/iceweasel/iceweasel17/Don-t-hardcode-page-size-on-ia64-or-sparc.patch That change (already applied in Debian experimental only for ia64/sparc) should perhaps also apply to mips(el). It seems it might fix the build issue of iceweasel 17 in experimental. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693173: gcc-mingw32: float comparison fails assertion only with -std=c99
reassign 693173 gcc
thanks
Hi Ben,
On Tue, Nov 13, 2012 at 11:33:01PM +, Ben Golightly wrote:
The following three line C programme generates erroneous output when
compiled with i586-mingw32msvc-gcc -std=c99
#include assert.h
float getfloat() { return 12345.6789f; }
int main(void) { assert(12345.6789f == getfloat()); }
When running the generated binary, the assertion is always triggered.
Steps to reproduce:
$ gcc float.c -o float-linux
$ i586-mingw32msvc-gcc float.c -o float
$ i586-mingw32msvc-gcc float.c -o float-c99 -std=c99
$ ./float-linux // works
$ wine ./float // works
$ wine ./float-c99 // outputs Assertion failed!
The following causes the assertion too, using gcc 4.7.2:
% gcc -std=c99 float.c -o float-linux-c99
% ./float-linux-c99
float-linux-c99: float.c:3: main: Assertion `12345.6789f == getfloat()' failed.
It seems this bug is not specific to gcc-mingw32, but is either really
a bug in gcc or expected behaviour in C99 (I don't know which).
Incidentally, since you're running unstable, you can use the
i686-w64-mingw32 triplet instead of i586-mingw32msvc; the latter will
be going away at some point...
Regards,
Stephen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696648: lazygal: Lazygal stops working when meets file with EXIF in wrong encoding
Package: lazygal Version: 0.7.4-1 Severity: wishlist I think it would be great to have parameter which says to lazygal to skip such errors (just report). -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lazygal depends on: ii python 2.7.3~rc2-1 ii python-genshi 0.6-3 ii python-imaging 1.1.7-4 ii python-pyexiv2 0.3.2-5 lazygal recommends no packages. Versions of packages lazygal suggests: ii gstreamer0.10-plugins-base 0.10.36-1 pn python-gst0.10 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#696639: Pending fixes for bugs in the libtext-levenshtein-perl package
tag 696639 + pending tag 695754 + pending thanks Some bugs in the libtext-levenshtein-perl package are closed in revision 0bf359602c63285fcf078781a4d9a5314c8da021 in branch 'master' by Dmitry Shachnev The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libtext-levenshtein-perl.git;a=commitdiff;h=0bf3596 Commit message: Fixed lintian warnings (Closes: #696639). - ancient-standards-version: bumped to 3.9.4. - debian-rules-missing-recommended-target: added build-arch and build-indep targets. - wiki-copyright-format-uri: updated debian/copyright to the latest format. Also, removed dead link from package description (Closes: #695754). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696639: libtext-levenshtein-perl: Patch to fix lintian warnings
On Mon, 24 Dec 2012 22:38:42 +0400, Dmitry Shachnev wrote: I didn't notice that the package has a git repository. Attached an updated patch against git master. Thanks, that's indeed helpful :) I've uploaded a new version with some additional polishing to unstable right now. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Das Internationale Format: Seit Dem Man Mich signature.asc Description: Digital signature
Bug#622960: Does this package still need help
Hello Guys, Has this package been adopted? Is there anyone that needs help? Can we close it if not? -- Regards Martin Naughton
Bug#696424: Possible patch
Hello,
attached is a possible patch for that issue. This is just a starting
point, as I was not able to test the patch myself. Also, I used 660 as
permissions to the file, I'm not sure of whether it's sensible or not.
Please review and test before applying.
HTH anyway,
Mt.
--
Nous avons neuf mois de vie privée avant de naître, ça devrait nous
suffire. -- Heathcote Williams, Actuel n°48, novembre 74.
Initial report (https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-5638)
| The sanlock server creates the /var/log/sanlock.log world writable
| allowing any one on the system to wipe the contents of the log file or
| to store data within the log file (bypassing any quotas applied to
| their account). The affected code (in src/log.c) is:
|
| int setup_logging(void) {
| int fd, rv;
| snprintf(logfile_path, PATH_MAX, %s/%s, SANLK_LOG_DIR,
| SANLK_LOGFILE_NAME);
| logfile_fp = fopen(logfile_path, a+);
This patch was proposed by Martin Quinson, but not really tested as I
don't use sanlock myself. Also, I used 660 as permissions to the file,
I'm not sure of whether it's sensible or not.
Index: sanlock-2.2/src/log.c
===
--- sanlock-2.2.orig/src/log.c 2012-05-07 17:43:52.0 +0200
+++ sanlock-2.2/src/log.c 2012-12-24 22:19:10.437901274 +0100
@@ -252,10 +252,12 @@
snprintf(logfile_path, PATH_MAX, %s/%s, SANLK_LOG_DIR,
SANLK_LOGFILE_NAME);
- logfile_fp = fopen(logfile_path, a+);
- if (logfile_fp) {
- fd = fileno(logfile_fp);
+ fd = open(logfile_path,O_CREAT | O_WRONLY, S_IRUSR|S_IWUSR | S_IRGRP|S_IWGRP);
+ if (fd != -1) {
fcntl(fd, F_SETFD, fcntl(fd, F_GETFD, 0) | FD_CLOEXEC);
+ logfile_fp = fdopen(fd, a+);
+ } else {
+ logfile_fp = NULL;
}
log_ents = malloc(log_num_ents * sizeof(struct entry));
Bug#553898: dogtail: Should this package be orphaned?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/24/2012 07:26 PM, Steve Langasek wrote: The package is no longer RC-buggy and /has/ been part of a stable release, though this is only because of the action of NMUers. I've added them to Cc: Mehdi, Bastian, do you have any personal interest in the dogtail package, and opinion on whether it should be orphaned? If it were orphaned, would either of you be interested in adopting it? I NMUed it only to get the python-apt transition done, iirc. I have no real interest in this package. Regards, - -- Mehdi -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJQ2MgNAAoJEDe1GR0FRlJoPZgH/isyHbSxU6OkRcNrqHkptsQN 3AtRfZecEWl8DR3mbhFAEfEEkNPqY3CgCfw70qu9n9lJPyve0Ll0xedum1KCOdyF 2zZU94b4kEoSUjRLYpbKdh1bElR1YDAOJ670LN735dktQZl+9E3ylM4FcWUCyWbs JwKuwRUFJiHfVeruB0wML6ou6+gZfNaguRDX+k3LpKtc4qeJgFsFIW7f1NJ/XYKS eilfJEoY7ZsYYCyGgboE9K30xcDDu0TlKNX9Q2v5wnIv7AsbmUfUan7P2QEeqXT2 FBwxyh4MWO2gMtkNieX3njobsn5pKUpPk4sb0hLFGXE+itN0G+JRDtaALVjSHHI= =HthM -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#675345: gnome-shell: Confirmed, backtrace
Package: gnome-shell Version: 3.4.2-4 Followup-For: Bug #675345 Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** gnome-shell freezes randomly for me. When it freezes, the mouse still moves and I can get to virtual terminals as others have noted. Killing gnome-shell and switching back doesn't seem to fix it for me - the new gnome-shell is also frozen. I can replace with metacity and continue working or save state. I fired up gnome-shell with debug symbols in gdb to reproduce the freeze. BACKTRACE Thread 9 (Thread 0x7fffc1bfc700 (LWP 23052)): #0 0x7fffedeff3cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fffee431624 in g_main_context_poll (n_fds=1, fds=0x7fffac00efb0, timeout=-1, context=0x23862b0, priority=optimized out) at /build/glib2.0-7fLB_j/glib2.0-2.33.12+really2.32.4/./glib/gmain.c:3440 #2 g_main_context_iterate (context=context@entry=0x23862b0, block=block@entry=1, dispatch=dispatch@entry=1, self=error reading variable: Unhandled dwarf expression opcode 0xfa) at /build/glib2.0-7fLB_j/glib2.0-2.33.12+really2.32.4/./glib/gmain.c:3141 #3 0x7fffee431744 in g_main_context_iteration (context=0x23862b0, may_block=may_block@entry=1) at /build/glib2.0-7fLB_j/glib2.0-2.33.12+really2.32.4/./glib/gmain.c:3207 #4 0x7fffee431791 in glib_worker_main (data=optimized out) at /build/glib2.0-7fLB_j/glib2.0-2.33.12+really2.32.4/./glib/gmain.c:4879 #5 0x7fffee453f45 in g_thread_proxy (data=0x7fffac00dcf0) at /build/glib2.0-7fLB_j/glib2.0-2.33.12+really2.32.4/./glib/gthread.c:801 #6 0x7fffee1d2d9b in start_thread (arg=0x7fffc1bfc700) at pthread_create.c:311 #7 0x7fffedf09b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 6 (Thread 0x7fffcadf5700 (LWP 23005)): #0 0x7fffedeff3cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fffee962e3f in poll_func (ufds=0x7fffc4001460, nfds=2, timeout=-1, userdata=0x9ab5a0) at pulse/thread-mainloop.c:69 #2 0x7fffee95439c in pa_mainloop_poll (m=m@entry=0x9ab800) at pulse/mainloop.c:873 #3 0x7fffee9549f9 in pa_mainloop_iterate (m=m@entry=0x9ab800, block=block@entry=1, retval=retval@entry=0x0) at pulse/mainloop.c:955 #4 0x7fffee954ab0 in pa_mainloop_run (m=0x9ab800, retval=retval@entry=0x0) at pulse/mainloop.c:973 #5 0x7fffee962def in thread (userdata=0x9a32d0) at pulse/thread-mainloop.c:88 #6 0x7fffe60d4443 in internal_thread_func (userdata=0x9a34b0) at pulsecore/thread-posix.c:83 #7 0x7fffee1d2d9b in start_thread (arg=0x7fffcadf5700) at pthread_create.c:311 #8 0x7fffedf09b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 5 (Thread 0x7fffcfffe700 (LWP 23002)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:168 #1 0x763f5c90 in PR_WaitCondVar () from /usr/lib/x86_64-linux-gnu/libnspr4.so #2 0x76ad5a47 in ?? () from /usr/lib/libmozjs185.so.1.0 #3 0x763fb3b3 in ?? () from /usr/lib/x86_64-linux-gnu/libnspr4.so #4 0x7fffee1d2d9b in start_thread (arg=0x7fffcfffe700) at pthread_create.c:311 #5 0x7fffedf09b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 4 (Thread 0x7fffe0957700 (LWP 23001)): #0 0x7fffedeff3cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fffee962e3f in poll_func (ufds=0x7fffd8001460, nfds=2, timeout=-1, userdata=0x879fd0) at pulse/thread-mainloop.c:69 #2 0x7fffee95439c in pa_mainloop_poll (m=m@entry=0x880550) at pulse/mainloop.c:873 #3 0x7fffee9549f9 in pa_mainloop_iterate (m=m@entry=0x880550, block=block@entry=1, retval=retval@entry=0x0) at pulse/mainloop.c:955 #4 0x7fffee954ab0 in pa_mainloop_run (m=0x880550, retval=retval@entry=0x0) at pulse/mainloop.c:973 #5 0x7fffee962def in thread (userdata=0x879b80) at pulse/thread-mainloop.c:88 #6 0x7fffe60d4443 in internal_thread_func (userdata=0x880800) at pulsecore/thread-posix.c:83 #7 0x7fffee1d2d9b in start_thread (arg=0x7fffe0957700) at pthread_create.c:311 #8 0x7fffedf09b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 3 (Thread 0x7fffe135f700 (LWP 22999)): #0 0x7fffedeff3cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fffee431624 in g_main_context_poll (n_fds=1, fds=0x7fffd40010e0, timeout=-1, context=0x86d630, priority=optimized out) at /build/glib2.0-7fLB_j/glib2.0-2.33.12+really2.32.4/./glib/gmain.c:3440 #2 g_main_context_iterate (context=0x86d630, block=block@entry=1, dispatch=dispatch@entry=1, self=error reading variable: Unhandled dwarf
Bug#686502: pxz produces archives broken for busybox's unxz
On Sat, 2012-12-22 at 10:21 -0800, Jonathan Nieder wrote:
What happens if a stream ends at a buffer boundary, followed by
padding? Or if padding doesn't fit in the buffer, for that
matter?
Hope that helps,
Please find attached new debdiff with fix of above mentioned issues.
Cheers,
diff -Nru busybox-1.20.0/debian/changelog busybox-1.20.0/debian/changelog
--- busybox-1.20.0/debian/changelog 2012-09-20 08:32:55.0 +0200
+++ busybox-1.20.0/debian/changelog 2012-12-21 21:59:39.0 +0100
@@ -1,3 +1,10 @@
+busybox (1:1.20.0-7.1) unstable; urgency=low
+
+ * Fix decompression of multi stream XZ compressed files
+(Closes: Bug#bug#686502)
+
+ -- Abou Al Montacir abou.almonta...@sfr.fr Thu, 21 Dec 2012 22:00:00 +0100
+
busybox (1:1.20.0-7) unstable; urgency=low
* set CONFIG_FEATURE_COPYBUF_KB from 4 to 64 for all flavours. This
diff -Nru busybox-1.20.0/debian/patches/fix-unxz-with-multiple-streams.patch busybox-1.20.0/debian/patches/fix-unxz-with-multiple-streams.patch
--- busybox-1.20.0/debian/patches/fix-unxz-with-multiple-streams.patch 1970-01-01 01:00:00.0 +0100
+++ busybox-1.20.0/debian/patches/fix-unxz-with-multiple-streams.patch 2012-12-24 23:12:05.0 +0100
@@ -0,0 +1,74 @@
+Author: Abou Al Montacir abou.almonta...@sfr.fr
+Purpose: Fix decompression of multi stream XZ compressed files
+ (Closes: bug#686502)
+
+--- busybox-1.20.0/archival/libarchive/decompress_unxz.c 2012-12-24 21:21:47.0 +0100
busybox-1.20.0/debian/build/deb/archival/libarchive/decompress_unxz.c 2012-12-24 23:10:35.0 +0100
+@@ -44,6 +44,7 @@
+ struct xz_dec *state;
+ unsigned char *membuf;
+ IF_DESKTOP(long long) int total = 0;
++ enum xz_ret r;
+
+ if (!global_crc32_table)
+ global_crc32_table = crc32_filltable(NULL, /*endian:*/ 0);
+@@ -59,12 +60,10 @@
+ strcpy((char*)membuf, HEADER_MAGIC);
+ iobuf.in_size = HEADER_MAGIC_SIZE;
+ } /* else: let xz code read check it */
+-
+- /* Limit memory usage to about 64 MiB. */
+- state = xz_dec_init(XZ_DYNALLOC, 64*1024*1024);
++ /* First stream is identical to starting a new stream after finishing decoding an old one */
++ r = XZ_STREAM_END;
+
+ while (1) {
+- enum xz_ret r;
+
+ if (iobuf.in_pos == iobuf.in_size) {
+ int rd = safe_read(src_fd, membuf, BUFSIZ);
+@@ -73,9 +72,25 @@
+ total = -1;
+ break;
+ }
++ /* No more bytes in stream. Stop */
++ if (rd == 0) {
++break;
++ }
+ iobuf.in_size = rd;
+ iobuf.in_pos = 0;
+ }
++ if (r == XZ_STREAM_END) {
++ /* Eat padding. Stream never starts with zeros */
++ while ((iobuf.in_pos iobuf.in_size) (iobuf.in[iobuf.in_pos] == 0)) {
++ iobuf.in_pos += 1;
++ }
++ /* Reached end of buffer. Fill it again from stream */
++ if (iobuf.in_pos == iobuf.in_size) {
++continue;
++ }
++ /* Initialize decoder for new stream. Limit memory usage to about 64 MiB. */
++ state = xz_dec_init(XZ_DYNALLOC, 64*1024*1024);
++ }
+ // bb_error_msg(in pos:%d size:%d out pos:%d size:%d,
+ //iobuf.in_pos, iobuf.in_size, iobuf.out_pos, iobuf.out_size);
+ r = xz_dec_run(state, iobuf);
+@@ -87,7 +102,9 @@
+ iobuf.out_pos = 0;
+ }
+ if (r == XZ_STREAM_END) {
+- break;
++ xz_dec_end(state);
++ /* Look for any other streams */
++ continue;
+ }
+ if (r != XZ_OK r != XZ_UNSUPPORTED_CHECK) {
+ bb_error_msg(corrupted data);
+@@ -95,7 +112,6 @@
+ break;
+ }
+ }
+- xz_dec_end(state);
+ free(membuf);
+
+ return total;
diff -Nru busybox-1.20.0/debian/patches/series busybox-1.20.0/debian/patches/series
--- busybox-1.20.0/debian/patches/series 2012-09-19 22:58:00.0 +0200
+++ busybox-1.20.0/debian/patches/series 2012-12-20 21:54:21.0 +0100
@@ -25,3 +25,6 @@
dont-force-no-alignment-for-s390.patch
stop-checking-ancient-kernel-version.patch
+
+# http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686502
+fix-unxz-with-multiple-streams.patch
signature.asc
Description: This is a digitally signed message part
Bug#696649: gnome-shell: Alt-mouse-1-down no longer moves window
Package: gnome-shell Version: 3.4.2-4 Severity: normal Dear Maintainer, Recent upgrade of gnome-shell seems to have removed Alt-mouse-1-down as a shortcut to move a window. This has worked for as long as I can remember and is rather irritating to lose. I can't set this as a shortcut through the gnome keyboard settings dialog. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-3 ii gconf-service3.2.5-1+build1 ii gir1.2-accountsservice-1.0 0.6.21-7 ii gir1.2-atk-1.0 2.4.0-2 ii gir1.2-caribou-1.0 0.4.4-1 ii gir1.2-clutter-1.0 1.12.0-1 ii gir1.2-cogl-1.0 1.10.2-6 ii gir1.2-coglpango-1.0 1.10.2-6 ii gir1.2-folks-0.6 0.6.9-1+b1 ii gir1.2-freedesktop 1.32.1-1 ii gir1.2-gconf-2.0 3.2.5-1+build1 ii gir1.2-gcr-3 3.4.1-3 ii gir1.2-gdesktopenums-3.0 3.4.2-3 ii gir1.2-gdkpixbuf-2.0 2.26.1-1 ii gir1.2-gee-1.0 0.6.4-2 ii gir1.2-gkbd-3.0 3.4.0.2-1 ii gir1.2-glib-2.0 1.32.1-1 ii gir1.2-gmenu-3.0 3.4.2-5 ii gir1.2-gnomebluetooth-1.03.4.2-1 ii gir1.2-gtk-3.0 3.4.2-4 ii gir1.2-json-1.0 0.14.2-1 ii gir1.2-mutter-3.03.4.1-5 ii gir1.2-networkmanager-1.00.9.4.0-6 ii gir1.2-pango-1.0 1.30.0-1 ii gir1.2-polkit-1.00.105-1 ii gir1.2-soup-2.4 2.38.1-2 ii gir1.2-telepathyglib-0.120.18.2-2 ii gir1.2-telepathylogger-0.2 0.4.0-2 ii gir1.2-upowerglib-1.00.9.17-1 ii gjs 1.32.0-2 ii gnome-bluetooth 3.4.2-1 ii gnome-icon-theme-symbolic3.4.0-2 ii gnome-settings-daemon3.4.2+git20120925.a4c817-2 ii gnome-shell-common 3.4.2-4 ii gnome-themes-standard3.4.2-2 ii gsettings-desktop-schemas3.6.0-1 ii libatk1.0-0 2.4.0-2 ii libc62.16-0experimental1 ii libcairo-gobject21.12.2-2 ii libcairo21.12.2-2 ii libcanberra0 0.28-6 ii libclutter-1.0-0 1.12.0-1 ii libcogl-pango0 1.10.2-6 ii libcogl9 1.10.2-6 ii libcroco30.6.6-2 ii libdbus-1-3 1.6.8-1 ii libdbus-glib-1-2 0.100-1 ii libebook-1.2-13 3.4.4-1 ii libecal-1.2-11 3.4.4-1 ii libedataserver-1.2-163.4.4-1 ii libedataserverui-3.0-1 3.4.4-1 ii libffi5 3.0.10-3 ii libfolks25 0.6.9-1+b1 ii libgck-1-0 3.4.1-3 ii libgconf-2-4 3.2.5-1+build1 ii libgcr-3-1 3.4.1-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgee2 0.6.4-2 ii libgirepository-1.0-11.32.1-1 ii libgjs0b [libgjs0-libmozjs185-1.0] 1.32.0-4 ii libgl1-mesa-glx [libgl1] 8.0.5-3 ii libglib2.0-0 2.33.12+really2.32.4-3 ii libgnome-keyring03.4.1-1 ii libgnome-menu-3-03.4.2-5 ii libgstreamer0.10-0 0.10.36-1 ii libgtk-3-0 3.4.2-4 ii libical0 0.48-2 ii libjson-glib-1.0-0 0.14.2-1 ii libmozjs185-1.0 1.8.5-1.0.0+dfsg-4 ii libmutter0 3.4.1-5 ii libnm-glib4 0.9.4.0-6 ii libnm-util2 0.9.4.0-6 ii libnspr4
Bug#686402: kfreebsd-kernel-headers: several headers assume _BSD_SOURCE
tags 686402 - patch thanks On 24/12/12 00:54, Steven Chamberlain wrote: --- kfreebsd-9-9.0.orig/sys/sys/filedesc.h 2011-08-11 13:30:23.0 +0100 +++ kfreebsd-9-9.0/sys/sys/filedesc.h 2012-12-24 00:48:21.750672610 + @@ -48,2 +48,2 @@ * This structure is used for the management of descriptors. It may be * shared by multiple processes. */ -#define NDSLOTTYPE u_long +#define NDSLOTTYPE __u_long Actually no... this breaks kernel compilation: clang -c -O2 -frename-registers -pipe -fno-strict-aliasing -O1 -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Win line -Wcast-qual -Wundef -Wno-pointer-sign -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I../../.. -I../../../contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_H EADERS -include opt_global.h -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -msoft-float -fno-asynchronous-unwind-tables -ffreestanding ../ ../../dev/syscons/scvidctl.c In file included from ../../../dev/syscons/scvidctl.c:44: ../../../sys/filedesc.h:57:2: error: unknown type name '__u_long'; did you mean 'u_long'? NDSLOTTYPE *fd_map; /* bitmap of free fds */ ^~ u_long ../../../sys/filedesc.h:48:20: note: expanded from macro 'NDSLOTTYPE' #define NDSLOTTYPE __u_long ^ ../../../sys/types.h:53:23: note: 'u_long' declared here typedef unsigned long u_long; ^ Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695130: openmotif is now LGPL, retirement of lesstif in jessie?
On Mon, Dec 24, 2012 at 12:01:37PM +0100, Paul Gevers wrote: If he agrees, we could start with packaging the next version already in experimental. Although of course, we should be focusing on releasing Wheezy right now. I would suggest then that you guys work togther and even might have a look at this very related RFP [1] :). Cheers, Adrian [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689098 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587179: dlocate -- -mp3 fails
Hey Norbert, I am currently going through some bugs which I am fixing through NMUs and I stumbled accross dlocate which has quite a few easily fixable bugs. I already fixed the manpage bugs and created an NMU in the DELAYED/5 queue [1]. I set up a github repository for my changes [2] and I would like to integrate your patch as well, of course. Could you please check whether your patch still applies and create an updated one, if necessary? I would then create a new Debian revision of dlocate and upload it later since the maintainer seems to be MIA. If you like, you can also adopt the package yourself :). Cheers, Adrian [1] http://ftp-master.debian.org/deferred.html [2] https://github.com/glaubitz/dlocate -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696141: kdenetwork: FTBFS: moc: .../kopete/protocols/sms/gsmlibprefs.h: No such file
Control: tags -1 unreproducible Control: severity -1 important Hi Thorsten, On Mon, Dec 17, 2012 at 08:29:22AM +, Thorsten Glaser wrote: kdenetwork fails to build, apparently looking for a file which it generated a few lines above, according to the attached build log. I tried on amd64 with pbuilder in wheezy and sid, and manually in a clean sid chroot (running debian/rules build-arch ; debian/rules binary-arch). Those 3 runs finished without failures. Can you think of a way to reproduce this on a release arch? I'm downgrading the bug because m68k is not a release arch. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656546: key not always mandatory etc.
found 656546 0.06-1 thanks File: /usr/share/man/man3/Geo::Google::MapObject.3pm.gz key The mandatory API key. You can sign up for one at http://code.google.com/apis/maps/signup.html. Current policies mean this is not necessarily mandatory now in all cases. Perhaps reword the man page. And fix the program! no API key at l.pl line 4 Sentence without context, which also needs to be fixed: Google Maps API You need to have one of these which can be obtained from http://code.google.com/apis/maps/signup.html. Update this sentence too: no API key To use this module you must sign up for an API key (http://code.google.com/apis/maps/signup.html) and supply it as the key parameter. P.S., # su - nobody $ /dev/null /dev/null man Geo::Google::MapObject standard input:180: warning [p 1, 9.3i]: can't break line standard input:210: warning [p 2, 4.0i]: can't break line... P.S., I recall the google docs say to emit %7C's instead of |'s, as seen with your static_map_url... Hmmm, it seems lots would need to be updated to make it match the current staticmaps standard... e.g., visible= computed along with markers=... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675754: O: kwiki -- Quickie Wiki that's not too Tricky
reassign 675754 ftp.debian.org retitle 675754 RM: kwiki -- RoQA; obsolete transitional package thanks On Sun, Jun 03, 2012 at 07:19:26AM +, Bart Martens wrote: Package: wnpp After consulting the MIA database, having a look at the PTS and DDPO pages, and the list of open bugs in the BTS, I concluded that this package is in fact orphaned. I'm therefor marking this package as orphaned now. I have made a few comments on the open bugs. My impression is that kwiki should be removed from Debian, but I have not yet decided to request the removal. This is a transitional package for transitions from pre-oldstable. It should just be removed. Gruesse, Frank -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695850: VCS-Browser link
VCS-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/libteam.git -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534409: namespace workaround
dlocate -L python-feedvalidator | xargs grep /kml/2.2 ... help me find the workaround, sed s/www.opengis.net/earth.google.com/ file.kml ... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693492: Perhaps we don't need it...
As of December 2012 the package is ready (completed). However pkg-bitcoin team is not convinced if we really need litecoin in Debian. At the moment Litecoin is redundant to Bitcoin and have very little or no value. See also https://en.bitcoin.it/wiki/Litecoin#Criticism If you're interested in litecoin package please consider support and maintenance implications for Debian as Litecoin have little or no use. -- Regards, Dmitry. signature.asc Description: This is a digitally signed message part.
Bug#696585: apper: Presentation of packages with Multiarch support on is sub-optimal (too much results)
Uh... Apparently, this was only implemented in a more recent version of Apper... You will find the latest release of Apper very soon in Debian Experimental (as soon as it is released). Also, Apper 0.8.x might be backported to Wheezy (but there's a larger amount of porting needed). Cheers, Matthias 2012/12/23 Paul Gevers elb...@debian.org: On 23-12-12 12:19, Matthias Klumpp wrote: Have you tried using Filter-Only native packages? The filters that I have available are: Installed Only installed Only available No filter Development Only development Only end user files No filter Graphical Only graphical Only text No filter Free Only free software Only non-free software No filter Supported Only supported software Only non-supported software No filter Which one should I use? Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
