Re: Proposal: removing libc5, altgcc and all their old-days dependencies
On Fri, Jun 20, 2003 at 09:27:57AM +0200, Francesco P. Lovergine wrote: > On Thu, Jun 19, 2003 at 09:43:23PM +0200, David Weinehall wrote: > > > > You, and rest of the minority who use libc5 program, can dual-boot > > an older distribution of Debian (say potato) where the programs still > > work. Yes, it can be a hassle, but it works. What about a solution using a libc5 aware chroot only, or something such ? So, no need to dual-boot, and a subset of woody containing only the libc5 stuff can be kept even after we drop official support for woody. I don't know if this would be feasible though. Friendly, Sven Luther
Bug#198158: architecture i386 isn't i386 anymore
On Fri, Jun 20, 2003 at 09:51:07AM +0200, Matthias Klose wrote: > Package: general > Severity: serious > Tags: sarge, sid > > [please don't reassign to any gcc/libstdc++ package] > > Nathanel's summary: > http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg02112.html > > A list of proposals what to do: > http://lists.debian.org/debian-devel/2003/debian-devel-200305/msg00360.html > > Some questions on this topic: > http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg01895.html > > > The solution I would favour would be: > > - drop the i386 support > > - keep the i386 architecture name > > - let dpkg-architecture output the new configuration string > (i.e. i486-linux) > > - if anybody wants to start the mini-i386 architecture, we have to > find an architecture name for it. > > changing the dpkg-architecture's ARCH string to i.e. i486 would break > a lot of build scripts ... So, why not fix this buginess of the build script withs going for a new i486 or i686 or whatever arch, and keeping the old i386 around for now. A new autobuilder would be needed, and today, diskspace is not really an unsolvable problem for the archive, which would grow by less than 10% anyway. Later we can either drop i386 entirely, or make a mini-i386 out of it. Other solutions might be to keep i386 around for safety, and implement beside it a newer subarch-aware ix86 archive or something such, and once that does work satisfactoryly move i386 to mini-i386. Come on, we already support 11 or so arches officially, and a bunch of other unofficially, surelly this would not be so expensive for us. Friendly, Sven Luther
Re: [mass bug filing?] Short descriptions being used as long descriptions and other policy violations
Javier Fernández-Sanguino Peña <[EMAIL PROTECTED]> wrote: [...] > However I've found a number of packages which use a long description which > is more or less the _same_ as the short description. Sample: > $ apt-cache show kdebase-data > (...) > Description: KDE Base (shared data) > KDE Base (shared data). > . > This package is part of the official KDE base module. > And some (2) others which do not provide an extended description at all or > provide an extended description of only one line. I've used an ugly scripts > (attached) which produces ugly results (attached too). > I was wondering, should I make a mass filing of bugs for those packages > who fail to produce a proper description? [...] I doubt that just filing bugs without fix makes sense, OTOH if you planned to submit 10 reports with "the description sucks, here is better one - tags:patch" instead of 100 simply stating "the description sucks", please go ahead. ;-) cu andreas
Re: versions of -dev packages
Here is a script that finds different versions of installed binary packages with the same source package name. Running this script on some of my systems gave me lots of interesting information ... find_inconsistent Description: application/shellscript
Re: versions of -dev packages
On Sat, Jun 21, 2003 at 09:52:35AM +0400, Nikita V. Youshchenko wrote:
> Here is a script that finds different versions of installed binary packages
> with the same source package name.
it does not take into account removed (deinstalled) packages, where only the
outdated config files are present.
Attached an ugly quick hack to fix that.
Greetings
Bernd
--
(OO) -- [EMAIL PROTECTED] --
( .. ) [EMAIL PROTECTED],linux.de,debian.org} http://home.pages.de/~eckes/
o--o *plush* 2048/93600EFD [EMAIL PROTECTED] +497257930613 BE5-RIPE
(OO) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
#!/bin/bash
cat /var/lib/dpkg/status | awk '
/^Package:/ {
p=$2
}
/^Status:/ {
st[p]=$2
}
/^Source:/ {
if ($2 in cnt) {
cnt[$2]++;
pkgs[$2] = pkgs[$2] " " p
} else {
cnt[$2] = 1
pkgs[$2] = p
}
}
/^Version:/ {
ver[p]=$2
}
END {
for (s in cnt) {
n = split(pkgs[s], l)
for (i = 2; i <= n && ver[l[i]]==ver[l[1]]; i++);
if (i > n)
continue
print("Source: " s)
for (i = 1; i <= n; i++)
print("Binary " l[i] ": " st[l[i]] "ed version "
ver[l[i]])
print
}
}
'
Re: Bug#198158: architecture i386 isn't i386 anymore
On Sat, Jun 21, 2003 at 03:06:17AM +0200, Sam Hocevar wrote: > > Really? Seems wrong to me. > >Indeed. MMX and PPro are orthogonal features. Wasn't there "Pentium MMX" in between? I have at least one computer with one of those processors.
TOP URGENT!
DEAR SIR/MADAM We have to introduce ourselves as one of the leading trading company in thefield of buying, selling and importing the raw material of yarn to thetextile co.You are kindly to be informed that the below mention items are the productsthat we work on them and we would like know if you could supply these itemsfor us:1-Pre-oriented yarn (p.o.y)2-polyester staple fiber3-viscose staple fiber4-acrylic staple fiber WE ARE IN URGENT NEED FOR : item :COTTON FIBER 1)COTTON FIBER (EXELNET GRADE WITH G.M.W INETNATIONAL STANDARD). 2)COTTON FIBER (A GRADE WITH S.M.W INETNATIONAL STANDARD). 3)COTTON FIBER ( B GRADE WITH M.W INETNATIONAL STANDARD). quantoty:500tons PLEASE SEND US YOUE COMPETATIVE PRICE(CIF BANDAR ABBAS 3%). BRGDS: ALYAFNAKH CO. HOSSEINEJAD&KHEYRABI GENERAL MANAGERS TELL:+9821-6412969 FAX:+9821-6416427 ADD:20,SHAGHAYEGH ST,VALIASR SQ,TEHRAN-IRAN
TOP URGENT!
DEAR SIR/MADAM We have to introduce ourselves as one of the leading trading company in thefield of buying, selling and importing the raw material of yarn to thetextile co.You are kindly to be informed that the below mention items are the productsthat we work on them and we would like know if you could supply these itemsfor us:1-Pre-oriented yarn (p.o.y)2-polyester staple fiber3-viscose staple fiber4-acrylic staple fiber WE ARE IN URGENT NEED FOR : item :COTTON FIBER 1)COTTON FIBER (EXELNET GRADE WITH G.M.W INETNATIONAL STANDARD). 2)COTTON FIBER (A GRADE WITH S.M.W INETNATIONAL STANDARD). 3)COTTON FIBER ( B GRADE WITH M.W INETNATIONAL STANDARD). quantoty:500tons PLEASE SEND US YOUE COMPETATIVE PRICE(CIF BANDAR ABBAS 3%). BRGDS: ALYAFNAKH CO. HOSSEINEJAD&KHEYRABI GENERAL MANAGERS TELL:+9821-6412969 FAX:+9821-6416427 ADD:20,SHAGHAYEGH ST,VALIASR SQ,TEHRAN-IRAN
Re: Bug#198158: architecture i386 isn't i386 anymore
Aaron Lehmann <[EMAIL PROTECTED]> wrote: > On Sat, Jun 21, 2003 at 03:06:17AM +0200, Sam Hocevar wrote: >>> Really? Seems wrong to me. >>Indeed. MMX and PPro are orthogonal features. > Wasn't there "Pentium MMX" in between? I have at least one computer > with one of those processors. They are orthogonal, there are both *586 and *686 with and without MMX. Iirc the development tree looks like this: -- time ---> Pentium PProPentiumII (PPro+MMX) | +--Pentium MMX cu andreas
Re: [mass bug filing?] Short descriptions being used as long descriptions and other policy violations
On pe, 2003-06-20 at 18:53, Javier Fernández-Sanguino Peña wrote: > I was wondering, should I make a mass filing of bugs for those packages > who fail to produce a proper description? Since this can seemingly be checked automatically, I would prefer you make a patch for lintian and/or linda instead. This way, there are not hundreds of new bug reports, which means less hassle for the maintainers, and new packages will also be checked for this. -- Enemies of Carlotta 1.0 mailing list manager: http://liw.iki.fi/liw/eoc/
Re: Bug#198158: architecture i386 isn't i386 anymore
On Fri, Jun 20, 2003 at 09:51:07AM +0200, Matthias Klose wrote: | Package: general | Severity: serious | Tags: sarge, sid | | [please don't reassign to any gcc/libstdc++ package] | | Nathanel's summary: | http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg02112.html | | A list of proposals what to do: | http://lists.debian.org/debian-devel/2003/debian-devel-200305/msg00360.html | | Some questions on this topic: | http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg01895.html | | | The solution I would favour would be: | | - drop the i386 support | | - keep the i386 architecture name | | - let dpkg-architecture output the new configuration string | (i.e. i486-linux) | | - if anybody wants to start the mini-i386 architecture, we have to | find an architecture name for it. | | changing the dpkg-architecture's ARCH string to i.e. i486 would break | a lot of build scripts ... | | comments welcome. | | | | -- | To UNSUBSCRIBE, email to [EMAIL PROTECTED] | with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] | | Please keep , a i386 or i586 architecture , for the via C3 processor . i686 architecture is not compatible with C3 . This processor is very used in the Via EPIA motherboard : See : http://www.viavpsd.com/product/epia_mini_itx_spec.jsp?motherboardId=21 http://www.mini-itx.com/ -- / Erwan MAS /\ | mailto:[EMAIL PROTECTED] |_/ ___| | \___\__/
Update re: read-only root filesystem
Some progress has been made toward the goal of making Debian easier to use with a read-only root filesystem. Action has been taken to remove variable files from /etc/, or at least to make it possible to do so locally, in the following packages: cupsys, laptop-net, pppconfig, sysvinit. Packages that still employ variable files in /etc/ include: mount, ifupdown, dhcpcd, linuxlogo, ppp, util-linux. Fortunately, some of the files can be replaced by symlinks. See my README file at http://panopticon.csustan.edu/thood/readonly-root.html for (incomplete) information. Many thanks to the maintainers who have been supporting this effort. -- Thomas Hood
Developer Accessible Hurd Machine
Greetings, Some time ago, Martin Schulze pointed out that there is no developer accessible Hurd machine available. I am happy to coordinate the donation of hardware for this if it is this something that you (developers, Hurd and otherwise) feel would be useful and possible? However, I've heard that Hurd is still unstable enough that we will probably need to place the machine at a Hurd developer's home or work. -devel: Is this something developers would like? -hurd: If consensus says we proceed, are there any volunteers for hosting this? Please include me to replies to -hurd since I am not on that list. Regards, Mako -- Benj. Mako Hill | Debian Hardware Donations Manager [EMAIL PROTECTED] | "Project Quartermaster" http://mako.yukidoke.org/ | [EMAIL PROTECTED] pgppq7Q2QRovG.pgp Description: PGP signature
Re: [mass bug filing?] Short descriptions being used as long descriptions and other policy violations
On Sat, Jun 21, 2003 at 12:09:29PM +0300, Lars Wirzenius wrote: > > I was wondering, should I make a mass filing of bugs for those packages > > who fail to produce a proper description? > > Since this can seemingly be checked automatically, I would prefer you > make a patch for lintian and/or linda instead. Lintian already tries to catch those like kdebase-data. > This way, there are not hundreds of new bug reports, which means less > hassle for the maintainers, and new packages will also be checked for > this. ...and everyone will continue pretending everything's fine. :P Automated checks are a good idea, but sometimes you just have to tell people explicitely to cut it out with the automated description shit. Perhaps hundreds of bug reports are clutter themselves, but it's not like they're undeserved. -- 2. That which causes joy or happiness.
Donation Available: Alphastation 200 (currently in the Netherlands)
Greetings, I have a (perhaps somewhat stale) offer from a donor for a Alphastation 200 in Amsterdam. If people are interested, please email me off list. The usual rules apply: Debian developers and people in close geographic proximity to get precedence in most cases but neither is absolutely necessary. Please CC me on mail to the -alpha list since I do not read the list. Regards, Mako -- Benj. Mako Hill | Debian Hardware Donations Manager [EMAIL PROTECTED] | "Project Quartermaster" http://mako.yukidoke.org/ | [EMAIL PROTECTED] pgpCoN1GPjCpI.pgp Description: PGP signature
Donation Available: SGI Indys
Greetings, I'm pleased to announce that there's been a bit of a glut in SGI Indys donated to Debian recently in both California and Germany. There are three Indy's available in Southern California and additional one may have a history of difficult booting. We can work out the details of this before we transfer them. The Californian hardware ranks as follows: 1-175mhz 128M & 4G hard drive. 24 bit graphics 1-175mhz 128M & 1G hard drive. 8 bit graphics 1-150mhz 64 or 96M 1G hd and 8 bit graphics. this box also has a FDDI board i think. Additionally, there are: 2- Indy cams 1- R4600 133 mhz CPU 1- R4600 100 mhz CPU several sleds many memory sticks (although many are small: 8Mb or 16Mb) The donor is willing to ship the machines either individually or to a central location, perhaps in southern California, where someone can swap things around and then reship them. Pending DPL approval, we can reimburse the person who does this for their shipping cost. Also, there are five Indys available in Germany already mentioned on an SPI list. I'm not sure what the status on these machines is but the donor can noot ship them. If people in Germany or near near-by are interested, I will try to arrange something with a developer in close proximity to the donor and then arrange for shipping reimbursement as well if possible. The routine is the normal one. If you'd like to get your hands on an Indy, email me personally, off list with the reason why you'd like it or need it or what you will use it for. If it's not Debian or free software related, don't bother. Priority goes to official Debian developers and NMs and people in close geographic proximity but neither are essential. Let me know if you have any questions or comments. Thanks! Regards, Mako -- Benj. Mako Hill | Debian Hardware Donations Manager [EMAIL PROTECTED] | "Project Quartermaster" http://mako.yukidoke.org/ | [EMAIL PROTECTED] pgpCqOWJD8Ber.pgp Description: PGP signature
Bug#198158: architecture i386 isn't i386 anymore
On Friday 20 June 2003 15:40, Josip Rodin wrote: > On Fri, Jun 20, 2003 at 02:25:52PM +0200, Adam Borowski wrote: > > As i686 is already like ten(?) years old, > > I was intrigued by this statement and went to look it up. > > CPU: Released: > - > 80386 1985 > 80486 1989 > Pentium 1993 > Pentium Pro 1995 > > > I would say 99.9% [1] machines that run sarge are 686 and higher > > > > [1] 90% of statistics are made up on the spot. > > Right. I can't say I have many at least one i586 and one i486 that I'd like to be able upgrade to 3.1 when > it comes out. > I think there are a few more
Bug#198314: RFA: rxsock, rexxtk
Package: wnpp Severity: normal rxsock[1] and rexxtk[2] need new maintainers. rxsock - Socket function library for Regina REXX rexxtk - Interface to Tcl/Tk for Regina REXX Rick -- [1] http://sourceforge.net/projects/rxsock/ [2] http://rexxtk.sourceforge.net/
Re: ITP: libtext-charwidth-perl, libtext-wrapi18n-perl
Tomohiro KUBOTA wrote: > Package: libtext-charwidth-perl > Description: Get width of characters on terminal > This module permits perl softwares to get the width of characters > and strings on terminal, using wcwidth() and wcswidth() in C. > . > It provides mbwidth(), mbswidth(), and mblen(). s/Get/get/; s/softwares/software/; s/width of characters (and strings)? on terminal/ display width of characters and strings on the terminal/x; (or at least, s/on terminal/on the terminal/) s/in C/from libc/; > Package: libtext-wrapi18n-perl > Description: International substitution of Text::Wrap > This module intends to substitute Text::Wrap, which supports > multibyte characters such as UTF-8, EUC-JP, and GB2312, fullwidth > characters such as east Asian characters, combining characters > such as diacritical marks and Thai, and languages which don't > use whitespaces between words such as Chinese and Japanese. > . > It provides wrap(). s/International substitution/internationalized substitute/; s/intends to substitute/is a substitution for/; s/, which supports/, supporting/; > License: perl Be careful of the tough new perl licensing policy of the ftp master. :-/ > Since these packages have to be Depends:ed by debconf package, > Priority: of these packages have to be important. (Joey and I > have agreed on this point, please see the debian-i18n thread.) Yep. -- see shy jo pgpybayBxmQoD.pgp Description: PGP signature
Re: Update re: read-only root filesystem
> Packages that still employ variable files in /etc/ include: > mount, ifupdown, dhcpcd, linuxlogo, ppp, util-linux. > Fortunately, some of the files can be replaced by symlinks. > See my README file at > http://panopticon.csustan.edu/thood/readonly-root.html > for (incomplete) information. > > Many thanks to the maintainers who have been supporting > this effort. Many thanks for your efforts too - I successfully swicthed to ro / with these advices (the only strange thing related to mount is that I can see the .journal ext3 file in / despite the fact that /dev/root is marked ext3 in /proc/mounts - remounting the / again solves this strange behaviour) A last remark: should/when will we consider that writing to /etc is a bug?
Re: Update re: read-only root filesystem
[I hope I did not sent twice this mail] > Packages that still employ variable files in /etc/ include: > mount, ifupdown, dhcpcd, linuxlogo, ppp, util-linux. > Fortunately, some of the files can be replaced by symlinks. > See my README file at > http://panopticon.csustan.edu/thood/readonly-root.html > for (incomplete) information. > > Many thanks to the maintainers who have been supporting > this effort. Many thanks for your efforts too - I successfully swicthed to ro / with these advices (the only strange thing related to mount is that I can see the .journal ext3 file in / despite the fact that /dev/root is marked ext3 in /proc/mounts - remounting the / again solves this strange behaviour) Another small problem occurs when trying to keep /dev in ro: # /etc/init.d/sysklogd start Starting system log daemon: syslogdchmod: changing permissions of `/dev/xconsole': Read-only file system Must /dev be in a rw fs? A last remark: should/when will we consider that writing to /etc is a bug?
Bug#198326: ITP: gdm-themes -- Themes for the GNOME Display Manager
Package: wnpp Version: unavailable; reported 2003-06-21 Severity: wishlist * Package name: gdm-themes Version : 0.1 Upstream Author : Many * URL : http://art.gnome.org/ http://ftp.ximian.com/pub/xd2/redhat-9-i386/source/ * License : GPL Description : Themes for the GNOME Display Manager This package provides a few additionnal themes for the GNOME Display Manager's greeter, giving different looks to your graphical login screen. To select them, use the gdmconfig software. There are random LGPL and GPL stuff in these themes, so I'm planning to just share everything under the GPL. A preliminary package is available at http://people.debian.org/~joss/packages/ . Thanks to appropriate use of JPEG, it is just a 350 KB download. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom pgpNtyHlvU3ol.pgp Description: PGP signature
Experimental: proftpd pre-1.2.9, for brave hearts
Hi guys this is to announce a preview (off sid) for current (cvs) version of proftpd. Testing and comments are welcome. An (incomplete) IPv6 patch is also available. http://people.debian.org/~frankie/debian/sid/experimental/proftpd/ The package will not be uploaded in sid, until a complete IPv6 patch will be available or 1.2.9 will be released. PS: it's intentionally a native pkg. -- Francesco P. Lovergine
Bug#198158: architecture i386 isn't i386 anymore
On Sat, Jun 21, 2003 at 02:13:03PM +0200, Allan Sandfeld Jensen wrote: > server, and it's pleanty fast. But more specialized libraries for i686 would > be a welcomed thing, both the scheduling and additional instructions can give > _significant_ speed-ups for many applications. Prove it or lose it. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | Dept. of Computing, `. `' | Imperial College, `- -><- | London, UK pgpmF5MQLLh5i.pgp Description: PGP signature
Re: Experimental: proftpd pre-1.2.9, for brave hearts
On Sat, 21 Jun 2003, Francesco Paolo Lovergine wrote: > Hi guys > > this is to announce a preview (off sid) for current (cvs) > version of proftpd. Testing and comments are welcome. > An (incomplete) IPv6 patch is also available. > > http://people.debian.org/~frankie/debian/sid/experimental/proftpd/ > > The package will not be uploaded in sid, until a complete IPv6 patch will > be available or 1.2.9 will be released. Just to avoid some duplicate work I am already on the IPv6 pkg... Thanks frankie for pkgs and patch! Fabio -- Our mission: make IPv6 the default IP protocol "We are on a mission from God" - Elwood Blues http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html
Bug#198158: architecture i386 isn't i386 anymore
Sven Luther <[EMAIL PROTECTED]> wrote: [...] > Come on, we already support 11 or so arches officially, and a bunch of > other unofficially, surelly this would not be so expensive for us. IMHO it's better to be coherent with the ARCH name. If i386 arch is no more supported, let's go to the next generation until the gcc support will drop the i486. -- Arnaud Vandyck, STE fi, ULg Formateur Cellule Programmation.
Can a polish speaker please translate this?
I got a bug report in what seems to be Polish. Unfortunately, babelfish can't handle it. Although I have a good idea of what it might be saying, just to make sure can someone translate it for me? -- Jaldhar H. Vyas <[EMAIL PROTECTED]> La Salle Debain - http://www.braincells.com/debian/ -- Forwarded message -- From: [EMAIL PROTECTED] Resent-From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Resent-cc: [EMAIL PROTECTED] (Jaldhar H. Vyas) Date: Sat, 21 Jun 2003 10:58:40 +0200 Resent-Date: Sat, 21 Jun 2003 09:03:05 UTC Subject: Bug#198276: Blad przy instalacji pakietu webmin_094woody1 Package: webmin Version: 0.94-7woody1 Wystepuje blad przy instalacji pakietu. Pakiet nie jest instalowany w calosci Powoduje to ze zaden pakiet dodatkowy nie jest instalowany Brakuje plikow webmin.acl, update.conf i innych Zapis sesji : [EMAIL PROTECTED]:~/webmin# dpkg -i webmin_0.94-7woody1_all.deb Zaznaczenie poprzednio nieznaznaczonego pakietu webmin. (Odczytywanie bazy danych ... 60487 plików i katalogów obecnie zainstalowanych.) Rozpakowanie webmin (z webmin_0.94-7woody1_all.deb) ... Konfigurowanie webmin (0.94-7woody1) ... [EMAIL PROTECTED]:~/webmin# dpkg -i webmin-core_0.94-7woody1_all.deb Zaznaczenie poprzednio nieznaznaczonego pakietu webmin-core. (Odczytywanie bazy danych ... 61146 plików i katalogów obecnie zainstalowanych.) Rozpakowanie webmin-core (z webmin-core_0.94-7woody1_all.deb) ... Konfigurowanie webmin-core (0.94-7woody1) ... /etc/webmin/webmin.acl: Nie ma takiego pliku ani katalogu dpkg: b³±d przetwarzania webmin-core (--install): podproces post-installation script zwróci³ kod b³êdu 2 Wyst±pi³y b³êdy podczas przetwarzania: webmin-core U¿ywam Debiana GNU/Linux 3.0, j±dra 2.4.20 (wlasna kompilacja)
Re: Can a polish speaker please translate this?
On Sat, Jun 21, 2003 at 05:07:36PM -0400, Jaldhar H. Vyas wrote: > Konfigurowanie webmin-core (0.94-7woody1) ... > /etc/webmin/webmin.acl: Nie ma takiego pliku ani katalogu > dpkg: b³±d przetwarzania webmin-core (--install): > podproces post-installation script zwróci³ kod b³êdu 2 > Wyst±pi³y b³êdy podczas przetwarzania: > webmin-core Not sure, but this link: http://mplayerhq.hu/pipermail/mplayer-users/2003-May/033284.html gives me the impression that "Nie ma takiego pliku ani katalogu" is ENOENT. -Josh -- New PGP public key: 0x27AFC3EE pgpkdQeyW6a92.pgp Description: PGP signature
Re: Can a polish speaker please translate this?
On Sat, Jun 21, 2003 at 05:07:36PM -0400, Jaldhar H. Vyas scribbled: > I got a bug report in what seems to be Polish. Unfortunately, babelfish > can't handle it. Although I have a good idea of what it might be saying, > just to make sure can someone translate it for me? Very thoughtful user, indeed Oh well, below is the translation > Jaldhar H. Vyas <[EMAIL PROTECTED]> > La Salle Debain - http://www.braincells.com/debian/ > > -- Forwarded message -- > From: [EMAIL PROTECTED] > Resent-From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Resent-cc: [EMAIL PROTECTED] (Jaldhar H. Vyas) > Date: Sat, 21 Jun 2003 10:58:40 +0200 > Resent-Date: Sat, 21 Jun 2003 09:03:05 UTC > Subject: Bug#198276: Blad przy instalacji pakietu webmin_094woody1 > > Package: webmin > Version: 0.94-7woody1 > > Wystepuje blad przy instalacji pakietu. Pakiet nie jest instalowany w calosci There has been an error installing the package. The package isn't entirely installed. > Powoduje to ze zaden pakiet dodatkowy nie jest instalowany It will cause that none of the additional (probably meant - depending upon this package) packages will be installed. > Brakuje plikow webmin.acl, update.conf i innych The webmin.acl, update.conf and other files are missing > Zapis sesji : Session transcript: > [EMAIL PROTECTED]:~/webmin# dpkg -i webmin_0.94-7woody1_all.deb > Zaznaczenie poprzednio nieznaznaczonego pakietu webmin. > (Odczytywanie bazy danych ... 60487 plików i katalogów obecnie > zainstalowanych.) > Rozpakowanie webmin (z webmin_0.94-7woody1_all.deb) ... > Konfigurowanie webmin (0.94-7woody1) ... the usual dpkg blurb > [EMAIL PROTECTED]:~/webmin# dpkg -i webmin-core_0.94-7woody1_all.deb > Zaznaczenie poprzednio nieznaznaczonego pakietu webmin-core. > (Odczytywanie bazy danych ... 61146 plików i katalogów obecnie > zainstalowanych.) > Rozpakowanie webmin-core (z webmin-core_0.94-7woody1_all.deb) ... > Konfigurowanie webmin-core (0.94-7woody1) ... the same blurb > /etc/webmin/webmin.acl: Nie ma takiego pliku ani katalogu File or directory not found > dpkg: b³±d przetwarzania webmin-core (--install): > podproces post-installation script zwróci³ kod b³êdu 2 > Wyst±pi³y b³êdy podczas przetwarzania: > webmin-core and blurb again > U¿ywam Debiana GNU/Linux 3.0, j±dra 2.4.20 (wlasna kompilacja) I'm using , kernel (own compilation) take care, marek pgpB3yHt5BbNM.pgp Description: PGP signature
Re: Update re: read-only root filesystem
[I'm CC'ing to the debian-devel list] Thomas Hood wrote: >>Another small problem occurs when trying to keep /dev in ro: >># /etc/init.d/sysklogd start >>Starting system log daemon: syslogdchmod: changing permissions of >>`/dev/xconsole': Read-only file system > > This occurs when /etc/init.d/sysklogd tries to do a chmod > on /dev/xconsole . I am not sure it should try to do this. There are other problems : for example it seems that the system changes the /dev/ttyXX or /dev/pts/XX ownership depending on who is being logged in.. it seems that several files in /dev will have to be symlinked to /run/dev and then proper devices being created ? # find /dev -mtime -1 /dev/urandom /dev/ptmx /dev/console /dev/tty1 /dev/tty2 /dev/tty3 /dev/tty4 /dev/tty5 /dev/tty6 /dev/ttyS1 /dev/pts /dev/pts/0 /dev/pts/1 /dev/pts/2 /dev/xconsole /dev/initctl /dev/log Symlinking /dev/xconsole to /run/xcolsole appears to work ; but maybe we should use a ""standard"" (two quotes) "/run/dev" for "changing devices" ? Is there a list of devices that are supposed to change (rights/ownership) during time? And should I fill a BTS for the /etc/init.d/sysklogd bogus with read-only /dev problem anyway? --- Xavier Roche [EMAIL PROTECTED]
Re: Update re: read-only root filesystem
On Sun, Jun 22, 2003 at 01:02:55AM +0200, Xavier Roche wrote: > or /dev/pts/XX ownership depending on who is being > logged in.. this is not a problem due to devpts filesystem. It may be a problem for /dev/cdrom. You can ignore it (use a sane cdrom group) or you can use dev filesystem. For the ttys, you also have to live with it, or simply use the dev filesystem. > /dev/initctl > /dev/log those noth are touched, but are normally sane. > Symlinking /dev/xconsole to /run/xcolsole appears to work ; but maybe we > should use a ""standard"" (two quotes) "/run/dev" for "changing devices" ? you do not need those, pipes can exiat on r/o filesystems without a problem. Greetings Bernd -- (OO) -- [EMAIL PROTECTED] -- ( .. ) [EMAIL PROTECTED],linux.de,debian.org} http://home.pages.de/~eckes/ o--o *plush* 2048/93600EFD [EMAIL PROTECTED] +497257930613 BE5-RIPE (OO) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
Re: Bug#198158: architecture i386 isn't i386 anymore
On Fri, Jun 20, 2003 at 09:11:41PM +0200, Cyrille Chepelov wrote: > Hmmm. Until all of glibc, the kernel and gcc deprecate and discard support > for 386 and 486, I'd love if I could keep my home edgge router running the > way it is thank you very much (and I'm happy with the great job the Security > Team is doing). Not that the flea market value of a Pentium Classic is that > high nowadays, but why fix what works? I thought Free Software was above > planned obsolescence... While we're at it, I fail to see the logic of removing support for i386 while we still support m68k.
Re: Proposal: removing libc5, altgcc and all their old-days dependencies
On Thu, Jun 19, 2003 at 12:57:03PM +0200, Francesco P. Lovergine wrote: > M, that's the basis of freelosophy. Don't use proprietary formats and > don't > use proprietary software. The risk of being unable to use your own > documents is concrete. Who owns your docs? Corel does. Microsoft does. Which is all nice, and which I agree with, but it doesn't solve the problem of what to do with the documents before you realized this was the case! In my own case, I have WordPerfect 4.x and 5.x documents dating back to the late 80s and early 90s that still require occasional usage of WordPerfect. Since providing this capability requires only free software on Debian's part, where exactly is the problem?
Re: Proposal: removing libc5, altgcc and all their old-days dependencies
On Thu, Jun 19, 2003 at 09:43:23PM +0200, David Weinehall wrote: > Alternative 1: > > You, and rest of the minority who use libc5 program, can dual-boot > an older distribution of Debian (say potato) where the programs still > work. Yes, it can be a hassle, but it works. Assuming it supports your hardware. Which it is not entirely likely to do. For instance: Many video cards require XFree 4.3.x or above. They require agpgart in the kernel. They require iwconfig and other wireless tools. There are a whole host of things that are not necessarily going to work from old distributions, and the situation is only getting worse. > Alternative 2: > > Debian can continue to drag along support for libc5-binaries (hey, > nobody out there with need for libc4?) to the end of days, with more and > more problems accumulating, and more and more baggage needed to build > them (for every new release of binutils/gcc/etc, it becomes less likely > that libc5 will work properly without serious tinkering). Why not just ship an old binutils/gcc to build the old libc5 binaries? I really don't understand why this is such a difficult problem. If, for instance, gcc 2.7.2 could build these things three years ago, why can't it now? It's not as if some fundamental kernel structures have changed in a hugely incompatible way; other binaries from that era work fine. -- John
Bug#198158: architecture i386 isn't i386 anymore
On Fri, Jun 20, 2003 at 02:25:52PM +0200, Adam Borowski wrote: > What about perusing the INT 6 idea, and going all the way up to i686? > As i686 is already like ten(?) years old, I would say 99.9% [1] machines > that run sarge are 686 and higher -- thus, moving to i686-specific > optimizations would be good for the vast majority of users (this comes > from someone who set up two servers on P MMX two weeks ago :p) I have *numerous* i586 machines installed at work. Not everyone can afford to upgrade for no good reason. Our i586 makes a perfectly good and reliable firewall (thanks to the Debian shorewall package). We have another one running a few dial-in lines for our traveling employees. There are others at various times doing specific tasks. An i586 works fine for these, even 100MHz or lower, and I think removing support for it would be a fairly silly thing. As I say this, I'm sure people can say the same about i486 and even i386 machines. Why exactly do we need to remove this support? While we're at it: not everyone reading e-mail has a network connection at the same time. I can't see what those URLs are pointing to, and it would be a lot better to post at least a summary in the e-mail.
Bug#198158: architecture i386 isn't i386 anymore
On Fri, Jun 20, 2003 at 03:28:02PM +0200, Adam Borowski wrote: > On Fri, 20 Jun 2003, Stephen Stafford wrote: > > On Fri, Jun 20, 2003 at 02:25:52PM +0200, Adam Borowski wrote: > > > What about perusing the INT 6 idea, and going all the way up to i686? > > While I support the removal of 386 support, I absolutely and strenuously > > object to going to 686. 686 isn't all that old at all (1997 IIRC), and I > > use a nunber of 4/586 machines still (I have one 486 which I use for > > embedded development and 3 P100 boxen which are used for various things like > > CVS server, gateway/firewall, testing various things). > Note that my idea was about patching the kernel that so the newer opcodes > would be emulated in software. Everything would still work even on a 386, > just slower -- and the speed decrease can be removed by running apt-build. I don't see how that suggestion can possibly be taken seriously. Very few i386 machines have the requisite disk space, memory, and swap space to build large applications in Debian today. -- John
mkdosfs patch to enable booting
This patch makes mkdosfs accept a new option "-B" that allows it to make a bootable partition. Requires that you give the filename of a file containing valid boot sector as an argument to -B. Will work if you give a bootable partition as argument. EG: mkdosfs -F 16 -B bootsect.fat16 /dev/sda1 mkdosfs -F 32 -B bootsect.fat32 /dev/sda1 or to keep current boot code... mkdosfs -F 32 -B /dev/sda1 /dev/sda1 NOTE: sent to redhat binutils list as it seemed to be the closest to the proper list. There seems to be no real maintainer for mkdosfs anymore... Sam dosfstools-2.8-bootcode.patch Description: Binary data smime.p7s Description: S/MIME cryptographic signature
Re: mkdosfs patch to enable booting
> NOTE: sent to redhat binutils list as it seemed to be the closest to > the proper list. There seems to be no real maintainer for mkdosfs > anymore... Sorry, binutils has nothing to do with mkdosfs.
