Bug#543312: CVE-2009-2732: Basic Authentication Null Pointer Denial of Service

[Giuseppe Iuculano]

Package: ntop
Severity: serious
Tags: security

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hi,
the following CVE (Common Vulnerabilities & Exposures) id was
published for ntop.

CVE-2009-2732[0]:
| The checkHTTPpassword function in http.c in ntop 3.3.10 and earlier
| allows remote attackers to cause a denial of service (NULL pointer
| dereference and daemon crash) via an Authorization HTTP header that
| lacks a : (colon) character in the base64-decoded string.

If you fix the vulnerability please also make sure to include the
CVE id in your changelog entry.

For further information see:

[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2732
http://security-tracker.debian.net/tracker/CVE-2009-2732

Cheers,
Giuseppe.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqSNzUACgkQNxpp46476aqaRwCePEnRlTpotXKtcCnxSRnqbSoX
imEAnRKiKt/JAzk57KKzHsAMFEo/v66K
=DhPT
-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#543309: local socket clamav-milter.ctl unsafe - milter set to error state

[Mark Rushing]

Package: clamav-milter
Version: 0.95.2+dfsg-1~volatile1
Severity: grave
Justification: renders package unusable


clamav-milter installs an m4 macro in /etc/mail/m4/clamav-milter.m4

The installation documentation says to include this macro in your sendmail.mc 
file.

Doing so will result in clamav-milter not working, with errors for each 
incoming email, as follows:

Milter (clamav): local socket name /var/run/clamav/clamav-milter.ctl unsafe
Milter (clamav): to error state

This happens because the clamav-milter.m4 macro has the following line:

INPUT_MAIL_FILTER(`clamav', `S=local:/var/run/clamav/clamav-milter.ctl, F=, 
T=S:4m;R:4m')dnl

That line points to a non-existent socket. The actual socket name is, instead, 
'milter.ctl'.

The bug is fixed by changing the clamav-milter.m4 line to read instead:

INPUT_MAIL_FILTER(`clamav', `S=local:/var/run/clamav/milter.ctl, F=, 
T=S:4m;R:4m')dnl

Sorry, I've been meaning to report this for a long time - just getting tired of 
always having to correct it... ;)

Mark

-- Package-specific info:
--- configuration ---
Checking configuration files in /etc/clamav

Config file: clamd.conf
---
LogFile = "/var/log/clamav/clamav.log"
LogFileUnlock disabled
LogFileMaxSize disabled
LogTime = "yes"
LogClean disabled
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
PidFile = "/var/run/clamav/clamd.pid"
TemporaryDirectory disabled
DatabaseDirectory = "/var/lib/clamav"
LocalSocket = "/var/run/clamav/clamd.ctl"
FixStaleSocket = "yes"
TCPSocket disabled
TCPAddr disabled
MaxConnectionQueueLength = "15"
StreamMaxLength = "10485760"
StreamMinPort = "1024"
StreamMaxPort = "2048"
MaxThreads = "12"
ReadTimeout = "180"
CommandReadTimeout = "5"
SendBufTimeout = "200"
MaxQueue = "100"
IdleTimeout = "30"
ExcludePath disabled
MaxDirectoryRecursion = "15"
FollowDirectorySymlinks disabled
FollowFileSymlinks disabled
SelfCheck = "3600"
VirusEvent disabled
ExitOnOOM disabled
Foreground disabled
Debug disabled
LeaveTemporaryFiles disabled
User = "clamav"
AllowSupplementaryGroups = "yes"
DetectPUA disabled
ExcludePUA disabled
IncludePUA disabled
AlgorithmicDetection = "yes"
ScanPE = "yes"
ScanELF = "yes"
DetectBrokenExecutables disabled
ScanMail = "yes"
MailFollowURLs disabled
ScanPartialMessages disabled
PhishingSignatures = "yes"
PhishingScanURLs = "yes"
PhishingAlwaysBlockCloak disabled
PhishingAlwaysBlockSSLMismatch disabled
HeuristicScanPrecedence disabled
StructuredDataDetection disabled
StructuredMinCreditCardCount = "3"
StructuredMinSSNCount = "3"
StructuredSSNFormatNormal = "yes"
StructuredSSNFormatStripped disabled
ScanHTML = "yes"
ScanOLE2 = "yes"
ScanPDF = "yes"
ScanArchive = "yes"
ArchiveBlockEncrypted disabled
MaxScanSize = "104857600"
MaxFileSize = "26214400"
MaxRecursion = "16"
MaxFiles = "1"
ClamukoScanOnAccess disabled
ClamukoScanOnOpen disabled
ClamukoScanOnClose disabled
ClamukoScanOnExec disabled
ClamukoIncludePath disabled
ClamukoExcludePath disabled
ClamukoMaxFileSize = "5242880"
DevACOnly disabled
DevACDepth disabled

Config file: freshclam.conf
---
LogFileMaxSize disabled
LogTime disabled
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
PidFile = "/var/run/clamav/freshclam.pid"
DatabaseDirectory = "/var/lib/clamav/"
Foreground disabled
Debug disabled
AllowSupplementaryGroups disabled
UpdateLogFile = "/var/log/clamav/freshclam.log"
DatabaseOwner = "clamav"
Checks = "24"
DNSDatabaseInfo = "current.cvd.clamav.net"
DatabaseMirror = "db.local.clamav.net", "database.clamav.net", 
"db.us.clamav.net"
MaxAttempts = "5"
ScriptedUpdates = "yes"
CompressLocalDatabase disabled
HTTPProxyServer disabled
HTTPProxyPort disabled
HTTPProxyUsername disabled
HTTPProxyPassword disabled
HTTPUserAgent disabled
NotifyClamd = "/etc/clamav/clamd.conf"
OnUpdateExecute disabled
OnErrorExecute disabled
OnOutdatedExecute disabled
LocalIPAddress disabled
ConnectTimeout = "30"
ReceiveTimeout = "30"
SubmitDetectionStats disabled
DetectionStatsCountry disabled
SafeBrowsing disabled

Config file: clamav-milter.conf
---
LogFile disabled
LogFileUnlock disabled
LogFileMaxSize = "1048576"
LogTime disabled
LogSyslog = "yes"
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
PidFile = "/var/run/clamav/clamav-milter.pid"
TemporaryDirectory = "/tmp"
FixStaleSocket = "yes"
MaxThreads = "10"
ReadTimeout = "180"
Foreground disabled
User = "clamav"
AllowSupplementaryGroups = "yes"
MaxFileSize = "26214400"
ClamdSocket = "unix:/var/run/clamav/clamd.ctl"
MilterSocket = "/var/run/clamav/milter.ctl"
LocalNet disabled
OnClean = "Accept"
OnInfected = "Quarantine"
OnFail = "Defer"
RejectMsg disabled
AddHeader = "Replace"
Chroot disabled
Whitelist disabled
SkipAuthenticated disabled
LogInfected = "Off"

Software settings
-
Version: 0.95.2
Optional features supported: MEMPOOL IPv6 FRESHCLAM_DNS_FIX AUTOIT_EA06 BZIP2 
Database directory: /var/lib/clamav/
main.cld: version 51, sigs: 545035, built on Thu May 14 0

Bug#539867: FIxed by running as same userid of the compile jobs

[Dominique Brazziel]

Since the kernel build is running as root, I had to 
invoke the monitor with 'gksudo distccmon-gnome'
and now it's displaying the nice progress monitor.

Sorry for the noise, OK to close.




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542888: bind9 stops during upgrade. again.

[LaMont Jones]

On Mon, Aug 24, 2009 at 11:05:00AM +1000, Craig Sanders wrote:
> i've already mentioned bug #453765.

And interestingly, all of the code added when that was closed is still
there.  And the commit log really tells the story - upgrading BIND9 from
something older than 1:9.5.0.dfsg-2

Leave named running during update.

BIND can safely continue to run during the upgrade process, just restart it
in postinst if it is running.

Of course, we can't actually do anything about the prerm script currently
on the machine... :-(

Addresses-Debian-Bug: 453765
Signed-off-by: LaMont Jones 

OTOH, that commit lacks changes to not stop it on upgrade.

> an even better option is for the bind9 package to actually make some
> effort to minimise downtime by restarting after upgrade rather than
> stopping early and starting late.

And it would appear that I was misremembering - it must have been a
different package.

> and i can not fathom why there's so much resistance to just adding
> '--restart-after-upgrade' to the call to dh_installinit.  it's a very
> simple fix with no downside.

Pretty sure --restart-after-upgrade wasn't something I was aware of at
the time.

> it was fine for years before i reported the problem the first time in
> Dec 2007 (bug #453765), and has been fine since that bug was closed in
> June 2008 up until the recent change that re-introduced the bug.

Interestingly, I'm pretty sure it was "not fine" for the interim, given
the missing prerm code.

lamont



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagging 542888

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 
> 2.10.11ubuntu5.8.04.3
> tags 542888 + pending
Bug #542888 [bind9] bind9 stops during upgrade. again.
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#518839: marked as done (dibbler: FTBFS: invalid application of 'sizeof' to incomplete type)

[Debian Bug Tracking System]

Your message dated Mon, 24 Aug 2009 04:32:17 +
with message-id 
and subject line Bug#518839: fixed in dibbler 0.7.3-0.1
has caused the Debian Bug report #518839,
regarding dibbler: FTBFS: invalid application of 'sizeof' to incomplete type
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.)


-- 
518839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dibbler
Version: 0.7.1-2
Severity: serious

From my pbuilder build log:

...
[CC ] /Port-linux/lowlevel-linux.o
cc -DLINUX   -I ../include  -Wall -funsigned-char -O2 -pedantic 
-DMOD_CLNT_BIND_REUSE -I. -c lowlevel-
linux.c 
lowlevel-linux.c: In function 'sock_recv':
lowlevel-linux.c:501: error: invalid application of 'sizeof' to incomplete type 
'struct in6_pktinfo' 
lowlevel-linux.c:502: error: invalid application of 'sizeof' to incomplete type 
'struct in6_pktinfo' 
lowlevel-linux.c:532: error: dereferencing pointer to incomplete type
make[2]: *** [lowlevel-linux.o] Error 1
make[2]: Leaving directory `/tmp/buildd/dibbler-0.7.1/Port-linux'
make[1]: *** [commonlibs] Error 1
make[1]: Leaving directory `/tmp/buildd/dibbler-0.7.1'
make: *** [build-arch-stamp] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2
-- 
Daniel Schepler



--- End Message ---
--- Begin Message ---
Source: dibbler
Source-Version: 0.7.3-0.1

We believe that the bug you reported is fixed in the latest version of
dibbler, which is due to be installed in the Debian FTP archive:

dibbler-client_0.7.3-0.1_amd64.deb
  to pool/main/d/dibbler/dibbler-client_0.7.3-0.1_amd64.deb
dibbler-doc_0.7.3-0.1_all.deb
  to pool/main/d/dibbler/dibbler-doc_0.7.3-0.1_all.deb
dibbler-relay_0.7.3-0.1_amd64.deb
  to pool/main/d/dibbler/dibbler-relay_0.7.3-0.1_amd64.deb
dibbler-server_0.7.3-0.1_amd64.deb
  to pool/main/d/dibbler/dibbler-server_0.7.3-0.1_amd64.deb
dibbler_0.7.3-0.1.diff.gz
  to pool/main/d/dibbler/dibbler_0.7.3-0.1.diff.gz
dibbler_0.7.3-0.1.dsc
  to pool/main/d/dibbler/dibbler_0.7.3-0.1.dsc
dibbler_0.7.3.orig.tar.gz
  to pool/main/d/dibbler/dibbler_0.7.3.orig.tar.gz



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 518...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kumar Appaiah  (supplier of updated dibbler 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, 23 Aug 2009 21:47:29 -0500
Source: dibbler
Binary: dibbler-server dibbler-client dibbler-relay dibbler-doc
Architecture: source amd64 all
Version: 0.7.3-0.1
Distribution: unstable
Urgency: low
Maintainer: Tomasz Mrugalski 
Changed-By: Kumar Appaiah 
Description: 
 dibbler-client - portable DHCPv6 client
 dibbler-doc - documentation for Dibbler
 dibbler-relay - portable DHCPv6 relay
 dibbler-server - portable DHCPv6 server
Closes: 518839
Changes: 
 dibbler (0.7.3-0.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * New upstream release.
 + Fix build errors due to invalid sizeof applications.
   (Closes: #518839)
   * debian/control:
 + Standards Version updated to 3.8.3 (no changes needed).
Checksums-Sha1: 
 9b07fb313528a23b9d80a532ff2e9f0a62e780d6 1080 dibbler_0.7.3-0.1.dsc
 44c804ad228140eda5cdbc6f9e85e58dec5927e3 3723163 dibbler_0.7.3.orig.tar.gz
 7fc36253fd9863690c171fe70fde25b13a91f62b 16426 dibbler_0.7.3-0.1.diff.gz
 2677405dc595580b7e380ff25046248c3d385146 439986 
dibbler-server_0.7.3-0.1_amd64.deb
 fe04bbc91c893a4a27b085165a3e897d36ff8a50 390002 
dibbler-client_0.7.3-0.1_amd64.deb
 3c43ef2e35501be90c2dac0fbd8e382d88366e84 132746 
dibbler-relay_0.7.3-0.1_amd64.deb
 8029ba3a9d409c6afbd4a5df1d9dbe03fb08d489 1262784 dibbler-doc_0.7.3-0.1_all.deb
Checksums-Sha256: 
 5174dc08acc2277890e9815971c81364a67ebd2c4f0615fffb96a05d5bfa8da4 1080 
dibbler_0.7.3-0.1.dsc
 95553d25dbd465a3d39e6ac710ae6a98ac573249694f27e44811684855c20c88 3723163 
dibbler_0.7.3.orig.tar.gz
 bf66942599f6af47cc3ca0fe5a66f3ca3d7cc1f0da6a72f872280c3723f85f5e 16426 
dibbler_0.7.3-0.1.diff.gz
 472c1e4c5d6ced27b4e96c89279d4454666df82b165c2fe3938bfd40dec73acf 439986 
dibbler-server_0.7.3-0.1_amd64.deb
 b0816fcce70fa1d47e82d312f97c36098190ba993eb987fdf3b790b689e0fb7a 390002 
dibbler-client_0.7.3-0.1_amd64.deb
 f588e631311

Bug#543079: libimager-perl: FTBFS: failed tests

[Tony Cook]

On Sat, Aug 22, 2009 at 06:47:53PM +0200, Lucas Nussbaum wrote:
> > t/t104ppm.ok
> > t/t105gif.ok
> > 
> > #   Failed test 'reading multiple images from tiff'
> > #   at t/t106tiff.t line 315.
> > Use of uninitialized value in subroutine entry at t/t106tiff.t line 318.
> > Use of uninitialized value in subroutine entry at t/t106tiff.t line 318.
> > im2 is not of type Imager::ImgRaw at t/t106tiff.t line 318.
> > # Looks like you planned 213 tests but only ran 67.
> > # Looks like you failed 1 test of 67 run.
> > # Looks like your test died just after 67.
> > t/t106tiffdubious
> > Test returned status 255 (wstat 65280, 0xff00)
> > DIED. FAILED tests 67-213
> > Failed 147/213 tests, 30.99% okay
> > t/t107bmp.ok

Hi,

I'm the upstream author.

This appears to be change in behaviour for tifflib and is present in
the original non-Debian sources, eg.

#include 
#include 

int main(void) {
  TIFF *tif;
  int i, y;
  char buf[100] = "\0";

  tif = TIFFOpen("foo.tif", "w");
  if (!tif) {
fprintf(stderr, "Cannot create file\n");
return 1;
  }
  for (i = 0; i < 2; ++i) {
int bytes_pp;
TIFFSetField(tif, TIFFTAG_IMAGEWIDTH, 20);
TIFFSetField(tif, TIFFTAG_IMAGELENGTH, 20);
TIFFSetField(tif, TIFFTAG_SAMPLESPERPIXEL, 3);
TIFFSetField(tif, TIFFTAG_PLANARCONFIG, PLANARCONFIG_CONTIG);
bytes_pp = TIFFScanlineSize(tif);
for (y = 0; y < 20; ++y) {
  TIFFWriteScanline(tif, buf, y, 0);
}
TIFFWriteDirectory(tif);
  }
  TIFFClose(tif);
  
  return 0;
}

gcc -otifdirtest tiffdirtest.c -ltiff
./tiffdirtest
tiffdump foo.tif | grep StripByteCounts

# Etch:
StripByteCounts (279) LONG (4) 1<160>
StripByteCounts (279) LONG (4) 1<160>

# Sid:
StripByteCounts (279) LONG (4) 1<0>
StripByteCounts (279) LONG (4) 1<0>

# original libtiff 3.9.0
(using LD_LIBRARY_PATH=/home/tony/local/tiff/lib ./tiffdirtest with tiffdirtest 
builting against an installed tifflib 3.9.0):
StripByteCounts (279) LONG (4) 1<0>
StripByteCounts (279) LONG (4) 1<0>

>From the Imager side of things, the single image function *doesn't*
produce the problem StripByteOffsets - and the only real difference
between that and the multiple image writer is the call to
TIFFWriteDirectory for each image in the multi-image code.






-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#499569: marked as done (gnupg-agent: modifies SigBlk mask of all processes spawned in the X session breaking unrelated software [i386 only?])

[Debian Bug Tracking System]

Your message dated Mon, 24 Aug 2009 01:17:11 +
with message-id 
and subject line Bug#499569: fixed in gnupg2 2.0.12-1
has caused the Debian Bug report #499569,
regarding gnupg-agent: modifies SigBlk mask of all processes spawned in the X 
session breaking unrelated software [i386 only?]
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.)


-- 
499569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnupg-agent
Version: 2.0.9-3
Severity: critical

gnupg-agent somehow manages to change the SigBlk mask causing all child
processes that are spawned part of the X session to have the SigBlk
mask set causing real-time signals to be blocked. This breaks all
applications spawned in that X session that rely on
real-time signals.

As this breaks unrelated software I set the severity to critical.

Here the summary of my full investigation:
About 2 months ago I started to suffer from an issue that first looked
like a bug in Mono's threading implementation. The test-case to
reproduce it looks like this:

Attachment:
test-thread-abort.cs

Compile:
mcs test-thread-abort.cs

Run:
mono test-thread-abort.exe

My output:
thread.Start()
Worker(): thread started
Worker(): working... 0
Worker(): working... 1
Worker(): working... 2
Worker(): working... 3
Worker(): working... 4
thread.Abort()
press enter to quit!
Worker(): working... 5
Worker(): working... 6
Worker(): working... 7
Worker(): working... 8
Worker(): working... 9
Worker(): working... 10
Worker(): working... 11
Worker(): working... 12
(continuing forever -> killed using ^C)

The expected output:
thread.Start()
Worker(): thread started
Worker(): working... 0
Worker(): working... 1
Worker(): working... 2
Worker(): working... 3
Worker(): working... 4
thread.Abort()
press enter to quit!
Worker(): thread aborted!
Worker(): thread ended

The thread was never aborted and thus forever continued on my system.
After more investigation in Mono's threading implementation I found
that it uses real-time signals to control the threads. A strace then
showed that the signal (SIGRT1) was send but never received This
made me really curious.

So I wrote a C test-case for this issue, which looks like this:

Attachment:
test-signal.c

Compile:
gcc test-signal.c -o test-signal

Run:
./test-signal

My Output:
SIGRTMIN: 34
sigismember(): 1
SIGRTMIN is blocked, trying to unblock...done.
sigismember(): 0
SIGRT_1 received
SIGRT_2 received
SIGQUIT received

The expected output:
SIGRTMIN: 34
sigismember(): 0
SIGRT_1 received
SIGRT_2 received
SIGQUIT received

And that proved the signal (SIGRT) is indeed already blocked when the
application is started.

Then I found out / learned that blocking signals is a feature and the
SigBlk mask is inherited to child processes. So something was setting
this mask, and I could not find out what it was till today.

I reinstalled my system (1 week ago) after I could not find the exact
cause of this issue (after 3 continuous days of investigation)
and today it started to happen again, after I was sponsoring a package
upload, for which I had to install pscd and gnupg-agent to get my
crypto card working again (after the reinstall).

Then I disabled the gpg-agent in my ~/.gnupg/gpg.conf, restarted my X
session and viola SigBlk mask is back to normal and all my lovely
applications work again like they should.

Enabling the gpg-agent in ~/.gnupg/gpg.conf again brings the issue back.

I noticed the gpg-agent is started in /etc/X11/Xsession.d/90gpg-agent,
but I no have no idea how it manages to change (or rather inherits) the
SigBlk mask of other processes spawned in the X session

Here also a little detection script I wrote to identify processes with
that set SigBlk mask (it also finds some "false-positives" as some apps
really need that mask, but not _all_ processes launched under the X
session!)

Attachment:
proc-sigblk.sh:

My output:
Name:   x-session-manag
Pid:21699
Uid:1000100010001000
Gid:1000100010001000
Name:   dbus-launch
Pid:21757
Uid:1000100010001000
Gid:1000100010001000
Name:   dbus-daemon
Pid:21758
Uid:1000100010001000
Gid:1000100010001000
Name:   seahorse-agent
Pid:21764
Uid:1000100010001000
Gid:1000100010001000
Name:   gnome-settings-
Pid:21769
Uid:1000100010001000
Gid:1000100010001000
Name:   metacity
Pid:21781
Uid:1000100010001000
Gid:1000100010001000
Name:

Bug#542888: bind9 stops during upgrade. again.

[Craig Sanders]

On Sun, Aug 23, 2009 at 06:00:11PM -0600, LaMont Jones wrote:
> On Mon, Aug 24, 2009 at 07:47:59AM +1000, Craig Sanders wrote:
> > i'm talking about a network being disrupted, not a single host. the
> > hosts DON'T have 127.0.0.1 in resolv.conf, they have the namesever.
>
> I've gone back as far as 9.2.4, and haven't found anywhere that the
> bind9 package actually kept itself from stoping bind9 during the
> upgrade.  I do know that bind 8 had code in the scripts to do that.

i've already mentioned bug #453765.

that bug was closed on Fri, 13 Jun 2008 16:54:42 -0600 with the
following message signed by you:

 * Leave named running during update.  Closes: #453765


> > > It's not critical severity - normal or wishlist would be more
> > > appropriate.
> >
> > it is critical. it breaks functionality for the entire local
> > network.
>
> Generally what I've seen done is a separate IP for the resolver, and
> during a scheduled upgrade, that IP is migrated to another host,
> specifically to avoid any disruption.

why jump through such bizarrely complicated and dangerous hoops to avoid
a non-problem?

bind9 has never had a single demonstrated problem with
restart-after-upgrade.

and what do you do if you're ssh-ed in to that machine on that IP
address? you can't change it, otherwise you kill your ssh connection.

(BTW, ssh along with pppd are the two classic examples of why it's
a really bad idea to stop-before-upgrade and start-after instead of
restart-after. for those packages, that not only maximises downtime
it can prevent logging in to fix any errors. named can too, if
hosts.allow/hosts.deny are configured to reject ssh from unknown
hostnames or to only allow connections from your domain).


> > it's not a matter of convenience. it's a matter of temporarily
> > breaking everything on the network that depends on DNS (which is
> > pretty much every network service or connection).
>
> Everything on the network that depends on this host for DNS.

which is, as i said, pretty much every network service or connection.

> Migrating the service to another host for the duration of the upgrade,
> or doing micro upgrades is certainly an option.

an even better option is for the bind9 package to actually make some
effort to minimise downtime by restarting after upgrade rather than
stopping early and starting late.

I'm still waiting to hear of any of the alleged problems caused by
restarting after upgrade that have been alluded to and hinted at
so mysteriously. so far, not one has even been theorised let alone
demonstrated to have happened.


and i can not fathom why there's so much resistance to just adding
'--restart-after-upgrade' to the call to dh_installinit.  it's a very
simple fix with no downside.


> > the bind9 package has worked reliably for many years with a restart
> > after upgrade rather than stop-early, start-late approach. there is no
> > reason for the current change in behaviour. it just maximises downtime.
> 
> Versions?

i don't know the version numbers, nor do i have an archive of every
historical release of the bind9 package to go searching through. i can
give you approximate dates instead:

it was fine for years before i reported the problem the first time in
Dec 2007 (bug #453765), and has been fine since that bug was closed in
June 2008 up until the recent change that re-introduced the bug.

craig

-- 
craig sanders 



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagging 542265

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # fixed by c2f59e0
> tags 542265 pending
Bug #542265 [logcheck-database] logcheck-database: ignore.d.server/sendmail 
conflicts with sendmail-base
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542265: sendmail-base and logcheck-database: error when trying to install together

[Frédéric Brière]

Here's the commit I made to allow removing conffiles in the future.
(Specific filenames were added in later commits.)  It's rather
straightforward (mostly copied from the Debian wiki), but I wouldn't
mind peer review just in case I screwed up.

As mentioned in the description, I decided to eschew the whole version
comparison bit.  Unlike most packages, we're likely to drop many more
conffiles in the future, and I wanted to come up with an easy solution
that would not result in a dozen of if/then blocks, or figuring out
which version to check for every time.

When you remove a rule files, all you have to do is remember to add it
to the list.  That's it!


commit 1299e472ce3f8cf26fa60c87ce0c5d541106e0ef
Author: Frédéric Brière 
Date:   Sun Aug 23 15:48:25 2009 -0400

Adding support for removing conffiles in logcheck-database's preinst

This basically copies rm_conffile() from the Debian wiki, to deal with
the fact that dpkg does not delete conffiles after they have been
removed from a package.

This version of rm_conffile() makes sure that the conffile still belongs
to our package, since it is possible for it to have migrated to another
package through a Replaces relationship.  (See bug #532484 for an
example.)

Thanks to this check, we can also avoid bothering with version
comparisions; calling rm_conffile() on subsequent upgrades will simply
do nothing.  (Of course, we still avoid calling it uselessly on fresh
installs.)

diff --git a/debian/logcheck-database.preinst b/debian/logcheck-database.preinst
index 3ff092e..c2d6589 100644
--- a/debian/logcheck-database.preinst
+++ b/debian/logcheck-database.preinst
@@ -14,8 +14,48 @@ set -e
 # the debian-policy package
 
 
+# List of conffiles which have been removed from this package.  These will be
+# deleted (or backed away) at the next upgrade.
+#
+# Conffiles must be listed here from the very moment of their removal; adding
+# them later on will not work correctly.
+
+REMOVED_CONFFILES=""
+
+
+# Copied from 
+rm_conffile() {
+local PKGNAME="$1"
+local CONFFILE="$2"
+
+[ -e "$CONFFILE" ] || return 0
+
+# Do nothing if that file no longer belongs to us
+dpkg-query --listfiles "$PKGNAME" | grep -q "^$CONFFILE$" || return 0
+
+local md5sum="$(md5sum $CONFFILE | sed -e 's/ .*//')"
+local old_md5sum="$(dpkg-query -W -f='${Conffiles}' $PKGNAME | \
+sed -n -e "\' $CONFFILE ' { s/ obsolete$//; s/.* //; p }")"
+if [ "$md5sum" != "$old_md5sum" ]; then
+echo "Obsolete conffile $CONFFILE has been modified by you."
+echo "Saving as $CONFFILE.dpkg-bak ..."
+mv -f "$CONFFILE" "$CONFFILE".dpkg-bak
+else
+echo "Removing obsolete conffile $CONFFILE ..."
+rm -f "$CONFFILE"
+fi
+}
+
+
 case "$1" in
 install|upgrade)
+# Remove $REMOVED_CONFFILES on upgrade, or when re-installing
+# after the package was removed (but not purged).
+if [ "$2" ]; then
+for CONFFILE in $REMOVED_CONFFILES; do
+rm_conffile logcheck-database "$CONFFILE"
+done
+fi
 ;;
 
 abort-upgrade)

-- 
* liw prefers not to have Linus run Debian, because then /me would
  have to run Red Hat, just to keep the power balance :)
-- #Debian



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#543025: cjk: FTBFS: cp: cannot stat `/usr/share/texmf/fonts/afm/public/thai/{garuda,norasi}*.afm': No such file or directory

[韓達耐]

Oops, looks like a bashism here.

I'll fix it in the SVN tomorrow and upload a new package.  Thanks for
the report!

-- 
Danai



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: bug forward to upstream

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 540679 http://bugzilla.xorp.org/show_bug.cgi?id=1092
Bug #540679 [xorp] xorp: FTBFS: error: cast from 'uint8_t*' to 'ArpHeader*' 
increases required alignment of target type
Set Bug forwarded-to-address to 'http://bugzilla.xorp.org/show_bug.cgi?id=1092'.
> --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#540973: Bug 540973 not fixed !

[Ondřej Surý]

On Mon, Aug 24, 2009 at 01:33, John D. Rowell wrote:
> Hi Ondřej,
>
> 2009/8/23 Ondřej Surý 
>>
>>  John,
>>
>> could you please add libdns50 version and dependencies to the bug
>> report, please? Again you can just add reportbug
>
> The original bug report _is_ from reportbug. Here's the libdns50 line:
>
> ii  libdns50   1:9.6.1.dfsg.P1-1 DNS Shared Library used by BIND
>
> Do you mean you'd like to get a "reportbug libdns50" instead of a "reportbug
> bind9"?

Yep, I meant that. Sorry for not being clear. reportbug doesn't do
recursive dependencies, and the link failure is between libdns.so.50
and libGeoIP.so.1.

So it would be better to know what version of libgeoip1 have you installed.

>> Also maybe objdump -T on libGeoIP.so.1 could be helpful, mine does
>> include needed symbol, does yours?
>>
>> # objdump -T libGeoIP.so.1.4.6 | grep GeoIP_country_name_by_ipnum_v6
>> 51d0 g    DF .text  0050  Base
>>  GeoIP_country_name_by_ipnum_v6
>
> My lib also contains the symbol, I have no idea why it is not found by the
> other libs:
>
> yoda:~# objdump -T /usr/lib/libGeoIP.so.1.4.6 | grep
> GeoIP_country_name_by_ipnum_v6
> 5190 g    DF .text  0050  Base    GeoIP_country_name_by_ipnum_v6
>
> I haven't rebooted the machine (for obvious reasons), maybe there's some
> other process that's keeping and older version of the lib in shared memory
> with the same version/signature as the "new" lib? Any tools to check that?

lsof /usr/lib/libGeoIP.so.1
or
lsof /usr/lib/libGeoIP.so.1.4.6

Also you can try:

lsof +L1 (which lists unlinked, but still used files)

> The problem does indeed seem to persist as more ppl are reporting it, and
> for each person who reports it there's usually at least 10 or 100 that don't
> bother. Maybe it only happens on 32bit systems.

Nope, my 32-bit as well as 64-bit chroot runs named just fine. But I
am using unstable pbuilder chroots. so something maybe rotten in
testing.

Are you able to test again on your box? Could you do:

# ldd /usr/lib/libdns.so.50
and
# ldd /usr/sbin/named

when it's not working?

Also maybe running

strace named -g

could give us some hints.

And finally does manually updating libgeoip1 to latest version from
unstable help?

Ondrej
-- 
Ondřej Surý 
http://blog.rfc1925.org/



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542810: [Bacula-devel] Sqlite3 and autoincrement

[Sven Hartge]

Kern Sibbald wrote:

> Based on the information you provided below, I have reopened the bug report 
> and posted my suggested fix.  Sorry that I missed the fact that the Bacula 
> developers added the offending "AUTOINCREMENT".  I would appreciate a 
> confirmation to the bug report whether or not my suggested fix works.

I will be able to test these fixes this Monday.

But since I came to the same conclusion WRT sed as you did (see
), I am
positive this should work as intended.

Grüße,
Sven.




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542888: bind9 stops during upgrade. again.

[LaMont Jones]

On Mon, Aug 24, 2009 at 07:47:59AM +1000, Craig Sanders wrote:
> i'm talking about a network being disrupted, not a single host.
> the hosts DON'T have 127.0.0.1 in resolv.conf, they have the namesever.

I've gone back as far as 9.2.4, and haven't found anywhere that the
bind9 package actually kept itself from stoping bind9 during the
upgrade.  I do know that bind 8 had code in the scripts to do that.

> > It's not critical severity - normal or wishlist would be more
> > appropriate.
> it is critical.  it breaks functionality for the entire local network.

Generally what I've seen done is a separate IP for the resolver, and
during a scheduled upgrade, that IP is migrated to another host,
specifically to avoid any disruption.

> it's not a matter of convenience. it's a matter of temporarily breaking
> everything on the network that depends on DNS (which is pretty much
> every network service or connection).

Everything on the network that depends on this host for DNS.  Migrating
the service to another host for the duration of the upgrade, or doing
micro upgrades is certainly an option.

> the bind9 package has worked reliably for many years with a restart
> after upgrade rather than stop-early, start-late approach. there is no
> reason for the current change in behaviour. it just maximises downtime.

Versions?

lamont



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#540973: Bug 540973 not fixed !

[John D. Rowell]

Hi Ondřej,

2009/8/23 Ondřej Surý 

>  John,
>
> could you please add libdns50 version and dependencies to the bug
> report, please? Again you can just add reportbug


The original bug report _is_ from reportbug. Here's the libdns50 line:

ii  libdns50   1:9.6.1.dfsg.P1-1 DNS Shared Library used by BIND

Do you mean you'd like to get a "reportbug libdns50" instead of a "reportbug
bind9"?

Also maybe objdump -T on libGeoIP.so.1 could be helpful, mine does
> include needed symbol, does yours?
>
> # objdump -T libGeoIP.so.1.4.6 | grep GeoIP_country_name_by_ipnum_v6
> 51d0 gDF .text  0050  Base
>  GeoIP_country_name_by_ipnum_v6


My lib also contains the symbol, I have no idea why it is not found by the
other libs:

yoda:~# objdump -T /usr/lib/libGeoIP.so.1.4.6 | grep
GeoIP_country_name_by_ipnum_v6
5190 gDF .text  0050  BaseGeoIP_country_name_by_ipnum_v6

I haven't rebooted the machine (for obvious reasons), maybe there's some
other process that's keeping and older version of the lib in shared memory
with the same version/signature as the "new" lib? Any tools to check that?

The problem does indeed seem to persist as more ppl are reporting it, and
for each person who reports it there's usually at least 10 or 100 that don't
bother. Maybe it only happens on 32bit systems.

Cheers,
jd

Bug#543263: marked as done (blcr_0.8.2-2 FTBFS on sparc (dist=unstable))

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 22:32:12 +
with message-id 
and subject line Bug#543263: fixed in blcr 0.8.2-3
has caused the Debian Bug report #543263,
regarding blcr_0.8.2-2 FTBFS on sparc (dist=unstable)
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.)


-- 
543263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: blcr
Version: 0.8.2-2
Severity: serious

> checking for value of CR_ASM_OP_HAND_CHKPT... 2147787009
> checking for value of CR_ASM_CHECKPOINT_STUB... 16384
> checking for value of CR_ASM_OP_HAND_ABORT... 2147787010
> checking for value of CR_ASM_CHECKPOINT_OMIT... 4
> checking for value of CR_ASM_SI_PID_OFFSET... 12
> checking for value of CR_ASM_NR_ioctl... 54
> checking for value of CR_ASM_NR_rt_sigreturn... 101
> checking for direction of stack growth... down
> checking for value of CR_SIGNUM... 64
> checking for void *... (cached) yes
> checking size of void *... (cached) 4
> configure: error: --enable-multilib not supported on architecture sparc
> make: *** [build-arch-stamp] Error 1
> dpkg-buildpackage: error: debian/rules build gave error exit status 2


--- End Message ---
--- Begin Message ---
Source: blcr
Source-Version: 0.8.2-3

We believe that the bug you reported is fixed in the latest version of
blcr, which is due to be installed in the Debian FTP archive:

blcr-source_0.8.2-3_all.deb
  to pool/main/b/blcr/blcr-source_0.8.2-3_all.deb
blcr-util_0.8.2-3_i386.deb
  to pool/main/b/blcr/blcr-util_0.8.2-3_i386.deb
blcr_0.8.2-3.diff.gz
  to pool/main/b/blcr/blcr_0.8.2-3.diff.gz
blcr_0.8.2-3.dsc
  to pool/main/b/blcr/blcr_0.8.2-3.dsc
libcr-dev_0.8.2-3_i386.deb
  to pool/main/b/blcr/libcr-dev_0.8.2-3_i386.deb
libcr0_0.8.2-3_i386.deb
  to pool/main/b/blcr/libcr0_0.8.2-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 543...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alan Woodland  (supplier of updated blcr 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, 23 Aug 2009 21:59:41 +0100
Source: blcr
Binary: blcr-util blcr-source libcr0 lib32cr0 libcr-dev
Architecture: source all i386
Version: 0.8.2-3
Distribution: unstable
Urgency: low
Maintainer: Alan Woodland 
Changed-By: Alan Woodland 
Description: 
 blcr-source - Source for the blcr kernel modules
 blcr-util  - Userspace tools to Checkpoint and Restart Linux processes
 lib32cr0   - (32bit) Libraries to Checkpoint and Restart Linux processes
 libcr-dev  - Development files for BLCR
 libcr0 - Libraries to Checkpoint and Restart Linux processes
Closes: 542643 543263
Changes: 
 blcr (0.8.2-3) unstable; urgency=low
 .
   * Disabled multilib on SPARC (Closes: #543263)
   * Patched configure to look for sys_open instead of _end when testing
 System.map validity (Closes: #542643)
   * Reduced depends on module package to recommends. (It will behave sanely)
   * Re-ran autoreconf
Checksums-Sha1: 
 319ca895559aa4932637e60739c47195c23e0a67 1146 blcr_0.8.2-3.dsc
 4609c156d9cd7175efa7645c6681b3eadffb5525 639936 blcr_0.8.2-3.diff.gz
 785bfcea1f16fc2c8d8f1d4958eddf42d90a9097 705238 blcr-source_0.8.2-3_all.deb
 d9e8ef569d4a69374569d7a7e10db6c0f876de6a 39306 blcr-util_0.8.2-3_i386.deb
 c14f600c4fd05319820adb3a65249bb10da56be8 29806 libcr0_0.8.2-3_i386.deb
 590af7c23347b76b6943656ab69ac30a6df47aa6 40714 libcr-dev_0.8.2-3_i386.deb
Checksums-Sha256: 
 139fca989a366387aea828df6c20a5e2e6804154a8aa5763f767bca7b14478cd 1146 
blcr_0.8.2-3.dsc
 dfd5725abae504b04790021f607e7dd92a622512939d981002812920e73f3063 639936 
blcr_0.8.2-3.diff.gz
 6eb8a096c274c63c0d49d25da7f4f5eb1f0c046d29b7e9d2241c97844cfa3d7e 705238 
blcr-source_0.8.2-3_all.deb
 570bee64789d07cf1b0df10012f5d46ab29098ab7a78754a0012bf6262edcb1f 39306 
blcr-util_0.8.2-3_i386.deb
 186dd13d77793d8805f50b99960c63453f2e73c8be3e0793363d71cc8eeb36a9 29806 
libcr0_0.8.2-3_i386.deb
 24d053824b63e927850aa649f086988b20991ad6cac618abb52346185a545eba 40714 
libcr-dev_0.8.2-3_i386.deb
Files: 
 c7514973f78ec9c3f7248835db5bb6f7 1146 misc optional blcr_0.8.2-3.dsc
 2902325ed84e09fd9961804961c8162d 639936 misc optional blcr_0.8.2-3.diff.gz
 d8c2ea2899effdeece896af34d385032 705238 misc optio

Bug#542888: bind9 stops during upgrade. again.

[Craig Sanders]

On Mon, Aug 24, 2009 at 12:33:56AM +0200, Ond??ej Surý wrote:
> While I don't exactly share LaMont's reasoning on this bug (LaMont:
> even if you do upgrade daemons separately, underlying libraries will
> change anyway while the daemon is running, so you need another restart
> anyway when libraries change), I do agree that it's much safer just to
> stop the deamon, install new version of bind9 and library
> dependencies, and after that to run it again.

instead of alluding to mysterious and unspecified failures that *might*
happen if a daemon like bind9 is restarted in the postinst rather than
stopped early and started later, how about actually giving some concrete
examples of those failures?

name some real problems that prove that it is less safe to restart after
an upgrade than stop before, start after.

and then prove that those problem(s) (if they even exist) are worse 
than taking down DNS for the entire duration of the upgrade.


whenever this issue comes up for any daemon, there's *always* some
hand-waving about the horrible problems that might happen, but never
even one single factual example.

contrast that to the actual problems that have been described (and
experienced) when the name-server is killed early and started later.

a real-world, factual problem that actually happens beats a
hypothetical, never-yet-been-demonstrated problem every time.


craig

-- 
craig sanders 



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#515254: marked as done (cheops: Depends on legacy GTK 1.2 libs)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 23:44:19 +0100
with message-id <1251067459.927401.9175.nullmai...@kmos.homeip.net>
and subject line Package cheops has been removed from Debian
has caused the Debian Bug report #515254,
regarding cheops: Depends on legacy GTK 1.2 libs
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.)


-- 
515254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cheops
Severity: serious

cheops build-depends on libgtk1.2-dev, which will be removed for Squeeze.

Please port it to use GTK 2 or request it's removal.

Cheers,
Moritz

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-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 cheops depends on:
ii  libc6 2.7-18 GNU C Library: Shared libraries
ii  libglib1.2ldbl1.2.10-19  The GLib library of C routines
pn  libgtk1.2  (no description available)
pn  libsnmp15  (no description available)
ii  libx11-6  2:1.1.5-2  X11 client-side library
ii  libxext6  2:1.0.4-1  X11 miscellaneous extension librar
ii  libxi62:1.1.4-1  X11 Input extension library
ii  xterm 239-1  X terminal emulator

cheops recommends no packages.

Versions of packages cheops suggests:
pn  vncviewer  (no description available)


--- End Message ---
--- Begin Message ---
Version: 0.61-15.1+rm

You filled the bug http://bugs.debian.org/515254 in Debian BTS
against the package cheops. I'm closing it at *unstable*, but it will
remain open for older distributions.

For more information about this package's removal, read
http://bugs.debian.org/539041. That bug might give the reasons why
this package was removed and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues

--- End Message ---

Bug#543291: octave3.0-headers: will not install on squeeze

[Jameson Graef Rollins]

Package: octave3.0-headers
Version: 3.0.5-6+b1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The package appears to have incompatible dependencies for squeeze:

servo:~ 0$ apt-cache policy gcc-4.3
gcc-4.3:
  Installed: 4.3.4-1
  Candidate: 4.3.4-1
  Version table:
 *** 4.3.4-1 0
500 http://debian.lcs.mit.edu testing/main Packages
200 http://ftp.us.debian.org unstable/main Packages
100 /var/lib/dpkg/status
servo:~ 0$ sudo apt-get install octave3.0-headers
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.
  octave3.0-headers: Depends: gcc-4.3 (< 4.3.4) but 4.3.4-1 is to be installed
 Depends: g++-4.3 (< 4.3.4) but 4.3.4-1 is to be installed
 Depends: gfortran-4.3 (< 4.3.4) but 4.3.4-1 is to be 
installed
E: Broken packages
servo:~ 100$ 

This is clearly related to #541444 (I assume).

Thanks.  Hopefully this can get cleared up soon, because I would
really like to use this package.  Unfortunately the alternative,
octave3.2, is also unavailable because of the similar bug above.

jamie.

- -- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages octave3.0-headers depends on:
ii  g++4:4.3.3-9 The GNU C++ compiler
ii  g++-4.34.3.4-1   The GNU C++ compiler
ii  gcc4:4.3.3-9 The GNU C compiler
ii  gcc-4.34.3.4-1   The GNU C compiler
ii  gfortran   4:4.3.3-9 The GNU Fortran 95 compiler
ii  gfortran-4.3   4.3.4-1   The GNU Fortran 95 compiler
ii  libblas-dev1.2-2 Basic Linear Algebra Subroutines 3
ii  libfftw3-dev   3.1.2-3.1 library for computing Fast Fourier
ii  libhdf5-serial-dev 1.6.6-4+b1Hierarchical Data Format 5 (HDF5) 
ii  liblapack-dev  3.2.1-1   library of linear algebra routines
ii  libncurses5-dev5.7+20090803-1+b1 developer's libraries and docs for
ii  libreadline5-dev   5.2-5 GNU readline and history libraries
ii  octave3.0  1:3.0.5-6+b1  GNU Octave language for numerical 

octave3.0-headers recommends no packages.

octave3.0-headers suggests no packages.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJKkcSIAAoJEO00zqvie6q8wDQQAKFRLNfzEHoxCN4tpKV+Lb6q
WtG9/WH3R3leT/E3QLdh3CJRMgqMAnmiFWFoPKeAELI4f1JaLWeW/TRZ367BDHSl
qdScgZto8E2dLGPSN2kpIZHQpezb5jBthaVCunQ/ElGf02ciS/ZnG7NpHLdbdc9y
ds5kw1+a1K2a0ZMNHwtqbYYPB4SzMYvnIfximuOVe4XTM6//zoGDUhgQoT42sanO
RexmRNswDG1hH3urn4VgpehkcwqNTxqDzDDBetBsxZB2hRmkIVcQ4Ri0gMzt3Ppi
H2F+7KzJpfG/g5IvbKiVtGwLkjXvj8mb9m+UW7hSRNUZ6sdv3+Q/UkszpkUBn1kq
FUZlLQ4b9SO9t1Qwc5n4JioLNAeR+7sDEtrBhclPNyoDMP1qpYuEUEObsC3kwXv/
xW53g7+FLlRBM1EETS1xLcKgEqkA/0ZfoNDkHO67biNNSJk6E8JLpd/b6QiE+fTJ
U7O/XnTjEEZN4fpVlmurYaXpbNhR50EZ7htoE/cwnfW9Dz4svhFIgzl31n78REf7
rIl8rUoM5ah/dRJthbAMS/ANwgxf0eMfeRcJuhW/Kk/ytbmkmPZgFMUYzHb6/3K/
hbAs4suLPwhs8gNZ7ok+TlhNCfywiByn0erca4SjPlnPrduwj9pYX8mbySgQti0o
0r9i0/1n4kxLP3gT4WMS
=2G0E
-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#542888: bind9 stops during upgrade. again.

[Ondřej Surý]

On Sun, Aug 23, 2009 at 23:47, Craig Sanders wrote:
> On Sun, Aug 23, 2009 at 01:56:18PM +0200, Ond??ej Surý wrote:
>> > a working nameserver is a core, essential component of a functioning
>> > network. while named is down, *everything* on the network that uses that
>> > nameserver ceases to function correctly.
>>
>> That's why you should never have only one "nameserver 127.0.0.1" in
>> your /etc/resolv.conf. Configure one or two more remote nameservers
>> and you're done.
>
> i'm talking about a network being disrupted, not a single host.
>
> the hosts DON'T have 127.0.0.1 in resolv.conf, they have the namesever.
>
>> It's not critical severity - normal or wishlist would be more
>> appropriate.
>
> it is critical.  it breaks functionality for the entire local network.
>
>> While I agree that it's not very convenient to have bind9 stopped for
>> longer time periods, there are other ways how to prevent this kind of
>
> it's not a matter of convenience. it's a matter of temporarily breaking
> everything on the network that depends on DNS (which is pretty much
> every network service or connection).
>
>
>> outage. And it's entirely different from f.e. quagga, where restart
>> could mean loss of connectivity at all. Which clearly doesn't happen
>> with bind - you just loose ability to resolv DNS, when you have only
>> one nameserver configured.
>
> actually, there are multiple nameservers on the network. it doesn't help
> as much as you might think. most, if not all, client resolver libraries
> try nameservers in series, not in parallel. they don't try the second
> or third resolver until the first times out. for some services, the DNS
> timeout is longer than the connection or authentication timeout.
>
> clearly you have no experience of dozens or hundreds of users

and clearly you know nothing about me and you are just making angry
comment. please refrain yourself of doing so next time.

> whinging at you saying "the internet isn't working" or "the
> file-server/intranet/web site/etc is dead" because the first nameserver
> in their dhcp-assigned resolv list is down and the NEXT nameserver isn't
> queried until the first times out.

current timeout in resolv.conf is set to 5 seconds, either set this to
lower value (if you can control the hosts), or don't upgrade the
server while many users are using it (that's why we do usually do
upgrades at night hours), or run some H-A solution like heartbeat or
ucarp.

> even if, for example, their browser has the intranet's IP cached, the
> users still can't to the intranet because the login scripts can't find
> the ldap server.
>
> DNS is not just a convenience, it's a fundamental service that
> everything else on the network depends on.

Yes, and that's the reason why you should not just run apt-get update
&& apt-get upgrade, but prepare for DNS service upgrade, if you need
to keep it running all the time.

While I don't exactly share LaMont's reasoning on this bug (LaMont:
even if you do upgrade daemons separately, underlying libraries will
change anyway while the daemon is running, so you need another restart
anyway when libraries change), I do agree that it's much safer just to
stop the deamon, install new version of bind9 and library
dependencies, and after that to run it again.

Ondrej
-- 
Ondřej Surý 
http://blog.rfc1925.org/



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#540973: Bug 540973 not fixed !

[Ondřej Surý]

Stéphane,

What keeps you from reopening the bug with more information? You know
"me too" messages are quite useless and "on my main server" doesn't
really bring any useful info for hunting down this bug. Same as your
rant below.

What about adding at least what reportbug adds to its bugreports:

- your architecture
- version of bind and related libraries (like that GeoIP library), you
can just run reportbug on bind9 and libdns50 (which really depends on
libgeopip1)

 John,

could you please add libdns50 version and dependencies to the bug
report, please? Again you can just add reportbug

Also maybe objdump -T on libGeoIP.so.1 could be helpful, mine does
include needed symbol, does yours?

# objdump -T libGeoIP.so.1.4.6 | grep GeoIP_country_name_by_ipnum_v6
51d0 gDF .text  0050  BaseGeoIP_country_name_by_ipnum_v6

Ondrej.

2009/8/22 Stéphane Dupont :
> Why is this bug still marked as "fixed" ?
>
> It isn't ! (See Message #32 et #37)
>
> Thanks,
> Stephane Dupont.
>



-- 
Ondřej Surý 
http://blog.rfc1925.org/



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542928: [pkg-cryptsetup-devel] Bug#542928: cryptsetup fail with kernel 2.6.30-6

[Jonas Meurer]

hello,

On 22/08/2009 Guillaume JAOUEN wrote:
> Since upgrade of the kernel to 2.6.30-6, my laptop fail to start and
> doesn't ask for the lucks passphrase so my LVM setup can't start and
> the system lost debian-root and debian-swap filesystem...
> 
> Rebooting with 2.6.29 old kernel start properly.

thanks for your bugreport. in order to detect the problem it would be
very useful if you could provide further information:

- do you use a selfcompiled kernel, or did you install the default
  debian kernel (in package linux-image-2.6.30-1-amd64)?

- if you use a selfcompiled kernel, could you attach the .config of both
  the working 2.6.29 kernel and the broken 2.6.30 kernel?

- when you boot the broken 2.6.30 kernel, what exactly happens? do you
  get some message like 'root filesystem not found'? do you see an
  emergency shell of the initramfs?

- from the initramfs shell, please give the output of 'cat /proc/crypto'
  and 'cat /proc/modules'.
  you can do that by saving the output into a logfile on the boot fs.
  i.e. if your boot partition is /dev/sda1, do the following:
  mount /dev/sda1 /boot
  cat /proc/crypto > /boot/proc_crypto_log
  cat /proc/modules > /boot/proc_modules_log

  afterwards reboot with the working 2.6.29 kernel and attach both
  logfiles from /boot to your reply mail.

greetings,
 jonas


signature.asc
Description: Digital signature

Bug#543286: aolserver4-nssha1 0.1-2 module nssha1.so relay on non existant lib libnssha1.so

[SoboL]

Package: aolserver4-nssha1
Version: 0.1-2
Severity: grave
Justification: renders package unusable

Hi

I've upgraded my server to squeeze and trying to run aolserver4 4.5.1. 
My server relies on aolserver4-nssha1 package.

When I'm trying to start server I get the following error in error.log:

[23/Aug/2009:22:17:38][25445.18446744072008759024][-main-] Warning: 
modload: could not load /usr/lib/aolserver4/bin/nssha1.so: libnssha1.so: 
cannot open shared object file: No such file or directory
[23/Aug/2009:22:17:38][25445.18446744072008759024][-main-] Fatal: 
modload: failed to load module '/usr/lib/aolserver4/bin/nssha1.so'


libnssha1.so is pretty much non existant in debian, can't find such lib 
nowhere on google.


Here's output from ldd:
box-7:/var/log/aolserver4# ldd /usr/lib/aolserver4/bin/nssha1.so
   linux-vdso.so.1 =>  (0x7fff28ffe000)
   libnssha1.so => not found
   libnsd.so => /usr/lib/aolserver4/lib/libnsd.so (0x7fa620ad5000)
   libnsthread.so => /usr/lib/aolserver4/lib/libnsthread.so 
(0x7fa6208ca000)

   libtcl8.4.so.0 => /usr/lib/libtcl8.4.so.0 (0x7fa6205f9000)
   libdl.so.2 => /lib/libdl.so.2 (0x7fa6203f5000)
   libpthread.so.0 => /lib/libpthread.so.0 (0x7fa6201d9000)
   libm.so.6 => /lib/libm.so.6 (0x7fa61ff56000)
   libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x7fa61fd3c000)
   libc.so.6 => /lib/libc.so.6 (0x7fa61f9ea000)
   /lib64/ld-linux-x86-64.so.2 (0x7fa620f54000)


Please fix this ASAP!

Regards,
SoboL


-- System Information:
Debian Release: squeeze/sid
 APT prefers testing
 APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages aolserver4-nssha1 depends on:
ii  aolserver4-core-4.5.1 [aolser 4.5.1-5AOL Web Server 4 - core 
libraries

ii  aolserver4-daemon 4.5.1-5AOL Web Server 4 - program
ii  libc6 2.9-23 GNU C Library: Shared libraries
ii  libgcc1   1:4.4.1-1  GCC support library
ii  tcl8.48.4.19-3   Tcl (the Tool Command 
Language) v8


aolserver4-nssha1 recommends no packages.

aolserver4-nssha1 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#543094: marked as done (gpe-calendar: FTBFS: Trying patch debian/patches/030-configure.patch at level 1 ... 0 ... 2 ... failure.)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 21:32:06 +
with message-id 
and subject line Bug#543094: fixed in gpe-calendar 0.92-3
has caused the Debian Bug report #543094,
regarding gpe-calendar: FTBFS: Trying patch debian/patches/030-configure.patch 
at level 1 ... 0 ... 2 ... failure.
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.)


-- 
543094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpe-calendar
Version: 0.92-2
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090822 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-gpe-calendar_0.92-2-amd64-3PNAYL/gpe-calendar-0.92'
> for i in ./config.guess ./config.sub  ; do \
>   if test -e $i.cdbs-orig ; then \
>   mv $i.cdbs-orig $i ; \
>   fi ; \
>   done
> make[1]: Leaving directory 
> `/build/user-gpe-calendar_0.92-2-amd64-3PNAYL/gpe-calendar-0.92'
> if [ "debian/stamp-patched" = "reverse-patches" ]; then rm -f 
> debian/stamp-patched; fi
> patches: debian/patches/010-configure.ac.patch 
> debian/patches/020-desktop-standard.patch debian/patches/030-configure.patch 
> debian/patches/040_migrate_to_soup_2.4.patch
> Trying patch debian/patches/010-configure.ac.patch at level 1 ... success.
> Trying patch debian/patches/020-desktop-standard.patch at level 1 ... success.
> Trying patch debian/patches/030-configure.patch at level 1 ... 0 ... 2 ... 
> failure.
> make: *** [debian/stamp-patched] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/08/22/gpe-calendar_0.92-2_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: gpe-calendar
Source-Version: 0.92-3

We believe that the bug you reported is fixed in the latest version of
gpe-calendar, which is due to be installed in the Debian FTP archive:

gpe-calendar_0.92-3.diff.gz
  to pool/main/g/gpe-calendar/gpe-calendar_0.92-3.diff.gz
gpe-calendar_0.92-3.dsc
  to pool/main/g/gpe-calendar/gpe-calendar_0.92-3.dsc
gpe-calendar_0.92-3_amd64.deb
  to pool/main/g/gpe-calendar/gpe-calendar_0.92-3_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 543...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Neil Williams  (supplier of updated gpe-calendar 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, 23 Aug 2009 21:50:19 +0100
Source: gpe-calendar
Binary: gpe-calendar
Architecture: source amd64
Version: 0.92-3
Distribution: unstable
Urgency: low
Maintainer: Neil Williams 
Changed-By: Neil Williams 
Description: 
 gpe-calendar - store and manage calendar events in GPE
Closes: 543094
Changes: 
 gpe-calendar (0.92-3) unstable; urgency=low
 .
   * Drop debian/patches/030-configure.patch (Closes: #543094)
Checksums-Sha1: 
 35e64004f6a7902e066d4c13982d01906bd1597f 1611 gpe-calendar_0.92-3.dsc
 307960a0236f8d5b72ad5a2504fb1fbc1d5fea97 8653 gpe-calendar_0.92-3.diff.gz
 9c4a0714bdc40fd5618c196c9b7bb95853424c30 189484 gpe-calendar_0.92-3_amd64.deb
Checksums-Sha256: 
 92f707e3d3a9f79a40b41c22fd32d1567ead4a95b0d41eaed8c916172346286b 1611 
gpe-calendar_0.92-3.dsc
 f3c194bbf4c923782ccc8162e52e9bb0883b850825c18b759bc17399133a4c9b 8653 
gpe-calendar_0.92-3.diff.gz
 2cf2faf2ae6aa9bb115569db2e606bdd2713862e5b3a2ec51345aa29db50bb6d 189484 
gpe-calendar_0.92-3_amd64.deb
Files: 
 2be64c3e8cf9ae2161e4b35134a06fc5 1611 utils optional gpe-calendar_0.92-3.dsc
 d1b9032ca2619552a9b3a8c91b760818 8653 utils optional 
gpe-calendar_0.92-3.diff.gz
 d2776643d0f376266fad5475f5858975 189484 utils optional 
gpe-calendar_0.9

Bug#543085: libhibernate3-java: FTBFS: You must specify a valid JAVA_HOME or JAVACMD!

[Matthias Klose]

On 23.08.2009 23:38, Damien Raude-Morvan wrote:

It's linked to default-jdk switch to JDBC6

An issue report [1] is open upstream on this subject, but it's not fixed and,
sadly, proposed patch just add stubs methods.

Ubuntu [2] build hibernate with an explicit dependencies on GCJ compiler.

[1] http://opensource.atlassian.com/projects/hibernate/browse/HHH-2412
[2] http://patches.ubuntu.com/libh/libhibernate3-java/libhibernate3-
java_3.3.1.GA+dak1-3ubuntu1.patch


as long as the source package only builds binary-indep packages, the same 
workaround can be applied. but because Debian uses GCJ for some architectures 
you still need to take care about the differences between Openjdk and GCJ for 
architecture dependent packages.


  Matthias



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542888: bind9 stops during upgrade. again.

[Craig Sanders]

On Sun, Aug 23, 2009 at 01:56:18PM +0200, Ond??ej Surý wrote:
> > a working nameserver is a core, essential component of a functioning
> > network. while named is down, *everything* on the network that uses that
> > nameserver ceases to function correctly.
> 
> That's why you should never have only one "nameserver 127.0.0.1" in
> your /etc/resolv.conf. Configure one or two more remote nameservers
> and you're done.

i'm talking about a network being disrupted, not a single host.

the hosts DON'T have 127.0.0.1 in resolv.conf, they have the namesever.

> It's not critical severity - normal or wishlist would be more
> appropriate.

it is critical.  it breaks functionality for the entire local network.

> While I agree that it's not very convenient to have bind9 stopped for
> longer time periods, there are other ways how to prevent this kind of

it's not a matter of convenience. it's a matter of temporarily breaking
everything on the network that depends on DNS (which is pretty much
every network service or connection).


> outage. And it's entirely different from f.e. quagga, where restart
> could mean loss of connectivity at all. Which clearly doesn't happen
> with bind - you just loose ability to resolv DNS, when you have only
> one nameserver configured.

actually, there are multiple nameservers on the network. it doesn't help
as much as you might think. most, if not all, client resolver libraries
try nameservers in series, not in parallel. they don't try the second
or third resolver until the first times out. for some services, the DNS
timeout is longer than the connection or authentication timeout.

clearly you have no experience of dozens or hundreds of users
whinging at you saying "the internet isn't working" or "the
file-server/intranet/web site/etc is dead" because the first nameserver
in their dhcp-assigned resolv list is down and the NEXT nameserver isn't
queried until the first times out.

even if, for example, their browser has the intranet's IP cached, the
users still can't to the intranet because the login scripts can't find
the ldap server.

DNS is not just a convenience, it's a fundamental service that
everything else on the network depends on.

the bind9 package has worked reliably for many years with a restart
after upgrade rather than stop-early, start-late approach. there is no
reason for the current change in behaviour. it just maximises downtime.

craig

-- 
craig sanders 



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#543085: libhibernate3-java: FTBFS: You must specify a valid JAVA_HOME or JAVACMD!

[Damien Raude-Morvan]

Le dimanche 23 août 2009 22:40:51, Torsten Werner a écrit :
> On Sat, Aug 22, 2009 at 6:47 PM, Lucas Nussbaum 
wrote:
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
>
> Any help is appriated:
>
> "[javac]
> /tmp/buildd/libhibernate3-java-3.3.1.GA+dak1/project/core/src/main/java/org
>/hibernate/jdbc/ResultSetWrapper.java:53:
> org.hibernate.jdbc.ResultSetWrapper is not abstract and does not
> override abstract method updateNClob(java.lang.String,java.io.Reader)
> in java.sql.ResultSet
> [javac] public class ResultSetWrapper implements ResultSet {
> [javac]^
> [javac]
> /tmp/buildd/libhibernate3-java-3.3.1.GA+dak1/project/core/src/main/java/org
>/hibernate/lob/BlobImpl.java:39: org.hibernate.lob.BlobImpl is not abstract
> and does not override
> abstract method getBinaryStream(long,long) in java.sql.Blob
> [javac] public class BlobImpl implements Blob {
> [javac]^
> [javac]
> /tmp/buildd/libhibernate3-java-3.3.1.GA+dak1/project/core/src/main/java/org
>/hibernate/lob/ClobImpl.java:41: org.hibernate.lob.ClobImpl is not abstract
> and does not override
> abstract method getCharacterStream(long,long) in java.sql.Clob
> [javac] public class ClobImpl implements Clob {
> [javac]^
> [javac]
> /tmp/buildd/libhibernate3-java-3.3.1.GA+dak1/project/core/src/main/java/org
>/hibernate/lob/SerializableBlob.java:36: org.hibernate.lob.SerializableBlob
> is not abstract and does not
> override abstract method getBinaryStream(long,long) in java.sql.Blob
> [javac] public class SerializableBlob implements Serializable, Blob {
> [javac]^
> [javac]
> /tmp/buildd/libhibernate3-java-3.3.1.GA+dak1/project/core/src/main/java/org
>/hibernate/lob/SerializableClob.java:38: org.hibernate.lob.SerializableClob
> is not abstract and does not
> override abstract method getCharacterStream(long,long) in
> java.sql.Clob
> [javac] public class SerializableClob implements Serializable, Clob {
> [javac]^"

It's linked to default-jdk switch to JDBC6

An issue report [1] is open upstream on this subject, but it's not fixed and, 
sadly, proposed patch just add stubs methods.

Ubuntu [2] build hibernate with an explicit dependencies on GCJ compiler.

[1] http://opensource.atlassian.com/projects/hibernate/browse/HHH-2412
[2] http://patches.ubuntu.com/libh/libhibernate3-java/libhibernate3-
java_3.3.1.GA+dak1-3ubuntu1.patch

Cheers,
-- 
Damien Raude-Morvan - http://damien.raude-morvan.com/


signature.asc
Description: This is a digitally signed message part.

Processed: setting package to gpe-calendar, tagging 543094

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #gpe-calendar (0.92-3) unstable; urgency=low
> #
> #  * Drop debian/patches/030-configure.patch (Closes: #543094)
> #
> package gpe-calendar
Limiting to bugs with field 'package' containing at least one of 'gpe-calendar'
Limit currently set to 'package':'gpe-calendar'

> tags 543094 + pending
Bug #543094 [gpe-calendar] gpe-calendar: FTBFS: Trying patch 
debian/patches/030-configure.patch at level 1 ... 0 ... 2 ... failure.
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542140: [Pkg-fglrx-devel] Bug#542140: fglrx-driver: fglrx driver doesn't work with linux-image-2.6.30 (AMD64)

[Gary Dale]

Patrick Matthäi wrote:

Gary Dale schrieb:

Bertrand Marc wrote:

Gary Dale a écrit :


I notice that the log heading reports the X server version as 
1.4.2. That seems a little strange.
Right, I didn't notice that. It's probably the issue, but still I 
can't figure out where it comes from.


Also noticed that I've somehow lost ACPI support. I know I used to 
have it and I don't recall removing it, so I reinstalled it. That 
should at least allow my screen to power down again.


If you installed fglrx with apt-get, you didn't installed 
'Recommands', so you probably should install fglrx-atieventsd to get 
ACPI support.


Bertrand

PS could you cc your replies to #542140 ?

No, it was likely just the lack of the ACPID that caused the problem. 
The fglrx-atieventsd was one of the .debs that installed OK earlier. 
Aptitude seems to think I've got the latest version.


So maybe we should add acpid to recommends on fglrx-atieventsd.

It should be part of any recent Linux install. I don't know how it got 
removed. However, all that installing it fixed was a problem I had with 
my screen not shutting off - something that has never been a problem 
before (other than the ongoing problem with mplayer/avidemux/etc. 
crashing the screensaver).





--
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#543134: libjboss-remoting-java: FTBFS: Nonexistent build-dependency: libtomcat5.5-java

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 543134 + help
Bug #543134 [libjboss-remoting-java] libjboss-remoting-java: FTBFS: Nonexistent 
build-dependency: libtomcat5.5-java
Added tag(s) help.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#543134: libjboss-remoting-java: FTBFS: Nonexistent build-dependency: libtomcat5.5-java

[Torsten Werner]

tags 543134 + help
thanks

I need help with this package:

"[javac] 
/tmp/buildd/libjboss-remoting-java-2.5.1/src/org/jboss/remoting/transport/coyote/OutputBuffer.java:611:
cannot find symbol
[javac] symbol  : method
convert(org.apache.tomcat.util.buf.CharChunk,org.apache.tomcat.util.buf.ByteChunk)
[javac] location: class org.apache.tomcat.util.buf.C2BConverter
[javac]   conv.convert(cb, bb);
[javac]   ^"

Thanks,
Torsten



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#543075: marked as done (libjcip-annotations-java: FTBFS: You must specify a valid JAVA_HOME or JAVACMD!)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 20:32:09 +
with message-id 
and subject line Bug#543075: fixed in libjcip-annotations-java 20060626-2
has caused the Debian Bug report #543075,
regarding libjcip-annotations-java: FTBFS: You must specify a valid JAVA_HOME 
or JAVACMD!
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.)


-- 
543075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjcip-annotations-java
Version: 20060626-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090822 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  /usr/bin/fakeroot debian/rules clean
> test -x debian/rules
> dh_testroot
> You must specify a valid JAVA_HOME or JAVACMD!
> make: *** [ant-sanity-check] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/08/22/libjcip-annotations-java_20060626-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: libjcip-annotations-java
Source-Version: 20060626-2

We believe that the bug you reported is fixed in the latest version of
libjcip-annotations-java, which is due to be installed in the Debian FTP 
archive:

libjcip-annotations-java-doc_20060626-2_all.deb
  to 
pool/main/libj/libjcip-annotations-java/libjcip-annotations-java-doc_20060626-2_all.deb
libjcip-annotations-java_20060626-2.diff.gz
  to 
pool/main/libj/libjcip-annotations-java/libjcip-annotations-java_20060626-2.diff.gz
libjcip-annotations-java_20060626-2.dsc
  to 
pool/main/libj/libjcip-annotations-java/libjcip-annotations-java_20060626-2.dsc
libjcip-annotations-java_20060626-2_all.deb
  to 
pool/main/libj/libjcip-annotations-java/libjcip-annotations-java_20060626-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 543...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Torsten Werner  (supplier of updated 
libjcip-annotations-java 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, 23 Aug 2009 22:05:22 +0200
Source: libjcip-annotations-java
Binary: libjcip-annotations-java libjcip-annotations-java-doc
Architecture: source all
Version: 20060626-2
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers 

Changed-By: Torsten Werner 
Description: 
 libjcip-annotations-java - Java Concurrency In Practice annotations library
 libjcip-annotations-java-doc - Java Concurrency In Practice annotations 
library documentation
Closes: 543075
Changes: 
 libjcip-annotations-java (20060626-2) unstable; urgency=low
 .
   * Really use default-java. (Closes: #543075)
   * Add missing Depends: ${misc:Depends}.
   * Update Standards-Version: 3.8.3.
   * Change Section: java.
   * Switch to explicit GPL-2+ for the Debian packaging.
Checksums-Sha1: 
 19c7e61cd5ac2b833907cd436c7cc2e4119acdad 1479 
libjcip-annotations-java_20060626-2.dsc
 a96f1afde24b4f89a012628bba7b400aaf8d1027 10457 
libjcip-annotations-java_20060626-2.diff.gz
 8b1f1306354991b0e0c90b0bf79ba263f59bbd2a 11686 
libjcip-annotations-java_20060626-2_all.deb
 d9e60f1da7f426f09274c0b4d4ad6fd65bf2bdf2 21860 
libjcip-annotations-java-doc_20060626-2_all.deb
Checksums-Sha256: 
 082213258bcd7877cb2fc7cbc30c48813a4d3378fa1bf6f1b3053159a0cb 1479 
libjcip-annotations-java_20060626-2.dsc
 27396d98ae36b118b36c529d831168f52d0b972dd17f40229f3e3dfaa8342ae5 10457 
libjcip-annotations-java_20060626-2.diff.gz
 97416752eae8de32bca0620e2f20ef77501baec7f8170418fb73486d4ee1fe64 11686 
libjcip-annotations-java_20060626-2_all.deb
 e5b919f8601f2828b3818b21a9ab2a831d286ccc5c83676ab775bf5842cee316 21860 
libjcip-annotations-java-doc_20060626-2_all.deb

Bug#542986: marked as done (hoichess: FTBFS: debug_printconfig.h:4: error: missing terminating " character)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 20:47:04 +
with message-id 
and subject line Bug#542986: fixed in hoichess 0.10.3-4
has caused the Debian Bug report #542986,
regarding hoichess: FTBFS: debug_printconfig.h:4: error: missing terminating " 
character
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.)


-- 
542986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hoichess
Version: 0.10.3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090822 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> g++ -Wall -g -O2 -DHAVE_PTHREAD -DHOICHESS -I. -Ichess -MT 
> .build-unix/.hoichess/debug.o -MD -MF .build-unix/.hoichess/debug.d -c -o 
> .build-unix/.hoichess/debug.o debug.cc
> In file included from debug.cc:150:
> debug_printconfig.h:4:72: warning: missing terminating " character
> In file included from debug.cc:150:
> debug_printconfig.h:4: error: missing terminating " character
> debug_printconfig.h:5:1: warning: missing terminating " character
> debug_printconfig.h:5: error: missing terminating " character
> debug_printconfig.h:8:80: warning: missing terminating " character
> debug_printconfig.h:8: error: missing terminating " character
> debug_printconfig.h:9:1: warning: missing terminating " character
> debug_printconfig.h:9: error: missing terminating " character
> debug_printconfig.h:12:82: warning: missing terminating " character
> debug_printconfig.h:12: error: missing terminating " character
> debug_printconfig.h:13:1: warning: missing terminating " character
> debug_printconfig.h:13: error: missing terminating " character
> debug_printconfig.h:16:64: warning: missing terminating " character
> debug_printconfig.h:16: error: missing terminating " character
> debug_printconfig.h:17:1: warning: missing terminating " character
> debug_printconfig.h:17: error: missing terminating " character
> debug_printconfig.h:20:70: warning: missing terminating " character
> debug_printconfig.h:21:1: warning: missing terminating " character
> debug_printconfig.h:24:54: warning: missing terminating " character
> debug_printconfig.h:24: error: missing terminating " character
> debug_printconfig.h:25:1: warning: missing terminating " character
> debug_printconfig.h:25: error: missing terminating " character
> debug_printconfig.h:28:54: warning: missing terminating " character
> debug_printconfig.h:28: error: missing terminating " character
> debug_printconfig.h:29:1: warning: missing terminating " character
> debug_printconfig.h:29: error: missing terminating " character
> debug_printconfig.h:32:62: warning: missing terminating " character
> debug_printconfig.h:32: error: missing terminating " character
> debug_printconfig.h:33:1: warning: missing terminating " character
> debug_printconfig.h:33: error: missing terminating " character
> debug_printconfig.h:36:60: warning: missing terminating " character
> debug_printconfig.h:36: error: missing terminating " character
> debug_printconfig.h:37:1: warning: missing terminating " character
> debug_printconfig.h:37: error: missing terminating " character
> debug_printconfig.h:40:64: warning: missing terminating " character
> debug_printconfig.h:40: error: missing terminating " character
> debug_printconfig.h:41:1: warning: missing terminating " character
> debug_printconfig.h:41: error: missing terminating " character
> debug_printconfig.h:44:78: warning: missing terminating " character
> debug_printconfig.h:44: error: missing terminating " character
> debug_printconfig.h:45:1: warning: missing terminating " character
> debug_printconfig.h:45: error: missing terminating " character
> debug_printconfig.h:48:96: warning: missing terminating " character
> debug_printconfig.h:48: error: missing terminating " character
> debug_printconfig.h:49:1: warning: missing terminating " character
> debug_printconfig.h:49: error: missing terminating " character
> debug_printconfig.h:52:64: warning: missing terminating " character
> debug_printconfig.h:53:1: warning: missing terminating " character
> debug_printconfig.h:56:66: warning: missing terminating " character
> debug_printconfig.h:56: error: missing terminating " character
> debug_printconfig.h:57:1: warning: missing terminating " character
> debug_printconfig.h:57: error: missing terminating " character
> debug_printconfig.h:60:70: warning: missing terminating " character
> debug_printconfig.h:60: error: missing terminating " character
> debug_p

Bug#542140: [Pkg-fglrx-devel] Bug#542140: fglrx-driver: fglrx driver doesn't work with linux-image-2.6.30 (AMD64)

[Patrick Matthäi]

Gary Dale schrieb:

Bertrand Marc wrote:

Gary Dale a écrit :


I notice that the log heading reports the X server version as 1.4.2. 
That seems a little strange.
Right, I didn't notice that. It's probably the issue, but still I 
can't figure out where it comes from.


Also noticed that I've somehow lost ACPI support. I know I used to 
have it and I don't recall removing it, so I reinstalled it. That 
should at least allow my screen to power down again.


If you installed fglrx with apt-get, you didn't installed 
'Recommands', so you probably should install fglrx-atieventsd to get 
ACPI support.


Bertrand

PS could you cc your replies to #542140 ?

No, it was likely just the lack of the ACPID that caused the problem. 
The fglrx-atieventsd was one of the .debs that installed OK earlier. 
Aptitude seems to think I've got the latest version.


So maybe we should add acpid to recommends on fglrx-atieventsd.



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#543085: libhibernate3-java: FTBFS: You must specify a valid JAVA_HOME or JAVACMD!

[Torsten Werner]

tags 543085 + help
thanks

On Sat, Aug 22, 2009 at 6:47 PM, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

Any help is appriated:

"[javac] 
/tmp/buildd/libhibernate3-java-3.3.1.GA+dak1/project/core/src/main/java/org/hibernate/jdbc/ResultSetWrapper.java:53:
org.hibernate.jdbc.ResultSetWrapper is not abstract and does not
override abstract method updateNClob(java.lang.String,java.io.Reader)
in java.sql.ResultSet
[javac] public class ResultSetWrapper implements ResultSet {
[javac]^
[javac] 
/tmp/buildd/libhibernate3-java-3.3.1.GA+dak1/project/core/src/main/java/org/hibernate/lob/BlobImpl.java:39:
org.hibernate.lob.BlobImpl is not abstract and does not override
abstract method getBinaryStream(long,long) in java.sql.Blob
[javac] public class BlobImpl implements Blob {
[javac]^
[javac] 
/tmp/buildd/libhibernate3-java-3.3.1.GA+dak1/project/core/src/main/java/org/hibernate/lob/ClobImpl.java:41:
org.hibernate.lob.ClobImpl is not abstract and does not override
abstract method getCharacterStream(long,long) in java.sql.Clob
[javac] public class ClobImpl implements Clob {
[javac]^
[javac] 
/tmp/buildd/libhibernate3-java-3.3.1.GA+dak1/project/core/src/main/java/org/hibernate/lob/SerializableBlob.java:36:
org.hibernate.lob.SerializableBlob is not abstract and does not
override abstract method getBinaryStream(long,long) in java.sql.Blob
[javac] public class SerializableBlob implements Serializable, Blob {
[javac]^
[javac] 
/tmp/buildd/libhibernate3-java-3.3.1.GA+dak1/project/core/src/main/java/org/hibernate/lob/SerializableClob.java:38:
org.hibernate.lob.SerializableClob is not abstract and does not
override abstract method getCharacterStream(long,long) in
java.sql.Clob
[javac] public class SerializableClob implements Serializable, Clob {
[javac]^"

Cheers,
Torsten



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#543072: librspec-ruby: FTBFS: /usr/lib/ruby/1.8/inline.rb:53:in `require': no such file to load -- rubygems (LoadError)

[Ryan Niebur]

On Sun, Aug 23, 2009 at 10:36:30PM +0200, Tobias Grimm wrote:
> Hello!
> 
> Ryan Niebur wrote:
> 
> > I'm working on the fixed version of libinline-ruby,
> 
> Great, thanks!
> 
> > however when using
> > a working version librspec-ruby still FTBFS due to test failures.
> 
> Mmm... I can't reproduce this. librspec-ruby builds fine with
> libinline-ruby 3.6.7-1 and libheckle-ruby 1.4.2-2 (tested with pbuilder
> for Debian/Sid). I've also built it with the libinline-ruby version from
> the SVN trunk too without any problems or test failures.
> 

hm, okay, this was probably a problem specific to my machine, I didn't
build in a chroot that time.


-- 
_
Ryan Niebur
ryanrya...@gmail.com


signature.asc
Description: Digital signature

Bug#543072: librspec-ruby: FTBFS: /usr/lib/ruby/1.8/inline.rb:53:in `require': no such file to load -- rubygems (LoadError)

[Tobias Grimm]

Hello!

Ryan Niebur wrote:

> I'm working on the fixed version of libinline-ruby,

Great, thanks!

> however when using
> a working version librspec-ruby still FTBFS due to test failures.

Mmm... I can't reproduce this. librspec-ruby builds fine with
libinline-ruby 3.6.7-1 and libheckle-ruby 1.4.2-2 (tested with pbuilder
for Debian/Sid). I've also built it with the libinline-ruby version from
the SVN trunk too without any problems or test failures.

If you encounter any problems with building librspec-ruby, please send me
a build log (a pbuilder log if possible).

bye,

Tobias





signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#542400: Unable to remove package, post removal script fails

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 542400 1:9-8-2
Bug #542400 [fglrx-driver] Unable to remove package, post removal script fails
There is no source info for the package 'fglrx-driver' at version '1:9-8-2' 
with architecture ''
Unable to make a source version for version '1:9-8-2'
Bug Marked as fixed in versions 1:9-8-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542400: Unable to remove package, post removal script fails

[Michael S Gilbert]

fixed 542400 1:9-8-2
thanks

tested revision 278.  your changes have fixed this problem.  thanks!

mike



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#541706: marked as done (gpe-expenses_0.1.7-2+b1(mipsel/unstable): shift: 2368: can't shift that many)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 20:02:21 +
with message-id 
and subject line Bug#541706: fixed in gpe-expenses 0.1.7-3
has caused the Debian Bug report #541706,
regarding gpe-expenses_0.1.7-2+b1(mipsel/unstable): shift: 2368: can't shift 
that many
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.)


-- 
541706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpe-expenses
Version: 0.1.7-2+b1
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of gpe-expenses_0.1.7-2+b1 on rem by sbuild/mipsel 99.999
> Build started at 20090815-0428

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: cdbs, debhelper (>= 5), autotools-dev, intltool (>= 0.40), 
> xsltproc, libglib2.0-dev (>= 2.6.0), libgpepimc-dev, libgpewidget-dev, 
> libqof-dev (>= 0.8.1), libpopt-dev, libgtk2.0-dev

[...]

> make[3]: Entering directory `/build/buildd/gpe-expenses-0.1.7/po-lib'
> cd .. \
> && CONFIG_FILES=po/Makefile.in CONFIG_HEADERS= CONFIG_LINKS= \
>  /bin/sh ./config.status
> config.status: creating po/Makefile.in
> config.status: executing depfiles commands
> shift: 2368: can't shift that many
> make[3]: *** [stamp-it] Error 2
> make[3]: Leaving directory `/build/buildd/gpe-expenses-0.1.7/po-lib'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/buildd/gpe-expenses-0.1.7'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/gpe-expenses-0.1.7'
> make: *** [debian/stamp-makefile-build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=mipsel&pkg=gpe-expenses&ver=0.1.7-2+b1



--- End Message ---
--- Begin Message ---
Source: gpe-expenses
Source-Version: 0.1.7-3

We believe that the bug you reported is fixed in the latest version of
gpe-expenses, which is due to be installed in the Debian FTP archive:

gpe-expenses_0.1.7-3.diff.gz
  to pool/main/g/gpe-expenses/gpe-expenses_0.1.7-3.diff.gz
gpe-expenses_0.1.7-3.dsc
  to pool/main/g/gpe-expenses/gpe-expenses_0.1.7-3.dsc
gpe-expenses_0.1.7-3_amd64.deb
  to pool/main/g/gpe-expenses/gpe-expenses_0.1.7-3_amd64.deb
libqofexpensesobjects-data_0.1.7-3_all.deb
  to pool/main/g/gpe-expenses/libqofexpensesobjects-data_0.1.7-3_all.deb
libqofexpensesobjects-dev_0.1.7-3_amd64.deb
  to pool/main/g/gpe-expenses/libqofexpensesobjects-dev_0.1.7-3_amd64.deb
libqofexpensesobjects-doc_0.1.7-3_all.deb
  to pool/main/g/gpe-expenses/libqofexpensesobjects-doc_0.1.7-3_all.deb
libqofexpensesobjects1-dbg_0.1.7-3_amd64.deb
  to pool/main/g/gpe-expenses/libqofexpensesobjects1-dbg_0.1.7-3_amd64.deb
libqofexpensesobjects1_0.1.7-3_amd64.deb
  to pool/main/g/gpe-expenses/libqofexpensesobjects1_0.1.7-3_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 541...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Neil Williams  (supplier of updated gpe-expenses 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, 23 Aug 2009 20:07:41 +0100
Source: gpe-expenses
Binary: gpe-expenses libqofexpensesobjects-doc libqofexpensesobjects1 
libqofexpensesobjects-dev libqofexpensesobjects1-dbg libqofexpensesobjects-data
Architecture: source all amd64
Version: 0.1.7-3
Distribution: unstable
Urgency: low
Maintainer: Neil Williams 
Changed-By: Neil Williams 
Description: 
 gpe-expenses - Simple expense records for GPE
 libqofexpensesobjects-data - QOF expenses objects - translations
 libqofexpensesobjects-dev - QOF expenses objects - development files
 libqofexpensesobjects-doc - QOF expenses objects - documentation
 libqofexpensesobjects1 - financial QOF objects for expenses handling
 libqofexpensesobjects1-dbg - QOF expenses objects - debug support
Closes: 541706
Changes: 
 gpe-expenses (0.1.7-3) unstable; urgency=low
 .
   * Regenerate autotools to cope with /bin/sh -> /bin/bash issues in
 config.status. Fixes mipsel build. (Closes:#541706) (LP: #415536)
Checksums-Sha1: 
 317ce67950fae8ca48e014addcdc75c4cfab183c 1637 gpe-expenses_0.1.7-3.dsc
 9e72c3044a58d82cc1d73567df40c12719d1610a 46

Bug#543073: libjboss-aop-java: FTBFS: java errors

[Torsten Werner]

tags 543073 + help
thanks


Hi,

On Sat, Aug 22, 2009 at 6:48 PM, Lucas Nussbaum wrote:
[javac] 433 problems (1 error, 432 warnings) > > BUILD FAILED

it looks like a qdox problem:

"[javac] 
/tmp/buildd/libjboss-aop-java-2.0.0.SP1/src/aspect-framework/main/org/jboss/aop/annotation/compiler/AnnotationDocletTagFactory.java:35:
org.jboss.aop.annotation.compiler.AnnotationDocletTagFactory is not
abstract and does
not override abstract method
createDocletTag(java.lang.String,java.lang.String,com.thoughtworks.qdox.model.AbstractBa
seJavaEntity,int) in com.thoughtworks.qdox.model.DocletTagFactory"

Is somebody able to help here?

Cheers,
Torsten



-- 
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#543073: libjboss-aop-java: FTBFS: java errors

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 543073 + help
Bug #543073 [libjboss-aop-java] libjboss-aop-java: FTBFS: java errors
Added tag(s) help.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542140: fglrx-driver: fglrx driver doesn't work with linux-image-2.6.30 (AMD64)

[Gary Dale]

Bertrand Marc wrote:

Gary Dale a écrit :


I notice that the log heading reports the X server version as 1.4.2. 
That seems a little strange.
Right, I didn't notice that. It's probably the issue, but still I 
can't figure out where it comes from.


Also noticed that I've somehow lost ACPI support. I know I used to 
have it and I don't recall removing it, so I reinstalled it. That 
should at least allow my screen to power down again.


If you installed fglrx with apt-get, you didn't installed 
'Recommands', so you probably should install fglrx-atieventsd to get 
ACPI support.


Bertrand

PS could you cc your replies to #542140 ?

No, it was likely just the lack of the ACPID that caused the problem. 
The fglrx-atieventsd was one of the .debs that installed OK earlier. 
Aptitude seems to think I've got the latest version.






--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#543089: marked as done (jaranalyzer: FTBFS: You must specify a valid JAVA_HOME or JAVACMD!)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 19:47:08 +
with message-id 
and subject line Bug#543089: fixed in jaranalyzer 1.2-4
has caused the Debian Bug report #543089,
regarding jaranalyzer: FTBFS: You must specify a valid JAVA_HOME or JAVACMD!
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.)


-- 
543089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jaranalyzer
Version: 1.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090822 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  /usr/bin/fakeroot debian/rules clean
> test -x debian/rules
> dh_testroot
> You must specify a valid JAVA_HOME or JAVACMD!
> make: *** [ant-sanity-check] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/08/22/jaranalyzer_1.2-3_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: jaranalyzer
Source-Version: 1.2-4

We believe that the bug you reported is fixed in the latest version of
jaranalyzer, which is due to be installed in the Debian FTP archive:

jaranalyzer_1.2-4.diff.gz
  to pool/main/j/jaranalyzer/jaranalyzer_1.2-4.diff.gz
jaranalyzer_1.2-4.dsc
  to pool/main/j/jaranalyzer/jaranalyzer_1.2-4.dsc
jaranalyzer_1.2-4_all.deb
  to pool/main/j/jaranalyzer/jaranalyzer_1.2-4_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 543...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Florian Grandel  (supplier of updated jaranalyzer 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: Fri, 14 Aug 2009 09:18:41 -0300
Source: jaranalyzer
Binary: jaranalyzer
Architecture: source all
Version: 1.2-4
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers 

Changed-By: Florian Grandel 
Description: 
 jaranalyzer - Dependency management utility for jar files
Closes: 540175 543089
Changes: 
 jaranalyzer (1.2-4) unstable; urgency=low
 .
   * closes: #540175
+ added default-jdk to Build-Depends
+ set JAVA_HOME to /usr/lib/jvm/default-java
+ thanks to Michael Bienia  and Marcus Better
 for reporting/patching
   * updated standards version
   * added ${misc:Depends}
   * added Vcs-* entries
   * added header to patch
   * added README.source
   * closes: #543089
Checksums-Sha1: 
 70678fef9b8927602b3fc696cc411daba447bb83 1354 jaranalyzer_1.2-4.dsc
 684eeaca060028d5f61b46711f8351c413daa6a4 5625 jaranalyzer_1.2-4.diff.gz
 3e815bc16bd1de88d0c3eebb6b9fe2b2d96a5e98 28610 jaranalyzer_1.2-4_all.deb
Checksums-Sha256: 
 4a5b2244c5f2dd9a46a6e1cdaa0c1ae3c17e0fba9d0c4804cb073de2d15cdf52 1354 
jaranalyzer_1.2-4.dsc
 d027afb3778941d4ea4486ef280b286134b2443ed903fd267e50f0067a5327d8 5625 
jaranalyzer_1.2-4.diff.gz
 b37981b910021a62dfd0625cf44e07bb67c9f3e9923b275097b12721b0b20fc2 28610 
jaranalyzer_1.2-4_all.deb
Files: 
 223c695db50eec805b45f17e2fa0f4e3 1354 java optional jaranalyzer_1.2-4.dsc
 4b25111c7fb314ff5bed61aec9b031e8 5625 java optional jaranalyzer_1.2-4.diff.gz
 b780e43cd12f089970b5497a6a092153 28610 java optional jaranalyzer_1.2-4_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqRmUUACgkQfY3dicTPjsO3EQCZATyH9DsFZ9Gz+RMjL5YoijSz
zeUAn2ohqSyxqPSJIW6Ung8xMGjeewN6
=tHhC
-END PGP SIGNATURE-


--- End Message ---

Bug#543263: blcr_0.8.2-2 FTBFS on sparc (dist=unstable)

[Alan Woodland]

tags 543263 confirmed
thanks

2009/8/23 Martin Zobel-Helas :
> Package: blcr
> Version: 0.8.2-2
> Severity: serious
>
>> checking for value of CR_ASM_OP_HAND_CHKPT... 2147787009
>> checking for value of CR_ASM_CHECKPOINT_STUB... 16384
>> checking for value of CR_ASM_OP_HAND_ABORT... 2147787010
>> checking for value of CR_ASM_CHECKPOINT_OMIT... 4
>> checking for value of CR_ASM_SI_PID_OFFSET... 12
>> checking for value of CR_ASM_NR_ioctl... 54
>> checking for value of CR_ASM_NR_rt_sigreturn... 101
>> checking for direction of stack growth... down
>> checking for value of CR_SIGNUM... 64
>> checking for void *... (cached) yes
>> checking size of void *... (cached) 4
>> configure: error: --enable-multilib not supported on architecture sparc
>> make: *** [build-arch-stamp] Error 1
>> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>

Oops, that's my mistake. I'll make an upload shortly that corrects this.

Alan



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542140: fglrx-driver: fglrx driver doesn't work with linux-image-2.6.30 (AMD64)

[Bertrand Marc]

Gary Dale a écrit :


I notice that the log heading reports the X server version as 1.4.2. 
That seems a little strange.
Right, I didn't notice that. It's probably the issue, but still I can't 
figure out where it comes from.


Also noticed that I've somehow lost ACPI support. I know I used to 
have it and I don't recall removing it, so I reinstalled it. That 
should at least allow my screen to power down again.


If you installed fglrx with apt-get, you didn't installed 'Recommands', 
so you probably should install fglrx-atieventsd to get ACPI support.


Bertrand

PS could you cc your replies to #542140 ?




--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: setting package to libqofexpensesobjects-data libqofexpensesobjects-dev libqofexpensesobjects1-dbg libqofexpensesobjects1 gpe-expenses libqofexpensesobjects-doc ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #gpe-expenses (0.1.7-3) unstable; urgency=low
> #
> #  * Regenerate autotools to cope with /bin/sh -> /bin/bash issues in
> #config.status. Fixes mipsel build. (Closes:#541706) (LP: #415536)
> #
> package libqofexpensesobjects-data libqofexpensesobjects-dev 
> libqofexpensesobjects1-dbg libqofexpensesobjects1 gpe-expenses 
> libqofexpensesobjects-doc
Limiting to bugs with field 'package' containing at least one of 
'libqofexpensesobjects-data', 'libqofexpensesobjects-dev', 
'libqofexpensesobjects1-dbg', 'libqofexpensesobjects1', 'gpe-expenses', 
'libqofexpensesobjects-doc'
Limit currently set to 'package':'libqofexpensesobjects-data', 
'libqofexpensesobjects-dev', 'libqofexpensesobjects1-dbg', 
'libqofexpensesobjects1', 'gpe-expenses', 'libqofexpensesobjects-doc'

> tags 541706 + pending
Bug #541706 [gpe-expenses] gpe-expenses_0.1.7-2+b1(mipsel/unstable): shift: 
2368: can't shift that many
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542140: fglrx-driver: fglrx driver doesn't work with linux-image-2.6.30 (AMD64)

[Bertrand Marc]

Gary Dale a écrit :

Yes. I followed Patrick's recipe:

# apt-get install fglrx-driver fglrx-glx fglrx-source module-assistant
# m-a a-i fglrx


See attached log:
Here are the interesting lines of your Xorg.0.log. It means you don't 
have hardware acceleration :


(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0
(WW) fglrx(0): could not detect X server version (query_status=-1)
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(WW) fglrx(0): ***
(WW) fglrx(0): * DRI initialization failed!  *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available*
(WW) fglrx(0): * *

But honestly I don't know why fglrx couldn't detect your Xorg version...

cheers,
Bertrand

X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-11)
Current Operating System: Linux transponder 2.6.30-1-amd64 #1 SMP Mon Aug 3 12:28:22 UTC 2009 x86_64
Build Date: 20 February 2009  04:53:05PM
 
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Module Loader present
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 Aug 23 13:47:50 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor "DELL P1110"
(**) |   |-->Device "ATI HD3300"
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) Including the default font path /usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType.
(**) FontPath set to:
	/usr/local/share/fonts,
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/cyrillic,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
(==) RgbPath set to "/etc/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x7c31c0
(II) Module ABI versions:
	X.Org ANSI C Emulation: 0.3
	X.Org Video Driver: 2.0
	X.Org XInput driver : 2.0
	X.Org Server Extension : 0.3
	X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.0
	ABI class: X.Org Video Driver, version 2.0
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1022,9600 card 1022,9600 rev 00 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1022,9602 card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:06:0: chip 1022,9606 card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:0a:0: chip 1022,9609 card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:11:0: chip 1002,4391 card 1458,b002 rev 00 class 01,06,01 hdr 00
(II) PCI: 00:12:0: chip 1002,4397 card 1458,5004 rev 00 class 0c,03,10 hdr 80
(II) PCI: 00:12:1: chip 1002,4398 card 1458,5004 rev 00 class 0c,03,10 hdr 00
(II) PCI: 00:12:2: chip 1002,4396 card 1458,5004 rev 00 class 0c,03,20 hdr 00
(II) PCI: 00:13:0: chip 1002,4397 card 1458,5004 rev 00 class 0c,03,10 hdr 80
(II) PCI: 00:13:1: chip 1002,4398 card 1458,5004 rev 00 class 0c,03,10 hdr 00
(II) PCI: 00:13:2: chip 1002,4396 card 1458,5004 rev 00 class 0c,03,20 hdr 00
(II) PCI: 00:14:0: chip 1002,4385 card 1458,4385 rev 3a class 0c,05,00 hdr 80
(II) PCI: 00:14:1: chip 1002,439c card 1458,5002 rev 00 class 01,01,8a hdr 00
(II) PCI: 00:14:2: chip 1002,4383 card 1458,a102 rev 00 class 04,03,00 hdr 00
(II) PCI: 00:14:3: chip 1002,439d card 1002,439d rev 00 class 06,01,00 hdr 80
(II) PCI: 00:14:4: chip 1002,4384 card , rev 00 class 06,04,01 hdr 81
(II) PCI: 00:14:5: chip 1002,4399 card 1458,5004 rev 00 class 0c,03,10 hdr 00
(II) PCI: 00:18:0: chip 1022,1200 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:1: chip 1022,1201 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:2: chip 1022,1202 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:3: chip 1022,1203 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:4: chip 1022,1204 card , rev 00 class 06,00,00 hdr 80
(II) PCI: 01:05:0: chip 1002,96

Processed: tagpending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #ruby-gstreamer0.10 (0.2.0-5) UNRELEASED; urgency=low
> #
> #  * Make ruby-gstreamer0.10 build with current versions of the ruby-gnome2
> #packages by depending on ruby-gnome2-dev for mkmf-gnome2.rb, closes:
> ##536952.
> #
> package libgstreamer0.10-ruby1.8 ruby-gstreamer0.10 libgstreamer0.10-ruby
Limiting to bugs with field 'package' containing at least one of 
'libgstreamer0.10-ruby1.8', 'ruby-gstreamer0.10', 'libgstreamer0.10-ruby'
Limit currently set to 'package':'libgstreamer0.10-ruby1.8', 
'ruby-gstreamer0.10', 'libgstreamer0.10-ruby'

> tags 536952 + pending confirmed
Bug #536952 [ruby-gstreamer0.10] ruby-gstreamer0.10: FTBFS: extconf.rb:10:in 
`require': no such file to load -- mkmf-gnome2 (LoadError)
Added tag(s) confirmed and pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagpending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #libinline-ruby (3.8.3-2) unstable; urgency=low
> #
> #  * don't require rubygems (Closes: #543165, #543061)
> #
> package libinline-ruby libinline-ruby1.8
Limiting to bugs with field 'package' containing at least one of 
'libinline-ruby', 'libinline-ruby1.8'
Limit currently set to 'package':'libinline-ruby', 'libinline-ruby1.8'

> tags 543165 + pending confirmed
Bug #543165 [libinline-ruby] [libinline-ruby] inline.rb requires rubygems and 
zentest_mapping
Added tag(s) confirmed and pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: librspec-ruby: FTBFS: /usr/lib/ruby/1.8/inline.rb:53:in `require': no such file to load -- rubygems (LoadError)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 543072 serious
Bug #543072 [librspec-ruby] librspec-ruby: FTBFS: 
/usr/lib/ruby/1.8/inline.rb:53:in `require': no such file to load -- rubygems 
(LoadError)
Severity set to 'serious' from 'normal'

> quit
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#540970: marked as done (protobuf-c: FTBFS due to missing B-D)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 18:33:13 +
with message-id 
and subject line Bug#540970: fixed in protobuf-c 0.11-1
has caused the Debian Bug report #540970,
regarding protobuf-c: FTBFS due to missing B-D
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.)


-- 
540970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: protobuf-c
Version: 0.10-2
Severity: serious
Tags: patch
Justification: FTBFS

Hi,

your package B-D on: “libprotobuf-dev, protobuf-compiler” (for the
proto* packages) but its configure(.ac) checks for linking with
“-lprotoc -lprotobuf”. The former is now in its own libprotoc-dev
package, please B-D on it.

Mraw,
KiBi.


--- End Message ---
--- Begin Message ---
Source: protobuf-c
Source-Version: 0.11-1

We believe that the bug you reported is fixed in the latest version of
protobuf-c, which is due to be installed in the Debian FTP archive:

libprotobuf-c0-dev_0.11-1_amd64.deb
  to pool/main/p/protobuf-c/libprotobuf-c0-dev_0.11-1_amd64.deb
libprotobuf-c0_0.11-1_amd64.deb
  to pool/main/p/protobuf-c/libprotobuf-c0_0.11-1_amd64.deb
protobuf-c-compiler_0.11-1_amd64.deb
  to pool/main/p/protobuf-c/protobuf-c-compiler_0.11-1_amd64.deb
protobuf-c_0.11-1.diff.gz
  to pool/main/p/protobuf-c/protobuf-c_0.11-1.diff.gz
protobuf-c_0.11-1.dsc
  to pool/main/p/protobuf-c/protobuf-c_0.11-1.dsc
protobuf-c_0.11.orig.tar.gz
  to pool/main/p/protobuf-c/protobuf-c_0.11.orig.tar.gz



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 540...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Robert S. Edmonds  (supplier of updated protobuf-c 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, 23 Aug 2009 13:59:24 -0400
Source: protobuf-c
Binary: protobuf-c-compiler libprotobuf-c0 libprotobuf-c0-dev
Architecture: amd64 source 
Version: 0.11-1
Distribution: unstable
Urgency: low
Maintainer: Robert S. Edmonds 
Changed-By: Robert S. Edmonds 
Closes: 529004 540970
Description:
 libprotobuf-c0 - Protocol Buffers C library
 libprotobuf-c0-dev - Protocol Buffers C static library and headers
 protobuf-c-compiler - protocol buffers C compiler
Changes:
 protobuf-c (0.11-1) unstable; urgency=low
 .
   * New upstream release; closes: #529004.
   * Add build dependency on libprotoc-dev; closes: #540970.
   * Drop .la file from libprotobuf-c0-dev.
Checksums-Sha1: 
 2903df4957be9d78372668b6d00bd79a481c634a 66262 
protobuf-c-compiler_0.11-1_amd64.deb
 4f6962940f46e7a5806fa1bee14a8bd24411a488 38462 
libprotobuf-c0-dev_0.11-1_amd64.deb
 7a26b7c90e1d2675fa2283400f3bd4f0b5219ff4 2606 protobuf-c_0.11-1.diff.gz
 d7f5acdba721b45202fb40e16c7a42a74aefb29b 1147 protobuf-c_0.11-1.dsc
 c2d3e7c18171cfe2aa47411fe332bc856a7c9e10 31098 libprotobuf-c0_0.11-1_amd64.deb
 f9856dff06b9d910c6486dc6e7cbc80df3f89ba4 479307 protobuf-c_0.11.orig.tar.gz
Checksums-Sha256: 
 64eadb2d38ffecb072e7bd8c43634c26041ba98c3290906d66e7feb186e3e146 66262 
protobuf-c-compiler_0.11-1_amd64.deb
 7e50c8b63351b14ce9688503f23ec2ae85d4a81d7a484260a05b5a453ec76fca 479307 
protobuf-c_0.11.orig.tar.gz
 bb1e26fa1b23a651050e799b9aabd3e6a7191268a8fa0eff14eb76d86b63ff61 31098 
libprotobuf-c0_0.11-1_amd64.deb
 795f6b44732dcdb83f511a841a9fc57831b4a0f714760e783196c5ebb50f2c9e 1147 
protobuf-c_0.11-1.dsc
 bd6603a0de170bbc2a2928b06e4468569aad5465e78ee5a5c141dace46813c47 2606 
protobuf-c_0.11-1.diff.gz
 ca13d980a46e25b1c2f21caed80010fc663a8637638025c3aeedb38b7fc57b9e 38462 
libprotobuf-c0-dev_0.11-1_amd64.deb
Files: 
 0635592125c01c558d661083d44d6a51 66262 devel optional 
protobuf-c-compiler_0.11-1_amd64.deb
 3802507ddc42bb2bbddfb11123f2faeb 31098 libs optional 
libprotobuf-c0_0.11-1_amd64.deb
 b073e60d23c113fc39f67d4b0a43c65f 38462 libdevel optional 
libprotobuf-c0-dev_0.11-1_amd64.deb
 86ccefcbdfb620fb9b71b22445c3940f 1147 devel optional protobuf-c_0.11-1.dsc
 cf9deb81ccd1b3e42997194d2a5a20b6 2606 devel optional protobuf-c_0.11-1.diff.gz
 e0ac27d54491d611d066968571f8fe54 479307 devel optional 
protobuf-c_0.11.orig.tar.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqRhq8ACgkQdp+/SHMBQJFUawCfSTxeROfvUQ6yoxNMeut6L6u2
zxcAn0GxgS7xz3WGBNODEvSTFjZXkxlr
=4

Bug#542400: Unable to remove package, post removal script fails

[Michael S Gilbert]

On Sun, 23 Aug 2009 20:49:13 +0200 Bertrand Marc Bertrand wrote:
> I don't think you should remove /usr/lib/fglrx/diversions/libglx.so by 
> hand. This file belongs to xserver-xorg-core (that's why there is a 
> diversion). 

agreed.  that is just a temporary solution to get the problematic
package removed.  it would be a *much* better idea to backup the
file, remove the package, then restore from the backup.

> I think it is related to the fact that fglrx-glx.postrm 
> removes fglrx-driver diversions although it shouldn't. Could you test 
> the last revision in svn (278) ?

will do.

mike



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542400: Unable to remove package, post removal script fails

[Bertrand Marc]

I don't think you should remove /usr/lib/fglrx/diversions/libglx.so by 
hand. This file belongs to xserver-xorg-core (that's why there is a 
diversion). I think it is related to the fact that fglrx-glx.postrm 
removes fglrx-driver diversions although it shouldn't. Could you test 
the last revision in svn (278) ?


Thanks,
Bertrand



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#527719: Status of geordi in unstable

[Chris Lamb]

Chris Lamb wrote:

> [some reasons why it doesn't build in the past]

I can now build it, but the runtime chroot creation needs to be rewritten
due to GCC/glibc changes. The package is unusable without this, hence no
upload.

Ubuntu seems to have uploaded a new version, but it's unclear what they
have done to address this. *shrug*


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org
   `-


signature.asc
Description: PGP signature

Bug#538316: marked as done (postgresql-8.3: FTBFS: couldn't find library libpq.so.5)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 18:04:00 +
with message-id 
and subject line Bug#538316: fixed in postgresql-8.3 8.3.7-4
has caused the Debian Bug report #538316,
regarding postgresql-8.3: FTBFS: couldn't find library libpq.so.5
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.)


-- 
538316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-8.3
Version: 8.3.7-3
Severity: serious

From my pbuilder build log (and it also appears in the buildd logs):

...
dh_installdeb -ppostgresql-8.3 
dh_perl -ppostgresql-8.3 
dh_shlibdeps -ppostgresql-8.3
dpkg-shlibdeps: warning: 
debian/postgresql-8.3/usr/lib/postgresql/8.3/lib/utf8_and_ascii.so contains an 
unresolvable reference to symbol pg_mic2ascii: it's probably a plugin.
dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to 
see them all).
dpkg-shlibdeps: warning: 
debian/postgresql-8.3/usr/lib/postgresql/8.3/lib/utf8_and_sjis.so contains an 
unresolvable reference to symbol UtfToLocal: it's probably a plugin.
dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to 
see them all).
dpkg-shlibdeps: warning: 
debian/postgresql-8.3/usr/lib/postgresql/8.3/lib/dict_snowball.so contains an 
unresolvable reference to symbol errstart: it's probably a plugin.
dpkg-shlibdeps: warning: 19 other similar warnings have been skipped (use -v to 
see them all).
dpkg-shlibdeps: warning: 
debian/postgresql-8.3/usr/lib/postgresql/8.3/lib/latin_and_mic.so contains an 
unresolvable reference to symbol latin2mic: it's probably a plugin.
dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to 
see them all).
dpkg-shlibdeps: warning: 
debian/postgresql-8.3/usr/lib/postgresql/8.3/lib/euc_tw_and_big5.so contains an 
unresolvable reference to symbol report_invalid_encoding: it's probably a 
plugin.
dpkg-shlibdeps: warning: 6 other similar warnings have been skipped (use -v to 
see them all).
dpkg-shlibdeps: warning: 
debian/postgresql-8.3/usr/lib/postgresql/8.3/lib/utf8_and_euc_kr.so contains an 
unresolvable reference to symbol UtfToLocal: it's probably a plugin.
dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to 
see them all).
dpkg-shlibdeps: warning: 
debian/postgresql-8.3/usr/lib/postgresql/8.3/lib/utf8_and_euc_jis_2004.so 
contains an unresolvable reference to symbol UtfToLocal: it's probably a plugin.
dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to 
see them all).
dpkg-shlibdeps: warning: 
debian/postgresql-8.3/usr/lib/postgresql/8.3/lib/ascii_and_mic.so contains an 
unresolvable reference to symbol pg_mic2ascii: it's probably a plugin.
dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to 
see them all).
dpkg-shlibdeps: warning: 
debian/postgresql-8.3/usr/lib/postgresql/8.3/lib/utf8_and_euc_jp.so contains an 
unresolvable reference to symbol UtfToLocal: it's probably a plugin.
dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to 
see them all).
dpkg-shlibdeps: warning: 
debian/postgresql-8.3/usr/lib/postgresql/8.3/lib/euc_cn_and_mic.so contains an 
unresolvable reference to symbol report_invalid_encoding: it's probably a 
plugin.
dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to 
see them all).
dpkg-shlibdeps: error: couldn't find library libpq.so.5 needed by 
debian/postgresql-8.3/usr/lib/postgresql/8.3/bin/pg_ctl (ELF format: 
'elf64-x86-64'; RPATH: '').
Note: libraries are not searched in other binary packages that do not have any 
shlibs or symbols file.
To help dpkg-shlibdeps find private libraries, you might need to set 
LD_LIBRARY_PATH.
dh_shlibdeps: dpkg-shlibdeps returned exit code 2
make: *** [binary-predeb-IMPL/postgresql-8.3] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
-- 
Daniel Schepler



--- End Message ---
--- Begin Message ---
Source: postgresql-8.3
Source-Version: 8.3.7-4

We believe that the bug you reported is fixed in the latest version of
postgresql-8.3, which is due to be installed in the Debian FTP archive:

postgresql-8.3_8.3.7-4.diff.gz
  to pool/main/p/postgresql-8.3/postgresql-8.3_8.3.7-4.diff.gz
postgresql-8.3_8.3.7-4.dsc
  to pool/main/p/postgresql-8.3/postgresql-8.3_8.3.7-4.dsc
postgresql-8.3_8.3.7-4_i386.deb
  to pool/main/p/postgresql-8.3/postgresql-8.3_8.3.7-4_i386.deb
postgresql-client-8.3_8.3.7-4_i386.deb
  to pool/main/p/postgresql-8.3/postgresql-client-8.3_8.3.7-4_i386.deb
postgresql-contrib-8.3_8.3.7

Bug#542133: marked as done (FTBFS: libnettle-dev is gone, replaced (and not provided) by nettle-dev)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 18:03:44 +
with message-id 
and subject line Bug#542133: fixed in pike7.6 7.6.112-5
has caused the Debian Bug report #542133,
regarding FTBFS: libnettle-dev is gone, replaced (and not provided) by 
nettle-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
542133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pike7.6
Version: 7.6.112-4
Severity: serious
Justification: FTBFS

Hi,

libnettle-dev's gone, and replaced by nettle-dev, which replaces it /
conflicts against it, but does not provide it. Your package now FTBFS
accordingly.

Mraw,
KiBi.


--- End Message ---
--- Begin Message ---
Source: pike7.6
Source-Version: 7.6.112-5

We believe that the bug you reported is fixed in the latest version of
pike7.6, which is due to be installed in the Debian FTP archive:

pike7.6-bzip2_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-bzip2_7.6.112-5_amd64.deb
pike7.6-core_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-core_7.6.112-5_amd64.deb
pike7.6-dev_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-dev_7.6.112-5_amd64.deb
pike7.6-doc_7.6.112-5_all.deb
  to pool/main/p/pike7.6/pike7.6-doc_7.6.112-5_all.deb
pike7.6-gdbm_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-gdbm_7.6.112-5_amd64.deb
pike7.6-gl_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-gl_7.6.112-5_amd64.deb
pike7.6-image_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-image_7.6.112-5_amd64.deb
pike7.6-manual_7.6.112-5_all.deb
  to pool/main/p/pike7.6/pike7.6-manual_7.6.112-5_all.deb
pike7.6-meta_7.6.112-5_all.deb
  to pool/main/p/pike7.6/pike7.6-meta_7.6.112-5_all.deb
pike7.6-mysql_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-mysql_7.6.112-5_amd64.deb
pike7.6-odbc_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-odbc_7.6.112-5_amd64.deb
pike7.6-pcre_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-pcre_7.6.112-5_amd64.deb
pike7.6-perl_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-perl_7.6.112-5_amd64.deb
pike7.6-pg_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-pg_7.6.112-5_amd64.deb
pike7.6-reference_7.6.112-5_all.deb
  to pool/main/p/pike7.6/pike7.6-reference_7.6.112-5_all.deb
pike7.6-sane_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-sane_7.6.112-5_amd64.deb
pike7.6-sdl_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-sdl_7.6.112-5_amd64.deb
pike7.6-svg_7.6.112-5_amd64.deb
  to pool/main/p/pike7.6/pike7.6-svg_7.6.112-5_amd64.deb
pike7.6_7.6.112-5.diff.gz
  to pool/main/p/pike7.6/pike7.6_7.6.112-5.diff.gz
pike7.6_7.6.112-5.dsc
  to pool/main/p/pike7.6/pike7.6_7.6.112-5.dsc
pike7.6_7.6.112-5_all.deb
  to pool/main/p/pike7.6/pike7.6_7.6.112-5_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 542...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Magnus Holmgren  (supplier of updated pike7.6 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, 23 Aug 2009 19:00:52 +0200
Source: pike7.6
Binary: pike7.6-core pike7.6 pike7.6-dev pike7.6-manual pike7.6-reference 
pike7.6-doc pike7.6-meta pike7.6-mysql pike7.6-pg pike7.6-odbc pike7.6-svg 
pike7.6-image pike7.6-sdl pike7.6-gdbm pike7.6-gl pike7.6-sane pike7.6-perl 
pike7.6-pcre pike7.6-bzip2
Architecture: source all amd64
Version: 7.6.112-5
Distribution: unstable
Urgency: low
Maintainer: Magnus Holmgren 
Changed-By: Magnus Holmgren 
Description: 
 pike7.6- Recommended metapackage for Pike 7.6
 pike7.6-bzip2 - Bzip2 module for Pike
 pike7.6-core - Powerful interpreted programming language
 pike7.6-dev - Development files for Pike 7.6
 pike7.6-doc - Pike 7.6 documentation metapackage
 pike7.6-gdbm - Gdbm module for Pike
 pike7.6-gl - Mesa module for Pike
 pike7.6-image - Image module for Pike
 pike7.6-manual - Pike 7.6 manual
 pike7.6-meta - Metapackage for Pike 7.6
 pike7.6-mysql - MySQL module for Pike
 pike7.6-odbc - Odbc module for Pike
 pike7.6-pcre - PCRE module for Pike
 pike7.6-perl - Perl module for Pike
 pike7.6-pg - PostgreSQL module for Pike
 pike7.6-reference - Pike 7.6 reference
 pike7.6-sane - SANE module for Pike
 pike7.6-sdl - SDL module for Pike
 pike7.6-svg -

Processed: tagpending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #libspreadsheet-ruby (0.6.4-3) UNRELEASED; urgency=low
> #
> #  * add build dep on ruby1.9 (Closes: #543034)
> #
> package libspreadsheet-ruby libspreadsheet-ruby1.9 libspreadsheet-ruby1.8 
> libspreadsheet-ruby-doc
Limiting to bugs with field 'package' containing at least one of 
'libspreadsheet-ruby', 'libspreadsheet-ruby1.9', 'libspreadsheet-ruby1.8', 
'libspreadsheet-ruby-doc'
Limit currently set to 'package':'libspreadsheet-ruby', 
'libspreadsheet-ruby1.9', 'libspreadsheet-ruby1.8', 'libspreadsheet-ruby-doc'

> tags 543034 + pending confirmed
Bug #543034 [libspreadsheet-ruby] libspreadsheet-ruby: FTBFS: make: 
/usr/bin/ruby1.9: Command not found
Added tag(s) confirmed and pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagpending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #libole-ruby (1.2.9-2) UNRELEASED; urgency=low
> #
> #  * add build dep on ruby1.9 (Closes: #543040)
> #
> package libole-ruby-doc libole-ruby1.9 libole-ruby1.8 libole-ruby
Limiting to bugs with field 'package' containing at least one of 
'libole-ruby-doc', 'libole-ruby1.9', 'libole-ruby1.8', 'libole-ruby'
Limit currently set to 'package':'libole-ruby-doc', 'libole-ruby1.9', 
'libole-ruby1.8', 'libole-ruby'

> tags 543040 + pending confirmed
Bug #543040 [libole-ruby] libole-ruby: FTBFS: make: /usr/bin/ruby1.9: Command 
not found
Added tag(s) confirmed and pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagpending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #libprawn-ruby (0.4.1+dfsg-2) UNRELEASED; urgency=low
> #
> #  * add build dep on ruby 1.9 (Closes: #543035)
> #
> package libprawn-ruby1.9 libprawn-ruby-common libprawn-ruby1.8 libprawn-ruby
Limiting to bugs with field 'package' containing at least one of 
'libprawn-ruby1.9', 'libprawn-ruby-common', 'libprawn-ruby1.8', 'libprawn-ruby'
Limit currently set to 'package':'libprawn-ruby1.9', 'libprawn-ruby-common', 
'libprawn-ruby1.8', 'libprawn-ruby'

> tags 543035 + pending confirmed
Bug #543035 [libprawn-ruby] libprawn-ruby: FTBFS: make: /usr/bin/ruby1.9: 
Command not found
Added tag(s) confirmed and pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542140: fglrx-driver: fglrx driver doesn't work with linux-image-2.6.30 (AMD64)

[Bertrand Marc]

Gary Dale a écrit :
I tried it with both the source and compiled modules with the same 
results. They installed without problems. However, apart from the 
higher refresh rate I'm getting with the fglrx driver, there's not a 
lot of difference between this and the vesa driver. The vesa driver 
still gives a faster display but with some flickering. This is the 
same result I got with manually installing the ATI drivers from the 
AMD web site.


Prior to upgrading to the 2.6.30 kernel, I was getting great results 
from the fglrx driver. Windows would drag smoothly and become 
semi-transparent. I could use the X video extensions for video output 
from Kaffeine, vlc & mplayer  (but the GL video didn't work). And I 
was getting a lot of desktop effects, such as virtual desktops sliding 
from one to another.


Any ideas on why the current driver's performance is so pitiful?


So we are getting closer ! Did you build the module with 
module-assistant ? And could you attach /var/log/Xorg.0.log ?


Thanks
Bertrand



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#543265: pgdesigner: After a long work but saved frequently, the project file still remain almost empty. The work lost.

[Paul Csanyi]

Package: pgdesigner
Version: 1.2.7-1
Severity: grave
Justification: renders package unusable

I worked with pgdesigner 8 hours continuously and saved - or autosaved 
- the project frequently.

Then close pgdesigner.  After a whyle run again pgdesigner, open the 
same project that being worked on, but the whole work lost: the design 
was empty.

-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages pgdesigner depends on:
ii  gambas2-gb-compress   2.7-1  The Gambas compression component
ii  gambas2-gb-compress-bzlib22.7-1  The Gambas bzlib2 component
ii  gambas2-gb-compress-zlib  2.7-1  The Gambas zlib compression compon
ii  gambas2-gb-db 2.7-1  Gambas database access common libr
ii  gambas2-gb-db-postgresql  2.7-1  The PostgreSQL driver for the Gamb
ii  gambas2-gb-form   2.7-1  A gambas native form component
ii  gambas2-gb-pdf2.7-1  The Gambas pdf component
ii  gambas2-gb-qt 2.7-1  The Gambas Qt GUI component
ii  gambas2-gb-qt-ext 2.7-1  The Gambas extended Qt GUI compone
ii  gambas2-gb-qt-kde 2.7-1  The Gambas KDE component
ii  gambas2-gb-qt-kde-html2.7-1  The Gambas KHTML component
ii  gambas2-gb-settings   2.7-1  Gambas utilities class
ii  gambas2-gb-xml2.7-1  Gambas XML component
ii  gambas2-runtime   2.7-1  The Gambas runtime

pgdesigner recommends no packages.

pgdesigner 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#542996: marked as done (python-django: FTBFS: failed tests)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 17:47:54 +
with message-id 
and subject line Bug#542996: fixed in python-django 1.1-3
has caused the Debian Bug report #542996,
regarding python-django: FTBFS: failed tests
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.)


-- 
542996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090822 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Apparently, the package assumes that network access (to google) is
available during the build. That cannot be assumed.

Relevant part:
> ==
> FAIL: Doctest: regressiontests.forms.tests.__test__.fields_tests
> --
> Traceback (most recent call last):
>   File 
> "/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/django/test/_doctest.py",
>  line 2180, in runTest
> raise self.failureException(self.format_failure(new.getvalue()))
> AssertionError: Failed doctest test for 
> regressiontests.forms.tests.__test__.fields_tests
>   File 
> "/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/tests/regressiontests/forms/tests.py",
>  line unknown line number, in fields_tests
> 
> --
> File 
> "/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/tests/regressiontests/forms/tests.py",
>  line ?, in regressiontests.forms.tests.__test__.fields_tests
> Failed example:
> f.clean('http://www.google.com') # This will fail if there's no Internet 
> connection
> Exception raised:
> Traceback (most recent call last):
>   File 
> "/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/django/test/_doctest.py",
>  line 1267, in __run
> compileflags, 1) in test.globs
>   File " regressiontests.forms.tests.__test__.fields_tests[335]>", line 1, in 
> f.clean('http://www.google.com') # This will fail if there's no 
> Internet connection
>   File 
> "/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/django/forms/fields.py",
>  line 580, in clean
> raise ValidationError(self.error_messages['invalid_link'])
> ValidationError: [u'This URL appears to be a broken link.']
> --
> File 
> "/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/tests/regressiontests/forms/tests.py",
>  line ?, in regressiontests.forms.tests.__test__.fields_tests
> Failed example:
> f.clean('http://www.google.com') # This will fail if there's no Internet 
> connection
> Exception raised:
> Traceback (most recent call last):
>   File 
> "/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/django/test/_doctest.py",
>  line 1267, in __run
> compileflags, 1) in test.globs
>   File " regressiontests.forms.tests.__test__.fields_tests[341]>", line 1, in 
> f.clean('http://www.google.com') # This will fail if there's no 
> Internet connection
>   File 
> "/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/django/forms/fields.py",
>  line 580, in clean
> raise ValidationError(self.error_messages['invalid_link'])
> ValidationError: [u'This URL appears to be a broken link.']
> 
> 
> --
> Ran 859 tests in 454.937s
> 
> FAILED (failures=1)
> No json fixture 'initial_data' in 
> '/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/django/contrib/csrf/fixtures'.
> Trying 
> '/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/django/contrib/csrf/fixtures'
>  for initial_data.json.zip fixture 'initial_data'...
> No json fixture 'initial_data' in 
> '/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/django/contrib/csrf/fixtures'.
> Trying 
> '/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/django/contrib/csrf/fixtures'
>  for initial_data.json.bz2 fixture 'initial_data'...
> No json fixture 'initial_data' in 
> '/build/user-python-django_1.1-2-amd64-rLoEmd/python-django-1.1/django/contrib/csrf/fixtures'.
> Checking absolute path for fixtures...
> Trying absolute path for initial_data.xml fixture 'initial_data'...
> No xml fixture 'initial_data' in absolute path.
> Trying absolute path f

Bug#543263: blcr_0.8.2-2 FTBFS on sparc (dist=unstable)

[Martin Zobel-Helas]

Package: blcr
Version: 0.8.2-2
Severity: serious

> checking for value of CR_ASM_OP_HAND_CHKPT... 2147787009
> checking for value of CR_ASM_CHECKPOINT_STUB... 16384
> checking for value of CR_ASM_OP_HAND_ABORT... 2147787010
> checking for value of CR_ASM_CHECKPOINT_OMIT... 4
> checking for value of CR_ASM_SI_PID_OFFSET... 12
> checking for value of CR_ASM_NR_ioctl... 54
> checking for value of CR_ASM_NR_rt_sigreturn... 101
> checking for direction of stack growth... down
> checking for value of CR_SIGNUM... 64
> checking for void *... (cached) yes
> checking size of void *... (cached) 4
> configure: error: --enable-multilib not supported on architecture sparc
> make: *** [build-arch-stamp] Error 1
> dpkg-buildpackage: error: debian/rules build gave error exit status 2



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: setting package to pike7.6-pcre pike7.6-sdl pike7.6-manual pike7.6-perl pike7.6-gl pike7.6-meta pike7.6-odbc pike7.6-bzip2 pike7.6-mysql pike7.6-pg pike7.6-core pike7.6-doc pike7.6-gdbm pik

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #pike7.6 (7.6.112-5) unstable; urgency=low
> #
> #  * Switch to Nettle 2.0 (Build-Depend on nettle-dev instead of
> #libnettle-dev) (Closes: #542133).
> #+ nettle_2.0.dpatch: Changes from upstream CVS needed to accommodate the
> #  API changes.
> #
> package pike7.6-pcre pike7.6-sdl pike7.6-manual pike7.6-perl pike7.6-gl 
> pike7.6-meta pike7.6-odbc pike7.6-bzip2 pike7.6-mysql pike7.6-pg pike7.6-core 
> pike7.6-doc pike7.6-gdbm pike7.6-image pike7.6-reference pike7.6-svg 
> pike7.6-dev pike7.6 pike7.6-sane
Limiting to bugs with field 'package' containing at least one of 
'pike7.6-pcre', 'pike7.6-sdl', 'pike7.6-manual', 'pike7.6-perl', 'pike7.6-gl', 
'pike7.6-meta', 'pike7.6-odbc', 'pike7.6-bzip2', 'pike7.6-mysql', 'pike7.6-pg', 
'pike7.6-core', 'pike7.6-doc', 'pike7.6-gdbm', 'pike7.6-image', 
'pike7.6-reference', 'pike7.6-svg', 'pike7.6-dev', 'pike7.6', 'pike7.6-sane'
Limit currently set to 'package':'pike7.6-pcre', 'pike7.6-sdl', 
'pike7.6-manual', 'pike7.6-perl', 'pike7.6-gl', 'pike7.6-meta', 'pike7.6-odbc', 
'pike7.6-bzip2', 'pike7.6-mysql', 'pike7.6-pg', 'pike7.6-core', 'pike7.6-doc', 
'pike7.6-gdbm', 'pike7.6-image', 'pike7.6-reference', 'pike7.6-svg', 
'pike7.6-dev', 'pike7.6', 'pike7.6-sane'

> tags 542133 + pending
Bug #542133 [pike7.6] FTBFS: libnettle-dev is gone, replaced (and not provided) 
by nettle-dev
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagging 543077

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny3
> tags 543077 + pending
Bug #543077 [jack-audio-connection-kit] jack-audio-connection-kit: FTBFS: 
/usr/bin/install: will not overwrite just-created 
`/build/user-jack-audio-connection-kit_0.116.2+svn3592-2-amd64-13Mg76/jack-audio-connection-kit-0.116.2+svn3592/debian/tmp//usr/share/man/man1/alsa_in.1'
 with `alsa_in.1'
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#543031: [hlx] Error messages from Emacs 22.3

[tom sgouros]

I'll fix it and put out a sub-release this week.

Thanks,

 -tom


Roland Stigge  wrote:

> Hi,
> 
> this error now also hits the Debian archive where it fails to build
> from source now. Should we rely on an official new hyperlatex version
> or try to introduce a Debian specific fix?
> 
> Thanks,
> 
> Roland
> 
> 
> Tomer Altman wrote:
> > In hyperlatex-format-newcommand:
> > hyperlatex.el:1241:42:Warning: `string-to-int' is an obsolete
> > function (as of
> > Emacs 22.1); use `string-to-number' instead.
> >
> > In hyperlatex-format-providecommand:
> > hyperlatex.el:1254:46:Warning: `string-to-int' is an obsolete
> > function (as of
> > Emacs 22.1); use `string-to-number' instead.
> >
> > In hyperlatex-format-newenvironment:
> > hyperlatex.el:1277:48:Warning: `string-to-int' is an obsolete
> > function (as of
> > Emacs 22.1); use `string-to-number' instead.
> >
> > In hyperlatex-format-makemenu:
> > hyperlatex.el:2121:17:Warning: `string-to-int' is an obsolete
> > function (as of
> > Emacs 22.1); use `string-to-number' instead.
> >
> > In hyperlatex-format-setcounter:
> > hyperlatex.el:3391:18:Warning: `string-to-int' is an obsolete
> > function (as of
> > Emacs 22.1); use `string-to-number' instead.
> >
> > In hyperlatex-format-addtocounter:
> > hyperlatex.el:3408:18:Warning: `string-to-int' is an obsolete
> > function (as of
> > Emacs 22.1); use `string-to-number' instead.
> > Wrote /usr/local/lib/hyperlatex/hyperlatex.elc
> > GNU Emacs 22.3.1
> > Copyright (C) 2008 Free Software Foundation, Inc.
> > GNU Emacs comes with ABSOLUTELY NO WARRANTY.
> > You may redistribute copies of Emacs
> > under the terms of the GNU General Public License.
> > For more information about these matters, see the file named COPYING.
> >
> 


-- 
 
 tomfool at as220 dot org
 http://sgouros.com  
 http://whatcheer.net



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#541116: marked as done (gnu-fdisk: FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 16:55:26 +
with message-id 
and subject line Bug#541116: fixed in gnu-fdisk 1.2.3-1
has caused the Debian Bug report #541116,
regarding gnu-fdisk: FTBFS
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.)


-- 
541116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnu-fdisk
Version: 1.2.2-1
Severity: serious

As you can see from the output below, the package FTBFS with an up to
date sid system:

,
| checking for uuid_generate in -luuid... yes
| checking for ped_device_read in -lparted... yes
| checking for libparted - version >= 1.7.0... UNKNOWN-dirty, bad version string
| no
| configure: error: *** libparted >= 1.7.0 not installed - please install first 
***
| make: *** [config.status] Error 1
| dpkg-buildpackage: error: debian/rules build gave error exit status 2
| rbr...@chagas:/tmp/gnu-fdisk-1.2.2$ dpkg --status libparted1.8-dev | grep 
Version
| Version: 1.8.8.git.2009.07.19-3
| rbr...@chagas:/tmp/gnu-fdisk-1.2.2$ 
`

While it is trivial to make the configure step be bypassed, since we
have a suitable library, the program (even if I use the updated 1.2.3
version from upstream) still segfaults with a memory leak.

Running it under valgrind shows a scary leak. :-/

Here is the output of a 1.2.3 compiled version:

,
| (...)
|Device Boot  Start End  Blocks   Id  System 
| ==15707== Invalid read of size 1
| ==15707==at 0x4C24092: strlen (mc_replace_strmem.c:242)
| ==15707==by 0x597242D: vfprintf (in /lib/libc-2.9.so)
| ==15707==by 0x5978499: printf (in /lib/libc-2.9.so)
| ==15707==by 0x405455: do_print (fdisk.c:1100)
| ==15707==by 0x408563: fdisk_do_list_devices (fdisk.c:1331)
| ==15707==by 0x40FE2B: fdisk_interactive_mode (ui.c:732)
| ==15707==by 0x408662: fdisk (fdisk.c:2844)
| ==15707==by 0x594A5C5: (below main) (in /lib/libc-2.9.so)
| ==15707==  Address 0xff is not stack'd, malloc'd or (recently) free'd
| ==15707== 
`

Apparently, the string used there is causing the strlen to run out of
bounds.


Regards, Rogério Brito.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31-rc5-1rb.pre6 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf-8, LC_CTYPE=pt_BR.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnu-fdisk depends on:
ii  libc6 2.9-24 GNU C Library: Shared libraries
ii  libncurses5   5.7+20090803-1 shared libraries for terminal hand
pn  libparted1.8-10(no description available)
ii  libreadline5  5.2-5  GNU readline and history libraries
ii  libuuid1  2.16-2.1   Universally Unique ID library

gnu-fdisk recommends no packages.

gnu-fdisk suggests no packages.

-- 
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org


--- End Message ---
--- Begin Message ---
Source: gnu-fdisk
Source-Version: 1.2.3-1

We believe that the bug you reported is fixed in the latest version of
gnu-fdisk, which is due to be installed in the Debian FTP archive:

gnu-fdisk_1.2.3-1.diff.gz
  to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3-1.diff.gz
gnu-fdisk_1.2.3-1.dsc
  to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3-1.dsc
gnu-fdisk_1.2.3-1_i386.deb
  to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3-1_i386.deb
gnu-fdisk_1.2.3.orig.tar.gz
  to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3.orig.tar.gz



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 541...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xavier Oswald  (supplier of updated gnu-fdisk 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: Fri, 21 Aug 2009 18:55:22 +0200
Source: gnu-fdisk
Binary: gnu-fdisk
Architecture: source i386
Version: 1.2.3-1
Distribution: unstable
Urgency: low
Maintainer: Parted Maintainer Team 
Changed-By: Xavier Oswald 
Description: 
 gnu-fdisk  - Linux fdisk replacement based

Bug#543031: [hlx] Error messages from Emacs 22.3

[Roland Stigge]

Great!

Would you also please have a look at the following bugs:

1) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517934 :

   Hyperlatex ERROR: Unknown command: HlxModeLevelUp

2) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473795 :

   htmlcaption generates wrong html code

Thanks!

bye,
  Roland


tom sgouros wrote:

I'll fix it and put out a sub-release this week.

Thanks,

 -tom


Roland Stigge  wrote:


Hi,

this error now also hits the Debian archive where it fails to build
from source now. Should we rely on an official new hyperlatex version
or try to introduce a Debian specific fix?

Thanks,

Roland


Tomer Altman wrote:

In hyperlatex-format-newcommand:
hyperlatex.el:1241:42:Warning: `string-to-int' is an obsolete
function (as of
Emacs 22.1); use `string-to-number' instead.

In hyperlatex-format-providecommand:
hyperlatex.el:1254:46:Warning: `string-to-int' is an obsolete
function (as of
Emacs 22.1); use `string-to-number' instead.

In hyperlatex-format-newenvironment:
hyperlatex.el:1277:48:Warning: `string-to-int' is an obsolete
function (as of
Emacs 22.1); use `string-to-number' instead.

In hyperlatex-format-makemenu:
hyperlatex.el:2121:17:Warning: `string-to-int' is an obsolete
function (as of
Emacs 22.1); use `string-to-number' instead.

In hyperlatex-format-setcounter:
hyperlatex.el:3391:18:Warning: `string-to-int' is an obsolete
function (as of
Emacs 22.1); use `string-to-number' instead.

In hyperlatex-format-addtocounter:
hyperlatex.el:3408:18:Warning: `string-to-int' is an obsolete
function (as of
Emacs 22.1); use `string-to-number' instead.
Wrote /usr/local/lib/hyperlatex/hyperlatex.elc
GNU Emacs 22.3.1
Copyright (C) 2008 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.









--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#533940: marked as done (gnu-fdisk: FTBFS: fdisk.c:1119: undefined reference to `ped_free')

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 16:55:24 +
with message-id 
and subject line Bug#533940: fixed in gnu-fdisk 1.2.3-1
has caused the Debian Bug report #533940,
regarding gnu-fdisk: FTBFS: fdisk.c:1119: undefined reference to `ped_free'
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.)


-- 
533940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnu-fdisk
Version: 1.2.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> x86_64-linux-gnu-gcc  -Wall -g -O2 -D_FILE_OFFSET_BITS=no  -Wl,-z,defs -o 
> fdisk main.o command.o fdisk.o common.o hacks.o strlist.o ui.o -lparted 
> -luuid  -ldl -ltermcap -lreadline
> fdisk.o: In function `do_print':
> /build/user-gnu-fdisk_1.2.2-1-amd64-1v9IYA/gnu-fdisk-1.2.2/src/fdisk.c:1119: 
> undefined reference to `ped_free'
> fdisk.o: In function `do_mkpart':
> /build/user-gnu-fdisk_1.2.2-1-amd64-1v9IYA/gnu-fdisk-1.2.2/src/fdisk.c:682: 
> undefined reference to `ped_free'
> fdisk.o: In function `part_xprint':
> /build/user-gnu-fdisk_1.2.2-1-amd64-1v9IYA/gnu-fdisk-1.2.2/src/fdisk.c:1164: 
> undefined reference to `ped_free'
> /build/user-gnu-fdisk_1.2.2-1-amd64-1v9IYA/gnu-fdisk-1.2.2/src/fdisk.c:1169: 
> undefined reference to `ped_free'
> common.o: In function `check_partition_consistency':
> /build/user-gnu-fdisk_1.2.2-1-amd64-1v9IYA/gnu-fdisk-1.2.2/src/common.c:2370: 
> undefined reference to `ped_free'
> common.o:/build/user-gnu-fdisk_1.2.2-1-amd64-1v9IYA/gnu-fdisk-1.2.2/src/common.c:183:
>  more undefined references to `ped_free' follow
> collect2: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/06/20/gnu-fdisk_1.2.2-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: gnu-fdisk
Source-Version: 1.2.3-1

We believe that the bug you reported is fixed in the latest version of
gnu-fdisk, which is due to be installed in the Debian FTP archive:

gnu-fdisk_1.2.3-1.diff.gz
  to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3-1.diff.gz
gnu-fdisk_1.2.3-1.dsc
  to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3-1.dsc
gnu-fdisk_1.2.3-1_i386.deb
  to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3-1_i386.deb
gnu-fdisk_1.2.3.orig.tar.gz
  to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3.orig.tar.gz



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 533...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xavier Oswald  (supplier of updated gnu-fdisk 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: Fri, 21 Aug 2009 18:55:22 +0200
Source: gnu-fdisk
Binary: gnu-fdisk
Architecture: source i386
Version: 1.2.3-1
Distribution: unstable
Urgency: low
Maintainer: Parted Maintainer Team 
Changed-By: Xavier Oswald 
Description: 
 gnu-fdisk  - Linux fdisk replacement based on libparted
Closes: 511035 516514 533940 536400 541085 541116
Changes: 
 gnu-fdisk (1.2.3-1) unstable; urgency=low
 .
   * New upstream release
   * Remove pointer.patch, fixed upstream
   * debian/control:
 - Remove quilt depends
 + Add Depends on dpkg (>= 1.15.4) | install-info
 + Bump Standards-Version to 3.8.3
   * Fix a needed recompilation (Closes: #541085)
   * Fix FTBFS(Closes: #533940, #541116)
   * Fix man page unavailable (Closes: #536400)
   * Fix expert mode has been removed (Closes: #516514)
   * Fix ext3 partitions working (Closes: #511035)
Checksums-Sha1: 
 bbac8646451a22cc5156197702991041e02e545f 1191 gnu-fdisk_1.2.3-1.dsc
 2764f07a7e3257904981a6590621c4ef223ba4c5 457944 gnu-fdisk_1.2.3.orig.tar.gz
 e8748d88ad6bf44430c5177a5fe4

Processed: tagging 538316

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 538316 pending
Bug #538316 [postgresql-8.3] postgresql-8.3: FTBFS: couldn't find library 
libpq.so.5
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 542996 + pending
Bug #542996 [python-django] python-django: FTBFS: failed tests
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#541085: marked as done (gnu-fdisk depends on libparted1.8-10 (>= 1.8.8.git.2008.03.24-9) [UNAVAILABLE])

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 16:55:26 +
with message-id 
and subject line Bug#541085: fixed in gnu-fdisk 1.2.3-1
has caused the Debian Bug report #541085,
regarding gnu-fdisk depends on libparted1.8-10 (>= 1.8.8.git.2008.03.24-9) 
[UNAVAILABLE]
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.)


-- 
541085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnu-fdisk
Version: 1.2.2-1
Severity: grave
Reason: "grave - A bug that renders the package unusable in all or nearly all 
situations."

Subject says it all.

It would seem that just a recompilation would fix this (if libparted*
has not changed its interface, that is).


Regards, Rogério Brito.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31-rc5-1rb.pre6 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf-8, LC_CTYPE=pt_BR.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnu-fdisk depends on:
ii  libc6 2.9-24 GNU C Library: Shared libraries
ii  libncurses5   5.7+20090803-1 shared libraries for terminal hand
pn  libparted1.8-10(no description available)
ii  libreadline5  5.2-5  GNU readline and history libraries
ii  libuuid1  2.16-2.1   Universally Unique ID library

gnu-fdisk recommends no packages.

gnu-fdisk suggests no packages.

-- 
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org


--- End Message ---
--- Begin Message ---
Source: gnu-fdisk
Source-Version: 1.2.3-1

We believe that the bug you reported is fixed in the latest version of
gnu-fdisk, which is due to be installed in the Debian FTP archive:

gnu-fdisk_1.2.3-1.diff.gz
  to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3-1.diff.gz
gnu-fdisk_1.2.3-1.dsc
  to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3-1.dsc
gnu-fdisk_1.2.3-1_i386.deb
  to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3-1_i386.deb
gnu-fdisk_1.2.3.orig.tar.gz
  to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3.orig.tar.gz



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 541...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xavier Oswald  (supplier of updated gnu-fdisk 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: Fri, 21 Aug 2009 18:55:22 +0200
Source: gnu-fdisk
Binary: gnu-fdisk
Architecture: source i386
Version: 1.2.3-1
Distribution: unstable
Urgency: low
Maintainer: Parted Maintainer Team 
Changed-By: Xavier Oswald 
Description: 
 gnu-fdisk  - Linux fdisk replacement based on libparted
Closes: 511035 516514 533940 536400 541085 541116
Changes: 
 gnu-fdisk (1.2.3-1) unstable; urgency=low
 .
   * New upstream release
   * Remove pointer.patch, fixed upstream
   * debian/control:
 - Remove quilt depends
 + Add Depends on dpkg (>= 1.15.4) | install-info
 + Bump Standards-Version to 3.8.3
   * Fix a needed recompilation (Closes: #541085)
   * Fix FTBFS(Closes: #533940, #541116)
   * Fix man page unavailable (Closes: #536400)
   * Fix expert mode has been removed (Closes: #516514)
   * Fix ext3 partitions working (Closes: #511035)
Checksums-Sha1: 
 bbac8646451a22cc5156197702991041e02e545f 1191 gnu-fdisk_1.2.3-1.dsc
 2764f07a7e3257904981a6590621c4ef223ba4c5 457944 gnu-fdisk_1.2.3.orig.tar.gz
 e8748d88ad6bf44430c5177a5fe4028b567821b2 19111 gnu-fdisk_1.2.3-1.diff.gz
 8c9a3a7e538a12e8c4a09d4abccb0c45c90f25b2 109686 gnu-fdisk_1.2.3-1_i386.deb
Checksums-Sha256: 
 668df061234b455d8e500ff30fc7999403de0b9277d4262659bc2949764094b1 1191 
gnu-fdisk_1.2.3-1.dsc
 28b53a27b96eb0bfd6b613162503f29b88fd244614044a93964c6a3b212b5519 457944 
gnu-fdisk_1.2.3.orig.tar.gz
 6e9832843b6a77e6887848c35e1e00327b6d05064632275382fa342934e1a435 19111 
gnu-fdisk_1.2.3-1.diff.gz
 af35d2507009b8591b78eb2463f9340dd4e8724a8febd02f77539dc0ff784605 109686 
gnu-fdisk_1.2.3-1_i386.deb
Files: 
 b9a7550e3abe433c4da6138b45e871df 1191 utils extra gnu-fdisk_1.2.3-1.dsc
 a2d1267474eab7a188

Bug#543031: [hlx] Error messages from Emacs 22.3

[Roland Stigge]

Hi,

this error now also hits the Debian archive where it fails to build from 
source now. Should we rely on an official new hyperlatex version or try 
to introduce a Debian specific fix?


Thanks,

Roland


Tomer Altman wrote:

In hyperlatex-format-newcommand:
hyperlatex.el:1241:42:Warning: `string-to-int' is an obsolete function 
(as of

Emacs 22.1); use `string-to-number' instead.

In hyperlatex-format-providecommand:
hyperlatex.el:1254:46:Warning: `string-to-int' is an obsolete function 
(as of

Emacs 22.1); use `string-to-number' instead.

In hyperlatex-format-newenvironment:
hyperlatex.el:1277:48:Warning: `string-to-int' is an obsolete function 
(as of

Emacs 22.1); use `string-to-number' instead.

In hyperlatex-format-makemenu:
hyperlatex.el:2121:17:Warning: `string-to-int' is an obsolete function 
(as of

Emacs 22.1); use `string-to-number' instead.

In hyperlatex-format-setcounter:
hyperlatex.el:3391:18:Warning: `string-to-int' is an obsolete function 
(as of

Emacs 22.1); use `string-to-number' instead.

In hyperlatex-format-addtocounter:
hyperlatex.el:3408:18:Warning: `string-to-int' is an obsolete function 
(as of

Emacs 22.1); use `string-to-number' instead.
Wrote /usr/local/lib/hyperlatex/hyperlatex.elc
GNU Emacs 22.3.1
Copyright (C) 2008 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.






--
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#533938: libpoex-role-sessioninstantiation-perl: FTBFS: tests failed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 533938 + pending
Bug #533938 [libpoex-role-sessioninstantiation-perl] 
libpoex-role-sessioninstantiation-perl: FTBFS: tests failed
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#533938: libpoex-role-sessioninstantiation-perl: FTBFS: tests failed

[gregor herrmann]

tag 533938 + pending
thanks

On Sun, 21 Jun 2009 16:44:45 +0200, Lucas Nussbaum wrote:

> During a rebuild of all packages in sid, your package failed to build on
> amd64.

The new upstream release 0.092280-1 doesn't FTBFS anymore.
At the moment it waits for the new (build) dependency
libpoex-types-perl (ITP: #543255, already in NEW).

Cheers,
gregor

-- 
 .''`.   http://info.comodo.priv.at/ -- GPG Key IDs: 0x00F3CFE4, 0x8649AA06
 : :' :  Debian GNU/Linux user, admin, & developer - http://www.debian.org/
 `. `'   Member of VIBE!AT, SPI Inc., fellow of FSFE | http://got.to/quote/
   `-NP: Bob Dylan: A Hard Rain's A-Gonna Fall


signature.asc
Description: Digital signature

Bug#541955: marked as done (dtrx: python-syck build-dependency no longer in Debian)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 16:49:36 +
with message-id 
and subject line Bug#541955: fixed in dtrx 6.5-2
has caused the Debian Bug report #541955,
regarding dtrx: python-syck build-dependency no longer in Debian
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.)


-- 
541955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dtrx
Severity: serious

As subject says, the python-syck is no longer in Debian (too buggy).

Your package is easy to fix (just replace it with python-yaml and change
the one test and you are done).

-- 
bye, Joerg
 one imagines he'll be campaigning with a grass-roots "free auric"
 stance
 or possibly "kill DanielS"
 Hmm, both powerful platforms.


--- End Message ---
--- Begin Message ---
Source: dtrx
Source-Version: 6.5-2

We believe that the bug you reported is fixed in the latest version of
dtrx, which is due to be installed in the Debian FTP archive:

dtrx_6.5-2.diff.gz
  to pool/main/d/dtrx/dtrx_6.5-2.diff.gz
dtrx_6.5-2.dsc
  to pool/main/d/dtrx/dtrx_6.5-2.dsc
dtrx_6.5-2_all.deb
  to pool/main/d/dtrx/dtrx_6.5-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 541...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Miguelangel Jose Freitas Loreto  (supplier of 
updated dtrx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 17 Aug 2009 08:54:34 -0430
Source: dtrx
Binary: dtrx
Architecture: source all
Version: 6.5-2
Distribution: unstable
Urgency: low
Maintainer: Miguelangel Jose Freitas Loreto 
Changed-By: Miguelangel Jose Freitas Loreto 
Description: 
 dtrx   - intelligently extract multiple archive types
Closes: 541955
Changes: 
 dtrx (6.5-2) unstable; urgency=low
 .
   * debian/control:
 - B-D-I: Using python-yaml instead of python-syck (Closes: #541955).
 - Standards-Version: 3.8.3
Checksums-Sha1: 
 1b61e355e32bd64b11759a3f795b21e1b7b0f629 1801 dtrx_6.5-2.dsc
 0f1af043ff09cbb532b563e16e035e94da7c3dea 2090 dtrx_6.5-2.diff.gz
 bee4d052f04c68b9d5060f337e07e0b4997d3b97 22868 dtrx_6.5-2_all.deb
Checksums-Sha256: 
 cbbda0f0f09178c61b09cfc5e198036b39a954b488d8c94b50f68be340d73b71 1801 
dtrx_6.5-2.dsc
 08b6cb23a783cc87c49e365ce3c4712c4e5e3cab799609e9b1790a00aa1e887b 2090 
dtrx_6.5-2.diff.gz
 ea0563c3ca2793b1b6d46950d90e960a7451680167d5a8e2835e9b8c0c64a2c3 22868 
dtrx_6.5-2_all.deb
Files: 
 600607fe6ffa48cc19d02be52b45bd36 1801 utils optional dtrx_6.5-2.dsc
 d2317995ee770518a1227d8224a1e4c7 2090 utils optional dtrx_6.5-2.diff.gz
 3dd874e89cd48d06dd3fb9efe1f77e19 22868 utils optional dtrx_6.5-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBAgAGBQJKkWPEAAoJEBxXDIkOS9Crsw0P/1u6V/atmJkn0myRsvdYKDlC
A7kakk7UY0Fl4a1Lyz21WWDlvWwUm1kMW2bKJHRMVSy0sor2ldmihisnnSKG/P+6
iAwWB+be9XJh0nGgmJhQ5JvZU3fb5tDLO6dAM+JxWg6b5VlX0YtMc0JBTqiR/pBL
QmdrY5BtN/PVm42kzHM3VRRi4RScXWC4R4IeB3/+kNPjn6YuEDkp+BMxW4ty27FD
U0B2cTc5T1uqLb6zHgJtuLwh2BuysphtHNT4r3eT68T5CD7FF3JTJSROQ2YVIfBZ
47OPxdTKcz8U7UfrZ2N0Fky5ttQBmdrArwnIBchs49DSN/BaqSScTwkF8t8uQ/HX
YcvQD99dFiLUvJD4ityW59DXbTReGPGLr1DnUWfOWafcuW3bQCOuNhUtwRL/jSKZ
GR8bBn4rfnir8kfP59WbeNOfZwA3rmeZ7u8VoDal7ezMg4Hky0F7CcdSYV/cI3L0
4D6X2hkqPcsO6CVQ8Xz2BeQmDXzOZy869idz0edH1ssZIO6INHebh+UA/lBvslv9
p8uRKbBEakYxVTCLL7TKJaltzT3o0Qlsi3mTLNBdS9ESqk5+8Bg1YhPvRd6emPpe
2Asn82UAd2ny+59G+FFB/z+ZgopwliqBdoPIJ/MeVKGggBw09ut8hsS9QQrPCV5M
iKr4+CT4M5v4x+np9lU4
=XUnf
-END PGP SIGNATURE-


--- End Message ---

Bug#542847: marked as done ([libc6-i386] Can't upgrade Sid)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 16:54:41 +
with message-id 
and subject line Bug#537466: fixed in gcc-4.4 4.4.1-3
has caused the Debian Bug report #537466,
regarding [libc6-i386] Can't upgrade Sid
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.)


-- 
537466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-i386
Version: 2.9-18
Severity: normal

--- Please enter the report below this line. ---

Error message of "aptitude safe-upgrade":

E: Couldn't configure pre-depend libc6-i386 for lib32stdc++6, probably a 
dependency cycle.

--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.30-1-amd64

Debian Release: squeeze/sid
  500 unstablewww.debian-multimedia.org 
  500 unstablehttp.us.debian.org 

--- Package information. ---
Depends  (Version) | Installed
==-+-===
libc6   (= 2.9-18) | 2.9-18


Package's Recommends field is empty.

Package's Suggests field is empty.






-- 
ASD Consultoria, Rio, RJ
Arq. Sávio M Ramos
Só usamos Linux desde 2000
www.debian.org


--- End Message ---
--- Begin Message ---
Source: gcc-4.4
Source-Version: 4.4.1-3

We believe that the bug you reported is fixed in the latest version of
gcc-4.4, which is due to be installed in the Debian FTP archive:

cpp-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/cpp-4.4_4.4.1-3_i386.deb
fixincludes_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/fixincludes_4.4.1-3_i386.deb
g++-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/g++-4.4-multilib_4.4.1-3_i386.deb
g++-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/g++-4.4_4.4.1-3_i386.deb
gcc-4.4-base_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gcc-4.4-base_4.4.1-3_i386.deb
gcc-4.4-locales_4.4.1-3_all.deb
  to pool/main/g/gcc-4.4/gcc-4.4-locales_4.4.1-3_all.deb
gcc-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gcc-4.4-multilib_4.4.1-3_i386.deb
gcc-4.4-source_4.4.1-3_all.deb
  to pool/main/g/gcc-4.4/gcc-4.4-source_4.4.1-3_all.deb
gcc-4.4_4.4.1-3.diff.gz
  to pool/main/g/gcc-4.4/gcc-4.4_4.4.1-3.diff.gz
gcc-4.4_4.4.1-3.dsc
  to pool/main/g/gcc-4.4/gcc-4.4_4.4.1-3.dsc
gcc-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gcc-4.4_4.4.1-3_i386.deb
gfortran-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gfortran-4.4-multilib_4.4.1-3_i386.deb
gfortran-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gfortran-4.4_4.4.1-3_i386.deb
gobjc++-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc++-4.4-multilib_4.4.1-3_i386.deb
gobjc++-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc++-4.4_4.4.1-3_i386.deb
gobjc-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc-4.4-multilib_4.4.1-3_i386.deb
gobjc-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc-4.4_4.4.1-3_i386.deb
lib64gcc1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gcc1-dbg_4.4.1-3_i386.deb
lib64gcc1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gcc1_4.4.1-3_i386.deb
lib64gfortran3-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gfortran3-dbg_4.4.1-3_i386.deb
lib64gfortran3_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gfortran3_4.4.1-3_i386.deb
lib64gomp1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gomp1-dbg_4.4.1-3_i386.deb
lib64gomp1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gomp1_4.4.1-3_i386.deb
lib64mudflap0-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64mudflap0-dbg_4.4.1-3_i386.deb
lib64mudflap0_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64mudflap0_4.4.1-3_i386.deb
lib64objc2-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64objc2-dbg_4.4.1-3_i386.deb
lib64objc2_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64objc2_4.4.1-3_i386.deb
lib64stdc++6-4.4-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64stdc++6-4.4-dbg_4.4.1-3_i386.deb
lib64stdc++6_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64stdc++6_4.4.1-3_i386.deb
libgcc1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgcc1-dbg_4.4.1-3_i386.deb
libgcc1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgcc1_4.4.1-3_i386.deb
libgfortran3-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgfortran3-dbg_4.4.1-3_i386.deb
libgfortran3_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgfortran3_4.4.1-3_i386.deb
libgomp1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgomp1-dbg_4.4.1-3_i386.deb
libgomp1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgomp1_4.4.1-3_i386.deb
libmudflap0-4.4-dev_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libmudflap0-4.4-dev_4.4.1-3_i386.deb
libmudflap0-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libmudflap0-dbg_4.4.1-3_i386.deb
libmudflap0_4.4.1-3_i386.deb
  to pool/main/g/

Bug#539151: inotifyx - FTBFS

[Y Giridhar Appaji Nag]

On 09/08/23 15:53 +0200, Bastian Blank said ...
> You seem to have a large missunderstanding how to build Debian packages,
> especially what the difference between arch indenpendent and arch
> dependent is. Also your sponsor (cced) either did not review the

It certainly looks like I did a poor job of reviewing this.  Thank you for
pointing out.

Ritesh, inotifyx being "Arch: any" should have binary-arch (and not
binary-indep) creating the binary package.  Please make the changes and we can
do another upload fixing this.  Do take a look at policy section 4.9 before
that.

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/


signature.asc
Description: Digital signature

Bug#537466: marked as done (Couldn't configure pre-depend libc6-i386 for lib32stdc++6)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 16:54:41 +
with message-id 
and subject line Bug#537466: fixed in gcc-4.4 4.4.1-3
has caused the Debian Bug report #537466,
regarding Couldn't configure pre-depend libc6-i386 for lib32stdc++6
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.)


-- 
537466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-i386
Version: 2.9-19
Severity: normal


I haven't updated my system since a week a go or so, and when running aptitude 
update && aptitude safe-upgrade, I get : 

Fetched 1492kB in 2s (626kB/s)
E: Couldn't configure pre-depend libc6-i386 for lib32stdc++6, probably a 
dependency cycle.
A package failed to install.  Trying to recover:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done


-- 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.31-rc3 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libc6-i386 depends on:
ii  libc6 2.9-19 GNU C Library: Shared libraries

libc6-i386 recommends no packages.

libc6-i386 suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: gcc-4.4
Source-Version: 4.4.1-3

We believe that the bug you reported is fixed in the latest version of
gcc-4.4, which is due to be installed in the Debian FTP archive:

cpp-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/cpp-4.4_4.4.1-3_i386.deb
fixincludes_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/fixincludes_4.4.1-3_i386.deb
g++-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/g++-4.4-multilib_4.4.1-3_i386.deb
g++-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/g++-4.4_4.4.1-3_i386.deb
gcc-4.4-base_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gcc-4.4-base_4.4.1-3_i386.deb
gcc-4.4-locales_4.4.1-3_all.deb
  to pool/main/g/gcc-4.4/gcc-4.4-locales_4.4.1-3_all.deb
gcc-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gcc-4.4-multilib_4.4.1-3_i386.deb
gcc-4.4-source_4.4.1-3_all.deb
  to pool/main/g/gcc-4.4/gcc-4.4-source_4.4.1-3_all.deb
gcc-4.4_4.4.1-3.diff.gz
  to pool/main/g/gcc-4.4/gcc-4.4_4.4.1-3.diff.gz
gcc-4.4_4.4.1-3.dsc
  to pool/main/g/gcc-4.4/gcc-4.4_4.4.1-3.dsc
gcc-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gcc-4.4_4.4.1-3_i386.deb
gfortran-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gfortran-4.4-multilib_4.4.1-3_i386.deb
gfortran-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gfortran-4.4_4.4.1-3_i386.deb
gobjc++-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc++-4.4-multilib_4.4.1-3_i386.deb
gobjc++-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc++-4.4_4.4.1-3_i386.deb
gobjc-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc-4.4-multilib_4.4.1-3_i386.deb
gobjc-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc-4.4_4.4.1-3_i386.deb
lib64gcc1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gcc1-dbg_4.4.1-3_i386.deb
lib64gcc1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gcc1_4.4.1-3_i386.deb
lib64gfortran3-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gfortran3-dbg_4.4.1-3_i386.deb
lib64gfortran3_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gfortran3_4.4.1-3_i386.deb
lib64gomp1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gomp1-dbg_4.4.1-3_i386.deb
lib64gomp1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gomp1_4.4.1-3_i386.deb
lib64mudflap0-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64mudflap0-dbg_4.4.1-3_i386.deb
lib64mudflap0_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64mudflap0_4.4.1-3_i386.deb
lib64objc2-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64objc2-dbg_4.4.1-3_i386.deb
lib64objc2_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64objc2_4.4.1-3_i386.deb
lib64stdc++6-4.4-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64stdc++6-4.4-dbg_4.4.1-3_i386.deb
lib64stdc++6_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64stdc++6_4.4.1-3_i386.deb
libgcc1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgcc1-dbg_4.4.1-3_i386.deb
libgcc1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgcc1_4.4.1-3_i386.deb
libgfortran3-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgfortran3-dbg_4.4.1-3_i386.deb
libgfortran3_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgfortran3_4.4.1-3_i386.deb
libgomp1-dbg_4.4.1-3_i386.d

Bug#537505: marked as done (Couldn't configure pre-depend libc6-i386 for lib32stdc++6)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 16:54:41 +
with message-id 
and subject line Bug#537466: fixed in gcc-4.4 4.4.1-3
has caused the Debian Bug report #537466,
regarding Couldn't configure pre-depend libc6-i386 for lib32stdc++6
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.)


-- 
537466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-i386
Version: 2.9-18, using old 32bit box to report 64 bit bug hanging new box...
Severity: normal


Subject: ..hangs apt* dry w "E: Couldn't configure pre-depend libc6-i386 for 
lib32objc2, probably a dependency cycle"
Package: libc6-i386
Version: 2.9-18
Severity: normal


...aptitude output on trying to upgrade pkgs:
celsius:~# aptitude
E: Couldn't configure pre-depend libc6-i386 for lib32objc2, probably a 
dependency cycle.
A package failed to install.  Trying to recover:
Press return to continue.

E: Couldn't configure pre-depend libc6-i386 for lib32objc2, probably a 
dependency cycle.
A package failed to install.  Trying to recover:
Press return to continue.

...trying to toss out lib32objc2, has libc6-i386 blame some other pkg.


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libc6-i386 depends on:
ii  libc6 2.9-18 GNU C Library: Shared libraries

libc6-i386 recommends no packages.

libc6-i386 suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: gcc-4.4
Source-Version: 4.4.1-3

We believe that the bug you reported is fixed in the latest version of
gcc-4.4, which is due to be installed in the Debian FTP archive:

cpp-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/cpp-4.4_4.4.1-3_i386.deb
fixincludes_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/fixincludes_4.4.1-3_i386.deb
g++-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/g++-4.4-multilib_4.4.1-3_i386.deb
g++-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/g++-4.4_4.4.1-3_i386.deb
gcc-4.4-base_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gcc-4.4-base_4.4.1-3_i386.deb
gcc-4.4-locales_4.4.1-3_all.deb
  to pool/main/g/gcc-4.4/gcc-4.4-locales_4.4.1-3_all.deb
gcc-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gcc-4.4-multilib_4.4.1-3_i386.deb
gcc-4.4-source_4.4.1-3_all.deb
  to pool/main/g/gcc-4.4/gcc-4.4-source_4.4.1-3_all.deb
gcc-4.4_4.4.1-3.diff.gz
  to pool/main/g/gcc-4.4/gcc-4.4_4.4.1-3.diff.gz
gcc-4.4_4.4.1-3.dsc
  to pool/main/g/gcc-4.4/gcc-4.4_4.4.1-3.dsc
gcc-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gcc-4.4_4.4.1-3_i386.deb
gfortran-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gfortran-4.4-multilib_4.4.1-3_i386.deb
gfortran-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gfortran-4.4_4.4.1-3_i386.deb
gobjc++-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc++-4.4-multilib_4.4.1-3_i386.deb
gobjc++-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc++-4.4_4.4.1-3_i386.deb
gobjc-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc-4.4-multilib_4.4.1-3_i386.deb
gobjc-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc-4.4_4.4.1-3_i386.deb
lib64gcc1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gcc1-dbg_4.4.1-3_i386.deb
lib64gcc1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gcc1_4.4.1-3_i386.deb
lib64gfortran3-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gfortran3-dbg_4.4.1-3_i386.deb
lib64gfortran3_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gfortran3_4.4.1-3_i386.deb
lib64gomp1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gomp1-dbg_4.4.1-3_i386.deb
lib64gomp1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gomp1_4.4.1-3_i386.deb
lib64mudflap0-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64mudflap0-dbg_4.4.1-3_i386.deb
lib64mudflap0_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64mudflap0_4.4.1-3_i386.deb
lib64objc2-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64objc2-dbg_4.4.1-3_i386.deb
lib64objc2_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64objc2_4.4.1-3_i386.deb
lib64stdc++6-4.4-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64stdc++6-4.4-dbg_4.4.1-3_i386.deb
lib64stdc++6_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64stdc++6_4.4.1-3_i386.deb
libgcc1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgcc1-dbg_4.4.1-3_i386.deb
libgcc1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgcc1_4.4.1-3_i386.deb
libgfortran3-dbg_4.4.1-3_i386.deb

Bug#519165: marked as done (set -u should not error on "${@:+}" if there are no args)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 16:48:40 +
with message-id 
and subject line Bug#519165: fixed in bash 4.0-4
has caused the Debian Bug report #519165,
regarding set -u should not error on "${@:+}" if there are no args
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.)


-- 
519165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exim4-config
Version: 4.69-9
Severity: important
File: /usr/sbin/update-exim4.conf

starting with bash version 4.0-1:

/var/log/boot:Sun Mar  8 19:13:03 2009: Starting
MTA:/usr/sbin/update-exim4.conf: line 38: $@: unbound variable

because "set -u" now applies to $@ too.


--- End Message ---
--- Begin Message ---
Source: bash
Source-Version: 4.0-4

We believe that the bug you reported is fixed in the latest version of
bash, which is due to be installed in the Debian FTP archive:

bash-builtins_4.0-4_i386.deb
  to pool/main/b/bash/bash-builtins_4.0-4_i386.deb
bash-doc_4.0-4_all.deb
  to pool/main/b/bash/bash-doc_4.0-4_all.deb
bash-minimal_4.0-4_i386.deb
  to pool/main/b/bash/bash-minimal_4.0-4_i386.deb
bash-static_4.0-4_i386.deb
  to pool/main/b/bash/bash-static_4.0-4_i386.deb
bash_4.0-4.diff.gz
  to pool/main/b/bash/bash_4.0-4.diff.gz
bash_4.0-4.dsc
  to pool/main/b/bash/bash_4.0-4.dsc
bash_4.0-4_i386.deb
  to pool/main/b/bash/bash_4.0-4_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 519...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated bash 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, 23 Aug 2009 16:09:36 +0200
Source: bash
Binary: bash bash-minimal bash-static bash-builtins bash-doc bashdb
Architecture: source all i386
Version: 4.0-4
Distribution: unstable
Urgency: low
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description: 
 bash   - The GNU Bourne Again SHell
 bash-builtins - Bash loadable builtins - headers & examples
 bash-doc   - Documentation and examples for the The GNU Bourne Again SHell
 bash-minimal - The GNU Bourne Again SHell (minimal version)
 bash-static - The GNU Bourne Again SHell (static version)
 bashdb - The GNU Bourne Again SHell Debugger
Closes: 506213 519165 522857 523706 540371
Changes: 
 bash (4.0-4) unstable; urgency=low
 .
   * Apply upstream patches 024 - 028.
 - patch 028 closes: #519165. bash-4.0 reverted to the historical
   shell behavior of raising an error when $@ or $* was expanded
   after `set -u' had been executed and there were no positional
   parameters.  The Posix working group has since clarified the
   standard's position on the issue, and $@ and $* are now the only
   variables, parameters, or special parameters that do not raise an
   error when unset if set -u is enabled.
   * Enable net redirections, now that bash isn't the default shell
 anymore.
   * Changes to the skeletoon .bashrc:
 - Fix example lines in /etc/bash.bashrc to enable bash completion.
   Closes: #523706, #522857.
 - Don't export HISTCONTROL in bashrc. Closes: #540371.
 - Support user dircolors settings in ~/.dircolors. Closes: #506213.
Checksums-Sha1: 
 d7472d32b143071146b69d32e8850dbfc44fbf6a 1119 bash_4.0-4.dsc
 57de0fc74b235053fabf6ba40ab13bbc80b3f93b 98018 bash_4.0-4.diff.gz
 8714b8dda4fdb88352294ac41565e1a8d95cee4c 312096 bash-doc_4.0-4_all.deb
 e778a9a13b47fe6b13be4b3eec68c59e052dd1ff 1096928 bash_4.0-4_i386.deb
 4799d7d000f85cb9f9f6044b181a932d97c6bae9 107052 bash-builtins_4.0-4_i386.deb
 32e8a0ca4c3ea739d1b3cf64107436c4d6399d45 760136 bash-static_4.0-4_i386.deb
 d7818113edaf94882e6daa73ea665236f6afea95 223150 bash-minimal_4.0-4_i386.deb
Checksums-Sha256: 
 b12ada41b85928f81a6467849dba33bf9a5963d570ae4141562d87d4aa639911 1119 
bash_4.0-4.dsc
 8fa86d5e8f26f196eb1eabf62c8de599ae3fbfa5fac6959e2b9b503e3ce570ab 98018 
bash_4.0-4.diff.gz
 d207cec972085d4338b9116dec8209ecef0daa8ae14a486d3824fd4d9e9d447c 312096 
bash-doc_4.0-4_all.deb
 59016011ca0b8e3fdb6d2f5b20ddb13d9a3493d138ed5242c9cd124c56cadc66 1096928 
bash_4.0-4_i386.deb
 8d7dd9a8d0466b255a1bcd8abcedd3e90c50e4520366c0110d9ff972dff8d683 107052 
bash-builtins_4.0-4_i386.deb
 43

Bug#543158: marked as done ([libc6-i386] Can't upgrade Sid)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 16:54:41 +
with message-id 
and subject line Bug#537466: fixed in gcc-4.4 4.4.1-3
has caused the Debian Bug report #537466,
regarding [libc6-i386] Can't upgrade Sid
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.)


-- 
537466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-i386
Version: 2.9-18
Severity: normal

--- Please enter the report below this line. ---

Error message of "aptitude safe-upgrade":

E: Couldn't configure pre-depend libc6-i386 for lib32stdc++6, probably
a dependency cycle.

--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.30-1-amd64

Debian Release: squeeze/sid
  500 unstablewww.debian-multimedia.org 
  500 unstablehttp.us.debian.org 

--- Package information. ---
Depends  (Version) | Installed
==-+-===
libc6   (= 2.9-18) | 2.9-18


Package's Recommends field is empty.

Package's Suggests field is empty.






-- 
ASD Consultoria, Rio, RJ
Arq. Sávio M Ramos
Só usamos Linux desde 2000
www.debian.org


--- End Message ---
--- Begin Message ---
Source: gcc-4.4
Source-Version: 4.4.1-3

We believe that the bug you reported is fixed in the latest version of
gcc-4.4, which is due to be installed in the Debian FTP archive:

cpp-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/cpp-4.4_4.4.1-3_i386.deb
fixincludes_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/fixincludes_4.4.1-3_i386.deb
g++-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/g++-4.4-multilib_4.4.1-3_i386.deb
g++-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/g++-4.4_4.4.1-3_i386.deb
gcc-4.4-base_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gcc-4.4-base_4.4.1-3_i386.deb
gcc-4.4-locales_4.4.1-3_all.deb
  to pool/main/g/gcc-4.4/gcc-4.4-locales_4.4.1-3_all.deb
gcc-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gcc-4.4-multilib_4.4.1-3_i386.deb
gcc-4.4-source_4.4.1-3_all.deb
  to pool/main/g/gcc-4.4/gcc-4.4-source_4.4.1-3_all.deb
gcc-4.4_4.4.1-3.diff.gz
  to pool/main/g/gcc-4.4/gcc-4.4_4.4.1-3.diff.gz
gcc-4.4_4.4.1-3.dsc
  to pool/main/g/gcc-4.4/gcc-4.4_4.4.1-3.dsc
gcc-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gcc-4.4_4.4.1-3_i386.deb
gfortran-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gfortran-4.4-multilib_4.4.1-3_i386.deb
gfortran-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gfortran-4.4_4.4.1-3_i386.deb
gobjc++-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc++-4.4-multilib_4.4.1-3_i386.deb
gobjc++-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc++-4.4_4.4.1-3_i386.deb
gobjc-4.4-multilib_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc-4.4-multilib_4.4.1-3_i386.deb
gobjc-4.4_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/gobjc-4.4_4.4.1-3_i386.deb
lib64gcc1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gcc1-dbg_4.4.1-3_i386.deb
lib64gcc1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gcc1_4.4.1-3_i386.deb
lib64gfortran3-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gfortran3-dbg_4.4.1-3_i386.deb
lib64gfortran3_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gfortran3_4.4.1-3_i386.deb
lib64gomp1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gomp1-dbg_4.4.1-3_i386.deb
lib64gomp1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64gomp1_4.4.1-3_i386.deb
lib64mudflap0-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64mudflap0-dbg_4.4.1-3_i386.deb
lib64mudflap0_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64mudflap0_4.4.1-3_i386.deb
lib64objc2-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64objc2-dbg_4.4.1-3_i386.deb
lib64objc2_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64objc2_4.4.1-3_i386.deb
lib64stdc++6-4.4-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64stdc++6-4.4-dbg_4.4.1-3_i386.deb
lib64stdc++6_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/lib64stdc++6_4.4.1-3_i386.deb
libgcc1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgcc1-dbg_4.4.1-3_i386.deb
libgcc1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgcc1_4.4.1-3_i386.deb
libgfortran3-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgfortran3-dbg_4.4.1-3_i386.deb
libgfortran3_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgfortran3_4.4.1-3_i386.deb
libgomp1-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgomp1-dbg_4.4.1-3_i386.deb
libgomp1_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libgomp1_4.4.1-3_i386.deb
libmudflap0-4.4-dev_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libmudflap0-4.4-dev_4.4.1-3_i386.deb
libmudflap0-dbg_4.4.1-3_i386.deb
  to pool/main/g/gcc-4.4/libmudflap0-dbg_4.4.1-3_i386.deb
libmudflap0_4.4.1-3_i386.deb
  to pool/main/g/g

Bug#541065: marked as done (python2.6-minimal: fails to install)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 18:52:56 +0200
with message-id <20090823165256.gd19...@puntila.winnegan.fake>
and subject line Not really a python bug
has caused the Debian Bug report #541065,
regarding python2.6-minimal: fails to install
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.)


-- 
541065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python2.6-minimal
Severity: grave
Justification: renders package unusable

Hi,

While installing python2.6, which depends on python2.6-minimal, I got these 
error messages

Unpacking python2.6-minimal (from .../python2.6-minimal_2.6.2-2_amd64.deb) ...
new installation of python2.6-minimal; /usr/lib/python2.6/site-packages is a 
directory
which is expected a symlink to /usr/local/lib/python2.6/dist-packages.
please find the package shipping files in /usr/lib/python2.6/site-packages and
file a bug report to ship these in /usr/lib/python2.6/dist-packages instead
aborting installation of python2.6-minimal
dpkg: error processing 
/var/cache/apt/archives/python2.6-minimal_2.6.2-2_amd64.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/python2.6-minimal_2.6.2-2_amd64.deb


And I don't quite understand as this is the first time python2.6 is being 
installed.

Regards,
ST
-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'transitional'), (500, 'gutsy'), (500, 
'experimental'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_HK.UTF-8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python2.6-minimal depends on:
ii  libc6  2.9-23GNU C Library: Shared libraries
ii  zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime

Versions of packages python2.6-minimal recommends:
pn  python2.6  (no description available)

Versions of packages python2.6-minimal suggests:
ii  binfmt-support1.2.12 Support for extra binary formats


--- End Message ---
--- Begin Message ---
Hi,

in a response to a private mail submitter LUK ShunTim admitted he had
an unofficial python package installed in
  /usr/lib/python2.6/site-packages/
and misinterpreted error messages.

I'm closing this bug. Having some 2.6 code I'm reluctant of
backporting to 2.5 I'm waiting to see 2.6 in testing ASAP.

Thanks
  Siggy
-- 
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org+
|54 days until|Open Source in Northern Germany: www.free-it.org|
|www.Ubucon.de|   tech contact:  b...@free-it.de|
+---> ceterum censeo javascriptum esse restrictam <+


signature.asc
Description: Digital signature
--- End Message ---

Bug#543251: abraca: FTBFS on sparc (dist=unstable)

[Benjamin Drung]

Thanks for reporting. Can you check if the attached comment.patch fixes
this build failure? I have no sparc machine to test this.

Cheers,
Benjamin
diff --git a/site_scons/site_tools/binaryblob.py b/site_scons/site_tools/binaryblob.py
index 1d20b70..64e78db 100644
--- a/site_scons/site_tools/binaryblob.py
+++ b/site_scons/site_tools/binaryblob.py
@@ -22,7 +22,7 @@ _assembly_template = """
   .globl %(full_name)s
   .type %(full_name)s, @object
 %(full_name)s:
-  .incbin "%(file)s" # MD5: %(md5)s
+  .incbin "%(file)s" /* MD5: %(md5)s */
   .byte 0
   .size %(full_name)s, .-%(full_name)s
 """


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

Bug#452851: marked as done (pypy - py.path.local.local.LocalPath may remove unrelated data)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 17:32:13 +0100
with message-id <20090823173213.3ed00...@sakaki.chris-lamb.co.uk>
and subject line Package pypy has been removed from Debian
has caused the Debian Bug report #452851,
regarding pypy - py.path.local.local.LocalPath may remove unrelated data
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.)


-- 
452851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pypy
Version: 1.0.0-3
Severity: grave

The make_numbered_dir method in py.path.local.local.LocalPath may remove
unrelated data in its cleanup function. It creates dirs named
/tmp/$prefix$number, which is easily predictable. It will remove all
dirs with the same prefix and a number smaller than a given keep
threshold regardless of the content and the source.

Bastian

-- 
You!  What PLANET is this!
-- McCoy, "The City on the Edge of Forever", stardate 3134.0


--- End Message ---
--- Begin Message ---
Version: 1.0.0-svn55443-1+rm

The pypy package has been removed from Debian so we are closing
the bugs that were still opened against it.

For more information about this package's removal, please read
http://bugs.debian.org/538858. That bug might give the reasons
why this package was removed and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.


Regards,


-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org
   `-


signature.asc
Description: PGP signature
--- End Message ---

Bug#487375: marked as done (pypy: FTBFS: Keeps running.)

[Debian Bug Tracking System]

Your message dated Sun, 23 Aug 2009 17:32:13 +0100
with message-id <20090823173213.3ed00...@sakaki.chris-lamb.co.uk>
and subject line Package pypy has been removed from Debian
has caused the Debian Bug report #487375,
regarding pypy: FTBFS: Keeps running.
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.)


-- 
487375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pypy
Version: 1.0.0-svn55443-1
Severity: serious

Hi,

Your package is failing to build with the following error:
[c]   26 nodes  [ array: 39749  boehm rtti: 748  func: 8864  struct: 212954 
]
[c]   261000 nodes  [ array: 39807  boehm rtti: 751  func: 8880  struct: 213220 
]
make[1]: *** [bin/pypy] Terminated
make: *** [build-arch-stamp] Terminated
Build killed with signal 15 after 150 minutes of inactivity

This means it didn't output anything for 150 minutes, and probably
hanged doing something.


Kurt



--- End Message ---
--- Begin Message ---
Version: 1.0.0-svn55443-1+rm

The pypy package has been removed from Debian so we are closing
the bugs that were still opened against it.

For more information about this package's removal, please read
http://bugs.debian.org/538858. That bug might give the reasons
why this package was removed and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.


Regards,


-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org
   `-


signature.asc
Description: PGP signature
--- End Message ---

Bug#540317: libcompizconfig0: Uninstalable due to libprotobuf3 removal

[Iustin Pop]

On Sat, Aug 22, 2009 at 11:19:07PM +0200, Philipp Kern wrote:
> On Fri, Aug 07, 2009 at 09:29:04AM +0200, Jean-Luc Coulon (f5ibh) wrote:
> > libprotobuf3 has been removed.
> > So libcompizconfig0 (and the whole compiz stack) is uninstalable.
> 
> I've scheduled binNMUs for this package now.  (Seems to be the only
> rdep of libprotobuf3 apart from protobuf itself.)
> 
> Iustin, as you have rdeps now on that library, please notify -release
> on a transition next time.  Thanks.

Sorry, I did notify the maintainers of the rdeps of libprotobufN (a while ago)
but I didn't realise that I need to notify -release. My apologies.

thanks,
iustin



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#543089: Should be ok in 1.2-4

[Florian Grandel]

Hi Lucas,

thanks for you bug report! This bug should be fixed with 1.2-4 which is 
waiting for sponsorship on mentors.debian.net:


- URL: http://mentors.debian.net/debian/pool/main/j/jaranalyzer
- Source repository: deb-src http://mentors.debian.net/debian unstable 
main contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/j/jaranalyzer/jaranalyzer_1.2-4.dsc


I already posted on debian-java but those who sponsored the package 
before didn't response yet.


Maybe you can sponsor this upload? Would be great.

Florian



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#543251: abraca: FTBFS on sparc (dist=unstable)

[Martin Zobel-Helas]

Package: abraca
Version: 0.4-1
Severity: serious

> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 7.0.50~), libgtk2.0-dev, libxmmsclient-glib-dev 
> (>= 0.6DrMattDestruction), pkg-config, scons, valac (>= 0.7.5)

[...]

> gzip -c build/data/abraca.1 > build/data/abraca.1.gz
> gdk_pixbuf_csource_action(["build/data/abraca_images.c", 
> "build/data/abraca_images.h", "build/data/abraca_images.vapi"], 
> ["build/data/abraca-32.png", "build/data/abraca-192.png", 
> "build/data/abraca-playlist-22.png", "build/data/abraca-collection-22.png", 
> "build/data/abraca-rating-rated.png", "build/data/abraca-rating-unrated.png"])
> gcc -o build/data/abraca_images.o -c -Wall -Wno-unused-variable -g 
> -DGETTEXT_PACKAGE=\"abraca\" -D_REENTRANT -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/pixman-1 -I/usr/include/freetype2 
> -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 
> -I/usr/lib/glib-2.0/include -I/usr/include/xmms2 -Ibuild -Ibuild/data 
> -Ibuild/data/ui -Ibuild/src/utils build/data/abraca_images.c
> binary_blob_asmsource_action(["build/data/ui/abraca_ui.s", 
> "build/data/ui/abraca_ui.h", "build/data/ui/abraca_ui.vapi"], 
> ["build/data/ui/about.xml", "build/data/ui/main_menu.xml", 
> "build/data/ui/mediainfo.xml"])
> as -o build/data/ui/abraca_ui.o build/data/ui/abraca_ui.s
> build/data/ui/abraca_ui.s: Assembler messages:
> build/data/ui/abraca_ui.s:6: Error: junk at end of line, first unrecognized 
> character is `#'
> build/data/ui/abraca_ui.s:14: Error: junk at end of line, first unrecognized 
> character is `#'
> build/data/ui/abraca_ui.s:22: Error: junk at end of line, first unrecognized 
> character is `#'
> scons: *** [build/data/ui/abraca_ui.o] Error 1
> scons: building terminated because of errors.
> make[1]: *** [override_dh_auto_build] Error 2
> make[1]: Leaving directory 
> `/build/buildd-abraca_0.4-1-sparc-oHjaAS/abraca-0.4'
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#542889: nvidia-kernel-source: kernel panic on amd64 with 185.18.31 drivers, Quadro card

[Christoph Anton Mitterer]

Hi.


This does not only affect Quadro cards...

btw: Could you please hurry up to upload the fixed version? Or could you
please reupload the older version?


Best wishes,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Processed: severity of 541630 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 541630 serious
Bug #541630 [linux-image-2.6.30-1-686] r128: Missing initialisation tests; 
missing firmware or deliberate attack can lead to crash
Severity set to 'serious' from 'important'

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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): Bug#541681: Bug #541681 nvidia: 800x600 uses too high a refresh rate for LCD monitors

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> package extremetuxracer
Limiting to bugs with field 'package' containing at least one of 
'extremetuxracer'
Limit currently set to 'package':'extremetuxracer'

> retitle 541681 nvidia: 800x600 uses too high a refresh rate for LCD monitors
Bug #541681 [extremetuxracer] extremetuxracer: Black screen - extreme tux racer 
freezes the screen
Changed Bug title to 'nvidia: 800x600 uses too high a refresh rate for LCD 
monitors' from 'extremetuxracer: Black screen - extreme tux racer freezes the 
screen'
> severity 541681 important
Bug #541681 [extremetuxracer] nvidia: 800x600 uses too high a refresh rate for 
LCD monitors
Severity set to 'important' from 'grave'

> reassign 541681 nvidia-glx
Bug #541681 [extremetuxracer] nvidia: 800x600 uses too high a refresh rate for 
LCD monitors
Bug reassigned from package 'extremetuxracer' to 'nvidia-glx'.
Failed to clear fixed versions and reopen on 541681: limit failed for bugs: 
541681.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#543248: nvidia-glx-legacy-71xx: Package is uninstallable (NOT a divert problem!)

[David Baron]

Package: nvidia-glx-legacy-71xx
Severity: grave
Justification: renders package unusable

Installing this baby will happily remove all of xorg.

Hint: Nvidia's version reports:
/usr/lib/xorg/modules/drivers//nvidia_drv.so: undefined symbol:
/ AllocateScreenPrivateIndex


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (650, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-davidb (PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#540497: Not reproduced here

[Patrick Wiseman]

I'd been holding this package because of the bug report, but today
went ahead and installed, and did not encounter the reported problem.

Patrick



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: fixed 543170 in 2.4.3-4lenny3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 543170 2.4.3-4lenny3
Bug #543170 {Done: Nico Golde } [pidgin] pidgin prior to 2.5.9 
HAS SECURITY ISSUE CVE-2009-2694
There is no source info for the package 'pidgin' at version '2.4.3-4lenny3' 
with architecture ''
Unable to make a source version for version '2.4.3-4lenny3'
Bug Marked as fixed in versions 2.4.3-4lenny3.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: fixed 543170 in 2.4.3-4lenny3+b1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 543170 2.4.3-4lenny3+b1
Bug #543170 {Done: Nico Golde } [pidgin] pidgin prior to 2.5.9 
HAS SECURITY ISSUE CVE-2009-2694
There is no source info for the package 'pidgin' at version '2.4.3-4lenny3+b1' 
with architecture ''
Unable to make a source version for version '2.4.3-4lenny3+b1'
Bug Marked as fixed in versions 2.4.3-4lenny3+b1.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: notfixed 543170 in 2.5.8-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfixed 543170 2.5.8-1
Bug #543170 {Done: Nico Golde } [pidgin] pidgin prior to 2.5.9 
HAS SECURITY ISSUE CVE-2009-2694
There is no source info for the package 'pidgin' at version '2.5.8-1' with 
architecture ''
Unable to make a source version for version '2.5.8-1'
Bug No longer marked as fixed in versions 2.5.8-1.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org