Re: Debian

On Fri, 19 Apr 2024 10:09:26 +0200 José Luis González González wrote: > On Fri, 19 Apr 2024 09:59:57 +0200 > José Luis González González wrote: > > > On Fri, 19 Apr 2024 09:39:02 +0200 > > José Luis González González wrote: > > > > > Good day, > > > > > > There's an issue with the dash

Re: Debian

You've written a lot of text here in a few mails, replying to yourself several times. This is not a positive pattern. On Fri, Apr 19, 2024 at 11:58:18AM +0200, José Luis González González wrote: >> There are similar issues with boa and dhttpd, and it seems Apache is going >> that way. > >nvi

Re: Debian

On Fri, 19 Apr 2024 10:09:26 +0200 José Luis González González wrote: > On Fri, 19 Apr 2024 09:59:57 +0200 > José Luis González González wrote: > > > On Fri, 19 Apr 2024 09:39:02 +0200 > > José Luis González González wrote: > > > > > Good day, > > > > > > There's an issue with the dash

Re: Debian

On Fri, 19 Apr 2024 09:59:57 +0200 José Luis González González wrote: > On Fri, 19 Apr 2024 09:39:02 +0200 > José Luis González González wrote: > > > Good day, > > > > There's an issue with the dash package and maintainer, and mutt as well. > > > > I even tried to reach dash maintainer

Re: [sylpheed:37255] Re: Debian 12 released with two RC bugs in Sylpheed

On Sun, 7 Apr 2024 15:18:57 +0200 José Luis González wrote: > I found the report now. It's #1036799. Yes, it looks like a temporary server issue. And you're sending via gmail now. But again, what do you expect a package maintainer to do? It's upstream where bugs get fixed. Your subject is

Re: Debian 12 released with two RC bugs in Sylpheed

In days of yore (Sun, 07 Apr 2024), José Luis González thus quoth: > Hi, > > Debian 12 was released with two Release Critical bugs I filed on May > 20th 2023 (#1036424 and #1036388) on Sylpheed about issues that I > found on stable, and remain, with Debian 12 released later on June 10th > 2023.

Re: Debian 12 released with two RC bugs in Sylpheed

On Sun, 7 Apr 2024 13:26:49 +0200 José Luis González wrote: > The maintainer accumulates a lot of bugs for the package, doesn't take > care about almost all, and when I filed a RC bug because the package > became unusable to me he downgraded severity to important claiming it > was just a Gmail

Bug#1056222: REGRESSIONS! Re: debian-edu-artwork 2.12.3-2~deb12u1 flagged for acceptance

On Fri, 24 Nov 2023 14:35:19 + Adam D Barratt wrote: Package: debian-edu-artwork Version: 2.12.3-2~deb12u1 Explanation: provide an Emerald theme based artwork for Debian Edu 12 This update causes some regressions (#1057815) - it modifies a conffile (/etc/plymouth/plymouthd.conf) -

Re: Debian Kernel version and ABI in respect of #1040901

On Fri, Jul 14, 2023 at 04:17:34PM +0200, Ben Hutchings wrote: > On Thu, 2023-07-13 at 21:16 +0200, Bastian Blank wrote: > [...] > > ## Proposed behaviour > > > > This tries to make sure everything apart from experimental gets new > > names and ABI on every upload. > > > > * experimental: > >

Re: Debian Kernel version and ABI in respect of #1040901

Hi On Thu, Jul 13, 2023 at 11:28:31PM +0300, Adrian Bunk wrote: > On Thu, Jul 13, 2023 at 09:16:15PM +0200, Bastian Blank wrote: > > ### NMU > > Can be easily added back by adding "bX" or so to the ABI. > That would be confusing, bX is naming convention for binNMUs in Debian > revisions. Right.

Re: Debian Kernel version and ABI in respect of #1040901

On Thu, 2023-07-13 at 21:16 +0200, Bastian Blank wrote: [...] > ## Proposed behaviour > > This tries to make sure everything apart from experimental gets new > names and ABI on every upload. > > * experimental: > Keep version 6.1~rc2-3~exp4, 6.1.2-3~exp4 > Keep ABI 6.1.0-0-arm64 [...]

Re: Debian Kernel version and ABI in respect of #1040901

On Thu, Jul 13, 2023 at 09:16:15PM +0200, Bastian Blank wrote: >... > ### NMU > > Can be easily added back by adding "bX" or so to the ABI. That would be confusing, bX is naming convention for binNMUs in Debian revisions. > ### BinNMU > > Is impossible to support. The version change requires

Re: Fwd: Re: Debian 8.3 Jessie KEYEXPIRED 11645052400

Set the clock on the affected system to a date before the key was expired. Example: # faketime 2019-05-01 apt update # faketime 2019-05-01 apt upgrade and so on ... Please note that 1024-bit DSA keys are no longer considered secure. Maybe better remove the MySQL stuff and add it back later.

Re: Fwd: Re: Debian 8.3 Jessie KEYEXPIRED 11645052400

On Wed, May 17, 2023 at 06:00:40PM -0300, Alan Homobono wrote: > ERROR: The certificate of "archive.debian.org" is not trusted. > ERROR: The certificate of "archive.debian.org" has expired. > > Any other suggestions? Then your options include, but are not limited to: 1. Downloading it on

Re: Fwd: Re: Debian 8.3 Jessie KEYEXPIRED 11645052400

Why and what time? Em 17/05/2023 18:46, Stephan Verbücheln escreveu: On Wed, 2023-05-17 at 18:00 -0300, Alan Homobono wrote: Any other suggestions? Have you tried setting the clock to the past (or using faketime)? Regards Stephan -- Atte., ALAN HOMOBONO Analista de TI - Suporte a

Re: Fwd: Re: Debian 8.3 Jessie KEYEXPIRED 11645052400

On Wed, 2023-05-17 at 18:00 -0300, Alan Homobono wrote: > Any other suggestions? Have you tried setting the clock to the past (or using faketime)? Regards Stephan signature.asc Description: This is a digitally signed message part

Fwd: Re: Debian 8.3 Jessie KEYEXPIRED 11645052400

Mensagem original Assunto: Re: Debian 8.3 Jessie KEYEXPIRED 11645052400 Data: 17/05/2023 17:46 De: Alan Homobono Para: Jonathan Wiltshire Hi Jonathan, Unsuccessful: # wget https://archive.debian.org/debian/pool/main/d/debian-archive-keyring/debian-archive-keyring_2017.5

Re: Debian 8.3 Jessie KEYEXPIRED 11645052400

On Sat, May 13, 2023 at 12:56:45AM -0300, Alan Homobono wrote: > Trying to upgrade Debian 8.3 Jessie to Debian 10.13 Buster, I continue > getting "KEYEXPIRED" error message after run apt-get update, even > renewing expired keys: # wget

Re: Debian 8.3 Jessie KEYEXPIRED 11645052400

Alan Homobono wrote on 13/05/2023 at 05:56:45+0200: > Trying to upgrade Debian 8.3 Jessie to Debian 10.13 Buster, I continue > getting "KEYEXPIRED" error message after run apt-get update, even renewing > expired keys: > > # apt-key list | grep -A 1 expired > pub 1024D/5072E1F5

Re: Debian 11.6 release date

On Mon, 2022-11-14 at 00:05 +0800, meida...@foxmail.com wrote: > I don't know much about Debian's messaging channels. It's been 2 > months since Debian 11.5 was released, and I was wondering if there > are any plans to release Debian 11.6 in the next few days? The Debian Release Team website

Re: debian-installer 20220917 via tpu

Hi, Ansgar (2022-09-20): > Cyril Brulebois writes: > > FTP Masters, please sync the installer from *tpu* to testing, once it's > > available there. > > > > dak copy-installer 20220917 -s bookworm-proposed-updates > > Done: > > +--- > | $ dak copy-installer 20220917 -s

Re: debian-installer 20220917 via tpu

Cyril Brulebois writes: > FTP Masters, please sync the installer from *tpu* to testing, once it's > available there. > > dak copy-installer 20220917 -s bookworm-proposed-updates Done: +--- | $ dak copy-installer 20220917 -s bookworm-proposed-updates | | Will copy installer version 20220917

Re: debian-archive-keyring, update for stretch, problem

Hi Adam, thanks for your reply! I have found the reason. I generated the signature using Debian/Testing (Bookworm), but the signature should be generated in the same environment, where it will be used (in this case Stretch). I regenerated signatures under stretch and everything works fine.

Re: debian-archive-keyring, update for stretch, problem

Hi, FWIW, I haven't touched d-a-k for a few years now, nor have I seen your package, so I'm largely guessing based on your provided text below. On Sat, 2022-03-12 at 21:52 +0100, Anton Gladky wrote: > I followed the README.maintainer. Added my key into team/members. > But then, when I just

Re: Debian 11 images for AWS m6i instances

Hi Giambattista, On Thu, Oct 14, 2021 at 10:32:50AM +0100, Giambattista Piranesi wrote: >I've noticed there are no official Debian 11 (Bullseye) images on AWS >compatible with m6i instances. > >Any chance to generate a m6-ready Debian 11 AMI?  What does it depend? The best place to ask about

Re: Debian 10.0 works with third generation Ryzen

Mick Ab wrote: > https://www.phoronix.com/scan.php?page=article=3900x-linux-distros=1 > > The above article shows that Debian 10.0 works okay with a third generation > Ryzen CPU. > > I understood that there were problems with Buster using third generation > Ryzen. > > Has this problem been

Re: Debian Linux kernel uploads

Hi, Hector Oron writes: > I would like to support Debian Linux kernel team by doing kernel > package uploads. Related to Linux uploads: I've added an exception to allow source-only uploads to NEW for src:linux. Feel free to try. Ansgar

Re: Debian Linux kernel uploads

Hi, On Sun, Oct 20, 2019 at 02:27:21PM +0100, Ben Hutchings wrote: > On Sun, 2019-10-20 at 13:58 +0200, Hector Oron wrote: > > Hello, > > > > I would like to support Debian Linux kernel team by doing kernel > > package uploads. > > > > Initially, I would like to attempt timely (weekly or

Re: Debian Linux kernel uploads

On Sun, 2019-10-20 at 13:58 +0200, Hector Oron wrote: > Hello, > > I would like to support Debian Linux kernel team by doing kernel > package uploads. > > Initially, I would like to attempt timely (weekly or bi-weekly, it > has not been discussed yet) updates for Debian Linux kernel package

Re: [debian-mysql] Bug#939866: Bug#939866: mariadb-server-10.1: replication hangs in state "Slave_IO_Running: Preparing" after upgrade from 10.1.38 to 10.1.41

la 14. syysk. 2019 klo 16.57 Adam D. Barratt (a...@adam-barratt.org.uk) kirjoitti: > > On Fri, 2019-09-13 at 21:10 +0300, Otto Kekäläinen wrote: > > To clarify, 10.3.18 has been uploaded to Debian unstable. Issue is > > still open for Buster and Stretch. > > Is there a likely ETA for when this

Re: [debian-mysql] Bug#939866: Bug#939866: mariadb-server-10.1: replication hangs in state "Slave_IO_Running: Preparing" after upgrade from 10.1.38 to 10.1.41

On Fri, 2019-09-13 at 21:10 +0300, Otto Kekäläinen wrote: > To clarify, 10.3.18 has been uploaded to Debian unstable. Issue is > still open for Buster and Stretch. Is there a likely ETA for when this might be resolvable? If you could prepare (preferably targeted) updates via the usual p-u path

Re: debian squeeze repository

On Tue, Feb 19, 2019 at 06:11:27PM +, miel...@t-online.de wrote: > > Ladies and gentlemen, > > I tried to update a debian squeeze OS, with a > /etc/apt/sources.list Debian 6 "Squeeze" stopped receiving security and errata updates in 2014. You should upgrade to a supported release as soon as

Re: [debian-mysql] Heads up to release team about MariadB 10.3

On 18/01/2019 10:59, Olaf van der Spek wrote: > On Thu, Jan 17, 2019 at 3:37 PM Emilio Pozuelo Monfort > wrote: >> That was with the old libdbd-mariadb-perl, and the new one (which was fine) >> wasn't migrating due to a build-dep on the new mysql-defaults, which was >> blocked >> on

Re: [debian-mysql] Heads up to release team about MariadB 10.3

On Thu, Jan 17, 2019 at 3:37 PM Emilio Pozuelo Monfort wrote: > That was with the old libdbd-mariadb-perl, and the new one (which was fine) > wasn't migrating due to a build-dep on the new mysql-defaults, which was > blocked > on mariadb-10.3, blocked on libdbd-mariadb-perl... I cheated a bit

Re: Debian/MIPSeb: proposal to drop mipseb port?

I'm still actively using it for a couple of different devices. Thanks, Brock On Sat, Jul 7, 2018 at 9:34 AM YunQiang Su wrote: > Hi, folks, > due to lack of enough man power and build machines for 3 mips* port at > the same time, I think that now it is time for us to have a talk about >

Re: Debian/MIPSeb: proposal to drop mipseb port?

Hi! You should ask in a more public forum rather than on Debian mailing lists if you want to know about potential users. Adrian > On Jul 7, 2018, at 8:31 AM, YunQiang Su wrote: > > Hi, folks, > due to lack of enough man power and build machines for 3 mips* port at > the same time, I think

Processed: Re: [debian-mysql] Bug#868666:

Processing control commands: > tags 865093 -moreinfo Bug #865093 [release.debian.org] stretch-pu: package mariadb-10.1/10.1.25-0+deb9u1 Removed tag(s) moreinfo. -- 865093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865093 868666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868666

Re: Debian 9.0

sare...@att.net: > There is something wrong with the Debian 9 iso's. I downloaded the Debian 9.0 > dvd iso and put it on a flash drive. It boots ,but when I try to install it a > dialog pups up asking for a cd. As you know 2 gb will not fit on a CD. I > re-downloaded and tried to install Debian

Re: d-i-netboot-images package outdated (was Re: Debian Installer Stretch RC 5 release)

Andrew M.A. Cater (2017-06-14): > Seeing the post on PXE for UEFI on planet.debian.org and noting that > you're planning another d-i release. Please mention a direct URL, planet has a volatile content… Maybe you're referring to this?

Re: d-i-netboot-images package outdated (was Re: Debian Installer Stretch RC 5 release)

On Wed, Jun 14, 2017 at 08:45:47AM +0200, Cyril Brulebois wrote: > Holger Levsen (2017-06-13): > > On Tue, Jun 13, 2017 at 10:19:17AM +0200, Cyril Brulebois wrote: > > > Known bugs in this release > > > == > > [...] > > > See the errata[2] for

Re: d-i-netboot-images package outdated (was Re: Debian Installer Stretch RC 5 release)

On Wed, Jun 14, 2017 at 08:45:47AM +0200, Cyril Brulebois wrote: > > Shall I file an RC bug to make the problem more visible and known? > As mentioned in the announce: We're doing another d-i upload for the > release anyway. til then, having up2date debian-installer-netboot-images packages

Re: d-i-netboot-images package outdated (was Re: Debian Installer Stretch RC 5 release)

Holger Levsen (2017-06-13): > On Tue, Jun 13, 2017 at 10:19:17AM +0200, Cyril Brulebois wrote: > > Known bugs in this release > > == > [...] > > See the errata[2] for details and a full list of known issues. > >

Re: d-i-netboot-images package outdated (was Re: Debian Installer Stretch RC 5 release)

On Tue, Jun 13, 2017 at 10:08:44AM +, Holger Levsen wrote: > On Tue, Jun 13, 2017 at 10:19:17AM +0200, Cyril Brulebois wrote: > > Known bugs in this release > > == > [...] > > See the errata[2] for details and a full list of known issues. > >

d-i-netboot-images package outdated (was Re: Debian Installer Stretch RC 5 release)

On Tue, Jun 13, 2017 at 10:19:17AM +0200, Cyril Brulebois wrote: > Known bugs in this release > == [...] > See the errata[2] for details and a full list of known issues. https://tracker.debian.org/pkg/debian-installer-netboot-images hasn't seen an update in a while (and

Re: [debian-mysql] Fixing the jessie->stretch upgrade path

On Fri, May 12, 2017, at 17:30, Norvald H. Ryeng wrote: > On Fri, 12 May 2017 14:09:02 +0200 > Ondřej Surý wrote: > > > On Fri, May 12, 2017, at 13:31, Norvald H. Ryeng wrote: > > > On Fri, 12 May 2017 11:26:13 +0200 > > > Ondřej Surý wrote: > > > > > > >

Re: [debian-mysql] Fixing the jessie->stretch upgrade path

On Fri, 12 May 2017 14:09:02 +0200 Ondřej Surý wrote: > On Fri, May 12, 2017, at 13:31, Norvald H. Ryeng wrote: > > On Fri, 12 May 2017 11:26:13 +0200 > > Ondřej Surý wrote: > > > > > Dear release team and fellow MySQL/MariaDB maintainers, > > > > > > the

Re: [debian-mysql] Fixing the jessie->stretch upgrade path

On Fri, 12 May 2017 11:26:13 +0200 Ondřej Surý wrote: > Dear release team and fellow MySQL/MariaDB maintainers, > > the situation in stretch in regards to clean upgrade path from jessie > is a little bit unfortunate. It works for most cases when something > depends on

Re: [debian-mysql] Fixing the jessie->stretch upgrade path

Hello! 2017-05-12 12:26 GMT+03:00 Ondřej Surý : > Therefore I am proposing a one time fix specifically targeted at > stretch. I would like to prepare 'mysql-transitional' package that will > create a couple of dummy/transitional packages structured like this: > > mysql-server

Re: [debian-mysql] Fixing the jessie->stretch upgrade path

On Fri, May 12, 2017, at 13:31, Norvald H. Ryeng wrote: > On Fri, 12 May 2017 11:26:13 +0200 > Ondřej Surý wrote: > > > Dear release team and fellow MySQL/MariaDB maintainers, > > > > the situation in stretch in regards to clean upgrade path from jessie > > is a little bit

Re: [debian-mysql] Fixing the jessie->stretch upgrade path

On Fri, 12 May 2017 11:26:13 +0200 Ondřej Surý wrote: > Dear release team and fellow MySQL/MariaDB maintainers, > > the situation in stretch in regards to clean upgrade path from jessie > is a little bit unfortunate. It works for most cases when something > depends on

Re: [debian-mysql] Fixing the jessie->stretch upgrade path

Hi Ondřej, Thank you for working on this. On Fri, May 12, 2017 at 11:26:13AM +0200, Ondřej Surý wrote: > Therefore I am proposing a one time fix specifically targeted at > stretch. I would like to prepare 'mysql-transitional' package that will > create a couple of dummy/transitional packages

Processed (with 2 errors): Re: [debian-mysql] Bug#855163: Missing mariadb-plugin-tokudb binary package on amd64

Processing control commands: > reassign -1 release.debian.org Bug #855163 [src:mariadb-10.1] Missing mariadb-plugin-tokudb binary package on amd64 Bug reassigned from package 'src:mariadb-10.1' to 'release.debian.org'. No longer marked as found in versions mariadb-10.1/10.1.21-5. Ignoring

Re: [debian-www] Please add mips64el to stretch and add pages for buster

On Mon, Feb 6, 2017 at 5:45 AM, Niels Thykier wrote: > Here are two updated patches. Committed. Removed some trailing whitespace and moved your name to Patch-by. -- bye, pabs https://wiki.debian.org/PaulWise

Re: [debian-www] Please add mips64el to stretch and add pages for buster

Emilio Pozuelo Monfort: > On 05/02/17 20:47, Niels Thykier wrote: >> Hi, >> >> I have made two patches for: >> * Adding mips64el as a release architecture for stretch > > powerpc needs to be commented out. > > Cheers, > Emilio > > Indeed, thanks for catching that. Here are two updated

Re: [debian-www] Please add mips64el to stretch and add pages for buster

On 05/02/17 20:47, Niels Thykier wrote: > Hi, > > I have made two patches for: > * Adding mips64el as a release architecture for stretch powerpc needs to be commented out. Cheers, Emilio > * Adding pages for buster under www.d.o/releases/buster >(also adds a version for stretch to fix a

Re: Debian-8.6

On Sun, 15 Jan 2017 22:05:53 + (UTC) wrote: > Why is Firefox 45 esr so buggy and freezes up in Debian 8.6 ? No add > ons or extensions are installed. Iceweazel was bad, but the outdated > Firefox makes Debian unusable when using the internet. Debian kde and > gnome notify me

Re: Debian 8.7 and Tomcat 8.5 support

dpawluk: > Hello, > I would like to ask, if Debian 8.7 release supports Apache 8.5.x? > Hi, Debian 8.7 will /not/ have Apache Tomcat 8.5, but it is available from jessie-backports (which has 8.5.9-1~bpo8+1 at the moment). Thanks, ~Niels

Re: [debian-mysql] getting mysql-5.6 out of stretch

On 27/10/16 11:33, Otto Kekäläinen wrote: > Hello! > > We have not filed a mass bug report against packages regarding > transitioning to default-mysql-*. Would you like to file it? > I made a Lintian rule that is now in use, but a mass bug filing would > speed things up. Yes, but please send a

Re: [debian-mysql] getting mysql-5.6 out of stretch

On Thu, 27 Oct 2016, Otto Kekäläinen wrote: > Hello! > > We have not filed a mass bug report against packages regarding > transitioning to default-mysql-*. Would you like to file it? > I made a Lintian rule that is now in use, but a mass bug filing would > speed things up. Isn't that a little

Re: [debian-mysql] getting mysql-5.6 out of stretch

Hello! We have not filed a mass bug report against packages regarding transitioning to default-mysql-*. Would you like to file it? I made a Lintian rule that is now in use, but a mass bug filing would speed things up.

Re: [debian-mysql] final decision about MySQL r-deps needed / cleaning up the MySQL mess

Hi, On Tue, Oct 18, 2016 at 01:17:27PM +0300, Otto Kekäläinen wrote: > 2016-10-18 11:38 GMT+03:00 Rene Engelhard : > > Simple: Because LO uses the C++ bindings and not the C bindings? If you > > mean why I don't build mysql-connector-c++ against mariadb, see my initial > > mail.

Re: [debian-mysql] final decision about MySQL r-deps needed / cleaning up the MySQL mess

2016-10-18 11:38 GMT+03:00 Rene Engelhard : > Simple: Because LO uses the C++ bindings and not the C bindings? If you > mean why I don't build mysql-connector-c++ against mariadb, see my initial > mail. Newer versions of it do not build with it. (the version in sid is > ooold.)

Re: [debian-mysql] final decision about MySQL r-deps needed / cleaning up the MySQL mess

Hello! 2016-10-17 22:01 GMT+03:00 Rene Engelhard : > This means I'll orphan mysql-connector-c++ (well, remove myself from > Uploaders:, > which makes it having no Uploader at all). Dmitry, if you want/need it > for mysql-connector-c++ feel free to add yourself and upload 1.1.7

Re: [debian-mysql] final decision about MySQL r-deps needed / cleaning up the MySQL mess

Hi, On Tue, Oct 18, 2016 at 11:28:32AM +0300, Otto Kekäläinen wrote: > 2016-10-17 22:01 GMT+03:00 Rene Engelhard : > > This means I'll orphan mysql-connector-c++ (well, remove myself from > > Uploaders:, > > which makes it having no Uploader at all). Dmitry, if you want/need it

Re: Debian Archive Signing Key

Sent from my Samsung Galaxy smartphone. Original message From: "Jp.vanzyl" Date: 18/09/2016 21:07 (GMT+02:00) To: Jvz22 , Jvz4773 , Jvz4773 , Jvz22 Subject:

Re: [debian-mysql] Introducing default-mysql-* metapackages

Hi, On Tue, Aug 16, 2016 at 11:36:15AM +0300, Otto Kekäläinen wrote: > Yes, this scheme is very flexible and in cases like > > mysql-connector-c++ the package can depend explicitly on the MySQL > > package and not the default package. OK. > > Or we keep a

Re: [debian-mysql] Introducing default-mysql-* metapackages

Hello! 2016-08-16 7:44 GMT+03:00 Rene Engelhard : > On Sun, Jul 10, 2016 at 05:22:22PM +0300, Otto Kekäläinen wrote: >> Hello maintainers of packages that depend in MySQL/MariaDB! > > Not everyone is required to read -devel. Mailing them where they read > it (and be it Cc'ing

Re: [Debian-ports-devel] [d...@debian.org: GCC 6 defaults change, including icu 57 and boost 1.61 transitions]

On 08/03/2016 10:54 PM, Aurelien Jarno wrote: > FYI as it will also have to to be done on the debian-ports architectures. > Note that the upload of gcc-defaults defaulting to gcc-6 just happened. I think this is really a bit of a short notice, but I will have to bite the bullet and fix all the

Re: [Debian-med-packaging] migration exception for mhap

On 2016-07-23 23:14, Afif Elghraoui wrote: على السبت 23 تـمـوز 2016 ‫06:56، كتب Jonathan Wiltshire: On 2016-07-23 09:22, Afif Elghraoui wrote: The latest upstream release of the mhap package adds a new dependency on libssw-java, which is not available for i386. The testing excuses page for

Re: [Debian-med-packaging] migration exception for mhap

على السبت 23 تـمـوز 2016 ‫06:56، كتب Jonathan Wiltshire: > On 2016-07-23 09:22, Afif Elghraoui wrote: >> The latest upstream release of the mhap package adds a new dependency >> on >> libssw-java, which is not available for i386. The testing excuses page >> for mhap currently says: >> >> 8 days

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

Excerpts from Otto Kekäläinen's message of 2016-07-03 12:46:29 +0100: > > 3. libmysqlclient.so.18 > > Here theres's no concensus yet within the pkg-mysql-maint team on this one. > And IMO, there won't be one until MariaDB accepts that they've created a forked library that is API-incompatible

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

On 2016-07-06 09:54, Otto Kekäläinen wrote: > 2016-07-05 19:52 GMT+03:00 Robie Basak : >> PROPOSAL B > > The whole pkg-mysql-maint team is behind the proposal Robie now wrote > about. We have been discussing actively and engineering it during the > last two days. It was

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

2016-07-05 19:52 GMT+03:00 Robie Basak : > PROPOSAL B The whole pkg-mysql-maint team is behind the proposal Robie now wrote about. We have been discussing actively and engineering it during the last two days. It was also one of the topics discussed at the MariaDB/MySQL Bof

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

On Tue, Jul 05, 2016 at 11:41:15AM +0200, Jonathan Wiltshire wrote: > > I suggest we extend the mysql-defaults source package to provide a > > real default-mysqlclient-dev metapackage, which other packages can > > build depend on, using versions if needed (just as default-jdk does). > > Yes. > >

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

2016-07-02 17:53 GMT+03:00 Otto Kekäläinen: > This is modeled after how default-jdk or default-mta works. Actually default-jdk is a real metapackage, while default-mta is a pure virtual package. I am not sure which way to pick here now.

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

2016-07-02 17:53 GMT+03:00 Otto Kekäläinen : > This is modeled after how default-jdk or default-mta works. Actually default-jdk is a real metapackage, while default-mta is a pure virtual package. I am not sure which way to pick here now.

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

Hello! What does the release team think of introducing new purely virtual packages named default-mysq-*, which are provided only by mariadb-* packages? This is modeled after how default-jdk or default-mta works. In code if would look like this:

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

On 24/06/16 20:05, Robie Basak wrote: > On Fri, Jun 24, 2016 at 07:53:56PM +0200, Julien Cristau wrote: >> Please don't use virtual-foo for non-virtual packages, that way lies >> madness and confusion and despair :) > > OK, but does anyone have any objection to the principle of my > suggestion,

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

On Fri, Jun 24, 2016 at 07:53:56PM +0200, Julien Cristau wrote: > Please don't use virtual-foo for non-virtual packages, that way lies > madness and confusion and despair :) OK, but does anyone have any objection to the principle of my suggestion, even if we must use a different name?

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

On Fri, Jun 24, 2016 at 14:55:34 +0100, Robie Basak wrote: > On Wed, Jun 01, 2016 at 07:03:42PM +0200, Andreas Beckmann wrote: > > I prepared a prototype for a separate mysql-common package (and > > default-* packages) at > > git://git.debian.org/git/users/anbe/tmp/mysql-defaults.git > > but so

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

On Wed, Jun 01, 2016 at 07:03:42PM +0200, Andreas Beckmann wrote: > I prepared a prototype for a separate mysql-common package (and > default-* packages) at > git://git.debian.org/git/users/anbe/tmp/mysql-defaults.git > but so far nobody had time to review it. A thought from Norvald. Do we really

Re: Debian Jessie - Incorrect permissions on /bin directory

On 02/03/16 12:46, Yves-Alexis Perez wrote: > On mer., 2016-02-03 at 14:37 +0100, Cyril Brulebois wrote: >> [Context: packages shipping /bin with “funny” permissions, seen in stable.] >> >> Yves-Alexis Perez (2016-02-03): >>> >>> On mar., 2016-02-02 at 17:16 +0100, Cyril

Re: Debian Jessie - Incorrect permissions on /bin directory

* Yves-Alexis Perez , 2016-03-02, 12:46: I did a quick check on a local mirror (which might be incomplete), and found three packages with errors: dpkg -c debian/pool/main/s/sed/sed_4.2.2-4+b1_amd64.deb |grep bin/$ drwxrwxr-x root/root 0 2014-11-08 19:28 ./bin/ dpkg

Re: Debian Jessie - Incorrect permissions on /bin directory

On mer., 2016-02-03 at 14:37 +0100, Cyril Brulebois wrote: > [Context: packages shipping /bin with “funny” permissions, seen in stable.] > > Yves-Alexis Perez (2016-02-03): > > > > On mar., 2016-02-02 at 17:16 +0100, Cyril Brulebois wrote: > > > > > > I didn't check the

Re: Debian Jessie - Incorrect permissions on /bin directory

[Context: packages shipping /bin with “funny” permissions, seen in stable.] Yves-Alexis Perez (2016-02-03): > On mar., 2016-02-02 at 17:16 +0100, Cyril Brulebois wrote: > > I didn't check the whole archive, but doing so might be interesting. > > I did a quick check on a local

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

Hi, jumping in here, cause I think this one is really uncalled for: On Wed, Jan 27, 2016 at 08:30:09PM +, Steven Chamberlain wrote: > And apart from sponsoring Debian packaging work, Oracle seems > conspicuously missing from: > http://debconf16.debconf.org/sponsors.html So is about

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

Norvald H. Ryeng wrote: > >Norvald H. Ryeng wrote: > >>Tell us exactly what you want, in detail. If you don't then I don't > >>think your position is reasonable. > > I don't recognize those words, and it's not in the style I usually express > myself. Are you paraphrasing? Sorry, that was Robie

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

On Wed, 27 Jan 2016 21:30:09 +0100, Steven Chamberlain wrote: And apart from sponsoring Debian packaging work, Oracle seems conspicuously missing from: http://debconf16.debconf.org/sponsors.html http://debconf15.debconf.org/ https://www.debian.org/mirror/sponsors

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

Excerpts from Steven Chamberlain's message of 2016-01-27 12:30:09 -0800: > I'll try to make this my last intervention in this thread. Because > it's not my decision, or area of responsibility, and I likely won't be > one of the people having to do the work when a decision is made, but... > I

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

Hi Niels, Thank you for your considered response. On Tue, Jan 26, 2016 at 11:50:08PM +, Niels Thykier wrote: > I do not feel the listed options accurately reflect the issues / > concerns in play. As *I see it*, these are the options: > > 1) Default to MySQL with MariaDB also available

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

Hi Otto, I agree entirely with the principles you presented, and thank you for making them. You also made some technical arguments (and I appreciate that they are technical and thus valuable and actionable), which I would like to rebut. On Wed, Jan 27, 2016 at 12:45:59AM +0200, Otto Kekäläinen

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

Robie Basak: > Hi Niels, > > Thank you for your considered response. > > On Tue, Jan 26, 2016 at 11:50:08PM +, Niels Thykier wrote: >> I do not feel the listed options accurately reflect the issues / >> concerns in play. As *I see it*, these are the options: >> >> 1) Default to MySQL with

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

Excerpts from Holger Levsen's message of 2016-01-26 02:45:32 -0800: > Hi, > > On Dienstag, 26. Januar 2016, Clint Byrum wrote: > > However, I have confidence that our friends in the MySQL engineering > > team can frame the loss of the last foothold for MySQL in Linux distros > > as a direct path

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

I'll try to make this my last intervention in this thread. Because it's not my decision, or area of responsibility, and I likely won't be one of the people having to do the work when a decision is made, but... Clint Byrum wrote: > most of these CVE's would remain fully undisclosed and unfixed in

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

On Tue, 26 Jan 2016 23:45:59 +0100, Otto Kekäläinen wrote: Examples of technical arguments I'd prefer to use instead of general disgust of Oracle arguments: - Quality: mysql-5.6 has 135 open bugs despite never being part of a Debian release and thus having exposure to the big

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

Hi, On Dienstag, 26. Januar 2016, Clint Byrum wrote: > However, I have confidence that our friends in the MySQL engineering > team can frame the loss of the last foothold for MySQL in Linux distros > as a direct path toward _less_ money for Oracle. why do you think so? I mean, doesn't less Mysql

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

> * Summary of options and selection status > > My original request for a decision proposed one of the following > options, which I think we all agree are the only options available: > > 1) We carry and ship both, which I believe is the preference of the > Debian MySQL Maintainers team by default

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

/ Stockholm / Vienna Subject: Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB ... >> I was wondering why after the 2016-01-19 announcement, there is still no >> patched mysql-5.5 in jessie or wheezy; and also why mariadb was only >> just patc

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

Hello! As the principal maintainer of MariaDB server packaging in Debian I should probably also chip in here. First of all I'd like to thank Robie for the summary. Robie is correct in pointing out that the release and security team's arguments are somewhat based on disgust for Oracle and less on

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

Hello! 2016-01-26 2:48 GMT+02:00 Steven Chamberlain : > I was wondering why after the 2016-01-19 announcement, there is still no > patched mysql-5.5 in jessie or wheezy; and also why mariadb was only > just patched today. Debian is typically much faster than this at >

  1   2   3   4   5   >