Re: Bug#297121: ITP: wmail -- WindowMaker docklet watching your inbox
Le Sunday 27 February 2005 à 10:08:02, Julien Danjou a écrit: > Package: wnpp > Severity: wishlist > Owner: Julien Danjou <[EMAIL PROTECTED]> > > * Package name: wmail > Version : 2.0 > Upstream Author : Sven Geisenhainer <[EMAIL PROTECTED]> > * URL : http://dockapps.org/file.php/id/70 > * License : Seems specific, but free and probably GPL-compatible > Description : WindowMaker docklet watching your inbox > > > wmail is a Window Maker docklet watching your inbox, which is either a > ordinary mbox or a directory conforming to qmails Maildir format. It > provides a nice little GUI displaying some useful pieces of information > about your inbox (as many other nice wm-apps doing nearly the same > thing...). Per default it uses the $MAIL environment-variable to locate > the inbox you are using, other mailing mechanisms like POP or IMAP are > not supported - use a tool like fetchmail to retrieve POP- or IMAP-based > mail. What are the differences with wmbiff [1]? What features does wmail provide that wmbiff does not? Bye, Package: wmbiff (0.4.26-1) A dockable app that displays information about mailboxes WMBiff is an WindowMaker docking utility, that displays the number of read and unread messages in (usually) five mailboxes. You can also define actions to execute on new mail arrival (for example, play a sound file), [auto]fetchmail from a remote server, execute your mail reader with a mouse click, or list subject lines from unread messages. WMBiff also supports notification of incoming Licq messages, so you can put Licq in the background. At this moment, wmbiff supports unix-style, maildir, pop3, APOP, IMAP and IMAPS mailboxes, as well as Licq and GnomeICU history files. It also includes scripts to perform miscellaneous tasks. At the moment, these include a checker for Debian security updates. wmbiff is similar to the wmmaiload package, but features an LED-style appearance, IMAPS support, and other minor differences. [1] http://packages.debian.org/unstable/x11/wmbiff -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Mactel-linux-devel] MacBook iSight works?
Hello, On 23/07/06, Junichi Uekawa <[EMAIL PROTECTED]> wrote: > I've created a Debian package. I'm having trouble in that it doesn't > seem to work at all with any application I tried. Could people try > out and see if it's going to work? Actually, I managed to get it working on MacBook with Ekiga. I'm looking for success/failure reports now. I installed the Debian package linux-uvc-source and recompiled the driver, installed it, installed libpt-plugins-v4l2 for ekiga and gnomemeeting. I report that my iSight is working on my MacBook pro 17". I now have a external USB webcam for sale :-) Thanks, -- Dr. Ludovic Rousseau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
malsync ready for adoption
Hello, Package: malsync Description: Allows a PalmOS PDA to synchronize to a MAL server MalSync is a command line tool that allows Palm Pilots to synchronize to the AvantGo (http://www.avantgo.com/) or Puma Technologies (http://www.pumatech.com/is_desktop_main.html) servers or any other Mobile Application Link (MAL) server. . Homepage: http://www.tomw.org/malsync/ The decision to orphan malsync is not related to recent GR votes. I do not want to maintain malsync anymore because: - upstream is not maintaining it - it can't compile using the latest libpisock9 library and has then a RC bug #389386 - I do not use it (plucker is much better and has a free software browser on the PDA) If you are interested you should also adopt libmal. It causes a problem on kpilot and I offered the package to the kpilot maintainer without an answer from him. See #389353. If no one adopt it I will request the removal of malsync from unstable. Regards, -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- signature.asc Description: Digital signature
Re: malsync ready for adoption
Le 16.10.2006, à 11:48:41, Daniel Schepler a écrit: > On Sunday 15 October 2006 21:48 pm, Ludovic Rousseau wrote: > > If you are interested you should also adopt libmal. It causes a problem > > on kpilot and I offered the package to the kpilot maintainer without an > > answer from him. See #389353. > > > > If no one adopt it I will request the removal of malsync from unstable. > > Sorry, I missed that message. I'm not interested in maintaining libmal; it's > just an optional add-on to kpilot. If libmal were removed from unstable, I > would most likely just recompile kdepim with the libmal-dev build-dep cut > out. OK. What is preferred for a buggy and unmaintained (upstream) package - removal or - orphaning I can orphan libmal but that will not solve #389353 and the QA will not be able to debug it without access to a PDA and an account on http://www.avantgo.com/ The upsteam maintainer can't test it either so I do not see a fast resolution here. > By the way, where did you get the idea that the submitter of #389353 and the > kpilot maintainer were the same person? I'm not "Peter Robin". :) Oops, sorry. Bye, -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#402193: ITP: macbook-backlight -- Program to change the brightness of Apple MacBook
Le 08.12.2006, à 21:08:49, Enrico Tassi a écrit: > Package: wnpp > Severity: wishlist > Owner: Enrico Tassi <[EMAIL PROTECTED]> > > > * Package name: macbook-backlight > Version : > Upstream Author : Ryan Lortie <[EMAIL PROTECTED]> > * URL : http://desrt.mcmaster.ca/code/macbook-backlight/ > * License : GPL > Programming Lang: C > Description : Program to change the brightness of Apple MacBook > > A simple C program to change the brightness of the MacBook display > tweaking some hardware registers. It works for the first (Core Duo) and > the second (Core 2 Duo) generation of MacBook. You can also have a look at the different (and maybe more actively maintained) version available from [1]. Maybe it would be a good idea to have a Debian package containing the different tools available at [2] instead of just the backlight tool. The other interesting tools are: - keyboard_brigthness - macbook-led - temperature (of the CPU) - hdaps-gl (GL-based laptop model that rotates in real-time via hdaps) These are 2 shell scripts and 2 small C programs. It would be a waste of resources to have a Debian package for each of these. I also propose myself as co-maintainer. I have a write svn access to the upstream repository. Regards, [1] http://svn.sourceforge.net/viewvc/mactel-linux/trunk/tools/backlight/ [2] http://svn.sourceforge.net/viewvc/mactel-linux/trunk/tools/ -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pilot-link in Sid and Sarge: Much bigger question
Le vendredi 25 avril 2003 à 15:27:57, David Krider a écrit: > I would love whatever pointers the lists may have to offer on this, but > it raises a much larger question about versions and currency in general. > I see that pilot-link is the same version in Sid as it is in Woody, and > that version is WELL OVER A YEAR OLD. That's two lifetimes in terms of > Linux. Every other distro of significance is shipping an up-to-date > version. It can't be *that* broken. To me, this doesn't bode well for > the future of Debian, or at least its viability on the desktop. Perhaps > the maintainers don't care about this. I'm new to Debian; I just don't know. You can use my backports at [1]. You will find pilot-link 0.11.7 (the same version as in Debian unstable). You will also find a backport of J-Pilot (one of the packages I maintain for Debian). I provide these backports exactly to solve your problem: help users using stable to use recent programs. Regards, [1] http://people.debian.org/~rousseau/jpilot/ -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
Bug#412149: general: "usb:" stopped working in both gpsbabel and jpilot
Le 23.02.2007, à 17:05:45, Steve Langasek a écrit: > On Fri, Feb 23, 2007 at 06:27:01PM -0600, Reid Priedhorsky wrote: > > The following are the packages I upgraded between working and non-working > > USB: > > > > > 2007-02-20 21:36:47 status installed libgphoto2-port0 2.2.1-16 > > 2007-02-20 21:36:50 status installed libgphoto2-2 2.2.1-16 > > > > > I'm not sure for which package this bug report is appropriate. libusb seems > > a > > likely candidate, but I haven't upgraded that package since October and > > haven't touched the configuration in a while. > > This latest libgphoto update fixed a security hole whereby libgphoto's udev > rules would wrongly grant access to the plugdev group on all usb devices > instead of just those related to cameras. An interesting possibility here > is that your use of libusb depended on libgphoto's bug. :) > > This was bug #405006. A comment from this bug log: > > > What class of USB devices are ending up under group plugdev that > > shouldn't? > > It concerns the raw USB devices, in /dev/bus/usb/, used by libusb for > userland drivers. > > So I would say this isn't a bug at all, but that you need to set up > additional permissions on /dev/bus/usb/* for your use. pilot-link from testing/etch provide the file /usr/share/pilot-link/udev/60-libpisock.rules This file should be installed as a udev rule to set the group and permission of the USB device used for the PDA. Also read /usr/share/doc/pilot-link/README.libusb.gz All this is automatic with pilot-link 0.12.2-7 (from unstable). bye, -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
where to find linux-kbuild-2.6.21?
Hello, I installed linux-image-2.6.21-1-686 from http://kernel-archive.buildserver.net and I would like to also install linux-headers-2.6.21-1-686 (to build some modules for the Apple MacBook Pro not included in the Debian kernel). The problem is that linux-headers-2.6.21-1-686 depends on linux-kbuild-2.6.21 but I can't find this package anywhere. Where is linux-kbuild-2.6.21? I sent this question on the debian-kernel mailing list 2 days ago but got no answer yet. Thanks -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: where to find linux-kbuild-2.6.21?
Le 08.05.2007, à 21:25:06, David Moreno Garza a écrit: > Ludovic Rousseau escribió: > > I installed linux-image-2.6.21-1-686 from > > http://kernel-archive.buildserver.net and I would like to also install > > linux-headers-2.6.21-1-686 (to build some modules for the Apple MacBook > > Pro not included in the Debian kernel). > > > > The problem is that linux-headers-2.6.21-1-686 depends on > > linux-kbuild-2.6.21 but I can't find this package anywhere. > > > > Where is linux-kbuild-2.6.21? > > AFAICT, linux-image-2.6.21 hasn't hit Debian yet. linux-image-2.6.21 is not yet available in unstable but is available from the snapshot server as described in [1]. I imagine that linux 2.6.21 is not the priority of the kernel team. So I will wait. I just want to make them aware of the missing package. Since linux-image-2.6.21 is not an official Debian package I can't use the BTS to report the bug. Do you know an efficient way to report the problem? Regards, [1] http://wiki.debian.org/DebianKernel -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: where to find linux-kbuild-2.6.21?
Le 10.05.2007, à 00:25:32, Stephen Gran a écrit: > This one time, at band camp, Ludovic Rousseau said: > > linux-image-2.6.21 is not yet available in unstable but is available > > from the snapshot server as described in [1]. > > > > I imagine that linux 2.6.21 is not the priority of the kernel team. So > > I will wait. I just want to make them aware of the missing package. > > Since linux-image-2.6.21 is not an official Debian package I can't use > > the BTS to report the bug. Do you know an efficient way to report the > > problem? > > I have always just asked them on IRC on #debian-kernel. Have you done this time again? If not, could you? (I do not use IRC.) Thanks -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495438: ITP: python-pyscard -- Python wrapper above PC/SC API
Package: wnpp Severity: wishlist Owner: Ludovic Rousseau <[EMAIL PROTECTED]> * Package name: python-pyscard Version : 1.6.7 Upstream Author : Jean-Daniel Aussel <[EMAIL PROTECTED]> * URL : http://pyscard.sourceforge.net/ * License : LGPL v2.1+ Programming Lang: C, Python Description : Python wrapper above PC/SC API This package contains a wrapper to use PC/SC from a Python program. PC/SC is an API to communicate with smart cards and smart card readers. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#447393: RFA: bins -- Generate static HTML photo albums using XML and EXIF tags
Package: wnpp Severity: normal Hello, I do not use bins anymore. The co-maintainer, Martin Michlmayr, do not have time to maintain it either. Debian bugs have been formwared upstream at https://gna.org/bugs/?group=bins but none were ever answered. It looks like bins has been orphaned upstream. If you want it please take it. Regards, Package info: Description: Generate static HTML photo albums using XML and EXIF tags BINS generates a complete static gallery (images and HTML) with thumbnails and image lists, using XML files to hold information about each image. Includes bins_edit and bins-edit-gui tools for adding information to the XML files. Interprets EXIF and JFIF tags (and Canon extensions) in the jpeg directly. Gallery appearance customizable through HTML templates; gallery can be generated in different languages. . Based on SWIGS (Structured Web Image Gallery System). . Homepage: http://bins.sautret.org/ -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
How to manage shared Debconf questions?
Hello, I maintain the source package pilot-link. Pilot-link is a set tools to communicate with a Palm PDA (through serial, USB or infra red). This source package provides a library libpisock8 and a package with command line tools pilot-link. The library uses by default the file /dev/pilot. /dev/pilot is, in general, a symbolic link to the real device (/dev/ttyS0, /dev/ttyS1, /dev/USB0, etc.) I also maintain jpilot which is a graphical application to synchronise with the PDA. jpilot uses libpisock8. History: I am not the original DD for pilot-link or for jpilot. Up to pilot-link 0.11.7-7 the Debconf question was in pilot-link package (the command line tools package) In pilot-link 0.11.8-1 I moved the Debconf question in libpisock8 since it is by this library that /dev/pilot is used. I then received bug #205059 asking to move the question elsewhere. The problem described in this bug is that libpisock8 is a dependency for evolution and only a few people using evolution also use a PDA. So I moved back the question in the command line tools package. I also included the Debconf question in the jpilot package. It is needed since jpilot is linked with libpisock8 but does not need the pilot-link package. So instaling jpilot, libpisock8 but not pilot-link would not create the needed /dev/pilot symlink. I asked the maintainers of packages using libpisock8, and directly using the PDA features (so not to the evolution package maintainer for example), to add the Debconf question in their package. I filed a whishlist bug on the packages: yank (#218663), mhc-utils (#218664), kpilot (#218665), gnome-pilot (#218666). I then have a discussion with the gnome-pilot maintainer (see bug #218666). The problem is that maintained the same Debconf question is duplicated work for all the maintainers (and even more work with the translations). Possible solutions: --- A. Have a duplicate question in most package using libpisock8 and /dev/pilot (solution I pushed). For example see debconf-devel(7): SHARED TEMPLATES It's actually possible to have a template and a question that are shared among a set of packages. All the packages have to provide an identical copy of the template in their templates files. This can be useful if a bunch of packages need to ask the same question, and you only want to bother the user with it once. Shared templates are gener- ally put in the shared/ pseudo-directory in the debconf template names- pace. B. Have the question in libpisock8 only and "annoy" users of evolution but without a PDA. C. Have a new and small package with only the Debconf question and add a dependency on this package for concerned packages. D. Centralise the Debconf question in pilot-link package only and add an not really needed dependency on this package. My prefered solution is A but I would like to get comments so I can "justify" my choice with related packages maintainers I've contacted . I have checked the Debian Developer's Reference "6.5 Configuration management with debconf" but it just redirects to debconf-devel(7). Thanks, -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
OT: smart card/USB dongle solution
Le mercredi 03 décembre 2003 à 14:00:51, Russell Coker a écrit: > I agree that smartcards would help a lot. However as has been previously > suggested the cost of 1200+ smart-card readers is probably prohibitive. I don't know how a USB dongle compares with a smart card reader regarding price. > I have sent a message to Werner asking if the GPG smart-card device could be > re-implemented with a USB interface. I think that a USB dongle with GPG > technology would be a good option as most developer's machines already have > USB support. You can also use a GemPC Key [1] smart card reader. A free software driver for this reader exists [2]. The GemPC Key is nice since it has the form factor of a USB dongle and still is a smart card reader (so with the security of the smart card). The smart card is a plug-in model like you can find in GSM phones. You can leave the smart card in the reader and remove the reader instead of removing the card. I am also aware of a cheaper product in which the smart card is soldered in the reader. This product is not yet publicly available. Regards, [1] http://www.gemplus.com/products/gempckey/ [2] http://pcsclite.alioth.debian.org/ccid.html -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
OT: Smartcards and Physical Security
Le mardi 02 décembre 2003 à 17:19:22, Tom a écrit: > Smartcards would have avoided the Debian compromise: merely having a > compromised DD box would have prevented bad guy from getting on the box
adopting/kidnapping plucker, any objection?
Hi, The package plucker has 2 RC bugs. The lastest upload is dated 1 Dec 2002 (one year ago!). The package was orphaned (#160472, 11 Sep 2002) and adopted by Pablo S. Torralba. Pablo S. Torralba was/is not yet a DD and the last upload was sponsored by Amaya Rodrigo Sastre. The two RC bugs are very easy to fix but nothing was done. I plan to do an NMU to correct these two RC bugs so that plucker can be released in sarge. I also plan to adopt plucker and package a new upstream version (Debian plucker is 1.2 and upstream is 1.6). If anyone has an objection to this adoption please reply on the list. Regards, -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
Re: adopting/kidnapping plucker, any objection?
Le vendredi 05 décembre 2003 à 12:38:10, Amaya a écrit: > I was out to the movies with him yesterday, he is not MIA or anything. > We even talked about plucker's state. He is in the proccess of fixing > the bugs. Good news. > Comanteinance may be an option? Why not. It may be a good solution. I will upload my NMU to correct the two RC bugs in DELAYED/7-day as explained in [1]. So he has enough/some time to fix the bugs himself and upload a new version. Thanks, [1] http://www.debian.org/doc/manuals/developers-reference/ch-pkgs.en.html#s-nmu-when -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
Re: Bug#276627: ITP: systraq -- monitor your system and warn when system files change
Le Friday 15 October 2004 à 10:47:26, Laurent Fousse a écrit: > Package: wnpp > Severity: wishlist > > * Package name: systraq > Version : 0.0.20041015 > Upstream Author : Joost van Baal > * URL : http://mdcc.cx/software/ > * License : GPL > Description : monitor your system and warn when system files change > > Systraq daily sends you an email listing the state of your system. > Furthermore, if critical files have changed, you'll get an email within a > shorter notice. Systraq consists of few very small shell scripts. > . > It can help you implementing a not too strict security policy. For more > demanding systems, you'd better use something like tripwire. Make sure you > really want to do the monitoring this script offers: it might not comply with > your site's privacy policy. Getting informed when users' config file change > might be too intrusive. > . > Other similar tools are available in Debian (`diffmon' for instance), but > systraq is less intrusive because it can warn for file changes without > mailing > a complete diff (which is not desirable for e.g. /etc/shadow). Can you also document what are the differences between systraq and checksecurity? checksecurity does _not_ send a diff of the modified files. This feature (no diff sent) seams to be the major advantage of systraq over what was provided by *BSD according to [1]. checksecurity was part of cron so any Debian stable user has it. It is now just recommended by cron. I do not object to the inclusion of this package but would like to know what are the benefits compared to an already existing Debian package. Regards, [1] http://mdcc.cx/pub/systraq/systraq-latest/doc/manual.html -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
Bug#143947: ITP: jpilot-mail -- Mail plugin for jpilot (Palm Pilot desktop)
Package: wnpp Version: N/A; reported 2002-04-21 Severity: wishlist * Package name: jpilot-mail Version : 0.0.6 Upstream Author : Oliver Kurth <[EMAIL PROTECTED]> * URL : http://innominate.org/kurth/jpilot-Mail/ * License : GPL Description : Mail plugin for jpilot (Palm Pilot desktop) jpilot-mail is a mail plugin for jpilot which enables you to deliver mail that was written on your pilot and upload mail that you received to your pilot. jpilot-mail sends mails via SMTP. This package was requested in RFP bug #87404 in Feb 2001. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: L10n of Debconf templates
Le Sunday 21 April 2002 à 09:24:15, Brian May a écrit: > On Fri, Apr 19, 2002 at 10:00:31AM +0200, Michael Piefel wrote: > > I wouldn't weep. Seperate files is a very reasonable thing to do. > > Dumb question of the day: how do you put it in a seperate file? > > What should this seperate file be called, etc? http://www.debian.org/international/l10n/templates/hints Maybe this page would benefit a better publicity. Manpages are fine but a good and real example is also very usefull. Regards, -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le Camembert, L.R. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#155950: [RFP]: grisbi -- A personal finance tracking program
Le jeudi 08 août 2002 à 19:01:32, Benjamin Drieu a écrit: > Package: wnpp > Severity: wishlist > > * Package name: grisbi > Version : 0.3.2 > Upstream Author : Cédric Auger <[EMAIL PROTECTED]> > * URL : http://www.grisbi.org/ > * License : GPL > Description : A personal finance tracking program based on GTK grisbi (grisbi-0.3.1.i386.deb) is already available as a Debian package from the official web site. Why not just patch (change - to _ in the name) and upload yourself (since you are a DD) the Debian version made by the upstream author? Regards, -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le Camembert, L.R. --
Re: apt-get wants to upgrade package to same version?
Le mercredi 21 août 2002 à 13:28:30, Brian May a écrit: > Hello, Hi, > I have just being playing around with apt-proxy, and noticed something > weird. Every time I run apt-get, it wants to upgrade the packages it > just upgraded 5 seconds ago (it only happens on this computer, too): [..] > scrooge:/tmp# apt-cache policy kerberos4kth1 > kerberos4kth1: > Installed: 1.1-11-2 > Candidate: 1.1-11-2 > Version Table: > 1.1-11-2 0 > -1 http://snoopy.apana.org.au unstable/main Packages > 1.1-11-2 0 > 700 http://snoopy.apana.org.au woody/main Packages > *** 1.1-11-2 0 > 100 /var/lib/dpkg/status > 1.1-8-2 0 > 700 http://snoopy.apana.org.au woody/updates/main Packages > 700 http://snoopy.apana.org.au woody/non-US/main Packages I have just had the same problem (with different packages). $ apt-cache policy libpisock8 libpisock8: Installed: 0.11.3-2 Candidate: 0.11.3-2 Version Table: 0.11.3-2 0 500 http://http.us.debian.org unstable/main Packages 0.11.3-2 0 990 http://people.debian.org woody/. Packages *** 0.11.3-2 0 100 /var/lib/dpkg/status And apt-get wanted to reinstall the same packages again and again. $ sudo apt-get -s upgrade Reading Package Lists... Done Building Dependency Tree... Done The following packages will be upgraded libpisock++0 libpisock8 pilot-link 3 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Inst libpisock8 (0.11.3-2 Backports from sid:3.0/stable) Inst libpisock++0 (0.11.3-2 Backports from sid:3.0/stable) Inst pilot-link (0.11.3-2 Backports from sid:3.0/stable) Conf libpisock8 (0.11.3-2 Backports from sid:3.0/stable) Conf libpisock++0 (0.11.3-2 Backports from sid:3.0/stable) Conf pilot-link (0.11.3-2 Backports from sid:3.0/stable) After I changed the order of the lines in /etc/apt/sources.list the "bug" was corrected. I now have: $ apt-cache policy libpisock8 libpisock8: Installed: 0.11.3-2 Candidate: 0.11.3-2 Version Table: *** 0.11.3-2 0 990 http://people.debian.org woody/. Packages 100 /var/lib/dpkg/status 0.11.3-2 0 500 http://http.us.debian.org unstable/main Packages from sources.list(5) you can read: "The file lists one source per line, with the most preferred source listed first." Try to reorder your sources.list file. Hope this helps. Regards, -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le Camembert, L.R. --
Bug#158798: ITP: jpilot-backup -- Backup plugin for J-Pilot
Package: wnpp Version: N/A; reported 2002-08-29 Severity: wishlist * Package name: jpilot-backup Version : 0.42 Upstream Author : Jason Day <[EMAIL PROTECTED]> * URL : http://jasonday.home.att.net/code/backup/backup.html * License : GPL Description : Backup plugin for J-Pilot This program enhances jpilot's own backup, making it much more flexible, handling automatic backups, configuring which applications/databases to back up and which to ignore, etc.
Bug#143659: ITP: jpilot-syncmal -- MAL plugin for jpilot (Palm Pilot desktop)
Package: wnpp Version: N/A; reported 2002-04-19 Severity: wishlist * Package name: jpilot-syncmal Version : 0.70 Upstream Author : Jason Day <[EMAIL PROTECTED]> * URL : http://jasonday.home.att.net/code/syncmal/syncmal.html * License : Mozilla Public License Description : MAL plugin for jpilot (Palm Pilot desktop) jpilot-syncmal is a MAL (Mobile Application Link) plugin for jpilot. The real job to synchronise over the Internet is done by malsync. . The most famous MAL sites are AvantGo (www.avantgo.com) or Puma Technologies (www.pumatech.com) servers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers
Hello, 2011/5/18 Hendrik Sattler : > Zitat von Godfrey Chung : > >> Before we started the driver project in 2009, we had requested to join as >> a developer for libccid in alioth.debian.org but the author rejected us with >> no reason. As the same time, our customer pushed us to release Linux driver. >> Therefore, we decided to release our Linux driver based on libccid and had a >> plan to release our driver to any Linux Distributions. Godfrey, I do not remember rejecting your request. The normal steps are first to send good patches to the project before requesting to join. You do not need to be on alioth.debian.org to participate to the development of libccid. Godfrey, do you participate on the MUSCLE (Movement for Using Smart Card in a Linux Environment) mailing list [1]? I could not find any message from "Godfrey Chung" in my email archives. > But libccid evolves and forks of such projects do usually not follow. This > leaves both in a rather sad situation. Did you track the changes of 1.3.12 > and 1.3.13? Any intention to rebase the work on 1.4.x so libusb-1.0 gets > used instead of libusb-0.1? Good question. >> Please note that libccid upstream author and Debian maintainer are same >> person. He may reject our changes. > > Let's CC him so that he can comment... Thanks for the notice. Godfrey, are you a Debian Developer? If not the bug should be an RFP instead of ITP. But that is a minor point. Bye, [1] http://musclecard.com/list.html -- Dr. Ludovic Rousseau -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktikqprmnpy8s6ntjgnevte4rfr+...@mail.gmail.com
How to use remove-on-upgrade to remove a configuration file?
Hello, I am fixing Debian bug #990154. After some work I am able to remove the obsolete conf file using: rm_conffile /etc/reader.conf.d/0comments 1.9.3-2~ pcscd in debian/pcscd.maintscript Nice. Now I would like to use the method documented in deb-conffiles https://manpages.debian.org/unstable/dpkg-dev/deb-conffiles.5.en.html I would need to add in the DEBIAN/conffiles of the pcscd package the line: remove-on-upgrade /etc/reader.conf.d/0comments But how do I generate a .deb package with this extra line? What is the magic dh command or file to do that? Where is it documented? I tried to use a file debian/pcscd.conffiles but this file is no more used with debhelper version 12 https://manpages.debian.org/buster/debhelper/dh_installdeb.1.en.html I searched for occurrences of "remove-on-upgrade" in https://codesearch.debian.net/ but I only find references to dpkg source code. No Debian package is using or has used "remove-on-upgrade"? Thanks -- Dr. Ludovic Rousseau
Re: How to use remove-on-upgrade to remove a configuration file?
Hello Niels, Le 08/08/2021 à 09:09, Niels Thykier a écrit : Ludovic Rousseau: Hello, I am fixing Debian bug #990154. After some work I am able to remove the obsolete conf file using: rm_conffile /etc/reader.conf.d/0comments 1.9.3-2~ pcscd in debian/pcscd.maintscript Nice. Now I would like to use the method documented in deb-conffiles https://manpages.debian.org/unstable/dpkg-dev/deb-conffiles.5.en.html I would need to add in the DEBIAN/conffiles of the pcscd package the line: remove-on-upgrade /etc/reader.conf.d/0comments But how do I generate a .deb package with this extra line? What is the magic dh command or file to do that? Where is it documented? I tried to use a file debian/pcscd.conffiles but this file is no more used with debhelper version 12 https://manpages.debian.org/buster/debhelper/dh_installdeb.1.en.html I searched for occurrences of "remove-on-upgrade" in https://codesearch.debian.net/ but I only find references to dpkg source code. No Debian package is using or has used "remove-on-upgrade"? Thanks Hi Ludovic, You cannot use that feature yet as it would break during upgrade. The dpkg version in stable does not support the feature. Which is also why there is no debhelper feature to support it yet. OK. I was searching for something that does not (yet) exist :-) My plan was to upload the package in Bullseye +1 so after the (soon) release of Bullseye. Bullseye will then be the new stable and will have dpkg 1.20.9. So that should work. No? Thanks -- Dr. Ludovic Rousseau
