Re: [DNG] my first two packages
il devuanizzato Aitor il 18-01-20 11:48:58 ha scritto: My short answer for now: - Use lowercase letters for the debian folder. A DEBIAN folder with uppercase letters will be created within each generated packages. "DEBIAN" uppercase is required from `dpkg-deb -b`: " Creates a debian archive from the filesystem tree stored in binary-directory. binary-directory must have a DEBIAN subdirectory, which contains the control information files such as the control file itself." I don't create package with Debian normal method documented, I don't understand how make good package. - Create a debian/rules file. This file is paramount, but it's missing! I insert rules file. I will commit soon. Hope this helps, Aitor. Thanks Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] mount.cifs fix (was: Re: We need upgrade reports)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 6 Jan 2020 22:58:06 +0100 Florian Zieboll wrote: > tl;dr: - The upgrade has been largely successful (besides cifs > mounts!). > (...) > >- There is one issue with cifs-utils left for further > investigation: Two fstab-mounted (remote) samba 4.2 shares, > formerly writable, have turned read-only - while my ascii > desktop has still r/w access. (As first client-side attempts > have not been successful yet, I will look at it another day, > together with the server.) Finally I came back to my beowulf cifs issue and, as actually expected, it was easily solvable at the client. From beowulf mount.cifs(8) for the "SMB protocol version" option: The default since v4.13.5 is for the client and server to negotiate the highest possible version greater than or equal to 2.1. In kernels prior to v4.13, the default was 1.0. For kernels between v4.13 and v4.13.5 the default is 3.0. The upgrade was from kernel v4.9 to v4.19; forcing the former default version 1.0 (vers=1.0) on mount made the shares writable again. Staying with the new default SMB version 3.0 (I /thought/ that I had tried this before), mount.cifs requires the "noperm" option to pass on the write permissions. lessons: 1. RTFM 2. slack configuration strikes back lulz & libre Grüße, Florian -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEELAr/aHjRNwfZVZJo7kVJef5EH9YFAl4jIGMACgkQ7kVJef5E H9anEhAAoxhnnCEfNMwtN2asure2B4wq35lvBHhk0gr5wt4fRVp3lz4oeibtvqqD w4Xs7H0LF/0MWDQ/qc5Qz4cbtLoM2APx8FusVE9vYffMswZryB8oBd/Q5rslmJMS rVCRi+/ItlyaWxhS0vKtpLAPiHNGVG83s2cSxoJgNbEcZgqSm7TXrbD+ZqYXGrO1 JfFsUluwxYxBVITp9sHEltd4nmnp+q4tmq3HMiLkB8HankeeqNguxTaCfa+z8Dqb S33Md16S1P2XW77TEAYcf6SZdQuha8wnaRlfypNn1NRQc9WcsW1x7nJMo7U4/4b4 +6FxWO14ZnQDDXAmYMGT1Zc5cwvsxFEd83DPxKYyQHGhrh2rTpDBBljUN+0Lf6ET m3bc8pk7IVrjdF+2154gZjNBnzLrZv+osS+ek8XzhZlBC7ISTpgBOZ485PqfXY9J FRq3tBeNrAE+MkmnOUvYFuHYL7aCsvNk3DUXv2Ky4UgVbyKQjOqrTYu7GxUA11wB vgDYkhELiNbLkPNx0xY5JoQut9rADP2VJVyqH4tUj4lYgl7U8uxfCB81NF5dAbY7 fnzQ60i18S8Q43+Fd2IUBGUsDlYdtKcxc6EbQqUNI1UOaXZ+w50d2E5cVE7aXTeD P0ydxVxt2OtMVoZLN7gzbJoeXcntwjwqtO55ohyAPfuZl+HVdRE= =r/RG -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] my first two packages
(...) within each generated packages (...) *package* ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] my first two packages
Hi Viverna, On 17/1/20 23:05, viverna wrote: Hi folks, I tried in my computers a epoch init system homemade package. I have no experience as packager and I don't like bureaucratic style for to make a Debian package or maybe I didn't understand it completely... :-) However I make my first, and maybe last :-) two package: epoch (base program) and epoch-data (config files). Grab it on: https://git.devuan.org/viverna/experimental-epoch https://git.devuan.org/viverna/experimental-epoch-data "make dist" make package "homemade" for arch amd64. Why Epoch? I like init scripts (for example runit) but epoch + daemon configuration file are the simplest infrastructure I know. epoch (program) is a package dependent on epoch-data (config file). Installing epoch, all config files are copied for all daemon installed and if grub is present epoch is added as entry in grub menu. Deleting epoch remove all scripts and entry in grub menu if grub is present. This solution is generic and could be applied for other init system. Init program (base program) and init-data (scripts init/config files). ifj in the devuan infrastructure to inject in all package init freedom (add conf file and init script in all daemon). With collaboration with ifj that disseminates in all packages init scripts or configuration files it could be guaranteed Init Freedom. There is no need of forking all daemon. Create 2 packages (init and init-data) for 1 init system. Create config file/init script for all daemon. Injected with ifj automatically. But there are problems: - I have little time to devote to this project. - Write code is ok for me but I am a very poor packager. I don't understand how make good packages. - I need help for write config file/init script for all daemon. - I (fairly) know only epoch and runit, other init just for the name. - Warning! Use it at your own risk! These packages are very very very experimental! However this could be a first start. My short answer for now: - Use lowercase letters for the debian folder. A DEBIAN folder with uppercase letters will be created within each generated packages. - Create a debian/rules file. This file is paramount, but it's missing! Hope this helps, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
