Processed: Re: Bug#650840: transition: zita-convolver
Processing commands for cont...@bugs.debian.org: clone 650840 -1 Bug#650840: transition: zita-convolver Bug 650840 cloned as bug 652019. reassign -1 ir.lv2 Bug #652019 [release.debian.org] transition: zita-convolver Bug reassigned from package 'release.debian.org' to 'ir.lv2'. found -1 1.3.1~dfsg0-1 Bug #652019 [ir.lv2] transition: zita-convolver Bug Marked as found in versions ir.lv2/1.3.1~dfsg0-1. retitle -1 Uninstalllable and needs porting to zita-convolver's new API Bug #652019 [ir.lv2] transition: zita-convolver Changed Bug title to 'Uninstalllable and needs porting to zita-convolver's new API' from 'transition: zita-convolver' severity -1 serious Bug #652019 [ir.lv2] Uninstalllable and needs porting to zita-convolver's new API Severity set to 'serious' from 'normal' block 650840 by -1 Bug #650840 [release.debian.org] transition: zita-convolver Was not blocked by any bugs. Added blocking bug(s) of 650840: 652019 thanks Stopping processing here. Please contact me if you need assistance. -- 650840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650840 652019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652019 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651204: 1.3.7-1 in experimental
Hi, I've uploaded a patched version to experimental. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651452: illuminator: FTBFS on sparc (tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte')
reopen 651452 retitle 651452 illuminator: FTBFS on archs where petsc uses liblam (tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte') found 651452 0.11.0-8.2 clone 651452 -1 retitle -1 illuminat: Build-Conflicts on libmpich2-dev to strict thanks Hi! * Alexander Reichle-Schmehl alexan...@schmehl.info [111212 13:45]: The problem seems to be, that petsc is linked to liblam on sparc, and therefore the additional linkerflad -llam is needed on that arch. I have no idea, why this issue han't shown up on armel, mips, mipsel or s390, the other arches on which petsc uses lam. My patch adds the missing flag on sparc. And here we are again, this time on armel. I have no idea, why 0.11.0-8.1 was build successfull on armel, as it seems to be the very same isssue according to the build logs: https://buildd.debian.org/status/logs.php?pkg=illuminatorarch=armel The trivial workarround would be to extend the host arch query in debian/rules similimar to the following: DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH) ifeq ($(DEB_HOST_ARCH), sparc) LLAM=-llam else ifeq ($(DEB_HOST_ARCH), armel) LLAM=-llam else LLAM= endif endif Note that I didn't test it, and as I have shown nicely in my NMU that isn't very reliable. So it might be better to check the lib itself, e.g. with objdump -x /usr/lib/libpetsc.so|grep -i liblam.so|grep NEEDED That shows the exptected line on sparc on armel, while it doesn't on amd64, but I didn't to further checks. + * Add libmpich2-dev to build-conflicts to prevent FTBFS as described in +http://bugs.debian.org/651452#22 and #27) Sorry, but that seems to have been a really bad idea, as not the build-depends on armhf, mips, mipsel, s390 and s390x can't be fullfilled at all. I'm not sure if it would be better to drop that complelty (as that seems to be a problem not showing up on the buildds) or make that a arch-specific build-conflict (which would be cleaner solution, but the list would need to be maintained). I clone this bug, as this is a different issue. Best Regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#651452: illuminator: FTBFS on sparc (tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte')
Processing commands for cont...@bugs.debian.org:
reopen 651452
Bug #651452 {Done: Alexander Reichle-Schmehl toli...@debian.org}
[src:illuminator] illuminator: FTBFS on sparc (tsview-tsview.o: undefined
reference to symbol 'lam_mpi_byte')
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
retitle 651452 illuminator: FTBFS on archs where petsc uses liblam
(tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte')
Bug #651452 [src:illuminator] illuminator: FTBFS on sparc (tsview-tsview.o:
undefined reference to symbol 'lam_mpi_byte')
Changed Bug title to 'illuminator: FTBFS on archs where petsc uses liblam
(tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte')' from
'illuminator: FTBFS on sparc (tsview-tsview.o: undefined reference to symbol
'lam_mpi_byte')'
found 651452 0.11.0-8.2
Bug #651452 [src:illuminator] illuminator: FTBFS on archs where petsc uses
liblam (tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte')
Bug Marked as found in versions illuminator/0.11.0-8.2.
clone 651452 -1
Bug#651452: illuminator: FTBFS on archs where petsc uses liblam
(tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte')
Bug 651452 cloned as bug 652025.
retitle -1 illuminat: Build-Conflicts on libmpich2-dev to strict
Bug #652025 [src:illuminator] illuminator: FTBFS on archs where petsc uses
liblam (tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte')
Changed Bug title to 'illuminat: Build-Conflicts on libmpich2-dev to strict'
from 'illuminator: FTBFS on archs where petsc uses liblam (tsview-tsview.o:
undefined reference to symbol 'lam_mpi_byte')'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
652025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652025
651452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651452
-1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640606: mythes-it: installation fails
tag 640606 pending thanks Lucas Nussbaum [2011-09-05 22:37 +0200]: + /usr/sbin/update-openoffice-dicts /var/lib/dpkg/info/mythes-it.postinst: 7: /var/lib/dpkg/info/mythes-it.postinst: /usr/sbin/update-openoffice-dicts: not found dpkg: error processing mythes-it (--configure): As this package is in collab-maint, I took the liberty to commit the (dead simple) fix to the packaging git. Enrico, want me to NMU, or want to upload yourself? Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Processed: Re: Bug#640606: mythes-it: installation fails
Processing commands for cont...@bugs.debian.org: tag 640606 pending Bug #640606 [mythes-it] mythes-it: installation fails Bug #640607 [mythes-it] openoffice.org-thesaurus-it: installation fails Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 640606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515284: geg: Depends on GTK 1.2
Barry deFreese wrote: Here is a patch that builds with Gtk2 as well as fix several packaging issues and bump standards version, etc. The patch builds fine but seems like it may have some issues at runtime so it probably needs a bit more work. Hope it helps. Sorry for not answering earlier, I probably gave a look at the patch, tried fixing runtime issues, and got lost. I just had a new look and there are issues around text views (probably not difficult to fix) but it also looks like the drawing in the equation view would need some serious work. Moritz Muehlenhoff wrote: Frederic, shall we proceed with removal from the archive? I am of this opinion. Fred -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650021: marked as done (CVE-2011-4349: SQL injection)
Your message dated Wed, 14 Dec 2011 11:02:13 + with message-id e1rambf-0003mv...@franck.debian.org and subject line Bug#650021: fixed in colord 0.1.15-1 has caused the Debian Bug report #650021, regarding CVE-2011-4349: SQL injection to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 650021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: colord Severity: grave Tags: security Hi, the following vulnerability was reported on oss-security by Ludwig Nussel of SuSE: colord did not quote user supplied strings which made it prone to SQL injections: https://bugs.freedesktop.org/show_bug.cgi?id=42904 https://bugzilla.novell.com/show_bug.cgi?id=698250 When colord runs as root and local active users are allowed to create new devices (both are the defaults AFAIK) this allows not only to corrupt colord's own database but also to leverage it to modify other databases in the system (PackageKit for example also uses sqlite). Patches: http://gitorious.org/colord/master/commit/1fadd90afcb4bbc47513466ee9bb1e4a8632ac3b http://gitorious.org/colord/master/commit/36549e0ed255e7dfa7852d08a75dd5f00cbd270e This has been assigned CVE-2011-4349. Cheers, Moritz -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: colord Source-Version: 0.1.15-1 We believe that the bug you reported is fixed in the latest version of colord, which is due to be installed in the Debian FTP archive: colord_0.1.15-1.debian.tar.gz to main/c/colord/colord_0.1.15-1.debian.tar.gz colord_0.1.15-1.dsc to main/c/colord/colord_0.1.15-1.dsc colord_0.1.15-1_amd64.deb to main/c/colord/colord_0.1.15-1_amd64.deb colord_0.1.15.orig.tar.xz to main/c/colord/colord_0.1.15.orig.tar.xz gir1.2-colord-1.0_0.1.15-1_amd64.deb to main/c/colord/gir1.2-colord-1.0_0.1.15-1_amd64.deb libcolord-dev_0.1.15-1_amd64.deb to main/c/colord/libcolord-dev_0.1.15-1_amd64.deb libcolord1_0.1.15-1_amd64.deb to main/c/colord/libcolord1_0.1.15-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 650...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christopher James Halse Rogers r...@ubuntu.com (supplier of updated colord package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 14 Dec 2011 15:25:41 +1100 Source: colord Binary: libcolord-dev libcolord1 colord gir1.2-colord-1.0 Architecture: source amd64 Version: 0.1.15-1 Distribution: unstable Urgency: low Maintainer: Christopher James Halse Rogers r...@ubuntu.com Changed-By: Christopher James Halse Rogers r...@ubuntu.com Description: colord - system service to manage device colour profiles -- system daemon gir1.2-colord-1.0 - GObject introspection data for the colord library libcolord-dev - system service to manage device colour profiles -- development fi libcolord1 - system service to manage device colour profiles -- runtime Closes: 650021 Changes: colord (0.1.15-1) unstable; urgency=low . * New upstream release. + Fixes sqlite injection vulnerability, preventing malicious applications from corrupting colord's database (Closes: #650021). * debian/patches/01_use_polkit_owner_annotation.patch: + Cherry-pick from upstream, enabling use of the PolicyKit owner annotation. * debian/control: + Add versioned Build-Depends on libpolkit-gobject-1-dev to ensure configure detects a new enough PolicyKit to enable the owner annotation. + Add versioned Depends on policykit-1 to colord to ensure a new enough PolicyKit to understand the owner annotation at runtime. * debian/rules: + Re-enable PolicyKit support now that the owner annotation is supported. * debian/patches/06_use_dbus_security_for_permissions.diff: + Drop; PolicyKit has been fixed. * debian/libcolord1.symbols: Add new symbols in 0.1.14 and 0.1.15 Checksums-Sha1:
Bug#640606: mythes-it: installation fails
On Wed, Dec 14, 2011 at 10:27:40AM +0100, Martin Pitt wrote: Lucas Nussbaum [2011-09-05 22:37 +0200]: + /usr/sbin/update-openoffice-dicts /var/lib/dpkg/info/mythes-it.postinst: 7: /var/lib/dpkg/info/mythes-it.postinst: /usr/sbin/update-openoffice-dicts: not found dpkg: error processing mythes-it (--configure): As this package is in collab-maint, I took the liberty to commit the (dead simple) fix to the packaging git. Enrico, want me to NMU, or want to upload yourself? Uploaded. Thanks for the patch! You saved me the time to do the research on what needed to be done, which unfortunately I didn't have. Ciao, Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini enr...@enricozini.org signature.asc Description: Digital signature
Bug#652035: wicd-curses: Crashs when running (Python UnicodeDecodeError)
Package: wicd-curses Version: 1.7.1~b3-2 Severity: grave Justification: renders package unusable Dear Maintainer, wicd-curses always crashs when I start the program. The error is: Traceback (most recent call last): File /usr/share/wicd/curses/wicd-curses.py, line 1063, in module main() File /usr/share/wicd/curses/wicd-curses.py, line 995, in main ui.run_wrapper(run) File /usr/lib/python2.7/dist-packages/urwid/raw_display.py, line 237, in run_wrapper return fn() File /usr/share/wicd/curses/wicd-curses.py, line 89, in wrapper return func(*args, **kargs) File /usr/share/wicd/curses/wicd-curses.py, line 1003, in run app = appGUI() File /usr/share/wicd/curses/wicd-curses.py, line 551, in __init__ self.update_netlist(force_check=True,firstrun=True) File /usr/share/wicd/curses/wicd-curses.py, line 89, in wrapper return func(*args, **kargs) File /usr/share/wicd/curses/wicd-curses.py, line 670, in update_netlist wiredL,wlessL = gen_network_list() File /usr/share/wicd/curses/wicd-curses.py, line 177, in gen_network_list label = NetLabel(network_id,is_active) File /usr/share/wicd/curses/wicd-curses.py, line 358, in __init__ self.stren,self.essid,self.encrypt,self.bssid,self.mode,self.channel) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 5: ordinal not in range(128) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wicd-curses depends on: ii python2.7.2-9 ii python-urwid 1.0.1-2 ii wicd-daemon 1.7.1~b3-2 Versions of packages wicd-curses recommends: ii sudo 1.8.3p1-2 wicd-curses suggests no packages. Versions of packages wicd depends on: ii wicd-daemon 1.7.1~b3-2 Versions of packages wicd-cli depends on: ii wicd-daemon 1.7.1~b3-2 Versions of packages wicd-cli recommends: ii sudo 1.8.3p1-2 Versions of packages wicd-gtk depends on: ii python 2.7.2-9 ii python-glade2 2.24.0-2 ii python-gtk22.24.0-2 ii wicd-daemon1.7.1~b3-2 Versions of packages wicd-gtk recommends: ii gksu 2.0.2-6 ii python-notify 0.1.1-3 Versions of packages wicd-daemon depends on: ii adduser 3.113 ii dbus1.4.16-1 ii debconf 1.5.41 ii dhcpcd 1:3.2.3-9 ii iproute 2017-1 ii iputils-ping3:20101006-1+b1 ii lsb-base3.2-28 ii net-tools 1.60-24.1 ii psmisc 22.14-1 ii python 2.7.2-9 ii python-dbus 0.84.0-2 ii python-gobject 3.0.2-4 ii python-wicd 1.7.1~b3-2 ii wireless-tools 30~pre9-7 ii wpasupplicant 0.7.3-5 wicd-daemon recommends no packages. Versions of packages wicd-daemon suggests: ii pm-utils 1.4.1-8 Versions of packages python-wicd depends on: ii python 2.7.2-9 ii python2.6 2.6.7-4 ii python2.7 2.7.2-8 -- debconf information: * wicd/users: florian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643782: ranger: Cannot be launched; ImportError raised
Hi Raphael, * Raphael Plasson rplas...@gmail.com, 2011-09-29, 18:06: ranger can actually be launched normally if the link /usr/bin/python is changed, and point to /usr/bin/python/2.6 instead of the now default /usr/bin/python/2.7. Please never ever change the /usr/bin/python symlink destination manually. More importantly, please don't post such ideas to BTS, because some people might follow such advice, breaking their systems horribly. (Yes, it happened it the past...) Thanks. If you want to run a program with non-standard Python version, this should do the trick most of the time: python2.6 /usr/bin/ranger -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652011: general: Repeated pattern of FHS violation: Dependencies of /sbin and /bin, belong in /lib
Russ Allbery writes (Re: Bug#652011: general: Repeated pattern of FHS violation: Dependencies of /sbin and /bin, belong in /lib): I don't know if it's worth the effort to unify /bin and /usr/bin or the other similar things that have been discussed from time to time, The situation we have, where this is something we vaguely try to do but don't spend a lot of effort on, is IMO perfectly reasonable. For example, it would be possible for someone who wanted to make a Debian derivative which shipped with a separate /usr by default to go and fix all of these bugs, and we shouldn't make that impossible by deliberately conflating / and /usr or by rejecting the bug reports. but I do think it may be time for Debian to just officially say that we don't support /usr on a (meaningfully) separate partition from /bin and /lib, and that binaries in /bin may have dependencies on /usr/lib. If we want to relax the policy, we could say in principle we think this is a nice to have but whether to support it is up to maintainers of individual packages. Let's please not go straight to deliberately breaking it for the sake of tidiness. Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643782: ranger: Cannot be launched; ImportError raised
Hi Roman, * Roman Z. rom...@lavabit.com, 2011-11-10, 14:09: ranger can't run if it can't find the ranger python module. It must be in one of the PYTHONPATH directories. On my install, ranger was installed to /usr/share/pyshared Which is completely normal. which is not in PYTHONPATH so ranger will not find it. It would be a task for postinst script to make them appear there. (But the package was broken, and was explicitly declaring that is supports only 2.6, so it didn't work.) It ought to be put at /usr/lib/pythonX/dist-packages/ instead with X being your python version. To fix this, create a link from the place ranger was installed to some place in your PYTHONPATH, for example: ln -s /usr/share/pyshared/ranger /usr/lib/python2.7/dist-packages/ranger Do not ever do this. More importantly, do not post such ideas to the BTS, because some people might follow your advice, breaking their systems horribly in a way that is very hard to debug. (Yes, it happened in the past...) Thanks. [...] ImportError: No module named gui.defaultui This is caused due to removal of the empty file ranger/gui/__init__.py, which is required for python to recognize that this directory is a python module. Lack of __init__.py files in /usr/share/pyshared is also completely normal. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651452: illuminator: FTBFS on sparc (tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte')
Hi Alexander, On Wed, 2011-12-14 at 10:09 +0100, Alexander Reichle-Schmehl wrote: reopen 651452 retitle 651452 illuminator: FTBFS on archs where petsc uses liblam (tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte') found 651452 0.11.0-8.2 clone 651452 -1 retitle -1 illuminat: Build-Conflicts on libmpich2-dev to strict That's not going to work: illuminator Build-Depends on mpi-default-dev, which depends on libmpich2-dev on several arches. Better to rip out the -llam and replace LLAM in the patch with -lmpi. I'll test then upload -12 with this change and let's see how it builds. Please don't zero-day NMU! -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part
Bug#652059: mlt: FTBFS(kfreebsd):
Package: src:mlt Version: 0.7.6+git20111213-1 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: g++ -I../.. -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre -ffast-math-g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DARCH_X86_64 -fPIC -pthread -Wno-deprecated -Wno-multichar -fno-rtti -D__LINUX_OSS__ -c -o consumer_rtaudio.o consumer_rtaudio.cpp g++ -I../.. -Wall -DPIC -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre -ffast-math-g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DARCH_X86_64 -fPIC -pthread -Wno-deprecated -Wno-multichar -fno-rtti -D__LINUX_OSS__ -c -o RtAudio.o RtAudio.cpp RtAudio.cpp:6376:23: fatal error: soundcard.h: No such file or directory compilation terminated. make[3]: *** [RtAudio.o] Error 1 Full build log at https://buildd.debian.org/status/fetch.php?pkg=mltarch=kfreebsd-i386ver=0.7.6%2Bgit20111213-1stamp=1323805688 Is this a include of linux/soundcard.h? If so switching to sys/soundcard.h might be the best way as it's there not only on linux but also on kfreebsd (and probably others) Regards Christoph If you have further questions please mail debian-...@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651872: opencv: FTBFS on kfreebsd
tags 651872 patch kthxbye On Mon, Dec 12, 2011 at 20:15:54 +0100, Julien Cristau wrote: Source: opencv Version: 2.3.1-1 Severity: serious opencv fails to build on the kfreebsd-* buildds: https://buildd.debian.org/status/package.php?p=opencv Fixed with the patch below. On top of 2.3.1-0exp1 because apparently debian-science svn wasn't updated with 2.3.1-1. Index: debian/patches/0001-drop-useless-asm-types-h.patch === --- debian/patches/0001-drop-useless-asm-types-h.patch (revision 0) +++ debian/patches/0001-drop-useless-asm-types-h.patch (revision 0) @@ -0,0 +1,27 @@ +From: Julien Cristau jcris...@debian.org +Date: Tue Dec 13 20:23:15 UTC 2011 +Subject: Drop useless asm/types.h include + +It's linux-specific, and unneeded there anyway. +Closes: #651872 + +--- a/modules/highgui/src/cap_libv4l.cpp.orig 2011-12-13 21:21:37.0 +0100 b/modules/highgui/src/cap_libv4l.cpp 2011-12-13 21:21:55.0 +0100 +@@ -236,7 +236,6 @@ + #include sys/mman.h + #include string.h + #include stdlib.h +-#include asm/types.h /* for videodev2.h */ + #include assert.h + #include sys/stat.h + #include sys/ioctl.h +--- a/modules/highgui/src/cap_v4l.cpp.orig 2011-12-13 23:08:01.0 +0100 b/modules/highgui/src/cap_v4l.cpp 2011-12-13 23:07:40.0 +0100 +@@ -218,7 +218,6 @@ + + #include string.h + #include stdlib.h +-#include asm/types.h /* for videodev2.h */ + #include assert.h + #include sys/stat.h + #include sys/ioctl.h Index: debian/patches/series === --- debian/patches/series (revision 44150) +++ debian/patches/series (working copy) @@ -1,3 +1,4 @@ +0001-drop-useless-asm-types-h.patch 0005-build-static-libs.patch 0007-typos-in-strings-docs.patch 0011_optimize_i486.patch Index: debian/changelog === --- debian/changelog(revision 44150) +++ debian/changelog(working copy) @@ -1,3 +1,10 @@ +opencv (2.3.1-0exp1.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Drop useless asm/types.h include to fix FTBFS on kfreebsd. + + -- Julien Cristau jcris...@debian.org Tue, 13 Dec 2011 22:17:22 +0100 + opencv (2.3.1-0exp1) experimental; urgency=low * New upstream release. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#651872: opencv: FTBFS on kfreebsd
Processing commands for cont...@bugs.debian.org: tags 651872 patch Bug #651872 [src:opencv] opencv: FTBFS on kfreebsd Added tag(s) patch. kthxbye Stopping processing here. Please contact me if you need assistance. -- 651872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637845: marked as done (deal.ii: FTBFS: arch-dependent build runs debian/rules build-doc target without Build-Depends-Indep packages installed)
Your message dated Wed, 14 Dec 2011 14:48:21 + with message-id e1raq85-0005yw...@franck.debian.org and subject line Bug#637845: fixed in deal.ii 7.0.0-3 has caused the Debian Bug report #637845, regarding deal.ii: FTBFS: arch-dependent build runs debian/rules build-doc target without Build-Depends-Indep packages installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 637845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:deal.ii Version: 7.0.0-2 Severity: serious For some reason, arch-dependent builds on the buildds are triggering the build-doc target, but doxygen is not installed because it's in Build-Depends-Indep but not Build-Depends. I can't figure out why it's doing this, and can't reproduce it. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- Source: deal.ii Source-Version: 7.0.0-3 We believe that the bug you reported is fixed in the latest version of deal.ii, which is due to be installed in the Debian FTP archive: deal.ii-doc_7.0.0-3_all.deb to main/d/deal.ii/deal.ii-doc_7.0.0-3_all.deb deal.ii-examples_7.0.0-3_all.deb to main/d/deal.ii/deal.ii-examples_7.0.0-3_all.deb deal.ii_7.0.0-3.debian.tar.gz to main/d/deal.ii/deal.ii_7.0.0-3.debian.tar.gz deal.ii_7.0.0-3.dsc to main/d/deal.ii/deal.ii_7.0.0-3.dsc libdeal.ii-dbg7.0.0_7.0.0-3_amd64.deb to main/d/deal.ii/libdeal.ii-dbg7.0.0_7.0.0-3_amd64.deb libdeal.ii-dbg_7.0.0-3_all.deb to main/d/deal.ii/libdeal.ii-dbg_7.0.0-3_all.deb libdeal.ii-dev_7.0.0-3_all.deb to main/d/deal.ii/libdeal.ii-dev_7.0.0-3_all.deb libdeal.ii7.0.0_7.0.0-3_amd64.deb to main/d/deal.ii/libdeal.ii7.0.0_7.0.0-3_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 637...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam C. Powell, IV hazel...@debian.org (supplier of updated deal.ii package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 12 Dec 2011 21:16:56 -0500 Source: deal.ii Binary: libdeal.ii-dbg7.0.0 libdeal.ii-dbg libdeal.ii7.0.0 libdeal.ii-dev deal.ii-doc deal.ii-examples Architecture: source all amd64 Version: 7.0.0-3 Distribution: unstable Urgency: low Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Adam C. Powell, IV hazel...@debian.org Description: deal.ii-doc - Finite element library - documentation deal.ii-examples - Finite element library - documentation libdeal.ii-dbg - Finite element library - development files libdeal.ii-dbg7.0.0 - Finite element library - shared library libdeal.ii-dev - Finite element library - development files libdeal.ii7.0.0 - Finite element library - shared library Closes: 637845 Changes: deal.ii (7.0.0-3) unstable; urgency=low . * Made perl script in -dev package executable. * Split install target, cleaned up others, removed build-indep from build (closes: #637845). Checksums-Sha1: a484fce0e42b8c1a07ca928e2669cede9654214c 1940 deal.ii_7.0.0-3.dsc 214dbdfe82311a95f3b2e463567bb53b9a49bb4c 19275 deal.ii_7.0.0-3.debian.tar.gz eae766a8349034cbe5a9a279462b9028e34fd13c 10564 libdeal.ii-dbg_7.0.0-3_all.deb 6d4a16334e716f3109919aeb17eb811e0c19b047 1361450 libdeal.ii-dev_7.0.0-3_all.deb 55b5bcf2161cffc82fbbc2f2ad9c5c40d2e3f4c1 86036640 deal.ii-doc_7.0.0-3_all.deb c3b30500712bffd8c069b82a44ee0b2b3c2ed29a 580902 deal.ii-examples_7.0.0-3_all.deb a35fb89bd94e08b76c80d465f9b3233a2f7e48e0 69465282 libdeal.ii-dbg7.0.0_7.0.0-3_amd64.deb f00e33fef57d642cd8713a32c1891dfd16f4191f 13151236 libdeal.ii7.0.0_7.0.0-3_amd64.deb Checksums-Sha256: 9524c0c00df75c727151b19b61fbedf1e48b900578b49a7fedce99e8df334ddd 1940 deal.ii_7.0.0-3.dsc 9a17d4fa6d6dfd173998034f07b3446ca75e84154e07c7ebec99d061d2b73cb2 19275 deal.ii_7.0.0-3.debian.tar.gz b7055730b0e4e5bbbd31c24200d833cde193505020b4bcd884b0593c29d2198f 10564 libdeal.ii-dbg_7.0.0-3_all.deb 74570e07baf49bfb3b7c024ce7279a77cbd7ff96ca108548c4859ce893c319dc 1361450
Bug#652061: elmerfem: FTBFS missing build-dependencvy?
Package: src:elmerfem Version: 6.1.0.svn.5396.dfsg-3 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the buildds: checking for dseupd_ in -larpack... yes configure: WARNING: No parallel arpack found. checking for pdneupd_ in -lparpack... no checking for HYPRE_IJMatrixCreate in -lHYPRE_IJ_mv... yes checking for dmumps_ in -ldmumps_scotch... yes checking for umfpack_di_defaults in -lumfpack... yes checking for mtc_init in -lmatc... yes configure: error: The MPI version needs parpack. Disabling MPI. checking for main in -lm... yes make: *** [stamp-build] Error 1 Full build log at https://buildd.debian.org/status/fetch.php?pkg=elmerfemarch=kfreebsd-amd64ver=6.1.0.svn.5396.dfsg-3stamp=1323818113 Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652070: awstats: virtualname / SiteDomain accepts nearly everything
Package: awstats Version: 7.0~dfsg-3 Severity: grave Justification: renders package unusable 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 *** - AWstats runs fine for months. - Yesterday apt updated Perl. - Now AWSTats directives %virtualname and SiteDomain accepts nearly all records of the logfile, even with an arbirtray string as SiteDomain, for example SiteDomain=fhawefruzasdfh -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/1 CPU core) 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 awstats depends on: ii perl 5.14.2-6 Versions of packages awstats recommends: ii coreutils 8.13-3 ii libnet-xwhois-perl 0.90-3 Versions of packages awstats suggests: ii apache2 2.2.21-3 ii apache2-mpm-prefork [httpd] 2.2.21-3 ii libgeo-ipfree-perl none ii libnet-dns-perl none ii libnet-ip-perl none ii liburi-perl 1.59-1 -- Configuration Files: /etc/awstats/awstats.conf changed [not included] /etc/awstats/awstats.conf.local changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641348: marked as done (trac-mercurial not up to date for trac 0.12 in debian wheezy)
Your message dated Wed, 14 Dec 2011 15:33:32 + with message-id e1raqpo-0003hl...@franck.debian.org and subject line Bug#641348: fixed in trac-mercurial 0.12.0.28-1 has caused the Debian Bug report #641348, regarding trac-mercurial not up to date for trac 0.12 in debian wheezy to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 641348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: trac-mercurial Version: 0.11.0.10-1 Severity: grave Tags: d-i Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropiate *** * What led up to the situation? Upgrade of trac in Debian Wheezy. * 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? trac-mercurial should have been upgraded as well. No new version available, not in testing, not in unstable. *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (40, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.38-1-686 (SMP w/2 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages trac-mercurial depends on: ii mercurial 1.9.1-2 ii python 2.6.7-3 ii python-support 1.0.14 ii trac0.12.2-1 trac-mercurial recommends no packages. trac-mercurial suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: trac-mercurial Source-Version: 0.12.0.28-1 We believe that the bug you reported is fixed in the latest version of trac-mercurial, which is due to be installed in the Debian FTP archive: trac-mercurial_0.12.0.28-1.debian.tar.gz to main/t/trac-mercurial/trac-mercurial_0.12.0.28-1.debian.tar.gz trac-mercurial_0.12.0.28-1.dsc to main/t/trac-mercurial/trac-mercurial_0.12.0.28-1.dsc trac-mercurial_0.12.0.28-1_all.deb to main/t/trac-mercurial/trac-mercurial_0.12.0.28-1_all.deb trac-mercurial_0.12.0.28.orig.tar.xz to main/t/trac-mercurial/trac-mercurial_0.12.0.28.orig.tar.xz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 641...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Egger christ...@debian.org (supplier of updated trac-mercurial package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 14 Dec 2011 16:10:32 +0100 Source: trac-mercurial Binary: trac-mercurial Architecture: source all Version: 0.12.0.28-1 Distribution: unstable Urgency: low Maintainer: Christoph Egger christ...@debian.org Changed-By: Christoph Egger christ...@debian.org Description: trac-mercurial - Mercurial version control backend for Trac Closes: 641154 641348 Changes: trac-mercurial (0.12.0.28-1) unstable; urgency=low . * New upstream version (Closes: #641348) * Move to dh_python2 (Closes: #641154) Checksums-Sha1: d563f7f2fc466727ca528808033dddbcb1096b1e 1999 trac-mercurial_0.12.0.28-1.dsc b2adf0e3cdf82f43ff542608a3451a9f93a0ace2 23284 trac-mercurial_0.12.0.28.orig.tar.xz fe3ea552faf91ca3478e069284750855accb1497 9850 trac-mercurial_0.12.0.28-1.debian.tar.gz daa31dd0a903ec6be77caa45258f180231520e7b 23636 trac-mercurial_0.12.0.28-1_all.deb Checksums-Sha256: 82b27f69eda3797787ba5a62ca4726ad971ee1f11a7ddad8caab7cdac9073b34 1999 trac-mercurial_0.12.0.28-1.dsc ce93b52a2565e1d90590401cc234945ee18e162a5a627d31846b7168dc0b56cb 23284 trac-mercurial_0.12.0.28.orig.tar.xz 0066d9da0d5fe5ab2c8ada71992124e647dbaf96dbee331ee95cc85cf180c465 9850 trac-mercurial_0.12.0.28-1.debian.tar.gz 742ca3ac6598ebbb640a5448f7ae8e43a63b7a8487da3c3d9676a4822cfba0c6 23636 trac-mercurial_0.12.0.28-1_all.deb Files: 447a131646c4151f26b981e3e05f2d13 1999 python optional trac-mercurial_0.12.0.28-1.dsc 869ea82aa34254ff224f0de1285ae853 23284 python optional trac-mercurial_0.12.0.28.orig.tar.xz 51ede93079616d689a082a56eaa14124 9850 python optional trac-mercurial_0.12.0.28-1.debian.tar.gz f8184296dff8cb56d7066cd98a41e266
Bug#652072: Scala installs lib/jline.jar blob from upstream
Package: scala Version: 2.9.1.dfsg-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, scala installs upstream's lib/jline.jar instead of relying on Debian's jline package. lib/jline.jar even contains a shared library (META-INF/native/linux32/libjansi.so). Regards, Thomas Koch - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages scala depends on: ii default-jre [java6-runtime]1:1.6-45 ii openjdk-6-jre [java6-runtime] 6b24~pre1-1 ii scala-library 2.9.1.dfsg-1 scala recommends no packages. Versions of packages scala suggests: ii scala-doc 2.9.1.dfsg-1 - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJO6MJ4AAoJEAf8SJEEK6ZaROUQAKXXdFgNYdYhFkRVn0apcFez dGUilrJHSH2/FD1o5/0eKR1VB78orLgkxd0Xw0JsVVHGriqdm7SJITsEbrIuuNvw m44V/DG+hSvhgAkeVzSlLY6mxJBdcMeU2k4xUGQRfP83K6mqGaFcyaJawzewwtOC QHgFA5edeYssqcgiORSqd2oLZ0yY+zZOqpSXLLqUfmgXVxKvOKMiYlGq5M4y79M6 nQ8U/y3KyoOnTAiGABD3IDKM5f10mpnzZJde5P81inFKUbGaTUuxnbbGLEXvjxVg aT83Hacj6HaSjRDJnlJzSIrtCoRC3riGL6SKszLaWkfF8q9I4vKGVWcVA7iJnbg5 Ex+8f4C9/DhGhG40/D2ErgO9HNa51ZQDVtlGUoXHduiwZmqcPo1iALYQmwhV/Dbf 9c1Sy1EQ6+/ZqorAjs9B3v19IwX6SMpnQG0jKQE7qzeOrJdC0Q5owSScf5ur3PVX obDK8Yo+v59YWS+TsQFFnSOu2rsrWQQMUJT4fX0w7cuUqdlo/nlTaW9ex8YF6MUW 15LVAECiVatotkxpwNKVCa88KQN2qf/3gE4ufqmTkwfbi7ihRhRHFhB3SwlKhJ0Q D6qbvB0aDDwoSyiYb410/DZ0lnN7OmBmRQ92Gd3B9fNC99siz/kbfH94DuqgYuVK xCU4kc8FG7WAJ7/ZMG4X =AFZK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652072: [Pkg-scala-maint] Bug#652072: Scala installs lib/jline.jar blob from upstream
On 12/14/2011 04:36 PM, Thomas Koch wrote: scala installs upstream's lib/jline.jar instead of relying on Debian's jline package. lib/jline.jar even contains a shared library (META-INF/native/linux32/libjansi.so). Yeah… the sad thing is that the two are incompatible (Debian's jline.jar and Scala's jline.jar), last I looked. I was pretty sure I installed the built jline.jar (not the one provided by upstream). I'll double check later. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#652070: awstats: virtualname / SiteDomain accepts nearly everything
Processing commands for cont...@bugs.debian.org: tag 652070 +moreinfo Bug #652070 [awstats] awstats: virtualname / SiteDomain accepts nearly everything Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 652070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652070: awstats: virtualname / SiteDomain accepts nearly everything
tag 652070 +moreinfo thanks - AWstats runs fine for months. - Yesterday apt updated Perl. - Now AWSTats directives %virtualname and SiteDomain accepts nearly all records of the logfile, even with an arbirtray string as SiteDomain, for example SiteDomain=fhawefruzasdfh Please, test the patch from bug #650492: http://anonscm.debian.org/gitweb/?p=collab-maint/awstats.git;a=blob;f=debian/patches/1018_perl5-14.patch if it fixes your problem. Or try explain exactly how to reproduce one. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625343: gltron: diff for NMU version 0.70final-9.1
tags 625343 + pending
thanks
Dear maintainer,
I've prepared an NMU for gltron (versioned as 0.70final-9.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key ID: 0x8649AA06
: :' : Debian GNU/Linux user, admin, developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of Free Software Foundation Europe
`-NP: U2: Love Rescue Me
diff -Nru gltron-0.70final/debian/changelog gltron-0.70final/debian/changelog
--- gltron-0.70final/debian/changelog 2010-04-02 03:31:24.0 +0200
+++ gltron-0.70final/debian/changelog 2011-12-14 17:03:41.0 +0100
@@ -1,3 +1,12 @@
+gltron (0.70final-9.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix ftbfs with gcc-4.6 -Werror: add patch gcc-4.6.patch from peter green
+(removes unused variables).
+(Closes: #625343)
+
+ -- gregor herrmann gre...@debian.org Wed, 14 Dec 2011 17:02:51 +0100
+
gltron (0.70final-9) unstable; urgency=low
* Change build-depends on xlibmesa-gl-dev to libgl1-mesa-dev
diff -Nru gltron-0.70final/debian/patches/gcc-4.6.patch gltron-0.70final/debian/patches/gcc-4.6.patch
--- gltron-0.70final/debian/patches/gcc-4.6.patch 1970-01-01 01:00:00.0 +0100
+++ gltron-0.70final/debian/patches/gcc-4.6.patch 2011-12-14 17:01:16.0 +0100
@@ -0,0 +1,109 @@
+Description: Fix build issues with gcc 4.6
+Author: Peter Green (plugw...@p10link.net)
+Bug-Debian: http://bugs.debian.org/625343
+
+--- gltron-0.70final.orig/src/game/computer.c
gltron-0.70final/src/game/computer.c
+@@ -27,11 +27,10 @@ AI_Parameters ai_params = {
+ void doComputerSimple(int player, int target, AI_Distances *distances) {
+ AI *ai;
+ Data *data;
+- Player *me, *him;
++ Player *me;
+ int level;
+
+ me = (game-player[ player ]);
+- him = (game-player[ target ]);
+ if(me-ai == NULL) {
+ printf(This player has no AI data!\n);
+ return;
+--- gltron-0.70final.orig/src/game/init_sdl.c
gltron-0.70final/src/game/init_sdl.c
+@@ -27,7 +27,6 @@ void inputInit(void) {
+ /* joystick */
+ if(SDL_Init(SDL_INIT_JOYSTICK) = 0) {
+ int i;
+- SDL_Joystick *joy;
+ int joysticks = SDL_NumJoysticks();
+
+ /* FIXME: why only two joysticks? */
+@@ -36,7 +35,7 @@ void inputInit(void) {
+ joysticks = 2;
+
+ for(i = 0; i joysticks; i++) {
+- joy = SDL_JoystickOpen(i);
++ SDL_JoystickOpen(i);
+ }
+ if(i)
+ SDL_JoystickEventState(SDL_ENABLE);
+--- gltron-0.70final.orig/src/video/trail.c
gltron-0.70final/src/video/trail.c
+@@ -81,8 +81,6 @@ void drawTrailLines(Player *p, PlayerVis
+ float height;
+
+ float *normal;
+- float dist;
+- float alpha;
+ Data *data;
+ Camera *cam;
+
+@@ -113,8 +111,8 @@ void drawTrailLines(Player *p, PlayerVis
+ while(s != data-trails + data-trailOffset) {
+ /* the current line is not drawn */
+ /* compute distance from line to eye point */
+-dist = getDist(s, cam-cam);
+- alpha = (game2-rules.grid_size - dist / 2) / game2-rules.grid_size;
++getDist(s, cam-cam);
++// alpha = (game2-rules.grid_size - dist / 2) / game2-rules.grid_size;
+ // trail_top[3] = alpha;
+ glColor4fv(trail_top);
+
+@@ -133,8 +131,8 @@ void drawTrailLines(Player *p, PlayerVis
+ glEnd();
+
+ /* compute distance from line to eye point */
+- dist = getDist(s, cam-cam);
+- alpha = (game2-rules.grid_size - dist / 2) / game2-rules.grid_size;
++ getDist(s, cam-cam);
++ //alpha = (game2-rules.grid_size - dist / 2) / game2-rules.grid_size;
+ // trail_top[3] = alpha;
+ glColor4fv(trail_top);
+
+--- gltron-0.70final.orig/nebu/scripting/scripting.c
gltron-0.70final/nebu/scripting/scripting.c
+@@ -156,11 +156,10 @@ int scripting_GetStringResult(char **s)
+ int scripting_CopyStringResult(char *s, int len) {
+ int status;
+ if(lua_isstring(L, -1)) {
+-int size, copy;
++int size;
+ status = 0;
+ size = lua_strlen(L, -1) + 1;
+-if(size len) { copy = len; status = 2; }
+-else copy = size;
++if(size len) { status = 2; }
+ memcpy( s, lua_tostring(L, -1), size );
+ } else
+ status = 1;
+--- gltron-0.70final.orig/nebu/video/video_system.c
gltron-0.70final/nebu/video/video_system.c
+@@ -19,7 +19,7 @@ void SystemInitWindow(int x, int y, int
+ }
+
+ void SystemInitDisplayMode(int f, unsigned char full) {
+- int bitdepth, zdepth;
++ int zdepth;
+
+ flags = f;
+ fullscreen = full;
+@@ -34,10 +34,8 @@ void SystemInitDisplayMode(int f, unsign
+
+ if(flags SYSTEM_32_BIT) {
+ zdepth = 24;
+-bitdepth = 32;
+ } else {
+ zdepth = 16;
+-bitdepth = 16;
+ }
+ if(flags SYSTEM_DEPTH)
+ SDL_GL_SetAttribute( SDL_GL_DEPTH_SIZE, zdepth);
diff -Nru gltron-0.70final/debian/patches/series gltron-0.70final/debian/patches/series
--- gltron-0.70final/debian/patches/series 2010-04-02 02:07:51.0 +0200
+++ gltron-0.70final/debian/patches/series 2011-12-14 17:02:47.0
Processed: gltron: diff for NMU version 0.70final-9.1
Processing commands for cont...@bugs.debian.org: tags 625343 + pending Bug #625343 [gltron] gltron: ftbfs with gcc-4.6 -Werror Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 625343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625327: marked as done (filtergen: ftbfs with gcc-4.6 -Werror)
Your message dated Wed, 14 Dec 2011 16:32:19 + with message-id e1rarkh-0002ym...@franck.debian.org and subject line Bug#625327: fixed in filtergen 0.12.4-5.1 has caused the Debian Bug report #625327, regarding filtergen: ftbfs with gcc-4.6 -Werror to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 625327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: filtergen Version: 0.12.4-5 Severity: important Tags: wheezy sid User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.6 ftbfs-werror This package builds with -Werror, and GCC 4.6 triggers new warnings which will make the package fail to build. Currently a Debian patch just passes -Wno-error=unused-but-set-variable and -Wno-error=unused-but-set-parameter to avoid build failures, but this patch will be reverted with the GCC 4.6.1 release, and the severity of the report will be raised. The full build log can be found at: http://people.debian.org/~doko/tmp/werror/filtergen_0.12.4-5_lsid64.buildlog The last lines of the build log are at the end of this report. ---End Message--- ---BeginMessage--- Source: filtergen Source-Version: 0.12.4-5.1 We believe that the bug you reported is fixed in the latest version of filtergen, which is due to be installed in the Debian FTP archive: filtergen_0.12.4-5.1.diff.gz to main/f/filtergen/filtergen_0.12.4-5.1.diff.gz filtergen_0.12.4-5.1.dsc to main/f/filtergen/filtergen_0.12.4-5.1.dsc filtergen_0.12.4-5.1_i386.deb to main/f/filtergen/filtergen_0.12.4-5.1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 625...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated filtergen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 Dec 2011 17:06:03 +0100 Source: filtergen Binary: filtergen Architecture: source i386 Version: 0.12.4-5.1 Distribution: unstable Urgency: low Maintainer: Matt Palmer mpal...@debian.org Changed-By: gregor herrmann gre...@debian.org Description: filtergen - packet filter generator for various firewall systems Closes: 625327 Changes: filtergen (0.12.4-5.1) unstable; urgency=low . * Non-maintainer upload. * Fix ftbfs with gcc-4.6 -Werror: add patch from peter green that removes some unused variables. (Closes: #625327) Checksums-Sha1: af17980bfd2acacb0ae4ab6becca46a3c02501ec 1727 filtergen_0.12.4-5.1.dsc 2fce3b33697cd8c2c6b8fe704b8dfaf7b4f373c0 19320 filtergen_0.12.4-5.1.diff.gz a9e855846de714a85cf91079d852f369039f7ee7 53462 filtergen_0.12.4-5.1_i386.deb Checksums-Sha256: 60637b5643dfcea954106de45755f1ef9a844e261797dfa9d49a5841fb2c4459 1727 filtergen_0.12.4-5.1.dsc 3bfaeae3cce663ab80f4d214f5cfa956b01d22ea78db4c1b0435c836f1e3e25e 19320 filtergen_0.12.4-5.1.diff.gz 13b17bbcbb4e35b8c96d4b6b7b4a00a64babe0985abeb61a7e88eb0cc120be47 53462 filtergen_0.12.4-5.1_i386.deb Files: d6990b8d645e02f23c87254bf58f2c70 1727 net optional filtergen_0.12.4-5.1.dsc 5df94d6df9e9932610fe49aace000f91 19320 net optional filtergen_0.12.4-5.1.diff.gz 4e29c83c5974b23cbb20f7ea6da1d4d7 53462 net optional filtergen_0.12.4-5.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJO5icLAAoJELs6aAGGSaoGXkgQAKOpgyUeo/aAV2BZZYtTxYyZ gV4Lm8qIvjl78xv0R31g8fmOv8D9mFp+uQIEbxx+rQxC+YPXghzJSG1reJkHY1or 3Prer3yy6yqthlxO0644PXb8AaluSlpD59bp6AOlLQ8MNywtV/n+R0QUf4Ngukjs v1bURvdNJ2CJt9XG2Z90EDAEegAgw03JakkxZuZKjn55AqW/D8bis0H3TYPGGZtb FGg4iCtWDrv035zNBBeWYuptQhmRTZ2DM9O9Go3dSo9/FOa8HiT7ImZ7I9221Kve E/AhjufT81LiiQ0xfTdmzASkll9pTN44iWFI2DZVn5ygQq5JEh9yTOanfjpl+xjo QPZczOy76osHPD0jLD4NT8Y412JH8RGPtp2SQXcG229MXLxE6s+TdcY6VvIksPp9 D3wEi4UgX+HQqGRQOXZ+ap7a1Y/z2MGkHoiiXQKCQD3aU02T+wF6BzpWOBB1bDtR tL4WLE5kLjW2rihwshXJL+m21rlQP7+6DJdyKdJKY3zV2JVoVPK3k2qUC9XfLIpS 4edVI2BkyVsNb62Uv3Ou6zC4d7PxotK6qtVLBv0GNjUJAROlM5nkAIKozqkDqmkt HjD9SYNOf5QCXUUH41RpwdKQ1WOivoHRyudrdmU+e6VLNuv2H0FLlLXdZP7A7T5u 9V8AfKIAnAtFziwYTwSs =VO/G -END PGP SIGNATURE- ---End Message---
Bug#640597: marked as done (ekeyd: installation fails)
Your message dated Wed, 14 Dec 2011 16:32:10 + with message-id e1rarky-0002ux...@franck.debian.org and subject line Bug#640597: fixed in ekeyd 1.1.5-1 has caused the Debian Bug report #640597, regarding ekeyd: installation fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 640597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ekeyd Version: 1.1.4-1 Severity: serious User: debian...@lists.debian.org Usertags: instest-20110825 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: Reading package lists... Building dependency tree... Reading state information... Starting Starting 2 Done The following extra packages will be installed: liblua5.1-0 liblua5.1-socket2 lua5.1 Suggested packages: munin-node Recommended packages: udev The following NEW packages will be installed: ekeyd liblua5.1-0 liblua5.1-socket2 lua5.1 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 394 kB of archives. After this operation, 1130 kB of additional disk space will be used. Get:1 http://localhost/debian/ sid/main liblua5.1-0 amd64 5.1.4-10 [94.4 kB] Get:2 http://localhost/debian/ sid/main liblua5.1-socket2 amd64 2.0.2-6 [48.1 kB] Get:3 http://localhost/debian/ sid/main lua5.1 amd64 5.1.4-10 [152 kB] Get:4 http://localhost/debian/ sid/main ekeyd amd64 1.1.4-1 [99.6 kB] Fetched 394 kB in 0s (29.6 MB/s) Selecting previously deselected package liblua5.1-0. (Reading database ... 6579 files and directories currently installed.) Unpacking liblua5.1-0 (from .../liblua5.1-0_5.1.4-10_amd64.deb) ... Selecting previously deselected package liblua5.1-socket2. Unpacking liblua5.1-socket2 (from .../liblua5.1-socket2_2.0.2-6_amd64.deb) ... Selecting previously deselected package lua5.1. Unpacking lua5.1 (from .../lua5.1_5.1.4-10_amd64.deb) ... Selecting previously deselected package ekeyd. Unpacking ekeyd (from .../ekeyd_1.1.4-1_amd64.deb) ... Dpkg hook: enabling sh trace for /var/lib/dpkg/info/apt-utils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/apt.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-files.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-passwd.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bash.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bsdutils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dash.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debconf.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debian-archive-keyring.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debianutils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dpkg.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/e2fslibs.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/ekeyd.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/findutils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/gnupg.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/initscripts.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/less.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libacl1.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libattr1.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libblkid1.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libbz2-1.0.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libc6.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libcomerr2.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libdb5.1.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libgc1c2.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libgcc1.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/liblua5.1-0.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/liblua5.1-socket2.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/liblzma2.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libmount1.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libncurses5.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libncursesw5.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libpam-modules.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libpam-runtime.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libpam0g.postinst Dpkg hook: enabling sh trace for
Bug#652072: [Pkg-scala-maint] Bug#652072: Bug#652072: Scala installs lib/jline.jar blob from upstream
On 12/14/2011 04:42 PM, Mehdi Dogguy wrote:
On 12/14/2011 04:36 PM, Thomas Koch wrote:
scala installs upstream's lib/jline.jar instead of relying on
Debian's jline package. lib/jline.jar even contains a shared
library (META-INF/native/linux32/libjansi.so).
Yeah… the sad thing is that the two are incompatible (Debian's
jline.jar and Scala's jline.jar), last I looked. I was pretty sure I
installed the built jline.jar (not the one provided by upstream).
I'll double check later.
It is not the case indeed. Thanks for reporting this bug.
I wonder if I'm not just going to drop jline from scala'a package and
rely on readline-editor instead (by using rlwrap -C scala). That would
help us to not care about their fork of jline. (or I could build jline
from src/jline). Inputs on this matter are welcome.
If we're going with the former, then we will need the little patch
attached to this mail.
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
--- a/compiler/scala/tools/nsc/interpreter/ILoop.scala
+++ b/compiler/scala/tools/nsc/interpreter/ILoop.scala
@@ -780,7 +780,6 @@ class ILoop(in0: Option[BufferedReader], protected val out: JPrintWriter)
)
catch {
case ex @ (_: Exception | _: NoClassDefFoundError) =
-echo(Failed to created JLineReader: + ex + \nFalling back to SimpleReader.)
SimpleReader()
}
}
Bug#652081: derivations: FTBFS: error: 'class XRef' has no member named 'getLastXRefPos'
Source: derivations
Version: 0.52.20100310-1
Severity: serious
Justification: fails to build from source
After fixing incompatibility with GCC 4.5 (see bug #615671), derivations
still FTBFS:
| /usr/bin/make -C PDF PDF.o
| make[4]: Entering directory
`/build/derivations-j8_fZI/derivations-0.52.20100310/btool/PDF'
| g++ -Wall -Wextra -O2 -c PDF.cc -o PDF.o
| PDF.cc: In function 'int PDF::offset_last_xref_table(const PDF::PDF)':
| PDF.cc:11:25: error: 'class XRef' has no member named 'getLastXRefPos'
| PDF.cc:12:1: warning: control reaches end of non-void function [-Wreturn-type]
| make[4]: *** [PDF.o] Error 1
| make[4]: Leaving directory
`/build/derivations-j8_fZI/derivations-0.52.20100310/btool/PDF'
| make[3]: *** [PDF/PDF.o] Error 2
| make[3]: Leaving directory
`/build/derivations-j8_fZI/derivations-0.52.20100310/btool'
| make[2]: *** [../btool/complete-pdf] Error 2
| make[1]: *** [tex/derivations.pdf] Error 2
| make: *** [build-stamp] Error 2
| dpkg-buildpackage: error: debian/rules build gave error exit status 2
| make[2]: Leaving directory
`/build/derivations-j8_fZI/derivations-0.52.20100310/tex'
| make[1]: Leaving directory
`/build/derivations-j8_fZI/derivations-0.52.20100310'
The attached patch fixed this. (Albeit, in order to access a method that
is declared as private, it resorts to an ugly hack.)
--
Jakub Wilk
--- derivations-0.52.20100310.orig/btool/PDF/PDF.cc
+++ derivations-0.52.20100310/btool/PDF/PDF.cc
@@ -1,14 +1,17 @@
+#define private public
#include PDF.h
#include sys/stat.h
#include PDF_rep.h
+#undef private
+
int PDF::file_length( const PDF pdf ) {
return pdf.rep-file_length1;
}
int PDF::offset_last_xref_table( const PDF pdf ) {
- return pdf.rep-xref-getLastXRefPos();
+ return pdf.rep-pdfdoc-getStartXRef();
}
PDF::Iref PDF::iref_catalog( const PDF pdf ) {
Bug#652072: [Pkg-scala-maint] Bug#652072: Scala installs lib/jline.jar blob from upstream
Mehdi Dogguy: I wonder if I'm not just going to drop jline from scala'a package and rely on readline-editor instead (by using rlwrap -C scala). That would help us to not care about their fork of jline. (or I could build jline from src/jline). Inputs on this matter are welcome. I think it is unacceptable for a package in main to just copy a .jar from upstream. Is there an entry in scala's issue tracker asking them to revert to an unpatched jline? Could you fill one and another Debian bug tracking this? Regards, Thomas Koch, http://www.koch.ro -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652082: gcc-msp430: FTBFS on sparc
Source: gcc-msp430 Version: 4.5.3~mspgcc-20110716-3 Severity: serious Justification: fails to build from source User: debian-sp...@lists.debian.org Usertags: sparc gcc-msp430 FTBFS on sparc: | sparc-linux-gnu-gcc -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat -DHAVE_CONFIG_H -DGENERATOR_FILE -o build/genrecog \ | build/genrecog.o build/rtl.o build/read-rtl.o build/ggc-none.o build/vec.o build/min-insn-modes.o build/gensupport.o build/print-rtl.o build/errors.o ../build-sparc-linux-gnu/libiberty/libiberty.a | build/genrecog /build/buildd-gcc-msp430_4.5.3~mspgcc-20110716-3-sparc-BwjXgt/gcc-msp430-4.5.3~mspgcc-20110716/./gcc-4.5.3/gcc/config/msp430/msp430.md \ | insn-conditions.md tmp-recog.c | /bin/bash: line 1: 6441 Bus error build/genrecog /build/buildd-gcc-msp430_4.5.3~mspgcc-20110716-3-sparc-BwjXgt/gcc-msp430-4.5.3~mspgcc-20110716/./gcc-4.5.3/gcc/config/msp430/msp430.md insn-conditions.md tmp-recog.c | make[3]: *** [s-recog] Error 138 | make[3]: Leaving directory `/build/buildd-gcc-msp430_4.5.3~mspgcc-20110716-3-sparc-BwjXgt/gcc-msp430-4.5.3~mspgcc-20110716/build-result/gcc' Full build log: https://buildd.debian.org/status/fetch.php?pkg=gcc-msp430arch=sparcver=4.5.3%7Emspgcc-20110716-3stamp=1323293228 I tried to reproduce the failure on smetana.d.o, but it failed differently there: | /home/jwilk/gcc-msp430-4.5.3~mspgcc-20110716/build-result/./gcc/xgcc -B/home/jwilk/gcc-msp430-4.5.3~mspgcc-20110716/build-result/./gcc/ -B/usr/msp430/bin/ -B/usr/msp430/lib/ -isystem /usr/msp430/include -isystem /usr/msp430/sys-include-g -O2 -mcpu=430x -O2 -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -DDF=SF -Dinhibit_libc -g -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../.././gcc -I/home/jwilk/gcc-msp430-4.5.3~mspgcc-20110716/./gcc-4.5.3/libgcc -I/home/jwilk/gcc-msp430-4.5.3~mspgcc-20110716/./gcc-4.5.3/libgcc/. -I/home/jwilk/gcc-msp430-4.5.3~mspgcc-20110716/./gcc-4.5.3/libgcc/../gcc -I/home/jwilk/gcc-msp430-4.5.3~mspgcc-20110716/./gcc-4.5.3/libgcc/../include -DHAVE_CC_TLS -DUSE_EMUTLS -o _negdi2.o -MT _negdi2.o -MD -MP -MF _negdi2.dep -DL_negdi2 -c /home/jwilk/gcc-msp430-4.5.3~mspgcc-20110716/./gcc-4.5.3/libgcc/../gcc/libgcc2.c \ | | /home/jwilk/gcc-msp430-4.5.3~mspgcc-20110716/./gcc-4.5.3/libgcc/../gcc/libgcc2.c: In function ‘__negdi2’: | /home/jwilk/gcc-msp430-4.5.3~mspgcc-20110716/./gcc-4.5.3/libgcc/../gcc/libgcc2.c:76:1: internal compiler error: Segmentation fault | Please submit a full bug report, | with preprocessed source if appropriate. | See http://gcc.gnu.org/bugs.html for instructions. | make[5]: *** [_negdi2.o] Error 1 | make[5]: Leaving directory `/home/jwilk/gcc-msp430-4.5.3~mspgcc-20110716/build-result/msp430/mcpu-430x/libgcc' -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652061: elmerfem: FTBFS missing build-dependencvy?
Hi Christoph, On Wed, 2011-12-14 at 16:01 +0100, Christoph Egger wrote: Package: src:elmerfem Version: 6.1.0.svn.5396.dfsg-3 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the buildds: checking for dseupd_ in -larpack... yes configure: WARNING: No parallel arpack found. checking for pdneupd_ in -lparpack... no checking for HYPRE_IJMatrixCreate in -lHYPRE_IJ_mv... yes checking for dmumps_ in -ldmumps_scotch... yes checking for umfpack_di_defaults in -lumfpack... yes checking for mtc_init in -lmatc... yes configure: error: The MPI version needs parpack. Disabling MPI. checking for main in -lm... yes make: *** [stamp-build] Error 1 Thanks for the report. Hmm, libparpack.so is still there, but doesn't have this symbol. Requires further investigation. I should be able to get to it in the next day or two. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part
Bug#651597: marked as done (Missing dependency on python-sphinx)
Your message dated Wed, 14 Dec 2011 17:03:16 + with message-id e1rasee-0006hl...@franck.debian.org and subject line Bug#651597: fixed in fabric 1.3.2-4 has caused the Debian Bug report #651597, regarding Missing dependency on python-sphinx to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 651597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fabric Version: 1.3.2-2 Severity: serious Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! fabric misses a dependency on python-sphinx: /usr/bin/make -C docs html make[2]: Entering directory `/tmp/buildd/fabric-1.3.2/docs' sphinx-build -b html -d _build/doctrees . _build/html make[2]: sphinx-build: Command not found make[2]: *** [html] Error 127 make[2]: Leaving directory `/tmp/buildd/fabric-1.3.2/docs' make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory `/tmp/buildd/fabric-1.3.2' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fabric depends on: ii python2.7.2-9 ii python-nose 1.0.0-1 ii python-paramiko 1.7.7.1-2 ii python-pkg-resources 0.6.24-1 ii python-support1.0.14 fabric recommends no packages. fabric suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk7jP7YACgkQKFvXofIqeU6YlgCfSmq5Nf3113Z4erUxY7wJHdh7 Qx4AnA5NpLCKDJu+TMdAhzYBouYytr9/ =7QTj -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: fabric Source-Version: 1.3.2-4 We believe that the bug you reported is fixed in the latest version of fabric, which is due to be installed in the Debian FTP archive: fabric_1.3.2-4.debian.tar.gz to main/f/fabric/fabric_1.3.2-4.debian.tar.gz fabric_1.3.2-4.dsc to main/f/fabric/fabric_1.3.2-4.dsc fabric_1.3.2-4_all.deb to main/f/fabric/fabric_1.3.2-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 651...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb la...@debian.org (supplier of updated fabric package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 14 Dec 2011 16:41:43 + Source: fabric Binary: fabric Architecture: source all Version: 1.3.2-4 Distribution: unstable Urgency: low Maintainer: Chris Lamb la...@debian.org Changed-By: Chris Lamb la...@debian.org Description: fabric - Simple Pythonic remote deployment tool Closes: 651597 651599 651602 Changes: fabric (1.3.2-4) unstable; urgency=low . * Call install in override_dh_auto_install, not clean. (Closes: #651599) * Add missing python-sphinx dependency. (Closes: #651597, #651602) Checksums-Sha1: a70e96558249899093eb64229690671baa4c051f 1158 fabric_1.3.2-4.dsc f91b1f165e636b3523406cef265b0159845db7da 3993 fabric_1.3.2-4.debian.tar.gz 0366e8452e07708fe3df8b7e03b5f8351e8ff8ec 316818 fabric_1.3.2-4_all.deb Checksums-Sha256: c0763b4b04be64fdd01b66971f74167a582e292ca6faec8769fae241f7fe3b96 1158 fabric_1.3.2-4.dsc c4a2309f570b4be4815a1cd5676b968a092ffe804091a7f38ea664b1843b0c48 3993 fabric_1.3.2-4.debian.tar.gz dd268aa38c5bb11653f0022f7506b97b3fe021487952530f48eb3cac5b53 316818 fabric_1.3.2-4_all.deb Files: 95645ee689743642eba6b83b308fc3e6 1158 net optional fabric_1.3.2-4.dsc baa981be90f47b2faea184599404728e 3993 net optional fabric_1.3.2-4.debian.tar.gz 3547b191c6be04121fa63e7a8a7594ff 316818 net optional fabric_1.3.2-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk7o1CUACgkQ5/8uW2NPmiBYAQCcClEerjRLb7D5UHIJ7qnyVu1T 6+8An3IDfK9W/a+qekPS9FFFyPp380uq =/2P8 -END PGP SIGNATURE- ---End Message---
Bug#651602: marked as done (FTBFS: make[2]: sphinx-build: Command not found)
Your message dated Wed, 14 Dec 2011 17:03:16 + with message-id e1rasee-0006hl...@franck.debian.org and subject line Bug#651597: fixed in fabric 1.3.2-4 has caused the Debian Bug report #651597, regarding FTBFS: make[2]: sphinx-build: Command not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 651597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fabric Version: 1.3.2-3 Severity: serious Fabric fails to build from source: ... copying fabric/contrib/project.py - build/lib.linux-x86_64-2.7/fabric/contrib copying fabric/contrib/__init__.py - build/lib.linux-x86_64-2.7/fabric/contrib copying fabric/contrib/console.py - build/lib.linux-x86_64-2.7/fabric/contrib copying fabric/contrib/django.py - build/lib.linux-x86_64-2.7/fabric/contrib copying fabric/contrib/files.py - build/lib.linux-x86_64-2.7/fabric/contrib /usr/bin/make -C docs html make[2]: Entering directory `/tmp/buildd/fabric-1.3.2/docs' sphinx-build -b html -d _build/doctrees . _build/html make[2]: sphinx-build: Command not found make[2]: *** [html] Error 127 make[2]: Leaving directory `/tmp/buildd/fabric-1.3.2/docs' make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory `/tmp/buildd/fabric-1.3.2' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Ana -- System Information: Versions of packages fabric depends on: ii python-nose 1.0.0-1 ii python-paramiko 1.7.7.1-2 ii python-pkg-resources 0.6.24-1 fabric recommends no packages. Versions of packages fabric suggests: ii libjs-jquery 1.7-1 -- no debconf information ---End Message--- ---BeginMessage--- Source: fabric Source-Version: 1.3.2-4 We believe that the bug you reported is fixed in the latest version of fabric, which is due to be installed in the Debian FTP archive: fabric_1.3.2-4.debian.tar.gz to main/f/fabric/fabric_1.3.2-4.debian.tar.gz fabric_1.3.2-4.dsc to main/f/fabric/fabric_1.3.2-4.dsc fabric_1.3.2-4_all.deb to main/f/fabric/fabric_1.3.2-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 651...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb la...@debian.org (supplier of updated fabric package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 14 Dec 2011 16:41:43 + Source: fabric Binary: fabric Architecture: source all Version: 1.3.2-4 Distribution: unstable Urgency: low Maintainer: Chris Lamb la...@debian.org Changed-By: Chris Lamb la...@debian.org Description: fabric - Simple Pythonic remote deployment tool Closes: 651597 651599 651602 Changes: fabric (1.3.2-4) unstable; urgency=low . * Call install in override_dh_auto_install, not clean. (Closes: #651599) * Add missing python-sphinx dependency. (Closes: #651597, #651602) Checksums-Sha1: a70e96558249899093eb64229690671baa4c051f 1158 fabric_1.3.2-4.dsc f91b1f165e636b3523406cef265b0159845db7da 3993 fabric_1.3.2-4.debian.tar.gz 0366e8452e07708fe3df8b7e03b5f8351e8ff8ec 316818 fabric_1.3.2-4_all.deb Checksums-Sha256: c0763b4b04be64fdd01b66971f74167a582e292ca6faec8769fae241f7fe3b96 1158 fabric_1.3.2-4.dsc c4a2309f570b4be4815a1cd5676b968a092ffe804091a7f38ea664b1843b0c48 3993 fabric_1.3.2-4.debian.tar.gz dd268aa38c5bb11653f0022f7506b97b3fe021487952530f48eb3cac5b53 316818 fabric_1.3.2-4_all.deb Files: 95645ee689743642eba6b83b308fc3e6 1158 net optional fabric_1.3.2-4.dsc baa981be90f47b2faea184599404728e 3993 net optional fabric_1.3.2-4.debian.tar.gz 3547b191c6be04121fa63e7a8a7594ff 316818 net optional fabric_1.3.2-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk7o1CUACgkQ5/8uW2NPmiBYAQCcClEerjRLb7D5UHIJ7qnyVu1T 6+8An3IDfK9W/a+qekPS9FFFyPp380uq =/2P8 -END PGP SIGNATURE- ---End Message---
Bug#651599: marked as done (fabric does not ship any binary)
Your message dated Wed, 14 Dec 2011 17:03:16 + with message-id e1rasee-0006hp...@franck.debian.org and subject line Bug#651599: fixed in fabric 1.3.2-4 has caused the Debian Bug report #651599, regarding fabric does not ship any binary to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 651599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fabric Version: 1.3.2-3 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! `dpkg -L fabric | grep bin` returns nothing. The package is a bit useless. It only contains documentation. Maybe a change in debhelper? - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fabric depends on: ii python-nose 1.0.0-1 ii python-paramiko 1.7.7.1-2 ii python-pkg-resources 0.6.24-1 fabric recommends no packages. Versions of packages fabric suggests: ii libjs-jquery 1.7-1 - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk7jPo8ACgkQKFvXofIqeU5ikACgtB+wrx4MIqFYgX+SckhPbC+1 Sc4An04Yzzov2jdAImKeVFx++m//phr2 =MI2W -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: fabric Source-Version: 1.3.2-4 We believe that the bug you reported is fixed in the latest version of fabric, which is due to be installed in the Debian FTP archive: fabric_1.3.2-4.debian.tar.gz to main/f/fabric/fabric_1.3.2-4.debian.tar.gz fabric_1.3.2-4.dsc to main/f/fabric/fabric_1.3.2-4.dsc fabric_1.3.2-4_all.deb to main/f/fabric/fabric_1.3.2-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 651...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb la...@debian.org (supplier of updated fabric package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 14 Dec 2011 16:41:43 + Source: fabric Binary: fabric Architecture: source all Version: 1.3.2-4 Distribution: unstable Urgency: low Maintainer: Chris Lamb la...@debian.org Changed-By: Chris Lamb la...@debian.org Description: fabric - Simple Pythonic remote deployment tool Closes: 651597 651599 651602 Changes: fabric (1.3.2-4) unstable; urgency=low . * Call install in override_dh_auto_install, not clean. (Closes: #651599) * Add missing python-sphinx dependency. (Closes: #651597, #651602) Checksums-Sha1: a70e96558249899093eb64229690671baa4c051f 1158 fabric_1.3.2-4.dsc f91b1f165e636b3523406cef265b0159845db7da 3993 fabric_1.3.2-4.debian.tar.gz 0366e8452e07708fe3df8b7e03b5f8351e8ff8ec 316818 fabric_1.3.2-4_all.deb Checksums-Sha256: c0763b4b04be64fdd01b66971f74167a582e292ca6faec8769fae241f7fe3b96 1158 fabric_1.3.2-4.dsc c4a2309f570b4be4815a1cd5676b968a092ffe804091a7f38ea664b1843b0c48 3993 fabric_1.3.2-4.debian.tar.gz dd268aa38c5bb11653f0022f7506b97b3fe021487952530f48eb3cac5b53 316818 fabric_1.3.2-4_all.deb Files: 95645ee689743642eba6b83b308fc3e6 1158 net optional fabric_1.3.2-4.dsc baa981be90f47b2faea184599404728e 3993 net optional fabric_1.3.2-4.debian.tar.gz 3547b191c6be04121fa63e7a8a7594ff 316818 net optional fabric_1.3.2-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk7o1CUACgkQ5/8uW2NPmiBYAQCcClEerjRLb7D5UHIJ7qnyVu1T 6+8An3IDfK9W/a+qekPS9FFFyPp380uq =/2P8 -END PGP SIGNATURE- ---End Message---
Bug#651597: marked as done (Missing dependency on python-sphinx)
Your message dated Wed, 14 Dec 2011 17:03:16 + with message-id e1rasee-0006hv...@franck.debian.org and subject line Bug#651602: fixed in fabric 1.3.2-4 has caused the Debian Bug report #651602, regarding Missing dependency on python-sphinx to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 651602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fabric Version: 1.3.2-2 Severity: serious Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! fabric misses a dependency on python-sphinx: /usr/bin/make -C docs html make[2]: Entering directory `/tmp/buildd/fabric-1.3.2/docs' sphinx-build -b html -d _build/doctrees . _build/html make[2]: sphinx-build: Command not found make[2]: *** [html] Error 127 make[2]: Leaving directory `/tmp/buildd/fabric-1.3.2/docs' make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory `/tmp/buildd/fabric-1.3.2' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fabric depends on: ii python2.7.2-9 ii python-nose 1.0.0-1 ii python-paramiko 1.7.7.1-2 ii python-pkg-resources 0.6.24-1 ii python-support1.0.14 fabric recommends no packages. fabric suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk7jP7YACgkQKFvXofIqeU6YlgCfSmq5Nf3113Z4erUxY7wJHdh7 Qx4AnA5NpLCKDJu+TMdAhzYBouYytr9/ =7QTj -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: fabric Source-Version: 1.3.2-4 We believe that the bug you reported is fixed in the latest version of fabric, which is due to be installed in the Debian FTP archive: fabric_1.3.2-4.debian.tar.gz to main/f/fabric/fabric_1.3.2-4.debian.tar.gz fabric_1.3.2-4.dsc to main/f/fabric/fabric_1.3.2-4.dsc fabric_1.3.2-4_all.deb to main/f/fabric/fabric_1.3.2-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 651...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb la...@debian.org (supplier of updated fabric package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 14 Dec 2011 16:41:43 + Source: fabric Binary: fabric Architecture: source all Version: 1.3.2-4 Distribution: unstable Urgency: low Maintainer: Chris Lamb la...@debian.org Changed-By: Chris Lamb la...@debian.org Description: fabric - Simple Pythonic remote deployment tool Closes: 651597 651599 651602 Changes: fabric (1.3.2-4) unstable; urgency=low . * Call install in override_dh_auto_install, not clean. (Closes: #651599) * Add missing python-sphinx dependency. (Closes: #651597, #651602) Checksums-Sha1: a70e96558249899093eb64229690671baa4c051f 1158 fabric_1.3.2-4.dsc f91b1f165e636b3523406cef265b0159845db7da 3993 fabric_1.3.2-4.debian.tar.gz 0366e8452e07708fe3df8b7e03b5f8351e8ff8ec 316818 fabric_1.3.2-4_all.deb Checksums-Sha256: c0763b4b04be64fdd01b66971f74167a582e292ca6faec8769fae241f7fe3b96 1158 fabric_1.3.2-4.dsc c4a2309f570b4be4815a1cd5676b968a092ffe804091a7f38ea664b1843b0c48 3993 fabric_1.3.2-4.debian.tar.gz dd268aa38c5bb11653f0022f7506b97b3fe021487952530f48eb3cac5b53 316818 fabric_1.3.2-4_all.deb Files: 95645ee689743642eba6b83b308fc3e6 1158 net optional fabric_1.3.2-4.dsc baa981be90f47b2faea184599404728e 3993 net optional fabric_1.3.2-4.debian.tar.gz 3547b191c6be04121fa63e7a8a7594ff 316818 net optional fabric_1.3.2-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk7o1CUACgkQ5/8uW2NPmiBYAQCcClEerjRLb7D5UHIJ7qnyVu1T 6+8An3IDfK9W/a+qekPS9FFFyPp380uq =/2P8 -END PGP SIGNATURE- ---End Message---
Bug#651602: marked as done (FTBFS: make[2]: sphinx-build: Command not found)
Your message dated Wed, 14 Dec 2011 17:03:16 + with message-id e1rasee-0006hv...@franck.debian.org and subject line Bug#651602: fixed in fabric 1.3.2-4 has caused the Debian Bug report #651602, regarding FTBFS: make[2]: sphinx-build: Command not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 651602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fabric Version: 1.3.2-3 Severity: serious Fabric fails to build from source: ... copying fabric/contrib/project.py - build/lib.linux-x86_64-2.7/fabric/contrib copying fabric/contrib/__init__.py - build/lib.linux-x86_64-2.7/fabric/contrib copying fabric/contrib/console.py - build/lib.linux-x86_64-2.7/fabric/contrib copying fabric/contrib/django.py - build/lib.linux-x86_64-2.7/fabric/contrib copying fabric/contrib/files.py - build/lib.linux-x86_64-2.7/fabric/contrib /usr/bin/make -C docs html make[2]: Entering directory `/tmp/buildd/fabric-1.3.2/docs' sphinx-build -b html -d _build/doctrees . _build/html make[2]: sphinx-build: Command not found make[2]: *** [html] Error 127 make[2]: Leaving directory `/tmp/buildd/fabric-1.3.2/docs' make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory `/tmp/buildd/fabric-1.3.2' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Ana -- System Information: Versions of packages fabric depends on: ii python-nose 1.0.0-1 ii python-paramiko 1.7.7.1-2 ii python-pkg-resources 0.6.24-1 fabric recommends no packages. Versions of packages fabric suggests: ii libjs-jquery 1.7-1 -- no debconf information ---End Message--- ---BeginMessage--- Source: fabric Source-Version: 1.3.2-4 We believe that the bug you reported is fixed in the latest version of fabric, which is due to be installed in the Debian FTP archive: fabric_1.3.2-4.debian.tar.gz to main/f/fabric/fabric_1.3.2-4.debian.tar.gz fabric_1.3.2-4.dsc to main/f/fabric/fabric_1.3.2-4.dsc fabric_1.3.2-4_all.deb to main/f/fabric/fabric_1.3.2-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 651...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb la...@debian.org (supplier of updated fabric package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 14 Dec 2011 16:41:43 + Source: fabric Binary: fabric Architecture: source all Version: 1.3.2-4 Distribution: unstable Urgency: low Maintainer: Chris Lamb la...@debian.org Changed-By: Chris Lamb la...@debian.org Description: fabric - Simple Pythonic remote deployment tool Closes: 651597 651599 651602 Changes: fabric (1.3.2-4) unstable; urgency=low . * Call install in override_dh_auto_install, not clean. (Closes: #651599) * Add missing python-sphinx dependency. (Closes: #651597, #651602) Checksums-Sha1: a70e96558249899093eb64229690671baa4c051f 1158 fabric_1.3.2-4.dsc f91b1f165e636b3523406cef265b0159845db7da 3993 fabric_1.3.2-4.debian.tar.gz 0366e8452e07708fe3df8b7e03b5f8351e8ff8ec 316818 fabric_1.3.2-4_all.deb Checksums-Sha256: c0763b4b04be64fdd01b66971f74167a582e292ca6faec8769fae241f7fe3b96 1158 fabric_1.3.2-4.dsc c4a2309f570b4be4815a1cd5676b968a092ffe804091a7f38ea664b1843b0c48 3993 fabric_1.3.2-4.debian.tar.gz dd268aa38c5bb11653f0022f7506b97b3fe021487952530f48eb3cac5b53 316818 fabric_1.3.2-4_all.deb Files: 95645ee689743642eba6b83b308fc3e6 1158 net optional fabric_1.3.2-4.dsc baa981be90f47b2faea184599404728e 3993 net optional fabric_1.3.2-4.debian.tar.gz 3547b191c6be04121fa63e7a8a7594ff 316818 net optional fabric_1.3.2-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk7o1CUACgkQ5/8uW2NPmiBYAQCcClEerjRLb7D5UHIJ7qnyVu1T 6+8An3IDfK9W/a+qekPS9FFFyPp380uq =/2P8 -END PGP SIGNATURE- ---End Message---
Bug#652061: elmerfem: FTBFS missing build-dependencvy?
Le mercredi 14 décembre 2011 à 11:58 -0500, Adam C Powell IV a écrit : Hi Christoph, On Wed, 2011-12-14 at 16:01 +0100, Christoph Egger wrote: Package: src:elmerfem Version: 6.1.0.svn.5396.dfsg-3 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the buildds: checking for dseupd_ in -larpack... yes configure: WARNING: No parallel arpack found. checking for pdneupd_ in -lparpack... no checking for HYPRE_IJMatrixCreate in -lHYPRE_IJ_mv... yes checking for dmumps_ in -ldmumps_scotch... yes checking for umfpack_di_defaults in -lumfpack... yes checking for mtc_init in -lmatc... yes configure: error: The MPI version needs parpack. Disabling MPI. checking for main in -lm... yes make: *** [stamp-build] Error 1 Thanks for the report. Hmm, libparpack.so is still there, but doesn't have this symbol. Requires further investigation. I should be able to get to it in the next day or two. hmhm, this is likely to be my fault. We (Debian, Scilab Octave) released a new version of arpack (since upstream is dead) [1]. We applied some patches from gentoo to switch to autotools. It might be the cause of your issue. Do you know which symbol is missing ? Sylvestre [1] http://forge.scilab.org/index.php/p/arpack-ng/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 646886 is important
Processing commands for cont...@bugs.debian.org: severity 646886 important Bug #646886 [src:gnome-online-accounts] FTBFS on kbsd: 'SYS_gettid' undeclared Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 646886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652011: general: Repeated pattern of FHS violation: Dependencies of /sbin and /bin, belong in /lib
Wow, if this sort of bug report is re-evoking questions on the whole
relevance of the historical FHS to modern distros, it does seem that
some real soul searching is in order on the part of the community as
far as the future of where people see Debian/GNU/Linux headed. Begin
with the end in mind, right? Not all roads lead to the same place, and
you choose a path according to where you want to end up.
Throwing my own two cents in: as far as Debian itself goes, I think
this distro ('stable', in particular) has a reputation of being a solid,
stable, rock of confidence that others can build off of and deviate
from. The center should hold, so that if something goes wrong in the
branches, the problem can hopefully be localized as quickly and
conveniently as possible.
I could be wrong, but my (admittedly stereotyped) impression of the
standard use cases is that if you've got someone who DOES want to mount
/usr separately from / (e.g. over NFS or because of a selectively
encrypted LVM), such person is more likely wanting to do so in pure
Debian, rather than, say, in Ubuntu.
In summary, I would argue that Debian's place in the world is such
that it should head down the path of fixing these FHS violations
strictly, rather than the path of loosening the policy. Give the
sys-admins who have been laboring with *nix for a couple decades a
Debian with single user mode in tip-top condition, always behaving as
it should as these foundational old-timers would see it. Enforce a
policy that anything being put into /sbin or /bin must pass the ldd
test. If a dependency is in /usr/lib then negotiations have to be made
to reach an agreement to either downgrade the binary to /usr/{s,}bin
or upgrade the library to /lib. (In the case of downgrading the
binary, you can say that the user of the Debian package bears the
responsibility to have ensured that the executables he personally
considers essential in his own context were accessible where he would
need them when he would need them. But the distro itself should take
responsibility for being CONSISTENT, and thus should not say, Here's
something available to you in /sbin---oh, but you can't actually use it
from there (so to speak).)
If someone wants a distro with a (totally?, partially?) revamped,
simplified, filesystem hierarchy that will make Linux less convoluted
and even more accessible to the wide modern market, then let them go
wild in a Debian derivative. Let Debian be the solid, faithful dad they
can go back to for advice or recovery if and when they fall or need it.
-Zach
PS Sorry if my inspirational speech here is a repetition of recent
discussion on devel lists which I don't participate in. But heck,
nobody's closed my bug report yet, so now you've got my two cents thrown
in there!
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652094: mysql-mmm-tools: missing dependancy on libpath-class-perl
Package: mysql-mmm-tools Version: 2.2.1-1 Severity: grave Justification: renders package unusable # /usr/sbin/mmm_backup Can't locate Path/Class.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at /usr/share/perl5/MMM/Tools/Tools.pm line 6. BEGIN failed--compilation aborted at /usr/share/perl5/MMM/Tools/Tools.pm line 6. Compilation failed in require at /usr/sbin/mmm_backup line 16. BEGIN failed--compilation aborted at /usr/sbin/mmm_backup line 16 solution is: apt-get install libpath-class-perl -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (990, 'stable'), (600, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mysql-mmm-tools depends on: ii libdbd-mysql-perl 4.020-1+b1 Perl5 database interface to the My ii libdbi-perl 1.616-1+b2 Perl Database Interface (DBI) ii mysql-mmm-common 2.2.1-1Multi-Master Replication Manager f mysql-mmm-tools recommends no packages. mysql-mmm-tools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649175: I Need Your help
-- Dear Friend,I have a very important and vital information for you which will benefit us and you have to know about it. Please contact me through my email so we can talk about it; Dr. Fatih Baja
Bug#652070: [Anfrage#: 4222203] Bug#652070: awstats: virtualname / SiteDomain [...]
Sehr geehrte/r Anfrager/in, Ihre Mail mit dem Absender Sergey B Kirpichev haben wir empfangen. Vielen Dank für Ihre Anfrage. Sergey B Kirpichev skirpic...@gmail.com schrieb: tag 652070 +moreinfo thanks - AWstats runs fine for months. - Yesterday apt updated Perl. - Now AWSTats directives %virtualname and SiteDomain accepts nearly all records of the logfile, even with an arbirtray string as SiteDomain, for example SiteDomain=fhawefruzasdfh Please, test the patch from bug #650492: http://anonscm.debian.org/gitweb/?p=collab- maint/awstats.git;a=blob;f=debian/patches/1018_perl5-14.patch if it fixes your problem. Thank you for this patch - it fixes the problem. Mit freundlichen Grüßen Andreas Rittershofer -- Systembetreuung des Landesbildungsservers Baden-Württemberg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652097: sysvinit: breaks system on reboot
Package: sysvinit Version: 2.88dsf-14 Severity: critical Justification: breaks the whole system Dear Maintainer, The new sysv packages in experimental look like they are breaking my system. reboot via # shutdown -r now, or # shutdown -h now, do not work, and the only way to reboot my machine is with magic-sysrq-b or hard reset. When the machine comes up again, login is displayed way too early (~3 seconds after grub), and once I login, the system seems to be severly broken... nothing besides root is mounted, hostname is not displayed, network has not been brought up, etc... If anyone else is hit with this, and you don't have sysv packages from unstable already in your cache for downgrading, the only way I've found is to chroot into your system via a livecd and downgrade that way to get your machine fully functional again. *note: System information was obtained with sysv packages at version 2.88dsf-13.13 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sysvinit depends on: ii initscripts 2.88dsf-13.13 ii libc6 2.13-22 ii libselinux1 2.1.0-4 ii libsepol1 2.1.0-1.1 ii sysv-rc 2.88dsf-13.13 ii sysvinit-utils 2.88dsf-13.13 sysvinit recommends no packages. sysvinit suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648744: zfsutils migration (Re: new ZFS installs completely broken in Wheezy/Sid)
El 13 de desembre de 2011 19:07, Arno Töll deb...@toell.net ha escrit: Note, I didn't find any /real/ problem when using zfsutils 8.3 with a 8.2 kernel. I didn't try it with 8.1 but I don't see why it would be different there. Well, zfs list fails with EINVAL on 8.1 kernel, and I recall seeing zpool status report non-sense in some combinations. Is there a point in having our users test yet another combination that isn't supported by upstream, fix the problems we find, etc? Our userbase is very small and noticeably bad at finding problems. If we do this IMHO there should be a benefit. If we could find a workaround by emulating this volinit call when an older kernel is detected, I guess we could happily use newer utils along with older kernels. I haven't looked at the code, but that's probably just some ioctl we could emulate easily. Doesn't hurt to implement that, it even helps for people using chroots, but removing the Breaks and encouraging users to test v28 userland with v15 kernel is a very different story. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652070: marked as done (awstats: virtualname / SiteDomain accepts nearly everything)
Your message dated Wed, 14 Dec 2011 19:02:12 + with message-id e1rau5k-0004gx...@franck.debian.org and subject line Bug#652070: fixed in awstats 7.0~dfsg-4 has caused the Debian Bug report #652070, regarding awstats: virtualname / SiteDomain accepts nearly everything to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 652070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: awstats Version: 7.0~dfsg-3 Severity: grave Justification: renders package unusable 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 *** - AWstats runs fine for months. - Yesterday apt updated Perl. - Now AWSTats directives %virtualname and SiteDomain accepts nearly all records of the logfile, even with an arbirtray string as SiteDomain, for example SiteDomain=fhawefruzasdfh -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/1 CPU core) 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 awstats depends on: ii perl 5.14.2-6 Versions of packages awstats recommends: ii coreutils 8.13-3 ii libnet-xwhois-perl 0.90-3 Versions of packages awstats suggests: ii apache2 2.2.21-3 ii apache2-mpm-prefork [httpd] 2.2.21-3 ii libgeo-ipfree-perl none ii libnet-dns-perl none ii libnet-ip-perl none ii liburi-perl 1.59-1 -- Configuration Files: /etc/awstats/awstats.conf changed [not included] /etc/awstats/awstats.conf.local changed [not included] -- no debconf information ---End Message--- ---BeginMessage--- Source: awstats Source-Version: 7.0~dfsg-4 We believe that the bug you reported is fixed in the latest version of awstats, which is due to be installed in the Debian FTP archive: awstats_7.0~dfsg-4.debian.tar.gz to main/a/awstats/awstats_7.0~dfsg-4.debian.tar.gz awstats_7.0~dfsg-4.dsc to main/a/awstats/awstats_7.0~dfsg-4.dsc awstats_7.0~dfsg-4_all.deb to main/a/awstats/awstats_7.0~dfsg-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 652...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sergey B Kirpichev skirpic...@gmail.com (supplier of updated awstats package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 14 Dec 2011 22:36:06 +0400 Source: awstats Binary: awstats Architecture: source all Version: 7.0~dfsg-4 Distribution: unstable Urgency: low Maintainer: Sergey B Kirpichev skirpic...@gmail.com Changed-By: Sergey B Kirpichev skirpic...@gmail.com Description: awstats- powerful and featureful web server log analyzer Closes: 650492 652070 Changes: awstats (7.0~dfsg-4) unstable; urgency=low . * Apply some compatibility fixes for perl 5.14: introduce 1018_perl5- 14.patch (Closes: #650492, #652070, thanks to Atsuhito Kohda) * Fixed Bug-Debian info for 016_downloads_list_page.patch Checksums-Sha1: 17b67c41d8c740760144805dd5b832cee6253f19 1968 awstats_7.0~dfsg-4.dsc a5ec048cf4268d5feac3b5fe485b353e14bf8e98 51554 awstats_7.0~dfsg-4.debian.tar.gz 50399bf699a5f0c2befdbfe950ca134bfb1a38ad 1050064 awstats_7.0~dfsg-4_all.deb Checksums-Sha256: 2fa13769e1dcd75abb961f4b78671274f4f646133d2456d5137c5951baf8c2af 1968 awstats_7.0~dfsg-4.dsc 4fada2f35c1bae73d624b49ef31fab5aa57748bba55d0a1758d8bca7ab68955a 51554 awstats_7.0~dfsg-4.debian.tar.gz 2f7ed52a4026da639c0b932a5cbba17dd5c03d7e28e6b8d6fe63d6865e95e481 1050064 awstats_7.0~dfsg-4_all.deb Files: 57c72c58eee23a63518c1eec205fabc7 1968 web optional awstats_7.0~dfsg-4.dsc 2b3e301a258fdb77297ae69bb0fcb09e 51554 web optional awstats_7.0~dfsg-4.debian.tar.gz 787c5b347c1e23964436c3f998ee7f33 1050064 web optional awstats_7.0~dfsg-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: # Wed Dec 14 19:03:25 UTC 2011 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: qapt tags 635380 + pending Bug #635380 [wnpp] ITP: qapt -- Qt wrapper around the libapt-pkg library and APT implementation Added tag(s) pending. # Source package in NEW: xen-api-libs tags 646727 + pending Bug #646727 [wnpp] ITP: xapi-libs - Libraries for XCP's XenAPI Toolstack Added tag(s) pending. # Source package in NEW: shogun tags 647753 + pending Bug #647753 [shogun] Please rebuild shogun as liblzma has been transition to liblzma5 Added tag(s) pending. # Source package in NEW: shogun tags 645249 + pending Bug #645249 [src:shogun] shogun: FTBFS: modular wrappers too large to compile Added tag(s) pending. # Source package in NEW: wader tags 492875 + pending Bug #492875 [wnpp] ITP: wader -- 3G daemon implementing ModemManager API Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 492875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492875 645249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645249 647753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647753 646727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646727 635380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652061: elmerfem: FTBFS missing build-dependencvy?
Hi Sylvestre, On Wed, 2011-12-14 at 18:50 +0100, Sylvestre Ledru wrote: Le mercredi 14 décembre 2011 à 11:58 -0500, Adam C Powell IV a écrit : Hi Christoph, On Wed, 2011-12-14 at 16:01 +0100, Christoph Egger wrote: Package: src:elmerfem Version: 6.1.0.svn.5396.dfsg-3 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the buildds: checking for dseupd_ in -larpack... yes configure: WARNING: No parallel arpack found. checking for pdneupd_ in -lparpack... no checking for HYPRE_IJMatrixCreate in -lHYPRE_IJ_mv... yes checking for dmumps_ in -ldmumps_scotch... yes checking for umfpack_di_defaults in -lumfpack... yes checking for mtc_init in -lmatc... yes configure: error: The MPI version needs parpack. Disabling MPI. checking for main in -lm... yes make: *** [stamp-build] Error 1 Thanks for the report. Hmm, libparpack.so is still there, but doesn't have this symbol. Requires further investigation. I should be able to get to it in the next day or two. hmhm, this is likely to be my fault. We (Debian, Scilab Octave) released a new version of arpack (since upstream is dead) [1]. We applied some patches from gentoo to switch to autotools. It might be the cause of your issue. Do you know which symbol is missing ? From the build log, configure is looking for dseupd_ but I don't know all of the symbols which Elmer uses. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part
Bug#652025: marked as done (illuminat: Build-Conflicts on libmpich2-dev to strict)
Your message dated Wed, 14 Dec 2011 14:28:56 -0500 with message-id 1323890937.23861.3.camel@workhorse and subject line Self-contradictory bug has caused the Debian Bug report #652025, regarding illuminat: Build-Conflicts on libmpich2-dev to strict to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 652025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: illuminator Version: 0.11.0-8.1 Severity: serious Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: Alexander Reichle-Schmehl toli...@debian.org See https://buildd.debian.org/status/fetch.php?pkg=illuminatorarch=sparcver=0.11.0-8.1stamp=1323062646 /usr/lib/lam/bin/mpicc -g -O2 -o .libs/tsview tsview-tsview.o libluminate/.libs/libluminate.so -lpetsc -lncurses -lhistory -lreadline /usr/bin/ld: tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte' /usr/bin/ld: note: 'lam_mpi_byte' is defined in DSO /usr/lib/liblam.so.4 so try adding it to the linker command line /usr/lib/liblam.so.4: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [tsview] Error 1 Cheers, Julien ---End Message--- ---BeginMessage--- This bug should never have been cloned -- as the cloning message indicates, it is impossible to satisfy the Build-Depends on mpi-default-dev which depends on libmpich2-dev, and Build-Conflict with libmpich2-dev. I'm about to upload a better fix for illuminator. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part ---End Message---
Bug#652035: wicd-curses: Crashs when running (Python UnicodeDecodeError)
Hello, On Wed, 14 Dec 2011 12:45:08 +0100, Florian Birée wrote: wicd-curses always crashs when I start the program. The error is: Traceback (most recent call last): File /usr/share/wicd/curses/wicd-curses.py, line 1063, in module main() File /usr/share/wicd/curses/wicd-curses.py, line 995, in main ui.run_wrapper(run) File /usr/lib/python2.7/dist-packages/urwid/raw_display.py, line 237, in run_wrapper return fn() File /usr/share/wicd/curses/wicd-curses.py, line 89, in wrapper return func(*args, **kargs) File /usr/share/wicd/curses/wicd-curses.py, line 1003, in run app = appGUI() File /usr/share/wicd/curses/wicd-curses.py, line 551, in __init__ self.update_netlist(force_check=True,firstrun=True) File /usr/share/wicd/curses/wicd-curses.py, line 89, in wrapper return func(*args, **kargs) File /usr/share/wicd/curses/wicd-curses.py, line 670, in update_netlist wiredL,wlessL = gen_network_list() File /usr/share/wicd/curses/wicd-curses.py, line 177, in gen_network_list label = NetLabel(network_id,is_active) File /usr/share/wicd/curses/wicd-curses.py, line 358, in __init__ self.stren,self.essid,self.encrypt,self.bssid,self.mode,self.channel) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 5: ordinal not in range(128) Do you have any unicode ESSID in /etc/wicd/wireless-settings.conf? Is it the ESSID you chose to automatically connect to? Thanks, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Bug#615120: marked as done (eglibc: alloca memory corruption)
Your message dated Wed, 14 Dec 2011 19:55:32 + with message-id e1rauvm-0002ma...@franck.debian.org and subject line Bug#615120: fixed in eglibc 2.11.3-1 has caused the Debian Bug report #615120, regarding eglibc: alloca memory corruption to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 615120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: eglibc version: 2.11.2-10 severity: grave tag: security A memory corruption issue has been disclosed for eglibc [0]. I've checked, and lenny (glibc), squeeze, and sid are affected by the poc. experimental is not. According to the report, this permits arbitrary code execution. [0] http://seclists.org/fulldisclosure/2011/Feb/635 ---End Message--- ---BeginMessage--- Source: eglibc Source-Version: 2.11.3-1 We believe that the bug you reported is fixed in the latest version of eglibc, which is due to be installed in the Debian FTP archive: eglibc-source_2.11.3-1_all.deb to main/e/eglibc/eglibc-source_2.11.3-1_all.deb eglibc_2.11.3-1.diff.gz to main/e/eglibc/eglibc_2.11.3-1.diff.gz eglibc_2.11.3-1.dsc to main/e/eglibc/eglibc_2.11.3-1.dsc eglibc_2.11.3.orig.tar.gz to main/e/eglibc/eglibc_2.11.3.orig.tar.gz glibc-doc_2.11.3-1_all.deb to main/e/eglibc/glibc-doc_2.11.3-1_all.deb libc-bin_2.11.3-1_amd64.deb to main/e/eglibc/libc-bin_2.11.3-1_amd64.deb libc-dev-bin_2.11.3-1_amd64.deb to main/e/eglibc/libc-dev-bin_2.11.3-1_amd64.deb libc6-dbg_2.11.3-1_amd64.deb to main/e/eglibc/libc6-dbg_2.11.3-1_amd64.deb libc6-dev-i386_2.11.3-1_amd64.deb to main/e/eglibc/libc6-dev-i386_2.11.3-1_amd64.deb libc6-dev_2.11.3-1_amd64.deb to main/e/eglibc/libc6-dev_2.11.3-1_amd64.deb libc6-i386_2.11.3-1_amd64.deb to main/e/eglibc/libc6-i386_2.11.3-1_amd64.deb libc6-pic_2.11.3-1_amd64.deb to main/e/eglibc/libc6-pic_2.11.3-1_amd64.deb libc6-prof_2.11.3-1_amd64.deb to main/e/eglibc/libc6-prof_2.11.3-1_amd64.deb libc6-udeb_2.11.3-1_amd64.udeb to main/e/eglibc/libc6-udeb_2.11.3-1_amd64.udeb libc6_2.11.3-1_amd64.deb to main/e/eglibc/libc6_2.11.3-1_amd64.deb libnss-dns-udeb_2.11.3-1_amd64.udeb to main/e/eglibc/libnss-dns-udeb_2.11.3-1_amd64.udeb libnss-files-udeb_2.11.3-1_amd64.udeb to main/e/eglibc/libnss-files-udeb_2.11.3-1_amd64.udeb locales-all_2.11.3-1_amd64.deb to main/e/eglibc/locales-all_2.11.3-1_amd64.deb locales_2.11.3-1_all.deb to main/e/eglibc/locales_2.11.3-1_all.deb nscd_2.11.3-1_amd64.deb to main/e/eglibc/nscd_2.11.3-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 615...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno aure...@debian.org (supplier of updated eglibc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 13 Dec 2011 11:23:12 +0100 Source: eglibc Binary: libc-bin libc-dev-bin glibc-doc eglibc-source locales locales-all nscd libc6 libc6-dev libc6-dbg libc6-prof libc6-pic libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-prof libc6.1-pic libc6.1-udeb libc0.3 libc0.3-dev libc0.3-dbg libc0.3-prof libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev libc0.1-dbg libc0.1-prof libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc64 libc6-dev-sparc64 libc6-s390x libc6-dev-s390x libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 libc6-dev-ppc64 libc6-mipsn32 libc6-dev-mipsn32 libc6-mips64 libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-sparcv9b libc6-i686 libc6-xen libc0.1-i686 libc0.3-i686 libc0.3-xen libc6.1-alphaev67 libnss-dns-udeb libnss-files-udeb Architecture: source all amd64 Version: 2.11.3-1 Distribution: stable Urgency: low Maintainer: Aurelien Jarno aure...@debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: eglibc-source - Embedded GNU C Library: sources glibc-doc - Embedded GNU C Library: Documentation libc-bin - Embedded GNU C Library: Binaries libc-dev-bin - Embedded GNU C Library: Development binaries libc0.1- Embedded GNU C Library: Shared libraries libc0.1-dbg - Embedded GNU C Library: detached debugging symbols libc0.1-dev - Embedded GNU C Library: Development Libraries and Header Files libc0.1-dev-i386 - Embedded GNU
Bug#652097: sysvinit: breaks system on reboot
On Wed, Dec 14, 2011 at 12:36:50PM -0600, Brian Paterni wrote: The new sysv packages in experimental look like they are breaking my system. Sorry to hear that. Knowing what went wrong here would help correct it. I'm running it without issues, but that's not to say your system is not different in some way. reboot via # shutdown -r now, or # shutdown -h now, do not work, and the only way to reboot my machine is with magic-sysrq-b or hard reset. When the machine comes up again, login is displayed way too early (~3 seconds after grub), and once I login, the system seems to be severly broken... nothing besides root is mounted, hostname is not displayed, network has not been brought up, etc... When you upgraded the packages, did you install all of sysvinit, sysvinit-utils, sysv-rc and initscripts, or just a subset? When it upgraded the conffiles in /etc, did it prompt whether to keep your version or install the new maintainer version? the only way I've found is to chroot into your system via a livecd and downgrade that way to get your machine fully functional again. When you downgraded, which package(s) did you downgrade? As above, did you do anything at any conffile prompts? Both the /lib/init/rw change and the /etc/mtab change only take proper effect after reboot, so I'm surprised that either of these could cause problems shutting down. When you rebooted, was /etc/mtab a file or a symlink; if it was a symlink, what was it pointing to? If you could, it would be great if you could upgrade to the experimental versions and check these things. It would also be great if you could identify what's going wrong at startup, and where. Is this an issue with insserv affecting the script ordering? Does insserv -v report anything? Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652011: general: Repeated pattern of FHS violation: Dependencies of /sbin and /bin, belong in /lib
On Wed, Dec 14, 2011 at 12:53:24PM -0500, Zachary Harris wrote:
Throwing my own two cents in: as far as Debian itself goes, I think
this distro ('stable', in particular) has a reputation of being a solid,
stable, rock of confidence that others can build off of and deviate
from. The center should hold, so that if something goes wrong in the
branches, the problem can hopefully be localized as quickly and
conveniently as possible.
At the same time, this does not mean that Debian should never change.
Do you have any concrete answers to the questions posed?
Merging / and /usr (in either direction) would always result in a
system with compatibility links. It's not like anything would be
broken by the change--all the paths available now would continue to
be available.
I could be wrong, but my (admittedly stereotyped) impression of the
standard use cases is that if you've got someone who DOES want to mount
/usr separately from / (e.g. over NFS or because of a selectively
encrypted LVM), such person is more likely wanting to do so in pure
Debian, rather than, say, in Ubuntu.
This is a bit beside the point. People keep bringing up mounting /usr
over NFS. No one to date has provided a sensible use case for it.
This is because old timers (or whoever) have failed to notice a
fundamental flaw: *package management does not work with a shared /usr*.
On a Debian there are really only two categories for partitions:
those under the control of the package manager, and those which
are not (user data etc.). Does it make sense to split package-managed
files over multiple partitions? (other than /var)
This is *the* key point. Under a package managed distribution /
and /usr are part of a *managed whole*. They can't exist separately,
even if they are on different partitions, mounted over NFS, or
whatever. It's fine that such things /work/, but we do need to
question /why/ one would do such a thing. If you're mounting /usr
over NFS, the real question is why aren't you mounting / over NFS,
which also then includes /usr?. Mounting /usr separately makes no
sense *at all*.
The same argument applies to encryption. / and /usr both contain a
selection of programs, libraries etc. If you're encrypting one, why
would you not encrypt all of it? And the same for mounting read-only.
The question that needs answering is this:
what are the reasons, today, for a separate /usr?
Excluding historical practice. What real function does it have?
Does it have any reason to continue to exist?
And regarding the LSB: I checked, and it would be entirely compliant
for Debian to merge the two.
Enforce a
policy that anything being put into /sbin or /bin must pass the ldd
test. If a dependency is in /usr/lib then negotiations have to be made
to reach an agreement to either downgrade the binary to /usr/{s,}bin
or upgrade the library to /lib. (In the case of downgrading the
binary, you can say that the user of the Debian package bears the
responsibility to have ensured that the executables he personally
considers essential in his own context were accessible where he would
need them when he would need them. But the distro itself should take
responsibility for being CONSISTENT, and thus should not say, Here's
something available to you in /sbin---oh, but you can't actually use it
from there (so to speak).)
The problem here is, can we /be/ consistent? What is one system's
essential package required for bringing up a working system is
someone else's occasionally-used tool that's not important at all.
Yet both might be required to be on the rootfs. We can't be all
things to all people in the current state. But unification /would/
*guarantee* things would always work and be consistent: every
program and library would always be right there on the rootfs.
The status quo is a best effort. Things sometimes break, and
there's an continuing migration of essential packages to the
rootfs. Given that a modern initramfs can mount pretty much any
filesystem, either locally or over a network, what's the *real*
reason for a separate /usr? It's certainly not for any booting-
related reason.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`-GPG Public Key: 0x25BFB848 Please GPG sign your mail.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651452: marked as done (illuminator: FTBFS on archs where petsc uses liblam (tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte'))
Your message dated Wed, 14 Dec 2011 21:05:44 + with message-id e1raw1i-00017z...@franck.debian.org and subject line Bug#651452: fixed in illuminator 0.11.0-12 has caused the Debian Bug report #651452, regarding illuminator: FTBFS on archs where petsc uses liblam (tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte') to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 651452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651452 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: illuminator Version: 0.11.0-8.1 Severity: serious Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: Alexander Reichle-Schmehl toli...@debian.org See https://buildd.debian.org/status/fetch.php?pkg=illuminatorarch=sparcver=0.11.0-8.1stamp=1323062646 /usr/lib/lam/bin/mpicc -g -O2 -o .libs/tsview tsview-tsview.o libluminate/.libs/libluminate.so -lpetsc -lncurses -lhistory -lreadline /usr/bin/ld: tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte' /usr/bin/ld: note: 'lam_mpi_byte' is defined in DSO /usr/lib/liblam.so.4 so try adding it to the linker command line /usr/lib/liblam.so.4: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[3]: *** [tsview] Error 1 Cheers, Julien ---End Message--- ---BeginMessage--- Source: illuminator Source-Version: 0.11.0-12 We believe that the bug you reported is fixed in the latest version of illuminator, which is due to be installed in the Debian FTP archive: illuminator-demo_0.11.0-12_amd64.deb to main/i/illuminator/illuminator-demo_0.11.0-12_amd64.deb illuminator-doc_0.11.0-12_all.deb to main/i/illuminator/illuminator-doc_0.11.0-12_all.deb illuminator_0.11.0-12.debian.tar.gz to main/i/illuminator/illuminator_0.11.0-12.debian.tar.gz illuminator_0.11.0-12.dsc to main/i/illuminator/illuminator_0.11.0-12.dsc libluminate-dev_0.11.0-12_amd64.deb to main/i/illuminator/libluminate-dev_0.11.0-12_amd64.deb libluminate7_0.11.0-12_amd64.deb to main/i/illuminator/libluminate7_0.11.0-12_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 651...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam C. Powell, IV hazel...@debian.org (supplier of updated illuminator package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 14 Dec 2011 14:23:54 -0500 Source: illuminator Binary: libluminate-dev libluminate7 illuminator-doc illuminator-demo Architecture: source all amd64 Version: 0.11.0-12 Distribution: unstable Urgency: low Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Adam C. Powell, IV hazel...@debian.org Description: illuminator-demo - Illuminator Distributed Visualization Library: demos illuminator-doc - Illuminator Distributed Visualization Library: documentation libluminate-dev - Illuminator Distributed Visualization Library: development files libluminate7 - Illuminator Distributed Visualization Library: shared library Closes: 651452 Changes: illuminator (0.11.0-12) unstable; urgency=low . * Removed LAM-specific code (LAM is deprecated), replaced it with -lmpi (should be unnecessary due to -lpetsc) (closes: #651452). Checksums-Sha1: 3e6ca25f3d1f2c992e725781ce72e182704c561c 1803 illuminator_0.11.0-12.dsc f5558e6c1ce4524511492be09aad098aef39aef4 10805 illuminator_0.11.0-12.debian.tar.gz 6e404cc61e112911d637b4af1cb4ffa582409a68 1125328 illuminator-doc_0.11.0-12_all.deb 27eead131bd70959075cc17582ae48b6919d4617 49518 libluminate-dev_0.11.0-12_amd64.deb d659d55891531a0ffde05d997daaeec1a4d45c32 43452 libluminate7_0.11.0-12_amd64.deb 9f4cd6f776c959f667c73a68fc31bed6be811df1 91180 illuminator-demo_0.11.0-12_amd64.deb Checksums-Sha256: b07acd8d2d103634ee1c0731b8ea4df7e28b36c5390ad03efc6c55d260ea5741 1803 illuminator_0.11.0-12.dsc 8b8f5774a91dc9eca8bdacf50bdaf22df3f79e4b1ea73263d94813287365c808 10805 illuminator_0.11.0-12.debian.tar.gz abfe65a07f931b8c66c890c46246cb720109e18e425b36040034e60d3c9ceac0 1125328 illuminator-doc_0.11.0-12_all.deb 0b6340be789dc8474ace6e99b84027c8133dc66fb568cb191047e18186bc2d86 49518 libluminate-dev_0.11.0-12_amd64.deb
Bug#652011: Repeated pattern of FHS violation: Dependencies of /sbin and /bin, belong in /lib
Roger Leigh wrote: The question that needs answering is this: what are the reasons, today, for a separate /usr? No, I don't think an answer to that precise question today would be especially helpful. As far as I can tell, it is not especially unsensible to use separate partitions for /usr, /etc, /var, /boot, and /opt. And whether it is sensible or not, unless you have a tool in mind that will automatically change the partitioning scheme of a running system, that's not going to help udev or crda very much. An obvious question to answer to help these programs is whether it makes sense to make /usr a separate partition and not mount it before starting init. An even more obvious question is where is the patch for initramfs-tools?. ;-) [...] The same argument applies to encryption. / and /usr both contain a selection of programs, libraries etc. If you're encrypting one, why would you not encrypt all of it? And the same for mounting read-only. Regarding mounting read-only: files in /etc change far more often than files in /usr/bin, for one thing. Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652109: python-nautilus: Cannot be initialized by Nautilus
Package: python-nautilus Version: 1.1-2 Severity: grave Tags: upstream Justification: renders package unusable Hello, since update of python-nautilus to version 1.1-2, it cannot be initialized by Nautilus, rendering applications using it useless. When running nautilus, the following messages appears : (nautilus:6756): Nautilus-Python-WARNING **: pygobject initialization failed (nautilus:6756): Nautilus-Python-WARNING **: nautilus_python_init_python failed Nautilus is then launched and seems to work properly, excepted that extensions relying on this library (e.g. nautilus-compare) have disappeared (it is as if they were not installed). Regards, Louis -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-486 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-nautilus depends on: ii gir1.2-nautilus-3.0 3.0.2-4 ii libatk1.0-0 2.2.0-2 ii libc6 2.13-21 ii libcairo-gobject2 1.10.2-6.1 ii libcairo2 1.10.2-6.1 ii libfontconfig1 2.8.0-3 ii libfreetype62.4.8-1 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-02.30.2-4 ii libgtk-3-0 3.2.2-3 ii libnautilus-extension1a 3.0.2-4 ii libpango1.0-0 1.29.4-2 ii libpython2.72.7.2-8 ii python-gobject [python-gi] 2.28.6-5 python-nautilus recommends no packages. python-nautilus suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634419: marked as done (libphone-ui-shr: FTBFS: util/ui-utils.c:505:2: error: implicit declaration of function 'elm_list_horizontal_mode_set' [-Werror=implicit-function-declaration])
Your message dated Wed, 14 Dec 2011 21:17:49 + with message-id e1rawcz-0002tq...@franck.debian.org and subject line Bug#634419: fixed in libphone-ui-shr 0.1+git20110827-1 has caused the Debian Bug report #634419, regarding libphone-ui-shr: FTBFS: util/ui-utils.c:505:2: error: implicit declaration of function 'elm_list_horizontal_mode_set' [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 634419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libphone-ui-shr Version: 0.1+git20100726-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../src/util -I../src/widget -I../src/view -DDATADIR=\/usr/share\ -DPKGDATADIR=\/usr/share/libphone-ui-shr\ -DPACKAGE=\libphone-ui-shr\ -DLOCALEDIR=\/usr/share/locale\ -DG_LOG_DOMAIN=\libphone-ui-shr\ -I/usr/include/freetype2 -I/usr/include/evas-1 -I/usr/include/eet-1 -I/usr/include/fribidi -I/usr/include/eina-1 -I/usr/include/eina-1/eina -I/usr/include/ecore-1 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/edje-1 -I/usr/include/lua5.1 -I/usr/include/embryo-1 -I/usr/include/elementary-0 -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/phoneui -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/fso-glib -I/usr/include/fsoframework-2.0 -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/fso-glib -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/fsoframework-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/phone-utils -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g3 -Wall -Wextra -Werror -g -O2 -g -O2 -Wall -c -o ui-utils.lo `test -f 'util/ui-utils.c' || echo './'`util/ui-utils.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../src/util -I../src/widget -I../src/view -DDATADIR=\/usr/share\ -DPKGDATADIR=\/usr/share/libphone-ui-shr\ -DPACKAGE=\libphone-ui-shr\ -DLOCALEDIR=\/usr/share/locale\ -DG_LOG_DOMAIN=\libphone-ui-shr\ -I/usr/include/freetype2 -I/usr/include/evas-1 -I/usr/include/eet-1 -I/usr/include/fribidi -I/usr/include/eina-1 -I/usr/include/eina-1/eina -I/usr/include/ecore-1 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/edje-1 -I/usr/include/lua5.1 -I/usr/include/embryo-1 -I/usr/include/elementary-0 -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/phoneui -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/fso-glib -I/usr/include/fsoframework-2.0 -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/fso-glib -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/fsoframework-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/phone-utils -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g3 -Wall -Wextra -Werror -g -O2 -g -O2 -Wall -c util/ui-utils.c -fPIC -DPIC -o .libs/ui-utils.o util/ui-utils.c: In function 'ui_utils_view_inwin_list': util/ui-utils.c:505:2: error: implicit declaration of function 'elm_list_horizontal_mode_set' [-Werror=implicit-function-declaration] cc1: all warnings being treated as errors make[3]: *** [ui-utils.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/07/18/libphone-ui-shr_0.1+git20100726-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source:
Bug#620960: RFS: inspircd
Le samedi 03 décembre 2011 à 11:39 +0100, Jan Lübbe a écrit : Hi! Hi, On Tue, 2011-11-01 at 22:00 +0100, Guillaume Delacour wrote: To access further information about this package, please visit the following URL: http://mentors.debian.net/package/inspircd Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/inspircd/inspircd_2.0.5-1.dsc It seems you've replaced that package with a new one on 2011-11-30. Did you want to that one uploaded, too? Yes, the package on mentors (2011-11-30) is the package i want to upload in the archive (i've forgot to include some stuff a few days ago and regenerate/reupload it on mentors). From the changelog it seems that you intend to maintain it as a pkg-irc team member, so I'd offer to review and upload it if you don't find a sponsor in your team. Absolutely yes, i didn't find any sponsor on the team (which have really only a few active members and not all are DD). I think we have to update inspircd before Wheezy freeze unless it will be removed as obsolete version. Best regards, Jan -- Guillaume Delacour g...@iroqwa.org signature.asc Description: Ceci est une partie de message numériquement signée
Bug#652011: Repeated pattern of FHS violation: Dependencies of /sbin and /bin, belong in /lib
Two clarifications: Jonathan Nieder wrote: Roger Leigh wrote: The question that needs answering is this: what are the reasons, today, for a separate /usr? No, I don't think an answer to that precise question today would be especially helpful. I'd like to apologize for this response. Hearing use cases is always welcome, especially when they are given in the spirit of being helpful rather than defensiveness. As far as I can tell, it is not especially unsensible to use separate partitions for /usr, /etc, /var, /boot, and /opt. It occured to me too late that it might sound like I am saying a /etc partition separate from / can work. By separate I only meant distinct (i.e., the /usr, /etc, /var, etc inodes all coming from different mounts). I also think I misunderstood your message. What kind of unification are you advocating? Fedora's setup, for example, allows /usr to be a separate filesystem. Sorry for the noise, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642476: marked as done (postfix: FTBFS on Linux 3 due to missing multiarch search path)
Your message dated Wed, 14 Dec 2011 22:43:05 +0100 with message-id 20111214214305.ga8...@radis.cristau.org and subject line Re: Bug#642476: postfix: FTBFS on Linux 3 due to missing multiarch search path has caused the Debian Bug report #642476, regarding postfix: FTBFS on Linux 3 due to missing multiarch search path to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 642476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: postfix Version: 2.8.4-1 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) User: debian-d...@lists.debian.org Usertags: multiarch [Note: This is a separate bug from #637565, which appears to be fixed in 2.8.4.] Dear Maintainer, Version 2.8.4 fails to build on machines using Linux 3.x with the following error message: gcc -Wmissing-prototypes -Wformat -DDEBIAN -DMAX_DYNAMIC_MAPS -DHAS_PCRE -DHAS_LDAP -DMYORIGIN_FROM_FILE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DHAS_CDB -DHAS_MYSQL -I/usr/include/mysql -DHAS_PGSQL -I/usr/include/postgresql -DHAS_SSL -I/usr/include/openssl -DUSE_SASL_AUTH -I/usr/include/sasl -DUSE_CYRUS_SASL -DUSE_TLS -O2 -I. -I../../include -DLINUX3 -o master master.o master_conf.o master_ent.o master_sig.o master_avail.o master_spawn.o master_service.o master_status.o master_listen.o master_vars.o master_wakeup.o master_watch.o master_flow.o ../../lib/libglobal.a ../../lib/libutil.a -lssl -lcrypto -lsasl2 -L/home/kevin/tmp/postfix-2.8.4/debian -ldb ../../lib/libutil.a: undefined reference to `yp_get_default_domain' ../../lib/libutil.a: undefined reference to `yp_match' collect2: ld returned 1 exit status The problem occurs because libnsl is not included in SYSLIBS because it is not found in /usr/lib64 /lib64 /usr/lib or /lib on machines using the latest libc6-dev packages, where it is in an arch-specific directory (e.g ./usr/lib/i386-linux-gnu/libnsl.a). Although it appears that the fix for this was applied to the Linux.2 system type, it was not applied (or was somehow unapplied) to Linux.3. The attached patch uses the same SEARCHDIRS logic for Linux.3 as Linux.2. Cheers, Kevin P.S. It doesn't look like anyone is committing to git://git.debian.org/~lamont/postfix.git anymore. Perhaps the Vcs-* tags in debian/control should be updated to git://anonscm.debian.org/users/lamont/postfix.git? -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.4-kevinoid1 (SMP w/2 CPU cores; PREEMPT) 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 postfix depends on: ii adduser3.113 ii debconf [debconf-2.0] 1.5.40 ii dpkg 1.16.0.3 ii libc6 2.13-18 ii libdb5.1 5.1.25-11 ii libsasl2-2 2.1.24~rc1.dfsg1+cvs2011-05-23-4 ii libssl1.0.01.0.0e-2 ii lsb-base 3.2-28 ii netbase4.46 ii ssl-cert 1.0.28 Versions of packages postfix recommends: ii python 2.6.7-3 Versions of packages postfix suggests: pn bsd-mailx [mail-reader] 8.1.2-0.20100314cvs-1 pn dovecot-common none pn evolution [mail-reader] 3.0.3-1+b1 pn icedove [mail-reader]3.1.13-1 pn libsasl2-modules 2.1.24~rc1.dfsg1+cvs2011-05-23-4 pn mutt [mail-reader] 1.5.21-5 pn opera [mail-reader] 11.50.1074 pn postfix-cdb none pn postfix-ldap none pn postfix-mysqlnone pn postfix-pcre none pn postfix-pgsqlnone pn procmail 3.22-19 pn resolvconf 1.59 pn sasl2-binnone pn ufw none -- debconf information excluded From 2b4cfb2a411442a24d1cc0e3ab5171751d8fea5e Mon Sep 17 00:00:00 2001 From: Kevin
Bug#652109: python-nautilus: Cannot be initialized by Nautilus
severity 652109 serious tags 652109 - upstream thanks On 14.12.2011 22:17, Louis wrote: Package: python-nautilus Version: 1.1-2 Severity: grave Tags: upstream Justification: renders package unusable Hello, since update of python-nautilus to version 1.1-2, it cannot be initialized by Nautilus, rendering applications using it useless. When running nautilus, the following messages appears : (nautilus:6756): Nautilus-Python-WARNING **: pygobject initialization failed (nautilus:6756): Nautilus-Python-WARNING **: nautilus_python_init_python failed Nautilus is then launched and seems to work properly, excepted that extensions relying on this library (e.g. nautilus-compare) have disappeared (it is as if they were not installed). ii python-gobject [python-gi] 2.28.6-5 python-nautilus needs python-gi = 3.0, not the virtual package that is provided by the old statics binding package. It's unfortunate, that the old python-gobject package does provide python-gi, so we need versioned depends. As soon as the current python-gi from unstable migrates to testing, python-nautilus should be working again. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#652109: python-nautilus: Cannot be initialized by Nautilus
Processing commands for cont...@bugs.debian.org: severity 652109 serious Bug #652109 [python-nautilus] python-nautilus: Cannot be initialized by Nautilus Severity set to 'serious' from 'grave' tags 652109 - upstream Bug #652109 [python-nautilus] python-nautilus: Cannot be initialized by Nautilus Removed tag(s) upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 652109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652011: general: Repeated pattern of FHS violation: Dependencies of /sbin and /bin, belong in /lib
On Wed, 14 Dec 2011, Roger Leigh wrote: [..] The same argument applies to encryption. / and /usr both contain a selection of programs, libraries etc. If you're encrypting one, why would you not encrypt all of it? Speed. On one of my relatively low-power portable systems, I have everything encrypted except /boot and /usr. /boot for obvious reasons; /usr because decryption is heavily CPU-bound, making encrypted /usr unworkably slow. Since encryption is for privacy reasons, I need encrypted / because of /etc. (And encrypted /home and /var of course.) Indeed, this means that programs in /bin and libs in /lib are also encrypted. But this actually does _not_ slow things down: the Linux disk cache is sensibly caching the decrypted data, so often-used stuff from /bin and /lib happily remains in already-decrypted cache. The interesting stuff from /usr is generally too large and too seldomly used to remain cached. So I'd say preferably not move /bin and /lib to /usr; but I'd say absolutely definitely not move /usr/bin and /usr/lib to /. (Well, in the latter case: unless you make sure that /bin and /lib are actually mountable separately. But that would really defeat the purpose.) Best regards, Anne Bezemer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652097: sysvinit: breaks system on reboot
On 2011-12-14 21:10 +0100, Roger Leigh wrote: On Wed, Dec 14, 2011 at 12:36:50PM -0600, Brian Paterni wrote: The new sysv packages in experimental look like they are breaking my system. Sorry to hear that. Knowing what went wrong here would help correct it. I'm running it without issues, but that's not to say your system is not different in some way. reboot via # shutdown -r now, or # shutdown -h now, do not work, and the only way to reboot my machine is with magic-sysrq-b or hard reset. When the machine comes up again, login is displayed way too early (~3 seconds after grub), and once I login, the system seems to be severly broken... nothing besides root is mounted, hostname is not displayed, network has not been brought up, etc... When you upgraded the packages, did you install all of sysvinit, sysvinit-utils, sysv-rc and initscripts, or just a subset? I'm having the same problem after upgrading all four packages, and it disappeared after downgrading sysvinit-utils to the version in unstable. Symptoms: On entering runlevel 6, sulogin was spawned, no way out except with sysrq keys. After a reboot, none of the initscripts had run when runlevel 2 was entered. HTH, Sven -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629795: marked as done (vala-terminal: FTBFS: build-dependency not installable: libvala-dev)
Your message dated Wed, 14 Dec 2011 22:17:56 + with message-id e1rax9a-0001tg...@franck.debian.org and subject line Bug#629795: fixed in vala-terminal 1.3-1 has caused the Debian Bug report #629795, regarding vala-terminal: FTBFS: build-dependency not installable: libvala-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 629795: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: vala-terminal Version: 1.2-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110607 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install vala-terminal build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-vala-terminal-dummy : Depends: libvala-dev but it is not installable E: Broken packages The full build log is available from: http://people.debian.org/~lucas/logs/2011/06/07/vala-terminal_1.2-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: vala-terminal Source-Version: 1.3-1 We believe that the bug you reported is fixed in the latest version of vala-terminal, which is due to be installed in the Debian FTP archive: vala-terminal_1.3-1.debian.tar.gz to main/v/vala-terminal/vala-terminal_1.3-1.debian.tar.gz vala-terminal_1.3-1.dsc to main/v/vala-terminal/vala-terminal_1.3-1.dsc vala-terminal_1.3-1_amd64.deb to main/v/vala-terminal/vala-terminal_1.3-1_amd64.deb vala-terminal_1.3.orig.tar.bz2 to main/v/vala-terminal/vala-terminal_1.3.orig.tar.bz2 A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 629...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Reichel s...@debian.org (supplier of updated vala-terminal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 14 Dec 2011 22:54:24 +0100 Source: vala-terminal Binary: vala-terminal Architecture: source amd64 Version: 1.3-1 Distribution: unstable Urgency: low Maintainer: Debian freesmartphone.org Team pkg-fso-ma...@lists.alioth.debian.org Changed-By: Sebastian Reichel s...@debian.org Description: vala-terminal - Terminal emulator for mobile devices Closes: 629795 650232 Changes: vala-terminal (1.3-1) unstable; urgency=low . [ Philipp Kaluza ] * new upstream release 1.3; thanks to Michael Lauer for rolling tarball * only available bz2-compressed; therefore move to format 3.0 (quilt) * builds with current valac (closes: #650232) * we don't actually need to link against libvala (closes: #629795); drop debian/patches/libvala-0.12-dev.patch * no longer suppress dh_auto_test * regenerate .c files during build to ease future binNMUs (and remove on dh_clean) . [ Sebastian Reichel ] * Add myself to Uploaders * Add Philipp Kaluza deb...@ghostroute.eu to Uploaders * Add DM-Upload-Allowed: yes * Use DEP5 style for debian/copyright * Update Standards-Version from 3.8.2 to 3.9.2 Checksums-Sha1: 414b1fe9838658904cbd8bb47d57200a81a4e2ea 2082
Bug#652097: I can confirm the failure to shutdown
And will probably need a bootable CD! --eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652097: [Pkg-sysvinit-devel] Bug#652097: sysvinit: breaks system on reboot
[Sven Joachim] I'm having the same problem after upgrading all four packages, and it disappeared after downgrading sysvinit-utils to the version in unstable. Symptoms: On entering runlevel 6, sulogin was spawned, no way out except with sysrq keys. After a reboot, none of the initscripts had run when runlevel 2 was entered. What is the output from 'ls /etc/rc?.d/'? What about the output from /usr/share/insserv/check-initd-order? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652097: [Pkg-sysvinit-devel] Bug#652097: sysvinit: breaks system on reboot
On Wed, Dec 14, 2011 at 11:33:23PM +0100, Petter Reinholdtsen wrote: [Sven Joachim] I'm having the same problem after upgrading all four packages, and it disappeared after downgrading sysvinit-utils to the version in unstable. Symptoms: On entering runlevel 6, sulogin was spawned, no way out except with sysrq keys. After a reboot, none of the initscripts had run when runlevel 2 was entered. What is the output from 'ls /etc/rc?.d/'? What about the output from /usr/share/insserv/check-initd-order? Looks like we've found the problem. It's due to the updated packaging not applying the patches in debian/startpar/patches. Looks like a simple enough fix. If we move debian/startpar into a patch, then the entire patchset can go into debian/patches so it's all automatically applied. Not entirely sure why I've not seen this on amd64 though. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652097: [Pkg-sysvinit-devel] Bug#652097: sysvinit: breaks system on reboot
[Roger Leigh] Looks like we've found the problem. It's due to the updated packaging not applying the patches in debian/startpar/patches. Looks like a simple enough fix. If we move debian/startpar into a patch, then the entire patchset can go into debian/patches so it's all automatically applied. Right. It is probably about time the startpar tool is split out into its own package. It should reduce the chance of such problems in the future. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652115: ruby1.8: FTBFS on sparc: ./sample/test.rb:1848: [BUG] Bus Error
Source: ruby1.8 Version: 1.8.7.352-2 Severity: serious Justification: fails to build from source User: debian-sp...@lists.debian.org Usertags: sparc ruby1.8 FTBFS on sparc: | ./sample/test.rb:1848: [BUG] Bus Error | ruby 1.8.7 (2011-06-30 patchlevel 352) [sparc-linux] | | test failed | make[1]: *** [test] Error 1 | make[1]: Leaving directory `/build/buildd-ruby1.8_1.8.7.352-2-sparc-NViQ1Z/ruby1.8-1.8.7.352' | make: *** [debian/stamp-makefile-build] Error 2 Full build log: https://buildd.debian.org/status/fetch.php?pkg=ruby1.8arch=sparcver=1.8.7.352-2stamp=1323883832 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652116: lua-lpeg: FTBFS on sparc: Segmentation fault
Source: lua-lpeg Version: 0.10.2-2 Severity: serious Justification: fails to build from source User: debian-sp...@lists.debian.org Usertags: sparc lua-lpeg FTBFS on sparc: | *** app static ** | ldd ./app | liblua5.1.so.0 = /usr/lib/sparc-linux-gnu/liblua5.1.so.0 (0x70054000) | libm.so.6 = /lib/sparc-linux-gnu/libm.so.6 (0x7008c000) | libdl.so.2 = /lib/sparc-linux-gnu/libdl.so.2 (0x70034000) | libc.so.6 = /lib/sparc-linux-gnu/libc.so.6 (0x70174000) | /lib/ld-linux.so.2 (0x7000) | HOME=/build/buildd-lua-lpeg_0.10.2-2-sparc-4rtthc/lua-lpeg-0.10.2/debian LUA_INIT= SEGFAULT_SIGNALS=all \ |catchsegv ./app test.lua | Segmentation fault | *** Segmentation fault | Register dump: | | PSR: ff001085 PC: 000121b4 NPC: 000121b8 Y: | g0: g1: 0028 g2: 03fc g3: 0006f03c | g4: 0030 g5: 0006f040 g6: 0040 g7: 70002bc0 | o0: 0006f040 o1: o2: o3: 0058 | o4: o5: 00032030 sp: ffda6dd8 o7: 00014320 | l0: 7032fb00 l1: 0048 l2: 0009 l3: 0024 | l4: 0038 l5: 2819 l6: 2c20 l7: ffda6ea4 | i0: 0006f010 i1: 0006f040 i2: 000b i3: 00017dc0 | i4: i5: 000b fp: ffda6e40 i7: 00015ecc | | Old mask: XFSR: 00200020 GSR: 00 FPRS: 7 | f0: f2: 000463636363 f4: 000463636363 | f6: 00032838 f8: 3ff0 f10: | f12: f14: 0003281800063b88 f16: 000463636363 | f18: 0005fbe8 f20: 000463636363 f22: 0005fc080005fa38 | f24: 000463636363 f26: 00039750ffda4d78 f28: 000463636363 | f30: 000327f8 f32: 000463636363 f34: 0003c714 | f36: 000463636363 f38: 0005fc28013a f40: 000463636363 | f42: 000397e80009 f44: 000463636363 f46: 0003c500 | f48: 000463636363 f50: 000463636363 f52: 0005fc080005fa38 | f54: 000463636363 f56: 00039750ffda4d78 f58: 000463636363 | f60: 000327f8 f62: 000463636363 | | Backtrace: | /lib/sparc-linux-gnu/libc.so.6(+0x38318)[0x701e8318] | /build/buildd-lua-lpeg_0.10.2-2-sparc-4rtthc/lua-lpeg-0.10.2/lpeg.c:1348(concat_l)[0x15ecc] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0xa2d4)[0x7002a2d4] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0xa708)[0x7002a708] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0x13e10)[0x70033e10] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0x13ea4)[0x70033ea4] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0x1413c)[0x7003413c] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0x150d4)[0x700350d4] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0xa74c)[0x7002a74c] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(lua_call+0x18)[0x70025978] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0x20104)[0x70040104] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0xa2d4)[0x7002a2d4] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0x1561c)[0x7003561c] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0xa74c)[0x7002a74c] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0x98e0)[0x700298e0] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(+0xa928)[0x7002a928] | /usr/lib/sparc-linux-gnu/liblua5.1.so.0(lua_pcall+0x50)[0x70025a10] | /usr/share/lua5.1-policy-dev/app.c:53(main)[0x1146c] | /lib/sparc-linux-gnu/libc.so.6(__libc_start_main+0x10c)[0x701d084c] | ??:0(_start)[0x1154c] | | Memory map: | | 0001-00018000 r-xp fd:03 1163327 /build/buildd-lua-lpeg_0.10.2-2-sparc-4rtthc/lua-lpeg-0.10.2/app | 00028000-0002a000 rwxp 8000 fd:03 1163327 /build/buildd-lua-lpeg_0.10.2-2-sparc-4rtthc/lua-lpeg-0.10.2/app | 0002a000-000d8000 rwxp 00:00 0 [heap] | 7000-70004000 rw-p 00:00 0 | 70004000-70008000 r-xp fd:08 163920 /lib/sparc-linux-gnu/libSegFault.so | 70008000-70016000 ---p 4000 fd:08 163920 /lib/sparc-linux-gnu/libSegFault.so | 70016000-70018000 r--p 2000 fd:08 163920 /lib/sparc-linux-gnu/libSegFault.so | 70018000-7001a000 rwxp 4000 fd:08 163920 /lib/sparc-linux-gnu/libSegFault.so | 7001a000-7001c000 rw-p 00:00 0 | 7002-70044000 r-xp fd:08 17537 /usr/lib/sparc-linux-gnu/liblua5.1.so.0.0.0 | 70044000-70054000 ---p 00024000 fd:08 17537 /usr/lib/sparc-linux-gnu/liblua5.1.so.0.0.0 | 70054000-70056000 rwxp 00024000 fd:08 17537 /usr/lib/sparc-linux-gnu/liblua5.1.so.0.0.0 | 70058000-7005c000 r-xp fd:08 163918 /lib/sparc-linux-gnu/libdl-2.13.so | 7005c000-7006a000 ---p 4000 fd:08 163918 /lib/sparc-linux-gnu/libdl-2.13.so | 7006a000-7006c000 r--p 2000 fd:08 163918 /lib/sparc-linux-gnu/libdl-2.13.so | 7006c000-7006e000 rwxp 4000 fd:08 163918 /lib/sparc-linux-gnu/libdl-2.13.so | 70094000-700b6000 r-xp fd:08 163870 /lib/sparc-linux-gnu/ld-2.13.so | 700c4000-700c6000 r--p 0002 fd:08 163870 /lib/sparc-linux-gnu/ld-2.13.so | 700c6000-700c8000 rwxp 00022000 fd:08 163870 /lib/sparc-linux-gnu/ld-2.13.so | 700c8000-7019a000 r-xp fd:08 163863
Bug#652117: bouncycastle: FTBFS on sparc: ICE: output_operand: invalid expression as operand
Source: bouncycastle Version: 1.44+dfsg-3 Severity: serious Justification: fails to build from source User: debian-sp...@lists.debian.org Usertags: sparc bouncycastle FTBFS on sparc: | /usr/bin/gcj -c -fsource-filename=/tmp/filev1tpRI -g -O2 -fPIC -findirect-dispatch -fjni bcprov-1.44.jar.3.jar -o bcprov-1.44.jar.3.o | jc1: internal compiler error: output_operand: invalid expression as operand | Please submit a full bug report, | with preprocessed source if appropriate. | See file:///usr/share/doc/gcj-4.6/README.Bugs for instructions. | make[1]: *** [bcprov-1.44.jar.3.o] Error 1 | make[1]: *** Waiting for unfinished jobs | make[1]: Leaving directory `/build/buildd-bouncycastle_1.44+dfsg-3-sparc-YQ760I/bouncycastle-1.44+dfsg/debian/libbcprov-java-gcj/usr/lib/gcj' | aot-compile: error: /usr/bin/make exited with code 2 | dh_nativejava: aot-compile -L /usr/lib/gcj -c -fsource-filename=/tmp/filev1tpRI debian/libbcprov-java debian/libbcprov-java-gcj/usr/lib/gcj returned exit code 1 | make: *** [binary-post-install/libbcprov-java-gcj] Error 25 Full build log: https://buildd.debian.org/status/fetch.php?pkg=bouncycastlearch=sparcver=1.44%2Bdfsg-3stamp=1323884955 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640012: postfix: diff for NMU version 2.8.5-1.1
tags 640012 + pending thanks Hi LaMont, I've prepared an NMU for postfix (versioned as 2.8.5-1.1) and will upload it shortly. Please find the diff attached. Cheers, Julien diff -u postfix-2.8.5/makedefs postfix-2.8.5/makedefs --- postfix-2.8.5/makedefs +++ postfix-2.8.5/makedefs @@ -381,7 +381,7 @@ done done ;; - GNU.0*|GNU/kFreeBSD.[567]*) + GNU.0*|GNU/kFreeBSD.*) SYSTYPE=GNU0 # Postfix no longer needs DB 1.85 compatibility if [ -f /usr/include/db.h ] diff -u postfix-2.8.5/debian/changelog postfix-2.8.5/debian/changelog --- postfix-2.8.5/debian/changelog +++ postfix-2.8.5/debian/changelog @@ -1,3 +1,10 @@ +postfix (2.8.5-1.1) unstable; urgency=high + + * Non-maintainer upload. + * Fix FTBFS on kfreebsd with patch from Christoph Egger (closes: #640012). + + -- Julien Cristau jcris...@debian.org Wed, 14 Dec 2011 23:33:12 +0100 + postfix (2.8.5-1) unstable; urgency=low [Wietse Venema] diff -u postfix-2.8.5/src/util/sys_defs.h postfix-2.8.5/src/util/sys_defs.h --- postfix-2.8.5/src/util/sys_defs.h +++ postfix-2.8.5/src/util/sys_defs.h @@ -835,7 +835,9 @@ #define HAS_DB #define DEF_DB_TYPE hash #define ALIAS_DB_MAP hash:/etc/aliases +#ifndef DEBIAN #define HAS_NIS +#endif #define GETTIMEOFDAY(t) gettimeofday(t,(struct timezone *) 0) #define ROOT_PATH /bin:/usr/bin:/sbin:/usr/sbin #define FIONREAD_IN_TERMIOS_H signature.asc Description: Digital signature
Bug#652011: general: Repeated pattern of FHS violation: Dependencies of /sbin and /bin, belong in /lib
On 14.12.2011 22:43, J.A. Bezemer wrote: So I'd say preferably not move /bin and /lib to /usr; but I'd say absolutely definitely not move /usr/bin and /usr/lib to /. (Well, in the latter case: unless you make sure that /bin and /lib are actually mountable separately. But that would really defeat the purpose.) Moving the bits from /lib and /(s)bin to /usr doesn't mean you won't be able to have /usr on a separate partition. It just means you'd have to use something like initramfs-tools to mount /usr for you. Actually, by moving the bits to /usr, you'd have to encrypt even less. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: postfix: diff for NMU version 2.8.5-1.1
Processing commands for cont...@bugs.debian.org: tags 640012 + pending Bug #640012 [src:postfix] postfix: FTBFS: kFreeBSD check hardcodes kernel version 5,6,7, current is 8 + no NIS on !linux Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 640012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639194: marked as done (phoneuid: FTBFS: libphone-ui.so: undefined reference to `free_smartphone_pim_get_messages_proxy')
Your message dated Wed, 14 Dec 2011 22:48:39 + with message-id e1raxct-0005cu...@franck.debian.org and subject line Bug#639194: fixed in phoneuid 0.1+git20110506-1 has caused the Debian Bug report #639194, regarding phoneuid: FTBFS: libphone-ui.so: undefined reference to `free_smartphone_pim_get_messages_proxy' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 639194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: phoneuid Version: 0.1+git20100502-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110822 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -Wall -Wextra -Werror -Wno-strict-aliasing -DDATADIR=\/usr/share\ -DPKGDATADIR=\/usr/share/phoneuid\ -DG_LOG_DOMAIN=\phoneuid\ -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/dbus-1.0 -I/usr/include/fso-glib -I/usr/include/fsoframework-2.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/phoneui -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -ggdb -g -O2 -g -O2 -Wall -ldl -pthread -ldbus-glib-1 -ldbus-1 -lpthread -lgobject-2.0 -lgthread-2.0 -lrt -lglib-2.0 -pthread -ldbus-1 -lpthread -lgthread-2.0 -lrt -lglib-2.0 -pthread -lphone-ui -ldbus-glib-1 -lfso-glib -lfsoframework -ldbus-1 -lpthread -lfsobasics -lgio-2.0 -lnl -lnl-route -lnl-nf -lnl-genl -lnl-cli -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0-o phoneuid phoneuid-phoneuid.o phoneuid-phoneuid-contacts.o phoneuid-phoneuid-messages.o phoneuid-phoneuid-call-management.o phoneuid-phoneuid-notification.o phoneuid-phoneuid-dialer.o phoneuid-phoneuid-settings.o phoneuid-phoneuid-idle-screen.o phoneuid-phoneuid-phone-log.o /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_pim_get_messages_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_device_get_idle_notifier_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_pim_get_calls_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_get_preferences_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_gsm_get_s_i_m_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_device_get_input_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_device_get_audio_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_gsm_get_network_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_get_usage_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_pim_get_fields_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_pim_get_message__proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_pim_get_contacts_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_device_get_power_supply_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_gsm_get_s_m_s_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_pim_get_contact_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_pim_get_tasks_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_pim_get_call_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_gsm_get_call_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_get_network_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_pim_get_call_query_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_pim_get_message_query_proxy' /usr/lib64/libphone-ui.so: undefined reference to `free_smartphone_gsm_get_p_d_p_proxy' collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2011/08/22/phoneuid_0.1+git20100502-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not
Bug#650534: util-linux: FTBFS: undefined reference to `rmd160_hash_buffer'
Thorsten Glaser, le Wed 30 Nov 2011 18:12:56 +, a écrit : util-linux FTBFS on all (release _and_ debian-ports) architectures: ‣ https://buildd.debian.org/status/package.php?p=util-linux ‣ http://buildd.debian-ports.org/status/package.php?p=util-linux Ping? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640012: marked as done (postfix: FTBFS: kFreeBSD check hardcodes kernel version 5,6,7, current is 8 + no NIS on !linux)
Your message dated Wed, 14 Dec 2011 23:04:07 + with message-id e1raxrr-0007gv...@franck.debian.org and subject line Bug#640012: fixed in postfix 2.8.5-1.1 has caused the Debian Bug report #640012, regarding postfix: FTBFS: kFreeBSD check hardcodes kernel version 5,6,7, current is 8 + no NIS on !linux to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 640012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:postfix Version: 2.8.4-1 Severity: serious X-Debbugs-Cc: debian-...@lists.debian.org,debian-h...@lists.debian.org Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd and hurd buildds. For kFreeBSD makedefs hardcodes kFreeBSD kernel Versions up to 7 while current is 8. Patch: diff -u postfix-2.8.4/makedefs postfix-2.8.4/makedefs --- postfix-2.8.4/makedefs +++ postfix-2.8.4/makedefs @@ -374,7 +374,7 @@ done done ;; - GNU.0*|GNU/kFreeBSD.[567]*) + GNU.0*|GNU/kFreeBSD*) SYSTYPE=GNU0 # Postfix no longer needs DB 1.85 compatibility if [ -f /usr/include/db.h ] Also there's no NIS on kfreebsd and hurd (See #545970). I tried to disable NIS in postfix with the following patch which results in a building postfix at least: --- postfix-2.8.4/src/util/sys_defs.h +++ postfix-2.8.4/src/util/sys_defs.h @@ -835,7 +835,9 @@ #define HAS_DB #define DEF_DB_TYPEhash #define ALIAS_DB_MAP hash:/etc/aliases +#ifndef DEBIAN #define HAS_NIS +#endif #define GETTIMEOFDAY(t)gettimeofday(t,(struct timezone *) 0) #define ROOT_PATH /bin:/usr/bin:/sbin:/usr/sbin #define FIONREAD_IN_TERMIOS_H Regards Christoph If you have further questions please mail debian-...@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer ---End Message--- ---BeginMessage--- Source: postfix Source-Version: 2.8.5-1.1 We believe that the bug you reported is fixed in the latest version of postfix, which is due to be installed in the Debian FTP archive: postfix-cdb_2.8.5-1.1_amd64.deb to main/p/postfix/postfix-cdb_2.8.5-1.1_amd64.deb postfix-dev_2.8.5-1.1_all.deb to main/p/postfix/postfix-dev_2.8.5-1.1_all.deb postfix-doc_2.8.5-1.1_all.deb to main/p/postfix/postfix-doc_2.8.5-1.1_all.deb postfix-ldap_2.8.5-1.1_amd64.deb to main/p/postfix/postfix-ldap_2.8.5-1.1_amd64.deb postfix-mysql_2.8.5-1.1_amd64.deb to main/p/postfix/postfix-mysql_2.8.5-1.1_amd64.deb postfix-pcre_2.8.5-1.1_amd64.deb to main/p/postfix/postfix-pcre_2.8.5-1.1_amd64.deb postfix-pgsql_2.8.5-1.1_amd64.deb to main/p/postfix/postfix-pgsql_2.8.5-1.1_amd64.deb postfix_2.8.5-1.1.diff.gz to main/p/postfix/postfix_2.8.5-1.1.diff.gz postfix_2.8.5-1.1.dsc to main/p/postfix/postfix_2.8.5-1.1.dsc postfix_2.8.5-1.1_amd64.deb to main/p/postfix/postfix_2.8.5-1.1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 640...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau jcris...@debian.org (supplier of updated postfix package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 14 Dec 2011 23:33:12 +0100 Source: postfix Binary: postfix postfix-ldap postfix-cdb postfix-pcre postfix-mysql postfix-pgsql postfix-dev postfix-doc Architecture: source amd64 all Version: 2.8.5-1.1 Distribution: unstable Urgency: high Maintainer: LaMont Jones lam...@debian.org Changed-By: Julien Cristau jcris...@debian.org Description: postfix- High-performance mail transport agent postfix-cdb - CDB map support for Postfix postfix-dev - Loadable modules development environment for Postfix postfix-doc - Documentation for Postfix postfix-ldap - LDAP map support for Postfix postfix-mysql - MySQL map support for Postfix postfix-pcre - PCRE map support for Postfix postfix-pgsql - PostgreSQL map support for Postfix Closes: 640012 Changes: postfix (2.8.5-1.1) unstable; urgency=high . * Non-maintainer upload. * Fix FTBFS on kfreebsd with patch from Christoph Egger (closes:
Bug#652011: general: Repeated pattern of FHS violation: Dependencies of /sbin and /bin, belong in /lib
On 14.12.2011 06:00, Russ Allbery wrote: I'm increasingly convinced by the recent discussion on debian-devel that doing all the (rather substantial) work required to keep this separation working is a waste of our collective time. We're not doing a very good job at it anyway, chasing all the library dependencies is a fair amount of work, and things have to keep moving around as dependencies change. And this is all to support use cases that, while real, are fairly marginal in my estimation. This does not seem like the most effective place for us to be spending our time. nod. I had to move a couple of libraries myself in the past and it's a laborious task (and I've often seen it not done right). E.g. while moving the library file to /lib, you should keep the devel files (.so symlink, .a/.la files, pkg-config files) in /usr/lib. You can't just move the .so symlink around, so you need to do it manually. The problem is, that the major build systems (autoconf/automake, cmake) don't have support for such split installations. I don't know if it's worth the effort to unify /bin and /usr/bin or the other similar things that have been discussed from time to time, but I do think it may be time for Debian to just officially say that we don't support /usr on a (meaningfully) separate partition from /bin and /lib, and that binaries in /bin may have dependencies on /usr/lib. The more I think about it, the more I like the idea to simply move everything to /usr, and make /(s)bin and /lib symlinks. While I personally never found it very useful to put /usr on a separate partition, I acknowledge that such installations are around (especially since d-i presents this partitioning scheme in such a prominent way) and we must not break such installations on upgrades. We'd have to make sure, that for such installations e.g. a initramfs is installed, which can mount /usr. That said, I'd also like to see us deprecate a separate /usr altogether. And a first step would be to update d-i to no longer present this option. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#652097: You can manually start the system
I managed to login once I figured out the keybord was back in querty mode. Then simulating a normal boot (mount /proc /sys, restart udev, clear mtab, mount -a, then networking. SO you do not absolutely need a boot disk. Annoying still. And yes only ssyinit-utils (and thus startpar is enough to fix the whole boot process). -- eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652097: [Pkg-sysvinit-devel] Bug#652097: sysvinit: breaks system on reboot
On Wed, Dec 14, 2011 at 11:33:23PM +0100, Petter Reinholdtsen wrote: [Sven Joachim] I'm having the same problem after upgrading all four packages, and it disappeared after downgrading sysvinit-utils to the version in unstable. Symptoms: On entering runlevel 6, sulogin was spawned, no way out except with sysrq keys. After a reboot, none of the initscripts had run when runlevel 2 was entered. What is the output from 'ls /etc/rc?.d/'? What about the output from /usr/share/insserv/check-initd-order? Could you possibly try http://people.debian.org/~rleigh/sysvinit/sysvinit_2.88dsf-15.dsc (amd64 packages are also in the same directory) This fixes the startpar issue mentioned previously. It would be good to know if this is the cause of the failure, or if the failure is due to something else. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645258: marked as done (python-django-lint: missing dependency on python-pkg-resources)
Your message dated Wed, 14 Dec 2011 23:33:11 +
with message-id e1rayjz-00024r...@franck.debian.org
and subject line Bug#645258: fixed in python-django-lint 0.13-2
has caused the Debian Bug report #645258,
regarding python-django-lint: missing dependency on python-pkg-resources
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
645258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-django-lint
Version: 0.13-1
Severity: serious
Justification: Policy 3.5
In a minimal chroot:
| $ django-lint
| Traceback (most recent call last):
| File /usr/bin/django-lint, line 5, in module
| from pkg_resources import load_entry_point
| ImportError: No module named pkg_resources
--
Jakub Wilk
---End Message---
---BeginMessage---
Source: python-django-lint
Source-Version: 0.13-2
We believe that the bug you reported is fixed in the latest version of
python-django-lint, which is due to be installed in the Debian FTP archive:
python-django-lint_0.13-2.debian.tar.gz
to main/p/python-django-lint/python-django-lint_0.13-2.debian.tar.gz
python-django-lint_0.13-2.dsc
to main/p/python-django-lint/python-django-lint_0.13-2.dsc
python-django-lint_0.13-2_all.deb
to main/p/python-django-lint/python-django-lint_0.13-2_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 645...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lamb la...@debian.org (supplier of updated python-django-lint package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 14 Dec 2011 23:21:48 +
Source: python-django-lint
Binary: python-django-lint
Architecture: source all
Version: 0.13-2
Distribution: unstable
Urgency: low
Maintainer: Chris Lamb la...@debian.org
Changed-By: Chris Lamb la...@debian.org
Description:
python-django-lint - Static analysis tool for Django projects and applications
Closes: 645258
Changes:
python-django-lint (0.13-2) unstable; urgency=low
.
* Add missing dependency on on python-pkg-resources (Closes: #645258)
* Set source package format to '3.0 (quilt)'
* Update Vcs-{Git,Browser}.
* Bump Standards-Version to 3.9.1.
* Bump Standards-Version to 3.9.2.
Checksums-Sha1:
64f9479bb58b9bce24d3d2993559e9e4199eb10e 1225 python-django-lint_0.13-2.dsc
71a2485308d1cc0020c2bc58273c9c314aed8a17 2190
python-django-lint_0.13-2.debian.tar.gz
9e8b7bce5745553b07df421fb142bfb8493afd83 12948
python-django-lint_0.13-2_all.deb
Checksums-Sha256:
18ecc866842b7b5efe10275aa4be6599c34e6277e304a02eac4fe347d1d70b42 1225
python-django-lint_0.13-2.dsc
d425d924be944c713827bc4412276a0acd07894b413ace8dba73e90186b12aab 2190
python-django-lint_0.13-2.debian.tar.gz
055d4a49cc21fde6ffe2c9e97e67bdac1737c25885b32e8d954ca46f775041f2 12948
python-django-lint_0.13-2_all.deb
Files:
e75d728e45d978b4a854eee0c501b44a 1225 python optional
python-django-lint_0.13-2.dsc
e144d33ff7aa793158db84dd39ad5e89 2190 python optional
python-django-lint_0.13-2.debian.tar.gz
a84bdc9608099cb5cf8eb909e1f6349d 12948 python optional
python-django-lint_0.13-2_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAk7pL7EACgkQ5/8uW2NPmiBJVACeIwSATgnfBn+WSmyFtFTvlAjh
CKkAniqMP+IwWQkfJ/6SfTjTMSM2m9PI
=suPP
-END PGP SIGNATURE-
---End Message---
Bug#515284: geg: Depends on GTK 1.2
retitle 515284 RM: geg -- RoM, depends on removed GTK 1.2 reassign 515284 ftp.debian.org thanks On Wed, Dec 14, 2011 at 10:30:58AM +0100, Frederic Peters wrote: Barry deFreese wrote: Here is a patch that builds with Gtk2 as well as fix several packaging issues and bump standards version, etc. The patch builds fine but seems like it may have some issues at runtime so it probably needs a bit more work. Hope it helps. Sorry for not answering earlier, I probably gave a look at the patch, tried fixing runtime issues, and got lost. I just had a new look and there are issues around text views (probably not difficult to fix) but it also looks like the drawing in the equation view would need some serious work. Moritz Muehlenhoff wrote: Frederic, shall we proceed with removal from the archive? I am of this opinion. Ok, reassigning to ftp.debian.org Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#515284: geg: Depends on GTK 1.2
Processing commands for cont...@bugs.debian.org: retitle 515284 RM: geg -- RoM, depends on removed GTK 1.2 Bug #515284 [geg] geg: Depends on GTK 1.2 Changed Bug title to 'RM: geg -- RoM, depends on removed GTK 1.2' from 'geg: Depends on GTK 1.2' reassign 515284 ftp.debian.org Bug #515284 [geg] RM: geg -- RoM, depends on removed GTK 1.2 Bug reassigned from package 'geg' to 'ftp.debian.org'. thanks Stopping processing here. Please contact me if you need assistance. -- 515284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596275: marked as done (phoneui-apps: not installable in sid on any architecture)
Your message dated Thu, 15 Dec 2011 00:57:34 +0100 with message-id 20111214235734.GA21978@earth.universe and subject line phoneui-apps is now installable has caused the Debian Bug report #596275, regarding phoneui-apps: not installable in sid on any architecture to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 596275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: phoneui-apps Version: 0.1+git20100801-1 Severity: grave User: trei...@debian.org Usertags: edos-uninstallable Hi, phoneui-apps is not installable on any architecture in sid: depends on one of: - phonefsod (= 0.1+git20100802-2) phonefsod (= 0.1+git20100802-2) depends on missing: - fso-deviced -Ralf. ---End Message--- ---BeginMessage--- phoneui-apps should be installable now. Most package updates from today are still building on armel, though. -- Sebastian signature.asc Description: Digital signature ---End Message---
Bug#652109: marked as done (python-nautilus: Cannot be initialized by Nautilus)
Your message dated Thu, 15 Dec 2011 00:17:52 + with message-id e1raz1e-0008db...@franck.debian.org and subject line Bug#652109: fixed in nautilus-python 1.1-3 has caused the Debian Bug report #652109, regarding python-nautilus: Cannot be initialized by Nautilus to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 652109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-nautilus Version: 1.1-2 Severity: grave Tags: upstream Justification: renders package unusable Hello, since update of python-nautilus to version 1.1-2, it cannot be initialized by Nautilus, rendering applications using it useless. When running nautilus, the following messages appears : (nautilus:6756): Nautilus-Python-WARNING **: pygobject initialization failed (nautilus:6756): Nautilus-Python-WARNING **: nautilus_python_init_python failed Nautilus is then launched and seems to work properly, excepted that extensions relying on this library (e.g. nautilus-compare) have disappeared (it is as if they were not installed). Regards, Louis -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-486 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-nautilus depends on: ii gir1.2-nautilus-3.0 3.0.2-4 ii libatk1.0-0 2.2.0-2 ii libc6 2.13-21 ii libcairo-gobject2 1.10.2-6.1 ii libcairo2 1.10.2-6.1 ii libfontconfig1 2.8.0-3 ii libfreetype62.4.8-1 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-02.30.2-4 ii libgtk-3-0 3.2.2-3 ii libnautilus-extension1a 3.0.2-4 ii libpango1.0-0 1.29.4-2 ii libpython2.72.7.2-8 ii python-gobject [python-gi] 2.28.6-5 python-nautilus recommends no packages. python-nautilus suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: nautilus-python Source-Version: 1.1-3 We believe that the bug you reported is fixed in the latest version of nautilus-python, which is due to be installed in the Debian FTP archive: nautilus-python_1.1-3.debian.tar.gz to main/n/nautilus-python/nautilus-python_1.1-3.debian.tar.gz nautilus-python_1.1-3.dsc to main/n/nautilus-python/nautilus-python_1.1-3.dsc python-nautilus_1.1-3_amd64.deb to main/n/nautilus-python/python-nautilus_1.1-3_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 652...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl bi...@debian.org (supplier of updated nautilus-python package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 15 Dec 2011 01:00:58 +0100 Source: nautilus-python Binary: python-nautilus Architecture: source amd64 Version: 1.1-3 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Michael Biebl bi...@debian.org Description: python-nautilus - Python binding for Nautilus components Closes: 652109 Changes: nautilus-python (1.1-3) unstable; urgency=low . * Bump debhelper compatibility to 8. * Set pkg-gnome-maintain...@lists.alioth.debian.org as Maintainer. * Tighten dependency on python-gi to ensure it has dynamic bindings support. Closes: #652109 Checksums-Sha1: 9b1c29ec1697b133e8676aab63724e0d354365c8 2201 nautilus-python_1.1-3.dsc 0c38fb0b8c57865b3c188590e978cbb1114fe105 5796 nautilus-python_1.1-3.debian.tar.gz 952690b0f6726bd0721e87a6fe99c249d4939563 20632 python-nautilus_1.1-3_amd64.deb Checksums-Sha256: ed9320e5692ddefb68316a638d8911e5be638d0a81a6b4a3314e68608a74aa88 2201 nautilus-python_1.1-3.dsc 1539e9bc4bdb71ddda30787b8de051cc8f5f92c7225c341de2db87e3662e103e 5796 nautilus-python_1.1-3.debian.tar.gz 4704fbed76fab0970e0654204bfb821ec54efbf3c5edb2bf4b424e68761d3c76 20632 python-nautilus_1.1-3_amd64.deb Files: 94fb6377b05f6a95cc5366ac8f62ea88 2201 python optional
Processed: limit source to swi-prolog, tagging 644974
Processing commands for cont...@bugs.debian.org: #swi-prolog (5.10.4-3) UNRELEASED; urgency=low # # * Make swi-prolog-nox depend on libncurses5-dev (closes: #644974) # limit source swi-prolog Limiting to bugs with field 'source' containing at least one of 'swi-prolog' Limit currently set to 'source':'swi-prolog' tags 644974 + pending Bug #644974 [swi-prolog-nox] swipl.pc links with -lncurses, but doesn't have a dependency on libncurses5-dev Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 644974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: cloning 644593, retitle -1 to swi-prolog-java: add support for other architectures ...
Processing commands for cont...@bugs.debian.org: clone 644593 -1 Bug#644593: swi-prolog: FTBFS: No rule to make target `install'. Stop. Bug 644593 cloned as bug 652130. retitle -1 swi-prolog-java: add support for other architectures Bug #652130 [src:swi-prolog] swi-prolog: FTBFS: No rule to make target `install'. Stop. Changed Bug title to 'swi-prolog-java: add support for other architectures' from 'swi-prolog: FTBFS: No rule to make target `install'. Stop.' severity -1 normal Bug #652130 [src:swi-prolog] swi-prolog-java: add support for other architectures Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 652130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652130 644593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644593 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652011: general: Repeated pattern of FHS violation: Dependencies of /sbin and /bin, belong in /lib
On 12/14/2011 04:43 PM, J.A. Bezemer wrote: On Wed, 14 Dec 2011, Roger Leigh wrote: [..] The same argument applies to encryption. / and /usr both contain a selection of programs, libraries etc. If you're encrypting one, why would you not encrypt all of it? Speed. On one of my relatively low-power portable systems, I have everything encrypted except /boot and /usr. /boot for obvious reasons; /usr because decryption is heavily CPU-bound, making encrypted /usr unworkably slow. Since encryption is for privacy reasons, I need encrypted / because of /etc. (And encrypted /home and /var of course.) Indeed, this means that programs in /bin and libs in /lib are also encrypted. But this actually does _not_ slow things down: the Linux disk cache is sensibly caching the decrypted data, so often-used stuff from /bin and /lib happily remains in already-decrypted cache. The interesting stuff from /usr is generally too large and too seldomly used to remain cached. Yep, that's actually the case for how I got pulled into the fray here. I recently did a squeeze install on the new laptop. I take the laptop out on the world a lot in a powered off state, and thought it would be nice to try Luks encryption for an extra layer of security, mostly for the sake of /home, /var /etc and swap. So I chose the automated partitioning scheme for encrypted LVM on the install disc. I really just wanted the encryption, and at first thought the extra LVM layer was an annoyance. Later, I found the LVM layer was cool to have because / needed much more space than d-i gave it, for backports kernels and headers (for modules for wireless card, etc.), and encrypted /usr (especially without AES acceleration on my processor) was a noticeable performance loss. So I was able to move /usr to the unencrypted partition I made after resizing LVM, expanded /, got backports kernels going (to the joy of the now working sound-card on the new machine), and now everything is working great. ... ... With the one caveat which brings us to today, that now I get complaints in the boot log when certain /bin functions are called with dependencies in /usr/lib that haven't been mounted yet. OK, so I admit it, don't shoot me, but the truth of the matter is that these boot log errors haven't yet practically caused me harm in any way (other than the time spent trying to be a responsible admin for my system and track down the reason I'm seeing log errors before they DO jump out and bite me right at the time of a crucial work deadline or whatever). On 12/14/2011 06:08 PM, Michael Biebl wrote: I acknowledge that such installations are around (especially since d-i presents this partitioning scheme in such a prominent way) Yep! In fact, one irony in this discussion is that on my own I wouldn't have dreamed of going to the effort to take the initiative to understand working with a separate /usr partition, if not for the fact that d-i had put it out in front of me! But actually, at the end of the day, it worked out well because I (and apparently others) have found that having a generally encrypted system with an unencrypted /usr is actually advantageous. And if someone does snag my laptop and want to yank out the hard drive, I'm really not concerned about them being able to find out what applications I have in my /usr. On 12/14/2011 03:43 PM, Roger Leigh wrote: But the distro itself should take responsibility for being CONSISTENT, and thus should not say, Here's something available to you in /sbin---oh, but you can't actually use it from there (so to speak).) The problem here is, can we /be/ consistent? What is one system's essential package required for bringing up a working system is someone else's occasionally-used tool that's not important at all. Yet both might be required to be on the rootfs. We can't be all things to all people in the current state. I think we're not fully understanding each other here. You are talking about one system's essential package vs. another system's non-important tool. We can agree that the package priority level (important vs. standard vs. optional) is subjective, and we can agree that in many ways, in many cases, it may be a subjective call as to whether an executable belongs in /sbin vs. /usr/sbin, for example. But what I'm calling consistency is as follows: once you have determined the location of all the binary executables across a given repository, you then have a fixed, objective, algorithmic rule for determining the placement of all the _libraries_ in that repository. Here is the explicit algorithm (I don't necessarily expect anyone to actually do it this way, but I'm a mathematician and we mathematicians like to write stuff like this out to either prove the existence of well-defined algorithms, or conversely to expose underlying false assumptions, so let's give it a try): Library Placement Algorithm (LPA): 1) Consider the set of all possible binary executables that any package
Bug#652097: marked as done (sysvinit: breaks system on reboot)
Your message dated Thu, 15 Dec 2011 00:49:00 + with message-id e1razvm-0003ot...@franck.debian.org and subject line Bug#652097: fixed in sysvinit 2.88dsf-15 has caused the Debian Bug report #652097, regarding sysvinit: breaks system on reboot to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 652097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sysvinit Version: 2.88dsf-14 Severity: critical Justification: breaks the whole system Dear Maintainer, The new sysv packages in experimental look like they are breaking my system. reboot via # shutdown -r now, or # shutdown -h now, do not work, and the only way to reboot my machine is with magic-sysrq-b or hard reset. When the machine comes up again, login is displayed way too early (~3 seconds after grub), and once I login, the system seems to be severly broken... nothing besides root is mounted, hostname is not displayed, network has not been brought up, etc... If anyone else is hit with this, and you don't have sysv packages from unstable already in your cache for downgrading, the only way I've found is to chroot into your system via a livecd and downgrade that way to get your machine fully functional again. *note: System information was obtained with sysv packages at version 2.88dsf-13.13 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sysvinit depends on: ii initscripts 2.88dsf-13.13 ii libc6 2.13-22 ii libselinux1 2.1.0-4 ii libsepol1 2.1.0-1.1 ii sysv-rc 2.88dsf-13.13 ii sysvinit-utils 2.88dsf-13.13 sysvinit recommends no packages. sysvinit suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: sysvinit Source-Version: 2.88dsf-15 We believe that the bug you reported is fixed in the latest version of sysvinit, which is due to be installed in the Debian FTP archive: initscripts_2.88dsf-15_amd64.deb to main/s/sysvinit/initscripts_2.88dsf-15_amd64.deb sysv-rc_2.88dsf-15_all.deb to main/s/sysvinit/sysv-rc_2.88dsf-15_all.deb sysvinit-utils_2.88dsf-15_amd64.deb to main/s/sysvinit/sysvinit-utils_2.88dsf-15_amd64.deb sysvinit_2.88dsf-15.debian.tar.gz to main/s/sysvinit/sysvinit_2.88dsf-15.debian.tar.gz sysvinit_2.88dsf-15.dsc to main/s/sysvinit/sysvinit_2.88dsf-15.dsc sysvinit_2.88dsf-15_amd64.deb to main/s/sysvinit/sysvinit_2.88dsf-15_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 652...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger Leigh rle...@debian.org (supplier of updated sysvinit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Format: 1.8 Date: Thu, 15 Dec 2011 00:24:22 + Source: sysvinit Binary: sysvinit sysvinit-utils sysv-rc initscripts Architecture: source amd64 all Version: 2.88dsf-15 Distribution: experimental Urgency: low Maintainer: Debian sysvinit maintainers pkg-sysvinit-de...@lists.alioth.debian.org Changed-By: Roger Leigh rle...@debian.org Description: initscripts - scripts for initializing and shutting down the system sysv-rc- System-V-like runlevel change mechanism sysvinit - System-V-like init utilities sysvinit-utils - System-V-like utilities Closes: 651862 652097 Changes: sysvinit (2.88dsf-15) experimental; urgency=low . [ Roger Leigh ] * /etc/init.d/skeleton: Small whitespace cleanup. Thanks to Peter Eisentraut. (Closes: #651862) * Move all patches in debian/startpar/patches to debian/patches and make debian/startpar/ content a separate patch applied to startpar/. Build and install startpar in debian/rules. (Closes: #652097). Checksums-Sha1: f756378819d89bbd696821cad2818a4fc2112ded 1658 sysvinit_2.88dsf-15.dsc 5a12f8cacad7781aae58f8b1cfaec761a4b3163e 180832 sysvinit_2.88dsf-15.debian.tar.gz 6e8532b1d038535ee5465491bc935262f2d4282a 126142 sysvinit_2.88dsf-15_amd64.deb
Bug#650958: Is this really RC
So far it sounds like this affects one user and is hard for others to reproduce. I'm wondering if this is really RC? (I'd like to see the new krb5 get into testing and samba has to migrate first. I'm not sure what besides this bug is holding it back, possibly it's moot because of transition issues if there are library transitions going on.) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647030: marked as done ([kbibtex] FTBS on ia64: maybe bug on qt)
Your message dated Thu, 15 Dec 2011 03:32:26 + with message-id e1rb23w-00038r...@franck.debian.org and subject line Bug#647030: fixed in kbibtex 0.4-1 has caused the Debian Bug report #647030, regarding [kbibtex] FTBS on ia64: maybe bug on qt to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 647030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kbibtex Version: 0.3-1 Severity: serious According to https://buildd.debian.org/status/fetch.php?pkg=kbibtexarch=ia64ver=0.4~beta1-1stamp=1317542896 Fail to build on ia64 due to alignement problem. Bastien ---End Message--- ---BeginMessage--- Source: kbibtex Source-Version: 0.4-1 We believe that the bug you reported is fixed in the latest version of kbibtex, which is due to be installed in the Debian FTP archive: kbibtex_0.4-1.debian.tar.gz to main/k/kbibtex/kbibtex_0.4-1.debian.tar.gz kbibtex_0.4-1.dsc to main/k/kbibtex/kbibtex_0.4-1.dsc kbibtex_0.4-1_amd64.deb to main/k/kbibtex/kbibtex_0.4-1_amd64.deb kbibtex_0.4.orig.tar.bz2 to main/k/kbibtex/kbibtex_0.4.orig.tar.bz2 A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 647...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Hanke m...@debian.org (supplier of updated kbibtex package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 15 Dec 2011 03:43:34 +0100 Source: kbibtex Binary: kbibtex Architecture: source amd64 Version: 0.4-1 Distribution: unstable Urgency: low Maintainer: Michael Hanke m...@debian.org Changed-By: Michael Hanke m...@debian.org Description: kbibtex- BibTeX editor for KDE Closes: 647030 Changes: kbibtex (0.4-1) unstable; urgency=low . * New upstream release. * Add patch to disable -Wcast-align flag to prevent a (presumably) false-positive warning to cause a FTBFS (Closes: #647030). * Adjust debian/copyright to include a standalone paragraph for the GPL-2. * Added patch to allow compiling with latest GCC (missing header includes). Checksums-Sha1: 6465c880b17cb5a8e66b42f8cef08a1d20fd4497 1918 kbibtex_0.4-1.dsc 23eb1380bc737b57f35125d28d2066ebb19ed71b 191138 kbibtex_0.4.orig.tar.bz2 91e1efbc51f170fd366e775cdfc5daec2dffe3e6 4718 kbibtex_0.4-1.debian.tar.gz c6c4cefb279e96ab55e43edf9fc921a91a5fcae3 608522 kbibtex_0.4-1_amd64.deb Checksums-Sha256: 28eac1e0b9bf3cc208862515e3bdf44398a2e1bc655c42cea1597920a2140b8c 1918 kbibtex_0.4-1.dsc 9a7f969d645cebb50b653db811b6bba734eb93e44e72237e49c1a4dbc05700c3 191138 kbibtex_0.4.orig.tar.bz2 68ea3907905ec1f72322d4f40fae46eae663ae93e5d1ef1ed8e19d99d36cb0e0 4718 kbibtex_0.4-1.debian.tar.gz cb6e5ba4a0879b740f3eb108c083fd3af92057a9d9e1b6233fd0ccbb71bcb9dc 608522 kbibtex_0.4-1_amd64.deb Files: 0321c60e5ef8fe892276e967bc43438c 1918 kde optional kbibtex_0.4-1.dsc 4f8dd815bc2d5754812fdebb2a7d4abb 191138 kde optional kbibtex_0.4.orig.tar.bz2 4500dbef33dbe06f40eba81bf4a6702d 4718 kde optional kbibtex_0.4-1.debian.tar.gz 8a560301a5a36177eeec86d2f312e7fb 608522 kde optional kbibtex_0.4-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJO6WZ6AAoJEMBz0ih/+56beRQP/2DTa/zeAbEHGJKBojYmR0HV +gW3Le6/mMfOCsiWA+7T8+UVZFTTxFTpUVikuYDNoxv6Op94Vfuj+FOq3WRo6ia4 MMbLDEgKwB/2wqxMSjCQEs2enj7uk4R35zNVQT61v9ccB+BZ0xNRmprZhNeeWRBk MzpDovz1pYw26k75PLUAT13nvUE/zKTOTJBr9OHUavHnHSYcIEK5T+XpUzv3VTVZ c1qTg8HONsvfPGaYgTn0xpAp98U6f+2aDuwxVRRUIjfd1/mqiuS/5tUO2ee0OfG2 ZaJYP4kkGCqGDMSboxpIKMGu15qKS+xs5yyyFNsorIcqVoEdG5Vnda+ooJKyAGHe VV/iepPERbcBjOcRnaKzUjNNVx61OerDPrfkbr38VcRZa8lLQUYKW7IQ2ncoToDW ck5iPXGAWKCStJ6JyKx9ueNfF00COYhCDrW3kK1pntQPA11HiFYccr145galewpy NOZobIGXOnVoKMQNhnGmNq4AnhVHv5ltNl6E0J/GgJNmcet66YjrbYJ9TzAJUaco +fv+GJXOH9uAqkJOF4WAZlt8fE4NLbNw5G7s9ij5v/z36bzjO1mxO82oaVuSPePf x9aPnQgmQkoSIqQiT7HTJjqyf1oQr1kdBcep5EmSoWSvX4JGzb9bPEpWuinZIEJ7 iasZoKCnb/erS9qf1Rp9 =jgxs -END PGP SIGNATURE- ---End Message---
Bug#652115: ruby1.8: FTBFS on sparc: ./sample/test.rb:1848: [BUG] Bus Error
On 14/12/11 at 23:40 +0100, Jakub Wilk wrote:
Source: ruby1.8
Version: 1.8.7.352-2
Severity: serious
Justification: fails to build from source
User: debian-sp...@lists.debian.org
Usertags: sparc
ruby1.8 FTBFS on sparc:
| ./sample/test.rb:1848: [BUG] Bus Error
| ruby 1.8.7 (2011-06-30 patchlevel 352) [sparc-linux]
|
| test failed
| make[1]: *** [test] Error 1
| make[1]: Leaving directory
`/build/buildd-ruby1.8_1.8.7.352-2-sparc-NViQ1Z/ruby1.8-1.8.7.352'
| make: *** [debian/stamp-makefile-build] Error 2
Full build log:
https://buildd.debian.org/status/fetch.php?pkg=ruby1.8arch=sparcver=1.8.7.352-2stamp=1323883832
Hi,
I have a pending mail in my inbox about sparc (see attachment). The last
days before the christmas vacations are just crazy, but I should be able
to address this next week.
Lucas
---BeginMessage---
On Thu, Nov 03, 2011 at 06:31:45AM +0100, Lucas Nussbaum wrote:
On 03/11/11 at 00:45 +, Jurij Smakov wrote:
[sparc] continuations are completely broken.
See http://redmine.ruby-lang.org/issues/5244 (minimal test case
included)
Much progress on that, thanks to Jurij Smakov who also took it to the
sparclinux list (thread at
http://thread.gmane.org/gmane.linux.ports.sparc/15364).
A partial fix has been commited upstream. I'm waiting for a final
decision to backport it.
FWIW, I've posted a patch which implements what I consider a proper
fix for this issue to the upstream bug. Since it's already closed and
Ruby bug tracker does not allow mere mortals to reopen, I'm not
even certain whether any of the upstream maintainers will notice it.
Thanks a lot! I will monitor the bug and make sure it ends up in Ruby
upstream and in the Debian package.
Lucas, please see the attached patches. The first one is a backport of
Ruby upstream commits r33757 and r33758 fixing the continuations
issue, which applies cleanly to Debian's ruby1.9.1-1.9.3.0-1. The
second patch turns off -fno-tree-sra hack (the problem is fixed in
gcc-4.6 4.6.2-6, which made it to unstable yesterday) and re-enables
the test suite for Debian on sparc. I've just confirmed that with
these patches applied ruby1.9.1-1.9.3.0-1 Debian package
successfully builds and the test suite passes. Note that the first
patch requires regenerating the configure script.
That renders bugs #593138 and #545345 obsolete, at least for unstable.
Best regards,
--
Jurij Smakov ju...@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
diff -aurN a/configure.in b/configure.in
--- a/configure.in 2011-12-10 08:59:53.0 +
+++ b/configure.in 2011-12-10 09:09:19.24408 +
@@ -1133,7 +1133,8 @@
[CFLAGS=-mieee $CFLAGS],
[osf*],# ccc
[CFLAGS=-ieee $CFLAGS],
- )])
+ )],
+[sparc*], [AC_LIBOBJ([sparc])])
ac_cv_header_net_socket_h=${ac_cv_header_net_socket_h=no}
if test $ac_cv_header_net_socket_h = yes; then
diff -aurN a/include/ruby/defines.h b/include/ruby/defines.h
--- a/include/ruby/defines.h 2011-06-06 07:11:37.0 +0100
+++ b/include/ruby/defines.h 2011-12-10 09:12:35.472002372 +
@@ -268,21 +268,8 @@
#endif
#if defined(sparc) || defined(__sparc__)
-static inline void
-flush_register_windows(void)
-{
-asm
-#ifdef __GNUC__
- volatile
-#endif
-# if defined(__sparc_v9__) || defined(__sparcv9) || defined(__arch64__)
- (flushw)
-# else
- (ta 0x03)
-# endif /* trap always to flush register windows if we are on a Sparc system */
- ;
-}
-# define FLUSH_REGISTER_WINDOWS flush_register_windows()
+void rb_sparc_flush_register_windows(void);
+# define FLUSH_REGISTER_WINDOWS rb_sparc_flush_register_windows()
#elif defined(__ia64)
void *rb_ia64_bsp(void);
void rb_ia64_flushrs(void);
diff -aurN a/sparc.c b/sparc.c
--- a/sparc.c 1970-01-01 01:00:00.0 +0100
+++ b/sparc.c 2011-12-10 09:12:50.155998557 +
@@ -0,0 +1,30 @@
+/
+ Flush register windows on sparc.
+
+ This function is in a separate file to prevent inlining. The flushw
+ assembler instruction used on sparcv9 flushes all register windows
+ except the current one, so if it is inlined, the current register
+ window of the process executing the instruction will not be flushed
+ correctly.
+
+ See http://redmine.ruby-lang.org/issues/5244 for discussion.
+*/
+void rb_sparc_flush_register_windows(void)
+{
+asm
+#ifdef __GNUC__
+__volatile__
+#endif
+
+/* This condition should be in sync with one in configure.in */
+#if defined(__sparcv9) || defined(__sparc_v9__) || defined(__arch64__)
+# ifdef __GNUC__
+(flushw : : : %o7)
+# else
+(flushw)
+# endif /* __GNUC__ */
+#else
+(ta 0x03)
+#endif
+;
+}
--- a/debian/rules 2011-10-31 07:38:05.0 +
+++ b/debian/rules 2011-12-10 09:15:42.652004446 +
@@ -39,7 +39,7 @@
else
CFLAGS += -g -O2
# Workaround for
Bug#650958: [Pkg-samba-maint] Bug#650958: Is this really RC
severity 650958 important thanks Quoting Sam Hartman (hartm...@mit.edu): So far it sounds like this affects one user and is hard for others to reproduce. I'm wondering if this is really RC? (I'd like to see the new krb5 get into testing and samba has to migrate first. I'm not sure what besides this bug is holding it back, possibly it's moot because of transition issues if there are library transitions going on.) Each time I see this bug at the top of my TODO pile, I'm wondering: - is it really RC (very probably affects only one architecture which I more or less consider as a toy architecture nowadays, particularly when it comes at building samba servers)? - is it reproducible on all powerpc systems? - is it really a samba issue? So, I would definitely agree to lower the bug's severity as it indirectly affects krb5. We really don't want to keep such an important package out of testing for a toy architecture and without even knowing if the issue really belongs to our packages. Done.. Thanks, Sam, for bringing me the last argument that convinced me to do what I was about to do since the beginning...:-) Anyway, if one of my comaintainers disagrees, he will have the opportunity to raise the bug's severity again, but then it means he commits himself to investigate the issue (wink). signature.asc Description: Digital signature
Processed: Re: [Pkg-samba-maint] Bug#650958: Is this really RC
Processing commands for cont...@bugs.debian.org: severity 650958 important Bug #650958 [samba] samba INTERNAL ERROR: Signal 11 - PANIC - BACKTRACE: 16 stack frames Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 650958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
