Issue #22529 has been updated by Lauri Tirkkonen.

I did a bisect:

    root@test-precise:~/src/puppet# git bisect start
    HEAD is now at b983664... (packaging) Update PUPPETVERSION for 3.3.0
    root@test-precise:~/src/puppet# git bisect bad
    root@test-precise:~/src/puppet# git bisect good 3.2.4
    Bisecting: 394 revisions left to test after this (roughly 9 steps)
    [c96e0a90275539a69a0dab945ea32e0ea9175456] Merge pull request #1767 from 
dalen/moduletool_dependency_attrs
    root@test-precise:~/src/puppet# git bisect run ./test.sh
    running ./test.sh
    Bisecting: 198 revisions left to test after this (roughly 8 steps)
    [a33ec84a241282a0ae9fe025c0ec9c0bd878fb57] Merge branch 
'maint/agent-logger-specs-on-windows'
    running ./test.sh
    Bisecting: 97 revisions left to test after this (roughly 7 steps)
    [d21da80fada545469b1a0eb2dc8568dea2df1105] Merge branch 'pull-1648'
    running ./test.sh
    Bisecting: 49 revisions left to test after this (roughly 6 steps)
    [6c34ed645695a2bbe48fab9616af4dd3a8081b4a] Merge branch 
'20383-duplicate_resource_error_location'
    running ./test.sh
    Bisecting: 24 revisions left to test after this (roughly 5 steps)
    [325b8bfad69f48d04059ecf3478b56950433933c] Merge pull request #1635 from 
hlindberg/issues/fix-20581
    running ./test.sh
    Bisecting: 12 revisions left to test after this (roughly 4 steps)
    [241c2e14c66de44173554ab4f9b2219c5a79334e] Merge branch 
'maint-stub_aptitude_dpkgquery'
    running ./test.sh
    Bisecting: 5 revisions left to test after this (roughly 3 steps)
    [9aa9d699921f9760eb8154e034cdeb48e8a7503b] Merge pull request #1636 from 
adrienthebo/maint-readme_developer_explain_side_effects_in_tests
    running ./test.sh
    Bisecting: 2 revisions left to test after this (roughly 2 steps)
    [e96ac6b6abb9f387e9b8cd097b024aaa4bc656ee] (#19875) Package descriptions 
obtained by rpm/dpkg providers
    running ./test.sh
    Bisecting: 0 revisions left to test after this (roughly 1 step)
    [f5bd40571c1a587382b9d70ca028bb1269aa5946] Merge branch 'stable'
    running ./test.sh
    e96ac6b6abb9f387e9b8cd097b024aaa4bc656ee is the first bad commit
    commit e96ac6b6abb9f387e9b8cd097b024aaa4bc656ee
    Author: Josh Partlow <[email protected]>
    Date:   Tue Apr 30 19:02:04 2013 -0700

        (#19875) Package descriptions obtained by rpm/dpkg providers
        
        Previously Puppet::Provider::Package::Rpm and Dpkg implementations
        obtained package information from the system without capturing package
        description information.
        
        This change modifies the rpm and dpkg-query format strings to include
        descriptions.  This can be used for querying package state on a node.
        
        The rpm implementation is a simple change relying on a SUMMARY field
        which is a single line and which does not change the one line per
        package parsing structure in the Rpm class.
        
        The dpkg implementation is a more complicated change because we are
        using a DESCRIPTION field in dpkg-query's format string, which is a
        multi-line value.  The first line is a summary, and is all we want, but
        dpkg-query then print's x additional lines of long description.  A new
        parse_multi_line method has been added to treat these multi-line results
        as a single entry, grab the first line with summary and ignore the
        excess lines without triggering warnings.  Completely invalid package
        entry results should still trigger warnings.
        
        Current dpkg-query versions (as of 1.16.2 from 2012, I believe) have a
        binary:Summary field which would return this to a single line parse and
        make it simpler and less error prone again.  But earlier Debian/Ubuntu
        installations don't have this (Ubuntu 12.04 for instance).
        
        Dpkg.instance, Dpkg#query both used a Dpkg.dpkgquery_piped to expose an
        IO pipe for parsing.  Regex match used in Rpm to ensure we only consume
        good query output lines.

    :040000 040000 000a7fa17c4459b7f8a2e1d9af8af566292668fe 
44b57bc5b432ca95683c78cfa0a5d214b2370957 M      lib
    :040000 040000 9fcc6bba7d30aaa5db3cc2df2bdaac7c14aeabde 
05373870ce621439aaf4f803e34879f4c61dd710 M      spec
    bisect run success
    root@test-precise:~/src/puppet# git checkout e96ac6
    Previous HEAD position was f5bd405... Merge branch 'stable'
    HEAD is now at e96ac6b... (#19875) Package descriptions obtained by 
rpm/dpkg providers



----------------------------------------
Bug #22529: apt package ensure absent/purged causes warnings on 3.3.0
https://projects.puppetlabs.com/issues/22529#change-97478

* Author: Lauri Tirkkonen
* Status: Unreviewed
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* Affected Puppet version: 3.3.0
* Keywords: 
* Branch: 
----------------------------------------
Since upgrading to 3.3.0 my Ubuntu agents are reporting new warnings on every 
run. This does not happen on 3.2.4 so this is a regression.

    # puppet apply -e "package {'deja-dup': ensure => purged }" 
    Notice: Compiled catalog for test-precise.niksula.hut.fi in environment 
production in 0.10 seconds
    Warning: Failed to match dpkg-query line "No packages found matching 
deja-dup.\n"
    Notice: Finished catalog run in 0.32 seconds


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to