Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging of
https://rubygems.org/gems/ruby-magic-static
It is a dependency of gitlab 13.9.5
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging of https://rubygems.org/gems/mini_portile2
which is a build dependency of ruby-magic-static gem, which in turn is
a dependency of gitlab 13.9.5
Package: gem2deb
Version: 1.4
Since the gemspec file has some binary data quilt is failing to create
a patch. Attached is the generated gemspec file. I had to manually
remove the offending characters using gedit and add it as
debian/gemspec for the build to work.
I'm not sure if it is
On Wed, 24 Mar 2021 12:44:28 +0530 Pirate Praveen
wrote:
> On Tue, 23 Mar 2021 21:31:28 + Mike Gabriel
wrote:
> > Package: ruby-licensee
> > Version: 9.14.1-1
> > Severity: grave
> > X-Debbugs-Cc: prav...@debian.org
> >
> > The ruby-licens
On Tue, 23 Mar 2021 21:31:28 + Mike Gabriel
wrote:
> Package: ruby-licensee
> Version: 9.14.1-1
> Severity: grave
> X-Debbugs-Cc: prav...@debian.org
>
> The ruby-licensee package as currently found in Debian experimental
> lacks the entire library folder of the licensee Gem. These files,
On 2021, മാർച്ച് 18 8:22:54 PM IST, Andrius Merkys wrote:
>Hello,
>
>On 2021-03-15 13:45, Pirate Praveen wrote:
>> On 2021, മാർച്ച് 15 4:21:37 PM IST, Nilesh Patra wrote:
>>>> $ node-sass
>>>> /usr/share/nodejs/normalize-package-data/lib/fixer.
On 2021, മാർച്ച് 15 4:21:37 PM IST, Nilesh Patra wrote:
>> Dear Maintainer,
>>
>> * What led up to the situation?
>>
>> I installed node-node-sass, and ran its installed binary node-sass.
>>
>> * What exactly did you do (or not do) that was effective (or
>> ineffective)?
>>
>> Ran the
[Ccing debian-release]
On Wed, 17 Feb 2021 14:01:40 + Julian Gilbey wrote:
> On Sun, Feb 14, 2021 at 02:26:30PM +0100, Jonas Smedegaard wrote:
> > I still recommend to request release team to ignore for this release
> > instead of lowering sverity, but don't care anough about this
On Fri, Mar 12, 2021 at 5:52 pm, Maximilian Stein wrote:
This matching is expected.
Can you share the error message? ruby-doorkeeper 5.3 to 5.5 update
is not supposed to break gitlab.
Basically, the rake commands (check, backup, ...) started to fail:
$ gitlab-rake gitlab:check :(
Control: reassign -1 gitlab
On Fri, Mar 12, 2021 at 10:02 pm, Pirate Praveen
wrote:
On Fri, 12 Mar 2021 10:57:45 +0100 Maximilian Stein
wrote:
> Package: gitlab-apt-pin-preferences
> Version: 2021.03.09
> Severity: normal
>
> Dear Maintainer,
>
> I am experimentin
On Fri, 12 Mar 2021 10:57:45 +0100 Maximilian Stein
wrote:
> Package: gitlab-apt-pin-preferences
> Version: 2021.03.09
> Severity: normal
>
> Dear Maintainer,
>
> I am experimenting with gitlab-apt-pin-preferences to get Gitlab's
> dependencies right. However, I noticed that now ruby-doorkeeper
Package: aptitude
Version: 0.8.11-7
When building node-mermaid
(https://salsa.debian.org/js-team/node-mermaid and buster-backports
branch or debian/8.9.1+ds+_cs26.20.25-1_bpo10+1 tag) with this command,
sbuild -A -s --force-orig-source -c buster-amd64-sbuild
--extra-repository='deb
t@omv:~# apt-show-versions -a ruby-pg-query
>ruby-pg-query not installed (not available)
ruby-pg-query is available people.debian. org/~praveen/staging. This was
mentioned in wiki for gitlab 13.8.
>On 11.03.2021 18:23, Pirate Praveen wrote:
>> On Mon, 11 Jan 2021 18:10:34 +020
On Mon, 11 Jan 2021 18:10:34 +0200 Dragos Jarca
wrote:
> Just to know, in previous version I have some trouble with licensee,
and
> I do the following to solve the problem:
>
> gitaly(13.4.6+dfsg1-2) and gitlab(13.4.7-2) have in Gemfile:
>
> gem 'rugged', '~> 0.28'
> ...
> gem 'licensee', '~>
On 2021, മാർച്ച് 9 12:56:44 AM IST, Mike Gabriel
wrote:
>Package: gitlab
>Version: 13.7.8+ds1-1~fto10+1
>Severity: serious
>
>Hi Praveen,
>
>here comes the other issue I am facing. Occurred with 13.7.7 and also
>occurs with 13.7.8:
>
>When I open a Git repos
On 2021, മാർച്ച് 8 1:24:48 AM IST, Antonio Terceiro wrote:
>On Sun, Mar 07, 2021 at 11:01:16PM +0530, Pirate Praveen wrote:
>> [adding release team]
>>
>> On Sun, Mar 7, 2021 at 10:49 pm, Utkarsh Gupta wrote:
>> > Hi Praveen,
>> >
>> >
[adding release team]
On Sun, Mar 7, 2021 at 10:49 pm, Utkarsh Gupta
wrote:
Hi Praveen,
On Sun, Mar 7, 2021 at 10:15 PM Pirate Praveen
wrote:
It looks like we will have to remove ruby-vcr and we will have to
disable tests for the following packages. I don't think there is
another way
It looks like we will have to remove ruby-vcr and we will have to
disable tests for the following packages. I don't think there is
another way, thoughts?
No reverse dependencies.
reverse-depends -b ruby-vcr
Reverse-Build-Depends
* nanoc
* ruby-coveralls
* ruby-graphlient
* ruby-mixlib-install
Package: puma
Version: 5.2.2-1
Severity: wishlist
Currently some failing tests are disabled via debian/ruby-tests.rake
t.test_files = FileList['test/**/*_test.rb'] +
FileList['test/**/test_*.rb'] -
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging of https://rubygems.org/gems/pg_query
This will replace ruby-gitlab-pg-query (which is a fork). Dependency of
gitlab 13.8.x
On Thu, 04 Feb 2021 20:49:39 +0200 Adrian Bunk wrote:
> /usr/lib/ruby/2.7.0/net/http.rb:960:in `initialize': Failed to open
TCP connection to codeload.github.com:443 (Network is unreachable -
connect(2) for "codeload.github.com" port 443) (Errno::ENETUNREACH)
>from
Package: gajim
severity: wishlist
I think gajim-urlimagepreview should be enabled by default as people
coming from most chat apps expect that feature by default and it
improves user experience a lot.
On 2021, മാർച്ച് 4 9:31:42 PM IST, Mike Gabriel
wrote:
>Control: tags -1 patch
>
>Hi Praveen,
>
>On Mi 03 Mär 2021 16:12:47 CET, Pirate Praveen wrote:
>
>> On 2021, മാർച്ച് 3 8:17:44 PM IST, Mike Gabriel
>> wrote:
>>> Hi Praveen,
>>>
>
On 2021, മാർച്ച് 3 8:17:44 PM IST, Mike Gabriel
wrote:
>Hi Praveen,
>
>On Mi 03 Mär 2021 15:38:46 CET, Pirate Praveen wrote:
>
>> On 2021, മാർച്ച് 3 7:54:13 PM IST, Mike Gabriel
>> wrote:
>>> Package: gitlab
>>> Version: 13.7.7-2~fto10+1
>>&
On 2021, മാർച്ച് 3 7:54:13 PM IST, Mike Gabriel
wrote:
>Package: gitlab
>Version: 13.7.7-2~fto10+1
>Severity: serious
>
>Hi Praveen,
>
>I can't upgrade gitlab from 13.4.7-2~fto10+1, I get the below error
>messages (webpack and ttf fonts). Don't wonder about the /srv
On 2021, മാർച്ച് 3 4:20:32 PM IST, Andreas Beckmann wrote:
>Package: gitlab
>Version: 13.4.7-2
>Severity: serious
>User: debian...@lists.debian.org
>Usertags: piuparts
>
>Hi,
>
>during a test with piuparts I noticed your package failed to install. As
>per definition of the release team this
On Tue, 2 Mar 2021 07:55:28 +0200 Dragos Jarca
wrote:
> For upgrade to work on experimental, I also removed
>
> /etc/gitlab/feature_flags/ops/dynamic_image_resizing.yml
>
> /etc/gitlab/initializers/rack_attack_global.rb
Thanks for these, I have now added them to maintscript for removing
On Sun, Feb 28, 2021 at 11:00 pm, Pirate Praveen
wrote:
On Sun, 28 Feb 2021 19:04:24 +0530 Pirate Praveen
wrote:
> Asking upstream for help
> https://gitlab.com/gitlab-org/gitlab/-/issues/323024
Removing these 3 files makes the upgrade to proceed,
/usr/share/gitlab/config/feature
On Sun, 28 Feb 2021 19:04:24 +0530 Pirate Praveen
wrote:
> Asking upstream for help
> https://gitlab.com/gitlab-org/gitlab/-/issues/323024
Removing these 3 files makes the upgrade to proceed,
/usr/share/gitlab/config/feature_flags/ops/api_kaminari_count_with
_limit.yml
/usr/share/
Control: forwarded -1
https://gitlab.com/gitlab-org/gitlab/-/issues/323024
On Sun, Feb 28, 2021 at 6:56 pm, Pirate Praveen
wrote:
On Sat, 27 Feb 2021 17:33:40 +0530 Pirate Praveen
wrote:
> This commit makes the upgrade work.
>
>
https://salsa.debian.org/ruby-team/gitlab
On Sat, 27 Feb 2021 17:33:40 +0530 Pirate Praveen
wrote:
> This commit makes the upgrade work.
>
>
https://salsa.debian.org/ruby-team/gitlab/-/commit/98741d55b7ed4b5eb1985981ab82e171c7d0e0c9
Looks like this did not really fix the issue when I tried it again on
another machine :(
On Wed, 9 Dec 2020 20:08:31 +0200 Dragos Jarca
wrote:
> Hi
>
> Some news about this bug?
>
> There are a lot of packages that depend of libsass and I cannot
install
> updates because use libsass 3.6.1 because of gitlab workaround.
>
> Now gitlab work with newer version of libsass?
It is
On Fri, 26 Feb 2021 14:40:46 +0530 Pirate Praveen
wrote:
> On Tue, 23 Feb 2021 00:47:30 +0530 Pirate Praveen
> wrote:
> > Installing 13.7.7 on a clean system (after purge) works, but fails
> when
> > upgrading from 13.6.7.
>
> What I found out so far is this,
&
On Tue, 23 Feb 2021 00:47:30 +0530 Pirate Praveen
wrote:
> Installing 13.7.7 on a clean system (after purge) works, but fails
when
> upgrading from 13.6.7.
What I found out so far is this,
/etc/gitlab/initializers/flipper.rb was obsoleted in 13.6 but we did
not remove it and tha
Package: gitlab
Severity: grave
Control: forwarded -1 https://github.com/yarnpkg/berry/issues/2384
This seems to be fixed in master but there is no release yet.
On Mon, 22 Feb 2021 22:59:51 +0530 Pirate Praveen
wrote:
> Package: gitlab
> Severity: important
> Control: tags -1 help
>
> I'm trying to update gitlab to 13.7.7 (master-13.7 branch in salsa),
>
> but installation fails with
Installing 13.7.7 on a clean system (after pu
Package: gitlab
Severity: important
Control: tags -1 help
I'm trying to update gitlab to 13.7.7 (master-13.7 branch in salsa),
but installation fails with
Bundle complete! 212 Gemfile dependencies, 393 gems now installed.
Gems in the groups development and test were not installed.
Use `bundle
On Sat, Feb 20, 2021 at 2:46 pm, Pirate Praveen
wrote:
So need help figuring out which packages need pinning here.
Fixed by updating pin on ruby-batch-loader.
On Sat, Feb 20, 2021 at 2:24 pm, Pirate Praveen
wrote:
Source repo
https://salsa.debian.org/fasttrack-team/gitlab-apt-pin-preferences
Binary package
https://people.debian.org/~praveen/fasttrack-staging/pool/main/g/gitlab-apt-pin-preferences/
More testing and feedback welcome.
# apt
Source repo
https://salsa.debian.org/fasttrack-team/gitlab-apt-pin-preferences
Binary package
https://people.debian.org/~praveen/fasttrack-staging/pool/main/g/gitlab-apt-pin-preferences/
More testing and feedback welcome.
node-babel-runtime needs to be installed from buster-backports for
yarnpkg to work, probably a bug in yarnpkg dependency declaration.
Package: gitlab
severity: wishlist
Attached file can be saved as /etc/apt/preferences.d/99gitlab to make
apt resolve dependencies correctly in fasttrack. I think the best place
for this would be fasttrack-archive-keyring. Comments?
Package: node-worker-loader node-loader-utils
On 2021, ഫെബ്രുവരി 19 6:23:13 PM IST, Maximilian Stein wrote:
>
>>> You will need to regenerate Gemfile.lock. See the wiki page for steps.
>>>
>>> It saves the exact versions used during installation in Gemfile.lock
>>>
>>> It is supposed to be handled automatically for most gems, but it does
On Fri, Feb 19, 2021 at 12:33 pm, Pirate Praveen
wrote:
On 2021, ഫെബ്രുവരി 19 2:22:27 AM IST, Maximilian
Stein wrote:
Uploaded gitaly 13.7.5 to fasttrack-staging. If someone can
confirm this, I will move it to fasttrack.
Hi,
I can confirm that gitaly-git2go is now present
On 2021, ഫെബ്രുവരി 19 2:22:27 AM IST, Maximilian Stein wrote:
>
>> Uploaded gitaly 13.7.5 to fasttrack-staging. If someone can confirm this, I
>> will move it to fasttrack.
>
>
>Hi,
>
>I can confirm that gitaly-git2go is now present, however gitlab now
>refuses to start since it's missing
On 2021, ഫെബ്രുവരി 18 12:15:14 AM IST, Pirate Praveen
wrote:
>
>
>On 2021, ഫെബ്രുവരി 17 8:27:19 PM IST, Pirate Praveen
> wrote:
>>
>>From what I understood from the logs, the error is coming from golang-git2go
>>and not from gitaly.
>>
>
>I got g
On 2021, ഫെബ്രുവരി 17 8:27:19 PM IST, Pirate Praveen
wrote:
>
>From what I understood from the logs, the error is coming from golang-git2go
>and not from gitaly.
>
I got gitaly-git2go built but it is not yet ready for an upload.
1. gitaly 13.7 worked but not
On 2021, ഫെബ്രുവരി 17 4:47:21 PM IST, Nilesh Patra wrote:
>Hi,
>
>On Wed, 17 Feb 2021 at 14:21, Pirate Praveen
>wrote:
>
>>
>>
>> On Wed, Feb 17, 2021 at 2:06 pm, Pirate Praveen
>> wrote:
>> > This is a bug in golang-gopkg-libgit2-git2go.v28-
On Wed, Feb 17, 2021 at 2:06 pm, Pirate Praveen
wrote:
This is a bug in golang-gopkg-libgit2-git2go.v28-dev
We will have to patch this to look for libgit2.pc from system
apt-file find libgit2.pc
libgit2-dev: /usr/lib/x86_64-linux-gnu/pkgconfig/libgit2.pc
But pkg-config --static libgit2
On Tue, 16 Feb 2021 18:31:45 +0100 Maximilian Stein
wrote:
> Hi,
> > This particular binary is built using go build tags, which I'm not
able integrate into dh-golang workflow yet.
> >
> > I'm trying. I was able to build it once in the past but I don't
seem to have committed it.
> >
> I was
On 2021, ഫെബ്രുവരി 16 5:41:22 PM IST, Antoine Le Gonidec
wrote:
>I built the missing binary from the upstream source, using the v13.6.5 tag.
>cf. https://gitlab.com/gitlab-org/gitaly.git
>The build environment is a Buster + backports + fasttrack, actually a copy of
>the server I run GitLab
On Sun, 13 Dec 2020 21:30:41 +0100 Jonas Smedegaard wrote:
> Package: node-uglifyjs-webpack-plugin
> Version: 1.3.0-9
> Severity: serious
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> node-uglifyjs-webpack-plugin is dead since 1.5 years, already carries a
> patch to not actually use
On 2021, ഫെബ്രുവരി 14 2:55:33 PM IST, Jonas Smedegaard wrote:
>Quoting Pirate Praveen (2021-02-14 08:32:08)
>>
>>
>> On 2021, ഫെബ്രുവരി 14 12:44:09 PM IST, Julian Gilbey wrote:
>> >webpack depends on node-uglifyjs-webpack-plugin, which in turn has a
On 2021, ഫെബ്രുവരി 14 12:44:09 PM IST, Julian Gilbey wrote:
>Source: node-webpack
>Version: 4.43.0-6
>Severity: serious
>
>webpack depends on node-uglifyjs-webpack-plugin, which in turn has a
>serious bug report against it because it is abandoned upstream.
We should reduce severity of that
On 2021, ഫെബ്രുവരി 13 8:19:52 PM IST, Chris Hofstaedtler
wrote:
>Hi,
>
>* Debian Bug Tracking System [210213 14:48]:
>> #980580: ruby-ruby2ruby: FTBFS: ERROR: Test "ruby2.7" failed: RuntimeError:
>> unknown arg type nil
>
>have you noticed the autopkgtest failures on all archs?
Yes, it
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging of https://rubygems.org/gems/gitlab-experiment
Dependency of gitlab 13.7
Package: ruby-graphlient
Version: 0.5.0-3
Severity: important
Currently tests are disabled because it fails on buildd but unable to
reproduce the failure locally. It'd be good to enable it once it
migrates to testing.
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging of https://rubygems.org/gems/asciidoctor-kroki
Dependency of gitlab 13.7
On 2021, ഫെബ്രുവരി 4 12:10:44 AM IST, Eric Van Buggenhaut
wrote:
>Package: gitlab
>Version: 13.5.7-1~fto+1
>Severity: important
>
>Dear Maintainer,
>
>I have been unable to complete an install of gitlab:
>
># apt -t buster-backports install gitlab/buster-fasttrack
On Tue, 02 Feb 2021 14:26:24 +0530 Pirate Praveen
wrote:
> Reproduce the issue during upgrade on a clean machine. Installed
gitlab
> 13.5.7 then tried to upgrade to 13.6.5 and the error happened.
>
> If anyone would like to have a look I can share access to a test
> machine
On Mon, Feb 1, 2021 at 3:22 pm, Pirate Praveen
wrote:
A clean install went fine. So probably something bad on my local test
machine.
Reproduce the issue during upgrade on a clean machine. Installed gitlab
13.5.7 then tried to upgrade to 13.6.5 and the error happened.
If anyone would
A clean install went fine. So probably something bad on my local test
machine.
Package: gitlab
Severity: important
Control: tags -1 help
When trying to update gitlab to 13.6.5 from
https://people.debian.org/~praveen/fasttrack-staging/ installation
fails with this error.
https://wiki.debian.org/gitlab#Buster_Fast_Track_Staging has steps to
reproduce
Package: ftp.debian.org
X-DebBugs-CC: debian-r...@lists.debian.org
In debian ruby_parser was originally packaged under ruby-parser instead
of ruby-ruby-parser but we renamed ruby-parser to ruby-ruby-parser
making the old ruby-parser obsolete. All reverse dependencies are
updated already to
package: wnpp
severity: wishlist
Packaging of https://rubygems.org/gems/scientist
Indirect dependency of gitlab 13.7 (via gitlab-experiment)
On 2021, ജനുവരി 27 9:41:47 PM IST, Pirate Praveen
wrote:
>Crashes in both X11 and Wayland on gnome 3.
Just tested with Window Maker and this time it did not crash. But video was
just showing black screen.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
the archive)
>>
>> You can use https://people.debian.org/~praveen/nheko/ to reproduce this
>> error.
>>
>> User glandos shared this stacktrace in upstream nheko matrix room.
>>
>> Thread 1 "nheko" received signal SIGSEGV, Segmentation fault.
>>
gstreamer1.0-vaapi should be in Depends
Package: nheko
Version: 0.8.0-1
Severity: important
Justification: voip is a new feature, there are still other
improvements worth an upgrade
I got this crash using nheko built using an older gcc 10 *till we have
gcc 10.3 is in the archive)
You can use https://people.debian.org/~praveen
Control: tags -1 pending
Added these two to Depends,
+ , gstreamer1.0-nice
+ , gstreamer1.0-qt5
gstreamer1.0-qt5 includes qmlgl
Package: nheko
Version: 0.8.0-1
Severity: important
I built nheko using an older gcc-10 from snapshot.debian.org (let me
know if anyone want to try this, I can push it to a repo till gcc-10 is
fixed in the archive).
currently nheko is missing a dependency on gspreamer nice plugins
it is
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging of https://rubygems.org/gems/gitlab-pg_query
Dependency of gitlab 13.6
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging on https://rubygems.org/gems/graphlient
a dependency of gitlab 13.6
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging on https://rubygems.org/gems/graphql-errors
Build dependency of graphlient (which is a dependency of gitlab 13.6)
On 2021, ജനുവരി 20 2:17:50 AM IST, Maximilian Stein wrote:
>
>> Someone else reported the artifacts issue was resolved in 13.5.6. See
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968626#40
>>
>Oh, sorry, i didn't mean artifact upload (bug 968626), but the Gitlab
>internal artifacts
On Mon, 11 Jan 2021 19:55:18 +0100 Lars Kruse
wrote:
> after upgrading from 13.4.7-2~fto10+1 to 13.5.6-1~fto10+1, every
issue
> view shows the following error message at the top:
>
> Failed to load sidebar lock status
Fixed in 13.5.7 in fasttrack-staging, will upload to fasttrack after
On Tue, Jan 19, 2021 at 7:52 pm, Maximilian Stein wrote:
Some good news finally.
After I switched to using only yarn for all modules (use unpatched
package.json) webpack is working fine. Now I will try to add back
the packaged modules one by one so we can know which module broke
it.
Control: reopen -1
Control: severity -1 important
Control: tags -1 help
On Tue, Jan 19, 2021 at 6:54 pm, Debian Bug Tracking System
wrote:
Your message dated Tue, 19 Jan 2021 18:50:13 +
with message-id
and subject line Bug#980406: fixed in node-xterm 3.8.1+~cs0.9.0-1
has caused the
Control: reassign -1 vmdb2
On Tue, Jan 19, 2021 at 6:08 pm, Julien Cristau
wrote:
On Sat, Dec 19, 2020 at 04:02:57PM +0530, Pirate Praveen wrote:
Package: vmdb2,xauth
Severity: wishlist
Control: block 913997 by -1
Hi,
Would you be open to change the yarn command if cmdtest renames
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging on https://rubygems.org/gems/rack-test
Build dependency of graphlient (which is a dependency of gitlab 13.6)
On Tue, Jan 19, 2021 at 5:06 pm, Xavier wrote:
Le 19/01/2021 à 15:04, Pirate Praveen a écrit :
On Tue, Jan 19, 2021 at 2:24 pm, Pirate Praveen
wrote:
Control: severity -1 serious
I was able to use xterm 3.8.1 from nmpjs.com with gitlab without
any
issues. So this is a bug
On Tue, Jan 19, 2021 at 2:24 pm, Pirate Praveen
wrote:
Control: severity -1 serious
I was able to use xterm 3.8.1 from nmpjs.com with gitlab without any
issues. So this is a bug in node-xterm debian build.
Trying to switch to rollup instead of browserify-lite, but tsc itself
is failing
Control: severity -1 serious
I was able to use xterm 3.8.1 from nmpjs.com with gitlab without any
issues. So this is a bug in node-xterm debian build.
On 2021, ജനുവരി 19 2:46:30 AM IST, Xavier wrote:
>Le 18/01/2021 à 18:47, Pirate Praveen a écrit :
>Maintaining an unsupported version means taking the risk to be unable to
>backport a security fix during stable life and LTS (we already have many
>examples).
>_Before freeze_,
On Tue, 19 Jan 2021 00:29:18 +0100 Christian Kastner wrote:
> Hi all,
>
> On Sat, 19 Dec 2020 Pirate Praveen wrote:>> Renaming the binary is
> harder, because there are at least two
> >> packages that use yarn from cmdtest during the build: gitano and
> >>
Package: node-xterm
Version: 3.8.1-4
Severity: important
When using packaged version of node-xterm in gitlab, the browser error
console has these errors and it break web IDE of gitlab (the progress
circle keeps spinning).
Source map error: Error: JSON.parse: unexpected character at line 1
On Mon, Jan 18, 2021 at 2:28 pm, Antonio Terceiro
wrote:
But the fact is that all the other reverse dependencies that used any
plugin now need to be changed accordingly. Otherwise we can just wait
for their chart features to break in subtle ways in the face of users.
Not specific to this
Control: severity -1 important
On Mon, 11 Jan 2021 18:39:31 +0100 Xavier wrote:
> Hi all,
>
> Bullseye freeze is coming and we still have problems with
node-request
> removal. In particular, node-jsdom is not easy to patch. I tried a
patch
> (not approved by upstream) but it needs a lot of
Some good news finally.
After I switched to using only yarn for all modules (use unpatched
package.json) webpack is working fine. Now I will try to add back the
packaged modules one by one so we can know which module broke it.
I will upload 13.5.7 to fasttrack now.
clipanion needs @wessberg/rollup-plugin-ts as build dependency
Package: yarnpkg
Version: 1.22.10+~cs22.25.14-1
Severity: important
Control: block 956423 by -1
Yarn 1.x branch is not receiving any updates upstream. We somehow
managed to get it build with newer versions of build dependencies for
bullseye, but we are not able to remove dependency on request
Package: leaflet-markercluster
Version: 1.4.1~dfsg-9
Severity: important
As tracked in
https://wiki.debian.org/Javascript/Nodejs/Transitions/Rollup-plugin-json-legacy-rm
and notified in
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2021-January/050132.html
It'd be good to
Package: leaflet
Version: 1.7.1~dfsg-2
Severity: important
As tracked in
https://wiki.debian.org/Javascript/Nodejs/Transitions/Rollup-plugin-json-legacy-rm
and notified in
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2021-January/050132.html
It'd be good to drop the
Package: wnpp
severity: wishlist
Owner: Pirate Praveen
Packaging of https://rubygems.org/gems/graphql-client
Dependency of gitlab 13.6
Package: aspcud,aptitude
severity: important
When trying to build node-buble (and any other package that build
depends on node-acorn provided as a virtual package by
node-debbundle-acorn in buster-backports)
(I)Distcheck: Cudf Universe: 61258 packages
(I)Distcheck: --checkonly specified,
Package: node-yaml,pkg-js-tools
Severity: important
When building node-yaml with nocheck build profile, the build fails
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=nodejs
mkdir node_modules
internal/modules/cjs/loader.js:638
throw err;
^
On Wed, Jan 13, 2021 at 12:22 pm, Xavier wrote:
CC to pkg-javascript-devel for node-yarnpkg elements
We can try to update yarnpkg to version 2 by building corepack [1].
I need help with these packages,
New modules: clipanion terser-webpack-plugin ts-loader
@zkochan/cmd-shim
Update
On 2021, ജനുവരി 11 7:00:11 PM IST, Dragos Jarca
wrote:
>Package: gitlab
>Followup-For: Bug #979563
>
>Dear Maintainer,
>
>My instance work great after upgrade to 13.5.6.1!
>
>I can see the content of folder and files on UI.
>I can fetch, push, etc.
>I added versions off packages if I use,
On 2021, ജനുവരി 11 12:17:15 AM IST, Antoine Le Gonidec
wrote:
>I see a new update (13.5.6) is available through fasttrack-staging. Is it
>supposed to include a fix for the missing assets issue discussed here, or
>would it probably still trigger it?
It still has that bug, but includes some
On 2021, ജനുവരി 10 10:45:45 PM IST, Maximilian Stein wrote:
>Is there anything else that we could try to workaround the issues?
>
Try copying that directory from older versions ?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
401 - 500 of 4028 matches
Mail list logo
