Bug#867190: stretch-pu: package apt/1.4.7
On Thu, Jul 13, 2017 at 09:00:06PM +0100, Adam D. Barratt wrote:
> Control: tags -1 -moreinfo +confirmed
>
> On Sun, 2017-07-09 at 17:08 +0200, Julian Andres Klode wrote:
> > The first one by David, the second by me, so this would end up
> > something like the following (order may be different, it's auto-generated
> > from git commits):
> >
> > apt (1.4.7) stretch; urgency=medium
> >
> > [ Robert Luberda ]
> > * fix a "critical" typo in old changelog entry (Closes: 866358)
> >
> > [ David Kalnischkies ]
> > * use port from SRV record instead of initial port
> > * travis: ignore profiling warning in progress lines
> >
> > [ Julian Andres Klode ]
> > * Reset failure reason when connection was successful
>
> maybe "... ensuring errors are correctly reported" or something similar?
>
> > * debian/gbp.conf: Set debian-branch to 1.4.y
> > * http: Do not try reading content if Content-Length is 0
> > * travis: Migrate to Docker
> > * Release 1.4.7 (LP: #1702326)
>
> Having the release item at the end looks slightly odd, imho. :-)
>
> Please feel free to upload something like the above (bearing in mind
> that the window for 9.1 closes this weekend).
Uploaded with:
apt (1.4.7) stretch; urgency=medium
.
* New release with important fixes up to 1.5~beta1; also see LP: #1702326
.
[ Robert Luberda ]
* fix a "critical" typo in old changelog entry (Closes: 866358)
.
[ David Kalnischkies ]
* test suite/travis CI: ignore profiling warning in progress lines
* use port from SRV record instead of initial port
.
[ Julian Andres Klode ]
* Reset failure reason when connection was successful, so later errors are
reported as such and not as "connection failure" warnings.
* debian/gbp.conf: Set debian-branch to 1.4.y
* http: A response with Content-Length: 0 has no content, so don't try to
read it - it will either timeout or the server closes the connection.
* travis CI: Migrate to Docker
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
Reply to: