Matthias Julius m...@julius-net.net writes:
Matthias Julius m...@julius-net.net writes:
I am looking for a sponsor for the new version 1.0~beta2-1
of my package krecipes.
It builds these binary packages:
krecipes - recipes manager for KDE
krecipes-data - recipes manager for KDE - data
Matthias Julius m...@julius-net.net writes:
I am looking for a sponsor for the new version 1.0~beta2-1
of my package krecipes.
It builds these binary packages:
krecipes - recipes manager for KDE
krecipes-data - recipes manager for KDE - data files
krecipes-doc - recipes manager for KDE
Sune Vuorela nos...@vuorela.dk writes:
On 2009-05-19, Matthias Julius m...@julius-net.net wrote:
I would really appreciate if someone could either help me to get my
krecipes package into Debian.
I am just not quite sure whether it is OK to hijack a package like
that from an unresponsive
Barry deFreese bdefre...@verizon.net writes:
Dmitrijs Ledkovs wrote:
I'm not a DD, but I think the correct way is to ping MIA team about it
and then after 2 weeks time you ping them again and they do a little
chat and come up with a solutions usally in your favor. Try that,
cause they record
Sune Vuorela nos...@vuorela.dk writes:
On 2009-05-19, Matthias Julius m...@julius-net.net wrote:
I just noticed that he actually cross-posted his messages to
pkg-kde-talk. There seems to be a little more human presence. Next
time I'll post there.
That's *NOT* a sponsering list
José Manuel Santamaría Lema panfa...@gmail.com writes:
On Martes, 19 de Mayo de 2009 23:43:50 Sune Vuorela escribió:
I don't know how close you follow debian development, but many members
of the debian kde people have been quite busy over the last month trying
to get kde in testing updated.
LI Daobing lidaob...@gmail.com writes:
3. consider remove the .la file if you already have a .pc file.
Is that a policy/best practice for library packages?
ok, consider there is no conclusion here. you can keep this file there. :)
But there seems to be a preference to remove it if rdepends
, dh_shlibdeps is complaining about a ton of unnecessary
dependencies. I have not yet tried to investigate where those are
coming from.
Kind regards
Matthias Julius
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Here we go ...
Paul Wise p...@debian.org writes:
On Tue, Apr 28, 2009 at 1:04 AM, Matthias Julius m...@julius-net.net wrote:
I would really be grateful if someone could take a look at this
package and possibly upload it for me.
You build-depend on libdb-dev, in sid that depends on libdb4.7
Paul Wise p...@debian.org writes:
On Sat, May 2, 2009 at 12:23 AM, Matthias Julius m...@julius-net.net wrote:
As explained in another post this should not affect the user since the
database format has not changed.
Please investigate the DB-upgrade thing Clint mentioned and forward
Matthias Julius m...@julius-net.net writes:
Paul Wise p...@debian.org writes:
I don't see anything in the maintainer scripts that would migrate the
db files. Does dnshistory or libdb handle upgrading the on-disk db
format? Or can libdb handle older versions of the on-disk db format?
I
Clint Adams sch...@debian.org writes:
Typically the fear which motivates this type of question is unfounded.
Looking at the dnshistory source code, it appears that the use of BDB
is trivial. Generally when the feature set you require could just
as easily have been satisfied by GDBM, there
Paul Wise p...@debian.org writes:
You build-depend on libdb-dev, in sid that depends on libdb4.7-dev but
the current dnshistory package is built against libdb4.6. Should you
add another debian/NEWS entry about this? I'm not sure what to do in
this situation, could you investigate?
I am not
Paul Wise p...@debian.org writes:
I don't see anything in the maintainer scripts that would migrate the
db files. Does dnshistory or libdb handle upgrading the on-disk db
format? Or can libdb handle older versions of the on-disk db format?
I was assuming the latter. But, reading
Matthias Julius li...@julius-net.net writes:
I am looking for a sponsor for the new version 1.3-2
of my package dnshistory.
It builds these binary packages:
dnshistory - Translating and storing of IP addresses from log files
The package appears to be lintian clean.
The upload would fix
sponsor twice in the last couple of
weeks. He did not respond to my emails.
I would be glad if someone uploaded this package for me.
Kind regards
Matthias Julius
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
In the light of the recent discussion about debian/copyright on -devel
I am wondering how verbose it actually needs to be. Given the
following files:
Files: foo.c
Copyright: 2006 Mr. X
License: GPL2+
Files: bar.c
Copyright: 2008 Mr. X
License: GPL2+
Files: baz.c
Copyright: 2005 Mr. Y
Neil Williams codeh...@debian.org writes:
On Mon, 13 Apr 2009 17:24:51 -0400
Matthias Julius li...@julius-net.net wrote:
I'd say condense all those down so that you only mention the one licence
once. There's no harm in collating copyright as long as the licences
are consistent (licence
Jonathan Wiltshire deb...@jwiltshire.org.uk writes:
On Mon, Apr 06, 2009 at 12:09:50PM +0200, Grammostola Rosea wrote:
make[3]: Entering directory `/tmp/buildd/jack-mixer-6'
GCONF_CONFIG_SOURCE= no --makefile-install-rule ./jack_mixer.schemas
^^
It's still that space
Paul Wise [EMAIL PROTECTED] writes:
Better to run a test suite or otherwise cause an FTBFS on
architectures where it is known to build broken or unusable binaries.
Not being fully portable isn't an RC bug and will not block testing
migration unless it is a regression and there is no good
Matthias Julius [EMAIL PROTECTED] writes:
Matthias Julius [EMAIL PROTECTED] writes:
I will address the other points you mentioned earlier and also the
issues Erik mentioned tonight (hopefully, maybe tomorrow) when I get
home.
OK, it took a little longer than two days, but I had a lot
Erik Schanze [EMAIL PROTECTED] writes:
IMO excluding of architectures is good if the program makes no sense on
it, e.g. because of missing hardware.
In your case it is a problem of unportable code, you should fix it
before.
Yes, generally I agree with you. But properly fixing the code
Matthias Julius [EMAIL PROTECTED] writes:
Dear mentors,
I am looking for a sponsor for the new version 1.19B-1
of my package varkon.
[...]
The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/v/varkon
- Source repository: deb-src http
Neil Williams [EMAIL PROTECTED] writes:
Try with:
1. Wrong directory for manual: ./usr/share/varkon/man/ should
be ./usr/share/doc/varkon-user-manual/
i.e usr/share/doc/$package_name/
Same for varkon-programmer-manual
Modify the doc-base files accordingly and change the symlink to the
Ricardo Mones [EMAIL PROTECTED] writes:
You can start reading the New Maintainer Guide [0], which will point you
to the Work-Needing and Prospective Packages [1], where you can look for
some orphaned package you may take care of.
[0]
Leo \costela\ Antunes [EMAIL PROTECTED] writes:
Andreas Hoenen wrote:
I have just uploaded dblatex 0.2.8-2 to mentors.debian.net [1].
Regarding the new lintian warning 'spelling-error-in-changelog' I have
opened a bug report [2].
[1] dget
a large /usr/share. For the
next release I will confirm with upstream that the files there are
really architecture independent and split it into a -data package if
appropriate or move the files into /usr/lib/varkon.
Kind regards
Matthias Julius
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
Russ Allbery [EMAIL PROTECTED] writes:
Agreed. I think debian/copyright should always refer to the exact version
of the GPL that the package says it's covered under and then document
whether only that version is permissable or whether the or later part is
available. (The exception is GPL
Russ Allbery [EMAIL PROTECTED] writes:
Dave Ewart [EMAIL PROTECTED] writes:
Yes, I do run lintian (and linda), but the spare machine I used to build
the packages was running Lenny at the time I built them. It's now Sid
;-)
You can also pin lintian in particular to unstable on a system
chaica [EMAIL PROTECTED] writes:
W: yougrabber source: changelog-should-mention-nmu
N:
N: When you NMU a package, that fact should be mentioned on the first
N: line in the changelog entry. Use the words NMU or Non-maintainer
N: upload (case insensitive).
N:
N: Maybe you didn't
Holger Levsen [EMAIL PROTECTED] writes:
./src/gnome-color-chooser.1 says the licence is GPL, which means GPL3, while
debian/copyright says the software is GPL2+... please fix.
Does it really mean GPL3? Do I have to compare the release date of a
software with the publishing date of the various
Russ Allbery [EMAIL PROTECTED] writes:
Charles Plessy [EMAIL PROTECTED] writes:
I am preparing a package using the makefile include for quilt, which
appeared in the quilt package starting from version 0.40. Only oldstable
has an inferior version. Would there be any benefit to remove the
Pierre THIERRY [EMAIL PROTECTED] writes:
Scribit Michael M. dies 02/04/2007 hora 07:48:
This sounds great, but could you please advice which brand of popcorn
meets the DFSG? I wouldn't want to violate the spirit of the
endeavor.
Probably only the one with traceability information, so you
Romain Beauxis [EMAIL PROTECTED] writes:
As far as I know it is not.
A native debian package can have a single tar.gz but not a package with
upstream releases..
This is also handy when uploading new debian releases since you don't have to
upload the orig tarball at each time.. How would
Charles Plessy [EMAIL PROTECTED] writes:
Having a simple and straghtforward patch system would lower the bar for
new packagers, as well as open the way to have .diff.gz files which
would only touch the debian directory, instead of containing a mixture
of packaging instructions, code changes,
This question is better placed on [EMAIL PROTECTED]
So, I am crossposting it there
Bernd Zeimetz [EMAIL PROTECTED] writes:
Hello,
since I'm not only a geek but also a photographer and GIMP user I've
decided to have a look at wnpp bug #398765 [1] and package the plugin
[2]. While packaging
Linas Žvirblis [EMAIL PROTECTED] writes:
Charles Plessy wrote:
I was kindly pointed out on -devel that the Debian menu system can
handle translations in its files.
No, it cannot. Not only that, but there also is no clear idea on HOW and
WHAT exactly it should do. There are simply way too
Daniel Baumann [EMAIL PROTECTED] writes:
Matthias Julius wrote:
- dget
http://mentors.debian.net/debian/pool/main/d/dnshistory/dnshistory_1.2-1.dsc
please fix the following things:
[...]
if you fix above things, i'm happy to sponsor it.
And I am happy that you are willing to do so
Daniel Baumann [EMAIL PROTECTED] writes:
Matthias Julius wrote:
This list was longer than I expected, but I appreciate that you took
the time to generate it. I hope I have fixed all the issues you have
pointed out.
everything, except:
* debian/copyright has a useless empty line
Daniel Baumann [EMAIL PROTECTED] writes:
Matthias Julius wrote:
Hmm, the opinion on this matter seems to be somwhat devided. Some
people suggest the revision should be increased every time an upload
is made to a public place like mentors.d.n.
if you insist on having it bumped, do it. i
Daniel Baumann [EMAIL PROTECTED] writes:
Matthias Julius wrote:
Sorry, my bad. I forgot to sign it and didn't wait for dupload to
finish.
no problem. checked again and uploaded it.
Thanks a lot.
if you need further sponsoring, contact me off-list
http://people.debian.org/~daniel
Yaroslav Halchenko [EMAIL PROTECTED] writes:
xpi and jar is the source -- it is just packaged with the other
than tar/gzip archiver and nested in each other to make our life fun ;-)
That is why there is no alternative tarball with the true source is
often provided (even if the license is GPL)
Panu Kalliokoski [EMAIL PROTECTED] writes:
I understand this, but it was exactly the same situation as with my
software packages -- they didn't have separate packaging and upstream
changes. There have been two times in their history when only packaging
information has been changed: when I
43 matches
Mail list logo
