GNU Health - Bugs: bug #46996, vobject version name changed
You are not allowed to post comments on this tracker with your current authentication level.
bug #46996: vobject version name changed
Submitter: | Luis Falcon <meanmicio> | ||
Submitted: | Thu 28 Jan 2016 12:06:39 PM UTC | ||
Category: | Installation | Severity: | 4 - Important |
Item Group: | None | Status: | Fixed |
Privacy: | Public | Assigned to: | meanmicio |
Open/Closed: | Closed | Release: | 3.0.0 |
Module: | gnuhealth-setup | Component: | None |
Jump to the original submission
Fri 29 Jan 2016 09:48:06 AM UTC, comment #6: |
Cédric Krier <cedk> |
Fri 29 Jan 2016 09:25:49 AM UTC, comment #5: Hi !
|
Luis Falcon <meanmicio> |
Fri 29 Jan 2016 07:12:31 AM UTC, comment #4: Is not showing that it will be better to no pin exact package number but just real dependencies? Other point is that you could miss security update with pinning package version. |
Cédric Krier <cedk> |
Fri 29 Jan 2016 06:49:44 AM UTC, comment #3: The vobject developers just released the vobject-0.8.2, reverting the issues it caused the latest version published a couple of days ago (renaming the package and removing the ez_setup dependency).
|
Luis Falcon <meanmicio> |
Thu 28 Jan 2016 12:47:40 PM UTC, comment #2: The new version gnuhealth-setup 3.0.1 that fixes this issue is now available at GNU.
|
Luis Falcon <meanmicio> |
Thu 28 Jan 2016 12:09:24 PM UTC, comment #1: Fixed on changeset 2376:6e74c0945df7
|
Luis Falcon <meanmicio> |
Thu 28 Jan 2016 12:06:39 PM UTC, original submission:
vobject (vCal / iCal module) name has changed on pypi , from vobject-0.8.1c to vobject-0.8.1c-dist . Additionally, ez_setup module is required on this version.
|
Luis Falcon <meanmicio> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-01-28 | meanmicio | Status | Confirmed | Fixed | |
Release | None | 3.0.0 | |||
2016-01-28 | meanmicio | Open/Closed | Open | Closed |
Powered by Savane 3.13-4448.
Corresponding source code
I think the argument about unreliable version schema is any way doomed by this precise bug.
Creating a "GNU Health security" that will check security for all the software stack sounds to me like impossible to achieve without a huge effort. For that, I think it is much better to rely on an existing project with such team (like Debian for example).
So for me if the goal to achieve is to have a reproducible setup as recommended installation, we should work with an existing distribution and provide packages for this one (or work with maintainer to provide it).