aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* add bug IDThierry Vignaud2014-10-231-1/+1
|
* typo fixThierry Vignaud2014-10-231-1/+1
|
* 5.015.01Thierry Vignaud2014-10-232-1/+3
|
* fix crashing in ptread when using log callback with rpm-4.12Thierry Vignaud2014-10-232-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fix by Panu Matilainen When rpmlog() occurs, it now grabs a read/write lock on the log context depending on whether it needs to save the log or not. The callback executes while the context lock is held, so when one call rpmlogMessage() or pretty much any rpmlog-related function from the callback, it'll try to lock the context again. Which is okay as long as rpmlog() only needed a read-lock on the context. However if it has a write-lock then attempting to grab a read-lock for rpmlogMessage() fails, but due to the largely missing error handling in rpmlog.c it falls through to crash and burn. The only reason we need to call rpmlogMessage() is that the callback does not match the callback function type in rpm >= 4.6: typedef int (*rpmlogCallback) (rpmlogRec rec, rpmlogCallbackData data); We shouldn't call that from log callback. We can avoid the issue by using rpmlogRecMessage() instead of rpmlogMessage() inside the callback. These are not the same, rpmlogRecMessage() returns the message of the *current* log event, whereas rpmlogMessage() returns the last *saved* log event. Which might not exist, might be from an earlier event or it might be the current event. ...and it'll not only work in all rpm >= 4.6 versions, but also give the actual log message at hand, instead of something that might have happened in the past.
* kill bogus filesThierry Vignaud2014-09-143-132/+0
|
* 5.005.00Thierry Vignaud2014-09-122-1/+3
|
* rename a variableThierry Vignaud2014-09-121-3/+3
|
* s/suggested/recommended/Thierry Vignaud2014-09-121-3/+3
|
* {suggested} is renamed {recommended} in stateThierry Vignaud2014-09-122-1/+2
| | | | Veuillez saisir le message de validation pour vos modifications. Les lignes
* kill unused argumentThierry Vignaud2014-09-121-2/+2
|
* add aliases for compatibilityThierry Vignaud2014-09-121-0/+3
|
* rename "no_suggests" option as "no_recommends"Thierry Vignaud2014-09-122-2/+3
|
* s/suggests/recommends/ in method namesThierry Vignaud2014-09-122-14/+15
|
* s/suggests/recommends/ in comments & variable namesThierry Vignaud2014-09-121-12/+12
|
* add support for generating recommends in synthesisThierry Vignaud2014-09-123-3/+7
| | | | aka having @recommends@ lines instead of @suggests@ ones
* recognize "recommends" lines in synthesisThierry Vignaud2014-09-121-1/+1
|
* rename "suggests" method as "recommends_nosense"Thierry Vignaud2014-09-124-4/+6
| | | | | in order to reflect reality but keep a suggests alias for compatibility for the time being
* rename "suggests" field to "recommends"Thierry Vignaud2014-09-124-8/+140
| | | | as this really what it is
* make it compatible with rpm-4.12.0Thierry Vignaud2014-09-122-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | rpm-4.12.0 introduces a new weak deps implementation (the 3rd one to be used in mdv/mga!) The tag we used to use (RPMTAG_SUGGESTSNAME) is now OLDSUGGESTSNAME => we need to handle both old & new tags Hopefully rpm-4.12.x enables to check both old & new tags when using xxxNVRS variants We thus have a choice between RECOMMEND & SUGGEST tags, that both fallback on older SUGGESTS tags if no new ones are found. The difference is that they filter old suggests depending on RPMSENSE_STRONG hint. As we used suggests in the recommends role, this is the perfect time to switch from suggests to recommends (with a patch on rpm in order to fallback RECOMMEND on weak (old) SUGGESTS instead of on strong (old) ENHANCES as we didn't used the later in mga) Our rpm is patched so that RECOMMENDNAME fallbacks too. In Suse, only RECOMMENDNEVRS is the only RECOMMEND variant that handle the fallback on old tags. However, using RPMTAG_RECOMMENDNEVRS makes URPM->suggest_nosense to return versionated suggests, which while not supported by urpmi, do are used by a couple packages (such as git or gnome-user-share) This breaks urpmi as suggests on "foo >= x.y" is not interpreted by urpmi which thinks that "foo" is a new suggests and reinstalls a previously removed suggests Hence we patched rpm.
* use HEADERGET_EXT instead of HEADERGET_DEFAULTThierry Vignaud2014-08-271-2/+2
| | | | | in order to access to extension tags such as new weak deps tags (needed for next commit)
* 4.314.31Thierry Vignaud2014-06-272-1/+3
|
* (compare) croak if used on URPM::Package object (mga#12766)Thierry Vignaud2014-05-172-0/+3
| | | | | | suggests to use compare_pkg instead (needs a new rpmdrake)
* simplify after commit 307fdff9e12f783b01d0275d92c22b4cf7dd020fThierry Vignaud2014-05-141-3/+1
| | | | | | | | | | | its return value is now always () rationale: resolve_rejected() was wrong, since it blindly removes installed pkgs w/o trying to promote anything and @diff_provides can be nicely used to handle rejecting package one by one, then _handle_diff_provides() should do the right job. (spot by perl_checker)
* kill support for kernel-*source-strippedThierry Vignaud2014-05-122-7/+3
| | | | We don't have those since 2004 (10 years+)...
* document pack_header()Thierry Vignaud2014-05-122-0/+14
|
* kill useless "$Id: " linesThierry Vignaud2014-05-095-5/+0
| | | | they're obsolete since switching to git
* kill frenglishThierry Vignaud2014-05-091-2/+2
| | | | | present since commit 74c3cfe40e76d2cf047e7cbc57653298a460b658 (12 years ago...)
* typo fixThierry Vignaud2014-05-091-3/+3
|
* typo fixThierry Vignaud2014-05-071-1/+1
|
* 4.304.30Thierry Vignaud2014-05-012-1/+3
|
* fix 64k size limit on provides sizeThierry Vignaud2014-05-012-3/+5
| | | | | | this broke installing 32 bit kernel for drakx-installer-binaries (spotted by Pascal Terjan)
* perl_checker cleanupThierry Vignaud2014-03-181-1/+1
|
* supplement blacklistThierry Vignaud2014-03-181-0/+1
|
* fix warning in debug messageThierry Vignaud2013-12-162-1/+3
| | | | | | | 'Argument "19697|19..." isn't numeric in array element at ...URPM/Resolve.pm' introduced by pixel in commit 1d945d2a483598dc982cf73ae932d83d4e35df9 on Sep 7 2007 ("add some debug messages)
* 4.294.29Thierry Vignaud2013-11-052-1/+3
|
* $trans->order: add support for "deploops" optionThierry Vignaud2013-11-052-1/+13
|
* enhance POD documentationThierry Vignaud2013-11-053-179/+551
|
* list the suggests() methodThierry Vignaud2013-11-051-0/+2
|
* indent optionsThierry Vignaud2013-11-051-0/+4
|
* document URPM::DB::verify() & URPM::stream2header()Thierry Vignaud2013-11-051-0/+8
| | | | why didn't you document it when you introduced them (pascal & rafael)?
* split into smaller sections for improved readabilityThierry Vignaud2013-11-051-17/+55
|
* (listlength) get rid of itThierry Vignaud2013-11-051-5/+1
|
* document transaction element APIThierry Vignaud2013-11-051-0/+22
|
* add "SEE ALSO" with link to urpmiThierry Vignaud2013-11-051-0/+6
|
* (resolve_requested_suggests) small optimizationThierry Vignaud2013-11-051-1/+1
|
* document search() optionsThierry Vignaud2013-11-051-3/+5
|
* fix doble spaceThierry Vignaud2013-11-051-1/+1
|
* "implement" create_transaction() in --env case (rule of least surprise)Thierry Vignaud2013-11-052-0/+10
| | | | (for rpmdrake --env)
* 4.284.28Thierry Vignaud2013-10-032-1/+3
|
* coverity: add a comment about "Argument cannot be negative"Thierry Vignaud2013-10-031-1/+1
| | | | "fd" is passed to a parameter that cannot be negative.
generated by cgit v1.2.1 (git 2.21.0) at 2024-11-21 15:30:00 +0000