Re: quick question regarding rabbitmq-server 3.8 EOL and Ubuntu 20.04 LTS

2022-07-15 Thread Alex Murray
Hi Josh,

The Ubuntu Security team endeavours to support the various packages in
each Ubuntu release for the lifetime of the Ubuntu release itself,
regardless of corresponding upstream project's release / support cycles.

In this case, even though upstream RabbitMQ will be ending support for
rabbitmq 3.8 on 31 July 2022, the Ubuntu Security team will then instead
look to backport patches from the upstream 3.9 (or 3.10 etc) releases to
the 3.8.2 release as shipped in Ubuntu 20.04 LTS as required.

Thanks,
Alex

On Wed, 2022-07-13 at 21:36:50 +, Josh Drake wrote:

> Hi,
>
> I had a quick question regarding the rabbitmq-server package in Ubuntu 20.04 
> LTS.  For background context, a rabbitmq support company we contracted seemed 
> certain that rabbitmq-server was going end of life at the end of July (likely 
> based on the info at https://www.rabbitmq.com/versions.html), and seemed 
> pretty sure that this also meant it would no longer receive backported 
> security patches on Ubuntu 20.04 LTS even though it is a LTS release.
>
> This didn't sound right to me, so my question is: Will the Ubuntu 20.04 LTS 
> version of rabbitmq-server continue to receive backported security patches 
> throughout the lifetime of Ubuntu 20.04 LTS, even after RabbitMQ's extended 
> support for 3.8 ends at the July 2022?
>
> Thanks,
> Josh Drake
> -- 
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Quick Question

2021-06-27 Thread Drew Howden Tech
Okay, thanks.

On Sunday, June 27, 2021, Colin Watson  wrote:

> [Please use more informative subject lines if possible.]
>
> On Sat, Jun 26, 2021 at 09:06:15PM -0400, Drew Howden Tech wrote:
> > Quick question: if I create a new package to resolve a 'needs-packaging'
> > bug, should I put my name in the maintainer field of the control file, or
> > 'Ubuntu Developers'?
>
> It doesn't matter much.  I lean towards your own.
>
> > Also, when patching/upgrading a package (to resolve a bug) should I
> > submit all the files (source package, resulting binary, etc.), or just
> > the debdiff/diff.gz?
>
> The debdiff (*not* just the .diff.gz - they aren't the same thing) is
> normally sufficient, although some reviewers may find it convenient to
> have a complete source package to download and perhaps sign/upload.  If
> the fix involves a new upstream version then you should submit the full
> source package.
>
> It isn't generally necessary to submit binaries unless a reviewer
> specifically asks for them, and they wouldn't be used anyway, although
> of course you should have test-built your fix and confirmed that it
> actually works.
>
> --
> Colin Watson (he/him)  [cjwat...@ubuntu.com]
>


-- 
Drew Howden
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Quick Question

2021-06-27 Thread Colin Watson
[Please use more informative subject lines if possible.]

On Sat, Jun 26, 2021 at 09:06:15PM -0400, Drew Howden Tech wrote:
> Quick question: if I create a new package to resolve a 'needs-packaging'
> bug, should I put my name in the maintainer field of the control file, or
> 'Ubuntu Developers'?

It doesn't matter much.  I lean towards your own.

> Also, when patching/upgrading a package (to resolve a bug) should I
> submit all the files (source package, resulting binary, etc.), or just
> the debdiff/diff.gz?

The debdiff (*not* just the .diff.gz - they aren't the same thing) is
normally sufficient, although some reviewers may find it convenient to
have a complete source package to download and perhaps sign/upload.  If
the fix involves a new upstream version then you should submit the full
source package.

It isn't generally necessary to submit binaries unless a reviewer
specifically asks for them, and they wouldn't be used anyway, although
of course you should have test-built your fix and confirmed that it
actually works.

-- 
Colin Watson (he/him)  [cjwat...@ubuntu.com]

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Quick Question

2021-06-26 Thread Drew Howden Tech
Quick question: if I create a new package to resolve a 'needs-packaging'
bug, should I put my name in the maintainer field of the control file, or
'Ubuntu Developers'? Also, when patching/upgrading a package (to resolve a
bug) should I submit all the files (source package, resulting binary,
etc.), or just the debdiff/diff.gz?

Drew Howden
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: quick question

2021-03-29 Thread Adam Carter
Hey,

After emailing you, I realized this may not be your responsibility and
you're focused on other stuff.

Who's the best person on your team to talk to about this?

Thanks in advance!
-Adam

On Thursday, March 25, 2021 at 6:02 AM, Adam Carter 
wrote:

> I wanted to check in and see if you got my note about display port
> standards?
>
> Thanks,
> -Adam
>
> On Monday, March 22, 2021 at 7:23 AM, Adam Carter 
> wrote:
>
>> I noticed you shared an article from En.Wikipedia.org when you talked
>> about display port standards, here:
>> lists.ubuntu.com/archives/ubuntu-quebec/2012-January/007826.html.
>>
>>
>> We recently published an article that discusses different display
>> standards, including High Definition Multimedia Interface (HDMI), Digital
>> Visual Interface (DVI), DisplayPort, and more.
>>
>>-
>>
>>We begin by reviewing why display standards are important
>>-
>>
>>Then, we describe the various types of cables.
>>-
>>
>>We end the article by looking at the elements to consider when
>>deciding which display cable is most appropriate for you.
>>
>>
>> We chose the sources we cited very carefully to ensure that we included
>> only the most reputable citations.
>>
>> Here's the article, if you're interested:
>> https://www.wiringo.com/everything-you-need-to-know-about-display-standards-hdmi-displayport-and-more.html
>>
>> Would you consider linking to our article?  I think some of your readers
>> would really find it helpful.
>>
>> Thank you for your time, and please let me know if you have any questions!
>>
>> Cheers,
>>
>> Adam
>>
>> --
>> Adam Carter
>> 5 Ross Rd
>> Durham, NH 03824
>>
>> BTW, if you didn't like getting this email, please reply with something
>> like "please don't email me anymore", and I'll make sure that we don't.
>>
>
>
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss