Re: wine-unstable in Debian
[Please don't CC me on messages to debian-devel.] Petr Baudis schrieb am 14.04.2012 16:51: > Hi! > > It appears that the last release of wine easily available in Debian > is from 2009, quite a surprising state for a high-profile project like > that. Kai Wasserbäch appears to be very kindly providing wine-unstable > packages for Debian at > > http://dev.carbon-project.org/debian/wine-unstable/ > > I would like to ask if you have considered contributing these packages > to Debian sid, or if there is some major hurdle preventing that action? I'm going to be brief: <http://lists.debian.org/debian-devel/2011/09/msg00177.html> (short version of my motivation behind those packages). Kind regards, Kai Wasserbäch -- E-Mail: cu...@debian.org IRC: Curan Jabber: dri...@debianforum.de URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 signature.asc Description: OpenPGP digital signature
Bug#662943: ITP: libimager-qrcode-perl -- Generate QR code with Imager using libqrencode
Package: wnpp Severity: wishlist Owner: "Kai Wasserbäch" * Package name: libimager-qrcode-perl Version : 0.033 Upstream Author : Yoshiki KURIHARA * URL : http://search.cpan.org/dist/Imager-QRCode/ * License : GPL-1+ or Artistic (same as Perl 5.8.8 or later) Programming Lang: Perl Description : Generate QR code with Imager using libqrencode This is the CPAN Perl module Imager::QRCode. The module adds an easy-to-use interface to Imager for QR code generation. The actual code generation is done by the system library libqrencode. My interest in this package is work-related and not anticipated to go away soon. -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 signature.asc Description: OpenPGP digital signature
Re: ecofont
Dear "810d4rk", 810d4rk schrieb am 06.12.2011 22:52: > Hi, may I ask if it is possible to include ecofont > (www.ecofont.com/assets/files/ecofont_vera_sans_regular.zip) in > debian? assuming (I haven't checked that), that the font satisfies the DFSG [0], you can either package the font yourself and file an "Intend To Package" (ITP) bug or you can ask others to package the font (no guarantee that will happen) by filing a "Request For Packaging" (RFP) bug. Both of those bugs must be filed against the wnpp "package". You should use reportbug for the procedure. Before filing either of those bugs, please check, whether somebody already has requested the package or is working on it ([1]). Kind regards, Kai Wasserbäch [0] <http://www.debian.org/social_contract#guidelines> [1] <http://www.debian.org/devel/wnpp/prospective> -- E-Mail: cu...@debian.org IRC: Curan Jabber: dri...@debianforum.de URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 signature.asc Description: OpenPGP digital signature
Re: Increasing minimum 'i386' processor
Dear Raphaël, Raphaël Hertzog schrieb am 20.11.2011 08:40: > On Sat, 19 Nov 2011, Ben Hutchings wrote: >> Also possibly: >> 6. DM&P/SiS Vortex86 and Vortex86SX. These supposedly have all >>586-class features except an FPU, and we could probably keep FPU >>emulation for them. > > FWIW, I do run Debian on such systems albeit with a custom kernel. > Given those CPU tend to be used in an "embedded" context I guess > it's ok if the official kernel does not support them. But it would be > nice if Debian's userspace could be kept compatible. Not sure what this > requires though... judging from the section you quoted from Ben's e-mail, I'd say you shouldn't be affected in the short term if the FPU is really the only thing missing to make it a full 586-class CPU (of course, a further increase to a higher instruction set class would hit you). Apart from that I wonder how many "embedded" x86 CPUs (instruction set < 586) are out there. Are they still sold in current products? If so it might(!) be worth to keep compatible with them, even if that would mean an additional kernel build*. On the other hand most embedded kernels are custom build anyway, in which case "offering the tools" to build a running Debian system should be enough, right? * The question here is (again): do we have some numbers on this, that could guide the decision? If not and the assumption by the kernel maintainers is "few systems still operational run with CPUs which don't at least support 586 instructions", then I'd find it reasonable to still disable the support in the kernel. In case a huge amount of systems is still running with such CPUs chances are good, we're hearing of them then. ;-) Kind regards, Kai Wasserbäch -- E-Mail: cu...@debian.org IRC: Curan Jabber: dri...@debianforum.de URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 signature.asc Description: OpenPGP digital signature
Re: Increasing minimum 'i386' processor
Dear Ben, Ben Hutchings schrieb am 19.11.2011 23:42: > The i386 architecture was the first in Linux and in Debian, but we have > long since dropped support for the original i386-compatible processors > and now require a minimum of a 486-class processor. > > I think it is time to increase the minimum requirement to 586-class, if > not for wheezy then immediately after. (Later it should be increased > further, and eventually i386 should be reduced to a partial architecture > that may be installed on amd64 systems.) This would allow the use of > optimisations and new instructions throughout userland that improve > performance for the vast majority of users. I think "in time for Wheezy" would be fine. People with an older CPU will most likely not have that much fun with newer releases anyway, simply because a lot of programs tend to get bigger and more power-hungry over time. Just out of curiosity: are there any numbers available, indicating how many installations with CPUs with an instruction set < 586 are still in use? Does popcon collect such information? Kind regards, Kai Wasserbäch -- E-Mail: cu...@debian.org IRC: Curan Jabber: dri...@debianforum.de URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 signature.asc Description: OpenPGP digital signature
Re: Bug#648286: ITP: r8168 -- Realtek r8168 device driver for Linux (DKMS version)
Dear Dimitry, Dmitry Smirnov schrieb am 10.11.2011 12:50: > Sorry, I don't understand... > > This is merely an alternative driver from hardware vendor. > Sometimes you might need alternatives if your hardware doesn't work well, > or if you just suspect it do not work well but you need something to > compare with. > > "Fixing stuff" is always good if you can do it. well, then what is different and why can't that be upstreamed? And is there a known case, where the driver provided by Debian doesn't work (if so, is there a bug filed)? Don't get me wrong: I love alternatives, but I don't see their value when it comes to device drivers. Kind regards, Kai Wasserbäch -- E-Mail: cu...@debian.org IRC: Curan Jabber: dri...@debianforum.de URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 signature.asc Description: OpenPGP digital signature
Re: TranscriberAG: successor of Transcriber as a Debian/Ubuntu package
[Dropping most of the CCs.] Dear Mr. Busson, bastien.bus...@dga.defense.gouv.fr schrieb am 22.09.2011 11:16: > We would be very pleased to see a TranscriberAG package be part of the > repositories as many people, especially from the research community, hope > after the removal of the Transcriber package. you either need to file a RFP (Request For Packaging) or an ITP (Intend To Package) bug. In the former case you just ask the project in general that somebody please start packaging TranscriberAG. No guarantee that this happens (maybe you can contact the previous Transcriber maintainer(s) and ask them, whether they'd be interested in packaging TranscriberAG). In the latter case you'd become the new maintainer of TranscriberAG and package it for Debian. Any questions regarding how to package something for Debian are either answered already by the documents listed under [0] (not all will apply to your case) or you can ask at [1] > This email and any attachments are intended solely for the use of the > individual to whom they are addressed.If you have received this e-mail in > error, please inform the sender immediately without keeping any copy > thereof and delete it from your system. Oh please don't send these standard disclaimers, especially not, when you're contacting a public mailing list. Kind regards, Kai Wasserbäch [0] <http://www.debian.org/devel/#packaging> [1] <mailto:debian-ment...@lists.debian.org> -- E-Mail: cu...@debian.org IRC: Curan Jabber: dri...@debianforum.de URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 signature.asc Description: OpenPGP digital signature
Re: alternative dependency ordering - with respect of packages in main
Dear Gerfried, Gerfried Fuchs schrieb am 20.09.2011 13:12: > Policy is clear on packages in main aren't allowed to depend on > packages outside of main. Now in a fair amount of cases this has been > worked around by having the package outside of main as alternative > dependency and a package in main offer basic functionality for the > package to still be able to work. > > I know that the buildd system likes to pull in the first package in > such an alternative dependency chain. And now I start to wonder: > > Is it allowed for a package in main to have a package _outside_ of main > as first component of an alternative dependency? The package in > question is extremely unlikely to ever be used as Build-Depends, so this > is of a more general question. I'd say – from a technical viewpoint – it should be ok, because the buildds (for main) just shouldn't offer the possibility to install something from outside of main. Though I must admit, that I've no idea, whether this is enforced by the buildds or not (I would hope so, because, otherwise we might end up with Policy-broken builds anyway, in case the main B-D isn't satisfiable at build time, while the non-main is). > What also might be used as argument is the social contract, DFSG #4: > "Our priorities are our users and free software" -- it can be argued > that we don't put the priority on free software in such a case. > > tl;dr - what do you think, is a "Depends: foo-contrib | foo" acceptable > for packages in main or should it be "Depends: foo | foo-contrib" > instead? Ideologically I'd vote for the latter, just to make sure people can rely on getting the free/open/libre installation on default, even if they might need contrib or non-free in some places. If you want/need (maybe add a README.Debian, explaining the differences) the contrib/non-free functionality, you can manually install that. Kind regards, Kai Wasserbäch -- E-Mail: cu...@debian.org IRC: Curan Jabber: dri...@debianforum.de URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 signature.asc Description: OpenPGP digital signature
Re: Wine status
Dear Cesare, dear Ove, Ove Kåven schrieb am 11.09.2011 14:56: > Den 11. sep. 2011 13:44, skrev Cesare Leonardi: >> In the recent past upstream site started to advertise this as Wine Debian >> package: http://dev.carbon-project.org/debian/wine-unstable/ I had nothing to do with that, I actually wasn't even informed in advance and just started to notice a lot more traffic on my site from one day to the other. >> These are deb package that upgrades wine-unstable and that you have to >> install with dpkg. In these days i've tested them and seem to work well. >> The person that make them is Kai Wasserbäch, a Debian developer. I know, that many, including some DDs, want me to provide a APT archive, but I'm not really happy with that, as it might encourage people to use third party packages without a second thought (like: Can I trust the provider?) >> I'm really confused. Why doesn't Kay packages can't be the official Debian >> packages? > > I suspect he always meant it to be temporary - letting users have > *something*, even if the packages may not be perfect and may not even have > been allowed into Debian at the time. This. (It actually served as a place where I could make the builds, I used for filing bugs, available to upstream; then it was named by winehq.org as the primary source for Debian.) You might even read that on my page (e.g. [0] or [1]) too. Though, of course, my blog is not mandatory reading. ;) > He hasn't offered to be a comaintainer. TBH I never intended to maintain Wine, though I'm doing this now, to some extent, anyway. ;) I used Wine and, when I reported upstream bugs to upstream, was asked to try the latest Git or release with some patches applied. Thus I needed to build them and also make the builds available to the upstream devs. (@Ove: I've already a multiarch-ready branch on my system which uses a significantly simplified debian/rules. If you are interested in that, let me know and I put it up somewhere.) Kind regards, Kai Wasserbäch [0] <http://www.carbon-project.org/On_the_unofficial_wine_unstable_packages_on_dev_carbon_project_org.html> [1] <http://dev.carbon-project.org/debian/> -- E-Mail: cu...@debian.org IRC: Curan Jabber: dri...@debianforum.de URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 signature.asc Description: OpenPGP digital signature
Re: 'Alioth' status update
Dear Stephen, Stephen Gran schrieb am 22.05.2011 12:27: > Some bits of the infrastructure are still being bolted back together, > and we expect to send further status updates as they happen. I might have missed that bit of information, but does the above mean, that the Gitweb instance will be back at git.d.o? Or do I need to change the Vcs-Browser fields in some of my packages? Thank you for all your work! Kind regards, Kai Wasserbäch -- E-Mail: cu...@debian.org IRC: Curan Jabber: dri...@debianforum.de URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 signature.asc Description: OpenPGP digital signature
Bug#626770: ITP: liblwp-authen-oauth-perl -- OAuth authentication plugin for LWP
Package: wnpp Severity: wishlist Owner: Kai Wasserbäch * Package name: liblwp-authen-oauth-perl Version : 1.01 Upstream Author : Timothy D Brody * URL : http://search.cpan.org/dist/LWP-Authen-OAuth/ * License : GPL-1+ or Artistic (same as Perl 5.8.8 or later) Programming Lang: Perl Description : OAuth authentication plugin for LWP This is the CPAN Perl module LWP::Authen::OAuth. LWP::Authen::OAuth is an easy to use OAuth authentication plugin for LWP, that should work transparent in almost all cases. Furthermore it reduces the amount of code that needs to be written for an OAuth authentication. -- E-Mail: cu...@debian.org IRC: Curan Jabber: dri...@debianforum.de URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 signature.asc Description: OpenPGP digital signature
Re: Bug#619021: ITP: snes9x -- Super NES emulator
Dear Benoît, Benoît Ryder schrieb am 20.03.2011 14:50: > * Package name: snes9x > Version : 1.52 this package was just removed ([0]) and one of the reasons was "dead upstream". Has this changed? I don't think so, as the removed version equals what you stated in your ITP. If the reasons which lead to the removal are still valid I'd argue against a new snes9x package (please note, that there are other emulators for SNES AFAICS). Kind regards, Kai Wasserbäch [0] <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617588> -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: Best practice for cleaning autotools-generated files?
Dear Marcin, Marcin Owsiany schrieb am 15.03.2011 23:29: > However that README does not give any hints on how to best do the > cleaning. How are others doing it? in puf we're using dh-autoreconf in the dh(7) sequence, which creates a list of modified files, backs them up and restores them later again (through its two commands dh_autoreconf and dh_autoreconf_clean). Kind regards, Kai Wasserbäch -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: How to close a Ubuntu bug?
Dear Scott, Scott Kitterman schrieb am 14.02.2011 22:46: > "Erik Schanze (Debian)" wrote: >> Is there any mail interface like Debian has? > > There is, but it still requires an account. I marked it fixed. can Ubuntu that at least open said interface up to Debian Developers using their Debian address and sign the message with their key (as available from keyring.debian.org)? Because this account requirement is really annoying. I don't want an account on Launchpad but as long as I'm forced to see bug reports on my PTS page (ok I could hide them with Element Hiding Helper or something) I want an easy interface like <mailto:cont...@bugs.debian.org>, so I can at least close or reassign bugs in case that is needed (an example where I'd like to have reassign capabilities: I've one bug showing for Skanlite, that is certainly not a bug in Skanlite but one in libksane (if it still exists at all, that ist), upstream agrees with me on this). Kind regards, Kai Wasserbäch P.S.: I understand that you are not Ubuntu and this is not your decision, but maybe you could pass this on to the proper people. ;) -- E-Mail: cu...@debian.org IRC: Curan Jabber: dri...@debianforum.de URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 signature.asc Description: OpenPGP digital signature
Re: Benötige eine USB Start-Disk(3,5´´F loppy) zum Start für USB-Stick
For the record: I answered Matthias in a private e-mail, just forgot to CC -devel, don't know why I didn't use the "answer list" function. Kind regards, Kai Wasserbäch -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: List of FTBFS in Ubuntu
Hello Lucas, Lucas Nussbaum schrieb am 03.12.2010 08:43: >>From time to time, I do archive rebuilds for Ubuntu too, and I thought > that the results would be interesting for DDs as well, since a FTBFS in > Ubuntu might indicate that the package will FTBFS in the future in > Debian, due to toolchain changes for example. > > Below is a dd-list of the failures. > > Kai Wasserbäch >plasma-widget-yawp already fixed upstream [0] and no problem for Debian (Squeeze), as we ship with KDE 4.4.5. Fix will be in the next upstream release but there is no hurry as KDE 4.6 isn't out yet (Ubuntu uses a beta of KDE 4.6 (4.5.80), where an header file included by yaWP was removed). Kind regards, Kai Wasserbäch [0] <http://yawp.svn.sourceforge.net/viewvc/yawp?view=revision&revision=430> -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: Misc Developer News (#24)
Hello Simon, Simon Ruggier schrieb am 07.11.2010 17:19: > On Sun, Nov 7, 2010 at 1:01 AM, Paul Wise wrote: >> Please file wishlist bugs on the relevant upstream bug trackers. > > I suspect that wouldn't be received very well. I'll file it on debshots > though. why not? just make it generic like „Please add upload functionality for multiple services“ or something like that. And then one of the services can be s.d.n. Kind regrads, Kai Wasserbäch -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: scanlite / scangui - what is the difference?
Dear Hans-J., Am 07.09.10 17:46, schrieb Hans-J. Ullrich: > scangui is part of the kipi-plugins. "apt-file search scangui" will show you. pthat's possible, but I can't check at the moment as I'm not on a Debian system here regularily. > I suppose, the KDE-people integrated your skanlite in KDE (which is ok, as it > is GPL). See in the menu (I have German KDE, so it is below "Bilder einlesen" > below "Grafik". Just to make sure: I'm just the maintainer for Debian (together with Mark Purcell). So I'm not sure how you mean "the KDE-people integrated [my] Skanlite". I consider myself a part (though with very minor contributions, so far) of the Debian KDE team. The place where Skanlite shows up in the K menu is controled by the .desktop file, which the Skanlite package ships (which is upstream's version, IIRC). > In the other hand, skanlite should be deinstalled, when kipi-plugins are > installed, and other round. Just to avoid double-applications. Hm, that would be hard to do Policy compliant (though I haven't rechecked just now (still on vacation)), because it's not a real conflict nor does one break the other. Maybe we could do it as a "Replaces". Though I'm not sure whether all users would want that (I'm not trying to use some random user as a shield, I simply don't know, but I could imagine somebody wanting some random KIPI plugi and still wanting Skanlite for scanning. Maybe we could split the scanning part out of the KIPI plugins so you can really decide between the two. But I'd expect this to be a change happening post-Squeeze.). Anyway, feel free to file a bug against Skanlite and/or scangui with severity wishlist. Though I'd really like to hear something from the KIPI maintainers first, but that's just my personal sentiment. Kind regards, Kai Wasserbäch -- Kai Wasserb√ch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: scanlite / scangui - what is the difference?
Dear Hans-J., I'm the maintainer of Skanlite (I assume you meant Skanlite). Skanlite is (AFAIK) the standalone "replacement" for Kooka, which uses libksane for accessing scanners. I started maintaining Skanlite, when I was missing Kooka from Squeeze (Kooka is the KDE 3.x standalone scanning application and was without upstream development for some time). After asking the Debian KDE maintainers on IRC I was directed towards Skanlite, which wasn't in Debian back then. I didn't find "scangui" on the KIPI homepage [0], but from your description I'd say it is another interface for libksane, which integrates with KIPI-aware programs. But I might be mistaken, as I'm on vacation right now and my internet connections is somewhat limited. Kind regards, Kai Wasserbäch [0] http://www.kipi-plugins.org/drupal/node/1 -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: Razer Mice
Hello Leo, initrd@comcast.net schrieb am 03.07.2010 17:19: > Pardon my accidentally sending my last reply as a private message. Mailing > lists are all new to me. So, let me start with an apology for that. no need to apologize as far as I'm concerned. > So let me find out about RFP on my own and I will deal with it. As I wrote in my first answer: just execute "reportbug wnpp" on a shell and follow the instructions. A RFP is a bug filed against the virtual wnpp package, see [0], for currently filed RFPs (and other types of bugs which are filed against wnpp like ITPs). More information on how to file a bug can be found at [1]. > My apologies again for the trouble and thank you for your replies. You're welcome! Kind regards, Kai Wasserbäch [0] <http://bugs.debian.org/wnpp> [1] <http://www.debian.org/Bugs/Reporting> -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: Razer Mice
Dear reporter, initrd@comcast.net schrieb am 02.07.2010 08:35: > After digging for support for Razer Gaming Mice for the past year, I came > across a project that supports a number of Razer mice and and uses pyqt4 for > the interface. This is a great tool and as I have noticed not just the number > of Linux users growing but gamers whom use such mice, such as myself (I own 2; > Copperhead & Death Adder), I thought it might be a great addition to the > Debian repositories. Is there someone willing to take this on? Is this the > place to ask? If not then redirect me. If so and no-one is willing, would > someone be willing to point me in the direction of how to get sponsored? > I have 5 years of experience using Linux and am willing to learn. you either want to file an so called "Request For Packaging" (RFP) bug, in case you just want to ask for inclusion of the package into Debian. To do that, please run: reportbug wnpp and follow the instructions. In case you want to maintain the package, you want to file an "Intend To Package" (ITP) bug. The command is the same as above, just select ITP instead of RFP when prompted. Please make sure, there isn't already a bug for the package you wish to see enter Debian (reportbug should help you take care of that). Kind regards, Kai Wasserbäch P.S.: What do you mean by "support for Razer Gaming Mice"? Do you mean some configuration interface for mapping buttons or changing sensitivity? Or do you mean a kernel module needed to get them working? In the latter case you might want to talk to the Kernel maintainers before you file a bug. -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: Parallellizing the boot in Debian Squeeze - ready for wider testing
Hello Petter, Petter Reinholdtsen schrieb am 08.05.2010 19:07: > Perhaps we should do a poll to collect > information on how testers experience their boot with > CONCURRENCY=makefile, [...] as one of the testers just a short reply: on several desktops and some basic servers insserv in conjunction with "CONCURRENCY=makefile" works well. I didn't have an unbootable system so far. As far as speed goes: I didn't measure the speed but it feels faster. ;) Kind regards, Kai Wasserbäch -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
ossp-uuid: Orphaning, a new upload or removal?
Dear Piotr, your package ossp-uuid wasn't updated since 2006 by you. In the meantime Steve Langasek and myself fixed several severe bugs (NMU). But we were both limited by what a NMU can do. This leaves the package in a shape I'd call unfit for release even though currently no RC bug is reported against it (I fixed the last). Therefore I'd like to ask you to either resume your work on the package, orphan it or ask for its removal. Though I'd say orphaning would be best for the moment, as postgresql seems to Build-Depend on ossp-uuid. Please note: because the next release starts to appear on the horizon and any action regarding ossp-uuid would have to be taken before the freeze, I'll expect your answer within 20 days (2010-02-15). I don't intend to give an offence by this, it's just to make sure, somebody might have time to step up and take over the package, in case that should be needed. Kind regards, Kai Wasserbäch P.S.: I'm CCing debian-devel (to give a warning ahead to anybody interested in postgresql) and mia (to document this contact attempt). -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debian.org/C%C3%B9ran GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Bug#530915: ITP: skanlite -- KDE4 image scanner based on the KSane backend
Package: wnpp Severity: wishlist Owner: Kai Wasserbaech * Package name: skanlite Version : 0.3 Upstream Author : Kåre Särs Arseniy Lartsev * URL : ftp://ftp.kde.org/pub/kde/stable/4.2.3/src/extragear/ * License : GPL2+ Programming Lang: C++ Description : KDE4 image scanner based on the KSane backend Skanlite is a small and simple scanner application for KDE4 which allows easy scanning of images with an attached scanner. Through the KSane backend it can access a wide variety of different scanner models. Skanlite can be considered the replacement of Kooka. -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Bug#529815: ITP: kde-plasmoid-yawp -- Yet Another Weather Plasmoid fetches weather forcasts for you
Package: wnpp Severity: wishlist Owner: Kai Wasserbäch * Package name: kde-plasmoid-yawp Version : 0.2.3 Upstream Author : Pierpaolo Vittorini , Marián Kyral , Ezequiel Aguerre , Ruan Strydom * URL : http://sourceforge.net/projects/yawp * License : GPL2 Programming Lang: C++ Description : Yet Another Weather Plasmoid fetches weather forcasts for you A nice and simple plasmoid for KDE 4.x to show the weather forcast, works with AccuWeather and Google Weather. Shows a few days in advance. Could be considered to be a replacement for the SuperKaramba script »LiquidWeather++«. -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: Heads-up: KDE4 hitting testing tonight (UTC)
Hello, Adeodato Simó schrieb: > For those following testing, this is just a quick mail to let you know > that KDE4 will become available in Squeeze with tonight's mirror pulse. > (It's KDE 4.2.2, I'm told 4.2.3 will shortly be uploaded to unstable.) > > A note for compiz users: unfortunately it hasn't been possible to migrate > to testing the new compiz, useable with KDE4, because it also depends on > a newer GNOME. In order to upgrade to KDE4, you will have to temporarily > uninstall compiz-kde, or grab compiz-kde and dependencies from unstable. thanks to everyone involved! Great job, but... ... is it possible that there are a few »Replaces« missing? Like »systemsettings replaces kcontrol«? ... is it a aptitude bug or a problem with the version numbers/epochs of the packages, that some packages would be removed because of unmet dependencies event though there is a new package which fits? (like kdm, kwin, ...) At least on my system aptitude reported a lot of broken packages and wanted to remove a hell of a lot of such packages. But I could figure it out manually, so no harm done. ... kaboom's backup functionality is somewhat dubious? Because for me it wasn't possible to backup some data like the album covers and settings of amarok, which led eventually to the point, were I needed to reconfigure amarok and feed it the covers again (form a manual backup). Anyway, I don't want to sound like a complainer and I'm not sure, the above issues are even grave enough for a bug report of minor severity. For me they aren't, but I guess, that should be improved until squeeze is released. So again: thanks for all the work! I love the new KDE and hopefully will continue to do so in the next weeks, when I've worked with it a little bit. ;) Kind regards, Kai -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: make-kpkg and 2.6.29.2 vanilla sources
Hello Raffaele, Raffaele Morelli schrieb: > [...] > > Is it a bug or what? No, as documented in the changelog ([0]) and probably elsewhere you need to put the needed scripts into [1]. In case of initrd generation example scrpts are shipped with kernel-package in [2]. I hope this helped. Greetings, Kai [0] <http://packages.debian.org/changelogs/pool/main/k/kernel-package/current/changelog#versionversion12.001> (please note, that it is also mentioned in later changelog entries for several reasons) [1] [2] -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: xcdroast does no longer work with wodim: Who to blame?
[WARNING: THIS MESSAGE IS PGP/MIME SIGNED, DON'T BLAME MY MUA ;)] The only thing I remember is an ancient (2006) discussion on heise online (and probably elsewhere too) [0] (German only, sorry) about this topic and all this has been brought forward and not backed up by any proofs. Back then the last reply was not to reply... could we please skip to that part. It's just not worth the effort. @all the DDs/DMs and all other contributors: please don't feed the troll. ;) Thanks, Kai [0] http://www.heise.de/open/news/foren/forum-104357/msg-11172557/read/ Joerg Schilling schrieb: >> xcdroast is looking for cdrecord, which does no longer exist in Debian >> Sid (apparently). And wodim does no longer provide a symlink as cdrecord >> or something (apparently). > >> So: xcdroast does no longer work. Who is to blame (Bug entry): xcdroats >> or wodim? > > You need to blame the people who are responsible for removing cdrecord > and who started to include a fork (wodim) that cannot be legally distributed. > > Just add cdrecord from: > > ftp://ftp.berlios.de/pub/cdrecord/alpha/ > > and you get a legal and working system. > > Jörg -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: deb...@carbon-project.org Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: Handling of removed packages
Hello, Marc 'HE' Brockschmidt schrieb: > For some time now, I have been thinking about the problem of packages > which are removed from the archive at some point, without an (enforced) > transition to a new package name. Users of such packages keep them > around, usually never noticing the fact that no security (or other) > support is available anymore. I have somewhat of a deja-vù here with that thread. When I remember correctly just about the beginning of this year there was a discussion about how to find/remove/manage obsolete packages either here on -devel or on -mentors. The aptitude-way Frans pointed out was mentioned there too (maybe by Frans, I can't recall). So the solution then was "the user must check aptitudes obsolete category". And for me that is enough, though a automatic notification by aptitude, when a package is added to that category would be nice. Kind regards, Kai P.S.: This e-mail is just a "reminder", that this was already discussed, but I have right now no time to search the archives. But eventually it helps to avoid reiterating all pros and cons. -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: [EMAIL PROTECTED] Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: GnuPG: Maintainer inactive?
Hello again, Kai Wasserbäch wrote: > [...] Is there anything I can help (I'm certainly not suitable as a maintainer > for that package myself, because it's too essential to be entrusted to someone > who is unknown to (nearly) all people on this list) with, e.g. by triaging > bugs? I've just seen, that Daniel Leidert is already on it and triages the bugs. If you (Daniel) would like me to help you, just let me know. Otherwise just: thank you. Kind regards, Kai Wasserbäch -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: [EMAIL PROTECTED] Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
GnuPG: Maintainer inactive?
Hello, on the 1st of April I wrote an e-mail to James Troup offering my help in hunting down open bugs which are no longer present an thus enabling him to concentrate on packaging GnuPG 1.4.9. But his last action regarding this package is well over an year old and the only updates I can see in the PTS were made by the Security Team. And before I forget to write it: I didn't receive an answer. So my question is: Is James known to be inactive? Are there others currently on the task to get a new version (upstream has 1.4.9) into Debian? Is there anything I can help (I'm certainly not suitable as a maintainer for that package myself, because it's too essential to be entrusted to someone who is unknown to (nearly) all people on this list) with, e.g. by triaging bugs? Should this question already have been discussed somewhere, please point me to it. Thank you in advance for your reply(s). Kind regards, Kai Wasserbäch -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: [EMAIL PROTECTED] Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: Wireless
Hello Jonathan, I think you would feel more at home on one of the user lists [0] or a Debian related forum like [1] and receive your answer faster. But I try to point you to some packages that might help (assuming you've installed your wireless card already). If you are using KDE, you can use for example kwirelessmonitor [2] (an applet for the systray) apart from the KNetworkManager [3]. Under Gnome you might want to have a look at Gnome Network Manager [4]. I hope I was of some help. Kind regards, Kai Wasserbäch P.S.: If you should get multiple answers I would suspect the delay of the mailinglist server as the culprit. ;) [0] http://lists.debian.org/debian-user/ or a localized one like http://lists.debian.org/debian-user-german/ [1] http://www.debianforum.de/ (a German-speaking forum) [2] http://packages.debian.org/etch/kwirelessmonitor [3] http://packages.debian.org/etch/network-manager-kde [4] http://packages.debian.org/etch/network-manager-gnome Jonathan Smith schrieb: > Hello How do I find wireless conncections on Debian? I have installed > Debian 4.0. > Thanks -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: [EMAIL PROTECTED] Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
Re: actively notifying users of removed packages
Hi, Olivier Berger schrieb: > FYI, according to > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464021 I suppose that > users having subscribed to packages in the PTS should now be notified of > such removals (which used not to be the case, and worried us a great > deal some weeks ago ;) this suggests, that a user should subscribe to every package he or she is using. That sound a little impracticable to me considering the number of installed packages on an average desktop system. Especially if someone used tasksel. So I'd prefer what Nico has suggested: subscribing to »secure-testing-announce«. But then it would also be nice to have that like Karl suggested it. From the point of an user that would be the easiest way and integrate wonderfully into the update process. But then stable is what is worked for and if someone uses testing/unstable he/she should watch for herself or himself. So there remains only one question (for me): how is this dealt with on a dist-upgrade? Is ensured that every removed package results in some kind of notification? I believe that is not so (remembering the removal of ipac-ng). Kind regards, Kai -- Kai Wasserbäch (Kai Wasserbaech) E-Mail: [EMAIL PROTECTED] Jabber (debianforum.de): Drizzt URL: http://wiki.debianforum.de/Drizzt_Do%27Urden GnuPG: 0xE1DE59D2 0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2 (http://pgpkeys.pca.dfn.de/pks/lookup?search=0xE1DE59D2&fingerprint=on&hash=on&op=vindex) signature.asc Description: OpenPGP digital signature
