[OT] Re: sarge, aptitude, archives
jeremy bentham [EMAIL PROTECTED]: I can only plead that as a recent emigre from slackware land, I became dazzled by Debian's slick package-management system and began to expect it to read my mind. Have you looked at Zenwalk? It's a SW downstream, and its netpkg rivals apt for dazzle factor. Fits on a ca. 2 Gb disk, and they've a live version CD you can try. -- Any technology distinguishable from magic is insufficiently advanced. (*)http://blinkynet.net/comp/uip5.html Linux Counter #80292 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge, aptitude, archives
On Mon,17.Nov.08, 19:32:42, jeremy bentham wrote: My sources.list deb http://archive.debian.org/debian-archive/ sarge main contrib non-free per the README at the archive site. That README is wrong, since there is no debian-archive directory on archive.debian.org, only a debian directory. This has already been reported: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505754. So you just need to s/debian-archive/debian/ in your sources.list. Alas, that was the first thing I tried--well, s/archive.debian.org/http.us.deb.org/. Suppose I should have put that in my first post [-; . I think you misunderstood, the correct line would be deb http://archive.debian.org/debian/ sarge main contrib non-free Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: sarge, aptitude, archives
On Nov 19 you wrote: On Mon,17.Nov.08, 19:32:42, jeremy bentham wrote: My sources.list deb http://archive.debian.org/debian-archive/ sarge main contrib non-free per the README at the archive site. That README is wrong, since there is no debian-archive directory on archive.debian.org, only a debian directory. This has already been reported: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505754. So you just need to s/debian-archive/debian/ in your sources.list. Alas, that was the first thing I tried--well, s/archive.debian.org/http.us.deb.org/. Suppose I should have put that in my first post [-; . I think you misunderstood, the correct line would be deb http://archive.debian.org/debian/ sarge main contrib non-free I see I didn't put that very well; no matter. I got the line right. My problem was simply not understanding aptitude. After getting those error messages I merely needed to press return, then u, select become root, type root's password and watch the progress bar I can only plead that as a recent emigre from slackware land, I became dazzled by Debian's slick package-management system and began to expect it to read my mind. ;-} Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) -- Dave Williams [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge, aptitude, archives
jeremy bentham [EMAIL PROTECTED]:
Please, no {advice, orders} to upgrade to etch. Consider this a
question about aptitude/sources.list/archives.
Fine. Why would you expect Sarge to work anymore? Just curious.
--
Any technology distinguishable from magic is insufficiently advanced.
(*)http://blinkynet.net/comp/uip5.html Linux Counter #80292
- -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge, aptitude, archives
On 2008-11-17 23:44 +0100, jeremy bentham wrote: I can't use aptitude anymore. It was working, pre-sarge-archive. Typing aptitude on the command line gives me this: W: Couldn't stat source package list http://archive.debian.org sarge/main Packages (/var/lib/apt/lists/archive.debian.org_debian-archive_dists_sarge_ main_binary-i386_Packages) - stat (2 No such file or directory) W: Couldn't stat source package list http://archive.debian.org sarge/contrib Packages (/var/lib/apt/lists/archive.debian.org_debian-archive_dists_sarge _contrib_binary-i386_Packages) - stat (2 No such file or directory) W: Couldn't stat source package list http://archive.debian.org sarge/non-free Packages (/var/lib/apt/lists/archive.debian.org_debian-archive_dists_sarge _non-free_binary-i386_Packages) - stat (2 No such file or directory) (That's 3 _long_ lines; I broke them up for e-mail convenience.) My sources.list deb http://archive.debian.org/debian-archive/ sarge main contrib non-free per the README at the archive site. That README is wrong, since there is no debian-archive directory on archive.debian.org, only a debian directory. This has already been reported: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505754. So you just need to s/debian-archive/debian/ in your sources.list. Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge, aptitude, archives
On Nov 18 you wrote: On 2008-11-17 23:44 +0100, jeremy bentham wrote: I can't use aptitude anymore. It was working, pre-sarge-archive. Typing aptitude on the command line gives me this: W: Couldn't stat source package list http://archive.debian.org sarge/main Packages (/var/lib/apt/lists/archive.debian.org_debian-archive_dists_sarge_ main_binary-i386_Packages) - stat (2 No such file or directory) W: Couldn't stat source package list http://archive.debian.org sarge/contrib Packages (/var/lib/apt/lists/archive.debian.org_debian-archive_dists_sarge _contrib_binary-i386_Packages) - stat (2 No such file or directory) W: Couldn't stat source package list http://archive.debian.org sarge/non-free Packages (/var/lib/apt/lists/archive.debian.org_debian-archive_dists_sarge _non-free_binary-i386_Packages) - stat (2 No such file or directory) (That's 3 _long_ lines; I broke them up for e-mail convenience.) My sources.list deb http://archive.debian.org/debian-archive/ sarge main contrib non-free per the README at the archive site. That README is wrong, since there is no debian-archive directory on archive.debian.org, only a debian directory. This has already been reported: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505754. So you just need to s/debian-archive/debian/ in your sources.list. Alas, that was the first thing I tried--well, s/archive.debian.org/http.us.deb.org/. Suppose I should have put that in my first post [-; . -- Dave Williams [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge Repository Gone
s. keeling wrote: Nick Boyce [EMAIL PROTECTED]: Can anyone confirm for me that it should be okay for us to repoint sources.list to archive.d.o for a while, in order to apt-get anything we Why not just point it at a locally mounted DVD? Then, you'd be safe from a direct strike on a.d.o (though nothing else)? :-P Yep, could do that - I think we've got an ISO for Sarge somewhere I found a blog post by Joerg Jaspert [1] explaining that he began the removal of Sarge from the main repository on 26th.Oct.2008, and is transferring it to archive.d.o, and expects the process to take a few days. Actually I've been trying to use the new repository, just to see what happens. It's a bit unreliable so far : Yesterday: MYBOX:/etc/apt# apt-get update Get:1 http://archive.debian.org sarge/main Packages [4523kB] Hit http://security.debian.org sarge/updates/main Packages Hit http://security.debian.org sarge/updates/main Release Hit http://security.debian.org sarge/updates/contrib Packages Hit http://security.debian.org sarge/updates/contrib Release Hit http://de3.samba.org sarge/samba Packages Hit http://de3.samba.org sarge/samba Release Get:2 http://archive.debian.org sarge/main Release [98B] Get:3 http://archive.debian.org sarge/non-free Packages [76.6kB] Get:4 http://archive.debian.org sarge/non-free Release [102B] Fetched 4599kB in 44s (104kB/s) Reading Package Lists... Done But today: MYBOX:/etc/apt# apt-get update Err http://security.debian.org sarge/updates/main Packages 404 Not Found Err http://archive.debian.org sarge/main Packages 404 Not Found Ign http://security.debian.org sarge/updates/main Release Ign http://archive.debian.org sarge/main Release Err http://security.debian.org sarge/updates/contrib Packages 404 Not Found Err http://archive.debian.org sarge/non-free Packages 404 Not Found Ign http://security.debian.org sarge/updates/contrib Release Ign http://archive.debian.org sarge/non-free Release Hit http://de3.samba.org sarge/samba Packages Hit http://de3.samba.org sarge/samba Release Failed to fetch http://security.debian.org/dists/sarge/updates/main/binary-i386/Packages.gz 404 Not Found Failed to fetch http://security.debian.org/dists/sarge/updates/contrib/binary-i386/Packages.gz 404 Not Found Failed to fetch http://archive.debian.org/debian-archive/dists/sarge/main/binary-i386/Packages.gz 404 Not Found Failed to fetch http://archive.debian.org/debian-archive/dists/sarge/non-free/binary-i386/Packages.gz 404 Not Found Reading Package Lists... Done E: Some index files failed to download, they have been ignored, or old ones used instead. I've just stopped using apt-get to d.o sites for now. I'd rather not have to leave a DVD in the server's DVD-ROM drive, but it could be done. [1] http://blog.ganneff.de/blog/2008/10/26/archiving-sarge-aka-oldstable.html Cheers Nick Boyce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge Repository Gone
Nick Boyce [EMAIL PROTECTED]: On our last remaining Sarge box (I know, I know ..) my periodic [snip] Can anyone confirm for me that it should be okay for us to repoint sources.list to archive.d.o for a while, in order to apt-get anything we Why not just point it at a locally mounted DVD? Then, you'd be safe from a direct strike on a.d.o (though nothing else)? :-P man apt-cdrom. -- Any technology distinguishable from magic is insufficiently advanced. (*)http://blinkynet.net/comp/uip5.html Linux Counter #80292 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning..
On 07/09/2008 09:52 PM, John Elliot wrote: Hi, We have a couple of Sarge servers running bind9(9.2.4-1sarge3) that appear to be vulnerable to the DNS cache poisoning issue(Looks like port randomization was only introduced in bind9.3?) - As the servers cannot be upgraded at this time to etch, what is the recommended course of action? Backports and upgrade to 9.3? There is a version of bind 9.3.4 for Sarge in backports.org, but they don't publish changelogs, so you'll have to research yourself if this bug has been fixed in their version. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning..
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Elliot wrote: Hi, We have a couple of Sarge servers running bind9(9.2.4-1sarge3) that appear to be vulnerable to the DNS cache poisoning issue(Looks like port randomization was only introduced in bind9.3?) - As the servers cannot be upgraded at this time to etch, what is the recommended course of action? Backports and upgrade to 9.3? I remember that DSA gave one or two workarounds... - -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIddhEchorMMFUmYwRAl6RAKCrvnVNNEC9/2NR/zcdzoUKWQhGnACbBhK5 tITKgtMi0qPVGJRRWEcEgZI= =phkL -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge, Bind9 (9.2.4-1sarge3) and DNS cache poisoning..
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/09/08 21:52, John Elliot wrote: Hi, We have a couple of Sarge servers running bind9(9.2.4-1sarge3) that appear to be vulnerable to the DNS cache poisoning issue(Looks like port randomization was only introduced in bind9.3?) - As the servers cannot be upgraded at this time to etch, what is the recommended course of action? Backports and upgrade to 9.3? Upgrade to Vista? - -- Ron Johnson, Jr. Jefferson LA USA Kittens give Morbo gas. In lighter news, the city of New New York is doomed. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkh1enQACgkQS9HxQb37XmfL7wCfZrv4e5TP7j8NLPT9VYpEMUv1 zCIAoIH904Sc6cuNb3Km+YEYdYC/FWLS =HGqO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge EOL date
On Mon Feb 04, 2008 at 10:15:14 +0100, Henrik Johansen wrote: Security Support for Debian GNU/Linux 3.0 (Woody) was terminated one year after the release of Debian GNU/Linux 3.1 (Sarge). Is Sarge following the same EOL cycle or can one expect a longer period of Security Support ? It will be the same; security support ending in April 2008. Steve -- Debian GNU/Linux System Administration http://www.debian-administration.org/ pgpt6OjlH7CxA.pgp Description: PGP signature
Re: Sarge EOL date
Steve Kemp wrote: [...] Security Support for Debian GNU/Linux 3.0 (Woody) was terminated one year after the release of Debian GNU/Linux 3.1 (Sarge). Is Sarge following the same EOL cycle or can one expect a longer period of Security Support ? It will be the same; security support ending in April 2008. Thank you for clarifying that for me. Steve -- Debian GNU/Linux System Administration http://www.debian-administration.org/ -- Med venlig hilsen / Best Regards Henrik Johansen [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge EOL date
Kevin Mark wrote: [...] Security Support for Debian GNU/Linux 3.0 (Woody) was terminated one year after the release of Debian GNU/Linux 3.1 (Sarge). Is Sarge following the same EOL cycle or can one expect a longer period of Security Support ? It will be the same; security support ending in April 2008. Steve -- Do you have systems that need this support continued? If so, there are Debian consultants on www.debian.org. Do you have systems that can not use testing or a newer stable release? We have ~50 servers that still are running Sarge. All I needed was an official EOL date so that I could plan the transition to Etch and justify the use of extra manhours to upper management. -K [...] -- Med venlig hilsen / Best Regards Henrik Johansen [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge r7 CDs released
On Mon, Jan 21, 2008 at 08:12:11PM +0100, Jens Franik wrote: Guten Tag Mattias Wadenstein, am Sonntag, 20. Januar 2008 um 10:29 schriebst Du: http://cdimage.debian.org/cdimage/archive/3.1_r7/ They are now authorized on the tracker I put on my seeding this images: debian-31r7-i386-binary-1.iso debian-31r7-i386-binary-2.iso debian-31r7-i386-businesscard.iso debian-31r7-i386-netinst.iso debian-update-3.1r7-i386-DVD-1.iso But the only item, which has been downloaded until now is the Update-i386-DVD with 1,26 Mb - nothing more. I guess nobody really needs them :-) Yup. Oldstable point releases are like that. There tends to be rather more interest in new major stable releases, as you might imagine. :-) -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Is there anybody out there? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge r7 CDs released
Guten Tag Mattias Wadenstein, am Sonntag, 20. Januar 2008 um 10:29 schriebst Du: http://cdimage.debian.org/cdimage/archive/3.1_r7/ They are now authorized on the tracker I put on my seeding this images: debian-31r7-i386-binary-1.iso debian-31r7-i386-binary-2.iso debian-31r7-i386-businesscard.iso debian-31r7-i386-netinst.iso debian-update-3.1r7-i386-DVD-1.iso But the only item, which has been downloaded until now is the Update-i386-DVD with 1,26 Mb - nothing more. I guess nobody really needs them :-) -- Mit freundlichen Grüßen Jens Franik mailto:[EMAIL PROTECTED]
Re: Sarge r7 CDs released
On Sun, 20 Jan 2008, Adrian Levi wrote: On 19/01/2008, Steve McIntyre [EMAIL PROTECTED] wrote: After a couple of false starts, we finally have the CDs and DVDs built for the latest sarge (oldstable) point release, 3.1 r7. See http://cdimage.debian.org/cdimage/archive/3.1_r7/ On Azureus bittorrent I get the error: Error(The requested download is not authorised for use with this tracker). They are now authorized on the tracker, but I don't have the space to seed them. I only have space for the current release and the current weekly build. /Mattias Wadenstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge r7 CDs released
Guten Tag Mattias Wadenstein, am Sonntag, 20. Januar 2008 um 10:29 schriebst Du: Error(The requested download is not authorised for use with this tracker). They are now authorized on the tracker, but I don't have the space to seed them. I only have space for the current release and the current weekly build. confirmed, no more error. But what should we do, to push the files. I am not the Geek for Bittorent Seeding. I can seed the Images for a week, but not forever with ADSL 600 up/6000 down. -- Mit freundlichen Grüßen Jens Franik mailto:[EMAIL PROTECTED]
Re: Sarge r7 CDs released
Guten Tag Mattias Wadenstein, am Sonntag, 20. Januar 2008 um 10:29 schriebst Du: They are now authorized on the tracker, but I don't have the space to seed them. I put the Update-DVD on and after i have downloaded the other 2 DVD i will seed them for a while. Anyone who will do the same? -- Mit freundlichen Grüßen Jens Franik mailto:[EMAIL PROTECTED]
Re: Sarge r7 CDs released
On 19/01/2008, Steve McIntyre [EMAIL PROTECTED] wrote: After a couple of false starts, we finally have the CDs and DVDs built for the latest sarge (oldstable) point release, 3.1 r7. See http://cdimage.debian.org/cdimage/archive/3.1_r7/ On Azureus bittorrent I get the error: Error(The requested download is not authorised for use with this tracker). Adrian -- 24x7x365 != 24x7x52 Stupid or bad maths? erno hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge r7 CDs released
Guten Tag Adrian Levi, am Samstag, 19. Januar 2008 um 23:35 schriebst Du: After a couple of false starts, we finally have the CDs and DVDs built for the latest sarge (oldstable) point release, 3.1 r7. http://cdimage.debian.org/cdimage/archive/3.1_r7/ On Azureus bittorrent I get the error: Error(The requested download is not authorised for use with this tracker). Confirmed - same Error here. -- Mit freundlichen Grüßen Jens Franik mailto:[EMAIL PROTECTED]
Re: Sarge - Lenny
On Friday 21 December 2007, Sven Joachim wrote: ... Please try to find out where you got /usr/local/share/perl/5.8.8/Errno.pm from. Regards, Sven Can't answer for the OP but I've downloaded various perl modules from CPAN and now my /usr/local/share is no longer arch independent. I mount /usr/local via NFS and I've had to create 32 and 64bit /usr/local/share/perl libs. Its a bug as I understand share, but I don't know where to file it since its not debian package breakage. I know some perl modules are availabe as packages. Is there a debian way to use CPAN for the others? stevem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Lenny
On 2007-12-22 05:28 +0100, Cam wrote:
apt-get dist-upgrade normally works a treat, but having used it lately
to move from Etch to Lenny (after appropriate /etc/apt/sources.list
changes) I encountered this ugly situation:
Preparing to replace indent 2.2.9-7 (using .../indent_2.2.9-9_i386.deb) ...
Errno architecture (i486-linux-gnu-thread-multi-2.6.22-3-amd64) does
not match executable architecture
(i486-linux-gnu-thread-multi-2.6.22.10) at
/usr/local/share/perl/5.8.8/Errno.pm line 11.
^
The same problem appeared in the thread install-info/dpkg b0rked ?
yesterday, see my reply there. Where does this local Errno.pm come
from?
I'm presently working around this by commenting lines 11-13 in
/usr/local/share/perl/5.8.8/Errno.pm:
11 #$Config{'archname'}-$Config{'osvers'} eq
12 #i486-linux-gnu-thread-multi-2.6.22-3-amd64 or
13 # die Errno architecture
(i486-linux-gnu-thread-multi-2.6.22-3-amd64) does not match executable
architectur$
The Errno.pm that is included in Debian's perl-base package does not
include this check.
...and clearly this isn't a solution at all. I feel distinctly uneasy
with a workaround that out-uglies the original problem like this one.
Does anyone have any idea of what is actually going on here?
Please try to find out where you got
/usr/local/share/perl/5.8.8/Errno.pm from.
Regards,
Sven
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge et module pour Marvell 88E8053 Résolu - pas propre
Francois a écrit : Donc, je reprends: * sarge, 2.6.8-4-686, et 'carte intégrée' maxwell 88E8053. * lscpi (ça commence mal !): Ethernet controller: Marvell Technology Group Ltd.: Unknown device 4362 j'(ai trouvé une solution à base de code propriétaire : Sur le site de http://www.syskonnect.eu/ * téléchargement du tarball pour SK-9E21, le décompresser * vérifier que j'ai bien les headers pour mon noyo * vérifier que /usr/src/linux est bien un lien vers le bon répertoire * lancer install.sh et hop @+ -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge with 2.6.13 ISO?
Thanks, that worked! For a client I need to install Sarge on a server. This needs to be Sarge since their Live server is also running Sarge, and upgrading to Etch is not an option right now. One of Kenshi Muto's customized Sarge installer images might work: http://mirror.home-dn.net/d-i/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge Netinst !
On Thu, Sep 27, 2007 at 11:20:54AM +, Najem, Saifeddine wrote: How can I get Netinst for Debian Linux 3.1 sarge? Why do you want to install old-stable? Have you checked the debian-CD ftpsite? See the debian web page. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge Netinst !
On Thu, Sep 27, 2007 at 11:20:54AM +, Najem, Saifeddine wrote: Hi, How can I get Netinst for Debian Linux 3.1 sarge? Beside the question why to install sarge, of course you might have your reasons, I think I found the latest build for the latest point release here: ftp://cdimage.debian.org/cdimage/archive/3.1_r6a/i386/iso-cd/ Cheers, Sven -- I want to believe in a freedom that's bold But all I remember is the freedom of old [ Flogging Molly - Black Friday Rule ] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge with 2.6.13 ISO?
On Mon, Sep 24, 2007 at 16:46:47 +0200, Pim Bliek wrote: Dear List, For a client I need to install Sarge on a server. This needs to be Sarge since their Live server is also running Sarge, and upgrading to Etch is not an option right now. However, this new server has a new Intel chipset with an E1000 netwerk card (GB). I found out here that I need kernel 2.6.13 for that: http://www.well.com/~allyn/debian_d945.html That page also describes a lengthy process to build a Sarge system rather from a seperate disk or using another PCI network card. Since I do not have physical access that road is a no-go right now. I can only have the ISP drop in a CD for me, and they can burn them from ISO. Is there anyone aware of a ISO image with Sarge on 2.6.13 or newer kernels? Or any other creative ideas? I'm quickly running out of options here.. Any help more than greatly appreciated! One of Kenshi Muto's customized Sarge installer images might work: http://mirror.home-dn.net/d-i/ -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge-Etch Upgrade Minor Problems
Glennie Vignarajah [EMAIL PROTECTED]: Le Wednesday 08 August 2007, Aikins, Ronald (Ron) (CIV) disait: The default settings for vi have been changed. Display looks weird in terms of colors, etc. Can't figure what vi/vim file needs changing. I have backups of course of all pre-upgrade config files. I've tried using the old /etc/vim/vimrc, but no change. If you've installed vim 7, try to edit /etc/vim/vimrc and check if 'runtimepath' contains '/usr/share/vim/vim70'. If not, try add it. IIRC, I resolved a problem related by doing this.(On our machines, Another thing to check is which vim is installed. I believe the default in Etch is vim-tiny, in which a number of useful features are unavailable. -- Any technology distinguishable from magic is insufficiently advanced. (*)http://blinkynet.net/comp/uip5.html Linux Counter #80292 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge-Etch Upgrade Minor Problems
Le Wednesday 08 August 2007, Aikins, Ronald (Ron) (CIV) disait: The default settings for vi have been changed. Display looks weird in terms of colors, etc. Can't figure what vi/vim file needs changing. I have backups of course of all pre-upgrade config files. I've tried using the old /etc/vim/vimrc, but no change. If youv've installed vim 7, try to edit /etc/vim/vimrc and check if 'runtimepath' contains '/usr/share/vim/vim70'. If not, try add it. IIRC, I resolved a problem related by doing this.(On our machines, we've got runtimepath set to ~/.vim,/etc/vim,/usr/share/vim/vimfiles,/usr/share/vim/addons,/usr/share/vim/vim70,/usr/share/vim/vimfiles, /usr/share/vim/addons/after,~/.vim/after) HTH -- Glennie Vignarajah It's a rare person who wants to hear what he doesn't want to hear. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge: Lost # of failed logins
On 07/27/2007 05:55 PM, Andrew Sackville-West wrote: On Fri, Jul 27, 2007 at 02:53:54PM -0500, Mumia W.. wrote: [...] The faillog command doesn't give any output to me, and /var/log/faillog is still zero bytes. so, what mechanism writes the faillog. Maybe it panics on bad perms? mine are 0644 root:root A Same here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge: Lost # of failed logins
On Fri, Jul 27, 2007 at 20:14:02 -0500, Mumia W.. wrote: On 07/27/2007 05:55 PM, Andrew Sackville-West wrote: On Fri, Jul 27, 2007 at 02:53:54PM -0500, Mumia W.. wrote: [...] The faillog command doesn't give any output to me, and /var/log/faillog is still zero bytes. so, what mechanism writes the faillog. Maybe it panics on bad perms? mine are 0644 root:root A Same here. I can remove /var/log/faillog on my system (Sid-amd64) and create a new one with touch (empty file, permissions like yours). After the first failed login the file is 32KB long (the same length as it had before) and both the login failure messages and the faillog command work normally again. I would of course be very worried if the faillog file disappeared on its own all of a sudden. (Now that I have become aware of its existence in the course of this thread.) Likewise, it would be suspicious if the empty seed file remained unchanged after subsequent login failures. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge: Lost # of failed logins
On 07/27/2007 05:57 AM, Florian Kulzer wrote: On Thu, Jul 26, 2007 at 20:44:49 -0700, Andrew Sackville-West wrote: On Thu, Jul 26, 2007 at 05:52:00PM -0600, Bob Proulx wrote: Florian Kulzer wrote: I have been using Debian for about 5 years now. As far as I remember, it always had the n failure(s) since last login message (if n was greater than zero). I have never seen that message. it works reliably on this particular up-to-date sid box, shows the proper number of failures. I think it must come from login, but I can't see what might cause to happen or not. [...] I do _not_ get this message over ssh, so it must come from that pair -- login or getty... I think this is controlled in /etc/login.defs: # # Enable logging and display of /var/log/faillog login failure info. # This option conflicts with the pam_tally PAM module. # FAILLOG_ENAByes [...] Hmm. My /var/log/faillog was missing, but even when I 'touch' it, the behavior doesn't change. My FAILLOG_ENAB is also yes in /etc/login.defs. In my /etc/pam.d/login file, session optional pam_lastlog.so is enabled. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge: Lost # of failed logins
On 07/26/2007 10:44 PM, Andrew Sackville-West wrote: On Thu, Jul 26, 2007 at 05:52:00PM -0600, Bob Proulx wrote: Florian Kulzer wrote: I have been using Debian for about 5 years now. As far as I remember, it always had the n failure(s) since last login message (if n was greater than zero). I have never seen that message. it works reliably on this particular up-to-date sid box, shows the proper number of failures. I think it must come from login, but I can't see what might cause to happen or not. [...] And it works on my Etch box, but my main box is still this Sarge computer. Nothing in /etc/profile, ~/.bash_profile or ~/.bashrc seems to produce this message. Surely the message comes from the 'login' command, but I can't see what feature of login enables that. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge: Lost # of failed logins
On Fri, Jul 27, 2007 at 08:50:46 -0500, Mumia W.. wrote: [...] Hmm. My /var/log/faillog was missing, but even when I 'touch' it, the behavior doesn't change. My FAILLOG_ENAB is also yes in /etc/login.defs. Do you get the normal output when you run faillog? $ faillog Login Failures Maximum Latest On root00 07/09/07 09:44:25 +0200 tty1 florian 00 07/27/07 09:15:42 +0200 tty1 In my /etc/pam.d/login file, session optional pam_lastlog.so is enabled. I have the same entry. My impression is that this module is responsible for the Last login: $DATE on $TERMINAL output. The message n failure(s) since last login seems to triggered later, after pam_motd.so and pam_mail.so have done their job. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge: Lost # of failed logins
On Thu, Jul 26, 2007 at 20:44:49 -0700, Andrew Sackville-West wrote: On Thu, Jul 26, 2007 at 05:52:00PM -0600, Bob Proulx wrote: Florian Kulzer wrote: I have been using Debian for about 5 years now. As far as I remember, it always had the n failure(s) since last login message (if n was greater than zero). I have never seen that message. it works reliably on this particular up-to-date sid box, shows the proper number of failures. I think it must come from login, but I can't see what might cause to happen or not. [...] I do _not_ get this message over ssh, so it must come from that pair -- login or getty... I think this is controlled in /etc/login.defs: # # Enable logging and display of /var/log/faillog login failure info. # This option conflicts with the pam_tally PAM module. # FAILLOG_ENAByes I do have the pam_tally.so module in /lib/security/, but it seems that it is not used in my present (Debian-default) PAM configuration. Bob Proulx and I are currently doing a brute-force comparison of all our installed packages and relevant configuration files. We will see if this turns up additional clues. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge: Lost # of failed logins
On 07/27/2007 09:16 AM, Florian Kulzer wrote: On Fri, Jul 27, 2007 at 08:50:46 -0500, Mumia W.. wrote: [...] Hmm. My /var/log/faillog was missing, but even when I 'touch' it, the behavior doesn't change. My FAILLOG_ENAB is also yes in /etc/login.defs. Do you get the normal output when you run faillog? $ faillog Login Failures Maximum Latest On root00 07/09/07 09:44:25 +0200 tty1 florian 00 07/27/07 09:15:42 +0200 tty1 [...] The faillog command doesn't give any output to me, and /var/log/faillog is still zero bytes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge: Lost # of failed logins
On Fri, Jul 27, 2007 at 02:53:54PM -0500, Mumia W.. wrote: On 07/27/2007 09:16 AM, Florian Kulzer wrote: On Fri, Jul 27, 2007 at 08:50:46 -0500, Mumia W.. wrote: [...] Hmm. My /var/log/faillog was missing, but even when I 'touch' it, the behavior doesn't change. My FAILLOG_ENAB is also yes in /etc/login.defs. Do you get the normal output when you run faillog? $ faillog Login Failures Maximum Latest On root00 07/09/07 09:44:25 +0200 tty1 florian 00 07/27/07 09:15:42 +0200 tty1 [...] The faillog command doesn't give any output to me, and /var/log/faillog is still zero bytes. so, what mechanism writes the faillog. Maybe it panics on bad perms? mine are 0644 root:root A signature.asc Description: Digital signature
Re: Sarge: Lost # of failed logins
Mumia W.. wrote: I'm using Sarge. When I log in, I no longer get a message telling me the # of failed logins. For example, if I try to login but use a wrong password, when I try again using the real password, I should see a message saying 1 failed login attempts. I no longer get that message. I personally have never seen such a message. You must have previously installed or configured something that added that functionality. How do I get it back, and what could I have changed to make it go away in the first place? It sounds to me that this was a local configuration that you had created previously. Whatever you did before you would need to do again or debug. By the way... Sarge is now oldstable and the new stable is Etch. Consider upgrading. Eventually security upgrade support for Sarge will be dropped. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge: Lost # of failed logins
Florian Kulzer([EMAIL PROTECTED]) is reported to have said: On Thu, Jul 26, 2007 at 13:51:27 -0600, Bob Proulx wrote: Mumia W.. wrote: I'm using Sarge. When I log in, I no longer get a message telling me the # of failed logins. For example, if I try to login but use a wrong password, when I try again using the real password, I should see a message saying 1 failed login attempts. I no longer get that message. I personally have never seen such a message. You must have previously installed or configured something that added that functionality. I have been using Debian for about 5 years now. As far as I remember, it always had the n failure(s) since last login message (if n was greater than zero). I never had to do anything to set it up, therefore I unfortunately don't know exactly how it works. My best guess is that it involves some PAM modules which parse /var/log/faillog and/or use the faillog command. Maybe this link helps to track it down: http://linux.sys-con.com/read/49058.htm (search for faillog on that page) Florian I still have the results you 'had'. I tried logging in, twice, with a bad passwd. Got the following. Last login: Thu Jul 26 21:01:03 2007 on tty6 Linux dj 2.6.18-4-amd64 #1 SMP Fri May 4 00:37:33 UTC 2007 x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. No mail. 1 failure since last login. BUT I failed twice! Last was Thu 26 Jul 2007 09:06:23 PM EDT on tty5. I seems to be coming from something after the motd but before the .bash_profile and .bashrc. Running etch on a new system and just noticed I had not enabled the boot log, so can't check that right now. Sorry. Wayne -- There were computers in Biblical times. Eve had an Apple. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge: Lost # of failed logins
On Thu, Jul 26, 2007 at 13:51:27 -0600, Bob Proulx wrote: Mumia W.. wrote: I'm using Sarge. When I log in, I no longer get a message telling me the # of failed logins. For example, if I try to login but use a wrong password, when I try again using the real password, I should see a message saying 1 failed login attempts. I no longer get that message. I personally have never seen such a message. You must have previously installed or configured something that added that functionality. I have been using Debian for about 5 years now. As far as I remember, it always had the n failure(s) since last login message (if n was greater than zero). I never had to do anything to set it up, therefore I unfortunately don't know exactly how it works. My best guess is that it involves some PAM modules which parse /var/log/faillog and/or use the faillog command. Maybe this link helps to track it down: http://linux.sys-con.com/read/49058.htm (search for faillog on that page) -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge: Lost # of failed logins
Florian Kulzer wrote: I have been using Debian for about 5 years now. As far as I remember, it always had the n failure(s) since last login message (if n was greater than zero). I have never seen that message. I never had to do anything to set it up, therefore I unfortunately don't know exactly how it works. My best guess is that it involves some PAM modules which parse /var/log/faillog and/or use the faillog command. Maybe this link helps to track it down: I always have a ~/.hushlogin. When I remove it I still never see failures. I see this instead: Last login: Thu Jul 26 17:32:14 2007 from dementia.proulx.com If you create a .hushlogin file for you does your login failure message at login go away? touch ~/.hushlogin The sshd uses the presence of .hushlogin to silence the banner. In the sshd man page: 1. If the login is on a tty, and no command has been specified, prints last login time and /etc/motd (unless prevented in the configuration file or by $HOME/.hushlogin; see the FILES section). But I never see anything about failures, just the motd and the last login time. So I don't think this is it. I am very curious as to what outputs for you the faillog! Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge: Lost # of failed logins
On Thu, Jul 26, 2007 at 05:52:00PM -0600, Bob Proulx wrote: Florian Kulzer wrote: I have been using Debian for about 5 years now. As far as I remember, it always had the n failure(s) since last login message (if n was greater than zero). I have never seen that message. it works reliably on this particular up-to-date sid box, shows the proper number of failures. I think it must come from login, but I can't see what might cause to happen or not. I never had to do anything to set it up, therefore I unfortunately don't know exactly how it works. My best guess is that it involves some PAM modules which parse /var/log/faillog and/or use the faillog command. Maybe this link helps to track it down: I always have a ~/.hushlogin. When I remove it I still never see failures. I see this instead: Last login: Thu Jul 26 17:32:14 2007 from dementia.proulx.com If you create a .hushlogin file for you does your login failure message at login go away? touch ~/.hushlogin I see _nothing_ with a ~/.hushlogin and everything: motd, Last login, failures etc, without ~/.hushlogin The sshd uses the presence of .hushlogin to silence the banner. In the sshd man page: 1. If the login is on a tty, and no command has been specified, prints last login time and /etc/motd (unless prevented in the configuration file or by $HOME/.hushlogin; see the FILES section). I do _not_ get this message over ssh, so it must come from that pair -- login or getty... A signature.asc Description: Digital signature
Re: Sarge install image (kernel 2.4)
On Wed July 4 2007 01:28, Gudjon I. Gudjonsson wrote: Hi Could anyone please point out where to find Sarge install images? I only had a quick look but I couldn't find any sarge install images. They must exist somewhere but I'm not sure where. I tried to install it with debootstrap but I can only make it boot on kernel 2.6.8. When I try to boot on kernel 2.4 it shows the message /sbin/init 432: cannot open dev/console I did not find any helpful recommendations on the internet but I hope the install disk works. Are you installing the amd64 version of sarge by chance? It requires the 2.6 kernel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge install image (kernel 2.4)
Gudjon I. Gudjonsson wrote: Hi Could anyone please point out where to find Sarge install images? I tried to install it with debootstrap but I can only make it boot on kernel 2.6.8. When I try to boot on kernel 2.4 it shows the message /sbin/init 432: cannot open dev/console I did not find any helpful recommendations on the internet but I hope the install disk works. Thanks Gudjon http://cdimage.debian.org/cdimage/archive/3.1_r6a/i386/iso-cd/ this could be where you are looking for. s. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge
On Thu, 21 Jun 2007, Tadeusz Prokocki wrote: Co mozna zrobic jesli uparlbym sie zeby instalowac sarge zawsze mozna z plytek, ale czy ktos zna sources.list by ciagnac z sieci np: deb http://ftp.task.gda.pl/debian oldstable main contrib powinno zadziałać. Pozdrawiam, Marek -- Wszystkiego jest mało, niczego jest w bród (Raz, Dwa, Trzy)
Re: Sarge - Etch = udev problems
On Fri, Jun 08, 2007 at 10:58:53PM -0500, Jacob S wrote: My latest problem is on a Thinkpad that I upgraded from Sarge to Etch. The upgrade installed a 2.6.18-*-486 kernel and udev, which I changed to a 2.6.18-*-686 kernel (and udev). Now whenever I boot the laptop it has a ton of permission problems in /dev. For starters, /dev/random, /dev/urandom, /dev/tty* /dev/null have permissions of 660 while being owned by root:root, which effectively restricts logins to root only. I edited /etc/udev/rules.d/020_permissions.rules to do different permissions and/or group ownerships, but it seems to be ignoring the rules. /var/log/syslog does not show any udev errors at boot time, either. It also broke my wireless connection, but I can not yet determine if that is udev related or not (not real sure how it could be, though). Welcome home :) Someone will probably have a solution. However, I found that in the end, especially for multiple boxes, that it was easier to just reinstall Etch. You may want to set up an apt-proxy on one box (an existing sarge?) first; the box that connects to the internet. Then each install can look to this box for the packages. After the first box, the packages will be in the proxy and you won't have to repeatedly download packages. I found that an Etch install took me about 20 minutes which is why it was easier than tracking down the problems. I know, with Debian, you're not supposed to need to. However, Sarge to Etch moved hotplug to udev, XFree86 to Xorg, UTF-8 by default, and a slew of pesky details. YMMV. Good luck. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Etch = udev problems
On Fri, Jun 08, 2007 at 22:58:53 -0500, Jacob S wrote: Howdy List, This being gone at school for 5 months and then trying to fix 6 computers when I get home all at the same time is getting old. :-) My latest problem is on a Thinkpad that I upgraded from Sarge to Etch. The upgrade installed a 2.6.18-*-486 kernel and udev, which I changed to a 2.6.18-*-686 kernel (and udev). Now whenever I boot the laptop it has a ton of permission problems in /dev. For starters, /dev/random, /dev/urandom, /dev/tty* /dev/null have permissions of 660 while being owned by root:root, which effectively restricts logins to root only. I edited /etc/udev/rules.d/020_permissions.rules to do different permissions and/or group ownerships, but it seems to be ignoring the rules. /var/log/syslog does not show any udev errors at boot time, either. Did you purge the hotplug package after the upgrade? You can check with dpkg -l hotplug | tail -n1. It should show pn (and not rc) as the first two characters. It also broke my wireless connection, but I can not yet determine if that is udev related or not (not real sure how it could be, though). I have tried Googling the problem as well as looking through the udev bugs on bugs.d.o, all to no avail. Does anyone have any thoughts or hints on what might be causing this udev problem? Let me know if you need any additional info or logfiles. TIA, Jacob -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge-Etch: which obsolete packages can be removed?
On Wed, 23 May 2007 22:02:46 +1000 Robert S [EMAIL PROTECTED] wrote: I've had a debian machine running for a number of years and I've upgraded from woody-sarge-etch. Looking at the listing in aptitude there are a lot of obsolete packages - such as gcc-2.95, gcc-3.0, python-2.1, ipchains, libdb2, libnewt0, libreadline3, slang1. I assume its safe to remove old versions of gcc and ipchains. What about the other ones? Am I likely to break things by removing ALL of these packages? Could it wreck locally compiled packages (of which there are not many)? It could indeed wreck locally compiled packages, because aptitude has no idea of the requirements of those packages. Have you considered recompiling them? -- Liam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge-Etch: which obsolete packages can be removed?
It could indeed wreck locally compiled packages, because aptitude has no idea of the requirements of those packages. Have you considered recompiling them? Yes - when I get back from my trip overseas and am able to fix up any damage! I assume that packages that are part of etch won't be affected?? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge-Etch: which obsolete packages can be removed?
On Wed, 23 May 2007 23:04:45 +1000 Robert S [EMAIL PROTECTED] wrote: It could indeed wreck locally compiled packages, because aptitude has no idea of the requirements of those packages. Have you considered recompiling them? Yes - when I get back from my trip overseas and am able to fix up any damage! I assume that packages that are part of etch won't be affected?? Won't be affected by what? The recompilation? -- Liam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge-Etch: which obsolete packages can be removed?
Yes - when I get back from my trip overseas and am able to fix up any damage! I assume that packages that are part of etch won't be affected?? Won't be affected by what? The recompilation? No - by purging the obsolete packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge-Etch: which obsolete packages can be removed?
On Thu, 24 May 2007 07:07:50 +1000 Robert S [EMAIL PROTECTED] wrote: Yes - when I get back from my trip overseas and am able to fix up any damage! I assume that packages that are part of etch won't be affected?? Won't be affected by what? The recompilation? No - by purging the obsolete packages. Correct. Etch is self-contained. None of the packages in etch depends on obsolete packages. -- Liam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ¿Sarge viene con los sources apuntanto a stable o a sarge?
El 1/05/07, Luis Rodrigo Gallardo Cruz [EMAIL PROTECTED] escribió: On Tue, May 01, 2007 at 01:56:37AM +0200, Iñaki Baz Castillo wrote: El problema era que los sources apuntaban a stable y no a sarge por lo que tras el update he instalado el vim de Etch junto con otras dependencias importantes. Que el kernel se haya desinstalado sin más y SIN INSTALARSE UNO NUEVO me ha sorprendido bastante, no doy crédito. ¿Cómo es posible en Debian? ¿alguien se lo explica? No, y es muy raro. No sólo sigue existiendo un paquete 'dummy' kernel-image-2.6 que se encarga del cambio de nombre, yo he practicado esa actualización y no me ha pasado nada parecido. ¿Has visto en el log de aptitude a ver si algo ahí te da una pista? No, ya miraré. Pero claro, si han usado apt-get no queda reflejado en ningún, es una de las cosas que me gusta de aptitude.
Re: ¿Sarge viene con los sources apuntanto a stable o a sarge?
El Lunes 30 Abril 2007 16:56, Iñaki Baz Castillo escribió: Hola, hoy casi la lío parda. Tenía que preparar un servidor remotamente, de esos que están alojados en un datacenter y que vienen con un Linux preinstalado. Se trataba de una Debian Sarge y lo primero que he hecho (por pura rutina) ha sido: # aptitude update # aptitude install vim y le he dado al intro sin mirar, ¿qué podía pasar? Pues bien, se ha desinstalado el Kernel 2.8.6 de Sarge y en su lugar se ha instalado ¡ninguno! Por suerte me he dado cuenta y no he borrado los módulos o tal vez habría perdido el control del sistema y adiós muy buenas. El problema era que los sources apuntaban a stable y no a sarge por lo que tras el update he instalado el vim de Etch junto con otras dependencias importantes. Que el kernel se haya desinstalado sin más y SIN INSTALARSE UNO NUEVO me ha sorprendido bastante, no doy crédito. ¿Cómo es posible en Debian? ¿alguien se lo explica? Por todo ello me gustaría saber si alguien puede confirmar si una Debian Sarge te coloca los sources apuntando a stable o a sarge. Miedo me da que sea a stable por la experiencia que he tenido hoy. Saludos. PD: También cabe la posibilidad de que los proveedores del servidor lo metan mano antes de entregarlo y hayan jugado con los sources y cometido el error. En cualquier caso entiendo que si Sarge viene con los sources apuntado a stable la situación es delicada. Hola Inaki A mi me ocurrio algo parecido con una Sarge testing actualizada a Sarge estable; en la ultima actualizacion mantuvo en los sources.lst, stable y casi actualizo muchos paquetes mas, pero no me sustituia el kernel, solo lo eliminaba! Yo creo que me perdi la actualizacion para cambiar los sources.lst
Re: Sarge Update Problem
Hello Brandon B ([EMAIL PROTECTED]) wrote: Hopefully someone can help here... I'm on an R50e Thinkpad with Sarge installed. I ran an upgrade (note: upgrade not dist-upgrade). Something strange happened. The file /etc/debian-release states 4.0 now. In my /etc/apt/apt.conf I had the following entry: APT::Default-Release sarge; As far as I know you cannot pin to codenames. Run apt-cache policy libc6 If your setting works, the version from sarge has a priority of 990. If it is 500, your setting was ignored because it is invalid, and you partially upgraded to etch. In that case, read the Etch release notes to complete your upgrade, or reinstall Sarge. [...] The following packages have unmet dependencies: xlibmesa-glu: Depends: xfree86-common but it is not installable Conflicts: libglu1 which is a virtual package. libglu1-mesa: Conflicts: libglu1 which is a virtual package. ** The Etch release notes have some info on this problem. regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 ICQ #17079270 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps-sarge.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge packages have disappeared
Nigel Henry wrote: I appreciate that Christian. Stable is now asigned to Etch. But do we have access to the Sarge repo, before Etch became stable? I think this equates as old-stable now. it would be a shame to think that all these packages for Sarge were now in the trash, and no longer available. it's 'oldstable' btw. using 'oldstable' or 'sarge' should help you. And btw - I don't use keywords 'stable' and 'testing' for some time - when I notice new release, I will start upgrading my machines one by one... On 15.04.07 15:53, Matthew K Poer wrote: If sarge is now old-stable (and I think it is), how would we access Woody packages? woody was archived about a year ago. It's not on public mirrors since, only if they mirror debian-archive. -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Microsoft dick is soft to do no harm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge packages have disappeared
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Nigel Henry escribió: On Sunday 15 April 2007 20:53, you wrote: nigel henry [EMAIL PROTECTED] writes: What's happened to the repo for Sarge Christian. Folks are getting 404's when trying to access it? Sarge the stable distribution is now called etch. Christian I appreciate that Christian. Stable is now asigned to Etch. But do we have access to the Sarge repo, before Etch became stable? I think this equates as old-stable now. it would be a shame to think that all these packages for Sarge were now in the trash, and no longer available. If you use in your `/etc/apt/sources.list' _sarge_ then you will be using sarge packages... They're still present and will be archived only once lenny get released as stable. Regards, Jose Luis. - -- ghostbar on Linux/Debian 'sid' i686 - #382503 Weblog: http://ghostbar.ath.cx/ - http://talug.org.ve http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGJhgsOKCtW8rKsRgRCupjAJ0UHqf36/8ftVgo7ZwyeiIldV6K6QCcCW7h CeIjS/fSxSJMrdc/3zuNFuo= =1CoL -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge packages have disappeared
On Wed, 2007-04-18 at 09:07 -0400, Jose Luis Rivas Contreras wrote: Nigel Henry escribió: On Sunday 15 April 2007 20:53, you wrote: nigel henry [EMAIL PROTECTED] writes: What's happened to the repo for Sarge Christian. Folks are getting 404's when trying to access it? Sarge the stable distribution is now called etch. Christian I appreciate that Christian. Stable is now asigned to Etch. But do we have access to the Sarge repo, before Etch became stable? I think this equates as old-stable now. it would be a shame to think that all these packages for Sarge were now in the trash, and no longer available. If you use in your `/etc/apt/sources.list' _sarge_ then you will be using sarge packages... They're still present and will be archived only once lenny get released as stable. This pertaining to Debian-Multimedia.org which is Christian Marrialat's stuff. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup signature.asc Description: This is a digitally signed message part
Re: Sarge-Etch upgrade breaks cupsys network printing
No replies? Clear as mud? Let me rephrase my question! :) My 2 computer network running sarge on both boxes printed fine until I upgraded one box to etch. Now only local printing works. Box A runs sarge. Box B with an HP5L printer runs etch. Box A config files are unchanged. Box B has new etch cupsd.conf, but trying the old sarge cupsd.conf did not work either. So Box B (etch) prints locally, but doesn't print jobs from Box A. Box A sees the printers on Box B: Box A: $ lpstat -a cups-PDF accepting requests since Jan 01 00:00 [EMAIL PROTECTED] accepting requests since Jan 01 00:00 HP5L accepting requests since Jan 01 00:00 Box A shows print jobs dispatched, but shows errors. This was a one page text file printed from firefox. Box A /var/log/cups/error_log: I [17/Apr/2007:09:57:18 -0400] Job 1 queued on 'HP5L' by 'jacki'. I [17/Apr/2007:09:57:18 -0400] Started backend /usr/lib/cups/backend/ipp (PID 3679) for job 1. I [17/Apr/2007:09:57:19 -0400] Job 2 queued on 'HP5L' by 'jacki'. I [17/Apr/2007:09:57:19 -0400] Started backend /usr/lib/cups/backend/ipp (PID 3680) for job 2. I [17/Apr/2007:09:57:19 -0400] Job 3 queued on 'HP5L' by 'jacki'. I [17/Apr/2007:09:57:19 -0400] Started backend /usr/lib/cups/backend/ipp (PID 3681) for job 3. N [17/Apr/2007:09:57:19 -0400] [Job 1] : Print file accepted - job ID 2. I [17/Apr/2007:09:57:19 -0400] Job 4 queued on 'HP5L' by 'jacki'. I [17/Apr/2007:09:57:19 -0400] Started backend /usr/lib/cups/backend/ipp (PID 3682) for job 4. N [17/Apr/2007:09:57:19 -0400] [Job 2] : Print file accepted - job ID 3. [...] cupsys spews jobs and has to be killed. Box A: /var/cups/page_log: HP5L jacki 1 [17/Apr/2007:09:57:19 -0400] 1 1 - localhost HP5L jacki 1 [17/Apr/2007:09:57:19 -0400] total 0 - localhost HP5L jacki 2 [17/Apr/2007:09:57:19 -0400] 1 1 - localhost HP5L jacki 2 [17/Apr/2007:09:57:19 -0400] total 0 - localhost HP5L jacki 3 [17/Apr/2007:09:57:19 -0400] 1 1 - localhost HP5L jacki 3 [17/Apr/2007:09:57:19 -0400] total 0 - localhost HP5L jacki 4 [17/Apr/2007:09:57:19 -0400] 1 1 - localhost HP5L jacki 4 [17/Apr/2007:09:57:19 -0400] total 0 - localhost Box B /var/log/cups/* has no entries for this time period. Box B: ~$ awk '!/^#/NF0' /etc/cups/cupsd.conf LogLevel info SystemGroup lpadmin Listen localhost:631 Listen /var/run/cups/cups.sock Browsing On BrowseOrder allow,deny BrowseAllow 192.168.1.103 BrowseAllow @LOCAL BrowseAddress 192.168.1.103 DefaultAuthType Basic Location / Order allow,deny Allow localhost Allow 192.168.1.103 /Location Location /admin Encryption Required Order allow,deny Allow localhost /Location Location /admin/conf AuthType Basic Require user @SYSTEM Order allow,deny Allow localhost /Location Policy default # Job-related operations must be done by the owner or an adminstrator... Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job Require user @OWNER @SYSTEM Order deny,allow /Limit # All administration operations require an adminstrator to authenticate... Limit Pause-Printer Resume-Printer Set-Printer-Attributes Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default AuthType Basic Require user @SYSTEM Order deny,allow /Limit # Only the owner or an administrator can cancel or authenticate a job... Limit Cancel-Job CUPS-Authenticate-Job Require user @OWNER @SYSTEM Order deny,allow /Limit Limit All Order deny,allow /Limit /Policy Printcap /var/run/cups/printcap Box A: $ awk '!/^#/NF0' /etc/cups/cupsd.conf DefaultCharset notused LogLevel info Printcap /var/run/cups/printcap Port 631 BrowseAddress 192.168.1.104 Location / Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From 192.168.1.104 /Location Location /jobs AuthType Basic AuthClass User /Location Location /admin AuthType Basic AuthClass System Order Deny,Allow Deny From All Allow From 127.0.0.1 /Location I'd appreciate any pointers, suggestions, or admonitions. The man pages, cups docs local and online, searching the net, all did not help. I'm sure I'm missing something really obvious. Thanks! Ralph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge-Etch upgrade breaks cupsys network printing
lame attempt to help below... On Tue, Apr 17, 2007 at 12:45:13PM -0400, Ralph Katz wrote: No replies? Clear as mud? Let me rephrase my question! :) My 2 computer network running sarge on both boxes printed fine until I upgraded one box to etch. Now only local printing works. Box A runs sarge. Box B with an HP5L printer runs etch. Box A config files are unchanged. Box B has new etch cupsd.conf, but trying the old sarge cupsd.conf did not work either. So Box B (etch) prints locally, but doesn't print jobs from Box A. [...] Box B: ~$ awk '!/^#/NF0' /etc/cups/cupsd.conf LogLevel info SystemGroup lpadmin Listen localhost:631 don't you need to listen to more than localhost?? hth A signature.asc Description: Digital signature
Re: Sarge-Etch upgrade breaks cupsys network printing
On Tue, 2007-04-17 at 12:45 -0400, Ralph Katz wrote: No replies? Clear as mud? Let me rephrase my question! :) Make sure these check boxes are checked in the admin interface at http://localhost:631/admin/ Share published printers connected to this system Allow remote administration Allow users to cancel any job (not just their own) Then wait for cups to reload the conf. in a few minutes the other machine will notice the proper url fo the printer and it will be able to work. Notice, something changed between Sarge and Etch as far as URLs for the printers. The Auto config stuff works better than forcing it. The only thing is you need to have your machine that has the real printer... make sure you define everything for it. To give you an example, my Epson RX600 was auto-setup properly by my Etch machine and my sid machine picked it up right away, as soon as I told my Etch machine to share ... -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup signature.asc Description: This is a digitally signed message part
Re: Sarge-Etch upgrade breaks cupsys network printing - RESOLVED
On 04/17/2007 03:08 PM, Greg Folkert wrote: On Tue, 2007-04-17 at 12:45 -0400, Ralph Katz wrote: No replies? Clear as mud? Let me rephrase my question! :) Make sure these check boxes are checked in the admin interface at http://localhost:631/admin/ Share published printers connected to this system Allow remote administration Allow users to cancel any job (not just their own) Then wait for cups to reload the conf. in a few minutes the other machine will notice the proper url fo the printer and it will be able to work. Notice, something changed between Sarge and Etch as far as URLs for the printers. The Auto config stuff works better than forcing it. The only thing is you need to have your machine that has the real printer... make sure you define everything for it. To give you an example, my Epson RX600 was auto-setup properly by my Etch machine and my sid machine picked it up right away, as soon as I told my Etch machine to share ... Works! Thank you, Greg. I didn't trust the web i/f, that was the obvious thing I missed. Regards, Ralph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge-Etch upgrade breaks cupsys network printing - RESOLVED
On Tue, 2007-04-17 at 16:30 -0400, Ralph Katz wrote: On 04/17/2007 03:08 PM, Greg Folkert wrote: On Tue, 2007-04-17 at 12:45 -0400, Ralph Katz wrote: No replies? Clear as mud? Let me rephrase my question! :) Make sure these check boxes are checked in the admin interface at http://localhost:631/admin/ Share published printers connected to this system Allow remote administration Allow users to cancel any job (not just their own) Then wait for cups to reload the conf. in a few minutes the other machine will notice the proper url fo the printer and it will be able to work. Notice, something changed between Sarge and Etch as far as URLs for the printers. The Auto config stuff works better than forcing it. The only thing is you need to have your machine that has the real printer... make sure you define everything for it. To give you an example, my Epson RX600 was auto-setup properly by my Etch machine and my sid machine picked it up right away, as soon as I told my Etch machine to share ... Works! Thank you, Greg. I didn't trust the web i/f, that was the obvious thing I missed. Cool, now if everyone would just trust that web interface. Yes it used to be teh sukc. Now though, it is nice and easy. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup signature.asc Description: This is a digitally signed message part
Re: Sarge packages have disappeared
On Sunday 15 April 2007 20:53, you wrote: nigel henry [EMAIL PROTECTED] writes: What's happened to the repo for Sarge Christian. Folks are getting 404's when trying to access it? Sarge the stable distribution is now called etch. Christian I appreciate that Christian. Stable is now asigned to Etch. But do we have access to the Sarge repo, before Etch became stable? I think this equates as old-stable now. it would be a shame to think that all these packages for Sarge were now in the trash, and no longer available. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge packages have disappeared
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nigel Henry wrote: On Sunday 15 April 2007 20:53, you wrote: nigel henry [EMAIL PROTECTED] writes: What's happened to the repo for Sarge Christian. Folks are getting 404's when trying to access it? Sarge the stable distribution is now called etch. Christian I appreciate that Christian. Stable is now asigned to Etch. But do we have access to the Sarge repo, before Etch became stable? I think this equates as old-stable now. it would be a shame to think that all these packages for Sarge were now in the trash, and no longer available. Nigel. If sarge is now old-stable (and I think it is), how would we access Woody packages? Not that I can think of a particularly good reason to want Woody packages... - -- Please do not use HTML mail for fully-textual messages. Matthew K Poer [EMAIL PROTECTED] Location: GA, USA Web: http://matthewpoer.freehostia.com GnuPG Public Key: 4DD0A9A6 Keyserver: subkeys.pgp.net Thinkpad 600: Debian Sarge Sony VAIO PCV-RS 520: Debian Etch -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGIoK2kRdiiE3QqaYRAluqAJ9Ox2/aKDCiKlEXRCijzQH+68iPfwCcCiPo WeojWkt5TsO4We8dTZHpOzo= =p+ak -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fwd: Re: Sarge packages have disappeared
-- Forwarded Message -- Subject: Re: Sarge packages have disappeared Date: Sunday 15 April 2007 21:50 From: Christian Marillat [EMAIL PROTECTED] To: Nigel Henry [EMAIL PROTECTED] Nigel Henry [EMAIL PROTECTED] writes: On Sunday 15 April 2007 20:53, you wrote: nigel henry [EMAIL PROTECTED] writes: What's happened to the repo for Sarge Christian. Folks are getting 404's when trying to access it? Sarge the stable distribution is now called etch. Christian I appreciate that Christian. Stable is now asigned to Etch. But do we have access to the Sarge repo, before Etch became stable? I think this equates as old-stable now. it would be a shame to think that all these packages for Sarge were now in the trash, and no longer available. Too late. Users should ask before the stable release (even if asked months before) to have an old-stable repository. Christian --- This is a bit sad. Christian has trashed all the available multimedia packages for Sarge since Etch has gone stable. In effect. if we want multimedia packages we are being forced to upgrade to, at least Etch. I have 1 Sarge, and 2 Etch installs. One of my Etch installs I'm soon going to put back on testing to see how lenny goes, but don't understand why packages that were available for Sarge from Christian Marillat's repo are now no longer available!!. Sometimes I wonder if I'm wasting my time working with computers. It might just be better taking my dog for a walk. Throwing a stick for him to fetch, and seeing him bringing it back to you. There's certainly more peace of mind when playing with a dog, than trying to resolve problems with the infernal machine. Apologies. Perhaps I'm just a bit T'd off at the mo. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge packages have disappeared
On Sun, 2007-04-15 at 15:53 -0400, Matthew K Poer wrote: If sarge is now old-stable (and I think it is), how would we access Woody packages? Here, http://archive.debian.org/ -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
Re: Fwd: Re: Sarge packages have disappeared
On Sun, 15 Apr 2007 22:21:12 +0200 Nigel Henry [EMAIL PROTECTED] wrote: This is a bit sad. Christian has trashed all the available multimedia packages for Sarge since Etch has gone stable. In effect. if we want multimedia packages we are being forced to upgrade to, at least Etch. I have 1 Sarge, and 2 Etch installs. One of my Etch installs I'm soon going to put back on testing to see how lenny goes, but don't understand why packages that were available for Sarge from Christian Marillat's repo are now no longer available!!. I think that's sad too. I'm waiting for a couple of weeks while the dust settles before upragding to etch. In the meantime I'm getting errors because I can't get an acroread upgrade for Sarge. -- Raquel Men are disturbed not by things, but by the view which they take of them. --Epictetus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fwd: Re: Sarge packages have disappeared
--- Raquel [EMAIL PROTECTED] wrote: On Sun, 15 Apr 2007 22:21:12 +0200 Nigel Henry [EMAIL PROTECTED] wrote: This is a bit sad. Christian has trashed all the available multimedia packages for Sarge since Etch has gone stable. Christian, Since Sarge will be supported by debian until it is moved to archive status (probably in about a year), do you think you could put the sarge packages back? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Automating Upgrades (was Re: Sarge - Etch: A Painful Upgrade)
On 04/13/2007 03:00 PM, Glen Pfeiffer wrote: On 04/13/2007 10:50 AM, Ralph Katz wrote: See the bug (latest messages), http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418911 turns out I missed one key step that has trapped others, too. Has it been considered that we could automate the recommended steps to upgrade? That would certainly help users avoid some of these gotcha's. How about a package just for the upgrade? I realize that maybe not all steps can be fully automated, but I think that can be handled gracefully. I am fairly new to Debian, but not averse to contributing. If this is something the team would like to have, I would consider doing it (with help). Glen, absolutely! Go for it, you have my vote. Now that you mention it, seems obvious this should be automated. Wish I had one! Regards, Ralph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Etch: A Painful Upgrade
On Thursday, 12.04.2007 at 18:30 -0400, Ralph Katz wrote: - aptitude update (etch sources) - aptitude upgrade - see lots of warnings This was your first sign of trouble. And, given that you were not fully committed to an upgrade at that point, it would probably have been better if you'd stopped there - and reported the errors/warnings you saw. In retrospect, absolutely! Given that you had trouble after what is a very simple operation, something fundamental must be wrong. Perhaps your previous downgrade from Sid to Sarge wasn't quite right, even though your system appeared to be operating fine. Not a chance. This machine had a fresh install of sarge last May (long after the sid/sarge downgrade) and was up-to-date as of the day of upgrade. Oh, OK, fair enough: your original post didn't make that clear. You said you stayed with Sarge, which suggested no reinstall. Any subsequent problems may well be as a result of that first problem. Are you *certain* your /etc/apt/sources.list were correct? What were the *actual* warnings (where you state lots of warnings)? Too late now to remember it all clearly, unless there's evidence in the logs. Many of the warnings are captured in the logs if you check the bug report #418911, I even cat /etc/apt/sources.list at one point in the capture. I posted 6 mbs of logs in the bug. What I was getting at, really, was that something hugely fundamental must have caused your error at that first stage. There's not enough information to figure out what: it *could* have been bad sources, it *could* have been lack of disk space, it *could* have been ... etc. etc. Without inspecting those first errors it's impossible to say. My post was more of a warning, 'heads-up, this may not be as easy as you think.' I hope to save others some aggravation and help the developers see how a user can flub it. Yeah, I realise that was your purpose ... :-) Dave. -- Please don't CC me on list messages! ... Dave Ewart - [EMAIL PROTECTED] - jabber: [EMAIL PROTECTED] All email from me is now digitally signed, key from http://www.sungate.co.uk/ Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92 signature.asc Description: Digital signature
Re: Sarge - Etch: A Painful Upgrade
On 04/13/2007, Dave Ewart wrote: What I was getting at, really, was that something hugely fundamental must have caused your error at that first stage. There's not enough See the bug (latest messages), http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418911 turns out I missed one key step that has trapped others, too. information to figure out what: it *could* have been bad sources, it *could* have been lack of disk space, it *could* have been ... etc. etc. Without inspecting those first errors it's impossible to say. My post was more of a warning, 'heads-up, this may not be as easy as you think.' I hope to save others some aggravation and help the developers see how a user can flub it. Yeah, I realise that was your purpose ... :-) Appreciate your comments, Dave. Re -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Automating Upgrades (was Re: Sarge - Etch: A Painful Upgrade)
On 04/13/2007 10:50 AM, Ralph Katz wrote: See the bug (latest messages), http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418911 turns out I missed one key step that has trapped others, too. Has it been considered that we could automate the recommended steps to upgrade? That would certainly help users avoid some of these gotcha's. How about a package just for the upgrade? I realize that maybe not all steps can be fully automated, but I think that can be handled gracefully. I am fairly new to Debian, but not averse to contributing. If this is something the team would like to have, I would consider doing it (with help). -- Glen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge - etch: usbnet
On Thu, 2007-04-12 at 03:15 +0200, Andreas Goesele wrote: I have a zaurus which under sarge I could connect to using usbnet and hotplug. This isn't something I have any experience with, but I did find some instructions for Etch[0], if you want to double check your configuration, and an old bug report[1] which might give you some help on tracking down this problem. If no one else can help you, I suggest you use reportbug to file a bug against the linux-2.6 package. 0. http://zsrep.sourceforge.net/docs/deb_etch_cradle_conf/ 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=335304 -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
Re: Sarge - Etch mailserver upgrade...
Pete Clarke wrote: cholet:~# aptitude dist-upgrade Reading Package Lists... Done Building Dependency Tree Reading extended state information Initializing package states... Done Some packages had unmet dependencies. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following packages have unmet dependencies: libfam0c102: Conflicts: libfam0 but 2.7.0-12 is to be installed. Check the release notes before upgrading. Read http://www.de.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#s-minimal_upgrade and use 4.5.4.1 or 4.5.4.2, whichever applies to your situation. Does this work ok? HTH, Johannes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Etch mailserver upgrade...
Read http://www.de.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#s-minimal_upgrade and use 4.5.4.1 or 4.5.4.2, whichever applies to your situation. Does this work ok? Doh! I read those notes too - that's how I managed to upgrade 6 o so boxes without a problem...just skipped that part because I saw X Windows stuff Thanks mate - much better! :-) Cheers, Pete. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge linux26 Install Corrupt?
On Thursday, 12.04.2007 at 13:02 -0500, Robert J Rae wrote: when I try to to install sarge as I have done many times via http, I now get warnings about kernel image removal and packages that have failed to install, web and mail packages that have worked fine in the past, so a little bit of reading points to etch upgrades having similar problems..but I don't want to upgrade.can I add some parameter at boot to just build a plain old sarge 3.1 ..or is my only option to build from the cd's It's possible that an HTTP install from a Sarge CD might look for 'stable' on the repositories? (Not sure, just thinking out loud) Anyway, if you're installing *afresh*, why don't you just use Etch, since it's now Stable? Dave. -- Please don't CC me on list messages! ... Dave Ewart - [EMAIL PROTECTED] - jabber: [EMAIL PROTECTED] All email from me is now digitally signed, key from http://www.sungate.co.uk/ Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92 signature.asc Description: Digital signature
Re: Sarge linux26 Install Corrupt?
On Thursday, 12.04.2007 at 21:31 +0100, Dave Ewart wrote: On Thursday, 12.04.2007 at 13:02 -0500, Robert J Rae wrote: when I try to to install sarge as I have done many times via http, I now get warnings about kernel image removal and packages that have failed to install, web and mail packages that have worked fine in the past, so a little bit of reading points to etch upgrades having similar problems..but I don't want to upgrade.can I add some parameter at boot to just build a plain old sarge 3.1 ..or is my only option to build from the cd's It's possible that an HTTP install from a Sarge CD might look for 'stable' on the repositories? (Not sure, just thinking out loud) To clarify - my point above is that 'stable' is no longer Sarge: and thus a Sarge net-install may not quite work any more. Dave. -- Please don't CC me on list messages! ... Dave Ewart - [EMAIL PROTECTED] - jabber: [EMAIL PROTECTED] All email from me is now digitally signed, key from http://www.sungate.co.uk/ Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92 signature.asc Description: Digital signature
Re: Sarge - Etch: A Painful Upgrade
On Thursday, 12.04.2007 at 14:13 -0400, Ralph Katz wrote: [bug report] If I may quote further from your report: - aptitude update (etch sources) - aptitude upgrade - see lots of warnings This was your first sign of trouble. And, given that you were not fully committed to an upgrade at that point, it would probably have been better if you'd stopped there - and reported the errors/warnings you saw. Given that you had trouble after what is a very simple operation, something fundamental must be wrong. Perhaps your previous downgrade from Sid to Sarge wasn't quite right, even though your system appeared to be operating fine. Any subsequent problems may well be as a result of that first problem. Are you *certain* your /etc/apt/sources.list were correct? What were the *actual* warnings (where you state lots of warnings)? Dave. -- Please don't CC me on list messages! ... Dave Ewart - [EMAIL PROTECTED] - jabber: [EMAIL PROTECTED] All email from me is now digitally signed, key from http://www.sungate.co.uk/ Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92 signature.asc Description: Digital signature
Re: Sarge linux26 Install Corrupt?
On Thu, 2007-04-12 at 13:02 -0500, Robert J Rae wrote: when I try to to install sarge as I have done many times via http, I now get warnings about kernel image removal and packages that have failed to install, web and mail packages that have worked fine in the past, so a little bit of reading points to etch upgrades having similar problems..but I don't want to upgrade.can I add some parameter at boot to just build a plain old sarge 3.1 ..or is my only option to build from the cd's Sarge is no longer stable. You installation CDs are looking at Etch as stable on the Debian repository mirrors. You will need to somehow make it them look for oldstable or Just install Etch from the Etch Installer, which is quite nice. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup signature.asc Description: This is a digitally signed message part
Re: Sarge - Etch: A Painful Upgrade
On 04/12/2007, Dave Ewart wrote: On Thursday, 12.04.2007 at 14:13 -0400, Ralph Katz wrote: [bug report] If I may quote further from your report: - aptitude update (etch sources) - aptitude upgrade - see lots of warnings This was your first sign of trouble. And, given that you were not fully committed to an upgrade at that point, it would probably have been better if you'd stopped there - and reported the errors/warnings you saw. In retrospect, absolutely! Given that you had trouble after what is a very simple operation, something fundamental must be wrong. Perhaps your previous downgrade from Sid to Sarge wasn't quite right, even though your system appeared to be operating fine. Not a chance. This machine had a fresh install of sarge last May (long after the sid/sarge downgrade) and was up-to-date as of the day of upgrade. Any subsequent problems may well be as a result of that first problem. Are you *certain* your /etc/apt/sources.list were correct? What were the *actual* warnings (where you state lots of warnings)? Too late now to remember it all clearly, unless there's evidence in the logs. Many of the warnings are captured in the logs if you check the bug report #418911, I even cat /etc/apt/sources.list at one point in the capture. I posted 6 mbs of logs in the bug. My post was more of a warning, 'heads-up, this may not be as easy as you think.' I hope to save others some aggravation and help the developers see how a user can flub it. Thanks Dave for your thoughts. Regards, Ralph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge - etch , apache 2.0 - apache 2.2 - problem
On Wednesday 11 April 2007 08:45, Albert Czarnecki wrote: Witam Po upgradzie z sarge na etch byl problem z apachem a dokladnie z opcja SSLOptions byl problem W wirtualce - SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire +CompatEnvVars apache2ctl -t Syntax error on line 59 of /etc/apache2/sites-enabled/cert: SSLOptions: Illegal option 'CompatEnvVars' Ktos moze sie orientuje czy to juz jest w samym apachu czy zastapili inna opcja? http://www.apache.org/dist/httpd/CHANGES_2.2 *) mod_ssl: Drop support for the CompatEnvVars argument to SSLOptions, which was never actually implemented in 2.0. [Joe Orton] :) -- Grzegorz Szymański | mailto:[EMAIL PROTECTED] | pgp:0x14A27314 jabber ID: [EMAIL PROTECTED]
Re: sarge - etch , apache 2.0 - apache 2.2 - problem
Grzegorz Szymański napisał(a): On Wednesday 11 April 2007 08:45, Albert Czarnecki wrote: Witam Po upgradzie z sarge na etch byl problem z apachem a dokladnie z opcja SSLOptions byl problem W wirtualce - SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire +CompatEnvVars apache2ctl -t Syntax error on line 59 of /etc/apache2/sites-enabled/cert: SSLOptions: Illegal option 'CompatEnvVars' Ktos moze sie orientuje czy to juz jest w samym apachu czy zastapili inna opcja? http://www.apache.org/dist/httpd/CHANGES_2.2 *) mod_ssl: Drop support for the CompatEnvVars argument to SSLOptions, which was never actually implemented in 2.0. [Joe Orton] :) Dzieki , musialem to przegabic:) Albert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge - etch: aptitude problem
On Thu, Apr 12, 2007 at 01:01:53AM +0200, Andreas Goesele wrote: Hi, doing an upgrade I encountered among others the following problem: I so far used apt-get, but following the release notes I switched to aptitude. But as a result much to much packages were installed: So my question: How can I - using aptitude - make sure that not all those meta-packages etc. are drawn in? By using the interactive mode of aptitude and confirming actions before going ahead. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge :sudo
n r a écrit, mardi 10 avril 2007, à 13:04 : bonjour, bonjour, j'ai voulu tester sudo !! Je modifie le fichier sudoers en rajoutant cette ligne webmALL=(root) NOPASSWD:/usr/bin/chgrp www-data /homed __ Sorry, user webm is not allowed to execute '/bin/chgrp www-data /homed' as root on serveur.domain.fr !! je ne vois pas mon erreur ?? /bin/chgrp != /usr/bin/chgrp :) -- Jacques L'helgoualc'h -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge :sudo
From: Jacques L'helgoualc'h [EMAIL PROTECTED] To: debian-user-french@lists.debian.org Subject: Re: sarge :sudo Date: Tue, 10 Apr 2007 15:38:41 +0200 n r a écrit, mardi 10 avril 2007, à 13:04 : bonjour, bonjour, j'ai voulu tester sudo !! Je modifie le fichier sudoers en rajoutant cette ligne webmALL=(root) NOPASSWD:/usr/bin/chgrp www-data /homed __ Sorry, user webm is not allowed to execute '/bin/chgrp www-data /homed' as root on serveur.domain.fr !! je ne vois pas mon erreur ?? /bin/chgrp != /usr/bin/chgrp :) en effet (oups) : je change dans sudoers webmALL=(root) NOPASSWD:/bin/chgrp www-data /homed je me logue webm webm:~$ sudo /bin/chgrp www-data /homed (mais il me demande le passwd ???) Password: _ MSN Hotmail sur i-mode : envoyez et recevez des e-mails depuis votre téléphone portable ! http://www.msn.fr/hotmailimode/ -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge jusqu'a quand ?
Le Tuesday 10 April 2007, [EMAIL PROTECTED]([EMAIL PROTECTED]) a écrit: Bonjour à toutes et tous, Salut, jusqu'à quand les serveurs auront les fichiers de sarge ? y aura t il encore des mises à jours de securités ? Normalement, c'est J+1An. Donc, jusqu'en avril 2008 A+ -- Glennie Vignarajah http://www.nephthys.org We can't all be heroes because somebody has to sit on the curb and clap as they go by. pgpaOB7IlKMIz.pgp Description: PGP signature
Re: sarge to etch upgrade failed with unmet dependencies
try running apt-get -f install for it to suggest a solution. Sometimes it is smarter than you are (and sometimes not) The force option simply allows apt-get to function if your package cache is broken. At least try it before reinstalling etch clean (although that might be fun) On 4/9/07, Tom Brown [EMAIL PROTECTED] wrote: On Monday 09 April 2007 14:51, Sven Arvidsson wrote: On Mon, 2007-04-09 at 14:25 -0700, Tom Brown wrote: I tried to uprade a dev server to etch today. The upgrade erred out on mysql upgrades. I'm told I might want to run 'apt-get -f install'. I've played with the force option before with bad results. Why are the libs that mysql depends on not upgraded first? Would it be a better idea to uninstall mysql, do the upgrade, then install the latest mysql? Any suggestions would be appreciated. Don't you need to upgrade libc6 first, as described in the release notes? I looked over the release notes. Thanks for pointing me there. The release notes said to do a 'dpkg --audit' on all installed packages. Here's what I found out: $ dpkg --audit The following packages are in a mess due to serious problems during installation. They must be reinstalled for them (and any packages that depend on them) to function properly: mysql-server-5.0 mysql database server binaries The following packages have been unpacked but not yet configured. They must be configured using dpkg --configure or the configure menu option in dselect for them to work: libmysqlclient15off mysql database client library libmysqlclient15-dev mysql database development files mysql-client-5.0 mysql database client binaries So, it turns out I have a damaged install of mysql-server. I tried to force a purge, but that failed. Well, it is a dev server so, a clean install of etch may be in order. Is there way to manually remove the package. I can manually remove the files, but what about the package db? Is it possible to do a manual uninstall from the db? If it is possible, is it worth the effort/risk? Thanks, Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- -Daniel ;-)
Re: sarge to etch upgrade failed with unmet dependencies
On 4/10/07, Tom Brown [EMAIL PROTECTED] wrote: Hi, I tried to uprade a dev server to etch today. The upgrade erred out on mysql upgrades. I'm told I might want to run 'apt-get -f install'. I've played with the force option before with bad results. Why are the libs that mysql depends on not upgraded first? Would it be a better idea to uninstall mysql, do the upgrade, then install the latest mysql? Any suggestions would be appreciated. Since no one else seems to be saying it, I'll just mention here that apt-get's -f option does not mean force. It means fix. See the manpage for more details. -- Kushal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge to etch upgrade failed with unmet dependencies
On Mon, 2007-04-09 at 14:25 -0700, Tom Brown wrote: I tried to uprade a dev server to etch today. The upgrade erred out on mysql upgrades. I'm told I might want to run 'apt-get -f install'. I've played with the force option before with bad results. Why are the libs that mysql depends on not upgraded first? Would it be a better idea to uninstall mysql, do the upgrade, then install the latest mysql? Any suggestions would be appreciated. Don't you need to upgrade libc6 first, as described in the release notes? -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
Re: sarge to etch upgrade failed with unmet dependencies
On Monday 09 April 2007 14:51, Sven Arvidsson wrote: On Mon, 2007-04-09 at 14:25 -0700, Tom Brown wrote: I tried to uprade a dev server to etch today. The upgrade erred out on mysql upgrades. I'm told I might want to run 'apt-get -f install'. I've played with the force option before with bad results. Why are the libs that mysql depends on not upgraded first? Would it be a better idea to uninstall mysql, do the upgrade, then install the latest mysql? Any suggestions would be appreciated. Don't you need to upgrade libc6 first, as described in the release notes? I looked over the release notes. Thanks for pointing me there. The release notes said to do a 'dpkg --audit' on all installed packages. Here's what I found out: $ dpkg --audit The following packages are in a mess due to serious problems during installation. They must be reinstalled for them (and any packages that depend on them) to function properly: mysql-server-5.0 mysql database server binaries The following packages have been unpacked but not yet configured. They must be configured using dpkg --configure or the configure menu option in dselect for them to work: libmysqlclient15off mysql database client library libmysqlclient15-dev mysql database development files mysql-client-5.0 mysql database client binaries So, it turns out I have a damaged install of mysql-server. I tried to force a purge, but that failed. Well, it is a dev server so, a clean install of etch may be in order. Is there way to manually remove the package. I can manually remove the files, but what about the package db? Is it possible to do a manual uninstall from the db? If it is possible, is it worth the effort/risk? Thanks, Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge to Etch, slighrly botched
On Thu, Apr 05, 2007 at 12:54:15PM -0700, Terrence Branscombe wrote: Today I followed the official Etch release notes to upgrade from Sarge to Etch and all went pretty well, except for some X services, i.e., the XDM and XFS services are no longer started at boot, nor can I start them manually with /etc/init.d/service name. Other TCP services like SSH and MySQL listener fire up just fine at boot, so the problem seems restricted to X-related network services. I do recall that during the upgrade I was advised that some TCP and UDP portmapper services would have to be manually restarted, but I am too much of a newbie to understand if that means something different that running a script from /etc/init.d/. All hints welcome! If xdm and xfs did not work, I'd probably try the 'reinstall' option of aptitude and see if that fixed it. I'd also consider making a bug report about this issue. -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal |mysite.verizon.net/kevin.mark/| | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keyserver: subkeys.pgp.net | my NPO: cfsg.org | |join the new debian-community.org to help Debian! | |___ Unless I ask to be CCd, assume I am subscribed ___| signature.asc Description: Digital signature
Re: Sarge to Etch, slighrly botched
On Thu, Apr 05, 2007 at 12:54:15PM -0700, Terrence Branscombe wrote: Today I followed the official Etch release notes to upgrade from Sarge to Etch and all went pretty well, except for some X services, i.e., the XDM and XFS services are no longer started at boot, nor can I start them manually with /etc/init.d/service name. Other TCP services like SSH and MySQL listener fire up just fine at boot, so the problem seems restricted to X-related network services. I do recall that during the upgrade I was advised that some TCP and UDP portmapper services would have to be manually restarted, but I am too much of a newbie to understand if that means something different that running a script from /etc/init.d/. If you did a reboot then _everything_ should have been restarted. If that still doesn't work: Boot single. Run the scripts in rc2.d one at a time with 'start' Watch for errors. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge Server with Sid Client? [was Re: I do consider Ubuntu to ...]
Am 2007-03-28 11:49:35, schrieb Chris Bannister: [Probably a silly question, but its something that I've been thinking about] It is a realy good question! Is there any problems running clients on Sid, but having your servers running stable? An example which springs to mind would be postgreSQL where the Sarge version is 7.x and Sid's client is postgresql-client-8.1. It depends, but it can be like here @me. Since I need functions of partitioning of tables I need PostgreSQL 8.2! But the upgrade was realy cool! -- Not a singel problem with the upgrade from 7.4 from Sarge to 8.2. But my own Workstations and my Customers running Clients based on 7.4 Which gaved us the hell! I had to build and install backports on ALL Sarge machines! I am guessing that you can't use the postgresql-client-8.1, i.e. psql, but would have to use ODBC or something similar. psql 8.1 will wok with a PostgreSQL 7.4 but not contraire. Do you have to worry about which versions of software your users are installing to access your servers, or, do you control all of that. Yes you should! Thanks, Greetings and nice Day Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSN LinuxMichi 0033/6/6192519367100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: Sarge Server with Sid Client? [was Re: I do consider Ubuntu to ...]
On Tue, Mar 27, 2007 at 07:42:27PM -0400, Roberto C. Sánchez wrote: On Wed, Mar 28, 2007 at 11:49:35AM +1200, Chris Bannister wrote: [Probably a silly question, but its something that I've been thinking about] Is there any problems running clients on Sid, but having your servers running stable? An example which springs to mind would be postgreSQL where the Sarge version is 7.x and Sid's client is postgresql-client-8.1. The answer is (as it is at many other times) it depends. I don't recall off the top of my head, but the psql client might well be able to speak to the older version of the server. In reality, the client is just communicating using SQL (plus some meta commands), so unless there has been some sort of non-compatible language change, you are probably OK. For other programs, it just depends. However, I would wager that most things that are network capable can either deal with different versions of applications connecting together or have some sort of compatibility (like NFS, which allows you to enable versions 2, 3 and 4 support for clients). Ah of course. I now remember why I thought of this. I wrote a simple c program to access my postgreSQL database and when I updated, the c program would no longer work. This was due to a change in the libraries versions. Of course, a recompile worked ok. Thanks for the insight. It helps to see the big picture when some of the fog clears. :-) -- Chris. == Don't forget to check that your /etc/apt/sources.lst entries point to etch and not testing, otherwise you may end up with a broken system once etch goes stable.
Re: Sarge Server with Sid Client? [was Re: I do consider Ubuntu to ...]
On Tue, Mar 27, 2007 at 11:25:21PM -0400, Jose Luis Rivas Contreras wrote: No really, all new versions are able to communicate with older versions. In fact in your server you need is what's more stable so must of servers (with Debian) are Sarge or Stable and you can use them even if you're in another thing different to Debian. Thanks. I should have realised what a daft question it was. -- Chris. == Don't forget to check that your /etc/apt/sources.lst entries point to etch and not testing, otherwise you may end up with a broken system once etch goes stable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge + dist-upgrade = ?
On Fri, Mar 30, 2007 at 12:08:37AM +0200, Martin Zobel-Helas wrote: Hi, On Thu Mar 29, 2007 at 14:57:47 -0700, Andrew Sackville-West wrote: On Thu, Mar 29, 2007 at 06:50:40PM -0300, Fernando Cacciola wrote: Hi All I just installed Debian Sarge from a 1-year old netinst CD on a HP Pavillion 1125LA notebook. Then I run apt-get dist-upgrade. What do I have now then? Still Sarge? 3.0, 3.1? You still have sarge, unless you changed the sources.list to point to something else. You've got the most recent sarge w/ security updates (I think that is on by default). I guess that's 3.1 r3 or so. 3.1r5 d'oh. thanks A signature.asc Description: Digital signature
Re: sarge + dist-upgrade = ?
Fernando Cacciola wrote: Hi All I just installed Debian Sarge from a 1-year old netinst CD on a HP Pavillion 1125LA notebook. Then I run apt-get dist-upgrade. What do I have now then? Still Sarge? 3.0, 3.1? The third field in /etc/apt/sources.list will tell you which distribution you are running. If you want to upgrade from Sarge to Etch, please read the release notes, (print it out) and then follow the instructions there. http://www.debian.org/releases/testing/i386/release-notes/ch-upgrading.en.html hth raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge + dist-upgrade = ?
On Thu, Mar 29, 2007 at 06:50:40PM -0300, Fernando Cacciola wrote: Hi All I just installed Debian Sarge from a 1-year old netinst CD on a HP Pavillion 1125LA notebook. Then I run apt-get dist-upgrade. What do I have now then? Still Sarge? 3.0, 3.1? You still have sarge, unless you changed the sources.list to point to something else. You've got the most recent sarge w/ security updates (I think that is on by default). I guess that's 3.1 r3 or so. A signature.asc Description: Digital signature
