It also exists in Fedora as well, here's the source-package: http://download.fedora.redhat.com/pub/fedora/linux/updates/13/SRPMS/putty-0.60-6.20100910svn.fc13.src.rpm

Sorry. That one's old. Here's the latest source: http://pkgs.fedoraproject.org/gitweb/?p=putty.git

Too late for the mageia 1 release, but we can import later and backport. ( there is already a mandriva package )

CC: (none) => misc

My CS instructor just suggested puTTy, so I could use a Mageia package, too.

CC: (none) => kmmos1

The Mandriva-version give me this:

Som desired packages cannot be installed:

putty-0.60-4mdv2010.0.x86_64 (because of insufficient libgdk-1.2.so.0()(64-bit))

If you add putty, please add libgdk as a dep as well.

Putty is available in cauldron, I'll try to put it in updates_testing for Mageia 1 as it was present in Mandriva.

CC: (none) => stormi
Assignee: bugsquad => stormi

Can you wait with this? I'm trying to upgrade it to latest stable version. Hopefully today.

CC: (none) => sander.lepik

no problem, I stepped in because it was assigned to no one :)

New version submitted to cauldron. You can move it to updates now. Not so sure how it's done when there is no previous version. :)

(In reply to comment #9)
> New version submitted to cauldron. You can move it to updates now. Not so sure
> how it's done when there is no previous version. :)

Here is how I will do. Not to be taken as the official way, but from the advice I got on IRC + my own thinking, I hope it is ok (done for several games already) : 

svn cp svn+ssh://svn.mageia.org/svn/packages/cauldron/putty
svn+ssh://svn.mageia.org/svn/packages/updates/1/putty
svn mkdir svn+ssh://svn.mageia.org/svn/binrepos/updates/1/putty
mgarepo co 1/putty
cd putty
vi SPECS/putty.spec #update release and add subrel
mgarepo sync -c
mgarepo submit -t 1 --define section=core/updates_testing

For release and subrel, usually a new package would have release 0 and subrel 1, but to allow migration from mandriva, I set a higher release that in mandriva 2010.2 if the version is the same, then increase it in cauldron too so that it's higher than in Mageia 1.

Submitted into Core Updates Testing, those who requested, please test.

Status: NEW => ASSIGNED
Assignee: stormi => qa-bugs

Tested now & it works AFAICS.

Closing as RESOLVED FIXED

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Reopening : the update still has to be pushed to updates.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

(In reply to comment #12)
> Tested now & it works AFAICS.

On wich arch did you test?


Tested here on i586:
Install - OK
Connecting to SSH - OK


We need test on x86_64.

(In reply to comment #10)
[...]
> then increase it in cauldron too so
> that it's higher than in Mageia 1.

(FWIW, this isn't necessarily needed, cauldron package is mag2 whereas the Mageia 1 package is mga1, so it's upgradable from mga1 -> Cauldron on time of submit to updates_testing; after that only the subrel should be bumped when rebuilding it in mga1).

(In reply to comment #16)
> (In reply to comment #10)
> [...]
> > then increase it in cauldron too so
> > that it's higher than in Mageia 1.
> 
> (FWIW, this isn't necessarily needed, cauldron package is mag2 whereas the
> Mageia 1 package is mga1, so it's upgradable from mga1 -> Cauldron on time of
> submit to updates_testing; after that only the subrel should be bumped when
> rebuilding it in mga1).

I do that to be safe : the point of subrel is to be increased without any risk of the package becoming not upgradable to the version in the n+1 distribution. If cauldron has release 5.mga2 and updates has 5.mga1, it looks safe, but as soon as we'll fix a bug in mga1, release will become 5.1.mga1 which is higher than 5.mga2. That's why, for security, I would se the release in cauldron to 6.mga2 so that we can increase the subrel at will in mga1. 

Am I overlooking something ?

I tested on x86_64.

Ok, this package can be moved to the Core Updates then.

Comment 15 and comment 18 show this update has been tested on both 32 and
64 bit systems.

Can someone from the sysadmin team push the package
putty
srpm putty-0.61-0.1.mga1.src.rpm
from Core Updates Testing to Core Updates please.

Advisory:
This update adds the putty graphical SSH, Telnet and Rlogin client which
was present in Mandriva 2010.2, but missing in Mageia 1.

CC: (none) => davidwhodgins

(In reply to comment #17)
> (In reply to comment #16)
> > (In reply to comment #10)
> > [...]
> > > then increase it in cauldron too so
> > > that it's higher than in Mageia 1.
> > 
> > (FWIW, this isn't necessarily needed, cauldron package is mag2 whereas the
> > Mageia 1 package is mga1, so it's upgradable from mga1 -> Cauldron on time of
> > submit to updates_testing; after that only the subrel should be bumped when
> > rebuilding it in mga1).
> 
> I do that to be safe : the point of subrel is to be increased without any risk
> of the package becoming not upgradable to the version in the n+1 distribution.
> If cauldron has release 5.mga2 and updates has 5.mga1, it looks safe, but as
> soon as we'll fix a bug in mga1, release will become 5.1.mga1 which is higher
> than 5.mga2. That's why, for security, I would se the release in cauldron to
> 6.mga2 so that we can increase the subrel at will in mga1. 
> 
> Am I overlooking something ?

No, you're right, 5.1mga1 is higher than 5mga2.

Note that comment 17 and comment 21 are about the release number in cauldron, so
it doesn't stop this update.

Can someone from the sysadmin team push the package
putty
srpm putty-0.61-0.1.mga1.src.rpm
from Core Updates Testing to Core Updates please.

Advisory:
This update adds the putty graphical SSH, Telnet and Rlogin client which
was present in Mandriva 2010.2, but missing in Mageia 1

Keywords: (none) => validated_update
CC: (none) => mageia-sysadm
Source RPM: (none) => putty-0.61-0.1.mga1.src.rpm

The release number is wrong, like for 2239 . Unvalidating update.

Release 0 is specifically done for pre release, and putty is not, so this should not be used.

Keywords: validated_update => (none)

I disagree, this is how updates were done in mdv and there are good reasons for that (see the current thread on the -dev ML)

Many other updates are in the same situation.

Keywords: (none) => validated_update

The package seems to be partially pushed : binaries are in updates and srpm in updates_testing.

I fixed the release to follow the policy, please push the new package.

Version: Cauldron => 1

Pushed to updates.

Status: REOPENED => RESOLVED
CC: (none) => boklm
Resolution: (none) => FIXED