Bug 786780 - ipset-6.11 is available
Summary: ipset-6.11 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ipset
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mathieu Bridon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-02 11:27 UTC by Upstream Release Monitoring
Modified: 2012-04-12 02:34 UTC (History)
3 users (show)

Fixed In Version: ipset-6.11-1.fc17
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-12 02:34:20 UTC
Type: ---


Attachments (Terms of Use)

Description Upstream Release Monitoring 2012-02-02 11:27:35 UTC
Latest upstream release: 6.11
Current version in Fedora Rawhide: 6.9.1
URL: http://ftp.netfilter.org/pub/ipset/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 1 Mathieu Bridon 2012-02-02 13:26:11 UTC
(The history of the wiki page tells me ipset was added to the upstream monitoring either by xosevp or salimma, so I'm adding you both to CC)

I find it a bit rude that someone added ipset to the upstream release monitoring without telling me.

At the very least, if someone is interested in the package, I would have expected them to talk to me and eventually become a co-maintainer.

Anyway, I'll try to do the update soon, probably next week.

Again, if you are interested in the package, I'll be more than happy to give you the ACLs in PackageDB. :)

Comment 2 Michel Alexandre Salim 2012-02-03 01:15:14 UTC
It was me, as you can see from the page history:

  https://fedoraproject.org/w/index.php?title=Upstream_release_monitoring&action=historysubmit&diff=269296&oldid=269287

but I'm not the person being rude; ipset was in the "Check My Packages, Please!" section (see the linked diff) and, assuming that people don't just list other people's packages there, I assumed one of the (co-)maintainers did, and just cleared it up. Sorry for the misunderstanding, though.

Comment 3 Account closed by user 2012-03-13 14:56:51 UTC
(In reply to comment #1)

> I find it a bit rude that someone added ipset to the upstream release
> monitoring without telling me.

Rude? Your current work as maintainer is to keep the package updated.

Anyway, you can put your name here:
https://fedoraproject.org/wiki/Upstream_Release_Monitoring#Package_Owner_Ignore_List
and you won't get any bug comming from upstream-release-monitoring.

-thanks-

Comment 4 Account closed by user 2012-03-15 15:43:53 UTC
changelog:

6.11
 - Support hostnames and service names with dash
 - Exceptions support added to hash:*net* types
 - Log warning when a hash type of set gets full
 - Set types moved into libipset library
 - Library map file added in order to support library versioning
 - doc: Linux 2.6.39 already has the defs (Jan Engelhardt)
 - build: install libipset in the right place (Jan Engelhardt)
 - Provide a pkgconfig file (Jan Engelhardt)
 - build: make distcheck work and use POSIX mode for tarball generation
   (Jan Engelhardt)
 - build: install libipset/linux_ip_set_list.h (Jan Engelhardt)
 - build: include libipset/nfproto.h (Jan Engelhardt)
 - build: process include/libipset/ (Jan Engelhardt)
 - build: use AC_CONFIG_AUX_DIR and stash away tools (Jan Engelhardt)
 - Update .gitignore (Jan Engelhardt)

6.10
 - Tests added to check ICMP/ICMPv6 type/code parsing
 - ICMP/ICMPv6 type/code parser bug fixed (bug reported by Sabitov)
 - ipset: fix lookup of tcp port names (Stephen Hemminger)
 - Optionally disable building the kernel module (Mathieu Bridon)
 - Make tidy complete

Comment 5 Mathieu Bridon 2012-03-28 10:38:08 UTC
(In reply to comment #3)
> (In reply to comment #1)
> 
> > I find it a bit rude that someone added ipset to the upstream release
> > monitoring without telling me.
> 
> Rude? Your current work as maintainer is to keep the package updated.

No, my job as a maintainer is to keep the package maintained. There is no obligation to always update.

And yes, I find it rude to add packages maintained by others in an opt-in mechanism without consulting them.

> Anyway, you can put your name here:
> https://fedoraproject.org/wiki/Upstream_Release_Monitoring#Package_Owner_Ignore_List
> and you won't get any bug comming from upstream-release-monitoring.

No.

The same page you quote even says:
  Please only add your own packages here!
  If you are not the maintainer or co-maintainer of a package, please
  do not add it here unless you were explicitly requested to do so by a
  maintainer/co-maintainer.

This means that this is an opt-in service, and maintainers should be the ones opting in.

I can understand that you have an interest in a package, but the least you can do is to ask the maintainers whether they are interested in using the Upstream Release Monitoring.

That being said, let's close this tangent. The bug report was about a new version being available, and it's being built on Koji. I'll push updates for Rawhide and Fedora 17.

Comment 6 Fedora Update System 2012-03-28 10:55:25 UTC
ipset-6.11-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/ipset-6.11-1.fc17

Comment 7 Fedora Update System 2012-03-28 19:36:36 UTC
Package ipset-6.11-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ipset-6.11-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-4834/ipset-6.11-1.fc17
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2012-04-12 02:34:20 UTC
ipset-6.11-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.