dparser
dparser copied to clipboard
jplevyak
Tarball 1.30 is broken
Hi!
The current tarball contains two extraneous entries, which are in addition wrong.
$ wget https://freefr.dl.sourceforge.net/dparser/d-1.30-src.tar.gz
--2019-01-08 06:45:03-- https://freefr.dl.sourceforge.net/dparser/d-1.30-src.tar.gz
Résolution de freefr.dl.sourceforge.net (freefr.dl.sourceforge.net)… 88.191.250.136, 2a01:e0d:1:8:58bf:fa88::1
Connexion à freefr.dl.sourceforge.net (freefr.dl.sourceforge.net)|88.191.250.136|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 239510 (234K) [application/x-gzip]
Sauvegarde en : « d-1.30-src.tar.gz »
d-1.30-src.tar.gz 100%[===================================================================================================================>] 233,90K --.-KB/s ds 0,05s
2019-01-08 06:45:04 (4,54 MB/s) — « d-1.30-src.tar.gz » sauvegardé [239510/239510]
$ tar tvf d-1.30-src.tar.gz | grep d/my
-rw-rw-r-- 0 jplevyak jplevyak 346 23 jan 2013 d/my.c
-rw-rw-r-- 0 jplevyak jplevyak 124 23 jan 2013 d/my.g
hrw-rw-r-- 0 jplevyak jplevyak 0 23 jan 2013 d/my.c link to d/my.c
hrw-rw-r-- 0 jplevyak jplevyak 0 23 jan 2013 d/my.g link to d/my.g
because of this, it cannot be easily extracted:
$ tar xf d-1.30-src.tar.gz
d/my.c: Can't create 'd/my.c'
d/my.g: Can't create 'd/my.g'
tar: Error exit delayed from previous errors.
Gads, that file is 5 years old. The current version is on github: https://github.com/jplevyak/dparser
I'll update the file and docs.
On Mon, Jan 7, 2019 at 9:48 PM Akim Demaille [email protected] wrote:
Hi!
The current tarball contains two extraneous entries, which are in addition wrong.
$ wget https://freefr.dl.sourceforge.net/dparser/d-1.30-src.tar.gz
--2019-01-08 06:45:03-- https://freefr.dl.sourceforge.net/dparser/d-1.30-src.tar.gz
Résolution de freefr.dl.sourceforge.net (freefr.dl.sourceforge.net)… 88.191.250.136, 2a01:e0d:1:8:58bf:fa88::1
Connexion à freefr.dl.sourceforge.net (freefr.dl.sourceforge.net)|88.191.250.136|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 239510 (234K) [application/x-gzip]
Sauvegarde en : « d-1.30-src.tar.gz »
d-1.30-src.tar.gz 100%[===================================================================================================================>] 233,90K --.-KB/s ds 0,05s
2019-01-08 06:45:04 (4,54 MB/s) — « d-1.30-src.tar.gz » sauvegardé [239510/239510]
$ tar tvf d-1.30-src.tar.gz | grep d/my
-rw-rw-r-- 0 jplevyak jplevyak 346 23 jan 2013 d/my.c
-rw-rw-r-- 0 jplevyak jplevyak 124 23 jan 2013 d/my.g
hrw-rw-r-- 0 jplevyak jplevyak 0 23 jan 2013 d/my.c link to d/my.c
hrw-rw-r-- 0 jplevyak jplevyak 0 23 jan 2013 d/my.g link to d/my.g
because of this, it cannot be easily extracted:
$ tar xf d-1.30-src.tar.gz
d/my.c: Can't create 'd/my.c'
d/my.g: Can't create 'd/my.g'
tar: Error exit delayed from previous errors.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jplevyak/dparser/issues/15, or mute the thread https://github.com/notifications/unsubscribe-auth/AARLoLPVHdzzjLQ-HwRe-roOrQ-WWkAbks5vBDEbgaJpZM4Z0z8n .
Yes, I can see that it's old, yet the releases on GitHub are even older. Do you mean that there won't be any releases in the future and that users are expected to pull master?
I can make a release, but the master is the stable.
On Wed, Jan 9, 2019 at 1:12 AM Akim Demaille [email protected] wrote:
Yes, I can see that it's old, yet the releases on GitHub are even older. Do you mean that there won't be any releases in the future and that users are expected to pull master?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jplevyak/dparser/issues/15#issuecomment-452624413, or mute the thread https://github.com/notifications/unsubscribe-auth/AARLoK6qWoRw9EUA1-A8QyMgDhZF4jV9ks5vBbJ9gaJpZM4Z0z8n .
The problem here is mainly distros. I arrived here because MacPorts relies on your releases, and it was stuck to 1.30, which is broken. I suppose MacPorts can build from a git repo, but it does not sound very sane to do that, that's too volatile. At least make tags. But releases is certainly the preferred option for distro maintainers.
I made a new release, and I'll check on MacPorts.
On Wed, Jan 9, 2019, 9:58 PM Akim Demaille <[email protected] wrote:
The problem here is mainly distros. I arrived here because MacPorts relies on your releases, and it was stuck to 1.30, which is broken. I suppose MacPorts can build from a git repo, but it does not sound very sane to do that, that's too volatile. At least make tags. But releases is certainly the preferred option for distro maintainers.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jplevyak/dparser/issues/15#issuecomment-452980280, or mute the thread https://github.com/notifications/unsubscribe-auth/AARLoJZjYu3GoRtvm58g_9WENXjEO7YDks5vBtaKgaJpZM4Z0z8n .