:: Re: [Dng] The result of my learning…
Página Principal
Delete this message
Reply to this message
Autor: Jaret Cantu
Data:  
Para: dng
Assunto: 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                   amd64        simple 
> 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 amd64        libgudev-1.0 introspection 
> data
> ii  libaudclient2:amd64 3.2.4-1 amd64        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 amd64        simple 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-1                            amd64 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.000000] 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@hp8530w:~#

>
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng