On Wed, Jun 14, 2023 at 11:27 AM David Given wrote:
>
> The sad thing is that bazel, which is the least bad build system I've ever
> used, works in a way that's completely antithetical to how Debian wants to
> build things: it doesn't want to use host software for anything and will,
> e.g.,
On Wed, 14 Jun 2023 at 09:35, Paul Wise wrote:
[...]
> The upstream repo seems to use bazel as its build system, at least
> according to the README. Is that not usable here? The bazel tool
> appears to be packaged in bazel-bootstrap in Debian.
>
bazel-bootstrap is very old, unfortunately ---
On Tue, 2023-06-13 at 19:22 +0200, Oliver Reiche wrote:
> 1. Due to the missing build description, is it ok if the maintainer
> provides a Makefile for building the C++ libraries in ./debian?
...
> 4. Such a Makefile (and control file) will be quite lengthy.
The upstream repo seems to use bazel
Dear mentors,
Wookey and I are trying to come up with a sane concept to package the
googleapis project [1]. During our initial investigation a few
questions came up that we would like to discuss publicly.
BACKGROUND:
'googleapis' is a collection of protocol buffer [2] files, an
interface
Hello debian-mentors,
i'm in the process of packaging 'bolt', the thunderbolt 3 device
manager. I've pushed the current state of the package to salsa [0].
There are still some lintian warnings about missing copyright
informations, but those are about manpage files, dockerfiles,
2. The upstream tarball is 'nautilus_0.12-beta1-2.tar.gz', and the
changelog version in their packaging is '0.12-1ubuntu1'. I changed
this to '0.12.beta1.2', but now I realise that it will be detected as
an NMU (at least, lintian thinks it is).
This was due to a typo in the changelog, silly
Hi there,
I recently decided to take on the packaging of an SVN extension for
Nautilus, available at:
http://code.google.com/p/nautilussvn/
ITP: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469181 (I did
discuss it with Josselin Mouette in between the RFP - ITP)
The upstream authors have
Hi debian-mentors,
I ITP'ed xymtex ( http://bugs.debian.org/304714 ), which (assuming I can
clear up some licensing issues) will be my first LaTeX macro package. I
have a few questions for you while I wait for upstream to reply to my
email about licensing clarifications:
1) Some .sty files are
I'm not completely familiar with the Debian packaging standards for TeX
macros, but I'm very familiar with TeX in general, so I'll try to answer
the questions that are general and leave the Debian-specific questions for
others.
Kevin B McCarty [EMAIL PROTECTED] writes:
1) Some .sty files are in
El Sábado, 14 de Febrero de 2004 12:57, Tommaso Moroni escribió:
Hi!
While packaging my first kde application I had some problems/doubts:
Is there any way to convert the upstream docbook in a man page?
I tried with docbook-to-man and docbook-utils but they both didn't work.
Have a look at a
El Sábado, 14 de Febrero de 2004 12:57, Tommaso Moroni escribió:
Hi!
While packaging my first kde application I had some problems/doubts:
Is there any way to convert the upstream docbook in a man page?
I tried with docbook-to-man and docbook-utils but they both didn't work.
Have a look at a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 14 February 2004 11:57, Tommaso Moroni
[EMAIL PROTECTED] wrote:
Also, is it normal that the program doesn't install the manual in
KHelpCenter?
This is because your package install the KHelp files
in /usr/share/doc/HTML (per KDE
Paul Cupis schrieb:
$(MAKE) install DESTDIR=$(CURDIR)/debian/knights \
kde_htmldir=$(CURDIR)/debian/knights/usr/share/doc/kde/HTML
Thanks, this made my rules file much more transparent.
But it worked better to use kde_htmldir=/usr/share/doc/kde/HTML.
Is there a similiar solution for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 15 February 2004 20:17, Eike \zyro\ Sauer
[EMAIL PROTECTED] wrote:
Is there a similiar solution for icons?
There is kde_icondir, but...
ATM I do:
dh_install src/hi16-app-kdiff3.png
usr/share/icons/hicolor/16x16/apps/ dh_install
Paul Cupis schrieb:
Have I missed something? Can you try removing the referenced code from
debian/rules and seeing if the resulting package is correct?
I'm sure I had a compelling reason to do this some day
- but I can't remember it. And the package seems to be fine
with all those lines
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 14 February 2004 11:57, Tommaso Moroni
[EMAIL PROTECTED] wrote:
Also, is it normal that the program doesn't install the manual in
KHelpCenter?
This is because your package install the KHelp files
in /usr/share/doc/HTML (per KDE
Paul Cupis schrieb:
$(MAKE) install DESTDIR=$(CURDIR)/debian/knights \
kde_htmldir=$(CURDIR)/debian/knights/usr/share/doc/kde/HTML
Thanks, this made my rules file much more transparent.
But it worked better to use kde_htmldir=/usr/share/doc/kde/HTML.
Is there a similiar solution for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 15 February 2004 20:17, Eike \zyro\ Sauer
[EMAIL PROTECTED] wrote:
Is there a similiar solution for icons?
There is kde_icondir, but...
ATM I do:
dh_install src/hi16-app-kdiff3.png
usr/share/icons/hicolor/16x16/apps/ dh_install
Paul Cupis schrieb:
Have I missed something? Can you try removing the referenced code from
debian/rules and seeing if the resulting package is correct?
I'm sure I had a compelling reason to do this some day
- but I can't remember it. And the package seems to be fine
with all those lines
Hi!
While packaging my first kde application I had some problems/doubts:
Is there any way to convert the upstream docbook in a man page?
I tried with docbook-to-man and docbook-utils but they both didn't work.
Also, is it normal that the program doesn't install the manual in KHelpCenter?
The
Tommaso Moroni schrieb:
Is there any way to convert the upstream docbook in a man page?
I tried with docbook-to-man and docbook-utils but they both didn't work.
I think it has to be a docbook document explicitly meant to be converted
to a man page. Otherwise, you'll have to write a short one
Hi!
While packaging my first kde application I had some problems/doubts:
Is there any way to convert the upstream docbook in a man page?
I tried with docbook-to-man and docbook-utils but they both didn't work.
Also, is it normal that the program doesn't install the manual in KHelpCenter?
The
Tommaso Moroni schrieb:
Is there any way to convert the upstream docbook in a man page?
I tried with docbook-to-man and docbook-utils but they both didn't work.
I think it has to be a docbook document explicitly meant to be converted
to a man page. Otherwise, you'll have to write a short one
Hi Tommaso!
You wrote:
Should I wait for my application to be approved or look for a sponsor?
No, just go ahead and find a sponsor.
Should I report an ITP even if I'm not a Debian Developer?
Yes, definately.
--
Kind regards,
Hi Tommaso!
You wrote:
Should I wait for my application to be approved or look for a sponsor?
No, just go ahead and find a sponsor.
Should I report an ITP even if I'm not a Debian Developer?
Yes, definately.
--
Kind regards,
Hi!
I've recently passed all the steps in the Debian NM process, but I
haven't been approved by the DAM yet.
I'm interested in packaging some software, and one of the packages I'd
like to maintain is nearly ready.
Should I wait for my application to be approved or look for a sponsor?
Should
On Wed, Jan 08, 2003 at 05:45:28AM +0100, Tommaso Moroni wrote:
I've recently passed all the steps in the Debian NM process, but I
haven't been approved by the DAM yet.
That happens to quite a few people.
I'm interested in packaging some software, and one of the packages I'd
like to
Second question: I am making a .deb that is for any platform (it is a
perl script/config files. But when I do the dpkg-buidpackage it makes
the deb blahblahblah_i386.deb although in the config files I have stated
that is for any platform. What am I doing wrong?
In your control file, you
Second question: I am making a .deb that is for any platform (it is a
perl script/config files. But when I do the dpkg-buidpackage it makes
the deb blahblahblah_i386.deb although in the config files I have stated
that is for any platform. What am I doing wrong?
In your control file, you
On 19 Jan 2002 00:02:18 -0500
Scott [EMAIL PROTECTED] wrote:
Hello All,
Hello
I am not a Debian Package Maintainer (as of yet). And this is probably
not the right mailing list for these questions. If not, please let me
know so I can move the discussion to the right place.
this is the
On 19 Jan 2002 00:02:18 -0500
Scott [EMAIL PROTECTED] wrote:
Hello All,
Hello
I am not a Debian Package Maintainer (as of yet). And this is probably
not the right mailing list for these questions. If not, please let me
know so I can move the discussion to the right place.
this is the right
Hello All,
I am not a Debian Package Maintainer (as of yet). And this is probably
not the right mailing list for these questions. If not, please let me
know so I can move the discussion to the right place.
I have written some software that I am going to package up as .debs for
distrubution.
Hello All,
I am not a Debian Package Maintainer (as of yet). And this is probably
not the right mailing list for these questions. If not, please let me
know so I can move the discussion to the right place.
I have written some software that I am going to package up as .debs for
distrubution.
On 19 Jan 2002, Scott wrote:
First question (of many to come): using dpkg-buidpackage, I use the
option -kgpg key id and sign the package successfully (I think). How
on earth do I check to see if the .deb is signed and correctly signed?
During the process of the build, it asks me for my
Second question: I am making a .deb that is for any platform (it is a
perl script/config files. But when I do the dpkg-buidpackage it makes
the deb blahblahblah_i386.deb although in the config files I have stated
that is for any platform. What am I doing wrong?
Have you said any platform,
Hello All,
I am not a Debian Package Maintainer (as of yet). And this is probably
not the right mailing list for these questions. If not, please let me
know so I can move the discussion to the right place.
I have written some software that I am going to package up as .debs for
distrubution.
Hello All,
I am not a Debian Package Maintainer (as of yet). And this is probably
not the right mailing list for these questions. If not, please let me
know so I can move the discussion to the right place.
I have written some software that I am going to package up as .debs for
distrubution.
On 19 Jan 2002, Scott wrote:
First question (of many to come): using dpkg-buidpackage, I use the
option -kgpg key id and sign the package successfully (I think). How
on earth do I check to see if the .deb is signed and correctly signed?
During the process of the build, it asks me for my
Second question: I am making a .deb that is for any platform (it is a
perl script/config files. But when I do the dpkg-buidpackage it makes
the deb blahblahblah_i386.deb although in the config files I have stated
that is for any platform. What am I doing wrong?
Have you said any platform,
Hi Frederico!
You wrote:
I'm packaging sel (I did an ITP on it yesterday); I've gotten to the
point were the package correctly builds, goes trough lintian with no
warnings, installs ok and deinstalls ok.
Great.
The package is relatively simple (well, only one bin, and actually just
two
Bas Zoetekouw [EMAIL PROTECTED] wrote:
Hi Frederico!
You wrote:
The program has 'less' harcoded into it, and uses it has a pager to
display the help, so I made the package depend on less... butt a better
aproach would be to change the code so it would get the PAGER env var
and go with it,
On Wed, Nov 29, 2000 at 08:16:12PM +0100, Bas Zoetekouw wrote:
Hi Frederico!
You wrote:
I'm packaging sel (I did an ITP on it yesterday); I've gotten to the
point were the package correctly builds, goes trough lintian with no
warnings, installs ok and deinstalls ok.
Great.
The
On Wed, Nov 29, 2000 at 07:54:22PM +, Colin Watson wrote:
Bas Zoetekouw [EMAIL PROTECTED] wrote:
Hi Frederico!
You wrote:
The program has 'less' harcoded into it, and uses it has a pager to
display the help, so I made the package depend on less... butt a better
aproach would be
Hello all!
I'm packaging sel (I did an ITP on it yesterday); I've gotten to the
point were the package correctly builds, goes trough lintian with no
warnings, installs ok and deinstalls ok.
The package is relatively simple (well, only one bin, and actually just
two or three code files)... my
Hi Frederico!
You wrote:
I'm packaging sel (I did an ITP on it yesterday); I've gotten to the
point were the package correctly builds, goes trough lintian with no
warnings, installs ok and deinstalls ok.
Great.
The package is relatively simple (well, only one bin, and actually just
two or
Bas Zoetekouw [EMAIL PROTECTED] wrote:
Hi Frederico!
You wrote:
The program has 'less' harcoded into it, and uses it has a pager to
display the help, so I made the package depend on less... butt a better
aproach would be to change the code so it would get the PAGER env var
and go with it, in
On Wed, Nov 29, 2000 at 08:16:12PM +0100, Bas Zoetekouw wrote:
Hi Frederico!
You wrote:
I'm packaging sel (I did an ITP on it yesterday); I've gotten to the
point were the package correctly builds, goes trough lintian with no
warnings, installs ok and deinstalls ok.
Great.
The
On Wed, Nov 29, 2000 at 07:54:22PM +, Colin Watson wrote:
Bas Zoetekouw [EMAIL PROTECTED] wrote:
Hi Frederico!
You wrote:
The program has 'less' harcoded into it, and uses it has a pager to
display the help, so I made the package depend on less... butt a better
aproach would be to
G'Evening...
I've several question and problems with a package I'm trying to build.
Well, here we go.
1. In the rules file some directories /var/run/diablo/, /var/spool/news/
are 775 and not 755. How evil is that? Honestly I don't know whether
755 breaks anything. And it already was like
Alexander Koch wrote:
G'Evening...
I've several question and problems with a package I'm trying to build.
Well, here we go.
1. In the rules file some directories /var/run/diablo/, /var/spool/news/
are 775 and not 755. How evil is that? Honestly I don't know whether
755 breaks
I should follow up that I downloaded and looked at Diablo
(but did not compile because I don't have xmake).
Looking at the XMakefile.inc, it appears that the author specifically
disabled dynamic linking for GNU systems, but not for others.
It would be worthwhile to contact the author to get his
On Sun, 15 November 1998 14:20:49 -0500, Mitch Blevins wrote:
I should follow up that I downloaded and looked at Diablo
(but did not compile because I don't have xmake).
dists/slink/main/binary-i386/devel/xmake_1.05-1.deb ,-)
Looking at the XMakefile.inc, it appears that the author
That's quite a lot of detail :)
Perhaps this should all be written down somewhere and become the
Python Subpolicy? We already have such subpolicies for emacs and
menu files and probably some that I forgot. It could be distributed
in the python package and referenced from debian-policy.
Richard
I am in the process of packaging linbot - a python script to do link
verification. I have a few questions -
1. linbot.py and associated *.py files need to be installed in the same
directory. I was thinking of installing these under /usr/lib/linbot/
Is this the Right Thing to do?
2. I will ln
54 matches
Mail list logo
