Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tagged release for 'syslinux'? #1

Open
boldandbusted opened this issue Oct 16, 2015 · 6 comments
Open

Tagged release for 'syslinux'? #1

boldandbusted opened this issue Oct 16, 2015 · 6 comments

Comments

@boldandbusted
Copy link

Howdy. I'm working on packaging msed (and, therefore, 'syslinux') for Gentoo. It's a bit easier on us if you create a tagged release of the 'syslinux' package so that some of our automagic versioned downloads can work. As an example, we have built-in constructs in Portage like so:

https://github.com/Drive-Trust-Alliance/sedutil/releases/download/${P}.tar.gz

Where ${P} is the version of the release. I'd like to do something similar for the PBA Syslinux stuffs, and, us being Gentoo, we of course prefer to compile it. :)

Thanks! Please let me know if I've left out important details.

@r0m30
Copy link
Contributor

r0m30 commented Oct 16, 2015

Looks like ALL the tags are gone :-(
When I try and push them I'm getting an unpack error. I think that recreating the repo may be easier than getting into the magic of git repair commands. If I have to redo this I'll post another message here before I do.

@r0m30
Copy link
Contributor

r0m30 commented Oct 16, 2015

I'm going to have to work on this more. I'm getting an error when I try and push the tags to github but it all works locally using file specs. When I look at the object it is complaining about I don't see the missing space it's complaining about.

@boldandbusted
Copy link
Author

No problem! Git can be a bear. :)

@r0m30
Copy link
Contributor

r0m30 commented Oct 16, 2015

This looks like one of those "this was always broken and now we fixed it" things. The tags from when they converted to git were broken but until now they still unpacked properly, so on the older repo they pushed fine but when creating this new repo they bombed out, I ended up deleting all pre 2005 tags an it looks like the rest of the tags are there now.

I don't think this will cause any problems for the pba.

Portage away......

@r0m30
Copy link
Contributor

r0m30 commented Oct 27, 2015

@boldandbusted Is it necessary to keep the tags in sync for your packaging? Put another way would it be best for you if I always tagged syslinux and sedutil the same? The syslinux repo will not be updated nearly as often as sedutil but I can tag it the same if required.

@boldandbusted
Copy link
Author

That would make things quite easy on my end. I'd never have to worry
about 'hard-coding' a specific version of syslinux while packaging msed.

Thanks!

Jesse Adelman
SF, CA

On Mon, Oct 26, 2015, at 05:13 PM, r0m30 wrote:

@boldandbusted Is it necessary to keep the tags in sync for your
packaging? Put another way would it be best for you if I always tagged
syslinux and sedutil the same? The syslinux repo will not be updated
nearly as often as sedutil but I can tag it the same if required.


Reply to this email directly or view it on GitHub:
#1 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants