[SOLVED] 2.1 -> 2.1.2: Custom Repository not working
-
@cmb:
Nothing has been changed re: support of custom package repos. 2.1.2 is the same in that regard as every past release. If your custom package repo doesn't work, it's because it's broken.
The repo is working perfectly with 2.1 and several pfSense boxes… How could it be broken?
Do I need any changes in the repo for newer releases? -
Do I need any changes in the repo for newer releases?
That is a classified information…
Mama's gonna check out all your girl friends for you
Mama won't let anyone dirty get through
Mama's gonna wait up till you get in
Mama will always find out where
You've been
Mamma's gonna keep baby healthy and clean…P.S. Secure boot coming soon. :P
-
That is a classified information…
I see…. It seems that you have some negative impressions :o
Anyway. The topic is serious and I would be very happy to get these classified informations ;)
-
Yeah, this topic is serious, however the "owner" of this (long ago forked community) project has chosen to behave like a moron and there's apparently nothing to change his mind. Maybe he is at least ashamed of himself and so he has kept hit trap shut for weeks and pretends to be invisible.
Other than that, you are wasting your time with creating your own packages. Instead, you should create your own project.
-
Other than that, you are wasting your time with creating your own packages. Instead, you should create your own project.
I think this is a bit more than people with custom repositories need… For myself it would be enough, if I could add PBI's manual in the GUI without using any repository. But that is is OT.
I will have a look at the source and try to get some more information...
-
Ok… This problem is just one of "please don't do this in the same main version of the product"... :o
On 2.1:
You need the repo to have a server root with 2 subdirectories and nothing else: "/pfSense" and "/packages" (both in the root of repo)http://your-repo.domain.tld/pfSense http://your-repo.domain.tld/packagesOn 2.1.2 (don't know for 2.1.1):
You need the "/pfSense" content be the root and a subdirectory "/packages".http://your-repo.domain.tld/ http://your-repo.domain.tld/packagesSmall change, but big impact. Optionally you can use https of course…
Would be nice to see this one in the documentation. -
On 2.1.2 (don't know for 2.1.1):
You need the "/pfSense" content be the root and a subdirectory "/packages".http://your-repo.domain.tld/ http://your-repo.domain.tld/packagesHi Hobby-Student
I did that but my two pfSense updated to 2.1.2 still said "Unable to communicate with X.X.X.X. Please verify DNS and…" I changed $path_to_files in xmlrpc.php and correct '../packages/' but not work. ¿Any ideas?
-
…I changed $path_to_files in xmlrpc.php and correct '../packages/' but not work. ¿Any ideas?
xmlrpc.php, line 45:
$path_to_files = './xmlrpc/';xmlrpc.php, line 124:
$path_to_files = './packages/';This should do the trick.
-
This should do the trick.
Yes, I did the "./packages/" change and the other no needed because always work with "./xmlrpc/" and have communication problem yet. No more changes needed in other files?
-
Yes, I did the "./packages/" change and the other no needed because always work with "./xmlrpc/" and have communication problem yet. No more changes needed in other files?
Was the repo working on 2.1?
Have you set right permissions on your webserver?
.htaccess as mentioned in the official wiki?
is test.php and xmlrpc_tester.php working? (just open in browser and see if it's reporting something)sure, that the "old" folder "pfSense" is now the root of your server?
http://repo.domain.tld/xmlrpc.php http://repo.domain.tld/xmlrpc/ http://repo.domain.tld/packages/ (and so on) -
Oh, yeah the base URL also changed when we moved from www.pfsense.com to packages.pfsense.org, 2.1.1 and later do not look in /pfSense/ by default for packages, rather in the root.
-
@cmb:
Oh, yeah the base URL also changed when we moved from www.pfsense.com to packages.pfsense.org, 2.1.1 and later do not look in /pfSense/ by default for packages, rather in the root.
Could this info please be added to the wiki?
-
My advice is to ignore doktornotor. He claims to be trained as a lawyer, but seemingly the only benefit he gained from law school was learning to act poorly in public.
The fact that he doesn't practice what he learned should give anyone pause.
As cmb related, we moved the repositories to their own server. Anyone running an official build likely followed without noticing.
We never signed up to supporting custom repos, etc.
-
@gonzopancho:
My advice is to ignore doktornotor. … We never signed up to supporting custom repos, etc.
Where's the -tools repo? Will you finally either publish that or stop misadvertising this as open-source? Perhaps FTC might be interested as well. ::)
-
As I've explained elsewhere, I don't respond to doktornotor or other abusive asshole like him (her? it?)
-
Where's the -tools repo?
-
doktornotor; we are looking forward to hear about your own opensource work (like pfsense) as soon as possible, untill then please at least be kind enough to shut up and respect theese nice people, they are not obligated to do anything you or anyone required
-
they are not obligated to do anything you or anyone required
Actually, they are as long as they advertise this as open source. They of course are free to stop this deceptive advertising.
P.S. As for "your own" - this is a m0n0wall fork based on FreeBSD. Not something written from scratch by ESF. And those "nice people" get as much respect as they deserve. In case of certain Jim T. who happens to own the Netgate/ESF thing, the respect has currently dropped below freezing point. ::)
-
Unlike doktornotor, Jim Thompson doesn't hide behind a pseudonym.
-
You should stick with washing the bottles, and keep WAY away from any customer/public relations. Frankly, your today's posts on this forum could be used as classic learning materials in a "How NOT to EVER deal with OSS community" course. ::)