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

Bug#905996: marked as done (nmu: clsync_0.4.1-1)

Your message dated Tue, 2 Oct 2018 18:15:37 +0200
with message-id <cb5c8e4e-ef2e-e092-5012-3d39b237ef63@debian.org>
and subject line Re: Bug#905996: nmu: clsync_0.4.1-1
has caused the Debian Bug report #905996,
regarding nmu: clsync_0.4.1-1
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.)


-- 
905996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905996
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: binnmu

Hi release team,

One of the goal of the glibc team for buster is to get rid of the
multiarch-support package, given that multiarch support in the dynamic
loader is fully supported in debian for a long time. Debhelper used to
add this dependency, but it's not the case anymore.

clsync is one out of two packages left in buster, the other one,
gtk2-engines-oxygen, should hopefully migrate in the next days.
Unfortunately clsync has an RC bug in sid, which prevents it to migrate
to buster. This RC bug is not present in buster, so the package hasn't
been autoremoved from there.

Therefore the easiest way to fix the issue is to trigger a binNMU in
*buster*, against a "recent" debhelper:

nmu clsync_0.4.1-1 . ANY . buster . -m "Rebuild to remove the pre-dependency on multiarch-support"

Thanks,
Aurelien

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
On 16/08/2018 23:03, Aurelien Jarno wrote:
> On 2018-08-15 05:45, Niels Thykier wrote:
>> Aurelien Jarno:
>> [...]
>>>> then removing clsync from testing is also an option
>>>> AFAICT.
>>>>
>>>> I am considering since clsync has had its FTBFS bug against sid for
>>>> almost 2 years now with no reaction from its maintainers.
>>>
>>> That solution has the same result than the binNMU, so that's also fine
>>> for me. I would leave the decision about what is the best way to achieve
>>> that to the release team.
>>>
>>> Thanks,
>>> Aurelien
>>>
>>
>> Could you please file an RC bug against clsync that affects the
>> *testing* version (tags sid + buster if that version is also in stable)
>> about this issue?
> 
> I have just filled #906307 for that.

The package is no longer in testing. Thus closing this testing binNMU request.

Cheers,
Emilio

--- End Message ---
Reply to: