Hello Theodore,
Il giorno mar, 13/08/2024 alle 13.23 -0400, Theodore Ts'o ha scritto:
> Can you show the output of the following commands?
[...]
Here they are:
first, as you asked, for 6.9.10 working kernel:
root@supergulp:~# lsinitramfs -l /boot/initrd.img-6.9.10-amd64 | grep libext2fs
lrwxrw
Hello Santiago,
Il giorno mar, 13/08/2024 alle 12.34 +0200, Santiago Vila ha scritto:
[...]
> Hello. This looks like a problem with fsck.ext4 to me.
>
> Does the problem go away if you regenerate the initrd of the kernel
> which does not boot properly doing this?
>
> dpkg-reconfigure linux-image
Package: src:linux
Version: 6.10.3-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
this is a debian testing machine. After today upgrade and reboot, the machine
does not start anymore.
In fact it stop with message:
The /usr filesystem on /dev/mapper/ssd-usr requires a
Hello Bastien,
thank you very much for your NMU.
Bye,
Giuseppe
Hello Lucas,
thank you for reporting this problem. I already fixed it in the new package I
am working on since a week. I should upload a fixed version in a few days.
Bye,
Giuseppe
Hello Thorsten,
thank you very much for your testing. Indeed the bug required more
fixing than what I did.
I did follow your steps for reproducing it, and now I have a new
package that fix it. If you want to try it, please fetch it here:
https://eppesuigoccas.homedns.org/~giuseppe/debian/libpaper1
Hello Thorsten, Voip, and Jacob,
I think the problem has been solved in version 1.1.27, currently in
unstable. I would really appreciate if you could test it, as well as I
did.
If this package passes your tests, I will ask for an unblock that will
let the package migrate to testing/buster in a few
Hello Thorsten,
it seems the problem raises while building the package; it is not
related to the new installer (as I was initially thinking).
In fact, while building the package, make displays a notice about a
circular dependency of debian/libpaper1.config and build-arch. Indeed,
make is right.
I
Il giorno dom, 23/12/2012 alle 17.27 +0100, Ivo De Decker ha scritto:
> Hi Joachim,
> On Sat, Dec 22, 2012 at 10:44:31PM +0100, Joachim Wiedorn wrote:
> > Ivo De Decker wrote on 2012-12-22 22:05:
> > > This is caused by this line in hylafax-server.postinst:
> > > chown uucp:uucp /var/spool/hylafax
Hi Thijs,
Il giorno dom, 14/10/2012 alle 16.00 +0200, Thijs Kinkhorst ha scritto:
> This security issue was fixed in unstable, thanks for that, but
> wheezy is still lacking the fix. This is because the unstable version
> cannot migrate due to it containing many auxilliary fixes. Could you
> coord
Hi Andreas,
Il giorno gio, 26/07/2012 alle 01.43 +0200, Andreas Beckmann ha scritto:
[...]
> hylafax-server (all versions in squeeze, wheezy, sid) creates the
> following directory:
>
> drwsrwxrwx 2 uucp uucp 40 Dec 12 2010 /var/spool/hylafax/tmp
>
> that is world writable and does not have
Hi Peter,
Il giorno dom, 25/12/2011 alle 15.50 +0200, Peter Eisentraut ha scritto:
> Source: hylafax
> Version: 2:6.0.5-5
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> It fails to build, but does not give any useful reason why:
[...]
Tod
Package: postgresql-client-8.4
Version: 8.4.5-0squeeze2
Severity: grave
Hi all,
I just moved from an old lenny machine to a new squeeze (testing) one,
and moved a few postgresql databases from 8.3 to 8.4 as these are the
shipped versions on Debian.
For one of these databases, I select to only imp
Hi Gregor,
the patch seems good to me. Please, only correct a small typo in
changelog, where you wrote where instead of were.
Bye,
Giuseppe
P.S. Thanks for working on hylafax package
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
Hi all,
the idea behind the use of RUN_HYLAFAX=1 is that the user should be able
to enable or disable hylafax daemon. This is not easy at all, since
hylafax daemons are many processes, and the user may select to start a
few of them from inittab. BTW, if the only way to start daemons is from
init.d
Il giorno mar, 07/12/2010 alle 18.18 +0100, gregor herrmann ha scritto:
> On Sun, 28 Nov 2010 14:26:43 +0100, gregor herrmann wrote:
[...]
> Ok, I've now prepared another patch that checks for the existence of
> /etc/mtab before using it, which should solve this bug.
I probably missed the new patc
Hi Gregor,
I reviewed your patch and I think it does not solve completely the
problem.
When you are in a chroot environment, /proc/mounts show all mounts on
all chroot, so you cannot know for sure if the one you found (and you
may found more than one) is yours.
Just to make and example, when I us
On Tue, 18 May 2010 12:48:54 +0200, Yves-Alexis Perez
wrote:
[...]
> Thanks. It doesn't seem strange, so I'm a bit lost. Which kind of mail
> does it crash on? Every one? What kind of account is it? Is there
> attachements to those mails?
[...]
I better checked: it seems eveolution only blocks o
On Tue, 18 May 2010 10:42:39 +0200, Yves-Alexis Perez
wrote:
[...]
> Please reply to the bug using reportbug so we get useful information
> about your installation.
here it is
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experim
Package: evolution
Version: 2.30.1.2-2
Severity: grave
Today evolution from unstable crash whenever I clock on a message title
(in message list window).
After installing evolution-dbg package and running evolution via gdb, I
get this information:
[New Thread 0xb2dfdb70 (LWP 12503)]
Program rece
Il giorno mer, 14/10/2009 alle 23.20 -0700, Ludovico Cavedon ha scritto:
> Hi,
[...]
> Thanks for the backtrace.
> Could you please also attach the output to the terminal when starting it with
> OWLOGGER_DEFAULT=debug qutecom -style plastique
> ?
giuse...@scarafaggio:~$ OWLOGGER_DEFAULT=debug qute
Package: qutecom
Version: 2.2~rc3.hg396~dfsg1-2+b1
Severity: grave
Since last update on unstable, qutecom does not start anymore. This is a
backtrace of what is happening:
giuse...@scarafaggio:~$ gdb qutecom
GNU gdb (GDB) 7.0-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3
Package: dkms
Version: 2.0.22.0-1
Severity: grave
While installing new mptsas driver (from file
mptlinux-4.18.00.00-1dkms.noarch.rpm) using dkms I get an error from
dkms. The error is shown here:
===
Saving old initrd as /boo
Hi all,
Il giorno mer, 29/07/2009 alle 09.39 +0100, Martin Meredith ha scritto:
[...]
> I've suggested that I adopt this, however, the current maintainer seems to
> want
> to stay as maintainer, and just do everything through "accessible by anyone"
> svn. I'm not too sure exactly what he wants to
package openswan-modules-source
forwarded 528747 http://bugs.xelerance.com/view.php?id=1026
thanks
I believe the patch for this problem is already upstream.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.d
Package: openswan-modules-source
Version: 1:2.6.21+dfsg-2
Severity: grave
trying to build klips modules using module-assistant and kernel
2.6.29-2-686 I get this error:
Building module for a 2.6 kernel
make[3]: Entering directory `/usr/src/modules/openswan'
make[4]: Entering directory `/usr/src/m
Same here. I don't know if could help, but running with "strace -ff", I
get this log:
[...]
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libc.so.6", O_RDONLY)= 3
read(3,
"\177ELF\1\2\1\0\0\0\0\0\0\0\0\0\0\3\0\10\0\0\0\1\0\1m\204\0\0\0004"...,
I wrote a small patch for this bug:
===
--- /usr/sbin/update-exim4.conf.orig2009-05-02 09:57:17.0 +0200
+++ /usr/sbin/update-exim4.conf 2009-05-10 10:32:40.0 +0200
@@ -150,7 +150,7 @@
# add localhost, get rid of spaces, trailing (
Package: exim4-config
Version: 4.69-10
Severity: grave
I got this error updating exim4-daemon-light on un unstable machine. The
result was a machine without exim running.
When executing the command "/usr/sbin/update-exim4.conf" (automatically
started from /etc/init.d/exim4) I get an error from "s
Package: pidgin
Version: 2.5.5-1
Justification: renders package unusable
Severity: grave
pidgin does not start anymore. This is what happens:
giuse...@scarafaggio:~$ pidgin
Illegal instruction
or
giuse...@scarafaggio:~$ strace -ff pidgin 2>&1 | tail -40
[pid 23380] gettimeofday({1241344224, 266
Shold this bug be merged with #523716 ?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Same problem with 2.6.26 linux kernel.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: util-linux
Version: 2.13.1.1-1
Severity: grave
Tags: patch
Yesterday I tried the d-i rc1 for lenny on a silicon graphics O2 (a
complete report is available as Debian bug #510060).
The problem I found against fdisk is that when using large disks (i.e.,
disks with more than 4096 sectors pe
Hi anonymous reporter,
Il giorno sab, 11/10/2008 alle 09.06 -0400, debian ha scritto:
> Package: cups
> Version: 1.3.8-1lenny1
> Severity: grave
> Justification: renders package unusable
[...]
in this report, you show a log with this error:
D [11/Oct/2008:08:31:37 -0400] [CGI] /usr/lib/cups/cgi-
Il giorno sab, 18/10/2008 alle 18.56 +0200, Christian Perrier ha
scritto:
[...]
> What puzzles me in the debug log you sent is:
>
> read(5, "/usr/lib/cups/cgi-bin/printers.cg"..., 1023) = 54
> time(NULL) = 1223728808
>
> an "i" letter seems to be missing there...
Thi
Package: udev
Version: 0.125-3
Severity: serious
Justification: no longer builds from source
Hi,
I am rebuilding udev on a debian etch using all required dependency
backported (recompiled and installed).
When building udev with command "dpkg-buildpackage -b -rfakeroot" I get
this error:
[...]
ma
Hi Jamey,
/usr/bin/awk is a symbolic link to the real awk alternative installed on
your system.
If I understood your report correctly, you was installing a new Debian
testing system. While still at the first installation run, you was
downloading/unpacking/configuring both awk (which one?) and libpa
Hi Lukasz,
I read your logs, but I need one more information (at least): what shell
are you using? And what version is it?
Bye,
Giuseppe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Lukasz,
could you please execute this command being sure you get the error? It
will log all actions from faxaddmodem into /tmp/faxaddmodem.log. Then
please send to me that file.
# sh -x /usr/sbin/faxaddmodem 2>/tmp/faxaddmodem.log
thanks,
Giuseppe
--
To UNSUBSCRIBE, email to [EMAIL PROTEC
package hylafax-server
retitle 443070 faxaddmodem doesn't release lock file in /var/lock/
quit
Hi Lukasz,
I changed the title of this bug report and I'll try to fix it during the
next days.
Bye,
Giuseppe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble?
On Thu, 20 Sep 2007 11:15:16 -0500 "Lukasz Szybalski" <[EMAIL PROTECTED]> wrote:
[...]
> faxserver:/home/unique# faxaddmodem
> Serial port that modem is connected to [ttyS0]? ttyS3
> Sorry, the device is currently in use by another program.
Hi Lukasz,
I think I found the problem: when faxaddmodem
Il giorno gio, 20/09/2007 alle 11.15 -0500, Lukasz Szybalski ha scritto:
[...]
> faxserver:/home/# dmesg |grep ttyS
> serial8250: ttyS3 at I/O 0x2e8 (irq = 3) is a 16550A
> 00:08: ttyS3 at I/O 0x2e8 (irq = 4) is a 16550A
> :05:04.0: ttyS0 at I/O 0x1010 (irq = 201) is a 16550A
> :05:04.0
Hi Lucas,
what card are you using? What are its vendor and model names? What is
the output of these commands:
# cat /proc/devices
# for i in $(find /proc -name \*serial\*)
do
echo '***' $i
[ -f "$i" ] && cat "$i" || ls -l "$i"
done
# (lspci ; lspci -n) | sort
# lsof | grep ttyS
Bye,
G
Hi Lucas,
faxaddmodem tell you that the device is in use, so probably the device
is in use. Could you please check who is using the device? One way to
see the process id is:
[EMAIL PROTECTED]:~$ sudo lsof /dev/ttyS0
Password:
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
faxgetty 3196 uucp
Il giorno sab, 10/03/2007 alle 14.43 -0800, Steve Langasek ha scritto:
> Hi Stephen,
>
> Here's the final NMU diff for the NMU which I'm uploading. The NMU will be
> uploaded to incoming shortly.
[...]
Hi Steve,
I prepared a new upload for this package too. It has been ready for one
week now sin
Hi Jamie,
Il giorno lun, 26/02/2007 alle 17.02 -0500, Jamie ffolliott ha scritto:
[...]
> The issue that forces manual editing is that: the package wants to maintain
> the libpam-ldap.conf, and will not allow me to specify a "uri" setting to
> speak to the ldap server via ldaps://. There are almo
Hi Jamie,
Il giorno lun, 26/02/2007 alle 12.38 -0800, Steve Langasek ha scritto:
[...]
> The nature of this bug is that the libpam-ldap.conf has been manually
> edited, and on upgrade the user is *not* prompted again, but the local
> changes are overwritten instead. That's the behavior that needs
Il giorno lun, 26/02/2007 alle 20.04 -0800, Steve Langasek ha scritto:
> On Mon, Feb 26, 2007 at 10:32:45AM +0100, Giuseppe Sacco wrote:
[...]
> > > Is the diff available somewhere for comment?
>
> > http://centrum.lixper.it/~giuseppe/libpam-ldap_183-0.0.diff.gz
> &g
Il giorno sab, 20/01/2007 alle 17.58 -0500, Jamie ffolliott ha scritto:
> Package: libpam-ldap
> Version: 180-1.4
>
> After an apt-get upgrade, the libpam-ldap packate updated, and in doing so
> it rewrote parts of the /etc/pam_ldap.conf file as follows
> - rewrote host, base, ldap_version, pam_pa
Hi Steve
Il giorno lun, 26/02/2007 alle 00.54 -0800, Steve Langasek ha scritto:
> On Mon, Feb 26, 2007 at 08:44:37AM +0100, Giuseppe Sacco wrote:
> > Il giorno lun, 26/02/2007 alle 01.31 -0500, Jamie ffolliott ha scritto:
> > > I'm on i386. A binary package is ok. Tha
Il giorno lun, 26/02/2007 alle 01.31 -0500, Jamie ffolliott ha scritto:
> I'm on i386. A binary package is ok. Thanks, I will have to try sometime
> tomorrow or in the evening.
http://centrum.lixper.it/~giuseppe/libpam-ldap_183-0.0_i386.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Hi Jamie,
in your bug reports you did not specify the architecture you are using.
I have a preliminary version for i386 that I wish you could test.
Please let me know if you have time to test it and if you prefer the
i386 binary or the source package.
Thanks,
Giuseppe
signature.asc
Description:
Il giorno mer, 21/02/2007 alle 16.23 -0500, Jamie ffolliott ha scritto:
> Package: libpam-ldap
> Version: 180-1.6
>
> 3rd report - can we please get an acknowledgement from somebody?
>
> The package is still broken in how it handles existing settings upon
> upgrades, and these settings are critic
Hi Debian kernel team,
would you please tag this bug as WONTFIX, so that it does not get
included in bug squashes anymore?
Thanks,
Giuseppe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
w a compiler bug.
+ *
+ * Giuseppe Sacco, 20061203
+ */
+assert(format != NULL);
+
va_list args;
va_start(args, format);
@@ -217,7 +227,18 @@
msg->msg + 4, MAXMSGSIZE + 1, format, args) + 1;
va_end(args);
+/*
+ * Changed from
if (len <=
Hi Thomas,
I read the whole report and maybe I misunderstood one point: you are
writing that the default config create the GettArgs option
in /etc/hylafax/config.ttyS?, so you tell that default config would call
getty.
I understand your point, but GettyArgs isn't enought to let hylafax call
getty:
Il giorno sab, 26/08/2006 alle 04.07 +0200, thomas schorpp ha scritto:
> Giuseppe Sacco wrote:
[...]
> > 1. if you do not want the have getty called on data calls, just set a
> > blank value for GettyArgs in /etc/hylafax/config.ttyS? . Then restart
> > hylafax.
> >
&g
Il giorno ven, 25/08/2006 alle 12.24 +0200, Thomas Schorpp ha scritto:
> Giuseppe Sacco wrote:
> >>Package: hylafax-server
> >>Version: 1:4.2.1-5sarge3
> >>Severity: grave
> >>Tags: security
> >>Justification: renders package unusable
> >>
&
> Package: hylafax-server
> Version: 1:4.2.1-5sarge3
> Severity: grave
> Tags: security
> Justification: renders package unusable
>
> Some line modems misinterpret human voice as V.9x, etc, connection
> requests. This makes the server spawn getty-link with attach to the
> line modem device which lo
Hi CAIRO,
I don't know if you had a look at the suggestion Lee wrote on this bug
report. It is available at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=363464 in the lower
part of the page.
Please try it and let me know if it solve the problem.
Thanks,
Giuseppe
--
To UNSUBSCRIBE, email t
package: tar
version: 1.15.91-1
severity: grave
Hi,
today I upgrade my unstable box and now it seems I cannot use tar
anymore:
[...]
[EMAIL PROTECTED]:/tmp/hylafax-4.3.0/cc$ LC_ALL=C LANG=C tar xzf
../../hylafax_4.3.0.orig.tar.gz
tar: ldap-nss.c:1312: do_init: Assertion
`cfg->ldc_uris[__session
Hi Matej,
Il giorno mar, 06/06/2006 alle 23.02 +0200, Matej Vela ha scritto:
[...]
> Unfortunately, there is no way to tell whether db_get returned a
> user-specified/preseeded value (which we should leave alone) or the
> value of the Default field (which we might want to override base
Hi Richard,
I am closing your bug report since in two months I never got a reply
from you and the problem was related to your configuration.
Bye,
Giuseppe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi all,
today I uploaded a new version of hylafax. This is not just a new Debian
package since it include a new upstream version.
The new version, 4.3.0-1, is currently available in unstable and will be
in testing in 10 days. A backported version for sarge is available for
i386[0] and powerpc[1].
CAiRO ha scritto:
[...]
Shouldn't there be a rule for text files by default? I haven't changed
anything in /etc/hylafax/typerules.
Yes, such a rule exists but it seems that it only works for plain 8bit
ASCII files. I will try to write a new rule and add it.
In the meantime, may I have a copy
CAiRO ha scritto:
Package: hylafax-client
Version: 2:4.2.5-3
Severity: serious
Justification: Policy 1.2.3
file fax.txt
fax.txt: UTF-8 Unicode text
So fax.txt is utf-8 text, but when I try to do:
sendfax -d 0815 fax.txt
fax.txt: Can not determine file type
Hylafax uses a private way to unde
Il giorno mer, 05/04/2006 alle 23.30 +1200, Richard J.Fairhall ha
scritto:
> Hi
>
> MIMENCODE was set to blank and ENCODING was set to 'base64' when I was having
> the encoding issue. I ran faxsetup and it changed MIMENCODE to
> '/usr/bin/mimencode' which fixed the issue.
[...]
Hi Richard,
this
Hylafax 4.2.5-1 was using the package mime-codecs in order to
call /usr/bin/base64-encode when converting TIFF or PDF to attachments.
mime-codecs is no more in Debian, so in hylafax 4.2.5-3 I decided to
use /usr/bin/uuencode from sharutils, since it is capable of converting
to base64.
The new con
Il giorno gio, 30/03/2006 alle 14.16 +1200, Richard Fairhall ha scritto:
> Package: hylafax
> Severity: grave
> Justification: renders package unusable
>
> Upgrading to 4.2.5-3 breaks mime encoding. When emails are sent to users
> with binary files attached such as tif or pdf the files are empty.
Bastian Blank ha scritto:
On Fri, Mar 17, 2006 at 12:46:21PM +0100, Giuseppe Sacco wrote:
Are you working on testing or unstable?
According to the db of ftp-master, both have the same version.
Right, but where did you use it? testing or unstable? I would like to
get the same environmnet
Bastian Blank ha scritto:
Package: hylafax-server
Version: 4.2.5-1
Severity: grave
hylafax-server fails to install if there is no configuration, which it
fails to create.
Are you working on testing or unstable?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tr
Package: hylafax-server
Version: 1:4.2.1-5sarge3
Hi Ernst,
thanks for your report and your patch. A new hylafax version was already
prepared with the Debian Security Team. This new package version has
been released yesterday.
I am closing this bug report since the problem has been already fix
Blars Blarson wrote:
On Mon, Aug 15, 2005 at 09:17:08AM +0200, Giuseppe Sacco wrote:
[...]
2. check that all daemons exited, using "ps aux | grep fax"
faxgetty restarts itself. Kill it and it restart again.
Are you runnig faxgetty from inittab? Could you please check if you ha
Hi Blars,
Blars Blarson wrote:
[...]
Hylafax refuses to configure durring upgrading from woody to sarge:
[...]
Could you please check if your problem is the same as bug #321854?
You may find more information about it here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321854
To try to fix
I just checked all hylafax scripts and the problem you reported is
present on many scripts:
etc/faxsetup.sh.in
etc/faxaddmodem.sh.in
util/wedged.sh.in
util/faxrecvd.sh.in
util/recvstats.sh.in
util/notify.sh.in
util/notify-4.1.sh.in
util/tiff2fax.sh.in
util/xferstats.sh.in
port/install.sh.in
html/t
Il Sun, Feb 27, 2005 at 12:14:23PM +0100, Bastian Blank ha scritto:
> Package: hylafax-server
> Version: 1:4.2.1-2
> Severity: grave
>
> Default faxrcvd uses the -a parameter of [, this is a bashism, but use
> /bin/sh, not /bin/bash.
I just checked manual pages of bash, dash, ksh and it seems th
Il Sun, Feb 27, 2005 at 11:23:26AM +0100, Bastian Blank ha scritto:
> Package: hylafax-server
> Version: 1:4.2.1-2
> Severity: grave
>
> hylafax-server is not upgradable:
>
> | # apt-get dist-upgrade -u
> | Reading Package Lists... Done
> | Building Dependency Tree... Done
> | Calculating Upgrade
Il giorno mer, 23-02-2005 alle 20:21 +0100, Adrian Bunk ha scritto:
> On Wed, Feb 23, 2005 at 07:59:39PM +0100, Giuseppe Sacco wrote:
[...]
> > Hi Adrian,
> > I did send a message to Noah, yesterday, about this NMU and about those
> > bugs; then I also get some information a
Il giorno mer, 23-02-2005 alle 19:34 +0100, Adrian Bunk ha scritto:
> On Wed, Feb 23, 2005 at 07:07:52PM +0100, Giuseppe Sacco wrote:
>
> > The last NMU upload for WDM include all translation update and fixes the
> > RC bug.
>
> Are you the new maintainer for wdm, or
The last NMU upload for WDM include all translation update and fixes the
RC bug.
Bye,
Giuseppe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
80 matches
Mail list logo
