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

Bug#900679: marked as done (nmu: Migrating developers-reference to Salsa and minor updates)

Your message dated Fri, 30 Nov 2018 00:02:18 +0100
with message-id <d0a06834-1e9f-2cc7-c690-b139f77959b3@free.fr>
and subject line Re: nmu: Migrating developers-reference to Salsa and minor updates
has caused the Debian Bug report #900679,
regarding nmu: Migrating developers-reference to Salsa and minor updates
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.)


-- 
900679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900679
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: developers-reference
Version: 3.4.19
Severity: normal

Dear Maintainer,

I would like to NMU developers-reference for migrating the repository to Salsa
and a couple of minor changes.

The complete changelog would be :

developers-reference (3.4.19+nmu1) UNRELEASED; urgency=medium

  [ Aurélien COUDERC ]
  * Non-maintainer upload.
  * Move repository to Salsa, update Vcs-* fields.
  * d/control: Bump Standards-Version to 4.1.4, no change needed.
  * Fix CSS text color to avoid the HTML version being unreadable when
    using a light on dark default browser stylesheet.

 -- Aurélien COUDERC <zecoucou@free.fr>  Thu, 31 May 2018 23:17:33 +0200


The repository is already up on Salsa at [0].
I’ve left the master branch untouched as was on Alioth and created an
nmu-3.4.19 branch with the changes above.
The complete diff is at [1].


[0] https://salsa.debian.org/dev-ref-team/developers-reference/
[1] https://salsa.debian.org/dev-ref-team/developers-
reference/compare/debian%2F3.4.19...nmu-3.4.19


Feel free to say if you think this is not a good idea or would better be done
differently.


Cheers,
--
Aurélien



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

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

developers-reference depends on no packages.

Versions of packages developers-reference recommends:
ii  debian-policy  4.1.4.1

Versions of packages developers-reference suggests:
ii  doc-base  0.10.8

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/doc/developers-reference/developers-reference.css (from developers-reference package)

--- End Message ---
--- Begin Message --- 
Version: 3.4.20

Le 16/11/2018 à 21:49, Holger Wansing a écrit :
> 
> Aurélien COUDERC <zecoucou@free.fr> wrote:
>> I would like to NMU developers-reference for migrating the repository to Salsa
>> and a couple of minor changes.
>>
>> The complete changelog would be :
>>
>> developers-reference (3.4.19+nmu1) UNRELEASED; urgency=medium
>>
>>   [ Aurélien COUDERC ]
>>   * Non-maintainer upload.
>>   * Move repository to Salsa, update Vcs-* fields.
>>   * d/control: Bump Standards-Version to 4.1.4, no change needed.
>>   * Fix CSS text color to avoid the HTML version being unreadable when
>>     using a light on dark default browser stylesheet.
> 
> The above changings were committed in the meantime, so the target of the
> OP and this bug is closed.
> 
> Thus this bug can closed, right?
> Any objections? (There was some discussion about maintenance of the
> devref package in this bug, however this does not deserve keeping this
> bug open, or it should be renamed accordingly.)

Indeed, this landed in 3.4.20 so closing the bug now.

Thanks for the ping.


Cheers,
--
Aurélien

--- End Message ---
Reply to: