Re: [DNG] eudev status
Anto, I just compiled, packaged (jessie, amd64), installed and tested your (unmodified) eudev and gudev sources. First I installed the debs to my current live-image chroot. The rebuilt image boots, runs and behaves normally, can't see any problem with it. Therefore the initramfs hooks are there and doing their job. I then installed to my current running system. No issues with the upgrade. Used dpkg -i, first libudev1 then udev. It's all good so far. Your version is current (I did not maintain mine), has an organised git system and does actually work so I will support yours in future. Please do post the deb packages. Thanks Anto, you did a great job. Next.. consolekit2? http://exegnulinux.net/nosystemd/pool/main/c/consolekit/ On 25/12/2016, Anto wrote: > > On 24/12/16 22:17, David Hare wrote: >>> Thanks David. Do you maintain the source of your eudev package on a git >>> repository? If so, would it be possible to share that with us? >>> >> No. All there is are the debs and sources posted earlier. It's really >> a one-off, I don't have the required time and skills to actually >> "maintain" it. >> >> antiX have also packaged and tested eudev, probably worth a look there >> too. >> >> Anto, I look forward to testing your eudev packages! >> >> D >> > Hello David, > > As I previously mentioned, I am not a software developer. And my > knowledge and experience in Debian packaging is very limited. So it > would be great if I could have comparison of eudev source, especially > the debian build script, as I am not sure if I have done the packaging > correctly. If you don't have it on any public git repository, I guess I > just have to diff your source against mine then. > > I have been using eudev on my 2 laptops, 1 Xen based VPS and 1 KVM based > VPS since May last year. So I have passed the testing stage since then. > But I am not sure if that would work too on other setup. > > I have just merged the updates on https://github.com/gentoo/eudev into > mine on https://github.com/anto/eudev/releases. > > I already compiled and installed them on the PC that I am using writing > this email now and on my KVM VPS. The screenshots of the installation on > my PC are on > https://minifora.eu/public/devuan/images/eudev_3.2.1_installation_on_hp8530w_25Dec2016_1.png > > and > https://minifora.eu/public/devuan/images/eudev_3.2.1_installation_on_hp8530w_25Dec2016_2.png. > > And the screenshots of the installation on my KVM VPS are on > https://minifora.eu/public/devuan/images/eudev_3.2.1_installation_on_KVM_VPS_25Dec2016_1.png > > and > https://minifora.eu/public/devuan/images/eudev_3.2.1_installation_on_KVM_VPS_25Dec2016_2.png. > > I have also updated the corresponding libgudev for my laptops, > https://github.com/anto/libgudev/releases. > > I can put the pre-compiled debian package in my web server if anyone > interested to try it. I only have them compiled for x86_64 and i686 > platforms though. > > Cheers, > > Anto > > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] eudev status
On 26/12/16 15:48, David Hare wrote: Anto, I just compiled, packaged (jessie, amd64), installed and tested your (unmodified) eudev and gudev sources. First I installed the debs to my current live-image chroot. The rebuilt image boots, runs and behaves normally, can't see any problem with it. Therefore the initramfs hooks are there and doing their job. I then installed to my current running system. No issues with the upgrade. Used dpkg -i, first libudev1 then udev. It's all good so far. Your version is current (I did not maintain mine), has an organised git system and does actually work so I will support yours in future. Please do post the deb packages. Thanks Anto, you did a great job. Next.. consolekit2? http://exegnulinux.net/nosystemd/pool/main/c/consolekit/ Hello David, You are welcome. I am glad if you found it useful.And thanks a lot for sharing your experience. My main intention to put it on a public git repository is to make it easier for the professionals to fork or pull it into a git repository and maintain it, instead of being maintained by an amateur like me. In regards the deb packages, I actually prefer not to provide them in order to minimise the risk of breaking somebody else's PC. As you know, unless users read the debian/control file and manually install all dependencies prior to installing eudev, dpkg --install will not pull them unlike apt-get install.So I think by forcing the users to compile it, they will have to install those dependencies which I think is safer. I have also put the orig and debian tarballs on https://github.com/anto/eudev/releases/tag/v3.2.1-1 and https://github.com/anto/libgudev/releases/tag/v230-2.2. So users who are interested to try can just do for instance the following to compile eudev package: $ tar xJf eudev_3.2.1.orig.tar.xz $ tar xJf eudev_3.2.1-1.debian.tar.xz $ mv debian eudev-3.2.1/ $ cd eudev-3.2.1 $ dpkg-buildpackage -us -uc At this point, the users who didn't install the build dependencies will get errors. I hope that theywouldrealise that they also have to install package dependencies before installing the deb packages that they need using dpkg --install. Yes. After I had eudev running, a part from consolekit I also stripped acpid, dbus, kmod, udisks2, upower, and some other packages from anything related to systemd. The list is too long for me to maintain so I didn't upgrade them until now. I just regularly check Devuan repository for newer versions. Cheers, Anto ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] eudev status
On 24/12/16 12:19, Jaromil wrote: dear David, Anto and others On Fri, 23 Dec 2016, David Hare wrote: Anto, you are the 4th to attempt eudev packaging (including me). In case you want to shrink down on the duplicate effort, I'd be happy to create a git repository in devuan-packages and give all your users maintainer access. This will also give you all the possibility to trigger builds on Devuan's CI, a procedure which is now well documented. Perhaps is too early as we are still rolling out jessie, but it sounds like something quite appropriate for ascii's development cycle. ciao Ciao Jaromil, Thanks a lot for the offer.However, no offence but wouldn't it be better if we focused on the resources for the development of vdev? I am using eudev as that is the most viable alternative for me until now. But I am afraid at one point, it would be hard to extract some features from systemd-udev for eudev due to format differences or what ever would that be. So I am afraid later on eudev will not be able to manage new devices. I think vdev is still the best alternative. I was quite pessimistic on the progress of vdev development after Jude mentioned that he hasno spare time anymore to work on it. But looking at the most recent activities onhttps://git.devuan.org/unsystemd/vdev/activity, it looks like it is gaining momentum again.So I am looking forward to test the Devuan package of vdev. Cheers, Anto ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] eudev status
Yes Provides, Replaces and Breaks in the correct combination will ensure both complete replacement without recompiling depending packages. Ideally we should also apply those labels also to the systemd-udev package to ensure a complete switching between as well as extend the test suite to ensure the switching between them is tested and works properly too. On 25 December 2016 9:57:38 AM NZDT, Svante Signell wrote: >On Sat, 2016-12-24 at 18:38 +0100, Anto wrote: >> Hello Hendrik, >> >> I think that was the idea of Jaret to change all package names into * >> eudev*, instead of keeping them the same as Gentoo does. But I could >> never made it properly working as a lot of packages still depend on >> mostly libudev. So I just followed Gentoo's approach in which we have >> to choose either to install udev or eudev, even both use the same >> package name. Perhaps if I would recompile all of the packages to >> make them depend on libeudev, it should work. But due to my lack of >> knowledge and experience on Debian packaging, I didn't dare to start. > >Hi, > >Isn't the Debian package Depends: Replaces: and Conflicts: exactly >designed for that? >___ >Dng mailing list >Dng@lists.dyne.org >https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Sent from my Android device with K-9 Mail. Please excuse my brevity.___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] apt configuration and repositories
Hi Massimiliano, On 2016-12-20 22:12, Massimiliano Baldinelli wrote: > Since the switch from Stretch to Ascii I noticed the lack of the long > packages descriptions in aptitude, [...] Devuan repositories still lacks Contents and translation files [1]. I am working around this by adding Debian sources and pinning them to -1 priority: Package: * Pin: release o=Debian Pin-Priority: -1 Package: * Pin: release o=Debian Backports Pin-Priority: -1 1: https://git.devuan.org/devuan/devuan-project/issues/75 Petr ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
