[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#928428: marked as done (unblock: [pre-approval] wicd/1.7.4+tb2-7)

Your message dated Thu, 6 Jun 2019 21:26:38 +0200
with message-id <f531ac97-c8dc-6a4d-00a6-26aa3d8d3c67@debian.org>
and subject line Re: Bug#928428: unblock: [pre-approval] wicd/1.7.4+tb2-7
has caused the Debian Bug report #928428,
regarding unblock: [pre-approval] wicd/1.7.4+tb2-7
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.)


-- 
928428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928428
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

In the light of dhcpcd5 automremoval (#928056, #928104, #928105), I'd
like to upload a wicd package which relies less on dhcpcd5. It
actually is already committed in Git, but the upload didn't happen due
to not having found the time to test it thoroughly on a machine which
only has dhcpcd5 installed. (Which I still plan to do, even iqn this
light.)

Currently the master branch of https://salsa.debian.org/debian/wicd
contains a bit more commits than useful at this stage of the release,
so I intent to cherry pick a bunch of these commits into a new branch
for buster/1.7.4+tb2-7 and then upload the remaining commits with
probably 1.7.4+tb2-8 after buster.

What I'd cherry-pick in any case:

  * Don't list dhcpcd5 as preferred DHCP client in the alternative
    dependencies list. (Closes: #901592)

This should (hopefully) also make wicd no more affected by dhcpcd5's
autoremoval.

What I think should be done, too, but is probably less important when
dhcpcd5 is removed:

  * Look for "dhcpcd5" instead of "dhcpcd". (Closes: #852343)

This is currently of normal severity but in combination with an
unfixed #901592 it is actually grave as it doesn't find the default
DHCP client anymore. Then again, if dhcpcd5 is no more the default or
even removed, the current severity of normal is more than fitting.

I'd also include these purely documentational changes:

  * d/copyright: Change Format URL to correct one

I'll prepare a feature branch for this in git including a planned
debdiff and let you know once it's ready for review/upload. I though
would happy to receive feedback from the release team beforehand.

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Hi Axel,

On Sun, 12 May 2019 22:21:12 +0200 Axel Beckert <abe@debian.org> wrote:
> So I'm generally fine with postponing this until bullseye. If you
> agree with my reasoning above, please close this unblock request.

For as far as I checked, I agree with the reasoning.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: