From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2007-12-14 23:11:51
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | don't know | Ver: 0.10.14 Summary: kill the gstreamer registry file Product: GStreamer Version: 0.10.14 Platform: Other OS/Version: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: don't know AssignedTo: gst...@li... ReportedBy: nek...@gm... QAContact: gst...@li... GNOME version: 2.19/2.20 GNOME milestone: Unspecified Please describe the problem: ~/.gstreamer-0.10/registry.i486.xml (autogenerated whenever I start a gstreamer app such as totem) corrupts itself way too easily *and* does not seem to provide any function at all, at least none that I can think of as an user. Steps to reproduce: I don't know. Actual results: Corrupt registry prevents the picture from being shown in video files. This is with files that totem has no problems playing in normal circumstances. Removing that file and restarting totem allows the video to be played back instantaneously without problems. Removing that file *and* preventing it from being created (using restrictive permissions) does not even cause problems, totem still plays the same video after a restart! This is the proof to me that this file must be useless. It has been over 25 times that I had to delete it on various computers that "wouldn't play videos that used to play before". I can't make people enthusiastic about the gstreamer technology if I have to tell them to clear some crazy, obscure hidden registry file every once in a while! Expected results: Do not ever create that file! Does this happen every time? happens once every few weeks/months Other information: The power user fix is this: rm ~/.gstreamer-0.10/registry* chmod ugo -w ~/.gstreamer-0.10/ -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2007-12-14 23:24:06
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | don't know | Ver: 0.10.14 ------- Comment #1 from Jeff Fortin 2007-12-14 23:24 UTC ------- Second command should read: chmod ugo-w ~/.gstreamer-0.10/ Sorry for the typo. -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2007-12-14 23:46:01
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | don't know | Ver: 0.10.14 ------- Comment #2 from David Schleef 2007-12-14 23:46 UTC ------- What makes your setup different from the the many users that don't have this problem? Do you mount your home directory over NFS? -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2007-12-15 01:15:29
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | don't know | Ver: 0.10.14 Jan Schmidt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |th...@ma... ------- Comment #3 from Jan Schmidt 2007-12-15 01:15 UTC ------- Yes, GStreamer will still work fine if it can't write the registry file, but it means that all the plugin shared libraries have to be scanned on startup, because the cached information is missing. This will make startup of your applications slower (a *lot* slower if there are many plugins), and waste memory loading information that isn't needed. -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2007-12-15 23:21:25
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | don't know | Ver: 0.10.14 Tim-Philipp Müller changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |t....@ze... Status|UNCONFIRMED |NEEDINFO -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2007-12-16 00:18:18
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | don't know | Ver: 0.10.14 Jeff Fortin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |UNCONFIRMED ------- Comment #4 from Jeff Fortin 2007-12-16 00:18 UTC ------- Nope, just standard ubuntu installations on regular local ext3 partitions. Mind you this is not just me: I had to "fix" this on my two computers regularly, and on two friends' computers which I had nothing to do with in daily use (anyway, they are using different ubuntu releases, so not an ubuntu problem I would expect). The "lot more people" argument is difficult to evaluate: maybe I'm the only human out there that noticed that registry file and the fact that clearing it solves problems. Other users would (or already did) thik "meh, totem/gst sucks" and install VLC, never to touch totem/gst again. Lot slower you say? I have all the plugins (good/bad/ugly, with multiverse variants, with w32codecs and gst pitfdll) I can get my paws on, here is my stopwatch benchmarks launching totem: - without write access to the gst folder (no registry): 2 seconds 30 - with write access and no existing registry: 1 second 90 - with write access and existing registry: 1 second 70 (cold boots between each trials) Warm startup time of 1 second 55. My machine: 1.8 ghz pentium M, 768 mb of DDR ram, 5400 rpm IDE hard drive. Ubuntu 7.10 (which is known for being slower than previous releases). My conclusions from those rough benchmarks: - the launch times are very low no matter what you do - I don't even know if those numbers are "statistically significative" - don't forget they have limited precision as I need to physically start and stop my wristwatch. I did run each trial a few times (lots of reboots), and you can easily get an error margin of half a second or worse! - do we really care about a variance of rougly 40% of a second on the cold launch of an app like totem? Wouldn't benefits of not having that registry offset gaining 400 ms of cold startup time? -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2007-12-16 00:48:07
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | don't know | Ver: 0.10.14 David Schleef changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO ------- Comment #5 from David Schleef 2007-12-16 00:43 UTC ------- Please attach a copy of the broken registry.*.xml file. -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2007-12-16 11:46:26
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | Ver: 0.10.14 Tim-Philipp Müller changed: What |Removed |Added ---------------------------------------------------------------------------- Component|don't know |gstreamer (core) -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2007-12-16 15:48:07
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | Ver: 0.10.14 ------- Comment #6 from Jeff Fortin 2007-12-16 15:48 UTC ------- I was dumb enough to delete it days before I reported this bug, so until it happens again I cannot provide it. I'm curious though, how is such a registry file supposed to handle cases where the user installs or removes codecs? If it can still detect that (I don't know if it does), how is it different than not having a registry at all? -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2007-12-16 16:07:48
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | Ver: 0.10.14 Jeff Fortin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |UNCONFIRMED ------- Comment #7 from Jeff Fortin 2007-12-16 16:07 UTC ------- Ok, this tickled me, so I went googlin' and I found these "proofs" that I am certainly not the only one who has noticed this problem and found the culprit being the registry: http://ubuntuforums.org/archive/index.php/t-348987.html "Might be a bit of a long shot, but it might help if you delete your gstreamer registry (it regenerates itself automatically once you use gstreamer again)" https://lists.ubuntu.com/archives/ubuntu-users/2006-September/094501.html (I think the registry is mentionned somewhere down that thread) http://ubuntuforums.org/showpost.php?p=1139960&postcount=2 (notice how he clearly put rm -f ~/.gstreamer-0.10/registry.i486.xml in the "installation" process!) http://ubuntuforums.org/showpost.php?p=3662184&postcount=7 "another thing to look for is corruption of the $HOME/.gstreamer-0.10/registry.i486.xml database. It has happened to me more times I care to remember that a problem with gstreamer was solved by deleting that file" So I would tend to reopen that bug report as, I think, the solution is to not have a registry at all (unless you can show me benchmarks that it really makes a huge performance difference, not just 0.4 seconds) -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2007-12-16 20:08:10
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | Ver: 0.10.14 Tim-Philipp Müller changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED Summary|kill the gstreamer registry |broken registry files |file |written to disk Target Milestone|HEAD |0.10.16 ------- Comment #8 from Tim-Philipp Müller 2007-12-16 20:08 UTC ------- Rest assured that we wouldn't bother with the registry if there wasn't a reason for having it. It's good of you to enquire about or investigate the purpose of it all though before declaring it useless. Yes, earlier versions of GStreamer-0.10 indeed had a bunch of issues related to registry reading and writing (mind you, at least one of those reports refers to ubuntu dapper, which is ancient). Those should be fixed these days though, and neither our build bots nor any users have reported any mysterious-possibly-registry-related-failures for a long time. However, I did have a look at the code and spotted a problem that may cause partial/broken registry files: we don't check the return value of close() when writing the file, yet sometimes write problems such as out-of-diskspace are only reported when the file is closed rather than during the write. I've fixed this in CVS: 2007-12-16 Tim-Philipp Müller <tim at centricular dot net> * gst/gstregistrybinary.c: (gst_registry_binary_write_cache): Use g_remove() and g_rename(). Check result of g_rename(), and don't leak the open file descriptor if we error out when writing. * gst/gstregistryxml.c: (load_plugin), (gst_registry_xml_write_cache): Must check the return value of close() after writing out the new registry file. Sometimes write problems such as out-of-diskspace are only reported when the file is closed and not already during the write. This may have caused partial/broken registry files in some rare circumstances. Should fix #503675. I hope this will fix it for you. If not, we probably need more information to go on. If you ever do run into this problem again, please do keep the registry file so we can have a look a it. Thanks! Lastly, there is one known problem with the registry and that is plugins wrapping other plugins (such as pitfdll [don't use that btw, it's highly unstable] or our libvisual plugin). If wrapped plugins are added or removed (e.g win32codecs changes), GStreamer doesn't know about this and doesn't update the registry. This should in the worst case result in error messages at run-time though, but not in 'codecs disappearing' without a reason. Bug #350477 is about this, and it should be harmless if things are packaged correctly. And of course the registry is updated in the normal case of codecs being updated, added or removed (e.g. files in /usr/lib/gstreamer-0.10 added/removed/changed). -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2007-12-16 23:52:46
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | Ver: 0.10.14 ------- Comment #9 from Jeff Fortin 2007-12-16 23:52 UTC ------- ok, thank you for your thorough explanation. I hope the problem you stumbled upon was the cause of all this (if not, I will try to remember keeping the registry next time). I don't remember having my hard disks full in a long time though, is gstreamer 0.10.14 considered so "old"? -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2009-08-02 18:26:02
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | Ver: 0.10.14 Jean-François Fortin Tam changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|FIXED | ------- Comment #10 from Jean-François Fortin Tam 2009-08-02 18:25 UTC ------- This happened again today with latest stuff from the gstreamer developers PPA for ubuntu. -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2009-08-02 18:26:07
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | Ver: 0.10.26 Jean-François Fortin Tam changed: What |Removed |Added ---------------------------------------------------------------------------- GNOME version|2.19/2.20 |2.25/2.26 Version|0.10.14 |0.10.26 -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2009-08-02 18:27:03
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | Ver: 0.10.26 ------- Comment #11 from Jean-François Fortin Tam 2009-08-02 18:26 UTC ------- Created an attachment (id=139746) --> (http://bugzilla.gnome.org/attachment.cgi?id=139746&action=view) samples of the registry The corrupt version prevented me from playing h264 and flv files. -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2009-08-02 19:55:50
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | Ver: 0.10.26 ------- Comment #12 from Tim-Philipp Müller 2009-08-02 19:55 UTC ------- The file looks ok at first glance. All the ffmpeg data is in the middle and not at the end, and I seem to be able to read the file just fine current git (ie. the latest core prerelease roughly): $ GST_REGISTRY=/home/tpm/tmp/broken-gst-registry/registry\ \(corrupt\).i486.bin gst-inspect-0.10 --gst-disable-registry-update | grep ffdec_h264 ffmpeg: ffdec_h264: FFMPEG H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 decoder No warnings or errors while reading in the file, and valgrind shows no problems either. So I'm tempted to say the registry file is probably alright. -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503675. |
From: GStreamer (bugzilla.gnome.o. <bug...@gn...> - 2009-11-07 22:52:00
|
https://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | 0.10.26 --- Comment #13 from David Schleef <ds...@sc...> 2009-11-07 22:51:43 UTC --- Indeed. These files appear to be identical except for ordering. If there is a bug here, it is not related to the registry. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
From: GStreamer (bugzilla.gnome.o. <bug...@gn...> - 2009-12-07 04:59:43
|
https://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | 0.10.26 --- Comment #14 from Jean-François Fortin Tam <nek...@gm...> 2009-12-06 15:42:19 UTC --- I had yet another occurence of this problem today on my netbook. I installed all the possible codecs (good, bad, ugly, gst-ffmpeg and ffmpeg itself) and still couldn't play H.264 files. I then saved a copy of my gstreamer registry (I put it under version control!) and cleared it out. The registry was recreated and everything worked fine. Will attach my samples of "broken" registry and working registry. It irks me that the registry has to be cleared periodically for the darn thing to work. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
From: GStreamer (bugzilla.gnome.o. <bug...@gn...> - 2009-12-07 05:02:04
|
https://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | 0.10.26 --- Comment #15 from Jean-François Fortin Tam <nek...@gm...> 2009-12-06 15:44:48 UTC --- Created an attachment (id=149200) --> (https://bugzilla.gnome.org/attachment.cgi?id=149200) samples of the registry 2 -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
From: GStreamer (bugzilla.gnome.o. <bug...@gn...> - 2009-12-07 05:05:05
|
https://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | 0.10.26 --- Comment #16 from Jean-François Fortin Tam <nek...@gm...> 2009-12-06 15:47:45 UTC --- Here's a question. Let's say you put those registry files in your .gstreamer-0.10 folder, and they prevent you from playing back H.264 and the like. Shouldn't those files be automatically overwritten by a clean and uncorrupt registry by gstreamer? How can they just sit there on my disk and require deletion, rather than update themselves? Also, maybe it doesn't update when you install gst-ffmpeg and ffmpeg? -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
From: GStreamer (bugzilla.gnome.o. <bug...@gn...> - 2009-12-30 20:12:40
|
https://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | 0.10.26 Stefan Kost (gstreamer, gtkdoc dev) <ensonic> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |en...@so... --- Comment #17 from Stefan Kost (gstreamer, gtkdoc dev) <en...@so...> 2009-12-30 20:12:19 UTC --- You have the registry cache under version control? Thats not a good idea. This is a cache and it is autogenerated/autoupdated as needed. The update is triggered by changes in the plugin files (new or removed ones) as well as timestamp changes. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
From: GStreamer (bugzilla.gnome.o. <bug...@gn...> - 2009-12-31 15:44:57
|
https://bugzilla.gnome.org/show_bug.cgi?id=503675 GStreamer | gstreamer (core) | 0.10.26 --- Comment #18 from Jean-François Fortin Tam <nek...@gm...> 2009-12-31 15:44:36 UTC --- Yes, it's under version control (bazaar to be exact), but it's just an added tool. It doesn't block the registry from auto updating or anything. The only thing I do with it is "bzr commit" when I noticed that the registry changed to something significant (ex: nonworking state) and then commit again when I reset the registry file. It acts more like a snapshot/time machine system. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |