[opensuse-packaging] Another python related query
Sascha, Since you're the python guru, I just noticed that you put python-scapy in D:L:P a few months ago and sent it to factory. The D:L:P version has a tarball version of "latest" which could mean anything. The specfile says 2.1.0 That's great, except scapy is also in security and it's version 2.2.0 there. I'm not positive security:scapy is the same thing as D:L:P:python-scapy, but the description of both is the sames o it sure looks like it. Seems like a D:L:P python-scapy should be updated to 2.2.0 and security-scapy either trashed or linked to D:L:P fyi: I haven't used scapy yet, I was just looking to see if we had it packaged so I could try it out and was surprised to see it twice. Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 08/15/2013 06:33 PM, Greg Freemyer wrote:
Sascha,
Since you're the python guru, I just noticed that you put python-scapy in D:L:P a few months ago and sent it to factory.
The D:L:P version has a tarball version of "latest" which could mean anything. The specfile says 2.1.0
That's great, except scapy is also in security and it's version 2.2.0 there.
I'm not positive security:scapy is the same thing as D:L:P:python-scapy, but the description of both is the sames o it sure looks like it.
I've checked and you are right, it's packaged twice.
Seems like a D:L:P python-scapy should be updated to 2.2.0 and security-scapy either trashed or linked to D:L:P
Since it's more on-topic, I'd say it can stay in security and the d:l:p version can be dropped. I'll do a submit request to merge them.
fyi: I haven't used scapy yet, I was just looking to see if we had it packaged so I could try it out and was surprised to see it twice.
That happens more often than we realize. -- Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)
On 08/16/2013 08:56 AM, Sascha Peilicke wrote:
On 08/15/2013 06:33 PM, Greg Freemyer wrote:
Sascha,
Since you're the python guru, I just noticed that you put python-scapy in D:L:P a few months ago and sent it to factory.
The D:L:P version has a tarball version of "latest" which could mean anything. The specfile says 2.1.0
That's great, except scapy is also in security and it's version 2.2.0 there.
I'm not positive security:scapy is the same thing as D:L:P:python-scapy, but the description of both is the sames o it sure looks like it.
I've checked and you are right, it's packaged twice.
Seems like a D:L:P python-scapy should be updated to 2.2.0 and security-scapy either trashed or linked to D:L:P
Since it's more on-topic, I'd say it can stay in security and the d:l:p version can be dropped. I'll do a submit request to merge them.
It's sr#195414 for the merge and sr#195412 to drop python-scapy from Factory. Once that is done, scapy could be submitted to Factory again.
fyi: I haven't used scapy yet, I was just looking to see if we had it packaged so I could try it out and was surprised to see it twice.
That happens more often than we realize.
-- Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)
On Fri, Aug 16, 2013 at 3:16 AM, Sascha Peilicke <speilicke@suse.com> wrote:
Since it's more on-topic, I'd say it can stay in security and the d:l:p version can be dropped. I'll do a submit request to merge them.
It's sr#195414 for the merge and sr#195412 to drop python-scapy from Factory. Once that is done, scapy could be submitted to Factory again.
It has been dropped from factory and I just did an SR from security: SR#196714 As a leaf package I assume the feature freeze will still allow it back in. Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (2)
-
Greg Freemyer -
Sascha Peilicke