Hello!
Is there a delay between when I upload a new package and when it shows
up on the web site? I just uploaded a new package but I don't see it in "My
Packages".
Thanks very much,
Aaron Boxer
On Fri, Apr 10, 2020 at 1:10 PM Andrey Rahmatullin wrote:
> On Fri, Apr 10, 2020 at 12:55:32PM -0400, Aaron Boxer wrote:
> > Hello!
> >
> > Is there a delay between when I upload a new package and when it shows
> > up on the web site? I just uploaded a new package
wnload the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/g/grok-jpeg2000/grok-jpeg2000_5.1.0-0.dsc
Changes since the last upload:
* Initial release
Many Thanks!
Aaron Boxer
:
dget -x
https://mentors.debian.net/debian/pool/main/g/grok-jpeg2000/grok-jpeg2000_6.0.0-1.dsc
Changes since the last upload:
* Initial release. Closes: #954265
Regards,
Aaron Boxer
Hello!,
I have created a new package for a library (grok) with the same name as an
existing debian package, so I have named my package grok-jpeg2000, because
it is an image coded for the JPEG 2000 standard. Will this mismatch between
my library name and my package name be a problem getting the pac
On Wed, Apr 22, 2020 at 12:22 PM Wookey wrote:
> On 2020-04-22 11:13 -0400, Aaron Boxer wrote:
> > Hello!,
> >
> > I have created a new package for a library (grok) with the same name as
> an
> > existing debian package, so I have named my package grok-jpeg2000
Hello,
My library can use SIMD vector operations such as AVX2 if available on
system.
What is the best way of managing this ? For simplicity, I could create two
packages, one with all SIMD disabled, and one assuming AVX2. What's the
standard way of approaching this?
Also, I tried logging onto #de
On Sat, Apr 25, 2020 at 5:10 PM Andrey Rahmatullin wrote:
> On Sat, Apr 25, 2020 at 02:53:51PM -0400, Aaron Boxer wrote:
> > Hello,
> > My library can use SIMD vector operations such as AVX2 if available on
> > system.
> > What is the best way of managing this ?
>
On Sat, Apr 25, 2020 at 10:49 PM Charles Plessy wrote:
> Le Sat, Apr 25, 2020 at 02:53:51PM -0400, Aaron Boxer a écrit :
> >
> > My library can use SIMD vector operations such as AVX2 if available on
> > system.
> > What is the best way of managing this ?
>
> Hel
libgrokj2k
Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/libg/libgrokj2k/libgrokj2k_7.1.0-1.dsc
Changes since the last upload:
* Initial release. Closes: #954265
Thank You!
--
Aaron Boxer
Hi Adam,
Thanks a lot for testing this I've fixed the build error - please try it
again when you have time.
Cheers,
Aaron
On Fri, May 1, 2020 at 7:21 PM Adam Borowski wrote:
> On Wed, Apr 29, 2020 at 04:53:38PM -0400, Aaron Boxer wrote:
> > * Package name: libgrokj2k
>
>
> Hi!
> Sorry for the delay.
>
> There's one problem left: the .symbols file for libgrokj2k1 declares a
> dependency on libgrokj2k (rather than 2k1). Please bump it a year ahead :)
>
Thanks! that was the last lintian warning :) All green now.
Hello,
My package libgrokj2k is currently in bookworm testing. I have a small
patch that fixes a serious bug in the encoder. How may I get this into
bookworm testing before release ?
The current version in testing is v10.0.5. I have created a patch branch
v10.0.5.1
with the library version still
Hi Folks,
I have successfully created a patched version of libgrokj2k to fix a serious
encoder bug.
https://mentors.debian.net/package/libgrokj2k/
Help uploading this to unstable would be greatly appreciated !
Thanks,
Aaron
ing, then 10.0.5-2 becomes your version
> string).
>
> Not sure if this will get migrated though due to testing freeze - might
> need special intervention to get in.
>
>
> Thomas
>
>
> On 3/20/23 09:12, Aaron Boxer wrote:
>
> Hello,
>
> My package libgrokj2k
Thanks, Santiago. How do I contact the release team to ask about unblock ?
On Mon, Mar 20, 2023 at 11:17 AM Santiago Ruano Rincón <
santiag...@riseup.net> wrote:
> El 20/03/23 a las 11:08, Aaron Boxer escribió:
> > Hi Folks,
> >
> > I have successfully created a patch
Hi Hilmar,
Thanks very much, I have submitted a bug report.
Aaron
On Mon, Mar 20, 2023 at 11:43 AM Preuße, Hilmar wrote:
> On 20.03.2023 16:38, Aaron Boxer wrote:
>
> Hi Aaron,
>
> are you subscribed to debian-devel-annou...@lists.debian.org ?
>
> > Thanks, Santia
Dear Mentors.
I submitted the libgrokj2k package over 6 months ago, and I am not clear on
its current status.
It has been accepted into the NEW repo, and has been released to UNSTABLE.
Are there any other steps needed before it is fully upstream ?
I have had questions from one user about when this
Thanks, guys!
On Wed, Dec 23, 2020 at 9:57 AM Adam Borowski wrote:
> On Wed, Dec 23, 2020 at 09:44:18AM -0500, Aaron Boxer wrote:
> > Dear Mentors.
> > I submitted the libgrokj2k package over 6 months ago, and I am not clear
> on
> > its current status.
> > It
Hi,
I have some questions about a lintian warning I am getting from my package.
It complains that the NAME section of the man page can't be parsed.
Here is how the section appears in my man page:
NAME
grk_compress — compresses images to JPEG 2000 format
Note: I generate the man page from m
On Wed, Dec 23, 2020 at 11:42 AM The Wanderer wrote:
> On 2020-12-23 at 11:25, Aaron Boxer wrote:
>
> > Hi,
> > I have some questions about a lintian warning I am getting from my
> package.
> > It complains that the NAME section of the man page can't be par
On Wed, Dec 23, 2020 at 12:56 PM Aaron Boxer wrote:
>
>
> On Wed, Dec 23, 2020 at 11:42 AM The Wanderer
> wrote:
>
>> On 2020-12-23 at 11:25, Aaron Boxer wrote:
>>
>> > Hi,
>> > I have some questions about a lintian warning I am getting from m
On Wed, Dec 23, 2020 at 1:36 PM The Wanderer wrote:
> On 2020-12-23 at 13:04, Aaron Boxer wrote:
>
> > On Wed, Dec 23, 2020 at 11:42 AM The Wanderer
> > wrote:
> >
> >> On 2020-12-23 at 11:25, Aaron Boxer wrote:
> >>
> >>> Hi,
> >&
On Wed, Dec 23, 2020 at 1:36 PM Robin Gustafsson wrote:
> Hi Aaron,
>
> > How can I get more insight into the problem?
>
> Lintian's explanation for bad-whatis-entry [1] mentions that it's
> "lexgrog" that fails to parse your header. (Looking at Lintian source
> [2], it's indeed just running lexg
> > I have had questions from one user about when this package will be
>> > available.
>>
>> As Andrey just mentioned, a new upload was needed. You've just gave us
>> 7.6.2-1, which I've sponsored. So that's done, and it should migrate to
>> testing shortly.
>>
>
>> > For more info, my latest upd
n has been in Testing
as of January 7th.
Thanks very much,
Aaron
On Wed, Dec 23, 2020 at 9:44 AM Aaron Boxer wrote:
> Dear Mentors.
> I submitted the libgrokj2k package over 6 months ago, and I am not clear
> on its current status.
> It has been accepted into the NEW repo, and has
On Wed, Jan 27, 2021 at 7:55 PM Jeremy Stanley wrote:
> On 2021-01-27 16:31:14 -0500 (-0500), Aaron Boxer wrote:
> > Is there a way of expediting my package's passage into Debian? It
> > has been at least 7 months since I first submitted. I currently
> > maintain m
Dear Mentors,
Last night I discovered a severe bug in my encoder. The bug affects lossy
compression of monochrome images, a very large class of images. The bug
causes the output pixels to be set to 0, which is pretty serious.
I realize there is a freeze on new packages leading up to Bullseye relea
Forgot to mention: this is the package in question:
https://tracker.debian.org/pkg/libgrokj2k
On Tue, Feb 2, 2021 at 9:03 AM Aaron Boxer wrote:
> Dear Mentors,
> Last night I discovered a severe bug in my encoder. The bug affects lossy
> compression of monochrome images, a very large
I've uploaded a new 7.6.6 version to the mentors site with a fix for this
issue
https://mentors.debian.net/package/libgrokj2k/
I see there isn't a soft freeze until Feb 12, so hopefully this can be
migrated before that deadline.
Thanks!
Aaron
On Tue, Feb 2, 2021 at 9:03 AM Aaron Bo
On Tue, Feb 2, 2021 at 3:22 PM Aaron Boxer wrote:
> I've uploaded a new 7.6.6 version to the mentors site with a fix for this
> issue
>
> https://mentors.debian.net/package/libgrokj2k/
>
> I see there isn't a soft freeze until Feb 12, so hopefully this can be
>
never mind :) as there are no packages at the moment, there is no link.
sorry for the noise,
Aaron
On Tue, Feb 2, 2021 at 6:53 PM Aaron Boxer wrote:
>
> On Tue, Feb 2, 2021 at 3:22 PM Aaron Boxer wrote:
>
>> I've uploaded a new 7.6.6 version to the mentors site with a f
Hi Guys,
My package is slated for auto removal for bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983775
I have just uploaded a patch for this bug to the mentors site,
can this please be pushed to testing ?
Thanks!
Aaron
On Wed, Mar 10, 2021 at 8:13 PM Adam Borowski wrote:
> On Wed, Mar 10, 2021 at 08:49:52AM -0500, Aaron Boxer wrote:
> > Hi Guys,
> > My package is slated for auto removal for bug
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983775
> >
> > I have just upl
Hello,
I have what I hope is a fix for the build failure on i386.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985116
Version 7.6.6-3 is uploaded to the mentors site,
and should be available shortly. Could someone please
push this to testing when they have time ?
Thanks!
Aaron
On Tue, Mar 16, 2021 at 1:32 PM Andrey Rahmatullin wrote:
> On Tue, Mar 16, 2021 at 01:05:11PM -0400, Aaron Boxer wrote:
> > Hello,
> > I have what I hope is a fix for the build failure on i386.
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985116
> >
> &g
On Tue, Mar 16, 2021 at 3:18 PM Andrey Rahmatullin wrote:
> On Tue, Mar 16, 2021 at 01:05:11PM -0400, Aaron Boxer wrote:
> > Hello,
> > I have what I hope is a fix for the build failure on i386.
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985116
> >
> &g
On Tue, Mar 16, 2021 at 3:18 PM Andrey Rahmatullin wrote:
> On Tue, Mar 16, 2021 at 01:05:11PM -0400, Aaron Boxer wrote:
> > Hello,
> > I have what I hope is a fix for the build failure on i386.
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985116
> >
> &g
On Wed, Mar 17, 2021 at 5:43 PM Andrey Rahmatullin wrote:
> On Tue, Mar 16, 2021 at 06:13:43PM -0400, Aaron Boxer wrote:
> > > > Hello,
> > > > I have what I hope is a fix for the build failure on i386.
> > > > https://bugs.debian.org/cgi-bin/bugreport
Hi Guys,
Just a polite ping about my recently uploaded new package for
a majour release of my library.
Thanks,
Aaron
Hello Again,
I've upgraded this package priority to high as it fixes a CVE
present in previous version.
It would be great if we can get this migrated.
Thanks,
Aaron
On Tue, Jun 8, 2021 at 12:11 PM Aaron Boxer wrote:
> Hi Guys,
> Just a polite ping about my recently uploaded new pack
oops, never mind - I see Bullseye is in freeze.
On Wed, Jul 7, 2021 at 10:00 AM Aaron Boxer wrote:
> Hello Again,
> I've upgraded this package priority to high as it fixes a CVE
> present in previous version.
> It would be great if we can get this migrated.
> Thanks,
>
Hello!
The libgrokj2k was removed from Debian due to build issues
with gcc 11. I have fixed this problem, and a host of other bugs.
I would be much obliged if my package at
https://mentors.debian.net/package/libgrokj2k/
could be uploaded.
Thanks very much,
Aaron
Hello!,
I have just updated the latest 9.7.5 version of my JPEG 2000 codec to
mentors.
Could someone be so kind as to transfer it over to Debian ?
https://mentors.debian.net/package/libgrokj2k/
Thanks so much,
Aaron
Hi Folk,
I just uploaded a new package for version 10.0 of this library.
Would someone be so kind as to upload the new package to unstable ?
https://mentors.debian.net/package/libgrokj2k/
Many Thanks,
Aaron
On Thu, Sep 8, 2022 at 11:00 AM Adam Borowski wrote:
> On Thu, Sep 08, 2022 at 10:11:45AM -0400, Aaron Boxer wrote:
> > I just uploaded a new package for version 10.0 of this library.
> > Would someone be so kind as to upload the new package to unstable ?
> >
> >
Here is the warning report
https://udd.debian.org/lintian/?packages=libgrokj2k
and explanation of the warning
https://lintian.debian.org/tags/executable-stack-in-shared-library
I ran `readelf -l` on the .so, and I noticed that there is no E flag
on the GNU_STACK entry. So, it looks like this is
a, I missed that. mips66el is not a target platform, so I suppose I can
ignore this warning.
On Mon, Sep 12, 2022 at 8:47 AM Andrey Rahmatullin wrote:
> On Mon, Sep 12, 2022 at 08:37:34AM -0400, Aaron Boxer wrote:
> > Here is the warning report
> >
> > https://u
Thanks, not a big deal then :)
On Mon, Sep 12, 2022 at 8:50 AM David Bürgin wrote:
> Aaron Boxer:
> > Here is the warning report
> >
> > https://udd.debian.org/lintian/?packages=libgrokj2k
> >
> > and explanation of the warning
> >
> > https://linti
On Mon, Sep 12, 2022 at 8:59 AM Andrey Rahmatullin wrote:
> On Mon, Sep 12, 2022 at 08:49:53AM -0400, Aaron Boxer wrote:
> > mips66el is not a target platform
> What do you mean?
>
by that, I mean I don't have access to this platform for my own testing,
and I doubt there are
Hello,
My codec project uses SIMD code for x86 and AArch64 architectures. Also, as
there are different versions of SIMD i.e. SSE vs AVX vs AVX2, the project
uses a library that builds multiple versions of the accelerated code and
chooses which version to use at runtime.
https://github.com/google/h
On Mon, Sep 12, 2022 at 10:37 AM Andrey Rahmatullin wrote:
> On Mon, Sep 12, 2022 at 10:05:36AM -0400, Aaron Boxer wrote:
> > My codec project uses SIMD code for x86 and AArch64 architectures. Also,
> as
> > there are different versions of SIMD i.e. SSE vs AVX vs AVX2, the
On Tue, Sep 13, 2022 at 2:58 AM Andrey Rahmatullin wrote:
> On Mon, Sep 12, 2022 at 05:25:27PM -0400, Aaron Boxer wrote:
> > Thanks, Andrey. I have fixed this problem. v10.0,0 has just been uploaded
> > to unstable - would you
> > recommend releasing a new version 10.0.1 wi
On Mon, Sep 12, 2022 at 11:45 PM Paul Wise wrote:
> On Mon, 2022-09-12 at 10:05 -0400, Aaron Boxer wrote:
>
> > My codec project uses SIMD code for x86 and AArch64 architectures.
> > Also, as there are different versions of SIMD i.e. SSE vs AVX vs
> > AVX2, the project us
Hello,
I currently have failed builds on mipsel and armel archs.
For these systems, it appears that I need to link explicitly
to libatomic. I've added the link flag, but the failures persist.
Any suggestions on setting up VMs for these architectures so
I can directly debug my builds ?
Thanks,
Aar
On Wed, Sep 14, 2022 at 10:32 AM Bo YU wrote:
> Hi,
> On Wed, Sep 14, 2022 at 09:45:45AM -0400, Aaron Boxer wrote:
> >Hello,
> >I currently have failed builds on mipsel and armel archs.
> >For these systems, it appears that I need to link explicitly
> >to libatomic.
Hello,
I have just pushed a new version to mentors that fixes the build on armel
and mipsel.
https://mentors.debian.net/package/libgrokj2k/
If this could be uploaded it would be greatly appreciated !
Aaron
On Fri, Sep 16, 2022 at 2:18 PM Adam Borowski wrote:
> On Fri, Sep 16, 2022 at 12:10:57PM -0400, Aaron Boxer wrote:
> > I have just pushed a new version to mentors that fixes the build on armel
> > and mipsel.
> >
> > https://mentors.debian.net/package/libgrokj2
On Fri, Sep 16, 2022 at 3:10 PM Aaron Boxer wrote:
>
>
> On Fri, Sep 16, 2022 at 2:18 PM Adam Borowski wrote:
>
>> On Fri, Sep 16, 2022 at 12:10:57PM -0400, Aaron Boxer wrote:
>> > I have just pushed a new version to mentors that fixes the build on
>> armel
https://qa.debian.org/bls/packages/l/libgrokj2k.html
>From the build logs, I am unable to find which compiler flags are hidden.
What's the best way of getting more information about the warning ?
Thanks!
On Mon, Sep 19, 2022 at 3:10 PM Jeremy Sowden wrote:
> On 2022-09-18, at 20:35:37 -0400, Aaron Boxer wrote:
> > https://qa.debian.org/bls/packages/l/libgrokj2k.html
> >
> > >From the build logs, I am unable to find which compiler flags are
> hidden.
> > Wh
On Mon, Sep 19, 2022 at 5:07 PM Aaron Boxer wrote:
>
>
> On Mon, Sep 19, 2022 at 3:10 PM Jeremy Sowden wrote:
>
>> On 2022-09-18, at 20:35:37 -0400, Aaron Boxer wrote:
>> > https://qa.debian.org/bls/packages/l/libgrokj2k.html
>> >
>> > >From th
Hi Folks,
I've just updated libgrokj2k on the mentors site - if someone could please
upload it to unstable, I would greatly appreciate it!
https://mentors.debian.net/package/libgrokj2k/
Thanks,
Aaron
63 matches
Mail list logo
