Bug 813231

Summary: btrfsprogs are out of date
Product: [openSUSE] openSUSE 12.3 Reporter: Jon Nelson <jnelson-suse>
Component: OtherAssignee: David Sterba <dsterba>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: forgotten_Si7ddX0wxG, hartrumpf, meissner
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 12.3   
Whiteboard: GOLD
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Jon Nelson 2013-04-03 15:56:21 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0

the btrfs programs are pretty out of date.
I request a re-pull and re-build.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Comment 1 David Sterba 2013-07-04 15:20:37 UTC 
Submitted to 12.2 and 12.3
Comment 2 Marcus Meissner 2013-07-05 12:54:18 UTC 
the opensuse review team wants to have the patchfilenames that were added or removed excplicitly listed in the .changes entry.

if you could do that for both Maintenance ahnd Factory?
Comment 3 David Sterba 2013-07-08 12:58:05 UTC 
Most of the package-local patches removed were subsequently merged or obsoleted upstream. There are like ~330 new patches merged on top of the latest release tag 0.20-rc1 -- do you mean to add them as a separate files instead of folding into the tar file?

A changelog entry for 300+ changes would be pretty long even if I describe only the visible changes, I'm afraid there will be probably nobody else besides the reviewers' team reading it. The code itself is tested and in wide use.

Do you see a way to lessen the amount of work spent on describing the changes?
Comment 4 Benjamin Brunner 2013-07-08 13:12:19 UTC 
In my opinion, it would be ok to add a comment to the changes-file like "removed patches which are included upstream" or something like that. Usually, the review-team accepts it too. 

Marcus, you are ok with that?
Comment 5 Marcus Meissner 2013-07-08 13:17:52 UTC 
two things:

The review team wants to know the patches that were removed, not their content.

So just a list of the patchfilenames and a single "merged upstream" or so
is sufficient. 

Second:
As for details of the change, a 2 - 4 highlevel change entries, like e.g.
"new important user visible feature xxxx" and "lots of bugs fixed".
Comment 6 Forgotten User Si7ddX0wxG 2013-10-03 06:28:47 UTC 
Hello,
Found following --Glenn
-sources
https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories


# git clone git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
Cloning into 'linux-btrfs'...
remote: Counting objects: 3168931, done.
remote: Compressing objects: 100% (483967/483967), done.

also log entries at:
http://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git/FETCH_HEAD

.
.
.
tag 'v3.1-rc8' of git://gitolite.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs 
tag 'v3.1-rc9' of git://gitolite.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs
Comment 7 David Sterba 2013-11-26 18:29:37 UTC 
12.3 update submitted (request 208582)
Comment 8 David Sterba 2013-11-26 18:29:58 UTC 
Closing.
Comment 9 Swamp Workflow Management 2013-12-04 12:05:54 UTC 
openSUSE-RU-2013:1816-1: An update that has three recommended fixes can now be installed.

Category: recommended (moderate)
Bug References: 727383,750185,813231
CVE References: 
Sources used:
openSUSE 12.3 (src):    btrfsprogs-3.12-49.4.1