Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
1 week ago, anyone who would have upgraded to mga2 with dsniff installed from mdv would have been in the exact same situation than now, except nobody cared at all. And the proof that nobody cared is that nobody pushed the rpm sooner. Would it have been pushed to 1, yes, that would have breached what we agreed to do. But it was not pushed to 1 ( and I would say likely on purpose ). So the only change with this upload is for people installing dsniff later. mga1 is not dead yet, so if someone who install mga1 now, could ask for dsniff and that should go to update since it is in mdv2010, right? That could be a problem imho... there always could be one person who upgrade from mdv2010 later... -- Angelo signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
Anssi Hannula skrev 3.1.2012 23:05: On 02.01.2012 12:21, guillomovitch wrote: Name: dsniff Relocations: (not relocatable) Version : 2.4 Vendor: Mageia.Org Release : 0.b1.1.mga2 Build Date: Mon Jan 2 11:18:17 2012 Install Date: (not installed) Build Host: ecosse Group : MonitoringSource RPM: (none) Size: 210074 License: BSD Signature : (none) Packager: guillomovitchguillomovitch URL : http://www.monkey.org/~dugsong/dsniff/ Summary : Network audit tools Description : Tools to audit network and to demonstrate the insecurity of cleartext network protocols. Please do not abuse this software. guillomovitchguillomovitch 2.4-0.b1.1.mga2: + Revision: 189630 - drop epoch, we don't care about updating from mdv anymore We don't? Oh yes we do. Atleast from 2010.1 Previous upgraders like me still have dsniff-2.4-0.b2.14mdv2010.1 on their MGA1 / cauldron systmes, which won't get upgraded to the MGA package without epoch. IMHO the epoch should be added. Yeah, it must be fixed. -- Thomas
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
Le 03/01/2012 22:05, Anssi Hannula a écrit : On 02.01.2012 12:21, guillomovitch wrote: Name: dsniff Relocations: (not relocatable) Version : 2.4 Vendor: Mageia.Org Release : 0.b1.1.mga2 Build Date: Mon Jan 2 11:18:17 2012 Install Date: (not installed) Build Host: ecosse Group : MonitoringSource RPM: (none) Size: 210074 License: BSD Signature : (none) Packager: guillomovitchguillomovitch URL : http://www.monkey.org/~dugsong/dsniff/ Summary : Network audit tools Description : Tools to audit network and to demonstrate the insecurity of cleartext network protocols. Please do not abuse this software. guillomovitchguillomovitch 2.4-0.b1.1.mga2: + Revision: 189630 - drop epoch, we don't care about updating from mdv anymore We don't? AFAIK, smooth upgrade garantee was only for mga1. Previous upgraders like me still have dsniff-2.4-0.b2.14mdv2010.1 on their MGA1 / cauldron systmes, which won't get upgraded to the MGA package without epoch. IMHO the epoch should be added. Well, given the target population, I though it was not worth to bloat the spec file forever just to handle a transitional issue. But feel free to readd it. -- BOFH excuse #260: We're upgrading /dev/null
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
Le mercredi 04 janvier 2012 à 11:03 +0200, Thomas Backlund a écrit : Anssi Hannula skrev 3.1.2012 23:05: On 02.01.2012 12:21, guillomovitch wrote: Name: dsniff Relocations: (not relocatable) Version : 2.4 Vendor: Mageia.Org Release : 0.b1.1.mga2 Build Date: Mon Jan 2 11:18:17 2012 Install Date: (not installed) Build Host: ecosse Group : MonitoringSource RPM: (none) Size: 210074 License: BSD Signature : (none) Packager: guillomovitchguillomovitch URL : http://www.monkey.org/~dugsong/dsniff/ Summary : Network audit tools Description : Tools to audit network and to demonstrate the insecurity of cleartext network protocols. Please do not abuse this software. guillomovitchguillomovitch 2.4-0.b1.1.mga2: + Revision: 189630 - drop epoch, we don't care about updating from mdv anymore We don't? Oh yes we do. Atleast from 2010.1 We did for 1, not for 2 or cauldron or anything else. So as long the package is not pushed on 1, I think we agreed that people could not care about upgrade path from Mandriva. -- Michael Scherer
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
On Wednesday 04 January 2012 10:54, Michael Scherer wrote: I think we agreed that people could not care about upgrade path from Mandriva. So, people like me who still run 2010.2 on many systems and later on would like to move to mga2 should first upgrade to mga1 and then upgrade to mga2? Or am I missing something? -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
Le 04/01/2012 14:18, Johnny A. Solbu a écrit : On Wednesday 04 January 2012 10:54, Michael Scherer wrote: I think we agreed that people could not care about upgrade path from Mandriva. So, people like me who still run 2010.2 on many systems and later on would like to move to mga2 should first upgrade to mga1 and then upgrade to mga2? Or am I missing something? No, 'no smooth upgrade garantee' only means you'll need to perform some manual update procedure for some very specific packages. For instance here, if you have dsniff installed, it won't be automatically upgraded, and you'll have to uninstall it first: rpm -e dsniff urpmi dsniff -- BOFH excuse #407: Route flapping at the NAP.
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
On 04.01.2012 11:54, Michael Scherer wrote: Le mercredi 04 janvier 2012 à 11:03 +0200, Thomas Backlund a écrit : Anssi Hannula skrev 3.1.2012 23:05: On 02.01.2012 12:21, guillomovitch wrote: Name: dsniff Relocations: (not relocatable) Version : 2.4 Vendor: Mageia.Org Release : 0.b1.1.mga2 Build Date: Mon Jan 2 11:18:17 2012 Install Date: (not installed) Build Host: ecosse Group : MonitoringSource RPM: (none) Size: 210074 License: BSD Signature : (none) Packager: guillomovitchguillomovitch URL : http://www.monkey.org/~dugsong/dsniff/ Summary : Network audit tools Description : Tools to audit network and to demonstrate the insecurity of cleartext network protocols. Please do not abuse this software. guillomovitchguillomovitch 2.4-0.b1.1.mga2: + Revision: 189630 - drop epoch, we don't care about updating from mdv anymore We don't? Oh yes we do. Atleast from 2010.1 We did for 1, not for 2 or cauldron or anything else. So as long the package is not pushed on 1, I think we agreed that people could not care about upgrade path from Mandriva. Well, I don't like that, IMO we should not remove upgradeability so soon, even if we won't officially support it. But anyway, this affects people doing 2010.1-mga1-mga2 as well... Or are you saying that isn't supported either, and people should do new installs?? -- Anssi Hannula
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
Le 04/01/2012 15:16, Anssi Hannula a écrit : On 04.01.2012 11:54, Michael Scherer wrote: Le mercredi 04 janvier 2012 à 11:03 +0200, Thomas Backlund a écrit : Anssi Hannula skrev 3.1.2012 23:05: On 02.01.2012 12:21, guillomovitch wrote: Name: dsniff Relocations: (not relocatable) Version : 2.4 Vendor: Mageia.Org Release : 0.b1.1.mga2 Build Date: Mon Jan 2 11:18:17 2012 Install Date: (not installed) Build Host: ecosse Group : MonitoringSource RPM: (none) Size: 210074 License: BSD Signature : (none) Packager: guillomovitchguillomovitch URL : http://www.monkey.org/~dugsong/dsniff/ Summary : Network audit tools Description : Tools to audit network and to demonstrate the insecurity of cleartext network protocols. Please do not abuse this software. guillomovitchguillomovitch 2.4-0.b1.1.mga2: + Revision: 189630 - drop epoch, we don't care about updating from mdv anymore We don't? Oh yes we do. Atleast from 2010.1 We did for 1, not for 2 or cauldron or anything else. So as long the package is not pushed on 1, I think we agreed that people could not care about upgrade path from Mandriva. Well, I don't like that, IMO we should not remove upgradeability so soon, even if we won't officially support it. But anyway, this affects people doing 2010.1-mga1-mga2 as well... Or are you saying that isn't supported either, and people should do new installs?? No, I just find it painful to add an ugly epoch tag in the spec file just to avoid some very few clever people (clever enough to run this kind of software) the need to run a pair of commands to update this specific package. However, if you prefer, just fix the spec file, I don't really care. -- BOFH excuse #171: NOTICE: alloc: /dev/null: filesystem full
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
04.01.2012 11:54, Michael Scherer skrev: Le mercredi 04 janvier 2012 à 11:03 +0200, Thomas Backlund a écrit : Anssi Hannula skrev 3.1.2012 23:05: On 02.01.2012 12:21, guillomovitch wrote: Name: dsniff Relocations: (not relocatable) Version : 2.4 Vendor: Mageia.Org Release : 0.b1.1.mga2 Build Date: Mon Jan 2 11:18:17 2012 Install Date: (not installed) Build Host: ecosse Group : MonitoringSource RPM: (none) Size: 210074 License: BSD Signature : (none) Packager: guillomovitchguillomovitch URL : http://www.monkey.org/~dugsong/dsniff/ Summary : Network audit tools Description : Tools to audit network and to demonstrate the insecurity of cleartext network protocols. Please do not abuse this software. guillomovitchguillomovitch 2.4-0.b1.1.mga2: + Revision: 189630 - drop epoch, we don't care about updating from mdv anymore We don't? Oh yes we do. Atleast from 2010.1 We did for 1, not for 2 or cauldron or anything else. So as long the package is not pushed on 1, I think we agreed that people could not care about upgrade path from Mandriva. That does not mean we should intentionally break upgrades either. -- Thomas
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
Le mercredi 04 janvier 2012 à 16:16 +0200, Anssi Hannula a écrit : On 04.01.2012 11:54, Michael Scherer wrote: Le mercredi 04 janvier 2012 à 11:03 +0200, Thomas Backlund a écrit : Anssi Hannula skrev 3.1.2012 23:05: On 02.01.2012 12:21, guillomovitch wrote: Name: dsniff Relocations: (not relocatable) Version : 2.4 Vendor: Mageia.Org Release : 0.b1.1.mga2 Build Date: Mon Jan 2 11:18:17 2012 Install Date: (not installed) Build Host: ecosse Group : MonitoringSource RPM: (none) Size: 210074 License: BSD Signature : (none) Packager: guillomovitchguillomovitch URL : http://www.monkey.org/~dugsong/dsniff/ Summary : Network audit tools Description : Tools to audit network and to demonstrate the insecurity of cleartext network protocols. Please do not abuse this software. guillomovitchguillomovitch 2.4-0.b1.1.mga2: + Revision: 189630 - drop epoch, we don't care about updating from mdv anymore We don't? Oh yes we do. Atleast from 2010.1 We did for 1, not for 2 or cauldron or anything else. So as long the package is not pushed on 1, I think we agreed that people could not care about upgrade path from Mandriva. Well, I don't like that, IMO we should not remove upgradeability so soon, even if we won't officially support it. Well, if we do not officially support it, then we do not support it, that's all. There is no that's unofficially supported or stuff like that. Supported mean we will do test and fix bug if they happen, and not supported mean we reserve our right to not do anything. And that's exactly what happen right now. But anyway, this affects people doing 2010.1-mga1-mga2 as well... Or are you saying that isn't supported either, and people should do new installs?? We do not support upgrading mdv2010.1 rpms with rpm from mga2, so if a maintainer want to remove this, he can. Someone doing mdv2010.1-mga1 will end with a mix of mdv2010.1 and mga1 if the system is not cleaned, and that's not something we should support, not more than mga X + any random repository upgrade to mga X+1 IE, that's not mga1 - mga2, that's mga1 + 3rd party repo that happened to work by chance to mga2. -- Michael Scherer
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
Le 04/01/2012 18:05, Thomas Backlund a écrit : That does not mean we should intentionally break upgrades either. I wonder how much energy will be wasted replying to this thread before someone fix the package directly... -- BOFH excuse #388: Bad user karma.
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
On 04.01.2012 19:29, Michael Scherer wrote: Le mercredi 04 janvier 2012 à 16:16 +0200, Anssi Hannula a écrit : On 04.01.2012 11:54, Michael Scherer wrote: Le mercredi 04 janvier 2012 à 11:03 +0200, Thomas Backlund a écrit : Anssi Hannula skrev 3.1.2012 23:05: On 02.01.2012 12:21, guillomovitch wrote: Name: dsniff Relocations: (not relocatable) Version : 2.4 Vendor: Mageia.Org Release : 0.b1.1.mga2 Build Date: Mon Jan 2 11:18:17 2012 Install Date: (not installed) Build Host: ecosse Group : MonitoringSource RPM: (none) Size: 210074 License: BSD Signature : (none) Packager: guillomovitchguillomovitch URL : http://www.monkey.org/~dugsong/dsniff/ Summary : Network audit tools Description : Tools to audit network and to demonstrate the insecurity of cleartext network protocols. Please do not abuse this software. guillomovitchguillomovitch 2.4-0.b1.1.mga2: + Revision: 189630 - drop epoch, we don't care about updating from mdv anymore We don't? Oh yes we do. Atleast from 2010.1 We did for 1, not for 2 or cauldron or anything else. So as long the package is not pushed on 1, I think we agreed that people could not care about upgrade path from Mandriva. Well, I don't like that, IMO we should not remove upgradeability so soon, even if we won't officially support it. Well, if we do not officially support it, then we do not support it, that's all. There is no that's unofficially supported or stuff like that. Supported mean we will do test and fix bug if they happen, and not supported mean we reserve our right to not do anything. And that's exactly what happen right now. IMO there is a level between officially supported and we intentionally break it, which means that we advise against it but do not hinder people from doing it. Also, I personally do fix any upgradeability bugs for the last several releases if such are reported to me (though you are right that I do not specifically test them, hence unsupported. But anyway, this affects people doing 2010.1-mga1-mga2 as well... Or are you saying that isn't supported either, and people should do new installs?? We do not support upgrading mdv2010.1 rpms with rpm from mga2, so if a maintainer want to remove this, he can. Someone doing mdv2010.1-mga1 will end with a mix of mdv2010.1 and mga1 if the system is not cleaned, and that's not something we should support, not more than mga X + any random repository upgrade to mga X+1 IE, that's not mga1 - mga2, that's mga1 + 3rd party repo that happened to work by chance to mga2. I have to strongly disagree with this. If upgrading from 2010.1 to mga1 is officially supported (and it is), we can't say you can't upgrade your mga1 system to mga2 anymore because you have some old pkgs installed which we never asked you to remove (assuming no non-mdv 3rd party repos here). Upgrading the distribution via path N - N+1 - N+2 - N+3 - N+4 (without extra repositories) should *always* be supported, and I see no reason to break that for the mdv-mga transition point either. -- Anssi Hannula
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
Le mercredi 04 janvier 2012 à 20:09 +0200, Anssi Hannula a écrit : On 04.01.2012 19:29, Michael Scherer wrote: Le mercredi 04 janvier 2012 à 16:16 +0200, Anssi Hannula a écrit : On 04.01.2012 11:54, Michael Scherer wrote: Le mercredi 04 janvier 2012 à 11:03 +0200, Thomas Backlund a écrit : Anssi Hannula skrev 3.1.2012 23:05: On 02.01.2012 12:21, guillomovitch wrote: Name: dsniff Relocations: (not relocatable) Version : 2.4 Vendor: Mageia.Org Release : 0.b1.1.mga2 Build Date: Mon Jan 2 11:18:17 2012 Install Date: (not installed) Build Host: ecosse Group : MonitoringSource RPM: (none) Size: 210074 License: BSD Signature : (none) Packager: guillomovitchguillomovitch URL : http://www.monkey.org/~dugsong/dsniff/ Summary : Network audit tools Description : Tools to audit network and to demonstrate the insecurity of cleartext network protocols. Please do not abuse this software. guillomovitchguillomovitch 2.4-0.b1.1.mga2: + Revision: 189630 - drop epoch, we don't care about updating from mdv anymore We don't? Oh yes we do. Atleast from 2010.1 We did for 1, not for 2 or cauldron or anything else. So as long the package is not pushed on 1, I think we agreed that people could not care about upgrade path from Mandriva. Well, I don't like that, IMO we should not remove upgradeability so soon, even if we won't officially support it. Well, if we do not officially support it, then we do not support it, that's all. There is no that's unofficially supported or stuff like that. Supported mean we will do test and fix bug if they happen, and not supported mean we reserve our right to not do anything. And that's exactly what happen right now. IMO there is a level between officially supported and we intentionally break it, which means that we advise against it but do not hinder people from doing it. Yes, there is different levels of support, obviously, since people have different but that doesn't mean we should rely on them, or try to officially use them. Again, saying we support that, so we do that, and we don't support this, so people are free to do what they want is simpler. The whole scheme of having stuff we do, stuff we do not promise but try to, stuff we do not promise and we do not try to ( or more ) make things less clear for everybody. Having a non uniform policy will make things harder for newer packagers ( and for olders too ). We have users ( in the past ) that complained about the lack of reliability of packages on Mandriva. And this was IMHO because we had a policy of 'we keep everything and we say they are in a section of maybe supported'. The whole message contribs is not supported but main is was simple and yet, too complex to grasp ( because people didn't check contrib/main before installing anything, ). It was also far from the truth because some stuff in contribs were more supported than stuff in main, and thus we were sending mixed messages. So we should really stick on what we support, and send a simple, clear and correct message. And I think we need to keep things simple to solve such issues in the long run. But anyway, this affects people doing 2010.1-mga1-mga2 as well... Or are you saying that isn't supported either, and people should do new installs?? We do not support upgrading mdv2010.1 rpms with rpm from mga2, so if a maintainer want to remove this, he can. Someone doing mdv2010.1-mga1 will end with a mix of mdv2010.1 and mga1 if the system is not cleaned, and that's not something we should support, not more than mga X + any random repository upgrade to mga X+1 IE, that's not mga1 - mga2, that's mga1 + 3rd party repo that happened to work by chance to mga2. I have to strongly disagree with this. If upgrading from 2010.1 to mga1 is officially supported (and it is), we can't say you can't upgrade your mga1 system to mga2 anymore because you have some old pkgs installed which we never asked you to remove (assuming no non-mdv 3rd party repos here). First, it doesn't break the whole upgrade. In fact, if we look carefully, people who were running non supported software ( ie a package from Mandriva ) will still run the same unsupported software and the same binary. And upgrade will likely work without error messages. Because nothing requires dsniff, except its own subpackage. Secondly, it didn't matter much before Guillaume uploaded dsniff. 1 week ago, anyone who would have upgraded to mga2 with dsniff installed from mdv would have been in the exact same situation than now, except nobody cared at all. And the proof that nobody cared is that nobody pushed the rpm sooner. Would it have been pushed to 1, yes, that would have breached what we agreed to do. But it was not pushed to 1
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
On 05.01.2012 00:16, Michael Scherer wrote: Le mercredi 04 janvier 2012 à 20:09 +0200, Anssi Hannula a écrit : On 04.01.2012 19:29, Michael Scherer wrote: Le mercredi 04 janvier 2012 à 16:16 +0200, Anssi Hannula a écrit : On 04.01.2012 11:54, Michael Scherer wrote: Le mercredi 04 janvier 2012 à 11:03 +0200, Thomas Backlund a écrit : Anssi Hannula skrev 3.1.2012 23:05: On 02.01.2012 12:21, guillomovitch wrote: Name: dsniff Relocations: (not relocatable) Version : 2.4 Vendor: Mageia.Org Release : 0.b1.1.mga2 Build Date: Mon Jan 2 11:18:17 2012 Install Date: (not installed) Build Host: ecosse Group : MonitoringSource RPM: (none) Size: 210074 License: BSD Signature : (none) Packager: guillomovitchguillomovitch URL : http://www.monkey.org/~dugsong/dsniff/ Summary : Network audit tools Description : Tools to audit network and to demonstrate the insecurity of cleartext network protocols. Please do not abuse this software. guillomovitchguillomovitch 2.4-0.b1.1.mga2: + Revision: 189630 - drop epoch, we don't care about updating from mdv anymore We don't? Oh yes we do. Atleast from 2010.1 We did for 1, not for 2 or cauldron or anything else. So as long the package is not pushed on 1, I think we agreed that people could not care about upgrade path from Mandriva. Well, I don't like that, IMO we should not remove upgradeability so soon, even if we won't officially support it. Well, if we do not officially support it, then we do not support it, that's all. There is no that's unofficially supported or stuff like that. Supported mean we will do test and fix bug if they happen, and not supported mean we reserve our right to not do anything. And that's exactly what happen right now. IMO there is a level between officially supported and we intentionally break it, which means that we advise against it but do not hinder people from doing it. Yes, there is different levels of support, obviously, since people have different but that doesn't mean we should rely on them, or try to officially use them. Again, saying we support that, so we do that, and we don't support this, so people are free to do what they want is simpler. The whole scheme of having stuff we do, stuff we do not promise but try to, stuff we do not promise and we do not try to ( or more ) make things less clear for everybody. Having a non uniform policy will make things harder for newer packagers ( and for olders too ). We have users ( in the past ) that complained about the lack of reliability of packages on Mandriva. And this was IMHO because we had a policy of 'we keep everything and we say they are in a section of maybe supported'. The whole message contribs is not supported but main is was simple and yet, too complex to grasp ( because people didn't check contrib/main before installing anything, ) It was not too complex, just badly implemented. The users got *no* in-GUI notification at all that contrib was unsupported (most users don't read wiki pages etc, especially if we don't link them to them). . It was also far from the truth because some stuff in contribs were more supported than stuff in main, and thus we were sending mixed messages. Right. So we should really stick on what we support, and send a simple, clear and correct message. And I think we need to keep things simple to solve such issues in the long run. I'm not advocating any change on the message sent to users, just to not break upgrade intentionally (by removing near-zero-maintentance upgrade support by dropping obsoletes/epochs that are needed for upgrade from the several last distribution versions). But anyway, this affects people doing 2010.1-mga1-mga2 as well... Or are you saying that isn't supported either, and people should do new installs?? We do not support upgrading mdv2010.1 rpms with rpm from mga2, so if a maintainer want to remove this, he can. Someone doing mdv2010.1-mga1 will end with a mix of mdv2010.1 and mga1 if the system is not cleaned, and that's not something we should support, not more than mga X + any random repository upgrade to mga X+1 IE, that's not mga1 - mga2, that's mga1 + 3rd party repo that happened to work by chance to mga2. I have to strongly disagree with this. If upgrading from 2010.1 to mga1 is officially supported (and it is), we can't say you can't upgrade your mga1 system to mga2 anymore because you have some old pkgs installed which we never asked you to remove (assuming no non-mdv 3rd party repos here). First, it doesn't break the whole upgrade. In fact, if we look carefully, people who were running non supported software ( ie a package from Mandriva ) will still run the same unsupported software and the same binary. And upgrade will likely work without error
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
On 02.01.2012 12:21, guillomovitch wrote: Name: dsniff Relocations: (not relocatable) Version : 2.4 Vendor: Mageia.Org Release : 0.b1.1.mga2 Build Date: Mon Jan 2 11:18:17 2012 Install Date: (not installed) Build Host: ecosse Group : MonitoringSource RPM: (none) Size: 210074 License: BSD Signature : (none) Packager: guillomovitch guillomovitch URL : http://www.monkey.org/~dugsong/dsniff/ Summary : Network audit tools Description : Tools to audit network and to demonstrate the insecurity of cleartext network protocols. Please do not abuse this software. guillomovitch guillomovitch 2.4-0.b1.1.mga2: + Revision: 189630 - drop epoch, we don't care about updating from mdv anymore We don't? Previous upgraders like me still have dsniff-2.4-0.b2.14mdv2010.1 on their MGA1 / cauldron systmes, which won't get upgraded to the MGA package without epoch. IMHO the epoch should be added. Also, not your fault but it seems genhdlist didn't handle the removal of epoch without altering rpm file name well, hdlists still show the epoch, causing urpmi to try upgrading to the now epoch-less version, causing the transaction to be rejected by rpm. -- Anssi Hannula
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2
On Tue, Jan 3, 2012 at 21:05, Anssi Hannula an...@mageia.org wrote: On 02.01.2012 12:21, guillomovitch wrote: Name : dsniff Relocations: (not relocatable) Version : 2.4 Vendor: Mageia.Org Release : 0.b1.1.mga2 Build Date: Mon Jan 2 11:18:17 2012 Install Date: (not installed) Build Host: ecosse Group : Monitoring Source RPM: (none) Size : 210074 License: BSD Signature : (none) Packager : guillomovitch guillomovitch URL : http://www.monkey.org/~dugsong/dsniff/ Summary : Network audit tools Description : Tools to audit network and to demonstrate the insecurity of cleartext network protocols. Please do not abuse this software. guillomovitch guillomovitch 2.4-0.b1.1.mga2: + Revision: 189630 - drop epoch, we don't care about updating from mdv anymore We don't? Previous upgraders like me still have dsniff-2.4-0.b2.14mdv2010.1 on their MGA1 / cauldron systmes, which won't get upgraded to the MGA package without epoch. IMHO the epoch should be added. Also, not your fault but it seems genhdlist didn't handle the removal of epoch without altering rpm file name well, hdlists still show the epoch, causing urpmi to try upgrading to the now epoch-less version, causing the transaction to be rejected by rpm. Yes genhdlist2 only considers the filename to decide if a package was added/removed, and keeps the header if filename didn't change
