Please upgrade git-core to 1.6.2.4

[Joseph Smidt]

Please upgrade git-core 1.6.0.4 to git-core 1.6.2.4 found in debian.

[Joseph Smidt (jsmidt)]

Here is the debdiff. Please sponsor the upload.

[Scott James Remnant (Canonical) (canonical-scott)]

Assuming that the debdiff is based off the Debian package, it does not include the previous Ubuntu debian/changelog entries.

Also you say that the package preserves an Ubuntu change of dropping a cvsps build-dependency, yet this is clearly still in the package.

You don't explain why you've dropped the Recommends on libauthen-sasl-perl and the Depends on libnet-smtp-ssl-perl?

[Joseph Smidt (jsmidt)]

Thank you for your comments. Here is the new debdiff based off of the Debian package in experimental: http://ftp.de.debian.org/debian/pool/main/g/git-core/git-core_1.6.0.6-1.dsc.

Please sponsor the upload.

[Scott James Remnant (Canonical) (canonical-scott)]

On Tue, 2009-01-20 at 17:54 +0000, Joseph Smidt wrote:

> ** Attachment added: "git-core_1.6.0.6-1ubuntu1.debdiff"
> http://launchpadlibrarian.net/21477877/git-core_1.6.0.6-1ubuntu1.debdiff
>
This now changes a Recommends to a Depends? Thoughts?

Is the fact that Debian have this as a Recommends not already
sufficient? Check the LP bug to see.

Scott
--
Scott James Remnant
<email address hidden>

[Joseph Smidt (jsmidt)]

This Recommends/Depends thing was to clear up a bug in Debian #505636. The original patch send to the Debian devs by the Ubuntu dev Kees Cook had libnet-smtp-ssl-perl as Depends and libauthen-sasl-perl as recommends. The Debian dev decided having both under recommends was sufficient to close the bug.

In the last debdiff I moved the one package to Depends to reflect the Ubuntu dev's wishes. However, my thoughts are that we should stick with how the Debian dev decided to implement it.

Here is the new debdiff.

[Anders Kaseorg (andersk)]

1.6.1.3 is in unstable now. Here is a new debdiff.

[Anders Kaseorg (andersk)]

I’ve built this package in my PPA <https://launchpad.net/~anders-kaseorg/+archive/ppa> and tested it. It should be ready for upload to Jaunty main.

[Anders Kaseorg (andersk)]

This also fixes bug 224038 (/etc/init.d/git-daemon is not a script) and bug 315870 (Outdated).

[Anders Kaseorg (andersk)]

1.6.2-1 is in testing now. Here is a new debdiff.

[Scott James Remnant (Canonical) (canonical-scott)]

None of these bugs seem severe enough to warrant breaking both Upstream Version Freeze and Feature Freeze for this, we can pick the update up in karmic

[Joseph Smidt (jsmidt)]

Scott,

      On Jan. 19, well before the feature freeze, a bug report was filed to bring git 1.6.0.4 to 1.6.0.6 to fix bugs and the patch to do so was even provided. You had some initial issues with the patch, but after they were addressed you assigned yourself to the bug report on Jan. 20.

      Then you decided to wait until after the feature freeze to say "None of these bugs seem severe enough to warrant breaking... Feature Freeze".

Scott, is it standard practice for member's of Ubuntu's technical board to assign themselves to bugs with patches submitted over a month before the feature freeze then wait until after the feature freeze and say "sorry, can't fix bugs after the feature freeze." Perhaps this is why Ubuntu has so many un-fulfilled confirmed bug reports.

Please:

1. Don't assign yourself to bugs of packages you have a public disdain for [1] if you won't patch them.

2. Don't assign yourself to bugs with a patch, then wait until after feature freeze to say "sorry, it's now too late."

PS. To be fair, most other Ubuntu developers do upload your patches when you get patches into the form they request when submitted a month before the feature freeze.

[1] http://www.netsplit.com/2009/02/17/git-sucks/

[Joseph Smidt (jsmidt)]

Scott,

I admit my last post was a knee-jerk reaction to a perceived neglect of git do to a personal bias. I am sorry I handled the situation so immaturely.

[Scott James Remnant (Canonical) (canonical-scott)]

On Thu, 2009-03-12 at 16:35 +0000, Joseph Smidt wrote:

> I admit my last post was a knee-jerk reaction to a perceived neglect of
> git do to a personal bias. I am sorry I handled the situation so
> immaturely.
>
No problem ;) We all have a scream and shout sometimes, often on our
blogs <g>

I'm obviously not biased against GIT in any way that'd stop me wanting
to import it - I actually /use/ it daily, which is why I rant about it
sometimes.

A correction to your post though, Jan 19 is before FF, but after Debian
Import Freeze (Dec 25th) so this request was already after the relevant
freeze.

I assigned the bug to myself as part of the usual sponsorship process,
we don't like them to go unassigned. As you'd expect, this isn't the
only bug on my list - nor the only project.

I'm sorry that I didn't get to it, but it does all come down to a matter
of priority. Had the update fixed some high or critical bugs, it would
have been much higher on my list and more likely to have been done.

I hear your concerns about the un-filfilled confirmed bug reports.
Unfortunately there doesn't seem to be any quick solution to this
problem that Ubuntu is having.

The simple fact is that we have literally hundreds of thousands of bugs,
and less than a hundred developers.

For example, it took two of us almost a week to fully debug and iron out
the issue of the floppy disk drive not being auto-loaded. That bug had
sat confirmed for two releases!

Scott
--
Scott James Remnant
<email address hidden>

[Anders Kaseorg (andersk)]

Doesn’t the Debian Import Freeze only affect automatic syncs from Debian? This package is ineligible for an automatic sync anyway, because of the Ubuntu modification. That is why it was held back on the obsolete version for so long. So perhaps this would be less of a problem in the future if we could find some way to remove the Ubuntu modification; for example, can we move cvsps to main?

[Anders Kaseorg (andersk)]

Debdiff for karmic, when you get around to it.

[Anders Kaseorg (andersk)]

Dropping the cvsps build dependency (because cvsps is in universe) is the last Ubuntu-specific patch that isn’t already in Debian. I filed a main inclusion report for cvsps, bug #369111. If that is accepted, we will be able to sync from unstable instead of doing another ubuntu1 upload.

[Scott James Remnant (Canonical) (canonical-scott)]

debdiff looks ok to me

[Launchpad Janitor (janitor)]

This bug was fixed in the package git-core - 1:1.6.2.4-1ubuntu1

---------------
git-core (1:1.6.2.4-1ubuntu1) karmic; urgency=low

  * Merge from debian unstable (LP: #319096, #224036, #315870), remaining
    changes:
    - debian/control: Drop recently introduced cvsps build dependency;
      it's only necessary or some self tests, but is in universe (Ubuntu
      specific).

 -- Anders Kaseorg <email address hidden> Wed, 29 Apr 2009 03:30:00 -0400