dmapi-2.2.9 release

dmapi-2.2.9 release

[Mike Frysinger]

[-- Attachment #1.1: Type: text/plain, Size: 195 bytes --]

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...
-mike

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

xfsprogs/xfsdump release process

[Mike Frysinger]

[-- Attachment #1.1: Type: text/plain, Size: 539 bytes --]

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

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfsprogs/xfsdump release process

[Felix Blyakher]

On Feb 22, 2009, at 2:39 PM, Mike Frysinger wrote:

> 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
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfsprogs/xfsdump release process

[Christoph Hellwig]

On Sun, Feb 22, 2009 at 11:00:45PM -0600, Felix Blyakher wrote:
> 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
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfsprogs/xfsdump release process

[Felix Blyakher]

On Feb 23, 2009, at 1:22 AM, Christoph Hellwig wrote:

> On Sun, Feb 22, 2009 at 11:00:45PM -0600, Felix Blyakher wrote:
>> 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
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfsprogs/xfsdump release process

[Mike Frysinger]

[-- Attachment #1.1: Type: text/plain, Size: 1190 bytes --]

On Monday 23 February 2009 11:10:44 Felix Blyakher wrote:
> On Feb 23, 2009, at 1:22 AM, Christoph Hellwig wrote:
> > On Sun, Feb 22, 2009 at 11:00:45PM -0600, Felix Blyakher wrote:
> >> 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.

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

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfsprogs/xfsdump release process

[Felix Blyakher]

On Feb 23, 2009, at 10:25 AM, Mike Frysinger wrote:

> On Monday 23 February 2009 11:10:44 Felix Blyakher wrote:
>> On Feb 23, 2009, at 1:22 AM, Christoph Hellwig wrote:
>>> On Sun, Feb 22, 2009 at 11:00:45PM -0600, Felix Blyakher wrote:
>>>> 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.
>
> 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
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfsprogs/xfsdump release process

[Eric Sandeen]

Felix Blyakher wrote:
> On Feb 23, 2009, at 10:25 AM, Mike Frysinger wrote:
> 
>> On Monday 23 February 2009 11:10:44 Felix Blyakher wrote:
>>> On Feb 23, 2009, at 1:22 AM, Christoph Hellwig wrote:
>>>> On Sun, Feb 22, 2009 at 11:00:45PM -0600, Felix Blyakher wrote:
>>>>> 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.
>> 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
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfsprogs/xfsdump release process

[Christoph Hellwig]

On Mon, Feb 23, 2009 at 01:29:55PM -0600, Eric Sandeen wrote:
> 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
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfsprogs/xfsdump release process

[Mike Frysinger]

[-- Attachment #1.1: Type: text/plain, Size: 681 bytes --]

On Sunday 22 February 2009 15:39:25 Mike Frysinger wrote:
> 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

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfsprogs/xfsdump release process

[Christoph Hellwig]

On Tue, Feb 24, 2009 at 10:05:48AM -0500, Mike Frysinger wrote:
> On Sunday 22 February 2009 15:39:25 Mike Frysinger wrote:
> > 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 ...

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
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfsprogs/xfsdump release process

[Mike Frysinger]

On Tuesday 24 February 2009 13:44:05 Christoph Hellwig wrote:
> On Tue, Feb 24, 2009 at 10:05:48AM -0500, Mike Frysinger wrote:
> > On Sunday 22 February 2009 15:39:25 Mike Frysinger wrote:
> > > 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 ...
>
> 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
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs