[gentoo-dev] Re: CUPS 1.4 and FFMpeg 0.6
Hi, I tried to create an appropriate news item for the CUPS 1.4 stabilisation. p...@g.o is cced. Release deadline is Monday 13 Sep 2010, comments please. Timo Gurr tg...@gentoo.org: If for whatever reason (broken/old printer drivers) that doesn't work out there's still the way to install CUPS 1.4 with USE=-usb to get the old CUPS 1.3 behaviour back. Title: Upgrade to CUPS 1.4 Author: Christian Faulhammer fa...@gentoo.org Author: Timo Gurr tg...@gentoo.org Author: Gentoo Printing Team print...@gentoo.org Content-Type: text/plain Posted: 2010-09-13 Revision: 1 News-Item-Format: 1.0 Display-If-Installed: net-print/cups-1.4 CUPS 1.4 is a major update in printing support and thus may cause some problems when coming from version 1.3. Most users should see a smooth update, although only net-print/gutenprint and net-print/hplip are considered as supported drivers. If you happen to rely on other drivers for your printer, you may have to research if problems occur. Local USB printers are known to occasionally have issues, which can be resolved in most cases by the following steps: 1. Disable usblp in your kernel configuration by setting CONFIG_USB_PRINTER=n. Don't forget to rebuild the kernel and reboot with that new image. 2. Delete /etc/cups. 3. (Re-)install CUPS 1.4 with USE=usb. 4. Configure printer(s) from scratch via the CUPS web interface. 5. If your printer is a multifunction device, be sure you got the udev rules setting the device permissions in shape so CUPS can access the device. If you still have issues, you can revert to the old CUPS 1.3 behaviour by setting USE=-usb on net-print/cups. V-Li -- Christian Faulhammer, Gentoo Lisp project URL:http://www.gentoo.org/proj/en/lisp/, #gentoo-lisp on FreeNode URL:http://gentoo.faulhammer.org/ signature.asc Description: PGP signature
Re: [gentoo-dev] bug-wranglers queue is large
Ping again The list has 100 unassigned bugs for more than one week I plan to create a patch for this[1] page and poke devrel for that [1]: http://www.gentoo.org/proj/en/devrel/staffing-needs/ Cheers -- Markos Chandras (hwoarang) Gentoo Linux Developer Web: http://hwoarang.silverarrow.org pgpx2qkJTCPck.pgp Description: PGP signature
Re: [gentoo-dev] bug-wranglers queue is large
On 9/10/10 4:18 AM, Markos Chandras wrote: I plan to create a patch for this[1] page and poke devrel for that [1]: http://www.gentoo.org/proj/en/devrel/staffing-needs/ Actually, you just need to add some tags to your project page and the Staffing Needs page gets automatically updated after few minutes. Example: recruitment job summaryHerd Tester/summary details Chromium in Gentoo project needs more people testing packages. We are not always able to reproduce reported issues, and having more people respond to testing requests would be useful. No quiz is necessary to start. /details requirements If you are running www-client/chromium or chromium-bin, and are willing to spend some time helping Gentoo, feel free to apply. /requirements contactal...@g.o/contact /job /recruitment signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] RFC Bugzilla interaction guide for devs editbugs users
On Tue, 7 Sep 2010 21:30:34 + Robin H. Johnson robb...@gentoo.org wrote: On Tue, Sep 07, 2010 at 10:47:27PM +0200, Róbert Čerňanský wrote: 2.3. Upstream issues Do not close a bug (as RESOLVED/UPSTREAM) until it is fixed by upstream. If the reason you propose this is visibility, then maybe we should make the quicksearch option include more than just open bugs. I've thought about having UPSTREAM/DUPLICATE/INVALID added so that bugzilla users can more easily discover whether a bug was already reported and was deemed fixed, a duplicate of another bug or canonically invalid. This implies that the upstream is alive enough to fix it. I feel it should mean that the bug has been reported to upstream, and that state is documented in the bug. If we keep every upstream bug open instead of closed, we'd have probably another 2500 open bugs (5312 RESO/UPSTREAM in the history of Gentoo, and I'm ballparking that 50% aren't actually fixed yet upstream). Quoting [1]: UPSTREAM It is not suitable to deal with the bug at this level, and the bug should be taken to the upstream developers for resolution. It all depends on the kind of bug. Requests for new features should probably normally go upstream (including the kind where a patch is available). That's out of our scope. With the above proposal, feature request bugs like bug #171277 [2] might not go unnoticed as easily. In the case of app-misc/screen, upstream did seem dead for a couple of years, and even now after many new features were added (including vertical split) and bug fixes were included there, there is still no new version out. I guess that bug is still not marked UPSTREAM just to aid in its visibility - after the bug was reopened, no more duplicates were filed. jer [1] https://bugs.gentoo.org/page.cgi?id=fields.html#resolution [2] https://bugs.gentoo.org/show_bug.cgi?id=171277
Re: [gentoo-dev] CUPS 1.4 and FFMpeg 0.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dne 9.9.2010 15:25, Timo Gurr napsal(a): The plan is to release an updated revision incorporating the QA fixes from bug #332591 (huge thanks to Tomáš Chvátal (scarabeus) for doing the actual work here!) Apart from that there's no real showstopper blocking a stabilization of CUPS 1.4. The printing guide could need an update though, I've already started working on it but my time is limited. Regarding stabilization we can't respect printer drivers which are not in the official tree since the few ones which are in are already hard to maintain with our low manpower, see foo2zjs for example (hplip is in a great shape thanks to the massive work of Daniel Pielmeier (billie) and gutenprint should be fine, too). As a general rule for upgrading to cups 1.4 when something regarding local usb printers doesn't work: 1. disable kernel usblp: CONFIG_USB_PRINTER=n 2. delete /etc/cups 3. (re-)install cups 1.4 with USE=usb 4. configure printer(s) from scratch via the cups webinterface 5. if your printer is a multifunction device, be sure you got the udev rules setting the device permissions in shape so cups can access the device If for whatever reason (broken/old printer drivers) that doesn't work out there's still the way to install CUPS 1.4 with USE=-usb to get the old CUPS 1.3 behaviour back. The printing team is suffering low manpower. We also have a bunch of open bugs which are probably invalid and caused by not following the upgrade path, broken drivers, or plain misconfiguration, but you can't close them without investigation to not upset our users. Not responding is quite as bad, but as I said above, this is due to lack of time. Regards Timo Gurr (tgurr) Since you guys again talk about stabling something, i added -r1 again. This time with really trimmed patches that fixes only build time issues or some issue i experienced localy. Feel free to rework that patches before stabling it :) Cheers Tomas -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyKwSAACgkQHB6c3gNBRYd2TgCeL+fxqR+gWXrQRILcwEJ2Cx3b cGIAn14As57qvq5l0T1qJ3xu/d6OfAUE =4F3p -END PGP SIGNATURE-
