Re: [DNG] Docker leaves Ubuntu for AlpineLinux (and hires its dev)
> I also don't understand that some media state he has been hired by Docker, > as according to his Linked In profiles, he is the founder and CTO: > https://www.linkedin.com/in/solomonhykes > More questions than answers, I'm afraid. the guy that have been hired by docker is natanael copa, creator of alpine linux : https://twitter.com/n_copa > > 2016-02-13 1:11 GMT+01:00 Nate Bargmann : >> >> I know Alpine Linux has been mentioned before on this list so I took >> some time and have investigated it a bit more. While I still prefer the >> Debian way that I've grown to know over the past 16 1/2 years, I do like >> certain aspects of Alpine. Even the largest ISO installed a very lean >> base system into a Virtual Box VM. OpenRC makes a very nice >> presentation on system start and the system seems lightning fast. There >> is even a Pi version I may need to try. >> >> If nothing else, the alternatives are proving to be an interesting >> change from the mainstream. >> >> - 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 > > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Docker leaves Ubuntu for AlpineLinux (and hires its dev)
Quote from Solomon Hykes' blog: "To build Docker we have re-used large quantities of plumbing: Linux, Go, lxc, aufs, lvm, iptables, virtualbox, vxlan, mesos, etcd, consul, systemd… the list goes on. " https://blog.docker.com/author/solomon/ I also don't understand that some media state he has been hired by Docker, as according to his Linked In profiles, he is the founder and CTO: https://www.linkedin.com/in/solomonhykes More questions than answers, I'm afraid. 2016-02-13 1:11 GMT+01:00 Nate Bargmann : > I know Alpine Linux has been mentioned before on this list so I took > some time and have investigated it a bit more. While I still prefer the > Debian way that I've grown to know over the past 16 1/2 years, I do like > certain aspects of Alpine. Even the largest ISO installed a very lean > base system into a Virtual Box VM. OpenRC makes a very nice > presentation on system start and the system seems lightning fast. There > is even a Pi version I may need to try. > > If nothing else, the alternatives are proving to be an interesting > change from the mainstream. > > - 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 > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Are you still paranoid if you turned out to be right?
On Fri, 12 Feb 2016 17:40:18 -0800 GoOSSBears wrote: > --- sl...@troubleshooters.com wrote: > From: Steve Litt > To: > Subject: [DNG] Are you still paranoid if you turned out to be right? > Date: Fri, 12 Feb 2016 17:53:15 -0500 > > > Hi all, > > > > For those of you who remember the most unpopular stuff I said on > > Debian-User, the stuff I said about Red Hat, the stuff people > > called me a conspiracy theorist for: Am I still paranoid if it > > turned out I was right? > > IIRC, the very last time you posted on Debian-User was back on 22 Oct > 2014 [01][02]. So would you care to elaborate what those previous D-U > posts were where you said the "unpopular stuff" on RH, among your D-U > postings that year from March[03], April[04], May[05], June[06], > July[07], August[08], September[09], and/or October[10] ?? > > TY https://lists.debian.org/debian-user/2014/10/msg00800.html https://lists.debian.org/debian-user/2014/10/msg01808.html https://lists.debian.org/debian-user/2014/09/msg01356.html There are more, but it's difficult because the Debian archives aren't searchable. Anyway, these three give you the feel for what I'm talking about. > For others, try the following Google search: > Refs > > [01]https://lists.debian.org/debian-user/2014/10/msg01982.html > [02]https://lists.debian.org/debian-user/2014/10/msg01981.html > [03]https://lists.debian.org/debian-user/2014/03/author3.html > [04]https://lists.debian.org/debian-user/2014/04/author3.html > [05]https://lists.debian.org/debian-user/2014/05/author4.html > [06]https://lists.debian.org/debian-user/2014/06/author4.html > [07]https://lists.debian.org/debian-user/2014/07/author4.html > [08]https://lists.debian.org/debian-user/2014/08/author3.html > [09]https://lists.debian.org/debian-user/2014/09/author5.html > [10]https://lists.debian.org/debian-user/2014/10/author5.html > - The preceding cover a lot of territory not germane to Red Hat profiting from from complexity. SteveT Steve Litt February 2016 featured book: The Key to Everyday Excellence http://www.troubleshooters.com/key ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Are you still paranoid if you turned out to be right?
--- sl...@troubleshooters.com wrote: From: Steve Litt To: Subject: [DNG] Are you still paranoid if you turned out to be right? Date: Fri, 12 Feb 2016 17:53:15 -0500 > Hi all, > > For those of you who remember the most unpopular stuff I said on > Debian-User, the stuff I said about Red Hat, the stuff people called me > a conspiracy theorist for: Am I still paranoid if it turned out I was > right? IIRC, the very last time you posted on Debian-User was back on 22 Oct 2014 [01][02]. So would you care to elaborate what those previous D-U posts were where you said the "unpopular stuff" on RH, among your D-U postings that year from March[03], April[04], May[05], June[06], July[07], August[08], September[09], and/or October[10] ?? TY Refs [01]https://lists.debian.org/debian-user/2014/10/msg01982.html [02]https://lists.debian.org/debian-user/2014/10/msg01981.html [03]https://lists.debian.org/debian-user/2014/03/author3.html [04]https://lists.debian.org/debian-user/2014/04/author3.html [05]https://lists.debian.org/debian-user/2014/05/author4.html [06]https://lists.debian.org/debian-user/2014/06/author4.html [07]https://lists.debian.org/debian-user/2014/07/author4.html [08]https://lists.debian.org/debian-user/2014/08/author3.html [09]https://lists.debian.org/debian-user/2014/09/author5.html [10]https://lists.debian.org/debian-user/2014/10/author5.html - https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng _ Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com Join Linux Discussions! --> http://Community.LinuxWaves.com ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Docker leaves Ubuntu for AlpineLinux (and hires its dev)
I know Alpine Linux has been mentioned before on this list so I took some time and have investigated it a bit more. While I still prefer the Debian way that I've grown to know over the past 16 1/2 years, I do like certain aspects of Alpine. Even the largest ISO installed a very lean base system into a Virtual Box VM. OpenRC makes a very nice presentation on system start and the system seems lightning fast. There is even a Pi version I may need to try. If nothing else, the alternatives are proving to be an interesting change from the mainstream. - 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
Re: [DNG] Frontend to pmount
On 02/12/2016 12:04 AM, aitor_czr wrote: > > On 02/09/2016 03:02 PM, fsmithred wrote: >> I was inpired by Steve Litt's amounter, but I prefer a semi-automatic. And >> I wanted an easy clicky way to use pmount. So I recycled some code from >> refracta2usb and added inotifywait. >> >> The result is a set of scripts that will pop up a window showing the >> partitions on the usb drive when it's plugged in. Then it mounts your >> choice and opens it in your default file manager. >> >> fsmithred > > > Did you know obdevicemenu? I found it in the Arch's forum, but now the > download link is forbidden. > > https://sourceforge.net/projects/obdevicemenu/files/ > > I can rescue this script. > > Aitor. > No, I've never seen it, but I'd be interested in looking at it and trying it. I like that pmount is simple and has few dependencies, but I also like to have alternatives, especially after the changes I've seen in software over the last year or so. Thanks, fsr ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Are you still paranoid if you turned out to be right?
Hi all, For those of you who remember the most unpopular stuff I said on Debian-User, the stuff I said about Red Hat, the stuff people called me a conspiracy theorist for: Am I still paranoid if it turned out I was right? See the following URL and quote: www.infoworld.com/article/3032647/open-source-tools/face-it-theres-no-money-in-open-source.html = As then-Red Hat CTO Brian Stevens once told me: "Red Hat's model works because of the complexity of the technology we work with. An operating platform has a lot of moving parts, and customers are willing to pay to be insulated from that complexity. I don't think you can take one finite element - like Apache - and make a business out of it [using our model]. You need product complexity." = Signed, sealed, delivered, they're busted! Ever wonder why the powers that be hate Devuan so much? Follow the money. I know that all of us have thought, on our darker days, that we can't forever remove the poetterizations Red Hat keeps paying millions to insert into strategic parts of Linux. But maybe, just maybe, the Red Hat tycoons are beginning to wonder whether they can forever fight Devuan and the other sans-systemd distros who can keep depoetterizing for free. SteveT Steve Litt February 2016 featured book: The Key to Everyday Excellence http://www.troubleshooters.com/key ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Docker leaves Ubuntu for AlpineLinux (and hires its dev)
On Thu, 11 Feb 2016 11:51:42 +0100 Jaromil wrote: > Here the news on Phoronix (well known hangout of systemd hooligans) > > https://www.phoronix.com/scan.php?page=news_item&px=Docket-Alpine-Images > > Very elegant of the editor to skip over the obviously implicit read > between the lines. Or am I the only one seeing a "systemd sucks" here > written with invisible ink? Alpine Linux uses OpenRC, which, in my opinion, sucks. That being said, the two big disadvantages of OpenRC are its inability to respawn, and it's gigantic, hairy init scripts. Both these disadvantages can be overcome by managing processes with daemontools-encore or s6 or Runit (as a supervisor, not an init). OpenRC runs the supervisor, and the supervisor supervises all the daemons. Although sysvinit can respawn, I think running a process supervisor off sysvinit and all the daemons off the process supervisor makes sense in sysvinit distros like Devuan[1]. [1] My process supervisor recommendation is at the user level, as opposed to a recommendation for Devuan to operate that way out of the box. SteveT Steve Litt February 2016 featured book: The Key to Everyday Excellence http://www.troubleshooters.com/key ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Docker leaves Ubuntu for AlpineLinux (and hires its dev)
On Thu, 11 Feb 2016 11:51:42 +0100 Jaromil wrote: > Here the news on Phoronix (well known hangout of systemd hooligans) > > https://www.phoronix.com/scan.php?page=news_item&px=Docket-Alpine-Images > > Very elegant of the editor to skip over the obviously implicit read > between the lines. Or am I the only one seeing a "systemd sucks" here > written with invisible ink? > > ciao :^) Wait: There is a plausible alternative motivation for Docker... From what I hear, Ubuntu is switching to this whole new, "in the cloud" type of packaging and other stuff. The move from Ubuntu could have been to avoid that cloud crap. But of course, Docker could have chosen Redhat, or OpenSuSE, or Debian, and apparently they didn't. Hm. I gotta snicker. On my local LUG's mailing list, a WAD (Walking Acronym Dispenser) posted all sorts of anti-anti-systemd stuff about how necessary systemd is in this age of containers. And now the leading container vendor moves to an OpenRC initted distro. So much for systemd's necessity in the age of containers. SteveT Steve Litt February 2016 featured book: The Key to Everyday Excellence http://www.troubleshooters.com/key ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Set up a local copy of Daniel Reurich's branch of my project
Hi, I would like to set up a local copy of Daniel Reurich's branch of my project so that I can help in fixing bugs. I am thinking of 'git clone' but I don't understand exactly whether it does what I want. This command may do what I need. mkdir daniel-simple-netaid cd daniel-simple-netaid git clone -b simple-netaid g...@git.devuan.org:net/simple-netaid.git At the end I also need to make sure I can 'git push' my changes to Daniel's branch. I have been granted developer access to it. Edward ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev packaging effort ( was: state of what's working for modern desktop usage)
Le 12/02/2016 16:00, shraptor a écrit : I dug up some very old correspondence I had with Jude regarding why he uses dash I said "however I dont have dash on my system so I had to symlink it to bash to make vdev run vdevd/helpers/LINUX/*.sh files" Here is what he said then 2015-05-22 06:25 "That should be temporary. I'm currently going through the scripts to make sure they work with Devuan's system shell (dash). When I create the "-release" branch, I will switch back to #!/bin/sh." Thanks for the confirmation :-) Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev packaging effort ( was: state of what's working for modern desktop usage)
On 2016-02-12 15:34, shraptor wrote: On 2016-02-12 10:50, Didier Kryn wrote: Le 12/02/2016 02:54, Rainer Weikusat a écrit : Didier Kryn writes: Le 11/02/2016 17:04, Rainer Weikusat a écrit : Didier Kryn writes: [...] It should be the name of a shell capable of running Bourne/ standard shell scripts. But this may not work if the /bin/dash in the original script was there for a reason, ie, it was using dash features. As I already wrote, vdev was working well with busybox's ash., replacing 'dash' with 'sh' in the shebang. If the question is why Jude replaced /bin/sh with /bin/dash in the middle of the development, I think it was to make sure to not invoke bash. But (sorry for the repetition) I used to modify the shebang everytime I tested a new version, and there was never any issue with the shell. There is no question here. *If* the script in question uses dash spuriously, ie, it doesn't use features specific to dash but is actually a Bourne shell script, replacing /bin/dash with /bin/sh should be fine. If not, stuff is going to break sooner or later, either because /bin/sh isn't really dash (eg, someone might use bash for that) or because of difference between the busybox and Debian (d)ash forks. There shouldn't be any "feature specific to dash", by construction. There are, "by construction". Eg, dash supports local, the POSIX /bin/sh doesn't. Then it seems Jude's scripts don't use that feature, and they shouldn't. If you check *.sh in vdev/vdevd/helpers/LINUX on git they use local I dug up some very old correspondence I had with Jude regarding why he uses dash I said "however I dont have dash on my system so I had to symlink it to bash to make vdev run vdevd/helpers/LINUX/*.sh files" Here is what he said then 2015-05-22 06:25 "That should be temporary. I'm currently going through the scripts to make sure they work with Devuan's system shell (dash). When I create the "-release" branch, I will switch back to #!/bin/sh." /Scooby ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev packaging effort ( was: state of what's working for modern desktop usage)
On 2016-02-12 10:50, Didier Kryn wrote: Le 12/02/2016 02:54, Rainer Weikusat a écrit : Didier Kryn writes: Le 11/02/2016 17:04, Rainer Weikusat a écrit : Didier Kryn writes: [...] It should be the name of a shell capable of running Bourne/ standard shell scripts. But this may not work if the /bin/dash in the original script was there for a reason, ie, it was using dash features. As I already wrote, vdev was working well with busybox's ash., replacing 'dash' with 'sh' in the shebang. If the question is why Jude replaced /bin/sh with /bin/dash in the middle of the development, I think it was to make sure to not invoke bash. But (sorry for the repetition) I used to modify the shebang everytime I tested a new version, and there was never any issue with the shell. There is no question here. *If* the script in question uses dash spuriously, ie, it doesn't use features specific to dash but is actually a Bourne shell script, replacing /bin/dash with /bin/sh should be fine. If not, stuff is going to break sooner or later, either because /bin/sh isn't really dash (eg, someone might use bash for that) or because of difference between the busybox and Debian (d)ash forks. There shouldn't be any "feature specific to dash", by construction. There are, "by construction". Eg, dash supports local, the POSIX /bin/sh doesn't. Then it seems Jude's scripts don't use that feature, and they shouldn't. If you check *.sh in vdev/vdevd/helpers/LINUX on git they use local Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev packaging effort ( was: state of what's working for modern desktop usage)
On 2016-02-11 23:48, Didier Kryn wrote: Le 11/02/2016 19:25, shraptor a écrit : In my setup /usr/bin/dash is a symlink to /usr/bin/bash That's a big mistake. On any Debian system, /bin/sh points to /bin/dash, and dash doesn't point to bash. Your system has certainly been hacked. Yes, It has been hacked by me, I could have installed dash but a symlink worked fine. It works! Sure, bash can process ash scripts. The problem is the opposite isn't true because bash provides a lot of additional features, "bashisms", which distros decided to erradicate from their scripts. Users are free to write bash or ksh scripts, but portable scripts must execute on ash. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev packaging effort ( was: state of what's working for modern desktop usage)
Rainer Weikusat writes: [/bin/dash -> /bin/sh] >>> There is no question here. *If* the script in question uses dash >>> spuriously, ie, it doesn't use features specific to dash but is actually >>> a Bourne shell script, replacing /bin/dash with /bin/sh should be >>> fine. If not, stuff is going to break sooner or later, either because >>> /bin/sh isn't really dash (eg, someone might use bash for that) or >>> because of difference between the busybox and Debian (d)ash forks. >> >> There shouldn't be any "feature specific to dash", by >> construction. > > There are, "by construction". Eg, dash supports local, the POSIX /bin/sh > doesn't. A more serious one (which has once bitten me badly): dash supports chdir as undocumented alias for cd (at least up to Wheezy) [rw@doppelsaurus]/tmp#dash -c 'chdir / && pwd' / [rw@doppelsaurus]/tmp#bash -c 'chdir / && pwd' bash: chdir: command not found And then, the busybox (d)ash and the Deban dash are still completely independent codebases ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev packaging effort ( was: state of what's working for modern desktop usage)
Le 12/02/2016 06:21, Adam Borowski a écrit : On Thu, Feb 11, 2016 at 11:41:19PM +0100, Didier Kryn wrote: But POSIX conformance is not enough, /bin/dash in the shebang obviously renders portability impossible. Just look at any system script in your Debian or Devuan system and tell me if any of them start with #! /bin/dash. https://codesearch.debian.net/results/%23!%2Fbin%2Fdash/page_0 Description of the package: cruft is a program to look over your system for anything that shouldn't be there, but is; or for anything that should be there, but isn't. It bases most of its results on dpkg's database, as well as a list of `extra files' that can appear during the lifetime of various packages. cruft is still in pre-release; your assistance in improving its accuracy and performance is appreciated. - end of desctiption This is a Debian-only package, therefore no concern for portability. Even given that, I wonder what the reason is to select dash as the interpreter, although I don't care much. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev packaging effort ( was: state of what's working for modern desktop usage)
Le 12/02/2016 02:54, Rainer Weikusat a écrit : Didier Kryn writes: Le 11/02/2016 17:04, Rainer Weikusat a écrit : Didier Kryn writes: [...] It should be the name of a shell capable of running Bourne/ standard shell scripts. But this may not work if the /bin/dash in the original script was there for a reason, ie, it was using dash features. As I already wrote, vdev was working well with busybox's ash., replacing 'dash' with 'sh' in the shebang. If the question is why Jude replaced /bin/sh with /bin/dash in the middle of the development, I think it was to make sure to not invoke bash. But (sorry for the repetition) I used to modify the shebang everytime I tested a new version, and there was never any issue with the shell. There is no question here. *If* the script in question uses dash spuriously, ie, it doesn't use features specific to dash but is actually a Bourne shell script, replacing /bin/dash with /bin/sh should be fine. If not, stuff is going to break sooner or later, either because /bin/sh isn't really dash (eg, someone might use bash for that) or because of difference between the busybox and Debian (d)ash forks. There shouldn't be any "feature specific to dash", by construction. There are, "by construction". Eg, dash supports local, the POSIX /bin/sh doesn't. Then it seems Jude's scripts don't use that feature, and they shouldn't. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Help me understand what Daniel Reurich is asking?
Hi Svante, El 12/02/16 a las 09:51, Svante Signell escribió: On Fri, 2016-02-12 at 09:29 +0100, aitor_czr wrote: >Hi Daniel and Edward, > > >In summary: > >1) DebSrc 3.0 (native) generates only a tar.gz, containing also the debian >folder. There is not a debian branch, and this is the reason why Edward >changed the version number from 0.1.1-1 to 0.1.1 in debian/changelog. > >2) DebSrc 3.0 (quilt), instead, generates an orig.tar.gz and a debian.tar.gz >separately. So, the version number must include the version in the debian >branch, this is 0.1.1-1 > >On the other hand, i cloned gdisk: > >https://git.devuan.org/pkg-admin/gdisk.git > >It uses the 3.0 (git) format, and now dpkg-guildpackage generates a binary >file: > > *gdisk_1.0.0-2+devuan0.4.git* Hello, This is very useful information. Can you (or somebody else) please write this down together as a sub-page of the the developer page https://git.devuan.org/devuan/devuan-project/wikis/guidelines (or wherever it belongs) and update the build procedure for different cases: native, git and quilt. This is very useful for people adopting packages for Devuan (like me). A follow-up question: You mention dpkg-buildpackage, what about git- buildpackage? Git-buildpackage must be used in the case of the 3.0 (quilt) format. This is the only one wich needs a orig.tar.bz2 / orig.tar.gz in the parent directory. Using the pristine-tar branch is also recommended in this concrete case. From my point of view, this format should be used in such projects envolving a lot of developers (the kernel, the grub, etc...) Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Help me understand what Daniel Reurich is asking?
On Fri, 2016-02-12 at 09:29 +0100, aitor_czr wrote: > Hi Daniel and Edward, > > > In summary: > > 1) DebSrc 3.0 (native) generates only a tar.gz, containing also the debian > folder. There is not a debian branch, and this is the reason why Edward > changed the version number from 0.1.1-1 to 0.1.1 in debian/changelog. > > 2) DebSrc 3.0 (quilt), instead, generates an orig.tar.gz and a debian.tar.gz > separately. So, the version number must include the version in the debian > branch, this is 0.1.1-1 > > On the other hand, i cloned gdisk: > > https://git.devuan.org/pkg-admin/gdisk.git > > It uses the 3.0 (git) format, and now dpkg-guildpackage generates a binary > file: > > *gdisk_1.0.0-2+devuan0.4.git* Hello, This is very useful information. Can you (or somebody else) please write this down together as a sub-page of the the developer page https://git.devuan.org/devuan/devuan-project/wikis/guidelines (or wherever it belongs) and update the build procedure for different cases: native, git and quilt. This is very useful for people adopting packages for Devuan (like me). A follow-up question: You mention dpkg-buildpackage, what about git- buildpackage? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Help me understand what Daniel Reurich is asking?
Hi Daniel and Edward, El 12/02/16 a las 06:09, aitor_czr escribió: On 02/12/2016 02:51 AM, Daniel Reurich wrote: Where can i find documentation about this other method? I've never used it. > >Are the existing *.git files generated by this format? See, for example, >the case of gdisk: > >http://packages.devuan.org/devuan/pool/main/g/gdisk/ > >There isn't any tarball in the repository...; a git file, instead. > >Although after downloading the sources of the project i find the same >3.0 (quilt) format in "debian/source/format", any 3.0 (native). > >Thanks in advance, > > Aitor. It's only used for packages that debian|devuan build for themselves. Look at the likes of debootstrap and other debian specific packages. Thanks, i had a look at the latest commits in edward's git repository, changing from DebSrc 3.0 (quilt) to DebSrc 3.0 (native) and removing all the stuffs related with quilt. Aitor. In summary: 1) DebSrc 3.0 (native) generates only a tar.gz, containing also the debian folder. There is not a debian branch, and this is the reason why Edward changed the version number from 0.1.1-1 to 0.1.1 in debian/changelog. 2) DebSrc 3.0 (quilt), instead, generates an orig.tar.gz and a debian.tar.gz separately. So, the version number must include the version in the debian branch, this is 0.1.1-1 On the other hand, i cloned gdisk: https://git.devuan.org/pkg-admin/gdisk.git It uses the 3.0 (git) format, and now dpkg-guildpackage generates a binary file: *gdisk_1.0.0-2+devuan0.4.git* Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
