inconsistent rebuild; exiting ravenadm; linux still broken - unsupported

[dan_pa...@rdsor.ro]

John,

it's that time of the year when I do a periodic check on ravenports

1. Building a package with ravenadm (pkg-bsd in this case) resulted in
27 packages being built, as required. Reissuing ravenadm build pkg-bsd
right after results in the same 27 packages being rebuilt, although
nothing changed. ravenadm (or most liekly pkg behind it) complained
about package options being changed. which they where not, of course,
since nothing changed.

2. ctrl-c. seems that exiting with Ctrl+C ravenadm do not perform any
cleanup of the mounts it used to serve the build chroots. any way to
exit ravenadm gratuitously except for waiting to finish building a
gazillion packages?

3. Linux support. Linux is still unsupported as of mid 2019. pkg is
broken on all linuxes I tried it. And since ravenadm relays on pkg, it
is broken too. Now, this situation is persistent by almost 2 years. At
one time you said you will add support for a package manager which
actually works on linux , prolly apt / dpkg combo. But that was long
ago, more than 6 months. My question is, do you still want to support
Linux with Ravenports, or only BSD derivatives and Solaris ? Cause in
current state it is unusable in Linux for anything but toying arround .

With thanks, Dan

[John Marino]

on 1), there's not enough information here.  There are logs starting with "0" in the log directory (e.g. 00_*, 01_*, etc) that have information why all packages are being rebuilt, particularly the one named "06_obsolete_packages.log".

2).  Control-C was never supported.  It's Control-Q.  Perhaps you mis-remembered?  It should be documented in the man page.

3) My plan is to fork pkg (and rename it) and try to track down where the bug is and fix it.

Supporting dpkg is still on a list, but not really very high.  Linux support is a priority.  Personally, on the linuxen I'm using, pkg works if the command is reissued.  I understand that on your linuxen, the broken commands never work even after reissue.  

I've had a lot of road bumps in my private life that have taken me away from Ravenports in general and linux in particular.  I hope that changes in the next few months.

John

--
You received this message because you are subscribed to the Google Groups "Ravenports" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravenports+...@googlegroups.com.
To post to this group, send email to raven...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ravenports/223dd2fe99ea243804c0aa722375b170%40rdsor.ro.
For more options, visit https://groups.google.com/d/optout.

[dan_pa...@rdsor.ro]

Thank you .

> information why all packages are being rebuilt, particularly the one
> named "06_obsolete_packages.log".

Im not giving a dog crap about dpkg to be honest, I just need the
package manager to work reliably. I like FreeBSDs pkg and Im used with
it since I have some FreeBSD machines, and I couldn't be more happy to
have it working. Im not really looking forward to debug pkg , maybe you
do not look forward to this too, but in the end if it gets fixed IMO is
better than supporting multiple package managers. I'm a big fan of one
consistent interface than shitloads of choices

> Personally, on the linuxen I'm using, pkg works if the command is
> reissued. I understand that on your >linuxen,

In my linuxen machines issuing pkg is a lottery. Reissuing it one or
more times usually gets the package installed. Once in past I got the
pkg database corrupted. But it is only half of the problem. ravenadm
itself relays on pkg to add / remove packages in the build chroot and
sometimes pkg fails there too. This, this is annoying as hell for me.


> I've had a lot of road bumps in my private life that have taken me..

Sorry to hear that man. I just hope you and your loved ones are OK.

[John Marino]

Hey Dan,

I've been busy forking pkg:

https://github.com/jrmarino/ravensw 

It currently builds without error on solaris and linux.

I'm still testing it for functionality (e.g. no regressions) but so far I'm not getting those segfaults.

While I was cleaning up the code, I found a couple of bugs that might have caused them on the stock package.

Once I'm satisfied it's working on the 4 major platforms, I'll update all the bootstraps to move ravenports away from pkg and to ravensw (along with instructions on how to make the transition)

I also have to go through all the man pages in greater detail to make them work for ravenports, and maybe check out some commands that assume /usr/ports and see if I can get them to work on ravenports formats.

Anyway, it's looking good so far.

John

[Dan Partelly]

Hey John,

Didn't checked Ravenports in a pretty long time. Much to my surprise I see that you decided to rewrite pkg. this is good news. Prolly it wont have to many bugs , ravenadm was remarkable at debut . You are a pretty prolific man.

What is the current state of the tool ?

DO you have a link on a prebuilt binary for ravensw, Linux X86_64 and the manifest files ? The old Linux  boostrap link doesnt seem to work anymore, not fond erro,  so cant use pkg static to fetch ravensw and run some tests with  it, regardless of the state ?