Package: mesa-common-dev
Version: 6.4.2-1
Severity: critical
Justification: breaks the whole system
The apt-get dist-upgrade failed on my system. I have tried doing an apt-get -f
install to fix the problem and also
tried removing the conflicting package to no avail. I hope the following
package: wnpp
severity: normal
owner: Santiago Ruano Rincón [EMAIL PROTECTED]
See http://lists.debian.org/debian-devel/2006/09/msg00330.html
Kind regards,
Santiago
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
Package: console-data
Version: 2:1.0-2
Severity: normal
This bug is mostly a reminder for me...and will collect translation updates.
We should reword the debconf templates so that they fit the devref
suggestions (no question for Select, no first person, etc.).
I'll do it in the SVN ASAP.
--
package: wnpp
severity: normal
owner: Santiago Ruano Rincón [EMAIL PROTECTED]
See http://lists.debian.org/debian-devel/2006/09/msg00330.html
Regards,
Santiago
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
reassign 251423 kbd-chooser
forcemerge 248882 251423
thanks
This very old bug should be assigned to kbd-chooser.
It is indeed requesting somethign similar to #248882 where one
solution could be the Ubuntu way to choose keymaps.
--
Hi, I found that the code
!-- body
in a web page opened but did not close a comment.
Therefore the rest of the page was treated as a comment and did not
display )-:.
Is -- supposed to be sufficient for a close of comment or does the
specification require -- (a space before the
package: wnpp
severity: normal
owner: Santiago Ruano Rincón [EMAIL PROTECTED]
See http://lists.debian.org/debian-devel/2006/09/msg00330.html
Regards,
Santiago
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
reassign 388172 mdadm
forcemerge 386315 388172
stop
On Mon, Sep 18, 2006 at 07:42:09PM -0400, Colin Wetherbee wrote:
Package: initramfs-tools
Version: 0.79
The mkinitramfs script invokes the mdadm hook in
/usr/share/initramfs-tools/hooks/. The hook, in turn, invokes the mdadm
script
Package: kmail
Version: 4:3.5.4-1
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The current Debian package of KMail has the patch that shows a confirmation box
to help debug dimap accounts. I just discovered a small bug that goes like
this:
1. Drag a message from the message
In d-i, kbd-chooser's prebaseconfig chroots to /target and runs
install-keymap with the user's selected keymap. On 2.4, this works and
we get a etc/console/boottime.kmap.gz in target. On 2.6, this has
recently stopped working, and we get many repeats of this to stderr
(caught into the d-i log):
YD == Yavor Doganov [EMAIL PROTECTED] writes:
YD When I receive a message (nevermind in muc or not), I got always
YD the following in the echo area, every time:
YD error in process filter: Symbol's function definition is void:
YD ja
Hm, there's no `ja' in emacs-jabber sources.
Le lundi 18 septembre 2006 23:29, Peter Eisentraut a écrit :
Michel Grentzinger wrote:
Sorry, but I've never installed egroupware-calendar...
This is a fresh install !
Well, I did a fresh install, as I have done many times, and I don't see
this happening. So you'd need to give me a
Jameson Rollins jrollins at gmail.com writes:
security.ask_for_password 2
security.password_lifetime 5
signon.expireMasterPassword true
The XUL/JS code associated with the master password configuration is in
chrome://pippki/content/pref-masterpass.xul
And these values are just
Package: cfengine2
Version: 2.1.20-1
Severity: normal
The code for the package action does only look at a package's version
when comparing an installed version against what the user supplies,
but totally ignores the version when actually running apt-get.
this becomes a problem whenever apt-get's
Package: wnpp
Severity: wishlist
Owner: Rémi Denis-Courmont [EMAIL PROTECTED]
* Package name: pax-utils
Version : 0.1.13
Upstream Author : Ned Ludd and Mike Frysinger
* URL : http://www.gentoo.org/~solar/pax/
* License : GPL
Description : ELF checking
reassign 388195 console-common
tags 388195 pending
thanks
Quoting Christian Perrier ([EMAIL PROTECTED]):
Package: console-data
Version: 2:1.0-2
Severity: normal
This bug is mostly a reminder for me...and will collect translation updates.
We should reword the debconf templates so that
reassign 388065 general
thanks
reassign 388065 cupsys
Bug#388065: My PC should warn me when I try to shut down while my printer is
still printing
Warning: Unknown package 'unknown'
Bug reassigned from package `unknown' to `cupsys'.
Such Windows-like feature would be nice, but there isn't
reassign 388065 general
thanks
reassign 388065 cupsys
Bug#388065: My PC should warn me when I try to shut down while my printer is
still printing
Warning: Unknown package 'unknown'
Bug reassigned from package `unknown' to `cupsys'.
Such Windows-like feature would be nice, but there isn't
On Mon, 18 Sep 2006, Jon Dowland wrote:
However, one thing that I used to do manually for acpid was
manage dock/undock events sent by my thinkpad x40 when I use
my ultrabase. These events used to be generated by the
ibm_acpi module.
I understand that having ibm_acpi manage the hotplugging
I actually see no real point in keeping this opened as Alastair
answered very clearly that this is not a bug.
Therefore, I propose closing this bug report.
--
Package: muttprint
Version: 0.72d-5
Severity: normal
The dependency on latex-ucs would force me to remove texlive from my
system. AFAIK ucs is included in texlive-latex-recommended so changing
the dependency to latex-ucs | texlive-latex-recommended would solve
it.
-- System Information:
Debian
Package: p0f
Version: 2.0.5-1
Severity: normal
Version 2.0.8 is now out (updating the report on 2.0.7). The newer
versions add a -0 option for wildcard queries to the cache. I'm in
the process of updating amavisd-new and postfix to use p0f and we need
that functionality.
It looks like there's
Package: fbi
Version: 2.05-2
Followup-For: Bug #361393
Hi,
firstly, thanks a lot for maintaining fbi.
I really appreciate that.
Secondly, I'm afaid you didn't fix the part of this bug that prompted me
to file it in the first place: fbgs still doesn't recognize -noverbose.
It DOES pass on -q,
tags 339362 moreinfo unreproducible
thanks
hi,
doing some BTS house cleaning, and i can't reproduce this problem in the
latest version of php5... so optomistically i'm hoping that the problem
is resolved. i'll tag the bug with moreinfo/unreproducible for now, and
close it in a week or two's
reopen 276067
thanks
From console-data settings, an Icelandic keyboard should now be chosen
when language is English and country is Iceland.
Untrue..:-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: live-package
Version: 0.99.6-1
Tags: patch
The make-live script cannot handle spaces in arguments. For example, if one
tries
make-live --packages vim emacs
only vim is installed, not emacs. It's even worse when there are options
inside the argument:
make-live --hook dpkg --install
tags 388156 pending
thanks
Bill Allombert [EMAIL PROTECTED] wrote:
Package: tex-common
Version: 0.28
Severity: serious
Hello Debian TeX maintainers,
There is an error when attempting to purge the package:
Removing tex-common ...
Purging configuration files for tex-common ...
Automatic build of john_1.6-40 on coconut0 by sbuild/ia64 0.49
...
gcc -c -Wall -O2 -fomit-frame-pointer -funroll-loops compiler.c
compiler.c: In function 'c_free_ident':
compiler.c:305: warning: dereferencing type-punned pointer will break
strict-aliasing rules
compiler.c:306: warning:
severity 388067 serious
stop
Max Kellermann [EMAIL PROTECTED] wrote:
On 2006/09/18 16:32, Frank K?ster [EMAIL PROTECTED] wrote:
Do you still have a full build log available?
I've attached a fresh build log (i386).
Thank you. It shows that dpkg-buildpackage first calls the build target
Package: mailman
Version: 1:2.1.8-3
Severity: wishlist
Tags: l10n, patch
The updated Vietnamese translation for the debconf file: mailman
translated and submitted by:
Clytie Siddall (vi-VN, Vietnamese free-software translation team /
nhóm Việt hóa phần mềm tự do)
vi.po.gz
Description: GNU
forcemerge 384057 388193
thanks
On Tue, Sep 19, 2006 at 03:48:09PM +1000, Matthew Byrne wrote:
The apt-get dist-upgrade failed on my system. I have tried doing an apt-get
-f install to fix the problem and also
tried removing the conflicting package to no avail. I hope the following
Package: amavisd-new
Version: 1:2.4.2-1
Severity: wishlist
Please forward upstream as you see appropriate.
p0f has the ability to run as a daemon and support queries via a unix
named pipe interface into the cache. Before p0f 2.0.7, this interface
wasn't useful to amavis because queries required
I'm attaching gl.po
--
Jacobo Tarrío | http://jacobo.tarrio.org/
# Galician translation of console-common
# Jacobo TarrÃo [EMAIL PROTECTED], 2005
#
#Translators, if you are not familiar with the PO format, gettext
#documentation is worth reading, especially sections
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: mailman
Severity: wishlist
Version: 1:2.1.8-2
Tags: l10n patch
Hi,
I updated Japanese debconf translation.
Please apply this.
Thanks,
- --
Kenshi Muto
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
found 376177 4.3.99.1-1
thanks
that's quite boring, especially since smart bjt has the bug closed in
upstream [1]. will the stable version be released like that? :'(
cheers,
rob
[1] http://bugzilla.xfce.org/show_bug.cgi?id=1910
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Le mardi 19 septembre 2006 à 01:35 +0200, Frans Pop a écrit :
On Tuesday 19 September 2006 01:07, you wrote:
On Mon, 2006-09-18 at 23:56 +0200, Frans Pop wrote:
Please include fc-list again in fontconfig-udeb.
I didn't intentionally remove it; was it present in some package?
Sorry, I
tags 386293 moreinfo unreproducible
thanks
I wrote two weeks ago:
Unpacking passwd (from .../passwd_1%3a4.0.18.1-2_i386.deb) ...
Setting up passwd (4.0.18.1-2) ...
no matching group file entry in /etc/gshadow
add group 'plugdev' in /etc/gshadow ?grpck: no changes
Please correct
On Mon, Sep 18, 2006 at 10:19:35PM +0200, Helge Kreutzmann wrote:
Hello Denis,
I'll try that on Saturday, but I assume that this X crash is a
PowerPC/Radeon specific bug, so I don't know if you'll be able to
reproduce.
Ok, then you may put xkb-data on hold, because these patches have
been
Package: tomboy
Version: 0.3.9+dfsg-2
Severity: normal
Tags: patch
Hi,
Attached is the diff for my tomboy 0.3.9+dfsg-2.1 NMU.
bye,
- michael
diff -u tomboy-0.3.9+dfsg/debian/changelog tomboy-0.3.9+dfsg/debian/changelog
--- tomboy-0.3.9+dfsg/debian/changelog
+++
Package: amavisd-new
Version: 1:2.4.2-1
Severity: normal
The p0f fingerprinting code in amavis currently writes its headers when
passing information down to SpamAssassin, but doesn't write the headers
into the actual message stream, so we don't record OS types for posterity
later (or for the
[EMAIL PROTECTED] skrev:
You are noted as the last translator of the Debian configuration translation
for
the console-common package.
Hi,
Here is the updated Swedish translation.
Regards,
Daniel
#
#Translators, if you are not familiar with the PO format, gettext
#documentation is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I stumbled also over the warning today. I use a private distribution
name for packages I don't want to upload anywhere but my own box.
So +1 from me for making the warning overridable.
Regards,
Bastian
- --
,''`. Bastian
Le samedi 16 Septembre 2006 16:36, Noèl Köthe a écrit :
tag 337202 + confirmed upstream
forwarded 337202 https://bugs.kde.org/show_bug.cgi?id=125682
thanks
Am Donnerstag, den 03.11.2005, 09:56 +0100 schrieb Thomas Nemeth:
Salut Thomas,
Salut !
Whe I try to configure date and time,
Package: orca
Version: 0.2.3
Severity: grave
Justification: renders package unusable
On non-i386 architectures, the orca package doesn't actually contain the
orca binary, as seen at eg. [1]. This is because the tarball contains
i386 objects that don't get rebuilt, resulting in a link error. From
Hi,
agreed that since the mtools/syslinux.c is used and not the
unix/syslinu.c, the relation to mtools should be a depends rather than a
recommends.
But as long as the package is not splitted into syslinux and
syslinux-data (or similar), I'll wait with changing this relation to not
have a
Hi,
I can not give you the partition table or map, because I reinstalled everything
again.
I now have installed MacOSX on a clean disk, the first 200 GB free HFS
partition, then 40 GB for MacOSX HFS+ case-sensitive
with journaling feature. After the MacOS X installation went fine, I installed
Please find attached the updated catalan translation of console-common
package.
Regards,
--
**
Orestes Mas Casals
Universitat Politècnica de Catalunya
Linux User 285092 http://counter.li.org
Clau pública PGP: 0x97451E6A a http://pgp.mit.edu/
Package: amavisd-new
Version: 1:2.4.2-1
Followup-For: Bug #364327
Rather than fix p0f-analyzer to do inline configuration, let's just
get rid of it and query p0f's cache directly. p0f 2.0.7 and later
do a fine and dandy job and the code in amavis can be greatly simplified.
cf. debian problem
warning: Can't read pathname for load map: Input/output error.
warning: .dynamic section for /usr/lib/libasound.so.2 is not at the
expected address
warning: difference appears to be caused by prelink, adjusting
expectations
Two things here:
On Tue, Sep 19, 2006 at 09:16:23AM +0200, Christian Perrier wrote:
Please respect the Reply-To: field and send your updated translation to
[EMAIL PROTECTED] This Debian bug report will collect ALL translation
updates. Please DO NOT send translation updates as separate bug reports,
this time.
Hi Christian
Here goes the updated translation, I hope it is as you requested.
Feel free to use it.
Regards,
Nuno Sénica
[EMAIL PROTECTED] wrote:
(PLEASE READ this mail carefully. The usual procedure is slightly changed
for that update)
Hi,
You are noted as the last translator of the
On Tue, 2006-09-19 at 02:33, Debian Bug Tracking System wrote:
From: Daniel Baumann [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: /usr/share/doc/syslinux/*.doc is empty.
Date: Tue, 19 Sep 2006 03:24:47 +0200
This was fixed already when I first uploaded a new syslinux package.
Package: wnpp
Michael Welle and I would like to take over rxvt from David
Moreno Garza, who recently offered the package for adoption
(http://lists.debian.org/debian-devel/2006/09/msg00330.html).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
Package: bugs.debian.org
Severity: wishlist
Tag: moreinfo
* Submitter: Gerfried Fuchs [EMAIL PROTECTED]
On Tue, 19 Sep 2006, Gerfried Fuchs wrote:
At the the i18n Extremadura Meeting[1] we discussed how to be able
to handle i18n and l10n bugs more conveniently and having a way to
be able to
severity 387417 important
thanks
Hi
Thanks, I'll add that dependency.
Regards,
// Ola
On Thu, Sep 14, 2006 at 12:13:35PM +0200, [EMAIL PROTECTED] wrote:
Package: vzctl
Version: 3.0.10-2
Package vzctl should depend on net/iproute.
Thx
Sebastian
--
- Ola
Hi,
FWIW, I managed to compile an SMP kernel (using gcc-4.0 since gcc-4.1 won't
compile it).
I decided to compile scsi disk (and driver etc) support in statically
and found out that some symbols called 'exit' are not found when linking
vmlinux together.
Based on some googling I commented out
reassign 388165 fontconfig-udeb
thanks
On Tuesday 19 September 2006 04:06, you wrote:
The new config shouldn't actually work any differently; all of the
pieces which were removed from the fonts.conf file have been put into
separate files in /etc/fonts/conf.d so the sans-serif alias should
On Tue, 19 Sep 2006, Drew Parsons wrote:
On Mon, 2006-09-18 at 16:49 +0200, Frans Pop wrote:
On Monday 18 September 2006 14:48, Drew Parsons wrote:
Could you tell me what the m68k flag is defined as, in the #if
defined( ) sense as in
Surprise, surprise. It is (taken from kbd-chooser
On 2006/09/19 09:07, Frank K?ster [EMAIL PROTECTED] wrote:
Strangely, I cannot reproduce this here (it happened exactly
once...). Maybe there's again some timeskew problem, but I doubt
it, since all these commands should take a while. Are you able to
reproduce this? If yes, please apply the
severity 387173 important
thanks
Hi
I'll look at this asap.
Regards,
// Ola
On Tue, Sep 12, 2006 at 02:15:19PM -0400, Adrian Irving-Beer wrote:
Package: xvnc4viewer
Version: 4.1.1+X4.3.0-17
Severity: normal
This is similar to bug #386404, but whereas that bug seems to have
been solved,
Hello,
Please note that the Diagnostics section of the man page
says:
Of course, trying to print an error message would be futile if an
error resulted from an output function, so par doesn't bother doing
any error checking on output functions.
This is because the errors from par are
Package: libraw1394-dev
Version: 1.2.1-1
Severity: normal
Hi,
Please move the libraw1394-doc dependency to recommends or suggests.
This package is definitely not needed when you build a source.
Christian
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT
On Tuesday 19 September 2006 03:49, you wrote:
Ok, it'll be in 2.4.1-3; I'm waiting to see if a few more translations
come along before releasing that though. IF you want it sooner, I'll
push it right away.
Some time in the next week (or even two) will do fine; later would become
problematic
Please find attached the dzongkha (dz) translation update for the
console-common package.
(See attached file: dz.po)
dz.po
Description: Binary data
Package: cacti
Version: 0.8.6h-4
Severity: serious
Justification: Policy 7.2
Subject: cacti: config/postrm depends on non-essential packages
(dbconfig-common, probably ucf)
Package: cacti
Severity: serious
Justification: Policy 7.2
hi there,
it was recently brought to my attention that the
Package: cacti
Version: -I
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Beckermann wrote:
On Saturday 16 September 2006 14:58, Eddy Petrişor wrote:
* The first about 20 lines of console output when starting boson
[EMAIL PROTECTED] ~/usr/src/traduceri/dipo/di/4th/samba $ boson 2/dev/null |
head
-n25 [EMAIL
Hi
Thanks for the report. I'll contact upstream about this, and also
try to determine how it should be myself.
Regards,
// Ola
On Sat, Sep 16, 2006 at 05:22:49PM +0200, [EMAIL PROTECTED] wrote:
Package: vzctl
Version: 3.0.10-3
Severity: grave
(Sorry and thankful in advance this time ;)
I agree.
Regards,
// Ola
On Fri, Sep 08, 2006 at 08:23:33PM +, Daniel Franganillo wrote:
Probably it should be a good idea to add the reasons why harden
conflicts with some services.
--
Tritt - Me and my sussie -
--
- Ola Lundqvist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/19/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
The templates in this package have been rewritten to better fit the
recommended writing style described in Debian Developers Reference.
This marks some of your translations as fuzzy. Please
Hello!
On Tue, Sep 19, 2006 at 07:33:28AM +0200, Wolfgang Lonien wrote:
Thomas Schwinge wrote:
Please try either a) linux-image-2.6-xen-* together with
^ That should have been
linux-image-2.6.16-2-xen-*.
xen-hypervisor-3.0.2-1-* or b)
notfound 0.72d-5
found 0.72d-6
thanks
Am Dienstag, 19. September 2006 08:55 schrieb Magnus Therning:
Package: muttprint
Version: 0.72d-5
Could you please report it against the correct version next time? :)
The dependency on latex-ucs would force me to remove texlive from my
system. AFAIK
Package: bacula-director-mysql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted
Package: acidbase
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject
Package: torrentflux
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: postfix-policyd
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: libdspam7-drv-pgsql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in
Package: serendipity
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Le lundi 18 septembre 2006 à 23:50 -0400, Pascal Giard a écrit :
tags 388174 unreproducible moreinfo
thx!
Hi,
i'm unable to reproduce your problem.
I added my inbox as an evolution folder.
It worked perfect. Do you have to browse (move around abit) to make it
crash? I also tried
Package: bugzilla
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject
Package: gocr
Version: 0.39-5
Severity: important
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=C,
Package: tikiwiki
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject
Package: otrs2
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject of
Package: nagios-mysql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: nagios-text
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: libdspam7-drv-mysql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in
Package: webcalendar
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: phpgacl
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject
On Sun, Sep 17, 2006 at 03:15:50AM -0400, José Parrella wrote:
tags 385883 +patch
thank you
I have succesfully built a Debian package which updates the references
to three functions which changed in tinysnmp's API. While the
compilation still produces warnings, I've been able to run ORCA
Package: simba
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject of
Package: mydms
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject of
Package: wnpp
Severity: wishlist
* Package name: Mozilla Lightning
Version : 0.1
Upstream Author : mozilla
* URL :
http://www.mozilla.org/projects/calendar/lightning/download.html
* License : Mozilla Public License
Description : Calendar extension for
Package: steam
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject of
Package: zabbix-server-mysql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in
Package: bacula-director-pgsql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted
Thomas Schwinge wrote:
Hello!
Hi Thomas,
I tried both the 2.6.16 (-18) as well as the 2.6.17 linux images
which are in Etch currently, and both have that same behaviour. Only the
older 2.6.16 (-17 or -16) kernels did boot the Dom0.
Is that still with xen-hypervisor-3.0-amd64? If yes, then
Package: cacti-cactid
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: nagios-pgsql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: openmpi-bin
Version: 1.1-1
Severity: important
When running /usr/bin/mpicc.openmpi, the program exits with
exit_group(-13). strace reveals that it's trying to open the file
/usr/share/openmpi/mpicc.openmpi-wrapper-data.txt. Using a symbolic
link named mpicc solves the problem (our mpicc
Package: jffnms
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject
1 - 100 of 420 matches
Mail list logo
