| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
See https://pycairo.readthedocs.io/en/latest/changelog.html#v1-20-0.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I made a mistake merge. Reverting it in c778945806b undid the state
on master, but now I realize it crippled the git merge mechanism.
As the merge contained a mix of commits from `master..staging-next`
and other commits from `staging-next..staging`, it got the
`staging-next` branch into a state that was difficult to recover.
I reconstructed the "desired" state of staging-next tree by:
- checking out the last commit of the problematic range: 4effe769e2b
- `git rebase -i --preserve-merges a8a018ddc0` - dropping the mistaken
merge commit and its revert from that range (while keeping
reapplication from 4effe769e2)
- merging the last unaffected staging-next commit (803ca85c209)
- fortunately no other commits have been pushed to staging-next yet
- applying a diff on staging-next to get it into that state
|
|
|
|
|
|
|
| |
I'm sorry; I didn't notice it contained staging commits.
This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing
changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075.
|
|
|
|
|
|
|
|
| |
* drop unneeded xlibs dependency
* correct license
* do not use pkgconfig alias
* use pytestCheckHook
* format
|
| |
|
| |
|
| |
|
|
|
|
| |
https://pycairo.readthedocs.io/en/latest/changelog.html#v1-18-1
|
|
|
|
| |
Changelog: https://pycairo.readthedocs.io/en/latest/changelog.html
|
| |
|
| |
|
|
|
|
| |
Only acts on one-line dependency lists.
|
| |
|
| |
|
|
|
|
| |
so that we can use the update script.
|
|
|
|
|
| |
Apply the same patch as for Python 3.5 so that this builds correctly.
Addresses #24501.
|
|
|
|
|
| |
This way all Python packages use the same function,
`buildPythonPackage`.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The patch was taken from FreeBSD, it is also used on debian. see:
https://svnweb.freebsd.org/ports/head/graphics/py3-cairo/files/pycairo-1.10.0-waf-py3_5.patch?revision=401900&view=markup
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Scilab note: the parameters already had pointed to nonexistent dirs
before this set of refactoring. But that config wasn't even used by
default.
|
|
|
|
|
|
| |
This commit was should fix issue #7586, but it does not.
This reverts commit e1c65ddfe11c8070dda00a66f2b4ae45bbddb0bc.
|
| |
|
|
|
|
|
|
|
|
| |
dependencies."
This reverts commit bf86758a42f7db8c1710f1226162d9e3b6c5e9e6.
See 71a9aa10ca25f5659a657d8910e11f36c3439a36
|
| |
|
| |
|
|
|
|
| |
Fixes #2693.
|
|
|
|
| |
Close #1802.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
a worthy goal to move the Python packages that are currently in
all-packages.nix into a single attribute set, but this doesn't
require moving python-packages.nix or the other changes made to that
file. The Python packages in all-packages.nix should simply be
moved to python-packages.nix, and ideally changed to use
buildPythonPackage.
svn path=/nixpkgs/trunk/; revision=21196
|
|
|
|
|
|
|
|
|
| |
- cleanup python libraries:
* moving all python libraries into a attr set into a directory
so that expressions can be used for both: python 2.5 and 2.6 easily
* disabling packages which don't build
svn path=/nixpkgs/trunk/; revision=21142
|
|
|
|
|
|
| |
With a newer glib, I could have used a newer pyobject.
svn path=/nixpkgs/trunk/; revision=20962
|
|
svn path=/nixpkgs/trunk/; revision=8666
|