Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
archive. The renaming of the library packages can now start. You can
upload the packages even before the toolchain is built for all architectures
because the packages with the new binary packages will be hold in the NEW
queue u
Additional patch at
http://people.ubuntu.com/patches/alsa-lib-biarch-2.diff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: qt4-x11
Version: 4.0.1-4
trying to rebuild after a sucessful build:
rm: cannot remove `tools/designer/src/plugins/tools/view3d/Makefile.Debug': No
such file or directory
rm: cannot remove `tools/designer/src/plugins/tools/view3d/Makefile.Release':
No such file or directory
rm: cannot r
Philipp Kern writes:
> On Nov 17, 2005, at 03:22, Matthias Klose wrote:
> > Compiler versions g++-4.0_4.0.2-4 and g++-3.4_3.4.4-10 are now in the
> > archive. The renaming of the library packages can now start.
>
> Apart of waiting for the dependencies... Do I need to
609-done (append "-done") so the
bug is closed.
Thank you.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Is hiding the password in the input really useful if it's written
to the configuration in clear text?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
reopen 339255
thanks
Debian Bug Tracking System writes:
> quantlib (0.3.11-2) unstable; urgency=low
> .
>* Rebuilt with new g++ for libstdc++ allocator transition (Closes: #339255)
The library package was not renamed. It's no reason, that you _can_
rebuild all other packages. Partial upgrad
Hamish Moffatt writes:
> On Tue, Nov 15, 2005 at 07:57:24AM +0100, Matthias Klose wrote:
> > Package: tqsllib
> > Severity: important
> >
> > Please do not take any action before reading
> > http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html
I'd like to help / betatest too, if I may.
Sources? (I have an autobuilder set up here, so the QA thing doesn't need
handholding... much.)
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smur
Dirk Eddelbuettel writes:
>
> severity 339255 normal
> tags 339255 + wontfix
> retitle 339255 "QuantLib has now been rebuilt with g++-4_4.0.2-4"
> thanks
>
> On 18 November 2005 at 09:15, Matthias Klose wrote:
> | reopen 339255
> | thanks
>
reopen 339255
thanks
Dirk Eddelbuettel writes:
>
> On 18 November 2005 at 13:58, Matthias Klose wrote:
> | Dirk Eddelbuettel writes:
> | >
> | > severity 339255 normal
> | > tags 339255 + wontfix
> | > retitle 339255 "QuantLib has now been rebuilt with g++-
Debian Bug Tracking System writes:
> As far as I can tell there is no actual bug here: the lib64c-dev
> provides exists in unstable and the dependency appears to do what I was
> expecting it to do.
yes, but you are required to depend on a real package as well, not
just only on a virtual package.
a goal to have one 2.x and one 3.x version in etch. if
2.x can be avoided, that's ok.
> > > That are separate things, and I'd like to have those orphaned bugreports
> > > reassigned to ftp.debian.org so I can deal with them.
> >
> > I'll reassign them to ftp.debian.org.
>
> Thank's a lot!
yeah, thanks a lot for your constructive comments!
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 339320 - moreinfo
thanks
Jeroen van Wolffelaar writes:
> tags 339320 moreinfo
> thanks
>
> On Tue, Nov 15, 2005 at 02:55:16PM +0100, Matthias Klose wrote:
> > Please remove readline4, after all packages are converted to use
> > readline5.
>
> Eh, no, they
> tag 339229 wontfix
> tag 339257 wontfix
any reason for these? please add a short rationale to the bug reports,
why this is wontfix.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 339219 + patch
thanks
http://people.ubuntu.com/patches/c2a-libsigc++-2.0.diff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 339159 + patch
thanks
http://people.ubuntu.com/patches/c2a-cppunit.diff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 339144 + patch
thanks
http://people.ubuntu.com/patches/c2a-aiksaurus.diff
please remove the build dependency on libstdc++2.10-dev, it's not
needed for anything.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 339161 + patch
thanks
http://people.ubuntu.com/patches/c2a-enchant.diff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 339241 + patch
thanks
http://people.ubuntu.com/patches/c2a-openexr.diff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 339211 + patch
thanks
http://people.ubuntu.com/patches/c2a-libmusicbrainz-2.0.diff
Note, that this patch drops python2.1 and python2.2 support, and add
python2.4 support as well.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECT
well, too late, but please add conflicts/replaces to "libcal3d10c2" as
well, when you update the package.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 339212 + patch
thanks
patch at http://people.ubuntu.com/patches/c2a-libmusicbrainz-2.1.diff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 339242 + patch
thanks
please find a patch at http://people.ubuntu.com/patches/c2a-openh323.diff
as a side note: the package doesn't correctly clean:
dpkg-source: building openh323 using existing openh323_1.15.6.orig.tar.gz
dpkg-source: building openh323 in openh323_1.15.6-1ubuntu1.diff.gz
d
tags 339250 + patch
thanks
please find a patch at http://people.ubuntu.com/patches/c2a-pcre3.diff
as a side note: the package doesn't clean:
dpkg-source -b pcre3-6.4
dpkg-source: building pcre3 using existing pcre3_6.4.orig.tar.gz
dpkg-source: building pcre3 in pcre3_6.4-1ubuntu1.diff.gz
dpkg-s
tags 339223 + patch
thanks
please find a patch at http://people.ubuntu.com/patches/c2a-libtunepimp.diff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 339158 + patch
thanks
please find a patch at http://people.ubuntu.com/patches/c2a-cppunit.diff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 339223 + patch
tags 335490 + patch
thanks
please find a patch at http://people.ubuntu.com/patches/c2a-pwlib.diff
fixed as well the FTBFS with openssl 0.9.8.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
change.
+Really fixes #339255.
+ * Remove standard tools from build dependencies, tighten build dependency
+on libboost-dev, built for the changed libstdc++ allocator.
+
+ -- Matthias Klose <[EMAIL PROTECTED]> Sat, 19 Nov 2005 13:38:54 +0100
+
quantlib (0.3.11-2) unstable; urgen
patch updated, the alsa-lib-biarch-2.diff is obsolet now.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Adeodato =?utf-8?B?U2ltw7M=?= writes:
> # doko, see explanation below
> tag 339250 - patch
> thanks
>
> * Matthias Klose [Wed, 23 Nov 2005 21:46:39 +0100]:
>
> > tags 339250 + patch
> > thanks
>
> > please find a patch at http://people.ubuntu.com/patches/c
Adeodato =?utf-8?B?U2ltw7M=?= writes:
> * Matthias Klose [Thu, 24 Nov 2005 22:29:15 +0100]:
>
> > right, that approach looks better, although currently you have to
> > rename both the package.
>
> I discussed it with vorlon, and we were going with the "ma
e C++ library yet.
+Closes: #339250.
+ * debian/rules: Remove testsavedregex in clean target.
+
+ -- Matthias Klose <[EMAIL PROTECTED]> Fri, 25 Nov 2005 07:59:14 +0100
+
pcre3 (6.4-1) unstable; urgency=low
* New upstream release (Closes: 333191)
diff -u pcre3-6.4/debian/libpcre3.fil
Package: libginac1.3c2a
Severity: serious
Unpacking libginac1.3c2a (from .../libginac1.3c2a_1.3.3-2_hppa.deb)
...
dpkg: error processing
/var/cache/apt/archives/libginac1.3c2a_1.3.3-2_hppa.deb (--unpack):
trying to overwrite `/usr/lib/libginac-1.3.so.2.1.0', which is also
in package libginac1.3c2
Package: glibc
Version: 2.3.5-8
Severity: serious
makes gcc* FTBFS on sparc, 2.3.5-6 looks ok.
long longval () { return (long) (sizeof (int)); }
unsigned long ulongval () { return (long) (sizeof (int)); }
#include
#include
int
main ()
{
FILE *f = fopen ("conftest.val", "w");
if (! f)
e
ic class Test {
> public static void main (String args[]) {
> System.exit (0);
> } }
with the current state of java on m68k, it seems to be better to
disable it. Any opinions?
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 340864 + pending
thanks
typo, already fixed in SVN
Kurt Roeckx writes:
> Package: gcc-4.1
> Version: 4.1ds0-0exp0
> Severity: important
>
>
> Hi,
>
> Your package is failing to build on amd64 with the following error:
> dh_movefiles: debian/tmp/usr//libssp.a not found (supposed to put it
Package: ppp
Version: 2.4.3-20050321+2
Severity: grave
Justification: renders package unusable
After terminating due to lack of activity, capi fails to reconnect on that line.
at the first connect you get capi/0:
19:53:14 thor pppd[9406]: capiplugin: connected: "" -> "01920783" outgoing
19:53:14 t
-
mfg
Matthias Taube
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
The bug was reported in the ppp BTS (http://www.samba.org/cgi-bin/ppp-bugs)
as #1172:
From: [EMAIL PROTECTED]
Subject: pppd hangup/dialin problem (related to 1143,1110,1167)
--
mfg
Matthias Taube
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
s are set properly,
check gnus-read-active-file, it should be 'some or nil for instance.
I'm not sure if there are other variables that cause Gnus to read the
whole active file without querying groups individually.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
o Gnus v0.4, and the
recommended setting. Not sure how this relates to Debian installations,
I have none ready at the moment. I might install Sarge or Sid into Xen
some day though.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
in the FILES section for the
interesting.groups directory. I have added two more FAQ entries in this
regard, to appear in 1.11.3.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
401 - 500 of 14114 matches
Mail list logo
