aboutsummaryrefslogtreecommitdiffstats
path: root/NEWS
Commit message (Collapse)AuthorAgeFilesLines
* Revert "workaround perl-5.26 vs librpm bug"Thierry Vignaud2017-09-141-0/+3
| | | | | This reverts commit 4cb2fcc5bf443de9f3f05fe085c42a317101321b. This is no more needed as of rpm-4.14.0-0.rc1.3.mga7
* 5.145.14Thierry Vignaud2017-09-071-0/+2
|
* use native 64bit integers instead of Math::Int64Thierry Vignaud2017-09-071-0/+3
| | | | it's now possible since perl-5.26.0-8.mga7
* Revert "make sure to use int64 on 32bit arch"Thierry Vignaud2017-09-071-2/+0
| | | | This reverts commit 8aceb9b6a318668d0795af52bf9ea9dbb33351d9.
* 5.135.13Thierry Vignaud2017-08-231-0/+2
|
* log previous changeThierry Vignaud2017-08-231-0/+2
|
* workaround perl-5.26 vs librpm bugThierry Vignaud2017-07-221-0/+1
| | | | | which results in the following on exit cleanup: 'panic: free from wrong pool, 0!=6c7010 during global destruction.'
* enhanceThierry Vignaud2017-07-221-1/+2
|
* fix test failure with perl-5.26Thierry Vignaud2017-07-211-0/+2
|
* 5.125.12Thierry Vignaud2016-11-101-0/+2
|
* make sure to use int64 on 32bit archPascal Terjan2016-11-101-0/+2
| | | | | else we may got total size to overflow (mga#19686) v2 by Thierry Vignaud: use native int64 on 64bit
* log previous commitsThierry Vignaud2016-11-101-0/+2
|
* add bug IDThierry Vignaud2016-10-201-1/+1
|
* 5.115.11Thierry Vignaud2016-10-201-0/+2
|
* fix crash introduced by mga#15353 fix (mga#19618)Thierry Vignaud2016-10-201-0/+1
| | | | | | | | rationale: - {debug_URPM} only exists if we're in debug mode - as this is an actual error, let's just always report it bug introduced in commit 070f1be3d5c3aa813f61d061c2a0fd38c2477c08
* fix another (old) compilation warningsThierry Vignaud2016-10-181-0/+2
| | | | use rpmTagGetValue() to get the char* name of the tag
* 5.105.10Thierry Vignaud2016-10-181-0/+2
|
* (get_int2) try new 64bit tag else old 32bit tagThierry Vignaud2016-10-181-0/+1
| | | | | | thus enabling to report size of >4Gb packages (however insane this is): rpmlib uses the old small tag for small packages and the new big tag for big packages (mga#19571)
* switch to uint64_t for sizes (mga#19571)Thierry Vignaud2016-10-181-0/+2
| | | | Thus we use 64bit for package size on 32bit too, thanks to Math::Int64
* 5.095.09Thierry Vignaud2016-10-161-0/+2
|
* log previous fixThierry Vignaud2016-10-161-0/+2
|
* 5.085.08Thierry Vignaud2016-10-141-0/+2
|
* (check) fix reporting problemsThierry Vignaud2016-10-141-0/+1
| | | | | | | | | | | | | | | | | for at least 12 years, since swiching rpm to 4.2 (see commit 60031191b7012fdfe8e1af6bd43ff9b36b0c5825) $trans->check() failed to actually report issues rationale: rpmtsCheck() only actually return !0 if it fails to open rpmdb... in order to check if any problem was found by rpmtsCheck(), one must call retrieving the problem set with rpmtsProblems() rpmtsCheck() success only means that the resolution was successfully attempted for all packages in the set, which isn't that usefull... this might help mga#15350...
* fix reporting size on big packages (mga#19571)Thierry Vignaud2016-10-131-0/+2
|
* 5.075.07Thierry Vignaud2016-04-141-0/+2
|
* don't push $fullname to callback stackThierry Vignaud2016-04-141-0/+2
| | | | that's no more needed...
* add support for "elem" callbackThierry Vignaud2016-04-141-0/+3
| | | | | This callback will be fired before each pkg being installed/removed Needs rpm >= rpm-4.13.0-0.rc1.28
* 5.065.06Thierry Vignaud2015-04-121-0/+2
|
* fix upgrade when package's in several mediaThierry Vignaud2015-04-121-0/+2
| | | | | | | | sort by ids (like in other places) when promoting (b/c of eg: conflicts), thus fixing upgrade when the same package is offered in several media (mga#15350) see commit 53e38beae4d9638f41b219521b802a2969d68909 for similar issue
* 5.055.05Thierry Vignaud2015-02-261-0/+2
|
* fix a segfault when callbacks don't get a headerPascal Terjan2015-02-261-0/+2
|
* 5.045.04Thierry Vignaud2015-02-261-0/+2
|
* callbacks now get pkg name instead of just pkg idThierry Vignaud2015-02-261-0/+3
| | | | thus fixing unknown package name on erases (mga#15032)
* 5.035.03Thierry Vignaud2014-11-141-0/+2
|
* Handle non numeric returns for traverse_tag_find callbackPascal Terjan2014-11-141-0/+1
| | | | fix a warning spot by Angelo Naselli
* add a missing PUTBACK in traverse_tag_find()Thierry Vignaud2014-11-141-0/+2
| | | | | | this is needed after using POPi bug introduced in commit 4294365db5d78909ae5a490e0714db379502cd80
* 5.025.02Thierry Vignaud2014-10-261-0/+2
|
* add >recommends method (mga#14376)Thierry Vignaud2014-10-261-0/+2
| | | | unlike recommends_nosense, it returns version too
* add bug IDThierry Vignaud2014-10-231-1/+1
|
* typo fixThierry Vignaud2014-10-231-1/+1
|
* 5.015.01Thierry Vignaud2014-10-231-0/+2
|
* fix crashing in ptread when using log callback with rpm-4.12Thierry Vignaud2014-10-231-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* 5.005.00Thierry Vignaud2014-09-121-0/+2
|
* {suggested} is renamed {recommended} in stateThierry Vignaud2014-09-121-0/+1
| | | | Veuillez saisir le message de validation pour vos modifications. Les lignes
* rename "no_suggests" option as "no_recommends"Thierry Vignaud2014-09-121-0/+1
|
* s/suggests/recommends/ in method namesThierry Vignaud2014-09-121-0/+1
|
* add support for generating recommends in synthesisThierry Vignaud2014-09-121-0/+2
| | | | aka having @recommends@ lines instead of @suggests@ ones
* rename "suggests" method as "recommends_nosense"Thierry Vignaud2014-09-121-0/+1
| | | | | in order to reflect reality but keep a suggests alias for compatibility for the time being
* make it compatible with rpm-4.12.0Thierry Vignaud2014-09-121-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* 4.314.31Thierry Vignaud2014-06-271-0/+2
|
generated by cgit v1.2.1 (git 2.21.0) at 2024-11-24 20:12:03 +0000