OK - good idea.  I’ve done the rename and pushed to alioth.  I did a rebuild 
and it was all fine
but please double check!  Luckily there are no reverse dependencies on this 
package yet.


Thanks,

Tim.

> On 13 Aug 2015, at 3:11 pm, Michael Stapelberg <[email protected]> wrote:
> 
> I think before uploading, we should take the opportunity to make the
> package comply with our new naming scheme. Once you’ve done that I’m
> happy to take a look at it.
> 
> On Thu, Aug 13, 2015 at 5:40 AM, Potter, Tim (Cloud Services)
> <[email protected]> wrote:
>> Hi everyone.  I noticed a while ago that a tag was made for v3 (yay) and 
>> Tianon has even
>> packaged it up.  It hasn’t been uploaded though - is there anything holding 
>> it up?
>> 
>> 
>> Tim.
>> 
>>> On 9 Jun 2015, at 10:50 am, Potter, Tim (Cloud Services) 
>>> <[email protected]> wrote:
>>> 
>>> I submitted a github issue asking if they would be so kind as to make 
>>> another snapshot.  No response yet - I’ve got an email address to try out 
>>> before saying this hasn’t worked.
>>> 
>>> 
>>> Tim.
>>> 
>>>> On 9 Jun 2015, at 5:54 am, Tianon Gravi <[email protected]> wrote:
>>>> 
>>>> Yeah, it's been my experience that upstream's usually pretty
>>>> responsive with these kinds of requests (which is what makes me think
>>>> they're worth at least poking before we go head-first into a
>>>> snapshot).
>>>> 
>>>> ♥,
>>>> - Tianon
>>>> 4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
>>>> 
>>>> 
>>>> On 8 June 2015 at 12:52, Michael Stapelberg <[email protected]> wrote:
>>>>> That sure would be nice. Depending on the urgency, I’d be okay with
>>>>> uploading a snapshot if upstream doesn’t reply quickly, though.
>>>>> 
>>>>> On Mon, Jun 8, 2015 at 9:40 PM, Tianon Gravi <[email protected]> wrote:
>>>>>> 
>>>>>> Oh jeez, my response must've been from my phone before I configured it
>>>>>> to reply-all by default:
>>>>>> 
>>>>>> Why not ask upstream to tag a v3 instead of packaging a snapshot?
>>>>>> 
>>>>>> ♥,
>>>>>> - Tianon
>>>>>> 4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
>>>>>> 
>>>>>> 
>>>>>> On 8 June 2015 at 12:29, Michael Stapelberg <[email protected]> 
>>>>>> wrote:
>>>>>>> Sorry for the late reply. This all sounds good to me, please go ahead.
>>>>>>> 
>>>>>>> On Mon, Jun 1, 2015 at 8:01 AM, Potter, Tim (Cloud Services)
>>>>>>> <[email protected]> wrote:
>>>>>>>> 
>>>>>>>> Hi everyone.  I’d like to propose an update to the golang-go-systemd
>>>>>>>> package, to pull in files from the unit directory require for fleet.
>>>>>>>> Here’s
>>>>>>>> a debdiff between the version in Debian and my changes:
>>>>>>>> 
>>>>>>>> debdiff /var/cache/apt/archives/golang-go-systemd-dev_2-1_all.deb
>>>>>>>> /Source/pkg-go/build-area/golang-go-systemd-dev_2~git20150505-1_all.deb
>>>>>>>> [The following lists of changes regard files as different if they have
>>>>>>>> different names, permissions or owners.]
>>>>>>>> 
>>>>>>>> Files in second .deb but not in first
>>>>>>>> -------------------------------------
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> 
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/activation/packetconns.go
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> 
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/activation/packetconns_test.go
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/daemon/sdnotify.go
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/machine1/dbus.go
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> 
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/machine1/dbus_test.go
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/unit/deserialize.go
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> 
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/unit/deserialize_test.go
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/unit/escape.go
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/unit/escape_test.go
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/unit/option.go
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/unit/option_test.go
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/unit/serialize.go
>>>>>>>> -rw-r--r--  root/root
>>>>>>>> 
>>>>>>>> /usr/share/gocode/src/github.com/coreos/go-systemd/unit/serialize_test.go
>>>>>>>> 
>>>>>>>> Control files: lines which differ (wdiff format)
>>>>>>>> ------------------------------------------------
>>>>>>>> Built-Using: golang (= [-2:1.2.1-2),-] {+2:1.4.2-3),+} golang-dbus (=
>>>>>>>> [-1-1)-] {+2-1)+}
>>>>>>>> Installed-Size: [-120-] {+137+}
>>>>>>>> Version: [-2-1-] {+2~git20150505-1+}
>>>>>>>> 
>>>>>>>> As you can see files are only added so this should be a change that
>>>>>>>> does
>>>>>>>> not break any existing packages.
>>>>>>>> 
>>>>>>>> Please let me know if this is OK and I can push the updates to the
>>>>>>>> pkg-go/packages repo.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Tim.
>>>>>>>> _______________________________________________
>>>>>>>> Pkg-go-maintainers mailing list
>>>>>>>> [email protected]
>>>>>>>> 
>>>>>>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> Best regards,
>>>>>>> Michael
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Best regards,
>>>>> Michael
>>> 
>>> _______________________________________________
>>> Pkg-go-maintainers mailing list
>>> [email protected]
>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>> 
> 
> 
> 
> -- 
> Best regards,
> Michael

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Pkg-go-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to