You are not logged in.
@x33a: Thank you!
Offline
@Lone_Wolf: Thank you. It seems like apg packages are more up to date, but less complete. Artoo's didn't build for me without several tweaks - sha2sums, conflicts, etc.
I guess I'll have to "roll my own", based probably on apg's packages.
Yeah, I noticed checksums, and will update soon. I have been busy with other stuff unfortunately.
Except the openrc-base package, the other packages grab directly the scripts from gentoo, and do fix them to suit arch linux.
Be aware, the source files will not be altered, the fixing will take place in the pkg folder, so that the user maintains all downloaded unaltered scripts in /src(can be set in /etc/makepkg.conf). However, this screwed up the checksums somehow.
My packages all conflict with apq's, due to different config locations in /etc. You can't mix them, to avoid trouble. But, my openrc-base package uses by default a more powerful and feature rich network implementation. If you have more than one network interface, then netifrc(default in openrc-base) is probably the better choice. Of course you can easily tweak both, my and apq build.
PS: What scripts are outdated? What scripts conflict for you? Have you noticed some?
As far as help, the gentoo help is best place to go for my packages.
eg:
https://wiki.gentoo.org/wiki/OpenRC
or
http://www.gentoo.org/doc/en/handbook/h … xml?part=4
Last edited by artoo (2014-02-25 22:02:09)
Offline
PS: What scripts are outdated? What scripts conflict for you? Have you noticed some?
For the scripts, I mostly noticed dependency problems (like the dependency on dbus-openrc), and outdated sha256sums. I'll try and go through the whole install again, this time taking more notes.
One thing I recall was that for dhcp the PKGBUILD mentions a non-existing script file var - _Idhcp3.
Offline
artoo wrote:PS: What scripts are outdated? What scripts conflict for you? Have you noticed some?
For the scripts, I mostly noticed dependency problems (like the dependency on dbus-openrc), and outdated sha256sums. I'll try and go through the whole install again, this time taking more notes.
One thing I recall was that for dhcp the PKGBUILD mentions a non-existing script file var - _Idhcp3.
Thanks, I will check dhcp abd look into dbus-openrc. You still have systemd installed, right? Or do you use dbus-eudev? Dbus-eudev does not provide the script, it is only dbus compiled against eudev, to make the scripts run without systemd, you would still need dbus-openrc.
As for checksums, and updated scripts, I went through them yesterday, and corrected/updated the builds.
I will likely update the AUR later the day.
Last edited by artoo (2014-02-26 11:21:56)
Offline
Thanks, I will check dhcp abd look into dbus-openrc. You still have systemd installed, right? Or do you use dbus-eudev? Dbus-eudev does not provide the script, it is only dbus compiled against eudev, to make the scripts run without systemd, you would still need dbus-openrc.
As for checksums, and updated scripts, I went through them yesterday, and corrected/updated the builds.
I will likely update the AUR later the day. :)
I still have systemd, will install eudev only after I have a fully working openrc. I'll try again later today, as soon as I see the updated scripts showing up.
I remembered a build conflict - ntp versus openntpd and a missing conflict: lm-sensors and lm_sensors-openrc both own /etc/conf.d/sensord
Offline
artoo wrote:Thanks, I will check dhcp abd look into dbus-openrc. You still have systemd installed, right? Or do you use dbus-eudev? Dbus-eudev does not provide the script, it is only dbus compiled against eudev, to make the scripts run without systemd, you would still need dbus-openrc.
As for checksums, and updated scripts, I went through them yesterday, and corrected/updated the builds.
I will likely update the AUR later the day.
I still have systemd, will install eudev only after I have a fully working openrc. I'll try again later today, as soon as I see the updated scripts showing up.
I remembered a build conflict - ntp versus openntpd and a missing conflict: lm-sensors and lm_sensors-openrc both own /etc/conf.d/sensord
I will check the time daemons again, and look into sensors. Thx for reporting.
I was thinking about a script, which checks gentoo for updated scripts to make life easy.
Edit: I can't find conflicts with time daemons, but the dbus problem occurs, if you don't have dbus-openrc from openrc-sys-split installed, I don't know if I should make a dependency for a split pkg in AUR.
The split sys pkg should be first to install, it also contains device-mapper, required by other packages.
The pkgbuild/packages work much better if you simply put the package in a local repo. You can do more pacman magic with them if in repo, such as groups.
Last edited by artoo (2014-02-26 21:43:06)
Offline
Hi,
I've built your new packages today from aur. Will probably follow your suggestion of adding them to a local repo later.
Here are the issues I found:
- openrc-misc-split depends on fcron, which conflicts with cronie (dependency of openrc-sys-split) and cronie-openrc
- openrc-misc-split depends on openntpd, which conflicts with ntp (dependency of openrc-net-split) and ntp-openrc
- openrc-misc-split installs a ntpd script, but the instructions are to "rc-update add openntpd default"
- openrc-net-split depends on ntp, which conflicts with openntpd (dependency of openrc-misc-split) and with openntpd-openrc
- openrc-sys-split depends on cronie, which conflicts with fcron (dependency of openrc-misc-split) and fcron-openrc
- openrc-sys-split installs scripts lvm, lvm-monitoring and lvmetad, but instructs to "rc-update add lvm2 default"
Seems like most stuff is now fixed, so in a couple of days I'll probably install eudev and remove systemd.
Offline
Hi,
I've built your new packages today from aur. Will probably follow your suggestion of adding them to a local repo later.
Here are the issues I found:
Why have the openrc-*-split PKGBUILDs makedepends at all? They only patch textfiles and package them. Only makepkg, coreutils and sed are makedepends.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
jbernardo wrote:Hi,
I've built your new packages today from aur. Will probably follow your suggestion of adding them to a local repo later.
Here are the issues I found:Why have the openrc-*-split PKGBUILDs makedepends at all? They only patch textfiles and package them. Only makepkg, coreutils and sed are makedepends.
Right, but I try to comply with namcap.
And namcap demands these makedepends.
Will I go against namcap advise? Not sure.
Last edited by artoo (2014-02-28 15:56:10)
Offline
Hi,
I've built your new packages today from aur. Will probably follow your suggestion of adding them to a local repo later.
Here are the issues I found:
- openrc-misc-split depends on fcron, which conflicts with cronie (dependency of openrc-sys-split) and cronie-openrc
- openrc-misc-split depends on openntpd, which conflicts with ntp (dependency of openrc-net-split) and ntp-openrc
- openrc-misc-split installs a ntpd script, but the instructions are to "rc-update add openntpd default"
- openrc-net-split depends on ntp, which conflicts with openntpd (dependency of openrc-misc-split) and with openntpd-openrc
- openrc-sys-split depends on cronie, which conflicts with fcron (dependency of openrc-misc-split) and fcron-openrc
- openrc-sys-split installs scripts lvm, lvm-monitoring and lvmetad, but instructs to "rc-update add lvm2 default"Seems like most stuff is now fixed, so in a couple of days I'll probably install eudev and remove systemd.
Thanks.
Bear with me, the .install stuff is on the todo list asap.
Edit: The conflicts are right as they are, except I overlooked something.
openntpd conflicts with ntp, fcron conflicts with cronie, so do the openrc pkgs.
yaourt should ask the user to uninstall the conflicting package before proceeding.
Last edited by artoo (2014-02-28 16:39:38)
Offline
yaourt should ask the user to uninstall the conflicting package before proceeding.
You shouldn't rely on yaourt to do anything. Always plan with makepkg in mind
Offline
artoo wrote:yaourt should ask the user to uninstall the conflicting package before proceeding.
You shouldn't rely on yaourt to do anything. Always plan with makepkg in mind
I don't. I was addressing the poster's issue with conflicts in AUR.
I just ran a test on a new set up arch system in vbox. everything works on user end.
Makepkg does work, surely.
Btw, what's you view on the makedeps vs namcap?
Offline
Btw, what's you view on the makedeps vs namcap?
I am not too sure. From a puritan point of view, heeding to namcap's advice seems sane though.
Offline
artoo wrote:Btw, what's you view on the makedeps vs namcap?
I am not too sure. From a puritan point of view, heeding to namcap's advice seems sane though.
Yeah, maybe someone involved with AUR or packaging standards could help.
Progandy raised a good point I forgot about.
Atm, the AUR doesn't do sanity checks, does it?
Offline
No, I don't think the AUR checks for any such stuff.
Offline
Warning: Packages in the AUR assume the base-devel group is installed, and AUR packages will not list members of this group as dependencies even if the package cannot be built without them. Please ensure this group is installed before complaining about failed builds.
example : sed is in base-devel group, so it's not needed to include it in depends/makedepends .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
What is the opinion on lvm & raid support, in terms of scripts?
On a normal arch kernel system, these things get activated by initramfs/hooks.
Are these needed? Any use cases on arch?
I personally don't make use of the lvm scripts to get my lvm activated.
Last edited by artoo (2014-02-28 21:26:16)
Offline
Hi all
I will plan to replace the systemd to openrc , some weeks ago tried but cannot set the eudev correctly.
What packages need from AUR and how to remove systemd (with udev) formely unnecessary for me?
Offline
Hi all
I will plan to replace the systemd to openrc , some weeks ago tried but cannot set the eudev correctly.
What packages need from AUR and how to remove systemd (with udev) formely unnecessary for me?
There are two packages, eudev and eudev-git.
If you prefer a development version, use eudev-git, if you want a more stable version, use eudev.
Its pretty straight forward.
Install eudev, which removes systemd, and install {dbus,upower,udisks2}-eudev, to get the services started.
You can additionally install eudev-openrc, which provides a postmount script for eudev.
Offline
There are two packages, eudev and eudev-git.
If you prefer a development version, use eudev-git, if you want a more stable version, use eudev.Its pretty straight forward.
Install eudev, which removes systemd, and install {dbus,upower,udisks2}-eudev, to get the services started.
You can additionally install eudev-openrc, which provides a postmount script for eudev.
what about mkinitcpio.conf or rc.conf settings ?
Offline
There are two packages, eudev and eudev-git.
If you prefer a development version, use eudev-git, if you want a more stable version, use eudev.Its pretty straight forward.
Install eudev, which removes systemd, and install {dbus,upower,udisks2}-eudev, to get the services started.
You can additionally install eudev-openrc, which provides a postmount script for eudev.what about mkinitcpio.conf or rc.conf settings ?
As far as I know, you need nothing to change on that front.
But, it depends a bit on your setup. If you use lvm, you might have to revert to a non lvmetad activation, but that is not a eudev issue, rather than mkinitcpio hook issue. Its on my to do test list, since lvmetad did not work with my old crashed harddrive, but it does with the new one.
Last edited by artoo (2014-03-02 15:26:25)
Offline
Have installed openrc, eudev and dbus-nosystemd from aur (and arch-services). Dbus is not starting from what I can tell so connman is complaining. Can see script for dbus but not sure how you get it started (or check if it is running) am assuming I need to rc-update?
Mr Green
Offline
Yeah dbus needs to be in the default runlevel. Is it present there?
Offline
Now that I have added it does seem to be working now. Did change a line in init.d so /run/dbus gets created. Networking is next on my list. Connman seems hit and miss at the moment, for a wired dhcp connection looking for a simple solution.
Thanks for the heads up..
Mr Green
Offline
Hello,
I have been working with Mr. Green over at ArchBang! and because much of the work we are doing applies to Arch as well I have joined the forums. I just added an article on eudev to the Arch Wiki, https://wiki.archlinux.org/index.php/Eudev
And I plan to help flesh out other articles soon on there so my fellow Arch/Archbang users who, like myself, are interested in alternatives have decent documentation to follow. I encourage others to follow suit if you have something to share.
To answer Mr. Green's question I just added dhcpcd to the default runlevel like so,
# rc-update add dhcpcd default
That works to start dhcp, so that works. netcfg is what I use for network management on my laptop, though.
Offline