> My package (cvs-autoreleasedeb) creates its cron job in the postinst
> script, because it asks the user if it wants cvs-autoreleasedeb to be
> runned in cron. So, as the file is created in the postinst, it doesn't
> really belongs to the package.
How about including the cron job in the .deb, bu
> Here are the solutions I've considered:
>
> * merge them into one source package. This would diverge from
>upstreams distribution model.
>
> * copy the header file into wordnet-grind. This would have to
>be kept in sync manually.
>
> * build wordnet-dev and force its installation
> what should happen with programs, which currently runs only on i386
> architectures? Is it a good idea to upload such programs into the debian
> archive.
>
> Sure, I must simply change the Architecture field in the control file:
> Architecture: i386
>
> ...but is this generaly a good solution?
> Where is the documentation on how these debian.net domain hosts are used
> for and how these names are allocated?
http://db.debian.org/doc-mail.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> Can't exec "/tmp/config.19501": Permission denied at
> /usr/share/perl/5.8.0/IPC/Open3.pm line 159.
> open2: exec of /tmp/config.19501 configure failed at
> /usr/share/perl5/Debconf/ConfModule.pm line 44
> iptables failed to preconfigure, with exit status 255
Try setting TMPDIR. These files a
> > If debmake is out-of-date, what are the best tools used today to make
> > a package?
>
> dh_make.
I'd suggest $EDITOR, as dh_make does not handle all cases well, and it
is way too easy to leave silly buglets in.
(Of course, a combination of dh_make and $EDITOR is a viable
compromise :)
ms
> | I'd suggest $EDITOR, as dh_make does not handle all cases well, and
> | it is way too easy to leave silly buglets in.
> |
> | (Of course, a combination of dh_make and $EDITOR is a viable
> | compromise :)
>
> In every case, I'll have to run lintian (debuild do it automatically,
> isn't it?) t
> - open devices (in my case tty?, ttyUSB?)
You do not necessarily need root for that, provided that something
else set the permissions up. Otherwise, you might open it as root and
drop privileges.
> - open syslog (and/or logfile)
This certainly does not need root privileges. At least, logging t
Hi!
I am a bit unsure about how to name two upcoming packages of mine, and
wouldn't mind a few suggests :)
So, I have this one package (ccze), which is extensible via plugins,
and I have two, separately maintained, extensions: one for running
perl scriptlets, and another for running slang scriptl
> > Question is, how should I call these packages? ccze-perl and
> > ccze-slang, or libccze-perl and libccze-slang? Or something completely
> > different? (If someone says ccze-foo1 and -foo2, I'm going to rip his
> > hands off :P)
>
> I would suggest ccze-perl and ccze-slang. (Isn't libfoo-perl
> 1) simply resign it, and upload.
>
> 2) rebuild it from source each time
I always did the second, and when I had the time and energy, I also
checked the diff between his previous version, and the then-current one.
> Is there any easy way to strip away the signature of the sponsoree
> and sign
> Are there any packages that do this? In order to fully build gnu-crypto
> successfully, I will need to be able to have a seperate build directory
> than the source directory. I have been having trouble setting this up
> properly in debian/rules however, and I was wondering if there were
> any
unsubscribe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
he configure commandline
However, I think it would be better to fix gettext..
Cheers,
--
Gergely Nagy \ mhp/|8]
pgpTyWv4bFvqg.pgp
Description: PGP signature
Because the DAM processess people in the order he likes, it is
entirely up to him. It is not documented anywhere that people will be
processed in any order, and I think that's good.
Just be patient, and wait, as most of the people do.
--
Gergely Nagy \ mhp/|8]
pgp4d5tinT5a0.pgp
Descri
7;t look at the
package)..
Cheers,
--
Gergely Nagy \ mhp/|8]
pgp02ZijWXUpY.pgp
Description: PGP signature
should be either `Upstream Author' or `Upstream
Authors', not that ugly (s).
--
Gergely Nagy \ mhp/|8]
pgptnH0nHtq5Q.pgp
Description: PGP signature
ry time I check.
I'm attaching the typescript, if anyone has any idea, please share it
with me.
Thanks,
--
Gergely Nagy \ mhp/|8]
Script started on Sun Oct 7 19:20:54 2001
8638:[EMAIL PROTECTED]: /tmp/tama-test] dpkg-source -x tama_1.0-11.dsc
dpkg-source: extracting tama in tama-1.0
8
on me I didn't notice): in
status.c, there was a buffer (char tmp[MAXNAME]), which got overflown
if the age of the tamagotchi exceeded 99 hours (my tamagotchi is far
older than that), that's why no-one could reproduce it except me :)
tama 1.0-12 is in preparation.
Cheers,
-
nk.
Anyways, you'd better use Build-Conflicts, or (preferred) port your
package to g++ 3.0.
Cheers,
--
Gergely Nagy \ mhp/|8]
pgpjs4JrfWhTA.pgp
Description: PGP signature
At Sun, 28 Oct 2001 21:24:29 -0500,
Duncan Findlay <[EMAIL PROTECTED]> wrote:
>
> Are there any resources anywhere to help me create a package for kernel
> modules that will work with make-kpkg?
You might want to take a look at dh-kpatches..
pgpf78cRNgclF.pgp
Description: PGP signature
At Tue, 30 Oct 2001 22:55:02 +0200, Hugo van der Merwe <[EMAIL PROTECTED]>
wrote:
> (I made another new version, and only uploaded then. So this was never
> the "topmost paragraph". Might that be the problem?)
The closed bugs get listed in the .changes file you upload. You might
want to look at t
> case "$1" in
> configure)
> ldconfig
> W: iiwusynth: postinst-unsafe-ldconfig
> Sorry, I don't get it !
Lintian is cannot parse shell scripts, it checks for some common
variants, and warns if your version didn't match what it expected.
Since you do the right thing, just ignore this
> The problem is that I have a debian native package (so no .diff.gz) that
> came from a CVS repository and I'm guessing if there is a way to not
> delete by hand CVS and .cvs... files each time I check out to build the
> package.
>
Use cvs export, or cvs-buildpackage. I'd go with the latter one.
> On the one hand, I am not allowed to change sourceforge.conf on
> upgrade, and on the other hand the user expects a dpkg-reconfigure to
> really reconfigure his system. Yet both operations do the same thing
> (invoke postinst). What to do?
>
Doesn't dpkg-reconfigure pass a `reconfigure' arg
The best thing would be to convince upstream to Do The Right
Thing(tm). Meanwhile, you can add stuff like this to your install target
in debian/rules:
DMANDIR=$(CURDIR)/debian/foobar/usr/share/man
install: build-stamp
${MAKE} install DESTDIR=$(CURDIR)/debian/foobar
mv
I think something like this would do the trick:
if yadayada; then
db_input foo/bar
fi
To be put in the debian/package.config script.
pgpHyd4tNPpTQ.pgp
Description: PGP signature
> So, what's wrong with this picture? Should I build-depend on bison and
> generate the file in the build target, or should I modify the makefile
> to not delete the generated file? Both seem ugly to me. Is there
> something else I should do?
Since dpkg-buildpackage will call debian/rules clean, w
> make distclean should not delete the files in the first place. The
> distclean target should remove only generated files which are not included
> in the distribution (such as object code), and since this bison output is
> rightly included in the distribution, it should be left alone.
But it is
> I've the upstream original tarball on the base directory :
>gphoto-2.0beta3.tar.gz
> Note that the upstream is 'gphoto' without '2' but the debian package
> name is 'gphoto2'
> The source tree is in
>gphoto2-2.0beta3/
>
> But when I build I get
> dpkg-genchanges: warning: missing Sectio
> But the original one untar the source in gphoto_2.0beta3.
It doesn't matter where the original untars. dpkg-source (which
extracts the tar and applies the Debian diff) can cope with it. Just
rename the tarball, and you'll be set.
> You mean I should only rename it ?
Yep.
pgpaGsE2tzeHm.pgp
D
> Have I missed something?
Are you sure that the Maintainer and the Changed-By field in the
.changes file are the same?
If they are different, it will count as an NMU from dinstalls point of
view.
I'd simply bounce the installation-acknowledgement mail to the
relevant [EMAIL PROTECTED] address.
> How to do this? (I ask mainly about the way of creating Sources.gz files) Are
> there any automagical tools for this?
apt-ftparchive
> The same about binary packages?
apt-ftparchive :)
pgpggW9khD7F1.pgp
Description: PGP signature
> How does this work and how can I get it to retry autobuilding
> the package?
It will retry when it gets to it. I'll just wait and wouldn't worry
much.
pgpyATkkwNSlU.pgp
Description: PGP signature
> > > sbuild.conf changes occasionally upstream with new watches
> > > and alternatives and I'll be tracking that. The user
> > > shouldn't have to pay much attention to the file.
> >
> > And marking it as conffile allows that. If the user didn't change the
> > file, it will be replaced with the
> I have the files dict-web1913.config dict-web1913.templates in
> ../debian. After running debuild, these files, and control, are in
> ../debian/dict-web1939/DEBIAN.
>
> However, when the package is installed, var/lib/dpkg/info
> contains:
>/var/lib/dpkg/info/dict-web1913.dict-we
> If I install the package with dpkg -i, the debconf note is not
> displayed. I have DEBCONF_DEBUG set to ``developer'', but no messages
> are output by debconf. I do have a postinst that contains:
>
> #! /bin/sh
> set -e
> . /usr/share/debconf/confmodule
>
Only that?
Can you put the sou
> > > #! /bin/sh
> > > set -e
> > > . /usr/share/debconf/confmodule
> > >
> >
> > Only that?
>
> It is a dummy package to ease the transition from dict-web1913 to
> dict-gcide. The postinst was only added to try make debconf work from
> dpkg -i.
>
Looking at the files on master, I think
Thus spoke Bob Hilliard <[EMAIL PROTECTED]> on 2002-03-11 10:55:29:
> Gergely Nagy <[EMAIL PROTECTED]> writes:
>
> > Looking at the files on master, I think I know the problem. The quick
> > fix is to call db_get dict-web1913/reconf in your postinst. Also,
>
> I know how to make single packages (at least they seem to work), but have
> no idea where to start for a multipackage thing. What documentation could
> I read in order to understand the procedure, or what simple existing
> package could I have a look at?
>
dh_make can generate rules for multi-b
> > I didn't look at the file, but doesn't that deal with MacOS? If yes, I
> > doubt you need to install it into the .deb.
>
> Fink? http://fink.sourceforge.net/
And? Neither Fink, nor MacOS X is "in" Debian. If the Fink folks want
to use a debian package, they need to change it anyway, and can
re, there are CVS/ stuff in both the
diff.gz and the .orig.tar.gz. If you're rolling the .orig.tar.gz
yourself, I'd drop the CVS/ things...
Apart from these, the package looks quite fine, good work!
Cheers,
--
Gergely Nagy \ mhp/|8]
pgpsg5Fyum4Vr.pgp
Description: PGP signature
> The upstream of zblast released 1.2 after he released 1.2pre.
> The problem is that dpkg thinks 1.2 is older than 1.2pre.
> So I asked him what I should do. He picked 1.2.1 for
> the Debian package, saying "I very rarely use x.y.z
> versions, and I've never used them for zblast."
>
> Did I do s
> Can someone who understands the underlying setup give me some advice on how
> to deal with this? (Note: I realize the feature set I'm after isn't useful
> to most folks; I'm running the temporary archive for one of the new-arch
> ports which does not yet have space in the main archive, but we'd r
> allows any version
> -> changelog may be out of date if only "package" is upgraded
>
> depneds on the same version
> -> forces the user to download huge "package-data" on each upgrade
How about >= some-version? This way, you can bump the version in the
-data package when the license changes, et
> dpkg compresses the diff file differently every time
> I build .deb . The uncompressed .diff is same.
> Is this an expected behavior?
Yes. gzip puts a timestamp in the resulting file.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE
d
the problem may go unnoticed. It means a dummy make run tho, which might
not be wise if even a dummy run takes long.
(I think it is a justifiable compromise in many cases)
Oh, and your approach should work too, even if it is not the best way to
accomplis the goal.
Cheers,
--
Gergely Nagy
--
> My package (cvs-autoreleasedeb) creates its cron job in the postinst
> script, because it asks the user if it wants cvs-autoreleasedeb to be
> runned in cron. So, as the file is created in the postinst, it doesn't
> really belongs to the package.
How about including the cron job in the .deb, but
> How do I proceed here? Put MPlayer in the "suggests" line? Or create an
> informational dialog that will show a warning about the dependency?
Depends: mplayer
Section: contrib/
In other words, do depend on mplayer (mplayer CVS has debian/ in it
anyway), and put kmencoder in contrib. Packages in
> Here are the solutions I've considered:
>
> * merge them into one source package. This would diverge from
>upstreams distribution model.
>
> * copy the header file into wordnet-grind. This would have to
>be kept in sync manually.
>
> * build wordnet-dev and force its installation.
> what should happen with programs, which currently runs only on i386
> architectures? Is it a good idea to upload such programs into the debian
> archive.
>
> Sure, I must simply change the Architecture field in the control file:
> Architecture: i386
>
> ...but is this generaly a good solution?
> Where is the documentation on how these debian.net domain hosts are used
> for and how these names are allocated?
http://db.debian.org/doc-mail.html
> Can't exec "/tmp/config.19501": Permission denied at
> /usr/share/perl/5.8.0/IPC/Open3.pm line 159.
> open2: exec of /tmp/config.19501 configure failed at
> /usr/share/perl5/Debconf/ConfModule.pm line 44
> iptables failed to preconfigure, with exit status 255
Try setting TMPDIR. These files a
> > If debmake is out-of-date, what are the best tools used today to make
> > a package?
>
> dh_make.
I'd suggest $EDITOR, as dh_make does not handle all cases well, and it
is way too easy to leave silly buglets in.
(Of course, a combination of dh_make and $EDITOR is a viable
compromise :)
pgp
> | I'd suggest $EDITOR, as dh_make does not handle all cases well, and
> | it is way too easy to leave silly buglets in.
> |
> | (Of course, a combination of dh_make and $EDITOR is a viable
> | compromise :)
>
> In every case, I'll have to run lintian (debuild do it automatically,
> isn't it?) t
> - open devices (in my case tty?, ttyUSB?)
You do not necessarily need root for that, provided that something
else set the permissions up. Otherwise, you might open it as root and
drop privileges.
> - open syslog (and/or logfile)
This certainly does not need root privileges. At least, logging t
Hi!
I am a bit unsure about how to name two upcoming packages of mine, and
wouldn't mind a few suggests :)
So, I have this one package (ccze), which is extensible via plugins,
and I have two, separately maintained, extensions: one for running
perl scriptlets, and another for running slang scriptl
> > Question is, how should I call these packages? ccze-perl and
> > ccze-slang, or libccze-perl and libccze-slang? Or something completely
> > different? (If someone says ccze-foo1 and -foo2, I'm going to rip his
> > hands off :P)
>
> I would suggest ccze-perl and ccze-slang. (Isn't libfoo-perl
> 1) simply resign it, and upload.
>
> 2) rebuild it from source each time
I always did the second, and when I had the time and energy, I also
checked the diff between his previous version, and the then-current one.
> Is there any easy way to strip away the signature of the sponsoree
> and sign
> Are there any packages that do this? In order to fully build gnu-crypto
> successfully, I will need to be able to have a seperate build directory
> than the source directory. I have been having trouble setting this up
> properly in debian/rules however, and I was wondering if there were
> any
Simon Paillard writes:
> Furthermore, there is a lintian warning I can't get fixed:
> W: librohc-dev: duplicate-changelog-files
> usr/share/doc/librohc-dev/ChangeLog.gz usr/share/doc/librohc-dev/changelog.gz
If you remove ChangeLog from debian/docs, that should get it fixed.
dh_installchangelog
> "Jörg" == Jörg Frings-Fürst writes:
Jörg> I am looking for a sponsor for my package "libmongo-client"
Jörg> Package name: libmongo-client
Jörg> Version : 0.1.8-2
As the former maintainer and upstream, there are a few issues I see with
the packaging (also sent earli
> "Jörg" == Jörg Frings-Fürst writes:
>> * The build: target was there for a reason. Without it, we will build
>> the arch-indep stuff by default too, which is something we want to
>> avoid.
>>
>> For example, it will FTBFS on buildds, because they do not install
>> b
> "Jörg" == Jörg Frings-Fürst writes:
Jörg> Hi Martin,
Jörg> Am Mittwoch, den 08.07.2015, 09:47 -0400 schrieb Martin Michlmayr:
>> * Jörg Frings-Fürst [2015-07-08 14:58]:
>> > for the ftbfs bug I have upload a new version of
>> > libmongo-client/0.1.8-2[1].
>>
> "Ole" == Ole Streicher writes:
Ole> I want to grant DM rights for a package that I sponsored, and I am a
bit
Ole> confused how this works in real life.
Ole> According to [1], I should create a file with the following format:
Ole> --8<--
Hi!
I just had a quick look at the libtheft packaging on mentors, and
noticed a few things that at the moment, prevent me from sponsoring the
package. These are:
- I was unable to find the public part of your GPG key, thus, was unable
to verify the signature on the source package. Where can one
201 - 266 of 266 matches
Mail list logo
