This bug has been fixed in an NMU I uploaded a short while ago. The
final diff is as detailed below.
The changes are the same as in Torsten's last patch, but I've
corrected the problems with the discrepancies between debian/control
and debian/control.in by merging the changes (incorrectly) made t
On Mon, May 23, 2005 at 09:52:36PM +0900, Kenshi Muto wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dear,
>
> I NMUed xlockmore 1:5.13-2.1 to fix RC #309760.
> I checked Eugene's patch solved this bug.
>
> Could you accept this for Sarge?
Approved
Gruesse,
--
Frank Lichtenheld
On Mon, May 23, 2005 at 07:31:58PM +0200, Kurt Roeckx wrote:
> On Mon, May 23, 2005 at 02:16:04AM +0200, Frank Lichtenheld wrote:
> It seems libid3tag's shlibs was set to 0.15.0b before the
> conversion to cdbs (so the verison in sarge) while it should have
> been 0.15.1b since the API was extended
also sprach Moshe Yudkowsky <[EMAIL PROTECTED]> [2005.05.23.2155 +0200]:
> But even so, through some interaction, this particular kernel
> update failed to go smoothly -- it left me in a state where
> I could no longer boot up.
yeah, this is bad.
> >Why are you manually calling `mdadm --assemble`
Processing commands for [EMAIL PROTECTED]:
> tag 310077 + fixed
Bug#310077: glui: Wrong package name in control file.
Tags were: pending patch
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, De
Package: lvm-common
Version: 1.5.18
Severity: critical
Justification: breaks the whole system
I ran an upgrade this morning and picked up this package, among others,
including a new kernel image. This generated a new initrd which rendered
my "Root on LVM" system unbootable into the new kernel.
Processing commands for [EMAIL PROTECTED]:
> tags 310077 - fixed
Bug#310077: glui: Wrong package name in control file.
Tags were: fixed pending patch
Tags removed: fixed
> tags 310077 + sarge
Bug#310077: glui: Wrong package name in control file.
Tags were: pending patch
Tags added: sarge
> thank
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.14
> tags 310077 = patch sarge
Bug#310077: glui: Wrong package name in control file.
Tags were: sarge pending patch
Tags set to: patch, sarge
>
End of message, stopping processing here.
Processing commands for [EMAIL PROTECTED]:
> tag 310321 unreproducible
Bug#310321: tetex-base: Package doesn't install because of ConTeX
initialization bug
There were no tags set.
Tags added: unreproducible
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
On Mon, May 23, 2005 at 10:45:53PM +0200, martin f krafft wrote:
> also sprach Frank Lichtenheld <[EMAIL PROTECTED]> [2005.05.23.2233 +0200]:
> > Why don't you generate the html-nochunks documentation anymore?
>
> No particular reason except that Roger's patch did not do so?
> Anyway, nochunks is
also sprach Frank Lichtenheld <[EMAIL PROTECTED]> [2005.05.23.2233 +0200]:
> > adduser-ng 0.1.2-1.1 fixes #310246 and should be in incoming now.
> > Build works in pbuilder. Please accept it.
>
> Why don't you generate the html-nochunks documentation anymore?
No particular reason except that Roge
tag 310321 unreproducible
thanks
I personally can't get this bug to reproduce here... can you give some
information as to what actually failed in pdfetex?
[As I have this version installed on quite a few machines, I'd
strongly lean to downgrading this bug if no one else can reproduce
it.]
Don A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2005-05-23, at 22:45, martin f krafft wrote:
also sprach Frank Lichtenheld <[EMAIL PROTECTED]> [2005.05.23.2233
+0200]:
adduser-ng 0.1.2-1.1 fixes #310246 and should be in incoming now.
Build works in pbuilder. Please accept it.
Why don't
also sprach martin f krafft <[EMAIL PROTECTED]> [2005.05.23.2245 +0200]:
> No particular reason except that Roger's patch did not do so?
> Anyway, nochunks is really just a convenience thing (single page, as
> opposed to multiple page), so does it really matter? I give you that
> maybe nochunks wou
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.14
> severity 274859 critical
Bug#274859: mdadm: Fails to start if auto=yes and /dev/md? is a symlink to
/dev/md/?
Severity set to `critical'.
> merge 274859 310412
Bug#274859: mdadm: Fa
Thanks, Don.
Don Armstrong <[EMAIL PROTECTED]> wrote:
> I personally can't get this bug to reproduce here... can you give some
> information as to what actually failed in pdfetex?
>
> [As I have this version installed on quite a few machines, I'd
> strongly lean to downgrading this bug if no one
On Mon, May 23, 2005 at 11:45:36PM +0300, Mantas Kriau??i??nas wrote:
Hi
> I wanna inform, that newest celestia doesn't build on sparc - look at
> http://buildd.debian.org/fetch.php?&pkg=celestia&ver=1.3.2-1&arch=sparc&stamp=1
Thank you for your report. I know that the package couldn't build on
For what it's worth, I intend to prepare new ICU packages for whatever
the current version of ICU is post-sarge. Last time I looked, this
was version 3.2. I have spoken to both the icu and icu28 maintainers
about this intention, though not for a few months. (I'm actually on
vacation now -- I ma
On Mon, May 23, 2005 at 11:12:57PM +0200, martin f krafft wrote:
> also sprach martin f krafft <[EMAIL PROTECTED]> [2005.05.23.2245 +0200]:
> > No particular reason except that Roger's patch did not do so?
> > Anyway, nochunks is really just a convenience thing (single page, as
> > opposed to multi
are you using devfs, or can you figure out what creates those
/dev/mdXX symlinks?
I need to fix #274859, this is urgent.
Thanks,
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' :proud Debian developer, admin, user, and author
`. `'`
`- Debian - when you have better things to do
On IRC we found out that this is related to mdadm not being able to
deal when the device node referred to by mdadm.conf is a symlink:
/dev/md1 is not a block device
this seems to be a special case for devfs only.
In the case of the bug submitter, /dev/md1 is root, /dev/md2 is
swap, /dev/md3 is
On Mon, 23 May 2005, Dirk Eddelbuettel wrote:
> The (upstream) R Core team is very careful not to "promise" entry
> points to R that it won't be able to support. So I doubt that you
> will get them to export other header files.
If that's the case, that's a slight problem, because rpy uses an
unsup
Package: libid3tag
Version: 0.15.1b-4.1
Severity: serious
Tags: sarge
The package defines a shlibs version of >= 0.15.0b. Between
0.15.0b and 0.15.1b there was a function added:
id3_field_gettextencoding()
This means that the shlibs version should have been changed to
>= 0.15.1b.
Kurt
--
T
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.14
> tags 274859 + pending
Bug#274859: mdadm: Fails to start if auto=yes and /dev/md? is a symlink to
/dev/md/?
Tags were: moreinfo
Bug#310412: mdadm refuses to start up on boot due to co
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.14
> # I'm not sure if this was really specific to sarge. As the package is not
> in sarge anymore at least the tag is wrong, can maybe closed
> tags 306303 - sarge
Bug#306303: Fails to
Your message dated Mon, 23 May 2005 19:02:28 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#310294: fixed in mailutils 1:0.6.1-4
has caused the attached Bug report 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 no
Hi,
I found that the version of libid3tag in sarge has a wrong
shlibs. See #310494. (The version in sid doesn't have one at
all, which is fixed in CVS, also see #310311)
It's been suggested that I ask -release if this is important to
get fixed in sarge or not. So my question is, is this an RC
Processing commands for [EMAIL PROTECTED]:
> tags 308534 - sarge
Bug#308534: wordpress: upstream security fix available
Tags were: sarge security
Tags removed: sarge
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administra
Your message dated Tue, 24 May 2005 01:24:12 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed
has caused the attached Bug report 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
As this bug was specific to sarge and the package isn't in sarge
currently can it be closed?
Gruesse,
--
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message dated Tue, 24 May 2005 01:22:07 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Can be closed
has caused the attached Bug report 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 re
On Mon, May 23, 2005 at 11:57:33PM +0200, martin f krafft wrote:
> are you using devfs, or can you figure out what creates those
> /dev/mdXX symlinks?
Wow, thats an old one. I don't recall what the circumstances were. For
some reason I think it was udev that was causing that problem. I half
rem
also sprach Andrew Phillips <[EMAIL PROTECTED]> [2005.05.24.0136 +0200]:
> This was several versions ago. Guessing from what I said, I think a good
> test to see if it still exists is to boot off the hd, with /dev/md* a link
> into /dev/md/, and seeing if auto=yes still works. I won't have time t
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.14
> tags 310412 + help
Bug#310412: mdadm refuses to start up on boot due to config file version problem
Tags were: pending moreinfo
Bug#274859: mdadm: Fails to start if auto=yes and /dev/
Please try again and try the following:
* Make sure you're using aptitude not apt-get
* Try using 'aptitude install pcmcia-cs' to manually install PCMCIA.
* Attach the output of your package lists *both* before and after
* Does it happen on full CD images?
* And please use the templates that Dafy
Greg,
On 23 May 2005 at 12:47, Warnes, Gregory R wrote:
| Hi All,
|
| Unfortunately, the R developers haven't (yet) made the API for interfacing
| with R fully public, so it is necessary to use 'internal' header files.
| Since these header files are (fortunately) constant for a given release of
The behavior of the oops I've experienced has changed with each different
kernel. I started with 2.6.8, then moved to 2.6.10 and now 2.6.11. I believe
they are related, but have no definitive data to demonstrate this.
2.6.8 & 2.6.10 were similar in the there would be the following displayed to
the
Am Montag, 23. Mai 2005 um 13:59:51 Uhr (-0700) schrieb Don Armstrong:
> tag 310321 unreproducible
> thanks
>
> I personally can't get this bug to reproduce here... can you give some
> information as to what actually failed in pdfetex?
I found out, via the log files, that it's a "TeX capacity exc
Your message dated Mon, 23 May 2005 19:24:37 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#310198: rpy: FTBFS: Does not have headers for R 2.1.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing commands for [EMAIL PROTECTED]:
> tags 274859 +patch
Bug#274859: mdadm: Fails to start if auto=yes and /dev/md? is a symlink to
/dev/md/?
Tags were: help pending moreinfo
Bug#310412: mdadm refuses to start up on boot due to config file version problem
Tags added: patch
> thanks
Stoppi
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.14
> tags 301316 - sarge
Bug#301316: conflict with icu28's icu-doc
Tags were: fixed sarge patch
Bug#310127: icu-doc is built by the icu and the icu28 source package
Tags removed: sarge
>
tags 274859 +patch
thanks
[martin f krafft]
> I checked out the source and opening is not hard... but mdadm also
> creates device nodes and uses S_ISBLK all over the place, so I don't
> really know whether adding a "|| S_ISLNK" will fix it.
I didn't actually test this, but I honestly don't see w
On Monday May 23, [EMAIL PROTECTED] wrote:
>
> tags 274859 +patch
> thanks
>
> [martin f krafft]
> > I checked out the source and opening is not hard... but mdadm also
> > creates device nodes and uses S_ISBLK all over the place, so I don't
> > really know whether adding a "|| S_ISLNK" will fix i
On Mon, May 23, 2005 at 07:49:26PM +0200, Martin Bickel wrote:
> On Mon, 23 May 2005 18:07:25 +0200, Bartosz Fenski aka fEnIo wrote:
> >Do you have any clue what could cause this crash on alpha architecture?
> Sorry, I don't know what's going wrong. But to be honest, I would have
> been surprised
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.14
> tags 310479 sid
Bug#310479: Severe breakage of root-on-lvm2 with lvm-common 1.5.18
There were no tags set.
Tags added: sid
>
End of message, stopping processing here.
Please contact
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.14
> tags 310479 sid
Bug#310479: Severe breakage of root-on-lvm2 with lvm-common 1.5.18
Tags were: sid
Tags added: sid
>
End of message, stopping processing here.
Please contact me if yo
On Mon, May 23, 2005 at 09:25:12PM +0100, Roger Leigh wrote:
> This bug has been fixed in an NMU I uploaded a short while ago. The
> final diff is as detailed below.
> The changes are the same as in Torsten's last patch, but I've
> corrected the problems with the discrepancies between debian/cont
Processing commands for [EMAIL PROTECTED]:
> tag 310191 + fixed
Bug#310191: ultrapoint: FTBFS: dpkg-deb: conffile
`/etc/vflib3/vflibcap-ultrapoint' does not appear in package
Tags were: sid
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug
Processing commands for [EMAIL PROTECTED]:
> tag 268924 + fixed
Bug#268924: lxdoom-x11: won't start, complains of being 'Unable to find
supported visual settings'
Tags were: patch
Tags added: fixed
> tag 279190 + fixed
Bug#279190: lxdoom: FTBFS on amd64: not including errno.h
Tags were: patch
Ta
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.14
> close 309746
Bug#309746: libpam-cracklib: passwd program segfaults when pam_cracklib.so used
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send
Your message dated Mon, 23 May 2005 19:59:27 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Elinks contains nonfree code
has caused the attached Bug report 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 respo
Package: gnugk
Version: 2.2.2-2
Severity: serious
Tags: sid
Justification: Policy 3.3
gnugk failed to build on the sparc buildd. It did build fine on my
sparc pbuilder, so it could be a due to problem in one of the
dependancies or sbuild/pbuilder differences or a broken sbuild
environment on vore
Processing commands for [EMAIL PROTECTED]:
> tags 310494 -sarge
Bug#310494: libid3tag: Incorrect shlibs.
Tags were: sarge
Tags removed: sarge
> severity 310494 important
Bug#310494: libid3tag: Incorrect shlibs.
Severity set to `important'.
> thanks
Stopping processing here.
Please contact me if
tags 310494 -sarge
severity 310494 important
thanks
Since 0.15.1b is the only upstream version of libid3tag in the archive, the
lack of versioned shlibs, or insufficiently strict shlibs, is not an RC bug
here.
Thanks,
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital s
You reported an FTBS of evolution2.2 version 2.1.6-1.
This package no longer exists and have been renamed evolution
which is at version 2.2.2-4.
Should i close the report or wait for the source to be removed
from the buildd ?
Regards
Alban
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
On Tue, 24 May 2005, Florian Cramer wrote:
> loading: Context Page Macros / Texts
> ! TeX capacity exceeded, sorry [pool size=225578].
> \c!linkertekst ->\c!internal! l
>inkertekst
> \setvalue #1->\expandafter \def \csname #1
>
Your message dated Mon, 23 May 2005 23:44:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line closing bug
has caused the attached Bug report 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 reop
Your message dated Mon, 23 May 2005 23:44:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line closing bug
has caused the attached Bug report 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 reop
Package: kernel-image-2.6.11-1-k7
Version: 2.6.11-3
Severity: critical
Justification: breaks the whole system
kernel-image-2.6.11-1-k7-2.6.11-5 fails to boot. I receive continuous
messages as follows:
initrd-tools: 0.1.80
/sbin/init: 360 cannot open bin/root: No such file
umount: bin: not mounte
On Mon, 23 May 2005, Craig Condit wrote:
Package: kernel-image-2.6.11-1-k7
Version: 2.6.11-3
Severity: critical
Justification: breaks the whole system
kernel-image-2.6.11-1-k7-2.6.11-5 fails to boot. I receive continuous
messages as follows:
initrd-tools: 0.1.80
/sbin/init: 360 cannot open bin
Your message dated Mon, 23 May 2005 21:47:30 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#310522: kernel-image-2.6.11-1-k7: fails to boot
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the ca
Title: Der neue Kontaktanzeigen-Markt ROTER-SUEDEN
Sehr geehrte Damen und Herren,wir dürfen Ihnen hiermit unseren neuen Kontaktanzeigenmarkt ROTER-SUEDEN vorstellen,seit 3 Tagen am Start. Einzugsgebiet: Deutschland, Österreich, Schweiz und Südtirolhttp://www.roter-sueden.de völlig real und f
Your message dated Tue, 24 May 2005 01:32:35 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#304035: fixed in llvm 1.4-3
has caused the attached Bug report 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 re
Your message dated Tue, 24 May 2005 01:32:35 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#308694: fixed in llvm 1.4-3
has caused the attached Bug report 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 re
Package: cupsys
Version: 1.1.23-10
Severity: grave
Justification: renders package unusable
When installing cupsys I got the following error message:
/var/lib/dpkg/info/cupsys.postinst: line 30: .: /etc/default/cupsys: is a
directory
dpkg: error processing cupsys (--configure):
subprocess post-i
101 - 165 of 165 matches
Mail list logo
