Processed (with 1 errors): fixed 564353 in 2.8.2-1, notfixed 564353 in src:openscenegraph/2.8.2-1
Processing commands for cont...@bugs.debian.org:
# Let's fix version information:
fixed 564353 2.8.2-1
Bug #564353 {Done: Manuel A. Fernandez Montecelo
manuel.montez...@gmail.com} [src:openscenegraph] openscenegraph: FTBFS:
Nonexistent build-dependency: libcoin40-dev
Bug Marked as fixed in versions openscenegraph/2.8.2-1.
notfixed 564353 src:openscenegraph/2.8.2-1
Unknown command or malformed arguments to command.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
564353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564353
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#589490: startupmanager crashes on amd64
Package: startupmanager Version: 1.9.13-5 Severity: grave Justification: renders package unusable Startupmanager is crashing on start with following error messages : Generating grub.cfg ... Found background image: Lake_mapourika_NZ1.tga Found linux image: /boot/vmlinuz-2.6.34-1-amd64 Found initrd image: /boot/initrd.img-2.6.34-1-amd64 Found linux image: /boot/vmlinuz-2.6.34 Found initrd image: /boot/initrd.img-2.6.34 Found Microsoft Windows XP Professionnel on /dev/sdb1 Found Ubuntu 10.04 LTS (10.04) on /dev/sdc12 Found Debian GNU/Linux (squeeze/sid) on /dev/sdc6 Found Windows 7 (loader) on /dev/sdd1 done Grub2 detected Usplash detected Splashy not detected Traceback (most recent call last): File /usr/sbin/startupmanager, line 54, in module main() File /usr/sbin/startupmanager, line 51, in main SumGui() File /usr/share/startupmanager/gtk_frontend.py, line 193, in __init__ self.setup_widgets() File /usr/share/startupmanager/gtk_frontend.py, line 202, in setup_widgets self.set_shared_grub_widgets() File /usr/share/startupmanager/gtk_frontend.py, line 223, in set_shared_grub_widgets self.timeout_spinner.set_value(self.grub.get_timeout()) File /usr/lib/pymodules/python2.6/bootconfig/grub.py, line 91, in get_timeout timeout = utils.extract_number(line) File /usr/lib/pymodules/python2.6/bootconfig/utils.py, line 64, in extract_number match = number_filter.search(line) TypeError: expected string or buffer zsh: exit 1 sudo startupmanager Any clue ?? Regards mahashakti89 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (996, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34-1-amd64 (SMP w/2 CPU cores) 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 startupmanager depends on: ii grub-pc 1.98+20100710-1 GRand Unified Bootloader, version ii menu 2.1.43 generates programs menu for all me ii python 2.6.5-8 interactive high-level object-orie ii python-glade22.17.0-2GTK+ bindings: Glade support ii python-gnome22.28.1-1Python bindings for the GNOME desk ii python-libxml2 2.7.7.dfsg-4Python bindings for the GNOME XML ii python-support 1.0.9 automated rebuilding support for P ii x11-xserver-utils7.5+1 X server utilities ii yelp 2.30.1+webkit-1 Help browser for GNOME startupmanager recommends no packages. startupmanager 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#576445: [patch]: sgml-base: Fails to purge
On Sat, 17 Jul 2010 16:27:52 +0200 Michael Banck mba...@debian.org wrote: On Mon, Apr 12, 2010 at 05:39:07PM +0900, Hideki Yamane wrote: +## remove /etc/sgml and /var/lib/sgml-base +for dir in /etc/sgml /var/lib/sgml-base +if [ -d $dir ]; then + rmdir --ignore-fail-on-non-empty $dir +fi This is not correct shell-code, you're missing the do ... done statements. I will upload the attached NMU from the current BSP by the end of the weekend if no maintainer upload happens. Oh, and thanks Michael, I'm happy to hear it'll be fixed with your patch :) -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- 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#589211: Python exceptions in status icon options
Processing commands for cont...@bugs.debian.org: tags 589211 + patch Bug #589211 [gtk-redshift] Python exceptions in status icon options Added tag(s) patch. clone 589211 -1 Bug#589211: Python exceptions in status icon options Bug 589211 cloned as bug 589494. retitle -1 gtk-redshift: doesn't depend on python Bug #589494 [gtk-redshift] Python exceptions in status icon options Changed Bug title to 'gtk-redshift: doesn't depend on python' from 'Python exceptions in status icon options' severity -1 serious Bug #589494 [gtk-redshift] gtk-redshift: doesn't depend on python Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 589494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589494 589211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589211 -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
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 588983 + pending Bug #588983 [python-feedvalidator] python-feedvalidator: errors out with ImportError: No module named Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 588983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588983 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#583832: marked as done (dulwich: FTBFS: FAILED (SKIP=2, errors=7))
Your message dated Sun, 18 Jul 2010 10:51:50 +0200 with message-id 87y6d99nq1@chillida.ipv6.sieglitzhof.net and subject line builds fine on porterbox, builds on same buildd now has caused the Debian Bug report #583832, regarding dulwich: FTBFS: FAILED (SKIP=2, errors=7) 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.) -- 583832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: dulwich Version: 0.6.0-4 Severity: important User: debian-...@lists.debian.org Usertags: kfreebsd Hi, your package FTBFS on kfreebsd-i386 (but not kfreebsd-amd64) with: | Ran 335 tests in 51.597s | FAILED (SKIP=2, errors=7) A quick grep shows: | ERROR: test_fetch_pack (test_client.DulwichClientTest) | ERROR: test_incremental_fetch_pack (test_client.DulwichClientTest) | ERROR: test_send_pack (test_client.DulwichClientTest) | ERROR: test_send_pack_multiple_errors (test_client.DulwichClientTest) | ERROR: test_send_pack_nothing_to_send (test_client.DulwichClientTest) | ERROR: test_send_pack_one_error (test_client.DulwichClientTest) | ERROR: test_send_without_report_status (test_client.DulwichClientTest) Full build logs: https://buildd.debian.org/status/package.php?p=dulwich Mraw, KiBi. ---End Message--- ---BeginMessage--- Hi all! dulwich is now building on both, the buildd where it failed previously and the k-i porterbox so assuming this was a temporary problem. Regards Christoph pgpI3HTS8vvhf.pgp Description: PGP signature ---End Message---
Bug#588608: aptitude (priority important) depends on libboost-iostreams (priority optional)
On Thu, Jul 15, 2010 at 09:17:38PM -0700, Russ Allbery wrote: I wouldn't place any of Boost in that category. In fact, I wouldn't place aptitude in that category, either. aptitude was historically the recommended tool to use for upgrades because it had the best dependency resolver for handling the dist-upgrade case. For so long as that's true, it should be priority: important, which means that by definition the things that it requires are also priority: important or higher. If apt-get is now strong enough that we can recommend it for upgrades without qualms, then aptitude is another alternative package manager and standard may be fine. Is that now the case? Not only is apt-get now strong enough to handle the cases for which we recommended aptitude in the sarge timeframe (with much better resolution of upgrades, installation of Recommends by default, and tracking of auto-installed packages), but aptitude has also had several deplorable regressions since etch. I don't know which of these made it into the lenny release or which are still present in squeeze, but: - When I type 'aptitude install foo', *removing* foo instead of upgrading is not a valid solution and should never be offered. - When I type 'aptitude install foo', installing 5 packages, removing 3 others, and upgrading 7 more *without installing foo* is not a valid solution and should never be offered. And the reason I don't know if these regressions are still present in lenny or squeeze is that, after about the second time running into such issues, I abandoned use of aptitude altogether. It's one thing to be unable to find a solution and throw me an error; I have no patience for tools that do something other than what I tell them to. On Sat, Jul 17, 2010 at 12:43:05AM +0900, Osamu Aoki wrote: Though I think any manual published on debian.org recommending aptitude for upgrades is a bug that should be fixed. I fail to understand your intent of this statement. Are you suggesting me to change the following text? Aptitude is the current preferred package management tool for the Debian system. Yes, I believe this text should be changed. How does it need to be changed? I am very curious and open for suggestion. I believe the correct recommendations would be: - apt-get for all commandline operations, including package installation and removal, and dist-upgrades - aptitude for an interactive text interface for managing the installed packages - update-manager for keeping your system up-to-date if you're running the default GNOME desktop. Please note this document[1] is claimed to be a secondary documentation. I am merely following the primary documentation: http://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#upgradingpackages | Release Notes for Debian GNU/Linux 5.0 (lenny) | | 4.5. Upgrading packages | | The recommended way to upgrade from previous Debian GNU/Linux releases | is to use the package management tool aptitude. This program makes safer | decisions about package installations than running apt-get directly. As I recall, there were long active discussion to reach this text. So at least, this assessment is not an opinion of a single developer. Two things: - This is a recommendation to use it as a tool for upgrading from previous releases, and is not an endorsement of the tool as a preferred package manager for other operations. The upgrade instructions in the release notes are carefully crafted to try to smoothly and correctly handle upgrades on as many users' systems as possible, and for that reason, solutions should be considered for each release that use tools other than those recommended for daily operations. - The recommendation in the release notes was correct /at the time it was drafted/ (i.e., for sarge). By lenny, it was giving noticeably worse results than apt-get in many cases, but by the time the issue was raised, some felt it was too late in the release cycle to revisit the text. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#588608: aptitude (priority important) depends on libboost-iostreams (priority optional)
On Fri, Jul 16, 2010 at 11:59:45AM +0200, Frans Pop wrote: Steve Langasek wrote: This manual represents the opinion of a single developer. And what does that have to do with the price of bananas in Iceland? The fact that aptitude is currently the recommended tool for package management has various reasons: user interface, features, dependency handling, etc. That status has evolved over the last 3 or so release cycles. You have even been part of some of the discussions (for example sarge - etch upgrade issues) Dependency handing is certainly not a reason to recommend aptitude. Yes, I was part of the discussions recommending it for release upgrades in the sarge and etch timeframe. For lenny, I strongly counseled *against* recommending aptitude for release upgrades, due to some concrete regressions in aptitude's upgrade handling at the same time that apt itself had reached parity on all the relevant features (improved upgrade resolver; Recommends handling). It remained in the release notes anyway owing to concerns that it was too late in the cycle to get good tester feedback on upgrades using apt-get, but I intend to again advise removing aptitude from the squeeze release notes in favor of apt-get. aptitude's resolver is just too inconsistent and has too many pathological edge cases for it to be a good idea to recommend its use as a dist-upgrader. Now for interactive upgrades, aptitude does have the best interface. But it doesn't follow that it should be Priority: important as a result; there are any number of packages that we may recommend for one purpose or another that nevertheless shouldn't be installed as 'important'. aptitude is the primary tool used by Debian Installer (and because of that its current priority of important is actally necessary). This is the only reason I see that it should be 'important'. I'm not (yet) convinced that this is necessary. Some alternatives would seem to be: - opportunistically install aptitude when a user wants fine-grained package selection in the installer; otherwise only install it when the 'standard' task is selected. (Downside: user has to wait for aptitude to be installed, introducing delay at another point in the installer.) - have the installer special-case the automatic installation of aptitude in spite of not being Priority: important, so that it's available at the right point in the installer. (Downside: special-casing; and if the user doesn't select the standard task, we either uninstall it at the end of the install leaving users without access to this interface post-install, or we leave it on everybody's system anyway, in which case it might as well just be Priority: important.) These are some other options to think about, but on balance, I would conclude that raising the priority of libboost-iostreams to important is actually the right solution. Boost is an annoyingly unstable library to depend on and its library transitions are painful, but most of the individual component libraries (including libboost-iostreams) are actually quite small with no unusual dependencies; and raising one of these components to important shouldn't cause any problems. It is also recommended in both the Release Notes (for stable release upgrades) and the Installation Guide. The first of these is a bug that needs fixed. The second is a reasonable recommendation if we're pointing users at the TUI; for the CLI we should simply recommend apt-get. So what's listed in the Debian Reference is a correct reflection of aptitude's current status and not, as you imply, the result of some single developer being on crack. Right, it's the result of several developers being on crack. :-P Regardless of whether there are other developers who agree with this particular opinion (which, for any given opinion, is bound to be the case), I think it's important to distinguish between documents whose drafting is done on open mailing lists and whose recommendations are the result of consensus (Debian Policy; DevRef, now that it's on debian-policy; Installation Guide; Release Notes) and those that are maintained by individuals. The latter are useful, but are not the word of the Project. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588983: marked as done (python-feedvalidator: errors out with ImportError: No module named ....)
Your message dated Sun, 18 Jul 2010 09:19:02 +
with message-id e1oaq1w-0005s8...@franck.debian.org
and subject line Bug#588983: fixed in python-feedvalidator 0~svn1022-2
has caused the Debian Bug report #588983,
regarding python-feedvalidator: errors out with ImportError: No module named
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.)
--
588983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-feedvalidator
Version: 0~svn1022-1
Severity: grave
Tags: l10n
Justification: renders package unusable
The issue is that with Debian squeeze /etc/default/locale now defines
LANGUAGE. On my system that file looks like this
# File generated by update-locale
#LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
The result is that LANGUAGE string is supplied as an environment
variable to all users which kills feedvalidator completely.
Here is the locale and the associated typical error for one of the
users on this system:
barb...@raven locale |grep LANG
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
barb...@raven feedvalidator highlights.atom
Validating file:///home/barbara/linuxlinks/loll/highlights.atom
Traceback (most recent call last):
File /usr/bin/feedvalidator, line 101, in module
main()
File /usr/bin/feedvalidator, line 97, in main
run()
File /usr/bin/feedvalidator, line 47, in run
from feedvalidator.formatter.text_plain import Formatter
File /usr/lib/pymodules/python2.6/feedvalidator/formatter/text_plain.py,
line 9, in module
from base import BaseFormatter
File /usr/lib/pymodules/python2.6/feedvalidator/formatter/base.py, line 12,
in module
lang = __import__('feedvalidator.i18n.%s' % LANGUAGE, globals(), locals(),
LANGUAGE)
ImportError: No module named en_CA:en
A quick look at the package list for python-feedvalidator indicates
the only i18n module there is called en.py. Indeed a workaround for
this issue is to set the LANGUAGE environment variable as follows:
LANGUAGE=en
before running feedvalidator. But unless people figure that out,
this bug means that nobody can use feedvalidator which is why I
have classified this as a grave error.
A quick look at en.py indicates it contains english error messages for
feedvalidator. If there is no prospect of translating those to
other languages, then I suggest simply importing that module
directly in /usr/lib/pymodules/python2.6/feedvalidator/formatter/base.py
without fooling around with LANGUAGE at all. Otherwise, you could do
something more complicated like use only the first two characters
of LANGUAGE to identify the language and store those in LA and
use that variable instead, but then if it fails to import
LA.py, fall back to en.py.
But without one of those fixes, python-feedvalidator will be broken
for everybody who is not aware of the LANGUAGE=en workaround.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-feedvalidator depends on:
ii python 2.6.5-5 An interactive high-level object-o
ii python-libxml2 2.7.7.dfsg-4 Python bindings for the GNOME XML
ii python-rdflib 2.4.2-1+b1 RDF library containing an RDF trip
ii python-support 1.0.9automated rebuilding support for P
python-feedvalidator recommends no packages.
python-feedvalidator suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: python-feedvalidator
Source-Version: 0~svn1022-2
We believe that the bug you reported is fixed in the latest version of
python-feedvalidator, which is due to be installed in the Debian FTP archive:
python-feedvalidator_0~svn1022-2.diff.gz
to main/p/python-feedvalidator/python-feedvalidator_0~svn1022-2.diff.gz
python-feedvalidator_0~svn1022-2.dsc
to main/p/python-feedvalidator/python-feedvalidator_0~svn1022-2.dsc
python-feedvalidator_0~svn1022-2_all.deb
to main/p/python-feedvalidator/python-feedvalidator_0~svn1022-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 588...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jakub Wilk jw...@debian.org (supplier of
Bug#589500: projectcenter.app: Cannot load the main model file 'ProjectCenter.gorm'
Package: projectcenter.app Version: 0.5.3~20100601-2 Severity: grave Justification: renders package unusable Hi, when I try to run ProjectCenter I get error messages: 2010-07-18 11:30:57.203 ProjectCenter[5618] Exception occured while loading model: the volatile domain Hungarian already exists 2010-07-18 11:30:57.207 ProjectCenter[5618] Failed to load Gorm 2010-07-18 11:30:57.207 ProjectCenter[5618] Could not load Gorm file: /usr/lib/GNUstep/Applications/ProjectCenter.app/Resources/English.lproj/ProjectCenter.gorm 2010-07-18 11:30:57.208 ProjectCenter[5618] Cannot load the main model file 'ProjectCenter.gorm' so I run ProjectCenter with gdb to get a backtrace what happening: csanyi...@debian:~$ gdb ProjectCenter GNU gdb (GDB) 7.0.1-debian Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/ProjectCenter...(no debugging symbols found)...done. (gdb) break -[NSException raise] Function -[NSException raise] not defined. Make breakpoint pending on future shared library load? (y or [n]) (gdb) r --GNU-Debug=dflt Starting program: /usr/bin/ProjectCenter --GNU-Debug=dflt [Thread debugging using libthread_db enabled] 2010-07-18 11:47:20.116 ProjectCenter[5852] Loading Backend from /usr/lib/GNUstep/Bundles/libgnustep-cairo-016.bundle 2010-07-18 11:47:20.377 ProjectCenter[5852] Initializing GNUstep x11 backend. 2010-07-18 11:47:20.380 ProjectCenter[5852] Opened display :0.0, display 0 screen 0 2010-07-18 11:47:20.456 ProjectCenter[5852] Found font family LMMonoPropLt10 2010-07-18 11:47:20.456 ProjectCenter[5852] fc enumerator: adding font: LMMonoPropLt10-BoldOblique 2010-07-18 11:47:20.456 ProjectCenter[5852] Found font family Century Schoolbook L 2010-07-18 11:47:20.456 ProjectCenter[5852] fc enumerator: adding font: Century Schoolbook L-BoldItalic 2010-07-18 11:47:20.456 ProjectCenter[5852] Found font family LMSansQuot8 2010-07-18 11:47:20.456 ProjectCenter[5852] fc enumerator: adding font: LMSansQuot8-BoldOblique 2010-07-18 11:47:20.456 ProjectCenter[5852] Found font family LMMonoLt10 2010-07-18 11:47:20.456 ProjectCenter[5852] fc enumerator: adding font: LMMonoLt10-LightOblique 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: LMMonoLt10-Light 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: Century Schoolbook L 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: LMSansQuot8-Bold 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: Century Schoolbook L-Italic 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: LMSansQuot8-Oblique 2010-07-18 11:47:20.457 ProjectCenter[5852] Found font family LMMathSymbols10 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: LMMathSymbols10-BoldItalic 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: LMSansQuot8 2010-07-18 11:47:20.457 ProjectCenter[5852] Found font family LMSans8 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: LMSans8 2010-07-18 11:47:20.457 ProjectCenter[5852] Found font family LMSans9 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: LMSans9 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: LMMathSymbols10-Italic 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: LMSans8-Oblique 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: LMSans9-Oblique 2010-07-18 11:47:20.457 ProjectCenter[5852] Found font family LMRomanSlant8 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: LMRomanSlant8-Italic 2010-07-18 11:47:20.457 ProjectCenter[5852] Found font family LMRomanSlant9 2010-07-18 11:47:20.457 ProjectCenter[5852] fc enumerator: adding font: LMRomanSlant9-Italic 2010-07-18 11:47:20.457 ProjectCenter[5852] Found font family LMMonoSlant10 2010-07-18 11:47:20.458 ProjectCenter[5852] fc enumerator: adding font: LMMonoSlant10-Italic 2010-07-18 11:47:20.458 ProjectCenter[5852] Found font family DejaVu Sans Mono 2010-07-18 11:47:20.458 ProjectCenter[5852] fc enumerator: adding font: DejaVu Sans Mono-Oblique 2010-07-18 11:47:20.458 ProjectCenter[5852] fc enumerator: adding font: DejaVu Sans Mono 2010-07-18 11:47:20.458 ProjectCenter[5852] fc enumerator: adding font: DejaVu Sans Mono-BoldOblique 2010-07-18 11:47:20.458 ProjectCenter[5852] fc enumerator: adding font: DejaVu Sans Mono-Bold 2010-07-18 11:47:20.458 ProjectCenter[5852] Found font family URW Palladio L 2010-07-18 11:47:20.458 ProjectCenter[5852] fc enumerator: adding font: URW Palladio L-Italic
Bug#577513: libdbd-sybase-perl: DBI/DBD internal version mismatch
Hi Gregor,
On Sat, Jul 17, 2010 at 05:50:12PM +0200, gregor herrmann wrote:
On Sat, 24 Apr 2010 17:35:03 +0900, Ansgar Burchardt wrote:
as the binNMUs have reached testing by now, libdbd-sybase-perl can be
updated to add a dependency on perl-dbdabi-*. I have prepared a patch
to do this. It also resolves several of lintian's warnings about the
packaging.
I wanted to ask about your plans for this bug. Is there anything else
we (as in: the Debian Perl Group) can do? Would you like me to upload
the package with Ansgar's patch? Anything else?
I've been postponing dealing with this bug, hoping that someone in the
Debian Perl Group would spontaneously provide a better interface for this
than the current one. The perl-dbdabi-* virtual package seems sensible
enough, but I'm not happy about including external makefiles in my
debian/rules. Could you please provide a dh_* command for this that adds
the value to the existing ${misc:Depends} variable?
Also, why does libdbd-sybase-perl need to depend on *both* libdbi-perl *an*
perl-dbdabi-*, given that the latter is provided by the former? Depending
on libdbi-perl looks quite redundant to me.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
Processed (with 1 errors): reopening 490180, reopening 450577
Processing commands for cont...@bugs.debian.org:
# Fixes for these bugs were reverted in 0.14.1-1:
reopen 490180
Bug #490180 {Done: Gustavo Noronha Silva gustavo.noro...@collabora.co.uk}
[python-pygoocanvas] Pygoocanvas needs python-cairo = 1.4
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
reopen 450577
Failed to reopen 450577: Not altering archived bugs; see unarchive.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
450577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450577
490180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490180
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: Re: Bug#588807: ImportError: No module named errors
Processing commands for cont...@bugs.debian.org: severity 588807 serious Bug #588807 [python-sphinx] ImportError: No module named errors Severity set to 'serious' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 588807: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588807 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#588807: ImportError: No module named errors
severity 588807 serious thanks * Julian Andres Klode j...@debian.org, 2010-07-12, 15:26: This causes python-apt to FTBFS: This doesn't warrant severity critical usually. Traceback (most recent call last): File setup.py, line 21, in module from sphinx.setup_command import BuildDoc File /usr/lib/python2.6/dist-packages/sphinx/setup_command.py, line 20, in module from sphinx.application import Sphinx File /usr/lib/python2.6/dist-packages/sphinx/application.py, line 24, in module from sphinx.config import Config File /usr/lib/python2.6/dist-packages/sphinx/config.py, line 17, in module from sphinx.errors import ConfigError ImportError: No module named errors Are files in /usr/lib/python2.6/dist-packages/sphinx/ symlinks? If this is the case, please remove the whole directory and merge this bug with #559572. -- Jakub Wilk signature.asc Description: Digital signature
Processed: tagging 583475
Processing commands for cont...@bugs.debian.org: tags 583475 + patch Bug #583475 [libllvm-ocaml-dev] libllvm-ocaml-dev: META file for ocaml-llvm has a wrong filename Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 583475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583475 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#585966: pdns-server: init.d script should provide the virtual facility $named
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, What contents should the file /etc/insserv.conf.d/pdns-server have? For the other bug reported, I'll check if the pdns-server is running or not before letting the script proceed. I'm planning to upload the package this afternoon. Regards, Matthijs Mohlmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxC3zIACgkQ2n1ROIkXqbB3pQCgo5zdTaC9z88kEgc913rJwMfl vXwAoIT2VktQEiSCDXDNKrsTeBGpZBOL =l4Gs -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#585966: pdns-server: init.d script should provide the virtual facility $named
[Matthijs Möhlmann] What contents should the file /etc/insserv.conf.d/pdns-server have? I believe this is the content needed: $named pdns It will add a hard dependency from $named to pdns. For the other bug reported, I'll check if the pdns-server is running or not before letting the script proceed. Great. Not sure if that is enough. Perhaps it is a idea to verify that it is listening on its port and replying to requests before continuing? The proper fix would be to change the source to make sure the config is loaded and the ports bound before forking, to ensure the server is operational. I'm planning to upload the package this afternoon. Great. :) 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#542285: debian packages of guile 1.9/2.0
Hi, On Sat 17 Jul 2010 14:50, l...@gnu.org (Ludovic Courtès) writes: Andy Wingo wi...@pobox.com writes: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542285. Is there any chance you could prod those folks? Ludo, can we get libgc people to help? Yes, the Debian folks just need to report upstream, if that’s not already done, and they’ll probably quickly get an answer. FWIW, people have been meaning to release libgc 7.2 for a while, which may fix the problem (and optionally add other problems ;-)). Copying the Debian libgc maintainer, then. With a report upstream, hopefully the libgc people can handle the Debian FTBFS problem themselves :) Andy -- http://wingolog.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 574042
Processing commands for cont...@bugs.debian.org: tags 574042 pending Bug #574042 [libnids] libnids1.21: Maintainer email address not working Bug #586602 [libnids] libnids: broken maintainer address Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 574042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574042 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#588550: [buildd-tools-devel] Bug#588550: sbuild: Fails to build binNMUs for packages with urgency comments in changelogs
On Fri, Jul 16, 2010 at 08:41:52PM +0200, Michael Banck wrote: tags 588550 +patch thanks On Fri, Jul 09, 2010 at 04:20:42PM +0100, Adam D. Barratt wrote: The recently scheduled binNMUs of the mandos package failed due to a problem with the auto-generated binNMU changelog; from one of the logs: parsechangelog/debian: warning: debian/changelog(l1): unrecognised line LINE: (1.0.14-1+b1) unstable; urgency=low parsechangelog/debian: error: Can't call method as_string on an undefined value at /usr/share/perl5/Dpkg/Changelog.pm line 250, STDIN line 8. This appears to be due to line 830 of lib/Sbuild/Build.pm which does: $firstline =~ /^(\S+)\s+\((\S+)\)\s+([^;]+)\s*;\s*urgency=(\S+)\s*$/; The most recent header line from the mandos changelog is: mandos (1.0.14-1) unstable; urgency=low (HIGH on mips and mipsel) Although unusual, this form is permitted by section 5.6.17 of Policy. I propose the attached patch, which ignores the rest of the line after the urgency field; I can successfully binNMU mandos_1.0.14-1 with it. I will probably upload the fix by the rest of weekend, if I don't hear complaints. That sounds fine to me. Please do a binNMU rather than using git master, which currently has some issues. Feel free to commit this fix onto git master and buildd branches, though! 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. signature.asc Description: Digital signature
Bug#588807: ImportError: No module named errors
merge 559572 588807 thanks On So, 2010-07-18 at 10:55 +0200, Jakub Wilk wrote: severity 588807 serious thanks * Julian Andres Klode j...@debian.org, 2010-07-12, 15:26: This causes python-apt to FTBFS: This doesn't warrant severity critical usually. I don't know why I chose critical. Traceback (most recent call last): File setup.py, line 21, in module from sphinx.setup_command import BuildDoc File /usr/lib/python2.6/dist-packages/sphinx/setup_command.py, line 20, in module from sphinx.application import Sphinx File /usr/lib/python2.6/dist-packages/sphinx/application.py, line 24, in module from sphinx.config import Config File /usr/lib/python2.6/dist-packages/sphinx/config.py, line 17, in module from sphinx.errors import ConfigError ImportError: No module named errors Are files in /usr/lib/python2.6/dist-packages/sphinx/ symlinks? If this is the case, please remove the whole directory and merge this bug with #559572. yes, there were symlinks; removing the directory fixes it. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.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#588807: ImportError: No module named errors
Processing commands for cont...@bugs.debian.org: merge 559572 588807 Bug#559572: python-sphinx: doesn't remove python-central leftovers Bug#588807: ImportError: No module named errors Merged 559572 588807. thanks Stopping processing here. Please contact me if you need assistance. -- 559572: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559572 588807: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588807 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#589513: /etc/init.d/mysql: line 75: /usr/bin/mysqladmin: No such file or directory
Package: mysql-server-core-5.1 Version: 5.1.48-1 Severity: grave Justification: renders package unusable This week, after full upgrading three different debian testing machines (after a 3 months stop in upgrades), I realize that mysqld is not started at boot. Here's some info. kernel log: 2010-07-18 13:47:14 fermi /etc/init.d/mysql[1968] 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in 2010-07-18 13:47:14 fermi /etc/init.d/mysql[1968] /etc/init.d/mysql: line 75: /usr/bin/mysqladmin: No such file or directory fermi:~# aptitude search ~i mysql i A libmysqlclient16 - MySQL database client library i A libqt4-sql-mysql - Qt 4 MySQL database driver i A mysql-common - MySQL database common files, e.g. /etc/mysql/my.cn i A mysql-server-core-5.1- MySQL database server binaries fermi:~# aptitude search ~c mysql c libmysqlclient15off - MySQL database client library c mysql-server-5.0 - MySQL database server binaries c mysql-server-5.1 - MySQL database server binaries and system database fermi:~# aptitude show mysql-server-core-5.1 Package: mysql-server-core-5.1 New: yes State: installed Automatically installed: yes Version: 5.1.48-1 Priority: optional Section: misc Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org Uncompressed Size: 9,916k Architecture: i386 Compressed Size: 3,932k Filename: pool/main/m/mysql-5.1/mysql-server-core-5.1_5.1.48-1_i386.deb MD5sum: 6a31c01d3ce2fc10ec0d520048d2a39f Archive: testing Depends: libc6 (= 2.7), libgcc1 (= 1:4.1.1), libstdc++6 (= 4.1.1), libwrap0 (= 7.6-4~), zlib1g (= 1:1.1.4) Conflicts: mysql-server-5.0 ( 5.1.45-2), mysql-server-5.1 ( 5.1.45-2) Provides: mysql-server-core, mysql-server-core-5.0 Description: MySQL database server binaries MySQL is a fast, stable and true multi-user, multi-threaded SQL database server. SQL (Structured Query Language) is the most popular database query language in the world. The main goals of MySQL are speed, robustness and ease of use. This package includes the server binaries but doesn't contain all the infrastructure needed to setup system databases. Homepage: http://dev.mysql.com/ Package: mysql-server-core-5.1 New: yes State: installed Automatically installed: yes Version: 5.1.48-1 Priority: optional Section: misc Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org Uncompressed Size: 9,916k Architecture: i386 Compressed Size: 3,932k Filename: pool/main/m/mysql-5.1/mysql-server-core-5.1_5.1.48-1_i386.deb MD5sum: 6a31c01d3ce2fc10ec0d520048d2a39f Archive: unstable Depends: libc6 (= 2.7), libgcc1 (= 1:4.1.1), libstdc++6 (= 4.1.1), libwrap0 (= 7.6-4~), zlib1g (= 1:1.1.4) Conflicts: mysql-server-5.0 ( 5.1.45-2), mysql-server-5.1 ( 5.1.45-2) Provides: mysql-server-core, mysql-server-core-5.0 Description: MySQL database server binaries MySQL is a fast, stable and true multi-user, multi-threaded SQL database server. SQL (Structured Query Language) is the most popular database query language in the world. The main goals of MySQL are speed, robustness and ease of use. This package includes the server binaries but doesn't contain all the infrastructure needed to setup system databases. Homepage: http://dev.mysql.com/ Package: mysql-server-core-5.1 New: yes State: installed Automatically installed: yes Version: 5.1.48-1 Priority: optional Section: misc Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org Uncompressed Size: 9,916k Architecture: i386 Compressed Size: 3,932k Filename: MD5sum: Archive: now Depends: libc6 (= 2.7), libgcc1 (= 1:4.1.1), libstdc++6 (= 4.1.1), libwrap0 (= 7.6-4~), zlib1g (= 1:1.1.4) Conflicts: mysql-server-5.0 ( 5.1.45-2), mysql-server-5.1 ( 5.1.45-2) Provides: mysql-server-core, mysql-server-core-5.0 Description: MySQL database server binaries MySQL is a fast, stable and true multi-user, multi-threaded SQL database server. SQL (Structured Query Language) is the most popular database query language in the world. The main goals of MySQL are speed, robustness and ease of use. This package includes the server binaries but doesn't contain all the infrastructure needed to setup system databases. Homepage: http://dev.mysql.com/ fermi:~# aptitude show mysql-common Package: mysql-common State: installed Automatically installed: yes Version: 5.1.48-1 Priority: optional Section: database Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org Uncompressed Size: 168k Architecture: all Compressed Size: 72.0k Filename: pool/main/m/mysql-5.1/mysql-common_5.1.48-1_all.deb MD5sum: ac2394361ccd68cf919f3248f6dfbfeb Archive: testing Conflicts: mysql-common-4.1 Replaces: mysql-common-4.1 Provides: mysql-common-4.1 Description: MySQL database common files, e.g.
Bug#589344: i386 and amd64 architectures
This problem is present also on amd64, not only on i386: $ ldd -r /usr/lib/libntrack.so.0 undefined symbol: _ntrack_arch_new (/usr/lib/libntrack.so.0) undefined symbol: _ntrack_arch_get_rfds (/usr/lib/libntrack.so.0) undefined symbol: _ntrack_arch_process_data (/usr/lib/libntrack.so.0) linux-vdso.so.1 = (0x7fff763ff000) libc.so.6 = /lib/libc.so.6 (0x7fa541527000) /lib64/ld-linux-x86-64.so.2 (0x7fa541aad000) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588550: [buildd-tools-devel] Bug#588550: sbuild: Fails to build binNMUs for packages with urgency comments in changelogs
On Sun, Jul 18, 2010 at 01:04:18PM +0100, Roger Leigh wrote: On Fri, Jul 16, 2010 at 08:41:52PM +0200, Michael Banck wrote: tags 588550 +patch thanks On Fri, Jul 09, 2010 at 04:20:42PM +0100, Adam D. Barratt wrote: The recently scheduled binNMUs of the mandos package failed due to a problem with the auto-generated binNMU changelog; from one of the logs: parsechangelog/debian: warning: debian/changelog(l1): unrecognised line LINE: (1.0.14-1+b1) unstable; urgency=low parsechangelog/debian: error: Can't call method as_string on an undefined value at /usr/share/perl5/Dpkg/Changelog.pm line 250, STDIN line 8. This appears to be due to line 830 of lib/Sbuild/Build.pm which does: $firstline =~ /^(\S+)\s+\((\S+)\)\s+([^;]+)\s*;\s*urgency=(\S+)\s*$/; The most recent header line from the mandos changelog is: mandos (1.0.14-1) unstable; urgency=low (HIGH on mips and mipsel) Although unusual, this form is permitted by section 5.6.17 of Policy. I propose the attached patch, which ignores the rest of the line after the urgency field; I can successfully binNMU mandos_1.0.14-1 with it. I will probably upload the fix by the rest of weekend, if I don't hear complaints. That sounds fine to me. Please do a binNMU rather than using git master, which currently has some issues. Feel free to commit this fix onto git master and buildd branches, though! I assume you mean NMU. A binNMU wouldn't change the source. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589516: libcompass-ruby1.8 and libcompass-ruby: error when trying to install together
Package: libcompass-ruby,libcompass-ruby1.8 Version: libcompass-ruby/0.10.2debian-1 Version: libcompass-ruby1.8/0.10.2debian-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2010-07-18 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libruby1.8 ruby1.8 libhaml-ruby1.8 libffi5 libffi-ruby1.8 libinotify-ruby1.8 librb-inotify-ruby1.8 libfssm-ruby1.8 libcompass-ruby1.8 libhaml-ruby libfssm-ruby libcompass-ruby Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libruby1.8. (Reading database ... 12231 files and directories currently installed.) Unpacking libruby1.8 (from .../libruby1.8_1.8.7.299-1_amd64.deb) ... Selecting previously deselected package ruby1.8. Unpacking ruby1.8 (from .../ruby1.8_1.8.7.299-1_amd64.deb) ... Selecting previously deselected package libhaml-ruby1.8. Unpacking libhaml-ruby1.8 (from .../libhaml-ruby1.8_3.0.9-1_all.deb) ... Selecting previously deselected package libffi5. Unpacking libffi5 (from .../libffi5_3.0.9-2_amd64.deb) ... Selecting previously deselected package libffi-ruby1.8. Unpacking libffi-ruby1.8 (from .../libffi-ruby1.8_0.6.3debian-1_amd64.deb) ... Selecting previously deselected package libinotify-ruby1.8. Unpacking libinotify-ruby1.8 (from .../libinotify-ruby1.8_0.0.2-4_amd64.deb) ... Selecting previously deselected package librb-inotify-ruby1.8. Unpacking librb-inotify-ruby1.8 (from .../librb-inotify-ruby1.8_0.7.0-4_all.deb) ... Selecting previously deselected package libfssm-ruby1.8. Unpacking libfssm-ruby1.8 (from .../libfssm-ruby1.8_0.1.4-2_all.deb) ... Selecting previously deselected package libcompass-ruby1.8. Unpacking libcompass-ruby1.8 (from .../libcompass-ruby1.8_0.10.2debian-1_all.deb) ... Selecting previously deselected package libhaml-ruby. Unpacking libhaml-ruby (from .../libhaml-ruby_3.0.9-1_all.deb) ... Selecting previously deselected package libfssm-ruby. Unpacking libfssm-ruby (from .../libfssm-ruby_0.1.4-2_all.deb) ... Selecting previously deselected package libcompass-ruby. Unpacking libcompass-ruby (from .../libcompass-ruby_0.10.2debian-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/libcompass-ruby_0.10.2debian-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/compass.1.gz', which is also in package libcompass-ruby1.8 0:0.10.2debian-1 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libcompass-ruby_0.10.2debian-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) cow-shell unlink .ilist: No such file or directory This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/share/man/man1/compass.1.gz This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589344: working on it
working on it I am working to solve this bug. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589518: [python] error of python during apt-get dist-upgrade
Package: python
Version: 2.6.5-5
Severity: critical
--- Please enter the report below this line. ---
During the apt-get dist-upgrade process I got (sorry it in in Italian)
Elaborazione dei trigger per menu...
Elaborazione dei trigger per python-support...
Compiling /usr/lib/pymodules/python2.4/MythTV/ttvdb/cache.py ...
SyntaxError: ('future feature with_statement is not defined',)
Date:dom lug 18 Time:13:35:35
User:root Computer:europa Base:~ Current:
and the apt-get stops (perhaps leaving not configured something). The
next apt-get dist-upgrade sid me that there is nothing to update.
Thanks
Marco
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.32-5-686-bigmem
Debian Release: squeeze/sid
500 testing-proposed-updates ftp.fr.debian.org
500 testing www.debian-multimedia.org
500 testing security.debian.org
500 testing http.us.debian.org
500 testing ftp.fr.debian.org
--- Package information. ---
Depends (Version) | Installed
=-+-===
python2.6 (= 2.6.5+20100616-1~) | 2.6.5+20100706-1
python-minimal (= 2.6.5-5) | 2.6.5-5
Package's Recommends field is empty.
Suggests (Version) | Installed
-+-=
python-doc (= 2.6.5-5) |
python-tk (= 2.6.5-5) | 2.6.5-1
python-profiler (= 2.6.5-5) |
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576445: NMU interdiff (was: Re: [patch]: sgml-base: Fails to purge)
Hi, attached is the NMU interdiff; I had to also move debhelper from Build-Depends-Indep to Build-Depends to fix a lintian error. diff -Nru sgml-base-1.26/debian/changelog sgml-base-1.26+nmu1/debian/changelog --- sgml-base-1.26/debian/changelog 2004-08-14 17:04:15.0 +0200 +++ sgml-base-1.26+nmu1/debian/changelog2010-07-18 14:39:38.0 +0200 @@ -1,3 +1,14 @@ +sgml-base (1.26+nmu1) unstable; urgency=low + + * Non-maintainer upload + * Applied patch from Hideki Yamane adding a check whether directories exist +before removing them on purge +(closes: Bug#576445) + * Moved debhelper from Build-Depends-Indep to Build-Depends as it is used in +the clean target, as per Policy section 7.7. + + -- Michael Banck mba...@debian.org Sat, 17 Jul 2010 16:27:02 +0200 + sgml-base (1.26) unstable; urgency=low * Removed creation of the transitional catalog in a installation diff -Nru sgml-base-1.26/debian/control sgml-base-1.26+nmu1/debian/control --- sgml-base-1.26/debian/control 2004-06-07 05:18:28.0 +0200 +++ sgml-base-1.26+nmu1/debian/control 2010-07-18 14:37:50.0 +0200 @@ -4,7 +4,7 @@ Maintainer: Debian XML/SGML Group debian-xml-sgml-p...@lists.alioth.debian.org Uploaders: Ardo van Rangelrooij a...@debian.org Standards-Version: 3.6.1 -Build-Depends-Indep: debhelper (= 4.1) +Build-Depends: debhelper (= 4.1) Package: sgml-base Section: text diff -Nru sgml-base-1.26/debian/sgml-base.postrm sgml-base-1.26+nmu1/debian/sgml-base.postrm --- sgml-base-1.26/debian/sgml-base.postrm 2004-08-14 17:04:15.0 +0200 +++ sgml-base-1.26+nmu1/debian/sgml-base.postrm 2010-07-17 16:15:59.0 +0200 @@ -15,16 +15,12 @@ rm -f /etc/sgml/catalog /etc/sgml/catalog.old ## -- -## remove /etc/sgml -cd /etc -rmdir --ignore-fail-on-non-empty sgml -cd - /dev/null - -## -- -## remove /var/lib/sgml-base -cd /var/lib -rmdir --ignore-fail-on-non-empty sgml-base -cd - /dev/null +## remove /etc/sgml and /var/lib/sgml-base +for dir in /etc/sgml /var/lib/sgml-base; do + if [ -d $dir ]; then + rmdir --ignore-fail-on-non-empty $dir + fi +done fi
Bug#576445: marked as done (sgml-base: Fails to purge)
Your message dated Sun, 18 Jul 2010 12:47:49 + with message-id e1oathz-0007pz...@franck.debian.org and subject line Bug#576445: fixed in sgml-base 1.26+nmu1 has caused the Debian Bug report #576445, regarding sgml-base: Fails to purge 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.) -- 576445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sgml-base Version: 1.26 Severity: serious Hi, I got this in a build log: Selecting previously deselected package sgml-base. Unpacking sgml-base (from .../sgml-base_1.26_all.deb) ... [...] Unpacking libao2 (from .../libao2_0.8.8-5.1_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libao2_0.8.8-5.1_i386.deb (--unpack): trying to overwrite '/etc/libao.conf', which is also in package libao4 0:1.0.0-2 [...] Errors were encountered while processing: /var/cache/apt/archives/libao2_0.8.8-5.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) apt-get failed. (It didn't configure any package.) And then during removal I get: Removing sgml-base ... Purging configuration files for sgml-base ... rmdir: failed to remove `sgml': No such file or directory dpkg: error processing sgml-base (--purge): subprocess installed post-removal script returned error exit status 1 Kurt ---End Message--- ---BeginMessage--- Source: sgml-base Source-Version: 1.26+nmu1 We believe that the bug you reported is fixed in the latest version of sgml-base, which is due to be installed in the Debian FTP archive: sgml-base_1.26+nmu1.dsc to main/s/sgml-base/sgml-base_1.26+nmu1.dsc sgml-base_1.26+nmu1.tar.gz to main/s/sgml-base/sgml-base_1.26+nmu1.tar.gz sgml-base_1.26+nmu1_all.deb to main/s/sgml-base/sgml-base_1.26+nmu1_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 576...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Banck mba...@debian.org (supplier of updated sgml-base 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: Sat, 17 Jul 2010 16:27:02 +0200 Source: sgml-base Binary: sgml-base Architecture: source all Version: 1.26+nmu1 Distribution: unstable Urgency: low Maintainer: Debian XML/SGML Group debian-xml-sgml-p...@lists.alioth.debian.org Changed-By: Michael Banck mba...@debian.org Description: sgml-base - SGML infrastructure and SGML catalog file support Closes: 576445 Changes: sgml-base (1.26+nmu1) unstable; urgency=low . * Non-maintainer upload * Applied patch from Hideki Yamane adding a check whether directories exist before removing them on purge (closes: Bug#576445) * Moved debhelper from Build-Depends-Indep to Build-Depends as it is used in the clean target, as per Policy section 7.7. Checksums-Sha1: 2efe84fde50b02a0ade32dfd52b6260e27e97482 803 sgml-base_1.26+nmu1.dsc a77cca2a1be3dcb41f366139b99ea7605affbd40 10304 sgml-base_1.26+nmu1.tar.gz 2a5064c1b906d0e543423f2b2ff4703a37e40d0b 11904 sgml-base_1.26+nmu1_all.deb Checksums-Sha256: 9ba12ffe031e5a8b9cd2c14d98df875945e180f7914b1f4f10793d77163832d0 803 sgml-base_1.26+nmu1.dsc dd3d59bfac43a6ab56690ef177969468529d1f2214bbe774ab5fb3cdc227ddd9 10304 sgml-base_1.26+nmu1.tar.gz b03ca8a48a9b2e8e422848c547addc84bcd00c66a3d89ec42b26c97b949d031e 11904 sgml-base_1.26+nmu1_all.deb Files: 20c5880fbbe8f04570e66c13862a6821 803 text optional sgml-base_1.26+nmu1.dsc 287d828b0fe71276c6aeb7d68ea5b467 10304 text optional sgml-base_1.26+nmu1.tar.gz 10e91c863e586daa391307123e95b41a 11904 text optional sgml-base_1.26+nmu1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMQvc0mHaJYZ7RAb8RA+ffAJ9xuR4WhfuGLMHOXUaibUykyqhEkACfZbUa QBi1bc06YtPLN3yGuUrywAI= =qtdG -END PGP SIGNATURE- ---End Message---
Bug#588586: marked as done (python-mock: doesn't depend on python)
Your message dated Sun, 18 Jul 2010 12:47:37 +
with message-id e1oathn-0007nj...@franck.debian.org
and subject line Bug#588586: fixed in python-mock 0.6.0-1.1
has caused the Debian Bug report #588586,
regarding python-mock: doesn't depend on python
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.)
--
588586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588586
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-mock
Version: 0.6.0-1
Severity: serious
Tags: patch
Justification: Debian Policy 3.5, Python Policy 2.4
Hello,
python-mock does not depend on python as it should. The attached patch
fixes this bug.
--
Jakub Wilk
diff -u python-mock-0.6.0/debian/control python-mock-0.6.0/debian/control
--- python-mock-0.6.0/debian/control
+++ python-mock-0.6.0/debian/control
@@ -9,7 +9,7 @@
Package: python-mock
Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
Recommends: libjs-jquery
Provides: ${python:Provides}
Description: Mocking and Testing Library
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: python-mock
Source-Version: 0.6.0-1.1
We believe that the bug you reported is fixed in the latest version of
python-mock, which is due to be installed in the Debian FTP archive:
python-mock_0.6.0-1.1.diff.gz
to main/p/python-mock/python-mock_0.6.0-1.1.diff.gz
python-mock_0.6.0-1.1.dsc
to main/p/python-mock/python-mock_0.6.0-1.1.dsc
python-mock_0.6.0-1.1_all.deb
to main/p/python-mock/python-mock_0.6.0-1.1_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 588...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Marek Kubica ma...@xivilization.net (supplier of updated python-mock 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: Sat, 17 Jul 2010 12:27:08 +0200
Source: python-mock
Binary: python-mock
Architecture: source all
Version: 0.6.0-1.1
Distribution: unstable
Urgency: low
Maintainer: David Watson da...@kutoken.com
Changed-By: Marek Kubica ma...@xivilization.net
Description:
python-mock - Mocking and Testing Library
Closes: 588586
Changes:
python-mock (0.6.0-1.1) unstable; urgency=low
.
* Non-maintainer upload.
* Fix doesn't depend on python by applying patch to debian/control
by Jakub Wilk (Closes: #588586)
Checksums-Sha1:
0bf551b76fe2d09cd8ad771333752f8cfa855f6f 1136 python-mock_0.6.0-1.1.dsc
5fe6016f4a09145524d2653e1c0b22636e2a02fa 2475 python-mock_0.6.0-1.1.diff.gz
c1b5d6379cfddd68b037ebc139c22270b962db4d 59282 python-mock_0.6.0-1.1_all.deb
Checksums-Sha256:
4176208d44439f22e97eec0cfb7b98638f0920655c071b5f21ef34e94fa865c0 1136
python-mock_0.6.0-1.1.dsc
048b5f98f48b1953a21cba190911adb472b65639b6ffaeed1f117ccea6464049 2475
python-mock_0.6.0-1.1.diff.gz
56a3f5433bf129916b90725851b2aa3aaee24781f1f5e24478b6afdfcc188374 59282
python-mock_0.6.0-1.1_all.deb
Files:
d30bd14a49ebefeef20b70c7e2c60b56 1136 python extra python-mock_0.6.0-1.1.dsc
004efeced5d9c9a87608e37394449971 2475 python extra
python-mock_0.6.0-1.1.diff.gz
ebe922db1095e04252d21781bed6de0a 59282 python extra
python-mock_0.6.0-1.1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFMQvPpmHaJYZ7RAb8RAyRtAKDDbFQjXgjd2Ylfv+StYtkiHhLWVgCfQtK8
PJGFym1GRtmSt/DUMS463E8=
=y+Wu
-END PGP SIGNATURE-
---End Message---
Bug#588550: [buildd-tools-devel] Bug#588550: sbuild: Fails to build binNMUs for packages with urgency comments in changelogs
Hi,
On Sun, Jul 18, 2010 at 02:14:36PM +0200, Kurt Roeckx wrote:
On Sun, Jul 18, 2010 at 01:04:18PM +0100, Roger Leigh wrote:
On Fri, Jul 16, 2010 at 08:41:52PM +0200, Michael Banck wrote:
tags 588550 +patch
thanks
On Fri, Jul 09, 2010 at 04:20:42PM +0100, Adam D. Barratt wrote:
The recently scheduled binNMUs of the mandos package failed due to a
problem with the auto-generated binNMU changelog; from one of the logs:
parsechangelog/debian: warning: debian/changelog(l1): unrecognised
line
LINE: (1.0.14-1+b1) unstable; urgency=low
parsechangelog/debian: error: Can't call method as_string on an
undefined value at /usr/share/perl5/Dpkg/Changelog.pm line 250, STDIN
line 8.
This appears to be due to line 830 of lib/Sbuild/Build.pm which does:
$firstline =~ /^(\S+)\s+\((\S+)\)\s+([^;]+)\s*;\s*urgency=(\S+)\s*$/;
The most recent header line from the mandos changelog is:
mandos (1.0.14-1) unstable; urgency=low (HIGH on mips and mipsel)
Although unusual, this form is permitted by section 5.6.17 of Policy.
I propose the attached patch, which ignores the rest of the line after
the urgency field; I can successfully binNMU mandos_1.0.14-1 with it. I
will probably upload the fix by the rest of weekend, if I don't hear
complaints.
That sounds fine to me. Please do a binNMU rather than using git
master, which currently has some issues. Feel free to commit this
fix onto git master and buildd branches, though!
I assume you mean NMU. A binNMU wouldn't change the source.
I've uploaded it now, the interdiff is attached.
Michael
only in patch2:
unchanged:
--- sbuild-0.60.0.orig/debian/changelog
+++ sbuild-0.60.0/debian/changelog
@@ -1,3 +1,11 @@
+sbuild (0.60.0-2) unstable; urgency=low
+
+ * sbuild:
+- disregard text after urgency field in the changelog, as further comments
+ are allowed by policy (Closes: #588550).
+
+ -- Michael Banck mba...@debian.org Sun, 18 Jul 2010 14:48:43 +0200
+
sbuild (0.60.0-1) unstable; urgency=low
* debian/control:
only in patch2:
unchanged:
--- sbuild-0.60.0.orig/lib/Sbuild/Build.pm
+++ sbuild-0.60.0/lib/Sbuild/Build.pm
@@ -827,7 +827,7 @@
$firstline = F while $firstline =~ /^$/;
{ local($/); undef $/; $text = F; }
close( F );
- $firstline =~
/^(\S+)\s+\((\S+)\)\s+([^;]+)\s*;\s*urgency=(\S+)\s*$/;
+ $firstline =~ /^(\S+)\s+\((\S+)\)\s+([^;]+)\s*;\s*urgency=(\S+).*$/;
my ($name, $version, $dists, $urgent) = ($1, $2, $3, $4);
my $NMUversion = $self-get('Version');
chomp( my $date = `date -R` );
Bug#554081: marked as done (need newer libgc version)
Your message dated Sun, 18 Jul 2010 13:02:13 + with message-id e1oatvv-bw...@franck.debian.org and subject line Bug#554081: fixed in ecl 10.3.1-3 has caused the Debian Bug report #554081, regarding need newer libgc version 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.) -- 554081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ecl Version: 9.10.2-1 Severity: serious This looks like a code copy of libatomic-ops, please elaborate. There was an error while trying to autobuild your package: sbuild (Debian sbuild) 0.58.2 (31 Jul 2009) on debian-31.osdl.marist.edu [...] s390-linux-gnu-gcc -fPIC -DPACKAGE_NAME=\gc\ -DPACKAGE_TARNAME=\gc\ -DPACKAGE_VERSION=\7.1\ -DPACKAGE_STRING=\gc 7.1\ -DPACKAGE_BUGREPORT=\hans.bo...@hp.com\ -DGC_VERSION_MAJOR=7 -DGC_VERSION_MINOR=1 -DPACKAGE=\gc\ -DVERSION=\7.1\ -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DGC_GCJ_SUPPORT=1 -DJAVA_FINALIZATION=1 -DATOMIC_UNCOLLECTABLE=1 -DLARGE_CONFIG=1 -I/build/buildd-ecl_9.10.2-1-s390-Gve93J/ecl-9.10.2/src/gc/include -fexceptions -I libatomic_ops/src -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fPIC -D_THREAD_SAFE -MT allchblk.lo -MD -MP -MF .deps/allchblk.Tpo -c /build/buildd-ecl_9.10.2-1-s390-Gve93J/ecl-9.10.2/src/gc/allchblk.c -o allchblk.o In file included from libatomic_ops/src/atomic_ops.h:212, from /build/buildd-ecl_9.10.2-1-s390-Gve93J/ecl-9.10.2/src/gc/include/private/gc_locks.h:30, from /build/buildd-ecl_9.10.2-1-s390-Gve93J/ecl-9.10.2/src/gc/include/private/gc_priv.h:85, from /build/buildd-ecl_9.10.2-1-s390-Gve93J/ecl-9.10.2/src/gc/allchblk.c:19: libatomic_ops/src/atomic_ops/sysdeps/gcc/s390.h:33:31: error: ordered_except_wr.h: No such file or directory libatomic_ops/src/atomic_ops/sysdeps/gcc/s390.h:34:43: error: all_aligned_atomic_load_store.h: No such file or directory make[4]: *** [allchblk.lo] Error 1 make[4]: Leaving directory `/build/buildd-ecl_9.10.2-1-s390-Gve93J/ecl-9.10.2/build/gc' make[3]: *** [install-recursive] Error 1 make[3]: Leaving directory `/build/buildd-ecl_9.10.2-1-s390-Gve93J/ecl-9.10.2/build/gc' make[2]: *** [libeclgc.a] Error 2 make[2]: Leaving directory `/build/buildd-ecl_9.10.2-1-s390-Gve93J/ecl-9.10.2/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd-ecl_9.10.2-1-s390-Gve93J/ecl-9.10.2' make: *** [build-arch-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Build finished at 20091016-0140 FAILED [dpkg-buildpackage died] ---End Message--- ---BeginMessage--- Source: ecl Source-Version: 10.3.1-3 We believe that the bug you reported is fixed in the latest version of ecl, which is due to be installed in the Debian FTP archive: ecl-doc_10.3.1-3_all.deb to main/e/ecl/ecl-doc_10.3.1-3_all.deb ecl_10.3.1-3.diff.gz to main/e/ecl/ecl_10.3.1-3.diff.gz ecl_10.3.1-3.dsc to main/e/ecl/ecl_10.3.1-3.dsc ecl_10.3.1-3_i386.deb to main/e/ecl/ecl_10.3.1-3_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 554...@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 ecl 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: Sun, 18 Jul 2010 12:46:53 +0200 Source: ecl Binary: ecl ecl-doc Architecture: source all i386 Version: 10.3.1-3 Distribution: experimental Urgency: low Maintainer: Debian Common Lisp Team pkg-common-lisp-de...@lists.alioth.debian.org Changed-By: Christoph Egger christ...@debian.org Description: ecl- Embeddable Common-Lisp: has an interpreter and can compile to C ecl-doc- documentation for Embeddable Common-Lisp Closes: 554081 Changes: ecl (10.3.1-3) experimental; urgency=low . * Version for experimental
Bug#573814: marked as done (ecl: Please support Renesas SH(sh4))
Your message dated Sun, 18 Jul 2010 13:02:13 +
with message-id e1oatvv-bw...@franck.debian.org
and subject line Bug#554081: fixed in ecl 10.3.1-3
has caused the Debian Bug report #554081,
regarding ecl: Please support Renesas SH(sh4)
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.)
--
554081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: ecl
Version: 10.2.1-1
Severity: important
Tags: patch
User: debian-...@superh.org
Usertags: sh4
X-Debbugs-CC: debian-sup...@lists.debian.org
Hi,
I am now trying to run Debian on Renesas SH(sh4) CPU.
http://buildd.debian-ports.org/status/architecture.php?suite=unstablea=sh4
ecl FTBFS on SH4.
Because xine-plugin does not support Renesas SH.
http://buildd.debian-ports.org/fetch.php?pkg=eclarch=sh4ver=10.2.1-1stamp=1267337068file=logas=raw
-
rm: invalid argument: `'
sh4-linux-gnu-gcc -fPIC -DPACKAGE_NAME=\gc\
-DPACKAGE_TARNAME=\gc\ -DPACKAGE_VERSION=\7.1\
-DPACKAGE_STRING=\gc 7.1\
-DPACKAGE_BUGREPORT=\hans.bo...@hp.com\ -DGC_VERSION_MAJOR=7
-DGC_VERSION_MINOR=1 -DPACKAGE=\gc\ -DVERSION=\7.1\
-DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1
-DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
-DHAVE_DLFCN_H=1 -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1
-DGC_GCJ_SUPPORT=1 -DJAVA_FINALIZATION=1 -DATOMIC_UNCOLLECTABLE=1
-DLARGE_CONFIG=1
-I/build/buildd-ecl_10.2.1-1-sh4-2jA9tI/ecl-10.2.1/src/gc/include
-fexceptions -I libatomic_ops/src -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
-g -O2 -fPIC -D_THREAD_SAFE -MT atomic_ops.lo -MD -MP -MF
.deps/atomic_ops.Tpo -c atomic_ops.c -o atomic_ops.o
atomic_ops.c:74: error: expected '=', ',', ';', 'asm' or
'__attribute__' before 'AO_locks'
atomic_ops.c:116: error: expected ';', ',' or ')' before '*' token
atomic_ops.c:124: error: expected ';', ',' or ')' before '*' token
atomic_ops.c:130: error: expected ';', ',' or ')' before '*' token
atomic_ops.c:139: error: expected '=', ',', ';', 'asm' or
'__attribute__' before 'init_lock'
atomic_ops.c: In function 'AO_compare_and_swap_emulation':
atomic_ops.c:144: error: 'AO_TS_t' undeclared (first use in this function)
atomic_ops.c:144: error: (Each undeclared identifier is reported only once
atomic_ops.c:144: error: for each function it appears in.)
atomic_ops.c:144: error: 'my_lock' undeclared (first use in this function)
atomic_ops.c:144: error: 'AO_locks' undeclared (first use in this function)
atomic_ops.c:150: error: 'init_lock' undeclared (first use in this function)
atomic_ops.c: In function 'AO_compare_double_and_swap_double_emulation':
atomic_ops.c:180: error: 'AO_TS_t' undeclared (first use in this function)
atomic_ops.c:180: error: 'my_lock' undeclared (first use in this function)
atomic_ops.c:180: error: 'AO_locks' undeclared (first use in this function)
atomic_ops.c:186: error: 'init_lock' undeclared (first use in this function)
atomic_ops.c: In function 'AO_store_full_emulation':
atomic_ops.c:215: error: 'AO_TS_t' undeclared (first use in this function)
atomic_ops.c:215: error: 'my_lock' undeclared (first use in this function)
atomic_ops.c:215: error: 'AO_locks' undeclared (first use in this function)
make[4]: *** [atomic_ops.lo] Error 1
make[3]: *** [install-recursive] Error 1
make[2]: *** [libeclgc.a] Error 2
make[1]: *** [all] Error 2
make: *** [build-arch-stamp] Error 2
-
I made patch to support SH. Could you apply this patch?
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--- ecl-10.2.1.orig/src/gc/libatomic_ops-1.2/src/atomic_ops.h
+++ ecl-10.2.1/src/gc/libatomic_ops-1.2/src/atomic_ops.h
@@ -229,6 +229,10 @@
# if defined(__cris__) || defined(CRIS)
# include atomic_ops/sysdeps/gcc/cris.h
# endif
+# if defined(__sh__) || defined(SH4)
+# include atomic_ops/sysdeps/gcc/sh.h
+# define AO_CAN_EMUL_CAS
+# endif /* __sh__ */
#endif /* __GNUC__ !AO_USE_PTHREAD_DEFS */
#if defined(__INTEL_COMPILER) !defined(AO_USE_PTHREAD_DEFS)
--- ecl-10.2.1.orig/src/gc/libatomic_ops-1.2/src/atomic_ops/sysdeps/Makefile.am
+++ ecl-10.2.1/src/gc/libatomic_ops-1.2/src/atomic_ops/sysdeps/Makefile.am
@@ -29,6 +29,7 @@
gcc/powerpc.h gcc/sparc.h \
gcc/hppa.h gcc/m68k.h gcc/s390.h \
gcc/ia64.h gcc/x86_64.h gcc/cris.h \
+ gcc/sh.h \
\
icc/ia64.h \
\
--- ecl-10.2.1.orig/src/gc/libatomic_ops-1.2/src/atomic_ops/sysdeps/gcc/sh.h
+++ ecl-10.2.1/src/gc/libatomic_ops-1.2/src/atomic_ops/sysdeps/gcc/sh.h
Bug#563411: marked as done (FTBFS [hppa] - error: invalid initializer)
Your message dated Sun, 18 Jul 2010 13:02:13 + with message-id e1oatvv-bw...@franck.debian.org and subject line Bug#554081: fixed in ecl 10.3.1-3 has caused the Debian Bug report #554081, regarding FTBFS [hppa] - error: invalid initializer 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.) -- 554081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ecl Version: 9.10.2-1 Severity: serious User: debian-h...@lists.debian.org Usertags: hppa ecl fails to build on hppa. The failure looks unique to hppa (other archs fail to build for apparently different reasons). From the most recent build attempt: [...] rm: invalid argument: `' hppa-linux-gnu-gcc -fPIC -DPACKAGE_NAME=\gc\ -DPACKAGE_TARNAME=\gc\ -DPACKAGE_VERSION=\7.1\ -DPACKAGE_STRING=\gc 7.1\ -DPACKAGE_BUGREPORT=\hans.bo...@hp.com\ -DGC_VERSION_MAJOR=7 -DGC_VERSION_MINOR=1 -DPACKAGE=\gc\ -DVERSION=\7.1\ -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DGC_GCJ_SUPPORT=1 -DJAVA_FINALIZATION=1 -DATOMIC_UNCOLLECTABLE=1 -DLARGE_CONFIG=1 -I/build/buildd/ecl-9.12.3/src/gc/include -fexceptions -I libatomic_ops/src -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fPIC -D_THREAD_SAFE -MT thread_local_alloc.lo -MD -MP -MF .deps/thread_local_alloc.Tpo -c /build/buildd/ecl-9.12.3/src/gc/thread_local_alloc.c -o thread_local_alloc.o depbase=`echo pthread_support.lo | sed 's|[^/]*$|.deps/|;s|\.lo$||'`; \ if /bin/sh ./libtool --tag=CC --mode=compile hppa-linux-gnu-gcc -fPIC -DPACKAGE_NAME=\gc\ -DPACKAGE_TARNAME=\gc\ -DPACKAGE_VERSION=\7.1\ -DPACKAGE_STRING=\gc\ 7.1\ -DPACKAGE_BUGREPORT=\hans.bo...@hp.com\ -DGC_VERSION_MAJOR=7 -DGC_VERSION_MINOR=1 -DPACKAGE=\gc\ -DVERSION=\7.1\ -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DGC_GCJ_SUPPORT=1 -DJAVA_FINALIZATION=1 -DATOMIC_UNCOLLECTABLE=1 -DLARGE_CONFIG=1 -I/build/buildd/ecl-9.12.3/src/gc/include -fexceptions -I libatomic_ops/src -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fPIC -D_THREAD_SAFE -MT pthread_support.lo -MD -MP -MF $depbase.Tpo -c -o pthread_support.lo /build/buildd/ecl-9.12.3/src/gc/pthread_support.c; \ then mv -f $depbase.Tpo $depbase.Plo; else rm -f $depbase.Tpo; exit 1; fi rm: invalid argument: `' hppa-linux-gnu-gcc -fPIC -DPACKAGE_NAME=\gc\ -DPACKAGE_TARNAME=\gc\ -DPACKAGE_VERSION=\7.1\ -DPACKAGE_STRING=\gc 7.1\ -DPACKAGE_BUGREPORT=\hans.bo...@hp.com\ -DGC_VERSION_MAJOR=7 -DGC_VERSION_MINOR=1 -DPACKAGE=\gc\ -DVERSION=\7.1\ -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DGC_GCJ_SUPPORT=1 -DJAVA_FINALIZATION=1 -DATOMIC_UNCOLLECTABLE=1 -DLARGE_CONFIG=1 -I/build/buildd/ecl-9.12.3/src/gc/include -fexceptions -I libatomic_ops/src -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fPIC -D_THREAD_SAFE -MT pthread_support.lo -MD -MP -MF .deps/pthread_support.Tpo -c /build/buildd/ecl-9.12.3/src/gc/pthread_support.c -o pthread_support.o /build/buildd/ecl-9.12.3/src/gc/pthread_support.c:1297: error: invalid initializer make[4]: *** [pthread_support.lo] Error 1 make[4]: Leaving directory `/build/buildd/ecl-9.12.3/build/gc' make[3]: *** [install-recursive] Error 1 make[3]: Leaving directory `/build/buildd/ecl-9.12.3/build/gc' make[2]: *** [libeclgc.a] Error 2 make[2]: Leaving directory `/build/buildd/ecl-9.12.3/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/ecl-9.12.3' make: *** [build-arch-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 ** Build finished at 20091231-1933 FAILED [dpkg-buildpackage died] -- /usr/bin/sudo dpkg --root=/home/buildd/build/chroot-unstable --purge m4 chrpath libgc-dev automake1.9 libgc1c2 libgmp3-dev dh-lisp autotools-dev
Bug#575261: marked as done (FTBFS [hppa] - error: invalid initializer)
Your message dated Sun, 18 Jul 2010 13:02:13 + with message-id e1oatvv-bw...@franck.debian.org and subject line Bug#554081: fixed in ecl 10.3.1-3 has caused the Debian Bug report #554081, regarding FTBFS [hppa] - error: invalid initializer 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.) -- 554081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ecl Version: 9.10.2-1 Severity: serious User: debian-h...@lists.debian.org Usertags: hppa ecl fails to build on hppa, starting with version 9.10.2-1. The tail of a recent build attempt follows. [...] hppa-linux-gnu-gcc -fPIC -DPACKAGE_NAME=\gc\ -DPACKAGE_TARNAME=\gc\ -DPACKAGE_VERSION=\7.1\ -DPACKAGE_STRING=\gc 7.1\ -DPACKAGE_BUGREPORT=\hans.bo...@hp.com\ -DGC_VERSION_MAJOR=7 -DGC_VERSION_MINOR=1 -DPACKAGE=\gc\ -DVERSION=\7.1\ -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DGC_GCJ_SUPPORT=1 -DJAVA_FINALIZATION=1 -DATOMIC_UNCOLLECTABLE=1 -DLARGE_CONFIG=1 -I/build/buildd-ecl_10.3.1-1-hppa-A1xbW6/ecl-10.3.1/src/gc/include -fexceptions -I libatomic_ops/src -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fPIC -D_THREAD_SAFE -MT thread_local_alloc.lo -MD -MP -MF .deps/thread_local_alloc.Tpo -c /build/buildd-ecl_10.3.1-1-hppa-A1xbW6/ecl-10.3.1/src/gc/thread_local_alloc.c -o thread_local_alloc.o depbase=`echo pthread_support.lo | sed 's|[^/]*$|.deps/|;s|\.lo$||'`; \ if /bin/bash ./libtool --tag=CC --mode=compile hppa-linux-gnu-gcc -fPIC -DPACKAGE_NAME=\gc\ -DPACKAGE_TARNAME=\gc\ -DPACKAGE_VERSION=\7.1\ -DPACKAGE_STRING=\gc\ 7.1\ -DPACKAGE_BUGREPORT=\hans.bo...@hp.com\ -DGC_VERSION_MAJOR=7 -DGC_VERSION_MINOR=1 -DPACKAGE=\gc\ -DVERSION=\7.1\ -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DGC_GCJ_SUPPORT=1 -DJAVA_FINALIZATION=1 -DATOMIC_UNCOLLECTABLE=1 -DLARGE_CONFIG=1 -I/build/buildd-ecl_10.3.1-1-hppa-A1xbW6/ecl-10.3.1/src/gc/include -fexceptions -I libatomic_ops/src -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fPIC -D_THREAD_SAFE -MT pthread_support.lo -MD -MP -MF $depbase.Tpo -c -o pthread_support.lo /build/buildd-ecl_10.3.1-1-hppa-A1xbW6/ecl-10.3.1/src/gc/pthread_support.c; \ then mv -f $depbase.Tpo $depbase.Plo; else rm -f $depbase.Tpo; exit 1; fi hppa-linux-gnu-gcc -fPIC -DPACKAGE_NAME=\gc\ -DPACKAGE_TARNAME=\gc\ -DPACKAGE_VERSION=\7.1\ -DPACKAGE_STRING=\gc 7.1\ -DPACKAGE_BUGREPORT=\hans.bo...@hp.com\ -DGC_VERSION_MAJOR=7 -DGC_VERSION_MINOR=1 -DPACKAGE=\gc\ -DVERSION=\7.1\ -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DGC_GCJ_SUPPORT=1 -DJAVA_FINALIZATION=1 -DATOMIC_UNCOLLECTABLE=1 -DLARGE_CONFIG=1 -I/build/buildd-ecl_10.3.1-1-hppa-A1xbW6/ecl-10.3.1/src/gc/include -fexceptions -I libatomic_ops/src -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fPIC -D_THREAD_SAFE -MT pthread_support.lo -MD -MP -MF .deps/pthread_support.Tpo -c /build/buildd-ecl_10.3.1-1-hppa-A1xbW6/ecl-10.3.1/src/gc/pthread_support.c -o pthread_support.o /build/buildd-ecl_10.3.1-1-hppa-A1xbW6/ecl-10.3.1/src/gc/pthread_support.c:1297: error: invalid initializer make[4]: *** [pthread_support.lo] Error 1 make[4]: Leaving directory `/build/buildd-ecl_10.3.1-1-hppa-A1xbW6/ecl-10.3.1/build/gc' make[3]: *** [install-recursive] Error 1 make[3]: Leaving directory `/build/buildd-ecl_10.3.1-1-hppa-A1xbW6/ecl-10.3.1/build/gc' make[2]: *** [libeclgc.a] Error 2 make[2]: Leaving directory `/build/buildd-ecl_10.3.1-1-hppa-A1xbW6/ecl-10.3.1/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd-ecl_10.3.1-1-hppa-A1xbW6/ecl-10.3.1' make: *** [build-arch-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 ---End Message--- ---BeginMessage--- Source: ecl Source-Version: 10.3.1-3 We believe that the bug you reported is fixed in the latest version of ecl, which is due to be installed in the
Bug#588550: marked as done (sbuild: Fails to build binNMUs for packages with urgency comments in changelogs)
Your message dated Sun, 18 Jul 2010 13:02:46 + with message-id e1oatw2-jq...@franck.debian.org and subject line Bug#588550: fixed in sbuild 0.60.0-2 has caused the Debian Bug report #588550, regarding sbuild: Fails to build binNMUs for packages with urgency comments in changelogs 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.) -- 588550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sbuild Version: 0.60.0-1 Severity: serious (Filed as serious as it prevents binNMUing packages which are policy compliant; I did argue with myself a little over the severity) Hi, The recently scheduled binNMUs of the mandos package failed due to a problem with the auto-generated binNMU changelog; from one of the logs: parsechangelog/debian: warning: debian/changelog(l1): unrecognised line LINE: (1.0.14-1+b1) unstable; urgency=low parsechangelog/debian: error: Can't call method as_string on an undefined value at /usr/share/perl5/Dpkg/Changelog.pm line 250, STDIN line 8. This appears to be due to line 830 of lib/Sbuild/Build.pm which does: $firstline =~ /^(\S+)\s+\((\S+)\)\s+([^;]+)\s*;\s*urgency=(\S+)\s*$/; The most recent header line from the mandos changelog is: mandos (1.0.14-1) unstable; urgency=low (HIGH on mips and mipsel) Although unusual, this form is permitted by section 5.6.17 of Policy. Regards, Adam ---End Message--- ---BeginMessage--- Source: sbuild Source-Version: 0.60.0-2 We believe that the bug you reported is fixed in the latest version of sbuild, which is due to be installed in the Debian FTP archive: buildd_0.60.0-2_all.deb to main/s/sbuild/buildd_0.60.0-2_all.deb libsbuild-perl_0.60.0-2_all.deb to main/s/sbuild/libsbuild-perl_0.60.0-2_all.deb sbuild_0.60.0-2.diff.gz to main/s/sbuild/sbuild_0.60.0-2.diff.gz sbuild_0.60.0-2.dsc to main/s/sbuild/sbuild_0.60.0-2.dsc sbuild_0.60.0-2_all.deb to main/s/sbuild/sbuild_0.60.0-2_all.deb wanna-build_0.60.0-2_all.deb to main/s/sbuild/wanna-build_0.60.0-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 588...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Banck mba...@debian.org (supplier of updated sbuild 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: Sun, 18 Jul 2010 14:48:43 +0200 Source: sbuild Binary: libsbuild-perl sbuild wanna-build buildd Architecture: source all Version: 0.60.0-2 Distribution: unstable Urgency: low Maintainer: Debian buildd-tools Developers buildd-tools-de...@lists.alioth.debian.org Changed-By: Michael Banck mba...@debian.org Description: buildd - Daemon for automatically building Debian binary packages from Deb libsbuild-perl - Tool for building Debian binary packages from Debian sources sbuild - Tool for building Debian binary packages from Debian sources wanna-build - Database to track building of Debian binary packages from Debian Closes: 588550 Changes: sbuild (0.60.0-2) unstable; urgency=low . * sbuild: - disregard text after urgency field in the changelog, as further comments are allowed by policy (Closes: #588550). Checksums-Sha1: cc082cf6533193efd7b9505e274fa95e24acb16b 1260 sbuild_0.60.0-2.dsc 95a3505493fc97c786ecdfcf7816c4a95fdf8774 498 sbuild_0.60.0-2.diff.gz a2b4d7492be29875ec12f599bdbd910d87dbd96b 207580 libsbuild-perl_0.60.0-2_all.deb 209dd832760d50fd263eb24c89c50e6f63837ddf 205384 sbuild_0.60.0-2_all.deb c950325cde7fedee6041ba089a3e5ec49d4dc91e 208156 wanna-build_0.60.0-2_all.deb 86120e40ca259b7e6522981d2ac5b3e185feb13e 197754 buildd_0.60.0-2_all.deb Checksums-Sha256: ea901a976c8d5830b27bf0758f7bf1298f1c51734fe712bea73fa97bb09f78b5 1260 sbuild_0.60.0-2.dsc c2b45c7468765d9ffd662d1f7f30fd7f7d4fd93bff40ae996e0610b07500d548 498 sbuild_0.60.0-2.diff.gz eee0c5878fbd5a6b0fc7db263f083938e8f3948f11e6c9cc50ffd49e2ebe436b 207580 libsbuild-perl_0.60.0-2_all.deb 25a7f509c19a97e6680dbb8ca095c5cf5ec88c3e29b93a2baf6f574ce34c9cf3 205384 sbuild_0.60.0-2_all.deb 9676b70553b1fbf72e1c0ff91b6e2c082d00a21f4994c77487e7ef085ca511a4 208156 wanna-build_0.60.0-2_all.deb 1ababf844804b8077bfcce6ed708993ba8f6f19dabbcc621a65938445b431413
Bug#588608: aptitude (priority important) depends on libboost-iostreams (priority optional)
On Sun, Jul 18, 2010 at 02:38:50AM +0200, Steve Langasek wrote: - When I type 'aptitude install foo', *removing* foo instead of upgrading is not a valid solution and should never be offered. It's still an outstanding (and irritating) bug as late as yesterday's sid... -- Jonathan Wiltshire 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Bug#549033: marked as done (pida: Uses deprecated libgtkhtml2)
Your message dated Sun, 18 Jul 2010 13:19:38 + with message-id e1oatmm-0001x3...@franck.debian.org and subject line Bug#549033: fixed in pida 0.5.1-5.2 has caused the Debian Bug report #549033, regarding pida: Uses deprecated libgtkhtml2 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.) -- 549033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pida Version: 0.5.1-5 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs libgtkhtml2 pida currently still uses libgtkhtml2, either directly or through the Python bindings. However, libgtkhtml2 is not really maintained upstream. After being in maintenance mode since 2005, it has not seen any new release for 2 years now. Iâd like to remove libgtkhtml2 packages before the squeeze release. This can only be done by getting rid of as much as possible of the reverse dependencies. For this to happen, the packages have to be migrated to another HTML rendering engine. There is gtkhtml3 of course, and now there is webkit, which is superior in terms of features and not too far from libgtkhtml2 in terms of API. I suggest that you migrate pida as soon as possible to use webkit for rendering. For most packages, which use libgtkhtml2 in a simple way, porting should be trivial - and even more so for those written in Python. As for bindings, they donât have any reverse dependencies except for the Python ones, so they should simply be removed ASAP, or drop libgtkhtml2 support. Thanks, -- .''`. Josselin Mouette : :' : `. `' âI recommend you to learn English in hope that you in `- future understand thingsâ -- Jörg Schilling ---End Message--- ---BeginMessage--- Source: pida Source-Version: 0.5.1-5.2 We believe that the bug you reported is fixed in the latest version of pida, which is due to be installed in the Debian FTP archive: pida_0.5.1-5.2.diff.gz to main/p/pida/pida_0.5.1-5.2.diff.gz pida_0.5.1-5.2.dsc to main/p/pida/pida_0.5.1-5.2.dsc pida_0.5.1-5.2_i386.deb to main/p/pida/pida_0.5.1-5.2_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 549...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marek Kubica ma...@xivilization.net (supplier of updated pida 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: Sat, 17 Jul 2010 15:47:56 +0200 Source: pida Binary: pida Architecture: source i386 Version: 0.5.1-5.2 Distribution: unstable Urgency: low Maintainer: Philipp Kaluza pk+d...@yomu.de Changed-By: Marek Kubica ma...@xivilization.net Description: pida - Python Integrated Development Application, a Python IDE Closes: 549033 Changes: pida (0.5.1-5.2) unstable; urgency=low . * Non-maintainer upload. * Fix Uses deprecated libgtkhtml2 by moving python-gtkhtml2 dependency into Suggests. (Closes: #549033) Checksums-Sha1: 9eb554e08fa68fa3d203faa431b475f8aac6208a 1288 pida_0.5.1-5.2.dsc e518bb2e5d0823d4c07494ec140e79e2ec404665 5733 pida_0.5.1-5.2.diff.gz 822f5a4785b64be78021f906e9e216c9b02d911f 464360 pida_0.5.1-5.2_i386.deb Checksums-Sha256: be4ed5a1f8ced9504892c7dc5542e4d06b88fc5d5b722aa989e72aaac7555734 1288 pida_0.5.1-5.2.dsc ab2922d1e61a6b9c51c6c8d9a23096b81147a8e134aa50998c22d94616e13593 5733 pida_0.5.1-5.2.diff.gz c8d8099b84f7afbe2a66e8456e65246fd87149897bde83fd78a921460d4dcf4f 464360 pida_0.5.1-5.2_i386.deb Files: 83793455aee3541733d7fc51a927ad3f 1288 devel optional pida_0.5.1-5.2.dsc 18d3fa58ffa43aed1d885d235b7e79bf 5733 devel optional pida_0.5.1-5.2.diff.gz 13b4a73ae7680343579077a3542e66ca 464360 devel optional pida_0.5.1-5.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMQvu3mHaJYZ7RAb8RA0KaAJ0SmpZLZCHh7uceBXTTRsObztibhwCeNdrS sENBTGzuJe8uRLhV2oFFoGc= =accU -END PGP SIGNATURE- ---End Message---
Bug#585966: marked as done (pdns-server: init.d script should provide the virtual facility $named)
Your message dated Sun, 18 Jul 2010 13:32:14 + with message-id e1oatyy-0003fj...@franck.debian.org and subject line Bug#585966: fixed in pdns 2.9.22-6 has caused the Debian Bug report #585966, regarding pdns-server: init.d script should provide the virtual facility $named 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.) -- 585966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pdns-server Version: 2.9.22-5 Severity: grave Tags: patch User: debian-...@lists.debian.org UserTags: debian-edu User: initscripts-ng-de...@lists.alioth.debian.org Usertags: incorrect-dependency The init.d script in the pdns-server package do not provide the virtual facility $named, causing all init.d scripts expecting the DNS server to be operational when they start during boot to fail. I discovered this with the Debian Edu main-server profile, were we include a lot of services on the same machine. Setting the severity to grave, as this causes other packages to fail to start properly at boot when used on a machine with pdns as the local DNS resolver. Providing a virtual facility is implemented by adding a file in /etc/insserv.conf.d/. Here is a patch to implement this for pdns-server. diff -uNr pdns-2.9.22/debian/pdns-server.insserv pdns-2.9.22-pere/debian/pdns-server.insserv --- pdns-2.9.22/debian/pdns-server.insserv 1970-01-01 01:00:00.0 +0100 +++ pdns-2.9.22-pere/debian/pdns-server.insserv 2010-06-15 10:55:49.858068000 +0200 @@ -0,0 +1 @@ +$named pdns diff -uNr pdns-2.9.22/debian/rules pdns-2.9.22-pere/debian/rules --- pdns-2.9.22/debian/rules2010-04-07 22:34:37.0 +0200 +++ pdns-2.9.22-pere/debian/rules 2010-06-15 10:57:14.054724000 +0200 @@ -87,6 +87,10 @@ # Install the stuff $(MAKE) install DESTDIR=$(CURDIR)/debian/tmp $(MAKE) -C pdns/docs html/index.html + # Set up init.d virtual facility + mkdir -p $(CURDIR)/debian/pdns-server/etc/insserv.conf.d + cp $(CURDIR)/debian/pdns-server.insserv \ + $(CURDIR)/debian/pdns-server/etc/insserv.conf.d/pdns-server dh_install Happy hacking, -- Petter Reinholdtsen ---End Message--- ---BeginMessage--- Source: pdns Source-Version: 2.9.22-6 We believe that the bug you reported is fixed in the latest version of pdns, which is due to be installed in the Debian FTP archive: pdns-backend-geo_2.9.22-6_amd64.deb to main/p/pdns/pdns-backend-geo_2.9.22-6_amd64.deb pdns-backend-ldap_2.9.22-6_amd64.deb to main/p/pdns/pdns-backend-ldap_2.9.22-6_amd64.deb pdns-backend-mysql_2.9.22-6_amd64.deb to main/p/pdns/pdns-backend-mysql_2.9.22-6_amd64.deb pdns-backend-pgsql_2.9.22-6_amd64.deb to main/p/pdns/pdns-backend-pgsql_2.9.22-6_amd64.deb pdns-backend-pipe_2.9.22-6_amd64.deb to main/p/pdns/pdns-backend-pipe_2.9.22-6_amd64.deb pdns-backend-sqlite3_2.9.22-6_amd64.deb to main/p/pdns/pdns-backend-sqlite3_2.9.22-6_amd64.deb pdns-backend-sqlite_2.9.22-6_amd64.deb to main/p/pdns/pdns-backend-sqlite_2.9.22-6_amd64.deb pdns-doc_2.9.22-6_all.deb to main/p/pdns/pdns-doc_2.9.22-6_all.deb pdns-server_2.9.22-6_amd64.deb to main/p/pdns/pdns-server_2.9.22-6_amd64.deb pdns_2.9.22-6.debian.tar.gz to main/p/pdns/pdns_2.9.22-6.debian.tar.gz pdns_2.9.22-6.dsc to main/p/pdns/pdns_2.9.22-6.dsc 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 585...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthijs Mohlmann matth...@cacholong.nl (supplier of updated pdns 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: Sun, 18 Jul 2010 14:48:27 +0200 Source: pdns Binary: pdns-server pdns-doc pdns-backend-pipe pdns-backend-ldap pdns-backend-geo pdns-backend-mysql pdns-backend-pgsql pdns-backend-sqlite pdns-backend-sqlite3 Architecture: source all amd64 Version: 2.9.22-6 Distribution: unstable Urgency: high Maintainer: Matthijs Mohlmann matth...@cacholong.nl Changed-By: Matthijs Mohlmann matth...@cacholong.nl Description: pdns-backend-geo - geo backend for PowerDNS pdns-backend-ldap - LDAP backend for PowerDNS pdns-backend-mysql - generic MySQL backend for PowerDNS
Processed: cloning 585890, reassign -1 to postgresql-9.0, reassign -2 to postgresql-common
Processing commands for cont...@bugs.debian.org: clone 585890 -1 -2 Bug#585890: fails to install due to incorrect dependencies in init.d LSB header Bug 585890 cloned as bugs 589523-589524. reassign -1 postgresql-9.0 9.0~beta3-1 Bug #589523 [postgresql] fails to install due to incorrect dependencies in init.d LSB header Bug reassigned from package 'postgresql' to 'postgresql-9.0'. Bug No longer marked as found in versions postgresql-8.4/8.4.4-1. Bug #589523 [postgresql-9.0] fails to install due to incorrect dependencies in init.d LSB header Bug Marked as found in versions postgresql-9.0/9.0~beta3-1. reassign -2 postgresql-common 108 Bug #589524 [postgresql] fails to install due to incorrect dependencies in init.d LSB header Bug reassigned from package 'postgresql' to 'postgresql-common'. Bug No longer marked as found in versions postgresql-8.4/8.4.4-1. Bug #589524 [postgresql-common] fails to install due to incorrect dependencies in init.d LSB header Bug Marked as found in versions postgresql-common/108. thanks Stopping processing here. Please contact me if you need assistance. -- 589524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589524 -2: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-2 585890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585890 589523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589523 -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#589344: bug fix
tags 589344 +patch diff -u ntrack-006/debian/changelog ntrack-006/debian/changelog --- ntrack-006/debian/changelog +++ ntrack-006/debian/changelog @@ -1,3 +1,10 @@ +ntrack (006-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Adding the libnl-dev package to Build-Depends (Closes: #589344) + + -- Davi d...@gnu.org Sun, 18 Jul 2010 14:24:06 +0100 + ntrack (006-1) unstable; urgency=low * Initial packaging for ntrack-006 (Closes: #570853) diff -u ntrack-006/debian/control ntrack-006/debian/control --- ntrack-006/debian/control +++ ntrack-006/debian/control @@ -5,7 +5,8 @@ Build-Depends: debhelper (=5), cdbs, quilt, libglib2.0-dev, python-gobject-dev, - libqt4-dev + libqt4-dev, + libnl-dev Standards-Version: 3.8.3 Package: libntrack0
Processed: bug fix
Processing commands for cont...@bugs.debian.org: tags 589344 +patch Bug #589344 [libntrack0] missing symbols in library Added tag(s) patch. End of message, stopping processing here. Please contact me if you need assistance. -- 589344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589344 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: Re: Bug#588523: smuxi-engine-twitter: lack of OAuth support
Processing commands for cont...@bugs.debian.org: severity 588523 important Bug #588523 [smuxi-engine-twitter] smuxi-engine-twitter: lack of OAuth support Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 588523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588523 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#589532: grub-rescue-pc: still does not depend on xorriso, although it should
Package: grub-rescue-pc Version: 1.98+20100710-1 Severity: grave Justification: renders package unusable Greetings, changelog for version 1.98+20100527-1 mentions: [cut] * Suggest xorriso (= 0.5.6.pl00) in grub-common, since grub-mkrescue now needs it. Depend on it in grub-rescue-pc. [cut] However, grub-rescue-pc still does not depend on xorriso (or the dependency was removed by mistake - I haven't reviewed every version since), and it is possible to install the former without the latter being automatically installed, with the result that grub-mkrescue exits with an error message: # grub-mkrescue -o 20100718a.iso Enabling BIOS support ... /usr/bin/grub-mkrescue: 323: xorriso: not found Of course, the iso image is not created. Best regards, Pier Luigi Pau -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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#586465: doesn't really fix xfce4-taskmanager on kbsd
Hi! Two things to note. First, the old taskmanager mostly worked on kbsd (probably using the /proc emulation present in kbsd. And secondly it doesn't build on the kfreebsd route, failing as below. Regards Christoph # source='app-manager.c' object='xfce4_taskmanager-app-manager.o' libtool=no gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\xfce4-taskmanager\ -DPACKAGE_LOCALE_DIR=\/usr/share/locale\ -DNDEBUG -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/libwnck-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/startup-notification-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gio-unix-2.0/ -g -O2 -g -Wall -O2 -c -o xfce4_taskmanager-app-manager.o `test -f 'app-manager.c' || echo './'`app-manager.c \ # source='task-manager-freebsd.c' object='xfce4_taskmanager-task-manager-freebsd.o' libtool=no gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\xfce4-taskmanager\ -DPACKAGE_LOCALE_DIR=\/usr/share/locale\ -DNDEBUG -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/libwnck-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/startup-notification-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gio-unix-2.0/ -g -O2 -g -Wall -O2 -c -o xfce4_taskmanager-task-manager-freebsd.o `test -f 'task-manager-freebsd.c' || echo './'`task-manager-freebsd.c task-manager-freebsd.c:11:17: error: kvm.h: No such file or directory task-manager-freebsd.c: In function ‘get_memory_usage’: task-manager-freebsd.c:49: error: ‘kvm_t’ undeclared (first use in this function) task-manager-freebsd.c:49: error: (Each undeclared identifier is reported only once task-manager-freebsd.c:49: error: for each function it appears in.) task-manager-freebsd.c:49: error: ‘kd’ undeclared (first use in this function) task-manager-freebsd.c:50: error: storage size of ‘kswap’ isn’t known task-manager-freebsd.c:52: warning: implicit declaration of function ‘kvm_openfiles’ task-manager-freebsd.c:55: warning: implicit declaration of function ‘kvm_getswapinfo’ task-manager-freebsd.c:59: warning: implicit declaration of function ‘kvm_close’ task-manager-freebsd.c:50: warning: unused variable ‘kswap’ task-manager-freebsd.c: At top level: task-manager-freebsd.c:102: error: expected ‘)’ before ‘*’ token task-manager-freebsd.c: In function ‘get_task_list’: task-manager-freebsd.c:197: error: ‘kvm_t’ undeclared (first use in this function) task-manager-freebsd.c:197: error: ‘kd’ undeclared (first use in this function) task-manager-freebsd.c:205: warning: implicit declaration of function ‘kvm_getprocs’ task-manager-freebsd.c:213: warning: implicit declaration of function ‘get_task_details’ task-manager-freebsd.c: In function ‘pid_is_sleeping’: task-manager-freebsd.c:225: error: ‘kvm_t’ undeclared (first use in this function) task-manager-freebsd.c:225: error: ‘kd’ undeclared (first use in this function) make[4]: *** [xfce4_taskmanager-task-manager-freebsd.o] Error 1 make[4]: Leaving directory `/home/christoph/xfce4-taskmanager-0.4.1/xfce4-taskmanager-1.0.0/src' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/christoph/xfce4-taskmanager-0.4.1/xfce4-taskmanager-1.0.0/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/christoph/xfce4-taskmanager-0.4.1/xfce4-taskmanager-1.0.0' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/christoph/xfce4-taskmanager-0.4.1/xfce4-taskmanager-1.0.0' make: *** [debian/stamp-makefile-build] Error 2 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582410: (Fwd) Bug#582410: libgtk2-perl: FTBFS on mips: Failed test 'callbacks encountered'
On Jul 17, 2010, at 10:28 AM, gregor herrmann wrote:
see below: libgtk2-perl has problems on the mips build daemon in
Debian. Maybe some of you guys has any idea what's going on there?
[snip]
On Thu, May 20, 2010 at 06:57:26PM +0300, Niko Tyni wrote:
Package: libgtk2-perl
Version: 1:1.221-6
Severity: serious
This package is not migrating to testing because it failed to build
on mips.
# Failed test 'callbacks encountered'
# at t/GtkCellRenderer.t line 228.
# Structures begin differing at:
# $got-[2] = 'size'
# $expected-[2] = 'render'
# Looks like you failed 1 test of 20.
t/GtkCellRenderer.t
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/20 subtests
This is reproducible on gabrielli.d.o.
It's something of a heisenbug: running with the perl debugger
('perl -d -Iblib/lib -Iblib/arch t/GtkCellRenderer.t') fails the first time,
but after a restart ('R') the tests pass.
The callback that doesn't get called is gtk2perl_cell_renderer_render(),
in xs/GtkCellRenderer.xs.
The class callbacks get initialized properly in
gtk2perl_cell_renderer_class_init(), but gtk+ never calls the renderer
one.
It would be somewhat interesting to eliminate xvfb from the loop, but
I can't seem to get an X11 connection to gabrielli.
Unfortunately I won't have the time to look further into this in the
next few weeks. Hope this note helps somebody else a bit.
There's 1.222 available upstream, but looking at the changes, I very
much doubt it fixes this.
This behavior implies that there are cases in which the cell renderer is never
being asked to draw itself. Since it works sometimes and not others, it seems
unlikely that this is a problem with the bindings, but instead some interesting
interaction between gtk+ and/or the display server.
The build log indicates that the code was built against gtk+ 2.20.x, which is
roughly in the right time frame to have offscreen rendering and some treeview
drawing speed fixes. Either of these might cause the cell renderers not to be
rendered. Is it possible to test this same binding code against an older or
newer gtk+?
The build log also shows the unit tests complaining that the display is missing
the RENDER extension, which means that the tests were running with a DISPLAY.
I presume it is to this that your xvfb comment refers.
If the DISPLAY variable is empty, the unit tests will skip the attempts to do
real drawing and such, and only test binding and marshaling code. This build
mode is intended for use by automated packaging systems, and may be the best
option.
--
Baseball is complicated. I think I'd rather stick with learning about
motorcycle engines.
-- Elysse, baffled by the rules of baseball
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589199: cannot install ardour on testing
reassing 589199 libaubio2 stop On Sat, Jul 17, 2010 at 17:11:38 (CEST), Adam D. Barratt wrote: On Thu, 2010-07-15 at 22:44 -0400, Reinhard Tartler wrote: On Thu, Jul 15, 2010 at 14:23:45 (EDT), Marco wrote: The following packages have unmet dependencies: ardour: Depends: jackd (= 0.103.0) but it is not going to be installed E: Broken packages please share the exact versions of the package and its dependencies you are trying to install. I'm especially curious to see your sources.list, potentially your /etc/apt/preferences (if non-empty/missing). is this stable? the dependency indicates that the package was built against a copy of libjack not in testing/unstable. The ardour packages in both testing and unstable depend on jackd (= 0.103.0). Although the exact versioning of the dependency isn't mentioned, I'd suspect this was added in 1:2.0~rc1-0ubuntu1, which was incorporated in to a package uploaded to Debian in April 2007. Yes, I'm sorry, this is definitely a problem in current Debian squeeze and sid. I am able to reproduce it: r...@debian:/tmp# apt-get install -s ardour Reading package lists... Done Building dependency tree Reading state information... Done 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: ardour: Depends: libaubio2 but it is not going to be installed Depends: libjack0 (= 0.118.0) but it is not going to be installed E: Broken packages However, this it *is* installable with jackd1: r...@debian:/tmp# apt-get install -s ardour jackd1 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: jackd1-firewire libaubio2 libgnomecanvasmm-2.6-1c2a libjack0 liblo7 liblrdf0 libvamp-hostsdk3 libvamp-sdk2 python-twisted python-twisted-lore python-twisted-mail python-twisted-names python-twisted-news python-twisted-runner python-twisted-words qjackctl Suggested packages: jamin jack-tools libjackasyn0 meterbridge liblo-dev liblrdf0-dev python-twisted-runner-dbg The following packages will be REMOVED: jackd2 jackd2-firewire libjack-jackd2-0 The following NEW packages will be installed: ardour jackd1 jackd1-firewire libaubio2 libgnomecanvasmm-2.6-1c2a libjack0 liblo7 liblrdf0 libvamp-hostsdk3 libvamp-sdk2 python-twisted python-twisted-lore python-twisted-mail python-twisted-names python-twisted-news python-twisted-runner python-twisted-words qjackctl 0 upgraded, 18 newly installed, 3 to remove and 0 not upgraded. just not with jackd2: r...@debian:/tmp# apt-get install -s ardour jackd2 Reading package lists... Done Building dependency tree Reading state information... Done jackd2 is already the newest version. 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: ardour: Depends: libaubio2 but it is not going to be installed Depends: libjack0 (= 0.118.0) but it is not going to be installed E: Broken packages In order to fix this bug, the package libaubio2 needs to be binNMUed. In this basis, I'm reassinging this bug to the package libaubio2 Adam, can you please schedule a binNMU? -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538133: Your mon / s-p-u upload
Hi Team,
On 06/19/2010 11:51 AM, Adam D. Barratt wrote:
Hi,
I've been reviewing the few remaining packages in s-p-u in preparation
for the upcoming point release and had a couple of comments / queries on
your mon upload.
- echo -n Starting $DESC:
- start-stop-daemon --start --quiet --pidfile $PIDFILE --chuid $USER
--group $GROUP --exec $DAEMON -- $DAEMON_OPTS
- echo $NAME.
+ if [ -f $PIDFILE ] ; then
+ echo $NAME daemon is already running.
+ else
+ echo -n Starting $DESC:
+ start-stop-daemon --start --oknodo --pidfile $PIDFILE --chuid
$USER --group $GROUP --exec $DAEMON -- $DAEMON_OPTS
+ echo $NAME.
+ fi
This looks like it should work, but would simply running the
start-stop-daemon --start --oknodo call in all cases not work, given
that it uses the pid file?
The restart section, on the other hand, is still not policy compliant:
restart)
-echo -n Restarting $DESC:
- start-stop-daemon --stop --quiet --pidfile $PIDFILE
- sleep 1
- start-stop-daemon --start --quiet --pidfile $PIDFILE --chuid $USER
--group $GROUP --exec $DAEMON -- $DAEMON_OPTS
- echo $NAME.
+ if [ -f $PIDFILE ] ; then
+ echo -n Restarting $DESC:
+ start-stop-daemon --stop --quiet --pidfile $PIDFILE
+ sleep 1
+ start-stop-daemon --start --quiet --pidfile $PIDFILE --chuid
$USER --group $GROUP --exec $DAEMON -- $DAEMON_OPTS
+ echo $NAME.
+ else
+ echo $NAME daemon is not running.
+ echo To start $NAME run: /etc/init.d/mon start
+ fi
Policy 9.3.2 says:
`restart'
stop and restart the service if it's already running, otherwise
start the service
which your updated script does not fulfil (specifically the otherwise
start the service section).
For future reference, it would be appreciated if you could send a mail
containing a debdiff and a brief explanation of the changes you'd like
to make to debian-rele...@lists.debian.org and wait for an ok, rather
than uploading directly to s-p-u; this allows us to review the patch and
makes it easier to incorporate any required changes.
Regards,
Adam
Sorry, that was my first s-p-u upload :(
As suggested, I'm sending this email to debian-release with the debdiff
attached.
The script seems to be Policy compliant now.
I keep on waiting for the OK to upload this new version.
Sorry for the inconvenience
Cheers
--
Dario Minnucci mid...@debian.org
Phone: +34 902021030 | Fax: +34 902024417
Key fingerprint = BAA1 7AAF B21D 6567 D457 D67D A82F BB83 F3D5 7033
diff -u mon-0.99.2/debian/mon.init.d mon-0.99.2/debian/mon.init.d
--- mon-0.99.2/debian/mon.init.d
+++ mon-0.99.2/debian/mon.init.d
@@ -44,16 +44,30 @@
set -e
-case $1 in
- start)
+
+function start_deamon {
echo -n Starting $DESC:
- start-stop-daemon --start --quiet --pidfile $PIDFILE --chuid $USER --group $GROUP --exec $DAEMON -- $DAEMON_OPTS
+ start-stop-daemon --start --oknodo --pidfile $PIDFILE --chuid $USER --group $GROUP --exec $DAEMON -- $DAEMON_OPTS
echo $NAME.
- ;;
- stop)
+}
+function stop_daemon {
echo -n Stopping $DESC:
- start-stop-daemon --stop --quiet --pidfile $PIDFILE
+ start-stop-daemon --stop --oknodo --pidfile $PIDFILE
echo $NAME.
+}
+
+
+
+case $1 in
+ start)
+ if [ -f $PIDFILE ] ; then
+ echo $NAME daemon is already running.
+ else
+ start_deamon
+ fi
+ ;;
+ stop)
+ stop_daemon
;;
#reload)
#
@@ -80,11 +94,14 @@
|| exit 0
;;
restart)
-echo -n Restarting $DESC:
- start-stop-daemon --stop --quiet --pidfile $PIDFILE
- sleep 1
- start-stop-daemon --start --quiet --pidfile $PIDFILE --chuid $USER --group $GROUP --exec $DAEMON -- $DAEMON_OPTS
- echo $NAME.
+ if [ -f $PIDFILE ] ; then
+ stop_daemon
+ sleep 1
+ start_deamon
+ else
+ echo $NAME daemon is not running.
+ start_deamon
+ fi
;;
*)
N=/etc/init.d/$NAME
diff -u mon-0.99.2/debian/changelog mon-0.99.2/debian/changelog
--- mon-0.99.2/debian/changelog
+++ mon-0.99.2/debian/changelog
@@ -1,3 +1,10 @@
+mon (0.99.2-13+lenny1) stable-proposed-updates; urgency=low
+
+ * debian/mon.init.d: Script fixes to return success when daemon
+is restarted but is already running. (Closes: #538133)
+
+ -- Dario Minnucci mid...@debian.org Sun, 18 Jul 2010 17:09:04 +0200
+
mon (0.99.2-13) unstable; urgency=low
* debian/control: Conforms with latest Standards Version 3.8.0
signature.asc
Description: OpenPGP digital signature
Bug#589199: cannot install ardour on testing
On Sun, 2010-07-18 at 17:20 +0200, Reinhard Tartler wrote: reassing 589199 libaubio2 stop On Sat, Jul 17, 2010 at 17:11:38 (CEST), Adam D. Barratt wrote: On Thu, 2010-07-15 at 22:44 -0400, Reinhard Tartler wrote: On Thu, Jul 15, 2010 at 14:23:45 (EDT), Marco wrote: The following packages have unmet dependencies: ardour: Depends: jackd (= 0.103.0) but it is not going to be installed E: Broken packages [...] The following packages have unmet dependencies: ardour: Depends: libaubio2 but it is not going to be installed Depends: libjack0 (= 0.118.0) but it is not going to be installed E: Broken packages [...] In order to fix this bug, the package libaubio2 needs to be binNMUed. In this basis, I'm reassinging this bug to the package libaubio2 Adam, can you please schedule a binNMU? binNMUs for aubio scheduled. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586465: doesn't really fix xfce4-taskmanager on kbsd
2010/7/18 Christoph Egger christ...@christoph-egger.org: Hi! Two things to note. First, the old taskmanager mostly worked on kbsd (probably using the /proc emulation present in kbsd. And secondly it doesn't build on the kfreebsd route, failing as below. Hi Christoph, As you may have guessed, my knowledge about kfreebsd is null. Thanks for telling me, in this case, it will probably work fine to build the project with the -linux.c source, that still uses fopen() within /proc. Frankly, I've never found something to deal with processes on Linux (I may look at the ps program actually). If you tell me afterwards what doesn't work, I can help providing patches. However, testing with the git master branch is a better idea in this case. The same patch as previously is attached but to build with -linux.c. Regards Christoph Kind Regards -- Mike --- configure.orig 2010-07-18 17:37:18.232382812 +0200 +++ configure 2010-07-18 17:39:12.338202369 +0200 @@ -13006,7 +13006,7 @@ done ;; - linux*) + linux*|kfreebsd*-gnu) ac_os_implementation=linux for ac_header in pwd.h signal.h stdio.h string.h sys/resource.h \ sys/stat.h sys/types.h unistd.h
Processed: reassign 589199 to libaubio2
Processing commands for cont...@bugs.debian.org: reassign 589199 libaubio2 Bug #589199 [ardour] cannot install ardour on testing Bug reassigned from package 'ardour' to 'libaubio2'. thanks Stopping processing here. Please contact me if you need assistance. -- 589199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589199 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#589546: hivex: FTBFS: missing b-d on libxml2-dev, pkg-config, others?
Package: hivex Version: 1.2.2+git20100712-1 Severity: serious Justification: fails to build from source hivex fails to build on the autobuilders, which typically start without a lot of packages installed: configure: error: The pkg-config script could not be found or is too old. Make sure it is in your PATH or set the PKG_CONFIG environment variable to the full path to pkg-config. Alternatively, you may set the environment variables LIBXML2_CFLAGS and LIBXML2_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. Adding a build dependency on pkg-config should address that particular error, but the build probably won't get much further unless you add one against libxml2-dev as well; please add both and double check that you aren't missing any others. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589547: xserver-xorg-video-nv: (EE) NV: Kernel modesetting driver in use, refusing to load: no xorg after kernel upgrade
Package: xserver-xorg-video-nv Version: 1:2.1.17-3 Severity: grave Justification: renders package unusable Hi after full-upgrading from 2.6.32-trunk-486 to 2.6.32-5-486 (and touching nothing on the config) the xserver is no more loaded due to a nv-driver/module problem: (EE) NV: Kernel modesetting driver in use, refusing to load (EE) No devices detected. Do not know what means Kernel modesetting driver, in trunk all was fine. (I'm writing my report from the trunk kernel). My card is a GeForce FX 5200. Here's a log of the attempts. fermi:~# cat /root/kdm.log.2010-07-18.1727 Note that your system uses syslog. All of kdm's internally generated messages (i.e., not from libraries and external programs/scripts it uses) go to the daemon.* syslog facility; check your syslog configuration to find out to which file(s) it is logged. PAM logs messages related to authentication to authpriv.*. X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.14-dsa-ia32 i686 Debian Current Operating System: Linux fermi 2.6.32-trunk-486 #1 Sun Jan 10 05:53:18 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-trunk-486 root=UUID=22cf65b7-ff9a-4728-b4b5-3e822d019398 ro quiet splash Build Date: 03 June 2010 04:08:50PM xorg-server 2:1.7.7-2 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Jul 18 12:27:51 2010 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (EE) Failed to load module nouveau (module does not exist, 0) (EE) Failed to load module vesa (module does not exist, 0) (EE) Failed to load module fbdev (module does not exist, 0) SELinux: Disabled on system, not enabling in X server QFont::fromString: Invalid description 'Serif,20,5,0,50,0' QFont::fromString: Invalid description 'Sans Serif,10,5,0,50,0' QFont::fromString: Invalid description 'Sans Serif,10,5,0,75,0' error setting MTRR (base = 0xd000, size = 0x0800, type = 1) Inappropriate ioctl for device (25) X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.14-dsa-ia32 i686 Debian Current Operating System: Linux fermi 2.6.32-5-486 #1 Tue Jun 1 04:27:25 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-486 root=UUID=22cf65b7-ff9a-4728-b4b5-3e822d019398 ro quiet splash Build Date: 03 June 2010 04:08:50PM xorg-server 2:1.7.7-2 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Jul 18 12:53:20 2010 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (EE) Failed to load module nouveau (module does not exist, 0) (EE) Failed to load module vesa (module does not exist, 0) (EE) Failed to load module fbdev (module does not exist, 0) (EE) NV: Kernel modesetting driver in use, refusing to load (EE) No devices detected. Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.14-dsa-ia32 i686 Debian Current Operating System: Linux fermi 2.6.32-5-486 #1 Tue Jun 1 04:27:25 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-486 root=UUID=22cf65b7-ff9a-4728-b4b5-3e822d019398 ro quiet splash Build Date: 03 June 2010 04:08:50PM xorg-server 2:1.7.7-2 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Jul 18 13:45:08 2010 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (EE) Failed to load module
Bug#589549: fetch-crl: cronjob fails everytime
Package: fetch-crl Version: 2.8.5-1 Severity: grave Justification: renders package unusable # cat /etc/cron.d/fetch-crl # Cron job running by default every 6 hours. # The lock file can be enabled or disabled via a # service fetch-crl-cron start # chkconfig fetch-crl-cron on # Note the lock file not existing is success hence the the slightly odd logic # below. 22 */6 * * *root[ ! -f /var/lock/fetch-crl-cron ] || /usr/sbin/fetch-crl -r 20 -a 24 --quiet # /usr/sbin/fetch-crl -r 20 -a 24 --quiet; echo $? fetch-crl[17688]: 20100718T184545+0200 '/etc/grid-security/certificates' is not a directory or cannot be written 2 # Of course this crap gets delivered four times a day as email. Helmut -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33.2 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages fetch-crl depends on: ii openssl 0.9.8o-1 Secure Socket Layer (SSL) binary a ii wget 1.12-2 retrieves files from the web fetch-crl recommends no packages. fetch-crl 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#589550: fetch-crl: package fails to install
Package: fetch-crl Version: 2.8.5-1 Severity: grave Justification: renders package unusable $ aptitude install fetch-crl ... Setting up fetch-crl (2.8.5-1) ... update-rc.d: error: expected runlevel [0-9S] (did you forget . ?) usage: update-rc.d [-n] [-f] basename remove update-rc.d [-n] basename defaults [NN | SS KK] update-rc.d [-n] basename start|stop NN runlvl [runlvl] [...] . update-rc.d [-n] basename disable|enable [S|2|3|4|5] -n: not really -f: force The disable|enable API is not stable and might change in the future. dpkg: error processing fetch-crl (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: fetch-crl $ Helmut -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33.2 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages fetch-crl depends on: ii openssl 0.9.8o-1 Secure Socket Layer (SSL) binary a ii wget 1.12-2 retrieves files from the web fetch-crl recommends no packages. fetch-crl 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#589551: clutter-1.0: FTBFS on kfreebsd-*: clutter-stage-glx.c:502: error: expected expression before '}' token
Source: clutter-1.0 Version: 1.2.12-1 Severity: serious Justification: FTBFS Hi, your package no longer builds from source on kfreebsd-*: | /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DG_LOG_DOMAIN=\ClutterGLX\ -I../.. -I../../clutter -I../../clutter/cogl -I../../clutter/x11 -I../../clutter -I../../clutter/cogl -DCLUTTER_COMPILATION -pthread -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/json-glib-1.0-DCLUTTER_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS -g -O2 -g -Wall -O2 -c -o clutter-stage-glx.lo clutter-stage-glx.c | libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DG_LOG_DOMAIN=\ClutterGLX\ -I../.. -I../../clutter -I../../clutter/cogl -I../../clutter/x11 -I../../clutter -I../../clutter/cogl -DCLUTTER_COMPILATION -pthread -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/json-glib-1.0 -DCLUTTER_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS -g -O2 -g -Wall -O2 -c clutter-stage-glx.c -fPIC -DPIC -o .libs/clutter-stage-glx.o | clutter-stage-glx.c: In function 'wait_for_vblank': | clutter-stage-glx.c:502: error: expected expression before '}' token | make[5]: *** [clutter-stage-glx.lo] Error 1 | make[5]: Leaving directory `/build/buildd-clutter-1.0_1.2.12-1-kfreebsd-amd64-TD7dXE/clutter-1.0-1.2.12/clutter/glx' Full build logs: https://buildd.debian.org/status/package.php?p=clutter-1.0 Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589552: ardour: Uninstallable
Package: ardour Severity: grave Tags: sid Justification: renders package unusable I get this when trying to install ardour: r...@asus:/home/tmac# apt-get install ardour Reading package lists... Done Building dependency tree Reading state information... Done 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. ardour: Depends: libaubio2 but it is not going to be installed E: Broken packages Meanwhile, libaubio2 is installed on my system... Torquil Sørensen -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ardour depends on: pn jackd none(no description available) ii libart-2.0-2 2.3.21-1 Library of functions for 2D graphi ii libasound2 1.0.23-1 shared library for ALSA applicatio ii libatk1.0-01.30.0-1 The ATK accessibility toolkit pn libaubio2 none(no description available) ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-4 The Cairo 2D vector graphics libra ii libcairomm-1.0-1 1.8.4-3 C++ wrappers for Cairo (shared lib ii libcurl3-gnutls7.21.0-1 Multi-protocol file transfer libra ii libfftw3-3 3.2.2-1 library for computing Fast Fourier ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.0-2 FreeType 2 font engine, shared lib ii libgcc11:4.4.4-7 GCC support library ii libglib2.0-0 2.24.1-1 The GLib library of C routines ii libglibmm-2.4-1c2a 2.24.2-1 C++ wrapper for the GLib toolkit ( ii libgnomecanvas2-0 2.30.1-1 A powerful object-oriented display pn libgnomecanvasmm-2.6-1 none(no description available) ii libgtk2.0-02.20.1-1 The GTK+ graphical user interface ii libgtkmm-2.4-1c2a 1:2.20.3-1C++ wrappers for GTK+ (shared libr ii libjack0 1:0.118+svn3796-7 JACK Audio Connection Kit (librari ii liblo7 0.26~repack-5 Lightweight OSC library ii liblrdf0 0.4.0-3 a library to manipulate RDF files ii libpango1.0-0 1.28.1-1 Layout and rendering of internatio ii libpangomm-1.4-1 2.26.2-1 C++ Wrapper for pango (shared libr ii libraptor1 1.4.21-2 Raptor RDF parser and serializer l ii librasqal2 0.9.19-1 Rasqal RDF query library ii librdf01.0.10-2 Redland Resource Description Frame ii libsamplerate0 0.1.7-3 Audio sample rate conversion libra ii libsigc++-2.0-0c2a 2.2.4.2-1 type-safe Signal Framework for C++ ii libslv2-9 0.6.6-4 A library for simple use of LV2 pl ii libsndfile11.0.21-2 Library for reading/writing audio ii libstdc++6 4.4.4-7 The GNU Standard C++ Library v3 ii libusb-0.1-4 2:0.1.12-15 userspace USB programming library ii libvamp-hostsdk3 2.1-1 helper library for Vamp hosts writ pn libvamp-sdk2 none(no description available) ii libxml22.7.7.dfsg-4 GNOME XML library ii libxslt1.1 1.1.26-5 XSLT 1.0 processing library - runt ii python 2.6.5-8 interactive high-level object-orie ii python-gtk22.17.0-2 Python bindings for the GTK+ widge pn python-twisted none(no description available) Versions of packages ardour recommends: ii iceweasel [www-browser] 3.5.10-1 Web browser based on Firefox ii w3m [www-browser] 0.5.2-7WWW browsable pager with excellent Versions of packages ardour suggests: pn jamin none (no description available) ii qjackctl 0.3.6-1User interface for controlling the -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588426: linux-image-2.6.32-5-amd64: fail to boot in a kvm virtual machine
This should probably be merged with #588509? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589560: firmware-iwlwifi: Wireless does not work anymore.
Package: firmware-iwlwifi Version: 0.26 Severity: grave Justification: renders package unusable Wireless does not work anymore. Version 0.25 was ok -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.97.2 tools for generating an initramfs ii linux-image-2.6.32-5-amd64 [l 2.6.32-15 Linux 2.6.32 for 64-bit PCs -- 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#585618: [Mesa-dev] [PATCH 1/6] pipe: Detect FreeBSD better
On Thu, Jun 24, 2010 at 01:07:17 -0700, Corbin Simpson wrote:
On Wed, Jun 23, 2010 at 6:31 PM, nobled nob...@dreamwidth.org wrote:
Taking advice from the Debian BSD porting guide:
http://glibc-bsd.alioth.debian.org/porting/PORTING
This should help fix Debian bug #585618 (gallium build failure).
---
src/gallium/include/pipe/p_config.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/gallium/include/pipe/p_config.h
b/src/gallium/include/pipe/p_config.h
index b81702a..68025fa 100644
--- a/src/gallium/include/pipe/p_config.h
+++ b/src/gallium/include/pipe/p_config.h
@@ -128,7 +128,7 @@
#define PIPE_OS_UNIX
#endif
-#if defined(__FreeBSD__)
+#if defined(__FreeBSD__) || defined(__FreeBSD_kernel__)
#define PIPE_OS_FREEBSD
#define PIPE_OS_BSD
#define PIPE_OS_UNIX
--
1.5.4.3
Looks reasonable; does this actually work for you? I'd like somebody
to test first.
I verified that this builds on a kfreebsd system on top of 7.8.2, and
looking at the differences between PIPE_OS_LINUX and PIPE_OS_{,FREE}BSD
in the code this seems reasonable, so
Reviewed-by: Julien Cristau jcris...@debian.org
Maybe also consider:
diff --git a/src/gallium/auxiliary/rtasm/rtasm_execmem.c
b/src/gallium/auxiliary/rtasm/rtasm_execmem.c
index 65d5ce7..bd84532 100644
--- a/src/gallium/auxiliary/rtasm/rtasm_execmem.c
+++ b/src/gallium/auxiliary/rtasm/rtasm_execmem.c
@@ -37,7 +37,7 @@
#include rtasm_execmem.h
-#if defined(PIPE_OS_BSD)
+#ifndef MAP_ANONYMOUS
#define MAP_ANONYMOUS MAP_ANON
#endif
(the kfreebsd glibc headers define MAP_ANONYMOUS to MAP_ANON already, so
this one shouldn't be strictly necessary)
Cheers,
Julien
signature.asc
Description: Digital signature
Bug#589466: marked as done (fbpanel: FTBFS on kfreebsd-*: volume.c:264: error: 'SOUND_MIXER_VOLUME' undeclared)
Your message dated Sun, 18 Jul 2010 17:32:12 + with message-id e1oaxim-0006tk...@franck.debian.org and subject line Bug#589466: fixed in fbpanel 6.1-2 has caused the Debian Bug report #589466, regarding fbpanel: FTBFS on kfreebsd-*: volume.c:264: error: 'SOUND_MIXER_VOLUME' undeclared 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.) -- 589466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: fbpanel Version: 6.1-1 Severity: serious Justification: FTBFS User: debian-...@lists.debian.org Usertags: kfreebsd Hi, your package no longer builds on kfreebsd-*: | cc -Wall -g -O2 -O2 -Wall -I/build/buildd-fbpanel_6.1-1-kfreebsd-i386-BPxwNN/fbpanel-6.1 -I/build/buildd-fbpanel_6.1-1-kfreebsd-i386-BPxwNN/fbpanel-6.1/panel -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -fPIC -O2 -Wall -I/build/buildd-fbpanel_6.1-1-kfreebsd-i386-BPxwNN/fbpanel-6.1 -I/build/buildd-fbpanel_6.1-1-kfreebsd-i386-BPxwNN/fbpanel-6.1/panel -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -fPI C -DPLUGIN -O2 -Wall -I/build/buildd-fbpanel_6.1-1-kfreebsd-i386-BPxwNN/fbpanel-6.1 -I/build/buildd-fbpanel_6.1-1-kfreebsd-i386-BPxwNN/fbpanel-6.1/panel -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -fPIC -DPLUGIN -c -o volume.o volume.c | volume.c: In function 'oss_get_volume': | volume.c:54: warning: implicit declaration of function 'MIXER_READ' | volume.c: In function 'oss_set_volume': | volume.c:69: warning: implicit declaration of function 'MIXER_WRITE' | volume.c: In function 'volume_constructor': | volume.c:264: error: 'SOUND_MIXER_VOLUME' undeclared (first use in this function) | volume.c:264: error: (Each undeclared identifier is reported only once | volume.c:264: error: for each function it appears in.) | make[3]: *** [volume.o] Error 1 Full build logs: https://buildd.debian.org/status/package.php?p=fbpanel Please contact -bsd@ if you need assistance. Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: fbpanel Source-Version: 6.1-2 We believe that the bug you reported is fixed in the latest version of fbpanel, which is due to be installed in the Debian FTP archive: fbpanel_6.1-2.debian.tar.gz to main/f/fbpanel/fbpanel_6.1-2.debian.tar.gz fbpanel_6.1-2.dsc to main/f/fbpanel/fbpanel_6.1-2.dsc fbpanel_6.1-2_amd64.deb to main/f/fbpanel/fbpanel_6.1-2_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 589...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. der...@debian.org (supplier of updated fbpanel 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: Sun, 18 Jul 2010 13:29:42 -0300 Source: fbpanel Binary: fbpanel Architecture: source amd64 Version: 6.1-2 Distribution: unstable Urgency: low Maintainer: Ulises Vitulli der...@debian.org Changed-By: der...@debian.org Description: fbpanel- A lightweight X11 desktop panel Closes: 589466 Changes: fbpanel (6.1-2) unstable; urgency=low . * Fix FTBFS on kFreeBSD due to linux-specific features (Closes: #589466). Checksums-Sha1: 2c3f99eb4dbc1fabdfd35d7a6fec4d3ba8546eb8 1699 fbpanel_6.1-2.dsc d9026370f9969a3a406dc4bd2fff7857026039d4 9974 fbpanel_6.1-2.debian.tar.gz c55df559840b85316dac26a0b346568c692838ad 237216 fbpanel_6.1-2_amd64.deb Checksums-Sha256:
Bug#589547: xserver-xorg-video-nv: (EE) NV: Kernel modesetting driver in use, refusing to load: no xorg after kernel upgrade
install: xserver-xorg-video-nouveau see if fixed.. - Original Message From: r.ductor r.duc...@gmail.com To: Debian Bug Tracking System sub...@bugs.debian.org Sent: Sun, July 18, 2010 5:40:51 PM Subject: Bug#589547: xserver-xorg-video-nv: (EE) NV: Kernel modesetting driver in use, refusing to load: no xorg after kernel upgrade Package: xserver-xorg-video-nv Version: 1:2.1.17-3 Severity: grave Justification: renders package unusable Hi after full-upgrading from 2.6.32-trunk-486 to 2.6.32-5-486 (and touching nothing on the config) the xserver is no more loaded due to a nv-driver/module problem: (EE) NV: Kernel modesetting driver in use, refusing to load (EE) No devices detected. Do not know what means Kernel modesetting driver, in trunk all was fine. (I'm writing my report from the trunk kernel). My card is a GeForce FX 5200. Here's a log of the attempts. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589552: ardour: Uninstallable
severity 589199 normal severity 589552 normal forcemerge 589552 589199 stop On Sun, Jul 18, 2010 at 18:54:24 (CEST), Torquil Macdonald Sørensen wrote: Package: ardour Severity: grave Tags: sid Justification: renders package unusable no, it doesn't. you can still install it with jackd1 I get this when trying to install ardour: please see a more detailed analysis in bug 589199. I'm merging these two bugs now. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#589552: ardour: Uninstallable
Processing commands for cont...@bugs.debian.org: severity 589199 normal Bug #589199 [libaubio2] cannot install ardour on testing Severity set to 'normal' from 'grave' severity 589552 normal Bug #589552 [ardour] ardour: Uninstallable Severity set to 'normal' from 'grave' forcemerge 589552 589199 Bug#589552: ardour: Uninstallable Bug#589199: cannot install ardour on testing Mismatch - only Bugs in the same package can be forcibly merged: Bug 589199 is not in the same package as 589552 stop Stopping processing here. Please contact me if you need assistance. -- 589199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589199 589552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589552 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#589532: grub-rescue-pc: still does not depend on xorriso, although it should
severity 589532 wishlist thanks On Sun, Jul 18, 2010 at 04:30:57PM +0200, Pier Luigi Pau wrote: Package: grub-rescue-pc Version: 1.98+20100710-1 Severity: grave Justification: renders package unusable No, it doesn't. Downgrading. Greetings, changelog for version 1.98+20100527-1 mentions: [cut] * Suggest xorriso (= 0.5.6.pl00) in grub-common, since grub-mkrescue now needs it. Depend on it in grub-rescue-pc. [cut] However, grub-rescue-pc still does not depend on xorriso (or the dependency was removed by mistake - I haven't reviewed every version since), and it is possible to install the former without the latter being automatically installed, with the result that grub-mkrescue exits with an error message: # grub-mkrescue -o 20100718a.iso But grub-mkrescue is not in the grub-rescue-pc package. grub-rescue-pc simply ships the disk images, and you can definitely use it without having xorriso. grub-mkrescue is in grub-common (which I think is the right place for it), and it would not be appropriate to have that depend on xorriso since grub-common has many other uses that don't require xorriso, but it suggests it. The wishlist item is that perhaps grub-mkrescue should explicitly advise installing the xorriso package if you don't have it. -- Colin Watson [cjwat...@debian.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#589532: grub-rescue-pc: still does not depend on xorriso, although it should
Processing commands for cont...@bugs.debian.org: severity 589532 wishlist Bug #589532 [grub-rescue-pc] grub-rescue-pc: still does not depend on xorriso, although it should Severity set to 'wishlist' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 589532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589532 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: severity of 589560 is important
Processing commands for cont...@bugs.debian.org: severity 589560 important Bug #589560 [firmware-iwlwifi] firmware-iwlwifi: Wireless does not work anymore. Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 589560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589560 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#581182: changing severity
severity 581182 important thanks Hi, On Fri, Jun 04 2010, Christoph Anton Mitterer wrote: severity 581182 grave stop Changing severity to grave (makes the package in question unusable or mostly so) as it seems that also 2.6.32 kernels are affected, which are now in unstable, and therefore make this package unusable there. So, I tried the latest stable kernel, 2.6.34.1: ,[ Commands used ] | export MODULE_LOC=/usr/local/src/kernel/modules | | ev=$(uname -n) | if [ -n $1 ]; then | ev=$1 | fi | | make-kpkg --rootcmd=fakeroot --append-to-version=-$ev kernel_image | fakeroot make-kpkg --append-to-version=-$ev modules_image ` , | __ sudo dpkg -i linux-image-2.6.34.1-anzu_2.6.34.1-anzu-10.00.Custom_amd64.deb\ | nvidia-kernel-2.6.34.1-anzu_195.36.24-1+2.6.34.1-anzu-10.00.Custom_amd64.deb | Selecting previously deselected package linux-image-2.6.34.1-anzu. | (Reading database ... 375994 files and directories currently installed.) | Unpacking linux-image-2.6.34.1-anzu (from linux-image-2.6.34.1-anzu_2.6.34.1-anzu-10.00.Custom_amd64.deb) ... | Examining /etc/kernel/preinst.d/ | Done. | Selecting previously deselected package nvidia-kernel-2.6.34.1-anzu. | Unpacking nvidia-kernel-2.6.34.1-anzu (from nvidia-kernel-2.6.34.1-anzu_195.36.24-1+2.6.34.1-anzu-10.00.Custom_amd64.deb) ... | Setting up linux-image-2.6.34.1-anzu (2.6.34.1-anzu-10.00.Custom) ... | Running depmod. | Examining /etc/kernel/postinst.d. | run-parts: executing /etc/kernel/postinst.d/dkms 2.6.34.1-anzu /boot/vmlinuz-2.6.34.1-anzu | run-parts: executing /etc/kernel/postinst.d/force-build-link 2.6.34.1-anzu /boot/vmlinuz-2.6.34.1-anzu | run-parts: executing /etc/kernel/postinst.d/initramfs 2.6.34.1-anzu /boot/vmlinuz-2.6.34.1-anzu | run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.34.1-anzu /boot/vmlinuz-2.6.34.1-anzu | Running postinst hook script update-grub. | Generating grub.cfg ... | Found linux image: /boot/vmlinuz-2.6.34.1-anzu | Found linux image: /boot/vmlinuz-2.6.34-anzu | Found linux image: /boot/vmlinuz-2.6.32.8-anzu | Found linux image: /boot/vmlinuz-2.6.32.7-anzu | Found linux image: /boot/vmlinuz-2.6.32.1-anzu | Found linux image: /boot/vmlinuz-2.6.32-anzu | Found memtest86 image: /memtest86.bin | Found memtest86+ image: /memtest86+_multiboot.bin | Found Ubuntu 7.04 (7.04) on /dev/sda2 | done | Setting up nvidia-kernel-2.6.34.1-anzu (195.36.24-1+2.6.34.1-anzu-10.00.Custom) ... ` Then I tried: make-kpkg --rootcmd=fakeroot --append-to-version=-anzu buildpackage And that failed. So, the buildpackage target is borked. That does not make it mostly useless. I'll look into the issue; in the meanwhile, you can build, individually, the packages you need; though I understand no changes files means you can't sign the result (hence important severity) manoj -- I have great faith in fools -- self confidence my friends call it. Edgar Allan Poe Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/ 4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20 05B6 CF48 9438 C577 9A1C -- 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#581182: changing severity
Processing commands for cont...@bugs.debian.org: severity 581182 important Bug #581182 [kernel-package] kernel-package: make-kpkg buildpackage fails with 2.6.33 Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 581182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581182 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#523323: openarena-data: missing source code
On Thu, 03 Dec 2009 at 02:30:39 +, Simon McVittie wrote: As well as applying the attached, it's also necessary to repack the orig.tar.gz, replacing pak0.pk3 and mp-pak0.pk3 with versions that have are output by the included strip-qvms.pl. This will truncate any vm/*.qvm to 0 bytes long. I've been reconsidering the approach I was using before, since it's pretty ugly, and every time we change the format of the extra info provided, we'd need to re-upload openarena-data (yuck). So, I think it's worth getting it right first time! The approach I'm now planning is: * QVMs have a magic number in the header, with two possible values identifying variations on the format. Add a third value, which means load native code instead, and patch the engine to understand it * Write a C program that can construct QVM files with a desired CRC32 by brute force. Make some QVMs with the following contents: - the magic number to mean go and load the native code - whatever random rubbish the script generated to get the desired CRC32 On my laptop, it takes seconds to brute-force this using zlib with the attached program: searching for such that NTVE has CRC32 0x00031337 collision found: = 0x6fb2d782 (in this machine's endianness, whatever that is) ./a.out 0x31337 26.11s user 0.00s system 99% cpu 26.139 total * Replace each QVM with a brute-forced one constructed as above * While we're repacking the source tarball anyway, it would be more transparent if we decompose the PK3 files into their component files plus an (ordered!) file list, used that as the orig tarball, and zip up the PK3 file during build; we could also check for mismatches during build Regards, Simon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589550: fetch-crl: package fails to install
On Sun, Jul 18, 2010 at 06:43:49PM +0200, Helmut Grohne wrote: Package: fetch-crl Version: 2.8.5-1 Severity: grave Justification: renders package unusable $ aptitude install fetch-crl ... Setting up fetch-crl (2.8.5-1) ... update-rc.d: error: expected runlevel [0-9S] (did you forget . ?) usage: update-rc.d [-n] [-f] basename remove update-rc.d [-n] basename defaults [NN | SS KK] update-rc.d [-n] basename start|stop NN runlvl [runlvl] [...] . update-rc.d [-n] basename disable|enable [S|2|3|4|5] -n: not really -f: force The disable|enable API is not stable and might change in the future. dpkg: error processing fetch-crl (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: fetch-crl $ This bug seems to only affect installations that are not yet converted to dependency based init. Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588038: marked as done (Directory traversal flaw by editing and saving list entries via php-admin web interface)
Your message dated Sun, 18 Jul 2010 19:17:52 + with message-id e1oazn2-0007mn...@franck.debian.org and subject line Bug#588038: fixed in mlmmj 1.2.17-1.1 has caused the Debian Bug report #588038, regarding Directory traversal flaw by editing and saving list entries via php-admin web interface 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.) -- 588038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mlmmj Severity: grave Tags: security Hi, please see http://www.openwall.com/lists/oss-security/2010/06/23/5 https://bugzilla.redhat.com/show_bug.cgi?id=607256 Proposed patch by upstream: http://www.openwall.com/lists/oss-security/2010/06/26/1 This is CVE-2009-4896. Cheers, Moritz -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=C, lc_ctype=de_de.iso-8859...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages mlmmj depends on: ii dctrl-tools 2.14 Command-line tools to process Debi ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy ii exim4-daemon-light [mail-tran 4.71-4 lightweight Exim MTA (v4) daemon ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib mlmmj recommends no packages. Versions of packages mlmmj suggests: pn mlmmj-php-web none (no description available) pn mlmmj-php-web-admin none (no description available) ---End Message--- ---BeginMessage--- Source: mlmmj Source-Version: 1.2.17-1.1 We believe that the bug you reported is fixed in the latest version of mlmmj, which is due to be installed in the Debian FTP archive: mlmmj-php-web-admin_1.2.17-1.1_all.deb to main/m/mlmmj/mlmmj-php-web-admin_1.2.17-1.1_all.deb mlmmj-php-web_1.2.17-1.1_all.deb to main/m/mlmmj/mlmmj-php-web_1.2.17-1.1_all.deb mlmmj_1.2.17-1.1.diff.gz to main/m/mlmmj/mlmmj_1.2.17-1.1.diff.gz mlmmj_1.2.17-1.1.dsc to main/m/mlmmj/mlmmj_1.2.17-1.1.dsc mlmmj_1.2.17-1.1_amd64.deb to main/m/mlmmj/mlmmj_1.2.17-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 588...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated mlmmj 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: Sat, 17 Jul 2010 02:21:19 +0800 Source: mlmmj Binary: mlmmj mlmmj-php-web mlmmj-php-web-admin Architecture: source amd64 all Version: 1.2.17-1.1 Distribution: unstable Urgency: high Maintainer: Daniel Walrond deb...@djw.org.uk Changed-By: Thomas Goirand z...@debian.org Description: mlmmj - mail server independent mailing list manager mlmmj-php-web - web interface for mlmmj, written in php mlmmj-php-web-admin - administrative web interface for mlmmj, written in php Closes: 588038 Changes: mlmmj (1.2.17-1.1) unstable; urgency=high . * Non-maintainer QA upload. * Fixes CVE-2009-4896 mlmmj-php-admin directory traversal (Closes: #588038). Checksums-Sha1: 92d8676106448b066a6f390a9d52aa8fac6f45f8 1017 mlmmj_1.2.17-1.1.dsc 0bd88c44f082c100b9d2752990354763a2a51eb7 22085 mlmmj_1.2.17-1.1.diff.gz 43258d1481a6009e2a7caa75622c2012d061f79c 210554 mlmmj_1.2.17-1.1_amd64.deb 98ac368b91ecfed2d9e6d21cc58133b0352563ee 18076 mlmmj-php-web_1.2.17-1.1_all.deb 5b6c57478814983be131753ed20d5b5c35ad1806 33224 mlmmj-php-web-admin_1.2.17-1.1_all.deb Checksums-Sha256: ec48493e649fcf6859d98967a17c0317db3e9f1a58d5031461cfdbef 1017 mlmmj_1.2.17-1.1.dsc 7c7e8bca7b31e408281a7563161d1981c9fdba724946d0b10a88eb8e03c6e514 22085 mlmmj_1.2.17-1.1.diff.gz d0e2311b56544af3fa698870f5e4c23eeae5a7d1d015919379b5bae274336971 210554 mlmmj_1.2.17-1.1_amd64.deb 63e043415bb937be3c81eecee4e600f28ca7d40114eb95e82edea6a5567e8242 18076 mlmmj-php-web_1.2.17-1.1_all.deb f798353c19cfb4234002b1e21c540ee7c6c293c249b432cb53af8ccb6845b473 33224 mlmmj-php-web-admin_1.2.17-1.1_all.deb Files: b88ef62bbb89c57d286d455fcd77ab4b 1017 mail optional mlmmj_1.2.17-1.1.dsc 0331f65b07abd8efa54ae4bacc1e6637 22085
Bug#589518: marked as done ([python] error of python during apt-get dist-upgrade)
Your message dated Sun, 18 Jul 2010 21:49:24 +0200
with message-id 20100718194924.gh20...@piotro.eu
and subject line Re: Bug#589518: [python] error of python during apt-get
dist-upgrade
has caused the Debian Bug report #589518,
regarding [python] error of python during apt-get dist-upgrade
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.)
--
589518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python
Version: 2.6.5-5
Severity: critical
--- Please enter the report below this line. ---
During the apt-get dist-upgrade process I got (sorry it in in Italian)
Elaborazione dei trigger per menu...
Elaborazione dei trigger per python-support...
Compiling /usr/lib/pymodules/python2.4/MythTV/ttvdb/cache.py ...
SyntaxError: ('future feature with_statement is not defined',)
Date:dom lug 18 Time:13:35:35
User:root Computer:europa Base:~ Current:
and the apt-get stops (perhaps leaving not configured something). The
next apt-get dist-upgrade sid me that there is nothing to update.
Thanks
Marco
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.32-5-686-bigmem
Debian Release: squeeze/sid
500 testing-proposed-updates ftp.fr.debian.org
500 testing www.debian-multimedia.org
500 testing security.debian.org
500 testing http.us.debian.org
500 testing ftp.fr.debian.org
--- Package information. ---
Depends (Version) | Installed
=-+-===
python2.6 (= 2.6.5+20100616-1~) | 2.6.5+20100706-1
python-minimal (= 2.6.5-5) | 2.6.5-5
Package's Recommends field is empty.
Suggests (Version) | Installed
-+-=
python-doc (= 2.6.5-5) |
python-tk (= 2.6.5-5) | 2.6.5-1
python-profiler (= 2.6.5-5) |
---End Message---
---BeginMessage---
[Marco Righi, 2010-07-18]
During the apt-get dist-upgrade process I got (sorry it in in Italian)
`LC_ALL=C apt-get dist-upgrade` will output in English... anyway,
there's no need for translation, bug is clear. MythTV requires
Python = 2.5 and its maintainer didn't set the right minimum version.
Debian doesn't have MythTV package so I'm closing this bug.
Christian: please put = 2.5 in XS-Python-Version or 2.5- in
debian/pyversions
Elaborazione dei trigger per menu...
Elaborazione dei trigger per python-support...
Compiling /usr/lib/pymodules/python2.4/MythTV/ttvdb/cache.py ...
SyntaxError: ('future feature with_statement is not defined',)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
---End Message---
Processed: libmodplug0c2: ABI change without soname change (causing silence)
Processing commands for cont...@bugs.debian.org: severity 588465 serious Bug #588465 [libmodplug0c2] libmodplug0c2: trackers become silent in VLC with 0.8.8 update Severity set to 'serious' from 'important' retitle 588465 libmodplug0c2: ABI change without soname change (causing silence) Bug #588465 [libmodplug0c2] libmodplug0c2: trackers become silent in VLC with 0.8.8 update Changed Bug title to 'libmodplug0c2: ABI change without soname change (causing silence)' from 'libmodplug0c2: trackers become silent in VLC with 0.8.8 update' thanks Stopping processing here. Please contact me if you need assistance. -- 588465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588465 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#589587: pymvpa: nonexistent build-dependency: python-numpy-ext
Source: pymvpa Version: 0.4.5~dev23-1 Severity: serious Justification: FTBFS pymvpa build-depends on python-numpy-ext, but this package is no longer available in unstable. -- Jakub Wilk signature.asc Description: Digital signature
Bug#580359: marked as done (slon_start exposes password in process list)
Your message dated Mon, 19 Jul 2010 00:18:02 +0200 with message-id 20100718221802.gb2...@mobee and subject line workaround for the issue has caused the Debian Bug report #580359, regarding slon_start exposes password in process list 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.) -- 580359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: slony1-bin Version: 1.2.20-2 Severity: serious Tags: security Hi, When starting slon with slon_start the password is exposed into the process list. This looks like a security risk to me. Laurent Bigonville ---End Message--- ---BeginMessage--- Hi, http://linuxfinances.info/info/faq.html#AEN48451 documents a workaround: Q: ps finds passwords on command line If I run a ps command, I, and everyone else, can see passwords on the command line. A: Take the passwords out of the Slony configuration, and put them into $(HOME)/.pgpass. Cheers, Serafeim ---End Message---
Bug#589588: mlpy: nonexistent build-dependency: python-numpy-ext
Source: mlpy Version: 2.2.0~dfsg1-1 Severity: serious Justification: FTBFS mlpy build-depends on python-numpy-ext, but this package is no longer available in unstable. -- Jakub Wilk signature.asc Description: Digital signature
Bug#589589: pynifti: nonexistent build-dependency: python-numpy-ext
Source: pynifti Version: 0.20100607.1-1 Severity: serious Justification: FTBFS pynifti build-depends on python-numpy-ext, but this package is no longer available in unstable. -- Jakub Wilk signature.asc Description: Digital signature
Bug#589590: scikit-learn: nonexistent build-dependency: python-numpy-ext
Source: scikit-learn Version: 0.4-1 Severity: serious Justification: FTBFS scikit-learn build-depends on python-numpy-ext, but this package is no longer available in unstable. -- Jakub Wilk signature.asc Description: Digital signature
Bug#589592: libvigraimpex: FTBFS: __multiarray_api.h:1208: error: 'NPY_API_VERSION' was not declared in this scope
Source: libvigraimpex Version: 1.7.0+dfsg-4 Severity: serious Justification: FTBFS VIGRA fails to build from source when built with numpy 1.4.1: […] | [ 51%] Building CXX object vigranumpy/src/core/CMakeFiles/vigranumpy_core.dir/vigranumpycore.cxx.o | cd /tmp/buildd/libvigraimpex-1.7.0+dfsg/obj.python2.6/vigranumpy/src/core /usr/lib/ccache/c++ -Dvigranumpy_core_EXPORTS -DHasHDF5 -g -O2 -O3 -DNDEBUG -fPIC -I/tmp/buildd/libvigraimpex-1.7.0+dfsg/include -I/tmp/buildd/libvigraimpex-1.7.0+dfsg/obj.python2.6/include -I/usr/include/python2.6 -I/usr/lib/pymodules/python2.6/numpy/core/include -o CMakeFiles/vigranumpy_core.dir/vigranumpycore.cxx.o -c /tmp/buildd/libvigraimpex-1.7.0+dfsg/vigranumpy/src/core/vigranumpycore.cxx | In file included from /usr/include/python2.6/Python.h:8, | from /tmp/buildd/libvigraimpex-1.7.0+dfsg/vigranumpy/src/core/vigranumpycore.cxx:39: | /usr/include/python2.6/pyconfig.h:1031:1: warning: _POSIX_C_SOURCE redefined | In file included from /usr/include/c++/4.4/i486-linux-gnu/bits/os_defines.h:39, | from /usr/include/c++/4.4/i486-linux-gnu/bits/c++config.h:243, | from /usr/include/c++/4.4/iostream:39, | from /tmp/buildd/libvigraimpex-1.7.0+dfsg/vigranumpy/src/core/vigranumpycore.cxx:38: | /usr/include/features.h:158:1: warning: this is the location of the previous definition | In file included from /usr/include/python2.6/Python.h:8, | from /tmp/buildd/libvigraimpex-1.7.0+dfsg/vigranumpy/src/core/vigranumpycore.cxx:39: | /usr/include/python2.6/pyconfig.h:1040:1: warning: _XOPEN_SOURCE redefined | In file included from /usr/include/c++/4.4/i486-linux-gnu/bits/os_defines.h:39, | from /usr/include/c++/4.4/i486-linux-gnu/bits/c++config.h:243, | from /usr/include/c++/4.4/iostream:39, | from /tmp/buildd/libvigraimpex-1.7.0+dfsg/vigranumpy/src/core/vigranumpycore.cxx:38: | /usr/include/features.h:160:1: warning: this is the location of the previous definition | In file included from /usr/include/python2.6/numpy/ndarrayobject.h:18, | from /usr/include/python2.6/numpy/arrayobject.h:14, | from /tmp/buildd/libvigraimpex-1.7.0+dfsg/include/vigra/numpy_array.hxx:50, | from /tmp/buildd/libvigraimpex-1.7.0+dfsg/vigranumpy/src/core/vigranumpycore.cxx:41: | /usr/include/python2.6/numpy/numpyconfig.h:4:26: error: _numpyconfig.h: No such file or directory | In file included from /usr/include/python2.6/numpy/ndarrayobject.h:68, | from /usr/include/python2.6/numpy/arrayobject.h:14, | from /tmp/buildd/libvigraimpex-1.7.0+dfsg/include/vigra/numpy_array.hxx:50, | from /tmp/buildd/libvigraimpex-1.7.0+dfsg/vigranumpy/src/core/vigranumpycore.cxx:41: | /usr/include/python2.6/numpy/npy_common.h:840: error: 'npy_int64' does not name a type | /usr/include/python2.6/numpy/npy_common.h:841: error: 'npy_int64' does not name a type | In file included from /usr/include/python2.6/numpy/ndarrayobject.h:1238, | from /usr/include/python2.6/numpy/arrayobject.h:14, | from /tmp/buildd/libvigraimpex-1.7.0+dfsg/include/vigra/numpy_array.hxx:50, | from /tmp/buildd/libvigraimpex-1.7.0+dfsg/vigranumpy/src/core/vigranumpycore.cxx:41: | /usr/include/python2.6/numpy/__multiarray_api.h: In function 'int _import_array()': | /usr/include/python2.6/numpy/__multiarray_api.h:1202: error: 'NPY_ABI_VERSION' was not declared in this scope | /usr/include/python2.6/numpy/__multiarray_api.h:1208: error: 'NPY_API_VERSION' was not declared in this scope | In file included from /tmp/buildd/libvigraimpex-1.7.0+dfsg/vigranumpy/src/core/vigranumpycore.cxx:41: | /tmp/buildd/libvigraimpex-1.7.0+dfsg/include/vigra/numpy_array.hxx: At global scope: | /tmp/buildd/libvigraimpex-1.7.0+dfsg/include/vigra/numpy_array.hxx:547: error: 'NPY_INT16' was not declared in this scope | /tmp/buildd/libvigraimpex-1.7.0+dfsg/include/vigra/numpy_array.hxx: In static member function 'static bool vigra::NumpyArrayValuetypeTraitsshort int::isValuetypeCompatible(const PyArrayObject*)': | /tmp/buildd/libvigraimpex-1.7.0+dfsg/include/vigra/numpy_array.hxx:547: error: 'NPY_INT16' was not declared in this scope | /tmp/buildd/libvigraimpex-1.7.0+dfsg/include/vigra/numpy_array.hxx: In static member function 'static PyObject* vigra::NumpyArrayValuetypeTraitsshort int::typeObject()': | /tmp/buildd/libvigraimpex-1.7.0+dfsg/include/vigra/numpy_array.hxx:547: error: 'NPY_INT16' was not declared in this scope | /tmp/buildd/libvigraimpex-1.7.0+dfsg/include/vigra/numpy_array.hxx: At global scope: | /tmp/buildd/libvigraimpex-1.7.0+dfsg/include/vigra/numpy_array.hxx:548: error: 'NPY_UINT16' was not declared in this scope | /tmp/buildd/libvigraimpex-1.7.0+dfsg/include/vigra/numpy_array.hxx: In static member function 'static bool
Bug#581318: intent to NMU
tags 584396 pending
tags 581318 pending
thanks
Dear maintainer,
I've prepared an NMU for d-shlibs (versioned as 0.44+nmu1) and uploaded it to
DELAYED/4. Please feel free to tell me if I should delay it longer.
Cheers,
Serafeim
diff -Nurp d-shlibs-0.44.orig//d-devlibdeps d-shlibs-0.44/d-devlibdeps
--- d-shlibs-0.44.orig//d-devlibdeps2010-04-25 17:13:29.0 +0200
+++ d-shlibs-0.44/d-devlibdeps 2010-07-19 01:15:46.0 +0200
@@ -102,13 +102,13 @@ function overridedevlibdeps () {
-e 's/libtheora0-dev/libtheora-dev/' \
-e 's/libvorbis0-dev/libvorbis-dev/' \
-e 's/libvorbisenc2-dev/libvorbis-dev/' \
- -e 's/libX\(.*\)[0-9]-dev/libx\1-dev/' \
-e 's/libX11-6-dev/libx11-dev | xlibs-dev ( 4.3.0)/' \
-e 's/libXext6-dev/libxext-dev | xlibs-dev ( 4.3.0)/' \
-e 's/libXi6-dev/libxi-dev | xlibs-dev ( 4.3.0)/' \
-e 's/libxml2-2-dev/libxml2-dev/' \
-e 's/libXpm4-dev/libxpm-dev | xlibs-dev ( 4.3.0)/' \
-e 's/libz1-dev/zlib1g-dev/' \
+ -e 's/libX\(.*\)[0-9]-dev/libx\1-dev/' \
${overri...@]/#/-e} \
diff -Nurp d-shlibs-0.44.orig//debian/changelog d-shlibs-0.44/debian/changelog
--- d-shlibs-0.44.orig//debian/changelog2010-04-25 17:27:32.0
+0200
+++ d-shlibs-0.44/debian/changelog 2010-07-19 01:23:12.0 +0200
@@ -1,3 +1,11 @@
+d-shlibs (0.44+nmu1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Apply patch to fix FTBFS of packages that depend on libx11-dev.
+Closes: bug#581318, bug#584396, thanks to Sebastian Andrzej Siewior.
+
+ -- Serafeim Zanikolas s...@debian.org Mon, 19 Jul 2010 01:16:20 +0200
+
d-shlibs (0.44) unstable; urgency=low
* Apply overrides before hardcoded quirks (in addition to afterwards
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: intent to NMU
Processing commands for cont...@bugs.debian.org: tags 584396 pending Bug #584396 [d-shlibs] unicap: FTBFS: devlibs error: There is no package matching [libx11--dev] and noone provides it, please report bug to d-shlibs maintainer Bug #581318 [d-shlibs] libgd2: FTBFS: devlibs error: There is no package matching [libx11--dev] and noone provides it, please report bug to d-shlibs maintainer Added tag(s) pending. Added tag(s) pending. tags 581318 pending Bug #581318 [d-shlibs] libgd2: FTBFS: devlibs error: There is no package matching [libx11--dev] and noone provides it, please report bug to d-shlibs maintainer Bug #584396 [d-shlibs] unicap: FTBFS: devlibs error: There is no package matching [libx11--dev] and noone provides it, please report bug to d-shlibs maintainer Ignoring request to alter tags of bug #581318 to the same tags previously set Ignoring request to alter tags of bug #584396 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 581318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581318 584396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584396 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#584348: marked as done (php5: FTBFS: cp: cannot create regular file `/build/user-php5_5.3.2-1-amd64-JiIO8n/php5-5.3.2/debian/libapache2-mod-php5/usr/bin/#i...@31393#': No such file or directory)
Your message dated Mon, 19 Jul 2010 01:02:45 +
with message-id e1oaekn-8n...@franck.debian.org
and subject line Bug#584348: fixed in php5 5.3.2-2
has caused the Debian Bug report #584348,
regarding php5: FTBFS: cp: cannot create regular file
`/build/user-php5_5.3.2-1-amd64-JiIO8n/php5-5.3.2/debian/libapache2-mod-php5/usr/bin/#i...@31393#':
No such file or directory
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.)
--
584348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: php5
Version: 5.3.2-1
Severity: serious
Tags: squeeze sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20100602 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
make[1]: Entering directory
`/build/user-php5_5.3.2-1-amd64-JiIO8n/php5-5.3.2/apache2-build'
Installing build environment:
/build/user-php5_5.3.2-1-amd64-JiIO8n/php5-5.3.2/debian/libapache2-mod-php5/usr/lib/php5/build/
Installing helper programs:
/build/user-php5_5.3.2-1-amd64-JiIO8n/php5-5.3.2/debian/libapache2-mod-php5/usr/bin/
program: phpize
cp: cannot create regular file
`/build/user-php5_5.3.2-1-amd64-JiIO8n/php5-5.3.2/debian/libapache2-mod-php5/usr/bin/#i...@31393#':
No such file or directory
program: php-config
Installing shared extensions:
/build/user-php5_5.3.2-1-amd64-JiIO8n/php5-5.3.2/debian/libapache2-mod-php5/usr/lib/php5/20090626/
Installing man pages:
/build/user-php5_5.3.2-1-amd64-JiIO8n/php5-5.3.2/debian/libapache2-mod-php5/usr/share/man/man1/
page: phpize.1
page: php-config.1
Installing header files:
/build/user-php5_5.3.2-1-amd64-JiIO8n/php5-5.3.2/debian/libapache2-mod-php5/usr/include/php5/
make[1]: Leaving directory
`/build/user-php5_5.3.2-1-amd64-JiIO8n/php5-5.3.2/apache2-build'
# remove netware and win32 headers that we don't want
cd debian/libapache2-mod-php5/usr/include/php5/ \
rm -f TSRM/readdir.h \
TSRM/tsrm_config.nw.h TSRM/tsrm_config.w32.h\
TSRM/tsrm_nw.h TSRM/tsrm_win32.h\
Zend/zend_config.nw.h Zend/zend_config.w32.h\
main/config.nw.h main/config.w32.h\
main/win95nt.h
# install PEAR
cp -a pear-build/* debian/php-pear/
# everything under usr/share/php/data except 'PEAR' is b0rken
# and actually needs to be fixed
[ ! -f debian/php-pear/usr/share/php/data/Structures_Graph/LICENSE ] || \
rm -f
debian/php-pear/usr/share/php/data/Structures_Graph/LICENSE
[ ! -f debian/php-pear/usr/share/php/doc/PEAR/INSTALL ] || \
rm -f debian/php-pear/usr/share/php/doc/PEAR/INSTALL
[ ! -f debian/php-pear/usr/share/php/doc/Structures_Graph/docs/generate.sh ]
|| \
rm -f
debian/php-pear/usr/share/php/doc/Structures_Graph/docs/generate.sh
for f in Structures_Graph/publish.sh Structures_Graph/package.sh \
Structures_Graph/genpackage.xml.pl; do \
rm -f debian/php-pear/usr/share/php/data/$f; \
done
# we don't want test suites
rm -f -r debian/php-pear/usr/share/php/test/
[ -d debian/php-pear/usr/share/php/doc ] { \
mkdir -p debian/php-pear/usr/share/doc/php5-common/PEAR; \
mv debian/php-pear/usr/share/php/doc/* \
debian/php-pear/usr/share/doc/php5-common/PEAR/; \
rm -f -r debian/php-pear/usr/share/php/doc; \
ln -s ../doc/php-pear/PEAR debian/php-pear/usr/share/php/doc; \
echo Dummy placeholder to prevent the directory's deletion \
debian/php-pear/usr/share/doc/php5-common/PEAR/.placeholder; \
}
# install extensions
ext=`./debian/libapache2-mod-php5/usr/bin/php-config --extension-dir`;\
for i in libapache2-mod-php5 libapache2-mod-php5filter php5-cgi
php5-cli; do \
mkdir -p debian/$i/${ext}; \
done; \
cat debian/modulelist debian/extramodulelist | while read package
extname dsoname; do \
if [ -z $dsoname ]; then dsoname=$package; fi; \
mkdir -p debian/php5-$package${ext}; \
chrpath debian/libapache2-mod-php5/${ext}/$dsoname.so; \
chrpath -d debian/libapache2-mod-php5/${ext}/$dsoname.so; \
install -m 644 -o root -g root \
debian/libapache2-mod-php5/${ext}/$dsoname.so \
debian/php5-$package${ext}/$dsoname.so;
Processed: re: poppler-utils: should not conflict with xpdf-utils 3.02-2
Processing commands for cont...@bugs.debian.org: severity 586620 serious Bug #586620 [poppler-utils] poppler-utils: should not conflict with xpdf-utils 3.02-2 Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 586620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586620 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#577513: libdbd-sybase-perl: DBI/DBD internal version mismatch
Hi,
Steve Langasek vor...@debian.org writes:
I've been postponing dealing with this bug, hoping that someone in the
Debian Perl Group would spontaneously provide a better interface for this
than the current one. The perl-dbdabi-* virtual package seems sensible
enough, but I'm not happy about including external makefiles in my
debian/rules. Could you please provide a dh_* command for this that adds
the value to the existing ${misc:Depends} variable?
A dh_perl_dbi command and a perl_dbi addon for dh have been included in
libdbi-perl_1.612-1. They add the required dependency to
${perl:Depends} (which is already used by dh_perl).
See also /usr/share/doc/libdbi-perl/README.Debian.
Also, why does libdbd-sybase-perl need to depend on *both* libdbi-perl *an*
perl-dbdabi-*, given that the latter is provided by the former? Depending
on libdbi-perl looks quite redundant to me.
I took that from Perl XS modules without too much thinking: dh_perl
usually adds a dependency on both perlapi-* and perl. But after
thinking some more, I agree with you: The case of XS modules is
different. There perlapi-* is provided by perl-base, but many modules
require functionality from the perl package.
I will remove the unversioned dependency on libdbi-perl that dh_perl_dbi
generates in the next upload.
Regards,
Ansgar
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583460: libmoose-policy-perl: FTBFS: tests failed
Hi, I just asked Florian about this bug and Moose-Policy is no longer recommended and EOLed. The package should be removed from Debian once liblatex-table-perl stops using it [1]. Regards, Ansgar [1] https://rt.cpan.org/Public/Bug/Display.html?id=59519 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583460: libmoose-policy-perl: FTBFS: tests failed
Hi Ansgar On Mon, Jul 19, 2010 at 02:05:29PM +0900, Ansgar Burchardt wrote: I just asked Florian about this bug and Moose-Policy is no longer recommended and EOLed. The package should be removed from Debian once liblatex-table-perl stops using it [1]. I'm going to look into liblatex-table-perl today, thanks for clearing this up! Bests Salvatore signature.asc Description: Digital signature
Processed: fixed 582946 in virtualbox-ose/3.2.0-1
Processing commands for cont...@bugs.debian.org:
fixed 582946 virtualbox-ose/3.2.0-1
Bug #582946 {Done: Felix Geyer debfx-...@fobos.de} [virtualbox-ose-dkms]
FATAL: Error inserting vboxnetflt : Invalid module format
The source virtualbox-ose and version 3.2.0-1 do not appear to match any binary
packages
Bug Marked as fixed in versions virtualbox-ose/3.2.0-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
582946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582946
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#562377: ifrit: FTBFS: make[3]: *** No rule to make target `/usr/lib/openmpi/lib/libmpi_cxx.so', needed by `/build/user-ifrit_3.2.8-1-amd64-Zd_ysf/ifrit-3.2.8/ifrit'. Stop.
On 24/12/09 at 11:44 +0100, Lucas Nussbaum wrote: Are you really sure you want to support building in parallel? Oops, apparently I was wrong on that, and that package doesn't support building in parallel. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
