Hello,
I am packaging sysinfo (#333680) and I have some problems with the
upstream tarball.
Upstream contains (limited list):
config.log
config.status
several .Po files
This is all cleaned up in the upstream distclean (which is called from
debian/rules clean), but Lintian complains about it
On Sun, Oct 16, 2005 at 05:00:01PM +0200, Stefano Zacchiroli wrote:
On Sat, Oct 15, 2005 at 09:48:26PM +0200, Christoph Berg wrote:
You can remove the transition package now; upgrades skipping a stable
release are not supported.
Interesting, is this policy or just common practice in past
Hi,
Adriaan Peeters wrote:
W: sysinfo source: configure-generated-file-in-source config.log
How can I resolve this without an override?
Not at all. It's an error upstream has made, but unless it affects the
build in a harmful way (which I doubt) I would just leave it at that and
ignore
Christoph Haas wrote:
On Saturday 15 October 2005 14:59, Bastian Venthur wrote:
[...]
kde-icons-nuovext
+ http://packages.qa.debian.org/k/kde-icons-nuovext.html
+ http://venthur.de/debian/nuovext/
closes: #324505 (Includes text files under /usr/share/icons)
Notes for
On Mon, 2005-10-17 at 10:38 +0200, Simon Richter wrote:
Furthermore I had to rerun automake because the original Makefile
installed extra doc files under /usr/doc/sysinfo. Is this the correct
solution or should I remove the files after running upstream make?
Both solutions are correct,
Hi,
Adriaan Peeters wrote:
sysinfodocdir = ${prefix}/doc/sysinfo
sysinfodoc_DATA = \
README\
COPYING\
AUTHORS\
ChangeLog\
INSTALL\
NEWS
EXTRA_DIST = \
$(sysinfodoc_DATA)\
How should I advise upstream to fix this (and remove the
On Mon, 17 Oct 2005, Simon Richter wrote:
Both solutions are correct, modifying the Makefile is easier to
understand for someone else looking at the package and will also show a
Modifying an *automake* generated makefile and easier to understand do not
belong in the same sentence.
Fixing
Hi, Bastian...
regarding kde-icons-nuovext...
On Monday 17 October 2005 13:10, Bastian Venthur wrote:
Christoph Haas wrote:
- it may be a matter of taste but I would not extract the upstream
tarball right into the debian/... directory. Why not using that file
as an *.orig.tar.gz.
On Sat, Oct 15, 2005 at 10:44:00AM +0300, Damyan Ivanov wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tommaso Moroni wrote:
The knights package uses dpatch to correct some mistakes in
po/de.po, thus generating a po/de.gmo which is different from the
upstream source. While this
Christoph Haas wrote:
Hi, Bastian...
regarding kde-icons-nuovext...
On Monday 17 October 2005 13:10, Bastian Venthur wrote:
Christoph Haas wrote:
- it may be a matter of taste but I would not extract the upstream
tarball right into the debian/... directory. Why not using that file
On Monday 17 October 2005 18:00, Bastian Venthur wrote:
Christoph Haas wrote:
Okay. Just keep in mind that you cannot change the orig.tar.gz which
is currently in Debian. You can only provide new *.diff.gz files for
the same upstream tarball. So it's more a todo when your upstream
Christoph Haas wrote:
Yes, that sounds like a rather good idea. Doesn't look too ugly and tricks
the version comparison system. :) If you don't know it already... see the
man page for dpkg. There is a nice option called --compare-versions
which allows you to find out whether a revision is
On Monday 17 October 2005 21:36, Bastian Venthur wrote:
Christoph Haas wrote:
I suggest you rather use dh_installchangelogs for that. Please see its
man page. (That means also removing the debian/docs file.)
The general problem here is, that upstream sometimes provides the
filenames of
Christoph Haas wrote:
On Monday 17 October 2005 21:36, Bastian Venthur wrote:
Christoph Haas wrote:
I suggest you rather use dh_installchangelogs for that. Please see its
man page. (That means also removing the debian/docs file.)
The general problem here is, that upstream sometimes
On Monday 17 October 2005 23:15, Bastian Venthur wrote:
Hehe, I guess my package is relatively perfect (and uploaded) now ;)
The $(CURDIR) is redundant in dh_installchangelogs. But I won't harass
you with that any more. :)
But one last question. What if upstream provides a README, which want
Hello,
I am an old-time debian user/sysadmin, but have never really attempted
to go deeper than that. I am currently massively deploying debian in the
company (a small telco/VoIP company in France) I now work for, and I am
facing issues with bonding and VLANs configuration.
In order to
Hello,
I am an old-time debian user/sysadmin, but have never really attempted
to go deeper than that. I am currently massively deploying debian in the
company (a small telco/VoIP company in France) I now work for, and I am
facing issues with bonding and VLANs configuration.
In order to
Thanks for all these comments. It's always a great feeling to discover
that someone took time to look at what you did - even if to report that
you did a lot of stupid things :)
I took them seriously, so I'll report everything that I noticed while
doing so. Please don't get me wrong - I'm
18 matches
Mail list logo
