Your message dated Fri, 10 Feb 2017 18:07:42 +0000 with message-id <20170210180742.ppeqj273ulpa3z67@powdarrmonkey.net> and subject line Re: Bug#854540: Please unblock package gitlab has caused the Debian Bug report #854540, regarding unblock: gitlab/8.13.11+dfsg-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 854540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854540 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit <submit@bugs.debian.org>
- Subject: Please unblock package gitlab
- From: Praveen Arimbrathodiyil <praveen@debian.org>
- Date: Wed, 08 Feb 2017 06:24:01 -0000
- Message-id: <[🔎] E-YEziFACrNBp78h6AnMqdmCjnZPnEUuD5SIPI9vNd219a@mailpile>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock Please unblock package gitlab It fixes grave bug #853251 (being able to push to a repo is a core functionality) debdiff attached unblock gitlab/8.13.11+dfsg-2 -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)Attachment: gitlab_8.13.11+dfsg-1.dsc..gitlab_8.13.11+dfsg-2.dsc.debdiff
Description: Binary dataAttachment: signature.html
Description: OpenPGP Digital Signature
--- End Message ---
--- Begin Message ---
- To: Pirate Praveen <me@j4v4m4n.in>, 854540-done@bugs.debian.org
- Subject: Re: Bug#854540: Please unblock package gitlab
- From: Jonathan Wiltshire <jmw@debian.org>
- Date: Fri, 10 Feb 2017 18:07:42 +0000
- Message-id: <20170210180742.ppeqj273ulpa3z67@powdarrmonkey.net>
- In-reply-to: <[🔎] 1486604517004.4ae2fb247e8a48@mozgaia>
- References: <[🔎] E-YEziFACrNBp78h6AnMqdmCjnZPnEUuD5SIPI9vNd219a@mailpile> <[🔎] 20170208201913.42pwi7ud4a4wex75@powdarrmonkey.net> <[🔎] 1486604517004.4ae2fb247e8a48@mozgaia>
On Thu, Feb 09, 2017 at 01:41:56AM +0000, Pirate Praveen wrote: > Control: tags -1 - moreinfo > > Jonathan Wiltshire wrote: > > If I read the diff right (and I'm happy to be corrected), you're patching > > files in debian/ with a patch in debian/patches/ ? Seems an odd way to go > > about things to me. > > The previous patch was incomplete and added a regression. Since upstream did not promise a timeline for the backport, I did the backport, but that missed some changes. This new patch is backported by upstream and tested to make sure the regression is gone. > Just seems an odd way to manage debian/ to me, but fine. > > Not all of your changes have entries in debian/changelog, please be careful > > to document them thoroghly. > > only lintian warnings were updated, I will be more thorough in future updates. And an uploader, but ok. Unblocked. Thanks, -- Jonathan Wiltshire jmw@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
--- End Message ---