Modify

Ticket #1066 (closed defect: wontfix)

Opened 10 years ago

Last modified 6 years ago

bcfg2 insists on updating held packages

Reported by: https://www.google.com/accounts/o8/id?id=AItOawkPb0RtPyicSdU7pLcv1UrX-yCh-YjkOwU Owned by: desai
Priority: major Milestone: Bcfg2 1.4.0 Release
Component: bcfg2-client Version: 1.0
Keywords: Cc:

Description

Some packages are put on hold on my system, but when I run:

bcfg2 -q -v -n

it still shows message In dryrun mode: suppressing entry installation for:

Attachments

Change History

comment:1 Changed 10 years ago by solj

If you are using Packages, then this will be a problem with the client side. You can check by trying to aptitude dist-upgrade on the client which would also want to upgrade the packages in question.

If you are using Pkgmgr, you can specify explicitly the version you want.

comment:2 follow-up: ↓ 3 Changed 10 years ago by https://www.google.com/accounts/o8/id?id=AItOawkPb0RtPyicSdU7pLcv1UrX-yCh-YjkOwU

I am using Packages. Why should I use aptitude dist-upgrade? I don't want to upgrade distribution - it not related IMO. aptitude upgrade doesn't propose to upgrade package in question, because it is put on hold explicitly.

comment:3 in reply to: ↑ 2 Changed 10 years ago by solj

Replying to https://www.google.com/accounts/o8/id?id=AItOawkPb0RtPyicSdU7pLcv1UrX-yCh-YjkOwU:

I am using Packages. Why should I use aptitude dist-upgrade? I don't want to upgrade distribution - it not related IMO. aptitude upgrade doesn't propose to upgrade package in question, because it is put on hold explicitly.

I can't reproduce this. You'll need to provide more information. If you cache the client configuration bcfg2 -qnc cached.xml, you will see that Packages doesn't send any particular version to be installed. The client only sees version='auto'. Therefore, either the client wants to reinstall these packages for some other reason, or the client's apt is trying to do the upgrade.

comment:4 follow-up: ↓ 5 Changed 10 years ago by https://www.google.com/accounts/o8/id?id=AItOawkPb0RtPyicSdU7pLcv1UrX-yCh-YjkOwU

I see. I am using aptitude and it's strange.

$ sudo aptitude upgrade   
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
                                         

However, apt-get proposes an update:

$ sudo apt-get upgrade -V
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be upgraded:
   trac-bitten (0.6-1 => 0.6b2.dfsg-3)
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/88.8 kB of archives.
After this operation, 102 kB disk space will be freed.

Seems like apt-get and aptitude way of holding packages are incompatible or apt-get can't hold packages at all. Why not to use aptitude instead of apt-get? It look more appealing for automated configuration management. This stuff is an absolute must for any SCM tool IMO - mark packages as "automatically installed" or "manually installed" so that packages can be auto-removed when no longer required, and this feature is just nice-to-have - score-based and (usually) smarter dependency resolver than apt-get.

Sadly. there are a lot of related bugreports with no indication when they will be fixed. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=146207 =/

comment:5 in reply to: ↑ 4 Changed 10 years ago by solj

Replying to https://www.google.com/accounts/o8/id?id=AItOawkPb0RtPyicSdU7pLcv1UrX-yCh-YjkOwU:

I see. I am using aptitude and it's strange.

$ sudo aptitude upgrade   
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
                                         

However, apt-get proposes an update:

$ sudo apt-get upgrade -V
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be upgraded:
   trac-bitten (0.6-1 => 0.6b2.dfsg-3)
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/88.8 kB of archives.
After this operation, 102 kB disk space will be freed.

Seems like apt-get and aptitude way of holding packages are incompatible or apt-get can't hold packages at all. Why not to use aptitude instead of apt-get? It look more appealing for automated configuration management. This stuff is an absolute must for any SCM tool IMO - mark packages as "automatically installed" or "manually installed" so that packages can be auto-removed when no longer required, and this feature is just nice-to-have - score-based and (usually) smarter dependency resolver than apt-get.

Sadly. there are a lot of related bugreports with no indication when they will be fixed. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=146207 =/

Weird. I'll leave this ticket open for now so that we can contemplate switching over to aptitude. We debated it before and at that time we didn't see any benefit to switching, however, this seems like the sort of situation where we may want to make the switch. In the interim, you can use the instructions in section 3.10 at http://www.debian.org/doc/manuals/apt-howto/ch-apt-get.en.html to pin the packages for your current clients.

comment:6 Changed 9 years ago by solj

  • Milestone changed from Bcfg2 1.3.0 Release to Bcfg2 1.4.0 Release

comment:7 Changed 6 years ago by solj

  • Status changed from new to closed
  • Resolution set to wontfix

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.