Help with patching PackageKit for *BSD
Hi! I don't think this is the right place to request this help, but I don't know a better one at time... (RFH seems to be too "big") The problem is the following: PackageKit (Debian package "src:packagekit") recently became Linux-specific by accident, and I need someone who knows *BSD/portable-programming better than I do to make it compile on *BSD again. The problem is this code: http://gitorious.org/packagekit/packagekit/blobs/master/lib/packagekit-glib2/pk-spawn-polkit-agent.c On *BSD I get: pk-spawn-polkit-agent.c:24:23: fatal error: sys/prctl.h: No such file or directory compilation terminated. make[5]: *** [libpackagekit_glib2_la-pk-spawn-polkit-agent.lo] Error 1 But I don't know how to solve this otherwise. Hints and patches welcome! this is really the only issue which blocks PK on kFreeBSD at time. Many thanks for any help! Regards, Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKNHny_T=X=xoreuMOVaqG5-rh2eon=x-gv-afclowbmngf...@mail.gmail.com
RFS: Algoscore
Dear mentors, I am looking for a sponsor for my package "algoscore". Package name: algoscore Version : 081112-1 Upstream Author : Jonatan Liljedahl URL : http://kymatica.com/algoscore License : GPLv3 Section : sound It builds these binary packages: algoscore - Graphical environment for algorithmic composition algoscore-data - GUI for algorithmic composition (data files) The package appears to be lintian clean. The upload would fix these bugs: 553270 My motivation for maintaining this package is: Simply because a user requested it for his sound studio. I think we need more professional sound-studio software like this. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/a/algoscore - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/a/algoscore/algoscore_081112-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: Algoscore
Dear mentors, I am looking for a sponsor for my package "algoscore". Package name: algoscore Version : 081112-1 Upstream Author : Jonatan Liljedahl URL : http://kymatica.com/algoscore License : GPLv3 Section : sound It builds these binary packages: algoscore - Graphical environment for algorithmic composition algoscore-data - GUI for algorithmic composition (data files) The package appears to be lintian clean. The upload would fix these bugs: 553270 My motivation for maintaining this package is: Simply because a user requested it for his sound studio. I think we need more professional sound-studio software like this. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/a/algoscore - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/a/algoscore/algoscore_081112-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: Algoscore
On Tue, 03 Nov 2009 19:14:30 -0300, Felipe Sateler wrote: > On Tue, 2009-11-03 at 20:38 +0100, Matthias Klumpp wrote: >> Dear mentors, >> >> I am looking for a sponsor for my package "algoscore". > > Some comments, I'm no DD so I can't upload. > > * liblo-dev exists currently only in experimental. liblo0-dev, on the > other hand (the old package) is for version 0.23. I think you can only > upload to experimental currently. > * You need to build-depend on libsndfile1-dev > * No need to depend on csound, you don't use it at build time (and at > runtime? maybe only the library). > * Your standards-version is not uptodate. > * There are a bunch of unneeded links. You should try building with > --as-needed. > * The version should probably be prefixed with 0.0 or something in case > upstream wants to change versioning scheme in the future. > * The examples should be under /usr/share/doc/algoscore, > not /usr/share/algoscore. The same for the help files. Fixed everything. Thanks! Regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: libqtintf4
Dear mentors, I am looking for a sponsor for my package "libqtintf4". * Package name: libqtintf4 Version : 1.72Qt4.5.2-1 Upstream Author : (C) 2009 Jan Van Hijfte * URL : http://users.telenet.be/Jan.Van.hijfte/qtforfpc/fpcqt4.html * License : GPL Section : libs It builds these binary packages: libqt4intf-dev - Qt4 interface bindings libqt4intf5 - Qt4 interface bindings The package appears to be lintian clean. The upload would fix these bugs: 554177 My motivation for maintaining this package is that I use the library by myself in many projects and a lot of FPC-Qt4 projects depend on it. I would love to see this in Debian. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libqtintf4 - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libqtintf4/libqtintf4_1.72Qt4.5.2-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: libqtintf4
On Sat, 7 Nov 2009 11:59:10 + (UTC), Sune Vuorela wrote: > Looks like lgpl Oops, misstyped! The debian/copyright file is correct >> It builds these binary packages: >> libqt4intf-dev - Qt4 interface bindings >> libqt4intf5 - Qt4 interface bindings > > For which language? For Pascal, but a few other languages use it under Windows. (but just experimental) >> - dget >> http://mentors.debian.net/debian/pool/main/l/libqtintf4/libqtintf4_1.72Qt4.5.2-1.dsc > > The sources seem to contain many autogenerated files with moc. these > should be redone on build. Okay, I will fix that. > How are the bindings done? By manually writing each wrapper class or by > some 'secret script' that helps? Seems it is all written manually. > It looks like the qreal handling is too fragile, but might be just > enough to make it work on debian, and it seems to assume > that all people using Qt on arm uses 'qtopia'. (qtopia doesn't exist > anymore) I'm not a Qt-Developer (I never used Qt in C++), but I can forward your mail to the libqt4intf-developers. Maybe they can do something. > And wouldn't it make more sense to create different bindings for each qt > module? That's what the python, c#, ruby, php, lua, ... bindings are > doing. Maybe... I forward this mail to the module devs. > The build system looks like it is a buildd killer. It basically builds > all files at once, instead of build all files and then link them > together. Yes, this is really a strange thing - but it works. > I'm not sure I like this way of creating qt bindings, I_think doing what > the kdebindigs people, by using the 'smoke' intermediate library is a > better way ahead. The libqt4intf is also available for Windows and MacOS-X. I dont't think Smoke works on those platforms. > I'm not interested in pascal, so I won't sponsor this. This is a first > list of comments from some Qt person ;) Do you have to be interested in a package to upload it? I think the comments will help upstream a lot to make this package better. > /Sune > - maintainer of qt, kde, including kde and qt bindings for various >languages. So you know a lot about this :-P Best regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: libqtintf4
Hello again! I got the following reply on your comments for the libqt4intf interface library from Den Jean, a Qt4-Intf developer: Original Message From: Den Jean To: Items specific to the Qt widget set On Sunday 8 November 2009 17:22:36 Matthias Klumpp wrote: > Off-topic but still: yes, SMOKE does work on those platforms. was not the case when the pascal binding was created. > It'd be nice if these bindings were generated by SMOKE because that > would make its maintenance easier both for upstream and for you. big ? mark > SMOKE does a very good job, you need to have written a binding to understand why so few bindings used smoke at that time > it's faster than the official bindings fast enough for a scripting language, it would be sad for a fast static language like FPC. > Nokia is providing (QtScript, PySide). Take a look at > http://www.kdedevelopers.org/blog/89 (and > http://www.kdedevelopers.org/node/4079 in particular). > > So, why do we not use SMOKE? Den, where are you? :-P Why did PyQt, PySide,QtJambi, QtAda,QtC,QtScript .. etc not use smoke ? I have seen many Qt bindings come and go. PerlQt3 used smoke, why was it that years after the Qt4.0 release there was no PerlQt4 :-) But a Pascal Smoke Qt 4 binding would be complementary, though my binding fulfills its goals, a smoke binding would be way more complete. I am looking forward to see your results (and comment on the quality ;-) ) Understand that the other bindings try to provide a GUI library to their language, whilst Lazarus already has one. Providing Lazarus with a Qt backend (widgetset) is something entirely different. regards, Den Jean - So I don't see any blocks for this package. It is also impossible that all Pascal developer switch to new SMOKE bindings within a week. I still wait for a comment on the moc-files and the build-script issue. Maybe this can be fixed for the Debian packaging. Regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: libqtintf4
Hello again! I got this reply from Den Jean about the sources as statement: [...] Makefiles just serve to finally create calls to gcc, these calls I wrote by hand (there was no qmake in qt2) to more easily configure which Qt to use on the system. - 2 different Qt's on a system: The system Qt used to be a Qt3 not so long ago (Debian stable is still qt3/kde3) or an old unwanted Qt4 (eg Qt 4.0 and you wanted Qt 4.4) - cross compiling The makefile would just pickup the wrong one. But for distro packaging, the system t is ofcourse the target Qt. Both methods can coexist. I would propose to store the rpm and deb packages somewhere (fpc website?), most distros allow the addition of package sources. - one for latest stable lazarus in a stable source and - an often refreshed one in a testing/cooker package source The binding source is created by scripts, with many manual steps. A Qt binding is actually always alot of manual work (defining solutions to every exception, just read the so called typedef system of QtJambi or a kalyptus generator. [...] He will definitely nor re-write the interface using SMOKE (because it is undocumented and not necessary. Also many applications depend on the existing libqt4intf). I dont's see why this package can not be included into Debian. The only thing which blocks the inclusion is the lack of a make system like qmake, right? If at least one uses this software, it is relevant for Debian, I think. Maybe they will switch to SMOKE later, but today the interface library is a fixed standard if you want to create Qt4 applications with FPC. Do you have comments on packaging? Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: libqtintf4
On Wed, 11 Nov 2009 00:15:18 + (UTC), Sune Vuorela wrote: > [...] > > I haven't gotten to the packaging yet, because there is two things from > upstream that *needs* to be fixed. > 1) The moc gerenated files *needs* to be generated on build, else the > build might break on each new qt version. > 2) The build system needs to be done in a way that doesn't kill buildds > when it can be avoided. > > Anyways: > Why does it build-depend on libqt4-core ? > Why do you chmod +x the compile_lib script when you use bash to run it > anyways? > How do you make sure the build fails, if the compile_lib script fails? > > /Sune The patch for the build-script also includes "set -e" int the buildscript, so the package build fails if the build script fails. The libqt4-core dependency is useless, I removed it. The chmod +x is also not needed of course, I removed it to within the new upload. I forwarded the "must haves" to the developers, maybe they'll fix them. Thanks! Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: libqtintf4 (ping)
Dear mentors, I am looking for a sponsor for my package "libqtintf4". * Package name: libqtintf4 Version : 1.72Qt4.5.2-1 Upstream Author : (C) 2009 Jan Van Hijfte * URL : http://users.telenet.be/Jan.Van.hijfte/qtforfpc/fpcqt4.html * License : GPL Section : libs It builds these binary packages: libqt4intf-dev - Qt4 interface bindings libqt4intf5 - Qt4 interface bindings The package appears to be lintian clean. The upload would fix these bugs: 554177 My motivation for maintaining this package is that I use the library by myself in many projects and a lot of FPC-Qt4 projects depend on it. I would love to see this in Debian. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libqtintf4 - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libqtintf4/libqtintf4_1.72Qt4.5.2-1.dsc I would be glad if someone uploaded this package for me. The package is lintian-clean. There were some concerns about the build-script, but because it's a really small lib there should be no problem in building this. A qmake-project as been created, but the application then needs a lot more time to be compiled. I decided to keep the small efficient build script this time. In future versions the lib may break the API/ABI to split up into different libs for every Qt library, but at time LCL apps need the current library. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: libqtintf4 (ping)
Hello again! After some work with upstream, all problems seem to be fixed now. The project contains a qmake-file, moc-files are generated automatically and buildscript fails on error. If upstream publishes the qmake-version of libqt4intf in a tarball with upstream-version in name I will fix the watch file too. Sune, could you please check the project if there's something left to do? Great thanks! Matthias Klumpp P.S: Now building the project takes over 12 minutes. You can fetch a coffee while it compiles. On Sat, 19 Dec 2009 11:09:40 + (UTC), Sune Vuorela wrote: > On 2009-12-18, Matthias Klumpp wrote: >> The package is lintian-clean. There were some concerns about the >> build-script, but because it's a really small lib there should be no >> problem in building this. > > The way it is built, it takes around 1G of memory to build. This *needs* > to be fixed. it might be a small lib, but the way it is built is just > plain wrong. Especially since this can be easily fixed. > > > The moc output files *must* be regenerated on build, else you end up > with issues like: > > In file included from qtpas.cpp:370: > lib/hooks//qwebsettings.cpp_mk:14:2: error: #error "This file was > generated using the moc from 4.5.2. It" > lib/hooks//qwebsettings.cpp_mk:15:2: error: #error "cannot be used with > the include files from this version of Qt." > lib/hooks//qwebsettings.cpp_mk:16:2: error: #error "(The moc has changed > too much.)" > > from next Qt upload. > > > and the build script *needs* to be fixed so that it actually fails when > build fails. > > dpatch apply-all > applying patch 01_buildscript.patch to ./ ... ok. > bash /tmp/libqtintf4-1.72Qt4.5.2/compile_lib.sh > Please Modify location of Qt4 in this script > touch build-stamp > fakeroot debian/rules binary > dh_testdir > dh_testroot > dh_clean -k > dh_installdirs > dh_install > dh_install: libqt4intf5 missing files (libqt4intf.so.*), aborting > > /Sune -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: libqtintf4 (ping)
Hello again! After some work with upstream, all problems seem to be fixed now. The project contains a qmake-file, moc-files are generated automatically and buildscript fails on error. If upstream publishes the qmake-version of libqt4intf in a tarball with upstream-version in name I will fix the watch file too. Sune, could you please check the project if there's something left to do? The new package was pushed to Debian mentors. Great thanks! Matthias Klumpp P.S: Now building the project takes over 12 minutes. You can fetch a coffee while it compiles. On Sat, 19 Dec 2009 11:09:40 + (UTC), Sune Vuorela wrote: > On 2009-12-18, Matthias Klumpp wrote: >> The package is lintian-clean. There were some concerns about the >> build-script, but because it's a really small lib there should be no >> problem in building this. > > The way it is built, it takes around 1G of memory to build. This *needs* > to be fixed. it might be a small lib, but the way it is built is just > plain wrong. Especially since this can be easily fixed. > > > The moc output files *must* be regenerated on build, else you end up > with issues like: > > In file included from qtpas.cpp:370: > lib/hooks//qwebsettings.cpp_mk:14:2: error: #error "This file was > generated using the moc from 4.5.2. It" > lib/hooks//qwebsettings.cpp_mk:15:2: error: #error "cannot be used with > the include files from this version of Qt." > lib/hooks//qwebsettings.cpp_mk:16:2: error: #error "(The moc has changed > too much.)" > > from next Qt upload. > > > and the build script *needs* to be fixed so that it actually fails when > build fails. > > dpatch apply-all > applying patch 01_buildscript.patch to ./ ... ok. > bash /tmp/libqtintf4-1.72Qt4.5.2/compile_lib.sh > Please Modify location of Qt4 in this script > touch build-stamp > fakeroot debian/rules binary > dh_testdir > dh_testroot > dh_clean -k > dh_installdirs > dh_install > dh_install: libqt4intf5 missing files (libqt4intf.so.*), aborting > > /Sune -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
How to handle source code dependencies?
Hi! I'm packaging a project at time which uses the FPC compiler and the GLScene ( http://glscene.org ) component set. The problem is: GLScene is just required once for building the package. The resulting binary does not need it. How should I handle this dependency? Do I have to create a package "glscene-src", which is just needed at compile-time? Or should I include the GLScene package in the project directory? Regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: How to handle source code dependencies?
It is not my project, but another one I'd like to package. GLScene is a collection of Pascal components to make OpenGL usable in those applications *very* easily. It contains a lot of classes and helper scripts the program needs to compile. Those scripts are integrated in the resulting binary. GLScene does not have an own binary. The binary of the applications will depend on OpenGL. It's the same if someone writes e.g. a set of classes to make access to PulseAudio in a C application easier. The binary will depend on PulseAudio, but not on the set of components you used. My problem is: GLScene is an IDE plugin, which integrates with the FPC IDE Lazarus. So - of course - the developer does not ship GLScene in his source code. If I want to package this project I have to get GLScene from somewhere to make the compile process work. Possible solutions would be to include the GLScene code directly into the project's source dir. If I do this, the package would get a huge diff file, cause the whole GLScene code was added. Another solution I could imagine is to package the GLScene code in a separate package, let it install into /usr/share/pascal or directly into the IDE and compile the application with this GLScene version. (This would also be good for other projects which use GLScene in Debian) So, what is the right way to do this? Matthias On Mon, 28 Dec 2009 11:05:26 +0800, Paul Wise wrote: > Please explain the situation in more detail. Why is the source code > required at build time? Why does the resulting binary not need > glscene? It sounds like the right thing to do would be to change your > project so that it builds against glscene in the normal way and > depends on it at runtime. Embedded code copies are never the right > thing to do, so don't include a copy of glscene in your project. > > -- > bye, > pabs > > http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: How to handle source code dependencies?
On Mon, 28 Dec 2009 15:21:10 -0300, Nicolas Alvarez wrote: > > Does Pascal have no notion of a shared library? > It has, but the GLScene solution does not use it. > Nope, that set of components would be in a separate shared library and the > application would dynamically link to it *and* PulseAudio. Unless that > library happens to be "header-only" (very rare in C, more common with C++ > template libraries). Could be done in this way, but in the case of GLScene it is some kind of IDE plugin. It contains a set of classes, not only a header for a library. Also, the C ABI does not allow classes, so if the GLScene team would move all relevant parts to a shared library, they would need to create a flat API without direct use of objects. I never used GLScene. GLScene integrates directly into the IDE, but it can also be used without it. I've seen a similar behavior in Java applications which included the whole code for a 3D engine directly into the application. Details about GLScene: http://wiki.lazarus.freepascal.org/index.php/GLScene -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: How to handle source code dependencies?
On Mon, 28 Dec 2009 21:35:50 +0200, George Danchev wrote: > > I'm not quite sure what a flat API means and whether you mean objects as > instances and classes as types here, but if that could not be explored in > the > sense of separate compilation and further dynamic linkage, then it is not > that > helpful. object == instance class == type Flat API means that you don't have classes to use but a set of "flat" functions which receive just pointers to an object. (like you have the class "Foo" which has the function "do_something". The lib will contain a "gpointer new_foo()" function and a "foo_do_something(gpointer obj)" function to work with the object. Normally you would access the object directly in your programming language, here you work with a pointer) But this is not really the subject of this entry... The problem is that a lot of Pascal developers include 3rd-party components directly into their source code. It is not common to move all functions into a separate library. > ... which does not mean it is a very good idea to do so. I don't know what > to > suggest, but chances are you spend your time with that approach, and then > you > realize that no sponsor would upload it the way it is. Not any > DFSG-compliant > software worth packaging, in my opinion. You're right with this... I created a package for GLScene (just a trial). The GLScene developers say the project is licensed under MPL, but I find parts of GPL and LGPL in the software too. Also there is no list of upstream authors. The worst thing is that GLScene needs a lot of manual work to integrate it into the IDE. I worked with Debconf for this, but the last problems are not worth the effort. So I contacted upstream about this. Maybe the affected code will be included directly into the source tarball. This would solve all GLScene problems. If this is not possible I better wait some months until the GLScene devs improved the IDE integration. Thank you for your help! Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: Algoscore (ping)
Dear mentors, I am looking for a sponsor for my package "algoscore". Package name: algoscore Version : 0.081112-1 Upstream Author : Jonatan Liljedahl URL : http://kymatica.com/algoscore License : GPLv3 Section : sound It builds these binary packages: algoscore - Graphical environment for algorithmic composition algoscore-data - GUI for algorithmic composition (data files) The package appears to be lintian clean. The upload would fix these bugs: 553270 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/a/algoscore - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/a/algoscore/algoscore_081112-1.dsc I would be glad if someone uploaded this package for me. This is just a ping. I changed all things which were problematic (like the strange version numer). Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: easymp3gain
Dear mentors, I am looking for a sponsor for my package "easymp3gain". * Package name: easymp3gain Version : 0.5.0-1 Upstream Author : Thomas Dieffenbach * URL : http://sourceforge.net/projects/easymp3gain/ * License : GPLv2 Section : sound It builds these binary packages: easymp3gain-gtk - GUI interface for MP3Gain, AACGain and VorbisGain The package appears to be lintian clean. The upload would fix these bugs: 563175 My motivation for maintaining this package is: I know upstream well, we work on some projects together. So it would be easy for me to contribute patches for this package. I also use eMP3Gain by myself: It's a valuable, well known tool in the OSS world and it got good reviews at Sourceforge. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/e/easymp3gain - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/e/easymp3gain/easymp3gain_0.5.0-1.dsc I would be really glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: easymp3gain
Hello! Thanks for reviewing the package! > * debian/control: > - - Please expand your long description, it is a bit short. > - - Write "mp3,ogg,mp4" as "mp3, ogg and mp4" please > > * debian/rules: > - - Use dh_lintian to install your override file > - - Remove the useless newlines and whitespaces at EOL Changed. > Currently the package is not buildable, because of #563236. This is really annoying. I built the package with my of version of FPC and Lazarus packages which do not have this error... Today FPC 2.4.0 was released, so the problem will vanish if the new version gets packaged for Debian and Lazarus is rebuilt. I uploaded the new version of easyMp3Gain. Freundliche Grüße und frohes neues Jahr / Kind regards and a happy new year Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: easymp3gain
Hello! Thanks for reviewing the package! > * debian/control: > - - Please expand your long description, it is a bit short. > - - Write "mp3,ogg,mp4" as "mp3, ogg and mp4" please > > * debian/rules: > - - Use dh_lintian to install your override file > - - Remove the useless newlines and whitespaces at EOL Changed. > Currently the package is not buildable, because of #563236. This is really annoying. I built the package with my of version of FPC and Lazarus packages which do not have this error... Today FPC 2.4.0 was released, so the problem will vanish if the new version gets packaged for Debian and Lazarus is rebuilt. I uploaded the new version of easyMp3Gain. Freundliche Grüße und frohes neues Jahr / Kind regards and a happy new year Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: easymp3gain
Hi again! Bug #563236 has been fixed, easyMp3Gain should build now. Regards Matthias Klumpp The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/e/easymp3gain - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/e/easymp3gain/easymp3gain_0.5.0-1.dsc -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: easymp3gain
Hi again! Bug #563236 has been fixed, easyMp3Gain should build now. Regards Matthias Klumpp The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/e/easymp3gain - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/e/easymp3gain/easymp3gain_0.5.0-1.dsc -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: easymp3gain
Hi! > P: easymp3gain source: source-contains-svn-control-dir lang/.svn > - - Just notify and punch upstream, to remove the .svn dirs with his next > release tarballs prop. Woops! Why wasn't this information shown to mee too? Maybe I should update my lintian... > W: easymp3gain-gtk: binary-without-manpage usr/bin/easymp3gain > - - Yep, just a missing manpage, those are important and also interesent > for upstream easyMp3Gain is a GUI application, it does not have any command line arguments. Is it really necessary to write a manpage, and if it is, who should write it? Upstream or me? > I: easymp3gain-gtk: desktop-entry-contains-encoding-key > /usr/share/applications/easymp3gain.desktop:2 Encoding Submitted to upstream, will be fixed soon. > I: easymp3gain-gtk: unused-override embedded-zlib > - - So and so those are not allowed, but now this isn't the case anymore > and just remove the dead override. Hmm... This override was necessary last time I compiled it, cause FPC embedded the ZLib and there was no flag to turn it off... I will remove the override, it does not seem to be necessary for now. Thanks and kind regards Matthias > The package can be found on mentors.debian.net: > - URL: http://mentors.debian.net/debian/pool/main/e/easymp3gain > - Source repository: deb-src http://mentors.debian.net/debian unstable > main > contrib non-free > - dget > http://mentors.debian.net/debian/pool/main/e/easymp3gain/easymp3gain_0.5.0-1.dsc -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: easymp3gain
Hi! On Mon, 11 Jan 2010 16:28:55 -0200, Rogério Brito wrote: > Hi, Mattias. > > On Jan 11 2010, Matthias Klumpp wrote: >> easyMp3Gain is a GUI application, it does not have any command line >> arguments. > > Then, please just state it for people using the manpages. The first > thing that I do when I get a new package is to look at the manpage of > the main executable. > > (Which I, BTW, assume is called the same as the package name, with all > lowercase characters, in the best Unix tradition). Okay, the I'll write one and do this also for some other projects I manage (just in case...) I do always check manpages first, but I never tried to look at a manpage of a GUI-app. Thanks! Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: libqt4pas
Dear mentors, I am looking for a sponsor for my package "libqt4pas". * Package name: libqt4pas Version : 2.0rcQt4.5.3-1 Upstream Author : Jan Van Hijfte * URL : http://users.telenet.be/Jan.Van.hijfte/qtforfpc/fpcqt4.html * License : LGPL with static linking exception Section : libs It builds these binary packages: libqt4pas-dev - Qt4 interface bindings libqt4pas5 - Qt4 interface bindings The package appears to be lintian clean. The upload would fix these bugs: 554177 This package is necessary to build FPC/LCL Pascal applications against Qt4. It would make lots of FPC apps able to be compiled for the KDE/Qt platform and fix some bugs depending on this. The package was previously known as "libqtintf4" and had some problems (MOC-files in source-code etc.), which have now been fixed by upstream. I use the lib by myself and I have a little bit C++ and very long Pascal development experience. I also work close to upstream, who changed everything which was missing for this package. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libqt4pas - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libqt4pas/libqt4pas_2.0rcQt4.5.3-1.dsc I would be really glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: easymp3gain
Hi! > - -IE --pedantic on the *.changes file ;-) Thanks, I didn't know that command... Better check all my packages with it next time. > Who wants to write it? :) > And yes every binary needs a manpage, if it is missing, it is a bug. I read about a decision to add a manpage to every binary in Debian packages some months ago... But then I met some developers who said something like "ignore this warning", so I was not sure anymore :-P I added a manpage and fixed all other problems, lintian is quiet now! The package has been uploaded to Debian mentors again. Kind regards Matthias Klumpp The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/e/easymp3gain - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/e/easymp3gain/easymp3gain_0.5.0-1.dsc -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: easymp3gain
> Thanks, I have uploaded it. Thanks for uploading! Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: libqt4pas - Qt4 interface bindings for Pascal (ping)
Dear mentors, I am looking for a sponsor for my package "libqt4pas". * Package name: libqt4pas Version : 2.1Qt4.5.3-1 Upstream Author : Jan Van Hijfte * URL : http://users.telenet.be/Jan.Van.hijfte/qtforfpc/fpcqt4.html * License : GPL with static linking exception Section : libs It builds these binary packages: libqt4pas-dev - Development files for Qt4Pas libqt4pas5 - Qt4 interface bindings The package appears to be lintian clean. The upload would fix bug 554177 and some feature requests of other packages. The library makes it possible to compile Qt4 interfaces for FPC/Lazarus applications like easyMp3Gain or WinFF. Especially KDE users would benefit from this lib. I worked with upstream to fix all issues which were in this source code and there should be no problems anymore which prevents this package from being uploaded. (Except one: Could someone please look if the lintian-override is correct?) The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libqt4pas - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libqt4pas/libqt4pas_2.1Qt4.5.3-1.dsc I would be really glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/f8ba27c3a84437da16782cfa7abd2...@mb8-2.1blu.de
RFS: easymp3gain (updated package), fixes RC bug
Dear mentors, I am looking for a sponsor for the new version 0.5.0-3 of my package "easymp3gain". It builds these binary packages: easymp3gain-gtk - GUI interface for MP3Gain, AACGain and VorbisGain The package appears to be lintian clean. The upload would fix these bugs: 577324 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/e/easymp3gain - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/e/easymp3gain/easymp3gain_0.5.0-3.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5e416aecafd3b58819556614d29a4...@mb8-2.1blu.de
Re: RFS: easymp3gain (updated package), fixes RC bug
> Hi, > > +Build-Depends: debhelper (>= 7), cdbs, quilt, fpc (>= 2.4.0), lcl > (>=0.9.28.2), lcl-gtk2 > - You don't need to depend on quilt anymore if you are using 3.0 (quilt) > > There is also an lintian error, which can not be overwritten and would > reject it from the repository: > E: easymp3gain-gtk: embedded-zlib ./usr/bin/easymp3gain > > this is a must fix! Hi! Unfortunately the embedded-zlib-bug cannot be fixed at time. It's very strange that this behavior suddenly appears on this package too. All other packages which use the LCL/FPC at time simply override this error. (Info at bug #472304) I included the override in easymp3gain too and removed the quilt-dependency since it is the default patching system now. (But now I get a lintian warning about missing quilt dependency now...) I also included an explanation for the lintian-override. Hope this helps! Greetings Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/f3325f4055851c63cb72b6175cb4b...@mb8-2.1blu.de
Re: RFS: easymp3gain (updated package), fixes RC bug
>> Hi! >> Unfortunately the embedded-zlib-bug cannot be fixed at time. It's very >> strange that this behavior suddenly appears on this package too. All >> other >> packages which use the LCL/FPC at time simply override this error. (Info >> at >> bug #472304) >> I included the override in easymp3gain too and removed the >> quilt-dependency > > This doesn't work, have a look at the Re: embedded-zlib and fpc thread on > this ML with the messages from today. I already did: >>> E: easymp3gain-gtk: embedded-zlib ./usr/bin/easymp3gain >> @ftp-masters: was the removal of embedded-zlib from the list of tags that >> can be overridden just temporary (because of the klibc incident)? >Yes it was temporary and its already back. I guess this means the error _can_ be overriden again, as - for example - the Lazarus package does, which has been updates e few days ago. Or did I get something wrong? The bug should have been fixed in FPC 2.4.0, but it seems it is not. I'll track that bug and look for a way to work around it, but at time it would be good to update the easyMp3Gain version to make it compile again. As soon as Lazarus reaches testing, the package will FTBFS on squeeze too. Cheers Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/267beb9172ad1cb7807726e5e0f4c...@mb8-2.1blu.de
Re: RFS: easymp3gain (updated package), fixes RC bug
I re-uploaded the package to DM again: - URL: http://mentors.debian.net/debian/pool/main/e/easymp3gain - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/e/easymp3gain/easymp3gain_0.5.0-3.dsc (Removed type-error in patch and CDBS include for quilt) The zlib-bug might get fixed with the new Lazarus major & FPC minor release, which enables FPC's completely new and much more intelligent resource-management. I'll forward a message abou this bug to the FPC developer mailing list to get some feedback about this bug. Regards Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/bc0301eda92ebdb5c5952cc34766e...@mb8-2.1blu.de
Re: RFS: easymp3gain (updated package), fixes RC bug
>> I already did: > E: easymp3gain-gtk: embedded-zlib ./usr/bin/easymp3gain @ftp-masters: was the removal of embedded-zlib from the list of tags >> that can be overridden just temporary (because of the klibc incident)? >>> Yes it was temporary and its already back. >> >> I guess this means the error _can_ be overriden again, as - for example - >> the Lazarus package does, which has been updates e few days ago. Or did I >> get something wrong? >> The bug should have been fixed in FPC 2.4.0, but it seems it is not. I'll >> track that bug and look for a way to work around it, but at time it would >> be good to update the easyMp3Gain version to make it compile again. >> As soon as Lazarus reaches testing, the package will FTBFS on squeeze >> too. >> Cheers >>Matthias > > No it is not possible, is back means: The reject for this check is back, > it was temporary disabled. > Hmm... I was able to override the error. And if you look at http://lintian.debian.org/tags/embedded-zlib.html there are several other packages which have an override for this. Is there a way to get an exception for easymp3gain to make the new version available in the archive? -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5918963675c6fdd8a39441171818c...@mb8-2.1blu.de
Re: embedded-zlib and fpc
On Tue, 13 Apr 2010 14:30:58 -0700, Russ Allbery wrote: > Russ Allbery writes: > >> The problem with embedded-zlib appears to be a false positive in Lintian. >> It seems to be triggering on the string: > >> "Seek in deflate compressed stream failed." > > Ah, no, I was looking in the wrong package. It's fp-units-base, and the > string is indeed exactly the problematic string indicating an embedded > copy of zlib: > > 4 deflate 1.1.2 Copyright 1995-1998 Jean-loup Gailly > > It's in usr/lib/fpc/2.4.0/units/i386-linux/paszlib/zdeflate.o, and that's > because despite being a completely different implementation translated to > Pascal, the Pascal implementation embeds exactly the same copyright and > version string as the C imlementation. Sigh. > > This is generally a false positive in that this is not the problem that > Lintian is trying to diagnose (although I don't understand why it only > sometimes shows up in builds of easymp3gain). I'm trying to figure out a > good way of having Lintian avoid this problem. > > I wonder if we can trigger off of that leading 4 to suppress this tag, > since that seems to be peculiar to the Pascal implementation. I think > I'll give that a try for the next Lintian release. Thank you! I asked at debian-devel for some info about this and worked with the FPC developers and came to exactly the same conclusion as you do. If you ldd the binary, you can also see zlib is dynamically linked. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/48e1691a135d06eb6ba6bd8f410a9...@mb8-2.1blu.de
Re: RFS: easymp3gain (updated package), fixes RC bug
> Okay, after all this confusion (mostly from my side with the zlib thing) > I have rechecked the package and uploaded it, thanks! Thank you! -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5842435c4bf0dfbc7481241cde9b4...@mb8-2.1blu.de
Update projectM packages
Hello! I recently repackaged the projectM music visualization libraries. Debian has version 1.2 at time, current upstream is 2.0.1. Now I have the following problem: My source package "projectm" would replace the "libprojectm" and the "libvisual-projectm" source packages. I contacted the authors of both packages, but did not receive a reply for months. My projectm-package provides some additional modules which come with projectM and are not in Debian yet. Accepting it would update all projectM packages, so that applications like Amarok can depend on it. (the package provides the Qt4 projectM bindings too) But the existing source package would have to be replaced. What is the correct way to switch to a new source package? Should I fill a RFS for the pkg and have the current devs of the projectm-packages to agree to this change? Thanks for your reply and kind regards! Matthias Klumpp The projectM source package builds these binary packages: libprojectm-dev - Advanced Milkdrop-compatible music visualization library - dev libprojectm-qt-dev - projectM Qt4 (development files) libprojectm-qt1 - projectM Qt4 bindings libprojectm2 - Advanced Milkdrop-compatible music visualization library libvisual-projectm - libvisual module for projectM projectm-data - Advanced Milkdrop-compatible music visualization library - data projectm-jack - projectM JackAudio module projectm-pulseaudio - projectM PulseAudio module projectm-test - projectM Test modules The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/projectm - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/projectm/projectm_2.0.1-1.dsc -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2c8ffbb86f2fdf033980f109d6779...@mb8-2.1blu.de
Re: Update projectM packages
Hi! > Please read devref: > > http://www.debian.org/doc/developers-reference/beyond-pkging.html#mia-qa > > libvisual-projectm is orphaned, so you don't need to contact anyone > for it. Just adding the libvisual-projectm binary package to the > libprojectm/projectm source package is enough for the ftpmasters to > autocruft remove the libvisual-projectm source package. > > A new upstream release isn't appropriate for an NMU. Okay. > Are you sure upstream didn't change the ABI without bumping the > SONAME? Looking at the symbols, it seems that there are a lot of > symbol renames, deletions and so on. It looks like they forgot to do a > SONAME bump. There is a transition freeze coming this month, this > should probably wait until squeeze is released, or go to experimental. I already contacted upstream about this, but I'm still waiting for a reply. > Normally one would rename the libprojectm source package to projectm > and change its version of the packaging instead of starting from > scratch. It would have been a lot more work to change libprojectm. All scripts and stuff needed to be changed. > A review of the package itself: > > debian/patches/debian-changes-2.0.1-0 needs editing and renaming. > Please forward the two patches upsream if you haven't already. Is done. > No need to distribute src/README since it is about compiling/installing. I'll remove it from including. > Er, your source package contains debian/libprojectm.debhelper.log, how > on earth did you manage that??? Seems to be some cruft I forgot to remove. > Wow, upstream sure does embed a lot of external libraries, fonts. It > is not appropriate to do that, please ask them to split them out of > the main source tarball into a dependencies.tar.gz or similar. While > upstream still embeds them and to ensure they are not used by Debian, > it is a good idea to rm -rf the relevant directories before running > upstream's build system. If any of them are actually used in Debian, > please notify the Debian security team. Okay, I'll ask them to do that. > Please reassign #580559 to src:libprojectm and merge it with #565355. > It looks like the maintainer is already working on this anyway, see > #565355 for details. Next time you might want to investigate more > closely before duplicating work? Finished. I packaged the projectM packages for myself a half year ago and found it in my directory a few menths ago. Then I decided to forward it to the maintainers, but after I did not received a reply, I was thinking about maintaining it by myself. But of course I would leave the projectM package to the libprojectm maintainer if he wants to have it. > There are many many (mostly minor) lintian complaints (including some > inappropriately overridden ones): > [blahblah...] I sent all this stuff to upstream. It's a little crazy upstream included some ancient Autotools stuff although the project is using cmake. > There are also a bunch of GCC and cmake warnings that should be sent > upstream. I already started diving into the code, but still have some problems to understand what's going on in several units. I better send this to upstream too. > Please ask upstream to support QuesoGLC in addition to FTGL for font > rendering. GLC allows font fallbacks so you can render a string that > has characters from several different fonts. pango might be another > alternative. Okay, didn't know about that. Thanks for your large analysis... Might take some days to fix all named issues. Cheers, Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/edff0ebd9d04108cd1d8483e24e29...@mb8-2.1blu.de
RFS: projectm
Dear mentors, I am looking for a sponsor for my package "projectm". * Package name: projectm Version : 2.0.1-1 Upstream Author : projectM Team * URL : http://projectm.sf.net * License : GPLv2 and LGPLv2.1 Section : sound It builds these binary packages: libprojectm-dev - Advanced Milkdrop-compatible music visualization library - dev libprojectm-qt-dev - projectM Qt4 (development files) libprojectm-qt1 - projectM Qt4 bindings libprojectm2 - Advanced Milkdrop-compatible music visualization library libvisual-projectm - libvisual module for projectM projectm-data - Advanced Milkdrop-compatible music visualization library - data projectm-jack - projectM JackAudio module projectm-pulseaudio - projectM PulseAudio module The package appears to be lintian clean. The upload would fix these bugs: 565355 My motivation for maintaining this package is: I use the library by myself. There's some "special" stuff to know about this package: The package replaces the orphaned libvisual-projectm package and the libprojectm source package. I got authorization from the maintainer of libprojectm to take over maintainership over this package. The pkg produces some Lintian warnings about ancient Autotools scripts or Windows binaries in the package. It also has some unnecessarily linked libraries in some binaries. All this stuff should be fixed by upstream, but upstream seems to have a lack of manpower at time, so I can't get a clean tarball or fixes for all issues. But the overall quality of the pkg is okay, I think. As soon as upstream provides a new tarball, I'll switch to it, but at time it does not seem that this will happen fast. (Upstream's busy at time...) By including the package in Debian, a lot of other apps would benefit from it. (Some audio-players use it for music visualization) It might be a good idea to test the package in experimental first. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/projectm - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/projectm/projectm_2.0.1-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/75b0cd3245c6764858fac94aa21b3...@mb8-2.1blu.de
Re: RFS: projectm
Hi! > I would be willing to co-maintain this package with you if you are > interested. Great! I added you to the list... > Have you considered contacting the Debian multimedia team? I'm sure someone > there would be interested in sponsoring projectm. I'm not subscribed to the Debian Multimedia list, but I'll send a request to the list now. > About the autotools issue, you can essentially update the build system in > the > form of a patch. If it's nothing more than rerunning autoreconf, than you > just > run it, acquire the diff of the build system, and then use that diff for > patching and unpatching the build system at build time. Not necessary. projectM uses cmake, the Autotools-Scripts are just some cruft from MacOs build or old projectM versions. I did a Lintian override for those errors, because they're not relevant for compiling. Regards Matthias >> The package can be found on mentors.debian.net: >> - URL: http://mentors.debian.net/debian/pool/main/p/projectm >> - Source repository: deb-src http://mentors.debian.net/debian unstable >> main >> contrib non-free >> - dget >> http://mentors.debian.net/debian/pool/main/p/projectm/projectm_2.0.1-1.dsc >> -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/120afb0903233c10ccc4a4c556bb1...@mb8-2.1blu.de
RFS: projectm (ping)
Hello! I'm still looking for someone interested in reviewing & sponsoring my packaging of projectM. Package details: * Package name: projectm Version : 2.0.1-1 Upstream Author : projectM Team * URL : http://projectm.sf.net * License : GPLv2 and LGPLv2.1 Section : sound It builds these binary packages: libprojectm-dev - Advanced Milkdrop-compatible music visualization library - dev libprojectm-qt-dev - projectM Qt4 (development files) libprojectm-qt1 - projectM Qt4 bindings libprojectm2 - Advanced Milkdrop-compatible music visualization library libvisual-projectm - libvisual module for projectM projectm-data - Advanced Milkdrop-compatible music visualization library - data projectm-jack - projectM JackAudio module projectm-pulseaudio - projectM PulseAudio module The package appears to be lintian clean. The upload would fix these bugs: 565355 There's some "special" stuff to know about this package: The package replaces the orphaned libvisual-projectm package and the libprojectm source package. I got authorization from the maintainer of libprojectm to take over maintainership over this package. The pkg produces some Lintian warnings about ancient Autotools scripts or Windows binaries in the package. (projectM uses CMake, the Autotools-Scripts are just cruft which isn't used) It also has some binaries which unnecessarily linked against some libraries. All this stuff should be fixed by upstream, but upstream seems to have a lack of manpower at time, so I can't get a clean tarball or fixes for all issues. But the overall quality of the pkg is okay, I think. By including the package in Debian, a lot of other apps would benefit from it. (Some audio-players use it for music visualization) The package actually would be maintained by me and Andres Mejia as co-maintainer. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/projectm - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/projectm/projectm_2.0.1-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/078b29188f89011f2a38cc7ce7def...@mb8-2.1blu.de
RFS: projectm (ping)
Hello! I'm still looking for someone interested in reviewing & sponsoring my packaging of projectM. Package details: * Package name: projectm Version : 2.0.1-1 Upstream Author : projectM Team * URL : http://projectm.sf.net * License : GPLv2 and LGPLv2.1 Section : sound It builds these binary packages: libprojectm-dev - Advanced Milkdrop-compatible music visualization library - dev libprojectm-qt-dev - projectM Qt4 (development files) libprojectm-qt1 - projectM Qt4 bindings libprojectm2 - Advanced Milkdrop-compatible music visualization library libvisual-projectm - libvisual module for projectM projectm-data - Advanced Milkdrop-compatible music visualization library - data projectm-jack - projectM JackAudio module projectm-pulseaudio - projectM PulseAudio module The package appears to be lintian clean. The upload would fix these bugs: 565355 There's some "special" stuff to know about this package: The package replaces the orphaned libvisual-projectm package and the libprojectm source package. I got authorization from the maintainer of libprojectm to take over maintainership over this package. The pkg produces some Lintian warnings about ancient Autotools scripts or Windows binaries in the package. (projectM uses CMake, the Autotools-Scripts are just cruft which isn't used) It also has some binaries which unnecessarily linked against some libraries. All this stuff should be fixed by upstream, but upstream seems to have a lack of manpower at time, so I can't get a clean tarball or fixes for all issues. But the overall quality of the pkg is okay, I think. By including the package in Debian, a lot of other apps would benefit from it. (Some audio-players use it for music visualization) The package might be a candidate to be maintained by the Debian-Multimedia team. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/projectm - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/projectm/projectm_2.0.1-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/a2c6e6cc3cbaa9e592652da7e380c...@mb8-2.1blu.de
Re: RFS: projectm (ping)
> > I just imported your package into the debian-multimedia git repo. > http://git.debian.org/?p=pkg-multimedia/projectm.git > > This should make it easier to review your package. I don't have time yet to > > review your package. Sorry. Maybe you can trying catching siretart on IRC. Okay. Can I get access to the Git repository to make changes on the package? The I would stop committing new packages to Debian Mentors and push all changes directly to the Git repo. Cheers Matthias >> Package details: >> >> * Package name: projectm >> Version : 2.0.1-1 >> Upstream Author : projectM Team >> * URL : http://projectm.sf.net >> * License : GPLv2 and LGPLv2.1 >> Section : sound >> >> It builds these binary packages: >> libprojectm-dev - Advanced Milkdrop-compatible music visualization >> library >> - dev >> libprojectm-qt-dev - projectM Qt4 (development files) >> libprojectm-qt1 - projectM Qt4 bindings >> libprojectm2 - Advanced Milkdrop-compatible music visualization library >> libvisual-projectm - libvisual module for projectM >> projectm-data - Advanced Milkdrop-compatible music visualization library >> - >> data >> projectm-jack - projectM JackAudio module >> projectm-pulseaudio - projectM PulseAudio module >> >> The package appears to be lintian clean. >> >> The upload would fix these bugs: 565355 >> >> There's some "special" stuff to know about this package: The package >> replaces the orphaned libvisual-projectm package and the libprojectm >> source >> package. >> I got authorization from the maintainer of libprojectm to take over >> maintainership over this package. >> The pkg produces some Lintian warnings about ancient Autotools scripts or >> Windows binaries in the package. (projectM uses CMake, the >> Autotools-Scripts are just cruft which isn't used) It also has some >> binaries which unnecessarily linked against some libraries. All this >> stuff >> should be >> fixed by upstream, but upstream seems to have a lack of manpower at time, >> so I can't get a clean tarball or fixes for all issues. >> But the overall quality of the pkg is okay, I think. >> By including the package in Debian, a lot of other apps would benefit >> from it. (Some audio-players use it for music visualization) >> The package might be a candidate to be maintained by the >> Debian-Multimedia >> team. >> >> The package can be found on mentors.debian.net: >> - URL: http://mentors.debian.net/debian/pool/main/p/projectm >> - Source repository: deb-src http://mentors.debian.net/debian unstable >> main >> contrib non-free >> - dget >> http://mentors.debian.net/debian/pool/main/p/projectm/projectm_2.0.1-1.dsc >> >> I would be glad if someone uploaded this package for me. >> >> Kind regards >> Matthias Klumpp >> -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/46f1e33ce0f3774c20adef94acfe4...@mb8-2.1blu.de
RFS: ultrastardx
Dear mentors, I am looking for a sponsor for my package "ultrastardx". * Package name: ultrastardx Version : 1.1rc-1 Upstream Author : UltraStar-Deluxe Team * URL : http://ultrastardeluxe.org * License : GPLv2 Section : games It builds these binary packages: ultrastar-deluxe - A singing competition game ultrastar-deluxe-data - A singing competition game (data files) The package appears to be lintian clean. The upload would fix these bugs: 586553 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/u/ultrastardx - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/u/ultrastardx/ultrastardx_1.1~rc1-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8075c3c157f33378c2c792826a1ff...@mb8-2.1blu.de
RFS: oxygen-molecule
Dear mentors, I am looking for a sponsor for my package "oxygen-molecule". * Package name: oxygen-molecule Version : 3.2-1 Upstream Author : Christian Collins * URL : http://www.kde-look.org/content/show.php?content=103741 * License : GPLv2+ Section : x11 It builds these binary packages: oxygen-molecule - GTK theme to match KDE desktop environment The package appears to be lintian clean. The upload would fix these bugs: 589168 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/o/oxygen-molecule - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/o/oxygen-molecule/oxygen-molecule_3.2-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8a27c3894f67ff7441138b2f9f321...@mb8-2.1blu.de
RFS: oxygen-molecule
Dear mentors, I am looking for a sponsor for my package "oxygen-molecule". * Package name: oxygen-molecule Version : 3.2-1 Upstream Author : Christian Collins * URL : http://www.kde-look.org/content/show.php?content=103741 * License : GPLv2+ Section : x11 It builds these binary packages: oxygen-molecule - GTK theme to match KDE desktop environment The package appears to be lintian clean. The upload would fix these bugs: 589168 Oxygen-Molecule is the default GTK+-Style in the current openSUSE release and some other distributions. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/o/oxygen-molecule - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/o/oxygen-molecule/oxygen-molecule_3.2-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/f660ec1436ffd2477edea554faa0c...@mb8-2.1blu.de
RFS: oxygen-molecule (ping)
Dear mentors, I am looking for a sponsor for my package "oxygen-molecule". * Package name: oxygen-molecule Version : 3.2-1 Upstream Author : S. Christian Collins * URL : http://www.kde-look.org/content/show.php?content=103741 * License : GPLv2+ Section : x11 It builds these binary packages: oxygen-molecule - GTK theme to match KDE desktop environment The package appears to be lintian clean. The upload would fix these bugs: 589168 Oxygen-Molecule is the default GTK+-Style in openSUSE 11.3 and some other distributions. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/o/oxygen-molecule - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/o/oxygen-molecule/oxygen-molecule_3.2-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6fecd6649ca1bc19c549a9153fdd7...@mb8-2.1blu.de
RFS: packagekit
Dear mentors, I am looking for a sponsor for my package "packagekit". * Package name: packagekit Version : 0.6.7-1 Upstream Author : Richard Hughes * URL : http://packagekit.org * License : GPLv2/LGPLv2 Section : admin It builds these binary packages: gstreamer0.10-packagekit - GStreamer plugin to install codecs using PackageKit libpackagekit-glib2-14 - Library for accessing PackageKit using GLib libpackagekit-glib2-dev - Library for accessing PackageKit using GLib (development files) libpackagekit-qt-dev - Library for accessing PackageKit using Qt4 (development files) libpackagekit-qt14 - Library for accessing PackageKit using Qt4 mozilla-packagekit - Plugin to install missing plugins using PackageKit packagekit - Provides a package management service packagekit-backend-apt - Python APT backend for PackageKit packagekit-backend-aptcc - C++ APT backend for PackageKit packagekit-backend-smart - Smart backend for PackageKit packagekit-bash-completion - Offer to install missing programs automatically packagekit-docs - Documentation for PackageKit packagekit-gtk-module - Install fonts automatically using PackageKit python-packagekit - PackageKit Python bindings The package appears to be lintian clean. The upload would fix these bugs: 468132 My motivation for maintaining this package is: I follow the project since version 0.2 (I think) and develop some own software on to of the PackageKit library. I use PackageKit daily and stay in contact with upstream. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc I would be glad if someone uploaded this package for me. Notes: The make distclean does not reset the source code. PackageKit re-generates the source code documentation, so debhelper will create a patch for all those files. This is somewhat ugly, does someone know how to disable this behavior? Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6acd3b3b0c82316823d7dc9df79ad...@mb8-2.1blu.de
RFS: packagekit
Dear mentors, I am looking for a sponsor for my package "packagekit". * Package name: packagekit Version : 0.6.7-1 Upstream Author : Richard Hughes * URL : http://packagekit.org * License : GPLv2/LGPLv2 Section : admin It builds these binary packages: gstreamer0.10-packagekit - GStreamer plugin to install codecs using PackageKit libpackagekit-glib2-14 - Library for accessing PackageKit using GLib libpackagekit-glib2-dev - Library for accessing PackageKit using GLib (development files) libpackagekit-qt-dev - Library for accessing PackageKit using Qt4 (development files) libpackagekit-qt14 - Library for accessing PackageKit using Qt4 mozilla-packagekit - Plugin to install missing plugins using PackageKit packagekit - Provides a package management service packagekit-backend-apt - Python APT backend for PackageKit packagekit-backend-aptcc - C++ APT backend for PackageKit packagekit-backend-smart - Smart backend for PackageKit packagekit-bash-completion - Offer to install missing programs automatically packagekit-docs - Documentation for PackageKit packagekit-gtk-module - Install fonts automatically using PackageKit python-packagekit - PackageKit Python bindings The package appears to be lintian clean. The upload would fix these bugs: 468132 My motivation for maintaining this package is: I follow the project since version 0.2 (I think) and develop some own software on to of the PackageKit library. I use PackageKit daily and stay in contact with upstream. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc I would be glad if someone uploaded this package for me. Notes regarding packaging: The make distclean does not reset the source code. PackageKit re-generates the source code documentation, so debhelper will create a patch for all those files. This is somewhat ugly, does someone know how to disable this behavior? Note on PackageKit: PackageKit has Debconf support now (the APTcc backend has it) and supports some other functions requested for Debian. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/177801b691bdb097fc12f2b6fdc2b...@mb8-2.1blu.de
Re: RFS: packagekit
On Fri, 27 Aug 2010 10:12:47 +0800, Paul Wise wrote: > On Thu, Aug 26, 2010 at 8:41 PM, Matthias Klumpp > wrote: > >> I am looking for a sponsor for my package "packagekit". > > I'd like to applaud your and others efforts on this package, well done. > > I don't have time to do ongoing sponsorship but I will attempt to > review the package this weekend. Great! Most work to make PackageKit Debian-compliant was done by Daniel Nicoletti, Richard Hughes, Sebastian Heinlein and many others. Before you complain about this after review: Do you know a way to disable the automatic patch creation which was introduced with the 3.0 deb format? PackageKit updates the documentation and other files during build. This is not undone in make distclean, so debhelper creates a huge patch in debian/patches, which is really ugly. Is there a workaround for this or do I have to live with it? Thanks, Matthias --- The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7c6c3619ecaff59bf5bff1ca27bad...@mb8-2.1blu.de
Re: RFS: packagekit
On Sat, 28 Aug 2010 00:50:34 +0900, Ansgar Burchardt wrote: > Matthias Klumpp writes: > >> Before you complain about this after review: Do you know a way to disable >> the automatic patch creation which was introduced with the 3.0 deb >> format? >> PackageKit updates the documentation and other files during build. This >> is >> not undone in make distclean, so debhelper creates a huge patch in >> debian/patches, which is really ugly. > > It's not specific to the 3.0 source format, the changes would also show > up in the .diff.gz with the old format. > > If the updated files are not needed for the next build, you can just > remove them in the clean target, either by listing them in debian/clean > with debhelper >= 7 or manually in debian/rules. I already do this, but the problem is that the script changes files, it does not only create new ones. So I'm completely unable to restore all files. Cheers Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ee536a1547a944f9bdc0570948eb8...@mb8-2.1blu.de
Re: RFS: packagekit
On Fri, 27 Aug 2010 16:37:18 +0200, David Paleino wrote: > On Fri, 27 Aug 2010 11:31:41 +0200, Matthias Klumpp wrote: > >> Before you complain about this after review: Do you know a way to disable >> the automatic patch creation which was introduced with the 3.0 deb >> format? >> PackageKit updates the documentation and other files during build. This >> is >> not undone in make distclean, so debhelper creates a huge patch in >> debian/patches, which is really ugly. >> Is there a workaround for this or do I have to live with it? > > You could just use format "1.0" :) > > Or disable the documentation-update-on-build, or bash upstream until they > provide already-updated documentation ;) I'll ask upstream :) Thanks! -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ee1eec82cd74e7347f1d7d8dfe9b3...@mb8-2.1blu.de
Re: RFS: packagekit
Hi again! >> I already do this, but the problem is that the script changes files, it >> does not only create new ones. >> So I'm completely unable to restore all files. > > No, not *completely*. You can move the files that get modified, build > everything > and move them back in the clean target. That's a common trick. > > Another one is to copy all the files in a subdirectory (say, cp -va src > tgt), > build the package there and just remove that subdirectory in the clean > target > once you're done. This way, the original sources are kept intact. Funny, a few hours ago I added exactly this for the docs/api folder. Maybe I'll extend it to restore the other files too. Thanks! -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2f5593c0ea327a67adb871c004a52...@mb8-2.1blu.de
Re: RFS: packagekit
Hi! I found a way to make the creation of the patch a little less annoying. You just need to run "debuild -S -sa" twice, if a patch is created, and the script will remove the patch and cleanup the sources automatically. This keeps the debian/patches directory clean. --- The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/d2c3f1412ca3e7edc5437f17eb5cc...@mb8-2.1blu.de
Re: RFS: packagekit
Hi! >> http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc > > A review as promised... > > The copyright situation is much more complex than what you present in > debian/copyright. Please look at each file and fully document the > license situation. It is possible to have a per-binary-package > copyright file, which you might want to do since the libraries are > licensed differently. I updated the license file. Should be okay now. > Why do you need to build in a subdirectory? Seems like it complicates > the debian/rules file for no benefit. You can drop many of the flags > from DEB_BASIC_AUTOTOOLS_FLAGS by using dh_auto_configure -- > $(DEB_BASIC_AUTOTOOLS_FLAGS) $(PK_CONFIGURE_FLAGS) instead. Same for > make vs dh_auto_install. Changed. I built in a subdirectory because I thought maybe the scripts would create their modified file versions there so I could easily cleanup the sources. This is not the case, so I dropped the out-of-source build as you said. > Why do you move the upstream helper scripts to /usr/lib? They're scripts and should not be in /usr/share/PackageKit. In this directory we only have documentation of PK. > Not sure that patch removal stuff is a good idea. Better to fix > upstream to not include generated files in the tarball. I asked upstream to do this. As soon as the problem is fixed I will remove the patch removal. > Can the ln -s can be achieved with dh_link instead? Changed. > The watch file isn't quite as specific as it could be, I would replace > (.*) with ([\d\.]+) and drop the blank line. Okay, done. > Why is most of 01_set_defaults.patch needed? Shouldn't we only need to > change the iceweasel thing? The patch sets the optimal settings for the APT(cc) backends for Debian. The other settings are set to good values which Kubuntu uses too. > 02_update_aptcc.patch is a pretty big patch, has it been applied upstream > yet? Yes. Will be included in the next PK release. > For the URLs in 00_set_vendor.patch I would suggest creating new pages > in the PackageKit namespace on the wiki focused on what PackageKit > needs from them and based on what other distros have in the equivalent > pages. Then make those pages CategoryPermalink. I'll do this. Can copy the Ubuntu page with instructions how to add new repositories? It's a pretty nice page. > I wonder if the s/emblem-favorite/distributor-logo/ part of > 00_set_vendor.patch should be forwarded upstream. Don't know... Fedora does not change this setting, so I think it's okay since Richard is the maintainer of the Fedora packaging and could easily change it upstream too. > The browser plugin package naming has changed recently, they should no > longer be called mozilla-* but browser-plugin-* or xul-ext-* IIRC. Okay, changed. > Is the smart backend useful in Debian? I can't see smart in Debian. See http://labix.org/smart . We do have a smart package in Debian Sid. > The upstream README duplicates the information from debian/control, > drop it from debian/docs. Done. > Please add explanations to README.Debian about why things aren't shipped. Added. > Would it be a good idea to turn on unit tests? That would help ensure > the package works on all arches. Unit tests always failed in pbuilder and while running a local debuild. I think they're broken at time, cause Fedora has them disabled too. I'll enable them if they do not block the build process. > Which features of PackageKit in Fedora will not work in Debian? > > An automated warning: > > configure: WARNING: Distro upgrade notification not supported Strange... ALL features of PackageKit the backend supports will work on Debian. (And the APT backends do support most of the PK features) Distro upgrade notifications have to be done by KPackageKit or GNOME-PackageKit. But anyway I don't think it's a good idea to let PackageKit do distro-upgrades, so APT will notify about a new distro release and do the upgrade instead. (PackageKit won't interrupt APT working as usual) > The package FTBFS in pbuilder: > > [...] > > ../configure: line 3493: syntax error near unexpected token `0.6.7' > ../configure: line 3493: `GOBJECT_INTROSPECTION_CHECK(0.6.7)' > make[1]: *** [config.status] Error 2 > make[1]: *** Waiting for unfinished jobs > lib/packagekit-glib2/Makefile.am:234: HAVE_INTROSPECTION does not > appear in AM_CONDITIONAL > lib/packagekit-glib2/Makefile.am:241: addprefix $(srcdir: non-POSIX > variable name > lib/packagekit-glib2/Makefile.am:241: (probably a GNU make extension) > make[1]: *** [../Makefile.in] Error 1 > make[1]: Leaving directory `/tmp/buildd/packagekit-0.6.7/build' > dh_auto_build: make -j2 returned exit code 2 > make: *** [build] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 Fixed. Thanks! -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2d866271de426ff58dbb4a72acec
Re: RFS: packagekit
Hi again! With the latest upload I fixed everything which was criticized on the packaging: The copyright is clear, it does not FTBFS on pbuilder, the mozilla package has been renamed to browser-plugin, we don't need the dirty hack to remove the source file anymore and new wiki pages have been created. (I basically took the information from Fedora) So, is there someone out there who wants to review/sponsor the package? Would be very nice :) Regards Matthias --- The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/9a54a70ec512406432afc47298734...@mb8-2.1blu.de
Re: RFS: packagekit
On Mon, 30 Aug 2010 15:12:18 +0200, David Bremner wrote: > On Sun, 29 Aug 2010 14:48:17 +0200, Matthias Klumpp > wrote: >> somone (pabs?) wrote: >> > Why do you move the upstream helper scripts to /usr/lib? >> They're scripts and should not be in /usr/share/PackageKit. In this >> directory we only have documentation of PK. > > As best I understand the Linux File Hierarchy Standard, and thus Debian > Policy, architecture independent files should go in /usr/share, even if > they are scripts. Perhaps you could make a subdirectory for the docs, > and one for the helper scripts I think someone from Ubuntu told me one time to move the scripts to /usr/lib... Anyway, I changed the packaging, the helper scripts now go to /usr/share/PackageKit Thanks, Matthias --- The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ca045f00ef38baed4b577dae18c6f...@mb8-2.1blu.de
Re: RFS: packagekit
On Tue, 31 Aug 2010 09:26:25 +0800, Paul Wise wrote: > On Mon, Aug 30, 2010 at 8:39 PM, Matthias Klumpp > wrote: > >> new wiki pages have been created. (I basically took the information from >> Fedora) > > Please move them under the PackageKit namespace, so... > > http://wiki.debian.org/PackageKit/PackageItemNotFound > and so on > > Also, what was the license for the Fedora pages? Please ensure that > the Debian wiki is in compliance with that license. Changed. (http://wiki.debian.org/PackageKit/ItemNotFound) I refreshed the patch and uploaded the package to Mentors again. The license of the Fedora Wiki is AFAIK CC-BY-SA, should be no problem to reuse the texts. (I also modified them to match the Debian situation) Regards Matthias --- The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/fbcce75cbe05f2296b4621e363d9e...@mb8-2.1blu.de
Re: Debian and Patents (was: Re: RFS: packagekit)
On Tue, 31 Aug 2010 13:12:37 +0530, Praveen A wrote: > 2010/8/31 Boyd Stephen Smith Jr. : >> I thought the patent encumbered software was banned from the repos due to >> legal risk to SPI. I get my ffmpeg and mp3 stuff from the >> debian-multimedia >> repositories which, while good, are not official. It is. Debian Sid ships a version of FFMpeg which has disabled patented codecs etc. The Debian software pool might be not completely free of patents, but the most dangerous and important aren't shipped. Also it AFAIK does not contain a lot of patented software. > apt-cache policy libmad0 ffmpeg > apt-cache show libmad0 ffmpeg > > pr...@savannah:~$ apt-cache policy libmad0 ffmpeg > libmad0: > Installed: 0.15.1b-5 > Candidate: 0.15.1b-5 > Version table: > *** 0.15.1b-5 0 > 500 http://ftp.de.debian.org sid/main Packages > 100 /var/lib/dpkg/status > ffmpeg: > Installed: (none) > Candidate: 4:0.5.2-3 > Version table: > 4:0.6-2 0 > 101 http://ftp.de.debian.org experimental/main Packages > 4:0.5.2-3 0 > 500 http://ftp.de.debian.org sid/main Packages > > It is in debian main. I was surprised to see even wmv/wma playing out > of the box with squeeze. Are you really sure? (Maybe I got something wrong, but this shouldn't be possible and it wasn't possible on my Debian installation) Cheers Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/814093d4a0fa771ecfad2874ac4cb...@mb8-2.1blu.de
Re: RFS: packagekit
Something left to do? Regards Matthias --- The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/db90e36d5f9e6d996cf66247352c6...@mb8-2.1blu.de
Re: RFS: packagekit
On Thu, 2 Sep 2010 15:39:55 +0800, Paul Wise wrote: > On Tue, Aug 31, 2010 at 10:56 PM, Matthias Klumpp > wrote: > >> The license of the Fedora Wiki is AFAIK CC-BY-SA, should be no problem to >> reuse the texts. (I also modified them to match the Debian situation) > > I mean stuff like indicating that the text is CC-BY-SA and listing the > copyright information. Uh, I already added the information to Debian's wiki, but it seems like I removed while moving the page to PackageKit namespace... Anyway, I added a reference to Fedorawiki and the information that the license is CC-BY-SA again. Cheers, Matthias > Please read the CC-BY-SA legal code and try to ensure you are doing > the right thing. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ec8d2b5434124d3df3c42db3bd891...@mb8-2.1blu.de
RFS: packagekit
Dear mentors, I am looking for a sponsor for my package "packagekit". * Package name: packagekit Version : 0.6.7-1 Upstream Author : Richard Hughes * URL : http://packagekit.org * License : GPLv2/LGPLv2 Section : admin It builds these binary packages: gstreamer0.10-packagekit - GStreamer plugin to install codecs using PackageKit libpackagekit-glib2-14 - Library for accessing PackageKit using GLib libpackagekit-glib2-dev - Library for accessing PackageKit using GLib (development files) libpackagekit-qt-dev - Library for accessing PackageKit using Qt4 (development files) libpackagekit-qt14 - Library for accessing PackageKit using Qt4 browser-plugin-packagekit - Plugin to install missing plugins using PackageKit packagekit - Provides a package management service packagekit-backend-apt - Python APT backend for PackageKit packagekit-backend-aptcc - C++ APT backend for PackageKit packagekit-backend-smart - Smart backend for PackageKit packagekit-bash-completion - Offer to install missing programs automatically packagekit-docs - Documentation for PackageKit packagekit-gtk-module - Install fonts automatically using PackageKit python-packagekit - PackageKit Python bindings The package appears to be lintian clean. The upload would fix these bugs: 468132 My motivation for maintaining this package is: I follow the project since version 0.1.5 and develop some own software on to of the PackageKit library. I use PackageKit daily and I'm in contact with upstream. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc I would be glad if someone uploaded this package for me. Note on PackageKit: PackageKit has Debconf support now (the APTcc backend has it) and supports some other functions requested for Debian, like solving the problem if a package installation requires a package removal etc. Nearly all problems some Debian devs named are fixed and PK ist ready for the repos. Kubuntu aleady uses it with great success. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/c051fe92db12157315c960c35f186...@mb8-2.1blu.de
RFS: packagekit (ping)
Dear mentors, I am looking for a sponsor for my package "packagekit". * Package name: packagekit Version : 0.6.7-1 Upstream Author : Richard Hughes * URL : http://packagekit.org * License : GPLv2/LGPLv2 Section : admin It builds these binary packages: gstreamer0.10-packagekit - GStreamer plugin to install codecs using PackageKit libpackagekit-glib2-14 - Library for accessing PackageKit using GLib libpackagekit-glib2-dev - Library for accessing PackageKit using GLib (development files) libpackagekit-qt-dev - Library for accessing PackageKit using Qt4 (development files) libpackagekit-qt14 - Library for accessing PackageKit using Qt4 browser-plugin-packagekit - Plugin to install missing plugins using PackageKit packagekit - Provides a package management service packagekit-backend-apt - Python APT backend for PackageKit packagekit-backend-aptcc - C++ APT backend for PackageKit packagekit-backend-smart - Smart backend for PackageKit packagekit-bash-completion - Offer to install missing programs automatically packagekit-docs - Documentation for PackageKit packagekit-gtk-module - Install fonts automatically using PackageKit python-packagekit - PackageKit Python bindings The package appears to be lintian clean. The upload would fix these bugs: 468132 My motivation for maintaining this package is: I follow the project since version 0.1.5 and develop some own software on to of the PackageKit library. I use PackageKit daily and I'm in contact with upstream. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc I would be glad if someone uploaded this package for me. Note on PackageKit: PackageKit has Debconf support now (the APTcc backend has it) and supports some other functions requested for Debian, like solving the problem if a package installation requires a package removal etc. Nearly all problems some Debian devs named are fixed and PK ist ready for the repos. Kubuntu aleady uses it with great success. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/d8c6de4f3cbdf9f3b2dd4da9390ea...@mb8-2.1blu.de
RFS: packagekit (ping)
Dear mentors, I am looking for a sponsor for my package "packagekit". * Package name: packagekit Version : 0.6.8-1 Upstream Author : Richard Hughes * URL : http://packagekit.org * License : GPLv2/LGPLv2 Section : admin It builds these binary packages: browser-plugin-packagekit - Plugin to install missing plugins using PackageKit gstreamer0.10-packagekit - GStreamer plugin to install codecs using PackageKit libpackagekit-glib2-14 - Library for accessing PackageKit using GLib libpackagekit-glib2-dev - Library for accessing PackageKit using GLib (development files) libpackagekit-qt-dev - Library for accessing PackageKit using Qt4 (development files) libpackagekit-qt14 - Library for accessing PackageKit using Qt4 packagekit - Provides a package management service packagekit-backend-apt - Python APT backend for PackageKit packagekit-backend-aptcc - C++ APT backend for PackageKit packagekit-backend-smart - Smart backend for PackageKit packagekit-bash-completion - Offer to install missing programs automatically packagekit-docs - Documentation for PackageKit packagekit-gtk-module - Install fonts automatically using PackageKit python-packagekit - PackageKit Python bindings The package appears to be lintian clean. The upload would fix these bugs: 468132 My motivation for maintaining this package is: I follow the project since version 0.1.5 and develop some own software on to of the PackageKit library. I use PackageKit daily and I'm in contact with upstream. Note on PackageKit: PackageKit has Debconf support now (the APTcc backend has it) and supports some other functions requested for Debian, like solving the problem if a package installation requires a package removal etc. Nearly all problems some Debian devs named are fixed and PK ist ready for the repos. Kubuntu aleady uses it with great success. I recently updated the pkg at Debian Mentors. Specially for Debian, v.0.6.8 provides these changes: - aptcc: Improved user experience by setting subprogress on package installation/remove/update (Daniel Nicoletti) - aptcc: Disable auto remove by default (Daniel Nicoletti) - aptcc: Fix how downloads are emitted (Daniel Nicoletti) - aptcc: Forbid canceling while installing, the user might need to dpkg --configure -a on the cmd line (Daniel Nicoletti) - aptcc: Improved how packages are emited (Daniel Nicoletti) - aptcc: Improved logic for the updates category (Daniel Nicoletti) - aptcc: make sure all downloaded packages emit FINISHED (Daniel Nicoletti) - aptcc: Show apt error message when we could not get the cache lock (Daniel Nicoletti) The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6bab7cbd638564923f7df9aa99320...@mb8-2.1blu.de
RFS: packagekit (ping2)
Dear mentors, I am looking for a sponsor for my package "packagekit". * Package name: packagekit Version : 0.6.8-1 Upstream Author : Richard Hughes * URL : http://packagekit.org * License : GPLv2/LGPLv2 Section : admin It builds these binary packages: browser-plugin-packagekit - Plugin to install missing plugins using PackageKit gstreamer0.10-packagekit - GStreamer plugin to install codecs using PackageKit libpackagekit-glib2-14 - Library for accessing PackageKit using GLib libpackagekit-glib2-dev - Library for accessing PackageKit using GLib (development files) libpackagekit-qt-dev - Library for accessing PackageKit using Qt4 (development files) libpackagekit-qt14 - Library for accessing PackageKit using Qt4 packagekit - Provides a package management service packagekit-backend-apt - Python APT backend for PackageKit packagekit-backend-aptcc - C++ APT backend for PackageKit packagekit-backend-smart - Smart backend for PackageKit packagekit-bash-completion - Offer to install missing programs automatically packagekit-docs - Documentation for PackageKit packagekit-gtk-module - Install fonts automatically using PackageKit python-packagekit - PackageKit Python bindings The package appears to be lintian clean. The upload would fix these bugs: 468132 My motivation for maintaining this package is: I follow the project since version 0.1.5 and develop some own software on to of the PackageKit library. I use PackageKit daily and I'm in contact with upstream. Note on PackageKit: PackageKit has Debconf support now (the APTcc backend has it) and supports some other functions requested for Debian, like solving the problem if a package installation requires a package removal etc. Nearly all problems some Debian devs named are fixed and PK ist ready for the repos. Kubuntu aleady uses it with great success. I recently updated the pkg at Debian Mentors. Specially for Debian, v.0.6.8 provides these changes: - aptcc: Improved user experience by setting subprogress on package installation/remove/update (Daniel Nicoletti) - aptcc: Disable auto remove by default (Daniel Nicoletti) - aptcc: Fix how downloads are emitted (Daniel Nicoletti) - aptcc: Forbid canceling while installing, the user might need to dpkg --configure -a on the cmd line (Daniel Nicoletti) - aptcc: Improved how packages are emited (Daniel Nicoletti) - aptcc: Improved logic for the updates category (Daniel Nicoletti) - aptcc: make sure all downloaded packages emit FINISHED (Daniel Nicoletti) - aptcc: Show apt error message when we could not get the cache lock (Daniel Nicoletti) The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bf89b9e6f7a3361b0f9498bfb355...@mb8-2.1blu.de
RFS: packagekit (ping2)
Dear mentors, I am looking for a sponsor for my package "packagekit". This package has been reviewed by Paul Wise and Asheesh Laroia already and should be completely free of any policy violations or other problems regarding packaging. I work closely with upstream and hope to find someone interested in sponsoring the package for Debian. Here you can find details about this package: * Package name: packagekit Version : 0.6.8-1 Upstream Author : Richard Hughes * URL : http://packagekit.org * License : GPLv2/LGPLv2 Section : admin It builds these binary packages: browser-plugin-packagekit - Plugin to install missing plugins using PackageKit gstreamer0.10-packagekit - GStreamer plugin to install codecs using PackageKit libpackagekit-glib2-14 - Library for accessing PackageKit using GLib libpackagekit-glib2-dev - Library for accessing PackageKit using GLib (development files) libpackagekit-qt-dev - Library for accessing PackageKit using Qt4 (development files) libpackagekit-qt14 - Library for accessing PackageKit using Qt4 packagekit - Provides a package management service packagekit-backend-apt - Python APT backend for PackageKit packagekit-backend-aptcc - C++ APT backend for PackageKit packagekit-backend-smart - Smart backend for PackageKit packagekit-bash-completion - Offer to install missing programs automatically packagekit-docs - Documentation for PackageKit packagekit-gtk-module - Install fonts automatically using PackageKit python-packagekit - PackageKit Python bindings The package appears to be lintian clean. The upload would fix these bugs: 468132 My motivation for maintaining this package is: [fill in]. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.8-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/d9d60fb9cd7342774321ea4029bf9...@mb8-2.1blu.de
Re: RFS: packagekit (ping2)
On Fri, 8 Oct 2010 22:38:59 +0200, Julien Viard de Galbert wrote: > On Fri, Oct 08, 2010 at 08:09:23PM +0200, Matthias Klumpp wrote: >> Dear mentors, >> >> I am looking for a sponsor for my package "packagekit". >> This package has been reviewed by Paul Wise and Asheesh Laroia already >> and >> should be completely free of any policy violations or other problems >> regarding packaging. > OK, I will save them to answer you within 4 days then ;) > Don't take me wrong, I'm not DD so I wont upload, but even if I were, by > reading your mail I just don't get what packagekit is, so I guess I'm > not the only one ;) Hmm, okay, if this is the problem I can solve it easily :P PackageKit is a DBus abstraction layer and Freedesktop standard for accessing package management. It allows you to implement access to package management into your application in a cross-distro way, for example the Anjuta IDE searches for required plugins using PackageKit and the Nautilus file manager can use it to install apps for missing mime-types etc. All these apps just need to know the PackageKit API, it does not matter if the distribution uses APT/Yum/Zypper/Emerge/. Also, PackageKit organizes all package management tasks in transactions, which allows you e.g to browse the package database while installing new packages/updates. PackageKit is also the basis for tools like GNOME-PackageKit, which provides an advanced, user-friendly PackageManager and System-Update GUI, as well as KPackageKit (Apper) does for KDE. (KDE can also use PackageKit to install missing Debug-Symbols automatically) For more information about PK, please read http://packagekit.org/pk-intro.html or http://en.wikipedia.org/wiki/PackageKit > >> I work closely with upstream and hope to find someone interested in >> sponsoring the package for Debian. >> >> Here you can find details about this package: >> >> * Package name: packagekit >> Version : 0.6.8-1 >> Upstream Author : Richard Hughes >> * URL : http://packagekit.org >> * License : GPLv2/LGPLv2 >> Section : admin >> >> It builds these binary packages: >> [...] >> The package appears to be lintian clean. >> >> The upload would fix these bugs: 468132 >> >> My motivation for maintaining this package is: [fill in]. > > And that should probably be filled too Oh, sorry, I forgot this... My motivation is that I work closely with upstream on some PK related tasks, including this package. I develop an extension for PackageKit, so I know the project's code well, also PackageKit is the basis of some own projects I develop. I also assist the Ubuntu packaging of PK sometimes (by providing patches etc.) and I think having PK in Debian is great for PackageKit by itself (as it tries to be a generic package management abstraction layer for all distros) and for Debian, as it then can benefit from all PK features and existing apps can depend on it, as well as Debian can have the (really nice) PK-based update-manager or other PK-based tools too. It also can use the global AppInstall data to create tools similar to Ubuntu's USC. (but cross-distro) >> The package can be found on mentors.debian.net: >> - URL: http://mentors.debian.net/debian/pool/main/p/packagekit >> - Source repository: deb-src http://mentors.debian.net/debian unstable >> main contrib non-free >> - dget >> http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.8-1.dsc >> >> I would be glad if someone uploaded this package for me. >> >> Kind regards >> Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/d66e5898c1659cf65492682a247e4...@mb8-2.1blu.de
Re: RFS: packagekit (ping2)
> > [...] (lots of further info on packagekit) > > Well, I am a DD and in principle could sponsor such a package, but I just > lack > all the know how needed to properly evaluate gnome-related packages. And, > as I > already wrote in another reponse to an RFS some minutes ago, it seems that > nobody else reading the RFS on this list is currently able to do such > sponsoring. Wouldn't it maybe be a good idea to contact the Debian GNOME > Team > instead? All the info is available at > > http://alioth.debian.org/projects/pkg-gnome PackageKit is no GNOME package (it's not part of GNOME). There is a GNOME frontend for it, called "GNOME-PackageKit". The PackageKit daemon uses GLib, but that's all. But as PackageKit is used (can be used) by many GNOME applications, the GNOME development team might be interested in having this in the repos. So, I'll write to their mailing list later, maybe someone is interested in sponsoring the package. > Hope this helps, Yep, at least I have some kind of perspective for this package now. I'll first ask the Ubuntu devs, then post on the pkg-gnome mailinglist. Thanks! -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/0a134f9c0962c9271f317ecd503bf...@mb8-2.1blu.de
RFS: debconf-kde (ping)
Dear mentors, I am looking for a sponsor for my package "debconf-kde". * Package name: debconf-kde Version : 0.1+git20101228-1 Upstream Author : Daniel Nicoletti * URL : https://projects.kde.org/projects/extragear/sysadmin/libdebconf-kde/ * License : LGPL-2+ Section : kde It builds these binary packages: debconf-kde-dbg - Debconf KDE debugging symbols debconf-kde-helper - Debconf KDE GUI frontend tool libdebconf-kde-dev - Development headers for the Debconf KDE library libdebconf-kde0 - Debconf KDE GUI library The package appears is lintian clean. The upload would fix these bugs: 606251 My motivation for maintaining this package is: This is a requirement of Apper (PackageKit KDE frontend) and Muon, and I'm going to package Apper for Debian, therefore this package is needed before. It also provides KDE Debconf dialogs for any application using PackageKit, which is extremely useful. This package has already been reviewed several times, but nobody has had enough time to sponsor it. (But it was uploaded to Ubuntu already) The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/d/debconf-kde - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/d/debconf-kde/debconf-kde_0.1+git20101228-1.dsc I would be glad if someone uploaded this package for me. Kind regards Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2fa8be694a822b6cea0f07cd66886...@mb8-2.1blu.de
Re: RFS: debconf-kde (ping)
> [...] > > It seems that no one has found the time to sponsor this package so far, > hence I > just did that and uploaded it. It looks mostly ok, apart from a few smaller > issues, which should be addressed in future versions: > > - There is no Homepage field and also no watch file. > - There is a symbols file, but that has a two problems: it's called > libdebconf-kde.symbols, and not libdebconf-kde0.symbols; second, you > should > preferably use the c++ pattern of dpkg-gensymbols, which was introduced > in > dpkg-dev 1.5.18. > - Lintian will also tell you the following: > I: debconf-kde-dbg: capitalization-error-in-description debian Debian > (and similarly for all other packages) Hi! Wow, great! Thanks for sponsoring this package! I'm currently working with pkg-kde on maintaining it under the pkg-kde-team umbrella, all the issues you mentioned above have been fixed in our Git branch :) Anyway, this means Debian is ready for Muon and Apper now ;) (as well as for a generic KDE Debconf-frontend) Cheers, Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1108e324798373d911d4918d866d...@mb8-2.1blu.de
RFS: Apper
Dear mentors, I am looking for a sponsor for my package "apper". * Package name: apper Version : 0.7.0-1 Upstream Author : Daniel Nicoletti * URL : http://kde-apps.org/content/show.php/Apper?content=84745 * License : GPL-2+ Section : kde It builds those binary packages: apper - KDE package management tool using PackageKit apper-dbg - Debugging symbols for Apper To access further information about this package, please visit the following URL: http://mentors.debian.net/package/apper Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/a/apper/apper_0.7.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Matthias Klumpp -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caknhny-62kxu2c3xgeqwtam1ggyjuz6ludvs-olloytmmms...@mail.gmail.com
Re: RFS: Apper
Hi! 2011/11/1 Andrew Starr-Bochicchio : > On Sat, Oct 22, 2011 at 4:54 PM, Matthias Klumpp > wrote: >>[...] > I'm not a DD, so I can not sponsor your package. I took a quick look > anyways. I found a few issues: > > 1) Running lintian on the resulting binary packages built in a clean > sid chroot produces the following error: > > E: apper: binary-or-shlib-defines-rpath usr/bin/apper > /tmp/buildd/apper-0.7.0/obj-i486-linux-gnu/lib >[...] This is a cmake bug, cmake does not clean up the rpath for some reason... I now added a workaround to the Apper pkg so the rpath gets reset. > > 2) Less important, but since the manpage is supplied in the debian dir: > > I: apper: hyphen-used-as-minus-sign usr/share/man/man1/apper.1.gz:18 > [...] Eh... I guess this is because of bug #208967 - I'll try if the manpage in newer Apper versions works, if so I'll just ignore this info since it will be fixed automatically with the next Apper release. Otherwise, I've to fix it somehow... > > 3) And completely optional: > > > I: apper: arch-dep-package-has-big-usr-share 2610kB 72% > [...] Hmm, yes. Maybe I should create a -data package. > > 2) Also, one nitpick thing I found is that in debian/copyright you > list two copyright holders on the same line, like so: > > Copyright: 2008 by Trever Fischer / 2009-2011 by Daniel Nicoletti >[...] Yes, fixed :) > > Hope that helps... Thank you for reviewing the package! I hope it can enter unstable soon :) Regards, Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caknhny-m3wkwhzur3sfpbdampfpnncm3ducxc4pdf0gmncc...@mail.gmail.com
Re: question about the packaging helpers
2014-01-30 Andreas Tille : > Hi, > > On Thu, Jan 30, 2014 at 08:35:09AM +, Roelof Wobben wrote: >> >> > Why not join the Debian GNOME team? >> > >> > https://wiki.debian.org/Teams/DebianGnome >> > >> Can I also learn there to package and get a sort of mentor who can learn me >> the right way ? Roelof > > Why not asking on the team mailing list? All teams *I* know (gnome > packaging does not belong to the lists I'm reading) are happy if > there are newcomers sending an introduction and asking for help. With my Tanglu hat on: Joining the GNOME team is one of the best things you can do to help! This will benefit Debian (and indirectly Tanglu), help you in learning the practices of the Debian-GNOME team and create better packages, and it will help Tanglu because you can provide new packages earlier to Tanglu, and the GNOME-Team because they can see how something performs on Tanglu (and get some more testing before a new Debian release). Simple win-win-win ;-) Cheers, Matthias -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKNHny9yWxGGFFPZvGyTGpyr=9Q7i+yG7Tdbg5ZDrHYU8=v...@mail.gmail.com
Re: Audiosum problem (unwanted binary)
Hi!
2014-02-04 Roelof Wobben :
> [...]
>
> I see this lintian errors :
>
> W: audiodup: empty-binary-package
> X: audiodup: package-contains-no-arch-dependent-files
Make sure your wrapping stuff gets installed to audiodup. You may want
to install into a temporary dir and use Debian .install files to
install your files:
http://www.debian.org/doc/manuals/maint-guide/dother.de.html#install
> But when I do this :
>
> Source: audiosum
> Section: sound
> Priority: optional
> Maintainer: Roelof Wobben
> Build-Depends: debhelper (>= 9.0.0), dh-autoreconf, libmhash-dev
> Standards-Version: 3.9.5
> Homepage: https://github.com/alvarezp/audiosum
> #Vcs-Git: git://git.debian.org/collab-maint/audiosum.git
> #Vcs-Browser: http://git.debian.org/?p=collab-maint/audiosum.git;a=summary
>
> Package: audiosum
> Architecture: any
> Depends: ${shlibs:Depends}, ${misc:Depends}
> Description: This tool helps to find duplicate mp3 files.
> The tool actually checksums the file, you have to find
> duplicate checksums. You might want to check the included
> audiodup script. It currently ignores ID3v1 tags in MP3 files.
>
> The compiling stops with this message :
>
> rm -rf debian/tmp
> rm -f *-stamp
> dpkg-source -b audiosum-0.2
> dpkg-source: info: using source format `3.0 (quilt)'
> dpkg-source: error: unwanted binary file:
> debian/audiodup/usr/share/doc/audiodup/changelog.Debian.gz
> dpkg-source: error: detected 1 unwanted binary file (add it in
> debian/source/include-binaries to allow its inclusion).
Because you changed the package config and did not remove the
temporary stuff, you get this mesage. Usually, dh_clean will take care
of it (but it doesn't know that this has to be removed, because you
deleted on package from control). A simple rm -r debian/audiodup will
fix this.
Cheers,
Matthias
--
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAKNHny-0iG2sjHyXir=XQQDYkmxG5K1s6N=6p0wgninjdo3...@mail.gmail.com
Re: Cjs failing test
2014-02-05 Roelof Wobben : > Hello, > > I have a failing test on the package cjs. > > I have asked upstream how to solve this and thet say use this : > DEB_BUILD_OPTIONS=nocheck > > Is this acceptable for a package which is hopefully once a part of Debian. > > According to upstream the failing test is Always failing but solving it or > deleting > the test has no priority. It is generally better to have tests run during package build, because you will see issues earlier. Upstream's response speaks for bad QA, or (in case of Mint sometimes the case) they don't know how to deal with the issue. What does the test actually test? If it is simple to fix, we should better get it fixed. Cheers, Matthias P.S: Are you using CDBS? If not, in case of dh, you need to override the auto-test command. -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caknhny_tokjtpwediv4v7_vhx7hudm31rho3geazvxd84aj...@mail.gmail.com
Re: cjs build error
2014-02-05 Roelof Wobben : > > > Oke, I put he complete build log on the bug report. > Can anyone also look at it to see something wierd. > I see no thing that could explain this problem. This test fails: https://github.com/linuxmint/cjs/blob/master/test/js/testLocale.js - I don't know where the issue is exactly, but from what the test checks, I would not simple ignore it's failure. Maybe your test_user_data/logs/stderr.log has some more information on where exactly the test fails. GTest is already executed in verbose mode, but doesn't look verbose enough. Cheers, Matthias -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caknhny8kdgk8paatn1yfz9xu9uskguc-bvyowvszguaywri...@mail.gmail.com
Re: cbds to dh7
2014-02-06 Roelof Wobben : > Hello, > > I saw that the Linux MInt people already had ported Cinnamon > to Debian. > > But they uses cbds > > Can this be easily be ported in dh7, which I rather use. There is no simple way, it basically needs a rewrite. Keep in mind that some GNOME packages like to use cdbs, because they have some built-in tools for optimization there (not sure if this still applies, just check the gjs package, maybe) Cheers, Matthias -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caknhny-0o3ibexqxb2rh6ahqerug8paeijwvugdem5jzn8b...@mail.gmail.com
Re: Cinnamon-desktop - no rule to build target error message
2014-02-12 20:06 GMT+01:00 Roelof Wobben : > Hello, > > When I try to build cinnamon-desktop with debuild I see this error message: > > make[1]: Map > '/home/roelof/porting_work/cinnamon-desktop/cinnamon-desktop-2.0.4' wordt > verlaten >dh_auto_test > make -j1 check > make[1]: Map > '/home/roelof/porting_work/cinnamon-desktop/cinnamon-desktop-2.0.4' wordt > binnengegaan > Making check in libcinnamon-desktop > make[2]: Map > '/home/roelof/porting_work/cinnamon-desktop/cinnamon-desktop-2.0.4/libcinnamon-desktop' > wordt binnengegaan > test -s ../libcinnamon-desktop/pnp.ids > make[2]: Map > '/home/roelof/porting_work/cinnamon-desktop/cinnamon-desktop-2.0.4/libcinnamon-desktop' > wordt verlaten > Making check in po > make[2]: Map > '/home/roelof/porting_work/cinnamon-desktop/cinnamon-desktop-2.0.4/po' wordt > binnengegaan > make[2]: *** There is no rule to make target > '../libgnome-desktop/display-name.c' neeeded for 'cinnamon-desktop.pot'. > Aborting. > > The tree which I build can be found here : > https://github.com/CinnamonDebian/cinnamon-desktop Looks like you are discovering loads and loads of Cinnamon bugs here! This is a bug in the makefile, because they renamed libgnome-desktop and apparently forgot to adjust a patch in the build-system. You can create a quilt patch for it and send it upstream. Btw, related question: Why can't they just use GJS and have to for it to CJS? GJS should be usable for anything in Cinnamon as well, and introducing forked code is always a bad thing (= more work for the security team). Cheers, Matthias -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caknhny-lx9od6vrbmwqsevxpz417s07icbaxcmuo2bx81sz...@mail.gmail.com
Re: Cinnamon-desktop - no rule to build target error message
2014-02-12 20:16 GMT+01:00 Roelof Wobben : > [...] > Yes, and what I find the most surprising it that if I use cdbs the bugs are > not there. > Do I have to make a patch in the Makefile ? or somewhere else ? > > Why they do not use cjs I do not know and I can ask upstream but Im sure we > do > not get a answer. I am not really happy how Linux Mint works ;-) But that's a different topic ^^ The problem with your build is, that they include a Makefile (po/Makefile) which is auto-generated. You will have to regenerate it, maybe no patch is needed. To you run dh-autoreconf already? (depend on it and add --with autoreconf). That will likely do the trick and also explains why the GNOME scripts in CDBS don't give you that error. Cheers, Matthias P.S: I only looked at it very briefly, so there might be other issues or I might be wrong with my idea ;-) -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caknhny9vnuv3si39f+wsayyylqxbkjsksnh_17nga9oqcav...@mail.gmail.com
Re: Do not want recieve mails from bugs.debian .
2014-02-15 13:43 GMT+01:00 Roelof Wobben : > Hello, > > How can I take care that I do not recieve mails from bugs.debian. You can unsubscribe from the corresponding bug, just check the bug's website and then send an email to the unsubscribe link. Do you care to write an explanation why you leave Debian? I think many people (including me) would like to get that feedback. Cheers, Matthias -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKNHny8nz3oHUm4Kam1p53hGBaUDx7XyuqSFS=jjcfkqk3j...@mail.gmail.com
Re: [Pkg-d-devel] Attempt to build BioD blocked by undeaD and missing module string (Was: How to build D source)
Hello!
2017-02-26 15:19 GMT+01:00 James Cowgill :
> Hi,
>
> On 26/02/17 07:03, Andreas Tille wrote:
>> On Sat, Feb 25, 2017 at 10:01:17PM +, James Cowgill wrote:
>>> On 25/02/17 21:31, Andreas Tille wrote:
I intend to package BioD[1] but I have no idea how to build the D code
(and run the unit tests). Considering BioD is a library I might need
something like a dynamic lib and a development package, but may be this
is different for D than in C.
>>>
>>> It looks like it uses "dub" as it's build system. Dub is packaged but
>>> has no users in the archive so you probably want to talk to the D
>>> language maintainers about it first to see what the correct way to
>>> handle this is.
>>
>> I just added "dub run" to debian/rules.
>
> I think you want "dub build" instead.
Yes, `dub build` is the right thing to do, but in general I would
strongly recommend to not use dub at all for Debian packaging.
It has a lot of issues which make it a pain to work with in the
context of Debian packaging, some of the issues are summarized at
https://gist.github.com/ximion/fe6264481319dd94c8308b1ea4e8207a
I did packaging with dub once, a d/rules file would look similar to
this:
https://anonscm.debian.org/git/pkg-packagekit/appstream-generator.git/tree/debian/rules?id=60dcc4c6e716f8ddbcf549f40bad0f5b800cb398
No package in Debian uses dub however, because it creates long-term
maintenance pain. The much better option is to submit a patch upstream
to build with either Automake, cmake or Meson. I strongly recommend
Meson here, because Meson configuration is very easy to write and it's
D support is already there (while it needs to be added to cmake with a
lot of macros, and Automake is just annoying to use in general).
Here is an example for a simple Meson build configuration for a very
small static D library:
https://github.com/repeatedly/mustache-d/commit/4e694202b02014871a767782606bacaf1422a3e2
At time, D stuff in Debian (with the exception of LDC itself) uses
either Meson or Automake.
>>> I notice it depends on undead which will need packaging first.
>>
>> There are two kinds of messages:
>>
>> bio/bam/bai/indexing.d(33,8): Deprecation: module std.stream is deprecated -
>> It will be removed from Phobos in October 2016. If you still need it, go to
>> https://github.com/DigitalMars/undeaD
>>
>> This is what James seems to refer to - I'm not sure whether this is
>> critical for the build here. I'd be willing to package undead if needed
>> but I'd prefer if some more skilled people would do so.
>
> Ah, I was looking at upstream git master which contains this dependency
> in dub.json:
> "dependencies": {
> "undead": "~>1.0.6"
> },
>
>> bio/bam/bai/indexing.d(38,8): Error: module string is in file
>> 'core/std/c/string.d' which cannot be read
>>
>> This seems to be critical. Do you have any hint?
>
> Maybe this PR would help?
> https://github.com/biod/BioD/pull/23
Which D compiler do you use for building? LDC or GDC? I would
recommend LDC here, since it supports the latest D runtime and
standard library versions, while GDC is lagging behind a lot.
The ideal solution here would be to port BioD away from using
deprecated stuff, but I am not sure how feasible this is - would be
nice to at least ask upstream on whether they accept patches for it.
Otherwise, undeaD needs to be in Debian first.
Cheers,
Matthias
--
I welcome VSRE emails. See http://vsre.info/
Re: [Pkg-d-devel] Attempt to build BioD blocked by undeaD and missing module string (Was: How to build D source)
2017-02-26 20:17 GMT+01:00 Andreas Tille :
> [...]
>> but in general I would
>> strongly recommend to not use dub at all for Debian packaging.
>> It has a lot of issues which make it a pain to work with in the
>> context of Debian packaging, some of the issues are summarized at
>> https://gist.github.com/ximion/fe6264481319dd94c8308b1ea4e8207a
>>
>> I did packaging with dub once, a d/rules file would look similar to
>> this:
>> https://anonscm.debian.org/git/pkg-packagekit/appstream-generator.git/tree/debian/rules?id=60dcc4c6e716f8ddbcf549f40bad0f5b800cb398
>>
>> No package in Debian uses dub however, because it creates long-term
>> maintenance pain. The much better option is to submit a patch upstream
>> to build with either Automake, cmake or Meson. I strongly recommend
>> Meson here, because Meson configuration is very easy to write and it's
>> D support is already there (while it needs to be added to cmake with a
>> lot of macros, and Automake is just annoying to use in general).
>>
>> Here is an example for a simple Meson build configuration for a very
>> small static D library:
>> https://github.com/repeatedly/mustache-d/commit/4e694202b02014871a767782606bacaf1422a3e2
>
> I'd fully trust your insight here but I admit Meson is totally new to me
> and crafting a Meson control file for a library without having any idea
> about D is a bit over my current status of knowledge. So I either need
> to use what upstream provides or ask here for help.
D is really easy to write if you know a bit of C and maybe Python or Java ^^
Writing a Meson build definition is trivial too, I can write on for
this project if you want and sibmit it upstream.
>> > Ah, I was looking at upstream git master which contains this dependency
>> > in dub.json:
>> > "dependencies": {
>> > "undead": "~>1.0.6"
>> > },
>> >
>> >> bio/bam/bai/indexing.d(38,8): Error: module string is in file
>> >> 'core/std/c/string.d' which cannot be read
>> >>
>> >> This seems to be critical. Do you have any hint?
>> >
>> > Maybe this PR would help?
>> > https://github.com/biod/BioD/pull/23
>>
>> Which D compiler do you use for building? LDC or GDC? I would
>> recommend LDC here, since it supports the latest D runtime and
>> standard library versions, while GDC is lagging behind a lot.
>> The ideal solution here would be to port BioD away from using
>> deprecated stuff, but I am not sure how feasible this is - would be
>> nice to at least ask upstream on whether they accept patches for it.
>> Otherwise, undeaD needs to be in Debian first.
>
> I admit I have no idea how to do this. Its the first time I see D code
> at all. May be it would be even better if the Debian D team could
> package BioD which I need for some other package as a pre-dependency.
I'd rather not want that to happen - the D team is currently mostly me
(and Markos), and packaging a library which we don't use is a bad
idea. I have too many packages already and I fear I will not be able
to adequately maintain them if I have too many and don't even use
them.
However, I could help with the packaging. I'll see whether BioD is
easy to port away from std.streams (doesn't look like it
unfortunately) and if not I could supply Meson build definitions to
the projects.
Is BioD a normal shared library? What are you doing with it?
Cheers,
Matthias
--
I welcome VSRE emails. See http://vsre.info/
Re: [Pkg-d-devel] Attempt to build BioD blocked by undeaD and missing module string (Was: How to build D source)
2017-02-28 13:17 GMT+01:00 Andreas Tille : > Hi Matthias, > > On Tue, Feb 28, 2017 at 11:16:37AM +0100, Matthias Klumpp wrote: >> > I'd fully trust your insight here but I admit Meson is totally new to me >> > and crafting a Meson control file for a library without having any idea >> > about D is a bit over my current status of knowledge. So I either need >> > to use what upstream provides or ask here for help. >> >> D is really easy to write if you know a bit of C and maybe Python or Java ^^ >> Writing a Meson build definition is trivial too, I can write on for >> this project if you want and submit it upstream. > > It would be helpful if you could provide a Meson build definition and > I'd happily submit it upstream. I had a coumple of minutes today: https://github.com/biod/BioD/pull/26 >> > I admit I have no idea how to do this. Its the first time I see D code >> > at all. May be it would be even better if the Debian D team could >> > package BioD which I need for some other package as a pre-dependency. >> >> I'd rather not want that to happen - the D team is currently mostly me >> (and Markos), and packaging a library which we don't use is a bad >> idea. I have too many packages already and I fear I will not be able >> to adequately maintain them if I have too many and don't even use >> them. > > That's OK. > >> However, I could help with the packaging. I'll see whether BioD is >> easy to port away from std.streams (doesn't look like it >> unfortunately) and if not I could supply Meson build definitions to >> the projects. > > The libbiod Git repository[1] is writable for every DD - so if you > would like to commit something there that would be really welcome. I am even member of the Debian Med team, I think, so helping out won't be a problem at all ^^ But don't count or rely on me please, I can't really promise anything. >> Is BioD a normal shared library? What are you doing with it? > > My final target (actually also a predependency for another target) > is sambamba[2] which using BioD as a git subrepository to build. That looks like fun, there are quite a couple of submodules... With BioD having a Meson build file now, it also got a pkg-config file, so integrating it with the sambamba Makefiles should be way easier (just calling pkg-config with the right flags while building should do the job). Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/
Re: Bug#773760: RFS: kcm-systemd/0.7.0-1 [ITP]
2014-12-23 0:56 GMT+01:00 Shawn Sörbom : > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "kcm-systemd" I would be interested in sponsoring this, but I will need some time (a few weeks) for the review, because I am currently a bit busy. So, if someone else is faster, feel free to jump in and review/upload it! I quickly skimmed over the package sources, and couldn't find issues so far (need to take a closer look though) Cheers, Matthias -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caknhny8+o6rbektq41ocx6c5w6aojltsqnrsbbwtv_gzv58...@mail.gmail.com
