Skip to contentSkip to conversation

dmapi-2.2.9 release

DISCUSSION Mike Frysinger 4 participants 12 messages Feb 22, 2009 – Feb 24, 2009

lore
Share & tools
lore
#1 lore raw

xfsprogs/xfsdump release process

Quoted 3 lines · On Sunday 22 February 2009 13:48:49 Mike Frysinger wrote:

how are release tarballs created ? seems like there's an error in the process as the dmapi-2.2.9 contains files it shouldnt. for example, autom4te.cache/, include/builddefs, etc...

in a similar vain, every xfsdump/xfsprogs release has made people run autoconf first as the configure script is considered part of the distclean target in general. i dont think that makes any sense as the configure script should be included with every release tarball.
-mike

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#2 lore raw

Re: xfsprogs/xfsdump release process

Quoted 9 lines · Mike Frysinger
Quoted 3 lines · On Sunday 22 February 2009 13:48:49 Mike Frysinger wrote:

how are release tarballs created ? seems like there's an error in the process as the dmapi-2.2.9 contains files it shouldnt. for example, autom4te.cache/, include/builddefs, etc...

in a similar vain, every xfsdump/xfsprogs release has made people run autoconf first as the configure script is considered part of the distclean target in general. i dont think that makes any sense as the configure script should be included with every release tarball.

Mike, you're absolutely right here. The config files got into the dmapi tarball by mistake, sorry for this. I verified that neither xfsprogs nor xfsdump have any extra files. New (clean) dmapi tarball will be on the oss site shortly.

Felix

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#3 lore raw

Re: xfsprogs/xfsdump release process

Quoted 4 lines · Felix Blyakher

Mike, you're absolutely right here. The config files got into the dmapi tarball by mistake, sorry for this. I verified that neither xfsprogs nor xfsdump have any extra files. New (clean) dmapi tarball will be on the oss site shortly.

Please don't overwrite already uploaded tarballs. Let's make a 2.2.10 release instead. We might just use the Makepkgs script for it after fixing it. See the question and patch on the list for xfsprogs for that, haven't checked dmapi works right yet.

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#4 lore raw

Re: xfsprogs/xfsdump release process

Quoted 10 lines · Christoph Hellwig
Quoted 4 lines · Felix Blyakher

Mike, you're absolutely right here. The config files got into the dmapi tarball by mistake, sorry for this. I verified that neither xfsprogs nor xfsdump have any extra files. New (clean) dmapi tarball will be on the oss site shortly.

Please don't overwrite already uploaded tarballs. Let's make a 2.2.10 release instead. We might just use the Makepkgs script for it after fixing it. See the question and patch on the list for xfsprogs for that, haven't checked dmapi works right yet.

Didn't think that removing the unneeded files from the package justifies the version bump. It doesn't change anything for people who already downloaded unclean dmapi tarballs.
Though, if opinion on this matter is that strong, I'd definitely bump the version, and will use updated Makepkgs.

Felix

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#5 lore raw

Re: xfsprogs/xfsdump release process

Quoted 12 lines · On Monday 23 February 2009 11:10:44 Felix Blyakher wrote:
Quoted 10 lines · Christoph Hellwig
Quoted 4 lines · Felix Blyakher

Mike, you're absolutely right here. The config files got into the dmapi tarball by mistake, sorry for this. I verified that neither xfsprogs nor xfsdump have any extra files. New (clean) dmapi tarball will be on the oss site shortly.

Please don't overwrite already uploaded tarballs. Let's make a 2.2.10 release instead. We might just use the Makepkgs script for it after fixing it. See the question and patch on the list for xfsprogs for that, haven't checked dmapi works right yet.

Quoted 5 lines

Didn't think that removing the unneeded files from the package justifies the version bump. It doesn't change anything for people who already downloaded unclean dmapi tarballs.
Though, if opinion on this matter is that strong, I'd definitely bump the version, and will use updated Makepkgs.

the problem is for people (like Gentoo) who already fetched the tarball, hashed it, and posted the resulting URL/hash to their packaging systems ... -mike

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#6 lore raw

Re: xfsprogs/xfsdump release process

Quoted 13 lines · Mike Frysinger
Quoted 12 lines · On Monday 23 February 2009 11:10:44 Felix Blyakher wrote:
Quoted 10 lines · Christoph Hellwig
Quoted 4 lines · Felix Blyakher

Mike, you're absolutely right here. The config files got into the dmapi tarball by mistake, sorry for this. I verified that neither xfsprogs nor xfsdump have any extra files. New (clean) dmapi tarball will be on the oss site shortly.

Please don't overwrite already uploaded tarballs. Let's make a 2.2.10 release instead. We might just use the Makepkgs script for it after fixing it. See the question and patch on the list for xfsprogs for that, haven't checked dmapi works right yet.

Quoted 8 lines
Quoted 5 lines

Didn't think that removing the unneeded files from the package justifies the version bump. It doesn't change anything for people who already downloaded unclean dmapi tarballs.
Though, if opinion on this matter is that strong, I'd definitely bump the version, and will use updated Makepkgs.

the problem is for people (like Gentoo) who already fetched the tarball, hashed it, and posted the resulting URL/hash to their packaging systems ...

OK, that's definitely convincing.

Felix

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#7 lore raw

Re: xfsprogs/xfsdump release process

Quoted 20 lines · Felix Blyakher
Quoted 18 lines · Mike Frysinger
Quoted 17 lines · On Monday 23 February 2009 11:10:44 Felix Blyakher wrote:
Quoted 11 lines · Christoph Hellwig
Quoted 5 lines · Felix Blyakher

Mike, you're absolutely right here. The config files got into the dmapi tarball by mistake, sorry for this. I verified that neither xfsprogs nor xfsdump have any extra files. New (clean) dmapi tarball
will be on the oss site shortly.

Please don't overwrite already uploaded tarballs. Let's make a 2.2.10
release instead. We might just use the Makepkgs script for it after fixing it. See the question and patch on the list for xfsprogs for that, haven't checked dmapi works right yet.

Didn't think that removing the unneeded files from the package justifies the version bump. It doesn't change anything for people who already downloaded unclean dmapi tarballs.
Though, if opinion on this matter is that strong, I'd definitely bump the version, and will use updated Makepkgs.

Quoted 6 lines
Quoted 4 lines

the problem is for people (like Gentoo) who already fetched the tarball,
hashed it, and posted the resulting URL/hash to their packaging systems ...

OK, that's definitely convincing.

Just FWIW, Fedora does similar. Changing md5sums on a released, versioned tarball could set off all sorts of worries for distributions, in general...

-Eric

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#8 lore raw

Re: xfsprogs/xfsdump release process

Quoted 3 lines · Eric Sandeen

Just FWIW, Fedora does similar. Changing md5sums on a released, versioned tarball could set off all sorts of worries for distributions, in general...

Yeah. Guys, what about declaring the 3.0.0 releases officially botched and get 3.0.1 out next week? That should include all the small fixes we have out now and whatever small stuff comes up from distros trying to use it.

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#9 lore raw

Re: xfsprogs/xfsdump release process

In reply to Mike Frysinger
Quoted 9 lines · On Sunday 22 February 2009 15:39:25 Mike Frysinger wrote:
Quoted 3 lines · On Sunday 22 February 2009 13:48:49 Mike Frysinger wrote:

how are release tarballs created ? seems like there's an error in the process as the dmapi-2.2.9 contains files it shouldnt. for example, autom4te.cache/, include/builddefs, etc...

in a similar vain, every xfsdump/xfsprogs release has made people run autoconf first as the configure script is considered part of the distclean target in general. i dont think that makes any sense as the configure script should be included with every release tarball.

so how are release tarballs made ? i dont see a "dist" target or anything ... -mike

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#10 lore raw

Re: xfsprogs/xfsdump release process

Quoted 6 lines · Mike Frysinger
Quoted 5 lines · On Sunday 22 February 2009 15:39:25 Mike Frysinger wrote:
Quoted 3 lines · On Sunday 22 February 2009 13:48:49 Mike Frysinger wrote:

how are release tarballs created ? seems like there's an error in the process as the dmapi-2.2.9 contains files it shouldnt. for example, autom4te.cache/, include/builddefs, etc...

Quoted 6 lines
Quoted 4 lines

in a similar vain, every xfsdump/xfsprogs release has made people run autoconf first as the configure script is considered part of the distclean target in general. i dont think that makes any sense as the configure script should be included with every release tarball.

so how are release tarballs made ? i dont see a "dist" target or anything ...

The current ones were made using a hacked up release script form me. There's a Makepkgs script in the tarballs that generates better tarballs, but knowledge about it was lost in various transitions and it started to bitrot. I'm fixing it up so we can use it for the next release right now.

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#11 lore raw

Re: xfsprogs/xfsdump release process

Quoted 12 lines · On Tuesday 24 February 2009 13:44:05 Christoph Hellwig wrote:
Quoted 11 lines · Mike Frysinger
Quoted 9 lines · On Sunday 22 February 2009 15:39:25 Mike Frysinger wrote:
Quoted 3 lines · On Sunday 22 February 2009 13:48:49 Mike Frysinger wrote:

how are release tarballs created ? seems like there's an error in the process as the dmapi-2.2.9 contains files it shouldnt. for example, autom4te.cache/, include/builddefs, etc...

in a similar vain, every xfsdump/xfsprogs release has made people run autoconf first as the configure script is considered part of the distclean target in general. i dont think that makes any sense as the configure script should be included with every release tarball.

Quoted 8 lines
Quoted 2 lines

so how are release tarballs made ? i dont see a "dist" target or anything ...

The current ones were made using a hacked up release script form me. There's a Makepkgs script in the tarballs that generates better tarballs, but knowledge about it was lost in various transitions and it started to bitrot. I'm fixing it up so we can use it for the next release right now.

ok, as long as the tarball has a configure script :) -mike

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs