Some doubts about patching
Hi all, I've been checking the website of "Release-critical bugs status" at http://bugs.debian.org/release-critical/debian/all.html. And I have several questions: * I have installed Wheezy but not Sid nor Squeeze: Can I filter the bugs to find only those corresponding to Wheezy? * Imagine that I start to create a patch: How do I know that there is any maintainer developping a patch for the same bug? * If I create a bug: Do I have to sign it before sending it to the DM or DD that maintain the package? And if so, my key is not in keyring.debian.org, is there a problem? -- ·´'`. :: Sr.Arcos http://www.debianart.org/cchost/?ccm=/people/SrArcos : :' : :: Debian GNU/Linux ¿Contributor? ¿Member? ¿Diffuser? User yet not Maintainer `. `' :: GPG Public Key2329D273 @ subkeys.pgp.net `-:: Fingerprint AF26 3EB5 E37B F81B 108E 3A57 E605 D0D4 2329 D273 Debian :: Ready to help https://alioth.debian.org/users/srarcos-guest/
Re: Some doubts about patching
On Sat, Jul 28, 2012 at 11:41:24AM +0200, Jose Antonio wrote: > Hi all, > > I've been checking the website of "Release-critical bugs status" at > http://bugs.debian.org/release-critical/debian/all.html. And I have several > questions: > > * I have installed Wheezy but not Sid nor Squeeze: Can I filter the bugs to > find only those corresponding to Wheezy? The second set of tags indicate what releases a bug applies to: O for oldstable (lenny), S for stable (squeeze), T for testing (wheezy), U for unstable (sid) or E for experimental. > > * Imagine that I start to create a patch: How do I know that there is any > maintainer developping a patch for the same bug? I don't know how you could know that. > > * If I create a bug: Do I have to sign it before sending it to the DM or DD > that maintain the package? And if so, my key is not in keyring.debian.org, > is there a problem? Anyone can report a bug without signature. Regards, Bart Martens -- 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/20120728094825.gf6...@master.debian.org
Re: Some doubts about patching
On 2012-07-28 11:41, Jose Antonio wrote: > Hi all, > > I've been checking the website of "Release-critical bugs status" at > http://bugs.debian.org/release-critical/debian/all.html. And I have several > questions: > > * I have installed Wheezy but not Sid nor Squeeze: Can I filter the bugs to > find only those corresponding to Wheezy? > > [...] Hi, http://bugs.debian.org/release-critical/ has a "Only bugs relevant to testing" link, which may be what you are looking for. ~Niels -- 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/5013b67b.90...@thykier.net
RFH: NFS support and networking
Hi folks, For several years, there have been a number of NFS issues in initscripts. Some of those are now resolved, but there are still a number of NFS issues present in wheezy which I'm unable to resolve myself, either because I can't reproduce them or because I'm insufficiently familiar with the issues involved. Some of these may be consequences of the new ifupdown and associated changes, but not all. We still have the ASYNCMOUNTNFS option in mountnfs.sh, which is a horrible hack in its own right. We should have a single way to mount NFS filesystems that works in all cases, rather than a poorly documented option that makes a broken script work in some situations. Current issues are: #540291 initscripts: fails to mount NFS shares at boot #674039 /etc/network/if-up.d/mountnfs: boot stalls by 3 minutes because network is not configured yet (using network-manager) But we also have: #430760 No NFS mounts after waking up server during client boot #434570 if-up.d/mountnfs doesn't work on nfs-root systems #434775 nfs-common: fails to mount nfs volumes when booted with ip= command line #496007 initscripts: if-up.d/mountnfs should not try to wait for all auto interfaces #521357 initscripts: /etc/network/if-up.d/mountnfs fails with slow interfaces (Token Ring) #530583 add ASYNCMOUNTNFS to default rcS #540291 initscripts: fails to mount NFS shares at boot #551555 mountnfs.sh: start should declare dependency on name resolver #578254 nfs mounts are not working at boot #602212 initscripts: NFS shares not mounted properly when using WLAN and NetworkManager #608862 network-manager: automounted nfs volumes no longer mount when connecting with wireless #612519 initscripts: mountnfs ignore ASYNCMOUNTNFS=no for hotplug interfaces #616330 /etc/network/if-up.d/mountnfs: mountnfs script stalls for 2minutes on boot Even discounting the network-manager related bugs, there are a lot of issues with NFS, and there have been for many years. If we want decent NFS support in wheezy, the mountnfs.sh and /etc/network/if-up.d/mountnfs scripts need some attention from an NFS expert. I would be very grateful for anyone who could contribute their time for getting some of the above issues resolved for wheezy. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- 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/20120728100355.gx25...@codelibre.net
Re: Some doubts about patching
On Sat, 28 Jul 2012 09:48:25 + Bart Martens wrote: > On Sat, Jul 28, 2012 at 11:41:24AM +0200, Jose Antonio wrote: > > * Imagine that I start to create a patch: How do I know that there is any > > maintainer developping a patch for the same bug? > > I don't know how you could know that. There are established protocols for that, well used in BSP's for a long time. 0: Join #debian-bugs in IRC irc.oftc.net 1: claim the bug number on that channel, describing what you are doing. Ask if anyone else wants to help or is interested in that package. 2: You can also claim the bug using the bts program from devscripts. 3: Write a reply to the bug, mentioning that you think you have some idea of what might be going on and that you're working on it. (i.e. by the time you think you know enough about the problem to create a patch, you should document the basic premise on the bug report so that everyone else knows that something might happen to help fix it.) Even if the patch isn't complete, *write something on the bug report* with as many details as you can provide. You don't have to solve every problem with the package. It's quite common for a package which fails to build from source to have one initial problem which then hides subsequent failures further in the build. If you can't fix the subsequent ones, just get the patch for the first one in the bug report. It will at least help someone else. For RC bugs during a freeze, as now, you really only want to fix the problem(s) directly related to the bug - it's not about making a complete tidy-up or fixing all lintian issues or anything except the bug. Keep the patch small and clean of generated output like autoconf changes and other noise. Overall, there are so many bugs and so few people working on them at any one time that if the bug report doesn't show someone already has some ideas for the fix, it's likely that nobody is actively working on it. Even if they are, your patch may show a different approach and is still worthwhile. > > * If I create a bug: Do I have to sign it before sending it to the DM or DD > > that maintain the package? And if so, my key is not in keyring.debian.org, > > is there a problem? > > Anyone can report a bug without signature. Signatures and keyring.debian.org only relate to uploads. Creating the patch is a large part of the work - don't stress if you can't upload, just create the patch and feed it back to the bug report. There are separate mechanisms for sponsoring the upload or you can just let someone else turn your patch into an upload. That can only happen if you put the patch into the bug report, so concentrate on that step. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpAENcnaOapy.pgp Description: PGP signature
Re: Calling Noah Slater
David Bremner writes: > A three weeks ago Jakub Wilk noticed a long standing file conflict > between racket and planet-venus (#680685). I realize three weeks is not > _that_ long to wait for a response, but we are in the freeze and I'd > like to resolve the bug. > > Does anyone (or Noah?) know if Noah is still interested in his Debian > packages? It seems like it is has been a few years since he last did an > upload. Gah, I typoed Noah's email in the first message of the thread, sorry about that. d -- 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/87lii4vz8o.fsf@zancas.localnet
Calling Noah Slater
Hi All; A three weeks ago Jakub Wilk noticed a long standing file conflict between racket and planet-venus (#680685). I realize three weeks is not _that_ long to wait for a response, but we are in the freeze and I'd like to resolve the bug. Does anyone (or Noah?) know if Noah is still interested in his Debian packages? It seems like it is has been a few years since he last did an upload. David -- 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/87obn0vzpm.fsf@zancas.localnet
Bug#683077: ITP: python-openslide -- python wrapper for reading whole slide image files
Package: wnpp Severity: wishlist Owner: Mathieu Malaterre * Package name: python-openslide Version : 0.3.0 Upstream Author : Carnegie Mellon University * URL : https://github.com/openslide/openslide-python * License : LGPL Programming Lang: Python Description : python wrapper for reading whole slide image files OpenSlide is a C library that provides a simple interface to read whole-slide images also known as virtual slides. . Whole-slide images, also known as virtual slides, are large, high resolution images used in digital pathology. Reading these images using standard image tools or libraries is a challenge because these tools are typically designed for images that can comfortably be uncompressed into RAM or a swap file. Whole-slide images routinely exceed RAM sizes, often occupying tens of gigabytes when uncompressed. Additionally, whole-slide images are typically multi-resolution, and only a small amount of image data might be needed at a particular resolution. . This library currently supports: * Trestle (.tif) * Hamamatsu (.vms, .vmu) * Aperio (.svs, .tif) * MIRAX (.mrxs) * Generic tiled TIFF (.tif) . This package contains the python module needed to run OpenSlide applications. -- 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/20120728132227.30960.80507.report...@lirispat.univ-lyon1.fr
Bug#683129: general: Please consider packaging libopencv-nonfree2.4.
Package: general Severity: wishlist Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? I need libopencv-nonfree2.4 to get my opencv code working. Reference: http://docs.opencv.org/modules/nonfree/doc/nonfree.html * What exactly did you do (or not do) that was effective (or ineffective)? N/A * What was the outcome of this action? I could not find libopencv-nonfree2.4 on snapshot.debian.org. * What outcome did you expect instead? I hope the package libopencv-nonfree2.4 can be packaged, just like the one in the following link. https://launchpad.net/~philip5/+archive/extra/+build/3654668 *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20120728235934.18138.17544.reportbug@aoi
Processed: reassign 683129 to wnpp, retitle 683129 to RFP: libopencv-nonfree2.4
Processing commands for cont...@bugs.debian.org: > reassign 683129 wnpp Bug #683129 [general] general: Please consider packaging libopencv-nonfree2.4. Bug reassigned from package 'general' to 'wnpp'. Ignoring request to alter found versions of bug #683129 to the same values previously set Ignoring request to alter fixed versions of bug #683129 to the same values previously set > retitle 683129 RFP: libopencv-nonfree2.4 Bug #683129 [wnpp] general: Please consider packaging libopencv-nonfree2.4. Changed Bug title to 'RFP: libopencv-nonfree2.4' from 'general: Please consider packaging libopencv-nonfree2.4.' > thanks Stopping processing here. Please contact me if you need assistance. -- 683129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13435215925379.transcr...@bugs.debian.org
Bug#683143: ITP: brise -- Rime Schema Repository
Package: wnpp Severity: wishlist Owner: Qijiang Fan * Package name: brise Version : 0+git20120727 Upstream Author : GONG Chen * URL : http://github.com/lotem/brise * License : GPL Programming Lang: None Description : Rime Schema Repository This is the schema data of RIME Input Method Engine. -- 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/20120729061928.25565.70453.reportbug@fqj1994-laptop
