Am Mittwoch, 28. September 2011, 11:15:54 schrieb Richard W.M. Jones:
On Wed, Sep 28, 2011 at 08:55:43AM +0200, Roberto Ragusa wrote:
On 09/27/2011 07:46 PM, Richard W.M. Jones wrote:
https://admin.fedoraproject.org/pkgdb/acls/name/unison213
On Mon, 3 Oct 2011 19:22:28 +0200
Gregor Tätzner gre...@freenet.de wrote:
Any news from the FESCO team? What's the conclusion of this
discussion?
No one has officially asked fesco...
Please file a ticket what you actually want to ask fesco here?
https://fedorahosted.org/fesco/newtplticket
On Mon, Oct 03, 2011 at 11:32:18AM -0600, Kevin Fenzi wrote:
On Mon, 3 Oct 2011 19:22:28 +0200
Gregor Tätzner gre...@freenet.de wrote:
Any news from the FESCO team? What's the conclusion of this
discussion?
No one has officially asked fesco...
Please file a ticket what you actually
Am Montag, 3. Oktober 2011, 20:26:11 schrieb Richard W.M. Jones:
On Mon, Oct 03, 2011 at 11:32:18AM -0600, Kevin Fenzi wrote:
On Mon, 3 Oct 2011 19:22:28 +0200
Gregor Tätzner gre...@freenet.de wrote:
Any news from the FESCO team? What's the conclusion of this
discussion?
No one
On Mon, Oct 03, 2011 at 10:05:09PM +0200, Gregor Tätzner wrote:
Another idea: Just put in the package *unison* the latest release and when a
new shiny version has been released we provide a compat version, so move
unison to *unisonXYZ* and update the *unison* package regularly.
I suppose
On 09/28/2011 11:00 PM, Richard W.M. Jones wrote:
I checked the source code, and unison sends a header which contains
the current major version number of the software (where major
version is a string, currently 2.40). If the major versions of
each end don't exactly match, unison aborts. It
Am Freitag, 30. September 2011, 11:10:27 schrieb Tom Callaway:
On 09/28/2011 11:00 PM, Richard W.M. Jones wrote:
I checked the source code, and unison sends a header which contains
the current major version number of the software (where major
version is a string, currently 2.40). If the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/30/2011 01:38 PM, Gregor Tätzner wrote:
so many creative ideas ;)
But I think such a program would be confusing to users: When
someone wants to install unison, he expects the package will
install unison and a menu entry. And not a unison
On Sep 29, 2011, at 1:13 AM, Garrett Holmstrom wrote:
One build could produce a package for each version. The packages'
n-v-rs could then be maintained independently. I am not sure how bodhi
would behave in such a case, though.
This most certainly is not optimal; I'm simply throwing
On Thursday, 29 September 2011 at 15:38, Jesse Keating wrote:
On Sep 29, 2011, at 1:13 AM, Garrett Holmstrom wrote:
One build could produce a package for each version. The packages'
n-v-rs could then be maintained independently. I am not sure how bodhi
would behave in such a case,
On Sep 29, 2011, at 12:50 PM, Dominik 'Rathann' Mierzejewski wrote:
One solution would be to make per-version subpackages conditional via macros
and build only the one that has been updated.
Example: we have unison-2.9-1 package which produces
unison-2.9-1
unison28-2.8-2
unison21-2.1-5
On 09/27/2011 07:46 PM, Richard W.M. Jones wrote:
https://admin.fedoraproject.org/pkgdb/acls/name/unison213
https://admin.fedoraproject.org/pkgdb/acls/name/unison227
https://admin.fedoraproject.org/pkgdb/acls/name/unison
Instead of introducing yet another variation, can we somehow create a
On Wed, Sep 28, 2011 at 08:55:43AM +0200, Roberto Ragusa wrote:
On 09/27/2011 07:46 PM, Richard W.M. Jones wrote:
https://admin.fedoraproject.org/pkgdb/acls/name/unison213
https://admin.fedoraproject.org/pkgdb/acls/name/unison227
https://admin.fedoraproject.org/pkgdb/acls/name/unison
On Wed, 28 Sep 2011 10:15:54 +0100
Richard W.M. Jones rjo...@redhat.com wrote:
On Wed, Sep 28, 2011 at 08:55:43AM +0200, Roberto Ragusa wrote:
On 09/27/2011 07:46 PM, Richard W.M. Jones wrote:
https://admin.fedoraproject.org/pkgdb/acls/name/unison213
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/28/2011 10:20 AM, Kevin Fenzi wrote:
The problem here is that upstream has no desire to keep a common
protocol, so you need the exact version on both ends. (If I recall
correctly). So, if you have say a debian box with version foo, you
On Wed, Sep 28, 2011 at 12:10:32PM -0400, Tom Callaway wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/28/2011 10:20 AM, Kevin Fenzi wrote:
The problem here is that upstream has no desire to keep a common
protocol, so you need the exact version on both ends. (If I recall
On Wed, Sep 28, 2011 at 2:15 AM, Richard W.M. Jones rjo...@redhat.com wrote:
On Wed, Sep 28, 2011 at 08:55:43AM +0200, Roberto Ragusa wrote:
On 09/27/2011 07:46 PM, Richard W.M. Jones wrote:
https://admin.fedoraproject.org/pkgdb/acls/name/unison213
On 2011-09-28 14:15, Kevin Fenzi wrote:
On Wed, 28 Sep 2011 22:00:40 +0100
Richard W.M. Jonesrjo...@redhat.com wrote:
I was thinking of something slightly simpler: a single 'unison'
package that contained several binaries, like /usr/bin/unison227,
/usr/bin/unison (symlink to latest).
That
On Tue, Sep 27, 2011 at 05:13:46PM +0200, Gregor Tätzner wrote:
Hi,
Anyone want to review this one:
https://bugzilla.redhat.com/show_bug.cgi?id=734531
I'm sure a lot of Fedora users are awaiting this update.
Questions ...
Are we going to obsolete these packages:
Am Dienstag, 27. September 2011, 19:46:08 schrieb Richard W.M. Jones:
On Tue, Sep 27, 2011 at 05:13:46PM +0200, Gregor Tätzner wrote:
Hi,
Anyone want to review this one:
https://bugzilla.redhat.com/show_bug.cgi?id=734531
I'm sure a lot of Fedora users are awaiting this update.
20 matches
Mail list logo
