zip vs bz2 revisited

[Nick Hilliard]

Hello,

None of Flyspray releases 0.9.9.{3,4,5,5.1} were released with tarball
files.  Worse still, 0.9.9.5.1 has been packaged with a broken archiver
which uses "\" as the directory separator for the end-of-file zip contents
list, while it uses "/" as the separator for the internal file headers.
Among others, this breaks Info-ZIP, which is used widely on *nix systems

I just can't understand why people deliberately break standards by doing
stupid things like arbitrarily changing delimiters.  But there you go.

Could someone make a tar.bz2 file available from flyspray.org, please?  I
need to update the FreeBSD port and right now, I can't do this without
repackaging the 0.9.9.5.1 zipfile as a tarball, hosting it somewhere else
and pointing the FreeBSD port at that.

thanks very much,

Nick
[FreeBSD flyspray port maintainer]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "flyspray" group.
To post to this group, send email to flyspray@...
To unsubscribe from this group, send email to flyspray-unsubscribe@....
If you only wish to be informed about new flyspray releases, visit http://www.flyspray.org/download and subscribe to the flyspray-announce list.
For more options, visit this group at http://groups.google.com/group/flyspray?hl=en
-~----------~----~----~----~------~----~------~--~---

[Florian Schmitz]

There are auto-generated bz2s available:
http://snaps.flyspray.org/flyspray-0.9.9-latest.tar.bz2

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "flyspray" group.
To post to this group, send email to flyspray@...
To unsubscribe from this group, send email to flyspray-unsubscribe@....
If you only wish to be informed about new flyspray releases, visit http://www.flyspray.org/download and subscribe to the flyspray-announce list.
For more options, visit this group at http://groups.google.com/group/flyspray?hl=en
-~----------~----~----~----~------~----~------~--~---

[Nick Hilliard]

> There are auto-generated bz2s available:
> http://snaps.flyspray.org/flyspray-0.9.9-latest.tar.bz2

I'm aware of the snapshots, but I can't update the port using a source file
which changes every time someone commits a patch.  The FreeBSD ports system
uses SHA1 and MD5 checksums to source compare file sizes, and even if it
didn't, each port update is tested carefully to ensure that it works
correctly.  If the source file changed daily, then that testing would be
pointless.

Nick

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "flyspray" group.
To post to this group, send email to flyspray@...
To unsubscribe from this group, send email to flyspray-unsubscribe@....
If you only wish to be informed about new flyspray releases, visit http://www.flyspray.org/download and subscribe to the flyspray-announce list.
For more options, visit this group at http://groups.google.com/group/flyspray?hl=en
-~----------~----~----~----~------~----~------~--~---

[Cristian Rodriguez-2]

On Tue, May 27, 2008 at 1:51 PM, Nick Hilliard <nick@...> wrote:
>
>> There are auto-generated bz2s available:
>> http://snaps.flyspray.org/flyspray-0.9.9-latest.tar.bz2
>
> I'm aware of the snapshots, but I can't update the port using a source file
> which changes every time someone commits a patch...

I will try to fix this "packaging" problem as soon as possible, with a
definitive, automated  solution though



--
"Any fool can make things bigger, more complex, and more violent. It
takes a touch of genius -- and a lot of courage -- to move in the
opposite direction. -- Albert Einstein

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "flyspray" group.
To post to this group, send email to flyspray@...
To unsubscribe from this group, send email to flyspray-unsubscribe@....
If you only wish to be informed about new flyspray releases, visit http://www.flyspray.org/download and subscribe to the flyspray-announce list.
For more options, visit this group at http://groups.google.com/group/flyspray?hl=en
-~----------~----~----~----~------~----~------~--~---

[Nick Hilliard]

Cristian Rodriguez wrote:
> I will try to fix this "packaging" problem as soon as possible, with a
> definitive, automated solution though

Many thanks - much appreciated!

Nick



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "flyspray" group.
To post to this group, send email to flyspray@...
To unsubscribe from this group, send email to flyspray-unsubscribe@....
If you only wish to be informed about new flyspray releases, visit http://www.flyspray.org/download and subscribe to the flyspray-announce list.
For more options, visit this group at http://groups.google.com/group/flyspray?hl=en
-~----------~----~----~----~------~----~------~--~---

[Nick Hilliard]

Cristian Rodriguez wrote:
> I will try to fix this "packaging" problem as soon as possible, with a
> definitive, automated  solution though

Hi Cristian,

Do you have a time-to-fix for this?  I cannot release an upgraded port for
FreeBSD without a functional source package, and the current version in
FreeBSD has known security problems.  I can host a fixed source package
from a third party site without too much bother, but I prefer not to do
this for integrity reasons.

Nick

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "flyspray" group.
To post to this group, send email to flyspray@...
To unsubscribe from this group, send email to flyspray-unsubscribe@....
If you only wish to be informed about new flyspray releases, visit http://www.flyspray.org/download and subscribe to the flyspray-announce list.
For more options, visit this group at http://groups.google.com/group/flyspray?hl=en
-~----------~----~----~----~------~----~------~--~---