Re: [Dng] The result of my learning in the last few days
The common way to update the upstream source of a Debian package is: 1) Checkout the upstream branch. 2) Unpack a tarball of the desired version. 3) Commit all changes. 4) Tag the commit as "upstream/$VERSION". 5) pristine-tar commit /path/to/upstream/tarball.tgz 6) Checkout master/development branch. 7) Merge with the upstream The only difference between the upstream branch and the master/development branch should be the debian/ directory, so the merge should go off without a hitch. Updating to a date instead of a release tag is also a bit unusual. ~jaret On 05/24/2015 10:28 PM, Anto wrote: Hello Everybody, I have learnt a lot in the last few days about some tiny parts in the development of packages for Debian based distros. The result of that is on https://git.devuan.org/anto/gentoo-eudev. There are some annoying issues that I still cannot find the solutions for. I have tried to respect the efforts of others by preserving their commits, but their last updates and commits on some files are not being shown on the "Files" tab. The other issue is that, there seems to be no way to add empty lines after the code block as Markdown always removes them. For instance, I would like to add an empty line above "On Debian wheezy installs" on README.md file. In regards to the licensing and setting the maintainer of the package, since I didn't fork the whole repository I am not sure whether I need to add the license and keep the previous maintainer or not. Do you have any suggestions on the above issues? A part from the above, I really appreciate any feedbacks from you especially on which parts that I did wrong and whether there is something that needs to be added or remove. Thanks a lot in advance. Cheers, Anto PS: Before you ask, yes I have been using the latest eudev package 3.0+ which is compatible with systemd-udev 219+ as shown below. However, I prefer to use the packages from Debian wheezy repository as much as possible. root@hp8530w:~# root@hp8530w:~# dpkg --list | egrep "udev|dbus" ii at-spi2-core 2.14.0-1 amd64 Assistive Technology Service Provider Interface (dbus core) ii dbus 1.8.16-1+devuan1 amd64simple interprocess messaging system (daemon and utilities) ii dbus-1-doc 1.8.16-1+devuan1 all simple interprocess messaging system (documentation) ii dbus-x11 1.8.16-1+devuan1 amd64 simple interprocess messaging system (X11 deps) ii gir1.2-gudev-1.0 219:3.0-1 amd64libgudev-1.0 introspection data ii libaudclient2:amd64 3.2.4-1 amd64audacious dbus remote control library ii libdbus-1-3:amd64 1.8.16-1+devuan1 amd64simple interprocess messaging system (library) ii libdbus-1-dev:amd64 1.8.16-1+devuan1 amd64simple interprocess messaging system (development headers) ii libdbus-glib-1-2:amd64 0.100.2-1 amd64simple interprocess messaging system (GLib-based shared library) ii libdbus-glib-1-dev 0.100.2-1 amd64simple interprocess messaging system (GLib interface) ii libgudev-1.0-0:amd64 219:3.0-1 amd64GObject-based wrapper library for libudev ii libgudev-1.0-dev 219:3.0-1 amd64libgudev-1.0 development files ii libnet-dbus-perl 1.0.0-1+b1 amd64Extension for the DBus bindings ii libudev-dev:amd64 219:3.0-1 amd64libudev development files ii libudev1:amd64 219:3.0-1 amd64 libudev shared library ii python-dbus 1.1.1-1amd64 simple interprocess messaging system (Python interface) ii python-dbus-dev 1.1.1-1 all main loop integration development files for python-dbus ii udev 219:3.0-1 amd64/dev/ and hotplug management daemon root@hp8530w:~# root@hp8530w:~# dpkg --list lightdm xfce4 xserver-xorg xserver-xorg-video-all consolekit Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=-=- ii consolekit 0.4.6-6 amd64 framework for defining and tracking users, sessions and seats ii lightdm 1.2.2-4 amd64 simple display manager ii xfce4 4.8.0.3 all Meta-package for the Xfce Lightweight Desktop Environment ii xserver-xorg 1:7.7+3~deb7u1 amd64 X.Org X server ii xserver-xorg-video-all 1:7.7+7 amd64 X.Org X server -- output driver metapackage root@hp8530w:~# root@hp8530w:~# root@hp8530w:~# dmesg | egrep "udev|Linux version" [0.00] Linux version 3.18.12-1v0-hp8530w (root@hp8530w) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP
[Dng] The result of my learning in the last few days
Hello Everybody, I have learnt a lot in the last few days about some tiny parts in the development of packages for Debian based distros. The result of that is on https://git.devuan.org/anto/gentoo-eudev. There are some annoying issues that I still cannot find the solutions for. I have tried to respect the efforts of others by preserving their commits, but their last updates and commits on some files are not being shown on the "Files" tab. The other issue is that, there seems to be no way to add empty lines after the code block as Markdown always removes them. For instance, I would like to add an empty line above "On Debian wheezy installs" on README.md file. In regards to the licensing and setting the maintainer of the package, since I didn't fork the whole repository I am not sure whether I need to add the license and keep the previous maintainer or not. Do you have any suggestions on the above issues? A part from the above, I really appreciate any feedbacks from you especially on which parts that I did wrong and whether there is something that needs to be added or remove. Thanks a lot in advance. Cheers, Anto PS: Before you ask, yes I have been using the latest eudev package 3.0+ which is compatible with systemd-udev 219+ as shown below. However, I prefer to use the packages from Debian wheezy repository as much as possible. root@hp8530w:~# root@hp8530w:~# dpkg --list | egrep "udev|dbus" ii at-spi2-core 2.14.0-1 amd64 Assistive Technology Service Provider Interface (dbus core) ii dbus 1.8.16-1+devuan1 amd64simple interprocess messaging system (daemon and utilities) ii dbus-1-doc 1.8.16-1+devuan1 all simple interprocess messaging system (documentation) ii dbus-x11 1.8.16-1+devuan1 amd64simple interprocess messaging system (X11 deps) ii gir1.2-gudev-1.0 219:3.0-1 amd64 libgudev-1.0 introspection data ii libaudclient2:amd64 3.2.4-1amd64 audacious dbus remote control library ii libdbus-1-3:amd64 1.8.16-1+devuan1 amd64 simple interprocess messaging system (library) ii libdbus-1-dev:amd64 1.8.16-1+devuan1 amd64 simple interprocess messaging system (development headers) ii libdbus-glib-1-2:amd64 0.100.2-1 amd64simple interprocess messaging system (GLib-based shared library) ii libdbus-glib-1-dev 0.100.2-1 amd64 simple interprocess messaging system (GLib interface) ii libgudev-1.0-0:amd64 219:3.0-1 amd64 GObject-based wrapper library for libudev ii libgudev-1.0-dev 219:3.0-1 amd64 libgudev-1.0 development files ii libnet-dbus-perl 1.0.0-1+b1 amd64 Extension for the DBus bindings ii libudev-dev:amd64 219:3.0-1 amd64 libudev development files ii libudev1:amd64 219:3.0-1 amd64 libudev shared library ii python-dbus 1.1.1-1amd64simple interprocess messaging system (Python interface) ii python-dbus-dev 1.1.1-1all main loop integration development files for python-dbus ii udev 219:3.0-1 amd64/dev/ and hotplug management daemon root@hp8530w:~# root@hp8530w:~# dpkg --list lightdm xfce4 xserver-xorg xserver-xorg-video-all consolekit Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=-=- ii consolekit 0.4.6-6 amd64 framework for defining and tracking users, sessions and seats ii lightdm 1.2.2-4 amd64 simple display manager ii xfce4 4.8.0.3 all Meta-package for the Xfce Lightweight Desktop Environment ii xserver-xorg 1:7.7+3~deb7u1amd64 X.Org X server ii xserver-xorg-video-all 1:7.7+7 amd64 X.Org X server -- output driver metapackage root@hp8530w:~# root@hp8530w:~# root@hp8530w:~# dmesg | egrep "udev|Linux version" [0.00] Linux version 3.18.12-1v0-hp8530w (root@hp8530w) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Sun Apr 26 17:33:02 CEST 2015 [0.785118] udevd[67]: starting version 3.0 [0.785425] random: udevd urandom read with 2 bits of entropy available [3.236958] udevd[289]: starting version 3.0 root@hp
Re: [Dng] The basic of building package
On 21/05/15 17:02, tilt wrote: Hi Anto, IMHO, knowing how to identify and work with existing packages that use quilt still is neccessary, for example to not break with the existing conventions of maintenance of such a package, and of course for taking countermeasures against unwelcome patches ... ;-) Getting quilt to work the Debian way is not difficult and well explained here: https://wiki.debian.org/UsingQuilt#Using_quilt_with_Debian_source_packages The section "Basic quilt tasks" covers the activities of creating new patches on top of an existing series of patches, and applying, unapplying and modifying them. Additionally, there's the activity of deleting an existing patch which can be accomplished with "quilt delete". IIRC, without the -r flag to "quilt delete", the patch is disabled, with the flag set it's physically deleted. Technically there's not much more to it. Kind regards, t. Thanks Tilt and some other guys who directly sent me your suggestions. When I started this thread, I was actually looking for tips and hints based on your experience in updating packages using the methods that are closer to the the old ways, e.g. using diff and patch. I am getting slower now to learn new ways. So instead of starting to learn about quilt and other development tools at the same time, I decided to focus my learning more only on git, as I think that covers most requirements. A part from the technical aspect in updating and forking packages, I would like to learn also about the non-technical aspects like the licensing, collaborating and respecting the efforts of others. I will post this on another thread based on the results of my learning in the last few days. Cheers, Anto ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[Dng] Unexpected upgrades when updating...
Hello, Running Devuan Jessie. I updated, marked all upgrades, and apt wanted to install ffmpeg instead of libav-tools. Looking at the proposed changes in detail, I see that this is a result of debian-multimedia.org (dmo) packages, as might be expected. What I *don't* get, though is why I'm getting dmo packages when my sources.list contains only the devuan merged repo, a Debian mirror, and angband.pl. apt-cache policy ffmpeg claims that this package is being offered via the devuan merged repo. So is there a way to make dmo packages go away? Secondly, I've installed googleearth via googleearth-package. It depends on lsb-core, which depends on the same version of lsb-release and lsb-base; apparently lsb-core has been rebuilt without rebuilding lsb-release and lsb-base, since they are unavailable. Thanks, Isaac Dunham ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] Slackware systemd creepin in maybe?
On 2015-05-24 12:17, Steve Litt wrote: On Sun, 24 May 2015 09:47:13 -0300 Marlon Nunes wrote: On 2015-05-23 15:21, Steve Litt wrote: > Xfce is starting to get too entangled, so I use Openbox. If Openbox > gets snared, I'll go to dwm. If firefox becomes entangled, I'll There are also lxqt (which uses openbox as their WM). http://lxqt.org/ http://lxqt.org/images/screenshots/plasma.png no sign of systemd. Very nice! Thanks for the pointer to LXQt. LXQt is the successor to the old LXDE, which is, IMHO the most stable of all the "Win9x style" window manager/desktop environments. I've used it for years on my travel notebook, and I've found it to always work: Something I can't say about most other Desktop Environments, *including* Xfce. When I go to a client to train them in Troubleshooting, I want a Win9x interface so I can go braindead about tech and concentrate on teaching. LXDE (and I presume LXQt) does that perfectly, and lxrandr is *especially* helpful when connecting to random projectors. Better yet, because LXQt is built around Openbox, you can configure its Openbox parts to respond to all the same hotkeys as just plain Openbox, which means you have LXQt's complete Win9x interface in parallel with the fastest known keyboard interface (especially if paired with dmenu). You're right, Marlon, LXDE, and therefore I'd assume LXQt, is a spectacularly productive interface for almost anyone. Thanks for reminding me. SteveT Steve Litt May 2015 featured book: Quit Joblessness: Start Your Own Business http://www.troubleshooters.com/startbiz ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng :D , I'm running a complete system without systemd: Openrc + eudev + lxqt = funtoo I'm planning to test vdev + openrc in funtoo. -- Stop slacking you lazy bum! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] Slackware systemd creepin in maybe?
On Sun, 24 May 2015 09:47:13 -0300 Marlon Nunes wrote: > On 2015-05-23 15:21, Steve Litt wrote: > > Xfce is starting to get too entangled, so I use Openbox. If Openbox > > gets snared, I'll go to dwm. If firefox becomes entangled, I'll > > There are also lxqt (which uses openbox as their WM). > http://lxqt.org/ > http://lxqt.org/images/screenshots/plasma.png > no sign of systemd. Very nice! Thanks for the pointer to LXQt. LXQt is the successor to the old LXDE, which is, IMHO the most stable of all the "Win9x style" window manager/desktop environments. I've used it for years on my travel notebook, and I've found it to always work: Something I can't say about most other Desktop Environments, *including* Xfce. When I go to a client to train them in Troubleshooting, I want a Win9x interface so I can go braindead about tech and concentrate on teaching. LXDE (and I presume LXQt) does that perfectly, and lxrandr is *especially* helpful when connecting to random projectors. Better yet, because LXQt is built around Openbox, you can configure its Openbox parts to respond to all the same hotkeys as just plain Openbox, which means you have LXQt's complete Win9x interface in parallel with the fastest known keyboard interface (especially if paired with dmenu). You're right, Marlon, LXDE, and therefore I'd assume LXQt, is a spectacularly productive interface for almost anyone. Thanks for reminding me. SteveT Steve Litt May 2015 featured book: Quit Joblessness: Start Your Own Business http://www.troubleshooters.com/startbiz ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] Slackware systemd creepin in maybe?
On 2015-05-23 15:21, Steve Litt wrote: On Sat, 23 May 2015 07:29:56 + toki wrote: On 23/05/2015 05:18, James Powell wrote: > True, but developers are banding together to resist this as well, > and fork projects as needed. But what happens when one has to fork everything from Firefox to Enkive to Hadoop to Tryton? In a word, boycott. Xfce is starting to get too entangled, so I use Openbox. If Openbox gets snared, I'll go to dwm. If firefox becomes entangled, I'll move to xxxterm or one of the other "light" browsers. If those get entangled, I'll use a text browser for most things, and a containerized GUI browser for the remainder. We work with free software, and pay no money for it, but maintaining *our* standards for what goes on our boxes is anything but free. We, and I mean we as a user community, not necessarily we as a distro, need to scale back our expectations, work harder, be more innovative, be flexible in changing our work habits to accommodate less-dependencied software. The person who "simply must" work a certain way and will not consider changing to adapt when his pet software goes entangled, will not survive in owner-maintainable software, and must join those who gleefully add locked computers to their locked phones. You know when I knew Devuan had it right? When Devuan declined to support Gnome. Declined to jump through ever increasing hoops to depoetterize ever more sabotaged software, but instead basically said "hey, if you're so in love with Gnome that it's a must have, then Devuan is the wrong place for you." If Tryton demands systemd, find a different ERP. If Hadoop demands systemd, find a different big data system. If Firefox (which isn't the the most stable program anyway) requires systemd, use xxxterm or whatever. If Enkive requires systemd, find something else to do whatever email machinations Enkive does. And when I say "different", I specifically include commercially licensed software, because vendor lockin is vendor lockin, whether by contract or by complexity ruling out owner maintenance. If it weren't for PC-BSD, Manjaro-OpenRC and Devuan, I'd be using a Mac today. Once I can't fix/modify my own possessions, does it really matter whether it's free software or not? If every consumer walked away from bad deals like systemd requirements, such bad deals would wither on the vine. We've come together as a community to make a systemd-free distro. That's half the job. The other half is each of us, as consumers, saying goodbye to those programs that decide it would be [hip|easier|necessary] to enmesh with V'jer. If enough of us do that and publicise it enough, "upstreams" might think twice before walking happily into their assimilation. By the way, for that one app that's absolutely business critical with absolutely no substitute, the consumer can use a container, so we don't have to put ourselves out of business to do this. SteveT Steve Litt May 2015 featured book: Quit Joblessness: Start Your Own Business http://www.troubleshooters.com/startbiz ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng There are also lxqt (which uses openbox as their WM). http://lxqt.org/ http://lxqt.org/images/screenshots/plasma.png no sign of systemd. -- Stop slacking you lazy bum! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] Slackware systemd creepin in maybe?
* On 2015 23 May 23:44 -0500, James Powell wrote: > Remember Lennart's remarks about BSD? > > "BSD isn't relevant anymore. It's a toy OS." Interesting quote considering OS/X is built on BSD and he is in the lead of the group chasing Apple's tail lights. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Ham radio, Linux, bikes, and more: http://www.n0nb.us ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
