[dev] FRR 2.0 Package now released in Ubuntu Snap store

Tue Apr 4 15:31:10 EDT 2017

Martin, you can easily reproduce the problem i described by simply running dpkg-buildpackage instruction.

> $ dpkg-buildpackage -rfakeroot -b -us -uc -d
> …
> dh_systemd_enable: Could not find "frr.service" in the /lib/systemd/system directory of frr-dbg. This could be a typo, or using Also= with a service file from another package. Please check carefully that this message is harmless.
> dh_systemd_enable: Cannot open(frr.service) for extracting the Also= line(s)
> dh_systemd_enable: Could not find "frr.service" in the /lib/systemd/system directory of frr-doc. This could be a typo, or using Also= with a service file from another package. Please check carefully that this message is harmless.
> dh_systemd_enable: Cannot open(frr.service) for extracting the Also= line(s)
> make[1]: Leaving directory '/sonic/src/frr'
> …

/Rodny

> On Apr 4, 2017, at 1:46 AM, Martin Winter <mwinter at opensourcerouting.org> wrote:
> 
> Rodny / Donald,
> 
> I’m happy to test the packages if you point me at the src (and potentially binary) packages.
> 
> I still hope we get some clean (and well tested) packages soon, but as a temp and quick fix,
> we can look at these.
> 
> - Martin
> 
> On 4 Apr 2017, at 0:58, Rodny Molina wrote:
> 
> Donald, before you upload these debian packages, you may want to check this out…
> 
> Have you tried to install/run these .deb images? If so, are you observing this too (see further below)?
> 
> I’m able to build .deb packages for Debian-Jessie, but typical installation instructions are missing in frr’s debian/rules (e.g. cp /usr/lib/frr/frr /etc/init.d/; update-rc.d frr defaults). In consequence, frr is not initiated as a service, nor we are giving users the chance of doing so, which is something quagga takes care of as part of its dpkg-building process.
> 
> As a fix, we could either defer ‘frr.service’ initialization to debian’s postinst-phase (quagga’s approach), or we can go ahead and insert these instructions in debian/rule itself. 
> 
> @Martin, do you have any suggestion? I can propose a fix but i’m far from being a deb-packager expert ;-)
> 
> 
> $ dpkg-buildpackage -rfakeroot -b -us -uc -d
> …
> dh_systemd_enable: Could not find "frr.service" in the /lib/systemd/system directory of frr-dbg. This could be a typo, or using Also= with a service file from another package. Please check carefully that this message is harmless.
> dh_systemd_enable: Cannot open(frr.service) for extracting the Also= line(s)
> dh_systemd_enable: Could not find "frr.service" in the /lib/systemd/system directory of frr-doc. This could be a typo, or using Also= with a service file from another package. Please check carefully that this message is harmless.
> dh_systemd_enable: Cannot open(frr.service) for extracting the Also= line(s)
> make[1]: Leaving directory '/sonic/src/frr'
> ...
> 
> /Rodny
> 
> 
>> On Apr 3, 2017, at 11:50 AM, Donald Sharp via dev <dev at lists.frrouting.org <mailto:dev at lists.frrouting.org>> wrote:
>> 
>> 
>> From: Donald Sharp <sharpd at cumulusnetworks.com <mailto:sharpd at cumulusnetworks.com>>
>> Subject: Re: [dev] FRR 2.0 Package now released in Ubuntu Snap store
>> Date: April 3, 2017 at 11:50:40 AM PDT
>> To: Martin Winter <mwinter at opensourcerouting.org <mailto:mwinter at opensourcerouting.org>>
>> Cc: JR Rivers <jrrivers at cumulusnetworks.com <mailto:jrrivers at cumulusnetworks.com>>, dev at lists.frrouting.org <mailto:dev at lists.frrouting.org>
>> 
>> 
>> I have built .deb packages for FRR for ubuntu 16.04.  Do we want to
>> put them up on the github page?  While we wait for more official
>> packaging?
>> 
>> donald
>> 
>> On Mon, Apr 3, 2017 at 2:47 PM, Martin Winter
>> <mwinter at opensourcerouting.org <mailto:mwinter at opensourcerouting.org>> wrote:
>>> We don’t have a official .deb or .rpm package yet.
>>> 
>>> I’m working with Silas (who is way better on deb packages than I am)
>>> to get debian packages fixed. (RPMs should be easier than debian packages)
>>> 
>>> - Martin
>>> 
>>> On 3 Apr 2017, at 7:24, JR Rivers wrote:
>>> 
>>> Any thoughts on RPM and DEB?
>>> 
>>> On Mon, Apr 3, 2017 at 7:13 AM, Jafar Al-Gharaibeh <jafar at atcorp.com <mailto:jafar at atcorp.com>> wrote:
>>>> 
>>>> Great work everyone, and thank you Martin for the update!
>>>> 
>>>> The link from your previous email: https://uappexplorer.com/app/frr.osr <https://uappexplorer.com/app/frr.osr>
>>>> 
>>>> shows only download option for arm64. Are the other architectures just
>>>> slow to show up?
>>>> 
>>>> Cheers,
>>>> Jafar
>>>> 
>>>> 
>>>> On 4/3/2017 4:40 AM, Martin Winter wrote:
>>>>> 
>>>>> The binary Snap Package for FRR 2.0 is now released in the snap store
>>>>> 
>>>>> Snap binary is currently available for amd64, i386, armhf and arm64 with
>>>>> ppc64el
>>>>> probably following in 1..2 days
>>>>> 
>>>>> I’ve also made the associated Snapcraft CI Testplan (and Store
>>>>> deployment) public as well
>>>>> (See https://ci1.netdef.org/browse/FRR-SNAP <https://ci1.netdef.org/browse/FRR-SNAP> and
>>>>> https://ci1.netdef.org/deploy/viewAllDeploymentProjects.action <https://ci1.netdef.org/deploy/viewAllDeploymentProjects.action> )
>>>>> 
>>>>> Enjoy,
>>>>> 
>>>>> - Martin
>>>>> 
>>>>> _______________________________________________
>>>>> dev mailing list
>>>>> dev at lists.frrouting.org <mailto:dev at lists.frrouting.org>
>>>>> https://lists.frrouting.org/listinfo/dev
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> dev mailing list
>>>> dev at lists.frrouting.org <mailto:dev at lists.frrouting.org>
>>>> https://lists.frrouting.org/listinfo/dev
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> dev mailing list
>>> dev at lists.frrouting.org <mailto:dev at lists.frrouting.org>
>>> https://lists.frrouting.org/listinfo/dev
>>> 
>> 
>> 
>> 
>> _______________________________________________
>> dev mailing list
>> dev at lists.frrouting.org <mailto:dev at lists.frrouting.org>
>> https://lists.frrouting.org/listinfo/dev
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20170404/cf43b237/attachment-0001.html>