| Summary: | Stabilization request for app-cdr/k3b-1.0.4 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Rodrigo Oliveira <rodrigo.dealer> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | devel, jakub, juantxorena, StormByte, znmeb |
| Priority: | High | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 171493, 188489, 201497 | ||
| Bug Blocks: | |||
|
Description
Rodrigo Oliveira
2007-06-05 01:38:08 UTC
I've only recently added -r1 (from the ChangeLog): *k3b-1.0.1-r1 (26 May 2007) Thus, this has to wait about 30 days and if we get no bug reports we can *then* stabilise it. I'm leaving this request open and have marked June, 27th as its review date on my task list. Thanks for your help! 1.0.2 is out; please bump to this instead. Also, I have had a nasty bug with ~k3b-1.0.1 where verify of DVD write hangs indefinitely. Timothy, while I appreciate that you let us know about the new version, please don't abuse stabilisation request bugs for requesting version bumps. Next time, please just file a new bug. 1.0.1 is working just fine for me, btw. Thus, I'll keep this open until it's time for stabilisation. I'm going to bump k3b later today. Arches, could you please stabilise this? Thanks! No way right now. Please check the tree and bugzilla, before asking arch teams for stabilization. Carlo, I did and I found a *dead* application with an appropriate dependency on <app-cdr/k3b-1.0. I tried compiling konqburn and got even *new* errors. I consider stabilising a 1.x version of k3b for the *first* time on Gentoo more important than waiting for a miraculous resurrection of konqburn. hydrogen is not interested in konqburn anymore either, btw: [2007-06-25 20:42] <Philantrop> hydrogen: Would I be right to assume that you're the hydrogen who was looking into bug 171493? :-) [2007-06-25 20:42] <jeeves> [...] [2007-06-25 20:43] <hydrogen> yea [2007-06-25 20:43] <hydrogen> a long time ago [2007-06-25 20:44] <hydrogen> that is to say: i havn't done anything with it [2007-06-25 20:45] <Philantrop> hydrogen: No problem. Do you intend to do anything with it? It seems abandoned. [2007-06-25 20:45] <hydrogen> not really I'd add a few more thoughts currently crossing my mind but I promised to respect and honour the CoC... :-> Now that bug 171493 is solved and konqburn is hardmasked, we should stabilize this. Arches, could you please stabilise? --- amd64 --- app-cdr/k3b-1.0.2 - USE: alsa css dvdr dvdread encode ffmpeg flac hal kde mp3 -musepack -musicbrainz -sndfile -vcd vorbis -emovix -linguas_af -linguas_ar -linguas_bg -linguas_br -linguas_bs -linguas_ca -linguas_cs -linguas_cy -linguas_da -linguas_de -linguas_el -linguas_en_GB -linguas_es -linguas_et -linguas_eu -linguas_fa -linguas_fi -linguas_fr -linguas_ga -linguas_gl -linguas_he -linguas_hi -linguas_hu -linguas_is -linguas_it -linguas_ja -linguas_ka -linguas_lt -linguas_mk -linguas_ms -linguas_nb -linguas_nds -linguas_nl -linguas_nn -linguas_pa -linguas_pl -linguas_pt -linguas_pt_BR -linguas_ru -linguas_rw -linguas_se -linguas_sk -linguas_sr -linguas_sr@Latn linguas_sv -linguas_ta -linguas_tr -linguas_uk -linguas_uz -linguas_zh_CN -linguas_zh_TW -debug xinerama -elibc_FreeBSD arts 1: emerges 2: passes collision-protect, (multilib-)strict, test 3: works (basic DVD writing tested) Portage 2.1.2.7 (default-linux/amd64/2007.0/desktop, gcc-4.1.2, glibc-2.5-r3, 2.6.20-gentoo-r8 x86_64) ================================================================= System uname: 2.6.20-gentoo-r8 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ Gentoo Base System release 1.12.9 Timestamp of tree: Fri, 29 Jun 2007 04:00:01 +0000 ccache version 2.4 [enabled] dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r7 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -ggdb -march=athlon64 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/init.d /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O2 -ggdb -march=athlon64 -pipe" DISTDIR="/tmp/portage" FEATURES="ccache collision-protect distlocks metadata-transfer multilib-strict parallel-fetch sandbox sfperms splitdebug strict test" GENTOO_MIRRORS="http://ds.thn.htu.se/linux/gentoo http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://mirror.switch.ch/mirror/gentoo/ http://trumpetti.atm.tut.fi/gentoo/" LANG="en_US.utf-8" LINGUAS="en sv" MAKEOPTS="-j4" PKGDIR="/tmp/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/private" SYNC="rsync://dx/gentoo-portage" USE="3dnow 3dnowext X a52 aac acpi aiglx alsa amd64 arts asf avi bash-completion berkdb bitmap-fonts branding browserplugin cairo ccache cdr cli cpudetection cracklib crypt cscope css cups cvs dbus divx divx4linux dlloader dri dvd dvdr dvdread eds emboss encode esd evo fam ffmpeg firefox flac foomaticdb fortran freetype gdbm geoip gif gimp gmedia gnokii gnome gpm gstreamer gtk hal http iconv ieee1394 imap imlib ipv6 isdnlog java javascript jfs jpeg kde kdeenablefinal kdehiddenvisibility kdepim kerberos libg++ logitech-mouse mad madwifi maildir midi mikmod mmx mmx2 mmxext mono mozbranding moznopango mozsvg mp3 mpeg mplayer msn mudflap ncurses nls nptl nptlonly nsplugin ntfs nvidia obex ogg oggvorbis opengl openmp oss pam pcre pdf pdflib perl png pppd python qt qt3 qt3support qt4 quicktime readline realmedia reflection reiserfs samba scanner sdl session spell spl sse sse2 ssl subversion svg symlink tcpd test tetex theora threads tiff truetype truetype-fonts type1-fonts udev unicode usb v4l v4l2 vim-syntax vim-with-x visualization vorbis wifi wmf wmp wxwindows xcomposite xface xfs xine xinerama xml xorg xosd xpm xprint xv xvid zlib" ALSA_CARDS="emu10k1" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="mouse keyboard evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en sv" USERLAND="GNU" VIDEO_CARDS="nv nvidia" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS (In reply to comment #2) > 1.0.2 is out; please bump to this instead. Should we stabilise this version or the one in the summary (“Stabilization request for app-cdr/k3b-1.0.1-r1”)? The one in the summary, please, namely 1.0.1-r1 which is working fine whereas 1.0.2 has some issues. k3b >=1.0 needs media-video/emovix stable before. You should ask the video-herd for stabilisation first. Probably you want to remove arches as long as no bug stabilisation-bug for emovix exists. Thanks, pylon. I should really take a short break... According bug 70313, the emovix version in portage is unsupported by upstream. A "new" version, 0.9, is available since 2004, and the bump request is still unsolved (even when it uses the same ebuild). That bug should be added as a dependency of this one IMHO. The updated package was added 8 July. So we will need to wait until at least 8 August to stabilise if the maintainer is willing to stabilise at that point and no blockers have cropped up. (In reply to comment #2) > 1.0.2 is out; please bump to this instead. > > Also, I have had a nasty bug with ~k3b-1.0.1 where verify of DVD write hangs > indefinitely. > I'm having problems burning DVDs with k3b 1.0.2. If I can isolate the problem, I'll file a bug against it, but what is happening (on two different burners and machines) is that it finishes writing the DVD, ejects it, and then can't seem to reload it, and the verify croaks because there isn't a DVD to verify. I haven't tested this with CDs. I pretty much have to have k3b -- nothing else I've found in Portage will burn a DVD and then verify it. (In reply to comment #16) > I'm having problems burning DVDs with k3b 1.0.2. If I can isolate the problem, > I'll file a bug against it, but what is happening (on two different burners and > machines) is that it finishes writing the DVD, ejects it, and then can't seem > to reload it, and the verify croaks because there isn't a DVD to verify. I > haven't tested this with CDs. I pretty much have to have k3b -- nothing else > I've found in Portage will burn a DVD and then verify it. Same as me. Affects 1.0.1 and 1.0.2. Please file new bug or post to k3b mailing list, rather than continue in this bug. Workaround is to set preferences to not eject/reload disk before verify. Then 1.0.2 works fine for me. Don't know about 1.0.1. :-) yep ... filed as bug 186173. Glad to hear there's a workaround. At last, emovix is stable in amd64 and x86. Since k3b-1.0.2 is in portage for more than a month and it hasn't got any regressions, I suggest that it can be stabilized instead 1.0.1-r1. Before this, ppc must stabilize media-video/emovix-0.9.0, which is in portage for a month and hasn't got any open bugs. Any news on this? Hi all. Are there any bugs not resolved, which blocks k3b 1.0.x stabilization? Well, can we move on with this finally? There won't be any fixed going to 0.12.17 upstream, don't see what's the point of getting stuck at that version. It seems thatk3b-1* versions have some regressions (bug #186173 and bug #189128). However, I have been unable to find any reference to this problems anywhere on the internet, maybe they aren't k3b related. Also, there is a bug that must be fixed before (bug #188489), and media-video/emovix-0.9.0 should be stabilized in ppc. This is getting ridiculous. The two "blocking" bugs are ignored, nobody knows if is k3b-related, kernel-related, hardware-related, growisofs.related or whatever. Even the few people affected by the bugs ignore them (few because nobody talks about them, neither in gentoo forums nor in any forums, mailing list or anything I have searched for). k3b is one of the most used programs in linux, version 1.x is nearly 9 months old and it comes with a lot of features, bugfixes and imporvements. I vote for stabilization of the last version, 1.0.4, which has been in portage +30 days. However, bug #199197 must be fixed before, but it seems trivial (I hope so). Also, ppc and ppc64 arch must stabilize media-video/emovix-0.9.0 along with k3b (no open bugs and +30 days in portage). Possible target archs: amd64 ppc (+media-video/emovix-0.9.0) ppc64 (+media-video/emovix-0.9.0) x86 Please, do it already. There's one k3b bug left related to eject which noone has any clue about, can easily be worked around by disabling the feature and should be reported upstream. Current 'stable' k3b is dead and buggy bitrot incompatible with cdrkit that noone will ever fix. (In reply to comment #25) > Please, do it already. There's one k3b bug left related to eject which noone > has any clue about, can easily be worked around by disabling the feature and > should be reported upstream. > > Current 'stable' k3b is dead and buggy bitrot incompatible with cdrkit that > noone will ever fix. > I'm not a dev, I can't add arches to CC list. (In reply to comment #26) > I'm not a dev, I can't add arches to CC list. Then ignore comments that haven't been intended for you anyway... :=) (In reply to comment #25) > Please, do it already. Yes, Jakub, I'm going to ask video later today to get emovix stabilised and once that's done, I'll add the arches here. Any news on this? In bug #186173 comment #12 there is a link to the kde bug system where there is a patch to fix that bug. Since emovix is stable where needed, a k3b-1.0.4-r1 version with the aformentioned patch could be stabilized without waiting another 30 days IMHO: is an upstream patch, and we have waited enough n*(30 days). (In reply to comment #30) > In bug #186173 comment #12 there is a link to the kde bug system where there is > a patch to fix that bug. Since emovix is stable where needed, a k3b-1.0.4-r1 > version with the aformentioned patch could be stabilized without waiting > another 30 days IMHO: is an upstream patch, and we have waited enough n*(30 > days). > That patch has not been approved by its author nor has it been committed to k3b trunk. Actually the patch is a revert of a long-standing bugfix for the "DMA disabled"-bug. I don't think we should add this patch before it's committed to k3b SVN. On the other hand, =app-cdr/k3b-1.0.4 fixes numerous bugs since the last stable version, so bug 186173 should not stop this from going stable, I think. Exactly what I think. Arches, please do your job. x86 stable amd64 stable ppc stable ppc64 done |
