Hi,
What the proper way to update debian/changelog, to increase the least
significant version # and add my change comment, and my id??
should I use the dch before dpkg-source -x *.dsc or after, to
streamline version # updating?
If after, how about the directory already created by
On Thu, 23 May 2013 04:13:12 +, T o n g wrote:
What the proper way to update debian/changelog, to increase the least
significant version # and add my change comment, and my id?
Please bear in mind that you'd be explaining to someone who has never
maintained a debian package before
On Thu, 23 May 2013 09:55:06 -0300, Eriberto wrote:
You should do what Prach Pongpanich said. And you can see what other
people done in their packages. A tip: . . .
Thanks Prach Eriberto for your answers.
I posted my OP, then I thought, since this is the first time I'm posting
here, better
On Thu, 23 May 2013 09:55:06 -0300, Eriberto wrote:
You can try make a test, put your package in mentors.debian.net and send
us the link, asking for a revision. I and others can help you to
understand the process.
I really appreciate the mentoring, and understand that each case would be
On Fri, 24 May 2013 02:14:39 +, T o n g wrote:
I'm a system learner. I.e., I learn through build up my overall
knowledge first, before rolling up my sleeves and dive in. While trying
to learn to maintain debian packages, I realized that there are A LOT to
learn, which is hard. And I found
On Fri, 24 May 2013 03:59:51 +, T o n g wrote:
Can anyone explain me in simple commands how I can build and test upload
this glimpse package please?
Hi, Thanks everyone who helped, including Charles.
You see, I didn't even know where to look for the old packages and didn't
know
On Sat, 25 May 2013 04:19:22 +, T o n g wrote:
Can anyone explain me in simple commands how I can build and test
upload this glimpse package please?
Hi, Thanks everyone who helped, including Charles...
Hi again,
I know it is recommended to always summarise after you get answers
Hi,
Is it the package maintainer's job to watch for upstream releases?
How does this Debian package upstream watching works *practically*?
From http://wiki.debian.org/debian/watch/ I have the impression that I
have to come up with a scheme to call the uscan program on regular basis,
whereas
Hi,
I had always been hoping to maintain some useful debian packages. Now
that I've successfully revived some abandoned debian packages, my
confident is gaining and want to pick up more.
I took a look at the orphaned package list, to my biggest surprise, there
are a *lot* of packages that I
Hi,
I'm using gpg-agent to remember and supply my GnuPG password when
building packages. But I'm still confused how gpg-agent works. I invoke
gpg-agent as:
eval $(gpg-agent --daemon)
It works sometimes. But what bothers me is that sometimes it doesn't
work. I.e., sometimes the building
Hi,
How can I fix the dpkg-deb: error: control directory has bad
permissions error?
I was simply trying to use pbuilder-satisfydepends with the emacs source
package.
apt-get source emacs24
cd emacs24*
sudo /usr/lib/pbuilder/pbuilder-satisfydepends
and this is what I get:
$ sudo
Hi,
The Debian package that I'm trying to create is libpam-ssh-agent
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595817
I need it to rsync files that belong to root between two systems as a
normal unprivileged user, without specifying password (the root account
is locked on both of
On Tue, 25 Jun 2013 20:45:15 -0700, Russ Allbery wrote:
If you need to customize *only* /etc/pam.d/sudo, I'm afraid that Debian
Policy says you're not allowed to do that. Basically, configuration
files are owned by a single package, and only that package may modify
it. That package *can*
On Fri, 21 Jun 2013 12:13:01 +0200, Élie Roux wrote:
there is already a debian/
up-to-date directory for the 2.3 version
(http://svn.gna.org/viewcvs/gregorio/tags/2.3/) which I would like to be
packaged for Debian; I think it should be quite an easy job...
Please tell me what to do!
Hi
/lintian-warning-native-package-dash-version-
help-195565821.html
http://www.mail-archive.com/debian-mentors@lists.debian.org/msg47311.html
The following is why and how I'm naming my files and directory:
On Wed, 26 Jun 2013 19:48:42 -0700, Russ Allbery wrote:
T o n g mlist4sunt...@yahoo.com writes
On Sat, 06 Jul 2013 13:21:07 +0600, Andrey Rahmatullin wrote:
How exactly should I name my files and directory in this case?
Also, how should I fix the other problems reported by lintian?
Did you read descriptions of tags lintian gave you?
Yes, not once, but several times. But because this is
On Sat, 06 Jul 2013 13:21:07 +0600, Andrey Rahmatullin wrote:
I: libpam-ssh-agent-auth source: missing-debian-source-format
That's your main problem. Without debian/source/format assumed format is
1.0 which means both no tar.bz2 support and possibility of making the
package native by
On Sat, 06 Jul 2013 20:52:48 +0600, Andrey Rahmatullin wrote:
I: libpam-ssh-agent-auth source: missing-debian-source-format
That's your main problem. Without debian/source/format assumed format
is 1.0 which means both no tar.bz2 support and possibility of making
the package native by
On Thu, 18 Jul 2013 23:19:10 +0600, Andrey Rahmatullin wrote:
If they provide a debian directory, that means to me that they have
done their best to make sure their software can at least be packed into
a Debian binary package in the limited Debian environment that they
choose to test. They
On Wed, 17 Jul 2013 21:17:49 +0200, Paul Gevers wrote:
On 17-07-13 20:30, Tong Sun wrote:
Re: Empty binary package
I'm wondering why the binary package built from my source package is
empty.
Here is what I've discovered so far:
- If I unpack the upstream tarball and build the
On Fri, 19 Jul 2013 08:38:49 +0200, Paul Gevers wrote:
On 19-07-13 05:13, T o n g wrote:
As said in OP,
Which I don't have anymore, so indeed please repeat it if you want my
help.
It was still included in the message that I previously replied.
- I unpack the upstream tarball and build
On Fri, 19 Jul 2013 21:57:14 +0200, Paul Gevers wrote:
- I then build the upstream into *source package* with 'debuild -S
-sa',
and then build the binary debian package *from this source package*.
The binary package built this way is however empty.
So how do you do the last step? And why is
On Sat, 20 Jul 2013 03:11:46 +, T o n g wrote:
Did you try to build debian binary package from there?
So please tell me what you mean with this sentence, I just don't know
what you mean.
build debian binary package from the source package that you just built.
I'll get back to you
On Sat, 20 Jul 2013 08:26:48 +0200, Paul Gevers wrote:
line, I put them there because I want to fix the following lintian
issues:
W: libpam-ssh-agent-auth source: debian-rules-missing-recommended-
target build-arch
W: libpam-ssh-agent-auth source: debian-rules-missing-recommended-
On Sat, 20 Jul 2013 18:17:20 +0200, Paul Gevers wrote:
I think these are the changes to the debian/rules in your mind, right?
[ . . . ]
Pretty close. . .
Thanks a lot again Paul for all the helps you gave.
My sponsor request has been sitting there for a while,
On Sun, 21 Jul 2013 12:21:26 +0200, Paul Gevers wrote:
There is probably more to fix, but I spent enough time already
Thanks a lot Paul for your detailed explanations. I'll look into them one
by one.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of
Hi,
The package that I want to pick up has a status:
The package should be updated to follow the last version of Debian
Policy (Standards-Version 3.9.4 instead of 3.8.3).
I never knew the details of Debian Policy before, but did try to read the
policy from 3.8.4 to 3.9.4, and find it a
Hi,
I found that Docker is the best tool for developing Debian/Ubuntu
packages, but seems no one has talked about it in Debian world. So here
is mine [1].
[1]
http://sfxpt.wordpress.com/2013/11/10/debianubuntu-package-developing-
with-docker/
If you build your packages with pbuilder, then
On Sun, 10 Nov 2013 19:36:16 -0500, Paul Tagliamonte wrote:
I found that Docker is the best tool for developing Debian/Ubuntu
packages, but seems no one has talked about it in Debian world
In fact, I have. I've got a few tools brewing for Debian that use
Docker. I've got it packaged and
Hi,
The package that I'm planning to maintain gives me the following error at
the end of the build:
for d in glimpse.1 glimpseindex.1 glimpseserver.1 ; do \
/usr/bin/install -c -m 444 $d /usr/share/man/man1 ; \
done
/usr/bin/install: cannot create regular file
On Mon, 11 Nov 2013 17:21:11 +0100, Dominik George wrote:
for d in glimpse.1 glimpseindex.1 glimpseserver.1 ; do \
/usr/bin/install -c -m 444 $d /usr/share/man/man1 ; \
done
Obviously, that should be ${DESTDIR}/usr/share/man/man1 .
So given the rules file posted in OP,
On Mon, 11 Nov 2013 23:40:46 +0600, Andrey Rahmatullin wrote:
for d in glimpse.1 glimpseindex.1 glimpseserver.1 ; do \
/usr/bin/install -c -m 444 $d /usr/share/man/man1 ; \
done
Obviously, that should be ${DESTDIR}/usr/share/man/man1 .
Hmm... I don't know if that is
On Mon, 11 Nov 2013 21:14:48 +0100, Dominik George wrote:
I took a look at the good build, which is glimpse-4.18.5, and I see:
for d in glimpse.1 glimpseindex.1 glimpseserver.1 ; do \
/usr/bin/install -c -m 444 $d
/export/build/glimpse/bld/
On Mon, 11 Nov 2013 12:11:53 -0800, Russ Allbery wrote:
Upstream doesn't appear to support DESTDIR in their build system and is
just trying to install things directly under prefix. You can possibly
work around this by setting prefix to $(CURDIR)/debian/tmp, but this
really should be fixed
On Fri, 15 Nov 2013 18:05:45 -0800, Russ Allbery wrote:
All usr/bin/ files have been successfully generated under
debian/glimpse/ usr/bin. Should I change all 'usr' to
'debian/glimpse/usr' without knowing why, or there is more proper way
to fix it?
It looks like you're installing (from
Hi,
How to determine build dependencies?
I was using 'dpkg-depcheck -d ./configure ...', but that seems to have
included much more than necessary.
For example for emacs, using motif instead of gtk3, I get [1], but I
don't think x11proto-randr-dev, libxinerama-dev, libxrandr-dev, libgl1-
Hi,
Last time I posted about that Docker being the best tool for developing
Debian/Ubuntu packages [1]. If you missed it, here is the recap:
- The reason Docker being the best tool for developing Debian/Ubuntu
packages is that, it gives you isolated pure pristine environments to
build
Hi,
I want to pack a simple perl script (http://proxytunnel.sourceforge.net/
files/pixelserv.pl.txt) as a package, but need your help.
I've checked out the
Debian Perl Policy
http://www.debian.org/doc/packaging-manuals/perl-policy/
and believe the script is fine.
But I don't know if there
Thanks a lot Robert for your comprehensive help. I found your
https://github.com/ramses0/xscreensaver-pi-hdmi/
an excellent example for me to follow as well.
Now,
On Sun, 01 Dec 2013 13:04:19 -0800, Robert Ames wrote:
I want to pack a simple perl script
(http://proxytunnel.sourceforge.net/
On Sat, 07 Dec 2013 09:19:37 +0800, Paul Wise wrote:
Don't symlink the manual page, that isn't useful at all. Just ignore the
warning until you or upstream have written a useful manual page.
OK. will do.
$(INSTALL) -m 644 file/dbab.addr $(etcdir)
This command installs the file
On Sat, 07 Dec 2013 10:20:57 +0800, Paul Wise wrote:
Only that the Makefile doesn't create a directory for it and assumes
that it exists already.
Ahhh!!!
THANKS!
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi,
I get some strange build error
- dpkg-source: error: cannot write /tmp/temp-lintian-lab-...
- unknown substitution variable ${shlibs:Depends}
Here are the details:
$ debuild -us -uc
[ . . . ]
/usr/bin/install -c -m 644 file/dbab.list- /export/build/dbab/git/
Thanks A LOT for the swift response.
On Sat, 07 Dec 2013 11:09:14 +0800, Paul Wise wrote:
- dpkg-source: error: cannot write /tmp/temp-lintian-lab-...
Something is wrong with your /tmp directory. It is probably either full
or has incorrect permissions.
I suspect it has something to do with
On Sat, 07 Dec 2013 03:28:14 +, T o n g wrote:
Well, I'll try building it outside docker...
building it outside docker is fine. So, will look into the problem
sometimes later...
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
Hi,
How to build to Debian source packages from Perl modules that have
(alien) dependencies? I.e., the dependencies are not exist yet.
- Can I specify multiple Perl modules to cpan2dsc/dh-make-perl?
- Or should I build the dependencies into binary packages and install
them first?
- Or should
Hi,
dh-make-perl is good to turn a CPAN module into Debian package.
However, it is still not clear to me how to maintain such built source
packages. Having fine-tuned all the control files under debian/ folder,
how can I make the changes to the new upstream release?
My upstream don't have
Hello all,
Could I get a packaging review for my newly adopted/built package
please?
The zh-autoconvert, Chinese encodings auto-converter, was orphaned more
than two years ago. Lintian reports 6 errors and 34 warnings about this
package
Hi,
I know that the best command options parser is the GNU getopt(3)
routines. I know that the GNU has a wrapper to generate C code around the
GNU getopt(3) routines -- the http://www.gnu.org/software/gengetopt/.
However, that wrapper, gengetopt, is dated and lacks of maintenance now.
It is
Hi,
I want to adopt the par2cmdline package, but on its QA page,
http://packages.qa.debian.org/p/par2cmdline.html
it says,
,-
| This package is part of the ongoing testing transition known as
| auto-libunwind. Please avoid uploads unrelated to this
| transition, they would likely delay it
On Sun, 22 Dec 2013 10:20:50 +0100, Niels Thykier wrote:
In the particular case, not much. libunwind is somewhat a special case...
Thanks a lot for your detailed explanation Niels!
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Hi,
I'm trying to manually converted my packages to 3.0 (quilt) source
format, and have gone so far as made dpkg-source recognize my efforts,
with some minor issues:
dpkg-source -b zh-autoconvert-0.3.16
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building
On Wed, 01 Jan 2014 20:54:40 +, T o n g wrote:
I'm trying to manually converted my packages to 3.0 (quilt) source
format,
and have gone so far as made dpkg-source recognize my efforts,
Having read https://wiki.debian.org/UsingQuilt over 3 to 5 times, and
starting from scratch step
Hi,
Is it possible to have a generic debian/rules that creates directories?
The upstream Makefiles was not designed to install into $DESTDIR but
to /, so it assumes /usr/bin exists, while that creates problems for me:
install -s -m 755 autogb /export/build/zh-autoconvert/bld/zh-
On Thu, 02 Jan 2014 00:23:42 +0100, Gergely Nagy wrote:
Is it possible to alter the following `debian/rules` file so that it
plays nicely with such upstream Makefiles?
Yes. You want to use dh_installdirs(1). I suggest you read its manpage.
Mind you, you won't need to touch debian/rules for
On Wed, 01 Jan 2014 21:00:18 -0800, Russ Allbery wrote:
There have been several replies to this, but none of them quite tell you
exactly what to do, so let me take a stab at that.
First, dh_installdirs is not actually useful for solving this particular
problem . . .
Thank you, thank you,
Hi,
I am doing test build of my binary package, and I get the following
warnings.
W: zh-autoconvert: empty-binary-package
I checked and it *is* empty, only containing copyright and changelog,
nothing else. I don't know why because it looks like the installation was
fine.
I've post the
On Thu, 02 Jan 2014 11:44:28 -0800, Russ Allbery wrote:
You're building multiple binary packages from the same source package.
This means that the Debian package build infrastructure has no inherent
way of determining which files go into which package. You have to tell
it explicitly.
Hi,
If I take a simple file (BSD-licensed), (greatly) improved it, and
include it in my package. How should I handle the situation?
- I should claim that the author of the new file is me, right?
- I should inherit the BSD-licensed, right?
- How to express that the new file was based on
On Thu, 02 Jan 2014 14:59:42 -0800, Russ Allbery wrote:
Usually I . . .
Thanks, as always!
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Thank you Michael for your review.
On Thu, 02 Jan 2014 17:44:33 -0600, Michael Shuler wrote:
1) incomplete source and debian packaging (symlinked to nowhere)
OK. didn't know that when I was using lndir. Easy fix.
2) native package (version 1.0.1 and debian/ dir should be separate from
Hi,
I'm trying to convert zh-autoconvert from pre-dh to using the dh for the
making.
I don't know how to fix the following problems:
W: zh-autoconvert: hardening-no-relro usr/bin/autogb
E: zh-autoconvert: pkg-has-shlibs-control-file-but-no-actual-shared-libs
W: zh-autoconvert:
Hi,
What's the cause (and fix) of the following error?
dpkg-source -b dbab-1.0.1
dpkg-source: error: can't build with source format '3.0 (quilt)':
version does not contain a revision
dpkg-buildpackage: error: dpkg-source -b dbab-1.0.1 gave error exit
status 255
Thanks
--
To
On Thu, 02 Jan 2014 17:44:33 -0600, Michael Shuler wrote:
1) incomplete source and debian packaging (symlinked to nowhere)
2) native package (version 1.0.1 and debian/ dir should be separate from
upstream source)
Hi everyone,
I've just uploaded a new version which should have fixed both
On Fri, 03 Jan 2014 22:02:00 +0100, Niels Thykier wrote:
I guess (without having it confirmed) that your package has a native
version (i.e. without a dash). For 3.0 (quilt) packages your package
must have a non-native version (e.g. 1.0.1-1).
BINGO. Thanks
--
To UNSUBSCRIBE, email to
On Fri, 03 Jan 2014 17:29:18 -0600, Michael Shuler wrote:
Prior to sending additional emails - make sure your build actually
works.
Oh I'm terribly sorry. Will do...
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Thu, 02 Jan 2014 16:20:57 -0500, Tong Sun wrote:
Package: sponsorship-requests Severity: normal
Dear mentors,
I am packing The Best Ad Blocking Method[1] into a Debian package
and am
looking for a sponsor for my package dbab, which starts with
reviewing it first.
[1]
Thanks.
On Fri, 03 Jan 2014 11:34:10 -0500, Stephen M. Webb wrote:
W: zh-autoconvert: hardening-no-relro usr/bin/autogb
To fix this one, you need to add $CPPFLAGS and $LDFLAGS to your linker
command line in your Makefile.
And add the following at the top of the Makefile as well:
# use
Hi,
pkg-has-shlibs-control-file-but-no-actual-shared-libs is sometimes
triggered for packages with a private shared library due to a bug in
Debhelper
That seems to have bitten me.
E: zh-autoconvert: pkg-has-shlibs-control-file-but-no-actual-shared-libs
W: zh-autoconvert:
On Sat, 04 Jan 2014 17:22:49 -0500, Stephen M. Webb wrote:
The instructions available on the web are for older versions of the
build infrastructure. The debhelper(7) manual page does mention
dpkg-buildflags flags are passed through at compat level 9, but it isn't
necessarily obvious what
On Sat, 04 Jan 2014 18:39:23 -0500, Stephen M. Webb wrote:
How can I make sure my building environment is at compat level 9?
From he debhelper(7) manpage:
Tell debhelper what compatibility level to use by writing a number to
debian/compat. For example, to turn on v9 mode:
%
Hi,
I'm having problem using lintian.
This was my previous question:
On Thu, 23 Jan 2014 15:49:31 -0500, Tong wrote:
On Thu, Jan 23, 2014 at 7:50 AM, Eriberto eribe...@eriberto.pro.br
wrote:
You have a lintian message yet:
I: shc: spelling-error-in-manpage usr/share/man/man1/shc.1.gz
On Tue, 28 Jan 2014 07:34:20 +0100, Niels Thykier wrote:
$ lintian -EviIL +pedantic --color auto --display-experimental
../*.dsc
[...]
I.e., when I invoke lintian manually, I didn't see problems reported
by debuild.
Lintian can check both source packages (*.dsc) or binary packages
Hi,
How can I do a git shallow clone from Debian anonscm git?
The project I want to clone is
http://anonscm.debian.org/gitweb/?p=collab-maint/ddclient.git;a=summary
in the package's description, the git url is
git://anonscm.debian.org/collab-maint/ddclient.git
Thus, I tried git clone
Hi,
I used the `dh_make` to create a new rules file, but found that what I
want to install are not in the final package.
Here is what the old rules file looks like:
install: build
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs
install -m 755
Hi,
Do I need to care about the lintian problems from the binary package that
I maintain/build?
For the following problems, I have no idea where they come from:
N: Processing binary package ddclient (version 3.8.2-1, arch all) ...
W: ddclient: using-imperative-form-in-templates
On Sat, 12 Jul 2014 09:27:32 +0200, Vincent Bernat wrote:
# main packaging script based on dh7 syntax %:
dh $@
override_dh_auto_install:
install -m 755 ddclient \
$(DESTDIR)/usr/sbin/ddclient
install -D -m 755 debian/ddclient.NetworkManager \
On Sat, 12 Jul 2014 13:14:23 +, T o n g wrote:
# main packaging script based on dh7 syntax %:
dh $@
override_dh_auto_install:
install -m 755 ddclient \
$(DESTDIR)/usr/sbin/ddclient
install -D -m 755 debian/ddclient.NetworkManager \
$(DESTDIR)/etc
On Sat, 12 Jul 2014 13:23:16 +, T o n g wrote:
override_dh_auto_install:
install -m 755 ddclient \
$(DESTDIR)/usr/sbin/ddclient
install -D -m 755 debian/ddclient.NetworkManager \
$(
)/etc/NetworkManager/dispatcher.d/50-ddclient
dh_auto_install
On Sat, 12 Jul 2014 09:36:34 +0200, Vincent Bernat wrote:
I think this warning hide another problem with your modifications is
that the SCRIPTSCOMMON tag doesn't get extended anymore. Ensure that
dh_installscripts-common is still executed.
Ah, you are right.
script -c debuild -i -us -uc -b
Hi,
I'm wondering if there is a central place that I can search for all Debian
change logs for all packages, to see if the same lintian problem I'm
having now have been dealt with before, and also see how exactly those
lintian problems are fixed.
Thanks
--
To UNSUBSCRIBE, email to
Hi,
What's that '-i' is for in the 'debuild -i' command?
I was looking for it in debuild dpkg-buildpackage man pages but still
wasn't sure what it is for.
The actual whole command I use is:
debuild -i -us -uc -b
I found that if I use -i I will get the following problems, whereas if -i
On Sun, 13 Jul 2014 12:02:05 +0200, Ross Gammon wrote:
I'm wondering if there is a central place that I can search for all
Debian change logs for all packages, to see if the same lintian
problem I'm having now have been dealt with before, and also see how
exactly those lintian problems are
On Sun, 13 Jul 2014 18:19:08 +0600, Andrey Rahmatullin wrote:
I used the `dh_make` to create a new rules file, but found that what I
want to install are not in the final package.
Here is what the old rules file looks like:
install: build
dh_testdir dh_testroot dh_clean -k
On Sun, 13 Jul 2014 18:18:21 +0600, Andrey Rahmatullin wrote:
I saw in the log,
...
dh_installdirs
debian/rules override_dh_auto_install
make[1]: Entering directory '/export/build/pkg/ddclient/bld/
ddclient-3.8.2'
install -m 755 ddclient \
/usr/sbin/ddclient
install -D -m 755
On Sun, 13 Jul 2014 22:29:37 +0600, Andrey Rahmatullin wrote:
dh_install(1) is a program, not a target.
install -m 755 ddclient \
$(DESTDIR)/usr/sbin/ddclient
install -D -m 755 debian/ddclient.NetworkManager \
$(DESTDIR)/etc/NetworkManager/dispatcher.d/50-ddclient
Hi,
Is it possible to separate gpg signing from package building?
As I'm still trying to learn Debian package building, I've found myself
fallen into this silly loop many times -- Thinking that the package would
be fine, I build it with gpg signing, but only to find out minutes later
that I
On Mon, 14 Jul 2014 00:26:22 +0200, Ross Gammon wrote:
On Sun, 13 Jul 2014 22:29:37 +0600, Andrey Rahmatullin wrote:
dh_install(1) is a program, not a target.
install -m 755 ddclient \ $(DESTDIR)/usr/sbin/ddclient
install -D -m 755 debian/ddclient.NetworkManager \
On Mon, 14 Jul 2014 04:06:16 +, T o n g wrote:
On Mon, 14 Jul 2014 00:26:22 +0200, Ross Gammon wrote:
On Sun, 13 Jul 2014 22:29:37 +0600, Andrey Rahmatullin wrote:
dh_install(1) is a program, not a target.
install -m 755 ddclient \ $(DESTDIR)/usr/sbin/ddclient
install -D -m 755
hi,
Please help me fix the lintian hardening-no-relro problem. My code is at
https://github.com/suntong001/histring (it is *very* small).
I tried to fix it myself, using the method from
https://wiki.debian.org/Hardening
and https://groups.google.com/forum/#!msg/debian-bollin/
On Mon, 25 Aug 2014 13:56:29 +0600, Andrey Rahmatullin wrote:
Please help me fix the lintian hardening-no-relro problem. My code is
at https://github.com/suntong001/histring (it is *very* small).
The proper way is just to bump debian/compat to 9.
I tried to ...
+DPKG_EXPORT_BUILDFLAGS =
On Thu, 28 Aug 2014 14:32:32 +0600, Andrey Rahmatullin wrote:
On Thu, Aug 28, 2014 at 12:50:23AM +, T o n g wrote:
Please help me fix the lintian hardening-no-relro problem. My code
is at https://github.com/suntong001/histring (it is *very* small).
The proper way is just to bump debian
[Re-try again as my previous question ended up as Message not available
in the mail archive]
Please help me fix the lintian hardening-no-relro problem. As mentioned
before, I've tried several ways myself but none worked. I've uploaded the
source package to
On Sat, 06 Sep 2014 14:03:10 +0600, Andrey Rahmatullin wrote:
Please help me fix the lintian hardening-no-relro problem. As
mentioned before, I've tried several ways myself but none worked. I've
uploaded the source package to
http://mentors.debian.net/debian/pool/main/h/histring/
Thanks for your response.
On Sun, 07 Sep 2014 16:55:14 +0600, Andrey Rahmatullin wrote:
On Sat, Sep 06, 2014 at 08:56:50PM +, T o n g wrote:
Yes, that's the first thing I tried, but still get the hardening-no-
relro problem:
https://github.com/suntong001/histring/blob/master/debian
On Thu, 11 Sep 2014 09:07:27 +0100, Azazel wrote:
Now that you've raised the debhelper compat level from 5 to 9, dh should
do the right thing. Just revert the changes in which you ripped out the
auto-tooling, e.g.:
OMG, you are my hero Azazel! histring is the package that I want to take
up
Hi,
My histring has this binary file contents changed error, how to fix it?
Here is the build log:
dpkg-source: info: using options from histring-1.1.0/debian/source/
options: --extend-diff-ignore=^Makefile$
fakeroot debian/rules clean
dh clean
dh_testdir
dh_auto_clean
On Fri, 12 Sep 2014 08:11:42 +0100, Azazel wrote:
Just out of curiosity, the source package I uploaded,
http://mentors.debian.net/debian/pool/main/h/histring/
histring_1.1.0-2.dsc
should be working according to your above principle, but why it is
failing?
Because you weren't using
On Fri, 12 Sep 2014 09:10:10 +0600, Andrey Rahmatullin wrote:
On Fri, Sep 12, 2014 at 02:28:34AM +, T o n g wrote:
Hi,
My histring has this binary file contents changed error, how to fix
it?
Here is the build log:
dpkg-source: info: using options from histring-1.1.0/debian
On Sun, 14 Sep 2014 12:14:13 +0600, Andrey Rahmatullin wrote:
The source is at https://github.com/suntong001/histring/
it is *very* small.
This package can't be built. You need to make sure you provide working
examples when you ask for help, otherwise people will stop helping you
quickly.
Hi,
My packages gives this warning:
dpkg-gencontrol: warning: Depends field of package dbab: unknown
substitution variable ${perl:Depends}
I am packaging Perl stuff, and I do use IO::Socket::INET in my code:
https://github.com/suntong001/dbab/blob/master/src/bin/dbab-svr
In
1 - 100 of 118 matches
Mail list logo
